idnits 2.17.1 draft-claise-energy-monitoring-mib-09.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 233 has weird spacing: '...tateSet pmPow...' == Line 236 has weird spacing: '...tiplier pmP...' == Line 272 has weird spacing: '...wStatus pmEne...' == Line 277 has weird spacing: '...nterval pmEne...' == Line 284 has weird spacing: '...wStatus pmEne...' == (4 more instances...) -- The document date (July 8, 2011) is 4675 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: January 8 2012 Independent Consultant 6 J. Quittek 7 T. Dietz 8 NEC Europe Ltd. 9 B. Claise 10 Cisco Systems, Inc. 11 July 8, 2011 13 Power and Energy Monitoring MIB 14 draft-claise-energy-monitoring-mib-09 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance 19 with the provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as 30 "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html 38 This Internet-Draft will expire on January 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 Scenarios................................ 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............................................. 71 109 15.2. Normative References...............................71 110 15.3. Informative References.............................71 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]. 174 Some of these scenarios are presented later in Section 8. " 175 Implementation Scenarios". 177 4. Terminology 179 The definitions of basic terms like Power Monitor, Power Monitor 180 Parent, Power Monitor Child, Power Monitor Meter Domain, Power 181 State can be found in the Power Management Architecture [EMAN- 182 FRAMEWORK]. 184 EDITOR'S NOTE: it is foreseen that some more term will follow 185 such a Proxy, Aggregator, Energy Management, etc... 187 Power State Set 189 A Power State Set is defined as a sequence of incremental 190 energy saving modes of a device. The elements of this set can 191 be viewed as an interface for the underlying device- 192 implemented power settings of a device. Examples of Power 193 State Sets include DTMF [DMTF], IEEE1621 [IEEE1621], ACPI 194 [ACPI] and EMAN. 196 Power State 198 A Power State is defined as a specific power setting for a 199 Power Monitor (e.g., shut, hibernate, sleep, high). Within the 200 context of a Power State Set, the Power State of a device is 201 one of the power saving modes in that Power State Set. 203 EDITOR'S NOTE: the definitions of Power State Series and Power 204 State should be copied over in [EMAN-FRAMEWORK], and referenced 205 here. 207 5. Architecture Concepts Applied to the MIB Module 209 This section describes the concepts specified in the Power 210 Monitor Architecture [EMAN-FRAMEWORK] that pertain to power 211 usage, with specific information related to the MIB module 212 specified in this document. This subsection maps to the section 213 "Architecture High Level Concepts" in the Power Monitoring 214 Architecture [EMAN-FRAMEWORK]. 216 The Energy Monitoring MIB has 2 independent MIB modules. The 217 first MIB module powerMonitorMIB is focused on measurement of 218 power and energy. The second MIB module powerQualityMIB is 219 focused on Power Quality measurement. 221 The powerMonitorMIB MIB module consists of four tables. The 222 first table pmPowerTable is indexed by pmPowerIndex and 223 pmPowerStateSetIndex. The second table pmPowerStateTable indexed 224 by pmPowerIndex, pmPowerStateSetIndex and pmPowerStateIndex. 225 pmEnergyParametersTable and pmEnergyTable are indexed by 226 pmPowerIndex. 228 pmPowerTable(1) 229 | 230 +---pmPowerEntry(1) [pmPowerIndex, pmPowerStateSet] 231 | | 232 | +-- --- Integer32 pmPowerIndex(1) 233 | +-- --- PowerStateSet pmPowerStateSet(2) 234 | +-- r-n Integer32 pmPower(3) 235 | +-- r-n Integer32 pmPowerNamePlate(4) 236 | +-- r-n UnitMultiplier pmPowerUnitMultiplier(5) 237 | +-- r-n Integer32 pmPowerAccuracy(6) 238 | +-- r-n INTEGER pmMeasurementCaliber(7) 239 | +-- r-n INTEGER pmPowerCurrentType(8) 240 | +-- r-n INTEGER pmPowerOrigin(9) 241 | +-- rwn Integer32 pmPowerAdminState(10) 242 | +-- r-n Integer32 pmPowerOperState(11) 243 | +-- r-n OwnerString pmPowerStateEnterReason(12) 244 | | 245 | | 246 +---pmPowerStateTable(2) 247 | +--pmPowerStateEntry(1) 248 | | [pmPowerIndex, 249 | | pmPowerStateSet, 250 | | pmpowerStateIndex] 251 | +-- --- Integer32 pmPowerStateIndex(1) 252 | +-- r-n Interger32 pmPowerStateMaxPower (2) 253 | +-- r-n UnitMultiplier 254 | pmPowerStatePowerUnitMultiplier (3) 255 | +-- r-n TimeTicks pmPowerStateTotalTime(4) 256 | +-- r-n Counter64 pmPowerStateEnterCount(5) 257 | 259 +pmEnergyParametersTable(1) 260 +---pmEnergyParametersEntry(1) [pmPowerIndex] 261 | 262 | +-- r-n TimeInterval 263 | pmEnergyParametersIntervalLength (1) 264 | +-- r-n Integer32 265 | pmEnergyParametersIntervalNumber (2) 266 | +-- r-n Integer32 267 | pmEnergyParametersIntervalMode (3) 268 | +-- r-n TimeInterval 269 | pmEnergyParametersIntervalWindow (4) 270 | +-- r-n Integer32 271 | pmEnergyParametersSampleRate (5) 272 | +-- r-n RowStatus pmEnergyParametersStatus (6) 273 | 274 +pmEnergyTable(1) 275 +---pmEnergyEntry(1) [pmPowerIndex] 276 | 277 | +-- r-n TimeInterval pmEnergyIntervalStartTime (1) 278 | +-- r-n Integer32 pmEnergyIntervalEnergyUsed (2) 279 | +-- r-n UnitMultiplier 280 | pmEnergyIntervalEnergyUnitMultiplier (3) 281 | +-- r-n Integer32 pmEnergyIntervalMax (4) 282 | +-- r-n TimeTicks 283 | pmEnergyIntervalDiscontinuityTime(5) 284 | +-- r-n RowStatus pmEnergyParametersStatus (6) 286 The powerQualityMIB consists of four tables. PmACPwrQualityTable 287 is indexed by pmPowerIndex. PmACPwrQualityPhaseTable is indexed 288 by pmPowerIndex and pmPhaseIndex. pmACPwrQualityWyePhaseTable 289 and pmACPwrQualityDelPhaseTable are indexed by pmPowerIndex and 290 pmPhaseIndex. 292 pmPowerTable(1) 293 | 294 +---PmACPwrQualityEntry (1) [pmPowerIndex] 295 | | 296 | | 297 | +----- INTEGER pmACPwrQualityConfiguration (1) 298 | +-- r-n Interger32 pmACPwrQualityAvgVoltage (2) 299 | +-- r-n Integer32 pmACPwrQualityAvgCurrent (3) 300 | +-- r-n Integer32 pmACPwrQualityFrequency (4) 301 | +-- r-n UnitMultiplier 302 | pmACPwrQualityPowerUnitMultiplier (5) 303 | +-- r-n Integer32 pmACPwrQualityPowerAccuracy (6) 304 | +-- r-n Interger32 pmACPwrQualityTotalActivePower (7) 305 | +-- r-n Integer32 306 | pmACPwrQualityTotalReactivePower (8) 307 | +-- r-n Integer32 pmACPwrQualityTotalApparentPower (9) 308 | +-- r-n Integer32 pmACPwrQualityTotalPowerFactor(10) 309 | +-- r-n Integer32 pmACPwrQualityThdAmpheres (11) 310 | 311 +pmACPwrQualityPhaseTable (1) 312 +---PmACPwrQualityPhaseEntry(1)[pmPowerIndex, 313 | | pmPhaseIndex] 314 | | 315 | +-- r-n Integer32 pmPhaseIndex (1) 316 | +-- r-n Integer32 317 | | pmACPwrQualityPhaseAvgCurrent (2) 318 | +-- r-n Integer32 319 | | pmACPwrQualityPhaseActivePower (3) 320 | +-- r-n Integer32 321 | | pmACPwrQualityPhaseReactivePower (4) 322 | +-- r-n Integer32 323 | | pmACPwrQualityPhaseApparentPower (5) 324 | +-- r-n Integer32 325 | | pmACPwrQualityPhasePowerFactor (6) 326 | +-- r-n Integer32 327 | | pmACPwrQualityPhaseImpedance (7) 328 | | 329 +pmACPwrQualityDelPhaseTable (1) 330 +-- pmACPwrQualityDelPhaseEntry(1) 331 | | [pmPowerIndex, 332 | | pmPhaseIndex] 333 | +-- r-n Integer32 334 | | pmACPwrQualityDelPhaseToNextPhaseVoltage (1) 335 | +-- r-n Integer32 336 | | pmACPwrQualityDelThdPhaseToNextPhaseVoltage (2) 337 | +-- r-n Integer32 pmACPwrQualityDelThdCurrent (3) 338 | | 339 +pmACPwrQualityWyePhaseTable (1) 340 +-- pmACPwrQualityWyePhaseEntry (1) 341 | | [pmPowerIndex, 342 | | pmPhaseIndex] 343 | +-- r-n Integer32 344 | | pmACPwrQualityWyePhaseToNeutralVoltage (1) 345 | +-- r-n Integer32 346 | | pmACPwrQualityWyePhaseCurrent (2) 347 | +-- r-n Integer32 348 | | pmACPwrQualityWyeThdPhaseToNeutralVoltage (3) 349 | . 351 A UML representation of the MIB objects in the two MIB modules 352 are powerMonitorMIB and powerQualityMIB are presented. 354 +--------------------------+ 355 | PowerMonitor ID | 356 | | 357 | Energy-aware-MIB (*) | 358 | | +---------------------------+ 359 | | | | 360 | pmPowerIndex | | PowerMonitor Attributes | 361 | pmPowerStateSetIndex | | | 362 +--------------------------+ | pmPowerNamePlate | 363 | | | pmPowerMeasurementCaliber | 364 | | | pmPowerOrigin | 365 | | | pmPowerCurrentType | 366 | | +---------------------------+ 367 | | | 368 | | | 369 v | v 370 +-----------------------------------------+ 371 | PowerMonitor Measurement | 372 | | 373 | pmPower | 374 | pmPowerUnitMultiplier | 375 | pmPowerAccuracy | 376 +-----------------------------------------+ 377 ^ | ^ 378 | | | 379 +-------------------------+ | | 380 | PowerMonitor State | | +------------------------+ 381 | | | | PowerMonitor State | 382 | pmPowerAdminState | | | Statistics | 383 | pmPowerOperState | | | | 384 | pmPowerStateEnterReason | | | pmPowerStateMaxPower | 385 +-------------------------+ | | pmPowerStateTotalTime | 386 | | pmPowerStateEnterCount | 387 | +------------------------+ 388 | 389 | 390 | 391 | 393 Figure 1:UML diagram for powerMonitor MIB 395 (*) Link with the ENERGY-AWARE-MIB 396 | 397 | 398 | 399 V 400 +------------------------------------+ 401 | Energy Table | 402 | | 403 | pmEnergyIntervalStartTime | 404 | pmEnergyIntervalEnergyUsed | 405 | pmEnergyIntervalMax | 406 | pmEnergyIntervalDiscontinuityTime | 407 +------------------------------------+ 409 +--------------------------+ 410 | PowerMonitor ID | 411 | | 412 | Energy-aware-MIB (*) | 413 | | 414 | pmPowerIndex | 415 | pmPowerStateSetIndex | 416 +--------------------------+ 417 | 418 v 419 +-------------------------------------+ 420 | Power Quality | 421 | | 422 | pmACPwrQualityConfiguration | 423 | pmACPwrQualityAvgVoltage | 424 | pmACPwrQualityAvgCurrent 425 | pmACPwrQualityFrequency | 426 | pmACPwrQualityPowerUnitMultiplier | 427 | pmACPwrQualityPowerAccuracy | 428 | pmACPwrQualityTotalActivePower | 429 | pmACPwrQualityTotalReactivePower | 430 | pmACPwrQualityTotalApparentPower | 431 | pmACPwrQualityTotalPowerFactor | 432 | pmACPwrQualityThdAmpheres | 433 +-------------------------------------+ ^ 434 ^ ^ | 435 | | ------- 436 | ---- | 437 | | | 438 | | | 439 +-------------------------------------+ | | 440 | Power Phase Quality | | | 441 | | | | 442 | pmPhaseIndex | | | 443 | pmACPwrQualityPhaseAvgCurrent | | | 444 | pmACPwrQualityAvgCurrent | | | 445 | pmACPwrQualityFrequency | | | 446 | pmACPwrQualityPowerUnitMultiplier | | | 447 | pmACPwrQualityPowerAccuracy | | | 448 | pmACPwrQualityPhaseActivePower | | | 449 | pmACPwrQualityPhaseReactivePower | | | 450 | pmACPwrQualityPhaselApparentPower | | | 451 | pmACPwrQualityPhaseImpedance | | | 452 +-------------------------------------+ | | 453 | | 454 | | 455 +---------------------------------------------+ | 456 | Power Quality DEL Configuration | | 457 | | | 458 | pmACPwrQualityDelPhaseToNextPhaseVoltage | | 459 | pmACPwrQualityDelThdPhaseToNextPhaseVoltage | | 460 | pmACPwrQualityDelThdCurrent | | 461 +---------------------------------------------+ | 462 | 463 | 464 +---------------------------------------------+ 465 | Power Quality WYE Configuration | 466 | | 467 | pmACPwrQualityWyePhaseToNeutralVoltage | 468 | pmACPwrQualityWyePhaseCurrent | 469 | pmACPwrQualityWyeThdPhaseToNeutralVoltage | 470 +---------------------------------------------+ 472 Figure 2: UML diagram for the powerQualityMIB 474 5.1. Power Monitor Information 476 Refer to the "Power Monitor Information" section in [EMAN- 477 FRAMEWORK] for background information. An energy aware device 478 is considered an instance of a Power Monitor as defined in the 479 [EMAN-FRAMEWORK]. 481 The Power Monitor identity information is specified in the MIB 482 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the 483 pmTable.In this table, every Power Monitor SHOULD have a 484 printable name pmName, and MUST HAVE a unique Power Monitor 485 index pmIndex. The ENERGY-AWARE-MIB module returns the 486 relationship (parent/child) between Power Monitors. 488 EDITOR'S NOTE: this last sentence will have to be updated with 489 terms such as Aggregator, Proxy, etc... when the [EMAN- 490 FRAMEWORK] will stabilize. 492 5.2. Power State 494 Refer to the "Power Monitor States" section in [EMAN-FRAMEWORK] 495 for background information. 497 A Power Monitor may have energy conservation modes called Power 498 States. Between the ON and OFF states of a device, there can be 499 several intermediate energy saving modes. Those energy saving 500 modes are called as Power States. 502 Power States, which represent universal states of power 503 management of a Power Monitor, are specified by the pmPowerState 504 MIB object. The actual Power State is specified by the 505 pmPowerOperState MIB object, while the pmPowerAdminState MIB 506 object specifies the Power State requested for the Power 507 Monitor. The difference between the values of pmPowerOperState 508 and pmPowerAdminState can be attributed that the Power Monitor 509 is busy transitioning from pmPowerAdminState into the 510 pmPowerOperState, at which point it will update the content of 511 pmPowerOperState. In addition, the possible reason for change 512 in Power State is reported in pmPowerStateEnterReason. 513 Regarding pmPowerStateEnterReason, management stations and Power 514 Monitors should support any format of the owner string dictated 515 by the local policy of the organization. It is suggested that 516 this name contain at least the reason for the transition change, 517 and one or more of the following: IP address, management station 518 name, network manager's name, location, or phone number. 520 The MIB objects pmPowerOperState, pmPowerAdminState , and 521 pmPowerStateEnterReason are contained in the pmPowerTable MIB 522 table. 524 The pmPowerStateTable table enumerates the maximum power usage 525 in watts, for every single supported Power State of each Power 526 State Set supported by the Power Monitor In addition, 527 PowerStateTable provides additional statistics: 528 pmPowerStateEnterCount, the number of times an entity has 529 visited a particular Power State, and pmPowerStateTotalTime, the 530 total time spent in a particular Power State of a Power Monitor. 532 5.2.1. Power State Set 534 There are several standards and implementations of Power State 535 Sets. A Power Monitor can support one or multiple Power State 536 Set implementation(s) concurrently. 538 There are currently three Power State Sets advocated: 540 Reserved(0) 541 IEEE1621(1) - [IEEE1621] 542 DMTF(2) - [DMTF] 543 EMAN(3) - [EMAN-MONITORING-MIB] 545 The respective specific states related to each Power State Set 546 are specified in the following sections. 548 5.2.2. IEEE1621 Power State Set 550 The IEEE1621 Power State Set [IEEE1621] consists of 3 551 rudimentary states : on, off or sleep. 552 on(0) - The device is fully On and all features of the 553 device are in working mode. 554 off(1) - The device is mechanically switched off and does 555 not consume energy. 556 sleep(2) - The device is in a power saving mode, and some 557 features may not be available immediately. 559 5.2.3. DMTF Power State Set 561 DMTF [DMTF] standards organization has defined a power profile 562 standard based on the CIM (Common Information Model) model that 563 consists of 15 power states ON (2), SleepLight (3), SleepDeep 564 (4), Off-Hard (5), Off-Soft (6), Hibernate(7), PowerCycle Off- 565 Soft (8), PowerCycle Off-Hard (9), MasterBus reset (10), 566 Diagnostic Interrupt (11), Off-Soft-Graceful (12), Off-Hard 567 Graceful (13), MasterBus reset Graceful (14), Power-Cycle Off- 568 Soft Graceful (15), PowerCycle-Hard Graceful (16). DMTF 569 standard is targeted for hosts and computers. Details of the 570 semantics of each Power State within the DMTF Power State Set 571 can be obtained from the DMTF Power State Management Profile 572 specification [DMTF]. 574 DMTF power profile extends ACPI power states. The following 575 table provides a mapping between DMTF and ACPI Power State Set: 577 --------------------------------------------------- 578 | DMTF | ACPI | 579 | Power State | Power State | 580 --------------------------------------------------- 581 | Reserved(0) | | 582 --------------------------------------------------- 583 | Reserved(1) | | 584 --------------------------------------------------- 585 | ON (2) | G0-S0 | 586 -------------------------------------------------- 587 | Sleep-Light (3) | G1-S1 G1-S2 | 588 -------------------------------------------------- 589 | Sleep-Deep (4) | G1-S3 | 590 -------------------------------------------------- 591 | Power Cycle (Off-Soft) (5) | G2-S5 | 592 --------------------------------------------------- 593 | Off-hard (6) | G3 | 594 --------------------------------------------------- 595 | Hibernate (Off-Soft) (7) | G1-S4 | 596 --------------------------------------------------- 597 | Off-Soft (8) | G2-S5 | 598 --------------------------------------------------- 599 | Power Cycle (Off-Hard) (9) | G3 | 600 --------------------------------------------------- 601 | Master Bus Reset (10) | G2-S5 | 602 --------------------------------------------------- 603 | Diagnostic Interrupt (11) | G2-S5 | 604 --------------------------------------------------- 605 | Off-Soft Graceful (12) | G2-S5 | 606 --------------------------------------------------- 607 | Off-Hard Graceful (13) | G3 | 608 --------------------------------------------------- 609 | MasterBus Reset Graceful (14) | G2-S5 | 610 --------------------------------------------------- 611 | Power Cycle off-soft Graceful (15)| G2-S5 | 612 --------------------------------------------------- 613 | Power Cycle off-hard Graceful (16)| G3 | 614 --------------------------------------------------- 615 Figure 3: DMTF and ACPI Powe State Set Mapping 617 5.2.4. EMAN Power State Set 619 The EMAN Power State Set represents an attempt for a uniform 620 standard approach to model the different levels of power 621 consumption of a device. The EMAN Power States are an expansion 622 of the basic Power States as defined in IEEE1621 that also 623 incorporate the Power States defined in ACPI and DMTF. 624 Therefore, in addition to the non-operational states as defined 625 in ACPI and DMTF standards, several intermediate operational 626 states have been defined. 628 There are twelve Power States, that expand on IEEE1621 on,sleep 629 and off. The expanded list of Power States are divided into six 630 operational states, and six non-operational states. The lowest 631 non-operational state is 1 and the highest is 6. Each non- 632 operational state corresponds to an ACPI state [ACPI] 633 corresponding to Global and System states between G3 (hard-off) 634 and G1 (sleeping). For Each operational state represent a 635 performance state, and may be mapped to ACPI states P0 (maximum 636 performance power) through P5 (minimum performance and minimum 637 power). 639 An Power Monitor may have fewer Power States than twelve and 640 would then map several policy states to the same power state. 641 Power Monitor with more than twelve states, would choose which 642 twelve to represent as power policy states. 644 In each of the non-operational states (from mechoff(1) to 645 ready(6)), the Power State preceding it is expected to have a 646 lower power consumption and a longer delay in returning to an 647 operational state: 649 IEEE1621 Power(off): 651 mechoff(1) : An off state where no entity features are 652 available. The entity is unavailable. 653 No energy is being consumed and the power 654 connector can be removed. This 655 corresponds to ACPI state G3. 657 softoff(2) : Similar to mechoff(1), but some 658 components remain powered or receive 659 trace power so that the entity 660 can be awakened from its off state. In 661 softoff(2), no context is saved and the 662 device typically requires a complete boot 663 when awakened. This corresponds to ACPI 664 state G2. 666 IEEE1621 Power(sleep) 668 hibernate(3): No entity features are available. The 669 entity may be awakened without requiring 670 a complete boot, but the time for 671 availability is longer than sleep(4). An 672 example for state hibernate(3) is a save 673 to-disk state where DRAM context is not 674 maintained. Typically, energy consumption 675 is zero or close to zero. This 676 corresponds to state G1, S4 in ACPI. 678 sleep(4) : No entity features are available, except 679 for out-of-band management, for example 680 wake-up mechanisms. The time for 681 availability is longer than standby(5). 682 An example for state sleep(4) is a save- 683 to-RAM state, where DRAM context is 684 maintained. Typically, energy 685 consumption is close to zero. This 686 corresponds to state G1, S3 in ACPI. 688 standby(5) : No entity features are available, except 689 for out-of-band management, for example 690 wake-up mechanisms. This mode is analogous 691 to cold-standy. The time for availability 692 is longer than ready(6). For example, the 693 processor context is not maintained. 694 Typically, energy consumption is close to 695 zero. This corresponds to state G1, S2 in 696 ACPI. 698 ready(6) : No entity features are available, except 699 for out-of-band management, for example 700 wake-up mechanisms. This mode is 701 analogous to hot-standby. The entity can 702 be quickly transitioned into an 703 operational state. For example, 704 processors are not executing, but 705 processor context is maintained. This 706 corresponds to state G1, S1 in ACPI. 708 IEEE1621 Power(on): 710 lowMinus(7) : Indicates some entity features may not be 711 available and the entity has selected 712 measures/options to provide less than 713 low(8) usage. This corresponds to 714 ACPI State G0. This includes operational 715 states lowMinus(7) to full(12). 717 low(8) : Indicates some features may not be 718 available and the entity has taken 719 measures or selected options to provide 720 less than mediumMinus(9) usage. 722 mediumMinus(9): Indicates all entity features are 723 available but the entity has taken 724 measures or selected options to provide 725 less than medium(10) usage. 727 medium(10) : Indicates all entity features are 728 available but the entity has taken 729 measures or selected options to provide 730 less than highMinus(11) usage. 732 highMinus(11): Indicates all entity features are 733 available and power usage is less 734 than high(12). 736 high(12) : Indicates all entity features are 737 available and the entity is consuming the 738 highest power. 740 5.3. Power Monitor Usage Information 742 Refer to the "Power Monitor Usage Measurement" section in [EMAN- 743 FRAMEWORK] for background information. 745 For a Power Monitor, power usage is reported using pmPower. The 746 magnitude of measurement is based on the pmPowerUnitMultiplier 747 MIB variable, based on the UnitMultiplier Textual Convention 748 (TC). Power measurement magnitude should conform to the IEC 749 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22] 750 definition of unit multiplier for the SI (System International) 751 units of measure. Measured values are represented in SI units 752 obtained by BaseValue * 10 raised to the power of the scale. 754 For example, if current power usage of a Power Monitor is 3, it 755 could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of 756 pmPowerUnitMultiplier. Note that other measurements throughout 757 the two MIB modules in this document use the same mechanism, 758 including pmPowerStatePowerUnitMultiplier, 759 pmEnergyIntervalEnergyUnitMultiplier, and 760 pmACPwrQualityPowerUnitMultiplier. 762 In addition to knowing the usage and magnitude, it is useful to 763 know how a pmPower measurement was obtained. An NMS can use 764 this to account for the accuracy and nature of the reading 765 between different implementations. For this pmPowerOrigin 766 describes whether the measurements were made at the device 767 itself or from a remote source. The pmPowerMeasurementCaliber 768 describes the method that was used to measure the power and can 769 distinguish actual or estimated values. There may be devices in 770 the network, which may not be able to measure or report power 771 consumption. For those devices, the object 772 pmPowerMeasurementCaliber shall report that measurement 773 mechanism is "unavailable" and the pmPower measurement shall be 774 "0". 776 The nameplate power rating of a Power Monitor is specified in 777 pmPowerNameplate MIB object. 779 5.4. Optional Power Usage Quality 781 Refer to the "Optional Power Usage Quality" section in [EMAN- 782 FRAMEWORK] for background information. 784 The optional powerQualityMIB MIB module can be implemented to 785 further describe power usage quality measurement. The 786 powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 787 standard to describe AC measurements. 789 The powerQualityMIB MIB module contains a primary table, the 790 pmACPwrQualityTable table, that defines power quality 791 measurements for supported pmIndex entities, as a sparse 792 extension of the pmPowerTable (with pmPowerIndex as primary 793 index). This pmACPwrQualityTable table contains such 794 information as the configuration (single phase, DEL 3 phases, 795 WYE 3 phases), voltage, frequency, power accuracy, total 796 active/reactive power/apparent power, amperage, and voltage. 798 In case of 3-phase power, the pmACPwrQualityPhaseTable 799 additional table is populated with power quality measurements 800 per phase (so double indexed by the pmPowerIndex and 801 pmPhaseIndex). This table, which describes attributes common to 802 both WYE and DEL configurations, contains the average current, 803 active/reactive/apparent power, power factor, and impedance. 805 In case of 3-phase power with a DEL configuration, the 806 pmACPwrQualityDelPhaseTable table describes the phase-to-phase 807 power quality measurements, i.e., voltage and current. 809 In case of 3-phase power with a Wye configuration, the 810 pmACPwrQualityWyePhaseTable table describes the phase-to-neutral 811 power quality measurements, i.e., voltage and current. 813 5.5. Optional Energy Measurement 815 Refer to the "Optional Energy and demand Measurement" section in 816 [EMAN-FRAMEWORK] for the definition and terminology information. 818 It is relevant to measure energy when there are actual power 819 measurements from a Power Monitor, and not when the power 820 measurement is assumed or predicted as specified in the 821 description clause of the object pmPowerMeasurementCaliber. 823 Two tables are introduced to characterize energy measurement of 824 a Power Monitor: pmEnergyTable and pmEnergyParametersTable. 825 Both energy and demand information can be represented via the 826 pmEnergyTable. Energy information will be an accumulation with 827 no interval. Demand information can be represented as an 828 average accumulation per interval of time. 830 The pmEnergyParametersTable consists of the parameters defining 831 the duration of measurement intervals in seconds, 832 (pmEnergyParametersIntervalLength), the number of successive 833 intervals to be stored in the pmEnergyTable, 834 (pmEnergyParametersIntervalNumber), the type of measurement 835 technique (pmEnergyParametersIntervalMode), and a sample rate 836 used to calculate the average (pmEnergyParametersSampleRate). 837 Judicious choice of the sampling rate will ensure accurate 838 measurement of energy while not imposing an excessive polling 839 burden. 841 There are three pmEnergyParametersIntervalMode types used for 842 energy measurement collection: period, sliding, and total. The 843 choices of the the three different modes of collection are based 844 on IEC standard 61850-7-4. Note that multiple 845 pmEnergyParametersIntervalMode types MAY be configured 846 simultaneously. 848 These three pmEnergyParametersIntervalMode types are illustrated 849 by the following three figures, for which: 851 - The horizontal axis represents the current time, with the 852 symbol <--- L ---> expressing the 853 pmEnergyParametersIntervalLength, and the 854 pmEnergyIntervalStartTime is represented by S1, S2, S3, S4, ..., 855 Sx where x is the value of pmEnergyParametersIntervalNumber. 857 - The vertical axis represents the time interval of sampling and 858 the value of pmEnergyIntervalEnergyUsed can be obtained at the 859 end of the sampling period. The symbol =========== denotes the 860 duration of the sampling period. 862 | | | =========== | 863 |============ | | | 864 | | | | 865 | |============ | | 866 | | | | 867 | <--- L ---> | <--- L ---> | <--- L ---> | 868 | | | | 869 S1 S2 S3 S4 871 Figure 4 : Period pmEnergyParametersIntervalMode 873 A pmEnergyParametersIntervalMode type of 'period' specifies non- 874 overlapping periodic measurements. Therefore, the next 875 pmEnergyIntervalStartTime is equal to the previous 876 pmEnergyIntervalStartTime plus pmEnergyParametersIntervalLength. 877 S2=S1+L; S3=S2+L, ... 879 |============ | 880 | | 881 | <--- L ---> | 882 | | 883 | |============ | 884 | | | 885 | | <--- L ---> | 886 | | | 887 | | |============ | 888 | | | | 889 | | | <--- L ---> | 890 | | | | 891 | | | |============ | 892 | | | | | 893 | | | | <--- L ---> | 894 S1 | | | | 895 | | | | 896 | | | | 897 S2 | | | 898 | | | 899 | | | 900 S3 | | 901 | | 902 | | 903 S4 905 Figure 5 : Sliding pmEnergyParametersIntervalMode 907 A pmEnergyParametersIntervalMode type of 'sliding' specifies 908 overlapping periodic measurements. 910 | | 911 |========================= | 912 | | 913 | | 914 | | 915 | <--- Total length ---> | 916 | | 917 S1 919 Figure 4 : Total pmEnergyParametersIntervalMode 921 A pmEnergyParametersIntervalMode type of 'total' specifies a 922 continuous measurement since the last reset. The value of 923 pmEnergyParametersIntervalNumber should be (1) one and 924 pmEnergyParametersIntervalLength is ignored. 926 The pmEnergyParametersStatus is used to start and stop energy 927 usage logging. The status of this variable is "active" when 928 all the objects in pmEnergyParametersTable are appropriate which 929 in turn indicates if pmEnergyTable entries exist or not. 931 The pmEnergyTable consists of energy measurements 932 inpmEnergyIntervalEnergyUsed , the units of the measured energy 933 pmEnergyIntervalEnergyUnitMultiplier, and the maximum observed 934 energy within a window - pmEnergyIntervalMax. 936 Measurements of the total energy consumed by a Power Monitor may 937 suffer from interruptions in the continuous measurement of 938 energy consumption. In order to indicate such interruptions, 939 the object pmEnergyIntervalDiscontinuityTime is provided for 940 indicating the time of the last interruption of total energy 941 measurement. pmEnergyIntervalDiscontinuityTime shall indicate 942 the sysUpTime [RFC3418] when the device was reset. 944 The following example illustrates the pmEnergyTable and 945 pmEnergyParametersTable: 947 First, in order to estimate energy, a time interval to sample 948 energy should be specified, i.e. 949 pmEnergyParametersIntervalLength can be set to "900 seconds" or 950 15 minutes and the number of consecutive intervals over which 951 the maximum energy is calculated 952 (pmEnergyParametersIntervalNumber) as "10". The sampling rate 953 internal to the Power Monitor for measurement of power usage 954 (pmEnergyParametersSampleRate) can be "1000 milliseconds", as 955 set by the Power Monitor as a reasonable value. Then, the 956 pmEnergyParametersStatus is set to active (value 1) to indicate 957 that the Power Monitor should start monitoring the usage per the 958 pmEnergyTable. 960 The indices in the pmEnergyTable are pmPowerIndex, which 961 identifies the Power Monitor, and pmEnergyIntervalStartTime, 962 which denotes the start time of the energy measurement interval 963 based on sysUpTime [RFC3418]. The value of 964 pmEnergyIntervalEnergyUsed is the measured energy consumption 965 over the time interval specified 966 (pmEnergyParametersIntervalLength) based on the Power Monitor 967 internal sampling rate (pmEnergyParametersSampleRate). While 968 choosing the values for the pmEnergyParametersIntervalLength and 969 pmEnergyParametersSampleRate, it is recommended to take into 970 consideration either the network element resources adequate to 971 process and store the sample values, and the mechanism used to 972 calculate the pmEnergyIntervalEnergyUsed. The units are derived 973 from pmEnergyIntervalPowerUnitMultiplier. For example, 974 pmEnergyIntervalPowerUsed can be "100" with 975 pmEnergyIntervalPowerUnits equal to 0, the measured energy 976 consumption of the Power Monitor is 100 watt-hours. The 977 pmEnergyIntervalMax is the maximum energyobserved and that can 978 be "150 watt-hours". 980 The pmEnergyTable has a buffer to retain a certain number of 981 intervals, as defined by pmEnergyParametersIntervalNumber. If 982 the default value of "10" is kept, then the pmEnergyTable 983 contains 10 energymeasurements, including the maximum. 985 Here is a brief explanation of how the maximum energy can be 986 calculated. The first observed energy measurement value is 987 taken to be the initial maximum. With each subsequent 988 measurement, based on numerical comparison, maximum energy may 989 be updated. The maximum value is retained as long as the 990 measurements are taking place. Based on periodic polling of 991 this table, an NMS could compute the maximum over a longer 992 period, i.e. a month, 3 months, or a year. 994 5.6. Fault Management 996 [EMAN-REQ] specifies requirements about Power States such as 997 "the current power state" , "the time of the last state change", 998 "the total time spent in each state", "the number of transitions 999 to each state" etc. Some of these requirements are fulfilled 1000 explicitly by MIB objects such as pmPowerOperState, 1001 pmPowerStateTotalTime and pmPowerStateEnterCount. Some of the 1002 other requirements are met via the SNMP NOTIFICATION mechanism. 1003 pmPowerStateChange SNMP notification which is generated when the 1004 value(s) of pmPowerStateSet, pmPowerOperState, pmPowerAdminState 1005 have changed. 1007 6. Discovery 1009 6.1. ENERGY-AWARE-MIB Module Implemented 1011 The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- 1012 MIB], if available, in order to discover all the Power Monitors 1013 and the relationships between those (notion of Parent/Child). 1014 In the ENERGY-AWARE-MIB module tables, the Power Monitors are 1015 indexed by the pmIndex. 1017 If an implementation of the ENERGY-AWARE-MIB module is available 1018 in the local SNMP context, for the same Power Monitor, the 1019 pmIndex value (EMAN-AWARE-MIB) MUST be assigned to the 1020 pmPowerIndex for The pmPowerIndex characterizes the Power 1021 Monitor in the powerMonitorMIB and powerQualityMIB MIB modules 1022 (this document). 1024 From there, the NMS must poll the pmPowerStateTable (specified 1025 in the powerMonitorMIB module in this document), which 1026 enumerates, amongst other things, the maximum power usage. As 1027 the entries in pmPowerStateTable table are indexed by the Power 1028 Monitor (pmPowerIndex), by the Power State Set 1029 (pmPowerStateSetIndex), and by the Power State 1030 (pmPowerStateIndex), the maximum power usage is discovered per 1031 Power Monitor, per Power State Set, and per Power Usage. In 1032 other words, polling the pmPowerStateTable allows the discovery 1033 of each Power State within every Power State Set supported by 1034 the Power Monitor. 1036 If the Power Monitor is an Aggregator or a Proxy, the MIB module 1037 would be populated with the Power Monitor Parent and Children 1038 information, which have their own Power Monitor index value 1039 (pmPowerIndex). However, the parent/child relationship must be 1040 discovered thanks to the ENERGY-AWARE-MIB module. 1042 Finally, the NMS can monitor the Power Quality thanks to the 1043 powerQualityMIB MIB module, which reuses the pmPowerIndex to 1044 index the Power Monitor. 1046 6.2. ENERGY-AWARE-MIB Module Not Implemented, ENTITY-MIB 1047 Implemented 1049 When the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] is not 1050 implemented, the NMS must poll the ENTITY-MIB [RFC4133] in order 1051 to discover some more information about the Power Monitors. 1052 Indeed, the index for the Power Monitors in the MIB modules 1053 specified in this document is the pmPowerIndex, which specifies: 1054 "If there is no implementation of the ENERGY-AWARE-MIB module 1055 but one of the ENTITY MIB module is available in the local SNMP 1056 context, then the same index of an entity MUST be chosen as 1057 assigned to the entity by object entPhysicalIndex in the ENTITY 1058 MIB module." 1060 As the Section 6.1. , the NMS must then poll the 1061 pmPowerStateTable (specified in the powerMonitorMIB module in 1062 this document), indexed by the Power Monitor (pmPowerIndex that 1063 inherited the entPhysicalIndex value), by the Power State Set 1064 (pmPowerStateSetIndex), and by the Power State 1065 (pmPowerStateIndex). Then the NMS has discovered every Power 1066 State within each Power State Set supported by the Power 1067 Monitor. 1069 Note that, without the ENERGY-AWARE-MIB module, the Power 1070 Monitor acts as an standalone device, i.e. the notion of 1071 parent/child can't be specified. 1073 6.3. ENERGY-AWARE-MIB Module and ENTITY-MIB Not Implemented 1075 If neither the ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] nor of 1076 the ENTITY MIB module [RFC4133] are available in the local SNMP 1077 context, then this MIB module may choose identity values from a 1078 further MIB module providing entity identities. 1080 Note that, without the ENERGY-AWARE-MIB module, the Power 1081 Monitor acts as an standalone device, i.e. the notion of 1082 parent/child can't be specified. 1084 7. Link with the other IETF MIBs 1086 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB 1088 RFC 4133 [RFC4133] defines the ENTITY MIB module that lists the 1089 physical entities of a networking device (router, switch, etc.) 1090 and those physical entities indexed by entPhysicalIndex. From 1091 an energy-management standpoint, the physical entities that 1092 consume or produce energy are of interest. 1094 RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that 1095 provides a standardized way of obtaining information (current 1096 value of the sensor, operational status of the sensor, and the 1097 data units precision) from sensors embedded in networking 1098 devices. Sensors are associated with each index of 1099 entPhysicalIndex of the ENTITY MIB [RFC4133]. While the focus 1100 of the Power and Energy Monitoring MIB is on measurement of 1101 power usage of networking equipment indexed by the ENTITY MIB, 1102 this MIB proposes a customized power scale for power measurement 1103 and different power state states of networking equipment, and 1104 functionality to configure the power state states. 1106 When this MIB module is used to monitor the power usage of 1107 devices like routers and switches, the ENTITY MIB and ENTITY- 1108 SENSOR MIB SHOULD be implemented. In such cases, the Power 1109 Monitors are modeled by the entPhysicalIndex through the 1110 pmPhysicalEntity MIB object specified in the pmTable in the 1111 ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. 1113 However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI 1114 C12.x accuracy classes required for electricity (i.e., 1%, 2%, 1115 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 1116 represents "The number of decimal places of precision in fixed- 1117 point sensor values returned by the associated entPhySensorValue 1118 object". The ANSI and IEC Standards are used for power 1119 measurement and these standards require that we use an accuracy 1120 class, not the scientific-number precision model specified in 1121 RFC3433. The pmPowerAccuracy MIB object models this accuracy. 1122 Note that pmPowerUnitMultipler represents the scale factor per 1123 IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], 1124 which is a more logical representation for power measurements 1125 (compared to entPhySensorScale), with the mantissa and the 1126 exponent values X * 10 ^ Y. 1128 Power measurements specifying the qualifier 'UNITS' for each 1129 measured value in watts are used in the LLDP-EXT-MED-MIB, POE 1130 [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier 1131 is used for the power measurement values. 1133 One cannot assume that the ENTITY MIB and ENTITY-SENSOR MIB are 1134 implemented for all Power Monitors that need to be monitored. A 1135 typical example is a converged building gateway, monitoring 1136 several other devices in the building, doing the proxy between 1137 SNMP and a protocol like BACNET. Another example is the home 1138 energy controller. In such cases, the pmPhysicalEntity value 1139 contains the zero value, thanks to PhysicalIndexOrZero textual 1140 convention. 1142 The pmPowerIndex MIB object has been kept as the unique Power 1143 Monitor index. The pmPower is similar to entPhySensorValue 1144 [RFC3433] and the pmPowerUnitMultipler is similar to 1145 entPhySensorScale. 1147 7.2. Link with the ENTITY-STATE MIB 1149 For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE 1150 MIB [RFC4268] specifies the operational states (entStateOper: 1151 unknown, enabled, disabled, testing), the alarm (entStateAlarm: 1152 unknown, underRepair, critical, major, minor, warning, 1153 indeterminate) and the possible values of standby states 1154 (entStateStandby: unknown, hotStandby, coldStandby, 1155 providingService). 1157 From a power monitoring point of view, in contrast to the entity 1158 operational states of entities, Power States are required, as 1159 proposed in the Power and Energy Monitoring MIB module. Those 1160 Power States can be mapped to the different operational states 1161 in the ENTITY-STATE MIB, if a formal mapping is required. For 1162 example, the entStateStandby "unknown", "hotStandby", 1163 "coldStandby", states could map to the Power State "unknown", 1164 "ready", "standby", respectively, while the entStateStandby 1165 "providingService" could map to any "low" to "high" Power State. 1167 7.3. Link with the POWER-OVER-ETHERNET MIB 1169 Power-over-Ethernet MIB [RFC3621] provides an energy monitoring 1170 and configuration framework for power over Ethernet devices. 1171 The RFC introduces a concept of a port group on a switch to 1172 define power monitoring and management policy and does not use 1173 the entPhysicalIndex as the index. Indeed, the 1174 pethMainPseConsumptionPower is indexed by the 1175 pethMainPseGroupIndex, which has no mapping with the 1176 entPhysicalIndex. 1178 One cannot assume that the Power-over-Ethernet MIB is 1179 implemented for all Power Monitors that need to be monitored. A 1180 typical example is a converged building gateway, monitoring 1181 several other devices in the building, doing the proxy between 1182 SNMP and a protocol like BACNET. Another example is the home 1183 energy controller. In such cases, the pmethPortIndex and 1184 pmethPortGrpIndex values contain the zero value, thanks to new 1185 PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero 1186 conventions. 1188 However, if the Power-over-Ethernet MIB [RFC3621] is supported, 1189 the Power Monitor pmethPortIndex and pmethPortGrpIndex contain 1190 the pethPsePortIndex and pethPsePortGroupIndex, respectively. 1192 As a consequence, the pmPowerIndex MIB object has been kept as 1193 the unique Power Monitor index. 1195 Note that, even though the Power-over-Ethernet MIB [RFC3621] was 1196 created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse 1197 the precision notion from the ENTITY-SENSOR MIB, i.e. the 1198 entPhySensorPrecision MIB object. 1200 7.4. Link with the UPS MIB 1202 To protect against unexpected power disruption, data centers and 1203 buildings make use of Uninterruptible Power Supplies (UPS). To 1204 protect critical assets, a UPS can be restricted to a particular 1205 subset or domain of the network. UPS usage typically lasts only 1206 for a finite period of time, until normal power supply is 1207 restored. Planning is required to decide on the capacity of the 1208 UPS based on output power and duration of probable power outage. 1209 To properly provision UPS power in a data center or building, it 1210 is important to first understand the total demand required to 1211 support all the entities in the site. This demand can be 1212 assessed and monitored via the Power and Energy Monitoring MIB. 1214 UPS MIB [RFC1628] provides information on the state of the UPS 1215 network. Implementation of the UPS MIB is useful at the 1216 aggregate level of a data center or a building. The MIB module 1217 contains several groups of variables: 1219 - upsIdent: Identifies the UPS entity (name, model, etc.). 1221 - upsBattery group: Indicates the battery state 1222 (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) 1224 - upsInput group: Characterizes the input load to the UPS 1225 (number of input lines, voltage, current, etc.). 1227 - upsOutput: Characterizes the output from the UPS (number of 1228 output lines, voltage, current, etc.) 1230 - upsAlarms: Indicates the various alarm events. 1232 The measurement of power in the UPS MIB is in Volts, Amperes and 1233 Watts. The units of power measurement are RMS volts and RMS 1234 Amperes. They are not based on the EntitySensorDataScale and 1235 EntitySensorDataPrecision of Entity-Sensor MIB. 1237 Both the Power and Energy Monitoring MIB and the UPS MIB may be 1238 implemented on the same UPS SNMP agent, without conflict. In 1239 this case, the UPS device itself is the Power Monitor Parent and 1240 any of the UPS meters or submeters are the Power Monitor 1241 Children. 1243 7.5. Link with the LLDP and LLDP-MED MIBs 1245 The LLDP Protocol is a Data Link Layer protocol used by network 1246 devices to advertise their identities, capabilities, and 1247 interconnections on a LAN network. 1249 The Media Endpoint Discovery is an enhancement of LLDP, known as 1250 LLDP-MED. The LLDP-MED enhancements specifically address voice 1251 applications. LLDP-MED covers 6 basic areas: capability 1252 discovery, LAN speed and duplex discovery, network policy 1253 discovery, location identification discovery, inventory 1254 discovery, and power discovery. 1256 Of particular interest to the current MIB module is the power 1257 discovery, which allows the endpoint device (such as a PoE 1258 phone) to convey power requirements to the switch. In power 1259 discovery, LLDP-MED has four Type Length Values (TLVs): power 1260 type, power source, power priority and power value. 1261 Respectively, those TLVs provide information related to the type 1262 of power (power sourcing entity versus powered device), how the 1263 device is powered (from the line, from a backup source, from 1264 external power source, etc.), the power priority (how important 1265 is it that this device has power?), and how much power the 1266 device needs. 1268 The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 1269 actually comes from the Power-over-Ethernet MIB [RFC3621]. If 1270 the Power-over-Ethernet MIB [RFC3621] is supported, the exact 1271 value from the pethPsePortPowerPriority [RFC3621] is copied over 1272 in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise 1273 the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From 1274 the Power and Energy Monitoring MIB, it is possible to identify 1275 the pethPsePortPowerPriority [RFC3621], thanks to the 1276 pmethPortIndex and pmethPortGrpIndex. 1278 The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to 1279 pmPowerOrigin in indicating if the power for an attached device 1280 is local or from a remote device. If the LLDP-MED MIB is 1281 supported, the following mapping can be applied to the 1282 pmPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and 1283 local(3) can be mapped to remote(2) and self(1), respectively. 1285 8. Implementation Scenarios 1287 This section provides an illustrative example scenario for the 1288 implementation of the Power Monitor, including Power Monitor 1289 Parent and Power Monitor Child relationships. 1291 Example Scenario of a campus network: Switch with PoE Endpoints 1292 with further connected Devices 1294 The campus network consists of switches that provide LAN 1295 connectivity. The switch with PoE ports is located in wiring 1296 closet. PoE IP phones are connected to the switch. The IP 1297 phones draw power from the PoE ports of the switch. In 1298 addition, a PC is daisy-chained from the IP phone for LAN 1299 connectivity. 1301 The IP phone consumes power from the PoE switch, while the PC 1302 consumes power from the wall outlet. 1304 The switch has implementations of Entity MIB [RFC4133] and 1305 energy-aware MIB [EMAN-AWARE-MIB] while the PC does not have 1306 implementation of the Entity MIB, but has an implementation of 1307 energy-aware MIB. The switch has the following attributes, 1308 pmPowerIndex "1", pmPhysicalEntity "2", and pmPowerMonitorId 1309 "UUID 1000". The power usage of the switch is "440 Watts". The 1310 switch does not have a Power Monitor Parent. 1312 The PoE switch port has the following attributes: The switch 1313 port has pmPowerIndex "3", pmPhysicalEntity is "12" and 1314 pmPowerMonitorId is "UUID 1000:3". The power metered at the POE 1315 switch port is "12 watts". In this example, the POE switch port 1316 has the switch as the Power Monitor Parent, with its pmParentID 1317 of "1000". 1319 The attributes of the PC are given below. The PC does not 1320 implementation of Entity MIB, and thus does not have 1321 pmPhysicalEntity. The pmPowerIndex (pmPIndex) of the PC is 1322 "57", the pmPowerMonitorId is "UUID 1000:57 ". The PC has a 1323 Power Monitor Parent, i.e. the switch port whose 1324 pmPowerMonitorId is "UUID 1000:3". The power usage of the PC is 1325 "120 Watts" and is communicated to the switch port. 1327 This example illustrates the important distinction between the 1328 Power Monitor Children: The IP phone draws power from the 1329 switch, while the PC has LAN connectivity from the phone, but is 1330 powered from the wall outlet. However, the Power Monitor Parent 1331 sends power control messages to both the Power Monitor Children 1332 (IP phone and PC) and the Children react to those messages. 1334 |--------------------------------------------------------------| 1335 | Switch | 1336 |==============================================================| 1337 | Switch | Switch | Switch | Switch | Switch | 1338 | pmPIndex | pmPhyIdx | pmPowerMonId | pmParentId | pmPower | 1339 | ============================================================ | 1340 | 1 | 2 | UUID 1000 | null | 440 | 1341 | ============================================================ | 1342 | | 1343 | SWITCH PORT | 1344 | ============================================================ | 1345 | | Switch | Switch | Switch | Switch | Switch | 1346 | | Port | Port | Port | Port | Port | | 1347 | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | 1348 | ============================================================ | 1349 | | 3 | 12 | UUID 1000:3 | UUID 1000 | 12 | | 1350 | ============================================================ | 1351 | ^ | 1352 | | | 1353 |-----------------------------------|--------------------------| 1354 | 1355 | 1356 POE IP PHONE | 1357 | 1358 | 1359 ============================================================= 1360 | IP phone | IP phone |IP phone |IP phone |IP phone| 1361 | pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower| 1362 =========================================================== 1363 | 31 | 0 | UUID 1000:31 | UUID 1000:3 | 12 | 1364 ============================================================ 1365 | 1366 | 1367 PC connected to switch via IP phone | 1368 | 1369 ============================================================= 1370 | PC | PC |PC |PC | PC | 1371 |pmPIndex| pmPhyIdx|pmPowerMonitorId|pmParentID| pmPower | 1372 ============================================================ 1373 | 57 | 0 | UUID 1000:57 | UUID 1000:3 | 120 | 1374 ============================================================= 1376 Figure 1: Example scenario 1378 9. Structure of the MIB 1380 The primary MIB object in this MIB module is the 1381 PowerMonitorMIBObject. The pmPowerTable table of 1382 PowerMonitorMibObject describes the power measurement attributes 1383 of a Power Monitor entity. The notion of identity of the device 1384 in terms of uniquely identification of the Power Monitor and its 1385 relationship to other entities in the network are addressed in 1386 [EMAN-AWARE-MIB]. 1388 The power measurement of Power Monitor contains information 1389 describing its power usage (pmPower) and its current power state 1390 (pmPowerOperState). In addition to power usage, additional 1391 information describing the units of measurement 1392 (pmPowerAccuracy, pmPowerUnitMultiplier), how power usage 1393 measurement was obtained (pmPowerMeasurementCaliber), the 1394 source of power (pmPowerOrigin) and the type of power 1395 (pmPowerCurrentTtype) are described. 1397 A Power Monitor may contain an optional pmPowerQuality table 1398 that describes the electrical characteristics associated with 1399 the current power state and usage. 1401 A Power Monitor may contain an optional pmEnergyTable to 1402 describe energy measurement information over time. 1404 A Power Monitor may also contain optional battery information 1405 associated with this entity. 1407 10. MIB Definitions 1409 -- ************************************************************ 1410 -- 1411 -- 1412 -- This MIB is used to monitor power usage of network 1413 -- devices 1414 -- 1415 -- ************************************************************* 1417 POWER-MONITOR-MIB DEFINITIONS ::= BEGIN 1419 IMPORTS 1420 MODULE-IDENTITY, 1421 OBJECT-TYPE, 1422 NOTIFICATION-TYPE, 1423 mib-2, 1424 Integer32, Counter64, TimeTicks 1425 FROM SNMPv2-SMI 1426 TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval 1427 FROM SNMPv2-TC 1428 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP 1429 FROM SNMPv2-CONF 1430 OwnerString 1431 FROM RMON-MIB; 1433 powerMonitorMIB MODULE-IDENTITY 1434 LAST-UPDATED "201107080000Z" -- 8 July 2011 1435 ORGANIZATION "IETF EMAN Working Group" 1436 CONTACT-INFO 1437 "WG charter: 1438 http://datatracker.ietf.org/wg/eman/charter/ 1440 Mailing Lists: 1441 General Discussion: eman@ietf.org 1443 To Subscribe: 1444 https://www.ietf.org/mailman/listinfo/eman 1446 Archive: 1447 http://www.ietf.org/mail-archive/web/eman 1449 Editors: 1450 Mouli Chandramouli 1451 Cisco Systems, Inc. 1452 Sarjapur Outer Ring Road 1453 Bangalore, 1454 IN 1455 Phone: +91 80 4426 3947 1456 Email: moulchan@cisco.com 1458 Brad Schoening 1459 44 Rivers Edge Drive 1460 Little Silver, NJ 07739 1461 US 1462 Email: brad@bradschoening.com 1464 Juergen Quittek 1465 NEC Europe Ltd. 1466 NEC Laboratories Europe 1467 Network Research Division 1468 Kurfuersten-Anlage 36 1469 Heidelberg 69115 1470 DE 1471 Phone: +49 6221 4342-115 1472 Email: quittek@neclab.eu 1474 Thomas Dietz 1475 NEC Europe Ltd. 1476 NEC Laboratories Europe 1477 Network Research Division 1478 Kurfuersten-Anlage 36 1479 69115 Heidelberg 1480 DE 1481 Phone: +49 6221 4342-128 1482 Email: Thomas.Dietz@nw.neclab.eu 1484 Benoit Claise 1485 Cisco Systems, Inc. 1486 De Kleetlaan 6a b1 1487 Degem 1831 1488 Belgium 1489 Phone: +32 2 704 5622 1490 Email: bclaise@cisco.com" 1492 DESCRIPTION 1493 "This MIB is used to monitor power and energy in 1494 devices." 1495 REVISION 1496 "201107080000Z" -- 8 July 2011 1497 DESCRIPTION 1498 "Initial version, published as RFC XXXX." 1500 ::= { mib-2 xxx } 1502 powerMonitorMIBNotifs OBJECT IDENTIFIER 1503 ::= { powerMonitorMIB 0 } 1505 powerMonitorMIBObjects OBJECT IDENTIFIER 1506 ::= { powerMonitorMIB 1 } 1508 powerMonitorMIBConform OBJECT IDENTIFIER 1509 ::= { powerMonitorMIB 2 } 1511 -- Textual Conventions 1513 PowerStateSet ::= TEXTUAL-CONVENTION 1514 STATUS current 1515 DESCRIPTION 1516 "PowerStateSet is a TC that describes the Power State 1517 Set a Power Monitor supports. IANA has created a 1518 registry of Power State Sets supported by a Power 1519 Monitor entity and IANA shall administer the list of 1520 Power State Sets. 1522 One byte is used to represent the Power State Set. 1524 field octets contents range 1525 ----- ------ -------- ----- 1526 1 1 Power State Set 1..255 1528 Note: 1529 the value of Power State Set in network byte order 1531 1 in the first byte indicates IEEE1621 Power State Set 1532 2 in the first byte indicates DMTF Power State Set 1533 3 in the first byte indicates EMAN Power State Set" 1535 REFERENCE 1536 "http://www.iana.org/assignments/eman 1537 RFC EDITOR NOTE: please change the previous URL 1538 if this is not the correct one after IANA assigned 1539 it." 1541 SYNTAX OCTET STRING (SIZE(1)) 1543 UnitMultiplier ::= TEXTUAL-CONVENTION 1544 STATUS current 1545 DESCRIPTION 1546 "The Unit Multiplier is an integer value that represents 1547 the IEEE 61850 Annex A units multiplier associated with 1548 the integer units used to measure the power or energy. 1550 For example, when used with pmPowerUnitMultiplier, -3 1551 represents 10^-3 or milliwatts." 1552 REFERENCE 1553 "The International System of Units (SI), 1554 National Institute of Standards and Technology, 1555 Spec. Publ. 330, August 1991." 1556 SYNTAX INTEGER { 1557 yocto(-24), -- 10^-24 1558 zepto(-21), -- 10^-21 1559 atto(-18), -- 10^-18 1560 femto(-15), -- 10^-15 1561 pico(-12), -- 10^-12 1562 nano(-9), -- 10^-9 1563 micro(-6), -- 10^-6 1564 milli(-3), -- 10^-3 1565 units(0), -- 10^0 1566 kilo(3), -- 10^3 1567 mega(6), -- 10^6 1568 giga(9), -- 10^9 1569 tera(12), -- 10^12 1570 peta(15), -- 10^15 1571 exa(18), -- 10^18 1572 zetta(21), -- 10^21 1573 yotta(24) -- 10^24 1574 } 1576 -- Objects 1578 pmPowerTable OBJECT-TYPE 1579 SYNTAX SEQUENCE OF PmPowerEntry 1580 MAX-ACCESS not-accessible 1581 STATUS current 1582 DESCRIPTION 1583 "This table lists Power Monitors." 1584 ::= { powerMonitorMIBObjects 1 } 1586 pmPowerEntry OBJECT-TYPE 1587 SYNTAX PmPowerEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "An entry describes the power usage of a Power Monitor." 1593 INDEX { pmPowerIndex, pmPowerStateSetIndex} 1594 ::= { pmPowerTable 1 } 1596 PmPowerEntry ::= SEQUENCE { 1597 pmPowerIndex Integer32, 1598 pmPowerStateSetIndex PowerStateSet, 1599 pmPower Integer32, 1600 pmPowerNameplate Integer32, 1601 pmPowerUnitMultiplier UnitMultiplier, 1602 pmPowerAccuracy Integer32, 1603 pmPowerMeasurementCaliber INTEGER, 1604 pmPowerCurrentType INTEGER, 1605 pmPowerOrigin INTEGER, 1606 pmPowerAdminState Integer32, 1607 pmPowerOperState Integer32, 1608 pmPowerStateEnterReason OwnerString 1609 } 1611 pmPowerIndex OBJECT-TYPE 1612 SYNTAX Integer32 (0..2147483647) 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "A unique value, for each Power Monitor. 1617 If an implementation of the ENERGY-AWARE-MIB module is 1618 available in the local SNMP context, then the same index 1619 as the one in the ENERGY-AWARE-MIB MUST be assigned for 1620 the identical Power Monitor. In this case, entities 1621 without an assigned value for pmIndex cannot be indexed 1622 by the pmPowerStateTable. 1624 If there is no implementation of the ENERGY-AWARE-MIB 1625 module but one of the ENTITY MIB module is available in 1626 the local SNMP context, then the same index of an entity 1627 MUST be chosen as assigned to the entity by object 1628 entPhysicalIndex in the ENTITY MIB module. In this case, 1629 entities without an assigned value for entPhysicalIndex 1630 cannot be indexed by the pmPowerStateTable. 1632 If neither the ENERGY-AWARE-MIB module nor of the ENTITY 1633 MIB module are available in the local SNMP context, then 1634 this MIB module may choose identity values from a further 1635 MIB module providing entity identities. In this case the 1636 value for each pmPowerIndex must remain constant at least 1637 from one re-initialization of the entity's network 1638 management system to the next re-initialization. 1640 In case that no other MIB modules have been chosen for 1641 providing entity identities, Power States can be reported 1642 exclusively for the local device on which this table is 1643 instantiated. Then this table will have a single entry 1644 only and an index value of 0 MUST be used." 1646 ::= { pmPowerEntry 1 } 1648 pmPowerStateSetIndex OBJECT-TYPE 1649 SYNTAX PowerStateSet 1650 MAX-ACCESS not-accessible 1651 STATUS current 1652 DESCRIPTION 1653 "This object indicates the Power State Set supported by 1654 the Power Monitor. The list of Power State Sets and 1655 their numbering are administered by IANA" 1656 ::= { pmPowerEntry 2 } 1658 pmPower OBJECT-TYPE 1659 SYNTAX Integer32 1660 UNITS "Watts" 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "This object indicates the 'instantaneous' RMS 1665 consumption for the Power Monitor. This value is 1666 specified in SI units of watts with the magnitude of 1667 watts (milliwatts, kilowatts, etc.) indicated separately 1668 in pmPowerUnitMultiplier. The accuracy of the measurement 1669 is specfied in pmPowerAccuracy. The direction of power 1670 flow is indicated by the sign on pmPower. If the Power 1671 Monitor is consuming power, the pmPower value will be 1672 positive. If the Power Monitor is producing power, the 1673 pmPower value will be negative. 1675 The pmPower MUST be less than or equal to the maximum 1676 power that can be consumed at the power state specified 1677 by pmPowerState. 1679 The pmPowerMeasurementCaliber object specifies how the 1680 usage value reported by pmPower was obtained. The pmPower 1681 value must report 0 if the pmPowerMeasurementCaliber is 1682 'unavailable'. For devices that can not measure or 1683 report power, this option can be used." 1684 ::= { pmPowerEntry 3 } 1686 pmPowerNameplate OBJECT-TYPE 1687 SYNTAX Integer32 1688 UNITS "Watts" 1689 MAX-ACCESS read-only 1690 STATUS current 1691 DESCRIPTION 1692 "This object indicates the rated maximum consumption for 1693 the fully populated Power Monitor. The nameplate power 1694 requirements are the maximum power numbers and, in almost 1695 all cases, are well above the expected operational 1696 consumption. The pmPowerNameplate is widely used for 1697 power provisioning. This value is specified in either 1698 units of watts or voltage and current. The units are 1699 therefore SI watts or equivalent Volt-Amperes with the 1700 magnitude (milliwatts, kilowatts, etc.) indicated 1701 separately in pmPowerUnitMultiplier." 1702 ::= { pmPowerEntry 4 } 1704 pmPowerUnitMultiplier OBJECT-TYPE 1705 SYNTAX UnitMultiplier 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The magnitude of watts for the usage value in pmPower 1710 and pmPowerNameplate." 1711 ::= { pmPowerEntry 5 } 1713 pmPowerAccuracy OBJECT-TYPE 1714 SYNTAX Integer32 (0..10000) 1715 UNITS "hundredths of percent" 1716 MAX-ACCESS read-only 1717 STATUS current 1718 DESCRIPTION 1719 "This object indicates a percentage value, in 100ths of a 1720 percent, representing the assumed accuracy of the usage 1721 reported by pmPower. For example: The value 1010 means 1722 the reported usage is accurate to +/- 10.1 percent. This 1723 value is zero if the accuracy is unknown or not 1724 applicable based upon the measurement method. 1726 ANSI and IEC define the following accuracy classes for 1727 power measurement: 1728 IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. 1729 ANSI C12.20 class 0.2, 0.5" 1730 ::= { pmPowerEntry 6 } 1732 pmPowerMeasurementCaliber OBJECT-TYPE 1733 SYNTAX INTEGER { 1734 unavailable(1) , 1735 unknown(2), 1736 actual(3) , 1737 estimated(4), 1738 presumed(5) } 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "This object specifies how the usage value reported by 1743 pmPower was obtained: 1745 - unavailable(1): Indicates that the usage is not 1746 available. In such a case, the pmPower value must be 0 1747 For devices that can not measure or report power this 1748 option can be used. 1750 - unknown(2): Indicates that the way the usage was 1751 determined is unknown. In some cases, entities report 1752 aggregate power on behalf of another device. In such 1753 cases it is not known whether the usage reported is 1754 actual(2), estimated(3) or presumed (4). 1756 - actual(3): Indicates that the reported usage was 1757 measured by the entity through some hardware or direct 1758 physical means. The usage data reported is not presumed 1759 (4) or estimated (3) but the real apparent current energy 1760 consumption rate. 1762 - estimated(4): Indicates that the usage was not 1763 determined by physical measurement. The value is a 1764 derivation based upon the device type, state, and/or 1765 current utilization using some algorithm or heuristic. It 1766 is presumed that the entity's state and current 1767 configuration were used to compute the value. 1769 - presumed(5): Indicates that the usage was not 1770 determined by physical measurement, algorithm or 1771 derivation. The usage was reported based upon external 1772 tables, specifications, and/or model information. For 1773 example, a PC Model X draws 200W, while a PC Model Y 1774 draws 210W" 1776 ::= { pmPowerEntry 7 } 1778 pmPowerCurrentType OBJECT-TYPE 1779 SYNTAX INTEGER { 1780 ac(1), 1781 dc(2), 1782 unknown(3) 1783 } 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "This object indicates whether the pmUsage for the Power 1788 Monitor reports alternative current AC(1), direct current 1789 DC(2), or that the current type is unknown(3)." 1790 ::= { pmPowerEntry 8 } 1792 pmPowerOrigin OBJECT-TYPE 1793 SYNTAX INTEGER { 1794 self (1), 1795 remote (2) 1796 } 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "This object indicates the source of power measurement 1801 and can be useful when modeling the power usage of 1802 attached devices. The power measurement can be performed 1803 by the entity itself or the power measurement of the 1804 entity can be reported by another trusted entity using a 1805 protocol extension. A value of self(1) indicates the 1806 measurement is performed by the entity, whereas remote(2) 1807 indicates that the measurement was performed by another 1808 entity." 1809 ::= { pmPowerEntry 9 } 1811 pmPowerAdminState OBJECT-TYPE 1812 SYNTAX Integer32 (1..65535) 1813 MAX-ACCESS read-write 1814 STATUS current 1815 DESCRIPTION 1816 "This object specifies the desired Power State for the 1817 Power Monitor, in the context of the Power State Set 1818 specified by pmPowerStateSetIndex in this table. 1819 Possible values of pmPowerAdminState are registered at 1820 IANA, per Power States Set. A current list of 1821 assignments can be found at 1822 1823 RFC-EDITOR: please check the location after IANA" 1825 ::= { pmPowerEntry 10 } 1827 pmPowerOperState OBJECT-TYPE 1828 SYNTAX Integer32 (1..65535) 1829 MAX-ACCESS read-only 1830 STATUS current 1831 DESCRIPTION 1832 "This object specifies the current operational Power 1833 State for the Power Monitor, in the context of the Power 1834 State Set specified by pmPowerStateSetIndex in this 1835 table. Possible values of pmPowerOperState are 1836 registered at IANA, per Power States Set. A current 1837 list of assignments can be found at 1838 1839 RFC-EDITOR: please check the list" 1840 ::= { pmPowerEntry 11 } 1842 pmPowerStateEnterReason OBJECT-TYPE 1843 SYNTAX OwnerString 1844 MAX-ACCESS read-create 1845 STATUS current 1846 DESCRIPTION 1847 "This string object describes the reason for the 1848 pmPowerAdminState 1849 transition Alternatively, this string may contain with 1850 the entity that configured this Power Monitor to this 1851 Power State." 1852 DEFVAL { "" } 1853 ::= { pmPowerEntry 12 } 1855 pmPowerStateTable OBJECT-TYPE 1856 SYNTAX SEQUENCE OF PmPowerStateEntry 1857 MAX-ACCESS not-accessible 1858 STATUS current 1859 DESCRIPTION 1860 "This table enumerates the maximum power usage, in watts, 1861 for every single supported Power State of each Power 1862 Monitor. 1864 This table has an expansion-dependent relationship on the 1865 pmPowerTable, containing rows describing each Power State 1866 for the corresponding Power Monitor. For every Power 1867 Monitor in the pmPowerTable, there is a corresponding 1868 entry in this table." 1869 ::= { powerMonitorMIBObjects 2 } 1871 pmPowerStateEntry OBJECT-TYPE 1872 SYNTAX PmPowerStateEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "A pmPowerStateEntry extends a corresponding 1877 pmPowerEntry. This entry displays max usage values at 1878 every single possible Power State supported by the Power 1879 Monitor. 1880 For example, given the values of a Power Monitor 1881 corresponding to a maximum usage of 11W at the 1882 state 1 (mechoff), 6 (ready), 8 (mediumMinus), 12 (High): 1884 State MaxUsage Units 1885 1 (mechoff 0 W 1886 2 (softoff) 0 W 1887 3 (hibernate) 0 W 1888 4 (sleep) 0 W 1889 5 (standby) 0 W 1890 6 (ready) 8 W 1891 7 (lowMinus) 8 W 1892 8 (low) 11 W 1893 9 (medimMinus) 11 W 1894 10 (medium) 11 W 1895 11 (highMinus) 11 W 1896 12 (high) 11 W 1898 Furthermore, this table extends to return the total time 1899 in each Power State, along with the number of times a 1900 particular Power State was entered." 1902 INDEX { 1903 pmPowerIndex, 1904 pmPowerStateSetIndex, 1905 pmPowerStateIndex 1907 } 1908 ::= { pmPowerStateTable 1 } 1910 PmPowerStateEntry ::= SEQUENCE { 1911 pmPowerStateIndex Integer32, 1912 pmPowerStateMaxPower Integer32, 1913 pmPowerStatePowerUnitMultiplier UnitMultiplier, 1914 pmPowerStateTotalTime TimeTicks, 1915 pmPowerStateEnterCount Counter64 1916 } 1918 pmPowerStateIndex OBJECT-TYPE 1919 SYNTAX Integer32 (1..65535) 1920 MAX-ACCESS not-accessible 1921 STATUS current 1922 DESCRIPTION 1923 "This object specifies the Power State for the Power 1924 Monitor, in the context of the Power State Set specified 1925 by pmPowerStateSetIndex in this table. 1927 This object specifies the index of the Power State of 1928 the Power Monitor within a Power State Set. The 1929 semantics of the specific Power State can be obtained 1930 from the Power State Set definition." 1931 ::= { pmPowerStateEntry 1 } 1933 pmPowerStateMaxPower OBJECT-TYPE 1934 SYNTAX Integer32 1935 UNITS "Watts" 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "This object indicates the maximum power for the Power 1940 Monitor at the particular Power State. This value is 1941 specified in SI units of watts with the magnitude of the 1942 units (milliwatts, kilowatts, etc.) indicated separately 1943 in pmPowerStatePowerUnitMultiplier. If the maximum power 1944 is not known for a certain Power State, then the value is 1945 encoded as 0xFFFF. 1947 For Power States not enumerated, the value of 1948 pmPowerStateMaxPower might be interpolated by using the 1949 next highest supported Power State." 1950 ::= { pmPowerStateEntry 3 } 1952 pmPowerStatePowerUnitMultiplier OBJECT-TYPE 1953 SYNTAX UnitMultiplier 1954 MAX-ACCESS read-only 1955 STATUS current 1956 DESCRIPTION 1957 "The magnitude of watts for the usage value in 1958 pmPowerStateMaxPower." 1959 ::= { pmPowerStateEntry 4 } 1961 pmPowerStateTotalTime OBJECT-TYPE 1962 SYNTAX TimeTicks 1963 MAX-ACCESS read-only 1964 STATUS current 1965 DESCRIPTION 1966 "This object indicates the total time in hundreds 1967 of seconds that the Power Monitor has been in this power 1968 state since the last reset, as specified in the 1969 sysUpTime." 1970 ::= { pmPowerStateEntry 5 } 1972 pmPowerStateEnterCount OBJECT-TYPE 1973 SYNTAX Counter64 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "This object indicates how often the Power Monitor has 1978 entered this power state, since the last reset of the 1979 device as specified in the sysUpTime." 1980 ::= { pmPowerStateEntry 6 } 1982 pmEnergyParametersTable OBJECT-TYPE 1983 SYNTAX SEQUENCE OF PmEnergyParametersEntry 1984 MAX-ACCESS not-accessible 1985 STATUS current 1986 DESCRIPTION 1987 "This table is used to configure the parameters for Energy 1988 measurement collection in the table pmEnergyTable." 1989 ::= { powerMonitorMIBObjects 4 } 1991 pmEnergyParametersEntry OBJECT-TYPE 1992 SYNTAX PmEnergyParametersEntry 1993 MAX-ACCESS not-accessible 1994 STATUS current 1995 DESCRIPTION 1996 "An entry controls an energy measurement in 1997 pmEnergyTable." 1998 INDEX { pmPowerIndex } 1999 ::= { pmEnergyParametersTable 1 } 2001 PmEnergyParametersEntry ::= SEQUENCE { 2002 pmEnergyParametersIntervalLength TimeInterval, 2003 pmEnergyParametersIntervalNumber Integer32, 2004 pmEnergyParametersIntervalMode Integer32, 2005 pmEnergyParametersIntervalWindow TimeInterval, 2006 pmEnergyParametersSampleRate Integer32, 2007 pmEnergyParametersStatus RowStatus 2008 } 2010 pmEnergyParametersIntervalLength OBJECT-TYPE 2011 SYNTAX TimeInterval 2012 UNITS "Seconds" 2013 MAX-ACCESS read-create 2014 STATUS current 2015 DESCRIPTION 2016 "This object indicates the length of time in seconds over 2017 which to compute the average pmEnergyIntervalEnergyUsed 2018 measurement in the pmEnergyTable table. The computation 2019 is based on the Power Monitor's internal sampling rate of 2020 power consumed or produced by the Power Monitor. The 2021 sampling rate is the rate at which the power monitor can 2022 read the power usage and may differ based on device 2023 capabilities. The average energy consumption is then 2024 computed over the length of the interval." 2025 DEFVAL { 900 } 2026 ::= { pmEnergyParametersEntry 1 } 2028 pmEnergyParametersIntervalNumber OBJECT-TYPE 2029 SYNTAX Integer32 2030 MAX-ACCESS read-create 2031 STATUS current 2032 DESCRIPTION 2033 "The number of intervals maintained in the pmEnergyTable. 2034 Each interval is characterized by a specific 2035 pmEnergyIntervalStartTime, used as an index to the table 2036 pmEnergyTable . Whenever the maximum number of entries is 2037 reached, the measurement over the new interval replaces 2038 the oldest measurement , except if the oldest measurement 2039 were to be the maximum pmEnergyIntervalMax, in which case 2040 the measurement the measurement over the next oldest 2041 interval is replaced." 2042 DEFVAL { 10 } 2043 ::= { pmEnergyParametersEntry 2 } 2045 pmEnergyParametersIntervalMode OBJECT-TYPE 2046 SYNTAX INTEGER { 2047 period(1), 2048 sliding(2), 2049 total(3) 2050 } 2051 MAX-ACCESS read-create 2052 STATUS current 2053 DESCRIPTION 2054 "A control object to define the mode of interval calculation 2055 for the computation of the average 2056 pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable 2057 table. 2058 A mode of period(1) specifies non-overlapping periodic 2059 measurements. 2061 A mode of sliding(2) specifies overlapping sliding windows 2062 where the interval between the start of one interval and 2063 the next is defined in pmEnergyParametersIntervalWindow. 2065 A mode of total(3) specifies non-periodic measurement. In 2066 this mode only one interval is used as this is a 2067 continuous measurement since the last reset. The value of 2068 pmEnergyParametersIntervalNumber should be (1) one and 2069 pmEnergyParametersIntervalLength is ignored. " 2070 ::= { pmEnergyParametersEntry 3 } 2072 pmEnergyParametersIntervalWindow OBJECT-TYPE 2073 SYNTAX TimeInterval 2074 UNITS "Seconds" 2075 MAX-ACCESS read-create 2076 STATUS current 2077 DESCRIPTION 2078 "The length of the duration window between the starting 2079 time of one sliding window and the next starting time in 2080 seconds, in order to compute the average 2081 pmEnergyIntervalEnergyUsed measurement in the pmEnergyTable 2082 table This is valid only when the 2083 pmEnergyParametersIntervalMode is sliding(2). The 2084 pmEnergyParametersIntervalWindow value should be a multiple 2085 of pmEnergyParametersSampleRate." 2086 ::= { pmEnergyParametersEntry 4 } 2088 pmEnergyParametersSampleRate OBJECT-TYPE 2089 SYNTAX Integer32 2090 UNITS "Milliseconds" 2091 MAX-ACCESS read-create 2092 STATUS current 2093 DESCRIPTION 2094 "The sampling rate, in milliseconds, at which the Power 2095 Monitor should poll power usage in order to compute the 2096 average pmEnergyIntervalEnergyUsed measurement in the 2097 table pmEnergyTable. The Power Monitor should initially 2098 set this sampling rate to a reasonable value, i.e., a 2099 compromise between intervals that will provide good 2100 accuracy by not being too long, but not so short that 2101 they affect the Power Monitor performance by requesting 2102 continuous polling. If the sampling rate is unknown, the 2103 value 0 is reported. The sampling rate should be selected 2104 so that pmEnergyParametersIntervalWindow is a multiple of 2105 pmEnergyParametersSampleRate." 2106 DEFVAL { 1000 } 2107 ::= { pmEnergyParametersEntry 5 } 2109 pmEnergyParametersStatus OBJECT-TYPE 2110 SYNTAX RowStatus 2111 MAX-ACCESS read-create 2112 STATUS current 2113 DESCRIPTION 2114 "The status of this row. The pmEnergyParametersStatus is 2115 used to start or stop energy usage logging. An entry 2116 status may not be active(1) unless all objects in the 2117 entry have an appropriate value. If this object is not 2118 equal to active(1), all associated usage-data logged into 2119 the pmEnergyTable will be deleted. The data can be 2120 destroyed by setting up the pmEnergyParametersStatus to 2121 destroy(2)." 2122 ::= {pmEnergyParametersEntry 6 } 2124 pmEnergyTable OBJECT-TYPE 2125 SYNTAX SEQUENCE OF PmEnergyIntervalEntry 2126 MAX-ACCESS not-accessible 2127 STATUS current 2128 DESCRIPTION 2129 "This table lists Power Monitor energy measurements. 2130 Entries in this table are only created if the 2131 corresponding value of object pmPowerMeasurementCaliber 2132 is active(2), i.e., if the power is actually metered." 2133 ::= { powerMonitorMIBObjects 5 } 2135 pmEnergyIntervalEntry OBJECT-TYPE 2136 SYNTAX PmEnergyIntervalEntry 2137 MAX-ACCESS not-accessible 2138 STATUS current 2139 DESCRIPTION 2140 "An entry describing energy measurements." 2141 INDEX { pmPowerIndex, pmEnergyParametersIntervalMode, 2142 pmEnergyIntervalStartTime } 2143 ::= { pmEnergyTable 1 } 2145 PmEnergyIntervalEntry ::= SEQUENCE { 2146 pmEnergyIntervalStartTime TimeTicks, 2147 pmEnergyIntervalEnergyUsed Integer32, 2148 pmEnergyIntervalEnergyUnitMultiplier UnitMultiplier, 2149 pmEnergyIntervalMax Integer32, 2150 pmEnergyIntervalDiscontinuityTime TimeTicks 2151 } 2153 pmEnergyIntervalStartTime OBJECT-TYPE 2154 SYNTAX TimeTicks 2155 UNITS "hundredths of seconds" 2156 MAX-ACCESS not-accessible 2157 STATUS current 2158 DESCRIPTION 2159 "The time (in hundredths of a second) since the 2160 network management portion of the system was last 2161 re-initialized, as specified in the sysUpTime [RFC3418]. 2162 This object is useful for reference of interval periods 2163 for which the energy is measured." 2164 ::= { pmEnergyIntervalEntry 1 } 2166 pmEnergyIntervalEnergyUsed OBJECT-TYPE 2167 SYNTAX Integer32 2168 UNITS "Watt-hours" 2169 MAX-ACCESS read-only 2170 STATUS current 2171 DESCRIPTION 2172 "This object indicates the energy used in units of watt- 2173 hours for the Power Monitor over the defined interval. 2174 This value is specified in the common billing units of 2175 watt-hours with the magnitude of watt-hours (kW-Hr, MW- 2176 Hr, etc.) indicated separately in 2177 pmEnergyIntervalEnergyUnitMultiplier." 2178 ::= { pmEnergyIntervalEntry 2 } 2180 pmEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE 2181 SYNTAX UnitMultiplier 2182 MAX-ACCESS read-only 2183 STATUS current 2184 DESCRIPTION 2185 "This object is the magnitude of watt-hours for the 2186 energy field in pmEnergyIntervalEnergyUsed." 2187 ::= { pmEnergyIntervalEntry 3 } 2189 pmEnergyIntervalMax OBJECT-TYPE 2190 SYNTAX Integer32 2191 UNITS "Watt-hours" 2192 MAX-ACCESS read-only 2193 STATUS current 2194 DESCRIPTION 2195 "This object is the maximum energy ever observed in 2196 pmEnergyIntervalEnergyUsed since the monitoring started. 2197 This value is specified in the common billing units of 2198 watt-hours with the magnitude of watt-hours (kW-Hr, MW- 2199 Hr, etc.) indicated separately in 2200 pmEnergyIntervalEnergyUnits." 2201 ::= { pmEnergyIntervalEntry 4 } 2203 pmEnergyIntervalDiscontinuityTime OBJECT-TYPE 2204 SYNTAX TimeTicks 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "The value of sysUpTime [RFC3418] on the most recent 2209 occasion at which any one or more of this entity's energy 2210 consumption counters suffered a discontinuity. If no such 2211 discontinuities have occurred since the last re- 2212 initialization of the local management subsystem, then 2213 this object contains a zero value." 2214 ::= { pmEnergyIntervalEntry 5 } 2216 -- Notifications 2218 pmPowerStateChange NOTIFICATION-TYPE 2219 OBJECTS {pmPowerAdminState, pmPowerOperState, 2220 pmPowerStateEnterReason} 2221 STATUS current 2222 DESCRIPTION 2223 "The SNMP entity generates the PmPowerStateChange when 2224 the value(s) of pmPowerAdminState or pmPowerOperState, 2225 in the context of the Power State Set, have changed for 2226 the Power Monitor represented by the pmPowerIndex." 2227 ::= { powerMonitorMIBNotifs 1 } 2229 -- Conformance 2231 powerMonitorMIBCompliances OBJECT IDENTIFIER 2232 ::= { powerMonitorMIB 3 } 2234 powerMonitorMIBGroups OBJECT IDENTIFIER 2235 ::= { powerMonitorMIB 4 } 2237 powerMonitorMIBFullCompliance MODULE-COMPLIANCE 2238 STATUS current 2239 DESCRIPTION 2240 "When this MIB is implemented with support for 2241 read-create, then such an implementation can 2242 claim full compliance. Such devices can then 2243 be both monitored and configured with this MIB." 2244 MODULE -- this module 2245 MANDATORY-GROUPS { 2246 powerMonitorMIBTableGroup, 2247 powerMonitorMIBStateTableGroup, 2248 powerMonitorMIBEnergyTableGroup, 2249 powerMonitorMIBEnergyParametersTableGroup, 2250 powerMonitorMIBNotifGroup 2251 } 2252 ::= { powerMonitorMIBCompliances 1 } 2254 powerMonitorMIBReadOnlyCompliance MODULE-COMPLIANCE 2255 STATUS current 2256 DESCRIPTION 2257 "When this MIB is implemented without support for 2258 read-create (i.e. in read-only mode), then such an 2259 implementation can claim read-only compliance. Such a 2260 device can then be monitored but can not be configured 2261 with this MIB." 2262 MODULE -- this module 2263 MANDATORY-GROUPS { 2264 powerMonitorMIBTableGroup, 2265 powerMonitorMIBStateTableGroup, 2266 powerMonitorMIBNotifGroup 2267 } 2269 OBJECT pmPowerOperState 2270 MIN-ACCESS read-only 2271 DESCRIPTION 2272 "Write access is not required." 2273 ::= { powerMonitorMIBCompliances 2 } 2275 -- Units of Conformance 2277 powerMonitorMIBTableGroup OBJECT-GROUP 2278 OBJECTS { 2279 pmPower, 2280 pmPowerNameplate, 2281 pmPowerUnitMultiplier, 2282 pmPowerAccuracy, 2283 pmPowerMeasurementCaliber, 2284 pmPowerCurrentType, 2285 pmPowerOrigin, 2286 pmPowerAdminState, 2287 pmPowerOperState, 2288 pmPowerStateEnterReason 2289 } 2290 STATUS current 2291 DESCRIPTION 2292 "This group contains the collection of all the objects 2293 related to the PowerMonitor." 2294 ::= { powerMonitorMIBGroups 1 } 2296 powerMonitorMIBStateTableGroup OBJECT-GROUP 2297 OBJECTS { 2298 pmPowerStateMaxPower, 2299 pmPowerStatePowerUnitMultiplier, 2300 pmPowerStateTotalTime, 2301 pmPowerStateEnterCount 2303 } 2304 STATUS current 2305 DESCRIPTION 2306 "This group contains the collection of all the 2307 objects related to the Power State." 2308 ::= { powerMonitorMIBGroups 2 } 2310 powerMonitorMIBEnergyParametersTableGroup OBJECT-GROUP 2311 OBJECTS { 2312 pmEnergyParametersIntervalLength, 2313 pmEnergyParametersIntervalNumber, 2314 pmEnergyParametersIntervalMode, 2315 pmEnergyParametersIntervalWindow, 2316 pmEnergyParametersSampleRate, 2317 pmEnergyParametersStatus 2318 } 2319 STATUS current 2320 DESCRIPTION 2321 "This group contains the collection of all the objects 2322 related to the configuration of the Energy Table." 2323 ::= { powerMonitorMIBGroups 3 } 2325 powerMonitorMIBEnergyTableGroup OBJECT-GROUP 2326 OBJECTS { 2327 -- Note that object 2328 -- pmEnergyIntervalStartTime is not 2329 -- included since it is not-accessible 2331 pmEnergyIntervalEnergyUsed, 2332 pmEnergyIntervalEnergyUnitMultiplier, 2333 pmEnergyIntervalMax, 2334 pmEnergyIntervalDiscontinuityTime 2335 } 2336 STATUS current 2337 DESCRIPTION 2338 "This group contains the collection of all the objects 2339 related to the Energy Table." 2340 ::= { powerMonitorMIBGroups 4 } 2342 powerMonitorMIBNotifGroup NOTIFICATION-GROUP 2343 NOTIFICATIONS { 2344 pmPowerStateChange 2345 } 2346 STATUS current 2347 DESCRIPTION 2348 "This group contains the notifications for the power and 2349 energy monitoring MIB Module." 2350 ::= { powerMonitorMIBGroups 5 } 2352 END 2354 -- ************************************************************ 2355 -- 2356 -- This MIB module is used to monitor power quality of networked 2357 -- devices with measurements. 2358 -- 2359 -- This MIB module is an extension of powerMonitorMIB module. 2360 -- 2361 -- ************************************************************* 2363 POWER-QUALITY-MIB DEFINITIONS ::= BEGIN 2365 IMPORTS 2366 MODULE-IDENTITY, 2367 OBJECT-TYPE, 2368 mib-2, 2369 Integer32 2370 FROM SNMPv2-SMI 2371 MODULE-COMPLIANCE, 2372 OBJECT-GROUP 2373 FROM SNMPv2-CONF 2374 UnitMultiplier, pmPowerIndex 2375 FROM POWER-MONITOR-MIB 2376 OwnerString 2377 FROM RMON-MIB; 2379 powerQualityMIB MODULE-IDENTITY 2381 LAST-UPDATED "201107080000Z" -- 8 July 2011 2382 ORGANIZATION "IETF EMAN Working Group" 2383 CONTACT-INFO 2384 "WG charter: 2385 http://datatracker.ietf.org/wg/eman/charter/ 2387 Mailing Lists: 2388 General Discussion: eman@ietf.org 2390 To Subscribe: 2391 https://www.ietf.org/mailman/listinfo/eman 2392 Archive: 2393 http://www.ietf.org/mail-archive/web/eman 2395 Editors: 2397 Mouli Chandramouli 2398 Cisco Systems, Inc. 2399 Sarjapur Outer Ring Road 2400 Bangalore, 2401 IN 2402 Phone: +91 80 4426 3947 2403 Email: moulchan@cisco.com 2405 Brad Schoening 2406 44 Rivers Edge Drive 2407 Little Silver, NJ 07739 2408 US 2409 Email: brad@bradschoening.com 2411 Juergen Quittek 2412 NEC Europe Ltd. 2413 NEC Laboratories Europe 2414 Network Research Division 2415 Kurfuersten-Anlage 36 2416 Heidelberg 69115 2417 DE 2418 Phone: +49 6221 4342-115 2419 Email: quittek@neclab.eu 2421 Thomas Dietz 2422 NEC Europe Ltd. 2423 NEC Laboratories Europe 2424 Network Research Division 2425 Kurfuersten-Anlage 36 2426 69115 Heidelberg 2427 DE 2428 Phone: +49 6221 4342-128 2429 Email: Thomas.Dietz@nw.neclab.eu 2431 Benoit Claise 2432 Cisco Systems, Inc. 2433 De Kleetlaan 6a b1 2434 Degem 1831 2435 Belgium 2436 Phone: +32 2 704 5622 2437 Email: bclaise@cisco.com" 2439 DESCRIPTION 2440 "This MIB is used to report AC power quality in 2441 devices. The table is a sparse augmentation of the 2442 pmPowerTable table from the powerMonitorMIB module. 2443 Both three-phase and single-phase power 2444 configurations are supported." 2445 REVISION 2447 "201107080000Z" -- 8 July 2011 2449 DESCRIPTION 2450 "Initial version, published as RFC YYY." 2452 ::= { mib-2 yyy } 2454 powerQualityMIBConform OBJECT IDENTIFIER 2455 ::= { powerQualityMIB 0 } 2457 powerQualityMIBObjects OBJECT IDENTIFIER 2458 ::= { powerQualityMIB 1 } 2460 -- Objects 2462 pmACPwrQualityTable OBJECT-TYPE 2463 SYNTAX SEQUENCE OF PmACPwrQualityEntry 2464 MAX-ACCESS not-accessible 2465 STATUS current 2466 DESCRIPTION 2467 "This table defines power quality measurements for 2468 supported pmPowerIndex entities. It is a sparse 2469 extension of the pmPowerTable." 2470 ::= { powerQualityMIBObjects 1 } 2472 pmACPwrQualityEntry OBJECT-TYPE 2473 SYNTAX PmACPwrQualityEntry 2474 MAX-ACCESS not-accessible 2475 STATUS current 2476 DESCRIPTION 2477 "This is a sparse extension of the pmPowerTable with 2478 entries for power quality measurements or 2479 configuration. Each measured value corresponds to an 2480 attribute in IEC 61850-7-4 for non-phase measurements 2481 within the object MMUX." 2482 INDEX { pmPowerIndex } 2483 ::= { pmACPwrQualityTable 1 } 2485 PmACPwrQualityEntry ::= SEQUENCE { 2486 pmACPwrQualityConfiguration INTEGER, 2487 pmACPwrQualityAvgVoltage Integer32, 2488 pmACPwrQualityAvgCurrent Integer32, 2489 pmACPwrQualityFrequency Integer32, 2490 pmACPwrQualityPowerUnitMultiplier UnitMultiplier, 2491 pmACPwrQualityPowerAccuracy Integer32, 2492 pmACPwrQualityTotalActivePower Integer32, 2493 pmACPwrQualityTotalReactivePower Integer32, 2494 pmACPwrQualityTotalApparentPower Integer32, 2495 pmACPwrQualityTotalPowerFactor Integer32, 2496 pmACPwrQualityThdAmpheres Integer32, 2497 pmACPwrQualityThdVoltage Integer32 2498 } 2500 pmACPwrQualityConfiguration OBJECT-TYPE 2501 SYNTAX INTEGER { 2502 sngl(1), 2503 del(2), 2504 wye(3) 2505 } 2506 MAX-ACCESS read-only 2507 STATUS current 2508 DESCRIPTION 2509 "Configuration describes the physical configurations 2510 of the power supply lines: 2512 * alternating current, single phase (SNGL) 2513 * alternating current, three phase delta (DEL) 2514 * alternating current, three phase Y (WYE) 2516 Three-phase configurations can be either connected in 2517 a triangular delta (DEL) or star Y (WYE) system. WYE 2518 systems have a shared neutral voltage, while DEL 2519 systems do not. Each phase is offset 120 degrees to 2520 each other." 2521 ::= { pmACPwrQualityEntry 1 } 2523 pmACPwrQualityAvgVoltage OBJECT-TYPE 2524 SYNTAX Integer32 2525 UNITS "0.1 Volt AC" 2526 MAX-ACCESS read-only 2527 STATUS current 2528 DESCRIPTION 2529 "A measured value for average 'instantaneous' RMS line 2530 voltage. For a 3-phase system, this is the average 2531 voltage (V1+V2+V3)/3. IEC 61850-7-4 measured value 2532 attribute 'Vol'" 2534 ::= { pmACPwrQualityEntry 2 } 2536 pmACPwrQualityAvgCurrent OBJECT-TYPE 2537 SYNTAX Integer32 2538 UNITS "Ampheres" 2539 MAX-ACCESS read-only 2540 STATUS current 2541 DESCRIPTION 2542 "A measured value of the current per phase. IEC 61850- 2543 7-4 attribute 'Amp'" 2544 ::= { pmACPwrQualityEntry 3 } 2546 pmACPwrQualityFrequency OBJECT-TYPE 2547 SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz 2548 UNITS "hertz" 2549 MAX-ACCESS read-only 2550 STATUS current 2551 DESCRIPTION 2552 "A measured value for the basic frequency of the AC 2553 circuit. IEC 61850-7-4 attribute 'Hz'." 2554 ::= { pmACPwrQualityEntry 4 } 2556 pmACPwrQualityPowerUnitMultiplier OBJECT-TYPE 2557 SYNTAX UnitMultiplier 2558 MAX-ACCESS read-only 2559 STATUS current 2560 DESCRIPTION 2561 "The magnitude of watts for the usage value in 2562 pmACPwrQualityTotalActivePower, 2563 pmACPwrQualityTotalReactivePower 2564 and pmACPwrQualityTotalApparentPower measurements. For 2565 3-phase power systems, this will also include 2566 pmACPwrQualityPhaseActivePower, 2567 pmACPwrQualityPhaseReactivePower and 2568 pmACPwrQualityPhaseApparentPower" 2569 ::= { pmACPwrQualityEntry 5 } 2571 pmACPwrQualityPowerAccuracy OBJECT-TYPE 2572 SYNTAX Integer32 (0..10000) 2573 UNITS "hundredths of percent" 2574 MAX-ACCESS read-only 2575 STATUS current 2576 DESCRIPTION 2577 "This object indicates a percentage value, in 100ths of 2578 a percent, representing the presumed accuracy of 2579 active, reactive, and apparent power usage reporting. 2580 For example: 1010 means the reported usage is accurate 2581 to +/- 10.1 percent. This value is zero if the 2582 accuracy is unknown. 2584 ANSI and IEC define the following accuracy classes for 2585 power measurement: IEC 62053-22 & 60044-1 class 0.1, 2586 0.2, 0.5, 1 & 3. 2587 ANSI C12.20 class 0.2 & 0.5" 2588 ::= { pmACPwrQualityEntry 6 } 2590 pmACPwrQualityTotalActivePower OBJECT-TYPE 2591 SYNTAX Integer32 2592 UNITS "RMS watts" 2593 MAX-ACCESS read-only 2594 STATUS current 2595 DESCRIPTION 2596 "A measured value of the actual power delivered to or 2597 consumed by the load. IEC 61850-7-4 attribute 'TotW'." 2598 ::= { pmACPwrQualityEntry 7 } 2600 pmACPwrQualityTotalReactivePower OBJECT-TYPE 2601 SYNTAX Integer32 2602 UNITS "volt-amperes reactive" 2603 MAX-ACCESS read-only 2604 STATUS current 2605 DESCRIPTION 2606 "A mesured value of the reactive portion of the 2607 apparent power. IEC 61850-7-4 attribute 'TotVAr'." 2608 ::= { pmACPwrQualityEntry 8 } 2610 pmACPwrQualityTotalApparentPower OBJECT-TYPE 2611 SYNTAX Integer32 2612 UNITS "volt-amperes" 2613 MAX-ACCESS read-only 2614 STATUS current 2615 DESCRIPTION 2616 "A measured value of the voltage and current which 2617 determines the apparent power. The apparent power is 2618 the vector sum of real and reactive power. 2620 Note: watts and volt-ampheres are equivalent units and 2621 may be combined. IEC 61850-7-4 attribute 'TotVA'." 2622 ::= { pmACPwrQualityEntry 9 } 2624 pmACPwrQualityTotalPowerFactor OBJECT-TYPE 2625 SYNTAX Integer32 (-10000..10000) 2626 UNITS "hundredths of percent" 2627 MAX-ACCESS read-only 2628 STATUS current 2629 DESCRIPTION 2630 "A measured value ratio of the real power flowing to 2631 the load versus the apparent power. It is dimensionless 2632 and expressed here as a percentage value in 100ths of a 2633 percent. A power factor of 100% indicates there is no 2634 inductance load and thus no reactive power. Power 2635 Factor can be positive or negative, where the sign 2636 should be in lead/lag (IEEE) form. IEC 61850-7-4 2637 attribute 'TotPF'." 2638 ::= { pmACPwrQualityEntry 10 } 2640 pmACPwrQualityThdAmpheres OBJECT-TYPE 2641 SYNTAX Integer32 (0..10000) 2642 UNITS "hundredths of percent" 2643 MAX-ACCESS read-only 2644 STATUS current 2645 DESCRIPTION 2646 "A calculated value for the current total harmonic 2647 distortion (THD). Method of calculation is not 2648 specified. IEC 61850-7-4 attribute 'ThdAmp'." 2649 ::= { pmACPwrQualityEntry 11 } 2651 pmACPwrQualityThdVoltage OBJECT-TYPE 2652 SYNTAX Integer32 (0..10000) 2653 UNITS "hundredths of percent" 2654 MAX-ACCESS read-only 2655 STATUS current 2656 DESCRIPTION 2657 "A calculated value for the voltage total harmonic 2658 distortion (THD). Method of calculation is not 2659 specified. IEC 61850-7-4 attribute 'ThdVol'." 2660 ::= { pmACPwrQualityEntry 12 } 2662 pmACPwrQualityPhaseTable OBJECT-TYPE 2663 SYNTAX SEQUENCE OF PmACPwrQualityPhaseEntry 2664 MAX-ACCESS not-accessible 2665 STATUS current 2666 DESCRIPTION 2667 "This table describes 3-phase power quality 2668 measurements. It is a sparse extension of the 2669 pmACPwrQualityTable." 2670 ::= { powerQualityMIBObjects 2 } 2672 pmACPwrQualityPhaseEntry OBJECT-TYPE 2673 SYNTAX PmACPwrQualityPhaseEntry 2674 MAX-ACCESS not-accessible 2675 STATUS current 2676 DESCRIPTION 2677 "An entry describes common 3-phase power quality 2678 measurements. 2680 This optional table describes 3-phase power quality 2681 measurements, with three entries for each supported 2682 pmPowerIndex entity. Entities having single phase 2683 power shall not have any entities. 2685 This table describes attributes common to both WYE and 2686 DEL. Entities having single phase power shall not have 2687 any entries here. It is a sparse extension of the 2688 pmACPwrQualityTable. 2690 These attributes correspond to IEC 61850-7.4 MMXU phase 2691 measurements." 2692 INDEX { pmPowerIndex, pmPhaseIndex } 2693 ::= { pmACPwrQualityPhaseTable 1 } 2695 PmACPwrQualityPhaseEntry ::= SEQUENCE { 2696 pmPhaseIndex Integer32, 2697 pmACPwrQualityPhaseAvgCurrent Integer32, 2698 pmACPwrQualityPhaseActivePower Integer32, 2699 pmACPwrQualityPhaseReactivePower Integer32, 2700 pmACPwrQualityPhaseApparentPower Integer32, 2701 pmACPwrQualityPhasePowerFactor Integer32, 2702 pmACPwrQualityPhaseImpedance Integer32 2703 } 2705 pmPhaseIndex OBJECT-TYPE 2706 SYNTAX Integer32 (0..359) 2707 MAX-ACCESS not-accessible 2708 STATUS current 2709 DESCRIPTION 2710 "A phase angle typically corresponding to 0, 120, 240." 2711 ::= { pmACPwrQualityPhaseEntry 1 } 2713 pmACPwrQualityPhaseAvgCurrent OBJECT-TYPE 2714 SYNTAX Integer32 2715 UNITS "Ampheres" 2716 MAX-ACCESS read-only 2717 STATUS current 2718 DESCRIPTION 2719 "A measured value of the current per phase. IEC 61850- 2720 7-4 attribute 'A'" 2721 ::= { pmACPwrQualityPhaseEntry 2 } 2723 pmACPwrQualityPhaseActivePower OBJECT-TYPE 2724 SYNTAX Integer32 2725 UNITS "RMS watts" 2726 MAX-ACCESS read-only 2727 STATUS current 2728 DESCRIPTION 2729 "A measured value of the actual power delivered to or 2730 consumed by the load. IEC 61850-7-4 attribute 'W'" 2731 ::= { pmACPwrQualityPhaseEntry 3 } 2733 pmACPwrQualityPhaseReactivePower OBJECT-TYPE 2734 SYNTAX Integer32 2735 UNITS "volt-amperes reactive" 2736 MAX-ACCESS read-only 2737 STATUS current 2738 DESCRIPTION 2739 "A measured value of the reactive portion of the 2740 apparent power. IEC 61850-7-4 attribute 'VAr'" 2741 ::= { pmACPwrQualityPhaseEntry 4 } 2743 pmACPwrQualityPhaseApparentPower OBJECT-TYPE 2744 SYNTAX Integer32 2745 UNITS "volt-amperes" 2746 MAX-ACCESS read-only 2747 STATUS current 2748 DESCRIPTION 2749 "A measured value of the voltage and current determines 2750 the apparent power. Active plus reactive power equals 2751 the total apparent powwer. 2753 Note: Watts and volt-ampheres are equivalent units and 2754 may be combined. IEC 61850-7-4 attribute 'VA'." 2755 ::= { pmACPwrQualityPhaseEntry 5 } 2757 pmACPwrQualityPhasePowerFactor OBJECT-TYPE 2758 SYNTAX Integer32 (-10000..10000) 2759 UNITS "hundredths of percent" 2760 MAX-ACCESS read-only 2761 STATUS current 2762 DESCRIPTION 2763 "A measured value ratio of the real power flowing to 2764 the load versus the apparent power for this phase. IEC 2765 61850-7-4 attribute 'PF'. Power Factor can be positive 2766 or negative where the sign should be in lead/lag (IEEE) 2767 form." 2768 ::= { pmACPwrQualityPhaseEntry 6 } 2770 pmACPwrQualityPhaseImpedance OBJECT-TYPE 2771 SYNTAX Integer32 2772 UNITS "volt-amperes" 2773 MAX-ACCESS read-only 2774 STATUS current 2775 DESCRIPTION 2776 "A measured value of the impedance. IEC 61850-7-4 attribute 2777 'Z'." 2778 ::= { pmACPwrQualityPhaseEntry 7 } 2780 pmACPwrQualityDelPhaseTable OBJECT-TYPE 2781 SYNTAX SEQUENCE OF PmACPwrQualityDelPhaseEntry 2782 MAX-ACCESS not-accessible 2783 STATUS current 2784 DESCRIPTION 2785 "This table describes DEL configuration phase-to-phase 2786 power quality measurements. This is a sparse extension 2787 of the pmACPwrQualityPhaseTable." 2788 ::= { powerQualityMIBObjects 3 } 2790 pmACPwrQualityDelPhaseEntry OBJECT-TYPE 2791 SYNTAX PmACPwrQualityDelPhaseEntry 2792 MAX-ACCESS not-accessible 2793 STATUS current 2794 DESCRIPTION 2795 "An entry describes quality attributes of a phase in a 2796 DEL 3-phase power system. Voltage measurements are 2797 provided both relative to each other and zero. 2799 Measured values are from IEC 61850-7-2 MMUX and THD from 2800 MHAI objects. 2802 For phase-to-phase measurements, the pmPhaseIndex is 2803 compared against the following phase at +120 degrees. 2804 Thus, the possible values are: 2806 pmPhaseIndex Next Phase Angle 2807 0 120 2808 120 240 2809 240 0 2810 " 2811 INDEX { pmPowerIndex, pmPhaseIndex} 2812 ::= { pmACPwrQualityDelPhaseTable 1} 2814 PmACPwrQualityDelPhaseEntry ::= SEQUENCE { 2815 pmACPwrQualityDelPhaseToNextPhaseVoltage Integer32, 2816 pmACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, 2817 pmACPwrQualityDelThdCurrent Integer32 2818 } 2820 pmACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE 2821 SYNTAX Integer32 2822 UNITS "0.1 Volt AC" 2823 MAX-ACCESS read-only 2824 STATUS current 2825 DESCRIPTION 2826 "A measured value of phase to next phase voltages, where 2827 the next phase is IEC 61850-7-4 attribute 'PPV'." 2828 ::= { pmACPwrQualityDelPhaseEntry 2 } 2830 pmACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE 2831 SYNTAX Integer32 (0..10000) 2832 UNITS "hundredths of percent" 2833 MAX-ACCESS read-only 2834 STATUS current 2835 DESCRIPTION 2836 "A calculated value for the voltage total harmonic 2837 disortion for phase to next phase. Method of calculation 2838 is not specified. IEC 61850-7-4 attribute 'ThdPPV'." 2839 ::= { pmACPwrQualityDelPhaseEntry 3 } 2841 pmACPwrQualityDelThdCurrent OBJECT-TYPE 2842 SYNTAX Integer32 (0..10000) 2843 UNITS "hundredths of percent" 2844 MAX-ACCESS read-only 2845 STATUS current 2846 DESCRIPTION 2847 "A calculated value for the voltage total harmonic 2848 disortion (THD) for phase to phase. Method of 2849 calculation is not specified. 2850 IEC 61850-7-4 attribute 'ThdPPV'." 2851 ::= { pmACPwrQualityDelPhaseEntry 4 } 2853 pmACPwrQualityWyePhaseTable OBJECT-TYPE 2854 SYNTAX SEQUENCE OF PmACPwrQualityWyePhaseEntry 2855 MAX-ACCESS not-accessible 2856 STATUS current 2857 DESCRIPTION 2858 "This table describes WYE configuration phase-to-neutral 2859 power quality measurements. This is a sparse extension 2860 of the pmACPwrQualityPhaseTable." 2861 ::= { powerQualityMIBObjects 4 } 2863 pmACPwrQualityWyePhaseEntry OBJECT-TYPE 2864 SYNTAX PmACPwrQualityWyePhaseEntry 2865 MAX-ACCESS not-accessible 2866 STATUS current 2867 DESCRIPTION 2868 "This table describes measurements of WYE configuration 2869 with phase to neutral power quality attributes. Three 2870 entries are required for each supported pmPowerIndex 2871 entry. Voltage measurements are relative to neutral. 2873 This is a sparse extension of the 2874 pmACPwrQualityPhaseTable. 2876 Each entry describes quality attributes of one phase of 2877 a WYE 3-phase power system. 2879 Measured values are from IEC 61850-7-2 MMUX and THD from 2880 MHAI objects." 2881 INDEX { pmPowerIndex, pmPhaseIndex } 2882 ::= { pmACPwrQualityWyePhaseTable 1} 2884 PmACPwrQualityWyePhaseEntry ::= SEQUENCE { 2885 pmACPwrQualityWyePhaseToNeutralVoltage Integer32, 2886 pmACPwrQualityWyePhaseCurrent Integer32, 2887 pmACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 2888 } 2890 pmACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE 2891 SYNTAX Integer32 2892 UNITS "0.1 Volt AC" 2893 MAX-ACCESS read-only 2894 STATUS current 2895 DESCRIPTION 2896 "A measured value of phase to neutral voltage. IEC 2897 61850-7-4 attribute 'PhV'." 2898 ::= { pmACPwrQualityWyePhaseEntry 1 } 2900 pmACPwrQualityWyePhaseCurrent OBJECT-TYPE 2901 SYNTAX Integer32 2902 UNITS "0.1 ampheres AC" 2903 MAX-ACCESS read-only 2904 STATUS current 2905 DESCRIPTION 2906 "A measured value of phase currents. IEC 61850-7-4 2907 attribute 'A'." 2908 ::= { pmACPwrQualityWyePhaseEntry 2 } 2910 pmACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE 2911 SYNTAX Integer32 (0..10000) 2912 UNITS "hundredths of percent" 2913 MAX-ACCESS read-only 2914 STATUS current 2915 DESCRIPTION 2916 "A calculated value of the voltage total harmonic 2917 distortion (THD) for phase to neutral. IEC 61850-7-4 2918 attribute 'ThdPhV'." 2919 ::= { pmACPwrQualityWyePhaseEntry 3 } 2921 -- Conformance 2923 powerQualityMIBCompliances OBJECT IDENTIFIER 2924 ::= { powerQualityMIB 2 } 2926 powerQualityMIBGroups OBJECT IDENTIFIER 2927 ::= { powerQualityMIB 3 } 2929 powerQualityMIBFullCompliance MODULE-COMPLIANCE 2930 STATUS current 2931 DESCRIPTION 2932 "When this MIB is implemented with support for read- 2933 create, then such an implementation can claim full 2934 compliance. Such devices can then be both monitored and 2935 configured with this MIB." 2936 MODULE -- this module 2937 MANDATORY-GROUPS { 2938 powerACPwrQualityMIBTableGroup, 2939 powerACPwrQualityPhaseMIBTableGroup 2940 } 2942 GROUP powerACPwrQualityDelPhaseMIBTableGroup 2943 DESCRIPTION 2944 "This group must only be implemented for a DEL phase 2945 configuration." 2947 GROUP powerACPwrQualityWyePhaseMIBTableGroup 2948 DESCRIPTION 2949 "This group must only be implemented for a WYE phase 2950 configuration." 2951 ::= { powerQualityMIBCompliances 1 } 2953 -- Units of Conformance 2955 powerACPwrQualityMIBTableGroup OBJECT-GROUP 2956 OBJECTS { 2957 -- Note that object pmPowerIndex is NOT 2958 -- included since it is not-accessible 2959 pmACPwrQualityConfiguration, 2960 pmACPwrQualityAvgVoltage, 2961 pmACPwrQualityAvgCurrent, 2962 pmACPwrQualityFrequency, 2963 pmACPwrQualityPowerUnitMultiplier, 2964 pmACPwrQualityPowerAccuracy, 2965 pmACPwrQualityTotalActivePower, 2966 pmACPwrQualityTotalReactivePower, 2967 pmACPwrQualityTotalApparentPower, 2968 pmACPwrQualityTotalPowerFactor, 2969 pmACPwrQualityThdAmpheres, 2970 pmACPwrQualityThdVoltage 2971 } STATUS current 2972 DESCRIPTION 2973 "This group contains the collection of all the power 2974 quality objects related to the Power Monitor." 2975 ::= { powerQualityMIBGroups 1 } 2977 powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP 2978 OBJECTS { 2979 -- Note that object pmPowerIndex is NOT 2980 -- included since it is not-accessible 2981 pmACPwrQualityPhaseAvgCurrent, 2982 pmACPwrQualityPhaseActivePower, 2983 pmACPwrQualityPhaseReactivePower, 2984 pmACPwrQualityPhaseApparentPower, 2985 pmACPwrQualityPhasePowerFactor, 2986 pmACPwrQualityPhaseImpedance 2987 } 2988 STATUS current 2989 DESCRIPTION 2990 "This group contains the collection of all 3-phase power 2991 quality objects related to the Power State." 2992 ::= { powerQualityMIBGroups 2 } 2994 powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP 2995 OBJECTS { 2996 -- Note that object pmPowerIndex and 2997 -- pmPhaseIndex are NOT included 2998 -- since they are not-accessible 2999 pmACPwrQualityDelPhaseToNextPhaseVoltage , 3000 pmACPwrQualityDelThdPhaseToNextPhaseVoltage, 3001 pmACPwrQualityDelThdCurrent 3002 } 3003 STATUS current 3004 DESCRIPTION 3005 "This group contains the collection of all quality 3006 attributes of a phase in a DEL 3-phase power system." 3007 ::= { powerQualityMIBGroups 3 } 3009 powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP 3010 OBJECTS { 3011 -- Note that object pmPowerIndex and 3012 -- pmPhaseIndex are NOT included 3013 -- since they are not-accessible 3014 pmACPwrQualityWyePhaseToNeutralVoltage, 3015 pmACPwrQualityWyePhaseCurrent, 3016 pmACPwrQualityWyeThdPhaseToNeutralVoltage 3017 } 3018 STATUS current 3019 DESCRIPTION 3020 "This group contains the collection of all WYE 3021 configuration phase-to-neutral power quality 3022 measurements." 3023 ::= { powerQualityMIBGroups 4 } 3025 END 3027 11. Security Considerations 3029 Some of the readable objects in these MIB modules (i.e., objects 3030 with a MAX-ACCESS other than not-accessible) may be considered 3031 sensitive or vulnerable in some network environments. It is 3032 thus important to control even GET and/or NOTIFY access to these 3033 objects and possibly to even encrypt the values of these objects 3034 when sending them over the network via SNMP. 3036 There are a number of management objects defined in these MIB 3037 modules with a MAX-ACCESS clause of read-write and/or read- 3038 create. Such objects MAY be considered sensitive or vulnerable 3039 in some network environments. The support for SET operations in 3040 a non-secure environment without proper protection can have a 3041 negative effect on network operations. The following are the 3042 tables and objects and their sensitivity/vulnerability: 3044 - Unauthorized changes to the pmPowerOperState (via 3045 thepmPowerAdminState ) MAY disrupt the power settings of the 3046 different Power Monitors, and therefore the state of 3047 functionality of the respective Power Monitors. 3048 - Unauthorized changes to the pmEnergyParametersTable MAY 3049 disrupt energy measurement in the pmEnergyTable table. 3051 SNMP versions prior to SNMPv3 did not include adequate security. 3052 Even if the network itself is secure (for example, by using 3053 IPsec), there is still no secure control over who on the secure 3054 network is allowed to access and GET/SET 3055 (read/change/create/delete) the objects in these MIB modules. 3057 It is RECOMMENDED that implementers consider the security 3058 features as provided by the SNMPv3 framework (see [RFC3410], 3059 section 8), including full support for the SNMPv3 cryptographic 3060 mechanisms (for authentication and privacy). 3062 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3063 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3064 enable cryptographic security. It is then a customer/operator 3065 responsibility to ensure that the SNMP entity giving access to 3066 an instance of these MIB modules is properly configured to give 3067 access to the objects only to those principals (users) that have 3068 legitimate rights to GET or SET (change/create/delete) them. 3070 12. IANA Considerations 3072 12.1. IANA Considerations for the MIB Modules 3074 The MIB modules in this document uses the following IANA- 3075 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers 3076 registry: 3078 Descriptor OBJECT IDENTIFIER value 3079 ---------- ----------------------- 3080 PowerMonitorMIB { mib-2 xxx } 3081 powerQualityMIB { mib-2 yyy } 3083 Additions to the MIB modules are subject to Expert Review 3084 [RFC5226], i.e., review by one of a group of experts designated 3085 by an IETF Area Director. The group of experts MUST check the 3086 requested MIB objects for completeness and accuracy of the 3087 description. Requests for MIB objects that duplicate the 3088 functionality of existing objects SHOULD be declined. The 3089 smallest available OIDs SHOULD be assigned to the new MIB 3090 objects. The specification of new MIB objects SHOULD follow the 3091 structure specified in Section 10. and MUST be published using 3092 a well-established and persistent publication medium. 3094 12.2. IANA Registration of new Power State Set 3096 This document specifies an initial set of Power State Sets. The 3097 list of these Power State Sets with their numeric identifiers is 3098 given in Section 5.2.1. The Internet Assigned Numbers Authority 3099 (IANA) has created a new registry for Power State Sets numeric 3100 identifiers and filled it with the initial list as in Section 3101 5.2.1. New Assignments to Power State Sets shall be 3102 administered by IANA and the guidelines and procedures are 3103 listed in this Section. 3105 New assignments in Power State Sets require a Standards Action 3106 [RFC5226], i.e., they are to be made via Standards Track RFCs 3107 approved by the IESG. The new Power State Set based on the 3108 following guidelines; firstly check if there are devices or 3109 entities that have implementations of the proposed Power State 3110 Set or secondly, if the new Power State Set has been adopted or 3111 approved by the respective energy management standards 3112 organizations. A pure vendor specific implementation of Power 3113 State Set shall not be adopted; since it would lead to 3114 proliferation of Power State Sets. 3116 12.2.1. IANA Registration of the IEEE1621 Power State Set 3118 This document specifies a set of values for the IEEE1621 Power 3119 State Set [IEEE1621]. The list of these values with their 3120 identifiers is given in Section 5.2.1. The Internet Assigned 3121 Numbers Authority (IANA) created a new registry for IEEE1621 3122 Power State Set identifiers and filled it with the initial list 3123 in Section 5.2.2. 3125 New assignments (or potentially deprecation) for IEEE1621 Power 3126 State Set will be administered by IANA through Expert Review 3127 [RFC5226], i.e., review by one of a group of experts designated 3128 by an IETF Area Director. The group of experts MUST check the 3129 requested state for completeness and accuracy of the 3130 description. 3132 12.2.2. IANA Registration of the DMTF Power State Set 3134 This document specifies a set of values for the DMTF Power State 3135 Set. The list of these values with their identifiers is given 3136 in Section 5.2.1. The Internet Assigned Numbers Authority 3137 (IANA) has created a new registry for DMTF Power State Set 3138 identifiers and filled it with the initial list in Section 3139 5.2.1. 3141 New assignments (or potentially deprecation) for DMTF Power 3142 State Set will be administered by IANA through Expert Review 3143 [RFC5226], i.e., review by one of a group of experts designated 3144 by an IETF Area Director. The group of experts MUST check the 3145 conformance with the DMTF standard [DMTF], on the top of 3146 checking for completeness and accuracy of the description. 3148 12.2.3. IANA Registration of the EMAN Power State Set 3150 This document specifies a set of values for the EMAN Power State 3151 Set. The list of these values with their identifiers is given 3152 in Section 5.2.1. The Internet Assigned Numbers Authority 3153 (IANA) has created a new registry for EMAN Power State Set 3154 identifiers and filled it with the initial list in Section 3155 5.2.1. 3157 New assignments (or potentially deprecation) for EMAN Power 3158 State Set New assignments in Power State Set require a Standards 3159 Action , i.e., they are to be made via Standards Track RFCs 3160 approved by the IESG. 3162 12. Contributors 3164 This document results from the merger of two initial proposals. 3165 The following persons made significant contributions either in 3166 one of the initial proposals or in this document. 3168 John Parello 3170 Rolf Winter 3172 Dominique Dudkowski 3174 13. Acknowledgment 3176 The authors would like to thank Shamita Pisal for her prototype 3177 of this MIB module, and her valuable feedback. The authors 3178 would like to Michael Brown for improving the text dramatically. 3180 14. Open Issues 3182 OPEN ISSUE : double-check all the IEC references in the draft. 3184 OPEN ISSUE: Description clause of pmPowerIndex Do we need this 3185 text Juergen Quittek to comment: 3187 "The identity provisioning method that has been chosen can be 3188 retrieved by reading the value of powerStateEnergyConsumerOid. 3189 In case of identities provided by the ENERGY-AWARE-MIB module, 3190 this OID points to an exising instance of pmPowerIndex, in case 3191 of the ENTITY MIB, the object points to a valid instance of 3192 entPhysicalIndex, and in a similar way, it points to a value of 3193 another MIB module if this is used for identifying entities. If 3194 no other MIB module has been chosen for providing entity 3195 identities, then the value of powerStateEnergyConsumerOid MUST 3196 be 0.0 (zeroDotZero). 3198 OPEN ISSUE : Juergen Schoenwalder review comments email May 3199 25, 2011 3201 PowerStateSeries ::= TEXTUAL-CONVENTION 3202 Why is this an OCTET STRING (SIZE(1)) and not simply an 3203 enumerated INTEGER? And if this is to be maintained by IANA, 3204 why not create a IANA-POWER-SERIES-TC MIB module so that one 3205 can simply fetch the latest version from IANA? 3207 New assignments in Power State Series require a Standards 3208 Action [RFC5226], i.e., they are to be made via Standards 3209 Track RFCs approved by the IESG. 3211 This raises the bar pretty high. If some future organization 3212 defines popular power states, do you think someone is going to 3213 go through the trouble of producing a standards-track 3214 specification for this? 3216 I also do not see why all objects in the pmPowerEntry are 3217 necessarily indexed by power series - some appear to me to be 3218 rather a property of the monitor and not the power state 3219 series the monitor happens to support. 3221 Since I started looking at the IANA considerations, I believe 3222 this text needs to be removed: 3224 OPEN ISSUE : Michael Schroff email comments Feb 24, 2011 3226 TimeStamps for Power measurements 3228 AC Power, Voltage, currrent measurement terminology 3230 3-phase WYE or Delta or hybrid of WYE and Delta 3231 NamePlate power consumption clarification 3233 Circuit breakers in scope of EMAN 3235 Response sent to mailing list requesting for more information 3236 and Clarification June 29, 2011. 3238 15. References 3240 15.2. Normative References 3242 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 3243 Requirement Levels, BCP 14, RFC 2119, March 1997. 3245 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3246 Schoenwaelder, Ed., "Structure of Management 3247 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3248 1999. 3250 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3251 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3252 STD 58, RFC 2579, April 1999. 3254 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3255 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3256 April 1999. 3258 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 3259 RFC3621, December 2003. 3261 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3262 3)", RFC 4133, August 2005. 3264 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 3265 Base extension module for TIA-TR41.4 media endpoint 3266 discovery information", July 2005. 3268 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 3269 energy-aware-mib-02 ", work in progress, July 2011. 3271 15.3. Informative References 3273 [RFC1628] S. Bradner, "UPS Management Information Base", RFC 3274 1628, May 1994 3276 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3277 "Introduction and Applicability Statements for Internet 3278 Standard Management Framework ", RFC 3410, December 3279 2002. 3281 [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. 3282 Waldbusser, "Management Information Base (MIB) for the 3283 Simple Network Management Protocol (SNMP)", RFC3418, 3284 December 2002. 3286 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity 3287 Sensor Management Information Base", RFC 3433, December 3288 2002. 3290 [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 3291 4268,November 2005. 3293 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 3294 "Guidelines for Writing an IANA Considerations Section 3295 in RFCs ", BCP 26, RFC 5226, May 2008. 3297 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 3298 M. Chandramouli, " Requirements for Energy Management 3299 ", draft-ietf-eman-requirements-03 (work in 3300 progress),July 2011. . 3302 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. 3303 Quittek, "Energy Management Framework", draft-ietf- 3304 eman-framework-02 , July 2011. 3306 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 3307 Quittek, J. and B. Claise "Energy and Power Monitoring 3308 MIB ", draft-claise-energy-monitoring-mib-09, July 3309 2011. 3311 [EMAN-AS] Tychon, E., Laherty, M., and B. Schoening, "Energy 3312 Management (EMAN) Applicability Statement", draft- 3313 tychon-eman-applicability-statement-02, work in 3314 progress, June 2011. 3316 [ACPI] "Advanced Configuration and Power Interface 3317 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 3318 0b.pdf 3320 [DMTF] "Power State Management Profile DMTF DSP1027 Version 3321 2.0" December 2009 3322 http://www.dmtf.org/sites/default/files/standards/docum 3323 ents/DSP1027_2.0.0.pdf 3325 [IEEE1621] "Standard for User Interface Elements in Power 3326 Control of Electronic Devices Employed in 3327 Office/Consumer Environments", IEEE 1621, December 3328 2004. 3330 [IEC.61850-7-4] International Electrotechnical Commission, 3331 "Communication networks and systems for power utility 3332 automation Part 7-4: Basic communication structure 3333 Compatible logical node classes and data object 3334 classes", 2010. 3336 [IEC.62053-21] International Electrotechnical Commission, 3337 "Electricity metering equipment (a.c.) Particular 3338 requirements Part 22: Static meters for active energy 3339 (classes 1 and 2)", 2003. 3341 [IEC.62053-22]International Electrotechnical Commission, 3342 "Electricity metering equipment (a.c.) Particular 3343 requirements Part 22: Static meters for active energy 3344 (classes 0,2 S and 0,5 S)", 2003. 3346 Authors' Addresses 3348 Mouli Chandramouli 3349 Cisco Systems, Inc. 3350 Sarjapur Outer Ring Road 3351 Bangalore, 3352 IN 3354 Phone: +91 80 4426 3947 3355 Email: moulchan@cisco.com 3357 Brad Schoening 3358 44 Rivers Edge Drive 3359 Little Silver, NJ 07739 3360 US 3361 Email: brad@bradschoening.com 3363 Juergen Quittek 3364 NEC Europe Ltd. 3366 NEC Laboratories Europe 3367 Network Research Division 3368 Kurfuersten-Anlage 36 3369 Heidelberg 69115 3370 DE 3372 Phone: +49 6221 4342-115 3373 Email: quittek@neclab.eu 3375 Thomas Dietz 3376 NEC Europe Ltd. 3377 NEC Laboratories Europe 3378 Network Research Division 3379 Kurfuersten-Anlage 36 3380 Heidelberg 69115 3381 DE 3383 Phone: +49 6221 4342-128 3384 Email: Thomas.Dietz@neclab.eu 3386 Benoit Claise 3387 Cisco Systems, Inc. 3388 De Kleetlaan 6a b1 3389 Diegem 1813 3390 BE 3392 Phone: +32 2 704 5622 3393 Email: bclaise@cisco.com