LCMVSPHERECONFIG1000041: VCF Cloud Proxy deployment fails with 'Invalid network details'
search cancel

LCMVSPHERECONFIG1000041: VCF Cloud Proxy deployment fails with 'Invalid network details'

book

Article ID: 453799

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • The VCF Installer fails during the Cloud Proxy deployment validation stage, displaying "error code LCMVSPHERECONFIG1000041: Invalid network details. This issue occurs when the network provided during the request is unrecognized or cannot be located within vCenter. Please verify your network configuration settings in vCenter and retry the deployment with the correct details."

  • The below screenshot shows the Task failure at Stage 1 of VCF Installation encountered during 'Validate Deploy Inputs' with an error message as LCMVSPHERECONFIG1000041. Upon expanding the error code, details of the error message as mentioned above can be seen in the screeshot.

 

  • Log snippet report about expected "dvs-portgroup-name" for the given vCenter server as per configuration spec file, is not to be found;

/var/log/vrlcm/vmware_vrlcm.log: 


YYYY-MM-DDTHH:MIN:SEC INFO vrlcm[####] [pool-3-thread-62] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMVSPHERECONFIG1000041', Retry : 'true', Causing Properties : '{ CAUSE :: ip === hostName === gateway === domain === searchpath === dns === netmask === network === deleteVm === vCenterHost === vcUsername === vcPassword YXYXYXYX  }'
com.vmware.vrealize.lcm.common.exception.userinput.InvalidNetworkDetails: Exception occurred while validating inputs for product : vrops. Unable to find networks : ["dvs-portgroup-name"] for the given clusterMO ::Stub: moRef = (ManagedObjectReference: type = ClusterComputeResource, value = domain-c10, serverGuid = null), binding = https://vCenterFQDN/sdk/vimService
        at com.vmware.vrealize.lcm.drivers.vsphere65.deploy.impl.BaseOvfDeploy.getDeployOptionsMOR(BaseOvfDeploy.java:1298) ~[vmlcm-vsphereplugin-driver-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.plugin.core.vsphere.tasks.ValidateDeployInputsTask.execute(ValidateDeployInputsTask.java:276) [vmlcm-vsphereplugin-core-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158) [vmlcm-engineservice-core-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60) [vmlcm-engineservice-core-9.0.2.0-SNAPSHOT.jar!/:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
        at java.base/java.lang.Thread.run(Unknown Source) [?:?]
YYYY-MM-DDTHH:MIN:SEC INFO vrlcm[####] [pool-3-thread-62] [c.v.v.l.p.a.s.Task]  -- ========================================
{
  "product" : {
    "object" : {
      "vmid" : "####",
      "tenant" : "default",
      "productUuid" : "####",
      "fleetEnabled" : false,
      "nodes" : [ ],
      "properties" : {
        "cloudProxyOTK" : "JXJXJXJX"
      },
      "references" : [ ]

Environment

VMware Cloud Foundation

VCF 9.x

Cause

The error "LCMVSPHERECONFIG1000041: Invalid network details" is a generic indicator that the network configuration in vCenter does not match the parameters specified in the VCF config.spec file. While this can result from various network mismatches, a common scenario is the manual renaming of a port group in vCenter after the VCF installation process has been initiated. In such cases, the Lifecycle Manager fails to locate or validate the expected virtual network, resulting in an automated deployment failure.

Resolution

To resolve the "Invalid network details" (LCMVSPHERECONFIG1000041) error, you must ensure the network configuration in vCenter aligns exactly with the parameters defined in the VCF config.spec file. Follow these steps:

  1. Port Group Name as stated in VCF Installer
    1. UI: Download the JSON file directly from the Cloud Builder interface on the screen where the Excel workbook was uploaded.
    2. SSH:  Log in to the Cloud Installer appliance via SSH and check the /opt/vmware/sddc-support/ or /opt/vmware/bringup/ directories.
    3. Open the .json file and search (Ctrl+F) for networkSpecs or portGroupSpec. Locate the portGroupName value (e.g., "portGroupName": "VCF-vMotion-PG"). Note the exact spelling and casing.
    4. Retrieve the correct port group name from the original VCF config.spec file (generated from your VCF Deployment Parameter Workbook). 
  2. Port Group Name as in vCenter Server
    1. Log in to the vCenter server Client using an administrative account.
    2. Navigate to Networking, expand the appropriate Datacenter and Distributed Switch, and locate the port group that was modified.
    3. Right-click the port group, select Rename, and update it to match the exact string retrieved from the config.spec file. Ensure there are no leading or trailing spaces, as the validation is case-sensitive. Match the Port-Group recorded in 1.d
  3. Return to the Cloud Builder or SDDC Manager interface and click Retry on the failed task to resume the installation.

Additional Information

As stated earlier, the error "LCMVSPHERECONFIG1000041: Invalid network details" is a generic indicator of the network configuration mismatch in vCenter.
See also VCF 9.0 Deployment Fails Due to DVPortGroup Naming with Forward Slash

Powered by Wolken Software