2009/5/27 Richard Gipps <[email protected]>:
> 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.
Given that all of the MIB objects being monitored appear to be scalars,
I'd start by converting all of the "monitor" lines to use exact instances.
I.e
monitor -i -S -r 5 -e NotifyEncryption "Encryption
enabled/disabled." != 1.3.6.1.4.1.33302.10.4.14.0
instead of
monitor -S -r 5 -e NotifyEncryption "Encryption enabled/disabled."
!= 1.3.6.1.4.1.33302.10.4.14
I suspect that what's happening is that the internal "snmpwalk" of ...10.4.14
(for the wildcarded monitor directive) is rolling over and picking up
the ....10.4.15.0
instance
That value then gets discarded ('cos it's not relevant to the monitored
object), but it would explain why you're seeing the current behaviour.
Dave
------------------------------------------------------------------------------
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
