Subject: more comments...

From: Stefan Wallin <[email-masked]>
Date: Wed, 16 Jan 2002 19:21:32 +0100 (CET)

Hi!
More comments...

alarmModelRowStatus
=====================
Current description of alarmModelRowStatus:
 
"Control for creating and deleting entries.  Entries may be modified
while active.
This row can not be deleted while it is being referenced by a value of
alarmActiveModelPointer"
 
I assume we should expand the restrictions to:
This row can not be deleted or _modified_ while it is being referenced by
a value of alarmActiveModelPointer.
 
Since the manager can not reestablish the alarm if the alarmModel has
changed after the reference was setup between alarmActiveTable and
alarmModelTable.
Also, as stated previously add:
If the status is notInService alarmActiveModel will not be updated with 
corresponding alarm.

Comments of editorial art:

1) The ITU-ALARM-TC and ITU-IANA-ALARM-TC are missing MODULE-IDENTITY
 
2) The module name starts with ITU which normally should indicate the
   enterprise owning the module, I wonder what ITU says...
 
3) Groups in ITU-ALARM-MIB have strange names considering their contained
   objects.
 
 ituAlarmServiceUserGroup OBJECT-GROUP
     OBJECTS {
               ituAlarmAdditionalText,
               ituAlarmActiveTrendIndication
             }
 ituAlarmSecurityGroup OBJECT-GROUP
       OBJECTS {
               ituAlarmActiveDetector,
               ituAlarmActiveServiceProvider,
               ituAlarmActiveServiceUser
              }
 
  The ituAlarmServiceGroup has nothing to do with serviceUsers, they are in
  the next group...
  change ituAlarmServiceUserGroup to something like ituAlarmEnhancedGroup

4) Page 44: examples section:

remove alarmActiveDetailsIndex, old obsoleted object I guess?
 
alarmActiveModelPointer ituAlarmActiveEntry.1.3 should be:
alarmActiveModelPointer alarmModelEntry.1.3

best regards Stefan

Stefan Wallin
Data Ductus AB
+46 70 5233262
[email-masked]

Stefan Wallin
Data Ductus AB
+46 70 5233262
[email-masked]