BGP4+ route reflection

A BGP device can act as a route-reflector client or as a route reflector. You can configure a BGP peer as a route-reflector client from the device that is going to reflect the routes and act as the route reflector using the neighbor route-reflector-client command.

When there is more than one route reflector, they should all belong to the same cluster. By default, the value for cluster-id is used as the device ID. The device ID can be changed using the cluster-id command.

The route-reflector server reflects the routes as follows:

• Routes from the client are reflected to the client as well as to nonclient peers.
• Routes from nonclient peers are reflected only to client peers.

If route-reflector clients are connected in a full IBGP mesh, you can disable client-to-client reflection on the route reflector using the no client-to-client-reflection command.

A BGP device advertises only those routes that are preferred ones and are installed into the Routing Table Manager (RTM). When a route cannot be installed into the RTM because the routing table is full, the route reflector may not reflect that route. In cases where the route reflector is not placed directly in the forwarding path, you can configure the route reflector to reflect routes even though those routes are not in the RTM using the always-propagate command.