New EVA4400 problem

 
Vladimir Fabecic
Honored Contributor

New EVA4400 problem

Hello
I am having problem with new EVA4400. Whatever I try to do, I get "Command execution failed. Error: Status code: 83". Controllers are in "unknown" state.
Controllers are connected to FC switch. Ports on FC switch are in "in sysnc" state, no link.
Looks like a firmware michmatch to me, but is that so?
Management module firmware is mmp-0001.4000-CR05B2.
Should management module firmware be downgraded or what?
Some screenshots are attached.
In vino veritas, in VMS cluster
8 REPLIES 8
Torsten.
Acclaimed Contributor

Re: New EVA4400 problem

Did you already try to set the WWN (see screenshot 2)?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vladimir Fabecic
Honored Contributor

Re: New EVA4400 problem

Screenshot 1 is what happen when I try to set wwid.
In vino veritas, in VMS cluster
Torsten.
Acclaimed Contributor

Re: New EVA4400 problem

I assume it did not work ever. Looks like the Management module cannot talk to the controllers.

I would start over. Power down the array, re-seat the module, switch on the disk enclosures, wait a while, switch on the controllers.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vladimir Fabecic
Honored Contributor

Re: New EVA4400 problem

Torsten,
I allready did what you said, but did not help.
Yes, looks like the Management module can not talk to the controllers, but why?
Firmware michmatch problem or what?
In vino veritas, in VMS cluster
Torsten.
Acclaimed Contributor

Re: New EVA4400 problem

I don't think it is an firmware issue, because the firmware is almost current. Maybe the module is bad? Consider to contact HP support.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Johan Guldmyr
Honored Contributor

Re: New EVA4400 problem

Hi, I have seen this once or twice caused by the back-end cabling not being done correctly.

Is it?

You can see in the installation guide how to cable it.

I have also seen this when CV was upgraded by the management module was not. Might work with downgrading..

The management module firmware is stored on the Command View CDs.
Vladimir Fabecic
Honored Contributor

Re: New EVA4400 problem

Hello Johan
Cabling was done OK (it looked like).
I upgreade firmware (was same problem after upgrade).
Then I turned off the storage and reseated everything (for third time, this time even cables and disks).
After that storage worked OK.
So maybe it really was cabling problem (i.e. contact problem).
Nice to know you had simular problem because of cabling.
In vino veritas, in VMS cluster
Johan Guldmyr
Honored Contributor

Re: New EVA4400 problem

Glad you got it back and working =)