draft-ietf-eman-energy-monitoring-mib-05.txt   draft-ietf-eman-energy-monitoring-mib-06.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: October 22, 2013 Independent Consultant Expires: February 15, 2014 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
April 22, 2013 July 15, 2013
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-05 draft-ietf-eman-energy-monitoring-mib-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79. with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html at http://www.ietf.org/shadow.html
This Internet-Draft will expire on October 2013. This Internet-Draft will expire on January 2014.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Abstract Abstract
This document defines a subset of the Management Information This document defines a subset of the Management Information
Base (MIB) for power and energy monitoring of devices. Base (MIB) for power and energy monitoring of devices.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED"
"MAY", and "OPTIONAL" in this document are to be interpreted as "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119]. described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction............................................ 3 1. Introduction............................................. 3
2. The Internet-Standard Management Framework.............. 4 2. The Internet-Standard Management Framework............... 4
3. Use Cases............................................... 4 3. Use Cases................................................ 4
4. Terminology............................................. 5 4. Terminology.............................................. 5
5. Architecture Concepts Applied to the MIB Module......... 6 5. Architecture Concepts Applied to the MIB Module.......... 6
5.1. Energy Object Information............................ 13 5.1. Energy Object Information............................. 13
5.2. Power State.......................................... 13 5.2. Power State........................................... 14
5.2.1. Power State Set...............................14 5.2.1. Power State Set................................14
5.2.2. IEEE1621 Power State Set......................15 5.3. Energy Object Usage Information....................... 15
5.2.3. DMTF Power State Set..........................15 5.4. Optional Power Usage Attributes....................... 16
5.2.4. EMAN Power State Set..........................16 5.5. Optional Energy Measurement........................... 17
5.3. Energy Object Usage Information...................... 19 5.6. Fault Management...................................... 21
5.4. Optional Power Usage Attributes...................... 20 6. Discovery............................................... 21
5.5. Optional Energy Measurement.......................... 21 7. Link with the other IETF MIBs........................... 22
5.6. Fault Management..................................... 25 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..22
6. Discovery.............................................. 25 7.2. Link with the ENTITY-STATE MIB......................23
7. Link with the other IETF MIBs.......................... 26 7.3. Link with the POWER-OVER-ETHERNET MIB...............24
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..26 7.4. Link with the UPS MIB...............................24
7.2. Link with the ENTITY-STATE MIB......................27 7.5. Link with the LLDP and LLDP-MED MIBs................25
7.3. Link with the POWER-OVER-ETHERNET MIB...............28 8. Implementation Scenario................................. 26
7.4. Link with the UPS MIB...............................29 9. Structure of the MIB.................................... 28
7.5. Link with the LLDP and LLDP-MED MIBs................30 10. MIB Definitions........................................ 29
8. Implementation Scenario................................ 30 11. Implementation Status.................................. 70
9. Structure of the MIB................................... 33 12. Security Considerations................................ 70
10. MIB Definitions....................................... 34 13. IANA Considerations.................................... 71
11. Security Considerations............................... 74 13.1. IANA Considerations for the MIB Modules.............. 71
12. IANA Considerations................................... 75 13.2. IANA Registration of new Power State Set............. 72
12.1. IANA Considerations for the MIB Modules............. 75 13.2.1. IANA Registration of the IEEE1621 Power State Set..72
12.2. IANA Registration of new Power State Set............ 75 13.2.2. IANA Registration of the DMTF Power State Set......72
12.2.1. IANA Registration of the IEEE1621 Power State Set.76 13.2.3. IANA Registration of the EMAN Power State Set.....73
12.2.2. IANA Registration of the DMTF Power State Set.....76 13.3. Updating the Registration of Existing Power State
12.2.3. IANA Registration of the EMAN Power State Set.....77 Sets....................................................... 73
12.3. Updating the Registration of Existing Power State 12. Contributors........................................... 73
Sets...................................................... 77 13. Acknowledgment......................................... 74
12. Contributors.......................................... 77 14. Open Issues............................................ 74
13. Acknowledgment........................................ 78 15. References............................................. 74
14. Open Issues........................................... 78 15.2. Normative References...............................74
15. References............................................ 78 15.3. Informative References.............................75
15.2. Normative References..............................78
15.3. Informative References............................79
1. Introduction 1. Introduction
This document defines a subset of the Management Information This document defines a subset of the Management Information
Base (MIB) for use in energy management of devices within or Base (MIB) for use in energy management of devices within or
connected to communication networks. The MIB modules in this connected to communication networks. The MIB modules in this
document are designed to provide a model for energy management, document are designed to provide a model for energy management,
which includes monitoring for power state and energy consumption which includes monitoring for power state and energy consumption
of networked elements. This MIB takes into account the Energy of networked elements. This MIB takes into account the Energy
Management Framework [EMAN-FMWK], which in turn, is based on the Management Framework [EMAN-FMWK], which in turn, is based on the
skipping to change at page 4, line 15 skipping to change at page 4, line 13
Applicability Statement [EMAN-AS]. Applicability Statement [EMAN-AS].
Where applicable, device monitoring extends to the individual Where applicable, device monitoring extends to the individual
components of the device and to any attached dependent devices. components of the device and to any attached dependent devices.
For example: A device can contain components that are For example: A device can contain components that are
independent from a power-state point of view, such as line independent from a power-state point of view, such as line
cards, processor cards, hard drives. A device can also have cards, processor cards, hard drives. A device can also have
dependent attached devices, such as a switch with PoE endpoints dependent attached devices, such as a switch with PoE endpoints
or a power distribution unit with attached endpoints. or a power distribution unit with attached endpoints.
Devices and their sub-components may be characterized by the Devices and their sub-components can be modeled using the
power-related attributes of a physical entity present in the containment tree of the ENTITY-MIB [RFC6933]. In addition,
ENTITY-MIB, even though the ENTITY-MIB compliance is not a ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] provides a framework
requirement due to the variety and broad base of devices for modeling the relationship between Energy Objects. It is
concerned with energy management. 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
stuations, 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
skipping to change at page 9, line 6 skipping to change at page 9, line 9
| +-- r-n Integer32 eoEnergyNet (4) | +-- r-n Integer32 eoEnergyNet (4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoEnergyUnitMultiplier (5) | eoEnergyUnitMultiplier (5)
| +-- r-n Integer32 eoEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyMaxConsumed (7) | +-- r-n Integer32 eoEnergyMaxConsumed (7)
| +-- r-n Integer32 eoEnergyMaxProduced (8) | +-- r-n Integer32 eoEnergyMaxProduced (8)
| +-- r-n TimeTicks | +-- r-n TimeTicks
| eoEnergyDiscontinuityTime(9) | eoEnergyDiscontinuityTime(9)
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]
| | | |
| | | |
skipping to change at page 11, line 21 skipping to change at page 11, line 25
| +---------------------------+ | +---------------------------+
|---- | Energy Object Attributes | |---- | Energy Object Attributes |
| | ------------------------- | | | ------------------------- |
| | eoPowerNamePlate | | | eoPowerNamePlate |
| | eoPowerMeasurementCaliber | | | eoPowerMeasurementCaliber |
| | eoPowerCurrentType | | | eoPowerCurrentType |
| | eoPowerOrigin | | | eoPowerOrigin |
| +---------------------------+ | +---------------------------+
| |
| +---------------------------------+ | +---------------------------------+
|---- |_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-AWARE-MIB
skipping to change at page 12, line 22 skipping to change at page 12, line 27
+----------------------------------+ +----------------------------------+
+-----------------------+ +-----------------------+
|---> | Energy Object ID (*) | |---> | Energy Object ID (*) |
| | --------------------- | | | --------------------- |
| | entPhysicalIndex | | | entPhysicalIndex |
| | entPhysicalName | | | entPhysicalName |
| | entPhysicalUUID | | | entPhysicalUUID |
| +-----------------------+ | +-----------------------+
| |
| +-------------------------------------------+ | +--------------------------------------+
|---- | Power Attributes | |---- | Power Attributes |
| | ----------------------------------------- | | | ------------------------------------ |
| | eoACPwrAttributesConfiguration | | | eoACPwrAttributesConfiguration |
| | eoACPwrAttributesAvgVoltage | | | eoACPwrAttributesAvgVoltage |
| | eoACPwrAttributesAvgCurrent | | | eoACPwrAttributesAvgCurrent |
| | eoACPwrAttributesFrequency | | | eoACPwrAttributesFrequency |
| | eoACPwrAttributesPowerUnitMultiplier | | | eoACPwrAttributesPowerUnitMultiplier |
| | eoACPwrAttributesPowerAccuracy | | | eoACPwrAttributesPowerAccuracy |
| | eoACPwrAttributesTotalActivePower | | | eoACPwrAttributesTotalActivePower |
| | eoACPwrAttributesTotalReactivePower | | | eoACPwrAttributesTotalReactivePower |
| | eoACPwrAttributesTotalApparentPower | | | eoACPwrAttributesTotalApparentPower |
| | eoACPwrAttributesTotalPowerFactor | | | eoACPwrAttributesTotalPowerFactor |
| | eoACPwrAttributesThdAmpheres | | | eoACPwrAttributesThdAmpheres |
| +-------------------------------------------+ | +--------------------------------------+
| |
| |
| +-------------------------------------------+ | +--------------------------------------+
|---- | Power Phase Attributes | |---- | Power Phase Attributes |
| | ----------------------------------------- | | | ------------------------------------ |
| | eoPhaseIndex | | | eoPhaseIndex |
| | eoACPwrAttributesPhaseAvgCurrent | | | eoACPwrAttributesPhaseAvgCurrent |
| | eoACPwrAttributesPhaseActivePower | | | eoACPwrAttributesPhaseActivePower |
| | eoACPwrAttributesPhaseReactivePower | | | eoACPwrAttributesPhaseReactivePower |
| | eoACPwrAttributesPhaseApparentPower | | | eoACPwrAttributesPhaseApparentPower |
| | eoACPwrAttributesPhasePowerFactor | | | eoACPwrAttributesPhasePowerFactor |
| | eoACPwrAttributesPhaseImpedance | | | eoACPwrAttributesPhaseImpedance |
| +-------------------------------------------+ | +--------------------------------------+
| |
| |
| +-----------------------------------------------------+ | +------------------------------------------------+
|---- | 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-AWARE-MIB
5.1. Energy Object Information 5.1. Energy Object Information
Refer to the "Energy Object Information" section in [EMAN-FMWK] Refer to the "Energy Object Information" section in [EMAN-FMWK]
for background information. An energy aware device is for background information. An energy aware device is
considered as an instance of a Energy Object as defined in the considered as an instance of a Energy Object as defined in the
[EMAN-FMWK]. [EMAN-FMWK].
The Energy Object identity information is specified in the MIB The Energy Object identity information is specified in the MIB
ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the
eoTable. In this table, the context of the Energy Object such as eoTable. In this table, the context of the Energy Object such as
Domain, Role Description, Importance are specified. In addition, Domain, RoleDescription, Importance are specified. In addition,
the ENERGY-AWARE-MIB module returns the relationship between the ENERGY-AWARE-MIB module returns the relationship between
Objects. There are several possible relationships between Parent Objects. There are several possible relationships between Parent
and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy, and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy,
PoweredBy, AggregatedBy and ProxyedBy. PoweredBy, and AggregatedBy.
5.2. Power State 5.2. Power State
Refer to the "Power States" section in [EMAN-FMWK] for Refer to the "Power States" section in [EMAN-FMWK] for
background information. background information.
An Energy Object may have energy conservation modes called Power An Energy Object may have energy conservation modes called Power
States. Between the ON and OFF states of a device, there can be States. Between the ON and OFF states of a device, there can be
several intermediate energy saving modes. Those energy saving several intermediate energy saving modes. Those energy saving
modes are called as Power States. modes are called as Power States.
skipping to change at page 15, line 12 skipping to change at page 15, line 17
unknown(0) unknown(0)
IEEE1621(256) - [IEEE1621] IEEE1621(256) - [IEEE1621]
DMTF(512) - [DMTF] DMTF(512) - [DMTF]
EMAN(1024) - [EMAN-MONITORING-MIB] EMAN(1024) - [EMAN-MONITORING-MIB]
The respective specific states related to each Power State Set The respective specific states related to each Power State Set
are specified in the following sections. The guidelines for are specified in the following sections. The guidelines for
addition of new Power State Sets have been specified in the IANA addition of new Power State Sets have been specified in the IANA
Considerations Section. Considerations Section.
5.2.2. IEEE1621 Power State Set The Power States within each Power State Set are listed in
[EMAN-FMWK]. The Textual Convention IANAPowerStateSet provides
The IEEE1621 Power State Set [IEEE1621] consists of 3 the proposed numbering of the Power States within the IEEE1621
rudimentary states : on, off or sleep. Power State Set, DMTF Power State Set and the EMAN Power State
on(0) - The device is fully On and all features of the
device are in working mode.
off(1) - The device is mechanically switched off and does
not consume energy.
sleep(2) - The device is in a power saving mode, and some
features may not be available immediately.
The Textual Convention IANAPowerStateSet provides the proposed
numbering of the Power States within the IEEE1621 Power State
Set. Set.
5.2.3. DMTF Power State Set
DMTF [DMTF] standards organization has defined a power profile
standard based on the CIM (Common Information Model) model that
consists of 15 power states ON (2), SleepLight (3), SleepDeep
(4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off-
Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10),
Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard
Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off-
Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF
standard is targeted for hosts and computers. Details of the
semantics of each Power State within the DMTF Power State Set
can be obtained from the DMTF Power State Management Profile
specification [DMTF].
DMTF power profile extends ACPI power states. The following
table provides a mapping between DMTF and ACPI Power State Set:
---------------------------------------------------
| DMTF | ACPI |
| Power State | Power State |
---------------------------------------------------
| Reserved(0) | |
---------------------------------------------------
| Reserved(1) | |
---------------------------------------------------
| ON (2) | G0-S0 |
--------------------------------------------------
| Sleep-Light (3) | G1-S1 G1-S2 |
--------------------------------------------------
| Sleep-Deep (4) | G1-S3 |
--------------------------------------------------
| Power Cycle (Off-Soft) (5) | G2-S5 |
---------------------------------------------------
| Off-hard (6) | G3 |
---------------------------------------------------
| Hibernate (Off-Soft) (7) | G1-S4 |
---------------------------------------------------
| Off-Soft (8) | G2-S5 |
---------------------------------------------------
| Power Cycle (Off-Hard) (9) | G3 |
---------------------------------------------------
| Master Bus Reset (10) | G2-S5 |
---------------------------------------------------
| Diagnostic Interrupt (11) | G2-S5 |
---------------------------------------------------
| Off-Soft Graceful (12) | G2-S5 |
---------------------------------------------------
| Off-Hard Graceful (13) | G3 |
---------------------------------------------------
| MasterBus Reset Graceful (14) | G2-S5 |
---------------------------------------------------
| Power Cycle off-soft Graceful (15)| G2-S5 |
---------------------------------------------------
| Power Cycle off-hard Graceful (16)| G3 |
---------------------------------------------------
Figure 3: DMTF and ACPI Powe State Set Mapping
The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the DMTF Power State Set.
5.2.4. EMAN Power State Set
The EMAN Power State Set represents an attempt for a uniform
standard approach to model the different levels of power
consumption of a device. The EMAN Power States are an expansion
of the basic Power States as defined in IEEE1621 that also
incorporate the Power States defined in ACPI and DMTF.
Therefore, in addition to the non-operational states as defined
in ACPI and DMTF standards, several intermediate operational
states have been defined.
There are twelve Power States, that expand on IEEE1621 on, sleep
and off. The expanded list of Power States are divided into six
operational states, and six non-operational states. The lowest
non-operational state is 1 and the highest is 6. Each non-
operational state corresponds to an ACPI state [ACPI]
corresponding to Global and System states between G3 (hard-off)
and G1 (sleeping). For Each operational state represent a
performance state, and may be mapped to ACPI states P0 (maximum
performance power) through P5 (minimum performance and minimum
power).
An Energy Object may have fewer Power States than twelve and
would then map several policy states to the same power state.
Energy Object with more than twelve states, would choose which
twelve to represent as power policy states.
In each of the non-operational states (from mechoff(1) to
ready(6)), the Power State preceding it is expected to have a
lower power consumption and a longer delay in returning to an
operational state:
IEEE1621 Power(off):
mechoff(1) : An off state where no entity features are
available. The entity is unavailable.
No energy is being consumed and the power
connector can be removed. This
corresponds to ACPI state G3.
softoff(2) : Similar to mechoff(1), but some
components remain powered or receive
trace power so that the entity
can be awakened from its off state. In
softoff(2), no context is saved and the
device typically requires a complete boot
when awakened. This corresponds to ACPI
state G2.
IEEE1621 Power(sleep)
hibernate(3): No entity features are available. The
entity may be awakened without requiring
a complete boot, but the time for
availability is longer than sleep(4). An
example for state hibernate(3) is a save
to-disk state where DRAM context is not
maintained. Typically, energy consumption
is zero or close to zero. This
corresponds to state G1, S4 in ACPI.
sleep(4) : No entity features are available, except
for out-of-band management, for example
wake-up mechanisms. The time for
availability is longer than standby(5).
An example for state sleep(4) is a save-
to-RAM state, where DRAM context is
maintained. Typically, energy
consumption is close to zero. This
corresponds to state G1, S3 in ACPI.
standby(5) : No entity features are available, except
for out-of-band management, for example
wake-up mechanisms. This mode is analogous
to cold-standy. The time for availability
is longer than ready(6). For example, the
processor context is not maintained.
Typically, energy consumption is close to
zero. This corresponds to state G1, S2 in
ACPI.
ready(6) : No entity features are available, except
for out-of-band management, for example
wake-up mechanisms. This mode is
analogous to hot-standby. The entity can
be quickly transitioned into an
operational state. For example,
processors are not executing, but
processor context is maintained. This
corresponds to state G1, S1 in ACPI.
IEEE1621 Power(on):
lowMinus(7) : Indicates some entity features may not be
available and the entity has selected
measures/options to provide less than
low(8) usage. This corresponds to
ACPI State G0. This includes operational
states lowMinus(7) to full(12).
low(8) : Indicates some features may not be
available and the entity has taken
measures or selected options to provide
less than mediumMinus(9) usage.
mediumMinus(9): Indicates all entity features are
available but the entity has taken
measures or selected options to provide
less than medium(10) usage.
medium(10) : Indicates all entity features are
available but the entity has taken
measures or selected options to provide
less than highMinus(11) usage.
highMinus(11): Indicates all entity features are
available and power usage is less
than high(12).
high(12) : Indicates all entity features are
available and the entity is consuming the
highest power.
The Textual Convention IANAPowerStateSet contains the proposed
numbering of the Power States within the EMAN Power State Set.
5.3. Energy Object Usage Information 5.3. Energy Object Usage Information
Refer to the "Energy Object Usage Measurement" section in [EMAN- Refer to the "Energy Object Usage Measurement" section in [EMAN-
FMWK] for background information. FMWK] for background information.
For an Energy Object, power usage is reported using eoPower. For an Energy Object, power usage is reported using eoPower.
The magnitude of measurement is based on the The magnitude of measurement is based on the
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
Textual Convention (TC). Power measurement magnitude should Textual Convention (TC). Power measurement magnitude should
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
skipping to change at page 20, line 28 skipping to change at page 16, line 21
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 Refer to the "Optional Power Usage Attributes" section in
[EMAN-FMWK] for background information. [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 Refer to the "Optional Energy and demand Measurement" section in
[EMAN-FMWK] for the definition and terminology information. [EMAN-FMWK] for the definition and terminology information.
skipping to change at page 22, line 16 skipping to change at page 18, line 10
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
skipping to change at page 24, line 29 skipping to change at page 20, line 21
15 minutes and the number of consecutive intervals over which 15 minutes and the number of consecutive intervals over which
the maximum energy is calculated the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active (value 1) to indicate eoEnergyParametersStatus is set to active (value 1) to indicate
that the Energy Object should start monitoring the usage per the that the Energy Object should start monitoring the usage per the
eoEnergyTable. eoEnergyTable.
The indices for the eoEnergyTable are eoEnergyParametersIndex The indices for the eoEnergyTable are eoEnergyParametersIndex
which identifies the index for the setting of energy measurement which identifies the index for the setting of energy measurement
collection Energy Object, and eoEnergyCollectionStartTime, which collection Energy Object, and eoEnergyCollectionStartTime, which
denotes the start time of the energy measurement interval based denotes the start time of the energy measurement interval based
on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the
measured energy consumption over the time interval specified measured energy consumption over the time interval specified
(eoEnergyParametersIntervalLength) based on the Energy Object (eoEnergyParametersIntervalLength) based on the Energy Object
internal sampling rate (eoEnergyParametersSampleRate). While internal sampling rate (eoEnergyParametersSampleRate). While
choosing the values for the eoEnergyParametersIntervalLength and choosing the values for the eoEnergyParametersIntervalLength and
eoEnergyParametersSampleRate, it is recommended to take into eoEnergyParametersSampleRate, it is recommended to take into
consideration either the network element resources adequate to consideration either the network element resources adequate to
process and store the sample values, and the mechanism used to process and store the sample values, and the mechanism used to
calculate the eoEnergyConsumed. The units are derived from calculate the eoEnergyConsumed. The units are derived from
eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be
"100" with eoEnergyUnitMultiplier equal to 0, the measured "100" with eoEnergyUnitMultiplier equal to 0, the measured
energy consumption of the Energy Object is 100 watt-hours. The energy consumption of the Energy Object is 100 watt-hours. The
eoEnergyMaxConsumed is the maximum energy observed and that can eoEnergyMaxConsumed is the maximum energy observed and that can
be "150 watt-hours". be "150 watt-hours".
The eoEnergyTable has a buffer to retain a certain number of The eoEnergyTable has a buffer to retain a certain number of
intervals, as defined by eoEnergyParametersIntervalNumber. intervals, as defined by eoEnergyParametersIntervalNumber.
If the default value of "10" is kept, then the eoEnergyTable If the default value of "10" is kept, then the eoEnergyTable
contains 10 energy measurements, including the maximum. contains 10 energy measurements, including the maximum.
Here is a brief explanation of how the maximum energy can be Here is a brief explanation of how the maximum energy can be
skipping to change at page 25, line 35 skipping to change at page 21, line 28
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
It is foreseen that most Energy Objects will require the It is foreseen that most Energy Objects will require the
implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a
prerequisite for this MIB module. In such a case, eoPowerTable prerequisite for this MIB module. In such a case, eoPowerTable
of the EMAN-MON-MIB is a sparse extension of the eoTable of of the EMAN-MON-MIB is a sparse extension of the eoTable of
ENERGY-AWARE-MIB. Every Energy Object MUST implement ENERGY-AWARE-MIB. Every Energy Object MUST implement
entPhysicalIndex, entPhysicalUUID and entPhysicalName from the entPhysicalIndex, entPhysicalUUID and entPhysicalName from the
ENTITY-MIB [EMAN-ENTITY]. As the primary index for the Energy ENTITY-MIB [RFC6933]. As the primary index for the Energy
Object, entPhysicalIndex is used. Object, entPhysicalIndex is used.
The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE-
MIB], if available, in order to discover all the Energy Objects MIB], if available, in order to discover all the Energy Objects
and the relationships between those (notion of Parent/Child). and the relationships between those (notion of Parent/Child).
In the ENERGY-AWARE-MIB module tables, the Energy Objects are In the ENERGY-AWARE-MIB module tables, the Energy Objects are
indexed by the entPhysicalIndex. indexed by the entPhysicalIndex.
If an implementation of the ENERGY-AWARE-MIB module is available If an implementation of the ENERGY-AWARE-MIB module is available
in the local SNMP context, for the same Energy Object, the in the local SNMP context, for the same Energy Object, the
skipping to change at page 31, line 21 skipping to change at page 27, line 8
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 [EMAN-ENTITY ] and The switch has implementations of ENTITY-MIB [RFC6933] and
ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have
implementation of the ENTITY-MIB, but has an implementation of implementation of the ENTITY-MIB, but has an implementation of
ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following
attributes, entPhysicalIndex "1", and 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". The
switch does not have an Energy Object Parent. switch does not have an Energy Object Parent.
The PoE switch port has the following attributes: The switch The PoE switch port has the following attributes: The switch
port has entPhysicalIndex "3", and 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
skipping to change at page 33, line 19 skipping to change at page 28, line 47
energyObjectMibObject describes the power measurement attributes energyObjectMibObject describes the power measurement attributes
of an Energy Object entity. The notion of identity of the device of an Energy Object entity. The notion of identity of the device
in terms of uniquely identification of the Energy Object and its in terms of uniquely identification of the Energy Object and its
relationship to other entities in the network are addressed in relationship to other entities in the network are addressed in
[EMAN-AWARE-MIB]. [EMAN-AWARE-MIB].
Logically, this MIB module is a sparse extension of the Logically, this MIB module is a sparse extension of the
[EMAN-AWARE-MIB] module. Thus the following requirements which [EMAN-AWARE-MIB] module. Thus the following requirements which
are applied to [EMAN-AWARE-MIB] are also applicable. As a are applied to [EMAN-AWARE-MIB] are also applicable. As a
requirement for this MIB module, [EMAN-AWARE-MIB] should be requirement for this MIB module, [EMAN-AWARE-MIB] should be
implemented and as Module Compliance of ENTITY-MIB V4 [EMAN- implemented and as Module Compliance of ENTITY-MIB V4 [RFC6933]
ENTITY] with respect to entity4CRCompliance should be supported with respect to entity4CRCompliance should be supported which
which requires 3 MIB objects (entPhysicalIndex, entPhysicalName requires 3 MIB objects (entPhysicalIndex, entPhysicalName and
and entPhysicalUUID ) MUST be implemented. entPhysicalUUID ) MUST be implemented.
eoMeterCapabilitiesTable is useful to enable applications to eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading that are supported by the local management system. By reading
the value of this object, it is possible for applications to the value of this object, it is possible for applications to
know which tables contain the information and are usable without know which tables contain the information and are usable without
walking through the table and querying every element which walking through the table and querying every element which
involves a trial-and-error process. involves a trial-and-error process.
skipping to change at page 34, line 16 skipping to change at page 30, line 4
-- ************************************************************ -- ************************************************************
-- --
-- --
-- This MIB is used to monitor power usage of network -- This MIB is used to monitor power usage of network
-- devices -- devices
-- --
-- ************************************************************* -- *************************************************************
ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
mib-2, mib-2,
Integer32, Counter32, TimeTicks Integer32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval, TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval,
TimeStamp 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;
energyObjectMib MODULE-IDENTITY energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201210220000Z" -- 22 October 2012 LAST-UPDATED "201306300000Z" -- 30 June 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:
skipping to change at page 36, line 18 skipping to change at page 31, line 50
from the ENERGY-AWARE-MIB. As a requirement from the ENERGY-AWARE-MIB. As a requirement
[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
"201210220000Z" -- 22 October 2012 "201306300000Z" -- 30 June 2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
::= { mib-2 xxx } ::= { mib-2 xxx }
energyObjectMibNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { energyObjectMib 0 } ::= { energyObjectMib 0 }
energyObjectMibObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
skipping to change at page 39, line 20 skipping to change at page 35, line 4
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 }
EoMeterCapabilitiesEntry ::= SEQUENCE { EoMeterCapabilitiesEntry ::= SEQUENCE {
eoMeterCapability BITS eoMeterCapability BITS
} }
eoMeterCapability OBJECT-TYPE eoMeterCapability OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
powermetering(1), -- power measurement powermetering(1), -- power measurement
energymetering(2), -- energy measurement energymetering(2), -- energy measurement
powerattributes(3) -- power attributes powerattributes(3) -- power attributes
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the Energy monitoring capabilities supported "An indication of the Energy monitoring capabilities supported
by this agent. This object use a BITS syntax and indicate the by this agent. This object use a BITS syntax and indicate the
MIB groups supported by the probe. By reading the value of this MIB groups supported by the probe. By reading the value of this
object, it is possible to determine the MIB tables supported. " object, it is possible to determine the MIB tables supported. "
::= { eoMeterCapabilitiesEntry 1 } ::= { eoMeterCapabilitiesEntry 1 }
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."
skipping to change at page 45, line 30 skipping to change at page 41, line 11
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.
For example, given the values of a Energy Object For example, given the values of a Energy Object
corresponding to a maximum usage of 0 W at the corresponding to a maximum usage of 0 W at the
state 1 (mechoff), 8 W at state 6 (ready), 11 W at state state 1 (mechoff), 8 W at state 6 (ready), 11 W at state
8 (mediumMinus),and 11 W at state 12 (high): 9 (mediumMinus),and 11 W at state 12 (high):
State MaxUsage Units State MaxUsage Units
1 (mechoff 0 W 1 (mechoff 0 W
2 (softoff) 0 W 2 (softoff) 0 W
3 (hibernate) 0 W 3 (hibernate) 0 W
4 (sleep) 0 W 4 (sleep) 0 W
5 (standby) 0 W 5 (standby) 0 W
6 (ready) 8 W 6 (ready) 8 W
7 (lowMinus) 8 W 7 (lowMinus) 8 W
8 (low) 11 W 8 (low) 11 W
9 (medimMinus) 11 W 9 (mediumMinus) 11 W
10 (medium) 11 W 10 (medium) 11 W
11 (highMinus) 11 W 11 (highMinus) 11 W
12 (high) 11 W 12 (high) 11 W
Furthermore, this table extends to return the total time Furthermore, this table extends to return the total time
in each Power State, along with the number of times a in each Power State, along with the number of times a
particular Power State was entered." particular Power State was entered."
INDEX { entPhysicalIndex, INDEX { entPhysicalIndex,
eoPowerStateIndex eoPowerStateIndex
skipping to change at page 48, line 31 skipping to change at page 44, line 11
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unique value, to identify the specific Energy Object "The unique value, to identify the specific Energy Object
on which the measurement is applied, the same index used on which the measurement is applied, the same index used
in the eoPowerTable to identify the Energy Object." in the eoPowerTable to identify the Energy Object."
::= { eoEnergyParametersEntry 1 } ::= { eoEnergyParametersEntry 1 }
eoEnergyParametersIndex OBJECT-TYPE eoEnergyParametersIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the index of the Energy "This object specifies the index of the Energy
Parameters setting for collection of energy measurements Parameters setting for collection of energy measurements
for an Energy Object. An Energy Object can have multiple for an Energy Object. An Energy Object can have multiple
eoEnergyParametersIndex, depending on the capability of eoEnergyParametersIndex, depending on the capability of
the Energy Object" the Energy Object"
::= { eoEnergyParametersEntry 2 } ::= { eoEnergyParametersEntry 2 }
eoEnergyParametersIntervalLength OBJECT-TYPE eoEnergyParametersIntervalLength OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the length of time in hundredth of "This object indicates the length of time in hundredth of
seconds over which to compute the average seconds over which to compute the average
eoEnergyConsumed measurement in the eoEnergyTable table. eoEnergyConsumed measurement in the eoEnergyTable table.
The computation is based on the Energy Object's internal The computation is based on the Energy Object's internal
sampling rate of power consumed or produced by the Energy sampling rate of power consumed or produced by the Energy
Object. The sampling rate is the rate at which the Energy Object. The sampling rate is the rate at which the Energy
Object can read the power usage and may differ based on Object can read the power usage and may differ based on
device capabilities. The average energy consumption is device capabilities. The average energy consumption is
then computed over the length of the interval." then computed over the length of the interval."
DEFVAL { 90000 } DEFVAL { 90000 }
::= { eoEnergyParametersEntry 3 } ::= { eoEnergyParametersEntry 3 }
eoEnergyParametersIntervalNumber OBJECT-TYPE eoEnergyParametersIntervalNumber OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of intervals maintained in the eoEnergyTable. "The number of intervals maintained in the eoEnergyTable.
Each interval is characterized by a specific Each interval is characterized by a specific
eoEnergyCollectionStartTime, used as an index to the eoEnergyCollectionStartTime, used as an index to the
table eoEnergyTable. Whenever the maximum number of table eoEnergyTable. Whenever the maximum number of
entries is reached, the measurement over the new interval entries is reached, the measurement over the new interval
replacesthe oldest measurement. There is one exception to replaces the oldest measurement. There is one exception
this rule: when the eoEnergyMaxConsumed and/or to this rule: when the eoEnergyMaxConsumed and/or
eoEnergyMaxProduced are in (one of) the two oldest eoEnergyMaxProduced are in (one of) the two oldest
measurement(s), they are left untouched and the next measurement(s), they are left untouched and the next
oldest measurement is replaced." oldest measurement is replaced."
DEFVAL { 10 } DEFVAL { 10 }
::= { eoEnergyParametersEntry 4 } ::= { eoEnergyParametersEntry 4 }
eoEnergyParametersIntervalMode OBJECT-TYPE eoEnergyParametersIntervalMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
period(1), period(1),
sliding(2), sliding(2),
total(3) total(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control object to define the mode of interval calculation "A control object to define the mode of interval calculation
for the computation of the average eoEnergyConsumed or for the computation of the average eoEnergyConsumed or
eoEnergyProduced measurement in the eoEnergyTable table. eoEnergyProduced measurement in the eoEnergyTable table.
A mode of period(1) specifies non-overlapping periodic A mode of period(1) specifies non-overlapping periodic
measurements. measurements.
A mode of sliding(2) specifies overlapping sliding windows A mode of sliding(2) specifies overlapping sliding windows
where the interval between the start of one interval and where the interval between the start of one interval and
the next is defined in eoEnergyParametersIntervalWindow. the next is defined in eoEnergyParametersIntervalWindow.
A mode of total(3) specifies non-periodic measurement. In A mode of total(3) specifies non-periodic measurement. In
this mode only one interval is used as this is a this mode only one interval is used as this is a
skipping to change at page 50, line 31 skipping to change at page 46, line 11
::= { eoEnergyParametersEntry 6 } ::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sampling rate, in milliseconds, at which the Energy "The sampling rate, in milliseconds, at which the Energy
Object should poll power usage in order to compute the Object should poll power usage in order to compute the
average eoEnergyConsumed, eoEnergyProduced measurements average eoEnergyConsumed, eoEnergyProduced measurements
in the table eoEnergyTable. The Energy Object should in the table eoEnergyTable. The Energy Object should
initially set this sampling rate to a reasonable value, initially set this sampling rate to a reasonable value,
i.e., a compromise between intervals that will provide i.e., a compromise between intervals that will provide
good accuracy by not being too long, but not so short good accuracy by not being too long, but not so short
that they affect the Energy Object performance by that they affect the Energy Object performance by
requesting continuous polling. If the sampling rate is requesting continuous polling. If the sampling rate is
unknown, the value 0 is reported. The sampling rate unknown, the value 0 is reported. The sampling rate
should be selected so that should be selected so that
eoEnergyParametersIntervalWindow is a multiple of eoEnergyParametersIntervalWindow is a multiple of
eoEnergyParametersSampleRate." eoEnergyParametersSampleRate."
skipping to change at page 53, line 24 skipping to change at page 49, line 4
eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced
." ."
::= { eoEnergyEntry 5 } ::= { eoEnergyEntry 5 }
eoEnergyAccuracy OBJECT-TYPE eoEnergyAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a percentage value, in 100ths of a "This object indicates a percentage value, in 100ths of a
percent, representing the presumed accuracy of Energy usage percent, representing the presumed accuracy of Energy usage
reporting. eoEnergyAccuracy is applicable to all Energy reporting. eoEnergyAccuracy is applicable to all Energy
measurements in the eoEnergyTable. measurements in the eoEnergyTable.
For example: 1010 means the reported usage is accurate to +/- For example: 1010 means the reported usage is accurate to +/-
10.1 percent. 10.1 percent.
This value is zero if the accuracy is unknown." This value is zero if the accuracy is unknown."
::= { eoEnergyEntry 6 } ::= { eoEnergyEntry 6 }
eoEnergyMaxConsumed OBJECT-TYPE eoEnergyMaxConsumed OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
skipping to change at page 54, line 33 skipping to change at page 50, line 13
occasion at which any one or more of this entity's energy occasion at which any one or more of this entity's energy
counters in this table suffered a discontinuity: counters in this table suffered a discontinuity:
eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no
such discontinuities have occurred since the last re- such discontinuities have occurred since the last re-
initialization of the local management subsystem, then initialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
::= { eoEnergyEntry 9 } ::= { eoEnergyEntry 9 }
-- Notifications -- Notifications
eoPowerEnableStatusNotification OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This variable indicates whether the
system produces the following notifications:
eoPowerStateChange.
A false value will prevent these notifications
from being generated."
DEFVAL { false }
::= { 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 1 } ::= { energyObjectMibNotifs 2 }
-- Conformance -- Conformance
energyObjectMibCompliances OBJECT IDENTIFIER energyObjectMibCompliances OBJECT IDENTIFIER
::= { energyObjectMib 3 } ::= { energyObjectMib 3 }
energyObjectMibGroups OBJECT IDENTIFIER energyObjectMibGroups OBJECT IDENTIFIER
::= { energyObjectMib 4 } ::= { energyObjectMib 4 }
energyObjectMibFullCompliance MODULE-COMPLIANCE energyObjectMibFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for "When this MIB is implemented with support for
read-create, then such an implementation can read-create, then such an implementation can
claim full compliance. Such devices can then claim full compliance. Such devices can then
be both monitored and configured with this MIB. be both monitored and configured with this MIB.
Module Compliance of [EMAN-ENTITY] 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,
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 [EMAN-ENTITY] 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 {EMAN-ENTITY] 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 [EMAN-ENTITY] 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 [EMAN-ENTITY] 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
skipping to change at page 57, line 33 skipping to change at page 53, line 29
eoPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the "This group contains the collection of all the
objects related to the Power State." objects related to the Power State."
::= { energyObjectMibGroups 2 } ::= { energyObjectMibGroups 2 }
energyObjectMibEnergyParametersTableGroup OBJECT-GROUP energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoEnergyObjectIndex,
eoEnergyParametersIndex, eoEnergyParametersIndex,
eoEnergyParametersIntervalLength, eoEnergyParametersIntervalLength,
eoEnergyParametersIntervalNumber, eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode, eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow, eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate, eoEnergyParametersSampleRate,
eoEnergyParametersStatus eoEnergyParametersStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 58, line 34 skipping to change at page 54, line 29
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
OBJECTS { eoPowerEnableStatusNotification }
STATUS current
DESCRIPTION "The collection of objects which are used
to enable notification."
::= { energyObjectMibGroups 6 }
energyObjectMibNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange eoPowerStateChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION "This group contains the notifications for
"This group contains the notifications for the power and the power and energy monitoring MIB Module."
energy monitoring MIB Module." ::= { energyObjectMibGroups 7 }
::= { energyObjectMibGroups 6 }
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 "201210220000Z" -- 22 October 2012 LAST-UPDATED "201306300000Z" -- 30 June 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:
skipping to change at page 61, line 13 skipping to change at page 57, line 19
[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
"201210220000Z" -- 22 2012 "201306300000Z" -- 30 June 2013
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { mib-2 yyy } ::= { mib-2 yyy }
powerAttributesMIBConform OBJECT IDENTIFIER powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 } ::= { powerAttributesMIB 0 }
powerAttributesMIBObjects OBJECT IDENTIFIER powerAttributesMIBObjects OBJECT IDENTIFIER
skipping to change at page 66, line 29 skipping to change at page 62, line 33
DEL. Entities having single phase power shall not have DEL. Entities having single phase power shall not have
any entries here. It is a sparse extension of the any entries here. It is a sparse extension of the
eoACPwrAttributesTable. eoACPwrAttributesTable.
These attributes correspond to IEC 61850-7.4 MMXU phase These attributes correspond to IEC 61850-7.4 MMXU phase
measurements." measurements."
INDEX { entPhysicalIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoPhaseIndex }
::= { 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 }
skipping to change at page 68, line 33 skipping to change at page 64, line 37
"This table describes DEL configuration phase-to-phase "This table describes DEL configuration phase-to-phase
power attributes measurements. This is a sparse power attributes measurements. This is a sparse
extension of the eoACPwrAttributesPhaseTable." extension of the eoACPwrAttributesPhaseTable."
::= { powerAttributesMIBObjects 3 } ::= { powerAttributesMIBObjects 3 }
eoACPwrAttributesDelPhaseEntry OBJECT-TYPE eoACPwrAttributesDelPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrAttributesDelPhaseEntry SYNTAX EoACPwrAttributesDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes power attributes attributes of a "An entry describes power attributes attributes of a
phase in a DEL 3-phase power system. Voltage phase in a DEL 3-phase power system. Voltage
measurements are provided both relative to each other measurements are provided both relative to each other
and zero. and zero.
Measured values are from IEC 61850-7-2 MMUX and THD from Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects. MHAI objects.
For phase-to-phase measurements, the eoPhaseIndex is For phase-to-phase measurements, the eoPhaseIndex is
compared against the following phase at +120 degrees. compared against the following phase at +120 degrees.
Thus, the possible values are: Thus, the possible values are:
skipping to change at page 70, line 31 skipping to change at page 66, line 34
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 Integer32 eoACPwrAttributesWyeThdPhaseToNeutralVoltage
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 71, line 34 skipping to change at page 67, line 37
::= { powerAttributesMIB 3 } ::= { powerAttributesMIB 3 }
powerAttributesMIBFullCompliance MODULE-COMPLIANCE powerAttributesMIBFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for read-create, "When this MIB is implemented with support for read-create,
then such an implementation can claim full compliance. then such an implementation can claim full compliance.
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 [EMAN-ENTITY] 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
skipping to change at page 73, line 35 skipping to change at page 69, line 40
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
-- eoPhaseIndex are NOT included -- eoPhaseIndex are NOT included
-- since they are not-accessible -- since they are not-accessible
eoACPwrAttributesDelPhaseToNextPhaseVoltage, eoACPwrAttributesDelPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage, eoACPwrAttributesDelThdPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdCurrent eoACPwrAttributesDelThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all power "This group contains the collection of all power
characteristic attributes of a phase in a DEL 3-phase characteristic attributes of a phase in a DEL 3-phase
power system." power system."
::= { 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
11. Security Considerations 11. Implementation Status
[RFC Editor: before publication please remove this section and
the reference to [I-D.sheffer-running-code], along the offered
experiment of which this section exists to assist document
reviewers.]
At the time of this writing the mandatory tables of the MIB
module eoPowerTable.and eoPowerStateTable have been implemented
as a standalone prototype for monitoring the energy consumption
of routers and switches. Network Management support for querying
MIB objects is under development.
12. Security Considerations
Some of the readable objects in these MIB modules (i.e., objects Some of the readable objects in these MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
thus important to control even GET and/or NOTIFY access to these thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects objects and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. when sending them over the network via SNMP.
There are a number of management objects defined in these MIB There are a number of management objects defined in these MIB
modules with a MAX-ACCESS clause of read-write and/or read- modules with a MAX-ACCESS clause of read-write and/or read-
skipping to change at page 75, line 18 skipping to change at page 71, line 41
mechanisms (for authentication and privacy). mechanisms (for authentication and privacy).
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.
12. IANA Considerations 13. IANA Considerations
12.1. IANA Considerations for the MIB Modules 13.1. IANA Considerations for the MIB Modules
The MIB modules in this document uses the following IANA- The MIB modules in this document uses the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
energyObjectMib { mib-2 xxx } energyObjectMib { mib-2 xxx }
powerAttributesMIB { mib-2 yyy } powerAttributesMIB { mib-2 yyy }
Additions to the MIB modules are subject to Expert Review Additions to the MIB modules are subject to Expert Review
[RFC5226], i.e., review by one of a group of experts designated [RFC5226], i.e., review by one of a group of experts designated
by an IETF Area Director. The group of experts MUST check the by an IETF Area Director. The group of experts MUST check the
requested MIB objects for completeness and accuracy of the requested MIB objects for completeness and accuracy of the
description. Requests for MIB objects that duplicate the description. Requests for MIB objects that duplicate the
functionality of existing objects SHOULD be declined. The functionality of existing objects SHOULD be declined. The
smallest available OIDs SHOULD be assigned to the new MIB smallest available OIDs SHOULD be assigned to the new MIB
objects. The specification of new MIB objects SHOULD follow the objects. The specification of new MIB objects SHOULD follow the
structure specified in Section 10. and MUST be published using structure specified in Section 10. and MUST be published using
a well-established and persistent publication medium. a well-established and persistent publication medium.
12.2. IANA Registration of new Power State Set 13.2. IANA Registration of new Power State Set
This document specifies an initial set of Power State Sets. The The initial set of Power State Sets are specified in [EMAN-
list of these Power State Sets with their numeric identifiers is FMWK]. IANA maintains a Textual Convention IANAPowerStateSet
given in Section 5.2.1. IANA maintains a Textual Convention with the initial set of Power State Sets and the Power States
IANAPowerStateSet with the initial set of Power State Sets and within those Power State Sets as proposed in the [EMAN-FMWK].
the Power States within those Power State Sets. The current The current version of IANAPowerStateSet Textual convention can
version of Textual convention can be accessed be accessed http://www.iana.org/assignments/IANAPowerStateSet
http://www.iana.org/assignments/IANAPowerStateSet
New Assignments to Power State Sets shall be administered by New Assignments to Power State Sets shall be administered by
IANA and the guidelines and procedures are listed in this IANA and the guidelines and procedures are specified in [EMAN-
Section. FMWK].
New assignments for Power State Set will be administered by IANA 13.2.1. IANA Registration of the IEEE1621 Power State Set
through 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 state for completeness and
accuracy of the description. A pure vendor specific
implementation of Power State Set shall not be adopted; since it
would lead to proliferation of Power State Sets.
12.2.1. IANA Registration of the IEEE1621 Power State Set The Internet Assigned Numbers Authority (IANA) has created a new
registry for IEEE1621 Power State Set identifiers and filled it
with the initial list in the Textual Convention
IANAPowerStateSet.
This document specifies a set of values for the IEEE1621 Power Guidelines for new assignments (or potentially deprecation) for
State Set [IEEE1621]. The list of these values with their IEEE1621 Power State Set are specified in [EMAN-FMWK].
identifiers is given in Section 5.2.1. The Internet Assigned
Numbers Authority (IANA) created a new registry for IEEE1621
Power State Set identifiers and filled it with the initial
listin the Textual Convention IANAPowerStateSet..
New assignments (or potentially deprecation) for IEEE1621 Power 13.2.2. IANA Registration of the DMTF Power State Set
State Set will 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 group of experts MUST check the
requested state for completeness and accuracy of the
description.
12.2.2. IANA Registration of the DMTF Power State Set The Internet Assigned Numbers Authority (IANA) has created a new
registry for DMTF Power State Set identifiers and filled it in
the Textual Convention IANAPowerStateSet.
This document specifies a set of values for the DMTF Power State Guidelines for new assignments (or potentially deprecation) for
Set. The list of these values with their identifiers is given DMTF Power State Set are specified in [EMAN-FMWK].
in Section 5.2.1. The Internet Assigned Numbers Authority
(IANA) has created a new registry for DMTF Power State Set
identifiers and filled it with the initial list in the Textual
Convention IANAPowerStateSet.
New assignments (or potentially deprecation) for DMTF Power
State Set will 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 group of experts MUST check the
conformance with the DMTF standard [DMTF], on the top of
checking for completeness and accuracy of the description.
12.2.3. IANA Registration of the EMAN Power State Set 13.2.3. IANA Registration of the EMAN Power State Set
This document specifies a set of values for the EMAN Power State The Internet Assigned Numbers Authority (IANA) has created a new
Set. The list of these values with their identifiers is given registry for EMAN Power State Set identifiers and filled it in
in Section 5.2.1. The Internet Assigned Numbers Authority the Textual Convention IANAPowerStateSet.
(IANA) has created a new registry for EMAN Power State Set
identifiers and filled it with the initial list in the Textual
Convention IANAPowerStateSet.
New assignments (or potentially deprecation) for EMAN Power
State Set will 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 group of experts MUST check the
requested state for completeness and accuracy of the
description.
12.3. Updating the Registration of Existing Power State Sets Guidelines for new assignments (or potentially deprecation) for
EMAN Power State Set are specified in [EMAN-FMWK].
13.3. Updating the Registration of Existing Power State Sets
IANA maintains a Textual Convention IANAPowerStateSet with the IANA maintains a Textual Convention IANAPowerStateSet with the
initial set of Power State Sets and the Power States within initial set of Power State Sets and the Power States within
those Power State Sets. The current version of Textual those Power State Sets. The current version of Textual
convention can be accessed convention can be accessed
http://www.iana.org/assignments/IANAPowerStateSet http://www.iana.org/assignments/IANAPowerStateSet
With the evolution of standards, over time, it may be important With the evolution of standards, over time, it may be important
to deprecate of some of the existing the Power State Sets or to deprecate of some of the existing the Power State Sets or
some of the states within a Power State Set. some of the states within a Power State Set.
skipping to change at page 78, line 4 skipping to change at page 73, line 47
registrant cannot be reached, IESG can designate an Expert to registrant cannot be reached, IESG can designate an Expert to
modify the IANA registry for the deprecation. modify the IANA registry for the deprecation.
12. Contributors 12. Contributors
This document results from the merger of two initial proposals. This document results from the merger of two initial proposals.
The following persons made significant contributions either in The following persons made significant contributions either in
one of the initial proposals or in this document. one of the initial proposals or in this document.
John Parello John Parello
Rolf Winter
Rolf Winter
Dominique Dudkowski Dominique Dudkowski
13. Acknowledgment 13. Acknowledgment
The authors would like to thank Shamita Pisal for her prototype The authors would like to thank Shamita Pisal for her prototype
of this MIB module, and her valuable feedback. The authors of this MIB module, and her valuable feedback. The authors
would like to Michael Brown for improving the text dramatically. would like to Michael Brown for improving the text dramatically.
We would like to thank Juergen Schoenwalder for proposing the We would like to thank Juergen Schoenwalder for proposing the
design of the Textual Convention for IANAPowerStateSet and Ira design of the Textual Convention for IANAPowerStateSet and Ira
skipping to change at page 78, line 27 skipping to change at page 74, line 25
design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki.
14. Open Issues 14. Open Issues
OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are
covered. Nominal Voltage to be reported as a range ? covered. Nominal Voltage to be reported as a range ?
OPEN ISSUE 2 IANA Registered Power State Sets deferred to [EMAN- OPEN ISSUE 2 IANA Registered Power State Sets deferred to [EMAN-
FMWK] FMWK]
OPEN ISSUE 3 Disabling eoPowerStateNotification
OPEN ISSUE 4 Units for eoParametersSampleRate in centiseconds to
match the same time scale
OPEN ISSUE 5 Windowing mechanism to determine the
eoEnergyMaxConsumed
15. References 15. References
15.2. Normative References 15.2. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, BCP 14, RFC 2119, March 1997. Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
skipping to change at page 79, line 31 skipping to change at page 75, line 19
[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.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
[EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- [EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili,
energy-aware-mib-08 ", work in progress, April 2013. "draft-ietf-eman-energy-aware-mib-09 ", work in
progress, July 2013.
15.3. Informative References 15.3. Informative References
[RFC1628] S. Bradner, "UPS Management Information Base", RFC [RFC1628] S. Bradner, "UPS Management Information Base", RFC
1628, May 1994 1628, May 1994
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework ", RFC 3410, December Standard Management Framework ", RFC 3410, December
2002. 2002.
skipping to change at page 80, line 18 skipping to change at page 76, line 7
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie,
"Guidelines for Writing an IANA Considerations Section "Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008. in RFCs ", BCP 26, RFC 5226, May 2008.
[EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and
M. Chandramouli, " Requirements for Energy Management", M. Chandramouli, " Requirements for Energy Management",
draft-ietf-eman-requirements-12, February 2013. draft-ietf-eman-requirements-14, May 2013.
[EMAN-FMWK] Claise, B., Parello, J., Schoening, B., Quittek, J. [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., Quittek, J.
and Nordman, B, "Energy Management Framework", draft- and Nordman, B, "Energy Management Framework", draft-
ietf-eman-framework-07, February 2013. ietf-eman-framework-08, July 2013.
[EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T.,
Quittek, J. and B. Claise "Energy and Power Monitoring Quittek, J. and B. Claise "Energy and Power Monitoring
MIB ", draft-ietf-eman-energy-monitoring-mib-04, MIB ", draft-ietf-eman-energy-monitoring-mib-05, April
October 2012. 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-03, April 2013. draft-ietf-eman-applicability-statement-03, April 2013.
[EMAN-ENTITY] A. Bierman, D. Romascanu, J. Quittek and M. [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", draft-ietf- Chandramouli " Entity MIB (Version 4)", RFC 6933, May
eman-rfc4133bis-06, February 2013. 2013.
[EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology",
draft-parello-eman-definitions-07, work in progress,
October 2012.
[ACPI] "Advanced Configuration and Power Interface [ACPI] "Advanced Configuration and Power Interface
Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3
0b.pdf 0b.pdf
[DMTF] "Power State Management Profile DMTF DSP1027 Version [DMTF] "Power State Management Profile DMTF DSP1027 Version
2.0" December 2009 2.0" December 2009
http://www.dmtf.org/sites/default/files/standards/docum http://www.dmtf.org/sites/default/files/standards/docum
ents/DSP1027_2.0.0.pdf ents/DSP1027_2.0.0.pdf
 End of changes. 90 change blocks. 
438 lines changed or deleted 242 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/