Hello!
A have a cluster of 6 hosts running ESXi 5.5, v 1331820. All are joined to a v5.5 dvSwitch named "dvSwitch-Nexus"
When I attempt to vMotion a VM from one host to another, I recieve the message "currently connected network interface 'Network adapter 1" uses network "dvSwitch-Nexus" which is not accessable."
When I searched on this error, it was in reference to migrations between different dvSwitches. But in this case, all of the hosts and the VM in question are all attached to the same dvSwitch.
Now, I have vCenter Operations running, and they're reporting that my hosts lost network redundancy. But all of them have dual NICs online and operational. I've taken each NIC out of the active order individually, triggered the alert on the host itself, then readded it to make it go away. But the vCOPS error remains. Not sure if this is related.
The only other thing I can think of that might be related to this issue is the LAG I originally set up. My hosts are Cisco UCS B200 M3s, and after some reading and consultation with our Cisco engineer, we removed the LAGs and migrated the interfaces back to standard uplinks. The vCOPS error seems to have begun soon after those were migrated back and the LAG removed. But even with two active uplinks and everything looking visible, I still can't vmotion across my dvSwitch.
My next step would be to remove the hosts from the dvSwitch and readd them, but I've VMs running on all of the hosts and because I can't vMotion them off, removing the hosts will be difficult. I can create standard portgroups and migrate them to those, and move the uplinks over to standard switches, but before I start down that path I thought I'd consult you all since there may be something I missed.
Any help or suggestions would be great, and I'm happy to answer any further questions. Many thanks!