erives
Enthusiast
Enthusiast

Renaming vSan vDS uplinks kills cluster

Jump to solution

I am sure this is a vDS rookie mistake on my side but Renaming the vSan vDS uplinks on a vSan cluster will Kill the cluster, dead Smiley Happy , the fact that my vcenter was within the cluster made things a little harder when trying to recover. I tried searching for documentation prior to making the change and there is no KB article explaining this behavior (GSS could not find one either.), but what it is more troubling is that no warning message is shown saying that the uplinks are being used and that stuff will stop working. Solution was to manually create a vSS and move and uplink and vmk to it, not fun since vC was down.

Tags (4)
1 Solution

Accepted Solutions
depping
Leadership
Leadership

It has been reported to our Product Management team, and they will be looking to see how we can prevent these situations from happening.

View solution in original post

10 Replies
larstr
Champion
Champion

erives,

What versions are you on. What exactly did you rename?  I've renamed the VDS port groups for vSAN without problems before.

Most things you do on a vDS will work out fine with vSAN, except changing MTU.

Lars

0 Kudos
SureshKumarMuth
Commander
Commander

Renaming uplink will disrupt your VDS operation, I have seen faced this issue.

Regards, Suresh https://vconnectit.wordpress.com/
larstr
Champion
Champion

Had to test it and can confirm that it fails....

pastedImage_0.png

Lars

erives
Enthusiast
Enthusiast

If you want to experience a roller coaster adrenaline type rush I encourage you to try it Smiley Happy (j/k). On the vC UI interface select the vDS / Configure / properties / Edit / Edit uplink names. Kids do not try this at home Smiley Happy.

Like i said, i am really green with vDS, but i always do my due diligence before making changes and I just could not find any KB explaining this and GSS confirmed there was nothing out there either. I think there is a post in the vSphere forum from someone that did this on the Mgmt vDS and it failed too. I did it on the vmotion vDS switch first and didnt see any issue but the moment i touched the vsan vDS everything shut down.

0 Kudos
TheBobkin
VMware Employee
VMware Employee

Hello erives​/Lars,

Would one of you be able to confirm whether the same behaviour occurs in the Flash-based client?

Bob

0 Kudos
larstr
Champion
Champion

Bob,

The exact same thing happens by using the flash client. Dangerous stuff.

pastedImage_0.png

Lars

0 Kudos
erives
Enthusiast
Enthusiast

Lars,

I know right. they should have that grayed out or give you at least a big red warning. i think a feature request may be the next step on this.

Ed

0 Kudos
TheBobkin
VMware Employee
VMware Employee

Hello Ed,

Feature Request is probably not the right avenue, more so PR(Problem Report) as this appears to be a supported workflow from our documentation (at least at uplink creation - and if not there should be both documentation and warnings of the impact of this). Can you PM me the SR number you opened for this? Also if you have the link to the Communities post that you think appears similar but Management network (as this is potentially not specific to vSAN traffic).

Bob

SureshKumarMuth
Commander
Commander

Hi Bob,

This is not something new, I have seen this issue from version 5.5. Changing the uplink name has always been causing issues and I was hoping this would have been rectified with some warning message in newer releases or VDS newer version checks the impact and roll back when we do some changes in port group.

Please keep us posted about your investigation results  on this issue with Engineering team.

Regards, Suresh https://vconnectit.wordpress.com/
depping
Leadership
Leadership

It has been reported to our Product Management team, and they will be looking to see how we can prevent these situations from happening.

View solution in original post