Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap (457 Views)
Reply
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 1 of 11 (608 Views)
Accepted Solution

HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Dear Admins,

I'm deploying AEG B.1000 pro, & C.1000 UPS with SNMP Adapter. The issue is HP Openview NNMi can only

receive "Agent Up with Possible Changes(coldStart Trap)",which is SNMPColdStart trap OID.1.3.6.1.6.3.1.1.5.1, but can't receive the UPS status snmp trap.
I have uploaded the  "RFC168cs121.MIB" coming with the AEG SNMP Adapter CD,but it seems not function.


From the "HPOpenview_KonfigurationCS121.doc" with the SNMP Adapter,there are some reference for NNM7.5 and lower version,can't use for NNMi9. The document point to "Do not change any existing NNM file in this directory CONF, create a file ALLOW_ALL with the following entry:  After this restart HP OV services – or start from commandline “xnmevents –events” - FINISH", and "Execute from a commandline : “xnmevents -replace ups_trapd.conf“.

these should be very important reference,but i don't know how to configure it at NNMi9.


Attached the pictures and snmp adpter doc for your review,thanks in advance for your kindly support!

Highly appreciate your kindly reference, how to configure it on HP NNMi9?


Brgds and Many thanks!

Please use plain text.
Honored Contributor
AndyKemp
Posts: 712
Registered: ‎05-17-2010
Message 2 of 11 (580 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

[ Edited ]

After you load the MIB, you have to load the events (aka traps) and then enable them for your system to accept them.

 

Navigate to the configuration workspace, MIBS, Loaded MIBs. Then go to the top menu bar, tools - load/unload mibs.

Find your mib and then select the "Load Incident Configuration" on the far right hand side.  You then have to go to Configuration-Incidents-SNMP Trap Configuration, locate the loaded traps and enable them.

Have a nice day :)

