VMware Cloud Foundation

 View Only
  • 1.  Air gap VVF deployment

    Posted Aug 29, 2026 10:01 PM

    I am deploying an air gapped VVF environment. I would like some comments on which is the better of the two options for obtaining lifecycle updates:

    1. Using the VCF download tool and pointing vCenter lifecycle to a UMDS repository it populates.
    2. Simply download the ESXi update depot and the Dell customizations and uploading manually through Lifecycle

    #1 seems overly complicated for just needed to upgrade the hypervisors, this is not a VCF deploymnet

    #2 i worry i may miss something that the VCF downloader would grab

    Thank you.



  • 2.  RE: Air gap VVF deployment

    Posted Aug 30, 2026 11:57 PM

    Hi Jeff,

    For a true air-gapped VCF environment, I would go with option 1 and maintain an internal/offline depot rather than manually importing each ESXi update into vCenter.
     
    Broadcom provides a supported VCF Offline Depot workflow specifically for disconnected environments. For VCF 5.2+, you can configure it under SDDC Manager → Lifecycle Management → Depot Settings → Set up an Offline Depot.
     
    This gives you a more repeatable lifecycle process and avoids manually moving individual bundles for every update. You can also point vCenter Lifecycle Manager to the offline UMDS repository and synchronize the ESXi image metadata/vendor add-ons from there.
     
    For option 2, manually importing the ESXi offline bundle and Dell vendor add-on into vLCM is supported for isolated vCenter environments, but I would use it more as a targeted/manual approach rather than the primary lifecycle strategy for VCF.
     
    So you aren't missing anything major with option 2, but for VCF I would prefer the Offline Depot approach because it keeps lifecycle management centralized and repeatable.



  • 3.  RE: Air gap VVF deployment

    Posted Sep 01, 2026 11:10 PM
    Edited by jeffj2000 Sep 01, 2026 11:10 PM

    Thank you! I will go with option 1, that makes sense. It is strange because I have turned off al telemetry (I think), and have lifecycle directed to a UMDS store, yet still every minute I see vCenter sending traffic to "162.159.140.167" "172.66.0.165" which are the Broadcom cloudflare IPs. 

    I cant figure what in vCenter would still be wanting to talk to Broadcom? This is a VSAN implementation and I have turned the internet connectivity off, which I believe means it shouldn't try to send telemetry as well. Any ideas?