Server Management - Systems Insight Manager
1752795 Members
6192 Online
108789 Solutions
New Discussion

Re: How to interpret attached CRITICAL SIM alert

 
Terence Ng
Advisor

How to interpret attached CRITICAL SIM alert

I have deployed SIM agent to VMware vSphere 4.0 hosts which are monitored by HP SIM Manager v5.3.

I have received similar following CRITICAL alert some time. What does it mean? How to resolve this kind of CRITICAL alert?

Event Name: System is unreachable
URL: http://HPSIM01.corp.abc.com:280/mxportal/MxContextLaunch.jsp?systems=~TW_VMFS_T1_11- vmapp1069-vmapp1069&tool=System%20Page
Event originator: ~TW_VMFS_T1_11- vmapp1069-vmapp1069
Event Severity: Critical
Event received: 25-May-2010, 16:13:03
Event description: The current system is no longer reachable from the central management server, hardware status polling has marked this system as not responding

TW_VMFS_T1_11 is a LUN from EVA8000 presented to vSphere host.

Thanks.
1 REPLY 1
BPE
Esteemed Contributor

Re: How to interpret attached CRITICAL SIM alert

Select your vSphere Server inside SIM and verify the associations.
You also should see a VM Guest system with your LUN name inside.

If this is the case you have the following situation. During the discovery or Identify of your esx server a list of all the guest vm is collected by WBEM. The active VM's are monitored automatically. If you stop or shutdown such a VM you get the system unreachable message.

You mention that you run SIM V5.3 did you applied all the patches for VM environments?

Verify also with the VSphere people that the os type is correct set for this VM.
There is a problem with Windows 2008 experimental os type because of some naming conventions. This leads to field separation problems in side the SIM code.

You should mention the hole event originator name to the vSphere people and they should find the related VM. The association list after a new identify of the vSphere server should also help.