28 Oct 2015
Originally posted on the VMware vSphere Blog.
Earlier this month, we released vSphere 6.0 Update 1. In this update we introduced some awesome new features for vCenter Server.
Let’s take a look at some of these just below:
- Installation and Upgrade using HTML 5 Installer for VCSA: The following installation and upgrade scenarios are now supported for vCenter Server Appliance using its HTML 5 installer:
- An installation using HTML 5 installer with a vCenter Server target is supported.
- An upgrade using HTML 5 installer with a vCenter Server target is not supported.
- An upgrade using command line with a vCenter Server target is supported.
- Backup and Restore with External Platform Services Controller: vCenter Server deployments with an external PSC (also called MxN) have support for backup and restoration.
- Appliance Management User Interface: An all new HTML5-based management interface for the appliance at https://<FQDN-or-IP>:5480.
- Platform Services Controller Interface: An all new HTML5-based management interface for the Platform Services Controller at https://<FQDN-or-IP>/psc/. </li> </ul>
- Interoperability: Virtual SAN and SMP-FT are interoperable.
- Hybrid Cloud Manager: Hybrid Cloud Manager has been updated for vSphere, and can be accessed directly from the vSphere Web Client.
- VCSA Authentication for Active Directory: VMware vCenter Server Virtual Appliance has been modified to only support AES256-CTS/AES128-CTS/RC4-HMAC encryption for Kerberos authentication between VCSA and Active Directory.
- Support for SSLv3: Support for SSLv3 has been disabled by default.
One additional feature that we introduced in vCenter Server 6.0 Update 1 is an in-place process for Updates in a major release (e.g. vCenter Server 6.0 to vCenter Server 6.0 Update 1) instead of the migration-based approach that was required in prior VCSA updates (e.g. vCenter Server 5.5 to vCenter Server 5.5 Update 1). With these new capabilities -- and, of course, resolved issues -- there's been a ton of interest in how to update the VCSA to 6.0 Update 1. So, let's get started and look at the process... Before you begin the upgrade process, ensure you have a validated backup and snapshot of your VCSA 6.0 system. Note that if you're using an external deployment model (MxN), that is, you deployed an external Platform Services Controller node separately from your vCenter Server (VCSA) node and wish to update to 6.0 Update 1, the process is exactly the same for both the PSC and the VCSA. Simply update the Platform Services Controller to 6.0 Update 1 first since it provides authentication services to the vCenter Server. Once the PSC is updated and back online you can move onto your VCSA and update it to 6.0 Update 1.
- Customer Experience Improvement Program: The opt-in Customer Experience Improvement Program (CEIP) provides VMware with information that enables VMware to improve the VMware products and services and to fix problems. When you choose to participate in CEIP, VMware will collect technical information listed below about your use of the VMware products and services in CEIP reports on a regular basis. This information does not personally identify you.
Review KB 2109760 for proper update and upgrade sequencing. Now, let's step through the process to update the VCSA 6.0 (or an external PSC 6.0) to Update 1. Step 1 - Visit the VMware Product Patches section on My VMware and download the VCSA 6.0 Update 1 Full Patch (VC-6.0.0U1-Appliance > VMware-vCenter-Server-Appliance-220.127.116.1100-3018521-patch-FP.iso).
Step 2 - Mount the VCSA 6.0 Update 1 Patch ISO to your VCSA 6.0 appliance using the vSphere Web Client or even the ESXi Embedded Host Client fling. Or if you rather, simply execute a quick PowerCLI script to mount the ISO
$iso = “[mgt-ds-nfs] iso/VMware-vCenter-Server-Appliance-18.104.22.16800-3018521-patch-FP.iso”
Get-CDDrive –vm “mgmt01vc01” | Set-CDDrive -IsoPath $iso –Connected $true Step 3 - SSH into your VCSA 6.0 appliance to launch the default appliancesh interface. Note: If you have disabled the appliancesh or are connected to the appliance DCUI, simply type "appliancesh" and login with the root credentials.
Step 4 - Option A: Run the following command to stage and install the patches from the attached VCSA 6.0 Update 1 Patch ISO immediately.
software-packages install --iso --acceptEulas
Option B: If you prefer to stage the update packages before performing the installation, run the following commands in succession:
Stage the Package from ISO: software-packages stage --iso --acceptEulas
Review the Staged Packages: software-packages list --staged
Install the Staged Packages: software-packages install --staged
If errors occur during the staging or installation of the patches, enable and launch the bash shell and review the /var/log/vmware/applmgmt/software-packages.log file for additional information.
shell.set --enabled True shell cd /var/log/vmware/applmgmt/ tail software-packaged.log –n 25 Step 5 - When the installation has completed, un-mount the VCSA 6.0 Update 1 Patch ISO from your VCSA 6.0 appliance using either the vSphere Web Client or PowerCLI.
Get-CDDrive –vm “mgmt01vc01” | Set-CDDrive -NoMedia Step 6 - Next, simply reboot your VCSA by running the following command:
shutdown reboot -r "Updated to vCenter Server 6.0 Update 1"
Step 7 - Provide some time for the VCSA to reboot and start its services. You can verify that the upgrade to vCenter Server Update 1 was successful by opening a browser and connecting to the new HTML5-based Appliance Management UI (Appliance MUI) at https://<FQDN-or-IP>:5480.
Check out Matthew Meyer's post on the all new Appliance MUI, too! Once you've updated to vSphere 6.0 Update 1, you'll notice in the Appliance MUI that we've re-introduced patching capabilities. For future updates, you'll no longer need to update from the applaincesh. Instead you can use the HTML5-based UI to patch from an ISO or even better URL-based patching directly from the default VMware repository or your own repository.
And there you have it, that's the process the update your VMware vCenter Server Appliance 6.0 to Update 1 to gain all the new feature and capabilities in this release. Related Documentation: