ping mpls l2vpn

Check the operability of Multiprotocol Label Switching (MPLS) Layer 2 virtual private network (VPN) connections. Type Ctrl+c to interrupt a ping mpls l2vpn command.

Options

instance instance-name local-site-id local-site-id-number remote-site-id remote-site-id-number — Ping a combination of the Layer 2 VPN routing instance name, the local site identifier, and the remote site identifier, testing the integrity of the Layer 2 VPN circuit (specified by the identifiers) between the ingress and egress provider edge (PE) routers.

interface interface-name — Ping an interface configured for the Layer 2 VPN on the egress PE router.

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.

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).

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.

Required Privilege Level

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.

ping mpls l2vpn instance

user@host> ping mpls l2vpn instance vpn1 remote-site-id
1 local-site-id 2

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

ping mpls l2vpn instance detail

user@host> ping mpls l2vpn instance vpn1 remote-site-id
1 local-site-id 2 detail

Request for seq 1, to interface 68, labels <800001, 100176>
Reply for seq 1, return code: Egress-ok
Request for seq 2, to interface 68, labels <800001, 100176>
Reply for seq 2, return code: Egress-ok
Request for seq 3, to interface 68, labels <800001, 100176>
Reply for seq 3, return code: Egress-ok
Request for seq 4, to interface 68, labels <800001, 100176>
Reply for seq 4, return code: Egress-ok
Request for seq 5, to interface 68, labels <800001, 100176>
Reply for seq 5, return code: Egress-ok

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

Syntax

Release Information