Configuring a Cluster
To set up a cluster of two switches, say, pleiades1 and pleiades2, you must first verify that they both belong to the same fabric instance, in this case corp-fab:
CLI network-admin@switch > fabric-node-show layout vertical
id: 184549641
name: pleiades1
fab-name: corp-fab
fab-id: b000109:5695af4f
cluster-id: 0:0
local-mac: 3a:7f:b1:43:8a:0f
fabric-network: in-band
control-network: in-band
mgmt-ip: 10.9.19.203/16
mgmt-mac: ec:f4:bb:fe:06:20
mgmt-secondary-macs:
in-band-ip: 192.168.168.203/24
in-band-mac: 3a:7f:b1:43:8a:0f
in-band-vlan: 0
in-band-secondary-macs:
fab-tid: 1
cluster-tid: 0
out-port: 0
version: 2.4.204009451,#47~14.04.1-Ubuntu
state: online
firmware-upgrade: not-required
device-state: ok
ports: 104
To create a cluster configuration, use the following command:
CLI network-admin@switch > cluster-create name cluster1 cluster-node-1 pleiades1 cluster-node-2 pleiades2
To verify the status of the cluster, use the cluster-show command:
CLI network-admin@switch > cluster-show
name state cluster-node-1 cluster-node-2
--------- ------- --------------- --------------
cluster1 online pleiades1 pleiades2
 
To replace a failed cluster node, use the fabric-join repeer-to-cluster-node command. However, you must evict the failed node from the fabric, and then run the fabric-join repeer-to-cluster-node command on an active node after replacing the failed node.
To display information about the cluster, use the cluster-info command:
CLI network-admin@switch > cluster-info format all layout vertical
name: cluster1
state: online
cluster-node-1: pleiades1
cluster-node-2: pleiades2
tid: 2
mode: master
ports: 69-71,129
remote-ports: 69-71,128