< draft-claise-power-management-arch-01.txt   draft-claise-power-management-arch-02.txt >
Network Working Group B. Claise Network Working Group B. Claise
Internet-Draft J. Parello Internet-Draft J. Parello
Intended Status: Informational B. Schoening Intended Status: Informational B. Schoening
Expires: March 17, 2011 Cisco Systems, Inc. Expires: April 20, 2011 Cisco Systems, Inc.
September 17, 2010 October 20, 2010
Power Management Architecture Power Management Architecture
draft-claise-power-management-arch-01 draft-claise-power-management-arch-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79. with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 2, line 24 skipping to change at page 3, line 5
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Abstract Abstract
This document defines the power management architecture. This document defines the power management architecture.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction............................................... 4 1. Introduction.............................................. 4
2. Uses Cases & Requirements.................................. 5 2. Use Cases & Requirements.................................. 5
3. Terminology................................................ 5 3. Terminology............................................... 5
4. Architecture High Level Concepts and Scope................. 6 4. Energy Management Reference Model......................... 7
4.1. Power Monitor Information............................. 8 5. Architecture High Level Concepts and Scope................ 9
4.2. Power Monitor Meter Domain............................ 8 5.1. Power Monitor Information........................... 11
4.3. Power Monitor Parent and Child........................ 9 5.2. Power Monitor Meter Domain.......................... 11
4.4. Power Monitor Context................................ 10 5.3. Power Monitor Parent and Child...................... 11
4.5. Power Monitor Levels................................. 11 5.4. Power Monitor Context............................... 12
4.6. Power Monitor Usage Measurement...................... 13 5.5. Power Monitor Levels................................ 13
4.7. Optional Power Usage Quality......................... 14 5.6. Power Monitor Usage Measurement..................... 16
4.8. Optional Energy Measurement.......................... 14 5.7. Optional Power Usage Quality........................ 17
4.9. Optional Battery Information......................... 15 5.8. Optional Energy Measurement......................... 18
5. Power Monitor Children Discovery.......................... 15 5.9. Optional Battery Information........................ 18
6. Configuration............................................. 16 6. Power Monitor Children Discovery......................... 18
7. Fault Management.......................................... 16 7. Configuration............................................ 19
8. Relationship with Other Standard Development 8. Fault Management......................................... 20
Organizations................................................ 17 9. IPFIX.................................................... 20
8.1. Information Modeling................................. 17 10. Relationship with Other Standards Development
8.2. Power Levels......................................... 17 Organizations............................................... 21
9. Implementation Scenarios.................................. 18 10.1. Information Modeling............................... 21
Scenario 1: Switch with PoE endpoints..................... 18 10.2. Power Levels....................................... 21
11. Implementation Scenarios................................ 22
Scenario 1: Switch with PoE endpoints.................... 22
Scenario 2: Switch with PoE endpoints with further connected Scenario 2: Switch with PoE endpoints with further connected
device(s)................................................. 18 device(s)................................................ 22
Scenario 3: A switch with Wireless Access Points.......... 18 Scenario 3: A switch with Wireless Access Points......... 22
Scenario 4: Network connected facilities gateway.......... 19 Scenario 4: Network connected facilities gateway......... 23
Scenario 5: Data Center Network........................... 19 Scenario 5: Data center network.......................... 23
Scenario 6: Building Gateway Device....................... 19 Scenario 6: Building gateway device...................... 23
Scenario 7: Power Consumption of UPS...................... 19 Scenario 7: Power consumption of UPS..................... 23
Scenario 8: Power Consumption of Battery-based Devices.... 20 Scenario 8: Power consumption of battery-based devices... 24
10. Security Considerations.................................. 20 12. Security Considerations................................. 24
11. IANA Considerations...................................... 20 12.1. Security Considerations for SNMP...................... 24
12. References............................................... 20 12.2. Security Considerations for IPFIX..................... 25
Normative References...................................... 20 13. IANA Considerations..................................... 25
Informative References.................................... 20 14. Acknowledgments......................................... 25
13. Authors' Addresses....................................... 21 15. References.............................................. 25
Normative References..................................... 25
Informative References................................... 26
TO DO: TO DO
. Since we have the notion of desired versus actual Power - Question for the Working Group: Should the WG consider
Level, we must deal with the notion of transition state: IPFIX in this architecture?
Gracefully versus hard way. Note: the transition states are - Question for the Working Group: How to specify the notion
apparently described in the DMTF model. of child capabilities, i.e. the capabilities that the
Power Monitor Parents have with Power Monitor Children.
For Example:
1. Monitoring (only reporting)
2. Configuration power state
3. Configuration: power
Example: on a PC, we can set power level without knowing
the power. A solution must be specified in this draft.
. In terms of other SDOs, discuss DMTF? - Question for the Working Group: Should transition states
be tracked when setting a level. Example: The configured
level is set to Off from High. The Actual level will
take time to update as the device powers down. Should
there be transitions shown or will the two variables
suffice to track the device state.
. Do we need the pmIndex persistence? - Question for working group: Should implementation
scenarios be incorporated in the architecture draft
. Security Considerations to be done - We should have a similar section, for all the drafts,
which includes an overview of all EMAN documents.
1. Introduction 1. Introduction
Network management is typically divided into areas of concerns Network management is typically divided into the five main
according to the ISO Telecommunications Management Network network management areas defined in the ISO Telecommunications
model. The model defines Fault, Configuration, Accounting, Management Network model: Fault, Configuration, Accounting,
Performance, and Security Management. Notably missing is an Performance, and Security Management. Absent from this model is
area of concern specifically covering energy management at an any consideration of energy management, which is now becoming a
equal level to these areas. critical area of concern worldwide.
With energy becoming a more critical area of concern, this This document defines an architecture for power management for
document defines an architecture for power management for use devices within or connected to communication networks. This
with devices in and connected to communication networks. This
architecture includes monitoring for power state and energy architecture includes monitoring for power state and energy
consumption of networked elements, taking into account the consumption of networked elements, covering the requirements
requirements specified in [POWER-MON-REQ]. However, this specified in [POWER-MON-REQ]. It also goes a step further in
architecture goes one step further, as it includes some elements defining some elements of configuration.
of elements of configuration.
Energy management is applicable to devices that comprise and Energy management is applicable to devices in communication
that are connected to a communication network. Target devices networks. Target devices for this specification include (but
for this specification include (but are not limited to): are not limited to): routers, switches, Power over Ethernet
routers, switches, Power over Ethernet (PoE) endpoints, protocol (PoE) endpoints, protocol gateways for building management
gateways for building management systems, intelligent meters, systems, intelligent meters, home energy gateway, hosts and
home energy gateway, hosts and servers, sensor proxy, etc. servers, sensor proxies, etc.
Where applicable, monitoring of a device is extended to the Where applicable, device monitoring extends to the individual
individual components of the device and/or to any attached components of the device and to any attached dependent devices.
dependent device(s). An example of such a case could be when a For example: A device can contain components that are
device contains components that are independent from a power independent from a power-state point of view, such as line
state point of view (such as line cards, processor cards, hard cards, processor cards, hard drives. A device can also have
drives) or when a devices has dependent attached devices (such dependent attached devices, such as a switch with PoE endpoints
as a switch with PoE endpoints or a power distribution unit with or a power distribution unit with attached endpoints.
attached endpoints).
2. Uses Cases & Requirements 2. Use Cases & Requirements
The requirements for power and energy monitoring for networking Requirements for power and energy monitoring for networking
devices are specified in [POWER-MON-REQ]. The requirements in devices are specified in [POWER-MON-REQ]. The requirements in
[POWER-MON-REQ] cover devices that typically make up a [POWER-MON-REQ] cover devices typically found in communications
communications network such as switches, routers, and various networks, such as switches, routers, and various connected
connected endpoints. For power monitoring to be useful, a endpoints. For a power monitoring architecture to be useful, it
specification should also be applicable to facility meters, should also apply to facility meters, power distribution units,
power distribution units, gateway proxies for commercial gateway proxies for commercial building control, home automation
building control, home automation devices and devices that devices, and devices that interface with the utility and/or
interface with the utility and/or smart grid. Due to this fact, smart grid. Accordingly, this architecture, the scope is
the scope of this architecture is broader than that specified in broader than that specified in [POWER-MON-REQ]. Several
[POWER-MON-REQ]. Several scenarios that cover these broader use scenarios that cover these broader use cases are presented later
cases are presented later in Section 9. - Implementation in Section 11. - Implementation Scenarios.
Scenarios.
3. Terminology 3. Terminology
This section contains definitions of major terms used in This section contains definitions of important terms used
explaining the concepts, examples, and the MIB definitions. throughout this specification.
IPFIX-specific terminology used in this document is defined in
section 2 of [RFC5101]. For example: Flow Record, Collector ,
etc... As in [RFC5101], these IPFIX-specific terms have the
first letter of a word capitalized.
Power Monitor Power Monitor
A Power Monitor is a system of one or more components that A Power Monitor is a component within a system of components
provide power, draws power, or reports energy consumption on that provides power, draws power, or reports energy consumption
behalf of another Power Monitor. It can be independently on behalf of another Power Monitor. It can be independently
managed from a power monitoring and power state configuration managed from a power-monitoring and power-state configuration
point of view. Examples of Power Monitors are: a router line point of view. Examples of Power Monitors are: a router line
card, a motherboard with a CPU, an IP phone connected with a card, a motherboard with a CPU, an IP phone connected with a
switch, etc. switch, etc.
Power Monitor Parent Power Monitor Parent
A Power Monitor Parent is a Power Monitor that is the root of A Power Monitor Parent is a Power Monitor that is the root of
one or multiple subtending Power Monitors, called Power Monitor one or more subtending Power Monitors, called Power Monitor
Children. The Power Monitor Parent is able to report the power Children. The Power Monitor Parent is able to collect data
state and energy consumption for his Power Monitor Child(ren). about or report on the power state and energy consumption of its
For example, in case of Power-over-Ethernet (PoE) device such as Power Monitor Children.
an IP phone or an access point attached to a switch port, the
switch is the source of power for the attached device. In such For example: A Power-over-Ethernet (PoE) device (such as an IP
a case, the Power Monitor Parent is the port of the switch, phone or an access point) is attached to a switch port. The
while the attached device is the Power Monitor Child. switch is the source of power for the attached device, so the
Power Monitor Parent is the switch, and the Power Monitor Child
is the device attached to the switch.
The Power Monitor Parent may report data or implement actions on
behalf of the Power Monitor Child. These capabilities must be
enumerated by the Power Monitor Parent.
The communication between the parent and child for monitoring or
collection of power data is left to the device manufacturer. For
example: A parent switch may use LLDP to communicate with a
connected child, and a parent lighting controller may use BACNET
to communicate with child lighting devices.
Power Monitor Child Power Monitor Child
A Power Monitor Child is a Power Monitor associated to a Power
Monitor Parent, which draws power from its Power Monitor Parent A Power Monitor Child is a Power Monitor associated with a Power
or reports its power usage and power state to its Power Monitor Monitor Parent, and which reports its power usage and power
Parent. state to its Power Monitor Parent. The Power Monitor Child may
or may not draw power from its Power Monitor Parent. .
Power Monitor Meter Domain Power Monitor Meter Domain
A Power Monitor Meter Domain is a name or name space that A Power Monitor Meter Domain is a name or name space that
logically groups together Power Monitors that comprises a zone logically groups Power Monitors into a zone of manageable power
of manageable power usage. Typically, this will comprise all usage. Typically, this zone will have as members all Power
Power Monitors that are powered from the same electrical panel Monitors that are powered from the same electrical panel or
or panels for which there is a meter or sub meter. For example, panels for which there is a meter or sub meter. For example:
all Power Monitors receiving power from the same distribution All Power Monitors receiving power from the same distribution
panel of a building, or all Power Monitors in a building for panel of a building, or all Power Monitors in a building for
which there is one main meter. From the point of monitoring which there is one main meter, would comprise a Power Monitor
power use, it is useful to report the total power usage as the Meter Doman. From the standpoint of power-use monitoring, it is
sum of power consumed by all the Power Monitors within a Power useful to report the total power usage as the sum of power
Monitor Meter Domain and then correlate that value to the consumed by all the Power Monitors within a Power Monitor Meter
metered usage. Domain and then correlate that value with the metered usage.
Power Level Power Level
A uniform way to classify power settings on a Power Monitor A Power Level is a uniform way to classify power settings on a
(e.g., shut, hibernate, sleep, high). Power Levels can be Power Monitor (e.g., shut, hibernate, sleep, high). Power
viewed as an interface for interacting with the underlying Levels can be viewed as an interface for the underlying device-
device implemented power settings. implemented power settings.
Manufacturer Power Level Manufacturer Power Level
A device specific way to classify power settings implemented on A Manufacturer Power Level is a device-specific way to classify
a Power Monitor. For cases where the implemented power setting power settings implemented on a Power Monitor. For cases where
cannot be directly mapped to a Power Level(s), the Manufacturer the implemented power settings cannot be directly mapped to
Power Levels are used to enumerate and show the relationship Power Levels, we can use the Manufacturer Power Levels to
between the implemented power settings and the Power Level enumerate and show the relationship between the implemented
interface. power settings and the Power Level interface.
4. Architecture High Level Concepts and Scope 4. Energy Management Reference Model
+---------------+
| NMS | -
+-----+---+-----+ |
| | |
| | | S
+---------+ +-------+ | N
| | | M
| | | P
+---------------+ +------+-------+ |
| Power Monitor | | Power Monitor | |
| Parent 1 | ... | Parent N | -
+---------------+ +---------------+
|||
(protocol |||
out of ||| +-------------+---------+
the scope)|||------| Power Monitor Child 1 |
|| +-----------------------+
||
|| +-------------+---------+
||-------| Power Monitor Child 2 |
| +-----------------------+
|
|
|-------- ...
|
|
| +-------------+---------+
|--------| Power Monitor Child M |
+-----------------------+
Figure 1: Energy Management Pull Reference Model
In this architecture a Network Management Station (NMS) will
poll MIB variables on a Power Monitors via SNMP. The Power
Monitor returns information for itself and for any Power Monitor
Children if applicable. The information returned will contain
business context, energy usage, power quality and other
information as described further.
The protocol between the Power Monitor Parent and Power Monitor
Children is out of scope of this document. The Power Monitor
Parent may speak to a Power Monitor Child using a manufacturer
selected protocol. This protocol may or may not based on IP.
In this way, a Power Monitor Parent acts as a PROXY for protocol
translation between the Power Monitor Parent and Child. The
Power Monitor Parent also acts as an aggregation point for other
subtended Power Monitor Children.
+---------------+
| NMS/Collector | ^ S
+-----+---+-----+ | N
| | | M I
| | | P P
+---------+ +-------+ | & F
| | | N I
| | | O X
+---------------+ +------+-------+ | T
| Power Monitor | | Power Monitor | | .
| Parent 1 | ... | Parent N | -
+---------------+ +---------------+
|||
(protocol |||
out of ||| +-------------+---------+
the scope)|||------| Power Monitor Child 1 |
|| +-----------------------+
||
|| +-------------+---------+
||-------| Power Monitor Child 2 |
| +-----------------------+
|
|
|-------- ...
|
|
| +-------------+---------+
|--------| Power Monitor Child M |
+-----------------------+
Figure 2: Energy Management PUSH Reference Model
The Power Monitor Parents may send SNMP notifications regarding
their own state or the state of their Power Monitor Children.
The Power Monitor Children do not send SNMP notifications on
their own.
As discussed in [POWER-MON-REQ], the Power Monitor Parents may
export IPFIX Flow Records [RFC5101] to a Collector. The IPFIX
protocol is well suited for regular time series export of
similar information, such as the energy consumed by the Power
Monitor Children.
EDITOR'S NOTE: at this point in time, there is no draft
specifying the IPFIX Flow Records.
5. Architecture High Level Concepts and Scope
The scope of this architecture is to enable networking and The scope of this architecture is to enable networking and
network attached devices to be managed with respect to their network-attached devices to be managed with respect to their
energy consumption or production. The goal is to make devices energy consumption or production. The goal is to make devices
energy aware. energy-aware.
The architecture describes how to make a device aware of its The architecture describes how to make a device aware of its
consumption or production of energy expressed as usage in watts. consumption or production of energy expressed as usage in watts.
This does not include: This does not include:
- Manufacturing costs in currency or environmental units - Manufacturing costs in currency or environmental units
- Embedded carbon or environmental equivalences of the device - Embedded carbon or environmental equivalences of the device
itself itself
- Cost in currency or environmental impact to dismantle or - Cost in currency or environmental impact to dismantle or
recycle the device recycle the device
- Relationship to an electrical or smart grid - Relationship to an electrical or smart grid
- Supply chain analysis - Supply chain analysis
- Conversion of the usage or production of energy to units - Conversion of the usage or production of energy to units
expressed from the source of that energy - for example the expressed from the source of that energy (such as the greenhouse
greenhouse gas emissions associated with 1000kW from a diesel gas emissions associated with 1000kW from a diesel source).
source.
This remainder of this section will go over the basic concepts The remainder of this section describes the basic concepts of
of the architecture. Each concept is then listed with notable the architecture. Each concept is examined in detail in
descriptions in subsequent sections. subsequent sections.
Examples will be provided in a later section to show how these Examples are provided in a later section to show how these
concepts can be fulfilled in an implementation. concepts can be implemented.
Given a Power Monitor, we can describe the information about the The basic concepts are:
Power Monitor through various data. A Power Monitor will have
basic naming and informational descriptors to identify it in the The Power Monitor will have basic naming and informational
network. descriptors to identify it in the network.
A Power Monitor can be part of a Power Monitor Meter Domain. A A Power Monitor can be part of a Power Monitor Meter Domain. A
Power Monitor Meter Domain is a manageable set of devices that Power Monitor Meter Domain is a manageable set of devices that
has a meter or sub-meter attached and typically corresponds to a has a meter or sub-meter attached and typically corresponds to a
power distribution point or panel. power distribution point or panel.
A Power Monitor can be a parent (Power Monitor Parent) or child A Power Monitor can be a parent (Power Monitor Parent) or child
(Power Monitor Child) of another Power Monitor. This allows for (Power Monitor Child) of another Power Monitor. This allows for
devices to aggregate reporting and/or control of power Power Monitor Parent to aggregate power reporting and control of
information. power information.
Each Power Monitor can have information to allow it to be Each Power Monitor can have information to allow it to be
described in the context of the business or ultimate use. This described in the context of the business or ultimate use. This
is in addition to its networked information. This allows for is in addition to its networked information. This allows for
tagging, grouping and differentiation between Power Monitors for tagging, grouping, and differentiation between Power Monitors
NMS. for NMS.
For control and universal monitoring each Power Monitor will For control and universal monitoring, each Power Monitor
implement or declare a set of known Power Levels. The Power implements or declares a set of known Power Levels. The Power
Levels can be mapped to Manufacturer Power Levels that indicate Levels are mapped to Manufacturer Power Levels that indicate the
the specific power setting for the device implementing the Power specific power settings for the device implementing the Power
Monitor, in case that Power Monitor doesn't implement yet the Monitor.
standard Power Levels [POWER-MON-MIB].
The desired Power Level variable is set, when setting the Power When the Power Level is set, a Power Monitor may be busy at the
Level. If the Power Monitor is busy at the request time, it request time. The Power Monitor will set the desired level and
might update the actual Power Level when his priority task is then update the actual Power Level when the priority task is
finished. This mechanism implies two different Power Level finished. This mechanism implies two different Power Level
variables: actual versus desired. variables: actual versus desired.
EDITOR'S NOTE: the transition state will have to be specified. EDITOR'S NOTE: The transition state will have to be specified.
Each Power Monitor will have usage information that describes Each Power Monitor will have usage information that describes
the power information along with how that usage was obtained or the power information along with how that usage was obtained or
derived. derived.
Optionally a Power Monitor can further describe the power Optionally, a Power Monitor can further describe the power
information with power quality information reflecting the information with power quality information reflecting the
electrical characteristics of the measurement. electrical characteristics of the measurement.
Optionally a Power Monitor can provide power usage over time to Optionally, a Power Monitor can provide power usage over time to
describe energy consumption describe energy consumption
If a Power Monitor has one or more batteries, it can provide If a Power Monitor has one or more batteries, it can provide
optional Battery information as well. optional battery information as well.
4.1. Power Monitor Information 5.1. Power Monitor Information
Every Power Monitor SHOULD have a unique printable name, and Every Power Monitor should have a unique printable name, and
MUST have a unique Power Monitor index. must have a unique Power Monitor index.
Possible naming conventions are: textual DNS name, MAC-address Possible naming conventions are: textual DNS name, MAC-address
of the device, interface ifName, or a text string uniquely of the device, interface ifName, or a text string uniquely
identifying the Power Monitor. As an example, in the case of IP identifying the Power Monitor. As an example, in the case of IP
phones, the Power Monitor name can be the device DNS name. phones, the Power Monitor name can be the device DNS name.
4.2. Power Monitor Meter Domain 5.2. Power Monitor Meter Domain
Each Power Monitor MUST be a member of a Power Monitor Meter Each Power Monitor must be a member of a Power Monitor Meter
Domain. The Power Monitor Meter Domain SHOULD map 1-1 with a Domain. The Power Monitor Meter Domain should map 1-1 with a
metered or sub-metered portion of the site. The Power Monitor metered or sub-metered portion of the site. The Power Monitor
Meter Domain MUST be configured on the Power Monitor Parent. Meter Domain must be configured on the Power Monitor Parent.
The Power Monitor Children MAY inherit its domain value from the The Power Monitor Children may inherit their domain values from
Power Monitor Parent or the Power Monitor Meter Domain MAY be the Power Monitor Parent or the Power Monitor Meter Domain may
configured directly in Power Monitor Child. be configured directly in a Power Monitor Child.
4.3. Power Monitor Parent and Child 5.3. Power Monitor Parent and Child
A Power Monitor can be connected to another Power Monitor and A Power Monitor Child reports its power usage to its Power
either draw power from that entity or report power usage to that Monitor Parent. A Power Monitor Child has one and only one
entity. Power Monitor Parent. If a Power Monitor had two parents there
would be a risk of double-reporting the power usage in the Power
Monitor Meter Domain. Therefore, a Power Monitor cannot be both
a Power Monitor Parent and a Power Monitor Child at the same
time.
A Power Monitor Child can be fully dependent on the Power A Power Monitor Child can be fully dependent on the Power
Monitor Parent (as in the case of Power Over Ethernet) or Monitor Parent for its power or independent from the parent
independent from the parent (such as a PC connected to a (such as a PC connected to a switch). In the dependently
switch). In the dependent case, the Power Monitor Parent powered case, the Power Monitor Parent provides power for the
provides power for the Power Monitor Child (the PoE case). In Power Monitor Child (as in the case of Power Over Ethernet
the independent case, the Power Monitor Child draws power from devices). In the independently powered case, the Power Monitor
another source (typically a wall outlet). Since the Power Child draws power from another source (typically a wall outlet).
Monitor Parent is not the source of power supply, the power Since the Power Monitor Parent is not the source of power
usage cannot be measured at the Power Monitor Parent. However, supply, the power usage cannot be measured at the Power Monitor
an independent Power Monitor Child may report Power Monitor Parent. However, an independent Power Monitor Child reports
information to the Power Monitor Parent. The Power Monitor Power Monitor information to the Power Monitor Parent. The
Child may listen to the power control settings from a Power Power Monitor Child may listen to the power control settings
Monitor Parent and could react to the control messages. Note from a Power Monitor Parent and could react to the control
that the communication between the Power Monitor Parent and messages. However, note that the communication between the
Power Monitor Child is out of scope of this document. Power Monitor Parent and Power Monitor Child is out of scope for
this document.
A Power Monitor cannot be at the same time a Power Monitor
Parent and a Power Monitor Child. Indeed such configuration
would lead to double counting the energy consumed within a
specific Power Monitor Domain.
A mechanism, outside of the scope of this document, should be in A mechanism, outside of the scope of this document, should be in
place to verify the connectivity between the Power Monitor place to verify the connectivity between the Power Monitor
Parent and its Power Monitor Children. If the Power Monitor Parent and its Power Monitor Children. If a Power Monitor Child
Child is unavailable, the Power Monitor Parent must follow some is unavailable, the Power Monitor Parent must follow some rules
rules to determine how long it should wait before removing the to determine how long it should wait before removing the Power
Power Monitor Child entry, along with all associated statistics, Monitor Child entry, along with all associated statistics, from
from his database. In some situations, such as connected its database. In some situations, such as a connected building
building, in which the Power Monitor Children are pretty static, in which the Power Monitor Children are somewhat static, this
this removal timer might be pretty long. The persistence across removal-delay period may be long, and persistence across a Power
a Power Monitor Parent reload could even make sense. However, Monitor Parent reload may make sense. However, in a networking
in a networking environment, where endpoints could come and go, environment, where endpoints can come and go, there is not much
there is not much sense to configure a long removal timer. In sense in configuring a long removal timer. In all cases, the
all cases, the removal timer or persistence must be clearly removal timer or persistence must be clearly specified.
specified.
Further examples of Power Monitor Parent and Child Further examples of Power Monitor Parent and Child
implementations are provided in the Implementation Scenarios implementations are provided in the Implementation Scenarios
section. section 11.
4.4. Power Monitor Context 5.4. Power Monitor Context
Monitored power will ultimately be collected to and reported Monitored power data will ultimately be collected by and
from a NMS. In order to aid in the reporting and reported from an NMS. In order to aid in reporting and in
differentiation between Power Monitors, each Power Monitor will differentiation between Power Monitors, each Power Monitor will
contain information to establish a business or site context. contain information establishing its business or site context.
A Power Monitor can provide an importance value in the range of A Power Monitor can provide an importance value in the range of
1..100 to help differentiate the use or relative value to the 1 to 100 to help differentiate a device's use or relative value
site. The importance range is from 1 (least important) to 100 to the site. The importance range is from 1 (least important)
(most important). The default importance value is 1. to 100 (most important). The default importance value is 1.
For example, a typical office environment has several types of For example: A typical office environment has several types of
phones, which can be rated according to the business impact: a phones, which can be rated according to their business impact.
public desk phone has a lower importance (for example, 10) than A public desk phone has a lower importance (for example, 10)
a business-critical emergency phone (for example, 100). As than a business-critical emergency phone (for example, 100). As
another example, a company can consider that a PC and a phone another example: A company can consider that a PC and a phone
for a customer-service engineer is more important than a PC and for a customer-service engineer is more important than a PC and
a phone for lobby use. a phone for lobby use.
Although network managers must establish their own ranking the
Although network managers must establish their own ranking, the
following is a broad recommendation: following is a broad recommendation:
. 90 to 100 Emergency response . 90 to 100 Emergency response
. 80 to 90 Executive or business critical . 80 to 90 Executive or business-critical
. 70 to 79 General or Average . 70 to 79 General or Average
. 60 to 69 Staff or support . 60 to 69 Staff or support
. 40 to 59 Public or guest . 40 to 59 Public or guest
. 1 to 39 Decorative or hospitality . 1 to 39 Decorative or hospitality
A Power Monitor can provide a set of keywords. These keywords A Power Monitor can provide a set of keywords. These keywords
are a list of tags that can be used for grouping and summary are a list of tags that can be used for grouping and summary
reporting within or between Power Monitor Meter Domains. All reporting within or between Power Monitor Meter Domains. All
alphanumeric characters and symbols such as #, (, $, !, and & alphanumeric characters and symbols, such as #, (, $, !, and &,
are allowed. Potential examples are: IT, lobby, HumanResources, are allowed. Potential examples are: IT, lobby, HumanResources,
Accounting, StoreRoom, CustomerSpace, router, phone, floor2, or Accounting, StoreRoom, CustomerSpace, router, phone, floor2, or
SoftwareLab. There is no default value for the keyword. SoftwareLab. There is no default value for a keyword.
Multiple keywords can be assigned to a device. In such cases, Multiple keywords can be assigned to a device. In such cases,
the keywords are separated by commas and no spaces between the keywords are separated by commas and no spaces between
keywords are allowed. For example, "HR,Bldg1,Private". keywords are allowed. For example, "HR,Bldg1,Private".
Additionally, a Power Monitor can provide a "role description" Additionally, a Power Monitor can provide a "role description"
string that indicates the purpose the Power Monitor serves in string that indicates the purpose the Power Monitor serves in
the network or to site/business. This could be a string the network or for the site/business. This could be a string
describing the context the device fulfils in deployment. For describing the context the device fulfills in deployment. For
example, a lighting fixture in a kitchen area could have a role example, a lighting fixture in a kitchen area could have a role
of "Hospitality Lighting" to provide context for the use of the of "Hospitality Lighting" to provide context for the use of the
device. device.
4.5. Power Monitor Levels 5.5. Power Monitor Levels
Power Levels represent universal states of power management of a Power Levels represent universal states of power management of a
Power Monitor. Each Power Level corresponds to a global, Power Monitor. Each Power Level corresponds to a global,
system, and performance state in the ACPI model. system, and performance state in the ACPI model [ACPI].
Level ACPI Global/System Name Level ACPI Global/System Power Level
State State Name
Non-operational states: Non-operational states:
1 G3, S5 Mech Off 1 G3, S5 Mech Off
2 G2, S5 Soft Off 2 G2, S5 Soft Off
3 G1, S4 Hibernate 3 G1, S4 Hibernate
4 G1, S3 Sleep 4 G1, S3 Sleep
5 G1, S2 Standby 5 G1, S2 Standby
6 G1, S1 Ready 6 G1, S1 Ready
Operational states: Operational states:
7 G0, S0, P5 LowMinus 7 G0, S0, P5 LowMinus
8 G0, S0, P4 Low 8 G0, S0, P4 Low
9 G0, S0, P3 MediumMinus 9 G0, S0, P3 MediumMinus
10 G0, S0, P2 Medium 10 G0, S0, P2 Medium
11 G0, S0, P1 HighMinus 11 G0, S0, P1 HighMinus
12 G0, S0, P0 High 12 G0, S0, P0 High
Figure 3: ACPI / Power Level Mapping
For example, a Power Monitor with a Power Level of 9 would For example, a Power Monitor with a Power Level of 9 would
indicate an operational state with MediumMinus Power Level. indicate an operational state with MediumMinus Power Level.
The Power Levels can be considered as guidelines for an The Power Levels can be considered as guidelines in order to
interface in order to promote interoperability across device promote interoperability across device types. Realistically,
types. Realistically, it is foreseen that each specific feature each specific feature requiring Power Levels will require a
requiring Power Levels will require a complete recommendation of complete recommendation of its own. For example, designing IP
its own. For example, designing IP phones with consistent Power phones with consistent Power Levels across vendors requires a
Levels across vendors requires a specification for IP phone specification for IP phone design, along with the Power Levels
design, along with the Power Levels mapping. mapping.
Manufacturer Power Levels are required in some situations, such
as when no mappings with the existing Power Levels are possible,
or when more than the twelve specified Power Levels are
required.
In some situation, Manufacturer Power Levels are required, for
example, when no mappings with the existing Power Levels are
possible or when more levels than the twelve specified Power
Levels are required.
A first example would be an imaginary device type, with only A first example would be an imaginary device type, with only
five levels: "none", "short", "tall", "grande", and "venti". five levels: "none", "short", "tall", "grande", and "venti".
Manufacturer Power Level Respective Name Manufacturer Power Level Respective Name
0 none 0 none
1 short 1 short
2 tall 2 tall
3 grande 3 grande
4 venti 4 venti
In the unlikely event of no possible mapping between these Figure 4: Mapping Example 1
Manufacturer Power Levels and the Power Levels, the Power Level
will remain 0 throughout the MIB module, as displayed below. In the unlikely event that there is no possible mapping between
these Manufacturer Power Levels and the proposed Power Monitor
Power Levels, the Power Level will remain 0 throughout the MIB
module, as displayed below.
Power Level / Name Manufacturer Power Level / Name Power Level / Name Manufacturer Power Level / Name
0 / unknown 0 / none 0 / unknown 0 / none
0 / unknown 1 / short 0 / unknown 1 / short
0 / unknown 2 / tall 0 / unknown 2 / tall
0 / unknown 3 / grande 0 / unknown 3 / grande
0 / unknown 4 / venti 0 / unknown 4 / venti
Figure 5: Mapping Example 2
If a mapping between the Manufacturer Power Levels and the Power If a mapping between the Manufacturer Power Levels and the Power
Levels is achievable, both series of levels exist in the MIB Monitor Power Levels is achievable, both series of levels must
module, allowing the NMS to understand the mapping between them exist in the MIB module in the Power Monitor Parent, allowing
by correlating the Power Level with the Manufacturer Power the NMS to understand the mapping between them by correlating
Levels. the Power Level with the Manufacturer Power Levels.
Power Level / Name Manufacturer Power Level / Name Power Level / Name Manufacturer Power Level / Name
1 / Mech Off 0 / none 1 / Mech Off 0 / none
2 / Soft Off 0 / none 2 / Soft Off 0 / none
3 / Hibernate 0 / none 3 / Hibernate 0 / none
4 / Sleep, Save-to-RAM 0 / none 4 / Sleep, Save-to-RAM 0 / none
5 / Standby 0 / none 5 / Standby 0 / none
6 / Ready 1 / short 6 / Ready 1 / short
7 / LowMinus 1 / short 7 / LowMinus 1 / short
8 / Low 1 / short 8 / Low 1 / short
9 / MediumMinus 2 / tall 9 / MediumMinus 2 / tall
10 / Medium 2 / tall 10 / Medium 2 / tall
11 / HighMinus 3 / grande 11 / HighMinus 3 / grande
12 / High 4 / venti 12 / High 4 / venti
How the Power Monitor Levels are then mapped, i.e. assigning the Figure 6: Mapping Example 3
directly lower or directly higher level, is an implementation
choice. However, its recommended that the Manufacturer Power How the Power Monitor Levels are then mapped is an
Levels l maps to the directly lower Power Level, so that setting implementation choice. However, it is recommended that the
all Power Meters to a Power Level would be conservative in terms Manufacturer Power Levels map to the lowest applicable Power
of disabled functionality on the Power Monitor implementing the Levels, so that setting all Power Monitors to a Power Level
Manufacturer Power Levels. would be conservative in terms of disabled functionality on the
Power Monitor.
A second example would be a device type, such as a dimmer or a A second example would be a device type, such as a dimmer or a
motor, with a high number of operational levels. For the sake motor, with a high number of operational levels. For the sake
of the example, 100 operational states are assumed. of the example, 100 operational states are assumed.
Power Level / Name Manufacturer Power Level / Name Power Level / Name Manufacturer Power Level / Name
1 / Mech Off 0 / off 1 / Mech Off 0 / off
2 / Soft Off 0 / off 2 / Soft Off 0 / off
3 / Hibernate 0 / off 3 / Hibernate 0 / off
4 / Sleep, Save-to-RAM 0 / off 4 / Sleep, Save-to-RAM 0 / off
5 / Standby 0 / off 5 / Standby 1 / off
6 / Ready 0 / off 6 / Ready 2 / off
7 / LowMinus 1 / 1% 7 / LowMinus 11 / 1%
7 / LowMinus 2 / 2% 7 / LowMinus 12 / 2%
7 / LowMinus 3 / 3% 7 / LowMinus 13 / 3%
. . . .
. . . .
. . . .
8 / Low 15 / 15% 8 / Low 15 / 15%
8 / Low 16 / 16% 8 / Low 16 / 16%
8 / Low 17 / 17% 8 / Low 17 / 17%
. . . .
. . . .
. . . .
9 / MediumMinus 30 / 30% 9 / MediumMinus 30 / 30%
skipping to change at page 13, line 38 skipping to change at page 16, line 38
. . . .
. . . .
10 / Medium 45 / 45% 10 / Medium 45 / 45%
10 / Medium 46 / 46% 10 / Medium 46 / 46%
10 / Medium 47 / 47% 10 / Medium 47 / 47%
. . . .
. . . .
. . . .
etc... etc...
4.6. Power Monitor Usage Measurement Figure 7: Mapping Example 4
As specified in section 6, this architecture allows the
configuration of the Power Level, while configuring the
Manufacturer Power Level from the MIB directly is not possible.
5.6. Power Monitor Usage Measurement
The usage or production or power must be qualified as more than
a value alone. A measurement should be qualified with the
units, magnitude, direction of power flow, and by what means the
measurement was made (ex: Root Mean Square versus Nameplate) .
In addition, the Power Monitor should describe how it intends to
measure usage as one of consumer, producer or meter of usage.
Given the intent any readings can be correctly summarized or
analyzed by an NMS. For example metered usage reported by a
meter and consumption usage reported by a device connected to
that meter may naturally measure the same usage. With the two
measurements identified by intent a proper summarization can be
made by an NMS.
For a Power Monitor, RMS (Root Mean Square) or RMS equivalent
(for example, after conversion to DC power) power usage must be
reported, including the magnitude of measurement, as multiple
scaling factors can be used.
The power usage measurement should conform to the IEC 61850 The power usage measurement should conform to the IEC 61850
definition of unit multiplier for the SI (System International) definition of unit multiplier for the SI (System International)
units of measure. The power usage measurement is considered an units of measure. The power usage measurement is considered an
instantaneous usage value and does not include the usage over instantaneous usage value and does not include the usage over
time. time.
Measured values are represented in SI units obtained by Measured values are represented in SI units obtained by
BaseValue * 10 raised to the power of scale. For example, if BaseValue * 10 raised to the power of the scale. For example,
current power usage of a Power Monitor is 3, it could be 3 W, 3 if current power usage of a Power Monitor is 3, it could be 3 W,
mW, 3 KW, 3 MW depending on the value of scaling factor (called 3 mW, 3 KW, or 3 MW, depending on the value of the scaling
pmPowerUnitMultiplier in the MIB module). factor
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 Power Monitor usage measurement was obtained: know how a Power Monitor usage measurement was obtained:
. whether the measurements were made at the device itself or . Whether the measurements were made at the device itself or
from a remote source from a remote source.
. Description of the method that was used to measure the . Description of the method that was used to measure the
power and can distinguish actual or estimated values. power and whether this method can distinguish actual or
estimated values.
An NMS can use this information to account for the accuracy and An NMS can use this information to account for the accuracy and
nature of the reading between different implementations. nature of the reading between different implementations.
In addition to the power usage the nameplate power rating of a In addition to the power usage, the nameplate power rating of a
Power Monitor is typically specified by the vendor as the Power Monitor is typically specified by the vendor as the
capacity required to power the device. Often this label is a capacity required to power the device. Often this label is a
conservative number and is the worst-case power draw. While the conservative number and is the worst-case power draw. While the
actual utilization of an entity can be lower, the nameplate actual utilization of an entity can be lower, the nameplate
power is important for provisioning, capacity planning and power is important for provisioning, capacity planning and
billing. billing.
4.7. Optional Power Usage Quality 5.7. Optional Power Usage Quality
Given a power measurement of a Power Monitor, it may in certain Given a power measurement of a Power Monitor, it may in certain
circumstances be desirable to know the power quality associated circumstances be desirable to know the power quality associated
with that measurement. The information model must adhere to the with that measurement. The information model must adhere to the
IEC 61850 7-2 standard to describe AC measurements. In some IEC 61850 7-2 standard for describing AC measurements. In some
Power Monitor Domains, the power quality may not be needed, Power Monitor Domains, the power quality may not be needed,
available, nor relevant to the Power Monitor. available, or relevant to the Power Monitor.
4.8. Optional Energy Measurement 5.8. Optional Energy Measurement
In addition to reporting the Power Level, an approach to In addition to reporting the Power Level, an approach to
characterize the energy demand is required. It is well known in characterizing the energy demand is required. It is well known
commercial electrical utility rates, that demand charges can be in commercial electrical utility rates that demand charges can
on par with actual power charges. So, it is useful to be on par with actual power charges, so it is useful to
characterize the demand. The demand can be described as the characterize the demand. The demand can be described as the
average energy of an Power Monitor over a time window, called a average energy of an Power Monitor over a time window called a
demand interval, typically 15 minutes. The highest peak energy demand interval (typically 15 minutes). The highest peak energy
demand measured over a time horizon, say 1 month or 1 year is demand measured over a time horizon, such as 1 month or 1 year,
often the basis for usage charges. A single window of time of is often the basis for usage charges. A single window of time
high usage can penalize the energy consumption charges. of high usage can penalize the consumer with higher energy
However, it is relevant to measure the demand only when there consumption charges. However, it is relevant to measure the
are actual power measurements from a Power Monitor, and not when demand only when there are actual power measurements from a
the power measurement is assumed or predicted. Power Monitor, and not when the power measurement is assumed or
predicted.
Several efficiency metrics can be derived and tracked with the Several efficiency metrics can be derived and tracked with the
demand usage data. demand usage data. For example:
. For example, per-packet power costs for a networking device . Per-packet power costs for a networking device (router or
(router or switch) can be calculated by an network switch) can be calculated by an NMS. The packet count can
management system. The packets count can be determined be determined from the traffic usage in the ifTable
from the traffic usage in the ifTable [RFC2863] from the [RFC2863], from the forwarding plane figure, or from the
forwarding plane figure, or from the platform platform specifications.
specifications.
. Watt-hour power can be combined with utility energy sources . Watt-hour power can be combined with utility energy sources
to estimate carbon footprint and other emission statistics. to estimate carbon footprint and other emission statistics.
4.9. Optional Battery Information 5.9. Optional Battery Information
Some Power Monitors might be running on batteries. Therefore Some Power Monitors may be running on batteries. Therefore
information such as the battery status (charging or information such as the battery status (charging or
discharging), remaining capacity, etc... must be available. discharging), remaining capacity, and so on, must be available.
5. Power Monitor Children Discovery 6. Power Monitor Children Discovery
There are multiple ways that the Power Monitor Parent can There are multiple ways that the Power Monitor Parent can
discover its Power Monitor Children, if not present on the same discover its Power Monitor Children, if they are not present on
physical network element. the same physical network element:
. In case of PoE, the Power Monitor Parent automatically . In case of PoE, the Power Monitor Parent automatically
discovers that a Power Monitor Child requests some power. discovers a Power Monitor Child when the Child requests
power.
. The Power Monitor Parent and Children may run the Link . The Power Monitor Parent and Children may run the Link
Layer Discovery Protocol [LLDP], or any proprietary similar Layer Discovery Protocol [LLDP], or any other discovery
protocols such as Cisco Discovery Protocol (CDP). The protocol, such as Cisco Discovery Protocol (CDP). The
Power Monitor Parent might even support the LLDP-MED MIB Power Monitor Parent might even support the LLDP-MED MIB
[LLDP-MED-MIB], which returns some extra information on the [LLDP-MED-MIB], which returns extra information on the
Power Monitor Children. Power Monitor Children.
. The Power Monitor Parent might reside on a network . The Power Monitor Parent may reside on a network connected
connected facilities gateway. A typical example is a facilities gateway. A typical example is a converged
converged building gateway, monitoring several other building gateway, monitoring several other devices in the
devices in the building, doing the proxy between SNMP and a building, and serving as a proxy between SNMP and a
protocol such as BACNET. protocol such as BACNET.
When a Power Monitor Child doesn't support the Power Levels, but When a Power Monitor Child supports only its own Manufacturer
its own Manufacturer Power Levels, the Power Monitor Parent will Power Levels, the Power Monitor Parent will have to discover
have to discover those Manufacturer Power Levels. Note that the those Manufacturer Power Levels. Note that the communication
communication specifications between the Power Monitor Parent specifications between the Power Monitor Parent and Children is
and Children is out of the scope of this document. This out of the scope of this document. This includes the
includes the Manufacturer Power Levels discovery, which is Manufacturer Power Levels discovery, which is protocol-specific.
protocol-specific.
6. Configuration 7. Configuration
This power management architecture allows the configuration of a This power management architecture allows the configuration of
couple of key parameters: the following key parameters:
. Power Monitor name: an unique printable name for the Power . Power Monitor name: A unique printable name for the Power
Monitor. Monitor.
. Power Monitor Role: an administratively assigned name to . Power Monitor Role: An administratively assigned name to
indicate the purpose a Power Monitor serves in the network. indicate the purpose a Power Monitor serves in the network.
. Power Monitor Importance: a ranking of how important the . Power Monitor Importance: A ranking of how important the
Power Monitor is on a scale of 1 to 100 compared to other Power Monitor is, on a scale of 1 to 100, compared with
Power Monitors in the same Power Monitor Meter Domain. other Power Monitors in the same Power Monitor Meter
. Power Monitor Keywords: a list of keywords that can be used Domain.
. Power Monitor Keywords: A list of keywords that can be used
to group Power Monitors for reporting or searching. to group Power Monitors for reporting or searching.
. Power Monitor Domain: specifies the name of a Power Monitor . Power Monitor Domain: Specifies the name of a Power Monitor
Meter Domain for the Power Monitor. Meter Domain for the Power Monitor.
. The Power Monitor Level: specifies the current Power Level . The Power Monitor Level: Specifies the current Power Level
(0..12) for the Power Monitor. (0..12) for the Power Monitor.
. Manufacturer Power Level and name . The energy demand parameters: For example, which interval
. The energy demand parameters: for example, which interval length to report the energy on, the number of intervals to
length to report the energy on, the number of interval to keep, etc.
keep, etc...
Interactions with established open protocols such as Wake-up-on- When a Power Monitor requires a mapping with the Manufacturer
Lan (WoL) and DASH [DASH] may require configuration in the Power Power Level, the Power Monitor configuration is done via the
Monitor as well, facilitating the communication between Power Power Level settings, and not directly via the Manufacturer
Monitor Parent and remote Power Monitor Children. Power Levels, which are read-only. Taking into account Figure
8, where the LowMinus Power Level corresponds to three different
Manufacturer Power Levels (11 for 1%, 12 for 2%, and 13 for 3%),
the implication is that this architecture will not set the
Manufacturer Power Level to one percent granularity without
communicating over or configuring the proprietary protocol for
this Power Monitor.
This architecture uses a Power Level MIB object to set up the
Power Level for a specific Power Monitor. However, the Power
Monitor might be busy executing an important task that requires
the current Power Level for some more time. For example, a PC
might have to finish a backup first, or an IP phone might be
busy with a current phone call. Therefore a second MIB object
contains the actual Power Level. A difference in values between
the two objects indicates that the Power Monitor is currently in
Power Level transition.
Interactions with established open protocols, such as Wake-up-
on-Lan (WoL) and DASH [DASH], may require configuration in the
Power Monitor as well, facilitating the communication between
Power Monitor Parent and remote Power Monitor Children.
Note that the communication specifications between the Power Note that the communication specifications between the Power
Monitor Parent and Children is out of the scope of this Monitor Parent and Children is out of the scope of this
document. This includes the communication of the power settings document. This includes communication of power settings and
and configuration information such as the Power Monitor Domain. configuration information, such as the Power Monitor Domain.
7. Fault Management 8. Fault Management
[POWER-MON-REQ] specifies some requirements about power states [POWER-MON-REQ] specifies some requirements about power states
such as "the current state - the time of the last change", "the such as "the current state - the time of the last 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... Such requirements are fulfilled via the each state", etc. Such requirements are fulfilled via the
pmPowerLevelChange NOTIFICATION-TYPE [POWER-MON-MIB]. This SNMP pmPowerLevelChange NOTIFICATION-TYPE [POWER-MON-MIB]. This SNMP
notification is generated when the value(s) of Power Level has notification is generated when the value(s) of Power Level has
changed for the Power Monitor. changed for the Power Monitor.
A push based mechanism such as IPFIX might be required to export 9. IPFIX
high volume time series of energy consumption values, as
mentioned in [POWER-MON-REQ].
8. Relationship with Other Standard Development Organizations A push-based mechanism, such as IPFIX [RFC5101], might be
required to export high-volume time series of energy consumption
values, as mentioned in [POWER-MON-REQ].
8.1. Information Modeling EDITOR'S NOTE: the Working Group should decide how much of IPFIX
should be described in this document
This power management architecture should reuse as much as 10. Relationship with Other Standards Development Organizations
possible existing standard efforts and not re-invent something
new, specifically in terms of information modeling and data
modeling [RFC3444].
The data model for power, energy related objects is based on the 10.1. Information Modeling
IEC 61850.
This power management architecture should, as much as possible,
reuse existing standards efforts, especially with respect to
information modeling and data modeling [RFC3444].
The data model for power, energy related objects is based on IEC
61850.
Specific examples include: Specific examples include:
. The scaling factor, which represent the magnitude of Power . The scaling factor, which represents Power Monitor usage
Monitor usage, conforms to the IEC 61850 definition of unit magnitude, conforms to the IEC 61850 definition of unit
multiplier for the SI (System International) units of multiplier for the SI (System International) units of
measure. measure.
. The power accuracy model is based on the ANSI and IEC . The power accuracy model is based on the ANSI and IEC
Standards, which require that we use an accuracy class for Standards, which require that we use an accuracy class for
power measurement. ANSI and IEC define the following power measurement. ANSI and IEC define the following
accuracy classes for power measurement: accuracy classes for power measurement:
. IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. . IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3.
. ANSI C12.20 class 0.2, 0.5 . ANSI C12.20 class 0.2, 0.5
. The powerQualityMIB MIB module adheres closely to the IEC . The powerQualityMIB MIB module adheres closely to the IEC
61850 7-2 standard to describe AC measurements. 61850 7-2 standard for describing AC measurements.
8.2. Power Levels 10.2. Power Levels
There are twelve Power Monitor Levels; divided into six There are twelve Power Monitor Levels. They are subdivided into
operational states, and six non-operational states. The lowest six operational states, and six non-operational states. The
non-operational state is 1 and the highest is six. Each non- lowest non-operational state is 1 and the highest is six. Each
operational state corresponds to an ACPI level [ACPI]. non-operational state corresponds to an ACPI level [ACPI].
9. Implementation Scenarios 11. Implementation Scenarios
The scope of power and energy monitoring consists of devices The scope of power and energy monitoring consists of devices
that consume power within and connected to a communications that consume power within and that are connected to a
network. These devices include: communications network. These devices include:
- Network devices and sub-components: devices such as routers - Network devices and sub-components: Devices such as routers
and switches and their sub-components. and switches and their sub-components.
- Network attached endpoints: devices that use the - Network attached endpoints: Devices that use the
communications network such as endpoints, PCs, or facility communications network, such as endpoints, PCs, and facility
gateways that proxy energy monitor and control for commercial gateways that proxy energy monitor and control for commercial
buildings or home automation, buildings or home automation.
- Network attached meters or supplies: devices that can monitor - Network attached meters or supplies: Devices that can monitor
the electrical supply such as smart meters or Universal Power the electrical supply, such as smart meters or Universal
Supplies (UPS) that meter and provide availability. Power Supplies (UPS) that meter and provide availability.
-
This section provides illustrative examples that model different This section provides illustrative examples that model different
scenarios for implementation of the Power Monitor including scenarios for implementation of the Power Monitor, including
Power Monitor Parent and Power Monitor Child relationships. Power Monitor Parent and Power Monitor Child relationships.
Each of the scenarios below is explained in more details in the Each of the scenarios below is explained in more detail in the
Power Monitor MIB document [POWER-MON-MIB], with a mapping to Power Monitor MIB document [POWER-MON-MIB], with a mapping to
the MIB Objects. the MIB Objects.
Scenario 1: Switch with PoE endpoints Scenario 1: Switch with PoE endpoints
Consider a PoE IP phone connected to a switch, as displayed on Consider a PoE IP phone connected to a switch. The IP phone
figure 1. The IP phone draws power from the PoE switch. draws power from the PoE switch.
Scenario 2: Switch with PoE endpoints with further connected Scenario 2: Switch with PoE endpoints with further connected
device(s) device(s)
Consider the same scenario as example 1 with an IP phone Consider the same example as in Scenario 1, but with a PC daisy-
connected to PoE port of a switch. Now, in addition, a PC is chained from the IP phone for LAN connectivity. The phone draws
also daisy-chained from the IP phone for LAN connectivity. The power from the PoE port of the switch, while the PC draws power
phone draws power from PoE port of the switch, while the PC from the wall outlet.
draws power from the wall outlet.
Scenario 3: A switch with Wireless Access Points Scenario 3: A switch with Wireless Access Points
Consider a Wireless Access Point connected to the PoE port of a Consider a WAP (Wireless Access Point) connected to the PoE port
switch. There are several PCs connected to the Wireless Access of a switch. There are several PCs connected to the Wireless
Point over Wireless protocols. All PCs draw power from the wall Access Point over Wireless protocols. All PCs draw power from
outlets. the wall outlets.
The switch port is the Power Monitor Parent for the Wireless The switch port is the Power Monitor Parent for the Wireless
Access Point (WAP) and the PCs. There is a distinction, between Access Point (WAP) and all the PCs. But there is a distinction
the Power Monitor Children, as the WAP draws power from the PoE among the Power Monitor Children, as the WAP draws power from
port of the switch and the PCs draw power from the wall outlet. the PoE port of the switch and the PCs draw power from the wall
outlet.
Scenario 4: Network connected facilities gateway Scenario 4: Network connected facilities gateway
At the top of the network hierarchy of a building network is a At the top of the network hierarchy of a building network is a
gateway device that can perform protocol conversion between many gateway device that can perform protocol conversion between many
facility management devices, such as BACNET, MODBUS, DALI, LON, facility management devices, such as BACNET, MODBUS, DALI, LON,
etc. There are power meters associated with power consuming etc. There are power meters associated with power-consuming
entities (Heating Ventilation & Air Conditioning - HVAC, entities (Heating Ventilation & Air Conditioning - HVAC,
lighting, electrical, fire control, elevators, etc). The lighting, electrical, fire control, elevators, etc). The
proposed MIB can be implemented on the gateway device. The proposed MIB can be implemented on the gateway device. The
gateway can be considered as the Power Monitor Parent, while the gateway can be considered as the Power Monitor Parent, while the
power meters associated with the energy consuming entities such power meters associated with the energy consuming entities can
can be considered as Power Monitor Children. be considered as its Power Monitor Children.
Scenario 5: Data Center Network Scenario 5: Data center network
A typical data center network consists of a hierarchy of A typical data center network consists of a hierarchy of
switches. At the bottom of hierarchy there are servers mounted switches. At the bottom of the hierarchy there are servers
on a rack, and those are connected to the top of the rack mounted on a rack, and these are connected to the top-of-the-
switches. The top switches are connected to aggregation rack switches. The top switches are connected to aggregation
switches that are in turn connected to core switches. As an switches that are in turn connected to core switches. As an
example, Server 1 and Server 2 are connected to different switch example, Server 1 and Server 2 are connected to different switch
ports of the top switch. ports of the top switch.
The proposed MIB can be implemented on the switches. The switch The proposed MIB can be implemented on the switches. The switch
can be considered as the Power Monitor Parent. The servers can can be considered as the Power Monitor Parent. The servers can
be considered as the Power Monitor Children. be considered as the Power Monitor Children.
Scenario 6: Building Gateway Device Scenario 6: Building gateway device
Similar scenario as the scenario 4. Similar scenario as the scenario 4.
Scenario 7: Power Consumption of UPS Scenario 7: Power consumption of UPS
Data centers and commercial buildings can have Uninterruptible Data centers and commercial buildings can have Uninterruptible
Power Supplies (UPS) connected to the network. The Power Monitor Power Supplies (UPS) connected to the network. The Power Monitor
can be used to model a UPS as a Power Monitor Parent with the can be used to model a UPS as a Power Monitor Parent with the
connected devices as Power Monitor Children. connected devices as Power Monitor Children.
Scenario 8: Power Consumption of Battery-based Devices Scenario 8: Power consumption of battery-based devices
A PC is typical example of a battery-based device. A PC is a typical example of a battery-based device.
10. Security Considerations 12. Security Considerations
TO DO Regarding the data attributes specified here, some or all may be
considered sensitive or vulnerable in some network environments.
Reading or writing these attributes without proper protection
such as encryption or access authorization may have negative
effects on the network capabilities.
11. IANA Considerations 12.1. Security Considerations for SNMP
Readable objects in a MIB modules (i.e., objects with a MAX-
ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important
to control GET and/or NOTIFY access to these objects and
possibly to encrypt the values of these objects when sending
them over the network via SNMP.
The support for SET operations in a non-secure environment
without proper protection can have a negative effect on network
operations. For example:
. Unauthorized changes to the Power Domain or business
context of a Power Monitor may result in misreporting or
interruption of power.
. Unauthorized changes to a power level may disrupt the power
settings of the different Power Monitors, and therefore the
level of functionality of the respective Power Monitors.
. Unauthorized changes to the demand history may disrupt
proper accounting of energy usage.
With respect to data transport SNMP versions prior to SNMPv3 did
not include adequate security. Even if the network itself is
secure (for example, by using IPsec), there is still no secure
control over who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in these MIB
modules.
It is recommended that implementers consider the security
features as provided by the SNMPv3 framework (see [RFC3410],
section 8), including full support for the SNMPv3 cryptographic
mechanisms (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is not
recommended. Instead, it is recommended to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to
an instance of these MIB modules is properly configured to give
access to the objects only to those principals (users) that have
legitimate rights to GET or SET (change/create/delete) them.
12.2. Security Considerations for IPFIX
EDITOR'S NOTE: to be completed if IPFIX is discussed in this
document
13. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
12. References 14. Acknowledgments
The authors would like to Michael Brown for improving the text
dramatically.
15. References
Normative References Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Requirement Levels, BCP 14, RFC 2119, March 1997. "Introduction and Applicability Statements for Internet
Standard Management Framework ", RFC 3410, December
2002.
[RFC5101] B. Claise, Ed., Specification of the IP Flow
Information Export (IPFIX) Protocol for the Exchange of
IP Traffic Flow Information, RFC 5101, January 2008.
[POWER-MON-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., [POWER-MON-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B.,
and M. Chandramouli, "Requirements for Power and M. Chandramouli, "Requirements for Power
Monitoring", draft-quittek-power-monitoring- Monitoring", draft-quittek-power-monitoring-
requirements-01 (work in progress), July 2010. requirements-01 (work in progress), July 2010.
[POWER-MON-MIB] Claise, B., Chandramouli, M., Parello, J., and [POWER-MON-MIB] Claise, B., Chandramouli, M., Parello, J., and
Schoening, B., "Power and Energy Monitoring MIB", Schoening, B., "Power and Energy Monitoring MIB",
draft-claise-energy-monitoring-mib-04, (work in draft-claise-energy-monitoring-mib-06, (work in
progress), Sept 2010. progress), October 2010.
Informative References Informative References
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3444] Pras, A., Schoenwaelder, J. "On the Differences [RFC3444] Pras, A., Schoenwaelder, J. "On the Differences
between Information Models and Data Models", RFC 3444, between Information Models and Data Models", RFC 3444,
January 2003. January 2003.
skipping to change at page 21, line 15 skipping to change at page 26, line 29
[LLDP] IEEE Std 802.1AB, "Station and Media Control [LLDP] IEEE Std 802.1AB, "Station and Media Control
Connectivity Discovery", 2005. Connectivity Discovery", 2005.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information
Base extension module for TIA-TR41.4 media endpoint Base extension module for TIA-TR41.4 media endpoint
discovery information", July 2005. discovery information", July 2005.
[DASH] "Desktop and mobile Architecture for System Hardware", [DASH] "Desktop and mobile Architecture for System Hardware",
http://www.dmtf.org/standards/mgmt/dash/ http://www.dmtf.org/standards/mgmt/dash/
13. Authors' Addresses Authors' Addresses
Benoit Claise Benoit Claise
Cisco Systems Inc. Cisco Systems, Inc.
De Kleetlaan 6a b1 De Kleetlaan 6a b1
Diegem 1813 Diegem 1813
BE BE
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com Email: bclaise@cisco.com
John Parello John Parello
Cisco Systems Inc. Cisco Systems, Inc.
3550 Cisco Way 3550 Cisco Way
San Jose, California 95134 San Jose, California 95134
US US
Phone: +1 408 525 2339 Phone: +1 408 525 2339
Email: jparello@cisco.com Email: jparello@cisco.com
Brad Schoening Brad Schoening
Cisco Systems Inc. Cisco Systems, Inc.
3550 Cisco Way 3550 Cisco Way
San Jose, California 95134 San Jose, California 95134
US US
Phone: +1 408 525 2339 Phone: +1 408 525 2339
Email: braschoe@cisco.com Email: braschoe@cisco.com
 End of changes. 151 change blocks. 
410 lines changed or deleted 643 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/