Upgrading to vRealize Operations 8.2

vRealize Operations Manager 8.2 was released on 6th Oct, 2020. It delivers new and enhanced capabilities for self-driving operations to help customers optimize, plan, and scale VMware Cloud, which includes on-premises private cloud or VMware SDDC in multiple public clouds such as VMware Cloud on AWS, while at the same time unifying multi-cloud monitoring. Powered by artificial intelligence (AI), this release takes us one step closer to the Cloud Operations Vision of providing a unified operations platform, deliver continuous performance optimization, efficient capacity and cost management, proactive planning, app-aware intelligent remediation, and integrated compliance.

To find more details on what is new with vRealize Operations 8.2, please visit the blog post – https://blogs.vmware.com/management/2020/10/whats-new-vrops-82.html

Please find below the steps to follow for a successful upgrade to vRealize Operations 8.2 :

Down-time requiredYes
Time RequiredRoughly 2 to 4 hours for environment of 2 x Large Nodes vROps ( This is a rough estimate and it can vary considerably with several environmental factors )
Impacts during upgradeNo Metrics will be collected during upgrade window.
Roll-back PlanSnapshots need to be taken prior to initiating upgrade and snapshot should be used as roll-back mechanism for any failures reported during upgrade steps.

Refer to below detailed steps for completing a successful upgrade:

Phase 1: Running Pre-upgrade Assessment tool – Time required: 15 minutes – Strongly Recommended to do this for any upgrades from vROps 7.x or prior versions

  1. Download upgrade assessment tool : vRealize Operations 8.2 – Upgrade Assessment Tool  ( Name of File: APUAT-8.2.0.16931956.pak, Size of File: 6.03 MB )
  2. Log in to the master node vRealize Operations Manager Administrator interface of your cluster at https://master-node-FQDN-or-IP-address/admin.
  3. Click Software Update in the left panel.
  4. Click Install a Software Update in the main panel.
  5. Follow the steps in the wizard to locate and install your PAK file. ( Check Install the PAK file even if it is already installed )
  6. Install the Upgrade Assessment Tool.
  7. Wait for the software update to complete.
  8. Access to Pre-upgrade assessment report  ( Refer to KB 78052 )– steps as below:
  • Navigate to the Support > Support Bundles tab.
  • Download the light support bundle that was generated from the installation of the Upgrade Assessment Tool.
  •  In the downloaded support bundle, open the cluster_timestamp_nodeaddress/nodeaddress_timestamp_nodeaddress/apuat-data/report/index.html file.
  • A list of all potentially impacted user content , if any , will be displayed in the “Removed / Discontinued Metrics “ tab
  • In the tab of “System Validation Checks” , you will find the report of system validation checks for upgrade and recommendations , if any. Follow the recommendations as suggested.
  1. If there are any remediations suggested for “System Validation Checks” in the above step , run the pre-upgrade assessment tool again after remediation tasks are completed. This is to make sure that all the upgrade pre-requisites are met before proceeding to the next phase of upgrade.


Phase 2 : Upgrading to vRops 8.2  

Upgrading to vROps 8.2 from vROps 7.x  

  1. Recommended to remove or update all impacted Management Packs, if any, prior to initiating the upgrade.
  2. Review the vRops 8.1 sizing for the environment prior to upgrade using vRops sizing calculator – https://kb.vmware.com/s/article/78495  . Make sure that the vRops nodes are sized based on the recommendations.
  3. Validate network settings on all nodes – Gateway , DNS , NTP server ( This is very important when there are multiple nodes in vRops Cluster )
  4. Download the following upgrade file required for upgrade: Use the download link from myvmware portal
File NameBuild#File SizeFile Type
vRealize_Operations_Manager-VA-8.1.1.16522883.pak165228832.31 GB.pak
  1. Make sure the root logins to all the vROps nodes are available.
  2. Make sure passwords for “root” account and “admin” account are reset and is not expired or not locked (On all nodes) – check by logging into SSH console of every node with root and admin accounts . If you have not logged into SSH earlier , the default password will be blank and just press enter at password prompt. After this it will ask for setting a new password.
  3. Make sure vRops cluster’s  “admin” account’s  password is not expired or locked – you may change from vRops admin portal.
  4. Make sure all the vROps nodes have sufficient disk space for upgrade (Minimum 5% free disk space required for each node): Check with command “df -h” from SSH session to each node.
  5. Optional step: If you have a large vROps cluster with more than 4 nodes , the upgrade process can be made faster by pre-copying upgrade files to all nodes. Pre-copy the upgrade files to all nodes except Master Node – follow steps as in KB 2127895
  6. Take the vROps cluster offline from Admin UI.
  7. Shut down the nodes in the sequence of Remote Collectors , Data nodes , Replica Node and Master Node.
  8. Take the snapshot of all the nodes.
  9. Power on the nodes in the sequence of Master Node , Replica Node , Data nodes and Remote collectors
  10. Initiate vROps In-place upgrade from Admin UI. 
  11. Once the upgrade is completed, verify functionality. If all functionality is reported correctly, take the cluster offline, shutdown nodes and delete the snapshots. Once snapshots are removed, power on the nodes in sequence of Master Node , Replica Node , Data Nodes and Remote Collectors
  12. Once all nodes are powered on , bring the vROps cluster Online.
  13. Because of vROps 8.1.x is included in vRealize Suite 2019 you should upgrade your vRealize Suite license from 2018 to 2019 as well.

Upgrading to vROps 8.2 from vRops 8.x 

  1. Download the upgrade file from the link – Download link for Upgrade file
File NameBuild#File SizeFile Type
vRealize_Operations_Manager-VA-8.x-to-8.2.0.16949151.pak169491512.5 GB.pak
  1. Make sure the root logins to all the vROps nodes are available.
  2. Make sure all the vROps nodes have sufficient disk space for upgrade (Minimum 5% free disk space required for each node): Check with command “df -h” from SSH session to each node.
  3. Take the vROps cluster offline from Admin UI.
  4. Shut down the nodes in the sequence of Remote Collectors , Data nodes , Replica Node and Master Node.
  5. Take the snapshot of all the nodes.
  6. Power on the nodes in the sequence of Master Node , Replica Node , Data nodes and Remote collectors
  7. Initiate vROps In-place upgrade from Admin UI. 
  8. Once the upgrade is completed, verify functionality. If all functionality is reported correctly, take the cluster offline, shutdown nodes and delete the snapshots. Once snapshots are removed, power on the nodes in sequence of Master Node , Replica Node , Data Nodes and Remote Collectors
  9. Once all nodes are powered on , bring the vROps cluster Online.

Additional resources :

KB 2001476 – How to reset the root password in vRealize Operations

KB 2078313 – How to reset the admin password in vRealize Operations Manager

Quick access to Commands available in vRops Nodes:

To reset vRops Cluster Admin password from root console :

$VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsSetAdminPassword.py –reset

To reset root or admin account in OS – to be run on all nodes

passwd root

passwd admin

To unlock the admin and root accounts in vRops – to be run on all nodes

pam_tally2 –user admin –reset
pam_tally2 –user root –reset

To validate if the accounts are locked  – to be run on all nodes:

passwd -S root

passwd -S admin

( If the account is not locked, you will see PS next to the username.  If the account is locked, you will see LK next to the username )

Advertisement

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at WordPress.com.

Up ↑