Setting up the probe to run in peer-to-peer mode
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.
Note: Peer-to-peer failover is not supported for all probes. Probes that list the
Mode, PeerHost, and PeerPort
properties when you run the command
$OMNIHOME/probes/nco_p_probename -dumpprops
support peer-to-peer failover.To set up a peer-to-peer failover relationship:
- For the master instance, set the Mode property to
master
and the PeerHost property to the network element name of the slave. - For the slave instance, set the Mode property to
slave
and the PeerHost property to the network element name of the master. - For both instances, set the PeerPort property to the port through which the master and slave communicate.
While the slave probe receives heartbeats from the master probe, it does not forward events to the ObjectServer. If the master probe shuts down, the slave probe stops receiving heartbeats from the master 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 probe continues to receive events, but no longer sends them to the ObjectServer.