Table of Contents
Advertisement
JunosE 11.2.x BGP and MPLS Configuration Guide
Related Topics
LDP Discovery Mechanisms
250
Table 53: Sub-TLVs Supported for the P2MP Responder Identifier TLV
(continued)
Subtype Number
Value
4
IPv6 Node Address P2MP
Responder Identifier
The echo response is always controlled by the Response Type field in the echo message
and also depends on whether the responding node is part of the point-to-multipoint LSP
that is denoted in the Target FEC Stack TLV. The following sections describe the sub-TLVs
of the P2MP Responder Identifier TLV, which are additional influencing factors to those
requirements and are not a replacement for those requirements:
Egress Address P2MP Responder Identifier Sub-TLVs on page 250
Node Address P2MP Responder Identifier Sub-TLVs on page 250
Egress Address P2MP Responder Identifier Sub-TLVs
You can use the IPv4 or IPv6 Egress Address P2MP Responder Identifier sub-TLVs in an
echo request that contains the RSVP P2MP Session or Multicast LDP FEC Stack sub-TLV.
An egress node that receives an echo request with this sub-TLV present responds only
if the node lies on the path to the address in the sub-TLV. The address in this sub-TLV
is the address of the egress node and does not specify the address of a branch or
intermediate node. This address is made available to the nodes upstream of the target
node, using signaling protocols, such as RSVP. This sub-TLV may be used to trace a
specific egress node in a point-to-multipoint LSP.
Node Address P2MP Responder Identifier Sub-TLVs
You can use the IPv4 or IPv6 Node Address P2MP Responder Identifier sub-TLVs in an
echo request that contains the RSVP P2MP Session or Multicast LDP FEC Stack sub-TLV.
A node that receives an echo request with this sub-TLV present responds only if the
address in the sub-TLV corresponds to any address that is local to the node. This address
in the sub-TLV might be of any physical interface or the router ID of the node itself. The
address in this sub-TLV can be the address of any transit, branch, or egress node for that
point-to-multipoint LSP.
Troubleshooting MTU Problems in Point-to-Point LSPs on page 379
Ping Extensions for Point-to-Multipoint LSPs Connectivity Verification at Egress Nodes
on page 246
Point-to-Multipoint LSPs Connectivity Verification at Egress Nodes Overview on page 246
Verifying and Troubleshooting MPLS Connectivity on page 370
LDP uses two different mechanisms for peer discovery. Peer discovery removes the need
to explicitly configure the label-switching peers for an LSR.
Comments
The IPv6 address in the sub-TLV
might be of any physical interface
or the router ID of the node itself.
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
Troubleshooting
