Top Posts
Offline VMware Cloud Foundation 9 Depot: Your Path...
VMware Cloud Foundation 9: Simplifying Identity with a...
What’s New In VMware Cloud Foundation 9.0
Deploying & Configuring the VMware LCM Bundle Utility...
VMware Cloud Foundation: Don’t Forget About SSO Service...
VMware Explore Las Vegas 2025: Illuminating the Path...
Securing Software Updates for VMware Cloud Foundation: What...
VMware Cloud Foundation 5.2: A Guide to Simplified...
VMware Cloud Foundation 5.2: Unlocking Secure Hybrid Cloud...
VMware Cloud Foundation – Memory Tiering: Optimizing Memory...
Virtual Bytes
  • Home
  • Home Data Center 2025
  • VMware
    • Cloud
    • Datacenter & Cloud Infrastructure
      • VMware ESXi
      • VMware vCenter
      • VMware vSAN
    • Networking & Security
    • Desktop & App Virtualization
      • Omnissa Horizon
    • Troubleshooting
    • Ansible
  • Education
  • Hardware
    • Hardware Tips & Tricks
  • Events
  • About
    • About Me
    • Home Lab Archives
      • Home Lab 2020-2022
      • Home Lab 2016-2020
Tag:

vsphere

VMware Cloud Foundation

Offline VMware Cloud Foundation 9 Depot: Your Path to Air-Gapped Deployments

by Tommy Grot July 1, 2025
written by Tommy Grot 8 minutes read

Deploying VMware Cloud Foundation (VCF) in environments with limited or no external network access – whether for security or logistical reasons – requires a little planning. One key piece is having a local depot for software packages. In this post, we’ll walk through setting up an offline depot web server for VCF 9, allowing you to keep your deployments running smoothly even when disconnected from the internet. We’ll cover the necessary components, configuration steps, and best practices to ensure a reliable and accessible offline repository. Let’s dive in!


What is Required

  • Generate download token on Broadcom Support Portal.
  • The offline depot must have:
    • The latest version of the VCF Download Tool, which you can download from the Broadcom Support Portal.
    • Virtual machine with Internet connectivity
    • Configure TCP keepalive in your SSH client to prevent socket connection timeouts.

Error: “Unable to connect to the Proxy Server” – VCF Download Tool is failing with proxy configured.

VMware is working on the solution for Proxy enabled downloads – KB Article

Upload the VCF Bundle Utility to the VM and extract it into a directory.

tar -xzvf vcf-download-tool-9.0.0.0.24703747.tar.gz

After extracting the VCF download tool, create a text document with your authentication token for downloading the binaries.

Executing the VCF Bundle Tool example:

./vcf-download-tool
Description:
Download all the necessary files. The command supports filtering to narrow down the selection of binaries based on the customer intent. At least one filter is required. In addition to the
binaries, it also downloads all of the needed metadata. However, UMDS binaries are excluded from the download. When executed multiple times with the same output directory, the command’s
behavior is cumulative, adding to previously downloaded binaries without overwriting them.

      --ceip=<ENABLE|DISABLE>
                            Enable or disable the Customer Experience Improvement Program (CEIP) within the VCF Download Tool. When the tool is used for the first time, if not provided, the
                              user will be prompted to make a choice about whether to participate in CEIP. After the initial selection, the value will be stored, making the parameter optional
                              in future runs. To change the persisted value pass the parameter with the new value. Valid values: ENABLE, DISABLE
* -d, --depot-store=<depotStore>
                            Directory where all binaries and metadata downloaded by the VCF Download Tool will be stored. This directory serves as the local repository for all downloaded
                              artifacts, maintaining the necessary structure for easy access and management.
  -h, --help                Displays a help message that provides information about the command and its available options, and then exits the tool.

