NOTE
All conguration for route reection takes place on the route reectors, not on the
clients.
Enter the following commands to congure a Brocade device as route reector 1. To congure route reector 2, enter the same
commands on the device that will be route reector 2. The clients require no conguration for route reection.
device(config-bgp)# cluster-id 1
Syntax: [no] cluster-id num | ip-addr
The num and ip-addr parameters specify the cluster ID and can be a number from 1 - 4294967295, or an IP address. The default is
the device ID. You can
congure one cluster ID on the device. All route-reector clients for the device are members of the cluster.
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.
To add an IBGP neighbor to the cluster, enter the following command:
device(config-bgp)# neighbor 10.0.1.0 route-reflector-client
Syntax: [no] neighbor ip-addr route-reector-client
Disabling or re-enabling client-to-client route reection
By default, the clients of a route reector are not required to be fully meshed. Routes from a client are reected to other clients. However,
if the clients are fully meshed, route reection is not required between clients.
If you need to disable route reection between clients, enter the no client-to-client-reection command. When this feature is disabled,
route reection does not occur between clients does still occur between clients and non-clients.
device(config-bgp-router)# no client-to-client-reflection
Enter the following command to re-enable the feature.
device(config-bgp)# client-to-client-reflection
Syntax: [no]
client-to-client-reection
Conguring confederations
A confederation is a BGP4 Autonomous System (AS) that has been subdivided into multiple, smaller autonomous systems. Subdividing
an AS into smaller autonomous systems simplies administration and reduces BGP4-related trac, which in turn reduces the complexity
of the Interior Border Gateway Protocol (IBGP) mesh among the BGP4 devices in the AS.
The Brocade implementation of this feature is based on RFC 3065.
Normally, all BGP4 devices within an AS must be fully meshed, so that each BGP4 device has BGP4 sessions to all the other BGP4
devices within the AS. This is feasible in smaller autonomous systems, but becomes unmanageable in autonomous systems containing
many BGP4 devices.
When you congure BGP4 devices into a confederation, all the devices within a sub-AS (a subdivision of the AS) use IBGP and must be
fully meshed. However, devices use EBGP to communicate between dierent sub-autonomous systems.
Optional BGP4 conguration tasks
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04 391
To Next Page
Loading...
Need help?
General
