Configuring Master-Capability

Each node is configurable to be master-capable or not. This means that a node can either be allowed to take on any node role, or be restricted to executing the standby node role only. The default is that a node can take on any role. The restriction is used to avoid the dual master condition. A master-capability configuration change takes effect at the next restart.

You can configure one or more nodes to be allowed to operate either as a master or a backup.

The configure stacking master-capability command allows you to set the master-capability of specific nodes, while configure stacking redundancy allows you to set the master-capability on all nodes in the stack.

The commands do not allow you to disable master-capability on all nodes in a stack topology.


If the entire stack is restarted in stacking mode without any node having master capability, you need to know the failsafe account and password to log into any node in the stack. If you do not know the failsafe account information, you might need to rescue the stack. See Rescuing a Stack that has No Primary-Capable Node.
You can use any of the following commands to configure the master-capability:
  • configure stacking [node-address node_address | slot slot_number] master-capability [on | off]
  • configure stacking redundancy [none | minimal | maximal]