Re: [OPSAWG] discuss on draft-ietf-opsawg-syslog-msg-mib-06.txt

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sat, 29 August 2009 18:41 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A06513A69D9 for <opsawg@core3.amsl.com>; Sat, 29 Aug 2009 11:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.152
X-Spam-Level:
X-Spam-Status: No, score=-2.152 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 PqdRZmWuQi4K for <opsawg@core3.amsl.com>; Sat, 29 Aug 2009 11:41:47 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 247BD3A68E0 for <opsawg@ietf.org>; Sat, 29 Aug 2009 11:41:46 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0D1E9C001F; Sat, 29 Aug 2009 20:41:53 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id DCs4Qng8ouQS; Sat, 29 Aug 2009 20:41:52 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2E113C000D; Sat, 29 Aug 2009 20:41:51 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id A2378C82C4E; Sat, 29 Aug 2009 20:41:49 +0200 (CEST)
Date: Sat, 29 Aug 2009 20:41:49 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Adrian Farrel <Adrian.Farrel@huawei.com>
Message-ID: <20090829184149.GD24348@elstar.local>
Mail-Followup-To: Adrian Farrel <Adrian.Farrel@huawei.com>, David Harrington <ietfdbh@comcast.net>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-ietf-opsawg-syslog-msg-mib@tools.ietf.org" <draft-ietf-opsawg-syslog-msg-mib@tools.ietf.org>
References: <20090828130615.GA22962@elstar.local> <052e01ca27f0$2a0e6060$0600a8c0@china.huawei.com> <C931F40537DD4D819257BBE94B042035@your029b8cecfe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C931F40537DD4D819257BBE94B042035@your029b8cecfe>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "draft-ietf-opsawg-syslog-msg-mib@tools.ietf.org" <draft-ietf-opsawg-syslog-msg-mib@tools.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] discuss on draft-ietf-opsawg-syslog-msg-mib-06.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Aug 2009 18:41:48 -0000

On Fri, Aug 28, 2009 at 11:49:50PM +0200, Adrian Farrel wrote:
 
> Two minor points:
> 
> 1.
> > Do entries ever get removed from this table?
> Not as I understand it. The index is monotonic increasing and wraps at the 
> maximum value (defined as the lesser of syslogMsgTableMaxSize and 
> 4294967295).

No, it wraps at 4294967295 always. What makes you believe it maps at
min(syslogMsgTableMaxSize, 4294967295)?

> > Does rollover just overwrite starting at the beginning of the table?
> Yes.

Only in the case where the agent has storage for 4294967295 table
entries, something I consider unlikely implementations will support.

> Yes. And this is what swings it for me.
> I am just left wondering whether an Agent is more loaded by a bulk read of 
> 10,000 entries or maintaining a pointer into the table.
> 
> Clear up this last point, and I'm done.

If you only need the oldest entry in table insertion time, such an
index is of course handy. The question is what practical value it has
to be able to retrieve this oldest entry quickly.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>