Browse Category

Cloud Foundation

VMware Cloud Foundation

Shutting down a vSAN Cluster

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

esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListUpdates

After the above is completed run the below only on 1 of the ESXi hosts. Take note of the host

python /usr/lib/vmware/vsan/bin/reboot_helper.py prepare

Place all ESXi hosts in maintenance mode with NoAction

esxcli system maintenanceMode set -e true -m noAction

Perform the necessary maintenance. Once the hosts are back up we will run the above in reverse

Remove the maintence mode on all ESXi hosts by running

esxcli system maintenanceMode set -e false

Run the below command on the same host it was originally run

python /usr/lib/vmware/vsan/bin/reboot_helper.py recover

vSAN availability can be checked by running

esxcli vsan cluster get

Enable cluster member updates for vCenter

esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates

Upgrading VCF 4.1.0.0 to 4.2.0.0 Step by Step

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

Next we are taken to the Upgrade page where we can follow the upgrade for each one of the components

Once the upgrade is complete we can click Finish to be returned back to the main screen

Because we are changing the SDDC-Manager versions i would strongly recommend to clear cache and log back in before going forward.

Next is the 4.2.0.0 update. Repository -> Bundle management -> Download now. In my case i already had it downloaded so the next step is to apply the upgrade by going to Inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Update Now for the VMware Cloud Foundation Update 4.2.0.0. The release notes can be found here

Once the upgrade starts we can follow its progress

Once the upgrade is completed we can click finish and go to the next step

Again i would recommend clearing the cache since we changed sddc-manager versions.

Once the upgrade is complete we are taken back to the previous page where we can see that the ESXi servers are next. The release notes can be found here. Click on Download Now

Once the download is complete we can click on Update now

If we have multiple clusters we can enable Cluster-level selection and select the specific cluster(s) we want to upgrade.

We can also enable sequential cluster upgrade as well as quick boot

We get to review the options once again before we click finish to to submit the task

Once submitted we can view the status by clicking on View Status

And with that we are finished with the workload domain. We can get back to the Update/Patches page

The next update is the configuration drift bundle. We can go to inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Download now. You will notice a new drop down that allows us to pick the Cloud Foundation version.

Once the download is complete click on update now

Once the upgrade started i got redirected to the Update status page.

Considering the update is only 219 MB the upgrade went through pretty quickly. Once its completed we can click finish to get back to the main sddc manager page

Next step is to upgrade NSX-T installation to NSX-T 3.1.0. The release notes can be found here. We can go to inventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Download now.

Once the download is complete click on Update Now

We can view the status and the steps by clicking on View Status.

Once the upgrade is complete we are redirected back to the available updates page showing that the vCenter server is next

Click on Download now and wait for the download to complete. Once the download is complete click on update now

We can view the task by clicking on View Status

Next are the the additional domains that we might have where we can follow the same instructions as above. The process will be allot quicker because the upgrades are already downloaded

If no additional upgrades are needed we can clean up the downloads by following the instructions on my other post here

vIDM 3.3.4 online upgrade

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

/usr/local/horizon/update/configureupdate.hzn manifest --set-version 3.3.2.0

Because we are switching operating systems to Photon OS 3 we need to download the dual boot update package from here. Look for VMware Identity Manager Service Virtual Appliance Dual Boot Update and transfer it to the vIDM server

And finally run the update

/usr/local/horizon/update/updatemgr.hzn update

Specify the path to the dualboot file. It would look something like this:

If everything went through properly you would be greeted with something like this

All we need to do now is to reboot.

If you are greeted by the following screen follow my other post here

Upgrading VCF 4.0.1.1 to 4.1.0.0

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

Next we are taken to the Upgrade page where we can follow the upgrade for each one of the components

Once the upgrade is complete we can click Finish to be returned back to the main screen

Because we are changing the SDDC-Manager version i would strongly recommend to clear cache and log back in before going forward.

The next update is the configuration drift bundle. We can go to nventory -> Workload Domains -> Select the workload domain -> Update/Patches -> Download now

Once the download is complete click on update now

Once the upgrade started i got redirected tot he Update status page. Considering the update is only 204 MB the upgrade went through pretty quickly. Once its completed we can click finish to get back to the main sddc manager page

Next step is to upgrade NSX-T installation to NSX-T 3.0.2. Click on Download now from the same page as above

Once the download is complete click on Update Now

We can view the status and the steps by clicking on View Status. Once the upgrade is complete we are redirected back to the available upates page showing that the vCenter server is next

Click on Download now and wait for the download to complete. Once the download is complete click on update now

We can view the task by clicking on View Status

Once the upgrade is complete we are taken back to the previous page where we can see that the ESXi servers are next. Click on Download Now

