1 module iana-hardware {
\r
3 namespace "urn:ietf:params:xml:ns:yang:iana-hardware";
\r
8 " Internet Assigned Numbers Authority
\r
10 12025 Waterfront Drive, Suite 300
\r
11 Los Angeles, CA 90094-2536
\r
12 United States of America
\r
13 Tel: +1 310 301 5800
\r
14 E-Mail: iana@iana.org>";
\r
17 "IANA-defined identities for hardware class.
\r
18 The latest revision of this YANG module can be obtained from
\r
20 Requests for new values should be made to IANA via
\r
21 email (iana@iana.org).
\r
22 Copyright (c) 2018 IETF Trust and the persons identified as
\r
23 authors of the code. All rights reserved.
\r
24 Redistribution and use in source and binary forms, with or
\r
25 without modification, is permitted pursuant to, and subject
\r
26 to the license terms contained in, the Simplified BSD License
\r
27 set forth in Section 4.c of the IETF Trust's Legal Provisions
\r
28 Relating to IETF Documents
\r
29 (https://trustee.ietf.org/license-info).
\r
30 The initial version of this YANG module is part of RFC 8348;
\r
31 see the RFC itself for full legal notices.";
\r
33 "https://www.iana.org/assignments/yang-parameters";
\r
35 revision 2018-03-13 {
\r
37 "Initial revision.";
\r
39 "RFC 8348: A YANG Data Model for Hardware Management";
\r
46 identity hardware-class {
\r
48 "This identity is the base for all hardware class
\r
53 base ianahw:hardware-class;
\r
55 "This identity is applicable if the hardware class is unknown
\r
60 base ianahw:hardware-class;
\r
62 "This identity is applicable if the hardware class is an
\r
63 overall container for networking equipment. Any class of
\r
64 physical component, except a stack, may be contained within a
\r
65 chassis; a chassis may only be contained within a stack.";
\r
68 identity backplane {
\r
69 base ianahw:hardware-class;
\r
71 "This identity is applicable if the hardware class is some sort
\r
72 of device for aggregating and forwarding networking traffic,
\r
73 such as a shared backplane in a modular ethernet switch. Note
\r
74 that an implementation may model a backplane as a single
\r
75 physical component, which is actually implemented as multiple
\r
76 discrete physical components (within a chassis or stack).";
\r
79 identity container {
\r
80 base ianahw:hardware-class;
\r
82 "This identity is applicable if the hardware class is capable
\r
83 of containing one or more removable physical entities,
\r
84 possibly of different types. For example, each (empty or
\r
85 full) slot in a chassis will be modeled as a container. Note
\r
86 that all removable physical components should be modeled
\r
87 within a container component, such as field-replaceable
\r
88 modules, fans, or power supplies. Note that all known
\r
89 containers should be modeled by the agent, including empty
\r
93 identity power-supply {
\r
94 base ianahw:hardware-class;
\r
96 "This identity is applicable if the hardware class is a
\r
97 power-supplying component.";
\r
101 base ianahw:hardware-class;
\r
103 "This identity is applicable if the hardware class is a fan or
\r
104 other heat-reduction component.";
\r
108 base ianahw:hardware-class;
\r
110 "This identity is applicable if the hardware class is some sort
\r
111 of sensor, such as a temperature sensor within a router
\r
116 base ianahw:hardware-class;
\r
118 "This identity is applicable if the hardware class is some sort
\r
119 of self-contained sub-system. If a module component is
\r
120 removable, then it should be modeled within a container
\r
121 component; otherwise, it should be modeled directly within
\r
122 another physical component (e.g., a chassis or another
\r
127 base ianahw:hardware-class;
\r
129 "This identity is applicable if the hardware class is some sort
\r
130 of networking port capable of receiving and/or transmitting
\r
131 networking traffic.";
\r
135 base ianahw:hardware-class;
\r
137 "This identity is applicable if the hardware class is some sort
\r
138 of super-container (possibly virtual) intended to group
\r
139 together multiple chassis entities. A stack may be realized
\r
140 by a virtual cable, a real interconnect cable attached to
\r
141 multiple chassis, or multiple interconnect cables. A stack
\r
142 should not be modeled within any other physical components,
\r
143 but a stack may be contained within another stack. Only
\r
144 chassis components should be contained within a stack.";
\r
148 base ianahw:hardware-class;
\r
150 "This identity is applicable if the hardware class is some sort
\r
151 of central processing unit.";
\r
154 identity energy-object {
\r
155 base ianahw:hardware-class;
\r
157 "This identity is applicable if the hardware class is some sort
\r
158 of energy object, i.e., it is a piece of equipment that is
\r
159 part of or attached to a communications network that is
\r
160 monitored, it is controlled, or it aids in the management of
\r
161 another device for Energy Management.";
\r
165 base ianahw:hardware-class;
\r
167 "This identity is applicable if the hardware class is some sort
\r
171 identity storage-drive {
\r
172 base ianahw:hardware-class;
\r
174 "This identity is applicable if the hardware class is some sort
\r
175 of component with data storage capability as its main
\r
176 functionality, e.g., hard disk drive (HDD), solid-state device
\r
177 (SSD), solid-state hybrid drive (SSHD), object storage device
\r