From ifmib-admin@ietf.org Mon Sep 11 04:40:42 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27781; Mon, 11 Sep 2000 04:40:42 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13714; Mon, 11 Sep 2000 04:32:43 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13691 for ; Mon, 11 Sep 2000 04:32:42 -0400 (EDT) Received: from alcanet.it (ns.alcanet.it [194.243.74.35]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27744 for ; Mon, 11 Sep 2000 04:32:40 -0400 (EDT) Received: from tlvsdy.vim.tlt.alcatel.it ([151.98.8.244]) by ns.alcanet.it with SMTP id <29751>; Mon, 11 Sep 2000 10:24:44 +0200 Received: from tlvhdk.netit.alcatel.it by tlvsdy.vim.tlt.alcatel.it (SMI-8.6/SMI-SVR4) id KAA09897; Mon, 11 Sep 2000 10:27:17 +0200 Received: from netit.alcatel.it (tlvqbe.vim.tlt.alcatel.it [151.98.40.146]) by tlvhdk.netit.alcatel.it (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id KAA18990; Mon, 11 Sep 2000 10:28:42 +0200 (METDST) Message-ID: <39BC9755.FCB22753@netit.alcatel.it> From: Massimo Canali Organization: Alcatel S.p.A. - Optics TND - Network Management X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: ifmib@ietf.org CC: Paolo Molgora Content-Type: multipart/mixed; boundary="------------B00F1E84D2CAEB44DFCF1B8B" Date: Mon, 11 Sep 2000 10:24:44 +0200 Subject: [ifmib] IF-MIB questions Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org This is a multi-part message in MIME format. --------------B00F1E84D2CAEB44DFCF1B8B Content-Type: multipart/alternative; boundary="------------41856F2C0FD5C69F018A9554" --------------41856F2C0FD5C69F018A9554 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by optimus.ietf.org id EAA13714 Content-Transfer-Encoding: quoted-printable Hello, My colleague and me are defining counter management for an Agent. We are studying the IF-MIB (RFC2863) and we have some questions about IfCounterDiscontinuityTime object usage: * Has a counter wrapping to be considered as a cause of ifCounterDiscontinuityTime object udpated? * When the ifAdminStaus and ifOperStatus objects switch to down has the Agent to update also the ifCounterDiscontinuityTime object? * In the ifCounterDiscontinuityTime definition the only counters associated to it are the one inside ifTable and ifXTable. Instead it is mentioned also in the the MAU-MIB counters ( e.g. ifMauJabberingStateEnters below). Are there any conflicts? Can we manage MAU-MIB counters as the IF-MIB ones? Can we envisage only one global ifCounterDiscontinuityTime object? MAU-MIB: ifMauJabberingStateEnters OBJECT-TYPE (=85) DESCRIPTION " (=85) Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCounter. RFC 2233, ifCounterDiscontinuityTime." Thanks in advance. Regards, Paolo and Massimo. --------------41856F2C0FD5C69F018A9554 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by optimus.ietf.org id EAA13714 Content-Transfer-Encoding: quoted-printable Hello,
My colleague and me are defining counter management for an Agent.
We are studying the IF-MIB (RFC2863) and we have some questions about
IfCounterDiscontinuityTime object usage:
  • Has a counter wrapping to be considered as a cause of ifCounterDiscontinu= ityTime object udpated?
  • When the ifAdminStaus and ifOperStatus objects switch to down has the Age= nt to update also the ifCounterDiscontinuityTime object?
  • In the ifCounterDiscontinuityTime definition the only counters associated to it are the one inside ifTable and ifXTable. Instead it is mentioned also in the the MAU-MIB counters ( e.g. ifMauJabberingStateEnters below). Are there any conflicts? Can we manage MAU-MIB counters as the IF-MIB one= s? Can we envisage only one global ifCounterDiscontinuityTime object?

    • MAU-MIB:
    ifMauJabberingStateEnters OBJECT-TYPE (=85)
    DESCRIPTION " (=85) Discontinuities in the value of this counter can occur at re-initialization of
    the management system, and at other times as indicated by the value of
    ifCounterDiscontinuityTime."
    REFERENCE   "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCo= unter. RFC 2233,
    ifCounterDiscontinuityTime."
     
Thanks in advance.
Regards,

Paolo and Massimo.
  --------------41856F2C0FD5C69F018A9554-- --------------B00F1E84D2CAEB44DFCF1B8B Content-Type: text/x-vcard; charset=us-ascii; name="Massimo.Canali.vcf" Content-Description: Card for Massimo Canali Content-Disposition: attachment; filename="Massimo.Canali.vcf" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit begin:vcard n:Canali;Massimo tel;fax:039 686 4185 tel;work:039 686 9259 x-mozilla-html:FALSE org:Alcatel ;A-Optics TND - Network Management System Team version:2.1 email;internet:massimo.Canali@netit.alcatel.it adr;quoted-printable:;;via Trento, 30=0D=0A;Vimercate;Milano;20059;Italy x-mozilla-cpt:;-1 fn:Massimo Canali end:vcard --------------B00F1E84D2CAEB44DFCF1B8B-- _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib From ifmib-admin@ietf.org Mon Sep 11 08:47:08 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA01090; Mon, 11 Sep 2000 08:47:04 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15685; Mon, 11 Sep 2000 08:39:58 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15666 for ; Mon, 11 Sep 2000 08:39:57 -0400 (EDT) Received: from itc-eml2.lannet.com (at.lannet.com [194.90.94.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00949 for ; Mon, 11 Sep 2000 08:39:54 -0400 (EDT) Received: by itc-eml2.lannet.com with Internet Mail Service (5.5.2650.21) id ; Mon, 11 Sep 2000 15:37:05 +0200 Message-ID: <15F58915DF84D311AC7D0090279AA614233BEB@itc-eml2.lannet.com> From: Dan Romascanu To: "'Massimo Canali'" , ifmib@ietf.org Cc: Paolo Molgora , "'bwijnen@lucent.com'" , "'hubmib@hprnd.rose.hp.com'" Subject: RE: [ifmib] IF-MIB questions Date: Mon, 11 Sep 2000 15:36:14 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org Paolo i Massimo, Truth is that the current practice is to consider media specific modules as extensions of the if-MIB. You are right that this contrradicts the DESCRIPTION clause of the ifDiscontinuityTime object. It looks like the phrase 'The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the ifTable or ifXTable.' is the one that contradicts the current practice, and we should consider taking it out at the next occasion. Ciao and Regards, Dan > -----Original Message----- > From: Massimo Canali [SMTP:Massimo.Canali@netit.alcatel.it] > Sent: Mon September 11 2000 10:25 > To: ifmib@ietf.org > Cc: Paolo Molgora > Subject: [ifmib] IF-MIB questions > > Hello, > My colleague and me are defining counter management for an Agent. > We are studying the IF-MIB (RFC2863) and we have some questions about > IfCounterDiscontinuityTime object usage: > > * Has a counter wrapping to be considered as a cause of > ifCounterDiscontinuityTime object udpated? > * When the ifAdminStaus and ifOperStatus objects switch to down has > the Agent to update also the ifCounterDiscontinuityTime object? > * In the ifCounterDiscontinuityTime definition the only counters > associated to it are the one inside ifTable and ifXTable. Instead it is > mentioned also in the the MAU-MIB counters ( e.g. > ifMauJabberingStateEnters below). Are there any conflicts? Can we manage > MAU-MIB counters as the IF-MIB ones? Can we envisage only one global > ifCounterDiscontinuityTime object? > > MAU-MIB: > ifMauJabberingStateEnters OBJECT-TYPE (...) > DESCRIPTION " (...) Discontinuities in the value of this counter can occur > at re-initialization of > the management system, and at other times as indicated by the value of > ifCounterDiscontinuityTime." > REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCounter. RFC > 2233, > ifCounterDiscontinuityTime." > > > Thanks in advance. > Regards, > > Paolo and Massimo. > << File: Card for Massimo Canali >> _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib From ifmib-admin@ietf.org Tue Sep 12 20:50:20 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA15749; Tue, 12 Sep 2000 20:50:20 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11660; Tue, 12 Sep 2000 20:43:14 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11642 for ; Tue, 12 Sep 2000 20:43:13 -0400 (EDT) Received: from ups.cisco.com (ups.cisco.com [171.69.18.21]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA15728 for ; Tue, 12 Sep 2000 20:43:12 -0400 (EDT) Received: (from kzm@localhost) by ups.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id RAA04960; Tue, 12 Sep 2000 17:42:40 -0700 (PDT) From: Keith McCloghrie Message-Id: <200009130042.RAA04960@ups.cisco.com> Subject: Re: [ifmib] IF-MIB questions To: Massimo.Canali@netit.alcatel.it (Massimo Canali) Date: Tue, 12 Sep 2000 17:42:40 -0700 (PDT) Cc: ifmib@ietf.org, PaoloFranco.Molgora@netit.alcatel.it (Paolo Molgora) In-Reply-To: <39BC9755.FCB22753@netit.alcatel.it> from "Massimo Canali" at Sep 11, 2000 10:24:44 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ups.cisco.com id RAA04960 X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id UAA11643 Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org X-MIME-Autoconverted: from 8bit to quoted-printable by optimus.ietf.org id UAA11660 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA15749 A discontinuity in the value of a counter occurs when the value changes from X to Y, but the number of new occurrences of the things it counts was not (Y-X) modulo 2**32. > * Has a counter wrapping to be considered as a cause of > ifCounterDiscontinuityTime object udpated? No, because of the modulo arithmetic. > * When the ifAdminStaus and ifOperStatus objects switch to down has > the Agent to update also the ifCounterDiscontinuityTime object? No, because the values of the counters do not change just because the value of ifAdminStaus and/or ifOperStatus changes to 'down'. > * In the ifCounterDiscontinuityTime definition the only counters > associated to it are the one inside ifTable and ifXTable. Instead > it is mentioned also in the the MAU-MIB counters ( e.g. > ifMauJabberingStateEnters below). Are there any conflicts? Can we > manage MAU-MIB counters as the IF-MIB ones? Can we envisage only > one global ifCounterDiscontinuityTime object? > MAU-MIB: > ifMauJabberingStateEnters OBJECT-TYPE (…) > DESCRIPTION " (…) Discontinuities in the value of this counter can > occur at re-initialization of > the management system, and at other times as indicated by the value > of > ifCounterDiscontinuityTime." > REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCounter. > RFC 2233, > ifCounterDiscontinuityTime." I don't think there's anything to prevent other counters from using ifCounterDiscontinuityTime, even though there are not specifically mentioned in its DESCRIPION. The relevant phrase in RFC 2863 is: "... relevant counters are the ..." Now, if it said: "... relevant counters are only the ..." then I would agree with you. Nevertheless, it would be clearer if it said: "... relevant counters include the ..." Keith. _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib From ifmib-admin@ietf.org Thu Sep 14 09:26:10 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11146; Thu, 14 Sep 2000 09:26:10 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12594; Thu, 14 Sep 2000 09:19:09 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12573 for ; Thu, 14 Sep 2000 09:19:08 -0400 (EDT) Received: from mail.kpnqwest.ch (mail.eunet.ch [146.228.10.7]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10953 for ; Thu, 14 Sep 2000 09:19:07 -0400 (EDT) From: dsvkdi@revproxy.iaea.or.at Received: from oettinger.davidoff.ch ([195.49.110.243]) by mail.kpnqwest.ch (8.9.3/1.34) via ESMTP id NAA15221 for ; Thu, 14 Sep 2000 13:18:34 GMT env-from (dsvkdi@revproxy.iaea.or.at) Received: from mail.mindspring.com by oettinger.davidoff.ch via SMTP id smtp\t9eegiqy.in; 14 Sep 2000 14:52:00 +0200 To: Date: Thu, 14 Sep 2000 05:18:15 Message-Id: <525.347308.199322@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ifmib] (no subject) Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 Webhosting International _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib