To create a bidirectional MPLS-TP LSP

Purpose

A bidirectional LSP consists of MPLS-TP LSPs or LER LSPs that are created on the edge NEs, and the LSR cross-connect—or transit path—that is created on the transit NEs. The NFM-P guides you through the creation of the bidirectional MPLS-TP LSP. When the Apply or OK button is disabled, verify that all necessary parameters are configured. When all possible parameters are configured, the NFM-P displays a Hint button to provide instructions on the necessary actions.

This procedure requires the existence of a numbered or unnumbered L3 network interface on the NE that hosts the MPLS-TP instance. See NE routing and forwarding for more information about how to configure network interfaces.

Note: NFM-P guided provisioning is available only for the creation of bidirectional MPLS-TP LSPs. The Hint button does not appear if you are configuring an existing bidirectional MPLS-TP LSP.

Steps
 

Choose Manage→MPLS→MPLS-TP LSPs from the NFM-P main menu. The Manage MPLS-TP LSPs form opens.


Click Create and choose Create Bidirectional TP-LSP. The Bidirectional TP-LSP (Create) form opens.


Configure the required parameters.

The TP-LSP ID must be in the range of the TP-LSP ID Minimum and TP-LSP ID Maximum parameters that you specified in Step 3 of To configure MPLS-TP on a routing instance .


Click Select in the LER A panel and choose a source site and click OK.


Click Select in the LER B panel and choose a source site and click OK.


Click on the LSP Path tab and click Create. The Bidirectional TP-LSP Path (Create) form opens.


Configure the required parameters

Note: You can create one working path and one protecting path per LSP. As required, repeat Step 6 to Step 17 to create the alternate path type.

The LSP Path Number parameter is a global LSP path number that configures the LSP path number on the LER A working and protecting paths, the LER B working and protecting paths, and on the LSR static hop.The LSP Path Number parameter must be the same on all of the hops.


Click on the LER A tab and click Select. The Select Out-Link - Bidirectional TP-LSP Path list form opens.


Choose a site and click OK.


10 

Click on the Hint button. A window appears displaying an instructional message.


11 

Perform one of the following:

  1. If the message “You have configured the LER-A Out-Link Interface. As a result, NFM-P has created the next LSR Path Hop, and has auto-filled the data between the LER-A and the newly created LSR Path Hop” appears, perform the following steps:

    1. Click on the LSR Path Hops tab and choose the LSR path hop with a configuration state of Incomplete and click Properties. The LSR Hop (Edit) form opens.

    2. Configure the required parameters and click OK. Go to Step 14 .

  2. If the message “You have configured the LER-A Out-Link Interface. NFM-P is unable to determine the next hop (this could be due to an unconnected cable). As a result, NFM-P has enabled the LSR Path Hop creation, and the LER-B Out-Link Interface selection.” appears, perform the following:

    • If the next hop in the path is not the LER B, go to Step 12 to create an LSR path hop.

    • If the next hop is the LER B, go to Step 14 .

  3. If the message “You have configured the LER-A Out-Link Interface. As a result, NFM-P has auto-completed the data between LER-A and LER-B.” appears, click OK to complete the path configuration.


12 

Create an LSR path hop:

Perform the following steps:

  1. Click on the LSR Path Hops tab and click Create. The LSR Hop (Create) form opens.

  2. Configure the Display Name parameter.

  3. Click Select in the Forward Out-Link panel and choose an interface and click OK. See To create an MPLS interface for information about how to configure MPLS interfaces.

  4. Click on the Hint button. The message “You have configured the Forward Out-Link Interface. As a result, NFM-P has auto-completed the data between this LSR Path Hop and the previous hop on the forward path.” appears.

  5. Click Select in the Reverse Out-Link panel and choose an interface and click OK. See To create an MPLS interface for information about how to configure MPLS interfaces.

  6. Click OK to close the form.


13 

Click on the Hint button. Perform one of the following based on the message returned:

  1. If the message “You have configured the LSR Path Hop Reverse Out-Link Interface. NFM-P is unable to determine the next hop (this could be due to an unconnected cable). As a result, NFM-P has enabled the LSR Path Hop creation, and the LER-B Out-Link Interface selection.”, perform the following.

    • If the next hop in the path is not the LER B, return to Step 12 to create an LSR path hop.

    • If the next hop is the LER B, go to Step 14

  2. If the message “You have configured the Reverse Out-Link Interface. As a result, NFM-P has created the next LSR Path Hop, and auto-completed the data between this LSR Path Hop and the newly created LSR Path Hop.” appears, perform the following steps:

    1. Click on the LSR Path Hops tab.

    2. Choose the LSR path hop with a configuration state of Incomplete and click Properties. The LSR Hop (Edit) form opens.

    3. Configure the required parameters and click OK. Go to Step 14 .

  3. If the message “You have configured the Reverse Out-Link Interface. As a result, NFM-P has auto-filled the data between this LSR Path Hop and LER-B.” appears, go to Step 17 .


14 

Click on the LER B tab.


15 

Click Select in the Out-Link panel and choose an interface and click OK. See To create an MPLS interface for information about how to configure MPLS interfaces.


16 

Click on the Hint button. The message “You have configured the LER-B Out-Link Interface. As a result, NFM-P has auto-completed the data between LER-B and its next hop on the forward path. The path configuration is now complete.” appears, click OK to complete the path configuration.


17 

Save your change and close the forms.


18 

Create a BFD template on the LER A and LER B. See To configure a BFD template policy .


19 

Create a proactive OAM template on the LER A and LER B. See To configure MPLS-TP on a routing instance .

End of steps