Re: Proposals to clarify xyzIntervalValidData description
"C. M. Heard/VVNET, Inc." <heard@vvnet.com> Fri, 12 June 1998 18:01 UTC
Delivery-Date: Fri, 12 Jun 1998 14:01:13 -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 OAA21696 for <ietf-archive@ietf.org>; Fri, 12 Jun 1998 14:01:12 -0400 (EDT)
Received: from rhine.cisco.com (rhine.cisco.com [171.69.43.21]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id OAA25624 for <ietf-archive@cnri.reston.va.us>; Fri, 12 Jun 1998 14:03:34 -0400 (EDT)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by rhine.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA28017 for <extdom.trunk-mib@aliashost.cisco.com>; Fri, 12 Jun 1998 10:54:08 -0700 (PDT)
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 KAA02372 for <trunk-mib@external.cisco.com>; Fri, 12 Jun 1998 10:54:05 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id KAA27389 for <trunk-mib@external.cisco.com>; Fri, 12 Jun 1998 10:54:04 -0700 (PDT)
Received: from shell16.ba.best.com(206.184.139.148) by proxy3.cisco.com via smap (V2.0) id xma027373; Fri, 12 Jun 98 17:53:58 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 KAA19311; Fri, 12 Jun 1998 10:50:42 -0700 (PDT)
X-Authentication-Warning: shell16.ba.best.com: heard owned process doing -bs
Date: Fri, 12 Jun 1998 10:50:41 -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: Proposals to clarify xyzIntervalValidData description
In-Reply-To: <35813441.BE1C3189@aur.alcatel.com>
Message-ID: <Pine.BSF.3.96.980612101802.11307B-100000@shell16.ba.best.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
On Fri, 12 Jun 1998, Rajesh Abbi wrote: > I'm glad to see the addition of the 'IntervalValidData' flags to the interval > tables. > > I would also mention other cases where data may not be collected for > an interval by the agent: > - Agent unable to keep up with data collection due to equipment performance > problems. > - Equipment may be in a state where data collection is interrupted. I think that this would be covered by the second of the two proposed description clauses in my note (that's certainly what was intended): "This variable assumes the value true(1) if the data stored XXX for this interval is both valid and complete. It is set to XXX false(2) if the data stored for this interval is incomplete XXX or otherwise invalid because: XXX XXX - the data stored for this interval is for a period greater XXX or less than 15 minutes; or XXX XXX - some data is missing (e.g., when a near-end defect prevents XXX some far-end data from being collected)." XXX If you think that additional clarification is needed, however, you are welcome to propose specific text. > An important case needs to be addressed explicitly in the MIBs - what happens > when an interface's ifAdminStatus is set to 'down' by a manager. In my > opinion the data collection must be stopped while the ifAdminStatus is 'down'. > This will be another case when data in an interval may be incomplete. > > What's the opinion of others ? It's certainly true that data cannot be collected when the interface is off-line. It had not occurred to me that someone might assume otherwise. Again, if you feel that additional clarification is needed, please propose specific text. > > Rajesh > Mike -- C. M. Heard/VVNET, Inc. heard@vvnet.com
- Proposals to clarify xyzIntervalValidData descrip… C. M. Heard/VVNET, Inc.
- Re: Proposals to clarify xyzIntervalValidData des… Rajesh Abbi
- Re: Proposals to clarify xyzIntervalValidData des… C. M. Heard/VVNET, Inc.