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

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

I think that would be OK, but where are the counters
kept to survive a restart?

Bert

> -----Original Message-----
> From: Nagi Reddy Jonnala (njonnala) [mailto:njonnala@cisco.com]
> Sent: Sunday, March 19, 2006 22:34
> To: Wijnen, Bert (Bert); stefaan.de_cnodder@alcatel.be
> Cc: radiusext@ops.ietf.org; Dan Romascanu (E-mail)
> Subject: MIB Counters discontinuity (Was RE: radius dynauth
> client/server mibs structure)
> 
> 
> Bert,
> 
> > Mmm... the "wraps from the max value to zero" is redundant, 
> > because that is the behaviour of every Counter32 and 
> > Counter64. That is already specified in RFC2578.
> > W.r.t "is reset upon system (re)initialization", that is not 
> > exactly waht we wanted either. I do not know what you mean 
> > with "reset".
> > It is not REQUIRED that counter reset to sero (if that is 
> > what you mean).
> > They MAY do so, butnot required.
> > I think what you want to write is:
> > 
> >    This counter will only experience a discuntinuity when the system
> >    (re)starts as indicated by the value of sysUpTime.
> > 
> 
> Do you think mentioning "may" in the sentence is appropriate.
> 
>  "This counter may experience a discontinuity when the system 
> (re)starts
> as indicated by the value of sysUpTime." 
> 
> 
> Thanks
> Nagi.
> 

--
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/>