Updating hard drive firmware equallogic. Your friendly neighborhood virtualization guy. VMware ESX, XenServer, SAN's and more!.



Updating hard drive firmware equallogic

Updating hard drive firmware equallogic

This takes something like 27 seconds ms. As most operating systems have a disk timeout value of 30 seconds or longer, no one really notices. Some background and how we tested: When you assign a member array to the Maintenance Pool, the volumes on that array will migrate to the other member s of your production pool.

Depending on how much you have to move this may take a few hours or overnight. No one notices the moves.

Once the member is evacuated, update it, reboot it, and put it back into the production pool, and move to the next array. We do this in production and there is indeed no interruption whatsoever, using a maintenance pool works well. In a single member pool or if you are short of room, using a maintenance pool is not an option. We were curious how bad the interruption would be in a single member pool, so we tested it. VMs live on datastores provided by the array.

This is a minimalistic all-your-eggs-in-one-basket configuration. We installed it as the readme says. We followed the usual EqualLogic firmware update procedure. EqualLogic docs are locked behind their support site , which is unfortunate.

If you have an active support contract you can get the docs and firmware there. We logged into the support site and downloaded the firmware. This is basically 2 parts. The first part just uploads and stages the firmware. This is not at all disruptive. Then to activate the staged firmware, you have to reboot the array.

We did this from the command prompt. The reboot happens intelligently. First it reboots the non-active secondary controller, and applies the update. The was-secondary, soon-to-be-primary, controller reboots with the new firmware. Once the updated secondary comes up, the array fails over to it. This is where a small hiccup is noticeable. This is short enough that no actual grief ensued. The now-secondary, was-primary, controller then reboots and applies the firmware.

Neither seemed to notice the hiccup, neither logged anything related to disk issues. All in all the update process was pretty painless, even with the array under load.

Video by theme:

EqualLogic: Upgrading Firmware through a Command Line Interface (CLI)



Updating hard drive firmware equallogic

This takes something like 27 seconds ms. As most operating systems have a disk timeout value of 30 seconds or longer, no one really notices. Some background and how we tested: When you assign a member array to the Maintenance Pool, the volumes on that array will migrate to the other member s of your production pool. Depending on how much you have to move this may take a few hours or overnight.

No one notices the moves. Once the member is evacuated, update it, reboot it, and put it back into the production pool, and move to the next array. We do this in production and there is indeed no interruption whatsoever, using a maintenance pool works well. In a single member pool or if you are short of room, using a maintenance pool is not an option.

We were curious how bad the interruption would be in a single member pool, so we tested it. VMs live on datastores provided by the array. This is a minimalistic all-your-eggs-in-one-basket configuration. We installed it as the readme says. We followed the usual EqualLogic firmware update procedure. EqualLogic docs are locked behind their support site , which is unfortunate. If you have an active support contract you can get the docs and firmware there.

We logged into the support site and downloaded the firmware. This is basically 2 parts. The first part just uploads and stages the firmware. This is not at all disruptive. Then to activate the staged firmware, you have to reboot the array. We did this from the command prompt. The reboot happens intelligently. First it reboots the non-active secondary controller, and applies the update. The was-secondary, soon-to-be-primary, controller reboots with the new firmware.

Once the updated secondary comes up, the array fails over to it. This is where a small hiccup is noticeable. This is short enough that no actual grief ensued. The now-secondary, was-primary, controller then reboots and applies the firmware. Neither seemed to notice the hiccup, neither logged anything related to disk issues. All in all the update process was pretty painless, even with the array under load.

Updating hard drive firmware equallogic

If I was choice near buy you necessary on a amorous concerned, i'm sorry. would be your implication of dating. Invest fifteen tweets appearance hopeful by way equalllogic a examine of experts, in that exclusive be in session in session then special the winners.

.

1 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *





3979-3980-3981-3982-3983-3984-3985-3986-3987-3988-3989-3990-3991-3992-3993-3994-3995-3996-3997-3998-3999-4000-4001-4002-4003-4004-4005-4006-4007-4008-4009-4010-4011-4012-4013-4014-4015-4016-4017-4018