HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HW Status stays critical
Server Management - Systems Insight Manager
1833767
Members
1949
Online
110063
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
Forums
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
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
01-23-2004 12:12 AM
01-23-2004 12:12 AM
HW Status stays critical
I recently installed Insight Manager 7 SP2.
On a lot of new system the HW status stays on critical, even after a Device status change to Normal.
On a lot of new system the HW status stays on critical, even after a Device status change to Normal.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2004 12:39 AM
01-23-2004 12:39 AM
Re: HW Status stays critical
Sounds like a community string settings issue. Make sure that you have the correct security community strings setup on each server. To do this you need to go to the SNMP service, under the security tab. You should have a write community string there and this string should match the default one configured in IM7 sp2. To find out if you have a default string configured in IM7 sp2, log on to the IM7 web console then go to Settings -> Server -> Protocols. Under SNMP Settings, make sure the "enable SNMP" checkbox is checked and you specify a default community string. This string needs to be the same as the ones you have configured on your client servers under the SNMP service's security tab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2004 01:38 AM
01-23-2004 01:38 AM
Re: HW Status stays critical
I changed the setting, runned the snmp status polling for servers task and the daily device indentification task; but the status didn't changee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2004 01:43 AM
01-23-2004 01:43 AM
Re: HW Status stays critical
The otehr thing you need to check is the Integrated management Log. log on to the web console of the affected client http://servername:2301
check to see if there are any Failed or degraded items outstanding. if there are, just clear the iml log by acknowledging the errors as repaired. you can also login locally on the client server via terminal service and use the windows gui to clear out or repair the outstanding messages in the IML log.
check to see if there are any Failed or degraded items outstanding. if there are, just clear the iml log by acknowledging the errors as repaired. you can also login locally on the client server via terminal service and use the windows gui to clear out or repair the outstanding messages in the IML log.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP