SDDC Manager precheck fails due to Virtual nic static IP check
Article ID: 433966
Updated On:
Products
Issue/Introduction
In VMware Cloud Foundation (VCF), an SDDC Manager upgrade fails during the precheck phase. The out-of-band check fails with the following error:
Cannot connect to vCenter <REDACTED_ID> of domain <REDACTED_HOSTNAME> to complete inventory sync
The domainmanager.log file contains errors similar to the following:
[OL4044] IMPORT_OPERATION_FAILED Import operation for sync with id <REDACTED_ID> failed internally. Command was python3 /opt/vmware/vcf/domainmanager/scripts/vcf-import-tool/vcf_brownfield.py sync --domain-name <REDACTED_HOSTNAME> --skip-ssh-thumbprint-validation --internal-vcf-auth --output-dir /var/log/vmware/vcf/domainmanager/brownfield/<REDACTED_ID>/ --non-interactive.
The Guardrails file located in /var/log/vmware/vcf/domainmanager/brownfield/<REDACTED_ID>/ on the SDDC Manager appliance shows the following failure:
"virtualNic","vmk1_<REDACTED_HOSTNAME>","Import","ERROR","VALIDATION_FAILED","Virtual nic static IP check.","Check if IP address associated with the virtual nic is static.","Virtual nic does not have a static IP assigned.","Ensure the virtual nic has an assigned static IP address by disabling DHCP."
Environment
VMware Cloud Foundation 9.0.0.0
Cause
The validation precheck fails because a VMkernel adapter (e.g., vmk1) is configured with a static IPv6 address, but the IPv4 settings are left as DHCP. The precheck strictly requires a statically assigned IP address and fails when DHCP is detected.
Resolution
-
Log in to the vSphere Client.
-
Navigate to the specific ESXi host identified in the Guardrails log.
-
Select the affected VMkernel adapter (e.g., vmk1).
-
Edit the settings and change the IPv4 configuration to No IPv4 settings.
-
Clear the failed synchronization tasks in the SDDC Manager UI.
-
Retry the inventory sync and proceed with the SDDC Manager upgrade precheck.
Additional Information
Subscribe to this knowledge article to get updates on this issue.
Feedback
