...

Should the primary address become inaccessible, then NMIS switches polling over to the fallback host_backup address, and raises an event  called 'Node Polling Failover'; the node is also flagged as being in 'degraded' state. This event is cleared if and when the primary address becomes reachable again.

When NMIS polling has fallen back to the secondary address, the node's status shows "Node Polling Failover" as one of the reasons for the degraded state, like in the screenshot below:

...

If all addresses of the node are unreachable, then NMIS flags the node as 'unreachable'.

In NMIS 8.6.7 and newer, the "Node Polling Failover" event is also raised if the primary address becomes unreachable (i.e. if fpingd detects it as unpingable). Additionally, a separate event "Backup Host Down" is raised if the host_backup address is unreachable. Either events' presence causes the node to be flagged 'degraded'.

Known Limitations

• NMIS currently pings both addresses in parallel.
  Changes of ping status do not cause events to be raised or cleared.
• Only one set of Ping (Response Time, Packet Loss) statistics is recorded.
  The Ping statistics will switch transparently from primary to fallback address if and when the primary becomes unreachable.
• Polling failover is not available for WMI data collection.
• Polling failover is not available for Service Monitoring.
• The polling failover decision is made for each ping, collect or update operation, regardless of both previous results and of which addresses are pingable.
  Whenever an SNMP connection needs to be opened, NMIS tries the primary address first, and if that fails, switches to the secondary.
  This can introduce undesirable delays to a node's polling, but minimises latency for switching back when the primary address becomes accessible again.