To help solve BGP scaling problems caused by the IBGP full-mesh requirement, you can divide your AS into sub-ASs called confederations. As Figure 81 shows, the connections between the sub-ASs are made through EBGP sessions, and the internal connections are made through standard IBGP sessions.
In the sample network, AS 17 has two separate confederations (sub-AS 64512 and sub-AS 64513), each of which has multiple routers. Within a sub-AS, an IGP (OSPF, for example) is used to establish network connectivity with internal peers. Between sub-ASs, an external BGP peering session is established.
Figure 81: Typical Network Using BGP Confederations
To configure the BGP confederations shown in Figure 81:
Table 140: Configuring BGP Confederations
Task |
J-Web Configuration Editor |
CLI Configuration Editor |
---|---|---|
Navigate to the Routing options level in the configuration hierarchy. |
|
From the [edit] hierarchy level, enter edit routing-options |
Set the AS number to the sub-AS number 64512. The sub-AS number is a unique AS number that is usually taken from the pool of private AS numbers—64512 through 65535. |
|
Set the sub-AS number: set autonomous-system 64512 |
Navigate to the Confederation level in the configuration hierarchy. |
|
From the [edit] hierarchy level, enter edit routing-options confederation |
Set the confederation number to the AS number 17. |
In the Confederation as box, enter 17. |
Set the confederation AS number: set 17 |
Add the sub-ASs as members of the confederation. Every sub-AS within the AS must be added as a confederation member. |
|
Add members to the confederation: set 17 members 64512 64513 |
Using EBGP, configure the peering session between the confederations (from Router A to Router B in this example). When setting the peer AS number for these sessions, use the sub-AS number rather than the AS number. | ||
Using IBGP, configure internal sessions within a sub-AS. You can configure an IBGP full mesh, or you can configure a route reflector. |
|