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