NSX Manager UI and API are inaccessible via the Virtual IP (VIP) and individual node IPs.
search cancel

NSX Manager UI and API are inaccessible via the Virtual IP (VIP) and individual node IPs.

book

Article ID: 437669

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX Manager UI and API are inaccessible via the Virtual IP (VIP) and individual node IPs.



  • One or more NSX Manager nodes report services in a "DOWN or DEGRADED" state when running get cluster status from the CLI.

  • Specific services such as HTTPS, MANAGER, and DATASTORE are reported as DOWN on the affected nodes.

  • vCenter or ESXi logs may show storage accessibility errors for the NSX Manager appliance disk files under hostd logs /var/run/log/hostd (e.g., Could not perform config check (storage not accessible)) 

    Hostd[210##73]: [Originator@6876 sub=Hostsvc.VmkVprobSource] Can't find datastore '7d5xxxx-c2fa-1e44-xxxx-0c42xxxxx65c'>> Datastore mapped to NSX manager nodes.
    Hostd[210###2]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:xx/7d5xxxx-c2fa-1e44-xxxx-0c42xxxxx65c/nsxmgr.vmx] Could not perform config check (storage not accessible): Fault cause: vim.fault.GenericVmConfigFault

Environment

VMware NSX

Cause

  • This issue occurs due to a Double-Point Failure within the NSX Management Cluster that results in a loss of quorum. A three-node cluster requires at least two healthy nodes to remain operational.

  • Running NSX Manager on vSAN with no redundancy (FTT=0) creates a single point of failure. Unlike mirrored configurations, an FTT=0 setup has no alternate data components to fail over to during a brief network or storage outage, leading to a permanent loss of node availability until manual intervention or backup restoration occurs.

Resolution

Step 1: Restore Underlying Stability:

  • Ensure the ESXi host for the hardware-failed node is repaired or the VM is moved to a healthy host.
  • Verify that vSAN datastore connectivity has been restored. Check for Successfully restored access to volume events in the ESXi hostd logs.

Step 2: Prevent Recurrence: (Actionable Recommendation)
To prevent future quorum loss during single-point storage outages, update the storage policy for all NSX Manager appliances:

  • Log in to vCenter Server.
  • Locate the NSX Manager VMs.
  • Edit the VM Storage Policy and change it from FTT=0 (No redundancy) to at least FTT=1 (RAID-1 Mirroring).
  • Wait for the vSAN objects to finish resynchronizing.

Impact / Risks :
Setting NSX Managers to FTT=0 is not recommended for production environments as it removes the software-defined high availability benefits of vSAN for the management plane.

Additional Information

Powered by Wolken Software