Re: [CCAMP] draft-ietf-ccamp-alarm-module-04/Clause 4.4 Alarm List history

stefan vallin <> Tue, 06 November 2018 07:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 82AB41277C8 for <>; Mon, 5 Nov 2018 23:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Njkfuj42Lq6A for <>; Mon, 5 Nov 2018 23:13:22 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8A44312777C for <>; Mon, 5 Nov 2018 23:13:21 -0800 (PST)
Received: by with SMTP id i26so8063011lfc.0 for <>; Mon, 05 Nov 2018 23:13:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AzVChbYT0rKa56eqNca7zmZv9byNuCbVeLS09uaRlP0=; b=Z91Sl+Vpz319Bo71bLPzMP9/Msy4hurX8qZL3YuMTaJzCC92D5WeABUTdrpSij80oy 7zHaWDAZUU19HNWKwjpvLMVkRGC3E0Ue0w9eaIO+T8mSuhKPqX4OQ085EhALZpFuUGtl 2TzQO/8eadHj1SNt/aUgmJpVMRLJD2k4/PnvCzUzVFRbvtGb6W9d7w6kgGuwB64aZe4r D+SnoFe8cKEggUlmrXaEe7zexgnkMGgZCwBvLPYzMLHFvfLLWZPdp743UP6X2j3o3Vq4 +aufTXzjI93SOYxcp94MO8Tu9uYCy2NK2A8Ey28Zg4aPuAdpprWWqsOMqUeQ9A6SS3S1 U/Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AzVChbYT0rKa56eqNca7zmZv9byNuCbVeLS09uaRlP0=; b=HgY6CI4bolK7BbyoQe2hfc/uKFH1HsvShf4gEWn/pqytwI/J0CQEqLfTcziLMM7WpT 53Epa84bFY3OFZMFQSnnSh4pptTLNOi0KXPG9L96ai7bZJCE5QwLytu/GYG2N3+hROH5 qZzzSwCQVUMaNzKl5EeY9lGC65dflnnFG7QgzqOPdHIeStxb4kXWetiSSrPc8qWmyeyc tv1GJ2qN6VHFvuDyogoowvvpDmukMIinDeteE+yI7ULUB97YJF4ntQs1Vofs4ySPcKhm UeSpYoNqb7d00Spbjol64e9ResTzDe0vccWG/EEsS7QjTjj9Tw15gh3JwHLAtFiBWTcO 74DQ==
X-Gm-Message-State: AGRZ1gK4wEOOtNAyNsnLSGCF1gPgOelw1hHEVZvwVPrf58wEdKZ+ZWmu Y9dknXjtG2MqnGb7GnN3whZ9pw4yZb0=
X-Google-Smtp-Source: AJdET5cajYxy54zYApYeeSRrnUXWOgKloBHfAaEtBsjXvlxSZNtM8p14Gus3uW3a/rzWV6kT2qL+ZQ==
X-Received: by 2002:a19:8f45:: with SMTP id r66mr15494801lfd.9.1541488399437; Mon, 05 Nov 2018 23:13:19 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id q124-v6sm7066138ljb.89.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Nov 2018 23:13:18 -0800 (PST)
From: stefan vallin <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CD5B8EFD-FBBF-4B68-9EB8-3EF8524B4A0A"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 6 Nov 2018 08:12:20 +0100
In-Reply-To: <>
Cc: "" <>
To: Marta Seda <>
References: <>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <>
Subject: Re: [CCAMP] draft-ietf-ccamp-alarm-module-04/Clause 4.4 Alarm List history
X-Mailman-Version: 2.1.29
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: Tue, 06 Nov 2018 07:13:25 -0000

Hi Marta!
Hope the below description helps:

Assume the following alarm notifications:
[time, resource, alarm-type, perceived-severity]

T1, r1, a-t1, warning
T2, r1, a-t1, clear
T3, r1, a-t1, warning
T4, r2, a-t2, warning
T5, r2, a-t2, clear
T6, r2, a-t2, warning
T7, r1, a-t1, clear

I will use the following truncated data-model for the alarm-list to illustrate:
     +--ro alarm* [resource alarm-type-id alarm-type-qualifier]
        +--ro is-cleared                 boolean
        +--ro last-changed               yang:date-and-time
        +--ro perceived-severity         severity
        +--ro status-change* [time]
           +--ro time                    yang:date-and-time
           +--ro perceived-severity      severity-with-clear

The above notifications will result in the following alarm list

alarm[r1, a-t1]
   is-cleared: true
   last-changed: T7
   perceived-severity: warning
     T7, clear
     T3, warning
     T2, clear
     T1, warning
alarm[r2, at-2]
   is-cleared: false
   last-changed: T6
   perceived-severity: warning
      T6, warning
      T5, clear
      T4, warning

The alarm list has two alarms, last changed at T7 and T6.
For each alarm you have the time stamps for the associated notifications.

So in order to get the original list of notifications, the management application
would have to flatten this. And this is by design. From usability perspective it
is not the list of notifcations that matters, it is how they map to the aggregated
alarm state. The operator sees two alarms and their history rather than 7 notifications.

br Stefan

> On 5 Nov 2018, at 17:35, Marta Seda <>; wrote:
> Hello Stefan,
> Some colleagues of mine that have been reviewing “draft-ietf-ccamp-module-04”.   We have a question about the structure used in Clause 4.4 for alarm history:
>   +--ro status-change* [time] {alarm-history}?
>          |  +--ro time                  yang:date-and-time
>          |  +--ro perceived-severity    severity-with-clear
>          |  +--ro alarm-text            alarm-text
> The status-change list has a single time key.
> If you wanted to troubleshoot and look at alarms that occurred during a specific time window (e.g., alarms that occurred in the past between time x and y), how could you do this in the present model?
> Or is the idea that a manager above the NETCONF server would provide that functionality through its own instrumentation? 
> Could you clarify the intent of the model?
> Thanks.
> Marta Seda
> _______________________________________________
> CCAMP mailing list
> <>
> <>