Redundancy and State Synchronization

You can configure SRC ACP to synchronize states with the SAE.

State synchronization enables the current state to be transferred when SRC ACP has started up or lost its state. SRC ACP does not have to keep a local and persistent copy of the state. However, SRC ACP requires additional bandwidth to transfer state information that can affect performance.

You can configure SRC ACP redundancy for a region of the network by installing SRC ACP on two different hosts and connecting both SRC ACP hosts to the SAE (see SRC ACP Overview). 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.

To configure SRC ACP redundancy, enable redundancy. In this situation, the primary and secondary SRC ACPs are set up as a community and will communicate with each other to determine the primary SRC ACP. The primary SRC ACP registers its interoperable object reference (IOR) with the SAE so that the SAE will communicate only with the primary SRC ACP. When the primary SRC ACP becomes unavailable, the secondary SRC ACP assumes the role of the primary SRC ACP and performs state synchronization if necessary.

Related Documentation

• SRC ACP Overview
• Interactions Between SRC ACP and Other Components
• Configuration Statements for SRC ACP
• Configuring SRC ACP (SRC CLI)
• Configuring SRC ACP Properties (SRC CLI)