NSX-T ESXi host configuration fails with error "Some error has occurred in service insertion module. (Error code: 9539)"
search cancel

NSX-T ESXi host configuration fails with error "Some error has occurred in service insertion module. (Error code: 9539)"

book

Article ID: 317156

calendar_today

Updated On:

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)"
  • During Transport Node Profile (TNP) creation, you see the error "Some error has occurred in service insertion module. (Error code: 9539)"
  • This issue has been observed in environments with multiple VS configurations and Multiple Compute Managers
  • 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-MM-##T##:MM:SS.494Z  WARN http-nio-127.0.0.1-7440-exec-5 DVSFinderImpl 14528 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" reqId="<UUID>" subcomp="manager" username="admin"] Multiple DVS objects found with same VC UUID <UUID>, switches size 2
2021-MM-##T##:MM:SS.494Z ERROR http-nio-127.0.0.1-7440-exec-5 SwitchingValidator 14528 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP9539" level="ERROR" reqId="<UUID>" subcomp="manager" username="admin"] Multiple VDS found by UUID : <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) 

    2026-MM-DDTHH:MM:SS.1522 ERROR http-nio-127.0.0.1-7440-exec-12 TransportNodeServiceImpl 6056 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP9539" level="ERROR"reqId="<UUID> subcomp="manager" username="admin] Multiple VDS found by UUID : ## ## ## ## ## ## ## ##-## ## ## ## ## ## ##.
    2025-MM-DDTHH:MM:SS.180Z  WARN http-nio-127.0.0.1-7440-exec-14 PolicyResourceChangeNotificationManager 6116 POLICY [nsx@6876 comp="nsx-manager" level="WARNING" reqId="<UUID>" subcomp="manager" username="admin"] Failure received invoking listener PolicyHostTransportNodeProfileNotificationListener for change CREATING on resource /infra/host-transport-node-profiles/TNP_<Name>
    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) ~[?:?]
            ...
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
VMware NSX 4.2.3.1

Cause

  • vCenter contains multiple Distributed Virtual Switches (VDS) sharing the same UUID, causing a conflict during NSX-T service insertion/fabric configuration.
  • NSX is configured with multiple Compute Managers (vCenters), where multiple vCenters have a Distributed Virtual Switches (VDS) sharing the same UUID

 

Resolution

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

Workaround:

  1. Verify VDS UUIDs in vCenter
    • Connect to your vCenter MOB as an administrator (Example: https://<vCenter.FQDN/mob)
    • Click on "content"
    • Click on "group-d1"
    • Click on the appropriate Datacenter (Example: "datacenter-3")
    • Click on the network folder (Example: "group-n7")
    • Look for object references in the form of "dvs-###" or additional network subfolders

  2. Identify duplicates
    • From the previous step click on any "dvs-###" objects that were found and examine their properties.
    • The "name" row will contain a "string" with the vCenter WebUI name given to the dvSwitch
    • The "uuid" row will contain a "string" with the dvSwitch UUID in the form of "50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##"



    • Compare the UUID values between your Distributed Switches to find which are duplicates

  3. Create a new Distributed Switch or remove the least priority duplicate.