From owner-disman@dorothy.peer.com  Tue Oct  3 16:12:14 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22414
	for <disman-archive@odin.ietf.org>; Tue, 3 Oct 2000 16:12:14 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e93K2EU21035;
	Tue, 3 Oct 2000 15:02:15 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA24099
	for disman-list; Tue, 3 Oct 2000 12:59:41 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA24093;
	Tue, 3 Oct 2000 12:59:38 -0700 (PDT)
Date: Tue, 3 Oct 2000 12:59:38 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010031959.MAA24093@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd: Question regarding DS1 MIB (RFC 2495)
Cc: Yosief.Sium@eto.ericsson.se
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e93K2EU21035
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA22414


Hi -

I'm forwarding a non-subscriber post that for some
reason was sent to the disman WG mailing list.
Subscription instructions are available at
http://www.ietf.org/html.charters/disman-charter.html

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA22521
> 	for <disman@dorothy.peer.com>; Tue, 3 Oct 2000 02:32:14 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e939Vwj14449
> 	for <disman@dorothy.peer.com>; Tue, 3 Oct 2000 04:31:59 -0500 (CDT)
> Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
> 	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id e939Vnt02579
> 	for <disman@dorothy.peer.com>; Tue, 3 Oct 2000 11:32:57 +0200 (MEST)
> Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Tue Oct 03 11:25:37 2000 +0200
> Received: by esealnt743.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
> 	id <T1RVB9N6>; Tue, 3 Oct 2000 11:31:48 +0200
> Message-ID: <89BF44E217C8D21192EB0008C7A4E25204C7EC37@enoasnt100.eto.ericsson.se>
> From: "Yosief Sium (ETO)" <Yosief.Sium@eto.ericsson.se>
> To: "'davef@newbridge.com'" <davef@newbridge.com>
> Cc: disman@dorothy.bmc.com
> Subject: Question regarding DS1 MIB (RFC 2495)
> Date: Tue, 3 Oct 2000 11:31:42 +0200 
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2651.58)
> Content-Type: text/plain;
> 	charset="ISO-8859-1"
> 
> Hi,
> 
> I've a little question regarding the trap dsx1LineStatusChange. This is sent whenever the status of an DS1/E1 line is changed. Based on this trap, the manager is supposed to browse dsx1ConfigTable to find out which line that changed the status. In case where you have a lot E1 lines, this may be time-consuming and inefficient. Is there any reason why dsx1LineIndex is sent with this trap so that the manager knows exactly which E1 line if affected without any extra effort? 
> 
> Thankfull for any input!
> 
> 
> Regards!
> Yosief Sium
> 


From owner-disman@dorothy.peer.com  Wed Oct  4 14:17:03 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA27913
	for <disman-archive@odin.ietf.org>; Wed, 4 Oct 2000 14:17:03 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e94IBeo13676;
	Wed, 4 Oct 2000 13:11:40 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA27280
	for disman-list; Wed, 4 Oct 2000 11:10:10 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA27274
	for disman@dorothy.bmc.com; Wed, 4 Oct 2000 11:10:07 -0700 (PDT)
Date: Wed, 4 Oct 2000 11:10:07 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010041810.LAA27274@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: OT: what does this mean?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e94IBeo13676
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA27913


Hi -

Does anyone know what this message says?  We think it's a
romance language, but we're pretty sure it's not Spanish,
French, or Latin.  It looks like it's coming from a disman
list subscriber's mail system, but none of the standard error
code information came with it.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> From -t@cwb.fnn.net Tue Oct  3 13:45:38 PDT 2000
> Date: 3 Oct 2000 20:16:38 -0000
> Message-ID: <20001003201638.29776.qmail@cwb.fnn.net>
> From: Sistema FutureMAIL <erro-email@cwb.fnn.net>
> To: owner-disman@dorothy.bmc.com
> Subject: Falha na mensagem
> 
> Ola!
> 
> Aqui eh o sistema FutureMail (funcionando no dominio
> cwb.fnn.net) e viemos lhe informar que sua mensagem
> para o usuario mateus@cwb.fnn.net falhou.
> 
> Isto aconteceu porque este usuario nao existe em
> nosso sistema. 
> 
> Voce verificou o endereco? Se este eh o unico endereco
> que voce tem desta pessoa, mande um e-mail para nos e
> tentaremos localiza-lo para voce.
> 
> Um Abraco!
> 
> Equipe FNN
> erro-email@cwb.fnn.net
> 
> 


From owner-disman@dorothy.peer.com  Thu Oct  5 13:15:32 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03395
	for <disman-archive@odin.ietf.org>; Thu, 5 Oct 2000 13:15:31 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e95H5md13389;
	Thu, 5 Oct 2000 12:05:49 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02524
	for disman-list; Thu, 5 Oct 2000 10:01:29 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02518;
	Thu, 5 Oct 2000 10:01:26 -0700 (PDT)
Date: Thu, 5 Oct 2000 10:01:26 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010051701.KAA02518@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd: Re: OT: what does this mean?
Cc: jrr@virata.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e95H5md13389
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA03395


Hi -

A post to the disman list bounced due to unknown subscriber address.
I've added jrr@viarata.com to the "posters" list.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA27973;
> 	Wed, 4 Oct 2000 12:03:21 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e94J31I24856;
> 	Wed, 4 Oct 2000 14:03:05 -0500 (CDT)
> Received: from boletus.cam.virata.com (boletus.cam.virata.com [192.168.219.9])
> 	by gatekeeper.cam.virata.com (8.9.3/8.8.5) with ESMTP id UAA14087;
> 	Wed, 4 Oct 2000 20:04:04 +0100
> Received: from mercury.cam.virata.com (mercury.cam.virata.com [192.168.219.17])
> 	by boletus.cam.virata.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA28914;
> 	Wed, 4 Oct 2000 20:04:04 +0100
> Received: from champignon.cam.virata.com (root@champignon.cam.virata.com [192.168.219.137])
> 	by mercury.cam.virata.com (8.9.3/8.9.3) with ESMTP id UAA23194;
> 	Wed, 4 Oct 2000 20:04:03 +0100 (BST)
> Received: (from jrr@localhost)
> 	by champignon.cam.virata.com (8.9.3/8.9.3/Debian/GNU) id UAA32543;
> 	Wed, 4 Oct 2000 20:04:02 +0100
> Date: Wed, 4 Oct 2000 20:04:02 +0100
> Message-Id: <200010041904.UAA32543@champignon.cam.virata.com>
> From: John Rickard <jrr@virata.com>
> To: rpresuhn@dorothy.bmc.com
> CC: disman@dorothy.bmc.com
> In-reply-to: <200010041810.LAA27274@dorothy.bmc.com> (message from Randy
> 	Presuhn on Wed, 4 Oct 2000 11:10:07 -0700 (PDT))
> Subject: Re: OT: what does this mean?
> 
> > Does anyone know what this message says?  We think it's a
> > romance language, but we're pretty sure it's not Spanish,
> > French, or Latin.
> 
> It's Portuguese.  A combination of knowledge of Italian, guesswork,
> Babelfish, and an online dictionary (http://www.ectaco.com/online/)
> yields the following rough translation:
> 
> > > Ola!
> 
> Hello!
> 
> > > Aqui eh o sistema FutureMail (funcionando no dominio
> > > cwb.fnn.net) e viemos lhe informar que sua mensagem
> > > para o usuario mateus@cwb.fnn.net falhou.
> 
> This is the FutureMail system (operating in the domain cwb.fnn.net)
> and we are writing to inform you that your message for the user
> mateus@cwb.fnn.net failed.
> 
> > > Isto aconteceu porque este usuario nao existe em
> > > nosso sistema.
> 
> This happened because this user does not exist in our system.
> 
> > > Voce verificou o endereco? Se este eh o unico endereco
> > > que voce tem desta pessoa, mande um e-mail para nos e
> > > tentaremos localiza-lo para voce.
> 
> Have you checked the address?  If this is the only address that you
> have of this person, send us an e-mail and we will try to locate him
> for you.
> 
> > > Um Abraco!
> 
> A hug!
> 
> -- 
> John Rickard
> 


From owner-disman@dorothy.peer.com  Thu Oct  5 13:25:47 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03534
	for <disman-archive@odin.ietf.org>; Thu, 5 Oct 2000 13:25:47 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e95HIc016203;
	Thu, 5 Oct 2000 12:18:38 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02734
	for disman-list; Thu, 5 Oct 2000 10:16:21 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02728;
	Thu, 5 Oct 2000 10:16:17 -0700 (PDT)
Date: Thu, 5 Oct 2000 10:16:17 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010051716.KAA02728@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd: RFC 2925 on Ping, Traceroute, and Lookup MIBs
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e95HIc016203
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA03534


Hi -

I'm forwarding a post from rfc-ed@ISI.EDU to the disman WG
mailing list.  I've added rfc-ed@ISI.EDU to the disman
posters list so that future postings from that address
won't be bounced.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA00649
> 	for <disman@dorothy.peer.com>; Wed, 4 Oct 2000 15:48:25 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e94Mm9d15759
> 	for <disman@dorothy.bmc.com>; Wed, 4 Oct 2000 17:48:09 -0500 (CDT)
> Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
> 	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA16397;
> 	Wed, 4 Oct 2000 15:49:13 -0700 (PDT)
> Message-Id: <200010042249.PAA16397@boreas.isi.edu>
> To: IETF-Announce: ;
> Subject: RFC 2925 on Ping, Traceroute, and Lookup MIBs
> Cc: rfc-ed@ISI.EDU, disman@dorothy.bmc.com
> Mime-Version: 1.0
> Content-Type: Multipart/Mixed; Boundary=NextPart
> Date: Wed, 04 Oct 2000 15:49:13 -0700
> From: RFC Editor <rfc-ed@ISI.EDU>
> 
> 
> --NextPart
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 2925
> 
>         Title:	    Definitions of Managed Objects for Remote Ping,
>                     Traceroute, and Lookup Operations
>         Author(s):  K. White
>         Status:     Standards Track
> 	Date:       September 2000
>         Mailbox:    wkenneth@us.ibm.com
>         Pages:      77
>         Characters: 150691
>         Updates/Obsoletes/SeeAlso:  None
> 
>         I-D Tag:    draft-ietf-disman-remops-mib-08.txt
> 
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2925.txt
> 
> 
> This memo defines Management Information Bases (MIBs) for performing
> remote ping, traceroute and lookup operations at a remote host.  When
> managing a network it is useful to be able to initiate and retrieve
> the results of ping or traceroute operations when performed at a
> remote host.  A Lookup capability is defined in order to enable
> resolving of either an IP address to an DNS name or an DNS name to an
> IP address at a remote host.
>  
> Currently, there are several enterprise-specific MIBs for performing
> remote ping or traceroute operations.  The purpose of this memo is to
> define a standards-based solution to enable interoperability.
> 
> This document is a product of the Distributed Management Working Group
> of the IETF.
> 
> This is now a Proposed Standard Protocol. 
> 
> This document specifies an Internet standards track protocol for
> the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the
> "Internet Official Protocol Standards" (STD 1) for the
> standardization state and status of this protocol.  Distribution
> of this memo is unlimited.
> 
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
> help: ways_to_get_rfcs.  For example:
> 
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
> 
>         help: ways_to_get_rfcs
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.echo 
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
> 
> 
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
> 
> ...
> 
> Below is the data which will enable a MIME compliant Mail Reader 
> implementation to automatically retrieve the ASCII version
> of the RFCs.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type:  Message/External-body;
>         access-type="mail-server";
>         server="RFC-INFO@RFC-EDITOR.ORG"
> 
> Content-Type: text/plain
> Content-ID: <001004154405.RFC@RFC-EDITOR.ORG>
> 
> RETRIEVE: rfc
> DOC-ID: rfc2925
> 
> --OtherAccess
> Content-Type:   Message/External-body;
>         name="rfc2925.txt";
>         site="ftp.isi.edu";
>         access-type="anon-ftp";
>         directory="in-notes"
> 
> Content-Type: text/plain
> Content-ID: <001004154405.RFC@RFC-EDITOR.ORG>
> 
> --OtherAccess--
> --NextPart--
> 


From owner-disman@dorothy.peer.com  Thu Oct  5 13:29:23 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03572
	for <disman-archive@odin.ietf.org>; Thu, 5 Oct 2000 13:29:23 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e95HQWt17783;
	Thu, 5 Oct 2000 12:26:32 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02861
	for disman-list; Thu, 5 Oct 2000 10:24:15 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02855;
	Thu, 5 Oct 2000 10:24:11 -0700 (PDT)
Date: Thu, 5 Oct 2000 10:24:11 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010051724.KAA02855@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd:FW: RFC 2925 on Ping, Traceroute, and Lookup MIBs
Cc: FFernandes@unispherenetworks.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e95HQWt17783
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA03572


Hi -

I'm forwarding a post from <FFernandes@unispherenetworks.com>
to the disman WG mailing list.  I've added
<FFernandes@unispherenetworks.com> to the "posters" list so
that future postings from that address won't be bounced.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id FAA02009
> 	for <disman@dorothy.peer.com>; Thu, 5 Oct 2000 05:59:42 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e95CxMg11714
> 	for <disman@dorothy.peer.com>; Thu, 5 Oct 2000 07:59:22 -0500 (CDT)
> Received: by uniwest1.redstonecom.com with Internet Mail Service (5.5.2650.21)
> 	id <TNL6G2R7>; Thu, 5 Oct 2000 09:00:22 -0400
> Message-ID: <49FF5C6DDBD8D311BBBD009027DE980CCBD1D9@uniwest1.redstonecom.com>
> From: "Fernandes, Flavio" <FFernandes@unispherenetworks.com>
> To: disman@dorothy.bmc.com
> Subject: FW: RFC 2925 on Ping, Traceroute, and Lookup MIBs
> Date: Thu, 5 Oct 2000 09:00:11 -0400 
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: multipart/mixed;
> 	boundary="----_=_NextPart_000_01C02ECC.32135DF0"
> 
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> 
> ------_=_NextPart_000_01C02ECC.32135DF0
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> -----Original Message-----
> From: RFC Editor [mailto:rfc-ed@ISI.EDU]
> Sent: Wednesday, October 04, 2000 6:49 PM
> Cc: rfc-ed@ISI.EDU; disman@dorothy.bmc.com
> Subject: RFC 2925 on Ping, Traceroute, and Lookup MIBs
> 
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 2925
> 
>         Title:	    Definitions of Managed Objects for Remote Ping,
>                     Traceroute, and Lookup Operations
>         Author(s):  K. White
>         Status:     Standards Track
> 	Date:       September 2000
>         Mailbox:    wkenneth@us.ibm.com
>         Pages:      77
>         Characters: 150691
>         Updates/Obsoletes/SeeAlso:  None
> 
>         I-D Tag:    draft-ietf-disman-remops-mib-08.txt
> 
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2925.txt
> 
> 
> This memo defines Management Information Bases (MIBs) for performing
> remote ping, traceroute and lookup operations at a remote host.  When
> managing a network it is useful to be able to initiate and retrieve
> the results of ping or traceroute operations when performed at a
> remote host.  A Lookup capability is defined in order to enable
> resolving of either an IP address to an DNS name or an DNS name to an
> IP address at a remote host.
>  
> Currently, there are several enterprise-specific MIBs for performing
> remote ping or traceroute operations.  The purpose of this memo is to
> define a standards-based solution to enable interoperability.
> 
> This document is a product of the Distributed Management Working Group
> of the IETF.
> 
> This is now a Proposed Standard Protocol. 
> 
> This document specifies an Internet standards track protocol for
> the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the
> "Internet Official Protocol Standards" (STD 1) for the
> standardization state and status of this protocol.  Distribution
> of this memo is unlimited.
> 
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
> help: ways_to_get_rfcs.  For example:
> 
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
> 
>         help: ways_to_get_rfcs
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.echo 
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
> 
> 
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
> 
> ...
> 
> Below is the data which will enable a MIME compliant Mail Reader 
> implementation to automatically retrieve the ASCII version
> of the RFCs.
> 
> 
> ------_=_NextPart_000_01C02ECC.32135DF0
> Content-Type: message/rfc822
> 
> To: 
> Subject: 
> Date: Thu, 5 Oct 2000 09:00:22 -0400 
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: multipart/mixed;
> 	boundary="----_=_NextPart_002_01C02ECC.32135DF0"
> 
> 
> ------_=_NextPart_002_01C02ECC.32135DF0
> Content-Type: text/plain
> 
> 
> 
> ------_=_NextPart_002_01C02ECC.32135DF0
> Content-Type: application/octet-stream;
> 	name="ATT49717.txt"
> Content-Disposition: attachment;
> 	filename="ATT49717.txt"
> 
> Content-type: message/external-body;
> 	access-type="mail-server";
> 	server="RFC-INFO@RFC-EDITOR.ORG"
> 
> Content-Type: text/plain
> Content-ID: <001004154405.RFC@RFC-EDITOR.ORG>
> 
> RETRIEVE: rfc
> DOC-ID: rfc2925
> 
> ------_=_NextPart_002_01C02ECC.32135DF0
> Content-Type: message/external-body;
> 	site="in-notes";
> 	dir="rfc2925.txt";
> 	mode="ftp.isi.edu";
> 	access-type="anon-ftp"
> 
> 
> ------_=_NextPart_002_01C02ECC.32135DF0--
> 
> ------_=_NextPart_000_01C02ECC.32135DF0--
> 


From owner-disman@dorothy.peer.com  Thu Oct  5 13:45:26 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03880
	for <disman-archive@odin.ietf.org>; Thu, 5 Oct 2000 13:45:21 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e95Hg9821060;
	Thu, 5 Oct 2000 12:42:09 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02979
	for disman-list; Thu, 5 Oct 2000 10:39:33 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA02973;
	Thu, 5 Oct 2000 10:39:30 -0700 (PDT)
Date: Thu, 5 Oct 2000 10:39:30 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010051739.KAA02973@dorothy.bmc.com>
To: disman@dorothy.peer.com, rpresuhn@dorothy.peer.com
Subject: Re:  Fwd: RFC 2925 on Ping, Traceroute, and Lookup MIBs
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e95Hg9821060
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA03880


Hi -

I'd like to offer a big THANK YOU & congratulations to Ken, our
reviewers (Juergen and David Partain) and the working group for
a job well done!

...
>         RFC 2925
> 
>         Title:	    Definitions of Managed Objects for Remote Ping,
>                     Traceroute, and Lookup Operations
>         Author(s):  K. White
>         Status:     Standards Track
...

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------


From owner-disman@dorothy.peer.com  Thu Oct  5 14:42:45 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04656
	for <disman-archive@odin.ietf.org>; Thu, 5 Oct 2000 14:42:44 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e95IcQd03781;
	Thu, 5 Oct 2000 13:38:26 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA03653
	for disman-list; Thu, 5 Oct 2000 11:34:06 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA03648
	for <Disman@dorothy.peer.com>; Thu, 5 Oct 2000 11:34:02 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e95IXjR02709
	for <Disman@dorothy.peer.com>; Thu, 5 Oct 2000 13:33:45 -0500 (CDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA21307
	for <Disman@dorothy.peer.com>; Thu, 5 Oct 2000 14:34:36 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA21288
	for <Disman@dorothy.peer.com>; Thu, 5 Oct 2000 14:34:35 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <42N1Y5TY>; Thu, 5 Oct 2000 20:34:30 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB097AA579@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Disman@dorothy.peer.com
Subject: RE: Fwd: RFC 2925 on Ping, Traceroute, and Lookup MIBs
Date: Thu, 5 Oct 2000 20:34:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>


Inline

> ----------
> From: 	Randy Presuhn[SMTP:rpresuhn@dorothy.peer.com]
> Sent: 	Thursday, October 05, 2000 7:39 PM
> To: 	disman@dorothy.peer.com; rpresuhn@dorothy.peer.com
> Subject: 	Re:  Fwd: RFC 2925 on Ping, Traceroute, and Lookup MIBs
> 
> 
> Hi -
> 
> I'd like to offer a big THANK YOU & congratulations to Ken, our
> reviewers (Juergen and David Partain) and the working group for
> a job well done!
> 
Well spoken words.
Thanks from your AD as well

Bert



From owner-disman@dorothy.peer.com  Tue Oct 10 08:39:37 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA02930
	for <disman-archive@odin.ietf.org>; Tue, 10 Oct 2000 08:38:42 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9ACPf212896;
	Tue, 10 Oct 2000 07:25:41 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA20890
	for disman-list; Tue, 10 Oct 2000 05:09:45 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id FAA20885
	for <disman@dorothy.peer.com>; Tue, 10 Oct 2000 05:09:40 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9AC9ML10251
	for <disman@dorothy.bmc.com>; Tue, 10 Oct 2000 07:09:22 -0500 (CDT)
Received: from pascal.unisinos.br (pascal.unisinos.br [10.16.163.2])
	by guru.unisinos.br (UNISINOS/) with ESMTP id e9ACAPN20381
	for <disman@dorothy.bmc.com>; Tue, 10 Oct 2000 10:10:26 -0200
Received: from PASCAL/SpoolDir by pascal.unisinos.br (Mercury 1.47);
    10 Oct 00 10:10:26 -0300
Received: from SpoolDir by PASCAL (Mercury 1.47); 10 Oct 00 10:10:07 -0300
Received: from skywalker (10.16.169.16) by pascal.unisinos.br (Mercury 1.47);
    10 Oct 00 10:10:07 -0300
Date: Tue, 10 Oct 2000 10:12:31 -0200
From: Luis F Balbinot <hades@ieee.org>
To: disman@dorothy.peer.com
Subject: Questions
X-Mailer: Sylpheed version 0.4.1 (GTK+ 1.2.8; Linux 2.2.16; i686)
Organization: Pesquisa em Redes de Alta Velocidade (PRAV)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID: <A37CFC629A@pascal.unisinos.br>
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hello,

I'm working on my dissertation and I have some questions
about the DISMAN WG. Don't worry, they're quite easy :)

The group defined, as part of the tasks, that the M2M MIB
would be considered. Well, as soon as I understand, this
MIB based the design of the Event MIB, right? And what
about the Notification Log MIB, is it based on it too?

Last one: how does the RMON WG work fit in the DISMAN
goals? Expression MIB?

Sorry for the (lame) questions, but I couldn't find a more
detailed document about the charter.

Thanks for your help!

Best Regards,
Luis F Balbinot <hades@ieee.org>
http://cscience.org/~hades


From owner-disman@dorothy.peer.com  Tue Oct 10 20:38:49 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16117
	for <disman-archive@odin.ietf.org>; Tue, 10 Oct 2000 20:38:48 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9B0UGT02860;
	Tue, 10 Oct 2000 19:30:16 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA09084
	for disman-list; Tue, 10 Oct 2000 17:27:53 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA09078
	for disman@dorothy.bmc.com; Tue, 10 Oct 2000 17:27:50 -0700 (PDT)
Date: Tue, 10 Oct 2000 17:27:50 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010110027.RAA09078@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Re:  Questions
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9B0UGT02860
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA16117


Hi -

> Date: Tue, 10 Oct 2000 10:12:31 -0200
> From: Luis F Balbinot <hades@ieee.org>
> To: disman@dorothy.bmc.com
> Subject: Questions
> Organization: Pesquisa em Redes de Alta Velocidade (PRAV)
> Message-ID: <A37CFC629A@pascal.unisinos.br>
> List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
...
> The group defined, as part of the tasks, that the M2M MIB
> would be considered. Well, as soon as I understand, this
> MIB based the design of the Event MIB, right? And what
> about the Notification Log MIB, is it based on it too?

"Based on" is a slippery phrase.

In addition to the M2M stuff, the RMON-MIB alarmTable and
eventTable are also part of the prior work that led up to
the design of the event and notification log MIB.  The much
older ISO/ITU work (IS 10164-* and the X.7xx series) also
played a part in the thinking.

> Last one: how does the RMON WG work fit in the DISMAN
> goals? Expression MIB?
...

This was discussed at some length around the time of the
rperfman BOF at the Adelaide IETF meeting.  Check out the
procedings for more background.  In short, when automated
monitoring or control can span instrumentation in multiple
systems, it's disman work.  RMON focuses on the operation of
a single probe (which may observe traffic on many interfaces).

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------


From owner-disman@dorothy.peer.com  Wed Oct 11 04:00:24 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04494
	for <disman-archive@odin.ietf.org>; Wed, 11 Oct 2000 04:00:24 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9B7u2O05080;
	Wed, 11 Oct 2000 02:56:06 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id AAA12479
	for disman-list; Wed, 11 Oct 2000 00:52:04 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id AAA12474
	for <disman@dorothy.peer.com>; Wed, 11 Oct 2000 00:52:01 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9B7pfK04477
	for <disman@dorothy.bmc.com>; Wed, 11 Oct 2000 02:51:42 -0500 (CDT)
Received: from ipb.pt ([212.55.186.95]) by fep02-svc.mail.telepac.pt
          (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP
          id <20001011075710.GLYA29419.fep02-svc.mail.telepac.pt@ipb.pt>
          for <disman@dorothy.bmc.com>; Wed, 11 Oct 2000 08:57:10 +0100
Message-ID: <39E41CB1.4050104@ipb.pt>
Date: Wed, 11 Oct 2000 08:54:25 +0100
From: RP <rlopes@ipb.pt>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14 i686; en-US; m17) Gecko/20000807
X-Accept-Language: en
MIME-Version: 1.0
To: disman@dorothy.peer.com
Subject: BITS construct question
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi.
I have a basic (I think) question about the BITS construct on the 
DISMAN-SCHEDULE-MIB (also on DISMAN-EVENT-MIB).
To issue an SNMP-SET to, for example, schedMonth to set january and 
december, the command should be:

$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 100000000001B

or

$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "100000000001"

or

$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "january"
$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "december"

or

$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 0
$ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 11

?
I tried the AdventNet MIB compiler and it generates code to store a 
String on the schedMonth object and validates it to be one of 
"january","february",...,"december".

I also tried the SMASH MIB compiler and it complaints about the DEFVAL { 
{ } }.

So, what is the data type to send to a BITS object? A string, a byte[], 
an int or other?
I looked the RFCs from 1066 to 2579 to look for how to set a BITS object 
and did not find nothing except that it is an enumeration of named bits. 
Now, how to set an enumeration of named bits? Send the name of the 
corresponding bit, send all the bits in an OCTET STRING or send the 
INTEGER correspondent to the bit position?

Thanks in advance.

Cheers,

Rui Pedro



From owner-disman@dorothy.peer.com  Wed Oct 11 05:26:04 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA05077
	for <disman-archive@odin.ietf.org>; Wed, 11 Oct 2000 05:26:04 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9B9Luq17710;
	Wed, 11 Oct 2000 04:22:00 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id CAA12694
	for disman-list; Wed, 11 Oct 2000 02:19:59 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA12689
	for <disman@dorothy.peer.com>; Wed, 11 Oct 2000 02:19:49 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9B9JTg17380
	for <disman@dorothy.peer.com>; Wed, 11 Oct 2000 04:19:30 -0500 (CDT)
Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137])
	by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id LAA02628;
	Wed, 11 Oct 2000 11:18:51 +0200 (MET DST)
