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

Configuring IP Exterior Gateway Protocols (BGP and EGP)

5-10

308628-14.00 Rev 00

Allowing Redundant Connections

By default, BGP performs redundancy checking on peer-to-peer TCP sessions.

BGP can maintain only one TCP session with a remote BGP peer. If the remote

peer attempts to establish another session on another physical connection, BGP

rejects the session. BGP uses a collision-detection method based on the router ID

to check for redundant sessions.

The advantage of a peer-to-peer configuration with multiple sessions on multiple

physical connections is redundancy -- if one connection fails, the peers can

communicate over another link. The disadvantage is that such a configuration

results in multiple copies of each route.

You can use the BCC or Site Manager to disable redundancy checking to allow

TCP sessions with the same remote peer on multiple physical connections.

You can also use the BCC to specify the maximum number of redundant routes

that BGP allows. By default, BGP allows up to 255 redundant routes.

Using the BCC

To disable or reenable redundancy checking, navigate to the BGP prompt and

enter:

redundant-connection

state>

state

is one of the following:

enabled

(default)

disabled

To specify the maximum number of redundant routes, navigate to the BGP prompt

and enter:

max-redundant-routes

max_routes>

max_routes

is the maximum number of redundant routes.

For example, the following command disables BGP redundancy checking,

allowing BGP to establish multiple TCP sessions (on different physical

connections) with the same remote peer:

/jointfilesconvert/106988/bgp#

redundant-connection disabled

/jointfilesconvert/106988/bgp#

1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 307 308

Brak uwag

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