Re: PerfHist-TC-MIB

"C. M. Heard/VVNET, Inc." <heard@vvnet.com> Wed, 27 May 1998 17:21 UTC

Delivery-Date: Wed, 27 May 1998 13:21:25 -0400
Return-Path: heard@vvnet.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 NAA06418 for <ietf-archive@ietf.org>; Wed, 27 May 1998 13:21:24 -0400 (EDT)
Received: from beasley.cisco.com (mailgate-sj-2.cisco.com [171.69.2.135]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA11630 for <ietf-archive@cnri.reston.va.us>; Wed, 27 May 1998 13:23:47 -0400 (EDT)
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by beasley.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id KAA05516 for <trunk-mib@external.cisco.com>; Wed, 27 May 1998 10:09:29 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id KAA02493 for <trunk-mib@external.cisco.com>; Wed, 27 May 1998 10:09:27 -0700 (PDT)
Received: from shell16.ba.best.com(206.184.139.148) by proxy3.cisco.com via smap (V2.0) id xma002481; Wed, 27 May 98 17:09:23 GMT
X-SMAP-Received-From: outside
Received: from localhost (heard@localhost) by shell16.ba.best.com (8.8.8/8.8.BEST) with SMTP id KAA24200; Wed, 27 May 1998 10:06:05 -0700 (PDT)
X-Authentication-Warning: shell16.ba.best.com: heard owned process doing -bs
Date: Wed, 27 May 1998 10:06:03 -0700
From: "C. M. Heard/VVNET, Inc." <heard@vvnet.com>
X-Sender: heard@shell16.ba.best.com
To: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
Subject: Re: PerfHist-TC-MIB
In-Reply-To: <3.0.32.19980527091345.00950640@shultz.argon.com>
Message-ID: <Pine.BSF.3.96.980527095847.18276D-100000@shell16.ba.best.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"

On Wed, 27 May 1998, Ken Chapman wrote:

> Kaj,
> I have an issue with it.  I agree with the three TC, but there is one
> missing:  PerfDayCount.
> It is quite different from PerfTotalCount; it starts at a specific time
> each day an is the aggregate of the 96 15-minute interval in the subsequent
> 24-hour interval.
> This is in support of the requirements specified in ANSI T1.231-1993,
> clause 9.1.2.1 (Current day register and Recent day registers).
> (I assume that the purpose of the MIB work is to support industry
> standards!)
> 	Ken

There are several things besides the Current day and Recent day registers
that are required by the ANSI performance monitoring standard T1.231 but
that are not in the IETF trunkmibs.  Some other notable ones are failure
counts, protection switching statictics, and (for SONET ADMs) pointer
justification statistics (this last was added in T1.231-1997).  Some or
all of these things would be good candidates for supplemental trunk MIBs,
which have in fact been proposed some time ago.  Why not put PerfDayCount
(and any other TCs needed to support the supplemental trunk MIBs) in a
Supplemental-PerfHist-TC-MIB?

Mike
--
C. M. Heard/VVNET, Inc.
heard@vvnet.com