Re: [CCAMP] Alarm Module work

"De La Marche, Dirk (Nokia - BE/Antwerp)" <> Thu, 07 June 2018 12:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C5CB5130EF8 for <>; Thu, 7 Jun 2018 05:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id f5msshNoIY0e for <>; Thu, 7 Jun 2018 05:45:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6D1F1130EE5 for <>; Thu, 7 Jun 2018 05:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=P3xK8L/OXYefpJobH+dnsSlAEun4dxI8Ytn5T02KKa8=; b=l43oN2YLFqoqHzfK+ujSbb2DBYvNe4MdDpacdF2zpESiCXStspGqMyUFR+HFIOOvtyQ65x3n2Q3yqTldSAhGsIgUcr06X1rbNYO9AlWQqsT72mIvHI0y+vbef1DsDH/pnMbEyYwgQhDyy/aGjF9ly7GbeJgCS881hHszVjyzE1I=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.6; Thu, 7 Jun 2018 12:45:00 +0000
Received: from ([fe80::d4e:1bc3:c897:78ca]) by ([fe80::d4e:1bc3:c897:78ca%3]) with mapi id 15.20.0863.004; Thu, 7 Jun 2018 12:45:00 +0000
From: "De La Marche, Dirk (Nokia - BE/Antwerp)" <>
To: stefan vallin <>
CC: NICK HANCOCK <>, Common Control and Measurement Plane Discussion List <>
Thread-Topic: [CCAMP] Alarm Module work
Thread-Index: AQHT+PyTXIQ9kDJyZku7l8czo2vJyqRKMfIAgAEo0OCACCuhAIABO9kw
Date: Thu, 7 Jun 2018 12:45:00 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2979; 7:++AJlf0AWoyO4j/gbol219mdC0ghxjC7+XAul7fmDNx1y54CQICEAroLp2iku+WsXQgfUww36TskpCnfuyANQ96zpObljvmE+EwhjIF9z8+sByAMTgL4Bx+VAU55oPUydr71WMvFPy+GO5Yhp00qWDFfXd6NTcEKZus5om1W8c+7gftYP/FxVbGuXg0bFYVME1a7I6gPOS6jevRJs6tOS0u4Z5E0y3wswVZCJrjLM+PRB+DqofEApq0tzfnIbbKk
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:(109105607167333); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7193020); SRVR:AM5PR0701MB2979;
x-ms-traffictypediagnostic: AM5PR0701MB2979:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(82608151540597)(109105607167333)(788757137089)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(11241501184)(806099)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:AM5PR0701MB2979; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2979;
x-forefront-prvs: 06968FD8C4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(376002)(366004)(346002)(39860400002)(396003)(199004)(189003)(236005)(102836004)(186003)(4326008)(26005)(9686003)(66066001)(99286004)(2906002)(54896002)(6916009)(6306002)(55016002)(2900100001)(59450400001)(33656002)(7696005)(76176011)(561944003)(9326002)(6506007)(53546011)(8936002)(106356001)(81166006)(6246003)(81156014)(68736007)(7736002)(105586002)(74316002)(8676002)(345774005)(53936002)(53946003)(478600001)(5660300001)(229853002)(97736004)(86362001)(6116002)(790700001)(3846002)(5250100002)(3660700001)(3280700002)(14454004)(316002)(11346002)(446003)(486006)(93886005)(54906003)(476003)(6436002)(19609705001)(25786009)(559001)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB2979;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: o8yIqbs0zz/mbtyCubyRKXLXf/kb9SwfOxwF0FAd+JhzUFh/fwvX1yH7ONta2We4IbE6OpMzEFskHG9vpI7Dm885WPlrDqmbg3kJdNKltW6sDA3cRKI41gP+cT2klfPIi/VKVsvsCMhqQYPbogCd5J7TyuGpfdUbWHy4bELtQQZHlht/hjtNTOmgXR+isuw8+BgSBMx7f6GUltH/1GDTXqKhAOwM+CRuyiJvAT1bhTw=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB2338ECC38E749ECDB0852A55F1640AM5PR0701MB2338_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: debd7643-1e2c-45b7-34a1-08d5cc747b90
X-MS-Exchange-CrossTenant-Network-Message-Id: debd7643-1e2c-45b7-34a1-08d5cc747b90
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2018 12:45:00.3332 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2979
Archived-At: <>
Subject: Re: [CCAMP] Alarm Module work
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Jun 2018 12:45:12 -0000

