- NSX 3.2.x
- The environment at one time ran NSX version 3.1.1
- VMs on a specific segment lose networking due to their ports being blocked
- On ESXi, the command net-dvs shows the VM port is blocked e.g.
net-dvs
port ########-####-####-####-############:
com.vmware.common.port.alias = ########-####-####-####-############ , propType = CONFIG
com.vmware.common.port.connectid = 1676471471 , propType = CONFIG
com.vmware.common.port.block = true , propType = CONFIG
com.vmware.common.port.backingType = nsx , propType = CONFIG
- NSX Manager syslog has an exception similar to this example
2023-02-15T11:50:45.694Z ERROR providerTaskExecutor-43 LogicalSwitchServiceImpl 2730 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP8005" level="ERROR" subcomp="manager"] Identifier LogicalSwitch/########-####-####-####-############ specified in the create call for entity LogicalSwitch already exists in the system.
2023-02-15T11:50:45.694Z ERROR providerTaskExecutor-43 PolicyProviderUtil 2730 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500015" level="ERROR" subcomp="manager"] Unexpected exception received during provider invocation.
com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
at com.vmware.nsx.management.switching.logicalnetwork.service.LogicalSwitchServiceImpl.validateLogicalSwitch(LogicalSwitchServiceImpl.java:593) ~[?:?]
at com.vmware.nsx.management.switching.logicalnetwork.service.LogicalSwitchServiceImpl.create(LogicalSwitchServiceImpl.java:690) ~[?:?]
at com.vmware.nsx.management.policy.providers.switching.SegmentProviderNsxT.createLogicalSwitchOnNSX(SegmentProviderNsxT.java:915) ~[?:?]
at com.vmware.nsx.management.policy.providers.switching.SegmentProviderNsxT.handleConnectivityChange(SegmentProviderNsxT.java:410) ~[?:?]
at com.vmware.nsx.management.policy.providers.switching.SegmentProviderNsxT.handleSegmentChange(SegmentProviderNsxT.java:251) ~[?:?]