MPLS OAM Configuration
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).
MPLS-TP mechanisms for OAM contain two main components:
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
This example uses the following hardware and software components:
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;
Note:Starting with Junos OS Release 16.1, MPLS-TP supports two additional channel types for the default LSPING (0x0008) channel type under the mpls-tp-mode statement. These additional channel types provide on-demand connectivity verification (CV) with and without IP/UDP encapsulation.
On-demand CV (0x0025)—This channel type is a new pseudowire channel type and is used for on-demand CV without IP/UDP encapsulation, where IP addressing is not available or non-IP encapsulation is preferred.
IPv4 (0x0021)—This channel type uses the IP/UDP encapsulation and provides interoperability support with other vendor devices using IP addressing.
The GACH-TLV is used along with the default LSPING channel type. As per RFC 7026, GACH-TLV is deprecated for 0x0021 and 0x0025 channel types.
To configure a channel type for MPLS-TP, include the
lsping-channel-type channel-typestatement at the[edit protocols mpls label-switched-path lsp-name oam mpls-tp-mode]and[edit protocols mpls oam mpls-tp-mode]hierarchy levels.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-addressconfiguration for the LSP is optional. If omitted, it is derived from thetoaddress 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.
Topology
Configuration
CLI Quick Configuration
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.
Router R0
set interfaces ge-4/1/1 unit 0 family inet address 10.10.11.1/30 set interfaces ge-4/1/1 unit 0 family iso set interfaces ge-4/1/1 unit 0 family inet6 set interfaces ge-4/1/1 unit 0 family mpls set interfaces ge-5/0/0 unit 0 family inet address 10.10.10.1/30 set interfaces ge-5/0/0 unit 0 family iso set interfaces ge-5/0/0 unit 0 family inet6 set interfaces ge-5/0/0 unit 0 family mpls set protocols rsvp interface ge-5/0/0.0 set protocols rsvp interface ge-4/1/1.0 set protocols mpls label-switched-path r0-to-r4 to 10.255.8.86 set protocols mpls label-switched-path r0-to-r4 oam mpls-tp-mode set protocols mpls label-switched-path r0-to-r4 associate-lsp r4-to-r0 from 10.255.8.86 set protocols mpls interface ge-5/0/0.0 set protocols mpls interface ge-4/1/1.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-5/0/0.0 set protocols ospf area 0.0.0.0 interface ge-4/1/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Router R1
set interfaces ge-0/0/5 unit 0 family inet address 10.10.10.2/30 set interfaces ge-0/0/5 unit 0 family iso set interfaces ge-0/0/5 unit 0 family inet6 set interfaces ge-0/0/5 unit 0 family mpls set interfaces ge-0/2/2 unit 0 family inet address 10.10.12.2/30 set interfaces ge-0/2/2 unit 0 family iso set interfaces ge-0/2/2 unit 0 family inet6 set interfaces ge-0/2/2 unit 0 family mpls set interfaces ge-1/0/2 unit 0 family inet address 10.10.13.2/30 set interfaces ge-1/0/2 unit 0 family iso set interfaces ge-1/0/2 unit 0 family inet6 set interfaces ge-1/0/2 unit 0 family mpls set interfaces ge-2/0/2 unit 0 family inet address 10.10.11.2/30 set interfaces ge-2/0/2 unit 0 family iso set interfaces ge-2/0/2 unit 0 family inet6 set interfaces ge-2/0/2 unit 0 family mpls set protocols rsvp interface ge-0/2/2.0 set protocols rsvp interface ge-0/0/5.0 set protocols rsvp interface ge-1/0/2.0 set protocols rsvp interface ge-2/0/2.0 set protocols mpls transit-lsp-association trace1 lsp-name-1 r0-to-r4 set protocols mpls transit-lsp-association trace1 from-1 10.255.8.207 set protocols mpls transit-lsp-association trace1 lsp-name-2 r4-to-r0 set protocols mpls transit-lsp-association trace1 from-2 10.255.8.86 set protocols mpls interface ge-0/0/5.0 set protocols mpls interface ge-2/0/2.0 set protocols mpls interface ge-1/0/2.0 set protocols mpls interface ge-0/2/2.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-0/0/5.0 set protocols ospf area 0.0.0.0 interface ge-0/2/2.0 metric 100 set protocols ospf area 0.0.0.0 interface ge-1/0/2.0 set protocols ospf area 0.0.0.0 interface ge-2/0/2.0 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Router R2
set interfaces ge-0/2/3 unit 0 family inet address 10.10.13.1/30 set interfaces ge-0/2/3 unit 0 family iso set interfaces ge-0/2/3 unit 0 family inet6 set interfaces ge-0/2/3 unit 0 family mpls set interfaces ge-1/3/2 unit 0 family inet address 10.10.14.1/30 set interfaces ge-1/3/2 unit 0 family iso set interfaces ge-1/3/2 unit 0 family inet6 set interfaces ge-1/3/2 unit 0 family mpls set interfaces ge-1/3/4 unit 0 family inet address 10.10.15.1/30 set interfaces ge-1/3/4 unit 0 family iso set interfaces ge-1/3/4 unit 0 family inet6 set interfaces ge-1/3/4 unit 0 family mpls set protocols rsvp interface ge-0/2/3.0 set protocols rsvp interface ge-1/3/2.0 set protocols rsvp interface ge-1/3/4.0 set protocols mpls transit-lsp-association trace1 lsp-name-1 r0-to-r4 set protocols mpls transit-lsp-association trace1 from-1 10.255.8.207 set protocols mpls transit-lsp-association trace1 lsp-name-2 r4-to-r0 set protocols mpls transit-lsp-association trace1 from-2 10.255.8.86 set protocols mpls interface ge-0/2/3.0 set protocols mpls interface ge-1/3/2.0 set protocols mpls interface ge-1/3/4.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-0/2/3.0 set protocols ospf area 0.0.0.0 interface ge-1/3/2.0 set protocols ospf area 0.0.0.0 interface ge-1/3/4.0 metric 100 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Router R3
set interfaces ge-1/2/1 unit 0 family inet address 10.10.16.2/30 set interfaces ge-1/2/1 unit 0 family iso set interfaces ge-1/2/1 unit 0 family inet6 set interfaces ge-1/2/1 unit 0 family mpls set interfaces ge-2/0/7 unit 0 family inet address 10.10.17.2/30 set interfaces ge-2/0/7 unit 0 family iso set interfaces ge-2/0/7 unit 0 family inet6 set interfaces ge-2/0/7 unit 0 family mpls set interfaces ge-2/2/0 unit 0 family inet address 10.10.14.2/30 set interfaces ge-2/2/0 unit 0 family iso set interfaces ge-2/2/0 unit 0 family inet6 set interfaces ge-2/2/0 unit 0 family mpls set protocols rsvp interface ge-2/2/0.0 set protocols rsvp interface ge-1/2/1.0 set protocols rsvp interface ge-2/0/7.0 set protocols mpls transit-lsp-association trace1 lsp-name-1 r0-to-r4 set protocols mpls transit-lsp-association trace1 from-1 10.255.8.207 set protocols mpls transit-lsp-association trace1 lsp-name-2 r4-to-r0 set protocols mpls transit-lsp-association trace1 from-2 10.255.8.86 set protocols mpls interface ge-2/2/0.0 set protocols mpls interface ge-1/2/1.0 set protocols mpls interface ge-2/0/7.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-2/2/0.0 set protocols ospf area 0.0.0.0 interface ge-1/2/1.0 set protocols ospf area 0.0.0.0 interface ge-2/0/7.0 metric 100 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Router R4
set interfaces ge-0/0/3 unit 0 family inet address 10.10.16.1/30 set interfaces ge-0/0/3 unit 0 family iso set interfaces ge-0/0/3 unit 0 family inet6 set interfaces ge-0/0/3 unit 0 family mpls set protocols rsvp interface ge-0/0/3.0 set protocols mpls label-switched-path r4-to-r0 to 10.255.8.207 set protocols mpls label-switched-path r4-to-r0 oam mpls-tp-mode set protocols mpls label-switched-path r4-to-r0 associate-lsp r0-to-r4 from 10.255.8.207 set protocols mpls interface ge-0/0/3.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-0/0/3.0 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Router R5
set interfaces ge-1/2/0 unit 0 family inet address 10.10.15.2/30 set interfaces ge-1/2/0 unit 0 family iso set interfaces ge-1/2/0 unit 0 family inet6 set interfaces ge-1/2/0 unit 0 family mpls set interfaces ge-2/0/0 unit 0 family inet address 10.10.12.1/30 set interfaces ge-2/0/0 unit 0 family iso set interfaces ge-2/0/0 unit 0 family inet6 set interfaces ge-2/0/0 unit 0 family mpls set interfaces ge-4/0/7 unit 0 family inet address 10.10.17.1/30 set interfaces ge-4/0/7 unit 0 family iso set interfaces ge-4/0/7 unit 0 family inet6 set interfaces ge-4/0/7 unit 0 family mpls set protocols rsvp interface ge-2/0/0.0 set protocols rsvp interface ge-1/2/0.0 set protocols rsvp interface ge-4/0/7.0 set protocols mpls transit-lsp-association trace1 lsp-name-1 r0-to-r4 set protocols mpls transit-lsp-association trace1 from-1 10.255.8.207 set protocols mpls transit-lsp-association trace1 lsp-name-2 r4-to-r0 set protocols mpls transit-lsp-association trace1 from-2 10.255.8.86 set protocols mpls interface ge-2/0/0.0 set protocols mpls interface ge-1/2/0.0 set protocols mpls interface ge-4/0/7.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-2/0/0.0 metric 100 set protocols ospf area 0.0.0.0 interface ge-1/2/0.0 metric 100 set protocols ospf area 0.0.0.0 interface ge-4/0/7.0 metric 100 set protocols ospf area 0.0.0.0 interface lo0.0 passive
Configuring Device R0
Step-by-Step Procedure
To configure the ingress router, R0:
Configure the interfaces.
[edit interfaces]user@R0# set ge-4/1/1 unit 0 family inet address 10.10.11.1/30 user@R0# set ge-4/1/1 unit 0 family iso user@R0# set ge-4/1/1 unit 0 family inet6 user@R0# set ge-4/1/1 unit 0 family mpls user@R0# set ge-5/0/0 unit 0 family inet address 10.10.10.1/30 user@R0# set ge-5/0/0 unit 0 family iso user@R0# set ge-5/0/0 unit 0 family inet6 user@R0# set ge-5/0/0 unit 0 family mplsConfigure MPLS on the interfaces.
[edit protocols mpls]user@R0# set interface ge-5/0/0.0 user@R0# set interface ge-4/1/1.0Configure an interior gateway protocol, such as OSPF.
[edit protocols ospf]user@R0# set traffic-engineering user@R0# set area 0.0.0.0 interface ge-5/0/0.0 user@R0# set area 0.0.0.0 interface ge-4/1/1.0 user@R0# set area 0.0.0.0 interface lo0.0 passiveConfigure a signaling protocol, such as RSVP.
[edit protocols rsvp]user@R0# set interface ge-5/0/0.0 user@R0# set interface ge-4/1/1.0Configure the LSP.
[edit protocols mpls]user@R0# set label-switched-path r0-to-r4 to 10.255.8.86Enable 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-modeConfigure 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.86After 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.
user@R0# show interfaces
ge-4/1/1 {
unit 0 {
family inet {
address 10.10.11.1/30;
}
family iso;
family inet6;
family mpls;
}
}
ge-5/0/0 {
unit 0 {
family inet {
address 10.10.10.1/30;
}
family iso;
family inet6;
family mpls;
}
}
user@R0# show protocols
rsvp {
interface ge-5/0/0.0;
interface ge-4/1/1.0;
}
mpls {
label-switched-path r0-to-r4 {
to 10.255.8.86;
oam mpls-tp-mode;
associate-lsp r4-to-r0 {
from 10.255.8.86;
}
}
interface ge-4/1/1.0;
interface ge-5/0/0.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-5/0/0.0;
interface ge-4/1/1.0;
interface lo0.0 {
passive;
}
}
}
Configuring Device R1
Step-by-Step Procedure
To configure the transit router, R1:
Configure the interfaces.
[edit interfaces]user@R1# set ge-0/0/5 unit 0 family inet address 10.10.10.2/30 user@R1# set ge-0/0/5 unit 0 family iso user@R1# set ge-0/0/5 unit 0 family inet6 user@R1# set ge-0/0/5 unit 0 family mpls user@R1# set ge-0/2/2 unit 0 family inet address 10.10.12.2/30 user@R1# set ge-0/2/2 unit 0 family iso user@R1# set ge-0/2/2 unit 0 family inet6 user@R1# set ge-0/2/2 unit 0 family mpls user@R1# set ge-2/0/2 unit 0 family inet address 10.10.11.2/30 user@R1# set ge-2/0/2 unit 0 family iso user@R1# set ge-2/0/2 unit 0 family inet6 user@R1# set ge-2/0/2 unit 0 family mpls user@R1# set ge-1/0/2 unit 0 family inet address 10.10.13.2/30 user@R1# set ge-1/0/2 unit 0 family iso user@R1# set ge-1/0/2 unit 0 family inet6 user@R1# set ge-1/0/2 unit 0 family mplsConfigure MPLS on the interfaces.
[edit protocols mpls]user@R1# set interface ge-0/0/5.0 user@R1# set interface ge-2/0/2.0 user@R1# set interface ge-1/0/2.0 user@R1# set interface ge-0/2/2.0Configure an interior gateway protocol, such as OSPF.
[edit protocols ospf]user@R1# set traffic-engineering user@R1# set area 0.0.0.0 interface ge-0/0/5.0 user@R1# set area 0.0.0.0 interface ge-2/0/2.0 user@R1# set area 0.0.0.0 interface ge-1/0/2.0 user@R1# set area 0.0.0.0 interface ge-0/2/2.0 metric 100 user@R1# set area 0.0.0.0 interface lo0.0 passiveConfigure a signaling protocol, such as RSVP.
[edit protocols rsvp]user@R1# set interface ge-0/0/5.0 user@R1# set interface ge-2/0/2.0 user@R1# set interface ge-1/0/2.0 user@R1# set interface ge-0/2/2.0Configure 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-r4 user@R1# set transit-lsp-association trace1 from-1 10.255.8.207 user@R1# set transit-lsp-association trace1 lsp-name-2 r4-to-r0 user@R1# set transit-lsp-association trace1 from-2 10.255.8.86If 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.
user@R1# show interfaces
ge-0/0/5 {
unit 0 {
family inet {
address 10.10.10.2/30;
}
family iso;
family inet6;
family mpls;
}
}
ge-0/2/2 {
unit 0 {
family inet {
address 10.10.12.2/30;
}
family iso;
family inet6;
family mpls;
}
}
ge-2/0/2 {
unit 0 {
family inet {
address 10.10.11.2/30;
}
family iso;
family inet6;
family mpls;
}
}
ge-1/0/2 {
unit 0 {
family inet {
address 10.10.13.2/30;
}
family iso;
family inet6;
family mpls;
}
}
user@R1# show protocols
rsvp {
interface ge-0/0/5.0;
interface ge-2/0/2.0;
interface ge-1/0/2.0;
interface ge-0/2/2.0;
}
mpls {
transit-lsp-association trace1 {
lsp-name-1 r0-to-r4;
from-1 10.255.8.207;
lsp-name-2 r4-to-r0;
from-2 10.255.8.86;
}
interface ge-0/0/5.0;
interface ge-2/0/2.0;
interface ge-1/0/2.0;
interface ge-0/2/2.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/5.0;
interface ge-1/0/2.0;
interface ge-2/0/2.0;
interface ge-0/2/2.0 {
metric 100;
}
interface lo0.0 {
passive;
}
}
}
Verification
Confirm that the configuration is working properly.
Verifying Associated Bidirectional LSPs
Purpose
Verify that the associated bidirectional LSP configuration is working properly.
Action
user@host> show mpls lsp 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
user@host> show mpls lsp detail
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.1user@host> show mpls lsp bidirectional 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.
Configuring OAM Ingress Policies for LDP
Using the ingress-policy statement, you can configure
an Operation, Administration, and Management (OAM) policy to choose
which forwarding equivalence classes (FECs) need to have OAM enabled.
If the FEC passes through the policy or if the FEC is explicitly configured,
OAM is enabled for a FEC. For FECs chosen using a policy, the BFD
parameters configured under [edit protocols ldp oam bfd-liveness-detection] are applied.
You configure the OAM ingress policy at the [edit
policy-options] hierarchy level. To configure an OAM ingress
policy, include the ingress-policy statement:
ingress-policy ingress-policy-name;
You can configure this statement at the following hierarchy levels:
ACX Series routers do not support [edit logical-systems] hierarchy level.
Tracing MPLS and LSP Packets and Operations
To trace MPLS and LSP packets and operations, include the traceoptions statement:
traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag; }
For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.
You can specify the following MPLS-specific flags in the MPLS traceoptions statement:
all—Trace all operations.connection—Trace all circuit cross-connect (CCC) activity.connection-detail—Trace detailed CCC activity.cspf—Trace CSPF computations.cspf-link—Trace links visited during CSPF computations.cspf-node—Trace nodes visited during CSPF computations.error—Trace MPLS error conditions.graceful-restart—Trace MPLS graceful restart events.lsping—Trace LSP ping packets and return codes.nsr-synchronization—Trace nonstop routing (NSR) synchronization events.nsr-synchronization-detail—Trace NSR synchronization events in detail.state—Trace all LSP state transitions.static—Trace static label-switched path.
When you configure trace options to track an MPLS LSP using
the cspf option, the CSPF log displays information about
the MPLS LSP using the term “generalized MPLS” (GMPLS).
For example, a message in the CSPF log might state that the “link
passes GMPLS constraints”. Generalized MPLS (GMPLS) is a superset
of MPLS, so this message is normal and does not affect proper MPLS
LSP operation.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.