ping mpls l3vpn
Syntax
ping mpls l3vpn prefix prefix-name <l3vpn-name> <bottom-label-ttl> <count count> <destination address> <detail> <exp forwarding-class> <logical-system (all | logical-system-name)> <size bytes> <source source-address> <sweep>
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
| 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 |
| destination address | (Optional) Specify an address other than the default
( |
| 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. |
| l3vpn-name | (Optional) Layer 3 VPN name. |
| logical-system (all | logical-system-name) | (Optional) Perform this operation on all logical systems or on the specified logical system. |
| prefix prefix-name | Ping to test whether a prefix is present in a provider edge (PE) router’s or switch's VPN routing and forwarding (VRF) table, by means of a Layer 3 VPN destination prefix. This option does not test the connection between a PE router or switch and a customer edge (CE) router or switch. |
| size bytes | (Optional) Size of the label-switched path (LSP) ping
request packet ( |
| 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 ( |
| 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
or switch (the router or switch receiving the MPLS echo packets) to
ping a Layer 2 circuit.
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.
If the Layer 3 VPN traffic transits a route reflector within
the network, the ping mpls l3vpn command does not work.
Required Privilege Level
network
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
ping mpls l3vpn
user@host> ping mpls l3vpn vpn1 prefix 10.255.245.122/32 !!!!! --- lsping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss
ping mpls l3vpn detail
user@host> ping mpls l3vpn vpn1 prefix 10.255.245.122/32 detail 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
Release Information
Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced
in Junos OS Release 9.6.