Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 652)

622 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
Active/Passive mode
To configure MCT to operate in the Active/Passive mode, set the mode for the cluster. The cluster
mode should be configured on both the node. If both nodes are not configured Active-Passive, then
the CCP will not be brought up. This configuration is not allowed after the cluster is deployed.
Brocade(config-cluster-c)# mode-active-passive
Syntax: [no] mode-active-passive
Client-role
The client-role command is used for configuring the per client role as Active or Passive. When the
global and per client role configurations are present, then per client role configuration takes the
highest precedence.
If Global and per client role configurations is not present, then the rbridge-id used for client role
election, the node with the lowest rbridge-id will be Active.
This global command will be applicable for all the MCT clients.
Brocade(config-cluster-c)#client-role active
This command will be applicable for a single MCT client.
Brocade(config-cluster-c-client-c1)# client-role passive
Syntax: [no] client-role <role>
The <role> parameter specifies if the client role is active or passive.
Client-role-revertible-delay timer
The client-role-revertible-delay timer command is used for configuring client role revertible delay
mode in case of port flaps, and to revert the client role after client role switch.
Brocade(config-cluster-c-client-c1)#client-role-revertible-delay timer 5
Syntax: [no] client-role-revertible-delay timer <value>
Enter a value of 1-240 minutes. Default value is 1 minute.
Displaying cluster information
Use the show cluster command to display the entire cluster configuration and show tech cluster
commmand to dsplay cluster configuration and operation information. See the Brocade MLXe,
NetIron MLX, and NetIron XMR Diagnostic Reference for additional information on these
commands.
Keep-alive VLAN
CCRR message are used to exchange information between peers. When the CCP is up, CCRR
messages are sent over CCP. When the CCP client reachability is down, you can use the
keep-alive-vlan command under cluster context so CCRR messages are periodically sent over the
keep-alive-vlan. Only one VLAN can be configured as a keep-alive-vlan. The keep-alive VLAN cannot
be a member VLAN of the MCT and this VLAN can be tagged or untagged. A port in keep-alive-vlan
cannot be assigned to another VLAN.