- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HP SIM problem when server rebooted
Server Management - Systems Insight Manager
1753856
Members
6979
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
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
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
тАО09-18-2008 10:41 AM
тАО09-18-2008 10:41 AM
HP SIM problem when server rebooted
I have HP SIM 5.2 running on a RHEL4U4 server. I have various HP Proliant servers running the latest Proliant Support Pack (8.12).
When the systems are initially discovered, all is well. The Product Name field and OS type fields are populated correctly. I can click the "System Management Homepage" link and reach the homepage for the server.
However, when I reboot a server it's entry in HP SIM becomes corrupted. The Product Name reverts to "Linux Server" rather than "HP Proliant DL380 G5". The OS type reverts to "Linux" rather than "Redhat Enterprise Linux 4".
If I click the "System Management Homepage" link I get an error "There is no System Management Homepage for". If I open a new window and type the address for the System Management Homepage in, it comes up as normal, only the link in HP SIM is broken.
If I delete the server from HP SIM and re-run discovery everything works again until the next reboot.
I'm unable to find anything in the logs. Please help!
When the systems are initially discovered, all is well. The Product Name field and OS type fields are populated correctly. I can click the "System Management Homepage" link and reach the homepage for the server.
However, when I reboot a server it's entry in HP SIM becomes corrupted. The Product Name reverts to "Linux Server" rather than "HP Proliant DL380 G5". The OS type reverts to "Linux" rather than "Redhat Enterprise Linux 4".
If I click the "System Management Homepage" link I get an error "There is no System Management Homepage for
If I delete the server from HP SIM and re-run discovery everything works again until the next reboot.
I'm unable to find anything in the logs. Please help!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 09:55 AM
тАО09-25-2008 09:55 AM
Re: HP SIM problem when server rebooted
Bump to the top, anyone with an idea??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 12:28 PM
тАО09-25-2008 12:28 PM
Re: HP SIM problem when server rebooted
Not sure if its the same issue, but the VMware ESX (which uses redhat for the console) there was an issue where an additional firewall hole needed to be opened to allow identification to work correctly.
As well as 2381 and 280 it needed 2301. The behaviour was similar to what you're seeing. It was fixed for VMware with the most recent PSP though.
As well as 2381 and 280 it needed 2301. The behaviour was similar to what you're seeing. It was fixed for VMware with the most recent PSP though.
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