Upgrading prechecks for VCFA/ VCF Automation fails withTopology Pre-checkIP addresses are unique across configurations Failed
Duplicate IP addresses detected across source VIPs, platform VIPs, or IP pool configurations.
When upgrading the VCFA/ Automation via https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/deployment/upgrading-cloud-foundation/phase-3-import-and-upgrade-aria-automation-8-to-vcf-automation-9.html, make sure that the VCF services runtime FQDN for VCF Automation is a NEW DNS/ FQDN entry, that is not in use.
Don't use the FQDN for VCF services runtime, or the FQDN for the 9.0.X VCF Automation, to be upgarded.
Because of the design change, switch from appliance to containers, the new FQND/ DNS for the "VCF services runtime instance that hosts the 9.1 VCF Automation nodes" it's required as a migration helper.
Logs check:
- ssh on the VCF services runtime with "vmware-system-user"
- elevate to root via# sudo -i
# less /tmp/services-logs/prelude/runtimevcf-mcfcm/vcfa-precheck-upgrade-90-topology-4gpc8-execute-script-<UUID>/main/console-log-<Epoch_Timestamp>.log
<Date && Time> stderr F 2026-06-04 13:10:57 [ERROR] - <OFFENDING_IP> (platform VIPs and source VIPs)
<Date && Time> stderr F 2026-06-04 13:10:57 [ERROR] PRECHECK FAILED: IP addresses must be unique across all configurations. Duplicates found: <OFFENDING_IP> (platform VIPs and source VIPs)9.1
Create 1 New FQDN with a unique corresponding IP, for the VCF services runtime instance that hosts the 9.1 VCF Automation nodes.
The corresponding IP must be outside of the CIDR that you already dedicated.
This FQDN is used only internally between VCF components, is not user-facing, and will not change the VCFA original FQDN/ IP etc.
https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/deployment/upgrading-cloud-foundation/phase-3-import-and-upgrade-aria-automation-8-to-vcf-automation-9.html