One of the new features of vSphere 7.0 Update 3 is that you can now manage NSX-T directly from the vSphere Client. In the new menu of the vSphere client UI, you will now find a section dedicated to NSX.
Opening this section currently brings up an NSX-T status information page. At this current stage, we are able to deploy new NSX-T instances, but existing NSX-T installations won’t be discovered.
Why is that?
As usual, a look at the Release Notes helps. There you’ll find the following statement for vCenter 7 Update 3:
You can see the vSphere Client NSX-T home page that enables the feature, but it does not work with NSX-T Data Center 3.1.x or earlier.
The most recent NSX-T version is 3.1.3 [as of 11/15/2021]. This means we have to wait for NSX-T version 3.2 until the integration works.
I’d like to point your attention to a new and useful feature which was introduced with vSphere 7 update 2. It is easily being overlooked in the abundance of new features, but it does a very good job in the prior to a vCenter update.
A requirement for the Update Planner is participation in the Customer Experience Improvement Program (CEIP).
The first sign of a new vCenter update is a notification banner at the top of vSphere Client.
Clicking on “View Updates” will take you directly to the Update Planner. This can also be found in the menu. To do this, select the vCenter in the Hosts & Clusters view and select “Updates” > vCenter Server > Update Planner in the menu bar at the top right.
All currently available updates are being displayed. In the case shown below, the vCenter is already at 7.0 Update 2, so only one possible update is listed. If several possible updates are available, the Update Planner can check the compatibility against all of them. To do this, select the radio button of the desired update (red box).
Once an update is selected, the action field “Generate Report” turns blue and shows the two possible sub-items “Interoperability” and “Pre-Update Checks“.
The Interoperability Check verifies not only the ESXi hosts but also the compatibility with other VMware products registered in vCenter.
Working with templates has become much easier in vSphere 7 since VMware added new features to content libraries. It is now possible to deploy VMs directly from templates in content libraries and to update templates while the orignal version stays in place.
If there are still classic templates in vCenter, you can clone them to a content library.
Transfer the old template to the content library as a new template.
Failed to export OVF package
After klicking OK, an error message “Failed to export OVF package” might be issued. Usually followed by a second message that leads to the root cause of the problem.
File ds:///vmfs/volumes/vsan:527a6824b9bfa7ad-36f48a2cd78b9685/1f40b55e-f88d-e569-9d66-002590bb2ed0/b02cb65d-e81b-49cb-a654-ef26ea21b2f7/ubuntu-20.04-live-server-amd64_5696e54c-c62a-4fa8-b007-0192a28ff53d.iso was not found
The only interesting part of the message are the last four words: “iso was not found“. Obviously the VM had an iso image mounted before it was converted to a template. Luckily that problem is easy to resolve by converting the template into a VM and removing the iso image from CD-ROM settings. Change it to “Client Device” for example. Convert the VM back to a template and retry cloning to content library. Without a mounted iso image the conversion works without an error.
Updates to the vCenter Server Appliance (VCSA) are usually easily done from the VAMI interface. In rare cases, however, problems may occur during the update. Recently I tried to update the VCSA in the lab from version 7.0.0 (16386335) to 7.0.0 U1 (16858589). The update was started via a locally mounted ISO image. It was detected that an update is available, but the update failed right after start. The problem referenced in the link above did not apply in this case.
In such cases it is worthwhile to try the VCSA shell. To do this, it must first be allowed in VAMI, then the session can be established via SSH client.
It is important that you’re NOT on the bash shell. You can return from bash to the VAMI shell with the command below.
In the first step the update packages are staged. The ISO should be mounted at this time.
software-packages stage --iso --acceptEulas
The process checks some requirements, detects source- and destination version and tests for a mounted iso.
software-packages list --staged
The command listed above will show details to the staged package.
If everything looks correct we can trigger the update.
software-packages install --staged
The update to version 7.0 U1 finished without any issues.