Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 102)

74 Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Configuring route reflection parameters
NOTE
If the cluster contains more than one route reflector, you need to configure the same cluster ID
on all the route reflectors in the cluster. The cluster ID helps route reflectors avoid loops within
the cluster.
• A route reflector is an IGP device configured to send BGP4 route information to all the clients
(other BGP4 devices) within the cluster. Route reflection is enabled on all BGP4 devices by
default but does not take effect unless you add route reflector clients to the device.
• A route reflector client is an IGP device identified as a member of a cluster. You identify a
device as a route reflector client on the device that is the route reflector, not on the client. The
client itself requires no additional configuration. In fact, the client does not know that it is a
route reflector client. The client just knows that it receives updates from its neighbors and does
not know whether one or more of those neighbors are route reflectors.
NOTE
Route reflection applies only among IBGP devices within the same AS. You cannot configure a cluster
that spans multiple ASs.
Figure 7 shows an example of a route reflector configuration. In this example, two devices are
configured as route reflectors for the same cluster, which provides redundancy in case one of the
reflectors becomes unavailable. Without redundancy, if a route reflector becomes unavailable, the
clients for that router are cut off from BGP4 updates.
AS1 contains a cluster with two route reflectors and two clients. The route reflectors are fully
meshed with other BGP4 devices, but the clients are not fully meshed and rely on the route
reflectors to propagate BGP4 route updates.
FIGURE 7 A route reflector configuration