Received: (from strauss@localhost)
	by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id LAA26066;
	Wed, 11 Oct 2000 11:18:50 +0200
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: strauss set sender to strauss@ibr.cs.tu-bs.de using -f
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: RP <rlopes@ipb.pt>
Cc: disman@dorothy.peer.com
Subject: Re: BITS construct question
References: <39E41CB1.4050104@ipb.pt>
Date: 11 Oct 2000 11:18:50 +0200
In-Reply-To: RP's message of "11 Oct 2000 09:59:09 +0200"
Message-ID: <ypwbswrivlx.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 64
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>


RP> I have a basic (I think) question about the BITS construct on the 
RP> DISMAN-SCHEDULE-MIB (also on DISMAN-EVENT-MIB).
RP> To issue an SNMP-SET to, for example, schedMonth to set january and 
RP> december, the command should be:

RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 100000000001B
RP> or
RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "100000000001"
RP> or
RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "january"
RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v "december"
RP> or
RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 0
RP> $ ./set localhost .1.3.6.1.2.1.63.1.2.1.6.x.y.z.v 11
RP> ?

In the sense of SMI syntax the first notation (100000000001B) should
do what you expect. It depends on what your `./set' does to interpret
the last argument. Maybe it is so clever to see from its own MIB
knowledge that `.1.3.6.1.2.1.63.1.2.1.6' is a BITS type and does
the appropriate transformation.

Anyhow, an SMIv2 BITS construct is mapped to an OCTET STRING in the
protocol, where each bit of each octet (except the padding bits)
represents one bit of the BITS construct.

RP> I tried the AdventNet MIB compiler and it generates code to store a 
RP> String on the schedMonth object and validates it to be one of 
RP> "january","february",...,"december".

As far as I understand your description of the generated code, this is
wrong, but maybe I misunderstand what the compiler generated.

RP> I also tried the SMASH MIB compiler and it complaints about the
RP> DEFVAL { { } }.

Seems to be a bad compiler. ;-)

RP> So, what is the data type to send to a BITS object? A string, a
RP> byte[], an int or other?

An OCTET STRING on the wire, whatever your SNMP toolkit matches it to
in your application code.  A byte array would be reasonable along with
some functions to check and modify single bits.

RP> I looked the RFCs from 1066 to 2579 to look for how to set a BITS
RP> object and did not find nothing except that it is an enumeration
RP> of named bits.  Now, how to set an enumeration of named bits? Send
RP> the name of the corresponding bit, send all the bits in an OCTET
RP> STRING or send the INTEGER correspondent to the bit position?

Send all the bits in an OCTET STRING.

See RFC 1906, Section 8 for the exact protocol encoding of BITS:

   (3)  When encoding an object whose syntax is described using the BITS
        construct, the value is encoded as an OCTET STRING, in which all
        the named bits in (the definition of) the bitstring, commencing
        with the first bit and proceeding to the last bit, are placed in
        bits 8 to 1 of the first octet, followed by bits 8 to 1 of each
        subsequent octet in turn, followed by as many bits as are needed of
        the final subsequent octet, commencing with bit 8.  Remaining bits,
        if any, of the final octet are set to zero on generation and
        ignored on receipt.


From owner-disman@dorothy.peer.com  Wed Oct 11 16:59:37 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21613
	for <disman-archive@odin.ietf.org>; Wed, 11 Oct 2000 16:59:36 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9BKhYW16319;
	Wed, 11 Oct 2000 15:43:35 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA14885
	for disman-list; Wed, 11 Oct 2000 13:40:15 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA14879;
	Wed, 11 Oct 2000 13:40:12 -0700 (PDT)
Date: Wed, 11 Oct 2000 13:40:12 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010112040.NAA14879@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd: Feature request for the Expression MIB
Cc: lheintz@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9BKhYW16319
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA21613


hi -

I'm forwarding a non-subscriber post to the disman WG list.
Subscription information is available at
http://www.ietf.org/html.charters/disman-charter.html

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA14819
> 	for <disman@dorothy.peer.com>; Wed, 11 Oct 2000 13:36:55 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9BKaVD14843
> 	for <disman@dorothy.bmc.com>; Wed, 11 Oct 2000 15:36:31 -0500 (CDT)
> Received: from fedex.cisco.com (fedex.cisco.com [171.69.18.27])
> 	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id NAA09672
> 	for <disman@dorothy.bmc.com>; Wed, 11 Oct 2000 13:37:42 -0700 (PDT)
> Received: from cisco.com (dhcp-171-68-129-192.cisco.com [171.68.129.192])
> 	by fedex.cisco.com (Mirapoint)
> 	with ESMTP id AFM04033 (AUTH lheintz);
> 	Wed, 11 Oct 2000 13:37:39 -0700 (PDT)
> Message-ID: <39E4CF57.36ED4735@cisco.com>
> Date: Wed, 11 Oct 2000 13:36:39 -0700
> From: Lauren Heintz <lheintz@cisco.com>
> Reply-To: lheintz@cisco.com
> Organization: Cisco Systems
> X-Mailer: Mozilla 4.5 [en] (WinNT; U)
> X-Accept-Language: en
> MIME-Version: 1.0
> To: disman@dorothy.bmc.com
> Subject: Feature request for the Expression MIB
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Hi,
> 
> I have a problem I'm trying to solve, and it
> seems that the Expression MIB is very close
> to what we need.  The key word here being "close."
> 
> I would like to suggest that future versions of
> the expression MIB support two new functions:
> topN(expression), bottomN(expression)?
> 
> Such expressions would allow one to pose
> queries such as:
> 
> What 10 interfaces had the greatest (top N=10)
> change in ifInErrors over the last 60 minutes?
> 
> What 5 golfers had the best scores (bottom N=5)
> posted in the last day?  (no sense asking
> for N=1 since we already know the answer)
> 
> Of course, I'm not suggesting you also design
> a golfing MIB.  That would instead be done
> in the appropriate IETF Playing-Group, which
> I would be willing to chair.
> 
> Does this seem like an appropriate enhancement
> to the expMIB, and would there be support for it?
> 
> Thanks,
> Lauren
> 


From owner-disman@dorothy.peer.com  Thu Oct 12 19:24:17 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA07716
	for <disman-archive@odin.ietf.org>; Thu, 12 Oct 2000 19:24:16 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9CNC9i02100;
	Thu, 12 Oct 2000 18:12:13 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA19969
	for disman-list; Thu, 12 Oct 2000 16:09:23 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id QAA19964
	for <disman@dorothy.peer.com>; Thu, 12 Oct 2000 16:09:08 -0700 (PDT)
From: ramk@cisco.com
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9CN8lT01503
	for <disman@dorothy.bmc.com>; Thu, 12 Oct 2000 18:08:47 -0500 (CDT)
Received: from itech-view5.cisco.com (itech-view5.cisco.com [171.69.63.172])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id QAA09275;
	Thu, 12 Oct 2000 16:08:11 -0700 (PDT)
Received: (ramk@localhost) by itech-view5.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA05194; Thu, 12 Oct 2000 16:08:10 -0700 (PDT)
Message-Id: <200010122308.QAA05194@itech-view5.cisco.com>
Subject: draft-ietf-disman-notif-log-mib-17.txt
To: internet-drafts@ietf.org
Date: Thu, 12 Oct 2000 16:08:10 -0700 (PDT)
Cc: disman@dorothy.peer.com
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Please accept draft-ietf-disman-notif-log-mib-17.txt for posting
as an internet-draft. It contains changes suggested by the IESG and
the disman working group...

Thank you,

Ram Kavasseri









Network Working Group                           Editor of this version:
Internet-Draft                                  Ramanathan R. Kavasseri
Expires April 2001                                  Cisco Systems, Inc.
                                            Author of previous version:
                                                            Bob Stewart
                                                        12 October 2000



                          Notification Log MIB

                 draft-ietf-disman-notif-log-mib-17.txt


                          Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other groups
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.''

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

Distribution of this document is unlimited. Please send comments to the
Distributed Management Working Group, <disman@dorothy.BMC.com>.


Copyright Notice

Copyright (C) The Internet Society (2000).  All Rights Reserved.















Internet Draft            Notification Log MIB           12 October 2000


1.  Abstract

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for logging SNMP
Notifications.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.


2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

    o   An overall architecture, described in RFC 2571 [RFC2571].

    o   Mechanisms for describing and naming objects and events for the
        purpose of management. The first version of this Structure of
        Management Information (SMI) is called SMIv1 and described in
        STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
        1215 [RFC1215]. The second version, called SMIv2, is described
        in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580
        [RFC2580].

    o   Message protocols for transferring management information. The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, RFC 1157 [RFC1157]. A second version of the
        SNMP message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
        and RFC 1906 [RFC1906]. The third version of the message
        protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
        RFC 2572 [RFC2572] and RFC 2574 [RFC2574].

    o   Protocol operations for accessing management information. The
        first set of protocol operations and associated PDU formats is
        described in STD 15, RFC 1157 [RFC1157]. A second set of
        protocol operations and associated PDU formats is described in
        RFC 1905 [RFC1905].

    o   A set of fundamental applications described in RFC 2573
        [RFC2573] and the view-based access control mechanism described
        in RFC 2575 [RFC2575].





Expires 12 April 2001                                           [Page 2]





Internet Draft            Notification Log MIB           12 October 2000


   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process. However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.


3.  Overview

Systems that support SNMP often need a mechanism for recording
Notification information as a hedge against lost Notifications, whether
those are Traps or Informs [RFC1905] that exceed retransmission limits.
This MIB therefore provides common infrastructure for other MIBs in the
form of a local logging function.  It is intended primarily for senders
of Notifications but could be used also by receivers.

Given the Notification Log MIB, individual MIBs bear less responsibility
to record the transient information associated with an event against the
possibility that the Notification message is lost, and applications can
poll the log to verify that they have not missed important
Notifications.


3.1.  Environment

The overall environmental concerns for the MIB are:

    o   SNMP Engines and Contexts

    o   Security









Expires 12 April 2001                                           [Page 3]





Internet Draft            Notification Log MIB           12 October 2000


3.1.1.  SNMP Engines and Contexts

There are two distinct information flows from multiple notification
originators that one may log. The first is the notifications that are
received (from one or more SNMP engines) for logging as SNMP informs and
traps. The other comprises notifications delivered to an SNMP engine at
the interface to the notification originator (using a notification
mechanism other than SNMP informs or traps).  The latter information
flow (using a notification mechanism other than SNMP informs or traps)
is modeled here as the SNMP engine (which maintains the log) sending a
notification to itself. The remainder of this section discusses the
handling of the former information flow - notifications (received in the
form of SNMP informs or traps) from multiple SNMP engines.

As described in the SNMP architecture [RFC2571], a given system may
support multiple SNMP engines operating independently of one another,
each with its own SNMP engine identification.  Furthermore, within the
purview of a given engine there may be multiple named management
contexts supporting overlapping or disjoint sets of MIB objects and
Notifications.  Thus, understanding a particular Notification requires
knowing the SNMP engine and management context from whence it came.

To provide the necessary source information for a logged Notification,
the MIB includes objects to record that Notification's source SNMP
engine ID and management context name.


3.1.2.  Security

Security for Notifications is awkward since access control for the
objects in the Notification can be checked only where the Notification
is created.  Thus such checking is possible only for locally-generated
Notifications, and even then only when security credentials are
available.

For the purpose of this discussion, "security credentials" means the
input values for the abstract service interface function isAccessAllowed
[RFC2571] and using those credentials means conceptually using that
function to see that those credentials allow access to the MIB objects
in question, operating as for a Notification Originator in [RFC2573].

The Notification Log MIB has the notion of a "named log."  By using log
names and view-based access control [RFC2575] a network administrator
can provide different access for different users.  When an application
creates a named log the security credentials of the creator stay





Expires 12 April 2001                                           [Page 4]





Internet Draft            Notification Log MIB           12 October 2000


associated with that log.

A managed system with fewer resources MAY disallow the creation of named
logs, providing only the default, null-named log.  Such a log has no
implicit security credentials for Notification object access control and
Notifications are put into it with no further checking.

When putting locally-generated Notifications into a named log, the
managed system MUST use the security credentials associated with that
log and MUST apply the same access control rules as described for a
Notification Originator in [RFC2573].

The managed system SHOULD NOT apply access control when adding remotely-
generated Notifications into either a named log or the default, null-
named log. In those cases the security of the information in the log
SHOULD be left to the normal, overall access control for the log itself.

The Notification Log MIB allows applications to set the maximum number
of Notifications that can be logged, using nlmConfigGlobalEntryLimit.
Similarly, an application can set the maximum age using
nlmConfigGlobalAgeOut, after which older Notifications MAY be timed out.
Please be aware that contention between multiple applications trying to
set these objects to different values MAY affect the reliability and
completeness of data seen by each application, i.e. it is possible that
one application may change the value of either of these objects,
resulting in some Notifications being deleted before the other
applications have had a chance to see them. This could be used to
orchestrate a denial-of-service attack.  Methods for countering such an
attack are for further study.


3.2.  Structure

The MIB has the following sections:

    o   Configuration -- control over how much the log can hold and what
        Notifications are to be logged.

    o   Statistics -- indications of logging activity.

    o   Log -- the Notifications themselves.









Expires 12 April 2001                                           [Page 5]





Internet Draft            Notification Log MIB           12 October 2000


