Re: FddiTime
"Camelot..Camelot..it's only a model" <stefani@quiver.enet.dec.com> Tue, 28 July 1992 14:18 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa01973; 28 Jul 92 10:18 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa01969; 28 Jul 92 10:18 EDT
Received: from CS.UTK.EDU by NRI.Reston.VA.US id aa11083; 28 Jul 92 10:19 EDT
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA23283; Tue, 28 Jul 92 09:30:47 -0400
Received: from inet-gw-2.pa.dec.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA23279; Tue, 28 Jul 92 09:30:40 -0400
Received: by inet-gw-2.pa.dec.com; id AA16526; Tue, 28 Jul 92 06:30:22 -0700
Received: by us1rmc.bb.dec.com; id AA09872; Tue, 28 Jul 92 08:46:55 -0400
Message-Id: <9207281246.AA09872@us1rmc.bb.dec.com>
Received: from quiver.enet; by us1rmc.enet; Tue, 28 Jul 92 09:28:53 EDT
Date: Tue, 28 Jul 1992 09:28:53 -0400
From: "Camelot..Camelot..it's only a model" <stefani@quiver.enet.dec.com>
To: dan@lannet.com
Cc: fddi-mib@cs.utk.edu, anil@quiver.enet.dec.com, stefani@quiver.enet.dec.com
Apparently-To: fddi-mib@cs.utk.edu, dan@lannet.com
Subject: Re: FddiTime
Dan, There have been some replies on the list (I can forward them to you) regarding Anil's suggestion to change FDDItime in the SNMP MIB from 80 nanosecond units to 1 microsecond units. The arguments against being the desire for consistency between the SNMP and SMT MIBs with regards to units and that any kind of conversion for a more understandable display format should occur in the NMS. There was some concern that the signed 32 bit integer defined in SNMP would restrict the range of values supported by SMT's unsigned 32 bit integer definition and that the switch to 1 microsecond units would overcome this restriction. After doing some quick math I came up with 2.86 minutes as a max on a signed 32 bit integer in 80 nanosecond units. Looking over SMT 7.1, it looks like none of the MAC timers get even close to this value, which leaves PORTMACLoopTime and SMTTrace-MaxExpiration as possible points of contention. PORTMACLoopTime does have its range explicitly stated in SMT 7.1 (2500000..4294967295 in 80 nanosecond units), but its status is optional so it's likely to be dropped from the SNMP MIB. SMTTrace-MaxExpiration has a range greater than 6 seconds, but it's unlikely that a user would need to set the value between 2.56 and 5.12 minutes. This leaves us with the original argument of making it easier for simple NMS's and MIB compilers to return timer values in understandable units. - Larry Stefani Networks & Communications Digital Equipment Corporation
- Re: FddiTime dan
- Re: FddiTime Camelot..Camelot..it's only a model