vCenter Becomes Inaccessible After vMotion Due to Incorrect VLAN Configuration
search cancel

vCenter Becomes Inaccessible After vMotion Due to Incorrect VLAN Configuration

book

Article ID: 421993

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • After performing a vMotion of the vCenter virtual machine, vCenter Server is unable to connect over the configured VM network.
  • The vMotion task completes successfully, but network connectivity to the vCenter Server is lost.

Environment

VMware vCenter 8.x

Cause

  • The destination ESXi host is not configured with the required VLAN ID for the VM network.
  • The VM network on the destination host is misconfigured with the wrong VLAN ID, resulting in loss of network connectivity after migration.

Resolution

  • Review and confirm that both the source and destination ESXi hosts have consistent and matching VLAN settings for the VM network.
  • Edit the VM network settings on the destination ESXi host to match the working settings on the source ESXi host the vCenter was migrated from.
  • Configure the correct VLAN ID for the port group used by the vCenter virtual machine.
  • After updating the VLAN configuration, verify that the vCenter Server is accessible by the management network.
Powered by Wolken Software