Re: PerfHist-TC-MIB
Ken Chapman <KChapman@Argon.com> Thu, 11 June 1998 13:21 UTC
Delivery-Date: Thu, 11 Jun 1998 09:21:26 -0400
Return-Path: KChapman@Argon.com
Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA17619 for <ietf-archive@ietf.org>; Thu, 11 Jun 1998 09:21:22 -0400 (EDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id JAA17802 for <ietf-archive@cnri.reston.va.us>; Thu, 11 Jun 1998 09:23:44 -0400 (EDT)
Received: from proxy1.cisco.com (proxy1.cisco.com [192.31.7.88]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id GAA23617 for <trunk-mib@external.cisco.com>; Thu, 11 Jun 1998 06:14:35 -0700 (PDT)
Received: (from smap@localhost) by proxy1.cisco.com (8.8.7/8.8.5) id GAA27198 for <trunk-mib@external.cisco.com>; Thu, 11 Jun 1998 06:14:33 -0700 (PDT)
Received: from shultz.argon.com(208.234.161.2) by proxy1.cisco.com via smap (V2.0) id xma027191; Thu, 11 Jun 98 13:14:30 GMT
X-SMAP-Received-From: outside
Received: from aruba (aruba.argon.com [208.234.161.60]) by shultz.argon.com (8.8.6/8.8.6) with SMTP id JAA03644; Thu, 11 Jun 1998 09:02:21 -0400 (EDT)
Message-Id: <3.0.32.19980611090207.009db940@shultz.argon.com>
X-Sender: kchapman@shultz.argon.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 11 Jun 1998 09:02:13 -0400
To: Jeff Johnson <jeff@redbacknetworks.com>, atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
From: Ken Chapman <KChapman@Argon.com>
Subject: Re: PerfHist-TC-MIB
Mime-Version: 1.0
Content-Type: text/enriched; charset="us-ascii"
At 04:15 PM 6/2/98 -0700, Jeff Johnson wrote: >I've been doing the IESG quality review on this document. There are two >issues which I would like to get the list(s) feedback on. > >1) Currently all three TCs have a syntax of Gauge32. IMO this implies >certain semantics which the TCs and the underlying MIB objects do not >possess. I'd prefer to see these all changed to Unsigned32. Note that >Gauge32 and Unsigned32 are encoded identicially, so there would be no >change to the data on the wire. I agree. >2) The xyzInvalidIntervals DESCRIPTION states simply "The number of >intervals for which no valid data is available." When an agent which >supports 96 intervals is initially powered up, should the invalid interval >counter be 0 or 96? In other words, are there initially 96 intervals which >are all invalid, or are there zero intervals? I think that it should be the number of UNAVAILABLE intervals and that it should be the difference between the number of SUPPORTED intervals and the number of AVAILABLE intervals. INVALID intervals are another matter altogether (see ANSI T1.231-1997 clause 9.1.2.2). Given that, the name is wrong. It should be xyzUnavailableIntervals and xyzValidIntervals should be xyzAvailableIntervals. I'm proposing that the SONET Supplemental MIB contain the following variables for 1-day intervals: sonetSupportedDays OBJECT-TYPE SYNTAX INTEGER (0..32) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of previous and recent 1-day intervals which the SONET interface supports." REFERENCE "ANSI T1.231-1997 clause 9.1.2.1." ::= { sonetSupMediumEntry 1 } sonetAvailableDays OBJECT-TYPE SYNTAX INTEGER (0..32) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of previous and recent 1-day intervals for which data is acutally available. For a SONET interface which supports n previous and recent day intervals, the number of available intervals will be n unless the device was brought online within the last n complete days, in which case the value will be the number of complete day intervals the device has been online. It is also possible that some intervals are unavailable in the case where the agent is a proxy." REFERENCE "ANSI T1.231-1997 clause 9.1.2.1." ::= { sonetSupMediumEntry 2 } And for each layer: sonetSectionDayValidData OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if the data for this interval is valid." REFERENCE "ANSI T1.231-1997 clause 9.1.2.2." ::= { sonetSectionDayEntry 3 } ============================================== <color><param>0000,8080,0000</param>Ken Chapman Argon Networks, Inc. KChapman@Argon.com 25 Porter Road tel: 978-486-0665 x146 Littleton, MA 01460 fax: 978-486-9379 http://www.Argon.com </color>==============================================
- PerfHist-TC-MIB Ken Chapman
- Re: PerfHist-TC-MIB Kaj Tesink
- Re: PerfHist-TC-MIB Ken Chapman
- Re: PerfHist-TC-MIB Rajesh Abbi
- Re: PerfHist-TC-MIB C. M. Heard/VVNET, Inc.
- Re: PerfHist-TC-MIB David Fowler
- Re: PerfHist-TC-MIB Kaj Tesink
- Re: PerfHist-TC-MIB Ken Chapman
- Re: DS1, DS3 and SONET Supplemental MIBs (WAS: Pe… C. M. Heard/VVNET, Inc.
- Re: DS1, DS3 and SONET Supplemental MIBs Kaj Tesink
- Re: PerfHist-TC-MIB Jeff Johnson
- Re: PerfHist-TC-MIB C. M. Heard/VVNET, Inc.
- Re: PerfHist-TC-MIB Rajesh Abbi
- Re: PerfHist-TC-MIB Keith McCloghrie
- Re: PerfHist-TC-MIB David Fowler
- Re: PerfHist-TC-MIB Randy Presuhn
- Re: PerfHist-TC-MIB Rajesh Abbi
- Re: PerfHist-TC-MIB Jeff Johnson
- Re: PerfHist-TC-MIB Jeff Johnson
- Re: PerfHist-TC-MIB jeff
- Re: PerfHist-TC-MIB C. M. Heard/VVNET, Inc.
- Re: PerfHist-TC-MIB Chunhui Teng
- Re: PerfHist-TC-MIB Chunhui Teng
- Re: PerfHist-TC-MIB Rajesh Abbi
- Re: PerfHist-TC-MIB jeff
- Re: PerfHist-TC-MIB Rajesh Abbi
- Re: PerfHist-TC-MIB C. M. Heard/VVNET, Inc.
- Re: PerfHist-TC-MIB Ken Chapman