Before you configure the cluster, meet the requirements described in this section for your configuration option.
Basic requirements
Initial configuration of both nodes (described in the Central Management System Administration Guide), including the following:
Static IP address (DHCP is not supported)
Hostname
Netmask
Default gateway IP address
Name server IP address
Important
Do not change the hostname of a node after the cluster is formed and running. To change the hostname, you must stop the cluster, remove the node from the cluster, rename the node, and then add the node back to the cluster.
A Central Management System license is installed on each node.
HA mode is enabled on both Central Management System nodes.
Both nodes use the same Central Management System appliance hardware or virtual model (for example, two CM 7500 models or two CM 4500V models).
Note
The CM 4500V and CM 7500V are the only virtual appliances that support Central Management System HA.
Both nodes use the same major and minor version (Release 7.7.0 or later) and the same build number of the Central Management System system image.
If you use an alternative HTTPS certificate (instead of the default system self-signed certificate), the alternative certificate is installed on each node. The node in the primary role uses this certificate to identify itself to the Web browsers running the Web UI. For details, see the "Managing HTTPS Certificates" section of the Central Management System Administration Guide.
A client-initiated connection is used to add appliances to the primary node for management only in a LAN deployment with a configured VIP address. If both of these requirements are not met, a server-initiated connection must be used. For details, see Appliance management .
LAN deployment requirements
The following additional requirements affect LAN deployments.
Physical Central Management System HA Deployment
One Ethernet cable (crossover type preferred) or switch to connect the two default HA interfaces
Dual-interface deployment only: One Ethernet cable (crossover type preferred) or switch to connect the two backup HA interfaces
Non-default interface only: IP address and network mask for each interface on both nodes if ether2 or ether3 is used as the default HA or backup HA interface.
Virtual Central Management System HA Deployment
Each node deployed on separate ESXi server
Non-default interface only: If ether2 or ether3 is used as the default HA or backup HA interface:
Virtual network configured as described in Virtual network requirements.
IP address and network mask for each interface on both nodes
WAN deployment requirements
The following additional requirements affect WAN deployments.
Firewall rules allow the cluster to use ports TCP and UDP 3470-3480 and TCP 22.
ICMP (Ping) is useful as a diagnostic tool to verify reachability between nodes; however, it is not mandatory and may be disabled if customer security policies restrict ICMP traffic.
Static route information for the default HA interface on each node:
IP address
Network mask
Default gateway IP address
Client-initiated connections to a Central Management System HA node are not supported in a WAN deployment. For details, see Appliance management .