********* 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. 
Normal:   Identification status is only available for servers, workstations, 
          or desktops, where monitoring is enabled. 

********* 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 did not respond to SNMP. Verify security settings and 
          community strings in Options->Security->Credentials->System 
          Credentials 
        * 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:   The system does not support SNMP.
        * Running SNMP base cluster identification using common cluster 
          MIB... 
Normal:   SNMP is not supported or globally disabled, skipping SNMP cluster 
          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. 
        * 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 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:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * 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... 
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. 
Minor:    If the http communication from CMS to target is working, but if it 
          is found to be slow then try increasing the Default connection 
          timeout parameter for http in global protocol settings. 
        * Running p-Class Identifier...
Normal:   The system is not a p-Class so skipping p-Class identification.
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * Running SSH Protocol identification...
Major:    Using SSH Protocol in discovery is disabled on the Central 
          Management Server (CMS). 
        * Running SSH Identification...
Major:    Using SSH Protocol in discovery is disabled on the Central 
          Management Server (CMS). 
        * Running WS-Man identification...
Major:    WS-Management(WS-Man) is globally disabled so skipping 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...
        * Running SNMP System Type manager ...
Normal:   The system does not support SNMP.
        * Running SNMP subtypes identification...
        * 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
        * Running Virtual Machine Management (VMM) Plug-in Identification...
        * System passed the discovery filter and will be added.
        * Building system relationships...
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.