VxRAIL Resetting Script

I want to get same procedure

So I've checked the SolveDesktop, but nothing the information.

I'm implementation partner, my SolveDesktop status is below.

Regards.

Hi,

Mine has a CS/PS Field Procedures that has the Installation and Reset Procedures.

I suggest you to talk to your EMC contacts.

Thanks,

Hi Gustavo,

Thank you for your advice.

OK, I'll ask EMC guys.

Regards.

Hey Norick,

Did you get the procedure and did you do the reset of the entire appliance? Because I have a case where the configuration didn't finish and I'm required to reset the appliance.

Thanks in advance.

Hi sonivivek,

Yes, I've gotten the procedure and done the reset.

You will get the information from each Generation/Version CS/PS Field Procedure "Restricted Procedures" on SolveDekstop.

And you will get reset tools from VxRail Software support site.

The tools require specific version for VxRail Software.

Regards.

Hello,

Anyone of you noticed if the VSAN gets really destroyed once the Reset is done. I have noticed that its not fully destroyed. I had a Gen2 Appliance which i reset and upon successfully rebuilt i could get access to my ISO folder i created in the VSAN.

That's why we really want trained support folks to run the reset workflows for the customers. ;0)

In order to have vSAN datastore really cleaned up, you will need to use "--eraseVSANObjects" when you perform the reset workflow.

Hi Thank you for the reply. Here is a reset command example. can you show where to add the --eraseVsanobject part.

C:\Python27\python.exe c:\reset\reset.pyc -d --destroyAllVMs -f -a -a -a --vlan [ --initialIpAddress= --initialSubnet= --initialGateway= ]

on the Vxrail reset guide its mention to use it with -destroyALLVMs

It does not really matter where you add it, but this is one possibility...

C:\Python27\python.exe c:\reset\reset.pyc -d --destroyAllVMs --eraseVSANObjects -f ... and so on....

Hi, I will practice destroying VSAN once we get our dummy appliance.

Question:

If Mr. customer had an appliance which was wrongly reset without specifying the --eraseVSANobject switch.

Is there any means to identify which VSAN object is not being used so that it can be deleted to save space.

Thanks.

Is there any means to identify which VSAN object is not being used so that it can be deleted to save space.

Yes, but not to the mortal humans like you and I.

This requires a support call to VMW which can only be made by EMC support folks covering VXRAIL. VMW teams (vSAN specialists) have access to a special tool that can find stale / unused objects and delete them.

Technically, things like ISO images (that you mentioned in earlier comments) could be deleted via datastore browser if they show up there.

Please don't attempt to delete anything using cli commands from ESXi (i.e. rm). That's not supported and can cause other problems.

Hi there.

Just in case that anyone searching for a reset procedure for a VxRail Gen3 system finds that article here:
NEVER EVER use the reset script on a gen3 Node. Even if the support tells you so. If you do use the script an Gen3 hardware it actually starts disabling the VMs but fails in a certain step, leaving the nodes in an unusable state.

The reset procedure for Gen3 is integrated in the system itself. You need to connect via KVM directly to the node and during the boot process you see an additional boot option (called RASR boot) to select. Use that one to boot into some sort of service mode where one selection is resetting the node. If you try this on a script resetted node, you will see bad block errors preventing the reset function from running. If you do see this, just reboot the node once more, repeating the exact same steps like before, and everything will work in the second attempt. Don´t ask me why that actually happens, it did on ten nodes in a crashed by script cluster for me. Support told me do use the golden image and reimage the nodes what would have taken a lot more time to do.

I´m not sure wether or not all support staff is actually aware of that issue so this is a "just in case" information. :-)

That's not supposed to happen. Feel free to ping me (privately) with the Dell EMC case number, so we can reach out to the support leadership team and RCA this.

Thanks.

Of course it´s not. :-)

It happened February this year twice with the Pearl Script solution. It might have been changed by now so maybe it won´t happen again, I only wanted to be sure, that the correct reset procedure is used with Gen3 systems. The case is already "solved" by now with the described solution. But of course you can check the related SR. I´ll send you the number via PN.

Thanks for the prompt response.

Regards

Terence