How To: Configure Out of band clustering on H seriesStep by step example for out of band clustering

How To: Configure Out of band clustering on H series

Objective
How to get going with Out of Band Clustering: In OOB clustering all the cluster control traffic uses eth0 or eth2 interface depending on the type of the node.
If you have HD & HC devices then you can use either eth0 or eth2 as your cluster control interface (where the control traffic will bet exchange between the nodes)
If you have low end devices like HB & TAxx you have to use only eth0 as your cluster control interface. eth2 is not supported on this platforms.

Environment
H series of nodes
Procedure
Planning
Assign a dedicated IP for the new cluster.
NB: this must be unique and is different to the two mgmt IP's if you are using eth2 interface as your cluster interface

Cluster Details
Name = provide any cluster name could be the combination of letters and numbers (e.g 1007)
ID = provide any cluster name could be the combination of letters and numbers (e.g 1007)
Mgmt IP = x.x.x.x /x (e.g 10.150.56.71/24)

Device A (Master node)
Stack ports = 1/1/x1..x2
Mgmt IP =
Cluster mgmt port = eth2 (for HD & HC devices)
Chassis Serial Number =
Box id = 1

Device B (standby node)
Stack ports = 2/1/x1..x2
Mgmt IP =
Cluster mgmt Port = eth2
Chassis Serial Number
New box id = 2

First, set up the cluster so each box communicates

On device A:
Re-run the Jump-Start script
(config) # config jump-start
...
Step 12: Cluster enable? [no] yes
Step 13: Cluster interface? [eth2]
Step 14: Cluster id (Back-end may take time to proceed)? [default-cluster] 1007
Step 15: Cluster name? [default-cluster] 1007
Step 16: Cluster mgmt IP address and masklen? [0.0.0.0/0] 10.150.56.71/24

#On device B
Change the chassis ID, please note, this will remove any existing configuration, so please take a back up first.
no chassis box-id 1
chassis box-id 2 serial-num <>

#Re-run the Jump-Start script
(config) # config jump-start
...
Step 12: Cluster enable? [no] yes
Step 13: Cluster interface? [eth2]
Step 14: Cluster id (Back-end may take time to proceed)? [default-cluster] 1007
Step 15: Cluster name? [default-cluster] 1007
Step 16: Cluster mgmt IP address and masklen? [0.0.0.0/0] 10.150.56.71/24

Log into VIP Address, the cluster mgmt IP set above.
chassis box-id 1 serial
card all box-id 1

chassis box-id 2 serial
card all box-id 2

Set up cluster stack-links (stack- link is used to send the data traffic between Gigamon nodes)
port 1/1/x1..x2 type stack
gigaStream alias box1-GSstack port 1/1/x1..x2

port 2/1/x1..x2 type stack
gigaStream alias box2-GSstack port 2/1/x1..x2

stack-link alias hc2-hc2 between gigastreams box1-GSstack and box2-GSstack

Additional Notes
please make sure that in an order to form the out of band cluster cluster name, cluster id, cluster interface and software version has to match with other nodes.
please also do not keep the cluster master preference default. for master node keep the cluster master preference higher (100 preferred) and for other nodes you can pick other number between 50 to 99
Verify all by using below commands on each nodes
show version
show cluster config
show cluster global brief

We recommend a clean node before joining existing cluster (reset factory only-traffic)