The reflector cluster-id command sets the cluster ID of the route reflectors.
The undo reflector cluster-id command removes the cluster ID of the route reflectors.
By default, each route reflector uses its router ID as the cluster ID.
| Parameter | Description | Value |
|---|---|---|
cluster-id |
Specifies the cluster ID of the route reflector. |
The value can be an integer ranging from 1 to 4294967295. It can also be identified in the IPv4 address format. |
BGP view, BGP-IPv4 unicast address family view, BGP-IPv6 unicast address family view, BGP-VPNv4 address family view, BGP-VPN instance IPv4 address family view, BGP-VPN instance IPv6 address family view, BGP-VPN-Target address family view
Usage Scenario
Sometimes, more than one route reflector (RR) needs to be configured in a cluster to improve network reliability and prevent single-point failures. If a cluster has more than one RR, the reflector cluster-id command needs to be used to set the same cluster ID for the RRs. This helps to identify the cluster and avoid routing loops.
Configuring an RR allows IBGP peers to advertise routes learned in the local AS to each other. The Cluster_List attribute is introduced to avoid loops within an AS. The Cluster_List is composed of a series of Cluster_IDs. It records all the RRs through which a route passes.
Configuration Impact
If the reflector cluster-id command is run several times, the latest configuration overrides the previous one.
Precautions
To ensure that a client can learn the routes reflected by an RR, the Cluster ID configured on the RR must be different from the Cluster ID of the client (By default, the client uses its Router ID as the cluster ID). If the Cluster ID is the same as the Cluster ID of the client, the client discards received routes.