NSX Native Loadbalancer VIPs are unreachable.

Products

• VMware NSX

Issue/Introduction

• The NSX VIP hosted on the Tier-1 Load Balancer is not reachable via ping.
• Proxy ARP entry for the VIP is missing in the following:

1. 1. In the Edge node's nestDB.
   2. In the controller’s adaptor_ufo_dump under ArpTableConfigMsg.

• Logs below  entry canCurrentNodeProcess : false can be observed, which indicates that the manager is not the owner of the entity and is unable to process the request for LRServiceIPWorker
  
  NSX-T manager's /var/log/proton/nsxapi.log : 

2025-09-26T06:50:11.101Z INFO policyProviderTaskScheduler-4 WorkerShardManager 4567 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] canCurrentNodeProcess : false, <<<<<<<<---------
for worker : LRServiceIPWorker, for workItem : WorkItem{identifier=LrServiceIpMapping/XXXXXXXXXXXXXXXXXXXXXXX, Timestamp{epoch=28699, address=11827091377}}

Environment

VMware NSX

Cause

The worker framework gets unsubscribed from the corfu listener and is unable to resubscribe again.
From the logs above, entry canCurrentNodeProcess : false can be observed, which indicates that the manager is not the owner of the entity and is unable to process the request.

 

Resolution

Permanent Fix

This issue has been resolved in NSX-T 3.2.3 and 3.2.4 & above.

 

Workaround

If you are unable to upgrade immediately, perform a rolling reboot of the NSX Managers.

• This initiates a full synchronization and re-subscribes the worker framework to the Corfu stream listener. After the reboot, Proxy ARP entries for the affected VIPs will be properly realized & The VIPs should then become reachable as expected.

 

 

Additional Information

For details, refer to the VMware NSX-T Data Center 3.2.3 Release Notes, under Resolved Issues, Fixed Issue ID: 3052786.

NSX-T 3.2.3 Release Notes