NSX Native Load Balancer and Virtual services are stuck in Unknown state.

Products

• VMware NSX

Issue/Introduction

• NSX Native Load balancers and Virtual servers status is seen in Unknown state in the NSX web GUI
• However from the command line, we see they are up and running without any production impact

edge node> get load-balancer ef0326c2-####-4c70-####-356d######## virtual-server cc4f99c3-####-47ce-####-f289######## status
Virtual Server
UUID        : cc4f99c3-####-47ce-####-f2899########
Display-Name: https-pool-load balancer
IP          : 10.#.#.#
Port        : 443
Status      : up

• Further we can notice Edge nodes status are also in Unknown status with controller connectivity unknown in the NSX web GUI but the same edge node with connected state from the edge command line.

nsxedge01> get controller
 Controller IP    Port     SSL         Status       Is Physical Master   Session State  Controller FQDN           Failure Reason        
  192.168.#.#     1235   enabled      not used            false              null              NA                       NA              
  192.168.#.#     1235   enabled      not used            false              null              NA                       NA              
  192.168.#.#     1235   enabled     connected             true               up               NA                       NA

Environment

VMware NSX

Cause

• NSX-opsagent service might not be running on the edge node and this can be confirmed by checking the nsx-opsagent-appliance status

root@edgenode:/var/log# /etc/init.d/nsx-opsagent-appliance status
  nsx-opsagent-appliance.service - NSX OpsAgent
     Loaded: loaded (/lib/systemd/system/nsx-opsagent-appliance.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Wed 2025-#-## 14:40:06 UTC; 1 week 5 days ago
   Main PID: 2916 (code=killed, signal=KILL)

• we can see the below traces in the syslog on the EDGE nodes

2026-01-06T08:08:18.380Z edgenode NSX 6501 - [nsx@6876 comp="nsx-edge" s2comp="nsx-rpc" tid="6574" level="WARNING"] RpcTransport[1] Unable to connect to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock: 111-Connection refused
2026-01-06T08:08:18.852Z edgenode NSX 1 - [nsx@6876 comp="nsx-edge" s2comp="nsx-net" tid="8" level="WARNING"] StreamConnection[219919 Connecting to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock sid:219919] Couldn't connect to 'unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock' (error: 111-Connection refused)
2026-01-06T08:08:18.852Z edgenode NSX 1 - [nsx@6876 comp="nsx-edge" s2comp="nsx-net" tid="8" level="WARNING"] StreamConnection[219919 Error to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock sid:-1] Error 111-Connection refused
2026-01-06T08:08:18.852Z edgenode NSX 1 - [nsx@6876 comp="nsx-edge" s2comp="nsx-rpc" tid="8" level="WARNING"] RpcConnection[219919 Connecting to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock 0] Couldn't connect to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock (error: 111-Connection refused)
2026-01-06T08:08:18.852Z edgenode NSX 1 - [nsx@6876 comp="nsx-edge" s2comp="nsx-rpc" tid="8" level="WARNING"] RpcTransport[0] Unable to connect to unix:///var/run/vmware/nsx-opsagent/alarms-provider-service.sock: 111-Connection refused

Resolution

Open an SSH session to the NSX edge nodes and Start the service by running this command:  /etc/init.d/nsx-opsagent-appliance restart