Re: [Disman] another question about alarmMib..

Michael Thatcher <thatcher@redback.com> Wed, 17 December 2008 05:52 UTC

Return-Path: <disman-bounces@ietf.org>
X-Original-To: disman-archive@megatron.ietf.org
Delivered-To: ietfarch-disman-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 038D73A6AD0; Tue, 16 Dec 2008 21:52:04 -0800 (PST)
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA12028C174 for <disman@core3.amsl.com>; Tue, 16 Dec 2008 13:20:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.228
X-Spam-Level:
X-Spam-Status: No, score=-1.228 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
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 4TzUWhdDniYa for <disman@core3.amsl.com>; Tue, 16 Dec 2008 13:20:03 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 4676B28C173 for <disman@ietf.org>; Tue, 16 Dec 2008 13:20:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 802EA1A9788; Tue, 16 Dec 2008 13:19:56 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01288-09; Tue, 16 Dec 2008 13:19:56 -0800 (PST)
Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id 652871A978C; Tue, 16 Dec 2008 13:19:56 -0800 (PST)
Message-ID: <49481B7C.1060301@redback.com>
Date: Tue, 16 Dec 2008 13:19:56 -0800
From: Michael Thatcher <thatcher@redback.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
References: <4946D492.5070107@redback.com> <004701c95fb1$c30f9c00$6801a8c0@oemcomputer>
In-Reply-To: <004701c95fb1$c30f9c00$6801a8c0@oemcomputer>
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at redback.com
X-Mailman-Approved-At: Tue, 16 Dec 2008 21:52:02 -0800
Cc: disman@ietf.org
Subject: Re: [Disman] another question about alarmMib..
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Randy Presuhn wrote:
Hi -

  
From: "Michael Thatcher" <thatcher@redback.com>
To: <disman@ietf.org>
Sent: Monday, December 15, 2008 2:05 PM
Subject: [Disman] another question about alarmMib..

the alarmActiveTable is indexed by alarmListName, alarmDataAndTime, 
alarmActiveIndex

the alarmActiveVariableTable is indexed by alarmListName, 
alarmActiveIndex, alarmActiveVariableIndex.

How come alarmDataAndTime are not an index into the 
alarmActiveVariableTable, since this table by definition has the varbind 
objects from the corresponding entry in alarmActiveTable?

This also seems to imply that alarmActiveIndex is always unique 
regardless of alarmDataAndTime.  Is this intentional?
    
Yes.  This should make it clear why alarmDateAndTime is needed
for the alarmActiveTable (it supports the ordering required for the
most common use cases) and not for the alarmActiveVariableTable
(these are meaningful only in the context of the alarm "containing"
these variables, and a time stamp is not needed to provide uniqueness.

  

The description of alarmClearIndex says that "This object has the same value as the alarmActiveIndex that this alarm instance had when it was active".  Does this mean that clear events cannot be placed in this table which do not have a related alarm in the alarmActiveTable?  If there are multiple related entries in the alarmActiveTable, does it matter which alarmActiveIndex value is used? 


mikeT