Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Configuring the MPLS Transport Profile for OAM

MPLS Transport Profile Overview

RFC 5654, Requirements of an MPLS Transport Profile, describes the requirements for the MPLS Transport Profile (MPLS-TP) that extends capabilities for Operation, Administration, and Maintenance (OAM) when MPLS is used for transport services and transport network operations. These capabilities help in troubleshooting and maintenance of a pseudowire or label-switched path (LSP).

• Generic Associated Channel Label (GAL)—A special label that enables an exception mechanism that informs the egress label-switching router (LSR) that a packet it receives on an LSP belongs to an associated control channel or the control plane.
• Generic Associated Channel Header (G-Ach)—A special header field that identifies the type of payload contained in the MPLS label-switched paths (LSPs). G-Ach has the same format as a pseudowire associated control channel header.

For more information about MPLS-TP, see RFC 5654, Requirements of an MPLS Transport Profile. For specific information about GAL and G-Ach, see RFC 5586, MPLS Generic Associated Channel.

The following capabilities are supported in the Junos OS implementation of MPLS-TP:

• MPLS-TP OAM can send and receive packets with GAL and G-Ach, without IP encapsulation.
• Two unidirectional RSVP LSPs between a pair of routers can be associated with each other to create an associated bidrectional LSP for binding a path for the GAL and G-Ach OAM messages. A single Bidirectional Forwarding Detection (BFD) session is established for the associated bidirectional LSP.

Example: Configuring the MPLS Transport Profile for OAM

This example shows how to configure the MPLS Transport Profile (MPLS-TP) for sending and receiving of OAM GAL and G-Ach messages across a label-switched path (LSP).

• Requirements
• Overview
• Configuration
• Verification

Requirements

• Six devices that can be a combination of M Series, MX Series, and T Series routers
• Junos OS Release 12.1 or later running on the devices

Overview

Junos OS Release 12.1 and later support MPLS Transport Profile (MPLS-TP) Operation, Administration, and Maintenance (OAM) capabilities. MPLS-TP introduces new capabilities for OAM when MPLS is used for transport services and transport network operations. This includes configuring Generic Associated Channel Label (GAL) and Generic Associated Channel Header (G-Ach) for OAM messages.

This example shows how to configure MPLS-TP OAM capability to send and receive GAL and G-Ach OAM messages without IP encapsulation. In addition, it also shows how to associate two unidirectional RSVP label-switched paths (LSPs) between a pair of routers to create an associated bidirectional LSP for binding a path for the GAL and G-Ach OAM messages.

Junos OS Release 12.1 and later support the following MPLS-TP capabilities:

• MPLS-TP OAM capability and the infrastructure required for MPLS applications to send and receive packets with GAL and G-Ach, without IP encapsulation.
• LSP-ping and Bidirectional Forwarding Detection (BFD) applications to send and receive packets using GAL and G-Ach, without IP encapsulation on transport LSPs.
• The association of two unidirectional RSVP LSPs, between a pair of routers, with each other to create an associated bidirectional LSP for binding a path for the GAL and G-Ach OAM messages. The associated bidirectional LSP model is supported only for associating the primary paths. A single BFD session is established for the associated bidirectional LSP.

Junos OS Release 12.1 and later does not support the following MPLS-TP capabilities:

• Point-to-multipoint RSVP LSPs and BGP LSPs
• Loss Measurement and Delay Measurement

You can enable GAL and G-Ach OAM operation using the following configuration statements:

• mpls-tp-mode—Include this statement at the [edit protocols mpls oam] hierarchy level to enable GAL and G-Ach OAM operation, without IP encapsulation, on all LSPs in the MPLS network.
  [edit protocols mpls oam]mpls-tp-mode;

  Include this statement at the [edit protocols mpls label-switched-path lsp-name oam] hierarchy level to enable GAL and G-Ach OAM operation without IP encapsulation on a specific LSP in the network.

  [edit protocols mpls label-switched-path lsp-name oam]mpls-tp-mode;
• associate-lsp lsp-name from from-ip-address—Include this statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level to configure associated bidirectional LSPs on the two ends of the LSP.
  [edit protocols mpls label-switched-path lsp-name ]associate-lsp lsp-name {from from-ip-address;}

  The from from-ip-address configuration for the LSP is optional. If omitted, it is derived from the to address of the ingress LSP configuration.

• transit-lsp-association—Include this statement at the [edit protocols mpls]
  hierarchy level to associate two LSPs at a transit router.
  [edit protocols mpls]transit-lsp-association transit-association-lsp-group-name {lsp-name-1 name-of-associated-lsp-1;from-1 address-of-associated-lsp-1;lsp-name-2 name-of-associated-lsp-2;from-2 address-of-associated-lsp-2;}

  The association of the LSPs in the transit nodes is useful for the return LSP path for TTL-expired LSP ping packets or traceroute.

