FrostyAtCBM

updated

12 years ago

F

FrostyAtCBM

2 Intern

•

63 Posts

•

3 Points

0

187951

November 3rd, 2011 15:00

Firmware and NVSRAM upgrades on dual-controller MD3200

I have a dual-controller MD3200 (plus a slaved MD1200) which is running firmware v07.70.06.63 and NVSRAM vN26x0-770890-005 and I need to upgrade both the firmware and the NVSRAM to take advantage of some new features.  I am also about to implement the High Performance Tier and another MD1220 tier of storage.

Wondering if anyone has experience of firmware and/or NVSRAM upgrades on the MD3200 dual-controller device?

From reading the upgrade notes, it seems like it should be possible for me to upgrade without having to shut down my VMs, however this strikes me as overly optimistic.  So I intend a planned systems outage, will shut down the VMs, then upgrade and restart all the VMs once the firmware is upgraded and the storage array is visible from my ESXi hosts.

Any thoughts or experiences that anyone can share?  e.g. will I need to physically reboot (power off and on) the storage arrays?  I was hoping to do most of this work from home and would like to avoid having to physically attend on site if I can.

  • JOHNADCO

    2 Intern

    •

    847 Posts

    3013

    1

    Posted November 3rd, 2011 16:00

    I have done it from home... (MD3000i)   Make sure the machine you are remoting into with MDSM on it is not running off the storage.   I made that mistake only once.

    I leave the ESX / ESXi hosts running but shut down the VM's.   The controllers get reset, as in basically powercycled by the updating,  I can't believe any VM would survive through that if left powered on.

  • FrostyAtCBM

    2 Intern

    •

    63 Posts

    •

    3 Points

    3013

    0

    Posted November 3rd, 2011 16:00

    Thanks John, that pretty much confirms my thinking.  I do have a physical server which I use for DR purposes, so I have installed the MD3200 management software on there and will use that one to do the firmware updating.  I also have my laptop which I will leave turned on in the office just in case I need to RDP to it.

  • nrosselli

    7 Posts

    3013

    1

    Posted November 6th, 2011 18:00

    I have upgrsded firmware several times without powering anything down.  As long as you have 2 controllers you are fine

  • dlreid

    3 Posts

    3013

    0

    Posted November 30th, 2011 11:00

    Was just wondering what type of VMs you were running.   I run primarily Linux.   Do you know if the IO all gets switched to the one controller thats not being upgraded, then switches IO to the upgraded controller when it upgrades the second controller?    I'm assuming thats what happens.    The MD3200 owners manual has the following notes regarding upgrading firmware and nvram:

    NOTE: I/O to the array can continue while you are upgrading RAID controller and NVSRAM firmware.

    NOTE: Dell recommends that the firmware and NVSRAM be upgraded during a maintenance period when the array is not being used for I/O.

    NOTE: The RAID enclosure must contain at least two disk drives in order to update the firmware on the controller.

    Kind of confusing as they are saying you can do the upgrade while there is IP activity then say you should do it while there is NO IO.    Maybe thats just to be extra safe?     Still, I was sold the Md3200 with dual controllers so there was redundancy and so i could do upgrades without having to take my servers out of service.   

    I know that during configuration changes (creating virtual disks, mapping them, etc) I will find that some of the preferred IO paths have switched to the other controller without any impact to the OS or apps running on the VMs.   So I guess I'm left with the impression you can do it while IO is active but Dell isn't going to take responsibility if there are issues as they have also said to do it during a maintenance window with no IO.

  • FrostyAtCBM

    2 Intern

    •

    63 Posts

    •

    3 Points

    3013

    0

    Posted November 30th, 2011 13:00

    We run almost exlusively Windows VMs.  Because we were also adding an additional tier of storage we decided in the end to completely shut down, recable, start it up again, then do the firmware upgrade with no servers booted up.  It was all relatively pain free, except for the moment when I tried to upgrade from 07.75 (interim) to 07.80 and discovered that I didn't have the latest MD Storage Manager software installed on one of the physical servers in the computer room.  Fortunately I did have it on a laptop and was able to run the final firmware update form there.

    Because I made a silly mistake in the cabling, we've had plenty of experience in the past week with the dual-controller setup.  I've been pulling out cables and changing them about all while everything is running.  This included physically ejecting controller 1 from the MD3200 and reinserting it, relying on it to auto-failover to controller 0.  All of that seemed to work flawlessly.  Whilst I would probably be more confident than before about doing firmware upgrades on a loaded MD3200 (provided it was dual-controller), I think I would still wimp out and schedule an outage ... just in case ... but that's just me and my paranoia I suppose!

  • dlreid

    3 Posts

    3013

    0

    Posted December 1st, 2011 06:00

    Thanks for your response.   Isn't being a little paranoid a required part of this job??  ;-)  

  • JSA01

    1 Message

    3013

    1

    Posted December 15th, 2014 07:00

    Yes as long as you have dual controllers you can update firmware and NVSRAM without taking anything down, thats the point of the dual controllers.

    Ive completed this plenty of times without issues. The key to updating these is very similar to the Equalogics and one thing you have to do is be patient as it can take a while.

    It may look like its hung or not doing anything but just wait and give it time to finish.