Foundry Networks Switch and Router Installation And Configuration Manual page 721

• The first time a route is reflected by a Layer 3 Switch configured as a route reflector, the route reflector adds
the CLUSTER_LIST attribute to the route. Other route reflectors who receive the route from an IBGP
neighbor add their cluster IDs to the front of the route's CLUSTER_LIST. If the route reflector does not have
a cluster ID configured, the Layer 3 Switch adds its router ID to the front of the CLUSTER_LIST.
• If Layer 3 Switch configured as a route reflector receives a route whose CLUSTER_LIST contains the route
reflector's own cluster ID, the route reflector discards the route and does not forward it.
Configuration Procedures
To configure a Foundry Layer 3 Switch to be a BGP4 route reflector, use either of the following methods.
NOTE: All configuration for route reflection takes place on the route reflectors, not on the clients.
USING THE CLI
Enter the following commands to configure a Foundry Layer 3 Switch as route reflector 1 in Figure 19.3 on
page 19-38. To configure route reflector 2, enter the same commands on the Foundry Layer 3 Switch that will be
route reflector 2. The clients require no configuration for route reflection.
BigIron(config-bgp-router)# cluster-id 1
BigIron(config-bgp-router)# neighbor 10.0.1.0 route-reflector-client
BigIron(config-bgp-router)# neighbor 10.0.2.0 route-reflector-client
Syntax: cluster-id <num>
The <num> parameter specifies the cluster ID and can be a number from 1 – 4294967295. The default is the
router ID, expressed as a 32-bit number. You can configure one cluster ID on the router. All route-reflector clients
for the router are members of the cluster.
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.
To add an IBGP neighbor to the cluster, enter the following command:
Syntax: neighbor <ip-addr> route-reflector-client
For more information abut the neighbor command, see "Adding BGP4 Neighbors" on page 19-14.
If you need to disable route reflection between clients, enter the following command. When the feature is
disabled, route reflection does not occur between clients but reflection does still occur between clients and non-
clients.
BigIron(config-bgp-router)# no client-to-client-reflection
Enter the following command to re-enable the feature:
BigIron(config-bgp-router)# client-to-client-reflection
Syntax: [no] client-to-client-reflection
USING THE WEB MANAGEMENT INTERFACE
1. Log on to the device using a valid user name and password for read-write access. The System configuration
panel is displayed.
2. Click on the plus sign next to Configure in the tree view to expand the list of configuration options.
3. Click on the plus sign next to BGP in the tree view to expand the list of BGP option links.
4. Click on the General link to display the BGP configuration panel, shown in Figure 19.2 on page 19-8.
5. If route reflection is not already enabled, select Enable next to Client To Client Reflection.
6. If the autonomous system (AS) the Layer 3 Switch is in will contain more than one route reflector (a route
reflector in addition to the Layer 3 Switch), enter a cluster ID in the Cluster ID field. The cluster ID is required
to avoid loops in an AS that contains more than one route reflector.
December 2000
Configuring BGP4
19 - 39