[DEPOT] Depot authentication settings:
*     --depot-download-token-file=<depotDownloadTokenFile>
                            Path to text file containing single line with depot download token. Download token can be generated at Broadcom download portal and used for authentication instead
                              of --depot-user and --depot-user-password-file.
      --depot-user-password-file=<depotUserPasswordFile>
                            Path to a text file that contains the password for the provided --depot-user. The file should have the password on a single line. If this parameter is not provided,
                              the user will be prompted to manually enter the password.
* -u, --depot-user=<depotUser>
                            Username used for authentication when accessing the depot from which binaries and metadata are downloaded.

[PROXY] Proxy configuration settings:
      --proxy-https         Specifies whether the proxy server is configured to be used with HTTPS connections.
      --proxy-user-password-file=<proxyServerPasswordFile>
                            Path to a text file containing the password for the provided --proxy-user. The file should contain the password on a single line. If this parameter is not provided,
                              the user will be prompted to enter the password manually.
* -r, --proxy-user=<proxyServerUserName>
                            Username required to authenticate to the proxy server. If the proxy server enforces authentication, this parameter allows you to provide the necessary credentials
                              for accessing the proxy.
* -s, --proxy-server=<proxyServerHostName>
                            Host name of the proxy server that the VCF Download Tool will use for internet access. The required format is <FQDN:Port>. The proxy server must be reachable from
                              the machine where the tool is running.

[VCF VERSION] VCF Version filter parameters:
      --automated-install   Download binaries needed by VCF Installer.
      --component=<component>
                            Component type for which to download binaries. Possible values [VCENTER, SDDC_MANAGER_VCF, NSX_T_MANAGER, ESX_HOST, VRSLCM, VRA, VROPS, VRLI, VRNI, VSAN_OSA_WITNESS,
                              VSAN_ESA_WITNESS, VSAN_FILE_SERVICES, VMTOOLS, VCFDT, VCF_OPS_CLOUD_PROXY, VIDB, HCX, VMRC, VRO].
      --lifecycle-managed-by=<SDDC_MANAGER_VCF|VRSLCM|SELF>
                            Download binaries whose lifecycle is managed by the provided component. Possible values [SDDC_MANAGER_VCF, VRSLCM, SELF].
      --patches-only        Download binaries for patch versions of components.
      --sku=<VCF|VVF>       Offering type for which binaries to be downloaded. Possible values [VCF, VVF].
  -t, --type=<INSTALL|UPGRADE>
                            Type of binary to be downloaded. Possible values [INSTALL, UPGRADE].
*     --vcf-version=<vcf version[..[end version]]>
                            Version of VMware Cloud Foundation (VCF) for which binaries to be downloaded. Provided version should be of format a.b, a.b.c or a.b.c.d. For example, if 9.0 is
                              provided, 9.0.0.0 major release and all the maintenance release for 9.0.x is returned. If 9.0.1 is provided only 9.0.1.x release is returned. If 9.0.1.0 is
                              provided, exact release version is matched. Version range is also supported with format start_version..end_version. When version range option is used all binaries
                              from start version inclusive till end version inclusive will be downloaded. If end version is not provided (e.g. 9.0..) binaries for all released versions higher
                              than 9.0 will be downloaded.

[BUNDLE ID] Bundle ID filter parameters:
      --id=<bundleIds>[,<bundleIds>...]
                            Accepts one or multiple binary IDs, which can be provided as a comma-separated list or by repeating the option.

[DOWNLOAD SPEC] Download spec filter parameters:
      --download-spec-file=<downloadSpecFile>
                            Path to the download specification file generated by the create download spec command. This file contains the details of the binaries required for the planned
                              upgrades in your environment.

Examples:
1. Download install binaries needed by VCF Installer for deploying VCF instance for a specific VCF version using depot username:
  vcf-download-tool binaries download --depot-store=<binaries_dir> --depot-user=<username> --depot-user-password-file=<password_file_path> --vcf-version=<VCF_version> --sku=VCF
