ping mpls lsp-end-point

Syntax

Release Information

Command introduced before JUNOS Release 7.4.

The size and sweep options were introduced in JUNOS Release 9.6.

Description

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

Options

prefix-name — LDP forwarding equivalence class (FEC) prefix or RSVP LSP endpoint address.

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 (127.0.0.1/32) for the ping echo requests. The address can be anything within the 127/8 subnet.

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

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

logical-system (all | logical-system-name) — (Optional) Perform this operation on all logical systems or on the specified logical system.

size bytes — (Optional) Size of the LSP ping request packet. If the endpoint is LDP-based, the minimum size of the packet is 88 bytes. If the endpoint is RSVP-based, the minimum size of the packet is 100 bytes. The maximum size in either case is 65468 bytes.

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 (lo.0).

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

Additional Information

If the LSP changes, the label and interface information displayed when the ping command was issued continues to be used. You must configure MPLS at the [edit protocols mpls] hierarchy level on the remote router 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 may 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.

Required Privilege Level

network

List of Sample Output

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 these packets are not counted in the received packets count. They are accounted for separately.

Sample Output

Route 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