Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Manual association

SOLVED
Go to solution

Manual association

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

15 REPLIES
shocko
Honored Contributor

Re: Manual association

What version of OA are you using? I think there was an advisory regarding this.

 

Related: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02886995&lang=en&cc=us&taskId=135&prodSeriesId=3188465

 

If my post was helpful please award me Kudos! or Points :)

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.

 

                       

shocko
Honored Contributor

Re: Manual association

The iLO is the key device for all associations. Can you post the XMLReply form the iLO?

If my post was helpful please award me Kudos! or Points :)

Re: Manual association

Hi Shocko,

 

I Attached the XML to this post (please, remove the .txt at the end)

 

Many thanks

 

Patrick

shocko
Honored Contributor

Re: Manual association

Looks like the iLO is detecting the enclosure details:

 

<BAY>6</BAY>
<ENCLOSURE_cUUID>42473930-3738-3234-594D-315000000000</ENCLOSURE_cUUID>
If my post was helpful please award me Kudos! or Points :)

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

shocko
Honored Contributor

Re: Manual association

Hi,

Can you check that indeed that is the UUID of the enclosure as identifed in SIM?

If my post was helpful please award me Kudos! or Points :)

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

shocko
Honored Contributor

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?

If my post was helpful please award me Kudos! or Points :)

Re: Manual association

Hi Shocko,

 

Yes, iLo and OA are in the same subnet.

 

to sumarize:

 

iLo3 are running FW version 1.50 or 1.55

iLo4 are running FW version 1.20 or 1.22

OA are running FW version 3.70 or 3.71

 

Association iLo3/4 <--> server is just working fine

Association Servers (via iLo3/4) <--> enclosure is NOT working

Association OA <--> enclosure is NOT working

 

Many thanks

 

Patrick

shocko
Honored Contributor

Re: Manual association

My iLO XML reply looks different on iLo 3 but my OA is 3.32 (see attached). Did you use the https://iloip/xmldata?item=All format to get the XML reply?

 

If my post was helpful please award me Kudos! or Points :)

Re: Manual association

Hi Shocko,

 

Yes, I got the XML file from https://iloip/xmldata?item=All. It looks quite similar to your file, except for the spaces after the serial number (probably added by my text editor).

 

I did some more investigation in the database itself, but still haven't found what could cause this problem.

 

Many thanks for your help

 

Partrick

shocko
Honored Contributor

Re: Manual association

I wish I had some more time and I would troubleshoot this against my own installation but, als, I don't. Could anyone from HP comment on how these associations are formed? I presume it's a stored proceededure in the DB that runs and creates them based on the UUIDs?

If my post was helpful please award me Kudos! or Points :)
shocko
Honored Contributor

Re: Manual association

See here: http://h18013.www1.hp.com/products/servers/management/hpsim/techsupport.html

Is forward reverse DNS in place for all OA/VC/iLO/Server?

If my post was helpful please award me Kudos! or Points :)
Solution

Re: Manual association

Hi,

 

I tried the Hotfix for SIM 7.2 which was just released, but did not help in my case.

 

Finally, I did something i don't like to do, but we simply could not wait longer without a reliable monitoring in place:

 

 

1) mxnode -r <EnclosureName> -x force (to remove the enclosure without having to remove all blades and switches in it)

 

2) start a Discovery  of the OA

 

The enclusure was rediscovered and all association were successfully re-done.

 

Hope this can help someone else

 

Regards

 

and thank you Shocko for your help

 

Patrick