[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Redundancy

You can configure SRC-ACP redundancy for a region of the network by installing SRC-ACP on two different hosts, installing a naming service application on the SAE, and connecting both SRC-ACP hosts to the SAE (see Figure 45). One SRC-ACP acts as the primary application, and the other as the secondary application.

NOTE: Both SRC-ACPs in a redundant pair must operate in the same mode. You cannot configure an SRC-ACP in edge mode and an SRC-ACP in backbone mode as a redundant pair.


The primary and secondary SRC-ACPs communicate with each other through a CORBA interface. When you start each SRC-ACP (see Starting SRC-ACP), it will register its redundancy CORBA interface with the naming service application, and import the interface for the other SRC-ACP from the naming service application.

Each SRC-ACP continuously monitors the other's availability. The primary SRC-ACP receives data from the SAE and sends any changes to the secondary SRC-ACP. If the secondary SRC-ACP is unavailable, the primary SRC-ACP caches the data to send when the secondary SRC-ACP becomes available.

If the primary SRC-ACP becomes unavailable, the secondary SRC-ACP immediately notifies the naming service application and assumes the primary role. If the former primary SRC-ACP recovers very quickly, it will again assume the primary role. However, if the former primary SRC-ACP recovers more slowly, it will assume the primary role only if the former secondary SRC-ACP becomes unavailable.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]