Skip to main content

Unable to See and add new ESXi hosts in 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\ file contents should look like this

driver = org.postgresql.Driverdbtype = PostgreSQLurl = jdbc:postgresql://localhost:5432/VCDB
username = vcpassword = {FNr2Aad>ws8Xo<Qpassword.encrypted = false

Grab the username and password (default userID happend to be "vc" and the password

To add the new version

Go to this Path on DOS Prompot
C:\Program Files\VMware\vCenter Server\vPostgres\bin\

Run Command
C:\Program Files\VMware\vCenter Server\vPostgres\bin>psql -U vc VCDB
Enter password as found above in the the file at C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\
Password for user vc:

Show database

Insert the new version into the database with follwoing command

Here 42 is the device ID and can be seen in the first column of the output of command

Again show the database bases, it should now list the support for vCenter 6.0+ version.

Show database

You should see the New vCenter version has been added to the database.

Exit the Database command prompt by typing \q

Restart the vCenter Server and add the hosts to Nexus 1000v normally.

Popular posts from this blog

How to check Gray-log current running version

If you planning to upgrade your graylog and want to see what your graylog current version is, here is how you can check it. Go to the Graylog Web Interface Click on System/Nodes Under System/Nodes --- Click on the N odes  Scroll down to the ' System ' Here you can see the current version of your graylog server

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine. What worked for me, is 1. Uncheck the "Connected and Connect at power on" from Device Status. 2. Then Change the Device type from " Datastore ISO File to Client Device " Radio Button 3. and press OK to save the changes. Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui where it asks "The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?" You need to select yes to eject the CD-ROM and then remove the ISO file successfully.

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.