tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

RFC 7460

 
 
 

Monitoring and Control MIB for Power and Energy

Part 4 of 4, p. 50 to 69
Prev RFC Part

 


prevText      Top      Up      ToC       Page 50 
9.3.  The POWER-ATTRIBUTES-MIB MIB Module

   -- ************************************************************
   --
   -- This MIB module is used to monitor power attributes of
   -- networked devices with measurements.
   --
   -- This MIB module is an extension of energyObjectMib module.
   --
   -- *************************************************************

   POWER-ATTRIBUTES-MIB DEFINITIONS ::= BEGIN

   IMPORTS
       MODULE-IDENTITY,
       OBJECT-TYPE,
       mib-2,
       Integer32, Unsigned32
          FROM SNMPv2-SMI
       MODULE-COMPLIANCE,
       OBJECT-GROUP
           FROM SNMPv2-CONF
      UnitMultiplier
         FROM ENERGY-OBJECT-MIB
       entPhysicalIndex
          FROM ENTITY-MIB;

   powerAttributesMIB MODULE-IDENTITY
       LAST-UPDATED    "201502090000Z"    -- 9 February 2015
       ORGANIZATION    "IETF EMAN Working Group"
       CONTACT-INFO
               "WG charter:
                http://datatracker.ietf.org/wg/eman/charter/

                Mailing Lists:
                General Discussion: eman@ietf.org

                To Subscribe:
                https://www.ietf.org/mailman/listinfo/eman

                Archive:
                http://www.ietf.org/mail-archive/web/eman

Top      Up      ToC       Page 51 
             Editors:

                Mouli Chandramouli
                Cisco Systems, Inc.
                Sarjapur Outer Ring Road
                Bangalore 560103
                India
                Phone: +91 80 4429 2409
                Email: moulchan@cisco.com

                Brad Schoening
                44 Rivers Edge Drive
                Little Silver, NJ 07739
                United States
                Email: brad.schoening@verizon.net

                Juergen Quittek
                NEC Europe Ltd.
                NEC Laboratories Europe
                Network Research Division
                Kurfuersten-Anlage 36
                Heidelberg  69115
                Germany
                Phone: +49 6221 4342-115
                Email: quittek@neclab.eu

                Thomas Dietz
                NEC Europe Ltd.
                NEC Laboratories Europe
                Network Research Division
                Kurfuersten-Anlage 36
                69115 Heidelberg
                Germany
                Phone: +49 6221 4342-128
                Email: Thomas.Dietz@nw.neclab.eu

                Benoit Claise
                Cisco Systems, Inc.
                De Kleetlaan 6a b1
                Degem 1831
                Belgium
                Phone:  +32 2 704 5622
                Email: bclaise@cisco.com"

