[netmod] FW: a question about ietf-hardware yang module

"Fengchong (frank)" <frank.fengchong@huawei.com> Tue, 25 June 2019 01:59 UTC

Return-Path: <frank.fengchong@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EEE86120223 for <netmod@ietfa.amsl.com>; Mon, 24 Jun 2019 18:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id OIX10k2f9IlJ for <netmod@ietfa.amsl.com>; Mon, 24 Jun 2019 18:59:55 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB502120219 for <netmod@ietf.org>; Mon, 24 Jun 2019 18:59:54 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id C173CF7B207415F18C28 for <netmod@ietf.org>; Tue, 25 Jun 2019 02:59:52 +0100 (IST)
Received: from DGGEMM403-HUB.china.huawei.com ( by lhreml704-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 25 Jun 2019 02:59:46 +0100
Received: from DGGEMM513-MBX.china.huawei.com ([]) by DGGEMM403-HUB.china.huawei.com ([]) with mapi id 14.03.0439.000; Tue, 25 Jun 2019 09:59:18 +0800
From: "Fengchong (frank)" <frank.fengchong@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>, "andy@yumaworks.com" <andy@yumaworks.com>
Thread-Topic: a question about ietf-hardware yang module
Thread-Index: AdUq+YdXGa8CTR9FQVSH0+UgSIb59A==
Date: Tue, 25 Jun 2019 01:59:18 +0000
Message-ID: <5756FB984666AD4BB8E1D63E2E3AA3D001ED25CD@dggemm513-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_5756FB984666AD4BB8E1D63E2E3AA3D001ED25CDdggemm513mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/oDpBE9KIsfVUAJugGnwKHXDb_GA>
Subject: [netmod] FW: a question about ietf-hardware yang module
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Jun 2019 01:59:58 -0000

    Can you clarify this question?

华为技术有限公司 Huawei Technologies Co., Ltd.
手  机:13776612983
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

发件人: Fengchong (frank)
发送时间: 2019年6月19日 10:21
收件人: 'netmod@ietf.org' <netmod@ietf.org>; 'andy@yumaworks.com' <andy@yumaworks.com>
抄送: yanjin (A) <rose.yan@huawei.com>
主题: a question about ietf-hardware yang module

Hi andy and all,
   I’m implementing ietf-hardware.yang, and I have a question about /hardware/last-change.

   module: ietf-hardware
     +--rw hardware
        +--ro last-change?   yang:date-and-time
        +--rw component* [name]
           +--rw name              string
           +--rw class             identityref
           +--ro physical-index?   int32 {entity-mib}?
           +--ro description?      string
           +--rw parent?           -> ../../component/name
           +--rw parent-rel-pos?   int32
           +--ro contains-child*   -> ../../component/name
           +--ro hardware-rev?     string
           +--ro firmware-rev?     string
           +--ro software-rev?     string
           +--ro serial-num?       string
           +--ro mfg-name?         string
           +--ro model-name?       string
           +--rw alias?            string
           +--rw asset-id?         string
           +--ro is-fru?           boolean
           +--ro mfg-date?         yang:date-and-time

           +--rw uri*              inet:uri

           +--ro uuid?             yang:uuid

           +--rw state {hardware-state}?

           |  +--ro state-last-changed?   yang:date-and-time

           |  +--rw admin-state?          admin-state

           |  +--ro oper-state?           oper-state

           |  +--ro usage-state?          usage-state

           |  +--ro alarm-state?          alarm-state

           |  +--ro standby-state?        standby-state

           +--ro sensor-data {hardware-sensor}?

              +--ro value?               sensor-value

              +--ro value-type?          sensor-value-type

              +--ro value-scale?         sensor-value-scale

              +--ro value-precision?     sensor-value-precision

              +--ro oper-status?         sensor-status

              +--ro units-display?       string

              +--ro value-timestamp?     yang:date-and-time

              +--ro value-update-rate?   uint32

Last-change’s description: "The time the '/hardware/component' list changed in the

           operational state.";
It seems this description means any change (configuration change or state change) of list /hardware/component/ will cause the update of /hardware/last-change.

But in description of  notification:hardware-state-change

    notification hardware-state-change {


        "A hardware-state-change notification is generated when the

         value of /hardware/last-change changes in the operational



        "RFC 6933<https://tools.ietf.org/html/rfc6933>: Entity MIB (Version 4) - entConfigChange";


This notification means if any change occurs in /hardware/last-change, a notification will be reported.

This notification also refers to Entity MIB’s entConfigChange.

My question is whether only configuration change of hardware component will cause the update of /hardware/last-change?