Brocade FastIron Ethernet Switch Layer 3 Routing Configuration Guide - Manual (Page 426)

Disabling or re-enabling client-to-client route reflection
By default, the clients of a route reflector are not required to be fully meshed. Routes from a client are
reflected to other clients. However, if the clients are fully meshed, route reflection is not required
between clients.
If you need to disable route reflection between clients, enter the no client-to-client-reflection
command. When this feature is disabled, route reflection 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-reflection
Configuring 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 simplifies administration
and reduces BGP4-related traffic, 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 configure 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 different sub-autonomous systems.
NOTE
Another way to reduce the complexity of an IBGP mesh is to use route reflection. However, if you want
to run different Interior Gateway Protocols (IGPs) within an AS, you must configure a confederation.
You can run a separate IGP within each sub-AS.
To configure a confederation, configure groups of BGP4 devices into sub-autonomous systems. A
sub-AS is simply an AS. The term "sub-AS" distinguishes autonomous systems within a confederation
from autonomous systems that are not in a confederation. For the viewpoint of remote autonomous
systems, the confederation ID is the AS ID. Remote autonomous systems do not know that the AS
represents multiple sub-autonomous systems with unique AS IDs.
NOTE
You can use any valid AS numbers for the sub-autonomous systems. If your AS is connected to the
Internet, Brocade recommends that you use numbers from within the private AS range (64512 through
65535). These are private autonomous system numbers and BGP4 devices do not propagate these
AS numbers to the Internet.
Disabling or re-enabling client-to-client route reflection
426 FastIron Ethernet Switch Layer 3 Routing Configuration Guide
53-1003087-04