Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual page 3837

Additional Information
Required Privilege
Level
List of Sample Output
Output Fields
ping mpls l2vpn ping mpls l2vpn
instance instance
ping mpls l2vpn
instance detail
Copyright © 2010, Juniper Networks, Inc.
—Reply using an IPv4 or IPv6 UDP packet.
ip-udp
—Do not reply to the ping request.
no-reply
The option and its suboptions
reply-mode
and are also available in Junos OS Release 10.2R4 and 10.3R2.
no-reply
size bytes —(Optional) Size of the label-switched path (LSP) ping request packet (
through bytes). Packets are 4-byte aligned. For example, If you enter a size
65468
of 97, 98, 99, or 100, the router or switch 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.
—(Optional) IP address of the outgoing interface. This address is
source source-address
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).
You must configure MPLS at the
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 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.
network
ping mpls l2vpn instance on page 3733
ping mpls l2vpn instance detail on page 3733
ping mpls l2vpn interface <interface-name> reply-mode on page 3734
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 (
that an echo reply was not received within the timeout period. An
echo reply was received with an error code these packets are not counted in the received
packets count. They are accounted for separately.
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
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>
Chapter 137: Operational Commands for MPLS
application-level-control-channel, ip-udp
lo.0
[edit protocols mpls] hierarchy level on the egress PE
,
96
).
. ) indicates
indicates that an
x
3733