From the NSX Manager central CLI, you can check the health status of each ESXi host.

The health status is reported as critical, unhealthy, or healthy. The host health-check command can also be invoked through the NSX Manager API.

For example:

nsxmgr> show host host-30 health-status
status: HEALTHY

nsxmgr> show host host-29 health-status
UNHEALTHY, Standard Switch vSwitch1 has no uplinks.

UNHEALTHY, Host host-29 mount point /vmfs/volumes/58e2c6d5-83319ac1-7830-005056014d86
volume "local_esx-06a" free percentage less than 20%: 0%.
Status: UNHEALTHY

nsxmgr> show host host-28 health-status
CRITICAL, VXLAN VDS vds-site-a VNI 200000 multicast addr is not synchronized with VSM: 0.0.0.0.
CRITICAL, VXLAN VDS vds-site-a VNI 200003 multicast addr is not synchronized with VSM: 0.0.0.0.
CRITICAL, VXLAN VDS vds-site-a VNI 5000 multicast addr is not synchronized with VSM: 0.0.0.0.
Status: CRITICAL

CRITICAL, Control plane agent on host is not in established state with controller. Please
investigate host connection issue with esxcli network ip connection
command.
CRITICAL, VXLAN VDS RegionA01-vDS-MGMT VNI 5007 connection to controller is down: 0.0.0.0
(down).

You can use the show host hostID health-status detail command to view the detailed health status of the specified host for each parameter.

The health checks are split into the following distinct categories:

  1. Deployment health checks, including deployment of NSX VIBs and host agents. Note that some of these checks can be used during runtime, such as the netcpa and firewall agent checks.

    The host associated cluster check [DONE]
    The NSX component installation check [DONE]
    The NSX module VXLAN installation check [DONE]
    The NSX module DLR installation check [DONE]
    The NSX VIB installation check [DONE]
    The control plane agent check [DONE]
    The firewall agent check [DONE]
    The NSX configuration file check [DONE]
    The host connection to controller check [DONE]

  2. Network connectivity health.

    The Distributed Switch uplink check [DONE]
    The Standard Switch uplink check [DONE]

  3. CPU, memory, and storage utilization health.

    The storage volume check [DONE]
    UNHEALTHY, Host host-34 mount point /vmfs/volumes/58e2c69b-38d4fa25-b33a-00505601dfe2
    volume "local_esx-05a" free percentage less than 20%: 0%.
    The Memory overcommit check [DONE]
    The physical CPU load check [DONE]
    The free memory usage check [DONE]

  4. Logical switch health.

    The VXLAN VDS existence check [DONE]
    The VXLAN VDS MTU check [DONE]
    The VXLAN gateway IP/MAC check [DONE]
    The VXLAN vmknic check [DONE]
    The VXLAN uplinks check [DONE]
    The VXLAN configuration check [DONE]
    The VXLAN vmknic IP address check [DONE]
    The VXLAN Overlay settings check [DONE]
    The VXLAN vni settings check [DONE]
    The host vmnic check [DONE]
    The VXLAN vmknic check [DONE]

Here are few examples of the output:

nsx-mgr> show host host-33 health-status detail
The host associated cluster check [DONE]
The NSX component installation check [DONE]
The NSX module VXLAN installation check [DONE]
The NSX module DLR installation check [DONE]
The NSX VIB installation check [DONE]
The control plane agent check [DONE]
The firewall agent check [DONE]
The NSX configuration file check [DONE]
The host connection to controller check [DONE]
The Distributed Switch uplink check [DONE]
The Standard Switch uplink check [DONE]
The storage volume check [DONE]
UNHEALTHY, Host host-34 mount point /vmfs/volumes/58e2c69b-38d4fa25-b33a-00505601dfe2
volume "local_esx-05a" free percentage less than 20%: 0%.
The Memory overcommit check [DONE]
The physical CPU load check [DONE]
The free memory usage check [DONE]
The VXLAN VDS existence check [DONE]
The VXLAN VDS MTU check [DONE]
The VXLAN gateway IP/MAC check [DONE]
The VXLAN vmknic check [DONE]
The VXLAN uplinks check [DONE]
The VXLAN configuration check [DONE]
The VXLAN vmknic IP address check [DONE]
The VXLAN Overlay settings check [DONE]
The VXLAN vni settings check [DONE]
The host vmnic check [DONE]
The VXLAN vmknic check [DONE]
Status: UNHEALTHY

nsx-mgr> show host host-33 health-status detail
The host associated cluster check [DONE]
The NSX component installation check [DONE]
The NSX module VXLAN installation check [DONE]
The NSX module DLR installation check [DONE]
The NSX VIB installation check [DONE]
The control plane agent check [DONE]
The firewall agent check [DONE]
The NSX configuration file check [DONE]
The host connection to controller check [DONE]
CRITICAL, Control plane agent on host is not in established state with controller. Please
investigate host connection issue with esxcli network ip connection
command.
The Distributed Switch uplink check [DONE]
The Standard Switch uplink check [DONE]
The storage volume check [DONE]
The Memory overcommit check [DONE]
The physical CPU load check [DONE]
The free memory usage check [DONE]
The VXLAN VDS existence check [DONE]
The VXLAN VDS MTU check [DONE]
The VXLAN gateway IP/MAC check [DONE]
The VXLAN vmknic check [DONE]
The VXLAN uplinks check [DONE]
The VXLAN configuration check [DONE]
The VXLAN vmknic IP address check [DONE]
The VXLAN Overlay settings check [DONE]
The VXLAN vni settings check [DONE]
CRITICAL, VXLAN VDS RegionA01-vDS-MGMT VNI 5007 connection to controller is down: 0.0.0.0
(down).
The host vmnic check [DONE]
The VXLAN vmknic check [DONE]
Status: CRITICAL

