1

OPSAWG Agenda Items 7,8, 9

Juergen Quittek, John Parello, Benoit Claise78th IETF Meeting, Maastricht, 2010

7. Energy Management Framework / Architecture draft-claise-power-management-arch-00

8. Energy Management IDs Requirements for Energy Management:

draft-quittek-power-monitoring-requirements-01 Power and Energy Monitoring MIB:

draft-claise-energy-monitoring-mib-04 Definition of Managed Objects for Energy Management:

draft-quittek-power-mib-01 Considerations for Power and Energy Management:

draft-norwin-energy-consider-00

9. Energy Management Working Group Charter Proposal charter proposal

Energy Management Framework/Architecture

draft-claise-power-management-arch-00

Brad Schoening, John Parello, Benoit Claise

78th IETF Meeting, Maastricht, 2010

3

Architecture: Problem Description

Monitoring Power and Energy, based on existing data models (IEC 61850, IEC 62053-22, ANSI C12.20, …)

The target devices include: Router & switches Attached devices such as Power over Ethernet (PoE) devices But not limited to PoE devices. Example: PC Intelligent meters Proxy for building energy management Home energy gateway Etc…

Based on the requirement draft-quittek-power-monitoring-requirements-01

Currently some overlap with draft-claise-energy-monitoring-mib-04

Existing Implementation

4

Architecture: Example: Router, PoE, and non PoE device

5

Architecture: Example: BMS

IP

6

Architecture: Example: Smart PDU

7

Architecture: Overview of Scenarios

Use Case Scenarios

Scenario 1: Switch with PoE endpointsScenario 2: Switch with PoE endpoints + device(s)Scenario 3: A switch with Wireless Access PointsScenario 4: Network connected facilities gatewayScenario 5: Data Center NetworkScenario 6: Power Consumption of UPSScenario 7: Power Consumption of Battery-based

8

Architecture: Overview of New Concepts

Monitoring Power Monitor Information Power Monitor Meter Domain Power Monitor Parent and Child Power Monitor Levels Power Monitor Context

TBD Discovery Authentication Entitlement

Basically a new architecture for OPS We should lay down a good foundation for future work

in the energy area

9

Architecture: Concept of Parent/Child

The parent/Child = the parent reporting the power for the end point (child) And actually the parent controlling the child power states (not in scope) For example, Wake-on-Lan

Scaling issue if the NMS would control each child Building Management System requires a proxy

pmIndex 1, port, metered power

pmIndex 2, phone, negotiated power, parent = switch

pmIndex 3, PC, reported power, parent = switch

10

Architecture: Concept of Power Levels

Level ACPI Global/System State Name 1 G3, S5 Mech Off 2 G2, S5 Soft Off 3 G1, S4 Hibernate 4 G2, S3 Sleep (Save-to-RAM)

5 G2, S2 Standby 6 G2, S1 Ready 7 G0, S0, P5 LowMinus 8 G0, S0, P4 Low 9 G0, S0, P3 MediumMinus 10 G0, S0, P2 Medium 11 G0, S0, P1 HighMinus 12 G0, S0, P0 High

G = Global state, S = System state, P = Performance state ACPI: Advanced Configuration and Power Interface

Non-operational states

Operational states

12

Architecture: Concept of User Defined Power Levels

User Defined Power Level User Defined Name 0 none 1 short 2 tall 3 grande 4 venti

STD Power Level/Name User Power Level / Name

1 / Mech Off 0 / none 2 / Soft Off 0 / none 3 / Hibernate 0 / none 4 / Sleep, Save-to-RAM 0 / none 5 / Standby 0 / none 6 / Ready 1 / short 7 / LowMinus 1 / short 8 / Low 1 / short 9 / MediumMinus 2 / tall 10 / Medium 2 / tall 11 / HighMinus 3 / grande 12 / High 4 / venti

Implementation:Device Manufacturer’s Capability

Interface:Mapped to the Standard Levels

Energy Management IDs

Various, Benoit Claise78th IETF Meeting, Maastricht, 2010

Requirements for Energy Management: draft-quittek-power-monitoring-requirements

Definiton of Managed Objects for Energy Management: draft-claise-energy-monitoring-mib-04

draft-quittek-power-mib

Considerations for Power and Energy Management: draft-norwin-energy-consider

draft-quittek-power-monitoring-requirements-01

Abstract

This memo discusses requirements for energy management, particularly for monitoring consumption and controlling power states of devices.

This memo further shows that existing IETF standards are not sufficient for energy management and that energy management requires architectural considerations that are different from common other management functions.

draft-quittek-power-mib-01

Created from Requirements document

In Process of merging with claise monitoring MIB Contain the optional battery module

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes extensions to the Entity MIB to provide information about the energy consumption, the power states and battery status of managed devices and their components.

draft-claise-energy-monitoring-mib-04

Created from Requirements document

Defines monitoring in terms of:Power Monitor InformationPower Monitor Meter DomainPower Monitor Parent and ChildPower Monitor ContextPower Monitor LevelsPower Monitor Usage MeasurementOptional Power Usage QualityOptional Energy Measurement

17

draft-claise-energy-monitoring-mib-04

pmIndex 1, port, metered power

pmIndex 2, phone, negotiated power

pmIndex 3, PC, reported power

pmIndex 3

pmIndex 2

pmIndex 1

Via an agent

Known via LLDP-MED

Can we assume that the ENTITY-MIB is supported on all monitored devices?

No, so can’t use the entPhysicalIndex as THE index in the table New index: pmIndex, for each power monitor

18

Monitoring MIB: What’s new in version 3 & 4

Explained all the concepts More use cases Link with the LLDP-MED MIB User defined Power Levels Power Quality Better alignment with the IEC data model

More reviews from partners

Note: this is a very very quick summary of a 75 pages draft

draft-norwin-energy-consider-00

Recently Submitted

Lists and defines areas and concepts to be considered with energy management

Summary

Multiple drafts evolving together Requirements MIB Architecture

A series of new concepts for the architecture We should lay down a good foundation for future work in the

energy area

21

END