Brocade FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide - Manual (Page 170)

Use the following command to enable or disable cluster client automatic configuration on a range of
ports.
Syntax: [no] client-auto-detect Ethernet x [ to y]
Use the following command as an alternative to client-auto-detect config . This command also
configures automatically detected clients into the running configuration and deploys all of the
automatically detected clients.
Syntax: client-auto-detect config deploy-all
Use the following command to start the cluster client automatic configuration. Within one minute of the
time that each client is discovered, the client is automatically configured and deployed into the running
configuration.
Make sure that the network connection and configuration are in place before using this command.
Syntax: client-auto-detect start [ config-deploy-all ]
Use the following command to stop the current running cluster client automatic configuration process.
All auto-detected but unconfigured clients will be cleared.
Syntax: client-auto-detect stop
MCT failover scenarios
The following scenarios describe what happens if specific elements in the MCT configuration fail.
• Client interface on one of the MCT cluster devices goes down.
‐ Traffic switches to the other cluster device with minimal traffic loss.
• MCT cluster device goes down.
‐ When an MCT cluster device goes down (for example, due to a power failure), the traffic
fails over to the other MCT cluster device.
• Hitless failover occurs.
‐ The MCT CCEPs stay up during hitless switchover, failover, or upgrade. Link protocols
such as UDLD and LACP on CCEPs do not flap. Traffic disruption is minimal (sub-
second). The MCT CCP connection flaps once, and MAC is re-synced between the peer
devices.
‐ The CCP goes down and comes back up again once the hitless failover is completed.
• ICL interface or CCP goes down (keep-alive is configured).
‐ If a keep-alive VLAN is used, the devices in the cluster can communicate even if the ICL
goes down. If the peer device is reachable over the keep-alive VLAN, the MCT peers
perform the master/slave negotiation per client. After negotiation, the slave shuts down its
client ports, and the master client ports continue to forward the traffic.
‐ The master/slave negotiation is performed per MCT client on the basis of RBridgeID and
client Local or Remote accessibility. If the client is reachable from both MCT devices, the
MCT failover scenarios
170 FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide
53-1003086-04