Destination address 127.0.0.1
100 bytes from 100.1.2.1: Sequence=1 time=49 ms Return Code=3(1)
Destination address 127.0.0.3
100 bytes from 100.1.2.1: Sequence=2 time=44 ms Return Code=3(1)
Destination address 127.0.0.1
100 bytes from 100.1.2.1: Sequence=3 time=60 ms Return Code=3(1)
Destination address 127.0.0.3
100 bytes from 100.1.2.1: Sequence=4 time=60 ms Return Code=3(1)
Destination address 127.0.0.1
100 bytes from 100.1.2.1: Sequence=5 time=76 ms Return Code=3(1)
Destination address 127.0.0.3
100 bytes from 100.1.2.1: Sequence=6 time=57 ms Return Code=3(1)
--- Ping statistics for FEC 3.3.3.9/32 ---
6 packets transmitted, 6 packets received, 0.0% packet loss
Round-trip min/avg/max = 44/57/76 ms
Table 47 Command output
Field
MPLS Ping FEC: 3.3.3.9/32 : 100 data bytes
Destination address
100 bytes from 100.1.2.1
Sequence
time
Return Code
Ping statistics for FEC 3.3.3.9/32
packets transmitted
packets received
packet loss
Round-trip min/avg/max
tracert mpls ipv4
Use tracert mpls ipv4 to trace MPLS LSPs from the ingress node to the egress node for an IPv4 prefix. You
can locate the error node according to the reply information.
Description
Verify LSP connectivity for FEC 3.3.3.9/32 by sending
100-byte MPLS echo requests.
Destination IP address in the IP header.
Received a 100-byte reply from 100.1.2.1.
Sequence number of the reply, for determination of packet
loss, disorder, or duplicate.
Packet round-trip delay.
Return code. The number in parentheses represents a return
subcode.
LSP verification statistics.
Number of MPLS echo requests sent.
Number of MPLS echo replies received.
Percentage of the unreplied packets to the total request
packets.
Minimum, average, and maximum round-trip delay.
144