| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Note 3.0 How to distinguish enterprise specific SNMP traps No replies DECPRG::PAVLUP 37 lines 12-JAN-1995 11:27 -------------------------------------------------------------------------------- I'd like to ask for an assistance from MCC gurus in a problem related to SNMP traps received by MCC station. I've got a customer who has SNMP monitored UPS boxes that also send traps when something goes wrong, etc. We have the traps received by MCC, notified in the notification window, that's fine. However, different events on the UPS boxes are distinguished by a number of EnterpriseSpecific trap received. And that's the point where I don't know how to continue. I get the trap, it is identified as EnterpriseSpecific, and in the details display I see the number of trap-type. It is required that different specific traps be notified in a different way in the window. I assume that a simple notification can't make it. Referring to 5149.3, I tried to make some rules that would fire after receiving the specific trap, but I did not succeed. 5149.3 suggests to write Occurrs rule against enterprise child entity to get variables from MIB, i.e. for example against "SNMP * DEC", or in our case against "SNMP * upsMIB". But even though it was possible to create a rule with an expression like SNMP * upsMIB any configuration event or SNMP * upsMIB any event I didn't make any of such rules fired (only rules against "SNMP *"). Does anyone have an experience how to distinguish enterprise specific traps, or what is the way how to achieve it? I'd appreciate any hint, comment or recommendation. Thanks in advance Petr.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6215.1 | Any hint??? | DECPRG::PAVLUP | Mon Feb 20 1995 16:52 | 4 | |
Could anyone spend few words, if the approach described is workable? Am I missing something? Or why it does not work...? Thanks Petr. | |||||
| 6215.2 | Some more info | DECPRG::PAVLUP | Tue Feb 21 1995 17:12 | 33 | |
Can anyone help me with the issues described here? I've got the upsMIB loaded in MCC V1.3 (OpenVMS). I've got a UPS in my lab now for testing. The UPS is claimed to implement the upsMIB (it is a VICTRON SNMP box attaching the UPS to network). When I register the UPS as an SNMP entity into MCC, it registers O.K. However, the entity does not show the upsMIB as a registered child. If I try to register the upsMIB subclass for the entity, I get a partial registration with a reason "No such entity". Can anyone tell me what is the most probable reason for this behaviour? The other problem is related to using notifications on enterprise specific traps generated by the UPS. I can create an appropriate notification (SNMP * upsMIB, any configuration event; or including specific trap name) but I'm not able to get the notification received in this way. The only technique that works is just a generic notification (SNMP *, any config event) which however does not allow to distinguish (in the notification window) different enterprise specific traps... This is almost of no use, as you can't distinguish an event of UPS going to batteries and coming back to external power... Can anyone tell me whether this situation might be a consequence of the not-full registration of upsMIB sublclass. Or at least, is this way of event capturing expected to work on VMS MCC (I found only note 4351 that refers to some similar problem but only on ULTRIX). Thanks for information and hints. Regards Petr. | |||||