Generated by All in One SEO v4.9.3, this is an llms.txt file, used by LLMs to index the site. # mgustafsson - yet another VMware blog ## Sitemaps - [XML Sitemap](https://www.martingustafsson.com/sitemap.xml): Contains all public & indexable URLs for this website. ## Posts - [Quick Tip: Renaming an Instance in VCF 9.x](https://www.martingustafsson.com/quick-tip-renaming-an-instance-in-vcf-9-x/) - With the introduction of VMware Cloud Foundation 9, managing multiple VCF instances across a VCF Fleet has become significantly more streamlined. Part of day-two operations often involves aligning your infrastructure with evolving organizational standards. Fortunately, VCF 9 makes renaming an underlying VCF instance non-disruptive and straightforward. In this scenario, we're changing an initial instance named - [VCF: Automate Custom ESXi ISO Mappings at Scale](https://www.martingustafsson.com/vcf-custom-esxi-iso-mapping/) - Automate VMware Cloud Foundation upgrades: pick ESXi bundles, map clusters to custom ISOs, skip mixed-vendor hosts, and update LCM in minutes. - [VCF - vLCM Image Management: Failed to retrieve images: 400 Bad Request](https://www.martingustafsson.com/vcf-vlcm-image-management-failed-to-retrieve-images-400-bad-request/) - Presented with a red banner and a 400 Bad Request error when visiting the Image Management tab in SDDC Manager? Chances are that you have had issues when trying to import a vLCM image the import has failed. In order to troubleshoot this issue, open up the /var/log/vmware/vcf/lcm/lcm-debug.log file. We can immediately spot some java - [Resetting the admin@local password in VCF](https://www.martingustafsson.com/resetting-the-adminlocal-password-in-vcf/) - These steps should not be performed in a production environment unless under the supervision of VMware Support. The admin@local password is used to issue API calls to your SDDC Manager in case the management vCenter is down. It is extremely important to know the password of this account in case disaster hits. In order to - [WEB UI TO CREATE VCF JSON FILES - UPDATED!](https://www.martingustafsson.com/web-ui-to-create-vcf-json-files-updated/) - Since I created my VCF JSON Generator, I never thought I'd see the amount of traffic that I did.Customers, partners, colleagues, and various users have expressed their gratitude for the generator. Skål/Cheers! We've made considerable changes to VCF since I created the generator, like adding vSAN ESA, splitting NSX traffic over multiple VDS and splitting - [VCF 5.1 Deep Dive: Custom NSX Edge Deployments](https://www.martingustafsson.com/vcf-5-1-deep-dive-custom-nsx-edge-deployments/) - For other 5.1 deep dives: vSAN ESA Multi pNIC/Multi VDS Deployment.. via the UI! Distributed Virtual Port Group Separation for Management Domain Appliances When deploying edge clusters from SDDC Manager, you are limited in the design options. When deployed via SDDC Manager, the workflow will always create a Tier-0 and Tier-1. Not very flexible, right? - [VCF 5.1 Deep Dive: Multi-pNIC / Multi-VDS in the UI](https://www.martingustafsson.com/vcf-5-1-deep-dive-multi-pnic-multi-vds-in-the-ui/) - For other 5.1 deep dives: vSAN ESA Distributed Virtual Port Group Separation for Management Domain Appliances Custom Edge Cluster Deployments Ever since we implement multi-pnic support back in VCF 3.9.1, customers have asked for an easier method to deploy clusters with >2 NICs and multiple distributed switches. Up until VCF 5.1, if the user wanted - [VCF 5.1 Deep Dive: Management Portgroup Separation](https://www.martingustafsson.com/vcf-5-1-deep-dive-management-portgroup-separation/) - For other 5.1 deep dives: vSAN ESA Multi pNIC/Multi VDS Deployment.. via the UI! Custom Edge Cluster Deployments Distributed Virtual Port Group Separation for management domain appliances That's a mouthful. Today, the management components reside on a subnet/vlan that is shared with the management ESXi hosts vmk0 interface. We are changing this. This feature enables - [VCF 5.1 Deep Dive: vSAN ESA](https://www.martingustafsson.com/vcf-5-1-deep-dive-vsan-esa/) - For other 5.1 deep dives: Multi pNIC/Multi VDS Deployment.. via the UI! Distributed Virtual Port Group Separation for Management Domain Appliances Custom Edge Cluster Deployments We now support vSAN ESA for both the management domain and VI Workload domains.That's right, we can do bringup and use ESA, pretty cool! Deploying a VI WLD/cluster with vSAN - [VMware Cloud Foundation 5.1 Released](https://www.martingustafsson.com/vmware-cloud-foundation-5-1-released/) - VMware Cloud Foundation 5.1 is now GA! This release brings a lot of new features to Cloud Foundation. I'm doing a deep dive into some of these features: vSAN ESA Multi pNIC/Multi VDS Deployment.. via the UI! Distributed Virtual Port Group Separation for Management Domain Appliances Custom Edge Cluster Deployments Sub-Transport Node Profiles capabilities This - [Using HCI Mesh with VCF (and compute-only clusters)](https://www.martingustafsson.com/using-hci-mesh-with-vcf-and-compute-only-clusters/) - Quick links: Mounting / Unmounting via vCenter ServerMounting / Unmounting via SDDC Manager Compute-only ClustersDeploying a HCI Mesh Compute-only Cluster in VCF VMware Cloud Foundation 4.2 introduced initial support for HCI Mesh allowing vSAN datastore capacity to be shared across different vSAN clusters within the same vCenter. VMware HCI Mesh is vSAN’s feature that provides - [Re-use Cloud Builder for Another Deployment](https://www.martingustafsson.com/re-use-cloud-builder-for-another-deployment/) - You can easily reset Cloud Builder to start another VMware Cloud Foundation deployment. Before you start, make sure that the previous deployment has successfully completed. 1. Login to Cloud Builder over SSH using the admin user. 2. Run the following CLI command to delete the current deployment. sudo psql -U postgres -d bringup -h localhost - [VMware Cloud Foundation 4.5 Released](https://www.martingustafsson.com/vmware-cloud-foundation-4-5-released/) - VMware Cloud Foundation 4.5 is GA! Amongst several bug fixes, there are a couple of new or improved features. I'll list them below. Tags! There's now support for tags! This allows us to use the existing tag platform that already exists in vCenter. We can assign and remove tags on hosts, clusters and workload domains - [Web UI to create VCF JSON files](https://www.martingustafsson.com/web-ui-to-create-vcf-json-files/) - Over the last months and years, I've received a lot of questions regarding JSONs and VCF - both from customers, partners and colleagues. The questions vary in everything from "how do I do this?", to help creating JSONs for specific purposes. As you may be aware, if you want to deploy a workload domain or - [VMware Cloud Foundation 4.4 Released](https://www.martingustafsson.com/vmware-cloud-foundation-4-4-released/) - VMware Cloud Foundation 4.4 is now GA! VCF 4.4 features log4j fixes for the entire BOM. VCF 4.4 also features flexible upgrades for the vRealize Suite. You can now upgrade vRS products without waiting for a new VCF BOM to be released. SSH is finally disabled on the ESXi hosts. Do note that some operations - [Activity logging in VCF 4.4](https://www.martingustafsson.com/activity-logging-in-vcf-4-4/) - With the release of VMware Cloud Foundation 4.4, we now capture all the API invocation calls, along with user context. The logs also capture user login/logout in the SDDC Manager UI. The activity log files are defined per service, so the user must know in which log to look. To help you easier understand in - [Deploy 2-node cluster in VMware Cloud Foundation](https://www.martingustafsson.com/deploy-2-node-cluster-in-vmware-cloud-foundation/) - With the release of VMware Cloud Foundation 4.4, we now support 2-node clusters. The requirements are as follows:• vSphere Lifecycle Management Images must be used. vLCM Baseline mode is not supported. • Principal storage must be one of the following: VMFS on FC, vVol or NFS. vSAN is not supported for 2-node clusters. You can - [VMware Cloud Foundation 4.3 Released](https://www.martingustafsson.com/vmware-cloud-foundation-4-3-released/) - VMware Cloud Foundation 4.3 has finally been released. Some of the new and fixed features include the option for SANs in the CSR, previously there was a limitation with the NSX-T CSR API that didn't include SANs leading to a warning when visiting the NSX-T VIP when you had replaced the certificate. What's New Flexibility - [LcmException: bundle checksum does NOT match the manifest value - VCF 4.3 Upgrade](https://www.martingustafsson.com/lcmexception-bundle-checksum-does-not-match-the-manifest-value-vcf-4-3-upgrade/) - I have now seen multiple reports of issues with downloading bundles part of the VMware Cloud Foundation 4.3 upgrade. LcmException: Bundle tar file size 5656422400 does NOT match the manifest value 5656289280LcmException: Bundle tar file size 7742392320 does NOT match the manifest value 7742259200LcmException: bundle checksum does NOT match the manifest value In some cases, - [SDDC Manager - Where's my history?](https://www.martingustafsson.com/sddc-manager-wheres-my-history/) - VMware Cloud Foundation 4.3 brought additional security hardening to SDDC Manager, one is to remove the history of the bash shell in SDDC Manager. This can be fairly annoying when troubleshooting logs or issuing API calls. You can disable this on the current session with set -o history, or you can disable it globally with - [Host IDs and matching FQDNs in VCF](https://www.martingustafsson.com/host-ids-and-matching-fqdns-in-vcf/) - If you're automating the deployment of an additional workload domain, cluster or expanding an already existing cluster, you'll know that you need the Host ID in order to issue the proper API calls. There are numerous ways of getting the Host ID. You can use the SDDC Manager UI and browse to the host, the - [Removing failed tasks in SDDC Manager](https://www.martingustafsson.com/removing-failed-tasks-in-sddc-manager/) - If you have failed tasks in the SDDC Manager UI there is a way to clear them. Simply get the task ID. This can be done from the various logs (depending on which type of operation it is), or by just clicking on the failed task in the SDDC Manager UI. 1. Click on the - [PowerCLI script to prepare ESXi hosts for VCF](https://www.martingustafsson.com/powercli-script-to-prepare-esxi-hosts-for-vcf/) - With VMware Cloud Foundation, there is a number of prerequisites needed to be configured on an ESXi host before it can be commissioned or used for a management domain bringup. When dealing with multiple ESXi hosts it is often quicker to script the configuration needed. Based on the official documentation, the following needs to be - [Same VLAN for Host TEP and Edge TEP in VCF?](https://www.martingustafsson.com/same-vlan-for-host-tep-and-edge-tep-in-vcf/) - NSX-T 3.1.0 added support for sharing the Geneve overlay transport VLAN between ESXi TEPs and Edge TEPs. I often receive the question whether this is supported or not in VMware Cloud Foundation, and the answer is no. The feature of having same VLAN for Edge TEP and Host TEP is available only for Edge VMs ## Pages - [Author](https://www.martingustafsson.com/about/) - Martin has over 17 years experience in the IT industry, across design, implementation, and administration of enterprise environments. Currently employed by VMware as a Staff Consultant within the Northern EMEA PSO team, focusing primarily on VMware Cloud Foundation. Disclaimer The views and opinions expressed on this site are strictly my own and do not reflect ## Categories - [VCF](https://www.martingustafsson.com/category/vcf/) - VMware Cloud Foundation ## Tags - [vcf](https://www.martingustafsson.com/tag/vcf/) - [lcm](https://www.martingustafsson.com/tag/lcm/) - [vmware](https://www.martingustafsson.com/tag/vmware/) - [esxi](https://www.martingustafsson.com/tag/esxi/)