Thanks Dave. I will have a look in to Disman implementation too.

DS>How would you handle monitoring an initially valid OID that was
DS>subsequently deleted?   Or creating the value being monitored as
DS>part of the same request as the monitoring entry?

DS>The DisMan approach is to allow the creation of a monitoring entry
DS>for such a "missing" value, but have a suitable status column
DS>in the table.   That provides a somewhat more flexible mechanism,
DS>and removes this sort of validation problem.

If the OID is valid initially and then deleted subsequently, we can
handle it in the polling part. I have a status column in the table for
each entry. If it is not accessible, I change the status to
"TEMP_UNAVAILABLE". But continue polling, and when ever I get back to
the entry, I change the status back to "VALID".

But initial creation of the entry is bit different. It would have been
better, in the initial phase itself, to tell to the user that "OID is
not valid" when ever he sets it, rather than during polling set the
status of the entry to "invalid/temp-unavailable".


Regards,
Geo



-----Original Message-----
From: Dave Shield [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 20, 2005 4:39 AM
To: George, Geo
Cc: net-snmp-users@lists.sourceforge.net
Subject: RE: snmp_synch_response

On Fri, 2005-06-17 at 23:19, George, Geo wrote:
> I need to monitor a user selected SNMP OID periodically.

Have you considered using the DISMAN-EVENT-MIB, which is
specifically designed for this very purpose?
  It's already implemented in the Net-SNMP agent.  See the
snmpd.conf(5) man page, under
      DISMAN-EVENT-MIB SUPPORT

>                                                 So when the
> user inputs an OID ....... I need to check whether the
> OID is valid (i.e. whether the agent can read it).

How would you handle monitoring an initially valid OID that was
subsequently deleted?   Or creating the value being monitored as
part of the same request as the monitoring entry?

The DisMan approach is to allow the creation of a monitoring entry
for such a "missing" value, but have a suitable status column
in the table.   That provides a somewhat more flexible mechanism,
and removes this sort of validation problem.

Dave



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to