So I am assuming that if things go wrong on an ESXi environment, that there is really nothing to do but move the VMs, blow the host away and start again?
Is this case, or is there another way to remove a VEM that has gotten into a corrupt state in relation to the VSM?
I think any reset commands need to be available from the VMA shell for ESXi users who don't have a service console.
Thanks for any help,
One possible option that may give you access to net-dvs etc. commands is to access the ESXi console through unsupported mode.
Here is one link I found that has a guide regarding setting this up:
Hope this helps
Thanks for that link. I now have shell access and have been able to execute some of the commands in the FAQ. I was able to delete the DVS.
Hhowever, it appears that some of the VEM related commands are not in the specified location:
Next unload the VEM kernel module[root@cae-esx-179 ~]# /usr/lib/ext/cisco/nexus/vem-v110/sbin/hotswap.sh -uandIf the above command fails with a "bad ioctl" error then remove the VEM module completely with "vem-remove -s -r"These files do not seem to be present anywhere. Have these files moved to a different location? The /usr/lib/ext directory does not even have a "cisco" folder in it on my ESXi host.I think I am very close to having this configuration deleted. vCenter now shows the dvs as "down". I am wondering if vCenter has something in it's database that shouldn't be there. I can't find any paths containing "cisco, "nexus", etc., so I am wondering if the VEM is already gone from the host, but something is hanging around in vCenter's DB....Thanks for any additional insight you can provide,Nathanael