<pre>Internet Engineering Task Force (IETF)                        A. Bierman
Request for Comments: 8348                                     YumaWorks
Category: Standards Track                                   M. Bjorklund
ISSN: 2070-1721                                           Tail-f Systems
                                                                 J. Dong
                                                     Huawei Technologies
                                                            D. Romascanu
                                                              March 2018


               <span class="h1">A YANG Data Model for Hardware Management</span>

Abstract

   This document defines a YANG data model for the management of
   hardware on a single server.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc8348">https://www.rfc-editor.org/info/rfc8348</a>.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






<span class="grey">Bierman, et al.              Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
      <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-3">3</a>
      <a href="#section-1.2">1.2</a>. Tree Diagrams ..............................................<a href="#page-3">3</a>
   <a href="#section-2">2</a>. Objectives ......................................................<a href="#page-4">4</a>
   <a href="#section-3">3</a>. Hardware Data Model .............................................<a href="#page-4">4</a>
      <a href="#section-3.1">3.1</a>. The Components Lists .......................................<a href="#page-5">5</a>
   <a href="#section-4">4</a>. Relationship to ENTITY-MIB ......................................<a href="#page-6">6</a>
   <a href="#section-5">5</a>. Relationship to ENTITY-SENSOR-MIB ...............................<a href="#page-8">8</a>
   <a href="#section-6">6</a>. Relationship to ENTITY-STATE-MIB ................................<a href="#page-8">8</a>
   <a href="#section-7">7</a>. Hardware YANG Modules ...........................................<a href="#page-9">9</a>
      <a href="#section-7.1">7.1</a>. "ietf-hardware" Module .....................................<a href="#page-9">9</a>
      <a href="#section-7.2">7.2</a>. "iana-hardware" Module ....................................<a href="#page-34">34</a>
   <a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-38">38</a>
      <a href="#section-8.1">8.1</a>. URI Registrations .........................................<a href="#page-38">38</a>
      <a href="#section-8.2">8.2</a>. YANG Module Registrations .................................<a href="#page-39">39</a>
   <a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-39">39</a>
   <a href="#section-10">10</a>. References ....................................................<a href="#page-40">40</a>
      <a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-40">40</a>
      <a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-41">41</a>
   <a href="#appendix-A">Appendix A</a>.  Hardware State Data Model ............................<a href="#page-42">42</a>
     <a href="#appendix-A.1">A.1</a>.  Hardware State YANG Module ................................<a href="#page-43">43</a>
   Acknowledgments ...................................................<a href="#page-60">60</a>
   Authors' Addresses ................................................<a href="#page-60">60</a>


























<span class="grey">Bierman, et al.              Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   This document defines a YANG data model [<a href="./rfc7950" title="&quot;The YANG 1.1 Data Modeling Language&quot;">RFC7950</a>] for the management
   of hardware on a single server.

   The data model includes configuration and system state (status
   information and counters for the collection of statistics).

   The data model in this document is designed to be compliant with the
   Network Management Datastore Architecture (NMDA) [<a href="./rfc8342" title="&quot;Network Management Datastore Architecture (NMDA)&quot;">RFC8342</a>].  For
   implementations that do not yet support NMDA, a temporary module with
   system state data only is defined in <a href="#appendix-A">Appendix A</a>.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  Terminology</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] [<a href="./rfc8174" title="&quot;Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words&quot;">RFC8174</a>] when, and only when, they appear in all
   capitals, as shown here.

   The following terms are defined in [<a href="./rfc8342" title="&quot;Network Management Datastore Architecture (NMDA)&quot;">RFC8342</a>] and are not redefined
   here:

   o  client

   o  server

   o  configuration

   o  system state

   o  operational state

   o  intended configuration

<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>.  Tree Diagrams</span>

   Tree diagrams used in this document follow the notation defined in
   [<a href="./rfc8340" title="&quot;YANG Tree Diagrams&quot;">RFC8340</a>].











<span class="grey">Bierman, et al.              Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Objectives</span>

   This section describes some of the design objectives for the hardware
   data model.

   o  The hardware data model needs to support many common properties
      used to identify hardware components.

   o  Important information and states about hardware components need to
      be collected from devices that support the hardware data model.

   o  The hardware data model should be suitable for new implementations
      to use as is.

   o  The hardware data model defined in this document can be
      implemented on a system that also implements ENTITY-MIB; thus, the
      mapping between the hardware data model and ENTITY-MIB should be
      clear.

   o  The data model should support pre-provisioning of hardware
      components.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Hardware Data Model</span>

   This document defines the YANG module "ietf-hardware", which has the
   following structure:

   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?           -&gt; ../../component/name
           +--rw parent-rel-pos?   int32
           +--ro contains-child*   -&gt; ../../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



<span class="grey">Bierman, et al.              Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           +--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

     notifications:
       +---n hardware-state-change
       +---n hardware-state-oper-enabled {hardware-state}?
       |  +--ro name?          -&gt; /hardware/component/name
       |  +--ro admin-state?   -&gt; /hardware/component/state/admin-state
       |  +--ro alarm-state?   -&gt; /hardware/component/state/alarm-state
       +---n hardware-state-oper-disabled {hardware-state}?
          +--ro name?          -&gt; /hardware/component/name
          +--ro admin-state?   -&gt; /hardware/component/state/admin-state
          +--ro alarm-state?   -&gt; /hardware/component/state/alarm-state

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  The Components Lists</span>

   The data model for hardware presented in this document uses a flat
   list of components.  Each component in the list is identified by its
   name.  Furthermore, each component has a mandatory "class" leaf.

   The "iana-hardware" module defines YANG identities for the hardware
   types in the IANA-maintained "IANA-ENTITY-MIB" registry.

   The "class" leaf is a YANG identity that describes the type of the
   hardware.  Vendors are encouraged to either directly use one of the
   common IANA-defined identities or derive a more specific identity
   from one of them.








<span class="grey">Bierman, et al.              Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Relationship to ENTITY-MIB</span>

   If the device implements the ENTITY-MIB [<a href="./rfc6933" title="&quot;Entity MIB (Version 4)&quot;">RFC6933</a>], each entry in the
   "/hardware/component" list in the operational state is mapped to one
   EntPhysicalEntry.  Objects that are writable in the MIB are mapped to
   "config true" nodes in the "/hardware/component" list, except
   entPhysicalSerialNum, which is writable in the MIB but "config false"
   in the YANG module.

   The "physical-index" leaf MUST contain the value of the corresponding
   entPhysicalEntry's entPhysicalIndex.

   The "class" leaf is mapped to both entPhysicalClass and
   entPhysicalVendorType.  If the value of the "class" leaf is an
   identity that either is derived from or is one of the identities in
   the "iana-hardware" module, then entPhysicalClass contains the
   corresponding IANAPhysicalClass enumeration value.  Otherwise,
   entPhysicalClass contains the IANAPhysicalClass value "other(1)".
   Vendors are encouraged to define an identity (derived from an
   identity in "iana-hardware" if possible) for each enterprise-specific
   registration identifier used for entPhysicalVendorType and use that
   identity for the "class" leaf.

   The following table lists the YANG data nodes with corresponding
   objects in the ENTITY-MIB.


























<span class="grey">Bierman, et al.              Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


   +--------------------------------+----------------------------------+
   | YANG data node in              | ENTITY-MIB object                |
   | /hardware/component            |                                  |
   +--------------------------------+----------------------------------+
   | name                           | entPhysicalName                  |
   | class                          | entPhysicalClass                 |
   |                                | entPhysicalVendorType            |
   | physical-index                 | entPhysicalIndex                 |
   | description                    | entPhysicalDescr                 |
   | parent                         | entPhysicalContainedIn           |
   | parent-rel-pos                 | entPhysicalParentRelPos          |
   | contains-child                 | entPhysicalChildIndex            |
   | hardware-rev                   | entPhysicalHardwareRev           |
   | firmware-rev                   | entPhysicalFirmwareRev           |
   | software-rev                   | entPhysicalSoftwareRev           |
   | serial-num                     | entPhysicalSerialNum             |
   | mfg-name                       | entPhysicalMfgName               |
   | model-name                     | entPhysicalModelName             |
   | alias                          | entPhysicalAlias                 |
   | asset-id                       | entPhysicalAssetID               |
   | is-fru                         | entPhysicalIsFRU                 |
   | mfg-date                       | entPhysicalMfgDate               |
   | uri                            | entPhysicalUris                  |
   | uuid                           | entPhysicalUUID                  |
   +--------------------------------+----------------------------------+

              YANG Data Nodes and Related ENTITY-MIB Objects
























