
From gmatusov@cablevision.com  Wed Jun 23 14:09:14 2010
Return-Path: <gmatusov@cablevision.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCEBB28C0E0 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 14:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.137
X-Spam-Level: **
X-Spam-Status: No, score=2.137 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAzWGmQxf2KI for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 14:09:13 -0700 (PDT)
Received: from cscpsmout02.cablevision.com (cscpsmout02.cablevision.com [167.206.119.145]) by core3.amsl.com (Postfix) with ESMTP id 7078628C0F5 for <ops-area@ietf.org>; Wed, 23 Jun 2010 14:09:12 -0700 (PDT)
Received: from c2gwiaoutvs.cablevision.com (c2gwiaoutvs.cablevision.com [10.128.36.152]) by cscpsmout02.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o5NL9JtC004411 for <ops-area@ietf.org>; Wed, 23 Jun 2010 17:09:19 -0400
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout02.cablevision.com o5NL9JtC004411
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1277327360; bh=wK05r/sw2MXaSKWF6QckDAr7FDAdLfUnYhNdjKd 2pXU=; h=Message-Id:Date:From:To:Subject:Mime-Version:Content-Type: Content-Transfer-Encoding; b=1Won78OwKm+5RLFLG1GIsNxFmVBB0TQFC6SM8 JxAcucCo6r1LACY3WA3nFBlEsvuSpC6c/KD7XM0H3LVbsQF5L2/oSqjdBURm/m90nlU vNYfJx2FHqM8bHPssIdPzkwh69iJiDtfx71KFxYLPdG+cqP+6gP2b7x5xssb0OE4f+4 =
Received: from C2GWIAOUTDOM-MTA by c2gwiaoutvs.cablevision.com with Novell_GroupWise; Wed, 23 Jun 2010 17:09:19 -0400
Message-Id: <4C223F8D.54CB.00CA.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.4 
Date: Wed, 23 Jun 2010 17:08:52 -0400
From: "Gene Matusovsky" <gmatusov@cablevision.com>
To: <ops-area@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Auth-Type: Internal IP
Subject: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 21:29:44 -0000

RFC1155 defines TimeTicks as a non-negative integer, with a maximum value of 4294967296. 

In our environment, this limiting the hrSystemUptime object id 1.3.6.1.2.1.25.1.1.0 to 497 days, at which point the counter rolls and resets back 0.  
This causes our NMS system to display in-accurate information from our field SNMP agents for their hrSystemUptime values.

Is there any workarounds to this problem we're facing? Are there any plans to increase the RFC1155 definition of TimeTicks to a higher 64 bit integer value?

-Thank You,
Gene Matusovsky




-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------

From gmatusov@cablevision.com  Wed Jun 23 14:29:44 2010
Return-Path: <gmatusov@cablevision.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02BB428C0E6 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 14:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.988
X-Spam-Level: 
X-Spam-Status: No, score=0.988 tagged_above=-999 required=5 tests=[AWL=1.149,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SARE_SUB_OBFU_Q0=0.303]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c98umqHb2GvT for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 14:29:43 -0700 (PDT)
Received: from cscpsmout02.cablevision.com (cscpsmout02.cablevision.com [167.206.119.145]) by core3.amsl.com (Postfix) with ESMTP id D13E43A69D9 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 14:29:42 -0700 (PDT)
Received: from c2gwiaoutvs.cablevision.com (c2gwiaoutvs.cablevision.com [10.128.36.152]) by cscpsmout02.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o5NLTnoh014228 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 17:29:49 -0400
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout02.cablevision.com o5NLTnoh014228
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1277328589; bh=6TUxmYDsvg/xbAkZyzj9nOUCJVWmjbGOmM48nYw Ooos=; h=Message-Id:Date:From:To:Subject:References:In-Reply-To: Mime-Version:Content-Type:Content-Transfer-Encoding; b=x9bJxgrm0wQ /xBRngP6n6LfkpDdeuiSlsFkejehVFCld23sllfJMJnvFExWFab1A7GPd/YtcpLQRBT PWpFREpcjxfxKufJzv4+iZUTj9hN72hIk0k2p52H/m+UyBpvc0WMmrjQTxMkXYT3s+J 2k06g9tkXUgxxH8FH5z3ppf2Zo=
Received: from C2GWIAOUTDOM-MTA by c2gwiaoutvs.cablevision.com with Novell_GroupWise; Wed, 23 Jun 2010 17:29:48 -0400
Message-Id: <4C224453.54CB.00CA.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.4 
Date: Wed, 23 Jun 2010 17:29:15 -0400
From: "Gene Matusovsky" <gmatusov@cablevision.com>
To: <ops-area@core3.amsl.com>
References: <20100623210914.DBFDF28C0F5@core3.amsl.com>
In-Reply-To: <20100623210914.DBFDF28C0F5@core3.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Auth-Type: Internal IP
Subject: [OPS-AREA] Confirm: ops-area@core3.amsl.com:wIRpoZTCJ3-g:sP7v94hezYLIq-VR0YLurEBUpqwIRPJMGdX3zg
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 21:29:44 -0000

>>> <ops-area@core3.amsl.com> 6/23/2010 5:09 PM >>>

Confirmation of list posting -- confirmation ID: wIRpoZTCJ3-g

The ietf.org mailing-list server has received a list posting from 
gmatusov@cablevision.com to ops-area@core3.amsl.com with the subject 
'RFC1155 Timeticks hitting maximum value'

As the sender address isn't subscribed to the list, and has not been
confirmed earlier, we have to request a confirmation of the address.
To confirm the address, send a message to ops-area@core3.amsl.com,
with the same subject line as this message.

(Simply sending a 'reply' to this message should work from most email
interfaces, since that usually leaves the subject line in the right
form.  The reply's additional "Re:" is ok.)

If you do not wish your posting to the list to go through, simply
disregard this message.  Questions to postmaster@ietf.org.



-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------

From randy_presuhn@mindspring.com  Wed Jun 23 15:15:31 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D81A3A69A8 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 15:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2
X-Spam-Level: **
X-Spam-Status: No, score=2 tagged_above=-999 required=5 tests=[BAYES_80=2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGXLVoeIZWS8 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 15:15:29 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id 0B3B03A6A00 for <ops-area@ietf.org>; Wed, 23 Jun 2010 15:15:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=fs4svyTsNhhZkNdVkLha4OLDR3eRS5E0oNPMjeZLehR3rydzZklOTXSyS9DDZ01y; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.41.55.58] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1ORYEL-0001xd-1z for ops-area@ietf.org; Wed, 23 Jun 2010 18:15:37 -0400
Message-ID: <011701cb1321$d689e180$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ops-area@ietf.org>
References: <4C223F8D.54CB.00CA.0@cablevision.com>
Date: Wed, 23 Jun 2010 15:17:15 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a91fc72053278035c3f171c773d8c6253ea16bff0d43b1aa350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.41.55.58
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 22:15:31 -0000

Hi -

> From: "Gene Matusovsky" <gmatusov@cablevision.com>
> To: <ops-area@ietf.org>

You'd be better off sending this to the MIB doctors list,
mib-doctors@ietf.org

> Sent: Wednesday, June 23, 2010 2:08 PM
> Subject: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>
> RFC1155 defines TimeTicks as a non-negative integer, with a maximum value of 4294967296.
>
> In our environment, this limiting the hrSystemUptime object id 1.3.6.1.2.1.25.1.1.0 to 497 days, at which point the counter rolls
and resets back 0.
> This causes our NMS system to display in-accurate information from our field SNMP agents for their hrSystemUptime values.

The snide response is to suggest getting another NMS.

But the reality is that hrSystemUptime has obvious limitations,
which the NMS developer should have understood when deciding
how to display it.

> Is there any workarounds to this problem we're facing? Are there any plans to increase the RFC1155 definition of TimeTicks to a
higher 64 bit integer value?

I am not aware of any such plans.  Making such a change would require
the creation of a whole new set of objects.  In many cases, however, the
TimeTicks approach no longer makes sense.   You might also take a look
at the material on snmpEngineBoots and snmpEngineTime in RFC 3414
to see how a closely related issue was dealt with.

Randy



From saperia@jdscons.com  Wed Jun 23 15:54:01 2010
Return-Path: <saperia@jdscons.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BC743A6801 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 15:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhD6ovFmC-EW for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 15:54:00 -0700 (PDT)
Received: from rs69.luxsci.com (rs69.luxsci.com [64.49.254.154]) by core3.amsl.com (Postfix) with ESMTP id 39FE53A67B8 for <ops-area@ietf.org>; Wed, 23 Jun 2010 15:53:58 -0700 (PDT)
Received: from [10.0.1.13] (c-98-229-133-101.hsd1.ma.comcast.net [98.229.133.101]) (authenticated bits=0) by rs69.luxsci.com (8.13.8/8.13.8) with ESMTP id o5NMs4t7025437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 23 Jun 2010 17:54:05 -0500
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Jon Saperia <saperia@jdscons.com>
X-Priority: 3
In-Reply-To: <011701cb1321$d689e180$6801a8c0@oemcomputer>
Date: Wed, 23 Jun 2010 18:54:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1081)
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 22:54:01 -0000

Why would a whole new set of objects be required to either fix, =
hrSystemUptime, or create a new higher capacity object?
/jon
On Jun 23, 2010, at 6:17 PM, Randy Presuhn wrote:

> Hi -
>=20
>> From: "Gene Matusovsky" <gmatusov@cablevision.com>
>> To: <ops-area@ietf.org>
>=20
> You'd be better off sending this to the MIB doctors list,
> mib-doctors@ietf.org
>=20
>> Sent: Wednesday, June 23, 2010 2:08 PM
>> Subject: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>>=20
>> RFC1155 defines TimeTicks as a non-negative integer, with a maximum =
value of 4294967296.
>>=20
>> In our environment, this limiting the hrSystemUptime object id =
1.3.6.1.2.1.25.1.1.0 to 497 days, at which point the counter rolls
> and resets back 0.
>> This causes our NMS system to display in-accurate information from =
our field SNMP agents for their hrSystemUptime values.
>=20
> The snide response is to suggest getting another NMS.
>=20
> But the reality is that hrSystemUptime has obvious limitations,
> which the NMS developer should have understood when deciding
> how to display it.
>=20
>> Is there any workarounds to this problem we're facing? Are there any =
plans to increase the RFC1155 definition of TimeTicks to a
> higher 64 bit integer value?
>=20
> I am not aware of any such plans.  Making such a change would require
> the creation of a whole new set of objects.  In many cases, however, =
the
> TimeTicks approach no longer makes sense.   You might also take a look
> at the material on snmpEngineBoots and snmpEngineTime in RFC 3414
> to see how a closely related issue was dealt with.
>=20
> Randy
>=20
>=20
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>=20


From randy_presuhn@mindspring.com  Wed Jun 23 16:28:51 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AC043A68B7 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 16:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1
X-Spam-Level: *
X-Spam-Status: No, score=1 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlthoV7aS+tj for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 16:28:50 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 132F13A6814 for <ops-area@ietf.org>; Wed, 23 Jun 2010 16:28:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=cKO1pSFWe5D4xZMdebOLd2B7MupN8o3K4eS8M2pR2oOl6hlKs0jRNLQgFg7AmY1I; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.41.55.58] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1ORZNJ-0006QO-T1 for ops-area@ietf.org; Wed, 23 Jun 2010 19:28:58 -0400
Message-ID: <014201cb132c$16668f60$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ops-area@ietf.org>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com>
Date: Wed, 23 Jun 2010 16:30:37 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a91fc720532780350074f45ece86a2a1507363a1a28b5d95350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.41.55.58
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 23:28:51 -0000

Hi -

> From: "Jon Saperia" <saperia@jdscons.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ops-area@ietf.org>
> Sent: Wednesday, June 23, 2010 3:54 PM
> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>
> Why would a whole new set of objects be required to either fix,
> hrSystemUptime, or create a new higher capacity object?

The question wasn't just about hrSystemUptime, but the fundamental
deficiency of time ticks.

Coming up with a new time ticks syntax would effectively mean
every existing time ticks object would at least need to be
considered for obsolescence, and new objects would need
to be created in appropriate cases.  Counters currently referencing those
time ticks objects as discontinuity indicators would then have to be
considered for update as well, unless we were going to say that
implementations MUST support both representations.  (This quickly
becomes a replay of the 32-bit counter / 64-bit counter / paired-counter
discussion from SMIv2.)

But that really wouldn't address the problem - an existing NMS
application that behaves badly when hrSystemUptime wraps.

Randy


