Network Working Group Internet-Draft M. Chandramouli Intended Status: Standards Track Cisco Systems, Inc. Expires: September 14, 2011 B. Schoening Independent Consultant J. Quittek T. Dietz NEC Europe Ltd. B. Claise Cisco Systems, Inc. March 14, 2011 Power and Energy Monitoring MIB draft-claise-energy-monitoring-mib-07 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on September, 2011. Expires September 14 2011 [Page 1] Internet-Draft March 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Abstract This document defines a subset of the Management Information Base (MIB) for power and energy monitoring of devices. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Table of Contents 1. Introduction.............................................. 4 2. The Internet-Standard Management Framework................ 5 3. Use Cases................................................. 5 4. Terminology............................................... 6 5. Architecture Concepts Applied to the MIB Module........... 6 5.1 Power Monitor Information............................. 6 5.2 Power Monitor States.................................. 6 5.3 Power Monitor Usage Measurement....................... 7 5.4 Optional Power Usage Quality.......................... 8 5.5 Optional Energy Measurement........................... 9 5.6 Optional Battery Information......................... 12 5.7 Fault Management..................................... 12 6. Implementation Scenarios................................. 13 Scenario 1: Switch with PoE Endpoints.................... 13 Expires September 14, 2011 [Page 2] Internet-Draft March 2011 Scenario 2: Switch with PoE Endpoints with Further Connected Devices.................................................. 15 Scenario 3: Switch with Wireless Access Points........... 16 Scenario 4: Network Connected Facilities Gateway......... 18 Scenario 5: Data Center Network.......................... 21 Scenario 6: Switch with Power Distribution Units (PDU)... 23 Scenario 7: Power Consumption of UPS..................... 24 Scenario 8: Power Consumption of Battery-Based Devices... 25 7. Link with the other IETF MIBs............................ 25 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB.. 25 7.2. Link with the ENTITY-STATE MIB...................... 26 7.3. Link with the POWER-OVER-ETHERNET MIB............... 26 7.4. Link with the UPS MIB............................... 27 7.5. Link with the LLDP and LLDP-MED MIBs................ 28 8. Structure of the MIB..................................... 29 9. MIB Definitions.......................................... 30 10. Security Considerations................................. 68 11. IANA Considerations..................................... 69 12. Contributors............................................ 69 13. Acknowledgment.......................................... 69 14. References.............................................. 69 14.1. Normative References............................... 69 14.2. Informative References............................. 70 Expires September 14, 2011 [Page 3] Internet-Draft March 2011 OPEN ISSUES: . The UUID is per box, not per port. So, for example, n the figure 5, the switch port should have pmPowerMonId of 1000, and not 1003 as displayed in the draft. This is a problem. The UUID must be unique within the component inside box. | ============================================================| | | | SWITCH PORT | | =========================================================== | | | Switch | Switch | Switch | Switch | Switch | | | Port | Port | Port | Port | Port | | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower| | | =========================================================== | | | 3 | 12 | UUID 1003 | UUID 1000 | 12 | | | =========================================================== | | ^ | | | | |-----------------------------------|-------------------------| 1. Introduction This document defines a subset of the Management Information Base (MIB) for use in energy management of devices within or connected to communication networks. The MIB modules in this document are designed to provide a model for energy management, which includes monitoring for power state and energy consumption of networked elements. This MIB takes into account the Power Management Architecture [EMAN-FRAMEWORK], which in turn, is based on the Power Monitoring Requirements [EMAN-REQ] . Energy management is applicable to devices in communication networks. Target devices for this specification include (but are not limited to): routers, switches, Power over Ethernet (PoE) endpoints, protocol gateways for building management systems, intelligent meters, home energy gateways, hosts and servers, sensor proxies, etc. Expires September 14, 2011 [Page 4] Internet-Draft March 2011 Where applicable, device monitoring extends to the individual components of the device and to any attached dependent devices. For example: A device can contain components that are independent from a power-state point of view, such as line cards, processor cards, hard drives. A device can also have dependent attached devices, such as a switch with PoE endpoints or a power distribution unit with attached endpoints. Devices and their sub-components may be characterized by the power-related attributes of a physical entity present in the ENTITY MIB, even though the ENTITY MIB compliance is not a requirement due to the variety and broad base of devices concerned with energy management. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies MIB modules that are compliant to SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Use Cases Requirements for power and energy monitoring for networking devices are specified in [EMAN-REQ]. The requirements in [EMAN- REQ] cover devices typically found in communications networks, such as switches, routers, and various connected endpoints. For a power monitoring architecture to be useful, it should also apply to facility meters, power distribution units, gateway proxies for commercial building control, home automation devices, and devices that interface with the utility and/or smart grid. Accordingly, the scope of the MIB modules in this document is broader than that specified in [EMAN-REQ]. Several scenarios that cover these broader use cases are presented later in Section 6 - Implementation Scenarios. Expires September 14, 2011 [Page 5] Internet-Draft March 2011 4. Terminology The definitions of basic terms like Power Monitor, Power Monitor Parent, Power Monitor Child, Power Monitor Meter Domain, Power State, and Manufacturer Power State can be found in the Power Management Architecture [EMAN-FRAMEWORK]. 5. Architecture Concepts Applied to the MIB Module This section describes the concepts specified in the Power Monitor Architecture [EMAN-FRAMEWORK] that pertain to power usage, with specific information related to the MIB module specified in this document. This subsection maps to the section "Architecture High Level Concepts" in the Power Monitoring Architecture [EMAN-FRAMEWORK]. 5.1 Power Monitor Information Refer to the "Power Monitor Information" section in [EMAN- FRAMEWORK] for background information. An energy aware device is considered an instance of a power monitor as defined in the [EMAN-FRAMEWORK]. The Power Monitor information is specified in the MIB module primary table, i.e. the pmTable. Every Power Monitor SHOULD have a printable name pmName, and MUST HAVE a unique Power Monitor index pmIndex, as specified in [POWER-AWARE-MIB]. 5.2 Power Monitor States Refer to the "Power Monitor States" section in [EMAN-FRAMEWORK] for background information. Power States, which represent universal states of power management of a Power Monitor, are specified by the pmPowerState MIB object. Via the pmPowerManufacturerActualPowerState MIB variable, the Manufacturer Power States might be read, in case the Power States specified in this document are not (yet) supported. The Manufacturer Power State name can be read with the pmPowerManufacturerActualPowerState Name MIB variable. When a Power Monitor requires a mapping with the Manufacturer Power State, the Power Monitor configuration is done via the Power State settings, and not directly via the Manufacturer Expires September 14, 2011 [Page 6] Internet-Draft March 2011 Power States, which are read-only. The actual Power State is specified by the pmPowerActualState MIB object, while the pmPowerState MIB object specifies the Power State requested for the Power Monitor. A difference in values between the pmPowerState and pmPowerActualState indicates that the Power Monitor is busy going into the pmPowerState, at which point it will update the content of pmPowerActualState. The MIB object pmPowerState and pmPowerManufacturerMappingId are contained in the pmTable MIB table. The pmPowerStateTable table enumerates the maximum power usage in watts, for every single supported Power State of each Power Monitor. In addition, PowerStateTable provides additional statistics: powerStateEnterCount, the number of times an entity has visited a particular power state, and powerStateTotalTime , the total time spent in a particular power state. The pmPowerStateMappingTable table enumerates the maximum power usage in watts, for every single Manufacturer Power State. Furthermore, this table maps the Manufacturer Power States to the Power States specified in this document (more specifically with the PowerMonitorState textual convention). Finally, this table returns the name of each Manufacturer Power State. In addition, the possible reason for change in power state (due to NMS or CLI) is reported in pmPowerStateEnterReason. 5.3 Power Monitor Usage Measurement Refer to the "Power Monitor Usage Measurement" section in [EMAN- FRAMEWORK] for background information. For a Power Monitor, power usage is reported using pmPower. The magnitude of measurement is based on the pmPowerUnitMultiplier MIB variable, based on the UnitMultiplier Textual Convention (TC). For example, if current power usage of a Power Monitor is 3, it could be 3 W, 3 mW, 3 KW, or 3 MW, depending on the value of pmPowerUnitMultiplier. Note that other measurements throughout the two MIB modules in this document use the same mechanism, including pmPowerStatePowerUnitMultiplier, pmDemandIntervalEnergyUnitMultiplier, and pmACPwrQualityPowerUnitMultiplier. In addition to knowing the usage and magnitude, it is useful to know how a pmPower measurement was obtained. An NMS can use Expires September 14, 2011 [Page 7] Internet-Draft March 2011 this to account for the accuracy and nature of the reading between different implementations. For this pmPowerOrigin describes whether the measurements were made at the device itself or from a remote source. The pmPowerMeasurementCaliber describes the method that was used to measure the power and can distinguish actual or estimated values. There may be devices in the network, which may not be able to measure or report power consumption. For those devices, the object pmPowerMeasurementCaliber shall report that measurement mechanism is "unavailable" and the pmPower measurement shall be "0". The nameplate power rating of a Power Monitor is specified in pmPowerNameplate MIB object. 5.4 Optional Power Usage Quality Refer to the "Optional Power Usage Quality" section in [EMAN- FRAMEWORK] for background information. The optional powerQualityMIB MIB module can be implemented to further describe power usage quality measurement. The powerQualityMIB MIB module adheres closely to the IEC 61850 7-2 standard to describe AC measurements. The powerQualityMIB MIB module contains a primary table, the pmACPwrQualityTable table, that defines power quality measurements for supported pmIndex entities, as a sparse extension of the pmTable (with pmPowerIndex as primary index). This pmACPwrQualityTable table contains such information as the configuration (single phase, DEL 3 phases, WYE 3 phases), voltage, frequency, power accuracy, total active/reactive power/apparent power, amperage, and voltage. In case of 3-phase power, the pmACPwrQualityPhaseTable additional table is populated with power quality measurements per phase (so double indexed by the pmPowerIndex and pmPhaseIndex). This table, which describes attributes common to both WYE and DEL configurations, contains the average current, active/reactive/apparent power, power factor, and impedance. In case of 3-phase power with a DEL configuration, the pmACPwrQualityDelPhaseTable table describes the phase-to-phase power quality measurements, i.e., voltage and current. Expires September 14, 2011 [Page 8] Internet-Draft March 2011 In case of 3-phase power with a Wye configuration, the pmACPwrQualityWyePhaseTable table describes the phase-to-neutral power quality measurements, i.e., voltage and current. 5.5 Optional Energy Measurement Refer to the "Optional Energy Measurement" section in [EMAN- FRAMEWORK] for background information. It is relevant to measure the demand only when there are actual power measurements from a Power Monitor, and not when the power measurement is assumed or predicted as specified in the description clause of the object pmPowerMeasurementCaliber. Two tables are introduced to characterize the energy demand: pmEnergyTable and pmEnergyParametersTable. The pmEnergyParametersTable table consists of parameters defining the duration of the demand intervals in seconds, (pmEnergyParametersIntervalLength), the number of demand intervals kept in the pmEnergyTable, (pmEnergyParametersIntervalNumber), the type of demand intervals (pmEnergyParametersIntervalMode), and a sample rate used to calculate the average (pmEnergyParametersSampleRate). Judicious choice of the SamplingRate will ensure accurate measurement of power while not imposing an excessive polling burden. There are three pmEnergyParametersIntervalMode types used for energy measurement collection: period, sliding, and total. Note that multiple pmEnergyParametersIntervalMode types MAY be configured simultaneously. These three pmEnergyParametersIntervalMode types are illustrated by the following three figures, for which: - The horizontal axis represents the current time, with the symbol <--- L ---> expressing the pmEnergyParametersIntervalLength, and the pmEnergyIntervalStartTime is represented by S1, S2, S3, S4, ..., Sx where x is the value of pmEnergyParametersIntervalNumber. - The vertical axis represents the time interval of sampling and the value of pmEnergyIntervalEnergyUsed can be obtained at the end of the sampling period. The symbol =========== denotes the duration of the sampling period. Expires September 14, 2011 [Page 9] Internet-Draft March 2011 | | | =========== | |============ | | | | | | | | |============ | | | | | | | <--- L ---> | <--- L ---> | <--- L ---> | | | | | S1 S2 S3 S4 Figure 1 : Period pmEnergyParametersIntervalMode A pmEnergyParametersIntervalMode type of 'period' specifies non- overlapping periodic measurements. Therefore, the next pmEnergyIntervalStartTime is equal to the previous pmEnergyIntervalStartTime plus pmEnergyParametersIntervalLength. S2=S1+L; S3=S2+L, ... |============ | | | | <--- L ---> | | | | |============ | | | | | | <--- L ---> | | | | | | |============ | | | | | | | | <--- L ---> | | | | | | | | |============ | | | | | | | | | | <--- L ---> | S1 | | | | | | | | | | | | S2 | | | | | | | | | S3 | | | | | | S4 Figure 2 : Sliding pmEnergyParametersIntervalMode A pmEnergyParametersIntervalMode type of 'sliding' specifies overlapping periodic measurements. Expires September 14, 2011 [Page 10] Internet-Draft March 2011 | | |========================= | | | | | | | | <--- Total length ---> | | | S1 Figure 3 : Total pmEnergyParametersIntervalMode A pmEnergyParametersIntervalMode type of 'total' specifies a continuous measurement since the last reset. The value of pmEnergyParametersIntervalNumber should be (1) one and pmEnergyParametersIntervalLength is ignored. The pmEnergyParametersStatus is useful to specify that the energy measurement is actual and thus to indicate if the pmEnergyTable entries exist or not. The pmDemand Table consists of energy measurements in pmDemandIntervalEnergyUsed, the scale of energy measured, pmDemandIntervalEnergyUnitMultiplier, and the maximum observed demand in a window - pmDemandIntervalMax. Measurements of the total energy consumed by an Power Monitor may suffer from interruptions in the continuous measurement of the current energy consumption. In order to indicate such interruptions, object pmEnergyIntervalDiscontinuityTime is provided for indicating the time of the last interruption of total energy measurement. pmEnergyIntervalDiscontinuityTime shall indicate the sysUpTime when the device was reset. The following example illustrates the pmEnergyTable and pmEnergyParametersTable: First, in order to estimate demand, an interval to sample energy should be specified, i.e. pmEnergyParametersIntervalLength can be "900 seconds" and the number of consecutive intervals over which the maximum demand is calculated (pmEnergyParametersIntervalNumber) as "10". The sampling rate internal to the Power Monitor for measurement of power usage (pmEnergyParametersSampleRate) can be "1000 milliseconds", as set by the Power Monitor as a reasonable value. Then, the pmEnergyParametersStatus is set to active (value 1) to indicate Expires September 14, 2011 [Page 11] Internet-Draft March 2011 that the Power Monitor should start monitoring the usage per the pmEnergyTable. The indices in the pmEnergyTable are pmPowerIndex, which identifies the Power Monitor, and pmDemandIntervalStartTime, which denotes the start time of the demand measurement interval based on sysUpTime. The value of pmDemandIntervalEnergyUsed is the measured energy consumption over the time interval specified (pmEnergyParametersIntervalLength) based on the Power Monitor internal sampling rate (pmEnergyParametersSampleRate). While choosing the values for the pmEnergyParametersIntervalLength and pmEnergyParametersSampleRate, it is recommended to take into consideration either the network element resources adequate to process and store the sample values, and the mechanism used to calculate the pmEnergyIntervalEnergyUsed. The units are derived from pmDemandIntervalPowerUnitMultiplier. For example, pmDemandIntervalPowerUsed can be "100" with pmDemandIntervalPowerUnits equal to 0, the demand is 100 watt- hours. The pmDemandIntervalMax is the maximum demand observed and can be "150 watt-hours". The pmEnergyTable has a buffer to retain a certain number of intervals, as defined by pmEnergyParametersIntervalNumber. If the default value of "10" is kept, then the pmEnergyTable contains 10 demand measurements, including the maximum. Here is a brief explanation of how the maximum demand can be calculated. The first observed demand measurement value is taken to be the initial maximum. With each subsequent measurement, based on numerical comparison, maximum demand may be updated. The maximum value is retained as long as the measurements are taking place. Based on periodic polling of this table, an NMS could compute the maximum over a longer period, i.e. a month, 3 months, or a year. 5.6 Optional Battery Information RFC'EDITOR NOTE: Power consumption of battery enabled devices can be obtained from ... (draft to be posted by Juergen Quittek). 5.7 Fault Management [EMAN-REQ] specifies some requirements about power states such as "the current state - the time of the last change", "the total time spent in each state", "the number of transitions to each state", etc. Such requirements are fulfilled via the Expires September 14, 2011 [Page 12] Internet-Draft March 2011 pmPowerStateChange NOTIFICATION-TYPE. This SNMP notification is generated when the value(s) of Power State has changed for the Power Monitor. 6. Implementation Scenarios The scope of power and energy monitoring consists of devices that consume power within and that are connected to a communications network. These devices include: - Network devices and sub-components: Devices such as routers and switches and their sub-components. - Network attached endpoints: Devices that use the communications network, such as endpoints, PCs, and facility gateways that proxy energy monitor and control for commercial buildings or home automation. - Network attached meters or supplies: Devices that can monitor the electrical supply, such as smart meters or Universal Power Supplies (UPS) that meter and provide availability. This section provides illustrative examples that model different scenarios for implementation of the Power Monitor, including Power Monitor Parent and Power Monitor Child relationships. Scenario 1: Switch with PoE Endpoints Consider a PoE IP phone connected to a switch, as displayed in Figure 4. The IP phone consumes power from the PoE switch. The switch has the following attributes, also illustrated in Figure 4: pmPowerIndex "1", pmPhysicalEntity "2", and pmPowerMonitorId "UUID 1000". The power usage of the switch is "440 Watts". The switch does not have a Power Monitor Parent. The PoE switch port has the following attributes: The switch port has pmPowerIndex "3", pmPhysicalEntity is "12" and pmPowerMonitorId is "UUID 1003". The power metered at the POE switch port is "12 watts". Note that the PoE switch port doesn't consume any power, it meters the usage. When summing power usage for the Power Monitor Meter Domain, the PoE switch port meter usage should be kept separate from actual Power Monitor Children usage. Expires September 14, 2011 [Page 13] Internet-Draft March 2011 In this example, the POE switch port has the switch as the Power Monitor Parent, with its pmParentID of "1000". The IP phone has the following attributes: the IP phone has pmPowerIndex "31" and pmPowerMonitorId "UUID 2003", but does not have an entry for pmPhysicalEntity, as the ENTITY MIB is not supported on this device. The IP phone has a Power Monitor Parent: the switch whose pmPowerMonitorId is "UUID 1000". The power usage of the IP phone is metered at the POE switch port and the pmPower on the PoE IP phone reports 12. |--------------------------------------------------------------| | Switch | |==============================================================| | |Switch | Switch | Switch | Switch | Switch | | | |pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | | | 1 | 2 | UUID 1000 | null | 440 | | | ============================================================ | | | | SWITCH PORT | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | | Port | Port | Port | Port | Port | | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | | | 3 | 12 | UUID 1003 | UUID 1000 | 12 | | | ============================================================ | | ^ | | | | |-------------------------------|----------------------------- | | | POE IP PHONE | | ============================================================== | IP phone| IP phone | IP phone | IP phone | IP phone| | pmPIndex| EntPhyIdx| pmPowerMonitorId| pmParentID| pmPower | ============================================================== | 31 | 0 | UUID 2003 | UUID 1000 | 12 | ============================================================== Figure 4: Scenario 1 Expires September 14, 2011 [Page 14] Internet-Draft March 2011 Scenario 2: Switch with PoE Endpoints with Further Connected Devices Consider the same scenario as example 1 with an IP phone connected to PoE port of a switch. Now, in addition, a PC is daisy-chained from the IP phone for LAN connectivity. The phone draws power from the PoE port of the switch, while the PC draws power from the wall outlet. The attributes of the switch, switch port and IP phone are the same as in Scenario 1. The attributes of the PC are given below. The PC does not have pmPhysicalEntity. The pmPowerIndex (pmPIndex) of the PC is "57", the pmPowerMonitorId is "UUID 3003". The PC has a Power Monitor Parent, i.e. the switch whose pmPowerMonitorId is "UUID 1000". The power usage of the PC is "120 Watts" and is communicated to the switch port. This example illustrates the important distinction between the Power Monitor Children: The IP phone draws power from the switch, while the PC has LAN connectivity from the phone, but is powered from the wall outlet. However, the Power Monitor Parent sends power control messages to both the Power Monitor Children (IP phone and PC) and the Children react to those messages. |--------------------------------------------------------------| | Switch | |==============================================================| | Switch | Switch | Switch | Switch | Switch | | pmPIndex | pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | ============================================================ | | 1 | 2 | UUID 1000 | null | 440 | | ============================================================ | | | | SWITCH PORT | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | Port | Port | Port | Port | Port | | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | | | 3 | 12 | UUID 1003 | UUID 1000 | 12 | | | ============================================================ | | ^ | | | | |-----------------------------------|--------------------------| | | POE IP PHONE | | Expires September 14, 2011 [Page 15] Internet-Draft March 2011 | ============================================================= | IP phone | IP phone |IP phone |IP phone |IP phone| | pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower | ============================================================ | 31 | 0 | UUID 2003 | UUID 1000 | 12 | ============================================================ | | PC connected to switch via IP phone | | ============================================================= | PC | PC |PC |PC | PC | |pmPIndex| pmPhyIdx|pmPowerMonitorId|pmParentID| pmPower | ============================================================ | 57 | 0 | UUID 3003 | UUID 1000 | 120 | ============================================================= Figure 5: Scenario 2 Scenario 3: Switch with Wireless Access Points Consider a Wireless Access Point connected to the PoE port of a switch. There are several PCs connected to the Wireless Access Point over Wireless protocols. All PCs draw power from the wall outlets. The switch port is the Power Monitor Parent for the Wireless Access Point (WAP) and the PCs. There is a distinction between the Power Monitor Children, as the WAP draws power from the PoE port of the switch and the PCs draw power from the wall outlet. The switch has pmPowerIndex "1", pmPhysicalEntity is "2" and pmPowerMonitorId is "UUID 1000". The power usage of the switch is "440 Watts". The switch does not have a Power Monitor Parent. The PoE switch port has the following attributes: The switch port has pmPowerIndex "3", pmPhysicalEntity is "12" and pmPowerMonitorId is "UUID 1003". The power usage of the POE switch port is "20 watts". The POE switch port has the switch as the parent and the pmParentID is "UUID 1000". The WAP has the following attributes: The WAP has no entry for pmPhysicalEntity, pmPowerIndex "47", and pmPowerMonitorId "UUID Expires September 14, 2011 [Page 16] Internet-Draft March 2011 2004". The WAP has a parent: the switch whose pmPowerMonitorId is "UUID 1000". The power usage of the WAP is measured at the PoE switch port. Neither of the two PCs - PC1 and PC2 - has pmPhysicalEntity. The pmPowerIndex of PC1 is "53" and the pmPowerMonitorId is "UUID 3". PC1 has a parent: the switch whose pmPowerMonitorId is "UUID 1000". The power usage of PC1 is "120 Watts" and is communicated to the switch port. The pmPowerIndex of PC2 is "58" and the pmPowerMonitorId is "UUID 5". PC2 has a parent: the switch whose pmPowerMonitorId is "UUID 1000". The power usage of the PC is "120 Watts" and is communicated to the switch port. |--------------------------------------------------------------| | Switch | |==============================================================| | Switch | Switch | Switch | Switch | Switch | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | ============================================================ | | 1 | 2 | UUID 1000 | null | 440 | | ============================================================ | | | | SWITCH PORT | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | | Port | Port | Port | Port | Port | | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | | | 3 | 12 | UUID 1003 | UUID 1000 | 20 | | | ============================================================ | | ^ | | | | |-----------------------------------------------|--------------| | POE Wireless Access Point | | | ============================================================== | WAP | WAP | WAP | WAP | WAP | | pmPIndex | pmPhyIdx | pmPowerMonId | pmParentID | pmPower | ============================================================== | 47 | 0 | UUID 2004 | UUID 1000 | 20 | ============================================================== . Expires September 14, 2011 [Page 17] Internet-Draft March 2011 . . . PC1 connected to WAP . . ============================================================== | PC | PC |PC | PC | PC | |pmPIndex| pmPhyIdx |pmPowerMonitorId | pmParentID | pmPower | ============================================================== | 53 | 0 | UUID 3004 | UUID 1000 | 120 | ============================================================== . . PC2 connected to WAP . . ================================================================ | PC | PC |PC | PC | PC | |pmPIndex| pmPhyIdx |pmPowerMonitorId | pmParentID | pmPower | =============================================================== | 58 | 0 | UUID 4004 | UUID 1000 | 120 | ================================================================ Figure 6: Scenario 3 Scenario 4: Network Connected Facilities Gateway ------ | NMS | | | ------ | | | ========================(IP Network) ^ | North side interface | ----------------------- | Building Gateway | | | Expires September 14, 2011 [Page 18] Internet-Draft March 2011 ----------------------- | | Ethernet Interface RS-232/ | | RS-438 | | MODBUS, BACNET, etc... | | --------- | -------- HVAC | Cont | | | Cont | UPS -------------- | roll | |--| roll |--------- | | | er 1 | | | er 3 | | | | --------- | -------- | | | | | | | -------- | ------- Lighting | Cont | | | Cont | Electrical ------------ | roll | |--| roll |------------ | | | er 2 | | | er 4 | | | | | -------- | ------- | | Figure 7: Scenario 4 A simplified illustration of the building gateway network is presented in Figure 7. At the top of the network hierarchy of a building network is a gateway device that can perform protocol conversion between many facility management devices. The south building gateway communicates to the controllers, via RS-232/RS- 485 interfaces, ethernet interfaces, and building management protocols such as BACNET or MODBUS. Each controller is associated with a specific energy-consuming function, such as HVAC, electrical or lighting. The controllers are in turn connected to the actual building energy management devices: meters, sub-meters, valves, actuators, etc. Controller 1 is associated with a meter for the HVAC system and controller 2 can be associated with a meter for the Lighting. Assuming that the MIB is implemented on the gateway device, the building gateway can be considered as the Power Monitor Parent, and the controllers associated with the meters can be considered as Power Monitor Children. Tthe power measurement collected is therfore at the granularity of a controller, which aggregates all the energy measurement collected from all the meters and sub-meters. However, if energy measurement needs to be collected at a meter state, then the MIB should be implemented at the controller state. Expires September 14, 2011 [Page 19] Internet-Draft March 2011 In building management, the EntPhysicalIndex usually is not defined for these Power Monitor Parents or Children, as the ENTITY MIB is generally not implemented for these devices. Hence the gateway, controller 1, and controller 2 all have pmPhysicalEntities of value zero. The pmPowerIndex of the gateway is "7", and the pmPowerMonitorId is "UUID 1000". The gateway does not have a Power Monitor Parent. The total power usage of the gateway and its children is "2000 Watts". Controller 1 has pmPowerIndex "707", and pmPowerMonitorId is "UUID 5007". Controller 1 will report a power usage of "2000 watts". Controller 1 has the gateway as the parent and its pmParentID is "UUID 1000". Controller 2 has pmPowerIndex "708", and pmPowerMonitorId is "UUID 5008". Controller 2 will report a power usage of "500 watts". Controller 2 has the gateway as the Power Monitor Parent and its pmParentID is "UUID 1007". ---------------------------------------------------------- | Building Gateway | | | |======================================================== | | Mediat | Mediat | Mediat | Mediat | Mediat | | pmPIndex | pmPhyIdx | pmPowerMonId | pmParentId|pmPower | |======================================================== | | 7 | None | UUID 1000 | Null | 2500 | |======================================================== | | ------------------------------------------------------ | | |=> Controller 1 ========================================================= | Cntrl1 | Cntrl1 | Cntrl1 | Cntrl1 | Cntrl1 | | pmPIndex| pmPhyIdx |pmPowerMonId|pmParentID | pmPower | |========================================================| | 707 | 0 | UUID 5007 | UUID 1000 | 2000 | |========================================================= | | |===>Controller 2 ========================================================== Expires September 14, 2011 [Page 20] Internet-Draft March 2011 | Cntrl2 | Cntrl2 | Cntrl2 | Cntrl2 | Cntrl2 | | pmPIndex | pmPhyIdx |pmPowerMonId| pmParentID |pmPower | | ========================================================| | 708 | 0 | UUID 5008 | UUID 1000 | 500 | | | |=========================================================| Figure 8: Scenario 4 Scenario 5: Data Center Network A typical data center network consists of a hierarchy of switches. At the bottom of the hierarchy are servers mounted on a rack, and these are connected to the top-of-the-rack switches. The top switches are connected to aggregation switches that are in turn connected to core switches. As an example, Server 1 and Server 2 are connected to different switch ports of the top switch, as shown in Figure 9. The proposed MIB can be implemented on the switches. The switch can be considered as the Power Monitor Parent. The servers can be considered as the Power Monitor Children. The switch has pmPowerIndex "1", pmPhysicalEntity is "2", and the pmPowerMonitorId is "UUID 1000". The power usage of the switch is "440 Watts". The switch does not have a parent. The switch ports are non-PoE and have the following attributes: Server 1 is connected to Switch port 1. Switch port 1 has pmPowerIndex "3", pmPhysicalEntity is "12", and pmPowerMonitorId is "UUID 1003". Switch port 2 has pmPowerIndex "4", pmPhysicalEntity is "13", and pmPowerMonitorId is "UUID 1004". The power usage of the non-POE switch port cannot be measured. The switch ports have the switch as the Power Monitor Parent and its pmParentID is "1000". Server 1 has a value of zero for pmPhysicalEntity. The pmPowerIndex of Server 1 is "5", and the pmPowerMonitorId is "UUID 2006". Server 1 has a Power Monitor Parent: The switch whose pmPowerMonitorId is "1000". The power usage of Server 1 is "200 Watts" and is communicated to the switch port. Server 2 has a value of zero for pmPhysicalEntity. The pmPowerIndex of Server 2 is "6", and the pmPowerMonitorId is "UUID 3006". Server 1 has a parent: The switch whose Expires September 14, 2011 [Page 21] Internet-Draft March 2011 pmPowerMonitorId is "1000". The power usage of the Server 2 is "140 Watts" and is communicated to the switch port. Communication of power usage of Server1 and Server2 to the switch is out of scope of this document. |--------------------------------------------------------------| | Switch | |==============================================================| | |Switch | Switch | Switch | Switch | Switch | | | |pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | | | 1 | 2 | UUID 1000 | null | 440 | | | ============================================================ | | | | | | SWITCH PORT 1 | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | Port1 | Port1 | Port1 | Port1 | Port1 | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | ============================================================ | | | 3 | 12 | UUID 1003 | UUID 1000 | NULL || | ============================================================ | | | | SWITCH PORT 2 | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | Port2 | Port2 | Port2 | Port2 | Port2 | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | ============================================================ | | | 4 | 13 | UUID 1004 | UUID 1000 | NULL | | ============================================================ | | | | | |--------------------------------------------------------------| | | | Server 1 connected to switch (Non-POE) | ============================================================= | | Server 1| Server 1 | Server 1 | Server 1 | Server 1 | | | pmPIndex| pmPhyIdx |pmPowerMonitorId|pmParentID| pmPower | |=>|============================================================ | | 5 | 0 | UUID 2006 | UUID 1000 | 200 | | ============================================================= | | Server 2 connected to switch (Non-POE) | ============================================================ Expires September 14, 2011 [Page 22] Internet-Draft March 2011 |=>| Server 2| Server 2 | Server 2 | Server 2 | Server 2 | | pmPIndex| pmPhyIdx |pmPowerMonitorId|pmParentID| pmPower | ============================================================= | 6 | 0 | UUID 3006 | UUID 1000 | 140 | ============================================================= Figure 9: Scenario 5 Scenario 6: Switch with Power Distribution Units (PDU) Consider Scenario 1 again, this time with two PDUs. The switch draws power from one of the PDUs, while the PDUs are plugged into the switch for LAN connectivity. The attributes of the switch and switch ports are the same as in Scenario 1. The attributes of the PDUs are given in Figure 11. The PDUs are network peers of the switch, with their own management agent and no pmPowerMonitor parent pmPowerMonitorId, as the PDUs are Power Monitor Parents themselves. The power usage of the PDUs are reporting 3000 watts and 12000 watts categorized as 'Meter'. This example illustrates the distinction between power supply, metering, and LAN connectivity. The PDUs supply and meter power to the switch, while the PC has LAN connectivity from the phone, but is powered from the wall outlet. However, the Power Monitor Parent sends power control messages to both the Power Monitor Children (IP phone and PC) and the children react to those messages. |--------------------------------------------------------------| | Switch | |==============================================================| | Switch | Switch | Switch | Switch | Switch | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | ============================================================ | | 1 | 2 | UUID 1000 | null | 440 | | ============================================================ | | | | SWITCH PORT | | ============================================================ | | | Switch | Switch | Switch | Switch | Switch | | | Port | Port | Port | Port | Port | | | | pmPIndex| pmPhyIdx | pmPowerMonId | pmParentId | pmPower | | | ============================================================ | Expires September 14, 2011 [Page 23] Internet-Draft March 2011 | | 3 | 12 | | UUID 1000 | 0 | | | ============================================================ | | | 4 | 13 | | UUID 1000 | 0 | | | ============================================================ | | ^ | | | | |-----------------------------------|--------------------------| | | PDU #1 (no children) | | | ============================================================= | PDU | PDU |PDU |PDU | Meter | | pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower | ============================================================ | 1 | 1 | UUID 2001 | null | 3000 | ============================================================ | | PDU #2 (with children)_ | | ============================================================= | PDU | PDU |PDU |PDU | Meter | | pmPIndex | pmPhyIdx |pmPowerMonitorId|pmParentID |pmPower | ============================================================ | 1 | 1 | UUID 3001 | null | 600 | | 2 | 2 | UUID 3002 | null | 1000 | | 3 | 3 | UUID 3003 | null | 800 | ============================================================= Figure 11: Scenario 6 Scenario 7: Power Consumption of UPS Data centers and commercial buildings can have Uninterruptible Power Supplies (UPS) connected to the network. The Power Monitor can be used to model a UPS as a Power Monitor Parent with the connected devices as Power Monitor Children. EDITOR'S NOTE: the example will be completed in the future. Expires September 14, 2011 [Page 24] Internet-Draft March 2011 Scenario 8: Power Consumption of Battery-Based Devices RFC'EDITOR NOTE: Power consumption of battery enabled devices can be obtained from ... (draft to be posted by Juergen Quittek). 7. Link with the other IETF MIBs 7.1. Link with the ENTITY MIB and the ENTITY-SENSOR MIB RFC 4133 [RFC4133] defines the ENTITY MIB module that lists the physical entities of a networking device (router, switch, etc.) and those physical entities indexed by entPhysicalIndex. From an energy-management standpoint, the physical entities that consume or produce energy are of interest. RFC 3433 [RFC3433] defines the ENTITY-SENSOR MIB module that provides a standardized way of obtaining information (current value of the sensor, operational status of the sensor, and the data units precision) from sensors embedded in networking devices. Sensors are associated with each index of entPhysicalIndex of the ENTITY MIB [RFC4133]. While the focus of the Power and Energy Monitoring MIB is on measurement of power usage of networking equipment indexed by the ENTITY MIB, this MIB proposes a customized power scale for power measurement and different power state states of networking equipment, and functionality to configure the power state states. When this MIB module is used to monitor the power usage of devices like routers and switches, the ENTITY MIB and ENTITY- SENSOR MIB SHOULD be implemented. In such cases, the Power Monitors are modeled by the entPhysicalIndex through the pmPhysicalEntity MIB object specified in the pmTable. However, the ENTITY-SENSOR MIB [RFC3433] does not have the ANSI C12.x accuracy classes required for electricity (i.e., 1%, 2%, 0.5% accuracy classes). Indeed, entPhySensorPrecision [RFC3433] represents "The number of decimal places of precision in fixed- point sensor values returned by the associated entPhySensorValue object". The ANSI and IEC Standards are used for power measurement and these standards require that we use an accuracy class, not the scientific-number precision model specified in RFC3433. The pmPowerAccuracy MIB object models this accuracy. Note that pmPowerUnitMultipler represents the scale factor per IEC 61850, which is a more logical representation for power Expires September 14, 2011 [Page 25] Internet-Draft March 2011 measurements (compared to entPhySensorScale), with the mantissa and the exponent values X * 10 ^ Y. Power measurements specifying the qualifier 'UNITS' for each measured value in watts are used in the LLDP-EXT-MED-MIB, POE [RFC3621], and UPS [RFC1628] MIBs. The same 'UNITS' qualifier is used for the power measurement values. One cannot assume that the ENTITY MIB and ENTITY-SENSOR MIB are implemented for all Power Monitors that need to be monitored. A typical example is a converged building gateway, monitoring several other devices in the building, doing the proxy between SNMP and a protocol like BACNET. Another example is the home energy controller. In such cases, the pmPhysicalEntity value contains the zero value, thanks to PhysicalIndexOrZero textual convention. The pmPowerIndex MIB object has been kept as the unique Power Monitor index. The pmPower is similar to entPhySensorValue [RFC3433] and the pmPowerUnitMultipler is similar to entPhySensorScale. 7.2. Link with the ENTITY-STATE MIB For each entity in the ENTITY-MIB [RFC4133], the ENTITY-STATE MIB [RFC4268] specifies the operational states (entStateOper: unknown, enabled, disabled, testing), the alarm (entStateAlarm: unknown, underRepair, critical, major, minor, warning, indeterminate) and the possible values of standby states (entStateStandby: unknown, hotStandby, coldStandby, providingService). From a power monitoring point of view, in contrast to the entity operational states of entities, Power States are required, as proposed in the Power and Energy Monitoring MIB module. Those Power States can be mapped to the different operational states in the ENTITY-STATE MIB, if a formal mapping is required. For example, the entStateStandby "unknown", "hotStandby", "coldStandby", states could map to the Power State "unknown", "ready", "standby", respectively, while the entStateStandby "providingService" could map to any "low" to "high" Power State. 7.3. Link with the POWER-OVER-ETHERNET MIB Power-over-Ethernet MIB [RFC3621] provides an energy monitoring and configuration framework for power over Ethernet devices. Expires September 14, 2011 [Page 26] Internet-Draft March 2011 The RFC introduces a concept of a port group on a switch to define power monitoring and management policy and does not use the entPhysicalIndex as the index. Indeed, the pethMainPseConsumptionPower is indexed by the pethMainPseGroupIndex, which has no mapping with the entPhysicalIndex. One cannot assume that the Power-over-Ethernet MIB is implemented for all Power Monitors that need to be monitored. A typical example is a converged building gateway, monitoring several other devices in the building, doing the proxy between SNMP and a protocol like BACNET. Another example is the home energy controller. In such cases, the pmethPortIndex and pmethPortGrpIndex values contain the zero value, thanks to new PethPsePortIndexOrZero and textual PethPsePortGroupIndexOrZero conventions. However, if the Power-over-Ethernet MIB [RFC3621] is supported, the Power Monitor pmethPortIndex and pmethPortGrpIndex contain the pethPsePortIndex and pethPsePortGroupIndex, respectively. As a consequence, the pmPowerIndex MIB object has been kept as the unique Power Monitor index. Note that, even though the Power-over-Ethernet MIB [RFC3621] was created after the ENTITY-SENSOR MIB [RFC3433], it does not reuse the precision notion from the ENTITY-SENSOR MIB, i.e. the entPhySensorPrecision MIB object. 7.4. Link with the UPS MIB To protect against unexpected power disruption, data centers and buildings make use of Uninterruptible Power Supplies (UPS). To protect critical assets, a UPS can be restricted to a particular subset or domain of the network. UPS usage typically lasts only for a finite period of time, until normal power supply is restored. Planning is required to decide on the capacity of the UPS based on output power and duration of probable power outage. To properly provision UPS power in a data center or building, it is important to first understand the total demand required to support all the entities in the site. This demand can be assessed and monitored via the Power and Energy Monitoring MIB. UPS MIB [RFC1628] provides information on the state of the UPS network. Implementation of the UPS MIB is useful at the aggregate level of a data center or a building. The MIB module contains several groups of variables: Expires September 14, 2011 [Page 27] Internet-Draft March 2011 - upsIdent: Identifies the UPS entity (name, model, etc.). - upsBattery group: Indicates the battery state (upsbatteryStatus, upsEstimatedMinutesRemaining, etc.) - upsInput group: Characterizes the input load to the UPS (number of input lines, voltage, current, etc.). - upsOutput: Characterizes the output from the UPS (number of output lines, voltage, current, etc.) - upsAlarms: Indicates the various alarm events. The measurement of power in the UPS MIB is in Volts, Amps and Watts. The units of power measurement are RMS volts and RMS Amps. They are not based on EntitySensorDataScale and EntitySensorDataPrecision of Entity-Sensor MIB. Both the Power and Energy Monitoring MIB and the UPS MIB may be implemented on the same UPS SNMP agent, without conflict. In this case, the UPS device itself is the Power Monitor Parent and any of the UPS meters or submeters are the Power Monitor Children. 7.5. Link with the LLDP and LLDP-MED MIBs The LLDP Protocol is a Data Link Layer protocol used by network devices to advertise their identities, capabilities, and interconnections on a LAN network. The Media Endpoint Discovery is an enhancement of LLDP, known as LLDP-MED. The LLDP-MED enhancements specifically address voice applications. LLDP-MED covers 6 basic areas: capability discovery, LAN speed and duplex discovery, network policy discovery, location identification discovery, inventory discovery, and power discovery. Of particular interest to the current MIB module is the power discovery, which allows the endpoint device (such as a PoE phone) to convey power requirements to the switch. In power discovery, LLDP-MED has four Type Length Values (TLVs): power type, power source, power priority and power value. Respectively, those TLVs provide information related to the type of power (power sourcing entity versus powered device), how the device is powered (from the line, from a backup source, from external power source, etc.), the power priority (how important Expires September 14, 2011 [Page 28] Internet-Draft March 2011 is it that this device has power?), and how much power the device needs. The power priority specified in the LLDP-MED MIB [LLDP-MED-MIB] actually comes from the Power-over-Ethernet MIB [RFC3621]. If the Power-over-Ethernet MIB [RFC3621] is supported, the exact value from the pethPsePortPowerPriority [RFC3621] is copied over in the lldpXMedRemXPoEPDPowerPriority [LLDP-MED-MIB]; otherwise the value in lldpXMedRemXPoEPDPowerPriority is "unknown". From the Power and Energy Monitoring MIB, it is possible to identify the pethPsePortPowerPriority [RFC3621], thanks to the pmethPortIndex and pmethPortGrpIndex. The lldpXMedLocXPoEPDPowerSource [LLDP-MED-MIB] is similar to pmPowerOrigin in indicating if the power for an attached device is local or from a remote device. If the LLDP-MED MIB is supported, the following mapping can be applied to the pmPowerOrigin: lldpXMedLocXPoEPDPowerSource fromPSE(2) and local(3) can be mapped to remote(2) and self(1), respectively. 8. Structure of the MIB The primary MIB object in this MIB module is the PowerMonitorMIBObject. The pmTable table of PowerMonitorMibObject describes an entity in the network that is a Power Monitor. A Power Monitor contains information describing itself as an entity in the context of the network (such as its Power Monitor Meter Domain pmDomainName) and attributes for describing its business context (such as pmImportance, pmRoleDescription and pmKeywords). A Power Monitor contains information describing its power usage (pmPower) and its power state (pmPowerState). Along with the power usage is information describing how the power usage was determined (such as pmPowerMeasurementCaliber and pmPowerOrigin). The pmPowerStateMappingTable table enumerates the maximum power usage in watts for every Manufacturer Power State. This table also maps the Manufacturer Power States to the Power States specified in this document (more specifically, to the PowerMonitorState textual convention). Finally, this table returns the name of each Manufacturer Power State. Expires September 14, 2011 [Page 29] Internet-Draft March 2011 A Power Monitor may contain an optional pmPowerQuality table that describes the electrical characteristics associated with the current power state and usage. A Power Monitor may contain an optional pmEnergyTable to describe energy information over time. A Power Monitor may also contain optional battery information associated with this entity. 9. MIB Definitions -- ************************************************************ -- -- -- This MIB is used to monitor power usage of network -- devices -- -- ************************************************************* POWER-MONITOR-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32, Counter64, TimeTicks FROM SNMPv2-SMI TEXTUAL-CONVENTION, DisplayString, RowStatus, TimeInterval FROM SNMPv2-TC MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP FROM SNMPv2-CONF OwnerString FROM RMON-MIB; powerMonitorMIB MODULE-IDENTITY LAST-UPDATED "201103140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 Expires September 14, 2011 [Page 30] Internet-Draft March 2011 USA Tel: +1 800 553-NETS E-mail: cs-snmp@cisco.com" DESCRIPTION "This MIB is used to monitor power and energy in devices." REVISION "201103140000Z" DESCRIPTION "Initial version, published as RFC XXXX." ::= { mib-2 xxxxx } powerMonitorMIBNotifs OBJECT IDENTIFIER ::= { powerMonitorMIB 0 } powerMonitorMIBObjects OBJECT IDENTIFIER ::= { powerMonitorMIB 1 } powerMonitorMIBConform OBJECT IDENTIFIER ::= { powerMonitorMIB 2 } -- Textual Conventions PowerMonitorState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An enumerated integer value that represents the value of the power policy state, a current power setting at which a Power Monitor uses power. There are twelve power policy states, divided into six operational states, and six non-operational states. The lowest non-operational state is 1 and the highest is six. Each non- operational state corresponds to an ACPI state [ACPI] corresponding to Global and System states between G3 (hard-off) and G1 (sleeping). For operational states, 6 is the lowest, and 12 the highest (full power). Each operational state represent a performance state, and may be mapped to ACPI states P0 (maximum performance power) through P5 (minimum performance and minimum power). An entity may have fewer power states than twelve and would then map several policy states to the same power state. Entities Expires September 14, 2011 [Page 31] Internet-Draft March 2011 with more than twelve states, would choose which twelve to represent as power policy states. Note that Power Monitor Parents MUST report some of the nonoperational Power States of their Power Monitor Children who are unable to report their Power State. For example: A phone may notify its Power Monitor Parent that it will go into a mechoff(1) or hibernate(3) state so that the Power Monitor Parent can report the phone's current state (such as zero or 1 watt). Conversely, a PC with Desktop and mobile Architecture for System Hardware [DASH] out-of-band management is an example where a Power Monitor Child can report its usage and state even when in a non-operational state. In each of the non-operational states (from mechoff(1) to ready(6)), the Power State preceding it is expected to have a lower power consumption and a longer delay in returning to an operational state: mechoff(1) : An off state where no entity features are available. The entity is unavailable. No energy is being consumed and the power connector can be removed. This corresponds to ACPI state G3. softoff(2) : Similar to mechoff(1), but some components remain powered or receive trace power so that the entity can be awakened from its off state. In softoff(2), no context is saved and the device typically requires a complete boot when awakened. This corresponds to ACPI state G2. hibernate(3): No entity features are available. The entity may be awakened without requiring a complete boot, but the time for availability is longer than sleep(4). An example for state hibernate(3) is a save to-disk state where DRAM context is not maintained. Typically, energy consumption is zero or close to zero. This corresponds to state G1, S4 in ACPI. sleep(4) : No entity features are available, except for out-of-band management, for example wake-up mechanisms. The time for Expires September 14, 2011 [Page 32] Internet-Draft March 2011 availability is longer than standby(5). An example for state sleep(4) is a save- to-RAM state, where DRAM context is maintained. Typically, energy consumption is close to zero. This corresponds to state G1, S3 in ACPI. standby(5) : No entity features are available, except for out-of-band management, for example wake-up mechanisms. This mode is analogous to cold-standy. The time for availability is longer than ready(6). For example, the processor context is not maintained. Typically, energy consumption is close to zero. This corresponds to state G1, S2 in ACPI. ready(6) : No entity features are available, except for out-of-band management, for example wake-up mechanisms. This mode is analogous to hot-standby. The entity can be quickly transitioned into an operational state. For example, processors are not executing, but processor context is maintained. This corresponds to state G1, S1 in ACPI. lowMinus(7) : Indicates some entity features may not be available and the entity has selected measures/options to provide less than low(8) usage. This corresponds to ACPI State G0. This includes operational states lowMinus(7) to full(12). low(8) : Indicates some features may not be available and the entity has taken measures or selected options to provide less than mediumMinus(9) usage. mediumMinus(9): Indicates all entity features are available but the entity has taken measures or selected options to provide less than medium(10) usage. medium(10) : Indicates all entity features are available but the entity has taken measures or selected options to provide less than highMinus(11) usage. Expires September 14, 2011 [Page 33] Internet-Draft March 2011 highMinus(11) : Indicates all entity features are available and power usage is less than high(12). high(12) : Indicates all entity features are available and the entity is consuming the highest power. Note that unknown(0) is not a Power State as such, but simply an indication that the Power State unavailable." SYNTAX INTEGER { unknown(0), mechoff(1), softoff(2), hibernate(3), sleep(4), standby(5), ready(6), lowMinus(7), low(8), mediumMinus(9), medium(10), highMinus(11), high(12) } UnitMultiplier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The Unit Multiplier is an integer value that represents the IEEE 61850 Annex A units multiplier associated with the integer units used to measure the power or energy. For example, when used with pmPowerUnitMultiplier, -3 represents 10^-3 or milliwatts." REFERENCE "The International System of Units (SI), National Institute of Standards and Technology, Spec. Publ. 330, August 1991." SYNTAX INTEGER { yocto(-24), -- 10^-24 zepto(-21), -- 10^-21 atto(-18), -- 10^-18 Expires September 14, 2011 [Page 34] Internet-Draft March 2011 femto(-15), -- 10^-15 pico(-12), -- 10^-12 nano(-9), -- 10^-9 micro(-6), -- 10^-6 milli(-3), -- 10^-3 units(0), -- 10^0 kilo(3), -- 10^3 mega(6), -- 10^6 giga(9), -- 10^9 tera(12), -- 10^12 peta(15), -- 10^15 exa(18), -- 10^18 zetta(21), -- 10^21 yotta(24) -- 10^24 } -- Objects pmPowerTable OBJECT-TYPE SYNTAX SEQUENCE OF PmPowerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists Power Monitors." ::= { powerMonitorMIBObjects 1 } pmPowerEntry OBJECT-TYPE SYNTAX PmPowerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describes the power usage of a Power Monitor." INDEX { pmPowerIndex } ::= { pmPowerTable 1 } PmPowerEntry ::= SEQUENCE { pmPowerIndex Integer32, pmPower Integer32, pmPowerNameplate Integer32, pmPowerUnitMultiplier UnitMultiplier, pmPowerAccuracy Integer32, pmPowerMeasurementCaliber INTEGER, pmPowerCurrentType INTEGER, pmPowerOrigin INTEGER, pmPowerState PowerMonitorState, pmPowerActualState PowerMonitorState, Expires September 14, 2011 [Page 35] Internet-Draft March 2011 pmPowerManufacturerActualPowerState Integer32, pmPowerManufacturerMappingId Integer32, pmPowerStateEnterReason OwnerString } pmPowerIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value, for each Power Monitor. If an implementation of the ENERGY AWARE MIB module is available in the local SNMP context, then the same index as the one in the ENERGY AWARE MIB MUST be assigned for the identical Power Monitor. In this case, entities without an assigned value for pmIndex cannot be indexed by the pmPowerStateTable. If there is no implementation of the ENERGY AWARE MIB module but one of the ENTITY MIB module is available in the local SNMP context, then the same index of an entity MUST be chosen as assigned to the entity by object entPhysicalIndex in the ENTITY MIB module. In this case, entities without an assigned value for entPhysicalIndex cannot be indexed by the pmPowerStateTable. If neither the ENERGY AWARE MIB module nor of the ENTITY MIB module are available in the local SNMP context, then this MIB module may choose identity values from a further MIB module providing entity identities. In this case the value for each pmPowerIndex must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. In case that no other MIB modules have been chosen for providing entity identities, Power States can be reported exclusively for the local device on which this table is instantiated. Then this table will have a single entry only and an index value of 0 MUST be used." ::= { pmPowerEntry 1 } pmPower OBJECT-TYPE SYNTAX Integer32 UNITS "Watts" MAX-ACCESS read-only Expires September 14, 2011 [Page 36] Internet-Draft March 2011 STATUS current DESCRIPTION "This object indicates the 'instantaneous' RMS consumption for the Power Monitor. This value is specified in SI units of watts with the magnitude of watts (milliwatts, kilowatts, etc.) indicated separately in pmPowerUnitMultiplier. The accuracy of the measurement is specfied in pmPowerAccuracy. The direction of power flow is indicated by the sign on pmPower. If the Power Monitor is consuming power, the pmPower value will be positive. If the Power Monitor is producing power, the pmPower value will be negative. The pmPower MUST be less than or equal to the maximum power that can be consumed at the power state specified by pmPowerState. The pmPowerMeasurementCaliber object specifies how the usage value reported by pmPower was obtained. The pmPower value must report 0 if the pmPowerMeasurementCaliber is 'unavailable'. For devices that can not measure or report power, this option can be used." ::= { pmPowerEntry 2 } pmPowerNameplate OBJECT-TYPE SYNTAX Integer32 UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the rated maximum consumption for the fully populated Power Monitor. The nameplate power requirements are the maximum power numbers and, in almost all cases, are well above the expected operational consumption. The pmPowerNameplate is widely used for power provisioning. This value is specified in either units of watts or voltage and current. The units are therefore SI watts or equivalent Volt-Amperes with the magnitude (milliwatts, kilowatts, etc.) indicated separately in pmPowerUnitMultiplier." ::= { pmPowerEntry 3 } pmPowerUnitMultiplier OBJECT-TYPE SYNTAX UnitMultiplier MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 14, 2011 [Page 37] Internet-Draft March 2011 "The magnitude of watts for the usage value in pmPower and pmPowerNameplate." ::= { pmPowerEntry 4 } pmPowerAccuracy OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates a percentage value, in 100ths of a percent, representing the assumed accuracy of the usage reported by pmPower. For example: The value 1010 means the reported usage is accurate to +/- 10.1 percent. This value is zero if the accuracy is unknown or not applicable based upon the measurement method. ANSI and IEC define the following accuracy classes for power measurement: IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. ANSI C12.20 class 0.2, 0.5" ::= { pmPowerEntry 5 } pmPowerMeasurementCaliber OBJECT-TYPE SYNTAX INTEGER { unavailable(1) , unknown(2), actual(3) , estimated(4), presumed(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies how the usage value reported by pmPower was obtained: - unavailable(1): Indicates that the usage is not available. In such a case, the pmPower value must be 0 For devices that can not measure or report power this option can be used. - unknown(2): Indicates that the way the usage was determined is unknown. In some cases, entities report aggregate power on behalf of another device. In such cases it is not known whether the usage reported is actual(2), estimated(3) or presumed (4). Expires September 14, 2011 [Page 38] Internet-Draft March 2011 - actual(3): Indicates that the reported usage was measured by the entity through some hardware or direct physical means. The usage data reported is not presumed (4) or estimated (3) but the real apparent current energy consumption rate. - estimated(4): Indicates that the usage was not determined by physical measurement. The value is a derivation based upon the device type, state, and/or current utilization using some algorithm or heuristic. It is presumed that the entity's state and current configuration were used to compute the value. - presumed(5): Indicates that the usage was not determined by physical measurement, algorithm or derivation. The usage was reported based upon external tables, specifications, and/or model information. For example, a PC Model X draws 200W, while a PC Model Y draws 210W" ::= { pmPowerEntry 6 } pmPowerCurrentType OBJECT-TYPE SYNTAX INTEGER { ac(1), dc(2), unknown(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether the pmUsage for the Power Monitor reports alternative current AC(1), direct current DC(2), or that the current type is unknown(3)." ::= { pmPowerEntry 7 } pmPowerOrigin OBJECT-TYPE SYNTAX INTEGER { self (1), remote (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the source of power measurement and can be useful when modeling the power usage of attached devices. The power measurement can be performed by the entity itself or the power measurement of the Expires September 14, 2011 [Page 39] Internet-Draft March 2011 entity can be reported by another trusted entity using a protocol extension. A value of self(1) indicates the measurement is performed by the entity, whereas remote(2) indicates that the measurement was performed by another entity." ::= { pmPowerEntry 8 } pmPowerState OBJECT-TYPE SYNTAX PowerMonitorState MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the Power State (0..12) requested for the Power Monitor. The pmPowerState values increase with the power consumption. If the Power Monitor is unable to report its Power State, it must report the value unknown(0). Note that unknown(0) is not a Power State as such, but simply an indication that the Power State is unknown." ::= { pmPowerEntry 9 } pmPowerActualState OBJECT-TYPE SYNTAX PowerMonitorState MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the current Power State (0..12) for the Power Monitor. If the Power Monitor is unable to report its Power State, it must report the value unknown(0). Note that unknown(0) is not a Power State as such, but simply an indication that the Power State is unknown." ::= { pmPowerEntry 10 } pmPowerManufacturerActualPowerState OBJECT-TYPE SYNTAX Integer32 (0..1000) MAX-ACCESS read-only STATUS current DESCRIPTION "This object is a positive integer which specifies the actual Manufacturer Power State for the Power Monitor. If the Manufacturer Power State is not defined, the pmPowerManufacturerActualPowerState will report 0. If the Power Monitor is unable to report its Manufacturer Power State, it must report the value 0." ::= { pmPowerEntry 11 } pmPowerManufacturerMappingId OBJECT-TYPE Expires September 14, 2011 [Page 40] Internet-Draft March 2011 SYNTAX Integer32 (1..1000) MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the actual Manufacturer Power State mapping ID for the Power Monitor. The pmPowerManufacturerMappingId points to the pmPowerStateMappingTable, which maps the Manufacturer Power States versus the standard ones specified in the PowerMonitorState textual convention. If the Manufacturer Power State mapping is not defined, the pmPowerManufacturerMappingId will report 0. If the Power Monitor is unable to report its Manufacturer Power State mapping ID, it must report the value 0." ::= { pmPowerEntry 12 } pmPowerStateEnterReason OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "This string object describes the reason for the last power state transition into this power state. Alternatively, this string may contain with the entity that configured this Power Monitor to this Power State." DEFVAL { "" } ::= { pmPowerEntry 13 } pmPowerStateTable OBJECT-TYPE SYNTAX SEQUENCE OF PmPowerStateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table enumerates the maximum power usage, in watts, for every single supported Power State of each Power Monitor. This table has an expansion-dependent relationship on the pmTable, containing rows describing each Power State for the corresponding Power Monitor. For every Power Monitor in the pmTable, there is a corresponding entry in this table." ::= { powerMonitorMIBObjects 2 } pmPowerStateEntry OBJECT-TYPE Expires September 14, 2011 [Page 41] Internet-Draft March 2011 SYNTAX PmPowerStateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A pmPowerStateEntry extends a corresponding pmPowerEntry. This entry displays max usage values at every single possible Power Monitor State supported by the Power Monitor. For example, given the values of a Power Monitor corresponding to a maximum usage of 11W at the state 1 (off), 6 (low), 8 (medium), 12 (full): State MaxUsage Units 1 0 0 5 0 0 6 8 0 7 8 0 8 11 0 12 11 0" INDEX { pmPowerIndex, pmPowerStateIndex } ::= { pmPowerStateTable 1 } PmPowerStateEntry ::= SEQUENCE { pmPowerStateIndex PowerMonitorState, pmPowerStateMaxPower Integer32, pmPowerStatePowerUnitMultiplier UnitMultiplier, pmPowerStateTotalTime TimeTicks, pmPowerStateEnterCount Counter64 } pmPowerStateIndex OBJECT-TYPE SYNTAX PowerMonitorState MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object indicates the state for which this entry describes the power usage." ::= { pmPowerStateEntry 1 } pmPowerStateMaxPower OBJECT-TYPE Expires September 14, 2011 [Page 42] Internet-Draft March 2011 SYNTAX Integer32 UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum power for the Power Monitor at the particular Power State. This value is specified in SI units of watts with the magnitude of the units (milliwatts, kilowatts, etc.) indicated separately in pmPowerStatePowerUnitMultiplier. If the maximum power is not known for a certain Power State, then the value is encoded as 0xFFFF. For Power States not enumerated, the value of pmPowerStateMaxPower might be interpolated by using the next highest supported Power State." ::= { pmPowerStateEntry 2 } pmPowerStatePowerUnitMultiplier OBJECT-TYPE SYNTAX UnitMultiplier MAX-ACCESS read-only STATUS current DESCRIPTION "The magnitude of watts for the usage value in pmPowerStateMaxPower." ::= { pmPowerStateEntry 3 } pmPowerStateTotalTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the total time in hundreds of seconds that the Power Monitor has been in this power state since the last reset, as specified in the sysUpTime." ::= { pmPowerStateEntry 4 } pmPowerStateEnterCount OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates how often the Power Monitor has entered this power state, since the last reset of the device as specified in the sysUpTime." Expires September 14, 2011 [Page 43] Internet-Draft March 2011 ::= { pmPowerStateEntry 5 } pmPowerStateMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF PmPowerStateMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table enumerates the maximum power usage, in watts, for every single Manufacturer Power State. This table also maps the Manufacturer Power States to the Power States specified in this document (more specifically, to the PowerMonitorState textual convention). Finally, this table returns the name of each Manufacturer Power State. For every different pmPowerManufacturerMappingId in the pmTable, there is a corresponding entry in this table." ::= { powerMonitorMIBObjects 3 } pmPowerStateMappingEntry OBJECT-TYPE SYNTAX PmPowerStateMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "For every pmPowerManufacturerMappingId, this entry displays the max usage value at every single possible Manufacturer Power State supported by the Power Monitor, along with the mapping at the standardized Power State For example, given the values of a Power Monitor corresponding to a maximum usage of 0, 3, 7, and 11W at the state 1 (off), 2 (low), 3 (medium), 4 (full), the mapping would be represent as follows: Pow. Lev. Manu. Pow. Lev./Name maxUsage 1 1/off 0 W 2 1/off 0 W 3 1/off 0 W 4 1/off 0 W 5 1/off 0 W 6 2/low 3 W 7 2/low 3 W 8 3/medium 7 W 9 3/medium 7 W 10 3/medium 7 W 11 3/medium 7 W 12 4/full 11 W In this example, the Manufacturer Power States map to the lowest applicable Power States, so that setting all Power Expires September 14, 2011 [Page 44] Internet-Draft March 2011 Monitors to a Power State would be conservative in terms of disabled functionality on the Power Monitor implementing the Manufacturer Power States." INDEX { pmPowerManufacturerMappingId, pmPowerStateIndex, pmManufacturerPowerState } ::= { pmPowerStateMappingTable 1 } PmPowerStateMappingEntry ::= SEQUENCE { pmManufacturerPowerState Integer32, pmManufacturerPowerStateMaxPower Integer32, pmManufacturerPowerStatePowerUnitMultiplier UnitMultiplier, pmManufacturerPowerStateName DisplayString } pmManufacturerPowerState OBJECT-TYPE SYNTAX Integer32 (0..10000) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object specifies the Manufacturer Power States for the specific pmPowerManufacturerMappingId." ::= { pmPowerStateMappingEntry 1 } pmManufacturerPowerStateMaxPower OBJECT-TYPE SYNTAX Integer32 UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum power for the Manufacturer Power State specified by the pmManufacturerPowerState index. This value is specified in SI units of watts with the magnitude of the units (milliwatts, kilowatts, etc.) indicated separately in pmManufacturerPowerStatePowerUnitMultiplier. If the maximum power is not known for a certain Power State, then the value is encoded as 0xFFFF. For Power States not enumerated, the value of pmManufacturerPowerStateMaxPower might be interpolated by using the next highest supported Power State." ::= { pmPowerStateMappingEntry 2 } pmManufacturerPowerStatePowerUnitMultiplier OBJECT-TYPE Expires September 14, 2011 [Page 45] Internet-Draft March 2011 SYNTAX UnitMultiplier MAX-ACCESS read-only STATUS current DESCRIPTION "The magnitude of watts for the usage value in pmManufacturerPowerStateMaxPower ." ::= { pmPowerStateMappingEntry 3 } pmManufacturerPowerStateName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current DESCRIPTION "The textual name of the manufacturer name for the Power State specified by the pmManufacturerPowerState index. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string." ::= { pmPowerStateMappingEntry 4 } pmEnergyParametersTable OBJECT-TYPE SYNTAX SEQUENCE OF PmEnergyParametersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Controls and configures the demand table pmEnergyTable." ::= { powerMonitorMIBObjects 4 } pmEnergyParametersEntry OBJECT-TYPE SYNTAX PmEnergyParametersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry controls an energy measurement in pmEnergyTable." INDEX { pmPowerIndex } ::= { pmEnergyParametersTable 1 } PmEnergyParametersEntry ::= SEQUENCE { pmEnergyParametersIntervalLength TimeInterval, pmEnergyParametersIntervalNumber Integer32, pmEnergyParametersIntervalMode Integer32, pmEnergyParametersIntervalWindow TimeInterval, pmEnergyParametersSampleRate Integer32, pmEnergyParametersStatus RowStatus } Expires September 14, 2011 [Page 46] Internet-Draft March 2011 pmEnergyParametersIntervalLength OBJECT-TYPE SYNTAX TimeInterval UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the length of time in seconds over which to compute the average pmDemandIntervalEnergyUsed measurement in the pmEnergyTable table. The computation is based on the Power Monitor's internal sampling rate of power consumed or produced by the Power Monitor. The sampling rate is the rate at which the power monitor can read the power usage and may differ based on device capabilities. The average energy consumption is then computed over the length of the demand interval." DEFVAL { 900 } ::= { pmEnergyParametersEntry 1 } pmEnergyParametersIntervalNumber OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The number of demand intervals maintained in the pmEnergyTable table. Each interval is characterized by a specific pmDemandIntervalStartTime, used as an index in the the table pmEnergyTable table pmDemandIntervalStartTime. Whenever the maximum number of entries is reached, the new demand interval replaces the oldest one, except if the oldest one is the pmDemandIntervalMax, in which case the next oldest interval is replaced." DEFVAL { 10 } ::= { pmEnergyParametersEntry 2 } pmEnergyParametersIntervalMode OBJECT-TYPE SYNTAX INTEGER { period(1), sliding(2), total(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "A control object to define the mode of interval calculation for the computation of the average Expires September 14, 2011 [Page 47] Internet-Draft March 2011 pmDemandIntervalEnergyUsed measurement in the pmEnergyTable table. A mode of period(1) specifies non-overlapping periodic measurements. A mode of sliding(2) specifies overlapping sliding windows where the interval between the start of one interval and the next is defined in pmEnergyParametersIntervalWindow. A mode of total(3) specifies non-periodic measurement. In this mode only one interval is used as this is a continuous measurement since the last reset. The value of pmEnergyParametersIntervalNumber should be (1) one and pmEnergyParametersIntervalLength is ignored. " ::= { pmEnergyParametersEntry 3 } pmEnergyParametersIntervalWindow OBJECT-TYPE SYNTAX TimeInterval UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The length of the duration window between the starting time of one sliding window and the next starting time in seconds, in order to compute the average pmDemandIntervalEnergyUsed measurement in the pmEnergyTable table This is valid only when the pmEnergyParametersIntervalMode is sliding(2). The pmEnergyParametersIntervalWindow value should be a multiple of pmEnergyParametersSampleRate." ::= { pmEnergyParametersEntry 4 } pmEnergyParametersSampleRate OBJECT-TYPE SYNTAX Integer32 UNITS "Milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The sampling rate, in milliseconds, at which the Power Monitor should poll power usage in order to compute the average pmDemandIntervalEnergyUsed measurement in the table pmEnergyTable. The Power Monitor should initially set this sampling rate to a reasonable value, i.e., a compromise between intervals that will provide good accuracy by not being too long, but not so short that they affect the Power Monitor performance by requesting continuous polling. If the sampling rate is unknown, the value 0 is reported. The sampling rate should be selected Expires September 14, 2011 [Page 48] Internet-Draft March 2011 so that pmEnergyParametersIntervalWindow is a multiple of pmEnergyParametersSampleRate." DEFVAL { 1000 } ::= { pmEnergyParametersEntry 5 } pmEnergyParametersStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row. The pmEnergyParametersStatus is used to start or stop energy usage logging. An entry status may not be active(1) unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated usage-data logged into the pmEnergyTable will be deleted. The data can be destroyed by setting up the pmEnergyParametersStatus to destroy(2)." ::= {pmEnergyParametersEntry 6 } pmEnergyTable OBJECT-TYPE SYNTAX SEQUENCE OF PmEnergyIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists Power Monitor energy measurements. Entries in this table are only created if the corresponding value of object pmPowerMeasurementCaliber is active(2), i.e., if the power is actually metered." ::= { powerMonitorMIBObjects 5 } pmEnergyIntervalEntry OBJECT-TYPE SYNTAX PmEnergyIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describing energy measurements." INDEX { pmPowerIndex, pmEnergyParametersIntervalMode, pmEnergyIntervalStartTime } ::= { pmEnergyTable 1 } PmEnergyIntervalEntry ::= SEQUENCE { pmEnergyIntervalStartTime TimeTicks, Expires September 14, 2011 [Page 49] Internet-Draft March 2011 pmEnergyIntervalEnergyUsed Integer32, pmEnergyIntervalEnergyUnitMultiplier UnitMultiplier, pmEnergyIntervalMax Integer32, pmEnergyIntervalDiscontinuityTime TimeTicks } pmEnergyIntervalStartTime OBJECT-TYPE SYNTAX TimeTicks UNITS "hundredths of seconds" MAX-ACCESS not-accessible STATUS current DESCRIPTION "The time (in hundredths of a second) since the network management portion of the system was last re-initialized, as specified in the sysUpTime [RFC3418]. This object is useful for reference of interval periods for which the demand is measured." ::= { pmEnergyIntervalEntry 1 } pmEnergyIntervalEnergyUsed OBJECT-TYPE SYNTAX Integer32 UNITS "Watt-hours" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the energy used in units of watt- hours for the Power Monitor over the defined interval. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kW-Hr, MW- Hr, etc.) indicated separately in pmEnergyIntervalEnergyUnitMultiplier." ::= { pmEnergyIntervalEntry 2 } pmEnergyIntervalEnergyUnitMultiplier OBJECT-TYPE SYNTAX UnitMultiplier MAX-ACCESS read-only STATUS current DESCRIPTION "This object is the magnitude of watt-hours for the energy field in pmEnergyIntervalEnergyUsed." ::= { pmEnergyIntervalEntry 3 } pmEnergyIntervalMax OBJECT-TYPE SYNTAX Integer32 UNITS "Watt-hours" MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 14, 2011 [Page 50] Internet-Draft March 2011 "This object is the maximum demand ever observed in pmEnergyIntervalEnergyUsed since the monitoring started. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kW-Hr, MW- Hr, etc.) indicated separately in pmEnergyIntervalEnergyUnits." ::= { pmEnergyIntervalEntry 4 } pmEnergyIntervalDiscontinuityTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which any one or more of this entity's energy consumption counters suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value." ::= { pmEnergyIntervalEntry 5 } -- Notifications pmPowerStateChange NOTIFICATION-TYPE OBJECTS {pmPowerState,pmPowerManufacturerActualPowerState, pmPowerStateEnterReason} STATUS current DESCRIPTION "The SNMP entity generates the PmPowerStateChange when the value(s) of pmPowerState and/or pmPowerManufacturerActualPowerState has changed for the Power Monitor represented by the pmPowerIndex." ::= { powerMonitorMIBNotifs 1 } -- Conformance powerMonitorMIBCompliances OBJECT IDENTIFIER ::= { powerMonitorMIB 3 } powerMonitorMIBGroups OBJECT IDENTIFIER ::= { powerMonitorMIB 4 } powerMonitorMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented with support for Expires September 14, 2011 [Page 51] Internet-Draft March 2011 read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB." MODULE -- this module MANDATORY-GROUPS { powerMonitorMIBTableGroup, powerMonitorMIBStateTableGroup, powerMonitorMIBStateMappingTableGroup, powerMonitorMIBEnergyTableGroup, powerMonitorMIBEnergyParametersTableGroup, powerMonitorMIBNotifGroup } ::= { powerMonitorMIBCompliances 1 } powerMonitorMIBReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented without support for read-create (i.e. in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but can not be configured with this MIB." MODULE -- this module MANDATORY-GROUPS { powerMonitorMIBTableGroup, powerMonitorMIBStateTableGroup, powerMonitorMIBStateMappingTableGroup, powerMonitorMIBNotifGroup } OBJECT pmPowerState MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { powerMonitorMIBCompliances 2 } -- Units of Conformance powerMonitorMIBTableGroup OBJECT-GROUP OBJECTS { pmPower, pmPowerNameplate, pmPowerUnitMultiplier, pmPowerAccuracy, pmPowerMeasurementCaliber, pmPoweCurrentType, Expires September 14, 2011 [Page 52] Internet-Draft March 2011 pmPowerOrigin, pmPowerState, pmPowerActualState, pmPowerManufacturerActualPowerState, pmPowerManufacturerMappingId, pmPowerStateEnterReason } STATUS current DESCRIPTION "This group contains the collection of all the objects related to the PowerMonitor." ::= { powerMonitorMIBGroups 1 } powerMonitorMIBStateTableGroup OBJECT-GROUP OBJECTS { pmPowerStateMaxPower, pmPowerStatePowerUnitMultiplier, pmPowerStateTotalTime, pmPowerStateEnterCount } STATUS current DESCRIPTION "This group contains the collection of all the objects related to the Power State." ::= { powerMonitorMIBGroups 2 } powerMonitorMIBStateMappingTableGroup OBJECT-GROUP OBJECTS { pmManufacturerPowerStateMaxPower, pmManufacturerPowerStatePowerUnitMultiplier, pmManufacturerPowerStateName } STATUS current DESCRIPTION "This table enumerates the maximum power usage in watts, for every single Manufacturer Power State." ::= { powerMonitorMIBGroups 3 } powerMonitorMIBEnergyParametersTableGroup OBJECT-GROUP OBJECTS { pmEnergyParametersIntervalLength, pmEnergyParametersIntervalNumber, pmEnergyParametersIntervalMode, pmEnergyParametersIntervalWindow, Expires September 14, 2011 [Page 53] Internet-Draft March 2011 pmEnergyParametersSampleRate, pmEnergyParametersStatus } STATUS current DESCRIPTION "This group contains the collection of all the objects related to the configuration of the Demand Table." ::= { powerMonitorMIBGroups 4 } powerMonitorMIBEnergyTableGroup OBJECT-GROUP OBJECTS { -- Note that object -- pmDemandIntervalStartTime is not -- included since it is not-accessible pmEnergyIntervalEnergyUsed, pmEnergyIntervalEnergyUnitMultiplier, pmEnergyIntervalMax, pmEnergyIntervalDiscontinuityTime } STATUS current DESCRIPTION "This group contains the collection of all the objects related to the Demand Table." ::= { powerMonitorMIBGroups 5 } powerMonitorMIBNotifGroup NOTIFICATION-GROUP NOTIFICATIONS { pmPowerStateChange } STATUS current DESCRIPTION "This group contains the notifications for the power and energy monitoring MIB Module." ::= { powerMonitorMIBGroups 6 } END -- ************************************************************ -- -- This MIB module is used to monitor power quality of networked -- devices with measurements. -- -- This MIB module is an extension of powerMonitorMIB module. -- -- ************************************************************* Expires September 14, 2011 [Page 54] Internet-Draft March 2011 POWER-QUALITY-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, Integer32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF UnitMultiplier, pmPowerIndex FROM POWER-MONITOR-MIB OwnerString FROM RMON-MIB; powerQualityMIB MODULE-IDENTITY LAST-UPDATED "201103140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-snmp@cisco.com" DESCRIPTION "This MIB is used to report AC power quality in devices. The table is a sparse augmentation of the pmTable table from the powerMonitorMIB module. Both three-phase and single-phase power configurations are supported." REVISION "201103140000Z" DESCRIPTION "Initial version, published as RFC XXXX." ::= { mib-2 yyyyy } powerQualityMIBConform OBJECT IDENTIFIER ::= { powerQualityMIB 0 } Expires September 14, 2011 [Page 55] Internet-Draft March 2011 powerQualityMIBObjects OBJECT IDENTIFIER ::= { powerQualityMIB 1 } -- Objects pmACPwrQualityTable OBJECT-TYPE SYNTAX SEQUENCE OF PmACPwrQualityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines power quality measurements for supported pmPowerIndex entities. It is a sparse extension of the pmPowerTable." ::= { powerQualityMIBObjects 1 } pmACPwrQualityEntry OBJECT-TYPE SYNTAX PmACPwrQualityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This is a sparse extension of the pmTable with entries for power quality measurements or configuration. Each measured value corresponds to an attribute in IEC 61850-7-4 for non-phase measurements within the object MMUX." INDEX { pmPowerIndex } ::= { pmACPwrQualityTable 1 } PmACPwrQualityEntry ::= SEQUENCE { pmACPwrQualityConfiguration INTEGER, pmACPwrQualityAvgVoltage Integer32, pmACPwrQualityAvgCurrent Integer32, pmACPwrQualityFrequency Integer32, pmACPwrQualityPowerUnitMultiplier UnitMultiplier, pmACPwrQualityPowerAccuracy Integer32, pmACPwrQualityTotalActivePower Integer32, pmACPwrQualityTotalReactivePower Integer32, pmACPwrQualityTotalApparentPower Integer32, pmACPwrQualityTotalPowerFactor Integer32, pmACPwrQualityThdAmpheres Integer32, pmACPwrQualityThdVoltage Integer32 } pmACPwrQualityConfiguration OBJECT-TYPE SYNTAX INTEGER { sngl(1), del(2), Expires September 14, 2011 [Page 56] Internet-Draft March 2011 wye(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Configuration describes the physical configurations of the power supply lines: * alternating current, single phase (SNGL) * alternating current, three phase delta (DEL) * alternating current, three phase Y (WYE) Three-phase configurations can be either connected in a triangular delta (DEL) or star Y (WYE) system. WYE systems have a shared neutral voltage, while DEL systems do not. Each phase is offset 120 degrees to each other." ::= { pmACPwrQualityEntry 1 } pmACPwrQualityAvgVoltage OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 Volt AC" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value for average 'instantaneous' RMS line voltage. For a 3-phase system, this is the average voltage (V1+V2+V3)/3. IEC 61850-7-4 measured value attribute 'Vol'" ::= { pmACPwrQualityEntry 2 } pmACPwrQualityAvgCurrent OBJECT-TYPE SYNTAX Integer32 UNITS "Ampheres" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the current per phase. IEC 61850- 7-4 attribute 'Amp'" ::= { pmACPwrQualityEntry 3 } pmACPwrQualityFrequency OBJECT-TYPE SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz UNITS "hertz" MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 14, 2011 [Page 57] Internet-Draft March 2011 "A measured value for the basic frequency of the AC circuit. IEC 61850-7-4 attribute 'Hz'." ::= { pmACPwrQualityEntry 4 } pmACPwrQualityPowerUnitMultiplier OBJECT-TYPE SYNTAX UnitMultiplier MAX-ACCESS read-only STATUS current DESCRIPTION "The magnitude of watts for the usage value in pmACPwrQualityTotalActivePower, pmACPwrQualityTotalReactivePower and pmACPwrQualityTotalApparentPower measurements. For 3-phase power systems, this will also include pmACPwrQualityPhaseActivePower, pmACPwrQualityPhaseReactivePower and pmACPwrQualityPhaseApparentPower" ::= { pmACPwrQualityEntry 5 } pmACPwrQualityPowerAccuracy OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates a percentage value, in 100ths of a percent, representing the presumed accuracy of active, reactive, and apparent power usage reporting. For example: 1010 means the reported usage is accurate to +/- 10.1 percent. This value is zero if the accuracy is unknown. ANSI and IEC define the following accuracy classes for power measurement: IEC 62053-22 & 60044-1 class 0.1, 0.2, 0.5, 1 & 3. ANSI C12.20 class 0.2 & 0.5" ::= { pmACPwrQualityEntry 6 } pmACPwrQualityTotalActivePower OBJECT-TYPE SYNTAX Integer32 UNITS "RMS watts" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the actual power delivered to or consumed by the load. IEC 61850-7-4 attribute 'TotW'." ::= { pmACPwrQualityEntry 7 } Expires September 14, 2011 [Page 58] Internet-Draft March 2011 pmACPwrQualityTotalReactivePower OBJECT-TYPE SYNTAX Integer32 UNITS "volt-amperes reactive" MAX-ACCESS read-only STATUS current DESCRIPTION "A mesured value of the reactive portion of the apparent power. IEC 61850-7-4 attribute 'TotVAr'." ::= { pmACPwrQualityEntry 8 } pmACPwrQualityTotalApparentPower OBJECT-TYPE SYNTAX Integer32 UNITS "volt-amperes" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the voltage and current which determines the apparent power. The apparent power is the vector sum of real and reactive power. Note: watts and volt-ampheres are equivalent units and may be combined. IEC 61850-7-4 attribute 'TotVA'." ::= { pmACPwrQualityEntry 9 } pmACPwrQualityTotalPowerFactor OBJECT-TYPE SYNTAX Integer32 (-10000..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value ratio of the real power flowing to the load versus the apparent power. It is dimensionless and expressed here as a percentage value in 100ths of a percent. A power factor of 100% indicates there is no inductance load and thus no reactive power. Power Factor can be positive or negative, where the sign should be in lead/lag (IEEE) form. IEC 61850-7-4 attribute 'TotPF'." ::= { pmACPwrQualityEntry 10 } pmACPwrQualityThdAmpheres OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 14, 2011 [Page 59] Internet-Draft March 2011 "A calculated value for the current total harmonic distortion (THD). Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdAmp'." ::= { pmACPwrQualityEntry 11 } pmACPwrQualityThdVoltage OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "A calculated value for the voltage total harmonic distortion (THD). Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdVol'." ::= { pmACPwrQualityEntry 12 } pmACPwrQualityPhaseTable OBJECT-TYPE SYNTAX SEQUENCE OF PmACPwrQualityPhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes 3-phase power quality measurements. It is a sparse extension of the pmACPwrQualityTable." ::= { powerQualityMIBObjects 2 } pmACPwrQualityPhaseEntry OBJECT-TYPE SYNTAX PmACPwrQualityPhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describes common 3-phase power quality measurements. This optional table describes 3-phase power quality measurements, with three entries for each supported pmPowerIndex entity. Entities having single phase power shall not have any entities. This table describes attributes common to both WYE and DEL. Entities having single phase power shall not have any entries here. It is a sparse extension of the pmACPwrQualityTable. These attributes correspond to IEC 61850-7.4 MMXU phase measurements." INDEX { pmPowerIndex, pmPhaseIndex } ::= { pmACPwrQualityPhaseTable 1 } Expires September 14, 2011 [Page 60] Internet-Draft March 2011 PmACPwrQualityPhaseEntry ::= SEQUENCE { pmPhaseIndex Integer32, pmACPwrQualityPhaseAvgCurrent Integer32, pmACPwrQualityPhaseActivePower Integer32, pmACPwrQualityPhaseReactivePower Integer32, pmACPwrQualityPhaseApparentPower Integer32, pmACPwrQualityPhasePowerFactor Integer32, pmACPwrQualityPhaseImpedance Integer32 } pmPhaseIndex OBJECT-TYPE SYNTAX Integer32 (0..359) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A phase angle typically corresponding to 0, 120, 240." ::= { pmACPwrQualityPhaseEntry 1 } pmACPwrQualityPhaseAvgCurrent OBJECT-TYPE SYNTAX Integer32 UNITS "Ampheres" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the current per phase. IEC 61850- 7-4 attribute 'A'" ::= { pmACPwrQualityPhaseEntry 2 } pmACPwrQualityPhaseActivePower OBJECT-TYPE SYNTAX Integer32 UNITS "RMS watts" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the actual power delivered to or consumed by the load. IEC 61850-7-4 attribute 'W'" ::= { pmACPwrQualityPhaseEntry 3 } pmACPwrQualityPhaseReactivePower OBJECT-TYPE SYNTAX Integer32 UNITS "volt-amperes reactive" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the reactive portion of the apparent power. IEC 61850-7-4 attribute 'VAr'" ::= { pmACPwrQualityPhaseEntry 4 } Expires September 14, 2011 [Page 61] Internet-Draft March 2011 pmACPwrQualityPhaseApparentPower OBJECT-TYPE SYNTAX Integer32 UNITS "volt-amperes" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the voltage and current determines the apparent power. Active plus reactive power equals the total apparent powwer. Note: Watts and volt-ampheres are equivalent units and may be combined. IEC 61850-7-4 attribute 'VA'." ::= { pmACPwrQualityPhaseEntry 5 } pmACPwrQualityPhasePowerFactor OBJECT-TYPE SYNTAX Integer32 (-10000..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value ratio of the real power flowing to the load versus the apparent power for this phase. IEC 61850-7-4 attribute 'PF'. Power Factor can be positive or negative where the sign should be in lead/lag (IEEE) form." ::= { pmACPwrQualityPhaseEntry 6 } pmACPwrQualityPhaseImpedance OBJECT-TYPE SYNTAX Integer32 UNITS "volt-amperes" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of the impedance. IEC 61850-7-4 attribute 'Z'." ::= { pmACPwrQualityPhaseEntry 7 } pmACPwrQualityDelPhaseTable OBJECT-TYPE SYNTAX SEQUENCE OF PmACPwrQualityDelPhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes DEL configuration phase-to-phase power quality measurements. This is a sparse extension of the pmACPwrQualityPhaseTable." ::= { powerQualityMIBObjects 3 } Expires September 14, 2011 [Page 62] Internet-Draft March 2011 pmACPwrQualityDelPhaseEntry OBJECT-TYPE SYNTAX PmACPwrQualityDelPhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describes quality attributes of a phase in a DEL 3-phase power system. Voltage measurements are provided both relative to each other and zero. Measured values are from IEC 61850-7-2 MMUX and THD from MHAI objects. For phase-to-phase measurements, the pmPhaseIndex is compared against the following phase at +120 degrees. Thus, the possible values are: pmPhaseIndex Next Phase Angle 0 120 120 240 240 0 " INDEX { pmPowerIndex, pmPhaseIndex} ::= { pmACPwrQualityDelPhaseTable 1} PmACPwrQualityDelPhaseEntry ::= SEQUENCE { pmACPwrQualityDelPhaseToNextPhaseVoltage Integer32, pmACPwrQualityDelThdPhaseToNextPhaseVoltage Integer32, pmACPwrQualityDelThdCurrent Integer32 } pmACPwrQualityDelPhaseToNextPhaseVoltage OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 Volt AC" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of phase to next phase voltages, where the next phase is IEC 61850-7-4 attribute 'PPV'." ::= { pmACPwrQualityDelPhaseEntry 2 } pmACPwrQualityDelThdPhaseToNextPhaseVoltage OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 14, 2011 [Page 63] Internet-Draft March 2011 "A calculated value for the voltage total harmonic disortion for phase to next phase. Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdPPV'." ::= { pmACPwrQualityDelPhaseEntry 3 } pmACPwrQualityDelThdCurrent OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "A calculated value for the voltage total harmonic disortion (THD) for phase to phase. Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdPPV'." ::= { pmACPwrQualityDelPhaseEntry 4 } pmACPwrQualityWyePhaseTable OBJECT-TYPE SYNTAX SEQUENCE OF PmACPwrQualityWyePhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes WYE configuration phase-to-neutral power quality measurements. This is a sparse extension of the pmACPwrQualityPhaseTable." ::= { powerQualityMIBObjects 4 } pmACPwrQualityWyePhaseEntry OBJECT-TYPE SYNTAX PmACPwrQualityWyePhaseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes measurements of WYE configuration with phase to neutral power quality attributes. Three entries are required for each supported pmPowerIndex entry. Voltage measurements are relative to neutral. This is a sparse extension of the pmACPwrQualityPhaseTable. Each entry describes quality attributes of one phase of a WYE 3-phase power system. Measured values are from IEC 61850-7-2 MMUX and THD from MHAI objects." INDEX { pmPowerIndex, pmPhaseIndex } ::= { pmACPwrQualityWyePhaseTable 1} Expires September 14, 2011 [Page 64] Internet-Draft March 2011 PmACPwrQualityWyePhaseEntry ::= SEQUENCE { pmACPwrQualityWyePhaseToNeutralVoltage Integer32, pmACPwrQualityWyePhaseCurrent Integer32, pmACPwrQualityWyeThdPhaseToNeutralVoltage Integer32 } pmACPwrQualityWyePhaseToNeutralVoltage OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 Volt AC" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of phase to neutral voltage. IEC 61850-7-4 attribute 'PhV'." ::= { pmACPwrQualityWyePhaseEntry 1 } pmACPwrQualityWyePhaseCurrent OBJECT-TYPE SYNTAX Integer32 UNITS "0.1 ampheres AC" MAX-ACCESS read-only STATUS current DESCRIPTION "A measured value of phase currents. IEC 61850-7-4 attribute 'A'." ::= { pmACPwrQualityWyePhaseEntry 2 } pmACPwrQualityWyeThdPhaseToNeutralVoltage OBJECT-TYPE SYNTAX Integer32 (0..10000) UNITS "hundredths of percent" MAX-ACCESS read-only STATUS current DESCRIPTION "A calculated value of the voltage total harmonic distortion (THD) for phase to neutral. IEC 61850-7-4 attribute 'ThdPhV'." ::= { pmACPwrQualityWyePhaseEntry 3 } -- Conformance powerQualityMIBCompliances OBJECT IDENTIFIER ::= { powerQualityMIB 2 } powerQualityMIBGroups OBJECT IDENTIFIER ::= { powerQualityMIB 3 } powerQualityMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION Expires September 14, 2011 [Page 65] Internet-Draft March 2011 "When this MIB is implemented with support for read- create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB." MODULE -- this module MANDATORY-GROUPS { powerACPwrQualityMIBTableGroup, powerACPwrQualityPhaseMIBTableGroup } GROUP powerACPwrQualityDelPhaseMIBTableGroup DESCRIPTION "This group must only be implemented for a DEL phase configuration." GROUP powerACPwrQualityWyePhaseMIBTableGroup DESCRIPTION "This group must only be implemented for a WYE phase configuration." ::= { powerQualityMIBCompliances 1 } -- Units of Conformance powerACPwrQualityMIBTableGroup OBJECT-GROUP OBJECTS { -- Note that object pmPowerIndex is NOT -- included since it is not-accessible pmACPwrQualityConfiguration, pmACPwrQualityAvgVoltage, pmACPwrQualityAvgCurrent, pmACPwrQualityFrequency, pmACPwrQualityPowerUnitMultiplier, pmACPwrQualityPowerAccuracy, pmACPwrQualityTotalActivePower, pmACPwrQualityTotalReactivePower, pmACPwrQualityTotalApparentPower, pmACPwrQualityTotalPowerFactor, pmACPwrQualityThdAmpheres, pmACPwrQualityThdVoltage } STATUS current DESCRIPTION "This group contains the collection of all the power quality objects related to the Power Monitor." ::= { powerQualityMIBGroups 1 } powerACPwrQualityPhaseMIBTableGroup OBJECT-GROUP Expires September 14, 2011 [Page 66] Internet-Draft March 2011 OBJECTS { -- Note that object pmPowerIndex is NOT -- included since it is not-accessible pmACPwrQualityPhaseAvgCurrent, pmACPwrQualityPhaseActivePower, pmACPwrQualityPhaseReactivePower, pmACPwrQualityPhaseApparentPower, pmACPwrQualityPhasePowerFactor, pmACPwrQualityPhaseImpedance } STATUS current DESCRIPTION "This group contains the collection of all 3-phase power quality objects related to the Power State." ::= { powerQualityMIBGroups 2 } powerACPwrQualityDelPhaseMIBTableGroup OBJECT-GROUP OBJECTS { -- Note that object pmPowerIndex and -- pmPhaseIndex are NOT included -- since they are not-accessible pmACPwrQualityDelPhaseToNextPhaseVoltage , pmACPwrQualityDelThdPhaseToNextPhaseVoltage, pmACPwrQualityDelThdCurrent } STATUS current DESCRIPTION "This group contains the collection of all quality attributes of a phase in a DEL 3-phase power system." ::= { powerQualityMIBGroups 3 } powerACPwrQualityWyePhaseMIBTableGroup OBJECT-GROUP OBJECTS { -- Note that object pmPowerIndex and -- pmPhaseIndex are NOT included -- since they are not-accessible pmACPwrQualityWyePhaseToNeutralVoltage, pmACPwrQualityWyePhaseCurrent, pmACPwrQualityWyeThdPhaseToNeutralVoltage } STATUS current DESCRIPTION "This group contains the collection of all WYE configuration phase-to-neutral power quality measurements." ::= { powerQualityMIBGroups 4 } Expires September 14, 2011 [Page 67] Internet-Draft March 2011 END 10. Security Considerations Some of the readable objects in these MIB modules (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. There are a number of management objects defined in these MIB modules with a MAX-ACCESS clause of read-write and/or read- create. Such objects MAY be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The following are the tables and objects and their sensitivity/vulnerability: . Unauthorized changes to the pmPowerState MAY disrupt the power settings of the different Power Monitors, and therefore the state of functionality of the respective Power Monitors. . Unauthorized changes to the pmDemandControlTable MAY disrupt energy measurement in the pmEnergyTable table. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example, by using IPsec), there is still no secure control over who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in these MIB modules. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of these MIB modules is properly configured to give access to the objects only to those principals (users) that have legitimate rights to GET or SET (change/create/delete) them. Expires September 14, 2011 [Page 68] Internet-Draft March 2011 11. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- PowerMonitorMIB { mib-2 xxx } Additions to this MIB module are subject to Expert Review [RFC5226], i.e., review by one of a group of experts designated by an IETF Area Director. The group of experts MUST check the requested MIB objects for completeness and accuracy of the description. Requests for MIB objects that duplicate the functionality of existing objects SHOULD be declined. The smallest available OID SHOULD be assigned to a new MIB objects. The specification of new MIB objects SHOULD follow the structure specified in Section 6 and MUST be published using a well- established and persistent publication medium. 12. Contributors This document results from the merger of two initial proposals. The following persons made significant contributions either in one of the initial proposals or in this document. John Parello Rolf Winter Dominique Dudkowski 13. Acknowledgment The authors would like to thank Shamita Pisal for her prototype of this MIB module, and her valuable feedback. The authors would like to Michael Brown for improving the text dramatically. 14. References 14.1. Normative References Expires September 14, 2011 [Page 69] Internet-Draft March 2011 [RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3621] Berger, A., and D. Romascanu, "Power Ethernet MIB", RFC3621, December 2003. [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005. [LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information Base extension module for TIA-TR41.4 media endpoint discovery information", July 2005. [POWER-AWARE-MIB], J. Parello, and B. Claise, "draft-parello- eman-energy-aware-mib-00", work in progress, October 2010. 14.2. Informative References [RFC1628] S. Bradner, "UPS Management Information Base", RFC 1628, May 1994 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet Standard Management Framework ", RFC 3410, December 2002. [RFC3418] Presun, R., Case, J., McCloghrie, K., Rose, M, and S. Waldbusser, "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", RFC3418, December 2002. Expires September 14, 2011 [Page 70] Internet-Draft March 2011 [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor Management Information Base", RFC 3433, December 2002. [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 4268,November 2005. [RFC5226] Narten, T. Alverstrand, H., A. and K. McCloghrie, "Guidelines for Writing an IANA Considerations Section in RFCs ", BCP 26, RFC 5226, May 2008. [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and M. Chandramouli, "Requirements for Power Monitoring", draft-ietf-eman-requirements-00 (work in progress), December 2010. [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., and J. Quittek, "Energy Management Framework", draft-ietf- eman-framework-01 (work in progress), March 2010. [ACPI] "Advanced Configuration and Power Interface Specification", http://www.acpi.info/spec30b.htm [DASH] "Desktop and mobile Architecture for System Hardware", http://www.dmtf.org/standards/mgmt/dash/ Authors' Addresses Mouli Chandramouli Cisco Systems, Inc. Sarjapur Outer Ring Road Bangalore, IN Phone: +91 80 4426 3947 Email: moulchan@cisco.com John Parello Cisco Systems, Inc. 3550 Cisco Way San Jose, California 95134 US Phone: +1 408 525 2339 Expires September 14, 2011 [Page 71] Internet-Draft March 2011 Email: jparello@cisco.com Brad Schoening 44 Rivers Edge Drive Little Silver, NJ 07739 US Email: brad@bradschoening.com Juergen Quittek (editor) NEC Europe Ltd. NEC Laboratories Europe Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 DE Phone: +49 6221 4342-115 Email: quittek@neclab.eu Thomas Dietz NEC Europe Ltd. NEC Laboratories Europe Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 DE Phone: +49 6221 4342-128 Email: Thomas.Dietz@neclab.eu Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 Diegem 1813 BE Phone: +32 2 704 5622 Email: bclaise@cisco.com Expires September 14, 2011 [Page 72] Internet-Draft March 2011 Expires September 14, 2011 [Page 73]