<span class="grey">Bierman, et al.              Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Relationship to ENTITY-SENSOR-MIB</span>

   If the device implements the ENTITY-SENSOR-MIB [<a href="./rfc3433" title="&quot;Entity Sensor Management Information Base&quot;">RFC3433</a>], each entry
   in the "/hardware/component" list where the container "sensor-data"
   exists is mapped to one EntPhySensorEntry.

   The following table lists the YANG data nodes with corresponding
   objects in the ENTITY-SENSOR-MIB.

   +-------------------------------------+-----------------------------+
   | YANG data node in                   | ENTITY-SENSOR-MIB object    |
   | /hardware/component/sensor-data     |                             |
   +-------------------------------------+-----------------------------+
   | value                               | entPhySensorValue           |
   | value-type                          | entPhySensorType            |
   | value-scale                         | entPhySensorScale           |
   | value-precision                     | entPhySensorPrecision       |
   | oper-status                         | entPhySensorOperStatus      |
   | units-display                       | entPhySensorUnitsDisplay    |
   | value-timestamp                     | entPhySensorValueTimeStamp  |
   | value-update-rate                   | entPhySensorValueUpdateRate |
   +-------------------------------------+-----------------------------+

           YANG Data Nodes and Related ENTITY-SENSOR-MIB Objects

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Relationship to ENTITY-STATE-MIB</span>

   If the device implements the ENTITY-STATE-MIB [<a href="./rfc4268" title="&quot;Entity State MIB&quot;">RFC4268</a>], each entry
   in the "/hardware/component" list where the container "state" exists
   is mapped to one EntStateEntry.

   The following table lists the YANG data nodes with corresponding
   objects in the ENTITY-STATE-MIB.

   +------------------------------------------+------------------------+
   | YANG data node in                        | ENTITY-STATE-MIB       |
   | /hardware/component/state                | object                 |
   +------------------------------------------+------------------------+
   | state-last-changed                       | entStateLastChanged    |
   | admin-state                              | entStateAdmin          |
   | oper-state                               | entStateOper           |
   | usage-state                              | entStateUsage          |
   | alarm-state                              | entStateAlarm          |
   | standby-state                            | entStateStandby        |
   +------------------------------------------+------------------------+

           YANG Data Nodes and Related ENTITY-SENSOR-MIB Objects




<span class="grey">Bierman, et al.              Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Hardware YANG Modules</span>

