Re: PerfHist-TC-MIB

Rajesh Abbi <abbira@aur.alcatel.com> Wed, 03 June 1998 18:03 UTC

Delivery-Date: Wed, 03 Jun 1998 14:03:30 -0400
Return-Path: abbira@aur.alcatel.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 OAA23876 for <ietf-archive@ietf.org>; Wed, 3 Jun 1998 14:03:29 -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 OAA14784 for <ietf-archive@cnri.reston.va.us>; Wed, 3 Jun 1998 14:05:51 -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 KAA21034 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:58:07 -0700 (PDT)
Received: (from smap@localhost) by proxy1.cisco.com (8.8.7/8.8.5) id KAA04984 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:58:04 -0700 (PDT)
Received: from aurms0.aur.alcatel.com(143.209.4.1) by proxy1.cisco.com via smap (V2.0) id xma004954; Wed, 3 Jun 98 17:57:57 GMT
X-SMAP-Received-From: outside
Received: from aursf1 (aursf1 [198.151.197.39]) by aurms0.aur.alcatel.com (8.8.8/8.8.7) with SMTP id NAA04677; Wed, 3 Jun 1998 13:47:49 -0400 (EDT)
Sender: abbira@aur.alcatel.com
Message-ID: <35758BD8.4245@aur.alcatel.com>
Date: Wed, 03 Jun 1998 13:46:00 -0400
From: Rajesh Abbi <abbira@aur.alcatel.com>
Organization: Alcatel Network Systems, Inc Raleigh, NC
X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Keith McCloghrie <kzm@cisco.com>
CC: heard@vvnet.com, atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
Subject: Re: PerfHist-TC-MIB
References: <199806031614.JAA09806@foxhound.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Keith McCloghrie wrote:
> 
> > The 'Perf***Count' objects are supposed to be 'monotonically increasing'
> > -
> > thus Counter32/Counter64 would have been a better representation.
> 
> This is incorrect.  For each of these objects, its value in one interval
> can be smaller than its value in the preceeding interval.
> 
> Keith.

These objects have a lifetime of 15-minutes.  During their lifetime
their
value is certainly 'monotonically increasing' !  After the interval is
over,
the current counter starts again - ie: a new instance is created.

Regarding Interval Counters - each interval is a 'separate instance' of
the
object.  The value in all 'historic' intervals (except the current one)
is
fixed - neither increasing nor decreasing.

Rajesh