EasyManuals Logo

Juniper JUNOSE 11.2.X BGP AND MPLS User Manual

Juniper JUNOSE 11.2.X BGP AND MPLS
742 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #453 background imageLoading...
Page #453 background image
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.
417Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Configuring BGP-MPLS Applications

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Juniper JUNOSE 11.2.X BGP AND MPLS and is the answer not in the manual?

Juniper JUNOSE 11.2.X BGP AND MPLS Specifications

General IconGeneral
BrandJuniper
ModelJUNOSE 11.2.X BGP AND MPLS
CategorySoftware
LanguageEnglish

Related product manuals