SIM 6.3 cannot discover one server

Q4U — Fri, 30 Dec 2011 17:51:44 GMT

I have a problem with one particular server being discovered. It is an older DL360, but there is an identical one that can be discovered and monitored. Oddly enough, if I install SIM on the one that cannot be discovered, it can discover the one that can't discover it. Here is the Target Details from the original SIM:

********* Significant issues and overall target discovery/identification
          status:
Major:    The system cannot be identified properly for HP SIM to manage;
          unable to get one or more of the following: model, serial number or
          unique identifier (UUID). For management processors, verify the
          system is running the latest firmware. For Linux based operating
          systems, you must have dmidecode installed, enable the
          PermitRootLogin and PasswordAuthentication in sshd, and use root
          sign-in credential. For HP-UX, verify the sign-in credential. For
          Windows, check if WMIMapper is configured correctly on the CMS and
          verify the sign-in credential.
Critical: The system(s) can not be identified by WBEM, SNMP or SSH

********* Additional results (listed for information only):

        * Starting identification process...
        * Checking for known running web servers...
        * Checking for System Management Homepage and other HP web agents...
Normal:   System Management Homepage (SMH) is installed or is responding on
          the system(s).
        * Checking for SNMP protocol support on system...
Normal:   The system did not respond to SNMP. Verify security settings and
          community strings in Options->Security->Credentials->System
          Credentials
        * Running SNMP System Type manager ...
Normal:   The system does not support SNMP.
        * Running SNMP base cluster identification using common cluster
          MIB...
Normal:   This system does not have the common cluster MIBs support.
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * Checking for WBEM protocol support on system...
Minor:    This system does not have any SMI-S CIMOMs installed. No storage
          systems will be found on this system.
Minor:    The Central Management System (CMS) cannot communicate with the
          CIMOM locally installed on the managed system using the WBEM
          protocol, Identification will try to identify Windows systems using
          the WMI Mapper as proxy; for Linux and HP-UX systems, check
          credentials by going to Options->Security->Credentials->System
          Credentials. For Linux systems also check if the HP WBEM provider
          is installed.
Critical: There are no valid WBEM / WMI credentials for the system(s).
        * Running WBEM rules based identification...
Minor:    Identification cannot get computer system hardware data from the
          WBEM / WMI providers.
        * 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 WS-Man identification...
Minor:    The system did not respond to WS-Management (WS-Man) request.
        * Running HP ProLiant management agent identification...
Normal:   The system does not support SNMP.
        * Running HP NetServer identification...
Normal:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * 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.
Normal:   OS Name is identified by the SSH 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 Serviceguard Identification...
        * Running SNMP subtypes identification...
        * Running RackManager Identifier which will discover systems in a
          rack if the automatic rack discovery option for RackManager is
          enabled...
Normal:   The system is not a Rack Manager, skipping automatic discovery of
          systems in the rack.
        * 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 Enclosure Manager Identifier which will discover systems in
          an enclosure if the automatic enclosure discovery option for
          Enclosure Manager is enabled...
Normal:   The system is not an Enclosure Manager, skipping automatic
          discovery of systems in the enclosure.
        * Running iLO Identifier which will discover the server if the
          automatic server discovery option for iLO is enabled...
Minor:    The system responds to the HTTP request but cannot get the XML
          output. It is normal for servers not to get the XML data.
        * Running p-Class Identifier...
Normal:   The system is not a p-Class so skipping p-Class identification.
        * Running Monarch OA Identification...
Normal:   The system is not a monarch OA so skipping monarch OA
          identification.
        * Resolving DNS names...
Normal:   The fully qualified domain name was successfully resolved for the
          system.
        * Running Virtual Machine Management (VMM) Plug-in Identification...
Normal:   Virtual Machine Management (VMM) Integration is not enabled so
          skipping VMM VM Identification.
        * Building system relationships...
Minor:    The Secure Shell key-based access authentication is not configured
          on the system(s).
Normal:   The trust between the CMS and the managed system is established.
        * Running system Manage Communication diagnosis...
        * System identification finished on system.

I'm stumped.

Re: SIM 6.3 cannot discover one server

Bart_Heungens — Fri, 30 Dec 2011 20:45:02 GMT

Hi,

For me it is a SNMP problem... Please check and compare the SNMP settings, and if it is running...

In the Security tab there should be the local 127.0.0.1 address and the address of the SIM server...

What do you see when you launch the SMH? I assume that it doesn't discover the server model either? This would mean also a badly configured SNMP...

Kr,

Bart

Re: SIM 6.3 cannot discover one server

Q4U — Fri, 30 Dec 2011 21:04:55 GMT

Thanks, Bart.

You are totally correct. It was SNMP. It was set to accept SNMP requests from localhost and an old server that has been retired. Not sure how I managed to get the other one setup without running into this problem, but apparently I did.

Thanks again.

Re: SIM 6.3 cannot discover one server

Bart_Heungens — Fri, 30 Dec 2011 21:14:37 GMT

You're welcome...

Re: SIM 6.3 cannot discover one server

Q4U — Fri, 30 Dec 2011 22:22:20 GMT

Now I can't get into the SMH. It times out and suggests a SNMP problem with having at least one Read/Write string. What did I break now?

Re: SIM 6.3 cannot discover one server

Q4U — Fri, 30 Dec 2011 22:52:40 GMT

Never mind. I reinstalled SMH and it came up fine. Now I can monitor all the servers from one place, finally!

Thanks again for your help.

topic Re: SIM 6.3 cannot discover one server in Server Management - Systems Insight Manager

SIM 6.3 cannot discover one server

Re: SIM 6.3 cannot discover one server

Re: SIM 6.3 cannot discover one server

Re: SIM 6.3 cannot discover one server

Re: SIM 6.3 cannot discover one server

Re: SIM 6.3 cannot discover one server