Workflow to configure PW routing and dynamic MS-PW services

Purpose

The following workflow lists the high-level steps required to configure PW routing and dynamic MS-PW services. Enabling MS-PW support requires configuration in the following areas:

  • network commissioning

  • SR NE pre-provisioning

  • dynamic MS-PW service

  • optional PW routing and MS-Service tasks

Stages
Network commissioning
 
1 

To use PW routing to establish dynamic pseudo-wires from source to destination, without using static routes and a specified path:

  1. Enable BGP on the routing instance of the required node. See To enable BGP on a routing instance for more information.

  2. Configure the BGP Family parameter to include the options MS-PW and IPv4. This must be done on the BGP site, associated BGP groups, and BGP peers.

    See the following procedures:

2 

If more than one equal cost route is required for the PW routing, configure the following:

  1. In the routing instance for the required NE, set the Maximum Number of Equal Cost Routes parameter to a value greater than 1. See To configure a routing instance or a VRF instance .

  2. For the required BGP Site, set the Multi Path parameter to a value greater than 1. See To configure global-level BGP .

3 

Configure a routing policy statement with the Family parameter having the MS-PW option enabled. This will then be exported under the BGP site. See To configure a routing policy statement .

4 

If path diversity is required for primary/standby MS-PWs, perform the following:

  1. Configure a routing policy statement having multiple statement entries, each associated with a different community, from a different neighbour, with family including MS-PW and a local preference. The communities configured here are used further on in the procedure when configuring a MS-PW local prefix. See To configure a routing policy statement for more information.

  2. Import the above policy under the BGP site. See To configure global-level BGP .

5 

If there are ASBRs, set Next Hop Self to True under each peer group. For example, set one for the inner-AS and one for the external-AS. Without this setting, the SDPs created by MS-PW routing only reach to the BGP interface's IP address, but not the system ID. See To configure peer-group-level BGP . Refer also to Chapter 79, VPRN service management for information on ASBRs.

6 

If all T-PEs and S-PEs are within the same AS, then the S-PEs must be configured as route reflectors (RR). Perform the following:

  1. Set the Cluster ID parameter on the BGP site or BGP peer group that includes the T-PEs as BGP peers on the S-PE. See Step 3 in To configure global-level BGP .

    Two T-PEs can not be configured as BGP peers to each other. They must be configured as BGP peers of the RR.

  2. Configure a routing policy statement with Advertise Next Hop Self set to true and Action set to Accept, and then export this policy under the BGP site. See To configure a routing policy statement .

This completes the summary of essential network commissioning requirements.

SR NE pre-provisioning
 
7 

Configure PW routing. See To configure PW routing on an NE.

Configure a dynamic MS-PW service
 
8 

Configure a dynamic MS-PW service using PW routing. See To configure a dynamic MS-PW service using PW routing .

Optional PW routing and MS-Service tasks
 
9 

As required, perform one or more of the following:

  1. On-demand resync of the MS-PW routing table for a specified NE is supported and can be accessed from a number of places in the NFM-P. See To display MS-PW routing tables for information on displaying MS-PW routing tables.

  2. Conduct various spoke SDP FEC operations from the endpoint of an Epipe site. See To perform spoke SDP FEC operations from an Epipe site endpoint .

  3. Discover and manage MS-PW switching sites. See To discover and manage MS-PW switching sites .

  4. Run an OAM VCCV Ping or Trace validation test for the MS-PW service. See To conduct MS-PW routing OAM tests .