Error "...does not belong to management network subnet..." While Deploying VCF Management Components on an NSX Overlay Segment during Day 0 deployment in VCF Installer

Products

• VMware SDDC Manager

Issue/Introduction

Following the documentation Deploy VCF Management Components on an NSX Overlay Segment for a Day 0 VCF deployment via VCF Installer results in an error on step 3

VCF Management Components validation workflow failed due to the following error(s): VCF Automation FQDN [automation_appliance_fqdn] is resolved to x.x.x.x IPv4 IP address, but it does not belong to management network subnet x.x.x.0/x obtained from vCenter server , VCF Automation node IP address x.x.x.x does not belong to the management network subnet x.x.x.0/x obtained from vCenter server , VCF Operations Node FQDN [operations_appliance_fqdn] resolved to x.x.x.x IPv4 IP address, but it does not belong to management network subnet x.x.x.0/x obtained from vCenter server , VCF Operations Collector FQDN [operations_collector_fqdn] is resolved to x.x.x.x IPv4 IP address, but it does not belong to management network subnet x.x.x.0/x obtained from vCenter server , VCF Operations Fleet Management FQDN [fleet_appliance_fqdn] is resolved to x.x.x.x IPv4 IP address, but it does not belong to management network subnet x.x.x.0/x obtained from vCenter server

Environment

VMware Cloud Foundation (VCF) 9.0

Cause

Known issue with the spelling of vcfManagementComponentsInfrastructureSpec in the JSON body provided in the documentation and in the API documentation within the VCF Installer when used for Day 0 deployment. This will be fixed in a future version of the product.

Resolution

Edit the JSON file created in step 1 of the instructions at Deploy VCF Management Components on an NSX Overlay Segment to correct the spelling from "vcfMangementComponentsInfrastructureSpec" to "vcfManagementComponentsInfrastructureSpec"

Note: If you are performing a Day N deployment via an already existing SDDC Manager, keep the misspelled version of "vcfMangementComponentsInfrastructureSpec" in the JSON file as the API requires this spelling to function.