Login
- Table of Contents
-
- 08-MPLS Configuration Guide
- 00-Preface
- 01-Basic MPLS configuration
- 02-Static LSP configuration
- 03-LDP configuration
- 04-MPLS TE configuration
- 05-Static CRLSP configuration
- 06-RSVP configuration
- 07-Tunnel policy configuration
- 08-MPLS L3VPN configuration
- 09-MPLS L2VPN configuration
- 10-VPLS configuration
- 11-MPLS OAM configuration
- 12-MCE configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 11-MPLS OAM configuration | 57.55 KB |
Restrictions and guidelines for MPLS OAM
Configuring MPLS OAM for LSP tunnels
Configuring MPLS ping for LSPs
Configuring MPLS tracert for LSPs
Configuring MPLS OAM for MPLS TE tunnels
Configuring MPLS ping for MPLS TE tunnels
Configuring MPLS tracert for MPLS TE tunnels
Configuring MPLS OAM
Overview
· 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.
Configuring MPLS ping for LSPs
Perform the following task in any view:
|
Task |
Command |
|
Use MPLS ping to verify MPLS LSP connectivity for an IPv4 prefix. |
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 ] ] ] |
Configuring MPLS tracert for LSPs
Perform the following task in any view:
|
Task |
Command |
|
Use MPLS tracert to trace the LSPs for an IPv4 prefix. |
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 ] ] ] |
Configuring MPLS OAM for MPLS TE tunnels
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.
Configuring MPLS ping for MPLS TE tunnels
Perform the following task in any view:
|
Task |
Command |
|
Use MPLS ping to verify MPLS TE tunnel connectivity. |
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 |
Configuring MPLS tracert for MPLS TE tunnels
Perform the following task in any view:
|
Task |
Command |
|
Use MPLS tracert to trace an MPLS TE tunnel. |
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 |
Configuring MPLS OAM for a PW
Virtual Circuit Connectivity Verification (VCCV) is an L2VPN PW OAM feature to verify PW connectivity in data plane. To implement VCCV, execute the ping mpls pw command to trigger PW connectivity detection. The packets used to verify PW connectivity are collectively referred to as VCCV packets. A PE transfers VCCV packets through an MPLS router alert label type control channel (CC) to test PW connectivity. The MPLS router alert label type CC identifies a VCCV packet by adding an MPLS router alert label before the PW label.
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.
Perform the following task in any view:
|
Task |
Command |
|
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 |
