Contents

Configuring MPLS OAM·· 1

About MPLS OAM·· 1

Fault management tools· 1

MPLS ping· 1

MPLS tracert 1

Protocols and standards· 1

Restrictions and guidelines: MPLS OAM configuration· 1

Verifying LSP connectivity· 2

Performing MPLS ping for LSPs· 2

Performing MPLS tracert for LSPs· 2

Verifying MPLS TE tunnel connectivity· 2

Performing MPLS ping for MPLS TE tunnels· 2

Performing MPLS tracert for MPLS TE tunnels· 3

Verifying PW connectivity· 3

About PW connectivity verification· 3

Performing MPLS ping for a PW·· 3

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

MPLS OAM provides on-demand fault management tools, which must be triggered manually, such as MPLS ping and MPLS tracert.

MPLS ping

MPLS ping tests the connectivity of a 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 a tunnel travels from the ingress to the egress to locate errors on the tunnel. MPLS tracert consecutively sends MPLS echo requests along the 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.

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 and guidelines: MPLS OAM configuration

MPLS OAM and VXLAN are mutually exclusive. Do not configure both features. For information about VXLAN, see VXLAN Configuration Guide.

Verifying 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 } ]

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 | fec-check ] * ipv4 ipv4-address mask-length [ destination start-address [ end-address [ address-increment ] ] ][ fec-type { generic | isis | ldp } ]

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 ]

Verifying MPLS TE tunnel connectivity

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

Verifying PW connectivity

About PW connectivity verification

Virtual Circuit Connectivity Verification (VCCV) is an L2VPN PW OAM feature to verify PW connectivity in data plane.

The packets used to verify PW connectivity are collectively referred to as VCCV packets. A PE transfers VCCV packets through a control channel (CC).

The device supports only the MPLS router alert label type CCs in the current software version. An MPLS router alert label type CC identifies a VCCV packet by adding an MPLS router alert label before the PW label.

Performing MPLS ping for a PW

Prerequisites

Before you configure MPLS ping for a PW, perform the following tasks:

1.     Create a PW class, and use the vccv cc command to configure the VCCV CC type in PW class view.

2.     Create the PW, and use the PW class created in the previous step for the PW.

Procedure

To use MPLS ping to verify the connectivity of a PW, 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 ] * pw ip-address pw-id pw-id [ remote remote-ip-address remote-pw-id ]