We have a 4-node cluster with NSX 6.4.4 and recently I noticed a strange thing I'd like to have a check with the community.
I noticed on one host, that was brought back from maintenance, that the virtualwire port groups related to the stretched VLANs are not present on dVS of the host
However after moving a VM, attached to one of the stretched VLAN, to that host works fine and the VM is reachable and the portgroup, then, shows up in the dVS on the vcenter.
Is this an expected behavior ?
thanks
SC
I believe you are referring to Stretched VXLAN not Stretched VLAN? In both the cases, Port group must show in DVS. Have you validated the Portgroup via ESXCLI when it was not showing in vCenter Server GUI?
hello @Sreec
Yes I'm referring to Stretched VXLAN.
Port groups are shown in the "networks" tabs in vcenter on the dVS, what I'm referring to is the "virtual switch" tab in the host configuration settings.
The host has the dVS in its configuration tab, and a standard virtual switch, but it doesn't show any of the dvpg defined in the dVS.
Only after moving a VM, which is using one dVPG, the corresponding dVPG is shown in the host's configuration.
It happens with all distributed port group, not only with those related to NSX VXLAN
I suppose this would be normal behavior but never noticed that
That is correct, only when we connect a VM to a port group it will leverage the virtual port on DVS/VSS. That is the reason U.I output is showing like that. You can certainly check this behavior from Networking->DVS-> Lite Topology view, Port-ID view, or using CLI commands on Host.
To fix event code 1942 Critical The backing portgroup [moid = {#}] of LogicalSwitch {#} is marked as missing.
In the vSphere Web Client, navigate to Home > Networking & Security > Logical Switches.
In the Status column, click the Out of sync link to see the detailed reason for this out of sync state
Click the Resolve button to resolve the issues This invokes API to recreate the backup DVPG.
There was a request to create a port group for a vApp network when deploying a vApp from the vcloud director. But due to some reason the port group was created and removed in the dvsiwtch, and in my case, the vApp was deleted from the vCloud director so the network also removed from the VC and NSX. If there is an error on the NSX UI follow the below solutions,
Your work is just excellent. I really love your work and thanks for sharing.