When configuring ESXi hosts in NSX-T "Some error has occurred in service insertion module. (Error code: 9539)"

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

• When installing or reconfiguring VMware NSX-T on an ESXi host using a VDS host switch, you see the error "Some error has occurred in service insertion module. (Error code: 9539)"
• In the /var/log/proton/nsxapi.log file on an NSX-T manager, you see entries similar to: "Multiple DVS objects found with same VC UUID" , "Multiple VDS found by UUID"

2021-03-31T10:48:17.494Z  WARN http-nio-127.0.0.1-7440-exec-5 DVSFinderImpl 14528 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" reqId="#####-####-####-####-#############" subcomp="manager" username="admin"] Multiple DVS objects found with same VC UUID ###############, switches size 2
2021-03-31T10:48:17.494Z ERROR http-nio-127.0.0.1-7440-exec-5 SwitchingValidator 14528 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP9539" level="ERROR" reqId="#####-####-####-####-########" subcomp="manager" username="admin"] Multiple VDS found by UUID : ###############
2021-03-31T10:48:17.494Z ERROR http-nio-127.0.0.1-7440-exec-5 JsonRpcErrorResolver 14528 - [nsx@6876 comp="nsx-manager" errorCode="MP100" level="ERROR" subcomp="manager"] Error discovered by JSON RPC 
 com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
        at com.vmware.nsx.management.switching.common.SwitchingValidator.getDvsByHostSwitchId(SwitchingValidator.java:997) ~[libnsx-switching.jar:?]

 

• While configuring  Transport Node Profile (TNP) 

2025-##-##T02:26:06.180Z ERROR http-nio-127.0.0.1-7440-exec-14 TransportNodeProfileServiceImpl 6116 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP9539" level="ERROR" reqId="bd87aca0-####-####-####-4eb40433df8d" subcomp="manager" username="admin"] Multiple VDS found by UUID : 50 ## ## ## ## ## ## ##-## ## ## ## ## 50 cb ae.
2025-##-##T02:26:06.180Z  WARN http-nio-127.0.0.1-7440-exec-14 PolicyResourceChangeNotificationManager 6116 POLICY [nsx@6876 comp="nsx-manager" level="WARNING" reqId="bd87aca0-####-####-####-4eb40433df8d" subcomp="manager" username="admin"] Failure received invoking listener PolicyHostTransportNodeProfileNotificationListener for change CREATING on resource /infra/host-transport-node-profiles/TNP_
UDC_-_DEV
com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
        at com.vmware.nsx.management.switching.common.SwitchingUtils.getDvsByHostSwitchId(SwitchingUtils.java:1952) ~[?:?]
        at com.vmware.nsx.management.switching.common.SwitchingUtils.isDvsSnicOffloaded(SwitchingUtils.java:2583) ~[?:?]
        at com.vmware.nsx.management.switching.common.SwitchingUtils.isDvsSnicOffloaded(SwitchingUtils.java:2576) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeProfileServiceImpl.validateHostSwitchSpec(TransportNodeProfileServiceImpl.java:1099) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeProfileServiceImpl.validateTransportNodeProfileConfig(TransportNodeProfileServiceImpl.java:1290) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeProfileServiceImpl.validateGlobalTNPConfig(TransportNodeProfileServiceImpl.java:332) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeProfileServiceImpl.validateTransportNodeProfileConfigs(TransportNodeProfileServiceImpl.java:299) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeProfileServiceImpl.preCreate(TransportNodeProfileServiceImpl.java:289) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.PolicyHostTransportNodeProfileNotificationListener.preCreate(PolicyHostTransportNodeProfileNotificationListener.java:92) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.PolicyHostTransportNodeProfileNotificationListener.handleResourceChange(PolicyHostTransportNodeProfileNotificationListener.java:82) ~[?:?]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center
VMware NSX

Cause

The issue occurs when vCenter has more than one VDS with the same UUID.

Resolution

NSX-T expects a unique VDS UUID on each vCenter.

Workaround:
Please make sure there are no duplicate VDS' on vCenter. You may need to create a new one and use that for NSX-T or remove the duplicate VDS.