Configuring BGP4
Figure 10.4 shows an example of a BGP4 confederation.
Confederation 10 |
| AS 20 | |
|
| ||
IBGP |
|
| |
Router A | Router B |
| |
|
| EBGP | |
EBGP |
|
| |
| This BGP4 router sees all | ||
|
| ||
|
| traffic from Confederation 10 | |
IBGP |
| as traffic from AS 10. | |
|
| ||
|
| Routers outside the confederation | |
|
| do not know or care that the routers | |
Router C | Router D | are subdivided into | |
confederation. | |||
|
|
Figure 10.4 Example BGP4 confederation
In this example, four routing switches are configured into two
Routers in other ASs are unaware that routers A – D are configured in a confederation. In fact, when routers in confederation 10 send traffic to routers in other ASs, the confederation ID is the same as the AS number for the routers in the confederation. Thus, routers in other ASs see traffic from AS 10 and are unaware that the routers in AS 10 are subdivided into
Configuring a BGP Confederation
Perform the following configuration tasks on each BGP router within the confederation:
•Configure the local AS number. The local AS number indicates membership in a
•Configure the confederation ID. The confederation ID is the AS number by which BGP routers outside the confederation know the confederation. Thus, a BGP router outside the confederation is not aware and does not care that your BGP routers are in multiple
•Configure the list of the
To configure a routing switch to be a member of a BGP confederation, use one of the following methods. The procedures show how to implement the example confederation shown in Figure 10.4.
10 - 37