VMware Cloud Community
kalebschaffner
Contributor
Contributor
‎05-18-2019 09:17 PM

Changed VDS uplink association, vSAN down, hosts can't ping.

Greetings,

I changed the associated VDS uplink to which physical vmnic was on which VDS vmnic (ex VDS uplink vmnic0 = physical vmnic1) to where vmnic0=vmnic4. Now my vCenter was running on this vSAN cluster and after doing that change, I can no longer ping the hosts on their vSAN IPs from others, vSAN itself is down and the vCenter server was on this vSAN and cannot be reached as it's down. Any idea on anything that I can do to get this back up and running?

On the ESXi host itself, it can't see the datastore to do anything with it.

Tags (3)
0 Kudos
1 Reply
kalebschaffner
Contributor
Contributor
‎05-18-2019 09:34 PM

Sooo.... turns out fixing the association via cli on the ESXi host with esxcfg-vswitch and putting back the NICs in the same order, resolved the issue entirely. We were trying to get rid of the copper management cable and go to all 10Gig.

I will update this post here soon with more information and screenshots to help any future users with this issue.

0 Kudos