Communication failure in the supervisory (primary) network

To understand the effects of a communication failure at the Supervisory Network level, refer to the matrix on the following page. It presents the original status of the redundant pair before the failure as well as the cause of the problem and the final condition.

The matrix shows the values of two attributes in the AppEngine used to monitor the status of the redundant pair. They are RedundancyPartnerStatus and RedundancyStatus. The attributes (and other key attributes) are included.

Considerations

The failover scenarios described in this section refer to topologies where there is at least one more platform besides the two hosting the redundant pair, i.e. client/server configuration.

If the topology consists of just two platforms hosting the redundant pair (peer-to-peer configuration) a failover does not occur in the event of a communication failure in the supervisory network. Instead, the Redundancy.PartnerStatus attribute is set to missed heartbeats while both partners synchronize data through the RMC.

In this case, the user can execute the failover either manually or via scripting, if required.