********* 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.175.32.28 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.
Minor:    The discovered server cannot be associated with its management
          processor. For Windows and Linux, verify that the supported HP
          Insight Management Agents or WBEM provider is installed on the
          server. For HP-UX, verify that the WBEM Services version has the
          Management Processor provider. Also, verify that the management
          processor has been discovered in HP SIM.
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 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 responded to an SNMP request; it supports SNMP Protocol
          and has a valid read community string.
        * Running SNMP System Type manager ...
Normal:   No matching SNMP System Type Manager rule for sysObjID was found.
        * 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:   Identification can get the system information from the ProLiant
          SNMP Foundation agents for servers.
        * Running HP NetServer identification...
Normal:   System supports the NetServer SNMP agent, adding system type.
        * Running HP-UX SNMP identification...
Normal:   System does not have the HP-UX SNMP agents installed.
        * 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.
Normal:   This Linux system 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...
Normal:   The system is not part of HP Serviceguard cluster.
        * Running SNMP subtypes identification...
        * No additional subtype(s) found from SNMP.
        * Running RackManager Identifier which will discover systems in a
          rack if the automatic rack discovery option for RackManager is
          enabled...
Normal:   A non-embedded operating system is detected so skipping the Rack
          Manager identification.
        * Running OA Identifier which will discover systems in an enclosure
          if the automatic enclosure discovery option for OA is enabled...
Normal:   A non-embedded operating system is detected so skipping the OA
          identification.
        * Running Enclosure Manager Identifier which will discover systems in
          an enclosure if the automatic enclosure discovery option for
          Enclosure Manager is enabled...
Normal:   A non-embedded operating system is detected so skipping the EM
          identification.
        * Running iLO Identifier which will discover the server if the
          automatic server discovery option for iLO is enabled...
Normal:   A non-embedded operating system is detected so skipping the ILO
          identification.
        * 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...
        * 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...
Normal:   SSH is configured on this system.
Normal:   The trust between the CMS and the managed system is established.
        * Running system Manage Communication diagnosis...
        * System identification finished on system.