I have HPSIM 7.4.0 on a server that monitors our HP hardware.
I have a 4x DL160G9 servers that I am looking to get SIM to discover and start monitoring.
All insight agents, SMH and anything else that the HP Service Pack has to offer has been installed. However, if I run a discovery on that server (which already has SNMP added and community strings) I can't get it to add into HP SIM and start monitoring.
Discovery logs:
********* 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... Minor: Global SNMPv3 Identification is disabled. * Running HP ProLiant management agent identification... Normal: Identification can get the system information from the ProLiant SNMP Foundation agents for servers. * Running SNMP base cluster identification using common cluster MIB... Normal: This system does not have the common cluster MIBs support. * 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: 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 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 XMLReply Identifier which will discover systems in a rack/enclosure if the automatic discovery option for the container node is enabled... Normal: A non-embedded operating system is detected so skipping the Management processor 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 IPMI protocol identification... Normal: Skipping IPMI discovery in favor of WBEM/SNMP discovery. * 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... Normal: A non-embedded operating system is detected so skipping the 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: System Management Homepage (SMH) is installed or is responding on the system(s). * 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... 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... Major: The identification or discovery of this system has timed out, so the task for this target has failed. If the managed system's CPU is heavily utilized, then you may want to increase the timeout value for identification for a single system. To do that, increase the IdentificationTaskDefaultThreadTimeoutSec property in the globalsettings.props file to 1800 (30 minutes) or more using the mxglobalsettings CLI command. For more information, see the online help.