Problems with an MSA1000 SAN

G

Gambit

Gawd
Joined
Aug 26, 2002
Messages
764
I think this is a long shot that someone will have an idea on how to fix this, but I figure it can't hurt to ask.

At work we have an HP MSA1000 SAN, running two separate arrays one for Exchange, one for our ESX hosts. On Friday, we got 4 new drives in to expand the capacity of the arrays. Upon plugging in the drives, the SAN halted with an error code of fc03h. At this point, everything stopped working (no drives for data). So, we rebooted the SAN ... same thing. After removing those 4 drives, the SAN booted properly... kind of. Exchange was able to see it's array and go on delivering e-mail, but the ESX hosts cannot see their array, so no VM machines can actually run.

After looking online, I found an HP article that says "Manufacturing tests have uncovered an issue where the HP StorageWorks MSA1500 and MSA1510i with dual controllers experience a lockup. Further testing has shown that a very limited number of controllers will experience this lockup condition, which is identified on the LCD display by the lockup codes F031h, F101h, F112h, F01ch, or FC03h. Updated controllers are available to address this issue."

I'm *hoping* that we just need new controllers / firmware for the MSA and things will start working. Anyone have any experience with this at all?
 
If the firmware of the SAN does not have a firmware upgrade tool or function, you will probably have to do this through CLI using Putty or PuttyTel, and possibly have a public FTP site/server from which to upload the firmware package. I know there is an HP NIC firmware upgrade tool, but I've only used it with printer NICs, I'm not sure if it would work properly with your SAN, so I would try accessing the firmware first and go from there.
 
maybe try an HP forum, this place tends to be home users and enthusiasts.
 
odditory said:
maybe try an HP forum, this place tends to be home users and enthusiasts.
Click to expand...

Yeah, but I also know some of you guys aren't just the type of guys who throw a few drive in a cheap case and call it a day too. I figure we will have to contact HP and see what they say, but until then, I didn't see any harm is seeing if anyone had run into something like this before.
 
You must log in or register to reply here.
Back
Top