1 module ietf-hardware {
\r
3 namespace "urn:ietf:params:xml:ns:yang:ietf-hardware";
\r
6 import ietf-inet-types {
\r
9 import ietf-yang-types {
\r
12 import iana-hardware {
\r
17 "IETF NETMOD (Network Modeling) Working Group";
\r
20 "WG Web: <https://datatracker.ietf.org/wg/netmod/>
\r
21 WG List: <mailto:netmod@ietf.org>
\r
22 Editor: Andy Bierman
\r
23 <mailto:andy@yumaworks.com>
\r
24 Editor: Martin Bjorklund
\r
25 <mailto:mbj@tail-f.com>
\r
27 <mailto:jie.dong@huawei.com>
\r
28 Editor: Dan Romascanu
\r
29 <mailto:dromasca@gmail.com>";
\r
32 "This module contains a collection of YANG definitions for
\r
34 This data model is designed for the Network Management Datastore
\r
35 Architecture (NMDA) defined in RFC 8342.
\r
36 Copyright (c) 2018 IETF Trust and the persons identified as
\r
37 authors of the code. All rights reserved.
\r
38 Redistribution and use in source and binary forms, with or
\r
39 without modification, is permitted pursuant to, and subject
\r
40 to the license terms contained in, the Simplified BSD License
\r
41 set forth in Section 4.c of the IETF Trust's Legal Provisions
\r
42 Relating to IETF Documents
\r
43 (https://trustee.ietf.org/license-info).
\r
44 This version of this YANG module is part of RFC 8348; see
\r
45 the RFC itself for full legal notices.";
\r
47 revision 2018-03-13 {
\r
49 "Initial revision.";
\r
51 "RFC 8348: A YANG Data Model for Hardware Management";
\r
58 feature entity-mib {
\r
60 "This feature indicates that the device implements
\r
63 "RFC 6933: Entity MIB (Version 4)";
\r
66 feature hardware-state {
\r
68 "Indicates that ENTITY-STATE-MIB objects are supported";
\r
70 "RFC 4268: Entity State MIB";
\r
73 feature hardware-sensor {
\r
75 "Indicates that ENTITY-SENSOR-MIB objects are supported";
\r
77 "RFC 3433: Entity Sensor Management Information Base";
\r
84 typedef admin-state {
\r
89 "The resource is unable to report administrative state.";
\r
94 "The resource is administratively prohibited from use.";
\r
96 enum shutting-down {
\r
99 "The resource usage is administratively limited to current
\r
100 instances of use.";
\r
105 "The resource is not administratively prohibited from
\r
110 "Represents the various possible administrative states.";
\r
112 "RFC 4268: Entity State MIB - EntityAdminState";
\r
115 typedef oper-state {
\r
120 "The resource is unable to report its operational state.";
\r
125 "The resource is totally inoperable.";
\r
131 "The resource is partially or fully operable.";
\r
136 "The resource is currently being tested and cannot
\r
137 therefore report whether or not it is operational.";
\r
141 "Represents the possible values of operational states.";
\r
143 "RFC 4268: Entity State MIB - EntityOperState";
\r
146 typedef usage-state {
\r
151 "The resource is unable to report usage state.";
\r
156 "The resource is servicing no users.";
\r
161 "The resource is currently in use, and it has sufficient
\r
162 spare capacity to provide for additional users.";
\r
167 "The resource is currently in use, but it currently has no
\r
168 spare capacity to provide for additional users.";
\r
172 "Represents the possible values of usage states.";
\r
174 "RFC 4268: Entity State MIB - EntityUsageState";
\r
177 typedef alarm-state {
\r
182 "The resource is unable to report alarm state.";
\r
187 "The resource is currently being repaired, which, depending
\r
188 on the implementation, may make the other values in this
\r
189 bit string not meaningful.";
\r
194 "One or more critical alarms are active against the
\r
200 "One or more major alarms are active against the
\r
206 "One or more minor alarms are active against the
\r
212 "One or more warning alarms are active against the
\r
215 bit indeterminate {
\r
218 "One or more alarms of whose perceived severity cannot be
\r
219 determined are active against this resource.";
\r
223 "Represents the possible values of alarm states. An alarm is a
\r
224 persistent indication of an error or warning condition.
\r
225 When no bits of this attribute are set, then no active alarms
\r
226 are known against this component and it is not under repair.";
\r
228 "RFC 4268: Entity State MIB - EntityAlarmStatus";
\r
231 typedef standby-state {
\r
236 "The resource is unable to report standby state.";
\r
241 "The resource is not providing service, but it will be
\r
242 immediately able to take over the role of the resource to
\r
243 be backed up, without the need for initialization
\r
244 activity, and will contain the same information as the
\r
245 resource to be backed up.";
\r
247 enum cold-standby {
\r
250 "The resource is to back up another resource, but it will
\r
251 not be immediately able to take over the role of a
\r
252 resource to be backed up and will require some
\r
253 initialization activity.";
\r
255 enum providing-service {
\r
258 "The resource is providing service.";
\r
262 "Represents the possible values of standby states.";
\r
264 "RFC 4268: Entity State MIB - EntityStandbyStatus";
\r
267 typedef sensor-value-type {
\r
272 "A measure other than those listed below.";
\r
277 "An unknown measurement or arbitrary, relative numbers";
\r
282 "A measure of electric potential (alternating current).";
\r
287 "A measure of electric potential (direct current).";
\r
292 "A measure of electric current.";
\r
297 "A measure of power.";
\r
302 "A measure of frequency.";
\r
307 "A measure of temperature.";
\r
312 "A measure of percent relative humidity.";
\r
317 "A measure of shaft revolutions per minute.";
\r
322 "A measure of cubic meters per minute (airflow).";
\r
327 "Value is one of 1 (true) or 2 (false)";
\r
331 "A node using this data type represents the sensor measurement
\r
332 data type associated with a physical sensor value. The actual
\r
333 data units are determined by examining a node of this type
\r
334 together with the associated sensor-value-scale node.
\r
335 A node of this type SHOULD be defined together with nodes of
\r
336 type sensor-value-scale and type sensor-value-precision.
\r
337 These three types are used to identify the semantics of a node
\r
338 of type sensor-value.";
\r
340 "RFC 3433: Entity Sensor Management Information Base -
\r
341 EntitySensorDataType";
\r
344 typedef sensor-value-scale {
\r
349 "Data scaling factor of 10^-24.";
\r
354 "Data scaling factor of 10^-21.";
\r
359 "Data scaling factor of 10^-18.";
\r
364 "Data scaling factor of 10^-15.";
\r
369 "Data scaling factor of 10^-12.";
\r
374 "Data scaling factor of 10^-9.";
\r
379 "Data scaling factor of 10^-6.";
\r
384 "Data scaling factor of 10^-3.";
\r
389 "Data scaling factor of 10^0.";
\r
394 "Data scaling factor of 10^3.";
\r
399 "Data scaling factor of 10^6.";
\r
404 "Data scaling factor of 10^9.";
\r
409 "Data scaling factor of 10^12.";
\r
414 "Data scaling factor of 10^15.";
\r
419 "Data scaling factor of 10^18.";
\r
424 "Data scaling factor of 10^21.";
\r
429 "Data scaling factor of 10^24.";
\r
433 "A node using this data type represents a data scaling factor,
\r
434 represented with an International System of Units (SI) prefix.
\r
435 The actual data units are determined by examining a node of
\r
436 this type together with the associated sensor-value-type.
\r
437 A node of this type SHOULD be defined together with nodes of
\r
438 type sensor-value-type and type sensor-value-precision.
\r
439 Together, associated nodes of these three types are used to
\r
440 identify the semantics of a node of type sensor-value.";
\r
442 "RFC 3433: Entity Sensor Management Information Base -
\r
443 EntitySensorDataScale";
\r
446 typedef sensor-value-precision {
\r
451 "A node using this data type represents a sensor value
\r
453 A node of this type SHOULD be defined together with nodes of
\r
454 type sensor-value-type and type sensor-value-scale. Together,
\r
455 associated nodes of these three types are used to identify the
\r
456 semantics of a node of type sensor-value.
\r
457 If a node of this type contains a value in the range 1 to 9,
\r
458 it represents the number of decimal places in the fractional
\r
459 part of an associated sensor-value fixed-point number.
\r
460 If a node of this type contains a value in the range -8 to -1,
\r
461 it represents the number of accurate digits in the associated
\r
462 sensor-value fixed-point number.
\r
463 The value zero indicates the associated sensor-value node is
\r
464 not a fixed-point number.
\r
465 Server implementers must choose a value for the associated
\r
466 sensor-value-precision node so that the precision and accuracy
\r
467 of the associated sensor-value node is correctly indicated.
\r
468 For example, a component representing a temperature sensor
\r
469 that can measure 0 to 100 degrees C in 0.1 degree
\r
470 increments, +/- 0.05 degrees, would have a
\r
471 sensor-value-precision value of '1', a sensor-value-scale
\r
472 value of 'units', and a sensor-value ranging from '0' to
\r
473 '1000'. The sensor-value would be interpreted as
\r
474 'degrees C * 10'.";
\r
476 "RFC 3433: Entity Sensor Management Information Base -
\r
477 EntitySensorPrecision";
\r
480 typedef sensor-value {
\r
482 range "-1000000000 .. 1000000000";
\r
485 "A node using this data type represents a sensor value.
\r
486 A node of this type SHOULD be defined together with nodes of
\r
487 type sensor-value-type, type sensor-value-scale, and
\r
488 type sensor-value-precision. Together, associated nodes of
\r
489 those three types are used to identify the semantics of a node
\r
491 The semantics of a node using this data type are determined by
\r
492 the value of the associated sensor-value-type node.
\r
493 If the associated sensor-value-type node is equal to 'voltsAC',
\r
494 'voltsDC', 'amperes', 'watts', 'hertz', 'celsius', or 'cmm',
\r
495 then a node of this type MUST contain a fixed-point number
\r
496 ranging from -999,999,999 to +999,999,999. The value
\r
497 -1000000000 indicates an underflow error. The value
\r
498 +1000000000 indicates an overflow error. The
\r
499 sensor-value-precision indicates how many fractional digits
\r
500 are represented in the associated sensor-value node.
\r
501 If the associated sensor-value-type node is equal to
\r
502 'percentRH', then a node of this type MUST contain a number
\r
503 ranging from 0 to 100.
\r
504 If the associated sensor-value-type node is equal to 'rpm',
\r
505 then a node of this type MUST contain a number ranging from
\r
506 -999,999,999 to +999,999,999.
\r
507 If the associated sensor-value-type node is equal to
\r
508 'truth-value', then a node of this type MUST contain either the
\r
509 value 1 (true) or the value 2 (false).
\r
510 If the associated sensor-value-type node is equal to 'other' or
\r
511 'unknown', then a node of this type MUST contain a number
\r
512 ranging from -1000000000 to 1000000000.";
\r
514 "RFC 3433: Entity Sensor Management Information Base -
\r
515 EntitySensorValue";
\r
518 typedef sensor-status {
\r
523 "Indicates that the server can obtain the sensor value.";
\r
528 "Indicates that the server presently cannot obtain the
\r
531 enum nonoperational {
\r
534 "Indicates that the server believes the sensor is broken.
\r
535 The sensor could have a hard failure (disconnected wire)
\r
536 or a soft failure such as out-of-range, jittery, or wildly
\r
537 fluctuating readings.";
\r
541 "A node using this data type represents the operational status
\r
542 of a physical sensor.";
\r
544 "RFC 3433: Entity Sensor Management Information Base -
\r
545 EntitySensorStatus";
\r
552 container hardware {
\r
554 "Data nodes representing components.
\r
555 If the server supports configuration of hardware components,
\r
556 then this data model is instantiated in the configuration
\r
557 datastores supported by the server. The leaf-list 'datastore'
\r
558 for the module 'ietf-hardware' in the YANG library provides
\r
559 this information.";
\r
562 type yang:date-and-time;
\r
565 "The time the '/hardware/component' list changed in the
\r
566 operational state.";
\r
572 "List of components.
\r
573 When the server detects a new hardware component, it
\r
574 initializes a list entry in the operational state.
\r
575 If the server does not support configuration of hardware
\r
576 components, list entries in the operational state are
\r
577 initialized with values for all nodes as detected by the
\r
579 Otherwise, this procedure is followed:
\r
580 1. If there is an entry in the '/hardware/component' list
\r
581 in the intended configuration with values for the nodes
\r
582 'class', 'parent', and 'parent-rel-pos' that are equal
\r
583 to the detected values, then the list entry in the
\r
584 operational state is initialized with the configured
\r
585 values, including the 'name'.
\r
586 2. Otherwise (i.e., there is no matching configuration
\r
587 entry), the list entry in the operational state is
\r
588 initialized with values for all nodes as detected by
\r
589 the implementation.
\r
590 If the '/hardware/component' list in the intended
\r
591 configuration is modified, then the system MUST behave as if
\r
592 it re-initializes itself and follow the procedure in (1).";
\r
594 "RFC 6933: Entity MIB (Version 4) - entPhysicalEntry";
\r
599 "The name assigned to this component.
\r
600 This name is not required to be the same as
\r
606 base ianahw:hardware-class;
\r
610 "An indication of the general hardware type of the
\r
613 "RFC 6933: Entity MIB (Version 4) - entPhysicalClass";
\r
616 leaf physical-index {
\r
617 if-feature entity-mib;
\r
619 range "1..2147483647";
\r
623 "The entPhysicalIndex for the entPhysicalEntry represented
\r
624 by this list entry.";
\r
626 "RFC 6933: Entity MIB (Version 4) - entPhysicalIndex";
\r
633 "A textual description of the component. This node should
\r
634 contain a string that identifies the manufacturer's name
\r
635 for the component and should be set to a distinct value
\r
636 for each version or model of the component.";
\r
638 "RFC 6933: Entity MIB (Version 4) - entPhysicalDescr";
\r
643 path "../../component/name";
\r
644 require-instance false;
\r
647 "The name of the component that physically contains this
\r
649 If this leaf is not instantiated, it indicates that this
\r
650 component is not contained in any other component.
\r
651 In the event that a physical component is contained by
\r
652 more than one physical component (e.g., double-wide
\r
653 modules), this node contains the name of one of these
\r
654 components. An implementation MUST use the same name
\r
655 every time this node is instantiated.";
\r
657 "RFC 6933: Entity MIB (Version 4) - entPhysicalContainedIn";
\r
660 leaf parent-rel-pos {
\r
662 range "0 .. 2147483647";
\r
665 "An indication of the relative position of this child
\r
666 component among all its sibling components. Sibling
\r
667 components are defined as components that:
\r
668 o share the same value of the 'parent' node and
\r
669 o share a common base identity for the 'class' node.
\r
670 Note that the last rule gives implementations flexibility
\r
671 in how components are numbered. For example, some
\r
672 implementations might have a single number series for all
\r
673 components derived from 'ianahw:port', while some others
\r
674 might have different number series for different
\r
675 components with identities derived from 'ianahw:port' (for
\r
676 example, one for registered jack 45 (RJ45) and one for
\r
677 small form-factor pluggable (SFP)).";
\r
680 "RFC 6933: Entity MIB (Version 4) -
\r
681 entPhysicalParentRelPos";
\r
684 leaf-list contains-child {
\r
686 path "../../component/name";
\r
690 "The name of the contained component.";
\r
692 "RFC 6933: Entity MIB (Version 4) - entPhysicalChildIndex";
\r
695 leaf hardware-rev {
\r
699 "The vendor-specific hardware revision string for the
\r
700 component. The preferred value is the hardware revision
\r
701 identifier actually printed on the component itself (if
\r
704 "RFC 6933: Entity MIB (Version 4) -
\r
705 entPhysicalHardwareRev";
\r
708 leaf firmware-rev {
\r
712 "The vendor-specific firmware revision string for the
\r
715 "RFC 6933: Entity MIB (Version 4) -
\r
716 entPhysicalFirmwareRev";
\r
719 leaf software-rev {
\r
724 "The vendor-specific software revision string for the
\r
727 "RFC 6933: Entity MIB (Version 4) -
\r
728 entPhysicalSoftwareRev";
\r
735 "The vendor-specific serial number string for the
\r
736 component. The preferred value is the serial number
\r
737 string actually printed on the component itself (if
\r
740 "RFC 6933: Entity MIB (Version 4) - entPhysicalSerialNum";
\r
747 "The name of the manufacturer of this physical component.
\r
748 The preferred value is the manufacturer name string
\r
749 actually printed on the component itself (if present).
\r
750 Note that comparisons between instances of the
\r
751 'model-name', 'firmware-rev', 'software-rev', and
\r
752 'serial-num' nodes are only meaningful amongst components
\r
753 with the same value of 'mfg-name'.
\r
754 If the manufacturer name string associated with the
\r
755 physical component is unknown to the server, then this
\r
756 node is not instantiated.";
\r
758 "RFC 6933: Entity MIB (Version 4) - entPhysicalMfgName";
\r
765 "The vendor-specific model name identifier string
\r
766 associated with this physical component. The preferred
\r
767 value is the customer-visible part number, which may be
\r
768 printed on the component itself.
\r
769 If the model name string associated with the physical
\r
770 component is unknown to the server, then this node is not
\r
773 "RFC 6933: Entity MIB (Version 4) - entPhysicalModelName";
\r
779 "An 'alias' name for the component, as specified by a
\r
780 network manager, that provides a non-volatile 'handle' for
\r
782 If no configured value exists, the server MAY set the
\r
783 value of this node to a locally unique value in the
\r
785 A server implementation MAY map this leaf to the
\r
786 entPhysicalAlias MIB object. Such an implementation needs
\r
787 to use some mechanism to handle the differences in size
\r
788 and characters allowed between this leaf and
\r
789 entPhysicalAlias. The definition of such a mechanism is
\r
790 outside the scope of this document.";
\r
792 "RFC 6933: Entity MIB (Version 4) - entPhysicalAlias";
\r
798 "This node is a user-assigned asset tracking identifier for
\r
800 A server implementation MAY map this leaf to the
\r
801 entPhysicalAssetID MIB object. Such an implementation
\r
802 needs to use some mechanism to handle the differences in
\r
803 size and characters allowed between this leaf and
\r
804 entPhysicalAssetID. The definition of such a mechanism is
\r
805 outside the scope of this document.";
\r
807 "RFC 6933: Entity MIB (Version 4) - entPhysicalAssetID";
\r
815 "This node indicates whether or not this component is
\r
816 considered a 'field-replaceable unit' by the vendor. If
\r
817 this node contains the value 'true', then this component
\r
818 identifies a field-replaceable unit. For all components
\r
819 that are permanently contained within a field-replaceable
\r
820 unit, the value 'false' should be returned for this
\r
823 "RFC 6933: Entity MIB (Version 4) - entPhysicalIsFRU";
\r
827 type yang:date-and-time;
\r
830 "The date of manufacturing of the managed component.";
\r
832 "RFC 6933: Entity MIB (Version 4) - entPhysicalMfgDate";
\r
838 "This node contains identification information about the
\r
841 "RFC 6933: Entity MIB (Version 4) - entPhysicalUris";
\r
848 "A Universally Unique Identifier of the component.";
\r
850 "RFC 6933: Entity MIB (Version 4) - entPhysicalUUID";
\r
854 if-feature hardware-state;
\r
856 "State-related nodes";
\r
858 "RFC 4268: Entity State MIB";
\r
860 leaf state-last-changed {
\r
861 type yang:date-and-time;
\r
864 "The date and time when the value of any of the
\r
865 admin-state, oper-state, usage-state, alarm-state, or
\r
866 standby-state changed for this component.
\r
867 If there has been no change since the last
\r
868 re-initialization of the local system, this node
\r
869 contains the date and time of local system
\r
870 initialization. If there has been no change since the
\r
871 component was added to the local system, this node
\r
872 contains the date and time of the insertion.";
\r
874 "RFC 4268: Entity State MIB - entStateLastChanged";
\r
880 "The administrative state for this component.
\r
881 This node refers to a component's administrative
\r
882 permission to service both other components within its
\r
883 containment hierarchy as well other users of its
\r
884 services defined by means outside the scope of this
\r
886 Some components exhibit only a subset of the remaining
\r
887 administrative state values. Some components cannot be
\r
888 locked; hence, this node exhibits only the 'unlocked'
\r
889 state. Other components cannot be shut down gracefully;
\r
890 hence, this node does not exhibit the 'shutting-down'
\r
893 "RFC 4268: Entity State MIB - entStateAdmin";
\r
900 "The operational state for this component.
\r
901 Note that this node does not follow the administrative
\r
902 state. An administrative state of 'down' does not
\r
903 predict an operational state of 'disabled'.
\r
904 Note that some implementations may not be able to
\r
905 accurately report oper-state while the admin-state node
\r
906 has a value other than 'unlocked'. In these cases, this
\r
907 node MUST have a value of 'unknown'.";
\r
909 "RFC 4268: Entity State MIB - entStateOper";
\r
916 "The usage state for this component.
\r
917 This node refers to a component's ability to service
\r
918 more components in a containment hierarchy.
\r
919 Some components will exhibit only a subset of the usage
\r
920 state values. Components that are unable to ever
\r
921 service any components within a containment hierarchy
\r
922 will always have a usage state of 'busy'. In some
\r
923 cases, a component will be able to support only one
\r
924 other component within its containment hierarchy and
\r
925 will therefore only exhibit values of 'idle' and
\r
928 "RFC 4268: Entity State MIB - entStateUsage";
\r
935 "The alarm state for this component. It does not
\r
936 include the alarms raised on child components within its
\r
937 containment hierarchy.";
\r
939 "RFC 4268: Entity State MIB - entStateAlarm";
\r
942 leaf standby-state {
\r
943 type standby-state;
\r
946 "The standby state for this component.
\r
947 Some components will exhibit only a subset of the
\r
948 remaining standby state values. If this component
\r
949 cannot operate in a standby role, the value of this node
\r
950 will always be 'providing-service'.";
\r
952 "RFC 4268: Entity State MIB - entStateStandby";
\r
956 container sensor-data {
\r
957 when 'derived-from-or-self(../class,
\r
958 "ianahw:sensor")' {
\r
960 "Sensor data nodes present for any component of type
\r
963 if-feature hardware-sensor;
\r
967 "Sensor-related nodes.";
\r
969 "RFC 3433: Entity Sensor Management Information Base";
\r
974 "The most recent measurement obtained by the server
\r
976 A client that periodically fetches this node should also
\r
977 fetch the nodes 'value-type', 'value-scale', and
\r
978 'value-precision', since they may change when the value
\r
981 "RFC 3433: Entity Sensor Management Information Base -
\r
982 entPhySensorValue";
\r
986 type sensor-value-type;
\r
988 "The type of data units associated with the
\r
991 "RFC 3433: Entity Sensor Management Information Base -
\r
995 type sensor-value-scale;
\r
997 "The (power of 10) scaling factor associated
\r
998 with the sensor value";
\r
1000 "RFC 3433: Entity Sensor Management Information Base -
\r
1001 entPhySensorScale";
\r
1004 leaf value-precision {
\r
1005 type sensor-value-precision;
\r
1007 "The number of decimal places of precision
\r
1008 associated with the sensor value";
\r
1010 "RFC 3433: Entity Sensor Management Information Base -
\r
1011 entPhySensorPrecision";
\r
1014 leaf oper-status {
\r
1015 type sensor-status;
\r
1017 "The operational status of the sensor.";
\r
1019 "RFC 3433: Entity Sensor Management Information Base -
\r
1020 entPhySensorOperStatus";
\r
1023 leaf units-display {
\r
1026 "A textual description of the data units that should be
\r
1027 used in the display of the sensor value.";
\r
1029 "RFC 3433: Entity Sensor Management Information Base -
\r
1030 entPhySensorUnitsDisplay";
\r
1033 leaf value-timestamp {
\r
1034 type yang:date-and-time;
\r
1036 "The time the status and/or value of this sensor was last
\r
1037 obtained by the server.";
\r
1039 "RFC 3433: Entity Sensor Management Information Base -
\r
1040 entPhySensorValueTimeStamp";
\r
1042 leaf value-update-rate {
\r
1044 units "milliseconds";
\r
1046 "An indication of the frequency that the server updates
\r
1047 the associated 'value' node, represented in
\r
1048 milliseconds. The value zero indicates:
\r
1049 - the sensor value is updated on demand (e.g.,
\r
1050 when polled by the server for a get-request),
\r
1051 - the sensor value is updated when the sensor
\r
1052 value changes (event-driven), or
\r
1053 - the server does not know the update rate.";
\r
1055 "RFC 3433: Entity Sensor Management Information Base -
\r
1056 entPhySensorValueUpdateRate";
\r
1066 notification hardware-state-change {
\r
1068 "A hardware-state-change notification is generated when the
\r
1069 value of /hardware/last-change changes in the operational
\r
1072 "RFC 6933: Entity MIB (Version 4) - entConfigChange";
\r
1075 notification hardware-state-oper-enabled {
\r
1076 if-feature hardware-state;
\r
1078 "A hardware-state-oper-enabled notification signifies that a
\r
1079 component has transitioned into the 'enabled' state.";
\r
1083 path "/hardware/component/name";
\r
1087 "The name of the component that has transitioned into the
\r
1088 'enabled' state.";
\r
1090 leaf admin-state {
\r
1092 path "/hardware/component/state/admin-state";
\r
1095 "The administrative state for the component.";
\r
1097 leaf alarm-state {
\r
1099 path "/hardware/component/state/alarm-state";
\r
1102 "The alarm state for the component.";
\r
1105 "RFC 4268: Entity State MIB - entStateOperEnabled";
\r
1108 notification hardware-state-oper-disabled {
\r
1109 if-feature hardware-state;
\r
1111 "A hardware-state-oper-disabled notification signifies that a
\r
1112 component has transitioned into the 'disabled' state.";
\r
1116 path "/hardware/component/name";
\r
1119 "The name of the component that has transitioned into the
\r
1120 'disabled' state.";
\r
1122 leaf admin-state {
\r
1124 path "/hardware/component/state/admin-state";
\r
1127 "The administrative state for the component.";
\r
1129 leaf alarm-state {
\r
1131 path "/hardware/component/state/alarm-state";
\r
1135 "The alarm state for the component.";
\r
1138 "RFC 4268: Entity State MIB - entStateOperDisabled";
\r