Yesterday was a very exciting day, VMware finally announced the new vCloud Suite 5.1. With new products and features announced, each one of them as great as ever.
But yours truly decided that instead of presenting you a generic “What’s new” post it was more interesting, at least for me and hope also to you, to focus in one of my favorite pieces of vSphere, the vCenter Server Virtual Appliance and in a couple of articles describe what new features are coming and how to perform an upgrade from 5.0 to 5.1.
What’s new in the VCSA 5.1
With this new release of the vCenter Server VA a few new features have been added, most of them related to the WebUI and to the new features and services that have been released globally for the vCenter 5.1, Windows and Linux based versions.
These new enhancements can be seen in the Summary section of the vCenter Server Tab as shown in the screenshot below.
From here all the vCenter Service can be started and stopped. The Services Tab no longer exists and it’s now a section of the vCenter Server Tab.
In the Storage Usage are you can check the disk usage of the different components of the VCSA.
There is also a Utilities are where you can:
- Generate a support bundle in case of an incidence with the vCenter Server.
- Download the configuration file of the VCSA and then open it in your favorite text editor.
- Launch again the Setup Wizard to configure the VCSA from scratch or make modifications to some of he initial settings.
- Upload the Windows Sysprep files to the vCenter VA.
- For this last option the procedure is quite simple. Click the
A new windows will open, select the operating system and browse for the location of the files.
The files will be uploaded to /etc/vmware-vpx/sysprep/<OS>.
Additionally in the vCenter Server Tab two new sections have been added.
The Service section where the VCSA administrator can setup:
- ESXi Dump Collector repository size
- vSphere Auto Deploy repository size
- Inventory size
The SSO section. Here you can configure all the settings related to the newly introduced Single Sign On server.
In the next post we will discuss about VCSA 5.1 initial deployment and how to upgrade from 5.0 and 5.1.
As he said it would be tremendously useful if you need to physically replace the server and don’t want to modify all your storage infrastructure, it’s easier to just modify the iqn of the new server and set it to the old name.
The task is as easier as the one described in last post. Using esxcli command with the iscsi namespace you can change the name and the alias of the adapter.
As a precaution first retrieve the current iqn to check that it’s the correct server.
To change the name you have to provide the adapter and the new name.
Hope you find this useful, any comments and suggestions are welcome as always.
Back in 2010 I wrote a post about how to get the iSCSI iqn of an ESXi 4.x server using vSphere CLI from the vMA or any other system with the vCLI installed on it.
The method described in that article is still valid for ESXi 5.0 since the old vicfg and esxcfg commands are still available, however with 5.0 version you can get a similar result using the new esxcli namespaces, following is how to do it.
First task is to get a list of the iSCSI HBAs in order to know the name of the software iSCSI initiator.
Next we get the info of the adapter.
Look at the Name field to get the iqn and we are done.