From saperia@jdscons.com  Wed Jun 23 16:43:44 2010
Return-Path: <saperia@jdscons.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4D0E3A69E8 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 16:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VIIjchRUmVp0 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 16:43:43 -0700 (PDT)
Received: from rs69.luxsci.com (rs69.luxsci.com [64.49.254.154]) by core3.amsl.com (Postfix) with ESMTP id C9CE83A6A0B for <ops-area@ietf.org>; Wed, 23 Jun 2010 16:43:43 -0700 (PDT)
Received: from [10.0.1.13] (c-98-229-133-101.hsd1.ma.comcast.net [98.229.133.101]) (authenticated bits=0) by rs69.luxsci.com (8.13.8/8.13.8) with ESMTP id o5NNhoWh032535 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 23 Jun 2010 18:43:51 -0500
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Jon Saperia <saperia@jdscons.com>
X-Priority: 3
In-Reply-To: <014201cb132c$16668f60$6801a8c0@oemcomputer>
Date: Wed, 23 Jun 2010 19:43:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1081)
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 23:43:45 -0000

But is was in the context specifically of hrSystemUptime - at least that =
is how I read it.  I was suggesting a surgical fix to a specific problem =
related to uptime.  That could be fixed with a single object and leave =
the others that use time ticks intact.

That said, I do agree with you that a good NMS should be able to deal =
with this and other oddities in this and many other objects. =20

/jon
On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:

> Hi -
>=20
>> From: "Jon Saperia" <saperia@jdscons.com>
>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
>> Cc: <ops-area@ietf.org>
>> Sent: Wednesday, June 23, 2010 3:54 PM
>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>>=20
>> Why would a whole new set of objects be required to either fix,
>> hrSystemUptime, or create a new higher capacity object?
>=20
> The question wasn't just about hrSystemUptime, but the fundamental
> deficiency of time ticks.
>=20
> Coming up with a new time ticks syntax would effectively mean
> every existing time ticks object would at least need to be
> considered for obsolescence, and new objects would need
> to be created in appropriate cases.  Counters currently referencing =
those
> time ticks objects as discontinuity indicators would then have to be
> considered for update as well, unless we were going to say that
> implementations MUST support both representations.  (This quickly
> becomes a replay of the 32-bit counter / 64-bit counter / =
paired-counter
> discussion from SMIv2.)
>=20
> But that really wouldn't address the problem - an existing NMS
> application that behaves badly when hrSystemUptime wraps.
>=20
> Randy
>=20
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>=20


From mark@ellisonsoftware.com  Wed Jun 23 18:17:12 2010
Return-Path: <mark@ellisonsoftware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E9A43A6A13 for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 18:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.117
X-Spam-Level: 
X-Spam-Status: No, score=-100.117 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JbizeM8t8Qg for <ops-area@core3.amsl.com>; Wed, 23 Jun 2010 18:17:11 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 471523A6902 for <ops-area@ietf.org>; Wed, 23 Jun 2010 18:17:11 -0700 (PDT)
Received: by vws14 with SMTP id 14so1215198vws.31 for <ops-area@ietf.org>; Wed, 23 Jun 2010 18:17:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.63.12 with SMTP id z12mr4543102vch.260.1277342236229; Wed,  23 Jun 2010 18:17:16 -0700 (PDT)
Sender: mark@ellisonsoftware.com
Received: by 10.220.181.9 with HTTP; Wed, 23 Jun 2010 18:17:16 -0700 (PDT)
In-Reply-To: <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com>
Date: Wed, 23 Jun 2010 21:17:16 -0400
X-Google-Sender-Auth: L4G16-PizrkTPy7yQ16kYJRiEGI
Message-ID: <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com>
From: Mark Ellison <ellison@ieee.org>
To: Jon Saperia <saperia@jdscons.com>
Content-Type: multipart/alternative; boundary=e0cb4e8876f13f41ff0489bc6a47
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 01:17:12 -0000

--e0cb4e8876f13f41ff0489bc6a47
Content-Type: text/plain; charset=ISO-8859-1

Hi-

I would anticipate that an intelligently designed NMS would watch for wrap
on a TimeTicks object by checking for an increment in snmpEngineBoots, or
alternatively, simply watch the value of the snmpEngineTime object, since
its granularity is seconds rather than 1/100th seconds yielding a 40k+ day
wrap interval.

In any case, the target system sure isn't running a MS OS ;-)

Regards,

Mark
--
http://EllisonSoftware.com/

On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com> wrote:

> But is was in the context specifically of hrSystemUptime - at least that is
> how I read it.  I was suggesting a surgical fix to a specific problem
> related to uptime.  That could be fixed with a single object and leave the
> others that use time ticks intact.
>
> That said, I do agree with you that a good NMS should be able to deal with
> this and other oddities in this and many other objects.
>
> /jon
> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
>
> > Hi -
> >
> >> From: "Jon Saperia" <saperia@jdscons.com>
> >> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> >> Cc: <ops-area@ietf.org>
> >> Sent: Wednesday, June 23, 2010 3:54 PM
> >> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
> >>
> >> Why would a whole new set of objects be required to either fix,
> >> hrSystemUptime, or create a new higher capacity object?
> >
> > The question wasn't just about hrSystemUptime, but the fundamental
> > deficiency of time ticks.
> >
> > Coming up with a new time ticks syntax would effectively mean
> > every existing time ticks object would at least need to be
> > considered for obsolescence, and new objects would need
> > to be created in appropriate cases.  Counters currently referencing those
> > time ticks objects as discontinuity indicators would then have to be
> > considered for update as well, unless we were going to say that
> > implementations MUST support both representations.  (This quickly
> > becomes a replay of the 32-bit counter / 64-bit counter / paired-counter
> > discussion from SMIv2.)
> >
> > But that really wouldn't address the problem - an existing NMS
> > application that behaves badly when hrSystemUptime wraps.
> >
> > Randy
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>

--e0cb4e8876f13f41ff0489bc6a47
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi- <br><br>I would anticipate that an intelligently designed NMS would wat=
ch for wrap on a TimeTicks object by checking for an increment in snmpEngin=
eBoots, or alternatively, simply watch the value of the snmpEngineTime obje=
ct, since its granularity is seconds rather than 1/100th seconds yielding a=
 40k+ day wrap interval.<br>
<br>In any case, the target system sure isn&#39;t running a MS OS ;-)<br><b=
r>Regards,<br><br>Mark<br>--<br><a href=3D"http://EllisonSoftware.com/">htt=
p://EllisonSoftware.com/</a><br><br><div class=3D"gmail_quote">On Wed, Jun =
23, 2010 at 7:43 PM, Jon Saperia <span dir=3D"ltr">&lt;<a href=3D"mailto:sa=
peria@jdscons.com">saperia@jdscons.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">But is was in the=
 context specifically of hrSystemUptime - at least that is how I read it. =
=A0I was suggesting a surgical fix to a specific problem related to uptime.=
 =A0That could be fixed with a single object and leave the others that use =
time ticks intact.<br>

<br>
That said, I do agree with you that a good NMS should be able to deal with =
this and other oddities in this and many other objects.<br>
<font color=3D"#888888"><br>
/jon<br>
</font><div><div></div><div class=3D"h5">On Jun 23, 2010, at 7:30 PM, Randy=
 Presuhn wrote:<br>
<br>
&gt; Hi -<br>
&gt;<br>
&gt;&gt; From: &quot;Jon Saperia&quot; &lt;<a href=3D"mailto:saperia@jdscon=
s.com">saperia@jdscons.com</a>&gt;<br>
&gt;&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_presuhn@=
mindspring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt;&gt; Cc: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a>=
&gt;<br>
&gt;&gt; Sent: Wednesday, June 23, 2010 3:54 PM<br>
&gt;&gt; Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value<br=
>
&gt;&gt;<br>
&gt;&gt; Why would a whole new set of objects be required to either fix,<br=
>
&gt;&gt; hrSystemUptime, or create a new higher capacity object?<br>
&gt;<br>
&gt; The question wasn&#39;t just about hrSystemUptime, but the fundamental=
<br>
&gt; deficiency of time ticks.<br>
&gt;<br>
&gt; Coming up with a new time ticks syntax would effectively mean<br>
&gt; every existing time ticks object would at least need to be<br>
&gt; considered for obsolescence, and new objects would need<br>
&gt; to be created in appropriate cases. =A0Counters currently referencing =
those<br>
&gt; time ticks objects as discontinuity indicators would then have to be<b=
r>
&gt; considered for update as well, unless we were going to say that<br>
&gt; implementations MUST support both representations. =A0(This quickly<br=
>
&gt; becomes a replay of the 32-bit counter / 64-bit counter / paired-count=
er<br>
&gt; discussion from SMIv2.)<br>
&gt;<br>
&gt; But that really wouldn&#39;t address the problem - an existing NMS<br>
&gt; application that behaves badly when hrSystemUptime wraps.<br>
&gt;<br>
&gt; Randy<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;<br>
<br>
_______________________________________________<br>
OPS-AREA mailing list<br>
<a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
</div></div></blockquote></div><br><br>

--e0cb4e8876f13f41ff0489bc6a47--

