Configuring Mpls Oam; Overview; Mpls Ping; Mpls Tracert - HP FlexNetwork 10500 Series Configuration Manual

Configuring MPLS OAM

Overview

MPLS Operation, Administration, and Maintenance (OAM) provides the on-demand tools for the
following purposes:
•
MPLS data plane connectivity verification.
•
Data plane and control plane consistency verification.
•
Fault locating.
The on-demand tools must be triggered manually, such as MPLS ping and MPLS tracert. You can
use the on-demand tools to detect and locate faults of MPLS 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

Restrictions and guidelines for MPLS OAM

MPLS OAM is mutually exclusive with EVI and VXLAN. For more information about EVI, see EVI
Configuration Guide. For more information about VXLAN, see VXLAN Configuration Guide.

Configuring MPLS OAM for LSP tunnels

To verify LSP connectivity, you can use the ping mpls ipv4 command or the tracert mpls ipv4
command to trigger LSP connectivity verification as needed.
418