Cloud Foundation

With the release of of VCF 4.3.1 i wanted to get my lab upgraded. The release blog can be found here and the release notes are here In order to get to 4.3.1.0 in the past we had to upgrade to each version incrementally. As per the documentation found here we can now upgrade from any release past 4.1.0.1 directly to 4.3.1 skipping the releases in between. We can do so by going to Repository -> Bundle management -> Download now. Download the Configuration drift bundle as well as the Update package. ...

In this post i will go over the Usage Report for vRealize Cloud Licenses. I will cover the online method which does the reporting automatically as well as the offline method that requires us to upload the usage manually. The documentation for the Usage Report can be found here. The vRealize Cloud Universal service description EULA and requirements can be found here. As described the EULA our responsibilities include: Deploy the latest version of vRealize Suite Lifecycle Manager in your on-premiseenvironment, and establish a connection between vRealize Suite Lifecycle Manager and your VMware customer account. Use vRealize Suite Lifecycle Manager to apply the vRealize Cloud Universal license key to on-premise components of the Service Offering and activate these components. Connect vRealize Suite Lifecycle Manager to vRealize Cloud Subscription Manager to enable usage reporting to VMware. If the on-premise environment is offline and unable to connect to vRealize Cloud Subscription Manager, you are responsible for periodically exporting a license report from vRealize Suite Lifecycle Manager and uploading the report to vRealize Cloud Subscription Manager, but no less than once per VMware fiscal quarter. We will be spending most of our time in vRealize® Suite Lifecycle Manager. Log in and go to the locker page either from the welcome screen ...

I have the need to completely shut down some of my vSAN clusters for various clusters and ive been having a hard time finding the proper procedure. As of 2/16/2021 VMware released guidance here Here are the steps i took to do it on my end. If you have the vCLS service enabled follow my other instructions here prior to starting the rest of this guide. Disable cluster member updates from vCenter on each ESXi host in the cluster by running ...

With the release of of VCF 4.2 i wanted to get my lab upgraded. The release blog can be found here and the release notes are here In order to get to 4.2.0.0 we have to upgrade to 4.1.0.1. We can do so by going to Repository -> Bundle management -> Download now The next step is to upgrade VCF by going to Inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Update Now for the VMware Cloud Foundation Update 4.1.0.1. The release notes can be found here ...

I wanted to go through the upgrade of vIDM 3.3.4 outside of lifecycle manager. I wanted to do it using the online upgrade via the console. Official documentation can be found here. First step is to log on to the console via the root credentials and upgrade the upgrade manager to 3.3.4 /usr/local/horizon/update/updatemgr.hzn updateinstaller Set the upgrade version that you are upgrading from in my case was 3.3.2 so i ran ...

With the release of of VCF 4.1 i wanted to get my lab upgraded. The release blog can be found here and the release notes are here In my case i pre downloaded the VMware Cloud Foundation Update 4.1.0.0 by going to Repository -> Bundle management -> Download now The next step is to upgrade VCF by going to Inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Update Now ...

I recently ran in to an issue where i had to re-register my NSX server with vIDM. The ask was to extract the Thumbprint from vIDM. The command i ran to extract it was: echo -n | openssl s_client -connect hostname:443 2>/dev/null | openssl x509 -noout -fingerprint -sha256 This can be used across multiple products where the Thumbprint needs to be extracted

If you followed my previous posts Deploying the vRealize suite using VCF 4.0 and vRealize Lifeycycle Manager (vRSLCM) enable product dowloads you should now have vRA and vIDM already downloaded. In my previous post i went over the installation of vIDM which is a pre requisite for vRA. You can find the link here Next, we need to create a new environment that will be used to deploy vRA. For this we can go to Lifecycle Operations -> Create Environment. Fill in the necessary information and click next ...

If you followed my previous posts Deploying the vRealize suite using VCF 4.0 and vRealize Lifeycycle Manager (vRSLCM) enable product dowloads you should now have vRA and vIDM already downloaded. Because im running on a deployment from VCF i can see that the datacenter was already provioned for me under under Home -> Lifecycle Operations -> Datacenters ...

While trying to deploy vRealize Suite Lifecycle Manager in VCF 4, i was prompted by an error X-Region Application Virtual Network is not created After doing some research i found out that the error is due to AVN not getting deployed part of the initial deployment. I remembered that VCF 4 doesnt actually require it so after i did some research i was able to find a kb article that allowed me to continue with my install. KB 78608 ...