idnits 2.17.1 draft-ietf-eman-energy-monitoring-mib-02.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 555 has weird spacing: '...tiplier eoP...' == Line 570 has weird spacing: '...tateSet eoPow...' == Line 594 has weird spacing: '...wStatus eoEne...' == Line 614 has weird spacing: '...exed by entPh...' == Line 859 has weird spacing: '...ment of an En...' == (11 more instances...) -- The document date (March 9, 2012) is 4431 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) == Missing Reference: 'ITU-T-M-3400' is mentioned on line 231, but not defined == Missing Reference: 'NMF' is mentioned on line 238, but not defined == Missing Reference: 'TMN' is mentioned on line 241, but not defined == Missing Reference: '1037C' is mentioned on line 273, but not defined == Missing Reference: 'ISO50001' is mentioned on line 291, but not defined == Missing Reference: 'IEEE100' is mentioned on line 342, but not defined == Missing Reference: 'IEC60050' is mentioned on line 326, but not defined == Missing Reference: 'SQL' is mentioned on line 435, but not defined ** 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-05 == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-03 -- No information found for draft-eman-ietf-energy-monitoring-mib - is the name correct? == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-00 == Outdated reference: A later version (-09) exists of draft-parello-eman-definitions-04 Summary: 1 error (**), 0 flaws (~~), 20 warnings (==), 5 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: September 8, 2012 Independent Consultant 6 J. Quittek 7 T. Dietz 8 NEC Europe Ltd. 9 B. Claise 10 Cisco Systems, Inc. 11 March 9, 2012 13 Power and Energy Monitoring MIB 14 draft-ietf-eman-energy-monitoring-mib-02 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 September 2012. 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............................................. 4 70 2. The Internet-Standard Management Framework............... 5 71 3. Use Cases................................................ 5 72 4. Terminology.............................................. 5 73 Energy Management.........................................6 74 Energy Management System (EnMS)...........................6 75 ISO Energy Management System..............................7 76 Energy....................................................7 77 Power.....................................................7 78 Demand....................................................8 79 Power Quality.............................................8 80 Electrical Equipment......................................8 81 Non-Electrical Equipment (Mechanical Equipment)...........8 82 Energy Object.............................................9 83 Electrical Energy Object..................................9 84 Non-Electrical Energy Object..............................9 85 Energy Monitoring.........................................9 86 Energy Control............................................9 87 Energy Management Domain.................................10 88 Energy Object Identification.............................10 89 Energy Object Context....................................10 90 Energy Object Relationship...............................10 91 Aggregation Relationship.................................11 92 Metering Relationship....................................11 93 Power Source Relationship................................11 94 Proxy Relationship.......................................11 95 Dependency Relationship..................................12 96 Energy Object Parent.....................................12 97 Energy Object Child......................................12 98 Power State..............................................12 99 Power State Set..........................................13 100 Nameplate Power..........................................13 101 5. Architecture Concepts Applied to the MIB Module......... 13 102 5.1. Energy Object Information............................. 20 103 5.2. Power State........................................... 20 104 5.2.1. Power State Set................................21 105 5.2.2. IEEE1621 Power State Set.......................22 106 5.2.3. DMTF Power State Set...........................22 107 5.2.4. EMAN Power State Set...........................23 108 5.3. Energy Object Usage Information....................... 26 109 5.4. Optional Power Usage Quality.......................... 27 110 5.5. Optional Energy Measurement........................... 28 111 5.6. Fault Management...................................... 32 112 6. Discovery............................................... 32 113 7. Link with the other IETF MIBs........................... 33 114 7.1. Link with theENTITY-MIBand the ENTITY-SENSOR MIB....33 115 7.2. Link with the ENTITY-STATE MIB......................34 116 7.3. Link with the POWER-OVER-ETHERNET MIB...............35 117 7.4. Link with the UPS MIB...............................35 118 7.5. Link with the LLDP and LLDP-MED MIBs................36 119 8. Implementation Scenario................................. 37 120 9. Structure of the MIB.................................... 39 121 10. MIB Definitions........................................ 40 122 11. Security Considerations................................ 78 123 12. IANA Considerations.................................... 79 124 12.1. IANA Considerations for the MIB Modules.............. 79 125 12.2. IANA Registration of new Power State Set............. 80 126 12.2.1. IANA Registration of the IEEE1621 Power State Set..80 127 12.2.2. IANA Registration of the DMTF Power State Set......81 128 12.2.3. IANA Registration of the EMAN Power State Set......81 129 12.3. Updating the Registration of Existing Power State 130 Sets................................................. 81 132 12. Contributors........................................... 82 133 13. Acknowledgment......................................... 82 134 14. Open Issues............................................ 82 135 15. References............................................. 84 136 15.2. Normative References...............................84 137 15.3. Informative References.............................84 139 1. Introduction 141 This document defines a subset of the Management Information 142 Base (MIB) for use in energy management of devices within or 143 connected to communication networks. The MIB modules in this 144 document are designed to provide a model for energy management, 145 which includes monitoring for power state and energy consumption 146 of networked elements. This MIB takes into account the Energy 147 Management Framework [EMAN-FRAMEWORK], which in turn, is based 148 on the Requirements for Energy Management[EMAN-REQ]. 150 Energy management is applicable to devices in communication 151 networks. Target devices for this specification include (but 152 are not limited to): routers, switches, Power over Ethernet 153 (PoE) endpoints, protocol gateways for building management 154 systems, intelligent meters, home energy gateways, hosts and 155 servers, sensor proxies, etc. Target devices and the use cases 156 for Energy Management are discussed in Energy Management 157 Applicability Statement [EMAN-AS]. 159 Where applicable, device monitoring extends to the individual 160 components of the device and to any attached dependent devices. 161 For example: A device can contain components that are 162 independent from a power-state point of view, such as line 163 cards, processor cards, hard drives. A device can also have 164 dependent attached devices, such as a switch with PoE endpoints 165 or a power distribution unit with attached endpoints. 167 Devices and their sub-components may be characterized by the 168 power-related attributes of a physical entity present in the 169 ENTITY MIB, even though the ENTITY-MIB compliance is not a 170 requirement due to the variety and broad base of devices 171 concerned with energy management. 173 2. The Internet-Standard Management Framework 175 For a detailed overview of the documents that describe the 176 current Internet-Standard Management Framework, please refer to 177 section 7 of RFC 3410 [RFC3410]. 179 Managed objects are accessed via a virtual information store, 180 termed the Management Information Base or MIB. MIB objects are 181 generally accessed through the Simple Network Management 182 Protocol (SNMP). Objects in the MIB are defined using the 183 mechanisms defined in the Structure of Management Information 184 (SMI). This memo specifies MIB modules that are compliant to 185 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 186 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 188 3. Use Cases 190 Requirements for power and energy monitoring for networking 191 devices are specified in [EMAN-REQ]. The requirements in [EMAN- 192 REQ] cover devices typically found in communications networks, 193 such as switches, routers, and various connected endpoints. For 194 a power monitoring architecture to be useful, it should also 195 apply to facility meters, power distribution units, gateway 196 proxies for commercial building control, home automation 197 devices, and devices that interface with the utility and/or 198 smart grid. Accordingly, the scope of the MIB modules in this 199 document is broader than that specified in [EMAN-REQ]. Several 200 use cases for Energy Management have been identified in the 201 "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An 202 illustrative example scenario is presented in Section 8. 204 4. Terminology 206 EDITOR'S NOTE: 207 - All terms are copied over from the version 4 of the 208 [EMAN-TERMINOLOGY] draft. The only difference in 209 definition is the Energy Management Domain, which has 210 been improved, to address one comment from Bill 211 Mielke. Hopefully, this version 4 is the final 212 version. 213 - "All" terms have been copied. Potentially, some 214 unused terms might have to be removed (example 215 Electrical Equipment". Alternatively, as this 216 document is the first standard track document in the 217 EMAN WG, it may become the reference document for the 218 terminology (instead of cutting/pasting the 219 terminology in all drafts) 220 - "Reference: herein" has not been copied over from 221 the terminology draft. 223 Energy Management 225 Energy Management is a set of functions for measuring, 226 modeling, planning, and optimizing networks to ensure 227 that the network elements and attached devices use 228 energy efficiently and is appropriate for the nature 229 of the application and the cost constraints of the 230 organization. 231 Reference: Adapted from [ITU-T-M-3400] 232 Example: A set of computer systems that will poll 233 electrical meters and store the readings 234 NOTES: 235 1. Energy management refers to the activities, methods, 236 procedures and tools that pertain to measuring, 237 modeling, planning, controlling and optimizing the 238 use of energy in networked systems [NMF]. 239 2. Energy Management is a management domain which is 240 congruent to any of FCAPS areas of management in the 241 ISO/OSI Network Management Model [TMN]. Energy 242 Management for communication networks and attached 243 devices is a subset or part of an organization's 244 greater Energy Management Policies. 246 Energy Management System (EnMS) 248 An Energy Management System is a combination of 249 hardware and software used to administer a network 250 with the primarily purpose being Energy Management. 251 Reference: Adapted from [1037C] 252 Example: A single computer system that polls data from 253 devices using SNMP 254 NOTES: 255 1. An Energy Management System according to [ISO50001] 256 (ISO-EnMS) is a set of systems or procedures upon 257 which organizations can develop and implement an 258 energy policy, set targets, action plans and take 259 into account legal requirements related to energy 260 use. An EnMS allows organizations to improve energy 261 performance and demonstrate conformity to 262 requirements, standards, and/or legal requirements. 263 2. Example ISO-EnMS: Company A defines a set of 264 policies and procedures indicating there should 265 exist multiple computerized systems that will poll 266 energy from their meters and pricing / source data 267 from their local utility. Company A specifies that 268 their CFO should collect information and summarize 269 it quarterly to be sent to an accounting firm to 270 produce carbon accounting reporting as required by 271 their local government. 272 3. For the purposes of EMAN, the definition from 273 [1037C] is the preferred meaning of an Energy 274 Management System (EnMS). The definition from 275 [ISO50001] can be referred to as ISO Energy 276 Management System (ISO-EnMS). 278 ISO Energy Management System 280 Energy Management System as defined by [ISO50001] 282 Energy 284 That which does work or is capable of doing work. As 285 used by electric utilities, it is generally a 286 reference to electrical energy and is measured in 287 kilo-watt hours (kWh). 288 Reference: [IEEE100] 289 NOTES 290 1. Energy is the capacity of a system to produce 291 external activity or perform work [ISO50001] 293 Power 295 The time rate at which energy is emitted, transferred, 296 or received; usually expressed in watts (or in joules 297 per second). 298 Reference: [IEEE100] 300 Demand 302 The average value of power or a related quantity over 303 a specified interval of time. Note: Demand is 304 expressed in kilowatts, kilovolt-amperes, kilovars, or 305 other suitable units. 307 Reference: [IEEE100] 308 NOTES: 309 1. typically kilowatts 310 2. Energy providers typically bill by Demand 311 measurements as well as for maximum Demand per 312 billing periods. Power values may spike during 313 short-terms by devices, but Demand measurements 314 recognize that maximum Demand does not equal maximum 315 Power during an interval. 317 Power Quality 319 Characteristics of the electric current, voltage and 320 frequencies at a given point in an electric power 321 system, evaluated against a set of reference technical 322 parameters. These parameters might, in some cases, 323 relate to the compatibility between electricity 324 supplied in an electric power system and the loads 325 connected to that electric power system. 326 Reference: [IEC60050] 328 Electrical Equipment 330 A general term including materials, fittings, devices, 331 appliances, fixtures, apparatus, machines, etc., used 332 as a part of, or in connection with, an electric 333 installation. 334 Reference: [IEEE100] 336 Non-Electrical Equipment (Mechanical Equipment) 338 A general term including materials, fittings, devices 339 appliances, fixtures, apparatus, machines, etc., used 340 as a part of, or in connection with, non-electrical 341 power installations. 342 Reference: Adapted from [IEEE100] 344 Energy Object 346 An Energy Object (EO) is a piece of equipment that is 347 part of or attached to a communications network that 348 is monitored, controlled, or aids in the management of 349 another device for Energy Management. 351 Electrical Energy Object 353 An Electrical Energy Object (EEO) is an Energy Object 354 that is a piece of Electrical Equipment 356 Non-Electrical Energy Object 358 A Non-Electrical Energy Object (NEEO) an Energy Object 359 that is a piece of Non-Electrical Equipment. 361 Energy Monitoring 363 Energy Monitoring is a part of Energy Management that 364 deals with collecting or reading information from 365 Energy Objects to aid in Energy Management. 366 NOTES: 367 1. This could include Energy, Power, Demand, Power 368 Quality, Context and/or Battery information. 370 Energy Control 372 Energy Control is a part of Energy Management that 373 deals with directing influence over Energy Objects. 375 NOTES: 376 1. Typically in order to optimize or ensure its 377 efficiency. 379 Energy Management Domain 381 An Energy Management Domain is a set of Energy Objects where all 382 objects in the domain are considered one unit of management. 384 For example, power distribution units and all of the attached 385 Energy Objects are part of the same Energy Management Domain. 387 For example, all EEO's drawing power from the same 388 distribution panel with the same AC voltage within a 389 building, or all EEO's in a building for which there 390 is one main meter, would comprise an Energy Management 391 Domain. 393 NOTES: 394 1. Typically, this set will have as members all EO's 395 that are powered from the same source. 397 Energy Object Identification 399 Energy Object Identification is a set of attributes 400 that enable an Energy Object to be: uniquely 401 identified among all Energy Management Domains; linked 402 to other systems; classified as to type, model, and or 403 manufacturer 405 Energy Object Context 407 Energy Object Context is a set of attributes that 408 allow an Energy Management System to classify the use 409 of the Energy Object within an organization. 410 NOTES: 411 1. The classification could contain the use and/or the 412 ranking of the Energy Object as compared to other 413 Energy Objects in the Energy Management Domain. 415 Energy Object Relationship 417 An Energy Objects Relationship is a functional 418 association between one or more Energy Objects 420 NOTES 421 1. Relationships can be named and could include 422 Aggregation, Metering, Power Source, Proxy and 423 Dependency. 425 Aggregation Relationship 427 An Energy Object may aggregate the Energy Management 428 information of one or more Energy Objects and is 429 referred to as an Aggregation Relationship. 430 NOTES: 431 1. Aggregate values may be obtained by reading values 432 from multiple Energy Objects and producing a single 433 value of more significant meaning such as average, 434 count, maximum, median, minimum, mode and most 435 commonly sum [SQL]. 437 Metering Relationship 439 An Energy Object may measure the Power or Energy of 440 another Energy Object(s) and is referred to as a 441 Metering Relationship. 443 Example: a PoE port on a switch measures the Power it 444 provides to the connected Energy Object. 446 Power Source Relationship 448 An Energy Object may be the source of or distributor 449 of Power to another Energy Object(s) and is referred 450 to as a Power Source Relationship. 452 Example: a PDU provides power for a connected host. 454 Proxy Relationship 456 An Energy Object that provides Energy Management 457 capabilities on behalf of another Energy Object is 458 referred to a Proxy Relationship. 460 Example: a protocol gateways device for Building 461 Management Systems (BMS) with subtended devices. 463 Dependency Relationship 465 An Energy Object may be a component of or rely 466 completely upon another Energy Object to operate and 467 is referred to as a Dependency Relationship. 469 Example: A Switch chassis with multiple line cards. 471 Energy Object Parent 473 An Energy Object Parent is an Energy Object that 474 participates in an Energy Object Relationships and is 475 considered as providing the capabilities in the 476 relationship. 478 Energy Object Child 480 An Energy Object Child is an Energy Object that 481 participates in an Energy Object Relationships and is 482 considered as receiving the capabilities in the 483 relationship. 485 Power State 487 A Power State is a condition or mode of a device that 488 broadly characterizes its capabilities, power 489 consumption, and responsiveness to input. 491 Reference: Adapted from [IEEE1621] 493 NOTES: 495 1. A Power State can be seen as a power setting of an 496 Energy Object that influences the power 497 consumption, the available functionality, and the 498 responsiveness of the Energy Object. 500 2. A Power State can be viewed as one method for 501 Energy Control 503 Power State Set 505 A collection of Power States that comprise one named 506 or logical grouping of control is a Power State Set. 508 Example: The states {on, off, and sleep} as defined in 509 [IEEE1621], or the 16 power states as defined by the 510 [DMTF] can be considered two different Power State 511 Sets. 513 Nameplate Power 515 The Nameplate Power is the maximal (nominal) Power 516 that a device can support. 518 NOTES: 520 1. This is typically determined via load testing and 521 is specified by the manufacturer as the maximum 522 value required for operating the device. This is 523 sometimes referred to as the worst-case Power. The 524 actual or average Power may be lower. The 525 Nameplate Power is typically used for provisioning 526 and capacity planning. 528 5. Architecture Concepts Applied to the MIB Module 530 This section describes the concepts specified in the Energy 531 Management Framework [EMAN-FRAMEWORK] that pertain to power 532 usage, with specific information related to the MIB module 533 specified in this document. This subsection maps to the section 534 "Architecture High Level Concepts" in the Power Monitoring 535 Architecture [EMAN-FRAMEWORK]. 537 The Energy Monitoring MIB has 2 independent MIB modules. The 538 first MIB module energyObjectMib is focused on measurement of 539 power and energy. The second MIB module powerQualityMIB is 540 focused on Power Quality measurements. 542 The energyObjectMib MIB module consists of four tables. The 543 first table eoPowerTable is indexed by entPhysicalIndex. The 544 second table eoPowerStateTable indexed by entPhysicalIndex and 545 eoPowerStateIndex. The eoEnergyParametersTable is indexed 546 by eoEnergyParametersIndex. The eoEnergyTable is indexed by 547 eoEnergyParametersIndex and eoEnergyCollectionStartTime. 549 eoPowerTable(1) 550 | 551 +---eoPowerEntry(1) [entPhysicalIndex] 552 | | 553 | +---r-n Integer32 eoPower(1) 554 | +-- r-n Integer32 eoPowerNamePlate(2) 555 | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3) 556 | +-- r-n Integer32 eoPowerAccuracy(4) 557 | +-- r-n INTEGER eoMeasurementCaliber(5) 558 | +-- r-n INTEGER eoPowerCurrentType(6) 559 | +-- r-n INTEGER eoPowerOrigin(7) 560 | +-- rwn Integer32 eoPowerAdminState(8) 561 | +-- r-n Integer32 eoPowerOperState(9) 562 | +-- r-n OwnerString eoPowerStateEnterReason(10) 563 | | 564 | | 565 +---eoPowerStateTable(2) 566 | +--eoPowerStateEntry(1) 567 | | [entPhysicalIndex, 568 | | eoPowerStateIndex] 569 | | 570 | +-- --n IANAPowerStateSet eoPowerStateIndex(1) 571 | +-- r-n Interger32 eoPowerStateMaxPower (2) 572 | +-- r-n UnitMultiplier 573 | eoPowerStatePowerUnitMultiplier (3) 574 | +-- r-n TimeTicks eoPowerStateTotalTime(4) 575 | +-- r-n Counter32 eoPowerStateEnterCount(5) 576 | 578 +eoEnergyParametersTable(1) 579 +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] 580 | 582 | +-- --n PhysicalIndex eoEnergyObjectIndex (1) 583 | + r-n Integer32 eoEnergyParametersIndex (2) 584 | +-- r-n TimeInterval 585 | eoEnergyParametersIntervalLength (3) 586 | +-- r-n Integer32 587 | eoEnergyParametersIntervalNumber (4) 588 | +-- r-n Integer32 589 | eoEnergyParametersIntervalMode (5) 590 | +-- r-n TimeInterval 591 | eoEnergyParametersIntervalWindow (6) 592 | +-- r-n Integer32 593 | eoEnergyParametersSampleRate (7) 594 | +-- r-n RowStatus eoEnergyParametersStatus (8) 595 | 596 +eoEnergyTable (1) 597 +---eoEnergyEntry(1) [eoEnergyParametersIndex, 598 eoEnergyCollectionStartTime] 599 | 600 | +-- r-n TimeTicks eoEnergyCollectionStartTime (1) 601 | +-- r-n Integer32 eoEnergyConsumed (2) 602 | +-- r-n Integer32 eoEnergyyProduced (3) 603 | +-- r-n Integer32 eoEnergyNet (4) 604 | +-- r-n UnitMultiplier 605 | eoEnergyUnitMultiplier (5) 606 | +-- r-n Integer32 eoEnergyAccuracy(6) 607 | +-- r-n Integer32 eoEnergyMaxConsumed (7) 608 | +-- r-n Integer32 eoEnergyMaxProduced (8) 609 | +-- r-n TimeTicks 610 | eoEnergyDiscontinuityTime(9) 611 | +-- r-n RowStatus eoEnergyParametersStatus (10) 613 The powerQualityMIB consists of four tables. eoACPwrQualityTable 614 is indexed by entPhysicalIndex. eoACPwrQualityPhaseTable is 615 indexed by entPhysicalIndex and eoPhaseIndex. 616 eoACPwrQualityWyePhaseTable and eoACPwrQualityDelPhaseTable are 617 indexed by entPhysicalIndex and eoPhaseIndex. 619 eoPowerQualityTable(1) 620 | 621 +---eoACPwrQualityEntry (1) [entPhysicalIndex] 622 | | 623 | | 624 | +---r-n INTEGER eoACPwrQualityConfiguration (1) 625 | +-- r-n Interger32 eoACPwrQualityAvgVoltage (2) 626 | +-- r-n Integer32 eoACPwrQualityAvgCurrent (3) 627 | +-- r-n Integer32 eoACPwrQualityFrequency (4) 628 | +-- r-n UnitMultiplier 629 | eoACPwrQualityPowerUnitMultiplier (5) 630 | +-- r-n Integer32 eoACPwrQualityPowerAccuracy (6) 631 | +-- r-n Interger32 eoACPwrQualityTotalActivePower (7) 632 | +-- r-n Integer32 633 | eoACPwrQualityTotalReactivePower (8) 634 | +-- r-n Integer32 eoACPwrQualityTotalApparentPower (9) 635 | +-- r-n Integer32 eoACPwrQualityTotalPowerFactor(10) 636 | +-- r-n Integer32 eoACPwrQualityThdAmpheres (11) 637 | 638 +eoACPwrQualityPhaseTable (1) 639 +---EoACPwrQualityPhaseEntry(1)[entPhysicalIndex, 640 | | eoPhaseIndex] 641 | | 642 | +-- r-n Integer32 eoPhaseIndex (1) 643 | +-- r-n Integer32 644 | | eoACPwrQualityPhaseAvgCurrent (2) 645 | +-- r-n Integer32 646 | | eoACPwrQualityPhaseActivePower (3) 647 | +-- r-n Integer32 648 | | eoACPwrQualityPhaseReactivePower (4) 649 | +-- r-n Integer32 650 | | eoACPwrQualityPhaseApparentPower (5) 651 | +-- r-n Integer32 652 | | eoACPwrQualityPhasePowerFactor (6) 653 | +-- r-n Integer32 654 | | eoACPwrQualityPhaseImpedance (7) 655 | | 656 +eoACPwrQualityDelPhaseTable (1) 657 +-- eoACPwrQualityDelPhaseEntry(1) 658 | | [entPhysicalIndex, 659 | | eoPhaseIndex] 660 | +-- r-n Integer32 661 | | eoACPwrQualityDelPhaseToNextPhaseVoltage (1) 662 | +-- r-n Integer32 663 | | eoACPwrQualityDelThdPhaseToNextPhaseVoltage (2) 664 | +-- r-n Integer32 eoACPwrQualityDelThdCurrent (3) 665 | | 666 +eoACPwrQualityWyePhaseTable (1) 667 +-- eoACPwrQualityWyePhaseEntry (1) 668 | | [entPhysicalIndex, 669 | | eoPhaseIndex] 670 | +-- r-n Integer32 671 | | eoACPwrQualityWyePhaseToNeutralVoltage (1) 672 | +-- r-n Integer32 673 | | eoACPwrQualityWyePhaseCurrent (2) 674 | +-- r-n Integer32 675 | | eoACPwrQualityWyeThdPhaseToNeutralVoltage (3) 676 | . 678 A UML representation of the MIB objects in the two MIB modules 679 are energyObjectMib and powerQualityMIB are presented. 681 +--------------------------+ 682 | Energy Object ID | 683 | ----------------------- | 684 | | 685 | entPhysIndex (*) | 686 | entPhysicalName (*) | 687 | entPhysicalUris (*) | +---------------------------+ 688 | (EO UUID) | | | 689 | | | Energy Object Attributes | 690 | | | ------------------------- | 691 | | | | 692 +--------------------------+ | eoPowerNamePlate | 693 | | | eoPowerMeasurementCaliber | 694 | | | eoPowerOrigin | 695 | | | eoPowerCurrentType | 696 | | +---------------------------+ 697 | | | 698 | | | 699 v | v 700 +-----------------------------------------+ 701 | Energy Object Measurement | 702 |--------------------------------------- | 703 | eoPower | 704 | eoPowerUnitMultiplier | 705 | eoPowerAccuracy | 706 +-----------------------------------------+ 707 ^ | ^ 708 | | | 709 +-------------------------+ | | 710 | Energy Object State | | +------------------------+ 711 | ----------------------- | | | Energy Object State | 712 | eoPowerAdminState | | | Statistics | 713 | eoPowerOperState | | |----------------------- | 714 | eoPowerStateEnterReason | | | eoPowerStateMaxPower | 715 +-------------------------+ | | eoPowerStateTotalTime | 716 | | eoPowerStateEnterCount | 717 | +------------------------+ 718 | 719 | 720 | 721 | 723 Figure 1:UML diagram for powerMonitor MIB 725 (*) Link with the ENTITY-MIB 726 | 727 | 728 V 730 +----------------------------------------+ 731 | Energy ParametersTable | 732 | -------------------------------------- | 733 | | 734 | eoEnergyObjectIndex | 735 | eoEnergyParametersIndex | 736 | eoEnergyParametersIntervalLength | 737 | eoEnergyParametersIntervalNumber | 738 | eoEnergyParametersIntervalMode | 739 | eoEnergyParametersIntervalWindow | 740 | eoEnergyParametersSampleRate | 741 | eoEnergyParametersStatus | 742 +----------------------------------------+ 744 | 745 | 746 | 747 V 748 +----------------------------------------+ 749 | Energy Table | 750 | ---------------------------------- | 751 | eoEnergyCollectionStartTime | 752 | eoEnergyConsumed | 753 | eoEnergyProduced | 754 | eoEnergyNet | 755 | eoEnergyUnitMultiplier | 756 | eoEnergyAccuracy | 757 | eoMaxConsumed | 758 | eoMaxProduced | 759 | eoDiscontinuityTime | 760 +----------------------------------------+ 762 +--------------------------+ 763 | EnergyObject ID | 764 | ----------------------- | 765 | | 766 | | 767 | entPhysicalIndex (*) | 768 | | 769 +--------------------------+ 770 | 771 v 772 +-------------------------------------+ 773 | Power Quality | 774 | ----------------------------------- | 775 | eoACPwrQualityConfiguration | 776 | eoACPwrQualityAvgVoltage | 777 | eoACPwrQualityAvgCurrent | 778 | eoACPwrQualityFrequency | 779 | eoACPwrQualityPowerUnitMultiplier | 780 | eoACPwrQualityPowerAccuracy | 781 | eoACPwrQualityTotalActivePower | 782 | eoACPwrQualityTotalReactivePower | 783 | eoACPwrQualityTotalApparentPower | 784 | eoACPwrQualityTotalPowerFactor | 785 | eoACPwrQualityThdAmpheres | 786 +-------------------------------------+ ^ 787 ^ ^ | 788 | | ------- 789 | ---- | 790 | | | 791 | | | 792 +-------------------------------------+ | | 793 | Power Phase Quality | | | 794 | ---------------------------------- | | | 795 | eoPhaseIndex | | | 796 | eoACPwrQualityPhaseAvgCurrent | | | 797 | eoACPwrQualityAvgCurrent | | | 798 | eoACPwrQualityFrequency | | | 799 | eoACPwrQualityPowerUnitMultiplier | | | 800 | eoACPwrQualityPowerAccuracy | | | 801 | eoACPwrQualityPhaseActivePower | | | 802 | eoACPwrQualityPhaseReactivePower | | | 803 | eoACPwrQualityPhaselApparentPower | | | 804 | eoACPwrQualityPhaseImpedance | | | 805 +-------------------------------------+ | | 806 | | 807 | | 808 +---------------------------------------------+ | 809 | Power Quality DEL Configuration | | 810 | | | 811 | eoACPwrQualityDelPhaseToNextPhaseVoltage | | 812 | eoACPwrQualityDelThdPhaseToNextPhaseVoltage | | 813 | eoACPwrQualityDelThdCurrent | | 814 +---------------------------------------------+ | 815 | 816 | 817 +---------------------------------------------+ 818 | Power Quality WYE Configuration | 819 | | 820 | eoACPwrQualityWyePhaseToNeutralVoltage | 821 | eoACPwrQualityWyePhaseCurrent | 822 | eoACPwrQualityWyeThdPhaseToNeutralVoltage | 823 +---------------------------------------------+ 825 Figure 2: UML diagram for the powerQualityMIB 827 (*) Link with the ENTITY-MIB 829 5.1. Energy Object Information 831 Refer to the "Energy Object Information" section in [EMAN- 832 FRAMEWORK] for background information. An energy aware device 833 is considered as an instance of a Energy Object as defined in 834 the [EMAN-FRAMEWORK]. 836 The Energy Object identity information is specified in the MIB 837 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the 838 eoTable. In this table, every Energy Object SHOULD have a 839 printable name eoName, and MUST HAVE a unique Energy Object 840 index entPhysicalUris and entPhysicalIndex. The ENERGY-AWARE-MIB 841 module returns the relationship (parent/child) between Energy 842 Objects. 844 EDITOR'S NOTE: this last sentence will have to be updated with 845 terms such as Aggregator, Proxy, etc... when the [EMAN- 846 FRAMEWORK] will stabilize. 848 5.2. Power State 850 Refer to the "Power States" section in [EMAN-FRAMEWORK] for 851 background information. 853 An Energy Object may have energy conservation modes called Power 854 States. Between the ON and OFF states of a device, there can be 855 several intermediate energy saving modes. Those energy saving 856 modes are called as Power States. 858 Power States, which represent universal states of power 859 management of an Energy Object, are specified by the 860 eoPowerState MIB object. The actual Power State is specified by 861 the eoPowerOperState MIB object, while the eoPowerAdminState MIB 862 object specifies the Power State requested for the Energy 863 Object. The difference between the values of eoPowerOperState 864 and eoPowerAdminState can be attributed that the Energy Object 865 is busy transitioning from eoPowerAdminState into the 866 eoPowerOperState, at which point it will update the content of 867 eoPowerOperState. In addition, the possible reason for change 868 in Power State is reported in eoPowerStateEnterReason. 869 Regarding eoPowerStateEnterReason, management stations and 870 Energy Objects should support any format of the owner string 871 dictated by the local policy of the organization. It is 872 suggested that this name contain at least the reason for the 873 transition change, and one or more of the following: IP address, 874 management station name, network manager's name, location, or 875 phone number. 877 The MIB objects eoPowerOperState, eoPowerAdminState , and 878 eoPowerStateEnterReason are contained in the eoPowerTable MIB 879 table. 881 The eoPowerStateTable table enumerates the maximum power usage 882 in watts, for every single supported Power State of each Power 883 State Set supported by the Energy Object. In addition, 884 PowerStateTable provides additional statistics: 885 eoPowerStateEnterCount, the number of times an entity has 886 visited a particular Power State, and eoPowerStateTotalTime, the 887 total time spent in a particular Power State of an Energy 888 Object. 890 5.2.1. Power State Set 892 There are several standards and implementations of Power State 893 Sets. A Energy Object can support one or multiple Power State 894 Set implementation(s) concurrently. 896 There are currently three Power State Sets advocated: 898 unknown(0) 899 IEEE1621(256) - [IEEE1621] 900 DMTF(512) - [DMTF] 901 EMAN(1024) - [EMAN-MONITORING-MIB] 903 The respective specific states related to each Power State Set 904 are specified in the following sections. The guidelines for 905 addition of new Power State Sets have been specified in the IANA 906 Considerations Section. 908 5.2.2. IEEE1621 Power State Set 910 The IEEE1621 Power State Set [IEEE1621] consists of 3 911 rudimentary states : on, off or sleep. 912 on(0) - The device is fully On and all features of the 913 device are in working mode. 914 off(1) - The device is mechanically switched off and does 915 not consume energy. 916 sleep(2) - The device is in a power saving mode, and some 917 features may not be available immediately. 919 The Textual Convention IANAPowerStateSet provides the proposed 920 numbering of the Power States within the IEEE1621 Power State 921 Set. 923 5.2.3. DMTF Power State Set 925 DMTF [DMTF] standards organization has defined a power profile 926 standard based on the CIM (Common Information Model) model that 927 consists of 15 power states ON (2), SleepLight (3), SleepDeep 928 (4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off- 929 Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10), 930 Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard 931 Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off- 932 Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF 933 standard is targeted for hosts and computers. Details of the 934 semantics of each Power State within the DMTF Power State Set 935 can be obtained from the DMTF Power State Management Profile 936 specification [DMTF]. 938 DMTF power profile extends ACPI power states. The following 939 table provides a mapping between DMTF and ACPI Power State Set: 941 --------------------------------------------------- 942 | DMTF | ACPI | 943 | Power State | Power State | 944 --------------------------------------------------- 945 | Reserved(0) | | 946 --------------------------------------------------- 947 | Reserved(1) | | 948 --------------------------------------------------- 949 | ON (2) | G0-S0 | 950 -------------------------------------------------- 951 | Sleep-Light (3) | G1-S1 G1-S2 | 952 -------------------------------------------------- 953 | Sleep-Deep (4) | G1-S3 | 954 -------------------------------------------------- 955 | Power Cycle (Off-Soft) (5) | G2-S5 | 956 --------------------------------------------------- 957 | Off-hard (6) | G3 | 958 --------------------------------------------------- 959 | Hibernate (Off-Soft) (7) | G1-S4 | 960 --------------------------------------------------- 961 | Off-Soft (8) | G2-S5 | 962 --------------------------------------------------- 963 | Power Cycle (Off-Hard) (9) | G3 | 964 --------------------------------------------------- 965 | Master Bus Reset (10) | G2-S5 | 966 --------------------------------------------------- 967 | Diagnostic Interrupt (11) | G2-S5 | 968 --------------------------------------------------- 969 | Off-Soft Graceful (12) | G2-S5 | 970 --------------------------------------------------- 971 | Off-Hard Graceful (13) | G3 | 972 --------------------------------------------------- 973 | MasterBus Reset Graceful (14) | G2-S5 | 974 --------------------------------------------------- 975 | Power Cycle off-soft Graceful (15)| G2-S5 | 976 --------------------------------------------------- 977 | Power Cycle off-hard Graceful (16)| G3 | 978 --------------------------------------------------- 979 Figure 3: DMTF and ACPI Powe State Set Mapping 981 The Textual Convention IANAPowerStateSet contains the proposed 982 numbering of the Power States within the DMTF Power State Set. 984 5.2.4. EMAN Power State Set 986 The EMAN Power State Set represents an attempt for a uniform 987 standard approach to model the different levels of power 988 consumption of a device. The EMAN Power States are an expansion 989 of the basic Power States as defined in IEEE1621 that also 990 incorporate the Power States defined in ACPI and DMTF. 991 Therefore, in addition to the non-operational states as defined 992 in ACPI and DMTF standards, several intermediate operational 993 states have been defined. 995 There are twelve Power States, that expand on IEEE1621 on,sleep 996 and off. The expanded list of Power States are divided into six 997 operational states, and six non-operational states. The lowest 998 non-operational state is 1 and the highest is 6. Each non- 999 operational state corresponds to an ACPI state [ACPI] 1000 corresponding to Global and System states between G3 (hard-off) 1001 and G1 (sleeping). For Each operational state represent a 1002 performance state, and may be mapped to ACPI states P0 (maximum 1003 performance power) through P5 (minimum performance and minimum 1004 power). 1006 An Energy Object may have fewer Power States than twelve and 1007 would then map several policy states to the same power state. 1008 Energy Object with more than twelve states, would choose which 1009 twelve to represent as power policy states. 1011 In each of the non-operational states (from mechoff(1) to 1012 ready(6)), the Power State preceding it is expected to have a 1013 lower power consumption and a longer delay in returning to an 1014 operational state: 1016 IEEE1621 Power(off): 1018 mechoff(1) : An off state where no entity features are 1019 available. The entity is unavailable. 1020 No energy is being consumed and the power 1021 connector can be removed. This 1022 corresponds to ACPI state G3. 1024 softoff(2) : Similar to mechoff(1), but some 1025 components remain powered or receive 1026 trace power so that the entity 1027 can be awakened from its off state. In 1028 softoff(2), no context is saved and the 1029 device typically requires a complete boot 1030 when awakened. This corresponds to ACPI 1031 state G2. 1033 IEEE1621 Power(sleep) 1035 hibernate(3): No entity features are available. The 1036 entity may be awakened without requiring 1037 a complete boot, but the time for 1038 availability is longer than sleep(4). An 1039 example for state hibernate(3) is a save 1040 to-disk state where DRAM context is not 1041 maintained. Typically, energy consumption 1042 is zero or close to zero. This 1043 corresponds to state G1, S4 in ACPI. 1045 sleep(4) : No entity features are available, except 1046 for out-of-band management, for example 1047 wake-up mechanisms. The time for 1048 availability is longer than standby(5). 1049 An example for state sleep(4) is a save- 1050 to-RAM state, where DRAM context is 1051 maintained. Typically, energy 1052 consumption is close to zero. This 1053 corresponds to state G1, S3 in ACPI. 1055 standby(5) : No entity features are available, except 1056 for out-of-band management, for example 1057 wake-up mechanisms. This mode is analogous 1058 to cold-standy. The time for availability 1059 is longer than ready(6). For example, the 1060 processor context is not maintained. 1061 Typically, energy consumption is close to 1062 zero. This corresponds to state G1, S2 in 1063 ACPI. 1065 ready(6) : No entity features are available, except 1066 for out-of-band management, for example 1067 wake-up mechanisms. This mode is 1068 analogous to hot-standby. The entity can 1069 be quickly transitioned into an 1070 operational state. For example, 1071 processors are not executing, but 1072 processor context is maintained. This 1073 corresponds to state G1, S1 in ACPI. 1075 IEEE1621 Power(on): 1077 lowMinus(7) : Indicates some entity features may not be 1078 available and the entity has selected 1079 measures/options to provide less than 1080 low(8) usage. This corresponds to 1081 ACPI State G0. This includes operational 1082 states lowMinus(7) to full(12). 1084 low(8) : Indicates some features may not be 1085 available and the entity has taken 1086 measures or selected options to provide 1087 less than mediumMinus(9) usage. 1089 mediumMinus(9): Indicates all entity features are 1090 available but the entity has taken 1091 measures or selected options to provide 1092 less than medium(10) usage. 1094 medium(10) : Indicates all entity features are 1095 available but the entity has taken 1096 measures or selected options to provide 1097 less than highMinus(11) usage. 1099 highMinus(11): Indicates all entity features are 1100 available and power usage is less 1101 than high(12). 1103 high(12) : Indicates all entity features are 1104 available and the entity is consuming the 1105 highest power. 1107 The Textual Convention IANAPowerStateSet contains the proposed 1108 numbering of the Power States within the EMAN Power State Set. 1110 5.3. Energy Object Usage Information 1112 Refer to the "Energy Object Usage Measurement" section in [EMAN- 1113 FRAMEWORK] for background information. 1115 For an Energy Object, power usage is reported using eoPower. 1116 The magnitude of measurement is based on the 1117 eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier 1118 Textual Convention (TC). Power measurement magnitude should 1119 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 1120 [IEC.62053-22] definition of unit multiplier for the SI (System 1121 International) units of measure. Measured values are 1122 represented in SI units obtained by BaseValue * 10 raised to the 1123 power of the scale. 1125 For example, if current power usage of an Energy Object is 3, it 1126 could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of 1127 eoPowerUnitMultiplier. Note that other measurements throughout 1128 the two MIB modules in this document use the same mechanism, 1129 including eoPowerStatePowerUnitMultiplier, 1130 eoEnergyUnitMultiplier, and eoACPwrQualityPowerUnitMultiplier. 1132 In addition to knowing the usage and magnitude, it is useful to 1133 know how a eoPower measurement was obtained. An NMS can use 1134 this to account for the accuracy and nature of the reading 1135 between different implementations. For this eoPowerOrigin 1136 describes whether the measurements were made at the device 1137 itself or from a remote source. The eoPowerMeasurementCaliber 1138 describes the method that was used to measure the power and can 1139 distinguish actual or estimated values. There may be devices in 1140 the network, which may not be able to measure or report power 1141 consumption. For those devices, the object 1142 eoPowerMeasurementCaliber shall report that measurement 1143 mechanism is "unavailable" and the eoPower measurement shall be 1144 "0". 1146 The nameplate power rating of an Energy Object is specified in 1147 eoPowerNameplate MIB object. 1149 5.4. Optional Power Usage Quality 1151 Refer to the "Optional Power Usage Quality" section in [EMAN- 1152 FRAMEWORK] for background information. 1154 The optional powerQualityMIB MIB module can be implemented to 1155 further describe power usage quality measurement. The 1156 powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 1157 standard to describe AC measurements. 1159 The powerQualityMIB MIB module contains a primary table, the 1160 eoACPwrQualityTable table, that defines power quality 1161 measurements for supported entPhysicalIndex entities, as a 1162 sparse extension of the eoPowerTable (with entPhysicalIndex as 1163 primary index). This eoACPwrQualityTable table contains such 1164 information as the configuration (single phase, DEL 3 phases, 1165 WYE 3 phases), voltage, frequency, power accuracy, total 1166 active/reactive power/apparent power, amperage, and voltage. 1168 In case of 3-phase power, the eoACPwrQualityPhaseTable 1169 additional table is populated with power quality measurements 1170 per phase (so double indexed by the entPhysicalIndex and 1171 eoPhaseIndex). This table, which describes attributes common to 1172 both WYE and DEL configurations, contains the average current, 1173 active/reactive/apparent power, power factor, and impedance. 1175 In case of 3-phase power with a DEL configuration, the 1176 eoACPwrQualityDelPhaseTable table describes the phase-to-phase 1177 power quality measurements, i.e., voltage and current. 1179 In case of 3-phase power with a Wye configuration, the 1180 eoACPwrQualityWyePhaseTable table describes the phase-to-neutral 1181 power quality measurements, i.e., voltage and current. 1183 5.5. Optional Energy Measurement 1185 Refer to the "Optional Energy and demand Measurement" section in 1186 [EMAN-FRAMEWORK] for the definition and terminology information. 1188 It is relevant to measure energy when there are actual power 1189 measurements from an Energy Object, and not when the power 1190 measurement is assumed or predicted as specified in the 1191 description clause of the object eoPowerMeasurementCaliber. 1193 Two tables are introduced to characterize energy measurement of 1194 an Energy Object: eoEnergyTable and eoEnergyParametersTable. 1195 Both energy and demand information can be represented via the 1196 eoEnergyTable. Energy information will be an accumulation with 1197 no interval. Demand information can be represented. 1198 The eoEnergyParametersTable consists of the parameters defining 1199 eoEnergyParametersIndex, an index of that specifies the setting 1200 for collection of energy measurements for an Energy Object, 1201 eoEnergyObjectIndex, linked to the entPhysicalIndex of the 1202 Energy Object, the duration of measurement intervals in seconds, 1203 (eoEnergyParametersIntervalLength), the number of successive 1204 intervals to be stored in the eoEnergyTable, 1205 (eoEnergyParametersIntervalNumber), the type of measurement 1206 technique (eoEnergyParametersIntervalMode), and a sample rate 1207 used to calculate the average (eoEnergyParametersSampleRate). 1208 Judicious choice of the sampling rate will ensure accurate 1209 measurement of energy while not imposing an excessive polling 1210 burden. 1212 There are three eoEnergyParametersIntervalMode types used for 1213 energy measurement collection: period, sliding, and total. The 1214 choices of the the three different modes of collection are based 1215 on IEC standard 61850-7-4. Note that multiple 1216 eoEnergyParametersIntervalMode types MAY be configured 1217 simultaneously. It is important to note that for a given Energy 1218 Object, multiple modes (periodic, total, sliding window) of 1219 energy measurement collection can be configured with the use of 1220 eoEnergyParametersIndex. However, simultaneous measurement in 1221 multiple modes for a given Energy Object depends on the Energy 1222 Object capability. 1224 These three eoEnergyParametersIntervalMode types are illustrated 1225 by the following three figures, for which: 1227 - The horizontal axis represents the current time, with the 1228 symbol <--- L ---> expressing the 1229 eoEnergyParametersIntervalLength, and the 1230 eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, 1231 ..., Sx where x is the value of 1232 eoEnergyParametersIntervalNumber. 1234 - The vertical axis represents the time interval of sampling and 1235 the value of eoEnergyConsumed can be obtained at the end of the 1236 sampling period. The symbol =========== denotes the duration of 1237 the sampling period. 1239 | | | =========== | 1240 |============ | | | 1241 | | | | 1242 | |============ | | 1243 | | | | 1244 | <--- L ---> | <--- L ---> | <--- L ---> | 1245 | | | | 1246 S1 S2 S3 S4 1248 Figure 4 : Period eoEnergyParametersIntervalMode 1250 A eoEnergyParametersIntervalMode type of 'period' specifies non- 1251 overlapping periodic measurements. Therefore, the next 1252 eoEnergyCollectionStartTime is equal to the previous 1253 eoEnergyCollectionStartTime plus 1254 eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... 1256 |============ | 1257 | | 1258 | <--- L ---> | 1259 | | 1260 | |============ | 1261 | | | 1262 | | <--- L ---> | 1263 | | | 1264 | | |============ | 1265 | | | | 1266 | | | <--- L ---> | 1267 | | | | 1268 | | | |============ | 1269 | | | | | 1270 | | | | <--- L ---> | 1271 S1 | | | | 1272 | | | | 1273 | | | | 1274 S2 | | | 1275 | | | 1276 | | | 1277 S3 | | 1278 | | 1279 | | 1280 S4 1282 Figure 5 : Sliding eoEnergyParametersIntervalMode 1284 A eoEnergyParametersIntervalMode type of 'sliding' specifies 1285 overlapping periodic measurements. 1287 | | 1288 |========================= | 1289 | | 1290 | | 1291 | | 1292 | <--- Total length ---> | 1293 | | 1294 S1 1296 Figure 6 : Total eoEnergyParametersIntervalMode 1298 A eoEnergyParametersIntervalMode type of 'total' specifies a 1299 continuous measurement since the last reset. The value of 1300 eoEnergyParametersIntervalNumber should be (1) one and 1301 eoEnergyParametersIntervalLength is ignored. 1303 The eoEnergyParametersStatus is used to start and stop energy 1304 usage logging. The status of this variable is "active" when 1305 all the objects in eoEnergyParametersTable are appropriate which 1306 in turn indicates if eoEnergyTable entries exist or not. 1308 The eoEnergyTable consists of energy measurements in 1309 eoEnergyConsumed, eoEnergyProduced and eoEnergyNet , the units 1310 of the measured energy eoEnergyUnitMultiplier, and the maximum 1311 observed energy within a window, eoEnergyMaxConsumed, 1312 eoEnergyMaxProduced. 1314 Measurements of the total energy consumed by an Energy Object 1315 may suffer from interruptions in the continuous measurement of 1316 energy consumption. In order to indicate such interruptions, 1317 the object eoEnergyDiscontinuityTime is provided for indicating 1318 the time of the last interruption of total energy measurement. 1319 eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] 1320 when the device was reset. 1322 The following example illustrates the eoEnergyTable and 1323 eoEnergyParametersTable: 1325 First, in order to estimate energy, a time interval to sample 1326 energy should be specified, i.e. 1327 eoEnergyParametersIntervalLength can be set to "900 seconds" or 1328 15 minutes and the number of consecutive intervals over which 1329 the maximum energy is calculated 1330 (eoEnergyParametersIntervalNumber) as "10". The sampling rate 1331 internal to the Energy Object for measurement of power usage 1332 (eoEnergyParametersSampleRate) can be "1000 milliseconds", as 1333 set by the Energy Object as a reasonable value. Then, the 1334 eoEnergyParametersStatus is set to active (value 1) to indicate 1335 that the Energy Object should start monitoring the usage per the 1336 eoEnergyTable. 1338 The indices for the eoEnergyTable are eoEnergyParametersIndex 1339 which identifies the index for the setting of energy measurement 1340 collection Energy Object, and eoEnergyCollectionStartTime, which 1341 denotes the start time of the energy measurement interval based 1342 on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the 1343 measured energy consumption over the time interval specified 1344 (eoEnergyParametersIntervalLength) based on the Energy Object 1345 internal sampling rate (eoEnergyParametersSampleRate). While 1346 choosing the values for the eoEnergyParametersIntervalLength and 1347 eoEnergyParametersSampleRate, it is recommended to take into 1348 consideration either the network element resources adequate to 1349 process and store the sample values, and the mechanism used to 1350 calculate the eoEnergyConsumed. The units are derived from 1351 eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be 1352 "100" with eoEnergyUnitMultiplier equal to 0, the measured 1353 energy consumption of the Energy Object is 100 watt-hours. The 1354 eoEnergyMaxConsumed is the maximum energy observed and that can 1355 be "150 watt-hours". 1357 The eoEnergyTable has a buffer to retain a certain number of 1358 intervals, as defined by eoEnergyParametersIntervalNumber. If 1359 the default value of "10" is kept, then the eoEnergyTable 1360 contains 10 energy measurements, including the maximum. 1362 Here is a brief explanation of how the maximum energy can be 1363 calculated. The first observed energy measurement value is 1364 taken to be the initial maximum. With each subsequent 1365 measurement, based on numerical comparison, maximum energy may 1366 be updated. The maximum value is retained as long as the 1367 measurements are taking place. Based on periodic polling of 1368 this table, an NMS could compute the maximum over a longer 1369 period, i.e. a month, 3 months, or a year. 1371 5.6. Fault Management 1373 [EMAN-REQ] specifies requirements about Power States such as 1374 "the current power state" , "the time of the last state change", 1375 "the total time spent in each state", "the number of transitions 1376 to each state" etc. Some of these requirements are fulfilled 1377 explicitly by MIB objects such as eoPowerOperState, 1378 eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the 1379 other requirements are met via the SNMP NOTIFICATION mechanism. 1380 eoPowerStateChange SNMP notification which is generated when the 1381 value(s) of ,eoPowerStateIndex, eoPowerOperState, 1382 eoPowerAdminState have changed. 1384 6. Discovery 1386 It is foreseen that most Energy Objects will require the 1387 implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a 1388 prerequisite for this MIB module. In such a case, eoPowerTable 1389 of the EMAN-MON-MIB is a sparse extension of the eoTable of 1390 ENERGY-AWARE-MIB. Every Energy Object MUST implement 1391 entPhysicalIndex, entPhysicalUris and entPhysicalName 1392 from the ENTITY-MIB [RFC4133]. As the index for the primary 1393 Energy Object, entPhysicalIndex is used. 1395 The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- 1396 MIB], if available, in order to discover all the Energy Objects 1397 and the relationships between those (notion of Parent/Child). 1398 In the ENERGY-AWARE-MIB module tables, the Energy Objects are 1399 indexed by the entPhysicalIndex. 1401 If an implementation of the ENERGY-AWARE-MIB module is available 1402 in the local SNMP context, for the same Energy Object, the 1403 entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The 1404 entPhysicalIndex characterizes the Energy Object in the 1405 energyObjectMib and powerQualityMIB MIB modules (this document). 1407 From there, the NMS must poll the eoPowerStateTable (specified 1408 in the energyObjectMib module in this document), which 1409 enumerates, amongst other things, the maximum power usage. As 1410 the entries in eoPowerStateTable table are indexed by the 1411 Energy Object ( entPhysicalIndex), by the Power State Set 1412 (eoPowerStateIndex), the maximum power usage is discovered per 1413 Energy Object, per Power State Set, and per Power Usage. In 1414 other words, polling the eoPowerStateTable allows the discovery 1415 of each Power State within every Power State Set supported by 1416 the Energy Object. 1418 If the Energy Object is an Aggregator or a Proxy, the MIB module 1419 would be populated with the Energy Object Parent and Children 1420 information, which have their own Energy Object index value ( 1421 entPhysicalIndex). However, the parent/child relationship must 1422 be discovered thanks to the ENERGY-AWARE-MIB module. 1424 Finally, the NMS can monitor the Power Quality thanks to the 1425 powerQualityMIB MIB module, which reuses the entPhysicalIndex to 1426 index the Energy Object. 1428 7. Link with the other IETF MIBs 1430 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 1432 RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the 1433 physical entities of a networking device (router, switch, etc.) 1434 and those physical entities indexed by entPhysicalIndex. From 1435 an energy-management standpoint, the physical entities that 1436 consume or produce energy are of interest. 1438 RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that 1439 provides a standardized way of obtaining information (current 1440 value of the sensor, operational status of the sensor, and the 1441 data units precision) from sensors embedded in networking 1442 devices. Sensors are associated with each index of 1443 entPhysicalIndex of the ENTITY-MIB[RFC4133]. While the focus of 1444 the Power and Energy Monitoring MIB is on measurement of power 1445 usage of networking equipment indexed by the ENTITY MIB, this 1446 MIB proposes a customized power scale for power measurement and 1447 different power state states of networking equipment, and 1448 functionality to configure the power state states. 1450 When this MIB module is used to monitor the power usage of 1451 devices like routers and switches, the ENTITY-MIB and ENTITY- 1452 SENSOR MIB SHOULD be implemented. In such cases, the Energy 1453 Objects are modeled by the entPhysicalIndex through the 1454 entPhysicalEntity MIB object specified in the eoTable in the 1455 ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. 1457 However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI 1458 C12.x accuracy classes required for electricity (i.e., 1%, 2%, 1459 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 1460 represents "The number of decimal places of precision in fixed- 1461 point sensor values returned by the associated entPhySensorValue 1462 object". The ANSI and IEC Standards are used for power 1463 measurement and these standards require that we use an accuracy 1464 class, not the scientific-number precision model specified in 1465 RFC3433. The eoPowerAccuracy MIB object models this accuracy. 1466 Note that eoPowerUnitMultipler represents the scale factor per 1467 IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], 1468 which is a more logical representation for power measurements 1469 (compared to entPhySensorScale), with the mantissa and the 1470 exponent values X * 10 ^ Y. 1472 Power measurements specifying the qualifier 'UNITS' for each 1473 measured value in watts are used in the LLDP-EXT-MED-MIB, POE 1474 [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier 1475 is used for the power measurement values. 1477 One cannot assume that the ENTITY-MIBand ENTITY-SENSOR MIB are 1478 implemented for all Energy Objects that need to be monitored. A 1479 typical example is a converged building gateway, monitoring 1480 several other devices in the building, doing the proxy between 1481 SNMP and a protocol like BACNET. Another example is the home 1482 energy controller. In such cases, the eoPhysicalEntity value 1483 contains the zero value, thanks to PhysicalIndexOrZero textual 1484 convention. 1486 The eoPower is similar to entPhySensorValue [RFC3433] and the 1487 eoPowerUnitMultipler is similar to entPhySensorScale. 1489 7.2. Link with the ENTITY-STATE MIB 1491 For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE 1492 MIB [RFC4268] specifies the operational states (entStateOper: 1493 unknown, enabled, disabled, testing), the alarm (entStateAlarm: 1494 unknown, underRepair, critical, major, minor, warning, 1495 indeterminate) and the possible values of standby states 1496 (entStateStandby: unknown, hotStandby, coldStandby, 1497 providingService). 1499 From a power monitoring point of view, in contrast to the entity 1500 operational states of entities, Power States are required, as 1501 proposed in the Power and Energy Monitoring MIB module. Those 1502 Power States can be mapped to the different operational states 1503 in the ENTITY-STATE MIB, if a formal mapping is required. For 1504 example, the entStateStandby "unknown", "hotStandby", 1505 "coldStandby", states could map to the Power State "unknown", 1506 "ready", "standby", respectively, while the entStateStandby 1507 "providingService" could map to any "low" to "high" Power State. 1509 7.3. Link with the POWER-OVER-ETHERNET MIB 1511 Power-over-Ethernet MIB [RFC3621] provides an energy monitoring 1512 and configuration framework for power over Ethernet devices. 1513 The RFC introduces a concept of a port group on a switch to 1514 define power monitoring and management policy and does not use 1515 the entPhysicalIndex as the index. Indeed, the 1516 pethMainPseConsumptionPower is indexed by the 1517 pethMainPseGroupIndex, which has no mapping with the 1518 entPhysicalIndex. 1520 One cannot assume that the Power-over-Ethernet MIB is 1521 implemented for all Energy Objects that need to be monitored. A 1522 typical example is a converged building gateway, monitoring 1523 several other devices in the building, doing the proxy between 1524 SNMP and a protocol like BACNET. Another example is the home 1525 energy controller. In such cases, the eoethPortIndex and 1526 eoethPortGrpIndex values contain the zero value, thanks to new 1527 PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero 1528 conventions. 1530 However, if the Power-over-Ethernet MIB [RFC3621] is supported, 1531 the Energy Object eoethPortIndex and eoethPortGrpIndex contain 1532 the pethPsePortIndex and pethPsePortGroupIndex, respectively. 1534 As a consequence, the entPhysicalIndex MIB object has been kept 1535 as the unique Energy Object index. 1537 Note that, even though the Power-over-Ethernet MIB [RFC3621] was 1538 created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse 1539 the precision notion from the ENTITY-SENSOR MIB, i.e. the 1540 entPhySensorPrecision MIB object. 1542 7.4. Link with the UPS MIB 1544 To protect against unexpected power disruption, data centers and 1545 buildings make use of Uninterruptible Power Supplies (UPS). To 1546 protect critical assets, a UPS can be restricted to a particular 1547 subset or domain of the network. UPS usage typically lasts only 1548 for a finite period of time, until normal power supply is 1549 restored. Planning is required to decide on the capacity of the 1550 UPS based on output power and duration of probable power outage. 1551 To properly provision UPS power in a data center or building, it 1552 is important to first understand the total demand required to 1553 support all the entities in the site. This demand can be 1554 assessed and monitored via the Power and Energy Monitoring MIB. 1556 UPS MIB [RFC1628] provides information on the state of the UPS 1557 network. Implementation of the UPS MIB is useful at the 1558 aggregate level of a data center or a building. The MIB module 1559 contains several groups of variables: 1561 - upsIdent: Identifies the UPS entity (name, model, etc.). 1563 - upsBattery group: Indicates the battery state 1564 (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) 1566 - upsInput group: Characterizes the input load to the UPS 1567 (number of input lines, voltage, current, etc.). 1569 - upsOutput: Characterizes the output from the UPS (number of 1570 output lines, voltage, current, etc.) 1572 - upsAlarms: Indicates the various alarm events. 1574 The measurement of power in the UPS MIB is in Volts, Amperes and 1575 Watts. The units of power measurement are RMS volts and RMS 1576 Amperes. They are not based on the EntitySensorDataScale and 1577 EntitySensorDataPrecision of ENTITY-SENSOR-MIB. 1579 Both the Power and Energy Monitoring MIB and the UPS MIB may be 1580 implemented on the same UPS SNMP agent, without conflict. In 1581 this case, the UPS device itself is the Energy Object Parent and 1582 any of the UPS meters or submeters are the Energy Object 1583 Children. 1585 7.5. Link with the LLDP and LLDP-MED MIBs 1587 The LLDP Protocol is a Data Link Layer protocol used by network 1588 devices to advertise their identities, capabilities, and 1589 interconnections on a LAN network. 1591 The Media Endpoint Discovery is an enhancement of LLDP, known as 1592 LLDP-MED. The LLDP-MED enhancements specifically address voice 1593 applications. LLDP-MED covers 6 basic areas: capability 1594 discovery, LAN speed and duplex discovery, network policy 1595 discovery, location identification discovery, inventory 1596 discovery, and power discovery. 1598 Of particular interest to the current MIB module is the power 1599 discovery, which allows the endpoint device (such as a PoE 1600 phone) to convey power requirements to the switch. In power 1601 discovery, LLDP-MED has four Type Length Values (TLVs): power 1602 type, power source, power priority and power value. 1603 Respectively, those TLVs provide information related to the type 1604 of power (power sourcing entity versus powered device), how the 1605 device is powered (from the line, from a backup source, from 1606 external power source, etc.), the power priority (how important 1607 is it that this device has power?), and how much power the 1608 device needs. 1610 The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 1611 actually comes from the Power-over-Ethernet MIB [RFC3621]. If 1612 the Power-over-Ethernet MIB [RFC3621] is supported, the exact 1613 value from the pethPsePortPowerPriority [RFC3621] is copied over 1614 in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise 1615 the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From 1616 the Power and Energy Monitoring MIB, it is possible to identify 1617 the pethPsePortPowerPriority [RFC3621], thanks to the 1618 eoethPortIndex and eoethPortGrpIndex. 1620 The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to 1621 eoPowerOrigin in indicating if the power for an attached device 1622 is local or from a remote device. If the LLDP-MED MIB is 1623 supported, the following mapping can be applied to the 1624 eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and 1625 local(3) can be mapped to remote(2) and self(1), respectively. 1627 8. Implementation Scenario 1629 This section provides an illustrative example scenario for the 1630 implementation of the Energy Object, including Energy Object 1631 Parent and Energy Object Child relationships. 1633 Example Scenario of a campus network: Switch with PoE Endpoints 1634 with further connected Devices 1636 The campus network consists of switches that provide LAN 1637 connectivity. The switch with PoE ports is located in wiring 1638 closet. PoE IP phones are connected to the switch. The IP 1639 phones draw power from the PoE ports of the switch. In 1640 addition, a PC is daisy-chained from the IP phone for LAN 1641 connectivity. 1643 The IP phone consumes power from the PoE switch, while the PC 1644 consumes power from the wall outlet. 1646 The switch has implementations of ENTITY-MIB [RFC4133] and 1647 ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have 1648 implementation of the ENTITY-MIB, but has an implementation of 1649 ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following 1650 attributes, entPhysicalIndex "1", and eoUUID "UUID 1000". The 1651 power usage of the switch is "440 Watts". The switch does not 1652 have an Energy Object Parent. 1654 The PoE switch port has the following attributes: The switch 1655 port has entPhysicalIndex "3", and eoUUID is "UUID 1000:3". The 1656 power metered at the POE switch port is "12 watts". In this 1657 example, the POE switch port has the switch as the Energy Object 1658 Parent, with its eoParentID of "1000". 1660 The attributes of the PC are given below. The PC does not have 1661 an entPhysicalIndex, andthe eoUUID is "UUID 1000:57 ". The PC 1662 has an Energy Object Parent, i.e. the switch port whose eoUUID 1663 is "UUID 1000:3". The power usage of the PC is "120 Watts" and 1664 is communicated to the switch port. 1666 This example illustrates the important distinction between the 1667 Energy Object Children: The IP phone draws power from the 1668 switch, while the PC has LAN connectivity from the phone, but is 1669 powered from the wall outlet. However, the Energy Object Parent 1670 sends power control messages to both the Energy Object Children 1671 (IP phone and PC) and the Children react to those messages. 1673 |-------------------------------------------------------| 1674 | Switch | 1675 |=======================================================| 1676 | Switch | Switch | Switch | Switch | 1677 | entPhyIndx | UUID |eoParentId | eoPower | 1678 | ===================================================== | 1679 | 1 | UUID 1000 | null | 440 | 1680 | ===================================================== | 1681 | | 1682 | SWITCH PORT | 1683 | ===================================================== | 1684 | | Switch | Switch | Switch | Switch | 1685 | | Port | Port | Port | Port | 1686 | | entPhyIndx | UUID | eoParentId | eoPower | 1687 | ===================================================== | 1688 | | 3 | UUID 1000:3 | 1000 | 12 | 1689 | ======================================================| 1690 | ^ 1691 | | 1692 |-----------------------------------|------------------- 1693 | 1694 | 1695 POE IP PHONE | 1696 | 1697 | 1698 ====================================================== 1699 | IP phone | IP phone | IP phone | IP phone | 1700 | entPhyIndx | UUID | eoParentID | eoPower | 1701 ====================================================== 1702 | Null | UUID 1000:31| UUID 1000:3 | 12 | 1703 ===================================================== 1704 | 1705 | 1706 PC connected to switch via IP phone | 1707 | 1708 ================================================== 1709 | PC | PC |PC | PC | 1710 |eoPhyIndx | UUID |eoParentID | eoPower | 1711 ================================================== 1712 | Null | UUID1000:57 | UUID 1000:3 | 120 | 1713 ================================================= 1715 Figure 1: Example scenario 1717 9. Structure of the MIB 1719 The primary MIB object in this MIB module is the 1720 energyObjectMibObject. The eoPowerTable table of 1721 energyObjectMibObject describes the power measurement attributes 1722 of an Energy Object entity. The notion of identity of the device 1723 in terms of uniquely identification of the Energy Object and its 1724 relationship to other entities in the network are addressed in 1725 [EMAN-AWARE-MIB]. 1727 Logically, this MIB module is a sparse extension of the 1728 [EMAN-AWARE-MIB] module. Thus the following requirements which 1729 are applied to [EMAN-AWARE-MIB] are also applicable. As a 1730 requirement for this MIB module, [EMAN-AWARE-MIB] should be 1731 implemented and the three MIB objects from ENTITY-MIB 1732 (entPhysicalIndex, entPhysicalName and entPhysicalUris) MUST be 1733 implemented. 1735 The power measurement of an Energy Object contains information 1736 describing its power usage (eoPower) and its current power state 1737 (eoPowerOperState). In addition to power usage, additional 1738 information describing the units of measurement 1739 (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage 1740 measurement was obtained (eoPowerMeasurementCaliber), the 1741 source of power (eoPowerOrigin) and the type of power 1742 (eoPowerCurrentTtype) are described. 1744 An Energy Object may contain an optional eoPowerQuality table 1745 that describes the electrical characteristics associated with 1746 the current power state and usage. 1748 An Energy Object may contain an optional eoEnergyTable to 1749 describe energy measurement information over time. 1751 An Energy Object may also contain optional battery information 1752 associated with this entity. 1754 10. MIB Definitions 1756 -- ************************************************************ 1757 -- 1758 -- 1759 -- This MIB is used to monitor power usage of network 1760 -- devices 1761 -- 1762 -- ************************************************************* 1764 ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN 1766 IMPORTS 1767 MODULE-IDENTITY, 1768 OBJECT-TYPE, 1769 NOTIFICATION-TYPE, 1770 mib-2, 1771 Integer32, Counter32, TimeTicks 1772 FROM SNMPv2-SMI 1773 TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval, 1774 TimeStamp 1775 FROM SNMPv2-TC 1776 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP 1777 FROM SNMPv2-CONF 1778 OwnerString 1779 FROM RMON-MIB 1780 entPhysicalIndex, PhysicalIndex 1781 FROM ENTITY-MIB; 1783 energyObjectMib MODULE-IDENTITY 1784 LAST-UPDATED "201202150000Z" -- 15 March 2012 1786 ORGANIZATION "IETF EMAN Working Group" 1787 CONTACT-INFO 1788 "WG charter: 1789 http://datatracker.ietf.org/wg/eman/charter/ 1791 Mailing Lists: 1792 General Discussion: eman@ietf.org 1794 To Subscribe: 1795 https://www.ietf.org/mailman/listinfo/eman 1797 Archive: 1798 http://www.ietf.org/mail-archive/web/eman 1800 Editors: 1801 Mouli Chandramouli 1802 Cisco Systems, Inc. 1803 Sarjapur Outer Ring Road 1804 Bangalore, 1805 IN 1806 Phone: +91 80 4426 3947 1807 Email: moulchan@cisco.com 1809 Brad Schoening 1810 44 Rivers Edge Drive 1811 Little Silver, NJ 07739 1812 US 1813 Email: brad@bradschoening.com 1815 Juergen Quittek 1816 NEC Europe Ltd. 1818 NEC Laboratories Europe 1819 Network Research Division 1820 Kurfuersten-Anlage 36 1821 Heidelberg 69115 1822 DE 1823 Phone: +49 6221 4342-115 1824 Email: quittek@neclab.eu 1826 Thomas Dietz 1827 NEC Europe Ltd. 1828 NEC Laboratories Europe 1829 Network Research Division 1830 Kurfuersten-Anlage 36 1831 69115 Heidelberg 1832 DE 1833 Phone: +49 6221 4342-128 1834 Email: Thomas.Dietz@nw.neclab.eu 1836 Benoit Claise 1837 Cisco Systems, Inc. 1838 De Kleetlaan 6a b1 1839 Degem 1831 1840 Belgium 1841 Phone: +32 2 704 5622 1842 Email: bclaise@cisco.com" 1844 DESCRIPTION 1845 "This MIB is used to monitor power and energy in 1846 devices. 1848 This table sparse extension of the eoTable 1849 from the ENERGY-AWARE-MIB. As a requirement 1850 [EMAN-AWARE-MIB] should be implemented and 1851 three MIB objects from ENTITY-MIB 1852 (entPhysicalIndex, entPhysicalName and 1853 entPhysicalUris)MUST be implemented. " 1855 REVISION 1856 "201202150000Z" -- 15 March 2012 1858 DESCRIPTION 1859 "Initial version, published as RFC XXXX." 1861 ::= { mib-2 xxx } 1863 energyObjectMibNotifs OBJECT IDENTIFIER 1864 ::= { energyObjectMib 0 } 1866 energyObjectMibObjects OBJECT IDENTIFIER 1867 ::= { energyObjectMib 1 } 1869 energyObjectMibConform OBJECT IDENTIFIER 1870 ::= { energyObjectMib 2 } 1872 -- Textual Conventions 1874 IANAPowerStateSet ::= TEXTUAL-CONVENTION 1875 STATUS current 1876 DESCRIPTION 1878 "IANAPowerState is a textual convention that describes 1879 Power State Sets and Power State Set Values an Energy Object 1880 supports. IANA has created a registry of Power State supported 1881 by an Energy Object and IANA shall administer the list of Power 1882 State Sets and Power States. 1884 The textual convention assumes that power states in a power 1885 state set are limited to 255 distinct values. For a Power 1886 State Set S, the named number with the value S * 256 is 1887 allocated to indicate the power state set. For a Power State X 1888 in the Power State S, the named number with the value S * 256 1889 + X + 1 is allocated to represent the power state." 1891 REFERENCE 1892 "http://www.iana.org/assignments/eman 1893 RFC EDITOR NOTE: please change the previous URL if this is 1894 not the correct one after IANA assigned it." 1896 SYNTAX INTEGER { 1897 other(0), -- indicates other set 1898 unknown(255), -- unknown power state 1900 ieee1621(256), -- indicates IEEE1621 set 1901 ieee1621On(257), 1902 ieee1621Off(258), 1903 ieee1621Sleep(259), 1905 dmtf(512), -- indicates DMTF set 1906 dmtfOn(513), 1907 dmtfSleepLight(514), 1908 dmtfSleepDeep(515), 1909 dmtfOffHard(516), 1910 dmtfOffSoft(517), 1911 dmtfHibernate(518), 1912 dmtfPowerOffSoft(519), 1913 dmtfPowerOffHard(520), 1914 dmtfMasterBusReset(521), 1915 dmtfDiagnosticInterrapt(522), 1916 dmtfOffSoftGraceful(523), 1917 dmtfOffHardGraceful(524), 1918 dmtfMasterBusResetGraceful(525), 1919 dmtfPowerCycleOffSoftGraceful(526), 1920 dmtfPowerCycleHardGraceful(527), 1922 eman(1024), -- indicates EMAN set 1923 emanmechoff(1025), 1924 emansoftoff(1026), 1925 emanhibernate(1027), 1926 emansleep(1028), 1927 emanstandby(1029), 1928 emanready(1030), 1929 emanlowMinus(1031), 1930 emanlow(1032), 1931 emanmediumMinus(1033), 1932 emanmedium(1034), 1933 emanhighMinus(1035), 1934 emanhigh(1036) 1935 } 1937 UnitMultiplier ::= TEXTUAL-CONVENTION 1938 STATUS current 1939 DESCRIPTION 1940 "The Unit Multiplier is an integer value that represents 1941 the IEEE 61850 Annex A units multiplier associated with 1942 the integer units used to measure the power or energy. 1944 For example, when used with eoPowerUnitMultiplier, -3 1945 represents 10^-3 or milliwatts." 1946 REFERENCE 1947 "The International System of Units (SI), 1948 National Institute of Standards and Technology, 1949 Spec. Publ. 330, August 1991." 1950 SYNTAX INTEGER { 1951 yocto(-24), -- 10^-24 1952 zepto(-21), -- 10^-21 1953 atto(-18), -- 10^-18 1954 femto(-15), -- 10^-15 1955 pico(-12), -- 10^-12 1956 nano(-9), -- 10^-9 1957 micro(-6), -- 10^-6 1958 milli(-3), -- 10^-3 1959 units(0), -- 10^0 1960 kilo(3), -- 10^3 1961 mega(6), -- 10^6 1962 giga(9), -- 10^9 1963 tera(12), -- 10^12 1964 peta(15), -- 10^15 1965 exa(18), -- 10^18 1966 zetta(21), -- 10^21 1967 yotta(24) -- 10^24 1968 } 1970 -- Objects 1972 eoPowerTable OBJECT-TYPE 1973 SYNTAX SEQUENCE OF EoPowerEntry 1974 MAX-ACCESS not-accessible 1975 STATUS current 1976 DESCRIPTION 1977 "This table lists Energy Objects." 1978 ::= { energyObjectMibObjects 1 } 1980 eoPowerEntry OBJECT-TYPE 1981 SYNTAX EoPowerEntry 1982 MAX-ACCESS not-accessible 1983 STATUS current 1984 DESCRIPTION 1985 "An entry describes the power usage of an Energy Object." 1987 INDEX { entPhysicalIndex } 1988 ::= { eoPowerTable 1 } 1990 EoPowerEntry ::= SEQUENCE { 1992 eoPower Integer32, 1993 eoPowerNameplate Integer32, 1994 eoPowerUnitMultiplier UnitMultiplier, 1995 eoPowerAccuracy Integer32, 1996 eoPowerMeasurementCaliber INTEGER, 1997 eoPowerCurrentType INTEGER, 1998 eoPowerOrigin INTEGER, 1999 eoPowerAdminState IANAPowerStateSet, 2000 eoPowerOperState IANAPowerStateSet, 2001 eoPowerStateEnterReason OwnerString 2002 } 2004 eoPower OBJECT-TYPE 2005 SYNTAX Integer32 2006 UNITS "Watts" 2007 MAX-ACCESS read-only 2008 STATUS current 2009 DESCRIPTION 2010 "This object indicates the power measured for the Energy 2011 Object. For alternating current, this value is obtained 2012 as an average over fixed number of AC cycles. . This 2013 value is specified in SI units of watts with the 2014 magnitude of watts (milliwatts, kilowatts, etc.) 2015 indicated separately in eoPowerUnitMultiplier. The 2016 accuracy of the measurement is specfied in 2017 eoPowerAccuracy. The direction of power flow is indicated 2018 by the sign on eoPower. If the Energy Object is consuming 2019 power, the eoPower value will be positive. If the Energy 2020 Object is producing power, the eoPower value will be 2021 negative. 2023 The eoPower MUST be less than or equal to the maximum 2024 power that can be consumed at the power state specified 2025 by eoPowerState. 2027 The eoPowerMeasurementCaliber object specifies how the 2028 usage value reported by eoPower was obtained. The eoPower 2029 value must report 0 if the eoPowerMeasurementCaliber is 2030 'unavailable'. For devices that can not measure or 2031 report power, this option can be used." 2032 ::= { eoPowerEntry 1 } 2034 eoPowerNameplate OBJECT-TYPE 2035 SYNTAX Integer32 2036 UNITS "Watts" 2037 MAX-ACCESS read-only 2038 STATUS current 2039 DESCRIPTION 2040 "This object indicates the rated maximum consumption for 2041 the fully populated Energy Object. The nameplate power 2042 requirements are the maximum power numbers and in almost 2043 all cases, are well above the expected operational 2044 consumption. The eoPowerNameplate is widely used for 2045 power provisioning. This value is specified in either 2046 units of watts or voltage and current. The units are 2047 therefore SI watts or equivalent Volt-Amperes with the 2048 magnitude (milliwatts, kilowatts, etc.) indicated 2049 separately in eoPowerUnitMultiplier." 2050 ::= { eoPowerEntry 2 } 2052 eoPowerUnitMultiplier OBJECT-TYPE 2053 SYNTAX UnitMultiplier 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The magnitude of watts for the usage value in eoPower 2058 and eoPowerNameplate." 2059 ::= { eoPowerEntry 3 } 2061 eoPowerAccuracy OBJECT-TYPE 2062 SYNTAX Integer32 (0..10000) 2063 UNITS "hundredths of percent" 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "This object indicates a percentage value, in 100ths of a 2068 percent, representing the assumed accuracy of the usage 2069 reported by eoPower. For example: The value 1010 means 2070 the reported usage is accurate to +/- 10.1 percent. This 2071 value is zero if the accuracy is unknown or not 2072 applicable based upon the measurement method. 2074 ANSI and IEC define the following accuracy classes for 2075 power measurement: 2076 IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. 2077 ANSI C12.20 class 0.2, 0.5" 2078 ::= { eoPowerEntry 4 } 2080 eoPowerMeasurementCaliber OBJECT-TYPE 2081 SYNTAX INTEGER { 2082 unavailable(1) , 2083 unknown(2), 2084 actual(3) , 2085 estimated(4), 2086 presumed(5) } 2087 MAX-ACCESS read-only 2088 STATUS current 2089 DESCRIPTION 2090 "This object specifies how the usage value reported by 2091 eoPower was obtained: 2093 - unavailable(1): Indicates that the usage is not 2094 available. In such a case, the eoPower value must be 0 2095 for devices that can not measure or report power this 2096 option can be used. 2098 - unknown(2): Indicates that the way the usage was 2099 determined is unknown. In some cases, entities report 2100 aggregate power on behalf of another device. In such 2101 cases it is not known whether the usage reported is 2102 actual(2), estimated(3) or presumed (4). 2104 - actual(3): Indicates that the reported usage was 2105 measured by the entity through some hardware or direct 2106 physical means. The usage data reported is not presumed 2107 (4) or estimated (3) but the real apparent current energy 2108 consumption rate. 2110 - estimated(4): Indicates that the usage was not 2111 determined by physical measurement. The value is a 2112 derivation based upon the device type, state, and/or 2113 current utilization using some algorithm or heuristic. It 2114 is presumed that the entity's state and current 2115 configuration were used to compute the value. 2117 - presumed(5): Indicates that the usage was not 2118 determined by physical measurement, algorithm or 2119 derivation. The usage was reported based upon external 2120 tables, specifications, and/or model information. For 2121 example, a PC Model X draws 200W, while a PC Model Y 2122 draws 210W" 2124 ::= { eoPowerEntry 5 } 2126 eoPowerCurrentType OBJECT-TYPE 2127 SYNTAX INTEGER { 2128 ac(1), 2129 dc(2), 2130 unknown(3) 2131 } 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "This object indicates whether the eoUsage for the 2136 Energy Object reports alternative current AC(1), direct 2137 current DC(2), or that the current type is unknown(3)." 2138 ::= { eoPowerEntry 6 } 2140 eoPowerOrigin OBJECT-TYPE 2141 SYNTAX INTEGER { 2142 self (1), 2143 remote (2) 2144 } 2145 MAX-ACCESS read-only 2146 STATUS current 2147 DESCRIPTION 2148 "This object indicates the source of power measurement 2149 and can be useful when modeling the power usage of 2150 attached devices. The power measurement can be performed 2151 by the entity itself or the power measurement of the 2152 entity can be reported by another trusted entity using a 2153 protocol extension. A value of self(1) indicates the 2154 measurement is performed by the entity, whereas remote(2) 2155 indicates that the measurement was performed by another 2156 entity." 2157 ::= { eoPowerEntry 7 } 2159 eoPowerAdminState OBJECT-TYPE 2160 SYNTAX IANAPowerStateSet 2161 MAX-ACCESS read-write 2162 STATUS current 2163 DESCRIPTION 2164 "This object specifies the desired Power State and the 2165 Power State Set for the Energy Object. Note that 2166 other(0) is not a Power State Set and unknown(255) is 2167 not a Power State as such, but simply an indication that 2168 the Power State of the Energy Object is unknown. 2169 Possible values of eoPowerAdminState within the Power 2170 State Set are registered at IANA. 2171 A current list of assignments can be found at 2172 2173 RFC-EDITOR: please check the location after IANA" 2174 ::= { eoPowerEntry 8 } 2176 eoPowerOperState OBJECT-TYPE 2177 SYNTAX IANAPowerStateSet 2178 MAX-ACCESS read-only 2179 STATUS current 2180 DESCRIPTION 2182 "This object specifies the current operational Power 2183 State and the Power State Set for the Energy Object. 2184 other(0) is not a Power State Set and unknown(255) is 2185 not a Power State as such, but simply an indication that 2186 the Power State of the Energy Object is unknown. 2188 Possible values of eoPowerAdminState within the Power 2189 State Set are registered at IANA. 2191 A current list of assignments can be found at 2192 2193 RFC-EDITOR: please check the location after IANA" 2195 ::= { eoPowerEntry 9 } 2197 eoPowerStateEnterReason OBJECT-TYPE 2198 SYNTAX OwnerString 2199 MAX-ACCESS read-create 2200 STATUS current 2201 DESCRIPTION 2202 "This string object describes the reason for the 2203 eoPowerAdminState 2204 transition Alternatively, this string may contain with 2205 the entity that configured this Energy Object to this 2206 Power State." 2207 DEFVAL { "" } 2208 ::= { eoPowerEntry 10 } 2210 eoPowerStateTable OBJECT-TYPE 2211 SYNTAX SEQUENCE OF EoPowerStateEntry 2212 MAX-ACCESS not-accessible 2213 STATUS current 2214 DESCRIPTION 2215 "This table enumerates the maximum power usage, in watts, 2216 for every single supported Power State of each Energy 2217 Object. 2219 This table has an expansion-dependent relationship on the 2220 eoPowerTable, containing rows describing each Power State 2221 for the corresponding Energy Object. For every Energy 2222 Object in the eoPowerTable, there is a corresponding 2223 entry in this table." 2224 ::= { energyObjectMibObjects 2 } 2226 eoPowerStateEntry OBJECT-TYPE 2227 SYNTAX EoPowerStateEntry 2228 MAX-ACCESS not-accessible 2229 STATUS current 2230 DESCRIPTION 2231 "A eoPowerStateEntry extends a corresponding 2232 eoPowerEntry. This entry displays max usage values at 2233 every single possible Power State supported by the Energy 2234 Object. 2235 For example, given the values of a Energy Object 2236 corresponding to a maximum usage of 11W at the 2237 state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High): 2239 State MaxUsage Units 2240 1 (mechoff 0 W 2241 2 (softoff) 0 W 2242 3 (hibernate) 0 W 2243 4 (sleep) 0 W 2244 5 (standby) 0 W 2245 6 (ready) 8 W 2246 7 (lowMinus) 8 W 2247 8 (low) 11 W 2248 9 (medimMinus) 11 W 2249 10 (medium) 11 W 2250 11 (highMinus) 11 W 2251 12 (high) 11 W 2253 Furthermore, this table extends to return the total time 2254 in each Power State, along with the number of times a 2255 particular Power State was entered." 2257 INDEX { entPhysicalIndex, 2258 eoPowerStateIndex 2259 } 2260 ::= { eoPowerStateTable 1 } 2262 EoPowerStateEntry ::= SEQUENCE { 2263 eoPowerStateIndex IANAPowerStateSet, 2264 eoPowerStateMaxPower Integer32, 2265 eoPowerStatePowerUnitMultiplier UnitMultiplier, 2266 eoPowerStateTotalTime TimeTicks, 2267 eoPowerStateEnterCount Counter32 2268 } 2270 eoPowerStateIndex OBJECT-TYPE 2271 SYNTAX IANAPowerStateSet 2272 MAX-ACCESS not-accessible 2273 STATUS current 2274 DESCRIPTION 2275 " 2276 This object specifies the index of the Power State of 2277 the Energy Object within a Power State Set. The 2278 semantics of the specific Power State can be obtained 2279 from the Power State Set definition." 2280 ::= { eoPowerStateEntry 1 } 2282 eoPowerStateMaxPower OBJECT-TYPE 2283 SYNTAX Integer32 2284 UNITS "Watts" 2285 MAX-ACCESS read-only 2286 STATUS current 2287 DESCRIPTION 2288 "This object indicates the maximum power for the Energy 2289 Object at the particular Power State. This value is 2290 specified in SI units of watts with the magnitude of the 2291 units (milliwatts, kilowatts, etc.) indicated separately 2292 in eoPowerStatePowerUnitMultiplier. If the maximum power 2293 is not known for a certain Power State, then the value is 2294 encoded as 0xFFFF. 2296 For Power States not enumerated, the value of 2297 eoPowerStateMaxPower might be interpolated by using the 2298 next highest supported Power State." 2299 ::= { eoPowerStateEntry 2 } 2301 eoPowerStatePowerUnitMultiplier OBJECT-TYPE 2302 SYNTAX UnitMultiplier 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "The magnitude of watts for the usage value in 2307 eoPowerStateMaxPower." 2308 ::= { eoPowerStateEntry 3 } 2310 eoPowerStateTotalTime OBJECT-TYPE 2311 SYNTAX TimeTicks 2312 MAX-ACCESS read-only 2313 STATUS current 2314 DESCRIPTION 2315 "This object indicates the total time in hundreds 2316 of seconds that the Energy Object has been in this power 2317 state since the last reset, as specified in the 2318 sysUpTime." 2319 ::= { eoPowerStateEntry 4 } 2321 eoPowerStateEnterCount OBJECT-TYPE 2322 SYNTAX Counter32 2323 MAX-ACCESS read-only 2324 STATUS current 2325 DESCRIPTION 2326 "This object indicates how often the Energy 2327 Object has 2328 entered this power state, since the last reset of the 2329 device as specified in the sysUpTime." 2330 ::= { eoPowerStateEntry 5 } 2332 eoEnergyParametersTable OBJECT-TYPE 2333 SYNTAX SEQUENCE OF EoEnergyParametersEntry 2334 MAX-ACCESS not-accessible 2335 STATUS current 2336 DESCRIPTION 2337 "This table is used to configure the parameters for 2338 Energy measurement collection in the table 2339 eoEnergyTable. This table allows the configuration of 2340 different measurement settings on the same Energy 2341 Object." 2342 ::= { energyObjectMibObjects 3 } 2344 eoEnergyParametersEntry OBJECT-TYPE 2345 SYNTAX EoEnergyParametersEntry 2346 MAX-ACCESS not-accessible 2347 STATUS current 2348 DESCRIPTION 2349 "An entry controls an energy measurement in 2350 eoEnergyTable." 2351 INDEX { eoEnergyParametersIndex } 2352 ::= { eoEnergyParametersTable 1 } 2354 EoEnergyParametersEntry ::= SEQUENCE { 2355 eoEnergyObjectIndex PhysicalIndex, 2356 eoEnergyParametersIndex Integer32, 2357 eoEnergyParametersIntervalLength TimeInterval, 2358 eoEnergyParametersIntervalNumber Integer32, 2359 eoEnergyParametersIntervalMode Integer32, 2360 eoEnergyParametersIntervalWindow TimeInterval, 2361 eoEnergyParametersSampleRate Integer32, 2362 eoEnergyParametersStatus RowStatus 2363 } 2365 eoEnergyObjectIndex OBJECT-TYPE 2366 SYNTAX PhysicalIndex 2367 MAX-ACCESS read-create 2368 STATUS current 2369 DESCRIPTION 2370 "The unique value, to identify the specific Energy Object 2371 on which the measurement is applied, the same index used 2372 in the eoPowerTable to identify the Energy Object." 2373 ::= { eoEnergyParametersEntry 1 } 2375 eoEnergyParametersIndex OBJECT-TYPE 2376 SYNTAX Integer32 (0..2147483647) 2377 MAX-ACCESS read-create 2378 STATUS current 2379 DESCRIPTION 2380 "This object specifies the index of the Energy 2381 Parameters setting for collection of energy measurements 2382 for an Energy Object. An Energy Object can have multiple 2383 eoEnergyParametersIndex, depending on the capability of 2384 the Energy Object" 2385 ::= { eoEnergyParametersEntry 2 } 2387 eoEnergyParametersIntervalLength OBJECT-TYPE 2388 SYNTAX TimeInterval 2389 MAX-ACCESS read-create 2390 STATUS current 2391 DESCRIPTION 2392 "This object indicates the length of time in hundredth of 2393 seconds over which to compute the average 2394 eoEnergyConsumed measurement in the eoEnergyTable table. 2395 The computation is based on the Energy Object's internal 2396 sampling rate of power consumed or produced by the Energy 2397 Object. The sampling rate is the rate at which the Energy 2398 Object can read the power usage and may differ based on 2399 device capabilities. The average energy consumption is 2400 then computed over the length of the interval." 2401 DEFVAL { 90000 } 2402 ::= { eoEnergyParametersEntry 3 } 2404 eoEnergyParametersIntervalNumber OBJECT-TYPE 2405 SYNTAX Integer32 2406 MAX-ACCESS read-create 2407 STATUS current 2408 DESCRIPTION 2410 "The number of intervals maintained in the eoEnergyTable. 2411 Each interval is characterized by a specific 2412 eoEnergyCollectionStartTime, used as an index to the 2413 table eoEnergyTable. Whenever the maximum number of 2414 entries is reached, the measurement over the new interval 2415 replacesthe oldest measurement. There is one exception to 2416 this rule: when the eoEnergyMaxConsumed and/or 2417 eoEnergyMaxProduced are in (one of) the two oldest 2418 measurement(s), they are left untouched and the next 2419 oldest measurement is replaced." 2420 DEFVAL { 10 } 2421 ::= { eoEnergyParametersEntry 4 } 2423 eoEnergyParametersIntervalMode OBJECT-TYPE 2424 SYNTAX INTEGER { 2425 period(1), 2426 sliding(2), 2427 total(3) 2429 } 2430 MAX-ACCESS read-create 2431 STATUS current 2432 DESCRIPTION 2433 "A control object to define the mode of interval calculation 2434 for the computation of the average eoEnergyConsumed or 2435 eoEnergyProduced measurement in the eoEnergyTable table. 2437 A mode of period(1) specifies non-overlapping periodic 2438 measurements. 2440 A mode of sliding(2) specifies overlapping sliding windows 2441 where the interval between the start of one interval and 2442 the next is defined in eoEnergyParametersIntervalWindow. 2444 A mode of total(3) specifies non-periodic measurement. In 2445 this mode only one interval is used as this is a 2446 continuous measurement since the last reset. The value of 2447 eoEnergyParametersIntervalNumber should be (1) one and 2448 eoEnergyParametersIntervalLength is ignored. " 2449 ::= { eoEnergyParametersEntry 5 } 2451 eoEnergyParametersIntervalWindow OBJECT-TYPE 2452 SYNTAX TimeInterval 2453 MAX-ACCESS read-create 2454 STATUS current 2455 DESCRIPTION 2456 "The length of the duration window between the starting 2457 time of one sliding window and the next starting time in 2458 hundredth of seconds, in order to compute the average of 2459 eoEnergyConsumed, eoEnergyProduced measurements in the 2460 eoEnergyTable table. This is valid only when the 2461 eoEnergyParametersIntervalMode is sliding(2). The 2462 eoEnergyParametersIntervalWindow value should be a multiple 2463 of eoEnergyParametersSampleRate." 2464 ::= { eoEnergyParametersEntry 6 } 2466 eoEnergyParametersSampleRate OBJECT-TYPE 2467 SYNTAX Integer32 2468 UNITS "Milliseconds" 2469 MAX-ACCESS read-create 2470 STATUS current 2471 DESCRIPTION 2472 "The sampling rate, in milliseconds, at which the Energy 2473 Object should poll power usage in order to compute the 2474 average eoEnergyConsumed, eoEnergyProduced measurements 2475 in the table eoEnergyTable. The Energy Object should 2476 initially set this sampling rate to a reasonable value, 2477 i.e., a compromise between intervals that will provide 2478 good accuracy by not being too long, but not so short 2479 that they affect the Energy Object performance by 2480 requesting continuous polling. If the sampling rate is 2481 unknown, the value 0 is reported. The sampling rate 2482 should be selected so that 2483 eoEnergyParametersIntervalWindow is a multiple of 2484 eoEnergyParametersSampleRate." 2485 DEFVAL { 1000 } 2486 ::= { eoEnergyParametersEntry 7 } 2488 eoEnergyParametersStatus OBJECT-TYPE 2489 SYNTAX RowStatus 2490 MAX-ACCESS read-create 2491 STATUS current 2492 DESCRIPTION 2493 "The status of this row. The eoEnergyParametersStatus is 2494 used to start or stop energy usage logging. An entry 2495 status may not be active(1) unless all objects in the 2496 entry have an appropriate value. If this object is not 2497 equal to active(1), all associated usage-data logged into 2498 the eoEnergyTable will be deleted. The data can be 2499 destroyed by setting up the eoEnergyParametersStatus to 2500 destroy(2)." 2501 ::= {eoEnergyParametersEntry 8 } 2503 eoEnergyTable OBJECT-TYPE 2504 SYNTAX SEQUENCE OF EoEnergyEntry 2505 MAX-ACCESS not-accessible 2506 STATUS current 2507 DESCRIPTION 2508 "This table lists Energy Object energy measurements. 2509 Entries in this table are only created if the 2510 corresponding value of object eoPowerMeasurementCaliber 2511 is active(2), i.e., if the power is actually metered." 2512 ::= { energyObjectMibObjects 4 } 2514 eoEnergyEntry OBJECT-TYPE 2515 SYNTAX EoEnergyEntry 2516 MAX-ACCESS not-accessible 2517 STATUS current 2518 DESCRIPTION 2519 "An entry describing energy measurements." 2520 INDEX { eoEnergyParametersIndex, 2521 eoEnergyCollectionStartTime } 2522 ::= { eoEnergyTable 1 } 2524 EoEnergyEntry ::= SEQUENCE { 2525 eoEnergyCollectionStartTime TimeTicks, 2526 eoEnergyConsumed Integer32, 2527 eoEnergyProduced Integer32, 2528 eoEnergyNet Integer32, 2529 eoEnergyUnitMultiplier UnitMultiplier, 2530 eoEnergyAccuracy Integer32, 2531 eoEnergyMaxConsumed Integer32, 2532 eoEnergyMaxProduced Integer32, 2533 eoEnergyDiscontinuityTime TimeStamp 2534 } 2536 eoEnergyCollectionStartTime OBJECT-TYPE 2537 SYNTAX TimeTicks 2538 UNITS "hundredths of seconds" 2539 MAX-ACCESS not-accessible 2540 STATUS current 2541 DESCRIPTION 2542 "The time (in hundredths of a second) since the 2543 network management portion of the system was last 2544 re-initialized, as specified in the sysUpTime [RFC3418]. 2545 This object is useful for reference of interval periods 2546 for which the energy is measured." 2547 ::= { eoEnergyEntry 1 } 2549 eoEnergyConsumed OBJECT-TYPE 2550 SYNTAX Integer32 2551 UNITS "Watt-hours" 2552 MAX-ACCESS read-only 2553 STATUS current 2554 DESCRIPTION 2555 "This object indicates the energy consumed in units of watt- 2556 hours for the Energy Object over the defined interval. 2557 This value is specified in the common billing units of watt- 2558 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2559 indicated separately in eoEnergyUnitMultiplier." 2560 ::= { eoEnergyEntry 2 } 2562 eoEnergyProduced OBJECT-TYPE 2563 SYNTAX Integer32 2564 UNITS "Watt-hours" 2565 MAX-ACCESS read-only 2566 STATUS current 2567 DESCRIPTION 2568 "This object indicates the energy produced in units of watt- 2569 hours for the Energy Object over the defined interval. 2571 This value is specified in the common billing units of watt- 2572 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2573 indicated separately in eoEnergyUnitMultiplier." 2574 ::= { eoEnergyEntry 3 } 2576 eoEnergyNet OBJECT-TYPE 2577 SYNTAX Integer32 2578 UNITS "Watt-hours" 2579 MAX-ACCESS read-only 2580 STATUS current 2581 DESCRIPTION 2582 "This object indicates the resultant of the energy consumed and 2583 energy produced for an energy object in units of watt-hours for 2584 the Energy Object over the defined interval. This value is 2585 specified in the common billing units of watt-hours 2586 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2587 indicated separately in eoEnergyUnitMultiplier." 2588 ::= { eoEnergyEntry 4 } 2590 eoEnergyUnitMultiplier OBJECT-TYPE 2591 SYNTAX UnitMultiplier 2592 MAX-ACCESS read-only 2593 STATUS current 2594 DESCRIPTION 2595 "This object is the magnitude of watt-hours for the 2596 energy field in eoEnergyConsumed, eoEnergyProduced, 2597 eoEnergyNet, eoEnergyMaxConsumed, and eoEnergyMaxProduced 2598 ." 2599 ::= { eoEnergyEntry 5 } 2601 eoEnergyAccuracy OBJECT-TYPE 2602 SYNTAX Integer32 (0..10000) 2603 UNITS "hundredths of percent" 2604 MAX-ACCESS read-only 2605 STATUS current 2606 DESCRIPTION 2607 "This object indicates a percentage value, in 100ths of a 2608 percent, representing the presumed accuracy of Energy usage 2609 reporting. eoEnergyAccuracy is applicable to all Energy 2610 measurements in the eoEnergyTable. 2612 For example: 1010 means the reported usage is accurate to +/- 2613 10.1 percent. 2614 This value is zero if the accuracy is unknown." 2616 ::= { eoEnergyEntry 6 } 2618 eoEnergyMaxConsumed OBJECT-TYPE 2619 SYNTAX Integer32 2620 UNITS "Watt-hours" 2621 MAX-ACCESS read-only 2622 STATUS current 2623 DESCRIPTION 2624 "This object is the maximum energy ever observed in 2625 eoEnergyConsumed since the monitoring started. This value 2626 is specified in the common billing units of watt-hours 2627 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2628 indicated separately in eoEnergyUnitMultiplier." 2629 ::= { eoEnergyEntry 7 } 2631 eoEnergyMaxProduced OBJECT-TYPE 2632 SYNTAX Integer32 2633 UNITS "Watt-hours" 2634 MAX-ACCESS read-only 2635 STATUS current 2636 DESCRIPTION 2637 "This object is the maximum energy ever observed in 2638 eoEnergyEnergyProduced since the monitoring started. This 2639 value is specified in the units of watt-hours with the 2640 magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated 2641 separately in eoEnergyEnergyUnitMultiplier." 2642 ::= { eoEnergyEntry 8 } 2644 eoEnergyDiscontinuityTime OBJECT-TYPE 2645 SYNTAX TimeStamp 2646 MAX-ACCESS read-only 2647 STATUS current 2648 DESCRIPTION 2650 "The value of sysUpTime [RFC3418] on the most recent 2651 occasion at which any one or more of this entity's energy 2652 counters in this table suffered a discontinuity: 2653 eoEnergyConsumed, eoEnergyProduced or eoEnergyNet. If no 2654 such discontinuities have occurred since the last re- 2655 initialization of the local management subsystem, then 2656 this object contains a zero value." 2657 ::= { eoEnergyEntry 9 } 2659 -- Notifications 2661 eoPowerStateChange NOTIFICATION-TYPE 2662 OBJECTS {eoPowerAdminState, eoPowerOperState, 2663 eoPowerStateEnterReason} 2664 STATUS current 2665 DESCRIPTION 2666 "The SNMP entity generates the eoPowerStateChange when 2667 the value(s) of eoPowerAdminState or eoPowerOperState, 2668 in the context of the Power State Set, have changed for 2669 the Energy Object represented by the entPhysicalIndex." 2670 ::= { energyObjectMibNotifs 1 } 2672 -- Conformance 2674 energyObjectMibCompliances OBJECT IDENTIFIER 2675 ::= { energyObjectMib 3 } 2677 energyObjectMibGroups OBJECT IDENTIFIER 2678 ::= { energyObjectMib 4 } 2680 energyObjectMibFullCompliance MODULE-COMPLIANCE 2681 STATUS current 2682 DESCRIPTION 2683 "When this MIB is implemented with support for 2684 read-create, then such an implementation can 2685 claim full compliance. Such devices can then 2686 be both monitored and configured with this MIB. 2687 The entPhysicalIndex, entPhysicalName, and 2688 entPhysicalUris [RFC4133] MUST be implemented." 2689 MODULE -- this module 2690 MANDATORY-GROUPS { 2691 energyObjectMibTableGroup, 2692 energyObjectMibStateTableGroup, 2693 energyObjectMibNotifGroup 2694 } 2696 GROUP energyObjectMibEnergyTableGroup 2698 DESCRIPTION "A compliant implementation does not 2699 have to implement. The entPhysicalIndex, 2700 entPhysicalName, and entPhysicalUris [RFC4133] 2701 MUST be implemented." 2703 GROUP energyObjectMibEnergyParametersTableGroup 2705 DESCRIPTION "A compliant implementation does not 2706 have to implement. The entPhysicalIndex, 2707 entPhysicalName, and entPhysicalUris [RFC4133] 2708 MUST be implemented." 2710 ::= { energyObjectMibCompliances 1 } 2712 energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE 2713 STATUS current 2714 DESCRIPTION 2715 "When this MIB is implemented without support for 2716 read-create (i.e. in read-only mode), then such an 2717 implementation can claim read-only compliance. Such a 2718 device can then be monitored but cannot be 2719 configured with this MIB. The entPhysicalIndex, 2720 entPhysicalName, and entPhysicalUris from [RFC4133] 2721 MUST be implemented. " 2722 MODULE -- this module 2723 MANDATORY-GROUPS { 2724 energyObjectMibTableGroup, 2725 energyObjectMibStateTableGroup, 2726 energyObjectMibNotifGroup 2727 } 2729 OBJECT eoPowerOperState 2730 MIN-ACCESS read-only 2731 DESCRIPTION 2732 "Write access is not required." 2733 ::= { energyObjectMibCompliances 2 } 2735 -- Units of Conformance 2737 energyObjectMibTableGroup OBJECT-GROUP 2738 OBJECTS { 2739 eoPower, 2740 eoPowerNameplate, 2741 eoPowerUnitMultiplier, 2742 eoPowerAccuracy, 2743 eoPowerMeasurementCaliber, 2744 eoPowerCurrentType, 2745 eoPowerOrigin, 2746 eoPowerAdminState, 2747 eoPowerOperState, 2748 eoPowerStateEnterReason 2749 } 2750 STATUS current 2751 DESCRIPTION 2752 "This group contains the collection of all the objects 2753 related to the PowerMonitor." 2754 ::= { energyObjectMibGroups 1 } 2756 energyObjectMibStateTableGroup OBJECT-GROUP 2757 OBJECTS { 2758 eoPowerStateMaxPower, 2759 eoPowerStatePowerUnitMultiplier, 2760 eoPowerStateTotalTime, 2761 eoPowerStateEnterCount 2762 } 2763 STATUS current 2764 DESCRIPTION 2765 "This group contains the collection of all the 2766 objects related to the Power State." 2767 ::= { energyObjectMibGroups 2 } 2769 energyObjectMibEnergyParametersTableGroup OBJECT-GROUP 2770 OBJECTS { 2771 eoEnergyObjectIndex, 2772 eoEnergyParametersIndex, 2773 eoEnergyParametersIntervalLength, 2774 eoEnergyParametersIntervalNumber, 2775 eoEnergyParametersIntervalMode, 2776 eoEnergyParametersIntervalWindow, 2777 eoEnergyParametersSampleRate, 2778 eoEnergyParametersStatus 2779 } 2780 STATUS current 2781 DESCRIPTION 2782 "This group contains the collection of all the objects 2783 related to the configuration of the Energy Table." 2784 ::= { energyObjectMibGroups 3 } 2786 energyObjectMibEnergyTableGroup OBJECT-GROUP 2787 OBJECTS { 2788 -- Note that object 2789 -- eoEnergyCollectionStartTime is not 2790 -- included since it is not-accessible 2792 eoEnergyConsumed, 2793 eoEnergyProduced, 2794 eoEnergyNet, 2795 eoEnergyUnitMultiplier, 2796 eoEnergyAccuracy, 2797 eoEnergyMaxConsumed, 2798 eoEnergyMaxProduced, 2799 eoEnergyDiscontinuityTime 2800 } 2801 STATUS current 2802 DESCRIPTION 2803 "This group contains the collection of all the objects 2804 related to the Energy Table." 2805 ::= { energyObjectMibGroups 4 } 2807 energyObjectMibNotifGroup NOTIFICATION-GROUP 2808 NOTIFICATIONS { 2809 eoPowerStateChange 2810 } 2811 STATUS current 2812 DESCRIPTION 2813 "This group contains the notifications for the power and 2814 energy monitoring MIB Module." 2815 ::= { energyObjectMibGroups 5 } 2817 END 2819 -- ************************************************************ 2820 -- 2821 -- This MIB module is used to monitor power quality of networked 2822 -- devices with measurements. 2823 -- 2824 -- This MIB module is an extension of energyObjectMib module. 2825 -- 2826 -- ************************************************************* 2828 POWER-QUALITY-MIB DEFINITIONS ::= BEGIN 2830 IMPORTS 2831 MODULE-IDENTITY, 2832 OBJECT-TYPE, 2833 mib-2, 2834 Integer32 2835 FROM SNMPv2-SMI 2836 MODULE-COMPLIANCE, 2837 OBJECT-GROUP 2838 FROM SNMPv2-CONF 2839 UnitMultiplier 2840 FROM ENERGY-OBJECT-MIB 2841 OwnerString 2842 FROM RMON-MIB 2843 entPhysicalIndex 2844 FROM ENTITY-MIB; 2846 powerQualityMIB MODULE-IDENTITY 2848 LAST-UPDATED "201203010000Z" -- 1 March 2012 2850 ORGANIZATION "IETF EMAN Working Group" 2851 CONTACT-INFO 2852 "WG charter: 2853 http://datatracker.ietf.org/wg/eman/charter/ 2855 Mailing Lists: 2856 General Discussion: eman@ietf.org 2858 To Subscribe: 2859 https://www.ietf.org/mailman/listinfo/eman 2861 Archive: 2862 http://www.ietf.org/mail-archive/web/eman 2864 Editors: 2866 Mouli Chandramouli 2867 Cisco Systems, Inc. 2868 Sarjapur Outer Ring Road 2869 Bangalore, 2870 IN 2871 Phone: +91 80 4426 3947 2872 Email: moulchan@cisco.com 2874 Brad Schoening 2875 44 Rivers Edge Drive 2876 Little Silver, NJ 07739 2877 US 2878 Email: brad@bradschoening.com 2880 Juergen Quittek 2881 NEC Europe Ltd. 2883 NEC Laboratories Europe 2884 Network Research Division 2885 Kurfuersten-Anlage 36 2886 Heidelberg 69115 2887 DE 2888 Phone: +49 6221 4342-115 2889 Email: quittek@neclab.eu 2891 Thomas Dietz 2892 NEC Europe Ltd. 2893 NEC Laboratories Europe 2894 Network Research Division 2895 Kurfuersten-Anlage 36 2896 69115 Heidelberg 2897 DE 2898 Phone: +49 6221 4342-128 2899 Email: Thomas.Dietz@nw.neclab.eu 2901 Benoit Claise 2902 Cisco Systems, Inc. 2903 De Kleetlaan 6a b1 2904 Degem 1831 2905 Belgium 2906 Phone: +32 2 704 5622 2907 Email: bclaise@cisco.com" 2909 DESCRIPTION 2910 "This MIB is used to report AC power quality in 2911 devices. The table is a sparse augmentation of the 2912 eoPowerTable table from the energyObjectMib module. 2913 Both three-phase and single-phase power 2914 configurations are supported. 2916 As a requirement for this MIB module, 2917 [EMAN-AWARE-MIB] should be implemented and 2918 three MIB objects from ENTITY-MIB (entPhysicalIndex, 2919 entPhysicalName and entPhysicalUris) MUST be 2920 implemented. " 2921 REVISION 2923 "201203010000Z" -- 1 March 2012 2925 DESCRIPTION 2926 "Initial version, published as RFC YYY." 2928 ::= { mib-2 yyy } 2930 powerQualityMIBConform OBJECT IDENTIFIER 2931 ::= { powerQualityMIB 0 } 2933 powerQualityMIBObjects OBJECT IDENTIFIER 2934 ::= { powerQualityMIB 1 } 2936 -- Objects 2938 eoACPwrQualityTable OBJECT-TYPE 2939 SYNTAX SEQUENCE OF EoACPwrQualityEntry 2940 MAX-ACCESS not-accessible 2941 STATUS current 2942 DESCRIPTION 2943 "This table defines power quality measurements for 2944 supported entPhysicalIndex entities. It is a sparse 2945 extension of the eoPowerTable." 2946 ::= { powerQualityMIBObjects 1 } 2948 eoACPwrQualityEntry OBJECT-TYPE 2949 SYNTAX EoACPwrQualityEntry 2950 MAX-ACCESS not-accessible 2951 STATUS current 2952 DESCRIPTION 2953 "This is a sparse extension of the eoPowerTable with 2954 entries for power quality measurements or 2955 configuration. Each measured value corresponds to an 2956 attribute in IEC 61850-7-4 for non-phase measurements 2957 within the object MMUX." 2959 INDEX {entPhysicalIndex } 2960 ::= { eoACPwrQualityTable 1 } 2962 EoACPwrQualityEntry ::= SEQUENCE { 2963 eoACPwrQualityConfiguration INTEGER, 2964 eoACPwrQualityAvgVoltage Integer32, 2965 eoACPwrQualityAvgCurrent Integer32, 2966 eoACPwrQualityFrequency Integer32, 2967 eoACPwrQualityPowerUnitMultiplier UnitMultiplier, 2968 eoACPwrQualityPowerAccuracy Integer32, 2969 eoACPwrQualityTotalActivePower Integer32, 2970 eoACPwrQualityTotalReactivePower Integer32, 2971 eoACPwrQualityTotalApparentPower Integer32, 2972 eoACPwrQualityTotalPowerFactor Integer32, 2973 eoACPwrQualityThdAmpheres Integer32, 2974 eoACPwrQualityThdVoltage Integer32 2975 } 2977 eoACPwrQualityConfiguration OBJECT-TYPE 2978 SYNTAX INTEGER { 2979 sngl(1), 2980 del(2), 2981 wye(3) 2982 } 2983 MAX-ACCESS read-only 2984 STATUS current 2985 DESCRIPTION 2986 "Configuration describes the physical configurations 2987 of the power supply lines: 2989 * alternating current, single phase (SNGL) 2990 * alternating current, three phase delta (DEL) 2991 * alternating current, three phase Y (WYE) 2993 Three-phase configurations can be either connected in 2994 a triangular delta (DEL) or star Y (WYE) system. WYE 2995 systems have a shared neutral voltage, while DEL 2996 systems do not. Each phase is offset 120 degrees to 2997 each other." 2998 ::= { eoACPwrQualityEntry 1 } 3000 eoACPwrQualityAvgVoltage OBJECT-TYPE 3001 SYNTAX Integer32 3002 UNITS "0.1 Volt AC" 3003 MAX-ACCESS read-only 3004 STATUS current 3005 DESCRIPTION 3006 "A measured value for average of the voltage measured 3007 over an integral number of AC cycles For a 3-phase 3008 system, this is the average voltage (V1+V2+V3)/3. IEC 3009 61850-7-4 measured value attribute 'Vol'" 3010 ::= { eoACPwrQualityEntry 2 } 3012 eoACPwrQualityAvgCurrent OBJECT-TYPE 3013 SYNTAX Integer32 3014 UNITS "Ampheres" 3015 MAX-ACCESS read-only 3016 STATUS current 3017 DESCRIPTION 3018 "A measured value of the current per phase. IEC 61850- 3019 7-4 attribute 'Amp'" 3020 ::= { eoACPwrQualityEntry 3 } 3022 eoACPwrQualityFrequency OBJECT-TYPE 3023 SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz 3024 UNITS "hertz" 3025 MAX-ACCESS read-only 3026 STATUS current 3027 DESCRIPTION 3028 "A measured value for the basic frequency of the AC 3029 circuit. IEC 61850-7-4 attribute 'Hz'." 3030 ::= { eoACPwrQualityEntry 4 } 3032 eoACPwrQualityPowerUnitMultiplier OBJECT-TYPE 3033 SYNTAX UnitMultiplier 3034 MAX-ACCESS read-only 3035 STATUS current 3036 DESCRIPTION 3037 "The magnitude of watts for the usage value in 3038 eoACPwrQualityTotalActivePower, 3039 eoACPwrQualityTotalReactivePower 3040 and eoACPwrQualityTotalApparentPower measurements. For 3041 3-phase power systems, this will also include 3042 eoACPwrQualityPhaseActivePower, 3043 eoACPwrQualityPhaseReactivePower and 3044 eoACPwrQualityPhaseApparentPower" 3045 ::= { eoACPwrQualityEntry 5 } 3047 eoACPwrQualityPowerAccuracy OBJECT-TYPE 3048 SYNTAX Integer32 (0..10000) 3049 UNITS "hundredths of percent" 3050 MAX-ACCESS read-only 3051 STATUS current 3052 DESCRIPTION 3053 "This object indicates a percentage value, in 100ths of 3054 a percent, representing the presumed accuracy of 3055 active, reactive, and apparent power usage reporting. 3056 For example: 1010 means the reported usage is accurate 3057 to +/- 10.1 percent. This value is zero if the 3058 accuracy is unknown. 3060 ANSI and IEC define the following accuracy classes for 3061 power measurement: IEC 62053-22 & 60044-1 class 0.1, 3062 0.2, 0.5, 1 & 3. 3063 ANSI C12.20 class 0.2 & 0.5" 3064 ::= { eoACPwrQualityEntry 6 } 3066 eoACPwrQualityTotalActivePower OBJECT-TYPE 3067 SYNTAX Integer32 3068 UNITS " watts" 3069 MAX-ACCESS read-only 3070 STATUS current 3071 DESCRIPTION 3072 "A measured value of the actual power delivered to or 3073 consumed by the load. IEC 61850-7-4 attribute 'TotW'." 3074 ::= { eoACPwrQualityEntry 7 } 3076 eoACPwrQualityTotalReactivePower OBJECT-TYPE 3077 SYNTAX Integer32 3078 UNITS "volt-amperes reactive" 3079 MAX-ACCESS read-only 3080 STATUS current 3081 DESCRIPTION 3082 "A mesured value of the reactive portion of the 3083 apparent power. IEC 61850-7-4 attribute 'TotVAr'." 3084 ::= { eoACPwrQualityEntry 8 } 3086 eoACPwrQualityTotalApparentPower OBJECT-TYPE 3087 SYNTAX Integer32 3088 UNITS "volt-amperes" 3089 MAX-ACCESS read-only 3090 STATUS current 3091 DESCRIPTION 3092 "A measured value of the voltage and current which 3093 determines the apparent power. The apparent power is 3094 the vector sum of real and reactive power. 3096 Note: watts and volt-ampheres are equivalent units and 3097 may be combined. IEC 61850-7-4 attribute 'TotVA'." 3098 ::= { eoACPwrQualityEntry 9 } 3100 eoACPwrQualityTotalPowerFactor OBJECT-TYPE 3101 SYNTAX Integer32 (-10000..10000) 3102 UNITS "hundredths of percent" 3103 MAX-ACCESS read-only 3104 STATUS current 3105 DESCRIPTION 3106 "A measured value ratio of the real power flowing to 3107 the load versus the apparent power. It is dimensionless 3108 and expressed here as a percentage value in 100ths of a 3109 percent. A power factor of 100% indicates there is no 3110 inductance load and thus no reactive power. Power 3111 Factor can be positive or negative, where the sign 3112 should be in lead/lag (IEEE) form. IEC 61850-7-4 3113 attribute 'TotPF'." 3114 ::= { eoACPwrQualityEntry 10 } 3116 eoACPwrQualityThdAmpheres OBJECT-TYPE 3117 SYNTAX Integer32 (0..10000) 3118 UNITS "hundredths of percent" 3119 MAX-ACCESS read-only 3120 STATUS current 3121 DESCRIPTION 3122 "A calculated value for the current total harmonic 3123 distortion (THD). Method of calculation is not 3124 specified. IEC 61850-7-4 attribute 'ThdAmp'." 3125 ::= { eoACPwrQualityEntry 11 } 3127 eoACPwrQualityThdVoltage OBJECT-TYPE 3128 SYNTAX Integer32 (0..10000) 3129 UNITS "hundredths of percent" 3130 MAX-ACCESS read-only 3131 STATUS current 3132 DESCRIPTION 3133 "A calculated value for the voltage total harmonic 3134 distortion (THD). Method of calculation is not 3135 specified. IEC 61850-7-4 attribute 'ThdVol'." 3136 ::= { eoACPwrQualityEntry 12 } 3138 eoACPwrQualityPhaseTable OBJECT-TYPE 3139 SYNTAX SEQUENCE OF EoACPwrQualityPhaseEntry 3140 MAX-ACCESS not-accessible 3141 STATUS current 3142 DESCRIPTION 3143 "This table describes 3-phase power quality 3144 measurements. It is a sparse extension of the 3145 eoACPwrQualityTable." 3146 ::= { powerQualityMIBObjects 2 } 3148 eoACPwrQualityPhaseEntry OBJECT-TYPE 3149 SYNTAX EoACPwrQualityPhaseEntry 3150 MAX-ACCESS not-accessible 3151 STATUS current 3152 DESCRIPTION 3153 "An entry describes common 3-phase power quality 3154 measurements. 3156 This optional table describes 3-phase power quality 3157 measurements, with three entries for each supported 3158 entPhysicalIndex entity. Entities having single phase 3159 power shall not have any entities. 3161 This table describes attributes common to both WYE and 3162 DEL. Entities having single phase power shall not have 3163 any entries here. It is a sparse extension of the 3164 eoACPwrQualityTable. 3166 These attributes correspond to IEC 61850-7.4 MMXU phase 3167 measurements." 3168 INDEX { entPhysicalIndex, eoPhaseIndex } 3169 ::= { eoACPwrQualityPhaseTable 1 } 3171 EoACPwrQualityPhaseEntry ::= SEQUENCE { 3172 eoPhaseIndex Integer32, 3173 eoACPwrQualityPhaseAvgCurrent Integer32, 3174 eoACPwrQualityPhaseActivePower Integer32, 3175 eoACPwrQualityPhaseReactivePower Integer32, 3176 eoACPwrQualityPhaseApparentPower Integer32, 3177 eoACPwrQualityPhasePowerFactor Integer32, 3178 eoACPwrQualityPhaseImpedance Integer32 3179 } 3181 eoPhaseIndex OBJECT-TYPE 3182 SYNTAX Integer32 (0..359) 3183 MAX-ACCESS not-accessible 3184 STATUS current 3185 DESCRIPTION 3186 "A phase angle typically corresponding to 0, 120, 240." 3187 ::= { eoACPwrQualityPhaseEntry 1 } 3189 eoACPwrQualityPhaseAvgCurrent OBJECT-TYPE 3190 SYNTAX Integer32 3191 UNITS "Ampheres" 3192 MAX-ACCESS read-only 3193 STATUS current 3194 DESCRIPTION 3195 "A measured value of the current per phase. IEC 61850- 3196 7-4 attribute 'A'" 3197 ::= { eoACPwrQualityPhaseEntry 2 } 3199 eoACPwrQualityPhaseActivePower OBJECT-TYPE 3200 SYNTAX Integer32 3201 UNITS " watts" 3202 MAX-ACCESS read-only 3203 STATUS current 3204 DESCRIPTION 3205 "A measured value of the actual power delivered to or 3206 consumed by the load. IEC 61850-7-4 attribute 'W'" 3207 ::= { eoACPwrQualityPhaseEntry 3 } 3209 eoACPwrQualityPhaseReactivePower OBJECT-TYPE 3210 SYNTAX Integer32 3211 UNITS "volt-amperes reactive" 3212 MAX-ACCESS read-only 3213 STATUS current 3214 DESCRIPTION 3215 "A measured value of the reactive portion of the 3216 apparent power. IEC 61850-7-4 attribute 'VAr'" 3217 ::= { eoACPwrQualityPhaseEntry 4 } 3219 eoACPwrQualityPhaseApparentPower OBJECT-TYPE 3220 SYNTAX Integer32 3221 UNITS "volt-amperes" 3222 MAX-ACCESS read-only 3223 STATUS current 3224 DESCRIPTION 3225 "A measured value of the voltage and current determines 3226 the apparent power. Active plus reactive power equals 3227 the total apparent powwer. 3229 Note: Watts and volt-ampheres are equivalent units and 3230 may be combined. IEC 61850-7-4 attribute 'VA'." 3231 ::= { eoACPwrQualityPhaseEntry 5 } 3233 eoACPwrQualityPhasePowerFactor OBJECT-TYPE 3234 SYNTAX Integer32 (-10000..10000) 3235 UNITS "hundredths of percent" 3236 MAX-ACCESS read-only 3237 STATUS current 3238 DESCRIPTION 3239 "A measured value ratio of the real power flowing to 3240 the load versus the apparent power for this phase. IEC 3241 61850-7-4 attribute 'PF'. Power Factor can be positive 3242 or negative where the sign should be in lead/lag (IEEE) 3243 form." 3244 ::= { eoACPwrQualityPhaseEntry 6 } 3246 eoACPwrQualityPhaseImpedance OBJECT-TYPE 3247 SYNTAX Integer32 3248 UNITS "volt-amperes" 3249 MAX-ACCESS read-only 3250 STATUS current 3251 DESCRIPTION 3252 "A measured value of the impedance. IEC 61850-7-4 attribute 3253 'Z'." 3254 ::= { eoACPwrQualityPhaseEntry 7 } 3256 eoACPwrQualityDelPhaseTable OBJECT-TYPE 3257 SYNTAX SEQUENCE OF EoACPwrQualityDelPhaseEntry 3258 MAX-ACCESS not-accessible 3259 STATUS current 3260 DESCRIPTION 3261 "This table describes DEL configuration phase-to-phase 3262 power quality measurements. This is a sparse extension 3263 of the eoACPwrQualityPhaseTable." 3264 ::= { powerQualityMIBObjects 3 } 3266 eoACPwrQualityDelPhaseEntry OBJECT-TYPE 3267 SYNTAX EoACPwrQualityDelPhaseEntry 3268 MAX-ACCESS not-accessible 3269 STATUS current 3270 DESCRIPTION 3271 "An entry describes quality attributes of a phase in a 3272 DEL 3-phase power system. Voltage measurements are 3273 provided both relative to each other and zero. 3275 Measured values are from IEC 61850-7-2 MMUX and THD from 3276 MHAI objects. 3278 For phase-to-phase measurements, the eoPhaseIndex is 3279 compared against the following phase at +120 degrees. 3280 Thus, the possible values are: 3282 eoPhaseIndex Next Phase Angle 3283 0 120 3284 120 240 3285 240 0 3286 " 3287 INDEX { entPhysicalIndex, eoPhaseIndex} 3288 ::= { eoACPwrQualityDelPhaseTable 1} 3290 EoACPwrQualityDelPhaseEntry ::= SEQUENCE { 3291 eoACPwrQualityDelPhaseToNextPhaseVoltage Integer32, 3292 eoACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, 3293 eoACPwrQualityDelThdCurrent Integer32 3294 } 3296 eoACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE 3297 SYNTAX Integer32 3298 UNITS "0.1 Volt AC" 3299 MAX-ACCESS read-only 3300 STATUS current 3301 DESCRIPTION 3302 "A measured value of phase to next phase voltages, where 3303 the next phase is IEC 61850-7-4 attribute 'PPV'." 3304 ::= { eoACPwrQualityDelPhaseEntry 2 } 3306 eoACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE 3307 SYNTAX Integer32 (0..10000) 3308 UNITS "hundredths of percent" 3309 MAX-ACCESS read-only 3310 STATUS current 3311 DESCRIPTION 3312 "A calculated value for the voltage total harmonic 3313 disortion for phase to next phase. Method of calculation 3314 is not specified. IEC 61850-7-4 attribute 'ThdPPV'." 3315 ::= { eoACPwrQualityDelPhaseEntry 3 } 3317 eoACPwrQualityDelThdCurrent OBJECT-TYPE 3318 SYNTAX Integer32 (0..10000) 3319 UNITS "hundredths of percent" 3320 MAX-ACCESS read-only 3321 STATUS current 3322 DESCRIPTION 3323 "A calculated value for the voltage total harmonic 3324 disortion (THD) for phase to phase. Method of 3325 calculation is not specified. 3326 IEC 61850-7-4 attribute 'ThdPPV'." 3327 ::= { eoACPwrQualityDelPhaseEntry 4 } 3329 eoACPwrQualityWyePhaseTable OBJECT-TYPE 3330 SYNTAX SEQUENCE OF EoACPwrQualityWyePhaseEntry 3331 MAX-ACCESS not-accessible 3332 STATUS current 3333 DESCRIPTION 3334 "This table describes WYE configuration phase-to-neutral 3335 power quality measurements. This is a sparse extension 3336 of the eoACPwrQualityPhaseTable." 3337 ::= { powerQualityMIBObjects 4 } 3339 eoACPwrQualityWyePhaseEntry OBJECT-TYPE 3340 SYNTAX EoACPwrQualityWyePhaseEntry 3341 MAX-ACCESS not-accessible 3342 STATUS current 3343 DESCRIPTION 3344 "This table describes measurements of WYE configuration 3345 with phase to neutral power quality attributes. Three 3346 entries are required for each supported entPhysicalIndex 3347 entry. Voltage measurements are relative to neutral. 3349 This is a sparse extension of the 3350 eoACPwrQualityPhaseTable. 3352 Each entry describes quality attributes of one phase of 3353 a WYE 3-phase power system. 3355 Measured values are from IEC 61850-7-2 MMUX and THD from 3356 MHAI objects." 3358 INDEX { entPhysicalIndex, eoPhaseIndex } 3359 ::= { eoACPwrQualityWyePhaseTable 1} 3361 EoACPwrQualityWyePhaseEntry ::= SEQUENCE { 3362 eoACPwrQualityWyePhaseToNeutralVoltage Integer32, 3363 eoACPwrQualityWyePhaseCurrent Integer32, 3364 eoACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 3365 } 3367 eoACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE 3368 SYNTAX Integer32 3369 UNITS "0.1 Volt AC" 3370 MAX-ACCESS read-only 3371 STATUS current 3372 DESCRIPTION 3373 "A measured value of phase to neutral voltage. IEC 3374 61850-7-4 attribute 'PhV'." 3375 ::= { eoACPwrQualityWyePhaseEntry 1 } 3377 eoACPwrQualityWyePhaseCurrent OBJECT-TYPE 3378 SYNTAX Integer32 3379 UNITS "0.1 ampheres AC" 3380 MAX-ACCESS read-only 3381 STATUS current 3382 DESCRIPTION 3383 "A measured value of phase currents. IEC 61850-7-4 3384 attribute 'A'." 3385 ::= { eoACPwrQualityWyePhaseEntry 2 } 3387 eoACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE 3388 SYNTAX Integer32 (0..10000) 3389 UNITS "hundredths of percent" 3390 MAX-ACCESS read-only 3391 STATUS current 3392 DESCRIPTION 3393 "A calculated value of the voltage total harmonic 3394 distortion (THD) for phase to neutral. IEC 61850-7-4 3395 attribute 'ThdPhV'." 3396 ::= { eoACPwrQualityWyePhaseEntry 3 } 3398 -- Conformance 3400 powerQualityMIBCompliances OBJECT IDENTIFIER 3401 ::= { powerQualityMIB 2 } 3403 powerQualityMIBGroups OBJECT IDENTIFIER 3404 ::= { powerQualityMIB 3 } 3406 powerQualityMIBFullCompliance MODULE-COMPLIANCE 3407 STATUS current 3408 DESCRIPTION 3409 "When this MIB is implemented with support for read-create, then 3410 such an implementation can claim full compliance. Such devices 3411 can then be both monitored and configured with this MIB. The 3412 entPhysicalIndex, entPhysicalName, and entPhysicalUris [RFC4133] 3413 MUST be implemented." 3414 MODULE -- this module 3415 MANDATORY-GROUPS { 3416 powerACPwrQualityMIBTableGroup 3417 } 3419 GROUP powerACPwrQualityOptionalMIBTableGroup 3420 DESCRIPTION 3421 "A compliant implementation does not have 3422 to implement." 3424 GROUP powerACPwrQualityPhaseMIBTableGroup 3425 DESCRIPTION 3426 "A compliant implementation does not have to 3427 implement." 3429 GROUP powerACPwrQualityDelPhaseMIBTableGroup 3430 DESCRIPTION 3431 "A compliant implementation does not have to 3432 implement." 3434 GROUP powerACPwrQualityWyePhaseMIBTableGroup 3435 DESCRIPTION 3436 "A compliant implementation does not have to 3437 implement." 3439 ::= { powerQualityMIBCompliances 1 } 3441 -- Units of Conformance 3443 powerACPwrQualityMIBTableGroup OBJECT-GROUP 3444 OBJECTS { 3445 -- Note that object entPhysicalIndex is 3446 NOT 3447 -- included since it is not-accessible 3449 eoACPwrQualityAvgVoltage, 3450 eoACPwrQualityAvgCurrent, 3451 eoACPwrQualityFrequency, 3452 eoACPwrQualityPowerUnitMultiplier, 3453 eoACPwrQualityPowerAccuracy, 3454 eoACPwrQualityTotalActivePower, 3455 eoACPwrQualityTotalReactivePower, 3456 eoACPwrQualityTotalApparentPower, 3457 eoACPwrQualityTotalPowerFactor 3458 } STATUS 3459 current 3460 DESCRIPTION 3461 "This group contains the collection of all the power 3462 quality objects related to the Energy Object." 3463 ::= { powerQualityMIBGroups 1 } 3465 powerACPwrQualityOptionalMIBTableGroup OBJECT-GROUP 3466 OBJECTS { 3467 eoACPwrQualityConfiguration, 3468 eoACPwrQualityThdAmpheres, 3469 eoACPwrQualityThdVoltage 3470 } STATUS current 3471 DESCRIPTION 3472 "This group contains the collection of all the power 3473 quality objects related to the Energy Object." 3474 ::= { powerQualityMIBGroups 2 } 3476 powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP 3477 OBJECTS { 3478 -- Note that object entPhysicalIndex is 3479 NOT 3480 -- included since it is not-accessible 3481 eoACPwrQualityPhaseAvgCurrent, 3482 eoACPwrQualityPhaseActivePower, 3483 eoACPwrQualityPhaseReactivePower, 3484 eoACPwrQualityPhaseApparentPower, 3485 eoACPwrQualityPhasePowerFactor, 3486 eoACPwrQualityPhaseImpedance 3487 } 3488 STATUS current 3489 DESCRIPTION 3490 "This group contains the collection of all 3-phase power 3491 quality objects related to the Power State." 3492 ::= { powerQualityMIBGroups 3 } 3494 powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP 3495 OBJECTS { 3496 -- Note that object entPhysicalIndex and 3497 -- eoPhaseIndex are NOT included 3498 -- since they are not-accessible 3499 eoACPwrQualityDelPhaseToNextPhaseVoltage , 3500 eoACPwrQualityDelThdPhaseToNextPhaseVoltage, 3501 eoACPwrQualityDelThdCurrent 3502 } 3503 STATUS current 3504 DESCRIPTION 3505 "This group contains the collection of all quality 3506 attributes of a phase in a DEL 3-phase power system." 3507 ::= { powerQualityMIBGroups 4 } 3509 powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP 3510 OBJECTS { 3511 -- Note that object entPhysicalIndex and 3512 -- eoPhaseIndex are NOT included 3513 -- since they are not-accessible 3514 eoACPwrQualityWyePhaseToNeutralVoltage, 3515 eoACPwrQualityWyePhaseCurrent, 3516 eoACPwrQualityWyeThdPhaseToNeutralVoltage 3517 } 3518 STATUS current 3519 DESCRIPTION 3520 "This group contains the collection of all WYE 3521 configuration phase-to-neutral power quality 3522 measurements." 3523 ::= { powerQualityMIBGroups 5 } 3525 END 3527 11. Security Considerations 3529 Some of the readable objects in these MIB modules (i.e., objects 3530 with a MAX-ACCESS other than not-accessible) may be considered 3531 sensitive or vulnerable in some network environments. It is 3532 thus important to control even GET and/or NOTIFY access to these 3533 objects and possibly to even encrypt the values of these objects 3534 when sending them over the network via SNMP. 3536 There are a number of management objects defined in these MIB 3537 modules with a MAX-ACCESS clause of read-write and/or read- 3538 create. Such objects MAY be considered sensitive or vulnerable 3539 in some network environments. The support for SET operations in 3540 a non-secure environment without proper protection can have a 3541 negative effect on network operations. The following are the 3542 tables and objects and their sensitivity/vulnerability: 3544 - Unauthorized changes to the eoPowerOperState (via 3545 theeoPowerAdminState ) MAY disrupt the power settings of the 3546 differentEnergy Objects, and therefore the state of 3547 functionality of the respective Energy Objects. 3548 - Unauthorized changes to the eoEnergyParametersTable MAY 3549 disrupt energy measurement in the eoEnergyTable table. 3551 SNMP versions prior to SNMPv3 did not include adequate security. 3552 Even if the network itself is secure (for example, by using 3553 IPsec), there is still no secure control over who on the secure 3554 network is allowed to access and GET/SET 3555 (read/change/create/delete) the objects in these MIB modules. 3557 It is RECOMMENDED that implementers consider the security 3558 features as provided by the SNMPv3 framework (see [RFC3410], 3559 section 8), including full support for the SNMPv3 cryptographic 3560 mechanisms (for authentication and privacy). 3562 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3563 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3564 enable cryptographic security. It is then a customer/operator 3565 responsibility to ensure that the SNMP entity giving access to 3566 an instance of these MIB modules is properly configured to give 3567 access to the objects only to those principals (users) that have 3568 legitimate rights to GET or SET (change/create/delete) them. 3570 12. IANA Considerations 3572 12.1. IANA Considerations for the MIB Modules 3574 The MIB modules in this document uses the following IANA- 3575 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers 3576 registry: 3578 Descriptor OBJECT IDENTIFIER value 3579 ---------- ----------------------- 3580 energyObjectMib { mib-2 xxx } 3581 powerQualityMIB { mib-2 yyy } 3583 Additions to the MIB modules are subject to Expert Review 3584 [RFC5226], i.e., review by one of a group of experts designated 3585 by an IETF Area Director. The group of experts MUST check the 3586 requested MIB objects for completeness and accuracy of the 3587 description. Requests for MIB objects that duplicate the 3588 functionality of existing objects SHOULD be declined. The 3589 smallest available OIDs SHOULD be assigned to the new MIB 3590 objects. The specification of new MIB objects SHOULD follow the 3591 structure specified in Section 10. and MUST be published using 3592 a well-established and persistent publication medium. 3594 12.2. IANA Registration of new Power State Set 3596 This document specifies an initial set of Power State Sets. The 3597 list of these Power State Sets with their numeric identifiers is 3598 given in Section 5.2.1. IANA maintains a Textual Convention 3599 IANAPowerStateSet with the initial set of Power State Sets and 3600 the Power States within those Power State Sets. The current 3601 version of Textual convention can be accessed 3602 http://www.iana.org/assignments/IANAPowerStateSet 3604 New Assignments to Power State Sets shall be administered by 3605 IANA and the guidelines and procedures are listed in this 3606 Section. 3608 New assignments for Power State Set will be administered by IANA 3609 through Expert Review [RFC5226], i.e., review by one of a group 3610 of experts designated by an IETF Area Director. The group of 3611 experts MUST check the requested state for completeness and 3612 accuracy of the description. A pure vendor specific 3613 implementation of Power State Set shall not be adopted; since it 3614 would lead to proliferation of Power State Sets. 3616 12.2.1. IANA Registration of the IEEE1621 Power State Set 3618 This document specifies a set of values for the IEEE1621 Power 3619 State Set [IEEE1621]. The list of these values with their 3620 identifiers is given in Section 5.2.1. The Internet Assigned 3621 Numbers Authority (IANA) created a new registry for IEEE1621 3622 Power State Set identifiers and filled it with the initial 3623 listin the Textual Convention IANAPowerStateSet.. 3625 New assignments (or potentially deprecation) for IEEE1621 Power 3626 State Set will be administered by IANA through Expert Review 3627 [RFC5226], i.e., review by one of a group of experts designated 3628 by an IETF Area Director. The group of experts MUST check the 3629 requested state for completeness and accuracy of the 3630 description. 3632 12.2.2. IANA Registration of the DMTF Power State Set 3634 This document specifies a set of values for the DMTF Power State 3635 Set. The list of these values with their identifiers is given 3636 in Section 5.2.1. The Internet Assigned Numbers Authority 3637 (IANA) has created a new registry for DMTF Power State Set 3638 identifiers and filled it with the initial list in the Textual 3639 Convention IANAPowerStateSet. 3640 New assignments (or potentially deprecation) for DMTF Power 3641 State Set will be administered by IANA through Expert Review 3642 [RFC5226], i.e., review by one of a group of experts designated 3643 by an IETF Area Director. The group of experts MUST check the 3644 conformance with the DMTF standard [DMTF], on the top of 3645 checking for completeness and accuracy of the description. 3647 12.2.3. IANA Registration of the EMAN Power State Set 3649 This document specifies a set of values for the EMAN Power State 3650 Set. The list of these values with their identifiers is given 3651 in Section 5.2.1. The Internet Assigned Numbers Authority 3652 (IANA) has created a new registry for EMAN Power State Set 3653 identifiers and filled it with the initial list in the Textual 3654 Convention IANAPowerStateSet. 3655 New assignments (or potentially deprecation) for EMAN Power 3656 State Set will be administered by IANA through Expert Review 3657 [RFC5226], i.e., review by one of a group of experts designated 3658 by an IETF Area Director. The group of experts MUST check the 3659 requested state for completeness and accuracy of the 3660 description. 3662 12.3. Updating the Registration of Existing Power State Sets 3664 IANA maintains a Textual Convention IANAPowerStateSet with the 3665 initial set of Power State Sets and the Power States within 3666 those Power State Sets. The current version of Textual 3667 convention can be accessed 3668 http://www.iana.org/assignments/IANAPowerStateSet 3670 With the evolution of standards, over time, it may be important 3671 to deprecate of some of the existing the Power State Sets or 3672 some of the states within a Power State Set. 3674 The registrant shall publish an Internet-draft or an individual 3675 submission with the clear specification on deprecation of Power 3676 State Sets or Power States registered with IANA. The 3677 deprecation shall be administered by IANA through Expert Review 3679 [RFC5226], i.e., review by one of a group of experts designated 3680 by an IETF Area Director. The process should also allow for a 3681 mechanism for cases where others have significant objections to 3682 claims on deprecation of a registration. In cases, where the 3683 registrant cannot be reached, IESG can designate an Expert to 3684 modify the IANA registry for the deprecation. 3686 12. Contributors 3688 This document results from the merger of two initial proposals. 3689 The following persons made significant contributions either in 3690 one of the initial proposals or in this document. 3692 John Parello 3694 Rolf Winter 3696 Dominique Dudkowski 3698 13. Acknowledgment 3700 The authors would like to thank Shamita Pisal for her prototype 3701 of this MIB module, and her valuable feedback. The authors 3702 would like to Michael Brown for improving the text dramatically. 3704 We would like to thank Juergen Schoenwalder for proposing the 3705 design of the Textual Convention for IANAPowerStateSet and Ira 3706 McDonald for his feedback. Thanks for the many comments on the 3707 design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. 3709 14. Open Issues 3711 OPEN ISSUE 1 Double-check all the IEC references in the draft. 3713 IEC 61850-7-4 has been widely referenced in many EMAN drafts. 3714 The other IEC references suggested in the email list are 3715 IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is 3716 important to resolve the correct IEC references soon. 3718 OPEN ISSUE 2 Light weight identification of a device 3720 "The identity provisioning method that has been chosen can be 3721 retrieved by reading the value of powerStateEnergyConsumerOid. 3723 In case of identities provided by the ENERGY-AWARE-MIB module, 3724 this OID points to an exising instance of eoPowerIndex, in 3725 case of the ENTITY-MIB, the object points to a valid instance 3726 of entPhysicalIndex, and in a similar way, it points to a 3727 value of another MIB module if this is used for identifying 3728 entities. If no other MIB module has been chosen for providing 3729 entity identities, then the value of 3730 powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero). 3732 OPEN ISSUE 3 Demand computation method 3734 "Energy not obtained by periodically polling a power 3735 measurement with a eoEnergyParametersSampleRate ; Energy (E) 3736 is measured to the product's certified IEC 62053-21 accuracy 3737 class" 3739 Need to verify with IEC62053-21. 3741 OPEN ISSUE 4 Consideration of IEEE-ISTO PWG in the IANA list of 3742 Power State Set ? Printer Power series could be added once the 3743 IANA procedure is in place. 3745 OPEN ISSUE 5 check if all the requirements from [EMAN-REQ] are 3746 covered. 3748 OPEN ISSUE 6 IANA Registered Power State Sets deferred to [EMAN- 3749 FRAMEWORK] 3751 OPEN ISSUE 7 Device capabilities discovery in terms of Power 3752 Quality measurements another MIB object 3754 OPEN ISSUE 8 Directional Metering of Energy not in requirements 3756 Open Issue 9 How to monitor remote objects, for which there is 3757 no entPhysicalIndex: with a proxyTable or indexed by the UUID?" 3759 15. References 3761 15.2. Normative References 3763 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 3764 Requirement Levels, BCP 14, RFC 2119, March 1997. 3766 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3767 Schoenwaelder, Ed., "Structure of Management 3768 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3769 1999. 3771 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3772 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3773 STD 58, RFC 2579, April 1999. 3775 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3776 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3777 April 1999. 3779 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 3780 RFC3621, December 2003. 3782 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3783 3)", RFC 4133, August 2005. 3785 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 3786 Base extension module for TIA-TR41.4 media endpoint 3787 discovery information", July 2005. 3789 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 3790 energy-aware-mib-04 ", work in progress, February 2012. 3792 15.3. Informative References 3794 [RFC1628] S. Bradner, "UPS Management Information Base", RFC 3795 1628, May 1994 3797 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3798 "Introduction and Applicability Statements for Internet 3799 Standard Management Framework ", RFC 3410, December 3800 2002. 3802 [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. 3803 Waldbusser, "Management Information Base (MIB) for the 3804 Simple Network Management Protocol (SNMP)", RFC3418, 3805 December 2002. 3807 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity 3808 Sensor Management Information Base", RFC 3433, December 3809 2002. 3811 [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 3812 4268,November 2005. 3814 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 3815 "Guidelines for Writing an IANA Considerations Section 3816 in RFCs ", BCP 26, RFC 5226, May 2008. 3818 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 3819 M. Chandramouli, " Requirements for Energy Managemen", 3820 draft-ietf-eman-requirements-05, November 2011. 3822 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. 3823 Quittek, "Energy Management Framework", draft-ietf- 3824 eman-framework-03, October 2011. 3826 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 3827 Quittek, J. and B. Claise "Energy and Power Monitoring 3828 MIB ", draft-eman-ietf-energy-monitoring-mib-01, 3829 October 2011. 3831 [EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy 3832 Management (EMAN) Applicability Statement", draft- 3833 ietf-eman-applicability-statement-00, December 2011. 3835 [EMAN-TERMINOLOGY] J. Parello, "Energy Management Terminology", 3836 draft-parello-eman-definitions-04, work in progress, 3837 December 2011. 3839 [ACPI] "Advanced Configuration and Power Interface 3840 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 3841 0b.pdf 3843 [DMTF] "Power State Management Profile DMTF DSP1027 Version 3844 2.0" December 2009 3845 http://www.dmtf.org/sites/default/files/standards/docum 3846 ents/DSP1027_2.0.0.pdf 3848 [IEEE1621] "Standard for User Interface Elements in Power 3849 Control of Electronic Devices Employed in 3850 Office/Consumer Environments", IEEE 1621, December 3851 2004. 3853 [IEC.61850-7-4] International Electrotechnical Commission, 3854 "Communication networks and systems for power utility 3855 automation Part 7-4: Basic communication structure 3856 Compatible logical node classes and data object 3857 classes", 2010. 3859 [IEC.62053-21] International Electrotechnical Commission, 3860 "Electricity metering equipment (a.c.) Particular 3861 requirements Part 22: Static meters for active energy 3862 (classes 1 and 2)", 2003. 3864 [IEC.62053-22]International Electrotechnical Commission, 3865 "Electricity metering equipment (a.c.) Particular 3866 requirements Part 22: Static meters for active energy 3867 (classes 0,2 S and 0,5 S)", 2003. 3869 Authors' Addresses 3871 Mouli Chandramouli 3872 Cisco Systems, Inc. 3873 Sarjapur Outer Ring Road 3874 Bangalore, 3875 IN 3877 Phone: +91 80 4426 3947 3878 Email: moulchan@cisco.com 3880 Brad Schoening 3881 44 Rivers Edge Drive 3882 Little Silver, NJ 07739 3883 US 3884 Email: brad@bradschoening.com 3886 Juergen Quittek 3887 NEC Europe Ltd. 3888 NEC Laboratories Europe 3889 Network Research Division 3890 Kurfuersten-Anlage 36 3891 Heidelberg 69115 3892 DE 3893 Phone: +49 6221 4342-115 3894 Email: quittek@neclab.eu 3896 Thomas Dietz 3897 NEC Europe Ltd. 3898 NEC Laboratories Europe 3899 Network Research Division 3900 Kurfuersten-Anlage 36 3901 Heidelberg 69115 3902 DE 3904 Phone: +49 6221 4342-128 3905 Email: Thomas.Dietz@neclab.eu 3907 Benoit Claise 3908 Cisco Systems, Inc. 3909 De Kleetlaan 6a b1 3910 Diegem 1813 3911 BE 3913 Phone: +32 2 704 5622 3914 Email: bclaise@cisco.com