<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>.  "ietf-hardware" Module</span>

   This YANG module imports typedefs from [<a href="./rfc6991" title="&quot;Common YANG Data Types&quot;">RFC6991</a>].

   &lt;CODE BEGINS&gt; file "ietf-hardware@2018-03-13.yang"

  module ietf-hardware {
    yang-version 1.1;
    namespace "urn:ietf:params:xml:ns:yang:ietf-hardware";
    prefix hw;

    import ietf-inet-types {
      prefix inet;
    }
    import ietf-yang-types {
      prefix yang;
    }
    import iana-hardware {
      prefix ianahw;
    }

    organization
      "IETF NETMOD (Network Modeling) Working Group";

    contact
      "WG Web:   &lt;<a href="https://datatracker.ietf.org/wg/netmod/">https://datatracker.ietf.org/wg/netmod/</a>&gt;
       WG List:  &lt;mailto:netmod@ietf.org&gt;

       Editor:   Andy Bierman
                 &lt;mailto:andy@yumaworks.com&gt;

       Editor:   Martin Bjorklund
                 &lt;mailto:mbj@tail-f.com&gt;

       Editor:   Jie Dong
                 &lt;mailto:jie.dong@huawei.com&gt;

       Editor:   Dan Romascanu
                 &lt;mailto:dromasca@gmail.com&gt;";

    description
      "This module contains a collection of YANG definitions for
       managing hardware.

       This data model is designed for the Network Management Datastore
       Architecture (NMDA) defined in <a href="./rfc8342">RFC 8342</a>.



<span class="grey">Bierman, et al.              Standards Track                    [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


       Copyright (c) 2018 IETF Trust and the persons identified as
       authors of the code.  All rights reserved.

       Redistribution and use in source and binary forms, with or
       without modification, is permitted pursuant to, and subject
       to the license terms contained in, the Simplified BSD License
       set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal Provisions
       Relating to IETF Documents
       (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>).

       This version of this YANG module is part of <a href="./rfc8348">RFC 8348</a>; see
       the RFC itself for full legal notices.";

    revision 2018-03-13 {
      description
        "Initial revision.";
      reference
        "<a href="./rfc8348">RFC 8348</a>: A YANG Data Model for Hardware Management";
    }

    /*
     * Features
     */

    feature entity-mib {
      description
        "This feature indicates that the device implements
         the ENTITY-MIB.";
      reference
        "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4)";
    }

    feature hardware-state {
      description
        "Indicates that ENTITY-STATE-MIB objects are supported";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB";
    }

    feature hardware-sensor {
      description
        "Indicates that ENTITY-SENSOR-MIB objects are supported";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base";
    }

    /*
     * Typedefs



<span class="grey">Bierman, et al.              Standards Track                   [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


     */

    typedef admin-state {
      type enumeration {
        enum unknown {
          value 1;
          description
            "The resource is unable to report administrative state.";
        }
        enum locked {
          value 2;
          description
            "The resource is administratively prohibited from use.";
        }
        enum shutting-down {
          value 3;
          description
            "The resource usage is administratively limited to current
             instances of use.";
        }
        enum unlocked {
          value 4;
          description
            "The resource is not administratively prohibited from
             use.";
        }
      }
      description
        "Represents the various possible administrative states.";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - EntityAdminState";
    }

    typedef oper-state {
      type enumeration {
        enum unknown {
          value 1;
          description
            "The resource is unable to report its operational state.";
        }
        enum disabled {
          value 2;
          description
            "The resource is totally inoperable.";
        }
        enum enabled {
          value 3;




<span class="grey">Bierman, et al.              Standards Track                   [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "The resource is partially or fully operable.";
        }
        enum testing {
          value 4;
          description
            "The resource is currently being tested and cannot
             therefore report whether or not it is operational.";
        }
      }
      description
        "Represents the possible values of operational states.";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - EntityOperState";
    }

    typedef usage-state {
      type enumeration {
        enum unknown {
          value 1;
          description
            "The resource is unable to report usage state.";
        }
        enum idle {
          value 2;
          description
            "The resource is servicing no users.";
        }
        enum active {
          value 3;
          description
            "The resource is currently in use, and it has sufficient
             spare capacity to provide for additional users.";
        }
        enum busy {
          value 4;
          description
            "The resource is currently in use, but it currently has no
             spare capacity to provide for additional users.";
        }
      }
      description
        "Represents the possible values of usage states.";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB -  EntityUsageState";
    }

    typedef alarm-state {



<span class="grey">Bierman, et al.              Standards Track                   [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


      type bits {
        bit unknown {
          position 0;
          description
            "The resource is unable to report alarm state.";
        }
        bit under-repair {
          position 1;
          description
            "The resource is currently being repaired, which, depending
             on the implementation, may make the other values in this
             bit string not meaningful.";
        }
        bit critical {
          position 2;
          description
            "One or more critical alarms are active against the
             resource.";
        }
        bit major {
          position 3;
          description
            "One or more major alarms are active against the
             resource.";
        }
        bit minor {
          position 4;
          description
            "One or more minor alarms are active against the
             resource.";
        }
        bit warning {
          position 5;
          description
            "One or more warning alarms are active against the
             resource.";
        }
        bit indeterminate {
          position 6;
          description
            "One or more alarms of whose perceived severity cannot be
             determined are active against this resource.";
        }
      }
      description
        "Represents the possible values of alarm states.  An alarm is a
         persistent indication of an error or warning condition.




<span class="grey">Bierman, et al.              Standards Track                   [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         When no bits of this attribute are set, then no active alarms
         are known against this component and it is not under repair.";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - EntityAlarmStatus";
    }

    typedef standby-state {
      type enumeration {
        enum unknown {
          value 1;
          description
            "The resource is unable to report standby state.";
        }
        enum hot-standby {
          value 2;
          description
            "The resource is not providing service, but it will be
             immediately able to take over the role of the resource to
             be backed up, without the need for initialization
             activity, and will contain the same information as the
             resource to be backed up.";
        }
        enum cold-standby {
          value 3;
          description
            "The resource is to back up another resource, but it will
             not be immediately able to take over the role of a
             resource to be backed up and will require some
             initialization activity.";
        }
        enum providing-service {
          value 4;
          description
            "The resource is providing service.";
        }
      }
      description
        "Represents the possible values of standby states.";
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - EntityStandbyStatus";
    }

    typedef sensor-value-type {
      type enumeration {
        enum other {
          value 1;
          description
            "A measure other than those listed below.";



<span class="grey">Bierman, et al.              Standards Track                   [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        }
        enum unknown {
          value 2;
          description
            "An unknown measurement or arbitrary, relative numbers";
        }
        enum volts-AC {
          value 3;
          description
            "A measure of electric potential (alternating current).";
        }
        enum volts-DC {
          value 4;
          description
            "A measure of electric potential (direct current).";
        }
        enum amperes {
          value 5;
          description
            "A measure of electric current.";
        }
        enum watts {
          value 6;
          description
            "A measure of power.";
        }
        enum hertz {
          value 7;
          description
            "A measure of frequency.";
        }
        enum celsius {
          value 8;
          description
            "A measure of temperature.";
        }
        enum percent-RH {
          value 9;
          description
            "A measure of percent relative humidity.";
        }
        enum rpm {
          value 10;
          description
            "A measure of shaft revolutions per minute.";
        }
        enum cmm {
          value 11;



<span class="grey">Bierman, et al.              Standards Track                   [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "A measure of cubic meters per minute (airflow).";
        }
        enum truth-value {
          value 12;
          description
            "Value is one of 1 (true) or 2 (false)";
        }
      }
      description
        "A node using this data type represents the sensor measurement
         data type associated with a physical sensor value.  The actual
         data units are determined by examining a node of this type
         together with the associated sensor-value-scale node.

         A node of this type SHOULD be defined together with nodes of
         type sensor-value-scale and type sensor-value-precision.
         These three types are used to identify the semantics of a node
         of type sensor-value.";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                   EntitySensorDataType";
    }

    typedef sensor-value-scale {
      type enumeration {
        enum yocto {
          value 1;
          description
            "Data scaling factor of 10^-24.";
        }
        enum zepto {
          value 2;
          description
            "Data scaling factor of 10^-21.";
        }
        enum atto {
          value 3;
          description
            "Data scaling factor of 10^-18.";
        }
        enum femto {
          value 4;
          description
            "Data scaling factor of 10^-15.";
        }
        enum pico {
          value 5;



<span class="grey">Bierman, et al.              Standards Track                   [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "Data scaling factor of 10^-12.";
        }
        enum nano {
          value 6;
          description
            "Data scaling factor of 10^-9.";
        }
        enum micro {
          value 7;
          description
            "Data scaling factor of 10^-6.";
        }
        enum milli {
          value 8;
          description
            "Data scaling factor of 10^-3.";
        }
        enum units {
          value 9;
          description
            "Data scaling factor of 10^0.";
        }
        enum kilo {
          value 10;
          description
            "Data scaling factor of 10^3.";
        }
        enum mega {
          value 11;
          description
            "Data scaling factor of 10^6.";
        }
        enum giga {
          value 12;
          description
            "Data scaling factor of 10^9.";
        }
        enum tera {
          value 13;
          description
            "Data scaling factor of 10^12.";
        }
        enum peta {
          value 14;
          description
            "Data scaling factor of 10^15.";
        }



<span class="grey">Bierman, et al.              Standards Track                   [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        enum exa {
          value 15;
          description
            "Data scaling factor of 10^18.";
        }
        enum zetta {
          value 16;
          description
            "Data scaling factor of 10^21.";
        }
        enum yotta {
          value 17;
          description
            "Data scaling factor of 10^24.";
        }
      }
      description
        "A node using this data type represents a data scaling factor,
         represented with an International System of Units (SI) prefix.
         The actual data units are determined by examining a node of
         this type together with the associated sensor-value-type.

         A node of this type SHOULD be defined together with nodes of
         type sensor-value-type and type sensor-value-precision.
         Together, associated nodes of these three types are used to
         identify the semantics of a node of type sensor-value.";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                   EntitySensorDataScale";
    }

    typedef sensor-value-precision {
      type int8 {
        range "-8 .. 9";
      }
      description
        "A node using this data type represents a sensor value
         precision range.

         A node of this type SHOULD be defined together with nodes of
         type sensor-value-type and type sensor-value-scale.  Together,
         associated nodes of these three types are used to identify the
         semantics of a node of type sensor-value.

         If a node of this type contains a value in the range 1 to 9,
         it represents the number of decimal places in the fractional
         part of an associated sensor-value fixed-point number.




<span class="grey">Bierman, et al.              Standards Track                   [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         If a node of this type contains a value in the range -8 to -1,
         it represents the number of accurate digits in the associated
         sensor-value fixed-point number.

         The value zero indicates the associated sensor-value node is
         not a fixed-point number.

         Server implementers must choose a value for the associated
         sensor-value-precision node so that the precision and accuracy
         of the associated sensor-value node is correctly indicated.

         For example, a component representing a temperature sensor
         that can measure 0 to 100 degrees C in 0.1 degree
         increments, +/- 0.05 degrees, would have a
         sensor-value-precision value of '1', a sensor-value-scale
         value of 'units', and a sensor-value ranging from '0' to
         '1000'.  The sensor-value would be interpreted as
         'degrees C * 10'.";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                   EntitySensorPrecision";
    }

    typedef sensor-value {
      type int32 {
        range "-1000000000 .. 1000000000";
      }
      description
       "A node using this data type represents a sensor value.

        A node of this type SHOULD be defined together with nodes of
        type sensor-value-type, type sensor-value-scale, and
        type sensor-value-precision.  Together, associated nodes of
        those three types are used to identify the semantics of a node
        of this data type.

        The semantics of a node using this data type are determined by
        the value of the associated sensor-value-type node.

        If the associated sensor-value-type node is equal to 'voltsAC',
        'voltsDC', 'amperes', 'watts', 'hertz', 'celsius', or 'cmm',
        then a node of this type MUST contain a fixed-point number
        ranging from -999,999,999 to +999,999,999.  The value
        -1000000000 indicates an underflow error.  The value
        +1000000000 indicates an overflow error.  The
        sensor-value-precision indicates how many fractional digits
        are represented in the associated sensor-value node.




<span class="grey">Bierman, et al.              Standards Track                   [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        If the associated sensor-value-type node is equal to
        'percentRH', then a node of this type MUST contain a number
        ranging from 0 to 100.

        If the associated sensor-value-type node is equal to 'rpm',
        then a node of this type MUST contain a number ranging from
        -999,999,999 to +999,999,999.

        If the associated sensor-value-type node is equal to
        'truth-value', then a node of this type MUST contain either the
        value 1 (true) or the value 2 (false).

        If the associated sensor-value-type node is equal to 'other' or
        'unknown', then a node of this type MUST contain a number
        ranging from -1000000000 to 1000000000.";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                   EntitySensorValue";
    }

    typedef sensor-status {
      type enumeration {
        enum ok {
          value 1;
          description
            "Indicates that the server can obtain the sensor value.";
        }
        enum unavailable {
          value 2;
          description
            "Indicates that the server presently cannot obtain the
             sensor value.";
        }
        enum nonoperational {
          value 3;
          description
            "Indicates that the server believes the sensor is broken.
             The sensor could have a hard failure (disconnected wire)
             or a soft failure such as out-of-range, jittery, or wildly
             fluctuating readings.";
        }
      }
      description
        "A node using this data type represents the operational status
         of a physical sensor.";
      reference
        "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                   EntitySensorStatus";



<span class="grey">Bierman, et al.              Standards Track                   [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


    }

    /*
     * Data nodes
     */

    container hardware {
      description
        "Data nodes representing components.

         If the server supports configuration of hardware components,
         then this data model is instantiated in the configuration
         datastores supported by the server.  The leaf-list 'datastore'
         for the module 'ietf-hardware' in the YANG library provides
         this information.";

      leaf last-change {
        type yang:date-and-time;
        config false;
        description
          "The time the '/hardware/component' list changed in the
           operational state.";
      }

      list component {
        key name;
        description
          "List of components.

           When the server detects a new hardware component, it
           initializes a list entry in the operational state.

           If the server does not support configuration of hardware
           components, list entries in the operational state are
           initialized with values for all nodes as detected by the
           implementation.

           Otherwise, this procedure is followed:

             1. If there is an entry in the '/hardware/component' list
                in the intended configuration with values for the nodes
                'class', 'parent', and 'parent-rel-pos' that are equal
                to the detected values, then the list entry in the
                operational state is initialized with the configured
                values, including the 'name'.






<span class="grey">Bierman, et al.              Standards Track                   [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


             2. Otherwise (i.e., there is no matching configuration
                entry), the list entry in the operational state is
                initialized with values for all nodes as detected by
                the implementation.

           If the '/hardware/component' list in the intended
           configuration is modified, then the system MUST behave as if
           it re-initializes itself and follow the procedure in (1).";
        reference
          "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalEntry";

        leaf name {
          type string;
          description
            "The name assigned to this component.

             This name is not required to be the same as
             entPhysicalName.";
        }

        leaf class {
          type identityref {
            base ianahw:hardware-class;
          }
          mandatory true;
          description
            "An indication of the general hardware type of the
             component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalClass";
        }

        leaf physical-index {
          if-feature entity-mib;
          type int32 {
            range "1..2147483647";
          }
          config false;
          description
            "The entPhysicalIndex for the entPhysicalEntry represented
             by this list entry.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalIndex";
        }

        leaf description {
          type string;
          config false;



<span class="grey">Bierman, et al.              Standards Track                   [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "A textual description of the component.  This node should
             contain a string that identifies the manufacturer's name
             for the component and should be set to a distinct value
             for each version or model of the component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalDescr";
        }

        leaf parent {
          type leafref {
            path "../../component/name";
            require-instance false;
          }
          description
            "The name of the component that physically contains this
             component.

             If this leaf is not instantiated, it indicates that this
             component is not contained in any other component.

             In the event that a physical component is contained by
             more than one physical component (e.g., double-wide
             modules), this node contains the name of one of these
             components.  An implementation MUST use the same name
             every time this node is instantiated.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalContainedIn";
        }

        leaf parent-rel-pos {
          type int32 {
            range "0 .. 2147483647";
          }
          description
            "An indication of the relative position of this child
             component among all its sibling components.  Sibling
             components are defined as components that:

               o share the same value of the 'parent' node and

               o share a common base identity for the 'class' node.

             Note that the last rule gives implementations flexibility
             in how components are numbered.  For example, some
             implementations might have a single number series for all
             components derived from 'ianahw:port', while some others
             might have different number series for different



<span class="grey">Bierman, et al.              Standards Track                   [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


             components with identities derived from 'ianahw:port' (for
             example, one for registered jack 45 (RJ45) and one for
             small form-factor pluggable (SFP)).";

          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                       entPhysicalParentRelPos";
        }

        leaf-list contains-child {
          type leafref {
            path "../../component/name";
          }
          config false;
          description
            "The name of the contained component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalChildIndex";
        }

        leaf hardware-rev {
          type string;
          config false;
          description
            "The vendor-specific hardware revision string for the
             component.  The preferred value is the hardware revision
             identifier actually printed on the component itself (if
             present).";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                       entPhysicalHardwareRev";
        }

        leaf firmware-rev {
          type string;
          config false;
          description
            "The vendor-specific firmware revision string for the
             component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                       entPhysicalFirmwareRev";
        }

        leaf software-rev {
          type string;
          config false;




<span class="grey">Bierman, et al.              Standards Track                   [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "The vendor-specific software revision string for the
             component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                       entPhysicalSoftwareRev";
        }

        leaf serial-num {
          type string;
          config false;
          description
            "The vendor-specific serial number string for the
             component.  The preferred value is the serial number
             string actually printed on the component itself (if
             present).";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalSerialNum";
        }

        leaf mfg-name {
          type string;
          config false;
          description
            "The name of the manufacturer of this physical component.
             The preferred value is the manufacturer name string
             actually printed on the component itself (if present).

             Note that comparisons between instances of the
             'model-name', 'firmware-rev', 'software-rev', and
             'serial-num' nodes are only meaningful amongst components
             with the same value of 'mfg-name'.

             If the manufacturer name string associated with the
             physical component is unknown to the server, then this
             node is not instantiated.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalMfgName";
        }

        leaf model-name {
          type string;
          config false;
          description
            "The vendor-specific model name identifier string
             associated with this physical component.  The preferred
             value is the customer-visible part number, which may be
             printed on the component itself.



<span class="grey">Bierman, et al.              Standards Track                   [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


             If the model name string associated with the physical
             component is unknown to the server, then this node is not
             instantiated.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalModelName";
        }

        leaf alias {
          type string;
          description
            "An 'alias' name for the component, as specified by a
             network manager, that provides a non-volatile 'handle' for
             the component.

             If no configured value exists, the server MAY set the
             value of this node to a locally unique value in the
             operational state.

             A server implementation MAY map this leaf to the
             entPhysicalAlias MIB object.  Such an implementation needs
             to use some mechanism to handle the differences in size
             and characters allowed between this leaf and
             entPhysicalAlias.  The definition of such a mechanism is
             outside the scope of this document.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalAlias";
        }

        leaf asset-id {
          type string;
          description
            "This node is a user-assigned asset tracking identifier for
             the component.

             A server implementation MAY map this leaf to the
             entPhysicalAssetID MIB object.  Such an implementation
             needs to use some mechanism to handle the differences in
             size and characters allowed between this leaf and
             entPhysicalAssetID.  The definition of such a mechanism is
             outside the scope of this document.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalAssetID";
        }

        leaf is-fru {
          type boolean;
          config false;




<span class="grey">Bierman, et al.              Standards Track                   [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          description
            "This node indicates whether or not this component is
             considered a 'field-replaceable unit' by the vendor.  If
             this node contains the value 'true', then this component
             identifies a field-replaceable unit.  For all components
             that are permanently contained within a field-replaceable
             unit, the value 'false' should be returned for this
             node.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalIsFRU";
        }

        leaf mfg-date {
          type yang:date-and-time;
          config false;
          description
            "The date of manufacturing of the managed component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalMfgDate";
        }

        leaf-list uri {
          type inet:uri;
          description
            "This node contains identification information about the
             component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalUris";
        }

        leaf uuid {
          type yang:uuid;
          config false;
          description
            "A Universally Unique Identifier of the component.";
          reference
            "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalUUID";
        }

        container state {
          if-feature hardware-state;
          description
            "State-related nodes";
          reference
            "<a href="./rfc4268">RFC 4268</a>: Entity State MIB";

          leaf state-last-changed {
            type yang:date-and-time;



<span class="grey">Bierman, et al.              Standards Track                   [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


            config false;
            description
              "The date and time when the value of any of the
               admin-state, oper-state, usage-state, alarm-state, or
               standby-state changed for this component.

               If there has been no change since the last
               re-initialization of the local system, this node
               contains the date and time of local system
               initialization.  If there has been no change since the
               component was added to the local system, this node
               contains the date and time of the insertion.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateLastChanged";
          }

          leaf admin-state {
            type admin-state;
            description
              "The administrative state for this component.

               This node refers to a component's administrative
               permission to service both other components within its
               containment hierarchy as well other users of its
               services defined by means outside the scope of this
               module.

               Some components exhibit only a subset of the remaining
               administrative state values.  Some components cannot be
               locked; hence, this node exhibits only the 'unlocked'
               state.  Other components cannot be shut down gracefully;
               hence, this node does not exhibit the 'shutting-down'
               state.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateAdmin";
          }

          leaf oper-state {
            type oper-state;
            config false;
            description
              "The operational state for this component.

               Note that this node does not follow the administrative
               state.  An administrative state of 'down' does not
               predict an operational state of 'disabled'.





<span class="grey">Bierman, et al.              Standards Track                   [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


               Note that some implementations may not be able to
               accurately report oper-state while the admin-state node
               has a value other than 'unlocked'.  In these cases, this
               node MUST have a value of 'unknown'.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOper";
          }

          leaf usage-state {
            type usage-state;
            config false;
            description
              "The usage state for this component.

               This node refers to a component's ability to service
               more components in a containment hierarchy.

               Some components will exhibit only a subset of the usage
               state values.  Components that are unable to ever
               service any components within a containment hierarchy
               will always have a usage state of 'busy'.  In some
               cases, a component will be able to support only one
               other component within its containment hierarchy and
               will therefore only exhibit values of 'idle' and
               'busy'.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateUsage";
          }

          leaf alarm-state {
            type alarm-state;
            config false;
            description
              "The alarm state for this component.  It does not
               include the alarms raised on child components within its
               containment hierarchy.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateAlarm";
          }

          leaf standby-state {
            type standby-state;
            config false;
            description
              "The standby state for this component.






<span class="grey">Bierman, et al.              Standards Track                   [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


               Some components will exhibit only a subset of the
               remaining standby state values.  If this component
               cannot operate in a standby role, the value of this node
               will always be 'providing-service'.";
            reference
              "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateStandby";
          }
        }

        container sensor-data {
          when 'derived-from-or-self(../class,
                                     "ianahw:sensor")' {
            description
              "Sensor data nodes present for any component of type
               'sensor'";
          }
          if-feature hardware-sensor;
          config false;

          description
            "Sensor-related nodes.";
          reference
            "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base";

          leaf value {
            type sensor-value;
            description
              "The most recent measurement obtained by the server
               for this sensor.

               A client that periodically fetches this node should also
               fetch the nodes 'value-type', 'value-scale', and
               'value-precision', since they may change when the value
               is changed.";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorValue";
          }

          leaf value-type {
            type sensor-value-type;
            description
              "The type of data units associated with the
               sensor value";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorType";
          }



<span class="grey">Bierman, et al.              Standards Track                   [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          leaf value-scale {
            type sensor-value-scale;
            description
              "The (power of 10) scaling factor associated
               with the sensor value";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorScale";
          }

          leaf value-precision {
            type sensor-value-precision;
            description
              "The number of decimal places of precision
               associated with the sensor value";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorPrecision";
          }

          leaf oper-status {
            type sensor-status;
            description
              "The operational status of the sensor.";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorOperStatus";
          }

          leaf units-display {
            type string;
            description
              "A textual description of the data units that should be
               used in the display of the sensor value.";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorUnitsDisplay";
          }

          leaf value-timestamp {
            type yang:date-and-time;
            description
              "The time the status and/or value of this sensor was last
               obtained by the server.";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorValueTimeStamp";
          }



<span class="grey">Bierman, et al.              Standards Track                   [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          leaf value-update-rate {
            type uint32;
            units "milliseconds";
            description
              "An indication of the frequency that the server updates
               the associated 'value' node, represented in
               milliseconds.  The value zero indicates:

                - the sensor value is updated on demand (e.g.,
                  when polled by the server for a get-request),

                - the sensor value is updated when the sensor
                  value changes (event-driven), or

                - the server does not know the update rate.";
            reference
              "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                         entPhySensorValueUpdateRate";
          }
        }
      }
    }

    /*
     * Notifications
     */

    notification hardware-state-change {
      description
        "A hardware-state-change notification is generated when the
         value of /hardware/last-change changes in the operational
         state.";
      reference
        "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entConfigChange";
    }

    notification hardware-state-oper-enabled {
      if-feature hardware-state;
      description
        "A hardware-state-oper-enabled notification signifies that a
         component has transitioned into the 'enabled' state.";

      leaf name {
        type leafref {
          path "/hardware/component/name";
        }





<span class="grey">Bierman, et al.              Standards Track                   [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        description
          "The name of the component that has transitioned into the
           'enabled' state.";
      }
      leaf admin-state {
        type leafref {
          path "/hardware/component/state/admin-state";
        }
        description
          "The administrative state for the component.";
      }
      leaf alarm-state {
        type leafref {
          path "/hardware/component/state/alarm-state";
        }
        description
          "The alarm state for the component.";
      }
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOperEnabled";
    }

    notification hardware-state-oper-disabled {
      if-feature hardware-state;
      description
        "A hardware-state-oper-disabled notification signifies that a
         component has transitioned into the 'disabled' state.";

      leaf name {
        type leafref {
          path "/hardware/component/name";
        }
        description
          "The name of the component that has transitioned into the
           'disabled' state.";
      }
      leaf admin-state {
        type leafref {
          path "/hardware/component/state/admin-state";
        }
        description
          "The administrative state for the component.";
      }
      leaf alarm-state {
        type leafref {
          path "/hardware/component/state/alarm-state";
        }




<span class="grey">Bierman, et al.              Standards Track                   [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        description
          "The alarm state for the component.";
      }
      reference
        "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOperDisabled";
    }

  }

   &lt;CODE ENDS&gt;

<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>.  "iana-hardware" Module</span>

   &lt;CODE BEGINS&gt; file "iana-hardware@2018-03-13.yang"

   module iana-hardware {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:iana-hardware";
     prefix ianahw;

     organization "IANA";
     contact
       "        Internet Assigned Numbers Authority

        Postal: ICANN
                12025 Waterfront Drive, Suite 300
                Los Angeles, CA  90094-2536
                United States of America

        Tel:    +1 310 301 5800
        E-Mail: iana@iana.org&gt;";

     description
       "IANA-defined identities for hardware class.

        The latest revision of this YANG module can be obtained from
        the IANA website.

        Requests for new values should be made to IANA via
        email (iana@iana.org).

        Copyright (c) 2018 IETF Trust and the persons identified as
        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject
        to the license terms contained in, the Simplified BSD License




<span class="grey">Bierman, et al.              Standards Track                   [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>).

        The initial version of this YANG module is part of <a href="./rfc8348">RFC 8348</a>;
        see the RFC itself for full legal notices.";
     reference
       "<a href="https://www.iana.org/assignments/yang-parameters">https://www.iana.org/assignments/yang-parameters</a>";

     revision 2018-03-13 {
       description
         "Initial revision.";
       reference
         "<a href="./rfc8348">RFC 8348</a>: A YANG Data Model for Hardware Management";
     }

     /*
      * Identities
      */

     identity hardware-class {
       description
         "This identity is the base for all hardware class
          identifiers.";
     }

     identity unknown {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is unknown
          to the server.";
     }

     identity chassis {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is an
          overall container for networking equipment.  Any class of
          physical component, except a stack, may be contained within a
          chassis; a chassis may only be contained within a stack.";
     }

     identity backplane {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of device for aggregating and forwarding networking traffic,
          such as a shared backplane in a modular ethernet switch.  Note



<span class="grey">Bierman, et al.              Standards Track                   [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          that an implementation may model a backplane as a single
          physical component, which is actually implemented as multiple
          discrete physical components (within a chassis or stack).";
     }

     identity container {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is capable
          of containing one or more removable physical entities,
          possibly of different types.  For example, each (empty or
          full) slot in a chassis will be modeled as a container.  Note
          that all removable physical components should be modeled
          within a container component, such as field-replaceable
          modules, fans, or power supplies.  Note that all known
          containers should be modeled by the agent, including empty
          containers.";
     }

     identity power-supply {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is a
          power-supplying component.";
     }

     identity fan {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is a fan or
          other heat-reduction component.";
     }

     identity sensor {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of sensor, such as a temperature sensor within a router
          chassis.";
     }

     identity module {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of self-contained sub-system.  If a module component is
          removable, then it should be modeled within a container




<span class="grey">Bierman, et al.              Standards Track                   [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


          component; otherwise, it should be modeled directly within
          another physical component (e.g., a chassis or another
          module).";
     }

     identity port {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of networking port capable of receiving and/or transmitting
          networking traffic.";
     }

     identity stack {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of super-container (possibly virtual) intended to group
          together multiple chassis entities.  A stack may be realized
          by a virtual cable, a real interconnect cable attached to
          multiple chassis, or multiple interconnect cables.  A stack
          should not be modeled within any other physical components,
          but a stack may be contained within another stack.  Only
          chassis components should be contained within a stack.";
     }

     identity cpu {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of central processing unit.";
     }

     identity energy-object {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of energy object, i.e., it is a piece of equipment that is
          part of or attached to a communications network that is
          monitored, it is controlled, or it aids in the management of
          another device for Energy Management.";
     }

     identity battery {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of battery.";



<span class="grey">Bierman, et al.              Standards Track                   [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


     }

     identity storage-drive {
       base ianahw:hardware-class;
       description
         "This identity is applicable if the hardware class is some sort
          of component with data storage capability as its main
          functionality, e.g., hard disk drive (HDD), solid-state device
          (SSD), solid-state hybrid drive (SSHD), object storage device
          (OSD), or other.";
     }
   }

   &lt;CODE ENDS&gt;

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  IANA Considerations</span>

   This document defines the initial version of the IANA-maintained
   "iana-hardware" YANG module.

   The "iana-hardware" YANG module is intended to reflect the
   "IANA-ENTITY-MIB" MIB module so that if a new enumeration is added to
   the "IANAPhysicalClass" textual convention, the same class is added
   as an identity derived from "ianahw:hardware-class".

   When the "iana-hardware" YANG module is updated, a new "revision"
   statement must be added in front of the existing revision statements.

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  URI Registrations</span>

   This document registers three URIs in the "IETF XML Registry"
   [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].  Per the format in <a href="./rfc3688">RFC 3688</a>, the following registrations
   have been made.

     URI: urn:ietf:params:xml:ns:yang:iana-hardware
     Registrant Contact: The IESG.
     XML: N/A, the requested URI is an XML namespace.

     URI: urn:ietf:params:xml:ns:yang:ietf-hardware
     Registrant Contact: The IESG.
     XML: N/A, the requested URI is an XML namespace.

     URI: urn:ietf:params:xml:ns:yang:ietf-hardware-state
     Registrant Contact: The IESG.
     XML: N/A, the requested URI is an XML namespace.






<span class="grey">Bierman, et al.              Standards Track                   [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  YANG Module Registrations</span>

   This document registers three YANG modules in the "YANG Module Names"
   registry [<a href="./rfc6020" title="&quot;YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)&quot;">RFC6020</a>].

     name:         iana-hardware
     namespace:    urn:ietf:params:xml:ns:yang:iana-hardware
     prefix:       ianahw
     reference:    <a href="./rfc8348">RFC 8348</a>

     name:         ietf-hardware
     namespace:    urn:ietf:params:xml:ns:yang:ietf-hardware
     prefix:       hw
     reference:    <a href="./rfc8348">RFC 8348</a>

     name:         ietf-hardware-state
     namespace:    urn:ietf:params:xml:ns:yang:ietf-hardware-state
     prefix:       hw-state
     reference:    <a href="./rfc8348">RFC 8348</a>

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Security Considerations</span>

   The YANG modules specified in this document define a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF [<a href="./rfc6241" title="&quot;Network Configuration Protocol (NETCONF)&quot;">RFC6241</a>] or RESTCONF [<a href="./rfc8040" title="&quot;RESTCONF Protocol&quot;">RFC8040</a>].  The lowest NETCONF layer
   is the secure transport layer, and the mandatory-to-implement secure
   transport is Secure Shell (SSH) [<a href="./rfc6242" title="&quot;Using the NETCONF Protocol over Secure Shell (SSH)&quot;">RFC6242</a>].  The lowest RESTCONF layer
   is HTTPS, and the mandatory-to-implement secure transport is TLS
   [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>].

   The NETCONF access control model [<a href="./rfc8341" title="&quot;Network Configuration Access Control Model&quot;">RFC8341</a>] provides the means to
   restrict access for particular NETCONF or RESTCONF users to a
   preconfigured subset of all available NETCONF or RESTCONF protocol
   operations and content.

   There are a number of data nodes defined in the YANG module
   "ietf-hardware" that are writable/creatable/deletable (i.e., config
   true, which is the default).  These data nodes may be considered
   sensitive or vulnerable in some network environments.  Write
   operations (e.g., edit-config) to these data nodes without proper
   protection can have a negative effect on network operations.  These
   are the subtrees and data nodes and their sensitivity/vulnerability:

   /hardware/component/admin-state:  Setting this node to 'locked' or
      'shutting-down' can cause disruption of services ranging from
      those running on a port to those on an entire device, depending on
      the type of component.




<span class="grey">Bierman, et al.              Standards Track                   [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


   Some of the readable data nodes in these YANG modules may be
   considered sensitive or vulnerable in some network environments.  It
   is thus important to control read access (e.g., via get, get-config,
   or notification) to these data nodes.  These are the subtrees and
   data nodes and their sensitivity/vulnerability:

   /hardware/component:  The leafs in this list expose information about
      the physical components in a device, which may be used to identify
      the vendor, model, version, and specific device-identification
      information of each system component.

   /hardware/component/sensor-data/value:  This node may expose the
      values of particular physical sensors in a device.

   /hardware/component/state:  Access to this node allows one to figure
      out what the active and standby resources in a device are.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  References</span>

<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
              DOI 10.17487/RFC2119, March 1997,
              &lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;.

   [<a id="ref-RFC3433">RFC3433</a>]  Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor
              Management Information Base", <a href="./rfc3433">RFC 3433</a>,
              DOI 10.17487/RFC3433, December 2002,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3433">https://www.rfc-editor.org/info/rfc3433</a>&gt;.

   [<a id="ref-RFC3688">RFC3688</a>]  Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
              DOI 10.17487/RFC3688, January 2004,
              &lt;<a href="https://www.rfc-editor.org/info/rfc3688">https://www.rfc-editor.org/info/rfc3688</a>&gt;.

   [<a id="ref-RFC4268">RFC4268</a>]  Chisholm, S. and D. Perkins, "Entity State MIB", <a href="./rfc4268">RFC 4268</a>,
              DOI 10.17487/RFC4268, November 2005,
              &lt;<a href="https://www.rfc-editor.org/info/rfc4268">https://www.rfc-editor.org/info/rfc4268</a>&gt;.

   [<a id="ref-RFC5246">RFC5246</a>]  Dierks, T. and E. Rescorla, "The Transport Layer Security
              (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
              DOI 10.17487/RFC5246, August 2008,
              &lt;<a href="https://www.rfc-editor.org/info/rfc5246">https://www.rfc-editor.org/info/rfc5246</a>&gt;.

   [<a id="ref-RFC6020">RFC6020</a>]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", <a href="./rfc6020">RFC 6020</a>,
              DOI 10.17487/RFC6020, October 2010,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6020">https://www.rfc-editor.org/info/rfc6020</a>&gt;.



<span class="grey">Bierman, et al.              Standards Track                   [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


   [<a id="ref-RFC6241">RFC6241</a>]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", <a href="./rfc6241">RFC 6241</a>, DOI 10.17487/RFC6241, June 2011,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6241">https://www.rfc-editor.org/info/rfc6241</a>&gt;.

   [<a id="ref-RFC6242">RFC6242</a>]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", <a href="./rfc6242">RFC 6242</a>, DOI 10.17487/RFC6242, June 2011,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6242">https://www.rfc-editor.org/info/rfc6242</a>&gt;.

   [<a id="ref-RFC6933">RFC6933</a>]  Bierman, A., Romascanu, D., Quittek, J., and M.
              Chandramouli, "Entity MIB (Version 4)", <a href="./rfc6933">RFC 6933</a>,
              DOI 10.17487/RFC6933, May 2013,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6933">https://www.rfc-editor.org/info/rfc6933</a>&gt;.

   [<a id="ref-RFC6991">RFC6991</a>]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              <a href="./rfc6991">RFC 6991</a>, DOI 10.17487/RFC6991, July 2013,
              &lt;<a href="https://www.rfc-editor.org/info/rfc6991">https://www.rfc-editor.org/info/rfc6991</a>&gt;.

   [<a id="ref-RFC7950">RFC7950</a>]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              <a href="./rfc7950">RFC 7950</a>, DOI 10.17487/RFC7950, August 2016,
              &lt;<a href="https://www.rfc-editor.org/info/rfc7950">https://www.rfc-editor.org/info/rfc7950</a>&gt;.

   [<a id="ref-RFC8040">RFC8040</a>]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", <a href="./rfc8040">RFC 8040</a>, DOI 10.17487/RFC8040, January 2017,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8040">https://www.rfc-editor.org/info/rfc8040</a>&gt;.

   [<a id="ref-RFC8174">RFC8174</a>]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
              <a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
              May 2017, &lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;.

   [<a id="ref-RFC8341">RFC8341</a>]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, <a href="./rfc8341">RFC 8341</a>,
              DOI 10.17487/RFC8341, March 2018,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8341">https://www.rfc-editor.org/info/rfc8341</a>&gt;.

   [<a id="ref-RFC8342">RFC8342</a>]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
              and R. Wilton, "Network Management Datastore Architecture
              (NMDA)", <a href="./rfc8342">RFC 8342</a>, DOI 10.17487/RFC8342, March 2018,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8342">https://www.rfc-editor.org/info/rfc8342</a>&gt;.

<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>.  Informative References</span>

   [<a id="ref-RFC8340">RFC8340</a>]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
              <a href="https://www.rfc-editor.org/bcp/bcp215">BCP 215</a>, <a href="./rfc8340">RFC 8340</a>, DOI 10.17487/RFC8340, March 2018,
              &lt;<a href="https://www.rfc-editor.org/info/rfc8340">https://www.rfc-editor.org/info/rfc8340</a>&gt;.






<span class="grey">Bierman, et al.              Standards Track                   [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Hardware State Data Model</span>

   This non-normative appendix contains a data model designed as a
   temporary solution for implementations that do not yet support the
   Network Management Datastore Architecture (NMDA) defined in
   [<a href="./rfc8342" title="&quot;Network Management Datastore Architecture (NMDA)&quot;">RFC8342</a>].  It has the following structure:

   module: ietf-hardware-state
     x--ro hardware
        x--ro last-change?   yang:date-and-time
        x--ro component* [name]
           x--ro name              string
           x--ro class             identityref
           x--ro physical-index?   int32 {entity-mib}?
           x--ro description?      string
           x--ro parent?           -&gt; ../../component/name
           x--ro parent-rel-pos?   int32
           x--ro contains-child*   -&gt; ../../component/name
           x--ro hardware-rev?     string
           x--ro firmware-rev?     string
           x--ro software-rev?     string
           x--ro serial-num?       string
           x--ro mfg-name?         string
           x--ro model-name?       string
           x--ro alias?            string
           x--ro asset-id?         string
           x--ro is-fru?           boolean
           x--ro mfg-date?         yang:date-and-time
           x--ro uri*              inet:uri
           x--ro uuid?             yang:uuid
           x--ro state {hardware-state}?
           |  x--ro state-last-changed?   yang:date-and-time
           |  x--ro admin-state?          hw:admin-state
           |  x--ro oper-state?           hw:oper-state
           |  x--ro usage-state?          hw:usage-state
           |  x--ro alarm-state?          hw:alarm-state
           |  x--ro standby-state?        hw:standby-state
           x--ro sensor-data {hardware-sensor}?
              x--ro value?               hw:sensor-value
              x--ro value-type?          hw:sensor-value-type
              x--ro value-scale?         hw:sensor-value-scale
              x--ro value-precision?     hw:sensor-value-precision
              x--ro oper-status?         hw:sensor-status
              x--ro units-display?       string
              x--ro value-timestamp?     yang:date-and-time
              x--ro value-update-rate?   uint32





<span class="grey">Bierman, et al.              Standards Track                   [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


     notifications:
       x---n hardware-state-change
       x---n hardware-state-oper-enabled {hardware-state}?
       |  x--ro name?          -&gt; /hardware/component/name
       |  x--ro admin-state?   -&gt; /hardware/component/state/admin-state
       |  x--ro alarm-state?   -&gt; /hardware/component/state/alarm-state
       x---n hardware-state-oper-disabled {hardware-state}?
          x--ro name?          -&gt; /hardware/component/name
          x--ro admin-state?   -&gt; /hardware/component/state/admin-state
          x--ro alarm-state?   -&gt; /hardware/component/state/alarm-state

<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>.  Hardware State YANG Module</span>

   &lt;CODE BEGINS&gt; file "ietf-hardware-state@2018-03-13.yang"

   module ietf-hardware-state {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-hardware-state";
     prefix hw-state;

     import ietf-inet-types {
       prefix inet;
     }
     import ietf-yang-types {
       prefix yang;
     }
     import iana-hardware {
       prefix ianahw;
     }
     import ietf-hardware {
       prefix hw;
     }

     organization
       "IETF NETMOD (Network Modeling) Working Group";

     contact
       "WG Web:   &lt;<a href="https://datatracker.ietf.org/wg/netmod/">https://datatracker.ietf.org/wg/netmod/</a>&gt;
        WG List:  &lt;mailto:netmod@ietf.org&gt;

        Editor:   Andy Bierman
                  &lt;mailto:andy@yumaworks.com&gt;

        Editor:   Martin Bjorklund
                  &lt;mailto:mbj@tail-f.com&gt;

        Editor:   Jie Dong
                  &lt;mailto:jie.dong@huawei.com&gt;



<span class="grey">Bierman, et al.              Standards Track                   [Page 43]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


        Editor:   Dan Romascanu
                  &lt;mailto:dromasca@gmail.com&gt;";

     description
       "This module contains a collection of YANG definitions for
        monitoring hardware.

        This data model is designed as a temporary solution for
        implementations that do not yet support the Network Management
        Datastore Architecture (NMDA) defined in <a href="./rfc8342">RFC 8342</a>.  Such an
        implementation cannot implement the module 'ietf-hardware'
        properly, since without NMDA support, it is not possible to
        distinguish between instances of nodes in the running
        configuration and operational states.

        The data model in this module is the same as the data model in
        'ietf-hardware', except all nodes are marked as 'config false'.

        If a server that implements this module but doesn't support NMDA
        also supports configuration of hardware components, it SHOULD
        also implement the module 'ietf-hardware' in the configuration
        datastores.  The corresponding state data is found in the
        '/hw-state:hardware' subtree.

        Copyright (c) 2018 IETF Trust and the persons identified as
        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject
        to the license terms contained in, the Simplified BSD License
        set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>).

        This version of this YANG module is part of <a href="./rfc8348">RFC 8348</a>; see
        the RFC itself for full legal notices.";

     revision 2018-03-13 {
       description
         "Initial revision.";
       reference
         "<a href="./rfc8348">RFC 8348</a>: A YANG Data Model for Hardware Management";
     }

     /*
      * Features
      */




<span class="grey">Bierman, et al.              Standards Track                   [Page 44]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


     feature entity-mib {
       status deprecated;
       description
         "This feature indicates that the device implements
          the ENTITY-MIB.";
       reference
         "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4)";
     }

     feature hardware-state {
       status deprecated;
       description
         "Indicates that ENTITY-STATE-MIB objects are supported";
       reference
         "<a href="./rfc4268">RFC 4268</a>: Entity State MIB";
     }

     feature hardware-sensor {
       status deprecated;
       description
         "Indicates that ENTITY-SENSOR-MIB objects are supported";
       reference
         "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base";
     }

     /*
      * Data nodes
      */

     container hardware {
       config false;
       status deprecated;
       description
         "Data nodes representing components.";

       leaf last-change {
         type yang:date-and-time;
         status deprecated;
         description
           "The time the '/hardware/component' list changed in the
            operational state.";
       }

       list component {
         key name;
         status deprecated;
         description
           "List of components.



<span class="grey">Bierman, et al.              Standards Track                   [Page 45]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


            When the server detects a new hardware component, it
            initializes a list entry in the operational state.

            If the server does not support configuration of hardware
            components, list entries in the operational state are
            initialized with values for all nodes as detected by the
            implementation.

            Otherwise, this procedure is followed:

              1. If there is an entry in the '/hardware/component' list
                 in the intended configuration with values for the nodes
                 'class', 'parent', and 'parent-rel-pos' that are equal
                 to the detected values, then:

              1a. If the configured entry has a value for 'mfg-name'
                  that is equal to the detected value or if the
                  'mfg-name' value cannot be detected, then the list
                  entry in the operational state is initialized with the
                  configured values for all configured nodes, including
                  the 'name'.

                  Otherwise, the list entry in the operational state is
                  initialized with values for all nodes as detected by
                  the implementation.  The implementation may raise an
                  alarm that informs about the 'mfg-name' mismatch
                  condition.  How this is done is outside the scope of
                  this document.

              1b. Otherwise (i.e., there is no matching configuration
                  entry), the list entry in the operational state is
                  initialized with values for all nodes as detected by
                  the implementation.

            If the '/hardware/component' list in the intended
            configuration is modified, then the system MUST behave as if
            it re-initializes itself and follow the procedure in (1).";
         reference
           "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalEntry";

         leaf name {
           type string;
           status deprecated;
           description
             "The name assigned to this component.

              This name is not required to be the same as
              entPhysicalName.";



<span class="grey">Bierman, et al.              Standards Track                   [Page 46]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         }

         leaf class {
           type identityref {
             base ianahw:hardware-class;
           }
           mandatory true;
           status deprecated;
           description
             "An indication of the general hardware type of the
              component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalClass";
         }

         leaf physical-index {
           if-feature entity-mib;
           type int32 {
             range "1..2147483647";
           }
           status deprecated;
           description
             "The entPhysicalIndex for the entPhysicalEntry represented
              by this list entry.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalIndex";
         }

         leaf description {
           type string;
           status deprecated;
           description
             "A textual description of the component.  This node should
              contain a string that identifies the manufacturer's name
              for the component and should be set to a distinct value
              for each version or model of the component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalDescr";
         }

         leaf parent {
           type leafref {
             path "../../component/name";
             require-instance false;
           }
           status deprecated;





<span class="grey">Bierman, et al.              Standards Track                   [Page 47]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           description
             "The name of the component that physically contains this
              component.

              If this leaf is not instantiated, it indicates that this
              component is not contained in any other component.

              In the event that a physical component is contained by
              more than one physical component (e.g., double-wide
              modules), this node contains the name of one of these
              components.  An implementation MUST use the same name
              every time this node is instantiated.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                        entPhysicalContainedIn";
         }

         leaf parent-rel-pos {
           type int32 {
             range "0 .. 2147483647";
           }
           status deprecated;
           description
             "An indication of the relative position of this child
              component among all its sibling components.  Sibling
              components are defined as components that:

                o share the same value of the 'parent' node and

                o share a common base identity for the 'class' node.

              Note that the last rule gives implementations flexibility
              in how components are numbered.  For example, some
              implementations might have a single number series for all
              components derived from 'ianahw:port', while some others
              might have different number series for different
              components with identities derived from 'ianahw:port' (for
              example, one for RJ45 and one for SFP).";

           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                        entPhysicalParentRelPos";
         }

         leaf-list contains-child {
           type leafref {
             path "../../component/name";
           }



<span class="grey">Bierman, et al.              Standards Track                   [Page 48]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           status deprecated;
           description
             "The name of the contained component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalChildIndex";
         }

         leaf hardware-rev {
           type string;
           status deprecated;
           description
             "The vendor-specific hardware revision string for the
              component.  The preferred value is the hardware revision
              identifier actually printed on the component itself (if
              present).";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                        entPhysicalHardwareRev";
         }

         leaf firmware-rev {
           type string;
           status deprecated;
           description
             "The vendor-specific firmware revision string for the
              component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                        entPhysicalFirmwareRev";
         }

         leaf software-rev {
           type string;
           status deprecated;
           description
             "The vendor-specific software revision string for the
              component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) -
                        entPhysicalSoftwareRev";
         }

         leaf serial-num {
           type string;
           status deprecated;






<span class="grey">Bierman, et al.              Standards Track                   [Page 49]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           description
             "The vendor-specific serial number string for the
              component.  The preferred value is the serial number
              string actually printed on the component itself (if
              present).";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalSerialNum";
         }

         leaf mfg-name {
           type string;
           status deprecated;
           description
             "The name of the manufacturer of this physical component.
              The preferred value is the manufacturer name string
              actually printed on the component itself (if present).

              Note that comparisons between instances of the
              'model-name', 'firmware-rev', 'software-rev', and
              'serial-num' nodes are only meaningful amongst components
              with the same value of 'mfg-name'.

              If the manufacturer name string associated with the
              physical component is unknown to the server, then this
              node is not instantiated.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalMfgName";
         }

         leaf model-name {
           type string;
           status deprecated;
           description
             "The vendor-specific model name identifier string
              associated with this physical component.  The preferred
              value is the customer-visible part number, which may be
              printed on the component itself.

              If the model name string associated with the physical
              component is unknown to the server, then this node is not
              instantiated.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalModelName";
         }

         leaf alias {
           type string;
           status deprecated;



<span class="grey">Bierman, et al.              Standards Track                   [Page 50]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           description
             "An 'alias' name for the component, as specified by a
              network manager, that provides a non-volatile 'handle' for
              the component.

              If no configured value exists, the server MAY set the
              value of this node to a locally unique value in the
              operational state.

              A server implementation MAY map this leaf to the
              entPhysicalAlias MIB object.  Such an implementation needs
              to use some mechanism to handle the differences in size
              and characters allowed between this leaf and
              entPhysicalAlias.  The definition of such a mechanism is
              outside the scope of this document.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalAlias";
         }

         leaf asset-id {
           type string;
           status deprecated;
           description
             "This node is a user-assigned asset tracking identifier for
              the component.

              A server implementation MAY map this leaf to the
              entPhysicalAssetID MIB object.  Such an implementation
              needs to use some mechanism to handle the differences in
              size and characters allowed between this leaf and
              entPhysicalAssetID.  The definition of such a mechanism is
              outside the scope of this document.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalAssetID";
         }

         leaf is-fru {
           type boolean;
           status deprecated;
           description
             "This node indicates whether or not this component is
              considered a 'field-replaceable unit' by the vendor.  If
              this node contains the value 'true', then this component
              identifies a field-replaceable unit.  For all components
              that are permanently contained within a field-replaceable
              unit, the value 'false' should be returned for this
              node.";




<span class="grey">Bierman, et al.              Standards Track                   [Page 51]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalIsFRU";
         }

         leaf mfg-date {
           type yang:date-and-time;
           status deprecated;
           description
             "The date of manufacturing of the managed component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalMfgDate";
         }

         leaf-list uri {
           type inet:uri;
           status deprecated;
           description
             "This node contains identification information about the
              component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalUris";
         }

         leaf uuid {
           type yang:uuid;
           status deprecated;
           description
             "A Universally Unique Identifier of the component.";
           reference
             "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entPhysicalUUID";
         }

         container state {
           if-feature hardware-state;
           status deprecated;
           description
             "State-related nodes";
           reference
             "<a href="./rfc4268">RFC 4268</a>: Entity State MIB";

           leaf state-last-changed {
             type yang:date-and-time;
             status deprecated;
             description
               "The date and time when the value of any of the
                admin-state, oper-state, usage-state, alarm-state, or
                standby-state changed for this component.




<span class="grey">Bierman, et al.              Standards Track                   [Page 52]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


                If there has been no change since the last
                re-initialization of the local system, this node
                contains the date and time of local system
                initialization.  If there has been no change since the
                component was added to the local system, this node
                contains the date and time of the insertion.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateLastChanged";
           }

           leaf admin-state {
             type hw:admin-state;
             status deprecated;
             description
               "The administrative state for this component.

                This node refers to a component's administrative
                permission to service both other components within its
                containment hierarchy as well as other users of its
                services defined by means outside the scope of this
                module.

                Some components exhibit only a subset of the remaining
                administrative state values.  Some components cannot be
                locked; hence, this node exhibits only the 'unlocked'
                state.  Other components cannot be shut down gracefully;
                hence, this node does not exhibit the 'shutting-down'
                state.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateAdmin";
           }

           leaf oper-state {
             type hw:oper-state;
             status deprecated;
             description
               "The operational state for this component.

                Note that this node does not follow the administrative
                state.  An administrative state of 'down' does not
                predict an operational state of 'disabled'.

                Note that some implementations may not be able to
                accurately report oper-state while the admin-state node
                has a value other than 'unlocked'.  In these cases, this
                node MUST have a value of 'unknown'.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOper";



<span class="grey">Bierman, et al.              Standards Track                   [Page 53]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           }

           leaf usage-state {
             type hw:usage-state;
             status deprecated;
             description
               "The usage state for this component.

                This node refers to a component's ability to service
                more components in a containment hierarchy.

                Some components will exhibit only a subset of the usage
                state values.  Components that are unable to ever
                service any components within a containment hierarchy
                will always have a usage state of 'busy'.  In some
                cases, a component will be able to support only one
                other component within its containment hierarchy and
                will therefore only exhibit values of 'idle' and
                'busy'.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateUsage";
           }

           leaf alarm-state {
             type hw:alarm-state;
             status deprecated;
             description
               "The alarm state for this component.  It does not
                include the alarms raised on child components within its
                containment hierarchy.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateAlarm";
           }

           leaf standby-state {
             type hw:standby-state;
             status deprecated;
             description
               "The standby state for this component.

                Some components will exhibit only a subset of the
                remaining standby state values.  If this component
                cannot operate in a standby role, the value of this node
                will always be 'providing-service'.";
             reference
               "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateStandby";
           }
         }



<span class="grey">Bierman, et al.              Standards Track                   [Page 54]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         container sensor-data {
           when 'derived-from-or-self(../class,
                                      "ianahw:sensor")' {
             description
               "Sensor data nodes present for any component of type
                'sensor'";
           }
           if-feature hardware-sensor;
           status deprecated;

           description
             "Sensor-related nodes.";
           reference
             "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base";

           leaf value {
             type hw:sensor-value;
             status deprecated;
             description
               "The most recent measurement obtained by the server
                for this sensor.

                A client that periodically fetches this node should also
                fetch the nodes 'value-type', 'value-scale', and
                'value-precision', since they may change when the value
                is changed.";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorValue";
           }

           leaf value-type {
             type hw:sensor-value-type;
             status deprecated;
             description
               "The type of data units associated with the
                sensor value";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorType";
           }

           leaf value-scale {
             type hw:sensor-value-scale;
             status deprecated;
             description
               "The (power of 10) scaling factor associated
                with the sensor value";



<span class="grey">Bierman, et al.              Standards Track                   [Page 55]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorScale";
           }

           leaf value-precision {
             type hw:sensor-value-precision;
             status deprecated;
             description
               "The number of decimal places of precision
                associated with the sensor value";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorPrecision";
           }

           leaf oper-status {
             type hw:sensor-status;
             status deprecated;
             description
               "The operational status of the sensor.";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorOperStatus";
           }

           leaf units-display {
             type string;
             status deprecated;
             description
               "A textual description of the data units that should be
                used in the display of the sensor value.";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorUnitsDisplay";
           }

           leaf value-timestamp {
             type yang:date-and-time;
             status deprecated;
             description
               "The time the status and/or value of this sensor was last
                obtained by the server.";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorValueTimeStamp";
           }




<span class="grey">Bierman, et al.              Standards Track                   [Page 56]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


           leaf value-update-rate {
             type uint32;
             units "milliseconds";
             status deprecated;
             description
               "An indication of the frequency that the server updates
                the associated 'value' node, represented in
                milliseconds.  The value zero indicates:

                 - the sensor value is updated on demand (e.g.,
                   when polled by the server for a get-request),

                 - the sensor value is updated when the sensor
                   value changes (event-driven), or

                 - the server does not know the update rate.";
             reference
               "<a href="./rfc3433">RFC 3433</a>: Entity Sensor Management Information Base -
                          entPhySensorValueUpdateRate";
           }
         }
       }
     }

     /*
      * Notifications
      */

     notification hardware-state-change {
       status deprecated;
       description
         "A hardware-state-change notification is generated when the
          value of /hardware/last-change changes in the operational
          state.";
       reference
         "<a href="./rfc6933">RFC 6933</a>: Entity MIB (Version 4) - entConfigChange";
     }

     notification hardware-state-oper-enabled {
       if-feature hardware-state;
       status deprecated;
       description
         "A hardware-state-oper-enabled notification signifies that a
          component has transitioned into the 'enabled' state.";

       leaf name {
         type leafref {
           path "/hardware/component/name";



<span class="grey">Bierman, et al.              Standards Track                   [Page 57]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         }
         status deprecated;
         description
           "The name of the component that has transitioned into the
            'enabled' state.";
       }
       leaf admin-state {
         type leafref {
           path "/hardware/component/state/admin-state";
         }
         status deprecated;
         description
           "The administrative state for the component.";
       }
       leaf alarm-state {
         type leafref {
           path "/hardware/component/state/alarm-state";
         }
         status deprecated;
         description
           "The alarm state for the component.";
       }
       reference
         "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOperEnabled";
     }

     notification hardware-state-oper-disabled {
       if-feature hardware-state;
       status deprecated;
       description
         "A hardware-state-oper-disabled notification signifies that a
          component has transitioned into the 'disabled' state.";

       leaf name {
         type leafref {
           path "/hardware/component/name";
         }
         status deprecated;
         description
           "The name of the component that has transitioned into the
            'disabled' state.";
       }
       leaf admin-state {
         type leafref {
           path "/hardware/component/state/admin-state";
         }
         status deprecated;




<span class="grey">Bierman, et al.              Standards Track                   [Page 58]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


         description
           "The administrative state for the component.";
       }
       leaf alarm-state {
         type leafref {
           path "/hardware/component/state/alarm-state";
         }
         status deprecated;
         description
           "The alarm state for the component.";
       }
       reference
         "<a href="./rfc4268">RFC 4268</a>: Entity State MIB - entStateOperDisabled";
     }

   }

   &lt;CODE ENDS&gt;

































<span class="grey">Bierman, et al.              Standards Track                   [Page 59]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
<span class="grey"><a href="./rfc8348">RFC 8348</a>                YANG Hardware Management              March 2018</span>


Acknowledgments

   The authors wish to thank the following individuals, who all provided
   helpful comments on various draft versions of this document: Bart
   Bogaert, Timothy Carey, William Lupton, and Juergen Schoenwaelder.

Authors' Addresses

   Andy Bierman
   YumaWorks

   Email: andy@yumaworks.com


   Martin Bjorklund
   Tail-f Systems

   Email: mbj@tail-f.com


   Jie Dong
   Huawei Technologies

   Email: jie.dong@huawei.com


   Dan Romascanu

   Email: dromasca@gmail.com






















Bierman, et al.              Standards Track                   [Page 60]
</pre>