From gmatusov@cablevision.com  Thu Jun 24 08:57:46 2010
Return-Path: <gmatusov@cablevision.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A12D3A6403 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 08:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.563
X-Spam-Level: *
X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[AWL=-0.574,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubksMhxXRS+9 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 08:57:45 -0700 (PDT)
Received: from cscpsmout02.cablevision.com (cscpsmout02.cablevision.com [167.206.119.145]) by core3.amsl.com (Postfix) with ESMTP id 036663A67CF for <ops-area@ietf.org>; Thu, 24 Jun 2010 08:57:44 -0700 (PDT)
Received: from c2gwiaoutvs.cablevision.com (c2gwiaoutvs.cablevision.com [10.128.36.152]) by cscpsmout02.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o5OFvkYL014584 for <ops-area@ietf.org>; Thu, 24 Jun 2010 11:57:46 -0400
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout02.cablevision.com o5OFvkYL014584
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1277395067; bh=WWTB4Ax+VVuXEn/Lp1ExIiR2KkGvQ/jM9Euv5UT dO6A=; h=Message-Id:Date:From:To:Cc:Subject:References:In-Reply-To: Mime-Version:Content-Type:Content-Transfer-Encoding; b=sQH/xRjEqVn iP8q+YZ7nrfyn97XmGnXAMFOaEhCr2272Q7CwWeOH0ubqpiz4l/6Nnwmih2H1KNdmrt HaUoFp3bEUAtaFPZOnTAda3OavpUoaVuV18etWNcuq/gCE9+eLMrxqbBVisUyf14pRN VNIkscKF1N3Ib+CtEtj2QIiLSw=
Received: from C2GWIAOUTDOM-MTA by c2gwiaoutvs.cablevision.com with Novell_GroupWise; Thu, 24 Jun 2010 11:57:46 -0400
Message-Id: <4C23481C.54CB.00CA.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.4 
Date: Thu, 24 Jun 2010 11:57:42 -0400
From: "Gene Matusovsky" <gmatusov@cablevision.com>
To: "Mark Ellison" <ellison@ieee.org>, "Jon Saperia" <saperia@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com>
In-Reply-To: <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Auth-Type: Internal IP
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 15:57:46 -0000

Thanks to all on the IETF list for providing solutions and suggestions that could be used to work around the existing 32bit Timetick limit. In our case, our SNMP agent vendor does not currently support snmpEngineTime or snmpEngineBoots. I will ask the developer to look into supporting these objects.

Perhaps another suggestion to the IETF board would be to define a new HC ASN1 Timeticks data type? This would provide compatibility to existing systems using the 32bit Timeticks, and give flexibility to agent developers to use a higher capacity Timeticks data type.

I believe something similar was done with IfInOctets/IfOutOctets when they were extended to "HC" High Capacity 64bit counters in RFC 2863.

On another note, does anyone know a case where a SNMP agent vendor/developer might have "broken the standard" and used 64bit counters for IfInOctets, IfOutOctets or TimeTicks 
Would this break anything in a closed island type Enterprise network? I am considering asking our SNMP agent developer to use 64bit data type for Timeticks on the agent. The NMS system doesn't care or check for standards, it just treats hrSystemUptime as an infinite increasing counter.

-Thanks,
Gene Matusovsky


>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
Hi-

I would anticipate that an intelligently designed NMS would watch for wrap
on a TimeTicks object by checking for an increment in snmpEngineBoots, or
alternatively, simply watch the value of the snmpEngineTime object, since
its granularity is seconds rather than 1/100th seconds yielding a 40k+ day
wrap interval.

In any case, the target system sure isn't running a MS OS ;-)

Regards,

Mark
--
http://EllisonSoftware.com/ 

On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com> wrote:

> But is was in the context specifically of hrSystemUptime - at least that is
> how I read it.  I was suggesting a surgical fix to a specific problem
> related to uptime.  That could be fixed with a single object and leave the
> others that use time ticks intact.
>
> That said, I do agree with you that a good NMS should be able to deal with
> this and other oddities in this and many other objects.
>
> /jon
> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
>
> > Hi -
> >
> >> From: "Jon Saperia" <saperia@jdscons.com>
> >> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> >> Cc: <ops-area@ietf.org>
> >> Sent: Wednesday, June 23, 2010 3:54 PM
> >> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
> >>
> >> Why would a whole new set of objects be required to either fix,
> >> hrSystemUptime, or create a new higher capacity object?
> >
> > The question wasn't just about hrSystemUptime, but the fundamental
> > deficiency of time ticks.
> >
> > Coming up with a new time ticks syntax would effectively mean
> > every existing time ticks object would at least need to be
> > considered for obsolescence, and new objects would need
> > to be created in appropriate cases.  Counters currently referencing those
> > time ticks objects as discontinuity indicators would then have to be
> > considered for update as well, unless we were going to say that
> > implementations MUST support both representations.  (This quickly
> > becomes a replay of the 32-bit counter / 64-bit counter / paired-counter
> > discussion from SMIv2.)
> >
> > But that really wouldn't address the problem - an existing NMS
> > application that behaves badly when hrSystemUptime wraps.
> >
> > Randy
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org 
> > https://www.ietf.org/mailman/listinfo/ops-area 
> >
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org 
> https://www.ietf.org/mailman/listinfo/ops-area 
>


-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------

From saperia@jdscons.com  Thu Jun 24 09:57:28 2010
Return-Path: <saperia@jdscons.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85D023A67E3 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 09:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.019
X-Spam-Level: 
X-Spam-Status: No, score=-1.019 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLPBnsUzg8v3 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 09:57:27 -0700 (PDT)
Received: from rs69.luxsci.com (rs69.luxsci.com [64.49.254.154]) by core3.amsl.com (Postfix) with ESMTP id 57DF13A67FB for <ops-area@ietf.org>; Thu, 24 Jun 2010 09:57:27 -0700 (PDT)
Received: from [10.0.1.2] (c-98-229-133-101.hsd1.ma.comcast.net [98.229.133.101]) (authenticated bits=0) by rs69.luxsci.com (8.13.8/8.13.8) with ESMTP id o5OGvUqH009859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Jun 2010 11:57:31 -0500
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Jon Saperia <saperia@jdscons.com>
In-Reply-To: <4C23481C.54CB.00CA.0@cablevision.com>
Date: Thu, 24 Jun 2010 12:57:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com>
To: Gene Matusovsky <gmatusov@cablevision.com>
X-Mailer: Apple Mail (2.1081)
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 16:57:28 -0000

Others may, but I am not aware of an implementation of hrSystemUptime as =
a 64-bit value.  One other solution that would not require a MIB object =
change since you seem to have development resources available is to fix =
the NMS.  A simple solution is to watch for the counter wrap in a way =
that is similar to what people have done for interfaces.

Your suggestion about exploring HC timeticks data objects is =
interesting, but that would require a working group taking up the =
activity.

/jon
On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:

> Thanks to all on the IETF list for providing solutions and suggestions =
that could be used to work around the existing 32bit Timetick limit. In =
our case, our SNMP agent vendor does not currently support =
snmpEngineTime or snmpEngineBoots. I will ask the developer to look into =
supporting these objects.
>=20
> Perhaps another suggestion to the IETF board would be to define a new =
HC ASN1 Timeticks data type? This would provide compatibility to =
existing systems using the 32bit Timeticks, and give flexibility to =
agent developers to use a higher capacity Timeticks data type.
>=20
> I believe something similar was done with IfInOctets/IfOutOctets when =
they were extended to "HC" High Capacity 64bit counters in RFC 2863.
>=20
> On another note, does anyone know a case where a SNMP agent =
vendor/developer might have "broken the standard" and used 64bit =
counters for IfInOctets, IfOutOctets or TimeTicks=20
> Would this break anything in a closed island type Enterprise network? =
I am considering asking our SNMP agent developer to use 64bit data type =
for Timeticks on the agent. The NMS system doesn't care or check for =
standards, it just treats hrSystemUptime as an infinite increasing =
counter.
>=20
> -Thanks,
> Gene Matusovsky
>=20
>=20
>>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
> Hi-
>=20
> I would anticipate that an intelligently designed NMS would watch for =
wrap
> on a TimeTicks object by checking for an increment in snmpEngineBoots, =
or
> alternatively, simply watch the value of the snmpEngineTime object, =
since
> its granularity is seconds rather than 1/100th seconds yielding a 40k+ =
day
> wrap interval.
>=20
> In any case, the target system sure isn't running a MS OS ;-)
>=20
> Regards,
>=20
> Mark
> --
> http://EllisonSoftware.com/=20
>=20
> On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com> =
wrote:
>=20
>> But is was in the context specifically of hrSystemUptime - at least =
that is
>> how I read it.  I was suggesting a surgical fix to a specific problem
>> related to uptime.  That could be fixed with a single object and =
leave the
>> others that use time ticks intact.
>>=20
>> That said, I do agree with you that a good NMS should be able to deal =
with
>> this and other oddities in this and many other objects.
>>=20
>> /jon
>> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
>>=20
>>> Hi -
>>>=20
>>>> From: "Jon Saperia" <saperia@jdscons.com>
>>>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
>>>> Cc: <ops-area@ietf.org>
>>>> Sent: Wednesday, June 23, 2010 3:54 PM
>>>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>>>>=20
>>>> Why would a whole new set of objects be required to either fix,
>>>> hrSystemUptime, or create a new higher capacity object?
>>>=20
>>> The question wasn't just about hrSystemUptime, but the fundamental
>>> deficiency of time ticks.
>>>=20
>>> Coming up with a new time ticks syntax would effectively mean
>>> every existing time ticks object would at least need to be
>>> considered for obsolescence, and new objects would need
>>> to be created in appropriate cases.  Counters currently referencing =
those
>>> time ticks objects as discontinuity indicators would then have to be
>>> considered for update as well, unless we were going to say that
>>> implementations MUST support both representations.  (This quickly
>>> becomes a replay of the 32-bit counter / 64-bit counter / =
paired-counter
>>> discussion from SMIv2.)
>>>=20
>>> But that really wouldn't address the problem - an existing NMS
>>> application that behaves badly when hrSystemUptime wraps.
>>>=20
>>> Randy
>>>=20
>>> _______________________________________________
>>> OPS-AREA mailing list
>>> OPS-AREA@ietf.org=20
>>> https://www.ietf.org/mailman/listinfo/ops-area=20
>>>=20
>>=20
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org=20
>> https://www.ietf.org/mailman/listinfo/ops-area=20
>>=20
>=20
>=20
> --------------------------------------------------------=20
> The information transmitted in this email and any of its attachments =
is intended only for the person or entity to which it is addressed and =
may contain information concerning Cablevision and/or its affiliates and =
subsidiaries that is proprietary, privileged, confidential and/or =
subject to copyright.   Any review, retransmission, dissemination or =
other use of, or taking of any action in reliance upon, this information =
by persons or entities other than the intended recipient(s) is =
prohibited and may be unlawful.  If you received this in error, please =
contact the sender immediately and delete and destroy the communication =
and all of the attachments you have received and all copies thereof.
> --------------------------------------------------------
>=20


From mrm@vmware.com  Thu Jun 24 10:02:59 2010
Return-Path: <mrm@vmware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20ADD3A6359 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 10:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.185
X-Spam-Level: 
X-Spam-Status: No, score=-104.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olSB5oN6CE4S for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 10:02:58 -0700 (PDT)
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [65.115.85.73]) by core3.amsl.com (Postfix) with ESMTP id 6ACA73A6831 for <ops-area@ietf.org>; Thu, 24 Jun 2010 10:02:58 -0700 (PDT)
Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 240124200F; Thu, 24 Jun 2010 10:03:07 -0700 (PDT)
Received: from pa-excaht04.vmware.com (pa-excaht04.vmware.com [10.113.81.155]) by mailhost2.vmware.com (Postfix) with ESMTP id 12E9A8E839; Thu, 24 Jun 2010 10:03:07 -0700 (PDT)
Received: from EXCH-MBX-3.vmware.com ([10.113.81.228]) by pa-excaht04.vmware.com ([10.113.81.155]) with mapi; Thu, 24 Jun 2010 10:03:07 -0700
From: Michael MacFaden <mrm@vmware.com>
To: Gene Matusovsky <gmatusov@cablevision.com>, Mark Ellison <ellison@ieee.org>, Jon Saperia <saperia@jdscons.com>
Date: Thu, 24 Jun 2010 10:01:22 -0700
Thread-Topic: [OPS-AREA] RFC1155 Timeticks hitting maximum value
Thread-Index: AcsTtgQKxPU1RKMuTYWVxTMWQDEHsAACNtKo
Message-ID: <35203D411DF5144CACC340A56A90E564043DE5E6A8@EXCH-MBX-3.vmware.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com>, <4C23481C.54CB.00CA.0@cablevision.com>
In-Reply-To: <4C23481C.54CB.00CA.0@cablevision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ops-area@ietf.org" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 17:02:59 -0000

From: ops-area-bounces@ietf.org [ops-area-bounces@ietf.org] On Behalf Of Ge=
ne Matusovsky [gmatusov@cablevision.com]
>On another note, does anyone know a case where a SNMP agent vendor/develop=
er might have "broken the standard" and used 64bit counters for IfInOctets,=
 IfOutOctets or TimeTicks
>Would this break anything in a closed island type Enterprise network?=20

The common 'breakage' that I'm aware is to not to change the syntax existin=
g counters such as ifInOctets
but to report 64 bit counters ifHCInOctets in SNMPv1.

Mike MacFaden

From gmatusov@cablevision.com  Thu Jun 24 12:01:03 2010
Return-Path: <gmatusov@cablevision.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2C013A6A51 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 12:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.122
X-Spam-Level: *
X-Spam-Status: No, score=1.122 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_05=-1.11, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHWPeTUh95rv for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 12:01:02 -0700 (PDT)
Received: from cscpsmout02.cablevision.com (cscpsmout02.cablevision.com [167.206.119.145]) by core3.amsl.com (Postfix) with ESMTP id E52F83A6A58 for <ops-area@ietf.org>; Thu, 24 Jun 2010 12:00:45 -0700 (PDT)
Received: from c2gwiaoutvs.cablevision.com (c2gwiaoutvs.cablevision.com [10.128.36.152]) by cscpsmout02.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o5OJ0pGq010455 for <ops-area@ietf.org>; Thu, 24 Jun 2010 15:00:51 -0400
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout02.cablevision.com o5OJ0pGq010455
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1277406051; bh=t7rGKCHCTchY2eugvmnWZFhdmwQiZQZ0gMkM0CC lujQ=; h=Message-Id:Date:From:To:Cc:Subject:References:In-Reply-To: Mime-Version:Content-Type:Content-Transfer-Encoding; b=TJfjpxViOJE aall50yMByfa1fpHc0MFI1PbWH0yXrw+wcZ5Gx90lH/nEIl8n3sgQE0bYnjXe3M8xeh L9dcp2BlWURHV0RQxIKEtZHbyh7SKz/5pSz6EEEYNFgPrYAiwOZatozvzPhBWYWW/Ud Zl2BzrOCy5S+2DIfYhF4icOQqI=
Received: from C2GWIAOUTDOM-MTA by c2gwiaoutvs.cablevision.com with Novell_GroupWise; Thu, 24 Jun 2010 15:00:51 -0400
Message-Id: <4C237304.54CB.00CA.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.4 
Date: Thu, 24 Jun 2010 15:00:47 -0400
From: "Gene Matusovsky" <gmatusov@cablevision.com>
To: "Jon Saperia" <saperia@jdscons.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com> <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com>
In-Reply-To: <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Auth-Type: Internal IP
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 19:01:04 -0000

Workarounds are possible, and can be done, but not everyone has development resources. With todays technology and higher capacity systems, the root of the issue can be addressed directly by extending RFC 1155/ 1902 Timeticks data type. This was done before with RFC 2863, when IfInOctets was updated to IfHCInOctets.

Are there any existing SNMP workgroups or ongoing projects. Perhaps this can be suggested to them, to attach to the next published RFC?

Any pointers would be appreciated.

-Thank You,
Gene Matusovsky

>>> Jon Saperia <saperia@jdscons.com> 6/24/2010 12:57 PM >>>
Others may, but I am not aware of an implementation of hrSystemUptime as a 64-bit value.  One other solution that would not require a MIB object change since you seem to have development resources available is to fix the NMS.  A simple solution is to watch for the counter wrap in a way that is similar to what people have done for interfaces.

Your suggestion about exploring HC timeticks data objects is interesting, but that would require a working group taking up the activity.

