One of the things that was very welcome for me (&colleagues) was the possibility to set MPIO defaults in vSphere. It wasn't waterproof when you had multiple types of storage but if you had Equallogic or EVA for example that did help not having to go into each datastore to check if MPIO was set correctly.
But I do have a war story you might like: I was HP Enterprise Storage certified so I did know one or two things about my stuff. So on that day that one of our EVA's at a customer (local gov wth 1000 active desktop clients) got stuck on a RAID rebuild at around 38% I called support. The only thing they needed to do was giving the controllers a little kick so that it would restart the rebuild. Nothing fancy. They would send an "HP Enterprise Storage certified" engineer to get it done. You get where we are going here? "No problem, just get me through the procedure. I can handles this".
So that's what we did. Hooking up the laptop at the serial port of the controller and going into config mode. Now enter this 4 digits hexadecimal command and we are done. The array reboots, one controller at a time and ... it's EMPTY! The whole config is gone, all RAID groups have disappeared, no more users, volumes, ... Guess what happened? I switched 2 of the 4 digits and magically that was another recognizable command that flushes the whole configuration. It took us 48hrs with a level XX R&D guy with lots of weird scripts to get everything back.
Lessons learned: if support offers you to take responsibility - GIVE IT! Image may be NSFW.
Clik here to view.
