Configuring A Bgp Confederation - H3C S5800 Series Configuration Manual

In general, it is not required to make clients of a route reflector fully meshed. The route reflector
forwards routing information between clients. If clients are fully meshed, you can disable route
reflection between clients to reduce routing costs.
In general, a cluster has only one route reflector, and the router ID is used to identify the cluster.
You can configure multiple route reflectors to improve network stability. In this case, you need to
specify the same cluster ID for these route reflectors using the reflector cluster-id command to
avoid routing loops.

Configuring a BGP Confederation

Configuring a BGP confederation is another way for reducing iBGP connections in an AS.
A confederation contains sub ASs. In each sub AS, iBGP peers are fully meshed. Between sub ASs,
eBGP connections are established.
If routers not compliant with RFC 3065 exist in the confederation, you can use the confederation
nonstandard command to make the local router compatible with these routers.
Configure a BGP confederation
After you split an AS into multiple sub ASs, you can configure a router in a sub AS in the following way:
1) Enable BGP and specify the AS number of the router.
2) Specify the confederation ID. From an outsider's perspective, the sub ASs of the confederation is
a single AS, which is identified by the confederation ID.
3) If the router needs to establish eBGP connections to other sub ASs, you need to specify the
peering sub ASs in the confederation.
A confederation contains 32 sub ASs at most. The AS number of a sub AS is effective only in the
confederation.
Follow these steps to configure a BGP confederation:
Enter system view
Enter BGP view
Configure a confederation ID
Specify peering sub ASs in the confederation
To do... Use the command...
system-view
bgp as-number
confederation id as-number
confederation peer-as
as-number-list
6-44
Remarks
—
—
Required
Not configured by
default.
Required
Not configured by
default.