Re: PerfHist-TC-MIB
David Fowler <davef@newbridge.com> Wed, 03 June 1998 17:14 UTC
Delivery-Date: Wed, 03 Jun 1998 13:14:03 -0400
Return-Path: davef@ca.newbridge.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 NAA22637 for <ietf-archive@ietf.org>; Wed, 3 Jun 1998 13:14:02 -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 NAA14512 for <ietf-archive@cnri.reston.va.us>; Wed, 3 Jun 1998 13:16:25 -0400 (EDT)
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id KAA14095 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:08:32 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id KAA21812 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:08:28 -0700 (PDT)
Received: from ns.newbridge.com(192.75.23.67) by proxy3.cisco.com via smap (V2.0) id xma021777; Wed, 3 Jun 98 17:08:19 GMT
X-SMAP-Received-From: outside
Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id NAA04397; Wed, 3 Jun 1998 13:01:49 -0400 (EDT)
Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma004292; Wed Jun 3 13:01:09 1998
Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 3 Jun 1998 17:01:09 UT
Received: from thor.ca.newbridge.com (thor121.ca.newbridge.com [138.120.121.43]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id NAA27226; Wed, 3 Jun 1998 13:01:09 -0400 (EDT)
Received: from newbridge.com (macdavef [138.120.55.103]) by thor.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id NAA06819; Wed, 3 Jun 1998 13:00:51 -0400
Message-ID: <3575825E.515C32D4@newbridge.com>
Date: Wed, 03 Jun 1998 13:05:47 -0400
From: David Fowler <davef@newbridge.com>
X-Mailer: Mozilla 4.04 (Macintosh; I; PPC)
MIME-Version: 1.0
To: "C. M. Heard/VVNET, Inc." <heard@vvnet.com>
CC: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
Subject: Re: PerfHist-TC-MIB
References: <Pine.BSF.3.96.980602225056.7629A-100000@shell16.ba.best.com>
Content-Type: text/plain; charset="us-ascii"; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
> Jeff Johnson wrote: > > > > 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? > Miek heard wrote: > My interpretation is that xyzValidIntervals + xyzInvalidIntervals always > sums to the number of intervals which the agent supports. This implies > that an agent which supports 96 intervals should report a value of 0 for > xyzValidIntervals and and a value of 96 for xyzInvalidIntervals when first > powered up. (If I got this wrong, I'd sure like to know.) > When an agent starts up, it has no valid intervals. It also has no invalid intervals. The definition for valid intervals is the latest ds1 draft is: "The number of previous near end intervals for which valid data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute near end intervals since the interface has been brought online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which valid data is available." The definition for invalid intervals from the same draft is "the number of intervals for which no valid data is availab" My intention in the creation of this object was to allow for the proxy case discussed above. That is, the number of invalid intervals would be the count of "missing" intervals on a proxy. Missing intervals occur when the proxy is out of touch with the actual interface and is unable to collect some intervals. With that meaning, my intention was that the number of invalid intervals could never be equal to or greater than the number of valid intervals since the number of valid intervals holds the maximum interval number for which there is valid data. For example, if the agent has been running for 12 hours, the number of valid intervals would be 48. If there was a communication disruption for one hour during that time, then the number of invalid intervals would be 4. All we really need to do is clarify that the number of invalid intervals must be less than the number of valid intervals and that it is intended for the proxy situation. Regards, David -- David Fowler Newbridge Networks 613-591-3600
- 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