I have gone thru the below command while reading
"no bgp client-to-client reflection"
It is mentioned that this command will be configured in the RR for disabling
the client to client route advertisement, if clients are fully meshed.
My question is "If the clients are fully meshed then what is the need of
Can you please take your few minutes and help me ?
>> My question is "If the clients are fully meshed then what is the need of
the RRS can still be useful to reflect routes coming from non-clients = other RRS clusters for example.
This is a way to save iBGP sessions those between clients and all non-clients.
the option is available to avoid to send BGP advertisements that would be considered worst then direct advertisement (for the cluster-list and cluster-id that are missing on direct client to client advertisement).
To be honest in networks I've worked on this option is not used.
Another possible option is to have multiple levels of route reflection this can be used for scalability.
The challenge in service provider networks is given by the number of routes to be handled.
For example, in a service provider network it is possible to deploy a group of RRS for address-family ipv4 unicast (global routing table) and a different set of RRS for vpnv4 routes.
It is even possible that vpnv4 routes space is divided into two or more parts that are managed by different meshs of RRS.
Hope to help