--automated-install --type=INSTALL
2. Download upgrade binaries whose lifecycle is managed by SDDC Manager for specific VCF version using depot token:
  vcf-download-tool binaries download --depot-store=<binaries_dir> --depot-download-token-file=<token_file_path> --vcf-version=<VCF_version> --lifecycle-managed-by=SDDC_MANAGER_VCF
--type=UPGRADE
3. Download binaries based on download specification file using depot token through proxy:
  vcf-download-tool binaries download --depot-store=<binaries_dir> --depot-download-token-file=<token_file_path> --download-spec-file=<download_spec_file_path> --proxy-server=<FQDN:Port>
--proxy-https --proxy-user=<username> --proxy-user-password-file=<password_file_path>

Commands:

  • binaries Management of the binaries files within the system.
  • metadata Management of the metadata files within the system.
  • releases Operations related to the VCF releases.
  • umds Manage the installation and execution of the UMDS (Update Manager Download Service) tool.

NOTE: The following command is for installation binaries ( –type=install ), specify upgrade parameters for upgrade binaries for VCF.

./vcf-download-tool binaries download --vcf-version 9.0.0 --automated-install -d /var/www/offline-bundles --depot-download-token-file /root/token.txt --type=install

Binaries are downloading! They are now available in OVA or ISO format, depending on whether you are installing or upgrading.

The binaries have been downloaded, and an example of the tree structure for the offline VCF Depot is shown below.

root@photon-69a92c0feee [ /var/www/offline-bundles/PROD ]# tree
.
├── COMP
│   ├── NSX_T_MANAGER
│   │   └── nsx-unified-appliance-9.0.0.0.24733065.ova
│   ├── SDDC_MANAGER_VCF
│   │   ├── Compatibility
│   │   │   └── VmwareCompatibilityData.json
│   │   └── VCF-SDDC-Manager-Appliance-9.0.0.0.24703748.ova
│   ├── VCENTER
│   │   └── VMware-VCSA-all-9.0.0.0.24755230.iso
│   ├── VCF_OPS_CLOUD_PROXY
│   │   └── Operations-Cloud-Proxy-9.0.0.0.24695833.ova
│   ├── VRA
│   │   └── vmsp-vcfa-combined-9.0.0.0.24701403.tar
│   ├── VROPS
│   │   └── Operations-Appliance-9.0.0.0.24695812.ova
│   └── VRSLCM
│       └── VCF-OPS-Lifecycle-Manager-Appliance-9.0.0.0.24695816.ova
├── metadata
│   ├── manifest
│   │   └── v1
│   │       └── vcfManifest.json
│   └── productVersionCatalog
│       └── v1
│           ├── productVersionCatalog.json
│           └── productVersionCatalog.sig
└── vsan
    └── hcl
        ├── all.json
        └── lastupdatedtime.json

16 directories, 13 files

July 1, 2025 0 comments 420 views
0 FacebookTwitterLinkedinThreadsBlueskyEmail
VMware ESXi

Installing / Upgrading VMware vSphere ESXi 7 Update 1 via iDRAC 8

by Tommy Grot October 7, 2020
written by Tommy Grot 2 minutes read

This post is guiding you on how to install or upgrade VMware ESXi 7 Update 1. This walk through will be the same for installing or upgrading ESXi, the only difference would be during the install you would specify a root password along with installing it.

Disclaimer: This also works for iDRAC 8 and below. On Dell PowerEdge 13th, 12th Generation servers.

Information Regarding the VMware vSphere Update via VMware’s Website – Click Here to Download, You will need to login with your VMware credentials.

Name:VMware-VMvisor-Installer-7.0U1-16850804.x86_64
Release Date:2020-10-06
Build Number:16850804

First Step: Log into iDRAC via root. Once logged in, click on Launch virtual console as below in the screenshot.

Once the Virtual Console window has opened. You will need to mount your VMware-VMvisor-Installer-7.0U1-16850804.x86_64.iso to the Virtual Optical Drive. Then click Map Device.

