draft-ietf-eman-energy-monitoring-mib-01.txt   draft-ietf-eman-energy-monitoring-mib-02.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: April 31 2012 Independent Consultant Expires: September 8, 2012 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
October 31, 2011 March 9, 2012
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-01 draft-ietf-eman-energy-monitoring-mib-02
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 February 2012. This Internet-Draft will expire on September 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119]. described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction............................................. 3 1. Introduction............................................. 4
2. The Internet-Standard Management Framework............... 4 2. The Internet-Standard Management Framework............... 5
3. Use Cases................................................ 4 3. Use Cases................................................ 5
4. Terminology.............................................. 5 4. Terminology.............................................. 5
5. Architecture Concepts Applied to the MIB Module.......... 5 Energy Management.........................................6
5.1. Energy Object Information............................. 12 Energy Management System (EnMS)...........................6
5.2. Power State........................................... 12 ISO Energy Management System..............................7
5.2.1. Power State Set................................13 Energy....................................................7
5.2.2. IEEE1621 Power State Set.......................13 Power.....................................................7
5.2.3. DMTF Power State Set...........................14 Demand....................................................8
5.2.4. EMAN Power State Set...........................15 Power Quality.............................................8
5.3. Energy Object Usage Information....................... 18 Electrical Equipment......................................8
5.4. Optional Power Usage Quality.......................... 18 Non-Electrical Equipment (Mechanical Equipment)...........8
5.5. Optional Energy Measurement........................... 19 Energy Object.............................................9
5.6. Fault Management...................................... 23 Electrical Energy Object..................................9
6. Discovery............................................... 23 Non-Electrical Energy Object..............................9
6.1. ENERGY-AWARE-MIB Module Implemented................... 23 Energy Monitoring.........................................9
6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB Energy Control............................................9
Implemented................................................ 24 Energy Management Domain.................................10
6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented.25 Energy Object Identification.............................10
7. Link with the other IETF MIBs........................... 25 Energy Object Context....................................10
7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB..25 Energy Object Relationship...............................10
7.2. Link with the ENTITY-STATE MIB......................26 Aggregation Relationship.................................11
7.3. Link with the POWER-OVER-ETHERNET MIB...............27 Metering Relationship....................................11
7.4. Link with the UPS MIB...............................28 Power Source Relationship................................11
7.5. Link with the LLDP and LLDP-MED MIBs................29 Proxy Relationship.......................................11
8. Implementation Scenario................................. 29 Dependency Relationship..................................12
9. Structure of the MIB.................................... 32 Energy Object Parent.....................................12
10. MIB Definitions........................................ 32 Energy Object Child......................................12
11. Security Considerations................................ 69 Power State..............................................12
12. IANA Considerations.................................... 70 Power State Set..........................................13
12.1. IANA Considerations for the MIB Modules.............. 70 Nameplate Power..........................................13
12.2. IANA Registration of new Power State Set............. 71 5. Architecture Concepts Applied to the MIB Module......... 13
12.2.1. IANA Registration of the IEEE1621 Power State Set..71 5.1. Energy Object Information............................. 20
12.2.2. IANA Registration of the DMTF Power State Set......71 5.2. Power State........................................... 20
12.2.3. IANA Registration of the EMAN Power State Set......72 5.2.1. Power State Set................................21
12. Contributors........................................... 72 5.2.2. IEEE1621 Power State Set.......................22
13. Acknowledgment......................................... 72 5.2.3. DMTF Power State Set...........................22
14. Open Issues............................................ 73 5.2.4. EMAN Power State Set...........................23
15. References............................................. 74 5.3. Energy Object Usage Information....................... 26
15.2. Normative References...............................74 5.4. Optional Power Usage Quality.......................... 27
15.3. Informative References.............................74 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
skipping to change at page 4, line 19 skipping to change at page 4, line 42
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 10 skipping to change at page 5, line 38
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
The definitions of basic terms such as Energy Object, Energy EDITOR'S NOTE:
Object Parent, Energy Object Child, Energy Object Meter - All terms are copied over from the version 4 of the
Domain, Power State can be found in the terminology draft [EMAN-TERMINOLOGY] draft. The only difference in
draft-parello-eman-definitions. 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.
Power State Set Energy Management
A Power State Set is defined as a sequence of incremental Energy Management is a set of functions for measuring,
energy saving modes of a device. The elements of this set can modeling, planning, and optimizing networks to ensure
be viewed as an interface for the underlying device- that the network elements and attached devices use
implemented power settings of a device. Examples of Power energy efficiently and is appropriate for the nature
State Sets include DTMF [DMTF], IEEE1621 [IEEE1621], ACPI of the application and the cost constraints of the
[ACPI] and EMAN. 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.
EDITOR NOTE: Use the latest definition from draft-parello- Energy Management System (EnMS)
eman-definitions
Power State 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).
A Power State is defined as a specific power setting for an ISO Energy Management System
Energy Object (e.g., shut, hibernate, sleep, high). Within the
context of a Power State Set, the Power State of a device is
one of the power saving modes in that Power State Set.
EDITOR NOTE: Use the latest definition from draft-parello- Energy Management System as defined by [ISO50001]
eman-definitions
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
association between one or more Energy Objects
NOTES
1. Relationships can be named and could include
Aggregation, Metering, Power Source, Proxy and
Dependency.
Aggregation Relationship
An Energy Object may aggregate the Energy Management
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
An Energy Object may measure the Power or Energy of
another Energy Object(s) and is referred to as a
Metering Relationship.
Example: a PoE port on a switch measures the Power it
provides to the connected Energy Object.
Power Source Relationship
An Energy Object may be the source of or distributor
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.
Proxy Relationship
An Energy Object that provides Energy Management
capabilities on behalf of another Energy Object is
referred to a Proxy Relationship.
Example: a protocol gateways device for Building
Management Systems (BMS) with subtended devices.
Dependency Relationship
An Energy Object may be a component of or rely
completely upon another Energy Object to operate and
is referred to as a Dependency Relationship.
Example: A Switch chassis with multiple line cards.
Energy Object Parent
An Energy Object Parent is an Energy Object that
participates in an Energy Object Relationships and is
considered as providing the capabilities in the
relationship.
Energy Object Child
An Energy Object Child is an Energy Object that
participates in an Energy Object Relationships and is
considered as receiving the capabilities in the
relationship.
Power State
A Power State is a condition or mode of a device that
broadly characterizes its capabilities, power
consumption, and responsiveness to input.
Reference: Adapted from [IEEE1621]
NOTES:
1. A Power State can be seen as a power setting of an
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
Energy Control
Power State Set
A collection of Power States that comprise one named
or logical grouping of control is a Power State Set.
Example: The states {on, off, and sleep} as defined in
[IEEE1621], or the 16 power states as defined by the
[DMTF] can be considered two different Power State
Sets.
Nameplate Power
The Nameplate Power is the maximal (nominal) Power
that a device can support.
NOTES:
1. This is typically determined via load testing and
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 powerQualityMIB is
focused on Power Quality measurements. focused on Power Quality 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 eoPowerIndex. The second first table eoPowerTable is indexed by entPhysicalIndex. The
table eoPowerStateTable indexed by eoPowerIndex,and second table eoPowerStateTable indexed by entPhysicalIndex and
eoPowerStateIndex. . The eoEnergyParametersTable and eoPowerStateIndex. The eoEnergyParametersTable is indexed
eoEnergyTable are indexed by eoPowerIndex. by eoEnergyParametersIndex. The eoEnergyTable is indexed by
eoEnergyParametersIndex and eoEnergyCollectionStartTime.
eoPowerTable(1) eoPowerTable(1)
| |
+---eoPowerEntry(1) [eoPowerIndex] +---eoPowerEntry(1) [entPhysicalIndex]
| | | |
| +-- --- Integer32 eoPowerIndex(1) | +---r-n Integer32 eoPower(1)
| +---r-n Integer32 eoPower(2) | +-- r-n Integer32 eoPowerNamePlate(2)
| +-- r-n Integer32 eoPowerNamePlate(3) | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3)
| +-- r-n UnitMultiplier eoPowerUnitMultiplier(4) | +-- r-n Integer32 eoPowerAccuracy(4)
| +-- r-n Integer32 eoPowerAccuracy(5) | +-- r-n INTEGER eoMeasurementCaliber(5)
| +-- r-n INTEGER eoMeasurementCaliber(6) | +-- r-n INTEGER eoPowerCurrentType(6)
| +-- r-n INTEGER eoPowerCurrentType(7) | +-- r-n INTEGER eoPowerOrigin(7)
| +-- r-n INTEGER eoPowerOrigin(8) | +-- rwn Integer32 eoPowerAdminState(8)
| +-- rwn Integer32 eoPowerAdminState(9) | +-- r-n Integer32 eoPowerOperState(9)
| +-- r-n Integer32 eoPowerOperState(10) | +-- r-n OwnerString eoPowerStateEnterReason(10)
| +-- r-n OwnerString eoPowerStateEnterReason(11)
| | | |
| | | |
+---eoPowerStateTable(2) +---eoPowerStateTable(2)
| +--eoPowerStateEntry(1) | +--eoPowerStateEntry(1)
| | [eoPowerIndex, | | [entPhysicalIndex,
| | eoPowerStateIndex] | | eoPowerStateIndex]
| | | |
| +-- --- 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 Counter64 eoPowerStateEnterCount(5) | +-- r-n Counter32 eoPowerStateEnterCount(5)
| |
+eoEnergyParametersTable(1) +eoEnergyParametersTable(1)
+---eoEnergyParametersEntry(1) [eoPowerIndex] +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
| |
| +-- --n PhysicalIndex eoEnergyObjectIndex (1)
| + r-n Integer32 eoEnergyParametersIndex (2)
| +-- r-n TimeInterval | +-- r-n TimeInterval
| eoEnergyParametersIntervalLength (1) | eoEnergyParametersIntervalLength (3)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersIntervalNumber (2) | eoEnergyParametersIntervalNumber (4)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersIntervalMode (3) | eoEnergyParametersIntervalMode (5)
| +-- r-n TimeInterval | +-- r-n TimeInterval
| eoEnergyParametersIntervalWindow (4) | eoEnergyParametersIntervalWindow (6)
| +-- r-n Integer32 | +-- r-n Integer32
| eoEnergyParametersSampleRate (5) | eoEnergyParametersSampleRate (7)
| +-- r-n RowStatus eoEnergyParametersStatus (6) | +-- r-n RowStatus eoEnergyParametersStatus (8)
| |
+eoEnergyTable(1) +eoEnergyTable (1)
+---eoEnergyEntry(1) [eoPowerIndex] +---eoEnergyEntry(1) [eoEnergyParametersIndex,
eoEnergyCollectionStartTime]
| |
| +-- r-n TimeInterval eoEnergyIntervalStartTime (1) | +-- r-n TimeTicks eoEnergyCollectionStartTime (1)
| +-- r-n Integer32 eoEnergyIntervalEnergyConsumed (2) | +-- r-n Integer32 eoEnergyConsumed (2)
| +-- r-n Integer32 eoEnergyIntervalEnergyProduced (3) | +-- r-n Integer32 eoEnergyyProduced (3)
| +-- r-n Integer32 eoEnergyIntervalEnergyNet (4) | +-- r-n Integer32 eoEnergyNet (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoEnergyIntervalEnergyUnitMultiplier (5) | eoEnergyUnitMultiplier (5)
| +-- r-n Integer32 eoEnergyIntervalEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyIntervalMaxConsumed (7) | +-- r-n Integer32 eoEnergyMaxConsumed (7)
| +-- r-n Integer32 eoEnergyIntervalMaxProduced (8) | +-- r-n Integer32 eoEnergyMaxProduced (8)
| +-- r-n TimeTicks | +-- r-n TimeTicks
| eoEnergyIntervalDiscontinuityTime(9) | eoEnergyDiscontinuityTime(9)
| +-- r-n RowStatus eoEnergyParametersStatus (10) | +-- r-n RowStatus eoEnergyParametersStatus (10)
The powerQualityMIB consists of four tables. eoACPwrQualityTable The powerQualityMIB consists of four tables. eoACPwrQualityTable
is indexed by eoPowerIndex. eoACPwrQualityPhaseTable is indexed is indexed by entPhysicalIndex. eoACPwrQualityPhaseTable is
by eoPowerIndex and eoPhaseIndex. eoACPwrQualityWyePhaseTable indexed by entPhysicalIndex and eoPhaseIndex.
and eoACPwrQualityDelPhaseTable are indexed by eoPowerIndex and eoACPwrQualityWyePhaseTable and eoACPwrQualityDelPhaseTable are
eoPhaseIndex. indexed by entPhysicalIndex and eoPhaseIndex.
eoPowerTable(1) eoPowerQualityTable(1)
| |
+---eoACPwrQualityEntry (1) [eoPowerIndex] +---eoACPwrQualityEntry (1) [entPhysicalIndex]
| | | |
| | | |
| +----- INTEGER eoACPwrQualityConfiguration (1) | +---r-n INTEGER eoACPwrQualityConfiguration (1)
| +-- r-n Interger32 eoACPwrQualityAvgVoltage (2) | +-- r-n Interger32 eoACPwrQualityAvgVoltage (2)
| +-- r-n Integer32 eoACPwrQualityAvgCurrent (3) | +-- r-n Integer32 eoACPwrQualityAvgCurrent (3)
| +-- r-n Integer32 eoACPwrQualityFrequency (4) | +-- r-n Integer32 eoACPwrQualityFrequency (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoACPwrQualityPowerUnitMultiplier (5) | eoACPwrQualityPowerUnitMultiplier (5)
| +-- r-n Integer32 eoACPwrQualityPowerAccuracy (6) | +-- r-n Integer32 eoACPwrQualityPowerAccuracy (6)
| +-- r-n Interger32 eoACPwrQualityTotalActivePower (7) | +-- r-n Interger32 eoACPwrQualityTotalActivePower (7)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrQualityTotalReactivePower (8) | eoACPwrQualityTotalReactivePower (8)
| +-- r-n Integer32 eoACPwrQualityTotalApparentPower (9) | +-- r-n Integer32 eoACPwrQualityTotalApparentPower (9)
| +-- r-n Integer32 eoACPwrQualityTotalPowerFactor(10) | +-- r-n Integer32 eoACPwrQualityTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrQualityThdAmpheres (11) | +-- r-n Integer32 eoACPwrQualityThdAmpheres (11)
| |
+eoACPwrQualityPhaseTable (1) +eoACPwrQualityPhaseTable (1)
+---EoACPwrQualityPhaseEntry(1)[eoPowerIndex, +---EoACPwrQualityPhaseEntry(1)[entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| | | |
| +-- r-n Integer32 eoPhaseIndex (1) | +-- r-n Integer32 eoPhaseIndex (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseAvgCurrent (2) | | eoACPwrQualityPhaseAvgCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseActivePower (3) | | eoACPwrQualityPhaseActivePower (3)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseReactivePower (4) | | eoACPwrQualityPhaseReactivePower (4)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseApparentPower (5) | | eoACPwrQualityPhaseApparentPower (5)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhasePowerFactor (6) | | eoACPwrQualityPhasePowerFactor (6)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityPhaseImpedance (7) | | eoACPwrQualityPhaseImpedance (7)
| | | |
+eoACPwrQualityDelPhaseTable (1) +eoACPwrQualityDelPhaseTable (1)
+-- eoACPwrQualityDelPhaseEntry(1) +-- eoACPwrQualityDelPhaseEntry(1)
| | [eoPowerIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityDelPhaseToNextPhaseVoltage (1) | | eoACPwrQualityDelPhaseToNextPhaseVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityDelThdPhaseToNextPhaseVoltage (2) | | eoACPwrQualityDelThdPhaseToNextPhaseVoltage (2)
| +-- r-n Integer32 eoACPwrQualityDelThdCurrent (3) | +-- r-n Integer32 eoACPwrQualityDelThdCurrent (3)
| | | |
+eoACPwrQualityWyePhaseTable (1) +eoACPwrQualityWyePhaseTable (1)
+-- eoACPwrQualityWyePhaseEntry (1) +-- eoACPwrQualityWyePhaseEntry (1)
| | [eoPowerIndex, | | [entPhysicalIndex,
| | eoPhaseIndex] | | eoPhaseIndex]
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyePhaseToNeutralVoltage (1) | | eoACPwrQualityWyePhaseToNeutralVoltage (1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyePhaseCurrent (2) | | eoACPwrQualityWyePhaseCurrent (2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrQualityWyeThdPhaseToNeutralVoltage (3) | | eoACPwrQualityWyeThdPhaseToNeutralVoltage (3)
| . | .
A UML representation of the MIB objects in the two MIB modules A UML representation of the MIB objects in the two MIB modules
are energyObjectMib and powerQualityMIB are presented. are energyObjectMib and powerQualityMIB are presented.
+--------------------------+ +--------------------------+
| Energy Object ID | | Energy Object ID |
| ----------------------- |
| | | |
| Energy-aware-MIB (*) | | entPhysIndex (*) |
| | +---------------------------+ | entPhysicalName (*) |
| | | | | entPhysicalUris (*) | +---------------------------+
| eoPowerIndex | |_ EnergyObject Attributes | | (EO UUID) | | |
| | | Energy Object Attributes |
| | | ------------------------- |
| | | | | | | |
+--------------------------+ | eoPowerNamePlate | +--------------------------+ | eoPowerNamePlate |
| | | eoPowerMeasurementCaliber | | | | eoPowerMeasurementCaliber |
| | | eoPowerOrigin | | | | eoPowerOrigin |
| | | eoPowerCurrentType | | | | eoPowerCurrentType |
| | +---------------------------+ | | +---------------------------+
| | | | | |
| | | | | |
v | v v | v
+-----------------------------------------+ +-----------------------------------------+
| EnergyObjec Measurement | | Energy Object Measurement |
| | |--------------------------------------- |
| eoPower | | eoPower |
| eoPowerUnitMultiplier | | eoPowerUnitMultiplier |
| eoPowerAccuracy | | eoPowerAccuracy |
+-----------------------------------------+ +-----------------------------------------+
^ | ^ ^ | ^
| | | | | |
+-------------------------+ | | +-------------------------+ | |
| EnergyObject State | | +------------------------+ | Energy Object State | | +------------------------+
| | | | EnergyObject State | | ----------------------- | | | Energy Object State |
| eoPowerAdminState | | | Statistics | | eoPowerAdminState | | | Statistics |
| eoPowerOperState | | | | | eoPowerOperState | | |----------------------- |
| eoPowerStateEnterReason | | | eoPowerStateMaxPower | | eoPowerStateEnterReason | | | eoPowerStateMaxPower |
+-------------------------+ | | eoPowerStateTotalTime | +-------------------------+ | | eoPowerStateTotalTime |
| | eoPowerStateEnterCount | | | eoPowerStateEnterCount |
| +------------------------+ | +------------------------+
| |
| |
| |
| |
Figure 1:UML diagram for powerMonitor MIB Figure 1:UML diagram for powerMonitor MIB
(*) Link with the ENERGY-AWARE-MIB (*) Link with the ENTITY-MIB
|
|
V
+----------------------------------------+
| Energy ParametersTable |
| -------------------------------------- |
| |
| eoEnergyObjectIndex |
| eoEnergyParametersIndex |
| eoEnergyParametersIntervalLength |
| eoEnergyParametersIntervalNumber |
| eoEnergyParametersIntervalMode |
| eoEnergyParametersIntervalWindow |
| eoEnergyParametersSampleRate |
| eoEnergyParametersStatus |
+----------------------------------------+
| |
| |
| |
V V
+----------------------------------------+ +----------------------------------------+
| Energy Table | | Energy Table |
| | | ---------------------------------- |
| eoEnergyIntervalStartTime | | eoEnergyCollectionStartTime |
| eoEnergyIntervalEnergyConsumed | | eoEnergyConsumed |
| eoEnergyIntervalEnergyProduced | | eoEnergyProduced |
| eoEnergyIntervalEnergyNet | | eoEnergyNet |
| eoEnergyIntervalEnergyUnitMultiplier | | eoEnergyUnitMultiplier |
| eoEnergyIntervalEnergyAccuracy | | eoEnergyAccuracy |
| eoEnergyIntervalMaxConsumed | | eoMaxConsumed |
| eoEnergyIntervalMaxProduced | | eoMaxProduced |
| eoEnergyIntervalDiscontinuityTime | | eoDiscontinuityTime |
+----------------------------------------+ +----------------------------------------+
+--------------------------+ +--------------------------+
| EnergyObject ID | | EnergyObject ID |
| ----------------------- |
| | | |
| Energy-aware-MIB (*) |
| | | |
| eoPowerIndex | | entPhysicalIndex (*) |
| | | |
+--------------------------+ +--------------------------+
| |
v v
+-------------------------------------+ +-------------------------------------+
| Power Quality | | Power Quality |
| | | ----------------------------------- |
| eoACPwrQualityConfiguration | | eoACPwrQualityConfiguration |
| eoACPwrQualityAvgVoltage | | eoACPwrQualityAvgVoltage |
| eoACPwrQualityAvgCurrent | eoACPwrQualityAvgCurrent |
| eoACPwrQualityFrequency | | eoACPwrQualityFrequency |
| eoACPwrQualityPowerUnitMultiplier | | eoACPwrQualityPowerUnitMultiplier |
| eoACPwrQualityPowerAccuracy | | eoACPwrQualityPowerAccuracy |
| eoACPwrQualityTotalActivePower | | eoACPwrQualityTotalActivePower |
| eoACPwrQualityTotalReactivePower | | eoACPwrQualityTotalReactivePower |
| eoACPwrQualityTotalApparentPower | | eoACPwrQualityTotalApparentPower |
| eoACPwrQualityTotalPowerFactor | | eoACPwrQualityTotalPowerFactor |
| eoACPwrQualityThdAmpheres | | eoACPwrQualityThdAmpheres |
+-------------------------------------+ ^ +-------------------------------------+ ^
^ ^ | ^ ^ |
| | ------- | | -------
| ---- | | ---- |
| | | | | |
| | | | | |
+-------------------------------------+ | | +-------------------------------------+ | |
| Power Phase Quality | | | | Power Phase Quality | | |
| | | | | ---------------------------------- | | |
| eoPhaseIndex | | | | eoPhaseIndex | | |
| eoACPwrQualityPhaseAvgCurrent | | | | eoACPwrQualityPhaseAvgCurrent | | |
| eoACPwrQualityAvgCurrent | | | | eoACPwrQualityAvgCurrent | | |
| eoACPwrQualityFrequency | | | | eoACPwrQualityFrequency | | |
| eoACPwrQualityPowerUnitMultiplier | | | | eoACPwrQualityPowerUnitMultiplier | | |
| eoACPwrQualityPowerAccuracy | | | | eoACPwrQualityPowerAccuracy | | |
| eoACPwrQualityPhaseActivePower | | | | eoACPwrQualityPhaseActivePower | | |
| eoACPwrQualityPhaseReactivePower | | | | eoACPwrQualityPhaseReactivePower | | |
| eoACPwrQualityPhaselApparentPower | | | | eoACPwrQualityPhaselApparentPower | | |
| eoACPwrQualityPhaseImpedance | | | | eoACPwrQualityPhaseImpedance | | |
skipping to change at page 12, line 5 skipping to change at page 20, line 17
+---------------------------------------------+ +---------------------------------------------+
| Power Quality WYE Configuration | | Power Quality WYE Configuration |
| | | |
| eoACPwrQualityWyePhaseToNeutralVoltage | | eoACPwrQualityWyePhaseToNeutralVoltage |
| eoACPwrQualityWyePhaseCurrent | | eoACPwrQualityWyePhaseCurrent |
| eoACPwrQualityWyeThdPhaseToNeutralVoltage | | eoACPwrQualityWyeThdPhaseToNeutralVoltage |
+---------------------------------------------+ +---------------------------------------------+
Figure 2: UML diagram for the powerQualityMIB Figure 2: UML diagram for the powerQualityMIB
(*) 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 eoIndex. The ENERGY-AWARE-MIB module returns the index entPhysicalUris and entPhysicalIndex. The ENERGY-AWARE-MIB
relationship (parent/child) between Energy Objects . module returns the relationship (parent/child) between Energy
Objects.
EDITOR'S NOTE: this last sentence will have to be updated with EDITOR'S NOTE: this last sentence will have to be updated with
terms such as Aggregator, Proxy, etc... when the [EMAN- terms such as Aggregator, Proxy, etc... when the [EMAN-
FRAMEWORK] will stabilize. FRAMEWORK] will stabilize.
5.2. Power State 5.2. Power State
Refer to the "Power States" section in [EMAN-FRAMEWORK] for Refer to the "Power States" section in [EMAN-FRAMEWORK] for
background information. background information.
skipping to change at page 13, line 29 skipping to change at page 21, line 45
There are several standards and implementations of Power State There are several standards and implementations of Power State
Sets. A Energy Object can support one or multiple Power State Sets. A Energy Object can support one or multiple Power State
Set implementation(s) concurrently. Set implementation(s) concurrently.
There are currently three Power State Sets advocated: There are currently three Power State Sets advocated:
unknown(0) unknown(0)
IEEE1621(256) - [IEEE1621] IEEE1621(256) - [IEEE1621]
DMTF(512) - [DMTF] DMTF(512) - [DMTF]
EMAN(1024) - [EMAN-MONITORING-MIB] EMAN(1024) - [EMAN-MONITORING-MIB]
The respective specific states related to each Power State Set The respective specific states related to each Power State Set
are specified in the following sections. The guidelines for are specified in the following sections. The guidelines for
addition of new Power State Sets have been specified in the IANA addition of new Power State Sets have been specified in the IANA
Considerations Section. Considerations Section.
5.2.2. IEEE1621 Power State Set 5.2.2. IEEE1621 Power State Set
The IEEE1621 Power State Set [IEEE1621] consists of 3 The IEEE1621 Power State Set [IEEE1621] consists of 3
rudimentary states : on, off or sleep. rudimentary states : on, off or sleep.
skipping to change at page 18, line 25 skipping to change at page 26, line 41
[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,
eoEnergyIntervalEnergyUnitMultiplier, and eoEnergyUnitMultiplier, and eoACPwrQualityPowerUnitMultiplier.
eoACPwrQualityPowerUnitMultiplier.
In addition to knowing the usage and magnitude, it is useful to In addition to knowing the usage and magnitude, it is useful to
know how a 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
skipping to change at page 19, line 12 skipping to change at page 27, line 26
Refer to the "Optional Power Usage Quality" section in [EMAN- Refer to the "Optional Power Usage Quality" section in [EMAN-
FRAMEWORK] for background information. FRAMEWORK] for background information.
The optional powerQualityMIB MIB module can be implemented to The optional powerQualityMIB MIB module can be implemented to
further describe power usage quality measurement. The further describe power usage quality measurement. The
powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 powerQualityMIB MIB module adheres closely to the IEC 61850 7-2
standard to describe AC measurements. standard to describe AC measurements.
The powerQualityMIB MIB module contains a primary table, the The powerQualityMIB MIB module contains a primary table, the
eoACPwrQualityTable table, that defines power quality eoACPwrQualityTable table, that defines power quality
measurements for supported eoPowerIndex entities, as a sparse measurements for supported entPhysicalIndex entities, as a
extension of the eoPowerTable (with eoPowerIndex as primary sparse extension of the eoPowerTable (with entPhysicalIndex as
index). This eoACPwrQualityTable table contains such primary index). This eoACPwrQualityTable table contains such
information as the configuration (single phase, DEL 3 phases, information as the configuration (single phase, DEL 3 phases,
WYE 3 phases), voltage, frequency, power accuracy, total WYE 3 phases), voltage, frequency, power accuracy, total
active/reactive power/apparent power, amperage, and voltage. active/reactive power/apparent power, amperage, and voltage.
In case of 3-phase power, the eoACPwrQualityPhaseTable In case of 3-phase power, the eoACPwrQualityPhaseTable
additional table is populated with power quality measurements additional table is populated with power quality measurements
per phase (so double indexed by the eoPowerIndex and per 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 eoACPwrQualityDelPhaseTable table describes the phase-to-phase
power quality measurements, i.e., voltage and current. power quality measurements, i.e., voltage and current.
In case of 3-phase power with a Wye configuration, the In case of 3-phase power with a Wye configuration, the
eoACPwrQualityWyePhaseTable table describes the phase-to-neutral eoACPwrQualityWyePhaseTable table describes the phase-to-neutral
skipping to change at page 19, line 45 skipping to change at page 28, line 16
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.
Two tables are introduced to characterize energy measurement of Two tables are introduced to characterize energy measurement of
an Energy Object: eoEnergyTable and eoEnergyParametersTable. an Energy Object: eoEnergyTable and eoEnergyParametersTable.
Both energy and demand information can be represented via the Both energy and demand information can be represented via the
eoEnergyTable. Energy information will be an accumulation with eoEnergyTable. Energy information will be an accumulation with
no interval. Demand information can be represented as an no interval. Demand information can be represented.
average accumulation per interval of time.
The eoEnergyParametersTable consists of the parameters defining The eoEnergyParametersTable consists of the parameters defining
the duration of measurement intervals in seconds, eoEnergyParametersIndex, an index of that specifies the setting
for collection of energy measurements for an Energy Object,
eoEnergyObjectIndex, linked to the entPhysicalIndex of the
Energy Object, the duration of measurement intervals in seconds,
(eoEnergyParametersIntervalLength), the number of successive (eoEnergyParametersIntervalLength), the number of successive
intervals to be stored in the eoEnergyTable, intervals to be stored in the eoEnergyTable,
(eoEnergyParametersIntervalNumber), the type of measurement (eoEnergyParametersIntervalNumber), the type of measurement
technique (eoEnergyParametersIntervalMode), and a sample rate technique (eoEnergyParametersIntervalMode), and a sample rate
used to calculate the average (eoEnergyParametersSampleRate). used to calculate the average (eoEnergyParametersSampleRate).
Judicious choice of the sampling rate will ensure accurate Judicious choice of the sampling rate will ensure accurate
measurement of energy while not imposing an excessive polling measurement of energy while not imposing an excessive polling
burden. burden.
There are three eoEnergyParametersIntervalMode types used for There are three eoEnergyParametersIntervalMode types used for
energy measurement collection: period, sliding, and total. The energy measurement collection: period, sliding, and total. The
choices of the the three different modes of collection are based choices of the the three different modes of collection are based
on IEC standard 61850-7-4. Note that multiple on IEC standard 61850-7-4. Note that multiple
eoEnergyParametersIntervalMode types MAY be configured eoEnergyParametersIntervalMode types MAY be configured
simultaneously. simultaneously. It is important to note that for a given Energy
Object, multiple modes (periodic, total, sliding window) of
energy measurement collection can be configured with the use of
eoEnergyParametersIndex. However, simultaneous measurement in
multiple modes for a given Energy Object depends on the Energy
Object capability.
These three eoEnergyParametersIntervalMode types are illustrated These three eoEnergyParametersIntervalMode types are illustrated
by the following three figures, for which: by the following three figures, for which:
- The horizontal axis represents the current time, with the - The horizontal axis represents the current time, with the
symbol <--- L ---> expressing the symbol <--- L ---> expressing the
eoEnergyParametersIntervalLength, and the eoEnergyParametersIntervalLength, and the
eoEnergyIntervalStartTime is represented by S1, S2, S3, S4, ..., eoEnergyCollectionStartTime is represented by S1, S2, S3, S4,
Sx where x is the value of eoEnergyParametersIntervalNumber. ..., Sx where x is the value of
eoEnergyParametersIntervalNumber.
- The vertical axis represents the time interval of sampling and - The vertical axis represents the time interval of sampling and
the value of eoEnergyIntervalEnergyUsed can be obtained at the the value of eoEnergyConsumed can be obtained at the end of the
end of the sampling period. The symbol =========== denotes the sampling period. The symbol =========== denotes the duration of
duration of the sampling period. the sampling period.
| | | =========== | | | | =========== |
|============ | | | |============ | | |
| | | | | | | |
| |============ | | | |============ | |
| | | | | | | |
| <--- L ---> | <--- L ---> | <--- L ---> | | <--- L ---> | <--- L ---> | <--- L ---> |
| | | | | | | |
S1 S2 S3 S4 S1 S2 S3 S4
Figure 4 : Period eoEnergyParametersIntervalMode Figure 4 : Period eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'period' specifies non- A eoEnergyParametersIntervalMode type of 'period' specifies non-
overlapping periodic measurements. Therefore, the next overlapping periodic measurements. Therefore, the next
eoEnergyIntervalStartTime is equal to the previous eoEnergyCollectionStartTime is equal to the previous
eoEnergyIntervalStartTime plus eoEnergyParametersIntervalLength. eoEnergyCollectionStartTime plus
S2=S1+L; S3=S2+L, ... eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ...
|============ | |============ |
| | | |
| <--- L ---> | | <--- L ---> |
| | | |
| |============ | | |============ |
| | | | | |
| | <--- L ---> | | | <--- L ---> |
| | | | | |
| | |============ | | | |============ |
skipping to change at page 21, line 47 skipping to change at page 30, line 25
| | | |
|========================= | |========================= |
| | | |
| | | |
| | | |
| <--- Total length ---> | | <--- Total length ---> |
| | | |
S1 S1
Figure 4 : Total eoEnergyParametersIntervalMode Figure 6 : Total eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'total' specifies a A eoEnergyParametersIntervalMode type of 'total' specifies a
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy The eoEnergyParametersStatus is used to start and stop energy
usage logging. The status of this variable is "active" when 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
eoEnergyIntervalEnergyUsed , the units of the measured energy eoEnergyConsumed, eoEnergyProduced and eoEnergyNet , the units
eoEnergyIntervalEnergyUnitMultiplier, and the maximum observed of the measured energy eoEnergyUnitMultiplier, and the maximum
energy within a window - eoEnergyIntervalMax. observed energy within a window, eoEnergyMaxConsumed,
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 eoEnergyIntervalDiscontinuityTime is provided for the object eoEnergyDiscontinuityTime is provided for indicating
indicating the time of the last interruption of total energy the time of the last interruption of total energy measurement.
measurement. eoEnergyIntervalDiscontinuityTime shall indicate eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418]
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 eoPowerIndex, which The indices for the eoEnergyTable are eoEnergyParametersIndex
identifies the Energy Object, and eoEnergyIntervalStartTime, which identifies the index for the setting of energy measurement
which denotes the start time of the energy measurement interval collection Energy Object, and eoEnergyCollectionStartTime, which
based on sysUpTime [RFC3418]. The value of denotes the start time of the energy measurement interval based
eoEnergyIntervalEnergyUsed is the measured energy consumption on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
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 eoEnergyIntervalEnergyUsed. The units are derived calculate the eoEnergyConsumed. The units are derived from
from eoEnergyIntervalPowerUnitMultiplier. For example, eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
eoEnergyIntervalPowerUsed can be "100" with "100" with eoEnergyUnitMultiplier equal to 0, the measured
eoEnergyIntervalPowerUnits equal to 0, the measured energy energy consumption of the Energy Object is 100 watt-hours. The
consumption of the Energy Object is 100 watt-hours. The eoEnergyMaxConsumed is the maximum energy observed and that can
eoEnergyIntervalMax 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. If
the default value of "10" is kept, then the eoEnergyTable 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
skipping to change at page 23, line 44 skipping to change at page 32, line 20
to each state" etc. Some of these requirements are fulfilled to each state" etc. Some of these requirements are fulfilled
explicitly by MIB objects such as eoPowerOperState, explicitly by MIB objects such as eoPowerOperState,
eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the
other requirements are met via the SNMP NOTIFICATION mechanism. other requirements are met via the SNMP NOTIFICATION mechanism.
eoPowerStateChange SNMP notification which is generated when the eoPowerStateChange SNMP notification which is generated when the
value(s) of ,eoPowerStateIndex, eoPowerOperState, value(s) of ,eoPowerStateIndex, eoPowerOperState,
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
6.1. ENERGY-AWARE-MIB Module Implemented It is foreseen that most Energy Objects will require the
implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a
prerequisite for this MIB module. In such a case, eoPowerTable
of the EMAN-MON-MIB is a sparse extension of the eoTable of
ENERGY-AWARE-MIB. Every Energy Object MUST implement
entPhysicalIndex, entPhysicalUris and entPhysicalName
from the ENTITY-MIB [RFC4133]. As the index for the primary
Energy 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 eoIndex. 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
eoIndex value (EMAN-AWARE-MIB) MUST be assigned to the entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The
eoPowerIndex. The eoPowerIndex characterizes the Energy Object entPhysicalIndex characterizes the Energy Object in the
in the energyObjectMib and powerQualityMIB MIB modules (this energyObjectMib and powerQualityMIB MIB modules (this document).
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 (eoPowerIndex), 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, per Power State Set, and per Power Usage. In
other words, polling the eoPowerStateTable allows the discovery other words, polling the eoPowerStateTable allows the discovery
of each Power State within every Power State Set supported by of each Power State within every Power State Set supported by
the Energy Object. the Energy Object.
If the Energy Object is an Aggregator or a Proxy, the MIB If the Energy Object is an Aggregator or a Proxy, the MIB module
module would be populated with the Energy Object Parent and would be populated with the Energy Object Parent and Children
Children information, which have their own Energy Object index information, which have their own Energy Object index value (
value (eoPowerIndex). However, the parent/child relationship entPhysicalIndex). However, the parent/child relationship must
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 Quality thanks to the
powerQualityMIB MIB module, which reuses the eoPowerIndex to powerQualityMIB MIB module, which reuses the entPhysicalIndex to
index the Energy Object. index the Energy Object.
6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB
Implemented
When the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] is not
implemented, the NMS must poll the ENTITY-MIB [RFC4133] in order
to discover some more information about the Energy Objects.
Indeed, the index for the Energy Objects in the MIB modules
specified in this document is the eoPowerIndex, which specifies:
"If there is no implementation of the ENERGY-AWARE-MIB module
but one of the ENTITY MIB module is available in the local SNMP
context, then the same index of an entity MUST be chosen as
assigned to the entity by object entPhysicalIndex in the ENTITY
MIB module."
As described in Section 6.1. the NMS must then poll the
eoPowerStateTable (specified in the energyObjectMib module in
this document), indexed by the Energy Object (eoPowerIndex that
inherited the entPhysicalIndex value), by the Power State
(eoPowerStateIndex). Then the NMS has discovered every Power
State within each Power State Set supported by the Energy
Object.
Note that, without the ENERGY-AWARE-MIB module, the Energy
Object acts as an standalone device, i.e. the notion of
parent/child can't be specified.
6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented
If neither the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] nor of
the ENTITY MIB module [RFC4133] are available in the local SNMP
context, then this MIB module may choose identity values from a
further MIB module providing entity identities.
Note that, without the ENERGY-AWARE-MIB module, the Energy
Object acts as a standalone device, i.e. the notion of
parent/child can't be specified.
7. Link with the other IETF MIBs 7. Link with the other IETF MIBs
7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
RFC 4133 [RFC4133] defines the ENTITY MIB module that lists the RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the
physical entities of a networking device (router, switch, etc.) physical entities of a networking device (router, switch, etc.)
and those physical entities indexed by entPhysicalIndex. From and those physical entities indexed by entPhysicalIndex. From
an energy-management standpoint, the physical entities that an energy-management standpoint, the physical entities that
consume or produce energy are of interest. consume or produce energy are of interest.
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that
provides a standardized way of obtaining information (current provides a standardized way of obtaining information (current
value of the sensor, operational status of the sensor, and the value of the sensor, operational status of the sensor, and the
data units precision) from sensors embedded in networking data units precision) from sensors embedded in networking
devices. Sensors are associated with each index of devices. Sensors are associated with each index of
entPhysicalIndex of the ENTITY MIB [RFC4133]. While the focus entPhysicalIndex of the ENTITY-MIB[RFC4133]. While the focus of
of the Power and Energy Monitoring MIB is on measurement of the Power and Energy Monitoring MIB is on measurement of power
power usage of networking equieoent indexed by the ENTITY MIB, usage of networking equipment indexed by the ENTITY MIB, this
this MIB proposes a customized power scale for power measurement MIB proposes a customized power scale for power measurement and
and different power state states of networking equipment, 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
C12.x accuracy classes required for electricity (i.e., 1%, 2%, C12.x accuracy classes required for electricity (i.e., 1%, 2%,
0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433]
represents "The number of decimal places of precision in fixed- represents "The number of decimal places of precision in fixed-
point sensor values returned by the associated entPhySensorValue point sensor values returned by the associated entPhySensorValue
skipping to change at page 26, line 29 skipping to change at page 34, line 25
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the (compared to entPhySensorScale), with the mantissa and the
exponent values X * 10 ^ Y. exponent values X * 10 ^ Y.
Power measurements specifying the qualifier 'UNITS' for each Power measurements specifying the qualifier 'UNITS' for each
measured value in watts are used in the LLDP-EXT-MED-MIB, POE measured value in watts are used in the LLDP-EXT-MED-MIB, POE
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier
is used for the power measurement values. is used for the power measurement values.
One cannot assume that the ENTITY MIB and ENTITY-SENSOR MIB are One cannot assume that the ENTITY-MIBand 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 eoPowerIndex MIB object has been kept as the unique index of The eoPower is similar to entPhySensorValue [RFC3433] and the
the Energy Object. The eoPower is similar to entPhySensorValue eoPowerUnitMultipler is similar to entPhySensorScale.
[RFC3433] and the eoPowerUnitMultipler is similar to
entPhySensorScale.
7.2. Link with the ENTITY-STATE MIB 7.2. Link with the ENTITY-STATE MIB
For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE
MIB [RFC4268] specifies the operational states (entStateOper: MIB [RFC4268] specifies the operational states (entStateOper:
unknown, enabled, disabled, testing), the alarm (entStateAlarm: unknown, enabled, disabled, testing), the alarm (entStateAlarm:
unknown, underRepair, critical, major, minor, warning, unknown, underRepair, critical, major, minor, warning,
indeterminate) and the possible values of standby states indeterminate) and the possible values of standby states
(entStateStandby: unknown, hotStandby, coldStandby, (entStateStandby: unknown, hotStandby, coldStandby,
providingService). providingService).
skipping to change at page 27, line 42 skipping to change at page 35, line 34
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.
As a consequence, the eoIndex MIB object has been kept as the As a consequence, the entPhysicalIndex MIB object has been kept
unique Energy Object index. as the unique Energy Object index.
Note that, even though the Power-over-Ethernet MIB [RFC3621] was Note that, even though the Power-over-Ethernet MIB [RFC3621] was
created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse
the precision notion from the ENTITY-SENSOR MIB, i.e. the the precision notion from the ENTITY-SENSOR MIB, i.e. the
entPhySensorPrecision MIB object. entPhySensorPrecision MIB object.
7.4. Link with the UPS MIB 7.4. Link with the UPS MIB
To protect against unexpected power disruption, data centers and To protect against unexpected power disruption, data centers and
buildings make use of Uninterruptible Power Supplies (UPS). To buildings make use of Uninterruptible Power Supplies (UPS). To
skipping to change at page 28, line 40 skipping to change at page 36, line 31
(number of input lines, voltage, current, etc.). (number of input lines, voltage, current, etc.).
- upsOutput: Characterizes the output from the UPS (number of - upsOutput: Characterizes the output from the UPS (number of
output lines, voltage, current, etc.) output lines, voltage, current, etc.)
- upsAlarms: Indicates the various alarm events. - upsAlarms: Indicates the various alarm events.
The measurement of power in the UPS MIB is in Volts, Amperes and The measurement of power in the UPS MIB is in Volts, Amperes and
Watts. The units of power measurement are RMS volts and RMS Watts. The units of power measurement are RMS volts and RMS
Amperes. They are not based on the EntitySensorDataScale and Amperes. They are not based on the EntitySensorDataScale and
EntitySensorDataPrecision of Entity-Sensor MIB. EntitySensorDataPrecision of ENTITY-SENSOR-MIB.
Both the Power and Energy Monitoring MIB and the UPS MIB may be Both the Power and Energy Monitoring MIB and the UPS MIB may be
implemented on the same UPS SNMP agent, without conflict. In implemented on the same UPS SNMP agent, without conflict. In
this case, the UPS device itself is the Energy Object Parent and this case, the UPS device itself is the Energy Object Parent and
any of the UPS meters or submeters are the Energy Object any of the UPS meters or submeters are the Energy Object
Children. Children.
7.5. Link with the LLDP and LLDP-MED MIBs 7.5. Link with the LLDP and LLDP-MED MIBs
The LLDP Protocol is a Data Link Layer protocol used by network The LLDP Protocol is a Data Link Layer protocol used by network
skipping to change at page 30, line 21 skipping to change at page 38, line 11
The campus network consists of switches that provide LAN The campus network consists of switches that provide LAN
connectivity. The switch with PoE ports is located in wiring connectivity. The switch with PoE ports is located in wiring
closet. PoE IP phones are connected to the switch. The IP closet. PoE IP phones are connected to the switch. The IP
phones draw power from the PoE ports of the switch. In phones draw power from the PoE ports of the switch. In
addition, a PC is daisy-chained from the IP phone for LAN addition, a PC is daisy-chained from the IP phone for LAN
connectivity. connectivity.
The IP phone consumes power from the PoE switch, while the PC The IP phone consumes power from the PoE switch, while the PC
consumes power from the wall outlet. consumes power from the wall outlet.
The switch has implementations of Entity MIB [RFC4133] and The switch has implementations of ENTITY-MIB [RFC4133] and
energy-aware MIB [EMAN-AWARE-MIB] while the PC does not have ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have
implementation of the Entity MIB, but has an implementation of implementation of the ENTITY-MIB, but has an implementation of
energy-aware MIB. The switch has the following attributes, ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following
eoPowerIndex "1", eoPhysicalEntity "2", and eoUUID "UUID 1000". attributes, entPhysicalIndex "1", and eoUUID "UUID 1000". The
The power usage of the switch is "440 Watts". The switch does power usage of the switch is "440 Watts". The switch does not
not have an Energy Object Parent. have an Energy Object Parent.
The PoE switch port has the following attributes: The switch The PoE switch port has the following attributes: The switch
port has eoPowerIndex "3", eoPhysicalEntity is "12" and eoUUID port has entPhysicalIndex "3", and eoUUID is "UUID 1000:3". The
is "UUID 1000:3". The power metered at the POE switch port is power metered at the POE switch port is "12 watts". In this
"12 watts". In this example, the POE switch port has the switch example, the POE switch port has the switch as the Energy Object
as the Energy Object Parent, with its eoParentID of "1000". Parent, with its eoParentID of "1000".
The attributes of the PC are given below. The PC does not The attributes of the PC are given below. The PC does not have
implementation of Entity MIB, and thus does not have an entPhysicalIndex, andthe eoUUID is "UUID 1000:57 ". The PC
eoPhysicalEntity. The eoPowerIndex (eoIndex) of the PC is "57", has an Energy Object Parent, i.e. the switch port whose eoUUID
the eoUUID is "UUID 1000:57 ". The PC has an Energy Object is "UUID 1000:3". The power usage of the PC is "120 Watts" and
Parent, i.e. the switch port whose eoUUID is "UUID 1000:3". The is communicated to the switch port.
power usage of the PC is "120 Watts" and is communicated to the
switch port.
This example illustrates the important distinction between the This example illustrates the important distinction between the
Energy Object Children: The IP phone draws power from the Energy Object Children: The IP phone draws power from the
switch, while the PC has LAN connectivity from the phone, but is switch, while the PC has LAN connectivity from the phone, but is
powered from the wall outlet. However, the Energy Object Parent powered from the wall outlet. However, the Energy Object Parent
sends power control messages to both the Energy Object Children sends power control messages to both the Energy Object Children
(IP phone and PC) and the Children react to those messages. (IP phone and PC) and the Children react to those messages.
|--------------------------------------------------------------| |-------------------------------------------------------|
| Switch | | Switch |
|==============================================================| |=======================================================|
| Switch | Switch | Switch | Switch | Switch | | Switch | Switch | Switch | Switch |
| eoIndex | eoPhyIdx | eoUUID |eoParentId | eoPower | | entPhyIndx | UUID |eoParentId | eoPower |
| ============================================================ | | ===================================================== |
| 1 | 2 | UUID 1000 | null | 440 | | 1 | UUID 1000 | null | 440 |
| ============================================================ | | ===================================================== |
| | | |
| SWITCH PORT | | SWITCH PORT |
| ============================================================ | | ===================================================== |
| | Switch | Switch | Switch | Switch | Switch | | | Switch | Switch | Switch | Switch |
| | Port | Port | Port | Port | Port | | | | Port | Port | Port | Port |
| | eoIndex| eoPhyIdx | eoUUID | eoParentId | eoPower | | | | entPhyIndx | UUID | eoParentId | eoPower |
| ============================================================ | | ===================================================== |
| | 3 | 12 | UUID 1000:3 | UUID 1000 | 12 | | | | 3 | UUID 1000:3 | 1000 | 12 |
| ============================================================ | | ======================================================|
| ^ | | ^
| | | | |
|-----------------------------------|--------------------------| |-----------------------------------|-------------------
| |
| |
POE IP PHONE | POE IP PHONE |
| |
| |
============================================================= ======================================================
| IP phone | IP phone |IP phone | IP phone |IP phone| | IP phone | IP phone | IP phone | IP phone |
| eoIndex | eoPhyIdx |eoUUID |eoParentID |eoPower | | entPhyIndx | UUID | eoParentID | eoPower |
=========================================================== ======================================================
| 31 | 0 |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 | PC |
|eoIndex| eoPhyIdx |eoUUID |eoParentID | eoPower | |eoPhyIndx | UUID |eoParentID | eoPower |
============================================================ ==================================================
| 57 | 0 | UUID 1000:57| UUID 1000:3| 120 | | Null | UUID1000: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
[EMAN-AWARE-MIB] module. Thus the following requirements which
are applied to [EMAN-AWARE-MIB] are also applicable. As a
requirement for this MIB module, [EMAN-AWARE-MIB] should be
implemented and the three MIB objects from ENTITY-MIB
(entPhysicalIndex, entPhysicalName and entPhysicalUris) MUST be
implemented.
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 eoPowerQuality table
skipping to change at page 33, line 6 skipping to change at page 41, line 6
-- --
-- ************************************************************* -- *************************************************************
ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
mib-2, mib-2,
Integer32, Counter64, TimeTicks Integer32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval,
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
FROM ENTITY-MIB;
energyObjectMib MODULE-IDENTITY energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201110310000Z" -- 31 October 2011 LAST-UPDATED "201202150000Z" -- 15 March 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 34, line 29 skipping to change at page 42, line 33
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 monitor power and energy in "This MIB is used to monitor power and energy in
devices." devices.
This table sparse extension of the eoTable
from the ENERGY-AWARE-MIB. As a requirement
[EMAN-AWARE-MIB] should be implemented and
three MIB objects from ENTITY-MIB
(entPhysicalIndex, entPhysicalName and
entPhysicalUris)MUST be implemented. "
REVISION REVISION
"201110310000Z" -- 31 October 2011 "201202150000Z" -- 15 March 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 35, line 4 skipping to change at page 43, line 12
energyObjectMibNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { energyObjectMib 0 } ::= { energyObjectMib 0 }
energyObjectMibObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
::= { energyObjectMib 1 } ::= { energyObjectMib 1 }
energyObjectMibConform OBJECT IDENTIFIER energyObjectMibConform OBJECT IDENTIFIER
::= { energyObjectMib 2 } ::= { energyObjectMib 2 }
-- Textual Conventions -- Textual Conventions
IANAPowerStateSet ::= TEXTUAL-CONVENTION IANAPowerStateSet ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IANAPowerStateSet is a textual convention that describes "IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of Power by an Energy Object and IANA shall administer the list of Power
State Sets and Power States. State Sets and Power States.
The textual convention assumes that power states in a power The textual convention assumes that power states in a power
state set are limited to 255 distinct values. For a Power state set are limited to 255 distinct values. For a Power
State Set S, the named number with the value S * 256 is State Set S, the named number with the value S * 256 is
allocated to indicate the power state set. For a Power State X allocated to indicate the power state set. For a Power State X
in the Power State S, the named number with the value S * 256 in the Power State S, the named number with the value S * 256
skipping to change at page 37, line 25 skipping to change at page 45, line 33
DESCRIPTION DESCRIPTION
"This table lists Energy Objects." "This table lists Energy Objects."
::= { energyObjectMibObjects 1 } ::= { energyObjectMibObjects 1 }
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 { eoPowerIndex}
::= { eoPowerTable 1 } INDEX { entPhysicalIndex }
::= { eoPowerTable 1 }
EoPowerEntry ::= SEQUENCE { EoPowerEntry ::= SEQUENCE {
eoPowerIndex Integer32,
eoPower Integer32, eoPower Integer32,
eoPowerNameplate Integer32, eoPowerNameplate Integer32,
eoPowerUnitMultiplier UnitMultiplier, eoPowerUnitMultiplier UnitMultiplier,
eoPowerAccuracy Integer32, eoPowerAccuracy Integer32,
eoPowerMeasurementCaliber INTEGER, eoPowerMeasurementCaliber INTEGER,
eoPowerCurrentType INTEGER, eoPowerCurrentType INTEGER,
eoPowerOrigin INTEGER, eoPowerOrigin INTEGER,
eoPowerAdminState IANAPowerStateSet, eoPowerAdminState IANAPowerStateSet,
eoPowerOperState IANAPowerStateSet, eoPowerOperState IANAPowerStateSet,
eoPowerStateEnterReason OwnerString eoPowerStateEnterReason OwnerString
} }
eoPowerIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value, for each Energy Object.
If an implementation of the ENERGY-AWARE-MIB module is
available in the local SNMP context, then the same index,
eoIndex, as the one in the ENERGY-AWARE-MIB MUST be
assigned for the identical Energy Object. In this case,
entities without an assigned value for eoIndex cannot be
indexed by the eoPowerStateTable.
If there is no implementation of the ENERGY-AWARE-MIB
module but one of the ENTITY MIB module is available in
the local SNMP context, then the same index of an entity
MUST be chosen as assigned to the entity by object
entPhysicalIndex in the ENTITY MIB module. In this case,
entities without an assigned value for entPhysicalIndex
cannot be indexed by the eoPowerStateTable.
If neither the ENERGY-AWARE-MIB module nor of the ENTITY
MIB module are available in the local SNMP context, then
this MIB module may choose identity values from a further
MIB module providing entity identities. In this case the
value for each eoPowerIndex must remain constant at least
from one re-initialization of the entity's network
management system to the next re-initialization.
In case that no other MIB modules have been chosen for
providing entity identities, Power States can be reported
exclusively for the local device on which this table is
instantiated. Then this table will have a single entry
only and an index value of 0 MUST be used."
::= { eoPowerEntry 1 }
eoPower OBJECT-TYPE eoPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watts" UNITS "Watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the power measured for the Energy "This object indicates the power measured for the Energy
Object. For alternating current, this value is obtained Object. For alternating current, this value is obtained
as an average over fixed number of AC cycles. . This as an average over fixed number of AC cycles. . This
value is specified in SI units of watts with the value is specified in SI units of watts with the
skipping to change at page 39, line 17 skipping to change at page 46, line 33
The eoPower MUST be less than or equal to the maximum The eoPower MUST be less than or equal to the maximum
power that can be consumed at the power state specified power that can be consumed at the power state specified
by eoPowerState. by eoPowerState.
The eoPowerMeasurementCaliber object specifies how the The eoPowerMeasurementCaliber object specifies how the
usage value reported by eoPower was obtained. The eoPower usage value reported by eoPower was obtained. The eoPower
value must report 0 if the eoPowerMeasurementCaliber is value must report 0 if the eoPowerMeasurementCaliber is
'unavailable'. For devices that can not measure or 'unavailable'. For devices that can not measure or
report power, this option can be used." report power, this option can be used."
::= { eoPowerEntry 2 } ::= { 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 3 } ::= { eoPowerEntry 2 }
eoPowerUnitMultiplier OBJECT-TYPE eoPowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in eoPower "The magnitude of watts for the usage value in eoPower
and eoPowerNameplate." and eoPowerNameplate."
::= { eoPowerEntry 4 } ::= { eoPowerEntry 3 }
eoPowerAccuracy OBJECT-TYPE eoPowerAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a percentage value, in 100ths of a "This object indicates a percentage value, in 100ths of a
percent, representing the assumed accuracy of the usage percent, representing the assumed accuracy of the usage
reported by eoPower. For example: The value 1010 means reported by eoPower. For example: The value 1010 means
the reported usage is accurate to +/- 10.1 percent. This the reported usage is accurate to +/- 10.1 percent. This
value is zero if the accuracy is unknown or not value is zero if the accuracy is unknown or not
applicable based upon the measurement method. applicable based upon the measurement method.
ANSI and IEC define the following accuracy classes for ANSI and IEC define the following accuracy classes for
power measurement: power measurement:
IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
ANSI C12.20 class 0.2, 0.5" ANSI C12.20 class 0.2, 0.5"
::= { eoPowerEntry 5 } ::= { eoPowerEntry 4 }
eoPowerMeasurementCaliber OBJECT-TYPE eoPowerMeasurementCaliber OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unavailable(1) , unavailable(1) ,
unknown(2), unknown(2),
actual(3) , actual(3) ,
estimated(4), estimated(4),
presumed(5) } presumed(5) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies how the usage value reported by "This object specifies how the usage value reported by
eoPower was obtained: eoPower was obtained:
- unavailable(1): Indicates that the usage is not - unavailable(1): Indicates that the usage is not
available. In such a case, the eoPower value must be 0 available. In such a case, the eoPower value must be 0
For devices that can not measure or report power this for devices that can not measure or report power this
option can be used. option can be used.
- unknown(2): Indicates that the way the usage was - unknown(2): Indicates that the way the usage was
determined is unknown. In some cases, entities report determined is unknown. In some cases, entities report
aggregate power on behalf of another device. In such aggregate power on behalf of another device. In such
cases it is not known whether the usage reported is cases it is not known whether the usage reported is
actual(2), estimated(3) or presumed (4). actual(2), estimated(3) or presumed (4).
- actual(3): Indicates that the reported usage was - actual(3): Indicates that the reported usage was
measured by the entity through some hardware or direct measured by the entity through some hardware or direct
skipping to change at page 41, line 15 skipping to change at page 48, line 33
is presumed that the entity's state and current is presumed that the entity's state and current
configuration were used to compute the value. configuration were used to compute the value.
- presumed(5): Indicates that the usage was not - presumed(5): Indicates that the usage was not
determined by physical measurement, algorithm or determined by physical measurement, algorithm or
derivation. The usage was reported based upon external derivation. The usage was reported based upon external
tables, specifications, and/or model information. For tables, specifications, and/or model information. For
example, a PC Model X draws 200W, while a PC Model Y example, a PC Model X draws 200W, while a PC Model Y
draws 210W" draws 210W"
::= { eoPowerEntry 6 } ::= { eoPowerEntry 5 }
eoPowerCurrentType OBJECT-TYPE eoPowerCurrentType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ac(1), ac(1),
dc(2), dc(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the eoUsage for the "This object indicates whether the eoUsage for the
Energy Object reports alternative current AC(1), direct Energy Object reports alternative current AC(1), direct
current DC(2), or that the current type is unknown(3)." current DC(2), or that the current type is unknown(3)."
::= { eoPowerEntry 7 } ::= { eoPowerEntry 6 }
eoPowerOrigin OBJECT-TYPE eoPowerOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
self (1), self (1),
remote (2) remote (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the source of power measurement "This object indicates the source of power measurement
and can be useful when modeling the power usage of and can be useful when modeling the power usage of
attached devices. The power measurement can be performed attached devices. The power measurement can be performed
by the entity itself or the power measurement of the by the entity itself or the power measurement of the
entity can be reported by another trusted entity using a entity can be reported by another trusted entity using a
protocol extension. A value of self(1) indicates the protocol extension. A value of self(1) indicates the
measurement is performed by the entity, whereas remote(2) measurement is performed by the entity, whereas remote(2)
indicates that the measurement was performed by another indicates that the measurement was performed by another
entity." entity."
::= { eoPowerEntry 8 } ::= { eoPowerEntry 7 }
eoPowerAdminState OBJECT-TYPE eoPowerAdminState OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the desired Power State and the "This object specifies the desired Power State and the
Power State Set for the Energy Object. Note that Power State Set for the Energy Object. Note that
other(0) is not a Power State Set and unknown(255) is other(0) is not a Power State Set and unknown(255) is
not a Power State as such, but simply an indication that not a Power State as such, but simply an indication that
the Power State of the Energy Object is unknown. the Power State of the Energy Object is unknown.
Possible values of eoPowerAdminState within the Power Possible values of eoPowerAdminState within the Power
State Set are registered at IANA. State Set are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<http://www.iana.org/assignments/eman> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
skipping to change at page 42, line 18 skipping to change at page 49, line 35
"This object specifies the desired Power State and the "This object specifies the desired Power State and the
Power State Set for the Energy Object. Note that Power State Set for the Energy Object. Note that
other(0) is not a Power State Set and unknown(255) is other(0) is not a Power State Set and unknown(255) is
not a Power State as such, but simply an indication that not a Power State as such, but simply an indication that
the Power State of the Energy Object is unknown. the Power State of the Energy Object is unknown.
Possible values of eoPowerAdminState within the Power Possible values of eoPowerAdminState within the Power
State Set are registered at IANA. State Set are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<http://www.iana.org/assignments/eman> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 9 } ::= { eoPowerEntry 8 }
eoPowerOperState OBJECT-TYPE eoPowerOperState OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the current operational Power "This object specifies the current operational Power
State and the Power State Set for the Energy Object. State and the Power State Set for the Energy Object.
other(0) is not a Power State Set and unknown(255) is other(0) is not a Power State Set and unknown(255) is
skipping to change at page 42, line 34 skipping to change at page 50, line 4
DESCRIPTION DESCRIPTION
"This object specifies the current operational Power "This object specifies the current operational Power
State and the Power State Set for the Energy Object. State and the Power State Set for the Energy Object.
other(0) is not a Power State Set and unknown(255) is other(0) is not a Power State Set and unknown(255) is
not a Power State as such, but simply an indication that not a Power State as such, but simply an indication that
the Power State of the Energy Object is unknown. the Power State of the Energy Object is unknown.
Possible values of eoPowerAdminState within the Power Possible values of eoPowerAdminState within the Power
State Set are registered at IANA. State Set are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<http://www.iana.org/assignments/eman> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 10 } ::= { eoPowerEntry 9 }
eoPowerStateEnterReason OBJECT-TYPE eoPowerStateEnterReason OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This string object describes the reason for the "This string object describes the reason for the
eoPowerAdminState eoPowerAdminState
transition Alternatively, this string may contain with transition Alternatively, this string may contain with
the entity that configured this Energy Object to this the entity that configured this Energy Object to this
skipping to change at page 43, line 4 skipping to change at page 50, line 21
eoPowerStateEnterReason OBJECT-TYPE eoPowerStateEnterReason OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This string object describes the reason for the "This string object describes the reason for the
eoPowerAdminState eoPowerAdminState
transition Alternatively, this string may contain with transition Alternatively, this string may contain with
the entity that configured this Energy Object to this the entity that configured this Energy Object to this
Power State." Power State."
DEFVAL { "" } DEFVAL { "" }
::= { eoPowerEntry 11 } ::= { eoPowerEntry 10 }
eoPowerStateTable OBJECT-TYPE eoPowerStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerStateEntry SYNTAX SEQUENCE OF EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates the maximum power usage, in watts, "This table enumerates the maximum power usage, in watts,
for every single supported Power State of each 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 2 }
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
skipping to change at page 44, line 9 skipping to change at page 51, line 23
8 (low) 11 W 8 (low) 11 W
9 (medimMinus) 11 W 9 (medimMinus) 11 W
10 (medium) 11 W 10 (medium) 11 W
11 (highMinus) 11 W 11 (highMinus) 11 W
12 (high) 11 W 12 (high) 11 W
Furthermore, this table extends to return the total time Furthermore, this table extends to return the total time
in each Power State, along with the number of times a in each Power State, along with the number of times a
particular Power State was entered." particular Power State was entered."
INDEX { eoPowerIndex, INDEX { entPhysicalIndex,
eoPowerStateIndex eoPowerStateIndex
} }
::= { eoPowerStateTable 1 } ::= { eoPowerStateTable 1 }
EoPowerStateEntry ::= SEQUENCE { EoPowerStateEntry ::= SEQUENCE {
eoPowerStateIndex IANAPowerStateSet, eoPowerStateIndex IANAPowerStateSet,
eoPowerStateMaxPower Integer32, eoPowerStateMaxPower Integer32,
eoPowerStatePowerUnitMultiplier UnitMultiplier, eoPowerStatePowerUnitMultiplier UnitMultiplier,
eoPowerStateTotalTime TimeTicks, eoPowerStateTotalTime TimeTicks,
eoPowerStateEnterCount Counter64 eoPowerStateEnterCount Counter32
} }
eoPowerStateIndex OBJECT-TYPE eoPowerStateIndex OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "
This object specifies the index of the Power State of This object specifies the index of the Power State of
the Energy Object within a Power State Set. The the Energy Object within a Power State Set. The
skipping to change at page 44, line 51 skipping to change at page 52, line 17
Object at the particular Power State. This value is Object at the particular Power State. This value is
specified in SI units of watts with the magnitude of the specified in SI units of watts with the magnitude of the
units (milliwatts, kilowatts, etc.) indicated separately units (milliwatts, kilowatts, etc.) indicated separately
in eoPowerStatePowerUnitMultiplier. If the maximum power in eoPowerStatePowerUnitMultiplier. If the maximum power
is not known for a certain Power State, then the value is is not known for a certain Power State, then the value is
encoded as 0xFFFF. encoded as 0xFFFF.
For Power States not enumerated, the value of For Power States not enumerated, the value of
eoPowerStateMaxPower might be interpolated by using the eoPowerStateMaxPower might be interpolated by using the
next highest supported Power State." next highest supported Power State."
::= { eoPowerStateEntry 3 } ::= { eoPowerStateEntry 2 }
eoPowerStatePowerUnitMultiplier OBJECT-TYPE eoPowerStatePowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in "The magnitude of watts for the usage value in
eoPowerStateMaxPower." eoPowerStateMaxPower."
::= { eoPowerStateEntry 4 } ::= { eoPowerStateEntry 3 }
eoPowerStateTotalTime OBJECT-TYPE eoPowerStateTotalTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the total time in hundreds "This object indicates the total time in hundreds
of seconds that the Energy Object has been in this power of seconds that the Energy Object has been in this power
state since the last reset, as specified in the state since the last reset, as specified in the
sysUpTime." sysUpTime."
::= { eoPowerStateEntry 5 } ::= { eoPowerStateEntry 4 }
eoPowerStateEnterCount OBJECT-TYPE eoPowerStateEnterCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the Energy "This object indicates how often the Energy
Object has Object has
entered this power state, since the last reset of the entered this power state, since the last reset of the
device as specified in the sysUpTime." device as specified in the sysUpTime."
::= { eoPowerStateEntry 6 } ::= { eoPowerStateEntry 5 }
eoEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyParametersEntry SYNTAX SEQUENCE OF EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to configure the parameters for Energy "This table is used to configure the parameters for
measurement collection in the table eoEnergyTable." Energy measurement collection in the table
::= { energyObjectMibObjects 4 } eoEnergyTable. This table allows the configuration of
different measurement settings on the same Energy
Object."
::= { energyObjectMibObjects 3 }
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 { eoPowerIndex } INDEX { eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
EoEnergyParametersEntry ::= SEQUENCE { EoEnergyParametersEntry ::= SEQUENCE {
eoEnergyParametersIntervalLength TimeInterval, eoEnergyObjectIndex PhysicalIndex,
eoEnergyParametersIntervalNumber Integer32, eoEnergyParametersIndex Integer32,
eoEnergyParametersIntervalMode Integer32, eoEnergyParametersIntervalLength TimeInterval,
eoEnergyParametersIntervalWindow TimeInterval, eoEnergyParametersIntervalNumber Integer32,
eoEnergyParametersSampleRate Integer32, eoEnergyParametersIntervalMode Integer32,
eoEnergyParametersStatus RowStatus eoEnergyParametersIntervalWindow TimeInterval,
eoEnergyParametersSampleRate Integer32,
eoEnergyParametersStatus RowStatus
} }
eoEnergyObjectIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The unique value, to identify the specific Energy Object
on which the measurement is applied, the same index used
in the eoPowerTable to identify the Energy Object."
::= { eoEnergyParametersEntry 1 }
eoEnergyParametersIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the index of the Energy
Parameters setting for collection of energy measurements
for an Energy Object. An Energy Object can have multiple
eoEnergyParametersIndex, depending on the capability of
the Energy Object"
::= { eoEnergyParametersEntry 2 }
eoEnergyParametersIntervalLength OBJECT-TYPE eoEnergyParametersIntervalLength OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the length of time in seconds over "This object indicates the length of time in hundredth of
which to compute the average eoEnergyIntervalEnergyUsed seconds over which to compute the average
measurement in the eoEnergyTable table. The computation eoEnergyConsumed measurement in the eoEnergyTable table.
is based on the Energy Object's internal sampling rate of The computation is based on the Energy Object's internal
power consumed or produced by the Energy Object. The sampling rate of power consumed or produced by the Energy
sampling rate is the rate at which the Energy Object can Object. The sampling rate is the rate at which the Energy
read the power usage and may differ based on device Object can read the power usage and may differ based on
capabilities. The average energy consumption is then device capabilities. The average energy consumption is
computed over the length of the interval." then computed over the length of the interval."
DEFVAL { 900 } DEFVAL { 90000 }
::= { eoEnergyParametersEntry 1 } ::= { eoEnergyParametersEntry 3 }
eoEnergyParametersIntervalNumber OBJECT-TYPE eoEnergyParametersIntervalNumber OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of intervals maintained in the eoEnergyTable. "The number of intervals maintained in the eoEnergyTable.
Each interval is characterized by a specific Each interval is characterized by a specific
eoEnergyIntervalStartTime, used as an index to the table eoEnergyCollectionStartTime, used as an index to the
eoEnergyTable . Whenever the maximum number of entries is table eoEnergyTable. Whenever the maximum number of
reached, the measurement over the new interval replaces entries is reached, the measurement over the new interval
the oldest measurement , except if the oldest measurement replacesthe oldest measurement. There is one exception to
were to be the maximum eoEnergyIntervalMax, in which case this rule: when the eoEnergyMaxConsumed and/or
the measurement the measurement over the next oldest eoEnergyMaxProduced are in (one of) the two oldest
interval is replaced." measurement(s), they are left untouched and the next
DEFVAL { 10 } oldest measurement is replaced."
DEFVAL { 10 }
::= { eoEnergyParametersEntry 2 } ::= { eoEnergyParametersEntry 4 }
eoEnergyParametersIntervalMode OBJECT-TYPE eoEnergyParametersIntervalMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
period(1), period(1),
sliding(2), sliding(2),
total(3) total(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control object to define the mode of interval calculation "A control object to define the mode of interval calculation
for the computation of the average for the computation of the average eoEnergyConsumed or
eoEnergyIntervalEnergyUsed measurement in the eoEnergyTable eoEnergyProduced measurement in the eoEnergyTable table.
table.
A mode of period(1) specifies non-overlapping periodic A mode of period(1) specifies non-overlapping periodic
measurements. measurements.
A mode of sliding(2) specifies overlapping sliding windows A mode of sliding(2) specifies overlapping sliding windows
where the interval between the start of one interval and where the interval between the start of one interval and
the next is defined in eoEnergyParametersIntervalWindow. the next is defined in eoEnergyParametersIntervalWindow.
A mode of total(3) specifies non-periodic measurement. In A mode of total(3) specifies non-periodic measurement. In
this mode only one interval is used as this is a this mode only one interval is used as this is a
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. " eoEnergyParametersIntervalLength is ignored. "
::= { eoEnergyParametersEntry 3 } ::= { eoEnergyParametersEntry 5 }
eoEnergyParametersIntervalWindow OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the duration window between the starting "The length of the duration window between the starting
time of one sliding window and the next starting time in time of one sliding window and the next starting time in
seconds, in order to compute the average hundredth of seconds, in order to compute the average of
eoEnergyIntervalEnergyUsed measurement in the eoEnergyTable eoEnergyConsumed, eoEnergyProduced measurements in the
table This is valid only when the eoEnergyTable table. This is valid only when the
eoEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyParametersIntervalWindow value should be a multiple eoEnergyParametersIntervalWindow value should be a multiple
of eoEnergyParametersSampleRate." of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 4 } ::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sampling rate, in milliseconds, at which the Energy "The sampling rate, in milliseconds, at which the Energy
Object should poll power usage in order to compute the Object should poll power usage in order to compute the
average eoEnergyIntervalEnergyUsed measurement in the average eoEnergyConsumed, eoEnergyProduced measurements
table eoEnergyTable. The Energy Object should initially in the table eoEnergyTable. The Energy Object should
set this sampling rate to a reasonable value, i.e., a initially set this sampling rate to a reasonable value,
compromise between intervals that will provide good i.e., a compromise between intervals that will provide
accuracy by not being too long, but not so short that good accuracy by not being too long, but not so short
they affect the Energy Object performance by requesting that they affect the Energy Object performance by
continuous polling. If the sampling rate is unknown, the requesting continuous polling. If the sampling rate is
value 0 is reported. The sampling rate should be selected unknown, the value 0 is reported. The sampling rate
so that eoEnergyParametersIntervalWindow is a multiple of should be selected so that
eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate." eoEnergyParametersSampleRate."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { eoEnergyParametersEntry 5 } ::= { eoEnergyParametersEntry 7 }
eoEnergyParametersStatus OBJECT-TYPE eoEnergyParametersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row. The eoEnergyParametersStatus is "The status of this row. The eoEnergyParametersStatus is
used to start or stop energy usage logging. An entry used to start or stop energy usage logging. An entry
status may not be active(1) unless all objects in the status may not be active(1) unless all objects in the
entry have an appropriate value. If this object is not entry have an appropriate value. If this object is not
equal to active(1), all associated usage-data logged into equal to active(1), all associated usage-data logged into
the eoEnergyTable will be deleted. The data can be the eoEnergyTable will be deleted. The data can be
destroyed by setting up the eoEnergyParametersStatus to destroyed by setting up the eoEnergyParametersStatus to
destroy(2)." destroy(2)."
::= {eoEnergyParametersEntry 6 } ::= {eoEnergyParametersEntry 8 }
eoEnergyTable OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyIntervalEntry 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 5 } ::= { energyObjectMibObjects 4 }
eoEnergyIntervalEntry OBJECT-TYPE eoEnergyEntry OBJECT-TYPE
SYNTAX EoEnergyIntervalEntry 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 { eoPowerIndex, eoEnergyParametersIntervalMode, INDEX { eoEnergyParametersIndex,
eoEnergyIntervalStartTime } eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 } ::= { eoEnergyTable 1 }
EoEnergyIntervalEntry ::= SEQUENCE { EoEnergyEntry ::= SEQUENCE {
eoEnergyIntervalStartTime TimeTicks, eoEnergyCollectionStartTime TimeTicks,
eoEnergyIntervalEnergyConsumed Integer32, eoEnergyConsumed Integer32,
eoEnergyIntervalEnergyProduced Integer32, eoEnergyProduced Integer32,
eoEnergyIntervalEnergyNet Integer32, eoEnergyNet Integer32,
eoEnergyIntervalEnergyUnitMultiplier UnitMultiplier, eoEnergyUnitMultiplier UnitMultiplier,
eoEnergyIntervalEnergyAccuracy Integer32, eoEnergyAccuracy Integer32,
eoEnergyIntervalMaxConsumed Integer32, eoEnergyMaxConsumed Integer32,
eoEnergyIntervalMaxProduced Integer32, eoEnergyMaxProduced Integer32,
eoEnergyIntervalDiscontinuityTime TimeTicks eoEnergyDiscontinuityTime TimeStamp
} }
eoEnergyIntervalStartTime OBJECT-TYPE eoEnergyCollectionStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
UNITS "hundredths of seconds" UNITS "hundredths of seconds"
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since the "The time (in hundredths of a second) since the
network management portion of the system was last network management portion of the system was last
re-initialized, as specified in the sysUpTime [RFC3418]. re-initialized, as specified in the sysUpTime [RFC3418].
This object is useful for reference of interval periods This object is useful for reference of interval periods
for which the energy is measured." for which the energy is measured."
::= { eoEnergyIntervalEntry 1 } ::= { eoEnergyEntry 1 }
eoEnergyIntervalEnergyConsumed OBJECT-TYPE eoEnergyConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy consumed in units of watt- "This object indicates the energy consumed in units of watt-
hours for the Energy Object over the defined interval. hours for the Energy Object over the defined interval.
This value is specified in the common billing units of watt- This value is specified in the common billing units of watt-
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyIntervalEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyIntervalEntry 2 } ::= { eoEnergyEntry 2 }
eoEnergyIntervalEnergyProduced OBJECT-TYPE eoEnergyProduced OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the energy produced in units of watt- "This object indicates the energy produced in units of watt-
hours for the Energy Object over the defined interval. hours for the Energy Object over the defined interval.
This value is specified in the common billing units of watt- This value is specified in the common billing units of watt-
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyIntervalEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyIntervalEntry 3 } ::= { eoEnergyEntry 3 }
eoEnergyIntervalEnergyNet OBJECT-TYPE eoEnergyNet OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the resultant of the energy consumed and "This object indicates the resultant of the energy consumed and
energy produced for an energy object in units of watt-hours for energy produced for an energy object in units of watt-hours for
the Energy Object over the defined interval. This value is the Energy Object over the defined interval. This value is
specified in the common billing units of watt-hours specified in the common billing units of watt-hours
with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyIntervalEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyIntervalEntry 4 } ::= { eoEnergyEntry 4 }
eoEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE eoEnergyUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the magnitude of watt-hours for the "This object is the magnitude of watt-hours for the
energy field in eoEnergyIntervalEnergyUsed." energy field in eoEnergyConsumed, eoEnergyProduced,
::= { eoEnergyIntervalEntry 5 } eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced
."
::= { eoEnergyEntry 5 }
eoEnergyIntervalEnergyAccuracy OBJECT-TYPE eoEnergyAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a percentage value, in 100ths of a "This object indicates a percentage value, in 100ths of a
percent, representing the presumed accuracy of Energy usage percent, representing the presumed accuracy of Energy usage
reporting. eoEnergyIntervalEnergyAccuracy is applicable to all reporting. eoEnergyAccuracy is applicable to all Energy
Energy measurements in the eoEnergyTable. measurements in the eoEnergyTable.
For example: 1010 means the reported usage is accurate to +/- For example: 1010 means the reported usage is accurate to +/-
10.1 percent. 10.1 percent.
This value is zero if the accuracy is unknown." This value is zero if the accuracy is unknown."
::= { eoEnergyIntervalEntry 6 } ::= { eoEnergyEntry 6 }
eoEnergyIntervalMaxConsumed OBJECT-TYPE eoEnergyMaxConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy ever observed in "This object is the maximum energy ever observed in
eoEnergyIntervalEnergyConsumed since the monitoring eoEnergyConsumed since the monitoring started. This value
started. This value is specified in the common billing is specified in the common billing units of watt-hours
units of watt-hours with the magnitude of watt-hours (kW- with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
Hr, MW-Hr, etc.) indicated separately in indicated separately in eoEnergyUnitMultiplier."
eoEnergyIntervalEnergyUnits." ::= { eoEnergyEntry 7 }
::= { eoEnergyIntervalEntry 7 }
eoEnergyIntervalMaxProduced OBJECT-TYPE eoEnergyMaxProduced OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy ever observed in "This object is the maximum energy ever observed in
eoEnergyIntervalEnergyProduced since the monitoring eoEnergyEnergyProduced since the monitoring started. This
started. This value is specified in the units of watt- value is specified in the units of watt-hours with the
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated
etc.) indicated separately in separately in eoEnergyEnergyUnitMultiplier."
eoEnergyIntervalEnergyUnits." ::= { eoEnergyEntry 8 }
::= { eoEnergyIntervalEntry 8 }
eoEnergyIntervalDiscontinuityTime OBJECT-TYPE eoEnergyDiscontinuityTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime [RFC3418] on the most recent "The value of sysUpTime [RFC3418] on the most recent
occasion at which any one or more of this entity's energy occasion at which any one or more of this entity's energy
consumption counters suffered a discontinuity. If no such counters in this table suffered a discontinuity:
discontinuities have occurred since the last re- eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no
such discontinuities have occurred since the last re-
initialization of the local management subsystem, then initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
::= { eoEnergyIntervalEntry 9 } ::= { eoEnergyEntry 9 }
-- Notifications -- Notifications
eoPowerStateChange NOTIFICATION-TYPE eoPowerStateChange NOTIFICATION-TYPE
OBJECTS {eoPowerAdminState, eoPowerOperState, OBJECTS {eoPowerAdminState, eoPowerOperState,
eoPowerStateEnterReason} eoPowerStateEnterReason}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP entity generates the eoPowerStateChange when "The SNMP entity generates the eoPowerStateChange when
the value(s) of eoPowerAdminState or eoPowerOperState, the value(s) of eoPowerAdminState or eoPowerOperState,
in the context of the Power State Set, have changed for in the context of the Power State Set, have changed for
the Energy Object represented by the eoPowerIndex." the Energy Object represented by the entPhysicalIndex."
::= { energyObjectMibNotifs 1 } ::= { energyObjectMibNotifs 1 }
-- Conformance -- Conformance
energyObjectMibCompliances OBJECT IDENTIFIER energyObjectMibCompliances OBJECT IDENTIFIER
::= { energyObjectMib 3 } ::= { energyObjectMib 3 }
energyObjectMibGroups OBJECT IDENTIFIER energyObjectMibGroups OBJECT IDENTIFIER
::= { energyObjectMib 4 } ::= { energyObjectMib 4 }
energyObjectMibFullCompliance MODULE-COMPLIANCE energyObjectMibFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for "When this MIB is implemented with support for
read-create, then such an implementation can read-create, then such an implementation can
claim full compliance. Such devices can then claim full compliance. Such devices can then
be both monitored and configured with this MIB." be both monitored and configured with this MIB.
The entPhysicalIndex, entPhysicalName, and
entPhysicalUris [RFC4133] MUST be implemented."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMibTableGroup,
energyObjectMibStateTableGroup, energyObjectMibStateTableGroup,
energyObjectMibEnergyTableGroup,
energyObjectMibEnergyParametersTableGroup,
energyObjectMibNotifGroup energyObjectMibNotifGroup
} }
GROUP energyObjectMibEnergyTableGroup
DESCRIPTION "A compliant implementation does not
have to implement. The entPhysicalIndex,
entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented."
GROUP energyObjectMibEnergyParametersTableGroup
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. " configured with this MIB. The entPhysicalIndex,
entPhysicalName, and entPhysicalUris from [RFC4133]
MUST be implemented. "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMibTableGroup,
energyObjectMibStateTableGroup, energyObjectMibStateTableGroup,
energyObjectMibNotifGroup energyObjectMibNotifGroup
} }
OBJECT eoPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 54, line 4 skipping to change at page 62, line 9
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the PowerMonitor." related to the PowerMonitor."
::= { energyObjectMibGroups 1 } ::= { energyObjectMibGroups 1 }
energyObjectMibStateTableGroup OBJECT-GROUP energyObjectMibStateTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPowerStateMaxPower, eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier, eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime, eoPowerStateTotalTime,
eoPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the "This group contains the collection of all the
objects related to the Power State." objects related to the Power State."
::= { energyObjectMibGroups 2 } ::= { energyObjectMibGroups 2 }
energyObjectMibEnergyParametersTableGroup OBJECT-GROUP energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoEnergyObjectIndex,
eoEnergyParametersIndex,
eoEnergyParametersIntervalLength, eoEnergyParametersIntervalLength,
eoEnergyParametersIntervalNumber, eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode, eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow, eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate, eoEnergyParametersSampleRate,
eoEnergyParametersStatus eoEnergyParametersStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the configuration of the Energy Table." related to the configuration of the Energy Table."
::= { energyObjectMibGroups 3 } ::= { energyObjectMibGroups 3 }
energyObjectMibEnergyTableGroup OBJECT-GROUP energyObjectMibEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- eoEnergyIntervalStartTime is not -- eoEnergyCollectionStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
eoEnergyIntervalEnergyConsumed, eoEnergyConsumed,
eoEnergyIntervalEnergyProduced, eoEnergyProduced,
eoEnergyIntervalEnergyNet, eoEnergyNet,
eoEnergyIntervalEnergyUnitMultiplier, eoEnergyUnitMultiplier,
eoEnergyIntervalEnergyAccuracy, eoEnergyAccuracy,
eoEnergyIntervalMaxConsumed, eoEnergyMaxConsumed,
eoEnergyIntervalMaxProduced, eoEnergyMaxProduced,
eoEnergyIntervalDiscontinuityTime 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 }
energyObjectMibNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange eoPowerStateChange
skipping to change at page 55, line 35 skipping to change at page 64, line 9
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, eoPowerIndex UnitMultiplier
FROM ENERGY-OBJECT-MIB FROM ENERGY-OBJECT-MIB
OwnerString OwnerString
FROM RMON-MIB; FROM RMON-MIB
entPhysicalIndex
FROM ENTITY-MIB;
powerQualityMIB MODULE-IDENTITY powerQualityMIB MODULE-IDENTITY
LAST-UPDATED "201110310000Z" -- 31 October 2011 LAST-UPDATED "201203010000Z" -- 1 March 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:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
Archive: Archive:
http://www.ietf.org/mail-archive/web/eman http://www.ietf.org/mail-archive/web/eman
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
skipping to change at page 57, line 12 skipping to change at page 65, line 36
Degem 1831 Degem 1831
Belgium Belgium
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com" Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to report AC power quality in "This MIB is used to report AC power quality in
devices. The table is a sparse augmentation of the devices. The table is a sparse augmentation of the
eoPowerTable table from the energyObjectMib module. eoPowerTable table from the energyObjectMib module.
Both three-phase and single-phase power Both three-phase and single-phase power
configurations are supported." configurations are supported.
As a requirement for this MIB module,
[EMAN-AWARE-MIB] should be implemented and
three MIB objects from ENTITY-MIB (entPhysicalIndex,
entPhysicalName and entPhysicalUris) MUST be
implemented. "
REVISION REVISION
"201110310000Z" -- 31 October 2011 "201203010000Z" -- 1 March 2012
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerQualityMIBConform OBJECT IDENTIFIER powerQualityMIBConform OBJECT IDENTIFIER
::= { powerQualityMIB 0 } ::= { powerQualityMIB 0 }
powerQualityMIBObjects OBJECT IDENTIFIER powerQualityMIBObjects OBJECT IDENTIFIER
::= { powerQualityMIB 1 } ::= { powerQualityMIB 1 }
-- Objects -- Objects
eoACPwrQualityTable OBJECT-TYPE eoACPwrQualityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrQualityEntry SYNTAX SEQUENCE OF EoACPwrQualityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines power quality measurements for "This table defines power quality measurements for
supported eoPowerIndex entities. It is a sparse supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable." extension of the eoPowerTable."
::= { powerQualityMIBObjects 1 } ::= { powerQualityMIBObjects 1 }
eoACPwrQualityEntry OBJECT-TYPE eoACPwrQualityEntry OBJECT-TYPE
SYNTAX EoACPwrQualityEntry SYNTAX EoACPwrQualityEntry
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 quality measurements or
configuration. Each measured value corresponds to an configuration. Each measured value corresponds to an
attribute in IEC 61850-7-4 for non-phase measurements attribute in IEC 61850-7-4 for non-phase measurements
within the object MMUX." within the object MMUX."
INDEX { eoPowerIndex }
INDEX {entPhysicalIndex }
::= { eoACPwrQualityTable 1 } ::= { eoACPwrQualityTable 1 }
EoACPwrQualityEntry ::= SEQUENCE { EoACPwrQualityEntry ::= SEQUENCE {
eoACPwrQualityConfiguration INTEGER, eoACPwrQualityConfiguration INTEGER,
eoACPwrQualityAvgVoltage Integer32, eoACPwrQualityAvgVoltage Integer32,
eoACPwrQualityAvgCurrent Integer32, eoACPwrQualityAvgCurrent Integer32,
eoACPwrQualityFrequency Integer32, eoACPwrQualityFrequency Integer32,
eoACPwrQualityPowerUnitMultiplier UnitMultiplier, eoACPwrQualityPowerUnitMultiplier UnitMultiplier,
eoACPwrQualityPowerAccuracy Integer32, eoACPwrQualityPowerAccuracy Integer32,
eoACPwrQualityTotalActivePower Integer32, eoACPwrQualityTotalActivePower Integer32,
skipping to change at page 58, line 30 skipping to change at page 67, line 12
eoACPwrQualityTotalPowerFactor Integer32, eoACPwrQualityTotalPowerFactor Integer32,
eoACPwrQualityThdAmpheres Integer32, eoACPwrQualityThdAmpheres Integer32,
eoACPwrQualityThdVoltage Integer32 eoACPwrQualityThdVoltage Integer32
} }
eoACPwrQualityConfiguration OBJECT-TYPE eoACPwrQualityConfiguration OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
sngl(1), sngl(1),
del(2), del(2),
wye(3) wye(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configuration describes the physical configurations "Configuration describes the physical configurations
of the power supply lines: of the power supply lines:
* alternating current, single phase (SNGL) * alternating current, single phase (SNGL)
* alternating current, three phase delta (DEL) * alternating current, three phase delta (DEL)
* alternating current, three phase Y (WYE) * alternating current, three phase Y (WYE)
skipping to change at page 62, line 15 skipping to change at page 70, line 44
eoACPwrQualityPhaseEntry OBJECT-TYPE eoACPwrQualityPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrQualityPhaseEntry SYNTAX EoACPwrQualityPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes common 3-phase power quality "An entry describes common 3-phase power quality
measurements. measurements.
This optional table describes 3-phase power quality This optional table describes 3-phase power quality
measurements, with three entries for each supported measurements, with three entries for each supported
eoPowerIndex entity. Entities having single phase entPhysicalIndex entity. Entities having single phase
power shall not have any entities. power shall not have any entities.
This table describes attributes common to both WYE and This table describes attributes common to both WYE and
DEL. Entities having single phase power shall not have DEL. Entities having single phase power shall not have
any entries here. It is a sparse extension of the any entries here. It is a sparse extension of the
eoACPwrQualityTable. eoACPwrQualityTable.
These attributes correspond to IEC 61850-7.4 MMXU phase These attributes correspond to IEC 61850-7.4 MMXU phase
measurements." measurements."
INDEX { eoPowerIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrQualityPhaseTable 1 } ::= { eoACPwrQualityPhaseTable 1 }
EoACPwrQualityPhaseEntry ::= SEQUENCE { EoACPwrQualityPhaseEntry ::= SEQUENCE {
eoPhaseIndex Integer32, eoPhaseIndex Integer32,
eoACPwrQualityPhaseAvgCurrent Integer32, eoACPwrQualityPhaseAvgCurrent Integer32,
eoACPwrQualityPhaseActivePower Integer32, eoACPwrQualityPhaseActivePower Integer32,
eoACPwrQualityPhaseReactivePower Integer32, eoACPwrQualityPhaseReactivePower Integer32,
eoACPwrQualityPhaseApparentPower Integer32, eoACPwrQualityPhaseApparentPower Integer32,
eoACPwrQualityPhasePowerFactor Integer32, eoACPwrQualityPhasePowerFactor Integer32,
eoACPwrQualityPhaseImpedance Integer32 eoACPwrQualityPhaseImpedance Integer32
skipping to change at page 64, line 49 skipping to change at page 73, line 30
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 { eoPowerIndex, eoPhaseIndex} INDEX { entPhysicalIndex, eoPhaseIndex}
::= { eoACPwrQualityDelPhaseTable 1} ::= { eoACPwrQualityDelPhaseTable 1}
EoACPwrQualityDelPhaseEntry ::= SEQUENCE { EoACPwrQualityDelPhaseEntry ::= SEQUENCE {
eoACPwrQualityDelPhaseToNextPhaseVoltage Integer32, eoACPwrQualityDelPhaseToNextPhaseVoltage Integer32,
eoACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, eoACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32,
eoACPwrQualityDelThdCurrent Integer32 eoACPwrQualityDelThdCurrent Integer32
} }
eoACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 66, line 12 skipping to change at page 74, line 41
of the eoACPwrQualityPhaseTable." of the eoACPwrQualityPhaseTable."
::= { powerQualityMIBObjects 4 } ::= { powerQualityMIBObjects 4 }
eoACPwrQualityWyePhaseEntry OBJECT-TYPE eoACPwrQualityWyePhaseEntry OBJECT-TYPE
SYNTAX EoACPwrQualityWyePhaseEntry SYNTAX EoACPwrQualityWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes measurements of WYE configuration "This table describes measurements of WYE configuration
with phase to neutral power quality attributes. Three with phase to neutral power quality attributes. Three
entries are required for each supported eoPowerIndex entries are required for each supported entPhysicalIndex
entry. Voltage measurements are relative to neutral. entry. Voltage measurements are relative to neutral.
This is a sparse extension of the This is a sparse extension of the
eoACPwrQualityPhaseTable. eoACPwrQualityPhaseTable.
Each entry describes quality attributes of one phase of Each entry describes quality attributes of one phase of
a WYE 3-phase power system. a WYE 3-phase power system.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects." MHAI objects."
INDEX { eoPowerIndex, eoPhaseIndex }
INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrQualityWyePhaseTable 1} ::= { eoACPwrQualityWyePhaseTable 1}
EoACPwrQualityWyePhaseEntry ::= SEQUENCE { EoACPwrQualityWyePhaseEntry ::= SEQUENCE {
eoACPwrQualityWyePhaseToNeutralVoltage Integer32, eoACPwrQualityWyePhaseToNeutralVoltage Integer32,
eoACPwrQualityWyePhaseCurrent Integer32, eoACPwrQualityWyePhaseCurrent Integer32,
eoACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 eoACPwrQualityWyeThdPhaseToNeutralVoltage Integer32
} }
eoACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE eoACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 67, line 27 skipping to change at page 76, line 8
powerQualityMIBCompliances OBJECT IDENTIFIER powerQualityMIBCompliances OBJECT IDENTIFIER
::= { powerQualityMIB 2 } ::= { powerQualityMIB 2 }
powerQualityMIBGroups OBJECT IDENTIFIER powerQualityMIBGroups OBJECT IDENTIFIER
::= { powerQualityMIB 3 } ::= { powerQualityMIB 3 }
powerQualityMIBFullCompliance MODULE-COMPLIANCE powerQualityMIBFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for read- "When this MIB is implemented with support for read-create, then
create, then such an implementation can claim full such an implementation can claim full compliance. Such devices
compliance. Such devices can then be both monitored and can then be both monitored and configured with this MIB. The
configured with this MIB." entPhysicalIndex, entPhysicalName, and entPhysicalUris [RFC4133]
MUST be implemented."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerACPwrQualityMIBTableGroup, powerACPwrQualityMIBTableGroup
powerACPwrQualityPhaseMIBTableGroup }
}
GROUP powerACPwrQualityOptionalMIBTableGroup
DESCRIPTION
"A compliant implementation does not have
to implement."
GROUP powerACPwrQualityPhaseMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to
implement."
GROUP powerACPwrQualityDelPhaseMIBTableGroup GROUP powerACPwrQualityDelPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"This group must only be implemented for a DEL phase "A compliant implementation does not have to
configuration." implement."
GROUP powerACPwrQualityWyePhaseMIBTableGroup GROUP powerACPwrQualityWyePhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"This group must only be implemented for a WYE phase "A compliant implementation does not have to
configuration." implement."
::= { powerQualityMIBCompliances 1 } ::= { powerQualityMIBCompliances 1 }
-- Units of Conformance -- Units of Conformance
powerACPwrQualityMIBTableGroup OBJECT-GROUP powerACPwrQualityMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object eoPowerIndex is NOT -- Note that object entPhysicalIndex is
NOT
-- included since it is not-accessible -- included since it is not-accessible
eoACPwrQualityConfiguration,
eoACPwrQualityAvgVoltage, eoACPwrQualityAvgVoltage,
eoACPwrQualityAvgCurrent, eoACPwrQualityAvgCurrent,
eoACPwrQualityFrequency, eoACPwrQualityFrequency,
eoACPwrQualityPowerUnitMultiplier, eoACPwrQualityPowerUnitMultiplier,
eoACPwrQualityPowerAccuracy, eoACPwrQualityPowerAccuracy,
eoACPwrQualityTotalActivePower, eoACPwrQualityTotalActivePower,
eoACPwrQualityTotalReactivePower, eoACPwrQualityTotalReactivePower,
eoACPwrQualityTotalApparentPower, eoACPwrQualityTotalApparentPower,
eoACPwrQualityTotalPowerFactor, eoACPwrQualityTotalPowerFactor
} STATUS
current
DESCRIPTION
"This group contains the collection of all the power
quality objects related to the Energy Object."
::= { powerQualityMIBGroups 1 }
powerACPwrQualityOptionalMIBTableGroup OBJECT-GROUP
OBJECTS {
eoACPwrQualityConfiguration,
eoACPwrQualityThdAmpheres, eoACPwrQualityThdAmpheres,
eoACPwrQualityThdVoltage eoACPwrQualityThdVoltage
} STATUS current } STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
quality objects related to the Energy Object." quality objects related to the Energy Object."
::= { powerQualityMIBGroups 1 } ::= { powerQualityMIBGroups 2 }
powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object eoPowerIndex is NOT -- Note that object entPhysicalIndex is
NOT
-- included since it is not-accessible -- included since it is not-accessible
eoACPwrQualityPhaseAvgCurrent, eoACPwrQualityPhaseAvgCurrent,
eoACPwrQualityPhaseActivePower, eoACPwrQualityPhaseActivePower,
eoACPwrQualityPhaseReactivePower, eoACPwrQualityPhaseReactivePower,
eoACPwrQualityPhaseApparentPower, eoACPwrQualityPhaseApparentPower,
eoACPwrQualityPhasePowerFactor, eoACPwrQualityPhasePowerFactor,
eoACPwrQualityPhaseImpedance eoACPwrQualityPhaseImpedance
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all 3-phase power "This group contains the collection of all 3-phase power
quality objects related to the Power State." quality objects related to the Power State."
::= { powerQualityMIBGroups 2 } ::= { powerQualityMIBGroups 3 }
powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object eoPowerIndex 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 , eoACPwrQualityDelPhaseToNextPhaseVoltage ,
eoACPwrQualityDelThdPhaseToNextPhaseVoltage, eoACPwrQualityDelThdPhaseToNextPhaseVoltage,
eoACPwrQualityDelThdCurrent eoACPwrQualityDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all quality "This group contains the collection of all quality
attributes of a phase in a DEL 3-phase power system." attributes of a phase in a DEL 3-phase power system."
::= { powerQualityMIBGroups 3 } ::= { powerQualityMIBGroups 4 }
powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object eoPowerIndex 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, eoACPwrQualityWyePhaseToNeutralVoltage,
eoACPwrQualityWyePhaseCurrent, eoACPwrQualityWyePhaseCurrent,
eoACPwrQualityWyeThdPhaseToNeutralVoltage eoACPwrQualityWyeThdPhaseToNeutralVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all WYE "This group contains the collection of all WYE
configuration phase-to-neutral power quality configuration phase-to-neutral power quality
measurements." measurements."
::= { powerQualityMIBGroups 4 } ::= { powerQualityMIBGroups 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 72, line 27 skipping to change at page 81, line 35
(IANA) has created a new registry for EMAN Power State Set (IANA) has created a new registry for EMAN Power State Set
identifiers and filled it with the initial list in the Textual identifiers and filled it with the initial list in the Textual
Convention IANAPowerStateSet. Convention IANAPowerStateSet.
New assignments (or potentially deprecation) for EMAN Power New assignments (or potentially deprecation) for EMAN Power
State Set will be administered by IANA through Expert Review State Set will be administered by IANA through Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested state for completeness and accuracy of the requested state for completeness and accuracy of the
description. description.
12.3. Updating the Registration of Existing Power State Sets
IANA maintains a Textual Convention IANAPowerStateSet with the
initial set of Power State Sets and the Power States within
those Power State Sets. The current version of Textual
convention can be accessed
http://www.iana.org/assignments/IANAPowerStateSet
With the evolution of standards, over time, it may be important
to deprecate of some of the existing the Power State Sets or
some of the states within a Power State Set.
The registrant shall publish an Internet-draft or an individual
submission with the clear specification on deprecation of Power
State Sets or Power States registered with IANA. The
deprecation shall be administered by IANA through Expert Review
[RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The process should also allow for a
mechanism for cases where others have significant objections to
claims on deprecation of a registration. In cases, where the
registrant cannot be reached, IESG can designate an Expert to
modify the IANA registry for the deprecation.
12. Contributors 12. Contributors
This document results from the merger of two initial proposals. This document results from the merger of two initial proposals.
The following persons made significant contributions either in The following persons made significant contributions either in
one of the initial proposals or in this document. one of the initial proposals or in this document.
John Parello John Parello
Rolf Winter Rolf Winter
Dominique Dudkowski Dominique Dudkowski
13. Acknowledgment 13. Acknowledgment
The authors would like to thank Shamita Pisal for her prototype The authors would like to thank Shamita Pisal for her prototype
of this MIB module, and her valuable feedback. The authors of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically. would like to Michael Brown for improving the text dramatically.
We would like to thank Juergen Schoenwalder for proposing the 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. McDonald for his feedback. Thanks for the many comments on the
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 Double-check all the IEC references in the draft.
IEC 61850-7-4 has been widely referenced in many EMAN drafts. IEC 61850-7-4 has been widely referenced in many EMAN drafts.
The other IEC references suggested in the email list are The other IEC references suggested in the email list are
IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is
important to resolve the correct IEC references soon. important to resolve the correct IEC references soon.
OPEN ISSUE 2 : Description clause of eoPowerIndex. Do we need OPEN ISSUE 2 Light weight identification of a device
this text ? Juergen Quittek to comment:
"The identity provisioning method that has been chosen can be "The identity provisioning method that has been chosen can be
retrieved by reading the value of powerStateEnergyConsumerOid. retrieved by reading the value of powerStateEnergyConsumerOid.
In case of identities provided by the ENERGY-AWARE-MIB module, In case of identities provided by the ENERGY-AWARE-MIB module,
this OID points to an exising instance of eoPowerIndex, in this OID points to an exising instance of eoPowerIndex, in
case of the ENTITY MIB, the object points to a valid instance case of the ENTITY-MIB, the object points to a valid instance
of entPhysicalIndex, and in a similar way, it points to a of entPhysicalIndex, and in a similar way, it points to a
value of another MIB module if this is used for identifying value of another MIB module if this is used for identifying
entities. If no other MIB module has been chosen for providing entities. If no other MIB module has been chosen for providing
entity identities, then the value of entity identities, then the value of
powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero). powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero).
OPEN ISSUE 3: Time Series of measurements required ? Mechanism OPEN ISSUE 3 Demand computation method
pull or push ? What shall the table consist of ?
Power, Voltage, Current, Energy and Demand.
OPEN ISSUE 4: Demand computation method
"Energy not obtained by periodically polling a power "Energy not obtained by periodically polling a power
measurement with a eoEnergyParametersSampleRate ; Energy (E) measurement with a eoEnergyParametersSampleRate ; Energy (E)
is measured to the product's certified IEC 62053-21 accuracy is measured to the product's certified IEC 62053-21 accuracy
class" class"
Need to verify with IEC62053-21. Need to verify with IEC62053-21.
OPEN ISSUE 5: Consideration of IEEE-ISTO PWG in the IANA list of 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 6: check if all the requirements from [EMAN-REQ] are OPEN ISSUE 5 check if all the requirements from [EMAN-REQ] are
covered. covered.
OPEN ISSUE 6 IANA Registered Power State Sets deferred to [EMAN-
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 74, line 43 skipping to change at page 84, 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-02 ", work in progress, July 2011. energy-aware-mib-04 ", work in progress, February 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 75, line 30 skipping to change at page 85, line 22
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 Management M. Chandramouli, " Requirements for Energy Managemen",
", draft-ietf-eman-requirements-03 (work in draft-ietf-eman-requirements-05, November 2011.
progress),July 2011. .
[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-02 , July 2011. eman-framework-03, October 2011.
[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-claise-energy-monitoring-mib-09, July MIB ", draft-eman-ietf-energy-monitoring-mib-01,
2011. October 2011.
[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-
tychon-eman-applicability-statement-02, work in ietf-eman-applicability-statement-00, December 2011.
progress, June 2011.
[EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology",
draft-parello-eman-definitions-04, work in progress,
December 2011.
[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. 229 change blocks. 
564 lines changed or deleted 981 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/