The first step in the NSX infrastructure upgrade process is the NSX Manager appliance upgrade.
Before you begin
Verify you have completed all the upgrade preparation tasks described in Preparing for the vCloud Networking and Security to NSX for vShield Endpoint Upgrade.
Verify that vShield Manager has sufficient disk space for the upgrade to NSX Manager. See System Requirements for NSX for vShield Endpoint.
Increase the vShield Manager virtual appliance's reserved memory to at least 16 GB and allocate 4 vCPU before upgrading to NSX 6.2.x.
About this task
Do not uninstall a deployed instance of vShield Manager appliance.
- Download the NSX upgrade bundle to a location to which vShield Manager can browse. The name of the upgrade bundle file is similar to VMware-vShield-Manager-upgrade-bundle-to-NSX-release-buildNumber.tar.gz.
- From the vShield Manager 5.5 inventory panel, click Settings & Reports.
- Click the Updates tab and then click Upload Upgrade Bundle .
- Click Choose File, select the VMware-vShield-Manager-upgrade-bundle-to-NSX-release-buildNumber.tar.gz file, and click Open.
- Click Upload File.
Uploading the file takes a few minutes.
- Click Install to begin the upgrade process.
- Click Confirm Install. The upgrade process reboots vShield Manager, so you might lose connectivity to the vShield Manager user interface. None of the other vShield components are rebooted.
- After the reboot, log in to the NSX Manager virtual appliance by opening a Web browser window and typing the IP address, for example, https://10.10.10.10. The upgraded NSX Manager has the same IP address as the vShield Manager.
The Summary tab displays the version of NSX Manager that you just installed.
- Navigate to and verify that the vCenter Server status is Connected.
- Close any existing browser sessions accessing the vSphere Web Client. Wait a few minutes and clear the browser cache before logging back in to the vSphere Web Client.
- If SSH was enabled on vShield Manager, you must enable it on NSX Manager after the upgrade. Log in to the NSX Manager virtual appliance and click View Summary. In System-level components, click Start for SSH service.
After upgrading from vCloud Networking and Security 5.x to NSX 6.x, you must use your CLI administrative login credentials to log in to the NSX Manager. Previously, in vCloud Networking and Security, two passwords were required, one for the CLI and another for the UI. Starting in NSX 6.x, only one password is required. For example:
Passwords in vCloud Networking and Security
mypassword#123 for the CLI
mypassword#456 for the UI
Passwords after upgrade to NSX
mypassword#123 for the CLI
mypassword#123 for the UI
After upgrading NSX Manager and connecting it to an existing vCenter Server, reset the Web Client server to allow for any NSX plug-ins to be upgraded as well.
In vCenter 5.5, you can do this by opening https://<vcenter-ip>:5480 and restarting the Web Client server.
In the vCenter Server Appliance 6.0, you can do this by logging into the vCenter Server shell as root and running the following commands.
Command> shell.set --enabled True Command> shell localhost:~ # cd /bin localhost:~ # service-control --stop vsphere-client localhost:~ # service-control --start vsphere-client
In vCenter Server 6.0 on Windows, you can do this by running the following commands.
cd C:\Program Files\VMware\vCenter Server\bin service-control --stop vspherewebclientsvc service-control --start vspherewebclientsvc
A restart is required to avoid unexpected errors, such as configured security groups not appearing in the Security Groups tab of Service Composer.
If the NSX plug-in does not display correctly in the vSphere Web Client, clear your browser's cache and history.
It is recommended to use different Web Clients to manage vCenter Servers running different versions of NSX Managers to avoid unexpected errors when different versions of NSX plug-ins are running.
What to do next
Create a backup of the NSX Manager. The previous NSX Manager backup is valid only for the previous release. See Back Up NSX Manager Data for vShield Endpoint.