Avaya Configuring IP Exterior Gateway Protocols (BGP and EGP) Instrukcja Użytkownika Pobierz pdf (Strona 96)

Configuring IP Exterior Gateway Protocols (BGP and EGP)

6-2

308628-14.00 Rev 00

Defining a Peer-to-Peer Session

To define a peer-to-peer session, you 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 situations 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 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 5-11

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 supply this information.

Using the BCC

Navigate to the BGP prompt and enter:

peer local

<local_address>

remote

<remote_address>

<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/106988/bgp#

peer local 2.2.2.2 remote 2.2.2.5 as 5

peer/2.2.2.2/2.2.2.5/5#

1 2 ... 91 92 93 94 95 96 97 98 99 100 101 ... 307 308

Brak uwag

Avaya Configuring IP Exterior Gateway Protocols (BGP and EGP) Instrukcja Użytkownika Strona 96