- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Missing Product Name "Unconfigured HP System"
Server Management - Systems Insight Manager
1753879
Members
7395
Online
108809
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
Go to solution
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
03-29-2007 08:03 PM
03-29-2007 08:03 PM
HP SIM v5.0 SP5 with agents 7.50 running on Microsoft Windows Advanced Server 2003 SP1.
Over the past week or so, we have had about six servers crash for one reason or another. HP SIM correctly changed their respective status at the time, and changed them back when the servers came back on-line.
However, all six of these servers in the CMS console no longer show any description under the "Product Name" column, and when you look at each server's system properties, the "subsystem" description is set to "Unconfigured HP System".
I have checked, checked and double checked everything you can think of (SNMP, community strings, etc. etc.) I have tried deleting and re-discovering all of the servers. I've tried copious amounts of Data Collections, Status Pollings and Identify Systems, but to no avail.
Please can anyone help, before I come to the stark realization that this software is purely and simply "flaky".
Over the past week or so, we have had about six servers crash for one reason or another. HP SIM correctly changed their respective status at the time, and changed them back when the servers came back on-line.
However, all six of these servers in the CMS console no longer show any description under the "Product Name" column, and when you look at each server's system properties, the "subsystem" description is set to "Unconfigured HP System".
I have checked, checked and double checked everything you can think of (SNMP, community strings, etc. etc.) I have tried deleting and re-discovering all of the servers. I've tried copious amounts of Data Collections, Status Pollings and Identify Systems, but to no avail.
Please can anyone help, before I come to the stark realization that this software is purely and simply "flaky".
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2007 02:21 AM
04-03-2007 02:21 AM
Solution
Have you tried restarting the agents and specifically SNMP on the managed nodes and then do a rediscovery?
I have found in the past, although I must admit with Windows 2000, that when the systems have crashed (Windows servers crashing - say it is not true!!!) that the SNMP is left in a funky state. Even though the server is restarted because of the crash, SNMP and hence the agents are still funked up. Restarting SNMP (which automatically restarts the agents) seemed to fix this. I know - I don't get it either; restarting a server should start all services cleanly...
Not sure if this is the case with Win2003.
Nelson
I have found in the past, although I must admit with Windows 2000, that when the systems have crashed (Windows servers crashing - say it is not true!!!) that the SNMP is left in a funky state. Even though the server is restarted because of the crash, SNMP and hence the agents are still funked up. Restarting SNMP (which automatically restarts the agents) seemed to fix this. I know - I don't get it either; restarting a server should start all services cleanly...
Not sure if this is the case with Win2003.
Nelson
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