In this example, R0 is the ingress router and R4 is the egress router. R1, R2, R3, and R5 are transit routers. The associated bidirectional LSP is established between the transit routers for sending and receiving the GAL and G-Ach OAM messages.

Figure 1 shows the topology used in this example.

Figure 1: MPLS-TP OAM Associated Bidirectional LSPs

Configuration

CLI Quick Configuration

Note: This example shows the configuration on all devices and shows step-by-step procedures for configuring the ingress router, R0, and transit router R1. Repeat the step-by-step procedure described for the ingress router, R0, on the egress router, R4. Repeat the step-by-step procedure for the transit router, R1, on the other transit routers, R2, R3, and R5. Be sure to modify the appropriate interface names, addresses, and other parameters appropriately.

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Configuring Device R0

Step-by-Step Procedure

1. Configure the interfaces.
   [edit interfaces]user@R0# set ge-4/1/1 unit 0 family inet address 10.10.11.1/30user@R0# set ge-4/1/1 unit 0 family isouser@R0# set ge-4/1/1 unit 0 family inet6user@R0# set ge-4/1/1 unit 0 family mplsuser@R0# set ge-5/0/0 unit 0 family inet address 10.10.10.1/30user@R0# set ge-5/0/0 unit 0 family isouser@R0# set ge-5/0/0 unit 0 family inet6user@R0# set ge-5/0/0 unit 0 family mpls
2. Configure MPLS on the interfaces.
   [edit protocols mpls]user@R0# set interface ge-5/0/0.0user@R0# set interface ge-4/1/1.0
3. Configure an interior gateway protocol, such as OSPF.
   [edit protocols ospf]user@R0# set traffic-engineeringuser@R0# set area 0.0.0.0 interface ge-5/0/0.0user@R0# set area 0.0.0.0 interface ge-4/1/1.0user@R0# set area 0.0.0.0 interface lo0.0 passive
4. Configure a signaling protocol, such as RSVP.
   [edit protocols rsvp]user@R0# set interface ge-5/0/0.0user@R0# set interface ge-4/1/1.0
5. Configure the LSP.
   [edit protocols mpls]user@R0# set label-switched-path r0-to-r4 to 10.255.8.86
6. Enable GAL and G-Ach OAM operation without IP encapsulation on the LSPs.
   [edit protocols mpls]user@R0# set label-switched-path r0-to-r4 oam mpls-tp-mode
7. Configure associated bidirectional LSPs on the two ends of the LSP.
   [edit protocols mpls]user@R0# set label-switched-path r0-to-r4 associate-lsp to-r0 from 10.255.8.86
8. After you are done configuring the device, commit the configuration.
   [edit]user@R0# commit

Results

Confirm your configuration by issuing the show interfaces and show protocols commands.

Configuring Device R1

Step-by-Step Procedure

1. Configure the interfaces.
   [edit interfaces]user@R1# set ge-0/0/5 unit 0 family inet address 10.10.10.2/30user@R1# set ge-0/0/5 unit 0 family isouser@R1# set ge-0/0/5 unit 0 family inet6user@R1# set ge-0/0/5 unit 0 family mplsuser@R1# set ge-0/2/2 unit 0 family inet address 10.10.12.2/30user@R1# set ge-0/2/2 unit 0 family isouser@R1# set ge-0/2/2 unit 0 family inet6user@R1# set ge-0/2/2 unit 0 family mplsuser@R1# set ge-2/0/2 unit 0 family inet address 10.10.11.2/30user@R1# set ge-2/0/2 unit 0 family isouser@R1# set ge-2/0/2 unit 0 family inet6user@R1# set ge-2/0/2 unit 0 family mplsuser@R1# set ge-1/0/2 unit 0 family inet address 10.10.13.2/30user@R1# set ge-1/0/2 unit 0 family isouser@R1# set ge-1/0/2 unit 0 family inet6user@R1# set ge-1/0/2 unit 0 family mpls
2. Configure MPLS on the interfaces.
   [edit protocols mpls]user@R1# set interface ge-0/0/5.0user@R1# set interface ge-2/0/2.0user@R1# set interface ge-1/0/2.0user@R1# set interface ge-0/2/2.0
3. Configure an interior gateway protocol, such as OSPF.
   [edit protocols ospf]user@R1# set traffic-engineeringuser@R1# set area 0.0.0.0 interface ge-0/0/5.0user@R1# set area 0.0.0.0 interface ge-2/0/2.0user@R1# set area 0.0.0.0 interface ge-1/0/2.0user@R1# set area 0.0.0.0 interface ge-0/2/2.0 metric 100user@R1# set area 0.0.0.0 interface lo0.0 passive
