HP SIM 7.2 First Time User and Error Messages

[rbk12sdus]

I am new to HP SIM and need help trying to fix the following errors on a Windows 2008 R2 box.  When I try to communicate between the servers these are the error messages I receive.  Any ideas on how to resolve the following problems:

Identification:
Identification status is only available for servers, workstations, or desktops, where monitoring is enabled.

Event:
HP SIM has not subscribed to the system(s) to receive WBEM or WS-MAN indications and the Central Management Server is not on the SNMP trap destination list, so no events will be received from the system(s).

Run Tools:

Secure Shell (SSH) is not installed on the system(s).

Version Control: 

The Version Control Agent (VCA) on the system(s) is not configured to use a Version Control Repository Manager (VCRM), and so cannot determine if there is software or firmware available to install.

[SwisspostIT]

Hi,

it seems that you didn't configure the managed servers at all, so I'll try to help a bit.

Here you'll find plenty of documentation for getting started, how to install and configure HP SIM and the agents etc.:http://h18004.www1.hp.com/products/servers/management/unified/infolibraryfm.html

You need to have the hp management agents (Insight management agents, version control agent, system management homepage) installed on each server you want to manage and you'll need to configure them.

If you use SNMP for managing the systems, you also need to configure the SNMP Service on each managed system, so that they will send the snmp traps to your SIM Server. (check: http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&tmp_geoLoc=true&docname=c01479520)

If you use firewalls between your managed systems and HP SIM Server check this: http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/MANAGINGHPServers-withHPSIM.pdf

Also if you have Windows Firewall enabled, you'll have to configure the ports on each managed system and on the SIM server, so that Windows Firewall doesn't block them.

Since these are all basic things to do, I suggest you to first read a bit the documentation in the information library (link above).

Regards,

Ville

[rbk12sdus]

HP System Management Homepage installation was verified by following the Installation and Configuration Guide on the target server (Link).  Download of the SMH was located and installed (Link).  The program was already installed on the server and went into either the “Repair” or “Remove” mode.  Using the step by step wizard the information was revised according to the documentation presented above underneath the SMH.  Opened the server SMH and everything displays green except File Space Used.  See attachment.

Returning back to the HPSIM server went to Configure => Manage Communications.  Selected the server where the SMH is installed and still receive the same results as described in the first post.  Are there additional installation agents needed to make the two systems communicate?

[SwisspostIT]

Hi,

did you make all these steps?

1) configure SNMP Service (SNMP community like the configured community on HP SIM Server, SNMP Trap destination,...)

2) HP SIM certificate in HP SMH (security --> trusted management servers)
3) check if Firewall drops any communication (you can check this in %Systemroot%\System32\LogFiles\Firewall\pfirewall.log --> check if any "DROP's" are from the IP of the HP SIM on the managed system's logfile and if any "DROP's" are from the ip of the managed system on the HP SIM's logfile)

Regards,

Ville

[rbk12sdus]

1. The SNMP Service Properties => Security Tab => found on the SIM Server where the Community is labeled as ***2013 with Read/Create rights.  Traps are setup with the same community name ***2013 with a trap destination of ***SIM2.
 

On the target server the same results are found underneath the SNMP Service Properties, Security and Traps tabs.  Any ideas?

2. Options => Security => HP Systems Insight Manager Server Certificate? or Options => Security => Credentials > Trusted Systems? :

The information below is what is shown with the certificate/public key issued by HP:
Subject: Common Name (CN): *****
Alternative Names: *****
Organizational Unit (OU): Hewlett-Packard Network Management Software
Organization (O): Hewlett-Packard Company
Locality (L): Palo Alto
State (ST): California
Country (C): US
Issued By: Common Name (CN): *****
Organizational Unit (OU): Hewlett-Packard Network Management Software
Organization (O): Hewlett-Packard Company
Locality (L): Palo Alto
State (ST): California
Country (C): US
Public key is RSA 2048 Bits, Valid from March 20, 2013 4:14:24 PM CDT to March 21, 2023 4:14:24 PM CDT

3. No logs found on the SIM server or target server at the location specified.  Empty folders.

[DBrune]

In the target server's SMH, navigate to Security>Trusted Management servers and make sure that your SIM server is on the list.  If not, you can import it right from there.

Do you have the correct credentials entered that will allow SIM to 'talk' with the target server's SMH?  That is one problem I've seen in the past (a couple of misconfigured targets).

[rbk12sdus]

1. Screen Shot #2 shows that "Certificate 2" server can not be selected from options provided.

2. How do you verify credentials on the SMH on the target server?  Found Options => Security => Global Credentials within HP SIM.  Attempted to log in to SMH with the same credentials used in the Global settings and doesn’t work.

[DBrune]

1. Screen Shot #2 shows that "Certificate 2" server can not be selected from options provided.

You  need to be logged in to the SMH as someone with administrative rights.  Some of the time SMH is set up with limited functionality when you are logged in with local access or anyonymous.  Log in to the SMH with your domain id (assuming you are an administrator).  You should be able to import the certificate at that time.

2. How do you verify credentials on the SMH on the target server?  Found Options => Security => Global Credentials within HP SIM.  Attempted to log in to SMH with the same credentials used in the Global settings and doesn’t work.

That is a problem.  You won't get much without the SMH responding.  You can receive traps (if SNMP is properly configured) but you won't get all the good hardware information.   For many environments, there is a service account set up with administrative access to just the things that SIM needs (like SMH). 

Try this for an experiment.  Create a discovery for just the one server, and put your credentials (assuming you have admin rights on the machine) in to the sign-in credentials for the discovery and your community strings in to the snmp tab.  Save it and run it, see if you get a full discovery on that machine.

[DBrune]

Here is a screenshot from Settings >>SMH>>Security>>User Groups indicating how to check who is authorized to do what on the SMH.

[rbk12sdus]

1. System Credentials:

Credentials where revised through repair option for SMH, allowing access to the certificate location within the “Trusted Management Servers” section.  There are two separate certificates, one for the old SIM we are currently running and one for the new SIM (the new install 7.2).  See Screen Shot #3.

2. Discovery Results from the target server:

********* 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.
Critical: The system(s) can not be identified by either WBEM or SNMP

********* 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...
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 WS-Man identification...
Minor:    The system did not respond to WS-Management (WS-Man) request.
        * 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...
        * 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.