/jon
On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:

> Thanks to all on the IETF list for providing solutions and suggestions that could be used to work around the existing 32bit Timetick limit. In our case, our SNMP agent vendor does not currently support snmpEngineTime or snmpEngineBoots. I will ask the developer to look into supporting these objects.
> 
> Perhaps another suggestion to the IETF board would be to define a new HC ASN1 Timeticks data type? This would provide compatibility to existing systems using the 32bit Timeticks, and give flexibility to agent developers to use a higher capacity Timeticks data type.
> 
> I believe something similar was done with IfInOctets/IfOutOctets when they were extended to "HC" High Capacity 64bit counters in RFC 2863.
> 
> On another note, does anyone know a case where a SNMP agent vendor/developer might have "broken the standard" and used 64bit counters for IfInOctets, IfOutOctets or TimeTicks 
> Would this break anything in a closed island type Enterprise network? I am considering asking our SNMP agent developer to use 64bit data type for Timeticks on the agent. The NMS system doesn't care or check for standards, it just treats hrSystemUptime as an infinite increasing counter.
> 
> -Thanks,
> Gene Matusovsky
> 
> 
>>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
> Hi-
> 
> I would anticipate that an intelligently designed NMS would watch for wrap
> on a TimeTicks object by checking for an increment in snmpEngineBoots, or
> alternatively, simply watch the value of the snmpEngineTime object, since
> its granularity is seconds rather than 1/100th seconds yielding a 40k+ day
> wrap interval.
> 
> In any case, the target system sure isn't running a MS OS ;-)
> 
> Regards,
> 
> Mark
> --
> http://EllisonSoftware.com/ 
> 
> On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com> wrote:
> 
>> But is was in the context specifically of hrSystemUptime - at least that is
>> how I read it.  I was suggesting a surgical fix to a specific problem
>> related to uptime.  That could be fixed with a single object and leave the
>> others that use time ticks intact.
>> 
>> That said, I do agree with you that a good NMS should be able to deal with
>> this and other oddities in this and many other objects.
>> 
>> /jon
>> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
>> 
>>> Hi -
>>> 
>>>> From: "Jon Saperia" <saperia@jdscons.com>
>>>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
>>>> Cc: <ops-area@ietf.org>
>>>> Sent: Wednesday, June 23, 2010 3:54 PM
>>>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>>>> 
>>>> Why would a whole new set of objects be required to either fix,
>>>> hrSystemUptime, or create a new higher capacity object?
>>> 
>>> The question wasn't just about hrSystemUptime, but the fundamental
>>> deficiency of time ticks.
>>> 
>>> Coming up with a new time ticks syntax would effectively mean
>>> every existing time ticks object would at least need to be
>>> considered for obsolescence, and new objects would need
>>> to be created in appropriate cases.  Counters currently referencing those
>>> time ticks objects as discontinuity indicators would then have to be
>>> considered for update as well, unless we were going to say that
>>> implementations MUST support both representations.  (This quickly
>>> becomes a replay of the 32-bit counter / 64-bit counter / paired-counter
>>> discussion from SMIv2.)
>>> 
>>> But that really wouldn't address the problem - an existing NMS
>>> application that behaves badly when hrSystemUptime wraps.
>>> 
>>> Randy
>>> 
>>> _______________________________________________
>>> OPS-AREA mailing list
>>> OPS-AREA@ietf.org 
>>> https://www.ietf.org/mailman/listinfo/ops-area 
>>> 
>> 
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org 
>> https://www.ietf.org/mailman/listinfo/ops-area 
>> 
> 
> 
> -------------------------------------------------------- 
> The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
> --------------------------------------------------------
> 


-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------

From mark@ellisonsoftware.com  Thu Jun 24 13:38:07 2010
Return-Path: <mark@ellisonsoftware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73C7B3A69C5 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 13:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.046
X-Spam-Level: 
X-Spam-Status: No, score=-101.046 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVTkduW0fwFb for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 13:38:05 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id CD3C83A69C6 for <ops-area@ietf.org>; Thu, 24 Jun 2010 13:38:04 -0700 (PDT)
Received: by mail-vw0-f44.google.com with SMTP id 2so313956vws.31 for <ops-area@ietf.org>; Thu, 24 Jun 2010 13:38:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.126.216 with SMTP id d24mr5486509vcs.43.1277411892778;  Thu, 24 Jun 2010 13:38:12 -0700 (PDT)
Sender: mark@ellisonsoftware.com
Received: by 10.220.181.9 with HTTP; Thu, 24 Jun 2010 13:38:11 -0700 (PDT)
In-Reply-To: <4C237304.54CB.00CA.0@cablevision.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com> <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com> <4C237304.54CB.00CA.0@cablevision.com>
Date: Thu, 24 Jun 2010 16:38:11 -0400
X-Google-Sender-Auth: gYbvQ5mpqqCn5N2MTqLo0vra0ks
Message-ID: <AANLkTim3REIt837sAkjeTW7tV0XMbuilu9FEFdHBKA70@mail.gmail.com>
From: Mark Ellison <ellison@ieee.org>
To: Gene Matusovsky <gmatusov@cablevision.com>
Content-Type: multipart/alternative; boundary=00504501635c1a2f390489cca2e9
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 20:38:07 -0000

--00504501635c1a2f390489cca2e9
Content-Type: text/plain; charset=ISO-8859-1

Gene,

Agreed, not everyone has development resources.

However, consider for a moment what you are asking for-  an "HC" version of
hrSystemUptime.  "HC" counters were introduced for the IF-MIB to handle wrap
situations that could occur every few minutes.  In the original post in this
thread, it was noted that hrSystemUpTime can wrap once every 497 days-
approximately every 16 months.

Even if an "HC" version of hrSystemUptime were designed, it would still need
to be implemented within the agents that the NMS will monitor- this would
take development resources, just as would implementing snmpEngineBoots and
snmpEngineTime.  Since the agent being monitored does not support these two
objects, one can safely assume that agent does not support SNMPv3.  In order
to support 64-bit counters, at least SNMPv2c is required since SNMPv1 does
not provide support for "HC" 64-bit counters.  Note that an agent that
implements SNMPv3 can be configured to allow retrieval of the snmpEngineTime
and snmpEngineBoots values via SNMPv2c or SNMPv1 protocol messages.

So, if the agent needs to be changed anyway to support a new object, the
approach that appears obvious to me, would be to upgrade the agent to
include compliant support for SNMPv3, which would make available the
snmpEngineBoots and snmpEngineTime objects for use with the NMS.

Hope this helps!

Regards,

Mark
http://EllisonSoftware.com

On Thu, Jun 24, 2010 at 3:00 PM, Gene Matusovsky
<gmatusov@cablevision.com>wrote:

> Workarounds are possible, and can be done, but not everyone has development
> resources. With todays technology and higher capacity systems, the root of
> the issue can be addressed directly by extending RFC 1155/ 1902 Timeticks
> data type. This was done before with RFC 2863, when IfInOctets was updated
> to IfHCInOctets.
>
> Are there any existing SNMP workgroups or ongoing projects. Perhaps this
> can be suggested to them, to attach to the next published RFC?
>
> Any pointers would be appreciated.
>
> -Thank You,
> Gene Matusovsky
>
> >>> Jon Saperia <saperia@jdscons.com> 6/24/2010 12:57 PM >>>
> Others may, but I am not aware of an implementation of hrSystemUptime as a
> 64-bit value.  One other solution that would not require a MIB object change
> since you seem to have development resources available is to fix the NMS.  A
> simple solution is to watch for the counter wrap in a way that is similar to
> what people have done for interfaces.
>
> Your suggestion about exploring HC timeticks data objects is interesting,
> but that would require a working group taking up the activity.
>
> /jon
> On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:
>
> > Thanks to all on the IETF list for providing solutions and suggestions
> that could be used to work around the existing 32bit Timetick limit. In our
> case, our SNMP agent vendor does not currently support snmpEngineTime or
> snmpEngineBoots. I will ask the developer to look into supporting these
> objects.
> >
> > Perhaps another suggestion to the IETF board would be to define a new HC
> ASN1 Timeticks data type? This would provide compatibility to existing
> systems using the 32bit Timeticks, and give flexibility to agent developers
> to use a higher capacity Timeticks data type.
> >
> > I believe something similar was done with IfInOctets/IfOutOctets when
> they were extended to "HC" High Capacity 64bit counters in RFC 2863.
> >
> > On another note, does anyone know a case where a SNMP agent
> vendor/developer might have "broken the standard" and used 64bit counters
> for IfInOctets, IfOutOctets or TimeTicks
> > Would this break anything in a closed island type Enterprise network? I
> am considering asking our SNMP agent developer to use 64bit data type for
> Timeticks on the agent. The NMS system doesn't care or check for standards,
> it just treats hrSystemUptime as an infinite increasing counter.
> >
> > -Thanks,
> > Gene Matusovsky
> >
> >
> >>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
> > Hi-
> >
> > I would anticipate that an intelligently designed NMS would watch for
> wrap
> > on a TimeTicks object by checking for an increment in snmpEngineBoots, or
> > alternatively, simply watch the value of the snmpEngineTime object, since
> > its granularity is seconds rather than 1/100th seconds yielding a 40k+
> day
> > wrap interval.
> >
> > In any case, the target system sure isn't running a MS OS ;-)
> >
> > Regards,
> >
> > Mark
> > --
> > http://EllisonSoftware.com/
> >
> > On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com>
> wrote:
> >
> >> But is was in the context specifically of hrSystemUptime - at least that
> is
> >> how I read it.  I was suggesting a surgical fix to a specific problem
> >> related to uptime.  That could be fixed with a single object and leave
> the
> >> others that use time ticks intact.
> >>
> >> That said, I do agree with you that a good NMS should be able to deal
> with
> >> this and other oddities in this and many other objects.
> >>
> >> /jon
> >> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
> >>
> >>> Hi -
> >>>
> >>>> From: "Jon Saperia" <saperia@jdscons.com>
> >>>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> >>>> Cc: <ops-area@ietf.org>
> >>>> Sent: Wednesday, June 23, 2010 3:54 PM
> >>>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
> >>>>
> >>>> Why would a whole new set of objects be required to either fix,
> >>>> hrSystemUptime, or create a new higher capacity object?
> >>>
> >>> The question wasn't just about hrSystemUptime, but the fundamental
> >>> deficiency of time ticks.
> >>>
> >>> Coming up with a new time ticks syntax would effectively mean
> >>> every existing time ticks object would at least need to be
> >>> considered for obsolescence, and new objects would need
> >>> to be created in appropriate cases.  Counters currently referencing
> those
> >>> time ticks objects as discontinuity indicators would then have to be
> >>> considered for update as well, unless we were going to say that
> >>> implementations MUST support both representations.  (This quickly
> >>> becomes a replay of the 32-bit counter / 64-bit counter /
> paired-counter
> >>> discussion from SMIv2.)
> >>>
> >>> But that really wouldn't address the problem - an existing NMS
> >>> application that behaves badly when hrSystemUptime wraps.
> >>>
> >>> Randy
> >>>
> >>> _______________________________________________
> >>> OPS-AREA mailing list
> >>> OPS-AREA@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ops-area
> >>>
> >>
> >> _______________________________________________
> >> OPS-AREA mailing list
> >> OPS-AREA@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ops-area
> >>
> >
> >
> > --------------------------------------------------------
> > The information transmitted in this email and any of its attachments is
> intended only for the person or entity to which it is addressed and may
> contain information concerning Cablevision and/or its affiliates and
> subsidiaries that is proprietary, privileged, confidential and/or subject to
> copyright.   Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient(s) is prohibited and may be
> unlawful.  If you received this in error, please contact the sender
> immediately and delete and destroy the communication and all of the
> attachments you have received and all copies thereof.
> > --------------------------------------------------------
> >
>
>
> --------------------------------------------------------
> The information transmitted in this email and any of its attachments is
> intended only for the person or entity to which it is addressed and may
> contain information concerning Cablevision and/or its affiliates and
> subsidiaries that is proprietary, privileged, confidential and/or subject to
> copyright.   Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient(s) is prohibited and may be
> unlawful.  If you received this in error, please contact the sender
> immediately and delete and destroy the communication and all of the
> attachments you have received and all copies thereof.
> --------------------------------------------------------
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>

