draft-ietf-eman-energy-monitoring-mib-02.txt   draft-ietf-eman-energy-monitoring-mib-03.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: September 8, 2012 Independent Consultant Expires: January 12, 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.
March 9, 2012 July 11, 2012
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-02 draft-ietf-eman-energy-monitoring-mib-03
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 September 2012. This Internet-Draft will expire on January 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............................................. 4 1. Introduction............................................... 3
2. The Internet-Standard Management Framework............... 5 2. The Internet-Standard Management Framework................. 4
3. Use Cases................................................ 5 3. Use Cases.................................................. 4
4. Terminology.............................................. 5 4. Terminology................................................ 5
Energy Management.........................................6 5. Architecture Concepts Applied to the MIB Module........... 6
Energy Management System (EnMS)...........................6 5.1. Energy Object Information............................... 13
ISO Energy Management System..............................7 5.2. Power State............................................. 13
Energy....................................................7 5.2.1. Power State Set................................. 14
Power.....................................................7 5.2.2. IEEE1621 Power State Set........................ 15
Demand....................................................8 5.2.3. DMTF Power State Set............................ 15
Power Quality.............................................8 5.2.4. EMAN Power State Set............................ 16
Electrical Equipment......................................8 5.3. Energy Object Usage Information......................... 19
Non-Electrical Equipment (Mechanical Equipment)...........8 5.4. Optional Power Usage Characteristics.................... 20
Energy Object.............................................9 5.5. Optional Energy Measurement............................. 21
Electrical Energy Object..................................9 5.6. Fault Management........................................ 25
Non-Electrical Energy Object..............................9 6. Discovery................................................. 25
Energy Monitoring.........................................9 7. Link with the other IETF MIBs............................. 26
Energy Control............................................9 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB... 26
Energy Management Domain.................................10 7.2. Link with the ENTITY-STATE MIB....................... 27
Energy Object Identification.............................10 7.3. Link with the POWER-OVER-ETHERNET MIB................ 28
Energy Object Context....................................10 7.4. Link with the UPS MIB................................ 29
Energy Object Relationship...............................10 7.5. Link with the LLDP and LLDP-MED MIBs................. 30
Aggregation Relationship.................................11 8. Implementation Scenario................................... 30
Metering Relationship....................................11 9. Structure of the MIB...................................... 33
Power Source Relationship................................11 10. MIB Definitions.......................................... 34
Proxy Relationship.......................................11 11. Security Considerations.................................. 73
Dependency Relationship..................................12 12. IANA Considerations...................................... 74
Energy Object Parent.....................................12 12.1. IANA Considerations for the MIB Modules................ 74
Energy Object Child......................................12 12.2. IANA Registration of new Power State Set............... 75
Power State..............................................12 12.2.1. IANA Registration of the IEEE1621 Power State Set 75
Power State Set..........................................13 12.2.2. IANA Registration of the DMTF Power State Set.... 75
Nameplate Power..........................................13 12.2.3. IANA Registration of the EMAN Power State Set.... 76
5. Architecture Concepts Applied to the MIB Module......... 13 12.3. Updating the Registration of Existing Power State Sets. 76
5.1. Energy Object Information............................. 20 12. Contributors............................................. 77
5.2. Power State........................................... 20 13. Acknowledgment........................................... 77
5.2.1. Power State Set................................21 14. Open Issues.............................................. 77
5.2.2. IEEE1621 Power State Set.......................22 15. References............................................... 78
5.2.3. DMTF Power State Set...........................22 15.2. Normative References................................ 78
5.2.4. EMAN Power State Set...........................23 15.3. Informative References.............................. 78
5.3. Energy Object Usage Information....................... 26
5.4. Optional Power Usage Quality.......................... 27
5.5. Optional Energy Measurement........................... 28
5.6. Fault Management...................................... 32
6. Discovery............................................... 32
7. Link with the other IETF MIBs........................... 33
7.1. Link with theENTITY-MIBand the ENTITY-SENSOR MIB....33
7.2. Link with the ENTITY-STATE MIB......................34
7.3. Link with the POWER-OVER-ETHERNET MIB...............35
7.4. Link with the UPS MIB...............................35
7.5. Link with the LLDP and LLDP-MED MIBs................36
8. Implementation Scenario................................. 37
9. Structure of the MIB.................................... 39
10. MIB Definitions........................................ 40
11. Security Considerations................................ 78
12. IANA Considerations.................................... 79
12.1. IANA Considerations for the MIB Modules.............. 79
12.2. IANA Registration of new Power State Set............. 80
12.2.1. IANA Registration of the IEEE1621 Power State Set..80
12.2.2. IANA Registration of the DMTF Power State Set......81
12.2.3. IANA Registration of the EMAN Power State Set......81
12.3. Updating the Registration of Existing Power State
Sets................................................. 81
12. Contributors........................................... 82
13. Acknowledgment......................................... 82
14. Open Issues............................................ 82
15. References............................................. 84
15.2. Normative References...............................84
15.3. Informative References.............................84
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-FRAMEWORK], which in turn, is based
on the Requirements for Energy Management[EMAN-REQ]. on the Requirements for Energy Management[EMAN-REQ].
Energy management is applicable to devices in communication Energy management is applicable to devices in communication
networks. Target devices for this specification include (but networks. Target devices for this specification include (but
are not limited to): routers, switches, Power over Ethernet are not limited to): routers, switches, Power over Ethernet
(PoE) endpoints, protocol gateways for building management (PoE) endpoints, protocol gateways for building management
systems, intelligent meters, home energy gateways, hosts and systems, intelligent meters, home energy gateways, hosts and
servers, sensor proxies, etc. 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 4, line 42 skipping to change at page 4, line 17
Where applicable, device monitoring extends to the individual Where applicable, device monitoring extends to the individual
components of the device and to any attached dependent devices. components of the device and to any attached dependent devices.
For example: A device can contain components that are For example: A device can contain components that are
independent from a power-state point of view, such as line independent from a power-state point of view, such as line
cards, processor cards, hard drives. A device can also have cards, processor cards, hard drives. A device can also have
dependent attached devices, such as a switch with PoE endpoints dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints. or a power distribution unit with attached endpoints.
Devices and their sub-components may be characterized by the Devices and their sub-components may be characterized by the
power-related attributes of a physical entity present in the power-related attributes of a physical entity present in the
ENTITY MIB, even though the ENTITY-MIB compliance is not a ENTITY-MIB, even though the ENTITY-MIB compliance is not a
requirement due to the variety and broad base of devices requirement due to the variety and broad base of devices
concerned with energy management. concerned with energy management.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please refer to current Internet-Standard Management Framework, please refer to
section 7 of RFC 3410 [RFC3410]. section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
skipping to change at page 5, line 38 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
EDITOR'S NOTE: Please refer to [EMAN-FRAMEWORK] for the definitions of the
- All terms are copied over from the version 4 of the following terminology used in this draft.
[EMAN-TERMINOLOGY] draft. The only difference in
definition is the Energy Management Domain, which has
been improved, to address one comment from Bill
Mielke. Hopefully, this version 4 is the final
version.
- "All" terms have been copied. Potentially, some
unused terms might have to be removed (example
Electrical Equipment". Alternatively, as this
document is the first standard track document in the
EMAN WG, it may become the reference document for the
terminology (instead of cutting/pasting the
terminology in all drafts)
- "Reference: herein" has not been copied over from
the terminology draft.
Energy Management
Energy Management is a set of functions for measuring,
modeling, planning, and optimizing networks to ensure
that the network elements and attached devices use
energy efficiently and is appropriate for the nature
of the application and the cost constraints of the
organization.
Reference: Adapted from [ITU-T-M-3400]
Example: A set of computer systems that will poll
electrical meters and store the readings
NOTES:
1. Energy management refers to the activities, methods,
procedures and tools that pertain to measuring,
modeling, planning, controlling and optimizing the
use of energy in networked systems [NMF].
2. Energy Management is a management domain which is
congruent to any of FCAPS areas of management in the
ISO/OSI Network Management Model [TMN]. Energy
Management for communication networks and attached
devices is a subset or part of an organization's
greater Energy Management Policies.
Energy Management System (EnMS)
An Energy Management System is a combination of
hardware and software used to administer a network
with the primarily purpose being Energy Management.
Reference: Adapted from [1037C]
Example: A single computer system that polls data from
devices using SNMP
NOTES:
1. An Energy Management System according to [ISO50001]
(ISO-EnMS) is a set of systems or procedures upon
which organizations can develop and implement an
energy policy, set targets, action plans and take
into account legal requirements related to energy
use. An EnMS allows organizations to improve energy
performance and demonstrate conformity to
requirements, standards, and/or legal requirements.
2. Example ISO-EnMS: Company A defines a set of
policies and procedures indicating there should
exist multiple computerized systems that will poll
energy from their meters and pricing / source data
from their local utility. Company A specifies that
their CFO should collect information and summarize
it quarterly to be sent to an accounting firm to
produce carbon accounting reporting as required by
their local government.
3. For the purposes of EMAN, the definition from
[1037C] is the preferred meaning of an Energy
Management System (EnMS). The definition from
[ISO50001] can be referred to as ISO Energy
Management System (ISO-EnMS).
ISO Energy Management System
Energy Management System as defined by [ISO50001]
Energy
That which does work or is capable of doing work. As
used by electric utilities, it is generally a
reference to electrical energy and is measured in
kilo-watt hours (kWh).
Reference: [IEEE100]
NOTES
1. Energy is the capacity of a system to produce
external activity or perform work [ISO50001]
Power
The time rate at which energy is emitted, transferred,
or received; usually expressed in watts (or in joules
per second).
Reference: [IEEE100]
Demand
The average value of power or a related quantity over
a specified interval of time. Note: Demand is
expressed in kilowatts, kilovolt-amperes, kilovars, or
other suitable units.
Reference: [IEEE100]
NOTES:
1. typically kilowatts
2. Energy providers typically bill by Demand
measurements as well as for maximum Demand per
billing periods. Power values may spike during
short-terms by devices, but Demand measurements
recognize that maximum Demand does not equal maximum
Power during an interval.
Power Quality
Characteristics of the electric current, voltage and
frequencies at a given point in an electric power
system, evaluated against a set of reference technical
parameters. These parameters might, in some cases,
relate to the compatibility between electricity
supplied in an electric power system and the loads
connected to that electric power system.
Reference: [IEC60050]
Electrical Equipment
A general term including materials, fittings, devices,
appliances, fixtures, apparatus, machines, etc., used
as a part of, or in connection with, an electric
installation.
Reference: [IEEE100]
Non-Electrical Equipment (Mechanical Equipment)
A general term including materials, fittings, devices
appliances, fixtures, apparatus, machines, etc., used
as a part of, or in connection with, non-electrical
power installations.
Reference: Adapted from [IEEE100]
Energy Object
An Energy Object (EO) is a piece of equipment that is
part of or attached to a communications network that
is monitored, controlled, or aids in the management of
another device for Energy Management.
Electrical Energy Object
An Electrical Energy Object (EEO) is an Energy Object
that is a piece of Electrical Equipment
Non-Electrical Energy Object
A Non-Electrical Energy Object (NEEO) an Energy Object
that is a piece of Non-Electrical Equipment.
Energy Monitoring
Energy Monitoring is a part of Energy Management that
deals with collecting or reading information from
Energy Objects to aid in Energy Management.
NOTES:
1. This could include Energy, Power, Demand, Power
Quality, Context and/or Battery information.
Energy Control
Energy Control is a part of Energy Management that
deals with directing influence over Energy Objects.
NOTES:
1. Typically in order to optimize or ensure its
efficiency.
Energy Management Domain
An Energy Management Domain is a set of Energy Objects where all
objects in the domain are considered one unit of management.
For example, power distribution units and all of the attached
Energy Objects are part of the same Energy Management Domain.
For example, all EEO's drawing power from the same
distribution panel with the same AC voltage within a
building, or all EEO's in a building for which there
is one main meter, would comprise an Energy Management
Domain.
NOTES:
1. Typically, this set will have as members all EO's
that are powered from the same source.
Energy Object Identification
Energy Object Identification is a set of attributes
that enable an Energy Object to be: uniquely
identified among all Energy Management Domains; linked
to other systems; classified as to type, model, and or
manufacturer
Energy Object Context
Energy Object Context is a set of attributes that
allow an Energy Management System to classify the use
of the Energy Object within an organization.
NOTES:
1. The classification could contain the use and/or the
ranking of the Energy Object as compared to other
Energy Objects in the Energy Management Domain.
Energy Object Relationship
An Energy Objects Relationship is a functional Device
association between one or more Energy Objects
NOTES Component
1. Relationships can be named and could include
Aggregation, Metering, Power Source, Proxy and
Dependency.
Aggregation Relationship Energy Management
An Energy Object may aggregate the Energy Management Energy Management System (EnMS)
information of one or more Energy Objects and is
referred to as an Aggregation Relationship.
NOTES:
1. Aggregate values may be obtained by reading values
from multiple Energy Objects and producing a single
value of more significant meaning such as average,
count, maximum, median, minimum, mode and most
commonly sum [SQL].
Metering Relationship ISO Energy Management System
An Energy Object may measure the Power or Energy of Energy
another Energy Object(s) and is referred to as a
Metering Relationship.
Example: a PoE port on a switch measures the Power it Power
provides to the connected Energy Object.
Power Source Relationship Demand
An Energy Object may be the source of or distributor Power Characteristics
of Power to another Energy Object(s) and is referred
to as a Power Source Relationship.
Example: a PDU provides power for a connected host. Electrical Equipment
Proxy Relationship Non-Electrical Equipment (Mechanical Equipment)
An Energy Object that provides Energy Management Energy Object
capabilities on behalf of another Energy Object is
referred to a Proxy Relationship.
Example: a protocol gateways device for Building Electrical Energy Object
Management Systems (BMS) with subtended devices.
Dependency Relationship Non-Electrical Energy Object
An Energy Object may be a component of or rely Energy Monitoring
completely upon another Energy Object to operate and
is referred to as a Dependency Relationship.
Example: A Switch chassis with multiple line cards. Energy Control
Energy Object Parent Provide Energy:
An Energy Object Parent is an Energy Object that Receive Energy:
participates in an Energy Object Relationships and is
considered as providing the capabilities in the
relationship.
Energy Object Child Power Interface
Power Inlet
An Energy Object Child is an Energy Object that Power Outlet
participates in an Energy Object Relationships and is
considered as receiving the capabilities in the
relationship.
Power State Energy Management Domain
A Power State is a condition or mode of a device that Energy Object Identification
broadly characterizes its capabilities, power
consumption, and responsiveness to input.
Reference: Adapted from [IEEE1621] Energy Object Context
NOTES: Energy Object Relationship
1. A Power State can be seen as a power setting of an Aggregation Relationship
Energy Object that influences the power
consumption, the available functionality, and the
responsiveness of the Energy Object.
2. A Power State can be viewed as one method for Metering Relationship
Energy Control
Power State Set Power Source Relationship
A collection of Power States that comprise one named Proxy Relationship
or logical grouping of control is a Power State Set.
Example: The states {on, off, and sleep} as defined in Energy Object Parent
[IEEE1621], or the 16 power states as defined by the
[DMTF] can be considered two different Power State
Sets.
Nameplate Power Energy Object Child
The Nameplate Power is the maximal (nominal) Power Power State
that a device can support.
NOTES: Power State Set
1. This is typically determined via load testing and Nameplate Power
is specified by the manufacturer as the maximum
value required for operating the device. This is
sometimes referred to as the worst-case Power. The
actual or average Power may be lower. The
Nameplate Power is typically used for provisioning
and capacity planning.
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-FRAMEWORK] that pertain to power
usage, with specific information related to the MIB module usage, with specific information related to the MIB module
specified in this document. This subsection maps to the section specified in this document. This subsection maps to the section
"Architecture High Level Concepts" in the Power Monitoring "Architecture High Level Concepts" in the Power Monitoring
Architecture [EMAN-FRAMEWORK]. Architecture [EMAN-FRAMEWORK].
The Energy Monitoring MIB has 2 independent MIB modules. The The Energy Monitoring MIB has 2 independent MIB modules. The
first MIB module energyObjectMib is focused on measurement of first MIB module energyObjectMib is focused on measurement of
power and energy. The second MIB module powerQualityMIB is power and energy. The second MIB module powerCharMIB is focused
focused on Power Quality 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 and second table eoPowerStateTable indexed by entPhysicalIndex,
eoPowerStateIndex. The eoEnergyParametersTable is indexed and eoPowerStateIndex. The eoEnergyParametersTable is indexed
by eoEnergyParametersIndex. The eoEnergyTable is indexed by by eoEnergyParametersIndex. The eoEnergyTable is indexed by
eoEnergyParametersIndex and eoEnergyCollectionStartTime. eoEnergyParametersIndex and eoEnergyCollectionStartTime.
eoMeterCapabilitiesTable(1)
|
+--- eoMeterCapabilitiesEntry(1) [entPhysicalIndex]
| |
| +---r-n BITS eoMeterCapability
|
eoPowerTable(1) eoPowerTable(1)
| |
+---eoPowerEntry(1) [entPhysicalIndex] +---eoPowerEntry(1) [entPhysicalIndex]
| | | |
| +---r-n Integer32 eoPower(1) | +---r-n Integer32 eoPower(1)
| +-- r-n Integer32 eoPowerNamePlate(2) | +-- r-n Integer32 eoPowerNamePlate(2)
| +-- r-n UnitMultiplier eoPowerUnitMultiplier(3) | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3)
| +-- r-n Integer32 eoPowerAccuracy(4) | +-- r-n Integer32 eoPowerAccuracy(4)
| +-- r-n INTEGER eoMeasurementCaliber(5) | +-- r-n INTEGER eoMeasurementCaliber(5)
| +-- r-n INTEGER eoPowerCurrentType(6) | +-- r-n INTEGER eoPowerCurrentType(6)
skipping to change at page 14, line 31 skipping to change at page 7, line 41
+---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)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersIntervalNumber (4) | eoEnergyParametersIntervalNumber (4)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersIntervalMode (5) | eoEnergyParametersIntervalMode (5)
| +-- r-n TimeInterval | +-- r-n TimeInterval
| eoEnergyParametersIntervalWindow (6) | eoEnergyParametersIntervalWindow (6)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersSampleRate (7) | eoEnergyParametersSampleRate (7)
| +-- r-n RowStatus eoEnergyParametersStatus (8) | +-- r-n RowStatus eoEnergyParametersStatus (8)
| |
+eoEnergyTable (1) +eoEnergyTable (1)
+---eoEnergyEntry(1) [eoEnergyParametersIndex, +---eoEnergyEntry(1) [ eoEnergyParametersIndex,
eoEnergyCollectionStartTime] eoEnergyCollectionStartTime]
| |
| +-- r-n TimeTicks eoEnergyCollectionStartTime (1) | +-- r-n TimeTicks eoEnergyCollectionStartTime (1)
| +-- r-n Integer32 eoEnergyConsumed (2) | +-- r-n Integer32 eoEnergyConsumed (2)
| +-- r-n Integer32 eoEnergyyProduced (3) | +-- r-n Integer32 eoEnergyyProduced (3)
| +-- r-n Integer32 eoEnergyNet (4) | +-- r-n Integer32 eoEnergyNet (4)
| +-- 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 powerQualityMIB consists of four tables. eoACPwrQualityTable The powerCharacteristicsMIB consists of four tables.
is indexed by entPhysicalIndex. eoACPwrQualityPhaseTable is eoACPwrCharTable is indexed by entPhysicalIndex.
indexed by entPhysicalIndex and eoPhaseIndex. eoACPwrCharPhaseTable is indexed by entPhysicalIndex and
eoACPwrQualityWyePhaseTable and eoACPwrQualityDelPhaseTable are eoPhaseIndex. eoACPwrCharWyePhaseTable and
indexed by entPhysicalIndex and eoPhaseIndex. eoACPwrCharDelPhaseTable are indexed by entPhysicalIndex and
eoPhaseIndex.
eoPowerQualityTable(1) eoACPwrCharTable(1)
| |
+---eoACPwrQualityEntry (1) [entPhysicalIndex] +---eoACPwrCharEntry (1) [ entPhysicalIndex]
| | | |
| | | |
| +---r-n INTEGER eoACPwrQualityConfiguration (1) | +---r-n INTEGER eoACPwrCharConfiguration (1)
| +-- r-n Interger32 eoACPwrQualityAvgVoltage (2) | +-- r-n Interger32 eoACPwrCharAvgVoltage (2)
| +-- r-n Integer32 eoACPwrQualityAvgCurrent (3) | +-- r-n Integer32 eoACPwrCharAvgCurrent (3)
| +-- r-n Integer32 eoACPwrQualityFrequency (4) | +-- r-n Integer32 eoACPwrCharFrequency (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoACPwrQualityPowerUnitMultiplier (5) | eoACPwrCharPowerUnitMultiplier (5)
| +-- r-n Integer32 eoACPwrQualityPowerAccuracy (6) | +-- r-n Integer32 eoACPwrCharPowerAccuracy (6)
| +-- r-n Interger32 eoACPwrQualityTotalActivePower (7) | +-- r-n Interger32 eoACPwrCharTotalActivePower (7)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrQualityTotalReactivePower (8) | eoACPwrCharTotalReactivePower (8)
| +-- r-n Integer32 eoACPwrQualityTotalApparentPower (9) | +-- r-n Integer32 eoACPwrCharTotalApparentPower (9)
| +-- r-n Integer32 eoACPwrQualityTotalPowerFactor(10) | +-- r-n Integer32 eoACPwrCharTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrQualityThdAmpheres (11) | +-- r-n Integer32 eoACPwrCharThdAmpheres (11)
| |
+eoACPwrQualityPhaseTable (1) +eoACPwrCharPhaseTable (1)
+---EoACPwrQualityPhaseEntry(1)[entPhysicalIndex, +---EoACPwrCharPhaseEntry(1)[ entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| | | |
| +-- r-n Integer32 eoPhaseIndex (1) | +-- r-n Integer32 eoPhaseIndex (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseAvgCurrent (2) | | eoACPwrCharPhaseAvgCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseActivePower (3) | | eoACPwrCharPhaseActivePower (3)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseReactivePower (4) | | eoACPwrCharPhaseReactivePower (4)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseApparentPower (5) | | eoACPwrCharPhaseApparentPower (5)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhasePowerFactor (6) | | eoACPwrCharPhasePowerFactor (6)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseImpedance (7) | | eoACPwrCharPhaseImpedance (7)
| | | |
+eoACPwrQualityDelPhaseTable (1) +eoACPwrCharDelPhaseTable (1)
+-- eoACPwrQualityDelPhaseEntry(1) +-- eoACPwrCharDelPhaseEntry(1)
| | [entPhysicalIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityDelPhaseToNextPhaseVoltage (1) | | eoACPwrCharDelPhaseToNextPhaseVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityDelThdPhaseToNextPhaseVoltage (2) | | eoACPwrCharDelThdPhaseToNextPhaseVoltage (2)
| +-- r-n Integer32 eoACPwrQualityDelThdCurrent (3) | +-- r-n Integer32 eoACPwrCharDelThdCurrent (3)
| | | |
+eoACPwrQualityWyePhaseTable (1) +eoACPwrCharWyePhaseTable (1)
+-- eoACPwrQualityWyePhaseEntry (1) +-- eoACPwrCharWyePhaseEntry (1)
| | [entPhysicalIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyePhaseToNeutralVoltage (1) | | eoACPwrCharWyePhaseToNeutralVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyePhaseCurrent (2) | | eoACPwrCharWyePhaseCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyeThdPhaseToNeutralVoltage (3) | | eoACPwrCharWyeThdPhaseToNeutralVoltage (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 powerQualityMIB are presented. are energyObjectMib and powerCharacteristicsMIB are presented.
+--------------------------+ +--------------------------+
| Energy Object ID | | Energy Object ID |
| ----------------------- | | ----------------------- |
| | | |
| entPhysIndex (*) | | entPhysIndex (*) |
| entPhysicalName (*) | | entPhysicalName (*) |
| entPhysicalUris (*) | +---------------------------+ | entPhysicalUris (*) | +---------------------------+
| (EO UUID) | | | | (EO UUID) | | |
| | | Energy Object Attributes | | | | Energy Object Attributes |
skipping to change at page 17, line 26 skipping to change at page 10, line 29
+--------------------------+ | eoPowerNamePlate | +--------------------------+ | eoPowerNamePlate |
| | | eoPowerMeasurementCaliber | | | | eoPowerMeasurementCaliber |
| | | eoPowerOrigin | | | | eoPowerOrigin |
| | | eoPowerCurrentType | | | | eoPowerCurrentType |
| | +---------------------------+ | | +---------------------------+
| | | | | |
| | | | | |
v | v v | v
+-----------------------------------------+ +-----------------------------------------+
| Energy Object Measurement | | Energy Object Measurement |
|--------------------------------------- | | --------------------------------------- |
| eoPower | | eoPower |
| eoPowerUnitMultiplier | | eoPowerUnitMultiplier |
| eoPowerAccuracy | | eoPowerAccuracy |
+-----------------------------------------+ +-----------------------------------------+
^ | ^ ^ | ^
| | | | | |
+-------------------------+ | | +-------------------------+ | |
| Energy Object State | | +------------------------+ | Energy Object State | | +------------------------+
| ----------------------- | | | Energy Object State | | ----------------------- | | | Energy Object State |
| eoPowerAdminState | | | Statistics | | eoPowerAdminState | | | Statistics |
skipping to change at page 19, line 11 skipping to change at page 12, line 13
| EnergyObject ID | | EnergyObject ID |
| ----------------------- | | ----------------------- |
| | | |
| | | |
| entPhysicalIndex (*) | | entPhysicalIndex (*) |
| | | |
+--------------------------+ +--------------------------+
| |
v v
+-------------------------------------+ +-------------------------------------+
| Power Quality | | Power Characteristics |
| ----------------------------------- | | ----------------------------------- |
| eoACPwrQualityConfiguration | | eoACPwrCharConfiguration |
| eoACPwrQualityAvgVoltage | | eoACPwrCharAvgVoltage |
| eoACPwrQualityAvgCurrent | | eoACPwrCharAvgCurrent |
| eoACPwrQualityFrequency | | eoACPwrCharFrequency |
| eoACPwrQualityPowerUnitMultiplier | | eoACPwrCharPowerUnitMultiplier |
| eoACPwrQualityPowerAccuracy | | eoACPwrCharPowerAccuracy |
| eoACPwrQualityTotalActivePower | | eoACPwrCharTotalActivePower |
| eoACPwrQualityTotalReactivePower | | eoACPwrCharTotalReactivePower |
| eoACPwrQualityTotalApparentPower | | eoACPwrCharTotalApparentPower |
| eoACPwrQualityTotalPowerFactor | | eoACPwrCharTotalPowerFactor |
| eoACPwrQualityThdAmpheres | | eoACPwrCharThdAmpheres |
+-------------------------------------+ ^ +-------------------------------------+ ^
^ ^ | ^ ^ |
| | ------- | | -------
| ---- | | ---- |
| | | | | |
| | | | | |
+-------------------------------------+ | | +-------------------------------------+ | |
| Power Phase Quality | | | | Power Phase Characteristics | | |
| ---------------------------------- | | | | ---------------------------------- | | |
| eoPhaseIndex | | | | eoPhaseIndex | | |
| eoACPwrQualityPhaseAvgCurrent | | | | eoACPwrCharPhaseAvgCurrent | | |
| eoACPwrQualityAvgCurrent | | | | eoACPwrCharAvgCurrent | | |
| eoACPwrQualityFrequency | | | | eoACPwrCharFrequency | | |
| eoACPwrQualityPowerUnitMultiplier | | | | eoACPwrCharPowerUnitMultiplier | | |
| eoACPwrQualityPowerAccuracy | | | | eoACPwrCharPowerAccuracy | | |
| eoACPwrQualityPhaseActivePower | | | | eoACPwrCharPhaseActivePower | | |
| eoACPwrQualityPhaseReactivePower | | | | eoACPwrCharPhaseReactivePower | | |
| eoACPwrQualityPhaselApparentPower | | | | eoACPwrCharPhaselApparentPower | | |
| eoACPwrQualityPhaseImpedance | | | | eoACPwrCharPhaseImpedance | | |
+-------------------------------------+ | | +-------------------------------------+ | |
| | | |
| | | |
+---------------------------------------------+ | +---------------------------------------------+ |
| Power Quality DEL Configuration | | | AC Input DEL Configuration | |
| | | | | |
| eoACPwrQualityDelPhaseToNextPhaseVoltage | | | eoACPwrCharDelPhaseToNextPhaseVoltage | |
| eoACPwrQualityDelThdPhaseToNextPhaseVoltage | | | eoACPwrCharDelThdPhaseToNextPhaseVoltage | |
| eoACPwrQualityDelThdCurrent | | | eoACPwrCharDelThdCurrent | |
+---------------------------------------------+ | +---------------------------------------------+ |
| |
| |
+---------------------------------------------+ +---------------------------------------------+
| Power Quality WYE Configuration | | AC Input WYE Configuration |
| | | |
| eoACPwrQualityWyePhaseToNeutralVoltage | | eoACPwrCharWyePhaseToNeutralVoltage |
| eoACPwrQualityWyePhaseCurrent | | eoACPwrCharWyePhaseCurrent |
| eoACPwrQualityWyeThdPhaseToNeutralVoltage | | eoACPwrCharWyeThdPhaseToNeutralVoltage |
+---------------------------------------------+ +---------------------------------------------+
Figure 2: UML diagram for the powerQualityMIB 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-
FRAMEWORK] for background information. An energy aware device FRAMEWORK] for background information. An energy aware device
is considered as an instance of a Energy Object as defined in is considered as an instance of a Energy Object as defined in
the [EMAN-FRAMEWORK]. the [EMAN-FRAMEWORK].
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 entPhysicalUris and entPhysicalIndex. The ENERGY-AWARE-MIB
module returns the relationship (parent/child) between Energy module returns the relationship (parent/child) between Energy
Objects. Objects. There are several possible relationships between Parent
and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy,
EDITOR'S NOTE: this last sentence will have to be updated with PoweredBy, AggregatedBy and ProxyedBy.
terms such as Aggregator, Proxy, etc... when the [EMAN-
FRAMEWORK] will stabilize.
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-FRAMEWORK] 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,
management station name, network manager's name, location, or management station name, network manager's name, location, or
skipping to change at page 23, line 39 skipping to change at page 16, line 42
--------------------------------------------------- ---------------------------------------------------
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 expansion consumption of a device. The EMAN Power States are an
of the basic Power States as defined in IEEE1621 that also expansion of the basic Power States as defined in IEEE1621 that
incorporate the Power States defined in ACPI and DMTF. also 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).
skipping to change at page 26, line 31 skipping to change at page 19, line 34
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. FRAMEWORK] 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 eoACPwrQualityPowerUnitMultiplier. eoEnergyUnitMultiplier, and eoACPwrCharPowerUnitMultiplier.
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 Quality 5.4. Optional Power Usage Characteristics
Refer to the "Optional Power Usage Quality" section in [EMAN- Refer to the "Optional Power Usage Characteristics" section in
FRAMEWORK] for background information. [EMAN-FRAMEWORK] for background information.
The optional powerQualityMIB MIB module can be implemented to The optional powerCharacteristicsMIB MIB module can be
further describe power usage quality measurement. The implemented to further describe power usage characteristics
powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 measurement. The powerCharacteristicsMIB MIB module adheres
standard to describe AC measurements. closely to the IEC 61850 7-2 standard to describe AC
measurements.
The powerQualityMIB MIB module contains a primary table, the The powerCharacteristicsMIB MIB module contains a primary table,
eoACPwrQualityTable table, that defines power quality the eoACPwrCharTable table, that defines Power Characteristics
measurements for supported entPhysicalIndex entities, as a measurements for supported entPhysicalIndex entities, as a
sparse extension of the eoPowerTable (with entPhysicalIndex as sparse extension of the eoPowerTable (with entPhysicalIndex as
primary index). This eoACPwrQualityTable table contains such primary index). This eoACPwrCharTable table contains such
information as the configuration (single phase, DEL 3 phases, information as the configuration (single phase, DEL 3 phases,
WYE 3 phases), voltage, frequency, power accuracy, total WYE 3 phases), voltage, frequency, power accuracy, total
active/reactive power/apparent power, amperage, and voltage. active/reactive power/apparent power, amperage, and voltage.
In case of 3-phase power, the eoACPwrQualityPhaseTable In case of 3-phase power, the eoACPwrCharPhaseTable additional
additional table is populated with power quality measurements table is populated with Power Characteristics measurements per
per phase (so double indexed by the entPhysicalIndex and phase (so double indexed by the entPhysicalIndex and
eoPhaseIndex). This table, which describes attributes common to eoPhaseIndex). This table, which describes attributes common to
both WYE and DEL configurations, contains the average current, both WYE and DEL configurations, contains the average current,
active/reactive/apparent power, power factor, and impedance. active/reactive/apparent power, power factor, and impedance.
In case of 3-phase power with a DEL configuration, the In case of 3-phase power with a DEL configuration, the
eoACPwrQualityDelPhaseTable table describes the phase-to-phase eoACPwrCharDelPhaseTable table describes the phase-to-phase
power quality measurements, i.e., voltage and current. 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
eoACPwrQualityWyePhaseTable table describes the phase-to-neutral eoACPwrCharWyePhaseTable table describes the phase-to-neutral
power quality measurements, i.e., voltage and current. 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-FRAMEWORK] for the definition and terminology information.
It is relevant to measure energy when there are actual power It is relevant to measure energy when there are actual power
measurements from 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.
skipping to change at page 30, line 38 skipping to change at page 23, line 40
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy The eoEnergyParametersStatus is used to start and stop energy
usage logging. The status of this variable is "active" when usage logging. The status of this variable is "active" when
all the objects in eoEnergyParametersTable are appropriate which all the objects in eoEnergyParametersTable are appropriate which
in turn indicates if eoEnergyTable entries exist or not. in turn indicates if eoEnergyTable entries exist or not.
The eoEnergyTable consists of energy measurements in The eoEnergyTable consists of energy measurements in
eoEnergyConsumed, eoEnergyProduced and eoEnergyNet , the units eoEnergyConsumed, eoEnergyProduced and eoEnergyNet, the units of
of the measured energy eoEnergyUnitMultiplier, and the maximum the measured energy eoEnergyUnitMultiplier, and the maximum
observed energy within a window, eoEnergyMaxConsumed, observed energy within a window, eoEnergyMaxConsumed,
eoEnergyMaxProduced. eoEnergyMaxProduced.
Measurements of the total energy consumed by an Energy Object Measurements of the total energy consumed by an Energy Object
may suffer from interruptions in the continuous measurement of may suffer from interruptions in the continuous measurement of
energy consumption. In order to indicate such interruptions, energy consumption. In order to indicate such interruptions,
the object eoEnergyDiscontinuityTime is provided for indicating the object eoEnergyDiscontinuityTime is provided for indicating
the time of the last interruption of total energy measurement. the time of the last interruption of total energy measurement.
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418]
when the device was reset. when the device was reset.
The following example illustrates the eoEnergyTable and The following example illustrates the eoEnergyTable and
eoEnergyParametersTable: eoEnergyParametersTable:
First, in order to estimate energy, a time interval to sample First, in order to estimate energy, a time interval to sample
energy should be specified, i.e. energy should be specified, i.e.
eoEnergyParametersIntervalLength can be set to "900 seconds" or eoEnergyParametersIntervalLength can be set to "900 seconds" or
15 minutes and the number of consecutive intervals over which 15 minutes and the number of consecutive intervals over which
the maximum energy is calculated the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active (value 1) to indicate eoEnergyParametersStatus is set to active (value 1) to indicate
that the Energy Object should start monitoring the usage per the that the Energy Object should start monitoring the usage per the
eoEnergyTable. eoEnergyTable.
The indices for the eoEnergyTable are eoEnergyParametersIndex The indices for the eoEnergyTable are eoEnergyParametersIndex
which identifies the index for the setting of energy measurement which identifies the index for the setting of energy measurement
collection Energy Object, and eoEnergyCollectionStartTime, which collection Energy Object, and eoEnergyCollectionStartTime, which
denotes the start time of the energy measurement interval based denotes the start time of the energy measurement interval based
on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
measured energy consumption over the time interval specified measured energy consumption over the time interval specified
(eoEnergyParametersIntervalLength) based on the Energy Object (eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (eoEnergyParametersSampleRate). While internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the eoEnergyParametersIntervalLength and choosing the values for the eoEnergyParametersIntervalLength and
eoEnergyParametersSampleRate, it is recommended to take into eoEnergyParametersSampleRate, it is recommended to take into
consideration either the network element resources adequate to consideration either the network element resources adequate to
process and store the sample values, and the mechanism used to process and store the sample values, and the mechanism used to
calculate the eoEnergyConsumed. The units are derived from calculate the eoEnergyConsumed. The units are derived from
eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
"100" with eoEnergyUnitMultiplier equal to 0, the measured "100" with eoEnergyUnitMultiplier equal to 0, the measured
energy consumption of the Energy Object is 100 watt-hours. The energy consumption of the Energy Object is 100 watt-hours. The
eoEnergyMaxConsumed is the maximum energy observed and that can eoEnergyMaxConsumed is the maximum energy observed and that can
be "150 watt-hours". be "150 watt-hours".
The eoEnergyTable has a buffer to retain a certain number of The eoEnergyTable has a buffer to retain a certain number of
intervals, as defined by eoEnergyParametersIntervalNumber. If intervals, as defined by eoEnergyParametersIntervalNumber.
the default value of "10" is kept, then the eoEnergyTable If the default value of "10" is kept, then the eoEnergyTable
contains 10 energy measurements, including the maximum. contains 10 energy measurements, including the maximum.
Here is a brief explanation of how the maximum energy can be Here is a brief explanation of how the maximum energy can be
calculated. The first observed energy measurement value is calculated. The first observed energy measurement value is
taken to be the initial maximum. With each subsequent taken to be the initial maximum. With each subsequent
measurement, based on numerical comparison, maximum energy may measurement, based on numerical comparison, maximum energy may
be updated. The maximum value is retained as long as the be updated. The maximum value is retained as long as the
measurements are taking place. Based on periodic polling of measurements are taking place. Based on periodic polling of
this table, an NMS could compute the maximum over a longer this table, an NMS could compute the maximum over a longer
period, i.e. a month, 3 months, or a year. period, i.e. a month, 3 months, or a year.
skipping to change at page 32, line 25 skipping to change at page 25, line 34
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 entPhysicalIndex, entPhysicalUris and entPhysicalName from the
from the ENTITY-MIB [RFC4133]. As the index for the primary ENTITY-MIB [RFC4133]. As the index for the primary Energy
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
entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The
entPhysicalIndex characterizes the Energy Object in the entPhysicalIndex characterizes the Energy Object in the
energyObjectMib and powerQualityMIB MIB modules (this document). energyObjectMib and the powerCharacteristicsMIB MIB modules
(this document).
From there, the NMS must poll the eoPowerStateTable (specified From there, the NMS must poll the eoPowerStateTable (specified
in the energyObjectMib module in this document), which in the energyObjectMib module in this document), which
enumerates, amongst other things, the maximum power usage. As enumerates, amongst other things, the maximum power usage. As
the entries in eoPowerStateTable table are indexed by the the entries in eoPowerStateTable table are indexed by the
Energy Object ( entPhysicalIndex), by the Power State Set Energy Object ( entPhysicalIndex), by the Power State Set
(eoPowerStateIndex), the maximum power usage is discovered per (eoPowerStateIndex), the maximum power usage is discovered per
Energy Object, per Power State Set, and per Power Usage. In Energy Object, and the power usage per Power State of the Power
other words, polling the eoPowerStateTable allows the discovery State Set. In other words, polling the eoPowerStateTable allows
of each Power State within every Power State Set supported by the discovery of each Power State within every Power State Set
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 Quality thanks to the Finally, the NMS can monitor the Power Characteristics thanks to
powerQualityMIB MIB module, which reuses the entPhysicalIndex to the powerCharacteristicsMIB MIB module, which reuses the
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
an energy-management standpoint, the physical entities that an energy-management standpoint, the physical entities that
consume or produce energy are of interest. consume or produce energy are of interest.
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that
provides a standardized way of obtaining information (current provides a standardized way of obtaining information (current
value of the sensor, operational status of the sensor, and the value of the sensor, operational status of the sensor, and the
data units precision) from sensors embedded in networking data units precision) from sensors embedded in networking
devices. Sensors are associated with each index of devices. Sensors are associated with each index of
entPhysicalIndex of the ENTITY-MIB[RFC4133]. While the focus of entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus
the Power and Energy Monitoring MIB is on measurement of power of the Power and Energy Monitoring MIB is on measurement of
usage of networking equipment indexed by the ENTITY MIB, this power usage of networking equipment indexed by the ENTITY-MIB,
MIB proposes a customized power scale for power measurement and this MIB proposes a customized power scale for power measurement
different power state states of networking equipment, and and different power state states of networking equipment, and
functionality to configure the power state states. functionality to configure the power state states.
When this MIB module is used to monitor the power usage of When this MIB module is used to monitor the power usage of
devices like routers and switches, the ENTITY-MIB and ENTITY- devices like routers and switches, the ENTITY-MIB and ENTITY-
SENSOR MIB SHOULD be implemented. In such cases, the Energy SENSOR MIB SHOULD be implemented. In such cases, the Energy
Objects are modeled by the entPhysicalIndex through the Objects are modeled by the entPhysicalIndex through the
entPhysicalEntity MIB object specified in the eoTable in the entPhysicalEntity MIB object specified in the eoTable in the
ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB].
However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI
skipping to change at page 34, line 25 skipping to change at page 27, line 28
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the (compared to entPhySensorScale), with the mantissa and the
exponent values X * 10 ^ Y. exponent values X * 10 ^ Y.
Power measurements specifying the qualifier 'UNITS' for each Power measurements specifying the qualifier 'UNITS' for each
measured value in watts are used in the LLDP-EXT-MED-MIB, POE measured value in watts are used in the LLDP-EXT-MED-MIB, POE
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier
is used for the power measurement values. is used for the power measurement values.
One cannot assume that the ENTITY-MIBand ENTITY-SENSOR MIB are One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are
implemented for all Energy Objects that need to be monitored. A implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, monitoring typical example is a converged building gateway, monitoring
several other devices in the building, doing the proxy between several other devices in the building, doing the proxy between
SNMP and a protocol like BACNET. Another example is the home SNMP and a protocol like BACNET. Another example is the home
energy controller. In such cases, the eoPhysicalEntity value energy controller. In such cases, the eoPhysicalEntity value
contains the zero value, thanks to PhysicalIndexOrZero textual contains the zero value, thanks to PhysicalIndexOrZero textual
convention. convention.
The eoPower is similar to entPhySensorValue [RFC3433] and the The eoPower is similar to entPhySensorValue [RFC3433] and the
eoPowerUnitMultipler is similar to entPhySensorScale. eoPowerUnitMultipler is similar to entPhySensorScale.
skipping to change at page 35, line 21 skipping to change at page 28, line 27
Power-over-Ethernet MIB [RFC3621] provides an energy monitoring Power-over-Ethernet MIB [RFC3621] provides an energy monitoring
and configuration framework for power over Ethernet devices. and configuration framework for power over Ethernet devices.
The RFC introduces a concept of a port group on a switch to The RFC introduces a concept of a port group on a switch to
define power monitoring and management policy and does not use define power monitoring and management policy and does not use
the entPhysicalIndex as the index. Indeed, the the entPhysicalIndex as the index. Indeed, the
pethMainPseConsumptionPower is indexed by the pethMainPseConsumptionPower is indexed by the
pethMainPseGroupIndex, which has no mapping with the pethMainPseGroupIndex, which has no mapping with the
entPhysicalIndex. entPhysicalIndex.
One cannot assume that the Power-over-Ethernet MIB is One cannot assume that the Power-over-Ethernet MIB is
implemented for all Energy Objects that need to be monitored. A implemented for all Energy Objects that need to be monitored.
typical example is a converged building gateway, monitoring A typical example is a converged building gateway, monitoring
several other devices in the building, doing the proxy between several other devices in the building, doing the proxy between
SNMP and a protocol like BACNET. Another example is the home SNMP and a protocol like BACNET. Another example is the home
energy controller. In such cases, the eoethPortIndex and energy controller. In such cases, the eoethPortIndex and
eoethPortGrpIndex values contain the zero value, thanks to new eoethPortGrpIndex values contain the zero value, thanks to new
PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero
conventions. conventions.
However, if the Power-over-Ethernet MIB [RFC3621] is supported, However, if the Power-over-Ethernet MIB [RFC3621] is supported,
the Energy Object eoethPortIndex and eoethPortGrpIndex contain the Energy Object eoethPortIndex and eoethPortGrpIndex contain
the pethPsePortIndex and pethPsePortGroupIndex, respectively. the pethPsePortIndex and pethPsePortGroupIndex, respectively.
skipping to change at page 39, line 17 skipping to change at page 32, line 31
| ======================================================| | ======================================================|
| ^ | ^
| | | |
|-----------------------------------|------------------- |-----------------------------------|-------------------
| |
| |
POE IP PHONE | POE IP PHONE |
| |
| |
====================================================== ======================================================
| IP phone | IP phone | IP phone | IP phone | | IP phone | IP phone | IP phone | IP phone |
| entPhyIndx | UUID | eoParentID | eoPower | | entPhyIndx | UUID | eoParentID | eoPower |
====================================================== ======================================================
| Null | UUID 1000:31| UUID 1000:3 | 12 | | Null | UUID 1000:31| UUID 1000:3 | 12 |
===================================================== =======================================================
| |
| |
PC connected to switch via IP phone | PC connected to switch via IP phone |
| |
================================================== =====================================================
| PC | PC |PC | PC | | PC | PC | PC | PC |
|eoPhyIndx | UUID |eoParentID | eoPower | |entPhyIndx | UUID | eoParentID | eoPower |
================================================== =====================================================
| Null | UUID1000:57 | UUID 1000:3 | 120 | | 7 | UUID 1000:57| UUID 1000:3 | 120 |
================================================= =====================================================
Figure 1: Example scenario Figure 1: Example scenario
9. Structure of the MIB 9. Structure of the MIB
The primary MIB object in this MIB module is the The primary MIB object in this MIB module is the
energyObjectMibObject. The eoPowerTable table of energyObjectMibObject. The eoPowerTable table of
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 the three MIB objects from ENTITY-MIB
(entPhysicalIndex, entPhysicalName and entPhysicalUris) MUST be (entPhysicalIndex, entPhysicalName and entPhysicalUris) MUST be
implemented. implemented.
eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading
the value of this object, it is possible for applications to
know which tables contain the information and are usable without
walking through the table and querying every element which
involves a trial-and-error process.
The power measurement of an Energy Object contains information The power measurement of an Energy Object contains information
describing its power usage (eoPower) and its current power state describing its power usage (eoPower) and its current power state
(eoPowerOperState). In addition to power usage, additional (eoPowerOperState). In addition to power usage, additional
information describing the units of measurement information describing the units of measurement
(eoPowerAccuracy, eoPowerUnitMultiplier), how power usage (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage
measurement was obtained (eoPowerMeasurementCaliber), the measurement was obtained (eoPowerMeasurementCaliber), the
source of power (eoPowerOrigin) and the type of power source of power (eoPowerOrigin) and the type of power
(eoPowerCurrentTtype) are described. (eoPowerCurrentTtype) are described.
An Energy Object may contain an optional eoPowerQuality table An Energy Object may contain an optional eoPowerCharacteristics
that describes the electrical characteristics associated with table that describes the electrical characteristics associated
the current power state and usage. with the current power state and usage.
An Energy Object may contain an optional eoEnergyTable to An Energy Object may contain an optional eoEnergyTable to
describe energy measurement information over time. describe energy measurement information over time.
An Energy Object may also contain optional battery information An Energy Object may also contain optional battery information
associated with this entity. associated with this entity.
10. MIB Definitions 10. MIB Definitions
-- ************************************************************ -- ************************************************************
skipping to change at page 41, line 19 skipping to change at page 34, line 35
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 "201202150000Z" -- 15 March 2012 LAST-UPDATED "201207110000Z" -- 11 July 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 42, line 39 skipping to change at page 36, line 11
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 and
three MIB objects from ENTITY-MIB three MIB objects from ENTITY-MIB
(entPhysicalIndex, entPhysicalName and (entPhysicalIndex, entPhysicalName and
entPhysicalUris)MUST be implemented. " entPhysicalUris)MUST be implemented. "
REVISION REVISION
"201202150000Z" -- 15 March 2012 "201207110000Z" -- 11 July 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 45, line 19 skipping to change at page 38, line 40
giga(9), -- 10^9 giga(9), -- 10^9
tera(12), -- 10^12 tera(12), -- 10^12
peta(15), -- 10^15 peta(15), -- 10^15
exa(18), -- 10^18 exa(18), -- 10^18
zetta(21), -- 10^21 zetta(21), -- 10^21
yotta(24) -- 10^24 yotta(24) -- 10^24
} }
-- Objects -- Objects
eoMeterCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is useful for helping applications determine the
monitoring capabilities supported by the local management
agents. It is possible for applications to know which tables
are usable without going through a trial-and-error process."
::= { energyObjectMibObjects 1 }
eoMeterCapabilitiesEntry OBJECT-TYPE
SYNTAX EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the metering capability of an Energy
Object."
INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 }
EoMeterCapabilitiesEntry ::= SEQUENCE {
eoMeterCapability BITS
}
eoMeterCapability OBJECT-TYPE
SYNTAX BITS {
none(0),
powermetering(1), -- power measurement
energymetering(2), -- energy measurement
powercharacteristics(3) -- Power Characteristics
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the Energy monitoring capabilities supported
by this agent. This object use a BITS syntax and indicate the
MIB groups supported by the probe. By reading the value of this
object, it is possible to determine the MIB tables supported. "
::= { eoMeterCapabilitiesEntry 1 }
eoPowerTable OBJECT-TYPE eoPowerTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerEntry SYNTAX SEQUENCE OF EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Energy Objects." "This table lists Energy Objects."
::= { energyObjectMibObjects 1 } ::= { energyObjectMibObjects 2 }
eoPowerEntry OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX EoPowerEntry SYNTAX EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the power usage of an Energy Object." "An entry describes the power usage of an Energy Object."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { eoPowerTable 1 } ::= { eoPowerTable 1 }
skipping to change at page 46, line 43 skipping to change at page 41, line 16
::= { eoPowerEntry 1 } ::= { eoPowerEntry 1 }
eoPowerNameplate OBJECT-TYPE eoPowerNameplate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watts" UNITS "Watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the rated maximum consumption for "This object indicates the rated maximum consumption for
the fully populated Energy Object. The nameplate power the fully populated Energy Object. The nameplate power
requirements are the maximum power numbers and in almost requirements are the maximum power numbers and, in almost
all cases, are well above the expected operational all cases, are well above the expected operational
consumption. The eoPowerNameplate is widely used for consumption. The eoPowerNameplate is widely used for
power provisioning. This value is specified in either power provisioning. This value is specified in either
units of watts or voltage and current. The units are units of watts or voltage and current. The units are
therefore SI watts or equivalent Volt-Amperes with the therefore SI watts or equivalent Volt-Amperes with the
magnitude (milliwatts, kilowatts, etc.) indicated magnitude (milliwatts, kilowatts, etc.) indicated
separately in eoPowerUnitMultiplier." separately in eoPowerUnitMultiplier."
::= { eoPowerEntry 2 } ::= { eoPowerEntry 2 }
eoPowerUnitMultiplier OBJECT-TYPE eoPowerUnitMultiplier OBJECT-TYPE
skipping to change at page 50, line 38 skipping to change at page 45, line 10
DESCRIPTION DESCRIPTION
"This table enumerates the maximum power usage, in watts, "This table enumerates the maximum power usage, in watts,
for every single supported Power State of each Energy for every single supported Power State of each Energy
Object. Object.
This table has an expansion-dependent relationship on the This table has an expansion-dependent relationship on the
eoPowerTable, containing rows describing each Power State eoPowerTable, containing rows describing each Power State
for the corresponding Energy Object. For every Energy for the corresponding Energy Object. For every Energy
Object in the eoPowerTable, there is a corresponding Object in the eoPowerTable, there is a corresponding
entry in this table." entry in this table."
::= { energyObjectMibObjects 2 } ::= { energyObjectMibObjects 3 }
eoPowerStateEntry OBJECT-TYPE eoPowerStateEntry OBJECT-TYPE
SYNTAX EoPowerStateEntry SYNTAX EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A eoPowerStateEntry extends a corresponding "A eoPowerStateEntry extends a corresponding
eoPowerEntry. This entry displays max usage values at eoPowerEntry. This entry displays max usage values at
every single possible Power State supported by the Energy every single possible Power State supported by the Energy
Object. Object.
skipping to change at page 53, line 13 skipping to change at page 47, line 32
eoEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyParametersEntry SYNTAX SEQUENCE OF EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to configure the parameters for "This table is used to configure the parameters for
Energy measurement collection in the table Energy measurement collection in the table
eoEnergyTable. This table allows the configuration of eoEnergyTable. This table allows the configuration of
different measurement settings on the same Energy different measurement settings on the same Energy
Object." Object."
::= { energyObjectMibObjects 3 } ::= { energyObjectMibObjects 4 }
eoEnergyParametersEntry OBJECT-TYPE eoEnergyParametersEntry OBJECT-TYPE
SYNTAX EoEnergyParametersEntry SYNTAX EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry controls an energy measurement in "An entry controls an energy measurement in
eoEnergyTable." eoEnergyTable."
INDEX { eoEnergyParametersIndex } INDEX { eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
skipping to change at page 56, line 39 skipping to change at page 51, line 14
eoEnergyTable OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyEntry SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Energy Object energy measurements. "This table lists Energy Object energy measurements.
Entries in this table are only created if the Entries in this table are only created if the
corresponding value of object eoPowerMeasurementCaliber corresponding value of object eoPowerMeasurementCaliber
is active(2), i.e., if the power is actually metered." is active(2), i.e., if the power is actually metered."
::= { energyObjectMibObjects 4 } ::= { energyObjectMibObjects 5 }
eoEnergyEntry OBJECT-TYPE eoEnergyEntry OBJECT-TYPE
SYNTAX EoEnergyEntry SYNTAX EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "An entry describing energy measurements."
INDEX { eoEnergyParametersIndex, INDEX { eoEnergyParametersIndex,
eoEnergyCollectionStartTime } eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 } ::= { eoEnergyTable 1 }
skipping to change at page 61, line 5 skipping to change at page 55, line 26
entPhysicalName, and entPhysicalUris [RFC4133] entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." MUST be implemented."
GROUP energyObjectMibEnergyParametersTableGroup GROUP energyObjectMibEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex, have to implement. The entPhysicalIndex,
entPhysicalName, and entPhysicalUris [RFC4133] entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." MUST be implemented."
GROUP energyObjectMibMeterCapabilitiesTableGroup
DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex,
entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented."
::= { 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. The entPhysicalIndex,
skipping to change at page 63, line 12 skipping to change at page 57, line 38
eoEnergyMaxConsumed, eoEnergyMaxConsumed,
eoEnergyMaxProduced, eoEnergyMaxProduced,
eoEnergyDiscontinuityTime eoEnergyDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Table." related to the Energy Table."
::= { energyObjectMibGroups 4 } ::= { energyObjectMibGroups 4 }
energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP
OBJECTS {
eoMeterCapability
}
STATUS current
DESCRIPTION
"This group contains the object indicating the
capability of the Energy Object"
::= { 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 5 } ::= { energyObjectMibGroups 6 }
END END
-- ************************************************************ -- ************************************************************
-- --
-- This MIB module is used to monitor power quality of networked -- This MIB module is used to monitor Power Characteristics of
-- 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-QUALITY-MIB DEFINITIONS ::= BEGIN POWER-CHARACTERISTICS-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
Integer32 Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier 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;
powerQualityMIB MODULE-IDENTITY powerCharacteristicsMIB MODULE-IDENTITY
LAST-UPDATED "201203010000Z" -- 1 March 2012 LAST-UPDATED "201207110000Z" -- 11 July 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 65, line 22 skipping to change at page 60, line 4
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 quality in "This MIB is used to report AC Power Characteristics
devices. The table is a sparse augmentation of the in devices. The table is a sparse augmentation of
eoPowerTable table from the energyObjectMib module. the eoPowerTable table from the energyObjectMib
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 and
three MIB objects from ENTITY-MIB (entPhysicalIndex, three MIB objects from ENTITY-MIB (entPhysicalIndex,
entPhysicalName and entPhysicalUris) MUST be entPhysicalName and entPhysicalUris) MUST be
implemented. " implemented. "
REVISION REVISION
"201203010000Z" -- 1 March 2012 "201207110000Z" -- 11 July 2012
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerQualityMIBConform OBJECT IDENTIFIER powerCharacteristicsMIBConform OBJECT IDENTIFIER
::= { powerQualityMIB 0 } ::= { powerCharacteristicsMIB 0 }
powerQualityMIBObjects OBJECT IDENTIFIER powerCharacteristicsMIBObjects OBJECT IDENTIFIER
::= { powerQualityMIB 1 } ::= { powerCharacteristicsMIB 1 }
-- Objects -- Objects
eoACPwrQualityTable OBJECT-TYPE eoACPwrCharTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrQualityEntry SYNTAX SEQUENCE OF EoACPwrCharEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines power quality measurements for "This table defines Power Characteristics measurements
supported entPhysicalIndex entities. It is a sparse for supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable." extension of the eoPowerTable."
::= { powerQualityMIBObjects 1 } ::= { powerCharacteristicsMIBObjects 1 }
eoACPwrQualityEntry OBJECT-TYPE eoACPwrCharEntry OBJECT-TYPE
SYNTAX EoACPwrQualityEntry SYNTAX EoACPwrCharEntry
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 quality 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 }
::= { eoACPwrQualityTable 1 } ::= { eoACPwrCharTable 1 }
EoACPwrQualityEntry ::= SEQUENCE { EoACPwrCharEntry ::= SEQUENCE {
eoACPwrQualityConfiguration INTEGER, eoACPwrCharConfiguration INTEGER,
eoACPwrQualityAvgVoltage Integer32, eoACPwrCharAvgVoltage Integer32,
eoACPwrQualityAvgCurrent Integer32, eoACPwrCharAvgCurrent Integer32,
eoACPwrQualityFrequency Integer32, eoACPwrCharFrequency Integer32,
eoACPwrQualityPowerUnitMultiplier UnitMultiplier, eoACPwrCharPowerUnitMultiplier UnitMultiplier,
eoACPwrQualityPowerAccuracy Integer32, eoACPwrCharPowerAccuracy Integer32,
eoACPwrQualityTotalActivePower Integer32, eoACPwrCharTotalActivePower Integer32,
eoACPwrQualityTotalReactivePower Integer32, eoACPwrCharTotalReactivePower Integer32,
eoACPwrQualityTotalApparentPower Integer32, eoACPwrCharTotalApparentPower Integer32,
eoACPwrQualityTotalPowerFactor Integer32, eoACPwrCharTotalPowerFactor Integer32,
eoACPwrQualityThdAmpheres Integer32, eoACPwrCharThdAmpheres Integer32,
eoACPwrQualityThdVoltage Integer32 eoACPwrCharThdVoltage Integer32
} }
eoACPwrQualityConfiguration OBJECT-TYPE eoACPwrCharConfiguration 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."
::= { eoACPwrQualityEntry 1 } ::= { eoACPwrCharEntry 1 }
eoACPwrQualityAvgVoltage OBJECT-TYPE eoACPwrCharAvgVoltage 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'"
::= { eoACPwrQualityEntry 2 } ::= { eoACPwrCharEntry 2 }
eoACPwrQualityAvgCurrent OBJECT-TYPE eoACPwrCharAvgCurrent 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'"
::= { eoACPwrQualityEntry 3 } ::= { eoACPwrCharEntry 3 }
eoACPwrQualityFrequency OBJECT-TYPE eoACPwrCharFrequency 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'."
::= { eoACPwrQualityEntry 4 } ::= { eoACPwrCharEntry 4 }
eoACPwrQualityPowerUnitMultiplier OBJECT-TYPE eoACPwrCharPowerUnitMultiplier 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
eoACPwrQualityTotalActivePower, eoACPwrCharTotalActivePower,
eoACPwrQualityTotalReactivePower eoACPwrCharTotalReactivePower
and eoACPwrQualityTotalApparentPower measurements. For and eoACPwrCharTotalApparentPower measurements.
3-phase power systems, this will also include For 3-phase power systems, this will include
eoACPwrQualityPhaseActivePower, eoACPwrCharPhaseActivePower,
eoACPwrQualityPhaseReactivePower and eoACPwrCharPhaseReactivePower and
eoACPwrQualityPhaseApparentPower" eoACPwrCharPhaseApparentPower"
::= { eoACPwrQualityEntry 5 } ::= { eoACPwrCharEntry 5 }
eoACPwrQualityPowerAccuracy OBJECT-TYPE eoACPwrCharPowerAccuracy 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"
::= { eoACPwrQualityEntry 6 } ::= { eoACPwrCharEntry 6 }
eoACPwrQualityTotalActivePower OBJECT-TYPE eoACPwrCharTotalActivePower 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'."
::= { eoACPwrQualityEntry 7 } ::= { eoACPwrCharEntry 7 }
eoACPwrQualityTotalReactivePower OBJECT-TYPE eoACPwrCharTotalReactivePower 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'."
::= { eoACPwrQualityEntry 8 } ::= { eoACPwrCharEntry 8 }
eoACPwrQualityTotalApparentPower OBJECT-TYPE eoACPwrCharTotalApparentPower 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'."
::= { eoACPwrQualityEntry 9 } ::= { eoACPwrCharEntry 9 }
eoACPwrQualityTotalPowerFactor OBJECT-TYPE eoACPwrCharTotalPowerFactor 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'."
::= { eoACPwrQualityEntry 10 } ::= { eoACPwrCharEntry 10 }
eoACPwrQualityThdAmpheres OBJECT-TYPE eoACPwrCharThdAmpheres 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'."
::= { eoACPwrQualityEntry 11 } ::= { eoACPwrCharEntry 11 }
eoACPwrQualityThdVoltage OBJECT-TYPE eoACPwrCharThdVoltage 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'."
::= { eoACPwrQualityEntry 12 } ::= { eoACPwrCharEntry 12 }
eoACPwrQualityPhaseTable OBJECT-TYPE eoACPwrCharPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrQualityPhaseEntry SYNTAX SEQUENCE OF EoACPwrCharPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes 3-phase power quality "This table describes 3-phase Power Characteristics
measurements. It is a sparse extension of the measurements. It is a sparse extension of the
eoACPwrQualityTable." eoACPwrCharTable."
::= { powerQualityMIBObjects 2 } ::= { powerCharacteristicsMIBObjects 2 }
eoACPwrQualityPhaseEntry OBJECT-TYPE eoACPwrCharPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrQualityPhaseEntry SYNTAX EoACPwrCharPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes common 3-phase power quality "An entry describes common 3-phase Power
measurements. Characteristics measurements.
This optional table describes 3-phase power quality This optional table describes 3-phase Power
measurements, with three entries for each supported Characteristics measurements, with three entries for
entPhysicalIndex entity. Entities having single phase each supported entPhysicalIndex entity. Entities
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
eoACPwrQualityTable. eoACPwrCharTable.
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 }
::= { eoACPwrQualityPhaseTable 1 } ::= { eoACPwrCharPhaseTable 1 }
EoACPwrQualityPhaseEntry ::= SEQUENCE { EoACPwrCharPhaseEntry ::= SEQUENCE {
eoPhaseIndex Integer32, eoPhaseIndex Integer32,
eoACPwrQualityPhaseAvgCurrent Integer32, eoACPwrCharPhaseAvgCurrent Integer32,
eoACPwrQualityPhaseActivePower Integer32, eoACPwrCharPhaseActivePower Integer32,
eoACPwrQualityPhaseReactivePower Integer32, eoACPwrCharPhaseReactivePower Integer32,
eoACPwrQualityPhaseApparentPower Integer32, eoACPwrCharPhaseApparentPower Integer32,
eoACPwrQualityPhasePowerFactor Integer32, eoACPwrCharPhasePowerFactor Integer32,
eoACPwrQualityPhaseImpedance Integer32 eoACPwrCharPhaseImpedance 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."
::= { eoACPwrQualityPhaseEntry 1 } ::= { eoACPwrCharPhaseEntry 1 }
eoACPwrQualityPhaseAvgCurrent OBJECT-TYPE eoACPwrCharPhaseAvgCurrent 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'"
::= { eoACPwrQualityPhaseEntry 2 } ::= { eoACPwrCharPhaseEntry 2 }
eoACPwrQualityPhaseActivePower OBJECT-TYPE eoACPwrCharPhaseActivePower 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'"
::= { eoACPwrQualityPhaseEntry 3 } ::= { eoACPwrCharPhaseEntry 3 }
eoACPwrQualityPhaseReactivePower OBJECT-TYPE eoACPwrCharPhaseReactivePower 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'"
::= { eoACPwrQualityPhaseEntry 4 } ::= { eoACPwrCharPhaseEntry 4 }
eoACPwrQualityPhaseApparentPower OBJECT-TYPE eoACPwrCharPhaseApparentPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the voltage and current determines "A measured value of the voltage and current determines
the apparent power. Active plus reactive power equals the apparent power. Active plus reactive power equals
the total apparent powwer. the total apparent 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'."
::= { eoACPwrQualityPhaseEntry 5 } ::= { eoACPwrCharPhaseEntry 5 }
eoACPwrQualityPhasePowerFactor OBJECT-TYPE eoACPwrCharPhasePowerFactor 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."
::= { eoACPwrQualityPhaseEntry 6 } ::= { eoACPwrCharPhaseEntry 6 }
eoACPwrQualityPhaseImpedance OBJECT-TYPE eoACPwrCharPhaseImpedance 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'."
::= { eoACPwrQualityPhaseEntry 7 } ::= { eoACPwrCharPhaseEntry 7 }
eoACPwrQualityDelPhaseTable OBJECT-TYPE eoACPwrCharDelPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrQualityDelPhaseEntry SYNTAX SEQUENCE OF EoACPwrCharDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes DEL configuration phase-to-phase "This table describes DEL configuration phase-to-phase
power quality measurements. This is a sparse extension Power Characteristics measurements. This is a sparse
of the eoACPwrQualityPhaseTable." extension of the eoACPwrCharPhaseTable."
::= { powerQualityMIBObjects 3 } ::= { powerCharacteristicsMIBObjects 3 }
eoACPwrQualityDelPhaseEntry OBJECT-TYPE eoACPwrCharDelPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrQualityDelPhaseEntry SYNTAX EoACPwrCharDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes quality attributes of a phase in a "An entry describes Power Characteristics attributes of
DEL 3-phase power system. Voltage measurements are a phase in a DEL 3-phase power system. Voltage
provided both relative to each other and zero. measurements are provided both relative to each other
and zero.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects. MHAI objects.
For phase-to-phase measurements, the 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}
::= { eoACPwrQualityDelPhaseTable 1} ::= { eoACPwrCharDelPhaseTable 1}
EoACPwrQualityDelPhaseEntry ::= SEQUENCE { EoACPwrCharDelPhaseEntry ::= SEQUENCE {
eoACPwrQualityDelPhaseToNextPhaseVoltage Integer32, eoACPwrCharDelPhaseToNextPhaseVoltage Integer32,
eoACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, eoACPwrCharDelThdPhaseToNextPhaseVoltage Integer32,
eoACPwrQualityDelThdCurrent Integer32 eoACPwrCharDelThdCurrent Integer32
} }
eoACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrCharDelPhaseToNextPhaseVoltage 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'."
::= { eoACPwrQualityDelPhaseEntry 2 } ::= { eoACPwrCharDelPhaseEntry 2 }
eoACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrCharDelThdPhaseToNextPhaseVoltage 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'."
::= { eoACPwrQualityDelPhaseEntry 3 } ::= { eoACPwrCharDelPhaseEntry 3 }
eoACPwrQualityDelThdCurrent OBJECT-TYPE eoACPwrCharDelThdCurrent 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'."
::= { eoACPwrQualityDelPhaseEntry 4 } ::= { eoACPwrCharDelPhaseEntry 4 }
eoACPwrQualityWyePhaseTable OBJECT-TYPE eoACPwrCharWyePhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrQualityWyePhaseEntry SYNTAX SEQUENCE OF EoACPwrCharWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes WYE configuration phase-to-neutral "This table describes WYE configuration phase-to-neutral
power quality measurements. This is a sparse extension Power Characteristics measurements. This is a sparse
of the eoACPwrQualityPhaseTable." extension of the eoACPwrCharPhaseTable."
::= { powerQualityMIBObjects 4 } ::= { powerCharacteristicsMIBObjects 4 }
eoACPwrQualityWyePhaseEntry OBJECT-TYPE eoACPwrCharWyePhaseEntry OBJECT-TYPE
SYNTAX EoACPwrQualityWyePhaseEntry SYNTAX EoACPwrCharWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes measurements of WYE configuration "This table describes measurements of WYE configuration
with phase to neutral power quality attributes. Three with phase to neutral Power Characteristics attributes.
entries are required for each supported entPhysicalIndex Three entries are required for each supported
entry. Voltage measurements are relative to neutral. entPhysicalIndex entry. Voltage measurements are
relative to neutral.
This is a sparse extension of the This is a sparse extension of the eoACPwrCharPhaseTable.
eoACPwrQualityPhaseTable.
Each entry describes quality attributes of one phase of Each entry describes Power Characteristics attributes 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 }
::= { eoACPwrQualityWyePhaseTable 1} ::= { eoACPwrCharWyePhaseTable 1}
EoACPwrQualityWyePhaseEntry ::= SEQUENCE { EoACPwrCharWyePhaseEntry ::= SEQUENCE {
eoACPwrQualityWyePhaseToNeutralVoltage Integer32, eoACPwrCharWyePhaseToNeutralVoltage Integer32,
eoACPwrQualityWyePhaseCurrent Integer32, eoACPwrCharWyePhaseCurrent Integer32,
eoACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 eoACPwrCharWyeThdPhaseToNeutralVoltage Integer32
} }
eoACPwrQualityWyePhaseToNeutralVoltage 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'."
::= { eoACPwrQualityWyePhaseEntry 1 } ::= { eoACPwrCharWyePhaseEntry 1 }
eoACPwrQualityWyePhaseCurrent OBJECT-TYPE eoACPwrCharWyePhaseCurrent 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'."
::= { eoACPwrQualityWyePhaseEntry 2 } ::= { eoACPwrCharWyePhaseEntry 2 }
eoACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrCharWyeThdPhaseToNeutralVoltage 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'."
::= { eoACPwrQualityWyePhaseEntry 3 } ::= { eoACPwrCharWyePhaseEntry 3 }
-- Conformance -- Conformance
powerQualityMIBCompliances OBJECT IDENTIFIER powerCharacteristicsMIBCompliances OBJECT IDENTIFIER
::= { powerQualityMIB 2 } ::= { powerCharacteristicsMIB 2 }
powerQualityMIBGroups OBJECT IDENTIFIER powerCharacteristicsMIBGroups OBJECT IDENTIFIER
::= { powerQualityMIB 3 } ::= { powerCharacteristicsMIB 3 }
powerQualityMIBFullCompliance 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, then
such an implementation can claim full compliance. Such devices such an implementation can claim full compliance. Such devices
can then be both monitored and configured with this MIB. The can then be both monitored and configured with this MIB. The
entPhysicalIndex, entPhysicalName, and entPhysicalUris [RFC4133] entPhysicalIndex, entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented." MUST be implemented."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerACPwrQualityMIBTableGroup powerACPwrCharMIBTableGroup
} }
GROUP powerACPwrQualityOptionalMIBTableGroup GROUP powerACPwrCharOptionalMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have "A compliant implementation does not have
to implement." to implement."
GROUP powerACPwrQualityPhaseMIBTableGroup GROUP powerACPwrCharPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
GROUP powerACPwrQualityDelPhaseMIBTableGroup GROUP powerACPwrCharDelPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
GROUP powerACPwrQualityWyePhaseMIBTableGroup GROUP powerACPwrCharWyePhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
::= { powerQualityMIBCompliances 1 } ::= { powerCharacteristicsMIBCompliances 1 }
-- Units of Conformance -- Units of Conformance
powerACPwrQualityMIBTableGroup OBJECT-GROUP powerACPwrCharMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex is -- Note that object entPhysicalIndex is NOT
NOT -- included since it is not-accessible
-- included since it is not-accessible
eoACPwrQualityAvgVoltage, eoACPwrCharAvgVoltage,
eoACPwrQualityAvgCurrent, eoACPwrCharAvgCurrent,
eoACPwrQualityFrequency, eoACPwrCharFrequency,
eoACPwrQualityPowerUnitMultiplier, eoACPwrCharPowerUnitMultiplier,
eoACPwrQualityPowerAccuracy, eoACPwrCharPowerAccuracy,
eoACPwrQualityTotalActivePower, eoACPwrCharTotalActivePower,
eoACPwrQualityTotalReactivePower, eoACPwrCharTotalReactivePower,
eoACPwrQualityTotalApparentPower, eoACPwrCharTotalApparentPower,
eoACPwrQualityTotalPowerFactor eoACPwrCharTotalPowerFactor
} STATUS } STATUS
current current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the Power
quality objects related to the Energy Object." Characteristics objects related to the Energy Object."
::= { powerQualityMIBGroups 1 } ::= { powerCharacteristicsMIBGroups 1 }
powerACPwrQualityOptionalMIBTableGroup OBJECT-GROUP powerACPwrCharOptionalMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoACPwrQualityConfiguration, eoACPwrCharConfiguration,
eoACPwrQualityThdAmpheres, eoACPwrCharThdAmpheres,
eoACPwrQualityThdVoltage eoACPwrCharThdVoltage
} STATUS current }
STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the Power
quality objects related to the Energy Object." Characteristics objects related to the Energy Object."
::= { powerQualityMIBGroups 2 } ::= { powerCharacteristicsMIBGroups 2 }
powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP powerACPwrCharPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex is -- Note that object entPhysicalIndex is NOT
NOT -- included since it is not-accessible
-- included since it is not-accessible eoACPwrCharPhaseAvgCurrent,
eoACPwrQualityPhaseAvgCurrent, eoACPwrCharPhaseActivePower,
eoACPwrQualityPhaseActivePower, eoACPwrCharPhaseReactivePower,
eoACPwrQualityPhaseReactivePower, eoACPwrCharPhaseApparentPower,
eoACPwrQualityPhaseApparentPower, eoACPwrCharPhasePowerFactor,
eoACPwrQualityPhasePowerFactor, eoACPwrCharPhaseImpedance
eoACPwrQualityPhaseImpedance
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all 3-phase power "This group contains the collection of all 3-phase Power
quality objects related to the Power State." characteristics objects related to the Power State."
::= { powerQualityMIBGroups 3 } ::= { powerCharacteristicsMIBGroups 3 }
powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrCharDelPhaseMIBTableGroup 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
eoACPwrQualityDelPhaseToNextPhaseVoltage , eoACPwrCharDelPhaseToNextPhaseVoltage ,
eoACPwrQualityDelThdPhaseToNextPhaseVoltage, eoACPwrCharDelThdPhaseToNextPhaseVoltage,
eoACPwrQualityDelThdCurrent eoACPwrCharDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all quality "This group contains the collection of all power
attributes of a phase in a DEL 3-phase power system." characteristic attributes of a phase in a DEL 3-phase
::= { powerQualityMIBGroups 4 } power system."
::= { powerCharacteristicsMIBGroups 4 }
powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrCharWyePhaseMIBTableGroup 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
eoACPwrQualityWyePhaseToNeutralVoltage, eoACPwrCharWyePhaseToNeutralVoltage,
eoACPwrQualityWyePhaseCurrent, eoACPwrCharWyePhaseCurrent,
eoACPwrQualityWyeThdPhaseToNeutralVoltage eoACPwrCharWyeThdPhaseToNeutralVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all WYE "This group contains the collection of all WYE
configuration phase-to-neutral power quality configuration phase-to-neutral Power Characteristics
measurements." measurements."
::= { powerQualityMIBGroups 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
thus important to control even GET and/or NOTIFY access to these thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects objects and possibly to even encrypt the values of these objects
skipping to change at page 79, line 44 skipping to change at page 74, line 35
12.1. IANA Considerations for the MIB Modules 12.1. IANA Considerations for the MIB Modules
The MIB modules in this document uses the following IANA- The MIB modules in this document uses the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
energyObjectMib { mib-2 xxx } energyObjectMib { mib-2 xxx }
powerQualityMIB { mib-2 yyy } powerCharacteristicsMIB { mib-2 yyy }
Additions to the MIB modules are subject to Expert Review Additions to the MIB modules are subject to Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested MIB objects for completeness and accuracy of the requested MIB objects for completeness and accuracy of the
description. Requests for MIB objects that duplicate the description. Requests for MIB objects that duplicate the
functionality of existing objects SHOULD be declined. The functionality of existing objects SHOULD be declined. The
smallest available OIDs SHOULD be assigned to the new MIB smallest available OIDs SHOULD be assigned to the new MIB
objects. The specification of new MIB objects SHOULD follow the objects. The specification of new MIB objects SHOULD follow the
structure specified in Section 10. and MUST be published using structure specified in Section 10. and MUST be published using
skipping to change at page 82, line 37 skipping to change at page 77, line 30
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 Double-check all the IEC references in the draft. OPEN ISSUE 1 Consideration of IEEE-ISTO PWG in the IANA list of
IEC 61850-7-4 has been widely referenced in many EMAN drafts.
The other IEC references suggested in the email list are
IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is
important to resolve the correct IEC references soon.
OPEN ISSUE 2 Light weight identification of a device
"The identity provisioning method that has been chosen can be
retrieved by reading the value of powerStateEnergyConsumerOid.
In case of identities provided by the ENERGY-AWARE-MIB module,
this OID points to an exising instance of eoPowerIndex, in
case of the ENTITY-MIB, the object points to a valid instance
of entPhysicalIndex, and in a similar way, it points to a
value of another MIB module if this is used for identifying
entities. If no other MIB module has been chosen for providing
entity identities, then the value of
powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero).
OPEN ISSUE 3 Demand computation method
"Energy not obtained by periodically polling a power
measurement with a eoEnergyParametersSampleRate ; Energy (E)
is measured to the product's certified IEC 62053-21 accuracy
class"
Need to verify with IEC62053-21.
OPEN ISSUE 4 Consideration of IEEE-ISTO PWG in the IANA list of
Power State Set ? Printer Power series could be added once the Power State Set ? Printer Power series could be added once the
IANA procedure is in place. IANA procedure is in place.
OPEN ISSUE 5 check if all the requirements from [EMAN-REQ] are OPEN ISSUE 2 check if all the requirements from [EMAN-REQ] are
covered. covered.
OPEN ISSUE 6 IANA Registered Power State Sets deferred to [EMAN- OPEN ISSUE 3 IANA Registered Power State Sets deferred to [EMAN-
FRAMEWORK] FRAMEWORK]
OPEN ISSUE 7 Device capabilities discovery in terms of Power
Quality measurements another MIB object
OPEN ISSUE 8 Directional Metering of Energy not in requirements
Open Issue 9 How to monitor remote objects, for which there is
no entPhysicalIndex: with a proxyTable or indexed by the UUID?"
15. References 15. References
15.2. Normative References 15.2. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, BCP 14, RFC 2119, March 1997. Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
skipping to change at page 84, line 36 skipping to change at page 78, line 36
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-04 ", work in progress, February 2012. energy-aware-mib-06 ", work in progress, July 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 85, line 15 skipping to change at page 79, line 17
[RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S.
Waldbusser, "Management Information Base (MIB) for the Waldbusser, "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", RFC3418, Simple Network Management Protocol (SNMP)", RFC3418,
December 2002. December 2002.
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity
Sensor Management Information Base", RFC 3433, December Sensor Management Information Base", RFC 3433, December
2002. 2002.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268,November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [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 Managemen", M. Chandramouli, " Requirements for Energy Management",
draft-ietf-eman-requirements-05, November 2011. draft-ietf-eman-requirements-07, July 2012.
[EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J.
Quittek, "Energy Management Framework", draft-ietf- Quittek, "Energy Management Framework", draft-ietf-
eman-framework-03, October 2011. eman-framework-04, March 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-eman-ietf-energy-monitoring-mib-01, MIB ", draft-ietf-eman-energy-monitoring-mib-02, March
October 2011. 2012.
[EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy [EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy
Management (EMAN) Applicability Statement", draft- Management (EMAN) Applicability Statement", draft-
ietf-eman-applicability-statement-00, December 2011. ietf-eman-applicability-statement-01, June 2012.
[EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology", [EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology",
draft-parello-eman-definitions-04, work in progress, draft-parello-eman-definitions-06, work in progress,
December 2011. July 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
 End of changes. 256 change blocks. 
792 lines changed or deleted 546 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/