HP SIM 7.2 First Time User and Error Messages

[DBrune]

It looks like you've gotten part of your problem solved.  I know you said that you have checked your SNMP settings for that server and made sure that the community strings are correct.  Have you tried deleting the strings and re-typing them (no copy-paste).  The strings are case-sensitive.  I'm sure this is all stuff you've probably looked at, but it's stuff I've found in the past, so I'm just laying it out there. 

Another thing that I've seen is problems with the SNMP service on my target server.  Sometimes re-starting the HP Agents and the SNMP service can do the trick. 

Are the SNMP ports (161 and 162) open on the firewall?

If you're running WMI/WBEM for management instead of SNMP, are ports 5988 and 5989 open?

You're running another instance of SIM, have you tried running identification on the server that is giving you trouble with your old SIM?

[rbk12sdus]

After updating the credentials within the SMH here is a screen shot of the user list.

[DBrune]

Your SMH is good to go, since discovery pulled model, serial, etc.  You just need to figure out what's going on with your SNMP.

[rbk12sdus]

SNMP settings double checked - removed and readded - on both the HPSIM and target server.  Also, the services were restarted for SNMP and HP Agents on both servers.  Get the same result when trying to discover the target server.

Below are the discovery results for the old HP SIM server with the same target:

********* Significant issues and overall target discovery/identification
          status:
Normal:   The system has valid hardware data (model, serial number, and
          unique identifier) and has been identified properly for SIM to
          manage.
Normal:   System(s) have been successfully identified.

********* 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.
        * 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...
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...
        * 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:   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...
Normal:   The trust between the CMS and the managed system is established.
        * Running system Manage Communication diagnosis...
        * System identification finished on system.

Within SIM there is an option to select the SNMP Trap Settings, attached is Screen Shot #5 for review.  Does is make a difference which one is selected for communication purposes?

[DBrune]

Within SIM there is an option to select the SNMP Trap Settings, attached is Screen Shot #5 for review.  Does is make a difference which one is selected for communication purposes?

That has to do with how a trap is handled once it reaches SIM.  It doesn't affect discovery.  Trap settings allows you to customize traps received, ie adding new or different wording to the description (Call Steve at xxx.xxx.xxx ASAP!!), change criticality, etc.

I'm at a bit of a loss as to what the problem is.  The agents are working, because your old SIM server discovered it just fine.  Unless the agents are old?  Are the HP agents up to date?  I mean, that's a long shot (since I haven't looked up which agent versions, hardware, OS's, etc are deprecated in 7.2) but I'm running out of ideas.  Since this is a new install, have you tried calling 1-800-633-3600?  (Software support). 

[rbk12sdus]

Found the following agent version cp017925.exe for Windows 2008 R2 version (Link).  Installed it on the target server using admin account.  Ran the discovery again and same result within SIM.  Is there a charge to call the 1-800-633-3600 number for support?

[rbk12sdus · Accepted solution]

After talking with HP these are the steps to follow for resolution of the problem:

1) Reinstalled the HP SMH Agent on the target server with the updated Version 7.2
2) Revised the SNMP trap information

- IP Address of the SIM Server

- Added localhost

- 127.0.0.1

3) Attempt to rediscover the system(s)

Spoke with Ujjwal Kumar Singh at HP.  He was very helpful and fluent English speaking CSR agent.

[Ging_rojas8990]

I am new to HP SIM , too.

I want to know whether it is required SQL server as database for SIM?