Table 1.

Health Check

Message

Description

The host associated cluster check

Host {hostId} doesn't belong to a cluster.

This heath check finds out if the particular host (host Id) is correctly associated with a cluster.

The NSX component installation check

Host {hostId} has no NSX components installed.

This heath check finds out if all the NSX components are installed correctly for the host (host Id).

The NSX module VXLAN installation check

The NSX module VXLAN is not installed/loaded/enabled on host {hostId}.

This heath check finds out if VXLAN is configured properly on the host (host Id).

The NSX module DLR installation check

The NSX module for distributed routing is not installed, loaded, or enabled on the host.

This heath check finds out if a distributed logical router (DLR) is installed correctly for the host (host Id).

The NSX VIB installation check

The NSX VIB installation check has failed on host.

This heath check finds out if the installed NSX VIBs are appropriate for the new ESXi version.

The NSX for vSphere data plane is incompatible with the ESXi host version. Investigate further by confirming that the esx-vsip VIB installed on the host matches the NSX version.

The control plane agent check

Service netcpad is not running on host {hostId}.

This heath check finds out if the control plane agent is communicating with the NSX Manager.

For troubleshooting, refer to Control Plane Agent (netcpa) Issues.

The firewall agent check

The NSX firewall agent is running or not on the host.

This heath check finds out if the firewall agent is running on the host (host Id).

For troubleshooting, refer to Troubleshooting Distributed Firewall.

The NSX configuration file check

The NSX configuration file /etc/vmware/netcpa/config-by-vsm.xml is not synchronized on host {hostId}.

This heath check finds out if the NSX configuration file /etc/vmware/netcpa/config-by-vsm.xml is synchronized with the host (host Id).

The host connection to controller check

Control plane agent on host is not in established state with controller.

This heath check finds out if the control plane agent is communicating with the host (host Id).

For troubleshooting, refer to Control Plane Agent (netcpa) Issues.

The Distributed Switch uplink check

Distributed Switch {dvsName} has no uplinks.

For troubleshooting, refer to vSphere Networking Guide.

The Standard Switch uplink check

Standard Switch {vswitchName} has no uplinks.

For troubleshooting, refer to vSphere Networking Guide.

The storage volume check

Host "+hostId+" mount point "+mountPoint+" volume \""+volumeName+"\" free percentage less than 20%: "+freePercent+"%.\n.

The Memory overcommit check

Memory overcommit info from esxtop can't be parsed. Host {hostId} memory is over commited.

The physical CPU load check

Host {hostId} Physical CPU Load (5 Minute Avg) info from esxtop can't be parsed. Host {hostId} Physical CPU Load (5 Minute Avg) is too high.

The free memory usage check

Host {hostId} mount point {mountPoint} volume {volumeName} free percentage less than 20%.

The VXLAN VDS existence check

No VXLAN VDS is configured on host {hostId}.

For troubleshooting, refer to vSphere Networking Guide.

The VXLAN VDS MTU check

VXLAN VDS {vxlanVds} MTU is less than 1550: {vxlanVdsMtu}. Please check MTU value of connected VMs is not greater than { vxlanVdsMtu-50}.

The VXLAN gateway IP/MAC check

Gateway IP/mac address of VXLAN VDS {vxlanVds} is not resolved.

The VXLAN vmknic check

VXLAN VDS {vxlanVds} has no vmknic.

Collect the vmkernel.log, and contact VMware technical support.

The VXLAN uplinks check

VXLAN VDS {vxlanVds} has no uplinks.

The VXLAN configuration check

Configuration of VXLAN VDS {+vxlanVds} of host {hostId} is not synchronized. Configuration of VXLAN VDS {vxlanVds} is not defined on NSX Manager. VXLAN VDS {vxlanVds} vmknic and uplink counts are not equal for teaming policy {vdsContext.getT eamingPolicy}.

Set the VXLAN portgroup teaming policy back to the original value.

The VXLAN vmknic IP address check

VXLAN VDS {vxlanVds} {vmknic}+{vmknic}+{ip address} is not resolved. VXLAN VDS {vxlanVds vmknic} +{vmknic}{ip address} is not resolved.

This check indicates that a VTEP does not have a valid IP address or lost a valid IP address.

The VXLAN Overlay settings check

VXLAN VDS {vxlanVds} overlay settings are not VXLAN: {overlay}{VXLAN VDS}{vxlanVds} overlay settings are not found.

The VXLAN vni settings check

VXLAN VDS {vxlanVds+ " VNI "+vni+}connection to controller is down VXLAN VDS {vxlanVds+ " VNI "+vni+"} segment info is not configured in NSX Manager. VXLAN VDS {"+vxlanVds+" VNI "+vni+" multicast addr "+multicastIp+"} is not synchronized with NSX Manager.