The Reflector Route types are configured in the web UI to define what the “peer” iBGP router is in relationship to the local router. The supported peer types are:
iBGP peer must be fully meshed. When the Route Reflector sees a route from the Non-Client, it must reflect to all clients.
iBGP peer is only connected to the Route Reflector (not fully meshed).
A route seen from this client type is reflected to all the Non-Client peers and also the Client peers.
iBGP peer is a reflector client and it is fully meshed with all other reflector clients.
Routes received from a meshed client are reflected to all neighbors except for other meshed-client iBGP peers.
A fundamental point in Route Reflector is the loop avoidance. In RR there are 2 attribute for this:
Ensure that both are configured in the BGP tab on the web UI. The Router ID field is for Originator-ID and Reflector Cluster ID is for the Cluster ID:
If the firewall is acting as the Route Reflector, make sure that the peers are defined properly by navigating to Network > Virtual-Routers. Then, click open the intended Virtual Router and go to BGP >Peer Group > Peer > Reflector Client :