Subject: Alarm MIB Issues List

From: "Sharon Chisholm" <[email-masked]>
Date: Thu, 11 Jan 2001 09:39:33 -0500

hi

Here is the issues and proposed solutions list for the Alarm
MIB.  

Dan and I are currently working on internet-drafts.  They will
likely be ready while Randy is on holiday.  Would the following
ID names be appropriate?
	draft-ietf-disman-alarm-mib-00.txt
	draft-ietf-disman-itualarm-mib-00.txt

Issues
1.	Performance
	a.	TimeFilter

	Add a TimeFilter object as the first index into the
alarmActiveTable. This will not help you figure out which alarms have been
cleared, but will provide an efficient way to tell which alarms have been
raised recently.

	b.	Provide lastChanged objects for alarmDetailsTable and
alarmActiveTable

	c.	Document algorithms for efficient use of the MIB data
structures

2.	Severity/States
	
	a. Model-neutral should use raise/clear.  Other states are reserved
for ITU MIB.

3.	What is the relationship between the MIBs?
	a.	ituAlarm MIB augments tables in alarm MIB

	b.    Use an OID and running index to point back

	c.	Describe the relationship between the MIBs

4.	Disagreement on how the mid-level manager keeps its alarm list up to
date.
		i.e..	Notifications vs. polling?

	a. Don't mention it and let the implementation decide?

5.	Do we want to address alarm aging?

	a. The definition of alarm that we seem to be converging on does not
allow for age-outs.  Remove reference to it in MIB description.

6.	Terms need definition
	a.	Fault
	b.	Notification
	c.	Alarm
	d.	Event/Informational Notification

7.	Making alarm definition and raise/clear relationship configurable?

	a. Sure, but the agent should have some row already created if
possible.

8.	Change ituAlarmAdditionalText to be UTF8?
9.	Would Tdomain/Taddress pair for alarmActiveEngineId be friendlier to
less mainstream implementations?

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario