236
Summary Count : 0
The output shows that Switch D has only one route 192.168.64.0/18 to AS 65106.
After the above configurations, ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24 and
192.168.99.0/24 from Switch D. The ping operations succeed.
BGP load balancing configuration example
Network requirements
As shown in Figure 60, run EBGP between Switch A and Switch B and between Switch A and Switch C.
Run IBGP between Switch B and Switch C. Configure load balancing over the two EBGP links on Switch
A.
Figure 60 Network diagram
Configuration considerations
On Switch A, establish EBGP connections with Switch B and Switch C. Configure BGP to advertise
network 8.1.1.0/24 to Switch B and Switch C, so that Switch B and Switch C can access the internal
network connected to Switch A.
On Switch B, establish an EBGP connection with Switch A and an IBGP connection with Switch C.
Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet
through Switch B. Configure a static route to interface loopback 0 on Switch C (or use a routing protocol
like OSPF) to establish the IBGP connection.
On Switch C, establish an EBGP connection with Switch A and an IBGP connection with Switch B.
Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet
through Switch C. Configure a static route to interface loopback 0 on Switch B (or use another protocol
like OSPF) to establish the IBGP connection.
Configure load balancing on Switch A.
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure BGP connections:
# Configure Switch A.