Internet Engineering Task Force (IETF) J. Parello
Request for Comments: 7461 B. Claise
Category: Standards Track M. Chandramouli
ISSN: 2070-1721 Cisco Systems, Inc.
March 2015
Internet Engineering Task Force (IETF) J. Parello
Request for Comments: 7461 B. Claise
Category: Standards Track M. Chandramouli
ISSN: 2070-1721 Cisco Systems, Inc.
March 2015
Energy Object Context MIB
能量对象上下文MIB
Abstract
摘要
This document defines a subset of a Management Information Base (MIB) for energy management of devices. The module addresses device identification, context information, and the energy relationships between devices.
本文档定义了用于设备能量管理的管理信息库（MIB）的子集。该模块处理设备标识、上下文信息和设备之间的能量关系。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7461.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7461.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Energy Management Document Overview ........................2
1.2. Conventions Used in This Document ..........................3
2. The Internet-Standard Management Framework ......................3
3. Terminology .....................................................4
4. Architecture Concepts Applied to the MIB Module .................4
4.1. Energy Object Identification ...............................8
4.2. Energy Object Context ......................................9
4.3. Links to Other Identifiers ................................10
4.4. Energy Object Relationships ...............................11
4.5. Energy Object Identity Persistence ........................12
5. MIB Definitions ................................................12
6. Security Considerations ........................................27
7. IANA Considerations ............................................28
8. References .....................................................29
8.1. Normative References ......................................29
8.2. Informative References ....................................30
Acknowledgments ...................................................31
Authors' Addresses ................................................32
1. Introduction ....................................................2
1.1. Energy Management Document Overview ........................2
1.2. Conventions Used in This Document ..........................3
2. The Internet-Standard Management Framework ......................3
3. Terminology .....................................................4
4. Architecture Concepts Applied to the MIB Module .................4
4.1. Energy Object Identification ...............................8
4.2. Energy Object Context ......................................9
4.3. Links to Other Identifiers ................................10
4.4. Energy Object Relationships ...............................11
4.5. Energy Object Identity Persistence ........................12
5. MIB Definitions ................................................12
6. Security Considerations ........................................27
7. IANA Considerations ............................................28
8. References .....................................................29
8.1. Normative References ......................................29
8.2. Informative References ....................................30
Acknowledgments ...................................................31
Authors' Addresses ................................................32
The Energy Management (EMAN) standards provide a specification for Energy Management. This document defines a subset of a Management Information Base (MIB) for use with network management protocols for Energy monitoring of network devices and devices attached to the network and possibly extending to devices in the industrial automation setting with a network interface.
能源管理（EMAN）标准为能源管理提供了规范。本文档定义了管理信息库（MIB）的子集，用于网络管理协议，用于网络设备和连接到网络的设备的能量监控，并可能扩展到具有网络接口的工业自动化设置中的设备。
The focus of the MIB module specified in this document is on the identification of Energy Objects and reporting the context and relationships of Energy Objects as defined in [RFC7326]. The module addresses Energy Object identification, Energy Object context, and Energy Object relationships.
本文件中规定的MIB模块的重点是能源对象的识别和报告[RFC7326]中定义的能源对象的上下文和关系。该模块处理能源对象标识、能源对象上下文和能源对象关系。
This document specifies the Energy Object Context (ENERGY-OBJECT-CONTEXT-MIB) and IANA Energy Relationship (IANA-ENERGY-RELATION-MIB) modules. The Energy Object Context MIB module specifies MIB objects for identification of Energy Objects, and reporting context and relationship of an Energy Object. The IANA Energy Relationship MIB module specifies the first version of the IANA-maintained definitions of relationships between Energy Objects.
本文档指定了能源对象上下文（Energy-Object-Context-MIB）和IANA能源关系（IANA-Energy-RELATION-MIB）模块。能源对象上下文MIB模块指定用于标识能源对象的MIB对象，并报告能源对象的上下文和关系。IANA能源关系MIB模块指定IANA维护的能源对象之间关系定义的第一个版本。
Firstly, to illustrate the importance of energy monitoring in networks and, secondly, to list some of the important areas to be addressed by the Energy Management Framework [RFC7326], several use cases and network scenarios are presented in the EMAN applicability statement document [EMAN-AS]. In addition, for each scenario, the target devices for energy management, and how those devices powered and metered are also presented. To address the network scenarios, requirements for power and energy monitoring for networking devices are specified in [RFC6988]. Based on the requirements in [RFC6988], [RFC7326] presents a solution approach.
首先，为了说明网络中能源监控的重要性，其次，为了列出能源管理框架[RFC7326]要解决的一些重要领域，在EMAN适用性声明文件[EMAN-AS]中介绍了几个用例和网络场景。此外，对于每个场景，还介绍了能源管理的目标设备，以及这些设备的供电和计量方式。为了解决网络场景，在[RFC6988]中规定了网络设备的功率和能量监控要求。根据[RFC6988]中的要求，[RFC7326]提出了一种解决方案。
Accordingly, the scope of the MIB modules in this document is in accordance to the requirements specified in [RFC6988] and the concepts from [RFC7326].
因此，本文件中MIB模块的范围符合[RFC6988]中规定的要求和[RFC7326]中的概念。
This document is based on the Energy Management Framework [RFC7326] and meets the requirements on identification of Energy Objects and their context and relationships as specified in the Energy Management requirements document [RFC6988].
本文件基于能源管理框架[RFC7326]，符合能源管理要求文件[RFC6988]中规定的能源对象及其上下文和关系的识别要求。
A second MIB module meeting the EMAN requirements [RFC6988] the Monitoring and Control MIB for Power and Energy [RFC7460], monitors the Energy Objects for Power States, for the Power and Energy consumption. Power State monitoring includes: retrieving Power States, Power State properties, current Power State, Power State transitions, and Power State statistics. In addition, this MIB module provides the Power Characteristics properties of the Power and Energy, along with optional characteristics.
第二个MIB模块满足EMAN要求[RFC6988]电力和能源监控MIB[RFC7460]，监控能源对象的电力状态、电力和能源消耗。电源状态监视包括：检索电源状态、电源状态属性、当前电源状态、电源状态转换和电源状态统计信息。此外，此MIB模块还提供电源和能量的电源特性以及可选特性。
The applicability statement document [EMAN-AS] provides the list of use cases, describes the common aspects between existing Energy standards and the EMAN standard, and shows how the EMAN framework relates to other frameworks.
适用性声明文件[EMAN-AS]提供了用例列表，描述了现有能源标准和EMAN标准之间的共同点，并说明了EMAN框架与其他框架的关系。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照[RFC2119]中的说明进行解释。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
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 with SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
Please refer to [RFC7326] for the definitions of the following terminology used in this document.
关于本文件中使用的下列术语的定义，请参考[RFC7326]。
Energy Management Energy Management System (EnMS) Energy Monitoring Energy Control electrical equipment non-electrical equipment (mechanical equipment) device component power inlet power outlet energy power demand provide energy receive energy meter (energy meter) battery Power Interface Nameplate Power Power Attributes Power Quality Power State Power State Set
能源管理能源管理系统（EnMS）能源监测能源控制电气设备非电气设备（机械设备）装置部件电源入口电源出口能源需求提供能源接收电能表（电能表）电池电源接口铭牌电源属性电源质量电源状态电源状态集
This section describes the basic concepts specified in the Energy Management Framework [RFC7326], with specific information related to the MIB modules specified in this document.
本节介绍了能源管理框架[RFC7326]中规定的基本概念，以及与本文件中规定的MIB模块相关的具体信息。
The Energy Object Context (ENERGY-OBJECT-CONTEXT-MIB) MIB module in this document specifies MIB objects for the identification of Energy Objects and reporting context and relationship of an Energy Object. The managed objects are contained in two tables: eoTable and eoRelationTable.
本文档中的能量对象上下文（Energy-Object-Context-MIB）MIB模块指定用于标识能量对象和报告能量对象的上下文和关系的MIB对象。托管对象包含在两个表中：eoTable和eoRelationTable。
The first table, eoTable, focuses on the link to the other MIB modules, on identification, and on the context of the Energy Object. The second table, eoRelationTable, specifies the relationships between Energy Objects. This is a simplified representation of the relationship between Energy Objects.
第一个表eoTable主要关注到其他MIB模块的链接、标识和能源对象的上下文。第二个表eoRelationTable指定能量对象之间的关系。这是能量对象之间关系的简化表示。
A "smidump-style" tree presentation of the MIB modules contained in the document is presented. The meaning of the three symbols in is a compressed representation of the object's MAX-ACCESS clause, which may have the following values:
本文介绍了文档中包含的MIB模块的“smidump样式”树表示。中三个符号的含义是对象的MAX-ACCESS子句的压缩表示，其可能具有以下值：
"not-accessible"->"---"
"accessible-for-notify"->"--n"
"read-only"->"r-n"
"read-write"->"rwn"
"not-accessible"->"---"
"accessible-for-notify"->"--n"
"read-only"->"r-n"
"read-write"->"rwn"
+- eoTable(1)
|
+- eoEntry(1) [entPhysicalIndex]
|
+-- r-n PethPsePortIndexOrZero eoEthPortIndex(1)
+-- r-n PethPsePortGroupIndexOrZero eoEthPortGrpIndex(2)
+-- r-n LldpPortNumberOrZero eoLldpPortNumber(3)
+-- rwn MacAddress eoMgmtMacAddress(4)
+-- r-n InetAddressType eoMgmtAddressType(5)
+-- r-n InetAddress eoMgmtAddress(6)
+-- r-n OCTET STRING eoMgmtDNSName(7)
+-- rwn SnmpAdminString eoDomainName(8)
+-- rwn SnmpAdminString eoRoleDescription(9)
+-- rwn EnergyObjectKeywordList eoKeywords(10)
+-- rwn Integer32 eoImportance(11)
+-- r-n INTEGER eoPowerCategory(12)
+-- rwn SnmpAdminString eoAlternateKey(13)
+-- r-n INTEGER eoPowerInterfaceType(14)
+- eoTable(1)
|
+- eoEntry(1) [entPhysicalIndex]
|
+-- r-n PethPsePortIndexOrZero eoEthPortIndex(1)
+-- r-n PethPsePortGroupIndexOrZero eoEthPortGrpIndex(2)
+-- r-n LldpPortNumberOrZero eoLldpPortNumber(3)
+-- rwn MacAddress eoMgmtMacAddress(4)
+-- r-n InetAddressType eoMgmtAddressType(5)
+-- r-n InetAddress eoMgmtAddress(6)
+-- r-n OCTET STRING eoMgmtDNSName(7)
+-- rwn SnmpAdminString eoDomainName(8)
+-- rwn SnmpAdminString eoRoleDescription(9)
+-- rwn EnergyObjectKeywordList eoKeywords(10)
+-- rwn Integer32 eoImportance(11)
+-- r-n INTEGER eoPowerCategory(12)
+-- rwn SnmpAdminString eoAlternateKey(13)
+-- r-n INTEGER eoPowerInterfaceType(14)
+- eoRelationTable(2)
|
+- eoRelationEntry(1) [entPhysicalIndex, eoRelationIndex]
|
+-- --n Integer32 eoRelationIndex(1)
+-- rwn UUIDorZero eoRelationID(2)
+-- rwn IANAEnergyRelationship eoRelationship(3)
+-- rwn RowStatus eoRelationStatus(4)
+-- rwn StorageType eoRelationStorageType(5)
+- eoRelationTable(2)
|
+- eoRelationEntry(1) [entPhysicalIndex, eoRelationIndex]
|
+-- --n Integer32 eoRelationIndex(1)
+-- rwn UUIDorZero eoRelationID(2)
+-- rwn IANAEnergyRelationship eoRelationship(3)
+-- rwn RowStatus eoRelationStatus(4)
+-- rwn StorageType eoRelationStorageType(5)
The following Unified Modeling Language (UML) diagram illustrates the relationship of the MIB objects in the eoTable, eoRelationTable, and ENTITY-MIB. The MIB objects describe the identity, context, and relationship of an Energy Object. The UML diagram, furthermore, contains objects from the ENTITY-MIB [RFC6933].
下面的统一建模语言（UML）图说明了eoTable、eoRelationTable和ENTITY-MIB中MIB对象的关系。MIB对象描述能量对象的标识、上下文和关系。此外，UML图还包含实体-MIB[RFC6933]中的对象。
+--------------------------+
| EO Context Information |
| ------------------------ |
| eoRoleDescription |
| eoKeywords |
| eoImportance |
| eoPowerCategory |
| eoPowerInterfaceType |
| eoDomainName |
+--------------------------+
^
|
+------------------------------+
|--- | EO Identification |
| | ---------------------------- |
| | entPhysicalIndex (*) |
| | entPhysicalName (*) |
| | entPhysicalUUID (*) |
| | entPhysicalClass (*) |
| --------------------------------
| +------------------------------+
|---> | Link to other identifiers |
| |------------------------------|
| | eoEthPortIndex (**) |
| | eoEthPortGrpIndex (**) |
| | eoLldpPortNumber (***) |
| | |
| | eoMgmtMacAddress (optional) |
| | eoMgmtAddressType (optional) |
| | eoMgmtAddress (optional) |
| | eoMgmtDNSName (optional) |
| | eoAlternateKey |
| +------------------------------+
| +------------------------------+
|---> | EO Relationship |
| ---------------------------- |
| eoRelationIndex |
| eoRelationID |
| eoRelationship |
| eoRelationStatus |
| eoRelationStorageType |
+------------------------------+
+--------------------------+
| EO Context Information |
| ------------------------ |
| eoRoleDescription |
| eoKeywords |
| eoImportance |
| eoPowerCategory |
| eoPowerInterfaceType |
| eoDomainName |
+--------------------------+
^
|
+------------------------------+
|--- | EO Identification |
| | ---------------------------- |
| | entPhysicalIndex (*) |
| | entPhysicalName (*) |
| | entPhysicalUUID (*) |
| | entPhysicalClass (*) |
| --------------------------------
| +------------------------------+
|---> | Link to other identifiers |
| |------------------------------|
| | eoEthPortIndex (**) |
| | eoEthPortGrpIndex (**) |
| | eoLldpPortNumber (***) |
| | |
| | eoMgmtMacAddress (optional) |
| | eoMgmtAddressType (optional) |
| | eoMgmtAddress (optional) |
| | eoMgmtDNSName (optional) |
| | eoAlternateKey |
| +------------------------------+
| +------------------------------+
|---> | EO Relationship |
| ---------------------------- |
| eoRelationIndex |
| eoRelationID |
| eoRelationship |
| eoRelationStatus |
| eoRelationStorageType |
+------------------------------+
(*) Compliance with entity4CRCompliance ENTITY-MIB [RFC6933]
(**) Link with the Power over Ethernet MIB [RFC3621]
(***) Link with LLDP MIBs [LLDP-MIB] [LLDP-MED-MIB]
(*) Compliance with entity4CRCompliance ENTITY-MIB [RFC6933]
(**) Link with the Power over Ethernet MIB [RFC3621]
(***) Link with LLDP MIBs [LLDP-MIB] [LLDP-MED-MIB]
Figure 1: MIB Objects Grouping
图1:MIB对象分组
As displayed in Figure 1, the MIB objects can be classified in different logical grouping of MIB objects.
如图1所示，MIB对象可以在不同的MIB对象逻辑分组中进行分类。
1) The Energy Object Identification. See Section 5.1 "Energy Object Identification". Devices and their sub-components are characterized by the power-related attributes of a physical entity present in the ENTITY-MIB [RFC6933].
1) 能量目标识别。参见第5.1节“能源物体识别”。设备及其子组件以实体MIB[RFC6933]中物理实体的功率相关属性为特征。
2) The Context Information. See Section 4.1 "Energy Object Context".
2) 上下文信息。参见第4.1节“能源对象上下文”。
3) The links to other MIB modules. See Section 4.3 "Links to Other Identifiers".
3) 指向其他MIB模块的链接。见第4.3节“与其他标识符的链接”。
4) The Energy Object Relationships specific information. See Section 4.4 "Energy Object Relationships".
4) 能量对象与特定信息之间的关系。参见第4.4节“能源对象关系”。
5) The Energy Object Identity Persistence. See Section 4.5 "Energy Object Identity Persistence".
5) 能量对象标识持久化。参见第4.5节“能源对象标识持久性”。
Refer to the "Identification" section in [RFC7326] for background information about Energy Objects.
有关能量物体的背景信息，请参阅[RFC7326]中的“识别”部分。
Every Energy Object MUST implement the unique index, entPhysicalIndex, entPhysicalName, entPhysicalClass, and entPhysicalUUID from the ENTITY-MIB [RFC6933]. Module Compliance with respect to entity4CRCompliance of ENTITY-MIB MUST be supported, which requires a limited number of objects supported (entPhysicalIndex, entPhysicalName, entPhysicalClass, and entPhysicalUUID). entPhysicalIndex is used as index for the Energy Object in the ENERGY-OBJECT-CONTEXT-MIB module. Every Energy Object MUST have a printable name assigned to it. Energy Objects MUST implement the entPhysicalName object specified in the ENTITY-MIB [RFC6933], which must contain the Energy Object name.
每个Energy对象都必须从ENTITY-MIB[RFC6933]实现唯一索引、entPhysicalIndex、entPhysicalName、entPhysicalClass和entPhysicalUUID。必须支持与ENTITY-MIB的entity4CRCompliance相关的模块遵从性，这要求支持的对象数量有限（entPhysicalIndex、entPhysicalName、entPhysicalClass和entPhysicalUUID）。entPhysicalIndex用作Energy-Object-CONTEXT-MIB模块中能量对象的索引。每个能量对象都必须指定一个可打印的名称。能量对象必须实现ENTITY-MIB[RFC6933]中指定的entPhysicalName对象，该对象必须包含能量对象名称。
For the ENERGY-OBJECT-CONTEXT-MIB compliance, every Energy Object instance MUST implement the entPhysicalUUID from the ENTITY-MIB [RFC6933].
为了符合ENERGY-OBJECT-CONTEXT-MIB，每个ENERGY对象实例都必须从ENTITY-MIB[RFC6933]实现entPhysicalUUID。
As displayed in [RFC4122], the following is an example of the string representation of a Universally Unique Identifier (UUID) as a URN: urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6.
如[RFC4122]所示，以下是通用唯一标识符（UUID）作为URN:URN:UUID:f81d4fae-7dec-11d0-a765-00a0c91e6bf6的字符串表示示例。
For example, to understand the relationship between Energy Object Components and Energy Objects, the ENTITY-MIB physical containment tree [RFC6933] MUST be implemented.
例如，为了理解能源对象组件和能源对象之间的关系，必须实现ENTITY-MIB物理包含树[RFC6933]。
A second example deals with one of the ENTITY-MIB extensions: if the Energy Object temperature is required, the managed objects from the ENTITY-SENSOR-MIB [RFC3433] should be supported.
第二个示例涉及ENTITY-MIB扩展之一：如果需要能量对象温度，则应支持ENTITY-SENSOR-MIB[RFC3433]中的受管对象。
Each Energy Object MUST belong to a single Energy Management Domain or in other words, an Energy Object cannot belong to more than one Energy Management Domain. Refer to the "Context: Domain" section in [RFC7326] for background information. The eoDomainName, which is an element of the eoTable, is a read-write MIB object. The Energy Management Domain should map 1:1 with a metered or sub-metered portion of the network. The Energy Management Domain MUST be configured on the Energy Object. The Energy Object MAY inherit some of the domain parameters (possibly domain name, some of the context information such as role or keywords, importance) from the Energy Object or the Energy Management Domain MAY be configured directly in an Energy Object.
每个能源对象必须属于单个能源管理域，或者换句话说，一个能源对象不能属于多个能源管理域。有关背景信息，请参阅[RFC7326]中的“上下文：域”部分。eoDomainName是eoTable的一个元素，是一个读写MIB对象。能量管理域应与网络的计量或子计量部分1:1映射。必须在能源对象上配置能源管理域。能量对象可以从能量对象继承一些域参数（可能是域名、一些上下文信息，例如角色或关键字、重要性），或者可以直接在能量对象中配置能量管理域。
When an Energy Object acts as a Power Aggregator, the Energy Objects for which Power should be aggregated MUST be members of the same Energy Management Domain, specified by the eoDomainName MIB Object.
当能源对象充当电源聚合器时，应为其聚合电源的能源对象必须是由eoDomainName MIB对象指定的同一能源管理域的成员。
Refer to the "Context: Domain" section in [RFC7326] for background information.
有关背景信息，请参阅[RFC7326]中的“上下文：域”部分。
An Energy Object must provide a value for eoImportance in the range of 1-100 to help differentiate the use or relative value of the device. The importance range is from 1 (least important) to 100 (most important). The default importance value is 1.
能量对象必须提供1-100范围内的EO重要性值，以帮助区分设备的用途或相对值。重要性范围从1（最不重要）到100（最重要）。默认的重要性值为1。
An Energy Object can provide a set of eoKeywords. These keywords are a list of tags that can be used for grouping and summary reporting within or between Energy Management Domains.
能量对象可以提供一组关键字。这些关键字是标签列表，可用于能源管理领域内或之间的分组和汇总报告。
An Energy Object can have Power Interfaces and those interfaces can be classified as Power Inlet, Power Outlet, or both.
能量对象可以有电源接口，这些接口可以分为电源入口、电源出口或两者。
An Energy Object can be classified based on the physical properties of the Energy Object. That Energy Object can be classified as consuming power or supplying power to other devices or that Energy Object can perform both of those functions and finally, an Energy Object can be a passive meter.
可以根据能量物体的物理特性对能量物体进行分类。该能源对象可分为消耗电力或向其他设备供电，或者该能源对象可执行这两种功能，最后，能源对象可为无源电表。
Additionally, an Energy Object can provide an eoRoleDescription string that indicates the purpose the Energy Object serves in the network.
此外，能源对象可以提供eoRoleDescription字符串，该字符串指示能源对象在网络中的用途。
While the entPhysicalIndex is the primary index for all MIB objects in the ENERGY-OBJECT-CONTEXT-MIB module, the Energy Management Systems (EnMS) must be able to make the link with the identifier(s) in other supported MIB modules.
虽然entPhysicalIndex是ENERGY-OBJECT-CONTEXT-MIB模块中所有MIB对象的主要索引，但能源管理系统（EnMS）必须能够与其他受支持的MIB模块中的标识符建立链接。
If the Energy Object is a Power over Ethernet (PoE) port, and if the Power over Ethernet MIB [RFC3621] is supported by the SNMP agent managing the Energy Object, then the Energy Objects eoethPortIndex and eoethPortGrpIndex MUST contain the corresponding values of pethPsePortIndex and pethPsePortGroupIndex [RFC3621].
如果能源对象是以太网供电（PoE）端口，并且管理能源对象的SNMP代理支持以太网供电MIB[RFC3621]，则能源对象eoethPortIndex和eoethPortGrpIndex必须包含相应的pethPsePortIndex和pethPsePortGroupIndex[RFC3621]值。
If the LLDP-MED MIB [LLDP-MIB] is supported by the Energy Object SNMP agent, then the Energy Object eoLldpPortNumber MUST contain the corresponding lldpLocPortNum from the LLDP MIB.
如果能源对象SNMP代理程序支持LLDP-MED MIB[LLDP-MIB]，则能源对象端口号必须包含LLDP MIB中相应的lldpLocPortNum。
The intent behind the links to the other MIB module identifier(s) is to correlate the instances in the different MIB modules. This will allow the ENERGY-OBJECT-CONTEXT-MIB module to reference other MIB modules in cases where the Power over Ethernet and the LLDP MIB modules are supported by the SNMP agent. Some use cases may not implement either of these two MIB modules for the Energy Objects. However, in situations where either of these two MIB modules are implemented, the EnMS must be able to correlate the instances in the different MIB modules.
链接到其他MIB模块标识符的目的是关联不同MIB模块中的实例。这将允许ENERGY-OBJECT-CONTEXT-MIB模块在SNMP代理支持以太网供电和LLDP MIB模块的情况下参考其他MIB模块。某些用例可能无法为能量对象实现这两个MIB模块中的任何一个。但是，在实现这两个MIB模块中的任何一个的情况下，EnMS必须能够关联不同MIB模块中的实例。
The eoAlternateKey object specifies an alternate key string that can be used to identify the Energy Object. Since an EnMS may need to correlate objects across management systems, this alternate key is provided to facilitate such a link. This optional value is intended as a foreign key or alternate identifier for a manufacturer or EnMS to use to correlate the unique Energy Object Id in other systems or namespaces. If an alternate key is not available or is not applicable, then the value is the zero-length string.
eoAlternateKey对象指定可用于标识能量对象的备用密钥字符串。由于EnMS可能需要跨管理系统关联对象，因此提供此备用密钥以促进此类链接。此可选值用作外键或备用标识符，供制造商或ENM用于关联其他系统或名称空间中的唯一能源对象Id。如果备用键不可用或不适用，则该值为零长度字符串。
An Energy Object can have additional MIB objects that can be used for easier identification by the EnMS. The optional objects eoMgmtMacAddress, eoMgmtAddressType, and eoMgmtDNSName can be used to help identify the relationship between the Energy Objects and other NMS objects. These objects can be used as an alternate key to help link the Energy Object with other keyed information that may be stored within the EnMS(s). For the optional objects that may not be included in some vendor implementations, the expected behavior when those objects are polled is a response noSuchInstance.
能源对象可以具有额外的MIB对象，这些MIB对象可用于更容易被EnMS识别。可选对象eoMgmtMacAddress、eoMgmtAddressType和eoMgmtDNSName可用于帮助确定能源对象与其他NMS对象之间的关系。这些对象可用作备用键，以帮助将能量对象与可能存储在EnMS中的其他键控信息链接。对于某些供应商实现中可能未包含的可选对象，轮询这些对象时的预期行为是响应noSuchInstance。
Refer to the "Relationships" section in [RFC7326] for the definition and background information. In order to link two Energy Objects, a separate table (eoRelationTable) has been introduced in this MIB module.
有关定义和背景信息，请参阅[RFC7326]中的“关系”部分。为了链接两个能源对象，在该MIB模块中引入了一个单独的表（eoRelationTable）。
Each Energy Object can have one or more Energy Object relationships with other Energy Objects. The relationship between Energy Objects is specified in eoRelationTable. The relationship between the Energy Objects is specified with the entPhysicalIndex of the Energy Object and the UUID of the remote Energy Object. The UUID MUST comply to the RFC 4122 specifications. It is important to note that it is possible that an Energy Object may not have an Energy Object relationship with other Energy Objects.
每个能量对象可以与其他能量对象具有一个或多个能量对象关系。能量对象之间的关系在eoRelationTable中指定。能源对象之间的关系由能源对象的entPhysicalIndex和远程能源对象的UUID指定。UUID必须符合RFC 4122规范。重要的是要注意，一个能量对象可能与其他能量对象没有能量对象关系。
The following relationships between Energy Objects have been considered in the eoRelationTable.
eoRelationTable中考虑了能量对象之间的以下关系。
Metering Relationship -> meteredBy / metering
Metering Relationship -> meteredBy / metering
Power Source Relationship -> poweredBy / powering
Power Source Relationship -> poweredBy / powering
Aggregation Relationship -> aggregatedBy / aggregating
Aggregation Relationship -> aggregatedBy / aggregating
Energy Object B has a "meteredBy" relationship with Energy Object A, if the energy consumption of Energy Object B is measured by Energy Object A. Equivalently, it is possible to indicate that Energy Object A has a "metering" relationship with Energy Object B.
如果能源对象B的能耗由能源对象a测量，则能源对象B与能源对象a具有“计量”关系。等效地，可以指示能源对象a与能源对象B具有“计量”关系。
Energy Object B has a "poweredBy" relationship with Energy Object A, if the power source of Energy Object B is Energy Object A. Equivalently, it is possible to indicate that Energy Object A has a "powering" relationship with Energy Object B.
如果能量对象B的电源是能量对象a，则能量对象B与能量对象a具有“通电”关系。等效地，可以指示能量对象a与能量对象B具有“通电”关系。
Energy Object B has "aggregatedBy" relationship with Energy Object A, if Energy Object A is an aggregation point for energy usage of Energy Object B. Equivalently, it is possible to indicate that Energy Object A has "aggregating" relationship with Energy Object B.
如果能量对象A是能量对象B能量使用的聚合点，则能量对象B与能量对象A具有“聚合”关系。等效地，可以指示能量对象A与能量对象B具有“聚合”关系。
The IANA-ENERGY-RELATION-MIB module in Section 5 below specifies the first version of the IANA-maintained definitions of relationships. This way, for Energy Relationships, new textual conventions can be specified, without updating the primary Energy Object Context MIB module.
下面第5节中的IANA-ENERGY-RELATION-MIB模块指定了IANA维护的关系定义的第一个版本。这样，对于能量关系，可以指定新的文本约定，而无需更新主能量对象上下文MIB模块。
In some situations, the Energy Object identity information should be persistent even after a device reload. For example, in a static setup where a switch monitors a series of connected PoE phones, there is a clear benefit for the EnMS if the Energy Object Identification and all associated information persist, as it saves a network discovery. However, in other situations, such as a wireless access point monitoring the mobile user PCs, there is not much advantage to persist the Energy Object Information. The identity information of an Energy Object should be persisted and there is value in the writable MIB objects persisted.
在某些情况下，即使在设备重新加载后，能量对象标识信息也应保持不变。例如，在交换机监控一系列已连接PoE电话的静态设置中，如果能量对象标识和所有相关信息持续存在，则EnMS将明显受益，因为它可以节省网络发现。然而，在其他情况下，例如监测移动用户pc的无线接入点，保持能量对象信息没有多大优势。能源对象的标识信息应保持不变，且可写MIB对象中存在值保持不变。
-- ************************************************************
--
--
-- This MIB is used for describing the identity and the
-- context information of Energy Objects in network
--
--
-- *************************************************************
-- ************************************************************
--
--
-- This MIB is used for describing the identity and the
-- context information of Energy Objects in network
--
--
-- *************************************************************
ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN
ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, Integer32 FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION, MacAddress, TruthValue, RowStatus, StorageType FROM SNMPv2-TC -- RFC 2579 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC 4001 entPhysicalIndex FROM ENTITY-MIB -- RFC 6933 UUIDorZero FROM UUID-TC-MIB -- RFC 6933 IANAEnergyRelationship FROM IANA-ENERGY-RELATION-MIB;
从SNMPv2 SMI导入MODULE-IDENTITY、OBJECT-TYPE、mib-2、Integer32--从SNMPv2 TC导入RFC 2578文本约定、MacAddress、TruthValue、RowStatus、StorageType--从SNMPv2 CONF导入RFC 2579 MODULE-COMPLIANCE、OBJECT-GROUP--从SNMP-FRAMEWORK-mib导入RFC 2580 SNMPadmin--从RFC 3411 InetAddressType，INET-ADDRESS-MIB中的InetAddress——ENTITY-MIB中的RFC 4001 entPhysicalIndex——UUID-TC-MIB中的RFC 6933 UUIDorZero——IANA-ENERGY-RELATION-MIB中的RFC 6933 IANAenergy关系；
energyObjectContextMIB MODULE-IDENTITY LAST-UPDATED "201502090000Z"
energyObjectContextMIB模块-标识上次更新“201502090000Z”
ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO
"WG Charter:
http://datatracker.ietf.org/wg/eman/charter/
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
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
Editors: John Parello Cisco Systems, Inc. 3550 Cisco Way San Jose, California 95134 United States Phone: +1 408 525 2339 Email: jparello@cisco.com
编辑：John Parello Cisco Systems，Inc.加利福尼亚州圣何塞市思科路3550号95134美国电话：+1 408 525 2339电子邮件：jparello@cisco.com
Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 Degem 1831 Belgium Phone: +32 2 704 5622 Email: bclaise@cisco.com
Benoit Claise Cisco Systems，Inc.De Kleetlaan 6a b1 Degem 1831比利时电话：+32 2 704 5622电子邮件：bclaise@cisco.com
Mouli Chandramouli Cisco Systems, Inc. Sarjapur Outer Ring Road Bangalore 560103 India Phone: +91 80 4429 2409 Email: moulchan@cisco.com"
Mouli Chandramouli Cisco Systems，Inc.Sarjapur外环路班加罗尔560103印度电话：+91 80 4429 2409电子邮件：moulchan@cisco.com"
DESCRIPTION "Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
说明“版权所有（c）2015 IETF信托基金和被认定为代码作者的人士。保留所有权利。
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).
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info).
This MIB is used for describing the identity and the context information of Energy Objects." REVISION "201502090000Z" DESCRIPTION "Initial version, published as RFC 7461."
此MIB用于描述能源对象的身份和上下文信息。“修订版”201502090000Z“说明”初始版本，发布为RFC 7461
::= { mib-2 231 }
::= { mib-2 231 }
energyObjectContextMIBNotifs OBJECT IDENTIFIER
::= { energyObjectContextMIB 0 }
energyObjectContextMIBNotifs OBJECT IDENTIFIER
::= { energyObjectContextMIB 0 }
energyObjectContextMIBObjects OBJECT IDENTIFIER
::= { energyObjectContextMIB 1 }
energyObjectContextMIBObjects OBJECT IDENTIFIER
::= { energyObjectContextMIB 1 }
energyObjectContextMIBConform OBJECT IDENTIFIER
::= { energyObjectContextMIB 2 }
energyObjectContextMIBConform OBJECT IDENTIFIER
::= { energyObjectContextMIB 2 }
-- Textual Conventions
--文本约定
PethPsePortIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
pethPsePortIndex convention, which defines a greater-
than-zero value used to identify a power Ethernet Power
Sourcing Equipment (PSE) port.
PethPsePortIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
pethPsePortIndex convention, which defines a greater-
than-zero value used to identify a power Ethernet Power
Sourcing Equipment (PSE) port.
This extension permits the additional value of zero. The semantics of the value zero are object-specific and must, therefore, be defined as part of the description of any object that uses this syntax. Examples of the usage of this extension are situations where none or all physical entities need to be referenced." SYNTAX Integer32 (0..2147483647)
此扩展允许附加值为零。值zero的语义是特定于对象的，因此必须定义为使用此语法的任何对象描述的一部分。使用此扩展的示例包括不需要引用任何或所有物理实体的情况。“语法整数32（0..2147483647）
PethPsePortGroupIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
pethPsePortGroupIndex convention from the Power Over
Ethernet MIB in RFC 3621, which defines a greater-than-zero
value used to identify the group containing the port to which
a power Ethernet PSE is connected. This extension
permits the additional value of zero. The semantics of
the value zero are object-specific and must, therefore,
PethPsePortGroupIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
pethPsePortGroupIndex convention from the Power Over
Ethernet MIB in RFC 3621, which defines a greater-than-zero
value used to identify the group containing the port to which
a power Ethernet PSE is connected. This extension
permits the additional value of zero. The semantics of
the value zero are object-specific and must, therefore,
be defined as part of the description of any object that uses this syntax. Examples of the usage of this extension are situations where none or all physical entities need to be referenced." SYNTAX Integer32 (0..2147483647)
被定义为使用此语法的任何对象的描述的一部分。使用此扩展的示例包括不需要引用任何或所有物理实体的情况。“语法整数32（0..2147483647）
LldpPortNumberOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
LldpPortNumber convention specified in the LLDP MIB,
which defines a greater than zero value used to uniquely
identify each port contained in the chassis (that is
known to the LLDP agent) by a port number. This
extension permits the additional value of zero. The
semantics of the value zero are object-specific and must,
therefore, be defined as part of the description of any
object that uses this syntax. Examples of the usage of
this extension are situations where none or all physical
entities need to be referenced."
SYNTAX Integer32(0..4096)
LldpPortNumberOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
LldpPortNumber convention specified in the LLDP MIB,
which defines a greater than zero value used to uniquely
identify each port contained in the chassis (that is
known to the LLDP agent) by a port number. This
extension permits the additional value of zero. The
semantics of the value zero are object-specific and must,
therefore, be defined as part of the description of any
object that uses this syntax. Examples of the usage of
this extension are situations where none or all physical
entities need to be referenced."
SYNTAX Integer32(0..4096)
EnergyObjectKeywordList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A list of keywords that can be used to group Energy
Objects for reporting or searching. If multiple keywords
are present, then this string will contain all the
keywords separated by the ',' character. All alphanumeric
characters and symbols (other than a comma), such as #,
(, $, !, and &, are allowed. White spaces before and
after the commas are ignored, as well as within a keyword
itself.
EnergyObjectKeywordList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A list of keywords that can be used to group Energy
Objects for reporting or searching. If multiple keywords
are present, then this string will contain all the
keywords separated by the ',' character. All alphanumeric
characters and symbols (other than a comma), such as #,
(, $, !, and &, are allowed. White spaces before and
after the commas are ignored, as well as within a keyword
itself.
For example, if an Energy Object were to be tagged with the keyword values 'hospitality' and 'guest', then the keyword list will be 'hospitality,guest'." SYNTAX OCTET STRING (SIZE (0..2048))
例如，如果要使用关键字值“hospitality”和“guest”标记能源对象，则关键字列表将为“hospitality，guest”。“语法八位字符串（大小（0..2048））
-- Objects
--物体
eoTable OBJECT-TYPE SYNTAX SEQUENCE OF EoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists Energy Objects."
eoTable对象类型EoEntry MAX-ACCESS的语法序列不可访问状态当前描述“此表列出了能源对象。”
::= { energyObjectContextMIBObjects 1 }
::= { energyObjectContextMIBObjects 1 }
eoEntry OBJECT-TYPE SYNTAX EoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry describes the attributes of an Energy Object. Whenever a new Energy Object is added or an existing Energy Object is deleted, a row in the eoTable is added or deleted."
eoEntry对象类型语法eoEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“条目描述能源对象的属性。每当添加新能源对象或删除现有能源对象时，都会添加或删除eoTable中的一行。”
INDEX {entPhysicalIndex }
::= { eoTable 1 }
INDEX {entPhysicalIndex }
::= { eoTable 1 }
EoEntry ::= SEQUENCE {
eoEthPortIndex PethPsePortIndexOrZero,
eoEthPortGrpIndex PethPsePortGroupIndexOrZero,
eoLldpPortNumber LldpPortNumberOrZero,
eoMgmtMacAddress MacAddress,
eoMgmtAddressType InetAddressType,
eoMgmtAddress InetAddress,
eoMgmtDNSName OCTET STRING,
eoDomainName SnmpAdminString,
eoRoleDescription SnmpAdminString,
eoKeywords EnergyObjectKeywordList,
eoImportance Integer32,
eoPowerCategory INTEGER,
eoAlternateKey SnmpAdminString,
eoPowerInterfaceType INTEGER
}
EoEntry ::= SEQUENCE {
eoEthPortIndex PethPsePortIndexOrZero,
eoEthPortGrpIndex PethPsePortGroupIndexOrZero,
eoLldpPortNumber LldpPortNumberOrZero,
eoMgmtMacAddress MacAddress,
eoMgmtAddressType InetAddressType,
eoMgmtAddress InetAddress,
eoMgmtDNSName OCTET STRING,
eoDomainName SnmpAdminString,
eoRoleDescription SnmpAdminString,
eoKeywords EnergyObjectKeywordList,
eoImportance Integer32,
eoPowerCategory INTEGER,
eoAlternateKey SnmpAdminString,
eoPowerInterfaceType INTEGER
}
eoEthPortIndex OBJECT-TYPE SYNTAX PethPsePortIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the power Ethernet port to which a Power over Ethernet device is connected. If the Power over Ethernet MIB in RFC 3621 is supported by the SNMP agent managing the Energy Object, then the Energy Object eoethPortIndex MUST contain the corresponding value of pethPsePortIndex. If such a power Ethernet port cannot be specified or is not known, then the object is zero." REFERENCE "RFC 3621: Power Ethernet MIB" DEFVAL { 0 }
eoEthPortIndex对象类型语法PethPsePortIndexOrZero MAX-ACCESS只读状态当前说明“此变量唯一标识通过以太网供电设备连接到的电力以太网端口。如果管理能源对象的SNMP代理支持RFC 3621中的以太网供电MIB，则能源对象eoethPortIndex必须包含相应的pethPsePortIndex值。如果无法指定或不知道这样的电力以太网端口，则对象为零。“REFERENCE”RFC 3621:power Ethernet MIB“deffal{0}
::= { eoEntry 1 }
::= { eoEntry 1 }
eoEthPortGrpIndex OBJECT-TYPE
SYNTAX PethPsePortGroupIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the group containing
the port to which a power over Ethernet device PSE is
connected (RFC 3621). If the Power over Ethernet MIB (RFC
3621) is supported by the SNMP agent managing the Energy
Object, then the Energy Object eoEthPortGrpIndex MUST
contain the corresponding value of eoethPortGrpIndex. If
such a power Ethernet port cannot be specified or is not
known, then the object is zero."
REFERENCE
"RFC 3621: Power Ethernet MIB"
DEFVAL { 0 }
::= { eoEntry 2 }
eoEthPortGrpIndex OBJECT-TYPE
SYNTAX PethPsePortGroupIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the group containing
the port to which a power over Ethernet device PSE is
connected (RFC 3621). If the Power over Ethernet MIB (RFC
3621) is supported by the SNMP agent managing the Energy
Object, then the Energy Object eoEthPortGrpIndex MUST
contain the corresponding value of eoethPortGrpIndex. If
such a power Ethernet port cannot be specified or is not
known, then the object is zero."
REFERENCE
"RFC 3621: Power Ethernet MIB"
DEFVAL { 0 }
::= { eoEntry 2 }
eoLldpPortNumber OBJECT-TYPE SYNTAX LldpPortNumberOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the port component (contained in the local chassis with the LLDP agent) as defined by the lldpLocPortNum in the LLDP-MIB and LLDP-MED-MIB. If the LLDP-MIB is supported by the SNMP agent managing the Energy Object, then the Energy Object eoLldpPortNumber MUST contain the corresponding value of lldpLocPortNum from the LLDP-MIB. If such a port number cannot be specified or is not known, then the object is zero." REFERENCE "LLDP MIB, IEEE 802.1AB-2005; LLDP-MED-MIB, ANSI/TIA-1057" DEFVAL { 0 }
eoLldpPortNumber对象类型语法LLDPPortNumberZero MAX-ACCESS只读状态当前描述“此变量唯一标识端口组件（包含在带有LLDP代理的本地机箱中）由LLDP-MIB和LLDP-MED-MIB中的lldpLocPortNum定义。如果管理能源对象的SNMP代理支持LLDP-MIB，则能源对象EOLLDPPORTNERM必须包含LLDP-MIB中lldpLocPortNum的相应值。如果无法指定或不知道此类端口号，则对象为零。”参考“LLDP MIB，IEEE 802.1AB-2005；LLDP-MED-MIB，ANSI/TIA-1057”定义{0}
::= { eoEntry 3 }
::= { eoEntry 3 }
eoMgmtMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies a Media Access Control (MAC) address
of the Energy Object."
::= { eoEntry 4 }
eoMgmtMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies a Media Access Control (MAC) address
of the Energy Object."
::= { eoEntry 4 }
eoMgmtAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the eoMgmtAddress type, i.e., an
IPv4 or IPv6 address. This object MUST be
populated when eoMgmtAddress is populated."
::= { eoEntry 5 }
eoMgmtAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the eoMgmtAddress type, i.e., an
IPv4 or IPv6 address. This object MUST be
populated when eoMgmtAddress is populated."
::= { eoEntry 5 }
eoMgmtAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the management address as an IPv4
address or IPv6 address of Energy Object. The IP address
type, i.e. IPv4 or IPv6, is determined by the
eoMgmtAddressType value. This object can be used as an
alternate key to help link the Energy Object with other
keyed information that may be stored within the EnMS(s)."
::= { eoEntry 6 }
eoMgmtAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the management address as an IPv4
address or IPv6 address of Energy Object. The IP address
type, i.e. IPv4 or IPv6, is determined by the
eoMgmtAddressType value. This object can be used as an
alternate key to help link the Energy Object with other
keyed information that may be stored within the EnMS(s)."
::= { eoEntry 6 }
eoMgmtDNSName OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies a DNS name of the eoMgmtAddress.
This object can be used as an alternate key to help link
the Energy Object with other keyed information that may
be stored within the EnMS(s). A DNS Name must always be a
fully qualified name. This MIB uses the same encoding as
the DNS protocol."
REFERENCE
"RFC 1034: Domain names - concepts and facilities,
Section 3.1."
::= { eoEntry 7 }
eoMgmtDNSName OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies a DNS name of the eoMgmtAddress.
This object can be used as an alternate key to help link
the Energy Object with other keyed information that may
be stored within the EnMS(s). A DNS Name must always be a
fully qualified name. This MIB uses the same encoding as
the DNS protocol."
REFERENCE
"RFC 1034: Domain names - concepts and facilities,
Section 3.1."
::= { eoEntry 7 }
eoDomainName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the name of an Energy Management Domain for the Energy Object. By default, this object should be an empty string. The value of eoDomainName must remain constant at least from one re-initialization of
eoDomainName对象类型语法SNMPAdministring MAX-ACCESS读写状态当前描述“此对象指定能源对象的能源管理域的名称。默认情况下，此对象应为空字符串。eoDomainName的值必须至少从一次重新初始化
the entity local management system to the next re-
initialization."
::= { eoEntry 8 }
the entity local management system to the next re-
initialization."
::= { eoEntry 8 }
eoRoleDescription OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies an administratively assigned name to indicate the purpose an Energy Object serves in the network.
eoRoleDescription对象类型语法SNMPAdministring MAX-ACCESS读写状态当前描述“此对象指定管理分配的名称，以指示能源对象在网络中的用途。
For example, we can have a phone deployed to a lobby with eoRoleDescription as 'Lobby phone'.
例如，我们可以将一部电话部署到大厅，其EOROLEDE描述为“大厅电话”。
This object specifies that the value is the zero-length
string value if no role description is configured.
The value of eoRoleDescription must remain constant at
least from one re-initialization of the entity local
management system to the next re-initialization."
::= { eoEntry 9 }
This object specifies that the value is the zero-length
string value if no role description is configured.
The value of eoRoleDescription must remain constant at
least from one re-initialization of the entity local
management system to the next re-initialization."
::= { eoEntry 9 }
eoKeywords OBJECT-TYPE SYNTAX EnergyObjectKeywordList MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies a list of keywords that can be used to group Energy Objects for reporting or searching. The value is the zero-length string if no keywords have been configured. If multiple keywords are present, then this string will contain all the keywords separated by the ',' character. For example, if an Energy Object were to be tagged with the keyword values 'hospitality' and 'guest', then the keyword list will be 'hospitality,guest'.
eoKeywords对象类型语法EnergyObjectKeywordList最大访问读写状态当前说明“此对象指定可用于对能源对象进行分组以进行报告或搜索的关键字列表。如果未配置关键字，则该值为零长度字符串。如果存在多个关键字，则此字符串将包含由“，”字符分隔的所有关键字。例如，如果要使用关键字值“hospitality”和“guest”标记能源对象，则关键字列表将为“hospitality，guest”。
If write access is implemented and a value is written
into the instance, the agent must retain the supplied
value in the eoKeywords instance associated with
the same physical entity for as long as that entity
remains instantiated. This includes instantiations
across all re-initializations/reboots of the local
management agent."
::= { eoEntry 10 }
If write access is implemented and a value is written
into the instance, the agent must retain the supplied
value in the eoKeywords instance associated with
the same physical entity for as long as that entity
remains instantiated. This includes instantiations
across all re-initializations/reboots of the local
management agent."
::= { eoEntry 10 }
eoImportance OBJECT-TYPE
对象类型
SYNTAX Integer32 (1..100) MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies a ranking of how important the Energy Object is (on a scale of 1 to 100) compared with other Energy Objects in the same Energy Management Domain. The ranking should provide a business or operational context for the Energy Object as compared to other similar Energy Objects. This ranking could be used as input for policy-based network management.
SYNTAX Integer32（1..100）MAX-ACCESS读写状态当前描述“此对象指定能源对象重要性的排名（以1到100的比例）与同一能源管理领域中的其他能源对象进行比较。与其他类似能源对象相比，排名应为能源对象提供业务或运营背景。此排名可作为基于策略的网络管理的输入。
Although network managers must establish their own ranking, the following is a broad recommendation:
尽管网络经理必须建立自己的排名，但以下是一个广泛的建议：
90 to 100 Emergency response 80 to 89 Executive or business critical 70 to 79 General or average 60 to 69 Staff or support 40 to 59 Public or guest 1 to 39 Decorative or hospitality
90至100紧急响应80至89执行或关键业务70至79一般或平均60至69名员工或支持40至59名公众或客人1至39名装饰或招待
The value of eoImportance must remain constant at least
from one re-initialization of the Energy Object local
management system to the next re-initialization."
DEFVAL { 1 }
::= { eoEntry 11 }
The value of eoImportance must remain constant at least
from one re-initialization of the Energy Object local
management system to the next re-initialization."
DEFVAL { 1 }
::= { eoEntry 11 }
eoPowerCategory OBJECT-TYPE
SYNTAX INTEGER {
consumer(0),
producer(1),
meter(2),
distributor(3),
store(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the Energy Object category, which
indicates the expected behavior or physical property of
the Energy Object, based on its design. An Energy Object
can be a consumer(0), producer(1), meter(2),
distributor(3), or store(4).
eoPowerCategory OBJECT-TYPE
SYNTAX INTEGER {
consumer(0),
producer(1),
meter(2),
distributor(3),
store(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the Energy Object category, which
indicates the expected behavior or physical property of
the Energy Object, based on its design. An Energy Object
can be a consumer(0), producer(1), meter(2),
distributor(3), or store(4).
In some cases, a meter is required to measure the power consumption. In such a case, this meter Energy Object category is meter(2). If a device is distributing
在某些情况下，需要一个仪表来测量功耗。在这种情况下，该仪表能量对象类别为仪表（2）。如果设备正在分发
electric Energy, the category of the Energy Object is
distributor (3). If a device is storing electric Energy,
the category of the device can be store (4)."
::= { eoEntry 12 }
electric Energy, the category of the Energy Object is
distributor (3). If a device is storing electric Energy,
the category of the device can be store (4)."
::= { eoEntry 12 }
eoAlternateKey OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The eoAlternateKey object specifies an alternate key
string that can be used to identify the Energy Object.
Since Energy Management Systems (EnMS) and Network
Management Systems (NMSs) may need to correlate objects
across management systems, this alternate key is provided
to provide such a link. This optional value is intended
as a foreign key or alternate identifier for a
manufacturer or EnMS/NMS to use to correlate the unique
Energy Object Id in other systems or namespaces. If an
alternate key is not available or is not applicable, then
the value is the zero-length string.
The value of eoAlternateKey must remain constant at
least from one re-initialization of the entity local
management system to the next re-initialization."
::= { eoEntry 13 }
eoAlternateKey OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The eoAlternateKey object specifies an alternate key
string that can be used to identify the Energy Object.
Since Energy Management Systems (EnMS) and Network
Management Systems (NMSs) may need to correlate objects
across management systems, this alternate key is provided
to provide such a link. This optional value is intended
as a foreign key or alternate identifier for a
manufacturer or EnMS/NMS to use to correlate the unique
Energy Object Id in other systems or namespaces. If an
alternate key is not available or is not applicable, then
the value is the zero-length string.
The value of eoAlternateKey must remain constant at
least from one re-initialization of the entity local
management system to the next re-initialization."
::= { eoEntry 13 }
eoPowerInterfaceType OBJECT-TYPE
SYNTAX INTEGER {
inlet(0),
outlet(1),
both(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the Power Interface for an Energy
Object. A Power Interface is an interface at which an
Energy Object is connected to a power transmission
medium, at which it can in turn receive power, provide
power, or both. A Power Interface type can be an inlet(0),
an outlet(1), or both(2), respectively."
::= { eoEntry 14 }
eoPowerInterfaceType OBJECT-TYPE
SYNTAX INTEGER {
inlet(0),
outlet(1),
both(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the Power Interface for an Energy
Object. A Power Interface is an interface at which an
Energy Object is connected to a power transmission
medium, at which it can in turn receive power, provide
power, or both. A Power Interface type can be an inlet(0),
an outlet(1), or both(2), respectively."
::= { eoEntry 14 }
eoRelationTable OBJECT-TYPE SYNTAX SEQUENCE OF EoRelationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
EoRelationEntry MAX-ACCESS的eoRelationTable对象类型语法序列不可访问状态当前描述
"This table describes the relationships between Energy
Objects."
::= { energyObjectContextMIBObjects 2 }
"This table describes the relationships between Energy
Objects."
::= { energyObjectContextMIBObjects 2 }
eoRelationEntry OBJECT-TYPE
SYNTAX EoRelationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table specifies the Energy relationship
between Energy objects. Energy relations between two
Energy objects are defined in RFC 7326."
REFERENCE
" RFC 7326: Energy Management Framework"
INDEX { entPhysicalIndex, eoRelationIndex }
::= { eoRelationTable 1 }
eoRelationEntry OBJECT-TYPE
SYNTAX EoRelationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table specifies the Energy relationship
between Energy objects. Energy relations between two
Energy objects are defined in RFC 7326."
REFERENCE
" RFC 7326: Energy Management Framework"
INDEX { entPhysicalIndex, eoRelationIndex }
::= { eoRelationTable 1 }
EoRelationEntry ::= SEQUENCE {
eoRelationIndex Integer32,
eoRelationID UUIDorZero,
eoRelationship IANAEnergyRelationship,
eoRelationStatus RowStatus,
eoRelationStorageType StorageType
}
EoRelationEntry ::= SEQUENCE {
eoRelationIndex Integer32,
eoRelationID UUIDorZero,
eoRelationship IANAEnergyRelationship,
eoRelationStatus RowStatus,
eoRelationStorageType StorageType
}
eoRelationIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary index to identify the Energy
Object related to another Energy Object."
::= { eoRelationEntry 1 }
eoRelationIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary index to identify the Energy
Object related to another Energy Object."
::= { eoRelationEntry 1 }
eoRelationID OBJECT-TYPE SYNTAX UUIDorZero MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the Universally Unique Identifier (UUID) of the peer (other) Energy Object. The UUID must comply with the specifications of UUID in UUID-TC-MIB.
eoRelationID对象类型语法UUIDorZero MAX-ACCESS read create STATUS current DESCRIPTION“此对象指定对等（其他）能源对象的通用唯一标识符（UUID）。UUID必须符合UUID-TC-MIB中的UUID规范。
If the UUID of the Energy Object is unknown or nonexistent, the eoRelationID will be set to a zero-length string instead. It is preferable that the value of entPhysicalUUID from ENTITY-MIB is used for values for this object."
如果能量对象的UUID未知或不存在，则eoRelationID将改为零长度字符串。最好将ENTITY-MIB中的entPhysicalUUID值用于此对象的值。”
REFERENCE
"RFC 6933: Entity MIB (Version 4)"
::= { eoRelationEntry 2 }
REFERENCE
"RFC 6933: Entity MIB (Version 4)"
::= { eoRelationEntry 2 }
eoRelationship OBJECT-TYPE
SYNTAX IANAEnergyRelationship
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object describes the relations between Energy
Objects. For each Energy Object, the relations between
the other Energy Objects are specified using the bitmap."
::= { eoRelationEntry 3 }
eoRelationship OBJECT-TYPE
SYNTAX IANAEnergyRelationship
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object describes the relations between Energy
Objects. For each Energy Object, the relations between
the other Energy Objects are specified using the bitmap."
::= { eoRelationEntry 3 }
eoRelationStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status controls and reflects the creation and activation status of a row in this table to specify energy relationship between Energy Objects.
eoRelationStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“状态控制并反映此表中行的创建和激活状态，以指定能量对象之间的能量关系。
An entry status may not be active(1) unless all objects in the entry have the appropriate values.
除非条目中的所有对象都具有适当的值，否则条目状态可能不会处于活动状态（1）。
No attempt to modify a row columnar object instance value in the eoRelationTable should be issued while the value of eoRelationStatus is active(1). The data can be destroyed by setting up the eoRelationStatus to destroy(2)."
当eoRelationStatus的值处于活动状态（1）时，不应尝试修改eoRelationTable中的行-列对象实例值。可以通过将eoRelationStatus设置为destroy（2）来销毁数据。”
::= { eoRelationEntry 4 }
::= { eoRelationEntry 4 }
eoRelationStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { nonVolatile }
::= {eoRelationEntry 5 }
eoRelationStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { nonVolatile }
::= {eoRelationEntry 5 }
-- Conformance
--一致性
energyObjectContextMIBCompliances OBJECT IDENTIFIER
::= { energyObjectContextMIBConform 1 }
energyObjectContextMIBCompliances OBJECT IDENTIFIER
::= { energyObjectContextMIBConform 1 }
energyObjectContextMIBGroups OBJECT IDENTIFIER
energyObjectContextMIBGroups对象标识符
::= { energyObjectContextMIBConform 2 }
::= { energyObjectContextMIBConform 2 }
energyObjectContextMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented with support for read-write, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB. Module Compliance of ENTITY-MIB with respect to entity4CRCompliance MUST be supported."
energyObjectContextMIBFullCompliance模块-符合性状态当前说明“当此MIB在支持读写的情况下实现时，这样的实现可以声称完全符合要求。然后可以使用此MIB监控和配置此类设备。必须支持ENTITY-MIB在entity4CRCompliance方面的模块合规性。”
MODULE -- this module
MANDATORY-GROUPS {
energyObjectContextMIBTableGroup,
energyObjectRelationTableGroup
}
MODULE -- this module
MANDATORY-GROUPS {
energyObjectContextMIBTableGroup,
energyObjectRelationTableGroup
}
GROUP energyObjectOptionalMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to
implement."
::= { energyObjectContextMIBCompliances 1 }
GROUP energyObjectOptionalMIBTableGroup
DESCRIPTION
"A compliant implementation does not have to
implement."
::= { energyObjectContextMIBCompliances 1 }
energyObjectContextMIBReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented without support for read-write (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but cannot be configured with this MIB. Module Compliance of ENTITY-MIB with respect to entity4CRCompliance MUST be supported." MODULE -- this module
EnergyObjectContextMibReadOnly COMPLIANCE MODULE-COMPLIANCE STATUS current DESCRIPTION“当此MIB在不支持读写的情况下实现时（即在只读模式下），则这样的实现可以声明只读符合性。这样的设备可以进行监视，但不能使用此MIB进行配置。必须支持ENTITY-MIB相对于entity4CRCompliance的模块符合性。“模块--此模块”
MANDATORY-GROUPS {
energyObjectContextMIBTableGroup,
energyObjectRelationTableGroup
}
MANDATORY-GROUPS {
energyObjectContextMIBTableGroup,
energyObjectRelationTableGroup
}
GROUP energyObjectOptionalMIBTableGroup DESCRIPTION "A compliant implementation does not have to implement the managed objects in this GROUP."
GROUP energyObjectOptionalMIBTableGroup DESCRIPTION“兼容实现不必实现此组中的托管对象。”
::= { energyObjectContextMIBCompliances 2 }
::= { energyObjectContextMIBCompliances 2 }
-- Units of Conformance
energyObjectContextMIBTableGroup OBJECT-GROUP
OBJECTS {
eoDomainName,
eoRoleDescription,
eoAlternateKey,
eoKeywords,
eoImportance,
eoPowerCategory,
eoPowerInterfaceType
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the EnergyObject."
-- Units of Conformance
energyObjectContextMIBTableGroup OBJECT-GROUP
OBJECTS {
eoDomainName,
eoRoleDescription,
eoAlternateKey,
eoKeywords,
eoImportance,
eoPowerCategory,
eoPowerInterfaceType
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the EnergyObject."
::= { energyObjectContextMIBGroups 1 }
::= { energyObjectContextMIBGroups 1 }
energyObjectOptionalMIBTableGroup OBJECT-GROUP
OBJECTS {
eoEthPortIndex,
eoEthPortGrpIndex,
eoLldpPortNumber,
eoMgmtMacAddress,
eoMgmtAddressType,
eoMgmtAddress,
eoMgmtDNSName
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Object."
::= { energyObjectContextMIBGroups 2 }
energyObjectOptionalMIBTableGroup OBJECT-GROUP
OBJECTS {
eoEthPortIndex,
eoEthPortGrpIndex,
eoLldpPortNumber,
eoMgmtMacAddress,
eoMgmtAddressType,
eoMgmtAddress,
eoMgmtDNSName
}
STATUS current
DESCRIPTION
"This group contains the collection of all the objects
related to the Energy Object."
::= { energyObjectContextMIBGroups 2 }
energyObjectRelationTableGroup OBJECT-GROUP OBJECTS {
energyObjectRelationTableGroup对象组对象{
eoRelationID,
eoRelationship,
eoRelationStatus,
eoRelationStorageType
}
STATUS current
DESCRIPTION
"This group contains the collection of all objects
specifying the relationship between Energy Objects."
::= { energyObjectContextMIBGroups 3 }
END
eoRelationID,
eoRelationship,
eoRelationStatus,
eoRelationStorageType
}
STATUS current
DESCRIPTION
"This group contains the collection of all objects
specifying the relationship between Energy Objects."
::= { energyObjectContextMIBGroups 3 }
END
IANA-ENERGY-RELATION-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
IANA-ENERGY-RELATION-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ianaEnergyRelationMIB MODULE-IDENTITY LAST-UPDATED "201502090000Z" -- February 9, 2015 ORGANIZATION "IANA" CONTACT-INFO " Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 United States Tel: +1-310-301-5800 EMail: iana@iana.org"
ianaEnergyRelationMIB MODULE-IDENTITY最后一次更新“201502090000Z”--2015年2月9日组织“IANA”联系方式“互联网分配号码管理局邮政：ICANN 12025 Waterfront Dr.，美国加利福尼亚州洛杉矶300号套房90094电话：+1-310-301-5800电子邮件：iana@iana.org"
DESCRIPTION "Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
说明“版权所有（c）2015 IETF信托基金和被认定为代码作者的人士。保留所有权利。
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).
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info).
This MIB module defines a TEXTUAL-CONVENTION that describes the relationships between Energy Objects.
此MIB模块定义了描述能量对象之间关系的文本约定。
The initial version of this MIB module was published in RFC 7461; for full legal notices see the RFC itself."
该MIB模块的初始版本发布在RFC 7461中；有关完整的法律通知，请参见RFC本身。”
REVISION "201502090000Z" -- February 9, 2015
DESCRIPTION "Initial version of this MIB as published in
RFC 7461."
::= { mib-2 232 }
REVISION "201502090000Z" -- February 9, 2015
DESCRIPTION "Initial version of this MIB as published in
RFC 7461."
::= { mib-2 232 }
-- Textual Conventions
--文本约定
IANAEnergyRelationship ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value specifying the type of
relationship between an Energy Object A, on
IANAEnergyRelationship ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value specifying the type of
relationship between an Energy Object A, on
which the relationship is specified, with the Energy Object B, identified by the UUID.
其中指定了与UUID标识的能量对象B的关系。
The enumeration 'poweredBy' is applicable if Energy Object A is poweredBy Energy Object B.
如果能量对象A由能量对象B供电，则枚举“poweredBy”适用。
The enumeration 'powering' is applicable if Energy Object A is powering Energy Object B.
如果能量对象A为能量对象B供电，则枚举“供电”适用。
The enumeration 'meteredBy' is applicable if Energy Object A is meteredBy Energy Object B.
如果能源对象A由能源对象B计量，则枚举“计量单位”适用。
The enumeration 'metering' is applicable if Energy Object A is metering Energy Object B.
如果能源对象A是计量能源对象B，则枚举“计量”适用。
The enumeration 'aggregatedBy' is applicable if Energy Object A is aggregatedBy Energy Object B.
如果能源对象A是由能源对象B聚合的，则枚举“aggregatedBy”适用。
The enumeration 'aggregating' is applicable if Energy Object A is aggregating Energy Object B."
如果能量对象A正在聚合能量对象B，则枚举“聚合”适用。”
SYNTAX INTEGER {
poweredBy(1), -- power relationship
powering(2),
meteredBy(3), -- meter relationship
metering(4),
aggregatedBy(5), -- aggregation relationship
aggregating(6)
}
SYNTAX INTEGER {
poweredBy(1), -- power relationship
powering(2),
meteredBy(3), -- meter relationship
metering(4),
aggregatedBy(5), -- aggregation relationship
aggregating(6)
}
END
终止
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:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作会使设备受到攻击。以下是表和对象及其敏感度/漏洞：
Unauthorized changes to the eoDomainName, entPhysicalName, eoRoleDescription, eoKeywords, eoImportance, eoAlternateKey, eoRelationID, eoRelationship, eoRelationStatus, and/or eoRelationStorageType MAY disrupt power and energy collection, and therefore any predefined policies defined in the network.
对eoDomainName、entPhysicalName、eoRoleDescription、eoKeywords、eoImportance、eoAlternateKey、eoRelationID、eoRelationStatus和/或eoRelationStorageType的未经授权的更改可能会中断电源和能量收集，从而中断网络中定义的任何预定义策略。
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.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
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].
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.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
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.
在某些情况下，能量和功率监测可以揭示有关个人活动和习惯的敏感信息。本规范的实施者应使用RFC 6988第9节中讨论的适当隐私保护，并且只有在获得适当授权的情况下，才能对个人和家庭进行监控。
The MIB modules in this document use the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配的对象标识符值：
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
energyObjectContextMIB { mib-2 231 }
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
energyObjectContextMIB { mib-2 231 }
This document defines the first version of the IANA-maintained IANA-ENERGY-RELATION-MIB module, which allows new definitions of relationships between Energy Objects.
本文档定义了IANA维护的IANA-ENERGY-RELATION-MIB模块的第一个版本，该模块允许对能源对象之间的关系进行新的定义。
A Specification Required as defined in [RFC5226] is REQUIRED for each modification of the energy relationships.
能量关系的每次修改都需要[RFC5226]中定义的规范。
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry.
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配的对象标识符值。
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
ianaEnergyRelationMIB { mib-2 232 }
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
ianaEnergyRelationMIB { mib-2 232 }
[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>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月<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>.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月<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>.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月<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>.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 25801999年4月<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>.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月<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>.
[RFC3621]Berger，A.和D.Romascanu，“电力以太网MIB”，RFC 36212003年12月<http://www.rfc-editor.org/info/rfc3621>.
[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>.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，2004年6月<http://www.rfc-editor.org/info/rfc3826>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005, <http://www.rfc-editor.org/info/rfc4122>.
[RFC4122]Leach，P.，Mealling，M.和R.Salz，“通用唯一标识符（UUID）URN名称空间”，RFC 4122，2005年7月<http://www.rfc-editor.org/info/rfc4122>.
[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>.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，STD 78，RFC 5591，2009年6月<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>.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 55922009年6月<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>.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，STD 78，RFC 63532011年7月<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>.
[RFC6933]Bierman，A.，Romascanu，D.，Quittek，J.，和M.Chandramouli，“实体MIB（版本4）”，RFC 69332013年5月<http://www.rfc-editor.org/info/rfc6933>.
[RFC7460] Chandramouli, Claise, B., Schoening, B., Quittek, J., and Dietz, T., "Monitoring and Control MIB for Power and Energy", RFC 7460, March 2015, <http://www.rfc-editor.org/info/rfc7460>.
[RFC7460]Chandramouli，Claise，B.，Schoining，B.，Quittek，J.，和Dietz，T.，“电力和能源的监控MIB”，RFC 7460，2015年3月<http://www.rfc-editor.org/info/rfc7460>.
[LLDP-MED-MIB] ANSI/TIA-1057, "The LLDP Management Information Base extension module for TIA-TR41.4 media endpoint discovery information", July 2005.
[LLDP-MED-MIB]ANSI/TIA-1057，“TIA-TR41.4媒体端点发现信息的LLDP管理信息库扩展模块”，2005年7月。
[LLDP-MIB] IEEE, "Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components", IEEE 802.1AB, May 2005.
[LLDP-MIB]IEEE，“用于LLDP配置、统计、本地系统数据和远程系统数据组件的管理信息基础模块”，IEEE 802.1AB，2005年5月。
[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>.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月<http://www.rfc-editor.org/info/rfc3410>.
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor Management Information Base", RFC 3433, December 2002, <http://www.rfc-editor.org/info/rfc3433>.
[RFC3433]Bierman，A.，Romascanu，D.，和K.Norseth，“实体传感器管理信息库”，RFC 3433，2002年12月<http://www.rfc-editor.org/info/rfc3433>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[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>.
[RFC6988]Quitek，J.，Ed.，Chandramouli，M.，Winter，R.，Dietz，T.，和B.Claise，“能源管理要求”，RFC 6988，2013年9月<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>.
[RFC7326]Parello，J.，Claise，B.，Schoining，B.，和J.Quitek，“能源管理框架”，RFC 7326，2014年9月<http://www.rfc-editor.org/info/rfc7326>.
[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.
[EMAN-AS]Schoening，B.，Chandramouli，M.，和B.Nordman，“能源管理（EMAN）适用性声明”，正在进行的工作，草案-ietf-EMAN-Applicability-Statement-082014年12月。
Acknowledgements
致谢
We would like to thank Juergen Quittek and Juergen Schoenwalder for their suggestions on the new design of eoRelationTable, which was a proposed solution for the open issue on the representation of Energy Object as a UUID list.
我们要感谢Juergen Quitek和Juergen Schoenwalder就eoRelationTable的新设计提出的建议，这是针对将能源对象表示为UUID列表这一公开问题提出的解决方案。
Many thanks to Juergen Quittek for many comments on the wording, text, and design of the MIB thus resulting in an improved document.
非常感谢Juergen Quitek对MIB的措辞、文本和设计提出的许多意见，从而改进了文档。
Many thanks to Alan Luchuk for the review of the MIB and his comments.
非常感谢Alan Luchuk对MIB的审查和他的评论。
In addition, the authors thank Bill Mielke for his multiple reviews, Brad Schoening and Juergen Schoenwaelder for their suggestions, and Michael Brown for dramatically improving this document.
此外，作者感谢Bill Mielke的多篇评论，感谢Brad Schoening和Juergen Schoenwaeld的建议，感谢Michael Brown对本文档的显著改进。
Finally, thanks to the EMAN WG chairs: Nevil Brownlee and Tom Nadeau.
最后，感谢伊曼工作组主席：内维尔·布朗利和汤姆·纳多。
Authors' Addresses
作者地址
John Parello Cisco Systems, Inc. 3550 Cisco Way San Jose, California 95134 United States
约翰·帕雷罗思科系统公司，美国加利福尼亚州圣何塞市思科大道3550号，邮编95134
Phone: +1 408 525 2339
EMail: jparello@cisco.com
Phone: +1 408 525 2339
EMail: jparello@cisco.com
Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 Diegem 1813 Belgium
比利时Benoit Claise思科系统有限公司De Kleetlaan 6a b1 Diegem 1813
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Mouli Chandramouli Cisco Systems, Inc. Sarjapur Outer Ring Road Bangalore 560103 India
Mouli Chandramouli Cisco Systems，Inc.印度班加罗尔Sarjapur外环路560103
Phone: +91 80 4429 2409
EMail: moulchan@cisco.com
Phone: +91 80 4429 2409
EMail: moulchan@cisco.com