Re: PerfHist-TC-MIB
Randy Presuhn <rpresuhn@dorothy.peer.com> Wed, 03 June 1998 17:41 UTC
Delivery-Date: Wed, 03 Jun 1998 13:41:12 -0400
Return-Path: rpresuhn@dorothy.peer.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 NAA23314 for <ietf-archive@ietf.org>; Wed, 3 Jun 1998 13:41:11 -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 NAA14649 for <ietf-archive@cnri.reston.va.us>; Wed, 3 Jun 1998 13:43:33 -0400 (EDT)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id KAA17662 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:35:19 -0700 (PDT)
Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id KAA03058 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 10:35:17 -0700 (PDT)
Received: from mail-gw1.bmc.com(198.64.253.22) by proxy2.cisco.com via smap (V2.0) id xma003036; Wed, 3 Jun 98 17:35:11 GMT
X-SMAP-Received-From: outside
Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA24375 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 12:25:41 -0500 (CDT)
Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma024369; Wed, 3 Jun 98 12:25:39 -0500
Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA25755 for <trunk-mib@external.cisco.com>; Wed, 3 Jun 1998 12:25:09 -0500 (CDT)
Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma025535; Wed, 3 Jun 98 12:24:59 -0500
Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA07419; Wed, 3 Jun 1998 12:25:27 -0500 (CDT)
Received: (from rpresuhn@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA08003; Wed, 3 Jun 1998 10:25:27 -0700 (PDT)
Date: Wed, 03 Jun 1998 10:25:27 -0700
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <199806031725.KAA08003@dorothy.peer.com>
To: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
Subject: Re: PerfHist-TC-MIB
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi - > Date: Tue, 2 Jun 1998 23:23:36 -0700 (PDT) > From: "C. M. Heard/VVNET, Inc." <heard@vvnet.com> > To: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com > Subject: Re: PerfHist-TC-MIB ... > I don't understand this. I always thought that if more that 2^32 - 1 of > the type of events counted by a PerfCurrentCount object occurred within > a 15 minute interval, then that PerfCurrentCount would be "pegged" at > 2^32 - 1 (i.e., would not roll over). Isn't this what a Gauge32 object > is supposed to do? ... Nope. "Pegging" behaviour of Gauges is folklore, due to the unfortunate use of the word "latch" in RFC 1155. The current description in RFC 1902 is explicit (note the last sentence): |7.1.7. Gauge32 | | The Gauge32 type represents a non-negative integer, which may | increase or decrease, but shall never exceed a maximum value. The | maximum value can not be greater than 2^32-1 (4294967295 decimal). | The value of a Gauge has its maximum value whenever the information | being modeled is greater or equal to that maximum value; if the | information being modeled subsequently decreases below the maximum | value, the Gauge also decreases. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." -----------------------------------------------------------------------
- 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