GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- How does SIM identifies in what server an ILO is?
Server Management - Systems Insight Manager
1856492
Members
13604
Online
104113
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
back
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
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
08-22-2006 09:09 PM
08-22-2006 09:09 PM
How does SIM identifies in what server an ILO is?
I got one ILO where SIM refuses to identify the server correctly. The server used to be called "dbprd04", but now is called "dbrac04". And SIM still identifies this ILO to be in "dbprd04". When I log into ilo itself, it does correctly "dbrac04". Because of this SIM shows the server "dbrac04" not to have a management processor, even when it does.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2006 04:32 AM
08-23-2006 04:32 AM
Re: How does SIM identifies in what server an ILO is?
I'm not sure if this is true for every server model and ilo version but the way SIM seems to know what ilo belongs where is by using the UUID which is a combination of the 6-digit partno and the serial number of the server. The server's UUID is then prepended with "ILO" and that is what is returned in the XML reply by the ILO.
I had to recently manually edit this information in bl460p firmware of a newly delivered blade server since it was missing for some reason. If the motherboard is replaced, the serial number will have to be updated manually in the RBSU and the partno will have to be verified as well. Upon boot the UUID will be updated to refect the changes and the ilo will update it's UUID accordingly.
I hope that helps more than it confuses. ;)
I had to recently manually edit this information in bl460p firmware of a newly delivered blade server since it was missing for some reason. If the motherboard is replaced, the serial number will have to be updated manually in the RBSU and the partno will have to be verified as well. Upon boot the UUID will be updated to refect the changes and the ilo will update it's UUID accordingly.
I hope that helps more than it confuses. ;)
"Did you get that memo?"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2006 04:34 AM
08-23-2006 04:34 AM
Re: How does SIM identifies in what server an ILO is?
Also, when I'm having hostname issues, sometimes just removing and rediscovering the devices will clear it up.
"Did you get that memo?"
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 2026 Hewlett Packard Enterprise Development LP