Setting up cluster client automatic configuration, Configuration, refer to – Brocade FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide User Manual
Page 169
device-1(config-cluster-SX-client-1)#rbridge-id 200
device-1(config-cluster-SX-client-1)#client-interface ether 1/5
device-1(config-cluster-SX-client-1)#deploy
To configure Client-2 on Brocade-2 in the topology of
on page 165, enter the following
command.
device-2(config-cluster-SX)# client client-2
device-2(config-cluster-SX-client-2)#rbridge-id 200
device-2(config-cluster-SX-client-2)#client-interface ether 2/8
device-2(config-cluster-SX-client-2)#deploy
Setting up cluster client automatic configuration
Complete the following steps to configure cluster client automatic configuration.
1. Enable the client auto-detect ports on both MCT devices.
device-1(config-cluster-SX)# client-auto-detect ethernet 1/15-1/16
In the port list, specify all the CCEPs for all potential clients.
2. Start the client auto-detect process on both cluster devices.
device-1(config-cluster-SX)# client-auto-detect start
Within one minute, the system reports information and errors (if there are mismatches such as an
LACP configuration mismatch). You can fix the mismatch while the process is running.
3. Check and fix the automatically detected clients.
device-1(config-cluster-SX)# show cluster cluster-SX client-auto-detect
cluster cluster-SX 4000
rbridge-id 3
session-vlan 3000
icl SX-MCT ethernet 1/7
peer 10.1.1.2 rbridge-id 2 icl SX-MCT
client-auto-config ethe 1/15 to 1/16 ethe 8/5 ethe 8/7 eth 8/9
client-auto-config start
deploy
client AUTO-FCX624-Router002438769e00
rbridge-id 3593
client-interface ethe 1/15
!
NOTE
At this point, the client configuration does not appear in the running configuration and cannot be
modified. Static trunk and LACP configuration are not effective yet.
4. Configure automatically detected clients into the running configuration.
device-1(config-cluster-SX)# client-auto-detect config
All automatically configured client information is now published into the running configuration, and the
static trunk configuration is generated, created, and deployed. LACP is started. By default, clients are
in the non-deployed state and the CCEPs is put into the disabled state. Ports that are successfully
programmed as CCEP are removed from the autoconfig-enabled port list. If the port list is empty,
which means all ports are configured into clients successfully, the automatic configuration process
stops. The original LLDP configuration is restored. Otherwise, the automatic configuration process
continues only on the ports still left in the list.
Other cluster client automatic configuration commands
You can use the following commands as an alternative to the step-by-step procedure in
Setting up cluster client automatic configuration
FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide
169
53-1003086-04