To provide fault tolerance and high availability to NSX Manager nodes, assign a virtual IP address (VIP) to a member of the NSX-T cluster.
NSX Managers of a cluster become part of an HTTPS group to service API and UI requests. The leader node of the cluster assumes ownership of the set VIP of the cluster to service any API and UI request. Any API and UI request coming in from clients is directed to the leader node.
When assigning Virtual IP, all the NSX Manager VMs in the cluster must be configured in the same subnet.
If the leader node that owns VIP becomes unavailable, NSX-T elects a new leader. The new leader owns the VIP. It sends out a gratuitous ARP packet advertising the new VIP to MAC address mapping. After a new leader node is elected, new API and UI requests are sent to the new leader node.
Failover of VIP to a new leader node of the cluster might take a few minutes to become functional. If the VIP fails over to a new leader node because the previous leader node became unavailable, reauthenticate credentials so that API requests are directed to the new leader node.
- From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
- Go to System > Overview.
- In the Virtual IP field, click Edit.
- Enter the VIP for the cluster. Ensure that VIP is part of the same subnet as the other management nodes.
- Click Save.
- To verify the cluster status and the API leader of the HTTPS group, enter the NSX Manager CLI command get cluster status verbose in the NSX Manager console or over SSH.
The following is an example output with the leader marked in bold.
Group Type: HTTPS Group Status: STABLE Members: UUID FQDN IP STATUS cdb93642-ccba-fdf4-8819-90bf018cd727 nsx-manager 126.96.36.199 UP 51a13642-929b-8dfc-3455-109e6cc2a7ae nsx-manager 188.8.131.52 UP d0de3642-d03f-c909-9cca-312fd22e486b nsx-manager 184.108.40.206 UP Leaders: SERVICE LEADER LEASE VERSION api cdb93642-ccba-fdf4-8819-90bf018cd727 8
- To troubleshoot VIP, verify Reverse Proxy logs at /var/log/proxy/reverse-proxy.log and cluster manager logs at /var/log/cbm/cbm.log in the NSX Manager CLI.
Any API requests to NSX-T is redirected to the virtual IP address of the cluster, which is owned by the leader node. The leader node then routes the request forward to the other components of the appliance.