A: Yes, a 4.0(4)SV1(2) VSM can run in backward compatible mode and control VEM running 4.0(4)SV1(1). Next run the following command on the VSM to make this ESX host end up as VEM module number 12 n1000v-MV# config t n1000v-MV(config)# vem 12 n1000v-MV(config-vem-slot)# host vmware id 333-5553-4537-32 When the ESX host with the UUID above is added to the N1KV it will come in as VEM module number 12 Upgrade A: Yes, users can upgrade their 4.0(4)SV1(1) VSMs and retain the existing configuration. Via CLI with the Login to the ESX box either via ssh or console access sbin#./esxcfg-info -u 333-5553-4537-32 The host id is that long string. First get the vmware host id from the ESX server. ![]() ![]() Once you know the UUID you can reserve the slot number on the VSM with the following commands. A: You need to know the UUID of the ESX host. # /usr/lib/vmware/bin/net-dvs -d -n '5b 4b 01 50 fd ae c8 79-05 1a 33 39 49 5c 5d 8b' If the above command fails with a 'bad ioctl' error then remove the VEM module completely with 'vem-remove -s -r' and rerun the 'net-dvs -d -n' command above have VMs that are inaccessible, make them accessible or remove them to get VUM to proceed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |