Was asked to cover a colleague on a “simple” storage upgrade on an EMC Clariion AX4-5 array. Add 8 disks, present to a windows host, enable data transfer.

Once Complete the original LUNs would be destroyed and redistributed – simples…

Except the operating code (Flare) on the array was relatively old 505 level. And the disks were relatively new 2TB SATA units. Navisphere Manager showed the drives as “unknown”.

Working backwards by searching for compatibility with the disk part number it was clear that a later release of AX4 operating code (Flare 720) was required.

Not a problem i thought, update the flare code and off we go. Being a belt and braces (a$$ covering) sort of chap i decided to do the update out of hours with Esxi4 hosts and windows server in maintenance mode.

Simplest way for an EMC storage dabbler to achieve this is to follow the instructions provided by EMC from the Upgrade and maintenance page : http://www.emc.com/microsites/clariion-support/ax45-service.htm

This page enables you to create custom documentation based on the task in question for the array type in use.

Tips of note provided in the doc:

• No Faulted (F) or transitioning (T) components in the array
• All servers must be running up to date Powerpath software and drivers
• Windows 2000 servers must be SP4
• Do not power down or reboot during update!
• Non highly available connected servers will be affected by the update as each SP is rebooted in turn.

Next to the Flare update. Weapon of choice is the Unisphere Service Manager application. This installs on Windows and then provides a GUI interface to connect to the existing array SP and perform the upgrade.

The first step involves checking the array for pre-requisite compatibility. This process also downloads any required patches based on the array type (flare, patches, disk firmware) and ensures the array is not faulted or pending software update application.

Next on to the update. Its a really simple process, mostly a next, next job to confirm that the update can go ahead. You will need to select the Flare PBU file from the repository during the upgrade process.

Once the process starts the second SPS will be upgraded and rebooted. At the point that the primary SPS starts the update process you will be kicked out of USM and will need to login in to the second SP.

A good blow by blow graphical blog of the Unisphere update process is available here: http://myitinfrastructure.wordpress.com/tag/unisphere/

Note that express install can only be selected once the pre-requisites task has been performed and the Flare OE copied to the controllers.

Once complete you will need to login to Navisphere manager and commit the software change. Until you do this you will get an error when performing certain operations – for instance LUN creation.

Right click on the array entry, go to the software tab and select the updated element and confirm the update.

Note: There is a lovely “reverse-answer” pop up that appears when you go into Navisphere Manager and select the properties of the array. A java message appears asking if you would like to “continue blocking certain features” and recommends that you say yes. By doing so you will not see the software tab and will soon be throwing things at the monitor in annoyance!

Like the grange hill kids, “just say no” to the continue blocking prompt and all will be fine!

Once enabled the disks can be configured and all is well.