HP SIM discovery blade information

[Egorchick]

Hi !

I have HP SIM 7.2 and I want to discover HP enclosure and blade information.

However I don't see any detailed information about blades after discovery. All blades are 460cG7. The only I can see is in attach. How can I discover Memory, Number of CPUs etc..

Help Please...

[n0kia]

Usually after a new discovery it runs a task called "Initial data collection" to collect the data from the providers.

Do a manual one and check it again.

Options > data collection.

[Egorchick]

Hi again!

The thing is, that I've already tried to do this. And when I start the process, I recieve the status "Skipped", and the folowwing text in STDOUT window:

"Data collection was skipped for this system because it is suspended or inaccessible.
Root Cause: The target system has been suspended or somehow become inaccessible.
Corrective Action: Check system status and reset (if appropriate) the following System Page: Suspend/Resume Monitoring."

By the fact, the server is acceseble, ping is OK.

Anything else ?

[Andrew_Haak]

If you discover a server blade trough an onboard admin the servers get added as serials. The OS names or ip need to be discovered seperately and you need to configure credentials in with the discovery job like windows! Linux or esx. If the os and other server info is correctly discoverec the serial is then replaced by either the IP adres or server name.

[Egorchick]

Well, in my case the problem was in iLO 3.

I've tryed the discovering of c7000 enc with G8 blades with just the credentials of OA and everything went fine. I got all info about blades.

But another problem is still going: I've got serial numbers insead of hostnames in Network Name and Preferred System Name

I've entered the credentials of ESXi servers installed inside, but this didn't solve the problem. For some servers I've got hostname, for some - don't. When I rediscover the servers

(first delete hp sim data using

C:\Users\Administrator>mxnode -lf >> C:\data\nodes.xml
C:\Users\Administrator>mxnode -r -f C:\data\nodes.xml -x force

)

I can see some servers have hostname, some servers still have serial number. And each time that servers are different.

For example the first discover blade 1 has hostname, the next discover it has serial.

From HP SIM server the nslookup is OK and ping -a is OK.

Anything helpful ?

[Andrew_Haak]

Hello,

Could you do a Identify for a server that stays a serial and post that log?

[Egorchick]

********* Significant issues and overall target discovery/identification
          status:
Minor:    The name of the system could not be resolved to a fully qualified
          domain name. For a Windows CMS, make sure that the domain name of
          the managed system is included in the DNS suffixes in the Windows
          Advanced TCP/IP Settings page.
Minor:    The reverse DNS lookup using the IP address: 10.10.2.117 failed. It
          might be that the nslookup timed out or DNS server cannot find this
          address, or that the domain does not exist.
Minor:    Verify that your name resolution service or the host file
          configuration is configured properly so that your system's hostname
          can be resolved to the fully qualified domain name.
Normal:   The system has valid hardware data (model, serial number, and
          unique identifier) and has been identified properly for SIM to
          manage.
********* Significant issues and overall target discovery/identification
          status:
Minor:    The name of the system could not be resolved to a fully qualified
          domain name. For a Windows CMS, make sure that the domain name of
          the managed system is included in the DNS suffixes in the Windows
          Advanced TCP/IP Settings page.
Minor:    The reverse DNS lookup using the IP address: 10.10.2.117 failed. It
          might be that the nslookup timed out or DNS server cannot find this
          address, or that the domain does not exist.
Minor:    Verify that your name resolution service or the host file
          configuration is configured properly so that your system's hostname
          can be resolved to the fully qualified domain name.
Normal:   The system has valid hardware data (model, serial number, and
          unique identifier) and has been identified properly for SIM to
          manage.

********* 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...
Normal:   The system did not respond to SNMPv3. Verify security settings and
          v3 credentials in Options->Security->Credentials->System
          Credentials
        * 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:   The system is not an Onboard Administrator, skipping automatic
          discovery of systems in the enclosure.
        * 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 bare-metal server will be added because the automatic server
          discovery option for iLO is enabled.
        * 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...
        * 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...
        * Checking if the Node is a Virtual Center...
Normal:   Skipping MxVirtualCenter Identifier.
        * 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.
        * Checking if the Node is a Virtual Center...
Normal:   Skipping MxVirtualCenter Identifier.
        * 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.

[Andrew_Haak]

Hello again,

That looks like an ILO log.

Normal:   This system is a management processor; attempting to get associated server information

The host you discovered is probably an unknown object as the credentials did not work for that object ? Could you try to find the server object, add the credentials and save them. SIM should then run a discovery job for that server. If it does can you post that log again ?

[Egorchick]

So you meen, that if my ESXi, that is installed on 10.10.xx.xx blade has IP 192.168.xx.xx Ishould add the 192.168.xx.xx IP to discovering?

[Andrew_Haak]

Yes.