VCF Automation 9.1 Environment Inaccessible Due to VIP Conflict with Legacy 9.0 Virtual Machines

Products

• VMware vSphere ESXi
• VMware Cloud Foundation

Issue/Introduction

After an expansion of the underlying datastore, the VCF Automation (VCFA) 9.1 environment becomes inaccessible. This article provides steps to resolve service recovery failure issues caused by datastore expansion and VIP contention. This scenario typically occurs when legacy VCF Automation 9.0 virtual machines remain powered on concurrently with the active 9.1 environment, leading to resource and networking conflicts.

Environment

• VMware Cloud Foundation (VCF) 9.1
• VCF Automation 9.1
• Legacy VCF Automation 9.0.x environment

Cause

Concurrent activation of legacy 9.0 VMs causes Virtual IP (VIP) contention with the 9.1 production environment.

Resolution

1. Expand the underlying datastore to resolve the initial storage-level stun condition.
2. Identify and power off all legacy VCF Automation 9.0 virtual machines that are active in the environment.
3. Validate that the production 9.1 environment is the sole consumer of the configured VIP.
4. Verify accessibility of the VCF Automation 9.1 environment.

Additional Information

If you encounter this issue, verify that no legacy 9.0 infrastructure components (VMs/services) are active before attempting to recover the 9.1 services. For further assistance with environment recovery, visit the Contact Broadcom Support page.

Note: For defects and enhancements, we recommend you subscribe to this article to receive updates on fix status.