draft-ietf-eman-energy-monitoring-mib-08.txt   draft-ietf-eman-energy-monitoring-mib-09.txt 
Network Working Group M. Chandramouli Network Working Group M. Chandramouli
B. Claise B. Claise
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended Status: Standards Track B. Schoening Intended Status: Standards Track B. Schoening
Expires: June 13, 2014 Independent Consultant Expires: August 14 2014 Independent Consultant
J. Quittek J. Quittek
T. Dietz T. Dietz
NEC Europe Ltd. NEC Europe Ltd.
December 13, 2013 February 14, 2014
Power and Energy Monitoring MIB Power and Energy Monitoring MIB
draft-ietf-eman-energy-monitoring-mib-08 draft-ietf-eman-energy-monitoring-mib-09
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 38 skipping to change at page 1, line 38
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed The list of Internet-Draft Shadow Directories can be accessed
at http://www.ietf.org/shadow.html at http://www.ietf.org/shadow.html
This Internet-Draft will expire on June 2014. This Internet-Draft will expire on August 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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.............................................. 4 4. Terminology............................................... 4
5. Architecture Concepts Applied to the MIB Modules......... 5 5. Architecture Concepts Applied to the MIB Modules.......... 5
5.1. Energy Object Information............................. 12 5.1. Energy Object Tables.................................... 5
5.2. Power State........................................... 13 5.1.1. ENERGY-OBJECT-MIB..................................... 5
5.2.1. Power State Set................................14 5.1.2. POWER-ATTRIBUTES-MIB.................................. 7
5.3. Energy Object Usage Information....................... 14 5.1.3. UML Diagram........................................... 9
5.4. Optional Power Usage Attributes....................... 15 5.2. Energy Object Identity................................. 11
5.5. Optional Energy Measurement........................... 15 5.3. Power State............................................ 12
5.6. Fault Management...................................... 19 5.3.1. Power State Set.................................13
6. Discovery............................................... 20 5.4. Energy Object Usage Information........................ 13
7. Link with the other IETF MIBs........................... 21 5.5. Optional Power Usage Attributes........................ 14
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..21 5.6. Optional Energy Measurement............................ 14
7.2. Link with the ENTITY-STATE MIB......................22 5.7. Fault Management....................................... 18
7.3. Link with the POWER-OVER-ETHERNET MIB...............22 6. Discovery................................................ 18
7.4. Link with the UPS MIB...............................23 7. Link with the other IETF MIBs............................ 19
7.5. Link with the LLDP and LLDP-MED MIBs................24 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB...19
8. Implementation Scenario................................. 25 7.2. Link with the ENTITY-STATE MIB.......................20
9. Structure of the MIB.................................... 27 7.3. Link with the POWER-OVER-ETHERNET MIB................21
10. MIB Definitions........................................ 28 7.4. Link with the UPS MIB................................21
11. Implementation Status.................................. 69 7.5. Link with the LLDP and LLDP-MED MIBs.................22
11.1. SNMP Research........................................ 70 8. Structure of the MIB..................................... 23
11.2. Cisco Systems........................................ 70 9. MIB Definitions.......................................... 24
12. Security Considerations................................ 71 10. Implementation Status................................... 62
13. IANA Considerations.................................... 72 10.1. SNMP Research......................................... 62
14. Contributors........................................... 73 10.2. Cisco Systems......................................... 62
12. Acknowledgment......................................... 73 11. Security Considerations................................. 63
13. References............................................. 74 12. IANA Considerations..................................... 64
13.1. Normative References...............................74 13. Contributors............................................ 64
13.2. Informative References.............................75 14. Acknowledgment.......................................... 65
15. References.............................................. 65
15.1. Normative References.................................. 65
15.2. Informative References................................ 66
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
Requirements for Energy Management [RFC6988]. the Requirements for Energy Management [RFC6988].
Energy management is applicable to devices in communication Energy management can be applied to devices in communication
networks. Target devices for this specification include (but are networks. Target devices for this specification include (but are
not limited to): routers, switches, Power over Ethernet (PoE) not limited to): routers, switches, Power over Ethernet (PoE)
endpoints, protocol gateways for building management systems, endpoints, protocol gateways for building management systems,
intelligent meters, home energy gateways, hosts and servers, intelligent meters, home energy gateways, hosts and servers,
sensor proxies, etc. Target devices and the use cases for Energy sensor proxies, etc. Target devices and the use cases for Energy
Management are discussed in Energy Management Applicability Management are discussed in Energy Management Applicability
Statement [EMAN-AS]. Statement [EMAN-AS].
Where applicable, device monitoring extends to the individual Where applicable, device monitoring extends to the individual
components of the device and to any attached dependent devices. components of the device and to any attached dependent devices.
skipping to change at page 4, line 33 skipping to change at page 4, line 31
Requirements for power and energy monitoring for networking Requirements for power and energy monitoring for networking
devices are specified in [RFC6988]. The requirements in devices are specified in [RFC6988]. The requirements in
[RFC6988] cover devices typically found in communications [RFC6988] cover devices typically found in communications
networks, such as switches, routers, and various connected networks, such as switches, routers, and various connected
endpoints. For a power monitoring architecture to be useful, it endpoints. For a power monitoring architecture to be useful, it
should also apply to facility meters, power distribution units, should also apply to facility meters, power distribution units,
gateway proxies for commercial building control, home automation gateway proxies for commercial building control, home automation
devices, and devices that interface with the utility and/or devices, and devices that interface with the utility and/or
smart grid. Accordingly, the scope of the MIB modules in this smart grid. Accordingly, the scope of the MIB modules in this
document is broader than that specified in [RFC6988]. Several document are broader than that specified in [RFC6988]. Several
use cases for Energy Management have been identified in the use cases for Energy Management have been identified in the
"Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An "Energy Management (EMAN) Applicability Statement" [EMAN-AS].
illustrative example scenario is presented in Section 8.
4. Terminology 4. Terminology
Please refer to [EMAN-FMWK] for the definitions of the Please refer to [EMAN-FMWK] for the definitions of the
following terminology used in this draft. following terminology used in this draft.
Energy Management Energy Management
Energy Management System (EnMS) Energy Management System (EnMS)
Energy Monitoring Energy Monitoring
Energy Control Energy Control
electrical equipment electrical equipment
non-electrical equipment (mechanical equipment) non-electrical equipment (mechanical equipment)
device device
component component
power inlet power inlet
power outlet power outlet
energy energy
power power
demand demand
provide energy provide energy
receive energy receive energy
meter (energy meter) meter (energy meter)
battery battery
Power Interface Power Interface
Nameplate Power Nameplate Power
Power Attributes Power Attributes
Power Quality Power Quality
Power State Power State
Power State Set Power State Set
5. Architecture Concepts Applied to the MIB Modules 5. Architecture Concepts Applied to the MIB Modules
This section describes the concepts specified in the Energy This section describes the concepts specified in the Energy
Management Framework [EMAN-FMWK] that pertain to power usage, Management Framework [EMAN-FMWK] that pertain to power usage,
with specific information related to the MIB module specified in with specific information related to the MIB module specified in
this document. This subsection maps to the different concepts this document. This subsection maps concepts developed in the
developed in the Energy Management Framework [EMAN-FMWK]. Energy Management Framework [EMAN-FMWK].
The Energy Monitoring MIB has 2 independent MIB modules ENERGY- The Energy Monitoring MIB has 2 independent MIB modules, ENERGY-
OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first MIB module OBJECT-MIB and POWER-ATTRIBUTES-MIB. The first, ENERGY-OBJECT-
ENERGY-OBJECT-MIB is focused on measurement of power and energy. MIB, is focused on measurement of power and energy. The second,
The second MIB module POWER-ATTRIBUTES-MIB is focused on Power POWER-ATTRIBUTES-MIB, is focused on power quality measurements
Attributes measurements for Energy Objects. for Energy Objects.
Devices and their sub-components can be modeled using the Devices and their sub-components can be modeled using the
containment tree of the ENTITY-MIB [RFC6933]. In addition, containment tree of the ENTITY-MIB [RFC6933].
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB] provides a
framework for modeling the relationship between Energy Objects.
It is conceivable to have implementations of ENERGY-OBJECT-
CONTEXT-MIB and ENERGY-OBJECT-MIB for modeling the relationships
between Energy Objects and also monitoring the Energy
consumption of those Energy Objects. In some situations, it is
possible to have implementation of ENERGY-OBJECT-MIB along
ENTITY-MIB V4 [RFC6933] with the Module compliance of
entity4CRCompliance. This compliance requires that the
following 3 MIB objects from ENTITY-MIB [RFC6933]
(entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be
implemented.
The ENERGY-OBJECT-MIB MIB module consists of five tables. 5.1. Energy Object Tables
5.1.1. ENERGY-OBJECT-MIB
The ENERGY-OBJECT-MIB module consists of five tables.
The first table is the eoMeterCapabilitiesTable. It indicates The first table is the eoMeterCapabilitiesTable. It indicates
the instrumentation available for each Energy Object. Thus, the the instrumentation available for each Energy Object. Entries
entries in this table indicate to the EnMS which other tables in this table indicate which other tables from the ENERGY-
from the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are OBJECT-MIB and POWER-ATTRIBUTES-MIB are available for each
available for each Energy Object. The eoMeterCapabilitiesTable Energy Object. The eoMeterCapabilitiesTable is indexed by
is indexed by entPhysicalIndex [RFC6933]. entPhysicalIndex [RFC6933].
The second table is the eoPowerTable. It returns the power The second table is the eoPowerTable. It reports the power
consumption of each Energy Object, as well as the units, sign, consumption of each Energy Object, as well as the units, sign,
measurement accuracy, and related objects. The eoPowerTable is measurement accuracy, and related objects. The eoPowerTable is
indexed by entPhysicalIndex. indexed by entPhysicalIndex.
The third table is the eoPowerStateTable. For each Energy The third table is the eoPowerStateTable. For each Energy
Object, it provides information and statistics about the Object, it reports information and statistics about the
supported Power States. The eoPowerStateTable is indexed by supported Power States. The eoPowerStateTable is indexed by
entPhysicalIndex and eoPowerStateIndex. entPhysicalIndex and eoPowerStateIndex.
The fourth table is the eoEnergyParametersTable. The entries in The fourth table is the eoEnergyParametersTable. The entries in
this table configure the parameters of energy and demand this table configure the parameters of energy and demand
measurement collection. This table is indexed by measurement collection. This table is indexed by
eoEnergyParametersIndex. eoEnergyParametersIndex.
The fifth table is the eoEnergyTable. The entries in this table The fifth table is the eoEnergyTable. The entries in this table
provide the log the energy and demand information. This table provide a log of the energy and demand information. This table
is indexed by eoEnergyParametersIndex. is indexed by eoEnergyParametersIndex.
A "smidump-style" tree presentation of the MIB modules contained
in the draft is presented. The meaning of the three symbols in
is a compressed representation of the object's MAX-ACCESS clause
which may have the following values:
"not-accessible"->"---"
"accessible-for-notify"->"--n"
"read-only"->"r-n"
"read-write"->"rwn"
eoMeterCapabilitiesTable(1) eoMeterCapabilitiesTable(1)
| |
+---eoMeterCapabilitiesEntry(1)[entPhysicalIndex] +---eoMeterCapabilitiesEntry(1)[entPhysicalIndex]
| | | |
| +---r-n BITS eoMeterCapability | +---r-n BITS eoMeterCapability
| |
eoPowerTable(2) eoPowerTable(2)
| |
+---eoPowerEntry(1) [entPhysicalIndex] +---eoPowerEntry(1) [entPhysicalIndex]
| | | |
| +---r-n Integer32 eoPower(1) | +---r-n Integer32 eoPower(1)
| +-- r-n Integer32 eoPowerNamePlate(2) | +-- r-n Integer32 eoPowerNamePlate(2)
| +-- r-n UnitMultiplier eoPowerUnitMultiplier(3) | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3)
| +-- r-n Integer32 eoPowerAccuracy(4) | +-- r-n Integer32 eoPowerAccuracy(4)
| +-- r-n INTEGER eoMeasurementCaliber(5) | +-- r-n INTEGER eoPowerMeasurementCaliber(5)
| +-- r-n INTEGER eoPowerCurrentType(6) | +-- r-n INTEGER eoPowerCurrentType(6)
| +-- r-n INTEGER eoPowerOrigin(7) | +-- r-n TruthValue eoPowerMeasurementLocal(7)
| +-- rwn IANAPowerStateSet eoPowerAdminState(8) | +-- rwn IANAPowerStateSet eoPowerAdminState(8)
| +-- r-n IANAPowerStateSet eoPowerOperState(9) | +-- r-n IANAPowerStateSet eoPowerOperState(9)
| +-- r-n OwnerString eoPowerStateEnterReason(10) | +-- r-n OwnerString eoPowerStateEnterReason(10)
| |
| |
+---eoPowerStateTable(3) +---eoPowerStateTable(3)
| +--eoPowerStateEntry(1) | +--eoPowerStateEntry(1)
| | [entPhysicalIndex, eoPowerStateIndex] | | [entPhysicalIndex, eoPowerStateIndex]
| | | |
| +-- --n IANAPowerStateSet eoPowerStateIndex(1) | +-- --n IANAPowerStateSet eoPowerStateIndex(1)
| +-- r-n Interger32 eoPowerStateMaxPower(2) | +-- r-n Integer32 eoPowerStateMaxPower(2)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoPowerStatePowerUnitMultiplier(3) | eoPowerStatePowerUnitMultiplier(3)
| +-- r-n TimeTicks eoPowerStateTotalTime(4) | +-- r-n TimeTicks eoPowerStateTotalTime(4)
| +-- r-n Counter32 eoPowerStateEnterCount(5) | +-- r-n Counter32 eoPowerStateEnterCount(5)
| |
+eoEnergyParametersTable(4) +eoEnergyParametersTable(4)
+---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex]
| |
| +-- --n PhysicalIndex eoEnergyObjectIndex(1) | +-- --n PhysicalIndex eoEnergyObjectIndex(1)
| + r-n Integer32 eoEnergyParametersIndex(2) | + r-n Integer32 eoEnergyParametersIndex(2)
| +-- r-n TimeInterval eoEnergyParametersIntervalLength(3) | +-- r-n TimeInterval eoEnergyParametersIntervalLength(3)
| +-- r-n Integer32 eoEnergyParametersIntervalNumber(4) | +-- r-n Integer32 eoEnergyParametersIntervalNumber(4)
| +-- r-n Integer32 eoEnergyParametersIntervalMode(5) | +-- r-n INTEGER eoEnergyParametersIntervalMode(5)
| +-- r-n TimeInterval eoEnergyParametersIntervalWindow(6) | +-- r-n TimeInterval eoEnergyParametersIntervalWindow(6)
| +-- r-n Integer32 eoEnergyParametersSampleRate(7) | +-- r-n Integer32 eoEnergyParametersSampleRate(7)
| +-- r-n RowStatus eoEnergyParametersStatus(8) | +-- r-n RowStatus eoEnergyParametersStatus(8)
| |
+eoEnergyTable(5) +eoEnergyTable(5)
+---eoEnergyEntry(1) +---eoEnergyEntry(1)
| [eoEnergyParametersIndex,eoEnergyCollectionStartTime] | [eoEnergyParametersIndex,eoEnergyCollectionStartTime]
| |
| +-- r-n TimeTicks eoEnergyCollectionStartTime(1) | +-- r-n TimeTicks eoEnergyCollectionStartTime(1)
| +-- r-n Integer32 eoEnergyConsumed(2) | +-- r-n Integer32 eoEnergyConsumed(2)
| +-- r-n Integer32 eoEnergyProvided(3) | +-- r-n Integer32 eoEnergyProvided(3)
| +-- r-n Integer32 eoEnergyStored(4) | +-- r-n Integer32 eoEnergyStored(4)
| +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5) | +-- r-n UnitMultiplier eoEnergyUnitMultiplier(5)
| +-- r-n Integer32 eoEnergyAccuracy(6) | +-- r-n Integer32 eoEnergyAccuracy(6)
| +-- r-n Integer32 eoEnergyMaxConsumed(7) | +-- r-n Integer32 eoEnergyMaxConsumed(7)
| +-- r-n Integer32 eoEnergyMaxProduced(8) | +-- r-n Integer32 eoEnergyMaxProduced(8)
| +-- r-n TimeTicks eoEnergyDiscontinuityTime(9) | +-- r-n TimeTicks eoEnergyDiscontinuityTime(9)
The powerAttributesMIB consists of four tables. 5.1.2. POWER-ATTRIBUTES-MIB
eoACPwrAttributesTable is indexed by entPhysicalIndex.
eoACPwrAttributesPhaseTable is indexed by entPhysicalIndex and The POWER-ATTRIBUTES-MIB module consists of three tables.
eoPhaseIndex. eoACPwrAttributesWyePhaseTable and
eoACPwrAttributesDelPhaseTable are indexed by entPhysicalIndex The first table is the eoACPwrAttributesTable. It indicates the
and eoPhaseIndex. power quality available for each Energy Object. The
eoACPwrAttributesTable is indexed by entPhysicalIndex [RFC6933].
The second table is the eoACPwrAttributesDelPhaseTable. The
entries in this table configure the parameters of energy and
demand measurement collection. This table is indexed by
eoEnergyParametersIndex.
The third table is the eoACPwrAttributesWyePhaseTable. For each
Energy Object, it reports information and statistics about the
supported Power States. The eoPowerStateTable is indexed by
entPhysicalIndex and eoPowerStateIndex.
eoACPwrAttributesTable(1) eoACPwrAttributesTable(1)
| |
+---eoACPwrAttributesEntry(1) [ entPhysicalIndex] +---eoACPwrAttributesEntry(1) [ entPhysicalIndex]
| | | |
| +---r-n INTEGER eoACPwrAttributesConfiguration(1) | +---r-n INTEGER eoACPwrAttributesConfiguration(1)
| +-- r-n Interger32 eoACPwrAttributesAvgVoltage(2) | +-- r-n Integer32 eoACPwrAttributesAvgVoltage(2)
| +-- r-n Integer32 eoACPwrAttributesAvgCurrent(3) | +-- r-n Integer32 eoACPwrAttributesAvgCurrent(3)
| +-- r-n Integer32 eoACPwrAttributesFrequency(4) | +-- r-n Integer32 eoACPwrAttributesFrequency(4)
| +-- r-n UnitMultiplier | +-- r-n UnitMultiplier
| eoACPwrAttributesPowerUnitMultiplier(5) | eoACPwrAttributesPowerUnitMultiplier(5)
| +-- r-n Integer32 eoACPwrAttributesPowerAccuracy(6) | +-- r-n Integer32 eoACPwrAttributesPowerAccuracy(6)
| +-- r-n Interger32 | +-- r-n Integer32
| eoACPwrAttributesTotalActivePower(7) | eoACPwrAttributesTotalActivePower(7)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrAttributesTotalReactivePower(8) | eoACPwrAttributesTotalReactivePower(8)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrAttributesTotalApparentPower(9) | eoACPwrAttributesTotalApparentPower(9)
| +-- r-n Integer32 | +-- r-n Integer32
| eoACPwrAttributesTotalPowerFactor(10) | eoACPwrAttributesTotalPowerFactor(10)
| +-- r-n Integer32 eoACPwrAttributesThdAmpheres(11) | +-- r-n Integer32 eoACPwrAttributesThdCurrent(11)
| +-- r-n Integer32 eoACPwrAttributesThdVoltage(12)
| |
+eoACPwrAttributesPhaseTable(2) +eoACPwrAttributesDelPhaseTable(2)
+---EoACPwrAttributesPhaseEntry(1) +-- eoACPwrAttributesDelPhaseEntry(1)
| | [ entPhysicalIndex, eoPhaseIndex] | | [entPhysicalIndex, eoACPwrAttributesDelPhaseIndex]
| | | |
| +-- r-n Integer32 eoPhaseIndex(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseAvgCurrent(2) | | eoACPwrAttributesDelPhaseIndex(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseActivePower(3) | | eoACPwrAttributesDelPhaseToNextPhaseVoltage(2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseReactivePower(4) | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(3)
| |
+eoACPwrAttributesWyePhaseTable(3)
+-- eoACPwrAttributesWyePhaseEntry(1)
| | [entPhysicalIndex, eoACPwrAttributesWyePhaseIndex]
| |
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseApparentPower(5) | | eoACPwrAttributesWyePhaseIndex(1)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhasePowerFactor(6) | | eoACPwrAttributesWyePhaseToNeutralVoltage(2)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesPhaseImpedance(7) | | eoACPwrAttributesWyeCurrent(3)
| |
+eoACPwrAttributesDelPhaseTable(3)
+-- eoACPwrAttributesDelPhaseEntry(1)
| | [entPhysicalIndex, eoPhaseIndex]
| |
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage(1) | | eoACPwrAttributesWyeActivePower(4)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(2) | | eoACPwrAttributesWyeReactivePower(5)
| +-- r-n Integer32 | +-- r-n Integer32
eoACPwrAttributesDelThdCurrent(3) | | eoACPwrAttributesWyeApparentPower(6)
| |
+eoACPwrAttributesWyePhaseTable(4)
+-- eoACPwrAttributesWyePhaseEntry(1)
| | [entPhysicalIndex, eoPhaseIndex]
| |
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyePhaseToNeutralVoltage(1) | | eoACPwrAttributesWyePowerFactor(7)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyePhaseCurrent(2) | | eoACPwrAttributesWyeThdCurrent(9)
| +-- r-n Integer32 | +-- r-n Integer32
| | eoACPwrAttributesWyeThdPhaseToNeutralVoltage(3) | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage(10)
| .
A UML representation of the MIB objects in the two MIB modules 5.1.3. UML Diagram
ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are presented.
A UML diagram representation of the MIB objects in the two MIB
modules ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB is presented.
+-----------------------+
| Meter Capabilities |
| --------------------- |
| eoMeterCapability |
+-----------------------+
+-------------------------+
| Energy Object State |
| ----------------------- |
| eoPowerAdminState |
| eoPowerOperState |
| eoPowerStateEnterReason |
+-------------------------+
|
|
v
+-----------------------+ +-----------------------+
|---> | Energy Object ID (*) | |---> | Energy Object ID (*) |
| | --------------------- | | | --------------------- |
| | entPhysicalIndex | | | entPhysicalIndex |
| | entPhysicalClass |
| | entPhysicalName | | | entPhysicalName |
| | entPhysicalUUID | | | entPhysicalUUID |
| +-----------------------+ | +-----------------------+
| | |
| +-----------------------------+
|---- | Energy Object Measurement |
| | --------------------------- |
| | eoPower |
| | eoPowerUnitMultiplier |
| | eoPowerAccuracy |
| +-----------------------------+
|
| +---------------------------+ | +---------------------------+
|---- | Energy Object Attributes | |---- | Power Table |
| | ------------------------- | | | ------------------------- |
| | eoPower |
| | eoPowerNamePlate | | | eoPowerNamePlate |
| | eoPowerUnitMultiplier |
| | eoPowerAccuracy |
| | eoPowerMeasurementCaliber | | | eoPowerMeasurementCaliber |
| | eoPowerCurrentType | | | eoPowerCurrentType |
| | eoPowerOrigin | | | eoPowerMeasurementLocal |
| | eoPowerAdminState |
| | eoPowerOperState |
| | eoPowerStateEnterReason |
| +---------------------------+ | +---------------------------+
| |
| +---------------------------------+ | +---------------------------------+
|---- | Energy Object State Statistics | |---- | Energy Object State Statistics |
|-------------------------------- | | |-------------------------------- |
| eoPowerStateMaxPower | | | eoPowerStateIndex |
| eoPowerStatePowerUnitMultiplier | | | eoPowerStateMaxPower |
| eoPowerStateTotalTime | | | eoPowerStatePowerUnitMultiplier |
| eoPowerStateEnterCount | | | eoPowerStateTotalTime |
+---------------------------------+ | | eoPowerStateEnterCount |
| +---------------------------------+
|
| +----------------------------------+
|---- | Energy ParametersTable |
| | -------------------------------- |
| | eoEnergyObjectIndex |
| | eoEnergyParametersIndex |
| | eoEnergyParametersIntervalLength |
| | eoEnergyParametersIntervalNumber |
| | eoEnergyParametersIntervalMode |
| | eoEnergyParametersIntervalWindow |
| | eoEnergyParametersSampleRate |
| | eoEnergyParametersStatus |
| +----------------------------------+
|
| +----------------------------------+
|---- | Energy Table |
| -------------------------------- |
| eoEnergyCollectionStartTime |
| eoEnergyConsumed |
| eoEnergyProvided |
| eoEnergyStored |
| eoEnergyUnitMultiplier |
| eoEnergyAccuracy |
| eoEnergyMaxConsumed |
| eoEnergyMaxProduced |
| eoDiscontinuityTime |
+----------------------------------+
Figure 1:UML diagram for energyObjectMIB Figure 1:UML diagram for energyObjectMib
(*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
+----------------------------------+
| Energy ParametersTable |
| -------------------------------- |
| eoEnergyObjectIndex |
| eoEnergyParametersIndex |
| eoEnergyParametersIntervalLength |
| eoEnergyParametersIntervalNumber |
| eoEnergyParametersIntervalMode |
| eoEnergyParametersIntervalWindow |
| eoEnergyParametersSampleRate |
| eoEnergyParametersStatus |
+----------------------------------+
|
V
+----------------------------------+
| Energy Table |
| -------------------------------- |
| eoEnergyCollectionStartTime |
| eoEnergyConsumed |
| eoEnergyProvided |
| eoEnergyStored |
| eoEnergyUnitMultiplier |
| eoEnergyAccuracy |
| eoEnergyMaxConsumed |
| eoEnergyMaxProduced |
| eoDiscontinuityTime |
+----------------------------------+
+-----------------------+ +-----------------------+
|---> | Energy Object ID (*) | |---> | Energy Object ID (*) |
| | --------------------- | | | --------------------- |
| | entPhysicalIndex | | | entPhysicalIndex |
| | entPhysicalName | | | entPhysicalName |
| | entPhysicalUUID | | | entPhysicalUUID |
| +-----------------------+ | +-----------------------+
| |
| +--------------------------------------+ | +--------------------------------------+
|---- | Power Attributes | |---- | Power Attributes |
skipping to change at page 12, line 6 skipping to change at page 11, line 16
| | eoACPwrAttributesConfiguration | | | eoACPwrAttributesConfiguration |
| | eoACPwrAttributesAvgVoltage | | | eoACPwrAttributesAvgVoltage |
| | eoACPwrAttributesAvgCurrent | | | eoACPwrAttributesAvgCurrent |
| | eoACPwrAttributesFrequency | | | eoACPwrAttributesFrequency |
| | eoACPwrAttributesPowerUnitMultiplier | | | eoACPwrAttributesPowerUnitMultiplier |
| | eoACPwrAttributesPowerAccuracy | | | eoACPwrAttributesPowerAccuracy |
| | eoACPwrAttributesTotalActivePower | | | eoACPwrAttributesTotalActivePower |
| | eoACPwrAttributesTotalReactivePower | | | eoACPwrAttributesTotalReactivePower |
| | eoACPwrAttributesTotalApparentPower | | | eoACPwrAttributesTotalApparentPower |
| | eoACPwrAttributesTotalPowerFactor | | | eoACPwrAttributesTotalPowerFactor |
| | eoACPwrAttributesThdAmpheres | | | eoACPwrAttributesThdCurrent |
| +--------------------------------------+ | | eoACPwrAttributesThdVoltage |
|
|
| +--------------------------------------+
|---- | Power Phase Attributes |
| | ------------------------------------ |
| | eoPhaseIndex |
| | eoACPwrAttributesPhaseAvgCurrent |
| | eoACPwrAttributesPhaseActivePower |
| | eoACPwrAttributesPhaseReactivePower |
| | eoACPwrAttributesPhaseApparentPower |
| | eoACPwrAttributesPhasePowerFactor |
| | eoACPwrAttributesPhaseImpedance |
| +--------------------------------------+ | +--------------------------------------+
| |
| |
| +------------------------------------------------+ | +------------------------------------------------+
|---- | AC Input DEL Configuration | |---- | AC Input DEL Configuration |
| | ---------------------------------------------- | | | ---------------------------------------------- |
| | eoACPwrAttributesDelPhaseIndex |
| | eoACPwrAttributesDelPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage | | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage |
| | eoACPwrAttributesDelThdCurrent |
| +------------------------------------------------+ | +------------------------------------------------+
| |
| |
| +----------------------------------------------+ | +----------------------------------------------+
|---- | AC Input WYE Configuration | |---- | AC Input WYE Configuration |
| -------------------------------------------- | | -------------------------------------------- |
| eoACPwrAttributesWyePhaseIndex |
| eoACPwrAttributesWyePhaseToNeutralVoltage | | eoACPwrAttributesWyePhaseToNeutralVoltage |
| eoACPwrAttributesWyePhaseCurrent | | eoACPwrAttributesWyeCurrent |
| eoACPwrAttributesWyeActivePower |
| eoACPwrAttributesWyeReactivePower |
| eoACPwrAttributesWyeApparentPower |
| eoACPwrAttributesWyePowerFactor |
| eoACPwrAttributesWyeThdCurrent |
| eoACPwrAttributesWyeThdPhaseToNeutralVoltage | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage |
+----------------------------------------------+ +----------------------------------------------+
Figure 2: UML diagram for the powerAttributesMIB Figure 2: UML diagram for the POWER-ATTRIBUTES-MIB
(*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB (*) Compliance with the ENERGY-OBJECT-CONTEXT-MIB
5.1. Energy Object Information 5.2. Energy Object Identity
The Energy Object identity information is specified in the The Energy Object identity information is specified in the
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB] primary ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB] primary table,
table, i.e. the eoTable. In this table, the context of the i.e., the eoTable. In this table, Energy Object context such as
Energy Object such as domain, role description, importance are domain, role description, and importance are specified. In
specified. In addition, the ENERGY-OBJECT-CONTEXT-MIB module addition, the ENERGY-OBJECT-CONTEXT-MIB module specifies the
specifies the relationship between Energy Objects. There are relationship between Energy Objects. There are several possible
several possible relationships between Energy Objects such as relationships between Energy Objects, such as meteredBy,
meteredBy, metering, poweredBy, powering, aggregatedBy, and metering, poweredBy, powering, aggregatedBy, and aggregating as
aggregating as defined in the IANA-ENERGY-RELATION-MIB MIB defined in the IANA-ENERGY-RELATION-MIB module [EMAN-AWARE-MIB].
module [EMAN-AWARE-MIB].
5.2. Power State 5.3. Power State
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 Power States.
Power States, which represent universal states of power Power States, which represent universal states of power
management of an Energy Object, are specified by the management of an Energy Object, are specified by the
eoPowerState MIB object. The actual Power State is specified by eoPowerState MIB object. The actual Power State is specified by
the eoPowerOperState MIB object, while the eoPowerAdminState MIB the eoPowerOperState MIB object, while the eoPowerAdminState MIB
object specifies the Power State requested for the Energy object specifies the Power State requested for the Energy
Object. The difference between the values of eoPowerOperState Object. The difference between the values of eoPowerOperState
and eoPowerAdminState can be attributed that the Energy Object and eoPowerAdminState indicate that the Energy Object is busy
is busy transitioning from eoPowerAdminState into the transitioning from eoPowerAdminState into the eoPowerOperState,
eoPowerOperState, at which point it will update the content of at which point it will update the content of eoPowerOperState.
eoPowerOperState. In addition, the possible reason for change In addition, the possible reason for change in Power State is
in Power State is reported in eoPowerStateEnterReason. reported in eoPowerStateEnterReason. Regarding
Regarding eoPowerStateEnterReason, management stations and eoPowerStateEnterReason, management stations and Energy Objects
Energy Objects should support any format of the owner string should support any format of the owner string dictated by the
dictated by the local policy of the organization. It is local policy of the organization. It is suggested that this
suggested that this name contain at least the reason for the name contain at least the reason for the transition change, and
transition change, and one or more of the following: IP address, one or more of the following: IP address, management station
management station name, network manager's name, location, or name, network manager's name, location, or phone number.
phone number.
The MIB objects eoPowerOperState, eoPowerAdminState , and The MIB objects eoPowerOperState, eoPowerAdminState , and
eoPowerStateEnterReason are contained in the eoPowerTable MIB eoPowerStateEnterReason are contained in the eoPowerTable MIB
table. table.
The eoPowerStateTable table enumerates the maximum power usage The eoPowerStateTable table enumerates the maximum power usage
in watts, for every single supported Power State of each Power in watts for every single supported Power State of each Power
State Set supported by the Energy Object. In addition, State Set supported by the Energy Object. In addition,
PowerStateTable provides additional statistics: PowerStateTable provides additional statistics such as
eoPowerStateEnterCount, the number of times an entity has eoPowerStateEnterCount, i.e., the number of times an entity has
visited a particular Power State, and eoPowerStateTotalTime, the visited a particular Power State, and eoPowerStateTotalTime,
total time spent in a particular Power State of an Energy i.e., the total time spent in a particular Power State of an
Object. Energy Object.
5.2.1. Power State Set 5.3.1. Power State Set
There are several standards and implementations of Power State There are several standards and implementations of Power State
Sets. An Energy Object can support one or multiple Power State Sets. An Energy Object can support one or multiple Power State
Set implementation(s) concurrently. Set implementations concurrently.
There are currently three Power State Sets advocated: There are currently three Power State Sets defined:
IEEE1621 - [IEEE1621] IEEE1621(256) - [IEEE1621]
DMTF - [DMTF] DMTF(512) - [DMTF]
EMAN - [EMAN-FMWK] EMAN(768) - [EMAN-FMWK]
The Power State Sets, along with each Power State within the The Power State Sets are listed in [EMAN-FMWK] along with each
Power Set are listed in [EMAN-FMWK]. Power State within the Power Set.
5.3. Energy Object Usage Information 5.4. Energy Object Usage Information
For an Energy Object, power usage is reported using eoPower. For an Energy Object, power usage is reported using eoPower.
The magnitude of measurement is based on the The magnitude of measurement is based on the
eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier
Textual Convention (TC). Power measurement magnitude should Textual Convention (TC). Power measurement magnitude should
conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22
[IEC.62053-22] definition of unit multiplier for the SI (System [IEC.62053-22] definition of unit multiplier for the SI (System
International) units of measure. Measured values are International) units of measure. Measured values are
represented in SI units obtained by BaseValue * 10 raised to the represented in SI units obtained by BaseValue * 10 raised to the
power of the scale. power of the unit multiplier.
For example, if current power usage of an Energy Object is 3, it For example, if current power usage of an Energy Object is 3, it
could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of
eoPowerUnitMultiplier. Note that other measurements throughout eoPowerUnitMultiplier. Note that other measurements throughout
the two MIB modules in this document use the same mechanism, the two MIB modules in this document use the same mechanism,
including eoPowerStatePowerUnitMultiplier, including eoPowerStatePowerUnitMultiplier,
eoEnergyUnitMultiplier, and eoEnergyUnitMultiplier, and
eoACPwrAttributesPowerUnitMultiplier. eoACPwrAttributesPowerUnitMultiplier.
In addition to knowing the usage and magnitude, it is useful to In addition to knowing the usage and magnitude, it is useful to
know how a eoPower measurement was obtained. An NMS can use know how an eoPower measurement was obtained. An NMS can use
this to account for the accuracy and nature of the reading this to account for the accuracy and nature of the reading
between different implementations. For this eoPowerOrigin between different implementations. For this
describes whether the measurements were made at the device eoPowerMeasurementLocal describes whether the measurements were
itself or from a remote source. The eoPowerMeasurementCaliber made at the device itself or from a remote source. The
describes the method that was used to measure the power and can eoPowerMeasurementCaliber describes the method that was used to
distinguish actual or estimated values. There may be devices in measure the power and can distinguish actual or estimated
the network, which may not be able to measure or report power values. There may be devices in the network, which may not be
consumption. For those devices, the object able to measure or report power consumption. For those devices,
eoPowerMeasurementCaliber shall report that measurement the object eoPowerMeasurementCaliber shall report that the
mechanism is "unavailable" and the eoPower measurement shall be measurement mechanism is "unavailable" and the eoPower
"0". measurement shall be "0".
The nameplate power rating of an Energy Object is specified in The nameplate power rating of an Energy Object is specified in
eoPowerNameplate MIB object. eoPowerNameplate MIB object.
5.4. Optional Power Usage Attributes 5.5. Optional Power Usage Attributes
The optional powerAttributesMIB MIB module can be implemented to The optional POWER-ATTRIBUTES-MIB module can be implemented to
further describe power usage attributes measurement. The further describe power usage attributes measurement. The POWER-
powerAttributesMIB MIB module adheres closely to the IEC 61850 ATTRIBUTES-MIB module is aligned with IEC 61850 7-2 standard to
7-2 standard to describe AC measurements. describe AC measurements.
The powerAttributesMIB MIB module contains a primary table, the The POWER-ATTRIBUTES-MIB module contains a primary table,
eoACPwrAttributesTable table, that defines power attributes eoACPwrAttributesTable, 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, an additional table is populated with
additional table is populated with Power Attributes measurements Power Attributes measurements per phase (hence, double indexed
per phase (so double indexed by the entPhysicalIndex and by the entPhysicalIndex and a phase index). This table,
eoPhaseIndex). This table, which describes attributes common to describes attributes specific to either WYE or DEL
both WYE and DEL configurations, contains the average current, configurations.
active/reactive/apparent power, power factor, and impedance.
In case of 3-phase power with a DEL configuration, the In a DEL configuration, the eoACPwrAttributesDelPhaseTable
eoACPwrAttributesDelPhaseTable table describes the phase-to- describes the phase-to-phase power attributes measurements,
phase power attributes measurements, i.e., voltage and current. i.e., voltage. In a DEL configuration, the current is equal in
all three phases.
In case of 3-phase power with a WYE configuration, the In a WYE configuration, the eoACPwrAttributesWyePhaseTable
eoACPwrAttributesWyePhaseTable table describes the phase-to- describes the phase-to-neutral power attributes measurements,
neutral power attributes measurements, i.e., voltage and i.e., voltage, current, active/reactive/apparent power, and
current. power factor.
5.5. Optional Energy Measurement 5.6. Optional Energy Measurement
It is relevant to measure energy and demand only when there are It is only relevant to measure energy and demand when there are
actual power measurements obtained from measurement hardware. If actual power measurements obtained from measurement hardware. If
the eoPowerMeasurementCaliber MIB object has values of the eoPowerMeasurementCaliber MIB object has values of
unavailable, unknown, estimated, or presumed, then the energy unavailable, unknown, estimated, or presumed, then the energy
and demand values are not useful. and demand values are not useful.
Two tables are introduced to characterize energy measurement of Two tables are introduced to characterize energy measurement of
an Energy Object: eoEnergyTable and eoEnergyParametersTable. an Energy Object: eoEnergyTable and eoEnergyParametersTable.
Both energy and demand information can be represented via the Both energy and demand information can be represented via the
eoEnergyTable. Energy information will be an accumulation with eoEnergyTable. Energy information will be an accumulation with
no interval. Demand information can be represented. no interval. Demand information can be represented.
The eoEnergyParametersTable consists of the parameters defining The eoEnergyParametersTable consists of the parameters defining
eoEnergyParametersIndex an index of that specifies the setting eoEnergyParametersIndex - an index of that specifies the setting
for collection of energy measurements for an Energy Object, for collection of energy measurements for an Energy Object,
eoEnergyObjectIndex linked to the entPhysicalIndex of the eoEnergyObjectIndex - linked to the entPhysicalIndex of the
Energy Object, the duration of measurement intervals in seconds, Energy Object, the duration of measurement intervals in seconds,
(eoEnergyParametersIntervalLength), the number of successive (eoEnergyParametersIntervalLength), the number of successive
intervals to be stored in the eoEnergyTable, intervals to be stored in the eoEnergyTable,
(eoEnergyParametersIntervalNumber), the type of measurement (eoEnergyParametersIntervalNumber), the type of measurement
technique (eoEnergyParametersIntervalMode), and a sample rate technique (eoEnergyParametersIntervalMode), and a sample rate
used to calculate the average (eoEnergyParametersSampleRate). used to calculate the average (eoEnergyParametersSampleRate).
Judicious choice of the sampling rate will ensure accurate Judicious choice of the sampling rate will ensure accurate
measurement of energy while not imposing an excessive polling measurement of energy while not imposing an excessive polling
burden. burden.
skipping to change at page 18, line 42 skipping to change at page 17, line 35
energy consumption. In order to indicate such interruptions, energy consumption. In order to indicate such interruptions,
the object eoEnergyDiscontinuityTime is provided for indicating the object eoEnergyDiscontinuityTime is provided for indicating
the time of the last interruption of total energy measurement. the time of the last interruption of total energy measurement.
eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418]
when the device was reset. when the device was reset.
The following example illustrates the eoEnergyTable and The following example illustrates the eoEnergyTable and
eoEnergyParametersTable: eoEnergyParametersTable:
First, in order to estimate energy, a time interval to sample First, in order to estimate energy, a time interval to sample
energy should be specified, i.e. energy should be specified, i.e.,
eoEnergyParametersIntervalLength can be set to "900 seconds" or eoEnergyParametersIntervalLength can be set to "900 seconds" or
15 minutes and the number of consecutive intervals over which 15 minutes and the number of consecutive intervals over which
the maximum energy is calculated the maximum energy is calculated
(eoEnergyParametersIntervalNumber) as "10". The sampling rate (eoEnergyParametersIntervalNumber) as "10". The sampling rate
internal to the Energy Object for measurement of power usage internal to the Energy Object for measurement of power usage
(eoEnergyParametersSampleRate) can be "1000 milliseconds", as (eoEnergyParametersSampleRate) can be "1000 milliseconds", as
set by the Energy Object as a reasonable value. Then, the set by the Energy Object as a reasonable value. Then, the
eoEnergyParametersStatus is set to active (value 1) to indicate eoEnergyParametersStatus is set to active to indicate that the
that the Energy Object should start monitoring the usage per 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
skipping to change at page 19, line 38 skipping to change at page 18, line 28
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
calculated. The first observed energy measurement value is calculated. The first observed energy measurement value is
taken to be the initial maximum. With each subsequent taken to be the initial maximum. With each subsequent
measurement, based on numerical comparison, maximum energy may measurement, based on numerical comparison, maximum energy may
be updated. The maximum value is retained as long as the be updated. The maximum value is retained as long as the
measurements are taking place. Based on periodic polling of measurements are taking place. Based on periodic polling of
this table, an NMS could compute the maximum over a longer this table, an NMS could compute the maximum over a longer
period, i.e. a month, 3 months, or a year. period, e.g., a month, 3 months, or a year.
5.6. Fault Management 5.7. Fault Management
[RFC6988] specifies requirements about Power States such as "the [RFC6988] specifies requirements about Power States such as "the
current Power State" , "the time of the last state change", "the current Power State" , "the time of the last state change", "the
total time spent in each state", "the number of transitions to total time spent in each state", "the number of transitions to
each state" etc. Some of these requirements are fulfilled each state" etc. Some of these requirements are fulfilled
explicitly by MIB objects such as eoPowerOperState, explicitly by MIB objects such as eoPowerOperState,
eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the
other requirements are met via the SNMP NOTIFICATION mechanism. other requirements are met via the SNMP NOTIFICATION mechanism.
eoPowerStateChange SNMP notification which is generated when the eoPowerStateChange SNMP notification which is generated when the
value(s) of ,eoPowerStateIndex, eoPowerOperState, value of oPowerStateIndex, eoPowerOperState, or
eoPowerAdminState have changed. eoPowerAdminState have changed.
6. Discovery 6. Discovery
It is foreseen that most Energy Objects will require the It is probable that most Energy Objects will require the
implementation of the ENERGY-OBJECT-CONTEXT-MIB MIB [EMAN-AWARE- implementation of the ENERGY-OBJECT-CONTEXT-MIB [EMAN-AWARE-MIB]
MIB] as a prerequisite for this MIB module. In such a case, as a prerequisite for this MIB module. In such a case,
eoPowerTable of the EMAN-MON-MIB is a sparse extension of the eoPowerTable of the EMAN-ENERGY-OBJECT-MIB is cross-referenced
eoTable of ENERGY-OBJECT-CONTEXT-MIB. Every Energy Object MUST with the eoTable of ENERGY-OBJECT-CONTEXT-MIB via
implement entPhysicalIndex, entPhysicalUUID and entPhysicalName entPhysicalIndex. Every Energy Object MUST implement
from the ENTITY-MIB [RFC6933]. As the primary index for the entPhysicalIndex, entPhysicalClass, entPhysicalName and
Energy Object, entPhysicalIndex is used: It characterizes the entPhysicalUUID from the ENTITY-MIB [RFC6933]. As the primary
Energy Object in the ENERGY-OBJECT-MIB and the POWER-ATTRIBUTES- index for the Energy Object, entPhysicalIndex is used: It
MIB MIB modules (this document). characterizes the Energy Object in the ENERGY-OBJECT-MIB and the
POWER-ATTRIBUTES-MIB MIB modules (this document).
The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module The NMS must first poll the ENERGY-OBJECT-CONTEXT-MIB MIB module
[EMAN-AWARE-MIB], if available, in order to discover all the [EMAN-AWARE-MIB], if available, in order to discover all the
Energy Objects and the relationships between those Energy Energy Objects and the relationships between those Energy
Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the Objects. In the ENERGY-OBJECT-CONTEXT-MIB module tables, the
Energy Objects are indexed by the entPhysicalIndex. Energy Objects are indexed by the entPhysicalIndex.
From there, the NMS must poll the eoPowerStateTable (specified From there, the NMS must poll the eoPowerStateTable (specified
in the ENERGY-OBJECT-MIB module in this document), which in the ENERGY-OBJECT-MIB module in this document), which
enumerates, amongst other things, the maximum power usage. As enumerates, amongst other things, the maximum power usage. As
the entries in eoPowerStateTable table are indexed by the the entries in eoPowerStateTable table are indexed by the
Energy Object ( entPhysicalIndex), by the Power State Set Energy Object ( entPhysicalIndex) and by the Power State Set
(eoPowerStateIndex), the maximum power usage is discovered per (eoPowerStateIndex), the maximum power usage is discovered per
Energy Object, and the power usage per Power State of the Power Energy Object, and the power usage per Power State of the Power
State Set. In other words, polling the eoPowerStateTable allows State Set. In other words, reading the eoPowerStateTable allows
the discovery of each Power State within every Power State Set the discovery of each Power State within every Power State Set
supported by the Energy Object. supported by the Energy Object.
If the Energy Object has an Aggregation Relationship with If the Energy Object is an Aggregator, the MIB module would be
another Energy Object, the MIB module would be populated with populated with the Energy Object relationship information, which
the Energy Object relationship information, which have their own have its own Energy Object index value (entPhysicalIndex).
Energy Object index value (entPhysicalIndex). However, the However, the Energy Object relationship must be discovered via
Energy Object relationship must be discovered thanks to the the ENERGY-OBJECT-CONTEXT-MIB module.
ENERGY-OBJECT-CONTEXT-MIB module.
Finally, the NMS can monitor the power attributes thanks to the Finally, the NMS can monitor the power attributes with the
powerAttributesMIB MIB module, which reuses the entPhysicalIndex POWER-ATTRIBUTES-MIB MIB module, which reuses the
to index the Energy Object. entPhysicalIndex to index the Energy Object.
7. Link with the other IETF MIBs 7. Link with the other IETF MIBs
7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB
RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the RFC 6933 [RFC6933] defines the ENTITY-MIB module that lists the
physical entities of a networking device (router, switch, etc.) physical entities of a networking device (router, switch, etc.)
and those physical entities indexed by entPhysicalIndex. From and those physical entities indexed by entPhysicalIndex. From
an energy-management standpoint, the physical entities that an energy-management standpoint, the physical entities that
consume or produce energy are of interest. consume or produce energy are of interest.
RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that
provides a standardized way of obtaining information (current provides a standardized way of obtaining information (current
value of the sensor, operational status of the sensor, and the value of the sensor, operational status of the sensor, and the
data units precision) from sensors embedded in networking data units precision) from sensors embedded in networking
devices. Sensors are associated with each index of devices. Sensors are associated with each index of
entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus entPhysicalIndex of the ENTITY-MIB [RFC6933]. While the focus
of the Power and Energy Monitoring MIB is on measurement of of the Power and Energy Monitoring MIB is on measurement of
power usage of networking equipment indexed by the ENTITY-MIB, power usage of networking equipment indexed by the ENTITY-MIB,
this MIB proposes a customized power scale for power measurement this MIB supports a customized power scale for power measurement
and different Power States of networking equipment, and and different Power States of networking equipment, and
functionality to configure the Power States. functionality to configure the Power States.
The Energy Objects are modeled by the entPhysicalIndex through The Energy Objects are modeled by the entPhysicalIndex through
the entPhysicalEntity MIB object specified in the eoTable in the the entPhysicalEntity MIB object specified in the eoTable in the
ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB]. ENERGY-OBJECT-CONTEXT-MIB MIB module [EMAN-AWARE-MIB].
The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x The ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x
accuracy classes required for electricity (i.e., 1%, 2%, 0.5% accuracy classes required for electricity (e.g., 1%, 2%, 0.5%
accuracy classes). Indeed, entPhySensorPrecision [RFC3433] accuracy classes). Indeed, entPhySensorPrecision [RFC3433]
represents "The number of decimal places of precision in fixed- represents "The number of decimal places of precision in fixed-
point sensor values returned by the associated entPhySensorValue point sensor values returned by the associated entPhySensorValue
object". The ANSI and IEC Standards are used for power object". The ANSI and IEC Standards are used for power
measurement and these standards require that we use an accuracy measurement and these standards require that we use an accuracy
class, not the scientific-number precision model specified in class, not the scientific-number precision model specified in
RFC3433. The eoPowerAccuracy MIB object models this accuracy. RFC3433. The eoPowerAccuracy MIB object models this accuracy.
Note that eoPowerUnitMultipler represents the scale factor per Note that eoPowerUnitMultipler represents the scale factor per
IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22],
which is a more logical representation for power measurements which is a more logical representation for power measurements
(compared to entPhySensorScale), with the mantissa and the (compared to entPhySensorScale), with the mantissa and the
exponent values X * 10 ^ Y. exponent values X * 10 ^ Y.
Power measurements specifying the qualifier 'UNITS' for each Power measurements specifying the qualifier 'UNITS' for each
measured value in watts are used in the LLDP-EXT-MED-MIB, POE measured value in watts are used in the LLDP-EXT-MED-MIB, POE
[RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier
is used for the power measurement values. is used for the power measurement values.
One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are
implemented for all Energy Objects that need to be monitored. A implemented for all Energy Objects that need to be monitored. A
typical example is a converged building gateway, monitoring typical example is a converged building gateway, which can
several other devices in the building, doing the proxy between monitor other devices in a building and provides a proxy between
SNMP and a protocol like BACNET. Another example is the home SNMP and a protocol like BACNET. Another example is the home
energy controller. In such cases, the eoPhysicalEntity value energy controller. In such cases, the eoPhysicalEntity value
contains the zero value, thanks to PhysicalIndexOrZero textual contains the zero value, using the PhysicalIndexOrZero textual
convention. convention.
The eoPower is similar to entPhySensorValue [RFC3433] and the The eoPower is similar to entPhySensorValue [RFC3433] and the
eoPowerUnitMultipler is similar to entPhySensorScale. eoPowerUnitMultipler is similar to entPhySensorScale.
7.2. Link with the ENTITY-STATE MIB 7.2. Link with the ENTITY-STATE MIB
For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE For each entity in the ENTITY-MIB [RFC6933], the ENTITY-STATE
MIB [RFC4268] specifies the operational states (entStateOper: MIB [RFC4268] specifies the operational states (entStateOper:
unknown, enabled, disabled, testing), the alarm (entStateAlarm: unknown, enabled, disabled, testing), the alarm (entStateAlarm:
unknown, underRepair, critical, major, minor, warning, unknown, underRepair, critical, major, minor, warning,
indeterminate) and the possible values of standby states indeterminate) and the possible values of standby states
(entStateStandby: unknown, hotStandby, coldStandby, (entStateStandby: unknown, hotStandby, coldStandby,
providingService). providingService).
From a power monitoring point of view, in contrast to the entity From a power monitoring point of view, in contrast to the entity
operational states of entities, Power States are required, as operational states of entities, Power States are required, as
proposed in the Power and Energy Monitoring MIB module. Those proposed in the Power and Energy Monitoring MIB module. Those
skipping to change at page 22, line 41 skipping to change at page 21, line 21
in the ENTITY-STATE MIB, if a formal mapping is required. For in the ENTITY-STATE MIB, if a formal mapping is required. For
example, the entStateStandby "unknown", "hotStandby", example, the entStateStandby "unknown", "hotStandby",
"coldStandby", states could map to the Power State "unknown", "coldStandby", states could map to the Power State "unknown",
"ready", "standby", respectively, while the entStateStandby "ready", "standby", respectively, while the entStateStandby
"providingService" could map to any "low" to "high" Power State. "providingService" could map to any "low" to "high" Power State.
7.3. Link with the POWER-OVER-ETHERNET MIB 7.3. Link with the POWER-OVER-ETHERNET MIB
Power-over-Ethernet MIB [RFC3621] provides an energy monitoring Power-over-Ethernet MIB [RFC3621] provides an energy monitoring
and configuration framework for power over Ethernet devices. and configuration framework for power over Ethernet devices.
The RFC introduces a concept of a port group on a switch to RFC 3621 defines a port group entity on a switch for power
define power monitoring and management policy and does not use monitoring and management policy and does not use the
the entPhysicalIndex as the index. Indeed, the entPhysicalIndex index. Indeed, pethMainPseConsumptionPower is
pethMainPseConsumptionPower is indexed by the indexed by the pethMainPseGroupIndex, which has no mapping with
pethMainPseGroupIndex, which has no mapping with the the entPhysicalIndex.
entPhysicalIndex.
One cannot assume that the Power-over-Ethernet MIB is
implemented for all Energy Objects that need to be monitored.
A typical example is a converged building gateway, monitoring
several other devices in the building, doing the proxy between
SNMP and a protocol like BACNET. Another example is the home
energy controller. In such cases, the eoethPortIndex and
eoethPortGrpIndex values contain the zero value, thanks to new
PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero
conventions.
However, if the Power-over-Ethernet MIB [RFC3621] is supported, If the Power-over-Ethernet MIB [RFC3621] is supported, the
the Energy Object eoethPortIndex and eoethPortGrpIndex contain Energy Object eoethPortIndex and eoethPortGrpIndex contain the
the pethPsePortIndex and pethPsePortGroupIndex, respectively. pethPsePortIndex and pethPsePortGroupIndex, respectively.
However, one cannot assume that the Power-over-Ethernet MIB is
implemented for most or all Energy Objects. In such cases, the
eoethPortIndex and eoethPortGrpIndex values contain the zero
value, via the new PethPsePortIndexOrZero and textual
PethPsePortGroupIndexOrZero conventions.
As a consequence, the entPhysicalIndex MIB object has been kept In either case, the entPhysicalIndex MIB object is used as the
as the unique Energy Object index. unique Energy Object index.
Note that, even though the Power-over-Ethernet MIB [RFC3621] was Note that, even though the Power-over-Ethernet MIB [RFC3621] was
created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse
the precision notion from the ENTITY-SENSOR MIB, i.e. the the precision notion from the ENTITY-SENSOR MIB, i.e., the
entPhySensorPrecision MIB object. entPhySensorPrecision MIB object.
7.4. Link with the UPS MIB 7.4. Link with the UPS MIB
To protect against unexpected power disruption, data centers and To protect against unexpected power disruption, data centers and
buildings make use of Uninterruptible Power Supplies (UPS). To buildings make use of Uninterruptible Power Supplies (UPS). To
protect critical assets, a UPS can be restricted to a particular protect critical assets, a UPS can be restricted to a particular
subset or domain of the network. UPS usage typically lasts only subset or domain of the network. UPS usage typically lasts only
for a finite period of time, until normal power supply is for a finite period of time, until normal power supply is
restored. Planning is required to decide on the capacity of the restored. Planning is required to decide on the capacity of the
skipping to change at page 24, line 10 skipping to change at page 22, line 28
(upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.)
- upsInput group: Characterizes the input load to the UPS - upsInput group: Characterizes the input load to the UPS
(number of input lines, voltage, current, etc.). (number of input lines, voltage, current, etc.).
- upsOutput: Characterizes the output from the UPS (number of - upsOutput: Characterizes the output from the UPS (number of
output lines, voltage, current, etc.) output lines, voltage, current, etc.)
- upsAlarms: Indicates the various alarm events. - upsAlarms: Indicates the various alarm events.
The measurement of power in the UPS MIB is in Volts, Amperes and The measurement of power in the UPS MIB is in volts, amperes and
Watts. The units of power measurement are RMS volts and RMS watts. The units of power measurement are RMS volts and RMS
Amperes. They are not based on the EntitySensorDataScale and Amperes. They are not based on the EntitySensorDataScale and
EntitySensorDataPrecision of ENTITY-SENSOR-MIB. EntitySensorDataPrecision of ENTITY-SENSOR-MIB.
Both the Power and Energy Monitoring MIB and the UPS MIB may be Both the Power and Energy Monitoring MIB and the UPS MIB may be
implemented on the same UPS SNMP agent, without conflict. In implemented on the same UPS SNMP agent, without conflict. In
this case, the UPS device itself is the Energy Object and any this case, the UPS device itself is the Energy Object and any
of the UPS meters or submeters are the Energy Objects with a of the UPS meters or submeters are the Energy Objects with a
possible relationship as defined in [EMAN-FMWK]. possible relationship as defined in [EMAN-FMWK].
7.5. Link with the LLDP and LLDP-MED MIBs 7.5. Link with the LLDP and LLDP-MED MIBs
skipping to change at page 24, line 50 skipping to change at page 23, line 18
of power (power sourcing entity versus powered device), how the of power (power sourcing entity versus powered device), how the
device is powered (from the line, from a backup source, from device is powered (from the line, from a backup source, from
external power source, etc.), the power priority (how important external power source, etc.), the power priority (how important
is it that this device has power?), and how much power the is it that this device has power?), and how much power the
device needs. device needs.
The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB]
actually comes from the Power-over-Ethernet MIB [RFC3621]. If actually comes from the Power-over-Ethernet MIB [RFC3621]. If
the Power-over-Ethernet MIB [RFC3621] is supported, the exact the Power-over-Ethernet MIB [RFC3621] is supported, the exact
value from the pethPsePortPowerPriority [RFC3621] is copied over value from the pethPsePortPowerPriority [RFC3621] is copied over
in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise into the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB];
the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From otherwise the value in lldpXMedRemXPoEPDPowerPriority is
the Power and Energy Monitoring MIB, it is possible to identify "unknown". From the Power and Energy Monitoring MIB, it is
the pethPsePortPowerPriority [RFC3621], thanks to the possible to identify the pethPsePortPowerPriority [RFC3621], via
eoethPortIndex and eoethPortGrpIndex. the eoethPortIndex and eoethPortGrpIndex.
The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to
eoPowerOrigin in indicating if the power for an attached device eoPowerMeasurementLocal in indicating if the power for an
is local or from a remote device. If the LLDP-MED MIB is attached device is local or from a remote device. If the LLDP-
supported, the following mapping can be applied to the MED MIB is supported, the following mapping can be applied to
eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and the eoPowerMeasurementLocal: lldpXMedLocXPoEPDPowerSource
local(3) can be mapped to remote(2) and self(1), respectively. fromPSE(2) and local(3) can be mapped to false and true,
respectively.
8. Implementation Scenario
This section provides an illustrative example scenario for the
implementation of the Energy Object, including Energy Object
relationships.
Example Scenario of a campus network: Switch with PoE Endpoints
with further connected devices.
The campus network consists of switches that provide LAN
connectivity. The switch with PoE ports is located in wiring
closet. PoE IP phones are connected to the switch. The IP
phones draw power from the PoE ports of the switch. In
addition, a PC is daisy-chained from the IP phone for LAN
connectivity.
The IP phone consumes power from the PoE switch, while the PC
consumes power from the wall outlet.
The switch has implementations of ENTITY-MIB [RFC6933] and
ENERGY-OBJECT-CONTEXT-MIB MIB [EMAN-AWARE-MIB]. while the PC
has an implementation of the ENTITY-MIB with
entity4CRCompliance, and an implementation of ENERGY-OBJECT-
CONTEXT-MIB MIB [EMAN-AWARE-MIB]. The switch has the following
attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID
1000". The power usage of the switch is "440 Watts".
The PoE switch port has the following attributes: The switch
port has entPhysicalIndex "3", and entPhysicalUUID is "UUID
1000:3". The power metered at the POE switch port is "12
watts". In this example, the POE switch port has an Energy
Object relationship with the switch with Energy Object index
"1000".
The attributes of the PC are given below. The PC has an
entPhysicalIndex "7" and its entPhysicalUUID is "UUID 1000:57 ".
The PC has an Energy Object relationship with the switch port
whose entPhysicalUUID is "UUID 1000:3". The power usage of the
PC is "120 Watts" and is communicated to the switch port.
The IP phone draws power from the switch, while the PC has LAN
connectivity from the phone, but is powered from the wall
outlet. However, the Energy Object switch sends power control
messages to both the Energy Object (IP phone and PC) and the
attached remote Energy Objects react to those messages.
|-------------------------------------------------------|
| Switch |
|=======================================================|
| Switch | Switch | | Switch |
| entPhyIndx | UUID | | eoPower |
| ===================================================== |
| 1 | UUID 1000 | null | 440 |
| ===================================================== |
| |
| SWITCH PORT |
| ===================================================== |
| | Switch | Switch | Switch | Switch |
| | Port | Port | UUID | Port |
| | entPhyIndx | UUID | | eoPower |
| ===================================================== |
| | 3 | UUID 1000:3 | 1000 | 12 |
| ======================================================|
| ^ |
| | |
|-----------------------------------|-------------------|
|
|
POE IP PHONE |
|
|
======================================================
| IP phone | IP phone | Port | IP phone |
| entPhyIndx | UUID | UUID | eoPower |
======================================================
| Null | UUID 1000:31| UUID 1000:3 | 12 |
=======================================================
|
|
PC connected to switch via IP phone |
|
=====================================================
| PC | PC | Port | PC |
|entPhyIndx | UUID | UUID | eoPower |
=====================================================
| 7 | UUID 1000:57| UUID 1000:3 | 120 |
=====================================================
Figure 6: Example scenario
9. Structure of the MIB 8. Structure of the MIB
The primary MIB object in this MIB module is the The primary MIB object in this MIB module is the
energyObjectMIBObject. The eoPowerTable table of energyObjectMibObjects root. The eoPowerTable table of
energyObjectMIBObject describes the power measurement attributes energyObjectMibObjects describes the power measurement
of an Energy Object entity. The notion of identity of the device attributes of an Energy Object entity. The identity of a 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
ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the ENERGY-OBJECT-CONTEXT-MIB module [EMAN-AWARE-MIB]. Thus the
following requirements which are applied to [EMAN-AWARE-MIB] are following requirements which are applied to [EMAN-AWARE-MIB] are
also applicable. As a requirement for this MIB module, [EMAN- also applicable. As a requirement for this MIB module, [EMAN-
AWARE-MIB] should be implemented and as Module Compliance of AWARE-MIB] SHOULD be implemented and as Module Compliance of
ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance MUST
should be supported which requires 3 MIB objects be supported which requires 4 MIB objects: entPhysicalIndex,
(entPhysicalIndex, entPhysicalName and entPhysicalUUID ) MUST be entPhysicalClass, entPhysicalName and entPhysicalUUID MUST be
implemented. implemented.
eoMeterCapabilitiesTable is useful to enable applications to eoMeterCapabilitiesTable is useful to enable applications to
determine the capabilities supported by the local management determine the capabilities supported by the local management
agent. This table indicates the energy monitoring MIB groups agent. This table indicates the energy monitoring MIB groups
that are supported by the local management system. By reading that are supported by the local management system. By reading
the value of this object, it is possible for applications to the value of this object, it is possible for applications to
know which tables contain the information and are usable without know which tables contain the information and are usable without
walking through the table and querying every element which walking through the table and querying every element which
involves a trial-and-error process. involves a trial-and-error process.
The power measurement of an Energy Object contains information The power measurement of an Energy Object contains information
describing its power usage (eoPower) and its current Power State describing its power usage (eoPower) and its current Power State
(eoPowerOperState). In addition to power usage, additional (eoPowerOperState). In addition to power usage, additional
information describing the units of measurement information describing the units of measurement
(eoPowerAccuracy, eoPowerUnitMultiplier), how power usage (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage
measurement was obtained (eoPowerMeasurementCaliber), the measurement was obtained (eoPowerMeasurementCaliber), the
source of power (eoPowerOrigin) and the type of power source of power measurement (eoPowerMeasurementLocal) and the
(eoPowerCurrentTtype) are described. type of power (eoPowerCurrentType) are described.
An Energy Object may contain an optional eoPowerAttributes table An Energy Object may contain an optional eoPowerAttributes table
that describes the electrical characteristics associated with that describes the electrical characteristics associated with
the current Power State and usage. the current Power State and usage.
An Energy Object may contain an optional eoEnergyTable to An Energy Object may contain an optional eoEnergyTable to
describe energy measurement information over time. describe energy measurement information over time.
An Energy Object may also contain optional battery information An Energy Object may also contain optional battery information
associated with this entity. associated with this entity.
10. MIB Definitions 9. MIB Definitions
-- ************************************************************ -- ************************************************************
-- --
-- --
-- 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, RowStatus, TimeInterval,
TimeStamp, TruthValue TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
entPhysicalIndex, PhysicalIndex entPhysicalIndex
FROM ENTITY-MIB FROM ENTITY-MIB
IANAPowerStateSet IANAPowerStateSet
FROM IANA-POWERSTATE-SET-MIB; FROM IANA-POWERSTATE-SET-MIB;
energyObjectMib MODULE-IDENTITY
LAST-UPDATED "201402140000Z" -- 14 Feb 2014
energyObjectMIB MODULE-IDENTITY
LAST-UPDATED "201312130000Z" -- 13 December 2013
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
skipping to change at page 29, line 27 skipping to change at page 25, line 43
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad.schoening@verizon.net Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
skipping to change at page 30, line 4 skipping to change at page 26, line 8
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
DE DE
Phone: +49 6221 4342-115 Phone: +49 6221 4342-115
Email: quittek@neclab.eu Email: quittek@neclab.eu
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu" Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to monitor power and energy in "This MIB is used to monitor power and energy in
devices. devices.
This table sparse extension of the eoTable The tables eoMeterCapabilitiesTable and eoPowerTable
from the ENERGY-OBJECT-CONTEXT-MIB. As a requirement are a sparse extension of the eoTable from the
[EMAN-AWARE-MIB] must be implemented. ENERGY-OBJECT-CONTEXT-MIB. As a requirement
[EMAN-AWARE-MIB] SHOULD be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4 with respect to
with respect to entity4CRCompliance should entity4CRCompliance MUST be supported which requires
be supported which requires implementation implementation of 4 MIB objects: entPhysicalIndex,
of 3 MIB objects (entPhysicalIndex, entPhysicalClass, entPhysicalName and entPhysicalUUID."
entPhysicalName and entPhysicalUUID)."
REVISION REVISION
"201312130000Z" -- 13 December 2013 "201402140000Z" -- 14 Feb 2014
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC XXXX."
::= { energyMIB 3 } ::= { mib-2 xxx }
energyObjectMIBNotifs OBJECT IDENTIFIER energyObjectMibNotifs OBJECT IDENTIFIER
::= { energyObjectMIB 0 } ::= { energyObjectMib 0 }
energyObjectMIBObjects OBJECT IDENTIFIER energyObjectMibObjects OBJECT IDENTIFIER
::= { energyObjectMIB 1 } ::= { energyObjectMib 1 }
energyObjectMIBConform OBJECT IDENTIFIER energyObjectMibConform OBJECT IDENTIFIER
::= { energyObjectMIB 2 } ::= { energyObjectMib 2 }
-- Textual Conventions -- Textual Conventions
IANAPowerStateSet ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of Power
State Sets and Power States.
The textual convention assumes that Power States in a power
state set are limited to 255 distinct values. For a Power
State Set S, the named number with the value S * 256 is
allocated to indicate the Power State set. For a Power State X
in the Power State S, the named number with the value S * 256
+ X + 1 is allocated to represent the Power State."
REFERENCE
"http://www.iana.org/assignments/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
SYNTAX INTEGER {
other(0), -- indicates other set
unknown(255), -- unknown
ieee1621(256), -- indicates IEEE1621 set
ieee1621On(257),
ieee1621Off(258),
ieee1621Sleep(259),
dmtf(512), -- indicates DMTF set
dmtfOn(513),
dmtfSleepLight(514),
dmtfSleepDeep(515),
dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set
emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
UnitMultiplier ::= TEXTUAL-CONVENTION UnitMultiplier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Unit Multiplier is an integer value that represents "The Unit Multiplier is an integer value that represents
the IEEE 61850 Annex A units multiplier associated with the IEEE 61850 Annex A units multiplier associated with
the integer units used to measure the power or energy. the integer units used to measure the power or energy.
For example, when used with eoPowerUnitMultiplier, -3 For example, when used with eoPowerUnitMultiplier, -3
represents 10^-3 or milliwatts." represents 10^-3 or milliwatts."
REFERENCE REFERENCE
"The International System of Units (SI), "The International System of Units (SI), National
National Institute of Standards and Technology, Institute of Standards and Technology, Spec. Publ. 330,
Spec. Publ. 330, August 1991." August 1991."
SYNTAX INTEGER { SYNTAX INTEGER {
yocto(-24), -- 10^-24 yocto(-24), -- 10^-24
zepto(-21), -- 10^-21 zepto(-21), -- 10^-21
atto(-18), -- 10^-18 atto(-18), -- 10^-18
femto(-15), -- 10^-15 femto(-15), -- 10^-15
pico(-12), -- 10^-12 pico(-12), -- 10^-12
nano(-9), -- 10^-9 nano(-9), -- 10^-9
micro(-6), -- 10^-6 micro(-6), -- 10^-6
milli(-3), -- 10^-3 milli(-3), -- 10^-3
units(0), -- 10^0 units(0), -- 10^0
skipping to change at page 31, line 47 skipping to change at page 29, line 22
eoMeterCapabilitiesTable OBJECT-TYPE eoMeterCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is useful for helping applications determine the "This table is useful for helping applications determine the
monitoring capabilities supported by the local management monitoring capabilities supported by the local management
agents. It is possible for applications to know which tables agents. It is possible for applications to know which tables
are usable without going through a trial-and-error process." are usable without going through a trial-and-error process."
::= { energyObjectMIBObjects 1 } ::= { energyObjectMibObjects 1 }
eoMeterCapabilitiesEntry OBJECT-TYPE eoMeterCapabilitiesEntry OBJECT-TYPE
SYNTAX EoMeterCapabilitiesEntry SYNTAX EoMeterCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the metering capability of an Energy "An entry describes the metering capability of an Energy
Object." Object."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { eoMeterCapabilitiesTable 1 } ::= { eoMeterCapabilitiesTable 1 }
skipping to change at page 32, line 29 skipping to change at page 29, line 48
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 indicates 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."
::= { energyObjectMIBObjects 2 } ::= { energyObjectMibObjects 2 }
eoPowerEntry OBJECT-TYPE eoPowerEntry OBJECT-TYPE
SYNTAX EoPowerEntry SYNTAX EoPowerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the power usage of an Energy Object." "An entry describes the power usage of an Energy Object."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { eoPowerTable 1 } ::= { eoPowerTable 1 }
EoPowerEntry ::= SEQUENCE { EoPowerEntry ::= SEQUENCE {
eoPower Integer32, eoPower Integer32,
eoPowerNameplate Integer32, eoPowerNameplate Integer32,
eoPowerUnitMultiplier UnitMultiplier, eoPowerUnitMultiplier UnitMultiplier,
eoPowerAccuracy Integer32, eoPowerAccuracy Integer32,
eoPowerMeasurementCaliber INTEGER, eoPowerMeasurementCaliber INTEGER,
eoPowerCurrentType INTEGER, eoPowerCurrentType INTEGER,
eoPowerOrigin INTEGER, eoPowerMeasurementLocal TruthValue,
eoPowerAdminState IANAPowerStateSet, eoPowerAdminState IANAPowerStateSet,
eoPowerOperState IANAPowerStateSet, eoPowerOperState IANAPowerStateSet,
eoPowerStateEnterReason OwnerString eoPowerStateEnterReason OwnerString
} }
eoPower OBJECT-TYPE eoPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watts" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the power measured for the Energy "This object indicates the power measured for the Energy
Object. For alternating current, this value is obtained Object. For alternating current, this value is obtained
as an average over fixed number of AC cycles. . This as an average over fixed number of AC cycles. This value
value is specified in SI units of watts with the is specified in SI units of watts with the magnitude of
magnitude of watts (milliwatts, kilowatts, etc.) watts (milliwatts, kilowatts, etc.) indicated separately
indicated separately in eoPowerUnitMultiplier. The in eoPowerUnitMultiplier. The accuracy of the measurement
accuracy of the measurement is specfied in is specfied in eoPowerAccuracy. The direction of power
eoPowerAccuracy. The direction of power flow is indicated flow is indicated by the sign on eoPower. If the Energy
by the sign on eoPower. If the Energy Object is consuming Object is consuming power, the eoPower value will be
power, the eoPower value will be positive. If the Energy positive. If the Energy Object is producing power, the
Object is producing power, the eoPower value will be eoPower value will be negative.
negative.
The eoPower MUST be less than or equal to the maximum The eoPower MUST be less than or equal to the maximum
power that can be consumed at the power state specified power that can be consumed at the power state specified
by eoPowerState. by eoPowerState.
The eoPowerMeasurementCaliber object specifies how the The eoPowerMeasurementCaliber object specifies how the
usage value reported by eoPower was obtained. The eoPower usage value reported by eoPower was obtained. The eoPower
value must report 0 if the eoPowerMeasurementCaliber is value must report 0 if the eoPowerMeasurementCaliber is
'unavailable'. For devices that can not measure or 'unavailable'. For devices that can not measure or
report power, this option can be used." report power, this option can be used."
skipping to change at page 34, line 4 skipping to change at page 31, line 22
The eoPower MUST be less than or equal to the maximum The eoPower MUST be less than or equal to the maximum
power that can be consumed at the power state specified power that can be consumed at the power state specified
by eoPowerState. by eoPowerState.
The eoPowerMeasurementCaliber object specifies how the The eoPowerMeasurementCaliber object specifies how the
usage value reported by eoPower was obtained. The eoPower usage value reported by eoPower was obtained. The eoPower
value must report 0 if the eoPowerMeasurementCaliber is value must report 0 if the eoPowerMeasurementCaliber is
'unavailable'. For devices that can not measure or 'unavailable'. For devices that can not measure or
report power, this option can be used." report power, this option can be used."
::= { eoPowerEntry 1 } ::= { eoPowerEntry 1 }
eoPowerNameplate OBJECT-TYPE eoPowerNameplate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watts" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the rated maximum consumption for "This object indicates the rated maximum consumption for
the fully populated Energy Object. The nameplate power the fully populated Energy Object. The nameplate power
requirements are the maximum power numbers and, in almost requirements are the maximum power numbers and, in almost
all cases, are well above the expected operational all cases, are well above the expected operational
consumption. The eoPowerNameplate is widely used for consumption. Nameplate power is widely used for power
power provisioning. This value is specified in either provisioning. This value is specified in either units of
units of watts or voltage and current. The units are watts or voltage and current. The units are therefore SI
therefore SI watts or equivalent Volt-Amperes with the watts or equivalent Volt-Amperes with the magnitude
magnitude (milliwatts, kilowatts, etc.) indicated (milliwatts, kilowatts, etc.) indicated separately in
separately in eoPowerUnitMultiplier." eoPowerUnitMultiplier."
::= { eoPowerEntry 2 } ::= { eoPowerEntry 2 }
eoPowerUnitMultiplier OBJECT-TYPE eoPowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in eoPower "The magnitude of watts for the usage value in eoPower
and eoPowerNameplate." and eoPowerNameplate."
::= { eoPowerEntry 3 } ::= { eoPowerEntry 3 }
skipping to change at page 35, line 27 skipping to change at page 32, line 43
- unavailable(1): Indicates that the usage is not - unavailable(1): Indicates that the usage is not
available. In such a case, the eoPower value must be 0 available. In such a case, the eoPower value must be 0
for devices that can not measure or report power this for devices that can not measure or report power this
option can be used. option can be used.
- unknown(2): Indicates that the way the usage was - unknown(2): Indicates that the way the usage was
determined is unknown. In some cases, entities report determined is unknown. In some cases, entities report
aggregate power on behalf of another device. In such aggregate power on behalf of another device. In such
cases it is not known whether the usage reported is cases it is not known whether the usage reported is
actual(2), estimated(3) or presumed (4). actual, estimated or static.
- actual(3): Indicates that the reported usage was - actual(3): Indicates that the reported usage was
measured by the entity through some hardware or direct measured by the entity through some hardware or direct
physical means. The usage data reported is not presumed physical means. The usage data reported is not estimated
(4) or estimated (3) but is the measured consumption or static but is the measured consumption rate.
rate.
- estimated(4): Indicates that the usage was not - estimated(4): Indicates that the usage was not
determined by physical measurement. The value is a determined by physical measurement. The value is a
derivation based upon the device type, state, and/or derivation based upon the device type, state, and/or
current utilization using some algorithm or heuristic. It current utilization using some algorithm or heuristic. It
is presumed that the entity's state and current is presumed that the entity's state and current
configuration were used to compute the value. configuration were used to compute the value.
- static(5): Indicates that the usage was not determined - static(5): Indicates that the usage was not determined
by physical measurement, algorithm or derivation. The by physical measurement, algorithm or derivation. The
usage was reported based upon external tables, usage was reported based upon external tables,
specifications, and/or model information. For example, a specifications, and/or model information. For example, a
PC Model X draws 200W, while a PC Model Y draws 210W" PC Model X draws 200W, while a PC Model Y draws 210W."
::= { eoPowerEntry 5 } ::= { eoPowerEntry 5 }
eoPowerCurrentType OBJECT-TYPE eoPowerCurrentType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ac(1), ac(1),
dc(2), dc(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the eoPower for the "This object indicates whether the eoPower for the
Energy Object reports alternating current AC(1), direct Energy Object reports alternating current 'ac', direct
current DC(2), or that the current type is unknown(3)." current 'dc', or that the current type is unknown."
::= { eoPowerEntry 6 } ::= { eoPowerEntry 6 }
eoPowerOrigin OBJECT-TYPE eoPowerMeasurementLocal OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TruthValue
self (1),
remote (2)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the source of power measurement "This object indicates the source of power measurement
and can be useful when modeling the power usage of and can be useful when modeling the power usage of
attached devices. The power measurement can be performed attached devices. The power measurement can be performed
by the entity itself or the power measurement of the by the entity itself or the power measurement of the
entity can be reported by another trusted entity using a entity can be reported by another trusted entity using a
protocol extension. A value of self(1) indicates the protocol extension. A value of true indicates the
measurement is performed by the entity, whereas remote(2) measurement is performed by the entity, whereas false
indicates that the measurement was performed by another indicates that the measurement was performed by another
entity." entity."
::= { eoPowerEntry 7 } ::= { eoPowerEntry 7 }
eoPowerAdminState OBJECT-TYPE eoPowerAdminState OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the desired Power State and the "This object specifies the desired Power State and the
skipping to change at page 37, line 10 skipping to change at page 34, line 18
A current list of assignments can be found at A current list of assignments can be found at
<http://www.iana.org/assignments/eman> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 8 } ::= { eoPowerEntry 8 }
eoPowerOperState OBJECT-TYPE eoPowerOperState OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the current operational Power "This object specifies the current operational Power
State and the Power State Set for the Energy Object. State and the Power State Set for the Energy Object.
other(0) is not a Power State Set and unknown(255) is other(0) is not a Power State Set and unknown(255) is
not a Power State as such, but simply an indication that not a Power State as such, but simply an indication that
the Power State of the Energy Object is unknown. the Power State of the Energy Object is unknown.
Possible values of eoPowerAdminState within the Power Possible values of eoPowerOperState within the Power
State Set are registered at IANA. State Set are registered at IANA. A current list of
A current list of assignments can be found at assignments can be found at
<http://www.iana.org/assignments/eman> <http://www.iana.org/assignments/eman>
RFC-EDITOR: please check the location after IANA" RFC-EDITOR: please check the location after IANA"
::= { eoPowerEntry 9 } ::= { eoPowerEntry 9 }
eoPowerStateEnterReason OBJECT-TYPE eoPowerStateEnterReason OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This string object describes the reason for the "This string object describes the reason for the
eoPowerAdminState eoPowerAdminState transition. Alternatively, this
transition Alternatively, this string may contain with string may contain with the entity that configured this
the entity that configured this Energy Object to this Energy Object to this Power State."
Power State."
DEFVAL { "" } DEFVAL { "" }
::= { eoPowerEntry 10 } ::= { eoPowerEntry 10 }
eoPowerStateTable OBJECT-TYPE eoPowerStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoPowerStateEntry SYNTAX SEQUENCE OF EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates the maximum power usage, in watts, "This table enumerates the maximum power usage, in watts,
for every single supported Power State of each Energy for every single supported Power State of each Energy
Object. Object.
This table has an expansion-dependent relationship on the This table has cross-reference with the eoPowerTable,
eoPowerTable, containing rows describing each Power State containing rows describing each Power State for the
for the corresponding Energy Object. For every Energy corresponding Energy Object. For every Energy Object in
Object in the eoPowerTable, there is a corresponding the eoPowerTable, there is a corresponding entry in this
entry in this table." table."
::= { energyObjectMIBObjects 3 } ::= { energyObjectMibObjects 3 }
eoPowerStateEntry OBJECT-TYPE eoPowerStateEntry OBJECT-TYPE
SYNTAX EoPowerStateEntry SYNTAX EoPowerStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A eoPowerStateEntry extends a corresponding "A eoPowerStateEntry extends a corresponding
eoPowerEntry. This entry displays max usage values at eoPowerEntry. This entry displays max usage values at
every single possible Power State supported by the Energy every single possible Power State supported by the Energy
Object. Object.
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 emanmechoff, 8 W at state 6 (ready), 11 W at state
9 (mediumMinus),and 11 W at state 12 (high): emanmediumMinus,and 11 W at state emanhigh:
State MaxUsage Units State MaxUsage Units
1 (mechoff 0 W emanmechoff 0 W
2 (softoff) 0 W emansoftoff 0 W
3 (hibernate) 0 W emanhibernate 0 W
4 (sleep) 0 W emansleep 0 W
5 (standby) 0 W emanstandby 0 W
6 (ready) 8 W emanready 8 W
7 (lowMinus) 8 W emanlowMinus 8 W
8 (low) 11 W emanlow 11 W
9 (mediumMinus) 11 W emanmediumMinus 11 W
10 (medium) 11 W emanmedium 11 W
11 (highMinus) 11 W emanhighMinus 11 W
12 (high) 11 W emnanhigh 11 W
Furthermore, this table extends to return the total time Furthermore, this table also includes the total time in
in each Power State, along with the number of times a 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
} }
::= { eoPowerStateTable 1 } ::= { eoPowerStateTable 1 }
EoPowerStateEntry ::= SEQUENCE { EoPowerStateEntry ::= SEQUENCE {
eoPowerStateIndex IANAPowerStateSet, eoPowerStateIndex IANAPowerStateSet,
eoPowerStateMaxPower Integer32, eoPowerStateMaxPower INTEGER,
eoPowerStatePowerUnitMultiplier UnitMultiplier, eoPowerStatePowerUnitMultiplier UnitMultiplier,
eoPowerStateTotalTime TimeTicks, eoPowerStateTotalTime TimeTicks,
eoPowerStateEnterCount Counter32 eoPowerStateEnterCount Counter32
} }
eoPowerStateIndex OBJECT-TYPE eoPowerStateIndex OBJECT-TYPE
SYNTAX IANAPowerStateSet SYNTAX IANAPowerStateSet
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "
This object specifies the index of the Power State of This object specifies the index of the Power State of
the Energy Object within a Power State Set. The the Energy Object within a Power State Set. The
semantics of the specific Power State can be obtained semantics of the specific Power State can be obtained
from the Power State Set definition." from the Power State Set definition."
skipping to change at page 39, line 18 skipping to change at page 36, line 21
DESCRIPTION DESCRIPTION
" "
This object specifies the index of the Power State of This object specifies the index of the Power State of
the Energy Object within a Power State Set. The the Energy Object within a Power State Set. The
semantics of the specific Power State can be obtained semantics of the specific Power State can be obtained
from the Power State Set definition." from the Power State Set definition."
::= { eoPowerStateEntry 1 } ::= { eoPowerStateEntry 1 }
eoPowerStateMaxPower OBJECT-TYPE eoPowerStateMaxPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watts" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum power for the Energy "This object indicates the maximum power for the Energy
Object at the particular Power State. This value is Object at the particular Power State. This value is
specified in SI units of watts with the magnitude of the specified in SI units of watts with the magnitude of the
units (milliwatts, kilowatts, etc.) indicated separately units (milliwatts, kilowatts, etc.) indicated separately
in eoPowerStatePowerUnitMultiplier. If the maximum power in eoPowerStatePowerUnitMultiplier. If the maximum power
is not known for a certain Power State, then the value is is not known for a certain Power State, then the value is
encoded as 0xFFFF. encoded as 0xFFFFFFFF.
For Power States not enumerated, the value of For Power States not enumerated, the value of
eoPowerStateMaxPower might be interpolated by using the eoPowerStateMaxPower might be interpolated by using the
next highest supported Power State." next highest supported Power State."
::= { eoPowerStateEntry 2 } ::= { eoPowerStateEntry 2 }
eoPowerStatePowerUnitMultiplier OBJECT-TYPE eoPowerStatePowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in "The magnitude of watts for the usage value in
eoPowerStateMaxPower." eoPowerStateMaxPower."
::= { eoPowerStateEntry 3 } ::= { eoPowerStateEntry 3 }
eoPowerStateTotalTime OBJECT-TYPE eoPowerStateTotalTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the total time in hundredth "This object indicates the total time in hundredths
of second that the Energy Object has been in this power of second that the Energy Object has been in this power
state since the last reset, as specified in the state since the last reset, as specified in the
sysUpTime." sysUpTime."
::= { eoPowerStateEntry 4 } ::= { eoPowerStateEntry 4 }
eoPowerStateEnterCount OBJECT-TYPE eoPowerStateEnterCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 40, line 29 skipping to change at page 37, line 29
eoEnergyParametersTable OBJECT-TYPE eoEnergyParametersTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyParametersEntry SYNTAX SEQUENCE OF EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to configure the parameters for "This table is used to configure the parameters for
Energy measurement collection in the table Energy measurement collection in the table
eoEnergyTable. This table allows the configuration of eoEnergyTable. This table allows the configuration of
different measurement settings on the same Energy Object. different measurement settings on the same Energy Object.
Implementation of this table only sense for Energy Implementation of this table only makes sense for Energy
Objects that an eoPowerMeasurementCaliber of actual(3)." Objects that an eoPowerMeasurementCaliber of actual."
::= { energyObjectMIBObjects 4 } ::= { energyObjectMibObjects 4 }
eoEnergyParametersEntry OBJECT-TYPE eoEnergyParametersEntry OBJECT-TYPE
SYNTAX EoEnergyParametersEntry SYNTAX EoEnergyParametersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry controls an energy measurement in "An entry controls an energy measurement in
eoEnergyTable." eoEnergyTable."
INDEX { eoEnergyObjectIndex, eoEnergyParametersIndex } INDEX { entPhysicalIndex, eoEnergyParametersIndex }
::= { eoEnergyParametersTable 1 } ::= { eoEnergyParametersTable 1 }
EoEnergyParametersEntry ::= SEQUENCE { EoEnergyParametersEntry ::= SEQUENCE {
eoEnergyObjectIndex PhysicalIndex,
eoEnergyParametersIndex Integer32, eoEnergyParametersIndex Integer32,
eoEnergyParametersIntervalLength TimeInterval, eoEnergyParametersIntervalLength TimeInterval,
eoEnergyParametersIntervalNumber Integer32, eoEnergyParametersIntervalNumber Integer32,
eoEnergyParametersIntervalMode INTEGER, eoEnergyParametersIntervalMode INTEGER,
eoEnergyParametersIntervalWindow TimeInterval, eoEnergyParametersIntervalWindow TimeInterval,
eoEnergyParametersSampleRate Integer32, eoEnergyParametersSampleRate Integer32,
eoEnergyParametersStatus RowStatus eoEnergyParametersStatus RowStatus
} }
eoEnergyObjectIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique value, to identify the specific Energy Object
on which the measurement is applied, the same index used
in the eoPowerTable to identify the Energy Object."
::= { eoEnergyParametersEntry 1 }
eoEnergyParametersIndex OBJECT-TYPE eoEnergyParametersIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
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 capabilities
the Energy Object" of 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 hundredths
seconds over which to compute the average of 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. The
default value of 15 minutes is a common interval used in
industry."
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
replaces the oldest measurement. There is one exception replaces the oldest measurement. There is one exception
to 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."
skipping to change at page 43, line 4 skipping to change at page 39, line 39
eoEnergyParametersIntervalLength is ignored. " eoEnergyParametersIntervalLength is ignored. "
::= { eoEnergyParametersEntry 5 } ::= { eoEnergyParametersEntry 5 }
eoEnergyParametersIntervalWindow OBJECT-TYPE eoEnergyParametersIntervalWindow OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the duration window between the starting "The length of the duration window between the starting
time of one sliding window and the next starting time in time of one sliding window and the next starting time in
hundredth of seconds, in order to compute the average of hundredths of seconds, in order to compute the average of
eoEnergyConsumed, eoEnergyProvided measurements in the eoEnergyConsumed, eoEnergyProvided measurements in the
eoEnergyTable table. This is valid only when the eoEnergyTable table. This is valid only when the
eoEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalMode is sliding(2). The
eoEnergyParametersIntervalWindow value should be a multiple eoEnergyParametersIntervalWindow value should be a multiple
of eoEnergyParametersSampleRate." of eoEnergyParametersSampleRate."
::= { eoEnergyParametersEntry 6 } ::= { eoEnergyParametersEntry 6 }
eoEnergyParametersSampleRate OBJECT-TYPE eoEnergyParametersSampleRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds" UNITS "Milliseconds"
skipping to change at page 43, line 30 skipping to change at page 40, line 16
average eoEnergyConsumed, eoEnergyProvided measurements average eoEnergyConsumed, eoEnergyProvided 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. The default value is one
second."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { eoEnergyParametersEntry 7 } ::= { eoEnergyParametersEntry 7 }
eoEnergyParametersStatus OBJECT-TYPE eoEnergyParametersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row. The eoEnergyParametersStatus is "The status of this row. The eoEnergyParametersStatus is
used to start or stop energy usage logging. An entry used to start or stop energy usage logging. An entry
status may not be active(1) unless all objects in the status may not be active(1) unless all objects in the
entry have an appropriate value. If this object is not entry have an appropriate value. If this object is not
equal to active(1), all associated usage-data logged into equal to active, all associated usage-data logged into
the eoEnergyTable will be deleted. The data can be the eoEnergyTable will be deleted. The data can be
destroyed by setting up the eoEnergyParametersStatus to destroyed by setting up the eoEnergyParametersStatus to
destroy(2)." destroy."
::= {eoEnergyParametersEntry 8 } ::= {eoEnergyParametersEntry 8 }
eoEnergyTable OBJECT-TYPE eoEnergyTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoEnergyEntry SYNTAX SEQUENCE OF EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists Energy Object energy measurements. "This table lists Energy Object energy measurements.
Entries in this table are only created if the Entries in this table are only created if the
corresponding value of object eoPowerMeasurementCaliber corresponding value of object eoPowerMeasurementCaliber
is active(3), i.e., if the power is actually metered." is active(3), i.e., if the power is actually metered."
::= { energyObjectMIBObjects 5 } ::= { energyObjectMibObjects 5 }
eoEnergyEntry OBJECT-TYPE eoEnergyEntry OBJECT-TYPE
SYNTAX EoEnergyEntry SYNTAX EoEnergyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describing energy measurements." "An entry describing energy measurements."
INDEX { eoEnergyParametersIndex, INDEX { eoEnergyParametersIndex,
eoEnergyCollectionStartTime } eoEnergyCollectionStartTime }
::= { eoEnergyTable 1 } ::= { eoEnergyTable 1 }
skipping to change at page 45, line 34 skipping to change at page 42, line 18
hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 3 } ::= { eoEnergyEntry 3 }
eoEnergyStored OBJECT-TYPE eoEnergyStored OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the resultant of the energy consumed and "This object indicates the difference of the energy consumed and
energy produced for an Energy Object in units of watt-hours for energy produced for an Energy Object in units of watt-hours for
the Energy Object over the defined interval. This value is the Energy Object over the defined interval. This value is
specified in the common billing units of watt-hours specified in the common billing units of watt-hours
with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.)
indicated separately in eoEnergyUnitMultiplier." indicated separately in eoEnergyUnitMultiplier."
::= { eoEnergyEntry 4 } ::= { eoEnergyEntry 4 }
eoEnergyUnitMultiplier OBJECT-TYPE eoEnergyUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the magnitude of watt-hours for the "This object is the magnitude of watt-hours for the
energy field in eoEnergyConsumed, eoEnergyProvided, energy field in eoEnergyConsumed, eoEnergyProvided,
eoEnergyStored, eoEnergyMaxConsumed, and eoEnergyStored, eoEnergyMaxConsumed, and
eoEnergyMaxProduced ." 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 accuracy, in 100ths
percent, representing the presumed accuracy of Energy usage of a percent, of Energy usage reporting. eoEnergyAccuracy
reporting. eoEnergyAccuracy is applicable to all Energy is applicable to all Energy measurements in the
measurements in the eoEnergyTable. 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"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy ever observed in "This object is the maximum energy observed in
eoEnergyConsumed since the monitoring started. This value eoEnergyConsumed since the monitoring started or was
is specified in the common billing units of watt-hours reinitialized. This value is specified in the common
with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) billing units of watt-hours with the magnitude of watt-
indicated separately in eoEnergyUnitMultiplier." hours (kW-Hr, MW-Hr, etc.) indicated separately in
eoEnergyUnitMultiplier."
::= { eoEnergyEntry 7 } ::= { eoEnergyEntry 7 }
eoEnergyMaxProduced OBJECT-TYPE eoEnergyMaxProduced OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Watt-hours" UNITS "Watt-hours"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the maximum energy ever observed in "This object is the maximum energy ever observed in
eoEnergyEnergyProduced since the monitoring started. This eoEnergyEnergyProduced since the monitoring started. This
skipping to change at page 47, line 26 skipping to change at page 44, line 6
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 eoPowerEnableStatusNotification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This variable indicates whether the DESCRIPTION
system produces the following notifications: "This object controls whether the system produces
eoPowerStateChange. notifications for eoPowerStateChange. A false value will
prevent these notifications from being generated."
A false value will prevent these notifications
from being generated."
DEFVAL { false } DEFVAL { false }
::= { energyObjectMIBNotifs 1 } ::= { energyObjectMibNotifs 1 }
eoPowerStateChange NOTIFICATION-TYPE eoPowerStateChange NOTIFICATION-TYPE
OBJECTS {eoPowerAdminState, eoPowerOperState, OBJECTS {eoPowerAdminState, eoPowerOperState,
eoPowerStateEnterReason} eoPowerStateEnterReason}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNMP entity generates the eoPowerStateChange when "The SNMP entity generates the eoPowerStateChange when
the value(s) of eoPowerAdminState or eoPowerOperState, the values of eoPowerAdminState or eoPowerOperState,
in the context of the Power State Set, have changed for in the context of the Power State Set, have changed for
the Energy Object represented by the entPhysicalIndex." the Energy Object represented by the entPhysicalIndex."
::= { energyObjectMIBNotifs 2 } ::= { energyObjectMibNotifs 2 }
-- Conformance -- Conformance
energyObjectMIBCompliances OBJECT IDENTIFIER energyObjectMibCompliances OBJECT IDENTIFIER
::= { energyObjectMIBConform 1 } ::= { energyObjectMibConform 1 }
energyObjectMIBGroups OBJECT IDENTIFIER energyObjectMibGroups OBJECT IDENTIFIER
::= { energyObjectMIBConform 2 } ::= { energyObjectMibConform 2 }
energyObjectMIBFullCompliance MODULE-COMPLIANCE energyObjectMibFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented with support for "When this MIB is implemented with support for
read-create, then such an implementation can read-create, then such an implementation can
claim full compliance. Such devices can then claim full compliance. Such devices can then
be both monitored and configured with this MIB. be both monitored and configured with this MIB.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMIBTableGroup, energyObjectMibTableGroup,
energyObjectMIBStateTableGroup, energyObjectMibStateTableGroup,
eoPowerEnableStatusNotificationGroup, eoPowerEnableStatusNotificationGroup,
energyObjectMIBNotifGroup energyObjectMibNotifGroup
} }
GROUP energyObjectMIBEnergyTableGroup GROUP energyObjectMibEnergyTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
GROUP energyObjectMIBEnergyParametersTableGroup GROUP energyObjectMibEnergyParametersTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of {RFC6933] Module Compliance of {RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
GROUP energyObjectMIBMeterCapabilitiesTableGroup GROUP energyObjectMibMeterCapabilitiesTableGroup
DESCRIPTION "A compliant implementation does not DESCRIPTION "A compliant implementation does not
have to implement. have to implement.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
::= { energyObjectMIBCompliances 1 } ::= { energyObjectMibCompliances 1 }
energyObjectMIBReadOnlyCompliance MODULE-COMPLIANCE energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this MIB is implemented without support for "When this MIB is implemented without support for
read-create (i.e. in read-only mode), then such an read-create (i.e., in read-only mode), then such an
implementation can claim read-only compliance. Such a implementation can claim read-only compliance. Such a
device can then be monitored but cannot be device can then be monitored but cannot be
configured with this MIB. configured with this MIB.
Module Compliance of [RFC6933] Module Compliance of [RFC6933]
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
energyObjectMIBTableGroup, energyObjectMibTableGroup,
energyObjectMIBStateTableGroup, energyObjectMibStateTableGroup,
energyObjectMIBNotifGroup energyObjectMibNotifGroup
} }
OBJECT eoPowerOperState OBJECT eoPowerOperState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { energyObjectMIBCompliances 2 } ::= { energyObjectMibCompliances 2 }
-- Units of Conformance -- Units of Conformance
energyObjectMIBTableGroup OBJECT-GROUP energyObjectMibTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPower, eoPower,
eoPowerNameplate, eoPowerNameplate,
eoPowerUnitMultiplier, eoPowerUnitMultiplier,
eoPowerAccuracy, eoPowerAccuracy,
eoPowerMeasurementCaliber, eoPowerMeasurementCaliber,
eoPowerCurrentType, eoPowerCurrentType,
eoPowerOrigin, eoPowerMeasurementLocal,
eoPowerAdminState, eoPowerAdminState,
eoPowerOperState, eoPowerOperState,
eoPowerStateEnterReason eoPowerStateEnterReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Object." related to the Energy Object."
::= { energyObjectMIBGroups 1 } ::= { energyObjectMibGroups 1 }
energyObjectMIBStateTableGroup OBJECT-GROUP energyObjectMibStateTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoPowerStateMaxPower, eoPowerStateMaxPower,
eoPowerStatePowerUnitMultiplier, eoPowerStatePowerUnitMultiplier,
eoPowerStateTotalTime, eoPowerStateTotalTime,
eoPowerStateEnterCount eoPowerStateEnterCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the "This group contains the collection of all the
objects related to the Power State." objects related to the Power State."
::= { energyObjectMIBGroups 2 }
energyObjectMIBEnergyParametersTableGroup OBJECT-GROUP ::= { energyObjectMibGroups 2 }
energyObjectMibEnergyParametersTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoEnergyParametersIndex,
eoEnergyParametersIntervalLength, eoEnergyParametersIntervalLength,
eoEnergyParametersIntervalNumber, eoEnergyParametersIntervalNumber,
eoEnergyParametersIntervalMode, eoEnergyParametersIntervalMode,
eoEnergyParametersIntervalWindow, eoEnergyParametersIntervalWindow,
eoEnergyParametersSampleRate, eoEnergyParametersSampleRate,
eoEnergyParametersStatus eoEnergyParametersStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the configuration of the Energy Table." related to the configuration of the Energy Table."
::= { energyObjectMibGroups 3 }
::= { energyObjectMIBGroups 3 } energyObjectMibEnergyTableGroup OBJECT-GROUP
energyObjectMIBEnergyTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object -- Note that object
-- eoEnergyCollectionStartTime is not -- eoEnergyCollectionStartTime is not
-- included since it is not-accessible -- included since it is not-accessible
eoEnergyConsumed, eoEnergyConsumed,
eoEnergyProvided, eoEnergyProvided,
eoEnergyStored, eoEnergyStored,
eoEnergyUnitMultiplier, eoEnergyUnitMultiplier,
eoEnergyAccuracy, eoEnergyAccuracy,
eoEnergyMaxConsumed, eoEnergyMaxConsumed,
eoEnergyMaxProduced, eoEnergyMaxProduced,
eoEnergyDiscontinuityTime eoEnergyDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the objects "This group contains the collection of all the objects
related to the Energy Table." related to the Energy Table."
::= { energyObjectMIBGroups 4 } ::= { energyObjectMibGroups 4 }
energyObjectMIBMeterCapabilitiesTableGroup OBJECT-GROUP energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoMeterCapability eoMeterCapability
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the object indicating the "This group contains the object indicating the
capability of the Energy Object" capability of the Energy Object"
::= { energyObjectMIBGroups 5 } ::= { energyObjectMibGroups 5 }
eoPowerEnableStatusNotificationGroup OBJECT-GROUP eoPowerEnableStatusNotificationGroup OBJECT-GROUP
OBJECTS { eoPowerEnableStatusNotification } OBJECTS { eoPowerEnableStatusNotification }
STATUS current STATUS current
DESCRIPTION "The collection of objects which are used DESCRIPTION "The collection of objects which are used
to enable notification." to enable notification."
::= { energyObjectMIBGroups 6 } ::= { energyObjectMibGroups 6 }
energyObjectMIBNotifGroup NOTIFICATION-GROUP energyObjectMibNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
eoPowerStateChange eoPowerStateChange
} }
STATUS current STATUS current
DESCRIPTION "This group contains the notifications for DESCRIPTION "This group contains the notifications for
the power and energy monitoring MIB Module." the power and energy monitoring MIB Module."
::= { energyObjectMIBGroups 7 } ::= { energyObjectMibGroups 7 }
END END
-- ************************************************************ -- ************************************************************
-- --
-- This MIB module is used to monitor power attributes of -- This MIB module is used to monitor power attributes of
-- networked devices with measurements. -- networked devices with measurements.
-- --
-- This MIB module is an extension of energyObjectMIB module. -- This MIB module is an extension of energyObjectMib module.
-- --
-- ************************************************************* -- *************************************************************
POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
Integer32 Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
UnitMultiplier UnitMultiplier
FROM ENERGY-OBJECT-MIB FROM ENERGY-OBJECT-MIB
OwnerString
FROM RMON-MIB
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
powerAttributesMIB MODULE-IDENTITY powerAttributesMIB MODULE-IDENTITY
LAST-UPDATED "201312130000Z" -- 13 December 2013 LAST-UPDATED "201402140000Z" -- 14 Feb 2014
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/eman/charter/ http://datatracker.ietf.org/wg/eman/charter/
Mailing Lists: Mailing Lists:
General Discussion: eman@ietf.org General Discussion: eman@ietf.org
To Subscribe: To Subscribe:
https://www.ietf.org/mailman/listinfo/eman https://www.ietf.org/mailman/listinfo/eman
Archive: Archive:
http://www.ietf.org/mail-archive/web/eman http://www.ietf.org/mail-archive/web/eman
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
skipping to change at page 53, line 20 skipping to change at page 49, line 33
Editors: Editors:
Mouli Chandramouli Mouli Chandramouli
Cisco Systems, Inc. Cisco Systems, Inc.
Sarjapur Outer Ring Road Sarjapur Outer Ring Road
Bangalore 560103 Bangalore 560103
IN IN
Phone: +91 80 4429 2409 Phone: +91 80 4429 2409
Email: moulchan@cisco.com Email: moulchan@cisco.com
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com
Brad Schoening Brad Schoening
44 Rivers Edge Drive 44 Rivers Edge Drive
Little Silver, NJ 07739 Little Silver, NJ 07739
US US
Email: brad.schoening@verizon.net Email: brad.schoening@verizon.net
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
skipping to change at page 54, line 5 skipping to change at page 50, line 7
Email: quittek@neclab.eu Email: quittek@neclab.eu
Thomas Dietz Thomas Dietz
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
Network Research Division Network Research Division
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
DE DE
Phone: +49 6221 4342-128 Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu" Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise
Cisco Systems, Inc.
De Kleetlaan 6a b1
Degem 1831
Belgium
Phone: +32 2 704 5622
Email: bclaise@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB is used to report AC power attributes in "This MIB is used to report AC power attributes in
devices. The table is a sparse augmentation of the devices. The table is a sparse augmentation of the
eoPowerTable table from the energyObjectMIB module. eoPowerTable table from the energyObjectMib module.
Both three-phase and single-phase power Both three-phase and single-phase power
configurations are supported. configurations are supported.
As a requirement for this MIB module, As a requirement for this MIB module,
[EMAN-AWARE-MIB] should be implemented. [EMAN-AWARE-MIB] SHOULD be implemented.
Module Compliance of ENTITY-MIB v4 Module Compliance of ENTITY-MIB v4
with respect to entity4CRCompliance should with respect to entity4CRCompliance MUST
be supported which requires implementation be supported which requires implementation
of 3 MIB objects (entPhysicalIndex, of 4 MIB objects: entPhysicalIndex, entPhysicalClass,
entPhysicalName and entPhysicalUUID)." entPhysicalName and entPhysicalUUID."
REVISION REVISION
"201312130000Z" -- 13 December 2013 "201402140000Z" -- 14 Feb 2014
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYY." "Initial version, published as RFC YYY."
::= { energyMIB 4 } ::= { mib-2 yyy }
powerAttributesMIBConform OBJECT IDENTIFIER powerAttributesMIBConform OBJECT IDENTIFIER
::= { powerAttributesMIB 0 } ::= { powerAttributesMIB 0 }
powerAttributesMIBObjects OBJECT IDENTIFIER powerAttributesMIBObjects OBJECT IDENTIFIER
::= { powerAttributesMIB 1 } ::= { powerAttributesMIB 1 }
-- Objects -- Objects
eoACPwrAttributesTable OBJECT-TYPE eoACPwrAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesEntry SYNTAX SEQUENCE OF EoACPwrAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines power attributes measurements for "This table contains power attributes measurements for
supported entPhysicalIndex entities. It is a sparse supported entPhysicalIndex entities. It is a sparse
extension of the eoPowerTable." extension of the eoPowerTable."
::= { powerAttributesMIBObjects 1 } ::= { powerAttributesMIBObjects 1 }
eoACPwrAttributesEntry OBJECT-TYPE eoACPwrAttributesEntry OBJECT-TYPE
SYNTAX EoACPwrAttributesEntry SYNTAX EoACPwrAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a sparse extension of the eoPowerTable with "This is a sparse extension of the eoPowerTable with
skipping to change at page 55, line 30 skipping to change at page 51, line 38
eoACPwrAttributesConfiguration INTEGER, eoACPwrAttributesConfiguration INTEGER,
eoACPwrAttributesAvgVoltage Integer32, eoACPwrAttributesAvgVoltage Integer32,
eoACPwrAttributesAvgCurrent Integer32, eoACPwrAttributesAvgCurrent Integer32,
eoACPwrAttributesFrequency Integer32, eoACPwrAttributesFrequency Integer32,
eoACPwrAttributesPowerUnitMultiplier UnitMultiplier, eoACPwrAttributesPowerUnitMultiplier UnitMultiplier,
eoACPwrAttributesPowerAccuracy Integer32, eoACPwrAttributesPowerAccuracy Integer32,
eoACPwrAttributesTotalActivePower Integer32, eoACPwrAttributesTotalActivePower Integer32,
eoACPwrAttributesTotalReactivePower Integer32, eoACPwrAttributesTotalReactivePower Integer32,
eoACPwrAttributesTotalApparentPower Integer32, eoACPwrAttributesTotalApparentPower Integer32,
eoACPwrAttributesTotalPowerFactor Integer32, eoACPwrAttributesTotalPowerFactor Integer32,
eoACPwrAttributesThdAmpheres Integer32, eoACPwrAttributesThdCurrent Integer32,
eoACPwrAttributesThdVoltage Integer32 eoACPwrAttributesThdVoltage Integer32
} }
eoACPwrAttributesConfiguration OBJECT-TYPE eoACPwrAttributesConfiguration OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
sngl(1), sngl(1),
del(2), del(2),
wye(3) wye(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 56, line 23 skipping to change at page 52, line 30
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value for average of the voltage measured "A measured value for average of the voltage measured
over an integral number of AC cycles For a 3-phase over an integral number of AC cycles For a 3-phase
system, this is the average voltage (V1+V2+V3)/3. IEC system, this is the average voltage (V1+V2+V3)/3. IEC
61850-7-4 measured value attribute 'Vol'" 61850-7-4 measured value attribute 'Vol'"
::= { eoACPwrAttributesEntry 2 } ::= { eoACPwrAttributesEntry 2 }
eoACPwrAttributesAvgCurrent OBJECT-TYPE eoACPwrAttributesAvgCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Ampheres" UNITS "amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the current per phase. IEC 61850- " A measured value for average of the current measured
7-4 attribute 'Amp'" over an integral number of AC cycles For a 3-phase
system, this is the average current (I1+I2+I3)/3. IEC
61850-7-4 attribute 'Amp'"
::= { eoACPwrAttributesEntry 3 } ::= { eoACPwrAttributesEntry 3 }
eoACPwrAttributesFrequency OBJECT-TYPE eoACPwrAttributesFrequency OBJECT-TYPE
SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz SYNTAX Integer32 (4500..6500)
UNITS "hertz" UNITS "0.01 hertz"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value for the basic frequency of the AC "A measured value for the basic frequency of the AC
circuit. IEC 61850-7-4 attribute 'Hz'." circuit. IEC 61850-7-4 attribute 'Hz'."
::= { eoACPwrAttributesEntry 4 } ::= { eoACPwrAttributesEntry 4 }
eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE
SYNTAX UnitMultiplier SYNTAX UnitMultiplier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The magnitude of watts for the usage value in "The magnitude of watts for the usage value in
eoACPwrAttributesTotalActivePower, eoACPwrAttributesTotalActivePower,
eoACPwrAttributesTotalReactivePower eoACPwrAttributesTotalReactivePower
and eoACPwrAttributesTotalApparentPower measurements. and eoACPwrAttributesTotalApparentPower measurements.
For 3-phase power systems, this will also include For 3-phase power systems, this will also include
eoACPwrAttributesPhaseActivePower, eoACPwrAttributesWyeActivePower,
eoACPwrAttributesPhaseReactivePower and eoACPwrAttributesWyeReactivePower and
eoACPwrAttributesPhaseApparentPower" eoACPwrAttributesWyeApparentPower"
::= { eoACPwrAttributesEntry 5 } ::= { eoACPwrAttributesEntry 5 }
eoACPwrAttributesPowerAccuracy OBJECT-TYPE eoACPwrAttributesPowerAccuracy OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a percentage value, in 100ths of "This object indicates a percentage value, in 100ths of
a percent, representing the presumed accuracy of a percent, representing the presumed accuracy of
skipping to change at page 57, line 30 skipping to change at page 53, line 35
accuracy is unknown. accuracy is unknown.
ANSI and IEC define the following accuracy classes for ANSI and IEC define the following accuracy classes for
power measurement: IEC 62053-22 & 60044-1 class 0.1, power measurement: IEC 62053-22 & 60044-1 class 0.1,
0.2, 0.5, 1 & 3. 0.2, 0.5, 1 & 3.
ANSI C12.20 class 0.2 & 0.5" ANSI C12.20 class 0.2 & 0.5"
::= { eoACPwrAttributesEntry 6 } ::= { eoACPwrAttributesEntry 6 }
eoACPwrAttributesTotalActivePower OBJECT-TYPE eoACPwrAttributesTotalActivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS " watts" UNITS "watts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the actual power delivered to or "A measured value of the actual power delivered to or
consumed by the load. IEC 61850-7-4 attribute 'TotW'." consumed by the load. IEC 61850-7-4 attribute 'TotW'."
::= { eoACPwrAttributesEntry 7 } ::= { eoACPwrAttributesEntry 7 }
eoACPwrAttributesTotalReactivePower OBJECT-TYPE eoACPwrAttributesTotalReactivePower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes reactive" UNITS "volt-amperes reactive"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A mesured value of the reactive portion of the "A measured value of the reactive portion of the
apparent power. IEC 61850-7-4 attribute 'TotVAr'." apparent power. IEC 61850-7-4 attribute 'TotVAr'."
::= { eoACPwrAttributesEntry 8 } ::= { eoACPwrAttributesEntry 8 }
eoACPwrAttributesTotalApparentPower OBJECT-TYPE eoACPwrAttributesTotalApparentPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "volt-amperes" UNITS "volt-amperes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of the voltage and current which "A measured value of the voltage and current which
determines the apparent power. The apparent power is determines the apparent power. The apparent power is
the vector sum of real and reactive power. the vector sum of real and reactive power.
Note: watts and volt-ampheres are equivalent units and Note: watts and volt-amperes are equivalent units and
may be combined. IEC 61850-7-4 attribute 'TotVA'." may be combined. IEC 61850-7-4 attribute 'TotVA'."
::= { eoACPwrAttributesEntry 9 } ::= { eoACPwrAttributesEntry 9 }
eoACPwrAttributesTotalPowerFactor OBJECT-TYPE eoACPwrAttributesTotalPowerFactor OBJECT-TYPE
SYNTAX Integer32 (-10000..10000) SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value ratio of the real power flowing to "A measured value ratio of the real power flowing to
the load versus the apparent power. It is dimensionless the load versus the apparent power. It is dimensionless
and expressed here as a percentage value in 100ths of a and expressed here as a percentage value in 100ths of a
percent. A power factor of 100% indicates there is no percent. A power factor of 100% indicates there is no
inductance load and thus no reactive power. Power inductance load and thus no reactive power. Power
Factor can be positive or negative, where the sign Factor can be positive or negative, where the sign
should be in lead/lag (IEEE) form. IEC 61850-7-4 should be in lead/lag (IEEE) form. IEC 61850-7-4
attribute 'TotPF'." attribute 'TotPF'."
::= { eoACPwrAttributesEntry 10 } ::= { eoACPwrAttributesEntry 10 }
eoACPwrAttributesThdAmpheres OBJECT-TYPE eoACPwrAttributesThdCurrent OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value for the current total harmonic "A calculated value for the current total harmonic
distortion (THD). Method of calculation is not distortion (THD). Method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdAmp'." specified. IEC 61850-7-4 attribute 'ThdAmp'."
::= { eoACPwrAttributesEntry 11 } ::= { eoACPwrAttributesEntry 11 }
skipping to change at page 59, line 5 skipping to change at page 55, line 5
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value for the voltage total harmonic "A calculated value for the voltage total harmonic
distortion (THD). Method of calculation is not distortion (THD). Method of calculation is not
specified. IEC 61850-7-4 attribute 'ThdVol'." specified. IEC 61850-7-4 attribute 'ThdVol'."
::= { eoACPwrAttributesEntry 12 } ::= { eoACPwrAttributesEntry 12 }
eoACPwrAttributesPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesPhaseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table describes 3-phase power attributes
measurements. It is a sparse extension of the
eoACPwrAttributesTable."
::= { powerAttributesMIBObjects 2 }
eoACPwrAttributesPhaseEntry OBJECT-TYPE
SYNTAX EoACPwrAttributesPhaseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes common 3-phase power attributes
measurements.
This optional table describes 3-phase power attributes
measurements, with three entries for each supported
entPhysicalIndex entity. Entities having single phase
power shall not have any entities.
This table describes attributes common to both WYE and
DEL. Entities having single phase power shall not have
any entries here. It is a sparse extension of the
eoACPwrAttributesTable.
These attributes correspond to IEC 61850-7.4 MMXU phase
measurements."
INDEX { entPhysicalIndex, eoPhaseIndex }
::= { eoACPwrAttributesPhaseTable 1 }
EoACPwrAttributesPhaseEntry ::= SEQUENCE {
eoPhaseIndex Integer32,
eoACPwrAttributesPhaseAvgCurrent Integer32,
eoACPwrAttributesPhaseActivePower Integer32,
eoACPwrAttributesPhaseReactivePower Integer32,
eoACPwrAttributesPhaseApparentPower Integer32,
eoACPwrAttributesPhasePowerFactor Integer32,
eoACPwrAttributesPhaseImpedance Integer32
}
eoPhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesPhaseEntry 1 }
eoACPwrAttributesPhaseAvgCurrent OBJECT-TYPE
SYNTAX Integer32
UNITS "Ampheres"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the current per phase. IEC 61850-
7-4 attribute 'A'"
::= { eoACPwrAttributesPhaseEntry 2 }
eoACPwrAttributesPhaseActivePower OBJECT-TYPE
SYNTAX Integer32
UNITS " watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the actual power delivered to or
consumed by the load. IEC 61850-7-4 attribute 'W'"
::= { eoACPwrAttributesPhaseEntry 3 }
eoACPwrAttributesPhaseReactivePower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes reactive"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the reactive portion of the
apparent power. IEC 61850-7-4 attribute 'VAr'"
::= { eoACPwrAttributesPhaseEntry 4 }
eoACPwrAttributesPhaseApparentPower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the voltage and current determines
the apparent power. Active plus reactive power equals
the total apparent power.
Note: Watts and volt-ampheres are equivalent units and
may be combined. IEC 61850-7-4 attribute 'VA'."
::= { eoACPwrAttributesPhaseEntry 5 }
eoACPwrAttributesPhasePowerFactor OBJECT-TYPE
SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value ratio of the real power flowing to
the load versus the apparent power for this phase. IEC
61850-7-4 attribute 'PF'. Power Factor can be positive
or negative where the sign should be in lead/lag (IEEE)
form."
::= { eoACPwrAttributesPhaseEntry 6 }
eoACPwrAttributesPhaseImpedance OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the impedance. IEC 61850-7-4 attribute
'Z'."
::= { eoACPwrAttributesPhaseEntry 7 }
eoACPwrAttributesDelPhaseTable OBJECT-TYPE eoACPwrAttributesDelPhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes DEL configuration phase-to-phase "This optional table describes 3-phase power attributes
power attributes measurements. This is a sparse measurements in a DEL configuration with phase-to-phase
extension of the eoACPwrAttributesPhaseTable." power attributes measurements. Entities having single
::= { powerAttributesMIBObjects 3 } phase power shall not have any entities. This is a
sparse extension of the eoACPwrAttributesTable.
These attributes correspond to IEC 61850-7.4 MMXU phase
related measurements and MHAI phase related measured
harmonic or interharmonics."
::= { powerAttributesMIBObjects 2 }
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 measurements of a phase in a
phase in a DEL 3-phase power system. Voltage DEL 3-phase power. Three entries are required for each
measurements are provided both relative to each other supported entPhysicalIndex entry. Voltage measurements
and zero. are provided relative to each other.
Measured values are from IEC 61850-7-2 MMUX and THD from
MHAI objects.
For phase-to-phase measurements, the eoPhaseIndex is For phase-to-phase measurements, the
compared against the following phase at +120 degrees. eoACPwrAttributesDelPhaseIndex is compared against the
Thus, the possible values are: following phase at +120 degrees. Thus, the possible
values are:
eoPhaseIndex Next Phase Angle eoACPwrAttributesDelPhaseIndex Next Phase Angle
0 120 0 120
120 240 120 240
240 0 240 0
" "
INDEX { entPhysicalIndex, eoPhaseIndex} INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex}
::= { eoACPwrAttributesDelPhaseTable 1} ::= { eoACPwrAttributesDelPhaseTable 1}
EoACPwrAttributesDelPhaseEntry ::= SEQUENCE { EoACPwrAttributesDelPhaseEntry ::= SEQUENCE {
eoACPwrAttributesDelPhaseIndex Integer32,
eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32, eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32, eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32
eoACPwrAttributesDelThdCurrent Integer32
} }
eoACPwrAttributesDelPhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesDelPhaseEntry 1 }
eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 Volt AC" UNITS "0.1 Volt AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of phase to next phase voltages, where "A measured value of phase to next phase voltages, where
the next phase is IEC 61850-7-4 attribute 'PPV'." the next phase is IEC 61850-7-4 attribute 'PPV'."
::= { eoACPwrAttributesDelPhaseEntry 2 } ::= { eoACPwrAttributesDelPhaseEntry 2 }
skipping to change at page 62, line 44 skipping to change at page 56, line 29
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value for the voltage total harmonic "A calculated value for the voltage total harmonic
disortion for phase to next phase. Method of calculation disortion for phase to next phase. Method of calculation
is not specified. IEC 61850-7-4 attribute 'ThdPPV'." is not specified. IEC 61850-7-4 attribute 'ThdPPV'."
::= { eoACPwrAttributesDelPhaseEntry 3 } ::= { eoACPwrAttributesDelPhaseEntry 3 }
eoACPwrAttributesDelThdCurrent OBJECT-TYPE
SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
disortion (THD) for phase to phase. Method of
calculation is not specified.
IEC 61850-7-4 attribute 'ThdPPV'."
::= { eoACPwrAttributesDelPhaseEntry 4 }
eoACPwrAttributesWyePhaseTable OBJECT-TYPE eoACPwrAttributesWyePhaseTable OBJECT-TYPE
SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes WYE configuration phase-to-neutral "This optional table describes 3-phase power attributes
power attributes measurements. This is a sparse measurements in a WYE configuration with phase-to-
extension of the eoACPwrAttributesPhaseTable." neutral power attributes measurements. Entities having
::= { powerAttributesMIBObjects 4 } single phase power shall not have any entities. This is
a sparse extension of the eoACPwrAttributesTable.
These attributes correspond to IEC 61850-7.4 MMXU phase
related measurements and MHAI phase related measured
harmonic or interharmonics."
::= { powerAttributesMIBObjects 3 }
eoACPwrAttributesWyePhaseEntry OBJECT-TYPE eoACPwrAttributesWyePhaseEntry OBJECT-TYPE
SYNTAX EoACPwrAttributesWyePhaseEntry SYNTAX EoACPwrAttributesWyePhaseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes measurements of WYE configuration "This table describes measurements of a phase in a WYE
with phase to neutral power attributes attributes. Three 3-phase power system. Three entries are required for
entries are required for each supported entPhysicalIndex each supported entPhysicalIndex entry. Voltage
entry. Voltage measurements are relative to neutral. measurements are relative to neutral.
This is a sparse extension of the
eoACPwrAttributesPhaseTable.
Each entry describes power attributes attributes of one
phase of a WYE 3-phase power system.
Measured values are from IEC 61850-7-2 MMUX and THD from Each entry describes power attributes of one phase of a
MHAI objects." WYE 3-phase power system."
INDEX { entPhysicalIndex, eoPhaseIndex } INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex }
::= { eoACPwrAttributesWyePhaseTable 1} ::= { eoACPwrAttributesWyePhaseTable 1}
EoACPwrAttributesWyePhaseEntry ::= SEQUENCE { EoACPwrAttributesWyePhaseEntry ::= SEQUENCE {
eoACPwrAttributesWyePhaseIndex Integer32,
eoACPwrAttributesWyePhaseToNeutralVoltage Integer32, eoACPwrAttributesWyePhaseToNeutralVoltage Integer32,
eoACPwrAttributesWyePhaseCurrent Integer32, eoACPwrAttributesWyeCurrent Integer32,
eoACPwrAttributesWyeActivePower Integer32,
eoACPwrAttributesWyeReactivePower Integer32,
eoACPwrAttributesWyeApparentPower Integer32,
eoACPwrAttributesWyePowerFactor Integer32,
eoACPwrAttributesWyeThdCurrent Integer32,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32 eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
} }
eoACPwrAttributesWyePhaseIndex OBJECT-TYPE
SYNTAX Integer32 (0..359)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A phase angle typically corresponding to 0, 120, 240."
::= { eoACPwrAttributesWyePhaseEntry 1 }
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 'PNV'."
::= { eoACPwrAttributesWyePhaseEntry 2 }
::= { eoACPwrAttributesWyePhaseEntry 1 }
eoACPwrAttributesWyePhaseCurrent OBJECT-TYPE eoACPwrAttributesWyeCurrent OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 ampheres AC" UNITS "0.1 amperes AC"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A measured value of phase currents. IEC 61850-7-4 "A measured value of phase currents. IEC 61850-7-4
attribute 'A'." attribute 'A'."
::= { eoACPwrAttributesWyePhaseEntry 2 } ::= { eoACPwrAttributesWyePhaseEntry 3 }
eoACPwrAttributesWyeActivePower OBJECT-TYPE
SYNTAX Integer32
UNITS "watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the actual power delivered to or
consumed by the load with the magnitude indicated
separately in eoPowerUnitMultiplier. IEC 61850-7-4
attribute 'W'"
::= { eoACPwrAttributesWyePhaseEntry 4 }
eoACPwrAttributesWyeReactivePower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes reactive"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the reactive portion of the
apparent power with the magnitude of indicated
separately in eoPowerUnitMultiplier. IEC 61850-7-4
attribute 'VAr'"
::= { eoACPwrAttributesWyePhaseEntry 5 }
eoACPwrAttributesWyeApparentPower OBJECT-TYPE
SYNTAX Integer32
UNITS "volt-amperes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value of the voltage and current determines
the apparent power with the indicated separately in
eoPowerUnitMultiplier. Active plus reactive power
equals the total apparent power.
Note: Watts and volt-amperes are equivalent units and
may be combined. IEC 61850-7-4 attribute 'VA'."
::= { eoACPwrAttributesWyePhaseEntry 6 }
eoACPwrAttributesWyePowerFactor OBJECT-TYPE
SYNTAX Integer32 (-10000..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A measured value ratio of the real power flowing to
the load versus the apparent power for this phase. IEC
61850-7-4 attribute 'PF'. Power Factor can be positive
or negative where the sign should be in lead/lag (IEEE)
form."
::= { eoACPwrAttributesWyePhaseEntry 7 }
eoACPwrAttributesWyeThdCurrent OBJECT-TYPE
SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A calculated value for the voltage total harmonic
disortion (THD) for phase to phase. Method of
calculation is not specified.
IEC 61850-7-4 attribute 'ThdA'."
::= { eoACPwrAttributesWyePhaseEntry 8 }
eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE
SYNTAX Integer32 (0..10000) SYNTAX Integer32 (0..10000)
UNITS "hundredths of percent" UNITS "hundredths of percent"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A calculated value of the voltage total harmonic "A calculated value of the voltage total harmonic
distortion (THD) for phase to neutral. IEC 61850-7-4 distortion (THD) for phase to neutral. IEC 61850-7-4
attribute 'ThdPhV'." attribute 'ThdPhV'."
::= { eoACPwrAttributesWyePhaseEntry 3 } ::= { eoACPwrAttributesWyePhaseEntry 9 }
-- Conformance -- Conformance
powerAttributesMIBCompliances OBJECT IDENTIFIER powerAttributesMIBCompliances OBJECT IDENTIFIER
::= { powerAttributesMIB 2 } ::= { powerAttributesMIB 2 }
powerAttributesMIBGroups OBJECT IDENTIFIER powerAttributesMIBGroups OBJECT IDENTIFIER
::= { 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 [RFC6933] with respect to Module Compliance of [RFC6933] with respect to
entity4CRCompliance should be supported which requires entity4CRCompliance MUST be supported which requires
implementation of 3 MIB objects (entPhysicalIndex, implementation of 4 MIB objects: entPhysicalIndex,
entPhysicalName and entPhysicalUUID)." entPhysicalClass, entPhysicalName and entPhysicalUUID."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
powerACPwrAttributesMIBTableGroup powerACPwrAttributesMIBTableGroup
} }
GROUP powerACPwrAttributesOptionalMIBTableGroup GROUP powerACPwrAttributesOptionalMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have "A compliant implementation does not have
to implement." to implement."
GROUP powerACPwrAttributesPhaseMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to
implement."
GROUP powerACPwrAttributesDelPhaseMIBTableGroup GROUP powerACPwrAttributesDelPhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
GROUP powerACPwrAttributesWyePhaseMIBTableGroup GROUP powerACPwrAttributesWyePhaseMIBTableGroup
DESCRIPTION DESCRIPTION
"A compliant implementation does not have to "A compliant implementation does not have to
implement." implement."
skipping to change at page 66, line 4 skipping to change at page 60, line 40
eoACPwrAttributesAvgVoltage, eoACPwrAttributesAvgVoltage,
eoACPwrAttributesAvgCurrent, eoACPwrAttributesAvgCurrent,
eoACPwrAttributesFrequency, eoACPwrAttributesFrequency,
eoACPwrAttributesPowerUnitMultiplier, eoACPwrAttributesPowerUnitMultiplier,
eoACPwrAttributesPowerAccuracy, eoACPwrAttributesPowerAccuracy,
eoACPwrAttributesTotalActivePower, eoACPwrAttributesTotalActivePower,
eoACPwrAttributesTotalReactivePower, eoACPwrAttributesTotalReactivePower,
eoACPwrAttributesTotalApparentPower, eoACPwrAttributesTotalApparentPower,
eoACPwrAttributesTotalPowerFactor eoACPwrAttributesTotalPowerFactor
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
attributes objects related to the Energy Object." attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 1 } ::= { powerAttributesMIBGroups 1 }
powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
eoACPwrAttributesConfiguration, eoACPwrAttributesConfiguration,
eoACPwrAttributesThdAmpheres, eoACPwrAttributesThdCurrent,
eoACPwrAttributesThdVoltage eoACPwrAttributesThdVoltage
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all the power "This group contains the collection of all the power
attributes objects related to the Energy Object." attributes objects related to the Energy Object."
::= { powerAttributesMIBGroups 2 } ::= { powerAttributesMIBGroups 2 }
powerACPwrAttributesPhaseMIBTableGroup OBJECT-GROUP
OBJECTS {
-- Note that object entPhysicalIndex is
-- NOT included since it is
-- not-accessible
eoACPwrAttributesPhaseAvgCurrent,
eoACPwrAttributesPhaseActivePower,
eoACPwrAttributesPhaseReactivePower,
eoACPwrAttributesPhaseApparentPower,
eoACPwrAttributesPhasePowerFactor,
eoACPwrAttributesPhaseImpedance
}
STATUS current
DESCRIPTION
"This group contains the collection of all 3-phase power
attributes objects related to the Power State."
::= { powerAttributesMIBGroups 3 }
powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoACPwrAttributesDelPhaseIndex are NOT
-- since they are not-accessible -- included since they are not-accessible
eoACPwrAttributesDelPhaseToNextPhaseVoltage , eoACPwrAttributesDelPhaseToNextPhaseVoltage,
eoACPwrAttributesDelThdPhaseToNextPhaseVoltage, eoACPwrAttributesDelThdPhaseToNextPhaseVoltage
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 attributes of a phase in a DEL 3-phase power system."
power system." ::= { powerAttributesMIBGroups 3 }
::= { powerAttributesMIBGroups 4 }
powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- Note that object entPhysicalIndex and -- Note that object entPhysicalIndex and
-- eoPhaseIndex are NOT included -- eoACPwrAttributesWyePhaseIndex are NOT
-- since they are not-accessible -- included since they are not-accessible
eoACPwrAttributesWyePhaseToNeutralVoltage, eoACPwrAttributesWyePhaseToNeutralVoltage,
eoACPwrAttributesWyePhaseCurrent, eoACPwrAttributesWyeCurrent,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage eoACPwrAttributesWyeActivePower,
eoACPwrAttributesWyeReactivePower,
eoACPwrAttributesWyeApparentPower,
eoACPwrAttributesWyePowerFactor,
eoACPwrAttributesWyeThdPhaseToNeutralVoltage,
eoACPwrAttributesWyeThdCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains the collection of all WYE "This group contains the collection of all power
configuration phase-to-neutral power attributes attributes of a phase in a WYE 3-phase power system."
measurements." ::= { powerAttributesMIBGroups 4 }
::= { powerAttributesMIBGroups 5 }
END END
IANA-POWERSTATE-SET-MIB DEFINITIONS ::= BEGIN 10. Implementation Status
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ianaPowerStateSetMIB MODULE-IDENTITY
LAST-UPDATED "201312130000Z" -- December 13, 2013
ORGANIZATION "IANA"
CONTACT-INFO "
Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1-310-823-9358
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines a TEXTUAL-CONVENTION that
describes the relationships between Energy Objects.
Copyright (C) The IETF Trust (2013).
The initial version of this MIB module was published in
RFC YYY; for full legal notices see the RFC itself.
Supplementary information may be available at
http://www.ietf.org/copyrights/ianamib.html"
REVISION "201312130000Z" -- December 13, 2013
DESCRIPTION "Initial version of this MIB as published in
RFC YYY."
::= { energyMIB 5 }
-- RFC Editor, please replace YYY with the IANA allocation
-- for this MIB module and YYY with the number of the
-- approved RFC
-- Textual Conventions
IANAPowerStateSet::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IANAPowerState is a textual convention that describes
Power State Sets and Power State Set Values an Energy Object
supports. IANA has created a registry of Power State supported
by an Energy Object and IANA shall administer the list of
Power State Sets and Power States.
The textual convention assumes that Power States in a power
state set are limited to 255 distinct values. For a Power
State Set S, the named number with the value S * 256 is
allocated to indicate the Power State set. For a Power State X
in the Power State S, the named number with the value S * 256
+ X + 1 is allocated to represent the Power State."
REFERENCE
"http://www.iana.org/assignments/eman
RFC EDITOR NOTE: please change the previous URL if this is
not the correct one after IANA assigned it."
SYNTAX INTEGER {
other(0), -- indicates other set
unknown(255), -- unknown
ieee1621(256), -- indicates IEEE1621 set
ieee1621On(257),
ieee1621Off(258),
ieee1621Sleep(259),
dmtf(512), -- indicates DMTF set
dmtfOn(513),
dmtfSleepLight(514),
dmtfSleepDeep(515),
dmtfOffHard(516),
dmtfOffSoft(517),
dmtfHibernate(518),
dmtfPowerOffSoft(519),
dmtfPowerOffHard(520),
dmtfMasterBusReset(521),
dmtfDiagnosticInterrapt(522),
dmtfOffSoftGraceful(523),
dmtfOffHardGraceful(524),
dmtfMasterBusResetGraceful(525),
dmtfPowerCycleOffSoftGraceful(526),
dmtfPowerCycleHardGraceful(527),
eman(1024), -- indicates EMAN set
emanmechoff(1025),
emansoftoff(1026),
emanhibernate(1027),
emansleep(1028),
emanstandby(1029),
emanready(1030),
emanlowMinus(1031),
emanlow(1032),
emanmediumMinus(1033),
emanmedium(1034),
emanhighMinus(1035),
emanhigh(1036)
}
END
11. Implementation Status
[Note to RFC Editor: Please remove this section and the [Note to RFC Editor: Please remove this section and the
reference to [RFC6982] before publication.] reference to [RFC6982] before publication.]
This section records the status of known implementations of the This section records the status of known implementations of the
EMAN-Monitoring MIB at the time of posting of this Internet- EMAN-Monitoring MIB at the time of posting of this Internet-
Draft, and is based on a proposal described in [RFC6982]. Draft, and is based on a proposal described in [RFC6982].
The description of implementations in this section is intended The description of implementations in this section is intended
to assist the IETF in its decision processes in progressing to assist the IETF in its decision processes in progressing
drafts to RFCs. drafts to RFCs.
11.1. SNMP Research 10.1. SNMP Research
Organization: SNMP Research, Inc. Organization: SNMP Research, Inc.
Maturity: Prototype based upon early drafts of the MIBs. Maturity: Prototype based upon early drafts of the MIBs.
We anticipate updating it to more recent We anticipate updating it to more recent
documents as development schedules allow. documents as development schedules allow.
Coverage: Code was generated to implement all MIB objects Coverage: Code was generated to implement all MIB objects
in ENTITY-MIB (Version 4), in ENTITY-MIB (Version 4),
ENERGY-OBJECT-CONTEXT-MIB, ENERGY-OBJECT-CONTEXT-MIB,
skipping to change at page 70, line 46 skipping to change at page 62, line 48
BATTERY-MIB BATTERY-MIB
were submitted to the EMAN Working Group were submitted to the EMAN Working Group
E-mail list. E-mail list.
Licensing: Proprietary, royalty licensing Licensing: Proprietary, royalty licensing
Contact: Alan Luchuk, luchuk at snmp.com Contact: Alan Luchuk, luchuk at snmp.com
URL: http://www.snmp.com/ URL: http://www.snmp.com/
11.2. Cisco Systems 10.2. Cisco Systems
Organization: Cisco Systems, Inc. Organization: Cisco Systems, Inc.
Maturity: Prototype based upon early version drafts of Maturity: Prototype based upon early version drafts of
the MIBs. We anticipate updating the MIB the MIBs. We anticipate updating the MIB
modules as when the drafts are updated. modules as when the drafts are updated.
Coverage: Code was generated to implement all MIB objects Coverage: Code was generated to implement all MIB objects
in the ENTITY-MIB (Version 4), and in the ENTITY-MIB (Version 4), and
ENERGY-OBJECT-MIB. ENERGY-OBJECT-MIB.
Implementation experience: The MIB modules are implemented Implementation experience: The MIB modules are implemented
on Cisco router platforms to measure and report on Cisco router platforms to measure and report
router energy measurements. The documents are router energy measurements. The documents are
implementable. implementable.
Licensing: Proprietary Licensing: Proprietary
URL: http://www.cisco.com URL: http://www.cisco.com
12. Security Considerations 11. Security Considerations
Some of the readable objects in these MIB modules (i.e., objects Some of the readable objects in these MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
thus important to control even GET and/or NOTIFY access to these thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects objects and possibly to even encrypt the values of these objects
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 72, line 18 skipping to change at page 64, line 18
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.
13. IANA Considerations 12. IANA Considerations
Additions to the ENERGY-OBJECT-MIB MIB and POWER-ATTRIBUTES-MIB
MIB modules are subject to Expert Review [RFC5226], i.e., review
by one of a group of experts designated by an IETF Area
Director. The group of experts MUST check the requested MIB
objects for completeness and accuracy of the description.
Requests for MIB objects that duplicate the functionality of
existing objects SHOULD be declined. The smallest available
OIDs SHOULD be assigned to the new MIB objects. The
specification of new MIB objects SHOULD follow the structure
specified in Section 10. and MUST be published using a well-
established and persistent publication medium.
13.1. IANA Registration of new Power State Set
The initial set of Power State Sets are specified in [EMAN-
FMWK]. IANA maintains a Textual Convention IANAPowerStateSet
with the initial set of Power State Sets and the Power States
within those Power State Sets as proposed in the [EMAN-FMWK].
The current version of IANAPowerStateSet Textual convention can
be accessed http://www.iana.org/assignments/IANAPowerStateSet.
New Assignments (and potential deprecation) to Power State Sets
shall be administered by IANA and the guidelines and
procedures are specified in [EMAN-FMWK], and will, as a
consequence, the IANAPowerStateSet Textual Convention should be
updated.
13.1.1. IANA Registration of the IEEE1621 Power State Set
The Internet Assigned Numbers Authority (IANA) has created a new
registry for IEEE1621 Power State Set identifiers and filled it
with the initial list in the Textual Convention
IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for
IEEE1621 Power State Set are specified in [EMAN-FMWK].
13.1.2. IANA Registration of the DMTF Power State Set The MIB modules in this document use the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
The Internet Assigned Numbers Authority (IANA) has created a new Descriptor OBJECT IDENTIFIER value
registry for DMTF Power State Set identifiers and filled it in
the Textual Convention IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for ---------- -----------------------
DMTF Power State Set are specified in [EMAN-FMWK].
13.1.3. IANA Registration of the EMAN Power State Set energyObjectMIB { mib-2 xxx }
The Internet Assigned Numbers Authority (IANA) has created a new powerAttributesMIB { mib-2 yyy }
registry for EMAN Power State Set identifiers and filled it in
the Textual Convention IANAPowerStateSet.
Guidelines for new assignments (or potentially deprecation) for Editor's Note (to be removed prior to publication): IANA is
EMAN Power State Set are specified in [EMAN-FMWK]. requested to assign a value for "XXX" and "YYY" under the 'mib-
2' subtree and to record the assignment in the SMI Numbers
registry. When the assignment has been made, the RFC Editor is
asked to replace "XXX" and "YYY"(here and in the MIB module)
with the assigned value and to remove this note.
14. Contributors 13. 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
12. Acknowledgment 14. 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.
The authors would like to thank Juergen Schoenwalder for The authors would like to thank Juergen Schoenwalder for
proposing the design of the Textual Convention for proposing the design of the Textual Convention for
IANAPowerStateSet and Ira McDonald for his feedback. Thanks for IANAPowerStateSet and Ira McDonald for his feedback. Special
the many comments on the design of the EnergyTable from Minoru appreciation to Laurent Guise for his review and input on power
Teraoka and Hiroto Ogaki. quality measurements. Thanks for the many comments on the design
of the EnergyTable from Minoru Teraoka and Hiroto Ogaki.
Many thanks to Alan Luchuk for the detailed review of the MIB Many thanks to Alan Luchuk for the detailed review of the MIB
and his comments. and his comments.
And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom
Nadeau. Nadeau.
13. References 15. References
13.1. Normative References 15.1. Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, BCP 14, RFC 2119, March 1997. Requirement Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB",
RFC3621, December 2003. RFC3621, December 2003.
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
3)", RFC 4133, August 2005. Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013.
[EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili, [EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili,
"draft-ietf-eman-energy-aware-mib-11 ", work in "draft-ietf-eman-energy-aware-mib-14", work in
progress, November 2013. progress, February 10 2013.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
13.2. Informative References 15.2. Informative References
[RFC1628] S. Bradner, "UPS Management Information Base", RFC [RFC1628] S. Bradner, "UPS Management Information Base", RFC
1628, May 1994 1628, May 1994
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework ", RFC 3410, December Standard Management Framework ", RFC 3410, December
2002. 2002.
[RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S.
skipping to change at page 75, line 30 skipping to change at page 66, line 34
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity
Sensor Management Information Base", RFC 3433, December Sensor Management Information Base", RFC 3433, December
2002. 2002.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC
4268, November 2005. 4268, November 2005.
[RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie,
"Guidelines for Writing an IANA Considerations Section "Guidelines for Writing an IANA Considerations Section
in RFCs ", BCP 26, RFC 5226, May 2008. in RFCs ", BCP 26, RFC 5226, May 2008.
[RFC6933] A. Bierman, D. Romascanu, J. Quittek and M.
Chandramouli " Entity MIB (Version 4)", RFC 6933, May
2013.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of
Running Code: The Implementation Status Section", RFC Running Code: The Implementation Status Section", RFC
6982, July 2013. 6982, July 2013.
[RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M. [RFC6988] Quittek, J., Winter, R., Dietz, T., Claise, B., and M.
Chandramouli, " Requirements for Energy Management", Chandramouli, " Requirements for Energy Management",
RFC 6988, September 2013. RFC 6988, September 2013.
[EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek, [EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek,
J., "Energy Management Framework", draft-ietf-eman- J., "Energy Management Framework", draft-ietf-eman-
 End of changes. 314 change blocks. 
1089 lines changed or deleted 810 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/