HPE 5800 Series Configuration Manual page 239

[SwitchC-bgp] router-id 3.3.3.3
[SwitchC-bgp] peer 10.220.2.217 as-number 64631
[SwitchC-bgp] import-route ospf
# Enable BGP, and configure Switch C as an EBGP peer on Switch D.
[SwitchD] bgp 64631
[SwitchD-bgp] router-id 4.4.4.4
[SwitchD-bgp] peer 10.220.2.16 as-number 65106
[SwitchD-bgp] quit
# Display IP routing table on Switch D.
[SwitchD] display ip routing-table
Routing Tables: Public
Destinations : 8
Destination/Mask
4.4.4.4/32
10.220.2.0/24
10.220.2.217/32
127.0.0.0/8
127.0.0.1/32
192.168.64.0/24
192.168.74.0/24
192.168.99.0/24
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 via 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.
Configure route summarization on Switch C to summarize 192.168.64.0/24, 192.168.74.0/24,
5.
and 192.168.99.0/24 into a single route 192.168.64.0/18, and disable advertisement of the
specific routes.
[SwitchC-bgp] aggregate 192.168.64.0 18 detail-suppressed
[SwitchC-bgp] quit
Verify the configuration:
6.
# Display IP routing table on Switch C.
[SwitchC] display ip routing-table
Routing Tables: Public
Destinations : 11
Destination/Mask
3.3.3.3/32
10.220.2.0/24
10.220.2.16/32
127.0.0.0/8
127.0.0.1/32
172.17.100.0/24
172.17.100.2/32
192.168.64.0/18
Routes : 8
Proto Pre Cost
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
BGP 255 1
BGP 255 1
BGP 255 1
Routes : 11
Proto Pre Cost
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
BGP 130 0
228
NextHop Interface
127.0.0.1 InLoop0
10.220.2.217 Vlan200
127.0.0.1 InLoop0
127.0.0.1 InLoop0
127.0.0.1 InLoop0
10.220.2.16 Vlan200
10.220.2.16 Vlan200
10.220.2.16 Vlan200
NextHop Interface
127.0.0.1 InLoop0
10.220.2.16 Vlan200
127.0.0.1 InLoop0
127.0.0.1 InLoop0
127.0.0.1 InLoop0
172.17.100.2 Vlan100
127.0.0.1 InLoop0
127.0.0.1 NULL0