NSX-T Manager UI reported to be inaccessible with error "Some appliance components are not functioning properly"

Products

• VMware vSAN

Issue/Introduction

• NSX-T Manager UI was inaccessible with below errors:

Some appliance components are not functioning properly.
Component health: MANAGER:DOWN, SEARCH:DOWN, UI:UP, NODE_MGMT:UP.
Error code: 101

Environment

 vSAN All Versions

Cause

This issue occurs if the host owning the NSX Manager node's namespace object goes down while its storage policy is set to FTT=0 (Failures to Tolerate = 0). Because an FTT=0 configuration provides no data redundancy on vSAN, any hardware failure on the host storing this namespace object will render the object inaccessible. Consequently, the host can no longer reach the .vmx path or the underlying storage object. This loss of storage accessibility causes the VM's node services to fail, ultimately resulting in the UI becoming unreachable.

 

• nsxmgr namespace object set with storage policy FTT0.

Object UUID:
  ########-####-####-####-############
Version:
  20
Owner:
  esxi-1##
Policy:
  stripeWidth: 1
      CSN: 1044
      spbmProfileName: VM Storage Profile - FTT 0

Type:
  vmnamespace
Path:
  /vmfs/volumes/vsan:#####-######/nsxmgr-### (Exists)
Group UUID:
  ########-####-####-####-############
Directory Name:
  nsxmgr###
Configuration:

      Component: ########-####-####-####-############
        Component State: ACTIVE,  Address Space(B): 273804165120 (255.00GB),  Disk UUID: ########-####-####-####-############,  Disk Name: t10.NVMe____Dell_#####:2
        Votes: 1,  Capacity Used(B): 213909504 (0.20GB),  Physical Capacity Used(B): 209715200 (0.20GB),  Total 4K Blocks Used(B): 55701504 (0.05GB),  Host Name: esxi-1##

 

 

• In /var/run/log.hostd.log  of host  esxi-1## which is down due to hardware related issues, The nsxmgr namespace object ########-####-####-####-############ is reported to be APD state. 

This leads to :

• • • Datastore inaccessibility to nsxmgr.
    • Input/Output error when tried accessing and reading the config file.
    • Storage reports to be inaccessible

 

2026-04-10T00:41:58.114Z In(166) Hostd[2101489]: [Originator@6876 sub=VmObjectStorageMonitor] Set APD state for 'vmnamespace' object '########-####-####-####-############'

2026-04-10T00:41:59.878Z Wa(164) Hostd[2101473]: [Originator@6876 sub=Hostsvc.VmkVprobSource] Can't find datastore '########-####-####-####-############'
2026-04-10T00:41:59.878Z In(166) Hostd[2101458]: -->          value = "########-####-####-####-############"
2026-04-10T00:41:59.878Z In(166) Hostd[2101473]: [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 278273 : Lost access to volume ########-####-####-####-############ (########-####-####-####-############) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
2026-04-10T00:42:00.115Z In(166) Hostd[2101463]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] Checking for home object accessibility (VM's current state: VM_STATE_ON, stable? true)
2026-04-10T00:42:00.115Z In(166) Hostd[2101463]: [Originator@6876 sub=VmObjectStorageMonitor] Object UUID '########-####-####-####-############' class 'vmnamespace' APD state: APD

2026-04-10T00:42:00.115Z In(166) Hostd[2101463]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] UpdateStorageAccessibilityStatusInt: Vm's storage accessibility status changed to false
2026-04-10T00:42:00.115Z In(166) Hostd[2101463]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] VM config backing gone - try to mark VM invalid.
2026-04-10T00:42:00.115Z Db(167) Hostd[2101463]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] Post act MarkBadLoad requested, current None
2026-04-10T00:42:00.115Z In(166) Hostd[2101463]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] Post act set from None to MarkBadLoad
2026-04-10T00:42:10.717Z Wa(164) Hostd[2101463]: [Originator@6876 sub=IoTracker] In thread 2101462, fopen("/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx") took over 9 sec.
2026-04-10T00:42:51.431Z In(166) Hostd[2101462]: [Originator@6876 sub=Libs] DictionaryLoad: Cannot open file "/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx": Input/output error.

2026-04-10T00:42:51.434Z Er(163) Hostd[2101462]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:#####/########-####-####-####-############/nsxmgr###.vmx] Could not perform config check (storage not accessible): Fault cause: vim.fault.GenericVmConfigFault

Resolution

Change the VM Storage Policy from FTT=0 to FTT=1 for the nsx manager node.

Change the Default Storage Policy for vSAN Datastores