Dave,
See my responses below...
>> I am using monitor to "keep an eye on" some parameters in a mib. I have
>> found that objects which are not being monitored are still being accessed by
>> snmpd (as if a get command was issued).> What objects are being accessed? The object being accessed (1.3.6.1.4.1.33302.10.4.15) is from one of our enterprise MIBs. I have attached the MIB for reference. >> I commented out all the monitor >> lines (in snmpd.conf)and the problem persisted. Next I commented out the >> notificationEvent lines (in snmpd.conf) and that seemed to fix the problem. > What are the contents of the snmpd.conf file? I have attached the snmpd.conf file. If you have a look in the snmpd.conf file you will see two lines commented out: #notificationEvent NotifyDownstreamNetworkId 1.3.6.1.4.1.33302.10.10.24 -m # monitor -S -r 5 -e NotifyDownstreamNetworkId "Downstream network ID changed." != 1.3.6.1.4.1.33302.10.4.15 Even though they are commented out the 1.3.6.1.4.1.33302.10.4.15 object is still being accessed. >> There are no notificationEvents linked to the particular object I am having >> the problem with. > Which is.... 1.3.6.1.4.1.33302.10.4.15 Richard.
JR900.mib
Description: JR900.mib
snmpd.conf
Description: snmpd.conf
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
