IETF Logo Mail Archive

Re: PerfHist-TC-MIB

jeff@redbacknetworks.com Wed, 03 June 1998 21:50 UTC

Delivery-Date: Wed, 03 Jun 1998 17:50:43 -0400
Return-Path: jeff@redbacknetworks.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 RAA28023 for <ietf-archive@ietf.org>; Wed, 3 Jun 1998 17:50:42 -0400 (EDT)
From: jeff@redbacknetworks.com
Received: from brittany.cisco.com (brittany.cisco.com [171.69.1.168]) by cnri.reston.va.us (8.8.5/8.8.7a) with SMTP id RAA16066 for <ietf-archive@cnri.reston.va.us>; Wed, 3 Jun 1998 17:53:04 -0400 (EDT)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by brittany.cisco.com (8.6.12/8.6.5) with ESMTP id OAA23602 for <extdom.trunk-mib@aliashost.cisco.com>; Wed, 3 Jun 1998 14:45:11 -0700
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id OAA09786 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 14:45:10 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id OAA15242 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 14:45:09 -0700 (PDT)
Received: from mail3.redbacknetworks.com(155.53.200.100) by proxy3.cisco.com via smap (V2.0) id xma015225; Wed, 3 Jun 98 21:45:03 GMT
X-SMAP-Received-From: outside
Received: from starbug.redbacknetworks.com (starbug.redbacknetworks.com [155.53.144.22]) by ns3.redbacknetworks.com (8.8.8/8.8.8) with ESMTP id OAA12138; Wed, 3 Jun 1998 14:41:18 -0700 (PDT)
Received: (from jeff@localhost) by starbug.redbacknetworks.com (8.8.5/8.8.5) id OAA28871; Wed, 3 Jun 1998 14:40:47 -0700 (PDT)
Message-Id: <199806032140.OAA28871@starbug.redbacknetworks.com>
Subject: Re: PerfHist-TC-MIB
To: davef@newbridge.com
Date: Wed, 03 Jun 1998 14:40:46 -0700
Cc: heard@vvnet.com, atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
In-Reply-To: <3575825E.515C32D4@newbridge.com> from "David Fowler" at Jun 3, 98 01:05:47 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

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

Let's go back to the example I gave earlier where the device has been
running more than 24 hours, but there was a communication disruption
whereby only intervals 1 and 96 were valid.  I think we can all agree
that according to the object description clauses that xyzValidIntervals
should be 96 and xyzInvalidIntervals should be 94.  Assuming the current
interval is "good", what should be the values of xyzValidIntervals and
xyzInvalidIntervals when the next 15 minute threshold is crossed (i.e.
intervals 1 and 2 are valid, intervals 3 through 96 are invalid).

/jeff

v2.23.0 | Report a Bug | By Email