VMware vRealize Business for cloud Upgrade from 7.3 to 7.6 version

-
Hello Everyone,

This post is for how to upgrade the VMware vRealize Business for cloud from 7.3 version to 7.6.

Upgrading the vRB is quite simple and easy for everyone. Before upgrading the vRB, we have upgraded our vRealize automation platform from 7.3 to 7.6 version successfully.
We have to unregister the vRB from vRA before upgrading it vRA as well as as vRB.

Below are steps involved for this upgradation.

1. Take snapshot of vRB appliance without memory option.
2. Backup the vRB appliance if possible.
3. Unregister the vRB from vRA via accessing vRB appliance VAMI portal.
4. Login to vRB VAMI console and go to vRA tab.
5. Provide all details like hostname, SSO default domain, SSO Admin user, SSO admin password.
6. Click on Unregister button and it will unregister the vRB from vRA.

Now, we will proceed for upgrading the vRB from 7.3 to 7.6 version.

1. Take a snapshot of the vRB appliance if not taken previously.
2. Download vRB update Repo ISO file from VMware website.
3. Update ISO format should be like this- "vRealize-Business-for-Cloud-7.6.0.28529-13134973-updaterepo.iso"
4. Attached update .ISO file on vRB appliance CDROM.
5. CDROM will mount inside the appliance automatically.
6. Go to vRB VAMI console and choose Update Tab, then go to settings tab and choose "Use           CDROM Updates" and save the settings.
7. Back to Status tab and click on Check Updates tab under Actions Tab.
8. It will show vRA 7.6 updates for the installation and click on "Install Updates".
9. A prompt will come for the installation start progress.
10. After 20-30 mins, vRB will be upgraded to 7.6 successfully and appliance will reboot auto as well.
11. Click the system tab and verify the updated appliance version.
12. Check health status of vRB appliance and re-register it with vRA, followed by same process as we followed for unregister it.
==================================================================



Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more