Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


ping mpls rsvp



Check the operability of MPLS RSVP-signaled label-switched path (LSP) connections. Type Ctrl+c to interrupt a ping mpls command.


count count

(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5.

destination address

(Optional) Specify an address other than the default ( for the ping echo requests. The address can be anything within the 127/8 subnet.


(Optional) Display detailed information about the echo requests sent and received.


When using the detail option, the reported time is based on the system time configured on the local and remote routers. Differences in these system times can result in inaccurate one way ping trip times being reported.

In practice, it is difficult to synchronize the system times of independent Juniper Networks routers with sufficient accuracy to provide a meaningful time value for the detail option (even when synchronized using NTP).


(Optional) Ping dynamically generated bypass LSPs, used for protecting other LSPs.

egress egress-address

(Optional) Only the specified egress router or switch responds to the ping request.

exp forwarding-class

(Optional) Value of the forwarding class for the MPLS ping packets.


(Optional) Specify the name of the interface protected by the manual bypass LSP. This option is only available when you have also used the manual-bypass option.

logical-system (all | logical-system-name)

(Optional) Perform this operation on all logical systems or on the specified logical system.


Ping an RSVP-signaled LSP using an LSP name.


(Optional) Ping manually configured bypass LSPs, used for protecting other LSPs. For this option, you must also specify the interface protected by the manual bypass LSP using the interface option.


(Optional) Send ping requests to each of the egress routers or switches participating in a point-to-multipoint LSP. You can also include the egress option to ping a specific egress router or switch participating in a point-to-multipoint LSP.

size bytes

(Optional) Size of the LSP ping request packet (100 through 65468 bytes). Packets are 4-byte aligned. For example, if you enter a size of 101, 102, 103, or 104, the router or switch uses a size value of 104 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 100-byte minimum.

source source-address

(Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface.

standby standby-path-name

(Optional) Name of the standby path.


(Optional) Automatically determine the size of the maximum transmission unit (MTU).

Additional Information

If the LSP changes, the label and interface information displayed when you issued the ping command continues to be used. You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote router or switch to ping an LSP terminating there. You must configure MPLS even if you intend to ping only LDP forwarding equivalence classes (FECs).

In asymmetric MTU scenarios, the echo response might be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large.


In a Juniper-Cisco interoperation network scenario, a point-to-multipoint LSP ping echo reply message from a Cisco device in a different IGP area is dropped on the Juniper device when the source address of the reply message is an interface address other than the loopback address or router ID. Starting in Junos OS Release 13.3X8, 14.2R6, 15.1R4, 15.1F6, 15.1F5-S8, 16.1R1, and later releases, such point-to-multipoint LSP ping echo reply messages are accepted by the Juniper device and the messages get logged as uncorrelated responses.

Required Privilege Level


Output Fields

When you enter this command, you are provided feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the timeout period. An x indicates that an echo reply was received with an error code. Packets with an error code are not counted in the received packets count. They are accounted for separately.

Sample Output

ping mpls rsvp (Echo Reply Received)

ping mpls rsvp (Echo Reply with Error Code)

ping mpls rsvp detail

ping mpls rsvp multipoint egress detail count

ping mpls rsvp multipoint detail count

ping mpls rsvp destination detail count size

ping mpls rsvp destination detail sweep size

Release Information

Command introduced before Junos OS Release 7.4.

The egress and multipoint options were introduced in Junos OS Release 9.2.

The size and sweep options were introduced in Junos OS Release 9.6.

The dynamic-bypass and manual-bypass options were introduced in Junos OS Release 10.2.