Andy Kemp,  CISSP
Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 3 of 11 (566 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Great guild, i did not enable it! Thks very much!

 

But it seemed still not incoming UPS traps,i'm trying to do more test.

 

Do any otherthings i should pay attention to?

 

Thks again for your great reference,that's very important for me!

Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 4 of 11 (561 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Hi ,

 

How to check if the HPOV NNMi received the trap? Is it only the enabled events can receive?

How to know if the UPS SNMP adapter has sent the trap?

I have enabled the ups snmp trap and assign to UPS group,still can't see any UPS trap in.

Attached picture for your review.

 

Brgds and Thanks!

Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 5 of 11 (544 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Hi ,

 

Below traps blocked,include the two kind of the enabled UPS traps:
1. such as ".1.3.6.1.4.1.1356.0.7", the correct ups traps from UPSMAN.mib,"testStarted - .1.3.6.1.4.1.1356.0.7"
2. incorrect ups traps,such as ".1.3.6.1.2.1.33.2.2",the traps less ".0" from the UPS-MIB.mib,"upsTrapTestCompleted - .1.3.6.1.2.1.33.2.0.2"
Other wks traps working fine,only the UPS traps blocked and changed.

What's the matter? Should be somewhere i don't know,and how to modify the trap? Need your professional guild,thanks a lot!


-------------------
D:\openview\bin>nnmtrapconfig.ovpl -dumpBlockList -u -p
Filter Configuration:
List of allowed trap OIDs:
.1.3.6.1.4.1.9.9.106.2.0.1
.1.3.6.1.4.1.8083.1.1.12.3.24
.1.3.6.1.4.1.1356.0.22
.1.3.6.1.4.1.8083.1.1.12.3.23
.1.3.6.1.4.1.8083.1.1.12.3.22
.1.3.6.1.4.1.8083.1.1.12.3.21
.1.3.6.1.4.1.8083.1.1.12.3.20
.1.3.6.1.4.1.2272.1.21.0.21
.1.3.6.1.4.1.1356.0.2
.1.3.6.1.4.1.9.9.176.2.0.1
.1.3.6.1.4.1.881.4.3.6.2.0.1
.1.3.6.1.4.1.9.9.221.0.1
.1.3.6.1.4.1.9.9.176.2.0.2
.1.3.6.1.4.1.8083.1.1.12.3.29
.1.3.6.1.4.1.881.4.3.6.2.0.4
.1.3.6.1.4.1.1356.0.6
.1.3.6.1.4.1.8083.1.1.12.3.28
.1.3.6.1.4.1.881.4.3.6.2.0.5
.1.3.6.1.4.1.1356.0.26
.1.3.6.1.4.1.8083.1.1.12.3.27
.1.3.6.1.4.1.8083.1.1.12.3.26
.1.3.6.1.4.1.1356.0.3
.1.3.6.1.4.1.8083.1.1.12.3.25
.1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.311.1.1.3.1.1
.1.3.6.1.4.1.2272.1.21.7
.1.3.6.1.4.1.2272.1.21.6
.1.3.6.1.4.1.8083.1.1.12.3.11
.1.3.6.1.4.1.8083.1.1.12.3.10
.1.3.6.1.4.1.1356.0.10
.1.3.6.1.4.1.2272.1.21.21
.1.3.6.1.4.1.8083.1.1.12.3.13
.1.3.6.1.4.1.1356.0.11
.1.3.6.1.4.1.8083.1.1.12.3.12
.1.3.6.1.4.1.881.4.3.9.2.0.1
.1.3.6.1.4.1.1356.0.16
.1.3.6.1.4.1.8083.1.1.12.3.19
.1.3.6.1.4.1.1356.0.17
.1.3.6.1.4.1.8083.1.1.12.3.18
.1.3.6.1.4.1.1356.0.18
.1.3.6.1.4.1.1356.0.12
.1.3.6.1.4.1.8083.1.1.12.3.15
.1.3.6.1.4.1.1356.0.13
.1.3.6.1.4.1.8083.1.1.12.3.14
.1.3.6.1.4.1.1356.0.14
.1.3.6.1.4.1.8083.1.1.12.3.17
.1.3.6.1.4.1.1356.0.15
.1.3.6.1.4.1.8083.1.1.12.3.16
.1.3.6.1.4.1.1356.0.7
.1.3.6.1.4.1.1356.0.8
.1.3.6.1.4.1.1356.0.9
.1.3.6.1.4.1.881.4.3.2.2.0.1
.1.3.6.1.4.1.881.4.3.2.2.0.6
.1.3.6.1.4.1.881.4.3.2.2.0.7
.1.3.6.1.4.1.881.4.3.2.2.0.8
.1.3.6.1.4.1.881.4.3.2.2.0.2
.1.3.6.1.2.1.33.2.3
.1.3.6.1.4.1.881.4.3.2.2.0.3
.1.3.6.1.2.1.33.2.4
.1.3.6.1.4.1.881.4.3.2.2.0.4
.1.3.6.1.4.1.881.4.3.2.2.0.5
.1.3.6.1.4.1.2272.1.21.14
.1.3.6.1.4.1.2272.1.21.0.42
.1.3.6.1.4.1.2272.1.21.17
.1.3.6.1.4.1.2272.1.21.0.41
.1.3.6.1.4.1.2272.1.21.13
.1.3.6.1.4.1.8083.1.1.12.3.49
.1.3.6.1.4.1.8083.1.1.12.3.48
.1.3.6.1.4.1.8083.1.1.12.3.47
.1.3.6.1.4.1.2272.1.21.18
.1.3.6.1.4.1.881.4.3.4.2.0.1
.1.3.6.1.4.1.881.4.3.4.2.0.2
.1.3.6.1.4.1.881.4.3.4.2.0.3
.1.3.6.1.4.1.881.4.3.4.2.0.4
.1.3.6.1.4.1.881.4.3.9.4.0.2
.1.3.6.1.4.1.881.4.3.9.4.0.1
.1.3.6.1.4.1.8083.1.1.12.3.31
.1.3.6.1.4.1.8083.1.1.12.3.30
.1.3.6.1.4.1.8083.1.1.12.3.33
.1.3.6.1.2.1.68.0.1
.1.3.6.1.4.1.8083.1.1.12.3.32
.1.3.6.1.4.1.8083.1.1.12.3.34
.1.3.6.1.4.1.881.4.3.6.2.0.7
.1.3.6.1.4.1.881.4.3.6.2.0.6
.1.3.6.1.4.1.9.5.0.4
.1.3.6.1.6.3.1.1.5.1
.1.3.6.1.6.3.1.1.5.2
.1.3.6.1.6.3.1.1.5.3
.1.3.6.1.4.1.9.5.0.3
.1.3.6.1.6.3.1.1.5.4
.1.3.6.1.4.1.881.4.3.5.2.0.3
.1.3.6.1.4.1.141.50.2.0.3
.1.3.6.1.4.1.881.4.3.5.2.0.2
.1.3.6.1.4.1.881.4.3.5.2.0.1
.1.3.6.1.4.1.9.9.13.3.0.9
.1.3.6.1.6.3.1.1.5.1.1.3.6.1.4.1.311.1.1.3.1.1
.1.3.6.1.4.1.141.50.2.0.1
.1.3.6.1.4.1.8083.1.1.12.3.2
.1.3.6.1.4.1.8083.1.1.12.3.4
.1.3.6.1.4.1.8083.1.1.12.3.3
.1.3.6.1.4.1.8083.1.1.12.3.5
.1.3.6.1.4.1.8083.1.1.12.3.6
.1.3.6.1.4.1.8083.1.1.12.3.7
.1.3.6.1.4.1.8083.1.1.12.3.8
.1.3.6.1.4.1.8083.1.1.12.3.9
.1.3.6.1.4.1.1978.8.1.2.0.1
.1.3.6.1.4.1.9.9.13.3.0.7
.1.3.6.1.4.1.9.9.13.3.0.8
.1.3.6.1.4.1.9.9.13.3.0.5
.1.3.6.1.4.1.9.9.13.3.0.6
.1.3.6.1.4.1.9.9.13.3.0.3
.1.3.6.1.4.1.9.9.13.3.0.4
.1.3.6.1.4.1.9.9.13.3.0.2
.1.3.6.1.4.1.9.9.117.2.0.5
.1.3.6.1.4.1.2272.1.21.0.7
.1.3.6.1.4.1.881.4.3.3.2.0.1
.1.3.6.1.4.1.881.4.3.3.2.0.2
.1.3.6.1.4.1.9.9.117.2.0.1
.1.3.6.1.4.1.881.4.3.3.2.0.3
.1.3.6.1.4.1.9.9.117.2.0.4
.1.3.6.1.4.1.2272.1.21.0.6
.1.3.6.1.4.1.881.4.3.3.2.0.4
.1.3.6.1.4.1.9.9.117.2.0.3
.1.3.6.1.4.1.881.4.3.3.2.0.5
.1.3.6.1.4.1.881.4.3.3.2.0.6
.1.3.6.1.6.3.1.1.5.1.1.3.6.1.4.1.9
.1.3.6.1.2.1.33.2.0.2
.1.3.6.1.2.1.33.2.0.3
.1.3.6.1.4.1.8083.1.1.12.3.58
.1.3.6.1.2.1.33.2.0.1
.1.3.6.1.4.1.8083.1.1.12.3.56
.1.3.6.1.6.3.1.1.5.2.1.3.6.1.4.1.9
.1.3.6.1.4.1.8083.1.1.12.3.57
.1.3.6.1.4.1.8083.1.1.12.3.54
.1.3.6.1.4.1.8083.1.1.12.3.55
.1.3.6.1.4.1.8083.1.1.12.3.52
.1.3.6.1.4.1.8083.1.1.12.3.53
.1.3.6.1.4.1.8083.1.1.12.3.50
.1.3.6.1.4.1.8083.1.1.12.3.51
.1.3.6.1.4.1.11.15.1.4.0.1
.1.3.6.1.2.1.33.2.0.4
.1.3.6.1.4.1.881.4.3.1.2.0.1
.1.3.6.1.4.1.881.4.3.1.2.0.2
.1.3.6.1.4.1.881.4.3.1.2.0.5
.1.3.6.1.4.1.881.4.3.1.2.0.6
.1.3.6.1.4.1.881.4.3.1.2.0.3
.1.3.6.1.4.1.881.4.3.1.2.0.4
.1.3.6.1.4.1.881.4.3.1.2.0.9
.1.3.6.1.4.1.881.4.3.1.2.0.7
.1.3.6.1.4.1.881.4.3.1.2.0.8
.1.3.6.1.4.1.11.15.1.4.1
.1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.9
.1.3.6.1.4.1.881.4.3.3.2.0.1001
.1.3.6.1.4.1.881.4.3.1.2.0.10
.1.3.6.1.4.1.2272.1.21.0.17
.1.3.6.1.4.1.2272.1.21.41
.1.3.6.1.4.1.2272.1.21.42
.1.3.6.1.4.1.2272.1.21.0.18
.1.3.6.1.4.1.2272.1.21.0.13
.1.3.6.1.4.1.2272.1.21.0.14
.1.3.6.1.6.3.1.1.5.3.1.3.6.1.4.1.9
.1.3.6.1.2.1.46.1.3.0.1

List of disallowed/disabled trap OIDs:
.1.3.6.1.4.1.1356.0.21
.1.3.6.1.2.1.17.0.2
.1.3.6.1.2.1.14.16.2.2
.1.3.6.1.4.1.1356.0.20
.1.3.6.1.2.1.14.16.2.1
.1.3.6.1.4.1.1356.0.29
.1.3.6.1.4.1.1356.0.1
.1.3.6.1.4.1.1356.0.27
.1.3.6.1.4.1.1356.0.28
.1.3.6.1.4.1.1356.0.25
.1.3.6.1.4.1.8083.1.1.12.3.1
.1.3.6.1.4.1.1356.0.5
.1.3.6.1.4.1.1356.0.4
.1.3.6.1.4.1.1356.0.23
.1.3.6.1.4.1.881.4.3.6.2.0.2
.1.3.6.1.4.1.1356.0.24
.1.3.6.1.4.1.881.4.3.6.2.0.3
.1.3.6.1.4.1.9.9.26.2.0.3
.1.3.6.1.4.1.1356.0.19
.1.3.6.1.6.3.1.1.5.5.1.3.6.1.4.1.311.1.1.3.1.2
.1.3.6.1.4.1.1978.17.2.0.1
.1.3.6.1.4.1.1978.17.2.0.2
.1.3.6.1.4.1.1978.17.2.0.5
.1.3.6.1.4.1.1978.17.2.0.6
.1.3.6.1.4.1.1978.17.2.0.3
.1.3.6.1.4.1.1978.17.2.0.1001
.1.3.6.1.4.1.1978.17.2.0.4
.1.3.6.1.4.1.1978.17.2.0.9
.1.3.6.1.4.1.1978.17.2.0.7
.1.3.6.1.4.1.1978.17.2.0.8
.1.3.6.1.6.3.1.1.5.5.1.3.6.1.4.1.311.1.1.3.1.3
.1.3.6.1.4.1.8083.1.1.12.3.42
.1.3.6.1.4.1.8083.1.1.12.3.41
.1.3.6.1.4.1.8083.1.1.12.3.40
.1.3.6.1.4.1.8083.1.1.12.3.46
.1.3.6.1.4.1.8083.1.1.12.3.45
.1.3.6.1.4.1.8083.1.1.12.3.44
.1.3.6.1.4.1.8083.1.1.12.3.43
.1.3.6.1.2.1.14.16.2.16
.1.3.6.1.4.1.9.9.41.2.0.1
.1.3.6.1.4.1.9.5.11.2.0.2
.1.3.6.1.2.1.15.0.2
.1.3.6.1.2.1.15.0.1
.1.3.6.1.4.1.9.9.46.2.0.7
.1.3.6.1.4.1.1978.17.2.0.13
.1.3.6.1.4.1.1978.17.2.0.12
.1.3.6.1.4.1.1978.17.2.0.15
.1.3.6.1.4.1.8083.1.1.12.3.35
.1.3.6.1.4.1.1978.17.2.0.14
.1.3.6.1.4.1.8083.1.1.12.3.37
.1.3.6.1.4.1.8083.1.1.12.3.36
.1.3.6.1.4.1.11937.0.1
.1.3.6.1.4.1.8083.1.1.12.3.39
.1.3.6.1.4.1.8083.1.1.12.3.38
.1.3.6.1.2.1.16.0.1
.1.3.6.1.2.1.16.0.2
.1.3.6.1.4.1.9.5.0.6
.1.3.6.1.4.1.881.4.3.6.2.0.8
.1.3.6.1.6.3.1.1.5.5
.1.3.6.1.2.1.17.0.1
.1.3.6.1.4.1.1978.17.2.0.10
.1.3.6.1.4.1.1978.17.2.0.11
.1.3.6.1.4.1.9.5.0.5



Blocking Caches:
Cache of blocked OIDs:
.1.3.6.1.4.1.881.4.3.4.2.7443184.0.1
.1.3.6.1.4.1.9.9.91.2.0.1
.1.3.6.1.4.1.881.4.3.4.2.7446064.0.1
.1.3.6.1.4.1.881.4.3.4.2.51663048.0.1
.1.3.6.1.4.1.881.4.3.4.2.7443968.0.1
.1.3.6.1.4.1.881.4.3.4.2.7445984.0.1
.1.3.6.1.4.1.881.4.3.6.2.0.14
.1.3.6.1.4.1.881.4.3.4.2.51684424.0.1
.1.3.6.1.4.1.881.4.3.4.2.51663784.0.1
.1.3.6.1.4.1.881.4.3.4.2.7446168.0.1
.1.3.6.1.4.1.9.9.118.0.2
.1.3.6.1.4.1.881.4.3.4.2.51654648.0.1
.1.3.6.1.4.1.881.4.3.4.2.7443904.0.1
.1.3.6.1.4.1.881.4.3.4.2.7446032.0.1

Please use plain text.
Honored Contributor
AndyKemp
Posts: 712
Registered: ‎05-17-2010
Message 6 of 11 (520 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Use  nnmtrapconfig.ovpl to clear the list of blocked OIDs.

 

NNMi out of the box will only accept and display SNMP notifications that are enabled and are sourced from a managed node AND object (interface or component)

 

So you need to ensure you added the UPS into the inventory, its SNMP reachable and you get a green ball on the object thats the source of the trap.

Have a nice day :)

Andy Kemp,  CISSP
Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 7 of 11 (507 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Dear AndyKemp,

 

The traps issue solved due to follow your guide,and the wrong MIB files.Thks very much!

 

Now another new matter need your reference:


There are only 4 SNMP traps from mid module RFC1628cs121.MIB,which loaded into HP NNMi9:
The following traps were added to incident configuration:
upsTrapAlarmEntryRemoved - .1.3.6.1.2.1.33.2.4
upsTrapAlarmEntryAdded - .1.3.6.1.2.1.33.2.3
upsTrapTestCompleted - .1.3.6.1.2.1.33.2.2
upsTrapOnBattery - .1.3.6.1.2.1.33.2.1

In case of any issues of UPS,HP NNMi has already configured to send e-mail alert upon the 4 upsTraps.I know about how to send the e-mail alert,but i don't know to dealwith the variables coming with UPS traps.Because only send message of "upsTrapAlarmEntryRemoved,or Added" meaning nothing,nobody can read about it.
Could you pls show me,or some reference on how to use the variables,espically "upsAlarmDescr"?
Highly appreciate for your kindly support!
 
--------------------quote,instruction of upsTrapAlarmEntryRemoved trap-------------------------
This trap is sent each time an alarm is removed from the alarm table. It is sent on the removal of all alarms except for
upsAlarmTestInProgress.
Variables:
1: upsAlarmId
Syntax: TEXTUAL_CONVENTION
Description: A unique identifier for an alarm condition. This value must remain constant.
2: upsAlarmDescr
Syntax: TEXTUAL_CONVENTION
Description: A reference to an alarm description object. The object referenced should not be accessible, but rather be used to provide a unique description of the alarm condition.
-------------------unquote-----------------------------------------------------------

Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 8 of 11 (496 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Dear AndyKemp,

 

From the CS121-SNMP adapter manual for HP NNM7.5,there are some reference for the UPS traps:

----quote-----

"UPS_TRAPD.CONF" ,this is the CS121 RFC 1628 TRAP configuration file.

This file is copied into <HP Openview Path>/BIN/.

After the copy process the file will be registered at HP OV by “xnmevents –replace upstrapd.conf”

----unquote----

 

How should i do in NNMi9.10 ? It seemed none "xnmevents" command.

 

Attached the cs121-snmp files for your review,thks!

 

 

Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 9 of 11 (468 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Dear AndyKemp,

 

From the CS121-SNMP adapter manual for HP NNM7.5,there are some reference for the UPS traps:

----quote-----

"UPS_TRAPD.CONF" ,this is the CS121 RFC 1628 TRAP configuration file.

This file is copied into <HP Openview Path>/BIN/.

After the copy process the file will be registered at HP OV by “xnmevents –replace upstrapd.conf”

----unquote----

 

How should i do in NNMi9.10 ? It seemed none "xnmevents" command.

Please use plain text.
Honored Contributor
AndyKemp
Posts: 712
Registered: ‎05-17-2010
Message 10 of 11 (461 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Apples and oranges.  7.5 and modern versions use different files and processes to accomplish simlar functions.    MIBS and notifications are now stored in the database, not trapd.conf.

 

 

You ahve to laod the MIB into the database, then you have to load the traps/notifications, then you have to enable the ones you want to see.  Thats the process of the current version of NNMi.

Have a nice day :)

Andy Kemp,  CISSP
Please use plain text.
Occasional Advisor
todaybusiness
Posts: 11
Registered: ‎10-20-2013
Message 11 of 11 (457 Views)

Re: HP NNMi9.10.9.11.004 can't receive UPS snmp trap

Dear AndyKemp,

 

Thks a lot for your kindly reference!
 
There are some information come from the SNMP adapter company,but i really don't know how to get the binding information,in the other word,i don't know to to use the variables,could you pls show me one example?


There are only 4 SNMP traps from mid module RFC1628cs121.MIB,which loaded into HP NNMi9:
The following traps were added to incident configuration:
upsTrapAlarmEntryRemoved - .1.3.6.1.2.1.33.2.4
upsTrapAlarmEntryAdded - .1.3.6.1.2.1.33.2.3
upsTrapTestCompleted - .1.3.6.1.2.1.33.2.2
upsTrapOnBattery - .1.3.6.1.2.1.33.2.1

In case of any issues of UPS,HP NNMi has already configured to send e-mail alert upon the 4 upsTraps.I know about how to send the e-mail alert,but i don't know to dealwith the variables coming with UPS traps.Because only send message of "upsTrapAlarmEntryRemoved,or Added" meaning nothing,nobody can read about it.
Could you pls show me,or some reference on how to use the variables,espically "upsAlarmDescr"?
Highly appreciate for your kindly support!
 
--------------------quote,instruction of upsTrapAlarmEntryRemoved trap-------------------------
This trap is sent each time an alarm is removed from the alarm table. It is sent on the removal of all alarms except for
upsAlarmTestInProgress.
Variables:
1: upsAlarmId
Syntax: TEXTUAL_CONVENTION
Description: A unique identifier for an alarm condition. This value must remain constant.
2: upsAlarmDescr
Syntax: TEXTUAL_CONVENTION
Description: A reference to an alarm description object. The object referenced should not be accessible, but rather be used to provide a unique description of the alarm condition.
-------------------unquote-----------------------------------------------------------

 

----quote----

The following alarms will be send as SNMP trap automatically:

1.3.6.1.2.1.33.2 upsTraps
1.3.6.1.2.1.33.2.1 upsTrapOnBattery
1.3.6.1.2.1.33.2.2 upsTrapTestCompleted
1.3.6.1.2.1.33.2.3 upsTrapAlarmEntryAdded
1.3.6.1.2.1.33.2.4 upsTrapAlarmEntryRemoved

The SNMP traps contain the following bindings:

1.3.6.1.2.1.33.1.6 upsAlarm
1.3.6.1.2.1.33.1.6.1 upsAlarmsPresent
1.3.6.1.2.1.33.1.6.2 upsAlarmTable
1.3.6.1.2.1.33.1.6.2.1 upsAlarmEntry
1.3.6.1.2.1.33.1.6.2.1.1 upsAlarmId
1.3.6.1.2.1.33.1.6.2.1.2 upsAlarmDescr
1.3.6.1.2.1.33.1.6.2.1.3 upsAlarmTime
1.3.6.1.2.1.33.1.6.3 upsWellKnownAlarms
1.3.6.1.2.1.33.1.6.3.1 upsAlarmBatteryBad
1.3.6.1.2.1.33.1.6.3.2 upsAlarmOnBattery
1.3.6.1.2.1.33.1.6.3.3 upsAlarmLowBattery
1.3.6.1.2.1.33.1.6.3.4 upsAlarmDepletedBattery
1.3.6.1.2.1.33.1.6.3.5 upsAlarmTempBad
1.3.6.1.2.1.33.1.6.3.6 upsAlarmInputBad
1.3.6.1.2.1.33.1.6.3.7 upsAlarmOutputBad
1.3.6.1.2.1.33.1.6.3.8 upsAlarmOutputOverload
1.3.6.1.2.1.33.1.6.3.9 upsAlarmOnBypass
1.3.6.1.2.1.33.1.6.3.10 upsAlarmBypassBad
1.3.6.1.2.1.33.1.6.3.11 upsAlarmOutputOffAsRequested
1.3.6.1.2.1.33.1.6.3.12 upsAlarmUpsOffAsRequested
1.3.6.1.2.1.33.1.6.3.13 upsAlarmChargerFailed
1.3.6.1.2.1.33.1.6.3.14 upsAlarmUpsOutputOff
1.3.6.1.2.1.33.1.6.3.15 upsAlarmUpsSystemOff
1.3.6.1.2.1.33.1.6.3.16 upsAlarmFanFailure
1.3.6.1.2.1.33.1.6.3.17 upsAlarmFuseFailure
1.3.6.1.2.1.33.1.6.3.18 upsAlarmGeneralFault
1.3.6.1.2.1.33.1.6.3.19 upsAlarmDiagnosticTestFailed
1.3.6.1.2.1.33.1.6.3.20 upsAlarmCommunicationsLost
1.3.6.1.2.1.33.1.6.3.21 upsAlarmAwaitingPower
1.3.6.1.2.1.33.1.6.3.22 upsAlarmShutdownPending
1.3.6.1.2.1.33.1.6.3.23 upsAlarmShutdownImminent
1.3.6.1.2.1.33.1.6.3.24 upsAlarmTestInProgress
1.3.6.1.2.1.33.1.6.3.25 upsAlarmAuxInput
1 1.3.6.1.2.1.33.1.6.3.26 upsAlarmAuxInput2
1.3.6.1.2.1.33.1.6.3.27 upsAlarmAuxInput3
1.3.6.1.2.1.33.1.6.3.28 upsAlarmAuxInput4

----unquote------

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