Error: One or more platform VIPs are already in use on the network during upgrade to VCF Automation 9.1

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

During the VCF Automation (VCFA) 9.1 upgrade process, specifically during the "Run Component Upgrade Precheck" task for VCF Automation Upgrade, the precheck may fail. This validation ensures that the new VCF services runtime environment has a dedicated, unique IP address. If the FQDN provided resolves to an IP already responding on the network, the upgrade cannot proceed.

Symptoms

• The VCF Automation upgrade task fails at the stage Run Component Upgrade Precheck with following error :
  

  One or more platform VIPs are already in use on the network.
  [com.broadcom.vcfa.upgrade.topology.check.test-topology-08b-platform-vip-available] 
  Resolution: The platform FQDN resolves to one or more VIPs that will be assigned to the new deployment. All resolved IP addresses must not be in use. Either free up the conflicting IP addresses or update DNS to point the platform FQDN to available IP addresses.

•  In VCF Automation 9.0.x, /tmp/vcfa-upgrade/logs/upgrade-precheck--test-topology-08b-platform-vip-available--<timestamp>.log reveals the following warning :
  

  YYYY-MM-DD HH:MM:SS [WARNING] IP ###.###.###.### is in use

Environment

VCF Automation 9.0.x

Cause

In VCF Automation 9.1, it requires a new FQDN for the VCF services runtime instance. The precheck fails if the IP address resolved by this FQDN is already assigned to a source node (VCF Automation 9.0.x node), a VIP, or any other device responding to network requests (Ping/ARP).

Resolution

1. Identify the IP Conflict: Perform an nslookup on the FQDN provided for the VCF services runtime to identify the resolved IP address.
2. Verify Usage: Confirm if the IP is currently in use by another device or is part of an existing IP pool/CIDR assigned to the VCF Automation 9.0.x nodes.
3. Update DNS: Change the DNS record for the VCF services runtime FQDN to point to a new, unused IP address. This IP must be outside of any existing CIDR blocks used by the current VCF Automation nodes.
4. Verify Availability: Ensure the new IP does not respond to a ping request before retrying.
5. Retry Upgrade: Retry the failed VCF Automation upgrade request from the Fleet Management.