--------------------------------------------------------------------------------
   System Name:  hbmntbck 
   Status:    Completed with major errors 
 
   Exit code: N/A 
   Stdout:  

********* Significant issues and overall target discovery/identification 
          status: 
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. 
Major:    HP SIM can access the system(s) SNMP data, but it cannot access all 
          the system information. 

********* 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...
Normal:   This system has at least one SMI-S CIMOM installed to serve as the 
          storage proxy to discover storage systems. 
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 WS-Man identification...
Minor:    The system did not respond to WS-Management (WS-Man) request.
        * Running HP ProLiant management agent identification...
Normal:   The ProLiant SNMP Foundation agents for servers are not installed 
          or are not configured. 
        * 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...
Minor:    The system(s) do not have Secure Shell (SSH) installed or it is not 
          running on the managed system(s). 
        * Running SSH Identification...
Normal:   SSH Protocol is not enabled so skipping SSH Identification.
        * Running Storage identification...
        * No storage profiles were found on this system.
        * Storage identification completed.
        * Running HP Serviceguard Identification...
        * 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:   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 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...
Normal:   The trust between the CMS and the managed system is established.
        * Running system Manage Communication diagnosis...
        * System identification finished on system. 

   Stderr: None