To ensure the connectivity between IBGP peers within an AS, you need to establish full-mesh connections between the IBGP peers. When there are many IBGP peers, it is costly to establish a fully-meshed network. A route reflector (RR) can solve this problem.

A cluster ID can help prevent routing loops between multiple RRs within a cluster and between clusters. When a cluster has multiple RRs, the same cluster ID must be configured for all the RRs within the cluster.

Enabling Route Reflector

The following example configures the local device Switch1 as the route reflector and the peer Switch2 as the client of the route reflector. No configuration is required on the client.

admin@XorPlus# set protocols bgp neighbor 2.2.2.2 ipv4-unicast route-reflector-client
admin@XorPlus# commit

Configuring Cluster ID

The following example configures a cluster ID for the RR. By default, each RR uses its router ID as the cluster ID.

admin@XorPlus# set protocols bgp cluster-id 100.100.100.100
admin@XorPlus# commit

Browser not supported