F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Appendix Protocol Reference-6PW100

40
information received from a client to other clients. In this way, all clients can receive routing
information from one another without establishing BGP sessions.
A router that is neither a route reflector nor a client is a non-client, which, as shown in Figure 29
must e
stablish BGP sessions to the route reflector and other non-clients.
Figure 29 Network diagram for a route reflector
The route reflector and clients form a cluster. Typically a cluster has one route reflector. The ID of
the route reflector is the Cluster_ID. You can configure more than one route reflector in a cluster to
improve availability as shown in Figure 30. The confi
gured route reflectors must have the same
Cluster_ID to avoid routing loops.
Figure 30 Network diagram for route reflectors
When the BGP routers in an AS are fully meshed, route reflection is unnecessary because it
consumes more bandwidth resources. You can use commands to disable route reflection instead of
modifying network configuration or changing network topology.
After route reflection is disabled between clients, routes can still be reflected between a client and
a non-client.
• Confederation
Confederation is another method to manage growing IBGP connections in an AS. It splits an AS
into multiple sub-ASs. In each sub-AS, IBGP peers are fully meshed. As shown in Figure 31,
intra-confed
eration EBGP connections are established between sub-Ass in AS 200.