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