Hi Stefan,

Thank you for your feedback.

Please find my replies interleaved with [DDlM]

Kind regards,

From: stefan vallin []
Sent: Wednesday, June 6, 2018 7:31 PM
To: De La Marche, Dirk (Nokia - BE/Antwerp) <>
Cc: NICK HANCOCK <>om>; Common Control and Measurement Plane Discussion List <>
Subject: Re: [CCAMP] Alarm Module work

Hi Dirk!
Thanks for your comments!

On 1 Jun 2018, at 16:11, De La Marche, Dirk (Nokia - BE/Antwerp) <<>> wrote:

Stefan, Nick,

Thank you for this interesting exchange of alarm ideas.

I have two questions related to the extended notification filtering proposal.

(1) In the two examples in this mail exchange the clear of the alarm always happens when the alarm is above the severity threshold line. What if the clear happens below the severity threshold line?  Will we in this case also send an alarm state change notification? Similarly if an alarm stays during its whole lifetime below the severity threshold line, we do not expect any notification, right? Wouldn’t this mean that the alarm application needs to remember the history of the alarm, i.e. whether a notification was once send (e.g. alarm severity was shortly above the severity threshold), in order to generate or not generate a clear notification?
I would imagine that an external alarm manager loses interest in an alarm once it drops below the severity threshold line (as indicated by the T4 notification).Would it still be interested in the notification once it is actually cleared on the box?
I vote on your last comment. Once the severity level drops below the filter level no notifications will be sent including clear notifications.
Above the notification threshold clear will always be sent.
Good comment! I will clarify according to above if you agree.

[DDlM] I agree with your feedback.

(2) if indeed the severity filtering functionality overlaps with the shelving feature, does this mean that the same rules apply to shelved alarms as they apply to severity filtered alarms, i.e. that a clear of the alarm always results in a clear notification? The case I am thinking about is an active alarm that is shelved. There is no notification defined at the moment the alarm is shelved which is inconsistent from an external alarm manager point of view. When the alarm clears while shelved don’t we also need a clear notification? How else will the external alarm manager stay in sync with the box’ alarm situation?
To shelf an alarm implies to ignore the alarm. No notifications will be sent, that is the purpose.
I do not agree that a manager should be able to stay in sync with shelved alarms. Shelved alarms are ignored by purpose.

[DDlM] Does this mean that when an external alarm manager shelves a set of alarms matching a set of configured shelf criteria that it should do its own clean-up (if it wishes to do so) of its own active alarm list and that, when it removes the shelf criteria (i.e. unshelves the set of alarms) that it is responsible to re-build its own active alarm list (if it wishes to do so)? I understand that there will be no notification when an active alarm is transferred from the list of active alarms to the list of shelved alarms (i.e. shelve action)  or when it is taken from the list of shelved alarms and re-inserted in the list of active alarms (i.e. unshelf action). I can understand the clean-up responsibility of the external alarm manager during the shelf action, but the re-building action would always imply a full resync with the active alarm list (even if no active alarms were transferred from the shelved list to the active alarm list).

Based on this mail exchange I would agree that alarm shelving is a workable method that can replace the severity filtering if we can provide a means (e.g. using notifications) to keep the alarm application on both NC server and NC client in sync. In my opinion this is an important criterium to validate any alarm model.
Notification filtering and alarm shelving are two different things.
To shelf an alarm means that alarms associated to the configured resource/alarm-type are ignored. For example a specific interface under test.

[DDlM] I understand and agree with you

Concerning the second proposal, a workable Alarm Severity Assignment Profile is something that is very valuable (since actually used by several, if not all the operators I have worked with). If we can overrule vendor-specific alarm severities on alarm-id and/or on object-id using wildcards we are fine.
Agree, I will probably go with the proposal from Nick, move the profile into the core module, name it alarm-profile and include the severity mapping

