I configured DismanEventMIB by using "monitor" directive in "snmpd.conf". And I am able to get the traps. If I want to turn off some traps from the application instead of changing "snmpd.conf" file, is it possible? Like disabling mteTriggerEventEntryStatus
or mteTriggerEnabled for those trap instances?
Thanks.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Net-snmp-users mailing list
Net-snmp-users (AT) lists (DOT) sourceforge.net
Please see the following page to unsubscribe or change other options:

19/10/06, Jing Guan <jguan (AT) gmu (DOT) eduwrote:
If I want to turn off some traps from the application instead of changing
"snmpd.conf" file, is it possible? Like disabling mteTriggerEventEntryStatus
or mteTriggerEnabled for those trap instances?

In general, the only way you can use the EntryStatus column is to delete
a trigger entry. But if you've set up this entry using "monitor" then it's
effectively read-only, and so can't be deleted.
[I'm not sure whether this allows a SET to mteTriggerEnabled or not]

If you've set it up via SNMP SET. then you can either delete it using
mteTriggerEventEntryStatus, or disable it using mteTriggerEnabled.

Dave

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo

Net-snmp-users mailing list
Net-snmp-users (AT) lists (DOT) sourceforge.net
Please see the following page to unsubscribe or change other options: