Table 51: TLVs Supported by MPLS LSP ping (continued)
CommentsValueType Number
This TLV is included in the MPLS echo request
packet to validate whether the IP address
specified in the TLV is an IP address of one of the
interfaces in the router. Four sub-TLVs are defined
for inclusion in the P2MP Responder Identifier TLV
in the echo request message.
P2MP Responder Identifier11
This TLV is included in the LSP ping message
(echo request) to enable the egress node of a
point-to-multipoint LSP to delay the transmission
of the response by a time interval that is limited
by the value specified in this TLV. In JunosE
Software, the delay is set to a maximum of 30
seconds.
Echo Jitter12
Table 52: Sub-TLVs Supported for the Target FEC Stack TLV
CommentsValueSubtype Number
–LDP IPv4 prefix1
–LDP IPv6 prefix2
–RSVP IPv4 LSP3
–VPN IPv4 prefix6
–VPN IPv6 prefix7
For VPLS and VPWSL2 VPN endpoint8
For Martini encapsulationFEC 128 pseudowire10
For identification of the
point-to-multipoint LSP for
which you want to verify
the data plane
RSVP P2MP IPv4 Session17
Related Topics MPLS Label Switching and Packet Forwarding Overview on page 218•
MPLS Connectivity Verification and Troubleshooting Methods
In IP networks, the ping and traceroute commands enable you to verify network
connectivity and find broken links or loops. In MPLS-enabled networks, you can use the
ping command to determine whether IP connectivity exists to a destination even when
the ping packets must traverse multiple LSPs. You can use the traceroute command to
determine the labels that data packets use when traversing LSPs to the destination.
Copyright © 2010, Juniper Networks, Inc.244
JunosE 11.2.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
