
Configuring IP Exterior Gateway Protocols (BGP and EGP)
4-2
308628-15.0 Rev 00
Defining a Peer-to-Peer Session
To define a peer-to-peer session, specify the following:
• Local IP interface address
• Remote IP interface address
• AS number of the autonomous system in which the remote BGP peer is
located
In configurations where BGP speakers reside on routers that have multiple
network connections over multiple IP interfaces (the typical case for IBGP
speakers), consider using the address of the router’s circuitless (virtual) IP
interface as the local peer address. In this way, you ensure that BGP is reachable
as long as there is an active circuit on the router.
If the remote peer is located in a different AS from the local peer, the remote
address must be on the same subnet as the local address. (To override this
restriction, see “
Enabling Multihop Connections” on page 3-13.)
If the local peer
and the remote peer are located in the same AS, BGP assumes that you are
configuring an IBGP session and does not impose this restriction.
You can use the BCC or Site Manager to specify this information.
Using the BCC
To define a peer-to-peer session, go to the BGP prompt (for example,
box; ip;
/jointfilesconvert/97454/bgp
) and enter
:
peer local
<local_address>
remote
<remote_address>
as
<as_number>
local_address
is the IP address of the local interface.
remote_address
is the IP address of the remote interface.
as_number
is the number of the AS in which the remote peer is located.
For example, the following command defines a session with a remote peer in
AS 5. The local IP interface is 2.2.2.2. The interface for the remote peer is 2.2.2.5.
/jointfilesconvert/97454/bgp#
peer local 2.2.2.2 remote 2.2.2.5 as 5
peer/2.2.2.2/2.2.2.5#
Komentáře k této Příručce