[DDlM] I agree!

Thanks again!
Br Stefan

Kind regards,
From: CCAMP [] On Behalf Of stefan vallin
Sent: Thursday, May 31, 2018 9:03 PM
Cc: Common Control and Measurement Plane Discussion List <<>>
Subject: Re: [CCAMP] Alarm Module work

Hi Nick!
Thanks for your comments, really appreciated!

On 31 May 2018, at 18:24, NICK HANCOCK <<>> wrote:

Hi Stefan,

Thanks for sharing this for discussion.

I absolutely agree that it is most important that we can progress the YANG Alarm Module to RFC asap, so that support for it can begin to be implemented in the industry.

1) Extended notification filtering.

The introduction of ‘notify-security-level’ here has one drawback in that it is a global configuration applying to all alarm types and thus does not allow the behaviour to be assigned based on type of resource, such as interface or object. This does not allow you to suppress alarms below a certain severity for some interface types that are not so important, for example, but keep normal alarm behaviour for other more important interfaces.
mmm, we could add resource and alarm type to notification filtering, but then we have alarm shelving and notification filtering as overlapping mechanisms.
I could argue that the manager/client could do the notification filtering.
My experience is that the severity level filtering is of less importance. You normally want to shelf based on resource and alarm type

Also just 'Crossing the specified level' may fulfil the desired behaviour for alarm types with a 1:1 mapping to severity level, but not for alarm types with severity life cycles. if the severity of the alarm continues to increase above the configured severity level, alarm notifications would also need to be sent.
That was the intention, will clarify.

Consider the following example assuming the severity-level is set to ‘major’:
           [(Time, severity, clear)]:
           [(T1, major, -), (T2, critical, -), (T3, major, -), (T4, minor, -), (T5, major), (T6, major, clear)]
I would expect alarm notifications at T1, T2, T3, and T6.
Adding some severity changes to your scenario
[(T1, major, -), (T2, critical, -), (T3, major, -), (T4, minor, -), (T5, warning), (T6, major), (T7, clear)]

Notifications will be sent at T1, T2, T3, T4, T6, T7

Changing this configuration to a choice does have its advantages, such as to allow the addition of other cases later or allow other SDOs or vendors to augment other cases.
So maybe a pragmatic approach so as to not block progress of this draft could be to keep the choice format but omit the ‘notify-security-level’ for now and continue discussions.
Or keep it :)

2) Alarm Severity Assignment Profile

The proposed implementation provides the means to override severities for alarm types with severity life cycles, but at the same time the implementation is relatively simple.
Also the use of a criteria to assign the severity to alarms – and I am assuming that it would work like for the shelf - allows resource-independent overriding of factory default severities through specification of an alarm-type only, but also to add additional overrides for specific resources. The only question is if there are multiple assignments that apply to a specific alarm instance which assignment should apply? For example, if I create an entry for
[(alarm-type-id, alarm-type-id-qualifier, resource, severity-level]
[(los,,,major),(los,,”interface 1”, critical)]
which severity assignment applies to interface 1? The more specific?
Good comment!
Priority order:
1) the more specific
  1.1) resource
  1.2) alarm type (remember hierarchical)
2) order in list

The implementation is also very specific to alarm severity assignment. The mechanism itself, though, is relatively generic, mapping information to alarms, in this case alarm severities. Other SDOs or vendors may wish to augment the list with other data nodes to use this mechanism to associate other data with alarm types and avoid having to implement multiple lists. So I believe that there would be a great advantage and added-value, if this list would be made more generic, such as renaming it to just ‘alarm-profile’, for example.
We are circling back and forth here.
The list has expressed the need to support ITU Alarm Severity Assignment Profile, this is exactly what the suggested model does.

And although it does fulfil the requirements of M.3100/M.3160,
as requested :)

including the list within the module ietf-alarms-itu would basically restrict the use and possible extension of the ASAP to ITU requirements only.
Not sure what you mean with "restrict"

Since possible augmentations could originate from requirements coming from other SDOs and vendors, it would IMHO not be prudent to include it in this module.
Nothing stops augmentations and additions of other features. Just felt there was a high pressure for ASAP which the suggestion captures.

