Configuration Guide User guide

844 FastIron Configuration Guide
53-1002494-02
Basic MCT configuration
22
• Double failures (for example, when the ICL goes down and the client interface goes down on
one of the MCT cluster devices)
Multiple failures could drop traffic in this scenario, even if there is a physical path available.
Cluster failover mode
The following failover modes can be configured with MCT:
• Fast-failover (default) - As soon as the ICL interface goes down the CCP goes down. All the
remote MAC addresses are flushed.
• Slow-failover - Even if the ICL interface goes down, the CCP waits for the hold-time before
taking the CCP down. Remote MAC addresses are flushed only when the CCP is down.
To disable the fast-failover mode, enter a command such as the following.
Brocade-1(config-cluster-SX)#peer 1.1.1.3 disable-fast-failover
Syntax: [no] peer <peer-ip> disable-fast-failover
Client isolation mode
NOTE
The CLI will allow modification of the client isolation mode on MCT cluster devices even when the
cluster is deployed. You must create the same isolation mode on both cluster devices.
MCT cluster devices can operate in two modes. Both peer devices should be configured in the
same mode.
Loose mode (default): When the CCP goes down, the peer device performs the master/slave
negotiation. After negotiation, the slave shuts down its peer ports, whereas the master peer ports
continue to forward the traffic (keep-alive VLAN configured).
If the keep-alive VLAN is not configured, both peer devices become master and both of the client
ports stay up.
Brocade-1(config-cluster-SX)#client-isolation loose
Strict mode: When the CCP goes down, the interfaces on both the cluster devices are
administratively shut down. In this mode, the client is completely isolated from the network if the
CCP is not operational.
Brocade-1(config-cluster-SX)#client-isolation strict
Syntax: [no] client-isolation <loose | strict>
Shutting down all client interfaces
Use the client-interfaces shutdown command when performing a hitless upgrade operation. This
command can be used to shut down all the local client interfaces in the cluster. This would result in
failover of traffic to the peer device.
Brocade-1(config-cluster-SX)#client-interfaces shutdown
Syntax: [no] client-interfaces shutdown