3.2.1.  Configuration

The configuration section contains objects to manage resource use by the
MIB.

This section also contains a table to specify what logs exist and how
they operate.  Deciding which Notifications are to be logged depends on
filters defined in the the snmpNotifyFilterTable in the standard SNMP
Notification MIB [RFC2573] identified by the initial index
(snmpNotifyFilterName) from that table.


3.2.2.  Statistics

The statistics section contains counters for Notifications logged and
discarded, supplying a means to understand the results of log capacity
configuration and resource problems.


3.2.3.  Log

The log contains the Notifications and the objects that came in their
variable binding list, indexed by an integer that reflects when the
entry was made.  An application that wants to collect all logged
Notifications or to know if it may have missed any can keep track of the
highest index it has retrieved and start from there on its next poll,
checking sysUpTime for a discontinuity that would have reset the index
and perhaps have lost entries.

Variables are in a table indexed by Notification index and variable
index within that Notification.  The values are kept as a "discriminated
union," with one value object per variable.  Exactly which value object
is instantiated depends on the SNMP data type of the variable, with a
separate object of appropriate type for each distinct SNMP data type.

An application can thus reconstruct the information from the
Notification PDU from what is recorded in the log.


3.3.  Example

Following is an example configuration of a named log for logging only
linkUp and linkDown Notifications.

In nlmConfigLogTable:





Expires 12 April 2001                                           [Page 6]





Internet Draft            Notification Log MIB           12 October 2000


    nlmConfigLogFilterName.5."links"    = "link-status"
    nlmConfigLogEntryLimit.5."links"    = 0
    nlmConfigLogAdminStatus.5."links"   = enabled
    nlmConfigLogOperStatus.5."links"    = operational
    nlmConfigLogStorageType.5."links"   = nonVolatile
    nlmConfigLogEntryStatus.5."links"   = active

Note that snmpTraps is:

    iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.5

Or numerically:

    1.3.6.1.6.3.1.1.5

And linkDown is snmpTraps.3 and linkUp is snmpTraps.4.

So to allow the two Notifications in snmpNotifyFilterTable:

    snmpNotifyFilterMask.11."link-status".1.3.6.1.6.3.1.1.5.3 = ''H
    snmpNotifyFilterType.11."link-status".1.3.6.1.6.3.1.1.5.3 = include
    snmpNotifyFilterStorageType.11."link-status".1.3.6.1.6.3.1.1.5.3
     = nonVolatile
    snmpNotifyFilterRowStatus.11."link-status".1.3.6.1.6.3.1.1.5.3
     = active

    snmpNotifyFilterMask.11."link-status".1.3.6.1.6.3.1.1.5.4 = ''H
    snmpNotifyFilterType.11."link-status".1.3.6.1.6.3.1.1.5.4 = include
    snmpNotifyFilterStorageType.11."link-status".1.3.6.1.6.3.1.1.5.4
     = nonVolatile
    snmpNotifyFilterRowStatus.11."link-status".1.3.6.1.6.3.1.1.5.4
     = active


















Expires 12 April 2001                                           [Page 7]





Internet Draft            Notification Log MIB           12 October 2000


4.  Definitions

NOTIFICATION-LOG-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE,
    Integer32, Unsigned32,
    TimeTicks, Counter32, Counter64,
    IpAddress, Opaque, mib-2       FROM SNMPv2-SMI
    TimeStamp, DateAndTime,
    StorageType, RowStatus,
    TAddress, TDomain              FROM SNMPv2-TC
    SnmpAdminString, SnmpEngineID  FROM SNMP-FRAMEWORK-MIB
    MODULE-COMPLIANCE, OBJECT-GROUP     FROM SNMPv2-CONF;

notificationLogMIB MODULE-IDENTITY
    LAST-UPDATED "200010120000Z"            -- 12 October 2000
    ORGANIZATION "IETF Distributed Management Working Group"
    CONTACT-INFO "Ramanathan Kavasseri
                  Cisco Systems, Inc.
                  170 West Tasman Drive,
                  San Jose CA 95134-1706.
                  Phone: +1 408 527 2446
                  Email: ramk@cisco.com"
    DESCRIPTION
     "The MIB module for logging SNMP Notifications, that is, Traps
     and Informs."
-- Revision History

       REVISION     "200010120000Z"            -- 12 October 2000
       DESCRIPTION  "This is the initial version of this MIB.
               Published as RFC xxxx"
    ::= { mib-2 xx } -- final assignment by IANA at publication time


notificationLogMIBObjects OBJECT IDENTIFIER ::= { notificationLogMIB 1 }

nlmConfig OBJECT IDENTIFIER ::= { notificationLogMIBObjects 1 }
nlmStats  OBJECT IDENTIFIER ::= { notificationLogMIBObjects 2 }
nlmLog         OBJECT IDENTIFIER ::= { notificationLogMIBObjects 3 }

--
-- Configuration Section
--






Expires 12 April 2001                                           [Page 8]





Internet Draft            Notification Log MIB           12 October 2000


nlmConfigGlobalEntryLimit OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
     "The maximum number of notification entries that may be held
     in nlmLogTable for all nlmLogNames added together.  A particular
     setting does not guarantee that much data can be held.

     If an application changes the limit while there are
     Notifications in the log, the oldest Notifications MUST be
     discarded to bring the log down to the new limit - thus the
     value of nlmConfigGlobalEntryLimit MUST take precedence over
     the values of nlmConfigGlobalAgeOut and nlmConfigLogEntryLimit,
     even if the Notification being discarded has been present for
     fewer minutes than the value of nlmConfigGlobalAgeOut, or if
     the named log has fewer entries than that specified in
     nlmConfigLogEntryLimit.

     A value of 0 means no limit.

     Please be aware that contention between multiple managers
     trying to set this object to different values MAY affect the
     reliability and completeness of data seen by each manager."
    DEFVAL { 0 }
    ::= { nlmConfig 1 }

nlmConfigGlobalAgeOut OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "minutes"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
     "The number of minutes a Notification SHOULD be kept in a log before
     it is automatically removed.

     If an application changes the value of nlmConfigGlobalAgeOut,
     Notifications older than the new time MAY be discarded to meet the
     new time.

     A value of 0 means no age out.

     Please be aware that contention between multiple managers
     trying to set this object to different values MAY affect the
     reliability and completeness of data seen by each manager."





Expires 12 April 2001                                           [Page 9]





Internet Draft            Notification Log MIB           12 October 2000


    DEFVAL { 1440 }  -- 24 hours
    ::= { nlmConfig 2 }


--
-- Basic Log Configuration Table
--

nlmConfigLogTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF NlmConfigLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A table of logging control entries."
    ::= { nlmConfig 3 }

nlmConfigLogEntry OBJECT-TYPE
    SYNTAX      NlmConfigLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A logging control entry.  Depending on the entry's storage type
     entries may be supplied by the system or created and deleted by
     applications using nlmConfigLogEntryStatus."
    INDEX      { nlmLogName }
    ::= { nlmConfigLogTable 1 }

NlmConfigLogEntry ::= SEQUENCE {
    nlmLogName           SnmpAdminString,
    nlmConfigLogFilterName    SnmpAdminString,
    nlmConfigLogEntryLimit    Unsigned32,
    nlmConfigLogAdminStatus   INTEGER,
    nlmConfigLogOperStatus    INTEGER,
    nlmConfigLogStorageType   StorageType,
    nlmConfigLogEntryStatus   RowStatus
    }

nlmLogName OBJECT-TYPE
    SYNTAX     SnmpAdminString (SIZE(0..32))
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
     "The name of the log.

     An implementation may allow multiple named logs, up to some





Expires 12 April 2001                                          [Page 10]





Internet Draft            Notification Log MIB           12 October 2000


     implementation-specific limit (which may be none).  A
     zero-length log name is reserved for creation and deletion by
     the managed system, and MUST be used as the default log name by
     systems that do not support named logs."
    ::= { nlmConfigLogEntry 1 }

nlmConfigLogFilterName OBJECT-TYPE
    SYNTAX     SnmpAdminString (SIZE(0..32))
    MAX-ACCESS read-create
    STATUS     current
    DESCRIPTION
     "A value of snmpNotifyFilterProfileName as used as an index
     into the snmpNotifyFilterTable in the SNMP Notification MIB,
     specifying the locally or remotely originated Notifications
     to be filtered out and not logged in this log.

     A zero-length value or a name that does not identify an
     existing entry in snmpNotifyFilterTable indicate no
     Notifications are to be logged in this log."
    DEFVAL { ''H }
    ::= { nlmConfigLogEntry 2 }

nlmConfigLogEntryLimit OBJECT-TYPE
    SYNTAX     Unsigned32
    MAX-ACCESS read-create
    STATUS     current
    DESCRIPTION
     "The maximum number of notification entries that can be held in
     nlmLogTable for this named log.  A particular setting does not
     guarantee that that much data can be held.

     If an application changes the limit while there are
     Notifications in the log, the oldest Notifications are discarded
     to bring the log down to the new limit.

     A value of 0 indicates no limit.

     Please be aware that contention between multiple managers
     trying to set this object to different values MAY affect the
     reliability and completeness of data seen by each manager."
    DEFVAL { 0 }
    ::= { nlmConfigLogEntry 3 }

nlmConfigLogAdminStatus OBJECT-TYPE
    SYNTAX     INTEGER { enabled(1), disabled(2) }





Expires 12 April 2001                                          [Page 11]





Internet Draft            Notification Log MIB           12 October 2000


    MAX-ACCESS read-create
    STATUS     current
    DESCRIPTION
     "Control to enable or disable the log without otherwise
     disturbing the log's entry.

     Please be aware that contention between multiple managers
     trying to set this object to different values MAY affect the
     reliability and completeness of data seen by each manager."
    DEFVAL { enabled }
    ::= { nlmConfigLogEntry 4 }

nlmConfigLogOperStatus OBJECT-TYPE
    SYNTAX     INTEGER { disabled(1), operational(2), noFilter(3) }
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
     "The operational status of this log:

          disabled  administratively disabled

          operational    administratively enabled and working

          noFilter  administratively enabled but either
                    nlmConfigLogFilterName is zero length
                    or does not name an existing entry in
                    snmpNotifyFilterTable"
    ::= { nlmConfigLogEntry 5 }

nlmConfigLogStorageType OBJECT-TYPE
    SYNTAX     StorageType
    MAX-ACCESS read-create
    STATUS     current
    DESCRIPTION
     "The storage type of this conceptual row."
    ::= { nlmConfigLogEntry 6 }

nlmConfigLogEntryStatus OBJECT-TYPE
    SYNTAX     RowStatus
    MAX-ACCESS read-create
    STATUS     current
    DESCRIPTION
     "Control for creating and deleting entries.  Entries may be
     modified while active.






Expires 12 April 2001                                          [Page 12]





Internet Draft            Notification Log MIB           12 October 2000


     For non-null-named logs, the managed system records the security
     credentials from the request that sets nlmConfigLogStatus
     to 'active' and uses that identity to apply access control to
     the objects in the Notification to decide if that Notification
     may be logged."
    ::= { nlmConfigLogEntry 7 }

--
-- Statistics Section
--

nlmStatsGlobalNotificationsLogged OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "notifications"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The number of Notifications put into the nlmLogTable.  This
     counts a Notification once for each log entry, so a Notification
      put into multiple logs is counted multiple times."
    ::= { nlmStats 1 }

nlmStatsGlobalNotificationsBumped OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "notifications"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The number of log entries discarded to make room for a new entry
     due to lack of resources or the value of nlmConfigGlobalEntryLimit
     or nlmConfigLogEntryLimit.  This does not include entries discarded
     due to the value of nlmConfigGlobalAgeOut."
    ::= { nlmStats 2 }

--
-- Log Statistics Table
--

nlmStatsLogTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF NlmStatsLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A table of Notification log statistics entries."
    ::= { nlmStats 3 }





Expires 12 April 2001                                          [Page 13]





Internet Draft            Notification Log MIB           12 October 2000


nlmStatsLogEntry OBJECT-TYPE
    SYNTAX      NlmStatsLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A Notification log statistics entry."
    AUGMENTS { nlmConfigLogEntry }
    ::= { nlmStatsLogTable 1 }

NlmStatsLogEntry ::= SEQUENCE {
    nlmStatsLogNotificationsLogged Counter32,
    nlmStatsLogNotificationsBumped Counter32
}

nlmStatsLogNotificationsLogged OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "notifications"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The number of Notifications put in this named log."
    ::= { nlmStatsLogEntry 1 }

nlmStatsLogNotificationsBumped OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "notifications"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The number of log entries discarded from this named log to make
     room for a new entry due to lack of resources or the value of
     nlmConfigGlobalEntryLimit or nlmConfigLogEntryLimit.  This does not
     include entries discarded due to the value of
     nlmConfigGlobalAgeOut."
    ::= { nlmStatsLogEntry 2 }


--
-- Log Section
--

--
-- Log Table
--






Expires 12 April 2001                                          [Page 14]





Internet Draft            Notification Log MIB           12 October 2000


nlmLogTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF NlmLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A table of Notification log entries.

     It is an implementation-specific matter whether entries in this
     table are preserved across initializations of the management
     system.  In general one would expect that they are not.

     Note that keeping entries across initializations of the
     management system leads to some confusion with counters and
     TimeStamps, since both of those are based on sysUpTime, which
     resets on management initialization.  In this situation,
     counters apply only after the reset and nlmLogTime for entries
     made before the reset MUST be set to 0."
    ::= { nlmLog 1 }

nlmLogEntry OBJECT-TYPE
    SYNTAX      NlmLogEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A Notification log entry.

     Entries appear in this table when Notifications occur and pass
     filtering by nlmConfigLogFilterName and access control.  They are
     removed to make way for new entries due to lack of resources or
     the values of nlmConfigGlobalEntryLimit, nlmConfigGlobalAgeOut, or
     nlmConfigLogEntryLimit.

     If adding an entry would exceed nlmConfigGlobalEntryLimit or system
     resources in general, the oldest entry in any log SHOULD be removed to
     make room for the new one.

     If adding an entry would exceed nlmConfigLogEntryLimit the oldest
     entry in that log SHOULD be removed to make room for the new one.

     Before the managed system puts a locally-generated Notification
     into a non-null-named log it assures that the creator of the log
     has access to the information in the Notification.  If not it
     does not log that Notification in that log."
    INDEX       { nlmLogName, nlmLogIndex }
    ::= { nlmLogTable 1 }





Expires 12 April 2001                                          [Page 15]





Internet Draft            Notification Log MIB           12 October 2000


NlmLogEntry ::= SEQUENCE {
    nlmLogIndex                Unsigned32,
    nlmLogTime                 TimeStamp,
    nlmLogDateAndTime          DateAndTime,
    nlmLogEngineID             SnmpEngineID,
    nlmLogEngineTAddress       TAddress,
    nlmLogEngineTDomain        TDomain,
    nlmLogContextEngineID      SnmpEngineID,
    nlmLogContextName          SnmpAdminString,
    nlmLogNotificationID       OBJECT IDENTIFIER
}

nlmLogIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (1..4294967295)
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
     "A monotonically increasing integer for the sole purpose of
     indexing entries within the named log.  When it reaches the
     maximum value, an extremely unlikely event, the agent wraps the
     value back to 1."
    ::= { nlmLogEntry 1 }

nlmLogTime OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value of sysUpTime when the entry was placed in the log. If
     the entry occurred before the most recent management system
     initialization this object value MUST be set to zero."
    ::= { nlmLogEntry 2 }

nlmLogDateAndTime OBJECT-TYPE
    SYNTAX      DateAndTime
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The local date and time when the entry was logged, instantiated
     only by systems that have date and time capability."
    ::= { nlmLogEntry 3 }

nlmLogEngineID OBJECT-TYPE
    SYNTAX      SnmpEngineID
    MAX-ACCESS  read-only





Expires 12 April 2001                                          [Page 16]





Internet Draft            Notification Log MIB           12 October 2000


    STATUS      current
    DESCRIPTION
     "The identification of the SNMP engine at which the Notification
     originated.

     If the log can contain Notifications from only one engine
     or the Trap is in SNMPv1 format, this object is a zero-length
     string."
    ::= { nlmLogEntry 4 }

nlmLogEngineTAddress OBJECT-TYPE
    SYNTAX      TAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The transport service address of the SNMP engine from which the
     Notification was received, formatted according to the corresponding
     value of nlmLogEngineTDomain. This is used to identify the source
     of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
     from the SNMPv1 trap pdu.

     This object MUST always be instantiated, even if the log
     can contain Notifications from only one engine.

     Please be aware that the nlmLogEngineTAddress may not uniquely
     identify the SNMP engine from which the Notification was received.
     For example, if an SNMP engine uses DHCP or NAT to obtain
     ip addresses, the address it uses may be shared with other
     network devices, and hence will not uniquely identify the
     SNMP engine."
    ::= { nlmLogEntry 5 }

nlmLogEngineTDomain OBJECT-TYPE
    SYNTAX      TDomain
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "Indicates the kind of transport service by which a Notification was
     received from an SNMP engine. nlmLogEngineTAddress contains the
     transport service address of the SNMP engine from which this
     Notification was received.

     Possible values for this object are presently found in the
     Transport Mappings for SNMPv2 document (RFC 1906 [8])."
    ::= { nlmLogEntry 6 }





Expires 12 April 2001                                          [Page 17]





Internet Draft            Notification Log MIB           12 October 2000


nlmLogContextEngineID OBJECT-TYPE
    SYNTAX      SnmpEngineID
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "If the Notification was received in a protocol which has a
      contextEngineID element like SNMPv3, this object has that value.
      Otherwise its value is a zero-length string."
     ::= { nlmLogEntry 7 }

nlmLogContextName OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The name of the SNMP MIB context from which the Notification came.
     For SNMPv1 Traps this is the community string from the Trap."
    ::= { nlmLogEntry 8 }

nlmLogNotificationID OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The NOTIFICATION-TYPE object identifer of the Notification that
     occurred."
    ::= { nlmLogEntry 9 }

--
-- Log Variable Table
--

nlmLogVariableTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF NlmLogVariableEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "A table of variables to go with Notification log entries."
    ::= { nlmLog 2 }

nlmLogVariableEntry OBJECT-TYPE
    SYNTAX      NlmLogVariableEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION





Expires 12 April 2001                                          [Page 18]





Internet Draft            Notification Log MIB           12 October 2000


     "A Notification log entry variable.

     Entries appear in this table when there are variables in
     the varbind list of a Notification in nlmLogTable."
    INDEX       { nlmLogName, nlmLogIndex, nlmLogVariableIndex }
    ::= { nlmLogVariableTable 1 }

NlmLogVariableEntry ::= SEQUENCE {
    nlmLogVariableIndex              Unsigned32,
    nlmLogVariableID                 OBJECT IDENTIFIER,
    nlmLogVariableValueType          INTEGER,
    nlmLogVariableCounter32Val       Counter32,
    nlmLogVariableUnsigned32Val      Unsigned32,
    nlmLogVariableTimeTicksVal       TimeTicks,
    nlmLogVariableInteger32Val       Integer32,
    nlmLogVariableOctetStringVal     OCTET STRING,
    nlmLogVariableIpAddressVal       IpAddress,
    nlmLogVariableOidVal             OBJECT IDENTIFIER,
    nlmLogVariableCounter64Val       Counter64,
    nlmLogVariableOpaqueVal          Opaque
}

nlmLogVariableIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (1..4294967295)
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
     "A monotonically increasing integer, starting at 1 for a given
     nlmLogIndex, for indexing variables within the logged
     Notification."
    ::= { nlmLogVariableEntry 1 }

nlmLogVariableID OBJECT-TYPE
    SYNTAX     OBJECT IDENTIFIER
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
     "The variable's object identifier."
    ::= { nlmLogVariableEntry 2 }

nlmLogVariableValueType OBJECT-TYPE
    SYNTAX      INTEGER { counter32(1), unsigned32(2), timeTicks(3),
                 integer32(4), ipAddress(5), octetString(6),
                 objectId(7), counter64(8), opaque(9) }
    MAX-ACCESS  read-only





Expires 12 April 2001                                          [Page 19]





