The reflector cluster-id command sets a cluster ID for an RR.
The undo reflector cluster-id command restores the default setting.
By default, each RR uses its router ID as the cluster ID.
| Parameter | Description | Value |
|---|---|---|
| cluster-id | Specifies the cluster ID of an RR. | The value can be an integer that ranges from 1 to 4294967295 or in the format of an IPv4 address. |
BGP view, BGP-IPv4 unicast address family view, BGP-IPv4 multicast address family view, BGP-VPN instance IPv4 address family view, BGP-VPNv4 address family view, BGP-IPv6 unicast address family view, BGP-VPN instance IPv6 address family view, BGP-VPNv6 address family view, BGP-VPLS address family view, BGP-L2VPN address family view, BGP L2VPN-AD address family view, BGP-EVPN address family view
Usage Scenario
Sometimes, more than one 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.
Precautions
If the reflector cluster-id command is run several times, the latest configuration overrides the previous one.
The reflector cluster-id command is run only on RRs.
To enable clients to receive routes reflected by RRs, ensure that the cluster ID of the RRs is different from the router ID of any client. If the cluster ID of the RRs is the same as the router ID of a client, the client will discard received routes.