XCS 5.110 to XCS 6.100 upgrade

[Jeff_Traigle]

Ok. I got the file from the previous post. Performing the upgrade went smoothly. However, after the EVA 6000 came back online and manageable by Command View EVA, it shows all of the disk drives as unmappable and none of the enclosures is listed under Rack 1. I'm wondering if there was supposed to be a cabling change associated with this upgrade that I didn't see mentioned in the sporadic documents I found. (According to HP, it's required going from VCS 3.110 to 4.110 on the EVA 5000s we have, which is why they are required to do those, I guess.) The cables from the enclosures to the loop switch in our other EVA 6000s that are already at 6.110 have whitish connectors. The cables in this one are all black. Part numbers don't match either. Anyone remember back to doing these that can shed some light on this?

[Niels Vejrup Pedersen]

Hello Jeff,

Its quite normal that right after a firmware upgrade the hardware will appear in the unmappable hardware folder.

This happens because the IO modules is still being updated - and after at while all will appear normal.

No cabling change is needed - this was only when going from VCS 3 to 4 (active/passive to active/active)

Regards

[Rob Leadbeater]

Hi,

The firmware upgrade on the EMUs is/was probably still running... If you look at the back of the EVA you'll see the EMUs counting up from 01 to 99 as they load their new code, before going back to the normal shelf position number...

Cheers,

Rob

[Jeff_Traigle]

How long is "a while"? It's been nearly 1.5 hours. The EMUs look normal, displaying the enclosure IDs.

[Jeff_Traigle]

Guess I should also mention this is Command View EVA v9.1 in case that might be part of the issue.

[Niels Vejrup Pedersen]

Hi,

Have you tried doing a Refresh on the EVA ? (mark eva in command view and press refresh)

I've seen that it does not update by it self.

Regards

[Jeff_Traigle]

Yep. Noticed that after sending the previous two replies. Even after the refresh, still shows all the drives as unmappable, however.

[Niels Vejrup Pedersen]

Are the EMU displaying the shelf number now ?

Are LED 3 on the EMU displaying anything ? (1+2 should be green and the third is fault led)

Regards

[Jeff_Traigle]

EMUs are displaying shelf/enclosure number.

No fault light. Heartbeat light is flashing green. Power light is green.

[Niels Vejrup Pedersen]

Thats strange..

Do you see anything usefull in the Controller Events ?

Regards

[Jeff_Traigle]

After the entries stating the EMU updates were completed, I see a few of these:

An HSV200 controller has processed a Storage System Management Interface command with the result of non-success return code.
Corrective action code: 00

The details are in the attachment.

[Rob Leadbeater · Accepted solution]

Hi,

> How long is "a while"? It's been nearly 1.5 hours.

Normally no more than 10-15 minutes on the EVAs I've done...

> Guess I should also mention this is Command View EVA v9.1

It might be... The compatibility matrix here:

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01858971/c01858971.pdf

says 9.1 should work, but the little foot note at the bottom of page 5 makes me wonder:

"HP recommends that you upgrade to XCS 6.2xx if you are using HP Command View EVA 8.0.1 or later."

Cheers,

Rob

[Niels Vejrup Pedersen]

Hello,
Everything with a CAC of 00 means no action should be taken.

As Rob states they recommend going to XCS 6.2xx. But your step to XCS 6.100 was required before going there.

If you got a support contract on the system i would recommend logging a call with HP. Just to check if its safe to upgrade before all the stuff moves from unmappable hardware folder.

Regards

[Niels Vejrup Pedersen]

Hello,

Did you find a solutions ?

Regards

[Jeff_Traigle]

I went ahead and did a code load on the disks this morning. They were all incredibly old firmware revisions also. After they were updated, the disk enclosures appeared and no disks are unmappable.