HP SIM VCR Recognition

robheck — Fri, 24 Jan 2014 15:48:09 GMT

I'm running HP SIM on a *NIX box and am trying to use a Windows VM as my VCRM. I've configured this, but it's not recognized in SIM as one of the repositories. My discovery results are as follows:

********* Significant issues and overall target discovery/identification
          status:
Major:    There is no working sign-in credential for this system. Go to
          Options -> Security -> Credentials -> System Credentials and either
          enter the credentials there or be sure that the checkbox enabling
          HP SIM to try other credentials is checked.
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.

********* 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...
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 ProLiant SNMP Foundation agents for servers are not installed
          or are not configured.
        * 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:   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 Virtual Machine Management (VMM) Plug-in Identification...
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * Running SSH Protocol identification...
Normal:   This system has SSH protocol support.
        * Running SSH Identification...
Minor:    The system cannot be logged in using SSH protocol; check
          credentials or check the settings in the SSH configuration file
        * 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:   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.
        * Building system relationships...
Minor:    The Secure Shell key-based access authentication is not configured
          on the system(s).
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.

Seems like the CMS doesn't think this is a system? Any thoughts on this? I appreciate any insight.

Re: HP SIM VCR Recognition

Andrew_Haak — Fri, 24 Jan 2014 23:15:29 GMT

Hello there,

Did you install the system management homepage? You need the System management homepage and if you have that installed please create a trust with the SIM server. You probably also need snmp or wbem support for the datasource. Snmp can be installed from windows add remove wbem is a seperate download.

Once installed check if ghe datasource is set and that you have either snmp or wbem credentials setup for the VCRM.

Kind regards,

Andrew

topic Re: HP SIM VCR Recognition in Server Management - Systems Insight Manager

HP SIM VCR Recognition

Re: HP SIM VCR Recognition