bgp wait-on-end-of-rib
•
Use to configure how long BGP waits to receive End-of-RIB markers from route-target
address family peers.
•
The wait interval applies to all route-target address family peers.
•
This command takes effect immediately.
•
Example
host1(config-router)#
address-family route-target signaling
host1(config-router-af)#
bgp wait-on-end-of-rib 360
•
Use the
no
version to restore the default wait interval, 60 seconds.
•
See bgp wait-on-end-of-rib.
neighbor maximum-prefix
•
Use to control how many prefixes can be received from a neighbor.
•
If you specify a BGP peer group by using the
peerGroupName
argument, all the members
of the peer group inherit the characteristic configured with this command unless it is
overridden for a specific peer.
•
By default, BGP checks the maximum prefix limit only against accepted routes. You
can specify the
strict
keyword to force BGP to check the maximum prefix against all
received routes. The accepted and received routes will likely differ when you have
configured inbound soft reconfiguration and route filters for incoming traffic.
•
This command takes effect immediately. To prevent a peer from continually flapping,
when it goes to state idle because the maximum number of prefixes has been reached,
the peer stays in state idle until you use the
clear ip bgp
command to issue a hard clear.
•
Example
host1(config-router)#
address-family route-target signaling
host1(config-router-af)#
neighbor maximum-prefix 10.1.2.3 100
•
Use the
no
version to remove the maximum number of prefixes.
•
See neighbor maximum-prefix.
Conditions for Advertising RT-MEM-NLRI Routes
The following conditions must be met for routes in the route-target address family to be
advertised to a BGP peer:
1.
The BGP peers have successfully negotiated the route-target address family.
2.
The import route-target list for the IPv4 VRF is not empty or is transitioning to empty.
In a VRF, a RT-MEM-NLRI attribute represented by (origin AS number:route target) is
advertised for every route target added to the VRF's route target import list when the
preceding conditions have been met.
A withdrawal for the RT-MEM-NLRI attribute is generated when the route target is
removed from this VRF's import list.
417
Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Configuring BGP-MPLS Applications
Summary of Contents for JUNOSE 11.2.X BGP AND MPLS
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 38: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 192: ...Copyright 2010 Juniper Networks Inc 156 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 242: ...Copyright 2010 Juniper Networks Inc 206 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 244: ...Copyright 2010 Juniper Networks Inc 208 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 310: ...Copyright 2010 Juniper Networks Inc 274 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 356: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 418: ...Copyright 2010 Juniper Networks Inc 382 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 524: ...Copyright 2010 Juniper Networks Inc 488 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 544: ...Copyright 2010 Juniper Networks Inc 508 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 608: ...Copyright 2010 Juniper Networks Inc 572 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 672: ...Copyright 2010 Juniper Networks Inc 636 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 674: ...Copyright 2010 Juniper Networks Inc 638 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 716: ...Copyright 2010 Juniper Networks Inc 680 JunosE 11 2 x BGP and MPLS Configuration Guide...
Page 717: ...PART 6 Index Index on page 683 681 Copyright 2010 Juniper Networks Inc...
Page 718: ...Copyright 2010 Juniper Networks Inc 682 JunosE 11 2 x BGP and MPLS Configuration Guide...