idnits 2.17.1 draft-ietf-eman-energy-monitoring-mib-07.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 310 has weird spacing: '...tiplier eoP...' == Line 324 has weird spacing: '...tateSet eoPow...' == Line 348 has weird spacing: '...wStatus eoEne...' == Line 367 has weird spacing: '...exed by entPh...' == Line 702 has weird spacing: '...ributes measu...' == (12 more instances...) == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 21, 2013) is 3838 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'ACPI' is defined on line 3502, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MED-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'EMAN-AWARE-MIB' -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-11 == Outdated reference: A later version (-13) exists of draft-ietf-eman-energy-monitoring-mib-06 == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-04 -- Obsolete informational reference (is this intentional?): RFC 6982 (Obsoleted by RFC 7942) Summary: 1 error (**), 0 flaws (~~), 13 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Chandramouli 3 Internet-Draft Cisco Systems, Inc. 4 Intended Status: Standards Track B. Schoening 5 Expires: April 21, 2014 Independent Consultant 6 J. Quittek 7 T. Dietz 8 NEC Europe Ltd. 9 B. Claise 10 Cisco Systems, Inc. 11 October 21, 2013 13 Power and Energy Monitoring MIB 14 draft-ietf-eman-energy-monitoring-mib-07 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance 19 with the provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as 30 "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html 38 This Internet-Draft will expire on April 2014. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with 50 respect to this document. Code Components extracted from this 51 document must include Simplified BSD License text as described 52 in Section 4.e of the Trust Legal Provisions and are provided 53 without warranty as described in the Simplified BSD License. 55 Abstract 57 This document defines a subset of the Management Information 58 Base (MIB) for power and energy monitoring of devices. 60 Conventions used in this document 62 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 63 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED" 64 "MAY", and "OPTIONAL" in this document are to be interpreted as 65 described in RFC 2119 [RFC2119]. 67 Table of Contents 69 1. Introduction.............................................. 3 70 2. The Internet-Standard Management Framework................ 4 71 3. Use Cases................................................. 4 72 4. Terminology............................................... 5 73 5. Architecture Concepts Applied to the MIB Module........... 6 74 5.1. Energy Object Information.............................. 13 75 5.2. Power State............................................ 14 76 5.2.1. Power State Set................................ 15 77 5.3. Energy Object Usage Information........................ 15 78 5.4. Optional Power Usage Attributes........................ 16 79 5.5. Optional Energy Measurement............................ 17 80 5.6. Fault Management....................................... 21 81 6. Discovery................................................ 21 82 7. Link with the other IETF MIBs............................ 22 83 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB...22 84 7.2. Link with the ENTITY-STATE MIB.......................23 85 7.3. Link with the POWER-OVER-ETHERNET MIB................24 86 7.4. Link with the UPS MIB................................25 87 7.5. Link with the LLDP and LLDP-MED MIBs.................26 88 8. Implementation Scenario.................................. 26 89 9. Structure of the MIB..................................... 29 90 10. MIB Definitions......................................... 30 91 11. Implementation Status................................... 70 92 11.1. SNMP Research......................................... 71 93 11.2. Cisco Systems......................................... 71 94 12. Security Considerations................................. 72 95 13. IANA Considerations..................................... 73 96 13.1. IANA Considerations for the MIB Modules............... 73 97 13.2. IANA Registration of new Power State Set.............. 73 98 13.2.1. IANA Registration of the IEEE1621 Power State Set..74 99 13.2.2. IANA Registration of the DMTF Power State Set......74 100 13.2.3. IANA Registration of the EMAN Power State Set......74 101 13.3. Updating the Registration of Existing Power State 102 Sets........................................................ 74 103 12. Contributors............................................ 75 104 13. Acknowledgment.......................................... 75 105 14. Open Issues............................................. 75 106 15. References.............................................. 76 107 15.2. Normative References............................... 76 108 15.3. Informative References............................. 76 110 1. Introduction 112 This document defines a subset of the Management Information 113 Base (MIB) for use in energy management of devices within or 114 connected to communication networks. The MIB modules in this 115 document are designed to provide a model for energy management, 116 which includes monitoring for power state and energy consumption 117 of networked elements. This MIB takes into account the Energy 118 Management Framework [EMAN-FMWK], which in turn, is based on the 119 Requirements for Energy Management [EMAN-REQ]. 121 Energy management is applicable to devices in communication 122 networks. Target devices for this specification include (but 123 are not limited to): routers, switches, Power over Ethernet 124 (PoE) endpoints, protocol gateways for building management 125 systems, intelligent meters, home energy gateways, hosts and 126 servers, sensor proxies, etc. Target devices and the use cases 127 for Energy Management are discussed in Energy Management 128 Applicability Statement [EMAN-AS]. 130 Where applicable, device monitoring extends to the individual 131 components of the device and to any attached dependent devices. 132 For example: A device can contain components that are 133 independent from a power-state point of view, such as line 134 cards, processor cards, hard drives. A device can also have 135 dependent attached devices, such as a switch with PoE endpoints 136 or a power distribution unit with attached endpoints. 138 Devices and their sub-components can be modeled using the 139 containment tree of the ENTITY-MIB [RFC6933]. In addition, 140 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] provides a framework 141 for modeling the relationship between Energy Objects. It is 142 conceivable to have implementations of ENERGY-AWARE-MIB and 143 ENERGY-OBJECT-MIB for modeling the relationships between Energy 144 Objects and also monitoring the Energy consumption. In some 145 situations, it is possible to have implementation of ENERGY- 146 OBJECT-MIB along with the requirement of Module Compliance of 147 ENTITY-MIB V4 [RFC6933] with respect to entity4CRCompliance 148 should be supported which requires 3 MIB objects 149 (entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be 150 implemented. 152 2. The Internet-Standard Management Framework 154 For a detailed overview of the documents that describe the 155 current Internet-Standard Management Framework, please refer to 156 section 7 of RFC 3410 [RFC3410]. 158 Managed objects are accessed via a virtual information store, 159 termed the Management Information Base or MIB. MIB objects are 160 generally accessed through the Simple Network Management 161 Protocol (SNMP). Objects in the MIB are defined using the 162 mechanisms defined in the Structure of Management Information 163 (SMI). This memo specifies MIB modules that are compliant to 164 SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, 165 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 167 3. Use Cases 169 Requirements for power and energy monitoring for networking 170 devices are specified in [EMAN-REQ]. The requirements in [EMAN- 171 REQ] cover devices typically found in communications networks, 172 such as switches, routers, and various connected endpoints. For 173 a power monitoring architecture to be useful, it should also 174 apply to facility meters, power distribution units, gateway 175 proxies for commercial building control, home automation 176 devices, and devices that interface with the utility and/or 177 smart grid. Accordingly, the scope of the MIB modules in this 178 document is broader than that specified in [EMAN-REQ]. Several 179 use cases for Energy Management have been identified in the 180 "Energy Management (EMAN) Applicability Statement" [EMAN-AS]. An 181 illustrative example scenario is presented in Section 8. 183 4. Terminology 185 Please refer to [EMAN-FMWK] for the definitions of the 186 following terminology used in this draft. 188 Device 190 Component 192 Energy Management 194 Energy Management System (EnMS) 196 ISO Energy Management System 198 Energy 200 Power 202 Demand 204 Power Attributes 206 Electrical Equipment 208 Non-Electrical Equipment (Mechanical Equipment) 210 Energy Object 212 Electrical Energy Object 214 Non-Electrical Energy Object 216 Energy Monitoring 218 Energy Control 219 Provide Energy: 221 Receive Energy: 223 Power Interface 225 Power Inlet 227 Power Outlet 229 Energy Management Domain 231 Energy Object Identification 233 Energy Object Context 235 Energy Object Relationship 237 Aggregation Relationship 239 Metering Relationship 241 Power Source Relationship 243 Proxy Relationship 245 Energy Object Parent 247 Energy Object Child 249 Power State 251 Power State Set 253 Nameplate Power 255 5. Architecture Concepts Applied to the MIB Module 257 This section describes the concepts specified in the Energy 258 Management Framework [EMAN-FMWK] that pertain to power usage, 259 with specific information related to the MIB module specified in 260 this document. This subsection maps to the section 261 "Architecture High Level Concepts" in the Power Monitoring 262 Architecture [EMAN-FMWK]. 264 The Energy Monitoring MIB has 2 independent MIB modules. The 265 first MIB module energyObjectMib is focused on measurement of 266 power and energy. The second MIB module powerCharMIB is focused 267 on Power Attributes measurements. 269 The energyObjectMib MIB module consists of five tables. 271 The first table is the eoMeterCapabilitiesTable. It indicates 272 the instrumentation available for each energy object. Thus, the 273 entries in this table indicate to the EnMS which other tables 274 from the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB are 275 available for each energy object. The eoMeterCapabilitiesTable 276 is indexed by entPhysicalIndex. 278 The second table is the eoPowerTable. It returns the power 279 consumption of each energy object, as well as the units, sign, 280 measurement accuracy, and related objects. The eoPowerTable is 281 indexed by entPhysicalIndex. 283 The third table is the eoPowerStateTable. For each energy 284 object, it provides information and statistics about the 285 supported power states. The eoPowerStateTable is indexed by 286 entPhysicalIndex and eoPowerStateIndex. 288 The fourth table is the eoEnergyParametersTable. The entries in 289 this table configure the parameters of energy and demand 290 measurement collection. This table is indexed by 291 eoEnergyParametersIndex. 293 The fifth table is the eoEnergyTable. The entries in this table 294 provide the log the energy and demand information. This table 295 is indexed by eoEnergyParametersIndex. 297 eoMeterCapabilitiesTable(1) 298 | 299 +---eoMeterCapabilitiesEntry(1)[entPhysicalIndex] 300 | | 301 | +---r-n BITS eoMeterCapability 302 | 304 eoPowerTable(2) 305 | 306 +---eoPowerEntry(1) [entPhysicalIndex] 307 | | 308 | +---r-n Integer32 eoPower(1) 309 | +-- r-n Integer32 eoPowerNamePlate(2) 310 | +-- r-n UnitMultiplier eoPowerUnitMultiplier(3) 311 | +-- r-n Integer32 eoPowerAccuracy(4) 312 | +-- r-n INTEGER eoMeasurementCaliber(5) 313 | +-- r-n INTEGER eoPowerCurrentType(6) 314 | +-- r-n INTEGER eoPowerOrigin(7) 315 | +-- rwn IANAPowerStateSet eoPowerAdminState(8) 316 | +-- r-n IANAPowerStateSet eoPowerOperState(9) 317 | +-- r-n OwnerString eoPowerStateEnterReason(10) 318 | 319 | 320 +---eoPowerStateTable(3) 321 | +--eoPowerStateEntry(1) 322 | | [entPhysicalIndex, eoPowerStateIndex] 323 | | 324 | +-- --n IANAPowerStateSet eoPowerStateIndex(1) 325 | +-- r-n Interger32 eoPowerStateMaxPower (2) 326 | +-- r-n UnitMultiplier 327 | eoPowerStatePowerUnitMultiplier (3) 328 | +-- r-n TimeTicks eoPowerStateTotalTime(4) 329 | +-- r-n Counter32 eoPowerStateEnterCount(5) 330 | 332 +eoEnergyParametersTable(4) 333 +---eoEnergyParametersEntry(1) [eoEnergyParametersIndex] 334 | 336 | +-- --n PhysicalIndex eoEnergyObjectIndex (1) 337 | + r-n Integer32 eoEnergyParametersIndex (2) 338 | +-- r-n TimeInterval 339 | eoEnergyParametersIntervalLength (3) 340 | +-- r-n Integer32 341 | eoEnergyParametersIntervalNumber (4) 342 | +-- r-n Integer32 343 | eoEnergyParametersIntervalMode (5) 344 | +-- r-n TimeInterval 345 | eoEnergyParametersIntervalWindow (6) 346 | +-- r-n Integer32 347 | eoEnergyParametersSampleRate (7) 348 | +-- r-n RowStatus eoEnergyParametersStatus (8) 349 | 350 +eoEnergyTable(5) 351 +---eoEnergyEntry(1) [ eoEnergyParametersIndex, 352 eoEnergyCollectionStartTime] 353 | 354 | +-- r-n TimeTicks eoEnergyCollectionStartTime (1) 355 | +-- r-n Integer32 eoEnergyConsumed (2) 356 | +-- r-n Integer32 eoEnergyProvided (3) 357 | +-- r-n Integer32 eoEnergyStored (4) 358 | +-- r-n UnitMultiplier 359 | eoEnergyUnitMultiplier (5) 360 | +-- r-n Integer32 eoEnergyAccuracy(6) 361 | +-- r-n Integer32 eoEnergyMaxConsumed (7) 362 | +-- r-n Integer32 eoEnergyMaxProduced (8) 363 | +-- r-n TimeTicks 364 | eoEnergyDiscontinuityTime(9) 366 The powerAttributesMIB consists of four tables. 367 eoACPwrAttributesTable is indexed by entPhysicalIndex. 368 eoACPwrAttributesPhaseTable is indexed by entPhysicalIndex and 369 eoPhaseIndex. eoACPwrAttributesWyePhaseTable and 370 eoACPwrAttributesDelPhaseTable are indexed by entPhysicalIndex 371 and eoPhaseIndex. 373 eoACPwrAttributesTable(1) 374 | 375 +---eoACPwrAttributesEntry(1) [ entPhysicalIndex] 376 | | 377 | | 378 | +---r-n INTEGER eoACPwrAttributesConfiguration (1) 379 | +-- r-n Interger32 eoACPwrAttributesAvgVoltage (2) 380 | +-- r-n Integer32 eoACPwrAttributesAvgCurrent (3) 381 | +-- r-n Integer32 eoACPwrAttributesFrequency (4) 382 | +-- r-n UnitMultiplier 383 | eoACPwrAttributesPowerUnitMultiplier (5) 384 | +-- r-n Integer32 eoACPwrAttributesPowerAccuracy (6) 385 | +-- r-n Interger32 386 eoACPwrAttributesTotalActivePower (7) 387 | +-- r-n Integer32 388 | eoACPwrAttributesTotalReactivePower (8) 389 | +-- r-n Integer32 390 eoACPwrAttributesTotalApparentPower (9) 391 | +-- r-n Integer32 392 eoACPwrAttributesTotalPowerFactor (10) 393 | +-- r-n Integer32 eoACPwrAttributesThdAmpheres (11) 394 | 395 +eoACPwrAttributesPhaseTable(2) 396 +---EoACPwrAttributesPhaseEntry(1)[ entPhysicalIndex, 397 | | eoPhaseIndex] 398 | | 399 | +-- r-n Integer32 eoPhaseIndex (1) 400 | +-- r-n Integer32 401 | | eoACPwrAttributesPhaseAvgCurrent (2) 402 | +-- r-n Integer32 403 | | eoACPwrAttributesPhaseActivePower (3) 404 | +-- r-n Integer32 405 | | eoACPwrAttributesPhaseReactivePower (4) 406 | +-- r-n Integer32 407 | | eoACPwrAttributesPhaseApparentPower (5) 408 | +-- r-n Integer32 409 | | eoACPwrAttributesPhasePowerFactor (6) 410 | +-- r-n Integer32 411 | | eoACPwrAttributesPhaseImpedance (7) 412 | | 413 +eoACPwrAttributesDelPhaseTable(3) 414 +-- eoACPwrAttributesDelPhaseEntry(1) 415 | | [entPhysicalIndex, 416 | | eoPhaseIndex] 417 | +-- r-n Integer32 418 | | eoACPwrAttributesDelPhaseToNextPhaseVoltage (1) 419 | +-- r-n Integer32 420 | |eoACPwrAttributesDelThdPhaseToNextPhaseVoltage (2) 421 | +-- r-n Integer32 422 eoACPwrAttributesDelThdCurrent (3) 423 | | 424 +eoACPwrAttributesWyePhaseTable(4) 425 +-- eoACPwrAttributesWyePhaseEntry(1) 426 | | [entPhysicalIndex, 427 | | eoPhaseIndex] 428 | +-- r-n Integer32 429 | | eoACPwrAttributesWyePhaseToNeutralVoltage (1) 430 | +-- r-n Integer32 431 | | eoACPwrAttributesWyePhaseCurrent (2) 432 | +-- r-n Integer32 433 | | eoACPwrAttributesWyeThdPhaseToNeutralVoltage (3) 434 | . 436 A UML representation of the MIB objects in the two MIB modules 437 are energyObjectMib and powerAttributesMIB are presented. 439 +-------------------------+ 440 | Energy Object State | 441 | ----------------------- | 442 | eoPowerAdminState | 443 | eoPowerOperState | 444 | eoPowerStateEnterReason | 445 +-------------------------+ 446 | 447 | 448 v 449 +-----------------------+ 451 |---> | Energy Object ID (*) | 452 | | --------------------- | 453 | | entPhysicalIndex | 454 | | entPhysicalName | 455 | | entPhysicalUUID | 456 | +-----------------------+ 457 | 458 | +-----------------------------+ 459 |---- | Energy Object Measurement | 460 | | --------------------------- | 461 | | eoPower | 462 | | eoPowerUnitMultiplier | 463 | | eoPowerAccuracy | 464 | +-----------------------------+ 465 | 466 | +---------------------------+ 467 |---- | Energy Object Attributes | 468 | | ------------------------- | 469 | | eoPowerNamePlate | 470 | | eoPowerMeasurementCaliber | 471 | | eoPowerCurrentType | 472 | | eoPowerOrigin | 473 | +---------------------------+ 474 | 475 | +---------------------------------+ 476 |---- | Energy Object State Statistics | 477 |-------------------------------- | 478 | eoPowerStateMaxPower | 479 | eoPowerStatePowerUnitMultiplier | 480 | eoPowerStateTotalTime | 481 | eoPowerStateEnterCount | 482 +---------------------------------+ 484 Figure 1:UML diagram for energyObjectMib 486 (*) Compliance with the ENERGY-AWARE-MIB 488 +----------------------------------+ 489 | Energy ParametersTable | 490 | -------------------------------- | 491 | eoEnergyObjectIndex | 492 | eoEnergyParametersIndex | 493 | eoEnergyParametersIntervalLength | 494 | eoEnergyParametersIntervalNumber | 495 | eoEnergyParametersIntervalMode | 496 | eoEnergyParametersIntervalWindow | 497 | eoEnergyParametersSampleRate | 498 | eoEnergyParametersStatus | 499 +----------------------------------+ 500 | 501 V 502 +----------------------------------+ 503 | Energy Table | 504 | -------------------------------- | 505 | eoEnergyCollectionStartTime | 506 | eoEnergyConsumed | 507 | eoEnergyProvided | 508 | eoEnergyStored | 509 | eoEnergyUnitMultiplier | 510 | eoEnergyAccuracy | 511 | eoEnergyMaxConsumed | 512 | eoEnergyMaxProduced | 513 | eoDiscontinuityTime | 514 +----------------------------------+ 516 +-----------------------+ 517 |---> | Energy Object ID (*) | 518 | | --------------------- | 519 | | entPhysicalIndex | 520 | | entPhysicalName | 521 | | entPhysicalUUID | 522 | +-----------------------+ 523 | 524 | +--------------------------------------+ 525 |---- | Power Attributes | 526 | | ------------------------------------ | 527 | | eoACPwrAttributesConfiguration | 528 | | eoACPwrAttributesAvgVoltage | 529 | | eoACPwrAttributesAvgCurrent | 530 | | eoACPwrAttributesFrequency | 531 | | eoACPwrAttributesPowerUnitMultiplier | 532 | | eoACPwrAttributesPowerAccuracy | 533 | | eoACPwrAttributesTotalActivePower | 534 | | eoACPwrAttributesTotalReactivePower | 535 | | eoACPwrAttributesTotalApparentPower | 536 | | eoACPwrAttributesTotalPowerFactor | 537 | | eoACPwrAttributesThdAmpheres | 538 | +--------------------------------------+ 539 | 540 | 541 | +--------------------------------------+ 542 |---- | Power Phase Attributes | 543 | | ------------------------------------ | 544 | | eoPhaseIndex | 545 | | eoACPwrAttributesPhaseAvgCurrent | 546 | | eoACPwrAttributesPhaseActivePower | 547 | | eoACPwrAttributesPhaseReactivePower | 548 | | eoACPwrAttributesPhaseApparentPower | 549 | | eoACPwrAttributesPhasePowerFactor | 550 | | eoACPwrAttributesPhaseImpedance | 551 | +--------------------------------------+ 552 | 553 | 554 | +------------------------------------------------+ 555 |---- | AC Input DEL Configuration | 556 | | ---------------------------------------------- | 557 | | eoACPwrAttributesDelPhaseToNextPhaseVoltage | 558 | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage | 559 | | eoACPwrAttributesDelThdCurrent | 560 | +------------------------------------------------+ 561 | 562 | +----------------------------------------------+ 563 |---- | AC Input WYE Configuration | 564 | ---------------------------------------------| 565 | eoACPwrAttributesWyePhaseToNeutralVoltage | 566 | eoACPwrAttributesWyePhaseCurrent | 567 | eoACPwrAttributesWyeThdPhaseToNeutralVoltage | 568 +----------------------------------------------+ 570 Figure 2: UML diagram for the powerAttributesMIB 572 (*) Compliance with the ENERGY-AWARE-MIB 574 5.1. Energy Object Information 576 Refer to the "Energy Object Information" section in [EMAN-FMWK] 577 for background information. An energy aware device is 578 considered as an instance of a Energy Object as defined in the 579 [EMAN-FMWK]. 581 The Energy Object identity information is specified in the MIB 582 ENERGY-AWARE-MIB module [EMAN-AWARE-MIB] primary table, i.e. the 583 eoTable. In this table, the context of the Energy Object such as 584 Domain, RoleDescription, Importance are specified. In addition, 585 the ENERGY-AWARE-MIB module returns the relationship between 586 Objects. There are several possible relationships between Parent 587 and Child as defined in [EMAN-AWARE-MIB] such as MeteredBy, 588 PoweredBy, and AggregatedBy. 590 5.2. Power State 592 Refer to the "Power States" section in [EMAN-FMWK] for 593 background information. 595 An Energy Object may have energy conservation modes called Power 596 States. Between the ON and OFF states of a device, there can be 597 several intermediate energy saving modes. Those energy saving 598 modes are called as Power States. 600 Power States, which represent universal states of power 601 management of an Energy Object, are specified by the 602 eoPowerState MIB object. The actual Power State is specified by 603 the eoPowerOperState MIB object, while the eoPowerAdminState MIB 604 object specifies the Power State requested for the Energy 605 Object. The difference between the values of eoPowerOperState 606 and eoPowerAdminState can be attributed that the Energy Object 607 is busy transitioning from eoPowerAdminState into the 608 eoPowerOperState, at which point it will update the content of 609 eoPowerOperState. In addition, the possible reason for change 610 in Power State is reported in eoPowerStateEnterReason. 611 Regarding eoPowerStateEnterReason, management stations and 612 Energy Objects should support any format of the owner string 613 dictated by the local policy of the organization. It is 614 suggested that this name contain at least the reason for the 615 transition change, and one or more of the following: IP address, 616 management station name, network manager's name, location, or 617 phone number. 619 The MIB objects eoPowerOperState, eoPowerAdminState , and 620 eoPowerStateEnterReason are contained in the eoPowerTable MIB 621 table. 623 The eoPowerStateTable table enumerates the maximum power usage 624 in watts, for every single supported Power State of each Power 625 State Set supported by the Energy Object. In addition, 626 PowerStateTable provides additional statistics: 627 eoPowerStateEnterCount, the number of times an entity has 628 visited a particular Power State, and eoPowerStateTotalTime, the 629 total time spent in a particular Power State of an Energy 630 Object. 632 5.2.1. Power State Set 634 There are several standards and implementations of Power State 635 Sets. A Energy Object can support one or multiple Power State 636 Set implementation(s) concurrently. 638 There are currently three Power State Sets advocated: 640 unknown(0) 641 IEEE1621(256) - [IEEE1621] 642 DMTF(512) - [DMTF] 643 EMAN(1024) - [EMAN-MONITORING-MIB] 645 The respective specific states related to each Power State Set 646 are specified in the following sections. The guidelines for 647 addition of new Power State Sets have been specified in the IANA 648 Considerations Section. 650 The Power States within each Power State Set are listed in 651 [EMAN-FMWK]. The Textual Convention IANAPowerStateSet provides 652 the proposed numbering of the Power States within the IEEE1621 653 Power State Set, DMTF Power State Set and the EMAN Power State 654 Set. 656 5.3. Energy Object Usage Information 658 Refer to the "Energy Object Usage Measurement" section in [EMAN- 659 FMWK] for background information. 661 For an Energy Object, power usage is reported using eoPower. 662 The magnitude of measurement is based on the 663 eoPowerUnitMultiplier MIB variable, based on the UnitMultiplier 664 Textual Convention (TC). Power measurement magnitude should 665 conform to the IEC 62053-21 [IEC.62053-21] and IEC 62053-22 666 [IEC.62053-22] definition of unit multiplier for the SI (System 667 International) units of measure. Measured values are 668 represented in SI units obtained by BaseValue * 10 raised to the 669 power of the scale. 671 For example, if current power usage of an Energy Object is 3, it 672 could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of 673 eoPowerUnitMultiplier. Note that other measurements throughout 674 the two MIB modules in this document use the same mechanism, 675 including eoPowerStatePowerUnitMultiplier, 676 eoEnergyUnitMultiplier, and 677 eoACPwrAttributesPowerUnitMultiplier. 679 In addition to knowing the usage and magnitude, it is useful to 680 know how a eoPower measurement was obtained. An NMS can use 681 this to account for the accuracy and nature of the reading 682 between different implementations. For this eoPowerOrigin 683 describes whether the measurements were made at the device 684 itself or from a remote source. The eoPowerMeasurementCaliber 685 describes the method that was used to measure the power and can 686 distinguish actual or estimated values. There may be devices in 687 the network, which may not be able to measure or report power 688 consumption. For those devices, the object 689 eoPowerMeasurementCaliber shall report that measurement 690 mechanism is "unavailable" and the eoPower measurement shall be 691 "0". 693 The nameplate power rating of an Energy Object is specified in 694 eoPowerNameplate MIB object. 696 5.4. Optional Power Usage Attributes 698 Refer to the "Optional Power Usage Attributes" section in 699 [EMAN-FMWK] for background information. 701 The optional powerAttributesMIB MIB module can be implemented to 702 further describe power usage attributes measurement. The 703 powerAttributesMIB MIB module adheres closely to the IEC 61850 704 7-2 standard to describe AC measurements. 706 The powerAttributesMIB MIB module contains a primary table, the 707 eoACPwrAttributesTable table, that defines power attributes 708 measurements for supported entPhysicalIndex entities, as a 709 sparse extension of the eoPowerTable (with entPhysicalIndex as 710 primary index). This eoACPwrAttributesTable table contains such 711 information as the configuration (single phase, DEL 3 phases, 712 WYE 3 phases), voltage, frequency, power accuracy, total 713 active/reactive power/apparent power, amperage, and voltage. 715 In case of 3-phase power, the eoACPwrAttributesPhaseTable 716 additional table is populated with Power Attributes measurements 717 per phase (so double indexed by the entPhysicalIndex and 718 eoPhaseIndex). This table, which describes attributes common to 719 both WYE and DEL configurations, contains the average current, 720 active/reactive/apparent power, power factor, and impedance. 722 In case of 3-phase power with a DEL configuration, the 723 eoACPwrAttributesDelPhaseTable table describes the phase-to- 724 phase power attributes measurements, i.e., voltage and current. 726 In case of 3-phase power with a Wye configuration, the 727 eoACPwrAttributesWyePhaseTable table describes the phase-to- 728 neutral power attributes measurements, i.e., voltage and 729 current. 731 5.5. Optional Energy Measurement 733 Refer to the "Optional Energy and demand Measurement" section in 734 [EMAN-FMWK] for the definition and terminology information. 736 It is relevant to measure energy and demand only when there are 737 actual power measurements obtained from measurement hardware. If 738 the eoPowerMeasurementCaliber MIB object has values of 739 unavailable, unknown, estimated, or presumed, then the energy 740 and demand values are not useful. 742 Two tables are introduced to characterize energy measurement of 743 an Energy Object: eoEnergyTable and eoEnergyParametersTable. 744 Both energy and demand information can be represented via the 745 eoEnergyTable. Energy information will be an accumulation with 746 no interval. Demand information can be represented. 747 The eoEnergyParametersTable consists of the parameters defining 748 eoEnergyParametersIndex an index of that specifies the setting 749 for collection of energy measurements for an Energy Object, 750 eoEnergyObjectIndex linked to the entPhysicalIndex of the 751 Energy Object, the duration of measurement intervals in seconds, 752 (eoEnergyParametersIntervalLength), the number of successive 753 intervals to be stored in the eoEnergyTable, 754 (eoEnergyParametersIntervalNumber), the type of measurement 755 technique (eoEnergyParametersIntervalMode), and a sample rate 756 used to calculate the average (eoEnergyParametersSampleRate). 757 Judicious choice of the sampling rate will ensure accurate 758 measurement of energy while not imposing an excessive polling 759 burden. 761 There are three eoEnergyParametersIntervalMode types used for 762 energy measurement collection: period, sliding, and total. The 763 choices of the the three different modes of collection are based 764 on IEC standard 61850-7-4. Note that multiple 765 eoEnergyParametersIntervalMode types MAY be configured 766 simultaneously. It is important to note that for a given Energy 767 Object, multiple modes (periodic, total, sliding window) of 768 energy measurement collection can be configured with the use of 769 eoEnergyParametersIndex. However, simultaneous measurement in 770 multiple modes for a given Energy Object depends on the Energy 771 Object capability. 773 These three eoEnergyParametersIntervalMode types are illustrated 774 by the following three figures, for which: 776 - The horizontal axis represents the current time, with the 777 symbol <--- L ---> expressing the 778 eoEnergyParametersIntervalLength, and the 779 eoEnergyCollectionStartTime is represented by S1, S2, S3, S4, 780 ..., Sx where x is the value of 781 eoEnergyParametersIntervalNumber. 783 - The vertical axis represents the time interval of sampling and 784 the value of eoEnergyConsumed can be obtained at the end of the 785 sampling period. The symbol =========== denotes the duration of 786 the sampling period. 788 | | | =========== | 789 |============ | | | 790 | | | | 791 | |============ | | 792 | | | | 793 | <--- L ---> | <--- L ---> | <--- L ---> | 794 | | | | 795 S1 S2 S3 S4 797 Figure 4 : Period eoEnergyParametersIntervalMode 799 A eoEnergyParametersIntervalMode type of 'period' specifies non- 800 overlapping periodic measurements. Therefore, the next 801 eoEnergyCollectionStartTime is equal to the previous 802 eoEnergyCollectionStartTime plus 803 eoEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... 805 |============ | 806 | | 807 | <--- L ---> | 808 | | 809 | |============ | 810 | | | 811 | | <--- L ---> | 812 | | | 813 | | |============ | 814 | | | | 815 | | | <--- L ---> | 816 | | | | 817 | | | |============ | 818 | | | | | 819 | | | | <--- L ---> | 820 S1 | | | | 821 | | | | 822 | | | | 823 S2 | | | 824 | | | 825 | | | 826 S3 | | 827 | | 828 | | 829 S4 831 Figure 5 : Sliding eoEnergyParametersIntervalMode 833 A eoEnergyParametersIntervalMode type of 'sliding' specifies 834 overlapping periodic measurements. 836 | | 837 |========================= | 838 | | 839 | | 840 | | 841 | <--- Total length ---> | 842 | | 843 S1 845 Figure 6 : Total eoEnergyParametersIntervalMode 847 A eoEnergyParametersIntervalMode type of 'total' specifies a 848 continuous measurement since the last reset. The value of 849 eoEnergyParametersIntervalNumber should be (1) one and 850 eoEnergyParametersIntervalLength is ignored. 852 The eoEnergyParametersStatus is used to start and stop energy 853 usage logging. The status of this variable is "active" when 854 all the objects in eoEnergyParametersTable are appropriate which 855 in turn indicates if eoEnergyTable entries exist or not. 857 The eoEnergyTable consists of energy measurements in 858 eoEnergyConsumed, eoEnergyProvided and eoEnergyStored, the units 859 of the measured energy eoEnergyUnitMultiplier, and the maximum 860 observed energy within a window eoEnergyMaxConsumed, 861 eoEnergyMaxProduced. 863 Measurements of the total energy consumed by an Energy Object 864 may suffer from interruptions in the continuous measurement of 865 energy consumption. In order to indicate such interruptions, 866 the object eoEnergyDiscontinuityTime is provided for indicating 867 the time of the last interruption of total energy measurement. 868 eoEnergyDiscontinuityTime shall indicate the sysUpTime [RFC3418] 869 when the device was reset. 871 The following example illustrates the eoEnergyTable and 872 eoEnergyParametersTable: 874 First, in order to estimate energy, a time interval to sample 875 energy should be specified, i.e. 876 eoEnergyParametersIntervalLength can be set to "900 seconds" or 877 15 minutes and the number of consecutive intervals over which 878 the maximum energy is calculated 879 (eoEnergyParametersIntervalNumber) as "10". The sampling rate 880 internal to the Energy Object for measurement of power usage 881 (eoEnergyParametersSampleRate) can be "1000 milliseconds", as 882 set by the Energy Object as a reasonable value. Then, the 883 eoEnergyParametersStatus is set to active (value 1) to indicate 884 that the Energy Object should start monitoring the usage per the 885 eoEnergyTable. 887 The indices for the eoEnergyTable are eoEnergyParametersIndex 888 which identifies the index for the setting of energy measurement 889 collection Energy Object, and eoEnergyCollectionStartTime, which 890 denotes the start time of the energy measurement interval based 891 on sysUpTime [RFC3418]. The value of eoEnergyComsumed is the 892 measured energy consumption over the time interval specified 893 (eoEnergyParametersIntervalLength) based on the Energy Object 894 internal sampling rate (eoEnergyParametersSampleRate). While 895 choosing the values for the eoEnergyParametersIntervalLength and 896 eoEnergyParametersSampleRate, it is recommended to take into 897 consideration either the network element resources adequate to 898 process and store the sample values, and the mechanism used to 899 calculate the eoEnergyConsumed. The units are derived from 900 eoEnergyUnitMultiplier. For example, eoEnergyConsumed can be 901 "100" with eoEnergyUnitMultiplier equal to 0, the measured 902 energy consumption of the Energy Object is 100 watt-hours. The 903 eoEnergyMaxConsumed is the maximum energy observed and that can 904 be "150 watt-hours". 906 The eoEnergyTable has a buffer to retain a certain number of 907 intervals, as defined by eoEnergyParametersIntervalNumber. 908 If the default value of "10" is kept, then the eoEnergyTable 909 contains 10 energy measurements, including the maximum. 911 Here is a brief explanation of how the maximum energy can be 912 calculated. The first observed energy measurement value is 913 taken to be the initial maximum. With each subsequent 914 measurement, based on numerical comparison, maximum energy may 915 be updated. The maximum value is retained as long as the 916 measurements are taking place. Based on periodic polling of 917 this table, an NMS could compute the maximum over a longer 918 period, i.e. a month, 3 months, or a year. 920 5.6. Fault Management 922 [EMAN-REQ] specifies requirements about Power States such as 923 "the current power state" , "the time of the last state change", 924 "the total time spent in each state", "the number of transitions 925 to each state" etc. Some of these requirements are fulfilled 926 explicitly by MIB objects such as eoPowerOperState, 927 eoPowerStateTotalTime and eoPowerStateEnterCount. Some of the 928 other requirements are met via the SNMP NOTIFICATION mechanism. 929 eoPowerStateChange SNMP notification which is generated when the 930 value(s) of ,eoPowerStateIndex, eoPowerOperState, 931 eoPowerAdminState have changed. 933 6. Discovery 935 It is foreseen that most Energy Objects will require the 936 implementation of the ENERGY-AWARE MIB [EMAN-AWARE-MIB] as a 937 prerequisite for this MIB module. In such a case, eoPowerTable 938 of the EMAN-MON-MIB is a sparse extension of the eoTable of 939 ENERGY-AWARE-MIB. Every Energy Object MUST implement 940 entPhysicalIndex, entPhysicalUUID and entPhysicalName from the 941 ENTITY-MIB [RFC6933]. As the primary index for the Energy 942 Object, entPhysicalIndex is used. 944 The NMS must first poll the ENERGY-AWARE-MIB module [EMAN-AWARE- 945 MIB], if available, in order to discover all the Energy Objects 946 and the relationships between those (notion of Parent/Child). 947 In the ENERGY-AWARE-MIB module tables, the Energy Objects are 948 indexed by the entPhysicalIndex. 950 If an implementation of the ENERGY-AWARE-MIB module is available 951 in the local SNMP context, for the same Energy Object, the 952 entPhysicalIndex value (EMAN-AWARE-MIB) shall be used. The 953 entPhysicalIndex characterizes the Energy Object in the 954 energyObjectMib and the powerAttributesMIB MIB modules (this 955 document). 957 From there, the NMS must poll the eoPowerStateTable (specified 958 in the energyObjectMib module in this document), which 959 enumerates, amongst other things, the maximum power usage. As 960 the entries in eoPowerStateTable table are indexed by the 961 Energy Object ( entPhysicalIndex), by the Power State Set 962 (eoPowerStateIndex), the maximum power usage is discovered per 963 Energy Object, and the power usage per Power State of the Power 964 State Set. In other words, polling the eoPowerStateTable allows 965 the discovery of each Power State within every Power State Set 966 supported by the Energy Object. 968 If the Energy Object is an Aggregator or a Proxy, the MIB module 969 would be populated with the Energy Object Parent and Children 970 information, which have their own Energy Object index value 971 (entPhysicalIndex). However, the parent/child relationship must 972 be discovered thanks to the ENERGY-AWARE-MIB module. 974 Finally, the NMS can monitor the power attributes thanks to the 975 powerAttributesMIB MIB module, which reuses the entPhysicalIndex 976 to index the Energy Object. 978 7. Link with the other IETF MIBs 980 7.1. Link with the ENTITY-MIB and the ENTITY-SENSOR MIB 982 RFC 4133 [RFC4133] defines the ENTITY-MIB module that lists the 983 physical entities of a networking device (router, switch, etc.) 984 and those physical entities indexed by entPhysicalIndex. From 985 an energy-management standpoint, the physical entities that 986 consume or produce energy are of interest. 988 RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that 989 provides a standardized way of obtaining information (current 990 value of the sensor, operational status of the sensor, and the 991 data units precision) from sensors embedded in networking 992 devices. Sensors are associated with each index of 993 entPhysicalIndex of the ENTITY-MIB [RFC4133]. While the focus 994 of the Power and Energy Monitoring MIB is on measurement of 995 power usage of networking equipment indexed by the ENTITY-MIB, 996 this MIB proposes a customized power scale for power measurement 997 and different power state states of networking equipment, and 998 functionality to configure the power state states. 1000 When this MIB module is used to monitor the power usage of 1001 devices like routers and switches, the ENTITY-MIB and ENTITY- 1002 SENSOR MIB SHOULD be implemented. In such cases, the Energy 1003 Objects are modeled by the entPhysicalIndex through the 1004 entPhysicalEntity MIB object specified in the eoTable in the 1005 ENERGY-AWARE-MIB MIB module [EMAN-AWARE-MIB]. 1007 However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI 1008 C12.x accuracy classes required for electricity (i.e., 1%, 2%, 1009 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] 1010 represents "The number of decimal places of precision in fixed- 1011 point sensor values returned by the associated entPhySensorValue 1012 object". The ANSI and IEC Standards are used for power 1013 measurement and these standards require that we use an accuracy 1014 class, not the scientific-number precision model specified in 1015 RFC3433. The eoPowerAccuracy MIB object models this accuracy. 1016 Note that eoPowerUnitMultipler represents the scale factor per 1017 IEC 62053-21 [IEC.62053-21] and IEC 62053-22 [IEC.62053-22], 1018 which is a more logical representation for power measurements 1019 (compared to entPhySensorScale), with the mantissa and the 1020 exponent values X * 10 ^ Y. 1022 Power measurements specifying the qualifier 'UNITS' for each 1023 measured value in watts are used in the LLDP-EXT-MED-MIB, POE 1024 [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier 1025 is used for the power measurement values. 1027 One cannot assume that the ENTITY-MIB and ENTITY-SENSOR MIB are 1028 implemented for all Energy Objects that need to be monitored. A 1029 typical example is a converged building gateway, monitoring 1030 several other devices in the building, doing the proxy between 1031 SNMP and a protocol like BACNET. Another example is the home 1032 energy controller. In such cases, the eoPhysicalEntity value 1033 contains the zero value, thanks to PhysicalIndexOrZero textual 1034 convention. 1036 The eoPower is similar to entPhySensorValue [RFC3433] and the 1037 eoPowerUnitMultipler is similar to entPhySensorScale. 1039 7.2. Link with the ENTITY-STATE MIB 1041 For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE 1042 MIB [RFC4268] specifies the operational states (entStateOper: 1043 unknown, enabled, disabled, testing), the alarm (entStateAlarm: 1044 unknown, underRepair, critical, major, minor, warning, 1045 indeterminate) and the possible values of standby states 1046 (entStateStandby: unknown, hotStandby, coldStandby, 1047 providingService). 1049 From a power monitoring point of view, in contrast to the entity 1050 operational states of entities, Power States are required, as 1051 proposed in the Power and Energy Monitoring MIB module. Those 1052 Power States can be mapped to the different operational states 1053 in the ENTITY-STATE MIB, if a formal mapping is required. For 1054 example, the entStateStandby "unknown", "hotStandby", 1055 "coldStandby", states could map to the Power State "unknown", 1056 "ready", "standby", respectively, while the entStateStandby 1057 "providingService" could map to any "low" to "high" Power State. 1059 7.3. Link with the POWER-OVER-ETHERNET MIB 1061 Power-over-Ethernet MIB [RFC3621] provides an energy monitoring 1062 and configuration framework for power over Ethernet devices. 1063 The RFC introduces a concept of a port group on a switch to 1064 define power monitoring and management policy and does not use 1065 the entPhysicalIndex as the index. Indeed, the 1066 pethMainPseConsumptionPower is indexed by the 1067 pethMainPseGroupIndex, which has no mapping with the 1068 entPhysicalIndex. 1070 One cannot assume that the Power-over-Ethernet MIB is 1071 implemented for all Energy Objects that need to be monitored. 1072 A typical example is a converged building gateway, monitoring 1073 several other devices in the building, doing the proxy between 1074 SNMP and a protocol like BACNET. Another example is the home 1075 energy controller. In such cases, the eoethPortIndex and 1076 eoethPortGrpIndex values contain the zero value, thanks to new 1077 PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero 1078 conventions. 1080 However, if the Power-over-Ethernet MIB [RFC3621] is supported, 1081 the Energy Object eoethPortIndex and eoethPortGrpIndex contain 1082 the pethPsePortIndex and pethPsePortGroupIndex, respectively. 1084 As a consequence, the entPhysicalIndex MIB object has been kept 1085 as the unique Energy Object index. 1087 Note that, even though the Power-over-Ethernet MIB [RFC3621] was 1088 created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse 1089 the precision notion from the ENTITY-SENSOR MIB, i.e. the 1090 entPhySensorPrecision MIB object. 1092 7.4. Link with the UPS MIB 1094 To protect against unexpected power disruption, data centers and 1095 buildings make use of Uninterruptible Power Supplies (UPS). To 1096 protect critical assets, a UPS can be restricted to a particular 1097 subset or domain of the network. UPS usage typically lasts only 1098 for a finite period of time, until normal power supply is 1099 restored. Planning is required to decide on the capacity of the 1100 UPS based on output power and duration of probable power outage. 1101 To properly provision UPS power in a data center or building, it 1102 is important to first understand the total demand required to 1103 support all the entities in the site. This demand can be 1104 assessed and monitored via the Power and Energy Monitoring MIB. 1106 UPS MIB [RFC1628] provides information on the state of the UPS 1107 network. Implementation of the UPS MIB is useful at the 1108 aggregate level of a data center or a building. The MIB module 1109 contains several groups of variables: 1111 - upsIdent: Identifies the UPS entity (name, model, etc.). 1113 - upsBattery group: Indicates the battery state 1114 (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) 1116 - upsInput group: Characterizes the input load to the UPS 1117 (number of input lines, voltage, current, etc.). 1119 - upsOutput: Characterizes the output from the UPS (number of 1120 output lines, voltage, current, etc.) 1122 - upsAlarms: Indicates the various alarm events. 1124 The measurement of power in the UPS MIB is in Volts, Amperes and 1125 Watts. The units of power measurement are RMS volts and RMS 1126 Amperes. They are not based on the EntitySensorDataScale and 1127 EntitySensorDataPrecision of ENTITY-SENSOR-MIB. 1129 Both the Power and Energy Monitoring MIB and the UPS MIB may be 1130 implemented on the same UPS SNMP agent, without conflict. In 1131 this case, the UPS device itself is the Energy Object Parent and 1132 any of the UPS meters or submeters are the Energy Object 1133 Children. 1135 7.5. Link with the LLDP and LLDP-MED MIBs 1137 The LLDP Protocol is a Data Link Layer protocol used by network 1138 devices to advertise their identities, capabilities, and 1139 interconnections on a LAN network. 1141 The Media Endpoint Discovery is an enhancement of LLDP, known as 1142 LLDP-MED. The LLDP-MED enhancements specifically address voice 1143 applications. LLDP-MED covers 6 basic areas: capability 1144 discovery, LAN speed and duplex discovery, network policy 1145 discovery, location identification discovery, inventory 1146 discovery, and power discovery. 1148 Of particular interest to the current MIB module is the power 1149 discovery, which allows the endpoint device (such as a PoE 1150 phone) to convey power requirements to the switch. In power 1151 discovery, LLDP-MED has four Type Length Values (TLVs): power 1152 type, power source, power priority and power value. 1153 Respectively, those TLVs provide information related to the type 1154 of power (power sourcing entity versus powered device), how the 1155 device is powered (from the line, from a backup source, from 1156 external power source, etc.), the power priority (how important 1157 is it that this device has power?), and how much power the 1158 device needs. 1160 The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] 1161 actually comes from the Power-over-Ethernet MIB [RFC3621]. If 1162 the Power-over-Ethernet MIB [RFC3621] is supported, the exact 1163 value from the pethPsePortPowerPriority [RFC3621] is copied over 1164 in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise 1165 the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From 1166 the Power and Energy Monitoring MIB, it is possible to identify 1167 the pethPsePortPowerPriority [RFC3621], thanks to the 1168 eoethPortIndex and eoethPortGrpIndex. 1170 The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to 1171 eoPowerOrigin in indicating if the power for an attached device 1172 is local or from a remote device. If the LLDP-MED MIB is 1173 supported, the following mapping can be applied to the 1174 eoPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and 1175 local(3) can be mapped to remote(2) and self(1), respectively. 1177 8. Implementation Scenario 1178 This section provides an illustrative example scenario for the 1179 implementation of the Energy Object, including Energy Object 1180 Parent and Energy Object Child relationships. 1182 Example Scenario of a campus network: Switch with PoE Endpoints 1183 with further connected devices. 1185 The campus network consists of switches that provide LAN 1186 connectivity. The switch with PoE ports is located in wiring 1187 closet. PoE IP phones are connected to the switch. The IP 1188 phones draw power from the PoE ports of the switch. In 1189 addition, a PC is daisy-chained from the IP phone for LAN 1190 connectivity. 1192 The IP phone consumes power from the PoE switch, while the PC 1193 consumes power from the wall outlet. 1195 The switch has implementations of ENTITY-MIB [RFC6933] and 1196 ENERGY-AWARE MIB [EMAN-AWARE-MIB] while the PC does not have 1197 implementation of the ENTITY-MIB, but has an implementation of 1198 ENERGY-AWARE MIB [EMAN-AWARE-MIB]. The switch has the following 1199 attributes, entPhysicalIndex "1", and entPhysicalUUID "UUID 1200 1000". The power usage of the switch is "440 Watts". The 1201 switch does not have an Energy Object Parent. 1203 The PoE switch port has the following attributes: The switch 1204 port has entPhysicalIndex "3", and entPhysicalUUID is "UUID 1205 1000:3". The power metered at the POE switch port is "12 1206 watts". In this example, the POE switch port has the switch as 1207 the Energy Object Parent, with its eoParentID of "1000". 1209 The attributes of the PC are given below. The PC does not have 1210 an entPhysicalIndex, and the entPhysicalUUID is "UUID 1000:57 ". 1211 The PC has an Energy Object Parent, i.e. the switch port whose 1212 entPhysicalUUID is "UUID 1000:3". The power usage of the PC is 1213 "120 Watts" and is communicated to the switch port. 1215 This example illustrates the important distinction between the 1216 Energy Object Children: The IP phone draws power from the 1217 switch, while the PC has LAN connectivity from the phone, but is 1218 powered from the wall outlet. However, the Energy Object Parent 1219 sends power control messages to both the Energy Object Children 1220 (IP phone and PC) and the Children react to those messages. 1222 |-------------------------------------------------------| 1223 | Switch | 1224 |=======================================================| 1225 | Switch | Switch | Switch | Switch | 1226 | entPhyIndx | UUID |eoParentId | eoPower | 1227 | ===================================================== | 1228 | 1 | UUID 1000 | null | 440 | 1229 | ===================================================== | 1230 | | 1231 | SWITCH PORT | 1232 | ===================================================== | 1233 | | Switch | Switch | Switch | Switch | 1234 | | Port | Port | Port | Port | 1235 | | entPhyIndx | UUID | eoParentId | eoPower | 1236 | ===================================================== | 1237 | | 3 | UUID 1000:3 | 1000 | 12 | 1238 | ======================================================| 1239 | ^ 1240 | | 1241 |-----------------------------------|------------------- 1242 | 1243 | 1244 POE IP PHONE | 1245 | 1246 | 1247 ====================================================== 1248 | IP phone | IP phone | IP phone | IP phone | 1249 | entPhyIndx | UUID | eoParentID | eoPower | 1250 ====================================================== 1251 | Null | UUID 1000:31| UUID 1000:3 | 12 | 1252 ======================================================= 1253 | 1254 | 1255 PC connected to switch via IP phone | 1256 | 1257 ===================================================== 1258 | PC | PC | PC | PC | 1259 |entPhyIndx | UUID | eoParentID | eoPower | 1260 ===================================================== 1261 | 7 | UUID 1000:57| UUID 1000:3 | 120 | 1262 ===================================================== 1264 Figure 1: Example scenario 1266 9. Structure of the MIB 1268 The primary MIB object in this MIB module is the 1269 energyObjectMibObject. The eoPowerTable table of 1270 energyObjectMibObject describes the power measurement attributes 1271 of an Energy Object entity. The notion of identity of the device 1272 in terms of uniquely identification of the Energy Object and its 1273 relationship to other entities in the network are addressed in 1274 [EMAN-AWARE-MIB]. 1276 Logically, this MIB module is a sparse extension of the 1277 [EMAN-AWARE-MIB] module. Thus the following requirements which 1278 are applied to [EMAN-AWARE-MIB] are also applicable. As a 1279 requirement for this MIB module, [EMAN-AWARE-MIB] should be 1280 implemented and as Module Compliance of ENTITY-MIB V4 [RFC6933] 1281 with respect to entity4CRCompliance should be supported which 1282 requires 3 MIB objects (entPhysicalIndex, entPhysicalName and 1283 entPhysicalUUID ) MUST be implemented. 1285 eoMeterCapabilitiesTable is useful to enable applications to 1286 determine the capabilities supported by the local management 1287 agent. This table indicates the energy monitoring MIB groups 1288 that are supported by the local management system. By reading 1289 the value of this object, it is possible for applications to 1290 know which tables contain the information and are usable without 1291 walking through the table and querying every element which 1292 involves a trial-and-error process. 1294 The power measurement of an Energy Object contains information 1295 describing its power usage (eoPower) and its current power state 1296 (eoPowerOperState). In addition to power usage, additional 1297 information describing the units of measurement 1298 (eoPowerAccuracy, eoPowerUnitMultiplier), how power usage 1299 measurement was obtained (eoPowerMeasurementCaliber), the 1300 source of power (eoPowerOrigin) and the type of power 1301 (eoPowerCurrentTtype) are described. 1303 An Energy Object may contain an optional eoPowerAttributes table 1304 that describes the electrical characteristics associated with 1305 the current power state and usage. 1307 An Energy Object may contain an optional eoEnergyTable to 1308 describe energy measurement information over time. 1310 An Energy Object may also contain optional battery information 1311 associated with this entity. 1313 10. MIB Definitions 1315 -- ************************************************************ 1316 -- 1317 -- 1318 -- This MIB is used to monitor power usage of network 1319 -- devices 1320 -- 1321 -- ************************************************************* 1323 ENERGY-OBJECT-MIB DEFINITIONS ::= BEGIN 1325 IMPORTS 1326 MODULE-IDENTITY, 1327 OBJECT-TYPE, 1328 NOTIFICATION-TYPE, 1329 mib-2, 1330 Integer32, Counter32, TimeTicks 1331 FROM SNMPv2-SMI 1332 TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval, 1333 TimeStamp, TruthValue 1334 FROM SNMPv2-TC 1335 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP 1336 FROM SNMPv2-CONF 1337 OwnerString 1338 FROM RMON-MIB 1339 entPhysicalIndex, PhysicalIndex 1340 FROM ENTITY-MIB; 1342 energyObjectMib MODULE-IDENTITY 1343 LAST-UPDATED "2013102120000Z" -- 21 October2013 1345 ORGANIZATION "IETF EMAN Working Group" 1346 CONTACT-INFO 1347 "WG charter: 1348 http://datatracker.ietf.org/wg/eman/charter/ 1350 Mailing Lists: 1351 General Discussion: eman@ietf.org 1353 To Subscribe: 1354 https://www.ietf.org/mailman/listinfo/eman 1355 Archive: 1356 http://www.ietf.org/mail-archive/web/eman 1358 Editors: 1359 Mouli Chandramouli 1360 Cisco Systems, Inc. 1361 Sarjapur Outer Ring Road 1362 Bangalore 560103 1363 IN 1364 Phone: +91 80 4429 2409 1365 Email: moulchan@cisco.com 1367 Brad Schoening 1368 44 Rivers Edge Drive 1369 Little Silver, NJ 07739 1370 US 1371 Email: brad.schoening@verizon.net 1373 Juergen Quittek 1374 NEC Europe Ltd. 1375 NEC Laboratories Europe 1376 Network Research Division 1377 Kurfuersten-Anlage 36 1378 Heidelberg 69115 1379 DE 1380 Phone: +49 6221 4342-115 1381 Email: quittek@neclab.eu 1383 Thomas Dietz 1384 NEC Europe Ltd. 1385 NEC Laboratories Europe 1386 Network Research Division 1387 Kurfuersten-Anlage 36 1388 69115 Heidelberg 1389 DE 1390 Phone: +49 6221 4342-128 1391 Email: Thomas.Dietz@nw.neclab.eu 1393 Benoit Claise 1394 Cisco Systems, Inc. 1395 De Kleetlaan 6a b1 1396 Degem 1831 1397 Belgium 1398 Phone: +32 2 704 5622 1399 Email: bclaise@cisco.com" 1401 DESCRIPTION 1402 "This MIB is used to monitor power and energy in 1403 devices. 1405 This table sparse extension of the eoTable 1406 from the ENERGY-AWARE-MIB. As a requirement 1407 [EMAN-AWARE-MIB] should be implemented. 1409 Module Compliance of ENTITY-MIB v4 1410 with respect to entity4CRCompliance should 1411 be supported which requires implementation 1412 of 3 MIB objects (entPhysicalIndex, 1413 entPhysicalName and entPhysicalUUID)." 1415 REVISION 1416 "2013102120000Z" -- 21 October2013 1418 DESCRIPTION 1419 "Initial version, published as RFC XXXX." 1421 ::= { mib-2 xxx } 1423 energyObjectMibNotifs OBJECT IDENTIFIER 1424 ::= { energyObjectMib 0 } 1426 energyObjectMibObjects OBJECT IDENTIFIER 1427 ::= { energyObjectMib 1 } 1429 energyObjectMibConform OBJECT IDENTIFIER 1430 ::= { energyObjectMib 2 } 1432 -- Textual Conventions 1434 IANAPowerStateSet ::= TEXTUAL-CONVENTION 1435 STATUS current 1436 DESCRIPTION 1438 "IANAPowerState is a textual convention that describes 1439 Power State Sets and Power State Set Values an Energy Object 1440 supports. IANA has created a registry of Power State supported 1441 by an Energy Object and IANA shall administer the list of Power 1442 State Sets and Power States. 1444 The textual convention assumes that power states in a power 1445 state set are limited to 255 distinct values. For a Power 1446 State Set S, the named number with the value S * 256 is 1447 allocated to indicate the power state set. For a Power State X 1448 in the Power State S, the named number with the value S * 256 1449 + X + 1 is allocated to represent the power state." 1451 REFERENCE 1452 "http://www.iana.org/assignments/eman 1453 RFC EDITOR NOTE: please change the previous URL if this is 1454 not the correct one after IANA assigned it." 1456 SYNTAX INTEGER { 1457 other(0), -- indicates other set 1458 unknown(255), -- unknown power state 1460 ieee1621(256), -- indicates IEEE1621 set 1461 ieee1621On(257), 1462 ieee1621Off(258), 1463 ieee1621Sleep(259), 1465 dmtf(512), -- indicates DMTF set 1466 dmtfOn(513), 1467 dmtfSleepLight(514), 1468 dmtfSleepDeep(515), 1469 dmtfOffHard(516), 1470 dmtfOffSoft(517), 1471 dmtfHibernate(518), 1472 dmtfPowerOffSoft(519), 1473 dmtfPowerOffHard(520), 1474 dmtfMasterBusReset(521), 1475 dmtfDiagnosticInterrapt(522), 1476 dmtfOffSoftGraceful(523), 1477 dmtfOffHardGraceful(524), 1478 dmtfMasterBusResetGraceful(525), 1479 dmtfPowerCycleOffSoftGraceful(526), 1480 dmtfPowerCycleHardGraceful(527), 1482 eman(1024), -- indicates EMAN set 1483 emanmechoff(1025), 1484 emansoftoff(1026), 1485 emanhibernate(1027), 1486 emansleep(1028), 1487 emanstandby(1029), 1488 emanready(1030), 1489 emanlowMinus(1031), 1490 emanlow(1032), 1491 emanmediumMinus(1033), 1492 emanmedium(1034), 1493 emanhighMinus(1035), 1494 emanhigh(1036) 1495 } 1497 UnitMultiplier ::= TEXTUAL-CONVENTION 1498 STATUS current 1499 DESCRIPTION 1500 "The Unit Multiplier is an integer value that represents 1501 the IEEE 61850 Annex A units multiplier associated with 1502 the integer units used to measure the power or energy. 1504 For example, when used with eoPowerUnitMultiplier, -3 1505 represents 10^-3 or milliwatts." 1506 REFERENCE 1507 "The International System of Units (SI), 1508 National Institute of Standards and Technology, 1509 Spec. Publ. 330, August 1991." 1510 SYNTAX INTEGER { 1511 yocto(-24), -- 10^-24 1512 zepto(-21), -- 10^-21 1513 atto(-18), -- 10^-18 1514 femto(-15), -- 10^-15 1515 pico(-12), -- 10^-12 1516 nano(-9), -- 10^-9 1517 micro(-6), -- 10^-6 1518 milli(-3), -- 10^-3 1519 units(0), -- 10^0 1520 kilo(3), -- 10^3 1521 mega(6), -- 10^6 1522 giga(9), -- 10^9 1523 tera(12), -- 10^12 1524 peta(15), -- 10^15 1525 exa(18), -- 10^18 1526 zetta(21), -- 10^21 1527 yotta(24) -- 10^24 1528 } 1530 -- Objects 1532 eoMeterCapabilitiesTable OBJECT-TYPE 1533 SYNTAX SEQUENCE OF EoMeterCapabilitiesEntry 1534 MAX-ACCESS not-accessible 1535 STATUS current 1536 DESCRIPTION 1538 "This table is useful for helping applications determine the 1539 monitoring capabilities supported by the local management 1540 agents. It is possible for applications to know which tables 1541 are usable without going through a trial-and-error process." 1542 ::= { energyObjectMibObjects 1 } 1544 eoMeterCapabilitiesEntry OBJECT-TYPE 1545 SYNTAX EoMeterCapabilitiesEntry 1546 MAX-ACCESS not-accessible 1547 STATUS current 1548 DESCRIPTION 1549 "An entry describes the metering capability of an Energy 1550 Object." 1551 INDEX { entPhysicalIndex } 1552 ::= { eoMeterCapabilitiesTable 1 } 1554 EoMeterCapabilitiesEntry ::= SEQUENCE { 1555 eoMeterCapability BITS 1556 } 1558 eoMeterCapability OBJECT-TYPE 1559 SYNTAX BITS { 1560 none(0), 1561 powermetering(1), -- power measurement 1562 energymetering(2), -- energy measurement 1563 powerattributes(3) -- power attributes 1564 } 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "An indication of the Energy monitoring capabilities supported 1569 by this agent. This object use a BITS syntax and indicate the 1570 MIB groups supported by the probe. By reading the value of this 1571 object, it is possible to determine the MIB tables supported. " 1572 ::= { eoMeterCapabilitiesEntry 1 } 1574 eoPowerTable OBJECT-TYPE 1575 SYNTAX SEQUENCE OF EoPowerEntry 1576 MAX-ACCESS not-accessible 1577 STATUS current 1578 DESCRIPTION 1579 "This table lists Energy Objects." 1580 ::= { energyObjectMibObjects 2 } 1582 eoPowerEntry OBJECT-TYPE 1583 SYNTAX EoPowerEntry 1584 MAX-ACCESS not-accessible 1585 STATUS current 1586 DESCRIPTION 1587 "An entry describes the power usage of an Energy Object." 1589 INDEX { entPhysicalIndex } 1590 ::= { eoPowerTable 1 } 1592 EoPowerEntry ::= SEQUENCE { 1594 eoPower Integer32, 1595 eoPowerNameplate Integer32, 1596 eoPowerUnitMultiplier UnitMultiplier, 1597 eoPowerAccuracy Integer32, 1598 eoPowerMeasurementCaliber INTEGER, 1599 eoPowerCurrentType INTEGER, 1600 eoPowerOrigin INTEGER, 1601 eoPowerAdminState IANAPowerStateSet, 1602 eoPowerOperState IANAPowerStateSet, 1603 eoPowerStateEnterReason OwnerString 1604 } 1606 eoPower OBJECT-TYPE 1607 SYNTAX Integer32 1608 UNITS "Watts" 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "This object indicates the power measured for the Energy 1613 Object. For alternating current, this value is obtained 1614 as an average over fixed number of AC cycles. . This 1615 value is specified in SI units of watts with the 1616 magnitude of watts (milliwatts, kilowatts, etc.) 1617 indicated separately in eoPowerUnitMultiplier. The 1618 accuracy of the measurement is specfied in 1619 eoPowerAccuracy. The direction of power flow is indicated 1620 by the sign on eoPower. If the Energy Object is consuming 1621 power, the eoPower value will be positive. If the Energy 1622 Object is producing power, the eoPower value will be 1623 negative. 1625 The eoPower MUST be less than or equal to the maximum 1626 power that can be consumed at the power state specified 1627 by eoPowerState. 1629 The eoPowerMeasurementCaliber object specifies how the 1630 usage value reported by eoPower was obtained. The eoPower 1631 value must report 0 if the eoPowerMeasurementCaliber is 1632 'unavailable'. For devices that can not measure or 1633 report power, this option can be used." 1634 ::= { eoPowerEntry 1 } 1636 eoPowerNameplate OBJECT-TYPE 1637 SYNTAX Integer32 1638 UNITS "Watts" 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This object indicates the rated maximum consumption for 1643 the fully populated Energy Object. The nameplate power 1644 requirements are the maximum power numbers and, in almost 1645 all cases, are well above the expected operational 1646 consumption. The eoPowerNameplate is widely used for 1647 power provisioning. This value is specified in either 1648 units of watts or voltage and current. The units are 1649 therefore SI watts or equivalent Volt-Amperes with the 1650 magnitude (milliwatts, kilowatts, etc.) indicated 1651 separately in eoPowerUnitMultiplier." 1652 ::= { eoPowerEntry 2 } 1654 eoPowerUnitMultiplier OBJECT-TYPE 1655 SYNTAX UnitMultiplier 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The magnitude of watts for the usage value in eoPower 1660 and eoPowerNameplate." 1661 ::= { eoPowerEntry 3 } 1663 eoPowerAccuracy OBJECT-TYPE 1664 SYNTAX Integer32 (0..10000) 1665 UNITS "hundredths of percent" 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This object indicates a percentage value, in 100ths of a 1670 percent, representing the assumed accuracy of the usage 1671 reported by eoPower. For example: The value 1010 means 1672 the reported usage is accurate to +/- 10.1 percent. This 1673 value is zero if the accuracy is unknown or not 1674 applicable based upon the measurement method. 1676 ANSI and IEC define the following accuracy classes for 1677 power measurement: 1678 IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. 1679 ANSI C12.20 class 0.2, 0.5" 1680 ::= { eoPowerEntry 4 } 1682 eoPowerMeasurementCaliber OBJECT-TYPE 1683 SYNTAX INTEGER { 1684 unavailable(1) , 1685 unknown(2), 1686 actual(3) , 1687 estimated(4), 1688 static(5) } 1689 MAX-ACCESS read-only 1690 STATUS current 1691 DESCRIPTION 1692 "This object specifies how the usage value reported by 1693 eoPower was obtained: 1695 - unavailable(1): Indicates that the usage is not 1696 available. In such a case, the eoPower value must be 0 1697 for devices that can not measure or report power this 1698 option can be used. 1700 - unknown(2): Indicates that the way the usage was 1701 determined is unknown. In some cases, entities report 1702 aggregate power on behalf of another device. In such 1703 cases it is not known whether the usage reported is 1704 actual(2), estimated(3) or presumed (4). 1706 - actual(3): Indicates that the reported usage was 1707 measured by the entity through some hardware or direct 1708 physical means. The usage data reported is not presumed 1709 (4) or estimated (3) but is the measured consumption 1710 rate. 1712 - estimated(4): Indicates that the usage was not 1713 determined by physical measurement. The value is a 1714 derivation based upon the device type, state, and/or 1715 current utilization using some algorithm or heuristic. It 1716 is presumed that the entity's state and current 1717 configuration were used to compute the value. 1719 - static(5): Indicates that the usage was not determined 1720 by physical measurement, algorithm or derivation. The 1721 usage was reported based upon external tables, 1722 specifications, and/or model information. For example, a 1723 PC Model X draws 200W, while a PC Model Y draws 210W" 1725 ::= { eoPowerEntry 5 } 1727 eoPowerCurrentType OBJECT-TYPE 1728 SYNTAX INTEGER { 1729 ac(1), 1730 dc(2), 1731 unknown(3) 1732 } 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "This object indicates whether the eoPower for the 1737 Energy Object reports alternating current AC(1), direct 1738 current DC(2), or that the current type is unknown(3)." 1739 ::= { eoPowerEntry 6 } 1741 eoPowerOrigin OBJECT-TYPE 1742 SYNTAX INTEGER { 1743 self (1), 1744 remote (2) 1745 } 1746 MAX-ACCESS read-only 1747 STATUS current 1748 DESCRIPTION 1749 "This object indicates the source of power measurement 1750 and can be useful when modeling the power usage of 1751 attached devices. The power measurement can be performed 1752 by the entity itself or the power measurement of the 1753 entity can be reported by another trusted entity using a 1754 protocol extension. A value of self(1) indicates the 1755 measurement is performed by the entity, whereas remote(2) 1756 indicates that the measurement was performed by another 1757 entity." 1758 ::= { eoPowerEntry 7 } 1760 eoPowerAdminState OBJECT-TYPE 1761 SYNTAX IANAPowerStateSet 1762 MAX-ACCESS read-write 1763 STATUS current 1764 DESCRIPTION 1765 "This object specifies the desired Power State and the 1766 Power State Set for the Energy Object. Note that 1767 other(0) is not a Power State Set and unknown(255) is 1768 not a Power State as such, but simply an indication that 1769 the Power State of the Energy Object is unknown. 1770 Possible values of eoPowerAdminState within the Power 1771 State Set are registered at IANA. 1772 A current list of assignments can be found at 1773 1774 RFC-EDITOR: please check the location after IANA" 1775 ::= { eoPowerEntry 8 } 1777 eoPowerOperState OBJECT-TYPE 1778 SYNTAX IANAPowerStateSet 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1783 "This object specifies the current operational Power 1784 State and the Power State Set for the Energy Object. 1785 other(0) is not a Power State Set and unknown(255) is 1786 not a Power State as such, but simply an indication that 1787 the Power State of the Energy Object is unknown. 1789 Possible values of eoPowerAdminState within the Power 1790 State Set are registered at IANA. 1791 A current list of assignments can be found at 1792 1793 RFC-EDITOR: please check the location after IANA" 1795 ::= { eoPowerEntry 9 } 1797 eoPowerStateEnterReason OBJECT-TYPE 1798 SYNTAX OwnerString 1799 MAX-ACCESS read-write 1800 STATUS current 1801 DESCRIPTION 1802 "This string object describes the reason for the 1803 eoPowerAdminState 1804 transition Alternatively, this string may contain with 1805 the entity that configured this Energy Object to this 1806 Power State." 1807 DEFVAL { "" } 1808 ::= { eoPowerEntry 10 } 1810 eoPowerStateTable OBJECT-TYPE 1811 SYNTAX SEQUENCE OF EoPowerStateEntry 1812 MAX-ACCESS not-accessible 1813 STATUS current 1814 DESCRIPTION 1815 "This table enumerates the maximum power usage, in watts, 1816 for every single supported Power State of each Energy 1817 Object. 1819 This table has an expansion-dependent relationship on the 1820 eoPowerTable, containing rows describing each Power State 1821 for the corresponding Energy Object. For every Energy 1822 Object in the eoPowerTable, there is a corresponding 1823 entry in this table." 1824 ::= { energyObjectMibObjects 3 } 1826 eoPowerStateEntry OBJECT-TYPE 1827 SYNTAX EoPowerStateEntry 1828 MAX-ACCESS not-accessible 1829 STATUS current 1830 DESCRIPTION 1831 "A eoPowerStateEntry extends a corresponding 1832 eoPowerEntry. This entry displays max usage values at 1833 every single possible Power State supported by the Energy 1834 Object. 1835 For example, given the values of a Energy Object 1836 corresponding to a maximum usage of 0 W at the 1837 state 1 (mechoff), 8 W at state 6 (ready), 11 W at state 1838 9 (mediumMinus),and 11 W at state 12 (high): 1840 State MaxUsage Units 1841 1 (mechoff 0 W 1842 2 (softoff) 0 W 1843 3 (hibernate) 0 W 1844 4 (sleep) 0 W 1845 5 (standby) 0 W 1846 6 (ready) 8 W 1847 7 (lowMinus) 8 W 1848 8 (low) 11 W 1849 9 (mediumMinus) 11 W 1850 10 (medium) 11 W 1851 11 (highMinus) 11 W 1852 12 (high) 11 W 1854 Furthermore, this table extends to return the total time 1855 in each Power State, along with the number of times a 1856 particular Power State was entered." 1858 INDEX { entPhysicalIndex, 1859 eoPowerStateIndex 1860 } 1861 ::= { eoPowerStateTable 1 } 1863 EoPowerStateEntry ::= SEQUENCE { 1864 eoPowerStateIndex IANAPowerStateSet, 1865 eoPowerStateMaxPower Integer32, 1866 eoPowerStatePowerUnitMultiplier UnitMultiplier, 1867 eoPowerStateTotalTime TimeTicks, 1868 eoPowerStateEnterCount Counter32 1869 } 1871 eoPowerStateIndex OBJECT-TYPE 1872 SYNTAX IANAPowerStateSet 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 " 1877 This object specifies the index of the Power State of 1878 the Energy Object within a Power State Set. The 1879 semantics of the specific Power State can be obtained 1880 from the Power State Set definition." 1881 ::= { eoPowerStateEntry 1 } 1883 eoPowerStateMaxPower OBJECT-TYPE 1884 SYNTAX Integer32 1885 UNITS "Watts" 1886 MAX-ACCESS read-only 1887 STATUS current 1888 DESCRIPTION 1889 "This object indicates the maximum power for the Energy 1890 Object at the particular Power State. This value is 1891 specified in SI units of watts with the magnitude of the 1892 units (milliwatts, kilowatts, etc.) indicated separately 1893 in eoPowerStatePowerUnitMultiplier. If the maximum power 1894 is not known for a certain Power State, then the value is 1895 encoded as 0xFFFF. 1897 For Power States not enumerated, the value of 1898 eoPowerStateMaxPower might be interpolated by using the 1899 next highest supported Power State." 1900 ::= { eoPowerStateEntry 2 } 1902 eoPowerStatePowerUnitMultiplier OBJECT-TYPE 1903 SYNTAX UnitMultiplier 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The magnitude of watts for the usage value in 1908 eoPowerStateMaxPower." 1910 ::= { eoPowerStateEntry 3 } 1912 eoPowerStateTotalTime OBJECT-TYPE 1913 SYNTAX TimeTicks 1914 MAX-ACCESS read-only 1915 STATUS current 1916 DESCRIPTION 1917 "This object indicates the total time in hundredth 1918 of second that the Energy Object has been in this power 1919 state since the last reset, as specified in the 1920 sysUpTime." 1921 ::= { eoPowerStateEntry 4 } 1923 eoPowerStateEnterCount OBJECT-TYPE 1924 SYNTAX Counter32 1925 MAX-ACCESS read-only 1926 STATUS current 1927 DESCRIPTION 1928 "This object indicates how often the Energy 1929 Object has 1930 entered this power state, since the last reset of the 1931 device as specified in the sysUpTime." 1932 ::= { eoPowerStateEntry 5 } 1934 eoEnergyParametersTable OBJECT-TYPE 1935 SYNTAX SEQUENCE OF EoEnergyParametersEntry 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "This table is used to configure the parameters for 1940 Energy measurement collection in the table 1941 eoEnergyTable. This table allows the configuration of 1942 different measurement settings on the same Energy Object. 1943 Implementation of this table only sense for energy 1944 objects that an eoPowerMeasurementCaliber of actual(3)." 1945 ::= { energyObjectMibObjects 4 } 1947 eoEnergyParametersEntry OBJECT-TYPE 1948 SYNTAX EoEnergyParametersEntry 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "An entry controls an energy measurement in 1953 eoEnergyTable." 1954 INDEX { eoEnergyObjectIndex, eoEnergyParametersIndex } 1955 ::= { eoEnergyParametersTable 1 } 1957 EoEnergyParametersEntry ::= SEQUENCE { 1958 eoEnergyObjectIndex PhysicalIndex, 1959 eoEnergyParametersIndex Integer32, 1960 eoEnergyParametersIntervalLength TimeInterval, 1961 eoEnergyParametersIntervalNumber Integer32, 1962 eoEnergyParametersIntervalMode INTEGER, 1963 eoEnergyParametersIntervalWindow TimeInterval, 1964 eoEnergyParametersSampleRate Integer32, 1965 eoEnergyParametersStatus RowStatus 1966 } 1968 eoEnergyObjectIndex OBJECT-TYPE 1969 SYNTAX PhysicalIndex 1970 MAX-ACCESS not-accessible 1971 STATUS current 1972 DESCRIPTION 1973 "The unique value, to identify the specific Energy Object 1974 on which the measurement is applied, the same index used 1975 in the eoPowerTable to identify the Energy Object." 1976 ::= { eoEnergyParametersEntry 1 } 1978 eoEnergyParametersIndex OBJECT-TYPE 1979 SYNTAX Integer32 (0..2147483647) 1980 MAX-ACCESS read-create 1981 STATUS current 1982 DESCRIPTION 1983 "This object specifies the index of the Energy 1984 Parameters setting for collection of energy measurements 1985 for an Energy Object. An Energy Object can have multiple 1986 eoEnergyParametersIndex, depending on the capability of 1987 the Energy Object" 1988 ::= { eoEnergyParametersEntry 2 } 1990 eoEnergyParametersIntervalLength OBJECT-TYPE 1991 SYNTAX TimeInterval 1992 MAX-ACCESS read-create 1993 STATUS current 1994 DESCRIPTION 1995 "This object indicates the length of time in hundredth of 1996 seconds over which to compute the average 1997 eoEnergyConsumed measurement in the eoEnergyTable table. 1998 The computation is based on the Energy Object's internal 1999 sampling rate of power consumed or produced by the Energy 2000 Object. The sampling rate is the rate at which the Energy 2001 Object can read the power usage and may differ based on 2002 device capabilities. The average energy consumption is 2003 then computed over the length of the interval." 2005 DEFVAL { 90000 } 2006 ::= { eoEnergyParametersEntry 3 } 2008 eoEnergyParametersIntervalNumber OBJECT-TYPE 2009 SYNTAX Integer32 2010 MAX-ACCESS read-create 2011 STATUS current 2012 DESCRIPTION 2014 "The number of intervals maintained in the eoEnergyTable. 2015 Each interval is characterized by a specific 2016 eoEnergyCollectionStartTime, used as an index to the 2017 table eoEnergyTable. Whenever the maximum number of 2018 entries is reached, the measurement over the new interval 2019 replaces the oldest measurement. There is one exception 2020 to this rule: when the eoEnergyMaxConsumed and/or 2021 eoEnergyMaxProduced are in (one of) the two oldest 2022 measurement(s), they are left untouched and the next 2023 oldest measurement is replaced." 2024 DEFVAL { 10 } 2025 ::= { eoEnergyParametersEntry 4 } 2027 eoEnergyParametersIntervalMode OBJECT-TYPE 2028 SYNTAX INTEGER { 2029 period(1), 2030 sliding(2), 2031 total(3) 2032 } 2033 MAX-ACCESS read-create 2034 STATUS current 2035 DESCRIPTION 2036 "A control object to define the mode of interval calculation 2037 for the computation of the average eoEnergyConsumed or 2038 eoEnergyProvided measurement in the eoEnergyTable table. 2040 A mode of period(1) specifies non-overlapping periodic 2041 measurements. 2043 A mode of sliding(2) specifies overlapping sliding windows 2044 where the interval between the start of one interval and 2045 the next is defined in eoEnergyParametersIntervalWindow. 2047 A mode of total(3) specifies non-periodic measurement. In 2048 this mode only one interval is used as this is a 2049 continuous measurement since the last reset. The value of 2050 eoEnergyParametersIntervalNumber should be (1) one and 2051 eoEnergyParametersIntervalLength is ignored. " 2052 ::= { eoEnergyParametersEntry 5 } 2054 eoEnergyParametersIntervalWindow OBJECT-TYPE 2055 SYNTAX TimeInterval 2056 MAX-ACCESS read-create 2057 STATUS current 2058 DESCRIPTION 2059 "The length of the duration window between the starting 2060 time of one sliding window and the next starting time in 2061 hundredth of seconds, in order to compute the average of 2062 eoEnergyConsumed, eoEnergyProvided measurements in the 2063 eoEnergyTable table. This is valid only when the 2064 eoEnergyParametersIntervalMode is sliding(2). The 2065 eoEnergyParametersIntervalWindow value should be a multiple 2066 of eoEnergyParametersSampleRate." 2067 ::= { eoEnergyParametersEntry 6 } 2069 eoEnergyParametersSampleRate OBJECT-TYPE 2070 SYNTAX Integer32 2071 UNITS "Milliseconds" 2072 MAX-ACCESS read-create 2073 STATUS current 2074 DESCRIPTION 2075 "The sampling rate, in milliseconds, at which the Energy 2076 Object should poll power usage in order to compute the 2077 average eoEnergyConsumed, eoEnergyProvided measurements 2078 in the table eoEnergyTable. The Energy Object should 2079 initially set this sampling rate to a reasonable value, 2080 i.e., a compromise between intervals that will provide 2081 good accuracy by not being too long, but not so short 2082 that they affect the Energy Object performance by 2083 requesting continuous polling. If the sampling rate is 2084 unknown, the value 0 is reported. The sampling rate 2085 should be selected so that 2086 eoEnergyParametersIntervalWindow is a multiple of 2087 eoEnergyParametersSampleRate." 2088 DEFVAL { 1000 } 2089 ::= { eoEnergyParametersEntry 7 } 2091 eoEnergyParametersStatus OBJECT-TYPE 2092 SYNTAX RowStatus 2093 MAX-ACCESS read-create 2094 STATUS current 2095 DESCRIPTION 2096 "The status of this row. The eoEnergyParametersStatus is 2097 used to start or stop energy usage logging. An entry 2098 status may not be active(1) unless all objects in the 2099 entry have an appropriate value. If this object is not 2100 equal to active(1), all associated usage-data logged into 2101 the eoEnergyTable will be deleted. The data can be 2102 destroyed by setting up the eoEnergyParametersStatus to 2103 destroy(2)." 2104 ::= {eoEnergyParametersEntry 8 } 2106 eoEnergyTable OBJECT-TYPE 2107 SYNTAX SEQUENCE OF EoEnergyEntry 2108 MAX-ACCESS not-accessible 2109 STATUS current 2110 DESCRIPTION 2111 "This table lists Energy Object energy measurements. 2112 Entries in this table are only created if the 2113 corresponding value of object eoPowerMeasurementCaliber 2114 is active(3), i.e., if the power is actually metered." 2115 ::= { energyObjectMibObjects 5 } 2117 eoEnergyEntry OBJECT-TYPE 2118 SYNTAX EoEnergyEntry 2119 MAX-ACCESS not-accessible 2120 STATUS current 2121 DESCRIPTION 2122 "An entry describing energy measurements." 2123 INDEX { eoEnergyParametersIndex, 2124 eoEnergyCollectionStartTime } 2125 ::= { eoEnergyTable 1 } 2127 EoEnergyEntry ::= SEQUENCE { 2128 eoEnergyCollectionStartTime TimeTicks, 2129 eoEnergyConsumed Integer32, 2130 eoEnergyProvided Integer32, 2131 eoEnergyStored Integer32, 2132 eoEnergyUnitMultiplier UnitMultiplier, 2133 eoEnergyAccuracy Integer32, 2134 eoEnergyMaxConsumed Integer32, 2135 eoEnergyMaxProduced Integer32, 2136 eoEnergyDiscontinuityTime TimeStamp 2137 } 2139 eoEnergyCollectionStartTime OBJECT-TYPE 2140 SYNTAX TimeTicks 2141 UNITS "hundredths of seconds" 2142 MAX-ACCESS not-accessible 2143 STATUS current 2144 DESCRIPTION 2145 "The time (in hundredths of a second) since the 2146 network management portion of the system was last 2147 re-initialized, as specified in the sysUpTime [RFC3418]. 2148 This object specifies the start time of the energy 2149 measurement sample. " 2150 ::= { eoEnergyEntry 1 } 2152 eoEnergyConsumed OBJECT-TYPE 2153 SYNTAX Integer32 2154 UNITS "Watt-hours" 2155 MAX-ACCESS read-only 2156 STATUS current 2157 DESCRIPTION 2158 "This object indicates the energy consumed in units of watt- 2159 hours for the Energy Object over the defined interval. 2160 This value is specified in the common billing units of watt- 2161 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2162 indicated separately in eoEnergyUnitMultiplier." 2163 ::= { eoEnergyEntry 2 } 2165 eoEnergyProvided OBJECT-TYPE 2166 SYNTAX Integer32 2167 UNITS "Watt-hours" 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This object indicates the energy produced in units of watt- 2172 hours for the Energy Object over the defined interval. 2173 This value is specified in the common billing units of watt- 2174 hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2175 indicated separately in eoEnergyUnitMultiplier." 2176 ::= { eoEnergyEntry 3 } 2178 eoEnergyStored OBJECT-TYPE 2179 SYNTAX Integer32 2180 UNITS "Watt-hours" 2181 MAX-ACCESS read-only 2182 STATUS current 2183 DESCRIPTION 2184 "This object indicates the resultant of the energy consumed and 2185 energy produced for an energy object in units of watt-hours for 2186 the Energy Object over the defined interval. This value is 2187 specified in the common billing units of watt-hours 2188 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2189 indicated separately in eoEnergyUnitMultiplier." 2190 ::= { eoEnergyEntry 4 } 2192 eoEnergyUnitMultiplier OBJECT-TYPE 2193 SYNTAX UnitMultiplier 2194 MAX-ACCESS read-only 2195 STATUS current 2196 DESCRIPTION 2197 "This object is the magnitude of watt-hours for the 2198 energy field in eoEnergyConsumed, eoEnergyProvided, 2199 eoEnergyStored, eoEnergyMaxConsumed, and 2200 eoEnergyMaxProduced ." 2201 ::= { eoEnergyEntry 5 } 2203 eoEnergyAccuracy OBJECT-TYPE 2204 SYNTAX Integer32 (0..10000) 2205 UNITS "hundredths of percent" 2206 MAX-ACCESS read-only 2207 STATUS current 2208 DESCRIPTION 2209 "This object indicates a percentage value, in 100ths of a 2210 percent, representing the presumed accuracy of Energy usage 2211 reporting. eoEnergyAccuracy is applicable to all Energy 2212 measurements in the eoEnergyTable. 2214 For example: 1010 means the reported usage is accurate to +/- 2215 10.1 percent. 2216 This value is zero if the accuracy is unknown." 2218 ::= { eoEnergyEntry 6 } 2220 eoEnergyMaxConsumed OBJECT-TYPE 2221 SYNTAX Integer32 2222 UNITS "Watt-hours" 2223 MAX-ACCESS read-only 2224 STATUS current 2225 DESCRIPTION 2226 "This object is the maximum energy ever observed in 2227 eoEnergyConsumed since the monitoring started. This value 2228 is specified in the common billing units of watt-hours 2229 with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) 2230 indicated separately in eoEnergyUnitMultiplier." 2231 ::= { eoEnergyEntry 7 } 2233 eoEnergyMaxProduced OBJECT-TYPE 2234 SYNTAX Integer32 2235 UNITS "Watt-hours" 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "This object is the maximum energy ever observed in 2240 eoEnergyEnergyProduced since the monitoring started. This 2241 value is specified in the units of watt-hours with the 2242 magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated 2243 separately in eoEnergyEnergyUnitMultiplier." 2244 ::= { eoEnergyEntry 8 } 2246 eoEnergyDiscontinuityTime OBJECT-TYPE 2247 SYNTAX TimeStamp 2248 MAX-ACCESS read-only 2249 STATUS current 2250 DESCRIPTION 2252 "The value of sysUpTime [RFC3418] on the most recent 2253 occasion at which any one or more of this entity's energy 2254 counters in this table suffered a discontinuity: 2255 eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If 2256 no such discontinuities have occurred since the last re- 2257 initialization of the local management subsystem, then 2258 this object contains a zero value." 2259 ::= { eoEnergyEntry 9 } 2261 -- Notifications 2263 eoPowerEnableStatusNotification OBJECT-TYPE 2264 SYNTAX TruthValue 2265 MAX-ACCESS read-write 2266 STATUS current 2267 DESCRIPTION "This variable indicates whether the 2268 system produces the following notifications: 2269 eoPowerStateChange. 2271 A false value will prevent these notifications 2272 from being generated." 2273 DEFVAL { false } 2274 ::= { energyObjectMibNotifs 1 } 2276 eoPowerStateChange NOTIFICATION-TYPE 2277 OBJECTS {eoPowerAdminState, eoPowerOperState, 2278 eoPowerStateEnterReason} 2279 STATUS current 2280 DESCRIPTION 2281 "The SNMP entity generates the eoPowerStateChange when 2282 the value(s) of eoPowerAdminState or eoPowerOperState, 2283 in the context of the Power State Set, have changed for 2284 the Energy Object represented by the entPhysicalIndex." 2285 ::= { energyObjectMibNotifs 2 } 2287 -- Conformance 2289 energyObjectMibCompliances OBJECT IDENTIFIER 2290 ::= { energyObjectMib 3 } 2292 energyObjectMibGroups OBJECT IDENTIFIER 2293 ::= { energyObjectMib 4 } 2295 energyObjectMibFullCompliance MODULE-COMPLIANCE 2296 STATUS current 2297 DESCRIPTION 2298 "When this MIB is implemented with support for 2299 read-create, then such an implementation can 2300 claim full compliance. Such devices can then 2301 be both monitored and configured with this MIB. 2303 Module Compliance of [RFC6933] 2304 with respect to entity4CRCompliance should 2305 be supported which requires implementation 2306 of 3 MIB objects (entPhysicalIndex, 2307 entPhysicalName and entPhysicalUUID)." 2309 MODULE -- this module 2310 MANDATORY-GROUPS { 2311 energyObjectMibTableGroup, 2312 energyObjectMibStateTableGroup, 2313 eoPowerEnableStatusNotificationGroup, 2314 energyObjectMibNotifGroup 2315 } 2317 GROUP energyObjectMibEnergyTableGroup 2319 DESCRIPTION "A compliant implementation does not 2320 have to implement. 2322 Module Compliance of [RFC6933] 2323 with respect to entity4CRCompliance should 2324 be supported which requires implementation 2325 of 3 MIB objects (entPhysicalIndex, 2326 entPhysicalName and entPhysicalUUID)." 2328 GROUP energyObjectMibEnergyParametersTableGroup 2330 DESCRIPTION "A compliant implementation does not 2331 have to implement. 2333 Module Compliance of {RFC6933] 2334 with respect to entity4CRCompliance should 2335 be supported which requires implementation 2336 of 3 MIB objects (entPhysicalIndex, 2337 entPhysicalName and entPhysicalUUID)." 2339 GROUP energyObjectMibMeterCapabilitiesTableGroup 2341 DESCRIPTION "A compliant implementation does not 2342 have to implement. 2344 Module Compliance of [RFC6933] 2345 with respect to entity4CRCompliance should 2346 be supported which requires implementation 2347 of 3 MIB objects (entPhysicalIndex, 2348 entPhysicalName and entPhysicalUUID)." 2350 ::= { energyObjectMibCompliances 1 } 2352 energyObjectMibReadOnlyCompliance MODULE-COMPLIANCE 2353 STATUS current 2354 DESCRIPTION 2355 "When this MIB is implemented without support for 2356 read-create (i.e. in read-only mode), then such an 2357 implementation can claim read-only compliance. Such a 2358 device can then be monitored but cannot be 2359 configured with this MIB. 2361 Module Compliance of [RFC6933] 2362 with respect to entity4CRCompliance should 2363 be supported which requires implementation 2364 of 3 MIB objects (entPhysicalIndex, 2365 entPhysicalName and entPhysicalUUID)." 2367 MODULE -- this module 2368 MANDATORY-GROUPS { 2369 energyObjectMibTableGroup, 2370 energyObjectMibStateTableGroup, 2371 energyObjectMibNotifGroup 2372 } 2374 OBJECT eoPowerOperState 2375 MIN-ACCESS read-only 2376 DESCRIPTION 2377 "Write access is not required." 2378 ::= { energyObjectMibCompliances 2 } 2380 -- Units of Conformance 2382 energyObjectMibTableGroup OBJECT-GROUP 2383 OBJECTS { 2384 eoPower, 2385 eoPowerNameplate, 2386 eoPowerUnitMultiplier, 2387 eoPowerAccuracy, 2388 eoPowerMeasurementCaliber, 2389 eoPowerCurrentType, 2390 eoPowerOrigin, 2391 eoPowerAdminState, 2392 eoPowerOperState, 2393 eoPowerStateEnterReason 2394 } 2395 STATUS current 2396 DESCRIPTION 2397 "This group contains the collection of all the objects 2398 related to the Energy Object." 2399 ::= { energyObjectMibGroups 1 } 2401 energyObjectMibStateTableGroup OBJECT-GROUP 2402 OBJECTS { 2403 eoPowerStateMaxPower, 2404 eoPowerStatePowerUnitMultiplier, 2405 eoPowerStateTotalTime, 2406 eoPowerStateEnterCount 2407 } 2408 STATUS current 2409 DESCRIPTION 2410 "This group contains the collection of all the 2411 objects related to the Power State." 2412 ::= { energyObjectMibGroups 2 } 2414 energyObjectMibEnergyParametersTableGroup OBJECT-GROUP 2415 OBJECTS { 2417 eoEnergyParametersIndex, 2418 eoEnergyParametersIntervalLength, 2419 eoEnergyParametersIntervalNumber, 2420 eoEnergyParametersIntervalMode, 2421 eoEnergyParametersIntervalWindow, 2422 eoEnergyParametersSampleRate, 2423 eoEnergyParametersStatus 2424 } 2425 STATUS current 2426 DESCRIPTION 2427 "This group contains the collection of all the objects 2428 related to the configuration of the Energy Table." 2429 ::= { energyObjectMibGroups 3 } 2431 energyObjectMibEnergyTableGroup OBJECT-GROUP 2432 OBJECTS { 2433 -- Note that object 2434 -- eoEnergyCollectionStartTime is not 2435 -- included since it is not-accessible 2437 eoEnergyConsumed, 2438 eoEnergyProvided, 2439 eoEnergyStored, 2440 eoEnergyUnitMultiplier, 2441 eoEnergyAccuracy, 2442 eoEnergyMaxConsumed, 2443 eoEnergyMaxProduced, 2444 eoEnergyDiscontinuityTime 2445 } 2446 STATUS current 2447 DESCRIPTION 2448 "This group contains the collection of all the objects 2449 related to the Energy Table." 2450 ::= { energyObjectMibGroups 4 } 2452 energyObjectMibMeterCapabilitiesTableGroup OBJECT-GROUP 2453 OBJECTS { 2454 eoMeterCapability 2455 } 2456 STATUS current 2457 DESCRIPTION 2458 "This group contains the object indicating the 2459 capability of the Energy Object" 2460 ::= { energyObjectMibGroups 5 } 2462 eoPowerEnableStatusNotificationGroup OBJECT-GROUP 2463 OBJECTS { eoPowerEnableStatusNotification } 2464 STATUS current 2465 DESCRIPTION "The collection of objects which are used 2466 to enable notification." 2467 ::= { energyObjectMibGroups 6 } 2469 energyObjectMibNotifGroup NOTIFICATION-GROUP 2470 NOTIFICATIONS { 2471 eoPowerStateChange 2472 } 2473 STATUS current 2474 DESCRIPTION "This group contains the notifications for 2475 the power and energy monitoring MIB Module." 2476 ::= { energyObjectMibGroups 7 } 2478 END 2480 -- ************************************************************ 2481 -- 2482 -- This MIB module is used to monitor power attributes of 2483 -- networked devices with measurements. 2484 -- 2485 -- This MIB module is an extension of energyObjectMib module. 2486 -- 2487 -- ************************************************************* 2489 POWER- ATTRIBUTES -MIB DEFINITIONS ::= BEGIN 2491 IMPORTS 2492 MODULE-IDENTITY, 2493 OBJECT-TYPE, 2494 mib-2, 2495 Integer32 2496 FROM SNMPv2-SMI 2497 MODULE-COMPLIANCE, 2498 OBJECT-GROUP 2499 FROM SNMPv2-CONF 2500 UnitMultiplier 2501 FROM ENERGY-OBJECT-MIB 2502 OwnerString 2503 FROM RMON-MIB 2504 entPhysicalIndex 2505 FROM ENTITY-MIB; 2507 powerAttributesMIB MODULE-IDENTITY 2509 LAST-UPDATED "2013102120000Z" -- 21 October 2013 2511 ORGANIZATION "IETF EMAN Working Group" 2512 CONTACT-INFO 2513 "WG charter: 2514 http://datatracker.ietf.org/wg/eman/charter/ 2516 Mailing Lists: 2517 General Discussion: eman@ietf.org 2519 To Subscribe: 2520 https://www.ietf.org/mailman/listinfo/eman 2522 Archive: 2523 http://www.ietf.org/mail-archive/web/eman 2525 Editors: 2527 Mouli Chandramouli 2528 Cisco Systems, Inc. 2529 Sarjapur Outer Ring Road 2530 Bangalore 560103 2531 IN 2532 Phone: +91 80 4429 2409 2533 Email: moulchan@cisco.com 2535 Brad Schoening 2536 44 Rivers Edge Drive 2537 Little Silver, NJ 07739 2538 US 2539 Email: brad.schoening@verizon.net 2541 Juergen Quittek 2542 NEC Europe Ltd. 2543 NEC Laboratories Europe 2544 Network Research Division 2545 Kurfuersten-Anlage 36 2546 Heidelberg 69115 2547 DE 2548 Phone: +49 6221 4342-115 2549 Email: quittek@neclab.eu 2551 Thomas Dietz 2552 NEC Europe Ltd. 2553 NEC Laboratories Europe 2554 Network Research Division 2555 Kurfuersten-Anlage 36 2556 69115 Heidelberg 2557 DE 2558 Phone: +49 6221 4342-128 2559 Email: Thomas.Dietz@nw.neclab.eu 2561 Benoit Claise 2562 Cisco Systems, Inc. 2563 De Kleetlaan 6a b1 2564 Degem 1831 2565 Belgium 2566 Phone: +32 2 704 5622 2567 Email: bclaise@cisco.com" 2569 DESCRIPTION 2570 "This MIB is used to report AC power attributes in 2571 devices. The table is a sparse augmentation of the 2572 eoPowerTable table from the energyObjectMib module. 2573 Both three-phase and single-phase power 2574 configurations are supported. 2576 As a requirement for this MIB module, 2577 [EMAN-AWARE-MIB] should be implemented. 2579 Module Compliance of ENTITY-MIB v4 2580 with respect to entity4CRCompliance should 2581 be supported which requires implementation 2582 of 3 MIB objects (entPhysicalIndex, 2583 entPhysicalName and entPhysicalUUID)." 2585 REVISION 2587 "2013102120000Z" -- 21 October 2013 2589 DESCRIPTION 2590 "Initial version, published as RFC YYY." 2592 ::= { mib-2 yyy } 2594 powerAttributesMIBConform OBJECT IDENTIFIER 2595 ::= { powerAttributesMIB 0 } 2597 powerAttributesMIBObjects OBJECT IDENTIFIER 2598 ::= { powerAttributesMIB 1 } 2600 -- Objects 2602 eoACPwrAttributesTable OBJECT-TYPE 2603 SYNTAX SEQUENCE OF EoACPwrAttributesEntry 2604 MAX-ACCESS not-accessible 2605 STATUS current 2606 DESCRIPTION 2607 "This table defines power attributes measurements for 2608 supported entPhysicalIndex entities. It is a sparse 2609 extension of the eoPowerTable." 2610 ::= { powerAttributesMIBObjects 1 } 2612 eoACPwrAttributesEntry OBJECT-TYPE 2613 SYNTAX EoACPwrAttributesEntry 2614 MAX-ACCESS not-accessible 2615 STATUS current 2616 DESCRIPTION 2617 "This is a sparse extension of the eoPowerTable with 2618 entries for power attributes measurements or 2619 configuration. Each measured value corresponds to an 2620 attribute in IEC 61850-7-4 for non-phase measurements 2621 within the object MMUX." 2623 INDEX {entPhysicalIndex } 2624 ::= { eoACPwrAttributesTable 1 } 2626 EoACPwrAttributesEntry ::= SEQUENCE { 2627 eoACPwrAttributesConfiguration INTEGER, 2628 eoACPwrAttributesAvgVoltage Integer32, 2629 eoACPwrAttributesAvgCurrent Integer32, 2630 eoACPwrAttributesFrequency Integer32, 2631 eoACPwrAttributesPowerUnitMultiplier UnitMultiplier, 2632 eoACPwrAttributesPowerAccuracy Integer32, 2633 eoACPwrAttributesTotalActivePower Integer32, 2634 eoACPwrAttributesTotalReactivePower Integer32, 2635 eoACPwrAttributesTotalApparentPower Integer32, 2636 eoACPwrAttributesTotalPowerFactor Integer32, 2637 eoACPwrAttributesThdAmpheres Integer32, 2638 eoACPwrAttributesThdVoltage Integer32 2639 } 2641 eoACPwrAttributesConfiguration OBJECT-TYPE 2642 SYNTAX INTEGER { 2643 sngl(1), 2644 del(2), 2645 wye(3) 2646 } 2648 MAX-ACCESS read-only 2649 STATUS current 2650 DESCRIPTION 2651 "Configuration describes the physical configurations 2652 of the power supply lines: 2654 * alternating current, single phase (SNGL) 2655 * alternating current, three phase delta (DEL) 2656 * alternating current, three phase Y (WYE) 2658 Three-phase configurations can be either connected in 2659 a triangular delta (DEL) or star Y (WYE) system. WYE 2660 systems have a shared neutral voltage, while DEL 2661 systems do not. Each phase is offset 120 degrees to 2662 each other." 2663 ::= { eoACPwrAttributesEntry 1 } 2665 eoACPwrAttributesAvgVoltage OBJECT-TYPE 2666 SYNTAX Integer32 2667 UNITS "0.1 Volt AC" 2668 MAX-ACCESS read-only 2669 STATUS current 2670 DESCRIPTION 2671 "A measured value for average of the voltage measured 2672 over an integral number of AC cycles For a 3-phase 2673 system, this is the average voltage (V1+V2+V3)/3. IEC 2674 61850-7-4 measured value attribute 'Vol'" 2675 ::= { eoACPwrAttributesEntry 2 } 2677 eoACPwrAttributesAvgCurrent OBJECT-TYPE 2678 SYNTAX Integer32 2679 UNITS "Ampheres" 2680 MAX-ACCESS read-only 2681 STATUS current 2682 DESCRIPTION 2683 "A measured value of the current per phase. IEC 61850- 2684 7-4 attribute 'Amp'" 2685 ::= { eoACPwrAttributesEntry 3 } 2687 eoACPwrAttributesFrequency OBJECT-TYPE 2688 SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz 2689 UNITS "hertz" 2690 MAX-ACCESS read-only 2691 STATUS current 2692 DESCRIPTION 2693 "A measured value for the basic frequency of the AC 2694 circuit. IEC 61850-7-4 attribute 'Hz'." 2695 ::= { eoACPwrAttributesEntry 4 } 2697 eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE 2698 SYNTAX UnitMultiplier 2699 MAX-ACCESS read-only 2700 STATUS current 2701 DESCRIPTION 2702 "The magnitude of watts for the usage value in 2703 eoACPwrAttributesTotalActivePower, 2704 eoACPwrAttributesTotalReactivePower 2705 and eoACPwrAttributesTotalApparentPower measurements. 2706 For 3-phase power systems, this will also include 2707 eoACPwrAttributesPhaseActivePower, 2708 eoACPwrAttributesPhaseReactivePower and 2709 eoACPwrAttributesPhaseApparentPower" 2710 ::= { eoACPwrAttributesEntry 5 } 2712 eoACPwrAttributesPowerAccuracy OBJECT-TYPE 2713 SYNTAX Integer32 (0..10000) 2714 UNITS "hundredths of percent" 2715 MAX-ACCESS read-only 2716 STATUS current 2717 DESCRIPTION 2718 "This object indicates a percentage value, in 100ths of 2719 a percent, representing the presumed accuracy of 2720 active, reactive, and apparent power usage reporting. 2721 For example: 1010 means the reported usage is accurate 2722 to +/- 10.1 percent. This value is zero if the 2723 accuracy is unknown. 2725 ANSI and IEC define the following accuracy classes for 2726 power measurement: IEC 62053-22 & 60044-1 class 0.1, 2727 0.2, 0.5, 1 & 3. 2728 ANSI C12.20 class 0.2 & 0.5" 2729 ::= { eoACPwrAttributesEntry 6 } 2731 eoACPwrAttributesTotalActivePower OBJECT-TYPE 2732 SYNTAX Integer32 2733 UNITS " watts" 2734 MAX-ACCESS read-only 2735 STATUS current 2736 DESCRIPTION 2737 "A measured value of the actual power delivered to or 2738 consumed by the load. IEC 61850-7-4 attribute 'TotW'." 2739 ::= { eoACPwrAttributesEntry 7 } 2741 eoACPwrAttributesTotalReactivePower OBJECT-TYPE 2742 SYNTAX Integer32 2743 UNITS "volt-amperes reactive" 2744 MAX-ACCESS read-only 2745 STATUS current 2746 DESCRIPTION 2747 "A mesured value of the reactive portion of the 2748 apparent power. IEC 61850-7-4 attribute 'TotVAr'." 2749 ::= { eoACPwrAttributesEntry 8 } 2751 eoACPwrAttributesTotalApparentPower OBJECT-TYPE 2752 SYNTAX Integer32 2753 UNITS "volt-amperes" 2754 MAX-ACCESS read-only 2755 STATUS current 2756 DESCRIPTION 2757 "A measured value of the voltage and current which 2758 determines the apparent power. The apparent power is 2759 the vector sum of real and reactive power. 2761 Note: watts and volt-ampheres are equivalent units and 2762 may be combined. IEC 61850-7-4 attribute 'TotVA'." 2763 ::= { eoACPwrAttributesEntry 9 } 2765 eoACPwrAttributesTotalPowerFactor OBJECT-TYPE 2766 SYNTAX Integer32 (-10000..10000) 2767 UNITS "hundredths of percent" 2768 MAX-ACCESS read-only 2769 STATUS current 2770 DESCRIPTION 2771 "A measured value ratio of the real power flowing to 2772 the load versus the apparent power. It is dimensionless 2773 and expressed here as a percentage value in 100ths of a 2774 percent. A power factor of 100% indicates there is no 2775 inductance load and thus no reactive power. Power 2776 Factor can be positive or negative, where the sign 2777 should be in lead/lag (IEEE) form. IEC 61850-7-4 2778 attribute 'TotPF'." 2779 ::= { eoACPwrAttributesEntry 10 } 2781 eoACPwrAttributesThdAmpheres OBJECT-TYPE 2782 SYNTAX Integer32 (0..10000) 2783 UNITS "hundredths of percent" 2784 MAX-ACCESS read-only 2785 STATUS current 2786 DESCRIPTION 2787 "A calculated value for the current total harmonic 2788 distortion (THD). Method of calculation is not 2789 specified. IEC 61850-7-4 attribute 'ThdAmp'." 2790 ::= { eoACPwrAttributesEntry 11 } 2792 eoACPwrAttributesThdVoltage OBJECT-TYPE 2793 SYNTAX Integer32 (0..10000) 2794 UNITS "hundredths of percent" 2795 MAX-ACCESS read-only 2796 STATUS current 2797 DESCRIPTION 2798 "A calculated value for the voltage total harmonic 2799 distortion (THD). Method of calculation is not 2800 specified. IEC 61850-7-4 attribute 'ThdVol'." 2801 ::= { eoACPwrAttributesEntry 12 } 2803 eoACPwrAttributesPhaseTable OBJECT-TYPE 2804 SYNTAX SEQUENCE OF EoACPwrAttributesPhaseEntry 2805 MAX-ACCESS not-accessible 2806 STATUS current 2807 DESCRIPTION 2808 "This table describes 3-phase power attributes 2809 measurements. It is a sparse extension of the 2810 eoACPwrAttributesTable." 2811 ::= { powerAttributesMIBObjects 2 } 2813 eoACPwrAttributesPhaseEntry OBJECT-TYPE 2814 SYNTAX EoACPwrAttributesPhaseEntry 2815 MAX-ACCESS not-accessible 2816 STATUS current 2817 DESCRIPTION 2818 "An entry describes common 3-phase power attributes 2819 measurements. 2821 This optional table describes 3-phase power attributes 2822 measurements, with three entries for each supported 2823 entPhysicalIndex entity. Entities having single phase 2824 power shall not have any entities. 2826 This table describes attributes common to both WYE and 2827 DEL. Entities having single phase power shall not have 2828 any entries here. It is a sparse extension of the 2829 eoACPwrAttributesTable. 2831 These attributes correspond to IEC 61850-7.4 MMXU phase 2832 measurements." 2833 INDEX { entPhysicalIndex, eoPhaseIndex } 2834 ::= { eoACPwrAttributesPhaseTable 1 } 2836 EoACPwrAttributesPhaseEntry ::= SEQUENCE { 2837 eoPhaseIndex Integer32, 2838 eoACPwrAttributesPhaseAvgCurrent Integer32, 2839 eoACPwrAttributesPhaseActivePower Integer32, 2840 eoACPwrAttributesPhaseReactivePower Integer32, 2841 eoACPwrAttributesPhaseApparentPower Integer32, 2842 eoACPwrAttributesPhasePowerFactor Integer32, 2843 eoACPwrAttributesPhaseImpedance Integer32 2844 } 2846 eoPhaseIndex OBJECT-TYPE 2847 SYNTAX Integer32 (0..359) 2848 MAX-ACCESS not-accessible 2849 STATUS current 2850 DESCRIPTION 2851 "A phase angle typically corresponding to 0, 120, 240." 2852 ::= { eoACPwrAttributesPhaseEntry 1 } 2854 eoACPwrAttributesPhaseAvgCurrent OBJECT-TYPE 2855 SYNTAX Integer32 2856 UNITS "Ampheres" 2857 MAX-ACCESS read-only 2858 STATUS current 2859 DESCRIPTION 2860 "A measured value of the current per phase. IEC 61850- 2861 7-4 attribute 'A'" 2862 ::= { eoACPwrAttributesPhaseEntry 2 } 2864 eoACPwrAttributesPhaseActivePower OBJECT-TYPE 2865 SYNTAX Integer32 2866 UNITS " watts" 2867 MAX-ACCESS read-only 2868 STATUS current 2869 DESCRIPTION 2870 "A measured value of the actual power delivered to or 2871 consumed by the load. IEC 61850-7-4 attribute 'W'" 2872 ::= { eoACPwrAttributesPhaseEntry 3 } 2874 eoACPwrAttributesPhaseReactivePower OBJECT-TYPE 2875 SYNTAX Integer32 2876 UNITS "volt-amperes reactive" 2877 MAX-ACCESS read-only 2878 STATUS current 2879 DESCRIPTION 2880 "A measured value of the reactive portion of the 2881 apparent power. IEC 61850-7-4 attribute 'VAr'" 2882 ::= { eoACPwrAttributesPhaseEntry 4 } 2884 eoACPwrAttributesPhaseApparentPower OBJECT-TYPE 2885 SYNTAX Integer32 2886 UNITS "volt-amperes" 2887 MAX-ACCESS read-only 2888 STATUS current 2889 DESCRIPTION 2890 "A measured value of the voltage and current determines 2891 the apparent power. Active plus reactive power equals 2892 the total apparent power. 2894 Note: Watts and volt-ampheres are equivalent units and 2895 may be combined. IEC 61850-7-4 attribute 'VA'." 2896 ::= { eoACPwrAttributesPhaseEntry 5 } 2898 eoACPwrAttributesPhasePowerFactor OBJECT-TYPE 2899 SYNTAX Integer32 (-10000..10000) 2900 UNITS "hundredths of percent" 2901 MAX-ACCESS read-only 2902 STATUS current 2903 DESCRIPTION 2904 "A measured value ratio of the real power flowing to 2905 the load versus the apparent power for this phase. IEC 2906 61850-7-4 attribute 'PF'. Power Factor can be positive 2907 or negative where the sign should be in lead/lag (IEEE) 2908 form." 2909 ::= { eoACPwrAttributesPhaseEntry 6 } 2911 eoACPwrAttributesPhaseImpedance OBJECT-TYPE 2912 SYNTAX Integer32 2913 UNITS "volt-amperes" 2914 MAX-ACCESS read-only 2915 STATUS current 2916 DESCRIPTION 2917 "A measured value of the impedance. IEC 61850-7-4 attribute 2918 'Z'." 2919 ::= { eoACPwrAttributesPhaseEntry 7 } 2921 eoACPwrAttributesDelPhaseTable OBJECT-TYPE 2922 SYNTAX SEQUENCE OF EoACPwrAttributesDelPhaseEntry 2923 MAX-ACCESS not-accessible 2924 STATUS current 2925 DESCRIPTION 2926 "This table describes DEL configuration phase-to-phase 2927 power attributes measurements. This is a sparse 2928 extension of the eoACPwrAttributesPhaseTable." 2929 ::= { powerAttributesMIBObjects 3 } 2931 eoACPwrAttributesDelPhaseEntry OBJECT-TYPE 2932 SYNTAX EoACPwrAttributesDelPhaseEntry 2933 MAX-ACCESS not-accessible 2934 STATUS current 2935 DESCRIPTION 2936 "An entry describes power attributes attributes of a 2937 phase in a DEL 3-phase power system. Voltage 2938 measurements are provided both relative to each other 2939 and zero. 2941 Measured values are from IEC 61850-7-2 MMUX and THD from 2942 MHAI objects. 2944 For phase-to-phase measurements, the eoPhaseIndex is 2945 compared against the following phase at +120 degrees. 2946 Thus, the possible values are: 2948 eoPhaseIndex Next Phase Angle 2949 0 120 2950 120 240 2951 240 0 2952 " 2953 INDEX { entPhysicalIndex, eoPhaseIndex} 2954 ::= { eoACPwrAttributesDelPhaseTable 1} 2956 EoACPwrAttributesDelPhaseEntry ::= SEQUENCE { 2957 eoACPwrAttributesDelPhaseToNextPhaseVoltage Integer32, 2958 eoACPwrAttributesDelThdPhaseToNextPhaseVoltage Integer32, 2959 eoACPwrAttributesDelThdCurrent Integer32 2960 } 2962 eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE 2963 SYNTAX Integer32 2964 UNITS "0.1 Volt AC" 2965 MAX-ACCESS read-only 2966 STATUS current 2967 DESCRIPTION 2968 "A measured value of phase to next phase voltages, where 2969 the next phase is IEC 61850-7-4 attribute 'PPV'." 2970 ::= { eoACPwrAttributesDelPhaseEntry 2 } 2972 eoACPwrAttributesDelThdPhaseToNextPhaseVoltage OBJECT-TYPE 2973 SYNTAX Integer32 (0..10000) 2974 UNITS "hundredths of percent" 2975 MAX-ACCESS read-only 2976 STATUS current 2977 DESCRIPTION 2978 "A calculated value for the voltage total harmonic 2979 disortion for phase to next phase. Method of calculation 2980 is not specified. IEC 61850-7-4 attribute 'ThdPPV'." 2981 ::= { eoACPwrAttributesDelPhaseEntry 3 } 2983 eoACPwrAttributesDelThdCurrent OBJECT-TYPE 2984 SYNTAX Integer32 (0..10000) 2985 UNITS "hundredths of percent" 2986 MAX-ACCESS read-only 2987 STATUS current 2988 DESCRIPTION 2989 "A calculated value for the voltage total harmonic 2990 disortion (THD) for phase to phase. Method of 2991 calculation is not specified. 2992 IEC 61850-7-4 attribute 'ThdPPV'." 2993 ::= { eoACPwrAttributesDelPhaseEntry 4 } 2995 eoACPwrAttributesWyePhaseTable OBJECT-TYPE 2996 SYNTAX SEQUENCE OF EoACPwrAttributesWyePhaseEntry 2997 MAX-ACCESS not-accessible 2998 STATUS current 2999 DESCRIPTION 3000 "This table describes WYE configuration phase-to-neutral 3001 power attributes measurements. This is a sparse 3002 extension of the eoACPwrAttributesPhaseTable." 3003 ::= { powerAttributesMIBObjects 4 } 3005 eoACPwrAttributesWyePhaseEntry OBJECT-TYPE 3006 SYNTAX EoACPwrAttributesWyePhaseEntry 3007 MAX-ACCESS not-accessible 3008 STATUS current 3009 DESCRIPTION 3010 "This table describes measurements of WYE configuration 3011 with phase to neutral power attributes attributes. Three 3012 entries are required for each supported entPhysicalIndex 3013 entry. Voltage measurements are relative to neutral. 3015 This is a sparse extension of the 3016 eoACPwrAttributesPhaseTable. 3018 Each entry describes power attributes attributes of one 3019 phase of a WYE 3-phase power system. 3021 Measured values are from IEC 61850-7-2 MMUX and THD from 3022 MHAI objects." 3023 INDEX { entPhysicalIndex, eoPhaseIndex } 3024 ::= { eoACPwrAttributesWyePhaseTable 1} 3026 EoACPwrAttributesWyePhaseEntry ::= SEQUENCE { 3027 eoACPwrAttributesWyePhaseToNeutralVoltage Integer32, 3028 eoACPwrAttributesWyePhaseCurrent Integer32, 3029 eoACPwrAttributesWyeThdPhaseToNeutralVoltage 3030 Integer32 3031 } 3033 eoACPwrAttributesWyePhaseToNeutralVoltage OBJECT-TYPE 3034 SYNTAX Integer32 3035 UNITS "0.1 Volt AC" 3036 MAX-ACCESS read-only 3037 STATUS current 3038 DESCRIPTION 3039 "A measured value of phase to neutral voltage. IEC 3040 61850-7-4 attribute 'PhV'." 3041 ::= { eoACPwrAttributesWyePhaseEntry 1 } 3043 eoACPwrAttributesWyePhaseCurrent OBJECT-TYPE 3044 SYNTAX Integer32 3045 UNITS "0.1 ampheres AC" 3046 MAX-ACCESS read-only 3047 STATUS current 3048 DESCRIPTION 3049 "A measured value of phase currents. IEC 61850-7-4 3050 attribute 'A'." 3051 ::= { eoACPwrAttributesWyePhaseEntry 2 } 3053 eoACPwrAttributesWyeThdPhaseToNeutralVoltage OBJECT-TYPE 3054 SYNTAX Integer32 (0..10000) 3055 UNITS "hundredths of percent" 3056 MAX-ACCESS read-only 3057 STATUS current 3058 DESCRIPTION 3059 "A calculated value of the voltage total harmonic 3060 distortion (THD) for phase to neutral. IEC 61850-7-4 3061 attribute 'ThdPhV'." 3062 ::= { eoACPwrAttributesWyePhaseEntry 3 } 3064 -- Conformance 3066 powerAttributesMIBCompliances OBJECT IDENTIFIER 3067 ::= { powerAttributesMIB 2 } 3069 powerAttributesMIBGroups OBJECT IDENTIFIER 3070 ::= { powerAttributesMIB 3 } 3072 powerAttributesMIBFullCompliance MODULE-COMPLIANCE 3073 STATUS current 3074 DESCRIPTION 3075 "When this MIB is implemented with support for read-create, 3076 then such an implementation can claim full compliance. 3078 Such devices can then be both monitored and configured with 3079 this MIB. 3081 Module Compliance of [RFC6933] with respect to 3082 entity4CRCompliance should be supported which requires 3083 implementation of 3 MIB objects (entPhysicalIndex, 3084 entPhysicalName and entPhysicalUUID)." 3086 MODULE -- this module 3087 MANDATORY-GROUPS { 3088 powerACPwrAttributesMIBTableGroup 3089 } 3091 GROUP powerACPwrAttributesOptionalMIBTableGroup 3092 DESCRIPTION 3093 "A compliant implementation does not have 3094 to implement." 3096 GROUP powerACPwrAttributesPhaseMIBTableGroup 3097 DESCRIPTION 3098 "A compliant implementation does not have to 3099 implement." 3101 GROUP powerACPwrAttributesDelPhaseMIBTableGroup 3102 DESCRIPTION 3103 "A compliant implementation does not have to 3104 implement." 3106 GROUP powerACPwrAttributesWyePhaseMIBTableGroup 3107 DESCRIPTION 3108 "A compliant implementation does not have to 3109 implement." 3111 ::= { powerAttributesMIBCompliances 1 } 3113 -- Units of Conformance 3115 powerACPwrAttributesMIBTableGroup OBJECT-GROUP 3116 OBJECTS { 3117 -- Note that object entPhysicalIndex is NOT 3118 -- included since it is not-accessible 3119 eoACPwrAttributesAvgVoltage, 3120 eoACPwrAttributesAvgCurrent, 3121 eoACPwrAttributesFrequency, 3122 eoACPwrAttributesPowerUnitMultiplier, 3123 eoACPwrAttributesPowerAccuracy, 3124 eoACPwrAttributesTotalActivePower, 3125 eoACPwrAttributesTotalReactivePower, 3126 eoACPwrAttributesTotalApparentPower, 3127 eoACPwrAttributesTotalPowerFactor 3128 } 3129 STATUS current 3130 DESCRIPTION 3131 "This group contains the collection of all the power 3132 attributes objects related to the Energy Object." 3133 ::= { powerAttributesMIBGroups 1 } 3135 powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP 3136 OBJECTS { 3137 eoACPwrAttributesConfiguration, 3138 eoACPwrAttributesThdAmpheres, 3139 eoACPwrAttributesThdVoltage 3140 } 3141 STATUS current 3142 DESCRIPTION 3143 "This group contains the collection of all the power 3144 attributes objects related to the Energy Object." 3145 ::= { powerAttributesMIBGroups 2 } 3147 powerACPwrAttributesPhaseMIBTableGroup OBJECT-GROUP 3148 OBJECTS { 3149 -- Note that object entPhysicalIndex is 3150 -- NOT included since it is 3151 -- not-accessible 3152 eoACPwrAttributesPhaseAvgCurrent, 3153 eoACPwrAttributesPhaseActivePower, 3154 eoACPwrAttributesPhaseReactivePower, 3155 eoACPwrAttributesPhaseApparentPower, 3156 eoACPwrAttributesPhasePowerFactor, 3157 eoACPwrAttributesPhaseImpedance 3158 } 3159 STATUS current 3160 DESCRIPTION 3161 "This group contains the collection of all 3-phase power 3162 attributes objects related to the Power State." 3163 ::= { powerAttributesMIBGroups 3 } 3165 powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP 3166 OBJECTS { 3167 -- Note that object entPhysicalIndex and 3168 -- eoPhaseIndex are NOT included 3169 -- since they are not-accessible 3170 eoACPwrAttributesDelPhaseToNextPhaseVoltage , 3171 eoACPwrAttributesDelThdPhaseToNextPhaseVoltage, 3172 eoACPwrAttributesDelThdCurrent 3173 } 3174 STATUS current 3175 DESCRIPTION 3176 "This group contains the collection of all power 3177 characteristic attributes of a phase in a DEL 3-phase 3178 power system." 3179 ::= { powerAttributesMIBGroups 4 } 3181 powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP 3182 OBJECTS { 3183 -- Note that object entPhysicalIndex and 3184 -- eoPhaseIndex are NOT included 3185 -- since they are not-accessible 3187 eoACPwrAttributesWyePhaseToNeutralVoltage, 3188 eoACPwrAttributesWyePhaseCurrent, 3189 eoACPwrAttributesWyeThdPhaseToNeutralVoltage 3190 } 3191 STATUS current 3192 DESCRIPTION 3193 "This group contains the collection of all WYE 3194 configuration phase-to-neutral power attributes 3195 measurements." 3196 ::= { powerAttributesMIBGroups 5 } 3198 END 3200 11. Implementation Status 3202 [Note to RFC Editor: Please remove this section and the 3203 reference to [RFC6982] before publication.] 3204 This section records the status of known implementations of the 3205 EMAN-Monitoring MIB at the time of posting of this Internet- 3206 Draft, and is based on a proposal described in [RFC6982]. 3208 The description of implementations in this section is intended 3209 to assist the IETF in its decision processes in progressing 3210 drafts to RFCs. 3212 11.1. SNMP Research 3214 Organization: SNMP Research, Inc. 3216 Maturity: Prototype based upon early drafts of the MIBs. 3217 We anticipate updating it to more recent 3218 documents as development schedules allow. 3220 Coverage: Code was generated to implement all MIB objects 3221 in ENTITY-MIB (Version 4), 3222 ENERGY-OBJECT-CONTEXT-MIB, 3223 ENERGY-OBJECT-MIB, 3224 POWER-CHARACTERISTICS-MIB, 3225 and BATTERY-MIB. 3227 Implementation experience: The documents are implementable. 3229 Comments: Technical comments about the 3230 ENERGY-OBJECT-CONTEXT-MIB, 3231 ENERGY-OBJECT-MIB, and 3232 BATTERY-MIB 3233 were submitted to the EMAN Working Group 3234 E-mail list. 3236 Licensing: Proprietary, royalty licensing 3238 Contact: Alan Luchuk, luchuk at snmp.com 3240 URL: http://www.snmp.com/ 3242 11.2. Cisco Systems 3244 Organization: Cisco Systems, Inc. 3246 Maturity: Prototype based upon early version drafts of 3247 the MIBs. We anticipate updating the MIB 3248 modules as when the drafts are updated. 3250 Coverage: Code was generated to implement all MIB objects 3251 in the ENTITY-MIB (Version 4), and 3252 ENERGY-OBJECT-MIB. 3254 Implementation experience: The MIB modules are implemented 3255 on Cisco router platforms to measure and report 3256 router energy measurements. The documents are 3257 implementable. 3259 Licensing: Proprietary 3261 URL: http://www.cisco.com 3263 12. Security Considerations 3265 Some of the readable objects in these MIB modules (i.e., objects 3266 with a MAX-ACCESS other than not-accessible) may be considered 3267 sensitive or vulnerable in some network environments. It is 3268 thus important to control even GET and/or NOTIFY access to these 3269 objects and possibly to even encrypt the values of these objects 3270 when sending them over the network via SNMP. 3272 There are a number of management objects defined in these MIB 3273 modules with a MAX-ACCESS clause of read-write and/or read- 3274 create. Such objects MAY be considered sensitive or vulnerable 3275 in some network environments. The support for SET operations in 3276 a non-secure environment without proper protection can have a 3277 negative effect on network operations. The following are the 3278 tables and objects and their sensitivity/vulnerability: 3280 - Unauthorized changes to the eoPowerOperState (via 3281 theeoPowerAdminState ) MAY disrupt the power settings of the 3282 differentEnergy Objects, and therefore the state of 3283 functionality of the respective Energy Objects. 3284 - Unauthorized changes to the eoEnergyParametersTable MAY 3285 disrupt energy measurement in the eoEnergyTable table. 3287 SNMP versions prior to SNMPv3 did not include adequate security. 3288 Even if the network itself is secure (for example, by using 3289 IPsec), there is still no secure control over who on the secure 3290 network is allowed to access and GET/SET 3291 (read/change/create/delete) the objects in these MIB modules. 3293 It is RECOMMENDED that implementers consider the security 3294 features as provided by the SNMPv3 framework (see [RFC3410], 3295 section 8), including full support for the SNMPv3 cryptographic 3296 mechanisms (for authentication and privacy). 3298 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3299 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3300 enable cryptographic security. It is then a customer/operator 3301 responsibility to ensure that the SNMP entity giving access to 3302 an instance of these MIB modules is properly configured to give 3303 access to the objects only to those principals (users) that have 3304 legitimate rights to GET or SET (change/create/delete) them. 3306 13. IANA Considerations 3308 13.1. IANA Considerations for the MIB Modules 3310 The MIB modules in this document uses the following IANA- 3311 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers 3312 registry: 3314 Descriptor OBJECT IDENTIFIER value 3315 ---------- ----------------------- 3316 energyObjectMib { mib-2 xxx } 3317 powerAttributesMIB { mib-2 yyy } 3319 Additions to the MIB modules are subject to Expert Review 3320 [RFC5226], i.e., review by one of a group of experts designated 3321 by an IETF Area Director. The group of experts MUST check the 3322 requested MIB objects for completeness and accuracy of the 3323 description. Requests for MIB objects that duplicate the 3324 functionality of existing objects SHOULD be declined. The 3325 smallest available OIDs SHOULD be assigned to the new MIB 3326 objects. The specification of new MIB objects SHOULD follow the 3327 structure specified in Section 10. and MUST be published using 3328 a well-established and persistent publication medium. 3330 13.2. IANA Registration of new Power State Set 3332 The initial set of Power State Sets are specified in [EMAN- 3333 FMWK]. IANA maintains a Textual Convention IANAPowerStateSet 3334 with the initial set of Power State Sets and the Power States 3335 within those Power State Sets as proposed in the [EMAN-FMWK]. 3336 The current version of IANAPowerStateSet Textual convention can 3337 be accessed http://www.iana.org/assignments/IANAPowerStateSet 3339 New Assignments to Power State Sets shall be administered by 3340 IANA and the guidelines and procedures are specified in [EMAN- 3341 FMWK]. 3343 13.2.1. IANA Registration of the IEEE1621 Power State Set 3345 The Internet Assigned Numbers Authority (IANA) has created a new 3346 registry for IEEE1621 Power State Set identifiers and filled it 3347 with the initial list in the Textual Convention 3348 IANAPowerStateSet. 3350 Guidelines for new assignments (or potentially deprecation) for 3351 IEEE1621 Power State Set are specified in [EMAN-FMWK]. 3353 13.2.2. IANA Registration of the DMTF Power State Set 3355 The Internet Assigned Numbers Authority (IANA) has created a new 3356 registry for DMTF Power State Set identifiers and filled it in 3357 the Textual Convention IANAPowerStateSet. 3359 Guidelines for new assignments (or potentially deprecation) for 3360 DMTF Power State Set are specified in [EMAN-FMWK]. 3362 13.2.3. IANA Registration of the EMAN Power State Set 3364 The Internet Assigned Numbers Authority (IANA) has created a new 3365 registry for EMAN Power State Set identifiers and filled it in 3366 the Textual Convention IANAPowerStateSet. 3368 Guidelines for new assignments (or potentially deprecation) for 3369 EMAN Power State Set are specified in [EMAN-FMWK]. 3371 13.3. Updating the Registration of Existing Power State Sets 3373 IANA maintains a Textual Convention IANAPowerStateSet with the 3374 initial set of Power State Sets and the Power States within 3375 those Power State Sets. The current version of Textual 3376 convention can be accessed 3377 http://www.iana.org/assignments/IANAPowerStateSet 3378 With the evolution of standards, over time, it may be important 3379 to deprecate of some of the existing the Power State Sets or 3380 some of the states within a Power State Set. 3382 The registrant shall publish an Internet-draft or an individual 3383 submission with the clear specification on deprecation of Power 3384 State Sets or Power States registered with IANA. The 3385 deprecation shall be administered by IANA through Expert Review 3386 [RFC5226], i.e., review by one of a group of experts designated 3387 by an IETF Area Director. The process should also allow for a 3388 mechanism for cases where others have significant objections to 3389 claims on deprecation of a registration. In cases, where the 3390 registrant cannot be reached, IESG can designate an Expert to 3391 modify the IANA registry for the deprecation. 3393 12. Contributors 3395 This document results from the merger of two initial proposals. 3396 The following persons made significant contributions either in 3397 one of the initial proposals or in this document. 3399 John Parello 3401 Rolf Winter 3403 Dominique Dudkowski 3405 13. Acknowledgment 3407 The authors would like to thank Shamita Pisal for her prototype 3408 of this MIB module, and her valuable feedback. The authors 3409 would like to Michael Brown for improving the text dramatically. 3411 We would like to thank Juergen Schoenwalder for proposing the 3412 design of the Textual Convention for IANAPowerStateSet and Ira 3413 McDonald for his feedback. Thanks for the many comments on the 3414 design of the EnergyTable from Minoru Teraoka and Hiroto Ogaki. 3416 14. Open Issues 3417 OPEN ISSUE 1 check if all the requirements from [EMAN-REQ] are 3418 covered. 3420 15. References 3422 15.2. Normative References 3424 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate 3425 Requirement Levels, BCP 14, RFC 2119, March 1997. 3427 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3428 Schoenwaelder, Ed., "Structure of Management 3429 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3430 1999. 3432 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3433 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3434 STD 58, RFC 2579, April 1999. 3436 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3437 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3438 April 1999. 3440 [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", 3441 RFC3621, December 2003. 3443 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3444 3)", RFC 4133, August 2005. 3446 [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information 3447 Base extension module for TIA-TR41.4 media endpoint 3448 discovery information", July 2005. 3450 [EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili, 3451 "draft-ietf-eman-energy-aware-mib-09 ", work in 3452 progress, July 2013. 3454 15.3. Informative References 3456 [RFC1628] S. Bradner, "UPS Management Information Base", RFC 3457 1628, May 1994 3459 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3460 "Introduction and Applicability Statements for Internet 3461 Standard Management Framework ", RFC 3410, December 3462 2002. 3464 [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. 3465 Waldbusser, "Management Information Base (MIB) for the 3466 Simple Network Management Protocol (SNMP)", RFC3418, 3467 December 2002. 3469 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity 3470 Sensor Management Information Base", RFC 3433, December 3471 2002. 3473 [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 3474 4268, November 2005. 3476 [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, 3477 "Guidelines for Writing an IANA Considerations Section 3478 in RFCs ", BCP 26, RFC 5226, May 2008. 3480 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 3481 M. Chandramouli, " Requirements for Energy Management", 3482 RFC 6988, September 2013. 3484 [EMAN-FMWK] Parello, J. Claise, B., Schoening, B. and Quittek, 3485 J., "Energy Management Framework", draft-ietf-eman- 3486 framework-11, October 2013. 3488 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 3489 Quittek, J. and B. Claise "Energy and Power Monitoring 3490 MIB ", draft-ietf-eman-energy-monitoring-mib-06, July 3491 2013. 3493 [EMAN-AS] Schoening, B., Chandramouli, M. and Nordman, B. 3494 "Energy Management (EMAN) Applicability Statement", 3495 draft-ietf-eman-applicability-statement-04, October 3496 2013. 3498 [RFC6933] A. Bierman, D. Romascanu, J. Quittek and M. 3499 Chandramouli " Entity MIB (Version 4)", RFC 6933, May 3500 2013. 3502 [ACPI] "Advanced Configuration and Power Interface 3503 Specification",http://www.acpi.info/DOWNLOADS/ACPIspec3 3504 0b.pdf 3506 [DMTF] "Power State Management Profile DMTF DSP1027 Version 3507 2.0" December 2009 3508 http://www.dmtf.org/sites/default/files/standards/docum 3509 ents/DSP1027_2.0.0.pdf 3511 [IEEE1621] "Standard for User Interface Elements in Power 3512 Control of Electronic Devices Employed in 3513 Office/Consumer Environments", IEEE 1621, December 3514 2004. 3516 [IEC.61850-7-4] International Electrotechnical Commission, 3517 "Communication networks and systems for power utility 3518 automation Part 7-4: Basic communication structure 3519 Compatible logical node classes and data object 3520 classes", 2010. 3522 [IEC.62053-21] International Electrotechnical Commission, 3523 "Electricity metering equipment (a.c.) Particular 3524 requirements Part 22: Static meters for active energy 3525 (classes 1 and 2)", 2003. 3527 [IEC.62053-22]International Electrotechnical Commission, 3528 "Electricity metering equipment (a.c.) Particular 3529 requirements Part 22: Static meters for active energy 3530 (classes 0,2 S and 0,5 S)", 2003. 3532 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of 3533 Running Code: The Implementation Status Section", RFC 3534 6982, July 2013. 3536 Authors' Addresses 3538 Mouli Chandramouli 3539 Cisco Systems, Inc. 3540 Sarjapur Outer Ring Road 3541 Bangalore 560103 3542 IN 3544 Phone: +91 80 4429 2409 3545 Email: moulchan@cisco.com 3546 Brad Schoening 3547 44 Rivers Edge Drive 3548 Little Silver, NJ 07739 3549 US 3550 Email: brad.schoening@verizon.net 3552 Juergen Quittek 3553 NEC Europe Ltd. 3554 NEC Laboratories Europe 3555 Network Research Division 3556 Kurfuersten-Anlage 36 3557 Heidelberg 69115 3558 DE 3560 Phone: +49 6221 4342-115 3561 Email: quittek@neclab.eu 3563 Thomas Dietz 3564 NEC Europe Ltd. 3565 NEC Laboratories Europe 3566 Network Research Division 3567 Kurfuersten-Anlage 36 3568 Heidelberg 69115 3569 DE 3571 Phone: +49 6221 4342-128 3572 Email: Thomas.Dietz@neclab.eu 3574 Benoit Claise 3575 Cisco Systems, Inc. 3576 De Kleetlaan 6a b1 3577 Diegem 1813 3578 BE 3580 Phone: +32 2 704 5622 3581 Email: bclaise@cisco.com