In this post we will go over the steps for deploying an AVS cluster on Azure. The first step was to log in to the azure portal at portal.azure.com. Once logged on we can search for “azure vmware solution” Then I tried to create a cluster by clicking on the Create button on the top left ...
With the release of of VCF 4.4.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.4.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.4.1 skipping the releases in between. We can do so by going to Repository -> Bundle management -> Download now. ...
With the release of of VCF 4.4 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.4 skipping the releases in between. We can do so by going to Repository -> Bundle management -> Download now. ...
I recently ran into a problem where i needed to route the subnet that is being used for the docker routing on the vROPS Cloud Proxy appliance. The network used is 172.17.0.0/16. For this we will try to route a portion of that subnet through my ethernet interface To test the configuration out without adding a persistent route i used the following command: ip route add 172.17.11.0/24 via 172.16.11.1 dev eth0 Verify that everything is running properly, if anything went wrong the route should get reverted on the next reboot. If the changes are successful we can add the route as persistent by editing the network configuration using vi: ...
In this guide we will go over Deploying the vROPS cloud proxy for cloud as well as on premise. The official VMware documentation can be found here To get started log in to your vROPS instance. If its cloud it would be something similar to https://www.mgmt.cloud.vmware.com/vrops-cloud/ui/index.action For on premise it would be https://vrops_url/ui/login.action Once you are logged on We can go to Data Sources -> Cloud Proxies and press on New. example: ...
In this article i will go over one of the workaround instructions to address CVE-2021-44228 and CVE-2021-45046 in vRealize Operations 7.x. I have tested the workaround on vROPS 7.5 as its still shipped with VCF 3.x and i haven’t yet seen documentation on a workaround for this version. If you are looking for instructions for version 8.x consult kb article 87076. This has been tested on December 21 2021. Please check the official documentation or open a ticket for production usage. Where possible, moving to a release that ships with the fixed Log4j is the cleaner long-term option — I covered upgrading vROps to 8.6.2 via vRSLCM separately. ...
In this guide we will go over Creating a Credential for MongoDB in vROPS for the True Visibility Management pack. The original documentation was posted here however it hasn’t yet been updated to vROPS 8.6 and the new vROPS cloud. Procedure From the Left navigation bar, select Data Sources -> Integrations -> Credentials Click the Add button on the top left. In the Manage Credential window that appears, select whether or not authentication is required for your MongoDB environment, then enter the information indicated below: ...
During one of the recent upgrades in my VCF environment i accidentally upgraded the ESXi 7.x build number to a later build that was not in the validated design which caused all kinds of issues and errors in my sddc manager. In order to address this i wanted to see i could actually downgrade the packages to a lower build number. It goes without saying that this procedure should not be done in a production environment and you should contact VMware customer support for an supported downgrade method. We will be working in the ESXi cli on this guide ...
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 ...