ping mpls l3vpn

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 a MPLS Layer 3 virtual private network (VPN) connection. Type Ctrl+c to interrupt a ping mpls l3vpn command.

Options

prefix prefix-name — Ping to test whether a prefix is present in a provider edge (PE) router's VPN routing and forwarding table, by means of a Layer 3 VPN destination prefix. This option does not test the connection between a PE router and a customer edge router.

l3vpn-name — (Optional) Layer 3 VPN name.

bottom-label-ttl — (Optional) Display the time-to-live value for the bottom label in the label stack.

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 label-switched path (LSP) ping request packet (96 through 65468 bytes). Packets are 4-byte aligned. For example, If you enter a size of 97, 98, 99, or 100, the router uses a size value of 100 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 96-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 (lo.0).

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

Additional Information

You must configure MPLS at the [edit protocols mpls] hierarchy level on the egress PE router (the router receiving the MPLS echo packets) to ping a Layer 2 circuit.

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

!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

Request for seq 1, to interface 68, labels <100128, 100112> 
Reply for seq 1, return code: Egress-ok 
Request for seq 2, to interface 68, labels <100128, 100112> 
Reply for seq 2, return code: Egress-ok 
Request for seq 3, to interface 68, labels <100128, 100112> 
Reply for seq 3, return code: Egress-ok 
Request for seq 4, to interface 68, labels <100128, 100112> 
Reply for seq 4, return code: Egress-ok 
Request for seq 5, to interface 68, labels <100128, 100112> 
Reply for seq 5, return code: Egress-ok
--- lsping statistics --- 
5 packets transmitted, 5 packets received, 0% packet loss