Re: [Disman] Alarm Mib

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 23 April 2012 12:46 UTC

Return-Path: <dromasca@avaya.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 0903121F85E3 for <disman@ietfa.amsl.com>; Mon, 23 Apr 2012 05:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.096
X-Spam-Level:
X-Spam-Status: No, score=-101.096 tagged_above=-999 required=5 tests=[AWL=-2.090, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, FRT_PENIS1=3.592, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 e1ts3V2+xgnU for <disman@ietfa.amsl.com>; Mon, 23 Apr 2012 05:46:28 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 379EA21F861E for <disman@ietf.org>; Mon, 23 Apr 2012 05:46:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FADhOlU/GmAcF/2dsb2JhbABEgkalZ4MnhXGBB4IJAQEBAQMFDQoJCAECSRACAQgNBAQBAQYBAQECBgIKCwEGAQEFEAEMAiAJCAEBBBIBBgIBGYdtC50VnH2Kd4VZYwSQGVcIiEuCTYoogmuBWg
X-IronPort-AV: E=Sophos; i="4.75,467,1330923600"; d="jpg'145?scan'145,208,217,145"; a="303142287"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Apr 2012 08:46:23 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Apr 2012 08:43:59 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01CD214F.16686C0A"
Date: Mon, 23 Apr 2012 14:46:21 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04078107E5@307622ANEX5.global.avaya.com>
In-Reply-To: <FBE0F7DF3682DF4B9D0176228D9DF5B3B3DEB3AB@gbplmail02.genband.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Alarm Mib
Thread-Index: Ac0Wmx+gvq9rdkYfQGO1cZoMyaSXswKsYskQ
References: <FBE0F7DF3682DF4B9D0176228D9DF5B3B3DEB3AB@gbplmail02.genband.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "April Pennisi" <april.pennisi@genband.com>
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 12:46:31 -0000

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!