VMware vSphere VM Disk Expansion or Console Access Issues During Replication Failover

Products

• VMware vCenter Server

Issue/Introduction

• This article describes a scenario where virtual machine (VM) disk size increases performed at the vCenter layer do not reflect within the Guest Operating System (GOS), and attempts to access the VM console fail.
• These symptoms occur when a VM is managed by a replication solution, such as Dell Power Protect, and the active instance of the VM resides on a recovery site while the administrator attempts to manage the VM on the protected site.

• Evidence of this mismatch often includes:

  • MAC address discrepancies between the NIC configuration in the protected vCenter and the MAC address observed within the GOS console.

  • The protected VM failing to reach the domain or authenticate, as it is not the active instance.

  • 

Environment

• VMware vCenter Server any version

Cause

• The root cause is a configuration state mismatch.
• The VM has been failed over to a replication site, meaning the "active" VM is currently running on the replication site vCenter.
• However, administrative attempts to modify or access the VM are being directed at the "protected" (source) site vCenter, where the VM is not truly active or fully reachable.

Resolution

Prerequisites

• Verify the current replication status of the VM via the Power Protect interface.

Steps

1. Identify Active Site: Log in to the Power Protect management interface to verify the current replication status and determine which vCenter site is hosting the active VM.
2. Verify vCenter Registration: In the vSphere Client, navigate to the VM and check the host and datacenter to confirm if it matches the active site identified in step 1.
3. Confirm VM State: Compare the MAC address of the VM's NIC in the vCenter VM Settings against the MAC address reported by the GOS (e.g., via ipconfig /all or ifconfig). A mismatch confirms the VM is running on a different vCenter site.
4. Access Active VM: If the VM has been failed over, perform all management tasks, such as disk expansion or console access, directly through the vCenter Server at the recovery site where the active VM resides.
5. Guest OS Rescan: Once connected to the active VM, perform a disk rescan in the GOS (e.g., Disk Management in Windows) to recognize the newly added storage space.
   
   

Workaround

If the replication state is unclear, halt all management attempts on the protected site to avoid configuration drift and immediately contact the replication vendor for guidance on failover and recovery state management.