How to monitor HP P4000 nodes with HP SIM?

[JRedmond]

I have a machine with HP SIM 6.3 installed and configured.  This machine has a NIC on the LAN and SAN network.  I have my HP P4000 cluster configured use SNMP pointing to the SAN IP of HP SIM.  When I try to run a discovery from HP SIM to the HP P4000 node IPs.  The credentials I configured is the administrator account for the P4000 cluster.  Here is the HP SIM errors I get back.  If I am  doing this incorrectly please say so.  There isn't a whole lot of information available on this.   Thanks in advance.

********* Significant issues and overall target discovery/identification
          status:
Minor:    The name of the system could not be resolved to a fully qualified
          domain name. For a Windows CMS, make sure that the domain name of
          the managed system is included in the DNS suffixes in the Windows
          Advanced TCP/IP Settings page.
Minor:    The reverse DNS lookup using the IP address: X.X.X.X failed. It
          might be that the nslookup timed out or DNS server cannot find this
          address, or that the domain does not exist.
Minor:    Verify that your name resolution service or the host file
          configuration is configured properly so that your system's hostname
          can be resolved to the fully qualified domain name.
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.
Critical: HP SIM cannot communicate with the SNMP service on the system(s).

********* 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 did not respond to SNMP. Verify security settings and
          community strings in Options->Security->Credentials->System
          Credentials
        * Running SNMP System Type manager ...
Normal:   The system does not support SNMP.
        * 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 WBEM protocol support.
Minor:    This system does not have any SMI-S CIMOMs installed. No storage
          systems will be found on this system.
Normal:   This system has a server CIMOM installed.
        * Running WBEM rules based identification...
Minor:    The computer system information is not available on the managed
          system; For HP hardware, please check the HP site to get the HP
          WBEM provider.
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...
Normal:   A non-embedded operating system is detected so skipping the WS-MAN
          identification.
        * Running HP ProLiant management agent identification...
Normal:   The system does not support SNMP.
        * Running HP NetServer identification...
Normal:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * 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 Storage identification...
        * Storage identification completed.
        * Running HP Serviceguard Identification...
        * Running SNMP subtypes identification...
        * Running RackManager Identifier which will discover systems in a
          rack if the automatic rack discovery option for RackManager is
          enabled...
Normal:   A non-embedded operating system is detected so skipping the Rack
          Manager identification.
        * 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 Enclosure Manager Identifier which will discover systems in
          an enclosure if the automatic enclosure discovery option for
          Enclosure Manager is enabled...
Normal:   A non-embedded operating system is detected so skipping the EM
          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 Monarch OA Identification...
Normal:   The system is not a monarch OA so skipping monarch OA
          identification.
        * Resolving DNS names...
        * 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...
Minor:    The Secure Shell key-based access authentication is not configured
          on the system(s).
Major:    In order to access Secure Sockets Layer (SSL) based tools such as
          System Management Homepage and Version Control Repository Manager
          on remote systems without performing an additional sign-in, you
          need to establish trust between the Central Management Server (CMS)
          and the managed system(s).
        * Running system Manage Communication diagnosis...
        * System identification finished on system.

[fred Passeron]

Hi

Here are some limks to help you out.

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01886197/c01886197.pdf

from the notes:

Integrating the HP LeftHand and HP P4000 MIBs into HP Systems Insight Manager

(HP SIM) Versions 6.0, 6.1, and 6.2

Find instructions about using the HP LeftHand and HP P4000 MIBs with HP Systems Insight Manager

(HP SIM) Versions 6.0, 6.1, and 6.2 at the Business Support Center:

NOTE:

•

SIM 6.2 supports device monitoring all P4000 devices and includes the 8.5 version SAN/iQ MIBs

•

SIM 6.2 supports device monitoring all P4000 devices with SAN/iQ 9 but the SAN/iQ 9 MIBs

must be re-loaded manually into SIM

•

A future release of SIM will include SAN/iQ 9 MIBs (6.2.2)

In your case, running HP SIM 6.3, the lefthand Mibs should be already here according to this :

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-722ee8c388c04a469c24ff60df&taskId=135&swLang=8&lang=en&cc=us&mode=5&

so follow the step 9 on the following page to setup properly snmp on your san IQ:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02505873&dimid=1150557916&dicid=alr_sep10&jumpid=em_alerts/us/sep10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts

hope it helps

Another thread on the subject that might help :

http://h30499.www3.hp.com/t5/HP-LeftHand-P4000/HPSIM-6-3-and-Lefthand-P4000/m-p/4795873#M2804

fred

[wkaefferlein]

Hi,

try sanmon as user and sanmon as password for authentication to p4000.

[RPMCanesandPats]

I'm having a similar issue in that I'm having a lot of trouble getting 2 of the nodes in my environment to show up under Remote Support Configuration Services.  They are part of the same management group as the other being discovered.  Thoughts?

[Buggsy]

I had a simial problem. I had two specific nodes who's serial numbers could not be read, which made remote support fail. For me, I just looked up the serial numerbs (we have them written down) and went to each node in SIM and manually entered the info. This fixed it up. Looked up the system in SIM, click on the Tools & Links tab, then the Edit System Properties. I also went back to each node and manualy tweaked them. At the bottom of the Edit System Properties, make sure you fill out the "Contract and Warranty Information" at the bottom. Without the Entitlement information, it work work either.