Blink, and you might have missed the announcements doing the rounds on Social Media about a minor release for some of VMware’s products.
Of the minor releases, the biggest one has to be vSphere 6.0 update 2 which packages Virtual SAN 6.2. Now you can get all the goodness of Dedupe & Compression, Erasure Coding (RAID 5 & 6), QoS, Sparse Swap Files, etc……
I’ve written a brief article on VSAN 6.2 for SearchVMware.com, so pop over there if you want to check out what was announced in Feburary’s Digital Enterprise event.
For more in-depth information on VSAN 6.2, point your browsers to Duncan Epping (Yellow-Bricks) and Cormac Hogan! These guys and their blogs have taught me everything I know about VSAN! =)
So without further ado, here’s what was released yesterday (and some from earlier in the month):
Now that vRealize Ops 6.2 has been released, it’s time to upgrade your Ops Manager virtual appliance. So how do you do that? Well, it’s pretty simple actually!
Nearly all of VMware’s virtual appliances have a simple upgrade process where you download an upgrade PAK file and upload it to the admin page of the appliance – and once uploaded it’s just a simple “click and install”….!
- First up, download the 6.2 upgrade PAK file from the My VMware Portal. You will required TWO upgrade PAK files, one to upgrade the vApps OS, the other to upgrade the vROps product.
For an OS upgrade, the file is: vRealize_Operations_Manager-VA-OS-xxx.pak
For the product upgrade of virtual appliance clusters, the file is: vRealize_Operations_Manager-VA-xxx.pak
- Before starting the upgrade it’s probably best to either take a backup or a snapshot of your entire vRealize Operations cluster as a precaution.
Note: The cluster can be online or offline when running the upgrade.
Log into the master node administrator interface via your web browser:
- On the left navigation menu, click Software Update. Note the version that vROps is currently at (for me it was 6.1). Click Install a Software Update.
- Firstly perform the OS upgrade. This updates the OS on the virtual appliance and restarts each virtual machine. Follow the wizard to locate and install the OS PAK file.
Note: If you have customised the content that vROps provides – such as alerts, symptoms, recommendations, and policies – and you want to install content updates, a best practice is to clone the content before performing the upgrade. You can then select the option to reset out-of-the-box content when you install the software update, and the update will provide new content without overwriting any customised content.
- Click Upload to stage the upgrade files.
- Once upload has completed, a summary of what the PAK file contains is listed. Click Next and accept the EULA, then click Finish to start the upgrade process.
- Once the upgrade is complete, vROps will restart and you need to log back into the admin page. Navigate to Software Update and you will see a message stating what previous software update was installed.
- Now repeat the upload and installation process for the Product upgrade PAK file.
- Once again, vROps will reboot after the Product upgrade PAK file has been installed. Log back in and navigate to Software Update, you should now see that vROps has been upgraded.
There you go… nice and simple!
If you encounter any issues, then head over to the vROps 6.2 Release Notes: http://pubs.vmware.com/Release_Notes/en/vrops/62/vrops-62-release-notes.html
So….. the penultimate piece of upgrade work planned for the DR environment is the upgrade of vCenter Operations Manager from 5.6 to 5.7.
The great thing about vCOPs is the ease of upgrading the appliance. Simply navigate to the administration page (https://vcops-ip/admin) and browse to the upgrade zip bundle! =)
1. Navigate to the admin page of vCenter Operations Manager and click on the Update tab. Click Browse and locate the vCOPs zipped upgrade bundle.
2. Wait for the file to unpack and upload.
3. Click Update to start the update process.
4. Click OK to proceed with the update.
5. Watch the update, or grab a cup of tea!
6. Once complete, reboot the appliance.
7. You may find that the registration of vCOPs to the linked vCenter Server will require updating. To do this browse to the Registration tab and click Update under vCenter Server Registration.
8. Enter the vCenter Server details and click Test Connection. If successful, click Apply.
9. Accept the security alert that moans about the SSL certificate not being trusted – this is the new SSL certificate that was generated when I upgraded my vCenter Server Appliance.
10. Reboot the appliance and Bob’s your uncle….. it should be up and running the latest version!