Internet Draft            Notification Log MIB           12 October 2000


    STATUS      current
    DESCRIPTION
     "The type of the value.  One and only one of the value
     objects that follow must be instantiated, based on this type."
    ::= { nlmLogVariableEntry 3 }

nlmLogVariableCounter32Val OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'counter32'."
    ::= { nlmLogVariableEntry 4 }

nlmLogVariableUnsigned32Val OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'unsigned32'."
    ::= { nlmLogVariableEntry 5 }

nlmLogVariableTimeTicksVal OBJECT-TYPE
    SYNTAX      TimeTicks
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'timeTicks'."
    ::= { nlmLogVariableEntry 6 }

nlmLogVariableInteger32Val OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'integer32'."
    ::= { nlmLogVariableEntry 7 }

nlmLogVariableOctetStringVal OBJECT-TYPE
    SYNTAX      OCTET STRING
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'octetString'."
    ::= { nlmLogVariableEntry 8 }





Expires 12 April 2001                                          [Page 20]





Internet Draft            Notification Log MIB           12 October 2000


nlmLogVariableIpAddressVal OBJECT-TYPE
    SYNTAX      IpAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'ipAddress'.
     Although this seems to be unfriendly for IPv6, we
     have to recognize that there are a number of older
     MIBs that do contain an IPv4 format address, known
     as IpAddress.

     IPv6 addresses are represented using TAddress or
     InetAddress, and so the underlying datatype is
     OCTET STRING, and their value would be stored in
     the nlmLogVariableOctetStringVal column."
    ::= { nlmLogVariableEntry 9 }

nlmLogVariableOidVal OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'objectId'."
    ::= { nlmLogVariableEntry 10 }

nlmLogVariableCounter64Val OBJECT-TYPE
    SYNTAX      Counter64
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'counter64'."
    ::= { nlmLogVariableEntry 11 }

nlmLogVariableOpaqueVal OBJECT-TYPE
    SYNTAX      Opaque
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The value when nlmLogVariableType is 'opaque'."
    ::= { nlmLogVariableEntry 12 }


--
-- Conformance
--





Expires 12 April 2001                                          [Page 21]





Internet Draft            Notification Log MIB           12 October 2000


notificationLogMIBConformance OBJECT IDENTIFIER ::=
    { notificationLogMIB 3 }
notificationLogMIBCompliances OBJECT IDENTIFIER ::=
    { notificationLogMIBConformance 1 }
notificationLogMIBGroups      OBJECT IDENTIFIER ::=
    { notificationLogMIBConformance 2 }

-- Compliance

notificationLogMIBCompliance MODULE-COMPLIANCE
     STATUS current
     DESCRIPTION
          "The compliance statement for entities which implement
          the Notification Log MIB."
     MODULE    -- this module
          MANDATORY-GROUPS {
               notificationLogConfigGroup,
               notificationLogStatsGroup,
               notificationLogLogGroup
          }

     OBJECT nlmConfigGlobalEntryLimit
         SYNTAX Unsigned32 (0..4294967295)
         MIN-ACCESS read-only
         DESCRIPTION
          "Implementations may choose a limit and not allow it to be
          changed or may enforce an upper or lower bound on the
          limit."

     OBJECT nlmConfigLogEntryLimit
         SYNTAX Unsigned32 (0..4294967295)
         MIN-ACCESS read-only
         DESCRIPTION
          "Implementations may choose a limit and not allow it to be
          changed or may enforce an upper or lower bound on the
          limit."

     OBJECT nlmConfigLogEntryStatus
         MIN-ACCESS read-only
         DESCRIPTION
          "Implementations may disallow the creation of named logs."

     GROUP notificationLogDateGroup
         DESCRIPTION
          "This group is mandatory on systems that keep wall clock





Expires 12 April 2001                                          [Page 22]





Internet Draft            Notification Log MIB           12 October 2000


          date and time and should not be implemented on systems that
          do not have a wall clock date."

     ::= { notificationLogMIBCompliances 1 }

-- Units of Conformance

notificationLogConfigGroup OBJECT-GROUP
     OBJECTS {
          nlmConfigGlobalEntryLimit,
          nlmConfigGlobalAgeOut,
          nlmConfigLogFilterName,
          nlmConfigLogEntryLimit,
          nlmConfigLogAdminStatus,
          nlmConfigLogOperStatus,
          nlmConfigLogStorageType,
          nlmConfigLogEntryStatus
     }
     STATUS current
     DESCRIPTION
          "Notification log configuration management."
     ::= { notificationLogMIBGroups 1 }

notificationLogStatsGroup OBJECT-GROUP
     OBJECTS {
          nlmStatsGlobalNotificationsLogged,
          nlmStatsGlobalNotificationsBumped,
          nlmStatsLogNotificationsLogged,
          nlmStatsLogNotificationsBumped
     }
     STATUS current
     DESCRIPTION
          "Notification log statistics."
     ::= { notificationLogMIBGroups 2 }

notificationLogLogGroup OBJECT-GROUP
     OBJECTS {
          nlmLogTime,
          nlmLogEngineID,
          nlmLogEngineTAddress,
          nlmLogEngineTDomain,
          nlmLogContextEngineID,
          nlmLogContextName,
          nlmLogNotificationID,






Expires 12 April 2001                                          [Page 23]





Internet Draft            Notification Log MIB           12 October 2000


          nlmLogVariableID,
          nlmLogVariableValueType,
          nlmLogVariableCounter32Val,
          nlmLogVariableUnsigned32Val,
          nlmLogVariableTimeTicksVal,
          nlmLogVariableInteger32Val,
          nlmLogVariableOctetStringVal,
          nlmLogVariableIpAddressVal,
          nlmLogVariableOidVal,
          nlmLogVariableCounter64Val,
          nlmLogVariableOpaqueVal
     }
     STATUS current
     DESCRIPTION
          "Notification log data."
     ::= { notificationLogMIBGroups 3 }

notificationLogDateGroup OBJECT-GROUP
     OBJECTS {
          nlmLogDateAndTime
     }
     STATUS current
     DESCRIPTION
          "Conditionally mandatory notification log data.
          This group is mandatory on systems that keep wall
          clock date and time and should not be implemented
          on systems that do not have a wall clock date."
     ::= { notificationLogMIBGroups 4 }

END




















Expires 12 April 2001                                          [Page 24]





Internet Draft            Notification Log MIB           12 October 2000


5.  Intellectual Property

The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights.  Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11.  Copies of claims of
rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general
license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat.

The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard.  Please address the information to the IETF Executive
Director.





























Expires 12 April 2001                                          [Page 25]





Internet Draft            Notification Log MIB           12 October 2000


6.  References

[RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
            for Describing SNMP Management Frameworks", RFC 2571, April
            1999

[RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
            of Management Information for TCP/IP-based Internets", STD
            16, RFC 1155, May 1990

[RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
            16, RFC 1212, March 1991

[RFC1215]   M. Rose, "A Convention for Defining Traps for use with the
            SNMP", RFC 1215, March 1991

[RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Structure of Management
            Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999

[RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Textual Conventions for
            SMIv2", STD 58, RFC 2579, April 1999

[RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Conformance Statements for
            SMIv2", STD 58, RFC 2580, April 1999

[RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
            Network Management Protocol", STD 15, RFC 1157, May 1990.

[RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Introduction to Community-based SNMPv2", RFC 1901, January
            1996.

[RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Transport Mappings for Version 2 of the Simple Network
            Management Protocol (SNMPv2)", RFC 1906, January 1996.

[RFC2572]   Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
            Processing and Dispatching for the Simple Network Management
            Protocol (SNMP)", RFC 2572, April 1999

[RFC2574]   Blumenthal, U., and B. Wijnen, "User-based Security Model
            (USM) for version 3 of the Simple Network Management





Expires 12 April 2001                                          [Page 26]





Internet Draft            Notification Log MIB           12 October 2000


            Protocol (SNMPv3)", RFC 2574, April 1999

[RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Protocol Operations for Version 2 of the Simple Network
            Management Protocol (SNMPv2)", RFC 1905, January 1996.

[RFC2573]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
            RFC 2573, April 1999

[RFC2575]   Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
            Access Control Model (VACM) for the Simple Network
            Management Protocol (SNMP)", RFC 2575, April 1999

[RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart,
            "Introduction to Version 3 of the Internet-standard Network
            Management Framework", RFC 2570, April 1999


































Expires 12 April 2001                                          [Page 27]





Internet Draft            Notification Log MIB           12 October 2000


7.  Security Considerations

Security issues are discussed in Section 3.1.2.


8.  Author's Address

     Bob Stewart
     Cisco Systems, Inc.
     170 West Tasman Drive
     San Jose, CA 95134-1706
     U.S.A.


     Ramanathan Kavasseri
     Cisco Systems, Inc.
     170 West Tasman Drive
     San Jose, CA 95134-1706
     U.S.A.

     Phone: +1 408 527 2446
     Email: ramk@cisco.com




























Expires 12 April 2001                                          [Page 28]





Internet Draft            Notification Log MIB           12 October 2000


9.  Full Copyright Statement

Copyright (C) The Internet Society (2000). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works.  However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the  purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
























Expires 12 April 2001                                          [Page 29]





Internet Draft            Notification Log MIB           12 October 2000


Table of Contents


1 Abstract ........................................................    2
2 The SNMP Management Framework ...................................    2
3 Overview ........................................................    3
3.1 Environment ...................................................    3
3.1.1 SNMP Engines and Contexts ...................................    4
3.1.2 Security ....................................................    4
3.2 Structure .....................................................    5
3.2.1 Configuration ...............................................    6
3.2.2 Statistics ..................................................    6
3.2.3 Log .........................................................    6
3.3 Example .......................................................    6
4 Definitions .....................................................    8
5 Intellectual Property ...........................................   25
6 References ......................................................   26
7 Security Considerations .........................................   28
8 Author's Address ................................................   28
9 Full Copyright Statement ........................................   29






























Expires 12 April 2001                                          [Page 30]



From owner-disman@dorothy.peer.com  Mon Oct 16 07:10:54 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA02100
	for <disman-archive@odin.ietf.org>; Mon, 16 Oct 2000 07:10:53 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9GB2Ao22637;
	Mon, 16 Oct 2000 06:02:10 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id DAA29009
	for disman-list; Mon, 16 Oct 2000 03:34:20 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id DAA29004
	for <disman@dorothy.peer.com>; Mon, 16 Oct 2000 03:34:10 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9GAXlB17513
	for <disman@dorothy.bmc.com>; Mon, 16 Oct 2000 05:33:47 -0500 (CDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01454;
	Mon, 16 Oct 2000 06:34:54 -0400 (EDT)
Message-Id: <200010161034.GAA01454@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@dorothy.peer.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-disman-notif-log-mib-17.txt
Date: Mon, 16 Oct 2000 06:34:54 -0400
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Notification Log MIB
	Author(s)	: R. Kavasseri, B. Stewart
	Filename	: draft-ietf-disman-notif-log-mib-17.txt
	Pages		: 30
	Date		: 13-Oct-00
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for logging SNMP
Notifications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-notif-log-mib-17.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-notif-log-mib-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-disman-notif-log-mib-17.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001013144953.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-notif-log-mib-17.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-notif-log-mib-17.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001013144953.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-disman@dorothy.peer.com  Mon Oct 16 13:48:30 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11837
	for <disman-archive@odin.ietf.org>; Mon, 16 Oct 2000 13:48:29 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9GHeZL27603;
	Mon, 16 Oct 2000 12:40:35 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA00354
	for disman-list; Mon, 16 Oct 2000 10:39:31 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA00348
	for disman@dorothy.bmc.com; Mon, 16 Oct 2000 10:39:27 -0700 (PDT)
Date: Mon, 16 Oct 2000 10:39:27 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010161739.KAA00348@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Fwd: I-D cutoffs
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9GHeZL27603
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA11837


Hi -

nb, fwd fyi.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> From ietf-123-owner@loki.ietf.org Mon Oct 16 09:36:41 PDT 2000
> Message-Id: <200010161542.LAA08162@ietf.org>
> To: IETF-Announce: ;
> Subject: Internet-Draft Cut-off Dates for San Diego IETF
> From: Internet-Drafts Administrator <internet-drafts@ietf.org>
> Date: Mon, 16 Oct 2000 11:42:58 -0400
> 
> 
> NOTE: There are TWO (2) Internet-Draft Cut-off dates
> 
> The IESG has authorized an experiment for the upcoming IETF meeting.
> There will be two Internet-Draft cut-off dates:
> 
> November 17: Cut-off for Initial Submissions (new documents)
> 
> All initial submissions (-00) must be submitted by Friday, November 17,
> 1730 US-EST.  Initial submissions received after this time will not be
> announced nor made available in the internet-drafts directory,  and
> will have to be resubmitted.
> 
> As before, all initial submissions (-00.txt) with a filename beginning
> with a draft-ietf MUST be approved by the appropriate WG Chair prior to
> processing and announcing. WG Chair approval must be received by
> Monday, November 20.
> 
> Do NOT wait until the last minute to submit.
> 
> Be advised: NO placeholders. Updates to initial submissions received
>             the week of November 17 will NOT be accepted.
> 
> 
> November 24: FINAL Internet-Draft Cut-off
> 
> All revised Internet-Draft submissions must be submitted by Friday,
> November 24 2000 at 1700 US-EST. Internet-Drafts received after this
> time will NOT be announced nor made available in the Internet-Drafts
> Directories.
> 
> We will begin accepting Internet-Draft submissions the week of the
> meeting, though announcements will NOT be sent until the IETF meeting
> is over.
> 
> Thank you for your understanding and cooperation. Please do not
> hesitate to contact us if you have any questions or concerns.
> 
> 
> 
> FYI:  These and other significant date can be found at 
>       http://www.ietf.org/meetings/cutoff_dates_49.html
> 
> 


From owner-disman@dorothy.peer.com  Tue Oct 17 06:57:58 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA07371
	for <disman-archive@odin.ietf.org>; Tue, 17 Oct 2000 06:57:57 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9HAsKK23853;
	Tue, 17 Oct 2000 05:54:20 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id DAA08743
	for disman-list; Tue, 17 Oct 2000 03:43:24 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id DAA08738
	for <disman@dorothy.peer.com>; Tue, 17 Oct 2000 03:43:08 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9HAgjl22364
	for <disman@dorothy.bmc.com>; Tue, 17 Oct 2000 05:42:45 -0500 (CDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06848;
	Tue, 17 Oct 2000 06:43:50 -0400 (EDT)
Message-Id: <200010171043.GAA06848@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: disman@dorothy.peer.com
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Notification Log MIB to Proposed Standard
Date: Tue, 17 Oct 2000 06:43:50 -0400
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>




The IESG has approved the Internet-Draft 'Notification Log MIB'
<draft-ietf-disman-notif-log-mib-17.txt> as a Proposed Standard.  This
document is the product of the Distributed Management Working Group.
The IESG contact persons are Bert Wijnen and Randy Bush.

 
Technical Summary
 
  This memo defines a portion of the Management Information Base (MIB)
  fo ruse with network management protocols in the Internet community.
  In particular, it describes managed objects used for logging SNMP
  Notifications.


Working Group Summary

  There is (rough) consensus in the WG that this document is
  ready for publication as Proposed Standard, so that we can
  collect implementation and interoperability experience.


Protocol Quality

  The document was reviewed for the IESG by David Harrington and
  Bert Wijnen.



From owner-disman@dorothy.peer.com  Tue Oct 17 13:16:42 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17159
	for <disman-archive@odin.ietf.org>; Tue, 17 Oct 2000 13:16:37 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9HH9Hq17809;
	Tue, 17 Oct 2000 12:09:21 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09619
	for disman-list; Tue, 17 Oct 2000 10:07:34 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09613
	for disman@dorothy.bmc.com; Tue, 17 Oct 2000 10:07:30 -0700 (PDT)
Date: Tue, 17 Oct 2000 10:07:30 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200010171707.KAA09613@dorothy.bmc.com>
To: disman@dorothy.peer.com
Subject: Re:  Protocol Action: Notification Log MIB to Proposed Standard
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9HH9Hq17809
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA17159


Hi -

> To: IETF-Announce: ;
> Cc: RFC Editor <rfc-editor@isi.edu>
> Cc: Internet Architecture Board <iab@isi.edu>
> Cc: disman@dorothy.bmc.com
> From: The IESG <iesg-secretary@ietf.org>
> Subject: Protocol Action: Notification Log MIB to Proposed Standard
> Date: Tue, 17 Oct 2000 06:43:50 -0400
...
> The IESG has approved the Internet-Draft 'Notification Log MIB'
> <draft-ietf-disman-notif-log-mib-17.txt> as a Proposed Standard.  This
> document is the product of the Distributed Management Working Group.
> The IESG contact persons are Bert Wijnen and Randy Bush.
...

WHEW!

A big THANK YOU to Bob Stewart (the original author), Ram
Kavasseri (the current editor), David Harrington (tireless
reviewer), Bert Wijnen (our AD, who really earned his keep
on this one), and the entire working group!

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------


From owner-disman@dorothy.peer.com  Tue Oct 17 13:35:19 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17468
	for <disman-archive@odin.ietf.org>; Tue, 17 Oct 2000 13:35:18 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e9HHT8H22120;
	Tue, 17 Oct 2000 12:29:08 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09809
	for disman-list; Tue, 17 Oct 2000 10:29:10 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA09804
	for <disman@dorothy.peer.com>; Tue, 17 Oct 2000 10:29:07 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e9HHShk22033
	for <disman@dorothy.peer.com>; Tue, 17 Oct 2000 12:28:43 -0500 (CDT)
Received: from wallace.heidelberg.ccrle.nec.de (root@Wallace.heidelberg.ccrle.nec.de [192.168.102.1])
	by yamato.ccrle.nec.de (8.10.1/8.10.1) with ESMTP id e9HHTrF26290
	for <disman@dorothy.peer.com>; Tue, 17 Oct 2000 19:29:53 +0200 (CEST)
Received: from ccrle.nec.de (belem.heidelberg.ccrle.nec.de [192.168.102.178])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA21714
	for <disman@dorothy.peer.com>; Tue, 17 Oct 2000 19:29:55 +0200
Message-ID: <39EC8C73.C7594A83@ccrle.nec.de>
Date: Tue, 17 Oct 2000 19:29:23 +0200
From: Juergen Quittek <quittek@ccrle.nec.de>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: DISMAN Mailing List <disman@dorothy.peer.com>
Subject: Free Script MIB Implementation
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.peer.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


An open-source implementation of the Script MIB (RFC 2592) and an
AgentX sub-agent toolkit (RFC 2741) are available at the Jasmin home
page http://www.ibr.cs.tu-bs.de/projects/jasmin/ under the GNU General
Public License.

The Jasmin (JAva Script Mib ImplementatioN) project is a collaboration
of the Technical University Braunschweig (http://www.ibr.cs.tu-bs.de/)
and the C&C Research Laboratories of NEC Europe Ltd.
(http://www.ccrle.nec.de/).

The Jasmin software distribtion includes 
  - an implementation of the Script MIB according to RFC 2592
    with a Java runtime engine,
  - a selection of demonstration scripts,
  - a Java package called `scriptmib' supporting the development of
    manager applications for the Script MIB,
  - Smurf, a graphical user interface to the Script MIB,
  - JAX, a Java package for building AgentX sub-agents.

The Script MIB is implemented as a loadable module for the UCD-SNMP
4.2 agent (http://ucd-snmp.ucdavis.edu/). It supports all managed
objects of RFC 2592 except for the code table.

Scripts can be written in Java (JDK 1.1.X). Furter runtime environments
for Perl and Tcl are under development. Runtime environments are linked
by the SMX protocol (RFC2593).

Each demonstration script demonstrates a different feature of the
implementation, such as receiving arguments, returning results, or
sending asynchronous notifications.

The scriptmib Java package provides an API to the Script MIB, that can
be used by management applications. It simplifies many common actions
on the Script MIB. For example, by a single method call, a script is
installed, an argument is passed, the script is started and its result
is returned.

Smurf, the Script Mib User inteRFace, is a graphical interface for
browsing and editing managed objects of the Script MIB. It can
establish connections to several runnning Script MIB implementations.

The JAX package consists of a Java class library for scripts which
allows them to dynamically extend the SNMP agent by new MIB objects
using the AgentX protocol (RFC 2741). The MIB implementing code can be
built based on the output of a libsmi-based JAX MIB compiler. The JAX
package is useful for distributed management script as well as other
agent extension environments.

Further documentation of the Jasmin software distribution and several
related documents are available at the Jasmin home page.

    Juergen
-- 
Juergen Quittek     quittek@ccrle.nec.de     Tel: +49 6221 90511-15
NEC Europe Ltd., C&C Research Laboratories   Fax: +49 6221 90511-55
Adenauerplatz 6, 69115 Heidelberg, Germany   http://www.ccrle.nec.de


From owner-disman@dorothy.bmc.com  Tue Oct 24 13:11:59 2000
Received: from tattler.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00866
	for <disman-archive@odin.ietf.org>; Tue, 24 Oct 2000 13:11:56 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id e9OGvRq19091;
	Tue, 24 Oct 2000 11:57:31 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA00993
	for disman-list; Tue, 24 Oct 2000 09:55:02 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA00988
	for <disman@dorothy.peer.com>; Tue, 24 Oct 2000 09:54:31 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with SMTP id e9OGs0X18206
	for <disman@dorothy.peer.com>; Tue, 24 Oct 2000 11:54:00 -0500 (CDT)
Received: from zrtpd004.us.nortel.com by zrtps06s.us.nortel.com;
          Mon, 23 Oct 2000 08:10:07 -0400
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2652.35) 
          id <44WR1VFD>; Mon, 23 Oct 2000 08:10:06 -0400
Message-ID: <6DDA62170439D31185750000F80826AC041EDA9D@zmerd004.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: internet-drafts@ietf.org
Cc: disman@dorothy.bmc.com
Subject: draft-chisholm-disman-active-alarm-01.txt
Date: Mon, 23 Oct 2000 08:10:01 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C03CEA.2B9F5510"
X-Orig: <schishol@americasm01.nt.com>
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C03CEA.2B9F5510
Content-Type: text/plain;
	charset="iso-8859-1"

hi

Please accept draft-chisholm-disman-active-alarm-01.txt for
posting as an internet-draft.

This update contains alarm content in addition to the Active
Alarm list after feedback from Pittsburgh and the disman mailing
list.  Many thanks to Dan Romascanu for his review of a draft
version of this draft.

thanks,

Sharon


INTERNET-DRAFT                                          S. Chisholm
                                                        Nortel Networks
                                                        October 22 2000

                                Alarm MIB

Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other groups
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress."


The list of current Internet-Drafts can be accessed at

http://www.ietf.org/ietf/1id-abstracts.txt


The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.


1. Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes management objects used for maintaining
   a list of alarms currently active on a network element.

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

    o   An overall architecture, described in RFC 2571 [RFC2571].

    o   Mechanisms for describing and naming objects and events for the
        purpose of management.  The first version of this Structure of
        Management Information (SMI) is called SMIv1 and described in
        STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC



Expires 22 April 2001                                           [Page 1]





Internet Draft                 Alarm MIB                22 October 2000


        1215 [RFC1215].  The second version, called SMIv2, is described
        in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
        STD 58, RFC 2580 [RFC2580].

    o   Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, RFC 1157 [RFC1157].  A second version of
        the SNMP message protocol, which is not an Internet standards
        track protocol, is called SNMPv2c and described in RFC 1901
        [RFC1901] and RFC 1906 [RFC1906].  The third version of the
        message protocol is called SNMPv3 and described in RFC 1906
        [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].

    o   Protocol operations for accessing management information.  The
        first set of protocol operations and associated PDU formats is
        described in STD 15, RFC 1157 [RFC1157].  A second set of
        protocol operations and associated PDU formats is described in
        RFC 1905 [RFC1905].

    o   A set of fundamental applications described in RFC 2573
        [RFC2573] and the view-based access control mechanism described
        in RFC 2575 [RFC2575].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations.  The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64).  Some machine readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process.  However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.


3. Introduction

   An alarm is an error condition occurring on a system that needs
   to be fixed, either automatically or through manual intervention.

   The alarm details table contains information which is applicable
   to all instances of an alarm.  It is populated at start-up with



Expires 22 April 2001                                           [Page 2]





Internet Draft                 Alarm MIB                22 October 2000


   all alarms that could happen on a system.  The information in this
   table should be fairly static during system operation.

   The active alarm table contains a list of alarms which are currently
   occurring on a system. It is intended that this table be queried
   upon device discovery and rediscovery to determine which alarms are
   currently active on the device. This allows the network management
   station to find out about any problems that may have occurred before
   it started managing a particular network element, or while it was out
   of contact with it.

   Each alarm should have a corresponding clear which removes it from
   the active alarm table. Alternatively it could be aged out.  The
   configuring and querying of alarm age-outs is not covered in this
   document.


4. Relation to Notification Log MIB

   This MIB is intended to compliment the notification log MIB, but
   can be used independently.  The active alarm table is defined in
   manner similar to that of the notification log table.  This format
   allows for the storage of any NOTIFICATION that can be defined using
   SMI.  Using the same format as the notification log MIB also
   simplifies operations for systems choosing to implement both MIBs.


5. Alarm Raise and Clear

   The alarm details table provides a means of defining the raise/clear
   relationship between alarms. The alarmDetailsPerceivedSeverity object
   indicates whether this is a raise alarm or a clear alarm. The
   alarmDetailsNotificationId gives the OID of this particular alarm. If
   this is a raise alarm, the alarmDetailsClearNotificationId object
   gives the OID of corresponding clear alarm.  If this is a clear
   alarm, the alarmDetailsClearNotificationId object gives the OID of
   one of the corresponding raise alarms for this clear.


6. ITU-T X.733, X.736 Trap Content

   Selected information from ITU-T X.733, X.736 alarm documents has been
   included in the alarmDetailsTable and the alarmActiveTable, depending
   on the variability of this information.  Support of these objects is
   not necessary to support the alarm raise/clear and active alarm
   components of this MIB.





Expires 22 April 2001                                           [Page 3]





Internet Draft                 Alarm MIB                22 October 2000


7. Definitions

ALARM-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE,
    experimental, Integer32, Unsigned32,
    TimeTicks, Counter32, Counter64,
    IpAddress, Opaque, mib-2            FROM SNMPv2-SMI
    TimeStamp, DateAndTime, DisplayString,
    StorageType, RowStatus              FROM SNMPv2-TC
    SnmpAdminString, SnmpEngineID       FROM SNMP-FRAMEWORK-MIB
    MODULE-COMPLIANCE, OBJECT-GROUP     FROM SNMPv2-CONF;

   alarm MODULE-IDENTITY
       LAST-UPDATED "000010220000Z"
       ORGANIZATION "Alarm MIB"
       CONTACT-INFO
               "   Sharon Chisholm
                   Nortel Networks
                   PO Box 3511 Station C
                   Ottawa, Ont.  K1Y 4H7
                   Canada

                   schishol@nortelnetworks.com"
       DESCRIPTION
               "The MIB module describes a generic solution
               to improve the reliability of SNMP traps by storing alarm
               details and the current list of active alarms."
       ::= { mib-2 xx }

alarmObjects OBJECT IDENTIFIER ::= { alarm 1 }


alarmDetailsTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF AlarmDetailsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of information about possible alarms on the system."
    ::= { alarmObjects 1 }

alarmDetailsEntry OBJECT-TYPE
    SYNTAX      AlarmDetailsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Entries appear in this table for each possible alarm."



Expires 22 April 2001                                           [Page 4]





Internet Draft                 Alarm MIB                22 October 2000


    INDEX       { alarmListName, alarmDetailsIndex }
    ::= { alarmDetailsTable 1 }

AlarmDetailsEntry ::= SEQUENCE {
    alarmDetailsIndex                 Unsigned32,
    alarmDetailsNotificationId        OBJECT IDENTIFIER,
    alarmDetailsClearNotificationId   OBJECT IDENTIFIER,
    alarmDetailsEventType             INTEGER,
    alarmDetailsProbableCause         INTEGER,
    alarmDetailsPerceivedSeverity     INTEGER,
    alarmDetailsAdditionalText        DisplayString }


alarmDetailsIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (1..4294967295)
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
        "A integer which acts as the
        index of entries within the named alarm list. "
    ::= { alarmDetailsEntry 1 }

alarmDetailsNotificationId OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The NOTIFICATION-TYPE object identifier of this alarm."
    ::= { alarmDetailsEntry 2 }

alarmDetailsClearNotificationId OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The NOTIFICATION-TYPE object identifier of the alarm which
         clears this alarm. If this entry corresponds to a clear
         alarm, then this object should be one of the notifications
         which sets this alarm condition"
    ::= { alarmDetailsEntry 3 }

alarmDetailsEventType OBJECT-TYPE
    SYNTAX              INTEGER
            {
            other (1),
            communityAlarmType (2),
            qualityOfServerAlarmType (3),
            processingErrorAlarmType (4),



Expires 22 April 2001                                           [Page 5]





Internet Draft                 Alarm MIB                22 October 2000


            equipmentAlarmType (5),
            environmentalAlarmType (6)                         }
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
             " Represents the event type values for the alarms as per
               (ITU-T X.733)."
     ::= { alarmDetailsEntry 4 }

alarmDetailsProbableCause OBJECT-TYPE
      SYNTAX         INTEGER
                       {
                        other (1),
                        adapterError (2),
                        applicationSubsystemFailure (3),
                        bandwidthReduced (4),
                        callEstablishmentError (5),
                        communicationsProtocolError (6),
                        communicationsSubsystemFailure (7),
                        configurationOrCustomizationError (8),
                        congestion (9),
                        corruptData (10),
                        cpuCyclesLimitExceeded (11),
                        dataSetOrModemError (12),
                        degradedSignal (13),
                        dteDceInterfaceError (14),
                        enclosureDoorOpen (15),
                        equipmentMalfunction (16),
                        excessiveVibration (17),
                        fileError (18),
                        fireDetected (19),
                        floodDetected (20),
                        framingError (21),
                        heatingOrVentilationOrCoolingSystemProblem (22),
                        humidityUnacceptable (23),
                        inputOutputDeviceError (24),
                        inputDeviceError (25),
                        lanError (26),
                        leakDetected (27),
                        localNodeTransmissionError (28),
                        lossOfFrame (29),
                        lossOfSignal (30),
                        materialSupplyExhausted (31),
                        multiplexerProblem (32),
                        outOfMemory (33),
                        ouputDeviceError (34),
                        performanceDegraded (35),
                        powerProblem (36),



Expires 22 April 2001                                           [Page 6]





Internet Draft                 Alarm MIB                22 October 2000


                        pressureUnacceptable (37),
                        processorProblem (38),
                        pumpFailure (39),
                        queueSizeExceeded (40),
                        receiveFailure (41),
                        receiverFailure (42),
                        remoteNodeTransmissionError (43),
                        resourceAtOrNearingCapacity (44),
                        responseTimeExecessive (45),
                        retransmissionRateExcessive (46),
                        softwareError (47),
                        softwareProgramAbnormallyTerminated (48),
                        softwareProgramError (49),
                        storageCapacityProblem (50),
                        temperatureUnacceptable (51),
                        thresholdCrossed (52),
                        timingProblem (53),
                        toxicLeakDetected (54),
                        transmitFailure (55),
                        transmitterFailure (56),
                        underlyingResourceUnavailable (57),
                        versionMismatch (58),
                        authenticationFailure (59),
                        breachOfConfidentiality (60),
                        cableTamper (61),
                        delayedInformation (62),
                        denialOfService (63),
                        duplicateInformation (64),
                        informationMissing (65),
                        informationModificationDetected (66),
                        informationOutOfSequence (67),
                        intrusionDetection (68),
                        keyExpired (69),
                        nonRepudiationFailure (70),
                        outOfHoursActivity (71),
                        outOfService (72),
                        proceduralError (73),
                        unauthorizedAccessAttempt (74),
                        unexpectedInformation (75)
                       }
    MAX-ACCESS  read-only
    STATUS       current

     DESCRIPTION
             " Represents the probable cause values for the alarms as
             per (ITU-T X.733, X.736)."
     ::= { alarmDetailsEntry 5 }




Expires 22 April 2001                                           [Page 7]





Internet Draft                 Alarm MIB                22 October 2000


alarmDetailsPerceivedSeverity OBJECT-TYPE
        SYNTAX          INTEGER                         {
            cleared (1),
            indeterminate (2),
            critical (3),
            major (4),
            minor (5),
            warning (6)                         }
    MAX-ACCESS  read-only
    STATUS       current
    DESCRIPTION
             " Represents the perceived severity values for the alarms
              as per (ITU-T X.733)."
     ::= { alarmDetailsEntry 6 }

alarmDetailsAdditionalText OBJECT-TYPE
        SYNTAX DisplayString
        MAX-ACCESS read-only
        STATUS     current
        DESCRIPTION
             " Represents the additional text field for the alarm as per
               (ITU-T X.733)."
         ::= { alarmDetailsEntry 7}

-- -- Active Alarm Table --


alarmActiveTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF AlarmActiveEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of Active Alarms entries."
    ::= { alarmObjects 2 }

alarmActiveEntry OBJECT-TYPE
    SYNTAX      AlarmActiveEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Entries appear in this table when alarms are active.  They are
        removed when the alarm is no longer occurring."
    INDEX       { alarmListName, alarmActiveIndex }
    ::= { alarmActiveTable 1 }

AlarmActiveEntry ::= SEQUENCE {
    alarmListName                    SnmpAdminString,
    alarmActiveIndex                 Unsigned32,



Expires 22 April 2001                                           [Page 8]





Internet Draft                 Alarm MIB                22 October 2000


    alarmActiveTime                  TimeStamp,
    alarmActiveDateAndTime           DateAndTime,
    alarmActiveEngineID              SnmpEngineID,
    alarmActiveEngineAddress         IpAddress,
    alarmActiveContextEngineID       SnmpEngineID,
    alarmActiveContextName           SnmpAdminString,
    alarmActiveVariables             Unsigned32,
    alarmActiveNotificationID        OBJECT IDENTIFIER,
    alarmActiveTrendIndication       INTEGER,
    alarmActiveLogIndex              Unsigned32,
    alarmActiveDetailsIndex          Unsigned32 }

alarmListName OBJECT-TYPE
    SYNTAX     SnmpAdminString (SIZE(0..32))
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
     "The name of the list of alarms.  This is the same as
     nlmLogName if the Nofication Log MIB is supported.

     An implementation may allow multiple named alarm lists, up to
     some implementation-specific limit (which may be none).  A
     zero-length list name is reserved for creation and deletion
     by the managed system, and MUST be used as the default log
     name by systems that do not support named alarm lists."
    ::= { alarmActiveEntry 1 }

alarmActiveIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (1..4294967295)
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
        "A monotonically increasing integer which acts as the
        index of entries within the named alarm list.  It wraps
        back to 1 after it reaches its maximum value."
    ::= { alarmActiveEntry 2 }

alarmActiveTime OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of sysUpTime when the alarm occurred. Alarms tend
        to get cleared and resent if still applicable at reboot, so this
        value tends to be is a valid sysUptime. In the case where the
        alarms are not cleared at reboot, and the alarm occurred before
        the most recent management system initialization, this object
        value MUST be set to zero."



Expires 22 April 2001                                           [Page 9]





Internet Draft                 Alarm MIB                22 October 2000


    ::= { alarmActiveEntry 3 }

alarmActiveDateAndTime OBJECT-TYPE
    SYNTAX      DateAndTime
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The local date and time when the alarm occurred, instantiated
        only by systems that have date and time capability."
    ::= { alarmActiveEntry 4 }

alarmActiveEngineID OBJECT-TYPE
    SYNTAX      SnmpEngineID
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The identification of the SNMP engine at which the alarm
        originated.
        If the alarm list can contain Notifications from only one
        engine or the Trap is from an SNMPv1 system, this object is not
        instantiated."
    ::= { alarmActiveEntry 5 }

alarmActiveEngineAddress OBJECT-TYPE
    SYNTAX      IpAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The IP Address of the SNMP engine on which the alarm is
     occurring. This is used to identify the source of an SNMPv1
     trap, since an alarmActiveEngineId cannot be extracted from the
     SNMPv1 trap pdu.

     This object MUST always be instantiated, even if the list
     can contain alarms from only one engine."
    ::= { alarmActiveEntry 6 }

alarmActiveContextEngineID OBJECT-TYPE
    SYNTAX      SnmpEngineID
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "If the alarm is occurring on a device using a protocol which
     has a contextEngineID element like SNMPv3, this object has that
     value. Otherwise its value is a zero-length string."
    ::= { alarmActiveEntry 7 }





Expires 22 April 2001                                          [Page 10]





Internet Draft                 Alarm MIB                22 October 2000


alarmActiveContextName OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The name of the SNMP MIB context from which the alarm came.
        For SNMPv1 Traps this is the community string from the Trap.
        If the alarm's source SNMP engine is known not to support
        multiple contexts, this object is not instantiated."
    ::= { alarmActiveEntry 8 }

alarmActiveVariables OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of variables in alarmActiveVariableTable for this
        Notification."
    ::= { alarmActiveEntry 9 }


alarmActiveNotificationID OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The NOTIFICATION-TYPE object identifier of the Notification
        that occurred."
    ::= { alarmActiveEntry 10 }


alarmActiveTrendIndication OBJECT-TYPE
    SYNTAX              INTEGER
       {
       moreSevere (1),
       noChange (2),
       lessSevere (3)
       }
    MAX-ACCESS  read-only
    STATUS       current
    DESCRIPTION
             " Represents the trend indication values for the alarms
             as per (ITU-T X.733)."
     ::= { alarmActiveEntry 11 }

alarmActiveLogIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (0..4294967295)
    MAX-ACCESS read-only



Expires 22 April 2001                                          [Page 11]





Internet Draft                 Alarm MIB                22 October 2000


    STATUS     current
    DESCRIPTION
        "This number can be considered a sequence number for the trap.
        It should be the same as the log index in the notification log
        MIB, if used.  If no log index or sequence number applies to the
        trap, then this object should have the value of 0."
    ::= { alarmActiveEntry 12 }

alarmActiveDetailsIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (0..4294967295)
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
        "The index of the corresponding row in the alarmDetails table.
        If the alarmDetails table is not supported this object should
        have a value of 0."
    ::= { alarmActiveEntry 13 }

-- -- Active Alarm Variable Table --

alarmActiveVariableTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF AlarmActiveVariableEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of variables to go with active alarm entries."
    ::= { alarmObjects 3 }

alarmActiveVariableEntry OBJECT-TYPE
    SYNTAX      AlarmActiveVariableEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Entries appear in this table when there are variables in
        the varbind list of a corresponding alarm in alarmActiveTable."
    INDEX   {  alarmListName, alarmActiveIndex, alarmActiveVariableIndex
}
    ::= { alarmActiveVariableTable 1 }

AlarmActiveVariableEntry ::= SEQUENCE {
    alarmActiveVariableIndex                 Unsigned32,
    alarmActiveVariableID                    OBJECT IDENTIFIER,
    alarmActiveVariableValueType             INTEGER,
    alarmActiveVariableCounter32Val          Counter32,
    alarmActiveVariableUnsigned32Val         Unsigned32,
    alarmActiveVariableTimeTicksVal          TimeTicks,
    alarmActiveVariableInteger32Val          Integer32,
    alarmActiveVariableOctetStringVal        OCTET STRING,



Expires 22 April 2001                                          [Page 12]





Internet Draft                 Alarm MIB                22 October 2000


    alarmActiveVariableIpAddressVal          IpAddress,
    alarmActiveVariableOidVal                OBJECT IDENTIFIER,
    alarmActiveVariableCounter64Val          Counter64,
    alarmActiveVariableOpaqueVal             Opaque }

alarmActiveVariableIndex OBJECT-TYPE
    SYNTAX     Unsigned32 (1..4294967295)
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
        "A monotonically increasing integer, starting at 1 for a given
        alarmActiveIndex, for indexing variables within the active
        alarm list."
    ::= { alarmActiveVariableEntry 1 }

alarmActiveVariableID OBJECT-TYPE
    SYNTAX     OBJECT IDENTIFIER
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
        "The variable's object identifier."
    ::= { alarmActiveVariableEntry 2 }

alarmActiveVariableValueType OBJECT-TYPE
    SYNTAX      INTEGER { counter32(1), unsigned32(2), timeTicks(3),
                          integer32(4), ipAddress(5), octetString(6),
                          objectId(7), counter64(8), opaque(9) }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The type of the value.  One and only one of the value
        objects that follow is used, based on this type."
    ::= { alarmActiveVariableEntry 3 }

alarmActiveVariableCounter32Val OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'counter32'."
    ::= { alarmActiveVariableEntry 4 }

alarmActiveVariableUnsigned32Val OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'unsigned32'."



Expires 22 April 2001                                          [Page 13]





Internet Draft                 Alarm MIB                22 October 2000


    ::= { alarmActiveVariableEntry 5 }

alarmActiveVariableTimeTicksVal OBJECT-TYPE
    SYNTAX      TimeTicks
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'timeTicks'."
    ::= { alarmActiveVariableEntry 6 }

alarmActiveVariableInteger32Val OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'integer32'."
    ::= { alarmActiveVariableEntry 7 }

alarmActiveVariableOctetStringVal OBJECT-TYPE
    SYNTAX      OCTET STRING
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'octetString'."
    ::= { alarmActiveVariableEntry 8 }

alarmActiveVariableIpAddressVal OBJECT-TYPE
    SYNTAX      IpAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'ipAddress'."
    ::= { alarmActiveVariableEntry 9 }

alarmActiveVariableOidVal OBJECT-TYPE
    SYNTAX      OBJECT IDENTIFIER
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'objectId'."
    ::= { alarmActiveVariableEntry 10 }

alarmActiveVariableCounter64Val OBJECT-TYPE
    SYNTAX      Counter64
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'counter64'."



Expires 22 April 2001                                          [Page 14]





Internet Draft                 Alarm MIB                22 October 2000


    ::= { alarmActiveVariableEntry 11 }

alarmActiveVariableOpaqueVal OBJECT-TYPE
    SYNTAX      Opaque
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value when alarmActiveVariableType is 'opaque'."
    ::= { alarmActiveVariableEntry 12 }

-- -- Statistics --

alarmActiveStatsTable  OBJECT-TYPE
       SYNTAX  SEQUENCE OF AlarmActiveStatsEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "This table represents the alarm statistics type
          information."
        ::= { alarmObjects 4 }


   alarmActiveStatsEntry OBJECT-TYPE
       SYNTAX  AlarmActiveStatsEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "Statistics on the current active alarms."

       INDEX   { alarmListName }

        ::= {  alarmActiveStatsTable 1 }



   AlarmActiveStatsEntry ::=
       SEQUENCE {
            alarmActiveStatsTotalActive    Unsigned32
                 }


  alarmActiveStatsTotalActive OBJECT-TYPE
       SYNTAX Unsigned32
       MAX-ACCESS read-only
       STATUS  current
       DESCRIPTION
          "The total number of currently active alarms on the system."




Expires 22 April 2001                                          [Page 15]





Internet Draft                 Alarm MIB                22 October 2000


        ::= { alarmActiveStatsEntry 1 }



     -- Conformance Stuff

     alarmConformance OBJECT IDENTIFIER ::= { alarm 2 }

     alarmDetailsGroup OBJECT-GROUP
          OBJECTS {
            alarmDetailsIndex,
                alarmDetailsNotificationId,
                alarmDetailsClearNotificationId,
                alarmDetailsEventType,
                alarmDetailsProbableCause,
                alarmDetailsPerceivedSeverity,
                alarmDetailsAdditionalText
          }
        STATUS   current
        DESCRIPTION
                "Alarm details list group."
           ::= { alarmConformance 2}


         alarmActiveListGroup OBJECT-GROUP                   OBJECTS {
                    alarmListName,
                alarmActiveIndex,
                alarmActiveTime,
                alarmActiveDateAndTime,
                alarmActiveEngineID,
                alarmActiveEngineAddress,
                alarmActiveContextEngineID,
                alarmActiveContextName,
                alarmActiveVariables,
                alarmActiveNotificationID,
                alarmActiveLogIndex,
                alarmActiveVariableIndex,
                alarmActiveVariableID,
                alarmActiveVariableValueType,
                alarmActiveVariableCounter32Val,
                alarmActiveVariableUnsigned32Val,
                alarmActiveVariableTimeTicksVal,
                alarmActiveVariableInteger32Val,
                alarmActiveVariableOctetStringVal,
                alarmActiveVariableIpAddressVal,
                alarmActiveVariableOidVal,
                alarmActiveVariableCounter64Val,
                alarmActiveVariableOpaqueVal



Expires 22 April 2001                                          [Page 16]





Internet Draft                 Alarm MIB                22 October 2000


                }                    STATUS   current
           DESCRIPTION
                "Active Alarm list group."
           ::= { alarmConformance 3}

     alarmActiveSummaryGroup  OBJECT-GROUP
           OBJECTS  {
                    alarmActiveStatsTotalActive
                     }
           STATUS   current
           DESCRIPTION
                " Active alarm summary group."
           ::= { alarmConformance 4}


alarmCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
           "The compliance statement for systems supporting
           the Alarm MIB."
       MODULE -- this module
           MANDATORY-GROUPS {
            alarmActiveListGroup
           }
           GROUP alarmActiveSummaryGroup
           DESCRIPTION
           "The actual active alarms."

        ::= { alarmConformance 1 }          END


8. Example

        Define the following Object:
          acmeWidgetIndex OBJECT-TYPE
            SYNTAX  Integer32
            MAX-ACCESS read-only
            STATUS   current
            DESCRIPTION
              "A unique number which identifies a particular Widget."
          ::= { acmeWidgetEntry 1 }

        Define the following three traps:
          acmeWidgetTemperatureCritical NOTIFICATION-TYPE
            OBJECTS { acmeWidgetIndex }
            STATUS      current
            DESCRIPTION
              "This trap indicates that the indicated



Expires 22 April 2001                                          [Page 17]





Internet Draft                 Alarm MIB                22 October 2000


                widget has reached a critical temperature."
          ::= { acmeWidgetTraps 1 }

          acmeWidgetTemperatureNormal NOTIFICATION-TYPE
            OBJECTS { acmeWidgetIndex }
            STATUS      current
            DESCRIPTION
              "This trap indicates that the indicated widget has
                reached a normal temperature."
          ::= { acmeWidgetTraps 2 }

          bgpBackwardTransition NOTIFICATION-TYPE
            OBJECTS { bgpPeerLastError,
                      bgpPeerState      }
            STATUS  current
            DESCRIPTION
               "The BGPBackwardTransition Event is generated
               when the BGP FSM moves from a higher numbered
               state to a lower numbered state."
           ::= { bgpTraps 2 }

        0. Active alarm table empty and nothing in notification log
                 ___________________________      _____________________
                | alarmActiveTable          |    | nlmLogTable         |
                |---------------------------|    |---------------------|
                | alarmActiveIndex |  alarm |    | nlmLogIndex | alarm |
                |---------------------------|    |---------------------|
                |___________________________|    |_____________________|

        1. Temperature of widget 2 goes critical
                 __________________________________________________
                | alarmActiveTable                                 |
                |--------------------------------------------------|
                | alarmActiveIndex |  alarm                        |
                |--------------------------------------------------|
                |        1         | acmeWidgetTemperatureCritical |
                |__________________________________________________|

                 _____________________________________________
                | nlmLogTable                                 |
                |---------------------------------------------|
                | nlmLogIndex |  alarm                        |
                |---------------------------------------------|
                |      1      | acmeWidgetTemperatureCritical |
                |_____________________________________________|


        2. BGP peering session transitions from a state of established



Expires 22 April 2001                                          [Page 18]





Internet Draft                 Alarm MIB                22 October 2000


           to opensent
                 __________________________________________________
                | alarmActiveTable                                 |
                |--------------------------------------------------|
                | alarmActiveIndex |  alarm                        |
                |--------------------------------------------------|
                |        1         | acmeWidgetTemperatureCritical |
                |        2         | bgpBackwardTransition         |
                |__________________________________________________|

                 _____________________________________________
                | nlmLogTable                                 |
                |---------------------------------------------|
                | nlmLogIndex |  alarm                        |
                |---------------------------------------------|
                |      1      | acmeWidgetTemperatureCritical |
                |      2      | bgpBackwardTransition         |
                |_____________________________________________|


        3. Temperature of widget 2 goes back to normal
                 __________________________________________________
                | alarmActiveTable                                 |
                |--------------------------------------------------|
                | alarmActiveIndex |  alarm                        |
                |--------------------------------------------------|
                |        2         | bgpBackwardTransition         |
                |__________________________________________________|

                 _____________________________________________
                | nlmLogTable                                 |
                |---------------------------------------------|
                | nlmLogIndex |  alarm                        |
                |---------------------------------------------|
                |      1      | acmeWidgetTemperatureCritical |
                |      2      | bgpBackwardTransition         |
                |      3      | acmeWidgetTemperatureNormal   |
                |_____________________________________________|


        4. Time passes .... BGP alarm ages out.

                 __________________________________________________
                | alarmActiveTable                                 |
                |--------------------------------------------------|
                | alarmActiveIndex |  alarm                        |
                |--------------------------------------------------|
                |__________________________________________________|



Expires 22 April 2001                                          [Page 19]





Internet Draft                 Alarm MIB                22 October 2000


                 _____________________________________________
                | nlmLogTable                                 |
                |---------------------------------------------|
                | nlmLogIndex |  alarm                        |
                |---------------------------------------------|
                |      1      | acmeWidgetTemperatureCritical |
                |      2      | bgpBackwardTransition         |
                |      3      | acmeWidgetTemperatureNormal   |
                |_____________________________________________|

9. Security Considerations


   There are no management objects defined in this MIB that have a MAX-
   ACCESS clause of read-write and/or read-create.  So, if this MIB is
   implemented correctly, then there is no risk that an intruder can
   alter or create any management objects of this MIB via direct SNMP
   SET operations.

10. Author's Address

   Sharon Chisholm
   Nortel Networks
   PO Box 3511, Station C
   Ottawa, Ontario, K1Y 4H7
   Canada

   Email: schishol@nortelnetworks.com

11. References
        [1] Stewart, B,  Kavasseri, R, "Notification Log MIB,
            draft 17, October 2000
        [2] ITU Recommendation X.733, "Information Technology - Open
            Systems Interconnection - System Management: Alarm Reporting
            Function", 1992
        [3] ITU Recommendation X.736, "Information Technology - Open
            Systems Interconnection - System Management: Security Alarm
            Reporting Function", 1992

12. Full Copyright Statement

Copyright (C) The Internet Society (2000). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included



Expires 22 April 2001                                          [Page 20]





Internet Draft                 Alarm MIB                22 October 2000


on all such copies and derivative works.  However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the  purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.


































Expires 22 April 2001                                          [Page 21]



------_=_NextPart_001_01C03CEA.2B9F5510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>draft-chisholm-disman-active-alarm-01.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi</FONT>
</P>

<P><FONT SIZE=3D2>Please accept =
draft-chisholm-disman-active-alarm-01.txt for</FONT>
<BR><FONT SIZE=3D2>posting as an internet-draft.</FONT>
</P>

<P><FONT SIZE=3D2>This update contains alarm content in addition to the =
Active</FONT>
<BR><FONT SIZE=3D2>Alarm list after feedback from Pittsburgh and the =
disman mailing</FONT>
<BR><FONT SIZE=3D2>list.&nbsp; Many thanks to Dan Romascanu for his =
review of a draft</FONT>
<BR><FONT SIZE=3D2>version of this draft.</FONT>
</P>

<P><FONT SIZE=3D2>thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Sharon</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>INTERNET-DRAFT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S. =
Chisholm</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Nortel =
Networks</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; October 22 =
2000</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm MIB</FONT>
</P>

<P><FONT SIZE=3D2>Status of this Memo</FONT>
</P>

<P><FONT SIZE=3D2>This document is an Internet-Draft and is in full =
conformance with all</FONT>
<BR><FONT SIZE=3D2>provisions of Section 10 of RFC2026.</FONT>
</P>

<P><FONT SIZE=3D2>Internet-Drafts are working documents of the Internet =
Engineering Task</FONT>
<BR><FONT SIZE=3D2>Force (IETF), its areas, and its working =
groups.&nbsp; Note that other groups</FONT>
<BR><FONT SIZE=3D2>may also distribute working documents as =
Internet-Drafts.</FONT>
</P>

<P><FONT SIZE=3D2>Internet-Drafts are draft documents valid for a =
maximum of six months</FONT>
<BR><FONT SIZE=3D2>and may be updated, replaced, or obsoleted by other =
documents at any</FONT>
<BR><FONT SIZE=3D2>time.&nbsp; It is inappropriate to use Internet- =
Drafts as reference material</FONT>
<BR><FONT SIZE=3D2>or to cite them other than as &quot;work in =
progress.&quot;</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The list of current Internet-Drafts can be accessed =
at</FONT>
</P>

<P><FONT SIZE=3D2><A =
HREF=3D"http://www.ietf.org/ietf/1id-abstracts.txt" =
TARGET=3D"_blank">http://www.ietf.org/ietf/1id-abstracts.txt</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The list of Internet-Draft Shadow Directories can be =
accessed at</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A>.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>1. Abstract</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; This memo defines a portion of the =
Management Information Base (MIB)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; for use with network management =
protocols in the Internet community.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; In particular, it describes management =
objects used for maintaining</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; a list of alarms currently active on a =
network element.</FONT>
</P>

<P><FONT SIZE=3D2>2.&nbsp; The SNMP Management Framework</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; The SNMP Management Framework presently =
consists of five major</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; components:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp; An overall =
architecture, described in RFC 2571 [RFC2571].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp; Mechanisms for =
describing and naming objects and events for the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; purpose =
of management.&nbsp; The first version of this Structure of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Management Information (SMI) is called SMIv1 and described in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STD 16, =
RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 1]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1215 =
[RFC1215].&nbsp; The second version, called SMIv2, is described</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in STD =
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STD 58, =
RFC 2580 [RFC2580].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp; Message protocols =
for transferring management information.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first =
version of the SNMP message protocol is called SNMPv1 and</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; described =
in STD 15, RFC 1157 [RFC1157].&nbsp; A second version of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the SNMP =
message protocol, which is not an Internet standards</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; track =
protocol, is called SNMPv2c and described in RFC 1901</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC1901] =
and RFC 1906 [RFC1906].&nbsp; The third version of the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message =
protocol is called SNMPv3 and described in RFC 1906</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp; Protocol operations =
for accessing management information.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first set =
of protocol operations and associated PDU formats is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; described =
in STD 15, RFC 1157 [RFC1157].&nbsp; A second set of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protocol =
operations and associated PDU formats is described in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RFC 1905 =
[RFC1905].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp; A set of fundamental =
applications described in RFC 2573</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC2573] =
and the view-based access control mechanism described</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in RFC =
2575 [RFC2575].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; A more detailed introduction to the =
current SNMP Management Framework</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; can be found in RFC 2570 =
[RFC2570].</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Managed objects are accessed via a =
virtual information store, termed</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; the Management Information Base or =
MIB.&nbsp; Objects in the MIB are</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; defined using the mechanisms defined in =
the SMI.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; This memo specifies a MIB module that is =
compliant to the SMIv2.&nbsp; A</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; MIB conforming to the SMIv1 can be =
produced through the appropriate</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; translations.&nbsp; The resulting =
translated MIB must be semantically</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; equivalent, except where objects or =
events are omitted because no</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; translation is possible (use of =
Counter64).&nbsp; Some machine readable</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; information in SMIv2 will be converted =
into textual descriptions in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; SMIv1 during the translation =
process.&nbsp; However, this loss of machine</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; readable information is not considered =
to change the semantics of the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; MIB.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>3. Introduction</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; An alarm is an error condition occurring =
on a system that needs</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; to be fixed, either automatically or =
through manual intervention.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; The alarm details table contains =
information which is applicable</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; to all instances of an alarm.&nbsp; It =
is populated at start-up with</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 2]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp; all alarms that could happen on a =
system.&nbsp; The information in this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; table should be fairly static during =
system operation.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; The active alarm table contains a list =
of alarms which are currently</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; occurring on a system. It is intended =
that this table be queried</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; upon device discovery and rediscovery =
to determine which alarms are</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; currently active on the device. This =
allows the network management</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; station to find out about any problems =
that may have occurred before</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; it started managing a particular =
network element, or while it was out</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; of contact with it.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Each alarm should have a corresponding =
clear which removes it from</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; the active alarm table. Alternatively =
it could be aged out.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; configuring and querying of alarm =
age-outs is not covered in this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; document.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>4. Relation to Notification Log MIB</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; This MIB is intended to compliment the =
notification log MIB, but</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; can be used independently.&nbsp; The =
active alarm table is defined in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; manner similar to that of the =
notification log table.&nbsp; This format</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; allows for the storage of any =
NOTIFICATION that can be defined using</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; SMI.&nbsp; Using the same format as the =
notification log MIB also</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; simplifies operations for systems =
choosing to implement both MIBs.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>5. Alarm Raise and Clear</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; The alarm details table provides a means =
of defining the raise/clear</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; relationship between alarms. The =
alarmDetailsPerceivedSeverity object</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; indicates whether this is a raise alarm =
or a clear alarm. The</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; alarmDetailsNotificationId gives the =
OID of this particular alarm. If</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; this is a raise alarm, the =
alarmDetailsClearNotificationId object</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; gives the OID of corresponding clear =
alarm.&nbsp; If this is a clear</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; alarm, the =
alarmDetailsClearNotificationId object gives the OID of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; one of the corresponding raise alarms =
for this clear.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>6. ITU-T X.733, X.736 Trap Content</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Selected information from ITU-T X.733, =
X.736 alarm documents has been</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; included in the alarmDetailsTable and =
the alarmActiveTable, depending</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; on the variability of this =
information.&nbsp; Support of these objects is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; not necessary to support the alarm =
raise/clear and active alarm</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; components of this MIB.</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 3]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>7. Definitions</FONT>
</P>

<P><FONT SIZE=3D2>ALARM-MIB DEFINITIONS ::=3D BEGIN</FONT>
</P>

<P><FONT SIZE=3D2>IMPORTS</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MODULE-IDENTITY, =
OBJECT-TYPE,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; experimental, Integer32, =
Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; TimeTicks, Counter32, =
Counter64,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; IpAddress, Opaque, =
mib-2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
FROM SNMPv2-SMI</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; TimeStamp, DateAndTime, =
DisplayString,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; StorageType, =
RowStatus&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; FROM SNMPv2-TC</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SnmpAdminString, =
SnmpEngineID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FROM =
SNMP-FRAMEWORK-MIB</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MODULE-COMPLIANCE, =
OBJECT-GROUP&nbsp;&nbsp;&nbsp;&nbsp; FROM SNMPv2-CONF;</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; alarm MODULE-IDENTITY</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LAST-UPDATED =
&quot;000010220000Z&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ORGANIZATION =
&quot;Alarm MIB&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
CONTACT-INFO</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &quot;&nbsp;&nbsp; Sharon Chisholm</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Nortel =
Networks</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PO Box 3511 Station =
C</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ottawa, Ont.&nbsp; K1Y =
4H7</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Canada</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
schishol@nortelnetworks.com&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &quot;The MIB module describes a generic =
solution</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; to improve the reliability of SNMP traps by =
storing alarm</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; details and the current list of active =
alarms.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { mib-2 =
xx }</FONT>
</P>

<P><FONT SIZE=3D2>alarmObjects OBJECT IDENTIFIER ::=3D { alarm 1 =
}</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmDetailsTable OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
AlarmDetailsEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
table of information about possible alarms on the system.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmObjects 1 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsEntry OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AlarmDetailsEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Entries appear in this table for each possible =
alarm.&quot;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 4]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { alarmListName, =
alarmDetailsIndex }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsTable 1 =
}</FONT>
</P>

<P><FONT SIZE=3D2>AlarmDetailsEntry ::=3D SEQUENCE {</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsNotificationId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT IDENTIFIER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsClearNotificationId&nbsp;&nbsp; OBJECT IDENTIFIER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsEventType&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; INTEGER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; alarmDetailsProbableCause&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsPerceivedSeverity&nbsp;&nbsp;&nbsp;&nbsp; INTEGER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmDetailsAdditionalText&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DisplayString }</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmDetailsIndex OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32 (1..4294967295)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
integer which acts as the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; index of =
entries within the named alarm list. &quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 1 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsNotificationId OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT IDENTIFIER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
NOTIFICATION-TYPE object identifier of this alarm.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 2 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsClearNotificationId OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT IDENTIFIER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
NOTIFICATION-TYPE object identifier of the alarm which</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
clears this alarm. If this entry corresponds to a clear</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
alarm, then this object should be one of the notifications</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
which sets this alarm condition&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 3 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsEventType OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; INTEGER</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; other (1),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; communityAlarmType (2),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; qualityOfServerAlarmType (3),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; processingErrorAlarmType (4),</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 5]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; equipmentAlarmType (5),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; environmentalAlarmType =
(6)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =
read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &quot; Represents the event type values for the alarms as =
per</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; (ITU-T X.733).&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 4 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsProbableCause OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; other (1),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; adapterError (2),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; applicationSubsystemFailure (3),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; bandwidthReduced (4),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; callEstablishmentError (5),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; communicationsProtocolError (6),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; communicationsSubsystemFailure (7),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; configurationOrCustomizationError (8),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; congestion (9),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; corruptData (10),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; cpuCyclesLimitExceeded (11),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; dataSetOrModemError (12),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; degradedSignal (13),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; dteDceInterfaceError (14),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; enclosureDoorOpen (15),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; equipmentMalfunction (16),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; excessiveVibration (17),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; fileError (18),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; fireDetected (19),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; floodDetected (20),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; framingError (21),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; heatingOrVentilationOrCoolingSystemProblem (22),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; humidityUnacceptable (23),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; inputOutputDeviceError (24),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; inputDeviceError (25),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; lanError (26),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; leakDetected (27),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; localNodeTransmissionError (28),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; lossOfFrame (29),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; lossOfSignal (30),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; materialSupplyExhausted (31),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; multiplexerProblem (32),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; outOfMemory (33),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; ouputDeviceError (34),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; performanceDegraded (35),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; powerProblem (36),</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 6]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; pressureUnacceptable (37),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; processorProblem (38),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; pumpFailure (39),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; queueSizeExceeded (40),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; receiveFailure (41),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; receiverFailure (42),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; remoteNodeTransmissionError (43),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; resourceAtOrNearingCapacity (44),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; responseTimeExecessive (45),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; retransmissionRateExcessive (46),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; softwareError (47),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; softwareProgramAbnormallyTerminated (48),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; softwareProgramError (49),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; storageCapacityProblem (50),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; temperatureUnacceptable (51),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; thresholdCrossed (52),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; timingProblem (53),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; toxicLeakDetected (54),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; transmitFailure (55),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; transmitterFailure (56),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; underlyingResourceUnavailable (57),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; versionMismatch (58),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; authenticationFailure (59),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; breachOfConfidentiality (60),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; cableTamper (61),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; delayedInformation (62),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; denialOfService (63),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; duplicateInformation (64),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; informationMissing (65),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; informationModificationDetected (66),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; informationOutOfSequence (67),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; intrusionDetection (68),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; keyExpired (69),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; nonRepudiationFailure (70),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; outOfHoursActivity (71),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; outOfService (72),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; proceduralError (73),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; unauthorizedAccessAttempt (74),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; unexpectedInformation (75)</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &quot; Represents the probable cause values for the alarms =
as</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; per (ITU-T X.733, X.736).&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 5 =
}</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 7]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmDetailsPerceivedSeverity OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
INTEGER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; {</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; cleared (1),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; indeterminate (2),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; critical (3),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; major (4),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; minor (5),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; warning =
(6)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &quot; Represents the perceived severity values for the =
alarms</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; as per (ITU-T X.733).&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { alarmDetailsEntry 6 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmDetailsAdditionalText OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX =
DisplayString</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &quot; Represents the additional text field for the alarm as =
per</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; (ITU-T X.733).&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
::=3D { alarmDetailsEntry 7}</FONT>
</P>

<P><FONT SIZE=3D2>-- -- Active Alarm Table --</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmActiveTable OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
AlarmActiveEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
table of Active Alarms entries.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmObjects 2 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveEntry OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AlarmActiveEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Entries appear in this table when alarms are active.&nbsp; They =
are</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; removed =
when the alarm is no longer occurring.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { alarmListName, =
alarmActiveIndex }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveTable 1 =
}</FONT>
</P>

<P><FONT SIZE=3D2>AlarmActiveEntry ::=3D SEQUENCE {</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmListName&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
SnmpAdminString,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32,</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 8]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveTime&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TimeStamp,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveDateAndTime&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; DateAndTime,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveEngineID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; SnmpEngineID,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveEngineAddress&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 IpAddress,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveContextEngineID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
SnmpEngineID,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveContextName&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; SnmpAdminString,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariables&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveNotificationID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT IDENTIFIER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveTrendIndication&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
INTEGER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveLogIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveDetailsIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Unsigned32 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmListName OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
SnmpAdminString (SIZE(0..32))</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; &quot;The name of the list =
of alarms.&nbsp; This is the same as</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; nlmLogName if the =
Nofication Log MIB is supported.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; An implementation may allow =
multiple named alarm lists, up to</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; some =
implementation-specific limit (which may be none).&nbsp; A</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; zero-length list name is =
reserved for creation and deletion</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; by the managed system, and =
MUST be used as the default log</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; name by systems that do not =
support named alarm lists.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 1 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveIndex OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32 (1..4294967295)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
monotonically increasing integer which acts as the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; index of =
entries within the named alarm list.&nbsp; It wraps</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; back to 1 =
after it reaches its maximum value.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 2 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveTime OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TimeStamp</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value of sysUpTime when the alarm occurred. Alarms tend</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to get =
cleared and resent if still applicable at reboot, so this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; value =
tends to be is a valid sysUptime. In the case where the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; alarms =
are not cleared at reboot, and the alarm occurred before</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the most =
recent management system initialization, this object</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; value =
MUST be set to zero.&quot;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 9]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 3 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveDateAndTime OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DateAndTime</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
local date and time when the alarm occurred, instantiated</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only by =
systems that have date and time capability.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 4 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveEngineID OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SnmpEngineID</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
identification of the SNMP engine at which the alarm</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
originated.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the =
alarm list can contain Notifications from only one</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; engine or =
the Trap is from an SNMPv1 system, this object is not</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
instantiated.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 5 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveEngineAddress OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IpAddress</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; &quot;The IP Address of the =
SNMP engine on which the alarm is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; occurring. This is used to =
identify the source of an SNMPv1</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; trap, since an =
alarmActiveEngineId cannot be extracted from the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; SNMPv1 trap pdu.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; This object MUST always be =
instantiated, even if the list</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; can contain alarms from =
only one engine.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 6 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveContextEngineID OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SnmpEngineID</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; &quot;If the alarm is =
occurring on a device using a protocol which</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; has a contextEngineID =
element like SNMPv3, this object has that</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; value. Otherwise its value =
is a zero-length string.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 7 =
}</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 10]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmActiveContextName OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SnmpAdminString</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
name of the SNMP MIB context from which the alarm came.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For =
SNMPv1 Traps this is the community string from the Trap.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the =
alarm's source SNMP engine is known not to support</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multiple =
contexts, this object is not instantiated.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 8 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariables OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
number of variables in alarmActiveVariableTable for this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Notification.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 9 =
}</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmActiveNotificationID OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT IDENTIFIER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
NOTIFICATION-TYPE object identifier of the Notification</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that =
occurred.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 10 =
}</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmActiveTrendIndication OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; INTEGER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; moreSevere =
(1),</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; noChange =
(2),</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lessSevere =
(3)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &quot; Represents the trend indication values for the =
alarms</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; as per (ITU-T X.733).&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 11 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveLogIndex OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32 (0..4294967295)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS read-only</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 11]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;This number can be considered a sequence number for the =
trap.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It should =
be the same as the log index in the notification log</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIB, if =
used.&nbsp; If no log index or sequence number applies to the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; trap, =
then this object should have the value of 0.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 12 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveDetailsIndex OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32 (0..4294967295)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
index of the corresponding row in the alarmDetails table.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the =
alarmDetails table is not supported this object should</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have a =
value of 0.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveEntry 13 =
}</FONT>
</P>

<P><FONT SIZE=3D2>-- -- Active Alarm Variable Table --</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableTable OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
AlarmActiveVariableEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
table of variables to go with active alarm entries.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmObjects 3 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableEntry OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AlarmActiveVariableEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; =
not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Entries appear in this table when there are variables in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
varbind list of a corresponding alarm in alarmActiveTable.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; INDEX&nbsp;&nbsp; {&nbsp; =
alarmListName, alarmActiveIndex, alarmActiveVariableIndex</FONT>
<BR><FONT SIZE=3D2>}</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableTable =
1 }</FONT>
</P>

<P><FONT SIZE=3D2>AlarmActiveVariableEntry ::=3D SEQUENCE {</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT =
IDENTIFIER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableValueType&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableCounter32Val&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Counter32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableUnsigned32Val&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Unsigned32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableTimeTicksVal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; TimeTicks,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableInteger32Val&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Integer32,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableOctetStringVal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; OCTET STRING,</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 12]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableIpAddressVal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; IpAddress,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableOidVal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT IDENTIFIER,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableCounter64Val&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Counter64,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableOpaqueVal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; Opaque }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableIndex OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32 (1..4294967295)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A =
monotonically increasing integer, starting at 1 for a given</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
alarmActiveIndex, for indexing variables within the active</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; alarm =
list.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
1 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableID OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT IDENTIFIER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
variable's object identifier.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
2 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableValueType OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER { counter32(1), =
unsigned32(2), timeTicks(3),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; integer32(4), ipAddress(5), octetString(6),</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; objectId(7), counter64(8), opaque(9) }</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
type of the value.&nbsp; One and only one of the value</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; objects =
that follow is used, based on this type.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
3 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableCounter32Val OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Counter32</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'counter32'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
4 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableUnsigned32Val OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'unsigned32'.&quot;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 13]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry 5 =
}</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableTimeTicksVal OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TimeTicks</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'timeTicks'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
6 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableInteger32Val OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Integer32</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'integer32'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
7 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableOctetStringVal OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OCTET STRING</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'octetString'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
8 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableIpAddressVal OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IpAddress</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'ipAddress'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
9 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableOidVal OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECT IDENTIFIER</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'objectId'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
10 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableCounter64Val OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Counter64</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'counter64'.&quot;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 14]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
11 }</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveVariableOpaqueVal OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Opaque</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp; read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; DESCRIPTION</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The =
value when alarmActiveVariableType is 'opaque'.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; ::=3D { alarmActiveVariableEntry =
12 }</FONT>
</P>

<P><FONT SIZE=3D2>-- -- Statistics --</FONT>
</P>

<P><FONT SIZE=3D2>alarmActiveStatsTable&nbsp; OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX&nbsp; =
SEQUENCE OF AlarmActiveStatsEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp; not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;This table represents the alarm statistics type</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
alarmObjects 4 }</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp; alarmActiveStatsEntry OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX&nbsp; =
AlarmActiveStatsEntry</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp; not-accessible</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Statistics on the current active alarms.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
INDEX&nbsp;&nbsp; { alarmListName }</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D =
{&nbsp; alarmActiveStatsTable 1 }</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp; AlarmActiveStatsEntry ::=3D</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE =
{</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; alarmActiveStatsTotalActive&nbsp;&nbsp;&nbsp; Unsigned32</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp; alarmActiveStatsTotalActive OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX =
Unsigned32</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS =
read-only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;The total number of currently active alarms on the =
system.&quot;</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 15]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
alarmActiveStatsEntry 1 }</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; -- Conformance Stuff</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; alarmConformance OBJECT =
IDENTIFIER ::=3D { alarm 2 }</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsGroup =
OBJECT-GROUP</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECTS =
{</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; alarmDetailsIndex,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsNotificationId,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsClearNotificationId,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsEventType,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsProbableCause,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsPerceivedSeverity,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmDetailsAdditionalText</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp; current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Alarm details list =
group.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
::=3D { alarmConformance 2}</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
alarmActiveListGroup =
OBJECT-GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OBJECTS {</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
alarmListName,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveIndex,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveTime,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveDateAndTime,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveEngineID,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveEngineAddress,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveContextEngineID,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveContextName,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariables,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveNotificationID,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveLogIndex,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableIndex,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableID,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableValueType,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableCounter32Val,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableUnsigned32Val,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableTimeTicksVal,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableInteger32Val,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableOctetStringVal,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableIpAddressVal,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableOidVal,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableCounter64Val,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; alarmActiveVariableOpaqueVal</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 16]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp; =
current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Active Alarm list group.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
::=3D { alarmConformance 3}</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; =
alarmActiveSummaryGroup&nbsp; OBJECT-GROUP</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECTS&nbsp; {</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
alarmActiveStatsTotalActive</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
STATUS&nbsp;&nbsp; current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &quot; Active alarm summary =
group.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
::=3D { alarmConformance 4}</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>alarmCompliance MODULE-COMPLIANCE</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp; =
current</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;The compliance statement for systems supporting</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the Alarm MIB.&quot;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MODULE -- this =
module</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MANDATORY-GROUPS {</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; alarmActiveListGroup</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
GROUP alarmActiveSummaryGroup</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;The actual active alarms.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
alarmConformance 1 =
}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; END</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>8. Example</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Define the =
following Object:</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
acmeWidgetIndex OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; SYNTAX&nbsp; Integer32</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; MAX-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; STATUS&nbsp;&nbsp; current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &quot;A unique number which identifies a particular =
Widget.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
acmeWidgetEntry 1 }</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Define the =
following three traps:</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
acmeWidgetTemperatureCritical NOTIFICATION-TYPE</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; OBJECTS { acmeWidgetIndex }</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &quot;This trap indicates that the indicated</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 17]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; widget has reached a critical =
temperature.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
acmeWidgetTraps 1 }</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
acmeWidgetTemperatureNormal NOTIFICATION-TYPE</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; OBJECTS { acmeWidgetIndex }</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &quot;This trap indicates that the indicated widget =
has</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; reached a normal temperature.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
acmeWidgetTraps 2 }</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bgpBackwardTransition NOTIFICATION-TYPE</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; OBJECTS { bgpPeerLastError,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bgpPeerState&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; STATUS&nbsp; current</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &quot;The BGPBackwardTransition Event is =
generated</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; when the BGP FSM moves from a higher =
numbered</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; state to a lower numbered state.&quot;</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
::=3D { bgpTraps 2 }</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0. Active =
alarm table empty and nothing in notification log</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
___________________________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
alarmActiveTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp; | =
nlmLogTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------|&nbsp;&nbsp;&nbsp; =
|---------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | alarmActiveIndex |&nbsp; alarm =
|&nbsp;&nbsp;&nbsp; | nlmLogIndex | alarm |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------|&nbsp;&nbsp;&nbsp; =
|---------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|___________________________|&nbsp;&nbsp;&nbsp; =
|_____________________|</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1. =
Temperature of widget 2 goes critical</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__________________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
alarmActiveTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | alarmActiveIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
acmeWidgetTemperatureCritical |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|__________________________________________________|</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
nlmLogTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | nlmLogIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | acmeWidgetTemperatureCritical =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________________________________________|</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2. BGP =
peering session transitions from a state of established</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 18]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
to opensent</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__________________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
alarmActiveTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | alarmActiveIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
acmeWidgetTemperatureCritical |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
bgpBackwardTransition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|__________________________________________________|</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
nlmLogTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | nlmLogIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | acmeWidgetTemperatureCritical =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
bgpBackwardTransition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________________________________________|</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3. =
Temperature of widget 2 goes back to normal</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__________________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
alarmActiveTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | alarmActiveIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
bgpBackwardTransition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|__________________________________________________|</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
nlmLogTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | nlmLogIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | acmeWidgetTemperatureCritical =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
bgpBackwardTransition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
acmeWidgetTemperatureNormal&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________________________________________|</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4. Time =
passes .... BGP alarm ages out.</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__________________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
alarmActiveTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | alarmActiveIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|--------------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|__________________________________________________|</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 19]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________________________</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | =
nlmLogTable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; | nlmLogIndex |&nbsp; =
alarm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | acmeWidgetTemperatureCritical =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
bgpBackwardTransition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
acmeWidgetTemperatureNormal&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________________________________________|</FONT>
</P>

<P><FONT SIZE=3D2>9. Security Considerations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp; There are no management objects defined =
in this MIB that have a MAX-</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ACCESS clause of read-write and/or =
read-create.&nbsp; So, if this MIB is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; implemented correctly, then there is no =
risk that an intruder can</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; alter or create any management objects =
of this MIB via direct SNMP</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; SET operations.</FONT>
</P>

<P><FONT SIZE=3D2>10. Author's Address</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Sharon Chisholm</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Nortel Networks</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; PO Box 3511, Station C</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Ottawa, Ontario, K1Y 4H7</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Canada</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Email: =
schishol@nortelnetworks.com</FONT>
</P>

<P><FONT SIZE=3D2>11. References</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [1] =
Stewart, B,&nbsp; Kavasseri, R, &quot;Notification Log MIB,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; draft 17, October 2000</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [2] ITU =
Recommendation X.733, &quot;Information Technology - Open</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Systems Interconnection - System Management: Alarm Reporting</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Function&quot;, 1992</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [3] ITU =
Recommendation X.736, &quot;Information Technology - Open</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Systems Interconnection - System Management: Security Alarm</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Reporting Function&quot;, 1992</FONT>
</P>

<P><FONT SIZE=3D2>12. Full Copyright Statement</FONT>
</P>

<P><FONT SIZE=3D2>Copyright (C) The Internet Society (2000). All Rights =
Reserved.</FONT>
</P>

<P><FONT SIZE=3D2>This document and translations of it may be copied =
and furnished to</FONT>
<BR><FONT SIZE=3D2>others, and derivative works that comment on or =
otherwise explain it or</FONT>
<BR><FONT SIZE=3D2>assist in its implementation may be prepared, =
copied, published and</FONT>
<BR><FONT SIZE=3D2>distributed, in whole or in part, without =
restriction of any kind,</FONT>
<BR><FONT SIZE=3D2>provided that the above copyright notice and this =
paragraph are included</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 20]</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Internet =
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alarm =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; 22 October 2000</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>on all such copies and derivative works.&nbsp; =
However, this document itself</FONT>
<BR><FONT SIZE=3D2>may not be modified in any way, such as by removing =
the copyright notice</FONT>
<BR><FONT SIZE=3D2>or references to the Internet Society or other =
Internet organizations,</FONT>
<BR><FONT SIZE=3D2>except as needed for the&nbsp; purpose of developing =
Internet standards in</FONT>
<BR><FONT SIZE=3D2>which case the procedures for copyrights defined in =
the Internet</FONT>
<BR><FONT SIZE=3D2>Standards process must be followed, or as required =
to translate it into</FONT>
<BR><FONT SIZE=3D2>languages other than English.</FONT>
</P>

<P><FONT SIZE=3D2>The limited permissions granted above are perpetual =
and will not be</FONT>
<BR><FONT SIZE=3D2>revoked by the Internet Society or its successors or =
assigns.</FONT>
</P>

<P><FONT SIZE=3D2>This document and the information contained herein is =
provided on an &quot;AS</FONT>
<BR><FONT SIZE=3D2>IS&quot; basis and THE INTERNET SOCIETY AND THE =
INTERNET ENGINEERING TASK</FONT>
<BR><FONT SIZE=3D2>FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, =
INCLUDING BUT NOT</FONT>
<BR><FONT SIZE=3D2>LIMITED TO ANY WARRANTY THAT THE USE OF THE =
INFORMATION HEREIN WILL NOT</FONT>
<BR><FONT SIZE=3D2>INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF =
MERCHANTABILITY OR</FONT>
<BR><FONT SIZE=3D2>FITNESS FOR A PARTICULAR PURPOSE.</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Expires 22 April =
2001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 21]</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C03CEA.2B9F5510--


From owner-disman@dorothy.bmc.com  Fri Oct 27 12:46:59 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA24574
	for <disman-archive@odin.ietf.org>; Fri, 27 Oct 2000 12:46:55 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id e9RGWDH20464;
	Fri, 27 Oct 2000 11:32:14 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA21481
	for disman-list; Fri, 27 Oct 2000 09:30:16 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA21475
	for disman@dorothy.bmc.com; Fri, 27 Oct 2000 09:30:12 -0700 (PDT)
Date: Fri, 27 Oct 2000 09:30:12 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200010271630.JAA21475@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Fwd: RE: draft-chisholm-disman-active-alarm-01.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9RGWDH20464
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA24574


Hi -

Yet another forwarded posting.

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA17785
> 	for <disman@dorothy.peer.com>; Thu, 26 Oct 2000 17:28:57 -0700 (PDT)
> Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
> 	by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e9R0TZU13806;
> 	Thu, 26 Oct 2000 19:29:35 -0500 (CDT)
> Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21)
> 	id <VJ74HRRL>; Thu, 26 Oct 2000 19:30:19 -0500
> Message-ID: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E9F6@es01-sjc.bmc.com>
> From: "Ayers, Mike" <Mike_Ayers@bmc.com>
> To: "'Sharon Chisholm'" <schishol@nortelnetworks.com>
> Cc: disman@dorothy.bmc.com
> Subject: RE: draft-chisholm-disman-active-alarm-01.txt
> Date: Thu, 26 Oct 2000 19:31:41 -0500
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> 
> 	Here's my commentary.
> 
> {AlarmDetailsEntry}
> 
> 	X.736/10164-7 (my copy dated 16Jul91, "almost final") mandates
> security alarm detector, service user, and service provider objects.  If
> these were added, not only would this MIB be mostly X.733/10164-4 and
> X.736/10164-7 compliant (other than that CMIP thing...), but I suspect such
> objects would appeal to the security folks as well.  Could these be added?
> 
> 	I can think of one way to do it.  The objects could be filled by
> declaring objects for them in the MIB which, when found in a trap, would be
> routed to the alarmDetailsEntry instead of the alarmActiveVariableEntry.  So
> long as these objects are defined in this MIB, there should be minimal risk
> of confusion.
> 
> 	On the other hand, one could argue that the ability to put
> independent objects with such a meaning into a trap (which would wind up in
> the alarmActiveVariableEntry) in itself fulfills the requirements.  However,
> this method would preclude transformation of X.736/10164-7 tables into the
> active alarm MIB (for, say, remote monitoring).
> 
> 	Therefore, if there is real possibility of the Active Alarm MIB
> being used to reflect or source an X.736/10164-7 table, the creation of such
> objects is important, otherwise it is just desireable (or possibly
> pointless).
> 
> {alarmDetailsEventType}
> 
> 	"communityAlarmType" s/b "communicationsAlarmType"
> 	"qualityOfServerAlarmType" s/b "qualityOfServiceAlarmType"
> 
> 	Need to add integrityViolationType, operationalViolationType,
> physicalViolationType, securityServiceOrMechanismViolationType, and
> timeDomainViolationType.
> 
> {alarmDetailsAdditionalText}
> 
> 	This is type DisplayString, which is limited to 255 bytes of 7 bit
> ASCII.  A UTF8String type would be much much better.  Please consider
> snipping that TC from draft-ietf-snmpconf-pm-03.txt.
> 
> {alarmActiveTime}
> 
> 	"tends to be is a valid" - delete "is".
> 
> {alarmActiveEngineAddress}
> 
> 	Wouldn't a TDomain/TAddress pair be more friendly to less mainstream
> implementations?
> 
> {alarmActiveVariableValueType}
> 
> 	If octetString=5 and ipAddress=6, then the index of the desired
> value will be a constant offset plus alarmActiveVariableValueType -
> otherwise, a lookup table will be needed.  I am sending a matching note to
> the Notification Log MIB author.
> 
> {alarmActiveListGroup}
> 
> 	[niggly] alarmActiveGroup would seem to fit the pattern better.
> 
> {alarmActiveSummaryGroup}
> 
> 	[niggly] alarmActiveStatsGroup would seem to fit the pattern better.
> 
> {ALARM-MIB DEFINITIONS}
> 
> 	[niggly] "END" should be at the left of the following line. (Yes, I
> know it affects nothing, that's why it says "niggly"  ;-)
> 
> 
> 	HTH,
> 
> /|/|ike
> 


From owner-disman@dorothy.bmc.com  Fri Oct 27 12:48:36 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25103
	for <disman-archive@odin.ietf.org>; Fri, 27 Oct 2000 12:48:36 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id e9RGWDm20462;
	Fri, 27 Oct 2000 11:32:14 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA21448
	for disman-list; Fri, 27 Oct 2000 09:29:22 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA21442
	for disman@dorothy.bmc.com; Fri, 27 Oct 2000 09:29:18 -0700 (PDT)
Date: Fri, 27 Oct 2000 09:29:18 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200010271629.JAA21442@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Fwd: RE: draft-ietf-disman-notif-log-mib-17.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id e9RGWDm20462
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA25103


Hi -

I'm forwarding a message from a disman subscriber who posted from
an address other than his subscription address.  (I've added this
address to the "posters" list.)

 -------------------------------------------------------
 Randy Presuhn           randy_presuhn@bmc.com
 Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
 Fax:   +1 408 965-0359  2141 North First Street
 http://www.bmc.com/     San José, California 95131  USA
 -------------------------------------------------------
 My opinions and BMC's are independent variables.
 -------------------------------------------------------

> Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA17775
> 	for <disman@dorothy.peer.com>; Thu, 26 Oct 2000 17:28:31 -0700 (PDT)
> Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
> 	by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e9R0TB213790;
> 	Thu, 26 Oct 2000 19:29:11 -0500 (CDT)
> Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21)
> 	id <VJ74HRR2>; Thu, 26 Oct 2000 19:29:55 -0500
> Message-ID: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E9F5@es01-sjc.bmc.com>
> From: "Ayers, Mike" <Mike_Ayers@bmc.com>
> To: "'ramk@cisco.com'" <ramk@cisco.com>
> Cc: disman@dorothy.bmc.com
> Subject: RE: draft-ietf-disman-notif-log-mib-17.txt
> Date: Thu, 26 Oct 2000 19:31:16 -0500
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> 
> 	I noticed one thing while referencing this doc as I checked the
> Active Alarm MIB proposal (draft-chisholm-disman-active-alarm-01.txt).
> 
> 	For nlmLogVariableValueType, if OctetString=5 and ipAddress=6, then
> the index of the desired value will be nlmLogVariableValueType plus a
> constant offset.  As it stands, a lookup table (or some odd logic) would be
> necessary.
> 
> 
> /|/|ike
> 


From owner-disman@dorothy.bmc.com  Mon Oct 30 09:37:23 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11583
	for <disman-archive@odin.ietf.org>; Mon, 30 Oct 2000 09:37:23 -0500 (EST)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id e9UEZkk17168;
	Mon, 30 Oct 2000 08:35:47 -0600 (CST)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id GAA00591
	for disman-list; Mon, 30 Oct 2000 06:31:53 -0800 (PST)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA00586
	for <disman@dorothy.peer.com>; Mon, 30 Oct 2000 06:31:48 -0800 (PST)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with SMTP id e9UEVG316345
	for <disman@dorothy.peer.com>; Mon, 30 Oct 2000 08:31:16 -0600 (CST)
Received: from zrchb213.us.nortel.com (actually zrchb213) 
          by smtprch1.nortel.com; Mon, 30 Oct 2000 08:27:51 -0600
Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2652.35) 
          id <VHCDMG1W>; Mon, 30 Oct 2000 08:27:43 -0600
Message-ID: <6DDA62170439D31185750000F80826AC04310759@zmerd004.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
Cc: disman@dorothy.bmc.com
Subject: RE: draft-chisholm-disman-active-alarm-01.txt
Date: Mon, 30 Oct 2000 08:27:40 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0427D.8F540F90"
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0427D.8F540F90
Content-Type: text/plain;
	charset="iso-8859-1"

hi

I start holidays tomorrow, so I will be reading any other
comments and suggestions when I get back November 26th.  
Please do reply though.

I can certainly incorporate the corrections, but I have a
question about the security information.  From my copy of
X.736:

Security alarm detector - This parameter identifies the detector
of the security alarm.

Service user - This parameter identifies the service-user whose
request for service led to the generation of the security alarm.

Service provider - This parameter identifies the intended service-provider
of the service that led to the generation of the security alarm.

These seem to apply to only a small subset of alarms.  Wouldn't it
then be better to go with the option you also suggested of just 
having them as varbinds in the trap, and therefore present in the
alarmActiveVariablesTable?

Also, are there any security implications of making this available in
a MIB?  I know a lot of systems have a way of turning off the SNMP
authentication failure trap for this reason.

thanks,

Sharon

PS.  I send explicitly as plain text, it just arrive as html. Network
     Gremlins.

-----Original Message-----
From: Ayers, Mike [mailto:Mike_Ayers@bmc.com]
Sent: Thursday, October 26, 2000 8:32 PM
To: Chisholm, Sharon [CAR:5K32:EXCH]
Cc: disman@dorothy.peer.com
Subject: RE: draft-chisholm-disman-active-alarm-01.txt



	Here's my commentary.

{AlarmDetailsEntry}

	X.736/10164-7 (my copy dated 16Jul91, "almost final") mandates
security alarm detector, service user, and service provider objects.  If
these were added, not only would this MIB be mostly X.733/10164-4 and
X.736/10164-7 compliant (other than that CMIP thing...), but I suspect such
objects would appeal to the security folks as well.  Could these be added?

	I can think of one way to do it.  The objects could be filled by
declaring objects for them in the MIB which, when found in a trap, would be
routed to the alarmDetailsEntry instead of the alarmActiveVariableEntry.  So
long as these objects are defined in this MIB, there should be minimal risk
of confusion.

	On the other hand, one could argue that the ability to put
independent objects with such a meaning into a trap (which would wind up in
the alarmActiveVariableEntry) in itself fulfills the requirements.  However,
this method would preclude transformation of X.736/10164-7 tables into the
active alarm MIB (for, say, remote monitoring).

	Therefore, if there is real possibility of the Active Alarm MIB
being used to reflect or source an X.736/10164-7 table, the creation of such
objects is important, otherwise it is just desireable (or possibly
pointless).

{alarmDetailsEventType}

	"communityAlarmType" s/b "communicationsAlarmType"
	"qualityOfServerAlarmType" s/b "qualityOfServiceAlarmType"

	Need to add integrityViolationType, operationalViolationType,
physicalViolationType, securityServiceOrMechanismViolationType, and
timeDomainViolationType.

{alarmDetailsAdditionalText}

	This is type DisplayString, which is limited to 255 bytes of 7 bit
ASCII.  A UTF8String type would be much much better.  Please consider
snipping that TC from draft-ietf-snmpconf-pm-03.txt.

{alarmActiveTime}

	"tends to be is a valid" - delete "is".

{alarmActiveEngineAddress}

	Wouldn't a TDomain/TAddress pair be more friendly to less mainstream
implementations?

{alarmActiveVariableValueType}

	If octetString=5 and ipAddress=6, then the index of the desired
value will be a constant offset plus alarmActiveVariableValueType -
otherwise, a lookup table will be needed.  I am sending a matching note to
the Notification Log MIB author.

{alarmActiveListGroup}

	[niggly] alarmActiveGroup would seem to fit the pattern better.

{alarmActiveSummaryGroup}

	[niggly] alarmActiveStatsGroup would seem to fit the pattern better.

{ALARM-MIB DEFINITIONS}

	[niggly] "END" should be at the left of the following line. (Yes, I
know it affects nothing, that's why it says "niggly"  ;-)


	HTH,

/|/|ike

------_=_NextPart_001_01C0427D.8F540F90
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: draft-chisholm-disman-active-alarm-01.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>hi</FONT>
</P>

<P><FONT SIZE=2>I start holidays tomorrow, so I will be reading any other</FONT>
<BR><FONT SIZE=2>comments and suggestions when I get back November 26th.&nbsp; </FONT>
<BR><FONT SIZE=2>Please do reply though.</FONT>
</P>

<P><FONT SIZE=2>I can certainly incorporate the corrections, but I have a</FONT>
<BR><FONT SIZE=2>question about the security information.&nbsp; From my copy of</FONT>
<BR><FONT SIZE=2>X.736:</FONT>
</P>

<P><FONT SIZE=2>Security alarm detector - This parameter identifies the detector</FONT>
<BR><FONT SIZE=2>of the security alarm.</FONT>
</P>

<P><FONT SIZE=2>Service user - This parameter identifies the service-user whose</FONT>
<BR><FONT SIZE=2>request for service led to the generation of the security alarm.</FONT>
</P>

<P><FONT SIZE=2>Service provider - This parameter identifies the intended service-provider</FONT>
<BR><FONT SIZE=2>of the service that led to the generation of the security alarm.</FONT>
</P>

<P><FONT SIZE=2>These seem to apply to only a small subset of alarms.&nbsp; Wouldn't it</FONT>
<BR><FONT SIZE=2>then be better to go with the option you also suggested of just </FONT>
<BR><FONT SIZE=2>having them as varbinds in the trap, and therefore present in the</FONT>
<BR><FONT SIZE=2>alarmActiveVariablesTable?</FONT>
</P>

<P><FONT SIZE=2>Also, are there any security implications of making this available in</FONT>
<BR><FONT SIZE=2>a MIB?&nbsp; I know a lot of systems have a way of turning off the SNMP</FONT>
<BR><FONT SIZE=2>authentication failure trap for this reason.</FONT>
</P>

<P><FONT SIZE=2>thanks,</FONT>
</P>

<P><FONT SIZE=2>Sharon</FONT>
</P>

<P><FONT SIZE=2>PS.&nbsp; I send explicitly as plain text, it just arrive as html. Network</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Gremlins.</FONT>
</P>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Ayers, Mike [<A HREF="mailto:Mike_Ayers@bmc.com">mailto:Mike_Ayers@bmc.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Thursday, October 26, 2000 8:32 PM</FONT>
<BR><FONT SIZE=2>To: Chisholm, Sharon [CAR:5K32:EXCH]</FONT>
<BR><FONT SIZE=2>Cc: disman@dorothy.peer.com</FONT>
<BR><FONT SIZE=2>Subject: RE: draft-chisholm-disman-active-alarm-01.txt</FONT>
</P>
<BR>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>Here's my commentary.</FONT>
</P>

<P><FONT SIZE=2>{AlarmDetailsEntry}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>X.736/10164-7 (my copy dated 16Jul91, &quot;almost final&quot;) mandates</FONT>
<BR><FONT SIZE=2>security alarm detector, service user, and service provider objects.&nbsp; If</FONT>
<BR><FONT SIZE=2>these were added, not only would this MIB be mostly X.733/10164-4 and</FONT>
<BR><FONT SIZE=2>X.736/10164-7 compliant (other than that CMIP thing...), but I suspect such</FONT>
<BR><FONT SIZE=2>objects would appeal to the security folks as well.&nbsp; Could these be added?</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>I can think of one way to do it.&nbsp; The objects could be filled by</FONT>
<BR><FONT SIZE=2>declaring objects for them in the MIB which, when found in a trap, would be</FONT>
<BR><FONT SIZE=2>routed to the alarmDetailsEntry instead of the alarmActiveVariableEntry.&nbsp; So</FONT>
<BR><FONT SIZE=2>long as these objects are defined in this MIB, there should be minimal risk</FONT>
<BR><FONT SIZE=2>of confusion.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>On the other hand, one could argue that the ability to put</FONT>
<BR><FONT SIZE=2>independent objects with such a meaning into a trap (which would wind up in</FONT>
<BR><FONT SIZE=2>the alarmActiveVariableEntry) in itself fulfills the requirements.&nbsp; However,</FONT>
<BR><FONT SIZE=2>this method would preclude transformation of X.736/10164-7 tables into the</FONT>
<BR><FONT SIZE=2>active alarm MIB (for, say, remote monitoring).</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>Therefore, if there is real possibility of the Active Alarm MIB</FONT>
<BR><FONT SIZE=2>being used to reflect or source an X.736/10164-7 table, the creation of such</FONT>
<BR><FONT SIZE=2>objects is important, otherwise it is just desireable (or possibly</FONT>
<BR><FONT SIZE=2>pointless).</FONT>
</P>

<P><FONT SIZE=2>{alarmDetailsEventType}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>&quot;communityAlarmType&quot; s/b &quot;communicationsAlarmType&quot;</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>&quot;qualityOfServerAlarmType&quot; s/b &quot;qualityOfServiceAlarmType&quot;</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>Need to add integrityViolationType, operationalViolationType,</FONT>
<BR><FONT SIZE=2>physicalViolationType, securityServiceOrMechanismViolationType, and</FONT>
<BR><FONT SIZE=2>timeDomainViolationType.</FONT>
</P>

<P><FONT SIZE=2>{alarmDetailsAdditionalText}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>This is type DisplayString, which is limited to 255 bytes of 7 bit</FONT>
<BR><FONT SIZE=2>ASCII.&nbsp; A UTF8String type would be much much better.&nbsp; Please consider</FONT>
<BR><FONT SIZE=2>snipping that TC from draft-ietf-snmpconf-pm-03.txt.</FONT>
</P>

<P><FONT SIZE=2>{alarmActiveTime}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>&quot;tends to be is a valid&quot; - delete &quot;is&quot;.</FONT>
</P>

<P><FONT SIZE=2>{alarmActiveEngineAddress}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>Wouldn't a TDomain/TAddress pair be more friendly to less mainstream</FONT>
<BR><FONT SIZE=2>implementations?</FONT>
</P>

<P><FONT SIZE=2>{alarmActiveVariableValueType}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>If octetString=5 and ipAddress=6, then the index of the desired</FONT>
<BR><FONT SIZE=2>value will be a constant offset plus alarmActiveVariableValueType -</FONT>
<BR><FONT SIZE=2>otherwise, a lookup table will be needed.&nbsp; I am sending a matching note to</FONT>
<BR><FONT SIZE=2>the Notification Log MIB author.</FONT>
</P>

<P><FONT SIZE=2>{alarmActiveListGroup}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>[niggly] alarmActiveGroup would seem to fit the pattern better.</FONT>
</P>

<P><FONT SIZE=2>{alarmActiveSummaryGroup}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>[niggly] alarmActiveStatsGroup would seem to fit the pattern better.</FONT>
</P>

<P><FONT SIZE=2>{ALARM-MIB DEFINITIONS}</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>[niggly] &quot;END&quot; should be at the left of the following line. (Yes, I</FONT>
<BR><FONT SIZE=2>know it affects nothing, that's why it says &quot;niggly&quot;&nbsp; ;-)</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>HTH,</FONT>
</P>

<P><FONT SIZE=2>/|/|ike</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0427D.8F540F90--


From owner-disman@dorothy.bmc.com  Mon Oct 30 20:27:20 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA15816
	for <disman-archive@odin.ietf.org>; Mon, 30 Oct 2000 20:27:20 -0500 (EST)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id e9V1Jmc15431;
	Mon, 30 Oct 2000 19:19:52 -0600 (CST)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA02172
	for disman-list; Mon, 30 Oct 2000 17:19:07 -0800 (PST)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA02167
	for <disman@dorothy.bmc.com>; Mon, 30 Oct 2000 17:19:03 -0800 (PST)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with SMTP id e9V1IXx15267
	for <disman@dorothy.bmc.com>; Mon, 30 Oct 2000 19:18:33 -0600 (CST)
Received: from netman (netman.6test.edu.cn [202.38.99.35])
	by 6bone.ipv6.net.edu.cn (8.10.1/8.10.1) with SMTP id e9V16nA07447
	for <disman@dorothy.bmc.com>; Tue, 31 Oct 2000 09:06:49 +0800 (CST)
Message-Id: <200010310106.e9V16nA07447@6bone.ipv6.net.edu.cn>
Date: Tue, 31 Oct 2000 9:18:2 +0800
From: Hu Qiang <huqiang@ns.6test.edu.cn>
Reply-To: huqiang@ns.6test.edu.cn
To: "disman@dorothy.bmc.com" <disman@dorothy.bmc.com>
X-mailer: FoxMail 3.0 beta 2 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


unsubscribe