Juniper BGP - CONFIGURATION GUIDE V 11.1.X Configuration Manual page 741

Node Address P2MP Responder Identifier sub-TLVs
sending of echo responses
if sub-TLV address matches with node
address....................................................241
specifying
IPv4 address of interface or router ID..........241
IPv6 address of interface or router ID..........241
nontransit service........................................................11
notice icons.............................................................xxxiii
notification message, BGP..............................................7
O
ORF (outbound route filtering)...................................126
Origin attribute..........................................................117
originator-ID, BGP........................................................11
OSPF interaction with BGP/MPLS VPNs......................479
backdoor link......................................................479
configuration........................................................17
domain identifier attribute..................................479
route type attribute.............................................479
routes
distributing between PEs.............................479
distributing from CE to PE...........................479
distributing from PE to CE...........................479
routing information, preserving..........................479
routing loops, preventing....................................479
sham link............................................................479
outbound route filtering capability.............................126
overlapping VPN topologies, configuring with route
targets....................................................................408
overlapping VPNs, configuring with route targets.......408
overload shutdown command......................................33
P
P routers....................................................................382
P2MP Responder Identifier TLV
conditions for echo response to originator
echo request not sent to egress node...........238
errors in TLV syntax....................................238
detecting data plane failures
at egress nodes in point-to-multipoint MPLS
LSPs.........................................................237
difference in type value for
between JUNOS Software and IETF
standard...................................................238
echo response to originator
in the absence of TLV in echo request.........238
excluded from echo requests
causes all nodes in path to ingress node to
respond....................................................240
response depends on Response Type field
................................................................240
including in
MPLS echo request packets..........................240
IP address in the TLV matching with interface IP
address
success response to the sender....................238
IP address in the TLV not matching with interface
IP address
no response to the sender...........................238
multiple sub-TLVs included in
using subtype numbers for processing
order........................................................240
supported sub-TLVs for
IPv4 Egress Address P2MP Responder
Identifier..................................................240
IPv4 Node Address P2MP Responder
Identifier..................................................240
IPv6 Egress Address P2MP Responder
Identifier..................................................240
IPv6 Node Address P2MP Responder
Identifier..................................................240
to process MPLS LSP ping messages, echo requests
validation of IP address in the TLV with
interface address......................................238
tracing the path from an ingress node
in point-to-multipoint LSPs..........................240
type number, 11.................................................240
type value defined in
IETF draft, Detecting Data Plane Failures in
Point-to-Multipoint Multiprotocol Label
Switching (MPLS) - Extensions to LSP Ping
................................................................238
type value reconciliation between
JUNOS Software and IETF draft...................238
without sub-TLVs included in
ignoring the entire TLV in echo
requests...................................................240
parallel routes, maximum number of.........................438
passive peers, BGP.......................................................43
passthrough for ATM over MPLS
control word support..........................................517
OAM cells...........................................................516
QoS classification................................................517
path attribute, BGP.......................................................10
path trigger delay command......................................290
path, BGP.......................................................................8
PE routers..................................................................382
peer groups, BGP...........................................................3
configuring............................................................26
monitoring..........................................................172
peer reachability
RSVP-TE..............................................................251
peer type, set the BGP..................................................28
peers (neighbors), BGP
assigning weights to............................................112
distributing information in access lists..................83
monitoring..........................................................172
passive..................................................................43
promiscuous.........................................................43
Index
705
Index