vCenter Server 7 to 8 Upgrade: No Networks Available for Target VCSA VM Due to Static VDS Port
search cancel

vCenter Server 7 to 8 Upgrade: No Networks Available for Target VCSA VM Due to Static VDS Port

book

Article ID: 403255

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

During the vCenter Server upgrade process from version 7 to 8, users may encounter an issue where no networks are available for selection when deploying the target vCenter Server Appliance (VCSA) VM.

Environment

VMware vCenter Server

Cause

This issue occurs when the source VCSA is configured on a static vSphere Distributed Switch (VDS) port.
For further explanation please see  > Upgrading the vCenter Server Appliance

Resolution

The most straight forward solution to this issue is setting the deploy target of the new vCenter Server Appliance as the current vCenter FQDN.  Once set in the upgrade wizard, the distributed switch port groups will be visible and the correct network for the deployment can be selected.

Additionally there are two other possible solutions if you cannot set the deploy target as the vCenter Server, all ideally performed before initiating the upgrade:

  1. Create an ephemeral port group on the same vSphere Distributed Switch (VDS) with the same VLAN as the vCenter Server Appliance (VCSA) currently uses. This is generally the simpler and recommended approach. The Broadcom TechDocs page "Static (non-ephemeral) or ephemeral port binding on a vSphere Distributed Switch" (Static (non-ephemeral) or ephemeral port binding on a vSphere Distributed Switch) provides further details on this.

  2. Migrate to a vSphere Standard Switch (VSS): Move the source VCSA from its static VDS port to a vSphere Standard Switch (VSS) before initiating the upgrade. After the upgrade and data transfer are complete, the new vCenter Server Appliance can be manually reconnected to its original non-ephemeral distributed virtual port group on the VDS. This method is more complex and carries a higher risk of network disruption if an incorrect vmnic is moved from the VDS to the VSS. However, it becomes the only viable option if the vCenter VM loses network connectivity and cannot be restored even with a rollback when attempting to use an ephemeral port group. This is necessary because when deploying the vCenter Server appliance directly on an ESXi host, non-ephemeral distributed virtual port groups are not supported and are not shown during the initial deployment phase.

Additional Information

Powered by Wolken Software