On Mon, 2005-06-20 at 15:32, George, Geo wrote:
> 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?


> 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".

Yup - that's sort of how DisMan handles things.


> 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".

Except that this assumes that "no valid at point X" is the same as
"not valid at all".  If there was a temporary blip at the point when
the monitoring entry was created, then the creation request would fail.
Even if the OID to be monitored became available again a second later.

Don't get me wrong - I can see the thinking behind your approach.
But it feels a bit more flexible for the management application to
make this sort of decision - create the monitoring entry, watch the
status object for two or three polling cycles, then delete the entry
if things seem to be consistently failing.

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_id=7477&alloc_id=16492&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