--00504501635c1a2f390489cca2e9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Gene,<br><br>Agreed, not everyone has development resources.<br><br>However=
, consider for a moment what you are asking for-=A0 an &quot;HC&quot; versi=
on of hrSystemUptime.=A0 &quot;HC&quot; counters were introduced for the IF=
-MIB to handle wrap situations that could occur every few minutes.=A0 In th=
e original post in this thread, it was noted that hrSystemUpTime can wrap o=
nce every 497 days- approximately every 16 months.<br>
<br>Even if an &quot;HC&quot; version of hrSystemUptime were designed, it w=
ould still need to be implemented within the agents that the NMS will monit=
or- this would take development resources, just as would implementing snmpE=
ngineBoots and snmpEngineTime.=A0 Since the agent being monitored does not =
support these two objects, one can safely assume that agent does not suppor=
t SNMPv3.=A0 In order to support 64-bit counters, at least SNMPv2c is requi=
red since SNMPv1 does not provide support for &quot;HC&quot; 64-bit counter=
s.=A0 Note that an agent that implements SNMPv3 can be configured to allow =
retrieval of the snmpEngineTime and snmpEngineBoots values via SNMPv2c or S=
NMPv1 protocol messages.<br>
<br>So, if the agent needs to be changed anyway to support a new object, th=
e approach that appears obvious to me, would be to upgrade the agent to inc=
lude compliant support for SNMPv3, which would make available the snmpEngin=
eBoots and snmpEngineTime objects for use with the NMS.<br>
<br>Hope this helps!<br><br>Regards,<br><br>Mark<br><a href=3D"http://Ellis=
onSoftware.com">http://EllisonSoftware.com</a><br><br><div class=3D"gmail_q=
uote">On Thu, Jun 24, 2010 at 3:00 PM, Gene Matusovsky <span dir=3D"ltr">&l=
t;<a href=3D"mailto:gmatusov@cablevision.com">gmatusov@cablevision.com</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Workarounds are p=
ossible, and can be done, but not everyone has development resources. With =
todays technology and higher capacity systems, the root of the issue can be=
 addressed directly by extending RFC 1155/ 1902 Timeticks data type. This w=
as done before with RFC 2863, when IfInOctets was updated to IfHCInOctets.<=
br>

<br>
Are there any existing SNMP workgroups or ongoing projects. Perhaps this ca=
n be suggested to them, to attach to the next published RFC?<br>
<br>
Any pointers would be appreciated.<br>
<br>
-Thank You,<br>
Gene Matusovsky<br>
<br>
&gt;&gt;&gt; Jon Saperia &lt;<a href=3D"mailto:saperia@jdscons.com">saperia=
@jdscons.com</a>&gt; 6/24/2010 12:57 PM &gt;&gt;&gt;<br>
<div><div></div><div class=3D"h5">Others may, but I am not aware of an impl=
ementation of hrSystemUptime as a 64-bit value. =A0One other solution that =
would not require a MIB object change since you seem to have development re=
sources available is to fix the NMS. =A0A simple solution is to watch for t=
he counter wrap in a way that is similar to what people have done for inter=
faces.<br>

<br>
Your suggestion about exploring HC timeticks data objects is interesting, b=
ut that would require a working group taking up the activity.<br>
<br>
/jon<br>
On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:<br>
<br>
&gt; Thanks to all on the IETF list for providing solutions and suggestions=
 that could be used to work around the existing 32bit Timetick limit. In ou=
r case, our SNMP agent vendor does not currently support snmpEngineTime or =
snmpEngineBoots. I will ask the developer to look into supporting these obj=
ects.<br>

&gt;<br>
&gt; Perhaps another suggestion to the IETF board would be to define a new =
HC ASN1 Timeticks data type? This would provide compatibility to existing s=
ystems using the 32bit Timeticks, and give flexibility to agent developers =
to use a higher capacity Timeticks data type.<br>

&gt;<br>
&gt; I believe something similar was done with IfInOctets/IfOutOctets when =
they were extended to &quot;HC&quot; High Capacity 64bit counters in RFC 28=
63.<br>
&gt;<br>
&gt; On another note, does anyone know a case where a SNMP agent vendor/dev=
eloper might have &quot;broken the standard&quot; and used 64bit counters f=
or IfInOctets, IfOutOctets or TimeTicks<br>
&gt; Would this break anything in a closed island type Enterprise network? =
I am considering asking our SNMP agent developer to use 64bit data type for=
 Timeticks on the agent. The NMS system doesn&#39;t care or check for stand=
ards, it just treats hrSystemUptime as an infinite increasing counter.<br>

&gt;<br>
&gt; -Thanks,<br>
&gt; Gene Matusovsky<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt;&gt; Mark Ellison &lt;<a href=3D"mailto:ellison@ieee.org">ellis=
on@ieee.org</a>&gt; 6/23/2010 9:17 PM &gt;&gt;&gt;<br>
&gt; Hi-<br>
&gt;<br>
&gt; I would anticipate that an intelligently designed NMS would watch for =
wrap<br>
&gt; on a TimeTicks object by checking for an increment in snmpEngineBoots,=
 or<br>
&gt; alternatively, simply watch the value of the snmpEngineTime object, si=
nce<br>
&gt; its granularity is seconds rather than 1/100th seconds yielding a 40k+=
 day<br>
&gt; wrap interval.<br>
&gt;<br>
&gt; In any case, the target system sure isn&#39;t running a MS OS ;-)<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Mark<br>
&gt; --<br>
&gt; <a href=3D"http://EllisonSoftware.com/" target=3D"_blank">http://Ellis=
onSoftware.com/</a><br>
&gt;<br>
&gt; On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia &lt;<a href=3D"mailto:sap=
eria@jdscons.com">saperia@jdscons.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; But is was in the context specifically of hrSystemUptime - at leas=
t that is<br>
&gt;&gt; how I read it. =A0I was suggesting a surgical fix to a specific pr=
oblem<br>
&gt;&gt; related to uptime. =A0That could be fixed with a single object and=
 leave the<br>
&gt;&gt; others that use time ticks intact.<br>
&gt;&gt;<br>
&gt;&gt; That said, I do agree with you that a good NMS should be able to d=
eal with<br>
&gt;&gt; this and other oddities in this and many other objects.<br>
&gt;&gt;<br>
&gt;&gt; /jon<br>
&gt;&gt; On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; Hi -<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From: &quot;Jon Saperia&quot; &lt;<a href=3D"mailto:saperi=
a@jdscons.com">saperia@jdscons.com</a>&gt;<br>
&gt;&gt;&gt;&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_=
presuhn@mindspring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt;&gt;&gt;&gt; Cc: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-area@ietf=
.org</a>&gt;<br>
&gt;&gt;&gt;&gt; Sent: Wednesday, June 23, 2010 3:54 PM<br>
&gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum =
value<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Why would a whole new set of objects be required to either=
 fix,<br>
&gt;&gt;&gt;&gt; hrSystemUptime, or create a new higher capacity object?<br=
>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The question wasn&#39;t just about hrSystemUptime, but the fun=
damental<br>
&gt;&gt;&gt; deficiency of time ticks.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Coming up with a new time ticks syntax would effectively mean<=
br>
&gt;&gt;&gt; every existing time ticks object would at least need to be<br>
&gt;&gt;&gt; considered for obsolescence, and new objects would need<br>
&gt;&gt;&gt; to be created in appropriate cases. =A0Counters currently refe=
rencing those<br>
&gt;&gt;&gt; time ticks objects as discontinuity indicators would then have=
 to be<br>
&gt;&gt;&gt; considered for update as well, unless we were going to say tha=
t<br>
&gt;&gt;&gt; implementations MUST support both representations. =A0(This qu=
ickly<br>
&gt;&gt;&gt; becomes a replay of the 32-bit counter / 64-bit counter / pair=
ed-counter<br>
&gt;&gt;&gt; discussion from SMIv2.)<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; But that really wouldn&#39;t address the problem - an existing=
 NMS<br>
&gt;&gt;&gt; application that behaves badly when hrSystemUptime wraps.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Randy<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; OPS-AREA mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPS-AREA mailing list<br>
&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------<br>
&gt; The information transmitted in this email and any of its attachments i=
s intended only for the person or entity to which it is addressed and may c=
ontain information concerning Cablevision and/or its affiliates and subsidi=
aries that is proprietary, privileged, confidential and/or subject to copyr=
ight. =A0 Any review, retransmission, dissemination or other use of, or tak=
ing of any action in reliance upon, this information by persons or entities=
 other than the intended recipient(s) is prohibited and may be unlawful. =
=A0If you received this in error, please contact the sender immediately and=
 delete and destroy the communication and all of the attachments you have r=
eceived and all copies thereof.<br>

&gt; --------------------------------------------------------<br>
&gt;<br>
<br>
<br>
--------------------------------------------------------<br>
The information transmitted in this email and any of its attachments is int=
ended only for the person or entity to which it is addressed and may contai=
n information concerning Cablevision and/or its affiliates and subsidiaries=
 that is proprietary, privileged, confidential and/or subject to copyright.=
 =A0 Any review, retransmission, dissemination or other use of, or taking o=
f any action in reliance upon, this information by persons or entities othe=
r than the intended recipient(s) is prohibited and may be unlawful. =A0If y=
ou received this in error, please contact the sender immediately and delete=
 and destroy the communication and all of the attachments you have received=
 and all copies thereof.<br>

--------------------------------------------------------<br>
_______________________________________________<br>
OPS-AREA mailing list<br>
<a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
</div></div></blockquote></div><br><br>

--00504501635c1a2f390489cca2e9--

From randy_presuhn@mindspring.com  Thu Jun 24 20:16:54 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 963153A683C for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 20:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.742
X-Spam-Level: 
X-Spam-Status: No, score=-0.742 tagged_above=-999 required=5 tests=[AWL=-0.743, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cmo2cED9Gfl5 for <ops-area@core3.amsl.com>; Thu, 24 Jun 2010 20:16:53 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com (Postfix) with ESMTP id 073EA3A67AA for <ops-area@ietf.org>; Thu, 24 Jun 2010 20:16:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=emKtgRR77/vf4rZTj407IPRJTmV0/d3Vr6bFNz9cbo4tDoBMQyI6CjDBuRIePNuR; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.33.93.177] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1ORzOz-0005Ye-VG; Thu, 24 Jun 2010 23:16:26 -0400
Message-ID: <001401cb1414$f979c680$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Gene Matusovsky" <gmatusov@cablevision.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com> <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com> <4C237304.54CB.00CA.0@cablevision.com>
Date: Thu, 24 Jun 2010 20:17:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a91fc72053278035007e21619f834fb50787e710da2f8101350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.33.93.177
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2010 03:16:54 -0000

Hi -

> From: "Gene Matusovsky" <gmatusov@cablevision.com>
> To: "Jon Saperia" <saperia@jdscons.com>
> Cc: <ops-area@ietf.org>; "Randy Presuhn" <randy_presuhn@mindspring.com>
> Sent: Thursday, June 24, 2010 12:00 PM
> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>
> Workarounds are possible, and can be done, but not everyone has development
> resources. With todays technology and higher capacity systems, the root of the
> issue can be addressed directly by extending RFC 1155/ 1902 Timeticks data type.

Not an option.  SMI rules do not allow this, for good reason - it would change the
on-the-wire representation.   See the ASN.1 in RFC 3416 for an explanation:
the Unsigned32 is tagged [APPLICATION 2], while Counter64 is tagged
[APPLICATION 6].

> This was done before with RFC 2863, when IfInOctets was updated to IfHCInOctets.

No, in that case a *new* object type was defined, because changing the syntax
of IfInOctets was not an option.  IfHCInOctets is a *different* object, not an "update"
to IfInOctets, even though their semantics are remarkably similar.

> Are there any existing SNMP workgroups or ongoing projects.
....

I'm not aware of any where this sort of change would be within scope.

Randy


