
Configuring IP Services
5-22
When setting up IBGP connections, consider using a circuitless IP interface.
Doing so separates the connection endpoint from any of the physical interfaces on
the router. For example, if the BGP connection is configured over a physical
interface and that interface becomes disabled, the IBGP connection will become
disabled as well. However, if you configure the BGP connection on a circuitless
interface, then as long as there is a valid path between the peer routers, the BGP
connection will stay alive.
Using IBGP in Intra-AS Routing
Because situations will arise where OSPF is not the IGP within some autonomous
systems, and because BGP does not interact well with IGP protocols other than
OSPF, Bay Networks implements IBGP intra-AS routing.
With IBGP intra-AS routing, an AS need not propagate BGP routes into the AS.
Instead, all routers in the AS must run IBGP to each border router. The IBGP
information is used in conjunction with the IGP route to the authoring BGP border
router to determine the next hop to use for external networks.
No BGP information is carried by the IGP. Each router uses IBGP exclusively to
determine reachability to external networks. When an IBGP update for a network
is received, it can be passed on to IP for inclusion in the forwarding tables only if
a viable IGP route to the correct border gateway is available.
Configuring BGP Message Logging
Site Manager allows you to control the event messages that BGP sends to the log
file by specifying
• Local and remote address of a peer-to-peer session or sessions
• Message severity level: fault, warning, information, trace, or debug, or all
levels
• BGP message type: Open, Update, Notification, or Keepalive
For instructions on using Site Manager to configure the router for IBGP communications,
see the BGP Intra-AS parameter on page 5-30.
Kommentare zu diesen Handbüchern