Network PC World

This error occurs repeatedly while adding ESXi host to the Nexus 1000v. The problem seems with the VMWare Update Manager (VUM) that it doesn't initiate the required VEM module for the installation on the ESXi host we are adding to the Nexus 1000v. I solved my problem by manually installing the .vib file on the ESXi host. And here are the steps to follow. Go to the Nexus 1000v through web browser You get list of links to download files, download your required .vib file from there. for me it was Cisco_bootbank_cisco-vem-v340-esx_5.2.1.3.2.8.0-6.0.1.vib Upload that vib file to the ESXi host with WinSCP, say in the /tmp folder Run following command to install the .vib file .i.e. the vem module. esxcli software vib install -v /tmp/Cisco_bootbank_cisco-vem-v340-esx_5.2.1.3.2.8.0-6.0.1.vib After the .vib file has been installed successfully, add the ESXi host to the Nexus 1000v.

After the VMWare upgrade from 5.x to 6.x and Nexus 1000v upgrade from 4.2 to 5.2 you are unable to add new hosts into the Nexus 1000v distributed switch, although the older hosts are seed added to the N1Kv distributed switch and running fine without any issues. This happens because Nexus 1000v has no knowledge of new versions of vCenter Server in its postgress database. You have to manually add the new version in the vCenter database to support the new Version. First you need to log in the the VCDB on command line, and for that you need to find the userID and password. To get the userID and password, open C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties vcdb.properties file contents should look like this driver = org.postgresql.Driverdbtype = PostgreSQLurl = jdbc:postgresql://localhost:5432/VCDB username = vc password = {FNr2Aad>ws8Xo<Q password.encrypted = false Grab the username and password (default userID happend to be "vc" and th...