To implement dual homing using SRRP

Steps
 
1 

Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens.

2 

Choose a VPRN service and click Properties. The VPRN Service (Edit) form opens.

3 

Create the redundant interface used for SRRP out-of-band messaging between the two NEs:

Note: The two sites that participate in the dual homing configuration do not have to be part of the same service.

Ensure that the pair of sites each contains a properly configured subscriber interface and SAPs underneath the group interface that are participating in the redundant configuration.

Ensure that all subscriber interface IP addresses have a gateway address configured on them.

  1. On the service navigation tree, click on the site to which you need to add the redundant pair; expand the entries for that site.

  2. Right-click on Redundant Interfaces for one site of the redundant pair, and choose Create Redundant Interface. The Redundant Interface (Create) form opens.

  3. Configure the required parameters.

  4. Click on the Addresses tab.

  5. Click Create. The IP Address (Create) form opens.

  6. To specify IP addresses for the redundant interface on the current and remote sites, configure the required parameters.

    The remote IP address must be on the same subnet as the redundant interface IP address of the current site. For example, if the IP address of the current site is 7.7.7.7, with a prefix length of 24, then the redundant interface IP address of the remote site must be 7.7.7.d, where d is a value from 0 to 255, excluding 7.

  7. Save the changes and close the forms.

4 

Create an SDP spoke binding between the current and remote sites. The Source Interface is the Redundant Interface you created in Step 3 and the Tunnel Termination Site is the remote site. The Return Tunnel must come from the remote site. See To configure a VPRN spoke SDP binding for more information.

5 

Assign the Redundant Interface to the Group Interface for the current site.

  1. On the service navigation tree under the Subscriber Interface, right-click on the Group Interface and choose Properties. The VPRN Group Interface (Edit) form opens.

  2. Select a redundant interface you created in Step 3 in the Redundant Interface panel.

  3. Save the changes and close the form.

6 

Create an SRRP Instance for the current site.

  1. On the service navigation tree under Group Interfaces, right-click on the SRRP Instances item for the current site, and choose Create SRRP Instance. The SRRP Instance (Create) form opens.

  2. Configure the required parameters.

    The SRRP ID value must be the same for the current and remote sites.

  3. Click on the Behavior tab and configure the general parameters.

  4. Select the SAP you need to use for the in-band messaging between the sites in the Port field.

  5. Configure the Policy Pointers for the SRRP Instance.

  6. Save the changes and close the form.

7 

Click Turn Up to activate the SRRP instance.

8 

Repeat Step 3 to Step 7 for the remote site.

Note: When you repeat Step 3 to Step 7 for the remote site, that site becomes the current site and the previously configured site is the remote site.

After the two sites have been properly set up, you can examine the SRRP peer associations at any time by right-clicking an SRRP Instance in the service navigation tree. This opens the SRRP Instance - Edit form, which contains a read-only field called SRRP Peer. The Site ID, Service ID, and Operational State of the associated peer appear in this field.

You can also examine the state of an SRRP Instance by checking the Operational Flags field. The flags indicate specific problems that might occur with the SRRP Instance, as follows:

  • Duplicate Subscriber IF Address: one of the local subscriber IP addresses is the same as a subscriber IP address on the remote node.

  • Redundant Interface Mismatch: the local SRRP instance and remote SRRP instance have mismatched redundant interfaces.

  • SAP Mismatch: the local SRRP instance is backing a different set of SAPs than the peer.

  • Subnet Mismatch: one of the subnets that SRRP is backing up does not have a match with the peer.

  • Dual Master: both SRRP instances are master at the same time.

  • SAP Tag Mismatch: the local SRRP instance is backing a set of SAPs with different remote and local tags.

  • SRRP ID Mismatch: the peer has a different SRRP instance ID backing the same subnet.

9 

Save the changes and close the forms.

End of steps