Disk Enclosures
1753399 Members
7129 Online
108792 Solutions
New Discussion юеВ

CommandView controller event log.

 
SOLVED
Go to solution
john_347
Regular Advisor

CommandView controller event log.

Hi all,

Has anyone come across this error in the EVA controller event log.

13:06:55:995
31-Jan-2011
Error Getting Name

The system seems to be able to get the Controller A name. The EVA's all seem to be working fine. Any ideas before I get HP support involved.

regards

JC
6 REPLIES 6
Johan Guldmyr
Honored Contributor

Re: CommandView controller event log.

Hey, if that is in the eva controller event log, there should be an event id as well, what is that? Can you please post the whole thing maybe?

What kind of EVA and which firmware(xcs or vcs version) and Command View version are you running?
Sivaramakrishna_1
Honored Contributor
Solution

Re: CommandView controller event log.

Hi,

I hope you are running with Command View EVA 9.3 version.

There is some know issue with the version, it will report "Error Getting Name" instead of Controller A/B.

This is expected to be corrected in next release of CV.

This will not cause any issue to the function of EVA. How ever you can follow below workaround to resolve this.

1. Shutdown of the controller which is working correctly.
2. Restart Command View EVA service and then Discover the EVA with single controller.
3. Verify Event logs if the affected controller is reporting its name correctly.
4. Power-up other controller.
5. Verify both the controllers are reporting correctly in the event logs.
Sudhakar Subramaniam
Trusted Contributor

Re: CommandView controller event log.

Can you please give the event id
john_347
Regular Advisor

Re: CommandView controller event log.

This is the message we get in the controller event log, there are no error codes.

07:04:37:549
17-Feb-2011
Error Getting Name

thx
john_347
Regular Advisor

Re: CommandView controller event log.

sorry guys,,,

EVA84000 XCS 09522000 CV 9.3

regards

Johan Guldmyr
Honored Contributor

Re: CommandView controller event log.

OK, see the fix above by Sivarama. According to that this is a cosmetical problem in CV 9.3.