topic Re: EVA 4400 - initial setup, problem controllers in HPE EVA Storage

EVA 4400 - initial setup, problem controllers

Greg Beifuss — Thu, 05 Mar 2009 18:18:11 GMT

My company recently got an EVA 4400 and I'm doing the initial setup. I've connected via WOCP and am having a terrible time figuring out what to do next. My System and both Controllers (1 & 2) are showing as 'unknown'. When I check the status of the controllers, they show as failed. I thought maybe the XCS and management module firmware version were out of synch, but I can't update the management module due to errors ("command execution failed. error: cannot access storage system. communications error") and I can't even determine the XCS version (blank fields). I can't set the WWN either, due to the same communications error.

Is this something I need to involve HP on (both controllers are defective out of the box?) or have I missed something? HP has already replaced the management module as the webserver component was crashing after 10 seconds (although the network connection wasn't lost).

Muchly appreciated,
Greg

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Thu, 05 Mar 2009 19:16:53 GMT

You probably got an EVA with mixed firmware versions. Check this thread:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1307730

Management module firmware is old, version 0001.0000, and the controllers probably have XCS 09004000 or 09006000.

Update it to the latest 0001.1000

http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=CommandViewEVA

Select CommandView v8.1 ABM ZIP format (T5494-10006.zip)

Also, you're not trapped by this, install Command View 8.02 on a server and initialize the EVA from there.

Re: EVA 4400 - initial setup, problem controllers

Uwe Zessin — Thu, 05 Mar 2009 19:17:06 GMT

It looks like the controller firmware (XCS) version and the management module (WOCP) version do not match - the internal communications protocol has been changed last year in October.

Maybe somebody as a compatibility table with the XCS revision and the WOCP revisions.

Unfortunately, the documented revision numbers and what the module reports are different (I have missed the chance to build such a table, but would like to see a complete one -
vcespon, do you have one?).

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Thu, 05 Mar 2009 19:32:43 GMT

0001.0000 = 1.00.00.080211
0001.0020 = 1.00.00.080916
0001.1000 = ????

Someone that has the latest firmware can check?

Re: EVA 4400 - initial setup, problem controllers

John Abbott_2 — Fri, 06 Mar 2009 11:06:11 GMT

Management firmware: mmp-0001.1000-000117R =
XCS version: 09006000
XCS build: CR1276lep

Re: EVA 4400 - initial setup, problem controllers

Bernhard Mueller — Fri, 06 Mar 2009 11:22:57 GMT

Greg,

is it possible, you have not yet connected the front end ports on the EVA controllers to a switch?

Make sure there is a link and try again.

Regards,
Bernhard

Re: EVA 4400 - initial setup, problem controllers

Greg Beifuss — Fri, 06 Mar 2009 15:21:56 GMT

"Also, you're not trapped by this, install Command View 8.02 on a server and initialize the EVA from there."

Can I get some info on this? I assume that I need to take a server and physically connect it to the SAN before installing CV for management. That's going to be an issue for us because it's our first SAN component & we were going to hook up some blades to it - right now I have no local storage on Blades to get started, nor do I have any HBA for a physical server connection to the SAN.

I still see us being stuck but I'm hopeful for suggestions to get me over this EVA hump.

Thanks!
Greg

Re: EVA 4400 - initial setup, problem controllers

Greybeard — Fri, 06 Mar 2009 15:29:10 GMT

Hi Greg, you don't need a server. anything with a FC HBA that you can install Command View onto will get it initialised, I used an old PC to try out CV 8 and it connected to my EVA 5k just fine.

Re: EVA 4400 - initial setup, problem controllers

Greg Beifuss — Fri, 06 Mar 2009 15:52:40 GMT

Again, I have no HBA on hand.
Anyone know if HP'll fix this for me if I open a ticket? Or is this my problem now?

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Fri, 06 Mar 2009 16:39:49 GMT

Have you updated the management module firmware to 0001.1000?

Currently you have 0001.0000 firmware, and if you do not have a Windows server with local disks and an HBA to install Command View on it, how did you plan to configure anything on that EVA?

You NEED Command View, either CV 8.1 on the management module or CV 8.02 on a Windows server.

Re: EVA 4400 - initial setup, problem controllers

Greg Beifuss — Fri, 06 Mar 2009 20:49:18 GMT

Installing management module firmware 1.00.00.080916 has let me see the controllers. Thanks!

Greg

Re: EVA 4400 - initial setup, problem controllers

Greg Beifuss — Fri, 06 Mar 2009 20:50:25 GMT

Installing management module firmware 1.00.00.080916 has let me see the controllers. Thanks!

Greg

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Fri, 06 Mar 2009 21:31:24 GMT

You still need a server with Command View 8.02, that firmware version does not have CV 8.1 embedded.

Re: EVA 4400 - initial setup, problem controllers

CLEB — Mon, 23 Mar 2009 15:00:46 GMT

vcespoon

I have the latest firmware, how do I check the versions?

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Mon, 23 Mar 2009 17:54:29 GMT

Latest versions are 09501000 for the EVA controllers (check in Command View), and 0001.2000 for the management module (check in the WOCP).

Re: EVA 4400 - initial setup, problem controllers

Víctor Cespón — Wed, 29 Jul 2009 11:28:05 GMT

Just to update the table:

0001.3000 (mmp.0001.3000) (Command View 9.01.00)
0001.2010 (mmp.0001.2010) (Command View 9.00.01)
0001.2000 (mmp.0001.2000) (Command View 9.00.00)
0001.1000 (mmp.0001.1000) (Command View 8.01.00)
0001.0020 (1.00.00.080916)
0001.0000 (1.00.00.080211)