Accton Technology ES4626 - Manual (Page 569)

569
SwitchD(config-router-bgp)#exit
Presently, the connection between SwitchB and SwitchA is EBGP, and other
connections with SwitchC and SwitchD are IBGP. SwitchB and SwitchD may have BGP
connection without physical connection. But there is a precondition that these two
switches must have reachable route to each other. This route can be attained through
static route or IGP.
13.8.4.2 Examples 2: configure BGP aggregation
In this sample, configure route aggregation. Firstly, enable command redistribute to
redistribute static route to BGP route table:
SwitchB(config)#ip route 193.0.0.0/24 11.1.12
SwitchB(config)#router bgp 100
SwitchB(config-router-bgp)#redistribute static
When there is at least one route affiliated to the specified range, the following
configuration will create an aggregation route in the BGP route table. The aggregation
route will be regarded as the AS from itself. More detailed route information about
193.0.0.0 will be announced.
SwitchB(config#router bgp 100
SwitchB(config-router-bgp)#aggregate 193.0.0.0/24
At the same time, the aggregation command above can be modified as following,
then this switch only announce aggregation route 193.0.0.0 and forbid to announce more
specified route to all the neighbors.
SwitchB(config-router-bgp)#aggregate 193.0.0.0/24 summary-only
13.8.4.3 Examples 3: configure BGP community attributes
In the following sample, “route map set-community” is used for the outgoing update
to neighbor 16.1.1.6. By accessing to route in table 1 to configure special community
value to “1111”, other can be announced normally.
Switch(config)#router bgp 100
Switch(config-router-bgp)#neighbor 16.1.1.6 remote-as 200
Switch(config-router-bgp)#neighbor 16.1.1.6 route-map set-community out
Switch(config-router-bgp)#exit
Switch(config)#route-map set-community permit 10
Switch(config-route-map)#match address 1
Switch(config-route-map)#set community 1111
Switch(config-route-map)#exit
Switch(config)#route-map set-community permit 20