H3C LS-3100-52P-OVS-H3 Operation Manual - page 711
1-48
Origin : i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 8.1.1.0/24 0.0.0.0 0 0 i
*> 9.0.0.0 3.1.1.1 0 0 65009?
# Use ping for verification.
[SwitchA] ping -a 8.1.1.1 9.1.2.1
PING 9.1.2.1: 56 data bytes, press CTRL_C to break
Reply from 9.1.2.1: bytes=56 Sequence=1 ttl=254 time=15 ms
Reply from 9.1.2.1: bytes=56 Sequence=2 ttl=254 time=31 ms
Reply from 9.1.2.1: bytes=56 Sequence=3 ttl=254 time=47 ms
Reply from 9.1.2.1: bytes=56 Sequence=4 ttl=254 time=46 ms
Reply from 9.1.2.1: bytes=56 Sequence=5 ttl=254 time=47 ms
--- 9.1.2.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 15/37/47 ms
BGP Load Balancing Configuration
Network requirements
As shown in the following figure, all the switches run BGP. Switch A resides in AS 65008, Switch B and
Switch C in AS 65009. Between Switch A and Switch B, Switch A and Switch C are eBGP connections,
and between Switch B and Switch C is an iBGP connection. Two routes are configured on Switch A for
load balancing.
Figure 1-22 Network diagram for BGP load balancing configuration
Vlan-int200
200.1.1.2/24
Switch A
AS 65008
Vlan-int100
8.1.1.1/8
Vlan-int400
9.1.1.2/24
Vlan-int300
200.1.2.1/24
Vlan-int200
200.1.1.1/24
Switch B
Switch C
AS 65009
Vlan-int300
200.1.2.2/24
Vlan-int400
9.1.1.1/24
EBGP
EBGP
IBGP
Configuration procedure
1) Configure IP addresses for interfaces (omitted)
2) Configure BGP connections
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp] router-id 1.1.1.1