Re: [netmod] 告警草案的两个问题,请光迎帮忙转发给作者咨询下

"Zhengguangying (Walker)" <zhengguangying@huawei.com> Thu, 31 August 2017 01:46 UTC

Return-Path: <zhengguangying@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AFD1204DA for <netmod@ietfa.amsl.com>; Wed, 30 Aug 2017 18:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEiFuk1uoBT0 for <netmod@ietfa.amsl.com>; Wed, 30 Aug 2017 18:46:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 843D712008A for <netmod@ietf.org>; Wed, 30 Aug 2017 18:46:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNQ26744; Thu, 31 Aug 2017 01:46:03 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 31 Aug 2017 02:46:01 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.219]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Thu, 31 Aug 2017 09:45:49 +0800
From: "Zhengguangying (Walker)" <zhengguangying@huawei.com>
To: "stefan@wallan.se" <stefan@wallan.se>, "mbj@tail-f.com" <mbj@tail-f.com>, "netmod@ietf.org" <netmod@ietf.org>
CC: "Zhangjun (Echo, CSD)" <olive.zhangjun@huawei.com>
Thread-Topic: 告警草案的两个问题,请光迎帮忙转发给作者咨询下
Thread-Index: AdMhPjJcmmc5jdtSRiOSfvMqurRiVQAvIQYA
Date: Thu, 31 Aug 2017 01:45:49 +0000
Message-ID: <381D7D55085B1E4D8B581BD652E1E140C91B1D8E@nkgeml513-mbx.china.huawei.com>
References: <096E479692B7D446AFC9FF3AE53CDB558BC01F04@nkgeml513-mbx.china.huawei.com>
In-Reply-To: <096E479692B7D446AFC9FF3AE53CDB558BC01F04@nkgeml513-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.169.155]
Content-Type: multipart/alternative; boundary="_000_381D7D55085B1E4D8B581BD652E1E140C91B1D8Enkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.59A76A5B.012A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.219, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2c3b0719804ddab62e040b42417bd6b5
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/gAh21mFs69WsEdS7w9FffNdDvMo>
Subject: Re: [netmod] 告警草案的两个问题,请光迎帮忙转发给作者咨询下
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2017 01:46:09 -0000

Hi all,

I have read  the “draft-vallin-netmod-alarm-module-02”, we have some comments want to discuss with you all,

https://www.ietf.org/id/draft-vallin-netmod-alarm-module-02.txt

notification alarm-notification {
  description
"This notification is used to report a state change for an
alarm. The same notification is used for reporting a newly
raised alarm, a cleared alarm or changing the text and/or
severity of an existing alarm.";
uses common-alarm-parameters;
uses alarm-state-change-parameters;
}

1. In alarm-notification, I have not find “is-cleared”, how to express alarm  active or cleared ?
2. What is your suggestion for “alarm reason” in alarm-notification or alarm-list? I have not find it in the draft.

Please help to confirm these comments, thanks

Regards
Zhangjun, Walker


 common-alarm-parameters   // Without “is-cleared”,how to express alarm  active or cleared ?
    resource
    alarm-type-id
    alarm-type-qualifier
    alt-resource
    related-alarm*
      resource
      alarm-type-id
      alarm-type-qualifier
    impacted-resource
    root-cause-resource*

 alarm-state-change-parameters  // Without “is-cleared”,how to express alarm is active or cleared ?
    time
    perceived-severity
    alarm-text

Zhangjun
walker