Before you begin, ensure your system meets the following requirements:
You must have a unique virtual IP address that is not used anywhere else in your network.
The commands must be run on a node that has the broker role enabled. This node will become the primary broker.
In case of two node clusters, ensure both the nodes are brokers. Failover does not happen between broker and compute nodes.
You must have a free IP address on your submission interface network that can be used as the virtual IP.
Virtual IP does not support IPv6 addresses.
If your management interface and submission interface are on different subnets, the virtual IP address must be on the same subnet as the submission interface.
Enable the virtual IP
This explains how to enable the virtual IP address for your cluster.
Enter CLI configuration mode.
hostname > enable hostname # configure terminal
Enable the virtual IP using the following command:
hostname (config) # mvx cluster vip <Virtual IP Address> netmask <NetMask> enable
For example, hostname (config) # mvx cluster vip 10.213.248.85 netmask /24 enable
When you run this command, the system:
Ensures the virtual IP always operates in the submission interface.
Checks if the specified virtual IP is free on the submission interface network. If the IP is in use, an error is returned.
Assigns the VIP to the specified submission interface of the current broker node. This node is set as VIP owner.
Verify the virtual IP configuration
After enabling the feature, verify that the virtual IP is assigned correctly and that the cluster recognizes the VIP owner.
Display the detailed cluster status to identify the VIP owner. The output will show the node role as broker (VIP owner) for the active node.
hostname # show mvx cluster status detail
Sample output:
IVX Cluster Nodes: Node Name : vx3100-109 Node Health : ready Node Role : broker SSH port : 22 Node Utilization : 0 % Node Name : vx-173 Node Health : ready Node Role : broker (VIP owner) SSH port : 22 Node Utilization : 0 % Node Name : vx6200-101 Node Health : ready Node Role : broker SSH port : 22 Node Utilization : 0 %
Display the configured virtual IP details.
show mvx cluster vip config
Sample output:
Virtual IP Configuration: Virtual IP : 10.1.1.3 Netmask : 24
Note
You can access the SSH and web UI using the virtual IP. You cannot configure the virtual IP from the CMS.
Disable the virtual IP
This disables the high availability feature and removes the virtual IP from the cluster.
Enter CLI configuration mode.
hostname > enable hostname # configure terminal
Disable the virtual IP feature.
hostname (config) # no mvx cluster vip enable Removed virtual IP configuration successfully.
Change the virtual IP address
To change the virtual IP address, you must first disable the current VIP configuration and then re-enable the feature with the new IP address.
Enter CLI configuration mode.
hostname > enable hostname # configure terminal
Disable the current virtual IP.
hostname (config) # no mvx cluster vip enable
Enable the feature with the new virtual IP address.
hostname (config) # mvx cluster vip <New Virtual IP> netmask <NetMask> enable