RE: MIB Counters discontinuity (Was RE: radius dynauth client/server mibs structure)

["Nagi Reddy Jonnala \(njonnala\)" <njonnala@cisco.com>]

> > Juergen, Bert and all,
> > 
> > We have two options then. Please let us know which one 
> works for you.
> > 
> > 1. As Juergen suggested "This counter uses sysUpTime as the 
> > discontinuity indicator. Any discontinuity of this counter 
> must cause a
> > reset of 	sysUpTime."
> > 
> > 2. All we want to convey in the MIBs is that the counter might 
> > experience discontinuity when the respective (DAC or DAS) module is 
> > (re)started. Not sure if we need to draw any relation to 
> sysUpTime or 
> > some other object. Is implementing the sysUptime mandatory?
> 
> An SNMP agent without sysUptime (the default discontinuity 
> indicator for all counters) is kind of broken.

OK.

> 
> > If not, does the below work?
> > 
> > "This counter may experience discontinuity when the Dynamic 
> > Authorization Client (DAC) module is (re)started".
> 
> Why only the DAC module?

IMO, in theory, a DAC/DAS can be restarted regardless of the system
restart(or sysUpTime). A similar statement is applicable to DAS
Mib/module.

Thanks
Nagi.

> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> 

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>