To do...
or peer group
Apply a routing policy to routes advertised to a
peer or peer group
Configuring a BGP route reflector
If an AS has many BGP routers, you can configure them as a cluster by configuring one of them as a route
reflector and others as clients to reduce iBGP connections.
To enhance network reliability and prevent single point of failure, specify multiple route reflectors for a
cluster. The route reflectors in the cluster must have the same cluster ID to avoid routing loops.
Follow these steps to configure a BGP route reflector:
To do...
Enter system view
Enter BGP view
Configure the router as a route
reflector and specify a peer or peer
group as its client
Enable route reflection between
clients
Configure the cluster ID of the route
reflector
CAUTION:
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, disable route reflection between clients to reduce
routing costs.
Generally, 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. To avoid routing loops, specify the same
cluster ID for these route reflectors by using the reflector cluster-id command.
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, use the confederation nonstandard
command to make the local router compatible with these routers.
Advertise the extended
community attribute to a
peer or peer group
Use the command...
system-view
bgp as-number
peer { group-name | ip-address }
reflect-client
reflect between-clients
reflector cluster-id cluster-id
Use the command...
peer { group-name | ip-address }
advertise-ext-community
peer { group-name | ip-address }
route-policy route-policy-name export
227
Remarks
default.
Required
Not configured by
default.
Remarks
—
—
Required
Not configured by default.
Optional
Enabled by default
Optional
By default, a route reflector uses its
router ID as the cluster ID.