for route reection takes place on the route reectors. Clients are unaware that they are members of a route reection cluster. All
members of the cluster must be in the same AS. The cluster ID can be any number from 1 - 4294967295, or an IP address.
The default is the device ID expressed as a 32-bit number.
NOTE
If the cluster contains more than one route reector, you need to congure the same cluster ID on all the route reectors in the
cluster. The cluster ID helps route reectors avoid loops within the cluster.
• A route reector is an IGP device congured to send BGP4 route information to all the clients (other BGP4 devices) within the
cluster. Route reection is enabled on all BGP4 devices by default but does not take eect unless you add route reector clients
to the device.
• A route reector client is an IGP device identied as a member of a cluster. You identify a device as a route reector client on the
device that is the route reector, not on the client. The client itself requires no additional conguration. In fact, the client does not
know that it is a route reector 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 reectors.
NOTE
Route reection applies only among IBGP devices within the same AS. You cannot congure a cluster that spans multiple
autonomous systems.
This is an example of a route reector conguration. In this example, two devices are congured as route reectors for the same cluster,
which provides redundancy in case one of the reectors becomes unavailable. Without redundancy, if a route reector becomes
unavailable, the clients for that device are cut o from BGP4 updates.
AS1 contains a cluster with two route reectors and two clients. The route reectors are fully meshed with other BGP4 devices, but the
clients are not fully meshed and rely on the route reectors to propagate BGP4 route updates.
Optional BGP4 conguration tasks
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04 389