If the previously created switches before the upgrade to 6.2.4 continues to work, but new Logical Switchces can not be created, then creation of LS may be broubleshoot. During the Logical Switch creation, NSX Manager sends the necessary API commands to the Controllers and vCenter Server. Controllers create the LS, and vCenter server creates a Port Group for this logical switch.
The error shows that VNI 5003 is assigned to the switch by the NSX Manager, so NSX Manager logs about this Vxlan may be helpful:
- Are there any error messages about the creation of the LS on NSX Manager:
show manager log reverse
2. show logical-switch list all --> If NSX Manager has created the LS, this sould be listed with the Name and the VNI
So it may be possible that controllers know about this LS. To check if the Controllers know about this LS is it possible to send the output of this command: (from the Controller CLI)
2. show control-cluster logical-switches vni 5003
and previously created LS as show control-cluster logical-switches vni 5001
If thecontroller part is successful, then most probably vCenter cannot create the Port Group. It can be concentrated on vCenter and ESXi hosts.
3. From one ESXi host:
esxcli network vswitch dvs vmware vxlan network list --vds-name Name_of_the-dVS_for_Vxlans--> This command should list VNI 5003 along with previously created VNIs. If 5003 is not listed then vCenter cannotcreate publish the Port Group to ESXi hosts.
(This link may be helpful for other commands)
https://vcdx133.com/2015/05/14/nsx-v-troubleshooting-deep-dive/
LACP Teaming Policy does not support Multiple vTEPS, is it also possible to check single vtep is used for ESXi hosts?
http://www.routetocloud.com/2014/05/nsx-and-teaming-policy/
