Contents

Configuring MPLS OAM·· 1

About MPLS OAM·· 1

MPLS ping· 1

MPLS tracert 1

Protocols and standards· 1

Verifying LSP connectivity· 1

Using MPLS ping for LSPs· 1

Using MPLS tracert for LSPs· 2

Verifying MPLS TE tunnel connectivity· 2

Using MPLS ping for MPLS TE tunnels· 2

Using MPLS tracert for MPLS TE tunnels· 2

Verifying PW connectivity· 2

About PW connectivity verification· 2

Configuring a PW class· 2

Using 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.

The device supports the following OAM features in the current software version:

·           MPLS ping for LSPs, MPLS TE tunnels, and PWs.

·           MPLS tracert for LSPs and MPLS TE tunnels.

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

Verifying LSP connectivity

Using MPLS ping for LSPs

To use MPLS ping 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 ] ] ]

Using MPLS tracert for LSPs

To use MPLS tracert to trace the LSPs for an IPv4 prefix, 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 ] ] ]

Verifying MPLS TE tunnel connectivity

Using 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

Using 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 for verifying 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 uses MPLS router alert labels as CCs in the current software version. An MPLS router alert label identifies a VCCV packet by adding an MPLS router alert label before the PW label.

Configuring a PW class

1.      Enter system view.

system-view

2.      Create a PW class and enter  its view.

pw-class class-name

3.      Specify the VCCV CC type.

vccv cc  router-alert

By default, no VCCV CC types are specified for a PW class.

Using MPLS ping for a PW

1.      Enter system view.

system-view

2.      Enter cross-connect group view.

xconnect-group group-name

3.      Enter cross-connect view.

connection connection-name

4.      Configure a PW, specify the created PW class for it, and enter PW view.

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] pw-class class-name [ tunnel-policy tunnel-policy-name ]

By default, no PW is configured.

5.      Use MPLS ping to verify the connectivity of a PW.

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

This command is available in any view.