NOTE
Another way to reduce the complexity of an IBGP mesh is to use route reection. However, if you want to run dierent Interior
Gateway Protocols (IGPs) within an AS, you must congure a confederation. You can run a separate IGP within each sub-AS.
To congure a confederation, congure groups of BGP4 devices into sub-autonomous systems. A sub-AS is simply an AS. The term
"sub-AS" distinguishes autonomous systems within a confederation from autonomous systems that are not in a confederation. For the
viewpoint of remote autonomous systems, the confederation ID is the AS ID. Remote autonomous systems do not know that the AS
represents multiple sub-autonomous systems with unique AS IDs.
NOTE
You can use any valid AS numbers for the sub-autonomous systems. If your AS is connected to the Internet, Brocade
recommends that you use numbers from within the private AS range (64512 through 65535). These are private autonomous
system numbers and BGP4 devices do not propagate these AS numbers to the Internet.
FIGURE 32 Example BGP4 confederation
In this example, four devices are congured into two sub-autonomous systems, each containing two of the devices. The sub-
autonomous systems are members of confederation 10. Devices within a sub-AS must be fully meshed and communicate using IBGP.
In this example, devices A and B use IBGP to communicate. devices C and D also use IBGP. However, the sub-autonomous systems
communicate with one another using EBGP. For example, device A communicates with device C using EBGP. The devices in the
confederation communicate with other autonomous systems using EBGP.
Devices in other autonomous systems are unaware that devices A through D are congured in a confederation. In fact, when devices in
confederation 10 send trac to devices in other autonomous systems, the confederation ID is the same as the AS number for the
Optional BGP4 conguration tasks
FastIron Ethernet Switch Layer 3 Routing
392 53-1003627-04
To Next Page
Loading...
Need help?
General
