draft-ietf-eman-energy-monitoring-mib-07.txt   draft-ietf-eman-energy-monitoring-mib-08.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
B. Claise
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: April 21, 2014 Independent Consultant Expires: June 13, 2014 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
B. Claise December 13, 2013
Cisco Systems, Inc.
October 21, 2013
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-07 draft-ietf-eman-energy-monitoring-mib-08
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 38
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 April 2014. This Internet-Draft will expire on June 2014.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided in Section 4.e of the Trust Legal Provisions and are provided
skipping to change at page 2, line 34 skipping to change at page 2, line 34
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED"
"MAY", and "OPTIONAL" in this document are to be interpreted as "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119]. described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction.............................................. 3 1. Introduction............................................. 3
2. The Internet-Standard Management Framework................ 4 2. The Internet-Standard Management Framework............... 4
3. Use Cases................................................. 4 3. Use Cases................................................ 4
4. Terminology............................................... 5 4. Terminology.............................................. 4
5. Architecture Concepts Applied to the MIB Module........... 6 5. Architecture Concepts Applied to the MIB Modules......... 5
5.1. Energy Object Information.............................. 13 5.1. Energy Object Information............................. 12
5.2. Power State............................................ 14 5.2. Power State........................................... 13
5.2.1. Power State Set................................ 15 5.2.1. Power State Set................................14
5.3. Energy Object Usage Information........................ 15 5.3. Energy Object Usage Information....................... 14
5.4. Optional Power Usage Attributes........................ 16 5.4. Optional Power Usage Attributes....................... 15
5.5. Optional Energy Measurement............................ 17 5.5. Optional Energy Measurement........................... 15
5.6. Fault Management....................................... 21 5.6. Fault Management...................................... 19
6. Discovery................................................ 21 6. Discovery............................................... 20
7. Link with the other IETF MIBs............................ 22 7. Link with the other IETF MIBs........................... 21
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB...22 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..21
7.2. Link with the ENTITY-STATE MIB.......................23 7.2. Link with the ENTITY-STATE MIB......................22
7.3. Link with the POWER-OVER-ETHERNET MIB................24 7.3. Link with the POWER-OVER-ETHERNET MIB...............22
7.4. Link with the UPS MIB................................25 7.4. Link with the UPS MIB...............................23
7.5. Link with the LLDP and LLDP-MED MIBs.................26 7.5. Link with the LLDP and LLDP-MED MIBs................24
8. Implementation Scenario.................................. 26 8. Implementation Scenario................................. 25
9. Structure of the MIB..................................... 29 9. Structure of the MIB.................................... 27
10. MIB Definitions......................................... 30 10. MIB Definitions........................................ 28
11. Implementation Status................................... 70 11. Implementation Status.................................. 69
11.1. SNMP Research......................................... 71 11.1. SNMP Research........................................ 70
11.2. Cisco Systems......................................... 71 11.2. Cisco Systems........................................ 70
12. Security Considerations................................. 72 12. Security Considerations................................ 71
13. IANA Considerations..................................... 73 13. IANA Considerations.................................... 72
13.1. IANA Considerations for the MIB Modules............... 73 14. Contributors........................................... 73
13.2. IANA Registration of new Power State Set.............. 73 12. Acknowledgment......................................... 73
13.2.1. IANA Registration of the IEEE1621 Power State Set..74 13. References............................................. 74
13.2.2. IANA Registration of the DMTF Power State Set......74 13.1. Normative References...............................74
13.2.3. IANA Registration of the EMAN Power State Set......74 13.2. Informative References.............................75
13.3. Updating the Registration of Existing Power State
Sets........................................................ 74
12. Contributors............................................ 75
13. Acknowledgment.......................................... 75
14. Open Issues............................................. 75
15. References.............................................. 76
15.2. Normative References............................... 76
15.3. Informative References............................. 76
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-FMWK], which in turn, is based on the Management Framework [EMAN-FMWK], which in turn, is based on the
Requirements for Energy Management [EMAN-REQ]. Requirements for Energy Management [RFC6988].
Energy management is applicable to devices in communication Energy management is applicable to devices in communication
networks. Target devices for this specification include (but networks. Target devices for this specification include (but are
are not limited to): routers, switches, Power over Ethernet not limited to): routers, switches, Power over Ethernet (PoE)
(PoE) endpoints, protocol gateways for building management endpoints, protocol gateways for building management systems,
systems, intelligent meters, home energy gateways, hosts and intelligent meters, home energy gateways, hosts and servers,
servers, sensor proxies, etc. Target devices and the use cases sensor proxies, etc. Target devices and the use cases for Energy
for Energy Management are discussed in Energy Management Management are discussed in Energy Management Applicability
Applicability Statement [EMAN-AS]. Statement [EMAN-AS].
Where applicable, device monitoring extends to the individual Where applicable, device monitoring extends to the individual
components of the device and to any attached dependent devices. components of the device and to any attached dependent devices.
For example: A device can contain components that are For example: A device can contain components that are
independent from a power-state point of view, such as line independent from a power-state point of view, such as line
cards, processor cards, hard drives. A device can also have cards, processor cards, hard drives. A device can also have
dependent attached devices, such as a switch with PoE endpoints dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints. or a power distribution unit with attached endpoints.
Devices and their sub-components can be modeled using the
containment tree of the ENTITY-MIB [RFC6933]. In addition,
ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] provides a framework
for modeling the relationship between Energy Objects. It is
conceivable to have implementations of ENERGY-AWARE-MIB and
ENERGY-OBJECT-MIB for modeling the relationships between Energy
Objects and also monitoring the Energy consumption. In some
situations, it is possible to have implementation of ENERGY-
OBJECT-MIB along with the requirement of Module Compliance of
ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance
should be supported which requires 3 MIB objects
(entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be
implemented.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please refer to current Internet-Standard Management Framework, please refer to
section 7 of RFC 3410 [RFC3410]. section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. MIB objects are termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management generally accessed through the Simple Network Management
Protocol (SNMP). Objects in the MIB are defined using the Protocol (SNMP). Objects in the MIB are defined using the
mechanisms defined in the Structure of Management Information mechanisms defined in the Structure of Management Information
(SMI). This memo specifies MIB modules that are compliant to (SMI). This memo specifies MIB modules that are compliant to
SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58,
RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
3. Use Cases 3. Use Cases
Requirements for power and energy monitoring for networking Requirements for power and energy monitoring for networking
devices are specified in [EMAN-REQ]. The requirements in [EMAN- devices are specified in [RFC6988]. The requirements in
REQ] cover devices typically found in communications networks, [RFC6988] cover devices typically found in communications
such as switches, routers, and various connected endpoints. For networks, such as switches, routers, and various connected
a power monitoring architecture to be useful, it should also endpoints. For a power monitoring architecture to be useful, it
apply to facility meters, power distribution units, gateway should also apply to facility meters, power distribution units,
proxies for commercial building control, home automation gateway proxies for commercial building control, home automation
devices, and devices that interface with the utility and/or devices, and devices that interface with the utility and/or
smart grid. Accordingly, the scope of the MIB modules in this smart grid. Accordingly, the scope of the MIB modules in this
document is broader than that specified in [EMAN-REQ]. Several document is broader than that specified in [RFC6988]. Several
use cases for Energy Management have been identified in the use cases for Energy Management have been identified in the
"Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An
illustrative example scenario is presented in Section 8. illustrative example scenario is presented in Section 8.
4. Terminology 4. Terminology
Please refer to [EMAN-FMWK] for the definitions of the Please refer to [EMAN-FMWK] for the definitions of the
following terminology used in this draft. following terminology used in this draft.
Device Energy Management
Component
Energy Management
Energy Management System (EnMS)
ISO Energy Management System
Energy
Power
Demand
Power Attributes
Electrical Equipment
Non-Electrical Equipment (Mechanical Equipment)
Energy Object
Electrical Energy Object Energy Management System (EnMS)
Energy Monitoring
Non-Electrical Energy Object Energy Control
Energy Monitoring electrical equipment
Energy Control non-electrical equipment (mechanical equipment)
Provide Energy:
Receive Energy: device
Power Interface component
Power Inlet power inlet
Power Outlet power outlet
Energy Management Domain energy
Energy Object Identification power
Energy Object Context demand
Energy Object Relationship provide energy
Aggregation Relationship receive energy
Metering Relationship meter (energy meter)
Power Source Relationship battery
Proxy Relationship Power Interface
Energy Object Parent Nameplate Power
Energy Object Child Power Attributes
Power State Power Quality
Power State Set Power State
Nameplate Power Power State Set
5. Architecture Concepts Applied to the MIB Module 5. Architecture Concepts Applied to the MIB Modules
This section describes the concepts specified in the Energy This section describes the concepts specified in the Energy
Management Framework [EMAN-FMWK] that pertain to power usage, Management Framework [EMAN-FMWK] that pertain to power usage,
with specific information related to the MIB module specified in with specific information related to the MIB module specified in
this document. This subsection maps to the section this document. This subsection maps to the different concepts
"Architecture High Level Concepts" in the Power Monitoring developed in the Energy Management Framework [EMAN-FMWK].
Architecture [EMAN-FMWK].
The Energy Monitoring MIB has 2 independent MIB modules. The The Energy Monitoring MIB has 2 independent MIB modules ENERGY-
first MIB module energyObjectMib is focused on measurement of OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first MIB module
power and energy. The second MIB module powerCharMIB is focused ENERGY-OBJECT-MIB is focused on measurement of power and energy.
on Power Attributes measurements. The second MIB module POWER-ATTRIBUTES-MIB is focused on Power
Attributes measurements for Energy Objects.
The energyObjectMib MIB module consists of five tables. Devices and their sub-components can be modeled using the
containment tree of the ENTITY-MIB [RFC6933]. In addition,
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB] provides a
framework for modeling the relationship between Energy Objects.
It is conceivable to have implementations of ENERGY-OBJECT-
CONTEXT-MIB and ENERGY-OBJECT-MIB for modeling the relationships
between Energy Objects and also monitoring the Energy
consumption of those Energy Objects. In some situations, it is
possible to have implementation of ENERGY-OBJECT-MIB along
ENTITY-MIB V4 [RFC6933] with the Module compliance of
entity4CRCompliance. This compliance requires that the
following 3 MIB objects from ENTITY-MIB [RFC6933]
(entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be
implemented.
The ENERGY-OBJECT-MIB MIB module consists of five tables.
The first table is the eoMeterCapabilitiesTable. It indicates The first table is the eoMeterCapabilitiesTable. It indicates
the instrumentation available for each energy object. Thus, the the instrumentation available for each Energy Object. Thus, the
entries in this table indicate to the EnMS which other tables entries in this table indicate to the EnMS which other tables
from the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are from the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are
available for each energy object. The eoMeterCapabilitiesTable available for each Energy Object. The eoMeterCapabilitiesTable
is indexed by entPhysicalIndex. is indexed by entPhysicalIndex [RFC6933].
The second table is the eoPowerTable. It returns the power The second table is the eoPowerTable. It returns the power
consumption of each energy object, as well as the units, sign, consumption of each Energy Object, as well as the units, sign,
measurement accuracy, and related objects. The eoPowerTable is measurement accuracy, and related objects. The eoPowerTable is
indexed by entPhysicalIndex. indexed by entPhysicalIndex.
The third table is the eoPowerStateTable. For each energy The third table is the eoPowerStateTable. For each Energy
object, it provides information and statistics about the Object, it provides information and statistics about the
supported power states. The eoPowerStateTable is indexed by supported Power States. The eoPowerStateTable is indexed by
entPhysicalIndex and eoPowerStateIndex. entPhysicalIndex and eoPowerStateIndex.
The fourth table is the eoEnergyParametersTable. The entries in The fourth table is the eoEnergyParametersTable. The entries in
this table configure the parameters of energy and demand this table configure the parameters of energy and demand
measurement collection. This table is indexed by measurement collection. This table is indexed by
eoEnergyParametersIndex. eoEnergyParametersIndex.
The fifth table is the eoEnergyTable. The entries in this table The fifth table is the eoEnergyTable. The entries in this table
provide the log the energy and demand information. This table provide the log the energy and demand information. This table
is indexed by eoEnergyParametersIndex. is indexed by eoEnergyParametersIndex.
skipping to change at page 8, line 18 skipping to change at page 7, line 36
| +-- r-n INTEGER eoPowerOrigin(7) | +-- r-n INTEGER eoPowerOrigin(7)
| +-- rwn IANAPowerStateSet eoPowerAdminState(8) | +-- rwn IANAPowerStateSet eoPowerAdminState(8)
| +-- r-n IANAPowerStateSet eoPowerOperState(9) | +-- r-n IANAPowerStateSet eoPowerOperState(9)
| +-- r-n OwnerString eoPowerStateEnterReason(10) | +-- r-n OwnerString eoPowerStateEnterReason(10)
| |
| |
+---eoPowerStateTable(3) +---eoPowerStateTable(3)
| +--eoPowerStateEntry(1) | +--eoPowerStateEntry(1)
| | [entPhysicalIndex, eoPowerStateIndex] | | [entPhysicalIndex, eoPowerStateIndex]
| | | |
| +-- --n IANAPowerStateSet eoPowerStateIndex(1) | +-- --n IANAPowerStateSet eoPowerStateIndex(1)
| +-- r-n Interger32 eoPowerStateMaxPower (2) | +-- r-n Interger32 eoPowerStateMaxPower(2)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoPowerStatePowerUnitMultiplier (3) | eoPowerStatePowerUnitMultiplier(3)
| +-- r-n TimeTicks eoPowerStateTotalTime(4) | +-- r-n TimeTicks eoPowerStateTotalTime(4)
| +-- r-n Counter32 eoPowerStateEnterCount(5) | +-- r-n Counter32 eoPowerStateEnterCount(5)
| |
+eoEnergyParametersTable(4) +eoEnergyParametersTable(4)
+---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
| |
| +-- --n PhysicalIndex eoEnergyObjectIndex(1)
| +-- --n PhysicalIndex eoEnergyObjectIndex (1) | + r-n Integer32 eoEnergyParametersIndex(2)
| + r-n Integer32 eoEnergyParametersIndex (2) | +-- r-n TimeInterval eoEnergyParametersIntervalLength(3)
| +-- r-n TimeInterval | +-- r-n Integer32 eoEnergyParametersIntervalNumber(4)
| eoEnergyParametersIntervalLength (3) | +-- r-n Integer32 eoEnergyParametersIntervalMode(5)
| +-- r-n Integer32 | +-- r-n TimeInterval eoEnergyParametersIntervalWindow(6)
| eoEnergyParametersIntervalNumber (4) | +-- r-n Integer32 eoEnergyParametersSampleRate(7)
| +-- r-n Integer32 | +-- r-n RowStatus eoEnergyParametersStatus(8)
| eoEnergyParametersIntervalMode (5)
| +-- r-n TimeInterval
| eoEnergyParametersIntervalWindow (6)
| +-- r-n Integer32
| eoEnergyParametersSampleRate (7)
| +-- r-n RowStatus eoEnergyParametersStatus (8)
| |
+eoEnergyTable(5) +eoEnergyTable(5)
+---eoEnergyEntry(1) [ eoEnergyParametersIndex, +---eoEnergyEntry(1)
eoEnergyCollectionStartTime] | [eoEnergyParametersIndex,eoEnergyCollectionStartTime]
| |
| +-- r-n TimeTicks eoEnergyCollectionStartTime (1) | +-- r-n TimeTicks eoEnergyCollectionStartTime(1)
| +-- r-n Integer32 eoEnergyConsumed (2) | +-- r-n Integer32 eoEnergyConsumed(2)
| +-- r-n Integer32 eoEnergyProvided (3) | +-- r-n Integer32 eoEnergyProvided(3)
| +-- r-n Integer32 eoEnergyStored (4) | +-- r-n Integer32 eoEnergyStored(4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5)
| eoEnergyUnitMultiplier (5) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyMaxConsumed(7)
| +-- r-n Integer32 eoEnergyMaxConsumed (7) | +-- r-n Integer32 eoEnergyMaxProduced(8)
| +-- r-n Integer32 eoEnergyMaxProduced (8) | +-- r-n TimeTicks eoEnergyDiscontinuityTime(9)
| +-- r-n TimeTicks
| eoEnergyDiscontinuityTime(9)
The powerAttributesMIB consists of four tables. The powerAttributesMIB consists of four tables.
eoACPwrAttributesTable is indexed by entPhysicalIndex. eoACPwrAttributesTable is indexed by entPhysicalIndex.
eoACPwrAttributesPhaseTable is indexed by entPhysicalIndex and eoACPwrAttributesPhaseTable is indexed by entPhysicalIndex and
eoPhaseIndex. eoACPwrAttributesWyePhaseTable and eoPhaseIndex. eoACPwrAttributesWyePhaseTable and
eoACPwrAttributesDelPhaseTable are indexed by entPhysicalIndex eoACPwrAttributesDelPhaseTable are indexed by entPhysicalIndex
and eoPhaseIndex. and eoPhaseIndex.
eoACPwrAttributesTable(1) eoACPwrAttributesTable(1)
| |
+---eoACPwrAttributesEntry(1) [ entPhysicalIndex] +---eoACPwrAttributesEntry(1) [ entPhysicalIndex]
| | | |
| | | +---r-n INTEGER eoACPwrAttributesConfiguration(1)
| +---r-n INTEGER eoACPwrAttributesConfiguration (1) | +-- r-n Interger32 eoACPwrAttributesAvgVoltage(2)
| +-- r-n Interger32 eoACPwrAttributesAvgVoltage (2) | +-- r-n Integer32 eoACPwrAttributesAvgCurrent(3)
| +-- r-n Integer32 eoACPwrAttributesAvgCurrent (3) | +-- r-n Integer32 eoACPwrAttributesFrequency(4)
| +-- r-n Integer32 eoACPwrAttributesFrequency (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoACPwrAttributesPowerUnitMultiplier (5) | eoACPwrAttributesPowerUnitMultiplier(5)
| +-- r-n Integer32 eoACPwrAttributesPowerAccuracy (6) | +-- r-n Integer32 eoACPwrAttributesPowerAccuracy(6)
| +-- r-n Interger32 | +-- r-n Interger32
eoACPwrAttributesTotalActivePower (7) | eoACPwrAttributesTotalActivePower(7)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrAttributesTotalReactivePower (8) | eoACPwrAttributesTotalReactivePower(8)
| +-- r-n Integer32 | +-- r-n Integer32
eoACPwrAttributesTotalApparentPower (9) | eoACPwrAttributesTotalApparentPower(9)
| +-- r-n Integer32 | +-- r-n Integer32
eoACPwrAttributesTotalPowerFactor (10) | eoACPwrAttributesTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrAttributesThdAmpheres (11) | +-- r-n Integer32 eoACPwrAttributesThdAmpheres(11)
| |
+eoACPwrAttributesPhaseTable(2) +eoACPwrAttributesPhaseTable(2)
+---EoACPwrAttributesPhaseEntry(1)[ entPhysicalIndex, +---EoACPwrAttributesPhaseEntry(1)
| | eoPhaseIndex] | | [ entPhysicalIndex, eoPhaseIndex]
| | | |
| +-- r-n Integer32 eoPhaseIndex (1) | +-- r-n Integer32 eoPhaseIndex(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseAvgCurrent (2) | | eoACPwrAttributesPhaseAvgCurrent(2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseActivePower (3) | | eoACPwrAttributesPhaseActivePower(3)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseReactivePower (4) | | eoACPwrAttributesPhaseReactivePower(4)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseApparentPower (5) | | eoACPwrAttributesPhaseApparentPower(5)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhasePowerFactor (6) | | eoACPwrAttributesPhasePowerFactor(6)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseImpedance (7) | | eoACPwrAttributesPhaseImpedance(7)
| | | |
+eoACPwrAttributesDelPhaseTable(3) +eoACPwrAttributesDelPhaseTable(3)
+-- eoACPwrAttributesDelPhaseEntry(1) +-- eoACPwrAttributesDelPhaseEntry(1)
| | [entPhysicalIndex, | | [entPhysicalIndex, eoPhaseIndex]
| | eoPhaseIndex] | |
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage (1) | | eoACPwrAttributesDelPhaseToNextPhaseVoltage(1)
| +-- r-n Integer32 | +-- r-n Integer32
| |eoACPwrAttributesDelThdPhaseToNextPhaseVoltage (2) | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(2)
| +-- r-n Integer32 | +-- r-n Integer32
eoACPwrAttributesDelThdCurrent (3) eoACPwrAttributesDelThdCurrent(3)
| | | |
+eoACPwrAttributesWyePhaseTable(4) +eoACPwrAttributesWyePhaseTable(4)
+-- eoACPwrAttributesWyePhaseEntry(1) +-- eoACPwrAttributesWyePhaseEntry(1)
| | [entPhysicalIndex, | | [entPhysicalIndex, eoPhaseIndex]
| | eoPhaseIndex] | |
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyePhaseToNeutralVoltage (1) | | eoACPwrAttributesWyePhaseToNeutralVoltage(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyePhaseCurrent (2) | | eoACPwrAttributesWyePhaseCurrent(2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyeThdPhaseToNeutralVoltage (3) | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage(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 powerAttributesMIB are presented. ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are presented.
+-------------------------+ +-------------------------+
| Energy Object State | | Energy Object State |
| ----------------------- | | ----------------------- |
| eoPowerAdminState | | eoPowerAdminState |
| eoPowerOperState | | eoPowerOperState |
| eoPowerStateEnterReason | | eoPowerStateEnterReason |
+-------------------------+ +-------------------------+
| |
| |
skipping to change at page 11, line 38 skipping to change at page 10, line 45
| |
| +---------------------------------+ | +---------------------------------+
|---- | Energy Object State Statistics | |---- | Energy Object State Statistics |
|-------------------------------- | |-------------------------------- |
| eoPowerStateMaxPower | | eoPowerStateMaxPower |
| eoPowerStatePowerUnitMultiplier | | eoPowerStatePowerUnitMultiplier |
| eoPowerStateTotalTime | | eoPowerStateTotalTime |
| eoPowerStateEnterCount | | eoPowerStateEnterCount |
+---------------------------------+ +---------------------------------+
Figure 1:UML diagram for energyObjectMib Figure 1:UML diagram for energyObjectMIB
(*) Compliance with the ENERGY-AWARE-MIB (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
+----------------------------------+ +----------------------------------+
| Energy ParametersTable | | Energy ParametersTable |
| -------------------------------- | | -------------------------------- |
| eoEnergyObjectIndex | | eoEnergyObjectIndex |
| eoEnergyParametersIndex | | eoEnergyParametersIndex |
| eoEnergyParametersIntervalLength | | eoEnergyParametersIntervalLength |
| eoEnergyParametersIntervalNumber | | eoEnergyParametersIntervalNumber |
| eoEnergyParametersIntervalMode | | eoEnergyParametersIntervalMode |
| eoEnergyParametersIntervalWindow | | eoEnergyParametersIntervalWindow |
skipping to change at page 13, line 24 skipping to change at page 12, line 31
| |
| |
| +------------------------------------------------+ | +------------------------------------------------+
|---- | AC Input DEL Configuration | |---- | AC Input DEL Configuration |
| | ---------------------------------------------- | | | ---------------------------------------------- |
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdCurrent | | | eoACPwrAttributesDelThdCurrent |
| +------------------------------------------------+ | +------------------------------------------------+
| |
|
| +----------------------------------------------+ | +----------------------------------------------+
|---- | AC Input WYE Configuration | |---- | AC Input WYE Configuration |
| ---------------------------------------------| | -------------------------------------------- |
| eoACPwrAttributesWyePhaseToNeutralVoltage | | eoACPwrAttributesWyePhaseToNeutralVoltage |
| eoACPwrAttributesWyePhaseCurrent | | eoACPwrAttributesWyePhaseCurrent |
| eoACPwrAttributesWyeThdPhaseToNeutralVoltage | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage |
+----------------------------------------------+ +----------------------------------------------+
Figure 2: UML diagram for the powerAttributesMIB Figure 2: UML diagram for the powerAttributesMIB
(*) Compliance with the ENERGY-AWARE-MIB (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
5.1. Energy Object Information 5.1. Energy Object Information
Refer to the "Energy Object Information" section in [EMAN-FMWK] The Energy Object identity information is specified in the
for background information. An energy aware device is ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB] primary
considered as an instance of a Energy Object as defined in the table, i.e. the eoTable. In this table, the context of the
[EMAN-FMWK]. Energy Object such as domain, role description, importance are
specified. In addition, the ENERGY-OBJECT-CONTEXT-MIB module
The Energy Object identity information is specified in the MIB specifies the relationship between Energy Objects. There are
ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the several possible relationships between Energy Objects such as
eoTable. In this table, the context of the Energy Object such as meteredBy, metering, poweredBy, powering, aggregatedBy, and
Domain, RoleDescription, Importance are specified. In addition, aggregating as defined in the IANA-ENERGY-RELATION-MIB MIB
the ENERGY-AWARE-MIB module returns the relationship between module [EMAN-AWARE-MIB].
Objects. There are several possible relationships between Parent
and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy,
PoweredBy, and AggregatedBy.
5.2. Power State 5.2. Power State
Refer to the "Power States" section in [EMAN-FMWK] for
background information.
An Energy Object may have energy conservation modes called Power An Energy Object may have energy conservation modes called Power
States. Between the ON and OFF states of a device, there can be States. Between the ON and OFF states of a device, there can be
several intermediate energy saving modes. Those energy saving several intermediate energy saving modes. Those energy saving
modes are called as Power States. modes are called as Power States.
Power States, which represent universal states of power Power States, which represent universal states of power
management of an Energy Object, are specified by the management of an Energy Object, are specified by the
eoPowerState MIB object. The actual Power State is specified by eoPowerState MIB object. The actual Power State is specified by
the eoPowerOperState MIB object, while the eoPowerAdminState MIB the eoPowerOperState MIB object, while the eoPowerAdminState MIB
object specifies the Power State requested for the Energy object specifies the Power State requested for the Energy
Object. The difference between the values of eoPowerOperState Object. The difference between the values of eoPowerOperState
and eoPowerAdminState can be attributed that the Energy Object and eoPowerAdminState can be attributed that the Energy Object
is busy transitioning from eoPowerAdminState into the is busy transitioning from eoPowerAdminState into the
eoPowerOperState, at which point it will update the content of eoPowerOperState, at which point it will update the content of
eoPowerOperState. In addition, the possible reason for change eoPowerOperState. In addition, the possible reason for change
in Power State is reported in eoPowerStateEnterReason. in Power State is reported in eoPowerStateEnterReason.
Regarding eoPowerStateEnterReason, management stations and Regarding eoPowerStateEnterReason, management stations and
Energy Objects should support any format of the owner string Energy Objects should support any format of the owner string
dictated by the local policy of the organization. It is dictated by the local policy of the organization. It is
suggested that this name contain at least the reason for the suggested that this name contain at least the reason for the
transition change, and one or more of the following: IP address, transition change, and one or more of the following: IP address,
management station name, network manager's name, location, or management station name, network manager's name, location, or
phone number. phone number.
The MIB objects eoPowerOperState, eoPowerAdminState , and The MIB objects eoPowerOperState, eoPowerAdminState , and
eoPowerStateEnterReason are contained in the eoPowerTable MIB eoPowerStateEnterReason are contained in the eoPowerTable MIB
table. table.
The eoPowerStateTable table enumerates the maximum power usage The eoPowerStateTable table enumerates the maximum power usage
in watts, for every single supported Power State of each Power in watts, for every single supported Power State of each Power
State Set supported by the Energy Object. In addition, State Set supported by the Energy Object. In addition,
PowerStateTable provides additional statistics: PowerStateTable provides additional statistics:
eoPowerStateEnterCount, the number of times an entity has eoPowerStateEnterCount, the number of times an entity has
visited a particular Power State, and eoPowerStateTotalTime, the visited a particular Power State, and eoPowerStateTotalTime, the
total time spent in a particular Power State of an Energy total time spent in a particular Power State of an Energy
Object. Object.
5.2.1. Power State Set 5.2.1. Power State Set
There are several standards and implementations of Power State There are several standards and implementations of Power State
Sets. A Energy Object can support one or multiple Power State Sets. An 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) IEEE1621 - [IEEE1621]
IEEE1621(256) - [IEEE1621] DMTF - [DMTF]
DMTF(512) - [DMTF] EMAN - [EMAN-FMWK]
EMAN(1024) - [EMAN-MONITORING-MIB]
The respective specific states related to each Power State Set
are specified in the following sections. The guidelines for
addition of new Power State Sets have been specified in the IANA
Considerations Section.
The Power States within each Power State Set are listed in The Power State Sets, along with each Power State within the
[EMAN-FMWK]. The Textual Convention IANAPowerStateSet provides Power Set are listed in [EMAN-FMWK].
the proposed numbering of the Power States within the IEEE1621
Power State Set, DMTF Power State Set and the EMAN Power State
Set.
5.3. Energy Object Usage Information 5.3. Energy Object Usage Information
Refer to the "Energy Object Usage Measurement" section in [EMAN-
FMWK] for background information.
For an Energy Object, power usage is reported using eoPower. For an Energy Object, power usage is reported using eoPower.
The magnitude of measurement is based on the The magnitude of measurement is based on the
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
Textual Convention (TC). Power measurement magnitude should Textual Convention (TC). Power measurement magnitude should
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
[IEC.62053-22] definition of unit multiplier for the SI (System [IEC.62053-22] definition of unit multiplier for the SI (System
International) units of measure. Measured values are International) units of measure. Measured values are
represented in SI units obtained by BaseValue * 10 raised to the represented in SI units obtained by BaseValue * 10 raised to the
power of the scale. power of the scale.
skipping to change at page 16, line 14 skipping to change at page 14, line 49
In addition to knowing the usage and magnitude, it is useful to In addition to knowing the usage and magnitude, it is useful to
know how a eoPower measurement was obtained. An NMS can use know how a eoPower measurement was obtained. An NMS can use
this to account for the accuracy and nature of the reading this to account for the accuracy and nature of the reading
between different implementations. For this eoPowerOrigin between different implementations. For this eoPowerOrigin
describes whether the measurements were made at the device describes whether the measurements were made at the device
itself or from a remote source. The eoPowerMeasurementCaliber itself or from a remote source. The eoPowerMeasurementCaliber
describes the method that was used to measure the power and can describes the method that was used to measure the power and can
distinguish actual or estimated values. There may be devices in distinguish actual or estimated values. There may be devices in
the network, which may not be able to measure or report power the network, which may not be able to measure or report power
consumption. For those devices, the object consumption. For those devices, the object
eoPowerMeasurementCaliber shall report that measurement eoPowerMeasurementCaliber shall report that measurement
mechanism is "unavailable" and the eoPower measurement shall be mechanism is "unavailable" and the eoPower measurement shall be
"0". "0".
The nameplate power rating of an Energy Object is specified in The nameplate power rating of an Energy Object is specified in
eoPowerNameplate MIB object. eoPowerNameplate MIB object.
5.4. Optional Power Usage Attributes 5.4. Optional Power Usage Attributes
Refer to the "Optional Power Usage Attributes" section in
[EMAN-FMWK] for background information.
The optional powerAttributesMIB MIB module can be implemented to The optional powerAttributesMIB MIB module can be implemented to
further describe power usage attributes measurement. The further describe power usage attributes measurement. The
powerAttributesMIB MIB module adheres closely to the IEC 61850 powerAttributesMIB MIB module adheres closely to the IEC 61850
7-2 standard to describe AC measurements. 7-2 standard to describe AC measurements.
The powerAttributesMIB MIB module contains a primary table, the The powerAttributesMIB MIB module contains a primary table, the
eoACPwrAttributesTable table, that defines power attributes eoACPwrAttributesTable table, that defines power attributes
measurements for supported entPhysicalIndex entities, as a measurements for supported entPhysicalIndex entities, as a
sparse extension of the eoPowerTable (with entPhysicalIndex as sparse extension of the eoPowerTable (with entPhysicalIndex as
primary index). This eoACPwrAttributesTable table contains such primary index). This eoACPwrAttributesTable 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 eoACPwrAttributesPhaseTable In case of 3-phase power, the eoACPwrAttributesPhaseTable
additional table is populated with Power Attributes measurements additional table is populated with Power Attributes measurements
per phase (so double indexed by the entPhysicalIndex 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
eoACPwrAttributesDelPhaseTable table describes the phase-to- eoACPwrAttributesDelPhaseTable table describes the phase-to-
phase power attributes measurements, i.e., voltage and current. phase power attributes 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
eoACPwrAttributesWyePhaseTable table describes the phase-to- eoACPwrAttributesWyePhaseTable table describes the phase-to-
neutral power attributes measurements, i.e., voltage and neutral power attributes measurements, i.e., voltage and
current. current.
5.5. Optional Energy Measurement 5.5. Optional Energy Measurement
Refer to the "Optional Energy and demand Measurement" section in
[EMAN-FMWK] for the definition and terminology information.
It is relevant to measure energy and demand only when there are It is relevant to measure energy and demand only when there are
actual power measurements obtained from measurement hardware. If actual power measurements obtained from measurement hardware. If
the eoPowerMeasurementCaliber MIB object has values of the eoPowerMeasurementCaliber MIB object has values of
unavailable, unknown, estimated, or presumed, then the energy unavailable, unknown, estimated, or presumed, then the energy
and demand values are not useful. and demand values are not useful.
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. no interval. Demand information can be represented.
The eoEnergyParametersTable consists of the parameters defining The eoEnergyParametersTable consists of the parameters defining
eoEnergyParametersIndex an index of that specifies the setting eoEnergyParametersIndex an index of that specifies the setting
for collection of energy measurements for an Energy Object, for collection of energy measurements for an Energy Object,
eoEnergyObjectIndex linked to the entPhysicalIndex of the eoEnergyObjectIndex linked to the entPhysicalIndex of the
Energy Object, the duration of measurement intervals in seconds, 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 three different modes of collection are based on
on IEC standard 61850-7-4. Note that multiple IEC standard 61850-7-4. Note that multiple
eoEnergyParametersIntervalMode types MAY be configured eoEnergyParametersIntervalMode types MAY be configured
simultaneously. It is important to note that for a given Energy simultaneously. It is important to note that for a given Energy
Object, multiple modes (periodic, total, sliding window) of Object, multiple modes (periodic, total, sliding window) of
energy measurement collection can be configured with the use of energy measurement collection can be configured with the use of
eoEnergyParametersIndex. However, simultaneous measurement in eoEnergyParametersIndex. However, simultaneous measurement in
multiple modes for a given Energy Object depends on the Energy multiple modes for a given Energy Object depends on the Energy
Object capability. 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
eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, eoEnergyCollectionStartTime is represented by S1, S2, S3, S4,
..., Sx where x is the value of ..., Sx where x is the value of
eoEnergyParametersIntervalNumber. eoEnergyParametersIntervalNumber.
- The vertical axis represents the time interval of sampling and - The vertical axis represents the time interval of sampling and
the value of eoEnergyConsumed can be obtained at the end of the the value of eoEnergyConsumed can be obtained at the end of the
sampling period. The symbol =========== denotes the duration of sampling period. The symbol =========== denotes the 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 3 : Period eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'period' specifies non- A eoEnergyParametersIntervalMode type of 'period' specifies non-
overlapping periodic measurements. Therefore, the next overlapping periodic measurements. Therefore, the next
eoEnergyCollectionStartTime is equal to the previous eoEnergyCollectionStartTime is equal to the previous
eoEnergyCollectionStartTime plus eoEnergyCollectionStartTime plus
eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ...
|============ | |============ |
| | | |
| <--- L ---> | | <--- L ---> |
skipping to change at page 19, line 17 skipping to change at page 17, line 43
| | | | | | | |
| | | | | | | |
S2 | | | S2 | | |
| | | | | |
| | | | | |
S3 | | S3 | |
| | | |
| | | |
S4 S4
Figure 5 : Sliding eoEnergyParametersIntervalMode Figure 4 : Sliding eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'sliding' specifies A eoEnergyParametersIntervalMode type of 'sliding' specifies
overlapping periodic measurements. overlapping periodic measurements.
| | | |
|========================= | |========================= |
| | | |
| | | |
| | | |
| <--- Total length ---> | | <--- Total length ---> |
| | | |
S1 S1
Figure 6 : Total eoEnergyParametersIntervalMode Figure 5 : Total eoEnergyParametersIntervalMode
A eoEnergyParametersIntervalMode type of 'total' specifies a A eoEnergyParametersIntervalMode type of 'total' specifies a
continuous measurement since the last reset. The value of continuous measurement since the last reset. The value of
eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalNumber should be (1) one and
eoEnergyParametersIntervalLength is ignored. eoEnergyParametersIntervalLength is ignored.
The eoEnergyParametersStatus is used to start and stop energy The eoEnergyParametersStatus is used to start and stop energy
usage logging. The status of this variable is "active" when usage logging. The status of this variable is "active" when all
all the objects in eoEnergyParametersTable are appropriate which the objects in eoEnergyParametersTable are appropriate which in
in turn indicates if eoEnergyTable entries exist or not. turn indicates if eoEnergyTable entries exist or not.
The eoEnergyTable consists of energy measurements in The eoEnergyTable consists of energy measurements in
eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units
of the measured energy eoEnergyUnitMultiplier, and the maximum of the measured energy eoEnergyUnitMultiplier, and the maximum
observed energy within a window eoEnergyMaxConsumed, observed energy within a window eoEnergyMaxConsumed,
eoEnergyMaxProduced. eoEnergyMaxProduced.
Measurements of the total energy consumed by an Energy Object Measurements of the total energy consumed by an Energy Object
may suffer from interruptions in the continuous measurement of may suffer from interruptions in the continuous measurement of
energy consumption. In order to indicate such interruptions, energy consumption. In order to indicate such interruptions,
skipping to change at page 20, line 29 skipping to change at page 19, line 7
15 minutes and the number of consecutive intervals over which 15 minutes and the number of consecutive intervals over which
the maximum energy is calculated the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active (value 1) to indicate eoEnergyParametersStatus is set to active (value 1) to indicate
that the Energy Object should start monitoring the usage per the that the Energy Object should start monitoring the usage per the
eoEnergyTable. eoEnergyTable.
The indices for the eoEnergyTable are eoEnergyParametersIndex The indices for the eoEnergyTable are eoEnergyParametersIndex
which identifies the index for the setting of energy measurement which identifies the index for the setting of energy measurement
collection Energy Object, and eoEnergyCollectionStartTime, which collection Energy Object, and eoEnergyCollectionStartTime, which
denotes the start time of the energy measurement interval based denotes the start time of the energy measurement interval based
on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
measured energy consumption over the time interval specified measured energy consumption over the time interval specified
(eoEnergyParametersIntervalLength) based on the Energy Object (eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (eoEnergyParametersSampleRate). While internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the eoEnergyParametersIntervalLength and choosing the values for the eoEnergyParametersIntervalLength and
eoEnergyParametersSampleRate, it is recommended to take into eoEnergyParametersSampleRate, it is recommended to take into
consideration either the network element resources adequate to consideration either the network element resources adequate to
process and store the sample values, and the mechanism used to process and store the sample values, and the mechanism used to
calculate the eoEnergyConsumed. The units are derived from calculate the eoEnergyConsumed. The units are derived from
eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
"100" with eoEnergyUnitMultiplier equal to 0, the measured "100" with eoEnergyUnitMultiplier equal to 0, the measured
energy consumption of the Energy Object is 100 watt-hours. The energy consumption of the Energy Object is 100 watt-hours. The
eoEnergyMaxConsumed is the maximum energy observed and that can eoEnergyMaxConsumed is the maximum energy observed and that can
be "150 watt-hours". be "150 watt-hours".
skipping to change at page 21, line 16 skipping to change at page 19, line 42
calculated. The first observed energy measurement value is calculated. The first observed energy measurement value is
taken to be the initial maximum. With each subsequent taken to be the initial maximum. With each subsequent
measurement, based on numerical comparison, maximum energy may measurement, based on numerical comparison, maximum energy may
be updated. The maximum value is retained as long as the be updated. The maximum value is retained as long as the
measurements are taking place. Based on periodic polling of measurements are taking place. Based on periodic polling of
this table, an NMS could compute the maximum over a longer this table, an NMS could compute the maximum over a longer
period, i.e. a month, 3 months, or a year. period, i.e. a month, 3 months, or a year.
5.6. Fault Management 5.6. Fault Management
[EMAN-REQ] specifies requirements about Power States such as [RFC6988] specifies requirements about Power States such as "the
"the current power state" , "the time of the last state change", current Power State" , "the time of the last state change", "the
"the total time spent in each state", "the number of transitions total time spent in each state", "the number of transitions to
to each state" etc. Some of these requirements are fulfilled each state" etc. Some of these requirements are fulfilled
explicitly by MIB objects such as eoPowerOperState, explicitly by MIB objects such as eoPowerOperState,
eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the
other requirements are met via the SNMP NOTIFICATION mechanism. other requirements are met via the SNMP NOTIFICATION mechanism.
eoPowerStateChange SNMP notification which is generated when the eoPowerStateChange SNMP notification which is generated when the
value(s) of ,eoPowerStateIndex, eoPowerOperState, value(s) of ,eoPowerStateIndex, eoPowerOperState,
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
It is foreseen that most Energy Objects will require the It is foreseen that most Energy Objects will require the
implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a implementation of the ENERGY-OBJECT-CONTEXT-MIB MIB [EMAN-AWARE-
prerequisite for this MIB module. In such a case, eoPowerTable MIB] as a prerequisite for this MIB module. In such a case,
of the EMAN-MON-MIB is a sparse extension of the eoTable of eoPowerTable of the EMAN-MON-MIB is a sparse extension of the
ENERGY-AWARE-MIB. Every Energy Object MUST implement eoTable of ENERGY-OBJECT-CONTEXT-MIB. Every Energy Object MUST
entPhysicalIndex, entPhysicalUUID and entPhysicalName from the implement entPhysicalIndex, entPhysicalUUID and entPhysicalName
ENTITY-MIB [RFC6933]. As the primary index for the Energy from the ENTITY-MIB [RFC6933]. As the primary index for the
Object, entPhysicalIndex is used. Energy Object, entPhysicalIndex is used: It characterizes the
Energy Object in the ENERGY-OBJECT-MIB and the POWER-ATTRIBUTES-
The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- MIB MIB modules (this document).
MIB], if available, in order to discover all the Energy Objects
and the relationships between those (notion of Parent/Child).
In the ENERGY-AWARE-MIB module tables, the Energy Objects are
indexed by the entPhysicalIndex.
If an implementation of the ENERGY-AWARE-MIB module is available The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module
in the local SNMP context, for the same Energy Object, the [EMAN-AWARE-MIB], if available, in order to discover all the
entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The Energy Objects and the relationships between those Energy
entPhysicalIndex characterizes the Energy Object in the Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the
energyObjectMib and the powerAttributesMIB MIB modules (this Energy Objects are indexed by the entPhysicalIndex.
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 ENERGY-OBJECT-MIB module in this document), which
enumerates, amongst other things, the maximum power usage. As enumerates, amongst other things, the maximum power usage. As
the entries in eoPowerStateTable table are indexed by the the entries in eoPowerStateTable table are indexed by the
Energy Object ( entPhysicalIndex), 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, and the power usage per Power State of the Power Energy Object, and the power usage per Power State of the Power
State Set. In other words, polling the eoPowerStateTable allows State Set. In other words, polling the eoPowerStateTable allows
the discovery of each Power State within every Power State Set the discovery of each Power State within every Power State Set
supported by the Energy Object. supported by the Energy Object.
If the Energy Object is an Aggregator or a Proxy, the MIB module If the Energy Object has an Aggregation Relationship with
would be populated with the Energy Object Parent and Children another Energy Object, the MIB module would be populated with
information, which have their own Energy Object index value the Energy Object relationship information, which have their own
(entPhysicalIndex). However, the parent/child relationship must Energy Object index value (entPhysicalIndex). However, the
be discovered thanks to the ENERGY-AWARE-MIB module. Energy Object relationship must be discovered thanks to the
ENERGY-OBJECT-CONTEXT-MIB module.
Finally, the NMS can monitor the power attributes thanks to the Finally, the NMS can monitor the power attributes thanks to the
powerAttributesMIB MIB module, which reuses the entPhysicalIndex powerAttributesMIB MIB module, which reuses the entPhysicalIndex
to index the Energy Object. to index the Energy Object.
7. Link with the other IETF MIBs 7. Link with the other IETF MIBs
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the
skipping to change at page 22, line 45 skipping to change at page 21, line 24
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that
provides a standardized way of obtaining information (current provides a standardized way of obtaining information (current
value of the sensor, operational status of the sensor, and the value of the sensor, operational status of the sensor, and the
data units precision) from sensors embedded in networking data units precision) from sensors embedded in networking
devices. Sensors are associated with each index of devices. Sensors are associated with each index of
entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus
of the Power and Energy Monitoring MIB is on measurement of of the Power and Energy Monitoring MIB is on measurement of
power usage of networking equipment indexed by the ENTITY-MIB, power usage of networking equipment indexed by the ENTITY-MIB,
this MIB proposes a customized power scale for power measurement this MIB proposes a customized power scale for power measurement
and different power state states of networking equipment, and and different Power States of networking equipment, and
functionality to configure the power state states. functionality to configure the Power States.
When this MIB module is used to monitor the power usage of The Energy Objects are modeled by the entPhysicalIndex through
devices like routers and switches, the ENTITY-MIB and ENTITY- the entPhysicalEntity MIB object specified in the eoTable in the
SENSOR MIB SHOULD be implemented. In such cases, the Energy ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB].
Objects are modeled by the entPhysicalIndex through the
entPhysicalEntity MIB object specified in the eoTable in the
ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB].
However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x
C12.x accuracy classes required for electricity (i.e., 1%, 2%, accuracy classes required for electricity (i.e., 1%, 2%, 0.5%
0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] accuracy classes). Indeed, entPhySensorPrecision [RFC3433]
represents "The number of decimal places of precision in fixed- represents "The number of decimal places of precision in fixed-
point sensor values returned by the associated entPhySensorValue point sensor values returned by the associated entPhySensorValue
object". The ANSI and IEC Standards are used for power object". The ANSI and IEC Standards are used for power
measurement and these standards require that we use an accuracy measurement and these standards require that we use an accuracy
class, not the scientific-number precision model specified in class, not the scientific-number precision model specified in
RFC3433. The eoPowerAccuracy MIB object models this accuracy. RFC3433. The eoPowerAccuracy MIB object models this accuracy.
Note that eoPowerUnitMultipler represents the scale factor per Note that eoPowerUnitMultipler represents the scale factor per
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the (compared to entPhySensorScale), with the mantissa and the
skipping to change at page 25, line 44 skipping to change at page 24, line 17
- 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 and any
any of the UPS meters or submeters are the Energy Object of the UPS meters or submeters are the Energy Objects with a
Children. possible relationship as defined in [EMAN-FMWK].
7.5. Link with the LLDP and LLDP-MED MIBs 7.5. Link with the LLDP and LLDP-MED MIBs
The LLDP Protocol is a Data Link Layer protocol used by network The LLDP Protocol is a Data Link Layer protocol used by network
devices to advertise their identities, capabilities, and devices to advertise their identities, capabilities, and
interconnections on a LAN network. interconnections on a LAN network.
The Media Endpoint Discovery is an enhancement of LLDP, known as The Media Endpoint Discovery is an enhancement of LLDP, known as
LLDP-MED. The LLDP-MED enhancements specifically address voice LLDP-MED. The LLDP-MED enhancements specifically address voice
applications. LLDP-MED covers 6 basic areas: capability applications. LLDP-MED covers 6 basic areas: capability
skipping to change at page 27, line 4 skipping to change at page 25, line 15
eoethPortIndex and eoethPortGrpIndex. eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
eoPowerOrigin in indicating if the power for an attached device eoPowerOrigin in indicating if the power for an attached device
is local or from a remote device. If the LLDP-MED MIB is is local or from a remote device. If the LLDP-MED MIB is
supported, the following mapping can be applied to the supported, the following mapping can be applied to the
eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and
local(3) can be mapped to remote(2) and self(1), respectively. local(3) can be mapped to remote(2) and self(1), respectively.
8. Implementation Scenario 8. Implementation Scenario
This section provides an illustrative example scenario for the This section provides an illustrative example scenario for the
implementation of the Energy Object, including Energy Object implementation of the Energy Object, including Energy Object
Parent and Energy Object Child relationships. relationships.
Example Scenario of a campus network: Switch with PoE Endpoints Example Scenario of a campus network: Switch with PoE Endpoints
with further connected devices. with further connected devices.
The campus network consists of switches that provide LAN The campus network consists of switches that provide LAN
connectivity. The switch with PoE ports is located in wiring connectivity. The switch with PoE ports is located in wiring
closet. PoE IP phones are connected to the switch. The IP closet. PoE IP phones are connected to the switch. The IP
phones draw power from the PoE ports of the switch. In phones draw power from the PoE ports of the switch. In
addition, a PC is daisy-chained from the IP phone for LAN addition, a PC is daisy-chained from the IP phone for LAN
connectivity. connectivity.
The IP phone consumes power from the PoE switch, while the PC The IP phone consumes power from the PoE switch, while the PC
consumes power from the wall outlet. consumes power from the wall outlet.
The switch has implementations of ENTITY-MIB [RFC6933] and The switch has implementations of ENTITY-MIB [RFC6933] and
ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have ENERGY-OBJECT-CONTEXT-MIB MIB [EMAN-AWARE-MIB]. while the PC
implementation of the ENTITY-MIB, but has an implementation of has an implementation of the ENTITY-MIB with
ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following entity4CRCompliance, and an implementation of ENERGY-OBJECT-
CONTEXT-MIB MIB [EMAN-AWARE-MIB]. The switch has the following
attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID
1000". The power usage of the switch is "440 Watts". The 1000". The power usage of the switch is "440 Watts".
switch does not have an Energy Object Parent.
The PoE switch port has the following attributes: The switch The PoE switch port has the following attributes: The switch
port has entPhysicalIndex "3", and entPhysicalUUID is "UUID port has entPhysicalIndex "3", and entPhysicalUUID is "UUID
1000:3". The power metered at the POE switch port is "12 1000:3". The power metered at the POE switch port is "12
watts". In this example, the POE switch port has the switch as watts". In this example, the POE switch port has an Energy
the Energy Object Parent, with its eoParentID of "1000". Object relationship with the switch with Energy Object index
"1000".
The attributes of the PC are given below. The PC does not have The attributes of the PC are given below. The PC has an
an entPhysicalIndex, and the entPhysicalUUID is "UUID 1000:57 ". entPhysicalIndex "7" and its entPhysicalUUID is "UUID 1000:57 ".
The PC has an Energy Object Parent, i.e. the switch port whose The PC has an Energy Object relationship with the switch port
entPhysicalUUID is "UUID 1000:3". The power usage of the PC is whose entPhysicalUUID is "UUID 1000:3". The power usage of the
"120 Watts" and is communicated to the switch port. PC is "120 Watts" and is communicated to the switch port.
This example illustrates the important distinction between the The IP phone draws power from the switch, while the PC has LAN
Energy Object Children: The IP phone draws power from the connectivity from the phone, but is powered from the wall
switch, while the PC has LAN connectivity from the phone, but is outlet. However, the Energy Object switch sends power control
powered from the wall outlet. However, the Energy Object Parent messages to both the Energy Object (IP phone and PC) and the
sends power control messages to both the Energy Object Children attached remote Energy Objects react to those messages.
(IP phone and PC) and the Children react to those messages.
|-------------------------------------------------------| |-------------------------------------------------------|
| Switch | | Switch |
|=======================================================| |=======================================================|
| Switch | Switch | Switch | Switch | | Switch | Switch | | Switch |
| entPhyIndx | UUID |eoParentId | eoPower | | entPhyIndx | UUID | | eoPower |
| ===================================================== | | ===================================================== |
| 1 | UUID 1000 | null | 440 | | 1 | UUID 1000 | null | 440 |
| ===================================================== | | ===================================================== |
| | | |
| SWITCH PORT | | SWITCH PORT |
| ===================================================== | | ===================================================== |
| | Switch | Switch | Switch | Switch | | | Switch | Switch | Switch | Switch |
| | Port | Port | Port | Port | | | Port | Port | UUID | Port |
| | entPhyIndx | UUID | eoParentId | eoPower | | | entPhyIndx | UUID | | eoPower |
| ===================================================== | | ===================================================== |
| | 3 | UUID 1000:3 | 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 | Port | IP phone |
| entPhyIndx | UUID | eoParentID | eoPower | | entPhyIndx | UUID | UUID | eoPower |
====================================================== ======================================================
| Null | UUID 1000:31| UUID 1000:3 | 12 | | Null | UUID 1000:31| UUID 1000:3 | 12 |
======================================================= =======================================================
| |
| |
PC connected to switch via IP phone | PC connected to switch via IP phone |
| |
===================================================== =====================================================
| PC | PC | PC | PC | | PC | PC | Port | PC |
|entPhyIndx | UUID | eoParentID | eoPower | |entPhyIndx | UUID | UUID | eoPower |
===================================================== =====================================================
| 7 | UUID 1000:57| UUID 1000:3 | 120 | | 7 | UUID 1000:57| UUID 1000:3 | 120 |
===================================================== =====================================================
Figure 1: Example scenario Figure 6: Example scenario
9. Structure of the MIB 9. Structure of the MIB
The primary MIB object in this MIB module is the The primary MIB object in this MIB module is the
energyObjectMibObject. The eoPowerTable table of energyObjectMIBObject. The eoPowerTable table of
energyObjectMibObject describes the power measurement attributes energyObjectMIBObject describes the power measurement attributes
of an Energy Object entity. The notion of identity of the device of an Energy Object entity. The notion of identity of the device
in terms of uniquely identification of the Energy Object and its in terms of uniquely identification of the Energy Object and its
relationship to other entities in the network are addressed in relationship to other entities in the network are addressed in
[EMAN-AWARE-MIB]. [EMAN-AWARE-MIB].
Logically, this MIB module is a sparse extension of the Logically, this MIB module is a sparse extension of the
[EMAN-AWARE-MIB] module. Thus the following requirements which ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the
are applied to [EMAN-AWARE-MIB] are also applicable. As a following requirements which are applied to [EMAN-AWARE-MIB] are
requirement for this MIB module, [EMAN-AWARE-MIB] should be also applicable. As a requirement for this MIB module, [EMAN-
implemented and as Module Compliance of ENTITY-MIB V4 [RFC6933] AWARE-MIB] should be implemented and as Module Compliance of
with respect to entity4CRCompliance should be supported which ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance
requires 3 MIB objects (entPhysicalIndex, entPhysicalName and should be supported which requires 3 MIB objects
entPhysicalUUID ) MUST be implemented. (entPhysicalIndex, entPhysicalName and entPhysicalUUID ) MUST be
implemented.
eoMeterCapabilitiesTable is useful to enable applications to eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading that are supported by the local management system. By reading
the value of this object, it is possible for applications to the value of this object, it is possible for applications to
know which tables contain the information and are usable without know which tables contain the information and are usable without
walking through the table and querying every element which walking through the table and querying every element which
involves a trial-and-error process. involves a trial-and-error process.
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 eoPowerAttributes table An Energy Object may contain an optional eoPowerAttributes table
that describes the electrical characteristics associated with that describes the electrical characteristics associated with
the current power state and usage. the current Power State and usage.
An Energy Object may contain an optional eoEnergyTable to An Energy Object may contain an optional eoEnergyTable to
describe energy measurement information over time. describe energy measurement information over time.
An Energy Object may also contain optional battery information An Energy Object may also contain optional battery information
associated with this entity. associated with this entity.
10. MIB Definitions 10. MIB Definitions
-- ************************************************************ -- ************************************************************
skipping to change at page 30, line 32 skipping to change at page 28, line 42
Integer32, Counter32, TimeTicks Integer32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval, TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval,
TimeStamp, TruthValue TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex, PhysicalIndex entPhysicalIndex, PhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB
IANAPowerStateSet
energyObjectMib MODULE-IDENTITY FROM IANA-POWERSTATE-SET-MIB;
LAST-UPDATED "2013102120000Z" -- 21 October2013
energyObjectMIB MODULE-IDENTITY
LAST-UPDATED "201312130000Z" -- 13 December 2013
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
skipping to change at page 31, line 16 skipping to change at page 29, line 27
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad.schoening@verizon.net Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
skipping to change at page 31, line 31 skipping to change at page 30, line 4
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-115 Phone: +49 6221 4342-115
Email: quittek@neclab.eu Email: quittek@neclab.eu
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu Email: Thomas.Dietz@nw.neclab.eu"
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to monitor power and energy in "This MIB is used to monitor power and energy in
devices. devices.
This table sparse extension of the eoTable This table sparse extension of the eoTable
from the ENERGY-AWARE-MIB. As a requirement from the ENERGY-OBJECT-CONTEXT-MIB. As a requirement
[EMAN-AWARE-MIB] should be implemented. [EMAN-AWARE-MIB] must be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"2013102120000Z" -- 21 October2013 "201312130000Z" -- 13 December 2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC YYY."
::= { mib-2 xxx } ::= { energyMIB 3 }
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
STATUS current
DESCRIPTION
"IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of Power
State Sets and Power States.
The textual convention assumes that power states in 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
allocated to indicate the power state set. For a Power State X
in the Power State S, the named number with the value S * 256
+ X + 1 is allocated to represent the power state."
REFERENCE
"http://www.iana.org/assignments/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
SYNTAX INTEGER {
other(0), -- indicates other set
unknown(255), -- unknown power state
ieee1621(256), -- indicates IEEE1621 set
ieee1621On(257),
ieee1621Off(258),
ieee1621Sleep(259),
dmtf(512), -- indicates DMTF set
dmtfOn(513),
dmtfSleepLight(514),
dmtfSleepDeep(515),
dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set
emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
UnitMultiplier ::= TEXTUAL-CONVENTION UnitMultiplier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Unit Multiplier is an integer value that represents "The Unit Multiplier is an integer value that represents
the IEEE 61850 Annex A units multiplier associated with the IEEE 61850 Annex A units multiplier associated with
the integer units used to measure the power or energy. the integer units used to measure the power or energy.
For example, when used with eoPowerUnitMultiplier, -3 For example, when used with eoPowerUnitMultiplier, -3
represents 10^-3 or milliwatts." represents 10^-3 or milliwatts."
REFERENCE REFERENCE
skipping to change at page 35, line 4 skipping to change at page 31, line 43
yotta(24) -- 10^24 yotta(24) -- 10^24
} }
-- Objects -- Objects
eoMeterCapabilitiesTable OBJECT-TYPE eoMeterCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is useful for helping applications determine the "This table is useful for helping applications determine the
monitoring capabilities supported by the local management monitoring capabilities supported by the local management
agents. It is possible for applications to know which tables agents. It is possible for applications to know which tables
are usable without going through a trial-and-error process." are usable without going through a trial-and-error process."
::= { energyObjectMibObjects 1 } ::= { energyObjectMIBObjects 1 }
eoMeterCapabilitiesEntry OBJECT-TYPE eoMeterCapabilitiesEntry OBJECT-TYPE
SYNTAX EoMeterCapabilitiesEntry SYNTAX EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the metering capability of an Energy "An entry describes the metering capability of an Energy
Object." Object."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 } ::= { eoMeterCapabilitiesTable 1 }
skipping to change at page 35, line 47 skipping to change at page 32, line 41
MIB groups supported by the probe. By reading the value of this MIB groups supported by the probe. By reading the value of this
object, it is possible to determine the MIB tables supported. " object, it is possible to determine the MIB tables supported. "
::= { eoMeterCapabilitiesEntry 1 } ::= { eoMeterCapabilitiesEntry 1 }
eoPowerTable OBJECT-TYPE eoPowerTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerEntry SYNTAX SEQUENCE OF EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Energy Objects." "This table lists Energy Objects."
::= { energyObjectMibObjects 2 } ::= { energyObjectMIBObjects 2 }
eoPowerEntry OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX EoPowerEntry SYNTAX EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the power usage of an Energy Object." "An entry describes the power usage of an Energy Object."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { eoPowerTable 1 } ::= { eoPowerTable 1 }
skipping to change at page 41, line 14 skipping to change at page 38, line 6
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 3 } ::= { energyObjectMIBObjects 3 }
eoPowerStateEntry OBJECT-TYPE eoPowerStateEntry OBJECT-TYPE
SYNTAX EoPowerStateEntry SYNTAX EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A eoPowerStateEntry extends a corresponding "A eoPowerStateEntry extends a corresponding
eoPowerEntry. This entry displays max usage values at eoPowerEntry. This entry displays max usage values at
every single possible Power State supported by the Energy every single possible Power State supported by the Energy
Object. Object.
skipping to change at page 43, line 38 skipping to change at page 40, line 29
eoEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyParametersEntry SYNTAX SEQUENCE OF EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to configure the parameters for "This table is used to configure the parameters for
Energy measurement collection in the table Energy measurement collection in the table
eoEnergyTable. This table allows the configuration of eoEnergyTable. This table allows the configuration of
different measurement settings on the same Energy Object. different measurement settings on the same Energy Object.
Implementation of this table only sense for energy Implementation of this table only sense for Energy
objects that an eoPowerMeasurementCaliber of actual(3)." Objects that an eoPowerMeasurementCaliber of actual(3)."
::= { energyObjectMibObjects 4 } ::= { energyObjectMIBObjects 4 }
eoEnergyParametersEntry OBJECT-TYPE eoEnergyParametersEntry OBJECT-TYPE
SYNTAX EoEnergyParametersEntry SYNTAX EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry controls an energy measurement in "An entry controls an energy measurement in
eoEnergyTable." eoEnergyTable."
INDEX { eoEnergyObjectIndex, eoEnergyParametersIndex } INDEX { eoEnergyObjectIndex, eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
skipping to change at page 47, line 19 skipping to change at page 44, line 12
eoEnergyTable OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyEntry SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Energy Object energy measurements. "This table lists Energy Object energy measurements.
Entries in this table are only created if the Entries in this table are only created if the
corresponding value of object eoPowerMeasurementCaliber corresponding value of object eoPowerMeasurementCaliber
is active(3), i.e., if the power is actually metered." is active(3), i.e., if the power is actually metered."
::= { energyObjectMibObjects 5 } ::= { energyObjectMIBObjects 5 }
eoEnergyEntry OBJECT-TYPE eoEnergyEntry OBJECT-TYPE
SYNTAX EoEnergyEntry SYNTAX EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "An entry describing energy measurements."
INDEX { eoEnergyParametersIndex, INDEX { eoEnergyParametersIndex,
eoEnergyCollectionStartTime } eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 } ::= { eoEnergyTable 1 }
skipping to change at page 48, line 44 skipping to change at page 45, line 35
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 3 } ::= { eoEnergyEntry 3 }
eoEnergyStored OBJECT-TYPE eoEnergyStored 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 eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 } ::= { eoEnergyEntry 4 }
eoEnergyUnitMultiplier OBJECT-TYPE eoEnergyUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 50, line 41 skipping to change at page 47, line 33
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This variable indicates whether the DESCRIPTION "This variable indicates whether the
system produces the following notifications: system produces the following notifications:
eoPowerStateChange. eoPowerStateChange.
A false value will prevent these notifications A false value will prevent these notifications
from being generated." from being generated."
DEFVAL { false } DEFVAL { false }
::= { energyObjectMibNotifs 1 } ::= { energyObjectMIBNotifs 1 }
eoPowerStateChange NOTIFICATION-TYPE eoPowerStateChange NOTIFICATION-TYPE
OBJECTS {eoPowerAdminState, eoPowerOperState, OBJECTS {eoPowerAdminState, eoPowerOperState,
eoPowerStateEnterReason} eoPowerStateEnterReason}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP entity generates the eoPowerStateChange when "The SNMP entity generates the eoPowerStateChange when
the 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 entPhysicalIndex." the Energy Object represented by the entPhysicalIndex."
::= { energyObjectMibNotifs 2 } ::= { energyObjectMIBNotifs 2 }
-- Conformance -- Conformance
energyObjectMibCompliances OBJECT IDENTIFIER energyObjectMIBCompliances OBJECT IDENTIFIER
::= { energyObjectMib 3 } ::= { energyObjectMIBConform 1 }
energyObjectMibGroups OBJECT IDENTIFIER energyObjectMIBGroups OBJECT IDENTIFIER
::= { energyObjectMib 4 } ::= { energyObjectMIBConform 2 }
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.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMIBTableGroup,
energyObjectMibStateTableGroup, energyObjectMIBStateTableGroup,
eoPowerEnableStatusNotificationGroup, eoPowerEnableStatusNotificationGroup,
energyObjectMibNotifGroup energyObjectMIBNotifGroup
} }
GROUP energyObjectMibEnergyTableGroup GROUP energyObjectMIBEnergyTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
GROUP energyObjectMibEnergyParametersTableGroup GROUP energyObjectMIBEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of {RFC6933] Module Compliance of {RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
GROUP energyObjectMibMeterCapabilitiesTableGroup GROUP energyObjectMIBMeterCapabilitiesTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
::= { energyObjectMibCompliances 1 } ::= { energyObjectMIBCompliances 1 }
energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE energyObjectMIBReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented without support for "When this MIB is implemented without support for
read-create (i.e. in read-only mode), then such an read-create (i.e. in read-only mode), then such an
implementation can claim read-only compliance. Such a implementation can claim read-only compliance. Such a
device can then be monitored but cannot be device can then be monitored but cannot be
configured with this MIB. configured with this MIB.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMibTableGroup, energyObjectMIBTableGroup,
energyObjectMibStateTableGroup, energyObjectMIBStateTableGroup,
energyObjectMibNotifGroup energyObjectMIBNotifGroup
} }
OBJECT eoPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { energyObjectMibCompliances 2 } ::= { energyObjectMIBCompliances 2 }
-- Units of Conformance -- Units of Conformance
energyObjectMibTableGroup OBJECT-GROUP energyObjectMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPower, eoPower,
eoPowerNameplate, eoPowerNameplate,
eoPowerUnitMultiplier, eoPowerUnitMultiplier,
eoPowerAccuracy, eoPowerAccuracy,
eoPowerMeasurementCaliber, eoPowerMeasurementCaliber,
eoPowerCurrentType, eoPowerCurrentType,
eoPowerOrigin, eoPowerOrigin,
eoPowerAdminState, eoPowerAdminState,
eoPowerOperState, eoPowerOperState,
eoPowerStateEnterReason eoPowerStateEnterReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Object." related to the Energy Object."
::= { energyObjectMibGroups 1 } ::= { energyObjectMIBGroups 1 }
energyObjectMibStateTableGroup OBJECT-GROUP energyObjectMIBStateTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPowerStateMaxPower, eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier, eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime, eoPowerStateTotalTime,
eoPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
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 {
eoEnergyParametersIndex, 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 }
energyObjectMibEnergyTableGroup OBJECT-GROUP ::= { energyObjectMIBGroups 3 }
energyObjectMIBEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- eoEnergyCollectionStartTime is not -- eoEnergyCollectionStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
eoEnergyConsumed, eoEnergyConsumed,
eoEnergyProvided, eoEnergyProvided,
eoEnergyStored, eoEnergyStored,
eoEnergyUnitMultiplier, eoEnergyUnitMultiplier,
eoEnergyAccuracy, eoEnergyAccuracy,
eoEnergyMaxConsumed, eoEnergyMaxConsumed,
eoEnergyMaxProduced, eoEnergyMaxProduced,
eoEnergyDiscontinuityTime eoEnergyDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Table." related to the Energy Table."
::= { energyObjectMibGroups 4 } ::= { energyObjectMIBGroups 4 }
energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP energyObjectMIBMeterCapabilitiesTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoMeterCapability eoMeterCapability
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the object indicating the "This group contains the object indicating the
capability of the Energy Object" capability of the Energy Object"
::= { energyObjectMibGroups 5 } ::= { energyObjectMIBGroups 5 }
eoPowerEnableStatusNotificationGroup OBJECT-GROUP eoPowerEnableStatusNotificationGroup OBJECT-GROUP
OBJECTS { eoPowerEnableStatusNotification } OBJECTS { eoPowerEnableStatusNotification }
STATUS current STATUS current
DESCRIPTION "The collection of objects which are used DESCRIPTION "The collection of objects which are used
to enable notification." to enable notification."
::= { energyObjectMibGroups 6 } ::= { energyObjectMIBGroups 6 }
energyObjectMibNotifGroup NOTIFICATION-GROUP energyObjectMIBNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange eoPowerStateChange
} }
STATUS current STATUS current
DESCRIPTION "This group contains the notifications for DESCRIPTION "This group contains the notifications for
the power and energy monitoring MIB Module." the power and energy monitoring MIB Module."
::= { energyObjectMibGroups 7 } ::= { energyObjectMIBGroups 7 }
END END
-- ************************************************************ -- ************************************************************
-- --
-- This MIB module is used to monitor power attributes of -- This MIB module is used to monitor power attributes of
-- networked devices with measurements. -- networked devices with measurements.
-- --
-- This MIB module is an extension of energyObjectMib module. -- This MIB module is an extension of energyObjectMIB module.
-- --
-- ************************************************************* -- *************************************************************
POWER- ATTRIBUTES -MIB DEFINITIONS ::= BEGIN POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
Integer32 Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier UnitMultiplier
FROM ENERGY-OBJECT-MIB FROM ENERGY-OBJECT-MIB
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
powerAttributesMIB MODULE-IDENTITY powerAttributesMIB MODULE-IDENTITY
LAST-UPDATED "2013102120000Z" -- 21 October 2013 LAST-UPDATED "201312130000Z" -- 13 December 2013
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 56, line 33 skipping to change at page 53, line 20
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad.schoening@verizon.net Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
skipping to change at page 57, line 8 skipping to change at page 54, line 5
Email: quittek@neclab.eu Email: quittek@neclab.eu
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu Email: Thomas.Dietz@nw.neclab.eu"
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to report AC power attributes in "This MIB is used to report AC power attributes in
devices. The table is a sparse augmentation of the devices. The table is a sparse augmentation of the
eoPowerTable table from the energyObjectMib module. eoPowerTable table from the energyObjectMIB module.
Both three-phase and single-phase power Both three-phase and single-phase power
configurations are supported. configurations are supported.
As a requirement for this MIB module, As a requirement for this MIB module,
[EMAN-AWARE-MIB] should be implemented. [EMAN-AWARE-MIB] should be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4
with respect to entity4CRCompliance should with respect to entity4CRCompliance should
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"2013102120000Z" -- 21 October 2013 "201312130000Z" -- 13 December 2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { energyMIB 4 }
powerAttributesMIBConform OBJECT IDENTIFIER powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 } ::= { powerAttributesMIB 0 }
powerAttributesMIBObjects OBJECT IDENTIFIER powerAttributesMIBObjects OBJECT IDENTIFIER
::= { powerAttributesMIB 1 } ::= { powerAttributesMIB 1 }
-- Objects -- Objects
eoACPwrAttributesTable OBJECT-TYPE eoACPwrAttributesTable OBJECT-TYPE
skipping to change at page 63, line 9 skipping to change at page 59, line 46
::= { eoACPwrAttributesPhaseTable 1 } ::= { eoACPwrAttributesPhaseTable 1 }
EoACPwrAttributesPhaseEntry ::= SEQUENCE { EoACPwrAttributesPhaseEntry ::= SEQUENCE {
eoPhaseIndex Integer32, eoPhaseIndex Integer32,
eoACPwrAttributesPhaseAvgCurrent Integer32, eoACPwrAttributesPhaseAvgCurrent Integer32,
eoACPwrAttributesPhaseActivePower Integer32, eoACPwrAttributesPhaseActivePower Integer32,
eoACPwrAttributesPhaseReactivePower Integer32, eoACPwrAttributesPhaseReactivePower Integer32,
eoACPwrAttributesPhaseApparentPower Integer32, eoACPwrAttributesPhaseApparentPower Integer32,
eoACPwrAttributesPhasePowerFactor Integer32, eoACPwrAttributesPhasePowerFactor Integer32,
eoACPwrAttributesPhaseImpedance Integer32 eoACPwrAttributesPhaseImpedance Integer32
} }
eoPhaseIndex OBJECT-TYPE eoPhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359) SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240." "A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesPhaseEntry 1 } ::= { eoACPwrAttributesPhaseEntry 1 }
eoACPwrAttributesPhaseAvgCurrent OBJECT-TYPE eoACPwrAttributesPhaseAvgCurrent OBJECT-TYPE
skipping to change at page 66, line 49 skipping to change at page 63, line 40
Each entry describes power attributes attributes of one Each entry describes power attributes attributes of one
phase of a WYE 3-phase power system. phase of a WYE 3-phase power system.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects." MHAI objects."
INDEX { entPhysicalIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrAttributesWyePhaseTable 1} ::= { eoACPwrAttributesWyePhaseTable 1}
EoACPwrAttributesWyePhaseEntry ::= SEQUENCE { EoACPwrAttributesWyePhaseEntry ::= SEQUENCE {
eoACPwrAttributesWyePhaseToNeutralVoltage Integer32, eoACPwrAttributesWyePhaseToNeutralVoltage Integer32,
eoACPwrAttributesWyePhaseCurrent Integer32, eoACPwrAttributesWyePhaseCurrent Integer32,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
Integer32
} }
eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 Volt AC" UNITS "0.1 Volt AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of phase to neutral voltage. IEC "A measured value of phase to neutral voltage. IEC
61850-7-4 attribute 'PhV'." 61850-7-4 attribute 'PhV'."
skipping to change at page 68, line 15 skipping to change at page 65, line 5
Such devices can then be both monitored and configured with Such devices can then be both monitored and configured with
this MIB. this MIB.
Module Compliance of [RFC6933] with respect to Module Compliance of [RFC6933] with respect to
entity4CRCompliance should be supported which requires entity4CRCompliance should be supported which requires
implementation of 3 MIB objects (entPhysicalIndex, implementation of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerACPwrAttributesMIBTableGroup powerACPwrAttributesMIBTableGroup
} }
GROUP powerACPwrAttributesOptionalMIBTableGroup GROUP powerACPwrAttributesOptionalMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have "A compliant implementation does not have
to implement." to implement."
GROUP powerACPwrAttributesPhaseMIBTableGroup GROUP powerACPwrAttributesPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
skipping to change at page 69, line 37 skipping to change at page 66, line 28
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
attributes objects related to the Energy Object." attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 2 } ::= { powerAttributesMIBGroups 2 }
powerACPwrAttributesPhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex is -- Note that object entPhysicalIndex is
-- NOT included since it is -- NOT included since it is
-- not-accessible -- not-accessible
eoACPwrAttributesPhaseAvgCurrent, eoACPwrAttributesPhaseAvgCurrent,
eoACPwrAttributesPhaseActivePower, eoACPwrAttributesPhaseActivePower,
eoACPwrAttributesPhaseReactivePower, eoACPwrAttributesPhaseReactivePower,
eoACPwrAttributesPhaseApparentPower, eoACPwrAttributesPhaseApparentPower,
eoACPwrAttributesPhasePowerFactor, eoACPwrAttributesPhasePowerFactor,
eoACPwrAttributesPhaseImpedance eoACPwrAttributesPhaseImpedance
} }
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
attributes objects related to the Power State." attributes objects related to the Power State."
::= { powerAttributesMIBGroups 3 } ::= { powerAttributesMIBGroups 3 }
powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
skipping to change at page 70, line 24 skipping to change at page 67, line 14
"This group contains the collection of all power "This group contains the collection of all power
characteristic attributes of a phase in a DEL 3-phase characteristic attributes of a phase in a DEL 3-phase
power system." power system."
::= { powerAttributesMIBGroups 4 } ::= { powerAttributesMIBGroups 4 }
powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrAttributesWyePhaseToNeutralVoltage,
eoACPwrAttributesWyePhaseToNeutralVoltage, eoACPwrAttributesWyePhaseCurrent,
eoACPwrAttributesWyePhaseCurrent, eoACPwrAttributesWyeThdPhaseToNeutralVoltage
eoACPwrAttributesWyeThdPhaseToNeutralVoltage
} }
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 attributes configuration phase-to-neutral power attributes
measurements." measurements."
::= { powerAttributesMIBGroups 5 } ::= { powerAttributesMIBGroups 5 }
END END
IANA-POWERSTATE-SET-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ianaPowerStateSetMIB MODULE-IDENTITY
LAST-UPDATED "201312130000Z" -- December 13, 2013
ORGANIZATION "IANA"
CONTACT-INFO "
Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1-310-823-9358
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines a TEXTUAL-CONVENTION that
describes the relationships between Energy Objects.
Copyright (C) The IETF Trust (2013).
The initial version of this MIB module was published in
RFC YYY; for full legal notices see the RFC itself.
Supplementary information may be available at
http://www.ietf.org/copyrights/ianamib.html"
REVISION "201312130000Z" -- December 13, 2013
DESCRIPTION "Initial version of this MIB as published in
RFC YYY."
::= { energyMIB 5 }
-- RFC Editor, please replace YYY with the IANA allocation
-- for this MIB module and YYY with the number of the
-- approved RFC
-- Textual Conventions
IANAPowerStateSet::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of
Power State Sets and Power States.
The textual convention assumes that Power States in 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
allocated to indicate the Power State set. For a Power State X
in the Power State S, the named number with the value S * 256
+ X + 1 is allocated to represent the Power State."
REFERENCE
"http://www.iana.org/assignments/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
SYNTAX INTEGER {
other(0), -- indicates other set
unknown(255), -- unknown
ieee1621(256), -- indicates IEEE1621 set
ieee1621On(257),
ieee1621Off(258),
ieee1621Sleep(259),
dmtf(512), -- indicates DMTF set
dmtfOn(513),
dmtfSleepLight(514),
dmtfSleepDeep(515),
dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set
emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
END
11. Implementation Status 11. Implementation Status
[Note to RFC Editor: Please remove this section and the [Note to RFC Editor: Please remove this section and the
reference to [RFC6982] before publication.] reference to [RFC6982] before publication.]
This section records the status of known implementations of the This section records the status of known implementations of the
EMAN-Monitoring MIB at the time of posting of this Internet- EMAN-Monitoring MIB at the time of posting of this Internet-
Draft, and is based on a proposal described in [RFC6982]. Draft, and is based on a proposal described in [RFC6982].
The description of implementations in this section is intended The description of implementations in this section is intended
to assist the IETF in its decision processes in progressing to assist the IETF in its decision processes in progressing
drafts to RFCs. drafts to RFCs.
11.1. SNMP Research 11.1. SNMP Research
skipping to change at page 71, line 24 skipping to change at page 70, line 28
Organization: SNMP Research, Inc. Organization: SNMP Research, Inc.
Maturity: Prototype based upon early drafts of the MIBs. Maturity: Prototype based upon early drafts of the MIBs.
We anticipate updating it to more recent We anticipate updating it to more recent
documents as development schedules allow. documents as development schedules allow.
Coverage: Code was generated to implement all MIB objects Coverage: Code was generated to implement all MIB objects
in ENTITY-MIB (Version 4), in ENTITY-MIB (Version 4),
ENERGY-OBJECT-CONTEXT-MIB, ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB, ENERGY-OBJECT-MIB,
POWER-CHARACTERISTICS-MIB, POWER-ATTRIBUTES-MIB,
and BATTERY-MIB. and BATTERY-MIB.
Implementation experience: The documents are implementable. Implementation experience: The documents are implementable.
Comments: Technical comments about the Comments: Technical comments about the
ENERGY-OBJECT-CONTEXT-MIB, ENERGY-OBJECT-CONTEXT-MIB,
ENERGY-OBJECT-MIB, and ENERGY-OBJECT-MIB, and
BATTERY-MIB BATTERY-MIB
were submitted to the EMAN Working Group were submitted to the EMAN Working Group
E-mail list. E-mail list.
skipping to change at page 73, line 22 skipping to change at page 72, line 20
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to responsibility to ensure that the SNMP entity giving access to
an instance of these MIB modules is properly configured to give an instance of these MIB modules is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to GET or SET (change/create/delete) them. legitimate rights to GET or SET (change/create/delete) them.
13. IANA Considerations 13. IANA Considerations
13.1. IANA Considerations for the MIB Modules Additions to the ENERGY-OBJECT-MIB MIB and POWER-ATTRIBUTES-MIB
MIB modules are subject to Expert Review [RFC5226], i.e., review
The MIB modules in this document uses the following IANA- by one of a group of experts designated by an IETF Area
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers Director. The group of experts MUST check the requested MIB
registry: objects for completeness and accuracy of the description.
Requests for MIB objects that duplicate the functionality of
Descriptor OBJECT IDENTIFIER value existing objects SHOULD be declined. The smallest available
---------- ----------------------- OIDs SHOULD be assigned to the new MIB objects. The
energyObjectMib { mib-2 xxx } specification of new MIB objects SHOULD follow the structure
powerAttributesMIB { mib-2 yyy } specified in Section 10. and MUST be published using a well-
established and persistent publication medium.
Additions to the MIB modules are subject to Expert Review
[RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the
requested MIB objects for completeness and accuracy of the
description. Requests for MIB objects that duplicate the
functionality of existing objects SHOULD be declined. The
smallest available OIDs SHOULD be assigned to the new MIB
objects. The specification of new MIB objects SHOULD follow the
structure specified in Section 10. and MUST be published using
a well-established and persistent publication medium.
13.2. IANA Registration of new Power State Set 13.1. IANA Registration of new Power State Set
The initial set of Power State Sets are specified in [EMAN- The initial set of Power State Sets are specified in [EMAN-
FMWK]. IANA maintains a Textual Convention IANAPowerStateSet FMWK]. IANA maintains a Textual Convention IANAPowerStateSet
with the initial set of Power State Sets and the Power States with the initial set of Power State Sets and the Power States
within those Power State Sets as proposed in the [EMAN-FMWK]. within those Power State Sets as proposed in the [EMAN-FMWK].
The current version of IANAPowerStateSet Textual convention can The current version of IANAPowerStateSet Textual convention can
be accessed http://www.iana.org/assignments/IANAPowerStateSet be accessed http://www.iana.org/assignments/IANAPowerStateSet.
New Assignments to Power State Sets shall be administered by
IANA and the guidelines and procedures are specified in [EMAN-
FMWK].
13.2.1. IANA Registration of the IEEE1621 Power State Set New Assignments (and potential deprecation) to Power State Sets
shall be administered by IANA and the guidelines and
procedures are specified in [EMAN-FMWK], and will, as a
consequence, the IANAPowerStateSet Textual Convention should be
updated.
13.1.1. IANA Registration of the IEEE1621 Power State Set
The Internet Assigned Numbers Authority (IANA) has created a new The Internet Assigned Numbers Authority (IANA) has created a new
registry for IEEE1621 Power State Set identifiers and filled it registry for IEEE1621 Power State Set identifiers and filled it
with the initial list in the Textual Convention with the initial list in the Textual Convention
IANAPowerStateSet. IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for Guidelines for new assignments (or potentially deprecation) for
IEEE1621 Power State Set are specified in [EMAN-FMWK]. IEEE1621 Power State Set are specified in [EMAN-FMWK].
13.2.2. IANA Registration of the DMTF Power State Set 13.1.2. IANA Registration of the DMTF Power State Set
The Internet Assigned Numbers Authority (IANA) has created a new The Internet Assigned Numbers Authority (IANA) has created a new
registry for DMTF Power State Set identifiers and filled it in registry for DMTF Power State Set identifiers and filled it in
the Textual Convention IANAPowerStateSet. the Textual Convention IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for Guidelines for new assignments (or potentially deprecation) for
DMTF Power State Set are specified in [EMAN-FMWK]. DMTF Power State Set are specified in [EMAN-FMWK].
13.2.3. IANA Registration of the EMAN Power State Set 13.1.3. IANA Registration of the EMAN Power State Set
The Internet Assigned Numbers Authority (IANA) has created a new The Internet Assigned Numbers Authority (IANA) has created a new
registry for EMAN Power State Set identifiers and filled it in registry for EMAN Power State Set identifiers and filled it in
the Textual Convention IANAPowerStateSet. the Textual Convention IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for Guidelines for new assignments (or potentially deprecation) for
EMAN Power State Set are specified in [EMAN-FMWK]. EMAN Power State Set are specified in [EMAN-FMWK].
13.3. Updating the Registration of Existing Power State Sets 14. Contributors
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
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 12. 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 The authors would like to thank Juergen Schoenwalder for
design of the Textual Convention for IANAPowerStateSet and Ira proposing the design of the Textual Convention for
McDonald for his feedback. Thanks for the many comments on the IANAPowerStateSet and Ira McDonald for his feedback. Thanks for
design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. the many comments on the design of the EnergyTable from Minoru
Teraoka and Hiroto Ogaki.
14. Open Issues Many thanks to Alan Luchuk for the detailed review of the MIB
OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are and his comments.
covered.
15. References And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom
Nadeau.
15.2. Normative References 13. References
13.1. 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
1999. 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
skipping to change at page 76, line 33 skipping to change at page 74, line 43
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB",
RFC3621, December 2003. RFC3621, December 2003.
[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.
[EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili,
"draft-ietf-eman-energy-aware-mib-11 ", work in
progress, November 2013.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
[EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili, 13.2. Informative References
"draft-ietf-eman-energy-aware-mib-09 ", work in
progress, July 2013.
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.
[RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S.
skipping to change at page 77, line 29 skipping to change at page 75, line 31
Sensor Management Information Base", RFC 3433, December Sensor Management Information Base", RFC 3433, December
2002. 2002.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie,
"Guidelines for Writing an IANA Considerations Section "Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008. in RFCs ", BCP 26, RFC 5226, May 2008.
[EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
M. Chandramouli, " Requirements for Energy Management", Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
Running Code: The Implementation Status Section", RFC
6982, July 2013.
[RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M.
Chandramouli, " Requirements for Energy Management",
RFC 6988, September 2013. RFC 6988, September 2013.
[EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek, [EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek,
J., "Energy Management Framework", draft-ietf-eman- J., "Energy Management Framework", draft-ietf-eman-
framework-11, October 2013. framework-11, October 2013.
[EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T.,
Quittek, J. and B. Claise "Energy and Power Monitoring
MIB ", draft-ietf-eman-energy-monitoring-mib-06, July
2013.
[EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B. [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B.
"Energy Management (EMAN) Applicability Statement", "Energy Management (EMAN) Applicability Statement",
draft-ietf-eman-applicability-statement-04, October draft-ietf-eman-applicability-statement-04, October
2013. 2013.
[RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013.
[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
[IEEE1621] "Standard for User Interface Elements in Power [IEEE1621] "Standard for User Interface Elements in Power
skipping to change at page 78, line 35 skipping to change at page 76, line 35
[IEC.62053-21] International Electrotechnical Commission, [IEC.62053-21] International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 1 and 2)", 2003. (classes 1 and 2)", 2003.
[IEC.62053-22]International Electrotechnical Commission, [IEC.62053-22]International Electrotechnical Commission,
"Electricity metering equipment (a.c.) Particular "Electricity metering equipment (a.c.) Particular
requirements Part 22: Static meters for active energy requirements Part 22: Static meters for active energy
(classes 0,2 S and 0,5 S)", 2003. (classes 0,2 S and 0,5 S)", 2003.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
Running Code: The Implementation Status Section", RFC
6982, July 2013.
Authors' Addresses Authors' Addresses
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Diegem 1813
BE
Phone: +32 2 704 5622
Email: bclaise@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad.schoening@verizon.net Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
skipping to change at page 79, line 31 skipping to change at line 3525
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@neclab.eu Email: Thomas.Dietz@neclab.eu
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Diegem 1813
BE
Phone: +32 2 704 5622
Email: bclaise@cisco.com
 End of changes. 216 change blocks. 
606 lines changed or deleted 557 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/