ping mpls lsp-end-point
Syntax
Release Information
Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced in Junos OS Release 9.6.
The instance option was introduced in Junos OS Release 10.0.
Description
Check the operability of MPLS label-switched path (LSP) endpoint connections. Type Ctrl+c to interrupt a ping mpls command.
Options
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
network
List of Sample Output
ping mpls lsp-end-point detailOutput 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 lsp-end-point detail
user@host> ping mpls lsp-end-point 10.255.245.119
detailRoute to end point address is via LDP FEC Request for seq 1, to interface 67, label 100032 Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 67, label 100032 Reply for seq 2, return code: Egress-ok Request for seq 3, to interface 67, label 100032 Reply for seq 3, return code: Egress-ok Request for seq 4, to interface 67, label 100032 Reply for seq 4, return code: Egress-ok Request for seq 5, to interface 67, label 100032 Reply for seq 5, return code: Egress-ok --- lsping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss