Old and new NSX-T segments are not available in vCenter for specific host(s)

Products

• VMware NSX

Issue/Introduction

• Old and new NSX-T segments are not available under vCenter for specific host(s) (Host > Networks). While browsing DVS level, all the segments are available.
• From desired_state_manager.json, we see "partial_success" for some logical switches states as shown below:
  "logical_switch_id": "#####-####-#####-#########",
          "state": "partial_success"
        }
• From nsx-syslog on host logs, we see the following error "did not apply logical switch ##### to hosted because del nsx is running"
  2024-02-21T16:26:53.297Z nsx-opsagent[2117551]: NSX 2117551 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="2118005" level="INFO"] [CallVimOpaqueNetwork] did NOT apply logical switch [uuid=#####-####-#####-#########] to hostd because del nsx is running
  
  
  
  

Environment

VMware NSX-T Data Center

Cause

A potential cause is that the host(s) impacted were re-prepared with NSX-T without successfully deleting the earlier nsx components on the hosts.

Resolution

This issue is resolved in VMware NSX 3.2.4, NSX 4.2.0 and higher, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround:

• Restart the opsagent at the host side with : /etc/init.d/nsx-opsagent restart
• Verify if the Segments are now realized.
• If the issue persists, we may need to take the following additional steps:
  • Unprepare the TN completely.
  • Prepare the TN again.
    
    

Additional Information

Impact/Risks:
Old and new NSX-T segments are not available under vCenter for specific host(s) (Host > Networks). While browsing DVS level, all the segments are available.