draft-ietf-eman-energy-monitoring-mib-00.txt   draft-ietf-eman-energy-monitoring-mib-01.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: February 5, 2012 Independent Consultant Expires: April 31 2012 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
August 5, 2011 October 31, 2011
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-00 draft-ietf-eman-energy-monitoring-mib-01
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79. with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 2, line 34 skipping to change at page 2, line 34
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119]. described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction............................................ 3 1. Introduction............................................. 3
2. The Internet-Standard Management Framework.............. 4 2. The Internet-Standard Management Framework............... 4
3. Use Cases............................................... 4 3. Use Cases................................................ 4
4. Terminology............................................. 5 4. Terminology.............................................. 5
5. Architecture Concepts Applied to the MIB Module......... 5 5. Architecture Concepts Applied to the MIB Module.......... 5
5.1. Power Monitor Information............................ 11 5.1. Energy Object Information............................. 12
5.2. Power State.......................................... 12 5.2. Power State........................................... 12
5.2.1. Power State Set...............................13 5.2.1. Power State Set................................13
5.2.2. IEEE1621 Power State Set......................13 5.2.2. IEEE1621 Power State Set.......................13
5.2.3. DMTF Power State Set..........................13 5.2.3. DMTF Power State Set...........................14
5.2.4. EMAN Power State Set..........................14 5.2.4. EMAN Power State Set...........................15
5.3. Power Monitor Usage Information...................... 17 5.3. Energy Object Usage Information....................... 18
5.4. Optional Power Usage Quality......................... 18 5.4. Optional Power Usage Quality.......................... 18
5.5. Optional Energy Measurement.......................... 19 5.5. Optional Energy Measurement........................... 19
5.6. Fault Management...................................... 22 5.6. Fault Management...................................... 23
6. Discovery............................................... 23 6. Discovery............................................... 23
6.1. ENERGY-AWARE-MIB Module Implemented................... 23 6.1. ENERGY-AWARE-MIB Module Implemented................... 23
6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB 6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB
Implemented................................................ 24 Implemented................................................ 24
6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented.24 6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented.25
7. Link with the other IETF MIBs........................... 24 7. Link with the other IETF MIBs........................... 25
7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB..24 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB..25
7.2. Link with the ENTITY-STATE MIB......................26 7.2. Link with the ENTITY-STATE MIB......................26
7.3. Link with the POWER-OVER-ETHERNET MIB...............26 7.3. Link with the POWER-OVER-ETHERNET MIB...............27
7.4. Link with the UPS MIB...............................27 7.4. Link with the UPS MIB...............................28
7.5. Link with the LLDP and LLDP-MED MIBs................28 7.5. Link with the LLDP and LLDP-MED MIBs................29
8. Implementation Scenario................................. 29 8. Implementation Scenario................................. 29
9. Structure of the MIB.................................... 31 9. Structure of the MIB.................................... 32
10. MIB Definitions........................................ 31 10. MIB Definitions........................................ 32
11. Security Considerations................................ 66 11. Security Considerations................................ 69
12. IANA Considerations.................................... 67 12. IANA Considerations.................................... 70
12.1. IANA Considerations for the MIB Modules.............. 67 12.1. IANA Considerations for the MIB Modules.............. 70
12.2. IANA Registration of new Power State Set............. 67 12.2. IANA Registration of new Power State Set............. 71
12.2.1. IANA Registration of the IEEE1621 Power State Set.68 12.2.1. IANA Registration of the IEEE1621 Power State Set..71
12.2.2. IANA Registration of the DMTF Power State Set.....68 12.2.2. IANA Registration of the DMTF Power State Set......71
12.2.3. IANA Registration of the EMAN Power State Set.....69 12.2.3. IANA Registration of the EMAN Power State Set......72
12. Contributors........................................... 69 12. Contributors........................................... 72
13. Acknowledgment......................................... 69 13. Acknowledgment......................................... 72
14. Open Issues............................................ 69 14. Open Issues............................................ 73
15. References............................................. 72 15. References............................................. 74
15.2. Normative References...............................72 15.2. Normative References...............................74
15.3. Informative References.............................72 15.3. Informative References.............................74
1. Introduction 1. Introduction
This document defines a subset of the Management Information This document defines a subset of the Management Information
Base (MIB) for use in energy management of devices within or Base (MIB) for use in energy management of devices within or
connected to communication networks. The MIB modules in this connected to communication networks. The MIB modules in this
document are designed to provide a model for energy management, document are designed to provide a model for energy management,
which includes monitoring for power state and energy consumption which includes monitoring for power state and energy consumption
of networked elements. This MIB takes into account the Power of networked elements. This MIB takes into account the Energy
Management Architecture [EMAN-FRAMEWORK], which in turn, is Management Framework [EMAN-FRAMEWORK], which in turn, is based
based on the Power Monitoring Requirements [EMAN-REQ]. on the Requirements for Energy Management[EMAN-REQ].
Energy management is applicable to devices in communication Energy management is applicable to devices in communication
networks. Target devices for this specification include (but networks. Target devices for this specification include (but
are not limited to): routers, switches, Power over Ethernet are not limited to): routers, switches, Power over Ethernet
(PoE) endpoints, protocol gateways for building management (PoE) endpoints, protocol gateways for building management
systems, intelligent meters, home energy gateways, hosts and systems, intelligent meters, home energy gateways, hosts and
servers, sensor proxies, etc. 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.
Devices and their sub-components may be characterized by the Devices and their sub-components may be characterized by the
skipping to change at page 5, line 4 skipping to change at page 5, line 6
REQ] cover devices typically found in communications networks, REQ] cover devices typically found in communications networks,
such as switches, routers, and various connected endpoints. For such as switches, routers, and various connected endpoints. For
a power monitoring architecture to be useful, it should also a power monitoring architecture to be useful, it should also
apply to facility meters, power distribution units, gateway apply to facility meters, power distribution units, gateway
proxies for commercial building control, home automation 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 is broader than that specified in [EMAN-REQ]. Several document is broader than that specified in [EMAN-REQ]. 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]. An "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An
illustrative example scenario is presented in Section 8. " illustrative example scenario is presented in Section 8.
Implementation Scenario".
4. Terminology 4. Terminology
The definitions of basic terms like Power Monitor, Power Monitor The definitions of basic terms such as Energy Object, Energy
Parent, Power Monitor Child, Power Monitor Meter Domain, Power Object Parent, Energy Object Child, Energy Object Meter
State can be found in the Power Management Architecture [EMAN- Domain, Power State can be found in the terminology draft
FRAMEWORK]. draft-parello-eman-definitions.
EDITOR'S NOTE: it is foreseen that some more term will follow
such a Proxy, Aggregator, Energy Management, etc...
Power State Set Power State Set
A Power State Set is defined as a sequence of incremental A Power State Set is defined as a sequence of incremental
energy saving modes of a device. The elements of this set can energy saving modes of a device. The elements of this set can
be viewed as an interface for the underlying device- be viewed as an interface for the underlying device-
implemented power settings of a device. Examples of Power implemented power settings of a device. Examples of Power
State Sets include DTMF [DMTF], IEEE1621 [IEEE1621], ACPI State Sets include DTMF [DMTF], IEEE1621 [IEEE1621], ACPI
[ACPI] and EMAN. [ACPI] and EMAN.
EDITOR NOTE: Use the latest definition from draft-parello-
eman-definitions
Power State Power State
A Power State is defined as a specific power setting for a A Power State is defined as a specific power setting for an
Power Monitor (e.g., shut, hibernate, sleep, high). Within the Energy Object (e.g., shut, hibernate, sleep, high). Within the
context of a Power State Set, the Power State of a device is context of a Power State Set, the Power State of a device is
one of the power saving modes in that Power State Set. one of the power saving modes in that Power State Set.
EDITOR'S NOTE: the definitions of Power State Series and Power EDITOR NOTE: Use the latest definition from draft-parello-
State should be copied over in [EMAN-FRAMEWORK], and referenced eman-definitions
here.
5. Architecture Concepts Applied to the MIB Module 5. Architecture Concepts Applied to the MIB Module
This section describes the concepts specified in the Power This section describes the concepts specified in the Energy
Monitor Architecture [EMAN-FRAMEWORK] that pertain to power Management Framework [EMAN-FRAMEWORK] that pertain to power
usage, with specific information related to the MIB module usage, with specific information related to the MIB module
specified in this document. This subsection maps to the section specified in this document. This subsection maps to the section
"Architecture High Level Concepts" in the Power Monitoring "Architecture High Level Concepts" in the Power Monitoring
Architecture [EMAN-FRAMEWORK]. Architecture [EMAN-FRAMEWORK].
The Energy Monitoring MIB has 2 independent MIB modules. The The Energy Monitoring MIB has 2 independent MIB modules. The
first MIB module powerMonitorMIB is focused on measurement of first MIB module energyObjectMib is focused on measurement of
power and energy. The second MIB module powerQualityMIB is power and energy. The second MIB module powerQualityMIB is
focused on Power Quality measurement. focused on Power Quality measurements.
The powerMonitorMIB MIB module consists of four tables. The The energyObjectMib MIB module consists of four tables. The
first table pmPowerTable is indexed by pmPowerIndex and first table eoPowerTable is indexed by eoPowerIndex. The second
pmPowerStateSetIndex. The second table pmPowerStateTable indexed table eoPowerStateTable indexed by eoPowerIndex,and
by pmPowerIndex, pmPowerStateSetIndex and pmPowerStateIndex. eoPowerStateIndex. . The eoEnergyParametersTable and
pmEnergyParametersTable and pmEnergyTable are indexed by eoEnergyTable are indexed by eoPowerIndex.
pmPowerIndex.
pmPowerTable(1) eoPowerTable(1)
| |
+---pmPowerEntry(1) [pmPowerIndex, pmPowerStateSet] +---eoPowerEntry(1) [eoPowerIndex]
| | | |
| +-- --- Integer32 pmPowerIndex(1) | +-- --- Integer32 eoPowerIndex(1)
| +-- --- PowerStateSet pmPowerStateSet(2) | +---r-n Integer32 eoPower(2)
| +-- r-n Integer32 pmPower(3) | +-- r-n Integer32 eoPowerNamePlate(3)
| +-- r-n Integer32 pmPowerNamePlate(4) | +-- r-n UnitMultiplier eoPowerUnitMultiplier(4)
| +-- r-n UnitMultiplier pmPowerUnitMultiplier(5) | +-- r-n Integer32 eoPowerAccuracy(5)
| +-- r-n Integer32 pmPowerAccuracy(6) | +-- r-n INTEGER eoMeasurementCaliber(6)
| +-- r-n INTEGER pmMeasurementCaliber(7) | +-- r-n INTEGER eoPowerCurrentType(7)
| +-- r-n INTEGER pmPowerCurrentType(8) | +-- r-n INTEGER eoPowerOrigin(8)
| +-- r-n INTEGER pmPowerOrigin(9) | +-- rwn Integer32 eoPowerAdminState(9)
| +-- rwn Integer32 pmPowerAdminState(10) | +-- r-n Integer32 eoPowerOperState(10)
| +-- r-n Integer32 pmPowerOperState(11) | +-- r-n OwnerString eoPowerStateEnterReason(11)
| +-- r-n OwnerString pmPowerStateEnterReason(12)
| | | |
| | | |
+---pmPowerStateTable(2) +---eoPowerStateTable(2)
| +--pmPowerStateEntry(1) | +--eoPowerStateEntry(1)
| | [pmPowerIndex, | | [eoPowerIndex,
| | pmPowerStateSet, | | eoPowerStateIndex]
| | pmpowerStateIndex] | |
| +-- --- Integer32 pmPowerStateIndex(1) | +-- --- IANAPowerStateSet eoPowerStateIndex(1)
| +-- r-n Interger32 pmPowerStateMaxPower (2) | +-- r-n Interger32 eoPowerStateMaxPower (2)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| pmPowerStatePowerUnitMultiplier (3) | eoPowerStatePowerUnitMultiplier (3)
| +-- r-n TimeTicks pmPowerStateTotalTime(4) | +-- r-n TimeTicks eoPowerStateTotalTime(4)
| +-- r-n Counter64 pmPowerStateEnterCount(5) | +-- r-n Counter64 eoPowerStateEnterCount(5)
| |
+pmEnergyParametersTable(1) +eoEnergyParametersTable(1)
+---pmEnergyParametersEntry(1) [pmPowerIndex] +---eoEnergyParametersEntry(1) [eoPowerIndex]
| |
| +-- r-n TimeInterval | +-- r-n TimeInterval
| pmEnergyParametersIntervalLength (1) | eoEnergyParametersIntervalLength (1)
| +-- r-n Integer32 | +-- r-n Integer32
| pmEnergyParametersIntervalNumber (2) | eoEnergyParametersIntervalNumber (2)
| +-- r-n Integer32 | +-- r-n Integer32
| pmEnergyParametersIntervalMode (3) | eoEnergyParametersIntervalMode (3)
| +-- r-n TimeInterval | +-- r-n TimeInterval
| pmEnergyParametersIntervalWindow (4) | eoEnergyParametersIntervalWindow (4)
| +-- r-n Integer32 | +-- r-n Integer32
| pmEnergyParametersSampleRate (5) | eoEnergyParametersSampleRate (5)
| +-- r-n RowStatus pmEnergyParametersStatus (6) | +-- r-n RowStatus eoEnergyParametersStatus (6)
| |
+pmEnergyTable(1) +eoEnergyTable(1)
+---pmEnergyEntry(1) [pmPowerIndex] +---eoEnergyEntry(1) [eoPowerIndex]
| |
| +-- r-n TimeInterval pmEnergyIntervalStartTime (1) | +-- r-n TimeInterval eoEnergyIntervalStartTime (1)
| +-- r-n Integer32 pmEnergyIntervalEnergyUsed (2) | +-- r-n Integer32 eoEnergyIntervalEnergyConsumed (2)
| +-- r-n Integer32 eoEnergyIntervalEnergyProduced (3)
| +-- r-n Integer32 eoEnergyIntervalEnergyNet (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| pmEnergyIntervalEnergyUnitMultiplier (3) | eoEnergyIntervalEnergyUnitMultiplier (5)
| +-- r-n Integer32 pmEnergyIntervalMax (4) | +-- r-n Integer32 eoEnergyIntervalEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyIntervalMaxConsumed (7)
| +-- r-n Integer32 eoEnergyIntervalMaxProduced (8)
| +-- r-n TimeTicks | +-- r-n TimeTicks
| pmEnergyIntervalDiscontinuityTime(5) | eoEnergyIntervalDiscontinuityTime(9)
| +-- r-n RowStatus pmEnergyParametersStatus (6) | +-- r-n RowStatus eoEnergyParametersStatus (10)
The powerQualityMIB consists of four tables. PmACPwrQualityTable The powerQualityMIB consists of four tables. eoACPwrQualityTable
is indexed by pmPowerIndex. PmACPwrQualityPhaseTable is indexed is indexed by eoPowerIndex. eoACPwrQualityPhaseTable is indexed
by pmPowerIndex and pmPhaseIndex. pmACPwrQualityWyePhaseTable by eoPowerIndex and eoPhaseIndex. eoACPwrQualityWyePhaseTable
and pmACPwrQualityDelPhaseTable are indexed by pmPowerIndex and and eoACPwrQualityDelPhaseTable are indexed by eoPowerIndex and
pmPhaseIndex. eoPhaseIndex.
pmPowerTable(1) eoPowerTable(1)
| |
+---PmACPwrQualityEntry (1) [pmPowerIndex] +---eoACPwrQualityEntry (1) [eoPowerIndex]
| | | |
| | | |
| +----- INTEGER pmACPwrQualityConfiguration (1) | +----- INTEGER eoACPwrQualityConfiguration (1)
| +-- r-n Interger32 pmACPwrQualityAvgVoltage (2) | +-- r-n Interger32 eoACPwrQualityAvgVoltage (2)
| +-- r-n Integer32 pmACPwrQualityAvgCurrent (3) | +-- r-n Integer32 eoACPwrQualityAvgCurrent (3)
| +-- r-n Integer32 pmACPwrQualityFrequency (4) | +-- r-n Integer32 eoACPwrQualityFrequency (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| pmACPwrQualityPowerUnitMultiplier (5) | eoACPwrQualityPowerUnitMultiplier (5)
| +-- r-n Integer32 pmACPwrQualityPowerAccuracy (6) | +-- r-n Integer32 eoACPwrQualityPowerAccuracy (6)
| +-- r-n Interger32 pmACPwrQualityTotalActivePower (7) | +-- r-n Interger32 eoACPwrQualityTotalActivePower (7)
| +-- r-n Integer32 | +-- r-n Integer32
| pmACPwrQualityTotalReactivePower (8) | eoACPwrQualityTotalReactivePower (8)
| +-- r-n Integer32 pmACPwrQualityTotalApparentPower (9) | +-- r-n Integer32 eoACPwrQualityTotalApparentPower (9)
| +-- r-n Integer32 pmACPwrQualityTotalPowerFactor(10) | +-- r-n Integer32 eoACPwrQualityTotalPowerFactor(10)
| +-- r-n Integer32 pmACPwrQualityThdAmpheres (11) | +-- r-n Integer32 eoACPwrQualityThdAmpheres (11)
| |
+pmACPwrQualityPhaseTable (1) +eoACPwrQualityPhaseTable (1)
+---PmACPwrQualityPhaseEntry(1)[pmPowerIndex, +---EoACPwrQualityPhaseEntry(1)[eoPowerIndex,
| | pmPhaseIndex] | | eoPhaseIndex]
| | | |
| +-- r-n Integer32 pmPhaseIndex (1) | +-- r-n Integer32 eoPhaseIndex (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhaseAvgCurrent (2) | | eoACPwrQualityPhaseAvgCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhaseActivePower (3) | | eoACPwrQualityPhaseActivePower (3)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhaseReactivePower (4) | | eoACPwrQualityPhaseReactivePower (4)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhaseApparentPower (5) | | eoACPwrQualityPhaseApparentPower (5)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhasePowerFactor (6) | | eoACPwrQualityPhasePowerFactor (6)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityPhaseImpedance (7) | | eoACPwrQualityPhaseImpedance (7)
| | | |
+pmACPwrQualityDelPhaseTable (1) +eoACPwrQualityDelPhaseTable (1)
+-- pmACPwrQualityDelPhaseEntry(1) +-- eoACPwrQualityDelPhaseEntry(1)
| | [pmPowerIndex, | | [eoPowerIndex,
| | pmPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityDelPhaseToNextPhaseVoltage (1) | | eoACPwrQualityDelPhaseToNextPhaseVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityDelThdPhaseToNextPhaseVoltage (2) | | eoACPwrQualityDelThdPhaseToNextPhaseVoltage (2)
| +-- r-n Integer32 pmACPwrQualityDelThdCurrent (3) | +-- r-n Integer32 eoACPwrQualityDelThdCurrent (3)
| | | |
+pmACPwrQualityWyePhaseTable (1) +eoACPwrQualityWyePhaseTable (1)
+-- pmACPwrQualityWyePhaseEntry (1) +-- eoACPwrQualityWyePhaseEntry (1)
| | [pmPowerIndex, | | [eoPowerIndex,
| | pmPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityWyePhaseToNeutralVoltage (1) | | eoACPwrQualityWyePhaseToNeutralVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityWyePhaseCurrent (2) | | eoACPwrQualityWyePhaseCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | pmACPwrQualityWyeThdPhaseToNeutralVoltage (3) | | eoACPwrQualityWyeThdPhaseToNeutralVoltage (3)
| . | .
A UML representation of the MIB objects in the two MIB modules A UML representation of the MIB objects in the two MIB modules
are powerMonitorMIB and powerQualityMIB are presented. are energyObjectMib and powerQualityMIB are presented.
+--------------------------+ +--------------------------+
| PowerMonitor ID | | Energy Object ID |
| | | |
| Energy-aware-MIB (*) | | Energy-aware-MIB (*) |
| | +---------------------------+ | | +---------------------------+
| | | | | | | |
| pmPowerIndex | | PowerMonitor Attributes | | eoPowerIndex | |_ EnergyObject Attributes |
| pmPowerStateSetIndex | | | | | | |
+--------------------------+ | pmPowerNamePlate | +--------------------------+ | eoPowerNamePlate |
| | | pmPowerMeasurementCaliber | | | | eoPowerMeasurementCaliber |
| | | pmPowerOrigin | | | | eoPowerOrigin |
| | | pmPowerCurrentType | | | | eoPowerCurrentType |
| | +---------------------------+ | | +---------------------------+
| | | | | |
| | | | | |
v | v v | v
+-----------------------------------------+ +-----------------------------------------+
| PowerMonitor Measurement | | EnergyObjec Measurement |
| | | |
| pmPower | | eoPower |
| pmPowerUnitMultiplier | | eoPowerUnitMultiplier |
| pmPowerAccuracy | | eoPowerAccuracy |
+-----------------------------------------+ +-----------------------------------------+
^ | ^ ^ | ^
| | | | | |
+-------------------------+ | | +-------------------------+ | |
| PowerMonitor State | | +------------------------+ | EnergyObject State | | +------------------------+
| | | | PowerMonitor State | | | | | EnergyObject State |
| pmPowerAdminState | | | Statistics | | eoPowerAdminState | | | Statistics |
| pmPowerOperState | | | | | eoPowerOperState | | | |
| pmPowerStateEnterReason | | | pmPowerStateMaxPower | | eoPowerStateEnterReason | | | eoPowerStateMaxPower |
+-------------------------+ | | pmPowerStateTotalTime | +-------------------------+ | | eoPowerStateTotalTime |
| | pmPowerStateEnterCount | | | eoPowerStateEnterCount |
| +------------------------+ | +------------------------+
| |
| |
| |
| |
Figure 1:UML diagram for powerMonitor MIB Figure 1:UML diagram for powerMonitor MIB
(*) Link with the ENERGY-AWARE-MIB (*) Link with the ENERGY-AWARE-MIB
| |
| |
| |
V V
+------------------------------------+ +----------------------------------------+
| Energy Table | | Energy Table |
| | | |
| pmEnergyIntervalStartTime | | eoEnergyIntervalStartTime |
| pmEnergyIntervalEnergyUsed | | eoEnergyIntervalEnergyConsumed |
| pmEnergyIntervalMax | | eoEnergyIntervalEnergyProduced |
| pmEnergyIntervalDiscontinuityTime | | eoEnergyIntervalEnergyNet |
+------------------------------------+ | eoEnergyIntervalEnergyUnitMultiplier |
| eoEnergyIntervalEnergyAccuracy |
| eoEnergyIntervalMaxConsumed |
| eoEnergyIntervalMaxProduced |
| eoEnergyIntervalDiscontinuityTime |
+----------------------------------------+
+--------------------------+ +--------------------------+
| PowerMonitor ID | | EnergyObject ID |
| | | |
| Energy-aware-MIB (*) | | Energy-aware-MIB (*) |
| | | |
| pmPowerIndex | | eoPowerIndex |
| pmPowerStateSetIndex | | |
+--------------------------+ +--------------------------+
| |
v v
+-------------------------------------+ +-------------------------------------+
| Power Quality | | Power Quality |
| | | |
| pmACPwrQualityConfiguration | | eoACPwrQualityConfiguration |
| pmACPwrQualityAvgVoltage | | eoACPwrQualityAvgVoltage |
| pmACPwrQualityAvgCurrent | eoACPwrQualityAvgCurrent
| pmACPwrQualityFrequency | | eoACPwrQualityFrequency |
| pmACPwrQualityPowerUnitMultiplier | | eoACPwrQualityPowerUnitMultiplier |
| pmACPwrQualityPowerAccuracy | | eoACPwrQualityPowerAccuracy |
| pmACPwrQualityTotalActivePower | | eoACPwrQualityTotalActivePower |
| pmACPwrQualityTotalReactivePower | | eoACPwrQualityTotalReactivePower |
| pmACPwrQualityTotalApparentPower | | eoACPwrQualityTotalApparentPower |
| pmACPwrQualityTotalPowerFactor | | eoACPwrQualityTotalPowerFactor |
| pmACPwrQualityThdAmpheres | | eoACPwrQualityThdAmpheres |
+-------------------------------------+ ^ +-------------------------------------+ ^
^ ^ | ^ ^ |
| | ------- | | -------
| ---- | | ---- |
| | | | | |
| | | | | |
+-------------------------------------+ | | +-------------------------------------+ | |
| Power Phase Quality | | | | Power Phase Quality | | |
| | | | | | | |
| pmPhaseIndex | | | | eoPhaseIndex | | |
| pmACPwrQualityPhaseAvgCurrent | | | | eoACPwrQualityPhaseAvgCurrent | | |
| pmACPwrQualityAvgCurrent | | | | eoACPwrQualityAvgCurrent | | |
| pmACPwrQualityFrequency | | | | eoACPwrQualityFrequency | | |
| pmACPwrQualityPowerUnitMultiplier | | | | eoACPwrQualityPowerUnitMultiplier | | |
| pmACPwrQualityPowerAccuracy | | | | eoACPwrQualityPowerAccuracy | | |
| pmACPwrQualityPhaseActivePower | | | | eoACPwrQualityPhaseActivePower | | |
| pmACPwrQualityPhaseReactivePower | | | | eoACPwrQualityPhaseReactivePower | | |
| pmACPwrQualityPhaselApparentPower | | | | eoACPwrQualityPhaselApparentPower | | |
| pmACPwrQualityPhaseImpedance | | | | eoACPwrQualityPhaseImpedance | | |
+-------------------------------------+ | | +-------------------------------------+ | |
| | | |
| | | |
+---------------------------------------------+ | +---------------------------------------------+ |
| Power Quality DEL Configuration | | | Power Quality DEL Configuration | |
| | | | | |
| pmACPwrQualityDelPhaseToNextPhaseVoltage | | | eoACPwrQualityDelPhaseToNextPhaseVoltage | |
| pmACPwrQualityDelThdPhaseToNextPhaseVoltage | | | eoACPwrQualityDelThdPhaseToNextPhaseVoltage | |
| pmACPwrQualityDelThdCurrent | | | eoACPwrQualityDelThdCurrent | |
+---------------------------------------------+ | +---------------------------------------------+ |
| |
| |
+---------------------------------------------+ +---------------------------------------------+
| Power Quality WYE Configuration | | Power Quality WYE Configuration |
| | | |
| pmACPwrQualityWyePhaseToNeutralVoltage | | eoACPwrQualityWyePhaseToNeutralVoltage |
| pmACPwrQualityWyePhaseCurrent | | eoACPwrQualityWyePhaseCurrent |
| pmACPwrQualityWyeThdPhaseToNeutralVoltage | | eoACPwrQualityWyeThdPhaseToNeutralVoltage |
+---------------------------------------------+ +---------------------------------------------+
Figure 2: UML diagram for the powerQualityMIB Figure 2: UML diagram for the powerQualityMIB
5.1. Power Monitor Information 5.1. Energy Object Information
Refer to the "Power Monitor Information" section in [EMAN- Refer to the "Energy Object Information" section in [EMAN-
FRAMEWORK] for background information. An energy aware device FRAMEWORK] for background information. An energy aware device
is considered an instance of a Power Monitor as defined in the is considered as an instance of a Energy Object as defined in
[EMAN-FRAMEWORK]. the [EMAN-FRAMEWORK].
The Power Monitor identity information is specified in the MIB The Energy Object identity information is specified in the MIB
ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the
pmTable.In this table, every Power Monitor SHOULD have a eoTable. In this table, every Energy Object SHOULD have a
printable name pmName, and MUST HAVE a unique Power Monitor printable name eoName, and MUST HAVE a unique Energy Object
index pmIndex. The ENERGY-AWARE-MIB module returns the index eoIndex. The ENERGY-AWARE-MIB module returns the
relationship (parent/child) between Power Monitors. relationship (parent/child) between Energy Objects .
EDITOR'S NOTE: this last sentence will have to be updated with EDITOR'S NOTE: this last sentence will have to be updated with
terms such as Aggregator, Proxy, etc... when the [EMAN- terms such as Aggregator, Proxy, etc... when the [EMAN-
FRAMEWORK] will stabilize. FRAMEWORK] will stabilize.
5.2. Power State 5.2. Power State
Refer to the "Power Monitor States" section in [EMAN-FRAMEWORK] Refer to the "Power States" section in [EMAN-FRAMEWORK] for
for background information. background information.
A Power Monitor may have energy conservation modes called Power An Energy Object may have energy conservation modes called Power
States. Between the ON and OFF states of a device, there can be States. Between the ON and OFF states of a device, there can be
several intermediate energy saving modes. Those energy saving several intermediate energy saving modes. Those energy saving
modes are called as Power States. modes are called as Power States.
Power States, which represent universal states of power Power States, which represent universal states of power
management of a Power Monitor, are specified by the pmPowerState management of an Energy Object, are specified by the
MIB object. The actual Power State is specified by the eoPowerState MIB object. The actual Power State is specified by
pmPowerOperState MIB object, while the pmPowerAdminState MIB the eoPowerOperState MIB object, while the eoPowerAdminState MIB
object specifies the Power State requested for the Power object specifies the Power State requested for the Energy
Monitor. The difference between the values of pmPowerOperState Object. The difference between the values of eoPowerOperState
and pmPowerAdminState can be attributed that the Power Monitor and eoPowerAdminState can be attributed that the Energy Object
is busy transitioning from pmPowerAdminState into the is busy transitioning from eoPowerAdminState into the
pmPowerOperState, at which point it will update the content of eoPowerOperState, at which point it will update the content of
pmPowerOperState. In addition, the possible reason for change eoPowerOperState. In addition, the possible reason for change
in Power State is reported in pmPowerStateEnterReason. in Power State is reported in eoPowerStateEnterReason.
Regarding pmPowerStateEnterReason, management stations and Power Regarding eoPowerStateEnterReason, management stations and
Monitors should support any format of the owner string dictated Energy Objects should support any format of the owner string
by the local policy of the organization. It is suggested that dictated by the local policy of the organization. It is
this name contain at least the reason for the transition change, suggested that this name contain at least the reason for the
and one or more of the following: IP address, management station transition change, and one or more of the following: IP address,
name, network manager's name, location, or phone number. management station name, network manager's name, location, or
phone number.
The MIB objects pmPowerOperState, pmPowerAdminState , and The MIB objects eoPowerOperState, eoPowerAdminState , and
pmPowerStateEnterReason are contained in the pmPowerTable MIB eoPowerStateEnterReason are contained in the eoPowerTable MIB
table. table.
The pmPowerStateTable table enumerates the maximum power usage The eoPowerStateTable table enumerates the maximum power usage
in watts, for every single supported Power State of each Power in watts, for every single supported Power State of each Power
State Set supported by the Power Monitor In addition, State Set supported by the Energy Object. In addition,
PowerStateTable provides additional statistics: PowerStateTable provides additional statistics:
pmPowerStateEnterCount, the number of times an entity has eoPowerStateEnterCount, the number of times an entity has
visited a particular Power State, and pmPowerStateTotalTime, the visited a particular Power State, and eoPowerStateTotalTime, the
total time spent in a particular Power State of a Power Monitor. total time spent in a particular Power State of an Energy
Object.
5.2.1. Power State Set 5.2.1. Power State Set
There are several standards and implementations of Power State There are several standards and implementations of Power State
Sets. A Power Monitor can support one or multiple Power State Sets. A Energy Object can support one or multiple Power State
Set implementation(s) concurrently. Set implementation(s) concurrently.
There are currently three Power State Sets advocated: There are currently three Power State Sets advocated:
Reserved(0) unknown(0)
IEEE1621(1) - [IEEE1621] IEEE1621(256) - [IEEE1621]
DMTF(2) - [DMTF] DMTF(512) - [DMTF]
EMAN(3) - [EMAN-MONITORING-MIB] EMAN(1024) - [EMAN-MONITORING-MIB]
The respective specific states related to each Power State Set The respective specific states related to each Power State Set
are specified in the following sections. are specified in the following sections. The guidelines for
addition of new Power State Sets have been specified in the IANA
Considerations Section.
5.2.2. IEEE1621 Power State Set 5.2.2. IEEE1621 Power State Set
The IEEE1621 Power State Set [IEEE1621] consists of 3 The IEEE1621 Power State Set [IEEE1621] consists of 3
rudimentary states : on, off or sleep. rudimentary states : on, off or sleep.
on(0) - The device is fully On and all features of the on(0) - The device is fully On and all features of the
device are in working mode. device are in working mode.
off(1) - The device is mechanically switched off and does off(1) - The device is mechanically switched off and does
not consume energy. not consume energy.
sleep(2) - The device is in a power saving mode, and some sleep(2) - The device is in a power saving mode, and some
features may not be available immediately. features may not be available immediately.
The Textual Convention IANAPowerStateSet provides the proposed
numbering of the Power States within the IEEE1621 Power State
Set.
5.2.3. DMTF Power State Set 5.2.3. DMTF Power State Set
DMTF [DMTF] standards organization has defined a power profile DMTF [DMTF] standards organization has defined a power profile
standard based on the CIM (Common Information Model) model that standard based on the CIM (Common Information Model) model that
consists of 15 power states ON (2), SleepLight (3), SleepDeep consists of 15 power states ON (2), SleepLight (3), SleepDeep
(4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off- (4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off-
Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10), Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10),
Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard
Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off- Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off-
Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF
skipping to change at page 14, line 45 skipping to change at page 15, line 15
| Off-Hard Graceful (13) | G3 | | Off-Hard Graceful (13) | G3 |
--------------------------------------------------- ---------------------------------------------------
| MasterBus Reset Graceful (14) | G2-S5 | | MasterBus Reset Graceful (14) | G2-S5 |
--------------------------------------------------- ---------------------------------------------------
| Power Cycle off-soft Graceful (15)| G2-S5 | | Power Cycle off-soft Graceful (15)| G2-S5 |
--------------------------------------------------- ---------------------------------------------------
| Power Cycle off-hard Graceful (16)| G3 | | Power Cycle off-hard Graceful (16)| G3 |
--------------------------------------------------- ---------------------------------------------------
Figure 3: DMTF and ACPI Powe State Set Mapping Figure 3: DMTF and ACPI Powe State Set Mapping
The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the DMTF Power State Set.
5.2.4. EMAN Power State Set 5.2.4. EMAN Power State Set
The EMAN Power State Set represents an attempt for a uniform The EMAN Power State Set represents an attempt for a uniform
standard approach to model the different levels of power standard approach to model the different levels of power
consumption of a device. The EMAN Power States are an expansion consumption of a device. The EMAN Power States are an expansion
of the basic Power States as defined in IEEE1621 that also of the basic Power States as defined in IEEE1621 that also
incorporate the Power States defined in ACPI and DMTF. incorporate the Power States defined in ACPI and DMTF.
Therefore, in addition to the non-operational states as defined Therefore, in addition to the non-operational states as defined
in ACPI and DMTF standards, several intermediate operational in ACPI and DMTF standards, several intermediate operational
states have been defined. states have been defined.
skipping to change at page 15, line 20 skipping to change at page 15, line 40
and off. The expanded list of Power States are divided into six and off. The expanded list of Power States are divided into six
operational states, and six non-operational states. The lowest operational states, and six non-operational states. The lowest
non-operational state is 1 and the highest is 6. Each non- non-operational state is 1 and the highest is 6. Each non-
operational state corresponds to an ACPI state [ACPI] operational state corresponds to an ACPI state [ACPI]
corresponding to Global and System states between G3 (hard-off) corresponding to Global and System states between G3 (hard-off)
and G1 (sleeping). For Each operational state represent a and G1 (sleeping). For Each operational state represent a
performance state, and may be mapped to ACPI states P0 (maximum performance state, and may be mapped to ACPI states P0 (maximum
performance power) through P5 (minimum performance and minimum performance power) through P5 (minimum performance and minimum
power). power).
An Power Monitor may have fewer Power States than twelve and An Energy Object may have fewer Power States than twelve and
would then map several policy states to the same power state. would then map several policy states to the same power state.
Power Monitor with more than twelve states, would choose which Energy Object with more than twelve states, would choose which
twelve to represent as power policy states. twelve to represent as power policy states.
In each of the non-operational states (from mechoff(1) to In each of the non-operational states (from mechoff(1) to
ready(6)), the Power State preceding it is expected to have a ready(6)), the Power State preceding it is expected to have a
lower power consumption and a longer delay in returning to an lower power consumption and a longer delay in returning to an
operational state: operational state:
IEEE1621 Power(off): IEEE1621 Power(off):
mechoff(1) : An off state where no entity features are mechoff(1) : An off state where no entity features are
skipping to change at page 17, line 25 skipping to change at page 17, line 49
less than highMinus(11) usage. less than highMinus(11) usage.
highMinus(11): Indicates all entity features are highMinus(11): Indicates all entity features are
available and power usage is less available and power usage is less
than high(12). than high(12).
high(12) : Indicates all entity features are high(12) : Indicates all entity features are
available and the entity is consuming the available and the entity is consuming the
highest power. highest power.
5.3. Power Monitor Usage Information The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the EMAN Power State Set.
Refer to the "Power Monitor Usage Measurement" section in [EMAN- 5.3. Energy Object Usage Information
Refer to the "Energy Object Usage Measurement" section in [EMAN-
FRAMEWORK] for background information. FRAMEWORK] for background information.
For a Power Monitor, power usage is reported using pmPower. The For an Energy Object, power usage is reported using eoPower.
magnitude of measurement is based on the pmPowerUnitMultiplier The magnitude of measurement is based on the
MIB variable, based on the UnitMultiplier Textual Convention eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
(TC). Power measurement magnitude should conform to the IEC Textual Convention (TC). Power measurement magnitude should
62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22] conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
definition of unit multiplier for the SI (System International) [IEC.62053-22] definition of unit multiplier for the SI (System
units of measure. Measured values are represented in SI units International) units of measure. Measured values are
obtained by BaseValue * 10 raised to the power of the scale. represented in SI units obtained by BaseValue * 10 raised to the
power of the scale.
For example, if current power usage of a Power Monitor is 3, it For example, if current power usage of an Energy Object is 3, it
could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of
pmPowerUnitMultiplier. Note that other measurements throughout eoPowerUnitMultiplier. Note that other measurements throughout
the two MIB modules in this document use the same mechanism, the two MIB modules in this document use the same mechanism,
including pmPowerStatePowerUnitMultiplier, including eoPowerStatePowerUnitMultiplier,
pmEnergyIntervalEnergyUnitMultiplier, and eoEnergyIntervalEnergyUnitMultiplier, and
pmACPwrQualityPowerUnitMultiplier. eoACPwrQualityPowerUnitMultiplier.
In addition to knowing the usage and magnitude, it is useful to In addition to knowing the usage and magnitude, it is useful to
know how a pmPower measurement was obtained. An NMS can use know how a eoPower measurement was obtained. An NMS can use
this to account for the accuracy and nature of the reading this to account for the accuracy and nature of the reading
between different implementations. For this pmPowerOrigin between different implementations. For this eoPowerOrigin
describes whether the measurements were made at the device describes whether the measurements were made at the device
itself or from a remote source. The pmPowerMeasurementCaliber itself or from a remote source. The eoPowerMeasurementCaliber
describes the method that was used to measure the power and can describes the method that was used to measure the power and can
distinguish actual or estimated values. There may be devices in distinguish actual or estimated values. There may be devices in
the network, which may not be able to measure or report power the network, which may not be able to measure or report power
consumption. For those devices, the object consumption. For those devices, the object
pmPowerMeasurementCaliber shall report that measurement eoPowerMeasurementCaliber shall report that measurement
mechanism is "unavailable" and the pmPower measurement shall be mechanism is "unavailable" and the eoPower measurement shall be
"0". "0".
The nameplate power rating of a Power Monitor is specified in The nameplate power rating of an Energy Object is specified in
pmPowerNameplate MIB object. eoPowerNameplate MIB object.
5.4. Optional Power Usage Quality 5.4. Optional Power Usage Quality
Refer to the "Optional Power Usage Quality" section in [EMAN- Refer to the "Optional Power Usage Quality" section in [EMAN-
FRAMEWORK] for background information. FRAMEWORK] for background information.
The optional powerQualityMIB MIB module can be implemented to The optional powerQualityMIB MIB module can be implemented to
further describe power usage quality measurement. The further describe power usage quality measurement. The
powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 powerQualityMIB MIB module adheres closely to the IEC 61850 7-2
standard to describe AC measurements. standard to describe AC measurements.
The powerQualityMIB MIB module contains a primary table, the The powerQualityMIB MIB module contains a primary table, the
pmACPwrQualityTable table, that defines power quality eoACPwrQualityTable table, that defines power quality
measurements for supported pmIndex entities, as a sparse measurements for supported eoPowerIndex entities, as a sparse
extension of the pmPowerTable (with pmPowerIndex as primary extension of the eoPowerTable (with eoPowerIndex as primary
index). This pmACPwrQualityTable table contains such index). This eoACPwrQualityTable table contains such
information as the configuration (single phase, DEL 3 phases, information as the configuration (single phase, DEL 3 phases,
WYE 3 phases), voltage, frequency, power accuracy, total WYE 3 phases), voltage, frequency, power accuracy, total
active/reactive power/apparent power, amperage, and voltage. active/reactive power/apparent power, amperage, and voltage.
In case of 3-phase power, the pmACPwrQualityPhaseTable In case of 3-phase power, the eoACPwrQualityPhaseTable
additional table is populated with power quality measurements additional table is populated with power quality measurements
per phase (so double indexed by the pmPowerIndex and per phase (so double indexed by the eoPowerIndex and
pmPhaseIndex). This table, which describes attributes common to eoPhaseIndex). This table, which describes attributes common to
both WYE and DEL configurations, contains the average current, both WYE and DEL configurations, contains the average current,
active/reactive/apparent power, power factor, and impedance. active/reactive/apparent power, power factor, and impedance.
In case of 3-phase power with a DEL configuration, the In case of 3-phase power with a DEL configuration, the
pmACPwrQualityDelPhaseTable table describes the phase-to-phase eoACPwrQualityDelPhaseTable table describes the phase-to-phase
power quality measurements, i.e., voltage and current. power quality measurements, i.e., voltage and current.
In case of 3-phase power with a Wye configuration, the In case of 3-phase power with a Wye configuration, the
pmACPwrQualityWyePhaseTable table describes the phase-to-neutral eoACPwrQualityWyePhaseTable table describes the phase-to-neutral
power quality measurements, i.e., voltage and current. power quality measurements, i.e., voltage and current.
5.5. Optional Energy Measurement 5.5. Optional Energy Measurement
Refer to the "Optional Energy and demand Measurement" section in Refer to the "Optional Energy and demand Measurement" section in
[EMAN-FRAMEWORK] for the definition and terminology information. [EMAN-FRAMEWORK] for the definition and terminology information.
It is relevant to measure energy when there are actual power It is relevant to measure energy when there are actual power
measurements from a Power Monitor, and not when the power measurements from an Energy Object, and not when the power
measurement is assumed or predicted as specified in the measurement is assumed or predicted as specified in the
description clause of the object pmPowerMeasurementCaliber. description clause of the object eoPowerMeasurementCaliber.
Two tables are introduced to characterize energy measurement of Two tables are introduced to characterize energy measurement of
a Power Monitor: pmEnergyTable and pmEnergyParametersTable. an Energy Object: eoEnergyTable and eoEnergyParametersTable.
Both energy and demand information can be represented via the Both energy and demand information can be represented via the
pmEnergyTable. Energy information will be an accumulation with eoEnergyTable. Energy information will be an accumulation with
no interval. Demand information can be represented as an no interval. Demand information can be represented as an
average accumulation per interval of time. average accumulation per interval of time.
The pmEnergyParametersTable consists of the parameters defining The eoEnergyParametersTable consists of the parameters defining
the duration of measurement intervals in seconds, the duration of measurement intervals in seconds,
(pmEnergyParametersIntervalLength), the number of successive (eoEnergyParametersIntervalLength), the number of successive
intervals to be stored in the pmEnergyTable, intervals to be stored in the eoEnergyTable,
(pmEnergyParametersIntervalNumber), the type of measurement (eoEnergyParametersIntervalNumber), the type of measurement
technique (pmEnergyParametersIntervalMode), and a sample rate technique (eoEnergyParametersIntervalMode), and a sample rate
used to calculate the average (pmEnergyParametersSampleRate). used to calculate the average (eoEnergyParametersSampleRate).
Judicious choice of the sampling rate will ensure accurate Judicious choice of the sampling rate will ensure accurate
measurement of energy while not imposing an excessive polling measurement of energy while not imposing an excessive polling
burden. burden.
There are three pmEnergyParametersIntervalMode types used for There are three eoEnergyParametersIntervalMode types used for
energy measurement collection: period, sliding, and total. The energy measurement collection: period, sliding, and total. The
choices of the the three different modes of collection are based choices of the the three different modes of collection are based
on IEC standard 61850-7-4. Note that multiple on IEC standard 61850-7-4. Note that multiple
pmEnergyParametersIntervalMode types MAY be configured eoEnergyParametersIntervalMode types MAY be configured
simultaneously. simultaneously.
These three pmEnergyParametersIntervalMode types are illustrated These three eoEnergyParametersIntervalMode types are illustrated
by the following three figures, for which: by the following three figures, for which:
- The horizontal axis represents the current time, with the - The horizontal axis represents the current time, with the
symbol <--- L ---> expressing the symbol <--- L ---> expressing the
pmEnergyParametersIntervalLength, and the eoEnergyParametersIntervalLength, and the
pmEnergyIntervalStartTime is represented by S1, S2, S3, S4, ..., eoEnergyIntervalStartTime is represented by S1, S2, S3, S4, ...,
Sx where x is the value of pmEnergyParametersIntervalNumber. Sx where x is the value of eoEnergyParametersIntervalNumber.
- The vertical axis represents the time interval of sampling and - The vertical axis represents the time interval of sampling and
the value of pmEnergyIntervalEnergyUsed can be obtained at the the value of eoEnergyIntervalEnergyUsed can be obtained at the
end of the sampling period. The symbol =========== denotes the end of the sampling period. The symbol =========== denotes the
duration of the sampling period. duration of the sampling period.
| | | =========== | | | | =========== |
|============ | | | |============ | | |
| | | | | | | |
| |============ | | | |============ | |
| | | | | | | |
| <--- L ---> | <--- L ---> | <--- L ---> | | <--- L ---> | <--- L ---> | <--- L ---> |
| | | | | | | |
S1 S2 S3 S4 S1 S2 S3 S4
Figure 4 : Period pmEnergyParametersIntervalMode Figure 4 : Period eoEnergyParametersIntervalMode
A pmEnergyParametersIntervalMode type of 'period' specifies non- A eoEnergyParametersIntervalMode type of 'period' specifies non-
overlapping periodic measurements. Therefore, the next overlapping periodic measurements. Therefore, the next
pmEnergyIntervalStartTime is equal to the previous eoEnergyIntervalStartTime is equal to the previous
pmEnergyIntervalStartTime plus pmEnergyParametersIntervalLength. eoEnergyIntervalStartTime plus eoEnergyParametersIntervalLength.
S2=S1+L; S3=S2+L, ... S2=S1+L; S3=S2+L, ...
|============ | |============ |
| | | |
| <--- L ---> | | <--- L ---> |
| | | |
| |============ | | |============ |
| | | | | |
| | <--- L ---> | | | <--- L ---> |
| | | | | |
skipping to change at page 21, line 5 skipping to change at page 21, line 33
| | | | | | | |
| | | | | | | |
S2 | | | S2 | | |
| | | | | |
| | | | | |
S3 | | S3 | |
| | | |
| | | |
S4 S4
Figure 5 : Sliding pmEnergyParametersIntervalMode Figure 5 : Sliding eoEnergyParametersIntervalMode
A pmEnergyParametersIntervalMode type of 'sliding' specifies A eoEnergyParametersIntervalMode type of 'sliding' specifies
overlapping periodic measurements. overlapping periodic measurements.
| | | |
|========================= | |========================= |
| | | |
| | | |
| | | |
| <--- Total length ---> | | <--- Total length ---> |
| | | |
S1 S1
Figure 4 : Total pmEnergyParametersIntervalMode Figure 4 : Total eoEnergyParametersIntervalMode
A pmEnergyParametersIntervalMode 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
pmEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
pmEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The pmEnergyParametersStatus 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 usage logging. The status of this variable is "active" when
all the objects in pmEnergyParametersTable are appropriate which all the objects in eoEnergyParametersTable are appropriate which
in turn indicates if pmEnergyTable entries exist or not. in turn indicates if eoEnergyTable entries exist or not.
The pmEnergyTable consists of energy measurements The eoEnergyTable consists of energy measurements in
inpmEnergyIntervalEnergyUsed , the units of the measured energy eoEnergyIntervalEnergyUsed , the units of the measured energy
pmEnergyIntervalEnergyUnitMultiplier, and the maximum observed eoEnergyIntervalEnergyUnitMultiplier, and the maximum observed
energy within a window - pmEnergyIntervalMax. energy within a window - eoEnergyIntervalMax.
Measurements of the total energy consumed by a Power Monitor may Measurements of the total energy consumed by an Energy Object
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 pmEnergyIntervalDiscontinuityTime is provided for the object eoEnergyIntervalDiscontinuityTime is provided for
indicating the time of the last interruption of total energy indicating the time of the last interruption of total energy
measurement. pmEnergyIntervalDiscontinuityTime shall indicate measurement. eoEnergyIntervalDiscontinuityTime shall indicate
the sysUpTime [RFC3418] when the device was reset. the sysUpTime [RFC3418] when the device was reset.
The following example illustrates the pmEnergyTable and The following example illustrates the eoEnergyTable and
pmEnergyParametersTable: 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.
pmEnergyParametersIntervalLength 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
(pmEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Power Monitor for measurement of power usage internal to the Energy Object for measurement of power usage
(pmEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Power Monitor as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
pmEnergyParametersStatus is set to active (value 1) to indicate eoEnergyParametersStatus is set to active (value 1) to indicate
that the Power Monitor should start monitoring the usage per the that the Energy Object should start monitoring the usage per the
pmEnergyTable. eoEnergyTable.
The indices in the pmEnergyTable are pmPowerIndex, which The indices for the eoEnergyTable are eoPowerIndex, which
identifies the Power Monitor, and pmEnergyIntervalStartTime, identifies the Energy Object, and eoEnergyIntervalStartTime,
which denotes the start time of the energy measurement interval which denotes the start time of the energy measurement interval
based on sysUpTime [RFC3418]. The value of based on sysUpTime [RFC3418]. The value of
pmEnergyIntervalEnergyUsed is the measured energy consumption eoEnergyIntervalEnergyUsed is the measured energy consumption
over the time interval specified over the time interval specified
(pmEnergyParametersIntervalLength) based on the Power Monitor (eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (pmEnergyParametersSampleRate). While internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the pmEnergyParametersIntervalLength and choosing the values for the eoEnergyParametersIntervalLength and
pmEnergyParametersSampleRate, 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 pmEnergyIntervalEnergyUsed. The units are derived calculate the eoEnergyIntervalEnergyUsed. The units are derived
from pmEnergyIntervalPowerUnitMultiplier. For example, from eoEnergyIntervalPowerUnitMultiplier. For example,
pmEnergyIntervalPowerUsed can be "100" with eoEnergyIntervalPowerUsed can be "100" with
pmEnergyIntervalPowerUnits equal to 0, the measured energy eoEnergyIntervalPowerUnits equal to 0, the measured energy
consumption of the Power Monitor is 100 watt-hours. The consumption of the Energy Object is 100 watt-hours. The
pmEnergyIntervalMax is the maximum energyobserved and that can eoEnergyIntervalMax is the maximum energy observed and that can
be "150 watt-hours". be "150 watt-hours".
The pmEnergyTable has a buffer to retain a certain number of The eoEnergyTable has a buffer to retain a certain number of
intervals, as defined by pmEnergyParametersIntervalNumber. If intervals, as defined by eoEnergyParametersIntervalNumber. If
the default value of "10" is kept, then the pmEnergyTable the default value of "10" is kept, then the eoEnergyTable
contains 10 energymeasurements, 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, i.e. a month, 3 months, or a year. period, i.e. a month, 3 months, or a year.
5.6. Fault Management 5.6. Fault Management
[EMAN-REQ] specifies requirements about Power States such as [EMAN-REQ] 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 "the total time spent in each state", "the number of transitions
to each state" etc. Some of these requirements are fulfilled to each state" etc. Some of these requirements are fulfilled
explicitly by MIB objects such as pmPowerOperState, explicitly by MIB objects such as eoPowerOperState,
pmPowerStateTotalTime and pmPowerStateEnterCount. 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.
pmPowerStateChange SNMP notification which is generated when the eoPowerStateChange SNMP notification which is generated when the
value(s) of pmPowerStateSet, pmPowerOperState, pmPowerAdminState value(s) of ,eoPowerStateIndex, eoPowerOperState,
have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
6.1. ENERGY-AWARE-MIB Module Implemented 6.1. ENERGY-AWARE-MIB Module Implemented
The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE-
MIB], if available, in order to discover all the Power Monitors MIB], if available, in order to discover all the Energy Objects
and the relationships between those (notion of Parent/Child). and the relationships between those (notion of Parent/Child).
In the ENERGY-AWARE-MIB module tables, the Power Monitors are
indexed by the pmIndex. In the ENERGY-AWARE-MIB module tables, the Energy Objects are
indexed by the eoIndex.
If an implementation of the ENERGY-AWARE-MIB module is available If an implementation of the ENERGY-AWARE-MIB module is available
in the local SNMP context, for the same Power Monitor, the in the local SNMP context, for the same Energy Object , the
pmIndex value (EMAN-AWARE-MIB) MUST be assigned to the eoIndex value (EMAN-AWARE-MIB) MUST be assigned to the
pmPowerIndex for The pmPowerIndex characterizes the Power eoPowerIndex. The eoPowerIndex characterizes the Energy Object
Monitor in the powerMonitorMIB and powerQualityMIB MIB modules in the energyObjectMib and powerQualityMIB MIB modules (this
(this document). document).
From there, the NMS must poll the pmPowerStateTable (specified From there, the NMS must poll the eoPowerStateTable (specified
in the powerMonitorMIB module in this document), which in the energyObjectMib 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 pmPowerStateTable table are indexed by the Power the entries in eoPowerStateTable table are indexed by the
Monitor (pmPowerIndex), by the Power State Set Energy Object (eoPowerIndex), by the Power State Set
(pmPowerStateSetIndex), and by the Power State (eoPowerStateIndex), the maximum power usage is discovered per
(pmPowerStateIndex), the maximum power usage is discovered per Energy Object, per Power State Set, and per Power Usage. In
Power Monitor, per Power State Set, and per Power Usage. In other words, polling the eoPowerStateTable allows the discovery
other words, polling the pmPowerStateTable allows the discovery
of each Power State within every Power State Set supported by of each Power State within every Power State Set supported by
the Power Monitor. the Energy Object.
If the Power Monitor is an Aggregator or a Proxy, the MIB module If the Energy Object is an Aggregator or a Proxy, the MIB
would be populated with the Power Monitor Parent and Children module would be populated with the Energy Object Parent and
information, which have their own Power Monitor index value Children information, which have their own Energy Object index
(pmPowerIndex). However, the parent/child relationship must be value (eoPowerIndex). However, the parent/child relationship
discovered thanks to the ENERGY-AWARE-MIB module. must be discovered thanks to the ENERGY-AWARE-MIB module.
Finally, the NMS can monitor the Power Quality thanks to the Finally, the NMS can monitor the Power Quality thanks to the
powerQualityMIB MIB module, which reuses the pmPowerIndex to powerQualityMIB MIB module, which reuses the eoPowerIndex to
index the Power Monitor. index the Energy Object.
6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB 6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB
Implemented Implemented
When the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] is not When the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] is not
implemented, the NMS must poll the ENTITY-MIB [RFC4133] in order implemented, the NMS must poll the ENTITY-MIB [RFC4133] in order
to discover some more information about the Power Monitors. to discover some more information about the Energy Objects.
Indeed, the index for the Power Monitors in the MIB modules Indeed, the index for the Energy Objects in the MIB modules
specified in this document is the pmPowerIndex, which specifies: specified in this document is the eoPowerIndex, which specifies:
"If there is no implementation of the ENERGY-AWARE-MIB module "If there is no implementation of the ENERGY-AWARE-MIB module
but one of the ENTITY MIB module is available in the local SNMP but one of the ENTITY MIB module is available in the local SNMP
context, then the same index of an entity MUST be chosen as context, then the same index of an entity MUST be chosen as
assigned to the entity by object entPhysicalIndex in the ENTITY assigned to the entity by object entPhysicalIndex in the ENTITY
MIB module." MIB module."
As the Section 6.1. , the NMS must then poll the As described in Section 6.1. the NMS must then poll the
pmPowerStateTable (specified in the powerMonitorMIB module in eoPowerStateTable (specified in the energyObjectMib module in
this document), indexed by the Power Monitor (pmPowerIndex that this document), indexed by the Energy Object (eoPowerIndex that
inherited the entPhysicalIndex value), by the Power State Set inherited the entPhysicalIndex value), by the Power State
(pmPowerStateSetIndex), and by the Power State (eoPowerStateIndex). Then the NMS has discovered every Power
(pmPowerStateIndex). Then the NMS has discovered every Power State within each Power State Set supported by the Energy
State within each Power State Set supported by the Power Object.
Monitor.
Note that, without the ENERGY-AWARE-MIB module, the Power Note that, without the ENERGY-AWARE-MIB module, the Energy
Monitor acts as an standalone device, i.e. the notion of Object acts as an standalone device, i.e. the notion of
parent/child can't be specified. parent/child can't be specified.
6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented 6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented
If neither the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] nor of If neither the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] nor of
the ENTITY MIB module [RFC4133] are available in the local SNMP the ENTITY MIB module [RFC4133] are available in the local SNMP
context, then this MIB module may choose identity values from a context, then this MIB module may choose identity values from a
further MIB module providing entity identities. further MIB module providing entity identities.
Note that, without the ENERGY-AWARE-MIB module, the Power Note that, without the ENERGY-AWARE-MIB module, the Energy
Monitor acts as an standalone device, i.e. the notion of Object acts as a standalone device, i.e. the notion of
parent/child can't be specified. parent/child can't be specified.
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 4133 [RFC4133] defines the ENTITY MIB module that lists the RFC 4133 [RFC4133] 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 [RFC4133]. While the focus entPhysicalIndex of the ENTITY MIB [RFC4133]. 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 equieoent indexed by the ENTITY MIB,
this MIB proposes a customized power scale for power measurement this MIB proposes a customized power scale for power measurement
and different power state states of networking equipment, and and different power state states of networking equipment, and
functionality to configure the power state states. functionality to configure the power state states.
When this MIB module is used to monitor the power usage of When this MIB module is used to monitor the power usage of
devices like routers and switches, the ENTITY MIB and ENTITY- devices like routers and switches, the ENTITY MIB and ENTITY-
SENSOR MIB SHOULD be implemented. In such cases, the Power SENSOR MIB SHOULD be implemented. In such cases, the Energy
Monitors are modeled by the entPhysicalIndex through the Objects are modeled by the entPhysicalIndex through the
pmPhysicalEntity MIB object specified in the pmTable in the entPhysicalEntity MIB object specified in the eoTable in the
ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB].
However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI
C12.x accuracy classes required for electricity (i.e., 1%, 2%, C12.x accuracy classes required for electricity (i.e., 1%, 2%,
0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 0.5% 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 pmPowerAccuracy MIB object models this accuracy. RFC3433. The eoPowerAccuracy MIB object models this accuracy.
Note that pmPowerUnitMultipler 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 Power Monitors that need to be monitored. A implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, monitoring typical example is a converged building gateway, monitoring
several other devices in the building, doing the proxy between several other devices in the building, doing the 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 pmPhysicalEntity value energy controller. In such cases, the eoPhysicalEntity value
contains the zero value, thanks to PhysicalIndexOrZero textual contains the zero value, thanks to PhysicalIndexOrZero textual
convention. convention.
The pmPowerIndex MIB object has been kept as the unique Power The eoPowerIndex MIB object has been kept as the unique index of
Monitor index. The pmPower is similar to entPhySensorValue the Energy Object. The eoPower is similar to entPhySensorValue
[RFC3433] and the pmPowerUnitMultipler is similar to [RFC3433] and the eoPowerUnitMultipler is similar to
entPhySensorScale. entPhySensorScale.
7.2. Link with the ENTITY-STATE MIB 7.2. Link with the ENTITY-STATE MIB
For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE For each entity in the ENTITY-MIB [RFC4133], 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,
skipping to change at page 26, line 45 skipping to change at page 27, line 29
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.
The RFC introduces a concept of a port group on a switch to The RFC introduces a concept of a port group on a switch to
define power monitoring and management policy and does not use define power monitoring and management policy and does not use
the entPhysicalIndex as the index. Indeed, the the entPhysicalIndex as the index. Indeed, the
pethMainPseConsumptionPower is indexed by the pethMainPseConsumptionPower is indexed by the
pethMainPseGroupIndex, which has no mapping with the pethMainPseGroupIndex, which has no mapping with the
entPhysicalIndex. entPhysicalIndex.
One cannot assume that the Power-over-Ethernet MIB is One cannot assume that the Power-over-Ethernet MIB is
implemented for all Power Monitors that need to be monitored. A implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, monitoring typical example is a converged building gateway, monitoring
several other devices in the building, doing the proxy between several other devices in the building, doing the 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 pmethPortIndex and energy controller. In such cases, the eoethPortIndex and
pmethPortGrpIndex values contain the zero value, thanks to new eoethPortGrpIndex values contain the zero value, thanks to new
PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero
conventions. conventions.
However, if the Power-over-Ethernet MIB [RFC3621] is supported, However, if the Power-over-Ethernet MIB [RFC3621] is supported,
the Power Monitor pmethPortIndex and pmethPortGrpIndex contain the Energy Object eoethPortIndex and eoethPortGrpIndex contain
the pethPsePortIndex and pethPsePortGroupIndex, respectively. the pethPsePortIndex and pethPsePortGroupIndex, respectively.
As a consequence, the pmPowerIndex MIB object has been kept as As a consequence, the eoIndex MIB object has been kept as the
the unique Power Monitor 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
skipping to change at page 28, line 12 skipping to change at page 28, line 44
- 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 Power Monitor Parent and this case, the UPS device itself is the Energy Object Parent and
any of the UPS meters or submeters are the Power Monitor any of the UPS meters or submeters are the Energy Object
Children. Children.
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
skipping to change at page 28, line 49 skipping to change at page 29, line 38
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
in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise
the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From
the Power and Energy Monitoring MIB, it is possible to identify the Power and Energy Monitoring MIB, it is possible to identify
the pethPsePortPowerPriority [RFC3621], thanks to the the pethPsePortPowerPriority [RFC3621], thanks to the
pmethPortIndex and pmethPortGrpIndex. eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
pmPowerOrigin in indicating if the power for an attached device eoPowerOrigin in indicating if the power for an attached device
is local or from a remote device. If the LLDP-MED MIB is is local or from a remote device. If the LLDP-MED MIB is
supported, the following mapping can be applied to the supported, the following mapping can be applied to the
pmPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and
local(3) can be mapped to remote(2) and self(1), respectively. local(3) can be mapped to remote(2) and self(1), respectively.
8. Implementation Scenario 8. Implementation Scenario
This section provides an illustrative example scenario for the This section provides an illustrative example scenario for the
implementation of the Power Monitor, including Power Monitor implementation of the Energy Object, including Energy Object
Parent and Power Monitor Child relationships. Parent and Energy Object Child relationships.
Example Scenario of a campus network: Switch with PoE Endpoints Example Scenario of a campus network: Switch with PoE Endpoints
with further connected Devices with further connected Devices
The campus network consists of switches that provide LAN The campus network consists of switches that provide LAN
connectivity. The switch with PoE ports is located in wiring connectivity. The switch with PoE ports is located in wiring
closet. PoE IP phones are connected to the switch. The IP closet. PoE IP phones are connected to the switch. The IP
phones draw power from the PoE ports of the switch. In phones draw power from the PoE ports of the switch. In
addition, a PC is daisy-chained from the IP phone for LAN addition, a PC is daisy-chained from the IP phone for LAN
connectivity. connectivity.
The IP phone consumes power from the PoE switch, while the PC The IP phone consumes power from the PoE switch, while the PC
consumes power from the wall outlet. consumes power from the wall outlet.
The switch has implementations of Entity MIB [RFC4133] and The switch has implementations of Entity MIB [RFC4133] and
energy-aware MIB [EMAN-AWARE-MIB] while the PC does not have energy-aware MIB [EMAN-AWARE-MIB] while the PC does not have
implementation of the Entity MIB, but has an implementation of implementation of the Entity MIB, but has an implementation of
energy-aware MIB. The switch has the following attributes, energy-aware MIB. The switch has the following attributes,
pmPowerIndex "1", pmPhysicalEntity "2", and pmPowerMonitorId eoPowerIndex "1", eoPhysicalEntity "2", and eoUUID "UUID 1000".
"UUID 1000". The power usage of the switch is "440 Watts". The The power usage of the switch is "440 Watts". The switch does
switch does not have a Power Monitor Parent. not have an Energy Object Parent.
The PoE switch port has the following attributes: The switch The PoE switch port has the following attributes: The switch
port has pmPowerIndex "3", pmPhysicalEntity is "12" and port has eoPowerIndex "3", eoPhysicalEntity is "12" and eoUUID
pmPowerMonitorId is "UUID 1000:3". The power metered at the POE is "UUID 1000:3". The power metered at the POE switch port is
switch port is "12 watts". In this example, the POE switch port "12 watts". In this example, the POE switch port has the switch
has the switch as the Power Monitor Parent, with its pmParentID as the Energy Object Parent, with its eoParentID of "1000".
of "1000".
The attributes of the PC are given below. The PC does not The attributes of the PC are given below. The PC does not
implementation of Entity MIB, and thus does not have implementation of Entity MIB, and thus does not have
pmPhysicalEntity. The pmPowerIndex (pmPIndex) of the PC is eoPhysicalEntity. The eoPowerIndex (eoIndex) of the PC is "57",
"57", the pmPowerMonitorId is "UUID 1000:57 ". The PC has a the eoUUID is "UUID 1000:57 ". The PC has an Energy Object
Power Monitor Parent, i.e. the switch port whose Parent, i.e. the switch port whose eoUUID is "UUID 1000:3". The
pmPowerMonitorId is "UUID 1000:3". The power usage of the PC is power usage of the PC is "120 Watts" and is communicated to the
"120 Watts" and is communicated to the switch port. switch port.
This example illustrates the important distinction between the This example illustrates the important distinction between the
Power Monitor Children: The IP phone draws power from the Energy Object Children: The IP phone draws power from the
switch, while the PC has LAN connectivity from the phone, but is switch, while the PC has LAN connectivity from the phone, but is
powered from the wall outlet. However, the Power Monitor Parent powered from the wall outlet. However, the Energy Object Parent
sends power control messages to both the Power Monitor Children sends power control messages to both the Energy Object Children
(IP phone and PC) and the Children react to those messages. (IP phone and PC) and the Children react to those messages.
|--------------------------------------------------------------| |--------------------------------------------------------------|
| Switch | | Switch |
|==============================================================| |==============================================================|
| Switch | Switch | Switch | Switch | Switch | | Switch | Switch | Switch | Switch | Switch |
| pmPIndex | pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | eoIndex | eoPhyIdx | eoUUID |eoParentId | eoPower |
| ============================================================ | | ============================================================ |
| 1 | 2 | UUID 1000 | null | 440 | | 1 | 2 | UUID 1000 | null | 440 |
| ============================================================ | | ============================================================ |
| | | |
| SWITCH PORT | | SWITCH PORT |
| ============================================================ | | ============================================================ |
| | Switch | Switch | Switch | Switch | Switch | | | Switch | Switch | Switch | Switch | Switch |
| | Port | Port | Port | Port | Port | | | | Port | Port | Port | Port | Port | |
| | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | | eoIndex| eoPhyIdx | eoUUID | eoParentId | eoPower | |
| ============================================================ | | ============================================================ |
| | 3 | 12 | UUID 1000:3 | UUID 1000 | 12 | | | | 3 | 12 | UUID 1000:3 | UUID 1000 | 12 | |
| ============================================================ | | ============================================================ |
| ^ | | ^ |
| | | | | |
|-----------------------------------|--------------------------| |-----------------------------------|--------------------------|
| |
| |
POE IP PHONE | POE IP PHONE |
| |
| |
============================================================= =============================================================
| IP phone | IP phone |IP phone |IP phone |IP phone| | IP phone | IP phone |IP phone | IP phone |IP phone|
| pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower| | eoIndex | eoPhyIdx |eoUUID |eoParentID |eoPower |
=========================================================== ===========================================================
| 31 | 0 | UUID 1000:31 | UUID 1000:3 | 12 | | 31 | 0 |UUID 1000:31 | UUID 1000:3 | 12 |
============================================================ ============================================================
| |
| |
PC connected to switch via IP phone | PC connected to switch via IP phone |
| |
============================================================= =============================================================
| PC | PC |PC |PC | PC | | PC | PC |PC |PC | PC |
|pmPIndex| pmPhyIdx|pmPowerMonitorId|pmParentID| pmPower | |eoIndex| eoPhyIdx |eoUUID |eoParentID | eoPower |
============================================================ ============================================================
| 57 | 0 | UUID 1000:57 | UUID 1000:3 | 120 | | 57 | 0 | UUID 1000:57| UUID 1000:3| 120 |
============================================================= =============================================================
Figure 1: Example scenario Figure 1: Example scenario
9. Structure of the MIB 9. Structure of the MIB
The primary MIB object in this MIB module is the The primary MIB object in this MIB module is the
PowerMonitorMIBObject. The pmPowerTable table of energyObjectMibObject. The eoPowerTable table of
PowerMonitorMibObject describes the power measurement attributes energyObjectMibObject describes the power measurement attributes
of a Power Monitor entity. The notion of identity of the device of an Energy Object entity. The notion of identity of the device
in terms of uniquely identification of the Power Monitor 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].
The power measurement of Power Monitor contains information The power measurement of an Energy Object contains information
describing its power usage (pmPower) and its current power state describing its power usage (eoPower) and its current power state
(pmPowerOperState). 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
(pmPowerAccuracy, pmPowerUnitMultiplier), how power usage (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage
measurement was obtained (pmPowerMeasurementCaliber), the measurement was obtained (eoPowerMeasurementCaliber), the
source of power (pmPowerOrigin) and the type of power source of power (eoPowerOrigin) and the type of power
(pmPowerCurrentTtype) are described. (eoPowerCurrentTtype) are described.
A Power Monitor may contain an optional pmPowerQuality table An Energy Object may contain an optional eoPowerQuality table
that describes the electrical characteristics associated with that describes the electrical characteristics associated with
the current power state and usage. the current power state and usage.
A Power Monitor may contain an optional pmEnergyTable to An Energy Object may contain an optional eoEnergyTable to
describe energy measurement information over time. describe energy measurement information over time.
A Power Monitor may also contain optional battery information An Energy Object may also contain optional battery information
associated with this entity. associated with this entity.
10. MIB Definitions 10. MIB Definitions
-- ************************************************************ -- ************************************************************
-- --
-- --
-- This MIB is used to monitor power usage of network -- This MIB is used to monitor power usage of network
-- devices -- devices
-- --
-- ************************************************************* -- *************************************************************
POWER-MONITOR-MIB DEFINITIONS ::= BEGIN ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
mib-2, mib-2,
Integer32, Counter64, TimeTicks Integer32, Counter64, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
OwnerString OwnerString
FROM RMON-MIB; FROM RMON-MIB;
powerMonitorMIB MODULE-IDENTITY energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201107080000Z" -- 8 July 2011 LAST-UPDATED "201110310000Z" -- 31 October 2011
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
skipping to change at page 33, line 39 skipping to change at page 34, line 31
De Kleetlaan 6a b1 De Kleetlaan 6a b1
Degem 1831 Degem 1831
Belgium Belgium
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com" Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to monitor power and energy in "This MIB is used to monitor power and energy in
devices." devices."
REVISION REVISION
"201107080000Z" -- 8 July 2011 "201110310000Z" -- 31 October 2011
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
::= { mib-2 xxx } ::= { mib-2 xxx }
powerMonitorMIBNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { powerMonitorMIB 0 } ::= { energyObjectMib 0 }
powerMonitorMIBObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
::= { powerMonitorMIB 1 } ::= { energyObjectMib 1 }
powerMonitorMIBConform OBJECT IDENTIFIER energyObjectMibConform OBJECT IDENTIFIER
::= { powerMonitorMIB 2 } ::= { energyObjectMib 2 }
-- Textual Conventions -- Textual Conventions
IANAPowerStateSet ::= TEXTUAL-CONVENTION
PowerStateSet ::= TEXTUAL-CONVENTION STATUS current
STATUS current
DESCRIPTION DESCRIPTION
"PowerStateSet is a TC that describes the Power State
Set a Power Monitor supports. IANA has created a
registry of Power State Sets supported by a Power
Monitor entity and IANA shall administer the list of
Power State Sets.
One byte is used to represent the Power State Set. "IANAPowerStateSet is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of Power
State Sets and Power States.
field octets contents range The textual convention assumes that power states in a power
----- ------ -------- ----- state set are limited to 255 distinct values. For a Power
1 1 Power State Set 1..255 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."
Note: REFERENCE
the value of Power State Set in network byte order "http://www.iana.org/assignments/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
1 in the first byte indicates IEEE1621 Power State Set SYNTAX INTEGER {
2 in the first byte indicates DMTF Power State Set other(0), -- indicates other set
3 in the first byte indicates EMAN Power State Set" unknown(255), -- unknown power state
REFERENCE ieee1621(256), -- indicates IEEE1621 set
"http://www.iana.org/assignments/eman ieee1621On(257),
RFC EDITOR NOTE: please change the previous URL ieee1621Off(258),
if this is not the correct one after IANA assigned ieee1621Sleep(259),
it."
SYNTAX OCTET STRING (SIZE(1)) dmtf(512), -- indicates DMTF set
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),
eman(1024), -- indicates EMAN set
emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
UnitMultiplier ::= TEXTUAL-CONVENTION UnitMultiplier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Unit Multiplier is an integer value that represents "The Unit Multiplier is an integer value that represents
the IEEE 61850 Annex A units multiplier associated with the IEEE 61850 Annex A units multiplier associated with
the integer units used to measure the power or energy. the integer units used to measure the power or energy.
For example, when used with pmPowerUnitMultiplier, -3 For example, when used with eoPowerUnitMultiplier, -3
represents 10^-3 or milliwatts." represents 10^-3 or milliwatts."
REFERENCE REFERENCE
"The International System of Units (SI), "The International System of Units (SI),
National Institute of Standards and Technology, National Institute of Standards and Technology,
Spec. Publ. 330, August 1991." Spec. Publ. 330, August 1991."
SYNTAX INTEGER { SYNTAX INTEGER {
yocto(-24), -- 10^-24 yocto(-24), -- 10^-24
zepto(-21), -- 10^-21 zepto(-21), -- 10^-21
atto(-18), -- 10^-18 atto(-18), -- 10^-18
femto(-15), -- 10^-15 femto(-15), -- 10^-15
skipping to change at page 35, line 36 skipping to change at page 37, line 11
giga(9), -- 10^9 giga(9), -- 10^9
tera(12), -- 10^12 tera(12), -- 10^12
peta(15), -- 10^15 peta(15), -- 10^15
exa(18), -- 10^18 exa(18), -- 10^18
zetta(21), -- 10^21 zetta(21), -- 10^21
yotta(24) -- 10^24 yotta(24) -- 10^24
} }
-- Objects -- Objects
pmPowerTable OBJECT-TYPE eoPowerTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmPowerEntry SYNTAX SEQUENCE OF EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Power Monitors." "This table lists Energy Objects."
::= { powerMonitorMIBObjects 1 } ::= { energyObjectMibObjects 1 }
pmPowerEntry OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX PmPowerEntry SYNTAX EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the power usage of a Power Monitor." "An entry describes the power usage of an Energy Object."
INDEX { eoPowerIndex}
INDEX { pmPowerIndex, pmPowerStateSetIndex} ::= { eoPowerTable 1 }
::= { pmPowerTable 1 }
PmPowerEntry ::= SEQUENCE { EoPowerEntry ::= SEQUENCE {
pmPowerIndex Integer32, eoPowerIndex Integer32,
pmPowerStateSetIndex PowerStateSet, eoPower Integer32,
pmPower Integer32, eoPowerNameplate Integer32,
pmPowerNameplate Integer32, eoPowerUnitMultiplier UnitMultiplier,
pmPowerUnitMultiplier UnitMultiplier, eoPowerAccuracy Integer32,
pmPowerAccuracy Integer32, eoPowerMeasurementCaliber INTEGER,
pmPowerMeasurementCaliber INTEGER, eoPowerCurrentType INTEGER,
pmPowerCurrentType INTEGER, eoPowerOrigin INTEGER,
pmPowerOrigin INTEGER, eoPowerAdminState IANAPowerStateSet,
pmPowerAdminState Integer32, eoPowerOperState IANAPowerStateSet,
pmPowerOperState Integer32, eoPowerStateEnterReason OwnerString
pmPowerStateEnterReason OwnerString
} }
pmPowerIndex OBJECT-TYPE eoPowerIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value, for each Power Monitor. "A unique value, for each Energy Object.
If an implementation of the ENERGY-AWARE-MIB module is If an implementation of the ENERGY-AWARE-MIB module is
available in the local SNMP context, then the same index available in the local SNMP context, then the same index,
as the one in the ENERGY-AWARE-MIB MUST be assigned for eoIndex, as the one in the ENERGY-AWARE-MIB MUST be
the identical Power Monitor. In this case, entities assigned for the identical Energy Object. In this case,
without an assigned value for pmIndex cannot be indexed entities without an assigned value for eoIndex cannot be
by the pmPowerStateTable. indexed by the eoPowerStateTable.
If there is no implementation of the ENERGY-AWARE-MIB If there is no implementation of the ENERGY-AWARE-MIB
module but one of the ENTITY MIB module is available in module but one of the ENTITY MIB module is available in
the local SNMP context, then the same index of an entity the local SNMP context, then the same index of an entity
MUST be chosen as assigned to the entity by object MUST be chosen as assigned to the entity by object
entPhysicalIndex in the ENTITY MIB module. In this case, entPhysicalIndex in the ENTITY MIB module. In this case,
entities without an assigned value for entPhysicalIndex entities without an assigned value for entPhysicalIndex
cannot be indexed by the pmPowerStateTable. cannot be indexed by the eoPowerStateTable.
If neither the ENERGY-AWARE-MIB module nor of the ENTITY If neither the ENERGY-AWARE-MIB module nor of the ENTITY
MIB module are available in the local SNMP context, then MIB module are available in the local SNMP context, then
this MIB module may choose identity values from a further this MIB module may choose identity values from a further
MIB module providing entity identities. In this case the MIB module providing entity identities. In this case the
value for each pmPowerIndex must remain constant at least value for each eoPowerIndex must remain constant at least
from one re-initialization of the entity's network from one re-initialization of the entity's network
management system to the next re-initialization. management system to the next re-initialization.
In case that no other MIB modules have been chosen for In case that no other MIB modules have been chosen for
providing entity identities, Power States can be reported providing entity identities, Power States can be reported
exclusively for the local device on which this table is exclusively for the local device on which this table is
instantiated. Then this table will have a single entry instantiated. Then this table will have a single entry
only and an index value of 0 MUST be used." only and an index value of 0 MUST be used."
::= { pmPowerEntry 1 } ::= { eoPowerEntry 1 }
pmPowerStateSetIndex OBJECT-TYPE
SYNTAX PowerStateSet
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Power State Set supported by
the Power Monitor. The list of Power State Sets and
their numbering are administered by IANA"
::= { pmPowerEntry 2 }
pmPower OBJECT-TYPE eoPower 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 'instantaneous' RMS "This object indicates the power measured for the Energy
consumption for the Power Monitor. This value is Object. For alternating current, this value is obtained
specified in SI units of watts with the magnitude of as an average over fixed number of AC cycles. . This
watts (milliwatts, kilowatts, etc.) indicated separately value is specified in SI units of watts with the
in pmPowerUnitMultiplier. The accuracy of the measurement magnitude of watts (milliwatts, kilowatts, etc.)
is specfied in pmPowerAccuracy. The direction of power indicated separately in eoPowerUnitMultiplier. The
flow is indicated by the sign on pmPower. If the Power accuracy of the measurement is specfied in
Monitor is consuming power, the pmPower value will be eoPowerAccuracy. The direction of power flow is indicated
positive. If the Power Monitor is producing power, the by the sign on eoPower. If the Energy Object is consuming
pmPower value will be negative. power, the eoPower value will be positive. If the Energy
Object is producing power, the eoPower value will be
negative.
The pmPower MUST be less than or equal to the maximum The eoPower MUST be less than or equal to the maximum
power that can be consumed at the power state specified power that can be consumed at the power state specified
by pmPowerState. by eoPowerState.
The pmPowerMeasurementCaliber object specifies how the The eoPowerMeasurementCaliber object specifies how the
usage value reported by pmPower was obtained. The pmPower usage value reported by eoPower was obtained. The eoPower
value must report 0 if the pmPowerMeasurementCaliber is value must report 0 if the eoPowerMeasurementCaliber is
'unavailable'. For devices that can not measure or 'unavailable'. For devices that can not measure or
report power, this option can be used." report power, this option can be used."
::= { pmPowerEntry 3 } ::= { eoPowerEntry 2 }
pmPowerNameplate OBJECT-TYPE eoPowerNameplate 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 rated maximum consumption for "This object indicates the rated maximum consumption for
the fully populated Power Monitor. The nameplate power the fully populated Energy Object. The nameplate power
requirements are the maximum power numbers and, in almost requirements are the maximum power numbers and, in almost
all cases, are well above the expected operational all cases, are well above the expected operational
consumption. The pmPowerNameplate is widely used for consumption. The eoPowerNameplate is widely used for
power provisioning. This value is specified in either power provisioning. This value is specified in either
units of watts or voltage and current. The units are units of watts or voltage and current. The units are
therefore SI watts or equivalent Volt-Amperes with the therefore SI watts or equivalent Volt-Amperes with the
magnitude (milliwatts, kilowatts, etc.) indicated magnitude (milliwatts, kilowatts, etc.) indicated
separately in pmPowerUnitMultiplier." separately in eoPowerUnitMultiplier."
::= { pmPowerEntry 4 } ::= { eoPowerEntry 3 }
pmPowerUnitMultiplier OBJECT-TYPE eoPowerUnitMultiplier 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 pmPower "The magnitude of watts for the usage value in eoPower
and pmPowerNameplate." and eoPowerNameplate."
::= { pmPowerEntry 5 } ::= { eoPowerEntry 4 }
pmPowerAccuracy OBJECT-TYPE eoPowerAccuracy 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
"This object indicates a percentage value, in 100ths of a "This object indicates a percentage value, in 100ths of a
percent, representing the assumed accuracy of the usage percent, representing the assumed accuracy of the usage
reported by pmPower. For example: The value 1010 means reported by eoPower. For example: The value 1010 means
the reported usage is accurate to +/- 10.1 percent. This the reported usage is accurate to +/- 10.1 percent. This
value is zero if the accuracy is unknown or not value is zero if the accuracy is unknown or not
applicable based upon the measurement method. applicable based upon the measurement method.
ANSI and IEC define the following accuracy classes for ANSI and IEC define the following accuracy classes for
power measurement: power measurement:
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
ANSI C12.20 class 0.2, 0.5" ANSI C12.20 class 0.2, 0.5"
::= { pmPowerEntry 6 } ::= { eoPowerEntry 5 }
pmPowerMeasurementCaliber OBJECT-TYPE eoPowerMeasurementCaliber OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unavailable(1) , unavailable(1) ,
unknown(2), unknown(2),
actual(3) , actual(3) ,
estimated(4), estimated(4),
presumed(5) } presumed(5) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies how the usage value reported by "This object specifies how the usage value reported by
pmPower was obtained: eoPower was obtained:
- unavailable(1): Indicates that the usage is not - unavailable(1): Indicates that the usage is not
available. In such a case, the pmPower value must be 0 available. In such a case, the eoPower value must be 0
For devices that can not measure or report power this For devices that can not measure or report power this
option can be used. option can be used.
- unknown(2): Indicates that the way the usage was - unknown(2): Indicates that the way the usage was
determined is unknown. In some cases, entities report determined is unknown. In some cases, entities report
aggregate power on behalf of another device. In such aggregate power on behalf of another device. In such
cases it is not known whether the usage reported is cases it is not known whether the usage reported is
actual(2), estimated(3) or presumed (4). actual(2), estimated(3) or presumed (4).
- actual(3): Indicates that the reported usage was - actual(3): Indicates that the reported usage was
skipping to change at page 39, line 46 skipping to change at page 41, line 15
is presumed that the entity's state and current is presumed that the entity's state and current
configuration were used to compute the value. configuration were used to compute the value.
- presumed(5): Indicates that the usage was not - presumed(5): Indicates that the usage was not
determined by physical measurement, algorithm or determined by physical measurement, algorithm or
derivation. The usage was reported based upon external derivation. The usage was reported based upon external
tables, specifications, and/or model information. For tables, specifications, and/or model information. For
example, a PC Model X draws 200W, while a PC Model Y example, a PC Model X draws 200W, while a PC Model Y
draws 210W" draws 210W"
::= { pmPowerEntry 7 } ::= { eoPowerEntry 6 }
pmPowerCurrentType OBJECT-TYPE eoPowerCurrentType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ac(1), ac(1),
dc(2), dc(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the pmUsage for the Power "This object indicates whether the eoUsage for the
Monitor reports alternative current AC(1), direct current Energy Object reports alternative current AC(1), direct
DC(2), or that the current type is unknown(3)." current DC(2), or that the current type is unknown(3)."
::= { pmPowerEntry 8 } ::= { eoPowerEntry 7 }
pmPowerOrigin OBJECT-TYPE eoPowerOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
self (1), self (1),
remote (2) remote (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the source of power measurement "This object indicates the source of power measurement
and can be useful when modeling the power usage of and can be useful when modeling the power usage of
attached devices. The power measurement can be performed attached devices. The power measurement can be performed
by the entity itself or the power measurement of the by the entity itself or the power measurement of the
entity can be reported by another trusted entity using a entity can be reported by another trusted entity using a
protocol extension. A value of self(1) indicates the protocol extension. A value of self(1) indicates the
measurement is performed by the entity, whereas remote(2) measurement is performed by the entity, whereas remote(2)
indicates that the measurement was performed by another indicates that the measurement was performed by another
entity." entity."
::= { pmPowerEntry 9 } ::= { eoPowerEntry 8 }
pmPowerAdminState OBJECT-TYPE eoPowerAdminState OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX IANAPowerStateSet
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the desired Power State for the
Power Monitor, in the context of the Power State Set "This object specifies the desired Power State and the
specified by pmPowerStateSetIndex in this table. Power State Set for the Energy Object. Note that
Possible values of pmPowerAdminState are registered at other(0) is not a Power State Set and unknown(255) is
IANA, per Power State Set. A current list of not a Power State as such, but simply an indication that
assignments can be found at 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> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 9 }
::= { pmPowerEntry 10 } eoPowerOperState OBJECT-TYPE
SYNTAX IANAPowerStateSet
pmPowerOperState OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the current operational Power "This object specifies the current operational Power
State for the Power Monitor, in the context of the Power State and the Power State Set for the Energy Object.
State Set specified by pmPowerStateSetIndex in this other(0) is not a Power State Set and unknown(255) is
table. Possible values of pmPowerOperState are not a Power State as such, but simply an indication that
registered at IANA, per Power State Set. A current list the Power State of the Energy Object is unknown.
of assignments can be found at
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> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the list" RFC-EDITOR: please check the location after IANA"
::= { pmPowerEntry 11 }
pmPowerStateEnterReason OBJECT-TYPE ::= { eoPowerEntry 10 }
eoPowerStateEnterReason OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This string object describes the reason for the "This string object describes the reason for the
pmPowerAdminState eoPowerAdminState
transition Alternatively, this string may contain with transition Alternatively, this string may contain with
the entity that configured this Power Monitor to this the entity that configured this Energy Object to this
Power State." Power State."
DEFVAL { "" } DEFVAL { "" }
::= { pmPowerEntry 12 } ::= { eoPowerEntry 11 }
pmPowerStateTable OBJECT-TYPE eoPowerStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmPowerStateEntry SYNTAX SEQUENCE OF EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates the maximum power usage, in watts, "This table enumerates the maximum power usage, in watts,
for every single supported Power State of each Power for every single supported Power State of each Energy
Monitor. Object.
This table has an expansion-dependent relationship on the This table has an expansion-dependent relationship on the
pmPowerTable, containing rows describing each Power State eoPowerTable, containing rows describing each Power State
for the corresponding Power Monitor. For every Power for the corresponding Energy Object. For every Energy
Monitor in the pmPowerTable, there is a corresponding Object in the eoPowerTable, there is a corresponding
entry in this table." entry in this table."
::= { powerMonitorMIBObjects 2 } ::= { energyObjectMibObjects 2 }
pmPowerStateEntry OBJECT-TYPE eoPowerStateEntry OBJECT-TYPE
SYNTAX PmPowerStateEntry SYNTAX EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pmPowerStateEntry extends a corresponding "A eoPowerStateEntry extends a corresponding
pmPowerEntry. This entry displays max usage values at eoPowerEntry. This entry displays max usage values at
every single possible Power State supported by the Power every single possible Power State supported by the Energy
Monitor. Object.
For example, given the values of a Power Monitor For example, given the values of a Energy Object
corresponding to a maximum usage of 11W at the corresponding to a maximum usage of 11W at the
state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High): state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High):
State MaxUsage Units State MaxUsage Units
1 (mechoff 0 W 1 (mechoff 0 W
2 (softoff) 0 W 2 (softoff) 0 W
3 (hibernate) 0 W 3 (hibernate) 0 W
4 (sleep) 0 W 4 (sleep) 0 W
5 (standby) 0 W 5 (standby) 0 W
6 (ready) 8 W 6 (ready) 8 W
skipping to change at page 42, line 28 skipping to change at page 44, line 9
8 (low) 11 W 8 (low) 11 W
9 (medimMinus) 11 W 9 (medimMinus) 11 W
10 (medium) 11 W 10 (medium) 11 W
11 (highMinus) 11 W 11 (highMinus) 11 W
12 (high) 11 W 12 (high) 11 W
Furthermore, this table extends to return the total time Furthermore, this table extends to return the total time
in each Power State, along with the number of times a in each Power State, along with the number of times a
particular Power State was entered." particular Power State was entered."
INDEX { INDEX { eoPowerIndex,
pmPowerIndex, eoPowerStateIndex
pmPowerStateSetIndex,
pmPowerStateIndex
} }
::= { pmPowerStateTable 1 } ::= { eoPowerStateTable 1 }
PmPowerStateEntry ::= SEQUENCE { EoPowerStateEntry ::= SEQUENCE {
pmPowerStateIndex Integer32, eoPowerStateIndex IANAPowerStateSet,
pmPowerStateMaxPower Integer32, eoPowerStateMaxPower Integer32,
pmPowerStatePowerUnitMultiplier UnitMultiplier, eoPowerStatePowerUnitMultiplier UnitMultiplier,
pmPowerStateTotalTime TimeTicks, eoPowerStateTotalTime TimeTicks,
pmPowerStateEnterCount Counter64 eoPowerStateEnterCount Counter64
} }
pmPowerStateIndex OBJECT-TYPE eoPowerStateIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX IANAPowerStateSet
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Power State for the Power "
Monitor, in the context of the Power State Set specified
by pmPowerStateSetIndex in this table.
This object specifies the index of the Power State of This object specifies the index of the Power State of
the Power Monitor within a Power State Set. The the Energy Object within a Power State Set. The
semantics of the specific Power State can be obtained semantics of the specific Power State can be obtained
from the Power State Set definition." from the Power State Set definition."
::= { pmPowerStateEntry 1 } ::= { eoPowerStateEntry 1 }
pmPowerStateMaxPower 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 Power "This object indicates the maximum power for the Energy
Monitor 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 pmPowerStatePowerUnitMultiplier. 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 0xFFFF. encoded as 0xFFFF.
For Power States not enumerated, the value of For Power States not enumerated, the value of
pmPowerStateMaxPower might be interpolated by using the eoPowerStateMaxPower might be interpolated by using the
next highest supported Power State." next highest supported Power State."
::= { pmPowerStateEntry 3 } ::= { eoPowerStateEntry 3 }
pmPowerStatePowerUnitMultiplier 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
pmPowerStateMaxPower." eoPowerStateMaxPower."
::= { pmPowerStateEntry 4 } ::= { eoPowerStateEntry 4 }
pmPowerStateTotalTime 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 hundreds "This object indicates the total time in hundreds
of seconds that the Power Monitor has been in this power of seconds 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."
::= { pmPowerStateEntry 5 } ::= { eoPowerStateEntry 5 }
pmPowerStateEnterCount OBJECT-TYPE eoPowerStateEnterCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the Power Monitor has "This object indicates how often the Energy
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."
::= { pmPowerStateEntry 6 } ::= { eoPowerStateEntry 6 }
pmEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmEnergyParametersEntry 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 Energy "This table is used to configure the parameters for Energy
measurement collection in the table pmEnergyTable." measurement collection in the table eoEnergyTable."
::= { powerMonitorMIBObjects 4 } ::= { energyObjectMibObjects 4 }
pmEnergyParametersEntry OBJECT-TYPE eoEnergyParametersEntry OBJECT-TYPE
SYNTAX PmEnergyParametersEntry 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
pmEnergyTable." eoEnergyTable."
INDEX { pmPowerIndex } INDEX { eoPowerIndex }
::= { pmEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
PmEnergyParametersEntry ::= SEQUENCE { EoEnergyParametersEntry ::= SEQUENCE {
pmEnergyParametersIntervalLength TimeInterval, eoEnergyParametersIntervalLength TimeInterval,
pmEnergyParametersIntervalNumber Integer32, eoEnergyParametersIntervalNumber Integer32,
pmEnergyParametersIntervalMode Integer32, eoEnergyParametersIntervalMode Integer32,
pmEnergyParametersIntervalWindow TimeInterval, eoEnergyParametersIntervalWindow TimeInterval,
pmEnergyParametersSampleRate Integer32, eoEnergyParametersSampleRate Integer32,
pmEnergyParametersStatus RowStatus eoEnergyParametersStatus RowStatus
} }
pmEnergyParametersIntervalLength OBJECT-TYPE eoEnergyParametersIntervalLength OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the length of time in seconds over "This object indicates the length of time in seconds over
which to compute the average pmEnergyIntervalEnergyUsed which to compute the average eoEnergyIntervalEnergyUsed
measurement in the pmEnergyTable table. The computation measurement in the eoEnergyTable table. The computation
is based on the Power Monitor's internal sampling rate of is based on the Energy Object's internal sampling rate of
power consumed or produced by the Power Monitor. The power consumed or produced by the Energy Object. The
sampling rate is the rate at which the power monitor can sampling rate is the rate at which the Energy Object can
read the power usage and may differ based on device read the power usage and may differ based on device
capabilities. The average energy consumption is then capabilities. The average energy consumption is then
computed over the length of the interval." computed over the length of the interval."
DEFVAL { 900 } DEFVAL { 900 }
::= { pmEnergyParametersEntry 1 } ::= { eoEnergyParametersEntry 1 }
pmEnergyParametersIntervalNumber OBJECT-TYPE eoEnergyParametersIntervalNumber OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of intervals maintained in the pmEnergyTable. "The number of intervals maintained in the eoEnergyTable.
Each interval is characterized by a specific Each interval is characterized by a specific
pmEnergyIntervalStartTime, used as an index to the table eoEnergyIntervalStartTime, used as an index to the table
pmEnergyTable . Whenever the maximum number of entries is eoEnergyTable . Whenever the maximum number of entries is
reached, the measurement over the new interval replaces reached, the measurement over the new interval replaces
the oldest measurement , except if the oldest measurement the oldest measurement , except if the oldest measurement
were to be the maximum pmEnergyIntervalMax, in which case were to be the maximum eoEnergyIntervalMax, in which case
the measurement the measurement over the next oldest the measurement the measurement over the next oldest
interval is replaced." interval is replaced."
DEFVAL { 10 } DEFVAL { 10 }
::= { pmEnergyParametersEntry 2 }
pmEnergyParametersIntervalMode OBJECT-TYPE ::= { eoEnergyParametersEntry 2 }
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 calculation
for the computation of the average for the computation of the average
pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable eoEnergyIntervalEnergyUsed measurement in the eoEnergyTable
table. 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 windows
where the interval between the start of one interval and where the interval between the start of one interval and
the next is defined in pmEnergyParametersIntervalWindow. 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. In
this mode only one interval is used as this is a 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
pmEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
pmEnergyParametersIntervalLength is ignored. " eoEnergyParametersIntervalLength is ignored. "
::= { pmEnergyParametersEntry 3 } ::= { eoEnergyParametersEntry 3 }
pmEnergyParametersIntervalWindow OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "Seconds" UNITS "Seconds"
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
seconds, in order to compute the average seconds, in order to compute the average
pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable eoEnergyIntervalEnergyUsed measurement in the eoEnergyTable
table This is valid only when the table This is valid only when the
pmEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalMode is sliding(2). The
pmEnergyParametersIntervalWindow value should be a multiple eoEnergyParametersIntervalWindow value should be a multiple
of pmEnergyParametersSampleRate." of eoEnergyParametersSampleRate."
::= { pmEnergyParametersEntry 4 } ::= { eoEnergyParametersEntry 4 }
pmEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
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 Power "The sampling rate, in milliseconds, at which the Energy
Monitor should poll power usage in order to compute the Object should poll power usage in order to compute the
average pmEnergyIntervalEnergyUsed measurement in the average eoEnergyIntervalEnergyUsed measurement in the
table pmEnergyTable. The Power Monitor should initially table eoEnergyTable. The Energy Object should initially
set this sampling rate to a reasonable value, i.e., a set this sampling rate to a reasonable value, i.e., a
compromise between intervals that will provide good compromise between intervals that will provide good
accuracy by not being too long, but not so short that accuracy by not being too long, but not so short that
they affect the Power Monitor performance by requesting they affect the Energy Object performance by requesting
continuous polling. If the sampling rate is unknown, the continuous polling. If the sampling rate is unknown, the
value 0 is reported. The sampling rate should be selected value 0 is reported. The sampling rate should be selected
so that pmEnergyParametersIntervalWindow is a multiple of so that eoEnergyParametersIntervalWindow is a multiple of
pmEnergyParametersSampleRate." eoEnergyParametersSampleRate."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { pmEnergyParametersEntry 5 } ::= { eoEnergyParametersEntry 5 }
pmEnergyParametersStatus OBJECT-TYPE eoEnergyParametersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row. The pmEnergyParametersStatus 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(1), all associated usage-data logged into equal to active(1), all associated usage-data logged into
the pmEnergyTable will be deleted. The data can be the eoEnergyTable will be deleted. The data can be
destroyed by setting up the pmEnergyParametersStatus to destroyed by setting up the eoEnergyParametersStatus to
destroy(2)." destroy(2)."
::= {pmEnergyParametersEntry 6 } ::= {eoEnergyParametersEntry 6 }
pmEnergyTable OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmEnergyIntervalEntry SYNTAX SEQUENCE OF EoEnergyIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Power Monitor energy measurements. "This table lists Energy Object energy measurements.
Entries in this table are only created if the Entries in this table are only created if the
corresponding value of object pmPowerMeasurementCaliber corresponding value of object eoPowerMeasurementCaliber
is active(2), i.e., if the power is actually metered." is active(2), i.e., if the power is actually metered."
::= { powerMonitorMIBObjects 5 } ::= { energyObjectMibObjects 5 }
pmEnergyIntervalEntry OBJECT-TYPE eoEnergyIntervalEntry OBJECT-TYPE
SYNTAX PmEnergyIntervalEntry SYNTAX EoEnergyIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "An entry describing energy measurements."
INDEX { pmPowerIndex, pmEnergyParametersIntervalMode, INDEX { eoPowerIndex, eoEnergyParametersIntervalMode,
pmEnergyIntervalStartTime } eoEnergyIntervalStartTime }
::= { pmEnergyTable 1 } ::= { eoEnergyTable 1 }
PmEnergyIntervalEntry ::= SEQUENCE { EoEnergyIntervalEntry ::= SEQUENCE {
pmEnergyIntervalStartTime TimeTicks, eoEnergyIntervalStartTime TimeTicks,
pmEnergyIntervalEnergyUsed Integer32, eoEnergyIntervalEnergyConsumed Integer32,
pmEnergyIntervalEnergyUnitMultiplier UnitMultiplier, eoEnergyIntervalEnergyProduced Integer32,
pmEnergyIntervalMax Integer32, eoEnergyIntervalEnergyNet Integer32,
pmEnergyIntervalDiscontinuityTime TimeTicks eoEnergyIntervalEnergyUnitMultiplier UnitMultiplier,
eoEnergyIntervalEnergyAccuracy Integer32,
eoEnergyIntervalMaxConsumed Integer32,
eoEnergyIntervalMaxProduced Integer32,
eoEnergyIntervalDiscontinuityTime TimeTicks
} }
pmEnergyIntervalStartTime OBJECT-TYPE eoEnergyIntervalStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
UNITS "hundredths of seconds" UNITS "hundredths of seconds"
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since the "The time (in hundredths of a second) since the
network management portion of the system was last network management portion of the system was last
re-initialized, as specified in the sysUpTime [RFC3418]. re-initialized, as specified in the sysUpTime [RFC3418].
This object is useful for reference of interval periods This object is useful for reference of interval periods
for which the energy is measured." for which the energy is measured."
::= { pmEnergyIntervalEntry 1 } ::= { eoEnergyIntervalEntry 1 }
pmEnergyIntervalEnergyUsed OBJECT-TYPE eoEnergyIntervalEnergyConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
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 used in units of watt- "This object indicates the energy consumed in units of watt-
hours for the Power Monitor over the defined interval. hours for the Energy Object over the defined interval.
This value is specified in the common billing units of This value is specified in the common billing units of watt-
watt-hours with the magnitude of watt-hours (kW-Hr, MW- hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
Hr, etc.) indicated separately in indicated separately in eoEnergyIntervalEnergyUnitMultiplier."
pmEnergyIntervalEnergyUnitMultiplier." ::= { eoEnergyIntervalEntry 2 }
::= { pmEnergyIntervalEntry 2 }
pmEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE eoEnergyIntervalEnergyProduced OBJECT-TYPE
SYNTAX Integer32
UNITS "Watt-hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the energy produced 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 eoEnergyIntervalEnergyUnitMultiplier."
::= { eoEnergyIntervalEntry 3 }
eoEnergyIntervalEnergyNet OBJECT-TYPE
SYNTAX Integer32
UNITS "Watt-hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the resultant 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 eoEnergyIntervalEnergyUnitMultiplier."
::= { eoEnergyIntervalEntry 4 }
eoEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
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 is the magnitude of watt-hours for the
energy field in pmEnergyIntervalEnergyUsed." energy field in eoEnergyIntervalEnergyUsed."
::= { pmEnergyIntervalEntry 3 } ::= { eoEnergyIntervalEntry 5 }
pmEnergyIntervalMax OBJECT-TYPE eoEnergyIntervalEnergyAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a percentage value, in 100ths of a
percent, representing the presumed accuracy of Energy usage
reporting. eoEnergyIntervalEnergyAccuracy is applicable to all
Energy measurements in the eoEnergyTable.
For example: 1010 means the reported usage is accurate to +/-
10.1 percent.
This value is zero if the accuracy is unknown."
::= { eoEnergyIntervalEntry 6 }
eoEnergyIntervalMaxConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
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 ever observed in
pmEnergyIntervalEnergyUsed since the monitoring started. eoEnergyIntervalEnergyConsumed since the monitoring
This value is specified in the common billing units of started. This value is specified in the common billing
watt-hours with the magnitude of watt-hours (kW-Hr, MW- units of watt-hours with the magnitude of watt-hours (kW-
Hr, etc.) indicated separately in Hr, MW-Hr, etc.) indicated separately in
pmEnergyIntervalEnergyUnits." eoEnergyIntervalEnergyUnits."
::= { pmEnergyIntervalEntry 4 } ::= { eoEnergyIntervalEntry 7 }
pmEnergyIntervalDiscontinuityTime OBJECT-TYPE eoEnergyIntervalMaxProduced OBJECT-TYPE
SYNTAX Integer32
UNITS "Watt-hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the maximum energy ever observed in
eoEnergyIntervalEnergyProduced 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
eoEnergyIntervalEnergyUnits."
::= { eoEnergyIntervalEntry 8 }
eoEnergyIntervalDiscontinuityTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION 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
consumption counters suffered a discontinuity. If no such consumption counters suffered a discontinuity. If no such
discontinuities have occurred since the last re- 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."
::= { pmEnergyIntervalEntry 5 } ::= { eoEnergyIntervalEntry 9 }
-- Notifications -- Notifications
pmPowerStateChange NOTIFICATION-TYPE eoPowerStateChange NOTIFICATION-TYPE
OBJECTS {pmPowerAdminState, pmPowerOperState, OBJECTS {eoPowerAdminState, eoPowerOperState,
pmPowerStateEnterReason} eoPowerStateEnterReason}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP entity generates the PmPowerStateChange when "The SNMP entity generates the eoPowerStateChange when
the value(s) of pmPowerAdminState or pmPowerOperState, the value(s) 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 Power Monitor represented by the pmPowerIndex." the Energy Object represented by the eoPowerIndex."
::= { powerMonitorMIBNotifs 1 } ::= { energyObjectMibNotifs 1 }
-- Conformance -- Conformance
powerMonitorMIBCompliances OBJECT IDENTIFIER energyObjectMibCompliances OBJECT IDENTIFIER
::= { powerMonitorMIB 3 } ::= { energyObjectMib 3 }
powerMonitorMIBGroups OBJECT IDENTIFIER energyObjectMibGroups OBJECT IDENTIFIER
::= { powerMonitorMIB 4 } ::= { energyObjectMib 4 }
powerMonitorMIBFullCompliance MODULE-COMPLIANCE energyObjectMibFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for "When this MIB is implemented with support for
read-create, then such an implementation can read-create, then such an implementation can
claim full compliance. Such devices can then claim full compliance. Such devices can then
be both monitored and configured with this MIB." be both monitored and configured with this MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerMonitorMIBTableGroup, energyObjectMibTableGroup,
powerMonitorMIBStateTableGroup, energyObjectMibStateTableGroup,
powerMonitorMIBEnergyTableGroup, energyObjectMibEnergyTableGroup,
powerMonitorMIBEnergyParametersTableGroup, energyObjectMibEnergyParametersTableGroup,
powerMonitorMIBNotifGroup energyObjectMibNotifGroup
} }
::= { powerMonitorMIBCompliances 1 } ::= { energyObjectMibCompliances 1 }
powerMonitorMIBReadOnlyCompliance MODULE-COMPLIANCE energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented without support for "When this MIB is implemented without support for
read-create (i.e. in read-only mode), then such an read-create (i.e. in read-only mode), then such an
implementation can claim read-only compliance. Such a implementation can claim read-only compliance. Such a
device can then be monitored but can not be configured device can then be monitored but cannot be
with this MIB." configured with this MIB. "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerMonitorMIBTableGroup, energyObjectMibTableGroup,
powerMonitorMIBStateTableGroup, energyObjectMibStateTableGroup,
powerMonitorMIBNotifGroup energyObjectMibNotifGroup
} }
OBJECT pmPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { powerMonitorMIBCompliances 2 } ::= { energyObjectMibCompliances 2 }
-- Units of Conformance -- Units of Conformance
powerMonitorMIBTableGroup OBJECT-GROUP energyObjectMibTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmPower, eoPower,
pmPowerNameplate, eoPowerNameplate,
pmPowerUnitMultiplier, eoPowerUnitMultiplier,
pmPowerAccuracy, eoPowerAccuracy,
pmPowerMeasurementCaliber, eoPowerMeasurementCaliber,
pmPowerCurrentType, eoPowerCurrentType,
pmPowerOrigin, eoPowerOrigin,
pmPowerAdminState, eoPowerAdminState,
pmPowerOperState, eoPowerOperState,
pmPowerStateEnterReason eoPowerStateEnterReason
} }
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 PowerMonitor." related to the PowerMonitor."
::= { powerMonitorMIBGroups 1 } ::= { energyObjectMibGroups 1 }
powerMonitorMIBStateTableGroup OBJECT-GROUP energyObjectMibStateTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmPowerStateMaxPower, eoPowerStateMaxPower,
pmPowerStatePowerUnitMultiplier, eoPowerStatePowerUnitMultiplier,
pmPowerStateTotalTime, eoPowerStateTotalTime,
pmPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the "This group contains the collection of all the
objects related to the Power State." objects related to the Power State."
::= { powerMonitorMIBGroups 2 } ::= { energyObjectMibGroups 2 }
powerMonitorMIBEnergyParametersTableGroup OBJECT-GROUP energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmEnergyParametersIntervalLength, eoEnergyParametersIntervalLength,
pmEnergyParametersIntervalNumber, eoEnergyParametersIntervalNumber,
pmEnergyParametersIntervalMode, eoEnergyParametersIntervalMode,
pmEnergyParametersIntervalWindow, eoEnergyParametersIntervalWindow,
pmEnergyParametersSampleRate, eoEnergyParametersSampleRate,
pmEnergyParametersStatus eoEnergyParametersStatus
} }
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 configuration of the Energy Table." related to the configuration of the Energy Table."
::= { powerMonitorMIBGroups 3 } ::= { energyObjectMibGroups 3 }
powerMonitorMIBEnergyTableGroup OBJECT-GROUP energyObjectMibEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- pmEnergyIntervalStartTime is not -- eoEnergyIntervalStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
pmEnergyIntervalEnergyUsed, eoEnergyIntervalEnergyConsumed,
pmEnergyIntervalEnergyUnitMultiplier, eoEnergyIntervalEnergyProduced,
pmEnergyIntervalMax, eoEnergyIntervalEnergyNet,
pmEnergyIntervalDiscontinuityTime eoEnergyIntervalEnergyUnitMultiplier,
eoEnergyIntervalEnergyAccuracy,
eoEnergyIntervalMaxConsumed,
eoEnergyIntervalMaxProduced,
eoEnergyIntervalDiscontinuityTime
} }
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."
::= { powerMonitorMIBGroups 4 } ::= { energyObjectMibGroups 4 }
powerMonitorMIBNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
pmPowerStateChange eoPowerStateChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the notifications for the power and "This group contains the notifications for the power and
energy monitoring MIB Module." energy monitoring MIB Module."
::= { powerMonitorMIBGroups 5 } ::= { energyObjectMibGroups 5 }
END END
-- ************************************************************ -- ************************************************************
-- --
-- This MIB module is used to monitor power quality of networked -- This MIB module is used to monitor power quality of networked
-- devices with measurements. -- devices with measurements.
-- --
-- This MIB module is an extension of powerMonitorMIB module. -- This MIB module is an extension of energyObjectMib module.
-- --
-- ************************************************************* -- *************************************************************
POWER-QUALITY-MIB DEFINITIONS ::= BEGIN POWER-QUALITY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
Integer32 Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier, pmPowerIndex UnitMultiplier, eoPowerIndex
FROM POWER-MONITOR-MIB FROM ENERGY-OBJECT-MIB
OwnerString OwnerString
FROM RMON-MIB; FROM RMON-MIB;
powerQualityMIB MODULE-IDENTITY powerQualityMIB MODULE-IDENTITY
LAST-UPDATED "201107080000Z" -- 8 July 2011 LAST-UPDATED "201110310000Z" -- 31 October 2011
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
Archive: Archive:
http://www.ietf.org/mail-archive/web/eman http://www.ietf.org/mail-archive/web/eman
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore, Bangalore,
IN IN
skipping to change at page 54, line 6 skipping to change at page 57, line 10
Cisco Systems, Inc. Cisco Systems, Inc.
De Kleetlaan 6a b1 De Kleetlaan 6a b1
Degem 1831 Degem 1831
Belgium Belgium
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com" Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to report AC power quality in "This MIB is used to report AC power quality in
devices. The table is a sparse augmentation of the devices. The table is a sparse augmentation of the
pmPowerTable table from the powerMonitorMIB 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."
REVISION REVISION
"201107080000Z" -- 8 July 2011 "201110310000Z" -- 31 October 2011
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerQualityMIBConform OBJECT IDENTIFIER powerQualityMIBConform OBJECT IDENTIFIER
::= { powerQualityMIB 0 } ::= { powerQualityMIB 0 }
powerQualityMIBObjects OBJECT IDENTIFIER powerQualityMIBObjects OBJECT IDENTIFIER
::= { powerQualityMIB 1 } ::= { powerQualityMIB 1 }
-- Objects -- Objects
pmACPwrQualityTable OBJECT-TYPE eoACPwrQualityTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmACPwrQualityEntry SYNTAX SEQUENCE OF EoACPwrQualityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines power quality measurements for "This table defines power quality measurements for
supported pmPowerIndex entities. It is a sparse supported eoPowerIndex entities. It is a sparse
extension of the pmPowerTable." extension of the eoPowerTable."
::= { powerQualityMIBObjects 1 } ::= { powerQualityMIBObjects 1 }
pmACPwrQualityEntry OBJECT-TYPE eoACPwrQualityEntry OBJECT-TYPE
SYNTAX PmACPwrQualityEntry SYNTAX EoACPwrQualityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a sparse extension of the pmPowerTable with "This is a sparse extension of the eoPowerTable with
entries for power quality measurements or entries for power quality measurements or
configuration. Each measured value corresponds to an configuration. Each measured value corresponds to an
attribute in IEC 61850-7-4 for non-phase measurements attribute in IEC 61850-7-4 for non-phase measurements
within the object MMUX." within the object MMUX."
INDEX { pmPowerIndex } INDEX { eoPowerIndex }
::= { pmACPwrQualityTable 1 } ::= { eoACPwrQualityTable 1 }
PmACPwrQualityEntry ::= SEQUENCE { EoACPwrQualityEntry ::= SEQUENCE {
pmACPwrQualityConfiguration INTEGER, eoACPwrQualityConfiguration INTEGER,
pmACPwrQualityAvgVoltage Integer32, eoACPwrQualityAvgVoltage Integer32,
pmACPwrQualityAvgCurrent Integer32, eoACPwrQualityAvgCurrent Integer32,
pmACPwrQualityFrequency Integer32, eoACPwrQualityFrequency Integer32,
pmACPwrQualityPowerUnitMultiplier UnitMultiplier, eoACPwrQualityPowerUnitMultiplier UnitMultiplier,
pmACPwrQualityPowerAccuracy Integer32, eoACPwrQualityPowerAccuracy Integer32,
pmACPwrQualityTotalActivePower Integer32, eoACPwrQualityTotalActivePower Integer32,
pmACPwrQualityTotalReactivePower Integer32, eoACPwrQualityTotalReactivePower Integer32,
pmACPwrQualityTotalApparentPower Integer32, eoACPwrQualityTotalApparentPower Integer32,
pmACPwrQualityTotalPowerFactor Integer32, eoACPwrQualityTotalPowerFactor Integer32,
pmACPwrQualityThdAmpheres Integer32, eoACPwrQualityThdAmpheres Integer32,
pmACPwrQualityThdVoltage Integer32 eoACPwrQualityThdVoltage Integer32
} }
pmACPwrQualityConfiguration OBJECT-TYPE eoACPwrQualityConfiguration OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
sngl(1), sngl(1),
del(2), del(2),
wye(3) wye(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configuration describes the physical configurations "Configuration describes the physical configurations
of the power supply lines: of the power supply lines:
* alternating current, single phase (SNGL) * alternating current, single phase (SNGL)
* alternating current, three phase delta (DEL) * alternating current, three phase delta (DEL)
* alternating current, three phase Y (WYE) * alternating current, three phase Y (WYE)
Three-phase configurations can be either connected in Three-phase configurations can be either connected in
a triangular delta (DEL) or star Y (WYE) system. WYE a triangular delta (DEL) or star Y (WYE) system. WYE
systems have a shared neutral voltage, while DEL systems have a shared neutral voltage, while DEL
systems do not. Each phase is offset 120 degrees to systems do not. Each phase is offset 120 degrees to
each other." each other."
::= { pmACPwrQualityEntry 1 } ::= { eoACPwrQualityEntry 1 }
pmACPwrQualityAvgVoltage OBJECT-TYPE eoACPwrQualityAvgVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 Volt AC" UNITS "0.1 Volt AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value for average 'instantaneous' RMS line "A measured value for average of the voltage measured
voltage. For a 3-phase system, this is the average over an integral number of AC cycles For a 3-phase
voltage (V1+V2+V3)/3. IEC 61850-7-4 measured value system, this is the average voltage (V1+V2+V3)/3. IEC
attribute 'Vol'" 61850-7-4 measured value attribute 'Vol'"
::= { eoACPwrQualityEntry 2 }
::= { pmACPwrQualityEntry 2 }
pmACPwrQualityAvgCurrent OBJECT-TYPE eoACPwrQualityAvgCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Ampheres" UNITS "Ampheres"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the current per phase. IEC 61850- "A measured value of the current per phase. IEC 61850-
7-4 attribute 'Amp'" 7-4 attribute 'Amp'"
::= { pmACPwrQualityEntry 3 } ::= { eoACPwrQualityEntry 3 }
pmACPwrQualityFrequency OBJECT-TYPE eoACPwrQualityFrequency OBJECT-TYPE
SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz
UNITS "hertz" UNITS "hertz"
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 the basic frequency of the AC
circuit. IEC 61850-7-4 attribute 'Hz'." circuit. IEC 61850-7-4 attribute 'Hz'."
::= { pmACPwrQualityEntry 4 } ::= { eoACPwrQualityEntry 4 }
pmACPwrQualityPowerUnitMultiplier OBJECT-TYPE eoACPwrQualityPowerUnitMultiplier 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
pmACPwrQualityTotalActivePower, eoACPwrQualityTotalActivePower,
pmACPwrQualityTotalReactivePower eoACPwrQualityTotalReactivePower
and pmACPwrQualityTotalApparentPower measurements. For and eoACPwrQualityTotalApparentPower measurements. For
3-phase power systems, this will also include 3-phase power systems, this will also include
pmACPwrQualityPhaseActivePower, eoACPwrQualityPhaseActivePower,
pmACPwrQualityPhaseReactivePower and eoACPwrQualityPhaseReactivePower and
pmACPwrQualityPhaseApparentPower" eoACPwrQualityPhaseApparentPower"
::= { pmACPwrQualityEntry 5 } ::= { eoACPwrQualityEntry 5 }
pmACPwrQualityPowerAccuracy OBJECT-TYPE eoACPwrQualityPowerAccuracy 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
"This object indicates a percentage value, in 100ths of "This object indicates a percentage value, in 100ths of
a percent, representing the presumed accuracy of a percent, representing the presumed accuracy of
active, reactive, and apparent power usage reporting. active, reactive, and apparent power usage reporting.
For example: 1010 means the reported usage is accurate For example: 1010 means the reported usage is accurate
to +/- 10.1 percent. This value is zero if the to +/- 10.1 percent. This value is zero if the
accuracy is unknown. accuracy is unknown.
ANSI and IEC define the following accuracy classes for ANSI and IEC define the following accuracy classes for
power measurement: IEC 62053-22 & 60044-1 class 0.1, power measurement: IEC 62053-22 & 60044-1 class 0.1,
0.2, 0.5, 1 & 3. 0.2, 0.5, 1 & 3.
ANSI C12.20 class 0.2 & 0.5" ANSI C12.20 class 0.2 & 0.5"
::= { pmACPwrQualityEntry 6 } ::= { eoACPwrQualityEntry 6 }
pmACPwrQualityTotalActivePower OBJECT-TYPE eoACPwrQualityTotalActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "RMS watts" UNITS " watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the actual power delivered to or "A measured value of the actual power delivered to or
consumed by the load. IEC 61850-7-4 attribute 'TotW'." consumed by the load. IEC 61850-7-4 attribute 'TotW'."
::= { pmACPwrQualityEntry 7 } ::= { eoACPwrQualityEntry 7 }
pmACPwrQualityTotalReactivePower OBJECT-TYPE eoACPwrQualityTotalReactivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes reactive" UNITS "volt-amperes reactive"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A mesured value of the reactive portion of the "A mesured value of the reactive portion of the
apparent power. IEC 61850-7-4 attribute 'TotVAr'." apparent power. IEC 61850-7-4 attribute 'TotVAr'."
::= { pmACPwrQualityEntry 8 } ::= { eoACPwrQualityEntry 8 }
pmACPwrQualityTotalApparentPower OBJECT-TYPE eoACPwrQualityTotalApparentPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes"
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 voltage and current which
determines the apparent power. The apparent power is determines the apparent power. The apparent power is
the vector sum of real and reactive power. the vector sum of real and reactive power.
Note: watts and volt-ampheres are equivalent units and Note: watts and volt-ampheres are equivalent units and
may be combined. IEC 61850-7-4 attribute 'TotVA'." may be combined. IEC 61850-7-4 attribute 'TotVA'."
::= { pmACPwrQualityEntry 9 } ::= { eoACPwrQualityEntry 9 }
pmACPwrQualityTotalPowerFactor OBJECT-TYPE eoACPwrQualityTotalPowerFactor OBJECT-TYPE
SYNTAX Integer32 (-10000..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
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 ratio of the real power flowing to
the load versus the apparent power. It is dimensionless the load versus the apparent power. It is dimensionless
and expressed here as a percentage value in 100ths of a and expressed here as a percentage value in 100ths of a
percent. A power factor of 100% indicates there is no percent. A power factor of 100% indicates there is no
inductance load and thus no reactive power. Power inductance load and thus no reactive power. Power
Factor can be positive or negative, where the sign Factor can be positive or negative, where the sign
should be in lead/lag (IEEE) form. IEC 61850-7-4 should be in lead/lag (IEEE) form. IEC 61850-7-4
attribute 'TotPF'." attribute 'TotPF'."
::= { pmACPwrQualityEntry 10 } ::= { eoACPwrQualityEntry 10 }
pmACPwrQualityThdAmpheres OBJECT-TYPE eoACPwrQualityThdAmpheres 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 current 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 'ThdAmp'." specified. IEC 61850-7-4 attribute 'ThdAmp'."
::= { pmACPwrQualityEntry 11 } ::= { eoACPwrQualityEntry 11 }
pmACPwrQualityThdVoltage OBJECT-TYPE eoACPwrQualityThdVoltage 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 voltage 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 'ThdVol'."
::= { pmACPwrQualityEntry 12 } ::= { eoACPwrQualityEntry 12 }
pmACPwrQualityPhaseTable OBJECT-TYPE eoACPwrQualityPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmACPwrQualityPhaseEntry SYNTAX SEQUENCE OF EoACPwrQualityPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes 3-phase power quality "This table describes 3-phase power quality
measurements. It is a sparse extension of the measurements. It is a sparse extension of the
pmACPwrQualityTable." eoACPwrQualityTable."
::= { powerQualityMIBObjects 2 } ::= { powerQualityMIBObjects 2 }
pmACPwrQualityPhaseEntry OBJECT-TYPE eoACPwrQualityPhaseEntry OBJECT-TYPE
SYNTAX PmACPwrQualityPhaseEntry SYNTAX EoACPwrQualityPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes common 3-phase power quality "An entry describes common 3-phase power quality
measurements. measurements.
This optional table describes 3-phase power quality This optional table describes 3-phase power quality
measurements, with three entries for each supported measurements, with three entries for each supported
pmPowerIndex entity. Entities having single phase eoPowerIndex entity. Entities having single phase
power shall not have any entities. power shall not have any entities.
This table describes attributes common to both WYE and This table describes attributes common to both WYE and
DEL. Entities having single phase power shall not have DEL. Entities having single phase power shall not have
any entries here. It is a sparse extension of the any entries here. It is a sparse extension of the
pmACPwrQualityTable. eoACPwrQualityTable.
These attributes correspond to IEC 61850-7.4 MMXU phase These attributes correspond to IEC 61850-7.4 MMXU phase
measurements." measurements."
INDEX { pmPowerIndex, pmPhaseIndex } INDEX { eoPowerIndex, eoPhaseIndex }
::= { pmACPwrQualityPhaseTable 1 } ::= { eoACPwrQualityPhaseTable 1 }
PmACPwrQualityPhaseEntry ::= SEQUENCE { EoACPwrQualityPhaseEntry ::= SEQUENCE {
pmPhaseIndex Integer32, eoPhaseIndex Integer32,
pmACPwrQualityPhaseAvgCurrent Integer32, eoACPwrQualityPhaseAvgCurrent Integer32,
pmACPwrQualityPhaseActivePower Integer32, eoACPwrQualityPhaseActivePower Integer32,
pmACPwrQualityPhaseReactivePower Integer32, eoACPwrQualityPhaseReactivePower Integer32,
pmACPwrQualityPhaseApparentPower Integer32, eoACPwrQualityPhaseApparentPower Integer32,
pmACPwrQualityPhasePowerFactor Integer32, eoACPwrQualityPhasePowerFactor Integer32,
pmACPwrQualityPhaseImpedance Integer32 eoACPwrQualityPhaseImpedance Integer32
} }
pmPhaseIndex OBJECT-TYPE eoPhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359) SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240." "A phase angle typically corresponding to 0, 120, 240."
::= { pmACPwrQualityPhaseEntry 1 } ::= { eoACPwrQualityPhaseEntry 1 }
pmACPwrQualityPhaseAvgCurrent OBJECT-TYPE eoACPwrQualityPhaseAvgCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Ampheres" UNITS "Ampheres"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the current per phase. IEC 61850- "A measured value of the current per phase. IEC 61850-
7-4 attribute 'A'" 7-4 attribute 'A'"
::= { pmACPwrQualityPhaseEntry 2 } ::= { eoACPwrQualityPhaseEntry 2 }
pmACPwrQualityPhaseActivePower OBJECT-TYPE eoACPwrQualityPhaseActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "RMS watts" UNITS " watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the actual power delivered to or "A measured value of the actual power delivered to or
consumed by the load. IEC 61850-7-4 attribute 'W'" consumed by the load. IEC 61850-7-4 attribute 'W'"
::= { pmACPwrQualityPhaseEntry 3 } ::= { eoACPwrQualityPhaseEntry 3 }
pmACPwrQualityPhaseReactivePower OBJECT-TYPE eoACPwrQualityPhaseReactivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes reactive" UNITS "volt-amperes reactive"
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 reactive portion of the
apparent power. IEC 61850-7-4 attribute 'VAr'" apparent power. IEC 61850-7-4 attribute 'VAr'"
::= { pmACPwrQualityPhaseEntry 4 } ::= { eoACPwrQualityPhaseEntry 4 }
pmACPwrQualityPhaseApparentPower OBJECT-TYPE eoACPwrQualityPhaseApparentPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes"
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 voltage and current determines
the apparent power. Active plus reactive power equals the apparent power. Active plus reactive power equals
the total apparent powwer. the total apparent powwer.
Note: Watts and volt-ampheres are equivalent units and Note: Watts and volt-ampheres are equivalent units and
may be combined. IEC 61850-7-4 attribute 'VA'." may be combined. IEC 61850-7-4 attribute 'VA'."
::= { pmACPwrQualityPhaseEntry 5 } ::= { eoACPwrQualityPhaseEntry 5 }
pmACPwrQualityPhasePowerFactor OBJECT-TYPE eoACPwrQualityPhasePowerFactor OBJECT-TYPE
SYNTAX Integer32 (-10000..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
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 ratio of the real power flowing to
the load versus the apparent power for this phase. IEC the load versus the apparent power for this phase. IEC
61850-7-4 attribute 'PF'. Power Factor can be positive 61850-7-4 attribute 'PF'. Power Factor can be positive
or negative where the sign should be in lead/lag (IEEE) or negative where the sign should be in lead/lag (IEEE)
form." form."
::= { pmACPwrQualityPhaseEntry 6 } ::= { eoACPwrQualityPhaseEntry 6 }
pmACPwrQualityPhaseImpedance OBJECT-TYPE eoACPwrQualityPhaseImpedance OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the impedance. IEC 61850-7-4 attribute "A measured value of the impedance. IEC 61850-7-4 attribute
'Z'." 'Z'."
::= { pmACPwrQualityPhaseEntry 7 } ::= { eoACPwrQualityPhaseEntry 7 }
pmACPwrQualityDelPhaseTable OBJECT-TYPE eoACPwrQualityDelPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmACPwrQualityDelPhaseEntry SYNTAX SEQUENCE OF EoACPwrQualityDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes DEL configuration phase-to-phase "This table describes DEL configuration phase-to-phase
power quality measurements. This is a sparse extension power quality measurements. This is a sparse extension
of the pmACPwrQualityPhaseTable." of the eoACPwrQualityPhaseTable."
::= { powerQualityMIBObjects 3 } ::= { powerQualityMIBObjects 3 }
pmACPwrQualityDelPhaseEntry OBJECT-TYPE eoACPwrQualityDelPhaseEntry OBJECT-TYPE
SYNTAX PmACPwrQualityDelPhaseEntry SYNTAX EoACPwrQualityDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes quality attributes of a phase in a "An entry describes quality attributes of a phase in a
DEL 3-phase power system. Voltage measurements are DEL 3-phase power system. Voltage measurements are
provided both relative to each other and zero. provided both relative to each other and zero.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects. MHAI objects.
For phase-to-phase measurements, the pmPhaseIndex is For phase-to-phase measurements, the eoPhaseIndex is
compared against the following phase at +120 degrees. compared against the following phase at +120 degrees.
Thus, the possible values are: Thus, the possible values are:
pmPhaseIndex Next Phase Angle eoPhaseIndex Next Phase Angle
0 120 0 120
120 240 120 240
240 0 240 0
" "
INDEX { pmPowerIndex, pmPhaseIndex} INDEX { eoPowerIndex, eoPhaseIndex}
::= { pmACPwrQualityDelPhaseTable 1} ::= { eoACPwrQualityDelPhaseTable 1}
PmACPwrQualityDelPhaseEntry ::= SEQUENCE { EoACPwrQualityDelPhaseEntry ::= SEQUENCE {
pmACPwrQualityDelPhaseToNextPhaseVoltage Integer32, eoACPwrQualityDelPhaseToNextPhaseVoltage Integer32,
pmACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, eoACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32,
pmACPwrQualityDelThdCurrent Integer32 eoACPwrQualityDelThdCurrent Integer32
} }
pmACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 Volt 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 to next phase voltages, where "A measured value of phase to next phase voltages, where
the next phase is IEC 61850-7-4 attribute 'PPV'." the next phase is IEC 61850-7-4 attribute 'PPV'."
::= { pmACPwrQualityDelPhaseEntry 2 } ::= { eoACPwrQualityDelPhaseEntry 2 }
pmACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrQualityDelThdPhaseToNextPhaseVoltage 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 voltage total harmonic
disortion for phase to next phase. Method of calculation disortion for phase to next phase. Method of calculation
is not specified. IEC 61850-7-4 attribute 'ThdPPV'." is not specified. IEC 61850-7-4 attribute 'ThdPPV'."
::= { pmACPwrQualityDelPhaseEntry 3 } ::= { eoACPwrQualityDelPhaseEntry 3 }
pmACPwrQualityDelThdCurrent OBJECT-TYPE eoACPwrQualityDelThdCurrent 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 voltage total harmonic
disortion (THD) for phase to phase. Method of disortion (THD) for phase to phase. Method of
calculation is not specified. calculation is not specified.
IEC 61850-7-4 attribute 'ThdPPV'." IEC 61850-7-4 attribute 'ThdPPV'."
::= { pmACPwrQualityDelPhaseEntry 4 } ::= { eoACPwrQualityDelPhaseEntry 4 }
pmACPwrQualityWyePhaseTable OBJECT-TYPE eoACPwrQualityWyePhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF PmACPwrQualityWyePhaseEntry SYNTAX SEQUENCE OF EoACPwrQualityWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes WYE configuration phase-to-neutral "This table describes WYE configuration phase-to-neutral
power quality measurements. This is a sparse extension power quality measurements. This is a sparse extension
of the pmACPwrQualityPhaseTable." of the eoACPwrQualityPhaseTable."
::= { powerQualityMIBObjects 4 } ::= { powerQualityMIBObjects 4 }
pmACPwrQualityWyePhaseEntry OBJECT-TYPE eoACPwrQualityWyePhaseEntry OBJECT-TYPE
SYNTAX PmACPwrQualityWyePhaseEntry SYNTAX EoACPwrQualityWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes measurements of WYE configuration "This table describes measurements of WYE configuration
with phase to neutral power quality attributes. Three with phase to neutral power quality attributes. Three
entries are required for each supported pmPowerIndex entries are required for each supported eoPowerIndex
entry. Voltage measurements are relative to neutral. entry. Voltage measurements are relative to neutral.
This is a sparse extension of the This is a sparse extension of the
pmACPwrQualityPhaseTable. eoACPwrQualityPhaseTable.
Each entry describes quality attributes of one phase of Each entry describes quality attributes of one phase of
a WYE 3-phase power system. a WYE 3-phase power system.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects." MHAI objects."
INDEX { pmPowerIndex, pmPhaseIndex } INDEX { eoPowerIndex, eoPhaseIndex }
::= { pmACPwrQualityWyePhaseTable 1} ::= { eoACPwrQualityWyePhaseTable 1}
PmACPwrQualityWyePhaseEntry ::= SEQUENCE { EoACPwrQualityWyePhaseEntry ::= SEQUENCE {
pmACPwrQualityWyePhaseToNeutralVoltage Integer32, eoACPwrQualityWyePhaseToNeutralVoltage Integer32,
pmACPwrQualityWyePhaseCurrent Integer32, eoACPwrQualityWyePhaseCurrent Integer32,
pmACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 eoACPwrQualityWyeThdPhaseToNeutralVoltage Integer32
} }
pmACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE eoACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 Volt 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 to neutral voltage. IEC "A measured value of phase to neutral voltage. IEC
61850-7-4 attribute 'PhV'." 61850-7-4 attribute 'PhV'."
::= { pmACPwrQualityWyePhaseEntry 1 } ::= { eoACPwrQualityWyePhaseEntry 1 }
pmACPwrQualityWyePhaseCurrent OBJECT-TYPE eoACPwrQualityWyePhaseCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 ampheres AC" UNITS "0.1 ampheres 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 currents. IEC 61850-7-4
attribute 'A'." attribute 'A'."
::= { pmACPwrQualityWyePhaseEntry 2 } ::= { eoACPwrQualityWyePhaseEntry 2 }
pmACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value of the voltage total harmonic "A calculated value of the voltage total harmonic
distortion (THD) for phase to neutral. IEC 61850-7-4 distortion (THD) for phase to neutral. IEC 61850-7-4
attribute 'ThdPhV'." attribute 'ThdPhV'."
::= { pmACPwrQualityWyePhaseEntry 3 } ::= { eoACPwrQualityWyePhaseEntry 3 }
-- Conformance -- Conformance
powerQualityMIBCompliances OBJECT IDENTIFIER powerQualityMIBCompliances OBJECT IDENTIFIER
::= { powerQualityMIB 2 } ::= { powerQualityMIB 2 }
powerQualityMIBGroups OBJECT IDENTIFIER powerQualityMIBGroups OBJECT IDENTIFIER
::= { powerQualityMIB 3 } ::= { powerQualityMIB 3 }
powerQualityMIBFullCompliance MODULE-COMPLIANCE powerQualityMIBFullCompliance MODULE-COMPLIANCE
skipping to change at page 64, line 45 skipping to change at page 68, line 4
GROUP powerACPwrQualityWyePhaseMIBTableGroup GROUP powerACPwrQualityWyePhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"This group must only be implemented for a WYE phase "This group must only be implemented for a WYE phase
configuration." configuration."
::= { powerQualityMIBCompliances 1 } ::= { powerQualityMIBCompliances 1 }
-- Units of Conformance -- Units of Conformance
powerACPwrQualityMIBTableGroup OBJECT-GROUP powerACPwrQualityMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object pmPowerIndex is NOT -- Note that object eoPowerIndex is NOT
-- included since it is not-accessible -- included since it is not-accessible
pmACPwrQualityConfiguration, eoACPwrQualityConfiguration,
pmACPwrQualityAvgVoltage, eoACPwrQualityAvgVoltage,
pmACPwrQualityAvgCurrent, eoACPwrQualityAvgCurrent,
pmACPwrQualityFrequency, eoACPwrQualityFrequency,
pmACPwrQualityPowerUnitMultiplier, eoACPwrQualityPowerUnitMultiplier,
pmACPwrQualityPowerAccuracy, eoACPwrQualityPowerAccuracy,
pmACPwrQualityTotalActivePower, eoACPwrQualityTotalActivePower,
pmACPwrQualityTotalReactivePower, eoACPwrQualityTotalReactivePower,
pmACPwrQualityTotalApparentPower, eoACPwrQualityTotalApparentPower,
pmACPwrQualityTotalPowerFactor, eoACPwrQualityTotalPowerFactor,
pmACPwrQualityThdAmpheres, eoACPwrQualityThdAmpheres,
pmACPwrQualityThdVoltage eoACPwrQualityThdVoltage
} STATUS current } STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
quality objects related to the Power Monitor." quality objects related to the Energy Object."
::= { powerQualityMIBGroups 1 } ::= { powerQualityMIBGroups 1 }
powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object pmPowerIndex is NOT -- Note that object eoPowerIndex is NOT
-- included since it is not-accessible -- included since it is not-accessible
pmACPwrQualityPhaseAvgCurrent, eoACPwrQualityPhaseAvgCurrent,
pmACPwrQualityPhaseActivePower, eoACPwrQualityPhaseActivePower,
pmACPwrQualityPhaseReactivePower, eoACPwrQualityPhaseReactivePower,
pmACPwrQualityPhaseApparentPower, eoACPwrQualityPhaseApparentPower,
pmACPwrQualityPhasePowerFactor, eoACPwrQualityPhasePowerFactor,
pmACPwrQualityPhaseImpedance eoACPwrQualityPhaseImpedance
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all 3-phase power "This group contains the collection of all 3-phase power
quality objects related to the Power State." quality objects related to the Power State."
::= { powerQualityMIBGroups 2 } ::= { powerQualityMIBGroups 2 }
powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object pmPowerIndex and -- Note that object eoPowerIndex and
-- pmPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
pmACPwrQualityDelPhaseToNextPhaseVoltage , eoACPwrQualityDelPhaseToNextPhaseVoltage ,
pmACPwrQualityDelThdPhaseToNextPhaseVoltage, eoACPwrQualityDelThdPhaseToNextPhaseVoltage,
pmACPwrQualityDelThdCurrent eoACPwrQualityDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all quality "This group contains the collection of all quality
attributes of a phase in a DEL 3-phase power system." attributes of a phase in a DEL 3-phase power system."
::= { powerQualityMIBGroups 3 } ::= { powerQualityMIBGroups 3 }
powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object pmPowerIndex and -- Note that object eoPowerIndex and
-- pmPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
pmACPwrQualityWyePhaseToNeutralVoltage, eoACPwrQualityWyePhaseToNeutralVoltage,
pmACPwrQualityWyePhaseCurrent, eoACPwrQualityWyePhaseCurrent,
pmACPwrQualityWyeThdPhaseToNeutralVoltage eoACPwrQualityWyeThdPhaseToNeutralVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all WYE "This group contains the collection of all WYE
configuration phase-to-neutral power quality configuration phase-to-neutral power quality
measurements." measurements."
::= { powerQualityMIBGroups 4 } ::= { powerQualityMIBGroups 4 }
END END
skipping to change at page 66, line 38 skipping to change at page 69, line 44
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 pmPowerOperState (via - Unauthorized changes to the eoPowerOperState (via
thepmPowerAdminState ) MAY disrupt the power settings of the theeoPowerAdminState ) MAY disrupt the power settings of the
different Power Monitors, and therefore the state of differentEnergy Objects, and therefore the state of
functionality of the respective Power Monitors. functionality of the respective Energy Objects.
- Unauthorized changes to the pmEnergyParametersTable MAY - Unauthorized changes to the eoEnergyParametersTable MAY
disrupt energy measurement in the pmEnergyTable 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
skipping to change at page 67, line 28 skipping to change at page 70, line 34
12. IANA Considerations 12. IANA Considerations
12.1. IANA Considerations for the MIB Modules 12.1. IANA Considerations for the MIB Modules
The MIB modules in this document uses the following IANA- The MIB modules in this document uses the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
PowerMonitorMIB { mib-2 xxx } energyObjectMib { mib-2 xxx }
powerQualityMIB { mib-2 yyy } powerQualityMIB { mib-2 yyy }
Additions to the MIB modules are subject to Expert Review Additions to the MIB modules are subject to Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested MIB objects for completeness and accuracy of the requested MIB objects for completeness and accuracy of the
description. Requests for MIB objects that duplicate the description. Requests for MIB objects that duplicate the
functionality of existing objects SHOULD be declined. The functionality of existing objects SHOULD be declined. The
smallest available OIDs SHOULD be assigned to the new MIB smallest available OIDs SHOULD be assigned to the new MIB
objects. The specification of new MIB objects SHOULD follow the objects. The specification of new MIB objects SHOULD follow the
structure specified in Section 10. and MUST be published using structure specified in Section 10. and MUST be published using
a well-established and persistent publication medium. a well-established and persistent publication medium.
12.2. IANA Registration of new Power State Set 12.2. IANA Registration of new Power State Set
This document specifies an initial set of Power State Sets. The This document specifies an initial set of Power State Sets. The
list of these Power State Sets with their numeric identifiers is list of these Power State Sets with their numeric identifiers is
given in Section 5.2.1. The Internet Assigned Numbers Authority given in Section 5.2.1. IANA maintains a Textual Convention
(IANA) has created a new registry for Power State Sets numeric IANAPowerStateSet with the initial set of Power State Sets and
identifiers and filled it with the initial list as in Section the Power States within those Power State Sets. The current
5.2.1. New Assignments to Power State Sets shall be version of Textual convention can be accessed
administered by IANA and the guidelines and procedures are http://www.iana.org/assignments/IANAPowerStateSet
listed in this Section.
New Assignments to Power State Sets shall be administered by
IANA and the guidelines and procedures are listed in this
Section.
New assignments for Power State Set will be administered by IANA New assignments for Power State Set will be administered by IANA
through Expert Review [RFC5226], i.e., review by one of a group through Expert Review [RFC5226], i.e., review by one of a group
of experts designated by an IETF Area Director. The group of of experts designated by an IETF Area Director. The group of
experts MUST check the requested state for completeness and experts MUST check the requested state for completeness and
accuracy of the description. A pure vendor specific accuracy of the description. A pure vendor specific
implementation of Power State Set shall not be adopted; since it implementation of Power State Set shall not be adopted; since it
would lead to proliferation of Power State Sets. would lead to proliferation of Power State Sets.
12.2.1. IANA Registration of the IEEE1621 Power State Set 12.2.1. IANA Registration of the IEEE1621 Power State Set
This document specifies a set of values for the IEEE1621 Power This document specifies a set of values for the IEEE1621 Power
State Set [IEEE1621]. The list of these values with their State Set [IEEE1621]. The list of these values with their
identifiers is given in Section 5.2.1. The Internet Assigned identifiers is given in Section 5.2.1. The Internet Assigned
Numbers Authority (IANA) created a new registry for IEEE1621 Numbers Authority (IANA) created a new registry for IEEE1621
Power State Set identifiers and filled it with the initial list Power State Set identifiers and filled it with the initial
in Section 5.2.2. listin the Textual Convention IANAPowerStateSet..
New assignments (or potentially deprecation) for IEEE1621 Power New assignments (or potentially deprecation) for IEEE1621 Power
State Set will be administered by IANA through Expert Review State Set will be administered by IANA through Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested state for completeness and accuracy of the requested state for completeness and accuracy of the
description. description.
12.2.2. IANA Registration of the DMTF Power State Set 12.2.2. IANA Registration of the DMTF Power State Set
This document specifies a set of values for the DMTF Power State This document specifies a set of values for the DMTF Power State
Set. The list of these values with their identifiers is given Set. The list of these values with their identifiers is given
in Section 5.2.1. The Internet Assigned Numbers Authority in Section 5.2.1. The Internet Assigned Numbers Authority
(IANA) has created a new registry for DMTF Power State Set (IANA) has created a new registry for DMTF Power State Set
identifiers and filled it with the initial list in Section identifiers and filled it with the initial list in the Textual
5.2.1. Convention IANAPowerStateSet.
New assignments (or potentially deprecation) for DMTF Power New assignments (or potentially deprecation) for DMTF Power
State Set will be administered by IANA through Expert Review State Set will be administered by IANA through Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
conformance with the DMTF standard [DMTF], on the top of conformance with the DMTF standard [DMTF], on the top of
checking for completeness and accuracy of the description. checking for completeness and accuracy of the description.
12.2.3. IANA Registration of the EMAN Power State Set 12.2.3. IANA Registration of the EMAN Power State Set
This document specifies a set of values for the EMAN Power State This document specifies a set of values for the EMAN Power State
Set. The list of these values with their identifiers is given Set. The list of these values with their identifiers is given
in Section 5.2.1. The Internet Assigned Numbers Authority in Section 5.2.1. The Internet Assigned Numbers Authority
(IANA) has created a new registry for EMAN Power State Set (IANA) has created a new registry for EMAN Power State Set
identifiers and filled it with the initial list in Section identifiers and filled it with the initial list in the Textual
5.2.1. Convention IANAPowerStateSet.
New assignments (or potentially deprecation) for EMAN Power New assignments (or potentially deprecation) for EMAN Power
State Set will be administered by IANA through Expert Review State Set will be administered by IANA through Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested state for completeness and accuracy of the requested state for completeness and accuracy of the
description. description.
12. Contributors 12. Contributors
This document results from the merger of two initial proposals. This document results from the merger of two initial proposals.
skipping to change at page 69, line 39 skipping to change at page 73, line 5
Rolf Winter Rolf Winter
Dominique Dudkowski Dominique Dudkowski
13. Acknowledgment 13. Acknowledgment
The authors would like to thank Shamita Pisal for her prototype The authors would like to thank Shamita Pisal for her prototype
of this MIB module, and her valuable feedback. The authors of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically. would like to Michael Brown for improving the text dramatically.
We would like to thank Juergen Schoenwalder for proposing the
design of the Textual Convention for IANAPowerStateSet and Ira
McDonald for his feedback.
14. Open Issues 14. Open Issues
OPEN ISSUE 1 : Double-check all the IEC references in the draft. OPEN ISSUE 1 : Double-check all the IEC references in the draft.
IEC 61850-7-4 has been widely referenced in many EMAN drafts. IEC 61850-7-4 has been widely referenced in many EMAN drafts.
The other IEC references suggested in the email list are: The other IEC references suggested in the email list are
IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is
important to resolve the correct IEC references soon. important to resolve the correct IEC references soon.
OPEN ISSUE 2 : Description clause of pmPowerIndex. Do we need OPEN ISSUE 2 : Description clause of eoPowerIndex. Do we need
this text ? Juergen Quittek to comment: this text ? Juergen Quittek to comment:
"The identity provisioning method that has been chosen can be "The identity provisioning method that has been chosen can be
retrieved by reading the value of powerStateEnergyConsumerOid. retrieved by reading the value of powerStateEnergyConsumerOid.
In case of identities provided by the ENERGY-AWARE-MIB module, In case of identities provided by the ENERGY-AWARE-MIB module,
this OID points to an exising instance of pmPowerIndex, in this OID points to an exising instance of eoPowerIndex, in
case of the ENTITY MIB, the object points to a valid instance case of the ENTITY MIB, the object points to a valid instance
of entPhysicalIndex, and in a similar way, it points to a of entPhysicalIndex, and in a similar way, it points to a
value of another MIB module if this is used for identifying value of another MIB module if this is used for identifying
entities. If no other MIB module has been chosen for providing entities. If no other MIB module has been chosen for providing
entity identities, then the value of entity identities, then the value of
powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero). powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero).
OPEN ISSUE 3: Textual convention for Power State Set OPEN ISSUE 3: Time Series of measurements required ? Mechanism
PowerStateSeries ::= TEXTUAL-CONVENTION
Why is this an OCTET STRING (SIZE(1)) and not simply an
enumerated INTEGER? And if this is to be maintained by IANA,
why not create a IANA-POWER-SERIES-TC MIB module so that one
can simply fetch the latest version from IANA?
Discussion is ongoing in the EMAN email list on the design of
the TC and IANA registration.
OPEN ISSUE 4: pmPowerEntry table has MIB objects which are
common across multiple Power State Sets.
This issue shall be fixed in the next revision of the draft.
OPEN ISSUE 5: TimeStamps for Power measurements required ?
OPEN ISSUE 6: Measurement of AC Power, Voltage, and Current
"AC power is not an RMS measurement, it is an average reading.
The term instantaneous AC power can be misleading and power
meters do not report it. "
Description clause of MIB objects pmPower,
pmACPwrQualityAvgVoltage, pmACPwrQualityAvgCurrent to be
updated. Sent email to Michael Suchoff for some text.
OPEN ISSUE 7: In addition to WYE and Delta AC power
configurations, 3-Phase hybrid of WYE and Delta should be
considered ?
Need more information on the hybrid of WYE and Delta
configuration. Email seeking clarification sent to Michael
Suchoff.
OPEN ISSUE 8: Nameplate power consumption should be a fixed
value or a range ?
Presently, Nameplate power consumption contains the max value
of power consumption (watts) of the device; useful for power
planning purposes. The voltage range can be useful for power
supply specification.
OPEN ISSUE 9: AC data center management is detection of tripped
circuit breakers, not covered in the MIB draft.
Are Circuit breakers in scope of EMAN ?
OPEN ISSUE 10: Time Series of measurements required ? Mechanism
pull or push ? What shall the table consist of ? pull or push ? What shall the table consist of ?
Power, Voltage, Current, Energy and Demand Power, Voltage, Current, Energy and Demand.
Discussion on the email list. Based on requirements with the
need for time series for Power, may need to be considered for
the MIB.
OPEN ISSUE 11: Demand computation method OPEN ISSUE 4: Demand computation method
"Energy not obtained by periodically polling a power "Energy not obtained by periodically polling a power
measurement with a pmEnergyParametersSampleRate ; Energy (E) measurement with a eoEnergyParametersSampleRate ; Energy (E)
is measured to the product's certified IEC 62053-21 accuracy is measured to the product's certified IEC 62053-21 accuracy
class" class"
Need to verify with IEC62053-21. Need to verify with IEC62053-21.
OPEN ISSUE 12: Consideration of IEEE-ISTO PWG in the IANA list OPEN ISSUE 5: Consideration of IEEE-ISTO PWG in the IANA list of
of Power State Set ? PWG Imaging Systems Power Management MIB Power State Set ? Printer Power series could be added once the
reference. IANA procedure is in place.
OPEN ISSUE 13: check if all the requirements from [EMAN-REQ] are OPEN ISSUE 6: check if all the requirements from [EMAN-REQ] are
covered. covered.
OPEN ISSUE 14: Required Information on Powered Entities
It would be helpful to identify variables that are static vs.
those that are dynamic. There are some that are absolutely
static, and others that just rarely change.
15. References 15. References
15.2. Normative References 15.2. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [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
 End of changes. 459 change blocks. 
1052 lines changed or deleted 1116 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/