Error: vIDM login failure and network isolation after failed VxRail upgrade

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After a failed or partially successful VxRail upgrade, the VMware Identity Manager (vIDM) environment may become inaccessible. While nodes appear powered on in the vSphere Client, login attempts fail with a blank page or red error, and Aria Suite Lifecycle (LCM) recovery operations fail.

Symptoms:

• vIDM login page is blank or displays a generic red error.
• One vIDM node (typically Node 3) is unreachable via SSH.
• Aria Suite Lifecycle auto-recovery or power operations return errors.
• The vIDM node shows as isolated in the database cluster health check.

Environment

• VMware Cloud Foundation (VCF) on Dell VxRail
• VMware Identity Manager (vIDM) 3.3.x

Cause

During the VxRail upgrade, the VM network configuration for a vIDM node is misconfigured, assigning the VM to an incorrect network port group. This prevents the node from communicating with the rest of the cluster and the database.

Resolution

Perform these steps to get this fixed

1. Log in to the vSphere Client.
2. Locate the vIDM VM that is unreachable via SSH.
3. Right-click the VM and select Edit Settings.
4. Verify the Network Adapter port group. If it does not match the other cluster nodes, reassign it to the correct port group.
5. Establish an SSH session to the recovered node as root.
6. Restart the database services to restore cluster quorum using these commands:  /etc/init.d/vpostgres restart  &  /etc/init.d/pgService restart
7. In Aria Suite Lifecycle, perform an Inventory Sync for the vIDM environment.