H3C Technologies H3C S12500-X Series Switches - Manual (Page 268)

254
192.168.99.0/24 BGP 255 1 10.220.2.16 Vlan200
BGP Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch D has learned routes to 192.168.64.0/24, 192.168.74.0/24, and
192.168.99.0/24 through BGP.
After the above configurations, ping hosts on networks 192.168.74.0/24, 192.168.99.0/24,
and 192.168.64.0/18 from Switch D. The ping operations succeed.
5. Configure route summarization on Switch C to summarize 192.168.64.0/24,
192.168.74.0/24, and 192.168.99.0/24 into a single route 192.168.64.0/18 on Switch C,
and disable advertisement of the specific routes.
[SwitchC-bgp-ipv4] aggregate 192.168.64.0 18 detail-suppressed
[SwitchC-bgp-ipv4] quit
[SwitchC-bgp] quit
613B
Verifying the configuration
# Display IP routing table on Switch C.
[SwitchC] display ip routing-table | include 192.168
192.168.64.0/18 BGP 130 0 127.0.0.1 NULL0
192.168.64.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.74.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.99.0/24 OSPF 150 1 172.17.100.1 Vlan100
The output shows that Switch C has a summary route 192.168.64.0/18 with the output interface Null0.
# Display IP routing table on Switch D.
[SwitchD] display ip routing-table protocol bgp
Summary Count : 1
BGP Routing table Status : <Active>
Summary Count : 1
Destination/Mask Proto Pre Cost NextHop Interface
192.168.64.0/18 BGP 255 0 10.220.2.16 Vlan200
BGP Routing table Status : <Inactive>
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.
342B
BGP load balancing configuration example
614B
Network requirements
As shown in
1161H
Figure 62 , 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.