Top      Up      ToC       Page 52 
       DESCRIPTION
          "Copyright (c) 2015 IETF Trust and the persons identified as
           authors of the code.  All rights reserved.

           Redistribution and use in source and binary forms, with or
           without modification, is permitted pursuant to, and subject
           to the license terms contained in, the Simplified BSD License
           set forth in Section 4.c of the IETF Trust's Legal Provisions
           Relating to IETF Documents
           (http://trustee.ietf.org/license-info).

           This MIB is used to report AC power attributes in devices.
           The table is a sparse augmentation of the eoPowerTable table
           from the energyObjectMib module.  Both three-phase and
           single-phase power configurations are supported.

           As a requirement for this MIB module, RFC 7461 SHOULD be
           implemented.

           Module Compliance of ENTITY-MIB v4 with respect to
           entity4CRCompliance MUST be supported which requires
           implementation of four MIB objects: entPhysicalIndex,
           entPhysicalClass, entPhysicalName, and entPhysicalUUID."
       REVISION "201502090000Z"     -- 9 February 2015
       DESCRIPTION
          "Initial version, published as RFC 7460"

      ::= { mib-2 230 }

   powerAttributesMIBConform  OBJECT IDENTIFIER
       ::= { powerAttributesMIB 0 }

   powerAttributesMIBObjects OBJECT IDENTIFIER
       ::= { powerAttributesMIB 1 }

   -- Objects

   eoACPwrAttributesTable OBJECT-TYPE
       SYNTAX          SEQUENCE OF EoACPwrAttributesEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "This table contains power attributes measurements for
          supported entPhysicalIndex entities.  It is a sparse
          extension of the eoPowerTable."
       ::= { powerAttributesMIBObjects 1 }

   eoACPwrAttributesEntry OBJECT-TYPE

Top      Up      ToC       Page 53 
       SYNTAX          EoACPwrAttributesEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "This is a sparse extension of the eoPowerTable with
          entries for power attributes measurements or
          configuration.  Each measured value corresponds to an
          attribute in IEC 61850-7-4 for non-phase measurements
          within the object MMXN."
       INDEX { entPhysicalIndex }
       ::= { eoACPwrAttributesTable 1 }

   EoACPwrAttributesEntry ::= SEQUENCE {
       eoACPwrAttributesConfiguration      INTEGER,
       eoACPwrAttributesAvgVoltage          Integer32,
       eoACPwrAttributesAvgCurrent          Unsigned32,
       eoACPwrAttributesFrequency           Integer32,
       eoACPwrAttributesPowerUnitMultiplier UnitMultiplier,
       eoACPwrAttributesPowerAccuracy      Integer32,
       eoACPwrAttributesTotalActivePower    Integer32,
       eoACPwrAttributesTotalReactivePower  Integer32,
       eoACPwrAttributesTotalApparentPower  Integer32,
       eoACPwrAttributesTotalPowerFactor    Integer32,
       eoACPwrAttributesThdCurrent          Integer32,
       eoACPwrAttributesThdVoltage         Integer32
                             }

   eoACPwrAttributesConfiguration OBJECT-TYPE
       SYNTAX INTEGER {
               sngl(1),
               del(2),
               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."
       ::= { eoACPwrAttributesEntry 1 }

Top      Up      ToC       Page 54 
   eoACPwrAttributesAvgVoltage OBJECT-TYPE
       SYNTAX          Integer32
       UNITS           "0.1 Volt AC"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A measured value for average of the voltage measured
          over an integral number of AC cycles.  For a three-phase
          system, this is the average voltage (V1+V2+V3)/3.  IEC
          61850-7-4 measured value attribute 'Vol'."
       ::= { eoACPwrAttributesEntry 2 }

   eoACPwrAttributesAvgCurrent OBJECT-TYPE
       SYNTAX          Unsigned32
       UNITS           "amperes"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A measured value for average of the current measured
          over an integral number of AC cycles.  For a three-phase
          system, this is the average current (I1+I2+I3)/3.  IEC
          61850-7-4 attribute 'Amp'."
       ::= { eoACPwrAttributesEntry 3 }

   eoACPwrAttributesFrequency OBJECT-TYPE
       SYNTAX          Integer32 (4500..6500)
       UNITS           "0.01 hertz"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A measured value for the basic frequency of the AC
          circuit.  IEC 61850-7-4 attribute 'Hz'."
       ::= { eoACPwrAttributesEntry 4 }

   eoACPwrAttributesPowerUnitMultiplier OBJECT-TYPE
       SYNTAX          UnitMultiplier
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "The magnitude of watts for the usage value in
          eoACPwrAttributesTotalActivePower,
          eoACPwrAttributesTotalReactivePower,
          and eoACPwrAttributesTotalApparentPower measurements.
          For three-phase power systems, this will also include
          eoACPwrAttributesWyeActivePower,
          eoACPwrAttributesWyeReactivePower, and
          eoACPwrAttributesWyeApparentPower."
       ::= { eoACPwrAttributesEntry 5 }

Top      Up      ToC       Page 55 
   eoACPwrAttributesPowerAccuracy OBJECT-TYPE
       SYNTAX          Integer32 (0..10000)
       UNITS           "hundredths of percent"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "This object indicates a percentage value, in hundredths 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"
       ::= { eoACPwrAttributesEntry 6 }

   eoACPwrAttributesTotalActivePower OBJECT-TYPE
       SYNTAX          Integer32
       UNITS           "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'."
       ::= { eoACPwrAttributesEntry 7 }

   eoACPwrAttributesTotalReactivePower 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 'TotVAr'."
       ::= { eoACPwrAttributesEntry 8 }

   eoACPwrAttributesTotalApparentPower OBJECT-TYPE
       SYNTAX          Integer32
       UNITS           "volt-amperes"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A measured value of the voltage and current that
          determines the apparent power.  The apparent power is the
          vector sum of real and reactive power.

Top      Up      ToC       Page 56 
          Note: watts and volt-amperes are equivalent units and may
          be combined.  IEC 61850-7-4 attribute 'TotVA'."
       ::= { eoACPwrAttributesEntry 9 }

   eoACPwrAttributesTotalPowerFactor OBJECT-TYPE
       SYNTAX          Integer32 (-10000..10000)
       UNITS           "hundredths"
       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 hundredths.  A power
          factor of 100% indicates there is no inductance load and
          thus no reactive power.  A Power Factor can be positive or
          negative, where the sign should be in lead/lag (IEEE)
          form.  IEC 61850-7-4 attribute 'TotPF'."
       ::= { eoACPwrAttributesEntry 10 }

   eoACPwrAttributesThdCurrent OBJECT-TYPE
       SYNTAX          Integer32 (0..10000)
       UNITS           "hundredths of percent"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A calculated value for the current total harmonic
          distortion (THD).  Method of calculation is not
          specified.  IEC 61850-7-4 attribute 'ThdAmp'."
       ::= { eoACPwrAttributesEntry 11 }

   eoACPwrAttributesThdVoltage 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).  The method of calculation is not
          specified.  IEC 61850-7-4 attribute 'ThdVol'."
       ::= { eoACPwrAttributesEntry 12 }

   eoACPwrAttributesDelPhaseTable OBJECT-TYPE
       SYNTAX          SEQUENCE OF EoACPwrAttributesDelPhaseEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "This optional table describes three-phase power attributes
          measurements in a DEL configuration with phase-to-phase

Top      Up      ToC       Page 57 
          power attributes measurements.  Entities having single
          phase power shall not have any entities.  This is a
          sparse extension of the eoACPwrAttributesTable.

          These attributes correspond to measurements related to
          the IEC 61850-7.4 MMXU phase and measured harmonic or
          interharmonics related to the MHAI phase."
       ::= { powerAttributesMIBObjects 2 }

   eoACPwrAttributesDelPhaseEntry OBJECT-TYPE
       SYNTAX          EoACPwrAttributesDelPhaseEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "An entry describes power measurements of a phase in a
          DEL three-phase power.  Three entries are required for each
          supported entPhysicalIndex entry.  Voltage measurements
          are provided relative to each other.

          For phase-to-phase measurements, the
          eoACPwrAttributesDelPhaseIndex is compared against the
          following phase at +120 degrees.  Thus, the possible
          values are:

          eoACPwrAttributesDelPhaseIndex    Next Phase Angle
                                0                 120
                               120                240
                               240                  0
          "
       INDEX { entPhysicalIndex, eoACPwrAttributesDelPhaseIndex }
       ::= { eoACPwrAttributesDelPhaseTable 1}

   EoACPwrAttributesDelPhaseEntry ::= SEQUENCE {
       eoACPwrAttributesDelPhaseIndex                   Integer32,
       eoACPwrAttributesDelPhaseToNextPhaseVoltage      Integer32,
       eoACPwrAttributesDelThdPhaseToNextPhaseVoltage   Integer32
                                      }

   eoACPwrAttributesDelPhaseIndex OBJECT-TYPE
       SYNTAX          Integer32 (0..359)
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "A phase angle typically corresponding to 0, 120, 240."
        ::= { eoACPwrAttributesDelPhaseEntry 1 }

   eoACPwrAttributesDelPhaseToNextPhaseVoltage OBJECT-TYPE
       SYNTAX          Integer32

Top      Up      ToC       Page 58 
       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'."
       ::= { eoACPwrAttributesDelPhaseEntry 2 }

   eoACPwrAttributesDelThdPhaseToNextPhaseVoltage 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 for phase to next phase.  Method of calculation
          is not specified.  IEC 61850-7-4 attribute 'ThdPPV'."
       ::= { eoACPwrAttributesDelPhaseEntry 3 }

   eoACPwrAttributesWyePhaseTable OBJECT-TYPE
       SYNTAX          SEQUENCE OF EoACPwrAttributesWyePhaseEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "This optional table describes three-phase power attributes
          measurements in a WYE configuration with phase-to-neutral
          power attributes measurements.  Entities having single
          phase power shall not have any entities.  This is a sparse
          extension of the eoACPwrAttributesTable.

          These attributes correspond to measurements related to
          the IEC 61850-7.4 MMXU phase and measured harmonic or
          interharmonics related to the MHAI phase."
       ::= { powerAttributesMIBObjects 3 }

   eoACPwrAttributesWyePhaseEntry OBJECT-TYPE
       SYNTAX          EoACPwrAttributesWyePhaseEntry
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "This table describes measurements of a phase in a WYE
          three-phase power system.  Three entries are required for
          each supported entPhysicalIndex entry.  Voltage
          measurements are relative to neutral.

          Each entry describes power attributes of one phase of a
          WYE three-phase power system."
       INDEX { entPhysicalIndex, eoACPwrAttributesWyePhaseIndex }

Top      Up      ToC       Page 59 
       ::= { eoACPwrAttributesWyePhaseTable 1}

   EoACPwrAttributesWyePhaseEntry ::= SEQUENCE {
        eoACPwrAttributesWyePhaseIndex            Integer32,
        eoACPwrAttributesWyePhaseToNeutralVoltage  Integer32,
        eoACPwrAttributesWyeCurrent              Integer32,
        eoACPwrAttributesWyeActivePower            Integer32,
        eoACPwrAttributesWyeReactivePower          Integer32,
        eoACPwrAttributesWyeApparentPower          Integer32,
        eoACPwrAttributesWyePowerFactor            Integer32,
        eoACPwrAttributesWyeThdCurrent            Integer32,
        eoACPwrAttributesWyeThdPhaseToNeutralVoltage Integer32
                                      }

   eoACPwrAttributesWyePhaseIndex OBJECT-TYPE
       SYNTAX          Integer32 (0..359)
       MAX-ACCESS      not-accessible
       STATUS          current
       DESCRIPTION
          "A phase angle typically corresponding to 0, 120, 240."
        ::= { eoACPwrAttributesWyePhaseEntry 1 }

   eoACPwrAttributesWyePhaseToNeutralVoltage 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 'PNV'."
       ::= { eoACPwrAttributesWyePhaseEntry 2 }

   eoACPwrAttributesWyeCurrent OBJECT-TYPE
       SYNTAX          Integer32
       UNITS           "0.1 amperes AC"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A measured value of phase currents.  IEC 61850-7-4
          attribute 'A'."
       ::= { eoACPwrAttributesWyePhaseEntry 3 }

   eoACPwrAttributesWyeActivePower OBJECT-TYPE
       SYNTAX          Integer32
       UNITS           "watts"
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION

Top      Up      ToC       Page 60 
          "A measured value of the actual power delivered to or
          consumed by the load with the magnitude indicated
          separately in eoPowerUnitMultiplier.  IEC 61850-7-4
          attribute 'W'."
       ::= { eoACPwrAttributesWyePhaseEntry 4 }

   eoACPwrAttributesWyeReactivePower 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 with the magnitude of indicated separately in
          eoPowerUnitMultiplier.  IEC 61850-7-4 attribute 'VAr'."
       ::= { eoACPwrAttributesWyePhaseEntry 5 }

   eoACPwrAttributesWyeApparentPower 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 with the indicated separately in
          eoPowerUnitMultiplier.  Active plus reactive power equals
          the total apparent power.

          Note: Watts and volt-amperes are equivalent units and may
          be combined.  IEC 61850-7-4 attribute 'VA'."
       ::= { eoACPwrAttributesWyePhaseEntry 6 }

   eoACPwrAttributesWyePowerFactor OBJECT-TYPE
       SYNTAX          Integer32 (-10000..10000)
       UNITS           "hundredths"
       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."
       ::= { eoACPwrAttributesWyePhaseEntry 7 }

   eoACPwrAttributesWyeThdCurrent OBJECT-TYPE
       SYNTAX          Integer32 (0..10000)
       UNITS           "hundredths of percent"

Top      Up      ToC       Page 61 
       MAX-ACCESS      read-only
       STATUS          current
       DESCRIPTION
          "A calculated value for the voltage total harmonic
          distortion (THD) for phase to phase.  Method of
          calculation is not specified.
          IEC 61850-7-4 attribute 'ThdA'."
       ::= { eoACPwrAttributesWyePhaseEntry 8 }

   eoACPwrAttributesWyeThdPhaseToNeutralVoltage 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'."
       ::= { eoACPwrAttributesWyePhaseEntry 9 }

   -- Conformance
   powerAttributesMIBCompliances  OBJECT IDENTIFIER
       ::= { powerAttributesMIB 2 }

   powerAttributesMIBGroups  OBJECT IDENTIFIER
       ::= { powerAttributesMIB 3 }

   powerAttributesMIBFullCompliance MODULE-COMPLIANCE
       STATUS          current
       DESCRIPTION
          "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 Compliance of RFC 6933 with respect to
          entity4CRCompliance MUST be supported which requires
          implementation of four MIB objects: entPhysicalIndex,
          entPhysicalClass, entPhysicalName, and entPhysicalUUID."
       REFERENCE
          "RFC 6933: Entity MIB (Version 4)"

       MODULE          -- this module
       MANDATORY-GROUPS {
                        powerACPwrAttributesMIBTableGroup
                                 }

       GROUP        powerACPwrAttributesOptionalMIBTableGroup

Top      Up      ToC       Page 62 
       DESCRIPTION
          "A compliant implementation does not have
          to implement."

       GROUP       powerACPwrAttributesDelPhaseMIBTableGroup
       DESCRIPTION
           "A compliant implementation does not have to implement."

       GROUP       powerACPwrAttributesWyePhaseMIBTableGroup
       DESCRIPTION
           "A compliant implementation does not have to implement."
       ::= { powerAttributesMIBCompliances 1 }

   -- Units of Conformance

   powerACPwrAttributesMIBTableGroup OBJECT-GROUP
       OBJECTS         {
                  -- Note that object entPhysicalIndex is NOT
                    -- included since it is not-accessible
                           eoACPwrAttributesAvgVoltage,
                           eoACPwrAttributesAvgCurrent,
                           eoACPwrAttributesFrequency,
                           eoACPwrAttributesPowerUnitMultiplier,
                           eoACPwrAttributesPowerAccuracy,
                           eoACPwrAttributesTotalActivePower,
                           eoACPwrAttributesTotalReactivePower,
                           eoACPwrAttributesTotalApparentPower,
                           eoACPwrAttributesTotalPowerFactor
                                               }
       STATUS          current
       DESCRIPTION
          "This group contains the collection of all the power
          attributes objects related to the Energy Object."
       ::= { powerAttributesMIBGroups  1 }

    powerACPwrAttributesOptionalMIBTableGroup OBJECT-GROUP
       OBJECTS         {
                           eoACPwrAttributesConfiguration,
                           eoACPwrAttributesThdCurrent,
                           eoACPwrAttributesThdVoltage
                       }
       STATUS          current
       DESCRIPTION
          "This group contains the collection of all the power
          attributes objects related to the Energy Object."
       ::= { powerAttributesMIBGroups  2 }

   powerACPwrAttributesDelPhaseMIBTableGroup OBJECT-GROUP

Top      Up      ToC       Page 63 
       OBJECTS         {
                       -- Note that object entPhysicalIndex and
                       -- eoACPwrAttributesDelPhaseIndex are NOT
                       -- included since they are not-accessible
                 eoACPwrAttributesDelPhaseToNextPhaseVoltage,
                 eoACPwrAttributesDelThdPhaseToNextPhaseVoltage
                       }
       STATUS          current
       DESCRIPTION
          "This group contains the collection of all power
          attributes of a phase in a DEL three-phase power system."
       ::= { powerAttributesMIBGroups 3 }

   powerACPwrAttributesWyePhaseMIBTableGroup OBJECT-GROUP
       OBJECTS         {
                          -- Note that object entPhysicalIndex and
                          -- eoACPwrAttributesWyePhaseIndex are NOT
                          -- included since they are not-accessible
                  eoACPwrAttributesWyePhaseToNeutralVoltage,
                  eoACPwrAttributesWyeCurrent,
                  eoACPwrAttributesWyeActivePower,
                  eoACPwrAttributesWyeReactivePower,
                  eoACPwrAttributesWyeApparentPower,
                  eoACPwrAttributesWyePowerFactor,
                  eoACPwrAttributesWyeThdPhaseToNeutralVoltage,
                  eoACPwrAttributesWyeThdCurrent
                       }
       STATUS          current
       DESCRIPTION
          "This group contains the collection of all power
          attributes of a phase in a WYE three-phase power system."
       ::= { powerAttributesMIBGroups 4 }

   END

10.  Security Considerations

   There are a number of management objects defined in this MIB module
   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 opens devices to attack.  These
   are the tables and objects and their sensitivity/vulnerability:

      - Unauthorized changes to the eoPowerOperState (via the
        eoPowerAdminState ) MAY disrupt the power settings of the
        differentEnergy Objects and, therefore, the state of
        functionality of the respective Energy Objects.

Top      Up      ToC       Page 64 
      - Unauthorized changes to the eoEnergyParametersTable MAY disrupt
        energy measurement in the eoEnergyTable 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 no control as to who on the secure network is allowed to
   access and GET/SET (read/change/create/delete) the objects in this
   MIB module.

   Implementations SHOULD provide the security features described by the
   SNMPv3 framework (see [RFC3410]), and implementations claiming
   compliance to the SNMPv3 standard MUST include full support for
   authentication and privacy via the User-based Security Model (USM)
   [RFC3414] with the AES cipher algorithm [RFC3826].  Implementations
   MAY also provide support for the Transport Security Model (TSM)
   [RFC5591] in combination with a secure transport such as SSH
   [RFC5592] or TLS/DTLS [RFC6353].

   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 this MIB module is properly configured to give access to
   the objects only to those principals (users) that have legitimate
   rights to indeed GET or SET (change/create/delete) them.

   In certain situations, energy and power monitoring can reveal
   sensitive information about individuals' activities and habits.
   Implementors of this specification should use appropriate privacy
   protections as discussed in Section 9 of RFC 6988 and monitoring of
   individuals and homes should only occur with proper authorization.

11.  IANA Considerations

   The MIB modules in this document use the following IANA-assigned
   OBJECT IDENTIFIER values recorded in the SMI Numbers registry:

      Descriptor                   OBJECT IDENTIFIER value
      ----------                   -----------------------

      IANAPowerStateSet-MIB           { mib-2 228 }

      energyObjectMIB                 { mib-2 229 }

      powerAttributesMIB              { mib-2 230 }

Top      Up      ToC       Page 65 
11.1.  IANAPowerStateSet-MIB Module

   The initial set of Power State Sets are specified in [RFC7326].  IANA
   maintains a Textual Convention PowerStateSet in the
   IANAPowerStateSet-MIB module (see Section 9.1), with the initial set
   of Power State Sets and the Power States within those Power State
   Sets as proposed in the [RFC7326].  The current version of
   PowerStateSet Textual Convention can be accessed
   <http://www.iana.org/assignments/power-state-sets>.

   New assignments (and potential deprecation) to Power State Sets shall
   be administered by IANA and the guidelines and procedures are
   specified in [RFC7326], and will, as a consequence, update the
   PowerStateSet Textual Convention.

12.  References

12.1.  Normative References

   [RFC2119]       Bradner, S., "Key words for use in RFCs to Indicate
                   Requirement Levels", BCP 14, RFC 2119, March 1997,
                   <http://www.rfc-editor.org/info/rfc2119>.

   [RFC2578]       McCloghrie, K., Ed., Perkins, D., Ed., and J.
                   Schoenwaelder, Ed., "Structure of Management
                   Information Version 2 (SMIv2)", STD 58, RFC 2578,
                   April 1999, <http://www.rfc-editor.org/info/rfc2578>.

   [RFC2579]       McCloghrie, K., Ed., Perkins, D., Ed., and J.
                   Schoenwaelder, Ed., "Textual Conventions for SMIv2",
                   STD 58, RFC 2579, April 1999,
                   <http://www.rfc-editor.org/info/rfc2579>.

   [RFC2580]       McCloghrie, K., Ed., Perkins, D., Ed., and J.
                   Schoenwaelder, Ed., "Conformance Statements for
                   SMIv2", STD 58, RFC 2580, April 1999,
                   <http://www.rfc-editor.org/info/rfc2580>.

   [RFC3414]       Blumenthal, U. and B. Wijnen, "User-based Security
                   Model (USM) for version 3 of the Simple Network
                   Management Protocol (SNMPv3)", STD 62, RFC 3414,
                   December 2002,
                   <http://www.rfc-editor.org/info/rfc3414>.

   [RFC3621]       Berger, A. and D. Romascanu, "Power Ethernet MIB",
                   RFC 3621, December 2003,
                   <http://www.rfc-editor.org/info/rfc3621>.

Top      Up      ToC       Page 66 
   [RFC3826]       Blumenthal, U., Maino, F., and K. McCloghrie, "The
                   Advanced Encryption Standard (AES) Cipher Algorithm
                   in the SNMP User-based Security Model", RFC 3826,
                   June 2004, <http://www.rfc-editor.org/info/rfc3826>.

   [RFC5591]       Harrington, D. and W. Hardaker, "Transport Security
                   Model for the Simple Network Management Protocol
                   (SNMP)", STD 78, RFC 5591, June 2009,
                   <http://www.rfc-editor.org/info/rfc5591>.

   [RFC5592]       Harrington, D., Salowey, J., and W. Hardaker, "Secure
                   Shell Transport Model for the Simple Network
                   Management Protocol (SNMP)", RFC 5592, June 2009,
                   <http://www.rfc-editor.org/info/rfc5592>.

   [RFC6353]       Hardaker, W., "Transport Layer Security (TLS)
                   Transport Model for the Simple Network Management
                   Protocol (SNMP)", STD 78, RFC 6353, July 2011,
                   <http://www.rfc-editor.org/info/rfc6353>.

   [RFC6933]       Bierman, A., Romascanu, D., Quittek, J., and M.
                   Chandramouli, "Entity MIB (Version 4)", RFC 6933, May
                   2013, <http://www.rfc-editor.org/info/rfc6933>.

   [RFC7461]       Parello, J., Claise, B., and M. Chandramouli, "Energy
                   Object Context MIB", RFC 7461, March 2015,
                   <http://www.rfc-editor.org/info/rfc7461>.

   [LLDP-MED-MIB]  ANSI/TIA-1057, "The LLDP Management Information Base
                   extension module for TIA-TR41.4 media endpoint
                   discovery information", July 2005.

12.2.  Informative References

   [RFC1628]       Case, J., Ed., "UPS Management Information Base", RFC
                   1628, May 1994,
                   <http://www.rfc-editor.org/info/rfc1628>.

   [RFC3410]       Case, J., Mundy, R., Partain, D., and B. Stewart,
                   "Introduction and Applicability Statements for
                   Internet-Standard Management Framework", RFC 3410,
                   December 2002,
                   <http://www.rfc-editor.org/info/rfc3410>.

   [RFC3418]       Presuhn, R., Ed., "Management Information Base (MIB)
                   for the Simple Network Management Protocol (SNMP)",
                   STD 62, RFC 3418, December 2002,
                   <http://www.rfc-editor.org/info/rfc3418>.

Top      Up      ToC       Page 67 
   [RFC3433]       Bierman, A., Romascanu, D., and K. Norseth, "Entity
                   Sensor Management Information Base", RFC 3433,
                   December 2002,
                   <http://www.rfc-editor.org/info/rfc3433>.

   [RFC4268]       Chisholm, S. and D. Perkins, "Entity State MIB", RFC
                   4268, November 2005,
                   <http://www.rfc-editor.org/info/rfc4268>.

   [RFC6988]       Quittek, J., Ed., Chandramouli, M., Winter, R.,
                   Dietz, T., and B. Claise, "Requirements for Energy
                   Management", RFC 6988, September 2013,
                   <http://www.rfc-editor.org/info/rfc6988>.

   [RFC7326]       Parello, J., Claise, B., Schoening, B., and J.
                   Quittek, "Energy Management Framework", RFC 7326,
                   September 2014,
                   <http://www.rfc-editor.org/info/rfc7326>.

   [DMTF]          DMTF, "Power State Management Profile", DSP1027,
                   Version 2.0, December 2009,
                   http://www.dmtf.org/sites/default/files/standards
                   /documents/DSP1027_2.0.0.pdf

   [EMAN-AS]       Schoening, B., Chandramouli, M., and B. Nordman,
                   "Energy Management (EMAN) Applicability Statement",
                   Work in Progress, draft-ietf-eman-applicability-
                   statement-08, December 2014.

   [IEC.61850-7-4] International Electrotechnical Commission,
                   "Communication networks and systems for power utility
                   automation  -- Part 7-4: Basic communication
                   structure  -- Compatible logical node classes and
                   data object classes", March 2010.

   [IEC.62053-21]  International Electrotechnical Commission,
                   "Electricity metering equipment (a.c.) -- Particular
                   requirements -- Part 21: Static meters for active
                   energy (classes 1 and 2)", January 2003.

   [IEC.62053-22]  International Electrotechnical Commission,
                   "Electricity metering equipment (a.c.) -- Particular
                   requirements -- Part 22: Static meters for active
                   energy (classes 0,2 S and 0,5 S)", January 2003.

Top      Up      ToC       Page 68 
   [IEEE1621]      "Standard for User Interface Elements in Power
                   Control of Electronic Devices Employed in
                   Office/Consumer Environments", IEEE 1621, December
                   2004.

Acknowledgments

   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.

   The authors would like to thank Juergen Schoenwalder for proposing
   the design of the Textual Convention for PowerStateSet and Ira
   McDonald for his feedback.  Special appreciation to Laurent Guise for
   his review and input on power quality measurements.  Thanks for the
   many comments on the design of the EnergyTable from Minoru Teraoka
   and Hiroto Ogaki.

   Many thanks to Alan Luchuk for the detailed review of the MIB and his
   comments.

   And finally, thanks to the EMAN chairs: Nevil Brownlee and Tom
   Nadeau.

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

Top      Up      ToC       Page 69 
Authors' Addresses

   Mouli Chandramouli
   Cisco Systems, Inc.
   Sarjapur Outer Ring Road
   Bangalore 560103
   India
   Phone: +91 80 4429 2409
   EMail: moulchan@cisco.com


   Benoit Claise
   Cisco Systems, Inc.
   De Kleetlaan 6a b1
   Diegem 1813
   Belgium
   Phone: +32 2 704 5622
   EMail: bclaise@cisco.com


   Brad Schoening
   44 Rivers Edge Drive
   Little Silver, NJ 07739
   United States
   EMail: brad.schoening@verizon.net


   Juergen Quittek
   NEC Europe, Ltd.
   NEC Laboratories Europe
   Network Research Division
   Kurfuersten-Anlage 36
   Heidelberg  69115
   Germany
   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
   Germany
   Phone: +49 6221 4342-128
   EMail: Thomas.Dietz@neclab.eu