Re: [Disman] Alarm Mib

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 23 April 2012 17:33 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: disman@ietfa.amsl.com
Delivered-To: disman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382EB21F8712 for <disman@ietfa.amsl.com>; Mon, 23 Apr 2012 10:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.518
X-Spam-Level:
X-Spam-Status: No, score=-97.518 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, FRT_PENIS1=3.592, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kTg+ZCSWq8X5 for <disman@ietfa.amsl.com>; Mon, 23 Apr 2012 10:33:49 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id CEC8021F86B4 for <disman@ietf.org>; Mon, 23 Apr 2012 10:33:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=sQvcYD+NTXJ0quF77UqWHlwl2PWvc7Qeoqx5tkH9ADxy4Pri1OxEa5TQARoRqc/h; 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.35.225.150] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SMN8z-0007ZV-E4; Mon, 23 Apr 2012 13:33:45 -0400
Message-ID: <009c01cd2177$6d2e7b40$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "April Pennisi" <april.pennisi@genband.com>
References: <FBE0F7DF3682DF4B9D0176228D9DF5B3B3DEB3AB@gbplmail02.genband.com> <EDC652A26FB23C4EB6384A4584434A04078107E5@307622ANEX5.global.avaya.com>
Date: Mon, 23 Apr 2012 10:35:06 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8882951211ce6890f881d351fa71de649933b5abfb079c72fda350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.35.225.150
Cc: disman@ietf.org
Subject: Re: [Disman] Alarm Mib
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 23 Apr 2012 17:33:50 -0000

Hi -

The omission was the subject of a proposed eratum reported July 29, 2009.
Section 5.2 of RFC 3877 notwithstanding, the view that prevailed at the time was:
  "Technically the submitter is right. However, the change cannot be made
    the way suggested in the Errata, but only by deprecating the object and
    defining a new object with correct enumerated values. This can be done
    only in a future version of the MIB module."

This eventually concluded with a recommendation of "hold for document update."

It looks like we, as a WG, may have blown it on this one.  There are really
two problems itentified in the original report: the missing enumeration value,
and the wrong explanatory text.  Both need to be fixed, and the IANA mechanism
seems appropriate.

Randy

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "April Pennisi" <april.pennisi@genband.com>
Cc: <disman@ietf.org>
Sent: Monday, April 23, 2012 5:46 AM
Subject: Re: [Disman] Alarm Mib


Hi April,

 

I hope that you do not mind if I am copying the disman WG list. 

 

I do not remember why we skipped this value, it may just have been a
miss. Maybe Sharon or Randy remember. 

 

In any case, according to section 5.2 in RFC 3877 this may be fixed
rather easily by requesting to add one new enumerated value in the IANA
maintained TC at http://www.iana.org/assignments/ianaitualarmtc-mib by
sending a mail to iana@iana.org. 

 

Regards,

 

Dan

 

 

 

From: April Pennisi [mailto:april.pennisi@genband.com] 
Sent: Tuesday, April 10, 2012 1:02 AM
To: Romascanu, Dan (Dan)
Subject: Alarm Mib

 

Hi Dan - 

 

I've been working on mapping alarms from a device to appropriate
probable causes defined in RFC 3877.

 

I notice there is one from M3100 missing from the list
IANAItuProbableCause in the Alarm MIB.  Reinitialized is missing.  (It
occurred to me because I'd like to use it.)

 

>From M3100:

 

lossOfRealTime ProbableCause
<http://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/Attribute-AS
N1Module.html#Attribute-ASN1Module.ProbableCause>  ::=
  localValue:157
 
-- A processing error alarm to be issued if the system detects that it
has lost the time in 
-- the real time clock but  the clock itself is working. This could
happen e.g. during a power 
-- cut in a small NE which does not have battery backup for the real
time clock.
reinitialized ProbableCause
<http://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/Attribute-AS
N1Module.html#Attribute-ASN1Module.ProbableCause>  ::=
  localValue:158
 
-- A processing error alarm to be issued after the system has
reinitialised. This will indicate 
-- to the management systems that the view they have of the managed
system may no longer 
-- be valid. Usage example: The managed 
-- system issues this alarm after a reinitialization with severity
warning to inform the
-- management system about the event. No clearing notification will be
sent.
applicationSubsystemFailure ProbableCause
<http://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/Attribute-AS
N1Module.html#Attribute-ASN1Module.ProbableCause>  ::=
  localValue:159
 
configurationOrCustomisationError ProbableCause
<http://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/Attribute-AS
N1Module.html#Attribute-ASN1Module.ProbableCause>  ::= localValue:160
 
>From the Alarm MIB:
            lossOfRealTimel (157),
 --A processing error alarm to be issued after the system has
 --reinitialised.  This will indicate
 --to the management systems that the view they have of the managed
 --system may no longer
 --be valid.  Usage example: The managed
 --system issues this alarm after a reinitialization with severity
 --warning to inform the
 --management system about the event.  No clearing notification will
 --be sent.
             applicationSubsystemFailure (158),
             configurationOrCustomisationError (159),

 

How can I add it?  I would think we cannot now insert it, but instead
add to the end of this list?

As reinitialized (616)?

 

I don't know if there are ways to update these things...

 

Thx!