draft-ietf-eman-energy-monitoring-mib-03.txt   draft-ietf-eman-energy-monitoring-mib-04.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: January 12, 2013 Independent Consultant Expires: April 22, 2013 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.
July 11, 2012 October 22, 2012
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-03 draft-ietf-eman-energy-monitoring-mib-04
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 1, line 39 skipping to change at page 1, line 39
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html at http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 2013. This Internet-Draft will expire on April 2013.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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........... 6 5. Architecture Concepts Applied to the MIB Module.......... 6
5.1. Energy Object Information............................... 13 5.1. Energy Object Information............................. 13
5.2. Power State............................................. 13 5.2. Power State........................................... 14
5.2.1. Power State Set................................. 14 5.2.1. Power State Set................................15
5.2.2. IEEE1621 Power State Set........................ 15 5.2.2. IEEE1621 Power State Set.......................15
5.2.3. DMTF Power State Set............................ 15 5.2.3. DMTF Power State Set...........................15
5.2.4. EMAN Power State Set............................ 16 5.2.4. EMAN Power State Set...........................17
5.3. Energy Object Usage Information......................... 19 5.3. Energy Object Usage Information....................... 19
5.4. Optional Power Usage Characteristics.................... 20 5.4. Optional Power Usage Characteristics.................. 20
5.5. Optional Energy Measurement............................. 21 5.5. Optional Energy Measurement........................... 21
5.6. Fault Management........................................ 25 5.6. Fault Management...................................... 25
6. Discovery................................................. 25 6. Discovery............................................... 26
7. Link with the other IETF MIBs............................. 26 7. Link with the other IETF MIBs........................... 27
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB... 26 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..27
7.2. Link with the ENTITY-STATE MIB....................... 27 7.2. Link with the ENTITY-STATE MIB......................28
7.3. Link with the POWER-OVER-ETHERNET MIB................ 28 7.3. Link with the POWER-OVER-ETHERNET MIB...............28
7.4. Link with the UPS MIB................................ 29 7.4. Link with the UPS MIB...............................29
7.5. Link with the LLDP and LLDP-MED MIBs................. 30 7.5. Link with the LLDP and LLDP-MED MIBs................30
8. Implementation Scenario................................... 30 8. Implementation Scenario................................. 31
9. Structure of the MIB...................................... 33 9. Structure of the MIB.................................... 33
10. MIB Definitions.......................................... 34 10. MIB Definitions........................................ 34
11. Security Considerations.................................. 73 11. Security Considerations................................ 74
12. IANA Considerations...................................... 74 12. IANA Considerations.................................... 75
12.1. IANA Considerations for the MIB Modules................ 74 12.1. IANA Considerations for the MIB Modules.............. 75
12.2. IANA Registration of new Power State Set............... 75 12.2. IANA Registration of new Power State Set............. 76
12.2.1. IANA Registration of the IEEE1621 Power State Set 75 12.2.1. IANA Registration of the IEEE1621 Power State Set 76
12.2.2. IANA Registration of the DMTF Power State Set.... 75 12.2.2. IANA Registration of the DMTF Power State Set.... 77
12.2.3. IANA Registration of the EMAN Power State Set.... 76 12.2.3. IANA Registration of the EMAN Power State Set.... 77
12.3. Updating the Registration of Existing Power State Sets. 76 12.3. Updating the Registration of Existing Power State
12. Contributors............................................. 77 Sets....................................................... 77
13. Acknowledgment........................................... 77 12. Contributors........................................... 78
14. Open Issues.............................................. 77 13. Acknowledgment......................................... 78
15. References............................................... 78 14. Open Issues............................................ 78
15.2. Normative References................................ 78 15. References............................................. 79
15.3. Informative References.............................. 78 15.2. Normative References...............................79
15.3. Informative References.............................79
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 Energy of networked elements. This MIB takes into account the Energy
Management Framework [EMAN-FRAMEWORK], which in turn, is based Management Framework [EMAN-FMWK], which in turn, is based on the
on the Requirements for Energy Management[EMAN-REQ]. 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. Target devices and the use cases servers, sensor proxies, etc. Target devices and the use cases
for Energy Management are discussed in Energy Management for Energy Management are discussed in Energy Management
Applicability Statement [EMAN-AS]. Applicability Statement [EMAN-AS].
skipping to change at page 5, line 9 skipping to change at page 5, line 9
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.
4. Terminology 4. Terminology
Please refer to [EMAN-FRAMEWORK] for the definitions of the Please refer to [EMAN-FMWK] for the definitions of the
following terminology used in this draft. following terminology used in this draft.
Device Device
Component Component
Energy Management Energy Management
Energy Management System (EnMS) Energy Management System (EnMS)
skipping to change at page 6, line 37 skipping to change at page 6, line 37
Power State Power State
Power State Set Power State Set
Nameplate Power Nameplate Power
5. Architecture Concepts Applied to the MIB Module 5. Architecture Concepts Applied to the MIB Module
This section describes the concepts specified in the Energy This section describes the concepts specified in the Energy
Management Framework [EMAN-FRAMEWORK] that pertain to power Management Framework [EMAN-FMWK] that pertain to power usage,
usage, with specific information related to the MIB module with specific information related to the MIB module specified in
specified in this document. This subsection maps to the section 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-FMWK].
The Energy Monitoring MIB has 2 independent MIB modules. The The Energy Monitoring MIB has 2 independent MIB modules. The
first MIB module energyObjectMib is focused on measurement of first MIB module energyObjectMib is focused on measurement of
power and energy. The second MIB module powerCharMIB is focused power and energy. The second MIB module powerCharMIB is focused
on Power Characteristics measurements. on Power Characteristics measurements.
The energyObjectMib MIB module consists of four tables. The The energyObjectMib MIB module consists of four tables. The
first table eoPowerTable is indexed by entPhysicalIndex. The first table eoPowerTable is indexed by entPhysicalIndex. The
second table eoPowerStateTable indexed by entPhysicalIndex, second table eoPowerStateTable indexed by entPhysicalIndex,
and eoPowerStateIndex. The eoEnergyParametersTable is indexed and eoPowerStateIndex. The eoEnergyParametersTable is indexed
skipping to change at page 7, line 39 skipping to change at page 7, line 39
| | | |
| | | |
+---eoPowerStateTable(2) +---eoPowerStateTable(2)
| +--eoPowerStateEntry(1) | +--eoPowerStateEntry(1)
| | [entPhysicalIndex, | | [entPhysicalIndex,
| | eoPowerStateIndex] | | eoPowerStateIndex]
| | | |
| +-- --n IANAPowerStateSet eoPowerStateIndex(1) | +-- --n IANAPowerStateSet eoPowerStateIndex(1)
| +-- r-n Interger32 eoPowerStateMaxPower (2) | +-- r-n Interger32 eoPowerStateMaxPower (2)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoPowerStatePowerUnitMultiplier (3) | eoPowerStatePowerUnitMultiplier (3)
| +-- r-n TimeTicks eoPowerStateTotalTime(4) | +-- r-n TimeTicks eoPowerStateTotalTime(4)
| +-- r-n Counter32 eoPowerStateEnterCount(5) | +-- r-n Counter32 eoPowerStateEnterCount(5)
| |
+eoEnergyParametersTable(1) +eoEnergyParametersTable(1)
+---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
| |
| +-- --n PhysicalIndex eoEnergyObjectIndex (1) | +-- --n PhysicalIndex eoEnergyObjectIndex (1)
| + r-n Integer32 eoEnergyParametersIndex (2) | + r-n Integer32 eoEnergyParametersIndex (2)
| +-- r-n TimeInterval | +-- r-n TimeInterval
| eoEnergyParametersIntervalLength (3) | eoEnergyParametersIntervalLength (3)
skipping to change at page 8, line 33 skipping to change at page 8, line 33
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoEnergyUnitMultiplier (5) | eoEnergyUnitMultiplier (5)
| +-- r-n Integer32 eoEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyMaxConsumed (7) | +-- r-n Integer32 eoEnergyMaxConsumed (7)
| +-- r-n Integer32 eoEnergyMaxProduced (8) | +-- r-n Integer32 eoEnergyMaxProduced (8)
| +-- r-n TimeTicks | +-- r-n TimeTicks
| eoEnergyDiscontinuityTime(9) | eoEnergyDiscontinuityTime(9)
| +-- r-n RowStatus eoEnergyParametersStatus (10) | +-- r-n RowStatus eoEnergyParametersStatus (10)
The powerCharacteristicsMIB consists of four tables. The powerCharacteristicsMIB consists of four tables.
eoACPwrCharTable is indexed by entPhysicalIndex. eoACPwrCharacteristicsTable is indexed by entPhysicalIndex.
eoACPwrCharPhaseTable is indexed by entPhysicalIndex and eoACPwrCharacteristicsPhaseTable is indexed by entPhysicalIndex
eoPhaseIndex. eoACPwrCharWyePhaseTable and and eoPhaseIndex. eoACPwrCharacteristicsWyePhaseTable and
eoACPwrCharDelPhaseTable are indexed by entPhysicalIndex and eoACPwrCharacteristicsDelPhaseTable are indexed by
eoPhaseIndex. entPhysicalIndex and eoPhaseIndex.
eoACPwrCharTable(1) eoACPwrCharacteristicsTable (1)
| |
+---eoACPwrCharEntry (1) [ entPhysicalIndex] +---eoACPwrCharacteristicsEntry (1) [ entPhysicalIndex]
| | | |
| | | |
| +---r-n INTEGER eoACPwrCharConfiguration (1) | +---r-n INTEGER eoACPwrCharacteristicsConfiguration
| +-- r-n Interger32 eoACPwrCharAvgVoltage (2) (1)
| +-- r-n Integer32 eoACPwrCharAvgCurrent (3) | +-- r-n Interger32 eoACPwrCharacteristicsAvgVoltage (2)
| +-- r-n Integer32 eoACPwrCharFrequency (4) | +-- r-n Integer32 eoACPwrCharacteristicsAvgCurrent (3)
| +-- r-n Integer32 eoACPwrCharacteristicsFrequency (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoACPwrCharPowerUnitMultiplier (5) | eoACPwrCharacteristicsPowerUnitMultiplier (5)
| +-- r-n Integer32 eoACPwrCharPowerAccuracy (6) | +-- r-n Integer32 eoACPwrCharacteristicsPowerAccuracy
| +-- r-n Interger32 eoACPwrCharTotalActivePower (7) (6)
| +-- r-n Interger32
eoACPwrCharacteristicsTotalActivePower (7)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrCharTotalReactivePower (8) | eoACPwrCharacteristicsTotalReactivePower (8)
| +-- r-n Integer32 eoACPwrCharTotalApparentPower (9) | +-- r-n Integer32
| +-- r-n Integer32 eoACPwrCharTotalPowerFactor(10) eoACPwrCharacteristicsTotalApparentPower (9)
| +-- r-n Integer32 eoACPwrCharThdAmpheres (11) | +-- r-n Integer32
eoACPwrCharacteristicsTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrCharacteristicsThdAmpheres
(11)
| |
+eoACPwrCharPhaseTable (1) +eoACPwrCharacteristicsPhaseTable (1)
+---EoACPwrCharPhaseEntry(1)[ entPhysicalIndex, +---EoACPwrCharacteristicsPhaseEntry(1)[ entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| | | |
| +-- r-n Integer32 eoPhaseIndex (1) | +-- r-n Integer32 eoPhaseIndex (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhaseAvgCurrent (2) | | eoACPwrCharacteristicsPhaseAvgCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhaseActivePower (3) | | eoACPwrCharacteristicsPhaseActivePower (3)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhaseReactivePower (4) | | eoACPwrCharacteristicsPhaseReactivePower (4)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhaseApparentPower (5) | | eoACPwrCharacteristicsPhaseApparentPower (5)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhasePowerFactor (6) | | eoACPwrCharacteristicsPhasePowerFactor (6)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharPhaseImpedance (7) | | eoACPwrCharacteristicsPhaseImpedance (7)
| | | |
+eoACPwrCharDelPhaseTable (1) +eoACPwrCharacteristicsDelPhaseTable (1)
+-- eoACPwrCharDelPhaseEntry(1) +-- eoACPwrCharacteristicsDelPhaseEntry(1)
| | [entPhysicalIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharDelPhaseToNextPhaseVoltage (1) | | eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage
(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharDelThdPhaseToNextPhaseVoltage (2) | | eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage
| +-- r-n Integer32 eoACPwrCharDelThdCurrent (3) (2)
| +-- r-n Integer32 eoACPwrCharacteristicsDelThdCurrent
(3)
| | | |
+eoACPwrCharWyePhaseTable (1) +eoACPwrCharacteristicsWyePhaseTable (1)
+-- eoACPwrCharWyePhaseEntry (1) +-- eoACPwrCharacteristicsWyePhaseEntry (1)
| | [entPhysicalIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharWyePhaseToNeutralVoltage (1) | | eoACPwrCharacteristicsWyePhaseToNeutralVoltage
(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharWyePhaseCurrent (2) | | eoACPwrCharacteristicsWyePhaseCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrCharWyeThdPhaseToNeutralVoltage (3) | | eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage
(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 energyObjectMib and powerCharacteristicsMIB are presented. are energyObjectMib and powerCharacteristicsMIB are presented.
+--------------------------+ +--------------------------+
| Energy Object ID | | Energy Object ID |
| ----------------------- | | ----------------------- |
| | | |
| entPhysIndex (*) | | entPhysIndex (*) |
| entPhysicalName (*) | | entPhysicalName (*) |
| entPhysicalUris (*) | +---------------------------+ | entPhysicalUUID (*) | +---------------------------+
| (EO UUID) | | | | | | |
| | | Energy Object Attributes | | | | Energy Object Attributes |
| | | ------------------------- | | | | ------------------------- |
| | | | | | | |
+--------------------------+ | eoPowerNamePlate | +--------------------------+ | eoPowerNamePlate |
| | | eoPowerMeasurementCaliber | | | | eoPowerMeasurementCaliber |
| | | eoPowerOrigin | | | | eoPowerOrigin |
| | | eoPowerCurrentType | | | | eoPowerCurrentType |
| | +---------------------------+ | | +---------------------------+
| | | | | |
| | | | | |
skipping to change at page 11, line 5 skipping to change at page 11, line 15
| eoPowerOperState | | |----------------------- | | eoPowerOperState | | |----------------------- |
| eoPowerStateEnterReason | | | eoPowerStateMaxPower | | eoPowerStateEnterReason | | | eoPowerStateMaxPower |
+-------------------------+ | | eoPowerStateTotalTime | +-------------------------+ | | eoPowerStateTotalTime |
| | eoPowerStateEnterCount | | | eoPowerStateEnterCount |
| +------------------------+ | +------------------------+
| |
| |
| |
| |
Figure 1:UML diagram for powerMonitor MIB Figure 1:UML diagram for energyObjectMib
(*) Link with the ENTITY-MIB (*) Link with the ENTITY-MIB
| |
| |
V V
+----------------------------------------+ +----------------------------------------+
| Energy ParametersTable | | Energy ParametersTable |
| -------------------------------------- | | -------------------------------------- |
| | | |
| eoEnergyObjectIndex | | eoEnergyObjectIndex |
skipping to change at page 11, line 33 skipping to change at page 11, line 43
| eoEnergyParametersSampleRate | | eoEnergyParametersSampleRate |
| eoEnergyParametersStatus | | eoEnergyParametersStatus |
+----------------------------------------+ +----------------------------------------+
| |
| |
| |
V V
+----------------------------------------+ +----------------------------------------+
| Energy Table | | Energy Table |
| ---------------------------------- | | -------------------------------------- |
| eoEnergyCollectionStartTime | | eoEnergyCollectionStartTime |
| eoEnergyConsumed | | eoEnergyConsumed |
| eoEnergyProduced | | eoEnergyProduced |
| eoEnergyNet | | eoEnergyNet |
| eoEnergyUnitMultiplier | | eoEnergyUnitMultiplier |
| eoEnergyAccuracy | | eoEnergyAccuracy |
| eoMaxConsumed | | eoMaxConsumed |
| eoMaxProduced | | eoMaxProduced |
| eoDiscontinuityTime | | eoDiscontinuityTime |
+----------------------------------------+ +----------------------------------------+
+--------------------------+ +--------------------------+
| EnergyObject ID | | EnergyObject ID |
| ----------------------- | | ----------------------- |
| | | |
| |
| entPhysicalIndex (*) | | entPhysicalIndex (*) |
| | | |
+--------------------------+ +--------------------------+
| |
v v
+-------------------------------------+ +--------------------------------------------+
| Power Characteristics | | Power Characteristics |
| ----------------------------------- | | ----------------------------------- |
| eoACPwrCharConfiguration | | eoACPwrCharacteristicsConfiguration |
| eoACPwrCharAvgVoltage | | eoACPwrCharacteristicsAvgVoltage |
| eoACPwrCharAvgCurrent | | eoACPwrCharacteristicsAvgCurrent |
| eoACPwrCharFrequency | | eoACPwrCharacteristicsFrequency |
| eoACPwrCharPowerUnitMultiplier | | eoACPwrCharacteristicsPowerUnitMultiplier |
| eoACPwrCharPowerAccuracy | | eoACPwrCharacteristicsPowerAccuracy |
| eoACPwrCharTotalActivePower | | eoACPwrCharacteristicsTotalActivePower |
| eoACPwrCharTotalReactivePower | | eoACPwrCharacteristicsTotalReactivePower |
| eoACPwrCharTotalApparentPower | | eoACPwrCharacteristicsTotalApparentPower |
| eoACPwrCharTotalPowerFactor | | eoACPwrCharacteristicsTotalPowerFactor |
| eoACPwrCharThdAmpheres | | eoACPwrCharacteristicsThdAmpheres |
+-------------------------------------+ ^ +--------------------------------------------+
^ ^ | ^ ^
| | ------- | |
| ---- | | -----------
| | | | |
| | | | |
+-------------------------------------+ | | +--------------------------------------------+ |
| Power Phase Characteristics | | | | Power Phase Characteristics | |
| ---------------------------------- | | | | ---------------------------------- | |
| eoPhaseIndex | | | | eoPhaseIndex | |
| eoACPwrCharPhaseAvgCurrent | | | | eoACPwrCharacteristicsPhaseAvgCurrent | |
| eoACPwrCharAvgCurrent | | | | eoACPwrCharacteristicsAvgCurrent | |
| eoACPwrCharFrequency | | | | eoACPwrCharacteristicsFrequency | |
| eoACPwrCharPowerUnitMultiplier | | | | eoACPwrCharacteristicsPowerUnitMultiplier | |
| eoACPwrCharPowerAccuracy | | | | eoACPwrCharacteristicsPowerAccuracy | |
| eoACPwrCharPhaseActivePower | | | | eoACPwrCharacteristicsPhaseActivePower | |
| eoACPwrCharPhaseReactivePower | | | | eoACPwrCharacteristicsPhaseReactivePower | |
| eoACPwrCharPhaselApparentPower | | | | eoACPwrCharacteristicsPhaselApparentPower | |
| eoACPwrCharPhaseImpedance | | | | eoACPwrCharacteristicsPhaseImpedance | |
+-------------------------------------+ | | +--------------------------------------------+ |
| | |
| | |
+---------------------------------------------+ | |
| AC Input DEL Configuration | | |
| | | |
| eoACPwrCharDelPhaseToNextPhaseVoltage | | |
| eoACPwrCharDelThdPhaseToNextPhaseVoltage | | +------------------------------------------------------+
| eoACPwrCharDelThdCurrent | | | AC Input DEL Configuration |
+---------------------------------------------+ | | |
| eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage |
| eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage |
| eoACPwrCharacteristicsDelThdCurrent |
+------------------------------------------------------+
| |
| |
+---------------------------------------------+ +---------------------------------------------------+
| AC Input WYE Configuration | | AC Input WYE Configuration |
| | | |
| eoACPwrCharWyePhaseToNeutralVoltage | | eoACPwrCharacteristicsWyePhaseToNeutralVoltage |
| eoACPwrCharWyePhaseCurrent | | eoACPwrCharacteristicsWyePhaseCurrent |
| eoACPwrCharWyeThdPhaseToNeutralVoltage | | eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage |
+---------------------------------------------+ +---------------------------------------------------+
Figure 2: UML diagram for the powerCharacteristicsMIB Figure 2: UML diagram for the powerCharacteristicsMIB
(*) Link with the ENTITY-MIB (*) Link with the ENTITY-MIB
5.1. Energy Object Information 5.1. Energy Object Information
Refer to the "Energy Object Information" section in [EMAN- Refer to the "Energy Object Information" section in [EMAN-FMWK]
FRAMEWORK] for background information. An energy aware device for background information. An energy aware device is
is considered as an instance of a Energy Object as defined in considered as an instance of a Energy Object as defined in the
the [EMAN-FRAMEWORK]. [EMAN-FMWK].
The Energy Object 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
eoTable. In this table, every Energy Object SHOULD have a eoTable. In this table, every Energy Object SHOULD have a
printable name eoName, and MUST HAVE a unique Energy Object printable name eoName, and MUST HAVE a unique Energy Object
index entPhysicalUris and entPhysicalIndex. The ENERGY-AWARE-MIB index entPhysicalUUID and entPhysicalIndex. The ENERGY-AWARE-MIB
module returns the relationship (parent/child) between Energy module returns the relationship (parent/child) between Energy
Objects. There are several possible relationships between Parent Objects. There are several possible relationships between Parent
and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy, and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy,
PoweredBy, AggregatedBy and ProxyedBy. PoweredBy, AggregatedBy and ProxyedBy.
5.2. Power State 5.2. Power State
Refer to the "Power States" section in [EMAN-FRAMEWORK] for Refer to the "Power States" section in [EMAN-FMWK] for
background information. background information.
An Energy Object 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 an Energy Object, are specified by the management of an Energy Object, are specified by the
eoPowerState MIB object. The actual Power State is specified by eoPowerState MIB object. The actual Power State is specified by
the eoPowerOperState MIB object, while the eoPowerAdminState MIB the eoPowerOperState MIB object, while the eoPowerAdminState MIB
object specifies the Power State requested for the Energy object specifies the Power State requested for the Energy
Object. The difference between the values of eoPowerOperState Object. The difference between the values of eoPowerOperState
and eoPowerAdminState can be attributed that the Energy Object and eoPowerAdminState can be attributed that the Energy Object
is busy transitioning from eoPowerAdminState into the is busy transitioning from eoPowerAdminState into the
eoPowerOperState, at which point it will update the content of eoPowerOperState, at which point it will update the content of
eoPowerOperState. In addition, the possible reason for change eoPowerOperState. In addition, the possible reason for change
in Power State is reported in eoPowerStateEnterReason. in Power State is reported in eoPowerStateEnterReason.
Regarding eoPowerStateEnterReason, management stations and Regarding eoPowerStateEnterReason, management stations and
Energy Objects should support any format of the owner string Energy Objects should support any format of the owner string
dictated by the local policy of the organization. It is dictated by the local policy of the organization. It is
suggested that this name contain at least the reason for the suggested that this name contain at least the reason for the
transition change, and one or more of the following: IP address, transition change, and one or more of the following: IP address,
skipping to change at page 15, line 38 skipping to change at page 16, line 14
(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
standard is targeted for hosts and computers. Details of the standard is targeted for hosts and computers. Details of the
semantics of each Power State within the DMTF Power State Set semantics of each Power State within the DMTF Power State Set
can be obtained from the DMTF Power State Management Profile can be obtained from the DMTF Power State Management Profile
specification [DMTF]. specification [DMTF].
DMTF power profile extends ACPI power states. The following DMTF power profile extends ACPI power states. The following
table provides a mapping between DMTF and ACPI Power State Set: table provides a mapping between DMTF and ACPI Power State Set:
--------------------------------------------------- ---------------------------------------------------
| DMTF | ACPI | | DMTF | ACPI |
| Power State | Power State | | Power State | Power State |
--------------------------------------------------- ---------------------------------------------------
| Reserved(0) | | | Reserved(0) | |
--------------------------------------------------- ---------------------------------------------------
| Reserved(1) | | | Reserved(1) | |
--------------------------------------------------- ---------------------------------------------------
skipping to change at page 16, line 42 skipping to change at page 17, line 16
--------------------------------------------------- ---------------------------------------------------
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 The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the DMTF Power State Set. 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 consumption of a device. The EMAN Power States are an expansion
expansion of the basic Power States as defined in IEEE1621 that of the basic Power States as defined in IEEE1621 that also
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.
There are twelve Power States, that expand on IEEE1621 on, sleep There are twelve Power States, that expand on IEEE1621 on, sleep
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 Energy Object 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.
skipping to change at page 19, line 27 skipping to change at page 19, line 48
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.
The Textual Convention IANAPowerStateSet contains the proposed The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the EMAN Power State Set. numbering of the Power States within the EMAN Power State Set.
5.3. Energy Object Usage Information 5.3. Energy Object Usage Information
Refer to the "Energy Object Usage Measurement" section in [EMAN- Refer to the "Energy Object Usage Measurement" section in [EMAN-
FRAMEWORK] for background information. FMWK] for background information.
For an Energy Object, power usage is reported using eoPower. For an Energy Object, power usage is reported using eoPower.
The magnitude of measurement is based on the The magnitude of measurement is based on the
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
Textual Convention (TC). Power measurement magnitude should Textual Convention (TC). Power measurement magnitude should
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
[IEC.62053-22] definition of unit multiplier for the SI (System [IEC.62053-22] definition of unit multiplier for the SI (System
International) units of measure. Measured values are International) units of measure. Measured values are
represented in SI units obtained by BaseValue * 10 raised to the represented in SI units obtained by BaseValue * 10 raised to the
power of the scale. power of the scale.
For example, if current power usage of an Energy Object 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
eoPowerUnitMultiplier. 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 eoPowerStatePowerUnitMultiplier, including eoPowerStatePowerUnitMultiplier,
eoEnergyUnitMultiplier, and eoACPwrCharPowerUnitMultiplier. eoEnergyUnitMultiplier, and
eoACPwrCharacteristicsPowerUnitMultiplier.
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 eoPower 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 eoPowerOrigin 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 eoPowerMeasurementCaliber 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
eoPowerMeasurementCaliber shall report that measurement eoPowerMeasurementCaliber shall report that measurement
mechanism is "unavailable" and the eoPower measurement shall be mechanism is "unavailable" and the eoPower measurement shall be
"0". "0".
The nameplate power rating of an Energy Object is specified in The nameplate power rating of an Energy Object is specified in
eoPowerNameplate MIB object. eoPowerNameplate MIB object.
5.4. Optional Power Usage Characteristics 5.4. Optional Power Usage Characteristics
Refer to the "Optional Power Usage Characteristics" section in Refer to the "Optional Power Usage Characteristics" section in
[EMAN-FRAMEWORK] for background information. [EMAN-FMWK] for background information.
The optional powerCharacteristicsMIB MIB module can be The optional powerCharacteristicsMIB MIB module can be
implemented to further describe power usage characteristics implemented to further describe power usage characteristics
measurement. The powerCharacteristicsMIB MIB module adheres measurement. The powerCharacteristicsMIB MIB module adheres
closely to the IEC 61850 7-2 standard to describe AC closely to the IEC 61850 7-2 standard to describe AC
measurements. measurements.
The powerCharacteristicsMIB MIB module contains a primary table, The powerCharacteristicsMIB MIB module contains a primary table,
the eoACPwrCharTable table, that defines Power Characteristics the eoACPwrCharacteristicsTable table, that defines power
measurements for supported entPhysicalIndex entities, as a characteristics measurements for supported entPhysicalIndex
sparse extension of the eoPowerTable (with entPhysicalIndex as entities, as a sparse extension of the eoPowerTable (with
primary index). This eoACPwrCharTable table contains such entPhysicalIndex as primary index). This
information as the configuration (single phase, DEL 3 phases, eoACPwrCharacteristicsTable table contains such information as
WYE 3 phases), voltage, frequency, power accuracy, total the configuration (single phase, DEL 3 phases, WYE 3 phases),
active/reactive power/apparent power, amperage, and voltage. voltage, frequency, power accuracy, total active/reactive
power/apparent power, amperage, and voltage.
In case of 3-phase power, the eoACPwrCharPhaseTable additional In case of 3-phase power, the eoACPwrCharacteristicsPhaseTable
table is populated with Power Characteristics measurements per additional table is populated with Power Characteristics
phase (so double indexed by the entPhysicalIndex and measurements per phase (so double indexed by the
eoPhaseIndex). This table, which describes attributes common to entPhysicalIndex and eoPhaseIndex). This table, which describes
both WYE and DEL configurations, contains the average current, attributes common to both WYE and DEL configurations, contains
active/reactive/apparent power, power factor, and impedance. the average current, 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
eoACPwrCharDelPhaseTable table describes the phase-to-phase eoACPwrCharacteristicsDelPhaseTable table describes the phase-
Power Characteristics measurements, i.e., voltage and current. to-phase power characteristics 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
eoACPwrCharWyePhaseTable table describes the phase-to-neutral eoACPwrCharacteristicsWyePhaseTable table describes the phase-
Power Characteristics measurements, i.e., voltage and current. to-neutral power characteristics 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-FMWK] 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 an Energy Object, 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 eoPowerMeasurementCaliber. description clause of the object eoPowerMeasurementCaliber.
Two tables are introduced to characterize energy measurement of Two tables are introduced to characterize energy measurement of
an Energy Object: eoEnergyTable and eoEnergyParametersTable. 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
eoEnergyTable. Energy information will be an accumulation with eoEnergyTable. Energy information will be an accumulation with
skipping to change at page 25, line 34 skipping to change at page 26, line 12
value(s) of ,eoPowerStateIndex, eoPowerOperState, value(s) of ,eoPowerStateIndex, eoPowerOperState,
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
It is foreseen that most Energy Objects will require the It is foreseen that most Energy Objects will require the
implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a
prerequisite for this MIB module. In such a case, eoPowerTable prerequisite for this MIB module. In such a case, eoPowerTable
of the EMAN-MON-MIB is a sparse extension of the eoTable of of the EMAN-MON-MIB is a sparse extension of the eoTable of
ENERGY-AWARE-MIB. Every Energy Object MUST implement ENERGY-AWARE-MIB. Every Energy Object MUST implement
entPhysicalIndex, entPhysicalUris and entPhysicalName from the entPhysicalIndex, entPhysicalUUID and entPhysicalName from the
ENTITY-MIB [RFC4133]. As the index for the primary Energy ENTITY-MIB [EMAN-ENTITY]. As the primary index for the Energy
Object, entPhysicalIndex is used. Object, entPhysicalIndex is used.
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 Energy Objects 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 Energy Objects are In the ENERGY-AWARE-MIB module tables, the Energy Objects are
indexed by the entPhysicalIndex. indexed by the entPhysicalIndex.
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 Energy Object, the in the local SNMP context, for the same Energy Object, the
skipping to change at page 26, line 22 skipping to change at page 26, line 46
State Set. In other words, polling the eoPowerStateTable allows State Set. In other words, polling the eoPowerStateTable allows
the discovery of each Power State within every Power State Set the discovery of each Power State within every Power State Set
supported by the Energy Object. supported by the Energy Object.
If the Energy Object is an Aggregator or a Proxy, the MIB module If the Energy Object is an Aggregator or a Proxy, the MIB module
would be populated with the Energy Object Parent and Children would be populated with the Energy Object Parent and Children
information, which have their own Energy Object index value information, which have their own Energy Object index value
(entPhysicalIndex). However, the parent/child relationship must (entPhysicalIndex). However, the parent/child relationship must
be discovered thanks to the ENERGY-AWARE-MIB module. be discovered thanks to the ENERGY-AWARE-MIB module.
Finally, the NMS can monitor the Power Characteristics thanks to Finally, the NMS can monitor the power characteristics thanks to
the powerCharacteristicsMIB MIB module, which reuses the the powerCharacteristicsMIB MIB module, which reuses the
entPhysicalIndex to index the Energy Object. entPhysicalIndex to index the Energy Object.
7. Link with the other IETF MIBs 7. Link with the other IETF MIBs
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
RFC 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
skipping to change at page 31, line 4 skipping to change at page 31, line 19
eoethPortIndex and eoethPortGrpIndex. eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
eoPowerOrigin 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
eoPowerOrigin: 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 Energy Object, including Energy Object implementation of the Energy Object, including Energy Object
Parent and Energy Object 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 [EMAN-ENTITY ] 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 [EMAN-AWARE-MIB]. The switch has the following ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following
attributes, entPhysicalIndex "1", and eoUUID "UUID 1000". The attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID
power usage of the switch is "440 Watts". The switch does not 1000". The power usage of the switch is "440 Watts". The
have an Energy Object Parent. switch does 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 entPhysicalIndex "3", and eoUUID is "UUID 1000:3". The port has entPhysicalIndex "3", and entPhysicalUUID is "UUID
power metered at the POE switch port is "12 watts". In this 1000:3". The power metered at the POE switch port is "12
example, the POE switch port has the switch as the Energy Object watts". In this example, the POE switch port has the switch as
Parent, with its eoParentID of "1000". the Energy Object Parent, with its eoParentID of "1000".
The attributes of the PC are given below. The PC does not have The attributes of the PC are given below. The PC does not have
an entPhysicalIndex, andthe eoUUID is "UUID 1000:57 ". The PC an entPhysicalIndex, and the entPhysicalUUID is "UUID 1000:57 ".
has an Energy Object Parent, i.e. the switch port whose eoUUID The PC has an Energy Object Parent, i.e. the switch port whose
is "UUID 1000:3". The power usage of the PC is "120 Watts" and entPhysicalUUID is "UUID 1000:3". The power usage of the PC is
is communicated to the switch port. "120 Watts" and is communicated to the switch port.
This example illustrates the important distinction between the This example illustrates the important distinction between the
Energy Object 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 Energy Object Parent powered from the wall outlet. However, the Energy Object Parent
sends power control messages to both the Energy Object 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 |
skipping to change at page 33, line 19 skipping to change at page 33, line 31
energyObjectMibObject describes the power measurement attributes energyObjectMibObject describes the power measurement attributes
of an Energy Object 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 Energy Object and its in terms of uniquely identification of the Energy Object and its
relationship to other entities in the network are addressed in relationship to other entities in the network are addressed in
[EMAN-AWARE-MIB]. [EMAN-AWARE-MIB].
Logically, this MIB module is a sparse extension of the Logically, this MIB module is a sparse extension of the
[EMAN-AWARE-MIB] module. Thus the following requirements which [EMAN-AWARE-MIB] module. Thus the following requirements which
are applied to [EMAN-AWARE-MIB] are also applicable. As a are applied to [EMAN-AWARE-MIB] are also applicable. As a
requirement for this MIB module, [EMAN-AWARE-MIB] should be requirement for this MIB module, [EMAN-AWARE-MIB] should be
implemented and the three MIB objects from ENTITY-MIB implemented and as Module Compliance of ENTITY-MIB V4 [EMAN-
(entPhysicalIndex, entPhysicalName and entPhysicalUris) MUST be ENTITY] with respect to entity4CRCompliance should be supported
implemented. which requires 3 MIB objects (entPhysicalIndex, entPhysicalName
and entPhysicalUUID ) MUST be implemented.
eoMeterCapabilitiesTable is useful to enable applications to eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading that are supported by the local management system. By reading
the value of this object, it is possible for applications to the value of this object, it is possible for applications to
know which tables contain the information and are usable without know which tables contain the information and are usable without
walking through the table and querying every element which walking through the table and querying every element which
involves a trial-and-error process. involves a trial-and-error process.
skipping to change at page 34, line 35 skipping to change at page 35, line 6
TimeStamp TimeStamp
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
entPhysicalIndex, PhysicalIndex entPhysicalIndex, PhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
energyObjectMib MODULE-IDENTITY energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201207110000Z" -- 11 July 2012 LAST-UPDATED "201210220000Z" -- 22 October 2012
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:
skipping to change at page 35, line 4 skipping to change at page 35, line 18
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 560103
IN IN
Phone: +91 80 4426 3947 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad@bradschoening.com Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-115 Phone: +49 6221 4342-115
Email: quittek@neclab.eu Email: quittek@neclab.eu
skipping to change at page 36, line 9 skipping to change at page 36, line 24
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.
This table sparse extension of the eoTable This table sparse extension of the eoTable
from the ENERGY-AWARE-MIB. As a requirement from the ENERGY-AWARE-MIB. As a requirement
[EMAN-AWARE-MIB] should be implemented and [EMAN-AWARE-MIB] should be implemented.
three MIB objects from ENTITY-MIB
(entPhysicalIndex, entPhysicalName and Module Compliance of ENTITY-MIB v4
entPhysicalUris)MUST be implemented. " with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"201207110000Z" -- 11 July 2012 "201210220000Z" -- 22 October 2012
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
::= { mib-2 xxx } ::= { mib-2 xxx }
energyObjectMibNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { energyObjectMib 0 } ::= { energyObjectMib 0 }
energyObjectMibObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
skipping to change at page 39, line 24 skipping to change at page 39, line 41
EoMeterCapabilitiesEntry ::= SEQUENCE { EoMeterCapabilitiesEntry ::= SEQUENCE {
eoMeterCapability BITS eoMeterCapability BITS
} }
eoMeterCapability OBJECT-TYPE eoMeterCapability OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
powermetering(1), -- power measurement powermetering(1), -- power measurement
energymetering(2), -- energy measurement energymetering(2), -- energy measurement
powercharacteristics(3) -- Power Characteristics powercharacteristics(3) -- power characteristics
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the Energy monitoring capabilities supported "An indication of the Energy monitoring capabilities supported
by this agent. This object use a BITS syntax and indicate the by this agent. This object use a BITS syntax and indicate the
MIB groups supported by the probe. By reading the value of this MIB groups supported by the probe. By reading the value of this
object, it is possible to determine the MIB tables supported. " object, it is possible to determine the MIB tables supported. "
::= { eoMeterCapabilitiesEntry 1 } ::= { eoMeterCapabilitiesEntry 1 }
skipping to change at page 54, line 50 skipping to change at page 55, line 22
energyObjectMibGroups OBJECT IDENTIFIER energyObjectMibGroups OBJECT IDENTIFIER
::= { energyObjectMib 4 } ::= { energyObjectMib 4 }
energyObjectMibFullCompliance 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.
The entPhysicalIndex, entPhysicalName, and
entPhysicalUris [RFC4133] MUST be implemented." Module Compliance of [EMAN-ENTITY]
with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMibTableGroup,
energyObjectMibStateTableGroup, energyObjectMibStateTableGroup,
energyObjectMibNotifGroup energyObjectMibNotifGroup
} }
GROUP energyObjectMibEnergyTableGroup GROUP energyObjectMibEnergyTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex, have to implement.
entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." Module Compliance of [EMAN-ENTITY]
with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
GROUP energyObjectMibEnergyParametersTableGroup GROUP energyObjectMibEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex, have to implement.
entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." Module Compliance of {EMAN-ENTITY]
with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
GROUP energyObjectMibMeterCapabilitiesTableGroup GROUP energyObjectMibMeterCapabilitiesTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex, have to implement.
entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." Module Compliance of [EMAN-ENTITY]
with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
::= { energyObjectMibCompliances 1 } ::= { energyObjectMibCompliances 1 }
energyObjectMibReadOnlyCompliance 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 cannot be device can then be monitored but cannot be
configured with this MIB. The entPhysicalIndex, configured with this MIB.
entPhysicalName, and entPhysicalUris from [RFC4133]
MUST be implemented. " Module Compliance of [EMAN-ENTITY]
with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMibTableGroup,
energyObjectMibStateTableGroup, energyObjectMibStateTableGroup,
energyObjectMibNotifGroup energyObjectMibNotifGroup
} }
OBJECT eoPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 56, line 29 skipping to change at page 57, line 25
eoPowerMeasurementCaliber, eoPowerMeasurementCaliber,
eoPowerCurrentType, eoPowerCurrentType,
eoPowerOrigin, eoPowerOrigin,
eoPowerAdminState, eoPowerAdminState,
eoPowerOperState, eoPowerOperState,
eoPowerStateEnterReason 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 Energy Object."
::= { energyObjectMibGroups 1 } ::= { energyObjectMibGroups 1 }
energyObjectMibStateTableGroup OBJECT-GROUP energyObjectMibStateTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPowerStateMaxPower, eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier, eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime, eoPowerStateTotalTime,
eoPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
skipping to change at page 58, line 11 skipping to change at page 59, line 4
::= { energyObjectMibGroups 5 } ::= { energyObjectMibGroups 5 }
energyObjectMibNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange 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."
::= { energyObjectMibGroups 6 } ::= { energyObjectMibGroups 6 }
END END
-- ************************************************************ -- ************************************************************
-- --
-- This MIB module is used to monitor Power Characteristics of -- This MIB module is used to monitor power characteristics of
-- networked devices with measurements. -- networked devices with measurements.
-- --
-- This MIB module is an extension of energyObjectMib module. -- This MIB module is an extension of energyObjectMib module.
-- --
-- ************************************************************* -- *************************************************************
POWER-CHARACTERISTICS-MIB DEFINITIONS ::= BEGIN POWER-CHARACTERISTICS-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
skipping to change at page 58, line 44 skipping to change at page 59, line 38
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier UnitMultiplier
FROM ENERGY-OBJECT-MIB FROM ENERGY-OBJECT-MIB
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
powerCharacteristicsMIB MODULE-IDENTITY powerCharacteristicsMIB MODULE-IDENTITY
LAST-UPDATED "201207110000Z" -- 11 July 2012 LAST-UPDATED "201210220000Z" -- 22 October 2012
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:
skipping to change at page 59, line 12 skipping to change at page 60, line 4
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 560103
IN IN
Phone: +91 80 4426 3947 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad@bradschoening.com Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-115 Phone: +49 6221 4342-115
Email: quittek@neclab.eu Email: quittek@neclab.eu
skipping to change at page 60, line 4 skipping to change at page 60, line 42
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise Benoit Claise
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 Characteristics "This MIB is used to report AC power characteristics
in devices. The table is a sparse augmentation of in devices. The table is a sparse augmentation of
the eoPowerTable table from the energyObjectMib the eoPowerTable table from the energyObjectMib
module. Both three-phase and single-phase power module. Both three-phase and single-phase power
configurations are supported. configurations are supported.
As a requirement for this MIB module, As a requirement for this MIB module,
[EMAN-AWARE-MIB] should be implemented and [EMAN-AWARE-MIB] should be implemented.
three MIB objects from ENTITY-MIB (entPhysicalIndex,
entPhysicalName and entPhysicalUris) MUST be Module Compliance of ENTITY-MIB v4
implemented. " with respect to entity4CRCompliance should
be supported which requires implementation
of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"201207110000Z" -- 11 July 2012 "201210220000Z" -- 22 October 2012
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerCharacteristicsMIBConform OBJECT IDENTIFIER powerCharacteristicsMIBConform OBJECT IDENTIFIER
::= { powerCharacteristicsMIB 0 } ::= { powerCharacteristicsMIB 0 }
powerCharacteristicsMIBObjects OBJECT IDENTIFIER powerCharacteristicsMIBObjects OBJECT IDENTIFIER
::= { powerCharacteristicsMIB 1 } ::= { powerCharacteristicsMIB 1 }
-- Objects -- Objects
eoACPwrCharTable OBJECT-TYPE eoACPwrCharacteristicsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrCharEntry SYNTAX SEQUENCE OF EoACPwrCharacteristicsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines Power Characteristics measurements "This table defines power characteristics measurements
for supported entPhysicalIndex entities. It is a sparse for supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable." extension of the eoPowerTable."
::= { powerCharacteristicsMIBObjects 1 } ::= { powerCharacteristicsMIBObjects 1 }
eoACPwrCharEntry OBJECT-TYPE eoACPwrCharacteristicsEntry OBJECT-TYPE
SYNTAX EoACPwrCharEntry SYNTAX EoACPwrCharacteristicsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a sparse extension of the eoPowerTable with "This is a sparse extension of the eoPowerTable with
entries for Power Characteristics measurements or entries for power characteristics 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 {entPhysicalIndex } INDEX {entPhysicalIndex }
::= { eoACPwrCharTable 1 } ::= { eoACPwrCharacteristicsTable 1 }
EoACPwrCharEntry ::= SEQUENCE { EoACPwrCharacteristicsEntry ::= SEQUENCE {
eoACPwrCharConfiguration INTEGER, eoACPwrCharacteristicsConfiguration INTEGER,
eoACPwrCharAvgVoltage Integer32, eoACPwrCharacteristicsAvgVoltage Integer32,
eoACPwrCharAvgCurrent Integer32, eoACPwrCharacteristicsAvgCurrent Integer32,
eoACPwrCharFrequency Integer32, eoACPwrCharacteristicsFrequency Integer32,
eoACPwrCharPowerUnitMultiplier UnitMultiplier, eoACPwrCharacteristicsPowerUnitMultiplier UnitMultiplier,
eoACPwrCharPowerAccuracy Integer32, eoACPwrCharacteristicsPowerAccuracy Integer32,
eoACPwrCharTotalActivePower Integer32, eoACPwrCharacteristicsTotalActivePower Integer32,
eoACPwrCharTotalReactivePower Integer32, eoACPwrCharacteristicsTotalReactivePower Integer32,
eoACPwrCharTotalApparentPower Integer32, eoACPwrCharacteristicsTotalApparentPower Integer32,
eoACPwrCharTotalPowerFactor Integer32, eoACPwrCharacteristicsTotalPowerFactor Integer32,
eoACPwrCharThdAmpheres Integer32, eoACPwrCharacteristicsThdAmpheres Integer32,
eoACPwrCharThdVoltage Integer32 eoACPwrCharacteristicsThdVoltage Integer32
} }
eoACPwrCharConfiguration OBJECT-TYPE eoACPwrCharacteristicsConfiguration 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."
::= { eoACPwrCharEntry 1 }
eoACPwrCharAvgVoltage OBJECT-TYPE ::= { eoACPwrCharacteristicsEntry 1 }
eoACPwrCharacteristicsAvgVoltage 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 of the voltage measured "A measured value for average of the voltage measured
over an integral number of AC cycles For a 3-phase over an integral number of AC cycles For a 3-phase
system, this is the average voltage (V1+V2+V3)/3. IEC system, this is the average voltage (V1+V2+V3)/3. IEC
61850-7-4 measured value attribute 'Vol'" 61850-7-4 measured value attribute 'Vol'"
::= { eoACPwrCharEntry 2 } ::= { eoACPwrCharacteristicsEntry 2 }
eoACPwrCharAvgCurrent OBJECT-TYPE eoACPwrCharacteristicsAvgCurrent 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'"
::= { eoACPwrCharEntry 3 } ::= { eoACPwrCharacteristicsEntry 3 }
eoACPwrCharFrequency OBJECT-TYPE eoACPwrCharacteristicsFrequency 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'."
::= { eoACPwrCharEntry 4 } ::= { eoACPwrCharacteristicsEntry 4 }
eoACPwrCharPowerUnitMultiplier OBJECT-TYPE eoACPwrCharacteristicsPowerUnitMultiplier 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
eoACPwrCharTotalActivePower, eoACPwrCharacteristicsTotalActivePower,
eoACPwrCharTotalReactivePower eoACPwrCharacteristicsTotalReactivePower
and eoACPwrCharTotalApparentPower measurements. and eoACPwrCharacteristicsTotalApparentPower
For 3-phase power systems, this will include measurements.
eoACPwrCharPhaseActivePower, For 3-phase power systems, this will also include
eoACPwrCharPhaseReactivePower and eoACPwrCharacteristicsPhaseActivePower,
eoACPwrCharPhaseApparentPower" eoACPwrCharacteristicsPhaseReactivePower and
::= { eoACPwrCharEntry 5 } eoACPwrCharacteristicsPhaseApparentPower"
eoACPwrCharPowerAccuracy OBJECT-TYPE ::= { eoACPwrCharacteristicsEntry 5 }
eoACPwrCharacteristicsPowerAccuracy 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"
::= { eoACPwrCharEntry 6 } ::= { eoACPwrCharacteristicsEntry 6 }
eoACPwrCharTotalActivePower OBJECT-TYPE eoACPwrCharacteristicsTotalActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS " 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'."
::= { eoACPwrCharEntry 7 } ::= { eoACPwrCharacteristicsEntry 7 }
eoACPwrCharTotalReactivePower OBJECT-TYPE eoACPwrCharacteristicsTotalReactivePower 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'."
::= { eoACPwrCharEntry 8 } ::= { eoACPwrCharacteristicsEntry 8 }
eoACPwrCharTotalApparentPower OBJECT-TYPE eoACPwrCharacteristicsTotalApparentPower 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'."
::= { eoACPwrCharEntry 9 } ::= { eoACPwrCharacteristicsEntry 9 }
eoACPwrCharTotalPowerFactor OBJECT-TYPE eoACPwrCharacteristicsTotalPowerFactor 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'."
::= { eoACPwrCharEntry 10 } ::= { eoACPwrCharacteristicsEntry 10 }
eoACPwrCharThdAmpheres OBJECT-TYPE eoACPwrCharacteristicsThdAmpheres 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'."
::= { eoACPwrCharEntry 11 } ::= { eoACPwrCharacteristicsEntry 11 }
eoACPwrCharThdVoltage OBJECT-TYPE eoACPwrCharacteristicsThdVoltage 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'."
::= { eoACPwrCharEntry 12 } ::= { eoACPwrCharacteristicsEntry 12 }
eoACPwrCharPhaseTable OBJECT-TYPE eoACPwrCharacteristicsPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrCharPhaseEntry SYNTAX SEQUENCE OF EoACPwrCharacteristicsPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes 3-phase Power Characteristics "This table describes 3-phase power characteristics
measurements. It is a sparse extension of the measurements. It is a sparse extension of the
eoACPwrCharTable." eoACPwrCharacteristicsTable."
::= { powerCharacteristicsMIBObjects 2 } ::= { powerCharacteristicsMIBObjects 2 }
eoACPwrCharPhaseEntry OBJECT-TYPE eoACPwrCharacteristicsPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrCharPhaseEntry SYNTAX EoACPwrCharacteristicsPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes common 3-phase Power "An entry describes common 3-phase power
Characteristics measurements. characteristics measurements.
This optional table describes 3-phase Power This optional table describes 3-phase power
Characteristics measurements, with three entries for characteristics measurements, with three entries for
each supported entPhysicalIndex entity. Entities each supported entPhysicalIndex entity. Entities
having single phase power shall not have any entities. having single phase 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
eoACPwrCharTable. eoACPwrCharacteristicsTable.
These attributes correspond to IEC 61850-7.4 MMXU phase These attributes correspond to IEC 61850-7.4 MMXU phase
measurements." measurements."
INDEX { entPhysicalIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrCharPhaseTable 1 } ::= { eoACPwrCharacteristicsPhaseTable 1 }
EoACPwrCharPhaseEntry ::= SEQUENCE { EoACPwrCharacteristicsPhaseEntry ::= SEQUENCE {
eoPhaseIndex Integer32, eoPhaseIndex Integer32,
eoACPwrCharPhaseAvgCurrent Integer32, eoACPwrCharacteristicsPhaseAvgCurrent Integer32,
eoACPwrCharPhaseActivePower Integer32, eoACPwrCharacteristicsPhaseActivePower Integer32,
eoACPwrCharPhaseReactivePower Integer32, eoACPwrCharacteristicsPhaseReactivePower Integer32,
eoACPwrCharPhaseApparentPower Integer32, eoACPwrCharacteristicsPhaseApparentPower Integer32,
eoACPwrCharPhasePowerFactor Integer32, eoACPwrCharacteristicsPhasePowerFactor Integer32,
eoACPwrCharPhaseImpedance Integer32
eoACPwrCharacteristicsPhaseImpedance Integer32
} }
eoPhaseIndex 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."
::= { eoACPwrCharPhaseEntry 1 } ::= { eoACPwrCharacteristicsPhaseEntry 1 }
eoACPwrCharPhaseAvgCurrent OBJECT-TYPE eoACPwrCharacteristicsPhaseAvgCurrent 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'"
::= { eoACPwrCharPhaseEntry 2 } ::= { eoACPwrCharacteristicsPhaseEntry 2 }
eoACPwrCharPhaseActivePower OBJECT-TYPE eoACPwrCharacteristicsPhaseActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS " 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'"
::= { eoACPwrCharPhaseEntry 3 } ::= { eoACPwrCharacteristicsPhaseEntry 3 }
eoACPwrCharPhaseReactivePower OBJECT-TYPE eoACPwrCharacteristicsPhaseReactivePower 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'"
::= { eoACPwrCharPhaseEntry 4 } ::= { eoACPwrCharacteristicsPhaseEntry 4 }
eoACPwrCharPhaseApparentPower OBJECT-TYPE eoACPwrCharacteristicsPhaseApparentPower 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 power. the total apparent 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 'VA'." may be combined. IEC 61850-7-4 attribute 'VA'."
::= { eoACPwrCharPhaseEntry 5 } ::= { eoACPwrCharacteristicsPhaseEntry 5 }
eoACPwrCharPhasePowerFactor OBJECT-TYPE eoACPwrCharacteristicsPhasePowerFactor 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."
::= { eoACPwrCharPhaseEntry 6 } ::= { eoACPwrCharacteristicsPhaseEntry 6 }
eoACPwrCharPhaseImpedance OBJECT-TYPE eoACPwrCharacteristicsPhaseImpedance 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'."
::= { eoACPwrCharPhaseEntry 7 } ::= { eoACPwrCharacteristicsPhaseEntry 7 }
eoACPwrCharDelPhaseTable OBJECT-TYPE eoACPwrCharacteristicsDelPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrCharDelPhaseEntry SYNTAX SEQUENCE OF
EoACPwrCharacteristicsDelPhaseEntry
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 Characteristics measurements. This is a sparse power characteristics measurements. This is a sparse
extension of the eoACPwrCharPhaseTable." extension of the eoACPwrCharacteristicsPhaseTable."
::= { powerCharacteristicsMIBObjects 3 } ::= { powerCharacteristicsMIBObjects 3 }
eoACPwrCharDelPhaseEntry OBJECT-TYPE eoACPwrCharacteristicsDelPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrCharDelPhaseEntry SYNTAX EoACPwrCharacteristicsDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes Power Characteristics attributes of "An entry describes power characteristics attributes of
a phase in a DEL 3-phase power system. Voltage a phase in a DEL 3-phase power system. Voltage
measurements are provided both relative to each other measurements are provided both relative to each other
and zero. 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 eoPhaseIndex 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:
eoPhaseIndex Next Phase Angle eoPhaseIndex Next Phase Angle
0 120 0 120
120 240 120 240
240 0 240 0
" "
INDEX { entPhysicalIndex, eoPhaseIndex} INDEX { entPhysicalIndex, eoPhaseIndex}
::= { eoACPwrCharDelPhaseTable 1} ::= { eoACPwrCharacteristicsDelPhaseTable 1}
EoACPwrCharDelPhaseEntry ::= SEQUENCE { EoACPwrCharacteristicsDelPhaseEntry ::= SEQUENCE {
eoACPwrCharDelPhaseToNextPhaseVoltage Integer32, eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage
eoACPwrCharDelThdPhaseToNextPhaseVoltage Integer32, Integer32,
eoACPwrCharDelThdCurrent Integer32 eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage
Integer32,
eoACPwrCharacteristicsDelThdCurrent
Integer32
} }
eoACPwrCharDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage 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'."
::= { eoACPwrCharDelPhaseEntry 2 } ::= { eoACPwrCharacteristicsDelPhaseEntry 2 }
eoACPwrCharDelThdPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage 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'."
::= { eoACPwrCharDelPhaseEntry 3 } ::= { eoACPwrCharacteristicsDelPhaseEntry 3 }
eoACPwrCharDelThdCurrent OBJECT-TYPE eoACPwrCharacteristicsDelThdCurrent 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'."
::= { eoACPwrCharDelPhaseEntry 4 } ::= { eoACPwrCharacteristicsDelPhaseEntry 4 }
eoACPwrCharWyePhaseTable OBJECT-TYPE eoACPwrCharacteristicsWyePhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrCharWyePhaseEntry SYNTAX SEQUENCE OF
EoACPwrCharacteristicsWyePhaseEntry
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 Characteristics measurements. This is a sparse power characteristics measurements. This is a sparse
extension of the eoACPwrCharPhaseTable." extension of the eoACPwrCharacteristicsPhaseTable."
::= { powerCharacteristicsMIBObjects 4 } ::= { powerCharacteristicsMIBObjects 4 }
eoACPwrCharWyePhaseEntry OBJECT-TYPE eoACPwrCharacteristicsWyePhaseEntry OBJECT-TYPE
SYNTAX EoACPwrCharWyePhaseEntry SYNTAX EoACPwrCharacteristicsWyePhaseEntry
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 Characteristics attributes. with phase to neutral power characteristics attributes.
Three entries are required for each supported Three entries are required for each supported
entPhysicalIndex entry. Voltage measurements are entPhysicalIndex entry. Voltage measurements are
relative to neutral. relative to neutral.
This is a sparse extension of the eoACPwrCharPhaseTable. This is a sparse extension of the
eoACPwrCharacteristicsPhaseTable.
Each entry describes Power Characteristics attributes of Each entry describes power characteristics attributes of
one phase of a WYE 3-phase power system. one phase of 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 { entPhysicalIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrCharWyePhaseTable 1} ::= { eoACPwrCharacteristicsWyePhaseTable 1}
EoACPwrCharWyePhaseEntry ::= SEQUENCE { EoACPwrCharacteristicsWyePhaseEntry ::= SEQUENCE {
eoACPwrCharWyePhaseToNeutralVoltage Integer32, eoACPwrCharacteristicsWyePhaseToNeutralVoltage
eoACPwrCharWyePhaseCurrent Integer32, Integer32,
eoACPwrCharWyeThdPhaseToNeutralVoltage Integer32 eoACPwrCharacteristicsWyePhaseCurrent
Integer32,
eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage
Integer32
} }
eoACPwrCharacteristicsWyePhaseToNeutralVoltage OBJECT-TYPE
eoACPwrCharWyePhaseToNeutralVoltage 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'."
::= { eoACPwrCharWyePhaseEntry 1 } ::= { eoACPwrCharacteristicsWyePhaseEntry 1 }
eoACPwrCharWyePhaseCurrent OBJECT-TYPE eoACPwrCharacteristicsWyePhaseCurrent 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'."
::= { eoACPwrCharWyePhaseEntry 2 } ::= { eoACPwrCharacteristicsWyePhaseEntry 2 }
eoACPwrCharWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage 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'."
::= { eoACPwrCharWyePhaseEntry 3 } ::= { eoACPwrCharacteristicsWyePhaseEntry 3 }
-- Conformance -- Conformance
powerCharacteristicsMIBCompliances OBJECT IDENTIFIER powerCharacteristicsMIBCompliances OBJECT IDENTIFIER
::= { powerCharacteristicsMIB 2 } ::= { powerCharacteristicsMIB 2 }
powerCharacteristicsMIBGroups OBJECT IDENTIFIER powerCharacteristicsMIBGroups OBJECT IDENTIFIER
::= { powerCharacteristicsMIB 3 } ::= { powerCharacteristicsMIB 3 }
powerCharacteristicsMIBFullCompliance MODULE-COMPLIANCE powerCharacteristicsMIBFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for read-create, then "When this MIB is implemented with support for read-create,
such an implementation can claim full compliance. Such devices then such an implementation can claim full compliance.
can then be both monitored and configured with this MIB. The Such devices can then be both monitored and configured with
entPhysicalIndex, entPhysicalName, and entPhysicalUris [RFC4133] this MIB.
MUST be implemented."
Module Compliance of [EMAN-ENTITY] with respect to
entity4CRCompliance should be supported which requires
implementation of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerACPwrCharMIBTableGroup powerACPwrCharacteristicsMIBTableGroup
} }
GROUP powerACPwrCharOptionalMIBTableGroup GROUP powerACPwrCharacteristicsOptionalMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have "A compliant implementation does not have
to implement." to implement."
GROUP powerACPwrCharPhaseMIBTableGroup GROUP powerACPwrCharacteristicsPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
GROUP powerACPwrCharDelPhaseMIBTableGroup GROUP powerACPwrCharacteristicsDelPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
GROUP powerACPwrCharWyePhaseMIBTableGroup GROUP powerACPwrCharacteristicsWyePhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
::= { powerCharacteristicsMIBCompliances 1 } ::= { powerCharacteristicsMIBCompliances 1 }
-- Units of Conformance -- Units of Conformance
powerACPwrCharMIBTableGroup OBJECT-GROUP powerACPwrCharacteristicsMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex is NOT -- Note that object entPhysicalIndex is NOT
-- included since it is not-accessible -- included since it is not-accessible
eoACPwrCharAvgVoltage, eoACPwrCharacteristicsAvgVoltage,
eoACPwrCharAvgCurrent, eoACPwrCharacteristicsAvgCurrent,
eoACPwrCharFrequency, eoACPwrCharacteristicsFrequency,
eoACPwrCharPowerUnitMultiplier,
eoACPwrCharPowerAccuracy, eoACPwrCharacteristicsPowerUnitMultiplier,
eoACPwrCharTotalActivePower, eoACPwrCharacteristicsPowerAccuracy,
eoACPwrCharTotalReactivePower, eoACPwrCharacteristicsTotalActivePower,
eoACPwrCharTotalApparentPower,
eoACPwrCharTotalPowerFactor eoACPwrCharacteristicsTotalReactivePower,
} STATUS
current eoACPwrCharacteristicsTotalApparentPower,
eoACPwrCharacteristicsTotalPowerFactor
}
STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the Power "This group contains the collection of all the power
Characteristics objects related to the Energy Object." characteristics objects related to the Energy Object."
::= { powerCharacteristicsMIBGroups 1 } ::= { powerCharacteristicsMIBGroups 1 }
powerACPwrCharOptionalMIBTableGroup OBJECT-GROUP powerACPwrCharacteristicsOptionalMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoACPwrCharConfiguration, eoACPwrCharacteristicsConfiguration,
eoACPwrCharThdAmpheres, eoACPwrCharacteristicsThdAmpheres,
eoACPwrCharThdVoltage eoACPwrCharacteristicsThdVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the Power "This group contains the collection of all the power
Characteristics objects related to the Energy Object." characteristics objects related to the Energy Object."
::= { powerCharacteristicsMIBGroups 2 } ::= { powerCharacteristicsMIBGroups 2 }
powerACPwrCharPhaseMIBTableGroup OBJECT-GROUP powerACPwrCharacteristicsPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex is NOT -- Note that object entPhysicalIndex is
-- included since it is not-accessible -- NOT included since it is
eoACPwrCharPhaseAvgCurrent, -- not-accessible
eoACPwrCharPhaseActivePower, eoACPwrCharacteristicsPhaseAvgCurrent,
eoACPwrCharPhaseReactivePower, eoACPwrCharacteristicsPhaseActivePower,
eoACPwrCharPhaseApparentPower,
eoACPwrCharPhasePowerFactor, eoACPwrCharacteristicsPhaseReactivePower,
eoACPwrCharPhaseImpedance
eoACPwrCharacteristicsPhaseApparentPower,
eoACPwrCharacteristicsPhasePowerFactor,
eoACPwrCharacteristicsPhaseImpedance
} }
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
characteristics objects related to the Power State." characteristics objects related to the Power State."
::= { powerCharacteristicsMIBGroups 3 } ::= { powerCharacteristicsMIBGroups 3 }
powerACPwrCharDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrCharacteristicsDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrCharDelPhaseToNextPhaseVoltage ,
eoACPwrCharDelThdPhaseToNextPhaseVoltage, eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage ,
eoACPwrCharDelThdCurrent
eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage,
eoACPwrCharacteristicsDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all power "This group contains the collection of all power
characteristic attributes of a phase in a DEL 3-phase characteristic attributes of a phase in a DEL 3-phase
power system." power system."
::= { powerCharacteristicsMIBGroups 4 } ::= { powerCharacteristicsMIBGroups 4 }
powerACPwrCharWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrCharacteristicsWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrCharWyePhaseToNeutralVoltage,
eoACPwrCharWyePhaseCurrent, eoACPwrCharacteristicsWyePhaseToNeutralVoltage,
eoACPwrCharWyeThdPhaseToNeutralVoltage eoACPwrCharacteristicsWyePhaseCurrent,
eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage
} }
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 Characteristics configuration phase-to-neutral power characteristics
measurements." measurements."
::= { powerCharacteristicsMIBGroups 5 } ::= { powerCharacteristicsMIBGroups 5 }
END END
11. Security Considerations 11. Security Considerations
Some of the readable objects in these MIB modules (i.e., objects Some of the readable objects in these MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
skipping to change at page 77, line 29 skipping to change at page 79, line 4
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 We would like to thank Juergen Schoenwalder for proposing the
design of the Textual Convention for IANAPowerStateSet and Ira design of the Textual Convention for IANAPowerStateSet and Ira
McDonald for his feedback. Thanks for the many comments on the McDonald for his feedback. Thanks for the many comments on the
design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki.
14. Open Issues 14. Open Issues
OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are
OPEN ISSUE 1 Consideration of IEEE-ISTO PWG in the IANA list of
Power State Set ? Printer Power series could be added once the
IANA procedure is in place.
OPEN ISSUE 2 check if all the requirements from [EMAN-REQ] are
covered. covered.
OPEN ISSUE 3 IANA Registered Power State Sets deferred to [EMAN- OPEN ISSUE 2 IANA Registered Power State Sets deferred to [EMAN-
FRAMEWORK] FMWK]
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
skipping to change at page 78, line 36 skipping to change at page 79, line 41
RFC3621, December 2003. RFC3621, December 2003.
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version
3)", RFC 4133, August 2005. 3)", RFC 4133, August 2005.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
[EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman-
energy-aware-mib-06 ", work in progress, July 2012. energy-aware-mib-05 ", work in progress, March 2012.
15.3. Informative References 15.3. Informative References
[RFC1628] S. Bradner, "UPS Management Information Base", RFC [RFC1628] S. Bradner, "UPS Management Information Base", RFC
1628, May 1994 1628, May 1994
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework ", RFC 3410, December Standard Management Framework ", RFC 3410, December
2002. 2002.
skipping to change at page 79, line 25 skipping to change at page 80, line 31
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie,
"Guidelines for Writing an IANA Considerations Section "Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008. in RFCs ", BCP 26, RFC 5226, May 2008.
[EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and
M. Chandramouli, " Requirements for Energy Management", M. Chandramouli, " Requirements for Energy Management",
draft-ietf-eman-requirements-07, July 2012. draft-ietf-eman-requirements-09, October 2012.
[EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., Quittek, J.
Quittek, "Energy Management Framework", draft-ietf- and Nordman, B, "Energy Management Framework", draft-
eman-framework-04, March 2012. ietf-eman-framework-05, July 2012.
[EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T.,
Quittek, J. and B. Claise "Energy and Power Monitoring Quittek, J. and B. Claise "Energy and Power Monitoring
MIB ", draft-ietf-eman-energy-monitoring-mib-02, March MIB ", draft-ietf-eman-energy-monitoring-mib-03, July
2012. 2012.
[EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B.
Management (EMAN) Applicability Statement", draft- "Energy Management (EMAN) Applicability Statement",
ietf-eman-applicability-statement-01, June 2012. draft-ietf-eman-applicability-statement-02, October 2012.
[EMAN-ENTITY] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", draft-ietf-
eman-rfc4133bis-03, October 2012.
[EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology", [EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology",
draft-parello-eman-definitions-06, work in progress, draft-parello-eman-definitions-07, work in progress,
July 2012. October 2012.
[ACPI] "Advanced Configuration and Power Interface [ACPI] "Advanced Configuration and Power Interface
Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3
0b.pdf 0b.pdf
[DMTF] "Power State Management Profile DMTF DSP1027 Version [DMTF] "Power State Management Profile DMTF DSP1027 Version
2.0" December 2009 2.0" December 2009
http://www.dmtf.org/sites/default/files/standards/docum http://www.dmtf.org/sites/default/files/standards/docum
ents/DSP1027_2.0.0.pdf ents/DSP1027_2.0.0.pdf
skipping to change at page 80, line 31 skipping to change at page 81, line 40
[IEC.62053-22]International Electrotechnical Commission, [IEC.62053-22]International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 0,2 S and 0,5 S)", 2003. (classes 0,2 S and 0,5 S)", 2003.
Authors' Addresses Authors' Addresses
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore, Bangalore 560103
IN IN
Phone: +91 80 4426 3947 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad@bradschoening.com Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-115 Phone: +49 6221 4342-115
 End of changes. 201 change blocks. 
432 lines changed or deleted 512 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/