vCenter became inaccessible following the migrating of a new DVS due to incorrect uplink configuration.

search cancel

book

calendar_today

VMware vCenter Server

You may find that the VMware vCenter Server and multiple virtual machines (VMs) enter an "Inaccessible" state within your environment.
This issue occurs when a host or cluster experiences a total loss of storage connectivity, rendering the underlying datastore unavailable.
While the virtual machines and vCenter become unresponsive, host management services typically remain available, allowing direct CLI access to the affected ESXi hosts.

VMware vCenter Server

The issue can occur when active storage network uplinks are mistakenly disconnected from the intended production storage DVS Network.
This misconfiguration interrupts storage communication for the ESXi hosts, causing the storage VMkernel interface (vmkX) to lose connectivity.
Once storage access is lost, the associated datastore becomes inaccessible, resulting in impacted virtual machines and vCenter Server becoming unavailable.

To restore connectivity to your storage network and bring vCenter and the impacted VMs back online, perform the following steps:

Access the ESXi Host Directly
Since vCenter is unavailable, connect directly to the affected ESXi host using SSH or through the local console.
Correct the DVS Uplink Assignment
Identify the physical uplinks connected to the incorrect or test DVS network and move them back to the intended production storage DVS network.
Example commands:
```
esxcfg-vswitch -Q vmnicX -V dvPort_ID_of_vmnic "dvSwitch"
```
Removes/unlinks the physical uplink from the current vDS assignment.
```
esxcfg-vswitch -P vmnicX -V unused_dvPort_ID "dvSwitch"
```
Adds/reassigns the physical uplink back to the required vDS uplink port.
Restore Storage VMkernel Connectivity
Verify and restore connectivity for the vmk1 storage interface after correcting the uplink assignment.

thumb_up Yes

thumb_down No