Specifying A Single-Hop Connection For Ibgp Peers; Controlling The Number Of Prefixes - Juniper JUNOSE SOFTWARE FOR E SERIES 11.0.X - BGP AND MPLS CONFIGURATION GUIDE 2009-12-30 Configuration Manual

Specifying a Single-Hop Connection for IBGP Peers

IBGP peers are multihop by default. However, you can use the neighbor
ibgp-single-hop command to enable single-hop connections for IBGP peers.
neighbor ibgp-singlehop

Controlling the Number of Prefixes

As the routing table increases in size, the processor and memory resources required
to process routing information increases. Some peers send so much routing
information that a BGP speaker can be overwhelmed by the updates. You can use
the neighbor maximum-prefix command to limit how many prefixes can be received
from a neighbor.
The router resets the BGP connection when the specified maximum is exceeded.
You can use the warning-only keyword to log a warning rather than reset the
connection. You can also configure the router so that a warning is logged when a
specified percentage of the maximum is exceeded.
In the following example, the router is configured to reset the BGP connection when
it receives more than 1,000 prefixes from its neighbor at 2.2.2.2:
This command takes effect immediately and automatically bounces the BGP
session.
Use the no version to return BGP to halt acceptance of such routers. Use the
default version to remove the explicit configuration from the peer or peer group
and reestablish inheritance of the feature configuration.
See neighbor ebgp-multihop
Use to specify an internal BGP peer as a single-hop peer for IBGP sessions.
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.
If the neighbor session type is anything other than internal BGP, issuing this
command generates an error message.
This command takes effect immediately and automatically bounces the BGP
session.
Example
host1(config-router)#neighbor 192.168.32.15 ibgp-singlehop
Use the no version to restore the default behavior, wherein the internal peer
cannot be a single-hop peer. Use the default version to remove the explicit
configuration from the peer or peer group and reestablish inheritance of the
feature configuration.
See neighbor ibgp-singlehop
Chapter 1: Configuring BGP Routing
Configuring BGP Peer Groups
33