I wanted to keep track of what needs to be done prior to actually being able to query API on vRA cloud. Ive been having a hard time finding the documentation i needed in the past First step is to get an API token for the specific username. We can do this by going to My account under User Settings in vRA Cloud Go to API Tokens and click on Generate a new api token ...
If you are like me and you tried to perform an upgrade of vIDM 3.3.x to 3.3.4 you were most likely greeted by no network connectivity after upgrade with the following screen: If you made a backup of the network configuration this is where we would restore it. If not we can perform it manually by running /opt/vmware/share/vami/vami_config_net Press 6 and go through the screens to configure the ip ...
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 ...
In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.3 release The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section Go to settings -> System Upgrade Click on Check for Upgrade We can see that the check found a new version available for 8.3 Click on Upgrade ...
I recently ran in to a situation where one of the events in vCenter wasn’t showing up in Operations Manager Doing some research and i found this kb article: 65106 Basically theres a file called eventlist.txt under /usr/lib/vmware-vcops/user/plugins/inbound/vmwarevi_adapter3/conf/ on the master node so i logged on to master node via ssh and did vi /usr/lib/vmware-vcops/user/plugins/inbound/vmwarevi_adapter3/conf/eventlist.txt Comment out the event that we want to get alerts for and restart the service by running ...
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