EVA8000 downgrade firmware

[Jon Hudson]

Hi,

I currently have an issue where I have a New (to me) 8000 running firmware version 6100.  However I am currently running command view 6.0.2 and will not see the device, I believe I need to downgrade the firmware to 6000 before I can see it.  Unfortunately I am unable to find this download anywhere, can anyone point me in the right direction of the download.  Software depot only seems to have the latest version.

I understand an upgrade to command view would help but I am unable to do this as I have legacy SAN devices also being managed

Thanks

[Torsten.]

AFAIR you need to uninitialize the EVA in order to downgrade (check manual) - better to use command view 9. Check also the compatibility guide!!!

[Johan Guldmyr]

Hi, can't you install CV on another server?
AFAIR CV 9.4 can be run inside a virtual machine.

[Jon Hudson · Accepted solution]

Thanks for your response, but HP have supplied xcs 6.000 for us to use, however I still have an issue where the command view is unable to see the 8000 are there any HBA settings I need to ensure are set before cv 6 will connect to an 8000?

[Torsten.]

Your controller software and CV version are both inactive (no longer supported).

Consider to use XCS 6240 and CV 9.4.

You need a new license for CV >6.x - ask HP!

[Jon Hudson]

OK, thanks for your assistance.

[Johan Guldmyr]

Maybe they don't have a license.

[KurtG]

XCS 6.100 was supported with cv eva 6.02 at time of release.

However 6.100 did have som serious issues on system with high utilization of provisioned capasity.

I remember that I did some upgrades to 6.110 on cv 6.02 and a couple of weeks later the cv 7 was released.

Point is; Youre fine with xcs 6.000 and 6.110 with a cv 6.02 installation seen from a management view.  Of course there
are many other reasons to implement av higher version of xcs and cv eva. (bugfixes)

KurtG

[Greybeard]

Do both controllers have charged cache batteries, if it's the first time connecting then CV 6 often fails to talk as it is a "new" host and dead cache batteries disable host I/O on the controllers.