- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: How to interpret attached CRITICAL SIM alert
Server Management - Systems Insight Manager
1752795
Members
6192
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2010 12:44 AM
05-25-2010 12:44 AM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2010 01:09 PM
05-26-2010 01:09 PM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP