Re: [Disman] another question about alarmMib..

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 16 December 2008 21:43 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 3053728C1AB; Tue, 16 Dec 2008 13:43:25 -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 8E40728C1AB for <disman@core3.amsl.com>; Tue, 16 Dec 2008 13:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.601, 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 jzET70jm18In for <disman@core3.amsl.com>; Tue, 16 Dec 2008 13:43:22 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by core3.amsl.com (Postfix) with ESMTP id C742B28C199 for <disman@ietf.org>; Tue, 16 Dec 2008 13:43:22 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=YyJ93LvCFTGv+R/EKiWxzYTJzBfeMMqr5yXUFG1DZbVbTkp+gG+arcK9deUzwL9m; 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 [64.105.35.88] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LChhB-0004Jb-A7 for disman@ietf.org; Tue, 16 Dec 2008 16:43:13 -0500
Message-ID: <000301c95fc7$8b51e320$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: disman@ietf.org
References: <4946D492.5070107@redback.com> <004701c95fb1$c30f9c00$6801a8c0@oemcomputer> <49481B7C.1060301@redback.com>
Date: Tue, 16 Dec 2008 13:44:55 -0800
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88858bc2ddbf51b90e4aacb604e386b2e7b27fdf930a0057a45350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.105.35.88
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

Hi -

> From: "Michael Thatcher" <thatcher@redback.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <disman@ietf.org>
> Sent: Tuesday, December 16, 2008 1:19 PM
> Subject: Re: [Disman] another question about alarmMib..
...
> 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?

It sounds that way.

> If there are multiple related entries in the alarmActiveTable,
> does it matter which alarmActiveIndex value is used?  

I can't imagine why it would.  It does, however, seem to be
an argument for maintaining a 1:1 correspondence, even
though I doubt that that was the intent.

It would be good to hear from the folks who have actually
already implemented or deployed this MIB.

Randy