Slow response from CommandView

[Tim Chilton]

I've noticed that occasionally, when I click on an object in CommandView it takes a really long time for the web page to respond. Sometimes up to 5 minutes. I know that the process on the array has a very low priority on the controller, but this seems a little much. Does anyone Have any ideas? I have EVA8100 running v6220 code and CommandView 9.2.

[AnthonySN]

what is the java version you have on the sms

[Tim Chilton]

The version is the most up-to-date: 1.6.0_20.

[Marcus Schack]

What specs are on the server that is runnign CV? How much memory? CPU? Is it running anything else? Speed of HBAs?

[susanta_dutta]

In some instances CV may respond slow, specially if your Array is highly busy with Host I/O or CV is managing many Arrays

Regards
Susanta

[DogBytes]

Since it's an occasional slow down, is it possible some scheduled tasks are taking over? For example, creating snapclones or running some custom sssu scripts?

[Tim Chilton]

The server itself should be more than adequate: DL360 G5 with dual 2GHz x86 cpu's, 4GB of RAM, and dual 4GB HBA's running W2K3 Standard. The only other thing running on the machine is SIM and that's just for call-home capability. The SMS only manages one array, and the SIM implementation is just for the array, two switches, and two servers. We do have some mirror clones running, but they only go through a scripted fracture/synchronization process in the early morning before I arrive.

[Marcus Schack]

Tom, have you verified your zoning? Have you checked that the switch ports that your server is plugged into at set at the proper speed? I know this seems to be basic stuff but we need to start some where. Has it always run slowly? When was the last time that the O/S was rebuilt?

[Tim Chilton]

The FC ports are properly zoned and both the switch port and HBA are hard set to 4Gbps. It doesn't always run slowly, just when I need to get something done in a rush. ;-) The server itself was built just over a year ago and I haven't been able to see any kind of cause/effect for the time. It's just that sometimes the page will take a good 2-3 minutes to refresh after each mouse clock.

[DogBytes]

Have you run EVAperf lately to get an idea how the EVA itself is performing?

[Tim Chilton]

That was one of the first things that I did. The array itself is running at about 20% of its capability across all categories of evaperf. The only times it gets higher than that is during the fracture/resynch process that happens at night. Even then, it barely breaks a sweat.

[Marcus Schack]

Ok.... how about checking the Task Manager on the SMS and see if there is anything else running that is taking a tonne of time? And just to verify, latest drivers for HBA and Java?

[DogBytes]

Quite the mystery.
Do you run CV EVA from your desktop or directly from the sms using localhost? (or possibly both). I'm just wondering if you've noticed any difference that might point to a network issue.

[Marcus Schack]

Are you running Storage Essentials at all? I also found other threads in here that might com in handy.

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

Uwe suggested something that might help.

[Marcus Schack]

And here is another that might help...

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

[Kurt Gunter · Accepted solution]

I was told by a technician this week that if any of the EVAs is doing something or in trouble (in other words, any time you need fast access to it) Command View will be busy dealing with the EVA output and will slow down substantially.

For example when reconstructing a RAID array, or last week when I had a loop switch fail, it was often 2-3 minutes between a click and a display. Again, HP said this is "normal".

I've had EULAs with "insert text here" in full-release versions. We STILL see that the MPIO DSM is packaged using "demo" software. And Command View is... well, not great even in its 9th version, as you can see.

I forsee a move to other vendors in our company because we're about fed up at this point.

[Tim Chilton]

Thanks, all!