Configures a virtual IP (VIP) address that provides access to the Web UI of the primary node. The VIP address must be in the same subnet as the two nodes. You must stop the cluster engine on the secondary node first and then on the primary node before you can configure the VIP address. The fe_address resource agent that manages the VIP address must be enabled before you can use the VIP address.
You can view the Web UI of the primary node, but not the secondary node. In a local area network (LAN) deployment, you can assign a virtual IP (VIP) address for the cluster. The VIP address is dynamic and moves from node to node, depending on which node has the primary role. To access the Web UI, you go to the VIP address, instead of to the management port's IP address or hostname. This eliminates the need to determine which node is primary before you log in to the Web UI.
The fe_address resource agent is disabled by default. The VIP address must be defined before you enable the resource agent. If you disable the resource agent later, the VIP address remains in the cluster configuration.
Note
This is a global configuration. It is configured on only one node, but is applied to the cluster.
Syntax
ha address vip <ip address>
Parameters
ip address
The virtual IP address.
Example
The following example configures a VIP address and then enables the fe_address resource agent.
node1 (config) # ha address vip 10.11.121.19 node1 (config) # ha resource fe_address enable
User role
Admin
Command mode
Config
Supported appliances
This command is supported on the following appliances running the specified releases or later:
Central Management System: Before Release 6.4.0. The
fe_accessresource agent was added in Release 7.7.0.
Note
For more information about Central Management System HA, see the Central Management High Availability Guide.