XCS10000000, CV9.4 and EVA4400 questions

[TheGord]

Hello,

So, going through all the PDFs and threads before installing XCS1000000 on our EVA4400...

We are at XCS95220000

Our mgmt server has CV9.4

Our drives are all running latest fw

Our FC switches are all running 6.4.1b

MPIO for our Windows based machines attached to the fabric is 4.02

The EVA Management Module/VOCP is running CV9.1/02.02.00.090604/mmp-001.3000-CR03D8 (We don't use it, CV9.4 runs off a remote server)

I see in one doc it says to upgrade the Management Module after upgrading the controllers, is that right? Is there risk/harm in doing it beforehand?

Is the ABM.pkg file all that's neede to update all of the Management Module?

I read that going from XCS9522000 to 10000000 is supported, providing there's no Continuous Replication and a couple of other things, has anyone out there completed this jump yet?

Is there anything else required to enable the Thin Provisioning and large LUN, etc, features?

Thoughts, comments, ideas, are appreciated.

Thanks.

G.

[Johan Guldmyr]

Hey! I would upgrade the mm - management module - as well. There were some issues with it and CV 9.1 so why not get both to the same level. The mm could come in handy if **** hits the fan. In which document did you see that it should be done beforehand? In the UPS - updating product software guide?

Are you updating firmware/drivers on the FC HBAs too?

[TheGord]

Hi there,

So yes, page 33-35 of the EVA UPS (XCS1000000) guide say to do the MM before the upgrade....but I'm pretty sure I saw another doc, say do it post firmware upgrade. Maybe not. Too many PDFs, and they're all changing with the EVA/P6000 rebranding.

Good question on the HBAs.  Our blades have latest and greatest, I'll have to do a quick check on the DLs.

Thanks.

G.

[TheGord]

So all went well. Got the management module and EVA4400 updated. Put the Thin Provisioning license code in CV and all is good.

G.