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
While I was doing the operations endpoint install on a new vROPS environment I experienced an strange error that I didn’t see before - Unable to register the agent due to server error. In order to find the issue I had to log in to my vROPS server in order to review the logs. I was able to find the End Point Adapter log file here: ...
From a lifecycle manager perspective we have a couple of ways to add keys to the environment If the my vmware user that is added to lifecycle manager has access to they keys, the keys can automatically discovered and imported. For this we can go to the locker from Home -> Locker -> License. If the keys are not discovered we can click on the refresh button up top to perform a manual sync ...
If you followed my previous posts Deploying the vRealize suite using VCF 4.0 and enabling product downloads in vRealize Lifecycle Manager, 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 Creating a New Environment 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 enabling product downloads in vRealize Lifecycle Manager, you should now have vRA and vIDM already downloaded. Creating the Environment in Lifecycle Operations 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 ...
In order to enable product downloads in lifecycle manager we need to go to Lifecycle Operations Adding a My VMware Account Settings -> My vmware Add my vmware account. Make sure the account added has a proper entitlement to perform downloads and patches. With the releases of 8.x and above we now have a password vault that we need to add the passwords to. When presented with the add my VMware Account Detail screen press on Click here to add a new password ...
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 doesn’t 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 ...
The official documentation for deploying the vRealize suite can be found here First step is to download the bundle by going to sddc-manager -> Repository -> Bundle management. Look for VMware Software Install Bundle - vRealize Suite Lifecycle Manager 8.1.0-16256499 After the download is complete we can go to Administration -> vRealize Suite and a deploy button should be available. If the deploy button is not available due to X-Region Application Virtual Network is not created errorplease follow the instructions found here: ...
I wanted to reuse my VCF downloaded bundles on another SDDC Manager system so that I wont have to download it from internet again. I’ve found an easy guide here in the VMware documentation. My goal was to download the specific bundle once and upload it on other SDDC Managers. Listing the Available Bundles The first command from SDDC manager was to list the bundles. The lcm bundle transfer utility can be found in /opt/vmware/vcf/lcm/lcm-tools/bin ...
VCF releases filled the SDDC Manager filesystem in my lab, so I used the bundle cleanup utility to reclaim the space. The first step was to identify the Bundle ID. We can find this by going to the bundle itself and checking out the details by clicking on View Details For example this specific Bundle ID is ee194251-9fe4-4729-9c29-ca5172acffc6 ...