APC discovery: No matching SNMP System Type Manager rule for sysObjID was found.

[Bruce Langston]

I have recently implemented HP SIM 6 in my mostly HP environment and have mostly good results with HP c-Class blades, DLs and EVAs.

We have about 20 APC PDUs (AP79xx) and an APC NetBotz 200 environmental monitor. I am trying to discover them and achieving success only with the NetBotz. All 21 devices have the same credentials and community string.

I have compiled and registered the powernet401 MIB.

HP SIM successfully discovers only the NetBotz. The PDUs all have the same result:

********* 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.


********* 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: The System Management Homepage is not installed on this system. It
may not be supported.
* 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: The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* 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...
* Running SNMP subtypes identification...
* No additional subtype(s) found from 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 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.
* Resolving DNS names...
Normal: The DNS 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...
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.

Bruce

[BPE]

Hi Bruce

Don't worry about the major status.
As you mention this is an APC product not HP.
In this case there is no HP Serial and Product number available. If you can get the trap in case of battery problems or power fail the setup is ok. We used the test function on the APC UPS and got the event inside SIM.

If you do not like the system type for the devices you can configure your own name under
Options ->Managed System Type...

bpe

[Bruce Langston]

Beep,

Thanks for the comment. Though I've been aware and, marginally, a user, of HP SIM and Compaq Insight Manager for many years, this is my first really production-level implementation. I'm still getting comfortable with the newer capabilities.

I'm, respectfully, hesitant to accept your explanation of this because, as I indicated, this MIB is delivering results for NetBotz monitor. The PDUs and the NetBotz are mature enough that I would expect them to work similarly for basic functions.

Maybe that's one of things I have to learn about HP SIM: you have to settle for what you can get.

I guess I can wait for something to happen or make something happen on one of the PDUs and see whether it notifies HP SIM.

Bruce

[Bruce Langston]

I htink the key indicators, buried in the original post are
* 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.
Sending a test trap works for the NetBotz but from the PDUs.

Anybody else have more success than this monitoring APC PDUs with HP SIM?

[Bruce Langston]

all right... I'm not giving up on this yet. I'm trying bpe's suggestion that I use the System Type Manager to create a rule that works for these APC PDUs.

I know who to use a MIB and, as I mentioned above, I'm using Getif to walk the MIBs I'm using with HP SIM.

I have the powernet401 MIB for APC.

I've created a few rules with Manage System Types. I have to say this is not a very intuitive process. With all the "Retrieve from system...," "Retrieve from MIB...," "Retrieve from system..." again, it's very confusing.

Then, the "Compare rule:"

I'm trying to get comfortable with using HP SIM to manage things other than my HP products. As I mentioned before, I have about 20 APC PDUs, three different models (AP7902, AP7932, AP7941). I used a MIB walker to find the right Object Identifier (1.3.6.1.4.1.318.1.3.4.5). I plugged that OI into the "object identifier" field under "Retrieve from system:," pluged in the community string and the IP address and clicked "Get response."
I did that for one of each APC model and it retrieved the right model number.
I created rules for each of them, but they all get discovered as AP7932. When I delete that rule they all get discovered as AP7902.

Is there a tutorial or explanation of how this is meant to work? The help is no help.

I attached a screenshot of my APC rules. I would appreciate some help, suggestions, probing questions, etc.

Bruce