Where to define SNMP traps for HP StorageWorks VA?

[Ralph Grothe]

Hi,

although I had written a cronjob that executes an armdsp -f every hour and parses the output for non-good FRU states, and which provides the result via send_nsca to my main Nagios server as a passive check result, I somehow feel this is a rather inadequate approach for a so-called managed device, irrespective that it has worked so far and quite reliably notified me of failed disks every now and then.

I am absolutely convinced that the VA has an intrinsic ability to emit SNMP traps on components' failure to some definable management host (in my case my Nagios server).

However, from sifting through the manpages of every arm* command and scouring docs.hp.com
I couldn't find any useful reference.

I assume there are quite a few users of an HP VA out there who possibly can point me to some doc or give me some hint to get me started.


Regards

Ralph

[Torsten.]

Some docs related to snmp based management of the VA, hope this helps:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00057439/c00057439.pdf

(HP Systems Insight Manager)

ftp://ftp.compaq.com/pub/products/storageworks/whitepapers/5982-2449EN.pdf

(HP OpenView Storage Area Manager)

Looks like the MIB is included in HP Systems Insight Manager - this is what you need I guess.

[Ralph Grothe]

Hi Torsten,

unfortunately a http get on your first url received a 404,
while for the second url our proxy returned that it fetched an empty doc.

Maybe your links have become stale?

Wasn't Compaq taken over by HP already some time ago?

[Torsten.]

These are google hits.
Just tested again, it is working for me.

BTW, there is some info in the commandview manual too (not too much),

"Event Reporting Software
The internal operation of the array is continually monitored and any significant
events are recorded. Command View SDM internal event reporting software
retrieves event information from the array and reports it to the user. The
software also retrieves data from the controller logs of the device and transmits
all significant/critical log notifications from the array and the disk devices to
all event listeners.
Command View SDM event software broadcasts these events to platform
dependent targets using SNMP applications with an SNMP agent to trap the
events. Command View SDM also stores these events to system log files.
Note Command View SDM does not support the SNMP set feature.
Device information cannot be configured from a remote host.
Event targets include the following. Note that integration into some of these
applications requires the use of the Enterprise Integrations software, which is
included with Command View SDM.

...

HP-UX
â Syslog
â HP EMS
â HP OpenView NNM (SNMP)
â HP Top Tools (SNMP)
â CA Unicenter TNG (SNMP)
â BMC Patrol (SNMP)
â Tivoli (SNMP)
â HP Systems Insight Manager 5.0
â Instant Support Enterprise Edition
Events are categorized as Information, Minor Warning, Major Warning,
Serious, and Critical. These events also provide descriptions useful for
troubleshooting. A current list of events is available from the HP web site:
http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm" (broken)

And BTW, it supports SMI-S.

[Torsten.]

"Wasn't Compaq taken over by HP already some time ago?"

Right, HP owns now this brand, the address space ...

This is for ftp.compaq.com

Registrant:
Hewlett-Packard Company
(DOM-89154)
3000 Hanover Road
Palo Alto
CA
94304
US

Domain Name: compaq.com

...
OrgName: Hewlett-Packard Company
OrgID: HP
Address: 3000 Hanover Street
City: Palo Alto
StateProv: CA
PostalCode: 94304
Country: US

NetRange: 161.114.0.0 - 161.114.255.255
CIDR: 161.114.0.0/16


and the "main" space

Hewlett-Packard 15.0.0.0 â 15.255.255.255
Hewlett-Packard (originally DEC, then Compaq) 16.0.0.0 â 16.255.255.255

http://en.wikipedia.org/wiki/List_of_assigned_/8_IP_address_blocks

;-)

[Torsten. · Accepted solution]

Back to the question ...

The VA is monitored by EMS, the module is the Remote Monitor (RemoteMonitor):

http://docs.hp.com/en/diag/ems/emd_rem.htm

You should have a look into the EMS configuration.

And of course it can be monitored by ISEE.

HTH!