From gmatusov@cablevision.com  Fri Jun 25 08:15:23 2010
Return-Path: <gmatusov@cablevision.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51923A6784 for <ops-area@core3.amsl.com>; Fri, 25 Jun 2010 08:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.362
X-Spam-Level: 
X-Spam-Status: No, score=0.362 tagged_above=-999 required=5 tests=[AWL=0.825,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NdY1QDYoyho for <ops-area@core3.amsl.com>; Fri, 25 Jun 2010 08:15:20 -0700 (PDT)
Received: from cscpsmout02.cablevision.com (cscpsmout02.cablevision.com [167.206.119.145]) by core3.amsl.com (Postfix) with ESMTP id 9B64728B23E for <ops-area@ietf.org>; Fri, 25 Jun 2010 08:15:16 -0700 (PDT)
Received: from c2gwiaoutvs.cablevision.com (c2gwiaoutvs.cablevision.com [10.128.36.152]) by cscpsmout02.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o5PFFLNF005211 for <ops-area@ietf.org>; Fri, 25 Jun 2010 11:15:21 -0400
X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout02.cablevision.com o5PFFLNF005211
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1277478921; bh=GVkDizLU3k+tbYsAAh2sL1wGtVbeIE4IOwIo0x0 m+BY=; h=Message-Id:Date:From:To:Cc:Subject:References:In-Reply-To: Mime-Version:Content-Type:Content-Transfer-Encoding; b=y6j7Xh95UzQ o7w3lymPh2o1VK3nIiBSqlNmq2yJ75NKtzwj/p4UlVQQdwIizrkT9wUEtYyjLDFHkZn ZhWbDQbNGRTp7IeYT1LElATjZ50P8yhawM86nKfOokmLBXlZ7eaT/aBFE9MVsNNzQoT l8Cz8hjcdZWASxceF3NmhrESvE=
Received: from C2GWIAOUTDOM-MTA by c2gwiaoutvs.cablevision.com with Novell_GroupWise; Fri, 25 Jun 2010 11:15:21 -0400
Message-Id: <4C248FA3.54CB.00CA.0@cablevision.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.4 
Date: Fri, 25 Jun 2010 11:15:13 -0400
From: "Gene Matusovsky" <gmatusov@cablevision.com>
To: "Mark Ellison" <ellison@ieee.org>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com> <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com> <4C237304.54CB.00CA.0@cablevision.com> <AANLkTim3REIt837sAkjeTW7tV0XMbuilu9FEFdHBKA70@mail.gmail.com>
In-Reply-To: <AANLkTim3REIt837sAkjeTW7tV0XMbuilu9FEFdHBKA70@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Auth-Type: Internal IP
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2010 15:15:23 -0000

Mark, thanks for the suggestion. I will look into upgrading our agent to a SNMPv3 compliant.

Going back to general question, given today's technological advances in memory and flash memory capacities, since when RFC 1155 was written, and being that there is a need by the community to increase the Timeticks maximum limit, can a suggestion be made to the IETF to create a new a "High Capacitity" Timeticks ASN.1 data type? 

-Thanks,
Gene

>>> Mark Ellison <ellison@ieee.org> 6/24/2010 4:38 PM >>>
Gene,

Agreed, not everyone has development resources.

However, consider for a moment what you are asking for-  an "HC" version of
hrSystemUptime.  "HC" counters were introduced for the IF-MIB to handle wrap
situations that could occur every few minutes.  In the original post in this
thread, it was noted that hrSystemUpTime can wrap once every 497 days-
approximately every 16 months.

Even if an "HC" version of hrSystemUptime were designed, it would still need
to be implemented within the agents that the NMS will monitor- this would
take development resources, just as would implementing snmpEngineBoots and
snmpEngineTime.  Since the agent being monitored does not support these two
objects, one can safely assume that agent does not support SNMPv3.  In order
to support 64-bit counters, at least SNMPv2c is required since SNMPv1 does
not provide support for "HC" 64-bit counters.  Note that an agent that
implements SNMPv3 can be configured to allow retrieval of the snmpEngineTime
and snmpEngineBoots values via SNMPv2c or SNMPv1 protocol messages.

So, if the agent needs to be changed anyway to support a new object, the
approach that appears obvious to me, would be to upgrade the agent to
include compliant support for SNMPv3, which would make available the
snmpEngineBoots and snmpEngineTime objects for use with the NMS.

Hope this helps!

Regards,

Mark
http://EllisonSoftware.com 

On Thu, Jun 24, 2010 at 3:00 PM, Gene Matusovsky
<gmatusov@cablevision.com>wrote:

> Workarounds are possible, and can be done, but not everyone has development
> resources. With todays technology and higher capacity systems, the root of
> the issue can be addressed directly by extending RFC 1155/ 1902 Timeticks
> data type. This was done before with RFC 2863, when IfInOctets was updated
> to IfHCInOctets.
>
> Are there any existing SNMP workgroups or ongoing projects. Perhaps this
> can be suggested to them, to attach to the next published RFC?
>
> Any pointers would be appreciated.
>
> -Thank You,
> Gene Matusovsky
>
> >>> Jon Saperia <saperia@jdscons.com> 6/24/2010 12:57 PM >>>
> Others may, but I am not aware of an implementation of hrSystemUptime as a
> 64-bit value.  One other solution that would not require a MIB object change
> since you seem to have development resources available is to fix the NMS.  A
> simple solution is to watch for the counter wrap in a way that is similar to
> what people have done for interfaces.
>
> Your suggestion about exploring HC timeticks data objects is interesting,
> but that would require a working group taking up the activity.
>
> /jon
> On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:
>
> > Thanks to all on the IETF list for providing solutions and suggestions
> that could be used to work around the existing 32bit Timetick limit. In our
> case, our SNMP agent vendor does not currently support snmpEngineTime or
> snmpEngineBoots. I will ask the developer to look into supporting these
> objects.
> >
> > Perhaps another suggestion to the IETF board would be to define a new HC
> ASN1 Timeticks data type? This would provide compatibility to existing
> systems using the 32bit Timeticks, and give flexibility to agent developers
> to use a higher capacity Timeticks data type.
> >
> > I believe something similar was done with IfInOctets/IfOutOctets when
> they were extended to "HC" High Capacity 64bit counters in RFC 2863.
> >
> > On another note, does anyone know a case where a SNMP agent
> vendor/developer might have "broken the standard" and used 64bit counters
> for IfInOctets, IfOutOctets or TimeTicks
> > Would this break anything in a closed island type Enterprise network? I
> am considering asking our SNMP agent developer to use 64bit data type for
> Timeticks on the agent. The NMS system doesn't care or check for standards,
> it just treats hrSystemUptime as an infinite increasing counter.
> >
> > -Thanks,
> > Gene Matusovsky
> >
> >
> >>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
> > Hi-
> >
> > I would anticipate that an intelligently designed NMS would watch for
> wrap
> > on a TimeTicks object by checking for an increment in snmpEngineBoots, or
> > alternatively, simply watch the value of the snmpEngineTime object, since
> > its granularity is seconds rather than 1/100th seconds yielding a 40k+
> day
> > wrap interval.
> >
> > In any case, the target system sure isn't running a MS OS ;-)
> >
> > Regards,
> >
> > Mark
> > --
> > http://EllisonSoftware.com/ 
> >
> > On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com>
> wrote:
> >
> >> But is was in the context specifically of hrSystemUptime - at least that
> is
> >> how I read it.  I was suggesting a surgical fix to a specific problem
> >> related to uptime.  That could be fixed with a single object and leave
> the
> >> others that use time ticks intact.
> >>
> >> That said, I do agree with you that a good NMS should be able to deal
> with
> >> this and other oddities in this and many other objects.
> >>
> >> /jon
> >> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
> >>
> >>> Hi -
> >>>
> >>>> From: "Jon Saperia" <saperia@jdscons.com>
> >>>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> >>>> Cc: <ops-area@ietf.org>
> >>>> Sent: Wednesday, June 23, 2010 3:54 PM
> >>>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
> >>>>
> >>>> Why would a whole new set of objects be required to either fix,
> >>>> hrSystemUptime, or create a new higher capacity object?
> >>>
> >>> The question wasn't just about hrSystemUptime, but the fundamental
> >>> deficiency of time ticks.
> >>>
> >>> Coming up with a new time ticks syntax would effectively mean
> >>> every existing time ticks object would at least need to be
> >>> considered for obsolescence, and new objects would need
> >>> to be created in appropriate cases.  Counters currently referencing
> those
> >>> time ticks objects as discontinuity indicators would then have to be
> >>> considered for update as well, unless we were going to say that
> >>> implementations MUST support both representations.  (This quickly
> >>> becomes a replay of the 32-bit counter / 64-bit counter /
> paired-counter
> >>> discussion from SMIv2.)
> >>>
> >>> But that really wouldn't address the problem - an existing NMS
> >>> application that behaves badly when hrSystemUptime wraps.
> >>>
> >>> Randy
> >>>
> >>> _______________________________________________
> >>> OPS-AREA mailing list
> >>> OPS-AREA@ietf.org 
> >>> https://www.ietf.org/mailman/listinfo/ops-area 
> >>>
> >>
> >> _______________________________________________
> >> OPS-AREA mailing list
> >> OPS-AREA@ietf.org 
> >> https://www.ietf.org/mailman/listinfo/ops-area 
> >>
> >
> >
> > --------------------------------------------------------
> > The information transmitted in this email and any of its attachments is
> intended only for the person or entity to which it is addressed and may
> contain information concerning Cablevision and/or its affiliates and
> subsidiaries that is proprietary, privileged, confidential and/or subject to
> copyright.   Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient(s) is prohibited and may be
> unlawful.  If you received this in error, please contact the sender
> immediately and delete and destroy the communication and all of the
> attachments you have received and all copies thereof.
> > --------------------------------------------------------
> >
>
>
> --------------------------------------------------------
> The information transmitted in this email and any of its attachments is
> intended only for the person or entity to which it is addressed and may
> contain information concerning Cablevision and/or its affiliates and
> subsidiaries that is proprietary, privileged, confidential and/or subject to
> copyright.   Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient(s) is prohibited and may be
> unlawful.  If you received this in error, please contact the sender
> immediately and delete and destroy the communication and all of the
> attachments you have received and all copies thereof.
> --------------------------------------------------------
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org 
> https://www.ietf.org/mailman/listinfo/ops-area 
>

-------------------------------------------------------- 
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright.   Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful.  If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
--------------------------------------------------------

From mark@ellisonsoftware.com  Fri Jun 25 16:05:27 2010
Return-Path: <mark@ellisonsoftware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D23B63A69C8 for <ops-area@core3.amsl.com>; Fri, 25 Jun 2010 16:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.446
X-Spam-Level: 
X-Spam-Status: No, score=-101.446 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_UNSUB18=0.131, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i+7Ds9E0Oa3D for <ops-area@core3.amsl.com>; Fri, 25 Jun 2010 16:05:25 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id EF06A3A68A7 for <ops-area@ietf.org>; Fri, 25 Jun 2010 16:05:24 -0700 (PDT)
Received: by vws2 with SMTP id 2so1873045vws.31 for <ops-area@ietf.org>; Fri, 25 Jun 2010 16:05:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.126.199 with SMTP id d7mr63164vcs.207.1277507130586; Fri,  25 Jun 2010 16:05:30 -0700 (PDT)
Sender: mark@ellisonsoftware.com
Received: by 10.220.181.9 with HTTP; Fri, 25 Jun 2010 16:05:30 -0700 (PDT)
In-Reply-To: <4C248FA3.54CB.00CA.0@cablevision.com>
References: <4C223F8D.54CB.00CA.0@cablevision.com> <011701cb1321$d689e180$6801a8c0@oemcomputer> <F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com> <014201cb132c$16668f60$6801a8c0@oemcomputer> <29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com> <AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com> <4C23481C.54CB.00CA.0@cablevision.com> <9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com> <4C237304.54CB.00CA.0@cablevision.com> <AANLkTim3REIt837sAkjeTW7tV0XMbuilu9FEFdHBKA70@mail.gmail.com> <4C248FA3.54CB.00CA.0@cablevision.com>
Date: Fri, 25 Jun 2010 19:05:30 -0400
X-Google-Sender-Auth: qnCZEhdFeaQYDNrgr30pls5T8zU
Message-ID: <AANLkTin5WuAIrlxLn67oU1mDbWkrwYltcRv15aO-QYrX@mail.gmail.com>
From: Mark Ellison <ellison@ieee.org>
To: Gene Matusovsky <gmatusov@cablevision.com>
Content-Type: multipart/alternative; boundary=0016369fa0b6b777110489e2ce31
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2010 23:05:28 -0000

--0016369fa0b6b777110489e2ce31
Content-Type: text/plain; charset=ISO-8859-1

Gene,

I am not aware of the existence of "a need by the community to increase the
Timeticks maximum limit".  You are of course welcome to write and submit an
internet-draft that describes this need and a solution.

Regards,

Mark


On Fri, Jun 25, 2010 at 11:15 AM, Gene Matusovsky
<gmatusov@cablevision.com>wrote:

> Mark, thanks for the suggestion. I will look into upgrading our agent to a
> SNMPv3 compliant.
>
> Going back to general question, given today's technological advances in
> memory and flash memory capacities, since when RFC 1155 was written, and
> being that there is a need by the community to increase the Timeticks
> maximum limit, can a suggestion be made to the IETF to create a new a "High
> Capacitity" Timeticks ASN.1 data type?
>
> -Thanks,
> Gene
>
> >>> Mark Ellison <ellison@ieee.org> 6/24/2010 4:38 PM >>>
> Gene,
>
> Agreed, not everyone has development resources.
>
> However, consider for a moment what you are asking for-  an "HC" version of
> hrSystemUptime.  "HC" counters were introduced for the IF-MIB to handle
> wrap
> situations that could occur every few minutes.  In the original post in
> this
> thread, it was noted that hrSystemUpTime can wrap once every 497 days-
> approximately every 16 months.
>
> Even if an "HC" version of hrSystemUptime were designed, it would still
> need
> to be implemented within the agents that the NMS will monitor- this would
> take development resources, just as would implementing snmpEngineBoots and
> snmpEngineTime.  Since the agent being monitored does not support these two
> objects, one can safely assume that agent does not support SNMPv3.  In
> order
> to support 64-bit counters, at least SNMPv2c is required since SNMPv1 does
> not provide support for "HC" 64-bit counters.  Note that an agent that
> implements SNMPv3 can be configured to allow retrieval of the
> snmpEngineTime
> and snmpEngineBoots values via SNMPv2c or SNMPv1 protocol messages.
>
> So, if the agent needs to be changed anyway to support a new object, the
> approach that appears obvious to me, would be to upgrade the agent to
> include compliant support for SNMPv3, which would make available the
> snmpEngineBoots and snmpEngineTime objects for use with the NMS.
>
> Hope this helps!
>
> Regards,
>
> Mark
> http://EllisonSoftware.com
>
> On Thu, Jun 24, 2010 at 3:00 PM, Gene Matusovsky
> <gmatusov@cablevision.com>wrote:
>
> > Workarounds are possible, and can be done, but not everyone has
> development
> > resources. With todays technology and higher capacity systems, the root
> of
> > the issue can be addressed directly by extending RFC 1155/ 1902 Timeticks
> > data type. This was done before with RFC 2863, when IfInOctets was
> updated
> > to IfHCInOctets.
> >
> > Are there any existing SNMP workgroups or ongoing projects. Perhaps this
> > can be suggested to them, to attach to the next published RFC?
> >
> > Any pointers would be appreciated.
> >
> > -Thank You,
> > Gene Matusovsky
> >
> > >>> Jon Saperia <saperia@jdscons.com> 6/24/2010 12:57 PM >>>
> > Others may, but I am not aware of an implementation of hrSystemUptime as
> a
> > 64-bit value.  One other solution that would not require a MIB object
> change
> > since you seem to have development resources available is to fix the NMS.
>  A
> > simple solution is to watch for the counter wrap in a way that is similar
> to
> > what people have done for interfaces.
> >
> > Your suggestion about exploring HC timeticks data objects is interesting,
> > but that would require a working group taking up the activity.
> >
> > /jon
> > On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:
> >
> > > Thanks to all on the IETF list for providing solutions and suggestions
> > that could be used to work around the existing 32bit Timetick limit. In
> our
> > case, our SNMP agent vendor does not currently support snmpEngineTime or
> > snmpEngineBoots. I will ask the developer to look into supporting these
> > objects.
> > >
> > > Perhaps another suggestion to the IETF board would be to define a new
> HC
> > ASN1 Timeticks data type? This would provide compatibility to existing
> > systems using the 32bit Timeticks, and give flexibility to agent
> developers
> > to use a higher capacity Timeticks data type.
> > >
> > > I believe something similar was done with IfInOctets/IfOutOctets when
> > they were extended to "HC" High Capacity 64bit counters in RFC 2863.
> > >
> > > On another note, does anyone know a case where a SNMP agent
> > vendor/developer might have "broken the standard" and used 64bit counters
> > for IfInOctets, IfOutOctets or TimeTicks
> > > Would this break anything in a closed island type Enterprise network? I
> > am considering asking our SNMP agent developer to use 64bit data type for
> > Timeticks on the agent. The NMS system doesn't care or check for
> standards,
> > it just treats hrSystemUptime as an infinite increasing counter.
> > >
> > > -Thanks,
> > > Gene Matusovsky
> > >
> > >
> > >>>> Mark Ellison <ellison@ieee.org> 6/23/2010 9:17 PM >>>
> > > Hi-
> > >
> > > I would anticipate that an intelligently designed NMS would watch for
> > wrap
> > > on a TimeTicks object by checking for an increment in snmpEngineBoots,
> or
> > > alternatively, simply watch the value of the snmpEngineTime object,
> since
> > > its granularity is seconds rather than 1/100th seconds yielding a 40k+
> > day
> > > wrap interval.
> > >
> > > In any case, the target system sure isn't running a MS OS ;-)
> > >
> > > Regards,
> > >
> > > Mark
> > > --
> > > http://EllisonSoftware.com/
> > >
> > > On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia <saperia@jdscons.com>
> > wrote:
> > >
> > >> But is was in the context specifically of hrSystemUptime - at least
> that
> > is
> > >> how I read it.  I was suggesting a surgical fix to a specific problem
> > >> related to uptime.  That could be fixed with a single object and leave
> > the
> > >> others that use time ticks intact.
> > >>
> > >> That said, I do agree with you that a good NMS should be able to deal
> > with
> > >> this and other oddities in this and many other objects.
> > >>
> > >> /jon
> > >> On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:
> > >>
> > >>> Hi -
> > >>>
> > >>>> From: "Jon Saperia" <saperia@jdscons.com>
> > >>>> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > >>>> Cc: <ops-area@ietf.org>
> > >>>> Sent: Wednesday, June 23, 2010 3:54 PM
> > >>>> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
> > >>>>
> > >>>> Why would a whole new set of objects be required to either fix,
> > >>>> hrSystemUptime, or create a new higher capacity object?
> > >>>
> > >>> The question wasn't just about hrSystemUptime, but the fundamental
> > >>> deficiency of time ticks.
> > >>>
> > >>> Coming up with a new time ticks syntax would effectively mean
> > >>> every existing time ticks object would at least need to be
> > >>> considered for obsolescence, and new objects would need
> > >>> to be created in appropriate cases.  Counters currently referencing
> > those
> > >>> time ticks objects as discontinuity indicators would then have to be
> > >>> considered for update as well, unless we were going to say that
> > >>> implementations MUST support both representations.  (This quickly
> > >>> becomes a replay of the 32-bit counter / 64-bit counter /
> > paired-counter
> > >>> discussion from SMIv2.)
> > >>>
> > >>> But that really wouldn't address the problem - an existing NMS
> > >>> application that behaves badly when hrSystemUptime wraps.
> > >>>
> > >>> Randy
> > >>>
> > >>> _______________________________________________
> > >>> OPS-AREA mailing list
> > >>> OPS-AREA@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/ops-area
> > >>>
> > >>
> > >> _______________________________________________
> > >> OPS-AREA mailing list
> > >> OPS-AREA@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/ops-area
> > >>
> > >
> > >
> > > --------------------------------------------------------
> > > The information transmitted in this email and any of its attachments is
> > intended only for the person or entity to which it is addressed and may
> > contain information concerning Cablevision and/or its affiliates and
> > subsidiaries that is proprietary, privileged, confidential and/or subject
> to
> > copyright.   Any review, retransmission, dissemination or other use of,
> or
> > taking of any action in reliance upon, this information by persons or
> > entities other than the intended recipient(s) is prohibited and may be
> > unlawful.  If you received this in error, please contact the sender
> > immediately and delete and destroy the communication and all of the
> > attachments you have received and all copies thereof.
> > > --------------------------------------------------------
> > >
> >
> >
> > --------------------------------------------------------
> > The information transmitted in this email and any of its attachments is
> > intended only for the person or entity to which it is addressed and may
> > contain information concerning Cablevision and/or its affiliates and
> > subsidiaries that is proprietary, privileged, confidential and/or subject
> to
> > copyright.   Any review, retransmission, dissemination or other use of,
> or
> > taking of any action in reliance upon, this information by persons or
> > entities other than the intended recipient(s) is prohibited and may be
> > unlawful.  If you received this in error, please contact the sender
> > immediately and delete and destroy the communication and all of the
> > attachments you have received and all copies thereof.
> > --------------------------------------------------------
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
>
> --------------------------------------------------------
> The information transmitted in this email and any of its attachments is
> intended only for the person or entity to which it is addressed and may
> contain information concerning Cablevision and/or its affiliates and
> subsidiaries that is proprietary, privileged, confidential and/or subject to
> copyright.   Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient(s) is prohibited and may be
> unlawful.  If you received this in error, please contact the sender
> immediately and delete and destroy the communication and all of the
> attachments you have received and all copies thereof.
> --------------------------------------------------------
>

--0016369fa0b6b777110489e2ce31
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Gene,<br><br>I am not aware of the existence of &quot;a need by the communi=
ty to increase the Timeticks maximum limit&quot;.=A0 You are of course welc=
ome to write and submit an internet-draft that describes this need and a so=
lution.<br>
<br>Regards,<br><br>Mark<br><br><br><div class=3D"gmail_quote">On Fri, Jun =
25, 2010 at 11:15 AM, Gene Matusovsky <span dir=3D"ltr">&lt;<a href=3D"mail=
to:gmatusov@cablevision.com">gmatusov@cablevision.com</a>&gt;</span> wrote:=
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Mark, thanks for =
the suggestion. I will look into upgrading our agent to a SNMPv3 compliant.=
<br>

<br>
Going back to general question, given today&#39;s technological advances in=
 memory and flash memory capacities, since when RFC 1155 was written, and b=
eing that there is a need by the community to increase the Timeticks maximu=
m limit, can a suggestion be made to the IETF to create a new a &quot;High =
Capacitity&quot; Timeticks ASN.1 data type?<br>

<br>
-Thanks,<br>
Gene<br>
<br>
&gt;&gt;&gt; Mark Ellison &lt;<a href=3D"mailto:ellison@ieee.org">ellison@i=
eee.org</a>&gt; 6/24/2010 4:38 PM &gt;&gt;&gt;<br>
<div><div></div><div class=3D"h5">Gene,<br>
<br>
Agreed, not everyone has development resources.<br>
<br>
However, consider for a moment what you are asking for- =A0an &quot;HC&quot=
; version of<br>
hrSystemUptime. =A0&quot;HC&quot; counters were introduced for the IF-MIB t=
o handle wrap<br>
situations that could occur every few minutes. =A0In the original post in t=
his<br>
thread, it was noted that hrSystemUpTime can wrap once every 497 days-<br>
approximately every 16 months.<br>
<br>
Even if an &quot;HC&quot; version of hrSystemUptime were designed, it would=
 still need<br>
to be implemented within the agents that the NMS will monitor- this would<b=
r>
take development resources, just as would implementing snmpEngineBoots and<=
br>
snmpEngineTime. =A0Since the agent being monitored does not support these t=
wo<br>
objects, one can safely assume that agent does not support SNMPv3. =A0In or=
der<br>
to support 64-bit counters, at least SNMPv2c is required since SNMPv1 does<=
br>
not provide support for &quot;HC&quot; 64-bit counters. =A0Note that an age=
nt that<br>
implements SNMPv3 can be configured to allow retrieval of the snmpEngineTim=
e<br>
and snmpEngineBoots values via SNMPv2c or SNMPv1 protocol messages.<br>
<br>
So, if the agent needs to be changed anyway to support a new object, the<br=
>
approach that appears obvious to me, would be to upgrade the agent to<br>
include compliant support for SNMPv3, which would make available the<br>
snmpEngineBoots and snmpEngineTime objects for use with the NMS.<br>
<br>
Hope this helps!<br>
<br>
Regards,<br>
<br>
Mark<br>
<a href=3D"http://EllisonSoftware.com" target=3D"_blank">http://EllisonSoft=
ware.com</a><br>
<br>
On Thu, Jun 24, 2010 at 3:00 PM, Gene Matusovsky<br>
&lt;<a href=3D"mailto:gmatusov@cablevision.com">gmatusov@cablevision.com</a=
>&gt;wrote:<br>
<br>
&gt; Workarounds are possible, and can be done, but not everyone has develo=
pment<br>
&gt; resources. With todays technology and higher capacity systems, the roo=
t of<br>
&gt; the issue can be addressed directly by extending RFC 1155/ 1902 Timeti=
cks<br>
&gt; data type. This was done before with RFC 2863, when IfInOctets was upd=
ated<br>
&gt; to IfHCInOctets.<br>
&gt;<br>
&gt; Are there any existing SNMP workgroups or ongoing projects. Perhaps th=
is<br>
&gt; can be suggested to them, to attach to the next published RFC?<br>
&gt;<br>
&gt; Any pointers would be appreciated.<br>
&gt;<br>
&gt; -Thank You,<br>
&gt; Gene Matusovsky<br>
&gt;<br>
&gt; &gt;&gt;&gt; Jon Saperia &lt;<a href=3D"mailto:saperia@jdscons.com">sa=
peria@jdscons.com</a>&gt; 6/24/2010 12:57 PM &gt;&gt;&gt;<br>
&gt; Others may, but I am not aware of an implementation of hrSystemUptime =
as a<br>
&gt; 64-bit value. =A0One other solution that would not require a MIB objec=
t change<br>
&gt; since you seem to have development resources available is to fix the N=
MS. =A0A<br>
&gt; simple solution is to watch for the counter wrap in a way that is simi=
lar to<br>
&gt; what people have done for interfaces.<br>
&gt;<br>
&gt; Your suggestion about exploring HC timeticks data objects is interesti=
ng,<br>
&gt; but that would require a working group taking up the activity.<br>
&gt;<br>
&gt; /jon<br>
&gt; On Jun 24, 2010, at 11:57 AM, Gene Matusovsky wrote:<br>
&gt;<br>
&gt; &gt; Thanks to all on the IETF list for providing solutions and sugges=
tions<br>
&gt; that could be used to work around the existing 32bit Timetick limit. I=
n our<br>
&gt; case, our SNMP agent vendor does not currently support snmpEngineTime =
or<br>
&gt; snmpEngineBoots. I will ask the developer to look into supporting thes=
e<br>
&gt; objects.<br>
&gt; &gt;<br>
&gt; &gt; Perhaps another suggestion to the IETF board would be to define a=
 new HC<br>
&gt; ASN1 Timeticks data type? This would provide compatibility to existing=
<br>
&gt; systems using the 32bit Timeticks, and give flexibility to agent devel=
opers<br>
&gt; to use a higher capacity Timeticks data type.<br>
&gt; &gt;<br>
&gt; &gt; I believe something similar was done with IfInOctets/IfOutOctets =
when<br>
&gt; they were extended to &quot;HC&quot; High Capacity 64bit counters in R=
FC 2863.<br>
&gt; &gt;<br>
&gt; &gt; On another note, does anyone know a case where a SNMP agent<br>
&gt; vendor/developer might have &quot;broken the standard&quot; and used 6=
4bit counters<br>
&gt; for IfInOctets, IfOutOctets or TimeTicks<br>
&gt; &gt; Would this break anything in a closed island type Enterprise netw=
ork? I<br>
&gt; am considering asking our SNMP agent developer to use 64bit data type =
for<br>
&gt; Timeticks on the agent. The NMS system doesn&#39;t care or check for s=
tandards,<br>
&gt; it just treats hrSystemUptime as an infinite increasing counter.<br>
&gt; &gt;<br>
&gt; &gt; -Thanks,<br>
&gt; &gt; Gene Matusovsky<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;&gt;&gt; Mark Ellison &lt;<a href=3D"mailto:ellison@ieee.org">=
ellison@ieee.org</a>&gt; 6/23/2010 9:17 PM &gt;&gt;&gt;<br>
&gt; &gt; Hi-<br>
&gt; &gt;<br>
&gt; &gt; I would anticipate that an intelligently designed NMS would watch=
 for<br>
&gt; wrap<br>
&gt; &gt; on a TimeTicks object by checking for an increment in snmpEngineB=
oots, or<br>
&gt; &gt; alternatively, simply watch the value of the snmpEngineTime objec=
t, since<br>
&gt; &gt; its granularity is seconds rather than 1/100th seconds yielding a=
 40k+<br>
&gt; day<br>
&gt; &gt; wrap interval.<br>
&gt; &gt;<br>
&gt; &gt; In any case, the target system sure isn&#39;t running a MS OS ;-)=
<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt;<br>
&gt; &gt; Mark<br>
&gt; &gt; --<br>
&gt; &gt; <a href=3D"http://EllisonSoftware.com/" target=3D"_blank">http://=
EllisonSoftware.com/</a><br>
&gt; &gt;<br>
&gt; &gt; On Wed, Jun 23, 2010 at 7:43 PM, Jon Saperia &lt;<a href=3D"mailt=
o:saperia@jdscons.com">saperia@jdscons.com</a>&gt;<br>
&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; But is was in the context specifically of hrSystemUptime - at=
 least that<br>
&gt; is<br>
&gt; &gt;&gt; how I read it. =A0I was suggesting a surgical fix to a specif=
ic problem<br>
&gt; &gt;&gt; related to uptime. =A0That could be fixed with a single objec=
t and leave<br>
&gt; the<br>
&gt; &gt;&gt; others that use time ticks intact.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; That said, I do agree with you that a good NMS should be able=
 to deal<br>
&gt; with<br>
&gt; &gt;&gt; this and other oddities in this and many other objects.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; /jon<br>
&gt; &gt;&gt; On Jun 23, 2010, at 7:30 PM, Randy Presuhn wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi -<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; From: &quot;Jon Saperia&quot; &lt;<a href=3D"mailto:s=
aperia@jdscons.com">saperia@jdscons.com</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:r=
andy_presuhn@mindspring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; Cc: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-area=
@ietf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; Sent: Wednesday, June 23, 2010 3:54 PM<br>
&gt; &gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting max=
imum value<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Why would a whole new set of objects be required to e=
ither fix,<br>
&gt; &gt;&gt;&gt;&gt; hrSystemUptime, or create a new higher capacity objec=
t?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; The question wasn&#39;t just about hrSystemUptime, but th=
e fundamental<br>
&gt; &gt;&gt;&gt; deficiency of time ticks.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Coming up with a new time ticks syntax would effectively =
mean<br>
&gt; &gt;&gt;&gt; every existing time ticks object would at least need to b=
e<br>
&gt; &gt;&gt;&gt; considered for obsolescence, and new objects would need<b=
r>
&gt; &gt;&gt;&gt; to be created in appropriate cases. =A0Counters currently=
 referencing<br>
&gt; those<br>
&gt; &gt;&gt;&gt; time ticks objects as discontinuity indicators would then=
 have to be<br>
&gt; &gt;&gt;&gt; considered for update as well, unless we were going to sa=
y that<br>
&gt; &gt;&gt;&gt; implementations MUST support both representations. =A0(Th=
is quickly<br>
&gt; &gt;&gt;&gt; becomes a replay of the 32-bit counter / 64-bit counter /=
<br>
&gt; paired-counter<br>
&gt; &gt;&gt;&gt; discussion from SMIv2.)<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; But that really wouldn&#39;t address the problem - an exi=
sting NMS<br>
&gt; &gt;&gt;&gt; application that behaves badly when hrSystemUptime wraps.=
<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Randy<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a=
><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br=
>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --------------------------------------------------------<br>
&gt; &gt; The information transmitted in this email and any of its attachme=
nts is<br>
&gt; intended only for the person or entity to which it is addressed and ma=
y<br>
&gt; contain information concerning Cablevision and/or its affiliates and<b=
r>
&gt; subsidiaries that is proprietary, privileged, confidential and/or subj=
ect to<br>
&gt; copyright. =A0 Any review, retransmission, dissemination or other use =
of, or<br>
&gt; taking of any action in reliance upon, this information by persons or<=
br>
&gt; entities other than the intended recipient(s) is prohibited and may be=
<br>
&gt; unlawful. =A0If you received this in error, please contact the sender<=
br>
&gt; immediately and delete and destroy the communication and all of the<br=
>
&gt; attachments you have received and all copies thereof.<br>
&gt; &gt; --------------------------------------------------------<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------<br>
&gt; The information transmitted in this email and any of its attachments i=
s<br>
&gt; intended only for the person or entity to which it is addressed and ma=
y<br>
&gt; contain information concerning Cablevision and/or its affiliates and<b=
r>
&gt; subsidiaries that is proprietary, privileged, confidential and/or subj=
ect to<br>
&gt; copyright. =A0 Any review, retransmission, dissemination or other use =
of, or<br>
&gt; taking of any action in reliance upon, this information by persons or<=
br>
&gt; entities other than the intended recipient(s) is prohibited and may be=
<br>
&gt; unlawful. =A0If you received this in error, please contact the sender<=
br>
&gt; immediately and delete and destroy the communication and all of the<br=
>
&gt; attachments you have received and all copies thereof.<br>
&gt; --------------------------------------------------------<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;<br>
<br>
</div></div>--------------------------------------------------------<br>
<div><div></div><div class=3D"h5">The information transmitted in this email=
 and any of its attachments is intended only for the person or entity to wh=
ich it is addressed and may contain information concerning Cablevision and/=
or its affiliates and subsidiaries that is proprietary, privileged, confide=
ntial and/or subject to copyright. =A0 Any review, retransmission, dissemin=
ation or other use of, or taking of any action in reliance upon, this infor=
mation by persons or entities other than the intended recipient(s) is prohi=
bited and may be unlawful. =A0If you received this in error, please contact=
 the sender immediately and delete and destroy the communication and all of=
 the attachments you have received and all copies thereof.<br>

--------------------------------------------------------<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>

--0016369fa0b6b777110489e2ce31--

From dromasca@avaya.com  Sun Jun 27 03:34:22 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 765C73A69BB for <ops-area@core3.amsl.com>; Sun, 27 Jun 2010 03:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.687,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9wWV+AGJkK2 for <ops-area@core3.amsl.com>; Sun, 27 Jun 2010 03:34:21 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id C08163A68FB for <ops-area@ietf.org>; Sun, 27 Jun 2010 03:34:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,491,1272859200"; d="scan'208";a="195425202"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 27 Jun 2010 06:34:28 -0400
X-IronPort-AV: E=Sophos;i="4.53,491,1272859200"; d="scan'208";a="476334942"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 27 Jun 2010 06:34:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 Jun 2010 12:34:05 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F39BC@307622ANEX5.global.avaya.com>
In-Reply-To: <001401cb1414$f979c680$6801a8c0@oemcomputer>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] RFC1155 Timeticks hitting maximum value
Thread-Index: AcsUFOS85kemBOElSQS+FRQCoAU+QwBzuPvA
References: <4C223F8D.54CB.00CA.0@cablevision.com><011701cb1321$d689e180$6801a8c0@oemcomputer><F29000F9-BD1F-4D9A-B0A4-409D068C7D0C@jdscons.com><014201cb132c$16668f60$6801a8c0@oemcomputer><29FB81E3-EAFA-4B9B-87DD-8FC8E73756F8@jdscons.com><AANLkTikMx6Y98asUpVmexWM1laF4xWmXYhAH3pH1IZbe@mail.gmail.com><4C23481C.54CB.00CA.0@cablevision.com><9A36AA20-DBE2-4497-83BE-BB843D1F6A6D@jdscons.com><4C237304.54CB.00CA.0@cablevision.com> <001401cb1414$f979c680$6801a8c0@oemcomputer>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, "Gene Matusovsky" <gmatusov@cablevision.com>
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jun 2010 10:34:22 -0000

