HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- SIM5 can not detect ILO in 380 G4
Server Management - Systems Insight Manager
1829117
Members
2121
Online
109986
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
03-20-2006 12:17 AM
03-20-2006 12:17 AM
SIM5 can not detect ILO in 380 G4
Hello All
I have a problem with our newly installed SIM5, SP4 installation. We have recently installed it and we are still having a active 4.2 running. on another server. We have a ILO board in a 380G4 that we try to discover manually in SIM5 but we do not succeed. SIM reports it as being unknown and not reachable. On the 4.2 we have it discovered and also reporting it as being healthy.
I have been trying to investigate the security settings for the ILO but I can not see what is wrong. How do we get SIM5 to detect the ILO board? Is there some security setting that I miss? or a certificate?
Thank you in advance.
Best regards
Tommy Frandsen
I have a problem with our newly installed SIM5, SP4 installation. We have recently installed it and we are still having a active 4.2 running. on another server. We have a ILO board in a 380G4 that we try to discover manually in SIM5 but we do not succeed. SIM reports it as being unknown and not reachable. On the 4.2 we have it discovered and also reporting it as being healthy.
I have been trying to investigate the security settings for the ILO but I can not see what is wrong. How do we get SIM5 to detect the ILO board? Is there some security setting that I miss? or a certificate?
Thank you in advance.
Best regards
Tommy Frandsen
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 03:47 AM
03-20-2006 03:47 AM
Re: SIM5 can not detect ILO in 380 G4
Forward and reverse lookups OK? Can you ping the IP address from the CMS?
Believe it or not, I had a very wierd and similar problem a month or two ago where the CMS could not ping a SUBSET of RIB cards that were on the same subnet. Worse than that, it was intermittent, it was ONLY RIB cards, and it was only RIB cards on the SAME subnet. I didn't have a problem with any RIB cards or servers anywhere else.
I never found the root cause, but what I did do was upgrade the HP Network Configuration Utility (this was a Proliant), and that seemed to fix it.
Believe it or not, I had a very wierd and similar problem a month or two ago where the CMS could not ping a SUBSET of RIB cards that were on the same subnet. Worse than that, it was intermittent, it was ONLY RIB cards, and it was only RIB cards on the SAME subnet. I didn't have a problem with any RIB cards or servers anywhere else.
I never found the root cause, but what I did do was upgrade the HP Network Configuration Utility (this was a Proliant), and that seemed to fix it.
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