draft-ietf-eman-energy-monitoring-mib-13.txt   rfc7460.txt 
Network Working Group M. Chandramouli Internet Engineering Task Force (IETF) M. Chandramouli
B. Claise Request for Comments: 7460 B. Claise
Internet-Draft Cisco Systems, Inc. Category: Standards Track Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening ISSN: 2070-1721 B. Schoening
Expires: May 27 2015 Independent Consultant Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe, Ltd.
Nov 27 2014 March 2015
Power, Energy Monitoring and Control MIB
draft-ietf-eman-energy-monitoring-mib-13
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as
"work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License.
Abstract
This document defines a subset of the Management Information Monitoring and Control MIB for Power and Energy
Base (MIB) for power and energy monitoring of devices.
Conventions used in this document Abstract
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL This document defines a subset of the Management Information Base
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", (MIB) for power and energy monitoring of devices.
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119].
Table of Contents Status of This Memo
1. Introduction ............................................... 3 This is an Internet Standards Track document.
2. The Internet-Standard Management Framework ................. 4
3. Use Cases .................................................. 4
4. Terminology ................................................ 4
5. Architecture Concepts Applied to the MIB Modules ........... 5
5.1. Energy Object Tables ..................................... 5
5.1.1. ENERGY-OBJECT-MIB ...................................... 5
5.1.2. POWER-ATTRIBUTES-MIB ................................... 7
5.1.3. UML Diagram ............................................ 9
5.2. Energy Object Identity .................................. 11
5.3.1. Power State Set ................................. 13
5.4. Energy Object Usage Information ......................... 13
5.5. Optional Power Usage Attributes ......................... 14
5.6. Optional Energy Measurement ............................. 14
5.7. Fault Management ........................................ 18
6. Discovery ................................................. 18
7. Link with the other IETF MIBs ............................. 19
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB ... 19
7.2. Link with the ENTITY-STATE MIB ....................... 20
7.3. Link with the POWER-OVER-ETHERNET MIB ................ 21
7.4. Link with the UPS MIB ................................ 21
7.5. Link with the LLDP and LLDP-MED MIBs ................. 22
8. Structure of the MIB....................................... 23
9. MIB Definitions ........................................... 24
9.1. The IANAPowerStateSet-MIB MIB Module ................. 24
9.2. The ENERGY-OBJECT-MIB MIB Module ..................... 26
9.3. The POWER-ATTRIBUTES-MIB MIB Module .................. 48
10. Implementation Status .................................... 61
10.1. SNMP Research .......................................... 61
10.2. Cisco Systems .......................................... 62
11. Security Considerations .................................. 62
12. IANA Considerations....................................... 63
12.1. IANAPowerStateSet-MIB module ........................... 64
13. Contributors ............................................. 64
14. Acknowledgment ........................................... 64
15. References ............................................... 65
15.1. Normative References ................................... 65
15.2. Informative References ................................. 65
1. Introduction This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This document defines a subset of the Management Information Information about the current status of this document, any errata,
Base (MIB) for use in energy management of devices within or and how to provide feedback on it may be obtained at
connected to communication networks. The MIB modules in this http://www.rfc-editor.org/info/rfc7460.
document are designed to provide a model for energy management,
which includes monitoring for Power State and energy consumption
of networked elements. This MIB takes into account the Energy
Management Framework [RFC7326], which, in turn, is based on the
Requirements for Energy Management [RFC6988].
Energy management can be applied to devices in communication Copyright Notice
networks. Target devices for this specification include (but are
not limited to): routers, switches, Power over Ethernet (PoE)
endpoints, protocol gateways for building management systems,
intelligent meters, home energy gateways, hosts and servers,
sensor proxies, etc. Target devices and the use cases for Energy
Management are discussed in Energy Management Applicability
Statement [EMAN-AS].
Where applicable, device monitoring extends to the individual Copyright (c) 2015 IETF Trust and the persons identified as the
components of the device and to any attached dependent devices. document authors. All rights reserved.
For example: A device can contain components that are
independent from a power-state point of view, such as line
cards, processor cards, hard drives. A device can also have
dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints.
2. The Internet-Standard Management Framework This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
For a detailed overview of the documents that describe the Table of Contents
current Internet-Standard Management Framework, please refer to
section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, 1. Introduction ....................................................3
termed the Management Information Base or MIB. MIB objects are 1.1. Conventions Used in This Document ..........................3
generally accessed through the Simple Network Management 2. The Internet-Standard Management Framework ......................3
Protocol (SNMP). Objects in the MIB are defined using the 3. Use Cases .......................................................4
mechanisms defined in the Structure of Management Information 4. Terminology .....................................................4
(SMI). This memo specifies MIB modules that are compliant to 5. Architecture Concepts Applied to the MIB Modules ................5
SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 5.1. Energy Object Tables .......................................5
RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 5.1.1. ENERGY-OBJECT-MIB ...................................5
5.1.2. POWER-ATTRIBUTES-MIB ................................7
5.1.3. UML Diagram .........................................9
5.2. Energy Object Identity ....................................12
5.3. Power State ...............................................12
5.3.1. Power State Set ....................................13
5.4. Energy Object Usage Information ...........................13
5.5. Optional Power Usage Attributes ...........................14
5.6. Optional Energy Measurement ...............................14
5.7. Fault Management ..........................................18
6. Discovery ......................................................18
7. Link with the Other IETF MIBs ..................................19
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB ........19
7.2. Link with the ENTITY-STATE MIB ............................20
7.3. Link with the POWER-OVER-ETHERNET MIB .....................21
7.4. Link with the UPS MIB .....................................21
7.5. Link with the LLDP and LLDP-MED MIBs ......................22
8. Structure of the MIB ...........................................23
9. MIB Definitions ................................................24
9.1. The IANAPowerStateSet-MIB Module ..........................24
9.2. The ENERGY-OBJECT-MIB MIB Module ..........................27
9.3. The POWER-ATTRIBUTES-MIB MIB Module .......................50
10. Security Considerations .......................................63
11. IANA Considerations ...........................................64
11.1. IANAPowerStateSet-MIB Module .............................65
12. References ....................................................65
12.1. Normative References .....................................65
12.2. Informative References ...................................66
Acknowledgments ...................................................68
Contributors ......................................................68
Authors' Addresses ................................................69
3. Use Cases 1. Introduction
Requirements for power and energy monitoring for networking This document defines a subset of the Management Information Base
devices are specified in [RFC6988]. The requirements in (MIB) for use in energy management of devices within or connected to
[RFC6988] cover devices typically found in communications communication networks. The MIB modules in this document are
networks, such as switches, routers, and various connected designed to provide a model for energy management, which includes
endpoints. For a power monitoring architecture to be useful, it monitoring for Power State and energy consumption of networked
should also apply to facility meters, power distribution units, elements. This MIB takes into account the "Energy Management
gateway proxies for commercial building control, home automation Framework" [RFC7326], which, in turn, is based on the "Requirements
devices, and devices that interface with the utility and/or for Energy Management" [RFC6988].
smart grid. Accordingly, the scope of the MIB modules in this
document are broader than that specified in [RFC6988]. Several
use cases for Energy Management have been identified in the
"Energy Management (EMAN) Applicability Statement" [EMAN-AS].
4. Terminology Energy management can be applied to devices in communication
networks. Target devices for this specification include (but are not
limited to) routers, switches, Power over Ethernet (PoE) endpoints,
protocol gateways for building management systems, intelligent
meters, home energy gateways, hosts and servers, sensor proxies, etc.
Target devices and the use cases for Energy Management are discussed
in Energy Management Applicability Statement [EMAN-AS].
Please refer to [RFC7326] for the definitions of the Where applicable, device monitoring extends to the individual
following terminology used in this draft. components of the device and to any attached dependent devices. For
example, a device can contain components that are independent from a
Power State point of view, such as line cards, processor cards, hard
drives. A device can also have dependent attached devices, such as a
switch with PoE endpoints or a power distribution unit with attached
endpoints.
Energy Management 1.1. Conventions Used in This Document
Energy Management System (EnMS)
Energy Monitoring
Energy Control
electrical equipment
non-electrical equipment (mechanical equipment)
device
component
power inlet
power outlet
energy
power
demand
provide energy
receive energy
meter (energy meter)
battery
Power Interface
Nameplate Power
Power Attributes
Power Quality
Power State
Power State Set
5. Architecture Concepts Applied to the MIB Modules The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
This section describes the concepts specified in the Energy 2. The Internet-Standard Management Framework
Management Framework [RFC7326] that pertain to power usage, with
specific information related to the MIB module specified in this
document. This subsection maps concepts developed in the Energy
Management Framework [RFC7326].
The Energy Monitoring MIB has 2 independent MIB modules, ENERGY- For a detailed overview of the documents that describe the current
OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first, ENERGY-OBJECT- Internet-Standard Management Framework, please refer to section 7 of
MIB, is focused on measurement of power and energy. The second, RFC 3410 [RFC3410].
POWER-ATTRIBUTES-MIB, is focused on power quality measurements
for Energy Objects.
Devices and their sub-components can be modeled using the Managed objects are accessed via a virtual information store, termed
containment tree of the ENTITY-MIB [RFC6933]. the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies MIB
modules that are compliant to SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
5.1. Energy Object Tables 3. Use Cases
5.1.1. ENERGY-OBJECT-MIB Requirements for power and energy monitoring for networking devices
are specified in [RFC6988]. The requirements in [RFC6988] cover
devices typically found in communications networks, such as switches,
routers, and various connected endpoints. For a power monitoring
architecture to be useful, it should also apply to facility meters,
power distribution units, gateway proxies for commercial building
control, home automation devices, and devices that interface with the
utility and/or smart grid. Accordingly, the scope of the MIB modules
in this document are broader than that specified in [RFC6988].
Several use cases for Energy Management have been identified in the
"Energy Management (EMAN) Applicability Statement" [EMAN-AS].
The ENERGY-OBJECT-MIB module consists of five tables. 4. Terminology
The first table is the eoMeterCapabilitiesTable. It indicates Please refer to [RFC7326] for the definitions of the following
the instrumentation available for each Energy Object. Entries terminology used in this document.
in this table indicate which other tables from the ENERGY-
OBJECT-MIB and POWER-ATTRIBUTES-MIB are available for each
Energy Object. The eoMeterCapabilitiesTable is indexed by
entPhysicalIndex [RFC6933].
The second table is the eoPowerTable. It reports the power Energy Management
consumption of each Energy Object, as well as the units, sign, Energy Management System (EnMS)
measurement accuracy, and related objects. The eoPowerTable is Energy Monitoring
indexed by entPhysicalIndex. Energy Control
electrical equipment
non-electrical equipment (mechanical equipment)
device
component
power inlet
power outlet
energy
power
demand
provide energy
receive energy
meter (energy meter)
battery
Power Interface
Nameplate Power
Power Attributes
Power Quality
Power State
Power State Set
The third table is the eoPowerStateTable. For each Energy 5. Architecture Concepts Applied to the MIB Modules
Object, it reports information and statistics about the
supported Power States. The eoPowerStateTable is indexed by
entPhysicalIndex and eoPowerStateIndex.
The fourth table is the eoEnergyParametersTable. The entries in This section describes the concepts specified in the Energy
this table configure the parameters of energy and demand Management Framework [RFC7326] that pertain to power usage, with
measurement collection. This table is indexed by specific information related to the MIB module specified in this
eoEnergyParametersIndex. document. This subsection maps concepts developed in the Energy
Management Framework [RFC7326].
The fifth table is the eoEnergyTable. The entries in this table The Energy Monitoring MIB has two independent MIB modules: ENERGY-
provide a log of the energy and demand information. This table OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first, ENERGY-OBJECT-MIB,
is indexed by eoEnergyParametersIndex. is focused on measurement of power and energy. The second, POWER-
A "smidump-style" tree presentation of the MIB modules contained ATTRIBUTES-MIB, is focused on power quality measurements for Energy
in the draft is presented. The meaning of the three symbols is a Objects.
compressed representation of the object's MAX-ACCESS clause
which may have the following values:
"not-accessible" -> "---" Devices and their sub-components can be modeled using the containment
"accessible-for-notify" -> "--n" tree of the ENTITY-MIB [RFC6933].
"read-only" -> "r-n"
"read-write" -> "rwn"
eoMeterCapabilitiesTable(1) 5.1. Energy Object Tables
|
+---eoMeterCapabilitiesEntry(1)[entPhysicalIndex]
| |
| +---r-n BITS eoMeterCapability
|
eoPowerTable(2) 5.1.1. ENERGY-OBJECT-MIB
|
+---eoPowerEntry(1) [entPhysicalIndex]
| |
| +---r-n Integer32 eoPower(1)
| +-- r-n Unsigned32 eoPowerNamePlate(2)
| +-- r-n UnitMultiplier eoPowerUnitMultiplier(3)
| +-- r-n Integer32 eoPowerAccuracy(4)
| +-- r-n INTEGER eoPowerMeasurementCaliber(5)
| +-- r-n INTEGER eoPowerCurrentType(6)
| +-- r-n TruthValue eoPowerMeasurementLocal(7)
| +-- rwn PowerStateSet eoPowerAdminState(8)
| +-- r-n PowerStateSet eoPowerOperState(9)
| +-- r-n OwnerString eoPowerStateEnterReason(10)
|
|
|
+---eoPowerStateTable(3)
|
| +--eoPowerStateEntry(1)
| | [entPhysicalIndex, eoPowerStateIndex]
| |
| +-- --n PowerStateSet eoPowerStateIndex(1)
| +-- r-n Integer32 eoPowerStateMaxPower(2)
| +-- r-n UnitMultiplier
| eoPowerStatePowerUnitMultiplier(3)
| +-- r-n TimeTicks eoPowerStateTotalTime(4)
| +-- r-n Counter32 eoPowerStateEnterCount(5)
|
+eoEnergyParametersTable(4)
|
+---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
|
| +-- --n PhysicalIndex eoEnergyObjectIndex(1)
| + r-n Integer32 eoEnergyParametersIndex(2)
| +-- rwn TimeInterval eoEnergyParametersIntervalLength(3)
| +-- rwn Unsigned32 eoEnergyParametersIntervalNumber(4)
| +-- rwn INTEGER eoEnergyParametersIntervalMode(5)
| +-- rwn TimeInterval eoEnergyParametersIntervalWindow(6)
| +-- rwn Unsigned32 eoEnergyParametersSampleRate(7)
| +-- rwn StorageType eoEnergyParametersStorageType(8)
| +-- rwn RowStatus eoEnergyParametersStatus(9)
|
+eoEnergyTable(5)
|
+---eoEnergyEntry(1)
| [eoEnergyParametersIndex,eoEnergyCollectionStartTime]
|
| +-- r-n TimeTicks eoEnergyCollectionStartTime(1)
| +-- r-n Unsigned32 eoEnergyConsumed(2)
| +-- r-n Unsigned32 eoEnergyProvided(3)
| +-- r-n Unsigned32 eoEnergyStored(4)
| +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5)
| +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Unsigned32 eoEnergyMaxConsumed(7)
| +-- r-n Unsigned32 eoEnergyMaxProduced(8)
| +-- r-n TimeTicks eoEnergyDiscontinuityTime(9)
5.1.2. POWER-ATTRIBUTES-MIB The ENERGY-OBJECT-MIB module consists of five tables.
The POWER-ATTRIBUTES-MIB module consists of three tables. The first table is the eoMeterCapabilitiesTable. It indicates the
instrumentation available for each Energy Object. Entries in this
table indicate which other tables from the ENERGY-OBJECT-MIB and
POWER-ATTRIBUTES-MIB are available for each Energy Object. The
eoMeterCapabilitiesTable is indexed by entPhysicalIndex [RFC6933].
The first table is the eoACPwrAttributesTable. It indicates the The second table is the eoPowerTable. It reports the power
power quality available for each Energy Object. The consumption of each Energy Object as well as the units, sign,
eoACPwrAttributesTable is indexed by entPhysicalIndex [RFC6933]. measurement accuracy, and related objects. The eoPowerTable is
indexed by entPhysicalIndex.
The second table is the eoACPwrAttributesDelPhaseTable. The The third table is the eoPowerStateTable. For each Energy Object, it
entries in this table configure the parameters of energy and reports information and statistics about the supported Power States.
demand measurement collection. This table is indexed by The eoPowerStateTable is indexed by entPhysicalIndex and
eoEnergyParametersIndex. eoPowerStateIndex.
The third table is the eoACPwrAttributesWyePhaseTable. For each The fourth table is the eoEnergyParametersTable. The entries in this
Energy Object, it reports information and statistics about the table configure the parameters of energy and demand measurement
supported Power States. The eoPowerStateTable is indexed by collection. This table is indexed by eoEnergyParametersIndex.
entPhysicalIndex and eoPowerStateIndex.
eoACPwrAttributesTable(1) The fifth table is the eoEnergyTable. The entries in this table
| provide a log of the energy and demand information. This table is
+---eoACPwrAttributesEntry(1) [ entPhysicalIndex] indexed by eoEnergyParametersIndex.
| |
| +---r-n INTEGER eoACPwrAttributesConfiguration(1)
| +-- r-n Integer32 eoACPwrAttributesAvgVoltage(2)
| +-- r-n Unsigned32 eoACPwrAttributesAvgCurrent(3)
| +-- r-n Integer32 eoACPwrAttributesFrequency(4)
| +-- r-n UnitMultiplier
| eoACPwrAttributesPowerUnitMultiplier(5)
| +-- r-n Integer32 eoACPwrAttributesPowerAccuracy(6)
| +-- r-n Integer32
| eoACPwrAttributesTotalActivePower(7)
| +-- r-n Integer32
| eoACPwrAttributesTotalReactivePower(8)
| +-- r-n Integer32
| eoACPwrAttributesTotalApparentPower(9)
| +-- r-n Integer32
| eoACPwrAttributesTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrAttributesThdCurrent(11)
| +-- r-n Integer32 eoACPwrAttributesThdVoltage(12)
|
+eoACPwrAttributesDelPhaseTable(2)
|
+-- eoACPwrAttributesDelPhaseEntry(1)
| | [entPhysicalIndex, eoACPwrAttributesDelPhaseIndex]
| |
| +-- r-n Integer32
| | eoACPwrAttributesDelPhaseIndex(1)
| +-- r-n Integer32
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage(2)
| +-- r-n Integer32
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(3)
| |
+eoACPwrAttributesWyePhaseTable(3)
|
+-- eoACPwrAttributesWyePhaseEntry(1)
| | [entPhysicalIndex, eoACPwrAttributesWyePhaseIndex]
| |
| +-- r-n Integer32
| | eoACPwrAttributesWyePhaseIndex(1)
| +-- r-n Integer32
| | eoACPwrAttributesWyePhaseToNeutralVoltage(2)
| +-- r-n Integer32
| | eoACPwrAttributesWyeCurrent(3)
| +-- r-n Integer32
| | eoACPwrAttributesWyeActivePower(4)
| +-- r-n Integer32
| | eoACPwrAttributesWyeReactivePower(5)
| +-- r-n Integer32
| | eoACPwrAttributesWyeApparentPower(6)
| +-- r-n Integer32
| | eoACPwrAttributesWyePowerFactor(7)
| +-- r-n Integer32
| | eoACPwrAttributesWyeThdCurrent(9)
| +-- r-n Integer32
| | eoACPwrAttributesWyeThdPhaseToNeutralVoltage(10)
5.1.3. UML Diagram A "smidump-style" tree presentation of the MIB modules contained in
the document is presented. The meaning of the three symbols is a
compressed representation of the object's MAX-ACCESS clause, which
may have the following values:
A UML diagram representation of the MIB objects in the two MIB "not-accessible" -> "---"
modules ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB is presented. "accessible-for-notify" -> "--n"
"read-only" -> "r-n"
"read-write" -> "rwn"
+-----------------------+ eoMeterCapabilitiesTable(1)
| Meter Capabilities | |
| --------------------- | +---eoMeterCapabilitiesEntry(1)[entPhysicalIndex]
| eoMeterCapability | | |
+-----------------------+ | +---r-n BITS eoMeterCapability
|
+-----------------------+ eoPowerTable(2)
|---> | Energy Object ID (*) |
| | --------------------- |
| | entPhysicalIndex |
| | entPhysicalClass |
| | entPhysicalName |
| | entPhysicalUUID |
| +-----------------------+
| |
| +---------------------------+ +---eoPowerEntry(1) [entPhysicalIndex]
|---- |_ Power Table | | |
| | ------------------------- | | +---r-n Integer32 eoPower(1)
| | eoPower | | +-- r-n Unsigned32 eoPowerNamePlate(2)
| | eoPowerNamePlate | | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3)
| | eoPowerUnitMultiplier | | +-- r-n Integer32 eoPowerAccuracy(4)
| | eoPowerAccuracy | | +-- r-n INTEGER eoPowerMeasurementCaliber(5)
| | eoPowerMeasurementCaliber | | +-- r-n INTEGER eoPowerCurrentType(6)
| | eoPowerCurrentType | | +-- r-n TruthValue eoPowerMeasurementLocal(7)
| | eoPowerMeasurementLocal | | +-- rwn PowerStateSet eoPowerAdminState(8)
| | eoPowerAdminState | | +-- r-n PowerStateSet eoPowerOperState(9)
| | eoPowerOperState | | +-- r-n OwnerString eoPowerStateEnterReason(10)
| | eoPowerStateEnterReason |
| +---------------------------+
| |
| +---------------------------------+
|---- |_Energy Object State Statistics |
| |-------------------------------- |
| | eoPowerStateIndex |
| | eoPowerStateMaxPower |
| | eoPowerStatePowerUnitMultiplier |
| | eoPowerStateTotalTime |
| | eoPowerStateEnterCount |
| +---------------------------------+
| |
| +----------------------------------+
|---- | Energy ParametersTable |
| | -------------------------------- |
| | eoEnergyObjectIndex |
| | eoEnergyParametersIndex |
| | eoEnergyParametersIntervalLength |
| | eoEnergyParametersIntervalNumber |
| | eoEnergyParametersIntervalMode |
| | eoEnergyParametersIntervalWindow |
| | eoEnergyParametersSampleRate |
| | eoEnergyParametersStorageType |
| | eoEnergyParametersStatus |
| +----------------------------------+
| |
| +----------------------------------+ +---eoPowerStateTable(3)
|---- | Energy Table |
| -------------------------------- |
| eoEnergyCollectionStartTime |
| eoEnergyConsumed |
| eoEnergyProvided |
| eoEnergyStored |
| eoEnergyUnitMultiplier |
| eoEnergyAccuracy |
| eoEnergyMaxConsumed |
| eoEnergyMaxProduced |
| eoDiscontinuityTime |
+----------------------------------+
Figure 1:UML diagram for energyObjectMib
(*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
+-----------------------+
|---> | Energy Object ID (*) |
| | --------------------- |
| | entPhysicalIndex |
| | entPhysicalName |
| | entPhysicalUUID |
| +-----------------------+
| |
| +--------------------------------------+ | +--eoPowerStateEntry(1)
|---- | Power Attributes | | | [entPhysicalIndex, eoPowerStateIndex]
| | ------------------------------------ | | |
| | eoACPwrAttributesConfiguration | | +-- --n PowerStateSet eoPowerStateIndex(1)
| | eoACPwrAttributesAvgVoltage | | +-- r-n Integer32 eoPowerStateMaxPower(2)
| | eoACPwrAttributesAvgCurrent | | +-- r-n UnitMultiplier
| | eoACPwrAttributesFrequency | | eoPowerStatePowerUnitMultiplier(3)
| | eoACPwrAttributesPowerUnitMultiplier | | +-- r-n TimeTicks eoPowerStateTotalTime(4)
| | eoACPwrAttributesPowerAccuracy | | +-- r-n Counter32 eoPowerStateEnterCount(5)
| | eoACPwrAttributesTotalActivePower |
| | eoACPwrAttributesTotalReactivePower |
| | eoACPwrAttributesTotalApparentPower |
| | eoACPwrAttributesTotalPowerFactor |
| | eoACPwrAttributesThdCurrent |
| | eoACPwrAttributesThdVoltage |
| +--------------------------------------+
| |
+eoEnergyParametersTable(4)
| |
| +------------------------------------------------+ +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
|---- | AC Input DEL Configuration |
| | ---------------------------------------------- |
| | eoACPwrAttributesDelPhaseIndex |
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage |
| +------------------------------------------------+
| |
| +-- --n PhysicalIndex eoEnergyObjectIndex(1)
| + r-n Integer32 eoEnergyParametersIndex(2)
| +-- rwn TimeInterval eoEnergyParametersIntervalLength(3)
| +-- rwn Unsigned32 eoEnergyParametersIntervalNumber(4)
| +-- rwn INTEGER eoEnergyParametersIntervalMode(5)
| +-- rwn TimeInterval eoEnergyParametersIntervalWindow(6)
| +-- rwn Unsigned32 eoEnergyParametersSampleRate(7)
| +-- rwn StorageType eoEnergyParametersStorageType(8)
| +-- rwn RowStatus eoEnergyParametersStatus(9)
| |
| +----------------------------------------------+ +eoEnergyTable(5)
|---- | AC Input WYE Configuration | |
| -------------------------------------------- | +---eoEnergyEntry(1)
| eoACPwrAttributesWyePhaseIndex | | [eoEnergyParametersIndex,eoEnergyCollectionStartTime]
| eoACPwrAttributesWyePhaseToNeutralVoltage | |
| eoACPwrAttributesWyeCurrent | | +-- r-n TimeTicks eoEnergyCollectionStartTime(1)
| eoACPwrAttributesWyeActivePower | | +-- r-n Unsigned32 eoEnergyConsumed(2)
| eoACPwrAttributesWyeReactivePower | | +-- r-n Unsigned32 eoEnergyProvided(3)
| eoACPwrAttributesWyeApparentPower | | +-- r-n Unsigned32 eoEnergyStored(4)
| eoACPwrAttributesWyePowerFactor | | +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5)
| eoACPwrAttributesWyeThdCurrent | | +-- r-n Integer32 eoEnergyAccuracy(6)
| eoACPwrAttributesWyeThdPhaseToNeutralVoltage | | +-- r-n Unsigned32 eoEnergyMaxConsumed(7)
+----------------------------------------------+ | +-- r-n Unsigned32 eoEnergyMaxProduced(8)
| +-- r-n TimeTicks eoEnergyDiscontinuityTime(9)
Figure 2: UML diagram for the POWER-ATTRIBUTES-MIB
(*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
5.2. Energy Object Identity
The Energy Object identity information is specified in the 5.1.2. POWER-ATTRIBUTES-MIB
ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB] primary table,
i.e., the eoTable. In this table, Energy Object context such as
domain, role description, and importance are specified. In
addition, the ENERGY-OBJECT-CONTEXT-MIB module specifies the
relationship between Energy Objects. There are several possible
relationships between Energy Objects, such as meteredBy,
metering, poweredBy, powering, aggregatedBy, and aggregating as
defined in the IANA-ENERGY-RELATION-MIB module [EMAN-AWARE-MIB].
5.3. Power State The POWER-ATTRIBUTES-MIB module consists of three tables.
An Energy Object may have energy conservation modes called Power The first table is the eoACPwrAttributesTable. It indicates the
States. Between the ON and OFF states of a device, there can be power quality available for each Energy Object. The
several intermediate energy saving modes. Those energy saving eoACPwrAttributesTable is indexed by entPhysicalIndex [RFC6933].
modes are called Power States.
Power States, which represent universal states of power The second table is the eoACPwrAttributesDelPhaseTable. The entries
management of an Energy Object, are specified by the in this table configure the parameters of energy and demand
eoPowerState MIB object. The actual Power State is specified by measurement collection. This table is indexed by
the eoPowerOperState MIB object, while the eoPowerAdminState MIB eoEnergyParametersIndex.
object specifies the Power State requested for the Energy
Object. The difference between the values of eoPowerOperState
and eoPowerAdminState indicates that the Energy Object is busy
transitioning from eoPowerAdminState into the eoPowerOperState,
at which point it will update the content of eoPowerOperState.
In addition, the possible reason for change in Power State is
reported in eoPowerStateEnterReason. Regarding
eoPowerStateEnterReason, management stations and Energy Objects
should support any format of the owner string dictated by the
local policy of the organization. It is suggested that this
name contain at least the reason for the transition change, and
one or more of the following: IP address, management station
name, network manager's name, location, or phone number.
The MIB objects eoPowerOperState, eoPowerAdminState , and The third table is the eoACPwrAttributesWyePhaseTable. For each
eoPowerStateEnterReason are contained in the eoPowerTable MIB Energy Object, it reports information and statistics about the
table. supported Power States. The eoPowerStateTable is indexed by
entPhysicalIndex and eoPowerStateIndex.
The eoPowerStateTable table enumerates the maximum power usage eoACPwrAttributesTable(1)
in watts for every single supported Power State of each Power |
State Set supported by the Energy Object. In addition, +---eoACPwrAttributesEntry(1) [ entPhysicalIndex]
PowerStateTable provides additional statistics such as | |
eoPowerStateEnterCount, i.e., the number of times an entity has | +---r-n INTEGER eoACPwrAttributesConfiguration(1)
visited a particular Power State, and eoPowerStateTotalTime, | +-- r-n Integer32 eoACPwrAttributesAvgVoltage(2)
i.e., the total time spent in a particular Power State of an | +-- r-n Unsigned32 eoACPwrAttributesAvgCurrent(3)
Energy Object. | +-- r-n Integer32 eoACPwrAttributesFrequency(4)
| +-- r-n UnitMultiplier
| eoACPwrAttributesPowerUnitMultiplier(5)
| +-- r-n Integer32 eoACPwrAttributesPowerAccuracy(6)
| +-- r-n Integer32
| eoACPwrAttributesTotalActivePower(7)
| +-- r-n Integer32
| eoACPwrAttributesTotalReactivePower(8)
| +-- r-n Integer32
| eoACPwrAttributesTotalApparentPower(9)
| +-- r-n Integer32
| eoACPwrAttributesTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrAttributesThdCurrent(11)
| +-- r-n Integer32 eoACPwrAttributesThdVoltage(12)
|
+eoACPwrAttributesDelPhaseTable(2)
|
+-- eoACPwrAttributesDelPhaseEntry(1)
| | [entPhysicalIndex, eoACPwrAttributesDelPhaseIndex]
| |
| +-- r-n Integer32
| | eoACPwrAttributesDelPhaseIndex(1)
| +-- r-n Integer32
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage(2)
| +-- r-n Integer32
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(3)
| |
+eoACPwrAttributesWyePhaseTable(3)
|
+-- eoACPwrAttributesWyePhaseEntry(1)
| | [entPhysicalIndex, eoACPwrAttributesWyePhaseIndex]
| |
| +-- r-n Integer32
| | eoACPwrAttributesWyePhaseIndex(1)
| +-- r-n Integer32
| | eoACPwrAttributesWyePhaseToNeutralVoltage(2)
| +-- r-n Integer32
| | eoACPwrAttributesWyeCurrent(3)
| +-- r-n Integer32
| | eoACPwrAttributesWyeActivePower(4)
| +-- r-n Integer32
| | eoACPwrAttributesWyeReactivePower(5)
| +-- r-n Integer32
| | eoACPwrAttributesWyeApparentPower(6)
| +-- r-n Integer32
| | eoACPwrAttributesWyePowerFactor(7)
| +-- r-n Integer32
| | eoACPwrAttributesWyeThdCurrent(9)
| +-- r-n Integer32
| | eoACPwrAttributesWyeThdPhaseToNeutralVoltage(10)
5.3.1. Power State Set 5.1.3. UML Diagram
There are several standards and implementations of Power State A Unified Modeling Language (UML) diagram representation of the MIB
Sets. An Energy Object can support one or multiple Power State objects in the two MIB modules, ENERGY-OBJECT-MIB and POWER-
Set implementations concurrently. ATTRIBUTES-MIB, is presented.
There are currently three Power State Sets defined: +-----------------------+
| Meter Capabilities |
| --------------------- |
| eoMeterCapability |
+-----------------------+
IEEE1621(256) - [IEEE1621] +-----------------------+
DMTF(512) - [DMTF] |---> | Energy Object ID (*) |
EMAN(768) - [RFC7326] | | --------------------- |
| | entPhysicalIndex |
| | entPhysicalClass |
| | entPhysicalName |
| | entPhysicalUUID |
| +-----------------------+
|
| +---------------------------+
|---- |_ Power Table |
| | ------------------------- |
| | eoPower |
| | eoPowerNamePlate |
| | eoPowerUnitMultiplier |
| | eoPowerAccuracy |
| | eoPowerMeasurementCaliber |
| | eoPowerCurrentType |
| | eoPowerMeasurementLocal |
| | eoPowerAdminState |
| | eoPowerOperState |
| | eoPowerStateEnterReason |
| +---------------------------+
| +---------------------------------+
|---- |_Energy Object State Statistics |
| |-------------------------------- |
| | eoPowerStateIndex |
| | eoPowerStateMaxPower |
| | eoPowerStatePowerUnitMultiplier |
| | eoPowerStateTotalTime |
| | eoPowerStateEnterCount |
| +---------------------------------+
|
| +----------------------------------+
|---- | Energy ParametersTable |
| | -------------------------------- |
| | eoEnergyObjectIndex |
| | eoEnergyParametersIndex |
| | eoEnergyParametersIntervalLength |
| | eoEnergyParametersIntervalNumber |
| | eoEnergyParametersIntervalMode |
| | eoEnergyParametersIntervalWindow |
| | eoEnergyParametersSampleRate |
| | eoEnergyParametersStorageType |
| | eoEnergyParametersStatus |
| +----------------------------------+
|
| +----------------------------------+
|---- | Energy Table |
| -------------------------------- |
| eoEnergyCollectionStartTime |
| eoEnergyConsumed |
| eoEnergyProvided |
| eoEnergyStored |
| eoEnergyUnitMultiplier |
| eoEnergyAccuracy |
| eoEnergyMaxConsumed |
| eoEnergyMaxProduced |
| eoDiscontinuityTime |
+----------------------------------+
The Power State Sets are listed in [RFC7326] along with each Figure 1: UML Diagram for energyObjectMib
Power State within the Power Set. The Power State Sets are
specified by the PowerStateSet Textual as an IANA-maintained MIB
module. The initial version of this MIB module is specified in
this document.
5.4. Energy Object Usage Information (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
+-----------------------+
|---> | Energy Object ID (*) |
| | --------------------- |
| | entPhysicalIndex |
| | entPhysicalName |
| | entPhysicalUUID |
| +-----------------------+
| +--------------------------------------+
|---- | Power Attributes |
| | ------------------------------------ |
| | eoACPwrAttributesConfiguration |
| | eoACPwrAttributesAvgVoltage |
| | eoACPwrAttributesAvgCurrent |
| | eoACPwrAttributesFrequency |
| | eoACPwrAttributesPowerUnitMultiplier |
| | eoACPwrAttributesPowerAccuracy |
| | eoACPwrAttributesTotalActivePower |
| | eoACPwrAttributesTotalReactivePower |
| | eoACPwrAttributesTotalApparentPower |
| | eoACPwrAttributesTotalPowerFactor |
| | eoACPwrAttributesThdCurrent |
| | eoACPwrAttributesThdVoltage |
| +--------------------------------------+
| +------------------------------------------------+
|---- | AC Input DEL Configuration |
| | ---------------------------------------------- |
| | eoACPwrAttributesDelPhaseIndex |
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage |
| +------------------------------------------------+
|
| +----------------------------------------------+
|---- | AC Input WYE Configuration |
| -------------------------------------------- |
| eoACPwrAttributesWyePhaseIndex |
| eoACPwrAttributesWyePhaseToNeutralVoltage |
| eoACPwrAttributesWyeCurrent |
| eoACPwrAttributesWyeActivePower |
| eoACPwrAttributesWyeReactivePower |
| eoACPwrAttributesWyeApparentPower |
| eoACPwrAttributesWyePowerFactor |
| eoACPwrAttributesWyeThdCurrent |
| eoACPwrAttributesWyeThdPhaseToNeutralVoltage |
+----------------------------------------------+
For an Energy Object, power usage is reported using eoPower. Figure 2: UML Diagram for the POWER-ATTRIBUTES-MIB
The magnitude of measurement is based on the
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
Textual Convention (TC). Power measurement magnitude should
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
[IEC.62053-22] definition of unit multiplier for the SI (System
International) units of measure. Measured values are
represented in SI units obtained by BaseValue * 10 raised to the
power of the unit multiplier.
For example, if current power usage of an Energy Object is 3, it (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of
eoPowerUnitMultiplier. Note that other measurements throughout
the two MIB modules in this document use the same mechanism,
including eoPowerStatePowerUnitMultiplier,
eoEnergyUnitMultiplier, and oACPwrAttributesPowerUnitMultiplier.
In addition to knowing the usage and magnitude, it is useful to 5.2. Energy Object Identity
know how an eoPower measurement was obtained. An NMS can use
this to account for the accuracy and nature of the reading
between different implementations. eoPowerMeasurementLocal
describes whether the measurements were made at the device
itself or from a remote source. The eoPowerMeasurementCaliber
describes the method that was used to measure the power and can
distinguish actual or estimated values. There may be devices in
the network, which may not be able to measure or report power
consumption. For those devices, the object
eoPowerMeasurementCaliber shall report that the measurement
mechanism is "unavailable" and the eoPower measurement shall be
"0".
The nameplate power rating of an Energy Object is specified in The Energy Object identity information is specified in the ENERGY-
eoPowerNameplate MIB object. OBJECT-CONTEXT-MIB module [RFC7461] primary table, i.e., the eoTable.
In this table, Energy Object context such as domain, role
description, and importance are specified. In addition, the ENERGY-
OBJECT-CONTEXT-MIB module specifies the relationship between Energy
Objects. There are several possible relationships between Energy
Objects, such as meteredBy, metering, poweredBy, powering,
aggregatedBy, and aggregating as defined in the IANA-ENERGY-RELATION-
MIB module [RFC7461].
5.5. Optional Power Usage Attributes 5.3. Power State
The optional POWER-ATTRIBUTES-MIB module can be implemented to An Energy Object may have energy-conservation modes called "Power
further describe power usage attributes measurement. The POWER- States". There may be several intermediate energy-saving modes
ATTRIBUTES-MIB module is aligned with IEC 61850 7-2 standard to between the ON and OFF states of a device.
describe AC measurements.
The POWER-ATTRIBUTES-MIB module contains a primary table, Power States, which represent universal states of power management of
eoACPwrAttributesTable, that defines power attributes an Energy Object, are specified by the eoPowerState MIB object. The
measurements for supported entPhysicalIndex entities, as a actual Power State is specified by the eoPowerOperState MIB object,
sparse extension of the eoPowerTable (with entPhysicalIndex as while the eoPowerAdminState MIB object specifies the Power State
primary index). This eoACPwrAttributesTable table contains such requested for the Energy Object. The difference between the values
information as the configuration (single phase, DEL 3 phases, of eoPowerOperState and eoPowerAdminState indicates that the Energy
WYE 3 phases), voltage, frequency, power accuracy, total Object is busy transitioning from eoPowerAdminState into the
active/reactive power/apparent power, amperage, and voltage. eoPowerOperState, at which point it will update the content of
eoPowerOperState. In addition, the possible reason for a change in
Power State is reported in eoPowerStateEnterReason. Regarding
eoPowerStateEnterReason, management stations and Energy Objects
should support any format of the owner string dictated by the local
policy of the organization. It is suggested that this name contain
at least the reason for the transition change, and one or more of the
following: IP address, management station name, network manager's
name, location, or phone number.
In case of 3-phase power, an additional table is populated with The MIB objects eoPowerOperState, eoPowerAdminState, and
Power Attributes measurements per phase (hence, double indexed eoPowerStateEnterReason are contained in the eoPowerTable.
by the entPhysicalIndex and a phase index). This table,
describes attributes specific to either WYE or DEL
configurations.
In a DEL configuration, the eoACPwrAttributesDelPhaseTable eoPowerStateTable enumerates the maximum power usage in watts for
describes the phase-to-phase power attributes measurements, every single supported Power State of each Power State Set supported
i.e., voltage. In a DEL configuration, the current is equal in by the Energy Object. In addition, eoPowerStateTable provides
all three phases. additional statistics such as eoPowerStateEnterCount, i.e., the
number of times an entity has visited a particular Power State, and
eoPowerStateTotalTime, i.e., the total time spent in a particular
Power State of an Energy Object.
In a WYE configuration, the eoACPwrAttributesWyePhaseTable 5.3.1. Power State Set
describes the phase-to-neutral power attributes measurements,
i.e., voltage, current, active/reactive/apparent power, and
power factor.
5.6. Optional Energy Measurement There are several standards and implementations of Power State Sets.
An Energy Object can support one or multiple Power State Set
implementations concurrently.
It is only relevant to measure energy and demand when there are There are currently three Power State Sets defined:
actual power measurements obtained from measurement hardware. If
the eoPowerMeasurementCaliber MIB object has values of
unavailable, unknown, estimated, or presumed, then the energy
and demand values are not useful.
Two tables are introduced to characterize energy measurement of IEEE1621(256) - [IEEE1621]
an Energy Object: eoEnergyTable and eoEnergyParametersTable. DMTF(512) - [DMTF]
Both energy and demand information can be represented via the EMAN(768) - [RFC7326]
eoEnergyTable. Demand information can be represented.
The eoEnergyParametersTable consists of the parameters defining
eoEnergyParametersIndex - an index for the Energy Object,
eoEnergyObjectIndex - linked to the entPhysicalIndex of the
Energy Object, the duration of measurement intervals in seconds,
(eoEnergyParametersIntervalLength), the number of successive
intervals to be stored in the eoEnergyTable,
(eoEnergyParametersIntervalNumber), the type of measurement
technique (eoEnergyParametersIntervalMode), and a sample rate
used to calculate the average (eoEnergyParametersSampleRate).
Judicious choice of the sampling rate will ensure accurate
measurement of energy while not imposing an excessive polling
burden.
There are three eoEnergyParametersIntervalMode types used for The Power State Sets are listed in [RFC7326] along with each Power
energy measurement collection: period, sliding, and total. The State within the Power Set. The Power State Sets are specified by
choices of the three different modes of collection are based on the PowerStateSet Textual Convention (TC) as an IANA-maintained MIB
IEC standard 61850-7-4. Note that multiple module. The initial version of this MIB module is specified in this
eoEnergyParametersIntervalMode types MAY be configured document.
simultaneously. It is important to note that for a given Energy
Object, multiple modes (periodic, total, sliding window) of
energy measurement collection can be configured with the use of
eoEnergyParametersIndex. However, simultaneous measurement in
multiple modes for a given Energy Object depends on the Energy
Object capability.
These three eoEnergyParametersIntervalMode types are illustrated 5.4. Energy Object Usage Information
by the following three figures, for which:
- The horizontal axis represents the current time, with the For an Energy Object, power usage is reported using eoPower. The
symbol <--- L ---> expressing the magnitude of measurement is based on the eoPowerUnitMultiplier MIB
eoEnergyParametersIntervalLength, and the variable, based on the UnitMultiplier TC. Power measurement
eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, magnitude should conform to the IEC 62053-21 [IEC.62053-21] and IEC
..., Sx where x is the value of 62053-22 [IEC.62053-22] definition of unit multiplier for the SI
eoEnergyParametersIntervalNumber. units of measure (where SI is the International System of Units).
Measured values are represented in SI units obtained by BaseValue *
10 raised to the power of the unit multiplier.
- The vertical axis represents the time interval of sampling and For example, if current power usage of an Energy Object is 3, it
the value of eoEnergyConsumed can be obtained at the end of the could be 3 W, 3 mW, 3 kW, or 3 MW, depending on the value of
sampling period. The symbol =========== denotes the duration of eoPowerUnitMultiplier. Note that other measurements throughout the
the sampling period. two MIB modules in this document use the same mechanism, including
eoPowerStatePowerUnitMultiplier, eoEnergyUnitMultiplier, and
oACPwrAttributesPowerUnitMultiplier.
| | | =========== | In addition to knowing the usage and magnitude, it is useful to know
|============ | | | how an eoPower measurement was obtained. A Network Management System
| | | | (NMS) can use this to account for the accuracy and nature of the
| |============ | | reading between different implementations. eoPowerMeasurementLocal
| | | | describes whether the measurements were made at the device itself or
| <--- L ---> | <--- L ---> | <--- L ---> | from a remote source. The eoPowerMeasurementCaliber describes the
| | | | method that was used to measure the power and can distinguish actual
S1 S2 S3 S4 or estimated values. There may be devices in the network that may
not be able to measure or report power consumption. For those
devices, the object eoPowerMeasurementCaliber shall report that the
measurement mechanism is "unavailable" and the eoPower measurement
shall be "0".
Figure 3 : Period eoEnergyParametersIntervalMode The nameplate power rating of an Energy Object is specified in
eoPowerNameplate MIB object.
A eoEnergyParametersIntervalMode type of 'period' specifies non- 5.5. Optional Power Usage Attributes
overlapping periodic measurements. Therefore, the next
eoEnergyCollectionStartTime is equal to the previous
eoEnergyCollectionStartTime plus
eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ...
|============ | The optional POWER-ATTRIBUTES-MIB module can be implemented to
| | further describe power attributes usage measurement. The POWER-
| <--- L ---> | ATTRIBUTES-MIB module is aligned with the IEC 61850 7-2 standard to
| | describe alternating current (AC) measurements.
| |============ |
| | |
| | <--- L ---> |
| | |
| | |============ |
| | | |
| | | <--- L ---> |
| | | |
| | | |============ |
| | | | |
| | | | <--- L ---> |
S1 | | | |
| | | |
| | | |
S2 | | |
| | |
| | |
S3 | |
| |
| |
S4
Figure 4 : Sliding eoEnergyParametersIntervalMode The POWER-ATTRIBUTES-MIB module contains a primary table,
eoACPwrAttributesTable, that defines power attributes measurements
for supported entPhysicalIndex entities, as a sparse extension of the
eoPowerTable (with entPhysicalIndex as primary index). This
eoACPwrAttributesTable table contains such information as the
configuration (single phase, DEL 3 phases, WYE 3 phases), frequency,
power accuracy, total active/reactive power/apparent power, amperage,
and voltage.
A eoEnergyParametersIntervalMode type of 'sliding' specifies In case of three-phase power, an additional table is populated with
overlapping periodic measurements. power attributes measurements per phase (hence, double indexed by the
entPhysicalIndex and a phase index). This table, describes
attributes specific to either WYE or DEL configurations.
| | In a DEL configuration, the eoACPwrAttributesDelPhaseTable describes
|========================= | the phase-to-phase power attributes measurements, i.e., voltage. In
| | a DEL configuration, the current is equal in all three phases.
| |
| |
| <--- Total length ---> |
| |
S1
Figure 5 : Total eoEnergyParametersIntervalMode In a WYE configuration, the eoACPwrAttributesWyePhaseTable describes
the phase-to-neutral power attributes measurements, i.e., voltage,
current, active/reactive/apparent power, and power factor.
A eoEnergyParametersIntervalMode type of 'total' specifies a 5.6. Optional Energy Measurement
continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy It is only relevant to measure energy and demand when there are
usage logging. The status of this variable is "active" when all actual power measurements obtained from measurement hardware. If the
the objects in eoEnergyParametersTable are appropriate which in eoPowerMeasurementCaliber MIB object has values of unavailable,
turn indicates if eoEnergyTable entries exist or not. Finally, unknown, estimated, or presumed, then the energy and demand values
the eoEnergyParametersStorageType variable indicates the storage are not useful.
type for this row, i.e. whether the persistence is maintained
across a device reload.
The eoEnergyTable consists of energy measurements in Two tables are introduced to characterize energy measurement of an
eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units Energy Object: eoEnergyTable and eoEnergyParametersTable. Both
of the measured energy eoEnergyUnitMultiplier, and the maximum energy and demand information can be represented via the
observed energy within a window eoEnergyMaxConsumed, eoEnergyTable. Demand information can be represented. The
eoEnergyMaxProduced. eoEnergyParametersTable consists of the parameters defining
eoEnergyParametersIndex -- an index for the Energy Object,
eoEnergyObjectIndex -- linked to the entPhysicalIndex of the Energy
Object, the duration of measurement intervals in seconds,
(eoEnergyParametersIntervalLength), the number of successive
intervals to be stored in the eoEnergyTable,
(eoEnergyParametersIntervalNumber), the type of measurement technique
(eoEnergyParametersIntervalMode), and a sample rate used to calculate
the average (eoEnergyParametersSampleRate). Judicious choice of the
sampling rate will ensure accurate measurement of energy while not
imposing an excessive polling burden.
Measurements of the total energy consumed by an Energy Object There are three eoEnergyParametersIntervalMode types used for energy
may suffer from interruptions in the continuous measurement of measurement collection: period, sliding, and total. The choices of
energy consumption. In order to indicate such interruptions, the three different modes of collection are based on IEC standard
the object eoEnergyDiscontinuityTime is provided for indicating 61850-7-4 [IEC.61850-7-4]. Note that multiple
the time of the last interruption of total energy measurement. eoEnergyParametersIntervalMode types MAY be configured
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] simultaneously. It is important to note that for a given Energy
when the device was reset. Object, multiple modes (periodic, total, sliding window) of energy
measurement collection can be configured with the use of
eoEnergyParametersIndex. However, simultaneous measurement in
multiple modes for a given Energy Object depends on the Energy Object
capability.
The following example illustrates the eoEnergyTable and These three eoEnergyParametersIntervalMode types are illustrated by
eoEnergyParametersTable: the following three figures, for which:
First, in order to estimate energy, a time interval to sample - The horizontal axis represents the current time, with the symbol
energy should be specified, i.e., <--- L ---> expressing the eoEnergyParametersIntervalLength and
eoEnergyParametersIntervalLength can be set to "900 seconds" or the eoEnergyCollectionStartTime is represented by S1, S2, S3,
15 minutes and the number of consecutive intervals over which S4, eoEnergyParametersIntervalNumber.
the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active to indicate that the
Energy Object should start monitoring the usage per the
eoEnergyTable.
The indices for the eoEnergyTable are eoEnergyParametersIndex, - The vertical axis represents the time interval of sampling and
which identifies the index for the setting of energy measurement the value of eoEnergyConsumed can be obtained at the end of the
collection Energy Object, and eoEnergyCollectionStartTime, which sampling period. The symbol =========== denotes the duration of
denotes the start time of the energy measurement interval based the sampling period.
on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
measured energy consumption over the time interval specified
(eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the eoEnergyParametersIntervalLength and
eoEnergyParametersSampleRate, it is recommended to take into
consideration either the network element resources adequate to
process and store the sample values, and the mechanism used to
calculate the eoEnergyConsumed. The units are derived from
eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
"100" with eoEnergyUnitMultiplier equal to 0, the measured
energy consumption of the Energy Object is 100 watt-hours. The
eoEnergyMaxConsumed is the maximum energy observed and that can
be "150 watt-hours".
The eoEnergyTable has a buffer to retain a certain number of | | | =========== |
intervals, as defined by eoEnergyParametersIntervalNumber. |============ | | |
If the default value of "10" is kept, then the eoEnergyTable | | | |
contains 10 energy measurements, including the maximum. | |============ | |
| | | |
| <--- L ---> | <--- L ---> | <--- L ---> |
| | | |
S1 S2 S3 S4
Here is a brief explanation of how the maximum energy can be Figure 3: Period eoEnergyParametersIntervalMode
calculated. The first observed energy measurement value is
taken to be the initial maximum. With each subsequent
measurement, based on numerical comparison, maximum energy may
be updated. The maximum value is retained as long as the
measurements are taking place. Based on periodic polling of
this table, an NMS could compute the maximum over a longer
period, e.g., a month, 3 months, or a year.
5.7. Fault Management A eoEnergyParametersIntervalMode type of 'period' specifies non-
overlapping periodic measurements. Therefore, the next
eoEnergyCollectionStartTime is equal to the previous
eoEnergyCollectionStartTime plus eoEnergyParametersIntervalLength.
S2=S1+L; S3=S2+L, ...
[RFC6988] specifies requirements about Power States such as "the |============ |
current Power State" , "the time of the last state change", "the | |
total time spent in each state", "the number of transitions to | <--- L ---> |
each state" etc. Some of these requirements are fulfilled | |
explicitly by MIB objects such as eoPowerOperState, | |============ |
eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the | | |
other requirements are met via the SNMP NOTIFICATION mechanism. | | <--- L ---> |
eoPowerStateChange SNMP notification which is generated when the | | |
value of oPowerStateIndex, eoPowerOperState, or | | |============ |
eoPowerAdminState have changed. | | | |
| | | <--- L ---> |
| | | |
| | | |============ |
| | | | |
| | | | <--- L ---> |
S1 | | | |
| | | |
| | | |
S2 | | |
| | |
| | |
S3 | |
| |
| |
S4
6. Discovery Figure 4: Sliding eoEnergyParametersIntervalMode
It is probable that most Energy Objects will require the A eoEnergyParametersIntervalMode type of 'sliding' specifies
implementation of the ENERGY-OBJECT-CONTEXT-MIB [EMAN-AWARE-MIB] overlapping periodic measurements.
as a prerequisite for this MIB module. In such a case,
eoPowerTable of the EMAN-ENERGY-OBJECT-MIB is cross-referenced
with the eoTable of ENERGY-OBJECT-CONTEXT-MIB via
entPhysicalIndex. Every Energy Object MUST implement
entPhysicalIndex, entPhysicalClass, entPhysicalName and
entPhysicalUUID from the ENTITY-MIB [RFC6933]. As the primary
index for the Energy Object, entPhysicalIndex is used: It
characterizes the Energy Object in the ENERGY-OBJECT-MIB and the
POWER-ATTRIBUTES-MIB MIB modules (this document).
The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module | |
[EMAN-AWARE-MIB], if available, in order to discover all the |========================= |
Energy Objects and the relationships between those Energy | |
Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the | |
Energy Objects are indexed by the entPhysicalIndex. | |
| <--- Total length ---> |
| |
S1
From there, the NMS must poll the eoPowerStateTable (specified Figure 5: Total eoEnergyParametersIntervalMode
in the ENERGY-OBJECT-MIB module in this document), which An eoEnergyParametersIntervalMode type of 'total' specifies a
enumerates, amongst other things, the maximum power usage. As continuous measurement since the last reset. The value of
the entries in eoPowerStateTable table are indexed by the eoEnergyParametersIntervalNumber should be (1) one and
Energy Object ( entPhysicalIndex) and by the Power State Set eoEnergyParametersIntervalLength is ignored.
(eoPowerStateIndex), the maximum power usage is discovered per
Energy Object, and the power usage per Power State of the Power
State Set. In other words, reading the eoPowerStateTable allows
the discovery of each Power State within every Power State Set
supported by the Energy Object.
The MIB module may be populated with the Energy Object The eoEnergyParametersStatus is used to start and stop energy usage
relationship information, which have its own Energy Object index logging. The status of this variable is "active" when all the
value (entPhysicalIndex). However, the Energy Object objects in eoEnergyParametersTable are appropriate, which, in turn,
relationship must be discovered via the ENERGY-OBJECT-CONTEXT- indicates whether or not eoEnergyTable entries exist. Finally, the
MIB module. eoEnergyParametersStorageType variable indicates the storage type for
this row, i.e., whether the persistence is maintained across a device
reload.
Finally, the NMS can monitor the power attributes with the The eoEnergyTable consists of energy measurements of
POWER-ATTRIBUTES-MIB MIB module, which reuses the eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, unit scale of
entPhysicalIndex to index the Energy Object. measured energy with eoEnergyUnitMultiplier, percentage accuracy with
eoEnergyAccuracy, and the maximum observed energy within a window in
eoEnergyMaxConsumed, eoEnergyMaxProduced, and
eoEnergyDiscontinuityTime.
7. Link with the other IETF MIBs Measurements of the total energy consumed by an Energy Object may
suffer from interruptions in the continuous measurement of energy
consumption. In order to indicate such interruptions, the object
eoEnergyDiscontinuityTime is provided for indicating the time of the
last interruption of total energy measurement.
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] when
the device was reset.
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB The following example illustrates the eoEnergyTable and
eoEnergyParametersTable:
RFC 6933 [RFC6933] defines the ENTITY-MIB module that lists the First, in order to estimate energy, a time interval to sample energy
physical entities of a networking device (router, switch, etc.) should be specified, i.e., eoEnergyParametersIntervalLength can be
and those physical entities indexed by entPhysicalIndex. From set to "900 seconds" or 15 minutes and the number of consecutive
an energy-management standpoint, the physical entities that intervals over which the maximum energy is calculated
consume or produce energy are of interest. (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as set by
the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active to indicate that the Energy
Object should start monitoring the usage per the eoEnergyTable.
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that The indices for the eoEnergyTable are eoEnergyParametersIndex, which
provides a standardized way of obtaining information (current identifies the index for the setting of energy measurement collection
value of the sensor, operational status of the sensor, and the Energy Object, and eoEnergyCollectionStartTime, which denotes the
data units precision) from sensors embedded in networking start time of the energy measurement interval based on sysUpTime
devices. Sensors are associated with each index of [RFC3418]. The value of eoEnergyComsumed is the measured energy
entPhysicalIndex of the ENTITY-MIB [RFC6933]. While the focus consumption over the time interval specified
of the Power, Energy Monitoring and Control MIB is on (eoEnergyParametersIntervalLength) based on the Energy Object
measurement of power usage of networking equipment indexed by internal sampling rate (eoEnergyParametersSampleRate). While
the ENTITY-MIB, this MIB supports a customized power scale for choosing the values for the eoEnergyParametersIntervalLength and
power measurement and different Power States of networking eoEnergyParametersSampleRate, it is recommended to take into
equipment, and functionality to configure the Power States. consideration both the network element resources adequate to process
and store the sample values and the mechanism used to calculate the
eoEnergyConsumed. The units are derived from eoEnergyUnitMultiplier.
For example, eoEnergyConsumed can be "100" with
eoEnergyUnitMultiplier equal to 0, the measured energy consumption of
the Energy Object is 100 watt-hours. The eoEnergyMaxConsumed is the
maximum energy observed and that can be "150 watt-hours".
The Energy Objects are modeled by the entPhysicalIndex through The eoEnergyTable has a buffer to retain a certain number of
the entPhysicalEntity MIB object specified in the eoTable in the intervals, as defined by eoEnergyParametersIntervalNumber. If the
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB]. default value of "10" is kept, then the eoEnergyTable contains 10
energy measurements, including the maximum.
The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x Here is a brief explanation of how the maximum energy can be
accuracy classes required for electricity (e.g., 1%, 2%, 0.5% calculated. The first observed energy measurement value is taken to
accuracy classes). Indeed, entPhySensorPrecision [RFC3433] be the initial maximum. With each subsequent measurement, based on
represents "The number of decimal places of precision in fixed- numerical comparison, maximum energy may be updated. The maximum
point sensor values returned by the associated entPhySensorValue value is retained as long as the measurements are taking place.
object". The ANSI and IEC Standards are used for power Based on periodic polling of this table, an NMS could compute the
measurement and these standards require that we use an accuracy maximum over a longer period, e.g., a month, 3 months, or a year.
class, not the scientific-number precision model specified in
RFC3433. The eoPowerAccuracy MIB object models this accuracy.
Note that eoPowerUnitMultipler represents the scale factor per
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the
exponent values X * 10 ^ Y.
Power measurements specifying the qualifier 'UNITS' for each 5.7. Fault Management
measured value in watts are used in the LLDP-EXT-MED-MIB, POE
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier
is used for the power measurement values.
One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are [RFC6988] specifies requirements about Power States such as "the
implemented for all Energy Objects that need to be monitored. A current Power State", "the time of the last state change", "the total
typical example is a converged building gateway, which can time spent in each state", "the number of transitions to each state",
monitor other devices in a building and provides a proxy between etc. Some of these requirements are fulfilled explicitly by MIB
SNMP and a protocol like BACNET. Another example is the home objects such as eoPowerOperState, eoPowerStateTotalTime, and
energy controller. In such cases, the eoPhysicalEntity value eoPowerStateEnterCount. Some of the other requirements are met via
contains the zero value, using the PhysicalIndexOrZero textual the SNMP NOTIFICATION mechanism. eoPowerStateChange SNMP
convention. notification which is generated when the value of oPowerStateIndex,
eoPowerOperState, or eoPowerAdminState have changed.
The eoPower is similar to entPhySensorValue [RFC3433] and the 6. Discovery
eoPowerUnitMultipler is similar to entPhySensorScale.
7.2. Link with the ENTITY-STATE MIB It is probable that most Energy Objects will require the
implementation of the ENERGY-OBJECT-CONTEXT-MIB [RFC7461] as a
prerequisite for this MIB module. In such a case, the eoPowerTable
of the EMAN-ENERGY-OBJECT-MIB is cross-referenced with the eoTable of
ENERGY-OBJECT-CONTEXT-MIB via entPhysicalIndex. Every Energy Object
MUST implement entPhysicalIndex, entPhysicalClass, entPhysicalName,
and entPhysicalUUID from the ENTITY-MIB [RFC6933]. As the primary
index for the Energy Object, entPhysicalIndex is used: it
characterizes the Energy Object in the ENERGY-OBJECT-MIB and the
POWER-ATTRIBUTES-MIB MIB modules (this document).
For each entity in the ENTITY-MIB [RFC6933], the ENTITY-STATE The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module
MIB [RFC4268] specifies the operational states (entStateOper: [RFC7461], if available, in order to discover all the Energy Objects
unknown, enabled, disabled, testing), the alarm (entStateAlarm: and the relationships between those Energy Objects. In the ENERGY-
unknown, underRepair, critical, major, minor, warning, OBJECT-CONTEXT-MIB module tables, the Energy Objects are indexed by
indeterminate) and the possible values of standby states the entPhysicalIndex.
(entStateStandby: unknown, hotStandby, coldStandby,
providingService).
From a power monitoring point of view, in contrast to the entity From there, the NMS must poll the eoPowerStateTable (specified in the
operational states of entities, Power States are required, as ENERGY-OBJECT-MIB module in this document), which enumerates, amongst
proposed in the Power, Energy Monitoring and Control MIB module. other things, the maximum power usage. As the entries in
Those Power States can be mapped to the different operational eoPowerStateTable table are indexed by the Energy Object
states in the ENTITY-STATE MIB, if a formal mapping is required. (entPhysicalIndex) and by the Power State Set (eoPowerStateIndex),
For example, the entStateStandby "unknown", "hotStandby", the maximum power usage is discovered per Energy Object, and the
"coldStandby", states could map to the Power State "unknown", power usage per Power State of the Power State Set. In other words,
"ready", "standby", respectively, while the entStateStandby reading the eoPowerStateTable allows the discovery of each Power
"providingService" could map to any "low" to "high" Power State. State within every Power State Set supported by the Energy Object.
7.3. Link with the POWER-OVER-ETHERNET MIB The MIB module may be populated with the Energy Object relationship
information, which have its own Energy Object index value
(entPhysicalIndex). However, the Energy Object relationship must be
discovered via the ENERGY-OBJECT-CONTEXT-MIB module.
Power-over-Ethernet MIB [RFC3621] provides an energy monitoring Finally, the NMS can monitor the power attributes with the POWER-
and configuration framework for power over Ethernet devices. ATTRIBUTES-MIB MIB module, which reuses the entPhysicalIndex to index
RFC 3621 defines a port group entity on a switch for power the Energy Object.
monitoring and management policy and does not use the
entPhysicalIndex index. Indeed, pethMainPseConsumptionPower is
indexed by the pethMainPseGroupIndex, which has no mapping with
the entPhysicalIndex.
If the Power-over-Ethernet MIB [RFC3621] is supported, the 7. Link with the Other IETF MIBs
Energy Object eoethPortIndex and eoethPortGrpIndex contain the
pethPsePortIndex and pethPsePortGroupIndex, respectively.
However, one cannot assume that the Power-over-Ethernet MIB is
implemented for most or all Energy Objects. In such cases, the
eoethPortIndex and eoethPortGrpIndex values contain the zero
value, via the new PethPsePortIndexOrZero and textual
PethPsePortGroupIndexOrZero conventions.
In either case, the entPhysicalIndex MIB object is used as the 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
unique Energy Object index.
Note that, even though the Power-over-Ethernet MIB [RFC3621] was [RFC6933] defines the ENTITY-MIB module that lists the physical
created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse entities of a networking device (router, switch, etc.) and those
the precision notion from the ENTITY-SENSOR MIB, i.e., the physical entities indexed by entPhysicalIndex. From an energy-
entPhySensorPrecision MIB object. management standpoint, the physical entities that consume or produce
energy are of interest.
7.4. Link with the UPS MIB [RFC3433] defines the ENTITY-SENSOR MIB module that provides a
standardized way of obtaining information (current value of the
sensor, operational status of the sensor, and the data-unit
precision) from sensors embedded in networking devices. Sensors are
associated with each index of the entPhysicalIndex of the ENTITY-MIB
[RFC6933]. While the focus of the Monitoring and Control MIB for
Power and Energy is on measurement of power usage of networking
equipment indexed by the ENTITY-MIB, this MIB supports a customized
power scale for power measurement and different Power States of
networking equipment and the functionality to configure the Power
States.
To protect against unexpected power disruption, data centers and The Energy Objects are modeled by the entPhysicalIndex through the
buildings make use of Uninterruptible Power Supplies (UPS). To entPhysicalEntity MIB object specified in the eoTable in the ENERGY-
protect critical assets, a UPS can be restricted to a particular OBJECT-CONTEXT-MIB MIB module [RFC7461].
subset or domain of the network. UPS usage typically lasts only
for a finite period of time, until normal power supply is
restored. Planning is required to decide on the capacity of the
UPS based on output power and duration of probable power outage.
To properly provision UPS power in a data center or building, it
is important to first understand the total demand required to
support all the entities in the site. This demand can be
assessed and monitored via the Power, Energy Monitoring and
Control MIB.
UPS MIB [RFC1628] provides information on the state of the UPS The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x accuracy
network. Implementation of the UPS MIB is useful at the classes required for electricity (e.g., 1%, 2%, and 0.5% accuracy
aggregate level of a data center or a building. The MIB module classes). Indeed, entPhySensorPrecision [RFC3433] represents "The
contains several groups of variables: number of decimal places of precision in fixed-point sensor values
returned by the associated entPhySensorValue object". The ANSI and
IEC standards are used for power measurement and these standards
require that we use an accuracy class, not the scientific-number
precision model specified in RFC3433. The eoPowerAccuracy MIB object
models this accuracy. Note that eoPowerUnitMultipler represents the
scale factor per IEC 62053-21 [IEC.62053-21] and IEC 62053-22
[IEC.62053-22], which is a more logical representation for power
measurements (compared to entPhySensorScale), with the mantissa and
the exponent values X * 10 ^ Y.
- upsIdent: Identifies the UPS entity (name, model, etc.). Power measurements specifying the qualifier 'UNITS' for each measured
value in watts are used in the LLDP-EXT-MED-MIB, Power Ethernet
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier is
used for the power measurement values.
- upsBattery group: Indicates the battery state One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIBs are
(upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, which can monitor
other devices in a building and provides a proxy between SNMP and a
protocol like BACnet. Another example is the home energy controller.
In such cases, the eoPhysicalEntity value contains the zero value,
using the PhysicalIndexOrZero Textual Convention.
- upsInput group: Characterizes the input load to the UPS The eoPower is similar to entPhySensorValue [RFC3433] and the
(number of input lines, voltage, current, etc.). eoPowerUnitMultipler is similar to entPhySensorScale.
- upsOutput: Characterizes the output from the UPS (number of 7.2. Link with the ENTITY-STATE MIB
output lines, voltage, current, etc.)
- upsAlarms: Indicates the various alarm events. For each entity in the ENTITY-MIB [RFC6933], the ENTITY-STATE MIB
[RFC4268] specifies the operational states (entStateOper: unknown,
enabled, disabled, testing), the alarm (entStateAlarm: unknown,
underRepair, critical, major, minor, warning, indeterminate), and the
possible values of standby states (entStateStandby: unknown,
hotStandby, coldStandby, providingService).
The measurement of power in the UPS MIB is in volts, amperes and From a power-monitoring point of view, in contrast to the entity
watts. The units of power measurement are RMS volts and RMS operational states of entities, Power States are required, as
Amperes. They are not based on the EntitySensorDataScale and proposed in the Monitoring and Control MIB for Power and Energy.
EntitySensorDataPrecision of ENTITY-SENSOR-MIB. Those Power States can be mapped to the different operational states
in the ENTITY-STATE MIB, if a formal mapping is required. For
example, the entStateStandby "unknown", "hotStandby", and
"coldStandby" states could map to the Power State "unknown", "ready",
"standby", respectively, while the entStateStandby "providingService"
could map to any "low" to "high" Power State.
Both the Power, Energy Monitoring and Control MIB and the UPS 7.3. Link with the POWER-OVER-ETHERNET MIB
MIB may be implemented on the same UPS SNMP agent, without
conflict. In this case, the UPS device itself is the Energy
Object and any of the UPS meters or submeters are the Energy
Objects with a possible relationship as defined in [RFC7326].
7.5. Link with the LLDP and LLDP-MED MIBs The Power-over-Ethernet MIB [RFC3621] provides an energy monitoring
and configuration framework for power over Ethernet devices. RFC
3621 defines a port group entity on a switch for power monitoring and
management policy and does not use the entPhysicalIndex index.
Indeed, pethMainPseConsumptionPower is indexed by the
pethMainPseGroupIndex, which has no mapping with the
entPhysicalIndex.
The LLDP Protocol is a Data Link Layer protocol used by network If the Power-over-Ethernet MIB [RFC3621] is supported, the Energy
devices to advertise their identities, capabilities, and Object eoethPortIndex and eoethPortGrpIndex contain the
interconnections on a LAN network. pethPsePortIndex and pethPsePortGroupIndex, respectively. However,
one cannot assume that the Power-over-Ethernet MIB is implemented for
most or all Energy Objects. In such cases, the eoethPortIndex and
eoethPortGrpIndex values contain the zero value, via the new
PethPsePortIndexOrZero and PethPsePortGroupIndexOrZero TCs.
The Media Endpoint Discovery is an enhancement of LLDP, known as In either case, the entPhysicalIndex MIB object is used as the unique
LLDP-MED. The LLDP-MED enhancements specifically address voice Energy Object index.
applications. LLDP-MED covers 6 basic areas: capability
discovery, LAN speed and duplex discovery, network policy
discovery, location identification discovery, inventory
discovery, and power discovery.
Of particular interest to the current MIB module is the power Note that, even though the Power-over-Ethernet MIB [RFC3621] was
discovery, which allows the endpoint device (such as a PoE created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse the
phone) to convey power requirements to the switch. In power precision notion from the ENTITY-SENSOR MIB, i.e., the
discovery, LLDP-MED has four Type Length Values (TLVs): power entPhySensorPrecision MIB object.
type, power source, power priority and power value.
Respectively, those TLVs provide information related to the type
of power (power sourcing entity versus powered device), how the
device is powered (from the line, from a backup source, from
external power source, etc.), the power priority (how important
is it that this device has power?), and how much power the
device needs.
The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 7.4. Link with the UPS MIB
actually comes from the Power-over-Ethernet MIB [RFC3621]. If
the Power-over-Ethernet MIB [RFC3621] is supported, the exact
value from the pethPsePortPowerPriority [RFC3621] is copied over
into the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB];
otherwise the value in lldpXMedRemXPoEPDPowerPriority is
"unknown". From the Power, Energy Monitoring and Control MIB, it
is possible to identify the pethPsePortPowerPriority [RFC3621],
via the eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to To protect against unexpected power disruption, data centers and
eoPowerMeasurementLocal in indicating if the power for an buildings make use of Uninterruptible Power Supplies (UPS). To
attached device is local or from a remote device. If the LLDP- protect critical assets, a UPS can be restricted to a particular
MED MIB is supported, the following mapping can be applied to subset or domain of the network. UPS usage typically lasts only for
the eoPowerMeasurementLocal: lldpXMedLocXPoEPDPowerSource a finite period of time, until normal power supply is restored.
fromPSE(2) and local(3) can be mapped to false and true, Planning is required to decide on the capacity of the UPS based on
respectively. output power and duration of probable power outage. To properly
provision UPS power in a data center or building, it is important to
first understand the total demand required to support all the
entities in the site. This demand can be assessed and monitored via
the Monitoring and Control MIB for Power and Energy.
8. Structure of the MIB The UPS MIB [RFC1628] provides information on the state of the UPS
network. Implementation of the UPS MIB is useful at the aggregate
level of a data center or a building. The MIB module contains
several groups of variables:
The primary MIB object in the energyObjectMib MIB module is the - upsIdent: Identifies the UPS entity (name, model, etc.).
energyObjectMibObjects root. The eoPowerTable table of
energyObjectMibObjects describes the power measurement
attributes of an Energy Object entity. The identity of a device
in terms of uniquely identification of the Energy Object and its
relationship to other entities in the network are addressed in
[EMAN-AWARE-MIB].
Logically, this MIB module is a sparse extension of the - upsBattery group: Indicates the battery state (upsbatteryStatus,
ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the upsEstimatedMinutesRemaining, etc.)
following requirements which are applied to [EMAN-AWARE-MIB] are
also applicable. As a requirement for this MIB module, [EMAN-
AWARE-MIB] SHOULD be implemented and as Module Compliance of
ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance MUST
be supported which requires 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and entPhysicalUUID MUST be
implemented.
eoMeterCapabilitiesTable is useful to enable applications to - upsInput group: Characterizes the input load to the UPS (number
determine the capabilities supported by the local management of input lines, voltage, current, etc.).
agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading
the value of this object, it is possible for applications to
know which tables contain the information and are usable without
walking through the table and querying every element which
involves a trial-and-error process.
The power measurement of an Energy Object contains information - upsOutput: Characterizes the output from the UPS (number of
describing its power usage (eoPower) and its current Power State output lines, voltage, current, etc.)
(eoPowerOperState). In addition to power usage, additional
information describing the units of measurement
(eoPowerAccuracy, eoPowerUnitMultiplier), how power usage
measurement was obtained (eoPowerMeasurementCaliber), the
source of power measurement (eoPowerMeasurementLocal) and the
type of power (eoPowerCurrentType) are described.
An Energy Object may contain an optional eoEnergyTable to - upsAlarms: Indicates the various alarm events.
describe energy measurement information over time.
An Energy Object may contain an optional eoACPwrAttributesTable The measurement of power in the UPS MIB is in volts, amperes, and
table (specified in the POWER-ATTRIBUTES-MIB module) that watts. The units of power measurement are root mean square (RMS)
describes the electrical characteristics associated with the volts and RMS amperes. They are not based on the
current Power State and usage. EntitySensorDataScale and EntitySensorDataPrecision of ENTITY-SENSOR-
MIB.
An Energy Object may also contain optional battery information Both the Monitoring and Control MIB for Power and Energy and the UPS
associated with this entity. MIB may be implemented on the same UPS SNMP agent, without conflict.
In this case, the UPS device itself is the Energy Object and any of
the UPS meters or submeters are the Energy Objects with a possible
relationship as defined in [RFC7326].
9. MIB Definitions 7.5. Link with the LLDP and LLDP-MED MIBs
9.1. The IANAPowerStateSet-MIB MIB Module The Link Layer Discovery Protocol (LLDP) is a Data Link Layer
protocol used by network devices to advertise their identities,
capabilities, and interconnections on a LAN network.
-- ************************************************************ The Media Endpoint Discovery is an enhancement of LLDP, known as
-- LLDP-MED. The LLDP-MED enhancements specifically address voice
-- applications. LLDP-MED covers six basic areas: capability discovery,
-- This MIB, maintained by IANA, contains a single Textual LAN speed and duplex discovery, network policy discovery, location
-- Convention: PowerStateSet identification discovery, inventory discovery, and power discovery.
--
-- ************************************************************
IANAPowerStateSet-MIB DEFINITIONS ::= BEGIN Of particular interest to the current MIB module is the power
discovery, which allows the endpoint device (such as a PoE phone) to
convey power requirements to the switch. In power discovery,
LLDP-MED has four Type-Length-Values (TLVs): power type, power
source, power priority, and power value. Respectively, those TLVs
provide information related to the type of power (power sourcing
entity versus powered device), how the device is powered (from the
line, from a backup source, from external power source, etc.), the
power priority (how important is it that this device has power?), and
how much power the device needs.
IMPORTS The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB]
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI actually comes from the Power-over-Ethernet MIB [RFC3621]. If the
TEXTUAL-CONVENTION FROM SNMPv2-TC; Power-over-Ethernet MIB [RFC3621] is supported, the exact value from
the pethPsePortPowerPriority [RFC3621] is copied over into the
lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise, the value
in lldpXMedRemXPoEPDPowerPriority is "unknown". From the Monitoring
and Control MIB for Power and Energy, it is possible to identify the
pethPsePortPowerPriority [RFC3621], via the eoethPortIndex and
eoethPortGrpIndex.
ianaPowerStateSet MODULE-IDENTITY The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
LAST-UPDATED "201406070000Z" -- 07 June 2014 eoPowerMeasurementLocal in indicating if the power for an attached
ORGANIZATION "IANA" device is local or from a remote device. If the LLDP-MED MIB is
CONTACT-INFO " supported, the following mapping can be applied to the
Internet Assigned Numbers Authority eoPowerMeasurementLocal: lldpXMedLocXPoEPDPowerSource fromPSE(2) and
Postal: ICANN local(3) can be mapped to false and true, respectively.
12025 Waterfront Drive Suite 300
Los Angeles, CA 90094
Tel: +1-310-301 5800
EMail: iana&iana.org"
DESCRIPTION 8. Structure of the MIB
"This MIB module defines the PowerStateSet Textual
Convention, which specifies the Power State Sets and
Power State Set Values an Energy Object supports
Copyright (C) The IETF Trust (2014). The primary MIB object in the energyObjectMib MIB module is the
The initial version of this MIB module was published in energyObjectMibObjects root. The eoPowerTable table of
RFC XXXX; for full legal notices see the RFC itself. energyObjectMibObjects describes the power measurement attributes of
an Energy Object entity. The identity of a device in terms of
uniquely identification of the Energy Object and its relationship to
other entities in the network are addressed in [RFC7461].
Supplementary information may be available at Logically, this MIB module is a sparse extension of the ENERGY-
http://www.ietf.org/copyrights/ianamib.html" OBJECT-CONTEXT-MIB module [RFC7461]. Thus, the following
requirements that are applied to [RFC7461] are also applicable. As a
requirement for this MIB module, [RFC7461] SHOULD be implemented and
as Module Compliance of ENTITY-MIB V4 [RFC6933] with respect to
entity4CRCompliance MUST be supported, which requires four MIB
objects: entPhysicalIndex, entPhysicalClass, entPhysicalName, and
entPhysicalUUID MUST be implemented.
-- revision history The eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management agent.
This table indicates the energy-monitoring MIB groups that are
supported by the local management system. By reading the value of
this object, it is possible for applications to know which tables
contain the information and are usable without walking through the
table and querying every element that involves a trial-and-error
process.
REVISION "201406070000Z" -- 07 June 2014 The power measurement of an Energy Object contains information
DESCRIPTION describing its power usage (eoPower) and its current Power State
"Initial version of this MIB module, as published as RFC (eoPowerOperState). In addition to power usage, additional
XXXX." information describing the units of measurement (eoPowerAccuracy,
eoPowerUnitMultiplier), how power usage measurement was obtained
(eoPowerMeasurementCaliber), the source of power measurement
(eoPowerMeasurementLocal), and the type of power (eoPowerCurrentType)
are described.
-- RFC Editor, please replace xxx with the IANA allocation An Energy Object may contain an optional eoEnergyTable to describe
-- for this MIB module and XXXX with the number of the energy measurement information over time.
-- approved RFC
::= { mib-2 xxx } An Energy Object may contain an optional eoACPwrAttributesTable table
(specified in the POWER-ATTRIBUTES-MIB module) that describes the
electrical characteristics associated with the current Power State
and usage.
PowerStateSet ::= TEXTUAL-CONVENTION An Energy Object may also contain optional battery information
STATUS current associated with this entity.
DESCRIPTION
"IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy
Object supports. IANA has created a registry of Power
State supported by an Energy Object and IANA shall
administer the list of Power State Sets and Power
States.
The textual convention assumes that Power States in a 9. MIB Definitions
power state set are limited to 255 distinct values. For
a Power State Set S, the named number with the value S *
256 is allocated to indicate the Power State set. For a
Power State X in the Power State S, the named number
with the value S * 256 + X + 1 is allocated to represent
the Power State.
Requests for new values should be made to IANA via email 9.1. The IANAPowerStateSet-MIB Module
(iana&iana.org)."
REFERENCE -- ************************************************************
"http://www.iana.org/assignments/power-state-sets" --
--
-- This MIB, maintained by IANA, contains a single Textual
-- Convention: PowerStateSet
--
-- ************************************************************
SYNTAX INTEGER { IANAPowerStateSet-MIB DEFINITIONS ::= BEGIN
other(0), -- indicates other set
unknown(255), -- unknown
ieee1621(256), -- indicates IEEE1621 set IMPORTS
ieee1621Off(257), MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
ieee1621Sleep(258), TEXTUAL-CONVENTION FROM SNMPv2-TC;
ieee1621On(259),
dmtf(512), -- indicates DMTF set ianaPowerStateSet MODULE-IDENTITY
dmtfOn(513), LAST-UPDATED "201502090000Z" -- 9 February 2015
dmtfSleepLight(514), ORGANIZATION "IANA"
dmtfSleepDeep(515), CONTACT-INFO "
dmtfOffHard(516), Internet Assigned Numbers Authority
dmtfOffSoft(517), Postal: ICANN
dmtfHibernate(518), 12025 Waterfront Drive, Suite 300
dmtfPowerOffSoft(519), Los Angeles, CA 90094
dmtfPowerOffHard(520), United States
dmtfMasterBusReset(521), Tel: +1-310-301 5800
dmtfDiagnosticInterrapt(522), EMail: iana@iana.org"
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set DESCRIPTION
emanmechoff(1025), "Copyright (c) 2015 IETF Trust and the persons identified as
emansoftoff(1026), authors of the code. All rights reserved.
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
END
9.2. The ENERGY-OBJECT-MIB MIB Module Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
-- ************************************************************ This MIB module defines the PowerStateSet Textual
-- Convention, which specifies the Power State Sets and
-- Power State Set Values an Energy Object supports.
-- This MIB is used to monitor power usage of network
-- devices
--
-- *************************************************************
ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN The initial version of this MIB module was published in
RFC 7460; for full legal notices see the RFC itself."
IMPORTS -- revision history
MODULE-IDENTITY, REVISION "201502090000Z" -- 9 February 2015
OBJECT-TYPE, DESCRIPTION
NOTIFICATION-TYPE, "Initial version of this MIB module, as published as RFC
mib-2, 7460."
Integer32, Counter32, Unsigned32, TimeTicks
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeInterval,
TimeStamp, TruthValue, StorageType
FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF
OwnerString
FROM RMON-MIB
entPhysicalIndex
FROM ENTITY-MIB
PowerStateSet
FROM IANAPowerStateSet-MIB;
energyObjectMib MODULE-IDENTITY ::= { mib-2 228 }
LAST-UPDATED "201406070000Z" -- 07 June 2014
ORGANIZATION "IETF EMAN Working Group" PowerStateSet ::= TEXTUAL-CONVENTION
CONTACT-INFO STATUS current
"WG charter: DESCRIPTION
http://datatracker.ietf.org/wg/eman/charter/ "IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy
Object supports. IANA has created a registry of Power
State supported by an Energy Object and IANA shall
administer the list of Power State Sets and Power
States.
Mailing Lists: The Textual Convention assumes that Power States in a
General Discussion: eman@ietf.org Power State Set are limited to 255 distinct values. For
a Power State Set S, the named number with the value S *
256 is allocated to indicate the Power State Set. For a
Power State X in the Power State Set S, the named number
with the value S * 256 + X + 1 is allocated to represent
the Power State.
To Subscribe: Requests for new values should be made to IANA via email
https://www.ietf.org/mailman/listinfo/eman (iana@iana.org)."
REFERENCE
"http://www.iana.org/assignments/power-state-sets"
Archive: SYNTAX INTEGER {
http://www.ietf.org/mail-archive/web/eman other(0), -- indicates other set
unknown(255), -- unknown
Editors: ieee1621(256), -- indicates IEEE1621 set
Mouli Chandramouli ieee1621Off(257),
Cisco Systems, Inc. ieee1621Sleep(258),
Sarjapur Outer Ring Road ieee1621On(259),
Bangalore 560103
IN
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
Brad Schoening dmtf(512), -- indicates DMTF set
44 Rivers Edge Drive dmtfOn(513),
Little Silver, NJ 07739 dmtfSleepLight(514),
US dmtfSleepDeep(515),
Email: brad.schoening@verizon.net dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
Juergen Quittek eman(1024), -- indicates EMAN set
NEC Europe Ltd. emanMechOff(1025),
NEC Laboratories Europe emanSoftOff(1026),
Network Research Division emanHibernate(1027),
Kurfuersten-Anlage 36 emanSleep(1028),
Heidelberg 69115 emanStandby(1029),
DE emanReady(1030),
Phone: +49 6221 4342-115 emanLowMinus(1031),
Email: quittek@neclab.eu emanLow(1032),
emanMediumMinus(1033),
emanMedium(1034),
emanHighMinus(1035),
emanHigh(1036)
}
END
Thomas Dietz 9.2. The ENERGY-OBJECT-MIB MIB Module
NEC Europe Ltd.
NEC Laboratories Europe
Network Research Division
Kurfuersten-Anlage 36
69115 Heidelberg
DE
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise -- ************************************************************
Cisco Systems, Inc. --
De Kleetlaan 6a b1 --
Degem 1831 -- This MIB is used to monitor power usage of network
Belgium -- devices
Phone: +32 2 704 5622 --
Email: bclaise@cisco.com" -- *************************************************************
DESCRIPTION ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN
"This MIB is used to monitor power and energy in
devices.
The tables eoMeterCapabilitiesTable and eoPowerTable IMPORTS
are a sparse extension of the eoTable from the MODULE-IDENTITY,
ENERGY-OBJECT-CONTEXT-MIB. As a requirement OBJECT-TYPE,
[EMAN-AWARE-MIB] SHOULD be implemented. NOTIFICATION-TYPE,
mib-2,
Integer32, Counter32, Unsigned32, TimeTicks
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeInterval,
TimeStamp, TruthValue, StorageType
FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF
OwnerString
FROM RMON-MIB
entPhysicalIndex
FROM ENTITY-MIB
PowerStateSet
FROM IANAPowerStateSet-MIB;
Module Compliance of ENTITY-MIB v4 with respect to energyObjectMib MODULE-IDENTITY
entity4CRCompliance MUST be supported which requires LAST-UPDATED "201502090000Z" -- 9 February 2015
implementation of 4 MIB objects: entPhysicalIndex, ORGANIZATION "IETF EMAN Working Group"
entPhysicalClass, entPhysicalName and entPhysicalUUID." CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/eman/charter/
REVISION "201406070000Z" -- 07 June 2014 Mailing Lists:
DESCRIPTION General Discussion: eman@ietf.org
"Initial version, published as RFC XXXX." To Subscribe:
https://www.ietf.org/mailman/listinfo/eman
-- RFC Editor, please replace yyy with the IANA allocation Archive:
-- for this MIB module and XXXX with the number of the http://www.ietf.org/mail-archive/web/eman
-- approved RFC
::= { mib-2 yyy } Editors:
Mouli Chandramouli
Cisco Systems, Inc.
Sarjapur Outer Ring Road
Bangalore 560103
India
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
energyObjectMibNotifs OBJECT IDENTIFIER Brad Schoening
::= { energyObjectMib 0 } 44 Rivers Edge Drive
Little Silver, NJ 07739
United States
Email: brad.schoening@verizon.net
energyObjectMibObjects OBJECT IDENTIFIER Juergen Quittek
::= { energyObjectMib 1 } NEC Europe, Ltd.
NEC Laboratories Europe
Network Research Division
Kurfuersten-Anlage 36
Heidelberg 69115
Germany
Phone: +49 6221 4342-115
Email: quittek@neclab.eu
energyObjectMibConform OBJECT IDENTIFIER Thomas Dietz
::= { energyObjectMib 2 } NEC Europe, Ltd.
NEC Laboratories Europe
Network Research Division
Kurfuersten-Anlage 36
69115 Heidelberg
Germany
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
-- Textual Conventions Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
UnitMultiplier ::= TEXTUAL-CONVENTION DESCRIPTION
STATUS current "Copyright (c) 2015 IETF Trust and the persons identified as
DESCRIPTION authors of the code. All rights reserved.
"The Unit Multiplier is an integer value that represents
the IEEE 61850 Annex A units multiplier associated with
the integer units used to measure the power or energy.
For example, when used with eoPowerUnitMultiplier, -3 Redistribution and use in source and binary forms, with or
represents 10^-3 or milliwatts." without modification, is permitted pursuant to, and subject
REFERENCE to the license terms contained in, the Simplified BSD License
"The International System of Units (SI), National set forth in Section 4.c of the IETF Trust's Legal Provisions
Institute of Standards and Technology, Spec. Publ. 330, Relating to IETF Documents
August 1991." (http://trustee.ietf.org/license-info).
SYNTAX INTEGER {
yocto(-24), -- 10^-24
zepto(-21), -- 10^-21
atto(-18), -- 10^-18
femto(-15), -- 10^-15
pico(-12), -- 10^-12
nano(-9), -- 10^-9
micro(-6), -- 10^-6
milli(-3), -- 10^-3
units(0), -- 10^0
kilo(3), -- 10^3
mega(6), -- 10^6
giga(9), -- 10^9
tera(12), -- 10^12
peta(15), -- 10^15
exa(18), -- 10^18
zetta(21), -- 10^21
yotta(24) -- 10^24
}
-- Objects This MIB is used to monitor power and energy in
devices.
eoMeterCapabilitiesTable OBJECT-TYPE The tables eoMeterCapabilitiesTable and eoPowerTable
SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry are a sparse extension of the eoTable from the
MAX-ACCESS not-accessible ENERGY-OBJECT-CONTEXT-MIB. As a requirement,
STATUS current [RFC7461] SHOULD be implemented.
DESCRIPTION
"This table is useful for helping applications determine
the monitoring capabilities supported by the local
management agents. It is possible for applications to
know which tables are usable without going through a
trial-and-error process."
::= { energyObjectMibObjects 1 }
eoMeterCapabilitiesEntry OBJECT-TYPE Module Compliance of ENTITY-MIB v4 with respect to
SYNTAX EoMeterCapabilitiesEntry entity4CRCompliance MUST be supported which requires
MAX-ACCESS not-accessible implementation of 4 MIB objects: entPhysicalIndex,
STATUS current entPhysicalClass, entPhysicalName and entPhysicalUUID."
DESCRIPTION REVISION "201502090000Z" -- 9 February 2015
"An entry describes the metering capability of an Energy DESCRIPTION
Object." "Initial version, published as RFC 7460."
INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 }
EoMeterCapabilitiesEntry ::= SEQUENCE { ::= { mib-2 229 }
eoMeterCapability BITS
}
eoMeterCapability OBJECT-TYPE energyObjectMibNotifs OBJECT IDENTIFIER
SYNTAX BITS { ::= { energyObjectMib 0 }
none(0),
powermetering(1), -- power measurement
energymetering(2), -- energy measurement
powerattributes(3) -- power attributes
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the energy monitoring capabilities
supported by this agent. This object use a BITS syntax
and indicates the MIB groups supported by the probe. By
reading the value of this object, it is possible to
determine the MIB tables supported. "
::= { eoMeterCapabilitiesEntry 1 }
eoPowerTable OBJECT-TYPE energyObjectMibObjects OBJECT IDENTIFIER
SYNTAX SEQUENCE OF EoPowerEntry ::= { energyObjectMib 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table lists Energy Objects."
::= { energyObjectMibObjects 2 }
eoPowerEntry OBJECT-TYPE energyObjectMibConform OBJECT IDENTIFIER
SYNTAX EoPowerEntry ::= { energyObjectMib 2 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the power usage of an Energy Object."
INDEX { entPhysicalIndex }
::= { eoPowerTable 1 }
EoPowerEntry ::= SEQUENCE { -- Textual Conventions
eoPower Integer32,
eoPowerNameplate Unsigned32,
eoPowerUnitMultiplier UnitMultiplier,
eoPowerAccuracy Integer32,
eoPowerMeasurementCaliber INTEGER,
eoPowerCurrentType INTEGER,
eoPowerMeasurementLocal TruthValue,
eoPowerAdminState PowerStateSet,
eoPowerOperState PowerStateSet,
eoPowerStateEnterReason OwnerString
}
eoPower OBJECT-TYPE UnitMultiplier ::= TEXTUAL-CONVENTION
SYNTAX Integer32 STATUS current
UNITS "watts" DESCRIPTION
MAX-ACCESS read-only "The Unit Multiplier is an integer value that represents
STATUS current the IEEE 61850 Annex A units multiplier associated with
DESCRIPTION the integer units used to measure the power or energy.
"This object indicates the power measured for the Energy
Object. For alternating current, this value is obtained
as an average over fixed number of AC cycles. This value
is specified in SI units of watts with the magnitude of
watts (milliwatts, kilowatts, etc.) indicated separately
in eoPowerUnitMultiplier. The accuracy of the measurement
is specified in eoPowerAccuracy. The direction of power
flow is indicated by the sign on eoPower. If the Energy
Object is consuming power, the eoPower value will be
positive. If the Energy Object is producing power, the
eoPower value will be negative.
The eoPower MUST be less than or equal to the maximum For example, when used with eoPowerUnitMultiplier, -3
power that can be consumed at the power state specified represents 10^-3 or milliwatts."
by eoPowerState. REFERENCE
"The International System of Units (SI), National
Institute of Standards and Technology, Spec. Publ. 330,
August 1991."
SYNTAX INTEGER {
yocto(-24), -- 10^-24
zepto(-21), -- 10^-21
atto(-18), -- 10^-18
femto(-15), -- 10^-15
pico(-12), -- 10^-12
nano(-9), -- 10^-9
micro(-6), -- 10^-6
milli(-3), -- 10^-3
units(0), -- 10^0
kilo(3), -- 10^3
mega(6), -- 10^6
giga(9), -- 10^9
tera(12), -- 10^12
peta(15), -- 10^15
exa(18), -- 10^18
zetta(21), -- 10^21
yotta(24) -- 10^24
}
The eoPowerMeasurementCaliber object specifies how the -- Objects
usage value reported by eoPower was obtained. The eoPower
value must report 0 if the eoPowerMeasurementCaliber is
'unavailable'. For devices that can not measure or
report power, this option can be used."
::= { eoPowerEntry 1 }
eoPowerNameplate OBJECT-TYPE eoMeterCapabilitiesTable OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry
UNITS "watts" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This table is useful for helping applications determine
"This object indicates the rated maximum consumption for the monitoring capabilities supported by the local
the fully populated Energy Object. The nameplate power management agents. It is possible for applications to
requirements are the maximum power numbers given in SI know which tables are usable without going through a
Watts and, in almost all cases, are well above the trial-and-error process."
expected operational consumption. Nameplate power is ::= { energyObjectMibObjects 1 }
widely used for power provisioning. This value is
specified in either units of watts or voltage and
current. The units are therefore SI watts or equivalent
Volt-Amperes with the magnitude (milliwatts, kilowatts,
etc.) indicated separately in eoPowerUnitMultiplier."
::= { eoPowerEntry 2 }
eoPowerUnitMultiplier OBJECT-TYPE eoMeterCapabilitiesEntry OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX EoMeterCapabilitiesEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in eoPower "An entry describes the metering capability of an Energy
and eoPowerNameplate." Object."
::= { eoPowerEntry 3 } INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 }
eoPowerAccuracy OBJECT-TYPE EoMeterCapabilitiesEntry ::= SEQUENCE {
SYNTAX Integer32 (0..10000) eoMeterCapability BITS
UNITS "hundredths of percent" }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a percentage value, in 100ths of a
percent, representing the assumed accuracy of the usage
reported by eoPower. For example: The value 1010 means
the reported usage is accurate to +/- 10.1 percent. This
value is zero if the accuracy is unknown or not
applicable based upon the measurement method.
ANSI and IEC define the following accuracy classes for eoMeterCapability OBJECT-TYPE
power measurement: SYNTAX BITS {
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. none(0),
ANSI C12.20 class 0.2, 0.5" powermetering(1), -- power measurement
energymetering(2), -- energy measurement
powerattributes(3) -- power attributes
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the energy-monitoring capabilities
supported by this agent. This object use a BITS syntax
and indicates the MIB groups supported by the probe. By
reading the value of this object, it is possible to
determine the MIB tables supported."
::= { eoMeterCapabilitiesEntry 1 }
::= { eoPowerEntry 4 } eoPowerTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table lists Energy Objects."
::= { energyObjectMibObjects 2 }
eoPowerMeasurementCaliber OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX INTEGER { SYNTAX EoPowerEntry
unavailable(1) , MAX-ACCESS not-accessible
unknown(2), STATUS current
actual(3) , DESCRIPTION
estimated(4), "An entry describes the power usage of an Energy Object."
static(5) } INDEX { entPhysicalIndex }
MAX-ACCESS read-only ::= { eoPowerTable 1 }
STATUS current
DESCRIPTION
"This object specifies how the usage value reported by
eoPower was obtained:
- unavailable(1): Indicates that the usage is not EoPowerEntry ::= SEQUENCE {
available. In such a case, the eoPower value must be 0 eoPower Integer32,
for devices that can not measure or report power this eoPowerNameplate Unsigned32,
option can be used. eoPowerUnitMultiplier UnitMultiplier,
eoPowerAccuracy Integer32,
eoPowerMeasurementCaliber INTEGER,
eoPowerCurrentType INTEGER,
eoPowerMeasurementLocal TruthValue,
eoPowerAdminState PowerStateSet,
eoPowerOperState PowerStateSet,
eoPowerStateEnterReason OwnerString
}
- unknown(2): Indicates that the way the usage was eoPower OBJECT-TYPE
determined is unknown. In some cases, entities report SYNTAX Integer32
aggregate power on behalf of another device. In such UNITS "watts"
cases it is not known whether the usage reported is MAX-ACCESS read-only
actual, estimated or static. STATUS current
DESCRIPTION
"This object indicates the power measured for the Energy
Object. For alternating current, this value is obtained
as an average over fixed number of AC cycles. This value
is specified in SI units of watts with the magnitude of
watts (milliwatts, kilowatts, etc.) indicated separately
in eoPowerUnitMultiplier. The accuracy of the measurement
is specified in eoPowerAccuracy. The direction of power
flow is indicated by the sign on eoPower. If the Energy
Object is consuming power, the eoPower value will be
positive. If the Energy Object is producing power, the
eoPower value will be negative.
- actual(3): Indicates that the reported usage was The eoPower MUST be less than or equal to the maximum
measured by the entity through some hardware or direct power that can be consumed at the Power State specified
physical means. The usage data reported is not estimated by eoPowerState.
or static but is the measured consumption rate.
- estimated(4): Indicates that the usage was not The eoPowerMeasurementCaliber object specifies how the
determined by physical measurement. The value is a usage value reported by eoPower was obtained. The eoPower
derivation based upon the device type, state, and/or value must report 0 if the eoPowerMeasurementCaliber is
current utilization using some algorithm or heuristic. It 'unavailable'. For devices that cannot measure or
is presumed that the entity's state and current report power, this option can be used."
configuration were used to compute the value. ::= { eoPowerEntry 1 }
- static(5): Indicates that the usage was not determined eoPowerNameplate OBJECT-TYPE
by physical measurement, algorithm or derivation. The SYNTAX Unsigned32
usage was reported based upon external tables, UNITS "watts"
specifications, and/or model information. For example, a MAX-ACCESS read-only
PC Model X draws 200W, while a PC Model Y draws 210W." STATUS current
::= { eoPowerEntry 5 } DESCRIPTION
"This object indicates the rated maximum consumption for
the fully populated Energy Object. The nameplate power
requirements are the maximum power numbers given in SI
watts and, in almost all cases, are well above the
expected operational consumption. Nameplate power is
widely used for power provisioning. This value is
specified in either units of watts or voltage and
current. The units are therefore SI watts or equivalent
Volt-Amperes with the magnitude (milliwatts, kilowatts,
etc.) indicated separately in eoPowerUnitMultiplier."
::= { eoPowerEntry 2 }
eoPowerCurrentType OBJECT-TYPE eoPowerUnitMultiplier OBJECT-TYPE
SYNTAX INTEGER { SYNTAX UnitMultiplier
ac(1), MAX-ACCESS read-only
dc(2), STATUS current
unknown(3) DESCRIPTION
} "The magnitude of watts for the usage value in eoPower
and eoPowerNameplate."
::= { eoPowerEntry 3 }
MAX-ACCESS read-only eoPowerAccuracy OBJECT-TYPE
STATUS current SYNTAX Integer32 (0..10000)
DESCRIPTION UNITS "hundredths of percent"
"This object indicates whether the eoPower for the MAX-ACCESS read-only
Energy Object reports alternating current 'ac', direct STATUS current
current 'dc', or that the current type is unknown." DESCRIPTION
::= { eoPowerEntry 6 } "This object indicates a percentage value, in hundredths of a
percent, representing the assumed accuracy of the usage
reported by eoPower. For example, the value 1010 means
the reported usage is accurate to +/- 10.1 percent. This
value is zero if the accuracy is unknown or not
applicable based upon the measurement method.
eoPowerMeasurementLocal OBJECT-TYPE ANSI and IEC define the following accuracy classes for
SYNTAX TruthValue power measurement:
MAX-ACCESS read-only IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
STATUS current ANSI C12.20 class 0.2, 0.5"
DESCRIPTION ::= { eoPowerEntry 4 }
"This object indicates the source of power measurement
and can be useful when modeling the power usage of
attached devices. The power measurement can be performed
by the entity itself or the power measurement of the
entity can be reported by another trusted entity using a
protocol extension. A value of true indicates the
measurement is performed by the entity, whereas false
indicates that the measurement was performed by another
entity."
::= { eoPowerEntry 7 }
eoPowerAdminState OBJECT-TYPE eoPowerMeasurementCaliber OBJECT-TYPE
SYNTAX PowerStateSet SYNTAX INTEGER {
MAX-ACCESS read-write unavailable(1) ,
STATUS current unknown(2),
DESCRIPTION actual(3) ,
"This object specifies the desired Power State and the estimated(4),
Power State Set for the Energy Object. Note that other(0) static(5) }
is not a Power State Set and unknown(255) is not a Power MAX-ACCESS read-only
State as such, but simply an indication that the Power STATUS current
State of the Energy Object is unknown. DESCRIPTION
Possible values of eoPowerAdminState within the Power "This object specifies how the usage value reported by
State Set are registered at IANA. eoPower was obtained:
A current list of assignments can be found at
http://www.iana.org/assignments/power-state-sets"
::= { eoPowerEntry 8 }
eoPowerOperState OBJECT-TYPE - unavailable(1): Indicates that the usage is not
SYNTAX PowerStateSet available. In such a case, the eoPower value must be 0
MAX-ACCESS read-only for devices that cannot measure or report power this
STATUS current option can be used.
DESCRIPTION
"This object specifies the current operational Power
State and the Power State Set for the Energy Object.
other(0) is not a Power State Set and unknown(255) is not
a Power State as such, but simply an indication that the
Power State of the Energy Object is unknown.
Possible values of eoPowerOperState within the Power - unknown(2): Indicates that the way the usage was
State Set are registered at IANA. A current list of determined is unknown. In some cases, entities report
assignments can be found at < aggregate power on behalf of another device. In such
http://www.iana.org/assignments/power-state-sets>" cases it is not known whether the usage reported is
::= { eoPowerEntry 9 } actual, estimated, or static.
eoPowerStateEnterReason OBJECT-TYPE - actual(3): Indicates that the reported usage was
SYNTAX OwnerString measured by the entity through some hardware or direct
MAX-ACCESS read-write physical means. The usage data reported is not estimated
STATUS current or static but is the measured consumption rate.
DESCRIPTION
"This string object describes the reason for the
eoPowerAdminState transition. Alternatively, this string
may contain with the entity that configured this Energy
Object to this Power State."
DEFVAL { "" }
::= { eoPowerEntry 10 }
eoPowerStateTable OBJECT-TYPE - estimated(4): Indicates that the usage was not
SYNTAX SEQUENCE OF EoPowerStateEntry determined by physical measurement. The value is a
MAX-ACCESS not-accessible derivation based upon the device type, state, and/or
STATUS current current utilization using some algorithm or heuristic. It
DESCRIPTION is presumed that the entity's state and current
"This table enumerates the maximum power usage, in watts, configuration were used to compute the value.
for every single supported Power State of each Energy
Object.
This table has cross-reference with the eoPowerTable, - static(5): Indicates that the usage was not determined
containing rows describing each Power State for the by physical measurement, algorithm, or derivation. The
corresponding Energy Object. For every Energy Object in usage was reported based upon external tables,
the eoPowerTable, there is a corresponding entry in this specifications, and/or model information. For example, a
table." PC Model X draws 200W, while a PC Model Y draws 210W."
::= { energyObjectMibObjects 3 } ::= { eoPowerEntry 5 }
eoPowerStateEntry OBJECT-TYPE eoPowerCurrentType OBJECT-TYPE
SYNTAX EoPowerStateEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible ac(1),
STATUS current dc(2),
DESCRIPTION unknown(3)
"A eoPowerStateEntry extends a corresponding }
eoPowerEntry. This entry displays max usage values at MAX-ACCESS read-only
every single possible Power State supported by the Energy STATUS current
Object. DESCRIPTION
For example, given the values of a Energy Object "This object indicates whether the eoPower for the
corresponding to a maximum usage of 0 W at the Energy Object reports alternating current 'ac', direct
state emanmechoff, 8 W at state 6 (ready), 11 W at state current 'dc', or that the current type is unknown."
emanmediumMinus,and 11 W at state emanhigh: ::= { eoPowerEntry 6 }
State MaxUsage Units eoPowerMeasurementLocal OBJECT-TYPE
emanmechoff 0 W SYNTAX TruthValue
emansoftoff 0 W MAX-ACCESS read-only
emanhibernate 0 W STATUS current
emansleep 0 W DESCRIPTION
emanstandby 0 W "This object indicates the source of power measurement
emanready 8 W and can be useful when modeling the power usage of
emanlowMinus 8 W attached devices. The power measurement can be performed
emanlow 11 W by the entity itself or the power measurement of the
emanmediumMinus 11 W entity can be reported by another trusted entity using a
emanmedium 11 W protocol extension. A value of true indicates the
emanhighMinus 11 W measurement is performed by the entity, whereas false
emnanhigh 11 W indicates that the measurement was performed by another
entity."
::= { eoPowerEntry 7 }
Furthermore, this table also includes the total time in eoPowerAdminState OBJECT-TYPE
each Power State, along with the number of times a SYNTAX PowerStateSet
particular Power State was entered." MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the desired Power State and the
Power State Set for the Energy Object. Note that other(0)
is not a Power State Set and unknown(255) is not a Power
State as such, but simply an indication that the Power
State of the Energy Object is unknown.
Possible values of eoPowerAdminState within the Power
State Set are registered at IANA.
A current list of assignments can be found at
<http://www.iana.org/assignments/power-state-sets>"
::= { eoPowerEntry 8 }
INDEX { entPhysicalIndex, eoPowerStateIndex } eoPowerOperState OBJECT-TYPE
::= { eoPowerStateTable 1 } SYNTAX PowerStateSet
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the current operational Power
State and the Power State Set for the Energy Object.
other(0) is not a Power State Set and unknown(255) is not
a Power State as such, but simply an indication that the
Power State of the Energy Object is unknown.
EoPowerStateEntry ::= SEQUENCE { Possible values of eoPowerOperState within the Power
eoPowerStateIndex PowerStateSet, State Set are registered at IANA. A current list of
eoPowerStateMaxPower INTEGER, assignments can be found at
eoPowerStatePowerUnitMultiplier UnitMultiplier, <http://www.iana.org/assignments/power-state-sets>"
eoPowerStateTotalTime TimeTicks, ::= { eoPowerEntry 9 }
eoPowerStateEnterCount Counter32
}
eoPowerStateIndex OBJECT-TYPE eoPowerStateEnterReason OBJECT-TYPE
SYNTAX PowerStateSet SYNTAX OwnerString
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the index of the Power State of "This string object describes the reason for the
the Energy Object within a Power State Set. The semantics eoPowerAdminState transition. Alternatively, this string
of the specific Power State can be obtained from the may contain with the entity that configured this Energy
Power State Set definition." Object to this Power State."
::= { eoPowerStateEntry 1 } DEFVAL { "" }
::= { eoPowerEntry 10 }
eoPowerStateMaxPower OBJECT-TYPE eoPowerStateTable OBJECT-TYPE
SYNTAX Integer32 SYNTAX SEQUENCE OF EoPowerStateEntry
UNITS "watts" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This table enumerates the maximum power usage, in watts,
"This object indicates the maximum power for the Energy for every single supported Power State of each Energy
Object at the particular Power State. This value is Object.
specified in SI units of watts with the magnitude of the
units (milliwatts, kilowatts, etc.) indicated separately
in eoPowerStatePowerUnitMultiplier. If the maximum power
is not known for a certain Power State, then the value is
encoded as 0xFFFFFFFF.
For Power States not enumerated, the value of This table has cross-reference with the eoPowerTable,
eoPowerStateMaxPower might be interpolated by using the containing rows describing each Power State for the
next highest supported Power State." corresponding Energy Object. For every Energy Object in
::= { eoPowerStateEntry 2 } the eoPowerTable, there is a corresponding entry in this
table."
::= { energyObjectMibObjects 3 }
eoPowerStatePowerUnitMultiplier OBJECT-TYPE eoPowerStateEntry OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX EoPowerStateEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in "A eoPowerStateEntry extends a corresponding
eoPowerStateMaxPower." eoPowerEntry. This entry displays max usage values at
::= { eoPowerStateEntry 3 } every single possible Power State supported by the Energy
Object.
For example, given the values of a Energy Object
corresponding to a maximum usage of 0 W at the
state emanmechoff, 8 W at state 6 (ready), 11 W at state
emanmediumMinus, and 11 W at state emanhigh:
eoPowerStateTotalTime OBJECT-TYPE State MaxUsage Units
SYNTAX TimeTicks emanmechoff 0 W
MAX-ACCESS read-only emansoftoff 0 W
STATUS current emanhibernate 0 W
DESCRIPTION emansleep 0 W
"This object indicates the total time in hundredths emanstandby 0 W
of second that the Energy Object has been in this power emanready 8 W
state since the last reset, as specified in the emanlowMinus 8 W
sysUpTime." emanlow 11 W
::= { eoPowerStateEntry 4 } emanmediumMinus 11 W
emanmedium 11 W
emanhighMinus 11 W
emnanhigh 11 W
eoPowerStateEnterCount OBJECT-TYPE Furthermore, this table also includes the total time in
SYNTAX Counter32 each Power State, along with the number of times a
MAX-ACCESS read-only particular Power State was entered."
STATUS current
DESCRIPTION
"This object indicates how often the Energy Object has
entered this power state, since the last reset of the
device as specified in the sysUpTime."
::= { eoPowerStateEntry 5 }
eoEnergyParametersTable OBJECT-TYPE INDEX { entPhysicalIndex, eoPowerStateIndex }
SYNTAX SEQUENCE OF EoEnergyParametersEntry ::= { eoPowerStateTable 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is used to configure the parameters for
Energy measurement collection in the table eoEnergyTable.
This table allows the configuration of different
measurement settings on the same Energy Object.
Implementation of this table only makes sense for Energy
Objects that an eoPowerMeasurementCaliber of actual."
::= { energyObjectMibObjects 4 }
eoEnergyParametersEntry OBJECT-TYPE EoPowerStateEntry ::= SEQUENCE {
SYNTAX EoEnergyParametersEntry eoPowerStateIndex PowerStateSet,
MAX-ACCESS not-accessible eoPowerStateMaxPower Integer32,
STATUS current eoPowerStatePowerUnitMultiplier UnitMultiplier,
DESCRIPTION eoPowerStateTotalTime TimeTicks,
"An entry controls an energy measurement in eoPowerStateEnterCount Counter32
eoEnergyTable." }
INDEX { entPhysicalIndex, eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 }
EoEnergyParametersEntry ::= SEQUENCE { eoPowerStateIndex OBJECT-TYPE
eoEnergyParametersIndex Integer32, SYNTAX PowerStateSet
eoEnergyParametersIntervalLength TimeInterval, MAX-ACCESS not-accessible
eoEnergyParametersIntervalNumber Unsigned32, STATUS current
eoEnergyParametersIntervalMode INTEGER, DESCRIPTION
eoEnergyParametersIntervalWindow TimeInterval, "This object specifies the index of the Power State of
eoEnergyParametersSampleRate Unsigned32, the Energy Object within a Power State Set. The semantics
eoEnergyParametersStorageType StorageType, of the specific Power State can be obtained from the
eoEnergyParametersStatus RowStatus Power State Set definition."
} ::= { eoPowerStateEntry 1 }
eoEnergyParametersIndex OBJECT-TYPE eoPowerStateMaxPower OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32
MAX-ACCESS not-accessible UNITS "watts"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"This object specifies the index of the Energy Parameters DESCRIPTION
setting for collection of energy measurements for an "This object indicates the maximum power for the Energy
Energy Object. An Energy Object can have multiple Object at the particular Power State. This value is
eoEnergyParametersIndex, depending on the capabilities of specified in SI units of watts with the magnitude of the
the Energy Object" units (milliwatts, kilowatts, etc.) indicated separately
::= { eoEnergyParametersEntry 2 } in eoPowerStatePowerUnitMultiplier. If the maximum power
is not known for a certain Power State, then the value is
encoded as 0xFFFFFFFF.
eoEnergyParametersIntervalLength OBJECT-TYPE For Power States not enumerated, the value of
SYNTAX TimeInterval eoPowerStateMaxPower might be interpolated by using the
MAX-ACCESS read-create next highest supported Power State."
STATUS current ::= { eoPowerStateEntry 2 }
DESCRIPTION
"This object indicates the length of time in hundredths
of seconds over which to compute the average
eoEnergyConsumed measurement in the eoEnergyTable table.
The computation is based on the Energy Object's internal
sampling rate of power consumed or produced by the Energy
Object. The sampling rate is the rate at which the Energy
Object can read the power usage and may differ based on
device capabilities. The average energy consumption is
then computed over the length of the interval. The
default value of 15 minutes is a common interval used in
industry."
DEFVAL { 90000 }
::= { eoEnergyParametersEntry 3 }
eoEnergyParametersIntervalNumber OBJECT-TYPE eoPowerStatePowerUnitMultiplier OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX UnitMultiplier
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of intervals maintained in the eoEnergyTable. "The magnitude of watts for the usage value in
Each interval is characterized by a specific eoPowerStateMaxPower."
eoEnergyCollectionStartTime, used as an index to the ::= { eoPowerStateEntry 3 }
table eoEnergyTable. Whenever the maximum number of
entries is reached, the measurement over the new interval
replaces the oldest measurement. There is one exception
to this rule: when the eoEnergyMaxConsumed and/or
eoEnergyMaxProduced are in (one of) the two oldest
measurement(s), they are left untouched and the next
oldest measurement is replaced."
DEFVAL { 10 }
::= { eoEnergyParametersEntry 4 }
eoEnergyParametersIntervalMode OBJECT-TYPE eoPowerStateTotalTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeTicks
period(1), MAX-ACCESS read-only
sliding(2), STATUS current
total(3) DESCRIPTION
} "This object indicates the total time in hundredths
MAX-ACCESS read-create of a second that the Energy Object has been in this power
STATUS current state since the last reset, as specified in the
DESCRIPTION sysUpTime."
"A control object to define the mode of interval ::= { eoPowerStateEntry 4 }
calculation for the computation of the average
eoEnergyConsumed or eoEnergyProvided measurement in the
eoEnergyTable table.
A mode of period(1) specifies non-overlapping periodic eoPowerStateEnterCount OBJECT-TYPE
measurements. SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates how often the Energy Object has
entered this power state, since the last reset of the
device as specified in the sysUpTime."
::= { eoPowerStateEntry 5 }
A mode of sliding(2) specifies overlapping sliding eoEnergyParametersTable OBJECT-TYPE
windows where the interval between the start of one SYNTAX SEQUENCE OF EoEnergyParametersEntry
interval and the next is defined in MAX-ACCESS not-accessible
eoEnergyParametersIntervalWindow. STATUS current
DESCRIPTION
"This table is used to configure the parameters for
energy measurement collection in the table eoEnergyTable.
This table allows the configuration of different
measurement settings on the same Energy Object.
Implementation of this table only makes sense for Energy
Objects that an eoPowerMeasurementCaliber of actual."
::= { energyObjectMibObjects 4 }
A mode of total(3) specifies non-periodic measurement. eoEnergyParametersEntry OBJECT-TYPE
In this mode only one interval is used as this is a SYNTAX EoEnergyParametersEntry
continuous measurement since the last reset. The value of MAX-ACCESS not-accessible
eoEnergyParametersIntervalNumber should be (1) one and STATUS current
eoEnergyParametersIntervalLength is ignored." DESCRIPTION
::= { eoEnergyParametersEntry 5 } "An entry controls an energy measurement in
eoEnergyTable."
INDEX { entPhysicalIndex, eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 }
eoEnergyParametersIntervalWindow OBJECT-TYPE EoEnergyParametersEntry ::= SEQUENCE {
SYNTAX TimeInterval eoEnergyParametersIndex Integer32,
MAX-ACCESS read-create eoEnergyParametersIntervalLength TimeInterval,
STATUS current eoEnergyParametersIntervalNumber Unsigned32,
DESCRIPTION eoEnergyParametersIntervalMode INTEGER,
"The length of the duration window between the starting eoEnergyParametersIntervalWindow TimeInterval,
time of one sliding window and the next starting time in eoEnergyParametersSampleRate Unsigned32,
hundredths of seconds, in order to compute the average of eoEnergyParametersStorageType StorageType,
eoEnergyConsumed, eoEnergyProvided measurements in the eoEnergyParametersStatus RowStatus
eoEnergyTable table. This is valid only when the }
eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyParametersIntervalWindow value should be a
multiple of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Integer32 (1..2147483647)
UNITS "Milliseconds" MAX-ACCESS not-accessible
MAX-ACCESS read-create STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This object specifies the index of the Energy Parameters
"The sampling rate, in milliseconds, at which the Energy setting for collection of energy measurements for an
Object should poll power usage in order to compute the Energy Object. An Energy Object can have multiple
average eoEnergyConsumed, eoEnergyProvided measurements eoEnergyParametersIndex, depending on the capabilities of
in the table eoEnergyTable. The Energy Object should the Energy Object"
initially set this sampling rate to a reasonable value, ::= { eoEnergyParametersEntry 2 }
i.e., a compromise between intervals that will provide
good accuracy by not being too long, but not so short
that they affect the Energy Object performance by
requesting continuous polling. If the sampling rate is
unknown, the value 0 is reported. The sampling rate
should be selected so that
eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate. The default value is one
second."
DEFVAL { 1000 }
::= { eoEnergyParametersEntry 7 }
eoEnergyParametersStorageType OBJECT-TYPE eoEnergyParametersIntervalLength OBJECT-TYPE
SYNTAX StorageType SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This object indicates the length of time in hundredths
DEFVAL { nonVolatile } of a second over which to compute the average
::= {eoEnergyParametersEntry 8 } eoEnergyConsumed measurement in the eoEnergyTable table.
The computation is based on the Energy Object's internal
sampling rate of power consumed or produced by the Energy
Object. The sampling rate is the rate at which the Energy
Object can read the power usage and may differ based on
device capabilities. The average energy consumption is
then computed over the length of the interval. The
default value of 15 minutes is a common interval used in
industry."
DEFVAL { 90000 }
::= { eoEnergyParametersEntry 3 }
eoEnergyParametersStatus OBJECT-TYPE eoEnergyParametersIntervalNumber OBJECT-TYPE
SYNTAX RowStatus SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row. The eoEnergyParametersStatus is "The number of intervals maintained in the eoEnergyTable.
used to start or stop energy usage logging. An entry Each interval is characterized by a specific
status may not be active(1) unless all objects in the eoEnergyCollectionStartTime, used as an index to the
entry have an appropriate value. If this object is not table eoEnergyTable. Whenever the maximum number of
equal to active, all associated usage-data logged into entries is reached, the measurement over the new interval
the eoEnergyTable will be deleted. The data can be replaces the oldest measurement. There is one exception
destroyed by setting up the eoEnergyParametersStatus to to this rule: when the eoEnergyMaxConsumed and/or
destroy." eoEnergyMaxProduced are in (one of) the two oldest
::= {eoEnergyParametersEntry 9 } measurement(s), they are left untouched and the next
oldest measurement is replaced."
DEFVAL { 10 }
::= { eoEnergyParametersEntry 4 }
eoEnergyTable OBJECT-TYPE eoEnergyParametersIntervalMode OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible period(1),
STATUS current sliding(2),
DESCRIPTION total(3)
"This table lists Energy Object energy measurements. }
Entries in this table are only created if the MAX-ACCESS read-create
corresponding value of object eoPowerMeasurementCaliber STATUS current
is active(3), i.e., if the power is actually metered." DESCRIPTION
::= { energyObjectMibObjects 5 } "A control object to define the mode of interval
calculation for the computation of the average
eoEnergyConsumed or eoEnergyProvided measurement in the
eoEnergyTable table.
eoEnergyEntry OBJECT-TYPE A mode of period(1) specifies non-overlapping periodic
SYNTAX EoEnergyEntry measurements.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describing energy measurements."
INDEX { eoEnergyParametersIndex,
eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 }
EoEnergyEntry ::= SEQUENCE { A mode of sliding(2) specifies overlapping sliding
eoEnergyCollectionStartTime TimeTicks, windows where the interval between the start of one
eoEnergyConsumed Unsigned32, interval and the next is defined in
eoEnergyProvided Unsigned32, eoEnergyParametersIntervalWindow.
eoEnergyStored Unsigned32,
eoEnergyUnitMultiplier UnitMultiplier,
eoEnergyAccuracy Integer32,
eoEnergyMaxConsumed Unsigned32,
eoEnergyMaxProduced Unsigned32,
eoEnergyDiscontinuityTime TimeStamp
}
eoEnergyCollectionStartTime OBJECT-TYPE A mode of total(3) specifies non-periodic measurement.
SYNTAX TimeTicks In this mode only one interval is used as this is a
UNITS "hundredths of seconds" continuous measurement since the last reset. The value of
MAX-ACCESS not-accessible eoEnergyParametersIntervalNumber should be (1) one and
STATUS current eoEnergyParametersIntervalLength is ignored."
DESCRIPTION ::= { eoEnergyParametersEntry 5 }
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized, as specified in the sysUpTime [RFC3418].
This object specifies the start time of the energy
measurement sample. "
::= { eoEnergyEntry 1 }
eoEnergyConsumed OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeInterval
UNITS "Watt-hours" MAX-ACCESS read-create
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The length of the duration window between the starting
"This object indicates the energy consumed in units of time of one sliding window and the next starting time in
watt-hours for the Energy Object over the defined hundredths of seconds, used to compute the average of
interval. This value is specified in the common billing eoEnergyConsumed, eoEnergyProvided measurements in the
units of watt-hours with the magnitude of watt-hours (kW- eoEnergyTable table. This is valid only when the
Hr, MW-Hr, etc.) indicated separately in eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyUnitMultiplier." eoEnergyParametersIntervalWindow value should be a
::= { eoEnergyEntry 2 } multiple of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 6 }
eoEnergyProvided OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Watt-hours" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy produced in units of "The sampling rate, in milliseconds, at which the Energy
watt-hours for the Energy Object over the defined Object should poll power usage in order to compute the
interval. average eoEnergyConsumed, eoEnergyProvided measurements
in the table eoEnergyTable. The Energy Object should
initially set this sampling rate to a reasonable value,
i.e., a compromise between intervals that will provide
good accuracy by not being too long, but not so short
that they affect the Energy Object performance by
requesting continuous polling. If the sampling rate is
unknown, the value 0 is reported. The sampling rate
should be selected so that
eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate. The default value is one
second."
DEFVAL { 1000 }
::= { eoEnergyParametersEntry 7 }
This value is specified in the common billing units of eoEnergyParametersStorageType OBJECT-TYPE
watt-hours with the magnitude of watt-hours (kW-Hr, MW- SYNTAX StorageType
Hr, etc.) indicated separately in MAX-ACCESS read-create
eoEnergyUnitMultiplier." STATUS current
::= { eoEnergyEntry 3 } DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { nonVolatile }
::= {eoEnergyParametersEntry 8 }
eoEnergyStored OBJECT-TYPE eoEnergyParametersStatus OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX RowStatus
UNITS "Watt-hours" MAX-ACCESS read-create
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The status of this row. The eoEnergyParametersStatus is
"This object indicates the difference of the energy used to start or stop energy usage logging. An entry
consumed and energy produced for an Energy Object in status may not be active(1) unless all objects in the
units of watt-hours for the Energy Object over the entry have an appropriate value. If this object is not
defined interval. This value is specified in the common equal to active, all associated usage-data logged into
billing units of watt-hours with the magnitude of watt- the eoEnergyTable will be deleted. The data can be
hours (kW-Hr, MW-Hr, etc.) indicated separately in destroyed by setting up the eoEnergyParametersStatus to
eoEnergyUnitMultiplier." destroy."
::= { eoEnergyEntry 4 } ::= {eoEnergyParametersEntry 9 }
eoEnergyUnitMultiplier OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the magnitude of watt-hours for the "This table lists Energy Object energy measurements.
energy field in eoEnergyConsumed, eoEnergyProvided, Entries in this table are only created if the
eoEnergyStored, eoEnergyMaxConsumed, and corresponding value of object eoPowerMeasurementCaliber
eoEnergyMaxProduced." is active(3), i.e., if the power is actually metered."
::= { eoEnergyEntry 5 } ::= { energyObjectMibObjects 5 }
eoEnergyAccuracy OBJECT-TYPE eoEnergyEntry OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX EoEnergyEntry
UNITS "hundredths of percent" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "An entry describing energy measurements."
"This object indicates a percentage accuracy, in 100ths INDEX { eoEnergyParametersIndex,
of a percent, of Energy usage reporting. eoEnergyAccuracy eoEnergyCollectionStartTime }
is applicable to all Energy measurements in the ::= { eoEnergyTable 1 }
eoEnergyTable.
For example: 1010 means the reported usage is accurate to EoEnergyEntry ::= SEQUENCE {
+/- 10.1 percent. eoEnergyCollectionStartTime TimeTicks,
eoEnergyConsumed Unsigned32,
eoEnergyProvided Unsigned32,
eoEnergyStored Unsigned32,
eoEnergyUnitMultiplier UnitMultiplier,
eoEnergyAccuracy Integer32,
eoEnergyMaxConsumed Unsigned32,
eoEnergyMaxProduced Unsigned32,
eoEnergyDiscontinuityTime TimeStamp
}
This value is zero if the accuracy is unknown." eoEnergyCollectionStartTime OBJECT-TYPE
::= { eoEnergyEntry 6 } SYNTAX TimeTicks
UNITS "hundredths of a second"
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized, as specified in the sysUpTime RFC 3418.
This object specifies the start time of the energy
measurement sample."
REFERENCE
"RFC 3418: Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)"
::= { eoEnergyEntry 1 }
eoEnergyMaxConsumed OBJECT-TYPE eoEnergyConsumed OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy observed in "This object indicates the energy consumed in units of
eoEnergyConsumed since the monitoring started or was watt-hours for the Energy Object over the defined
reinitialized. This value is specified in the common interval. This value is specified in the common billing
billing units of watt-hours with the magnitude of watt- units of watt-hours with the magnitude of watt-hours
hours (kW-Hr, MW-Hr, etc.) indicated separately in kWh, MWh, etc.) indicated separately in
eoEnergyUnitMultiplier." eoEnergyUnitMultiplier."
::= { eoEnergyEntry 7 } ::= { eoEnergyEntry 2 }
eoEnergyMaxProduced OBJECT-TYPE eoEnergyProvided OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy ever observed in "This object indicates the energy produced in units of
eoEnergyEnergyProduced since the monitoring started. This watt-hours for the Energy Object over the defined
value is specified in the units of watt-hours with the interval.
magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated
separately in eoEnergyEnergyUnitMultiplier."
::= { eoEnergyEntry 8 }
eoEnergyDiscontinuityTime OBJECT-TYPE This value is specified in the common billing units of
SYNTAX TimeStamp watt-hours with the magnitude of watt-hours (kWh, MWh,
MAX-ACCESS read-only etc.) indicated separately in
STATUS current eoEnergyUnitMultiplier."
DESCRIPTION ::= { eoEnergyEntry 3 }
"The value of sysUpTime [RFC3418] on the most recent
occasion at which any one or more of this entity's energy
counters in this table suffered a discontinuity:
eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If
no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then
this object contains a zero value."
::= { eoEnergyEntry 9 }
-- Notifications eoEnergyStored OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Watt-hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the difference of the energy
consumed and energy produced for an Energy Object in
units of watt-hours for the Energy Object over the
defined interval. This value is specified in the common
billing units of watt-hours with the magnitude of
watt-hours (kWh, MWh, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 }
eoPowerEnableStatusNotification eoEnergyUnitMultiplier OBJECT-TYPE
OBJECT-TYPE SYNTAX UnitMultiplier
SYNTAX TruthValue MAX-ACCESS read-only
MAX-ACCESS read-write STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This object is the magnitude of watt-hours for the
"This object controls whether the system produces energy field in eoEnergyConsumed, eoEnergyProvided,
notifications for eoPowerStateChange. A false value will eoEnergyStored, eoEnergyMaxConsumed, and
prevent these notifications from being generated." eoEnergyMaxProduced."
DEFVAL { false } ::= { eoEnergyEntry 5 }
::= { energyObjectMibNotifs 1 }
eoPowerStateChange NOTIFICATION-TYPE eoEnergyAccuracy OBJECT-TYPE
OBJECTS {eoPowerAdminState, eoPowerOperState, SYNTAX Integer32 (0..10000)
eoPowerStateEnterReason} UNITS "hundredths of percent"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The SNMP entity generates the eoPowerStateChange when DESCRIPTION
the values of eoPowerAdminState or eoPowerOperState, "This object indicates a percentage accuracy, in hundredths
in the context of the Power State Set, have changed for of a percent, of Energy usage reporting. eoEnergyAccuracy
the Energy Object represented by the entPhysicalIndex." is applicable to all Energy measurements in the
::= { energyObjectMibNotifs 2 } eoEnergyTable.
-- Conformance For example, 1010 means the reported usage is accurate to
+/- 10.1 percent.
energyObjectMibCompliances OBJECT IDENTIFIER This value is zero if the accuracy is unknown."
::= { energyObjectMibConform 1 } ::= { eoEnergyEntry 6 }
energyObjectMibGroups OBJECT IDENTIFIER eoEnergyMaxConsumed OBJECT-TYPE
::= { energyObjectMibConform 2 } SYNTAX Unsigned32
UNITS "Watt-hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the maximum energy observed in
eoEnergyConsumed since the monitoring started or was
reinitialized. This value is specified in the common
billing units of watt-hours with the magnitude of
watt-hours (kWh, MWh, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 7 }
energyObjectMibFullCompliance MODULE-COMPLIANCE eoEnergyMaxProduced OBJECT-TYPE
STATUS current SYNTAX Unsigned32
DESCRIPTION UNITS "Watt-hours"
"When this MIB is implemented with support for MAX-ACCESS read-only
read-create, then such an implementation can STATUS current
claim full compliance. Such devices can then DESCRIPTION
be both monitored and configured with this MIB. "This object is the maximum energy ever observed in
eoEnergyEnergyProduced since the monitoring started. This
value is specified in the units of watt-hours with the
magnitude of watt-hours (kWh, MWh, etc.) indicated
separately in eoEnergyEnergyUnitMultiplier."
::= { eoEnergyEntry 8 }
Module Compliance of [RFC6933] eoEnergyDiscontinuityTime OBJECT-TYPE
with respect to entity4CRCompliance MUST SYNTAX TimeStamp
be supported which requires implementation MAX-ACCESS read-only
of 4 MIB objects: entPhysicalIndex, entPhysicalClass, STATUS current
entPhysicalName and entPhysicalUUID." DESCRIPTION
MODULE -- this module "The value of sysUpTime RFC 3418 on the most recent
MANDATORY-GROUPS { occasion at which any one or more of this entity's energy
energyObjectMibTableGroup, counters in this table suffered a discontinuity:
energyObjectMibStateTableGroup, eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If
eoPowerEnableStatusNotificationGroup, no such discontinuities have occurred since the last
energyObjectMibNotifGroup re-initialization of the local management subsystem, then
} this object contains a zero value."
REFERENCE
"RFC 3418: Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)"
::= { eoEnergyEntry 9 }
GROUP energyObjectMibEnergyTableGroup -- Notifications
DESCRIPTION "A compliant implementation does not
have to implement."
GROUP energyObjectMibEnergyParametersTableGroup eoPowerEnableStatusNotification
DESCRIPTION "A compliant implementation does not OBJECT-TYPE
have to implement." SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls whether the system produces
notifications for eoPowerStateChange. A false value will
prevent these notifications from being generated."
DEFVAL { false }
::= { energyObjectMibNotifs 1 }
GROUP energyObjectMibMeterCapabilitiesTableGroup eoPowerStateChange NOTIFICATION-TYPE
DESCRIPTION "A compliant implementation does not OBJECTS {eoPowerAdminState, eoPowerOperState,
have to implement." eoPowerStateEnterReason}
::= { energyObjectMibCompliances 1 } STATUS current
DESCRIPTION
"The SNMP entity generates the eoPowerStateChange when
the values of eoPowerAdminState or eoPowerOperState,
in the context of the Power State Set, have changed for
the Energy Object represented by the entPhysicalIndex."
::= { energyObjectMibNotifs 2 }
energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE -- Conformance
STATUS current
DESCRIPTION
"When this MIB is implemented without support for
read-create (i.e., in read-only mode), then such an
implementation can claim read-only compliance. Such a
device can then be monitored but cannot be
configured with this MIB.
Module Compliance of [RFC6933] with respect to energyObjectMibCompliances OBJECT IDENTIFIER
entity4CRCompliance MUST be supported which requires ::= { energyObjectMibConform 1 }
implementation of 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and entPhysicalUUID."
MODULE -- this module
MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
energyObjectMibNotifGroup
}
OBJECT eoPowerOperState energyObjectMibGroups OBJECT IDENTIFIER
MIN-ACCESS read-only ::= { energyObjectMibConform 2 }
DESCRIPTION energyObjectMibFullCompliance MODULE-COMPLIANCE
"Write access is not required." STATUS current
::= { energyObjectMibCompliances 2 } DESCRIPTION
"When this MIB is implemented with support for
read-create, then such an implementation can
claim full compliance. Such devices can then
be both monitored and configured with this MIB.
-- Units of Conformance Module Compliance of RFC 6933
with respect to entity4CRCompliance MUST
be supported, which requires implementation
of four MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
REFERENCE
"RFC 6933: Entity MIB (Version 4)"
MODULE -- this module
MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
eoPowerEnableStatusNotificationGroup,
energyObjectMibNotifGroup
}
energyObjectMibTableGroup OBJECT-GROUP GROUP energyObjectMibEnergyTableGroup
OBJECTS {
eoPower,
eoPowerNameplate,
eoPowerUnitMultiplier,
eoPowerAccuracy,
eoPowerMeasurementCaliber,
eoPowerCurrentType,
eoPowerMeasurementLocal,
eoPowerAdminState,
eoPowerOperState,
eoPowerStateEnterReason
}
STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "A compliant implementation does not
related to the Energy Object." have to implement."
::= { energyObjectMibGroups 1 }
energyObjectMibStateTableGroup OBJECT-GROUP
OBJECTS {
eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime,
eoPowerStateEnterCount
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Power State."
::= { energyObjectMibGroups 2 }
energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS {
eoEnergyParametersIntervalLength,
eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate,
eoEnergyParametersStorageType,
eoEnergyParametersStatus
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the configuration of the Energy Table."
::= { energyObjectMibGroups 3 }
energyObjectMibEnergyTableGroup OBJECT-GROUP
OBJECTS {
-- Note that object
-- eoEnergyCollectionStartTime is not
-- included since it is not-accessible
eoEnergyConsumed,
eoEnergyProvided,
eoEnergyStored,
eoEnergyUnitMultiplier,
eoEnergyAccuracy,
eoEnergyMaxConsumed,
eoEnergyMaxProduced,
eoEnergyDiscontinuityTime
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Table."
::= { energyObjectMibGroups 4 }
energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP
OBJECTS {
eoMeterCapability
}
STATUS current
DESCRIPTION
"This group contains the object indicating the capability
of the Energy Object"
::= { energyObjectMibGroups 5 }
eoPowerEnableStatusNotificationGroup OBJECT-GROUP
OBJECTS { eoPowerEnableStatusNotification }
STATUS current
DESCRIPTION
"The collection of objects which are used to enable
notification."
::= { energyObjectMibGroups 6 }
energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS {
eoPowerStateChange
}
STATUS current
DESCRIPTION
"This group contains the notifications for
the Power, Energy Monitoring and Control MIB Module."
::= { energyObjectMibGroups 7 }
END
9.3. The POWER-ATTRIBUTES-MIB MIB Module
-- ************************************************************
--
-- This MIB module is used to monitor power attributes of
-- networked devices with measurements.
--
-- This MIB module is an extension of energyObjectMib module.
--
-- *************************************************************
POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
mib-2,
Integer32, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
UnitMultiplier
FROM ENERGY-OBJECT-MIB
entPhysicalIndex
FROM ENTITY-MIB;
powerAttributesMIB MODULE-IDENTITY
LAST-UPDATED "201406070000Z" -- 07 June 2014
ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists:
General Discussion: eman@ietf.org
To Subscribe:
https://www.ietf.org/mailman/listinfo/eman
Archive:
http://www.ietf.org/mail-archive/web/eman
Editors:
Mouli Chandramouli
Cisco Systems, Inc.
Sarjapur Outer Ring Road
Bangalore 560103
IN
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
Brad Schoening
44 Rivers Edge Drive
Little Silver, NJ 07739
US
Email: brad.schoening@verizon.net
Juergen Quittek GROUP energyObjectMibEnergyParametersTableGroup
NEC Europe Ltd. DESCRIPTION
NEC Laboratories Europe "A compliant implementation does not
Network Research Division have to implement."
Kurfuersten-Anlage 36
Heidelberg 69115
DE
Phone: +49 6221 4342-115
Email: quittek@neclab.eu
Thomas Dietz GROUP energyObjectMibMeterCapabilitiesTableGroup
NEC Europe Ltd. DESCRIPTION
NEC Laboratories Europe "A compliant implementation does not
Network Research Division have to implement."
Kurfuersten-Anlage 36 ::= { energyObjectMibCompliances 1 }
69115 Heidelberg
DE
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE
Cisco Systems, Inc. STATUS current
De Kleetlaan 6a b1 DESCRIPTION
Degem 1831 "When this MIB is implemented without support for
Belgium read-create (i.e., in read-only mode), then such an
Phone: +32 2 704 5622 implementation can claim read-only compliance. Such a
Email: bclaise@cisco.com" device can then be monitored but cannot be
configured with this MIB.
DESCRIPTION Module Compliance of [RFC6933] with respect to
"This MIB is used to report AC power attributes in entity4CRCompliance MUST be supported which requires
devices. The table is a sparse augmentation of the implementation of 4 MIB objects: entPhysicalIndex,
eoPowerTable table from the energyObjectMib module. entPhysicalClass, entPhysicalName and entPhysicalUUID."
Both three-phase and single-phase power REFERENCE
configurations are supported. "RFC 6933: Entity MIB (Version 4)"
MODULE -- this module
MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
energyObjectMibNotifGroup
}
As a requirement for this MIB module, ::= { energyObjectMibCompliances 2 }
[EMAN-AWARE-MIB] SHOULD be implemented.
Module Compliance of ENTITY-MIB v4 with respect to -- Units of Conformance
entity4CRCompliance MUST be supported which requires
implementation of 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and
entPhysicalUUID."
REVISION "201406070000Z" -- 07 June 2014 energyObjectMibTableGroup OBJECT-GROUP
DESCRIPTION OBJECTS {
"Initial version, published as RFC XXXX" eoPower,
eoPowerNameplate,
eoPowerUnitMultiplier,
eoPowerAccuracy,
eoPowerMeasurementCaliber,
eoPowerCurrentType,
eoPowerMeasurementLocal,
eoPowerAdminState,
eoPowerOperState,
eoPowerStateEnterReason
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Object."
::= { energyObjectMibGroups 1 }
-- RFC Editor, please replace zzz with the IANA allocation energyObjectMibStateTableGroup OBJECT-GROUP
-- for this MIB module and XXXX with the number of the OBJECTS {
-- approved RFC eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime,
eoPowerStateEnterCount
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Power State."
::= { energyObjectMibGroups 2 }
::= { mib-2 zzz } energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS {
eoEnergyParametersIntervalLength,
eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate,
eoEnergyParametersStorageType,
eoEnergyParametersStatus
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the configuration of the Energy Table."
::= { energyObjectMibGroups 3 }
powerAttributesMIBConform OBJECT IDENTIFIER energyObjectMibEnergyTableGroup OBJECT-GROUP
::= { powerAttributesMIB 0 } OBJECTS {
-- Note that object
-- eoEnergyCollectionStartTime is not
-- included since it is not-accessible
eoEnergyConsumed,
eoEnergyProvided,
eoEnergyStored,
eoEnergyUnitMultiplier,
eoEnergyAccuracy,
eoEnergyMaxConsumed,
eoEnergyMaxProduced,
eoEnergyDiscontinuityTime
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Table."
::= { energyObjectMibGroups 4 }
powerAttributesMIBObjects OBJECT IDENTIFIER energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP
::= { powerAttributesMIB 1 } OBJECTS {
eoMeterCapability
}
STATUS current
DESCRIPTION
"This group contains the object indicating the capability
of the Energy Object"
::= { energyObjectMibGroups 5 }
-- Objects eoPowerEnableStatusNotificationGroup OBJECT-GROUP
OBJECTS { eoPowerEnableStatusNotification }
STATUS current
DESCRIPTION
"The collection of objects that are used to enable
notification."
::= { energyObjectMibGroups 6 }
eoACPwrAttributesTable OBJECT-TYPE energyObjectMibNotifGroup NOTIFICATION-GROUP
SYNTAX SEQUENCE OF EoACPwrAttributesEntry NOTIFICATIONS {
MAX-ACCESS not-accessible eoPowerStateChange
STATUS current }
DESCRIPTION STATUS current
"This table contains power attributes measurements for DESCRIPTION
supported entPhysicalIndex entities. It is a sparse "This group contains the notifications for
extension of the eoPowerTable." the Monitoring and Control MIB for Power and Energy."
::= { powerAttributesMIBObjects 1 } ::= { energyObjectMibGroups 7 }
eoACPwrAttributesEntry OBJECT-TYPE END
SYNTAX EoACPwrAttributesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is a sparse extension of the eoPowerTable with
entries for power attributes measurements or
configuration. Each measured value corresponds to an
attribute in IEC 61850-7-4 for non-phase measurements
within the object MMUX."
INDEX { entPhysicalIndex }
::= { eoACPwrAttributesTable 1 }
EoACPwrAttributesEntry ::= SEQUENCE { 9.3. The POWER-ATTRIBUTES-MIB MIB Module
eoACPwrAttributesConfiguration INTEGER,
eoACPwrAttributesAvgVoltage Integer32,
eoACPwrAttributesAvgCurrent Unsigned32,
eoACPwrAttributesFrequency Integer32,
eoACPwrAttributesPowerUnitMultiplier UnitMultiplier,
eoACPwrAttributesPowerAccuracy Integer32,
eoACPwrAttributesTotalActivePower Integer32,
eoACPwrAttributesTotalReactivePower Integer32,
eoACPwrAttributesTotalApparentPower Integer32,
eoACPwrAttributesTotalPowerFactor Integer32,
eoACPwrAttributesThdCurrent Integer32,
eoACPwrAttributesThdVoltage Integer32
}
eoACPwrAttributesConfiguration OBJECT-TYPE -- ************************************************************
SYNTAX INTEGER { --
sngl(1), -- This MIB module is used to monitor power attributes of
del(2), -- networked devices with measurements.
wye(3) --
} -- This MIB module is an extension of energyObjectMib module.
MAX-ACCESS read-only --
STATUS current -- *************************************************************
DESCRIPTION
"Configuration describes the physical configurations of
the power supply lines:
* alternating current, single phase (SNGL) POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN
* alternating current, three phase delta (DEL)
* alternating current, three phase Y (WYE)
Three-phase configurations can be either connected in a IMPORTS
triangular delta (DEL) or star Y (WYE) system. WYE MODULE-IDENTITY,
systems have a shared neutral voltage, while DEL systems OBJECT-TYPE,
do not. Each phase is offset 120 degrees to each other." mib-2,
::= { eoACPwrAttributesEntry 1 } Integer32, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
UnitMultiplier
FROM ENERGY-OBJECT-MIB
entPhysicalIndex
FROM ENTITY-MIB;
eoACPwrAttributesAvgVoltage OBJECT-TYPE powerAttributesMIB MODULE-IDENTITY
SYNTAX Integer32 LAST-UPDATED "201502090000Z" -- 9 February 2015
UNITS "0.1 Volt AC" ORGANIZATION "IETF EMAN Working Group"
MAX-ACCESS read-only CONTACT-INFO
STATUS current "WG charter:
DESCRIPTION http://datatracker.ietf.org/wg/eman/charter/
"A measured value for average of the voltage measured
over an integral number of AC cycles For a 3-phase
system, this is the average voltage (V1+V2+V3)/3. IEC
61850-7-4 measured value attribute 'Vol'"
::= { eoACPwrAttributesEntry 2 }
eoACPwrAttributesAvgCurrent OBJECT-TYPE Mailing Lists:
SYNTAX Unsigned32 General Discussion: eman@ietf.org
UNITS "amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value for average of the current measured
over an integral number of AC cycles For a 3-phase
system, this is the average current (I1+I2+I3)/3. IEC
61850-7-4 attribute 'Amp'"
::= { eoACPwrAttributesEntry 3 }
eoACPwrAttributesFrequency OBJECT-TYPE To Subscribe:
SYNTAX Integer32 (4500..6500) https://www.ietf.org/mailman/listinfo/eman
UNITS "0.01 hertz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value for the basic frequency of the AC
circuit. IEC 61850-7-4 attribute 'Hz'."
::= { eoACPwrAttributesEntry 4 }
eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE Archive:
SYNTAX UnitMultiplier http://www.ietf.org/mail-archive/web/eman
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The magnitude of watts for the usage value in
eoACPwrAttributesTotalActivePower,
eoACPwrAttributesTotalReactivePower
and eoACPwrAttributesTotalApparentPower measurements.
For 3-phase power systems, this will also include
eoACPwrAttributesWyeActivePower,
eoACPwrAttributesWyeReactivePower and
eoACPwrAttributesWyeApparentPower"
::= { eoACPwrAttributesEntry 5 }
eoACPwrAttributesPowerAccuracy OBJECT-TYPE Editors:
SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a percentage value, in 100ths of a
percent, representing the presumed accuracy of active,
reactive, and apparent power usage reporting. For
example: 1010 means the reported usage is accurate to +/-
10.1 percent. This value is zero if the accuracy is
unknown.
ANSI and IEC define the following accuracy classes for Mouli Chandramouli
power measurement: IEC 62053-22 & 60044-1 class 0.1, 0.2, Cisco Systems, Inc.
0.5, 1 & 3. Sarjapur Outer Ring Road
ANSI C12.20 class 0.2 & 0.5" Bangalore 560103
::= { eoACPwrAttributesEntry 6 } India
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
eoACPwrAttributesTotalActivePower OBJECT-TYPE Brad Schoening
SYNTAX Integer32 44 Rivers Edge Drive
UNITS "watts" Little Silver, NJ 07739
MAX-ACCESS read-only United States
STATUS current Email: brad.schoening@verizon.net
DESCRIPTION
"A measured value of the actual power delivered to or
consumed by the load. IEC 61850-7-4 attribute 'TotW'."
::= { eoACPwrAttributesEntry 7 }
eoACPwrAttributesTotalReactivePower OBJECT-TYPE Juergen Quittek
SYNTAX Integer32 NEC Europe Ltd.
UNITS "volt-amperes reactive" NEC Laboratories Europe
MAX-ACCESS read-only Network Research Division
STATUS current Kurfuersten-Anlage 36
DESCRIPTION Heidelberg 69115
"A measured value of the reactive portion of the apparent Germany
power. IEC 61850-7-4 attribute 'TotVAr'." Phone: +49 6221 4342-115
::= { eoACPwrAttributesEntry 8 } Email: quittek@neclab.eu
eoACPwrAttributesTotalApparentPower OBJECT-TYPE Thomas Dietz
SYNTAX Integer32 NEC Europe Ltd.
UNITS "volt-amperes" NEC Laboratories Europe
MAX-ACCESS read-only Network Research Division
STATUS current Kurfuersten-Anlage 36
DESCRIPTION 69115 Heidelberg
"A measured value of the voltage and current which Germany
determines the apparent power. The apparent power is the Phone: +49 6221 4342-128
vector sum of real and reactive power. Email: Thomas.Dietz@nw.neclab.eu
Note: watts and volt-amperes are equivalent units and may Benoit Claise
be combined. IEC 61850-7-4 attribute 'TotVA'." Cisco Systems, Inc.
::= { eoACPwrAttributesEntry 9 } De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
eoACPwrAttributesTotalPowerFactor OBJECT-TYPE DESCRIPTION
SYNTAX Integer32 (-10000..10000) "Copyright (c) 2015 IETF Trust and the persons identified as
UNITS "hundredths" authors of the code. All rights reserved.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value ratio of the real power flowing to the
load versus the apparent power. It is dimensionless and
expressed here as a percentage value in 100ths. A power
factor of 100% indicates there is no inductance load and
thus no reactive power. Power Factor can be positive or
negative, where the sign should be in lead/lag (IEEE)
form. IEC 61850-7-4 attribute 'TotPF'."
::= { eoACPwrAttributesEntry 10 }
eoACPwrAttributesThdCurrent OBJECT-TYPE Redistribution and use in source and binary forms, with or
SYNTAX Integer32 (0..10000) without modification, is permitted pursuant to, and subject
UNITS "hundredths of percent" to the license terms contained in, the Simplified BSD License
MAX-ACCESS read-only set forth in Section 4.c of the IETF Trust's Legal Provisions
STATUS current Relating to IETF Documents
DESCRIPTION (http://trustee.ietf.org/license-info).
"A calculated value for the current total harmonic
distortion (THD). Method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdAmp'."
::= { eoACPwrAttributesEntry 11 }
eoACPwrAttributesThdVoltage OBJECT-TYPE This MIB is used to report AC power attributes in devices.
SYNTAX Integer32 (0..10000) The table is a sparse augmentation of the eoPowerTable table
UNITS "hundredths of percent" from the energyObjectMib module. Both three-phase and
MAX-ACCESS read-only single-phase power configurations are supported.
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
distortion (THD). Method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdVol'."
::= { eoACPwrAttributesEntry 12 }
eoACPwrAttributesDelPhaseTable OBJECT-TYPE As a requirement for this MIB module, RFC 7461 SHOULD be
SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry implemented.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This optional table describes 3-phase power attributes
measurements in a DEL configuration with phase-to-phase
power attributes measurements. Entities having single
phase power shall not have any entities. This is a
sparse extension of the eoACPwrAttributesTable.
These attributes correspond to IEC 61850-7.4 MMXU phase Module Compliance of ENTITY-MIB v4 with respect to
related measurements and MHAI phase related measured entity4CRCompliance MUST be supported which requires
harmonic or interharmonics." implementation of four MIB objects: entPhysicalIndex,
::= { powerAttributesMIBObjects 2 } entPhysicalClass, entPhysicalName, and entPhysicalUUID."
REVISION "201502090000Z" -- 9 February 2015
DESCRIPTION
"Initial version, published as RFC 7460"
eoACPwrAttributesDelPhaseEntry OBJECT-TYPE ::= { mib-2 230 }
SYNTAX EoACPwrAttributesDelPhaseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes power measurements of a phase in a
DEL 3-phase power. Three entries are required for each
supported entPhysicalIndex entry. Voltage measurements
are provided relative to each other.
For phase-to-phase measurements, the powerAttributesMIBConform OBJECT IDENTIFIER
eoACPwrAttributesDelPhaseIndex is compared against the ::= { powerAttributesMIB 0 }
following phase at +120 degrees. Thus, the possible
values are:
eoACPwrAttributesDelPhaseIndex Next Phase Angle powerAttributesMIBObjects OBJECT IDENTIFIER
0 120 ::= { powerAttributesMIB 1 }
120 240
240 0
"
INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex }
::= { eoACPwrAttributesDelPhaseTable 1}
EoACPwrAttributesDelPhaseEntry ::= SEQUENCE { -- Objects
eoACPwrAttributesDelPhaseIndex Integer32,
eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32
}
eoACPwrAttributesDelPhaseIndex OBJECT-TYPE eoACPwrAttributesTable OBJECT-TYPE
SYNTAX Integer32 (0..359) SYNTAX SEQUENCE OF EoACPwrAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240." "This table contains power attributes measurements for
::= { eoACPwrAttributesDelPhaseEntry 1 } supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable."
::= { powerAttributesMIBObjects 1 }
eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrAttributesEntry OBJECT-TYPE
SYNTAX Integer32 SYNTAX EoACPwrAttributesEntry
UNITS "0.1 Volt AC" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This is a sparse extension of the eoPowerTable with
"A measured value of phase to next phase voltages, where entries for power attributes measurements or
the next phase is IEC 61850-7-4 attribute 'PPV'." configuration. Each measured value corresponds to an
::= { eoACPwrAttributesDelPhaseEntry 2 } attribute in IEC 61850-7-4 for non-phase measurements
within the object MMXN."
INDEX { entPhysicalIndex }
::= { eoACPwrAttributesTable 1 }
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage OBJECT-TYPE EoACPwrAttributesEntry ::= SEQUENCE {
SYNTAX Integer32 (0..10000) eoACPwrAttributesConfiguration INTEGER,
UNITS "hundredths of percent" eoACPwrAttributesAvgVoltage Integer32,
MAX-ACCESS read-only eoACPwrAttributesAvgCurrent Unsigned32,
STATUS current eoACPwrAttributesFrequency Integer32,
DESCRIPTION eoACPwrAttributesPowerUnitMultiplier UnitMultiplier,
"A calculated value for the voltage total harmonic eoACPwrAttributesPowerAccuracy Integer32,
disortion for phase to next phase. Method of calculation eoACPwrAttributesTotalActivePower Integer32,
is not specified. IEC 61850-7-4 attribute 'ThdPPV'." eoACPwrAttributesTotalReactivePower Integer32,
::= { eoACPwrAttributesDelPhaseEntry 3 } eoACPwrAttributesTotalApparentPower Integer32,
eoACPwrAttributesTotalPowerFactor Integer32,
eoACPwrAttributesThdCurrent Integer32,
eoACPwrAttributesThdVoltage Integer32
}
eoACPwrAttributesWyePhaseTable OBJECT-TYPE eoACPwrAttributesConfiguration OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible sngl(1),
STATUS current del(2),
DESCRIPTION wye(3)
"This optional table describes 3-phase power attributes }
measurements in a WYE configuration with phase-to-neutral MAX-ACCESS read-only
power attributes measurements. Entities having single STATUS current
phase power shall not have any entities. This is a sparse DESCRIPTION
extension of the eoACPwrAttributesTable. "Configuration describes the physical configurations of
the power supply lines:
These attributes correspond to IEC 61850-7.4 MMXU phase * alternating current, single phase (SNGL)
related measurements and MHAI phase related measured * alternating current, three-phase delta (DEL)
harmonic or interharmonics." * alternating current, three-phase Y (WYE)
::= { powerAttributesMIBObjects 3 }
eoACPwrAttributesWyePhaseEntry OBJECT-TYPE Three-phase configurations can be either connected in a
SYNTAX EoACPwrAttributesWyePhaseEntry triangular delta (DEL) or star Y (WYE) system. WYE
MAX-ACCESS not-accessible systems have a shared neutral voltage, while DEL systems
STATUS current do not. Each phase is offset 120 degrees to each other."
DESCRIPTION ::= { eoACPwrAttributesEntry 1 }
"This table describes measurements of a phase in a WYE 3-
phase power system. Three entries are required for each
supported entPhysicalIndex entry. Voltage measurements
are relative to neutral.
Each entry describes power attributes of one phase of a eoACPwrAttributesAvgVoltage OBJECT-TYPE
WYE 3-phase power system." SYNTAX Integer32
INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex } UNITS "0.1 Volt AC"
::= { eoACPwrAttributesWyePhaseTable 1} MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value for average of the voltage measured
over an integral number of AC cycles. For a three-phase
system, this is the average voltage (V1+V2+V3)/3. IEC
61850-7-4 measured value attribute 'Vol'."
::= { eoACPwrAttributesEntry 2 }
EoACPwrAttributesWyePhaseEntry ::= SEQUENCE { eoACPwrAttributesAvgCurrent OBJECT-TYPE
eoACPwrAttributesWyePhaseIndex Integer32, SYNTAX Unsigned32
eoACPwrAttributesWyePhaseToNeutralVoltage Integer32, UNITS "amperes"
eoACPwrAttributesWyeCurrent Integer32, MAX-ACCESS read-only
eoACPwrAttributesWyeActivePower Integer32, STATUS current
eoACPwrAttributesWyeReactivePower Integer32, DESCRIPTION
eoACPwrAttributesWyeApparentPower Integer32, "A measured value for average of the current measured
eoACPwrAttributesWyePowerFactor Integer32, over an integral number of AC cycles. For a three-phase
eoACPwrAttributesWyeThdCurrent Integer32, system, this is the average current (I1+I2+I3)/3. IEC
eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32 61850-7-4 attribute 'Amp'."
} ::= { eoACPwrAttributesEntry 3 }
eoACPwrAttributesWyePhaseIndex OBJECT-TYPE eoACPwrAttributesFrequency OBJECT-TYPE
SYNTAX Integer32 (0..359) SYNTAX Integer32 (4500..6500)
MAX-ACCESS not-accessible UNITS "0.01 hertz"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"A phase angle typically corresponding to 0, 120, 240." DESCRIPTION
::= { eoACPwrAttributesWyePhaseEntry 1 } "A measured value for the basic frequency of the AC
circuit. IEC 61850-7-4 attribute 'Hz'."
::= { eoACPwrAttributesEntry 4 }
eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE
SYNTAX Integer32 SYNTAX UnitMultiplier
UNITS "0.1 Volt AC" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The magnitude of watts for the usage value in
"A measured value of phase to neutral voltage. IEC eoACPwrAttributesTotalActivePower,
61850-7-4 attribute 'PNV'." eoACPwrAttributesTotalReactivePower,
::= { eoACPwrAttributesWyePhaseEntry 2 } and eoACPwrAttributesTotalApparentPower measurements.
For three-phase power systems, this will also include
eoACPwrAttributesWyeActivePower,
eoACPwrAttributesWyeReactivePower, and
eoACPwrAttributesWyeApparentPower."
::= { eoACPwrAttributesEntry 5 }
eoACPwrAttributesWyeCurrent OBJECT-TYPE eoACPwrAttributesPowerAccuracy OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..10000)
UNITS "0.1 amperes AC" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of phase currents. IEC 61850-7-4 "This object indicates a percentage value, in hundredths of a
attribute 'A'." percent, representing the presumed accuracy of active,
::= { eoACPwrAttributesWyePhaseEntry 3 } reactive, and apparent power usage reporting. For
example, 1010 means the reported usage is accurate to +/-
10.1 percent. This value is zero if the accuracy is
unknown.
eoACPwrAttributesWyeActivePower OBJECT-TYPE ANSI and IEC define the following accuracy classes for
SYNTAX Integer32 power measurement: IEC 62053-22 & 60044-1 class 0.1, 0.2,
UNITS "watts" 0.5, 1, & 3.
MAX-ACCESS read-only ANSI C12.20 class 0.2 & 0.5"
STATUS current ::= { eoACPwrAttributesEntry 6 }
DESCRIPTION
"A measured value of the actual power delivered to or
consumed by the load with the magnitude indicated
separately in eoPowerUnitMultiplier. IEC 61850-7-4
attribute 'W'"
::= { eoACPwrAttributesWyePhaseEntry 4 }
eoACPwrAttributesWyeReactivePower OBJECT-TYPE eoACPwrAttributesTotalActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes reactive" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the reactive portion of the apparent "A measured value of the actual power delivered to or
power with the magnitude of indicated separately in consumed by the load. IEC 61850-7-4 attribute 'TotW'."
eoPowerUnitMultiplier. IEC 61850-7-4 attribute 'VAr'" ::= { eoACPwrAttributesEntry 7 }
::= { eoACPwrAttributesWyePhaseEntry 5 }
eoACPwrAttributesWyeApparentPower OBJECT-TYPE eoACPwrAttributesTotalReactivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes reactive"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the voltage and current determines "A measured value of the reactive portion of the apparent
the apparent power with the indicated separately in power. IEC 61850-7-4 attribute 'TotVAr'."
eoPowerUnitMultiplier. Active plus reactive power equals ::= { eoACPwrAttributesEntry 8 }
the total apparent power.
Note: Watts and volt-amperes are equivalent units and may eoACPwrAttributesTotalApparentPower OBJECT-TYPE
be combined. IEC 61850-7-4 attribute 'VA'." SYNTAX Integer32
::= { eoACPwrAttributesWyePhaseEntry 6 } UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the voltage and current that
determines the apparent power. The apparent power is the
vector sum of real and reactive power.
eoACPwrAttributesWyePowerFactor OBJECT-TYPE Note: watts and volt-amperes are equivalent units and may
SYNTAX Integer32 (-10000..10000) be combined. IEC 61850-7-4 attribute 'TotVA'."
UNITS "hundredths" ::= { eoACPwrAttributesEntry 9 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value ratio of the real power flowing to the
load versus the apparent power for this phase. IEC
61850-7-4 attribute 'PF'. Power Factor can be positive or
negative where the sign should be in lead/lag (IEEE)
form."
::= { eoACPwrAttributesWyePhaseEntry 7 }
eoACPwrAttributesWyeThdCurrent OBJECT-TYPE eoACPwrAttributesTotalPowerFactor OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "hundredths"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value for the voltage total harmonic "A measured value ratio of the real power flowing to the
disortion (THD) for phase to phase. Method of load versus the apparent power. It is dimensionless and
calculation is not specified. expressed here as a percentage value in hundredths. A power
IEC 61850-7-4 attribute 'ThdA'." factor of 100% indicates there is no inductance load and
::= { eoACPwrAttributesWyePhaseEntry 8 } thus no reactive power. A Power Factor can be positive or
negative, where the sign should be in lead/lag (IEEE)
form. IEC 61850-7-4 attribute 'TotPF'."
::= { eoACPwrAttributesEntry 10 }
eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesThdCurrent OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value of the voltage total harmonic "A calculated value for the current total harmonic
distortion (THD) for phase to neutral. IEC 61850-7-4 distortion (THD). Method of calculation is not
attribute 'ThdPhV'." specified. IEC 61850-7-4 attribute 'ThdAmp'."
::= { eoACPwrAttributesWyePhaseEntry 9 } ::= { eoACPwrAttributesEntry 11 }
-- Conformance eoACPwrAttributesThdVoltage OBJECT-TYPE
powerAttributesMIBCompliances OBJECT IDENTIFIER SYNTAX Integer32 (0..10000)
::= { powerAttributesMIB 2 } UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
distortion (THD). The method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdVol'."
::= { eoACPwrAttributesEntry 12 }
powerAttributesMIBGroups OBJECT IDENTIFIER eoACPwrAttributesDelPhaseTable OBJECT-TYPE
::= { powerAttributesMIB 3 } SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This optional table describes three-phase power attributes
measurements in a DEL configuration with phase-to-phase
power attributes measurements. Entities having single
phase power shall not have any entities. This is a
sparse extension of the eoACPwrAttributesTable.
powerAttributesMIBFullCompliance MODULE-COMPLIANCE These attributes correspond to measurements related to
STATUS current the IEC 61850-7.4 MMXU phase and measured harmonic or
DESCRIPTION interharmonics related to the MHAI phase."
"When this MIB is implemented with support for read- ::= { powerAttributesMIBObjects 2 }
create, then such an implementation can claim full
compliance. Such devices can then be both monitored and
configured with this MIB.
Module Compliance of [RFC6933] with respect to eoACPwrAttributesDelPhaseEntry OBJECT-TYPE
entity4CRCompliance MUST be supported which requires SYNTAX EoACPwrAttributesDelPhaseEntry
implementation of 4 MIB objects: entPhysicalIndex, MAX-ACCESS not-accessible
entPhysicalClass, entPhysicalName and entPhysicalUUID." STATUS current
DESCRIPTION
"An entry describes power measurements of a phase in a
DEL three-phase power. Three entries are required for each
supported entPhysicalIndex entry. Voltage measurements
are provided relative to each other.
MODULE -- this module For phase-to-phase measurements, the
MANDATORY-GROUPS { eoACPwrAttributesDelPhaseIndex is compared against the
powerACPwrAttributesMIBTableGroup following phase at +120 degrees. Thus, the possible
} values are:
GROUP powerACPwrAttributesOptionalMIBTableGroup eoACPwrAttributesDelPhaseIndex Next Phase Angle
DESCRIPTION 0 120
"A compliant implementation does not have 120 240
to implement." 240 0
"
INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex }
::= { eoACPwrAttributesDelPhaseTable 1}
GROUP powerACPwrAttributesDelPhaseMIBTableGroup EoACPwrAttributesDelPhaseEntry ::= SEQUENCE {
DESCRIPTION eoACPwrAttributesDelPhaseIndex Integer32,
"A compliant implementation does not have to implement." eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32
}
GROUP powerACPwrAttributesWyePhaseMIBTableGroup eoACPwrAttributesDelPhaseIndex OBJECT-TYPE
DESCRIPTION SYNTAX Integer32 (0..359)
"A compliant implementation does not have to implement." MAX-ACCESS not-accessible
::= { powerAttributesMIBCompliances 1 } STATUS current
DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesDelPhaseEntry 1 }
-- Units of Conformance eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 Volt AC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of phase to next phase voltages, where
the next phase is IEC 61850-7-4 attribute 'PPV'."
::= { eoACPwrAttributesDelPhaseEntry 2 }
powerACPwrAttributesMIBTableGroup OBJECT-GROUP eoACPwrAttributesDelThdPhaseToNextPhaseVoltage OBJECT-TYPE
OBJECTS { SYNTAX Integer32 (0..10000)
-- Note that object entPhysicalIndex is NOT UNITS "hundredths of percent"
-- included since it is not-accessible MAX-ACCESS read-only
eoACPwrAttributesAvgVoltage, STATUS current
eoACPwrAttributesAvgCurrent, DESCRIPTION
eoACPwrAttributesFrequency, "A calculated value for the voltage total harmonic
eoACPwrAttributesPowerUnitMultiplier, distortion for phase to next phase. Method of calculation
eoACPwrAttributesPowerAccuracy, is not specified. IEC 61850-7-4 attribute 'ThdPPV'."
eoACPwrAttributesTotalActivePower, ::= { eoACPwrAttributesDelPhaseEntry 3 }
eoACPwrAttributesTotalReactivePower,
eoACPwrAttributesTotalApparentPower,
eoACPwrAttributesTotalPowerFactor
}
STATUS current
DESCRIPTION
"This group contains the collection of all the power
attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 1 }
powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP eoACPwrAttributesWyePhaseTable OBJECT-TYPE
OBJECTS { SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry
eoACPwrAttributesConfiguration, MAX-ACCESS not-accessible
eoACPwrAttributesThdCurrent, STATUS current
eoACPwrAttributesThdVoltage DESCRIPTION
} "This optional table describes three-phase power attributes
STATUS current measurements in a WYE configuration with phase-to-neutral
DESCRIPTION power attributes measurements. Entities having single
"This group contains the collection of all the power phase power shall not have any entities. This is a sparse
attributes objects related to the Energy Object." extension of the eoACPwrAttributesTable.
::= { powerAttributesMIBGroups 2 }
powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP These attributes correspond to measurements related to
OBJECTS { the IEC 61850-7.4 MMXU phase and measured harmonic or
-- Note that object entPhysicalIndex and interharmonics related to the MHAI phase."
-- eoACPwrAttributesDelPhaseIndex are NOT ::= { powerAttributesMIBObjects 3 }
-- included since they are not-accessible
eoACPwrAttributesDelPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage
}
STATUS current
DESCRIPTION
"This group contains the collection of all power
attributes of a phase in a DEL 3-phase power system."
::= { powerAttributesMIBGroups 3 }
powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP eoACPwrAttributesWyePhaseEntry OBJECT-TYPE
OBJECTS { SYNTAX EoACPwrAttributesWyePhaseEntry
-- Note that object entPhysicalIndex and MAX-ACCESS not-accessible
-- eoACPwrAttributesWyePhaseIndex are NOT STATUS current
-- included since they are not-accessible DESCRIPTION
eoACPwrAttributesWyePhaseToNeutralVoltage, "This table describes measurements of a phase in a WYE
eoACPwrAttributesWyeCurrent, three-phase power system. Three entries are required for
eoACPwrAttributesWyeActivePower, each supported entPhysicalIndex entry. Voltage
eoACPwrAttributesWyeReactivePower, measurements are relative to neutral.
eoACPwrAttributesWyeApparentPower,
eoACPwrAttributesWyePowerFactor,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage,
eoACPwrAttributesWyeThdCurrent
}
STATUS current Each entry describes power attributes of one phase of a
DESCRIPTION WYE three-phase power system."
"This group contains the collection of all power INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex }
attributes of a phase in a WYE 3-phase power system." ::= { eoACPwrAttributesWyePhaseTable 1}
::= { powerAttributesMIBGroups 4 }
END EoACPwrAttributesWyePhaseEntry ::= SEQUENCE {
eoACPwrAttributesWyePhaseIndex Integer32,
eoACPwrAttributesWyePhaseToNeutralVoltage Integer32,
eoACPwrAttributesWyeCurrent Integer32,
eoACPwrAttributesWyeActivePower Integer32,
eoACPwrAttributesWyeReactivePower Integer32,
eoACPwrAttributesWyeApparentPower Integer32,
eoACPwrAttributesWyePowerFactor Integer32,
eoACPwrAttributesWyeThdCurrent Integer32,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
}
10. Implementation Status eoACPwrAttributesWyePhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesWyePhaseEntry 1 }
[Note to RFC Editor: Please remove this section and the eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE
reference to [RFC6982] before publication.] SYNTAX Integer32
UNITS "0.1 Volt AC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of phase to neutral voltage. IEC
61850-7-4 attribute 'PNV'."
::= { eoACPwrAttributesWyePhaseEntry 2 }
This section records the status of known implementations of the eoACPwrAttributesWyeCurrent OBJECT-TYPE
EMAN-Monitoring MIB at the time of posting of this Internet- SYNTAX Integer32
Draft, and is based on a proposal described in [RFC6982]. UNITS "0.1 amperes AC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of phase currents. IEC 61850-7-4
attribute 'A'."
::= { eoACPwrAttributesWyePhaseEntry 3 }
The description of implementations in this section is intended eoACPwrAttributesWyeActivePower OBJECT-TYPE
to assist the IETF in its decision processes in progressing SYNTAX Integer32
drafts to RFCs. UNITS "watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the actual power delivered to or
consumed by the load with the magnitude indicated
separately in eoPowerUnitMultiplier. IEC 61850-7-4
attribute 'W'."
::= { eoACPwrAttributesWyePhaseEntry 4 }
10.1. SNMP Research eoACPwrAttributesWyeReactivePower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes reactive"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the reactive portion of the apparent
power with the magnitude of indicated separately in
eoPowerUnitMultiplier. IEC 61850-7-4 attribute 'VAr'."
::= { eoACPwrAttributesWyePhaseEntry 5 }
Organization: SNMP Research, Inc. eoACPwrAttributesWyeApparentPower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the voltage and current determines
the apparent power with the indicated separately in
eoPowerUnitMultiplier. Active plus reactive power equals
the total apparent power.
Maturity: Prototype based upon early drafts of the MIBs. Note: Watts and volt-amperes are equivalent units and may
We anticipate updating it to more recent be combined. IEC 61850-7-4 attribute 'VA'."
documents as development schedules allow. ::= { eoACPwrAttributesWyePhaseEntry 6 }
Coverage: Code was generated to implement all MIB objects eoACPwrAttributesWyePowerFactor OBJECT-TYPE
in ENTITY-MIB (Version 4), SYNTAX Integer32 (-10000..10000)
ENERGY-OBJECT-CONTEXT-MIB, UNITS "hundredths"
ENERGY-OBJECT-MIB, MAX-ACCESS read-only
POWER-ATTRIBUTES-MIB, STATUS current
and BATTERY-MIB. DESCRIPTION
"A measured value ratio of the real power flowing to the
load versus the apparent power for this phase. IEC
61850-7-4 attribute 'PF'. Power Factor can be positive or
negative where the sign should be in lead/lag (IEEE)
form."
::= { eoACPwrAttributesWyePhaseEntry 7 }
Implementation experience: The documents are implementable. eoACPwrAttributesWyeThdCurrent OBJECT-TYPE
SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
distortion (THD) for phase to phase. Method of
calculation is not specified.
IEC 61850-7-4 attribute 'ThdA'."
::= { eoACPwrAttributesWyePhaseEntry 8 }
Comments: Technical comments about the eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE
ENERGY-OBJECT-CONTEXT-MIB, SYNTAX Integer32 (0..10000)
ENERGY-OBJECT-MIB, and UNITS "hundredths of percent"
BATTERY-MIB MAX-ACCESS read-only
were submitted to the EMAN Working Group STATUS current
E-mail list. DESCRIPTION
"A calculated value of the voltage total harmonic
distortion (THD) for phase to neutral. IEC 61850-7-4
attribute 'ThdPhV'."
::= { eoACPwrAttributesWyePhaseEntry 9 }
Licensing: Proprietary, royalty licensing -- Conformance
Contact: Alan Luchuk, luchuk at snmp.com powerAttributesMIBCompliances OBJECT IDENTIFIER
::= { powerAttributesMIB 2 }
URL: http://www.snmp.com/ powerAttributesMIBGroups OBJECT IDENTIFIER
::= { powerAttributesMIB 3 }
10.2. Cisco Systems powerAttributesMIBFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"When this MIB is implemented with support for read-
create, then such an implementation can claim full
compliance. Such devices can then be both monitored and
configured with this MIB.
Organization: Cisco Systems, Inc. Module Compliance of RFC 6933 with respect to
entity4CRCompliance MUST be supported which requires
implementation of four MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName, and entPhysicalUUID."
REFERENCE
"RFC 6933: Entity MIB (Version 4)"
Maturity: Prototype based upon early version drafts of MODULE -- this module
the MIBs. We anticipate updating the MIB MANDATORY-GROUPS {
modules as when the drafts are updated. powerACPwrAttributesMIBTableGroup
}
Coverage: Code was generated to implement all MIB objects GROUP powerACPwrAttributesOptionalMIBTableGroup
in the ENTITY-MIB (Version 4), and DESCRIPTION
ENERGY-OBJECT-MIB. "A compliant implementation does not have
to implement."
Implementation experience: The MIB modules are implemented GROUP powerACPwrAttributesDelPhaseMIBTableGroup
on Cisco router platforms to measure and report DESCRIPTION
router energy measurements. The documents are "A compliant implementation does not have to implement."
implementable.
Licensing: Proprietary GROUP powerACPwrAttributesWyePhaseMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to implement."
::= { powerAttributesMIBCompliances 1 }
URL: http://www.cisco.com -- Units of Conformance
11. Security Considerations powerACPwrAttributesMIBTableGroup OBJECT-GROUP
OBJECTS {
-- Note that object entPhysicalIndex is NOT
-- included since it is not-accessible
eoACPwrAttributesAvgVoltage,
eoACPwrAttributesAvgCurrent,
eoACPwrAttributesFrequency,
eoACPwrAttributesPowerUnitMultiplier,
eoACPwrAttributesPowerAccuracy,