draft-ietf-eman-energy-monitoring-mib-09.txt   draft-ietf-eman-energy-monitoring-mib-10.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
B. Claise B. Claise
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: August 14 2014 Independent Consultant Expires: December 7 2014 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
February 14, 2014 June 7, 2014
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-09 draft-ietf-eman-energy-monitoring-mib-10
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance Status of this Memo
with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet This Internet-Draft is submitted to IETF in full conformance
Engineering Task Force (IETF), its areas, and its working with the provisions of BCP 78 and BCP 79.
groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet
months and may be updated, replaced, or obsoleted by other Engineering Task Force (IETF), its areas, and its working
documents at any time. It is inappropriate to use Internet- groups. Note that other groups may also distribute working
Drafts as reference material or to cite them other than as documents as Internet-Drafts.
"work in progress."
The list of current Internet-Drafts can be accessed at Internet-Drafts are draft documents valid for a maximum of six
http://www.ietf.org/ietf/1id-abstracts.txt 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 Internet-Draft Shadow Directories can be accessed The list of current Internet-Drafts can be accessed at
at http://www.ietf.org/shadow.html http://www.ietf.org/ietf/1id-abstracts.txt
This Internet-Draft will expire on August 2014. The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html
Copyright Notice This Internet-Draft will expire on August 2014.
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright Notice
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Copyright (c) 2014 IETF Trust and the persons identified as the
Provisions Relating to IETF Documents document authors. All rights reserved.
(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 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.
This document defines a subset of the Management Information Abstract
Base (MIB) for power and energy monitoring of devices.
Conventions used in this document This document defines a subset of the Management Information
Base (MIB) for power and energy monitoring of devices.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL Conventions used in this document
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119].
Table of Contents 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].
1. Introduction.............................................. 3 Table of Contents
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. 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
10. Implementation Status................................... 62
10.1. SNMP Research......................................... 62
10.2. Cisco Systems......................................... 62
11. Security Considerations................................. 63
12. IANA Considerations..................................... 64
13. Contributors............................................ 64
14. Acknowledgment.......................................... 65
15. References.............................................. 65
15.1. Normative References.................................. 65
15.2. Informative References................................ 66
1. Introduction 1. Introduction ..............................................3
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. 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 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 .........................................61
11. Security Considerations .................................62
12. IANA Considerations......................................63
12.1. IANAPowerStateSet-MIB module ..........................63
13. Contributors ............................................64
14. Acknowledgment ..........................................64
15. References ..............................................64
15.1. Normative References ..................................64
15.2. Informative References ................................65
This document defines a subset of the Management Information 1. Introduction
Base (MIB) for use in energy management of devices within or
connected to communication networks. The MIB modules in this
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 [EMAN-FMWK], which, in turn, is based on
the Requirements for Energy Management [RFC6988].
Energy management can be applied to devices in communication This document defines a subset of the Management Information
networks. Target devices for this specification include (but are Base (MIB) for use in energy management of devices within or
not limited to): routers, switches, Power over Ethernet (PoE) connected to communication networks. The MIB modules in this
endpoints, protocol gateways for building management systems, document are designed to provide a model for energy management,
intelligent meters, home energy gateways, hosts and servers, which includes monitoring for Power State and energy consumption
sensor proxies, etc. Target devices and the use cases for Energy of networked elements. This MIB takes into account the Energy
Management are discussed in Energy Management Applicability Management Framework [EMAN-FMWK], which, in turn, is based on
Statement [EMAN-AS]. 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].
Where applicable, device monitoring extends to the individual Where applicable, device monitoring extends to the individual
components of the device and to any attached dependent devices. components of the device and to any attached dependent devices.
For example: A device can contain components that are For example: A device can contain components that are
independent from a power-state point of view, such as line independent from a power-state point of view, such as line
cards, processor cards, hard drives. A device can also have cards, processor cards, hard drives. A device can also have
dependent attached devices, such as a switch with PoE endpoints dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints. or a power distribution unit with attached endpoints.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please refer to current Internet-Standard Management Framework, please refer to
section 7 of RFC 3410 [RFC3410]. section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. MIB objects are termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management generally accessed through the Simple Network Management
Protocol (SNMP). Objects in the MIB are defined using the Protocol (SNMP). Objects in the MIB are defined using the
mechanisms defined in the Structure of Management Information mechanisms defined in the Structure of Management Information
(SMI). This memo specifies MIB modules that are compliant to (SMI). This memo specifies MIB modules that are compliant to
SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58,
RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
3. Use Cases 3. Use Cases
Requirements for power and energy monitoring for networking Requirements for power and energy monitoring for networking
devices are specified in [RFC6988]. The requirements in devices are specified in [RFC6988]. The requirements in
[RFC6988] cover devices typically found in communications [RFC6988] cover devices typically found in communications
networks, such as switches, routers, and various connected networks, such as switches, routers, and various connected
endpoints. For a power monitoring architecture to be useful, it endpoints. For a power monitoring architecture to be useful, it
should also apply to facility meters, power distribution units, should also apply to facility meters, power distribution units,
gateway proxies for commercial building control, home automation gateway proxies for commercial building control, home automation
devices, and devices that interface with the utility and/or devices, and devices that interface with the utility and/or
smart grid. Accordingly, the scope of the MIB modules in this smart grid. Accordingly, the scope of the MIB modules in this
document are broader than that specified in [RFC6988]. Several document are broader than that specified in [RFC6988]. Several
use cases for Energy Management have been identified in the use cases for Energy Management have been identified in the
"Energy Management (EMAN) Applicability Statement" [EMAN-AS]. "Energy Management (EMAN) Applicability Statement" [EMAN-AS].
4. Terminology 4. Terminology
Please refer to [EMAN-FMWK] for the definitions of the Please refer to [EMAN-FMWK] for the definitions of the
following terminology used in this draft. following terminology used in this draft.
Energy Management Energy Management
Energy Management System (EnMS) Energy Management System (EnMS)
Energy Monitoring Energy Monitoring
Energy Control Energy Control
electrical equipment 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
non-electrical equipment (mechanical equipment) 5. Architecture Concepts Applied to the MIB Modules
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 This section describes the concepts specified in the Energy
Management Framework [EMAN-FMWK] 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 [EMAN-FMWK].
This section describes the concepts specified in the Energy The Energy Monitoring MIB has 2 independent MIB modules, ENERGY-
Management Framework [EMAN-FMWK] that pertain to power usage, OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first, ENERGY-OBJECT-
with specific information related to the MIB module specified in MIB, is focused on measurement of power and energy. The second,
this document. This subsection maps concepts developed in the POWER-ATTRIBUTES-MIB, is focused on power quality measurements
Energy Management Framework [EMAN-FMWK]. for Energy Objects.
The Energy Monitoring MIB has 2 independent MIB modules, ENERGY- Devices and their sub-components can be modeled using the
OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first, ENERGY-OBJECT- containment tree of the ENTITY-MIB [RFC6933].
MIB, is focused on measurement of power and energy. The second,
POWER-ATTRIBUTES-MIB, is focused on power quality measurements
for Energy Objects.
Devices and their sub-components can be modeled using the 5.1. Energy Object Tables
containment tree of the ENTITY-MIB [RFC6933].
5.1. Energy Object Tables 5.1.1. ENERGY-OBJECT-MIB
5.1.1. ENERGY-OBJECT-MIB The ENERGY-OBJECT-MIB module consists of five tables.
The ENERGY-OBJECT-MIB module consists of five 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 eoMeterCapabilitiesTable. It indicates The second table is the eoPowerTable. It reports the power
the instrumentation available for each Energy Object. Entries consumption of each Energy Object, as well as the units, sign,
in this table indicate which other tables from the ENERGY- measurement accuracy, and related objects. The eoPowerTable is
OBJECT-MIB and POWER-ATTRIBUTES-MIB are available for each indexed by entPhysicalIndex.
Energy Object. The eoMeterCapabilitiesTable is indexed by
entPhysicalIndex [RFC6933].
The second table is the eoPowerTable. It reports the power The third table is the eoPowerStateTable. For each Energy
consumption of each Energy Object, as well as the units, sign, Object, it reports information and statistics about the
measurement accuracy, and related objects. The eoPowerTable is supported Power States. The eoPowerStateTable is indexed by
indexed by entPhysicalIndex. entPhysicalIndex and eoPowerStateIndex.
The third table is the eoPowerStateTable. For each Energy The fourth table is the eoEnergyParametersTable. The entries in
Object, it reports information and statistics about the this table configure the parameters of energy and demand
supported Power States. The eoPowerStateTable is indexed by measurement collection. This table is indexed by
entPhysicalIndex and eoPowerStateIndex. eoEnergyParametersIndex.
The fourth table is the eoEnergyParametersTable. The entries in The fifth table is the eoEnergyTable. The entries in this table
this table configure the parameters of energy and demand provide a log of the energy and demand information. This table
measurement collection. This table is indexed by is indexed by eoEnergyParametersIndex.
eoEnergyParametersIndex. A "smidump-style" tree presentation of the MIB modules contained
in the draft is presented. The meaning of the three symbols in
is a compressed representation of the object's MAX-ACCESS clause
which may have the following values:
The fifth table is the eoEnergyTable. The entries in this table "not-accessible" -> "---"
provide a log of the energy and demand information. This table "accessible-for-notify" -> "--n"
is indexed by eoEnergyParametersIndex. "read-only" -> "r-n"
A "smidump-style" tree presentation of the MIB modules contained "read-write" -> "rwn"
in the draft is presented. The meaning of the three symbols in
is a compressed representation of the object's MAX-ACCESS clause
which may have the following values:
"not-accessible"->"---" eoMeterCapabilitiesTable(1)
"accessible-for-notify"->"--n" |
"read-only"->"r-n" +---eoMeterCapabilitiesEntry(1)[entPhysicalIndex]
"read-write"->"rwn" | |
| +---r-n BITS eoMeterCapability
|
eoMeterCapabilitiesTable(1) eoPowerTable(2)
| |
+---eoMeterCapabilitiesEntry(1)[entPhysicalIndex] +---eoPowerEntry(1) [entPhysicalIndex]
| | | |
| +---r-n BITS eoMeterCapability | +---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)
eoPowerTable(2) 5.1.2. POWER-ATTRIBUTES-MIB
|
+---eoPowerEntry(1) [entPhysicalIndex]
| |
| +---r-n Integer32 eoPower(1)
| +-- r-n Integer32 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 IANAPowerStateSet eoPowerAdminState(8)
| +-- r-n IANAPowerStateSet eoPowerOperState(9)
| +-- r-n OwnerString eoPowerStateEnterReason(10)
|
|
+---eoPowerStateTable(3)
| +--eoPowerStateEntry(1)
| | [entPhysicalIndex, eoPowerStateIndex]
| |
| +-- --n IANAPowerStateSet 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)
| +-- r-n TimeInterval eoEnergyParametersIntervalLength(3)
| +-- r-n Integer32 eoEnergyParametersIntervalNumber(4)
| +-- r-n INTEGER eoEnergyParametersIntervalMode(5)
| +-- r-n TimeInterval eoEnergyParametersIntervalWindow(6)
| +-- r-n Integer32 eoEnergyParametersSampleRate(7)
| +-- r-n RowStatus eoEnergyParametersStatus(8)
|
+eoEnergyTable(5)
+---eoEnergyEntry(1)
| [eoEnergyParametersIndex,eoEnergyCollectionStartTime]
|
| +-- r-n TimeTicks eoEnergyCollectionStartTime(1)
| +-- r-n Integer32 eoEnergyConsumed(2)
| +-- r-n Integer32 eoEnergyProvided(3)
| +-- r-n Integer32 eoEnergyStored(4)
| +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5)
| +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyMaxConsumed(7)
| +-- r-n Integer32 eoEnergyMaxProduced(8)
| +-- r-n TimeTicks eoEnergyDiscontinuityTime(9)
5.1.2. POWER-ATTRIBUTES-MIB The POWER-ATTRIBUTES-MIB module consists of three tables.
The POWER-ATTRIBUTES-MIB module consists of three tables. The first table is the eoACPwrAttributesTable. It indicates the
power quality available for each Energy Object. The
eoACPwrAttributesTable is indexed by entPhysicalIndex [RFC6933].
The first table is the eoACPwrAttributesTable. It indicates the The second table is the eoACPwrAttributesDelPhaseTable. The
power quality available for each Energy Object. The entries in this table configure the parameters of energy and
eoACPwrAttributesTable is indexed by entPhysicalIndex [RFC6933]. demand measurement collection. This table is indexed by
eoEnergyParametersIndex.
The second table is the eoACPwrAttributesDelPhaseTable. The The third table is the eoACPwrAttributesWyePhaseTable. For each
entries in this table configure the parameters of energy and Energy Object, it reports information and statistics about the
demand measurement collection. This table is indexed by supported Power States. The eoPowerStateTable is indexed by
eoEnergyParametersIndex. entPhysicalIndex and eoPowerStateIndex.
The third table is the eoACPwrAttributesWyePhaseTable. For each eoACPwrAttributesTable(1)
Energy Object, it reports information and statistics about the |
supported Power States. The eoPowerStateTable is indexed by +---eoACPwrAttributesEntry(1) [ entPhysicalIndex]
entPhysicalIndex and eoPowerStateIndex. | |
| +---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)
eoACPwrAttributesTable(1) 5.1.3. UML Diagram
|
+---eoACPwrAttributesEntry(1) [ entPhysicalIndex]
| |
| +---r-n INTEGER eoACPwrAttributesConfiguration(1)
| +-- r-n Integer32 eoACPwrAttributesAvgVoltage(2)
| +-- r-n Integer32 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 UML diagram representation of the MIB objects in the two MIB
modules ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB is presented.
A UML diagram representation of the MIB objects in the two MIB +-----------------------+
modules ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB is presented. | Meter Capabilities |
| --------------------- |
| eoMeterCapability |
+-----------------------+
+-----------------------+ +-----------------------+
| Meter Capabilities | |---> | Energy Object ID (*) |
| --------------------- | | | --------------------- |
| eoMeterCapability | | | 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 |
+----------------------------------+
+-----------------------+ Figure 1:UML diagram for energyObjectMib
|---> | Energy Object ID (*) |
| | --------------------- |
| | 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 |
| | eoEnergyParametersStatus |
| +----------------------------------+
|
| +----------------------------------+
|---- | Energy Table |
| -------------------------------- |
| eoEnergyCollectionStartTime |
| eoEnergyConsumed |
| eoEnergyProvided |
| eoEnergyStored |
| eoEnergyUnitMultiplier |
| eoEnergyAccuracy |
| eoEnergyMaxConsumed |
| eoEnergyMaxProduced |
| eoDiscontinuityTime |
+----------------------------------+
Figure 1:UML diagram for energyObjectMib (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
(*) 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 |
+----------------------------------------------+
+-----------------------+ Figure 2: UML diagram for the POWER-ATTRIBUTES-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 |
+----------------------------------------------+
Figure 2: UML diagram for the POWER-ATTRIBUTES-MIB (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
(*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB 5.2. Energy Object Identity
5.2. Energy Object Identity The Energy Object identity information is specified in the
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].
The Energy Object identity information is specified in the 5.3. Power State
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 An Energy Object may have energy conservation modes called Power
States. Between the ON and OFF states of a device, there can be
several intermediate energy saving modes. Those energy saving
modes are called Power States.
An Energy Object may have energy conservation modes called Power Power States, which represent universal states of power
States. Between the ON and OFF states of a device, there can be management of an Energy Object, are specified by the
several intermediate energy saving modes. Those energy saving eoPowerState MIB object. The actual Power State is specified by
modes are called Power States. the eoPowerOperState MIB object, while the eoPowerAdminState MIB
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.
Power States, which represent universal states of power The MIB objects eoPowerOperState, eoPowerAdminState , and
management of an Energy Object, are specified by the eoPowerStateEnterReason are contained in the eoPowerTable MIB
eoPowerState MIB object. The actual Power State is specified by table.
the eoPowerOperState MIB object, while the eoPowerAdminState MIB
object specifies the Power State requested for the Energy
Object. The difference between the values of eoPowerOperState
and eoPowerAdminState indicate 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 eoPowerStateTable table enumerates the maximum power usage
eoPowerStateEnterReason are contained in the eoPowerTable MIB in watts for every single supported Power State of each Power
table. State Set supported by the Energy Object. In addition,
PowerStateTable provides 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.
The eoPowerStateTable table enumerates the maximum power usage 5.3.1. Power State Set
in watts for every single supported Power State of each Power
State Set supported by the Energy Object. In addition,
PowerStateTable provides 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.
5.3.1. Power State Set There are several standards and implementations of Power State
Sets. An Energy Object can support one or multiple Power State
Set implementations concurrently.
There are several standards and implementations of Power State There are currently three Power State Sets defined:
Sets. An Energy Object can support one or multiple Power State
Set implementations concurrently.
There are currently three Power State Sets defined: IEEE1621(256) - [IEEE1621]
DMTF(512) - [DMTF]
EMAN(768) - [EMAN-FMWK]
IEEE1621(256) - [IEEE1621] The Power State Sets are listed in [EMAN-FMWK] along with each
DMTF(512) - [DMTF] Power State within the Power Set. The Power State Sets are
EMAN(768) - [EMAN-FMWK] specified by the PowerStateSet Textual as an IANA-maintained MIB
module. The initial version of this MIB module is specified in
this document.
The Power State Sets are listed in [EMAN-FMWK] along with each 5.4. Energy Object Usage Information
Power State within the Power Set.
5.4. Energy Object Usage Information For an Energy Object, power usage is reported using eoPower.
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 an Energy Object, power usage is reported using eoPower. For example, if current power usage of an Energy Object is 3, it
The magnitude of measurement is based on the could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier eoPowerUnitMultiplier. Note that other measurements throughout
Textual Convention (TC). Power measurement magnitude should the two MIB modules in this document use the same mechanism,
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 including eoPowerStatePowerUnitMultiplier,
[IEC.62053-22] definition of unit multiplier for the SI (System eoEnergyUnitMultiplier, and oACPwrAttributesPowerUnitMultiplier.
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 In addition to knowing the usage and magnitude, it is useful to
could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of know how an eoPower measurement was obtained. An NMS can use
eoPowerUnitMultiplier. Note that other measurements throughout this to account for the accuracy and nature of the reading
the two MIB modules in this document use the same mechanism, between different implementations. eoPowerMeasurementLocal
including eoPowerStatePowerUnitMultiplier, describes whether the measurements were made at the device
eoEnergyUnitMultiplier, and itself or from a remote source. The eoPowerMeasurementCaliber
eoACPwrAttributesPowerUnitMultiplier. 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".
In addition to knowing the usage and magnitude, it is useful to The nameplate power rating of an Energy Object is specified in
know how an eoPower measurement was obtained. An NMS can use eoPowerNameplate MIB object.
this to account for the accuracy and nature of the reading
between different implementations. For this
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 5.5. Optional Power Usage Attributes
eoPowerNameplate MIB object.
5.5. Optional Power Usage Attributes The optional POWER-ATTRIBUTES-MIB module can be implemented to
further describe power usage attributes measurement. The POWER-
ATTRIBUTES-MIB module is aligned with IEC 61850 7-2 standard to
describe AC measurements.
The optional POWER-ATTRIBUTES-MIB module can be implemented to The POWER-ATTRIBUTES-MIB module contains a primary table,
further describe power usage attributes measurement. The POWER- eoACPwrAttributesTable, that defines power attributes
ATTRIBUTES-MIB module is aligned with IEC 61850 7-2 standard to measurements for supported entPhysicalIndex entities, as a
describe AC measurements. 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), voltage, frequency, power accuracy, total
active/reactive power/apparent power, amperage, and voltage.
The POWER-ATTRIBUTES-MIB module contains a primary table, In case of 3-phase power, an additional table is populated with
eoACPwrAttributesTable, that defines power attributes Power Attributes measurements per phase (hence, double indexed
measurements for supported entPhysicalIndex entities, as a by the entPhysicalIndex and a phase index). This table,
sparse extension of the eoPowerTable (with entPhysicalIndex as describes attributes specific to either WYE or DEL
primary index). This eoACPwrAttributesTable table contains such configurations.
information as the configuration (single phase, DEL 3 phases,
WYE 3 phases), voltage, frequency, power accuracy, total
active/reactive power/apparent power, amperage, and voltage.
In case of 3-phase power, an additional table is populated with In a DEL configuration, the eoACPwrAttributesDelPhaseTable
Power Attributes measurements per phase (hence, double indexed describes the phase-to-phase power attributes measurements,
by the entPhysicalIndex and a phase index). This table, i.e., voltage. In a DEL configuration, the current is equal in
describes attributes specific to either WYE or DEL all three phases.
configurations.
In a DEL configuration, the eoACPwrAttributesDelPhaseTable In a WYE configuration, the eoACPwrAttributesWyePhaseTable
describes the phase-to-phase power attributes measurements, describes the phase-to-neutral power attributes measurements,
i.e., voltage. In a DEL configuration, the current is equal in i.e., voltage, current, active/reactive/apparent power, and
all three phases. power factor.
In a WYE configuration, the eoACPwrAttributesWyePhaseTable 5.6. Optional Energy Measurement
describes the phase-to-neutral power attributes measurements,
i.e., voltage, current, active/reactive/apparent power, and
power factor.
5.6. Optional Energy Measurement It is only relevant to measure energy and demand when there are
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.
It is only relevant to measure energy and demand when there are Two tables are introduced to characterize energy measurement of
actual power measurements obtained from measurement hardware. If an Energy Object: eoEnergyTable and eoEnergyParametersTable.
the eoPowerMeasurementCaliber MIB object has values of Both energy and demand information can be represented via the
unavailable, unknown, estimated, or presumed, then the energy eoEnergyTable. Demand information can be represented.
and demand values are not useful. 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.
Two tables are introduced to characterize energy measurement of There are three eoEnergyParametersIntervalMode types used for
an Energy Object: eoEnergyTable and eoEnergyParametersTable. energy measurement collection: period, sliding, and total. The
Both energy and demand information can be represented via the choices of the three different modes of collection are based on
eoEnergyTable. Energy information will be an accumulation with IEC standard 61850-7-4. Note that multiple
no interval. Demand information can be represented. eoEnergyParametersIntervalMode types MAY be configured
The eoEnergyParametersTable consists of the parameters defining simultaneously. It is important to note that for a given Energy
eoEnergyParametersIndex - an index of that specifies the setting Object, multiple modes (periodic, total, sliding window) of
for collection of energy measurements for an Energy Object, energy measurement collection can be configured with the use of
eoEnergyObjectIndex - linked to the entPhysicalIndex of the eoEnergyParametersIndex. However, simultaneous measurement in
Energy Object, the duration of measurement intervals in seconds, multiple modes for a given Energy Object depends on the Energy
(eoEnergyParametersIntervalLength), the number of successive Object capability.
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 These three eoEnergyParametersIntervalMode types are illustrated
energy measurement collection: period, sliding, and total. The by the following three figures, for which:
choices of the three different modes of collection are based on
IEC standard 61850-7-4. Note that multiple
eoEnergyParametersIntervalMode types MAY be configured
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 - The horizontal axis represents the current time, with the
by the following three figures, for which: symbol <--- L ---> expressing the
eoEnergyParametersIntervalLength, and the
eoEnergyCollectionStartTime is represented by S1, S2, S3, S4,
..., Sx where x is the value of
eoEnergyParametersIntervalNumber.
- The horizontal axis represents the current time, with the - The vertical axis represents the time interval of sampling and
symbol <--- L ---> expressing the the value of eoEnergyConsumed can be obtained at the end of the
eoEnergyParametersIntervalLength, and the sampling period. The symbol =========== denotes the duration of
eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, the sampling period.
..., Sx where x is the value of
eoEnergyParametersIntervalNumber.
- The vertical axis represents the time interval of sampling and | | | =========== |
the value of eoEnergyConsumed can be obtained at the end of the |============ | | |
sampling period. The symbol =========== denotes the duration of | | | |
the sampling period. | |============ | |
| | | |
| <--- L ---> | <--- L ---> | <--- L ---> |
| | | |
S1 S2 S3 S4
| | | =========== | Figure 3 : Period eoEnergyParametersIntervalMode
|============ | | |
| | | |
| |============ | |
| | | |
| <--- L ---> | <--- L ---> | <--- L ---> |
| | | |
S1 S2 S3 S4
Figure 3 : Period eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'period' specifies non- A eoEnergyParametersIntervalMode type of 'period' specifies non-
overlapping periodic measurements. Therefore, the next overlapping periodic measurements. Therefore, the next
eoEnergyCollectionStartTime is equal to the previous eoEnergyCollectionStartTime is equal to the previous
eoEnergyCollectionStartTime plus eoEnergyCollectionStartTime plus
eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ...
|============ | |============ |
| | | |
| <--- L ---> | | <--- L ---> |
| | | |
| |============ | | |============ |
| | | | | |
| | <--- L ---> | | | <--- L ---> |
| | | | | |
| | |============ | | | |============ |
| | | | | | | |
| | | <--- L ---> | | | | <--- L ---> |
| | | | | | | |
| | | |============ | | | | |============ |
| | | | | | | | | |
| | | | <--- L ---> | | | | | <--- L ---> |
S1 | | | | S1 | | | |
| | | | | | | |
| | | | | | | |
S2 | | | S2 | | |
| | | | | |
| | | | | |
S3 | | S3 | |
| | | |
| | | |
S4 S4
Figure 4 : Sliding eoEnergyParametersIntervalMode Figure 4 : Sliding eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'sliding' specifies A eoEnergyParametersIntervalMode type of 'sliding' specifies
overlapping periodic measurements. overlapping periodic measurements.
| | | |
|========================= | |========================= |
| | | |
| | | |
| | | |
| <--- Total length ---> | | <--- Total length ---> |
| | | |
S1 S1
Figure 5 : Total eoEnergyParametersIntervalMode Figure 5 : Total eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'total' specifies a A eoEnergyParametersIntervalMode type of 'total' specifies a
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy The eoEnergyParametersStatus is used to start and stop energy
usage logging. The status of this variable is "active" when all usage logging. The status of this variable is "active" when all
the objects in eoEnergyParametersTable are appropriate which in the objects in eoEnergyParametersTable are appropriate which in
turn indicates if eoEnergyTable entries exist or not. turn indicates if eoEnergyTable entries exist or not. Finally,
the eoEnergyParametersStorageType variable indicates the storage
type for this row, i.e. whether the persistence is maintained
across a device reload.
The eoEnergyTable consists of energy measurements in The eoEnergyTable consists of energy measurements in
eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units
of the measured energy eoEnergyUnitMultiplier, and the maximum of the measured energy eoEnergyUnitMultiplier, and the maximum
observed energy within a window eoEnergyMaxConsumed, observed energy within a window eoEnergyMaxConsumed,
eoEnergyMaxProduced. eoEnergyMaxProduced.
Measurements of the total energy consumed by an Energy Object Measurements of the total energy consumed by an Energy Object
may suffer from interruptions in the continuous measurement of may suffer from interruptions in the continuous measurement of
energy consumption. In order to indicate such interruptions, energy consumption. In order to indicate such interruptions,
the object eoEnergyDiscontinuityTime is provided for indicating the object eoEnergyDiscontinuityTime is provided for indicating
the time of the last interruption of total energy measurement. the time of the last interruption of total energy measurement.
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418]
when the device was reset. when the device was reset.
The following example illustrates the eoEnergyTable and The following example illustrates the eoEnergyTable and
eoEnergyParametersTable: eoEnergyParametersTable:
First, in order to estimate energy, a time interval to sample First, in order to estimate energy, a time interval to sample
energy should be specified, i.e., energy should be specified, i.e.,
eoEnergyParametersIntervalLength can be set to "900 seconds" or eoEnergyParametersIntervalLength can be set to "900 seconds" or
15 minutes and the number of consecutive intervals over which 15 minutes and the number of consecutive intervals over which
the maximum energy is calculated the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active to indicate that the eoEnergyParametersStatus is set to active to indicate that the
Energy Object should start monitoring the usage per the Energy Object should start monitoring the usage per the
eoEnergyTable. eoEnergyTable.
The indices for the eoEnergyTable are eoEnergyParametersIndex, The indices for the eoEnergyTable are eoEnergyParametersIndex,
which identifies the index for the setting of energy measurement which identifies the index for the setting of energy measurement
collection Energy Object, and eoEnergyCollectionStartTime, which collection Energy Object, and eoEnergyCollectionStartTime, which
denotes the start time of the energy measurement interval based denotes the start time of the energy measurement interval based
on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
measured energy consumption over the time interval specified measured energy consumption over the time interval specified
(eoEnergyParametersIntervalLength) based on the Energy Object (eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (eoEnergyParametersSampleRate). While internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the eoEnergyParametersIntervalLength and choosing the values for the eoEnergyParametersIntervalLength and
eoEnergyParametersSampleRate, it is recommended to take into eoEnergyParametersSampleRate, it is recommended to take into
consideration either the network element resources adequate to consideration either the network element resources adequate to
process and store the sample values, and the mechanism used to process and store the sample values, and the mechanism used to
calculate the eoEnergyConsumed. The units are derived from calculate the eoEnergyConsumed. The units are derived from
eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
"100" with eoEnergyUnitMultiplier equal to 0, the measured "100" with eoEnergyUnitMultiplier equal to 0, the measured
energy consumption of the Energy Object is 100 watt-hours. The energy consumption of the Energy Object is 100 watt-hours. The
eoEnergyMaxConsumed is the maximum energy observed and that can eoEnergyMaxConsumed is the maximum energy observed and that can
be "150 watt-hours". be "150 watt-hours".
The eoEnergyTable has a buffer to retain a certain number of The eoEnergyTable has a buffer to retain a certain number of
intervals, as defined by eoEnergyParametersIntervalNumber. intervals, as defined by eoEnergyParametersIntervalNumber.
If the default value of "10" is kept, then the eoEnergyTable If the default value of "10" is kept, then the eoEnergyTable
contains 10 energy measurements, including the maximum. contains 10 energy measurements, including the maximum.
Here is a brief explanation of how the maximum energy can be Here is a brief explanation of how the maximum energy can be
calculated. The first observed energy measurement value is calculated. The first observed energy measurement value is
taken to be the initial maximum. With each subsequent taken to be the initial maximum. With each subsequent
measurement, based on numerical comparison, maximum energy may measurement, based on numerical comparison, maximum energy may
be updated. The maximum value is retained as long as the be updated. The maximum value is retained as long as the
measurements are taking place. Based on periodic polling of measurements are taking place. Based on periodic polling of
this table, an NMS could compute the maximum over a longer this table, an NMS could compute the maximum over a longer
period, e.g., a month, 3 months, or a year. period, e.g., a month, 3 months, or a year.
5.7. Fault Management 5.7. Fault Management
[RFC6988] specifies requirements about Power States such as "the [RFC6988] specifies requirements about Power States such as "the
current Power State" , "the time of the last state change", "the current Power State" , "the time of the last state change", "the
total time spent in each state", "the number of transitions to total time spent in each state", "the number of transitions to
each state" etc. Some of these requirements are fulfilled each state" etc. Some of these requirements are fulfilled
explicitly by MIB objects such as eoPowerOperState, explicitly by MIB objects such as eoPowerOperState,
eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the
other requirements are met via the SNMP NOTIFICATION mechanism. other requirements are met via the SNMP NOTIFICATION mechanism.
eoPowerStateChange SNMP notification which is generated when the eoPowerStateChange SNMP notification which is generated when the
value of oPowerStateIndex, eoPowerOperState, or value of oPowerStateIndex, eoPowerOperState, or
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
It is probable that most Energy Objects will require the It is probable that most Energy Objects will require the
implementation of the ENERGY-OBJECT-CONTEXT-MIB [EMAN-AWARE-MIB] implementation of the ENERGY-OBJECT-CONTEXT-MIB [EMAN-AWARE-MIB]
as a prerequisite for this MIB module. In such a case, as a prerequisite for this MIB module. In such a case,
eoPowerTable of the EMAN-ENERGY-OBJECT-MIB is cross-referenced eoPowerTable of the EMAN-ENERGY-OBJECT-MIB is cross-referenced
with the eoTable of ENERGY-OBJECT-CONTEXT-MIB via with the eoTable of ENERGY-OBJECT-CONTEXT-MIB via
entPhysicalIndex. Every Energy Object MUST implement entPhysicalIndex. Every Energy Object MUST implement
entPhysicalIndex, entPhysicalClass, entPhysicalName and entPhysicalIndex, entPhysicalClass, entPhysicalName and
entPhysicalUUID from the ENTITY-MIB [RFC6933]. As the primary entPhysicalUUID from the ENTITY-MIB [RFC6933]. As the primary
index for the Energy Object, entPhysicalIndex is used: It index for the Energy Object, entPhysicalIndex is used: It
characterizes the Energy Object in the ENERGY-OBJECT-MIB and the characterizes the Energy Object in the ENERGY-OBJECT-MIB and the
POWER-ATTRIBUTES-MIB MIB modules (this document). POWER-ATTRIBUTES-MIB MIB modules (this document).
The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module
[EMAN-AWARE-MIB], if available, in order to discover all the [EMAN-AWARE-MIB], if available, in order to discover all the
Energy Objects and the relationships between those Energy Energy Objects and the relationships between those Energy
Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the
Energy Objects are indexed by the entPhysicalIndex. Energy Objects are indexed by the entPhysicalIndex.
From there, the NMS must poll the eoPowerStateTable (specified From there, the NMS must poll the eoPowerStateTable (specified
in the ENERGY-OBJECT-MIB module in this document), which in the ENERGY-OBJECT-MIB module in this document), which
enumerates, amongst other things, the maximum power usage. As enumerates, amongst other things, the maximum power usage. As
the entries in eoPowerStateTable table are indexed by the the entries in eoPowerStateTable table are indexed by the
Energy Object ( entPhysicalIndex) and by the Power State Set Energy Object ( entPhysicalIndex) and by the Power State Set
(eoPowerStateIndex), the maximum power usage is discovered per (eoPowerStateIndex), the maximum power usage is discovered per
Energy Object, and the power usage per Power State of the Power Energy Object, and the power usage per Power State of the Power
State Set. In other words, reading the eoPowerStateTable allows State Set. In other words, reading the eoPowerStateTable allows
the discovery of each Power State within every Power State Set the discovery of each Power State within every Power State Set
supported by the Energy Object. supported by the Energy Object.
If the Energy Object is an Aggregator, the MIB module would be The MIB module may be populated with the Energy Object
populated with the Energy Object relationship information, which relationship information, which have its own Energy Object index
have its own Energy Object index value (entPhysicalIndex). value (entPhysicalIndex). However, the Energy Object
However, the Energy Object relationship must be discovered via relationship must be discovered via the ENERGY-OBJECT-CONTEXT-
the ENERGY-OBJECT-CONTEXT-MIB module. MIB module.
Finally, the NMS can monitor the power attributes with the Finally, the NMS can monitor the power attributes with the
POWER-ATTRIBUTES-MIB MIB module, which reuses the POWER-ATTRIBUTES-MIB MIB module, which reuses the
entPhysicalIndex to index the Energy Object. entPhysicalIndex to index the Energy Object.
7. Link with the other IETF MIBs 7. Link with the other IETF MIBs
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
RFC 6933 [RFC6933] defines the ENTITY-MIB module that lists the RFC 6933 [RFC6933] defines the ENTITY-MIB module that lists the
physical entities of a networking device (router, switch, etc.) physical entities of a networking device (router, switch, etc.)
and those physical entities indexed by entPhysicalIndex. From and those physical entities indexed by entPhysicalIndex. From
an energy-management standpoint, the physical entities that an energy-management standpoint, the physical entities that
consume or produce energy are of interest. consume or produce energy are of interest.
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that
provides a standardized way of obtaining information (current provides a standardized way of obtaining information (current
value of the sensor, operational status of the sensor, and the value of the sensor, operational status of the sensor, and the
data units precision) from sensors embedded in networking data units precision) from sensors embedded in networking
devices. Sensors are associated with each index of devices. Sensors are associated with each index of
entPhysicalIndex of the ENTITY-MIB [RFC6933]. While the focus entPhysicalIndex of the ENTITY-MIB [RFC6933]. While the focus
of the Power and Energy Monitoring MIB is on measurement of of the Power and Energy Monitoring MIB is on measurement of
power usage of networking equipment indexed by the ENTITY-MIB, power usage of networking equipment indexed by the ENTITY-MIB,
this MIB supports a customized power scale for power measurement this MIB supports a customized power scale for power measurement
and different Power States of networking equipment, and and different Power States of networking equipment, and
functionality to configure the Power States. functionality to configure the Power States.
The Energy Objects are modeled by the entPhysicalIndex through The Energy Objects are modeled by the entPhysicalIndex through
the entPhysicalEntity MIB object specified in the eoTable in the the entPhysicalEntity MIB object specified in the eoTable in the
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB]. ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB].
The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x
accuracy classes required for electricity (e.g., 1%, 2%, 0.5% accuracy classes required for electricity (e.g., 1%, 2%, 0.5%
accuracy classes). Indeed, entPhySensorPrecision [RFC3433] accuracy classes). Indeed, entPhySensorPrecision [RFC3433]
represents "The number of decimal places of precision in fixed- represents "The number of decimal places of precision in fixed-
point sensor values returned by the associated entPhySensorValue point sensor values returned by the associated entPhySensorValue
object". The ANSI and IEC Standards are used for power object". The ANSI and IEC Standards are used for power
measurement and these standards require that we use an accuracy measurement and these standards require that we use an accuracy
class, not the scientific-number precision model specified in class, not the scientific-number precision model specified in
RFC3433. The eoPowerAccuracy MIB object models this accuracy. RFC3433. The eoPowerAccuracy MIB object models this accuracy.
Note that eoPowerUnitMultipler represents the scale factor per Note that eoPowerUnitMultipler represents the scale factor per
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the (compared to entPhySensorScale), with the mantissa and the
exponent values X * 10 ^ Y. exponent values X * 10 ^ Y.
Power measurements specifying the qualifier 'UNITS' for each Power measurements specifying the qualifier 'UNITS' for each
measured value in watts are used in the LLDP-EXT-MED-MIB, POE measured value in watts are used in the LLDP-EXT-MED-MIB, POE
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier
is used for the power measurement values. is used for the power measurement values.
One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are
implemented for all Energy Objects that need to be monitored. A implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, which can typical example is a converged building gateway, which can
monitor other devices in a building and provides a proxy between monitor other devices in a building and provides a proxy between
SNMP and a protocol like BACNET. Another example is the home SNMP and a protocol like BACNET. Another example is the home
energy controller. In such cases, the eoPhysicalEntity value energy controller. In such cases, the eoPhysicalEntity value
contains the zero value, using the PhysicalIndexOrZero textual contains the zero value, using the PhysicalIndexOrZero textual
convention. convention.
The eoPower is similar to entPhySensorValue [RFC3433] and the The eoPower is similar to entPhySensorValue [RFC3433] and the
eoPowerUnitMultipler is similar to entPhySensorScale. eoPowerUnitMultipler is similar to entPhySensorScale.
7.2. Link with the ENTITY-STATE MIB 7.2. Link with the ENTITY-STATE MIB
For each entity in the ENTITY-MIB [RFC6933], the ENTITY-STATE For each entity in the ENTITY-MIB [RFC6933], the ENTITY-STATE
MIB [RFC4268] specifies the operational states (entStateOper: MIB [RFC4268] specifies the operational states (entStateOper:
unknown, enabled, disabled, testing), the alarm (entStateAlarm: unknown, enabled, disabled, testing), the alarm (entStateAlarm:
unknown, underRepair, critical, major, minor, warning, unknown, underRepair, critical, major, minor, warning,
indeterminate) and the possible values of standby states indeterminate) and the possible values of standby states
(entStateStandby: unknown, hotStandby, coldStandby, (entStateStandby: unknown, hotStandby, coldStandby,
providingService). providingService).
From a power monitoring point of view, in contrast to the entity From a power monitoring point of view, in contrast to the entity
operational states of entities, Power States are required, as operational states of entities, Power States are required, as
proposed in the Power and Energy Monitoring MIB module. Those proposed in the Power and Energy Monitoring MIB module. Those
Power States can be mapped to the different operational states Power States can be mapped to the different operational states
in the ENTITY-STATE MIB, if a formal mapping is required. For in the ENTITY-STATE MIB, if a formal mapping is required. For
example, the entStateStandby "unknown", "hotStandby", example, the entStateStandby "unknown", "hotStandby",
"coldStandby", states could map to the Power State "unknown", "coldStandby", states could map to the Power State "unknown",
"ready", "standby", respectively, while the entStateStandby "ready", "standby", respectively, while the entStateStandby
"providingService" could map to any "low" to "high" Power State. "providingService" could map to any "low" to "high" Power State.
7.3. Link with the POWER-OVER-ETHERNET MIB 7.3. Link with the POWER-OVER-ETHERNET MIB
Power-over-Ethernet MIB [RFC3621] provides an energy monitoring Power-over-Ethernet MIB [RFC3621] provides an energy monitoring
and configuration framework for power over Ethernet devices. and configuration framework for power over Ethernet devices.
RFC 3621 defines a port group entity on a switch for power RFC 3621 defines a port group entity on a switch for power
monitoring and management policy and does not use the monitoring and management policy and does not use the
entPhysicalIndex index. Indeed, pethMainPseConsumptionPower is entPhysicalIndex index. Indeed, pethMainPseConsumptionPower is
indexed by the pethMainPseGroupIndex, which has no mapping with indexed by the pethMainPseGroupIndex, which has no mapping with
the entPhysicalIndex. the entPhysicalIndex.
If the Power-over-Ethernet MIB [RFC3621] is supported, the If the Power-over-Ethernet MIB [RFC3621] is supported, the
Energy Object eoethPortIndex and eoethPortGrpIndex contain the Energy Object eoethPortIndex and eoethPortGrpIndex contain the
pethPsePortIndex and pethPsePortGroupIndex, respectively. pethPsePortIndex and pethPsePortGroupIndex, respectively.
However, one cannot assume that the Power-over-Ethernet MIB is However, one cannot assume that the Power-over-Ethernet MIB is
implemented for most or all Energy Objects. In such cases, the implemented for most or all Energy Objects. In such cases, the
eoethPortIndex and eoethPortGrpIndex values contain the zero eoethPortIndex and eoethPortGrpIndex values contain the zero
value, via the new PethPsePortIndexOrZero and textual value, via the new PethPsePortIndexOrZero and textual
PethPsePortGroupIndexOrZero conventions. PethPsePortGroupIndexOrZero conventions.
In either case, the entPhysicalIndex MIB object is used as the In either case, the entPhysicalIndex MIB object is used as the
unique Energy Object index. unique Energy Object index.
Note that, even though the Power-over-Ethernet MIB [RFC3621] was Note that, even though the Power-over-Ethernet MIB [RFC3621] was
created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse
the precision notion from the ENTITY-SENSOR MIB, i.e., the the precision notion from the ENTITY-SENSOR MIB, i.e., the
entPhySensorPrecision MIB object. entPhySensorPrecision MIB object.
7.4. Link with the UPS MIB 7.4. Link with the UPS MIB
To protect against unexpected power disruption, data centers and To protect against unexpected power disruption, data centers and
buildings make use of Uninterruptible Power Supplies (UPS). To buildings make use of Uninterruptible Power Supplies (UPS). To
protect critical assets, a UPS can be restricted to a particular protect critical assets, a UPS can be restricted to a particular
subset or domain of the network. UPS usage typically lasts only subset or domain of the network. UPS usage typically lasts only
for a finite period of time, until normal power supply is for a finite period of time, until normal power supply is
restored. Planning is required to decide on the capacity of the restored. Planning is required to decide on the capacity of the
UPS based on output power and duration of probable power outage. UPS based on output power and duration of probable power outage.
To properly provision UPS power in a data center or building, it To properly provision UPS power in a data center or building, it
is important to first understand the total demand required to is important to first understand the total demand required to
support all the entities in the site. This demand can be support all the entities in the site. This demand can be
assessed and monitored via the Power and Energy Monitoring MIB. assessed and monitored via the Power and Energy Monitoring MIB.
UPS MIB [RFC1628] provides information on the state of the UPS UPS MIB [RFC1628] provides information on the state of the UPS
network. Implementation of the UPS MIB is useful at the network. Implementation of the UPS MIB is useful at the
aggregate level of a data center or a building. The MIB module aggregate level of a data center or a building. The MIB module
contains several groups of variables: contains several groups of variables:
- upsIdent: Identifies the UPS entity (name, model, etc.). - upsIdent: Identifies the UPS entity (name, model, etc.).
- upsBattery group: Indicates the battery state - upsBattery group: Indicates the battery state
(upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.)
- upsInput group: Characterizes the input load to the UPS - upsInput group: Characterizes the input load to the UPS
(number of input lines, voltage, current, etc.). (number of input lines, voltage, current, etc.).
- upsOutput: Characterizes the output from the UPS (number of - upsOutput: Characterizes the output from the UPS (number of
output lines, voltage, current, etc.) output lines, voltage, current, etc.)
- upsAlarms: Indicates the various alarm events. - upsAlarms: Indicates the various alarm events.
The measurement of power in the UPS MIB is in volts, amperes and The measurement of power in the UPS MIB is in volts, amperes and
watts. The units of power measurement are RMS volts and RMS watts. The units of power measurement are RMS volts and RMS
Amperes. They are not based on the EntitySensorDataScale and Amperes. They are not based on the EntitySensorDataScale and
EntitySensorDataPrecision of ENTITY-SENSOR-MIB. EntitySensorDataPrecision of ENTITY-SENSOR-MIB.
Both the Power and Energy Monitoring MIB and the UPS MIB may be Both the Power and Energy Monitoring MIB and the UPS MIB may be
implemented on the same UPS SNMP agent, without conflict. In implemented on the same UPS SNMP agent, without conflict. In
this case, the UPS device itself is the Energy Object and any this case, the UPS device itself is the Energy Object and any of
of the UPS meters or submeters are the Energy Objects with a the UPS meters or submeters are the Energy Objects with a
possible relationship as defined in [EMAN-FMWK]. possible relationship as defined in [EMAN-FMWK].
7.5. Link with the LLDP and LLDP-MED MIBs 7.5. Link with the LLDP and LLDP-MED MIBs
The LLDP Protocol is a Data Link Layer protocol used by network The LLDP Protocol is a Data Link Layer protocol used by network
devices to advertise their identities, capabilities, and devices to advertise their identities, capabilities, and
interconnections on a LAN network. interconnections on a LAN network.
The Media Endpoint Discovery is an enhancement of LLDP, known as The Media Endpoint Discovery is an enhancement of LLDP, known as
LLDP-MED. The LLDP-MED enhancements specifically address voice LLDP-MED. The LLDP-MED enhancements specifically address voice
applications. LLDP-MED covers 6 basic areas: capability applications. LLDP-MED covers 6 basic areas: capability
discovery, LAN speed and duplex discovery, network policy discovery, LAN speed and duplex discovery, network policy
discovery, location identification discovery, inventory discovery, location identification discovery, inventory
discovery, and power discovery. discovery, and power discovery.
Of particular interest to the current MIB module is the power Of particular interest to the current MIB module is the power
discovery, which allows the endpoint device (such as a PoE discovery, which allows the endpoint device (such as a PoE
phone) to convey power requirements to the switch. In power phone) to convey power requirements to the switch. In power
discovery, LLDP-MED has four Type Length Values (TLVs): power discovery, LLDP-MED has four Type Length Values (TLVs): power
type, power source, power priority and power value. type, power source, power priority and power value.
Respectively, those TLVs provide information related to the type Respectively, those TLVs provide information related to the type
of power (power sourcing entity versus powered device), how the of power (power sourcing entity versus powered device), how the
device is powered (from the line, from a backup source, from device is powered (from the line, from a backup source, from
external power source, etc.), the power priority (how important external power source, etc.), the power priority (how important
is it that this device has power?), and how much power the is it that this device has power?), and how much power the
device needs. device needs.
The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB]
actually comes from the Power-over-Ethernet MIB [RFC3621]. If actually comes from the Power-over-Ethernet MIB [RFC3621]. If
the Power-over-Ethernet MIB [RFC3621] is supported, the exact the Power-over-Ethernet MIB [RFC3621] is supported, the exact
value from the pethPsePortPowerPriority [RFC3621] is copied over value from the pethPsePortPowerPriority [RFC3621] is copied over
into the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; into the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB];
otherwise the value in lldpXMedRemXPoEPDPowerPriority is otherwise the value in lldpXMedRemXPoEPDPowerPriority is
"unknown". From the Power and Energy Monitoring MIB, it is "unknown". From the Power and Energy Monitoring MIB, it is
possible to identify the pethPsePortPowerPriority [RFC3621], via possible to identify the pethPsePortPowerPriority [RFC3621], via
the eoethPortIndex and eoethPortGrpIndex. the eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
eoPowerMeasurementLocal in indicating if the power for an eoPowerMeasurementLocal in indicating if the power for an
attached device is local or from a remote device. If the LLDP- attached device is local or from a remote device. If the LLDP-
MED MIB is supported, the following mapping can be applied to MED MIB is supported, the following mapping can be applied to
the eoPowerMeasurementLocal: lldpXMedLocXPoEPDPowerSource the eoPowerMeasurementLocal: lldpXMedLocXPoEPDPowerSource
fromPSE(2) and local(3) can be mapped to false and true, fromPSE(2) and local(3) can be mapped to false and true,
respectively. respectively.
8. Structure of the MIB 8. Structure of the MIB
The primary MIB object in this MIB module is the The primary MIB object in the energyObjectMib MIB module is the
energyObjectMibObjects root. The eoPowerTable table of energyObjectMibObjects root. The eoPowerTable table of
energyObjectMibObjects describes the power measurement energyObjectMibObjects describes the power measurement
attributes of an Energy Object entity. The identity of a device attributes of an Energy Object entity. The identity of a device
in terms of uniquely identification of the Energy Object and its in terms of uniquely identification of the Energy Object and its
relationship to other entities in the network are addressed in relationship to other entities in the network are addressed in
[EMAN-AWARE-MIB]. [EMAN-AWARE-MIB].
Logically, this MIB module is a sparse extension of the Logically, this MIB module is a sparse extension of the
ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the
following requirements which are applied to [EMAN-AWARE-MIB] are following requirements which are applied to [EMAN-AWARE-MIB] are
also applicable. As a requirement for this MIB module, [EMAN- also applicable. As a requirement for this MIB module, [EMAN-
AWARE-MIB] SHOULD be implemented and as Module Compliance of AWARE-MIB] SHOULD be implemented and as Module Compliance of
ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance MUST ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance MUST
be supported which requires 4 MIB objects: entPhysicalIndex, be supported which requires 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and entPhysicalUUID MUST be entPhysicalClass, entPhysicalName and entPhysicalUUID MUST be
implemented. implemented.
eoMeterCapabilitiesTable is useful to enable applications to eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading that are supported by the local management system. By reading
the value of this object, it is possible for applications to the value of this object, it is possible for applications to
know which tables contain the information and are usable without know which tables contain the information and are usable without
walking through the table and querying every element which walking through the table and querying every element which
involves a trial-and-error process. involves a trial-and-error process.
The power measurement of an Energy Object contains information The power measurement of an Energy Object contains information
describing its power usage (eoPower) and its current Power State describing its power usage (eoPower) and its current Power State
(eoPowerOperState). In addition to power usage, additional (eoPowerOperState). In addition to power usage, additional
information describing the units of measurement information describing the units of measurement
(eoPowerAccuracy, eoPowerUnitMultiplier), how power usage (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage
measurement was obtained (eoPowerMeasurementCaliber), the measurement was obtained (eoPowerMeasurementCaliber), the
source of power measurement (eoPowerMeasurementLocal) and the source of power measurement (eoPowerMeasurementLocal) and the
type of power (eoPowerCurrentType) are described. type of power (eoPowerCurrentType) are described.
An Energy Object may contain an optional eoPowerAttributes table An Energy Object may contain an optional eoEnergyTable to
that describes the electrical characteristics associated with describe energy measurement information over time.
the current Power State and usage.
An Energy Object may contain an optional eoEnergyTable to An Energy Object may contain an optional eoACPwrAttributesTable
describe energy measurement information over time. table (specified in the POWER-ATTRIBUTES-MIB module) that
describes the electrical characteristics associated with the
current Power State and usage.
An Energy Object may also contain optional battery information An Energy Object may also contain optional battery information
associated with this entity. associated with this entity.
9. MIB Definitions 9. MIB Definitions
-- ************************************************************ 9.1. The IANAPowerStateSet-MIB MIB Module
--
--
-- This MIB is used to monitor power usage of network
-- devices
--
-- *************************************************************
ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN -- ************************************************************
--
--
-- This MIB, maintained by IANA, contains a single Textual
-- Convention: PowerStateSet
--
-- ************************************************************
IMPORTS IANAPowerStateSet-MIB DEFINITIONS ::= BEGIN
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
mib-2,
Integer32, Counter32, TimeTicks
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeInterval, IMPORTS
TimeStamp, TruthValue MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC;
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF
OwnerString
FROM RMON-MIB
entPhysicalIndex
FROM ENTITY-MIB
IANAPowerStateSet
FROM IANA-POWERSTATE-SET-MIB;
energyObjectMib MODULE-IDENTITY ianaPowerStateSet MODULE-IDENTITY
LAST-UPDATED "201402140000Z" -- 14 Feb 2014 LAST-UPDATED "201406070000Z" -- 07 June 2014
ORGANIZATION "IANA"
CONTACT-INFO "
Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1-310-823-9358
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines the PowerStateSet Textual
Convention, which specifies the Power State Sets and
Power State Set Values an Energy Object supports
ORGANIZATION "IETF EMAN Working Group" Copyright (C) The IETF Trust (2014).
CONTACT-INFO The initial version of this MIB module was published in
"WG charter: RFC YYY; for full legal notices see the RFC itself.
http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Supplementary information may be available at
General Discussion: eman@ietf.org http://www.ietf.org/copyrights/ianamib.html"
To Subscribe: -- revision history
https://www.ietf.org/mailman/listinfo/eman
Archive: REVISION "201406070000Z" -- 07 June 2014
http://www.ietf.org/mail-archive/web/eman DESCRIPTION
"Initial version of this MIB module, as published as RFC
XXXX."
Editors: -- RFC Editor, please replace YYY with the IANA allocation
Mouli Chandramouli -- for this MIB module and YYY with the number of the
Cisco Systems, Inc. -- approved RFC
Sarjapur Outer Ring Road
Bangalore 560103
IN
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
Brad Schoening ::= { mib-2 xxx }
44 Rivers Edge Drive
Little Silver, NJ 07739
US
Email: brad.schoening@verizon.net
Juergen Quittek PowerStateSet ::= TEXTUAL-CONVENTION
NEC Europe Ltd. STATUS current
NEC Laboratories Europe DESCRIPTION
Network Research Division "IANAPowerState is a textual convention that describes
Kurfuersten-Anlage 36 Power State Sets and Power State Set Values an Energy
Heidelberg 69115 Object supports. IANA has created a registry of Power
DE State supported by an Energy Object and IANA shall
Phone: +49 6221 4342-115 administer the list of Power State Sets and Power
Email: quittek@neclab.eu States.
Thomas Dietz The textual convention assumes that Power States in a
NEC Europe Ltd. power state set are limited to 255 distinct values. For
NEC Laboratories Europe a Power State Set S, the named number with the value S *
Network Research Division 256 is allocated to indicate the Power State set. For a
Kurfuersten-Anlage 36 Power State X in the Power State S, the named number
69115 Heidelberg with the value S * 256 + X + 1 is allocated to represent
DE the Power State.
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise Requests for new values should be made to IANA via email
Cisco Systems, Inc. (iana&iana.org)."
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION REFERENCE
"This MIB is used to monitor power and energy in "http://www.iana.org/assignments/power-state-sets"
devices.
The tables eoMeterCapabilitiesTable and eoPowerTable SYNTAX INTEGER {
are a sparse extension of the eoTable from the other(0), -- indicates other set
ENERGY-OBJECT-CONTEXT-MIB. As a requirement unknown(255), -- unknown
[EMAN-AWARE-MIB] SHOULD be implemented.
Module Compliance of ENTITY-MIB v4 with respect to ieee1621(256), -- indicates IEEE1621 set
entity4CRCompliance MUST be supported which requires ieee1621Off(257),
implementation of 4 MIB objects: entPhysicalIndex, ieee1621Sleep(258),
entPhysicalClass, entPhysicalName and entPhysicalUUID." ieee1621On(259),
REVISION dmtf(512), -- indicates DMTF set
"201402140000Z" -- 14 Feb 2014 dmtfOn(513),
dmtfSleepLight(514),
dmtfSleepDeep(515),
dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
DESCRIPTION eman(1024), -- indicates EMAN set
"Initial version, published as RFC XXXX." emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
END
::= { mib-2 xxx } 9.2. The ENERGY-OBJECT-MIB MIB Module
energyObjectMibNotifs OBJECT IDENTIFIER -- ************************************************************
::= { energyObjectMib 0 } --
--
-- This MIB is used to monitor power usage of network
-- devices
--
-- *************************************************************
energyObjectMibObjects OBJECT IDENTIFIER ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN
::= { energyObjectMib 1 }
energyObjectMibConform OBJECT IDENTIFIER IMPORTS
::= { energyObjectMib 2 } MODULE-IDENTITY,
OBJECT-TYPE,
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;
-- Textual Conventions energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201406070000Z" -- 07 June 2014
IANAPowerStateSet ::= TEXTUAL-CONVENTION ORGANIZATION "IETF EMAN Working Group"
STATUS current CONTACT-INFO
DESCRIPTION "WG charter:
http://datatracker.ietf.org/wg/eman/charter/
"IANAPowerState is a textual convention that describes Mailing Lists:
Power State Sets and Power State Set Values an Energy Object General Discussion: eman@ietf.org
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 power To Subscribe:
state set are limited to 255 distinct values. For a Power https://www.ietf.org/mailman/listinfo/eman
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."
REFERENCE Archive:
"http://www.iana.org/assignments/eman http://www.ietf.org/mail-archive/web/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
SYNTAX INTEGER { Editors:
other(0), -- indicates other set Mouli Chandramouli
unknown(255), -- unknown 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
ieee1621(256), -- indicates IEEE1621 set Juergen Quittek
ieee1621On(257), NEC Europe Ltd.
ieee1621Off(258), NEC Laboratories Europe
ieee1621Sleep(259), Network Research Division
Kurfuersten-Anlage 36
Heidelberg 69115
DE
Phone: +49 6221 4342-115
Email: quittek@neclab.eu
dmtf(512), -- indicates DMTF set Thomas Dietz
dmtfOn(513), NEC Europe Ltd.
dmtfSleepLight(514), NEC Laboratories Europe
dmtfSleepDeep(515), Network Research Division
dmtfOffHard(516), Kurfuersten-Anlage 36
dmtfOffSoft(517), 69115 Heidelberg
dmtfHibernate(518), DE
dmtfPowerOffSoft(519), Phone: +49 6221 4342-128
dmtfPowerOffHard(520), Email: Thomas.Dietz@nw.neclab.eu
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set Benoit Claise
emanmechoff(1025), Cisco Systems, Inc.
emansoftoff(1026), De Kleetlaan 6a b1
emanhibernate(1027), Degem 1831
emansleep(1028), Belgium
emanstandby(1029), Phone: +32 2 704 5622
emanready(1030), Email: bclaise@cisco.com"
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
UnitMultiplier ::= TEXTUAL-CONVENTION DESCRIPTION
STATUS current "This MIB is used to monitor power and energy in
DESCRIPTION devices.
"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 The tables eoMeterCapabilitiesTable and eoPowerTable
represents 10^-3 or milliwatts." are a sparse extension of the eoTable from the
REFERENCE ENERGY-OBJECT-CONTEXT-MIB. As a requirement
"The International System of Units (SI), National [EMAN-AWARE-MIB] SHOULD be implemented.
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
}
-- Objects Module Compliance of ENTITY-MIB v4 with respect to
entity4CRCompliance MUST be supported which requires
implementation of 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and entPhysicalUUID."
eoMeterCapabilitiesTable OBJECT-TYPE REVISION "201406070000Z" -- 07 June 2014
SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry DESCRIPTION
MAX-ACCESS not-accessible "Initial version, published as RFC XXXX."
STATUS current
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 ::= { mib-2 yyy }
SYNTAX EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the metering capability of an Energy
Object."
INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 }
EoMeterCapabilitiesEntry ::= SEQUENCE { energyObjectMibNotifs OBJECT IDENTIFIER
eoMeterCapability BITS ::= { energyObjectMib 0 }
}
eoMeterCapability OBJECT-TYPE energyObjectMibObjects OBJECT IDENTIFIER
SYNTAX BITS { ::= { energyObjectMib 1 }
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 energyObjectMibConform OBJECT IDENTIFIER
SYNTAX SEQUENCE OF EoPowerEntry ::= { energyObjectMib 2 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table lists Energy Objects."
::= { energyObjectMibObjects 2 }
eoPowerEntry OBJECT-TYPE -- Textual Conventions
SYNTAX EoPowerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the power usage of an Energy Object."
INDEX { entPhysicalIndex } UnitMultiplier ::= TEXTUAL-CONVENTION
::= { eoPowerTable 1 } STATUS current
DESCRIPTION
"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.
EoPowerEntry ::= SEQUENCE { For example, when used with eoPowerUnitMultiplier, -3
represents 10^-3 or milliwatts."
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
}
eoPower Integer32, -- Objects
eoPowerNameplate Integer32, eoMeterCapabilitiesTable OBJECT-TYPE
eoPowerUnitMultiplier UnitMultiplier, SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry
eoPowerAccuracy Integer32, MAX-ACCESS not-accessible
eoPowerMeasurementCaliber INTEGER, STATUS current
eoPowerCurrentType INTEGER, DESCRIPTION
eoPowerMeasurementLocal TruthValue, "This table is useful for helping applications determine
eoPowerAdminState IANAPowerStateSet, the monitoring capabilities supported by the local
eoPowerOperState IANAPowerStateSet, management agents. It is possible for applications to
eoPowerStateEnterReason OwnerString know which tables are usable without going through a
} trial-and-error process."
::= { energyObjectMibObjects 1 }
eoPower OBJECT-TYPE eoMeterCapabilitiesEntry OBJECT-TYPE
SYNTAX Integer32 SYNTAX EoMeterCapabilitiesEntry
UNITS "watts" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "An entry describes the metering capability of an Energy
"This object indicates the power measured for the Energy Object."
Object. For alternating current, this value is obtained INDEX { entPhysicalIndex }
as an average over fixed number of AC cycles. This value ::= { eoMeterCapabilitiesTable 1 }
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 specfied 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 EoMeterCapabilitiesEntry ::= SEQUENCE {
power that can be consumed at the power state specified eoMeterCapability BITS
by eoPowerState. }
The eoPowerMeasurementCaliber object specifies how the eoMeterCapability OBJECT-TYPE
usage value reported by eoPower was obtained. The eoPower SYNTAX BITS {
value must report 0 if the eoPowerMeasurementCaliber is none(0),
'unavailable'. For devices that can not measure or powermetering(1), -- power measurement
report power, this option can be used." energymetering(2), -- energy measurement
::= { eoPowerEntry 1 } 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 }
eoPowerNameplate OBJECT-TYPE eoPowerTable OBJECT-TYPE
SYNTAX Integer32 SYNTAX SEQUENCE OF EoPowerEntry
UNITS "watts" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This table lists Energy Objects."
"This object indicates the rated maximum consumption for ::= { energyObjectMibObjects 2 }
the fully populated Energy Object. The nameplate power
requirements are the maximum power numbers 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 }
eoPowerUnitMultiplier OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX EoPowerEntry
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 power usage of an Energy Object."
and eoPowerNameplate." INDEX { entPhysicalIndex }
::= { eoPowerEntry 3 } ::= { eoPowerTable 1 }
eoPowerAccuracy OBJECT-TYPE EoPowerEntry ::= SEQUENCE {
SYNTAX Integer32 (0..10000) eoPower Integer32,
UNITS "hundredths of percent" eoPowerNameplate Unsigned32,
MAX-ACCESS read-only eoPowerUnitMultiplier UnitMultiplier,
STATUS current eoPowerAccuracy Integer32,
DESCRIPTION eoPowerMeasurementCaliber INTEGER,
"This object indicates a percentage value, in 100ths of a eoPowerCurrentType INTEGER,
percent, representing the assumed accuracy of the usage eoPowerMeasurementLocal TruthValue,
reported by eoPower. For example: The value 1010 means eoPowerAdminState PowerStateSet,
the reported usage is accurate to +/- 10.1 percent. This eoPowerOperState PowerStateSet,
value is zero if the accuracy is unknown or not eoPowerStateEnterReason OwnerString,
applicable based upon the measurement method. }
ANSI and IEC define the following accuracy classes for eoPower OBJECT-TYPE
power measurement: SYNTAX Integer32
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. UNITS "watts"
ANSI C12.20 class 0.2, 0.5" MAX-ACCESS read-only
::= { eoPowerEntry 4 } 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.
eoPowerMeasurementCaliber OBJECT-TYPE The eoPower MUST be less than or equal to the maximum
SYNTAX INTEGER { power that can be consumed at the power state specified
unavailable(1) , by eoPowerState.
unknown(2),
actual(3) ,
estimated(4),
static(5) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies how the usage value reported by
eoPower was obtained:
- unavailable(1): Indicates that the usage is not The eoPowerMeasurementCaliber object specifies how the
available. In such a case, the eoPower value must be 0 usage value reported by eoPower was obtained. The eoPower
for devices that can not measure or report power this value must report 0 if the eoPowerMeasurementCaliber is
option can be used. 'unavailable'. For devices that can not measure or
report power, this option can be used."
::= { eoPowerEntry 1 }
- unknown(2): Indicates that the way the usage was eoPowerNameplate OBJECT-TYPE
determined is unknown. In some cases, entities report SYNTAX Unsigned32
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 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 }
- actual(3): Indicates that the reported usage was eoPowerUnitMultiplier OBJECT-TYPE
measured by the entity through some hardware or direct SYNTAX UnitMultiplier
physical means. The usage data reported is not estimated MAX-ACCESS read-only
or static but is the measured consumption rate. STATUS current
DESCRIPTION
"The magnitude of watts for the usage value in eoPower
and eoPowerNameplate."
::= { eoPowerEntry 3 }
- estimated(4): Indicates that the usage was not eoPowerAccuracy OBJECT-TYPE
determined by physical measurement. The value is a SYNTAX Integer32 (0..10000)
derivation based upon the device type, state, and/or UNITS "hundredths of percent"
current utilization using some algorithm or heuristic. It MAX-ACCESS read-only
is presumed that the entity's state and current STATUS current
configuration were used to compute the value. 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
power measurement:
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
ANSI C12.20 class 0.2, 0.5"
::= { eoPowerEntry 4 }
eoPowerMeasurementCaliber OBJECT-TYPE
SYNTAX INTEGER {
unavailable(1) ,
unknown(2),
actual(3) ,
estimated(4),
static(5) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies how the usage value reported by
eoPower was obtained:
- unavailable(1): Indicates that the usage is not
available. In such a case, the eoPower value must be 0
for devices that can not measure or report power this
option can be used.
- unknown(2): Indicates that the way the usage was
determined is unknown. In some cases, entities report
aggregate power on behalf of another device. In such
cases it is not known whether the usage reported is
actual, estimated or static.
- actual(3): Indicates that the reported usage was
measured by the entity through some hardware or direct
physical means. The usage data reported is not estimated
or static but is the measured consumption rate.
- estimated(4): Indicates that the usage was not
determined by physical measurement. The value is a
derivation based upon the device type, state, and/or
current utilization using some algorithm or heuristic. It
is presumed that the entity's state and current
configuration were used to compute the value.
- static(5): Indicates that the usage was not determined - static(5): Indicates that the usage was not determined
by physical measurement, algorithm or derivation. The by physical measurement, algorithm or derivation. The
usage was reported based upon external tables, usage was reported based upon external tables,
specifications, and/or model information. For example, a specifications, and/or model information. For example, a
PC Model X draws 200W, while a PC Model Y draws 210W." PC Model X draws 200W, while a PC Model Y draws 210W."
::= { eoPowerEntry 5 }
::= { eoPowerEntry 5 } eoPowerCurrentType OBJECT-TYPE
SYNTAX INTEGER {
eoPowerCurrentType OBJECT-TYPE ac(1),
SYNTAX INTEGER { dc(2),
ac(1), unknown(3)
dc(2), }
unknown(3) MAX-ACCESS read-only
} STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "This object indicates whether the eoPower for the
DESCRIPTION Energy Object reports alternating current 'ac', direct
"This object indicates whether the eoPower for the current 'dc', or that the current type is unknown."
Energy Object reports alternating current 'ac', direct ::= { eoPowerEntry 6 }
current 'dc', or that the current type is unknown."
::= { eoPowerEntry 6 }
eoPowerMeasurementLocal OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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
SYNTAX IANAPowerStateSet
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/eman>
RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 8 }
eoPowerOperState OBJECT-TYPE eoPowerMeasurementLocal OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the current operational Power "This object indicates the source of power measurement
State and the Power State Set for the Energy Object. and can be useful when modeling the power usage of
other(0) is not a Power State Set and unknown(255) is attached devices. The power measurement can be performed
not a Power State as such, but simply an indication that by the entity itself or the power measurement of the
the Power State of the Energy Object is unknown. 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 }
Possible values of eoPowerOperState within the Power eoPowerAdminState OBJECT-TYPE
State Set are registered at IANA. A current list of SYNTAX PowerStateSet
assignments can be found at MAX-ACCESS read-write
<http://www.iana.org/assignments/eman> STATUS current
RFC-EDITOR: please check the location after IANA" 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 }
::= { eoPowerEntry 9 } eoPowerOperState OBJECT-TYPE
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.
eoPowerStateEnterReason OBJECT-TYPE Possible values of eoPowerOperState within the Power
SYNTAX OwnerString State Set are registered at IANA. A current list of
MAX-ACCESS read-write assignments can be found at <
STATUS current http://www.iana.org/assignments/power-state-sets>"
DESCRIPTION ::= { eoPowerEntry 9 }
"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 eoPowerStateEnterReason OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerStateEntry SYNTAX OwnerString
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates the maximum power usage, in watts, "This string object describes the reason for the
for every single supported Power State of each Energy eoPowerAdminState transition. Alternatively, this string
Object. may contain with the entity that configured this Energy
Object to this Power State."
DEFVAL { "" }
::= { eoPowerEntry 10 }
This table has cross-reference with the eoPowerTable, eoPowerStateTable OBJECT-TYPE
containing rows describing each Power State for the SYNTAX SEQUENCE OF EoPowerStateEntry
corresponding Energy Object. For every Energy Object in MAX-ACCESS not-accessible
the eoPowerTable, there is a corresponding entry in this STATUS current
table." DESCRIPTION
::= { energyObjectMibObjects 3 } "This table enumerates the maximum power usage, in watts,
for every single supported Power State of each Energy
Object.
eoPowerStateEntry OBJECT-TYPE This table has cross-reference with the eoPowerTable,
SYNTAX EoPowerStateEntry containing rows describing each Power State for the
MAX-ACCESS not-accessible corresponding Energy Object. For every Energy Object in
STATUS current the eoPowerTable, there is a corresponding entry in this
DESCRIPTION table."
"A eoPowerStateEntry extends a corresponding ::= { energyObjectMibObjects 3 }
eoPowerEntry. This entry displays max usage values at
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:
State MaxUsage Units eoPowerStateEntry OBJECT-TYPE
emanmechoff 0 W SYNTAX EoPowerStateEntry
emansoftoff 0 W MAX-ACCESS not-accessible
emanhibernate 0 W STATUS current
emansleep 0 W DESCRIPTION
emanstandby 0 W "A eoPowerStateEntry extends a corresponding
emanready 8 W eoPowerEntry. This entry displays max usage values at
emanlowMinus 8 W every single possible Power State supported by the Energy
emanlow 11 W Object.
emanmediumMinus 11 W For example, given the values of a Energy Object
emanmedium 11 W corresponding to a maximum usage of 0 W at the
emanhighMinus 11 W state emanmechoff, 8 W at state 6 (ready), 11 W at state
emnanhigh 11 W emanmediumMinus,and 11 W at state emanhigh:
Furthermore, this table also includes the total time in State MaxUsage Units
each Power State, along with the number of times a emanmechoff 0 W
particular Power State was entered." emansoftoff 0 W
emanhibernate 0 W
emansleep 0 W
emanstandby 0 W
emanready 8 W
emanlowMinus 8 W
emanlow 11 W
emanmediumMinus 11 W
emanmedium 11 W
emanhighMinus 11 W
emnanhigh 11 W
INDEX { entPhysicalIndex, Furthermore, this table also includes the total time in
eoPowerStateIndex each Power State, along with the number of times a
} particular Power State was entered."
::= { eoPowerStateTable 1 }
EoPowerStateEntry ::= SEQUENCE { INDEX { entPhysicalIndex, eoPowerStateIndex }
eoPowerStateIndex IANAPowerStateSet, ::= { eoPowerStateTable 1 }
eoPowerStateMaxPower INTEGER,
eoPowerStatePowerUnitMultiplier UnitMultiplier,
eoPowerStateTotalTime TimeTicks,
eoPowerStateEnterCount Counter32
} EoPowerStateEntry ::= SEQUENCE {
eoPowerStateIndex PowerStateSet,
eoPowerStateMaxPower INTEGER,
eoPowerStatePowerUnitMultiplier UnitMultiplier,
eoPowerStateTotalTime TimeTicks,
eoPowerStateEnterCount Counter32
}
eoPowerStateIndex OBJECT-TYPE eoPowerStateIndex OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX PowerStateSet
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "This object specifies the index of the Power State of
This object specifies the index of the Power State of the Energy Object within a Power State Set. The semantics
the Energy Object within a Power State Set. The of the specific Power State can be obtained from the
semantics of the specific Power State can be obtained Power State Set definition."
from the Power State Set definition." ::= { eoPowerStateEntry 1 }
::= { eoPowerStateEntry 1 }
eoPowerStateMaxPower OBJECT-TYPE eoPowerStateMaxPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "watts" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum power for the Energy "This object indicates the maximum power for the Energy
Object at the particular Power State. This value is Object at the particular Power State. This value is
specified in SI units of watts with the magnitude of the specified in SI units of watts with the magnitude of the
units (milliwatts, kilowatts, etc.) indicated separately units (milliwatts, kilowatts, etc.) indicated separately
in eoPowerStatePowerUnitMultiplier. If the maximum power in eoPowerStatePowerUnitMultiplier. If the maximum power
is not known for a certain Power State, then the value is is not known for a certain Power State, then the value is
encoded as 0xFFFFFFFF. encoded as 0xFFFFFFFF.
For Power States not enumerated, the value of For Power States not enumerated, the value of
eoPowerStateMaxPower might be interpolated by using the eoPowerStateMaxPower might be interpolated by using the
next highest supported Power State." next highest supported Power State."
::= { eoPowerStateEntry 2 } ::= { eoPowerStateEntry 2 }
eoPowerStatePowerUnitMultiplier OBJECT-TYPE eoPowerStatePowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in "The magnitude of watts for the usage value in
eoPowerStateMaxPower." eoPowerStateMaxPower."
::= { eoPowerStateEntry 3 } ::= { eoPowerStateEntry 3 }
eoPowerStateTotalTime OBJECT-TYPE eoPowerStateTotalTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the total time in hundredths "This object indicates the total time in hundredths
of second that the Energy Object has been in this power of second that the Energy Object has been in this power
state since the last reset, as specified in the state since the last reset, as specified in the
sysUpTime." sysUpTime."
::= { eoPowerStateEntry 4 } ::= { eoPowerStateEntry 4 }
eoPowerStateEnterCount OBJECT-TYPE eoPowerStateEnterCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the Energy "This object indicates how often the Energy Object has
Object has entered this power state, since the last reset of the
entered this power state, since the last reset of the device as specified in the sysUpTime."
device as specified in the sysUpTime." ::= { eoPowerStateEntry 5 }
::= { eoPowerStateEntry 5 }
eoEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyParametersEntry SYNTAX SEQUENCE OF EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to configure the parameters for "This table is used to configure the parameters for
Energy measurement collection in the table Energy measurement collection in the table eoEnergyTable.
eoEnergyTable. This table allows the configuration of This table allows the configuration of different
different measurement settings on the same Energy Object. measurement settings on the same Energy Object.
Implementation of this table only makes sense for Energy Implementation of this table only makes sense for Energy
Objects that an eoPowerMeasurementCaliber of actual." Objects that an eoPowerMeasurementCaliber of actual."
::= { energyObjectMibObjects 4 } ::= { energyObjectMibObjects 4 }
eoEnergyParametersEntry OBJECT-TYPE eoEnergyParametersEntry OBJECT-TYPE
SYNTAX EoEnergyParametersEntry SYNTAX EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry controls an energy measurement in "An entry controls an energy measurement in
eoEnergyTable." eoEnergyTable."
INDEX { entPhysicalIndex, eoEnergyParametersIndex } INDEX { entPhysicalIndex, eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
EoEnergyParametersEntry ::= SEQUENCE { EoEnergyParametersEntry ::= SEQUENCE {
eoEnergyParametersIndex Integer32, eoEnergyParametersIndex Integer32,
eoEnergyParametersIntervalLength TimeInterval, eoEnergyParametersIntervalLength TimeInterval,
eoEnergyParametersIntervalNumber Integer32, eoEnergyParametersIntervalNumber Unsigned32,
eoEnergyParametersIntervalMode INTEGER, eoEnergyParametersIntervalMode INTEGER,
eoEnergyParametersIntervalWindow TimeInterval, eoEnergyParametersIntervalWindow TimeInterval,
eoEnergyParametersSampleRate Integer32, eoEnergyParametersSampleRate Unsigned32,
eoEnergyParametersStatus RowStatus eoEnergyParametersStorageType StorageType,
} eoEnergyParametersStatus RowStatus
eoEnergyParametersIndex OBJECT-TYPE }
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the index of the Energy
Parameters setting for collection of energy measurements
for an Energy Object. An Energy Object can have multiple
eoEnergyParametersIndex, depending on the capabilities
of the Energy Object"
::= { eoEnergyParametersEntry 2 }
eoEnergyParametersIntervalLength OBJECT-TYPE eoEnergyParametersIndex OBJECT-TYPE
SYNTAX TimeInterval SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the length of time in hundredths "This object specifies the index of the Energy Parameters
of seconds over which to compute the average setting for collection of energy measurements for an
eoEnergyConsumed measurement in the eoEnergyTable table. Energy Object. An Energy Object can have multiple
The computation is based on the Energy Object's internal eoEnergyParametersIndex, depending on the capabilities of
sampling rate of power consumed or produced by the Energy the Energy Object"
Object. The sampling rate is the rate at which the Energy ::= { eoEnergyParametersEntry 2 }
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 eoEnergyParametersIntervalLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION 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 }
"The number of intervals maintained in the eoEnergyTable. eoEnergyParametersIntervalNumber OBJECT-TYPE
Each interval is characterized by a specific SYNTAX Unsigned32
eoEnergyCollectionStartTime, used as an index to the MAX-ACCESS read-create
table eoEnergyTable. Whenever the maximum number of STATUS current
entries is reached, the measurement over the new interval DESCRIPTION
replaces the oldest measurement. There is one exception "The number of intervals maintained in the eoEnergyTable.
to this rule: when the eoEnergyMaxConsumed and/or Each interval is characterized by a specific
eoEnergyMaxProduced are in (one of) the two oldest eoEnergyCollectionStartTime, used as an index to the
measurement(s), they are left untouched and the next table eoEnergyTable. Whenever the maximum number of
oldest measurement is replaced." entries is reached, the measurement over the new interval
DEFVAL { 10 } replaces the oldest measurement. There is one exception
::= { eoEnergyParametersEntry 4 } 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 eoEnergyParametersIntervalMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
period(1), period(1),
sliding(2), sliding(2),
total(3) total(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control object to define the mode of interval calculation "A control object to define the mode of interval
for the computation of the average eoEnergyConsumed or calculation for the computation of the average
eoEnergyProvided measurement in the eoEnergyTable table. eoEnergyConsumed or eoEnergyProvided measurement in the
eoEnergyTable table.
A mode of period(1) specifies non-overlapping periodic A mode of period(1) specifies non-overlapping periodic
measurements. measurements.
A mode of sliding(2) specifies overlapping sliding windows A mode of sliding(2) specifies overlapping sliding
where the interval between the start of one interval and windows where the interval between the start of one
the next is defined in eoEnergyParametersIntervalWindow. interval and the next is defined in
eoEnergyParametersIntervalWindow.
A mode of total(3) specifies non-periodic measurement. In A mode of total(3) specifies non-periodic measurement.
this mode only one interval is used as this is a In this mode only one interval is used as this is a
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. " eoEnergyParametersIntervalLength is ignored."
::= { eoEnergyParametersEntry 5 } ::= { eoEnergyParametersEntry 5 }
eoEnergyParametersIntervalWindow OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the duration window between the starting "The length of the duration window between the starting
time of one sliding window and the next starting time in time of one sliding window and the next starting time in
hundredths of seconds, in order to compute the average of hundredths of seconds, in order to compute the average of
eoEnergyConsumed, eoEnergyProvided measurements in the eoEnergyConsumed, eoEnergyProvided measurements in the
eoEnergyTable table. This is valid only when the eoEnergyTable table. This is valid only when the
eoEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyParametersIntervalWindow value should be a multiple eoEnergyParametersIntervalWindow value should be a
of eoEnergyParametersSampleRate." multiple of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 6 } ::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Unsigned32
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sampling rate, in milliseconds, at which the Energy "The sampling rate, in milliseconds, at which the Energy
Object should poll power usage in order to compute the Object should poll power usage in order to compute the
average eoEnergyConsumed, eoEnergyProvided measurements average eoEnergyConsumed, eoEnergyProvided measurements
in the table eoEnergyTable. The Energy Object should in the table eoEnergyTable. The Energy Object should
initially set this sampling rate to a reasonable value, initially set this sampling rate to a reasonable value,
i.e., a compromise between intervals that will provide i.e., a compromise between intervals that will provide
good accuracy by not being too long, but not so short good accuracy by not being too long, but not so short
that they affect the Energy Object performance by that they affect the Energy Object performance by
requesting continuous polling. If the sampling rate is requesting continuous polling. If the sampling rate is
unknown, the value 0 is reported. The sampling rate unknown, the value 0 is reported. The sampling rate
should be selected so that should be selected so that
eoEnergyParametersIntervalWindow is a multiple of eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate. The default value is one eoEnergyParametersSampleRate. The default value is one
second." second."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { eoEnergyParametersEntry 7 } ::= { eoEnergyParametersEntry 7 }
eoEnergyParametersStatus OBJECT-TYPE eoEnergyParametersStorageType OBJECT-TYPE
SYNTAX RowStatus SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { nonVolatile }
::= {eoEnergyParametersEntry 8 }
eoEnergyParametersStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row. The eoEnergyParametersStatus is "The status of this row. The eoEnergyParametersStatus is
used to start or stop energy usage logging. An entry used to start or stop energy usage logging. An entry
status may not be active(1) unless all objects in the status may not be active(1) unless all objects in the
entry have an appropriate value. If this object is not entry have an appropriate value. If this object is not
equal to active, all associated usage-data logged into equal to active, all associated usage-data logged into
the eoEnergyTable will be deleted. The data can be the eoEnergyTable will be deleted. The data can be
destroyed by setting up the eoEnergyParametersStatus to destroyed by setting up the eoEnergyParametersStatus to
destroy." destroy."
::= {eoEnergyParametersEntry 8 }
eoEnergyTable OBJECT-TYPE ::= {eoEnergyParametersEntry 9 }
SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table lists Energy Object energy measurements.
Entries in this table are only created if the
corresponding value of object eoPowerMeasurementCaliber
is active(3), i.e., if the power is actually metered."
::= { energyObjectMibObjects 5 }
eoEnergyEntry OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX EoEnergyEntry SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "This table lists Energy Object energy measurements.
INDEX { eoEnergyParametersIndex, Entries in this table are only created if the
eoEnergyCollectionStartTime } corresponding value of object eoPowerMeasurementCaliber
::= { eoEnergyTable 1 } is active(3), i.e., if the power is actually metered."
::= { energyObjectMibObjects 5 }
EoEnergyEntry ::= SEQUENCE { eoEnergyEntry OBJECT-TYPE
eoEnergyCollectionStartTime TimeTicks, SYNTAX EoEnergyEntry
eoEnergyConsumed Integer32, MAX-ACCESS not-accessible
eoEnergyProvided Integer32, STATUS current
eoEnergyStored Integer32, DESCRIPTION
eoEnergyUnitMultiplier UnitMultiplier, "An entry describing energy measurements."
eoEnergyAccuracy Integer32, INDEX { eoEnergyParametersIndex,
eoEnergyMaxConsumed Integer32, eoEnergyCollectionStartTime }
eoEnergyMaxProduced Integer32, ::= { eoEnergyTable 1 }
eoEnergyDiscontinuityTime TimeStamp
}
eoEnergyCollectionStartTime OBJECT-TYPE EoEnergyEntry ::= SEQUENCE {
SYNTAX TimeTicks eoEnergyCollectionStartTime TimeTicks,
UNITS "hundredths of seconds" eoEnergyConsumed Unsigned32,
MAX-ACCESS not-accessible eoEnergyProvided Unsigned32,
STATUS current eoEnergyStored Unsigned32,
DESCRIPTION eoEnergyUnitMultiplier UnitMultiplier,
"The time (in hundredths of a second) since the eoEnergyAccuracy Integer32,
network management portion of the system was last eoEnergyMaxConsumed Unsigned32,
re-initialized, as specified in the sysUpTime [RFC3418]. eoEnergyMaxProduced Unsigned32,
This object specifies the start time of the energy eoEnergyDiscontinuityTime TimeStamp
measurement sample. " }
::= { eoEnergyEntry 1 }
eoEnergyConsumed OBJECT-TYPE eoEnergyCollectionStartTime OBJECT-TYPE
SYNTAX Integer32 SYNTAX TimeTicks
UNITS "Watt-hours" UNITS "hundredths of seconds"
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy consumed in units of watt- "The time (in hundredths of a second) since the
hours for the Energy Object over the defined interval. network management portion of the system was last
This value is specified in the common billing units of watt- re-initialized, as specified in the sysUpTime [RFC3418].
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) This object specifies the start time of the energy
indicated separately in eoEnergyUnitMultiplier." measurement sample. "
::= { eoEnergyEntry 2 } ::= { eoEnergyEntry 1 }
eoEnergyProvided OBJECT-TYPE eoEnergyConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Unsigned32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy consumed 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 (kW-
Hr, MW-Hr, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 2 }
"This object indicates the energy produced in units of watt- eoEnergyProvided OBJECT-TYPE
hours for the Energy Object over the defined interval. SYNTAX Unsigned32
This value is specified in the common billing units of watt- UNITS "Watt-hours"
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) MAX-ACCESS read-only
indicated separately in eoEnergyUnitMultiplier." STATUS current
::= { eoEnergyEntry 3 } DESCRIPTION
"This object indicates the energy produced in units of
watt-hours for the Energy Object over the defined
interval.
eoEnergyStored OBJECT-TYPE This value is specified in the common billing units of
SYNTAX Integer32 watt-hours with the magnitude of watt-hours (kW-Hr, MW-
UNITS "Watt-hours" Hr, etc.) indicated separately in
MAX-ACCESS read-only eoEnergyUnitMultiplier."
STATUS current ::= { eoEnergyEntry 3 }
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 (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 }
eoEnergyUnitMultiplier OBJECT-TYPE eoEnergyStored OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "Watt-hours"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"This object is the magnitude of watt-hours for the DESCRIPTION
energy field in eoEnergyConsumed, eoEnergyProvided, "This object indicates the difference of the energy
eoEnergyStored, eoEnergyMaxConsumed, and consumed and energy produced for an Energy Object in
eoEnergyMaxProduced." units of watt-hours for the Energy Object over the
::= { eoEnergyEntry 5 } defined interval. This value is specified in the common
billing units of watt-hours with the magnitude of watt-
hours (kW-Hr, MW-Hr, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 }
eoEnergyAccuracy OBJECT-TYPE eoEnergyUnitMultiplier OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX UnitMultiplier
UNITS "hundredths of percent" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This object is the magnitude of watt-hours for the
"This object indicates a percentage accuracy, in 100ths energy field in eoEnergyConsumed, eoEnergyProvided,
of a percent, of Energy usage reporting. eoEnergyAccuracy eoEnergyStored, eoEnergyMaxConsumed, and
is applicable to all Energy measurements in the eoEnergyMaxProduced."
eoEnergyTable. ::= { eoEnergyEntry 5 }
For example: 1010 means the reported usage is accurate to +/- eoEnergyAccuracy OBJECT-TYPE
10.1 percent. SYNTAX Integer32 (0..10000)
This value is zero if the accuracy is unknown." UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a percentage accuracy, in 100ths
of a percent, of Energy usage reporting. eoEnergyAccuracy
is applicable to all Energy measurements in the
eoEnergyTable.
::= { eoEnergyEntry 6 } For example: 1010 means the reported usage is accurate to
+/- 10.1 percent.
eoEnergyMaxConsumed OBJECT-TYPE This value is zero if the accuracy is unknown."
SYNTAX Integer32 ::= { eoEnergyEntry 6 }
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 (kW-Hr, MW-Hr, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 7 }
eoEnergyMaxProduced OBJECT-TYPE eoEnergyMaxConsumed OBJECT-TYPE
SYNTAX Integer32 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 is the maximum energy observed in
eoEnergyEnergyProduced since the monitoring started. This eoEnergyConsumed since the monitoring started or was
value is specified in the units of watt-hours with the reinitialized. This value is specified in the common
magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated billing units of watt-hours with the magnitude of watt-
separately in eoEnergyEnergyUnitMultiplier." hours (kW-Hr, MW-Hr, etc.) indicated separately in
::= { eoEnergyEntry 8 } eoEnergyUnitMultiplier."
::= { eoEnergyEntry 7 }
eoEnergyDiscontinuityTime OBJECT-TYPE eoEnergyMaxProduced OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "Watt-hours"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
DESCRIPTION
"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 (kW-Hr, MW-Hr, etc.) indicated
separately in eoEnergyEnergyUnitMultiplier."
::= { eoEnergyEntry 8 }
eoEnergyDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime [RFC3418] on the most recent "The value of sysUpTime [RFC3418] on the most recent
occasion at which any one or more of this entity's energy occasion at which any one or more of this entity's energy
counters in this table suffered a discontinuity: counters in this table suffered a discontinuity:
eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If
no such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
::= { eoEnergyEntry 9 } ::= { eoEnergyEntry 9 }
-- Notifications -- Notifications
eoPowerEnableStatusNotification OBJECT-TYPE eoPowerEnableStatusNotification
SYNTAX TruthValue OBJECT-TYPE
MAX-ACCESS read-write SYNTAX TruthValue
STATUS current MAX-ACCESS read-write
DESCRIPTION STATUS current
DESCRIPTION
"This object controls whether the system produces "This object controls whether the system produces
notifications for eoPowerStateChange. A false value will notifications for eoPowerStateChange. A false value will
prevent these notifications from being generated." prevent these notifications from being generated."
DEFVAL { false } DEFVAL { false }
::= { energyObjectMibNotifs 1 } ::= { energyObjectMibNotifs 1 }
eoPowerStateChange NOTIFICATION-TYPE eoPowerStateChange NOTIFICATION-TYPE
OBJECTS {eoPowerAdminState, eoPowerOperState, OBJECTS {eoPowerAdminState, eoPowerOperState,
eoPowerStateEnterReason} eoPowerStateEnterReason}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP entity generates the eoPowerStateChange when "The SNMP entity generates the eoPowerStateChange when
the values of eoPowerAdminState or eoPowerOperState, the values of eoPowerAdminState or eoPowerOperState,
in the context of the Power State Set, have changed for in the context of the Power State Set, have changed for
the Energy Object represented by the entPhysicalIndex." the Energy Object represented by the entPhysicalIndex."
::= { energyObjectMibNotifs 2 } ::= { energyObjectMibNotifs 2 }
-- Conformance -- Conformance
energyObjectMibCompliances OBJECT IDENTIFIER
::= { energyObjectMibConform 1 }
energyObjectMibGroups OBJECT IDENTIFIER
::= { energyObjectMibConform 2 }
energyObjectMibFullCompliance 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.
Module Compliance of [RFC6933]
with respect to entity4CRCompliance MUST
be supported which requires implementation
of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
MODULE -- this module
MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
eoPowerEnableStatusNotificationGroup,
energyObjectMibNotifGroup
}
GROUP energyObjectMibEnergyTableGroup
DESCRIPTION "A compliant implementation does not
have to implement.
Module Compliance of [RFC6933]
with respect to entity4CRCompliance MUST
be supported which requires implementation
of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
GROUP energyObjectMibEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not energyObjectMibCompliances OBJECT IDENTIFIER
have to implement. ::= { energyObjectMibConform 1 }
Module Compliance of {RFC6933] energyObjectMibGroups OBJECT IDENTIFIER
with respect to entity4CRCompliance MUST ::= { energyObjectMibConform 2 }
be supported which requires implementation
of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
GROUP energyObjectMibMeterCapabilitiesTableGroup energyObjectMibFullCompliance 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.
DESCRIPTION "A compliant implementation does not Module Compliance of [RFC6933]
have to implement. with respect to entity4CRCompliance MUST
be supported which requires implementation
of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
MODULE -- this module
MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
eoPowerEnableStatusNotificationGroup,
energyObjectMibNotifGroup
}
Module Compliance of [RFC6933] GROUP energyObjectMibEnergyTableGroup
with respect to entity4CRCompliance MUST DESCRIPTION "A compliant implementation does not
be supported which requires implementation have to implement."
of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID."
::= { energyObjectMibCompliances 1 } GROUP energyObjectMibEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not
have to implement."
energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE GROUP energyObjectMibMeterCapabilitiesTableGroup
STATUS current DESCRIPTION "A compliant implementation does not
DESCRIPTION have to implement."
"When this MIB is implemented without support for ::= { energyObjectMibCompliances 1 }
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] energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE
with respect to entity4CRCompliance MUST STATUS current
be supported which requires implementation DESCRIPTION
of 4 MIB objects: entPhysicalIndex, entPhysicalClass, "When this MIB is implemented without support for
entPhysicalName and entPhysicalUUID." 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 -- this module Module Compliance of [RFC6933] with respect to
MANDATORY-GROUPS { entity4CRCompliance MUST be supported which requires
energyObjectMibTableGroup, implementation of 4 MIB objects: entPhysicalIndex,
energyObjectMibStateTableGroup, entPhysicalClass, entPhysicalName and entPhysicalUUID."
energyObjectMibNotifGroup MODULE -- this module
} MANDATORY-GROUPS {
energyObjectMibTableGroup,
energyObjectMibStateTableGroup,
energyObjectMibNotifGroup
}
OBJECT eoPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { energyObjectMibCompliances 2 }
-- Units of Conformance ::= { energyObjectMibCompliances 2 }
energyObjectMibTableGroup OBJECT-GROUP -- Units of Conformance
OBJECTS {
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 }
energyObjectMibStateTableGroup OBJECT-GROUP energyObjectMibTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPowerStateMaxPower, eoPower,
eoPowerStatePowerUnitMultiplier, eoPowerNameplate,
eoPowerStateTotalTime, eoPowerUnitMultiplier,
eoPowerStateEnterCount eoPowerAccuracy,
} eoPowerMeasurementCaliber,
STATUS current eoPowerCurrentType,
DESCRIPTION eoPowerMeasurementLocal,
"This group contains the collection of all the eoPowerAdminState,
objects related to the Power State." eoPowerOperState,
eoPowerStateEnterReason
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Object."
::= { energyObjectMibGroups 1 }
::= { energyObjectMibGroups 2 } 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 energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS { 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."
eoEnergyParametersIntervalLength, ::= { energyObjectMibGroups 3 }
eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate,
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 energyObjectMibEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- eoEnergyCollectionStartTime is not -- eoEnergyCollectionStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
eoEnergyConsumed, eoEnergyConsumed,
eoEnergyProvided, eoEnergyProvided,
eoEnergyStored, eoEnergyStored,
eoEnergyUnitMultiplier, eoEnergyUnitMultiplier,
eoEnergyAccuracy, eoEnergyAccuracy,
eoEnergyMaxConsumed, eoEnergyMaxConsumed,
eoEnergyMaxProduced, eoEnergyMaxProduced,
eoEnergyDiscontinuityTime eoEnergyDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Table." related to the Energy Table."
::= { energyObjectMibGroups 4 } ::= { energyObjectMibGroups 4 }
energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoMeterCapability eoMeterCapability
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the object indicating the "This group contains the object indicating the capability
capability of the Energy Object" of the Energy Object"
::= { energyObjectMibGroups 5 } ::= { energyObjectMibGroups 5 }
eoPowerEnableStatusNotificationGroup OBJECT-GROUP eoPowerEnableStatusNotificationGroup OBJECT-GROUP
OBJECTS { eoPowerEnableStatusNotification } OBJECTS { eoPowerEnableStatusNotification }
STATUS current STATUS current
DESCRIPTION "The collection of objects which are used DESCRIPTION
to enable notification." "The collection of objects which are used to enable
::= { energyObjectMibGroups 6 } notification."
::= { energyObjectMibGroups 6 }
energyObjectMibNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange eoPowerStateChange
} }
STATUS current STATUS current
DESCRIPTION "This group contains the notifications for DESCRIPTION
the power and energy monitoring MIB Module." "This group contains the notifications for
::= { energyObjectMibGroups 7 } the power and energy monitoring MIB Module."
::= { energyObjectMibGroups 7 }
END 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 -- ************************************************************
--
-- This MIB module is used to monitor power attributes of
-- networked devices with measurements.
--
-- This MIB module is an extension of energyObjectMib module.
--
-- *************************************************************
IMPORTS POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN
MODULE-IDENTITY,
OBJECT-TYPE,
mib-2,
Integer32
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
UnitMultiplier
FROM ENERGY-OBJECT-MIB
entPhysicalIndex
FROM ENTITY-MIB;
powerAttributesMIB MODULE-IDENTITY 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;
LAST-UPDATED "201402140000Z" -- 14 Feb 2014 powerAttributesMIB MODULE-IDENTITY
ORGANIZATION "IETF EMAN Working Group" LAST-UPDATED "201406070000Z" -- 07 June 2014
CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: ORGANIZATION "IETF EMAN Working Group"
General Discussion: eman@ietf.org CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/eman/charter/
To Subscribe: Mailing Lists:
https://www.ietf.org/mailman/listinfo/eman General Discussion: eman@ietf.org
Archive: To Subscribe:
http://www.ietf.org/mail-archive/web/eman https://www.ietf.org/mailman/listinfo/eman
Editors: Archive:
http://www.ietf.org/mail-archive/web/eman
Mouli Chandramouli Editors:
Cisco Systems, Inc.
Sarjapur Outer Ring Road
Bangalore 560103
IN
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
Brad Schoening Mouli Chandramouli
44 Rivers Edge Drive Cisco Systems, Inc.
Little Silver, NJ 07739 Sarjapur Outer Ring Road
US Bangalore 560103
Email: brad.schoening@verizon.net IN
Phone: +91 80 4429 2409
Email: moulchan@cisco.com
Juergen Quittek Brad Schoening
NEC Europe Ltd. 44 Rivers Edge Drive
NEC Laboratories Europe Little Silver, NJ 07739
Network Research Division US
Kurfuersten-Anlage 36 Email: brad.schoening@verizon.net
Heidelberg 69115
DE
Phone: +49 6221 4342-115
Email: quittek@neclab.eu
Thomas Dietz Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg Heidelberg 69115
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-115
Email: Thomas.Dietz@nw.neclab.eu Email: quittek@neclab.eu
Benoit Claise Thomas Dietz
Cisco Systems, Inc. NEC Europe Ltd.
De Kleetlaan 6a b1 NEC Laboratories Europe
Degem 1831 Network Research Division
Belgium Kurfuersten-Anlage 36
Phone: +32 2 704 5622 69115 Heidelberg
Email: bclaise@cisco.com" DE
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
DESCRIPTION Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION
"This MIB is used to report AC power attributes in "This MIB is used to report AC power attributes in
devices. The table is a sparse augmentation of the devices. The table is a sparse augmentation of the
eoPowerTable table from the energyObjectMib module. eoPowerTable table from the energyObjectMib module.
Both three-phase and single-phase power Both three-phase and single-phase power
configurations are supported. configurations are supported.
As a requirement for this MIB module, As a requirement for this MIB module,
[EMAN-AWARE-MIB] SHOULD be implemented. [EMAN-AWARE-MIB] SHOULD be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4 with respect to
with respect to entity4CRCompliance MUST entity4CRCompliance MUST be supported which requires
be supported which requires implementation implementation of 4 MIB objects: entPhysicalIndex,
of 4 MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalClass, entPhysicalName and
entPhysicalName and entPhysicalUUID." entPhysicalUUID."
REVISION
"201402140000Z" -- 14 Feb 2014
DESCRIPTION
"Initial version, published as RFC YYY."
::= { mib-2 yyy }
powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 }
powerAttributesMIBObjects OBJECT IDENTIFIER REVISION "201406070000Z" -- 07 June 2014
::= { powerAttributesMIB 1 } DESCRIPTION
"Initial version, published as RFC XXXX"
::= { mib-2 zzz }
-- Objects powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 }
eoACPwrAttributesTable OBJECT-TYPE powerAttributesMIBObjects OBJECT IDENTIFIER
SYNTAX SEQUENCE OF EoACPwrAttributesEntry ::= { powerAttributesMIB 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains power attributes measurements for
supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable."
::= { powerAttributesMIBObjects 1 }
eoACPwrAttributesEntry OBJECT-TYPE -- Objects
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 OBJECT-TYPE
::= { eoACPwrAttributesTable 1 } SYNTAX SEQUENCE OF EoACPwrAttributesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains power attributes measurements for
supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable."
::= { powerAttributesMIBObjects 1 }
EoACPwrAttributesEntry ::= SEQUENCE { eoACPwrAttributesEntry OBJECT-TYPE
eoACPwrAttributesConfiguration INTEGER, SYNTAX EoACPwrAttributesEntry
eoACPwrAttributesAvgVoltage Integer32, MAX-ACCESS not-accessible
eoACPwrAttributesAvgCurrent Integer32, STATUS current
eoACPwrAttributesFrequency Integer32, DESCRIPTION
eoACPwrAttributesPowerUnitMultiplier UnitMultiplier, "This is a sparse extension of the eoPowerTable with
eoACPwrAttributesPowerAccuracy Integer32, entries for power attributes measurements or
eoACPwrAttributesTotalActivePower Integer32, configuration. Each measured value corresponds to an
eoACPwrAttributesTotalReactivePower Integer32, attribute in IEC 61850-7-4 for non-phase measurements
eoACPwrAttributesTotalApparentPower Integer32, within the object MMUX."
eoACPwrAttributesTotalPowerFactor Integer32, INDEX { entPhysicalIndex }
eoACPwrAttributesThdCurrent Integer32, ::= { eoACPwrAttributesTable 1 }
eoACPwrAttributesThdVoltage Integer32
}
eoACPwrAttributesConfiguration OBJECT-TYPE EoACPwrAttributesEntry ::= SEQUENCE {
SYNTAX INTEGER { eoACPwrAttributesConfiguration INTEGER,
sngl(1), eoACPwrAttributesAvgVoltage Integer32,
del(2), eoACPwrAttributesAvgCurrent Unsigned32,
wye(3) eoACPwrAttributesFrequency Integer32,
} eoACPwrAttributesPowerUnitMultiplier UnitMultiplier,
MAX-ACCESS read-only eoACPwrAttributesPowerAccuracy Integer32,
STATUS current eoACPwrAttributesTotalActivePower Integer32,
DESCRIPTION eoACPwrAttributesTotalReactivePower Integer32,
"Configuration describes the physical configurations eoACPwrAttributesTotalApparentPower Integer32,
of the power supply lines: eoACPwrAttributesTotalPowerFactor Integer32,
eoACPwrAttributesThdCurrent Integer32,
eoACPwrAttributesThdVoltage Integer32
}
* alternating current, single phase (SNGL) eoACPwrAttributesConfiguration OBJECT-TYPE
* alternating current, three phase delta (DEL) SYNTAX INTEGER {
* alternating current, three phase Y (WYE) sngl(1),
del(2),
wye(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Configuration describes the physical configurations of
the power supply lines:
Three-phase configurations can be either connected in * alternating current, single phase (SNGL)
a triangular delta (DEL) or star Y (WYE) system. WYE * alternating current, three phase delta (DEL)
systems have a shared neutral voltage, while DEL * alternating current, three phase Y (WYE)
systems do not. Each phase is offset 120 degrees to
each other."
::= { eoACPwrAttributesEntry 1 }
eoACPwrAttributesAvgVoltage OBJECT-TYPE Three-phase configurations can be either connected in a
SYNTAX Integer32 triangular delta (DEL) or star Y (WYE) system. WYE
UNITS "0.1 Volt AC" systems have a shared neutral voltage, while DEL systems
MAX-ACCESS read-only do not. Each phase is offset 120 degrees to each other."
STATUS current ::= { eoACPwrAttributesEntry 1 }
DESCRIPTION
"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 eoACPwrAttributesAvgVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "amperes" UNITS "0.1 Volt AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A measured value for average of the current measured "A measured value for average of the voltage measured
over an integral number of AC cycles For a 3-phase over an integral number of AC cycles For a 3-phase
system, this is the average current (I1+I2+I3)/3. IEC system, this is the average voltage (V1+V2+V3)/3. IEC
61850-7-4 attribute 'Amp'" 61850-7-4 measured value attribute 'Vol'"
::= { eoACPwrAttributesEntry 3 } ::= { eoACPwrAttributesEntry 2 }
eoACPwrAttributesFrequency OBJECT-TYPE eoACPwrAttributesAvgCurrent OBJECT-TYPE
SYNTAX Integer32 (4500..6500) SYNTAX Unsigned32
UNITS "0.01 hertz" UNITS "amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value for the basic frequency of the AC "A measured value for average of the current measured
circuit. IEC 61850-7-4 attribute 'Hz'." over an integral number of AC cycles For a 3-phase
::= { eoACPwrAttributesEntry 4 } system, this is the average current (I1+I2+I3)/3. IEC
61850-7-4 attribute 'Amp'"
::= { eoACPwrAttributesEntry 3 }
eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE eoACPwrAttributesFrequency OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX Integer32 (4500..6500)
MAX-ACCESS read-only UNITS "0.01 hertz"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The magnitude of watts for the usage value in DESCRIPTION
eoACPwrAttributesTotalActivePower, "A measured value for the basic frequency of the AC
eoACPwrAttributesTotalReactivePower circuit. IEC 61850-7-4 attribute 'Hz'."
and eoACPwrAttributesTotalApparentPower measurements. ::= { eoACPwrAttributesEntry 4 }
For 3-phase power systems, this will also include
eoACPwrAttributesWyeActivePower,
eoACPwrAttributesWyeReactivePower and
eoACPwrAttributesWyeApparentPower"
::= { eoACPwrAttributesEntry 5 }
eoACPwrAttributesPowerAccuracy OBJECT-TYPE eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX UnitMultiplier
UNITS "hundredths of percent" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The magnitude of watts for the usage value in
"This object indicates a percentage value, in 100ths of eoACPwrAttributesTotalActivePower,
a percent, representing the presumed accuracy of eoACPwrAttributesTotalReactivePower
active, reactive, and apparent power usage reporting. and eoACPwrAttributesTotalApparentPower measurements.
For example: 1010 means the reported usage is accurate For 3-phase power systems, this will also include
to +/- 10.1 percent. This value is zero if the eoACPwrAttributesWyeActivePower,
accuracy is unknown. eoACPwrAttributesWyeReactivePower and
eoACPwrAttributesWyeApparentPower"
::= { eoACPwrAttributesEntry 5 }
ANSI and IEC define the following accuracy classes for eoACPwrAttributesPowerAccuracy OBJECT-TYPE
power measurement: IEC 62053-22 & 60044-1 class 0.1, SYNTAX Integer32 (0..10000)
0.2, 0.5, 1 & 3. UNITS "hundredths of percent"
ANSI C12.20 class 0.2 & 0.5" MAX-ACCESS read-only
::= { eoACPwrAttributesEntry 6 } 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.
eoACPwrAttributesTotalActivePower 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. IEC 61850-7-4 attribute 'TotW'."
::= { eoACPwrAttributesEntry 7 }
eoACPwrAttributesTotalReactivePower 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 "A measured value of the actual power delivered to or
apparent power. IEC 61850-7-4 attribute 'TotVAr'." consumed by the load. IEC 61850-7-4 attribute 'TotW'."
::= { eoACPwrAttributesEntry 8 } ::= { eoACPwrAttributesEntry 7 }
eoACPwrAttributesTotalApparentPower 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 which "A measured value of the reactive portion of the apparent
determines the apparent power. The apparent power is power. IEC 61850-7-4 attribute 'TotVAr'."
the vector sum of real and reactive power. ::= { eoACPwrAttributesEntry 8 }
Note: watts and volt-amperes are equivalent units and eoACPwrAttributesTotalApparentPower OBJECT-TYPE
may be combined. IEC 61850-7-4 attribute 'TotVA'." SYNTAX Integer32
::= { eoACPwrAttributesEntry 9 } UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the voltage and current which
determines the apparent power. The apparent power is the
vector sum of real and reactive power.
eoACPwrAttributesTotalPowerFactor 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 of percent" ::= { 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. It is dimensionless
and expressed here as a percentage value in 100ths of a
percent. 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 eoACPwrAttributesTotalPowerFactor OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "ten-thousandths"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value for the current total harmonic "A measured value ratio of the real power flowing to the
distortion (THD). Method of calculation is not load versus the apparent power. It is a dimensionless
specified. IEC 61850-7-4 attribute 'ThdAmp'." value between -1 and 1. A power factor of 1 indicates
::= { eoACPwrAttributesEntry 11 } 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 }
eoACPwrAttributesThdVoltage 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 for the voltage total harmonic "A calculated value for the current total harmonic
distortion (THD). Method of calculation is not distortion (THD). Method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdVol'." specified. IEC 61850-7-4 attribute 'ThdAmp'."
::= { eoACPwrAttributesEntry 12 } ::= { eoACPwrAttributesEntry 11 }
eoACPwrAttributesDelPhaseTable OBJECT-TYPE eoACPwrAttributesThdVoltage OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry SYNTAX Integer32 (0..10000)
MAX-ACCESS not-accessible UNITS "hundredths of percent"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"This optional table describes 3-phase power attributes DESCRIPTION
measurements in a DEL configuration with phase-to-phase "A calculated value for the voltage total harmonic
power attributes measurements. Entities having single distortion (THD). Method of calculation is not
phase power shall not have any entities. This is a specified. IEC 61850-7-4 attribute 'ThdVol'."
sparse extension of the eoACPwrAttributesTable. ::= { eoACPwrAttributesEntry 12 }
These attributes correspond to IEC 61850-7.4 MMXU phase eoACPwrAttributesDelPhaseTable OBJECT-TYPE
related measurements and MHAI phase related measured SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry
harmonic or interharmonics." MAX-ACCESS not-accessible
::= { powerAttributesMIBObjects 2 } 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.
eoACPwrAttributesDelPhaseEntry OBJECT-TYPE These attributes correspond to IEC 61850-7.4 MMXU phase
SYNTAX EoACPwrAttributesDelPhaseEntry related measurements and MHAI phase related measured
MAX-ACCESS not-accessible harmonic or interharmonics."
STATUS current ::= { powerAttributesMIBObjects 2 }
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 eoACPwrAttributesDelPhaseEntry OBJECT-TYPE
eoACPwrAttributesDelPhaseIndex is compared against the SYNTAX EoACPwrAttributesDelPhaseEntry
following phase at +120 degrees. Thus, the possible MAX-ACCESS not-accessible
values are: 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.
eoACPwrAttributesDelPhaseIndex Next Phase Angle For phase-to-phase measurements, the
0 120 eoACPwrAttributesDelPhaseIndex is compared against the
120 240 following phase at +120 degrees. Thus, the possible
240 0 values are:
"
INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex}
::= { eoACPwrAttributesDelPhaseTable 1}
EoACPwrAttributesDelPhaseEntry ::= SEQUENCE { eoACPwrAttributesDelPhaseIndex Next Phase Angle
eoACPwrAttributesDelPhaseIndex Integer32, 0 120
eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32, 120 240
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32 240 0
} "
INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex }
::= { eoACPwrAttributesDelPhaseTable 1}
eoACPwrAttributesDelPhaseIndex OBJECT-TYPE EoACPwrAttributesDelPhaseEntry ::= SEQUENCE {
SYNTAX Integer32 (0..359) eoACPwrAttributesDelPhaseIndex Integer32,
MAX-ACCESS not-accessible eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32,
STATUS current eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32
DESCRIPTION }
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesDelPhaseEntry 1 }
eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrAttributesDelPhaseIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..359)
UNITS "0.1 Volt AC" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "A phase angle typically corresponding to 0, 120, 240."
"A measured value of phase to next phase voltages, where ::= { eoACPwrAttributesDelPhaseEntry 1 }
the next phase is IEC 61850-7-4 attribute 'PPV'."
::= { eoACPwrAttributesDelPhaseEntry 2 }
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32
UNITS "hundredths of percent" UNITS "0.1 Volt AC"
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 of phase to next phase voltages, where
disortion for phase to next phase. Method of calculation the next phase is IEC 61850-7-4 attribute 'PPV'."
is not specified. IEC 61850-7-4 attribute 'ThdPPV'." ::= { eoACPwrAttributesDelPhaseEntry 2 }
::= { eoACPwrAttributesDelPhaseEntry 3 }
eoACPwrAttributesWyePhaseTable OBJECT-TYPE eoACPwrAttributesDelThdPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry SYNTAX Integer32 (0..10000)
MAX-ACCESS not-accessible UNITS "hundredths of percent"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"This optional table describes 3-phase power attributes DESCRIPTION
measurements in a WYE configuration with phase-to- "A calculated value for the voltage total harmonic
neutral power attributes measurements. Entities having disortion for phase to next phase. Method of calculation
single phase power shall not have any entities. This is is not specified. IEC 61850-7-4 attribute 'ThdPPV'."
a sparse extension of the eoACPwrAttributesTable. ::= { eoACPwrAttributesDelPhaseEntry 3 }
These attributes correspond to IEC 61850-7.4 MMXU phase eoACPwrAttributesWyePhaseTable OBJECT-TYPE
related measurements and MHAI phase related measured SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry
harmonic or interharmonics." MAX-ACCESS not-accessible
::= { powerAttributesMIBObjects 3 } STATUS current
DESCRIPTION
"This optional table describes 3-phase power attributes
measurements in a WYE configuration with phase-to-neutral
power attributes measurements. Entities having single
phase power shall not have any entities. This is a sparse
extension of the eoACPwrAttributesTable.
eoACPwrAttributesWyePhaseEntry OBJECT-TYPE These attributes correspond to IEC 61850-7.4 MMXU phase
SYNTAX EoACPwrAttributesWyePhaseEntry related measurements and MHAI phase related measured
MAX-ACCESS not-accessible harmonic or interharmonics."
STATUS current ::= { powerAttributesMIBObjects 3 }
DESCRIPTION
"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 eoACPwrAttributesWyePhaseEntry OBJECT-TYPE
WYE 3-phase power system." SYNTAX EoACPwrAttributesWyePhaseEntry
INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex } MAX-ACCESS not-accessible
::= { eoACPwrAttributesWyePhaseTable 1} STATUS current
DESCRIPTION
"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.
EoACPwrAttributesWyePhaseEntry ::= SEQUENCE { Each entry describes power attributes of one phase of a
eoACPwrAttributesWyePhaseIndex Integer32, WYE 3-phase power system."
eoACPwrAttributesWyePhaseToNeutralVoltage Integer32, INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex }
eoACPwrAttributesWyeCurrent Integer32, ::= { eoACPwrAttributesWyePhaseTable 1}
eoACPwrAttributesWyeActivePower Integer32,
eoACPwrAttributesWyeReactivePower Integer32,
eoACPwrAttributesWyeApparentPower Integer32,
eoACPwrAttributesWyePowerFactor Integer32,
eoACPwrAttributesWyeThdCurrent Integer32,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
}
eoACPwrAttributesWyePhaseIndex OBJECT-TYPE EoACPwrAttributesWyePhaseEntry ::= SEQUENCE {
SYNTAX Integer32 (0..359) eoACPwrAttributesWyePhaseIndex Integer32,
MAX-ACCESS not-accessible eoACPwrAttributesWyePhaseToNeutralVoltage Integer32,
STATUS current eoACPwrAttributesWyeCurrent Integer32,
DESCRIPTION eoACPwrAttributesWyeActivePower Integer32,
"A phase angle typically corresponding to 0, 120, 240." eoACPwrAttributesWyeReactivePower Integer32,
::= { eoACPwrAttributesWyePhaseEntry 1 } eoACPwrAttributesWyeApparentPower Integer32,
eoACPwrAttributesWyePowerFactor Integer32,
eoACPwrAttributesWyeThdCurrent Integer32,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
}
eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesWyePhaseIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..359)
UNITS "0.1 Volt AC" MAX-ACCESS not-accessible
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "A phase angle typically corresponding to 0, 120, 240."
"A measured value of phase to neutral voltage. IEC ::= { eoACPwrAttributesWyePhaseEntry 1 }
61850-7-4 attribute 'PNV'."
::= { eoACPwrAttributesWyePhaseEntry 2 }
eoACPwrAttributesWyeCurrent OBJECT-TYPE eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 amperes AC" UNITS "0.1 Volt AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of phase currents. IEC 61850-7-4 "A measured value of phase to neutral voltage. IEC
attribute 'A'." 61850-7-4 attribute 'PNV'."
::= { eoACPwrAttributesWyePhaseEntry 3 }
eoACPwrAttributesWyeActivePower OBJECT-TYPE ::= { eoACPwrAttributesWyePhaseEntry 2 }
SYNTAX Integer32
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 }
eoACPwrAttributesWyeReactivePower OBJECT-TYPE eoACPwrAttributesWyeCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes reactive" UNITS "0.1 amperes AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the reactive portion of the "A measured value of phase currents. IEC 61850-7-4
apparent power with the magnitude of indicated attribute 'A'."
separately in eoPowerUnitMultiplier. IEC 61850-7-4 ::= { eoACPwrAttributesWyePhaseEntry 3 }
attribute 'VAr'"
::= { eoACPwrAttributesWyePhaseEntry 5 }
eoACPwrAttributesWyeApparentPower OBJECT-TYPE eoACPwrAttributesWyeActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "watts"
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 actual power delivered to or
the apparent power with the indicated separately in consumed by the load with the magnitude indicated
eoPowerUnitMultiplier. Active plus reactive power separately in eoPowerUnitMultiplier. IEC 61850-7-4
equals the total apparent power. attribute 'W'"
::= { eoACPwrAttributesWyePhaseEntry 4 }
Note: Watts and volt-amperes are equivalent units and eoACPwrAttributesWyeReactivePower OBJECT-TYPE
may be combined. IEC 61850-7-4 attribute 'VA'." SYNTAX Integer32
::= { eoACPwrAttributesWyePhaseEntry 6 } 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 }
eoACPwrAttributesWyePowerFactor OBJECT-TYPE eoACPwrAttributesWyeApparentPower OBJECT-TYPE
SYNTAX Integer32 (-10000..10000) SYNTAX Integer32
UNITS "hundredths of percent" UNITS "volt-amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value ratio of the real power flowing to "A measured value of the voltage and current determines
the load versus the apparent power for this phase. IEC the apparent power with the indicated separately in
61850-7-4 attribute 'PF'. Power Factor can be positive eoPowerUnitMultiplier. Active plus reactive power equals
or negative where the sign should be in lead/lag (IEEE) the total apparent power.
form."
::= { eoACPwrAttributesWyePhaseEntry 7 }
eoACPwrAttributesWyeThdCurrent OBJECT-TYPE Note: Watts and volt-amperes are equivalent units and may
SYNTAX Integer32 (0..10000) be combined. IEC 61850-7-4 attribute 'VA'."
UNITS "hundredths of percent" ::= { eoACPwrAttributesWyePhaseEntry 6 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
disortion (THD) for phase to phase. Method of
calculation is not specified.
IEC 61850-7-4 attribute 'ThdA'."
::= { eoACPwrAttributesWyePhaseEntry 8 }
eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesWyePowerFactor OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "ten-thousandths"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value of the voltage total harmonic "A measured value ratio of the real power flowing to the
distortion (THD) for phase to neutral. IEC 61850-7-4 load versus the apparent power for this phase. It is a
attribute 'ThdPhV'." dimensionless value between -1 and 1. IEC 61850-7-4
::= { eoACPwrAttributesWyePhaseEntry 9 } attribute 'PF'. Power Factor can be positive or negative
where the sign should be in lead/lag (IEEE) form."
::= { eoACPwrAttributesWyePhaseEntry 7 }
-- Conformance 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
disortion (THD) for phase to phase. Method of
calculation is not specified.
IEC 61850-7-4 attribute 'ThdA'."
::= { eoACPwrAttributesWyePhaseEntry 8 }
powerAttributesMIBCompliances OBJECT IDENTIFIER eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE
::= { powerAttributesMIB 2 } SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value of the voltage total harmonic
distortion (THD) for phase to neutral. IEC 61850-7-4
attribute 'ThdPhV'."
::= { eoACPwrAttributesWyePhaseEntry 9 }
powerAttributesMIBGroups OBJECT IDENTIFIER -- Conformance
::= { powerAttributesMIB 3 }
powerAttributesMIBFullCompliance MODULE-COMPLIANCE powerAttributesMIBCompliances OBJECT IDENTIFIER
STATUS current ::= { powerAttributesMIB 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.
Module Compliance of [RFC6933] with respect to powerAttributesMIBGroups OBJECT IDENTIFIER
entity4CRCompliance MUST be supported which requires ::= { powerAttributesMIB 3 }
implementation of 4 MIB objects: entPhysicalIndex,
entPhysicalClass, entPhysicalName and entPhysicalUUID."
MODULE -- this module powerAttributesMIBFullCompliance MODULE-COMPLIANCE
MANDATORY-GROUPS { STATUS current
powerACPwrAttributesMIBTableGroup 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.
GROUP powerACPwrAttributesOptionalMIBTableGroup Module Compliance of [RFC6933] with respect to
DESCRIPTION entity4CRCompliance MUST be supported which requires
"A compliant implementation does not have implementation of 4 MIB objects: entPhysicalIndex,
to implement." entPhysicalClass, entPhysicalName and entPhysicalUUID."
GROUP powerACPwrAttributesDelPhaseMIBTableGroup MODULE -- this module
DESCRIPTION MANDATORY-GROUPS {
"A compliant implementation does not have to powerACPwrAttributesMIBTableGroup
implement." }
GROUP powerACPwrAttributesWyePhaseMIBTableGroup GROUP powerACPwrAttributesOptionalMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have
implement." to implement."
::= { powerAttributesMIBCompliances 1 } GROUP powerACPwrAttributesDelPhaseMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to implement."
-- Units of Conformance GROUP powerACPwrAttributesWyePhaseMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to implement."
::= { powerAttributesMIBCompliances 1 }
powerACPwrAttributesMIBTableGroup OBJECT-GROUP -- Units of Conformance
OBJECTS {
-- Note that object entPhysicalIndex is NOT
-- included since it is not-accessible
eoACPwrAttributesAvgVoltage, powerACPwrAttributesMIBTableGroup OBJECT-GROUP
eoACPwrAttributesAvgCurrent, OBJECTS {
eoACPwrAttributesFrequency, -- Note that object entPhysicalIndex is NOT
eoACPwrAttributesPowerUnitMultiplier, -- included since it is not-accessible
eoACPwrAttributesPowerAccuracy, eoACPwrAttributesAvgVoltage,
eoACPwrAttributesTotalActivePower, eoACPwrAttributesAvgCurrent,
eoACPwrAttributesTotalReactivePower, eoACPwrAttributesFrequency,
eoACPwrAttributesTotalApparentPower, eoACPwrAttributesPowerUnitMultiplier,
eoACPwrAttributesTotalPowerFactor eoACPwrAttributesPowerAccuracy,
} eoACPwrAttributesTotalActivePower,
STATUS current eoACPwrAttributesTotalReactivePower,
DESCRIPTION eoACPwrAttributesTotalApparentPower,
"This group contains the collection of all the power eoACPwrAttributesTotalPowerFactor
attributes objects related to the Energy Object." }
::= { powerAttributesMIBGroups 1 } STATUS current
DESCRIPTION
"This group contains the collection of all the power
attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 1 }
powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoACPwrAttributesConfiguration, eoACPwrAttributesConfiguration,
eoACPwrAttributesThdCurrent, eoACPwrAttributesThdCurrent,
eoACPwrAttributesThdVoltage eoACPwrAttributesThdVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
attributes objects related to the Energy Object." attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 2 } ::= { powerAttributesMIBGroups 2 }
powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoACPwrAttributesDelPhaseIndex are NOT -- eoACPwrAttributesDelPhaseIndex are NOT
-- included since they are not-accessible -- included since they are not-accessible
eoACPwrAttributesDelPhaseToNextPhaseVoltage, eoACPwrAttributesDelPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage eoACPwrAttributesDelThdPhaseToNextPhaseVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all power "This group contains the collection of all power
attributes of a phase in a DEL 3-phase power system." attributes of a phase in a DEL 3-phase power system."
::= { powerAttributesMIBGroups 3 } ::= { powerAttributesMIBGroups 3 }
powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoACPwrAttributesWyePhaseIndex are NOT -- eoACPwrAttributesWyePhaseIndex are NOT
-- included since they are not-accessible -- included since they are not-accessible
eoACPwrAttributesWyePhaseToNeutralVoltage, eoACPwrAttributesWyePhaseToNeutralVoltage,
eoACPwrAttributesWyeCurrent, eoACPwrAttributesWyeCurrent,
eoACPwrAttributesWyeActivePower, eoACPwrAttributesWyeActivePower,
eoACPwrAttributesWyeReactivePower, eoACPwrAttributesWyeReactivePower,
eoACPwrAttributesWyeApparentPower, eoACPwrAttributesWyeApparentPower,
eoACPwrAttributesWyePowerFactor, eoACPwrAttributesWyePowerFactor,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage, eoACPwrAttributesWyeThdPhaseToNeutralVoltage,
eoACPwrAttributesWyeThdCurrent eoACPwrAttributesWyeThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all power "This group contains the collection of all power
attributes of a phase in a WYE 3-phase power system." attributes of a phase in a WYE 3-phase power system."
::= { powerAttributesMIBGroups 4 } ::= { powerAttributesMIBGroups 4 }
END END
10. Implementation Status 10. Implementation Status
[Note to RFC Editor: Please remove this section and the [Note to RFC Editor: Please remove this section and the
reference to [RFC6982] before publication.] reference to [RFC6982] before publication.]
This section records the status of known implementations of the This section records the status of known implementations of the
EMAN-Monitoring MIB at the time of posting of this Internet- EMAN-Monitoring MIB at the time of posting of this Internet-
Draft, and is based on a proposal described in [RFC6982]. Draft, and is based on a proposal described in [RFC6982].
The description of implementations in this section is intended The description of implementations in this section is intended
to assist the IETF in its decision processes in progressing to assist the IETF in its decision processes in progressing
drafts to RFCs. drafts to RFCs.
10.1. SNMP Research 10.1. SNMP Research
Organization: SNMP Research, Inc. Organization: SNMP Research, Inc.
Maturity: Prototype based upon early drafts of the MIBs. Maturity: Prototype based upon early drafts of the MIBs.
We anticipate updating it to more recent We anticipate updating it to more recent
documents as development schedules allow. documents as development schedules allow.
Coverage: Code was generated to implement all MIB objects Coverage: Code was generated to implement all MIB objects
in ENTITY-MIB (Version 4), in ENTITY-MIB (Version 4),
ENERGY-OBJECT-CONTEXT-MIB, ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB, ENERGY-OBJECT-MIB,
POWER-ATTRIBUTES-MIB, POWER-ATTRIBUTES-MIB,
and BATTERY-MIB. and BATTERY-MIB.
Implementation experience: The documents are implementable. Implementation experience: The documents are implementable.
Comments: Technical comments about the Comments: Technical comments about the
ENERGY-OBJECT-CONTEXT-MIB, ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB, and ENERGY-OBJECT-MIB, and
BATTERY-MIB BATTERY-MIB
were submitted to the EMAN Working Group were submitted to the EMAN Working Group
E-mail list. E-mail list.
Licensing: Proprietary, royalty licensing Licensing: Proprietary, royalty licensing
Contact: Alan Luchuk, luchuk at snmp.com Contact: Alan Luchuk, luchuk at snmp.com
URL: http://www.snmp.com/ URL: http://www.snmp.com/
10.2. Cisco Systems 10.2. Cisco Systems
Organization: Cisco Systems, Inc. Organization: Cisco Systems, Inc.
Maturity: Prototype based upon early version drafts of Maturity: Prototype based upon early version drafts of
the MIBs. We anticipate updating the MIB the MIBs. We anticipate updating the MIB
modules as when the drafts are updated. modules as when the drafts are updated.
Coverage: Code was generated to implement all MIB objects Coverage: Code was generated to implement all MIB objects
in the ENTITY-MIB (Version 4), and in the ENTITY-MIB (Version 4), and
ENERGY-OBJECT-MIB. ENERGY-OBJECT-MIB.
Implementation experience: The MIB modules are implemented Implementation experience: The MIB modules are implemented
on Cisco router platforms to measure and report on Cisco router platforms to measure and report
router energy measurements. The documents are router energy measurements. The documents are
implementable. implementable.
Licensing: Proprietary Licensing: Proprietary
URL: http://www.cisco.com URL: http://www.cisco.com
11. Security Considerations 11. Security Considerations
Some of the readable objects in these MIB modules (i.e., objects Some of the readable objects in these MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
thus important to control even GET and/or NOTIFY access to these thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects objects and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. when sending them over the network via SNMP.
There are a number of management objects defined in these MIB There are a number of management objects defined in these MIB
modules with a MAX-ACCESS clause of read-write and/or read- modules with a MAX-ACCESS clause of read-write and/or read-
create. Such objects MAY be considered sensitive or vulnerable create. Such objects MAY be considered sensitive or vulnerable
in some network environments. The support for SET operations in in some network environments. The support for SET operations in
a non-secure environment without proper protection can have a a non-secure environment without proper protection can have a
negative effect on network operations. The following are the negative effect on network operations. The following are the
tables and objects and their sensitivity/vulnerability: tables and objects and their sensitivity/vulnerability:
- Unauthorized changes to the eoPowerOperState (via - Unauthorized changes to the eoPowerOperState (via
theeoPowerAdminState ) MAY disrupt the power settings of the theeoPowerAdminState ) MAY disrupt the power settings of the
differentEnergy Objects, and therefore the state of differentEnergy Objects, and therefore the state of
functionality of the respective Energy Objects. functionality of the respective Energy Objects.
- Unauthorized changes to the eoEnergyParametersTable MAY - Unauthorized changes to the eoEnergyParametersTable MAY
disrupt energy measurement in the eoEnergyTable table. disrupt energy measurement in the eoEnergyTable table.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example, by using Even if the network itself is secure (for example, by using
IPsec), there is still no secure control over who on the secure IPsec), there is still no secure control over who on the secure
network is allowed to access and GET/SET network is allowed to access and GET/SET
(read/change/create/delete) the objects in these MIB modules. (read/change/create/delete) the objects in these MIB modules.
It is RECOMMENDED that implementers consider the security It is RECOMMENDED that implementers consider the security
features as provided by the SNMPv3 framework (see [RFC3410], features as provided by the SNMPv3 framework (see [RFC3410],
section 8), including full support for the SNMPv3 cryptographic section 8), including full support for the SNMPv3 cryptographic
mechanisms (for authentication and privacy). mechanisms (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to responsibility to ensure that the SNMP entity giving access to
an instance of these MIB modules is properly configured to give an instance of these MIB modules is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to GET or SET (change/create/delete) them. legitimate rights to GET or SET (change/create/delete) them.
12. IANA Considerations 12. IANA Considerations
The MIB modules in this document use the following IANA-assigned The MIB modules in this document use the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
energyObjectMIB { mib-2 xxx } IANAPowerStateSet-MIB { mib-2 xxx }
powerAttributesMIB { mib-2 yyy } energyObjectMIB { mib-2 yyy }
Editor's Note (to be removed prior to publication): IANA is powerAttributesMIB { mib-2 zzz }
requested to assign a value for "XXX" and "YYY" under the 'mib-
2' subtree and to record the assignment in the SMI Numbers
registry. When the assignment has been made, the RFC Editor is
asked to replace "XXX" and "YYY"(here and in the MIB module)
with the assigned value and to remove this note.
13. Contributors EDITOR'S NOTE (to be removed prior to publication): IANA is
requested to assign a value for "yyy" and "zzz" under the 'mib-
2' subtree and to record the assignment in the SMI Numbers
registry. When the assignment has been made, the RFC Editor is
asked to replace "yyy" and "zzz"(here and in the MIB module)
with the assigned value and to remove this note.
This document results from the merger of two initial proposals. 12.1. IANAPowerStateSet-MIB module
The following persons made significant contributions either in
one of the initial proposals or in this document.
John Parello This document defines the initial version of the IANA-maintained
The initial set of Power State Sets are specified in [EMAN-
FMWK]. IANA maintains a Textual Convention PowerStateSet in the
IANAPowerStateSet-MIB module, with the initial set of Power
State Sets and the Power States within those Power State Sets as
proposed in the [EMAN-FMWK]. The current version of
PowerStateSet Textual convention can be accessed
http://www.iana.org/assignments/power-state-sets.
Rolf Winter New Assignments (and potential deprecation) to Power State Sets
shall be administered by IANA and the guidelines and procedures
are specified in [EMAN-FMWK], and will, as a consequence, the
IANAPowerStateSet Textual Convention should be updated.
Dominique Dudkowski 13. Contributors
14. Acknowledgment This document results from the merger of two initial proposals.
The following persons made significant contributions either in
one of the initial proposals or in this document:
The authors would like to thank Shamita Pisal for her prototype John Parello
of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically.
The authors would like to thank Juergen Schoenwalder for Rolf Winter
proposing the design of the Textual Convention for
IANAPowerStateSet and Ira McDonald for his feedback. Special
appreciation to Laurent Guise for his review and input on power
quality measurements. Thanks for the many comments on the design
of the EnergyTable from Minoru Teraoka and Hiroto Ogaki.
Many thanks to Alan Luchuk for the detailed review of the MIB Dominique Dudkowski
and his comments.
And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom 14. Acknowledgment
Nadeau.
15. References The authors would like to thank Shamita Pisal for her prototype
of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically.
15.1. Normative References The authors would like to thank Juergen Schoenwalder for
proposing the design of the Textual Convention for PowerStateSet
and Ira McDonald for his feedback. Special appreciation to
Laurent Guise for his review and input on power quality
measurements. Thanks for the many comments on the design of the
EnergyTable from Minoru Teraoka and Hiroto Ogaki.
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Many thanks to Alan Luchuk for the detailed review of the MIB
and his comments.
And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom
Nadeau.
15. References
15.1. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, BCP 14, RFC 2119, March 1997. Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB",
RFC3621, December 2003. RFC3621, December 2003.
[RFC6933] A. Bierman, D. Romascanu, J. Quittek and M. [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", RFC 6933, May Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013. 2013.
[EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili, [EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili,
"draft-ietf-eman-energy-aware-mib-14", work in "draft-ietf-eman-energy-aware-mib-14", work in
progress, February 10 2013. progress, February 10 2013.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
15.2. Informative References 15.2. Informative References
[RFC1628] S. Bradner, "UPS Management Information Base", RFC [RFC1628] S. Bradner, "UPS Management Information Base", RFC
1628, May 1994 1628, May 1994
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework ", RFC 3410, December Standard Management Framework ", RFC 3410, December
2002. 2002.
[RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S.
Waldbusser, "Management Information Base (MIB) for the Waldbusser, "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", RFC3418, Simple Network Management Protocol (SNMP)", RFC3418,
December 2002. December 2002.
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity
Sensor Management Information Base", RFC 3433, December Sensor Management Information Base", RFC 3433, December
2002. 2002.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
"Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
Running Code: The Implementation Status Section", RFC Running Code: The Implementation Status Section", RFC
6982, July 2013. 6982, July 2013.
[RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M. [RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M.
Chandramouli, " Requirements for Energy Management", Chandramouli, " Requirements for Energy Management",
RFC 6988, September 2013. RFC 6988, September 2013.
[EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek, [EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek,
J., "Energy Management Framework", draft-ietf-eman- J., "Energy Management Framework", draft-ietf-eman-
framework-11, October 2013. framework-19, April 2014.
[EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B. [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B.
"Energy Management (EMAN) Applicability Statement", "Energy Management (EMAN) Applicability Statement",
draft-ietf-eman-applicability-statement-04, October draft-ietf-eman-applicability-statement-05, April 2014.
2013.
[ACPI] "Advanced Configuration and Power Interface
Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3
0b.pdf
[DMTF] "Power State Management Profile DMTF DSP1027 Version [DMTF] "Power State Management Profile DMTF DSP1027 Version
2.0" December 2009 2.0" December 2009
http://www.dmtf.org/sites/default/files/standards/docum http://www.dmtf.org/sites/default/files/standards/docum
ents/DSP1027_2.0.0.pdf ents/DSP1027_2.0.0.pdf
[IEEE1621] "Standard for User Interface Elements in Power [IEEE1621] "Standard for User Interface Elements in Power
Control of Electronic Devices Employed in Control of Electronic Devices Employed in
Office/Consumer Environments", IEEE 1621, December Office/Consumer Environments", IEEE 1621, December
2004. 2004.
[IEC.61850-7-4] International Electrotechnical Commission, [IEC.61850-7-4] International Electrotechnical Commission,
"Communication networks and systems for power utility "Communication networks and systems for power utility
automation Part 7-4: Basic communication structure automation Part 7-4: Basic communication structure
Compatible logical node classes and data object Compatible logical node classes and data object
classes", 2010. classes", 2010.
[IEC.62053-21] International Electrotechnical Commission, [IEC.62053-21] International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 1 and 2)", 2003. (classes 1 and 2)", 2003.
[IEC.62053-22]International Electrotechnical Commission, [IEC.62053-22]International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 0,2 S and 0,5 S)", 2003. (classes 0,2 S and 0,5 S)", 2003.
Authors' Addresses Authors' Addresses
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
 End of changes. 446 change blocks. 
2658 lines changed or deleted 2709 lines changed or added

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