Create hosts for OOB

[dmcken]

Is your feature request related to a problem? Please describe.
The physical state of the machine is not always available via the OS running on the machine, quite a few enterprise servers have a IPMI / BMC interface of some sort (HP - iLo, Dell - iDRAC) which gives a way to monitor the physical hardware.

Describe the solution you'd like
What I would like is to have the primary IP use the platform (if set) to monitor the OS running on the server, (e.g. proxmox, windows, linux) and the OOB IP be used to pull in the template via the device-type set for the server. This monitoring is separate from the host for the OS itself (naming could be "--<serial #>").

This needs to take into account OOB IPs set on I guess I would call embedded systems (most commonly network devices, e.g. Cisco, Juniper, Mikrotik, etc). Add another custom field (I would say to the device type) to flag that this is separate from the OS? This would be opt-in (i.e. off by default and only turned on the device-types that can be identified as having a separate BMC).

Describe alternatives you've considered
Trying to maintain a single host with multiple templates (and underlying macros for stuff like community strings and passwords) I believe is asking for problems. At the very least most BMCs don't support running external code (given their privileged low-level access to the hardware) like the zabbix-agent and are usually monitored by SNMP. Re-purposing the hardware can happen which only affects the OS but you may want to continue tracking any issues with the physical hardware separately.