"Not all addresses from the VCF Management Services IPv4 pool are part of the management network" when deploying VCF Management Services.
search cancel

"Not all addresses from the VCF Management Services IPv4 pool are part of the management network" when deploying VCF Management Services.

book

Article ID: 440223

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

This article provides guidelines for choosing IPs during a VCF Management Services deployment. 

During a VCF 9.1 greenfield installation or upgrade, the Management Services Platform (VMSP) cluster fails to deploy and displays the following error:

Not all addresses from the VCF Management Services IPv4 pool are part of the management network

Environment

VMware Cloud Foundation 9.1.x

Cause

This failure occurs because the IP address range or CIDR provided for the VCF Management Services does not reside entirely within the existing Management Network.

Resolution

You can resolve this issue using the UI Method (for standard, contiguous IP blocks) or the API Method (for non-contiguous IPs or custom networks).

The minimum required is 12 IPs, up to a maximum of 30 IPs for a fully scaled out deployment. The additional 18 IP addresses are required later for these scenarios:

  • New VCF Management Services components are added (Log Management, Realtime Metrics).
  • Existing VCF Management services are scaled out (Log Management).
  • New VCF Management Services nodes are added as an upgrade to future versions.

Expanding the VCF Management Services range is possible post-deployment using the steps in Network Actions for VCF Services Runtime.

 

UI Method

Refer to Deploy VCF Management Services and License Server as Part of VCF Upgrade to 9.1 - UI Procedure for full details.

  • Install: Provide a continuous IP range that resides within the existing Management Network. The minimum required range is 12 IPs, up to a maximum of 30 IPs for a fully scaled out deployment. 
  • Upgrade: Provide a CIDR range that resides within the existing Management Network. The minimum required range is a /28 network (12 IPs)  up to a maximum of 30 IPs (a /27 network) for a fully scaled out deployment. 

(Broadcom is working to improve the UI options available in upcoming releases.)

 

API Method

Use the SDDC Manager API to assign non-contiguous IPs or to define a custom network if your management network lacks sufficient space.

  1. Navigate to the SDDC Manager API Explorer via VCF Operations UI > Build > Developer Center > APIs and SDKs > SDDC Manager > API Explorer.

  2. Draft a JSON payload for the API-driven deployment based on the VCF 9.1 upgrade documentation.

  3. Locate the vspClusterSpec section in your JSON payload and define your IPs using only one of the following formats: a CIDR, an IP Range, or a list of non-continuous IPs.

  4. (Optional) You can define a custom network using the xRegionNetwork object in your payload if IP space is limited. The IPs defined in the vspClusterSpec must reside in this network if utilized. The VMware Identity Broker (vIDB) must also reside on this custom network or be transitioned to it first.  Remove this section if its not necessary.

  5. Validate your JSON payload by executing POST /v1/vcf-management-components/validations.

  6. Retrieve the validation results using GET /v1/vcf-management-components/validations/{validationID} and correct any errors received.

  7. Execute the deployment by copying your validated payload into POST /v1/vcf-management-components.

  8. Monitor the task progress via VCF Operations UI > Build > Tasks.

 

 

Additional Information

The configuration wizard UI requires the following:

  • A dedicated IP range for the VCF services runtime with a minimum of 12 IP addresses up to a maximum of 30 IPs.
  • FQDNs for VCF services runtime, fleet component, and instance component.
    • In the context of deploying VCF management services, the required FQDN for the fleet component includes the fleet lifecycle, Salt RaaS, and software depot components.
    • The FQDN for the instance component includes the SDDC lifecycle, Salt master, real-time metrics, real-time metrics store, and telemetry components. 
  • FQDN for Identity Broker 
    • Important: vIDB must reside on the same network as the VCF Management Services, whether that be the management network or a custom defined one.
  • FQDN for the License Server that is deployed separately. 

All FQDNs must resolve to unique IP addresses outside of the IP range provided for the VCF services runtime, but still within the management network.

 

Refer the documents below for more information:

Powered by Wolken Software