idnits 2.17.1 draft-ietf-eman-energy-monitoring-mib-00.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 232 has weird spacing: '...tateSet pmPow...' == Line 235 has weird spacing: '...tiplier pmP...' == Line 271 has weird spacing: '...wStatus pmEne...' == Line 276 has weird spacing: '...nterval pmEne...' == Line 283 has weird spacing: '...wStatus pmEne...' == (4 more instances...) -- The document date (August 5, 2011) is 4646 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) ** 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-03 == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-02 == Outdated reference: A later version (-05) exists of draft-tychon-eman-applicability-statement-02 Summary: 1 error (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Chandramouli 3 Internet-Draft Cisco Systems, Inc. 4 Intended Status: Standards Track B. Schoening 5 Expires: February 5, 2012 Independent Consultant 6 J. Quittek 7 T. Dietz 8 NEC Europe Ltd. 9 B. Claise 10 Cisco Systems, Inc. 11 August 5, 2011 13 Power and Energy Monitoring MIB 14 draft-ietf-eman-energy-monitoring-mib-00 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 February 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............................................ 3 70 2. The Internet-Standard Management Framework.............. 4 71 3. Use Cases............................................... 4 72 4. Terminology............................................. 5 73 5. Architecture Concepts Applied to the MIB Module......... 5 74 5.1. Power Monitor Information............................ 11 75 5.2. Power State.......................................... 12 76 5.2.1. Power State Set...............................13 77 5.2.2. IEEE1621 Power State Set......................13 78 5.2.3. DMTF Power State Set..........................13 79 5.2.4. EMAN Power State Set..........................14 80 5.3. Power Monitor Usage Information...................... 17 81 5.4. Optional Power Usage Quality......................... 18 82 5.5. Optional Energy Measurement.......................... 19 83 5.6. Fault Management...................................... 22 84 6. Discovery............................................... 23 85 6.1. ENERGY-AWARE-MIB Module Implemented................... 23 86 6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB 87 Implemented................................................ 24 88 6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented.24 89 7. Link with the other IETF MIBs........................... 24 90 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB..24 91 7.2. Link with the ENTITY-STATE MIB......................26 92 7.3. Link with the POWER-OVER-ETHERNET MIB...............26 93 7.4. Link with the UPS MIB...............................27 94 7.5. Link with the LLDP and LLDP-MED MIBs................28 95 8. Implementation Scenario................................. 29 96 9. Structure of the MIB.................................... 31 97 10. MIB Definitions........................................ 31 98 11. Security Considerations................................ 66 99 12. IANA Considerations.................................... 67 100 12.1. IANA Considerations for the MIB Modules.............. 67 101 12.2. IANA Registration of new Power State Set............. 67 102 12.2.1. IANA Registration of the IEEE1621 Power State Set.68 103 12.2.2. IANA Registration of the DMTF Power State Set.....68 104 12.2.3. IANA Registration of the EMAN Power State Set.....69 105 12. Contributors........................................... 69 106 13. Acknowledgment......................................... 69 107 14. Open Issues............................................ 69 108 15. References............................................. 72 109 15.2. Normative References...............................72 110 15.3. Informative References.............................72 112 1. Introduction 114 This document defines a subset of the Management Information 115 Base (MIB) for use in energy management of devices within or 116 connected to communication networks. The MIB modules in this 117 document are designed to provide a model for energy management, 118 which includes monitoring for power state and energy consumption 119 of networked elements. This MIB takes into account the Power 120 Management Architecture [EMAN-FRAMEWORK], which in turn, is 121 based on the Power Monitoring Requirements [EMAN-REQ]. 123 Energy management is applicable to devices in communication 124 networks. Target devices for this specification include (but 125 are not limited to): routers, switches, Power over Ethernet 126 (PoE) endpoints, protocol gateways for building management 127 systems, intelligent meters, home energy gateways, hosts and 128 servers, sensor proxies, etc. 130 Where applicable, device monitoring extends to the individual 131 components of the device and to any attached dependent devices. 132 For example: A device can contain components that are 133 independent from a power-state point of view, such as line 134 cards, processor cards, hard drives. A device can also have 135 dependent attached devices, such as a switch with PoE endpoints 136 or a power distribution unit with attached endpoints. 138 Devices and their sub-components may be characterized by the 139 power-related attributes of a physical entity present in the 140 ENTITY MIB, even though the ENTITY MIB compliance is not a 141 requirement due to the variety and broad base of devices 142 concerned with energy management. 144 2. The Internet-Standard Management Framework 146 For a detailed overview of the documents that describe the 147 current Internet-Standard Management Framework, please refer to 148 section 7 of RFC 3410 [RFC3410]. 150 Managed objects are accessed via a virtual information store, 151 termed the Management Information Base or MIB. MIB objects are 152 generally accessed through the Simple Network Management 153 Protocol (SNMP). Objects in the MIB are defined using the 154 mechanisms defined in the Structure of Management Information 155 (SMI). This memo specifies MIB modules that are compliant to 156 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 157 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 159 3. Use Cases 161 Requirements for power and energy monitoring for networking 162 devices are specified in [EMAN-REQ]. The requirements in [EMAN- 163 REQ] cover devices typically found in communications networks, 164 such as switches, routers, and various connected endpoints. For 165 a power monitoring architecture to be useful, it should also 166 apply to facility meters, power distribution units, gateway 167 proxies for commercial building control, home automation 168 devices, and devices that interface with the utility and/or 169 smart grid. Accordingly, the scope of the MIB modules in this 170 document is broader than that specified in [EMAN-REQ]. Several 171 use cases for Energy Management have been identified in the 172 "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An 173 illustrative example scenario is presented in Section 8. " 174 Implementation Scenario". 176 4. Terminology 178 The definitions of basic terms like Power Monitor, Power Monitor 179 Parent, Power Monitor Child, Power Monitor Meter Domain, Power 180 State can be found in the Power Management Architecture [EMAN- 181 FRAMEWORK]. 183 EDITOR'S NOTE: it is foreseen that some more term will follow 184 such a Proxy, Aggregator, Energy Management, etc... 186 Power State Set 188 A Power State Set is defined as a sequence of incremental 189 energy saving modes of a device. The elements of this set can 190 be viewed as an interface for the underlying device- 191 implemented power settings of a device. Examples of Power 192 State Sets include DTMF [DMTF], IEEE1621 [IEEE1621], ACPI 193 [ACPI] and EMAN. 195 Power State 197 A Power State is defined as a specific power setting for a 198 Power Monitor (e.g., shut, hibernate, sleep, high). Within the 199 context of a Power State Set, the Power State of a device is 200 one of the power saving modes in that Power State Set. 202 EDITOR'S NOTE: the definitions of Power State Series and Power 203 State should be copied over in [EMAN-FRAMEWORK], and referenced 204 here. 206 5. Architecture Concepts Applied to the MIB Module 208 This section describes the concepts specified in the Power 209 Monitor Architecture [EMAN-FRAMEWORK] that pertain to power 210 usage, with specific information related to the MIB module 211 specified in this document. This subsection maps to the section 212 "Architecture High Level Concepts" in the Power Monitoring 213 Architecture [EMAN-FRAMEWORK]. 215 The Energy Monitoring MIB has 2 independent MIB modules. The 216 first MIB module powerMonitorMIB is focused on measurement of 217 power and energy. The second MIB module powerQualityMIB is 218 focused on Power Quality measurement. 220 The powerMonitorMIB MIB module consists of four tables. The 221 first table pmPowerTable is indexed by pmPowerIndex and 222 pmPowerStateSetIndex. The second table pmPowerStateTable indexed 223 by pmPowerIndex, pmPowerStateSetIndex and pmPowerStateIndex. 224 pmEnergyParametersTable and pmEnergyTable are indexed by 225 pmPowerIndex. 227 pmPowerTable(1) 228 | 229 +---pmPowerEntry(1) [pmPowerIndex, pmPowerStateSet] 230 | | 231 | +-- --- Integer32 pmPowerIndex(1) 232 | +-- --- PowerStateSet pmPowerStateSet(2) 233 | +-- r-n Integer32 pmPower(3) 234 | +-- r-n Integer32 pmPowerNamePlate(4) 235 | +-- r-n UnitMultiplier pmPowerUnitMultiplier(5) 236 | +-- r-n Integer32 pmPowerAccuracy(6) 237 | +-- r-n INTEGER pmMeasurementCaliber(7) 238 | +-- r-n INTEGER pmPowerCurrentType(8) 239 | +-- r-n INTEGER pmPowerOrigin(9) 240 | +-- rwn Integer32 pmPowerAdminState(10) 241 | +-- r-n Integer32 pmPowerOperState(11) 242 | +-- r-n OwnerString pmPowerStateEnterReason(12) 243 | | 244 | | 245 +---pmPowerStateTable(2) 246 | +--pmPowerStateEntry(1) 247 | | [pmPowerIndex, 248 | | pmPowerStateSet, 249 | | pmpowerStateIndex] 250 | +-- --- Integer32 pmPowerStateIndex(1) 251 | +-- r-n Interger32 pmPowerStateMaxPower (2) 252 | +-- r-n UnitMultiplier 253 | pmPowerStatePowerUnitMultiplier (3) 254 | +-- r-n TimeTicks pmPowerStateTotalTime(4) 255 | +-- r-n Counter64 pmPowerStateEnterCount(5) 256 | 258 +pmEnergyParametersTable(1) 259 +---pmEnergyParametersEntry(1) [pmPowerIndex] 260 | 261 | +-- r-n TimeInterval 262 | pmEnergyParametersIntervalLength (1) 263 | +-- r-n Integer32 264 | pmEnergyParametersIntervalNumber (2) 265 | +-- r-n Integer32 266 | pmEnergyParametersIntervalMode (3) 267 | +-- r-n TimeInterval 268 | pmEnergyParametersIntervalWindow (4) 269 | +-- r-n Integer32 270 | pmEnergyParametersSampleRate (5) 271 | +-- r-n RowStatus pmEnergyParametersStatus (6) 272 | 273 +pmEnergyTable(1) 274 +---pmEnergyEntry(1) [pmPowerIndex] 275 | 276 | +-- r-n TimeInterval pmEnergyIntervalStartTime (1) 277 | +-- r-n Integer32 pmEnergyIntervalEnergyUsed (2) 278 | +-- r-n UnitMultiplier 279 | pmEnergyIntervalEnergyUnitMultiplier (3) 280 | +-- r-n Integer32 pmEnergyIntervalMax (4) 281 | +-- r-n TimeTicks 282 | pmEnergyIntervalDiscontinuityTime(5) 283 | +-- r-n RowStatus pmEnergyParametersStatus (6) 285 The powerQualityMIB consists of four tables. PmACPwrQualityTable 286 is indexed by pmPowerIndex. PmACPwrQualityPhaseTable is indexed 287 by pmPowerIndex and pmPhaseIndex. pmACPwrQualityWyePhaseTable 288 and pmACPwrQualityDelPhaseTable are indexed by pmPowerIndex and 289 pmPhaseIndex. 291 pmPowerTable(1) 292 | 293 +---PmACPwrQualityEntry (1) [pmPowerIndex] 294 | | 295 | | 296 | +----- INTEGER pmACPwrQualityConfiguration (1) 297 | +-- r-n Interger32 pmACPwrQualityAvgVoltage (2) 298 | +-- r-n Integer32 pmACPwrQualityAvgCurrent (3) 299 | +-- r-n Integer32 pmACPwrQualityFrequency (4) 300 | +-- r-n UnitMultiplier 301 | pmACPwrQualityPowerUnitMultiplier (5) 302 | +-- r-n Integer32 pmACPwrQualityPowerAccuracy (6) 303 | +-- r-n Interger32 pmACPwrQualityTotalActivePower (7) 304 | +-- r-n Integer32 305 | pmACPwrQualityTotalReactivePower (8) 306 | +-- r-n Integer32 pmACPwrQualityTotalApparentPower (9) 307 | +-- r-n Integer32 pmACPwrQualityTotalPowerFactor(10) 308 | +-- r-n Integer32 pmACPwrQualityThdAmpheres (11) 309 | 310 +pmACPwrQualityPhaseTable (1) 311 +---PmACPwrQualityPhaseEntry(1)[pmPowerIndex, 312 | | pmPhaseIndex] 313 | | 314 | +-- r-n Integer32 pmPhaseIndex (1) 315 | +-- r-n Integer32 316 | | pmACPwrQualityPhaseAvgCurrent (2) 317 | +-- r-n Integer32 318 | | pmACPwrQualityPhaseActivePower (3) 319 | +-- r-n Integer32 320 | | pmACPwrQualityPhaseReactivePower (4) 321 | +-- r-n Integer32 322 | | pmACPwrQualityPhaseApparentPower (5) 323 | +-- r-n Integer32 324 | | pmACPwrQualityPhasePowerFactor (6) 325 | +-- r-n Integer32 326 | | pmACPwrQualityPhaseImpedance (7) 327 | | 328 +pmACPwrQualityDelPhaseTable (1) 329 +-- pmACPwrQualityDelPhaseEntry(1) 330 | | [pmPowerIndex, 331 | | pmPhaseIndex] 332 | +-- r-n Integer32 333 | | pmACPwrQualityDelPhaseToNextPhaseVoltage (1) 334 | +-- r-n Integer32 335 | | pmACPwrQualityDelThdPhaseToNextPhaseVoltage (2) 336 | +-- r-n Integer32 pmACPwrQualityDelThdCurrent (3) 337 | | 338 +pmACPwrQualityWyePhaseTable (1) 339 +-- pmACPwrQualityWyePhaseEntry (1) 340 | | [pmPowerIndex, 341 | | pmPhaseIndex] 342 | +-- r-n Integer32 343 | | pmACPwrQualityWyePhaseToNeutralVoltage (1) 344 | +-- r-n Integer32 345 | | pmACPwrQualityWyePhaseCurrent (2) 346 | +-- r-n Integer32 347 | | pmACPwrQualityWyeThdPhaseToNeutralVoltage (3) 348 | . 350 A UML representation of the MIB objects in the two MIB modules 351 are powerMonitorMIB and powerQualityMIB are presented. 353 +--------------------------+ 354 | PowerMonitor ID | 355 | | 356 | Energy-aware-MIB (*) | 357 | | +---------------------------+ 358 | | | | 359 | pmPowerIndex | | PowerMonitor Attributes | 360 | pmPowerStateSetIndex | | | 361 +--------------------------+ | pmPowerNamePlate | 362 | | | pmPowerMeasurementCaliber | 363 | | | pmPowerOrigin | 364 | | | pmPowerCurrentType | 365 | | +---------------------------+ 366 | | | 367 | | | 368 v | v 369 +-----------------------------------------+ 370 | PowerMonitor Measurement | 371 | | 372 | pmPower | 373 | pmPowerUnitMultiplier | 374 | pmPowerAccuracy | 375 +-----------------------------------------+ 376 ^ | ^ 377 | | | 378 +-------------------------+ | | 379 | PowerMonitor State | | +------------------------+ 380 | | | | PowerMonitor State | 381 | pmPowerAdminState | | | Statistics | 382 | pmPowerOperState | | | | 383 | pmPowerStateEnterReason | | | pmPowerStateMaxPower | 384 +-------------------------+ | | pmPowerStateTotalTime | 385 | | pmPowerStateEnterCount | 386 | +------------------------+ 387 | 388 | 389 | 390 | 392 Figure 1:UML diagram for powerMonitor MIB 394 (*) Link with the ENERGY-AWARE-MIB 395 | 396 | 397 | 398 V 399 +------------------------------------+ 400 | Energy Table | 401 | | 402 | pmEnergyIntervalStartTime | 403 | pmEnergyIntervalEnergyUsed | 404 | pmEnergyIntervalMax | 405 | pmEnergyIntervalDiscontinuityTime | 406 +------------------------------------+ 408 +--------------------------+ 409 | PowerMonitor ID | 410 | | 411 | Energy-aware-MIB (*) | 412 | | 413 | pmPowerIndex | 414 | pmPowerStateSetIndex | 415 +--------------------------+ 416 | 417 v 418 +-------------------------------------+ 419 | Power Quality | 420 | | 421 | pmACPwrQualityConfiguration | 422 | pmACPwrQualityAvgVoltage | 423 | pmACPwrQualityAvgCurrent 424 | pmACPwrQualityFrequency | 425 | pmACPwrQualityPowerUnitMultiplier | 426 | pmACPwrQualityPowerAccuracy | 427 | pmACPwrQualityTotalActivePower | 428 | pmACPwrQualityTotalReactivePower | 429 | pmACPwrQualityTotalApparentPower | 430 | pmACPwrQualityTotalPowerFactor | 431 | pmACPwrQualityThdAmpheres | 432 +-------------------------------------+ ^ 433 ^ ^ | 434 | | ------- 435 | ---- | 436 | | | 437 | | | 438 +-------------------------------------+ | | 439 | Power Phase Quality | | | 440 | | | | 441 | pmPhaseIndex | | | 442 | pmACPwrQualityPhaseAvgCurrent | | | 443 | pmACPwrQualityAvgCurrent | | | 444 | pmACPwrQualityFrequency | | | 445 | pmACPwrQualityPowerUnitMultiplier | | | 446 | pmACPwrQualityPowerAccuracy | | | 447 | pmACPwrQualityPhaseActivePower | | | 448 | pmACPwrQualityPhaseReactivePower | | | 449 | pmACPwrQualityPhaselApparentPower | | | 450 | pmACPwrQualityPhaseImpedance | | | 451 +-------------------------------------+ | | 452 | | 453 | | 454 +---------------------------------------------+ | 455 | Power Quality DEL Configuration | | 456 | | | 457 | pmACPwrQualityDelPhaseToNextPhaseVoltage | | 458 | pmACPwrQualityDelThdPhaseToNextPhaseVoltage | | 459 | pmACPwrQualityDelThdCurrent | | 460 +---------------------------------------------+ | 461 | 462 | 463 +---------------------------------------------+ 464 | Power Quality WYE Configuration | 465 | | 466 | pmACPwrQualityWyePhaseToNeutralVoltage | 467 | pmACPwrQualityWyePhaseCurrent | 468 | pmACPwrQualityWyeThdPhaseToNeutralVoltage | 469 +---------------------------------------------+ 471 Figure 2: UML diagram for the powerQualityMIB 473 5.1. Power Monitor Information 475 Refer to the "Power Monitor Information" section in [EMAN- 476 FRAMEWORK] for background information. An energy aware device 477 is considered an instance of a Power Monitor as defined in the 478 [EMAN-FRAMEWORK]. 480 The Power Monitor identity information is specified in the MIB 481 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the 482 pmTable.In this table, every Power Monitor SHOULD have a 483 printable name pmName, and MUST HAVE a unique Power Monitor 484 index pmIndex. The ENERGY-AWARE-MIB module returns the 485 relationship (parent/child) between Power Monitors. 487 EDITOR'S NOTE: this last sentence will have to be updated with 488 terms such as Aggregator, Proxy, etc... when the [EMAN- 489 FRAMEWORK] will stabilize. 491 5.2. Power State 493 Refer to the "Power Monitor States" section in [EMAN-FRAMEWORK] 494 for background information. 496 A Power Monitor may have energy conservation modes called Power 497 States. Between the ON and OFF states of a device, there can be 498 several intermediate energy saving modes. Those energy saving 499 modes are called as Power States. 501 Power States, which represent universal states of power 502 management of a Power Monitor, are specified by the pmPowerState 503 MIB object. The actual Power State is specified by the 504 pmPowerOperState MIB object, while the pmPowerAdminState MIB 505 object specifies the Power State requested for the Power 506 Monitor. The difference between the values of pmPowerOperState 507 and pmPowerAdminState can be attributed that the Power Monitor 508 is busy transitioning from pmPowerAdminState into the 509 pmPowerOperState, at which point it will update the content of 510 pmPowerOperState. In addition, the possible reason for change 511 in Power State is reported in pmPowerStateEnterReason. 512 Regarding pmPowerStateEnterReason, management stations and Power 513 Monitors should support any format of the owner string dictated 514 by the local policy of the organization. It is suggested that 515 this name contain at least the reason for the transition change, 516 and one or more of the following: IP address, management station 517 name, network manager's name, location, or phone number. 519 The MIB objects pmPowerOperState, pmPowerAdminState , and 520 pmPowerStateEnterReason are contained in the pmPowerTable MIB 521 table. 523 The pmPowerStateTable table enumerates the maximum power usage 524 in watts, for every single supported Power State of each Power 525 State Set supported by the Power Monitor In addition, 526 PowerStateTable provides additional statistics: 527 pmPowerStateEnterCount, the number of times an entity has 528 visited a particular Power State, and pmPowerStateTotalTime, the 529 total time spent in a particular Power State of a Power Monitor. 531 5.2.1. Power State Set 533 There are several standards and implementations of Power State 534 Sets. A Power Monitor can support one or multiple Power State 535 Set implementation(s) concurrently. 537 There are currently three Power State Sets advocated: 539 Reserved(0) 540 IEEE1621(1) - [IEEE1621] 541 DMTF(2) - [DMTF] 542 EMAN(3) - [EMAN-MONITORING-MIB] 544 The respective specific states related to each Power State Set 545 are specified in the following sections. 547 5.2.2. IEEE1621 Power State Set 549 The IEEE1621 Power State Set [IEEE1621] consists of 3 550 rudimentary states : on, off or sleep. 551 on(0) - The device is fully On and all features of the 552 device are in working mode. 553 off(1) - The device is mechanically switched off and does 554 not consume energy. 555 sleep(2) - The device is in a power saving mode, and some 556 features may not be available immediately. 558 5.2.3. DMTF Power State Set 560 DMTF [DMTF] standards organization has defined a power profile 561 standard based on the CIM (Common Information Model) model that 562 consists of 15 power states ON (2), SleepLight (3), SleepDeep 563 (4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off- 564 Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10), 565 Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard 566 Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off- 567 Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF 568 standard is targeted for hosts and computers. Details of the 569 semantics of each Power State within the DMTF Power State Set 570 can be obtained from the DMTF Power State Management Profile 571 specification [DMTF]. 573 DMTF power profile extends ACPI power states. The following 574 table provides a mapping between DMTF and ACPI Power State Set: 576 --------------------------------------------------- 577 | DMTF | ACPI | 578 | Power State | Power State | 579 --------------------------------------------------- 580 | Reserved(0) | | 581 --------------------------------------------------- 582 | Reserved(1) | | 583 --------------------------------------------------- 584 | ON (2) | G0-S0 | 585 -------------------------------------------------- 586 | Sleep-Light (3) | G1-S1 G1-S2 | 587 -------------------------------------------------- 588 | Sleep-Deep (4) | G1-S3 | 589 -------------------------------------------------- 590 | Power Cycle (Off-Soft) (5) | G2-S5 | 591 --------------------------------------------------- 592 | Off-hard (6) | G3 | 593 --------------------------------------------------- 594 | Hibernate (Off-Soft) (7) | G1-S4 | 595 --------------------------------------------------- 596 | Off-Soft (8) | G2-S5 | 597 --------------------------------------------------- 598 | Power Cycle (Off-Hard) (9) | G3 | 599 --------------------------------------------------- 600 | Master Bus Reset (10) | G2-S5 | 601 --------------------------------------------------- 602 | Diagnostic Interrupt (11) | G2-S5 | 603 --------------------------------------------------- 604 | Off-Soft Graceful (12) | G2-S5 | 605 --------------------------------------------------- 606 | Off-Hard Graceful (13) | G3 | 607 --------------------------------------------------- 608 | MasterBus Reset Graceful (14) | G2-S5 | 609 --------------------------------------------------- 610 | Power Cycle off-soft Graceful (15)| G2-S5 | 611 --------------------------------------------------- 612 | Power Cycle off-hard Graceful (16)| G3 | 613 --------------------------------------------------- 614 Figure 3: DMTF and ACPI Powe State Set Mapping 616 5.2.4. EMAN Power State Set 618 The EMAN Power State Set represents an attempt for a uniform 619 standard approach to model the different levels of power 620 consumption of a device. The EMAN Power States are an expansion 621 of the basic Power States as defined in IEEE1621 that also 622 incorporate the Power States defined in ACPI and DMTF. 623 Therefore, in addition to the non-operational states as defined 624 in ACPI and DMTF standards, several intermediate operational 625 states have been defined. 627 There are twelve Power States, that expand on IEEE1621 on,sleep 628 and off. The expanded list of Power States are divided into six 629 operational states, and six non-operational states. The lowest 630 non-operational state is 1 and the highest is 6. Each non- 631 operational state corresponds to an ACPI state [ACPI] 632 corresponding to Global and System states between G3 (hard-off) 633 and G1 (sleeping). For Each operational state represent a 634 performance state, and may be mapped to ACPI states P0 (maximum 635 performance power) through P5 (minimum performance and minimum 636 power). 638 An Power Monitor may have fewer Power States than twelve and 639 would then map several policy states to the same power state. 640 Power Monitor with more than twelve states, would choose which 641 twelve to represent as power policy states. 643 In each of the non-operational states (from mechoff(1) to 644 ready(6)), the Power State preceding it is expected to have a 645 lower power consumption and a longer delay in returning to an 646 operational state: 648 IEEE1621 Power(off): 650 mechoff(1) : An off state where no entity features are 651 available. The entity is unavailable. 652 No energy is being consumed and the power 653 connector can be removed. This 654 corresponds to ACPI state G3. 656 softoff(2) : Similar to mechoff(1), but some 657 components remain powered or receive 658 trace power so that the entity 659 can be awakened from its off state. In 660 softoff(2), no context is saved and the 661 device typically requires a complete boot 662 when awakened. This corresponds to ACPI 663 state G2. 665 IEEE1621 Power(sleep) 667 hibernate(3): No entity features are available. The 668 entity may be awakened without requiring 669 a complete boot, but the time for 670 availability is longer than sleep(4). An 671 example for state hibernate(3) is a save 672 to-disk state where DRAM context is not 673 maintained. Typically, energy consumption 674 is zero or close to zero. This 675 corresponds to state G1, S4 in ACPI. 677 sleep(4) : No entity features are available, except 678 for out-of-band management, for example 679 wake-up mechanisms. The time for 680 availability is longer than standby(5). 681 An example for state sleep(4) is a save- 682 to-RAM state, where DRAM context is 683 maintained. Typically, energy 684 consumption is close to zero. This 685 corresponds to state G1, S3 in ACPI. 687 standby(5) : No entity features are available, except 688 for out-of-band management, for example 689 wake-up mechanisms. This mode is analogous 690 to cold-standy. The time for availability 691 is longer than ready(6). For example, the 692 processor context is not maintained. 693 Typically, energy consumption is close to 694 zero. This corresponds to state G1, S2 in 695 ACPI. 697 ready(6) : No entity features are available, except 698 for out-of-band management, for example 699 wake-up mechanisms. This mode is 700 analogous to hot-standby. The entity can 701 be quickly transitioned into an 702 operational state. For example, 703 processors are not executing, but 704 processor context is maintained. This 705 corresponds to state G1, S1 in ACPI. 707 IEEE1621 Power(on): 709 lowMinus(7) : Indicates some entity features may not be 710 available and the entity has selected 711 measures/options to provide less than 712 low(8) usage. This corresponds to 713 ACPI State G0. This includes operational 714 states lowMinus(7) to full(12). 716 low(8) : Indicates some features may not be 717 available and the entity has taken 718 measures or selected options to provide 719 less than mediumMinus(9) usage. 721 mediumMinus(9): Indicates all entity features are 722 available but the entity has taken 723 measures or selected options to provide 724 less than medium(10) usage. 726 medium(10) : Indicates all entity features are 727 available but the entity has taken 728 measures or selected options to provide 729 less than highMinus(11) usage. 731 highMinus(11): Indicates all entity features are 732 available and power usage is less 733 than high(12). 735 high(12) : Indicates all entity features are 736 available and the entity is consuming the 737 highest power. 739 5.3. Power Monitor Usage Information 741 Refer to the "Power Monitor Usage Measurement" section in [EMAN- 742 FRAMEWORK] for background information. 744 For a Power Monitor, power usage is reported using pmPower. The 745 magnitude of measurement is based on the pmPowerUnitMultiplier 746 MIB variable, based on the UnitMultiplier Textual Convention 747 (TC). Power measurement magnitude should conform to the IEC 748 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22] 749 definition of unit multiplier for the SI (System International) 750 units of measure. Measured values are represented in SI units 751 obtained by BaseValue * 10 raised to the power of the scale. 753 For example, if current power usage of a Power Monitor is 3, it 754 could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of 755 pmPowerUnitMultiplier. Note that other measurements throughout 756 the two MIB modules in this document use the same mechanism, 757 including pmPowerStatePowerUnitMultiplier, 758 pmEnergyIntervalEnergyUnitMultiplier, and 759 pmACPwrQualityPowerUnitMultiplier. 761 In addition to knowing the usage and magnitude, it is useful to 762 know how a pmPower measurement was obtained. An NMS can use 763 this to account for the accuracy and nature of the reading 764 between different implementations. For this pmPowerOrigin 765 describes whether the measurements were made at the device 766 itself or from a remote source. The pmPowerMeasurementCaliber 767 describes the method that was used to measure the power and can 768 distinguish actual or estimated values. There may be devices in 769 the network, which may not be able to measure or report power 770 consumption. For those devices, the object 771 pmPowerMeasurementCaliber shall report that measurement 772 mechanism is "unavailable" and the pmPower measurement shall be 773 "0". 775 The nameplate power rating of a Power Monitor is specified in 776 pmPowerNameplate MIB object. 778 5.4. Optional Power Usage Quality 780 Refer to the "Optional Power Usage Quality" section in [EMAN- 781 FRAMEWORK] for background information. 783 The optional powerQualityMIB MIB module can be implemented to 784 further describe power usage quality measurement. The 785 powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 786 standard to describe AC measurements. 788 The powerQualityMIB MIB module contains a primary table, the 789 pmACPwrQualityTable table, that defines power quality 790 measurements for supported pmIndex entities, as a sparse 791 extension of the pmPowerTable (with pmPowerIndex as primary 792 index). This pmACPwrQualityTable table contains such 793 information as the configuration (single phase, DEL 3 phases, 794 WYE 3 phases), voltage, frequency, power accuracy, total 795 active/reactive power/apparent power, amperage, and voltage. 797 In case of 3-phase power, the pmACPwrQualityPhaseTable 798 additional table is populated with power quality measurements 799 per phase (so double indexed by the pmPowerIndex and 800 pmPhaseIndex). This table, which describes attributes common to 801 both WYE and DEL configurations, contains the average current, 802 active/reactive/apparent power, power factor, and impedance. 804 In case of 3-phase power with a DEL configuration, the 805 pmACPwrQualityDelPhaseTable table describes the phase-to-phase 806 power quality measurements, i.e., voltage and current. 808 In case of 3-phase power with a Wye configuration, the 809 pmACPwrQualityWyePhaseTable table describes the phase-to-neutral 810 power quality measurements, i.e., voltage and current. 812 5.5. Optional Energy Measurement 814 Refer to the "Optional Energy and demand Measurement" section in 815 [EMAN-FRAMEWORK] for the definition and terminology information. 817 It is relevant to measure energy when there are actual power 818 measurements from a Power Monitor, and not when the power 819 measurement is assumed or predicted as specified in the 820 description clause of the object pmPowerMeasurementCaliber. 822 Two tables are introduced to characterize energy measurement of 823 a Power Monitor: pmEnergyTable and pmEnergyParametersTable. 824 Both energy and demand information can be represented via the 825 pmEnergyTable. Energy information will be an accumulation with 826 no interval. Demand information can be represented as an 827 average accumulation per interval of time. 829 The pmEnergyParametersTable consists of the parameters defining 830 the duration of measurement intervals in seconds, 831 (pmEnergyParametersIntervalLength), the number of successive 832 intervals to be stored in the pmEnergyTable, 833 (pmEnergyParametersIntervalNumber), the type of measurement 834 technique (pmEnergyParametersIntervalMode), and a sample rate 835 used to calculate the average (pmEnergyParametersSampleRate). 836 Judicious choice of the sampling rate will ensure accurate 837 measurement of energy while not imposing an excessive polling 838 burden. 840 There are three pmEnergyParametersIntervalMode types used for 841 energy measurement collection: period, sliding, and total. The 842 choices of the the three different modes of collection are based 843 on IEC standard 61850-7-4. Note that multiple 844 pmEnergyParametersIntervalMode types MAY be configured 845 simultaneously. 847 These three pmEnergyParametersIntervalMode types are illustrated 848 by the following three figures, for which: 850 - The horizontal axis represents the current time, with the 851 symbol <--- L ---> expressing the 852 pmEnergyParametersIntervalLength, and the 853 pmEnergyIntervalStartTime is represented by S1, S2, S3, S4, ..., 854 Sx where x is the value of pmEnergyParametersIntervalNumber. 856 - The vertical axis represents the time interval of sampling and 857 the value of pmEnergyIntervalEnergyUsed can be obtained at the 858 end of the sampling period. The symbol =========== denotes the 859 duration of the sampling period. 861 | | | =========== | 862 |============ | | | 863 | | | | 864 | |============ | | 865 | | | | 866 | <--- L ---> | <--- L ---> | <--- L ---> | 867 | | | | 868 S1 S2 S3 S4 870 Figure 4 : Period pmEnergyParametersIntervalMode 872 A pmEnergyParametersIntervalMode type of 'period' specifies non- 873 overlapping periodic measurements. Therefore, the next 874 pmEnergyIntervalStartTime is equal to the previous 875 pmEnergyIntervalStartTime plus pmEnergyParametersIntervalLength. 876 S2=S1+L; S3=S2+L, ... 878 |============ | 879 | | 880 | <--- L ---> | 881 | | 882 | |============ | 883 | | | 884 | | <--- L ---> | 885 | | | 886 | | |============ | 887 | | | | 888 | | | <--- L ---> | 889 | | | | 890 | | | |============ | 891 | | | | | 892 | | | | <--- L ---> | 893 S1 | | | | 894 | | | | 895 | | | | 896 S2 | | | 897 | | | 898 | | | 899 S3 | | 900 | | 901 | | 902 S4 904 Figure 5 : Sliding pmEnergyParametersIntervalMode 906 A pmEnergyParametersIntervalMode type of 'sliding' specifies 907 overlapping periodic measurements. 909 | | 910 |========================= | 911 | | 912 | | 913 | | 914 | <--- Total length ---> | 915 | | 916 S1 918 Figure 4 : Total pmEnergyParametersIntervalMode 920 A pmEnergyParametersIntervalMode type of 'total' specifies a 921 continuous measurement since the last reset. The value of 922 pmEnergyParametersIntervalNumber should be (1) one and 923 pmEnergyParametersIntervalLength is ignored. 925 The pmEnergyParametersStatus is used to start and stop energy 926 usage logging. The status of this variable is "active" when 927 all the objects in pmEnergyParametersTable are appropriate which 928 in turn indicates if pmEnergyTable entries exist or not. 930 The pmEnergyTable consists of energy measurements 931 inpmEnergyIntervalEnergyUsed , the units of the measured energy 932 pmEnergyIntervalEnergyUnitMultiplier, and the maximum observed 933 energy within a window - pmEnergyIntervalMax. 935 Measurements of the total energy consumed by a Power Monitor may 936 suffer from interruptions in the continuous measurement of 937 energy consumption. In order to indicate such interruptions, 938 the object pmEnergyIntervalDiscontinuityTime is provided for 939 indicating the time of the last interruption of total energy 940 measurement. pmEnergyIntervalDiscontinuityTime shall indicate 941 the sysUpTime [RFC3418] when the device was reset. 943 The following example illustrates the pmEnergyTable and 944 pmEnergyParametersTable: 946 First, in order to estimate energy, a time interval to sample 947 energy should be specified, i.e. 948 pmEnergyParametersIntervalLength can be set to "900 seconds" or 949 15 minutes and the number of consecutive intervals over which 950 the maximum energy is calculated 951 (pmEnergyParametersIntervalNumber) as "10". The sampling rate 952 internal to the Power Monitor for measurement of power usage 953 (pmEnergyParametersSampleRate) can be "1000 milliseconds", as 954 set by the Power Monitor as a reasonable value. Then, the 955 pmEnergyParametersStatus is set to active (value 1) to indicate 956 that the Power Monitor should start monitoring the usage per the 957 pmEnergyTable. 959 The indices in the pmEnergyTable are pmPowerIndex, which 960 identifies the Power Monitor, and pmEnergyIntervalStartTime, 961 which denotes the start time of the energy measurement interval 962 based on sysUpTime [RFC3418]. The value of 963 pmEnergyIntervalEnergyUsed is the measured energy consumption 964 over the time interval specified 965 (pmEnergyParametersIntervalLength) based on the Power Monitor 966 internal sampling rate (pmEnergyParametersSampleRate). While 967 choosing the values for the pmEnergyParametersIntervalLength and 968 pmEnergyParametersSampleRate, it is recommended to take into 969 consideration either the network element resources adequate to 970 process and store the sample values, and the mechanism used to 971 calculate the pmEnergyIntervalEnergyUsed. The units are derived 972 from pmEnergyIntervalPowerUnitMultiplier. For example, 973 pmEnergyIntervalPowerUsed can be "100" with 974 pmEnergyIntervalPowerUnits equal to 0, the measured energy 975 consumption of the Power Monitor is 100 watt-hours. The 976 pmEnergyIntervalMax is the maximum energyobserved and that can 977 be "150 watt-hours". 979 The pmEnergyTable has a buffer to retain a certain number of 980 intervals, as defined by pmEnergyParametersIntervalNumber. If 981 the default value of "10" is kept, then the pmEnergyTable 982 contains 10 energymeasurements, including the maximum. 984 Here is a brief explanation of how the maximum energy can be 985 calculated. The first observed energy measurement value is 986 taken to be the initial maximum. With each subsequent 987 measurement, based on numerical comparison, maximum energy may 988 be updated. The maximum value is retained as long as the 989 measurements are taking place. Based on periodic polling of 990 this table, an NMS could compute the maximum over a longer 991 period, i.e. a month, 3 months, or a year. 993 5.6. Fault Management 995 [EMAN-REQ] specifies requirements about Power States such as 996 "the current power state" , "the time of the last state change", 997 "the total time spent in each state", "the number of transitions 998 to each state" etc. Some of these requirements are fulfilled 999 explicitly by MIB objects such as pmPowerOperState, 1000 pmPowerStateTotalTime and pmPowerStateEnterCount. Some of the 1001 other requirements are met via the SNMP NOTIFICATION mechanism. 1002 pmPowerStateChange SNMP notification which is generated when the 1003 value(s) of pmPowerStateSet, pmPowerOperState, pmPowerAdminState 1004 have changed. 1006 6. Discovery 1008 6.1. ENERGY-AWARE-MIB Module Implemented 1010 The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- 1011 MIB], if available, in order to discover all the Power Monitors 1012 and the relationships between those (notion of Parent/Child). 1013 In the ENERGY-AWARE-MIB module tables, the Power Monitors are 1014 indexed by the pmIndex. 1016 If an implementation of the ENERGY-AWARE-MIB module is available 1017 in the local SNMP context, for the same Power Monitor, the 1018 pmIndex value (EMAN-AWARE-MIB) MUST be assigned to the 1019 pmPowerIndex for The pmPowerIndex characterizes the Power 1020 Monitor in the powerMonitorMIB and powerQualityMIB MIB modules 1021 (this document). 1023 From there, the NMS must poll the pmPowerStateTable (specified 1024 in the powerMonitorMIB module in this document), which 1025 enumerates, amongst other things, the maximum power usage. As 1026 the entries in pmPowerStateTable table are indexed by the Power 1027 Monitor (pmPowerIndex), by the Power State Set 1028 (pmPowerStateSetIndex), and by the Power State 1029 (pmPowerStateIndex), the maximum power usage is discovered per 1030 Power Monitor, per Power State Set, and per Power Usage. In 1031 other words, polling the pmPowerStateTable allows the discovery 1032 of each Power State within every Power State Set supported by 1033 the Power Monitor. 1035 If the Power Monitor is an Aggregator or a Proxy, the MIB module 1036 would be populated with the Power Monitor Parent and Children 1037 information, which have their own Power Monitor index value 1038 (pmPowerIndex). However, the parent/child relationship must be 1039 discovered thanks to the ENERGY-AWARE-MIB module. 1041 Finally, the NMS can monitor the Power Quality thanks to the 1042 powerQualityMIB MIB module, which reuses the pmPowerIndex to 1043 index the Power Monitor. 1045 6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB 1046 Implemented 1048 When the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] is not 1049 implemented, the NMS must poll the ENTITY-MIB [RFC4133] in order 1050 to discover some more information about the Power Monitors. 1051 Indeed, the index for the Power Monitors in the MIB modules 1052 specified in this document is the pmPowerIndex, which specifies: 1053 "If there is no implementation of the ENERGY-AWARE-MIB module 1054 but one of the ENTITY MIB module is available in the local SNMP 1055 context, then the same index of an entity MUST be chosen as 1056 assigned to the entity by object entPhysicalIndex in the ENTITY 1057 MIB module." 1059 As the Section 6.1. , the NMS must then poll the 1060 pmPowerStateTable (specified in the powerMonitorMIB module in 1061 this document), indexed by the Power Monitor (pmPowerIndex that 1062 inherited the entPhysicalIndex value), by the Power State Set 1063 (pmPowerStateSetIndex), and by the Power State 1064 (pmPowerStateIndex). Then the NMS has discovered every Power 1065 State within each Power State Set supported by the Power 1066 Monitor. 1068 Note that, without the ENERGY-AWARE-MIB module, the Power 1069 Monitor acts as an standalone device, i.e. the notion of 1070 parent/child can't be specified. 1072 6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented 1074 If neither the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] nor of 1075 the ENTITY MIB module [RFC4133] are available in the local SNMP 1076 context, then this MIB module may choose identity values from a 1077 further MIB module providing entity identities. 1079 Note that, without the ENERGY-AWARE-MIB module, the Power 1080 Monitor acts as an standalone device, i.e. the notion of 1081 parent/child can't be specified. 1083 7. Link with the other IETF MIBs 1085 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB 1087 RFC 4133 [RFC4133] defines the ENTITY MIB module that lists the 1088 physical entities of a networking device (router, switch, etc.) 1089 and those physical entities indexed by entPhysicalIndex. From 1090 an energy-management standpoint, the physical entities that 1091 consume or produce energy are of interest. 1093 RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that 1094 provides a standardized way of obtaining information (current 1095 value of the sensor, operational status of the sensor, and the 1096 data units precision) from sensors embedded in networking 1097 devices. Sensors are associated with each index of 1098 entPhysicalIndex of the ENTITY MIB [RFC4133]. While the focus 1099 of the Power and Energy Monitoring MIB is on measurement of 1100 power usage of networking equipment indexed by the ENTITY MIB, 1101 this MIB proposes a customized power scale for power measurement 1102 and different power state states of networking equipment, and 1103 functionality to configure the power state states. 1105 When this MIB module is used to monitor the power usage of 1106 devices like routers and switches, the ENTITY MIB and ENTITY- 1107 SENSOR MIB SHOULD be implemented. In such cases, the Power 1108 Monitors are modeled by the entPhysicalIndex through the 1109 pmPhysicalEntity MIB object specified in the pmTable in the 1110 ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. 1112 However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI 1113 C12.x accuracy classes required for electricity (i.e., 1%, 2%, 1114 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 1115 represents "The number of decimal places of precision in fixed- 1116 point sensor values returned by the associated entPhySensorValue 1117 object". The ANSI and IEC Standards are used for power 1118 measurement and these standards require that we use an accuracy 1119 class, not the scientific-number precision model specified in 1120 RFC3433. The pmPowerAccuracy MIB object models this accuracy. 1121 Note that pmPowerUnitMultipler represents the scale factor per 1122 IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], 1123 which is a more logical representation for power measurements 1124 (compared to entPhySensorScale), with the mantissa and the 1125 exponent values X * 10 ^ Y. 1127 Power measurements specifying the qualifier 'UNITS' for each 1128 measured value in watts are used in the LLDP-EXT-MED-MIB, POE 1129 [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier 1130 is used for the power measurement values. 1132 One cannot assume that the ENTITY MIB and ENTITY-SENSOR MIB are 1133 implemented for all Power Monitors that need to be monitored. A 1134 typical example is a converged building gateway, monitoring 1135 several other devices in the building, doing the proxy between 1136 SNMP and a protocol like BACNET. Another example is the home 1137 energy controller. In such cases, the pmPhysicalEntity value 1138 contains the zero value, thanks to PhysicalIndexOrZero textual 1139 convention. 1141 The pmPowerIndex MIB object has been kept as the unique Power 1142 Monitor index. The pmPower is similar to entPhySensorValue 1143 [RFC3433] and the pmPowerUnitMultipler is similar to 1144 entPhySensorScale. 1146 7.2. Link with the ENTITY-STATE MIB 1148 For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE 1149 MIB [RFC4268] specifies the operational states (entStateOper: 1150 unknown, enabled, disabled, testing), the alarm (entStateAlarm: 1151 unknown, underRepair, critical, major, minor, warning, 1152 indeterminate) and the possible values of standby states 1153 (entStateStandby: unknown, hotStandby, coldStandby, 1154 providingService). 1156 From a power monitoring point of view, in contrast to the entity 1157 operational states of entities, Power States are required, as 1158 proposed in the Power and Energy Monitoring MIB module. Those 1159 Power States can be mapped to the different operational states 1160 in the ENTITY-STATE MIB, if a formal mapping is required. For 1161 example, the entStateStandby "unknown", "hotStandby", 1162 "coldStandby", states could map to the Power State "unknown", 1163 "ready", "standby", respectively, while the entStateStandby 1164 "providingService" could map to any "low" to "high" Power State. 1166 7.3. Link with the POWER-OVER-ETHERNET MIB 1168 Power-over-Ethernet MIB [RFC3621] provides an energy monitoring 1169 and configuration framework for power over Ethernet devices. 1170 The RFC introduces a concept of a port group on a switch to 1171 define power monitoring and management policy and does not use 1172 the entPhysicalIndex as the index. Indeed, the 1173 pethMainPseConsumptionPower is indexed by the 1174 pethMainPseGroupIndex, which has no mapping with the 1175 entPhysicalIndex. 1177 One cannot assume that the Power-over-Ethernet MIB is 1178 implemented for all Power Monitors that need to be monitored. A 1179 typical example is a converged building gateway, monitoring 1180 several other devices in the building, doing the proxy between 1181 SNMP and a protocol like BACNET. Another example is the home 1182 energy controller. In such cases, the pmethPortIndex and 1183 pmethPortGrpIndex values contain the zero value, thanks to new 1184 PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero 1185 conventions. 1187 However, if the Power-over-Ethernet MIB [RFC3621] is supported, 1188 the Power Monitor pmethPortIndex and pmethPortGrpIndex contain 1189 the pethPsePortIndex and pethPsePortGroupIndex, respectively. 1191 As a consequence, the pmPowerIndex MIB object has been kept as 1192 the unique Power Monitor index. 1194 Note that, even though the Power-over-Ethernet MIB [RFC3621] was 1195 created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse 1196 the precision notion from the ENTITY-SENSOR MIB, i.e. the 1197 entPhySensorPrecision MIB object. 1199 7.4. Link with the UPS MIB 1201 To protect against unexpected power disruption, data centers and 1202 buildings make use of Uninterruptible Power Supplies (UPS). To 1203 protect critical assets, a UPS can be restricted to a particular 1204 subset or domain of the network. UPS usage typically lasts only 1205 for a finite period of time, until normal power supply is 1206 restored. Planning is required to decide on the capacity of the 1207 UPS based on output power and duration of probable power outage. 1208 To properly provision UPS power in a data center or building, it 1209 is important to first understand the total demand required to 1210 support all the entities in the site. This demand can be 1211 assessed and monitored via the Power and Energy Monitoring MIB. 1213 UPS MIB [RFC1628] provides information on the state of the UPS 1214 network. Implementation of the UPS MIB is useful at the 1215 aggregate level of a data center or a building. The MIB module 1216 contains several groups of variables: 1218 - upsIdent: Identifies the UPS entity (name, model, etc.). 1220 - upsBattery group: Indicates the battery state 1221 (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) 1223 - upsInput group: Characterizes the input load to the UPS 1224 (number of input lines, voltage, current, etc.). 1226 - upsOutput: Characterizes the output from the UPS (number of 1227 output lines, voltage, current, etc.) 1229 - upsAlarms: Indicates the various alarm events. 1231 The measurement of power in the UPS MIB is in Volts, Amperes and 1232 Watts. The units of power measurement are RMS volts and RMS 1233 Amperes. They are not based on the EntitySensorDataScale and 1234 EntitySensorDataPrecision of Entity-Sensor MIB. 1236 Both the Power and Energy Monitoring MIB and the UPS MIB may be 1237 implemented on the same UPS SNMP agent, without conflict. In 1238 this case, the UPS device itself is the Power Monitor Parent and 1239 any of the UPS meters or submeters are the Power Monitor 1240 Children. 1242 7.5. Link with the LLDP and LLDP-MED MIBs 1244 The LLDP Protocol is a Data Link Layer protocol used by network 1245 devices to advertise their identities, capabilities, and 1246 interconnections on a LAN network. 1248 The Media Endpoint Discovery is an enhancement of LLDP, known as 1249 LLDP-MED. The LLDP-MED enhancements specifically address voice 1250 applications. LLDP-MED covers 6 basic areas: capability 1251 discovery, LAN speed and duplex discovery, network policy 1252 discovery, location identification discovery, inventory 1253 discovery, and power discovery. 1255 Of particular interest to the current MIB module is the power 1256 discovery, which allows the endpoint device (such as a PoE 1257 phone) to convey power requirements to the switch. In power 1258 discovery, LLDP-MED has four Type Length Values (TLVs): power 1259 type, power source, power priority and power value. 1260 Respectively, those TLVs provide information related to the type 1261 of power (power sourcing entity versus powered device), how the 1262 device is powered (from the line, from a backup source, from 1263 external power source, etc.), the power priority (how important 1264 is it that this device has power?), and how much power the 1265 device needs. 1267 The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 1268 actually comes from the Power-over-Ethernet MIB [RFC3621]. If 1269 the Power-over-Ethernet MIB [RFC3621] is supported, the exact 1270 value from the pethPsePortPowerPriority [RFC3621] is copied over 1271 in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise 1272 the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From 1273 the Power and Energy Monitoring MIB, it is possible to identify 1274 the pethPsePortPowerPriority [RFC3621], thanks to the 1275 pmethPortIndex and pmethPortGrpIndex. 1277 The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to 1278 pmPowerOrigin in indicating if the power for an attached device 1279 is local or from a remote device. If the LLDP-MED MIB is 1280 supported, the following mapping can be applied to the 1281 pmPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and 1282 local(3) can be mapped to remote(2) and self(1), respectively. 1284 8. Implementation Scenario 1286 This section provides an illustrative example scenario for the 1287 implementation of the Power Monitor, including Power Monitor 1288 Parent and Power Monitor Child relationships. 1290 Example Scenario of a campus network: Switch with PoE Endpoints 1291 with further connected Devices 1293 The campus network consists of switches that provide LAN 1294 connectivity. The switch with PoE ports is located in wiring 1295 closet. PoE IP phones are connected to the switch. The IP 1296 phones draw power from the PoE ports of the switch. In 1297 addition, a PC is daisy-chained from the IP phone for LAN 1298 connectivity. 1300 The IP phone consumes power from the PoE switch, while the PC 1301 consumes power from the wall outlet. 1303 The switch has implementations of Entity MIB [RFC4133] and 1304 energy-aware MIB [EMAN-AWARE-MIB] while the PC does not have 1305 implementation of the Entity MIB, but has an implementation of 1306 energy-aware MIB. The switch has the following attributes, 1307 pmPowerIndex "1", pmPhysicalEntity "2", and pmPowerMonitorId 1308 "UUID 1000". The power usage of the switch is "440 Watts". The 1309 switch does not have a Power Monitor Parent. 1311 The PoE switch port has the following attributes: The switch 1312 port has pmPowerIndex "3", pmPhysicalEntity is "12" and 1313 pmPowerMonitorId is "UUID 1000:3". The power metered at the POE 1314 switch port is "12 watts". In this example, the POE switch port 1315 has the switch as the Power Monitor Parent, with its pmParentID 1316 of "1000". 1318 The attributes of the PC are given below. The PC does not 1319 implementation of Entity MIB, and thus does not have 1320 pmPhysicalEntity. The pmPowerIndex (pmPIndex) of the PC is 1321 "57", the pmPowerMonitorId is "UUID 1000:57 ". The PC has a 1322 Power Monitor Parent, i.e. the switch port whose 1323 pmPowerMonitorId is "UUID 1000:3". The power usage of the PC is 1324 "120 Watts" and is communicated to the switch port. 1326 This example illustrates the important distinction between the 1327 Power Monitor Children: The IP phone draws power from the 1328 switch, while the PC has LAN connectivity from the phone, but is 1329 powered from the wall outlet. However, the Power Monitor Parent 1330 sends power control messages to both the Power Monitor Children 1331 (IP phone and PC) and the Children react to those messages. 1333 |--------------------------------------------------------------| 1334 | Switch | 1335 |==============================================================| 1336 | Switch | Switch | Switch | Switch | Switch | 1337 | pmPIndex | pmPhyIdx | pmPowerMonId | pmParentId | pmPower | 1338 | ============================================================ | 1339 | 1 | 2 | UUID 1000 | null | 440 | 1340 | ============================================================ | 1341 | | 1342 | SWITCH PORT | 1343 | ============================================================ | 1344 | | Switch | Switch | Switch | Switch | Switch | 1345 | | Port | Port | Port | Port | Port | | 1346 | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | 1347 | ============================================================ | 1348 | | 3 | 12 | UUID 1000:3 | UUID 1000 | 12 | | 1349 | ============================================================ | 1350 | ^ | 1351 | | | 1352 |-----------------------------------|--------------------------| 1353 | 1354 | 1355 POE IP PHONE | 1356 | 1357 | 1358 ============================================================= 1359 | IP phone | IP phone |IP phone |IP phone |IP phone| 1360 | pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower| 1361 =========================================================== 1362 | 31 | 0 | UUID 1000:31 | UUID 1000:3 | 12 | 1363 ============================================================ 1364 | 1365 | 1366 PC connected to switch via IP phone | 1367 | 1368 ============================================================= 1369 | PC | PC |PC |PC | PC | 1370 |pmPIndex| pmPhyIdx|pmPowerMonitorId|pmParentID| pmPower | 1371 ============================================================ 1372 | 57 | 0 | UUID 1000:57 | UUID 1000:3 | 120 | 1373 ============================================================= 1375 Figure 1: Example scenario 1377 9. Structure of the MIB 1379 The primary MIB object in this MIB module is the 1380 PowerMonitorMIBObject. The pmPowerTable table of 1381 PowerMonitorMibObject describes the power measurement attributes 1382 of a Power Monitor entity. The notion of identity of the device 1383 in terms of uniquely identification of the Power Monitor and its 1384 relationship to other entities in the network are addressed in 1385 [EMAN-AWARE-MIB]. 1387 The power measurement of Power Monitor contains information 1388 describing its power usage (pmPower) and its current power state 1389 (pmPowerOperState). In addition to power usage, additional 1390 information describing the units of measurement 1391 (pmPowerAccuracy, pmPowerUnitMultiplier), how power usage 1392 measurement was obtained (pmPowerMeasurementCaliber), the 1393 source of power (pmPowerOrigin) and the type of power 1394 (pmPowerCurrentTtype) are described. 1396 A Power Monitor may contain an optional pmPowerQuality table 1397 that describes the electrical characteristics associated with 1398 the current power state and usage. 1400 A Power Monitor may contain an optional pmEnergyTable to 1401 describe energy measurement information over time. 1403 A Power Monitor may also contain optional battery information 1404 associated with this entity. 1406 10. MIB Definitions 1408 -- ************************************************************ 1409 -- 1410 -- 1411 -- This MIB is used to monitor power usage of network 1412 -- devices 1413 -- 1414 -- ************************************************************* 1416 POWER-MONITOR-MIB DEFINITIONS ::= BEGIN 1418 IMPORTS 1419 MODULE-IDENTITY, 1420 OBJECT-TYPE, 1421 NOTIFICATION-TYPE, 1422 mib-2, 1423 Integer32, Counter64, TimeTicks 1424 FROM SNMPv2-SMI 1425 TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval 1426 FROM SNMPv2-TC 1427 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP 1428 FROM SNMPv2-CONF 1429 OwnerString 1430 FROM RMON-MIB; 1432 powerMonitorMIB MODULE-IDENTITY 1433 LAST-UPDATED "201107080000Z" -- 8 July 2011 1434 ORGANIZATION "IETF EMAN Working Group" 1435 CONTACT-INFO 1436 "WG charter: 1437 http://datatracker.ietf.org/wg/eman/charter/ 1439 Mailing Lists: 1440 General Discussion: eman@ietf.org 1442 To Subscribe: 1443 https://www.ietf.org/mailman/listinfo/eman 1445 Archive: 1446 http://www.ietf.org/mail-archive/web/eman 1448 Editors: 1449 Mouli Chandramouli 1450 Cisco Systems, Inc. 1451 Sarjapur Outer Ring Road 1452 Bangalore, 1453 IN 1454 Phone: +91 80 4426 3947 1455 Email: moulchan@cisco.com 1457 Brad Schoening 1458 44 Rivers Edge Drive 1459 Little Silver, NJ 07739 1460 US 1461 Email: brad@bradschoening.com 1463 Juergen Quittek 1464 NEC Europe Ltd. 1465 NEC Laboratories Europe 1466 Network Research Division 1467 Kurfuersten-Anlage 36 1468 Heidelberg 69115 1469 DE 1470 Phone: +49 6221 4342-115 1471 Email: quittek@neclab.eu 1473 Thomas Dietz 1474 NEC Europe Ltd. 1475 NEC Laboratories Europe 1476 Network Research Division 1477 Kurfuersten-Anlage 36 1478 69115 Heidelberg 1479 DE 1480 Phone: +49 6221 4342-128 1481 Email: Thomas.Dietz@nw.neclab.eu 1483 Benoit Claise 1484 Cisco Systems, Inc. 1485 De Kleetlaan 6a b1 1486 Degem 1831 1487 Belgium 1488 Phone: +32 2 704 5622 1489 Email: bclaise@cisco.com" 1491 DESCRIPTION 1492 "This MIB is used to monitor power and energy in 1493 devices." 1494 REVISION 1495 "201107080000Z" -- 8 July 2011 1496 DESCRIPTION 1497 "Initial version, published as RFC XXXX." 1499 ::= { mib-2 xxx } 1501 powerMonitorMIBNotifs OBJECT IDENTIFIER 1502 ::= { powerMonitorMIB 0 } 1504 powerMonitorMIBObjects OBJECT IDENTIFIER 1505 ::= { powerMonitorMIB 1 } 1507 powerMonitorMIBConform OBJECT IDENTIFIER 1508 ::= { powerMonitorMIB 2 } 1510 -- Textual Conventions 1512 PowerStateSet ::= TEXTUAL-CONVENTION 1513 STATUS current 1514 DESCRIPTION 1515 "PowerStateSet is a TC that describes the Power State 1516 Set a Power Monitor supports. IANA has created a 1517 registry of Power State Sets supported by a Power 1518 Monitor entity and IANA shall administer the list of 1519 Power State Sets. 1521 One byte is used to represent the Power State Set. 1523 field octets contents range 1524 ----- ------ -------- ----- 1525 1 1 Power State Set 1..255 1527 Note: 1528 the value of Power State Set in network byte order 1530 1 in the first byte indicates IEEE1621 Power State Set 1531 2 in the first byte indicates DMTF Power State Set 1532 3 in the first byte indicates EMAN Power State Set" 1534 REFERENCE 1535 "http://www.iana.org/assignments/eman 1536 RFC EDITOR NOTE: please change the previous URL 1537 if this is not the correct one after IANA assigned 1538 it." 1540 SYNTAX OCTET STRING (SIZE(1)) 1542 UnitMultiplier ::= TEXTUAL-CONVENTION 1543 STATUS current 1544 DESCRIPTION 1545 "The Unit Multiplier is an integer value that represents 1546 the IEEE 61850 Annex A units multiplier associated with 1547 the integer units used to measure the power or energy. 1549 For example, when used with pmPowerUnitMultiplier, -3 1550 represents 10^-3 or milliwatts." 1551 REFERENCE 1552 "The International System of Units (SI), 1553 National Institute of Standards and Technology, 1554 Spec. Publ. 330, August 1991." 1555 SYNTAX INTEGER { 1556 yocto(-24), -- 10^-24 1557 zepto(-21), -- 10^-21 1558 atto(-18), -- 10^-18 1559 femto(-15), -- 10^-15 1560 pico(-12), -- 10^-12 1561 nano(-9), -- 10^-9 1562 micro(-6), -- 10^-6 1563 milli(-3), -- 10^-3 1564 units(0), -- 10^0 1565 kilo(3), -- 10^3 1566 mega(6), -- 10^6 1567 giga(9), -- 10^9 1568 tera(12), -- 10^12 1569 peta(15), -- 10^15 1570 exa(18), -- 10^18 1571 zetta(21), -- 10^21 1572 yotta(24) -- 10^24 1573 } 1575 -- Objects 1577 pmPowerTable OBJECT-TYPE 1578 SYNTAX SEQUENCE OF PmPowerEntry 1579 MAX-ACCESS not-accessible 1580 STATUS current 1581 DESCRIPTION 1582 "This table lists Power Monitors." 1583 ::= { powerMonitorMIBObjects 1 } 1585 pmPowerEntry OBJECT-TYPE 1586 SYNTAX PmPowerEntry 1587 MAX-ACCESS not-accessible 1588 STATUS current 1589 DESCRIPTION 1590 "An entry describes the power usage of a Power Monitor." 1592 INDEX { pmPowerIndex, pmPowerStateSetIndex} 1593 ::= { pmPowerTable 1 } 1595 PmPowerEntry ::= SEQUENCE { 1596 pmPowerIndex Integer32, 1597 pmPowerStateSetIndex PowerStateSet, 1598 pmPower Integer32, 1599 pmPowerNameplate Integer32, 1600 pmPowerUnitMultiplier UnitMultiplier, 1601 pmPowerAccuracy Integer32, 1602 pmPowerMeasurementCaliber INTEGER, 1603 pmPowerCurrentType INTEGER, 1604 pmPowerOrigin INTEGER, 1605 pmPowerAdminState Integer32, 1606 pmPowerOperState Integer32, 1607 pmPowerStateEnterReason OwnerString 1608 } 1610 pmPowerIndex OBJECT-TYPE 1611 SYNTAX Integer32 (0..2147483647) 1612 MAX-ACCESS not-accessible 1613 STATUS current 1614 DESCRIPTION 1615 "A unique value, for each Power Monitor. 1616 If an implementation of the ENERGY-AWARE-MIB module is 1617 available in the local SNMP context, then the same index 1618 as the one in the ENERGY-AWARE-MIB MUST be assigned for 1619 the identical Power Monitor. In this case, entities 1620 without an assigned value for pmIndex cannot be indexed 1621 by the pmPowerStateTable. 1623 If there is no implementation of the ENERGY-AWARE-MIB 1624 module but one of the ENTITY MIB module is available in 1625 the local SNMP context, then the same index of an entity 1626 MUST be chosen as assigned to the entity by object 1627 entPhysicalIndex in the ENTITY MIB module. In this case, 1628 entities without an assigned value for entPhysicalIndex 1629 cannot be indexed by the pmPowerStateTable. 1631 If neither the ENERGY-AWARE-MIB module nor of the ENTITY 1632 MIB module are available in the local SNMP context, then 1633 this MIB module may choose identity values from a further 1634 MIB module providing entity identities. In this case the 1635 value for each pmPowerIndex must remain constant at least 1636 from one re-initialization of the entity's network 1637 management system to the next re-initialization. 1639 In case that no other MIB modules have been chosen for 1640 providing entity identities, Power States can be reported 1641 exclusively for the local device on which this table is 1642 instantiated. Then this table will have a single entry 1643 only and an index value of 0 MUST be used." 1645 ::= { pmPowerEntry 1 } 1647 pmPowerStateSetIndex OBJECT-TYPE 1648 SYNTAX PowerStateSet 1649 MAX-ACCESS not-accessible 1650 STATUS current 1651 DESCRIPTION 1652 "This object indicates the Power State Set supported by 1653 the Power Monitor. The list of Power State Sets and 1654 their numbering are administered by IANA" 1655 ::= { pmPowerEntry 2 } 1657 pmPower OBJECT-TYPE 1658 SYNTAX Integer32 1659 UNITS "Watts" 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "This object indicates the 'instantaneous' RMS 1664 consumption for the Power Monitor. This value is 1665 specified in SI units of watts with the magnitude of 1666 watts (milliwatts, kilowatts, etc.) indicated separately 1667 in pmPowerUnitMultiplier. The accuracy of the measurement 1668 is specfied in pmPowerAccuracy. The direction of power 1669 flow is indicated by the sign on pmPower. If the Power 1670 Monitor is consuming power, the pmPower value will be 1671 positive. If the Power Monitor is producing power, the 1672 pmPower value will be negative. 1674 The pmPower MUST be less than or equal to the maximum 1675 power that can be consumed at the power state specified 1676 by pmPowerState. 1678 The pmPowerMeasurementCaliber object specifies how the 1679 usage value reported by pmPower was obtained. The pmPower 1680 value must report 0 if the pmPowerMeasurementCaliber is 1681 'unavailable'. For devices that can not measure or 1682 report power, this option can be used." 1683 ::= { pmPowerEntry 3 } 1685 pmPowerNameplate OBJECT-TYPE 1686 SYNTAX Integer32 1687 UNITS "Watts" 1688 MAX-ACCESS read-only 1689 STATUS current 1690 DESCRIPTION 1691 "This object indicates the rated maximum consumption for 1692 the fully populated Power Monitor. The nameplate power 1693 requirements are the maximum power numbers and, in almost 1694 all cases, are well above the expected operational 1695 consumption. The pmPowerNameplate is widely used for 1696 power provisioning. This value is specified in either 1697 units of watts or voltage and current. The units are 1698 therefore SI watts or equivalent Volt-Amperes with the 1699 magnitude (milliwatts, kilowatts, etc.) indicated 1700 separately in pmPowerUnitMultiplier." 1701 ::= { pmPowerEntry 4 } 1703 pmPowerUnitMultiplier OBJECT-TYPE 1704 SYNTAX UnitMultiplier 1705 MAX-ACCESS read-only 1706 STATUS current 1707 DESCRIPTION 1708 "The magnitude of watts for the usage value in pmPower 1709 and pmPowerNameplate." 1710 ::= { pmPowerEntry 5 } 1712 pmPowerAccuracy OBJECT-TYPE 1713 SYNTAX Integer32 (0..10000) 1714 UNITS "hundredths of percent" 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "This object indicates a percentage value, in 100ths of a 1719 percent, representing the assumed accuracy of the usage 1720 reported by pmPower. For example: The value 1010 means 1721 the reported usage is accurate to +/- 10.1 percent. This 1722 value is zero if the accuracy is unknown or not 1723 applicable based upon the measurement method. 1725 ANSI and IEC define the following accuracy classes for 1726 power measurement: 1727 IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. 1728 ANSI C12.20 class 0.2, 0.5" 1729 ::= { pmPowerEntry 6 } 1731 pmPowerMeasurementCaliber OBJECT-TYPE 1732 SYNTAX INTEGER { 1733 unavailable(1) , 1734 unknown(2), 1735 actual(3) , 1736 estimated(4), 1737 presumed(5) } 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "This object specifies how the usage value reported by 1742 pmPower was obtained: 1744 - unavailable(1): Indicates that the usage is not 1745 available. In such a case, the pmPower value must be 0 1746 For devices that can not measure or report power this 1747 option can be used. 1749 - unknown(2): Indicates that the way the usage was 1750 determined is unknown. In some cases, entities report 1751 aggregate power on behalf of another device. In such 1752 cases it is not known whether the usage reported is 1753 actual(2), estimated(3) or presumed (4). 1755 - actual(3): Indicates that the reported usage was 1756 measured by the entity through some hardware or direct 1757 physical means. The usage data reported is not presumed 1758 (4) or estimated (3) but the real apparent current energy 1759 consumption rate. 1761 - estimated(4): Indicates that the usage was not 1762 determined by physical measurement. The value is a 1763 derivation based upon the device type, state, and/or 1764 current utilization using some algorithm or heuristic. It 1765 is presumed that the entity's state and current 1766 configuration were used to compute the value. 1768 - presumed(5): Indicates that the usage was not 1769 determined by physical measurement, algorithm or 1770 derivation. The usage was reported based upon external 1771 tables, specifications, and/or model information. For 1772 example, a PC Model X draws 200W, while a PC Model Y 1773 draws 210W" 1775 ::= { pmPowerEntry 7 } 1777 pmPowerCurrentType OBJECT-TYPE 1778 SYNTAX INTEGER { 1779 ac(1), 1780 dc(2), 1781 unknown(3) 1782 } 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "This object indicates whether the pmUsage for the Power 1787 Monitor reports alternative current AC(1), direct current 1788 DC(2), or that the current type is unknown(3)." 1789 ::= { pmPowerEntry 8 } 1791 pmPowerOrigin OBJECT-TYPE 1792 SYNTAX INTEGER { 1793 self (1), 1794 remote (2) 1795 } 1796 MAX-ACCESS read-only 1797 STATUS current 1798 DESCRIPTION 1799 "This object indicates the source of power measurement 1800 and can be useful when modeling the power usage of 1801 attached devices. The power measurement can be performed 1802 by the entity itself or the power measurement of the 1803 entity can be reported by another trusted entity using a 1804 protocol extension. A value of self(1) indicates the 1805 measurement is performed by the entity, whereas remote(2) 1806 indicates that the measurement was performed by another 1807 entity." 1808 ::= { pmPowerEntry 9 } 1810 pmPowerAdminState OBJECT-TYPE 1811 SYNTAX Integer32 (1..65535) 1812 MAX-ACCESS read-write 1813 STATUS current 1814 DESCRIPTION 1815 "This object specifies the desired Power State for the 1816 Power Monitor, in the context of the Power State Set 1817 specified by pmPowerStateSetIndex in this table. 1818 Possible values of pmPowerAdminState are registered at 1819 IANA, per Power State Set. A current list of 1820 assignments can be found at 1821 1822 RFC-EDITOR: please check the location after IANA" 1824 ::= { pmPowerEntry 10 } 1826 pmPowerOperState OBJECT-TYPE 1827 SYNTAX Integer32 (1..65535) 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "This object specifies the current operational Power 1832 State for the Power Monitor, in the context of the Power 1833 State Set specified by pmPowerStateSetIndex in this 1834 table. Possible values of pmPowerOperState are 1835 registered at IANA, per Power State Set. A current list 1836 of assignments can be found at 1837 1838 RFC-EDITOR: please check the list" 1839 ::= { pmPowerEntry 11 } 1841 pmPowerStateEnterReason OBJECT-TYPE 1842 SYNTAX OwnerString 1843 MAX-ACCESS read-create 1844 STATUS current 1845 DESCRIPTION 1846 "This string object describes the reason for the 1847 pmPowerAdminState 1848 transition Alternatively, this string may contain with 1849 the entity that configured this Power Monitor to this 1850 Power State." 1851 DEFVAL { "" } 1852 ::= { pmPowerEntry 12 } 1854 pmPowerStateTable OBJECT-TYPE 1855 SYNTAX SEQUENCE OF PmPowerStateEntry 1856 MAX-ACCESS not-accessible 1857 STATUS current 1858 DESCRIPTION 1859 "This table enumerates the maximum power usage, in watts, 1860 for every single supported Power State of each Power 1861 Monitor. 1863 This table has an expansion-dependent relationship on the 1864 pmPowerTable, containing rows describing each Power State 1865 for the corresponding Power Monitor. For every Power 1866 Monitor in the pmPowerTable, there is a corresponding 1867 entry in this table." 1868 ::= { powerMonitorMIBObjects 2 } 1870 pmPowerStateEntry OBJECT-TYPE 1871 SYNTAX PmPowerStateEntry 1872 MAX-ACCESS not-accessible 1873 STATUS current 1874 DESCRIPTION 1875 "A pmPowerStateEntry extends a corresponding 1876 pmPowerEntry. This entry displays max usage values at 1877 every single possible Power State supported by the Power 1878 Monitor. 1879 For example, given the values of a Power Monitor 1880 corresponding to a maximum usage of 11W at the 1881 state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High): 1883 State MaxUsage Units 1884 1 (mechoff 0 W 1885 2 (softoff) 0 W 1886 3 (hibernate) 0 W 1887 4 (sleep) 0 W 1888 5 (standby) 0 W 1889 6 (ready) 8 W 1890 7 (lowMinus) 8 W 1891 8 (low) 11 W 1892 9 (medimMinus) 11 W 1893 10 (medium) 11 W 1894 11 (highMinus) 11 W 1895 12 (high) 11 W 1897 Furthermore, this table extends to return the total time 1898 in each Power State, along with the number of times a 1899 particular Power State was entered." 1901 INDEX { 1902 pmPowerIndex, 1903 pmPowerStateSetIndex, 1904 pmPowerStateIndex 1906 } 1907 ::= { pmPowerStateTable 1 } 1909 PmPowerStateEntry ::= SEQUENCE { 1910 pmPowerStateIndex Integer32, 1911 pmPowerStateMaxPower Integer32, 1912 pmPowerStatePowerUnitMultiplier UnitMultiplier, 1913 pmPowerStateTotalTime TimeTicks, 1914 pmPowerStateEnterCount Counter64 1915 } 1917 pmPowerStateIndex OBJECT-TYPE 1918 SYNTAX Integer32 (1..65535) 1919 MAX-ACCESS not-accessible 1920 STATUS current 1921 DESCRIPTION 1922 "This object specifies the Power State for the Power 1923 Monitor, in the context of the Power State Set specified 1924 by pmPowerStateSetIndex in this table. 1926 This object specifies the index of the Power State of 1927 the Power Monitor within a Power State Set. The 1928 semantics of the specific Power State can be obtained 1929 from the Power State Set definition." 1930 ::= { pmPowerStateEntry 1 } 1932 pmPowerStateMaxPower OBJECT-TYPE 1933 SYNTAX Integer32 1934 UNITS "Watts" 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "This object indicates the maximum power for the Power 1939 Monitor at the particular Power State. This value is 1940 specified in SI units of watts with the magnitude of the 1941 units (milliwatts, kilowatts, etc.) indicated separately 1942 in pmPowerStatePowerUnitMultiplier. If the maximum power 1943 is not known for a certain Power State, then the value is 1944 encoded as 0xFFFF. 1946 For Power States not enumerated, the value of 1947 pmPowerStateMaxPower might be interpolated by using the 1948 next highest supported Power State." 1949 ::= { pmPowerStateEntry 3 } 1951 pmPowerStatePowerUnitMultiplier OBJECT-TYPE 1952 SYNTAX UnitMultiplier 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The magnitude of watts for the usage value in 1957 pmPowerStateMaxPower." 1958 ::= { pmPowerStateEntry 4 } 1960 pmPowerStateTotalTime OBJECT-TYPE 1961 SYNTAX TimeTicks 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "This object indicates the total time in hundreds 1966 of seconds that the Power Monitor has been in this power 1967 state since the last reset, as specified in the 1968 sysUpTime." 1969 ::= { pmPowerStateEntry 5 } 1971 pmPowerStateEnterCount OBJECT-TYPE 1972 SYNTAX Counter64 1973 MAX-ACCESS read-only 1974 STATUS current 1975 DESCRIPTION 1976 "This object indicates how often the Power Monitor has 1977 entered this power state, since the last reset of the 1978 device as specified in the sysUpTime." 1979 ::= { pmPowerStateEntry 6 } 1981 pmEnergyParametersTable OBJECT-TYPE 1982 SYNTAX SEQUENCE OF PmEnergyParametersEntry 1983 MAX-ACCESS not-accessible 1984 STATUS current 1985 DESCRIPTION 1986 "This table is used to configure the parameters for Energy 1987 measurement collection in the table pmEnergyTable." 1988 ::= { powerMonitorMIBObjects 4 } 1990 pmEnergyParametersEntry OBJECT-TYPE 1991 SYNTAX PmEnergyParametersEntry 1992 MAX-ACCESS not-accessible 1993 STATUS current 1994 DESCRIPTION 1995 "An entry controls an energy measurement in 1996 pmEnergyTable." 1997 INDEX { pmPowerIndex } 1998 ::= { pmEnergyParametersTable 1 } 2000 PmEnergyParametersEntry ::= SEQUENCE { 2001 pmEnergyParametersIntervalLength TimeInterval, 2002 pmEnergyParametersIntervalNumber Integer32, 2003 pmEnergyParametersIntervalMode Integer32, 2004 pmEnergyParametersIntervalWindow TimeInterval, 2005 pmEnergyParametersSampleRate Integer32, 2006 pmEnergyParametersStatus RowStatus 2007 } 2009 pmEnergyParametersIntervalLength OBJECT-TYPE 2010 SYNTAX TimeInterval 2011 UNITS "Seconds" 2012 MAX-ACCESS read-create 2013 STATUS current 2014 DESCRIPTION 2015 "This object indicates the length of time in seconds over 2016 which to compute the average pmEnergyIntervalEnergyUsed 2017 measurement in the pmEnergyTable table. The computation 2018 is based on the Power Monitor's internal sampling rate of 2019 power consumed or produced by the Power Monitor. The 2020 sampling rate is the rate at which the power monitor can 2021 read the power usage and may differ based on device 2022 capabilities. The average energy consumption is then 2023 computed over the length of the interval." 2024 DEFVAL { 900 } 2025 ::= { pmEnergyParametersEntry 1 } 2027 pmEnergyParametersIntervalNumber OBJECT-TYPE 2028 SYNTAX Integer32 2029 MAX-ACCESS read-create 2030 STATUS current 2031 DESCRIPTION 2032 "The number of intervals maintained in the pmEnergyTable. 2033 Each interval is characterized by a specific 2034 pmEnergyIntervalStartTime, used as an index to the table 2035 pmEnergyTable . Whenever the maximum number of entries is 2036 reached, the measurement over the new interval replaces 2037 the oldest measurement , except if the oldest measurement 2038 were to be the maximum pmEnergyIntervalMax, in which case 2039 the measurement the measurement over the next oldest 2040 interval is replaced." 2041 DEFVAL { 10 } 2042 ::= { pmEnergyParametersEntry 2 } 2044 pmEnergyParametersIntervalMode OBJECT-TYPE 2045 SYNTAX INTEGER { 2046 period(1), 2047 sliding(2), 2048 total(3) 2049 } 2050 MAX-ACCESS read-create 2051 STATUS current 2052 DESCRIPTION 2053 "A control object to define the mode of interval calculation 2054 for the computation of the average 2055 pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable 2056 table. 2057 A mode of period(1) specifies non-overlapping periodic 2058 measurements. 2060 A mode of sliding(2) specifies overlapping sliding windows 2061 where the interval between the start of one interval and 2062 the next is defined in pmEnergyParametersIntervalWindow. 2064 A mode of total(3) specifies non-periodic measurement. In 2065 this mode only one interval is used as this is a 2066 continuous measurement since the last reset. The value of 2067 pmEnergyParametersIntervalNumber should be (1) one and 2068 pmEnergyParametersIntervalLength is ignored. " 2069 ::= { pmEnergyParametersEntry 3 } 2071 pmEnergyParametersIntervalWindow OBJECT-TYPE 2072 SYNTAX TimeInterval 2073 UNITS "Seconds" 2074 MAX-ACCESS read-create 2075 STATUS current 2076 DESCRIPTION 2077 "The length of the duration window between the starting 2078 time of one sliding window and the next starting time in 2079 seconds, in order to compute the average 2080 pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable 2081 table This is valid only when the 2082 pmEnergyParametersIntervalMode is sliding(2). The 2083 pmEnergyParametersIntervalWindow value should be a multiple 2084 of pmEnergyParametersSampleRate." 2085 ::= { pmEnergyParametersEntry 4 } 2087 pmEnergyParametersSampleRate OBJECT-TYPE 2088 SYNTAX Integer32 2089 UNITS "Milliseconds" 2090 MAX-ACCESS read-create 2091 STATUS current 2092 DESCRIPTION 2093 "The sampling rate, in milliseconds, at which the Power 2094 Monitor should poll power usage in order to compute the 2095 average pmEnergyIntervalEnergyUsed measurement in the 2096 table pmEnergyTable. The Power Monitor should initially 2097 set this sampling rate to a reasonable value, i.e., a 2098 compromise between intervals that will provide good 2099 accuracy by not being too long, but not so short that 2100 they affect the Power Monitor performance by requesting 2101 continuous polling. If the sampling rate is unknown, the 2102 value 0 is reported. The sampling rate should be selected 2103 so that pmEnergyParametersIntervalWindow is a multiple of 2104 pmEnergyParametersSampleRate." 2105 DEFVAL { 1000 } 2106 ::= { pmEnergyParametersEntry 5 } 2108 pmEnergyParametersStatus OBJECT-TYPE 2109 SYNTAX RowStatus 2110 MAX-ACCESS read-create 2111 STATUS current 2112 DESCRIPTION 2113 "The status of this row. The pmEnergyParametersStatus is 2114 used to start or stop energy usage logging. An entry 2115 status may not be active(1) unless all objects in the 2116 entry have an appropriate value. If this object is not 2117 equal to active(1), all associated usage-data logged into 2118 the pmEnergyTable will be deleted. The data can be 2119 destroyed by setting up the pmEnergyParametersStatus to 2120 destroy(2)." 2121 ::= {pmEnergyParametersEntry 6 } 2123 pmEnergyTable OBJECT-TYPE 2124 SYNTAX SEQUENCE OF PmEnergyIntervalEntry 2125 MAX-ACCESS not-accessible 2126 STATUS current 2127 DESCRIPTION 2128 "This table lists Power Monitor energy measurements. 2129 Entries in this table are only created if the 2130 corresponding value of object pmPowerMeasurementCaliber 2131 is active(2), i.e., if the power is actually metered." 2132 ::= { powerMonitorMIBObjects 5 } 2134 pmEnergyIntervalEntry OBJECT-TYPE 2135 SYNTAX PmEnergyIntervalEntry 2136 MAX-ACCESS not-accessible 2137 STATUS current 2138 DESCRIPTION 2139 "An entry describing energy measurements." 2140 INDEX { pmPowerIndex, pmEnergyParametersIntervalMode, 2141 pmEnergyIntervalStartTime } 2142 ::= { pmEnergyTable 1 } 2144 PmEnergyIntervalEntry ::= SEQUENCE { 2145 pmEnergyIntervalStartTime TimeTicks, 2146 pmEnergyIntervalEnergyUsed Integer32, 2147 pmEnergyIntervalEnergyUnitMultiplier UnitMultiplier, 2148 pmEnergyIntervalMax Integer32, 2149 pmEnergyIntervalDiscontinuityTime TimeTicks 2150 } 2152 pmEnergyIntervalStartTime OBJECT-TYPE 2153 SYNTAX TimeTicks 2154 UNITS "hundredths of seconds" 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "The time (in hundredths of a second) since the 2159 network management portion of the system was last 2160 re-initialized, as specified in the sysUpTime [RFC3418]. 2161 This object is useful for reference of interval periods 2162 for which the energy is measured." 2163 ::= { pmEnergyIntervalEntry 1 } 2165 pmEnergyIntervalEnergyUsed OBJECT-TYPE 2166 SYNTAX Integer32 2167 UNITS "Watt-hours" 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This object indicates the energy used in units of watt- 2172 hours for the Power Monitor over the defined interval. 2173 This value is specified in the common billing units of 2174 watt-hours with the magnitude of watt-hours (kW-Hr, MW- 2175 Hr, etc.) indicated separately in 2176 pmEnergyIntervalEnergyUnitMultiplier." 2177 ::= { pmEnergyIntervalEntry 2 } 2179 pmEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE 2180 SYNTAX UnitMultiplier 2181 MAX-ACCESS read-only 2182 STATUS current 2183 DESCRIPTION 2184 "This object is the magnitude of watt-hours for the 2185 energy field in pmEnergyIntervalEnergyUsed." 2186 ::= { pmEnergyIntervalEntry 3 } 2188 pmEnergyIntervalMax OBJECT-TYPE 2189 SYNTAX Integer32 2190 UNITS "Watt-hours" 2191 MAX-ACCESS read-only 2192 STATUS current 2193 DESCRIPTION 2194 "This object is the maximum energy ever observed in 2195 pmEnergyIntervalEnergyUsed since the monitoring started. 2196 This value is specified in the common billing units of 2197 watt-hours with the magnitude of watt-hours (kW-Hr, MW- 2198 Hr, etc.) indicated separately in 2199 pmEnergyIntervalEnergyUnits." 2200 ::= { pmEnergyIntervalEntry 4 } 2202 pmEnergyIntervalDiscontinuityTime OBJECT-TYPE 2203 SYNTAX TimeTicks 2204 MAX-ACCESS read-only 2205 STATUS current 2206 DESCRIPTION 2207 "The value of sysUpTime [RFC3418] on the most recent 2208 occasion at which any one or more of this entity's energy 2209 consumption counters suffered a discontinuity. If no such 2210 discontinuities have occurred since the last re- 2211 initialization of the local management subsystem, then 2212 this object contains a zero value." 2213 ::= { pmEnergyIntervalEntry 5 } 2215 -- Notifications 2217 pmPowerStateChange NOTIFICATION-TYPE 2218 OBJECTS {pmPowerAdminState, pmPowerOperState, 2219 pmPowerStateEnterReason} 2220 STATUS current 2221 DESCRIPTION 2222 "The SNMP entity generates the PmPowerStateChange when 2223 the value(s) of pmPowerAdminState or pmPowerOperState, 2224 in the context of the Power State Set, have changed for 2225 the Power Monitor represented by the pmPowerIndex." 2226 ::= { powerMonitorMIBNotifs 1 } 2228 -- Conformance 2230 powerMonitorMIBCompliances OBJECT IDENTIFIER 2231 ::= { powerMonitorMIB 3 } 2233 powerMonitorMIBGroups OBJECT IDENTIFIER 2234 ::= { powerMonitorMIB 4 } 2236 powerMonitorMIBFullCompliance MODULE-COMPLIANCE 2237 STATUS current 2238 DESCRIPTION 2239 "When this MIB is implemented with support for 2240 read-create, then such an implementation can 2241 claim full compliance. Such devices can then 2242 be both monitored and configured with this MIB." 2243 MODULE -- this module 2244 MANDATORY-GROUPS { 2245 powerMonitorMIBTableGroup, 2246 powerMonitorMIBStateTableGroup, 2247 powerMonitorMIBEnergyTableGroup, 2248 powerMonitorMIBEnergyParametersTableGroup, 2249 powerMonitorMIBNotifGroup 2250 } 2251 ::= { powerMonitorMIBCompliances 1 } 2253 powerMonitorMIBReadOnlyCompliance MODULE-COMPLIANCE 2254 STATUS current 2255 DESCRIPTION 2256 "When this MIB is implemented without support for 2257 read-create (i.e. in read-only mode), then such an 2258 implementation can claim read-only compliance. Such a 2259 device can then be monitored but can not be configured 2260 with this MIB." 2261 MODULE -- this module 2262 MANDATORY-GROUPS { 2263 powerMonitorMIBTableGroup, 2264 powerMonitorMIBStateTableGroup, 2265 powerMonitorMIBNotifGroup 2266 } 2268 OBJECT pmPowerOperState 2269 MIN-ACCESS read-only 2270 DESCRIPTION 2271 "Write access is not required." 2272 ::= { powerMonitorMIBCompliances 2 } 2274 -- Units of Conformance 2276 powerMonitorMIBTableGroup OBJECT-GROUP 2277 OBJECTS { 2278 pmPower, 2279 pmPowerNameplate, 2280 pmPowerUnitMultiplier, 2281 pmPowerAccuracy, 2282 pmPowerMeasurementCaliber, 2283 pmPowerCurrentType, 2284 pmPowerOrigin, 2285 pmPowerAdminState, 2286 pmPowerOperState, 2287 pmPowerStateEnterReason 2288 } 2289 STATUS current 2290 DESCRIPTION 2291 "This group contains the collection of all the objects 2292 related to the PowerMonitor." 2293 ::= { powerMonitorMIBGroups 1 } 2295 powerMonitorMIBStateTableGroup OBJECT-GROUP 2296 OBJECTS { 2297 pmPowerStateMaxPower, 2298 pmPowerStatePowerUnitMultiplier, 2299 pmPowerStateTotalTime, 2300 pmPowerStateEnterCount 2302 } 2303 STATUS current 2304 DESCRIPTION 2305 "This group contains the collection of all the 2306 objects related to the Power State." 2307 ::= { powerMonitorMIBGroups 2 } 2309 powerMonitorMIBEnergyParametersTableGroup OBJECT-GROUP 2310 OBJECTS { 2311 pmEnergyParametersIntervalLength, 2312 pmEnergyParametersIntervalNumber, 2313 pmEnergyParametersIntervalMode, 2314 pmEnergyParametersIntervalWindow, 2315 pmEnergyParametersSampleRate, 2316 pmEnergyParametersStatus 2317 } 2318 STATUS current 2319 DESCRIPTION 2320 "This group contains the collection of all the objects 2321 related to the configuration of the Energy Table." 2322 ::= { powerMonitorMIBGroups 3 } 2324 powerMonitorMIBEnergyTableGroup OBJECT-GROUP 2325 OBJECTS { 2326 -- Note that object 2327 -- pmEnergyIntervalStartTime is not 2328 -- included since it is not-accessible 2330 pmEnergyIntervalEnergyUsed, 2331 pmEnergyIntervalEnergyUnitMultiplier, 2332 pmEnergyIntervalMax, 2333 pmEnergyIntervalDiscontinuityTime 2334 } 2335 STATUS current 2336 DESCRIPTION 2337 "This group contains the collection of all the objects 2338 related to the Energy Table." 2339 ::= { powerMonitorMIBGroups 4 } 2341 powerMonitorMIBNotifGroup NOTIFICATION-GROUP 2342 NOTIFICATIONS { 2343 pmPowerStateChange 2344 } 2345 STATUS current 2346 DESCRIPTION 2347 "This group contains the notifications for the power and 2348 energy monitoring MIB Module." 2349 ::= { powerMonitorMIBGroups 5 } 2351 END 2353 -- ************************************************************ 2354 -- 2355 -- This MIB module is used to monitor power quality of networked 2356 -- devices with measurements. 2357 -- 2358 -- This MIB module is an extension of powerMonitorMIB module. 2359 -- 2360 -- ************************************************************* 2362 POWER-QUALITY-MIB DEFINITIONS ::= BEGIN 2364 IMPORTS 2365 MODULE-IDENTITY, 2366 OBJECT-TYPE, 2367 mib-2, 2368 Integer32 2369 FROM SNMPv2-SMI 2370 MODULE-COMPLIANCE, 2371 OBJECT-GROUP 2372 FROM SNMPv2-CONF 2373 UnitMultiplier, pmPowerIndex 2374 FROM POWER-MONITOR-MIB 2375 OwnerString 2376 FROM RMON-MIB; 2378 powerQualityMIB MODULE-IDENTITY 2380 LAST-UPDATED "201107080000Z" -- 8 July 2011 2381 ORGANIZATION "IETF EMAN Working Group" 2382 CONTACT-INFO 2383 "WG charter: 2384 http://datatracker.ietf.org/wg/eman/charter/ 2386 Mailing Lists: 2387 General Discussion: eman@ietf.org 2389 To Subscribe: 2390 https://www.ietf.org/mailman/listinfo/eman 2391 Archive: 2392 http://www.ietf.org/mail-archive/web/eman 2394 Editors: 2396 Mouli Chandramouli 2397 Cisco Systems, Inc. 2398 Sarjapur Outer Ring Road 2399 Bangalore, 2400 IN 2401 Phone: +91 80 4426 3947 2402 Email: moulchan@cisco.com 2404 Brad Schoening 2405 44 Rivers Edge Drive 2406 Little Silver, NJ 07739 2407 US 2408 Email: brad@bradschoening.com 2410 Juergen Quittek 2411 NEC Europe Ltd. 2412 NEC Laboratories Europe 2413 Network Research Division 2414 Kurfuersten-Anlage 36 2415 Heidelberg 69115 2416 DE 2417 Phone: +49 6221 4342-115 2418 Email: quittek@neclab.eu 2420 Thomas Dietz 2421 NEC Europe Ltd. 2422 NEC Laboratories Europe 2423 Network Research Division 2424 Kurfuersten-Anlage 36 2425 69115 Heidelberg 2426 DE 2427 Phone: +49 6221 4342-128 2428 Email: Thomas.Dietz@nw.neclab.eu 2430 Benoit Claise 2431 Cisco Systems, Inc. 2432 De Kleetlaan 6a b1 2433 Degem 1831 2434 Belgium 2435 Phone: +32 2 704 5622 2436 Email: bclaise@cisco.com" 2438 DESCRIPTION 2439 "This MIB is used to report AC power quality in 2440 devices. The table is a sparse augmentation of the 2441 pmPowerTable table from the powerMonitorMIB module. 2442 Both three-phase and single-phase power 2443 configurations are supported." 2444 REVISION 2446 "201107080000Z" -- 8 July 2011 2448 DESCRIPTION 2449 "Initial version, published as RFC YYY." 2451 ::= { mib-2 yyy } 2453 powerQualityMIBConform OBJECT IDENTIFIER 2454 ::= { powerQualityMIB 0 } 2456 powerQualityMIBObjects OBJECT IDENTIFIER 2457 ::= { powerQualityMIB 1 } 2459 -- Objects 2461 pmACPwrQualityTable OBJECT-TYPE 2462 SYNTAX SEQUENCE OF PmACPwrQualityEntry 2463 MAX-ACCESS not-accessible 2464 STATUS current 2465 DESCRIPTION 2466 "This table defines power quality measurements for 2467 supported pmPowerIndex entities. It is a sparse 2468 extension of the pmPowerTable." 2469 ::= { powerQualityMIBObjects 1 } 2471 pmACPwrQualityEntry OBJECT-TYPE 2472 SYNTAX PmACPwrQualityEntry 2473 MAX-ACCESS not-accessible 2474 STATUS current 2475 DESCRIPTION 2476 "This is a sparse extension of the pmPowerTable with 2477 entries for power quality measurements or 2478 configuration. Each measured value corresponds to an 2479 attribute in IEC 61850-7-4 for non-phase measurements 2480 within the object MMUX." 2481 INDEX { pmPowerIndex } 2482 ::= { pmACPwrQualityTable 1 } 2484 PmACPwrQualityEntry ::= SEQUENCE { 2485 pmACPwrQualityConfiguration INTEGER, 2486 pmACPwrQualityAvgVoltage Integer32, 2487 pmACPwrQualityAvgCurrent Integer32, 2488 pmACPwrQualityFrequency Integer32, 2489 pmACPwrQualityPowerUnitMultiplier UnitMultiplier, 2490 pmACPwrQualityPowerAccuracy Integer32, 2491 pmACPwrQualityTotalActivePower Integer32, 2492 pmACPwrQualityTotalReactivePower Integer32, 2493 pmACPwrQualityTotalApparentPower Integer32, 2494 pmACPwrQualityTotalPowerFactor Integer32, 2495 pmACPwrQualityThdAmpheres Integer32, 2496 pmACPwrQualityThdVoltage Integer32 2497 } 2499 pmACPwrQualityConfiguration OBJECT-TYPE 2500 SYNTAX INTEGER { 2501 sngl(1), 2502 del(2), 2503 wye(3) 2504 } 2505 MAX-ACCESS read-only 2506 STATUS current 2507 DESCRIPTION 2508 "Configuration describes the physical configurations 2509 of the power supply lines: 2511 * alternating current, single phase (SNGL) 2512 * alternating current, three phase delta (DEL) 2513 * alternating current, three phase Y (WYE) 2515 Three-phase configurations can be either connected in 2516 a triangular delta (DEL) or star Y (WYE) system. WYE 2517 systems have a shared neutral voltage, while DEL 2518 systems do not. Each phase is offset 120 degrees to 2519 each other." 2520 ::= { pmACPwrQualityEntry 1 } 2522 pmACPwrQualityAvgVoltage OBJECT-TYPE 2523 SYNTAX Integer32 2524 UNITS "0.1 Volt AC" 2525 MAX-ACCESS read-only 2526 STATUS current 2527 DESCRIPTION 2528 "A measured value for average 'instantaneous' RMS line 2529 voltage. For a 3-phase system, this is the average 2530 voltage (V1+V2+V3)/3. IEC 61850-7-4 measured value 2531 attribute 'Vol'" 2533 ::= { pmACPwrQualityEntry 2 } 2535 pmACPwrQualityAvgCurrent OBJECT-TYPE 2536 SYNTAX Integer32 2537 UNITS "Ampheres" 2538 MAX-ACCESS read-only 2539 STATUS current 2540 DESCRIPTION 2541 "A measured value of the current per phase. IEC 61850- 2542 7-4 attribute 'Amp'" 2543 ::= { pmACPwrQualityEntry 3 } 2545 pmACPwrQualityFrequency OBJECT-TYPE 2546 SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz 2547 UNITS "hertz" 2548 MAX-ACCESS read-only 2549 STATUS current 2550 DESCRIPTION 2551 "A measured value for the basic frequency of the AC 2552 circuit. IEC 61850-7-4 attribute 'Hz'." 2553 ::= { pmACPwrQualityEntry 4 } 2555 pmACPwrQualityPowerUnitMultiplier OBJECT-TYPE 2556 SYNTAX UnitMultiplier 2557 MAX-ACCESS read-only 2558 STATUS current 2559 DESCRIPTION 2560 "The magnitude of watts for the usage value in 2561 pmACPwrQualityTotalActivePower, 2562 pmACPwrQualityTotalReactivePower 2563 and pmACPwrQualityTotalApparentPower measurements. For 2564 3-phase power systems, this will also include 2565 pmACPwrQualityPhaseActivePower, 2566 pmACPwrQualityPhaseReactivePower and 2567 pmACPwrQualityPhaseApparentPower" 2568 ::= { pmACPwrQualityEntry 5 } 2570 pmACPwrQualityPowerAccuracy OBJECT-TYPE 2571 SYNTAX Integer32 (0..10000) 2572 UNITS "hundredths of percent" 2573 MAX-ACCESS read-only 2574 STATUS current 2575 DESCRIPTION 2576 "This object indicates a percentage value, in 100ths of 2577 a percent, representing the presumed accuracy of 2578 active, reactive, and apparent power usage reporting. 2579 For example: 1010 means the reported usage is accurate 2580 to +/- 10.1 percent. This value is zero if the 2581 accuracy is unknown. 2583 ANSI and IEC define the following accuracy classes for 2584 power measurement: IEC 62053-22 & 60044-1 class 0.1, 2585 0.2, 0.5, 1 & 3. 2586 ANSI C12.20 class 0.2 & 0.5" 2587 ::= { pmACPwrQualityEntry 6 } 2589 pmACPwrQualityTotalActivePower OBJECT-TYPE 2590 SYNTAX Integer32 2591 UNITS "RMS watts" 2592 MAX-ACCESS read-only 2593 STATUS current 2594 DESCRIPTION 2595 "A measured value of the actual power delivered to or 2596 consumed by the load. IEC 61850-7-4 attribute 'TotW'." 2597 ::= { pmACPwrQualityEntry 7 } 2599 pmACPwrQualityTotalReactivePower OBJECT-TYPE 2600 SYNTAX Integer32 2601 UNITS "volt-amperes reactive" 2602 MAX-ACCESS read-only 2603 STATUS current 2604 DESCRIPTION 2605 "A mesured value of the reactive portion of the 2606 apparent power. IEC 61850-7-4 attribute 'TotVAr'." 2607 ::= { pmACPwrQualityEntry 8 } 2609 pmACPwrQualityTotalApparentPower OBJECT-TYPE 2610 SYNTAX Integer32 2611 UNITS "volt-amperes" 2612 MAX-ACCESS read-only 2613 STATUS current 2614 DESCRIPTION 2615 "A measured value of the voltage and current which 2616 determines the apparent power. The apparent power is 2617 the vector sum of real and reactive power. 2619 Note: watts and volt-ampheres are equivalent units and 2620 may be combined. IEC 61850-7-4 attribute 'TotVA'." 2621 ::= { pmACPwrQualityEntry 9 } 2623 pmACPwrQualityTotalPowerFactor OBJECT-TYPE 2624 SYNTAX Integer32 (-10000..10000) 2625 UNITS "hundredths of percent" 2626 MAX-ACCESS read-only 2627 STATUS current 2628 DESCRIPTION 2629 "A measured value ratio of the real power flowing to 2630 the load versus the apparent power. It is dimensionless 2631 and expressed here as a percentage value in 100ths of a 2632 percent. A power factor of 100% indicates there is no 2633 inductance load and thus no reactive power. Power 2634 Factor can be positive or negative, where the sign 2635 should be in lead/lag (IEEE) form. IEC 61850-7-4 2636 attribute 'TotPF'." 2637 ::= { pmACPwrQualityEntry 10 } 2639 pmACPwrQualityThdAmpheres OBJECT-TYPE 2640 SYNTAX Integer32 (0..10000) 2641 UNITS "hundredths of percent" 2642 MAX-ACCESS read-only 2643 STATUS current 2644 DESCRIPTION 2645 "A calculated value for the current total harmonic 2646 distortion (THD). Method of calculation is not 2647 specified. IEC 61850-7-4 attribute 'ThdAmp'." 2648 ::= { pmACPwrQualityEntry 11 } 2650 pmACPwrQualityThdVoltage OBJECT-TYPE 2651 SYNTAX Integer32 (0..10000) 2652 UNITS "hundredths of percent" 2653 MAX-ACCESS read-only 2654 STATUS current 2655 DESCRIPTION 2656 "A calculated value for the voltage total harmonic 2657 distortion (THD). Method of calculation is not 2658 specified. IEC 61850-7-4 attribute 'ThdVol'." 2659 ::= { pmACPwrQualityEntry 12 } 2661 pmACPwrQualityPhaseTable OBJECT-TYPE 2662 SYNTAX SEQUENCE OF PmACPwrQualityPhaseEntry 2663 MAX-ACCESS not-accessible 2664 STATUS current 2665 DESCRIPTION 2666 "This table describes 3-phase power quality 2667 measurements. It is a sparse extension of the 2668 pmACPwrQualityTable." 2669 ::= { powerQualityMIBObjects 2 } 2671 pmACPwrQualityPhaseEntry OBJECT-TYPE 2672 SYNTAX PmACPwrQualityPhaseEntry 2673 MAX-ACCESS not-accessible 2674 STATUS current 2675 DESCRIPTION 2676 "An entry describes common 3-phase power quality 2677 measurements. 2679 This optional table describes 3-phase power quality 2680 measurements, with three entries for each supported 2681 pmPowerIndex entity. Entities having single phase 2682 power shall not have any entities. 2684 This table describes attributes common to both WYE and 2685 DEL. Entities having single phase power shall not have 2686 any entries here. It is a sparse extension of the 2687 pmACPwrQualityTable. 2689 These attributes correspond to IEC 61850-7.4 MMXU phase 2690 measurements." 2691 INDEX { pmPowerIndex, pmPhaseIndex } 2692 ::= { pmACPwrQualityPhaseTable 1 } 2694 PmACPwrQualityPhaseEntry ::= SEQUENCE { 2695 pmPhaseIndex Integer32, 2696 pmACPwrQualityPhaseAvgCurrent Integer32, 2697 pmACPwrQualityPhaseActivePower Integer32, 2698 pmACPwrQualityPhaseReactivePower Integer32, 2699 pmACPwrQualityPhaseApparentPower Integer32, 2700 pmACPwrQualityPhasePowerFactor Integer32, 2701 pmACPwrQualityPhaseImpedance Integer32 2702 } 2704 pmPhaseIndex OBJECT-TYPE 2705 SYNTAX Integer32 (0..359) 2706 MAX-ACCESS not-accessible 2707 STATUS current 2708 DESCRIPTION 2709 "A phase angle typically corresponding to 0, 120, 240." 2710 ::= { pmACPwrQualityPhaseEntry 1 } 2712 pmACPwrQualityPhaseAvgCurrent OBJECT-TYPE 2713 SYNTAX Integer32 2714 UNITS "Ampheres" 2715 MAX-ACCESS read-only 2716 STATUS current 2717 DESCRIPTION 2718 "A measured value of the current per phase. IEC 61850- 2719 7-4 attribute 'A'" 2720 ::= { pmACPwrQualityPhaseEntry 2 } 2722 pmACPwrQualityPhaseActivePower OBJECT-TYPE 2723 SYNTAX Integer32 2724 UNITS "RMS watts" 2725 MAX-ACCESS read-only 2726 STATUS current 2727 DESCRIPTION 2728 "A measured value of the actual power delivered to or 2729 consumed by the load. IEC 61850-7-4 attribute 'W'" 2730 ::= { pmACPwrQualityPhaseEntry 3 } 2732 pmACPwrQualityPhaseReactivePower OBJECT-TYPE 2733 SYNTAX Integer32 2734 UNITS "volt-amperes reactive" 2735 MAX-ACCESS read-only 2736 STATUS current 2737 DESCRIPTION 2738 "A measured value of the reactive portion of the 2739 apparent power. IEC 61850-7-4 attribute 'VAr'" 2740 ::= { pmACPwrQualityPhaseEntry 4 } 2742 pmACPwrQualityPhaseApparentPower OBJECT-TYPE 2743 SYNTAX Integer32 2744 UNITS "volt-amperes" 2745 MAX-ACCESS read-only 2746 STATUS current 2747 DESCRIPTION 2748 "A measured value of the voltage and current determines 2749 the apparent power. Active plus reactive power equals 2750 the total apparent powwer. 2752 Note: Watts and volt-ampheres are equivalent units and 2753 may be combined. IEC 61850-7-4 attribute 'VA'." 2754 ::= { pmACPwrQualityPhaseEntry 5 } 2756 pmACPwrQualityPhasePowerFactor OBJECT-TYPE 2757 SYNTAX Integer32 (-10000..10000) 2758 UNITS "hundredths of percent" 2759 MAX-ACCESS read-only 2760 STATUS current 2761 DESCRIPTION 2762 "A measured value ratio of the real power flowing to 2763 the load versus the apparent power for this phase. IEC 2764 61850-7-4 attribute 'PF'. Power Factor can be positive 2765 or negative where the sign should be in lead/lag (IEEE) 2766 form." 2767 ::= { pmACPwrQualityPhaseEntry 6 } 2769 pmACPwrQualityPhaseImpedance OBJECT-TYPE 2770 SYNTAX Integer32 2771 UNITS "volt-amperes" 2772 MAX-ACCESS read-only 2773 STATUS current 2774 DESCRIPTION 2775 "A measured value of the impedance. IEC 61850-7-4 attribute 2776 'Z'." 2777 ::= { pmACPwrQualityPhaseEntry 7 } 2779 pmACPwrQualityDelPhaseTable OBJECT-TYPE 2780 SYNTAX SEQUENCE OF PmACPwrQualityDelPhaseEntry 2781 MAX-ACCESS not-accessible 2782 STATUS current 2783 DESCRIPTION 2784 "This table describes DEL configuration phase-to-phase 2785 power quality measurements. This is a sparse extension 2786 of the pmACPwrQualityPhaseTable." 2787 ::= { powerQualityMIBObjects 3 } 2789 pmACPwrQualityDelPhaseEntry OBJECT-TYPE 2790 SYNTAX PmACPwrQualityDelPhaseEntry 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "An entry describes quality attributes of a phase in a 2795 DEL 3-phase power system. Voltage measurements are 2796 provided both relative to each other and zero. 2798 Measured values are from IEC 61850-7-2 MMUX and THD from 2799 MHAI objects. 2801 For phase-to-phase measurements, the pmPhaseIndex is 2802 compared against the following phase at +120 degrees. 2803 Thus, the possible values are: 2805 pmPhaseIndex Next Phase Angle 2806 0 120 2807 120 240 2808 240 0 2809 " 2810 INDEX { pmPowerIndex, pmPhaseIndex} 2811 ::= { pmACPwrQualityDelPhaseTable 1} 2813 PmACPwrQualityDelPhaseEntry ::= SEQUENCE { 2814 pmACPwrQualityDelPhaseToNextPhaseVoltage Integer32, 2815 pmACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, 2816 pmACPwrQualityDelThdCurrent Integer32 2817 } 2819 pmACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE 2820 SYNTAX Integer32 2821 UNITS "0.1 Volt AC" 2822 MAX-ACCESS read-only 2823 STATUS current 2824 DESCRIPTION 2825 "A measured value of phase to next phase voltages, where 2826 the next phase is IEC 61850-7-4 attribute 'PPV'." 2827 ::= { pmACPwrQualityDelPhaseEntry 2 } 2829 pmACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE 2830 SYNTAX Integer32 (0..10000) 2831 UNITS "hundredths of percent" 2832 MAX-ACCESS read-only 2833 STATUS current 2834 DESCRIPTION 2835 "A calculated value for the voltage total harmonic 2836 disortion for phase to next phase. Method of calculation 2837 is not specified. IEC 61850-7-4 attribute 'ThdPPV'." 2838 ::= { pmACPwrQualityDelPhaseEntry 3 } 2840 pmACPwrQualityDelThdCurrent OBJECT-TYPE 2841 SYNTAX Integer32 (0..10000) 2842 UNITS "hundredths of percent" 2843 MAX-ACCESS read-only 2844 STATUS current 2845 DESCRIPTION 2846 "A calculated value for the voltage total harmonic 2847 disortion (THD) for phase to phase. Method of 2848 calculation is not specified. 2849 IEC 61850-7-4 attribute 'ThdPPV'." 2850 ::= { pmACPwrQualityDelPhaseEntry 4 } 2852 pmACPwrQualityWyePhaseTable OBJECT-TYPE 2853 SYNTAX SEQUENCE OF PmACPwrQualityWyePhaseEntry 2854 MAX-ACCESS not-accessible 2855 STATUS current 2856 DESCRIPTION 2857 "This table describes WYE configuration phase-to-neutral 2858 power quality measurements. This is a sparse extension 2859 of the pmACPwrQualityPhaseTable." 2860 ::= { powerQualityMIBObjects 4 } 2862 pmACPwrQualityWyePhaseEntry OBJECT-TYPE 2863 SYNTAX PmACPwrQualityWyePhaseEntry 2864 MAX-ACCESS not-accessible 2865 STATUS current 2866 DESCRIPTION 2867 "This table describes measurements of WYE configuration 2868 with phase to neutral power quality attributes. Three 2869 entries are required for each supported pmPowerIndex 2870 entry. Voltage measurements are relative to neutral. 2872 This is a sparse extension of the 2873 pmACPwrQualityPhaseTable. 2875 Each entry describes quality attributes of one phase of 2876 a WYE 3-phase power system. 2878 Measured values are from IEC 61850-7-2 MMUX and THD from 2879 MHAI objects." 2880 INDEX { pmPowerIndex, pmPhaseIndex } 2881 ::= { pmACPwrQualityWyePhaseTable 1} 2883 PmACPwrQualityWyePhaseEntry ::= SEQUENCE { 2884 pmACPwrQualityWyePhaseToNeutralVoltage Integer32, 2885 pmACPwrQualityWyePhaseCurrent Integer32, 2886 pmACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 2887 } 2889 pmACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE 2890 SYNTAX Integer32 2891 UNITS "0.1 Volt AC" 2892 MAX-ACCESS read-only 2893 STATUS current 2894 DESCRIPTION 2895 "A measured value of phase to neutral voltage. IEC 2896 61850-7-4 attribute 'PhV'." 2897 ::= { pmACPwrQualityWyePhaseEntry 1 } 2899 pmACPwrQualityWyePhaseCurrent OBJECT-TYPE 2900 SYNTAX Integer32 2901 UNITS "0.1 ampheres AC" 2902 MAX-ACCESS read-only 2903 STATUS current 2904 DESCRIPTION 2905 "A measured value of phase currents. IEC 61850-7-4 2906 attribute 'A'." 2907 ::= { pmACPwrQualityWyePhaseEntry 2 } 2909 pmACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE 2910 SYNTAX Integer32 (0..10000) 2911 UNITS "hundredths of percent" 2912 MAX-ACCESS read-only 2913 STATUS current 2914 DESCRIPTION 2915 "A calculated value of the voltage total harmonic 2916 distortion (THD) for phase to neutral. IEC 61850-7-4 2917 attribute 'ThdPhV'." 2918 ::= { pmACPwrQualityWyePhaseEntry 3 } 2920 -- Conformance 2922 powerQualityMIBCompliances OBJECT IDENTIFIER 2923 ::= { powerQualityMIB 2 } 2925 powerQualityMIBGroups OBJECT IDENTIFIER 2926 ::= { powerQualityMIB 3 } 2928 powerQualityMIBFullCompliance MODULE-COMPLIANCE 2929 STATUS current 2930 DESCRIPTION 2931 "When this MIB is implemented with support for read- 2932 create, then such an implementation can claim full 2933 compliance. Such devices can then be both monitored and 2934 configured with this MIB." 2935 MODULE -- this module 2936 MANDATORY-GROUPS { 2937 powerACPwrQualityMIBTableGroup, 2938 powerACPwrQualityPhaseMIBTableGroup 2939 } 2941 GROUP powerACPwrQualityDelPhaseMIBTableGroup 2942 DESCRIPTION 2943 "This group must only be implemented for a DEL phase 2944 configuration." 2946 GROUP powerACPwrQualityWyePhaseMIBTableGroup 2947 DESCRIPTION 2948 "This group must only be implemented for a WYE phase 2949 configuration." 2950 ::= { powerQualityMIBCompliances 1 } 2952 -- Units of Conformance 2954 powerACPwrQualityMIBTableGroup OBJECT-GROUP 2955 OBJECTS { 2956 -- Note that object pmPowerIndex is NOT 2957 -- included since it is not-accessible 2958 pmACPwrQualityConfiguration, 2959 pmACPwrQualityAvgVoltage, 2960 pmACPwrQualityAvgCurrent, 2961 pmACPwrQualityFrequency, 2962 pmACPwrQualityPowerUnitMultiplier, 2963 pmACPwrQualityPowerAccuracy, 2964 pmACPwrQualityTotalActivePower, 2965 pmACPwrQualityTotalReactivePower, 2966 pmACPwrQualityTotalApparentPower, 2967 pmACPwrQualityTotalPowerFactor, 2968 pmACPwrQualityThdAmpheres, 2969 pmACPwrQualityThdVoltage 2970 } STATUS current 2971 DESCRIPTION 2972 "This group contains the collection of all the power 2973 quality objects related to the Power Monitor." 2974 ::= { powerQualityMIBGroups 1 } 2976 powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP 2977 OBJECTS { 2978 -- Note that object pmPowerIndex is NOT 2979 -- included since it is not-accessible 2980 pmACPwrQualityPhaseAvgCurrent, 2981 pmACPwrQualityPhaseActivePower, 2982 pmACPwrQualityPhaseReactivePower, 2983 pmACPwrQualityPhaseApparentPower, 2984 pmACPwrQualityPhasePowerFactor, 2985 pmACPwrQualityPhaseImpedance 2986 } 2987 STATUS current 2988 DESCRIPTION 2989 "This group contains the collection of all 3-phase power 2990 quality objects related to the Power State." 2991 ::= { powerQualityMIBGroups 2 } 2993 powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP 2994 OBJECTS { 2995 -- Note that object pmPowerIndex and 2996 -- pmPhaseIndex are NOT included 2997 -- since they are not-accessible 2998 pmACPwrQualityDelPhaseToNextPhaseVoltage , 2999 pmACPwrQualityDelThdPhaseToNextPhaseVoltage, 3000 pmACPwrQualityDelThdCurrent 3001 } 3002 STATUS current 3003 DESCRIPTION 3004 "This group contains the collection of all quality 3005 attributes of a phase in a DEL 3-phase power system." 3006 ::= { powerQualityMIBGroups 3 } 3008 powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP 3009 OBJECTS { 3010 -- Note that object pmPowerIndex and 3011 -- pmPhaseIndex are NOT included 3012 -- since they are not-accessible 3013 pmACPwrQualityWyePhaseToNeutralVoltage, 3014 pmACPwrQualityWyePhaseCurrent, 3015 pmACPwrQualityWyeThdPhaseToNeutralVoltage 3016 } 3017 STATUS current 3018 DESCRIPTION 3019 "This group contains the collection of all WYE 3020 configuration phase-to-neutral power quality 3021 measurements." 3022 ::= { powerQualityMIBGroups 4 } 3024 END 3026 11. Security Considerations 3028 Some of the readable objects in these MIB modules (i.e., objects 3029 with a MAX-ACCESS other than not-accessible) may be considered 3030 sensitive or vulnerable in some network environments. It is 3031 thus important to control even GET and/or NOTIFY access to these 3032 objects and possibly to even encrypt the values of these objects 3033 when sending them over the network via SNMP. 3035 There are a number of management objects defined in these MIB 3036 modules with a MAX-ACCESS clause of read-write and/or read- 3037 create. Such objects MAY be considered sensitive or vulnerable 3038 in some network environments. The support for SET operations in 3039 a non-secure environment without proper protection can have a 3040 negative effect on network operations. The following are the 3041 tables and objects and their sensitivity/vulnerability: 3043 - Unauthorized changes to the pmPowerOperState (via 3044 thepmPowerAdminState ) MAY disrupt the power settings of the 3045 different Power Monitors, and therefore the state of 3046 functionality of the respective Power Monitors. 3047 - Unauthorized changes to the pmEnergyParametersTable MAY 3048 disrupt energy measurement in the pmEnergyTable table. 3050 SNMP versions prior to SNMPv3 did not include adequate security. 3051 Even if the network itself is secure (for example, by using 3052 IPsec), there is still no secure control over who on the secure 3053 network is allowed to access and GET/SET 3054 (read/change/create/delete) the objects in these MIB modules. 3056 It is RECOMMENDED that implementers consider the security 3057 features as provided by the SNMPv3 framework (see [RFC3410], 3058 section 8), including full support for the SNMPv3 cryptographic 3059 mechanisms (for authentication and privacy). 3061 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3062 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3063 enable cryptographic security. It is then a customer/operator 3064 responsibility to ensure that the SNMP entity giving access to 3065 an instance of these MIB modules is properly configured to give 3066 access to the objects only to those principals (users) that have 3067 legitimate rights to GET or SET (change/create/delete) them. 3069 12. IANA Considerations 3071 12.1. IANA Considerations for the MIB Modules 3073 The MIB modules in this document uses the following IANA- 3074 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers 3075 registry: 3077 Descriptor OBJECT IDENTIFIER value 3078 ---------- ----------------------- 3079 PowerMonitorMIB { mib-2 xxx } 3080 powerQualityMIB { mib-2 yyy } 3082 Additions to the MIB modules are subject to Expert Review 3083 [RFC5226], i.e., review by one of a group of experts designated 3084 by an IETF Area Director. The group of experts MUST check the 3085 requested MIB objects for completeness and accuracy of the 3086 description. Requests for MIB objects that duplicate the 3087 functionality of existing objects SHOULD be declined. The 3088 smallest available OIDs SHOULD be assigned to the new MIB 3089 objects. The specification of new MIB objects SHOULD follow the 3090 structure specified in Section 10. and MUST be published using 3091 a well-established and persistent publication medium. 3093 12.2. IANA Registration of new Power State Set 3095 This document specifies an initial set of Power State Sets. The 3096 list of these Power State Sets with their numeric identifiers is 3097 given in Section 5.2.1. The Internet Assigned Numbers Authority 3098 (IANA) has created a new registry for Power State Sets numeric 3099 identifiers and filled it with the initial list as in Section 3100 5.2.1. New Assignments to Power State Sets shall be 3101 administered by IANA and the guidelines and procedures are 3102 listed in this Section. 3104 New assignments for Power State Set will be administered by IANA 3105 through Expert Review [RFC5226], i.e., review by one of a group 3106 of experts designated by an IETF Area Director. The group of 3107 experts MUST check the requested state for completeness and 3108 accuracy of the description. A pure vendor specific 3109 implementation of Power State Set shall not be adopted; since it 3110 would lead to proliferation of Power State Sets. 3112 12.2.1. IANA Registration of the IEEE1621 Power State Set 3114 This document specifies a set of values for the IEEE1621 Power 3115 State Set [IEEE1621]. The list of these values with their 3116 identifiers is given in Section 5.2.1. The Internet Assigned 3117 Numbers Authority (IANA) created a new registry for IEEE1621 3118 Power State Set identifiers and filled it with the initial list 3119 in Section 5.2.2. 3121 New assignments (or potentially deprecation) for IEEE1621 Power 3122 State Set will be administered by IANA through Expert Review 3123 [RFC5226], i.e., review by one of a group of experts designated 3124 by an IETF Area Director. The group of experts MUST check the 3125 requested state for completeness and accuracy of the 3126 description. 3128 12.2.2. IANA Registration of the DMTF Power State Set 3130 This document specifies a set of values for the DMTF Power State 3131 Set. The list of these values with their identifiers is given 3132 in Section 5.2.1. The Internet Assigned Numbers Authority 3133 (IANA) has created a new registry for DMTF Power State Set 3134 identifiers and filled it with the initial list in Section 3135 5.2.1. 3137 New assignments (or potentially deprecation) for DMTF Power 3138 State Set will be administered by IANA through Expert Review 3139 [RFC5226], i.e., review by one of a group of experts designated 3140 by an IETF Area Director. The group of experts MUST check the 3141 conformance with the DMTF standard [DMTF], on the top of 3142 checking for completeness and accuracy of the description. 3144 12.2.3. IANA Registration of the EMAN Power State Set 3146 This document specifies a set of values for the EMAN Power State 3147 Set. The list of these values with their identifiers is given 3148 in Section 5.2.1. The Internet Assigned Numbers Authority 3149 (IANA) has created a new registry for EMAN Power State Set 3150 identifiers and filled it with the initial list in Section 3151 5.2.1. 3153 New assignments (or potentially deprecation) for EMAN Power 3154 State Set will be administered by IANA through Expert Review 3155 [RFC5226], i.e., review by one of a group of experts designated 3156 by an IETF Area Director. The group of experts MUST check the 3157 requested state for completeness and accuracy of the 3158 description. 3160 12. Contributors 3162 This document results from the merger of two initial proposals. 3163 The following persons made significant contributions either in 3164 one of the initial proposals or in this document. 3166 John Parello 3168 Rolf Winter 3170 Dominique Dudkowski 3172 13. Acknowledgment 3174 The authors would like to thank Shamita Pisal for her prototype 3175 of this MIB module, and her valuable feedback. The authors 3176 would like to Michael Brown for improving the text dramatically. 3178 14. Open Issues 3180 OPEN ISSUE 1 : Double-check all the IEC references in the draft. 3182 IEC 61850-7-4 has been widely referenced in many EMAN drafts. 3183 The other IEC references suggested in the email list are: 3184 IEC 61000-4-30 and IEC 62053-21 and IEC 62301. It is 3185 important to resolve the correct IEC references soon. 3187 OPEN ISSUE 2 : Description clause of pmPowerIndex. Do we need 3188 this text ? Juergen Quittek to comment: 3190 "The identity provisioning method that has been chosen can be 3191 retrieved by reading the value of powerStateEnergyConsumerOid. 3192 In case of identities provided by the ENERGY-AWARE-MIB module, 3193 this OID points to an exising instance of pmPowerIndex, in 3194 case of the ENTITY MIB, the object points to a valid instance 3195 of entPhysicalIndex, and in a similar way, it points to a 3196 value of another MIB module if this is used for identifying 3197 entities. If no other MIB module has been chosen for providing 3198 entity identities, then the value of 3199 powerStateEnergyConsumerOid MUST be 0.0 (zeroDotZero). 3201 OPEN ISSUE 3: Textual convention for Power State Set 3203 PowerStateSeries ::= TEXTUAL-CONVENTION 3204 Why is this an OCTET STRING (SIZE(1)) and not simply an 3205 enumerated INTEGER? And if this is to be maintained by IANA, 3206 why not create a IANA-POWER-SERIES-TC MIB module so that one 3207 can simply fetch the latest version from IANA? 3209 Discussion is ongoing in the EMAN email list on the design of 3210 the TC and IANA registration. 3212 OPEN ISSUE 4: pmPowerEntry table has MIB objects which are 3213 common across multiple Power State Sets. 3215 This issue shall be fixed in the next revision of the draft. 3217 OPEN ISSUE 5: TimeStamps for Power measurements required ? 3219 OPEN ISSUE 6: Measurement of AC Power, Voltage, and Current 3221 "AC power is not an RMS measurement, it is an average reading. 3222 The term instantaneous AC power can be misleading and power 3223 meters do not report it. " 3225 Description clause of MIB objects pmPower, 3226 pmACPwrQualityAvgVoltage, pmACPwrQualityAvgCurrent to be 3227 updated. Sent email to Michael Suchoff for some text. 3229 OPEN ISSUE 7: In addition to WYE and Delta AC power 3230 configurations, 3-Phase hybrid of WYE and Delta should be 3231 considered ? 3232 Need more information on the hybrid of WYE and Delta 3233 configuration. Email seeking clarification sent to Michael 3234 Suchoff. 3236 OPEN ISSUE 8: Nameplate power consumption should be a fixed 3237 value or a range ? 3239 Presently, Nameplate power consumption contains the max value 3240 of power consumption (watts) of the device; useful for power 3241 planning purposes. The voltage range can be useful for power 3242 supply specification. 3244 OPEN ISSUE 9: AC data center management is detection of tripped 3245 circuit breakers, not covered in the MIB draft. 3247 Are Circuit breakers in scope of EMAN ? 3249 OPEN ISSUE 10: Time Series of measurements required ? Mechanism 3250 pull or push ? What shall the table consist of ? 3251 Power, Voltage, Current, Energy and Demand 3253 Discussion on the email list. Based on requirements with the 3254 need for time series for Power, may need to be considered for 3255 the MIB. 3257 OPEN ISSUE 11: Demand computation method 3259 "Energy not obtained by periodically polling a power 3260 measurement with a pmEnergyParametersSampleRate ; Energy (E) 3261 is measured to the product's certified IEC 62053-21 accuracy 3262 class" 3264 Need to verify with IEC62053-21. 3266 OPEN ISSUE 12: Consideration of IEEE-ISTO PWG in the IANA list 3267 of Power State Set ? PWG Imaging Systems Power Management MIB 3268 reference. 3270 OPEN ISSUE 13: check if all the requirements from [EMAN-REQ] are 3271 covered. 3273 OPEN ISSUE 14: Required Information on Powered Entities 3274 It would be helpful to identify variables that are static vs. 3275 those that are dynamic. There are some that are absolutely 3276 static, and others that just rarely change. 3278 15. References 3280 15.2. Normative References 3282 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 3283 Requirement Levels, BCP 14, RFC 2119, March 1997. 3285 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3286 Schoenwaelder, Ed., "Structure of Management 3287 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3288 1999. 3290 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3291 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3292 STD 58, RFC 2579, April 1999. 3294 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3295 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3296 April 1999. 3298 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 3299 RFC3621, December 2003. 3301 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3302 3)", RFC 4133, August 2005. 3304 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 3305 Base extension module for TIA-TR41.4 media endpoint 3306 discovery information", July 2005. 3308 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 3309 energy-aware-mib-02 ", work in progress, July 2011. 3311 15.3. Informative References 3313 [RFC1628] S. Bradner, "UPS Management Information Base", RFC 3314 1628, May 1994 3316 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3317 "Introduction and Applicability Statements for Internet 3318 Standard Management Framework ", RFC 3410, December 3319 2002. 3321 [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. 3322 Waldbusser, "Management Information Base (MIB) for the 3323 Simple Network Management Protocol (SNMP)", RFC3418, 3324 December 2002. 3326 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity 3327 Sensor Management Information Base", RFC 3433, December 3328 2002. 3330 [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 3331 4268,November 2005. 3333 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 3334 "Guidelines for Writing an IANA Considerations Section 3335 in RFCs ", BCP 26, RFC 5226, May 2008. 3337 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 3338 M. Chandramouli, " Requirements for Energy Management 3339 ", draft-ietf-eman-requirements-03 (work in 3340 progress),July 2011. . 3342 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. 3343 Quittek, "Energy Management Framework", draft-ietf- 3344 eman-framework-02 , July 2011. 3346 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 3347 Quittek, J. and B. Claise "Energy and Power Monitoring 3348 MIB ", draft-claise-energy-monitoring-mib-09, July 3349 2011. 3351 [EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy 3352 Management (EMAN) Applicability Statement", draft- 3353 tychon-eman-applicability-statement-02, work in 3354 progress, June 2011. 3356 [ACPI] "Advanced Configuration and Power Interface 3357 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 3358 0b.pdf 3360 [DMTF] "Power State Management Profile DMTF DSP1027 Version 3361 2.0" December 2009 3362 http://www.dmtf.org/sites/default/files/standards/docum 3363 ents/DSP1027_2.0.0.pdf 3365 [IEEE1621] "Standard for User Interface Elements in Power 3366 Control of Electronic Devices Employed in 3367 Office/Consumer Environments", IEEE 1621, December 3368 2004. 3370 [IEC.61850-7-4] International Electrotechnical Commission, 3371 "Communication networks and systems for power utility 3372 automation Part 7-4: Basic communication structure 3373 Compatible logical node classes and data object 3374 classes", 2010. 3376 [IEC.62053-21] International Electrotechnical Commission, 3377 "Electricity metering equipment (a.c.) Particular 3378 requirements Part 22: Static meters for active energy 3379 (classes 1 and 2)", 2003. 3381 [IEC.62053-22]International Electrotechnical Commission, 3382 "Electricity metering equipment (a.c.) Particular 3383 requirements Part 22: Static meters for active energy 3384 (classes 0,2 S and 0,5 S)", 2003. 3386 Authors' Addresses 3388 Mouli Chandramouli 3389 Cisco Systems, Inc. 3390 Sarjapur Outer Ring Road 3391 Bangalore, 3392 IN 3394 Phone: +91 80 4426 3947 3395 Email: moulchan@cisco.com 3397 Brad Schoening 3398 44 Rivers Edge Drive 3399 Little Silver, NJ 07739 3400 US 3401 Email: brad@bradschoening.com 3403 Juergen Quittek 3404 NEC Europe Ltd. 3405 NEC Laboratories Europe 3406 Network Research Division 3407 Kurfuersten-Anlage 36 3408 Heidelberg 69115 3409 DE 3411 Phone: +49 6221 4342-115 3412 Email: quittek@neclab.eu 3414 Thomas Dietz 3415 NEC Europe Ltd. 3416 NEC Laboratories Europe 3417 Network Research Division 3418 Kurfuersten-Anlage 36 3419 Heidelberg 69115 3420 DE 3422 Phone: +49 6221 4342-128 3423 Email: Thomas.Dietz@neclab.eu 3425 Benoit Claise 3426 Cisco Systems, Inc. 3427 De Kleetlaan 6a b1 3428 Diegem 1813 3429 BE 3431 Phone: +32 2 704 5622 3432 Email: bclaise@cisco.com