- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Manual association
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-21-2013 02:58 AM
05-21-2013 02:58 AM
Hello,
We did an upgrade from SIM 7.1.2 to 7.2 and at the same time, we moved the remote database from a SQL 2008 to a SQL 2012. Since then, the association between OA and Enclosure doesn't seams to work, even if the discovery process is running fine, without any error.
Is there a way to do a manual association ?
Thank you for your help
Regards
Patrick
Solved! Go to Solution.
- Tags:
- upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2013 05:21 AM
05-23-2013 05:21 AM
Re: Manual association
What version of OA are you using? I think there was an advisory regarding this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2013 01:40 AM
05-28-2013 01:40 AM
Re: Manual association
Hi Shocko,
It seams to be a very similar issue, but we are using the latest versions of firmware and software:
Versions in use:
HP SIM: 7.2 (with a remote SQL 2012 sp1)
OA: 3.71 and 3.70
ilo3: 1.55 and 1.50
ilo4: 1.20 and 1.22
We've seen this issue on all the above firmware combinations (was working fine with SIM version 7.1)
The OA discovery process don't raise any error, but the association is not created.
Many thanks for your help
Patrick
OA DIscovery log:
********* Significant issues and overall target discovery/identification
status:
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Normal: System(s) have been successfully identified.
********* Additional results (listed for information only):
* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Normal: The system responded to an SNMP request; it supports SNMP Protocol
and has a valid read community string.
* Checking for SNMPv3 protocol support on system...
Minor: Global SNMPv3 Identification is disabled.
* Running HP ProLiant management agent identification...
Normal: This system is a management processor; attempting to get associated
server information.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: The system is identified as management processor, skipping SNMP
cluster identification.
* Checking for WBEM protocol support on system...
Normal: The system is not a server so skipping WBEM identification.
* Running WBEM rules based identification...
Normal: The system is not a server so skipping WBEM identification.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM
credentials may not be specified so skipping VM Identification.
* Running Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP NetServer identification...
Normal: System does does not have the NetServer SNMP agents installed.
* Running HP-UX SNMP identification...
Normal: System does not have the HP-UX SNMP agents installed.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: Systems in an enclosure and Virtual Connect domains will be created
because the automatic enclosure discovery option for OA is enabled.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Normal: The system is not an Integrated Lights-Out management processor;
skipping automatic discovery of bare-metal system.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: Skipping IPMI discovery. System is logical device.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
credential.
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP System Type manager ...
Normal: No matching SNMP System Type Manager rule for sysObjID was found.
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping MxVirtualCenter Identifier.
* Checking if this system is supported by Insight Control power
management...
* System is a management processor that supports Insight Control
power management.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2013 02:12 AM
05-28-2013 02:12 AM
Re: Manual association
The iLO is the key device for all associations. Can you post the XMLReply form the iLO?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2013 02:46 AM
05-28-2013 02:46 AM
Re: Manual association
Hi Shocko,
I Attached the XML to this post (please, remove the .txt at the end)
Many thanks
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2013 03:07 AM
05-28-2013 03:07 AM
Re: Manual association
Looks like the iLO is detecting the enclosure details:
<BAY>6</BAY> <ENCLOSURE_cUUID>42473930-3738-3234-594D-315000000000</ENCLOSURE_cUUID>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2013 02:36 AM
05-29-2013 02:36 AM
Re: Manual association
Yes the xmlreply content is correct
It seams to be more the job that write the association in the HP SIM DB which is not working correctly
Does someone know if this job has a logfile and in which table is this association first writen?
BTH, the association between ilo <--> server is working fine. Only the associations between enclosure <--> server and between enclosure <--> OA are not commited in the DB.
Thanks
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2013 06:23 AM
05-29-2013 06:23 AM
Re: Manual association
Hi,
Can you check that indeed that is the UUID of the enclosure as identifed in SIM?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2013 06:19 AM
05-31-2013 06:19 AM
Re: Manual association
Hi Shocko
The enclosure UUID in HP SIM is a bit different (in the end):
From the ilo4:
<ENCLOSURE_cUUID>42473930-3738-3234-594D-315000000000</ENCLOSURE_cUUID>
Withinh HP SIM:
42473930-3738-3234-594D-315020202020
But I'm not sure the association is done using this UUID, if you look at an xmlReplay.xml from an ilo3 (attached to this post), there is no UUID. We can only see the rack name and enclosure name.
Thank you
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2013 06:44 AM
05-31-2013 06:44 AM
Re: Manual association
Aplogies, I think I'm confusing some different threads here. my understanding was that:
- iLo associates server to iLo
- iLo assocaites server to enclosure
For this reaosn, the iLO is critical (and it's firmware version) as it talks to the enclosure (via the OA i'd imagine). The OA must manage it's own association. Are the iLos and the OA's all on the same network segment?