HP SIM and Storeonce D2D's (410 Views)
Reply
Occasional Contributor
Marvin99
Posts: 4
Registered: ‎12-05-2013
Message 1 of 5 (410 Views)

HP SIM and Storeonce D2D's

Hi,

 

I have 17 D2D devices which I have been asked to monitor using HPSIM 7.2. They are 2502i's 2504i's 4324's and 4210's. I have added the MIB's I have created a new object type and followed all the documentation and during discovery all but 3 have shown correctly.

I am having an issue with the 4210 because HPSIM doesnt recognise the device type and I cannot find any MIBS for it or looking at the documentation I cant see what is required to get it to work. but also I have 2x 2504i's that dont work, now the MIBS say they are for 2504i's but when I log onto these they say they are HP StorageWorks D2D2504i - G02-E where all the other 2504i's say they are HP StorageWorks D2D2504i - G02 only. I cannot find out what the difference is between the G02 and the G02-E but that is what appears to be making insight not be able to tell what it is. All software versions are 2.2.18 and I have been told the same software source code was used on got versions of hardware with no issues seen.

 

Has anyone else had this issue? or could anyone else tell me something to try? I am using SNMP and SSH for discovery. and an example failure is below.

 

********* Significant issues and overall target discovery/identification
          status:
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: The system(s) can not be identified by WBEM, SNMP or SSH

 

Thanks

 

Please use plain text.
Trusted Contributor
Andrew_Haak
Posts: 331
Registered: ‎09-13-2013
Message 2 of 5 (387 Views)

Re: HP SIM and Storeonce D2D's

Hello Marvin,

Could you post the complete log of the discovery? I don't see the snmp entry. Could it be that the snmp for the failing object is different from the discovered objects?

When you look at the failed object is snmp a discovered protocol ? And do you see any info?
Sometimes the community could be different like public for the one with little info and an other community with more info.

Kind regards,

Andrew
Kind regards,

Andrew
Please use plain text.
Occasional Contributor
Marvin99
Posts: 4
Registered: ‎12-05-2013
Message 3 of 5 (377 Views)

Re: HP SIM and Storeonce D2D's

********* Significant issues and overall target discovery/identification
          status:
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: The system(s) can not be identified by WBEM, SNMP or SSH

********* 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...
Minor:    Global SNMPv3 Identification is disabled.
        * 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...
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:   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...
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.


                       

Please use plain text.
Occasional Contributor
Marvin99
Posts: 4
Registered: ‎12-05-2013
Message 4 of 5 (375 Views)

Re: HP SIM and Storeonce D2D's

It looks like the 4210 discovered this time, it went green but with minimal information, not as much as has been logged for the other tyoe of D2D's

 

Identification

Address

10.20.126.10

Preferred System Name

ukshavdtd001

Network Name

ukshavdtd001.via.novonet

Serial Number

HPCZJ3280HSB

Product Description

System Type

Storage Device

Product Model

HP StorageWorks D2D

Hardware Description

HP StoreOnce Backup HPCZJ3280HSB HPCZJ3280HSB

Management Protocols

SNMP:1.0, SSH:SSH-2.0-OpenSSH_5.8

 

The log for that one looks like this

 

********* 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:   Identification status is only available for servers, workstations,
          or desktops, where monitoring is enabled.

********* 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:   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 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:   Found matching SNMP System Type Manager rule and the system type
          will be added.
        * 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...
        * 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.

Please use plain text.
Trusted Contributor
Andrew_Haak
Posts: 331
Registered: ‎09-13-2013
Message 5 of 5 (363 Views)

Re: HP SIM and Storeonce D2D's

Hello Marvin,

I gues you've also seen that the second Discovery has found a valid snmp community and the first did not respond with a valid community. Could be a config error on the first device or perhaps a firewall. The first would be more plausibel. Even with a missing mib you should get logging that says valid community. Compare snmp setting beteren the two devices and see if the objects differ in op subnet range.

Kind regards,

Andrew
Kind regards,

Andrew
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation