With the latest release of ESXi7U1 i wanted to get my lab up to date. I dont have enough resources in my lab to migrate the vCenter to another ESXi server so i want to perform the upgrade via cli. More details about the release can found here The first step was to open the firewall for outgoing traffic for http esxcli network firewall ruleset set -e true -r httpClient Second step was to list the updates by executing ...
While i was trying to perform an upgrade to my ESXi installation i ran in to the below error: The fix was pretty simple. The hypervisor doesnt have enough space to download and install the package so we need to enable one of the available datastores for the function. For vCenter go to the host in question to Configure -> System -> System Swap While reviewing the configuration i noticed that i had 2 options enabled ...
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 ...
After upgrading my vCenter Server to the latest vSphere 7.0 Update 1, I was unable to see ESXi 7.0 Update 1 Image. When I attempted to sync the updates I got the error “Download patch definitions task failed while syncing depots. Error: ‘integrity.fault.HostPatchInvalidVendorCode’.” Seeing as the error mentioned the depots, navigate to Menu->Lifecycle Manager and then select the Settings tab and then Patch Setup. Select the radio button for Partner provided Addons for ESXi and click Disable. Proceed to click on Action and then Sync Updates. The sync should now complete successfully. ...
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 didnt 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: /storage/log/vcops/log/adapters/EndPointAdapter/ While reviewing the log i found a strange error pointing me to the adapter ...
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 ...
vRealize Lifeycycle Manager (vRSLCM) come with a Certificate Management feature. We can access the certificate management from Home -> Locker -> Certificate We can generate Self Signed certificates for products managed by Lifecycle Manager as well as certificate requests to be signed by a certification authority Generate a new CSR Download the CSR and take it to the certified authority, in my case im using a Microsoft server /certsrv/certrqxt.asp ...
In order to enable product downloads in lifecycle manager we need to go to Lifecycle Operations 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 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 ...