Peer-to-peer failover functionality
The probe supports failover configurations where two probes run simultaneously. One probe acts as the master probe, sending events to the ObjectServer; the other acts as the slave probe on standby. If the master probe fails, the slave probe activates.
Standard peer-to-peer behavior
By default, the slave probe establishes a connection with, and polls, the TL1 devices and receives the same events as the master probe, but it does not forward the events to the ObjectServer. If the master probe shuts down, the slave probe stops receiving heartbeats from the master probe and any events it receives thereafter are forwarded to the ObjectServer on behalf of the master probe. When the master probe is running again, the slave continues to receive events, but stops sending them to the ObjectServer.
Reducing event traffic
When two TL1 probes are running in a peer-to-peer failover configuration and both are polling devices, there can be an excessive amount of traffic for the client TL1 devices or gateways. This can cause the failure of the TL1 management in the client network.
To reduce event traffic, you can configure the slave probe to not establish a connection with any TL1 device until failover occurs by setting the SlaveMode property of the slave probe to 1.