draft-ietf-netmod-entity-00.txt   draft-ietf-netmod-entity-01.txt 
Network Working Group A. Bierman Network Working Group A. Bierman
Internet-Draft YumaWorks Internet-Draft YumaWorks
Intended status: Standards Track M. Bjorklund Intended status: Standards Track M. Bjorklund
Expires: November 14, 2016 Tail-f Systems Expires: May 4, 2017 Tail-f Systems
J. Dong J. Dong
Huawei Technologies Huawei Technologies
D. Romascanu D. Romascanu
Avaya October 31, 2016
May 13, 2016
A YANG Data Model for Entity Management A YANG Data Model for Hardware Management
draft-ietf-netmod-entity-00 draft-ietf-netmod-entity-01
Abstract Abstract
This document defines a YANG data model for the management of This document defines a YANG data model for the management of
multiple physical entities managed by a single server. hardware on a single server.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 14, 2016. This Internet-Draft will expire on May 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 13 skipping to change at page 2, line 13
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 2 1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 2
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Entity Data Model . . . . . . . . . . . . . . . . . . . . . . 3 3. Hardware Data Model . . . . . . . . . . . . . . . . . . . . . 3
3.1. The Physical Entry Lists . . . . . . . . . . . . . . . . 5 3.1. The Components Lists . . . . . . . . . . . . . . . . . . 5
4. Relationship to ENTITY-MIB . . . . . . . . . . . . . . . . . 5 4. Relationship to ENTITY-MIB . . . . . . . . . . . . . . . . . 5
5. Relationship to ENTITY-SENSOR-MIB . . . . . . . . . . . . . . 6 5. Relationship to ENTITY-SENSOR-MIB . . . . . . . . . . . . . . 6
6. Relationship to ENTITY-STATE-MIB . . . . . . . . . . . . . . 6 6. Relationship to ENTITY-STATE-MIB . . . . . . . . . . . . . . 6
7. Entity YANG Module . . . . . . . . . . . . . . . . . . . . . 6 7. Hardware YANG Module . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
9. Security Considerations . . . . . . . . . . . . . . . . . . . 35 9. Security Considerations . . . . . . . . . . . . . . . . . . . 35
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35
11. Normative References . . . . . . . . . . . . . . . . . . . . 35 11. Normative References . . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
This document defines a YANG [I-D.ietf-netmod-rfc6020bis] data model This document defines a YANG [I-D.ietf-netmod-rfc6020bis] data model
for the management of multiple physical entities managed by a single for the management of hardware on a single server.
server.
The data model includes configuration data and state data (status The data model includes configuration data and state data (status
information and counters for the collection of statistics). information and counters for the collection of statistics).
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 14, [RFC2119].
skipping to change at page 3, line 16 skipping to change at page 3, line 16
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Objectives 2. Objectives
This section describes some of the design objectives for the entity This section describes some of the design objectives for the hardware
model. model.
o There are many common properties used to identify the entities, o There are many common properties used to identify hardware
which need to be supported in the entity data module. components, which need to be supported in the hardware data model.
o There are many important information and states about the o There are many important information and states about the
entities, which needs to be collected from the devices which components, which needs to be collected from the devices which
support the entity data model. support the hardware data model.
o The entity data model SHOULD be suitable for new implementations o The hardware data model SHOULD be suitable for new implementations
to use as is. to use as is.
o The entity data model defined in this document can be implemented o The hardware data model defined in this document can be
on a system that also implements ENTITY-MIB, thus the mapping implemented on a system that also implements ENTITY-MIB, thus the
between the entity data model and ENTITY-MIB SHOULD be clear. mapping between the hardware data model and ENTITY-MIB SHOULD be
clear.
3. Entity Data Model 3. Hardware Data Model
This document defines the YANG module "ietf-entity", which has the This document defines the YANG module "ietf-hardware", which has the
following structure: following structure:
module: ietf-entity module: ietf-hardware
+--ro entity-state +--ro hardware-state
| +--ro last-change? yang:date-and-time | +--ro last-change? yang:date-and-time
| +--ro physical-entity* [name] | +--ro component* [name]
| +--ro name string | +--ro name string
| +--ro class? identityref | +--ro class identityref
| +--ro physical-index? int32 {entity-mib}? | +--ro physical-index? int32 {entity-mib}?
| +--ro description? string | +--ro description? string
| +--ro contained-in* -> ../../physical-entity/name | +--ro contained-in* -> ../../component/name
| +--ro contains-child* -> ../../physical-entity/name | +--ro contains-child* -> ../../component/name
| +--ro parent-rel-pos? int32 | +--ro parent-rel-pos? int32
| +--ro hardware-rev? string | +--ro hardware-rev? string
| +--ro firmware-rev? string | +--ro firmware-rev? string
| +--ro software-rev? string | +--ro software-rev? string
| +--ro serial-num? string | +--ro serial-num? string
| +--ro mfg-name? string | +--ro mfg-name? string
| +--ro model-name? string | +--ro model-name? string
| +--ro alias? string | +--ro alias? string
| +--ro asset-id? string | +--ro asset-id? string
| +--ro is-fru? boolean | +--ro is-fru? boolean
| +--ro mfg-date? yang:date-and-time | +--ro mfg-date? yang:date-and-time
| +--ro uri* inet:uri | +--ro uri* inet:uri
| +--ro uuid? yang:uuid | +--ro uuid? yang:uuid
| +--ro state {entity-state}? | +--ro state {entity-state}?
| | +--ro state-last-changed? yang:date-and-time | | +--ro state-last-changed? yang:date-and-time
| | +--ro admin-state? entity-admin-state | | +--ro admin-state? admin-state
| | +--ro oper-state? entity-oper-state | | +--ro oper-state? oper-state
| | +--ro usage-state? entity-usage-state | | +--ro usage-state? usage-state
| | +--ro alarm-status? entity-alarm-status | | +--ro alarm-status? alarm-status
| | +--ro standby-status? entity-standby-status | | +--ro standby-status? standby-status
| +--ro sensor-data {entity-sensor}? | +--ro sensor-data {entity-sensor}?
| +--ro data-type? entity-sensor-data-type | +--ro data-type? sensor-data-type
| +--ro data-scale? entity-sensor-data-scale | +--ro data-scale? sensor-data-scale
| +--ro precision? entity-sensor-precision | +--ro precision? sensor-precision
| +--ro value? entity-sensor-value | +--ro value? sensor-value
| +--ro oper-status? entity-sensor-status | +--ro oper-status? sensor-status
| +--ro sensor-units-display? string | +--ro sensor-units-display? string
| +--ro value-timestamp? yang:date-and-time | +--ro value-timestamp? yang:date-and-time
| +--ro value-update-rate? uint32 | +--ro value-update-rate? uint32
+--rw entity {entity-config}? +--rw hardware {hardware-config}?
+--rw physical-entity* [name] +--rw component* [name]
+--rw name string +--rw name string
+--rw serial-num? string +--rw serial-num? string
+--rw alias? string +--rw alias? string
+--rw asset-id? string +--rw asset-id? string
+--rw uri* inet:uri +--rw uri* inet:uri
+--rw admin-state? entity-admin-state {entity-state}? +--rw admin-state? admin-state {entity-state}?
notifications: notifications:
+---n ent-config-change +---n harwdare-state-change
+---n ent-state-oper-enabled {entity-state}? +---n hardware-state-oper-enabled {entity-state}?
| +--ro name? -> /entity-state/physical-entity | +--ro name? -> /hardware-state/component/name
/name | +--ro admin-state?
| +--ro admin-state? -> /entity-state/physical-entity | | -> /hardware-state/component/state/admin-state
/state/admin-state | +--ro alarm-status?
| +--ro alarm-status? -> /entity-state/physical-entity | -> /hardware-state/component/state/alarm-status
/state/alarm-status +---n hardware-state-oper-disabled {entity-state}?
+---n ent-state-oper-disabled {entity-state}? +--ro name? -> /hardware-state/component/name
+--ro name? -> /entity-state/physical-entity +--ro admin-state?
/name | -> /hardware-state/component/state/admin-state
+--ro admin-state? -> /entity-state/physical-entity +--ro alarm-status?
/state/admin-state -> /hardware-state/component/state/alarm-status
+--ro alarm-status? -> /entity-state/physical-entity
/state/alarm-status
3.1. The Physical Entry Lists 3.1. The Components Lists
The data model for physical entities presented in this document uses The data model for hardware presented in this document uses a flat
a flat list of entities. Each entity in the list is identified by list of components. Each component in the list is identified by its
its name. Furthermore, each entity has a mandatory "class" leaf. name. Furthermore, each component has a mandatory "class" leaf.
The "iana-entity" module defines YANG identities for the hardware The "iana-entity" module defines YANG identities for the hardware
types in the IANA-maintained "IANA-ENTITY-MIB" registry. types in the IANA-maintained "IANA-ENTITY-MIB" registry.
The "class" leaf is a YANG identity that describes the type of the The "class" leaf is a YANG identity that describes the type of the
hardware. Vendors are encouraged to either directly use one of the hardware. Vendors are encouraged to either directly use one of the
common IANA-defined identities, or derive a more specific identity common IANA-defined identities, or derive a more specific identity
from one of them. from one of them.
There is one optional list of configured physical entities ("/entity/ There is one optional list of configured components ("/hardware/
physical-entity"), and a separate list for the operational state of component"), and a separate list for the operational state of all
all physical entities ("/entity-state/physical-entity"). components ("/hardware-state/component").
4. Relationship to ENTITY-MIB 4. Relationship to ENTITY-MIB
If the device implements the ENTITY-MIB [RFC6933], each entry in the If the device implements the ENTITY-MIB [RFC6933], each entry in the
/entity-state/physical-entity list is mapped to one EntPhysicalEntry. /hardware-state/component list is mapped to one EntPhysicalEntry.
Objects that are writable in the MIB are mapped to nodes in the Objects that are writable in the MIB are mapped to nodes in the
/entity/physical-entity list. /hardware/component list.
The "physical-index" leaf MUST contain the value of the corresponding The "physical-index" leaf MUST contain the value of the corresponding
entPhysicalEntry's entPhysicalIndex. entPhysicalEntry's entPhysicalIndex.
The "class" leaf is mapped to both entPhysicalClass and The "class" leaf is mapped to both entPhysicalClass and
entPhysicalVendorType. If the value of the "class" leaf is an entPhysicalVendorType. If the value of the "class" leaf is an
identity that is either derived from or is one of the identities in identity that is either derived from or is one of the identities in
the "iana-entity" module, then entPhysicalClass contains the the "iana-entity" module, then entPhysicalClass contains the
corresponding IANAPhysicalClass enumeration value. Otherwise, corresponding IANAPhysicalClass enumeration value. Otherwise,
entPhysicalClass contains the IANAPhysicalClass value "other(1)". entPhysicalClass contains the IANAPhysicalClass value "other(1)".
Vendors are encouraged to define an identity (derived from an Vendors are encouraged to define an identity (derived from an
identity in "iana-entity" if possible) for each enterprise-specific identity in "iana-entity" if possible) for each enterprise-specific
registration identifier used for entPhysicalVendorType, and use that registration identifier used for entPhysicalVendorType, and use that
identity for the "class" leaf. identity for the "class" leaf.
The following tables list the YANG data nodes with corresponding The following tables list the YANG data nodes with corresponding
objects in the ENTITY-MIB. objects in the ENTITY-MIB.
-- YANG data nodes and related ENTITY-MIB objects +----------------------------------+--------------------------------+
+------------------------------------+------------------------------+ | YANG data node in /hardware- | ENTITY-MIB object |
| YANG data node in /entity-state | ENTITY-MIB object | | state/component | |
| /physical-entity | | +----------------------------------+--------------------------------+
+------------------------------------+------------------------------+ | name | entPhysicalName |
| name | entPhysicalName | | class | entPhysicalClass |
| class | entPhysicalClass | | | entPhysicalVendorType |
| | entPhysicalVendorType | | physical-index | entPhysicalIndex |
| physical-index | entPhysicalIndex | | description | entPhysicalDescr |
| description | entPhysicalDescr | | contained-in | entPhysicalContainedIn |
| contained-in | entPhysicalContainedIn | | contains-child | entPhysicalChildIndex |
| contains-child | entPhysicalChildIndex | | parent-rel-pos | entPhysicalParentRelPos |
| parent-rel-pos | entPhysicalParentRelPos | | hardware-rev | entPhysicalHardwareRev |
| hardware-rev | entPhysicalHardwareRev | | firmware-rev | entPhysicalFirmwareRev |
| firmware-rev | entPhysicalFirmwareRev | | software-rev | entPhysicalSoftwareRev |
| software-rev | entPhysicalSoftwareRev | | serial-num | entPhysicalSerialNum |
| serial-num | entPhysicalSerialNum | | mfg-name | entPhysicalMfgName |
| mfg-name | entPhysicalMfgName | | model-name | entPhysicalModelName |
| model-name | entPhysicalModelName | | alias | entPhysicalAlias |
| alias | entPhysicalAlias | | asset-id | entPhysicalAssetID |
| asset-id | entPhysicalAssetID | | is-fru | entPhysicalIsFRU |
| is-fru | entPhysicalIsFRU | | mfg-date | entPhysicalMfgDate |
| mfg-date | entPhysicalMfgDate | | uri | entPhysicalUris |
| uri | entPhysicalUris | | uuid | entPhysicalUUID |
| uuid | entPhysicalUUID | +----------------------------------+--------------------------------+
+------------------------------------+------------------------------+
YANG data nodes and related ENTITY-MIB objects
5. Relationship to ENTITY-SENSOR-MIB 5. Relationship to ENTITY-SENSOR-MIB
TBD relationship to [RFC3433]. TBD relationship to [RFC3433].
6. Relationship to ENTITY-STATE-MIB 6. Relationship to ENTITY-STATE-MIB
TBD relationship to [RFC4268]. TBD relationship to [RFC4268].
7. Entity YANG Module 7. Hardware YANG Module
<CODE BEGINS> file "ietf-entity@2016-05-13.yang"
module ietf-entity {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-entity";
prefix ent;
import ietf-inet-types {
prefix inet;
}
import ietf-yang-types {
prefix yang;
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
WG Chair: Lou Berger <CODE BEGINS> file "ietf-hardware@2016-10-25.yang"
<mailto:lberger@labn.net>
WG Chair: Juergen Schoenwaelder module ietf-hardware {
<mailto:j.schoenwaelder@jacobs-university.de> yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-hardware";
prefix hw;
WG Chair: Kent Watsen import ietf-inet-types {
<mailto:kwatsen@juniper.net> prefix inet;
}
import ietf-yang-types {
prefix yang;
}
import iana-entity {
prefix ianaent;
}
Editor: Andy Bierman organization
<mailto:andy@yumaworks.com> "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
Editor: Martin Bjorklund contact
<mailto:mbj@tail-f.com> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
Editor: Jie Dong WG Chair: Lou Berger
<mailto:jie.dong@huawei.com> <mailto:lberger@labn.net>
Editor: Dan Romascanu WG Chair: Kent Watsen
<mailto:dromasca@avaya.com>"; <mailto:kwatsen@juniper.net>
// RFC Ed.: replace XXXX with actual RFC number and remove this Editor: Andy Bierman
// note. <mailto:andy@yumaworks.com>
description Editor: Martin Bjorklund
"This module contains a collection of YANG definitions for <mailto:mbj@tail-f.com>
managing physical entities.
Copyright (c) 2016 IETF Trust and the persons identified as Editor: Jie Dong
authors of the code. All rights reserved. <mailto:jie.dong@huawei.com>
Redistribution and use in source and binary forms, with or Editor: Dan Romascanu
without modification, is permitted pursuant to, and subject <mailto:dromasca@gmail.com>";
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see // RFC Ed.: replace XXXX with actual RFC number and remove this
the RFC itself for full legal notices."; // note.
// RFC Ed.: update the date below with the date of RFC publication description
// and remove this note. "This module contains a collection of YANG definitions for
revision 2016-05-13 { managing hardware.
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Entity Management";
}
/* Copyright (c) 2016 IETF Trust and the persons identified as
* Features authors of the code. All rights reserved.
*/
feature entity-mib { Redistribution and use in source and binary forms, with or
description without modification, is permitted pursuant to, and subject
"This feature indicates that the device implements to the license terms contained in, the Simplified BSD License
the ENTITY-MIB."; set forth in Section 4.c of the IETF Trust's Legal Provisions
reference "RFC 6933: Entity MIB (Version 4)"; Relating to IETF Documents
} (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
feature entity-config { // RFC Ed.: update the date below with the date of RFC publication
description // and remove this note.
"Indicates that the server supports configuration of revision 2016-10-25 {
physical entities."; description
} "Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Hardware Management";
}
feature entity-state { /*
description * Features
"Indicates the ENTITY-STATE-MIB objects are supported"; */
reference "RFC 4268: Entity State MIB";
}
feature entity-sensor { feature entity-mib {
description description
"Indicates the ENTITY-SENSOR-MIB objects are supported"; "This feature indicates that the device implements
reference "RFC 3433: Entity Sensor MIB"; the ENTITY-MIB.";
} reference "RFC 6933: Entity MIB (Version 4)";
}
/* feature hardware-config {
* Typedefs description
*/ "Indicates that the server supports configuration of
hardware components.";
}
typedef entity-admin-state { feature entity-state {
type enumeration { description
enum unknown { "Indicates the ENTITY-STATE-MIB objects are supported";
value 1; reference "RFC 4268: Entity State MIB";
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 "RFC 4268: EntityAdminState";
}
typedef entity-oper-state { feature entity-sensor {
type enumeration { description
enum unknown { "Indicates the ENTITY-SENSOR-MIB objects are supported";
value 1; reference "RFC 3433: Entity Sensor MIB";
description }
"The resource is unable to report operational state.";
}
enum disabled {
value 2;
description
"The resource is totally inoperable.";
}
enum enabled {
value 3;
description
"The resource is partially or fully operable.";
}
enum testing {
value 4;
description
"The resource is currently being tested and cannot
therefore report whether it is operational or not.";
}
} /*
description * Typedefs
"Represents the possible values of operational states."; */
reference "RFC 4268: EntityOperState";
}
typedef entity-usage-state { typedef admin-state {
type enumeration { type enumeration {
enum unknown { enum unknown {
value 1; value 1;
description description
"The resource is unable to report usage state."; "The resource is unable to report administrative state.";
} }
enum idle { enum locked {
value 2; value 2;
description description
"The resource is servicing no users."; "The resource is administratively prohibited from use.";
} }
enum active { enum shutting-down {
value 3; value 3;
description description
"The resource is currently in use and it has sufficient "The resource usage is administratively limited to current
spare capacity to provide for additional users."; instances of use.";
} }
enum busy { enum unlocked {
value 4; value 4;
description description
"The resource is currently in use, but it currently has "The resource is not administratively prohibited from
no spare capacity to provide for additional users."; use.";
} }
} }
description description
"Represents the possible values of usage states."; "Represents the various possible administrative states.";
reference "RFC 4268, EntityUsageState"; reference "RFC 4268: EntityAdminState";
} }
typedef entity-alarm-status { typedef oper-state {
type bits { type enumeration {
bit unknown { enum unknown {
position 0; value 1;
description description
"The resource is unable to report alarm state."; "The resource is unable to report operational state.";
} }
bit under-repair { enum disabled {
position 1; value 2;
description description
"The resource is currently being repaired, which, depending "The resource is totally inoperable.";
on the implementation, may make the other values in this }
bit string not meaningful."; enum enabled {
} value 3;
bit critical { description
position 2; "The resource is partially or fully operable.";
description }
"One or more critical alarms are active against the enum testing {
resource."; value 4;
} description
bit major { "The resource is currently being tested and cannot
position 3; therefore report whether it is operational or not.";
description }
"One or more major alarms are active against the resource."; }
} description
bit minor { "Represents the possible values of operational states.";
position 4; reference "RFC 4268: EntityOperState";
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.
This alarm status is not defined in X.733.";
}
bit indeterminate {
position 6;
description
"One or more alarms of whose perceived severity cannot be
determined are active against this resource.
This alarm status is not defined in X.733.";
}
}
description
"Represents the possible values of alarm status.
An Alarm [RFC3877] is a persistent indication of an error or
warning condition.
When no bits of this attribute are set, then no active typedef usage-state {
alarms are known against this entity and it is not under type enumeration {
repair."; enum unknown {
reference "RFC 4268: EntityAlarmStatus"; 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 "RFC 4268, EntityUsageState";
}
typedef entity-standby-status { typedef alarm-status {
type enumeration { type bits {
enum unknown { bit unknown {
value 1; position 0;
description description
"The resource is unable to report standby state."; "The resource is unable to report alarm state.";
} }
enum hot-standby { bit under-repair {
value 2; position 1;
description description
"The resource is not providing service, but it will be "The resource is currently being repaired, which, depending
immediately able to take over the role of the resource on the implementation, may make the other values in this
to be backed up, without the need for initialization bit string not meaningful.";
activity, and will contain the same information as the }
resource to be backed up."; bit critical {
} position 2;
enum cold-standby { description
value 3; "One or more critical alarms are active against the
description resource.";
"The resource is to back up another resource, but will not }
be immediately able to take over the role of a resource bit major {
to be backed up, and will require some initialization position 3;
activity."; description
} "One or more major alarms are active against the
enum providing-service { resource.";
value 4; }
description bit minor {
"The resource is providing service."; position 4;
} description
} "One or more minor alarms are active against the
description resource.";
"Represents the possible values of standby status."; }
reference "RFC 4268: EntityStandbyStatus"; bit warning {
} position 5;
description
"One or more warning alarms are active against the
resource. This alarm status is not defined in X.733.";
}
bit indeterminate {
position 6;
description
"One or more alarms of whose perceived severity cannot be
determined are active against this resource.
This alarm status is not defined in X.733.";
}
}
description
"Represents the possible values of alarm status.
An Alarm [RFC3877] is a persistent indication of an error or
warning condition.
typedef entity-sensor-data-type { When no bits of this attribute are set, then no active
type enumeration { alarms are known against this component and it is not under
enum other { repair.";
value 1; reference "RFC 4268: EntityAlarmStatus";
description }
"A measure other than those listed below.";
}
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;
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
"An node using this data type represents the Entity Sensor
measurement data type associated with a physical sensor
value. The actual data units are determined by examining an
node of this type together with the associated
entity-sensor-data-scale node.
An node of this type SHOULD be defined together with nodes typedef standby-status {
of type entity-sensor-data-scale and type enumeration {
entity-sensor-precision. These three types are used to enum unknown {
identify the semantics of an node of type value 1;
entity-sensor-value."; description
reference "RFC 3433: EntitySensorDataType"; "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 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 status.";
reference "RFC 4268: EntityStandbyStatus";
}
typedef entity-sensor-data-scale { typedef sensor-data-type {
type enumeration { type enumeration {
enum yocto { enum other {
value 1; value 1;
description description
"Data scaling factor of 10^-24."; "A measure other than those listed below.";
} }
enum zepto { enum unknown {
value 2; value 2;
description description
"Data scaling factor of 10^-21."; "An unknown measurement, or arbitrary, relative numbers";
} }
enum atto { enum volts-AC {
value 3; value 3;
description description
"Data scaling factor of 10^-18."; "A measure of electric potential (alternating current).";
} }
enum femto { enum volts-DC {
value 4; value 4;
description description
"Data scaling factor of 10^-15."; "A measure of electric potential (direct current).";
} }
enum pico { enum amperes {
value 5; value 5;
description description
"Data scaling factor of 10^-12."; "A measure of electric current.";
} }
enum nano { enum watts {
value 6; value 6;
description description
"Data scaling factor of 10^-9."; "A measure of power.";
} }
enum micro { enum hertz {
value 7; value 7;
description description
"Data scaling factor of 10^-6."; "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;
description
"A measure of cubic meters per minute (airflow).";
}
enum truth-value {
value 12;
description
"Value is one of 1 (true) or 2 (false)";
}
} }
enum milli { description
value 8; "An node using this data type represents the Entity Sensor
description measurement data type associated with a physical sensor
"Data scaling factor of 10^-3."; value. The actual data units are determined by examining an
} node of this type together with the associated
enum units { sensor-data-scale node.
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 exa {
value 14;
description
"Data scaling factor of 10^15.";
}
enum peta {
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
"An 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 an
node of this type together with the associated
entity-sensor-data-type.
An node of this type SHOULD be defined together with nodes An node of this type SHOULD be defined together with nodes
of type entity-sensor-data-type and entity-sensor-precision. of type sensor-data-scale and
Together, associated nodes of these three types are used to sensor-precision. These three types are used to
identify the semantics of an node of type identify the semantics of an node of type
entity-sensor-value."; sensor-value.";
reference "RFC 3433: EntitySensorDataScale"; reference "RFC 3433: EntitySensorDataType";
} }
typedef entity-sensor-precision { typedef sensor-data-scale {
type int32 { type enumeration {
range "-8 .. 9"; enum yocto {
} value 1;
description description
"An node using this data type represents a sensor "Data scaling factor of 10^-24.";
precision range. }
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;
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 exa {
value 14;
description
"Data scaling factor of 10^15.";
}
enum peta {
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
"An 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 an
node of this type together with the associated
sensor-data-type.
An node of this type SHOULD be defined together with nodes An node of this type SHOULD be defined together with nodes
of type entity-sensor-data-type and entity-sensor-data-scale. of type sensor-data-type and sensor-precision.
Together, associated nodes of these three types are used to Together, associated nodes of these three types are used to
identify the semantics of an node of type identify the semantics of an node of type
entity-sensor-value. sensor-value.";
reference "RFC 3433: EntitySensorDataScale";
}
If an node of this type contains a value in the range 1 to 9, typedef sensor-precision {
it represents the number of decimal places in the fractional type int32 {
part of an associated entity-sensor-value fixed- point number. range "-8 .. 9";
}
description
"An node using this data type represents a sensor
precision range.
If an node of this type contains a value in the range -8 to An node of this type SHOULD be defined together with nodes
-1, it represents the number of accurate digits in the of type sensor-data-type and sensor-data-scale.
associated entity-sensor-value fixed-point number. Together, associated nodes of these three types are used to
identify the semantics of an node of type
sensor-value.
The value zero indicates the associated entity-sensor-value If an node of this type contains a value in the range 1 to 9,
node is not a fixed-point number. it represents the number of decimal places in the fractional
part of an associated sensor-value fixed- point number.
Server implementors must choose a value for the associated If an node of this type contains a value in the range -8 to
entity-sensor-precision node so that the precision and -1, it represents the number of accurate digits in the
accuracy of the associated entity-sensor-value node is associated sensor-value fixed-point number.
correctly indicated.
For example, a physical entity representing a temperature The value zero indicates the associated sensor-value
sensor that can measure 0 degrees to 100 degrees C in 0.1 node is not a fixed-point number.
degree increments, +/- 0.05 degrees, would have an
entity-sensor-precision value of '1', an
entity-sensor-data-scale value of 'units', and an
entity-sensor-value ranging from '0' to '1000'. The
entity-sensor-value would be interpreted as 'degrees C * 10'.";
reference "RFC 3433: EntitySensorPrecision";
}
typedef entity-sensor-value { Server implementors must choose a value for the associated
type int32 { sensor-precision node so that the precision and
range "-1000000000 .. 1000000000"; accuracy of the associated sensor-value node is
} correctly indicated.
description
"An node using this data type represents an Entity Sensor
value.
An node of this type SHOULD be defined together with nodes For example, a component representing a temperature
of type entity-sensor-data-type, entity-sensor-data-scale, and sensor that can measure 0 degrees to 100 degrees C in 0.1
entity-sensor-precision. Together, associated nodes of those degree increments, +/- 0.05 degrees, would have an
three types are used to identify the semantics of an node of sensor-precision value of '1', an
this data type. sensor-data-scale value of 'units', and an
sensor-value ranging from '0' to '1000'. The
sensor-value would be interpreted as
'degrees C * 10'.";
reference "RFC 3433: EntitySensorPrecision";
}
The semantics of an node using this data type are determined typedef sensor-value {
by the value of the associated entity-sensor-data-type node. type int32 {
range "-1000000000 .. 1000000000";
}
description
"An node using this data type represents an Entity Sensor
value.
If the associated entity-sensor-data-type node is equal to An node of this type SHOULD be defined together with nodes
'voltsAC', 'voltsDC', 'amperes', 'watts', 'hertz', of type sensor-data-type, sensor-data-scale, and
'celsius', or 'cmm', then an node of this type MUST sensor-precision. Together, associated nodes of those
contain a fixed point number ranging from -999,999,999 to three types are used to identify the semantics of an node of
+999,999,999. The value -1000000000 indicates an underflow this data type.
error. The value +1000000000 indicates an overflow error. The
entity-sensor-precision indicates how many fractional digits
are represented in the associated entity-sensor-value node.
If the associated entity-sensor-data-type node is equal to The semantics of an node using this data type are determined
'percentRH', then an node of this type MUST contain a by the value of the associated sensor-data-type node.
number ranging from 0 to 100.
If the associated entity-sensor-data-type node is equal to If the associated sensor-data-type node is equal to
'rpm', then an node of this type MUST contain a number 'voltsAC', 'voltsDC', 'amperes', 'watts', 'hertz',
ranging from -999,999,999 to +999,999,999. 'celsius', or 'cmm', then an 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-precision indicates how many fractional digits
are represented in the associated sensor-value node.
If the associated entity-sensor-data-type node is equal to If the associated sensor-data-type node is equal to
'truthvalue', then an node of this type MUST contain 'percentRH', then an node of this type MUST contain a
either the value 1 (true) or the value 2 (false)'. number ranging from 0 to 100.
If the associated entity-sensor-data-type node is equal to If the associated sensor-data-type node is equal to
'other' or unknown', then an node of this type MUST 'rpm', then an node of this type MUST contain a number
contain a number ranging from -1000000000 to 1000000000."; ranging from -999,999,999 to +999,999,999.
reference "RFC 3433: EntitySensorValue";
}
typedef entity-sensor-status { If the associated sensor-data-type node is equal to
type enumeration { 'truthvalue', then an node of this type MUST contain
enum ok { either the value 1 (true) or the value 2 (false)'.
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
"An node using this data type represents the operational
status of a physical sensor.";
reference "RFC 3433: EntitySensorStatus";
}
/* If the associated sensor-data-type node is equal to
* Identities 'other' or unknown', then an node of this type MUST
*/ contain a number ranging from -1000000000 to 1000000000.";
reference "RFC 3433: EntitySensorValue";
}
identity entity-physical-class { typedef sensor-status {
description type enumeration {
"This identity is the base for all physical entity class enum ok {
identifiers."; 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
"An node using this data type represents the operational
status of a physical sensor.";
reference "RFC 3433: EntitySensorStatus";
}
/* /*
* Operational state data nodes * Operational state data nodes
*/ */
container entity-state { container hardware-state {
config false; config false;
description description
"Data nodes for the operational state of physical entities."; "Data nodes for the operational state of components.";
leaf last-change { leaf last-change {
type yang:date-and-time; type yang:date-and-time;
description description
"The time the '/entity-state/physical-entity' list changed."; "The time the '/hardware-state/component' list
} changed.";
}
list physical-entity { list component {
key name; key name;
description description
"List of physical entities"; "List of components.";
reference "RFC 6933: entPhysicalEntry"; reference "RFC 6933: entPhysicalEntry";
leaf name { leaf name {
type string; type string;
description description
"Administrative name assigned to this physical entity. "Administrative name assigned to this component.
No restrictions apply. Not required to be the same as No restrictions apply. Not required to be the same as
entPhysicalName."; entPhysicalName.";
} }
leaf class { leaf class {
type identityref { type identityref {
base entity-physical-class; base ianaent:entity-physical-class;
} }
mandatory true; mandatory true;
description description
"An indication of the general hardware type "An indication of the general hardware type
of the physical entity."; of the component.";
reference "RFC 6933: entPhysicalClass"; reference "RFC 6933: entPhysicalClass";
} }
leaf physical-index { leaf physical-index {
if-feature entity-mib; if-feature entity-mib;
type int32 { type int32 {
range "1..2147483647"; range "1..2147483647";
} }
description description
"The entPhysicalIndex for the entPhysicalEntry represented "The entPhysicalIndex for the entPhysicalEntry represented
by this list entry."; by this list entry.";
reference "RFC 6933: entPhysicalIndex"; reference "RFC 6933: entPhysicalIndex";
} }
leaf description { leaf description {
type string; type string;
description description
"A textual description of physical entity. This node "A textual description of component. This node
should contain a string that identifies the manufacturer's should contain a string that identifies the manufacturer's
name for the physical entity and should be set to a name for the component and should be set to a
distinct value for each version or model of the physical distinct value for each version or model of the
entity."; component.";
reference "RFC 6933: entPhysicalDescr"; reference "RFC 6933: entPhysicalDescr";
} }
leaf-list contained-in { leaf-list contained-in {
type leafref { type leafref {
path "../../physical-entity/name"; path "../../component/name";
} }
description description
"The name of the physical entity that 'contains' "The name of the component that 'contains'
this physical entity."; this component.";
reference "RFC 6933: entPhysicalContainedIn"; reference "RFC 6933: entPhysicalContainedIn";
} }
leaf-list contains-child { leaf-list contains-child {
type leafref { type leafref {
path "../../physical-entity/name"; path "../../component/name";
} }
description description
"The name of the contained physical entity."; "The name of the contained component.";
reference "RFC 6933: entPhysicalChildIndex"; reference "RFC 6933: entPhysicalChildIndex";
} }
leaf parent-rel-pos { leaf parent-rel-pos {
type int32 { type int32 {
range "0 .. 2147483647"; range "0 .. 2147483647";
} }
description description
"An indication of the relative position of this child "An indication of the relative position of this child
component among all its sibling components. Sibling component among all its sibling components. Sibling
components are defined as physical entities that share the components are defined as components that share the
same instance values of each of the contained-in same instance values of each of the contained-in
and class elements."; and class elements.";
reference "RFC 6933: entPhysicalParentRelPos"; reference "RFC 6933: entPhysicalParentRelPos";
} }
leaf hardware-rev { leaf hardware-rev {
type string; type string;
description description
"The vendor-specific hardware revision string for the "The vendor-specific hardware revision string for the
physical entity. The preferred value is the hardware component. The preferred value is the hardware
revision identifier actually printed on the component revision identifier actually printed on the component
itself (if present)."; itself (if present).";
reference "RFC 6933: entPhysicalHardwareRev"; reference "RFC 6933: entPhysicalHardwareRev";
} }
leaf firmware-rev {
type string;
description
"The vendor-specific firmware revision string for the
component.";
reference "RFC 6933: entPhysicalFirmwareRev";
}
leaf firmware-rev { leaf software-rev {
type string; type string;
description description
"The vendor-specific firmware revision string for the "The vendor-specific software revision string for the
physical entity."; component.";
reference "RFC 6933: entPhysicalFirmwareRev"; reference "RFC 6933: entPhysicalSoftwareRev";
} }
leaf software-rev { leaf serial-num {
type string; type string;
description description
"The vendor-specific software revision string for the "The vendor-specific serial number string for the
physical entity."; component. The preferred value is the serial number
reference "RFC 6933: entPhysicalSoftwareRev"; string actually printed on the component itself (if
} present).
leaf serial-num { If a serial number has been configured for this component
type string; in /hardware/component/serial-num, this node contains
description the configured value.";
"The vendor-specific serial number string for the physical reference "RFC 6933: entPhysicalSerialNum";
entity. The preferred value is the serial number string }
actually printed on the component itself (if present).
If a serial number has been configured for this entity in leaf mfg-name {
/entity/physical-entity/serial-num, this node contains the type string;
configured value."; description
reference "RFC 6933: entPhysicalSerialNum"; "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).
leaf mfg-name { Note that comparisons between instances of the model-name,
type string; firmware-rev, software-rev, and the serial-num nodes are
description only meaningful amongst component with the same
"The name of the manufacturer of this physical component. value of mfg-name.
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, If the manufacturer name string associated with the
firmware-rev, software-rev, and the serial-num nodes are physical component is unknown to the server, then this
only meaningful amongst physical entities with the same node will contain a zero-length string.";
value of mfg-name. reference "RFC 6933: entPhysicalMfgName";
}
leaf model-name {
type string;
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 manufacturer name string associated with the If the model name string associated with the physical
physical component is unknown to the server, then this component is unknown to the server, then this node will
node will contain a zero-length string."; contain a zero-length string.";
reference "RFC 6933: entPhysicalModelName";
}
reference "RFC 6933: entPhysicalMfgName"; leaf alias {
} type string {
length "0 .. 32";
}
description
"An 'alias' name for the component, as specified by
a network manager, and provides a non-volatile 'handle'
for the component.
leaf model-name { If an alias has been configured for this component in
type string; /hardware/component/alias, this node contains the
description configured value. If no such alias has been configured,
"The vendor-specific model name identifier string associated the server may set the value of this node to a locally
with this physical component. The preferred value is the unique value.";
customer-visible part number, which may be printed on the reference "RFC 6933: entPhysicalAlias";
component itself. }
If the model name string associated with the physical leaf asset-id {
component is unknown to the server, then this node will type string {
contain a zero-length string."; length "0 .. 32";
reference "RFC 6933: entPhysicalModelName"; }
} description
"This node is a user-assigned asset tracking identifier
(as specified by a network manager) for the component
and provides non-volatile storage of this information.
leaf alias { If an asset tracking identifier has been configured for
type string { this component in /hardware/component/addet-id, this
length "0 .. 32"; node contains the configured value.";
} reference "RFC 6933: entPhysicalAssetID";
description }
"An 'alias' name for the physical entity, as specified by
a network manager, and provides a non-volatile 'handle'
for the physical entity.
If an alias has been configured for this entity in leaf is-fru {
/entity/physical-entity/alias, this node contains the type boolean;
configured value. If no such alias has been configured, description
the server may set the value of this node to a locally "This node indicates whether or not this component
unique value."; is considered a 'field replaceable unit' by the vendor.
reference "RFC 6933: entPhysicalAlias"; 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 "RFC 6933: entPhysicalIsFRU";
}
leaf asset-id { leaf mfg-date {
type string { type yang:date-and-time;
length "0 .. 32"; description
} "The date of manufacturing of the managed component.";
description reference "RFC 6933: entPhysicalMfgDate";
"This node is a user-assigned asset tracking identifier }
(as specified by a network manager) for the physical entity
and provides non-volatile storage of this information.
If an asset tracking identifier has been configured for leaf-list uri {
this entity in /entity/physical-entity/addet-id, this node type inet:uri;
contains the configured value."; description
reference "RFC 6933: entPhysicalAssetID"; "This node contains identification information about the
} component.
leaf is-fru {
type boolean;
description
"This node indicates whether or not this physical entity
is considered a 'field replaceable unit' by the vendor. If
this node contains the value 'true', then this
physical entity identifies a field replaceable unit. For
all physical entities that represent components permanently
contained within a field replaceable unit, the value
'false' should be returned for this node.";
reference "RFC 6933: entPhysicalIsFRU";
}
leaf mfg-date { If uris have been configured for this component in
type yang:date-and-time; /hardware/component/uri, this node contains the
description configured values.";
"The date of manufacturing of the managed entity."; reference "RFC 6933: entPhysicalUris";
reference "RFC 6933: entPhysicalMfgDate"; }
}
leaf-list uri { leaf uuid {
type inet:uri; type yang:uuid;
description description
"This node contains identification information about the "A Universally Unique Identifier of the component.";
physical entity. reference "RFC 6933: entPhysicalUUID";
}
If uris have been configured for this entity in container state {
/entity/physical-entity/uri, this node contains the if-feature entity-state;
configured values."; description
reference "RFC 6933: entPhysicalUris"; "State-related nodes";
} reference "RFC 4268: Entity State MIB";
leaf uuid { leaf state-last-changed {
type yang:uuid; type yang:date-and-time;
description description
"A Universally Unique Identifier of the physical entity."; "The date and time when the value of any of the
reference "RFC 6933: entPhysicalUUID"; admin-state, oper-state, usage-state, alarm-status, or
} standby-status changed for this component.
container state { If there has been no change since the last
if-feature entity-state; re-initialization of the local system, this node
description contains the date and time of local system
"State-related nodes"; initialization. If there has been no change since the
reference "RFC 4268: Entity State MIB"; component was added to the local system, this node
contains the date and time of the insertion.";
reference "RFC 4268: entStateLastChanged";
}
leaf state-last-changed { leaf admin-state {
type yang:date-and-time; type admin-state;
description description
"The date and time when the value of any of the "The administrative state for this component.
admin-state, oper-state, usage-state, alarm-status, or
standby-status changed for this entity.
If there has been no change since the last This node refers to an entities administrative
re-initialization of the local system, this node contains permission to service both other entities within its
the date and time of local system initialization. If containment hierarchy as well other users of its
there has been no change since the entity was added to services defined by means outside the scope of this
the local system, this node contains the date and time of module.
the insertion.";
reference "RFC 4268: entStateLastChanged";
}
leaf admin-state { Some components exhibit only a subset of the
type entity-admin-state; remaining administrative state values. Some entities
description cannot be locked, and hence this node exhibits only the
"The administrative state for this entity. 'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this node does not exhibit the
'shutting-down' state.";
reference "RFC 4268: entStateAdmin";
}
This node refers to an entities administrative permission leaf oper-state {
to service both other entities within its containment type oper-state;
hierarchy as well other users of its services defined by description
means outside the scope of this module. "The operational state for this component.
Some physical entities exhibit only a subset of the Note that this node does not follow the administrative
remaining administrative state values. Some entities state. An administrative state of down does not predict
cannot be locked, and hence this node exhibits only the an operational state of disabled.
'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this node does not exhibit the
'shutting-down' state.";
reference "RFC 4268: entStateAdmin";
}
leaf oper-state { Note that some implementations may not be able to
type entity-oper-state; accurately report oper-state while the admin-state node
description has a value other than 'unlocked'. In these cases, this
"The operational state for this entity. node MUST have a value of 'unknown'.";
reference "RFC 4268: entStateOper";
}
Note that this node does not follow the administrative leaf usage-state {
state. An administrative state of down does not predict type usage-state;
an operational state of disabled. description
"The usage state for this component.
Note that some implementations may not be able to This node refers to a component's ability to service
accurately report oper-state while the admin-state node more components in a containment hierarchy.
has a value other than 'unlocked'. In these cases, this
node MUST have a value of 'unknown'.";
reference "RFC 4268: entStateOper";
}
leaf usage-state {
type entity-usage-state;
description
"The usage state for this entity.
This node refers to an entity's ability to service more Some entities will exhibit only a subset of the usage
physical entities in a containment hierarchy. state values. Entities that are unable to ever service
any entities within a containment hierarchy will always
have a usage state of 'busy'. Some entities will only
ever be able to support one component within its
containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'.";
reference "RFC 4268, entStateUsage";
}
Some entities will exhibit only a subset of the usage leaf alarm-status {
state values. Entities that are unable to ever service type alarm-status;
any entities within a containment hierarchy will always description
have a usage state of 'busy'. Some entities will only "The alarm status for this component. It does not
ever be able to support one entity within its containment include the alarms raised on child components within its
hierarchy and will therefore only exhibit values of containment hierarchy.";
'idle' and 'busy'."; reference "RFC 4268: entStateAlarm";
reference "RFC 4268, entStateUsage"; }
}
leaf alarm-status { leaf standby-status {
type entity-alarm-status; type standby-status;
description description
"The alarm status for this entity. It does not include "The standby status for this component.
the alarms raised on child components within its
containment hierarchy.";
reference "RFC 4268: entStateAlarm";
}
leaf standby-status { Some entities will exhibit only a subset of the
type entity-standby-status; remaining standby state values. If this component
description cannot operate in a standby role, the value of this
"The standby status for this entity. node will always be 'providing-service'.";
reference "RFC 4268: entStateStandby";
}
}
Some entities will exhibit only a subset of the container sensor-data {
remaining standby state values. If this entity when 'derived-from-or-self(../class,
cannot operate in a standby role, the value of this "ianaent:sensor")' {
node will always be 'providing-service'."; description
reference "RFC 4268: entStateStandby"; "Sensor data nodes present for any component of type
} 'sensor'";
} }
if-feature entity-sensor;
description
"Sensor-related nodes.";
reference "RFC 3433: Entity Sensor MIB";
container sensor-data { leaf data-type {
when 'derived-from-or-self(../class, type sensor-data-type;
"iana-entity", "sensor")' { description
description "The type of data units associated with the
"Sensor data nodes present for any entity of type sensor value";
'sensor'"; reference "RFC 3433: entPhySensorType";
} }
if-feature entity-sensor;
description
"Sensor-related nodes.";
reference "RFC 3433: Entity Sensor MIB";
leaf data-type { leaf data-scale {
type entity-sensor-data-type; type sensor-data-scale;
description description
"The type of data units associated with the "The (power of 10) scaling factor associated
sensor value"; with the sensor value";
reference "RFC 3433: entPhySensorType"; reference "RFC 3433: entPhySensorScale";
} }
leaf data-scale { leaf precision {
type entity-sensor-data-scale; type sensor-precision;
description description
"The (power of 10) scaling factor associated "The number of decimal places of precision
with the sensor value"; associated with the sensor value";
reference "RFC 3433: entPhySensorScale"; reference "RFC 3433: entPhySensorPrecision";
} }
leaf precision { leaf value {
type entity-sensor-precision; type sensor-value;
description description
"The number of decimal places of precision "The most recent measurement obtained by the server
associated with the sensor value"; for this sensor.";
reference "RFC 3433: entPhySensorPrecision"; reference "RFC 3433: entPhySensorValue";
} }
leaf value { leaf oper-status {
type entity-sensor-value; type sensor-status;
description description
"The most recent measurement obtained by the server "The operational status of the sensor.";
for this sensor."; reference "RFC 3433: entPhySensorOperStatus";
reference "RFC 3433: entPhySensorValue"; }
}
leaf oper-status { leaf sensor-units-display {
type entity-sensor-status; type string;
description description
"The operational status of the sensor."; "A textual description of the data units that should be
reference "RFC 3433: entPhySensorOperStatus"; used in the display of the sensor value.";
} reference "RFC 3433: entPhySensorUnitsDisplay";
leaf sensor-units-display { }
type string;
description
"A textual description of the data units that should be
used in the display of the sensor value.";
reference "RFC 3433: 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 "RFC 3433: entPhySensorValueTimeStamp";
}
leaf value-timestamp { leaf value-update-rate {
type yang:date-and-time; type uint32;
description units "milliseconds";
"The time the status and/or value of this sensor was description
last obtained by the server."; "An indication of the frequency that the server updates
reference "RFC 3433: entPhySensorValueTimeStamp"; the associated 'value' node, representing in
} milliseconds. The value zero indicates:
leaf value-update-rate { - the sensor value is updated on demand (e.g.,
type uint32; when polled by the server for a get-request),
units "milliseconds"; - the sensor value is updated when the sensor
description value changes (event-driven),
"An indication of the frequency that the server updates - the server does not know the update rate.";
the associated 'value' node, representing in reference "RFC 3433: entPhySensorValueUpdateRate";
milliseconds. The value zero indicates: }
}
}
}
- the sensor value is updated on demand (e.g., /*
when polled by the server for a get-request), * Configuration data nodes
- the sensor value is updated when the sensor */
value changes (event-driven),
- the server does not know the update rate.";
reference "RFC 3433: entPhySensorValueUpdateRate";
}
}
}
}
/* container hardware {
* Configuration data nodes if-feature hardware-config;
*/ description
"Configuration parameters for components.";
container entity { list component {
if-feature entity-config; key name;
description description
"Configuration parameters for physical entities."; "List of configuration data for components.";
list physical-entity { leaf name {
key name; type string;
description description
"List of configuration data for physical entities."; "Administrative name assigned to this component.
No restrictions apply.";
leaf name { }
type string;
description
"Administrative name assigned to this physical entity.
No restrictions apply."; leaf serial-num {
} type string;
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).
leaf serial-num { This node is indented to be used for components
type string; for which the server cannot determine the serial number.";
description reference "RFC 6933: entPhysicalSerialNum";
"The vendor-specific serial number string for the physical }
entity. The preferred value is the serial number string
actually printed on the component itself (if present).
This node is indented to be used for physical entities leaf alias {
for which the server cannot determine the serial number."; type string {
reference "RFC 6933: entPhysicalSerialNum"; length "0 .. 32";
} }
description
"This node is an 'alias' name for the component, as
specified by a network manager, and provides a non-
volatile 'handle' for the component.";
reference "RFC 6933: entPhysicalAlias";
}
leaf alias { leaf asset-id {
type string { type string {
length "0 .. 32"; length "0 .. 32";
} }
description description
"This node is an 'alias' name for the physical entity, as "This node is a user-assigned asset tracking identifier
specified by a network manager, and provides a non-volatile (as specified by a network manager) for the component";
'handle' for the physical entity."; reference "RFC 6933: entPhysicalAssetID";
reference "RFC 6933: entPhysicalAlias"; }
}
leaf asset-id { leaf-list uri {
type string { type inet:uri;
length "0 .. 32"; description
} "This node contains identification information about the
description component.";
"This node is a user-assigned asset tracking identifier reference "RFC 6933: entPhysicalUris";
(as specified by a network manager) for the physical }
entity";
reference "RFC 6933: entPhysicalAssetID";
}
leaf-list uri { leaf admin-state {
type inet:uri; if-feature entity-state;
description type admin-state;
"This node contains identification information about the description
physical entity."; "The administrative state for this component.
reference "RFC 6933: entPhysicalUris";
}
leaf admin-state { This node refers to a component's administrative
if-feature entity-state; permission to service both other entities within
type entity-admin-state; its containment hierarchy as well other users of
description its services defined by means outside the scope
"The administrative state for this entity. of this module.
This node refers to an entity's administrative Some components exhibit only a subset of the
permission to service both other entities within remaining administrative state values. Some entities
its containment hierarchy as well other users of cannot be locked, and hence this node exhibits only
its services defined by means outside the scope the 'unlocked' state. Other entities cannot be shutdown
of this module. gracefully, and hence this node does not exhibit the
'shutting-down' state.";
reference "RFC 4268, entStateAdmin";
}
}
}
Some physical entities exhibit only a subset of the /*
remaining administrative state values. Some entities * Notifications
cannot be locked, and hence this node exhibits only */
the 'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this node does not exhibit the
'shutting-down' state.";
reference "RFC 4268, entStateAdmin";
}
}
}
/* notification harwdare-state-change {
* Notifications description
*/ "A hardware-state-change notification is generated when the
value of /hardware-state/last-change changes.";
reference "RFC 6933, entConfigChange";
}
notification ent-config-change { notification hardware-state-oper-enabled {
description if-feature entity-state;
"An ent-config-change notification is generated when the value description
of /entity-state/last-change changes."; "A hardware-state-oper-enabled notification signifies that
reference "RFC 6933, entConfigChange"; a component has transitioned into the 'enabled' state.";
}
notification ent-state-oper-enabled { leaf name {
if-feature entity-state; type leafref {
description path "/hardware-state/component/name";
"An ent-state-oper-enabled notification signifies that }
an entity has transitioned into the 'enabled' state."; description
"The name of the component that has transitioned into the
'enabled' state.";
}
leaf admin-state {
type leafref {
path "/hardware-state/component/state/admin-state";
}
description
"The administrative state for the component.";
}
leaf alarm-status {
type leafref {
path "/hardware-state/component/state/alarm-status";
}
description
"The alarm status for the component.";
}
reference "RFC 4268, entStateOperEnabled";
}
leaf name { notification hardware-state-oper-disabled {
type leafref { if-feature entity-state;
path "/entity-state/physical-entity/name"; description
} "A hardware-state-oper-disabled notification signifies that
description a component has transitioned into the 'disabled' state.";
"The name of the entity that has transitioned into the
'enabled' state.";
}
leaf admin-state {
type leafref {
path "/entity-state/physical-entity/state/admin-state";
} leaf name {
description type leafref {
"The administrative state for the entity."; path "/hardware-state/component/name";
} }
leaf alarm-status { description
type leafref { "The name of the component that has transitioned into the
path "/entity-state/physical-entity/state/alarm-status"; 'disabled' state.";
} }
description leaf admin-state {
"The alarm status for the entity."; type leafref {
} path "/hardware-state/component/state/admin-state";
reference "RFC 4268, entStateOperEnabled"; }
} description
"The administrative state for the component.";
}
leaf alarm-status {
type leafref {
path "/hardware-state/component/state/alarm-status";
}
description
"The alarm status for the component.";
}
reference "RFC 4268, entStateOperDisabled";
}
notification ent-state-oper-disabled { }
if-feature entity-state;
description
"An ent-state-oper-disabled notification signifies that
an entity has transitioned into the 'disabled' state.";
leaf name { <CODE ENDS>
type leafref { <CODE BEGINS> file "iana-entity@2016-10-25.yang"
path "/entity-state/physical-entity/name";
}
description
"The name of the entity that has transitioned into the
'disabled' state.";
}
leaf admin-state {
type leafref {
path "/entity-state/physical-entity/state/admin-state";
}
description
"The administrative state for the entity.";
}
leaf alarm-status {
type leafref {
path "/entity-state/physical-entity/state/alarm-status";
}
description
"The alarm status for the entity.";
}
reference "RFC 4268, entStateOperDisabled";
}
} module iana-entity {
namespace "urn:ietf:params:xml:ns:yang:iana-entity";
prefix ianaent;
<CODE ENDS> organization "IANA";
Move this to a separate document?: contact
" Internet Assigned Numbers Authority
<CODE BEGINS> file "iana-entity@2016-05-13.yang" Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
module iana-entity { Tel: +1 310 823 9358
namespace "urn:ietf:params:xml:ns:yang:iana-entity"; <mailto:iana@iana.org>";
prefix ianaent;
import ietf-entity { description
prefix ent; "IANA defined identities for physical class.";
} reference
"https://www.iana.org/assignments/ianaentity-mib/ianaentity-mib";
organization "IANA"; // RFC Ed.: replace XXXX with actual RFC number and remove this
contact // note.
" Internet Assigned Numbers Authority
Postal: ICANN // RFC Ed.: update the date below with the date of RFC publication
4676 Admiralty Way, Suite 330 // and remove this note.
Marina del Rey, CA 90292 revision 2016-10-25 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for hardware Management";
}
Tel: +1 310 823 9358 /*
<mailto:iana@iana.org>"; * Identities
*/
description identity entity-physical-class {
"IANA defined identities for physical class."; description
reference "This identity is the base for all physical entity class
"https://www.iana.org/assignments/ianaentity-mib/ianaentity-mib"; identifiers.";
}
// RFC Ed.: replace XXXX with actual RFC number and remove this identity unknown {
// note. base ianaent:entity-physical-class;
description
"This identity is applicable if the physical entity class
is unknown to the server.";
}
// RFC Ed.: update the date below with the date of RFC publication identity chassis {
// and remove this note. base ianaent:entity-physical-class;
revision 2016-05-13 { description
description "This identity is applicable if the physical entity class
"Initial revision."; is an overall container for networking equipment. Any class
reference of physical entity, except a stack, may be contained within a
"RFC XXXX: A YANG Data Model for Entity Management"; chassis; a chassis may only be contained within a stack.";
} }
identity unknown { identity backplane {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is unknown to the server."; is some sort of device for aggregating and forwarding
} networking traffic, such as a shared backplane in a modular
identity chassis { ethernet switch. Note that an implementation may model a
base ent:entity-physical-class; backplane as a single physical entity, which is actually
description implemented as multiple discrete physical components (within a
"This identity is applicable if the physical entity class chassis or stack).";
is an overall container for networking equipment. Any class of }
physical entity, except a stack, may be contained within a
chassis; a chassis may only be contained within a stack.";
}
identity backplane { identity container {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of device for aggregating and forwarding is capable of containing one or more removable physical
networking traffic, such as a shared backplane in a modular entities, possibly of different types. For example, each
ethernet switch. Note that an implementation may model a (empty or full) slot in a chassis will be modeled as a
backplane as a single physical entity, which is actually container. Note that all removable physical entities should
implemented as multiple discrete physical components (within a be modeled within a container entity, such as field-
chassis or stack)."; replaceable modules, fans, or power supplies. Note that all
} known containers should be modeled by the agent, including
empty containers.";
}
identity container { identity power-supply {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is capable of containing one or more removable physical is a power-supplying component.";
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 entities should be
modeled within a container entity, 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 { identity fan {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is a power-supplying component."; is a fan or other heat-reduction component.";
} }
identity fan { identity sensor {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is a fan or other heat-reduction component."; is some sort of sensor, such as a temperature sensor within a
} router chassis.";
identity sensor { }
base ent:entity-physical-class;
description
"This identity is applicable if the physical entity class
is some sort of sensor, such as a temperature sensor within a
router chassis.";
}
identity module { identity module {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of self-contained sub-system. If a 'module' is some sort of self-contained sub-system. If a 'module'
entity is removable, then it should be modeled within a entity is removable, then it should be modeled within a
container entity; otherwise, it should be modeled directly container entity; otherwise, it should be modeled directly
within another physical entity (e.g., a chassis or another within another physical entity (e.g., a chassis or another
module)."; module).";
} }
identity port { identity port {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of networking port, capable of receiving and/or is some sort of networking port, capable of receiving and/or
transmitting networking traffic."; transmitting networking traffic.";
} }
identity stack { identity stack {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of super-container (possibly virtual) intended to is some sort of super-container (possibly virtual) intended to
group together multiple chassis entities. A stack may be group together multiple chassis entities. A stack may be
realized by a 'virtual' cable, a real interconnect cable realized by a 'virtual' cable, a real interconnect cable
attached to multiple chassis, or multiple interconnect cables. attached to multiple chassis, or multiple interconnect cables.
A stack should not be modeled within any other physical A stack should not be modeled within any other physical
entities, but a stack may be contained within another stack. entities, but a stack may be contained within another stack.
Only chassis entities should be contained within a stack."; Only chassis entities should be contained within a stack.";
} }
identity cpu { identity cpu {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of central processing unit."; is some sort of central processing unit.";
} }
identity energy-object { identity energy-object {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of energy object, i.e., a piece of equipment that is some sort of energy object, i.e., a piece of equipment that
is part of or attached to a communications network that is is part of or attached to a communications network that is
monitored, controlled, or aids in the management of another monitored, controlled, or aids in the management of another
device for Energy Management."; device for Energy Management.";
} }
identity battery { identity battery {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of battery."; is some sort of battery.";
} }
identity storage-drive { identity storage-drive {
base ent:entity-physical-class; base ianaent:entity-physical-class;
description description
"This identity is applicable if the physical entity class "This identity is applicable if the physical entity class
is some sort of entity with data storage capability as main is some sort of entity with data storage capability as main
functionality, e.g., disk drive (HDD), solid state device functionality, e.g., disk drive (HDD), solid state device
(SSD), hybrid (SSHD), object storage (OSD) or other."; (SSD), hybrid (SSHD), object storage (OSD) or other.";
} }
} }
<CODE ENDS> <CODE ENDS>
8. IANA Considerations 8. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688]. This document registers a URI in the IETF XML registry [RFC3688].
Following the format in RFC 3688, the following registration is Following the format in RFC 3688, the following registration is
requested to be made. requested to be made.
URI: TBD URI: urn:ietf:params:xml:ns:yang:ietf-hardware
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names This document registers a YANG module in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-entity name: ietf-hardware
namespace: TBD namespace: urn:ietf:params:xml:ns:yang:ietf-hardware
prefix: ent prefix: hw
reference: RFC XXXX reference: RFC XXXX
9. Security Considerations 9. Security Considerations
TBD TBD
10. Acknowledgements 10. Acknowledgements
TBD TBD
11. Normative References 11. Normative References
[I-D.ietf-netmod-rfc6020bis] [I-D.ietf-netmod-rfc6020bis]
Bjorklund, M., "The YANG 1.1 Data Modeling Language", Bjorklund, M., "The YANG 1.1 Data Modeling Language",
draft-ietf-netmod-rfc6020bis-12 (work in progress), April draft-ietf-netmod-rfc6020bis-14 (work in progress), June
2016. 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor
Management Information Base", RFC 3433, DOI 10.17487/ Management Information Base", RFC 3433,
RFC3433, December 2002, DOI 10.17487/RFC3433, December 2002,
<http://www.rfc-editor.org/info/rfc3433>. <http://www.rfc-editor.org/info/rfc3433>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 4268, [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 4268,
DOI 10.17487/RFC4268, November 2005, DOI 10.17487/RFC4268, November 2005,
<http://www.rfc-editor.org/info/rfc4268>. <http://www.rfc-editor.org/info/rfc4268>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M. [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M.
Chandramouli, "Entity MIB (Version 4)", RFC 6933, DOI Chandramouli, "Entity MIB (Version 4)", RFC 6933,
10.17487/RFC6933, May 2013, DOI 10.17487/RFC6933, May 2013,
<http://www.rfc-editor.org/info/rfc6933>. <http://www.rfc-editor.org/info/rfc6933>.
Appendix A. Open Issues
o Should the model support pre-configuration of hardware components?
The current model supports pre-configuration of components
provided the operator knows the name of the component to be
installed. A more useful model would use the parent component,
class, and parent-rel-pos as identification. If the system
detects a component and there is configuration available for the
parent component, class, and parent-rel-pos then the system would
instatiate the component with the provided name, and optionally
additional parameters.
o Is there a need for a standard action 'reset' that can be used to
reset components?
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
YumaWorks YumaWorks
Email: andy@yumaworks.com Email: andy@yumaworks.com
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
Email: mbj@tail-f.com Email: mbj@tail-f.com
skipping to change at page 36, line 20 skipping to change at page 36, line 43
Tail-f Systems Tail-f Systems
Email: mbj@tail-f.com Email: mbj@tail-f.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Dan Romascanu Dan Romascanu
Avaya
Email: dromasca@avaya.com Email: dromasca@gmail.com
 End of changes. 182 change blocks. 
1326 lines changed or deleted 1338 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/