Route Confederations - Extreme Networks ExtremeWare XOS Guide Manual

BGP Features
enable ipforwarding vlan to_c1
create vlan to_c2
config vlan to_c2 add port 1:2
config vlan to_c2 ipaddress 30.0.0.2/24
enable ipforwarding vlan to_c2
config bgp router 2.2.2.2
config bgp as-number 100
create bgp neighbor 10.0.0.1 remote-as 100
create bgp neighbor 20.0.0.1 remote-as 100
create bgp neighbor 30.0.0.1 remote-as 100
config bgp neighbor 20.0.0.1 route-reflector-client
config bgp neighbor 30.0.0.1 route-reflector-client
enable bgp neighbor all
enable bgp
To configure router 3.3.3.3, use the following commands:
create vlan to_rr
config vlan to_rr add port 1:1
config vlan to_rr ipaddress 20.0.0.1/24
enable ipforwarding vlan to_rr
config bgp router 3.3.3.3
config bgp as-number 100
create bgp neighbor 20.0.0.2 remote-as 100
enable bgp neighbor all
enable bgp
To configure router 4.4.4.4, use the following commands:
create vlan to_rr
config vlan to_rr add port 1:1
config vlan to_rr ipaddress 30.0.0.1/24
enable ipforwarding vlan to_rr
config bgp router 4.4.4.4
config bgp as-number 100
create bgp neighbor 30.0.0.2 remote-as 100
enable bgp neighbor all
enable bgp

Route Confederations

BGP requires networks to use a fully-meshed router configuration. This requirement does not scale well,
especially when BGP is used as an interior gateway protocol. One way to reduce the size of a
fully-meshed AS is to divide the AS into multiple sub-autonomous systems and group them into a
routing confederation. Within the confederation, each sub-AS must be fully-meshed. The confederation is
advertised to other networks as a single AS.
ExtremeWare XOS 10.1 Concepts Guide 207