Symptoms:
2023-08-12 08:20:34.918 GMT ERROR http-nio-127.0.0.1-7441-exec-177 RemoteServerUtil:121 - - [nsxv@6876 comp="nsx-manager" level="ERROR" subcomp="manager"] Throwing remote base exception
com.vmware.vshield.vsm.remoting.server.exceptions.RemoteBaseException: Internal server error has occurred.
at com.vmware.vshield.vsm.remoting.server.util.RemoteServerUtil.convertException(RemoteServerUtil.java:114) [vsm-core-1.0.jar:?]
java.lang.IllegalArgumentException: No enum constant com.vmware.vshield.vsm.vdn.model.VdnHostErrorStatus.2
at java.lang.Enum.valueOf(Enum.java:238) ~[?:1.8.0_342]
at com.vmware.vshield.vsm.vdn.model.VdnHostErrorStatus.valueOf(VdnHostErrorStatus.java:1) ~[vsphere-1.0.jar:?]
at com.vmware.vshield.vsm.vdn.service.VdnInventoryServiceImpl.buildVdnInventoryHost(VdnInventoryServiceImpl.java:759) ~[vsphere-1.0.jar:?]
There was an invalid entry in the vxlan feature of the hosts in the NSX database.
There is no resolution, as there are no new NSX for vSphere releases.
Workaround:
If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.
Impact/Risks:
Unable to use host Transport Zone during migration from NSX-V to NSX-T.