Table of Contents
Advertisement
JunosE 11.2.x BGP and MPLS Configuration Guide
Related Topics
MPLS Connectivity Verification and Troubleshooting Methods
244
Table 51: TLVs Supported by MPLS LSP ping (continued)
Type Number
Value
11
P2MP Responder Identifier
12
Echo Jitter
Table 52: Sub-TLVs Supported for the Target FEC Stack TLV
Subtype Number
Value
1
LDP IPv4 prefix
2
LDP IPv6 prefix
3
RSVP IPv4 LSP
6
VPN IPv4 prefix
7
VPN IPv6 prefix
8
L2 VPN endpoint
10
FEC 128 pseudowire
17
RSVP P2MP IPv4 Session
MPLS Label Switching and Packet Forwarding Overview on page 218
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.
Comments
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.
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.
Comments
–
–
–
–
–
For VPLS and VPWS
For Martini encapsulation
For identification of the
point-to-multipoint LSP for
which you want to verify
the data plane
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
Troubleshooting