=20

> -----Original Message-----
> From: ops-area-bounces@ietf.org=20
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Randy Presuhn
> Sent: Friday, June 25, 2010 6:17 AM
> To: Gene Matusovsky
> Cc: ops-area@ietf.org
> Subject: Re: [OPS-AREA] RFC1155 Timeticks hitting maximum value
>=20
> Hi -
>=20
> > From: "Gene Matusovsky" <gmatusov@cablevision.com>

...

>=20
> > Are there any existing SNMP workgroups or ongoing projects.
> ....
>=20
> I'm not aware of any where this sort of change would be within scope.
>=20
> Randy
>=20

Gene,

The OPSAWG can be used to host at least a first proposal, to test if
there is enough interest from the community. The way to go is to submit
an individual Internet-Draft to the OPSAWG for discussion.=20

Dan

From dromasca@avaya.com  Tue Jun 29 04:19:42 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8329A3A6AB8 for <ops-area@core3.amsl.com>; Tue, 29 Jun 2010 04:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.747
X-Spam-Level: 
X-Spam-Status: No, score=-0.747 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrJdCc59V2RB for <ops-area@core3.amsl.com>; Tue, 29 Jun 2010 04:19:41 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id F18D43A6A6E for <ops-area@ietf.org>; Tue, 29 Jun 2010 04:19:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,503,1272859200"; d="scan'208";a="22861968"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 29 Jun 2010 07:19:44 -0400
X-IronPort-AV: E=Sophos;i="4.53,503,1272859200"; d="scan'208";a="476890159"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jun 2010 07:19:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Jun 2010 13:19:08 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F3E6D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Preliminary Agenda for the OPSAREA meeting - call for agenda items
Thread-Index: AcsXfOQsIVlmeegjSQ+hSDn14ofTaQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] Preliminary Agenda for the OPSAREA meeting - call for agenda items
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2010 11:19:42 -0000

Here is the preliminary agenda for the OPSAREA meeting in Maastricht. We
are inviting for items to be added to the agenda.=20

Thanks and Regards,

Ron and Dan

------------------------

OPS-AREA Open meeting Preliminary Agenda

Monday, July 26, 2010

Area Directors and Meeting Chairs: Dan Romascanu and Ron Bonica

1. Note well, agenda bashing, note takers, jabber scribe, blue sheets -
5 min=20
=20
2. OAM Workshop proposal and plans - Ron Bonica - 15 min

3. Management harmonization - Mehmet Ersue, Nigel Davis - 15 min

4. WG status review - 3 min each WG

5. Open mic - any time left
