Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    ping mpls l3vpn


    ping mpls l3vpn [ vrf vrfName ]
    { targetAddress targetMask | targetIpv6Prefix }
    [ destination startIpAddress endIpAddress increment ]
    [ source address sourceAddr ] [ [ repeat ] packetCount ]
    [ ttl ttlValue ] [ timeout timeOutVal ]
    [ data-size dataSize | sweep-sizes sweepMin sweepMax sweepInt ]
    [ pad { ones | zeros | random | hex-data hexData } ]
    [ reply mode { ipv4-udp | ipv4-udp-with-router-alert } ]
    [ reply pad-tlv ] [ reply dscp trafficClass ]
    [ interval txdelayVal ] [ exp-bits bitValue ] [ bottom-label-ttl bottomLabelTtl ]
    [ detail ]

    Release Information

    Command introduced in JunosE Release 8.0.0.


    Sends an MPLS echo request packet to the specified L3VPN IP or IPv6 prefix, or alternatively, sends MPLS echo packets to the egress node in a point-to-multipoint LSP. There is no no version.

    The echo request packet generated by this command contains either the VPN IPv4 sub-TLV or VPN IPv6 sub-TLV described in RFC 4379—Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures (February 2006). Which sub-TLV is included depends on whether the ping is intended for an IPv4 prefix or an IPv6 prefix.

    You can use this command to send a request to a VPNv4 prefix in the specified VRF. If you do not specify a VRF, then you must issue the command from the VRF context. In any case, the ping originates from the parent router.

    The MPLS echo request packets and echo reply packets created by this command to detect connectivity to egress nodes in point-to-multipoint LSPs use the P2MP Responder Identifier TLV described in the IETF draft, Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol Label Switching (MPLS) - Extensions to LSP Ping—draft-ietf-mpls-p2mp-lsp-ping-08.txt (February 2010 expiration).


    • vrfName—Name of the VRF context
    • targetAddress—IP address of the target VPN network
    • targetMask—Netmask for the target address
    • targetIpv6Prefix—IPv6 prefix for the target VPN network
    • startIpAddress—First IP address within the destination range
    • endIpAddress—Last IP address within the 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
    • repeat—Specifies that multiple ping packets are sent
    • packetCount—Number of packets to send to the destination address, in the range 0–4294967295; default value is 5; 0 means ping forever
    • ttlValue—Hop count specified by setting the time-to-live field in the header, in the range 1–255; default value is 32
    • timeOutVal—Number of seconds in the range 1–32 to wait for an MPLS echo reply packet before the connection attempt times out
    • dataSize—Number of bytes comprising the MPLS packet, including the header, in the range 0–64000; default value is 100 bytes
    • sweep-sizes—Configures payload sizes, enabling you to vary the sizes of the echo packets being sent. This capability is useful for determining the minimum sizes of the MTUs configured on the nodes along the path to the destination address. This reduces packet fragmentation which contributes to performance problems. The default is not to sweep; all packets are the same size.
      • sweepMin—Minimum payload size in the range 0–64000
      • sweepMax—Maximum payload size in the range 0–64000
      • sweepInt—Number of bytes to add to the size of the packet; the change in the size of subsequent ping packets while sweeping across a range of sizes. For example, you can configure the sweep interval to sweep across the range of packets from 0 bytes to 10,000 bytes in increments of sweepInt. By default, send 100, 101, 102, 103...1000. If sweepInt is 5, send 100, 105, 110, 115...1000). When “ sweeping,” the default interval is 1.
    • pad—Specifies the type of bits contained in the pad TLV. You can set the bits to all ones, all zeros, a random mixture of ones and zeros, or a specific hexadecimal data pattern, in the range from 0x0–0xFFFFFFFF. The default data pattern is all zeros.
    • 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
    • txDelayVal—Number of milliseconds in the range 1–50 between transmission of each echo request; default value is 10 ms
    • 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


    Privileged Exec, User Exec

    Published: 2014-08-18