Administrator Guide

Usage
Information
When a BGP cluster contains only one route reflector, the cluster ID is the route reflector’s router ID. For
redundancy, a BGP cluster may contain two or more route reflectors. Assign a cluster ID with the bgp
cluster-id command. Without a cluster ID, the route reflector cannot recognize route updates from
the other route reflectors within the cluster.
The default format for displaying the cluster-id is dotted decimal, but if you enter the cluster-id as an
integer, it is displayed as an integer.
This command automatically restarts the BGP instance for the configuration to take effect.
Related
Commands
bgp client-to-client reflection — enables route reflection between the route reflector and clients.
neighbor route-reflector-client — configures a route reflector and clients.
show ip bgp cluster-list — views paths with a cluster ID.
bgp confederation identifier
Configure an identifier for a BGP confederation.
Z9000
Syntax
bgp confederation identifier as-number
To delete a BGP confederation identifier, use the no bgp confederation identifier as-
number command.
Parameters
as-number Enter the AS number. The range is from 0 to 65535 (2 byte), from 1 to
4294967295 (4 byte), or from 0.1 to 65535.65535 (dotted format).
Defaults Not configured.
Command Modes ROUTER BGP
Command
History
This guide is platform-specific. For command information about other platforms, refer to the relevant Dell
Networking OS Command Line Reference Guide.
The following is a list of the Dell Networking OS version history for this command.
Version Description
9.7(0.0) Introduced on the S6000–ON.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
7.8.1.0 Introduced on the S-Series.
7.7.1.0 Introduced on the C-Series. Added support for the 4-byte format
Usage
Information
To accept 4-byte formats before entering a 4-byte AS number, configure your system. All the routers in
the Confederation must be 4 byte or 2 byte identified routers. You cannot mix them.
The autonomous systems configured in this command are visible to the EBGP neighbors. Each
autonomous system is fully meshed and contains a few connections to other autonomous systems. The
next hop, MED, and local preference information is preserved throughout the confederation.
Dell Networking OS accepts confederation EBGP peers without a LOCAL_PREF attribute. The software
sends AS_CONFED_SET and accepts AS_CONFED_SET and AS_CONF_SEQ.
If a local-as is configured, BGP does not allow for the configuration of BGP confederation. Similarly, if
BGP confederation is configured, then BGP does not allow the configuration of local-as.
Border Gateway Protocol 279