EVA4400 multiple errors

[Alexis Novik]

Hi, guys!

I have new EVA4400 with 2 problems.

1-st onboard WOCP can't connect to Cotroller 1 Management port.
2-nd i can't manage EVA via CV EVA.

I made fresh install W2K3 x86 SERVER. Installed Proliant Support Pack, MPIO, EVA SmartStart 2.1.

I can see previously initialized EVA when i push "discover button. But it said that EVA doing something that prevents managing system.

EVA connected to single Blade Switch with 2 connected servers. I've connected Contr.1 FP1 and Contr.2 FP1 ports to Blade switch and made zones which consists of 2 EVA ports and 1 Blade FC port.

[Steven Clementi]

I think you might be seeing the warning you get when yo uchange management servers.

You said you installed a new server running command view. When ever you try to manage an EVA from a different server than the server that previously managed it, you will get a warning with a couple of buttons. You need to "take control" of the EVA in order to manage it.

Can you post a screenshot?


Steven

[Alexis Novik]

Hi!

No. I know what are you talking about. It doesn't offer me to take a control. The message says, that the system is busy with some task, which doesn't allow me to manage the array at the moment.

But i've tried to shutdown everything for 2 days. Power it on and see this message again.

[Alexis Novik]

anyone?

[Steven Clementi · Accepted solution]

Do you happen to know what version of XCS the EVA is running?

I've encountered several weird behavioral characteristics with older firmwares similar to what you are experiencing.

You should be able to attach to the Management Module (WOCP) to find the XCS version.


Steven

[Alexis Novik]

XCS Version is 09003000
WOCP is 1.00.00.080211

i've attached screenshots.

[Dileep..]

i will suggest to reboot master controller first and do a discover again.if still issue persists reboot the other controller as well.

Management card communication issue needs to be consulted with HP.

[Alexis Novik]

Thanks, Deleep
But i can't reboot Controller 1 because of this issue with current management card FW issue. (Controller Link failure)
I've tried to interchange controllers. But no luck...

I also have another perfectly working EVA 4400. how can i update controllers from failed one on working one?

[Alexis Novik]

Also tried to update firmware and uninitialize eva using SSSU and Management card.
No results..

SSSU reporting about delay and cancel operation. WOCP reporting that system already uninitialized. But when i try to enter WWN it reports that system already initialized.

Weird situation... It never happened with hundred of eve x100 i've installed before.

[Dileep..]

if you have another EVA4400, then try swapping the management card. this will help isolate the issue . after this if its work you can go with master controller reboot.

[Uwe Zessin]

According to "untitled3.jpg", the HSV controllers do not have a WWN set.

- Press the "Set WWN" button and enter the WWN/checksum.

- Then reboot the EVA management server. Go to the Windows device manager and make sure there are all 4 controller devices. If not, check your zoning.

- Try to discover the EVA from Command View - both controllers should be there.

- From there you _should_ be able to initialize the EVA, even if the WOCP has internal communications problems.

- If the EVA has been initialized and the WOCP cannot talk to controller 1, you might want to reboot it once so that #2 becomes the master controller.

- Set up a non-default IP address on the WOCP, but remember not to use the 10.*.*.* range.

- Do a XCS firmware upgrade on the EVA - the WOCP will no longer be able to talk with any controller, but that is OK.

- Do a WOCP firmware upgrade. Make sure you follow the instructions exactly and give it enough time to recover.

- That should fix the whole system.

[Alexis Novik]

>- Press the "Set WWN" button and enter the >WWN/checksum.
When i try to Set WWN it said "System already initialized."

>- Then reboot the EVA management server. Go >to the Windows device manager and make sure >there are all 4 controller devices. If not, >check your zoning.
All 4 devices is in there. Zoning is correct.

>- If the EVA has been initialized and the >WOCP cannot talk to controller 1, you might >want to reboot it once so that #2 becomes >the master controller.
I've tried to reboot Controller 2 (active)
But first Controller doesn't gain control :(

>- Set up a non-default IP address on the >WOCP, but remember not to use the 10.*.*.* >range.
Also tried to do this. Changed address, it became unreachable. New IP doesn't ping. Computer IP changed also. It is became reachable only when i reset it.

But thanks will try to start from the begining.

[Steven Clementi]

If command View is not "managing" the EVA, SSSU is not going to be helpful.

Have you opened up a service ticket with HP support yet?

My EVA4400 with 09003000 had a problem where CV would not even load up after the 4400 was online for a short while.

I had to manually shut it down and do a cold boot. Immeditely after, CV was working so I updated the firmware quickly and have not had a problem since.

Make sure you are at CV 8.0.2.


Steven

[Alexis Novik]

Thanks, Steven to mention about 8.0.2!

I've started EVA for 1 time. And after working overnight i started CV in the morning. It stops responding to managament, but presented luns still accesible.
Will try to update CV.

Thanks again

[Uwe Zessin]

> SSSU is not going to be helpful.

"set system NAME manage" allows you do assume management from within SSSU.


I don't know if this is related, but I have seen a few times that the tree of a newly initialized EVA could not be opened by pressing the "+" (at least for some time - I have not looked at it into details). It was necessary to press the [Discover] button.

[Alexis Novik]

Hi again!

>set system EVA manage
After this command in SSSU now it asked me to enter storage system password from OCP.
Tried to set password from WOCP and then in CV.
WOCP password set, CV reported about password mismatch. (Seems to be BUG)

Is there any posibility to _downgrade_ WOCP FW vewrsion? Didn't find any FWs but v0001.0020.

P.S.
And i can't open support ticket because of lack of service personel in my country.
I was in HP support few years ago, now i am PreSale engeneer. So i know.. The only possibility is replace some parts. But can't diagnose which one to replace.

[Uwe Zessin]

> WOCP password set

I do't have access to a 4400 right now to verify it, but my understanding is that there are multiple passwords:

- 'Windows user/password' to talk to CV-EVA instance from the browser, SSSU and RSM

- WOCP password to talk to the module from the browser

- 'storage system password' used to authenticate a CV-EVA instance against an EVA system. Last time I checked, you could not do firmware upgrades with a 'storage system password' set.

[Alexis Novik]

On Eva4100 there was password on OCP
Without entering that password you won't be able to access CV or SSSU.
On 4400 this password is on WOCP. (not control panel password or windows password)

[Alexis Novik]

what about WOCP FW rollback?
Any chance to obtain previous revision FW?

[Phillip Thayer]

I had a problem similar to this and the support person had me connect a MSA type serial cable to the maintenance port of the controller. Once you are connected to the maintenance port you can power cycle the controller and see if there is a problem with the controller. It will show you the controller boot POST messages and if there is a problem it will display an error message. Then you would need to replace that controller. You can try this on each controller alternately and see what comes up. When I was having the problem with the EVA4400 it turned out that they needed to replace the entire controller shelf backplane to get it working again.

Phil

[Rob Leadbeater]

Hi Alexis,

> And i can't open support ticket because of
> lack of service personel in my country.

I don't see why that should stop you opening a support ticket.

Diagnosis of faults is rarely done by someone in the same country anymore. They might spot something that allows you to get things fixed without needing someone on site.

Cheers,

Rob

[Alexis Novik]

Thanks all of you guys for help!

Problem solved replacing Management Controller module from working EVA4400. I've updated XCS to latest version, then updated WOCP FW.

Now everything working fine. One drive failed during initialization process. But i have spare.