best regards Stefan

Best regards

This message has been classified General Business by NICK HANCOCK on Thursday, 31 May 2018 at 18:24:19.

From: CCAMP [] On Behalf Of stefan vallin
Sent: Monday, May 28, 2018 2:12 PM
To: Common Control and Measurement Plane Discussion List
Subject: [CCAMP] Alarm Module work

Me and Martin are working on an updated version of the alarm module. Several smaller things pointed out by reviewers. Thank you all.

We would like to share 2 things for discussion:
1) Extended notification filtering
2) Alarm Severity Assignment Profile

We are now stretching the limit for being a first core module with only relevant features.
At this point I think it is more important to start having implementation support rather than adding even more features which might scare people of from implementing it.

1) Extended notification filtering
See suggestion below, added the capability to filter on severity.
We did not include resource filtering since that would be too much overlap with shelving.

      choice notify-status-changes {
          "This leaf controls the notifications sent for alarm status
           updates. There are three options:
           1. notifications are sent for all updates, severity level
              changes and alarm text changes
           2. notifications are only sent for alarm raise and clear
           3. notifications are sent for status changes equal to or
              above the specified severity level. Clear notifications
              shall always be sent
              Notifications shall also be sent for state changes that
              makes an alarm less severe than the specified level.
           In option 3, assuming the severity level is set to major,
           and that the alarm has the following state changes
           [(Time, severity, clear)]:
           [(T1, major, -), (T2, minor, -), (T3, warning, -),
            (T4, minor, -), (T5, major), (T6, major, clear)]
           In that case, notifications will be sent at
           T1, T2, T5 and T6";
        leaf notify-all-state-changes {
          type empty;
            "Send notifications for all status changes.";
        leaf notify-raise-and-clear {
          type empty;
            "Send notifications only for raise, clear, and re-raise.
             Notifications for severity level changes or alarm text
             changes are not sent.";
        leaf notify-severity-level {
          type severity;
            "Only send notifications for alarm state changes
             crossing the specified level. Always send clear

2) Alarm Severity Assignment Profile

We have renamed ietf-alarms-x733 to ietf-alarms-itu since it now includes X.733 as well as M.3100/M.3160 features

  list alarm-severity-assignment-profile {
      if-feature alarm-severity-assignment-profile;
      key "alarm-type-id alarm-type-qualifier resource";
      ordered-by user;
        "If an alarm matches the criteria in one of the entries
         in this list the configured severity levels shall be
         used instead of the system default. Note well that the
         mapping allows for several severity levels since this
         alarm module uses a stateful alarm model where
         the same alarm can have the following states:
         [(warning, not cleared),(minor, not cleared),
          (minor, cleared)]

         The configuration of this list shall update the
         /al:alarms/al:alarm-inventory/al:alarm-type list so that a
         client can always get a full picture of the possible alarms
         by reading the alarm inventory. If an alarm matches several
         entries in this list, the first match is used.";
        "M.3160/M.3100 Alarm Severity Assignment Profile, ASAP";
      leaf alarm-type-id {
        type al:alarm-type-id;
          "The alarm type identifier to match for severity
      leaf alarm-type-qualifier {
        type string;
          "A W3C regular expression that is used to match
           an alarm type qualifier.";
      leaf resource {
        type al:resource-match;
          "Specifies which resources to match for severity
      leaf-list severity-levels {
        type al:severity;
        ordered-by user;
          "Specifies the configured severity level(s) for the
           matching alarm. If the alarm has several severity
           levels the leaf-list shall be given in rising severity
           order. The original M3100/M3160 ASAP function only
           allows for a one-to-one mapping between alarm type and
           severity but since the IETF alarm module supports stateful
           alarms the mapping must allow for several severity levels.

           Assume a high-utilisation alarm type with two
           thresholds with the system default severity levels of
           threshold1 = warning and threshold2 = minor. Setting this
           leaf-list to (minor, major) will assign the severity
           levels threshold1 = minor and threshold2 = major";
      leaf description {
        type string;
        mandatory true;
          "A description of the alarm severity profile.";

Stefan Vallin<>