Configures a BGP neighbor to be a route reflector client.
| remoteaddr | Specifies the IPv4 or IPv6 address of a BGP neighbor. |
| all | Specifies all IPv4 and IPv6 neighbors. |
| route-reflector-client | Specifies for the BGP neighbor to be a route reflector client. |
| no-route-reflector-client | Specifies for the BGP neighbor not to be a route reflector client. |
N/A.
Another way to overcome the difficulties of creating a fully-meshed AS is to use route reflectors. Route reflectors allow a single router to serve as a central routing point for the AS or sub-AS.
Use this command to implicitly define the router to be a route reflector. The neighbor must be in the same AS as the router.
This command applies to the current VR or VRF context.
When changing the route reflector status of a peer, the peer is automatically disabled and re-enabled and a warning message appears on the console and in the log.
A cluster is formed by the route reflector and its client routers. Peer routers that are not part of the cluster must be fully meshed according to the rules of BGP.
The following command configures a BGP neighbor to be a route reflector client:
configure bgp neighbor 192.168.1.5 route-reflector-client
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
Support for IPv6 was added in ExtremeXOS 12.6 BGP.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the BGP feature, see the Switch Engine 32.2 Feature License Requirements document.