Last month the fine folks at VMware released an upgrade (5.7) of vCenter Operations Manager (vCOps) 5.6 that we discussed in the last article.
After going through the update process and looking at how VMware has been working its way towards using a web interface for all of its management components instead of the VI client I can only hope that this is how all of these components will be updated in the future. In this article we’ll first look at the new features of 5.7 and then walk through the update steps from version 5.6.
vCOPs update package
vCOps 5.7 features
In our last article we focused on the included, Foundation edition of vCOps. Unfortunately, if that is the edition that you are running (like me) you are not going to be able to make use of the bigger features of this update. What Foundation 5.7 will get you is greater browser support (adding all current versions of IE, Firefox and Chrome), security hardening of the vApp, and the ability to scale vCOps to be able to cover over 10,000 Virtual Machines. As an avid Chrome user I’m pleased by the browser support entry these aren’t anything to write home about.
With all of the paid editions of vCOps what you do get is some great abilities in terms of capacity management. First off you now have the ability to create policies which define thresholds and then apply them to clusters, hosts, VMs, etc. These policies can cover anything from VM CPU usage to network throughput. There are quite a few out of the box policies defined that you can then assign that will cover most everybody’s needs but you also have the capability to create your own.
These policies can now in turn be used for actual management. If a threshold for given host or datastore is exceeded vCenter has the ability to restrict admittance of any new VMs to the managed object until the metric falls below maximum level.
Finally for the Advanced and Enterprise edition crowd there are also new and updated widgets. Widgets in the vCOps world are little boxes for your dashboards that can show more refined pieces of information in a visual manner. Further these levels also now get greater import and export ability.
So remember in the last article how you went to the vSphere download page and selected the .ova file for vCOps 5.6? Now is when you are going to want the other option, the .pak file. Updates are always done with PAK Updater files. Once downloaded you’ll need to get into the admin page of your main vCOps server which can be accessed at https://IP OF VM/admin. Enter your admin credentials and select the update tab. Here you’ll need to browse to where you download the PAK file and then click the update button. It will then proceed to upload the file for you. Finally, after you accept the EULA and say you really do want to update the updater will take it from there. Once done it will present you with the screen above showing all the component’s status. That’s it!