Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCenter Server loses network connection after DRS vMotion when configured with DVS network Port Group (1023181)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 20111Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

vCenter Server loses network connection after DRS vMotion when configured with DVS network Port Group

vCenter Server loses network connection and the VirtualCenter Server service stops if it is migrated to a host that is configured for DVS port group and does not have an appropriate physical uplink connected to it.

You cannot reconnect to the network

If you try to reconnect to the network, you see the error:

Invalid configuration for device - 0

Cause

This issue occurs if:

You have vCenter Server running in a virtual machine with two hosts configured in DRS cluster that is set to Fully Automated mode.

vCenter Server is connected to a port group on a distributed virtual switch (DVS).

You add a third host to the cluster and to the DVS, which triggers vMotion of the vCenter Server virtual machine from the inventory.

The vCenter Server virtual machine is migrated to the third host, which does not have the uplinks connected yet.

This causes the VirtualCenter Server service to stop and the vCenter Server virtual machine network to go into a disconnected state.

This issue may also occur if the vCenter Database Server is a virtual machine and is migrated to the third host, which does not have the uplinks connected yet. This causes the vCenter Server to fail to connect to its database virtual machine.

Resolution

To workaround this issue, connect the vCenter Server virtual machine to the standard switch port group, then later migrate to DVS when the third host's physical uplinks are configured:

Determine which host holds the vCenter Server virtual machine and connect vSphere Client directly to it.

Create a port group on standard vSwitch on this host and configure it for the required VLAN (if any).

Connect a valid uplink to this vSwitch.

Connect the network adapter uplink of the vCenter Server virtual machine to this Standard Switch port group.

Start the VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Connect vSphere Client to the vCenter Server.

Configure the third host's physical uplinks before migrating it back to the DVS port group.

Change the network adapter uplink to DVS port group and delete the standard vSwitch when connectivity is restored.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant