
Configuring Route and Traffic-Load Balancing
308628-14.00 Rev 00
9-7
Now assume that the local EBGP speaker has received from its remote peer
advertisements for routes to three destinations: destination_1, destination_2, and
destination_3.
If you configure the local EBGP speaker for ECMP route balancing, BGP submits
one BGP route to the routing table for each BGP destination, using in turn
(round-robin) the available ECMP routes, as follows:
1.
BGP submits a BGP route to destination_1 and specifies interface 1 as the
next hop.
2.
BGP submits a BGP route to destination_2 and specifies interface 2 as the
next hop.
3.
BGP submits a BGP route to destination_3 and specifies interface 1 as the
next hop.
If you configure EBGP for traffic balancing, BGP submits multiple BGP routes,
one for each static ECMP route, in the following manner:
1.
BGP submits two routes to destination_1. One route specifies interface 1; the
second route specifies interface 2.
2.
BGP submits two IP routes to destination_2. One route specifies interface 1;
the second route specifies interface 2.
3.
BGP submits two IP routes to destination_3. One route specifies interface 1;
the second route specifies interface 2.
You can use the BCC or Site Manager to configure EBGP ECMP for route
balance and traffic load balance.
Using the BCC
Navigate to the BGP prompt and choose a peer to modify. Enter:
e/jointfilesconvert/106988/bgp-ecmp-method <
method>
method
is one of the values shown in Table 9-2.
Komentarze do niniejszej Instrukcji