[CCAMP] Comments on draft-vallin-ccamp-alarm-module-01

[Balazs Lengyel <[e-mail]>]

Hello,

Generally the module is good, but some comments:

4.5.1) Add as a recommendation: An alarm agent SHOULD describe how long it retains cleared/closed alarms: till manually purged or if it has an automatic removal policy.

5.1.1) State that shelving is effectively a way for the operator to suppress an alarm type/resource. Using the word suppress or block would make it easier to understand why do we do shelving.

For us it is a common situation that the operator does not want to suppress an alarm type, just change the severity level e.g. stating that a particular alarm type is not critical just minor. I am missing this functionality

typedef resource) It should be stated that when the resource is modeled both in YANG and in SNMP and possibly has other addresses (simple string, distinguished name) which should appear in the resource leaf/type. IS there a fixed precedence between these address types? IMHO there should be.

typedef severity) Which severity should be assigned to a loss of redundancy type problem? E.g. Link to one of the 2 license servers down.

container alarm-shelving)

- the description starts with "This list ..."

- Is it possible to unshelve an alarm? When will an alarm have operator-state un-shelved? If an un-shelved alarm is acknowledged, will the systems still remember it was unshelved? IMHO if we support unshelving it should be a separate property not part of operator state. I would need to know that the alarm was unshelved AND acknowledged, both.

container alarm inventory)

- the description starts with "This list ..."

As this container contains alarm-types, it should be called "container alarm-TYPE-inventory"

container summary)

"This container gives a summary of number of alarms and shelved alarms"

If the operator decided to suppress (shelve) an alarm, it
SHOULD NOT be part of the summary counters. I shelved it because
I am not interested, than don't count it.
If I try to assess my network node's health and I decided that typeX alarms are
not relevant for me, then an alarm count indicating I have 100 typeX suppressed alarms is misleading.
We need counters that exclude shelved alarms.

container shelved-alarms) The description does not allow for unshelving. Then why do we have such an operator state?

regards Balazs

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
Senior Specialist
Mobile: [phone]              email: [e-mail]