Once the download is complete we can click on Update now

If we have multiple clusters we can enable Cluster-level selection and select the specific luster(s) we want to upgrade.

We can also enable sequential cluster upgrade as well as quick boot

We get to review the options once again before we click finish to to submit the task

Once submitted we can view the status by clicking on View Status

And with that we are finished with the workload domain. We can get back to the Update/Patches page to see that there are no more updates available

Next is the Workload domains where we can follow the same instructions as above. The process will be allot quicker because the upgrades are already downloaded

Extracting SSL Thumbprint

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

Deploying vRA with vRealize Lifecycle Manager in a VCF 4 Environment

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

Select vRealize Automation, select the version and install type then click next

Review and accept the EULA then click Next

Next screen is the key. Click on Select and select the vRA key from the inventory. If we need to add the key manually we can follow the steps in my post here

Verify the key selection click on Validate Association and click on next

Select the certificate and click next. If a new certificate needs to be create follow the instructions on my post here

Make the proper selections for where the vRA server will get deployed and click Next

Fill in the proper network configuration and click next

Specify the proper network configuration for the product and click next

Run the precheck and verify that everything is green then click Next

Verify the summary and click submit

Next we are taken to the request details where we can follow the process that LCM is performing for us automatically.

We can see that the task completed

If we go to environments we can see that the vRA Environment

Deploying vIDM with vRealize Lifecycle Manager in a VCF 4 Environment

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

However it seems like my Environment is not completely configured. In order to configure we can go to Home -> Lifecycle Operations -> Create Environment

Add a new password to the vault that will be used by our installation wizards. We can add a password by clicking on the + sign next to the Default Password

Enter the password details and click add

Now i can select the new password by clicking on Select Default Password. I can select the Datacenter from the drop down and click Next.

Select the VMware Identify Manager and click Next

Accept the EULA and click Next

Select the certificate. If you do not have a certificate you can follow the instructions i have here. Click next

Select the proper details to where the server will be deployed

Fill in the network information and click next

Fill in the product information

Run the precheck and verify that everything is valid and click next

Verify the details in the Summary and click Submit

We are taken to the request details page

Once the deployment is complete we can see the vIDM server under Environments

X-Region Application Virtual Network is not created error

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

All i had to do is log in to my sddc manager with my root credentials and execute the following commands:

cd /home/vcf
echo "feature.vcf.avn.greenfield=false" >> feature.properties
chown vcf:vcf feature.properties
chmod 644 feature.properties
/opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Once that was complete i was able to start the deployment

Deploying the vRealize suite using VCF 4.0

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 error please follow the instructions found here:

Verify the Prerequisites and click on begin

Fill up the network settings and click next

Fill up the Virtual Appliance Settings:

Review the summary and click Finish

We can follow the progress by click on the Task on the bottom of the screen

This allows me to see the subtasks that are running

Once the deployment is complete we can open the vRealize Suite Lifecycle Manager by clicking on the link

Downloading specific VCF bundles

I wanted to reuse my VCF downloaded bundles on another SDDC Manager system so that i wont have to download it from internet again. Ive 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.

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

./lcm-bundle-transfer-util -du ${depotUser} -l -p ${product_version}

I replaced the ${depotUser} with my vmware email address and ${product_version} with the version of the VCF product i wanted to install in my case 4.0.1.1. I was greeted with a list of bundle IDs and the specific component that it was for:

Enter Myvmware user password:
Validating the depot user credentials...

Bundle         Product  Bundle Size  Components
               Version  (in MB)
bundle-27565   4.0.1.1  10092.0 MB   SDDC_MANAGER_VCF-4.0.1.1-16660200
bundle-27336   4.0.1.1  5220.0 MB   VCENTER-7.0.0.10600-16620007-PATCH
bundle-27337   4.0.1.1  7613.0 MB   VCENTER-7.0.0.10600-16620007-INSTALL

In my case i need the installer. To download a specific bundle we run

./lcm-bundle-transfer-util --download --outputDirectory ${absolute-path-output-dir} --depotUser ${depotUser} -b ${bundle_name}

in my case it was:

./lcm-bundle-transfer-util --download --outputDirectory /some/temporary/location --depotUser my@vmware.id -b bundle-27565

This allowed me to grab the download from /some/temporary/path and save it/upload it on my other SDDC Managers that were missing it.

Finally before the patch can be used in SDDC Manager we need to upload it to the repo. Please note that once we issue the upload command the download gets deleted, so make sure you save the download ahead of time

./lcm-bundle-transfer-util --upload --bundleDirectory /some/temporary/path -b bundle-27565

Once the upload was complete i was able to see it in SDDC Manager as an package that i can apply.

  • 1
  • 2