Alarms triggered in NSX Manager indicating that the UI is inaccessible as the Proton service is going down intermittently.

Products

• VMware NSX

Issue/Introduction

• The status of the cluster reports that the manager service down intermittently.

Environment

VMware NSX NSX 4.2.2.1

Cause

• The issue was due to the presence of  a stale TZP in the NSX manager
• The proton & tanuki logs have the following entries which indicate the presence of a stale TZ 

>> var/log/proton/nsxapi.log

12722:2025-09-17T13:58:17.016Z INFO Thread-29 HeartbeatServiceClientImpl 1988293 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Stopping heartbeat for entity: PROTON
66801:2025-09-17T14:02:47.927Z INFO Thread-29 HeartbeatServiceClientImpl 1995148 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Stopping heartbeat for entity: PROTON

>> var/log/corfu/tanuki.log

INFO | jvm 3 | YYYY/MM/DD 21:52:39 | java.lang.NullPointerException: Cannot invoke "com.vmware.nsx.management.model.switching.transportzoneprofile.TransportZoneProfileTypeIdEntry.getBuilder()" because "value" is null
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.model.TransportZone.lambda$setTransportProfileIds$1(TransportZone.java:147)
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at java.base/java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.model.TransportZone.setTransportProfileIds(TransportZone.java:147)
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.ufodao.TransportZoneDaoHelper.convertToManagedTransportZone(TransportZoneDaoHelper.java:159)
INFO | jvm 3 | YYYY/MM/DD 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.dao.TransportZoneQueryDao.getTransportZonesForAType_aroundBody16(TransportZoneQueryDao.java:431)
INFO | jvm 3 | 2025/09/17 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.dao.TransportZoneQueryDao$AjcClosure17.run(TransportZoneQueryDao.java:1)
INFO | jvm 3 | 2025/09/17 21:52:39 | at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
INFO | jvm 3 | 2025/09/17 21:52:39 | at io.micrometer.core.aop.TimedAspect.processWithTimer(TimedAspect.java:119)
INFO | jvm 3 | 2025/09/17 21:52:39 | at io.micrometer.core.aop.TimedAspect.ajc$inlineAccessMethod$io_micrometer_core_aop_TimedAspect$io_micrometer_core_aop_TimedAspect$processWithTimer(TimedAspect.java:1)
INFO | jvm 3 | 2025/09/17 21:52:39 | at io.micrometer.core.aop.TimedAspect.timedMethod(TimedAspect.java:97)
INFO | jvm 3 | 2025/09/17 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.dao.TransportZoneQueryDao.getTransportZonesForAType(TransportZoneQueryDao.java:417)
INFO | jvm 3 | 2025/09/17 21:52:39 | at com.vmware.nsx.management.switching.infrastructure.service.DefaultTransportZones.init(DefaultTransportZones.java:59)
INFO | jvm 3 | 2025/09/17 21:52:39 | at com.vmware.nsx.management.policy.policyframework.sharding.PolicyInitializer.lambda$processInitializerQueue$0(PolicyInitializer.java:141)
INFO | jvm 3 | 2025/09/17 21:52:39 | at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source)
INFO | jvm 3 | 2025/09/17 21:52:39 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO | jvm 3 | 2025/09/17 21:52:39 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO | jvm 3 | 2025/09/17 21:52:39 | at com.vmware.nsx.util.concurrent.Executors$MeteredRunnable.run(Executors.java:353)
INFO | jvm 3 | 2025/09/17 21:52:39 | at java.base/java.lang.Thread.run(Unknown Source)



Resolution

• The issue is resolved in NSX Version 9.1.0.0.24958816.
• If the above logs matches in the NSX manager please open a Broadcom Technical Support case. For more information, see How to Submit a Support Request