Contents

Configuring MPLS OAM·· 1

About MPLS OAM·· 1

Fault management tools· 1

MPLS ping· 1

MPLS tracert 1

Periodic MPLS tracert 1

Protocols and standards· 1

Restrictions: Hardware compatibility with MPLS OAM·· 2

Restrictions and guidelines: MPLS OAM configuration· 2

Verifying LSP connectivity· 2

About LSP connectivity verification· 2

Performing MPLS ping for LSPs· 2

Performing MPLS tracert for LSPs· 3

Configuring periodic MPLS tracert for LSPs· 3

Verifying MPLS TE tunnel connectivity· 3

About MPLS TE tunnel connectivity verification· 3

Performing MPLS ping for MPLS TE tunnels· 4

Performing MPLS tracert for MPLS TE tunnels· 4

Configuring MPLS OAM

About MPLS OAM

MPLS Operation, Administration, and Maintenance (OAM) provides fault management tools for the following purposes:

·     MPLS data plane connectivity verification.

·     Data plane and control plane consistency verification.

·     Fault locating.

Fault management tools

The fault management tools include the following types:

·     On-demand tools—Tools that must be triggered manually, such as MPLS ping and MPLS tracert.

·     Proactive tools—Tools that are triggered by the system automatically, such as BFD for MPLS, and periodic MPLS tracert.

You can use these tools to detect and locate faults of LSPs.

MPLS ping

MPLS ping tests the connectivity of an LSP tunnel, MPLS TE tunnel, PW, Flex-Algo LSP, or SR-MPLS TE policy tunnel. At the ingress node, MPLS ping adds the label associated with a tunnel into an MPLS echo request and sends it to the egress node over the tunnel. The egress node processes the request and returns an MPLS echo reply to the ingress node. An MPLS echo reply with a success notification indicates that the tunnel is available for data forwarding. An MPLS echo reply with an error code indicates that the tunnel has failed.

MPLS tracert

MPLS tracert displays the path that an LSP tunnel, MPLS TE tunnel, Flex-Algo LSP, or SR-MPLS policy tunnel travels from the ingress to the egress to locate errors on the tunnel. MPLS tracert consecutively sends MPLS echo requests along the LSP tunnel, with the TTL increasing from 1 to a specific value. Each hop along the tunnel returns an MPLS echo reply to the ingress due to TTL timeout so the ingress can collect information about each hop along the tunnel. This information allows you to locate the failed node or access information for each hop, for example, the label allocated by each downstream hop.

Periodic MPLS tracert

The periodic MPLS tracert feature automatically traces an LSP tunnel at intervals. It locates errors on the LSP tunnel, verifies the consistency of the data plane and control plane, and records the detected errors in system logs. You can check the logs to monitor LSP connectivity.

Protocols and standards

·     RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures

·     RFC 5085, Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires

Restrictions: Hardware compatibility with MPLS OAM

MPLS OAM is not available on the S9825 switch series.

Restrictions and guidelines: MPLS OAM configuration

To use MPLS OAM on an MPLS-capable device, set the hardware resource mode to the routing mode by using the hardware-resource switch-mode command. For more information about this command, see hardware resource management commands in System Management Command Reference.

Verifying LSP connectivity

About LSP connectivity verification

To verify LSP connectivity, you can use one of the following methods:

·     Use the ping mpls ipv4 command or the tracert mpls ipv4 command to trigger LSP connectivity verification as needed.

·     Configure periodic MPLS tracert for the system to automatically verify LSP connectivity.

Performing MPLS ping for LSPs

Pinging the LSPs for an IPv4 prefix

To verify MPLS LSP connectivity for an IPv4 prefix, execute the following command in any view:

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * ipv4 ipv4-address mask-length [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { generic | isis | ldp | ospf } ]

Pinging the LSPs for an IPv6 prefix

To verify MPLS LSP connectivity for an IPv6 prefix, execute the following command in any view:

ping mpls [ -a source-ip6 | -c count | -tc traffic-class | -h ttl-value | -m wait-time | -r reply-mode | -s packet-size | -t time-out | -v ] * ipv6 ipv6-address prefix-length nexthop nexthop-address6 ] [ fec-type { generic | isis | ldp } ] [ nil-fec ]

Pinging the LSPs of the specified outgoing labels

To verify MPLS LSP connectivity by specifying the outgoing labels, execute the following command in any view:

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * out-labels out-label-value&<1-n> interface interface-type interface-number [ nexthop nexthop-address ]

Performing MPLS tracert for LSPs

Tracing the path of the LSPs for an IPv4 prefix

To trace the path that the LSPs for an IPv4 prefix take from the ingress node to the egress node, execute the following command in any view:

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | ddmap | fec-check ] * ipv4 ipv4-address mask-length [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { generic | isis | ldp | ospf } ]

Tracing the path of the LSPs for an IPv6 prefix

To trace the path that the LSPs for an IPv6 prefix take from the ingress node to the egress node, execute the following command in any view:

tracert mpls [ -a source-ip6 | -tc traffic-class | -h ttl-value | -r reply-mode | -t time-out | -v ] * ipv6 ipv6-address prefix-length [ flex-algo flex-algo-id ] [ nexthop nexthop-address6 ] [ fec-type { generic | isis | ldp } ] [ nil-fec ]

Tracing the path of the LSPs of the specified outgoing labels

To trace the path that the LSPs of the specified outgoing labels take from the ingress node to the egress node, execute the following command in any view:

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | fec-check ]* out-labels out-label-value&<1-n> interface interface-type interface-number [ nexthop nexthop-address ]

Configuring periodic MPLS tracert for LSPs

1.     Enter system view.

system-view

2.     Enable periodic LSP tracert for a FEC.

mpls periodic-tracert dest-addr mask-length [ -a source-ip | -exp exp-value | -h ttl-value | -m wait-time | -rtos tos-value | -t time-out | -u retry-attempt | fec-check ] *

By default, periodic LSP tracert is disabled.

Verifying MPLS TE tunnel connectivity

About MPLS TE tunnel connectivity verification

To verify MPLS TE tunnel connectivity, you can use the ping mpls te command or the tracert mpls te command to trigger MPLS TE tunnel connectivity verification as needed.

Performing MPLS ping for MPLS TE tunnels

To use MPLS ping to verify MPLS TE tunnel connectivity, execute the following command in any view:

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * te tunnel interface-number

Performing MPLS tracert for MPLS TE tunnels

To use MPLS tracert to trace an MPLS TE tunnel, execute the following command in any view:

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | fec-check ] * te tunnel interface-number