Avaya Configuring IP Services Instrukcja Użytkownika Strona 287

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 650
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 286
Configuring and Customizing BGP
303528-A Rev 00
8-19
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
Navigate to the BGP prompt and enter:
redundant-connection
state
max-redundant-routes
max_routes
state is one of the following:
enabled
(default)
disabled
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/92449/bgp# redundant-connection disabled
/jointfilesconvert/92449/bgp#
The following command configures BGP to allow up to 50 redundant routes:
/jointfilesconvert/92449/bgp# max-redundant-routes 50
/jointfilesconvert/92449/bgp#
Przeglądanie stron 286
1 2 ... 282 283 284 285 286 287 288 289 290 291 292 ... 649 650

Komentarze do niniejszej Instrukcji

Brak uwag