Country

- China
- France
- Germany
- Japan
- Korea
- Spain
- Taiwan
- United Kingdom
- United States

Contact Us
|
Country
United States

# Technical Documentation

- Download Software
- Research a Problem
- Case Management
- Contract & Product Management
- Technical Documentation
  - Advanced Search
  - Documentation Archive
  - Documentation Bug Report
  - Enterprise MIBs
  - File Format Help
  - Glossary
  - Portable Libraries
- End-of-Life Products
- Contact Support
- Guidelines and Policies
- Security Resources

# trace mpls vpls

#### Syntax

trace mpls vpls [ vrf vrfName ] vplsName
[ sender-site-id senderSiteId ] remote-site-id remoteSiteId
[ data-size dataSize ]
[ destination startIpAddress endIpAddress increment
]
[ source address sourceAddr ]
[ ttl ttlValue ] [ timeout timeOutVal ]
[ reply mode { ipv4-udp | ipv4-udp-with-router-alert } ]
[ reply pad-tlv ] [ reply dscp trafficClass ]
[ exp-bits bitValue ] [ bottom-label-ttl bottomLabelTtl ] [ detail ]

#### Release Information

Command introduced in JunosE Release 8.0.0.

data-size keyword and dataSize variable added in JunosE Release 11.1.0.

#### Description

Sends MPLS echo request packets with successively higher TTL values to the specified VPLS instance. Discovers the path MPLS packets follow to the destination. There is no no version.

The MPLS echo request packets and echo reply packets created by this command use the L2 endpoint sub-TLV described in RFC 4379—Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures (February 2006).

#### Options

- vrfName—Name of the VRF context from which to generate the ping
- vplsName—Name of a VPLS instance created with the bridge vpls transport-virtual-router command
- senderSiteId—Numerical identifier for the site sending the MPLS echo request packet; must be an unsigned 16-bit integer greater than zero that is unique across the VPLS domain
- remoteSiteId—Numerical identifier for the site receiving the MPLS echo request packet; must be an unsigned 16-bit integer greater than zero that is unique across the VPLS domain
- dataSize—Size of the LSP ping message (does not include the UDP, IP, and MPLS headers of the packet); in the range 0–6400 bytes. The default value is 100 bytes. You can use this option to enable the pad TLV to be added to the MPLS LSP ping message (echo request), which results in the future MPLS LSP ping echo requests to be of the same specified number of bytes.
- startIpAddress—First IP address within the 127.0.0.0/8 destination range
- endIpAddress—Last IP address within the 127.0.0.0/8 destination range
- increment—Number in the range 0–255 that specifies the increment between addresses in the destination address range
- sourceAddr—IP address used as the packet source address
- ttlValue—Hop count specified by setting the time-to-live field in the header, in the range 1–255; default value is 32; however, by default, the TTL on the inner (stacked) label is set to 1 while transmitting the echo request packet, which causes the packet to be exceptioned to the SRP module when the stacked label is exposed
- timeOutVal—Number of seconds in the range 1–32 to wait for an MPLS echo reply packet before the connection attempt times out
- reply mode—Specifies the reply mode for the echo request packet
  - ipv4-udp—Specifies that the echo request packet is an IPv4 UDP packet
  - ipv4-udp-with-router-alert—Specifies that the echo request packet is an IPv4 UDP packet with the router alert bit set in the header so all routers examine this packet more closely to determine whether further processing is necessary
- reply pad-tlv—Requests sender of an echo reply to send a pad TLV
- trafficClass—Number in the range 0–255 that represents the value of the traffic class that the sender of an echo reply is requested to set
- bitValue—Value of the EXP bits in the range 0–7 included in the MPLS echo request packet
- bottomLabelTtl—Time-to-live value of the bottom label in the stack
- detail—Displays detailed information about MPLS echo request sent and echo replies received

#### Mode

Privileged Exec, User Exec

#### Published: 2010-07-14

Help
|
My Account
|
Log Out