Re: Command View EVA stopped working

Hi,

My EVA Management appliance serves out the following webpage.

https://localhost:2381/command_view_eva

This has stopped working and I have rebooted the management appliance several times.

Any help would be apprecriated as to why this has stopped .

Many thanks,

Paul

24 REPLIES 24

1. Update the CV version
2. Restart hp command view eva service

post the update..

If you are keen to win, you should be willing to lose.

Not sure what version I have. Can you post a link to the latest version available ?

Cannot understand why it would stop working and will not start up on a reboot!

Regards,

Paul

To find your current version of CV
Try -

http:///osm/tools/support/support.asp

CV patches and updates are at -
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?lang=en&cc=us&taskId=135&prodTypeId=12169&prodSeriesId=471497

If you are keen to win, you should be willing to lose.

Also I cannot connect to the EVA using SSSU

SSSU Sel Manager ipaddress user=administrator pass=password

SSSU> Sho system
ERROR: EMClient APITNG error
EMCLIENTAPISOCKET_CONNECT_ERROR
Cannot establish socket connection with the server.

This error tends to suggest something else at fault!

Paul

EVA make?
Firmware?
Are hosts able to see the EVA?
Is the switch able to see EVA and SMA?
I hope you are using SSSU version 6 -

SSSU 6.O is at

http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodName
Id=3185481〈=en&cc=us&taskId=135&prodTypeId=12169&prodSeriesId=471497

If you are keen to win, you should be willing to lose.

SSSU uses TCP/IP to talk to running CommandView. If no CommandView, then no SSSU.

Are you using - SMA or SMS??

If you are keen to win, you should be willing to lose.

SMA.

This has been working fine until this week. No other changes have been made on the SMA!.

Regards,

Paul

1. Do Event logs on the SMA inidcate towards any failure?
2. CV version?
3. Is the SMA managing more than one EVA?
4. Have updates been of any use?

If you are keen to win, you should be willing to lose.

Which version of XCS are you using?
Command View v.3.x will show similar error connecting to XCS v.5.03x and CV v.4.x when you try to connect to XCS v.5.1xx.

Paul,

Has anything changed on the SMA. Have you allow MS patches, JRE or SmartStart7.2 to be install? All of thes elements can have the effect you discribe.

If your host still see there LUNS the problem is on the SMA.

Hi Paul,

Can you terminal service into your SMA then run the SSSU commands locally?

Is this SMA able to resolve over the network? Can you run full, short name resolution against this box?

Has anyone outside of you made any changes to your network?

I didn't see select cell in you sssu command.

As Adam stated, no command view, no sssu.

Paul,

Welcome to the club, we're having that same problem. I started a thead on this as well:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1068884

I then got Telephone Support involved. They had Field Service come in and reinstall Command View EVA with no luck.

The plan now is on this Sunday morning to shut down all servers using our EVA3000 (Ouch!), shut down both HSV100 disk controllers, power both off and then back on. For some reason they think this will fix the problem, they're 90% sure.

I'll keep you informed what happens.

Vic

There are 10 kinds of people, one that understands binary and one that doesn't.

The proposed fix from HP is to rebuild the SMA from scratch!.

I have not done this yet. However I have reinstalled Command View and Java RT but to no effect. Also installed Command View on a different server attached to the SAN but it cannot see any EVA when discovering!.

Any ideas?

Regards,

Paul

Paul,

FYI: On Sunday we did shut down everything connected to the EVA3000 so we could shut down and power off both HSV100 disk controllers at the same time. After reboot the Command View EVA started working again. They believe there was a 'hung process' in the HSV100s whatever that means.

Vic

There are 10 kinds of people, one that understands binary and one that doesn't.

Victor,

thanks for the update. I will be performing the same attempted fix this weekend and I will post here the result.

Interesting to note that HP have not suggested this but to just rebuild the SMA!

Regards,

Paul

We stopped and shutoff power to the EVA8000 over the weekend and restarted and the EVA Command view started working again.

However this has stopped working again. I get the following message on Command View

"A command is in progress on this management server agent. You must wait for the outstanding command to complete before performing another action".

We did have some work going on our DNS Server at the weekend and I left the Command View window up. When I came in this morning the window was still up but the hourglass was running, tried to stop so killed this and tried again and received this message.

Any ideas? Would the stop and start of DNS affect communications?

Regards,
Paul

Paul,

Did you power off both controllers at the same time? It's important that both be turned off. If you did one and then the other, the problem moves to the controller that's still on.

What version of Command View EVA are you running? Service upgraded ours to V6.0. Maybe do that before reinstalling the whole thing.

Vic

There are 10 kinds of people, one that understands binary and one that doesn't.

We had an issue where CV EVA would stop responding, but it looks to be slightly different from the descriptions above.
I could access CV EVA, but all attempts to then access the EVA detail would fail.
Restarting both Controllers would fix the problem, and unlike other posters I did not need to close both down.
I restarted the Master Controller and then after it had restarted and the second became the Master, restarted that one.
As a note I've moved to CV EVA 6 as it seems more stable here, especially as regards SMI-S connectivity back to HPSIM.

Our CommandView has stopped working again!.
I have shutdown and powered off the entire EVA and restarted and still get nothing! on Command View.

I have installed Command View on another server connected to the EVA and get the following on a path test

System Node WWN Model Version Role OS SCSI Device
Port Target LUN Ping (Âµsec) Status
5000-1FE1-5008-B040 HSV210 5000 Unknown Scsi4
1 0 0 219 Unknown
5000-1FE1-5008-B040 HSV210 5000 Unknown Scsi4
1 2 0 162 Unknown
5000-1FE1-5008-B040 HSV210 5000 Unknown Scsi4
1 1 0 220 Unknown
5000-1FE1-5008-B040 HSV210 5000 Unknown Scsi4
1 3 0 184 Busy

Any ideas? help please.

I have a call that has been elevated to EVA engineering for sometime now and they are saying thaey have had no other customers that have experienced this. However there has been at least another 1 who has contributed on this thread.

Paul

I too have this same issue. I HATE all HP tools. They are all CRAP CRAP CRAP. Monkeys programming this CRAP on the backend.

FIX YOUR ISSUES HP. RESTARTING PRODUCTION EVAs IS NOT A SOLUTION. Suggesting that you need to shut two controllers down at the same time is ridiculous. WHY DON'T YOU UNDERSTAND THIS.

Everyone always asks in the most polite way 'why can't we do this' and 'what can't we do that'. SCREW THAT. We pay big bucks so you chimps get this crap right.

SO GET IT RIGHT AND FIX THIS #$%%# ISSUE.

Have a customer that got this after the Windows patches last week. The same on 2 different Management servers (not SMA). He's running V5 of command view.

Apologies for not getting back sooner. The issue was resolved by upgraded the firmware on the HSV210 controllers to V6 (patched). Also rebuilt Pc and installed Command View 6.
This fixed the problem.
Regards,

Paul

That's not what I call a solution...