Inband Cluster Management with GigaVUE TA Series (Including a White Box)
A GigaVUE TA Series node can never be the leader or standby in a cluster configuration. In the example, How to Setup Inband Cluster Management on a New Cluster, if a GigaVUE TA Series node is added to the cluster, it can only take the role of Normal.
Additionally, a license is required to enable cluster formation with a GigaVUE TA Series node. For each GigaVUE TA Series node in a cluster, a specific Advanced Features License is required that is tied to the serial number of that node. In order to add a GigaVUE TA Series node to an Inband cluster, it is important that you have the Advanced Features License installed and enabled on the GigaVUE TA Series node before joining the cluster.
Using the same example as in the section, How to Setup Inband Cluster Management on a New Cluster, we recreated the following example. In it, we add a GigaVUE TA Series node Certified Traffic Aggregation White Box (white box) to establish a stack link from GigaVUE TA Series (8/1/x5..x20) to leader (7/8/x5..x20).
Note: The faceplate numbering of a white box is different. Refer to White Box Port and Faceplate Labeling.
In this example, Seattle is the leader. The nodes to be configured in the Inband cluster are as follows:
|
Node Number |
Node Name |
Node Type |
|
1 |
Seattle |
GigaVUE‑HC3 |
|
2 |
Washington |
Certified Traffic Aggregation White Box |
Note: To configure Inband Cluster Management, you must maintain a command shell for the leader as well as the target nodes, due to the offline configuration that needs to be applied to leader.
Configuration Steps for Leader: Seattle
1Open an SSH or terminal session to the Seattle node.
Part 1: Using the Jump-Start Wizard to Configure Node 1
| 1. | In config, enter configuration jump-start to start the jump-start wizard: |
gigamon-0d0024 > enable
gigamon-0d0024 # configure terminal
gigamon-0d0024 (config) # configuration jump-start
GigaVUE‑OS configuration wizard
| 2. | Enter the parameter values to configure the leader. |
Step 1: Hostname? [gigamon-0d0024] Seattle
Step 2: Management interface? [eth0]
Step 3: Use DHCP on eth0 interface? no
Step 4: Use zeroconf on eth0 interface? [no]
Step 5: Primary IPv4 address and masklen? [0.0.0.0/0] 10.150.52.6/24
Step 6: Default gateway? 10.150.52.1
Step 7: Primary DNS server? 192.168.2.20
Step 8: Domain name? gigamon.com
Step 9: Enable IPv6? [yes]
Step 10: Enable IPv6 autoconfig (SLAAC) on eth0 interface? [no]
Step 11: Enable DHCPv6 on eth0 interface? [no]
Step 12: Enable secure cryptography? [no]
Step 13: Enable secure passwords? [no]
Step 14: Minimum password length? [8]
Step 15: Admin password?
Please enter a password. Password is a must.
Step 15: Admin password?
Step 15: Confirm admin password?
Note: In Step 16, accept the default of No so that you do not enable the cluster.
Step 16: Cluster enable? [no]
Note: In Step 17, assign the box ID of your chassis.
Step 17: Box-id for the chassis? [1] 7
Note: To change the answers in the jump-start wizard, enter the step number that you want to change. Click Enter to save changes and exit.
Choice:
Configuration changes saved.
System in classic mode
Seattle (config) #
Part 2: Configuring Inband Cluster on the Leader
| 3. | You need to disable the zeroconf feature on the default cluster interface on eth2 of the control card (HCCv2) in the Seattle node, and make cluster interface Inband with relevant cluster information. |
Seattle (config) # no interface eth2 zeroconf
Seattle (config) # cluster interface inband
Seattle (config) # cluster id 600
Seattle (config) # cluster name 600
Seattle (config) # cluster leader address vip 10.150.52.233 /24
Seattle (config) # interface inband zeroconf
Seattle (config) #
| 4. | Enter show interfaces to perform a confirmation check. |
| 5. | Make sure that no IP address is assigned on eth2 and new IP address is auto assigned for Inband interface. |
Seattle (config) # show interfaces
.
.
.
Interface eth2 status:
Comment:
Admin up: yes
Link up: yes
DHCP running: no
IP address:
Note: The IP address field on eth2 should be empty.
Netmask:
IPv6 enabled: no
Speed: 1000Mb/s (auto)
.
.
.
Interface inband status:
Comment:
Admin up: yes
Link up: yes
DHCP running: no
IP address: 169.254.51.255
Note: The IP address field is automatically assigned.
Netmask: 255.255.0.0
Seattle (config) #
2Enter show cluster configured to display the current cluster configuration.
Seattle [600: leader] (config) # show cluster configured
Global cluster config:
Cluster enabled: no
Cluster ID: 600
Cluster name: 600
Cluster control interface: inband
Note: The cluster control interface is set to inband.
Cluster port: 60102
Cluster expected nodes: 2
Cluster startup time: 180
Cluster shared secret: 1234567890123456
Cluster leader preference: 60
Cluster leader auto-discovery enabled: yes
Cluster leader manual port: 60102
Cluster leader virtual IP address: 10.150.52.233/24
Cluster leader management interface: eth0
Seattle [600: leader] (config) #
Note: If the jump-start script is used after the Inband cluster is configured, the “inband” option will be available for the cluster interface along with eth0, eth1 and eth2.
Part 3: Configured Leader is Ready for Inband Cluster
| 6. | Enter the card slot and number command. If the designated stack port is located at slot 7, then wait for the card at slot 7 to come “up” to the “oper state.” |
Seattle (config) # card slot 7/8
| 7. | Enter show card to perform a confirmation check. |
Seattle [600: leader] (config) # show card
Box ID: 7 (leader)
Slot Config Oper Status HW Type Product Code Serial Num HW Rev
-----------------------------------------------------------------------------
1 no inserted GigaPORT-X12G04 132-0045 1450-0162 B4-a6
2 no inserted GigaPORT-C01 132-00A8 1A80-0114 A2-5
3 no inserted GigaPORT-Q08 132-00AK 1AK0-0022 A0-a4
4 no inserted GigaPORT-X12G04 132-0045 1450-0181 B4-a6
cc1 yes up H-CCv2 132-0089 1890-0036 5.2-df
5 no inserted GigaPORT-X12G04 132-0045 1450-0224 C2-a6
6 no inserted GigaPORT-Q02X32 132-0087 1870-0157 B2-a1
7 no inserted GigaPORT-C01 132-00A8 1A80-0107 A2-5
8 yes up GigaPORT-Q02X32/2q 132-0087 1870-0167 B2-a2
Seattle [600: leader] (config) #
| 8. | Assign and enable the stack ports. Make them stack GigaStream. |
| 9. | Enable the cluster. |
Note: The Seattle node is now the leader as indicated in the CLI prompt.
Seattle (config) # port 7/8/x5..x20 type stack
Seattle (config) # port 7/8/x5..x20 params admin enable
Seattle (config) # gigastream alias big_bridge_7to8 port 7/8/x5..x20
Seattle (config) # cluster enable
Seattle [600: leader] (config) #
Part 4: Apply Offline Remote Node Configuration on the Leader
| 10. | Apply offline remote node configuration on the leader as shown in the CLI command to conclude leader setup. |
Seattle [600: leader] (config) # chassis box-id 8 serial-num QTFCEA4170003 type ly2r
Seattle [600: leader] (config) # card slot 8/1 product-code 132-0087 mode 48x
Note: It is imperative to add the mode configured on the GigaVUE TA Series node that is joining the cluster to ensure that the leader has the correct configuration. Refer to Offline Remote Configuration for GigaVUE TA Series Nodes.
Seattle [600: leader] (config) # port 8/1/x5..x20 type stack
! Box '8' is down, unable to validate SFP type for stack port.
Note: The box number is down, unable to validate SFP type for stack port message is expected behavior.
.
.
.
Seattle [600: leader] (config) # port 8/1/x5..x20 params admin enable
Seattle [600: leader] (config) # gigastream alias big_bridge_8to7 port 8/1/x5..x20
Seattle [600: leader] (config) # write memory
3Enter show running-config to perform a confirmation check.
Seattle [600: leader] (config) # show running-config
Configure Inband Cluster on the Remote Target Node: Certified Traffic Aggregation White Box: Washington
Part 1: Using the jump-start wizard to configure the node:
Do you want to use the wizard for initial configuration? yes
Step 1: Hostname? [gigamon-5508f4] Washington
Step 2: Management Interface <eth0> ? [eth0]
Step 3: Use DHCP on eth0 interface? no
Step 4: Use zeroconf on eth0 interface? [no] no
Step 5: Primary IPv4 address and masklen? [0.0.0.0/0] 10.115.26.114 /21
Step 6: Default gateway? 10.115.24.1
Step 7: Primary DNS server? 10.10.1.20
Step 8: Domain name? gigamon.com
Step 9: Enable IPv6? [yes]
Step 10: Enable IPv6 autoconfig (SLAAC) on eth0 interface? [no]
Step 11: Enable DHCPv6 on eth0 interface? [no]
Step 12: Enable secure cryptography? [no]
Step 13: Enable secure passwords? [no]
Step 14: Minimum password length? [8]
Step 15: Admin password?
Please enter a password. Password is a must.
Step 15: Admin password?
Step 15: Confirm admin password?
No valid advanced features license found!
Step 16: Box-id for the chassis? [1] 8
You have entered the following information:
1. Hostname: Washington
2. Management Interface <eth0> : eth0
3. Use DHCP on eth0 interface: no
4. Use zeroconf on eth0 interface: no
5. Primary IPv4 address and masklen: 10.115.26.114/21
6. Default gateway: 10.115.24.1
7. Primary DNS server: 10.10.1.20
8. Domain name: gigamon.com
9. Enable IPv6: yes
10. Enable IPv6 autoconfig (SLAAC) on eth0 interface: no
11. Enable DHCPv6 on eth0 interface: no
12. Enable secure cryptography: no
13. Enable secure passwords: no
14. Minimum password length: 8
16. Admin password: ********
17. Box-id for the chassis: 8
To change an answer, enter the step number to return to.
Otherwise hit <enter> to save changes and exit.
Choice:
Configuration saved to database 'initial'
Configuration changes saved.
Part 2: Configure the Inband Cluster on the Remote Target GigaVUE TA Series Node
Washington (config) # card slot 8/1
Washington (config) # license install box-id 8 key <Port_License>
License installed successfully on slot 8/1
Washington (config) # license install box-id 8 key <Advanced_Features_License>
License installed successfully on slot 8/1
Washington (config) # cluster interface inband
Washington (config) # cluster id 600
Washington (config) # cluster name 600
Washington (config) # cluster leader address vip 10.115.26.151 /21
Washington (config) # interface inband zeroconf
Washington (config) # card slot 8/1
Washington (config) # port 8/1/x5..x20 type stack
Washington (config) # port 8/1/x5..x20 params admin enable
Washington (config) # gigastream alias big_bridge_8to7 port-list 8/1/x5..x20
Washington (config) # write memory
Configuration saved to database 'initial'
Enter show cluster configured to display the cluster configuration settings.
Make sure that the “Inband” value is defined in the cluster control interface.
Washington (config) # show cluster configured
Global cluster config:
Cluster enabled: no
Cluster ID: 600
Cluster name: 600
Cluster control interface: inband
Note: The cluster control interface is set to “inband”.
Cluster port: 60102
Cluster expected nodes: 1
Cluster startup time: 180
Cluster shared secret: 1234567890123456
Cluster leader preference: 0
Cluster leader auto-discovery enabled: yes
Cluster leader manual port: 60102
Cluster leader virtual IP address: 10.115.26.151/21
Cluster leader management interface: eth0
Note: Stack interface should show as up.
Washington (config) # show port params port-list 8/1/x5
Parameter 8/1/x5
====================== ===============
Name Alias:
Type: stack
Admin: enabled
Link status: up
Note: The Link Status indicates that the stack port is “up” state.
Auto Negotiate: off
Duplex: full
Speed (Mbps): 10000
MTU: 9400
Force Link Up: off
Port Relay: N/A
...
Now that you have established the port license and Advanced Features License on the GigaVUE TA Series, move to the leader in the cluster and run the following steps. (The following example shows the steps on a GigaVUE-TA1.)
Part 3: Enable the Cluster on the Joining GigaVUE TA Series Node
Washington (config) # cluster enable
Washington [600: unknown] (config) #
Note: The Washington node is in an unknown transitional state.
Washington [600: normal] (config) #
Part 4: Finish Configuration of the Cluster on the Leader (Only Required with GigaVUE TA Series Nodes Including White Box)
Note: Ensure GigaVUE TA Series node or the white box has joined the cluster and the chassis is up.
Seattle [600: leader] # show chassis
For white box nodes, the Quanta box information is shown as HW Type. This will vary with the GigaVUE nodes.
Install the Port License of the GigaVUE TA Series Node (Normal) on Leader
Seattle [600: leader] (config) # license install box-id 8 key <Port_License>
License installed successfully on slot 8/1
Seattle [600: leader] (config) # show license
---------
Box 1
---------
---------
Box 8
---------
Slot Feature Parameters Expiration Date
------------------------------------------
1 PORT - Never
Chassis-Feature Parameters
---------------------------
CLUSTER -
Check the License on Washington Node
System in classic mode
Washington [600: normal] > en
Washington [600: normal] # show license
---------
Box 8
---------
Slot Feature Parameters Expiration Date
------------------------------------------
1 PORT - Never
Chassis-Feature Parameters
---------------------------
CLUSTER -
MORE INFORMATION 
