After an upgrade to NSX 9.0, the NSX UI is intermittently inaccessible. On the Appliances page, the cluster status shows as Unavailable and there are no details for any of the manager nodes

Products

• VMware NSX

Issue/Introduction

• NSX was recently upgraded to version 9.0
• The NSX UI is intermittently inaccessible. You may see a message similar to the following:
  
  Some appliance components are not functioning properly.
Component health: MANAGER:DOWN, SEARCH:DOWN, UI:UP, NODE_MGMT:UP.
Error code: 101
  
  
• When the UI is accessible, the System > Appliances page shows the cluster status as Unavailable.
• On the same page, the Service Status, CPU, Memory and Storage details are blank for all nodes.
• On the System > Fabric > Transport Zones page, there is no transport zone named nsx-vlan-transportzone. There is a VLAN backed transport zone present with the Default tag applied.
• When the get cluster status command is run as the admin user from one of the manager nodes, most services have a status of UP, but SHA, APPLIANCE_PROXY and SEARCH have a status of UNKNOWN for all manager nodes. Checking the status of any of these services individually (via get service <service name>) shows that they are in a running state.
• Checking the status of the proton service as the root user via the systemctl status proton command shows that the proton service has been restarted since the last time the node was booted.
• Messages similar to the following are seen in the /var/log/proton/nsxapi.log file:
  
  

  2025-08-20T13:56:12.850Z  INFO PolicyInitializer-1-4 DefaultTransportZones 1512839 FABRIC [nsx@4413 comp="nsx-manager" level="INFO" subcomp="manager"] DefaultTransportZones creating default TZs
  ...
  2025-08-20T13:56:12.863Z  INFO PolicyInitializer-1-4 PolicyServiceImpl 1512839 POLICY [nsx@4413 comp="nsx-manager" level="INFO" subcomp="manager"] Entity /infra/sites/default/enforcement-points/default/transport-zones/a95c914d-748d-497c-94ab-10d4647daeba does not exist, creating
  ...
  2025-08-20T13:56:12.874Z  INFO PolicyInitializer-1-4 TransportZoneNotificationListener 1512839 FABRIC [nsx@4413 comp="nsx-manager" level="INFO" subcomp="manager"] TransportZoneNotificationListener preCreate with NotificationContext{resource=PolicyTransportZone{tzType=VLAN_BACKED, nsxId='00000000-0000-0000-0000-000000000000', uplinkTeamingPolicyNames=null, isDefault=true, hostSwitchId=null, transportZoneProfilePaths=null, transportProfileIds=null, transportProfileChanged=false, nestedVdrMacAddress=null, isSecurityTZ=false, forwardingMode=null, authorizedVlans=null}[policyPath=/infra/sites/default/enforcement-points/default/transport-zones/a95c914d-748d-497c-94ab-10d4647daeba, markedForDelete=false], previousStateIfAny=null, path=/infra/sites/default/enforcement-points/default/transport-zones/a95c914d-748d-497c-94ab-10d4647daeba, change=CREATING, ufoTxn=org.corfudb.runtime.collections.TxnContext@16d8c95}
  ...
  2025-08-20T13:56:12.875Z ERROR PolicyInitializer-1-4 TransportZoneServiceImpl 1512839 FABRIC [nsx@4413 comp="nsx-manager" errorCode="MP8109" level="ERROR" subcomp="manager"] VLAN default TransportZone <TZ Name> already exists
  ...
  2025-08-20T13:56:12.876Z  WARN PolicyInitializer-1-4 PolicyResourceChangeNotificationManager 1512839 POLICY [nsx@4413 comp="nsx-manager" level="WARNING" subcomp="manager"] Failure received invoking listener TransportZoneNotificationListener for change CREATING on resource /infra/sites/default/enforcement-points/default/transport-zones/a95c914d-748d-497c-94ab-10d4647daebacom.vmware.nsx.management.switching.common.exceptions.SwitchingException: null

Environment

VMware NSX 9.0

Cause

Prior to the upgrade to 9.0, the pre-installed default VLAN transport zone, nsx-vlan-transportzone, had been deleted and replaced with a different default VLAN-backed transport zone. NSX will attempt to create the nsx-vlan-transportzone VLAN-backed transport zone and mark it as default, and will fail repeatedly, causing the proton service to restart.

Resolution

This is a known issue impacting VMware NSX. There is currently no resolution.

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Additional Information

If you are contacting Broadcom support about this issue, please provide the following:

• NSX Manager support bundles.
• The PolicyTransportZone.txt file generated by running the following command on one of the manager nodes:
  
  /opt/vmware/bin/corfu_tool_runner.py -o showTable -n nsx -t PolicyTransportZone > PolictyTransportZone.txt