4. Configure a signaling protocol, such as RSVP.
   [edit protocols rsvp]user@R1# set interface ge-0/0/5.0user@R1# set interface ge-2/0/2.0user@R1# set interface ge-1/0/2.0user@R1# set interface ge-0/2/2.0
5. Configure the association of the two LSPs on the transit router.
   [edit protocols mpls]user@R1# set transit-lsp-association trace1 lsp-name-1 r0-to-r4user@R1# set transit-lsp-association trace1 from-1 10.255.8.207user@R1# set transit-lsp-association trace1 lsp-name-2 r4-to-r0user@R1# set transit-lsp-association trace1 from-2 10.255.8.86
6. If you are done configuring the device, commit the configuration.
   [edit]user@R1# commit

Results

Confirm your configuration by issuing the show interfaces and show protocols commands.

Verification

Confirm that the configuration is working properly.

Verifying Associated Bidirectional LSPs

Purpose

Verify that the associated bidirectional LSP configuration is working properly.

Action

Ingress LSP: 1 sessions
To              From            State Rt P   ActivePath   LSPname
10.10.11.1  10.255.8.86  			 Up     0 *                r0-to-r4 Assoc-Bidir
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To         From           State Rt Style Labelin Labelout LSPname
10.10.16.1  10.255.8.207  Up    0  1 FF       3           r4-to-r0 Assoc-Bidir
Total 2 displayed, Up 2, Down 0

Transit LSP: 1 sessions
To          From           State  Rt Style Labelin Labelout LSPname
10.10.10.2  10.255.8.168  Up      1  1 FF  301264        3 r0-to-r4 Assoc-Bidir
Total 3 displayed, Up 3, Down 0

Ingress LSP: 1 sessions

10.10.11.1
  From: 10.255.8.86, State: Up, ActiveRoute: 0, LSPname: r0-to-r4
  Associated Bidirectional
  Associated LSP: r0-to-r4, 10.255.8.86
  ActivePath:  (primary)
  LSPtype: Static Configured
  LoadBalance: Random
  Encoding type: Packet, Switching type: PSC-1, GPID: Unknown
 *Primary                    State: Up

Egress LSP: 1 sessions

10.255.102.29
  From: 10.255.102.172, LSPstate: Up, ActiveRoute: 0
    LSPname: r4-to-r0, LSPpath: Primary
    Associated Bidirectional
    Associated LSP: 10.10.16.1, to-r0>
    Suggested label received: -, Suggested label sent: -
    Recovery label received: -, Recovery label sent: -
    Resv style: 1 FF, Label in: 3, Label out: -
    Time left:  144, Since: Fri Jun 17 21:41:05 2011
    Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
    Port number: sender 6 receiver 14468 protocol 0
    PATH rcvfrom: 10.10.13.1 (ge-2/0/0.0) 84 pkts
    Adspec: received MTU 1500
    PATH sentto: localclient
    RESV rcvfrom: localclient
    Record route: 10.10.14.2 10.10.13.1 <self>

Transit LSP: 1 sessions

10.255.102.30
  From: 10.255.102.172, LSPstate: Up, ActiveRoute: 1
    LSPname: to_airstream, LSPpath: Primary
    Associated Bidirectional
    Associated LSP: r0-to-r4, 10.255.8.168
    Suggested label received: -, Suggested label
    Recovery label received: -, Recovery label sent: 3
    Resv style: 1 FF, Label in: 301264, Label out: 3
    Time left:  132, Since: Fri Jun 17 21:40:56 2011
    Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
    Port number: sender 28 receiver 14465 protocol 0
    PATH rcvfrom: 10.10.13.1 (ge-2/0/0.0) 84 pkts
    Adspec: received MTU 1500 sent MTU 1500
    PATH sentto: 10.10.10.1 (ge-3/0/0.0) 84 pkts
    RESV rcvfrom: 10.10.10.1 (ge-3/0/0.0) 84 pkts
    Explct route: 10.10.10.1
    Record route: 10.10.16.1 10.10.15.2 10.10.13.1 <self> 10.10.10.1

Ingress LSP: 1 session
To              From            State Rt P     ActivePath       LSPname
10.255.8.86     10.255.8.207    Up     0 *                      r0-to-r4 
 Assoc-Bidir
Total 1 displayed, Up 1, Down 0
Aug 28 06:56:26 [TRACE] [R0 coleman re0]
Egress LSP: 1 session
To              From            State   Rt Style Labelin Labelout LSPname
10.255.8.207    10.255.8.86  	Up       0  1 FF       3        - to-r0
 Assoc-Bidir
Total 1 displayed, Up 1, Down 0
Aug 28 06:56:26 [TRACE] [R0 coleman re0]
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Meaning

The output of the show mpls lsp, show mpls detail, and show mpls bidirectional commands displays the details of the associated bidirectional LSPs and the LSP association information.