To take full advantage of SRRP resiliency and diagnostic capabilities, the SRRP instance should be tied to a MCS peering that terminates on the redundant node. The SRRP instance is tied to the peering using the srrp srrp-id command within the appropriate MCS peering configuration. Once the peering is associated with the SRRP instance, MCS synchronizes the local information about the SRRP instance with the neighbor router. MCS automatically derives the MCS key for the SRRP instance based on the SRRP instance ID. For example, an SRRP instance ID of 1 would appear in the MCS peering database with a MCS-key srrp-0000000001.
The SRRP instance information stored and sent to the neighbor router consists of:
The SRRP instance MCS key
Containing service type and ID
Containing subscriber IP interface name
Subscriber subnet information
Containing group IP interface information
The SRRP group IP interface redundant IP interface name, IP address and mask
The SRRP advertisement message SAP
The local system IP address (SRRP advertisement message source IP address)
The Group IP interface MAC address
The SRRP gateway MAC address
The SRRP instance administration state (up / down)
The SRRP instance operational state (disabled / becoming-backup / backup / becoming-master / master)
The current SRRP priority
Remote redundant IP interface availability (available / unavailable)
Local receive SRRP advertisement SAP availability (available / unavailable)