Update group for IPv4 Unicast, index 0.2:
Attributes:
Minimum advertisement interval:30
Messages formatted:2, replicated:2
Neighbors in this update group:
10.0.101.91
BGP Neighbor Configuration: Example
The following example shows how BGP neighbors on an autonomous system are configured to share
information. In the example, a BGP router is assigned to autonomous system 109, and two networks are listed
as originating in the autonomous system. Then the addresses of three remote routers (and their autonomous
systems) are listed. The router being configured shares information about networks 172 .16 .0.0 and 192.168
.7.0 with the neighbor routers. The first router listed is in a different autonomous system; the second neighbor
and remote-as commands specify an internal neighbor (with the same autonomous system number) at address
172 .26 .234.2; and the third neighbor and remote-as commands specify a neighbor on a different autonomous
system.
route-policy pass-all
pass
end-policy
router bgp 109
address-family ipv4 unicast
network 172.16.0.0 255.255.0.0
network 192.168.7.0 255.255.0.0
neighbor 172.16.200.1
remote-as 167
exit
address-family ipv4 unicast
route-policy pass-all in
route-policy pass-out out
neighbor 172.26.234.2
remote-as 109
exit
address-family ipv4 unicast
neighbor 172.26.64.19
remote-as 99
exit
address-family ipv4 unicast
route-policy pass-all in
route-policy pass-all out
BGP Confederation: Example
The following is a sample configuration that shows several peers in a confederation. The confederation consists
of three internal autonomous systems with autonomous system numbers 6001, 6002, and 6003. To the BGP
speakers outside the confederation, the confederation looks like a normal autonomous system with autonomous
system number 666 (specified using the bgp confederation identifier command).
In a BGP speaker in autonomous system 6001, the bgp confederation peers command marks the peers from
autonomous systems 6002 and 6003 as special eBGP peers. Hence, peers 171.16 .232.55 and 171.16 .232.56
get the local preference, next hop, and MED unmodified in the updates. The router at 171 .19 .69.1 is a normal
eBGP speaker, and the updates received by it from this peer are just like a normal eBGP update from a peer
in autonomous system 666.
router bgp 6001
bgp confederation identifier 666
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
OL-30423-03 161
Implementing BGP
BGP Neighbor Configuration: Example
To Next Page
Loading...
Need help?
General
