In VCF 9.x, offline depots rely on a centralized /metadata directory containing productVersionCatalog.json and vcfManifest.json for SDDC Manager and Fleet Management to detect binaries, compatibility, and HCL data. In an environment that disconnected the local repository lacks the updated point-in-time manifest required to recognize the 9.0.2.x binaries.
VCF 9.0.x
VCF 9.1.x
VCF 9.0+ architecture requires metadata to be continuously updated directly through Broadcom's infrastructure. By default, metadata is either fetched directly during a metadata refresh or pulled automatically each time a binary is downloaded via the VCFDT. Without direct internet access or the manual staging of these files, the lifecycle management services will fail to sync.
To resolve the missing metadata in the dark site, the customer can utilize one of two methods from an external, internet-connected machine:
Method 1: Point-in-Time Metadata ZIP (Static)
Navigate to the Broadcom Support Portal (BSP).
Download the standalone 9.0.2 metadata file: vcf-9.0.2.0-offline-depot-metadata.zip.
Securely transfer the ZIP across the airgap and extract it into the root directory of the local depot server to build the /PROD/metadata/ structure.
Method 2: VCF Download Tool (Dynamic & Recommended)
Download the latest VCF Download Tool from the BSP.
Run the tool on an external connected machine; it will automatically fetch the most up-to-date metadata, compatibility, and HCL data alongside the binaries.
Transfer the generated payload to the dark site depot.
1. VCF Download Tool (BSP): VCF 9.x Drivers & Tools Download
2. VCF 9.0.2 Static Metadata (BSP): VCF 9.0.2.0 Offline Depot Metadata Download
3. Offline Depot Configuration Guide: William Lam's VCF 9.1 VCF Download Tool (VCFDT) Cheatsheet provides documented, validated steps for configuring local HTTP/HTTPS servers and working with offline depots using the VCFDT.