|
Categories: NSX

Things have been a bit busy here, so playing around with VMware’s new NSX virtual networking solution is a bit slow.

However I had some time the other day so thought Id first do an upgrade to the latest version. This started simply enough by opening an https session to the NSX Manager.

Selecting the Manage/Upgrade option..

NSX Manager ..and browsing to the upgrade file I had downloaded.

Only to  be shown the following error! Invalid upgrade bundle file ….gz, upgrade file name has extension tar.gz

NSX Upgrade Error

This must be one of the easiest fixes I’ve had to apply. Simply rename the file from *.gz to *.tar.gz and off we go..

Confirm Upgrade

Feel free to take a snapshot at this point before clicking the upgrade option. Clicking upgrade starts the process off.

Running Upgrade

All done!

Upgrade Complete

Finally a check under the controller https console that the version is reported correctly.

Check NSX Version

Thats it! Well for the Manager appliance anyway. You now go back into the Web Client and upgrade the hosts .vib components. You will see an upgrade hyperlink in the Web Client beside each host on the Host Preparation tab, clicking this will update the host VTEP and other components.

Next its the controller’s turn. VMware recommend 3 controllers for redundancy ideally hosted on a 3 node management cluster. In my case with my single nested ESXi server I was only running one.

You need an SSH host to serve up the *.nub upgrade file. I just used the VMFS and accessed the file via the vSphere host.

First copy the file to the SSH host using whatever tool to hand. I used filezilla. Then after logging into the Controller shell, use the copy file command to copy the upgrade file to the controller appliance.

Copy File

Run the install software-update filename command and off it goes..

Install

You will get kicked off once completed and the controller will restart. Once NSX its back up you can log in and check the version is updated from 3.2.1 to 3.2.2 (6.0.3 to 6.0.4)

Please note: Its recommended to use the REST API to take a configuration snapshot. I did not do this in my test environment, but I would most definitely want to do it on any production system. The syntax is GET https://NSXManagerIPAddress/api/2.0/vdn/controller/controllerID/snapshot where controllerID is basically the display name of the controller appliance in the Web Client GUI.

At this point I added a second controller to check that the Manager would deploy the correct version. It did!

Now back to the lab. Im planning to deploy multiple layer 2 virtual lans and some routers as well as a zero trust model with the new per vm security model.

Related Post