During the reboot of the server you may have to press F11 to get into the Boot Menu and select the One Time Boot Menu and go down to Virtual Optical Drive.

Once you select Virtual Optical Drive you will see the Dell BIOS loading and running through its boot up processes.

Now loading the VMware-VMvisor-Installer-7.0U1-16850804.x86_64.iso and it loads into memory.

Once the VMware ESXi 7.0.1 installer has loaded you will be greeted with a menu to follow through which is pretty straightforward.

Accept EULA.

Install or Upgrade VMware ESXi 7.0.1 on the correct corresponding datastore. If it is on a SD Card or Flash it will show up. Ensure to not install it on a VMFS datastore!

During this step. You have the ability to install a fresh or upgrade an existing environment. This will depend on your scenario. Please follow through carefully and ensure you have all backups of your DATA!

This will be the Final Screen prior to proceeding with the Installation or Upgrade! Press F11 to upgrade or accept if it is a fresh install.

Please be patient and let install finish 🙂

Install / Upgrade is complete! Now you may un map the virtual optical drive and reboot the host! And Enjoy the new VMware vSphere Update 7.0.1

October 7, 2020 1 comment 9K views
1 FacebookTwitterLinkedinThreadsBlueskyEmail
VMware Troubleshooting

VMware VAMI – Unable to login

by Tommy Grot July 19, 2019
written by Tommy Grot 1 minutes read

Do you have a issue with logging into VMware vCenter Appliance Management? If so there is a little work around to getting back into your VAMI! I wanted to upgrade my vCenter Server to 6.7U2 via webUI “https://<FQDN>:5480″ and I ran into this little issue.

First Enable SSH at the vCenter Level – from your Remote Console

Login into your vCenter via Console (VMRC)

Then Go into “Troubleshooting Mode Options”

Then Enable SSH

Login into vCenter via SSH – Once logged in, run this command

service-control --status

Once you run the first command, then run this command to start all vCenter Services to a running and operational state.

service-control --start --all

After all the processes have been started, you may login into your vCenter VAMI, but I prefer to reboot the vCenter Server to give it a fresh start after the service fix.

After this is all done, make sure to DISABLE SSH! Just a security precaution.

July 19, 2019 0 comments 1.5K views
0 FacebookTwitterLinkedinThreadsBlueskyEmail




Recent Posts

  • Offline VMware Cloud Foundation 9 Depot: Your Path to Air-Gapped Deployments
  • VMware Cloud Foundation 9: Simplifying Identity with a Unified SSO Experience
  • What’s New In VMware Cloud Foundation 9.0
  • Deploying & Configuring the VMware LCM Bundle Utility on Photon OS: A Step-by-Step Guide
  • VMware Cloud Foundation: Don’t Forget About SSO Service Accounts

AI cloud Cloud Computing cloud director configure cyber security director dns domain controller ESXi How To las vegas llm llms multicloud NSx NSX-T 3.2.0 NVMe sddc security servers ssh storage tenant upgrade vcd vcda VCDX vcenter VCF vcf 9 VDC vexpert Virtual Machines VMs vmware vmware.com vmware aria VMware Cloud Foundation VMware cluster VMware Explore VMware NSX vrslcm vsan walkthrough

  • Twitter
  • Instagram
  • Linkedin
  • Youtube

@2023 - All Right Reserved. Designed and Developed by Virtual Bytes

Virtual Bytes
  • Home
  • Home Data Center 2025
  • VMware
    • Cloud
    • Datacenter & Cloud Infrastructure
      • VMware ESXi
      • VMware vCenter
      • VMware vSAN
    • Networking & Security
    • Desktop & App Virtualization
      • Omnissa Horizon
    • Troubleshooting
    • Ansible
  • Education
  • Hardware
    • Hardware Tips & Tricks
  • Events
  • About
    • About Me
    • Home Lab Archives
      • Home Lab 2020-2022
      • Home Lab 2016-2020