Right-click on an NE in the navigation tree and choose Properties. The Network Element (Edit) form opens.

Click on the Globals tab, then on the Service tab.

Click on the PW Routing tab.

Configure the general parameters.

The SPE Address must be unique in the network. This parameter must be configured on all T-PEs and S-PEs that are involved in this PW routing.

The Number of BGP Routes, Number of Static Routes, Number of Local Routes, and Number of Host Routes attributes are for information only and can be resync-ed from the NE.

To create one or more local prefixes:

1. Click on the Local Prefixes tab.

2. Click Create. The PW Routing NE Local Prefix (Create) form opens.

3. Configure the Local Prefix parameter.

   You must configure this parameter to enable the MS-PW routing configuration on a T-PE node. This Local Prefix is also used in other portions of the MS-PW configuration, such as setting static routes on the remote T-PE or intermediate S-PEs, and setting Source Attachment Individual Identifier (SAII) and Target Attachment Individual Identifier (TAII) addresses on a spoke SDP FEC on the T-PE.

4. Click Create in the BGP RD panel. The PW Routing NE BGP RD (Create) form opens.

   A route distinguisher must be configured to enable this local prefix to be advertised by MP-BGP to the network.

5. Configure the Route Distinguisher parameter.

6. Configure the BGP Community parameter.

   The BGP Community can only be selected from the list. Members were created as part of the routing policy configuration in To configure a routing policy statement and importing the routing policy under the BGP site in To configure global-level BGP .

7. Save the changes and close the forms.

   You can create up to four route distinguishers per local prefix. You can create up to 16 local prefixes per NE. The local prefixes you create must be unique in the network.

   At this point the NE can start to advertise the defined local prefix to its BGP peers.

To configure one or more static routes:

1. Click on the Static Routes tab.

2. Click Create. The PW Routing NE Static Route Configuration (Create) form opens.

   A static route can be configured on both the T-PE and S-PE, based on your requirements.

3. Configure the Target T-PE’s PW Address parameter to specify the local prefix defined in the remote T-PE. It can be selected from a managed T-PE or S-PE, or directly entered.

4. Configure the Next Hop parameter to specify the system IP address of the next-hop S-PE or T-PE. It can be selected from a managed T-PE or directly entered.

5. Save the changes and close the form.

   At this point the NE can start to advertise the defined static route to its BGP peers.

To configure an explicit path:

1. Click on the Configured Paths tab. All configured paths are listed.

   The path should be configured on the T-PEs, which is then used in the spoke SDP FEC to establish a pseudo-wire through the specified path.

2. Click Create. The PW Routing NE Path Configuration (Create) form opens.

3. Specify a Path Name.

4. Click Create in the Hops panel. The PW Routing Hop (Create) form opens.

5. Configure the Hop ID parameter.

6. Configure the Hop Address parameter.

   This specifies the system IP address of the next-hop S-PE or T-PE (where the T-LDP session to a given S-PE terminates). It can be entered directly or chosen from the managed S-PE or T-PE by clicking the Select button.

7. Save the changes and close the forms.

Save the changes and close the forms.

End of steps