idnits 2.17.1 draft-ietf-eman-energy-monitoring-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 281 has weird spacing: '...tiplier eoP...' == Line 296 has weird spacing: '...tateSet eoPow...' == Line 320 has weird spacing: '...wStatus eoEne...' == Line 340 has weird spacing: '...exed by entPh...' == Line 903 has weird spacing: '...defines power...' == (13 more instances...) -- The document date (October 22, 2012) is 4197 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'EMAN-TERMINOLOGY' is defined on line 3665, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MED-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'EMAN-AWARE-MIB' -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-14) exists of draft-ietf-eman-requirements-09 == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-05 == Outdated reference: A later version (-13) exists of draft-ietf-eman-energy-monitoring-mib-03 == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-02 == Outdated reference: A later version (-06) exists of draft-ietf-eman-rfc4133bis-03 == Outdated reference: A later version (-09) exists of draft-parello-eman-definitions-07 Summary: 2 errors (**), 0 flaws (~~), 15 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Chandramouli 3 Internet-Draft Cisco Systems, Inc. 4 Intended Status: Standards Track B. Schoening 5 Expires: April 22, 2013 Independent Consultant 6 J. Quittek 7 T. Dietz 8 NEC Europe Ltd. 9 B. Claise 10 Cisco Systems, Inc. 11 October 22, 2012 13 Power and Energy Monitoring MIB 14 draft-ietf-eman-energy-monitoring-mib-04 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance 19 with the provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as 30 "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html 38 This Internet-Draft will expire on April 2013. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with 50 respect to this document. Code Components extracted from this 51 document must include Simplified BSD License text as described 52 in Section 4.e of the Trust Legal Provisions and are provided 53 without warranty as described in the Simplified BSD License. 55 Abstract 57 This document defines a subset of the Management Information 58 Base (MIB) for power and energy monitoring of devices. 60 Conventions used in this document 62 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 63 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", 64 "MAY", and "OPTIONAL" in this document are to be interpreted as 65 described in RFC 2119 [RFC2119]. 67 Table of Contents 69 1. Introduction............................................. 3 70 2. The Internet-Standard Management Framework............... 4 71 3. Use Cases................................................ 4 72 4. Terminology.............................................. 5 73 5. Architecture Concepts Applied to the MIB Module.......... 6 74 5.1. Energy Object Information............................. 13 75 5.2. Power State........................................... 14 76 5.2.1. Power State Set................................15 77 5.2.2. IEEE1621 Power State Set.......................15 78 5.2.3. DMTF Power State Set...........................15 79 5.2.4. EMAN Power State Set...........................17 80 5.3. Energy Object Usage Information....................... 19 81 5.4. Optional Power Usage Characteristics.................. 20 82 5.5. Optional Energy Measurement........................... 21 83 5.6. Fault Management...................................... 25 84 6. Discovery............................................... 26 85 7. Link with the other IETF MIBs........................... 27 86 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB..27 87 7.2. Link with the ENTITY-STATE MIB......................28 88 7.3. Link with the POWER-OVER-ETHERNET MIB...............28 89 7.4. Link with the UPS MIB...............................29 90 7.5. Link with the LLDP and LLDP-MED MIBs................30 91 8. Implementation Scenario................................. 31 92 9. Structure of the MIB.................................... 33 93 10. MIB Definitions........................................ 34 94 11. Security Considerations................................ 74 95 12. IANA Considerations.................................... 75 96 12.1. IANA Considerations for the MIB Modules.............. 75 97 12.2. IANA Registration of new Power State Set............. 76 98 12.2.1. IANA Registration of the IEEE1621 Power State Set 76 99 12.2.2. IANA Registration of the DMTF Power State Set.... 77 100 12.2.3. IANA Registration of the EMAN Power State Set.... 77 101 12.3. Updating the Registration of Existing Power State 102 Sets....................................................... 77 103 12. Contributors........................................... 78 104 13. Acknowledgment......................................... 78 105 14. Open Issues............................................ 78 106 15. References............................................. 79 107 15.2. Normative References...............................79 108 15.3. Informative References.............................79 110 1. Introduction 112 This document defines a subset of the Management Information 113 Base (MIB) for use in energy management of devices within or 114 connected to communication networks. The MIB modules in this 115 document are designed to provide a model for energy management, 116 which includes monitoring for power state and energy consumption 117 of networked elements. This MIB takes into account the Energy 118 Management Framework [EMAN-FMWK], which in turn, is based on the 119 Requirements for Energy Management [EMAN-REQ]. 121 Energy management is applicable to devices in communication 122 networks. Target devices for this specification include (but 123 are not limited to): routers, switches, Power over Ethernet 124 (PoE) endpoints, protocol gateways for building management 125 systems, intelligent meters, home energy gateways, hosts and 126 servers, sensor proxies, etc. Target devices and the use cases 127 for Energy Management are discussed in Energy Management 128 Applicability Statement [EMAN-AS]. 130 Where applicable, device monitoring extends to the individual 131 components of the device and to any attached dependent devices. 132 For example: A device can contain components that are 133 independent from a power-state point of view, such as line 134 cards, processor cards, hard drives. A device can also have 135 dependent attached devices, such as a switch with PoE endpoints 136 or a power distribution unit with attached endpoints. 138 Devices and their sub-components may be characterized by the 139 power-related attributes of a physical entity present in the 140 ENTITY-MIB, even though the ENTITY-MIB compliance is not a 141 requirement due to the variety and broad base of devices 142 concerned with energy management. 144 2. The Internet-Standard Management Framework 146 For a detailed overview of the documents that describe the 147 current Internet-Standard Management Framework, please refer to 148 section 7 of RFC 3410 [RFC3410]. 150 Managed objects are accessed via a virtual information store, 151 termed the Management Information Base or MIB. MIB objects are 152 generally accessed through the Simple Network Management 153 Protocol (SNMP). Objects in the MIB are defined using the 154 mechanisms defined in the Structure of Management Information 155 (SMI). This memo specifies MIB modules that are compliant to 156 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 157 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 159 3. Use Cases 161 Requirements for power and energy monitoring for networking 162 devices are specified in [EMAN-REQ]. The requirements in [EMAN- 163 REQ] cover devices typically found in communications networks, 164 such as switches, routers, and various connected endpoints. For 165 a power monitoring architecture to be useful, it should also 166 apply to facility meters, power distribution units, gateway 167 proxies for commercial building control, home automation 168 devices, and devices that interface with the utility and/or 169 smart grid. Accordingly, the scope of the MIB modules in this 170 document is broader than that specified in [EMAN-REQ]. Several 171 use cases for Energy Management have been identified in the 172 "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An 173 illustrative example scenario is presented in Section 8. 175 4. Terminology 177 Please refer to [EMAN-FMWK] for the definitions of the 178 following terminology used in this draft. 180 Device 182 Component 184 Energy Management 186 Energy Management System (EnMS) 188 ISO Energy Management System 190 Energy 192 Power 194 Demand 196 Power Characteristics 198 Electrical Equipment 200 Non-Electrical Equipment (Mechanical Equipment) 202 Energy Object 204 Electrical Energy Object 206 Non-Electrical Energy Object 208 Energy Monitoring 210 Energy Control 212 Provide Energy: 214 Receive Energy: 216 Power Interface 217 Power Inlet 219 Power Outlet 221 Energy Management Domain 223 Energy Object Identification 225 Energy Object Context 227 Energy Object Relationship 229 Aggregation Relationship 231 Metering Relationship 233 Power Source Relationship 235 Proxy Relationship 237 Energy Object Parent 239 Energy Object Child 241 Power State 243 Power State Set 245 Nameplate Power 247 5. Architecture Concepts Applied to the MIB Module 249 This section describes the concepts specified in the Energy 250 Management Framework [EMAN-FMWK] that pertain to power usage, 251 with specific information related to the MIB module specified in 252 this document. This subsection maps to the section 253 "Architecture High Level Concepts" in the Power Monitoring 254 Architecture [EMAN-FMWK]. 256 The Energy Monitoring MIB has 2 independent MIB modules. The 257 first MIB module energyObjectMib is focused on measurement of 258 power and energy. The second MIB module powerCharMIB is focused 259 on Power Characteristics measurements. 261 The energyObjectMib MIB module consists of four tables. The 262 first table eoPowerTable is indexed by entPhysicalIndex. The 263 second table eoPowerStateTable indexed by entPhysicalIndex, 264 and eoPowerStateIndex. The eoEnergyParametersTable is indexed 265 by eoEnergyParametersIndex. The eoEnergyTable is indexed by 266 eoEnergyParametersIndex and eoEnergyCollectionStartTime. 268 eoMeterCapabilitiesTable(1) 269 | 270 +--- eoMeterCapabilitiesEntry(1) [entPhysicalIndex] 271 | | 272 | +---r-n BITS eoMeterCapability 273 | 275 eoPowerTable(1) 276 | 277 +---eoPowerEntry(1) [entPhysicalIndex] 278 | | 279 | +---r-n Integer32 eoPower(1) 280 | +-- r-n Integer32 eoPowerNamePlate(2) 281 | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3) 282 | +-- r-n Integer32 eoPowerAccuracy(4) 283 | +-- r-n INTEGER eoMeasurementCaliber(5) 284 | +-- r-n INTEGER eoPowerCurrentType(6) 285 | +-- r-n INTEGER eoPowerOrigin(7) 286 | +-- rwn Integer32 eoPowerAdminState(8) 287 | +-- r-n Integer32 eoPowerOperState(9) 288 | +-- r-n OwnerString eoPowerStateEnterReason(10) 289 | | 290 | | 291 +---eoPowerStateTable(2) 292 | +--eoPowerStateEntry(1) 293 | | [entPhysicalIndex, 294 | | eoPowerStateIndex] 295 | | 296 | +-- --n IANAPowerStateSet eoPowerStateIndex(1) 297 | +-- r-n Interger32 eoPowerStateMaxPower (2) 298 | +-- r-n UnitMultiplier 299 | eoPowerStatePowerUnitMultiplier (3) 300 | +-- r-n TimeTicks eoPowerStateTotalTime(4) 301 | +-- r-n Counter32 eoPowerStateEnterCount(5) 302 | 304 +eoEnergyParametersTable(1) 305 +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] 306 | 308 | +-- --n PhysicalIndex eoEnergyObjectIndex (1) 309 | + r-n Integer32 eoEnergyParametersIndex (2) 310 | +-- r-n TimeInterval 311 | eoEnergyParametersIntervalLength (3) 312 | +-- r-n Integer32 313 | eoEnergyParametersIntervalNumber (4) 314 | +-- r-n Integer32 315 | eoEnergyParametersIntervalMode (5) 316 | +-- r-n TimeInterval 317 | eoEnergyParametersIntervalWindow (6) 318 | +-- r-n Integer32 319 | eoEnergyParametersSampleRate (7) 320 | +-- r-n RowStatus eoEnergyParametersStatus (8) 321 | 322 +eoEnergyTable (1) 323 +---eoEnergyEntry(1) [ eoEnergyParametersIndex, 324 eoEnergyCollectionStartTime] 325 | 326 | +-- r-n TimeTicks eoEnergyCollectionStartTime (1) 327 | +-- r-n Integer32 eoEnergyConsumed (2) 328 | +-- r-n Integer32 eoEnergyyProduced (3) 329 | +-- r-n Integer32 eoEnergyNet (4) 330 | +-- r-n UnitMultiplier 331 | eoEnergyUnitMultiplier (5) 332 | +-- r-n Integer32 eoEnergyAccuracy(6) 333 | +-- r-n Integer32 eoEnergyMaxConsumed (7) 334 | +-- r-n Integer32 eoEnergyMaxProduced (8) 335 | +-- r-n TimeTicks 336 | eoEnergyDiscontinuityTime(9) 337 | +-- r-n RowStatus eoEnergyParametersStatus (10) 339 The powerCharacteristicsMIB consists of four tables. 340 eoACPwrCharacteristicsTable is indexed by entPhysicalIndex. 341 eoACPwrCharacteristicsPhaseTable is indexed by entPhysicalIndex 342 and eoPhaseIndex. eoACPwrCharacteristicsWyePhaseTable and 343 eoACPwrCharacteristicsDelPhaseTable are indexed by 344 entPhysicalIndex and eoPhaseIndex. 346 eoACPwrCharacteristicsTable (1) 347 | 348 +---eoACPwrCharacteristicsEntry (1) [ entPhysicalIndex] 349 | | 350 | | 351 | +---r-n INTEGER eoACPwrCharacteristicsConfiguration 352 (1) 353 | +-- r-n Interger32 eoACPwrCharacteristicsAvgVoltage (2) 354 | +-- r-n Integer32 eoACPwrCharacteristicsAvgCurrent (3) 355 | +-- r-n Integer32 eoACPwrCharacteristicsFrequency (4) 356 | +-- r-n UnitMultiplier 357 | eoACPwrCharacteristicsPowerUnitMultiplier (5) 358 | +-- r-n Integer32 eoACPwrCharacteristicsPowerAccuracy 359 (6) 360 | +-- r-n Interger32 361 eoACPwrCharacteristicsTotalActivePower (7) 362 | +-- r-n Integer32 363 | eoACPwrCharacteristicsTotalReactivePower (8) 364 | +-- r-n Integer32 365 eoACPwrCharacteristicsTotalApparentPower (9) 366 | +-- r-n Integer32 367 eoACPwrCharacteristicsTotalPowerFactor(10) 368 | +-- r-n Integer32 eoACPwrCharacteristicsThdAmpheres 369 (11) 370 | 371 +eoACPwrCharacteristicsPhaseTable (1) 372 +---EoACPwrCharacteristicsPhaseEntry(1)[ entPhysicalIndex, 373 | | eoPhaseIndex] 374 | | 375 | +-- r-n Integer32 eoPhaseIndex (1) 376 | +-- r-n Integer32 377 | | eoACPwrCharacteristicsPhaseAvgCurrent (2) 378 | +-- r-n Integer32 379 | | eoACPwrCharacteristicsPhaseActivePower (3) 380 | +-- r-n Integer32 381 | | eoACPwrCharacteristicsPhaseReactivePower (4) 382 | +-- r-n Integer32 383 | | eoACPwrCharacteristicsPhaseApparentPower (5) 384 | +-- r-n Integer32 385 | | eoACPwrCharacteristicsPhasePowerFactor (6) 386 | +-- r-n Integer32 387 | | eoACPwrCharacteristicsPhaseImpedance (7) 388 | | 389 +eoACPwrCharacteristicsDelPhaseTable (1) 390 +-- eoACPwrCharacteristicsDelPhaseEntry(1) 391 | | [entPhysicalIndex, 392 | | eoPhaseIndex] 393 | +-- r-n Integer32 394 | | eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage 395 (1) 396 | +-- r-n Integer32 397 | | eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage 398 (2) 399 | +-- r-n Integer32 eoACPwrCharacteristicsDelThdCurrent 400 (3) 401 | | 402 +eoACPwrCharacteristicsWyePhaseTable (1) 403 +-- eoACPwrCharacteristicsWyePhaseEntry (1) 404 | | [entPhysicalIndex, 405 | | eoPhaseIndex] 406 | +-- r-n Integer32 407 | | eoACPwrCharacteristicsWyePhaseToNeutralVoltage 408 (1) 409 | +-- r-n Integer32 410 | | eoACPwrCharacteristicsWyePhaseCurrent (2) 411 | +-- r-n Integer32 412 | | eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage 413 (3) 414 | . 416 A UML representation of the MIB objects in the two MIB modules 417 are energyObjectMib and powerCharacteristicsMIB are presented. 419 +--------------------------+ 420 | Energy Object ID | 421 | ----------------------- | 422 | | 423 | entPhysIndex (*) | 424 | entPhysicalName (*) | 425 | entPhysicalUUID (*) | +---------------------------+ 426 | | | | 427 | | | Energy Object Attributes | 428 | | | ------------------------- | 429 | | | | 430 +--------------------------+ | eoPowerNamePlate | 431 | | | eoPowerMeasurementCaliber | 432 | | | eoPowerOrigin | 433 | | | eoPowerCurrentType | 434 | | +---------------------------+ 435 | | | 436 | | | 437 v | v 438 +-----------------------------------------+ 439 | Energy Object Measurement | 440 | --------------------------------------- | 441 | eoPower | 442 | eoPowerUnitMultiplier | 443 | eoPowerAccuracy | 444 +-----------------------------------------+ 445 ^ | ^ 446 | | | 447 +-------------------------+ | | 448 | Energy Object State | | +------------------------+ 449 | ----------------------- | | | Energy Object State | 450 | eoPowerAdminState | | | Statistics | 451 | eoPowerOperState | | |----------------------- | 452 | eoPowerStateEnterReason | | | eoPowerStateMaxPower | 453 +-------------------------+ | | eoPowerStateTotalTime | 454 | | eoPowerStateEnterCount | 455 | +------------------------+ 456 | 457 | 458 | 459 | 461 Figure 1:UML diagram for energyObjectMib 463 (*) Link with the ENTITY-MIB 465 | 466 | 467 V 469 +----------------------------------------+ 470 | Energy ParametersTable | 471 | -------------------------------------- | 472 | | 473 | eoEnergyObjectIndex | 474 | eoEnergyParametersIndex | 475 | eoEnergyParametersIntervalLength | 476 | eoEnergyParametersIntervalNumber | 477 | eoEnergyParametersIntervalMode | 478 | eoEnergyParametersIntervalWindow | 479 | eoEnergyParametersSampleRate | 480 | eoEnergyParametersStatus | 481 +----------------------------------------+ 483 | 484 | 485 | 486 V 487 +----------------------------------------+ 488 | Energy Table | 489 | -------------------------------------- | 490 | eoEnergyCollectionStartTime | 491 | eoEnergyConsumed | 492 | eoEnergyProduced | 493 | eoEnergyNet | 494 | eoEnergyUnitMultiplier | 495 | eoEnergyAccuracy | 496 | eoMaxConsumed | 497 | eoMaxProduced | 498 | eoDiscontinuityTime | 499 +----------------------------------------+ 501 +--------------------------+ 502 | EnergyObject ID | 503 | ----------------------- | 504 | | 505 | entPhysicalIndex (*) | 506 | | 507 +--------------------------+ 508 | 509 v 510 +--------------------------------------------+ 511 | Power Characteristics | 512 | ----------------------------------- | 513 | eoACPwrCharacteristicsConfiguration | 514 | eoACPwrCharacteristicsAvgVoltage | 515 | eoACPwrCharacteristicsAvgCurrent | 516 | eoACPwrCharacteristicsFrequency | 517 | eoACPwrCharacteristicsPowerUnitMultiplier | 518 | eoACPwrCharacteristicsPowerAccuracy | 519 | eoACPwrCharacteristicsTotalActivePower | 520 | eoACPwrCharacteristicsTotalReactivePower | 521 | eoACPwrCharacteristicsTotalApparentPower | 522 | eoACPwrCharacteristicsTotalPowerFactor | 523 | eoACPwrCharacteristicsThdAmpheres | 524 +--------------------------------------------+ 525 ^ ^ 526 | | 527 | ----------- 528 | | 529 | | 530 +--------------------------------------------+ | 531 | Power Phase Characteristics | | 532 | ---------------------------------- | | 533 | eoPhaseIndex | | 534 | eoACPwrCharacteristicsPhaseAvgCurrent | | 535 | eoACPwrCharacteristicsAvgCurrent | | 536 | eoACPwrCharacteristicsFrequency | | 537 | eoACPwrCharacteristicsPowerUnitMultiplier | | 538 | eoACPwrCharacteristicsPowerAccuracy | | 539 | eoACPwrCharacteristicsPhaseActivePower | | 540 | eoACPwrCharacteristicsPhaseReactivePower | | 541 | eoACPwrCharacteristicsPhaselApparentPower | | 542 | eoACPwrCharacteristicsPhaseImpedance | | 543 +--------------------------------------------+ | 544 | 545 | 546 | 547 | 548 | 549 | 550 +------------------------------------------------------+ 551 | AC Input DEL Configuration | 552 | | 553 | eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage | 554 | eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage | 555 | eoACPwrCharacteristicsDelThdCurrent | 556 +------------------------------------------------------+ 557 | 558 | 559 +---------------------------------------------------+ 560 | AC Input WYE Configuration | 561 | | 562 | eoACPwrCharacteristicsWyePhaseToNeutralVoltage | 563 | eoACPwrCharacteristicsWyePhaseCurrent | 564 | eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage | 565 +---------------------------------------------------+ 567 Figure 2: UML diagram for the powerCharacteristicsMIB 569 (*) Link with the ENTITY-MIB 571 5.1. Energy Object Information 573 Refer to the "Energy Object Information" section in [EMAN-FMWK] 574 for background information. An energy aware device is 575 considered as an instance of a Energy Object as defined in the 576 [EMAN-FMWK]. 578 The Energy Object identity information is specified in the MIB 579 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the 580 eoTable. In this table, every Energy Object SHOULD have a 581 printable name eoName, and MUST HAVE a unique Energy Object 582 index entPhysicalUUID and entPhysicalIndex. The ENERGY-AWARE-MIB 583 module returns the relationship (parent/child) between Energy 584 Objects. There are several possible relationships between Parent 585 and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy, 586 PoweredBy, AggregatedBy and ProxyedBy. 588 5.2. Power State 590 Refer to the "Power States" section in [EMAN-FMWK] for 591 background information. 593 An Energy Object may have energy conservation modes called Power 594 States. Between the ON and OFF states of a device, there can be 595 several intermediate energy saving modes. Those energy saving 596 modes are called as Power States. 598 Power States, which represent universal states of power 599 management of an Energy Object, are specified by the 600 eoPowerState MIB object. The actual Power State is specified by 601 the eoPowerOperState MIB object, while the eoPowerAdminState MIB 602 object specifies the Power State requested for the Energy 603 Object. The difference between the values of eoPowerOperState 604 and eoPowerAdminState can be attributed that the Energy Object 605 is busy transitioning from eoPowerAdminState into the 606 eoPowerOperState, at which point it will update the content of 607 eoPowerOperState. In addition, the possible reason for change 608 in Power State is reported in eoPowerStateEnterReason. 609 Regarding eoPowerStateEnterReason, management stations and 610 Energy Objects should support any format of the owner string 611 dictated by the local policy of the organization. It is 612 suggested that this name contain at least the reason for the 613 transition change, and one or more of the following: IP address, 614 management station name, network manager's name, location, or 615 phone number. 617 The MIB objects eoPowerOperState, eoPowerAdminState , and 618 eoPowerStateEnterReason are contained in the eoPowerTable MIB 619 table. 621 The eoPowerStateTable table enumerates the maximum power usage 622 in watts, for every single supported Power State of each Power 623 State Set supported by the Energy Object. In addition, 624 PowerStateTable provides additional statistics: 625 eoPowerStateEnterCount, the number of times an entity has 626 visited a particular Power State, and eoPowerStateTotalTime, the 627 total time spent in a particular Power State of an Energy 628 Object. 630 5.2.1. Power State Set 632 There are several standards and implementations of Power State 633 Sets. A Energy Object can support one or multiple Power State 634 Set implementation(s) concurrently. 636 There are currently three Power State Sets advocated: 638 unknown(0) 639 IEEE1621(256) - [IEEE1621] 640 DMTF(512) - [DMTF] 641 EMAN(1024) - [EMAN-MONITORING-MIB] 643 The respective specific states related to each Power State Set 644 are specified in the following sections. The guidelines for 645 addition of new Power State Sets have been specified in the IANA 646 Considerations Section. 648 5.2.2. IEEE1621 Power State Set 650 The IEEE1621 Power State Set [IEEE1621] consists of 3 651 rudimentary states : on, off or sleep. 653 on(0) - The device is fully On and all features of the 654 device are in working mode. 655 off(1) - The device is mechanically switched off and does 656 not consume energy. 657 sleep(2) - The device is in a power saving mode, and some 658 features may not be available immediately. 660 The Textual Convention IANAPowerStateSet provides the proposed 661 numbering of the Power States within the IEEE1621 Power State 662 Set. 664 5.2.3. DMTF Power State Set 666 DMTF [DMTF] standards organization has defined a power profile 667 standard based on the CIM (Common Information Model) model that 668 consists of 15 power states ON (2), SleepLight (3), SleepDeep 669 (4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off- 670 Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10), 671 Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard 672 Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off- 673 Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF 674 standard is targeted for hosts and computers. Details of the 675 semantics of each Power State within the DMTF Power State Set 676 can be obtained from the DMTF Power State Management Profile 677 specification [DMTF]. 679 DMTF power profile extends ACPI power states. The following 680 table provides a mapping between DMTF and ACPI Power State Set: 682 --------------------------------------------------- 683 | DMTF | ACPI | 684 | Power State | Power State | 685 --------------------------------------------------- 686 | Reserved(0) | | 687 --------------------------------------------------- 688 | Reserved(1) | | 689 --------------------------------------------------- 690 | ON (2) | G0-S0 | 691 -------------------------------------------------- 692 | Sleep-Light (3) | G1-S1 G1-S2 | 693 -------------------------------------------------- 694 | Sleep-Deep (4) | G1-S3 | 695 -------------------------------------------------- 696 | Power Cycle (Off-Soft) (5) | G2-S5 | 697 --------------------------------------------------- 698 | Off-hard (6) | G3 | 699 --------------------------------------------------- 700 | Hibernate (Off-Soft) (7) | G1-S4 | 701 --------------------------------------------------- 702 | Off-Soft (8) | G2-S5 | 703 --------------------------------------------------- 704 | Power Cycle (Off-Hard) (9) | G3 | 705 --------------------------------------------------- 706 | Master Bus Reset (10) | G2-S5 | 707 --------------------------------------------------- 708 | Diagnostic Interrupt (11) | G2-S5 | 709 --------------------------------------------------- 710 | Off-Soft Graceful (12) | G2-S5 | 711 --------------------------------------------------- 712 | Off-Hard Graceful (13) | G3 | 713 --------------------------------------------------- 714 | MasterBus Reset Graceful (14) | G2-S5 | 715 --------------------------------------------------- 716 | Power Cycle off-soft Graceful (15)| G2-S5 | 717 --------------------------------------------------- 718 | Power Cycle off-hard Graceful (16)| G3 | 719 --------------------------------------------------- 720 Figure 3: DMTF and ACPI Powe State Set Mapping 722 The Textual Convention IANAPowerStateSet contains the proposed 723 numbering of the Power States within the DMTF Power State Set. 725 5.2.4. EMAN Power State Set 727 The EMAN Power State Set represents an attempt for a uniform 728 standard approach to model the different levels of power 729 consumption of a device. The EMAN Power States are an expansion 730 of the basic Power States as defined in IEEE1621 that also 731 incorporate the Power States defined in ACPI and DMTF. 732 Therefore, in addition to the non-operational states as defined 733 in ACPI and DMTF standards, several intermediate operational 734 states have been defined. 736 There are twelve Power States, that expand on IEEE1621 on, sleep 737 and off. The expanded list of Power States are divided into six 738 operational states, and six non-operational states. The lowest 739 non-operational state is 1 and the highest is 6. Each non- 740 operational state corresponds to an ACPI state [ACPI] 741 corresponding to Global and System states between G3 (hard-off) 742 and G1 (sleeping). For Each operational state represent a 743 performance state, and may be mapped to ACPI states P0 (maximum 744 performance power) through P5 (minimum performance and minimum 745 power). 747 An Energy Object may have fewer Power States than twelve and 748 would then map several policy states to the same power state. 749 Energy Object with more than twelve states, would choose which 750 twelve to represent as power policy states. 752 In each of the non-operational states (from mechoff(1) to 753 ready(6)), the Power State preceding it is expected to have a 754 lower power consumption and a longer delay in returning to an 755 operational state: 757 IEEE1621 Power(off): 759 mechoff(1) : An off state where no entity features are 760 available. The entity is unavailable. 761 No energy is being consumed and the power 762 connector can be removed. This 763 corresponds to ACPI state G3. 765 softoff(2) : Similar to mechoff(1), but some 766 components remain powered or receive 767 trace power so that the entity 768 can be awakened from its off state. In 769 softoff(2), no context is saved and the 770 device typically requires a complete boot 771 when awakened. This corresponds to ACPI 772 state G2. 774 IEEE1621 Power(sleep) 776 hibernate(3): No entity features are available. The 777 entity may be awakened without requiring 778 a complete boot, but the time for 779 availability is longer than sleep(4). An 780 example for state hibernate(3) is a save 781 to-disk state where DRAM context is not 782 maintained. Typically, energy consumption 783 is zero or close to zero. This 784 corresponds to state G1, S4 in ACPI. 786 sleep(4) : No entity features are available, except 787 for out-of-band management, for example 788 wake-up mechanisms. The time for 789 availability is longer than standby(5). 790 An example for state sleep(4) is a save- 791 to-RAM state, where DRAM context is 792 maintained. Typically, energy 793 consumption is close to zero. This 794 corresponds to state G1, S3 in ACPI. 796 standby(5) : No entity features are available, except 797 for out-of-band management, for example 798 wake-up mechanisms. This mode is analogous 799 to cold-standy. The time for availability 800 is longer than ready(6). For example, the 801 processor context is not maintained. 802 Typically, energy consumption is close to 803 zero. This corresponds to state G1, S2 in 804 ACPI. 806 ready(6) : No entity features are available, except 807 for out-of-band management, for example 808 wake-up mechanisms. This mode is 809 analogous to hot-standby. The entity can 810 be quickly transitioned into an 811 operational state. For example, 812 processors are not executing, but 813 processor context is maintained. This 814 corresponds to state G1, S1 in ACPI. 816 IEEE1621 Power(on): 818 lowMinus(7) : Indicates some entity features may not be 819 available and the entity has selected 820 measures/options to provide less than 821 low(8) usage. This corresponds to 822 ACPI State G0. This includes operational 823 states lowMinus(7) to full(12). 825 low(8) : Indicates some features may not be 826 available and the entity has taken 827 measures or selected options to provide 828 less than mediumMinus(9) usage. 830 mediumMinus(9): Indicates all entity features are 831 available but the entity has taken 832 measures or selected options to provide 833 less than medium(10) usage. 835 medium(10) : Indicates all entity features are 836 available but the entity has taken 837 measures or selected options to provide 838 less than highMinus(11) usage. 840 highMinus(11): Indicates all entity features are 841 available and power usage is less 842 than high(12). 844 high(12) : Indicates all entity features are 845 available and the entity is consuming the 846 highest power. 848 The Textual Convention IANAPowerStateSet contains the proposed 849 numbering of the Power States within the EMAN Power State Set. 851 5.3. Energy Object Usage Information 853 Refer to the "Energy Object Usage Measurement" section in [EMAN- 854 FMWK] for background information. 856 For an Energy Object, power usage is reported using eoPower. 857 The magnitude of measurement is based on the 858 eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier 859 Textual Convention (TC). Power measurement magnitude should 860 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 861 [IEC.62053-22] definition of unit multiplier for the SI (System 862 International) units of measure. Measured values are 863 represented in SI units obtained by BaseValue * 10 raised to the 864 power of the scale. 866 For example, if current power usage of an Energy Object is 3, it 867 could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of 868 eoPowerUnitMultiplier. Note that other measurements throughout 869 the two MIB modules in this document use the same mechanism, 870 including eoPowerStatePowerUnitMultiplier, 871 eoEnergyUnitMultiplier, and 872 eoACPwrCharacteristicsPowerUnitMultiplier. 874 In addition to knowing the usage and magnitude, it is useful to 875 know how a eoPower measurement was obtained. An NMS can use 876 this to account for the accuracy and nature of the reading 877 between different implementations. For this eoPowerOrigin 878 describes whether the measurements were made at the device 879 itself or from a remote source. The eoPowerMeasurementCaliber 880 describes the method that was used to measure the power and can 881 distinguish actual or estimated values. There may be devices in 882 the network, which may not be able to measure or report power 883 consumption. For those devices, the object 884 eoPowerMeasurementCaliber shall report that measurement 885 mechanism is "unavailable" and the eoPower measurement shall be 886 "0". 888 The nameplate power rating of an Energy Object is specified in 889 eoPowerNameplate MIB object. 891 5.4. Optional Power Usage Characteristics 893 Refer to the "Optional Power Usage Characteristics" section in 894 [EMAN-FMWK] for background information. 896 The optional powerCharacteristicsMIB MIB module can be 897 implemented to further describe power usage characteristics 898 measurement. The powerCharacteristicsMIB MIB module adheres 899 closely to the IEC 61850 7-2 standard to describe AC 900 measurements. 902 The powerCharacteristicsMIB MIB module contains a primary table, 903 the eoACPwrCharacteristicsTable table, that defines power 904 characteristics measurements for supported entPhysicalIndex 905 entities, as a sparse extension of the eoPowerTable (with 906 entPhysicalIndex as primary index). This 907 eoACPwrCharacteristicsTable table contains such information as 908 the configuration (single phase, DEL 3 phases, WYE 3 phases), 909 voltage, frequency, power accuracy, total active/reactive 910 power/apparent power, amperage, and voltage. 912 In case of 3-phase power, the eoACPwrCharacteristicsPhaseTable 913 additional table is populated with Power Characteristics 914 measurements per phase (so double indexed by the 915 entPhysicalIndex and eoPhaseIndex). This table, which describes 916 attributes common to both WYE and DEL configurations, contains 917 the average current, active/reactive/apparent power, power 918 factor, and impedance. 920 In case of 3-phase power with a DEL configuration, the 921 eoACPwrCharacteristicsDelPhaseTable table describes the phase- 922 to-phase power characteristics measurements, i.e., voltage and 923 current. 925 In case of 3-phase power with a Wye configuration, the 926 eoACPwrCharacteristicsWyePhaseTable table describes the phase- 927 to-neutral power characteristics measurements, i.e., voltage and 928 current. 930 5.5. Optional Energy Measurement 932 Refer to the "Optional Energy and demand Measurement" section in 933 [EMAN-FMWK] for the definition and terminology information. 935 It is relevant to measure energy when there are actual power 936 measurements from an Energy Object, and not when the power 937 measurement is assumed or predicted as specified in the 938 description clause of the object eoPowerMeasurementCaliber. 940 Two tables are introduced to characterize energy measurement of 941 an Energy Object: eoEnergyTable and eoEnergyParametersTable. 942 Both energy and demand information can be represented via the 943 eoEnergyTable. Energy information will be an accumulation with 944 no interval. Demand information can be represented. 945 The eoEnergyParametersTable consists of the parameters defining 946 eoEnergyParametersIndex, an index of that specifies the setting 947 for collection of energy measurements for an Energy Object, 948 eoEnergyObjectIndex, linked to the entPhysicalIndex of the 949 Energy Object, the duration of measurement intervals in seconds, 950 (eoEnergyParametersIntervalLength), the number of successive 951 intervals to be stored in the eoEnergyTable, 952 (eoEnergyParametersIntervalNumber), the type of measurement 953 technique (eoEnergyParametersIntervalMode), and a sample rate 954 used to calculate the average (eoEnergyParametersSampleRate). 955 Judicious choice of the sampling rate will ensure accurate 956 measurement of energy while not imposing an excessive polling 957 burden. 959 There are three eoEnergyParametersIntervalMode types used for 960 energy measurement collection: period, sliding, and total. The 961 choices of the the three different modes of collection are based 962 on IEC standard 61850-7-4. Note that multiple 963 eoEnergyParametersIntervalMode types MAY be configured 964 simultaneously. It is important to note that for a given Energy 965 Object, multiple modes (periodic, total, sliding window) of 966 energy measurement collection can be configured with the use of 967 eoEnergyParametersIndex. However, simultaneous measurement in 968 multiple modes for a given Energy Object depends on the Energy 969 Object capability. 971 These three eoEnergyParametersIntervalMode types are illustrated 972 by the following three figures, for which: 974 - The horizontal axis represents the current time, with the 975 symbol <--- L ---> expressing the 976 eoEnergyParametersIntervalLength, and the 977 eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, 978 ..., Sx where x is the value of 979 eoEnergyParametersIntervalNumber. 981 - The vertical axis represents the time interval of sampling and 982 the value of eoEnergyConsumed can be obtained at the end of the 983 sampling period. The symbol =========== denotes the duration of 984 the sampling period. 986 | | | =========== | 987 |============ | | | 988 | | | | 989 | |============ | | 990 | | | | 991 | <--- L ---> | <--- L ---> | <--- L ---> | 992 | | | | 993 S1 S2 S3 S4 994 Figure 4 : Period eoEnergyParametersIntervalMode 996 A eoEnergyParametersIntervalMode type of 'period' specifies non- 997 overlapping periodic measurements. Therefore, the next 998 eoEnergyCollectionStartTime is equal to the previous 999 eoEnergyCollectionStartTime plus 1000 eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... 1002 |============ | 1003 | | 1004 | <--- L ---> | 1005 | | 1006 | |============ | 1007 | | | 1008 | | <--- L ---> | 1009 | | | 1010 | | |============ | 1011 | | | | 1012 | | | <--- L ---> | 1013 | | | | 1014 | | | |============ | 1015 | | | | | 1016 | | | | <--- L ---> | 1017 S1 | | | | 1018 | | | | 1019 | | | | 1020 S2 | | | 1021 | | | 1022 | | | 1023 S3 | | 1024 | | 1025 | | 1026 S4 1028 Figure 5 : Sliding eoEnergyParametersIntervalMode 1030 A eoEnergyParametersIntervalMode type of 'sliding' specifies 1031 overlapping periodic measurements. 1033 | | 1034 |========================= | 1035 | | 1036 | | 1037 | | 1038 | <--- Total length ---> | 1039 | | 1040 S1 1042 Figure 6 : Total eoEnergyParametersIntervalMode 1044 A eoEnergyParametersIntervalMode type of 'total' specifies a 1045 continuous measurement since the last reset. The value of 1046 eoEnergyParametersIntervalNumber should be (1) one and 1047 eoEnergyParametersIntervalLength is ignored. 1049 The eoEnergyParametersStatus is used to start and stop energy 1050 usage logging. The status of this variable is "active" when 1051 all the objects in eoEnergyParametersTable are appropriate which 1052 in turn indicates if eoEnergyTable entries exist or not. 1054 The eoEnergyTable consists of energy measurements in 1055 eoEnergyConsumed, eoEnergyProduced and eoEnergyNet, the units of 1056 the measured energy eoEnergyUnitMultiplier, and the maximum 1057 observed energy within a window, eoEnergyMaxConsumed, 1058 eoEnergyMaxProduced. 1060 Measurements of the total energy consumed by an Energy Object 1061 may suffer from interruptions in the continuous measurement of 1062 energy consumption. In order to indicate such interruptions, 1063 the object eoEnergyDiscontinuityTime is provided for indicating 1064 the time of the last interruption of total energy measurement. 1065 eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] 1066 when the device was reset. 1068 The following example illustrates the eoEnergyTable and 1069 eoEnergyParametersTable: 1071 First, in order to estimate energy, a time interval to sample 1072 energy should be specified, i.e. 1073 eoEnergyParametersIntervalLength can be set to "900 seconds" or 1074 15 minutes and the number of consecutive intervals over which 1075 the maximum energy is calculated 1076 (eoEnergyParametersIntervalNumber) as "10". The sampling rate 1077 internal to the Energy Object for measurement of power usage 1078 (eoEnergyParametersSampleRate) can be "1000 milliseconds", as 1079 set by the Energy Object as a reasonable value. Then, the 1080 eoEnergyParametersStatus is set to active (value 1) to indicate 1081 that the Energy Object should start monitoring the usage per the 1082 eoEnergyTable. 1084 The indices for the eoEnergyTable are eoEnergyParametersIndex 1085 which identifies the index for the setting of energy measurement 1086 collection Energy Object, and eoEnergyCollectionStartTime, which 1087 denotes the start time of the energy measurement interval based 1088 on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the 1089 measured energy consumption over the time interval specified 1090 (eoEnergyParametersIntervalLength) based on the Energy Object 1091 internal sampling rate (eoEnergyParametersSampleRate). While 1092 choosing the values for the eoEnergyParametersIntervalLength and 1093 eoEnergyParametersSampleRate, it is recommended to take into 1094 consideration either the network element resources adequate to 1095 process and store the sample values, and the mechanism used to 1096 calculate the eoEnergyConsumed. The units are derived from 1097 eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be 1098 "100" with eoEnergyUnitMultiplier equal to 0, the measured 1099 energy consumption of the Energy Object is 100 watt-hours. The 1100 eoEnergyMaxConsumed is the maximum energy observed and that can 1101 be "150 watt-hours". 1103 The eoEnergyTable has a buffer to retain a certain number of 1104 intervals, as defined by eoEnergyParametersIntervalNumber. 1105 If the default value of "10" is kept, then the eoEnergyTable 1106 contains 10 energy measurements, including the maximum. 1108 Here is a brief explanation of how the maximum energy can be 1109 calculated. The first observed energy measurement value is 1110 taken to be the initial maximum. With each subsequent 1111 measurement, based on numerical comparison, maximum energy may 1112 be updated. The maximum value is retained as long as the 1113 measurements are taking place. Based on periodic polling of 1114 this table, an NMS could compute the maximum over a longer 1115 period, i.e. a month, 3 months, or a year. 1117 5.6. Fault Management 1119 [EMAN-REQ] specifies requirements about Power States such as 1120 "the current power state" , "the time of the last state change", 1121 "the total time spent in each state", "the number of transitions 1122 to each state" etc. Some of these requirements are fulfilled 1123 explicitly by MIB objects such as eoPowerOperState, 1124 eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the 1125 other requirements are met via the SNMP NOTIFICATION mechanism. 1126 eoPowerStateChange SNMP notification which is generated when the 1127 value(s) of ,eoPowerStateIndex, eoPowerOperState, 1128 eoPowerAdminState have changed. 1130 6. Discovery 1132 It is foreseen that most Energy Objects will require the 1133 implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a 1134 prerequisite for this MIB module. In such a case, eoPowerTable 1135 of the EMAN-MON-MIB is a sparse extension of the eoTable of 1136 ENERGY-AWARE-MIB. Every Energy Object MUST implement 1137 entPhysicalIndex, entPhysicalUUID and entPhysicalName from the 1138 ENTITY-MIB [EMAN-ENTITY]. As the primary index for the Energy 1139 Object, entPhysicalIndex is used. 1141 The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- 1142 MIB], if available, in order to discover all the Energy Objects 1143 and the relationships between those (notion of Parent/Child). 1144 In the ENERGY-AWARE-MIB module tables, the Energy Objects are 1145 indexed by the entPhysicalIndex. 1147 If an implementation of the ENERGY-AWARE-MIB module is available 1148 in the local SNMP context, for the same Energy Object, the 1149 entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The 1150 entPhysicalIndex characterizes the Energy Object in the 1151 energyObjectMib and the powerCharacteristicsMIB MIB modules 1152 (this document). 1154 From there, the NMS must poll the eoPowerStateTable (specified 1155 in the energyObjectMib module in this document), which 1156 enumerates, amongst other things, the maximum power usage. As 1157 the entries in eoPowerStateTable table are indexed by the 1158 Energy Object ( entPhysicalIndex), by the Power State Set 1159 (eoPowerStateIndex), the maximum power usage is discovered per 1160 Energy Object, and the power usage per Power State of the Power 1161 State Set. In other words, polling the eoPowerStateTable allows 1162 the discovery of each Power State within every Power State Set 1163 supported by the Energy Object. 1165 If the Energy Object is an Aggregator or a Proxy, the MIB module 1166 would be populated with the Energy Object Parent and Children 1167 information, which have their own Energy Object index value 1168 (entPhysicalIndex). However, the parent/child relationship must 1169 be discovered thanks to the ENERGY-AWARE-MIB module. 1171 Finally, the NMS can monitor the power characteristics thanks to 1172 the powerCharacteristicsMIB MIB module, which reuses the 1173 entPhysicalIndex to index the Energy Object. 1175 7. Link with the other IETF MIBs 1177 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 1179 RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the 1180 physical entities of a networking device (router, switch, etc.) 1181 and those physical entities indexed by entPhysicalIndex. From 1182 an energy-management standpoint, the physical entities that 1183 consume or produce energy are of interest. 1185 RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that 1186 provides a standardized way of obtaining information (current 1187 value of the sensor, operational status of the sensor, and the 1188 data units precision) from sensors embedded in networking 1189 devices. Sensors are associated with each index of 1190 entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus 1191 of the Power and Energy Monitoring MIB is on measurement of 1192 power usage of networking equipment indexed by the ENTITY-MIB, 1193 this MIB proposes a customized power scale for power measurement 1194 and different power state states of networking equipment, and 1195 functionality to configure the power state states. 1197 When this MIB module is used to monitor the power usage of 1198 devices like routers and switches, the ENTITY-MIB and ENTITY- 1199 SENSOR MIB SHOULD be implemented. In such cases, the Energy 1200 Objects are modeled by the entPhysicalIndex through the 1201 entPhysicalEntity MIB object specified in the eoTable in the 1202 ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. 1204 However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI 1205 C12.x accuracy classes required for electricity (i.e., 1%, 2%, 1206 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 1207 represents "The number of decimal places of precision in fixed- 1208 point sensor values returned by the associated entPhySensorValue 1209 object". The ANSI and IEC Standards are used for power 1210 measurement and these standards require that we use an accuracy 1211 class, not the scientific-number precision model specified in 1212 RFC3433. The eoPowerAccuracy MIB object models this accuracy. 1213 Note that eoPowerUnitMultipler represents the scale factor per 1214 IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], 1215 which is a more logical representation for power measurements 1216 (compared to entPhySensorScale), with the mantissa and the 1217 exponent values X * 10 ^ Y. 1219 Power measurements specifying the qualifier 'UNITS' for each 1220 measured value in watts are used in the LLDP-EXT-MED-MIB, POE 1222 [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier 1223 is used for the power measurement values. 1225 One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are 1226 implemented for all Energy Objects that need to be monitored. A 1227 typical example is a converged building gateway, monitoring 1228 several other devices in the building, doing the proxy between 1229 SNMP and a protocol like BACNET. Another example is the home 1230 energy controller. In such cases, the eoPhysicalEntity value 1231 contains the zero value, thanks to PhysicalIndexOrZero textual 1232 convention. 1234 The eoPower is similar to entPhySensorValue [RFC3433] and the 1235 eoPowerUnitMultipler is similar to entPhySensorScale. 1237 7.2. Link with the ENTITY-STATE MIB 1239 For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE 1240 MIB [RFC4268] specifies the operational states (entStateOper: 1241 unknown, enabled, disabled, testing), the alarm (entStateAlarm: 1242 unknown, underRepair, critical, major, minor, warning, 1243 indeterminate) and the possible values of standby states 1244 (entStateStandby: unknown, hotStandby, coldStandby, 1245 providingService). 1247 From a power monitoring point of view, in contrast to the entity 1248 operational states of entities, Power States are required, as 1249 proposed in the Power and Energy Monitoring MIB module. Those 1250 Power States can be mapped to the different operational states 1251 in the ENTITY-STATE MIB, if a formal mapping is required. For 1252 example, the entStateStandby "unknown", "hotStandby", 1253 "coldStandby", states could map to the Power State "unknown", 1254 "ready", "standby", respectively, while the entStateStandby 1255 "providingService" could map to any "low" to "high" Power State. 1257 7.3. Link with the POWER-OVER-ETHERNET MIB 1259 Power-over-Ethernet MIB [RFC3621] provides an energy monitoring 1260 and configuration framework for power over Ethernet devices. 1261 The RFC introduces a concept of a port group on a switch to 1262 define power monitoring and management policy and does not use 1263 the entPhysicalIndex as the index. Indeed, the 1264 pethMainPseConsumptionPower is indexed by the 1265 pethMainPseGroupIndex, which has no mapping with the 1266 entPhysicalIndex. 1268 One cannot assume that the Power-over-Ethernet MIB is 1269 implemented for all Energy Objects that need to be monitored. 1270 A typical example is a converged building gateway, monitoring 1271 several other devices in the building, doing the proxy between 1272 SNMP and a protocol like BACNET. Another example is the home 1273 energy controller. In such cases, the eoethPortIndex and 1274 eoethPortGrpIndex values contain the zero value, thanks to new 1275 PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero 1276 conventions. 1278 However, if the Power-over-Ethernet MIB [RFC3621] is supported, 1279 the Energy Object eoethPortIndex and eoethPortGrpIndex contain 1280 the pethPsePortIndex and pethPsePortGroupIndex, respectively. 1282 As a consequence, the entPhysicalIndex MIB object has been kept 1283 as the unique Energy Object index. 1285 Note that, even though the Power-over-Ethernet MIB [RFC3621] was 1286 created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse 1287 the precision notion from the ENTITY-SENSOR MIB, i.e. the 1288 entPhySensorPrecision MIB object. 1290 7.4. Link with the UPS MIB 1292 To protect against unexpected power disruption, data centers and 1293 buildings make use of Uninterruptible Power Supplies (UPS). To 1294 protect critical assets, a UPS can be restricted to a particular 1295 subset or domain of the network. UPS usage typically lasts only 1296 for a finite period of time, until normal power supply is 1297 restored. Planning is required to decide on the capacity of the 1298 UPS based on output power and duration of probable power outage. 1299 To properly provision UPS power in a data center or building, it 1300 is important to first understand the total demand required to 1301 support all the entities in the site. This demand can be 1302 assessed and monitored via the Power and Energy Monitoring MIB. 1304 UPS MIB [RFC1628] provides information on the state of the UPS 1305 network. Implementation of the UPS MIB is useful at the 1306 aggregate level of a data center or a building. The MIB module 1307 contains several groups of variables: 1309 - upsIdent: Identifies the UPS entity (name, model, etc.). 1311 - upsBattery group: Indicates the battery state 1312 (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) 1313 - upsInput group: Characterizes the input load to the UPS 1314 (number of input lines, voltage, current, etc.). 1316 - upsOutput: Characterizes the output from the UPS (number of 1317 output lines, voltage, current, etc.) 1319 - upsAlarms: Indicates the various alarm events. 1321 The measurement of power in the UPS MIB is in Volts, Amperes and 1322 Watts. The units of power measurement are RMS volts and RMS 1323 Amperes. They are not based on the EntitySensorDataScale and 1324 EntitySensorDataPrecision of ENTITY-SENSOR-MIB. 1326 Both the Power and Energy Monitoring MIB and the UPS MIB may be 1327 implemented on the same UPS SNMP agent, without conflict. In 1328 this case, the UPS device itself is the Energy Object Parent and 1329 any of the UPS meters or submeters are the Energy Object 1330 Children. 1332 7.5. Link with the LLDP and LLDP-MED MIBs 1334 The LLDP Protocol is a Data Link Layer protocol used by network 1335 devices to advertise their identities, capabilities, and 1336 interconnections on a LAN network. 1338 The Media Endpoint Discovery is an enhancement of LLDP, known as 1339 LLDP-MED. The LLDP-MED enhancements specifically address voice 1340 applications. LLDP-MED covers 6 basic areas: capability 1341 discovery, LAN speed and duplex discovery, network policy 1342 discovery, location identification discovery, inventory 1343 discovery, and power discovery. 1345 Of particular interest to the current MIB module is the power 1346 discovery, which allows the endpoint device (such as a PoE 1347 phone) to convey power requirements to the switch. In power 1348 discovery, LLDP-MED has four Type Length Values (TLVs): power 1349 type, power source, power priority and power value. 1350 Respectively, those TLVs provide information related to the type 1351 of power (power sourcing entity versus powered device), how the 1352 device is powered (from the line, from a backup source, from 1353 external power source, etc.), the power priority (how important 1354 is it that this device has power?), and how much power the 1355 device needs. 1357 The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 1358 actually comes from the Power-over-Ethernet MIB [RFC3621]. If 1359 the Power-over-Ethernet MIB [RFC3621] is supported, the exact 1360 value from the pethPsePortPowerPriority [RFC3621] is copied over 1361 in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise 1362 the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From 1363 the Power and Energy Monitoring MIB, it is possible to identify 1364 the pethPsePortPowerPriority [RFC3621], thanks to the 1365 eoethPortIndex and eoethPortGrpIndex. 1367 The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to 1368 eoPowerOrigin in indicating if the power for an attached device 1369 is local or from a remote device. If the LLDP-MED MIB is 1370 supported, the following mapping can be applied to the 1371 eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and 1372 local(3) can be mapped to remote(2) and self(1), respectively. 1374 8. Implementation Scenario 1376 This section provides an illustrative example scenario for the 1377 implementation of the Energy Object, including Energy Object 1378 Parent and Energy Object Child relationships. 1380 Example Scenario of a campus network: Switch with PoE Endpoints 1381 with further connected devices. 1383 The campus network consists of switches that provide LAN 1384 connectivity. The switch with PoE ports is located in wiring 1385 closet. PoE IP phones are connected to the switch. The IP 1386 phones draw power from the PoE ports of the switch. In 1387 addition, a PC is daisy-chained from the IP phone for LAN 1388 connectivity. 1390 The IP phone consumes power from the PoE switch, while the PC 1391 consumes power from the wall outlet. 1393 The switch has implementations of ENTITY-MIB [EMAN-ENTITY ] and 1394 ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have 1395 implementation of the ENTITY-MIB, but has an implementation of 1396 ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following 1397 attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID 1398 1000". The power usage of the switch is "440 Watts". The 1399 switch does not have an Energy Object Parent. 1401 The PoE switch port has the following attributes: The switch 1402 port has entPhysicalIndex "3", and entPhysicalUUID is "UUID 1403 1000:3". The power metered at the POE switch port is "12 1404 watts". In this example, the POE switch port has the switch as 1405 the Energy Object Parent, with its eoParentID of "1000". 1407 The attributes of the PC are given below. The PC does not have 1408 an entPhysicalIndex, and the entPhysicalUUID is "UUID 1000:57 ". 1409 The PC has an Energy Object Parent, i.e. the switch port whose 1410 entPhysicalUUID is "UUID 1000:3". The power usage of the PC is 1411 "120 Watts" and is communicated to the switch port. 1413 This example illustrates the important distinction between the 1414 Energy Object Children: The IP phone draws power from the 1415 switch, while the PC has LAN connectivity from the phone, but is 1416 powered from the wall outlet. However, the Energy Object Parent 1417 sends power control messages to both the Energy Object Children 1418 (IP phone and PC) and the Children react to those messages. 1420 |-------------------------------------------------------| 1421 | Switch | 1422 |=======================================================| 1423 | Switch | Switch | Switch | Switch | 1424 | entPhyIndx | UUID |eoParentId | eoPower | 1425 | ===================================================== | 1426 | 1 | UUID 1000 | null | 440 | 1427 | ===================================================== | 1428 | | 1429 | SWITCH PORT | 1430 | ===================================================== | 1431 | | Switch | Switch | Switch | Switch | 1432 | | Port | Port | Port | Port | 1433 | | entPhyIndx | UUID | eoParentId | eoPower | 1434 | ===================================================== | 1435 | | 3 | UUID 1000:3 | 1000 | 12 | 1436 | ======================================================| 1437 | ^ 1438 | | 1439 |-----------------------------------|------------------- 1440 | 1441 | 1442 POE IP PHONE | 1443 | 1444 | 1445 ====================================================== 1446 | IP phone | IP phone | IP phone | IP phone | 1447 | entPhyIndx | UUID | eoParentID | eoPower | 1448 ====================================================== 1449 | Null | UUID 1000:31| UUID 1000:3 | 12 | 1450 ======================================================= 1451 | 1452 | 1453 PC connected to switch via IP phone | 1454 | 1455 ===================================================== 1456 | PC | PC | PC | PC | 1457 |entPhyIndx | UUID | eoParentID | eoPower | 1458 ===================================================== 1459 | 7 | UUID 1000:57| UUID 1000:3 | 120 | 1460 ===================================================== 1462 Figure 1: Example scenario 1464 9. Structure of the MIB 1466 The primary MIB object in this MIB module is the 1467 energyObjectMibObject. The eoPowerTable table of 1468 energyObjectMibObject describes the power measurement attributes 1469 of an Energy Object entity. The notion of identity of the device 1470 in terms of uniquely identification of the Energy Object and its 1471 relationship to other entities in the network are addressed in 1472 [EMAN-AWARE-MIB]. 1474 Logically, this MIB module is a sparse extension of the 1475 [EMAN-AWARE-MIB] module. Thus the following requirements which 1476 are applied to [EMAN-AWARE-MIB] are also applicable. As a 1477 requirement for this MIB module, [EMAN-AWARE-MIB] should be 1478 implemented and as Module Compliance of ENTITY-MIB V4 [EMAN- 1479 ENTITY] with respect to entity4CRCompliance should be supported 1480 which requires 3 MIB objects (entPhysicalIndex, entPhysicalName 1481 and entPhysicalUUID ) MUST be implemented. 1483 eoMeterCapabilitiesTable is useful to enable applications to 1484 determine the capabilities supported by the local management 1485 agent. This table indicates the energy monitoring MIB groups 1486 that are supported by the local management system. By reading 1487 the value of this object, it is possible for applications to 1488 know which tables contain the information and are usable without 1489 walking through the table and querying every element which 1490 involves a trial-and-error process. 1492 The power measurement of an Energy Object contains information 1493 describing its power usage (eoPower) and its current power state 1494 (eoPowerOperState). In addition to power usage, additional 1495 information describing the units of measurement 1496 (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage 1497 measurement was obtained (eoPowerMeasurementCaliber), the 1498 source of power (eoPowerOrigin) and the type of power 1499 (eoPowerCurrentTtype) are described. 1501 An Energy Object may contain an optional eoPowerCharacteristics 1502 table that describes the electrical characteristics associated 1503 with the current power state and usage. 1505 An Energy Object may contain an optional eoEnergyTable to 1506 describe energy measurement information over time. 1508 An Energy Object may also contain optional battery information 1509 associated with this entity. 1511 10. MIB Definitions 1513 -- ************************************************************ 1514 -- 1515 -- 1516 -- This MIB is used to monitor power usage of network 1517 -- devices 1518 -- 1519 -- ************************************************************* 1521 ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN 1523 IMPORTS 1524 MODULE-IDENTITY, 1525 OBJECT-TYPE, 1526 NOTIFICATION-TYPE, 1527 mib-2, 1528 Integer32, Counter32, TimeTicks 1529 FROM SNMPv2-SMI 1530 TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval, 1531 TimeStamp 1532 FROM SNMPv2-TC 1533 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP 1534 FROM SNMPv2-CONF 1535 OwnerString 1536 FROM RMON-MIB 1537 entPhysicalIndex, PhysicalIndex 1538 FROM ENTITY-MIB; 1540 energyObjectMib MODULE-IDENTITY 1541 LAST-UPDATED "201210220000Z" -- 22 October 2012 1543 ORGANIZATION "IETF EMAN Working Group" 1544 CONTACT-INFO 1545 "WG charter: 1546 http://datatracker.ietf.org/wg/eman/charter/ 1548 Mailing Lists: 1549 General Discussion: eman@ietf.org 1551 To Subscribe: 1552 https://www.ietf.org/mailman/listinfo/eman 1554 Archive: 1555 http://www.ietf.org/mail-archive/web/eman 1557 Editors: 1558 Mouli Chandramouli 1559 Cisco Systems, Inc. 1560 Sarjapur Outer Ring Road 1561 Bangalore 560103 1562 IN 1563 Phone: +91 80 4429 2409 1564 Email: moulchan@cisco.com 1566 Brad Schoening 1567 44 Rivers Edge Drive 1568 Little Silver, NJ 07739 1569 US 1570 Email: brad.schoening@verizon.net 1572 Juergen Quittek 1573 NEC Europe Ltd. 1574 NEC Laboratories Europe 1575 Network Research Division 1576 Kurfuersten-Anlage 36 1577 Heidelberg 69115 1578 DE 1579 Phone: +49 6221 4342-115 1580 Email: quittek@neclab.eu 1582 Thomas Dietz 1583 NEC Europe Ltd. 1584 NEC Laboratories Europe 1585 Network Research Division 1586 Kurfuersten-Anlage 36 1587 69115 Heidelberg 1588 DE 1589 Phone: +49 6221 4342-128 1590 Email: Thomas.Dietz@nw.neclab.eu 1592 Benoit Claise 1593 Cisco Systems, Inc. 1594 De Kleetlaan 6a b1 1595 Degem 1831 1596 Belgium 1597 Phone: +32 2 704 5622 1598 Email: bclaise@cisco.com" 1600 DESCRIPTION 1601 "This MIB is used to monitor power and energy in 1602 devices. 1604 This table sparse extension of the eoTable 1605 from the ENERGY-AWARE-MIB. As a requirement 1606 [EMAN-AWARE-MIB] should be implemented. 1608 Module Compliance of ENTITY-MIB v4 1609 with respect to entity4CRCompliance should 1610 be supported which requires implementation 1611 of 3 MIB objects (entPhysicalIndex, 1612 entPhysicalName and entPhysicalUUID)." 1614 REVISION 1615 "201210220000Z" -- 22 October 2012 1617 DESCRIPTION 1618 "Initial version, published as RFC XXXX." 1620 ::= { mib-2 xxx } 1622 energyObjectMibNotifs OBJECT IDENTIFIER 1623 ::= { energyObjectMib 0 } 1625 energyObjectMibObjects OBJECT IDENTIFIER 1626 ::= { energyObjectMib 1 } 1628 energyObjectMibConform OBJECT IDENTIFIER 1629 ::= { energyObjectMib 2 } 1631 -- Textual Conventions 1633 IANAPowerStateSet ::= TEXTUAL-CONVENTION 1634 STATUS current 1635 DESCRIPTION 1637 "IANAPowerState is a textual convention that describes 1638 Power State Sets and Power State Set Values an Energy Object 1639 supports. IANA has created a registry of Power State supported 1640 by an Energy Object and IANA shall administer the list of Power 1641 State Sets and Power States. 1643 The textual convention assumes that power states in a power 1644 state set are limited to 255 distinct values. For a Power 1645 State Set S, the named number with the value S * 256 is 1646 allocated to indicate the power state set. For a Power State X 1647 in the Power State S, the named number with the value S * 256 1648 + X + 1 is allocated to represent the power state." 1650 REFERENCE 1651 "http://www.iana.org/assignments/eman 1652 RFC EDITOR NOTE: please change the previous URL if this is 1653 not the correct one after IANA assigned it." 1655 SYNTAX INTEGER { 1656 other(0), -- indicates other set 1657 unknown(255), -- unknown power state 1659 ieee1621(256), -- indicates IEEE1621 set 1660 ieee1621On(257), 1661 ieee1621Off(258), 1662 ieee1621Sleep(259), 1664 dmtf(512), -- indicates DMTF set 1665 dmtfOn(513), 1666 dmtfSleepLight(514), 1667 dmtfSleepDeep(515), 1668 dmtfOffHard(516), 1669 dmtfOffSoft(517), 1670 dmtfHibernate(518), 1671 dmtfPowerOffSoft(519), 1672 dmtfPowerOffHard(520), 1673 dmtfMasterBusReset(521), 1674 dmtfDiagnosticInterrapt(522), 1675 dmtfOffSoftGraceful(523), 1676 dmtfOffHardGraceful(524), 1677 dmtfMasterBusResetGraceful(525), 1678 dmtfPowerCycleOffSoftGraceful(526), 1679 dmtfPowerCycleHardGraceful(527), 1681 eman(1024), -- indicates EMAN set 1682 emanmechoff(1025), 1683 emansoftoff(1026), 1684 emanhibernate(1027), 1685 emansleep(1028), 1686 emanstandby(1029), 1687 emanready(1030), 1688 emanlowMinus(1031), 1689 emanlow(1032), 1690 emanmediumMinus(1033), 1691 emanmedium(1034), 1692 emanhighMinus(1035), 1693 emanhigh(1036) 1694 } 1696 UnitMultiplier ::= TEXTUAL-CONVENTION 1697 STATUS current 1698 DESCRIPTION 1699 "The Unit Multiplier is an integer value that represents 1700 the IEEE 61850 Annex A units multiplier associated with 1701 the integer units used to measure the power or energy. 1703 For example, when used with eoPowerUnitMultiplier, -3 1704 represents 10^-3 or milliwatts." 1705 REFERENCE 1706 "The International System of Units (SI), 1707 National Institute of Standards and Technology, 1708 Spec. Publ. 330, August 1991." 1709 SYNTAX INTEGER { 1710 yocto(-24), -- 10^-24 1711 zepto(-21), -- 10^-21 1712 atto(-18), -- 10^-18 1713 femto(-15), -- 10^-15 1714 pico(-12), -- 10^-12 1715 nano(-9), -- 10^-9 1716 micro(-6), -- 10^-6 1717 milli(-3), -- 10^-3 1718 units(0), -- 10^0 1719 kilo(3), -- 10^3 1720 mega(6), -- 10^6 1721 giga(9), -- 10^9 1722 tera(12), -- 10^12 1723 peta(15), -- 10^15 1724 exa(18), -- 10^18 1725 zetta(21), -- 10^21 1726 yotta(24) -- 10^24 1727 } 1729 -- Objects 1731 eoMeterCapabilitiesTable OBJECT-TYPE 1732 SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry 1733 MAX-ACCESS not-accessible 1734 STATUS current 1735 DESCRIPTION 1736 "This table is useful for helping applications determine the 1737 monitoring capabilities supported by the local management 1738 agents. It is possible for applications to know which tables 1739 are usable without going through a trial-and-error process." 1740 ::= { energyObjectMibObjects 1 } 1742 eoMeterCapabilitiesEntry OBJECT-TYPE 1743 SYNTAX EoMeterCapabilitiesEntry 1744 MAX-ACCESS not-accessible 1745 STATUS current 1746 DESCRIPTION 1747 "An entry describes the metering capability of an Energy 1748 Object." 1749 INDEX { entPhysicalIndex } 1750 ::= { eoMeterCapabilitiesTable 1 } 1752 EoMeterCapabilitiesEntry ::= SEQUENCE { 1753 eoMeterCapability BITS 1754 } 1756 eoMeterCapability OBJECT-TYPE 1757 SYNTAX BITS { 1758 none(0), 1759 powermetering(1), -- power measurement 1760 energymetering(2), -- energy measurement 1761 powercharacteristics(3) -- power characteristics 1762 } 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "An indication of the Energy monitoring capabilities supported 1767 by this agent. This object use a BITS syntax and indicate the 1768 MIB groups supported by the probe. By reading the value of this 1769 object, it is possible to determine the MIB tables supported. " 1770 ::= { eoMeterCapabilitiesEntry 1 } 1772 eoPowerTable OBJECT-TYPE 1773 SYNTAX SEQUENCE OF EoPowerEntry 1774 MAX-ACCESS not-accessible 1775 STATUS current 1776 DESCRIPTION 1777 "This table lists Energy Objects." 1778 ::= { energyObjectMibObjects 2 } 1780 eoPowerEntry OBJECT-TYPE 1781 SYNTAX EoPowerEntry 1782 MAX-ACCESS not-accessible 1783 STATUS current 1784 DESCRIPTION 1785 "An entry describes the power usage of an Energy Object." 1787 INDEX { entPhysicalIndex } 1788 ::= { eoPowerTable 1 } 1790 EoPowerEntry ::= SEQUENCE { 1792 eoPower Integer32, 1793 eoPowerNameplate Integer32, 1794 eoPowerUnitMultiplier UnitMultiplier, 1795 eoPowerAccuracy Integer32, 1796 eoPowerMeasurementCaliber INTEGER, 1797 eoPowerCurrentType INTEGER, 1798 eoPowerOrigin INTEGER, 1799 eoPowerAdminState IANAPowerStateSet, 1800 eoPowerOperState IANAPowerStateSet, 1801 eoPowerStateEnterReason OwnerString 1802 } 1804 eoPower OBJECT-TYPE 1805 SYNTAX Integer32 1806 UNITS "Watts" 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "This object indicates the power measured for the Energy 1811 Object. For alternating current, this value is obtained 1812 as an average over fixed number of AC cycles. . This 1813 value is specified in SI units of watts with the 1814 magnitude of watts (milliwatts, kilowatts, etc.) 1815 indicated separately in eoPowerUnitMultiplier. The 1816 accuracy of the measurement is specfied in 1817 eoPowerAccuracy. The direction of power flow is indicated 1818 by the sign on eoPower. If the Energy Object is consuming 1819 power, the eoPower value will be positive. If the Energy 1820 Object is producing power, the eoPower value will be 1821 negative. 1823 The eoPower MUST be less than or equal to the maximum 1824 power that can be consumed at the power state specified 1825 by eoPowerState. 1827 The eoPowerMeasurementCaliber object specifies how the 1828 usage value reported by eoPower was obtained. The eoPower 1829 value must report 0 if the eoPowerMeasurementCaliber is 1830 'unavailable'. For devices that can not measure or 1831 report power, this option can be used." 1832 ::= { eoPowerEntry 1 } 1834 eoPowerNameplate OBJECT-TYPE 1835 SYNTAX Integer32 1836 UNITS "Watts" 1837 MAX-ACCESS read-only 1838 STATUS current 1839 DESCRIPTION 1840 "This object indicates the rated maximum consumption for 1841 the fully populated Energy Object. The nameplate power 1842 requirements are the maximum power numbers and, in almost 1843 all cases, are well above the expected operational 1844 consumption. The eoPowerNameplate is widely used for 1845 power provisioning. This value is specified in either 1846 units of watts or voltage and current. The units are 1847 therefore SI watts or equivalent Volt-Amperes with the 1848 magnitude (milliwatts, kilowatts, etc.) indicated 1849 separately in eoPowerUnitMultiplier." 1850 ::= { eoPowerEntry 2 } 1852 eoPowerUnitMultiplier OBJECT-TYPE 1853 SYNTAX UnitMultiplier 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The magnitude of watts for the usage value in eoPower 1858 and eoPowerNameplate." 1859 ::= { eoPowerEntry 3 } 1861 eoPowerAccuracy OBJECT-TYPE 1862 SYNTAX Integer32 (0..10000) 1863 UNITS "hundredths of percent" 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION 1867 "This object indicates a percentage value, in 100ths of a 1868 percent, representing the assumed accuracy of the usage 1869 reported by eoPower. For example: The value 1010 means 1870 the reported usage is accurate to +/- 10.1 percent. This 1871 value is zero if the accuracy is unknown or not 1872 applicable based upon the measurement method. 1874 ANSI and IEC define the following accuracy classes for 1875 power measurement: 1876 IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. 1877 ANSI C12.20 class 0.2, 0.5" 1878 ::= { eoPowerEntry 4 } 1880 eoPowerMeasurementCaliber OBJECT-TYPE 1881 SYNTAX INTEGER { 1882 unavailable(1) , 1883 unknown(2), 1884 actual(3) , 1885 estimated(4), 1886 presumed(5) } 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "This object specifies how the usage value reported by 1891 eoPower was obtained: 1893 - unavailable(1): Indicates that the usage is not 1894 available. In such a case, the eoPower value must be 0 1895 for devices that can not measure or report power this 1896 option can be used. 1898 - unknown(2): Indicates that the way the usage was 1899 determined is unknown. In some cases, entities report 1900 aggregate power on behalf of another device. In such 1901 cases it is not known whether the usage reported is 1902 actual(2), estimated(3) or presumed (4). 1904 - actual(3): Indicates that the reported usage was 1905 measured by the entity through some hardware or direct 1906 physical means. The usage data reported is not presumed 1907 (4) or estimated (3) but the real apparent current energy 1908 consumption rate. 1910 - estimated(4): Indicates that the usage was not 1911 determined by physical measurement. The value is a 1912 derivation based upon the device type, state, and/or 1913 current utilization using some algorithm or heuristic. It 1914 is presumed that the entity's state and current 1915 configuration were used to compute the value. 1917 - presumed(5): Indicates that the usage was not 1918 determined by physical measurement, algorithm or 1919 derivation. The usage was reported based upon external 1920 tables, specifications, and/or model information. For 1921 example, a PC Model X draws 200W, while a PC Model Y 1922 draws 210W" 1924 ::= { eoPowerEntry 5 } 1926 eoPowerCurrentType OBJECT-TYPE 1927 SYNTAX INTEGER { 1928 ac(1), 1929 dc(2), 1930 unknown(3) 1931 } 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "This object indicates whether the eoUsage for the 1936 Energy Object reports alternative current AC(1), direct 1937 current DC(2), or that the current type is unknown(3)." 1938 ::= { eoPowerEntry 6 } 1940 eoPowerOrigin OBJECT-TYPE 1941 SYNTAX INTEGER { 1942 self (1), 1943 remote (2) 1944 } 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "This object indicates the source of power measurement 1949 and can be useful when modeling the power usage of 1950 attached devices. The power measurement can be performed 1951 by the entity itself or the power measurement of the 1952 entity can be reported by another trusted entity using a 1953 protocol extension. A value of self(1) indicates the 1954 measurement is performed by the entity, whereas remote(2) 1955 indicates that the measurement was performed by another 1956 entity." 1957 ::= { eoPowerEntry 7 } 1959 eoPowerAdminState OBJECT-TYPE 1960 SYNTAX IANAPowerStateSet 1961 MAX-ACCESS read-write 1962 STATUS current 1963 DESCRIPTION 1964 "This object specifies the desired Power State and the 1965 Power State Set for the Energy Object. Note that 1966 other(0) is not a Power State Set and unknown(255) is 1967 not a Power State as such, but simply an indication that 1968 the Power State of the Energy Object is unknown. 1969 Possible values of eoPowerAdminState within the Power 1970 State Set are registered at IANA. 1971 A current list of assignments can be found at 1972 1973 RFC-EDITOR: please check the location after IANA" 1974 ::= { eoPowerEntry 8 } 1976 eoPowerOperState OBJECT-TYPE 1977 SYNTAX IANAPowerStateSet 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1982 "This object specifies the current operational Power 1983 State and the Power State Set for the Energy Object. 1984 other(0) is not a Power State Set and unknown(255) is 1985 not a Power State as such, but simply an indication that 1986 the Power State of the Energy Object is unknown. 1988 Possible values of eoPowerAdminState within the Power 1989 State Set are registered at IANA. 1990 A current list of assignments can be found at 1991 1992 RFC-EDITOR: please check the location after IANA" 1994 ::= { eoPowerEntry 9 } 1996 eoPowerStateEnterReason OBJECT-TYPE 1997 SYNTAX OwnerString 1998 MAX-ACCESS read-create 1999 STATUS current 2000 DESCRIPTION 2001 "This string object describes the reason for the 2002 eoPowerAdminState 2003 transition Alternatively, this string may contain with 2004 the entity that configured this Energy Object to this 2005 Power State." 2006 DEFVAL { "" } 2007 ::= { eoPowerEntry 10 } 2009 eoPowerStateTable OBJECT-TYPE 2010 SYNTAX SEQUENCE OF EoPowerStateEntry 2011 MAX-ACCESS not-accessible 2012 STATUS current 2013 DESCRIPTION 2014 "This table enumerates the maximum power usage, in watts, 2015 for every single supported Power State of each Energy 2016 Object. 2018 This table has an expansion-dependent relationship on the 2019 eoPowerTable, containing rows describing each Power State 2020 for the corresponding Energy Object. For every Energy 2021 Object in the eoPowerTable, there is a corresponding 2022 entry in this table." 2023 ::= { energyObjectMibObjects 3 } 2025 eoPowerStateEntry OBJECT-TYPE 2026 SYNTAX EoPowerStateEntry 2027 MAX-ACCESS not-accessible 2028 STATUS current 2029 DESCRIPTION 2030 "A eoPowerStateEntry extends a corresponding 2031 eoPowerEntry. This entry displays max usage values at 2032 every single possible Power State supported by the Energy 2033 Object. 2034 For example, given the values of a Energy Object 2035 corresponding to a maximum usage of 11W at the 2036 state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High): 2038 State MaxUsage Units 2039 1 (mechoff 0 W 2040 2 (softoff) 0 W 2041 3 (hibernate) 0 W 2042 4 (sleep) 0 W 2043 5 (standby) 0 W 2044 6 (ready) 8 W 2045 7 (lowMinus) 8 W 2046 8 (low) 11 W 2047 9 (medimMinus) 11 W 2048 10 (medium) 11 W 2049 11 (highMinus) 11 W 2050 12 (high) 11 W 2052 Furthermore, this table extends to return the total time 2053 in each Power State, along with the number of times a 2054 particular Power State was entered." 2056 INDEX { entPhysicalIndex, 2057 eoPowerStateIndex 2058 } 2059 ::= { eoPowerStateTable 1 } 2061 EoPowerStateEntry ::= SEQUENCE { 2062 eoPowerStateIndex IANAPowerStateSet, 2063 eoPowerStateMaxPower Integer32, 2064 eoPowerStatePowerUnitMultiplier UnitMultiplier, 2065 eoPowerStateTotalTime TimeTicks, 2066 eoPowerStateEnterCount Counter32 2067 } 2069 eoPowerStateIndex OBJECT-TYPE 2070 SYNTAX IANAPowerStateSet 2071 MAX-ACCESS not-accessible 2072 STATUS current 2073 DESCRIPTION 2074 " 2075 This object specifies the index of the Power State of 2076 the Energy Object within a Power State Set. The 2077 semantics of the specific Power State can be obtained 2078 from the Power State Set definition." 2079 ::= { eoPowerStateEntry 1 } 2081 eoPowerStateMaxPower OBJECT-TYPE 2082 SYNTAX Integer32 2083 UNITS "Watts" 2084 MAX-ACCESS read-only 2085 STATUS current 2086 DESCRIPTION 2087 "This object indicates the maximum power for the Energy 2088 Object at the particular Power State. This value is 2089 specified in SI units of watts with the magnitude of the 2090 units (milliwatts, kilowatts, etc.) indicated separately 2091 in eoPowerStatePowerUnitMultiplier. If the maximum power 2092 is not known for a certain Power State, then the value is 2093 encoded as 0xFFFF. 2095 For Power States not enumerated, the value of 2096 eoPowerStateMaxPower might be interpolated by using the 2097 next highest supported Power State." 2098 ::= { eoPowerStateEntry 2 } 2100 eoPowerStatePowerUnitMultiplier OBJECT-TYPE 2101 SYNTAX UnitMultiplier 2102 MAX-ACCESS read-only 2103 STATUS current 2104 DESCRIPTION 2105 "The magnitude of watts for the usage value in 2106 eoPowerStateMaxPower." 2107 ::= { eoPowerStateEntry 3 } 2109 eoPowerStateTotalTime OBJECT-TYPE 2110 SYNTAX TimeTicks 2111 MAX-ACCESS read-only 2112 STATUS current 2113 DESCRIPTION 2114 "This object indicates the total time in hundreds 2115 of seconds that the Energy Object has been in this power 2116 state since the last reset, as specified in the 2117 sysUpTime." 2118 ::= { eoPowerStateEntry 4 } 2120 eoPowerStateEnterCount OBJECT-TYPE 2121 SYNTAX Counter32 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "This object indicates how often the Energy 2126 Object has 2127 entered this power state, since the last reset of the 2128 device as specified in the sysUpTime." 2129 ::= { eoPowerStateEntry 5 } 2131 eoEnergyParametersTable OBJECT-TYPE 2132 SYNTAX SEQUENCE OF EoEnergyParametersEntry 2133 MAX-ACCESS not-accessible 2134 STATUS current 2135 DESCRIPTION 2136 "This table is used to configure the parameters for 2137 Energy measurement collection in the table 2138 eoEnergyTable. This table allows the configuration of 2139 different measurement settings on the same Energy 2140 Object." 2141 ::= { energyObjectMibObjects 4 } 2143 eoEnergyParametersEntry OBJECT-TYPE 2144 SYNTAX EoEnergyParametersEntry 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "An entry controls an energy measurement in 2149 eoEnergyTable." 2150 INDEX { eoEnergyParametersIndex } 2151 ::= { eoEnergyParametersTable 1 } 2153 EoEnergyParametersEntry ::= SEQUENCE { 2154 eoEnergyObjectIndex PhysicalIndex, 2155 eoEnergyParametersIndex Integer32, 2156 eoEnergyParametersIntervalLength TimeInterval, 2157 eoEnergyParametersIntervalNumber Integer32, 2158 eoEnergyParametersIntervalMode Integer32, 2159 eoEnergyParametersIntervalWindow TimeInterval, 2160 eoEnergyParametersSampleRate Integer32, 2161 eoEnergyParametersStatus RowStatus 2162 } 2164 eoEnergyObjectIndex OBJECT-TYPE 2165 SYNTAX PhysicalIndex 2166 MAX-ACCESS read-create 2167 STATUS current 2168 DESCRIPTION 2169 "The unique value, to identify the specific Energy Object 2170 on which the measurement is applied, the same index used 2171 in the eoPowerTable to identify the Energy Object." 2172 ::= { eoEnergyParametersEntry 1 } 2174 eoEnergyParametersIndex OBJECT-TYPE 2175 SYNTAX Integer32 (0..2147483647) 2176 MAX-ACCESS read-create 2177 STATUS current 2178 DESCRIPTION 2179 "This object specifies the index of the Energy 2180 Parameters setting for collection of energy measurements 2181 for an Energy Object. An Energy Object can have multiple 2182 eoEnergyParametersIndex, depending on the capability of 2183 the Energy Object" 2184 ::= { eoEnergyParametersEntry 2 } 2186 eoEnergyParametersIntervalLength OBJECT-TYPE 2187 SYNTAX TimeInterval 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "This object indicates the length of time in hundredth of 2192 seconds over which to compute the average 2193 eoEnergyConsumed measurement in the eoEnergyTable table. 2194 The computation is based on the Energy Object's internal 2195 sampling rate of power consumed or produced by the Energy 2196 Object. The sampling rate is the rate at which the Energy 2197 Object can read the power usage and may differ based on 2198 device capabilities. The average energy consumption is 2199 then computed over the length of the interval." 2200 DEFVAL { 90000 } 2201 ::= { eoEnergyParametersEntry 3 } 2203 eoEnergyParametersIntervalNumber OBJECT-TYPE 2204 SYNTAX Integer32 2205 MAX-ACCESS read-create 2206 STATUS current 2207 DESCRIPTION 2209 "The number of intervals maintained in the eoEnergyTable. 2210 Each interval is characterized by a specific 2211 eoEnergyCollectionStartTime, used as an index to the 2212 table eoEnergyTable. Whenever the maximum number of 2213 entries is reached, the measurement over the new interval 2214 replacesthe oldest measurement. There is one exception to 2215 this rule: when the eoEnergyMaxConsumed and/or 2216 eoEnergyMaxProduced are in (one of) the two oldest 2217 measurement(s), they are left untouched and the next 2218 oldest measurement is replaced." 2219 DEFVAL { 10 } 2220 ::= { eoEnergyParametersEntry 4 } 2222 eoEnergyParametersIntervalMode OBJECT-TYPE 2223 SYNTAX INTEGER { 2224 period(1), 2225 sliding(2), 2226 total(3) 2227 } 2228 MAX-ACCESS read-create 2229 STATUS current 2230 DESCRIPTION 2231 "A control object to define the mode of interval calculation 2232 for the computation of the average eoEnergyConsumed or 2233 eoEnergyProduced measurement in the eoEnergyTable table. 2235 A mode of period(1) specifies non-overlapping periodic 2236 measurements. 2238 A mode of sliding(2) specifies overlapping sliding windows 2239 where the interval between the start of one interval and 2240 the next is defined in eoEnergyParametersIntervalWindow. 2242 A mode of total(3) specifies non-periodic measurement. In 2243 this mode only one interval is used as this is a 2244 continuous measurement since the last reset. The value of 2245 eoEnergyParametersIntervalNumber should be (1) one and 2246 eoEnergyParametersIntervalLength is ignored. " 2247 ::= { eoEnergyParametersEntry 5 } 2249 eoEnergyParametersIntervalWindow OBJECT-TYPE 2250 SYNTAX TimeInterval 2251 MAX-ACCESS read-create 2252 STATUS current 2253 DESCRIPTION 2254 "The length of the duration window between the starting 2255 time of one sliding window and the next starting time in 2256 hundredth of seconds, in order to compute the average of 2257 eoEnergyConsumed, eoEnergyProduced measurements in the 2258 eoEnergyTable table. This is valid only when the 2259 eoEnergyParametersIntervalMode is sliding(2). The 2260 eoEnergyParametersIntervalWindow value should be a multiple 2261 of eoEnergyParametersSampleRate." 2262 ::= { eoEnergyParametersEntry 6 } 2264 eoEnergyParametersSampleRate OBJECT-TYPE 2265 SYNTAX Integer32 2266 UNITS "Milliseconds" 2267 MAX-ACCESS read-create 2268 STATUS current 2269 DESCRIPTION 2270 "The sampling rate, in milliseconds, at which the Energy 2271 Object should poll power usage in order to compute the 2272 average eoEnergyConsumed, eoEnergyProduced measurements 2273 in the table eoEnergyTable. The Energy Object should 2274 initially set this sampling rate to a reasonable value, 2275 i.e., a compromise between intervals that will provide 2276 good accuracy by not being too long, but not so short 2277 that they affect the Energy Object performance by 2278 requesting continuous polling. If the sampling rate is 2279 unknown, the value 0 is reported. The sampling rate 2280 should be selected so that 2281 eoEnergyParametersIntervalWindow is a multiple of 2282 eoEnergyParametersSampleRate." 2284 DEFVAL { 1000 } 2285 ::= { eoEnergyParametersEntry 7 } 2287 eoEnergyParametersStatus OBJECT-TYPE 2288 SYNTAX RowStatus 2289 MAX-ACCESS read-create 2290 STATUS current 2291 DESCRIPTION 2292 "The status of this row. The eoEnergyParametersStatus is 2293 used to start or stop energy usage logging. An entry 2294 status may not be active(1) unless all objects in the 2295 entry have an appropriate value. If this object is not 2296 equal to active(1), all associated usage-data logged into 2297 the eoEnergyTable will be deleted. The data can be 2298 destroyed by setting up the eoEnergyParametersStatus to 2299 destroy(2)." 2300 ::= {eoEnergyParametersEntry 8 } 2302 eoEnergyTable OBJECT-TYPE 2303 SYNTAX SEQUENCE OF EoEnergyEntry 2304 MAX-ACCESS not-accessible 2305 STATUS current 2306 DESCRIPTION 2307 "This table lists Energy Object energy measurements. 2308 Entries in this table are only created if the 2309 corresponding value of object eoPowerMeasurementCaliber 2310 is active(2), i.e., if the power is actually metered." 2311 ::= { energyObjectMibObjects 5 } 2313 eoEnergyEntry OBJECT-TYPE 2314 SYNTAX EoEnergyEntry 2315 MAX-ACCESS not-accessible 2316 STATUS current 2317 DESCRIPTION 2318 "An entry describing energy measurements." 2319 INDEX { eoEnergyParametersIndex, 2320 eoEnergyCollectionStartTime } 2321 ::= { eoEnergyTable 1 } 2323 EoEnergyEntry ::= SEQUENCE { 2324 eoEnergyCollectionStartTime TimeTicks, 2325 eoEnergyConsumed Integer32, 2326 eoEnergyProduced Integer32, 2327 eoEnergyNet Integer32, 2328 eoEnergyUnitMultiplier UnitMultiplier, 2329 eoEnergyAccuracy Integer32, 2330 eoEnergyMaxConsumed Integer32, 2331 eoEnergyMaxProduced Integer32, 2332 eoEnergyDiscontinuityTime TimeStamp 2333 } 2335 eoEnergyCollectionStartTime OBJECT-TYPE 2336 SYNTAX TimeTicks 2337 UNITS "hundredths of seconds" 2338 MAX-ACCESS not-accessible 2339 STATUS current 2340 DESCRIPTION 2341 "The time (in hundredths of a second) since the 2342 network management portion of the system was last 2343 re-initialized, as specified in the sysUpTime [RFC3418]. 2344 This object is useful for reference of interval periods 2345 for which the energy is measured." 2346 ::= { eoEnergyEntry 1 } 2348 eoEnergyConsumed OBJECT-TYPE 2349 SYNTAX Integer32 2350 UNITS "Watt-hours" 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "This object indicates the energy consumed in units of watt- 2355 hours for the Energy Object over the defined interval. 2356 This value is specified in the common billing units of watt- 2357 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2358 indicated separately in eoEnergyUnitMultiplier." 2359 ::= { eoEnergyEntry 2 } 2361 eoEnergyProduced OBJECT-TYPE 2362 SYNTAX Integer32 2363 UNITS "Watt-hours" 2364 MAX-ACCESS read-only 2365 STATUS current 2366 DESCRIPTION 2367 "This object indicates the energy produced in units of watt- 2368 hours for the Energy Object over the defined interval. 2369 This value is specified in the common billing units of watt- 2370 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2371 indicated separately in eoEnergyUnitMultiplier." 2372 ::= { eoEnergyEntry 3 } 2374 eoEnergyNet OBJECT-TYPE 2375 SYNTAX Integer32 2376 UNITS "Watt-hours" 2377 MAX-ACCESS read-only 2378 STATUS current 2379 DESCRIPTION 2380 "This object indicates the resultant of the energy consumed and 2381 energy produced for an energy object in units of watt-hours for 2382 the Energy Object over the defined interval. This value is 2383 specified in the common billing units of watt-hours 2384 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2385 indicated separately in eoEnergyUnitMultiplier." 2386 ::= { eoEnergyEntry 4 } 2388 eoEnergyUnitMultiplier OBJECT-TYPE 2389 SYNTAX UnitMultiplier 2390 MAX-ACCESS read-only 2391 STATUS current 2392 DESCRIPTION 2393 "This object is the magnitude of watt-hours for the 2394 energy field in eoEnergyConsumed, eoEnergyProduced, 2395 eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced 2396 ." 2397 ::= { eoEnergyEntry 5 } 2399 eoEnergyAccuracy OBJECT-TYPE 2400 SYNTAX Integer32 (0..10000) 2401 UNITS "hundredths of percent" 2402 MAX-ACCESS read-only 2403 STATUS current 2404 DESCRIPTION 2405 "This object indicates a percentage value, in 100ths of a 2406 percent, representing the presumed accuracy of Energy usage 2407 reporting. eoEnergyAccuracy is applicable to all Energy 2408 measurements in the eoEnergyTable. 2410 For example: 1010 means the reported usage is accurate to +/- 2411 10.1 percent. 2412 This value is zero if the accuracy is unknown." 2414 ::= { eoEnergyEntry 6 } 2416 eoEnergyMaxConsumed OBJECT-TYPE 2417 SYNTAX Integer32 2418 UNITS "Watt-hours" 2419 MAX-ACCESS read-only 2420 STATUS current 2421 DESCRIPTION 2422 "This object is the maximum energy ever observed in 2423 eoEnergyConsumed since the monitoring started. This value 2424 is specified in the common billing units of watt-hours 2425 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2426 indicated separately in eoEnergyUnitMultiplier." 2427 ::= { eoEnergyEntry 7 } 2429 eoEnergyMaxProduced OBJECT-TYPE 2430 SYNTAX Integer32 2431 UNITS "Watt-hours" 2432 MAX-ACCESS read-only 2433 STATUS current 2434 DESCRIPTION 2435 "This object is the maximum energy ever observed in 2436 eoEnergyEnergyProduced since the monitoring started. This 2437 value is specified in the units of watt-hours with the 2438 magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated 2439 separately in eoEnergyEnergyUnitMultiplier." 2440 ::= { eoEnergyEntry 8 } 2442 eoEnergyDiscontinuityTime OBJECT-TYPE 2443 SYNTAX TimeStamp 2444 MAX-ACCESS read-only 2445 STATUS current 2446 DESCRIPTION 2448 "The value of sysUpTime [RFC3418] on the most recent 2449 occasion at which any one or more of this entity's energy 2450 counters in this table suffered a discontinuity: 2451 eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no 2452 such discontinuities have occurred since the last re- 2453 initialization of the local management subsystem, then 2454 this object contains a zero value." 2455 ::= { eoEnergyEntry 9 } 2457 -- Notifications 2459 eoPowerStateChange NOTIFICATION-TYPE 2460 OBJECTS {eoPowerAdminState, eoPowerOperState, 2461 eoPowerStateEnterReason} 2462 STATUS current 2463 DESCRIPTION 2464 "The SNMP entity generates the eoPowerStateChange when 2465 the value(s) of eoPowerAdminState or eoPowerOperState, 2466 in the context of the Power State Set, have changed for 2467 the Energy Object represented by the entPhysicalIndex." 2469 ::= { energyObjectMibNotifs 1 } 2471 -- Conformance 2473 energyObjectMibCompliances OBJECT IDENTIFIER 2474 ::= { energyObjectMib 3 } 2476 energyObjectMibGroups OBJECT IDENTIFIER 2477 ::= { energyObjectMib 4 } 2479 energyObjectMibFullCompliance MODULE-COMPLIANCE 2480 STATUS current 2481 DESCRIPTION 2482 "When this MIB is implemented with support for 2483 read-create, then such an implementation can 2484 claim full compliance. Such devices can then 2485 be both monitored and configured with this MIB. 2487 Module Compliance of [EMAN-ENTITY] 2488 with respect to entity4CRCompliance should 2489 be supported which requires implementation 2490 of 3 MIB objects (entPhysicalIndex, 2491 entPhysicalName and entPhysicalUUID)." 2493 MODULE -- this module 2494 MANDATORY-GROUPS { 2495 energyObjectMibTableGroup, 2496 energyObjectMibStateTableGroup, 2497 energyObjectMibNotifGroup 2498 } 2500 GROUP energyObjectMibEnergyTableGroup 2502 DESCRIPTION "A compliant implementation does not 2503 have to implement. 2505 Module Compliance of [EMAN-ENTITY] 2506 with respect to entity4CRCompliance should 2507 be supported which requires implementation 2508 of 3 MIB objects (entPhysicalIndex, 2509 entPhysicalName and entPhysicalUUID)." 2511 GROUP energyObjectMibEnergyParametersTableGroup 2513 DESCRIPTION "A compliant implementation does not 2514 have to implement. 2516 Module Compliance of {EMAN-ENTITY] 2517 with respect to entity4CRCompliance should 2518 be supported which requires implementation 2519 of 3 MIB objects (entPhysicalIndex, 2520 entPhysicalName and entPhysicalUUID)." 2522 GROUP energyObjectMibMeterCapabilitiesTableGroup 2524 DESCRIPTION "A compliant implementation does not 2525 have to implement. 2527 Module Compliance of [EMAN-ENTITY] 2528 with respect to entity4CRCompliance should 2529 be supported which requires implementation 2530 of 3 MIB objects (entPhysicalIndex, 2531 entPhysicalName and entPhysicalUUID)." 2533 ::= { energyObjectMibCompliances 1 } 2535 energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE 2536 STATUS current 2537 DESCRIPTION 2538 "When this MIB is implemented without support for 2539 read-create (i.e. in read-only mode), then such an 2540 implementation can claim read-only compliance. Such a 2541 device can then be monitored but cannot be 2542 configured with this MIB. 2544 Module Compliance of [EMAN-ENTITY] 2545 with respect to entity4CRCompliance should 2546 be supported which requires implementation 2547 of 3 MIB objects (entPhysicalIndex, 2548 entPhysicalName and entPhysicalUUID)." 2550 MODULE -- this module 2551 MANDATORY-GROUPS { 2552 energyObjectMibTableGroup, 2553 energyObjectMibStateTableGroup, 2554 energyObjectMibNotifGroup 2555 } 2557 OBJECT eoPowerOperState 2558 MIN-ACCESS read-only 2559 DESCRIPTION 2560 "Write access is not required." 2562 ::= { energyObjectMibCompliances 2 } 2564 -- Units of Conformance 2566 energyObjectMibTableGroup OBJECT-GROUP 2567 OBJECTS { 2568 eoPower, 2569 eoPowerNameplate, 2570 eoPowerUnitMultiplier, 2571 eoPowerAccuracy, 2572 eoPowerMeasurementCaliber, 2573 eoPowerCurrentType, 2574 eoPowerOrigin, 2575 eoPowerAdminState, 2576 eoPowerOperState, 2577 eoPowerStateEnterReason 2578 } 2579 STATUS current 2580 DESCRIPTION 2581 "This group contains the collection of all the objects 2582 related to the Energy Object." 2583 ::= { energyObjectMibGroups 1 } 2585 energyObjectMibStateTableGroup OBJECT-GROUP 2586 OBJECTS { 2587 eoPowerStateMaxPower, 2588 eoPowerStatePowerUnitMultiplier, 2589 eoPowerStateTotalTime, 2590 eoPowerStateEnterCount 2591 } 2592 STATUS current 2593 DESCRIPTION 2594 "This group contains the collection of all the 2595 objects related to the Power State." 2596 ::= { energyObjectMibGroups 2 } 2598 energyObjectMibEnergyParametersTableGroup OBJECT-GROUP 2599 OBJECTS { 2600 eoEnergyObjectIndex, 2601 eoEnergyParametersIndex, 2602 eoEnergyParametersIntervalLength, 2603 eoEnergyParametersIntervalNumber, 2604 eoEnergyParametersIntervalMode, 2605 eoEnergyParametersIntervalWindow, 2606 eoEnergyParametersSampleRate, 2607 eoEnergyParametersStatus 2609 } 2610 STATUS current 2611 DESCRIPTION 2612 "This group contains the collection of all the objects 2613 related to the configuration of the Energy Table." 2614 ::= { energyObjectMibGroups 3 } 2616 energyObjectMibEnergyTableGroup OBJECT-GROUP 2617 OBJECTS { 2618 -- Note that object 2619 -- eoEnergyCollectionStartTime is not 2620 -- included since it is not-accessible 2622 eoEnergyConsumed, 2623 eoEnergyProduced, 2624 eoEnergyNet, 2625 eoEnergyUnitMultiplier, 2626 eoEnergyAccuracy, 2627 eoEnergyMaxConsumed, 2628 eoEnergyMaxProduced, 2629 eoEnergyDiscontinuityTime 2630 } 2631 STATUS current 2632 DESCRIPTION 2633 "This group contains the collection of all the objects 2634 related to the Energy Table." 2635 ::= { energyObjectMibGroups 4 } 2637 energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP 2638 OBJECTS { 2639 eoMeterCapability 2640 } 2641 STATUS current 2642 DESCRIPTION 2643 "This group contains the object indicating the 2644 capability of the Energy Object" 2645 ::= { energyObjectMibGroups 5 } 2647 energyObjectMibNotifGroup NOTIFICATION-GROUP 2648 NOTIFICATIONS { 2649 eoPowerStateChange 2650 } 2651 STATUS current 2652 DESCRIPTION 2653 "This group contains the notifications for the power and 2654 energy monitoring MIB Module." 2656 ::= { energyObjectMibGroups 6 } 2658 END 2660 -- ************************************************************ 2661 -- 2662 -- This MIB module is used to monitor power characteristics of 2663 -- networked devices with measurements. 2664 -- 2665 -- This MIB module is an extension of energyObjectMib module. 2666 -- 2667 -- ************************************************************* 2669 POWER-CHARACTERISTICS-MIB DEFINITIONS ::= BEGIN 2671 IMPORTS 2672 MODULE-IDENTITY, 2673 OBJECT-TYPE, 2674 mib-2, 2675 Integer32 2676 FROM SNMPv2-SMI 2677 MODULE-COMPLIANCE, 2678 OBJECT-GROUP 2679 FROM SNMPv2-CONF 2680 UnitMultiplier 2681 FROM ENERGY-OBJECT-MIB 2682 OwnerString 2683 FROM RMON-MIB 2684 entPhysicalIndex 2685 FROM ENTITY-MIB; 2687 powerCharacteristicsMIB MODULE-IDENTITY 2689 LAST-UPDATED "201210220000Z" -- 22 October 2012 2691 ORGANIZATION "IETF EMAN Working Group" 2692 CONTACT-INFO 2693 "WG charter: 2694 http://datatracker.ietf.org/wg/eman/charter/ 2696 Mailing Lists: 2697 General Discussion: eman@ietf.org 2699 To Subscribe: 2700 https://www.ietf.org/mailman/listinfo/eman 2701 Archive: 2702 http://www.ietf.org/mail-archive/web/eman 2704 Editors: 2706 Mouli Chandramouli 2707 Cisco Systems, Inc. 2708 Sarjapur Outer Ring Road 2709 Bangalore 560103 2710 IN 2711 Phone: +91 80 4429 2409 2712 Email: moulchan@cisco.com 2714 Brad Schoening 2715 44 Rivers Edge Drive 2716 Little Silver, NJ 07739 2717 US 2718 Email: brad.schoening@verizon.net 2720 Juergen Quittek 2721 NEC Europe Ltd. 2722 NEC Laboratories Europe 2723 Network Research Division 2724 Kurfuersten-Anlage 36 2725 Heidelberg 69115 2726 DE 2727 Phone: +49 6221 4342-115 2728 Email: quittek@neclab.eu 2730 Thomas Dietz 2731 NEC Europe Ltd. 2732 NEC Laboratories Europe 2733 Network Research Division 2734 Kurfuersten-Anlage 36 2735 69115 Heidelberg 2736 DE 2737 Phone: +49 6221 4342-128 2738 Email: Thomas.Dietz@nw.neclab.eu 2740 Benoit Claise 2741 Cisco Systems, Inc. 2742 De Kleetlaan 6a b1 2743 Degem 1831 2744 Belgium 2745 Phone: +32 2 704 5622 2746 Email: bclaise@cisco.com" 2748 DESCRIPTION 2749 "This MIB is used to report AC power characteristics 2750 in devices. The table is a sparse augmentation of 2751 the eoPowerTable table from the energyObjectMib 2752 module. Both three-phase and single-phase power 2753 configurations are supported. 2755 As a requirement for this MIB module, 2756 [EMAN-AWARE-MIB] should be implemented. 2758 Module Compliance of ENTITY-MIB v4 2759 with respect to entity4CRCompliance should 2760 be supported which requires implementation 2761 of 3 MIB objects (entPhysicalIndex, 2762 entPhysicalName and entPhysicalUUID)." 2764 REVISION 2766 "201210220000Z" -- 22 October 2012 2768 DESCRIPTION 2769 "Initial version, published as RFC YYY." 2771 ::= { mib-2 yyy } 2773 powerCharacteristicsMIBConform OBJECT IDENTIFIER 2774 ::= { powerCharacteristicsMIB 0 } 2776 powerCharacteristicsMIBObjects OBJECT IDENTIFIER 2777 ::= { powerCharacteristicsMIB 1 } 2779 -- Objects 2781 eoACPwrCharacteristicsTable OBJECT-TYPE 2782 SYNTAX SEQUENCE OF EoACPwrCharacteristicsEntry 2783 MAX-ACCESS not-accessible 2784 STATUS current 2785 DESCRIPTION 2786 "This table defines power characteristics measurements 2787 for supported entPhysicalIndex entities. It is a sparse 2788 extension of the eoPowerTable." 2789 ::= { powerCharacteristicsMIBObjects 1 } 2791 eoACPwrCharacteristicsEntry OBJECT-TYPE 2792 SYNTAX EoACPwrCharacteristicsEntry 2793 MAX-ACCESS not-accessible 2794 STATUS current 2795 DESCRIPTION 2796 "This is a sparse extension of the eoPowerTable with 2797 entries for power characteristics measurements or 2798 configuration. Each measured value corresponds to an 2799 attribute in IEC 61850-7-4 for non-phase measurements 2800 within the object MMUX." 2802 INDEX {entPhysicalIndex } 2803 ::= { eoACPwrCharacteristicsTable 1 } 2805 EoACPwrCharacteristicsEntry ::= SEQUENCE { 2806 eoACPwrCharacteristicsConfiguration INTEGER, 2807 eoACPwrCharacteristicsAvgVoltage Integer32, 2808 eoACPwrCharacteristicsAvgCurrent Integer32, 2809 eoACPwrCharacteristicsFrequency Integer32, 2810 eoACPwrCharacteristicsPowerUnitMultiplier UnitMultiplier, 2811 eoACPwrCharacteristicsPowerAccuracy Integer32, 2812 eoACPwrCharacteristicsTotalActivePower Integer32, 2813 eoACPwrCharacteristicsTotalReactivePower Integer32, 2814 eoACPwrCharacteristicsTotalApparentPower Integer32, 2815 eoACPwrCharacteristicsTotalPowerFactor Integer32, 2816 eoACPwrCharacteristicsThdAmpheres Integer32, 2817 eoACPwrCharacteristicsThdVoltage Integer32 2818 } 2820 eoACPwrCharacteristicsConfiguration OBJECT-TYPE 2821 SYNTAX INTEGER { 2822 sngl(1), 2823 del(2), 2824 wye(3) 2825 } 2826 MAX-ACCESS read-only 2827 STATUS current 2828 DESCRIPTION 2829 "Configuration describes the physical configurations 2830 of the power supply lines: 2832 * alternating current, single phase (SNGL) 2833 * alternating current, three phase delta (DEL) 2834 * alternating current, three phase Y (WYE) 2836 Three-phase configurations can be either connected in 2837 a triangular delta (DEL) or star Y (WYE) system. WYE 2838 systems have a shared neutral voltage, while DEL 2839 systems do not. Each phase is offset 120 degrees to 2840 each other." 2842 ::= { eoACPwrCharacteristicsEntry 1 } 2844 eoACPwrCharacteristicsAvgVoltage OBJECT-TYPE 2845 SYNTAX Integer32 2846 UNITS "0.1 Volt AC" 2847 MAX-ACCESS read-only 2848 STATUS current 2849 DESCRIPTION 2850 "A measured value for average of the voltage measured 2851 over an integral number of AC cycles For a 3-phase 2852 system, this is the average voltage (V1+V2+V3)/3. IEC 2853 61850-7-4 measured value attribute 'Vol'" 2854 ::= { eoACPwrCharacteristicsEntry 2 } 2856 eoACPwrCharacteristicsAvgCurrent OBJECT-TYPE 2857 SYNTAX Integer32 2858 UNITS "Ampheres" 2859 MAX-ACCESS read-only 2860 STATUS current 2861 DESCRIPTION 2862 "A measured value of the current per phase. IEC 61850- 2863 7-4 attribute 'Amp'" 2864 ::= { eoACPwrCharacteristicsEntry 3 } 2866 eoACPwrCharacteristicsFrequency OBJECT-TYPE 2867 SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz 2868 UNITS "hertz" 2869 MAX-ACCESS read-only 2870 STATUS current 2871 DESCRIPTION 2872 "A measured value for the basic frequency of the AC 2873 circuit. IEC 61850-7-4 attribute 'Hz'." 2874 ::= { eoACPwrCharacteristicsEntry 4 } 2876 eoACPwrCharacteristicsPowerUnitMultiplier OBJECT-TYPE 2877 SYNTAX UnitMultiplier 2878 MAX-ACCESS read-only 2879 STATUS current 2880 DESCRIPTION 2881 "The magnitude of watts for the usage value in 2882 eoACPwrCharacteristicsTotalActivePower, 2883 eoACPwrCharacteristicsTotalReactivePower 2884 and eoACPwrCharacteristicsTotalApparentPower 2885 measurements. 2886 For 3-phase power systems, this will also include 2887 eoACPwrCharacteristicsPhaseActivePower, 2888 eoACPwrCharacteristicsPhaseReactivePower and 2889 eoACPwrCharacteristicsPhaseApparentPower" 2891 ::= { eoACPwrCharacteristicsEntry 5 } 2893 eoACPwrCharacteristicsPowerAccuracy OBJECT-TYPE 2894 SYNTAX Integer32 (0..10000) 2895 UNITS "hundredths of percent" 2896 MAX-ACCESS read-only 2897 STATUS current 2898 DESCRIPTION 2899 "This object indicates a percentage value, in 100ths of 2900 a percent, representing the presumed accuracy of 2901 active, reactive, and apparent power usage reporting. 2902 For example: 1010 means the reported usage is accurate 2903 to +/- 10.1 percent. This value is zero if the 2904 accuracy is unknown. 2906 ANSI and IEC define the following accuracy classes for 2907 power measurement: IEC 62053-22 & 60044-1 class 0.1, 2908 0.2, 0.5, 1 & 3. 2909 ANSI C12.20 class 0.2 & 0.5" 2910 ::= { eoACPwrCharacteristicsEntry 6 } 2912 eoACPwrCharacteristicsTotalActivePower OBJECT-TYPE 2913 SYNTAX Integer32 2914 UNITS " watts" 2915 MAX-ACCESS read-only 2916 STATUS current 2917 DESCRIPTION 2918 "A measured value of the actual power delivered to or 2919 consumed by the load. IEC 61850-7-4 attribute 'TotW'." 2920 ::= { eoACPwrCharacteristicsEntry 7 } 2922 eoACPwrCharacteristicsTotalReactivePower OBJECT-TYPE 2923 SYNTAX Integer32 2924 UNITS "volt-amperes reactive" 2925 MAX-ACCESS read-only 2926 STATUS current 2927 DESCRIPTION 2928 "A mesured value of the reactive portion of the 2929 apparent power. IEC 61850-7-4 attribute 'TotVAr'." 2930 ::= { eoACPwrCharacteristicsEntry 8 } 2932 eoACPwrCharacteristicsTotalApparentPower OBJECT-TYPE 2933 SYNTAX Integer32 2934 UNITS "volt-amperes" 2935 MAX-ACCESS read-only 2936 STATUS current 2937 DESCRIPTION 2938 "A measured value of the voltage and current which 2939 determines the apparent power. The apparent power is 2940 the vector sum of real and reactive power. 2942 Note: watts and volt-ampheres are equivalent units and 2943 may be combined. IEC 61850-7-4 attribute 'TotVA'." 2944 ::= { eoACPwrCharacteristicsEntry 9 } 2946 eoACPwrCharacteristicsTotalPowerFactor OBJECT-TYPE 2947 SYNTAX Integer32 (-10000..10000) 2948 UNITS "hundredths of percent" 2949 MAX-ACCESS read-only 2950 STATUS current 2951 DESCRIPTION 2952 "A measured value ratio of the real power flowing to 2953 the load versus the apparent power. It is dimensionless 2954 and expressed here as a percentage value in 100ths of a 2955 percent. A power factor of 100% indicates there is no 2956 inductance load and thus no reactive power. Power 2957 Factor can be positive or negative, where the sign 2958 should be in lead/lag (IEEE) form. IEC 61850-7-4 2959 attribute 'TotPF'." 2960 ::= { eoACPwrCharacteristicsEntry 10 } 2962 eoACPwrCharacteristicsThdAmpheres OBJECT-TYPE 2963 SYNTAX Integer32 (0..10000) 2964 UNITS "hundredths of percent" 2965 MAX-ACCESS read-only 2966 STATUS current 2967 DESCRIPTION 2968 "A calculated value for the current total harmonic 2969 distortion (THD). Method of calculation is not 2970 specified. IEC 61850-7-4 attribute 'ThdAmp'." 2971 ::= { eoACPwrCharacteristicsEntry 11 } 2973 eoACPwrCharacteristicsThdVoltage OBJECT-TYPE 2974 SYNTAX Integer32 (0..10000) 2975 UNITS "hundredths of percent" 2976 MAX-ACCESS read-only 2977 STATUS current 2978 DESCRIPTION 2979 "A calculated value for the voltage total harmonic 2980 distortion (THD). Method of calculation is not 2981 specified. IEC 61850-7-4 attribute 'ThdVol'." 2982 ::= { eoACPwrCharacteristicsEntry 12 } 2984 eoACPwrCharacteristicsPhaseTable OBJECT-TYPE 2985 SYNTAX SEQUENCE OF EoACPwrCharacteristicsPhaseEntry 2986 MAX-ACCESS not-accessible 2987 STATUS current 2988 DESCRIPTION 2989 "This table describes 3-phase power characteristics 2990 measurements. It is a sparse extension of the 2991 eoACPwrCharacteristicsTable." 2992 ::= { powerCharacteristicsMIBObjects 2 } 2994 eoACPwrCharacteristicsPhaseEntry OBJECT-TYPE 2995 SYNTAX EoACPwrCharacteristicsPhaseEntry 2996 MAX-ACCESS not-accessible 2997 STATUS current 2998 DESCRIPTION 2999 "An entry describes common 3-phase power 3000 characteristics measurements. 3002 This optional table describes 3-phase power 3003 characteristics measurements, with three entries for 3004 each supported entPhysicalIndex entity. Entities 3005 having single phase power shall not have any entities. 3007 This table describes attributes common to both WYE and 3008 DEL. Entities having single phase power shall not have 3009 any entries here. It is a sparse extension of the 3010 eoACPwrCharacteristicsTable. 3012 These attributes correspond to IEC 61850-7.4 MMXU phase 3013 measurements." 3014 INDEX { entPhysicalIndex, eoPhaseIndex } 3015 ::= { eoACPwrCharacteristicsPhaseTable 1 } 3017 EoACPwrCharacteristicsPhaseEntry ::= SEQUENCE { 3018 eoPhaseIndex Integer32, 3019 eoACPwrCharacteristicsPhaseAvgCurrent Integer32, 3020 eoACPwrCharacteristicsPhaseActivePower Integer32, 3021 eoACPwrCharacteristicsPhaseReactivePower Integer32, 3022 eoACPwrCharacteristicsPhaseApparentPower Integer32, 3023 eoACPwrCharacteristicsPhasePowerFactor Integer32, 3025 eoACPwrCharacteristicsPhaseImpedance Integer32 3026 } 3028 eoPhaseIndex OBJECT-TYPE 3029 SYNTAX Integer32 (0..359) 3030 MAX-ACCESS not-accessible 3031 STATUS current 3032 DESCRIPTION 3033 "A phase angle typically corresponding to 0, 120, 240." 3034 ::= { eoACPwrCharacteristicsPhaseEntry 1 } 3036 eoACPwrCharacteristicsPhaseAvgCurrent OBJECT-TYPE 3037 SYNTAX Integer32 3038 UNITS "Ampheres" 3039 MAX-ACCESS read-only 3040 STATUS current 3041 DESCRIPTION 3042 "A measured value of the current per phase. IEC 61850- 3043 7-4 attribute 'A'" 3044 ::= { eoACPwrCharacteristicsPhaseEntry 2 } 3046 eoACPwrCharacteristicsPhaseActivePower OBJECT-TYPE 3047 SYNTAX Integer32 3048 UNITS " watts" 3049 MAX-ACCESS read-only 3050 STATUS current 3051 DESCRIPTION 3052 "A measured value of the actual power delivered to or 3053 consumed by the load. IEC 61850-7-4 attribute 'W'" 3054 ::= { eoACPwrCharacteristicsPhaseEntry 3 } 3056 eoACPwrCharacteristicsPhaseReactivePower OBJECT-TYPE 3057 SYNTAX Integer32 3058 UNITS "volt-amperes reactive" 3059 MAX-ACCESS read-only 3060 STATUS current 3061 DESCRIPTION 3062 "A measured value of the reactive portion of the 3063 apparent power. IEC 61850-7-4 attribute 'VAr'" 3064 ::= { eoACPwrCharacteristicsPhaseEntry 4 } 3066 eoACPwrCharacteristicsPhaseApparentPower OBJECT-TYPE 3067 SYNTAX Integer32 3068 UNITS "volt-amperes" 3069 MAX-ACCESS read-only 3070 STATUS current 3071 DESCRIPTION 3072 "A measured value of the voltage and current determines 3073 the apparent power. Active plus reactive power equals 3074 the total apparent power. 3076 Note: Watts and volt-ampheres are equivalent units and 3077 may be combined. IEC 61850-7-4 attribute 'VA'." 3078 ::= { eoACPwrCharacteristicsPhaseEntry 5 } 3080 eoACPwrCharacteristicsPhasePowerFactor OBJECT-TYPE 3081 SYNTAX Integer32 (-10000..10000) 3082 UNITS "hundredths of percent" 3083 MAX-ACCESS read-only 3084 STATUS current 3085 DESCRIPTION 3086 "A measured value ratio of the real power flowing to 3087 the load versus the apparent power for this phase. IEC 3088 61850-7-4 attribute 'PF'. Power Factor can be positive 3089 or negative where the sign should be in lead/lag (IEEE) 3090 form." 3091 ::= { eoACPwrCharacteristicsPhaseEntry 6 } 3093 eoACPwrCharacteristicsPhaseImpedance OBJECT-TYPE 3094 SYNTAX Integer32 3095 UNITS "volt-amperes" 3096 MAX-ACCESS read-only 3097 STATUS current 3098 DESCRIPTION 3099 "A measured value of the impedance. IEC 61850-7-4 attribute 3100 'Z'." 3101 ::= { eoACPwrCharacteristicsPhaseEntry 7 } 3103 eoACPwrCharacteristicsDelPhaseTable OBJECT-TYPE 3104 SYNTAX SEQUENCE OF 3105 EoACPwrCharacteristicsDelPhaseEntry 3106 MAX-ACCESS not-accessible 3107 STATUS current 3108 DESCRIPTION 3109 "This table describes DEL configuration phase-to-phase 3110 power characteristics measurements. This is a sparse 3111 extension of the eoACPwrCharacteristicsPhaseTable." 3112 ::= { powerCharacteristicsMIBObjects 3 } 3114 eoACPwrCharacteristicsDelPhaseEntry OBJECT-TYPE 3115 SYNTAX EoACPwrCharacteristicsDelPhaseEntry 3116 MAX-ACCESS not-accessible 3117 STATUS current 3118 DESCRIPTION 3119 "An entry describes power characteristics attributes of 3120 a phase in a DEL 3-phase power system. Voltage 3121 measurements are provided both relative to each other 3122 and zero. 3124 Measured values are from IEC 61850-7-2 MMUX and THD from 3125 MHAI objects. 3127 For phase-to-phase measurements, the eoPhaseIndex is 3128 compared against the following phase at +120 degrees. 3129 Thus, the possible values are: 3131 eoPhaseIndex Next Phase Angle 3132 0 120 3133 120 240 3134 240 0 3135 " 3136 INDEX { entPhysicalIndex, eoPhaseIndex} 3137 ::= { eoACPwrCharacteristicsDelPhaseTable 1} 3139 EoACPwrCharacteristicsDelPhaseEntry ::= SEQUENCE { 3140 eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage 3141 Integer32, 3142 eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage 3143 Integer32, 3144 eoACPwrCharacteristicsDelThdCurrent 3145 Integer32 3146 } 3148 eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage OBJECT-TYPE 3149 SYNTAX Integer32 3150 UNITS "0.1 Volt AC" 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "A measured value of phase to next phase voltages, where 3155 the next phase is IEC 61850-7-4 attribute 'PPV'." 3156 ::= { eoACPwrCharacteristicsDelPhaseEntry 2 } 3158 eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage OBJECT-TYPE 3159 SYNTAX Integer32 (0..10000) 3160 UNITS "hundredths of percent" 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "A calculated value for the voltage total harmonic 3165 disortion for phase to next phase. Method of calculation 3166 is not specified. IEC 61850-7-4 attribute 'ThdPPV'." 3167 ::= { eoACPwrCharacteristicsDelPhaseEntry 3 } 3169 eoACPwrCharacteristicsDelThdCurrent OBJECT-TYPE 3170 SYNTAX Integer32 (0..10000) 3171 UNITS "hundredths of percent" 3172 MAX-ACCESS read-only 3173 STATUS current 3174 DESCRIPTION 3175 "A calculated value for the voltage total harmonic 3176 disortion (THD) for phase to phase. Method of 3177 calculation is not specified. 3178 IEC 61850-7-4 attribute 'ThdPPV'." 3179 ::= { eoACPwrCharacteristicsDelPhaseEntry 4 } 3181 eoACPwrCharacteristicsWyePhaseTable OBJECT-TYPE 3182 SYNTAX SEQUENCE OF 3183 EoACPwrCharacteristicsWyePhaseEntry 3184 MAX-ACCESS not-accessible 3185 STATUS current 3186 DESCRIPTION 3187 "This table describes WYE configuration phase-to-neutral 3188 power characteristics measurements. This is a sparse 3189 extension of the eoACPwrCharacteristicsPhaseTable." 3190 ::= { powerCharacteristicsMIBObjects 4 } 3192 eoACPwrCharacteristicsWyePhaseEntry OBJECT-TYPE 3193 SYNTAX EoACPwrCharacteristicsWyePhaseEntry 3194 MAX-ACCESS not-accessible 3195 STATUS current 3196 DESCRIPTION 3197 "This table describes measurements of WYE configuration 3198 with phase to neutral power characteristics attributes. 3199 Three entries are required for each supported 3200 entPhysicalIndex entry. Voltage measurements are 3201 relative to neutral. 3203 This is a sparse extension of the 3204 eoACPwrCharacteristicsPhaseTable. 3206 Each entry describes power characteristics attributes of 3207 one phase of a WYE 3-phase power system. 3209 Measured values are from IEC 61850-7-2 MMUX and THD from 3210 MHAI objects." 3211 INDEX { entPhysicalIndex, eoPhaseIndex } 3212 ::= { eoACPwrCharacteristicsWyePhaseTable 1} 3214 EoACPwrCharacteristicsWyePhaseEntry ::= SEQUENCE { 3215 eoACPwrCharacteristicsWyePhaseToNeutralVoltage 3216 Integer32, 3217 eoACPwrCharacteristicsWyePhaseCurrent 3218 Integer32, 3219 eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage 3220 Integer32 3221 } 3222 eoACPwrCharacteristicsWyePhaseToNeutralVoltage OBJECT-TYPE 3223 SYNTAX Integer32 3224 UNITS "0.1 Volt AC" 3225 MAX-ACCESS read-only 3226 STATUS current 3227 DESCRIPTION 3228 "A measured value of phase to neutral voltage. IEC 3229 61850-7-4 attribute 'PhV'." 3230 ::= { eoACPwrCharacteristicsWyePhaseEntry 1 } 3232 eoACPwrCharacteristicsWyePhaseCurrent OBJECT-TYPE 3233 SYNTAX Integer32 3234 UNITS "0.1 ampheres AC" 3235 MAX-ACCESS read-only 3236 STATUS current 3237 DESCRIPTION 3238 "A measured value of phase currents. IEC 61850-7-4 3239 attribute 'A'." 3240 ::= { eoACPwrCharacteristicsWyePhaseEntry 2 } 3242 eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage OBJECT-TYPE 3243 SYNTAX Integer32 (0..10000) 3244 UNITS "hundredths of percent" 3245 MAX-ACCESS read-only 3246 STATUS current 3247 DESCRIPTION 3248 "A calculated value of the voltage total harmonic 3249 distortion (THD) for phase to neutral. IEC 61850-7-4 3250 attribute 'ThdPhV'." 3251 ::= { eoACPwrCharacteristicsWyePhaseEntry 3 } 3253 -- Conformance 3255 powerCharacteristicsMIBCompliances OBJECT IDENTIFIER 3256 ::= { powerCharacteristicsMIB 2 } 3258 powerCharacteristicsMIBGroups OBJECT IDENTIFIER 3259 ::= { powerCharacteristicsMIB 3 } 3261 powerCharacteristicsMIBFullCompliance MODULE-COMPLIANCE 3262 STATUS current 3263 DESCRIPTION 3264 "When this MIB is implemented with support for read-create, 3265 then such an implementation can claim full compliance. 3266 Such devices can then be both monitored and configured with 3267 this MIB. 3269 Module Compliance of [EMAN-ENTITY] with respect to 3270 entity4CRCompliance should be supported which requires 3271 implementation of 3 MIB objects (entPhysicalIndex, 3272 entPhysicalName and entPhysicalUUID)." 3274 MODULE -- this module 3275 MANDATORY-GROUPS { 3276 powerACPwrCharacteristicsMIBTableGroup 3277 } 3279 GROUP powerACPwrCharacteristicsOptionalMIBTableGroup 3280 DESCRIPTION 3281 "A compliant implementation does not have 3282 to implement." 3284 GROUP powerACPwrCharacteristicsPhaseMIBTableGroup 3285 DESCRIPTION 3286 "A compliant implementation does not have to 3287 implement." 3289 GROUP powerACPwrCharacteristicsDelPhaseMIBTableGroup 3290 DESCRIPTION 3291 "A compliant implementation does not have to 3292 implement." 3294 GROUP powerACPwrCharacteristicsWyePhaseMIBTableGroup 3295 DESCRIPTION 3296 "A compliant implementation does not have to 3297 implement." 3299 ::= { powerCharacteristicsMIBCompliances 1 } 3301 -- Units of Conformance 3303 powerACPwrCharacteristicsMIBTableGroup OBJECT-GROUP 3304 OBJECTS { 3305 -- Note that object entPhysicalIndex is NOT 3306 -- included since it is not-accessible 3308 eoACPwrCharacteristicsAvgVoltage, 3309 eoACPwrCharacteristicsAvgCurrent, 3310 eoACPwrCharacteristicsFrequency, 3312 eoACPwrCharacteristicsPowerUnitMultiplier, 3313 eoACPwrCharacteristicsPowerAccuracy, 3314 eoACPwrCharacteristicsTotalActivePower, 3316 eoACPwrCharacteristicsTotalReactivePower, 3318 eoACPwrCharacteristicsTotalApparentPower, 3319 eoACPwrCharacteristicsTotalPowerFactor 3320 } 3321 STATUS current 3322 DESCRIPTION 3323 "This group contains the collection of all the power 3324 characteristics objects related to the Energy Object." 3325 ::= { powerCharacteristicsMIBGroups 1 } 3327 powerACPwrCharacteristicsOptionalMIBTableGroup OBJECT-GROUP 3328 OBJECTS { 3329 eoACPwrCharacteristicsConfiguration, 3330 eoACPwrCharacteristicsThdAmpheres, 3331 eoACPwrCharacteristicsThdVoltage 3332 } 3333 STATUS current 3334 DESCRIPTION 3335 "This group contains the collection of all the power 3336 characteristics objects related to the Energy Object." 3337 ::= { powerCharacteristicsMIBGroups 2 } 3339 powerACPwrCharacteristicsPhaseMIBTableGroup OBJECT-GROUP 3340 OBJECTS { 3341 -- Note that object entPhysicalIndex is 3342 -- NOT included since it is 3343 -- not-accessible 3344 eoACPwrCharacteristicsPhaseAvgCurrent, 3345 eoACPwrCharacteristicsPhaseActivePower, 3347 eoACPwrCharacteristicsPhaseReactivePower, 3349 eoACPwrCharacteristicsPhaseApparentPower, 3350 eoACPwrCharacteristicsPhasePowerFactor, 3352 eoACPwrCharacteristicsPhaseImpedance 3353 } 3354 STATUS current 3355 DESCRIPTION 3356 "This group contains the collection of all 3-phase power 3357 characteristics objects related to the Power State." 3358 ::= { powerCharacteristicsMIBGroups 3 } 3360 powerACPwrCharacteristicsDelPhaseMIBTableGroup OBJECT-GROUP 3361 OBJECTS { 3362 -- Note that object entPhysicalIndex and 3363 -- eoPhaseIndex are NOT included 3364 -- since they are not-accessible 3366 eoACPwrCharacteristicsDelPhaseToNextPhaseVoltage , 3368 eoACPwrCharacteristicsDelThdPhaseToNextPhaseVoltage, 3369 eoACPwrCharacteristicsDelThdCurrent 3370 } 3371 STATUS current 3372 DESCRIPTION 3373 "This group contains the collection of all power 3374 characteristic attributes of a phase in a DEL 3-phase 3375 power system." 3376 ::= { powerCharacteristicsMIBGroups 4 } 3378 powerACPwrCharacteristicsWyePhaseMIBTableGroup OBJECT-GROUP 3379 OBJECTS { 3380 -- Note that object entPhysicalIndex and 3381 -- eoPhaseIndex are NOT included 3382 -- since they are not-accessible 3384 eoACPwrCharacteristicsWyePhaseToNeutralVoltage, 3385 eoACPwrCharacteristicsWyePhaseCurrent, 3387 eoACPwrCharacteristicsWyeThdPhaseToNeutralVoltage 3388 } 3389 STATUS current 3390 DESCRIPTION 3391 "This group contains the collection of all WYE 3392 configuration phase-to-neutral power characteristics 3393 measurements." 3394 ::= { powerCharacteristicsMIBGroups 5 } 3396 END 3398 11. Security Considerations 3400 Some of the readable objects in these MIB modules (i.e., objects 3401 with a MAX-ACCESS other than not-accessible) may be considered 3402 sensitive or vulnerable in some network environments. It is 3403 thus important to control even GET and/or NOTIFY access to these 3404 objects and possibly to even encrypt the values of these objects 3405 when sending them over the network via SNMP. 3407 There are a number of management objects defined in these MIB 3408 modules with a MAX-ACCESS clause of read-write and/or read- 3409 create. Such objects MAY be considered sensitive or vulnerable 3410 in some network environments. The support for SET operations in 3411 a non-secure environment without proper protection can have a 3412 negative effect on network operations. The following are the 3413 tables and objects and their sensitivity/vulnerability: 3415 - Unauthorized changes to the eoPowerOperState (via 3416 theeoPowerAdminState ) MAY disrupt the power settings of the 3417 differentEnergy Objects, and therefore the state of 3418 functionality of the respective Energy Objects. 3419 - Unauthorized changes to the eoEnergyParametersTable MAY 3420 disrupt energy measurement in the eoEnergyTable table. 3422 SNMP versions prior to SNMPv3 did not include adequate security. 3423 Even if the network itself is secure (for example, by using 3424 IPsec), there is still no secure control over who on the secure 3425 network is allowed to access and GET/SET 3426 (read/change/create/delete) the objects in these MIB modules. 3428 It is RECOMMENDED that implementers consider the security 3429 features as provided by the SNMPv3 framework (see [RFC3410], 3430 section 8), including full support for the SNMPv3 cryptographic 3431 mechanisms (for authentication and privacy). 3433 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3434 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3435 enable cryptographic security. It is then a customer/operator 3436 responsibility to ensure that the SNMP entity giving access to 3437 an instance of these MIB modules is properly configured to give 3438 access to the objects only to those principals (users) that have 3439 legitimate rights to GET or SET (change/create/delete) them. 3441 12. IANA Considerations 3443 12.1. IANA Considerations for the MIB Modules 3445 The MIB modules in this document uses the following IANA- 3446 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers 3447 registry: 3449 Descriptor OBJECT IDENTIFIER value 3450 ---------- ----------------------- 3451 energyObjectMib { mib-2 xxx } 3452 powerCharacteristicsMIB { mib-2 yyy } 3454 Additions to the MIB modules are subject to Expert Review 3455 [RFC5226], i.e., review by one of a group of experts designated 3456 by an IETF Area Director. The group of experts MUST check the 3457 requested MIB objects for completeness and accuracy of the 3458 description. Requests for MIB objects that duplicate the 3459 functionality of existing objects SHOULD be declined. The 3460 smallest available OIDs SHOULD be assigned to the new MIB 3461 objects. The specification of new MIB objects SHOULD follow the 3462 structure specified in Section 10. and MUST be published using 3463 a well-established and persistent publication medium. 3465 12.2. IANA Registration of new Power State Set 3467 This document specifies an initial set of Power State Sets. The 3468 list of these Power State Sets with their numeric identifiers is 3469 given in Section 5.2.1. IANA maintains a Textual Convention 3470 IANAPowerStateSet with the initial set of Power State Sets and 3471 the Power States within those Power State Sets. The current 3472 version of Textual convention can be accessed 3473 http://www.iana.org/assignments/IANAPowerStateSet 3475 New Assignments to Power State Sets shall be administered by 3476 IANA and the guidelines and procedures are listed in this 3477 Section. 3479 New assignments for Power State Set will be administered by IANA 3480 through Expert Review [RFC5226], i.e., review by one of a group 3481 of experts designated by an IETF Area Director. The group of 3482 experts MUST check the requested state for completeness and 3483 accuracy of the description. A pure vendor specific 3484 implementation of Power State Set shall not be adopted; since it 3485 would lead to proliferation of Power State Sets. 3487 12.2.1. IANA Registration of the IEEE1621 Power State Set 3489 This document specifies a set of values for the IEEE1621 Power 3490 State Set [IEEE1621]. The list of these values with their 3491 identifiers is given in Section 5.2.1. The Internet Assigned 3492 Numbers Authority (IANA) created a new registry for IEEE1621 3493 Power State Set identifiers and filled it with the initial 3494 listin the Textual Convention IANAPowerStateSet.. 3496 New assignments (or potentially deprecation) for IEEE1621 Power 3497 State Set will be administered by IANA through Expert Review 3498 [RFC5226], i.e., review by one of a group of experts designated 3499 by an IETF Area Director. The group of experts MUST check the 3500 requested state for completeness and accuracy of the 3501 description. 3503 12.2.2. IANA Registration of the DMTF Power State Set 3505 This document specifies a set of values for the DMTF Power State 3506 Set. The list of these values with their identifiers is given 3507 in Section 5.2.1. The Internet Assigned Numbers Authority 3508 (IANA) has created a new registry for DMTF Power State Set 3509 identifiers and filled it with the initial list in the Textual 3510 Convention IANAPowerStateSet. 3511 New assignments (or potentially deprecation) for DMTF Power 3512 State Set will be administered by IANA through Expert Review 3513 [RFC5226], i.e., review by one of a group of experts designated 3514 by an IETF Area Director. The group of experts MUST check the 3515 conformance with the DMTF standard [DMTF], on the top of 3516 checking for completeness and accuracy of the description. 3518 12.2.3. IANA Registration of the EMAN Power State Set 3520 This document specifies a set of values for the EMAN Power State 3521 Set. The list of these values with their identifiers is given 3522 in Section 5.2.1. The Internet Assigned Numbers Authority 3523 (IANA) has created a new registry for EMAN Power State Set 3524 identifiers and filled it with the initial list in the Textual 3525 Convention IANAPowerStateSet. 3526 New assignments (or potentially deprecation) for EMAN Power 3527 State Set will be administered by IANA through Expert Review 3528 [RFC5226], i.e., review by one of a group of experts designated 3529 by an IETF Area Director. The group of experts MUST check the 3530 requested state for completeness and accuracy of the 3531 description. 3533 12.3. Updating the Registration of Existing Power State Sets 3535 IANA maintains a Textual Convention IANAPowerStateSet with the 3536 initial set of Power State Sets and the Power States within 3537 those Power State Sets. The current version of Textual 3538 convention can be accessed 3539 http://www.iana.org/assignments/IANAPowerStateSet 3540 With the evolution of standards, over time, it may be important 3541 to deprecate of some of the existing the Power State Sets or 3542 some of the states within a Power State Set. 3544 The registrant shall publish an Internet-draft or an individual 3545 submission with the clear specification on deprecation of Power 3546 State Sets or Power States registered with IANA. The 3547 deprecation shall be administered by IANA through Expert Review 3548 [RFC5226], i.e., review by one of a group of experts designated 3549 by an IETF Area Director. The process should also allow for a 3550 mechanism for cases where others have significant objections to 3551 claims on deprecation of a registration. In cases, where the 3552 registrant cannot be reached, IESG can designate an Expert to 3553 modify the IANA registry for the deprecation. 3555 12. Contributors 3557 This document results from the merger of two initial proposals. 3558 The following persons made significant contributions either in 3559 one of the initial proposals or in this document. 3561 John Parello 3563 Rolf Winter 3565 Dominique Dudkowski 3567 13. Acknowledgment 3569 The authors would like to thank Shamita Pisal for her prototype 3570 of this MIB module, and her valuable feedback. The authors 3571 would like to Michael Brown for improving the text dramatically. 3573 We would like to thank Juergen Schoenwalder for proposing the 3574 design of the Textual Convention for IANAPowerStateSet and Ira 3575 McDonald for his feedback. Thanks for the many comments on the 3576 design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. 3578 14. Open Issues 3579 OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are 3580 covered. 3582 OPEN ISSUE 2 IANA Registered Power State Sets deferred to [EMAN- 3583 FMWK] 3585 15. References 3587 15.2. Normative References 3589 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 3590 Requirement Levels, BCP 14, RFC 2119, March 1997. 3592 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3593 Schoenwaelder, Ed., "Structure of Management 3594 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3595 1999. 3597 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3598 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3599 STD 58, RFC 2579, April 1999. 3601 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3602 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3603 April 1999. 3605 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 3606 RFC3621, December 2003. 3608 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3609 3)", RFC 4133, August 2005. 3611 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 3612 Base extension module for TIA-TR41.4 media endpoint 3613 discovery information", July 2005. 3615 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 3616 energy-aware-mib-05 ", work in progress, March 2012. 3618 15.3. Informative References 3620 [RFC1628] S. Bradner, "UPS Management Information Base", RFC 3621 1628, May 1994 3623 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3624 "Introduction and Applicability Statements for Internet 3625 Standard Management Framework ", RFC 3410, December 3626 2002. 3628 [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. 3629 Waldbusser, "Management Information Base (MIB) for the 3630 Simple Network Management Protocol (SNMP)", RFC3418, 3631 December 2002. 3633 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity 3634 Sensor Management Information Base", RFC 3433, December 3635 2002. 3637 [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 3638 4268, November 2005. 3640 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 3641 "Guidelines for Writing an IANA Considerations Section 3642 in RFCs ", BCP 26, RFC 5226, May 2008. 3644 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 3645 M. Chandramouli, " Requirements for Energy Management", 3646 draft-ietf-eman-requirements-09, October 2012. 3648 [EMAN-FMWK] Claise, B., Parello, J., Schoening, B., Quittek, J. 3649 and Nordman, B, "Energy Management Framework", draft- 3650 ietf-eman-framework-05, July 2012. 3652 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 3653 Quittek, J. and B. Claise "Energy and Power Monitoring 3654 MIB ", draft-ietf-eman-energy-monitoring-mib-03, July 3655 2012. 3657 [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B. 3658 "Energy Management (EMAN) Applicability Statement", 3659 draft-ietf-eman-applicability-statement-02, October 2012. 3661 [EMAN-ENTITY] A. Bierman, D. Romascanu, J. Quittek and M. 3662 Chandramouli " Entity MIB (Version 4)", draft-ietf- 3663 eman-rfc4133bis-03, October 2012. 3665 [EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology", 3666 draft-parello-eman-definitions-07, work in progress, 3667 October 2012. 3669 [ACPI] "Advanced Configuration and Power Interface 3670 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 3671 0b.pdf 3673 [DMTF] "Power State Management Profile DMTF DSP1027 Version 3674 2.0" December 2009 3675 http://www.dmtf.org/sites/default/files/standards/docum 3676 ents/DSP1027_2.0.0.pdf 3678 [IEEE1621] "Standard for User Interface Elements in Power 3679 Control of Electronic Devices Employed in 3680 Office/Consumer Environments", IEEE 1621, December 3681 2004. 3683 [IEC.61850-7-4] International Electrotechnical Commission, 3684 "Communication networks and systems for power utility 3685 automation Part 7-4: Basic communication structure 3686 Compatible logical node classes and data object 3687 classes", 2010. 3689 [IEC.62053-21] International Electrotechnical Commission, 3690 "Electricity metering equipment (a.c.) Particular 3691 requirements Part 22: Static meters for active energy 3692 (classes 1 and 2)", 2003. 3694 [IEC.62053-22]International Electrotechnical Commission, 3695 "Electricity metering equipment (a.c.) Particular 3696 requirements Part 22: Static meters for active energy 3697 (classes 0,2 S and 0,5 S)", 2003. 3699 Authors' Addresses 3701 Mouli Chandramouli 3702 Cisco Systems, Inc. 3703 Sarjapur Outer Ring Road 3704 Bangalore 560103 3705 IN 3707 Phone: +91 80 4429 2409 3708 Email: moulchan@cisco.com 3710 Brad Schoening 3711 44 Rivers Edge Drive 3712 Little Silver, NJ 07739 3713 US 3714 Email: brad.schoening@verizon.net 3716 Juergen Quittek 3717 NEC Europe Ltd. 3718 NEC Laboratories Europe 3719 Network Research Division 3720 Kurfuersten-Anlage 36 3721 Heidelberg 69115 3722 DE 3724 Phone: +49 6221 4342-115 3725 Email: quittek@neclab.eu 3727 Thomas Dietz 3728 NEC Europe Ltd. 3729 NEC Laboratories Europe 3730 Network Research Division 3731 Kurfuersten-Anlage 36 3732 Heidelberg 69115 3733 DE 3735 Phone: +49 6221 4342-128 3736 Email: Thomas.Dietz@neclab.eu 3738 Benoit Claise 3739 Cisco Systems, Inc. 3740 De Kleetlaan 6a b1 3741 Diegem 1813 3742 BE 3744 Phone: +32 2 704 5622 3745 Email: bclaise@cisco.com