Internet Engineering Task Force (IETF) A. Bierman
Request for Comments: 6933 YumaWorks, Inc.
Obsoletes: 4133 D. Romascanu
Category: Standards Track Avaya
ISSN: 2070-1721 J. Quittek
NEC Europe Ltd.
M. Chandramouli
Cisco Systems, Inc.
May 2013
Internet Engineering Task Force (IETF) A. Bierman
Request for Comments: 6933 YumaWorks, Inc.
Obsoletes: 4133 D. Romascanu
Category: Standards Track Avaya
ISSN: 2070-1721 J. Quittek
NEC Europe Ltd.
M. Chandramouli
Cisco Systems, Inc.
May 2013
Entity MIB (Version 4)
实体MIB（版本4）
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于管理由单个简单网络管理协议（SNMP）代理管理的多个逻辑和物理实体的托管对象。本文档指定实体MIB的版本4。本备忘录废除了发布为RFC 4133的实体MIB模块的第3版。
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/rfc6933.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6933.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 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
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从该文档中提取的代码组件必须
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.
包括信托法律条款第4.e节中所述的简化BSD许可证文本，且不提供简化BSD许可证中所述的担保。
Table of Contents
目录
1. The SNMP Management Framework ...................................3
2. Overview ........................................................3
2.1. Terms ......................................................5
2.2. Relationship to Community Strings ..........................6
2.3. Relationship to SNMP Contexts ..............................6
2.4. Relationship to Proxy Mechanisms ...........................6
2.5. Relationship to a Chassis MIB ..............................7
2.6. Relationship to the Interfaces MIB .........................7
2.7. Relationship to the Other MIB Modules ......................7
2.8. Relationship to Naming Scopes ..............................7
2.9. Multiple Instances of the Entity MIB .......................8
2.10. Re-Configuration of Entities ..............................9
2.11. Textual Convention Change .................................9
2.12. MIB Structure .............................................9
2.12.1. entityPhysical Group ..............................10
2.12.2. entityLogical Group ...............................12
2.12.3. entityMapping Group ...............................12
2.12.4. entityGeneral Group ...............................13
2.12.5. entityNotifications Group .........................13
2.13. Multiple Agents ..........................................13
2.14. Changes Since RFC 2037 ...................................14
2.14.1. Textual Conventions ...............................14
2.14.2. New entPhysicalTable Objects ......................14
2.14.3. New entLogicalTable Objects .......................14
2.14.4. Bug Fixes .........................................14
2.15. Changes Since RFC 2737 ...................................15
2.15.1. Textual Conventions ...............................15
2.15.2. New Objects .......................................15
2.15.3. Bug Fixes .........................................15
2.16. Changes Since RFC 4133 ...................................15
2.16.1. MIB Module Addition ...............................15
2.16.2. Modification to Some of the MIB Objects ...........15
2.16.3. New TC for Universally Unique Identifier ..........16
3. MIB Definitions ................................................16
3.1. ENTITY-MIB ................................................16
3.2. IANA-ENTITY-MIB ...........................................50
3.3. UUID-TC-MIB ...............................................53
4. Usage Examples .................................................55
4.1. Router/Bridge .............................................55
4.2. Repeaters .................................................62
4.3. EMAN Example ..............................................69
5. Security Considerations ........................................70
1. The SNMP Management Framework ...................................3
2. Overview ........................................................3
2.1. Terms ......................................................5
2.2. Relationship to Community Strings ..........................6
2.3. Relationship to SNMP Contexts ..............................6
2.4. Relationship to Proxy Mechanisms ...........................6
2.5. Relationship to a Chassis MIB ..............................7
2.6. Relationship to the Interfaces MIB .........................7
2.7. Relationship to the Other MIB Modules ......................7
2.8. Relationship to Naming Scopes ..............................7
2.9. Multiple Instances of the Entity MIB .......................8
2.10. Re-Configuration of Entities ..............................9
2.11. Textual Convention Change .................................9
2.12. MIB Structure .............................................9
2.12.1. entityPhysical Group ..............................10
2.12.2. entityLogical Group ...............................12
2.12.3. entityMapping Group ...............................12
2.12.4. entityGeneral Group ...............................13
2.12.5. entityNotifications Group .........................13
2.13. Multiple Agents ..........................................13
2.14. Changes Since RFC 2037 ...................................14
2.14.1. Textual Conventions ...............................14
2.14.2. New entPhysicalTable Objects ......................14
2.14.3. New entLogicalTable Objects .......................14
2.14.4. Bug Fixes .........................................14
2.15. Changes Since RFC 2737 ...................................15
2.15.1. Textual Conventions ...............................15
2.15.2. New Objects .......................................15
2.15.3. Bug Fixes .........................................15
2.16. Changes Since RFC 4133 ...................................15
2.16.1. MIB Module Addition ...............................15
2.16.2. Modification to Some of the MIB Objects ...........15
2.16.3. New TC for Universally Unique Identifier ..........16
3. MIB Definitions ................................................16
3.1. ENTITY-MIB ................................................16
3.2. IANA-ENTITY-MIB ...........................................50
3.3. UUID-TC-MIB ...............................................53
4. Usage Examples .................................................55
4.1. Router/Bridge .............................................55
4.2. Repeaters .................................................62
4.3. EMAN Example ..............................................69
5. Security Considerations ........................................70
6. IANA Considerations ............................................72
7. Acknowledgements ...............................................73
8. References .....................................................73
8.1. Normative References ......................................73
8.2. Informative References ....................................74
6. IANA Considerations ............................................72
7. Acknowledgements ...............................................73
8. References .....................................................73
8.1. Normative References ......................................73
8.2. Informative References ....................................74
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 a MIB module that is compliant to the 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]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照RFC 2119[RFC2119]中的说明进行解释。
There is a need for a standardized way of representing a single agent, which supports multiple instances of one MIB module. This is presently true for at least 3 standard MIB modules and is likely to become true for more and more MIB modules as time passes. For example:
需要一种表示单个代理的标准化方法，它支持一个MIB模块的多个实例。目前至少有3个标准MIB模块是这样，随着时间的推移，越来越多的MIB模块可能会这样。例如：
- multiple instances of a bridge supported within a single device that has a single agent;
- 具有单个代理的单个设备内支持的网桥的多个实例；
- multiple repeaters supported by a single agent; and
- 由单个代理支持的多个中继器；和
- multiple OSPF backbone areas, each operating as part of its own Autonomous System and each identified by the same area-id (e.g., 0.0.0.0), supported inside a single router with one agent.
- 多个OSPF主干区域，每个区域作为其自身自治系统的一部分运行，并且每个区域由相同的区域id（例如，0.0.0.0）标识，在具有一个代理的单个路由器内受支持。
The single agent present in each of these cases implies a relationship binds these entities. Effectively, there is some "overall" physical entity that houses the sum of the things managed by that one agent, i.e., there are multiple "logical" entities within a single physical entity. Sometimes, the overall physical entity
在每种情况下，存在的单个代理意味着这些实体之间存在一种关系。实际上，存在一些“整体”物理实体，其中包含由该代理管理的事物的总和，即，在单个物理实体中存在多个“逻辑”实体。有时，整个物理实体
contains multiple (smaller) physical entities, and each logical entity is associated with a particular physical entity. Sometimes, the overall physical entity is a "compound" of multiple physical entities (e.g., a stack of stackable hubs).
包含多个（较小）物理实体，每个逻辑实体与特定物理实体关联。有时，整个物理实体是多个物理实体的“复合物”（例如，一堆可堆叠的集线器）。
What is needed is a way to determine exactly which logical entities are managed by the agent (with some version of SNMP) in order to communicate with the agent about a particular logical entity. When different logical entities are associated with different physical entities within the overall physical entity, it is also useful to be able to use this information to distinguish between logical entities.
需要的是一种方法来准确地确定代理（使用某些版本的SNMP）管理哪些逻辑实体，以便与代理就特定逻辑实体进行通信。当不同的逻辑实体与整个物理实体中的不同物理实体相关联时，能够使用此信息来区分逻辑实体也很有用。
In these situations, there is no need for varbinds for multiple logical entities to be referenced in the same SNMP message (although that might be useful in the future). Rather, it is sufficient, and in some situations preferable, to have the context/community in the message identify the logical entity to which the varbinds apply.
在这些情况下，在同一个SNMP消息中引用多个逻辑实体不需要varbinds（尽管这在将来可能有用）。相反，让消息中的上下文/社区标识varbind应用的逻辑实体就足够了，而且在某些情况下更可取。
Version 2 of this MIB addresses new requirements that have emerged since the publication of the first Entity MIB [RFC2037]. There is a need for a standardized way of providing non-volatile, administratively assigned identifiers for physical components represented with the Entity MIB. There is also a need to align the Entity MIB with the SNMPv3 administrative framework (STD 62, [RFC3411]). Implementation experience has shown that additional physical component attributes are also desirable.
该MIB的版本2解决了自发布第一个实体MIB[RFC2037]以来出现的新需求。需要一种标准化的方法，为实体MIB表示的物理组件提供非易失性的、管理分配的标识符。还需要将实体MIB与SNMPv3管理框架（STD 62，[RFC3411]）对齐。实施经验表明，附加的物理组件属性也是可取的。
Version 3 of this MIB addresses new requirements that have emerged since the publication of the second Entity MIB [RFC2737]. There is a need to identify physical entities that are central processing units (CPUs) and a need to provide a Textual Convention (TC) that identifies an entPhysicalIndex value or zero, where the value zero has application-specific semantics. Two new objects have been added to the entPhysicalTable to identify the manufacturing date and provide additional URIs for a particular physical entity.
该MIB的第3版解决了自第二个实体MIB[RFC2737]发布以来出现的新需求。需要识别作为中央处理器（CPU）的物理实体，并且需要提供一个文本约定（TC），用于识别entPhysicalIndex值或零，其中值零具有特定于应用程序的语义。entPhysicalTable中添加了两个新对象，以标识制造日期并为特定物理实体提供附加URI。
Version 4 of this MIB addresses new requirements that have emerged since the publication of the third version of the Entity MIB [RFC4133]. There is a need to add new enumerated values for entity physical classes, a need to provide identification information for physical entities using a Universally Unique Identifier (UUID) format, and a need to have compliant implementations of the Entity MIB with a smaller subsets of MIB objects for devices with constrained resources.
本MIB第4版解决了自发布第三版实体MIB[RFC4133]以来出现的新需求。需要为实体物理类添加新的枚举值，需要使用通用唯一标识符（UUID）格式为物理实体提供标识信息，需要为资源受限的设备提供具有较小MIB对象子集的实体MIB兼容实现。
The PhysicalClass TEXTUAL-CONVENTION was deprecated, and a new IANAPhysicalClass TC (maintained by IANA) was created. A new TC, UUIDorZero, was created to represent a UUID, and a new MIB object was
不推荐使用PhysicalClass文本约定，并创建了一个新的IANAPhysicalClass TC（由IANA维护）。创建了一个新的TC UUIDRZero来表示UUID，并创建了一个新的MIB对象
added to the entPhysicalTable to identify an entity. A new compliance statement, entity4CRCompliance, has been added for possible implementation of a selected subset of MIB objects by entities with constrained resources.
添加到entPhysicalTable以标识实体。添加了一个新的符合性声明entity4CRCompliance，以便资源受限的实体可能实现MIB对象的选定子集。
The following terms are used throughout this document:
本文件中使用了以下术语：
- Naming Scope A "naming scope" represents the set of information that may be potentially accessed through a single SNMP operation. All instances within the naming scope share the same unique identifier space. For SNMPv1, a naming scope is identified by the value of the associated entLogicalCommunity instance. For SNMPv3, the term "context" is used instead of "naming scope". The complete definition of an SNMP context can be found in Section 3.3.1 of RFC 3411 [RFC3411].
- 命名范围“命名范围”表示可能通过单个SNMP操作访问的信息集。命名范围内的所有实例共享相同的唯一标识符空间。对于SNMPv1，命名范围由关联的entLogicalCommunity实例的值标识。对于SNMPv3，使用术语“上下文”而不是“命名范围”。SNMP上下文的完整定义见RFC 3411[RFC3411]第3.3.1节。
- Multi-Scoped Object A MIB object for which identical instance values identify different managed information in different naming scopes is called a "multi-scoped" MIB object.
- 多作用域对象相同实例值标识不同命名作用域中不同托管信息的MIB对象称为“多作用域”MIB对象。
- Single-Scoped Object A MIB object for which identical instance values identify the same managed information in different naming scopes is called a "single-scoped" MIB object.
- 单作用域对象相同实例值标识不同命名作用域中相同托管信息的MIB对象称为“单作用域”MIB对象。
- Logical Entity A managed system contains one or more "logical entities", each represented by at most one instantiation of each of a particular set of MIB objects. A set of management functions is associated with each logical entity. Examples of logical entities include routers, bridges, print-servers, etc.
- 逻辑实体受管系统包含一个或多个“逻辑实体”，每个“逻辑实体”最多由一组特定MIB对象的一个实例化表示。一组管理功能与每个逻辑实体相关联。逻辑实体的示例包括路由器、网桥、打印服务器等。
- Physical Entity A "physical entity" or "physical component" represents an identifiable physical resource within a managed system. Zero or more logical entities may utilize a physical resource at any given time. Determining which physical components are represented by an agent in the EntPhysicalTable is an implementation-specific matter. Typically, physical resources (e.g., communications ports, backplanes, sensors, daughter-cards, power supplies, and the overall chassis), which can be managed via functions associated with one or more logical entities, are included in the MIB.
- 物理实体“物理实体”或“物理组件”表示管理系统内的可识别物理资源。零个或多个逻辑实体可在任何给定时间使用物理资源。确定哪些物理组件由EntPhysicalTable中的代理表示是一个特定于实现的问题。通常，MIB中包括可通过与一个或多个逻辑实体相关联的功能进行管理的物理资源（例如，通信端口、背板、传感器、子卡、电源和整个机箱）。
- Containment Tree Each physical component may be modeled as 'contained' within another physical component. A "containment-tree" is the conceptual sequence of entPhysicalIndex values that uniquely specifies the exact physical location of a physical component within the managed system. It is generated by 'following and recording' each entPhysicalContainedIn instance 'up the tree towards the root' until a value of zero, indicating no further containment, is found.
- 包含树每个物理组件可以建模为“包含”在另一个物理组件中。“包含树”是entPhysicalIndex值的概念序列，它唯一地指定了托管系统中物理组件的确切物理位置。它是通过“跟踪并记录”实例中的每个entPhysicalContainedIn“向上到根”生成的，直到找到一个零值，表示没有进一步的包含。
For community-based SNMP, differentiating logical entities is one (but not the only) purpose of the community string [RFC1157]. This is accommodated by representing each community string as a logical entity.
对于基于社区的SNMP，区分逻辑实体是社区字符串[RFC1157]的一个（但不是唯一）用途。这可以通过将每个社区字符串表示为逻辑实体来实现。
Note that different logical entities may share the same naming scope and, therefore, the same values of entLogicalCommunity. This is possible, providing they have no need for the same instance of a MIB object to represent different managed information.
请注意，不同的逻辑实体可能共享相同的命名范围，因此entLogicalCommunity的值相同。这是可能的，前提是它们不需要MIB对象的同一实例来表示不同的托管信息。
Version 2 of the Entity MIB contains support for associating SNMPv3 contexts with logical entities. Two new MIB objects, defining an SnmpEngineID and ContextName pair, are used together to identify an SNMP context associated with a logical entity. This context can be used (in conjunction with the entLogicalTAddress and entLogicalTDomain MIB objects) to send SNMPv3 messages on behalf of a particular logical entity.
实体MIB的版本2支持将SNMPv3上下文与逻辑实体关联。两个新的MIB对象（定义SnmpEngineID和ContextName对）一起用于标识与逻辑实体关联的SNMP上下文。此上下文可用于（与EntLogicalAddress和EntLogicalDomain MIB对象一起）代表特定逻辑实体发送SNMPv3消息。
The Entity MIB is designed to allow functional component discovery. The administrative relationships between different logical entities are not visible in any Entity MIB tables. A Network Management System (NMS) cannot determine whether MIB instances in different naming scopes are realized locally or remotely (e.g., via some proxy mechanism) by examining any particular Entity MIB objects.
实体MIB旨在允许功能组件发现。不同逻辑实体之间的管理关系在任何实体MIB表中都不可见。网络管理系统（NMS）无法通过检查任何特定实体MIB对象来确定不同命名范围内的MIB实例是本地实现还是远程实现（例如，通过某种代理机制）。
The management of administrative framework functions is not an explicit goal of the Entity MIB WG at this time. This new area of functionality may be revisited after some operational experience with the Entity MIB is gained.
目前，管理框架职能的管理不是实体MIB工作组的明确目标。在获得实体MIB的一些操作经验后，可以重新访问这个新的功能领域。
Note that for community-based versions of SNMP, a network administrator will likely be able to associate community strings with naming scopes that have proprietary mechanisms, as a matter of configuration. There are no mechanisms for managing naming scopes defined in this MIB.
请注意，对于基于社区的SNMP版本，网络管理员可能能够将社区字符串与具有专有机制的命名范围相关联，这是一个配置问题。没有管理此MIB中定义的命名范围的机制。
Some readers may recall that a previous IETF working group attempted to define a Chassis MIB. No consensus was reached by that working group, possibly because its scope was too broad. As such, it is not the purpose of the ENTITY-MIB module to be a "Chassis MIB replacement", nor is it within the scope of the ENTITY-MIB module to contain all the information that might be necessary to manage a "chassis". On the other hand, the entities represented by an implementation of the ENTITY-MIB module might well be contained in a chassis.
一些读者可能还记得，以前的IETF工作组曾试图定义机箱MIB。该工作组没有达成共识，可能是因为其范围太广。因此，ENTITY-MIB模块的目的不是“机箱MIB替换”，也不在ENTITY-MIB模块的范围内，包含管理“机箱”可能需要的所有信息。另一方面，ENTITY-MIB模块的实现所表示的实体很可能包含在机箱中。
The Entity MIB contains a mapping table identifying physical components that have 'external values' (e.g., ifIndex) associated with them within a given naming scope. This table can be used to identify the physical location of each interface in the ifTable [RFC2863]. Because ifIndex values in different contexts are not related to one another, the interface-to-physical-component associations are relative to the same logical entity within the agent.
实体MIB包含一个映射表，标识在给定命名范围内具有与其关联的“外部值”（如ifIndex）的物理组件。此表可用于确定ifTable[RFC2863]中每个接口的物理位置。由于不同上下文中的iIndex值彼此不相关，因此物理组件关联的接口相对于代理中的同一逻辑实体。
The Entity MIB also contains entPhysicalName and entPhysicalAlias objects, which approximate the semantics of the ifName and ifAlias objects (respectively) from the Interfaces MIB [RFC2863] for all types of physical components.
实体MIB还包含entPhysicalName和entPhysicalAlias对象，它们分别近似于接口MIB[RFC2863]中所有类型物理组件的ifName和ifAlias对象的语义。
The Entity MIB contains a mapping table identifying physical components that have identifiers from other standard MIB modules associated with them. For example, this table can be used along with the physical mapping table to identify the physical location of each repeater port in the rptrPortTable or each interface in the ifTable.
实体MIB包含一个映射表，该映射表标识具有与之相关联的其他标准MIB模块标识符的物理组件。例如，此表可与物理映射表一起使用，以标识rptrPortTable中每个中继器端口或ifTable中每个接口的物理位置。
There is some question as to which MIB objects may be returned within a given naming scope. MIB objects that are not multi-scoped within a managed system are likely to ignore context information in
关于在给定的命名范围内可以返回哪些MIB对象，存在一些问题。在托管系统中不具有多作用域的MIB对象可能会忽略系统中的上下文信息
implementation. In such a case, it is likely such objects will be returned in all naming scopes (e.g., not just the 'default' naming scope or the SNMPv3 default context).
实施在这种情况下，很可能会在所有命名范围（例如，不只是“默认”命名范围或SNMPv3默认上下文）中返回此类对象。
For example, a community string used to access the management information for logical device 'bridge2' may allow access to all the non-bridge-related objects in the 'default' naming scope, as well as a second instance of the Bridge MIB [RFC4188].
例如，用于访问逻辑设备“bridge2”的管理信息的社区字符串可能允许访问“默认”命名范围内的所有非网桥相关对象，以及网桥MIB的第二个实例[RFC4188]。
The isolation of single-scoped MIB objects by the agent is an implementation-specific matter. An agent may wish to limit the objects returned in a particular naming scope to only the multi-scoped objects in that naming scope (e.g., system group and the Bridge MIB). In this case, all single-scoped management information would belong to a common naming scope (e.g., 'default'), which itself may contain some multi-scoped objects (e.g., system group).
代理对单作用域MIB对象的隔离是一个特定于实现的问题。代理可能希望将特定命名范围内返回的对象限制为该命名范围内的多作用域对象（例如，系统组和网桥MIB）。在这种情况下，所有单作用域管理信息将属于一个公共命名作用域（例如，“默认”），该命名作用域本身可能包含一些多作用域对象（例如，系统组）。
It is possible that more than one agent may exist in a managed system. In such cases, multiple instances of the Entity MIB (representing the same managed objects) may be available to an NMS.
托管系统中可能存在多个代理。在这种情况下，NMS可以使用实体MIB的多个实例（表示相同的托管对象）。
In order to reduce complexity for agent implementation, multiple instances of the Entity MIB are not required to be equivalent or even consistent. An NMS may be able to 'align' instances returned by different agents by examining the columns of each table, but vendor-specific identifiers and (especially) index values are likely to be different. Each agent may be managing different subsets of the entire chassis as well.
为了降低代理实现的复杂性，实体MIB的多个实例不需要等价甚至一致。NMS可能能够通过检查每个表的列来“对齐”不同代理返回的实例，但供应商特定的标识符和（特别是）索引值可能不同。每个代理也可以管理整个机箱的不同子集。
When all of a physically modular device is represented by a single agent, the entry (for which entPhysicalContainedIn has the value zero) would likely have 'chassis' as the value of its entPhysicalClass. Alternatively, for an agent on a module where the agent represents only the physical entities on that module (not those on other modules), the entry (for which entPhysicalContainedIn has the value zero) would likely have 'module' as the value of its entPhysicalClass.
当所有物理模块化设备都由单个代理表示时，条目（entPhysicalContainedIn的值为零）可能将“机箱”作为其entPhysicalClass的值。或者，对于模块上的代理，如果该代理仅表示该模块上的物理实体（而不是其他模块上的实体），则条目（entPhysicalContainedIn的值为零）可能将“module”作为其entPhysicalClass的值。
An agent implementation of the entLogicalTable is not required to contain information about logical entities managed primarily by other agents. That is, the entLogicalTAddress and entLogicalTDomain objects in the entLogicalTable are provided to support a historical multiplexing mechanism, not to identify other SNMP agents.
entLogicalTable的代理实现不需要包含主要由其他代理管理的逻辑实体的信息。也就是说，提供entLogicalTable中的EntLogicalAddress和EntLogicalDomain对象是为了支持历史多路复用机制，而不是为了识别其他SNMP代理。
Note that the Entity MIB is a single-scoped MIB, in the event an agent represents the MIB in different naming scopes.
请注意，实体MIB是单作用域MIB，如果代理在不同的命名作用域中表示MIB。
Most of the MIB objects defined in this MIB have, at most, a read-only MAX-ACCESS clause. This is a conscious decision by the working group to limit this MIB's scope. The second version of the Entity MIB allows a network administrator to configure some common attributes of physical components.
此MIB中定义的大多数MIB对象最多有一个只读MAX-ACCESS子句。这是工作组有意识地决定限制MIB的范围。实体MIB的第二个版本允许网络管理员配置物理组件的一些公共属性。
Version 1 of the Entity MIB contains three MIB objects defined with the (now obsolete) DisplayString TEXTUAL-CONVENTION. In version 2 of the Entity MIB, the syntax for these objects has been updated to use the (now preferred) SnmpAdminString TEXTUAL-CONVENTION.
实体MIB的版本1包含三个MIB对象，它们是用（现已过时的）DisplayString文本约定定义的。在实体MIB的版本2中，这些对象的语法已更新为使用（现在首选）SNMPAdministring文本约定。
The ENTMIB working group (which was in charge of the document at that point) realized that this change is not strictly supported by SMIv2. In their judgment, the alternative of deprecating the old objects and defining new objects would have had a more adverse impact on backward compatibility and interoperability, given the particular semantics of these objects.
ENTMIB工作组（当时负责该文档）意识到SMIv2并不严格支持此更改。根据他们的判断，考虑到这些对象的特定语义，弃用旧对象和定义新对象的替代方案会对向后兼容性和互操作性产生更不利的影响。
The Entity MIB contains five groups of MIB objects:
实体MIB包含五组MIB对象：
- entityPhysical group Describes the physical entities managed by a single agent.
- entityPhysical group描述由单个代理管理的物理实体。
- entityLogical group Describes the logical entities managed by a single agent.
- entityLogical group描述由单个代理管理的逻辑实体。
- entityMapping group Describes the associations between the physical entities, logical entities, interfaces, and non-interface ports managed by a single agent.
- entityMapping组描述由单个代理管理的物理实体、逻辑实体、接口和非接口端口之间的关联。
- entityGeneral group Describes general system attributes shared by potentially all types of entities managed by a single agent.
- entityGeneral group描述由单个代理管理的所有类型实体共享的常规系统属性。
- entityNotifications group Contains status indication notifications.
- entityNotifications组包含状态指示通知。
This group contains a single table to identify physical system components, called the entPhysicalTable.
此组包含一个用于标识物理系统组件的表，称为entPhysicalTable。
The entPhysicalTable contains one row per physical entity and must always contain at least one row for an "overall" physical entity, which should have an entPhysicalClass value of 'stack(11)', 'chassis(3)', or 'module(9)'.
entPhysicalTable每个物理实体包含一行，并且对于“总体”物理实体，必须始终至少包含一行，其entPhysicalClass值应为“堆栈（11）”、“机箱（3）”或“模块（9）”。
Each row is indexed by an arbitrary, small integer and contains a description and type of the physical entity. It also optionally contains the index number of another entPhysicalEntry, indicating a containment relationship between the two.
每一行都由一个任意的小整数索引，并包含物理实体的描述和类型。它还可以选择包含另一个entPhysicalEntry的索引号，指示两者之间的包含关系。
Version 2 of the Entity MIB provides additional MIB objects for each physical entity. Some common read-only attributes have been added, as well as three writable string objects.
实体MIB的版本2为每个物理实体提供了额外的MIB对象。添加了一些常见的只读属性，以及三个可写字符串对象。
- entPhysicalAlias This string can be used by an NMS as a non-volatile identifier for the physical component. Maintaining a non-volatile string for every physical component represented in the entPhysicalTable can be costly and unnecessary. An agent may algorithmically generate entPhysicalAlias strings for particular entries (e.g., based on the entPhysicalClass value).
- entPhysicalAlias此字符串可由NMS用作物理组件的非易失性标识符。为entPhysicalTable中表示的每个物理组件维护一个非易失性字符串可能代价高昂且不必要。代理可以通过算法为特定条目生成entPhysicalAlias字符串（例如，基于entPhysicalClass值）。
- entPhysicalAssetID This string is provided to store a user-specific asset identifier for removable physical components. In order to reduce the non-volatile storage needed by a particular agent, a network administrator should only assign asset identifiers to physical entities that are field-replaceable (i.e., not permanently contained within another physical entity).
- entPhysicalAssetID此字符串用于存储可移动物理组件的用户特定资产标识符。为了减少特定代理所需的非易失性存储，网络管理员应仅将资产标识符分配给可现场更换的物理实体（即，不永久包含在另一个物理实体中）。
- entPhysicalSerialNum This string is provided to store a vendor-specific serial number string for physical components. This writable object is used when an agent cannot identify the serial numbers of all installed physical entities and a network administrator wishes to configure the non-volatile serial number strings manually (via an NMS application).
- entPhysicalSerialNum此字符串用于存储物理组件的特定于供应商的序列号字符串。当代理无法识别所有已安装物理实体的序列号，且网络管理员希望手动（通过NMS应用程序）配置非易失性序列号字符串时，使用此可写对象。
Version 3 of the Entity MIB provides two additional MIB objects for each physical entity:
实体MIB的版本3为每个物理实体提供了两个额外的MIB对象：
- entPhysicalMfgDate This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported the object is not instantiated. The special value '0000000000000000'H may also be returned in this case.
- EntPhysicalFGDate此对象包含受管实体的制造日期。如果制造日期未知或不受支持，则不会实例化对象。在这种情况下，还可能返回特殊值“0000000000000000”。
- entPhysicalUris This object provides additional identification information about the physical entity.
- entPhysicalUris此对象提供有关物理实体的附加标识信息。
This object contains one or more Uniform Resource Identifiers (URIs); therefore, the syntax of this object must conform to [RFC3986], Section 3. Uniform Resource Names (URNs) [RFC3406] are resource identifiers with the specific requirements for enabling location-independent identification of a resource, as well as longevity of reference. URNs are part of the larger URI family with the specific goal of providing persistent naming of resources. URI schemes and URN namespaces are registered by IANA (see http://www.iana.org/assignments/uri-schemes and http://www.iana.org/assignments/urn-namespaces).
此对象包含一个或多个统一资源标识符（URI）；因此，该对象的语法必须符合[RFC3986]第3节的规定。统一资源名称（URN）[RFC3406]是资源标识符，具有实现资源位置独立标识以及引用寿命的特定要求。URN是更大的URI系列的一部分，其具体目标是提供资源的持久命名。URI方案和URN名称空间由IANA注册（请参阅http://www.iana.org/assignments/uri-schemes 和http://www.iana.org/assignments/urn-namespaces).
For example, the entPhysicalUris object may be used to encode a URI containing a Common Language Equipment Identifier (CLEI) URN for the managed physical entity. The URN namespace for CLEIs is defined in [RFC4152], and the CLEI format is defined in [T1.213] and [T1.213a]. For example, an entPhysicalUris instance may have the value of:
例如，EntPhysicalURI对象可用于编码包含托管物理实体的公共语言设备标识符（CLEI）URN的URI。CLEIs的URN命名空间在[RFC4152]中定义，CLEI格式在[T1.213]和[T1.213a]中定义。例如，EntPhysicalURI实例的值可能为：
URN:CLEI:D4CE18B7AA
URN:CLEI:D4CE18B7AA
[RFC3986] and [RFC4152] identify this as a URI in the CLEI URN namespace. The specific CLEI code, D4CE18B7AA, is based on the example provided in [T1.213a].
[RFC3986]和[RFC4152]将其标识为CLEI URN命名空间中的URI。具体的CLEI代码D4CE18B7AA基于[T1.213a]中提供的示例。
Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored.
可能存在多个URI，并由空格字符分隔。忽略前导和尾随空格字符。
If no additional identification information is known about the physical entity or supported, the object is not instantiated.
如果不知道或不支持有关物理实体的其他标识信息，则不会实例化该对象。
Version 4 of the Entity MIB module provides an additional MIB object for each physical entity.
实体MIB模块的版本4为每个物理实体提供了一个附加的MIB对象。
- entPhysicalUUID This object provides an unique identification about the physical entity. This object contains a globally unique identifier for the physical entity with the format defined in RFC 4122 [RFC4122].
- entPhysicalUUID此对象提供有关物理实体的唯一标识。此对象包含物理实体的全局唯一标识符，其格式在RFC 4122[RFC4122]中定义。
To support the existing implementations of ENTITY-MIB version 3 [RFC4133], entPhysicalUris object should be used to store the UUID value of the physical entity as well in URN format. This duplication of information enables backward compatibility. Note that entPhysicalUris allows write access while entPhysicalUUID is read-only.
为了支持ENTITY-MIB版本3[RFC4133]的现有实现，应使用EntPhysicalURI对象以URN格式存储物理实体的UUID值。这种信息复制实现了向后兼容性。请注意，entPhysicalUris允许写访问，而entPhysicalUUID是只读的。
This group contains a single table to identify logical entities, called the entLogicalTable.
该组包含一个用于标识逻辑实体的表，称为entLogicalTable。
The entLogicalTable contains one row per logical entity. Each row is indexed by an arbitrary, small integer and contains a name, description, and type of the logical entity. It also contains information to allow access to the MIB information for the logical entity. This includes SNMP versions that use a community name (with some form of implied context representation) and SNMP versions that use the SNMP ARCH [RFC3411] method of context identification.
entLogicalTable每个逻辑实体包含一行。每一行都由一个任意的小整数索引，并包含逻辑实体的名称、描述和类型。它还包含允许访问逻辑实体的MIB信息的信息。这包括使用团体名称（具有某种形式的隐含上下文表示）的SNMP版本和使用上下文标识的SNMP ARCH[RFC3411]方法的SNMP版本。
If an agent represents multiple logical entities with this MIB, then this group must be implemented for all logical entities known to the agent.
如果代理使用此MIB表示多个逻辑实体，则必须为代理已知的所有逻辑实体实现此组。
If an agent represents a single logical entity, or multiple logical entities within a single naming scope, then implementation of this group may be omitted by the agent.
如果代理表示单个逻辑实体或单个命名范围内的多个逻辑实体，则代理可能会忽略此组的实现。
This group contains three tables to identify associations between different system components.
此组包含三个表，用于标识不同系统组件之间的关联。
- entLPMappingTable This table contains mappings between entLogicalIndex values (logical entities) and entPhysicalIndex values (the physical components supporting that entity). A logical entity can map to more than one physical component, and more than one logical entity can map to (share) the same physical component. If an agent represents a single logical entity, or multiple logical entities within a single naming scope, then implementation of this table may be omitted by the agent.
- entLPMappingTable此表包含entLogicalIndex值（逻辑实体）和entPhysicalIndex值（支持该实体的物理组件）之间的映射。一个逻辑实体可以映射到多个物理组件，多个逻辑实体可以映射（共享）同一个物理组件。如果代理表示单个逻辑实体或单个命名范围内的多个逻辑实体，则代理可能会忽略此表的实现。
- entAliasMappingTable This table contains mappings between entLogicalIndex, entPhysicalIndex pairs, and 'alias' object identifier values. This allows resources managed with other MIB modules (e.g., repeater ports, bridge ports, physical and logical interfaces) to be identified in the physical entity hierarchy. Note that each alias identifier is only relevant in a particular naming scope. If an agent represents a single logical entity, or multiple logical entities within a single naming scope, then implementation of this table may be omitted by the agent.
- entAliasMappingTable此表包含entLogicalIndex、entPhysicalIndex对和“alias”对象标识符值之间的映射。这允许在物理实体层次结构中标识使用其他MIB模块（例如，中继器端口、网桥端口、物理和逻辑接口）管理的资源。请注意，每个别名标识符仅与特定命名范围相关。如果代理表示单个逻辑实体或单个命名范围内的多个逻辑实体，则代理可能会忽略此表的实现。
- entPhysicalContainsTable This table contains simple mappings between entPhysicalContainedIn values for each container/'containee' relationship in the managed system. The indexing of this table allows an NMS to quickly discover the entPhysicalIndex values for all children of a given physical entity.
- EntPhysicalContainedStable此表包含托管系统中每个容器/containee关系的entPhysicalContainedIn值之间的简单映射。此表的索引允许NMS快速发现给定物理实体的所有子级的entPhysicalIndex值。
This group contains general information relating to the other object groups.
此组包含与其他对象组相关的一般信息。
At this time, the entGeneral group contains a single scalar object (entLastChangeTime), which represents the value of sysUpTime when any part of the Entity MIB configuration last changed.
此时，entGeneral组包含一个标量对象（entLastChangeTime），它表示实体MIB配置的任何部分上次更改时的sysUpTime值。
This group contains notification definitions relating to the overall status of the Entity MIB instantiation.
此组包含与实体MIB实例化的总体状态相关的通知定义。
Even though a primary motivation for this MIB is to represent the multiple logical entities supported by a single agent, another motivation is to represent multiple logical entities supported by multiple agents (in the same "overall" physical entity). Indeed, it is implicit in the SNMP architecture that the number of agents is transparent to a network management station.
尽管此MIB的主要动机是表示单个代理支持的多个逻辑实体，但另一个动机是表示多个代理支持的多个逻辑实体（在同一个“整体”物理实体中）。实际上，在SNMP体系结构中，代理的数量对网络管理站是透明的。
However, there is no agreement at this time as to the degree of cooperation that should be expected for agent implementations. Therefore, multiple agents within the same managed system are free to implement the Entity MIB independently. (For more information, refer to Section 2.9, "Multiple Instances of the Entity MIB".)
然而，对于代理实现的预期合作程度，目前还没有达成一致意见。因此，同一管理系统中的多个代理可以独立地实现实体MIB。（有关更多信息，请参阅第2.9节“实体MIB的多个实例”。）
The PhysicalClass TC text has been clarified, and a new enumeration to support 'stackable' components has been added. The SnmpEngineIdOrNone TC has been added to support SNMPv3.
PhysicalClass TC文本已澄清，并添加了一个新的枚举以支持“可堆叠”组件。已添加SnmpEngineIdOrNone TC以支持SNMPv3。
The entPhysicalHardwareRev, entPhysicalFirmwareRev, and entPhysicalSoftwareRev objects have been added for revision identification.
已添加entPhysicalHardwareRev、entPhysicalFirmwareRev和entPhysicalSoftwareRev对象以进行版本标识。
The entPhysicalSerialNum, entPhysicalMfgName, entPhysicalModelName, and entPhysicalIsFRU objects have been added for better vendor identification for physical components. In the event the agent cannot identify this information, the entPhysicalSerialNum object can be set by a management station.
已添加entPhysicalSerialNum、entPhysicalModelName、entPhysicalModelName和entPhysicalIsFRU对象，以便更好地识别物理组件的供应商。如果代理无法识别此信息，管理站可以设置entPhysicalSerialNum对象。
The entPhysicalAlias and entPhysicalAssetID objects have been added for better user component identification. These objects are intended to be set by a management station and preserved by the agent across restarts.
已添加entPhysicalAlias和entPhysicalAssetID对象，以更好地识别用户组件。这些对象将由管理站设置，并由代理在重新启动期间保留。
The entLogicalContextEngineID and entLogicalContextName objects have been added to provide an SNMP context for SNMPv3 access on behalf of a logical entity.
已添加entLogicalContextEngineID和entLogicalContextName对象，以代表逻辑实体为SNMPv3访问提供SNMP上下文。
A bug was fixed in the entLogicalCommunity object. The subrange was incorrect (1..255) and is now correct (0..255). The description clause has also been clarified. This object is now deprecated.
entLogicalCommunity对象中修复了一个bug。子范围不正确（1..255），现在正确（0..255）。说明条款也已澄清。此对象现在已弃用。
The entLastChangeTime object description has been changed to generalize the events that cause an update to the last change timestamp.
entLastChangeTime对象描述已更改，以概括导致更新到上次更改时间戳的事件。
The syntax was changed from DisplayString to SnmpAdminString for the entPhysicalDescr, entPhysicalName, and entLogicalDescr objects.
entPhysicalDescr、entPhysicalName和entLogicalDescr对象的语法已从DisplayString更改为SnmpAdminString。
The PhysicalIndexOrZero TC has been added to allow objects to reference an entPhysicalIndex value or zero. The PhysicalClass TC has been extended to support a new enumeration for central processing units.
添加了PhysicalIndexOrZero TC以允许对象引用entPhysicalIndex值或零。PhysicalClass TC已扩展为支持中央处理器的新枚举。
The entPhysicalMfgDate object has been added to the entPhysicalTable to provide the date of manufacturing of the managed entity.
EntPhysicalFGDate对象已添加到entPhysicalTable中，以提供托管实体的制造日期。
The entPhysicalUris object has been added to the entPhysicalTable to provide additional identification information about the physical entity, such as a Common Language Equipment Identifier (CLEI) URN.
EntPhysicalURI对象已添加到entPhysicalTable中，以提供有关物理实体的其他标识信息，例如公共语言设备标识符（CLEI）URN。
The syntax was changed from INTEGER to Integer32 for the entPhysicalParentRelPos, entLogicalIndex, and entAliasLogicalIndexOrZero objects, and from INTEGER to PhysicalIndexOrZero for the entPhysicalContainedIn object.
entPhysicalParentRelPos、entLogicalIndex和entAliasLogicalIndexOrZero对象的语法从整数更改为整数32，entPhysicalContainedIn对象的语法从整数更改为物理IndexorZero。
Over time, there may be the need to add new enumerated values to the PhysicalClass TEXTUAL-CONVENTION. To allow for such additions without requiring re-issuing of this MIB module, a new MIB module called IANA-ENTITY-MIB that provides the IANA-maintained TEXTUAL-CONVENTION IANAPhysicalClass has been created. The PhysicalClass TC has been deprecated.
随着时间的推移，可能需要向PhysicalClass文本约定添加新的枚举值。为了允许在不需要重新发布此MIB模块的情况下进行此类添加，已创建一个名为IANA-ENTITY-MIB的新MIB模块，该模块提供IANA维护的文本约定IANAPhysicalClass。PhysicalClass TC已被弃用。
A new MIB object has been added to the entPhysicalTable, entPhysicalUUID. In comparison to entPhysicalUris, the new object is read-only and restricted to a fixed size to allow only for RFC 4122 [RFC4122] compliant values. The PhysicalClass TEXTUAL-CONVENTION was deprecated, and a new IANAPhysicalClass TC (maintained by IANA) has been created.
新的MIB对象已添加到entPhysicalTable中，即entPhysicalUUID。与EntPhysicalURI相比，新对象是只读的，并且限制为固定大小，以仅允许符合RFC 4122[RFC4122]的值。不推荐使用PhysicalClass文本约定，并创建了一个新的IANAPhysicalClass TC（由IANA维护）。
Two new MODULE-COMPLIANCE modules have been created: entity4Compliance for full compliance with version 4 of the Entity MIB, and entity4CRCompliance for devices with constrained resources like batteries that might require a limited number of objects to be supported (entPhysicalClass, entPhysicalName, and entPhysicalUUID).
已经创建了两个新的模块遵从性模块：Entity4CCompliance以完全遵从实体MIB的版本4，以及entity4CRCompliance以适用于资源受限的设备，如电池，这些设备可能需要支持数量有限的对象（entPhysicalClass、entPhysicalName和entPhysicalUUID）。
A new TEXTUAL-CONVENTION, UUIDorZero, was created to represent a Universally Unique Identifier (UUID) with a syntax that conforms to [RFC4122], Section 4.1. Defining it as a TC will allow for future reuse in other MIB modules that will import the TC. This Textual Convention is included in the UUID-TC-MIB module.
创建了一个新的文本约定UUIDorZero，用符合[RFC4122]第4.1节的语法表示通用唯一标识符（UUID）。将其定义为TC将允许将来在导入TC的其他MIB模块中重用。此文本约定包含在UUID-TC-MIB模块中。
ENTITY-MIB DEFINITIONS ::= BEGIN
ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE, Integer32 FROM SNMPv2-SMI -- RFC 2578 TDomain, TAddress, TEXTUAL-CONVENTION, AutonomousType, RowPointer, TimeStamp, TruthValue, DateAndTime FROM SNMPv2-TC -- RFC 2579 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 UUIDorZero FROM UUID-TC-MIB -- RFC 6933 IANAPhysicalClass FROM IANA-ENTITY-MIB; -- RFC 6933
从SNMPv2 SMI中导入模块标识、对象类型、mib-2、通知类型、整数32--RFC 2578 TDomain、TadAddress、文本约定、自治类型、行指针、时间戳、TruthValue、日期和时间从SNMPv2 TC--RFC 2579模块符合性、对象组、，SNMPv2 CONF中的通知组--SNMP-FRAMEWORK-MIB中的RFC 2580 SNMPadmin安装--UUID-TC-MIB中的RFC 3411 UUIDorZero--IANA-ENTITY-MIB中的RFC 6933 IANAPhysicalClass；--RFC 6933
entityMIB MODULE-IDENTITY
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IETF Energy Management Working Group"
CONTACT-INFO
"WG Email: eman@ietf.org
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/eman
entityMIB MODULE-IDENTITY
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IETF Energy Management Working Group"
CONTACT-INFO
"WG Email: eman@ietf.org
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/eman
Andy Bierman YumaWorks, Inc. 274 Redwood Shores Parkway, #133 Redwood City, CA 94065 USA Phone: +1 408-716-0466 Email: andy@yumaworks.com
Andy Bierman YumaWorks，Inc.美国加利福尼亚州红木城133号红木海岸公园路274号电话：+1 408-716-0466电子邮件：andy@yumaworks.com
Dan Romascanu Avaya Park Atidim, Bldg. #3 Tel Aviv, 61581 Israel Phone: +972-3-6458414 Email: dromasca@avaya.com
Dan Romascanu Avaya Park Atidim，特拉维夫3号楼，61581以色列电话：+972-3-6458414电子邮件：dromasca@avaya.com
Juergen Quittek NEC Europe Ltd. Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany Phone: +49 6221 4342-115 Email: quittek@neclab.eu
Juergen Quittek NEC欧洲有限公司网络研究部Kurfuersten Anlage 36 Heidelberg 69115德国电话：+49 6221 4342-115电子邮件：quittek@neclab.eu
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 "The MIB module for representing multiple logical entities supported by a single SNMP agent.
DESCRIPTION“用于表示单个SNMP代理支持的多个逻辑实体的MIB模块。
Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2013 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)."
REVISION "201304050000Z" -- April 5, 2013
修订版“201304050000Z”-2013年4月5日
DESCRIPTION "Entity MIB (Version 4). This revision obsoletes RFC 4133. - Creation of a new MIB module, IANA-ENTITY-MIB, which makes the PhysicalIndex TC an IANA-maintained TEXTUAL-CONVENTION. IANAPhysicalClass is now imported from the IANA-ENTITY-MIB. - Addition of a new MIB object to the entPhysicalTable, entPhysicalUUID. UUIDorZero is imported from the UUID-TC-MIB. - Addition of two new MODULE-COMPLIANCE modules-entity4Compliance and entity4CRCompliance. This version is published as RFC 6933."
说明“实体MIB（版本4）。此修订版废除了RFC 4133。-创建新的MIB模块，即IANA-ENTITY-MIB，使PhysicalIndex TC成为IANA维护的文本约定。IANAPhysicalClass现在从IANA-ENTITY-MIB导入。-将新MIB对象添加到entPhysicalTable，entPhysicalUUID。UUIDRZero从UUID-TC-MIB导入。-添加两个新模块—符合性模块—entity4Compliance和entity4CRCompliance。此版本发布为RFC 6933。”
REVISION "200508100000Z" DESCRIPTION "Initial Version of Entity MIB (Version 3). This revision obsoletes RFC 2737. Additions: - cpu(12) enumeration added to IANAPhysicalClass TC - DISPLAY-HINT clause to PhysicalIndex TC - PhysicalIndexOrZero TC - entPhysicalMfgDate object - entPhysicalUris object Changes: - entPhysicalContainedIn SYNTAX changed from INTEGER to PhysicalIndexOrZero
修订版“200508100000Z”说明“实体MIB初始版本（第3版）。此修订版淘汰RFC 2737。增补：-cpu（12）枚举添加到PhysicalIndex TC-PhysicalIndexOrZero TC-EntPhysicalFGDate对象-entPhysicalUris对象更改的IANAPhysicalClass TC-DISPLAY-HINT子句中：-entPhysicalContainedIn语法从整数更改为PhysicalIndexOrZero
This version was published as RFC 4133."
此版本作为RFC 4133发布。”
REVISION "199912070000Z" DESCRIPTION "Initial Version of Entity MIB (Version 2). This revision obsoletes RFC 2037. This version was published as RFC 2737."
修订版“1999120700NZ”说明“实体MIB的初始版本（第2版）。此修订版淘汰RFC 2037。此版本发布为RFC 2737。”
REVISION "199610310000Z"
DESCRIPTION
"Initial version (version 1), published as
RFC 2037."
::= { mib-2 47 }
REVISION "199610310000Z"
DESCRIPTION
"Initial version (version 1), published as
RFC 2037."
::= { mib-2 47 }
entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
-- MIB contains four groups
entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
-- MIB contains four groups
entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
-- Textual Conventions
PhysicalIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An arbitrary value that uniquely identifies the physical
entity. The value should be a small positive integer.
Index values for different physical entities are not
necessarily contiguous."
SYNTAX Integer32 (1..2147483647)
-- Textual Conventions
PhysicalIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An arbitrary value that uniquely identifies the physical
entity. The value should be a small positive integer.
Index values for different physical entities are not
necessarily contiguous."
SYNTAX Integer32 (1..2147483647)
PhysicalIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This TEXTUAL-CONVENTION is an extension of the
PhysicalIndex convention, which defines a greater than zero
value used to identify a physical entity. 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)
PhysicalIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This TEXTUAL-CONVENTION is an extension of the
PhysicalIndex convention, which defines a greater than zero
value used to identify a physical entity. 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)
SnmpEngineIdOrNone ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A specially formatted SnmpEngineID string for use with the
Entity MIB.
SnmpEngineIdOrNone ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A specially formatted SnmpEngineID string for use with the
Entity MIB.
If an instance of an object of SYNTAX SnmpEngineIdOrNone has a non-zero length, then the object encoding and semantics are defined by the SnmpEngineID TEXTUAL-CONVENTION (see STD 62, RFC 3411).
如果语法为SnmpEngineIdOrNone的对象实例具有非零长度，则对象编码和语义由SnmpEngineID文本约定定义（参见STD 62，RFC 3411）。
If an instance of an object of SYNTAX SnmpEngineIdOrNone contains a zero-length string, then no appropriate SnmpEngineID is associated with the logical entity (i.e., SNMPv3 is not supported)." SYNTAX OCTET STRING (SIZE(0..32)) -- empty string or SnmpEngineID
如果语法为SnmpEngineIdOrNone的对象实例包含长度为零的字符串，则没有适当的SnmpEngineID与逻辑实体相关联（即不支持SNMPv3）。“语法八位组字符串（大小（0..32））--空字符串或SnmpEngineID
PhysicalClass ::= TEXTUAL-CONVENTION
STATUS deprecated
DESCRIPTION
"Starting with version 4 of the ENTITY-MIB, this TC is
deprecated, and the usage of the IANAPhysicalClass TC from
the IANA-ENTITY-MIB is recommended instead.
PhysicalClass ::= TEXTUAL-CONVENTION
STATUS deprecated
DESCRIPTION
"Starting with version 4 of the ENTITY-MIB, this TC is
deprecated, and the usage of the IANAPhysicalClass TC from
the IANA-ENTITY-MIB is recommended instead.
An enumerated value that provides an indication of the general hardware type of a particular physical entity. There are no restrictions as to the number of entPhysicalEntries of each entPhysicalClass, which must be instantiated by an agent.
一种枚举值，用于指示特定物理实体的通用硬件类型。每个entPhysicalClass的entPhysicalEntries数量没有限制，必须由代理实例化。
The enumeration 'other' is applicable if the physical entity class is known but does not match any of the supported values.
如果物理实体类已知但与任何支持的值都不匹配，则枚举“other”适用。
The enumeration 'unknown' is applicable if the physical entity class is unknown to the agent.
如果代理未知物理实体类，则枚举“未知”适用。
The enumeration 'chassis' is applicable if the physical entity class is an overall container for networking equipment. Any class of physical entity, except a stack, may be contained within a chassis; a chassis may only be contained within a stack.
如果物理实体类是网络设备的总体容器，则枚举“机箱”适用。任何类别的物理实体（堆栈除外）都可以包含在机箱中；机箱只能包含在堆栈中。
The enumeration 'backplane' is applicable if the physical entity class is some sort of device for aggregating and forwarding networking traffic, such as a shared backplane in a modular ethernet switch. Note that an agent may model a backplane as a single physical entity, which is actually implemented as multiple discrete physical components (within a chassis or stack).
如果物理实体类是用于聚合和转发网络流量的某种设备，例如模块化以太网交换机中的共享背板，则枚举“背板”适用。请注意，代理可以将背板建模为单个物理实体，实际实现为多个离散物理组件（在机箱或堆栈中）。
The enumeration 'container' is applicable if the physical entity class is capable of containing one or more removable physical entities, possibly of different types. For example, each (empty or full) slot in a chassis will be modeled as a container. Note that all removable physical entities should be modeled within a container entity, such
如果物理实体类能够包含一个或多个可移动物理实体（可能是不同类型的），则枚举“容器”适用。例如，机箱中的每个（空或满）插槽都将建模为一个容器。请注意，所有可移动物理实体都应在容器实体内建模，例如
as field-replaceable modules, fans, or power supplies. Note that all known containers should be modeled by the agent, including empty containers.
作为现场可更换模块、风扇或电源。请注意，所有已知容器都应由代理建模，包括空容器。
The enumeration 'powerSupply' is applicable if the physical entity class is a power-supplying component.
如果物理实体类是电源供应组件，则枚举“powerSupply”适用。
The enumeration 'fan' is applicable if the physical entity class is a fan or other heat-reduction component.
如果物理实体类是风扇或其他散热组件，则枚举“风扇”适用。
The enumeration 'sensor' is applicable if the physical entity class is some sort of sensor, such as a temperature sensor within a router chassis.
如果物理实体类是某种传感器，例如路由器机箱内的温度传感器，则枚举“传感器”适用。
The enumeration 'module' is applicable if the physical entity class is some sort of self-contained sub-system. If the enumeration 'module' is removable, then it should be modeled within a container entity; otherwise, it should be modeled directly within another physical entity (e.g., a chassis or another module).
如果物理实体类是某种自包含子系统，则枚举“模块”适用。如果枚举“模块”是可移动的，那么它应该在容器实体中建模；否则，应直接在另一个物理实体（例如机箱或另一个模块）内对其进行建模。
The enumeration 'port' is applicable if the physical entity class is some sort of networking port capable of receiving and/or transmitting networking traffic.
如果物理实体类是某种能够接收和/或发送网络流量的网络端口，则枚举“端口”适用。
The enumeration 'stack' is applicable if the physical entity class is some sort of super-container (possibly virtual) intended to group together multiple chassis entities. A stack may be realized by a 'virtual' cable, a real interconnect cable, attached to multiple chassis, or may in fact be comprised of multiple interconnect cables. A stack should not be modeled within any other physical entities, but a stack may be contained within another stack. Only chassis entities should be contained within a stack.
如果物理实体类是某种超级容器（可能是虚拟的），用于将多个机箱实体组合在一起，则枚举“堆栈”适用。堆栈可以通过连接到多个机箱的“虚拟”电缆、真实互连电缆实现，或者实际上可以由多个互连电缆组成。堆栈不应在任何其他物理实体中建模，但堆栈可能包含在另一个堆栈中。堆栈中只应包含机箱实体。
The enumeration 'cpu' is applicable if the physical entity class is some sort of central processing unit." SYNTAX INTEGER { other(1), unknown(2), chassis(3), backplane(4), container(5), -- e.g., chassis slot or daughter-card holder powerSupply(6), fan(7), sensor(8), module(9), -- e.g., plug-in card or daughter-card port(10),
枚举“cpu”适用于物理实体类是某种中央处理单元的情况。“语法整数{其他（1）、未知（2）、机箱（3）、背板（4）、容器（5），--例如机箱插槽或子卡支架电源（6）、风扇（7）、传感器（8）、模块（9），--例如插件卡或子卡端口（10），
stack(11), -- e.g., stack of multiple chassis entities cpu(12) }
堆栈（11）——例如，多个机箱实体的堆栈cpu（12）}
-- The Physical Entity Table
entPhysicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains one row per physical entity. There is
always at least one row for an 'overall' physical entity."
::= { entityPhysical 1 }
-- The Physical Entity Table
entPhysicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains one row per physical entity. There is
always at least one row for an 'overall' physical entity."
::= { entityPhysical 1 }
entPhysicalEntry OBJECT-TYPE SYNTAX EntPhysicalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular physical entity.
entPhysicalEntry对象类型语法entPhysicalEntry MAX-ACCESS不可访问状态当前描述“有关特定物理实体的信息。
Each entry provides objects (entPhysicalDescr,
entPhysicalVendorType, and entPhysicalClass) to help an NMS
identify and characterize the entry and objects
(entPhysicalContainedIn and entPhysicalParentRelPos) to help
an NMS relate the particular entry to other entries in this
table."
INDEX { entPhysicalIndex }
::= { entPhysicalTable 1 }
Each entry provides objects (entPhysicalDescr,
entPhysicalVendorType, and entPhysicalClass) to help an NMS
identify and characterize the entry and objects
(entPhysicalContainedIn and entPhysicalParentRelPos) to help
an NMS relate the particular entry to other entries in this
table."
INDEX { entPhysicalIndex }
::= { entPhysicalTable 1 }
EntPhysicalEntry ::= SEQUENCE {
entPhysicalIndex PhysicalIndex,
entPhysicalDescr SnmpAdminString,
entPhysicalVendorType AutonomousType,
entPhysicalContainedIn PhysicalIndexOrZero,
entPhysicalClass IANAPhysicalClass,
entPhysicalParentRelPos Integer32,
entPhysicalName SnmpAdminString,
entPhysicalHardwareRev SnmpAdminString,
entPhysicalFirmwareRev SnmpAdminString,
entPhysicalSoftwareRev SnmpAdminString,
entPhysicalSerialNum SnmpAdminString,
entPhysicalMfgName SnmpAdminString,
entPhysicalModelName SnmpAdminString,
entPhysicalAlias SnmpAdminString,
entPhysicalAssetID SnmpAdminString,
entPhysicalIsFRU TruthValue,
EntPhysicalEntry ::= SEQUENCE {
entPhysicalIndex PhysicalIndex,
entPhysicalDescr SnmpAdminString,
entPhysicalVendorType AutonomousType,
entPhysicalContainedIn PhysicalIndexOrZero,
entPhysicalClass IANAPhysicalClass,
entPhysicalParentRelPos Integer32,
entPhysicalName SnmpAdminString,
entPhysicalHardwareRev SnmpAdminString,
entPhysicalFirmwareRev SnmpAdminString,
entPhysicalSoftwareRev SnmpAdminString,
entPhysicalSerialNum SnmpAdminString,
entPhysicalMfgName SnmpAdminString,
entPhysicalModelName SnmpAdminString,
entPhysicalAlias SnmpAdminString,
entPhysicalAssetID SnmpAdminString,
entPhysicalIsFRU TruthValue,
entPhysicalMfgDate DateAndTime, entPhysicalUris OCTET STRING, entPhysicalUUID UUIDorZero
EntPhysicalFGDate日期和时间，EntPhysicalURI八位字节字符串，entPhysicalUUID UUIDRZero
}
}
entPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index for this entry."
::= { entPhysicalEntry 1 }
entPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index for this entry."
::= { entPhysicalEntry 1 }
entPhysicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of physical entity. This object
should contain a string that identifies the manufacturer's
name for the physical entity and should be set to a
distinct value for each version or model of the physical
entity."
::= { entPhysicalEntry 2 }
entPhysicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of physical entity. This object
should contain a string that identifies the manufacturer's
name for the physical entity and should be set to a
distinct value for each version or model of the physical
entity."
::= { entPhysicalEntry 2 }
entPhysicalVendorType OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID.
entPhysicalVendorType对象类型语法AutonomousType MAX-ACCESS只读状态当前描述“物理实体的供应商特定硬件类型的指示。请注意，这与MIB-II的sysObjectID的定义不同。
An agent should set this object to an enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device.
代理应将此对象设置为企业特定的注册标识符值，以详细指示特定的设备类型。entPhysicalClass的关联实例用于指示硬件设备的常规类型。
If no vendor-specific registration identifier exists for
this physical entity, or the value is unknown by this agent,
then the value { 0 0 } is returned."
::= { entPhysicalEntry 3 }
If no vendor-specific registration identifier exists for
this physical entity, or the value is unknown by this agent,
then the value { 0 0 } is returned."
::= { entPhysicalEntry 3 }
entPhysicalContainedIn OBJECT-TYPE SYNTAX PhysicalIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "The value of entPhysicalIndex for the physical entity that 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed.
entPhysicalContainedIn对象类型语法PhysicalIndexOrZero MAX-ACCESS只读状态当前说明“包含此物理实体的物理实体的entPhysicalIndex值。值为零表示此物理实体不包含在任何其他物理实体中。请注意，“包含”关系集定义了严格的层次结构；也就是说，不允许递归。
In the event that a physical entity is contained by more
than one physical entity (e.g., double-wide modules), this
object should identify the containing entity with the lowest
value of entPhysicalIndex."
::= { entPhysicalEntry 4 }
In the event that a physical entity is contained by more
than one physical entity (e.g., double-wide modules), this
object should identify the containing entity with the lowest
value of entPhysicalIndex."
::= { entPhysicalEntry 4 }
entPhysicalClass OBJECT-TYPE SYNTAX IANAPhysicalClass MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of the general hardware type of the physical entity.
entPhysicalClass对象类型语法IANAPhysicalClass MAX-ACCESS只读状态当前描述“物理实体的常规硬件类型指示。
An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one entity.
代理应将此对象设置为标准枚举值，该值最准确地指示物理实体的常规类，如果有多个实体，则设置为主类。
If no appropriate standard registration identifier exists
for this physical entity, then the value 'other(1)' is
returned. If the value is unknown by this agent, then the
value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 }
If no appropriate standard registration identifier exists
for this physical entity, then the value 'other(1)' is
returned. If the value is unknown by this agent, then the
value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 }
entPhysicalParentRelPos OBJECT-TYPE SYNTAX Integer32 (-1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.
entPhysicalParentRelPos对象类型语法整数32（-1..2147483647）最大访问只读状态当前说明“该‘子’组件在其所有‘兄弟’组件中的相对位置指示。同级组件定义为entPhysicalEntries，它们共享每个entPhysicalContainedIn和entPhysicalClass对象的相同实例值。
An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the entPhysicalContainedIn instance in each sibling entry).
NMS可以使用此对象标识特定父级的所有同级组件的相对顺序（由每个同级条目中的entPhysicalContainedIn实例标识）。
If possible, this value should match any external labeling of the physical component. For example, for a container (e.g., card slot) labeled as 'slot #3', entPhysicalParentRelPos should have the value '3'. Note that the entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of '1'.
如果可能，此值应与物理组件的任何外部标签匹配。例如，对于标记为“插槽#3”的容器（例如卡插槽），entPhysicalParentRelPos的值应为“3”。请注意，插槽3中插入的模块的entPhysicalEntry的entPhysicalParentRelPos值应为“1”。
If the physical position of this component does not match any external numbering or clearly visible ordering, then user documentation or other external reference material should be used to determine the parent-relative position. If this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of 'sibling' components, perhaps based on internal representation of the components.
如果该组件的物理位置与任何外部编号或清晰可见的顺序不匹配，则应使用用户文档或其他外部参考资料来确定父相对位置。如果这是不可能的，那么代理应该为给定的一组“同级”组件分配一致（但可能是任意的）顺序，可能是基于组件的内部表示。
If the agent cannot determine the parent-relative position for some reason, or if the associated value of entPhysicalContainedIn is '0', then the value '-1' is returned. Otherwise, a non-negative integer is returned, indicating the parent-relative position of this physical entity.
如果代理由于某种原因无法确定父级相对位置，或者如果entPhysicalContainedIn的关联值为“0”，则返回值“-1”。否则，将返回一个非负整数，指示此物理实体的父级相对位置。
Parent-relative ordering normally starts from '1' and continues to 'N', where 'N' represents the highest positioned child entity. However, if the physical entities (e.g., slots) are labeled from a starting position of zero, then the first sibling should be associated with an entPhysicalParentRelPos value of '0'. Note that this ordering may be sparse or dense, depending on agent implementation.
父相对顺序通常从“1”开始，继续到“N”，其中“N”表示位置最高的子实体。但是，如果物理实体（例如插槽）从零开始标记，则第一个同级应与entPhysicalParentRelPos值“0”关联。请注意，这种排序可能是稀疏的，也可能是密集的，这取决于代理实现。
The actual values returned are not globally meaningful, as each 'parent' component may use different numbering algorithms. The ordering is only meaningful among siblings of the same parent component.
返回的实际值没有全局意义，因为每个“父”组件可能使用不同的编号算法。排序仅在同一父组件的同级之间有意义。
The agent should retain parent-relative position values
across reboots, either through algorithmic assignment or use
of non-volatile storage."
::= { entPhysicalEntry 6 }
The agent should retain parent-relative position values
across reboots, either through algorithmic assignment or use
of non-volatile storage."
::= { entPhysicalEntry 6 }
entPhysicalName OBJECT-TYPE
entPhysicalName对象类型
SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device.
语法SNMPAdministring MAX-ACCESS只读状态当前描述“物理实体的文本名称。此对象的值应为本地设备分配的组件名称，并且应适合在设备的“控制台”输入的命令中使用。这可能是文本名称（例如，“控制台”）或简单的组件编号（例如，端口或模块编号，如“1”），具体取决于设备的物理组件命名语法。
If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string.
如果没有本地名称，或者如果此对象不适用，则此对象包含长度为零的字符串。
Note that the value of entPhysicalName for two physical
entities will be the same in the event that the console
interface does not distinguish between them, e.g., slot-1
and the card in slot-1."
::= { entPhysicalEntry 7 }
Note that the value of entPhysicalName for two physical
entities will be the same in the event that the console
interface does not distinguish between them, e.g., slot-1
and the card in slot-1."
::= { entPhysicalEntry 7 }
entPhysicalHardwareRev OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present).
entPhysicalHardwareRev对象类型语法SNMPAdministring MAX-ACCESS只读状态当前描述“物理实体的供应商特定硬件修订字符串。首选值是实际打印在组件本身上的硬件修订标识符（如果存在）。
Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner.
请注意，如果版本信息以不可打印（例如二进制）格式存储在内部，则代理必须以特定于实现的方式将此类信息转换为可打印格式。
If no specific hardware revision string is associated with
the physical component, or if this information is unknown to
the agent, then this object will contain a zero-length
string."
::= { entPhysicalEntry 8 }
If no specific hardware revision string is associated with
the physical component, or if this information is unknown to
the agent, then this object will contain a zero-length
string."
::= { entPhysicalEntry 8 }
entPhysicalFirmwareRev OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current
entPhysicalFirmwareRev对象类型语法SNMPAdministring MAX-ACCESS只读状态当前
DESCRIPTION "The vendor-specific firmware revision string for the physical entity.
DESCRIPTION“物理实体的供应商特定固件版本字符串。
Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner.
请注意，如果版本信息以不可打印（例如二进制）格式存储在内部，则代理必须以特定于实现的方式将此类信息转换为可打印格式。
If no specific firmware programs are associated with the
physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 9 }
If no specific firmware programs are associated with the
physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 9 }
entPhysicalSoftwareRev OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The vendor-specific software revision string for the physical entity.
entPhysicalSoftwareRev对象类型语法SNMPAdministring MAX-ACCESS只读状态当前描述“物理实体的供应商特定软件版本字符串。
Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner.
请注意，如果版本信息以不可打印（例如二进制）格式存储在内部，则代理必须以特定于实现的方式将此类信息转换为可打印格式。
If no specific software programs are associated with the
physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 10 }
If no specific software programs are associated with the
physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 10 }
entPhysicalSerialNum OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present).
entPhysicalSerialNum对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS读写状态当前描述“物理实体的供应商特定序列号字符串。首选值是组件本身上实际打印的序列号字符串（如果存在）。
On the first instantiation of a physical entity, the value of entPhysicalSerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the entPhysicalSerialNum will be set to a zero-length string instead.
On the first instantiation of a physical entity, the value of entPhysicalSerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the entPhysicalSerialNum will be set to a zero-length string instead.translate error, please retry
Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object. Agents that cannot provide non-volatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object.
请注意，能够正确识别所有已安装物理实体的序列号的实现不需要提供对entPhysicalSerialNum对象的写入访问。无法为entPhysicalSerialNum字符串提供非易失性存储的代理不需要实现对此对象的写访问。
Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique serial numbers. An agent does not have to provide write access for such entities and may return a zero-length string.
并非每个物理组件都有序列号，甚至不需要序列号。entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体（例如，中继器模块内的中继器端口）不需要自己的唯一序列号。代理不必为这些实体提供写访问，并且可以返回零长度字符串。
If write access is implemented for an instance of
entPhysicalSerialNum and a value is written into the
instance, the agent must retain the supplied value in the
entPhysicalSerialNum 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 network management system,
including those resulting in a change of the physical
entity's entPhysicalIndex value."
::= { entPhysicalEntry 11 }
If write access is implemented for an instance of
entPhysicalSerialNum and a value is written into the
instance, the agent must retain the supplied value in the
entPhysicalSerialNum 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 network management system,
including those resulting in a change of the physical
entity's entPhysicalIndex value."
::= { entPhysicalEntry 11 }
entPhysicalMfgName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present).
EntPhysicalFGName对象类型语法SNMPAdministring MAX-ACCESS只读状态当前描述“此物理组件的制造商名称。首选值是组件本身上实际打印的制造商名称字符串（如果存在）。
Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects are only meaningful amongst entPhysicalEntries with the same value of entPhysicalMfgName.
请注意，entPhysicalModelName、entPhysicalFirmwareRev、entPhysicalSoftwareRev和entPhysicalSerialNum对象实例之间的比较仅在具有相同EntPhysicalFGName值的EntPhysicalEntry之间有意义。
If the manufacturer name string associated with the physical
component is unknown to the agent, then this object will
contain a zero-length string."
::= { entPhysicalEntry 12 }
If the manufacturer name string associated with the physical
component is unknown to the agent, then this object will
contain a zero-length string."
::= { entPhysicalEntry 12 }
entPhysicalModelName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself.
entPhysicalModelName对象类型语法SNMPAdministring MAX-ACCESS只读状态当前描述“与此物理组件关联的供应商特定型号名称标识符字符串。首选值是客户可见的零件号，可以打印在组件本身上。
If the model name string associated with the physical
component is unknown to the agent, then this object will
contain a zero-length string."
::= { entPhysicalEntry 13 }
If the model name string associated with the physical
component is unknown to the agent, then this object will
contain a zero-length string."
::= { entPhysicalEntry 13 }
entPhysicalAlias OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "This object is an 'alias' name for the physical entity, as specified by a network manager, and provides a non-volatile 'handle' for the physical entity.
entPhysicalAlias对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS读写状态当前描述“此对象是网络管理器指定的物理实体的“别名”，并为物理实体提供非易失性的“句柄”。
On the first instantiation of a physical entity, the value of entPhysicalAlias associated with that entity is set to the zero-length string. However, the agent may set the value to a locally unique default value, instead of a zero-length string.
在物理实体的第一次实例化时，与该实体关联的entPhysicalAlias的值设置为零长度字符串。但是，代理可以将该值设置为本地唯一的默认值，而不是长度为零的字符串。
If write access is implemented for an instance of
entPhysicalAlias and a value is written into the instance,
the agent must retain the supplied value in the
entPhysicalAlias 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 network management system,
including those resulting in a change of the physical
entity's entPhysicalIndex value."
::= { entPhysicalEntry 14 }
If write access is implemented for an instance of
entPhysicalAlias and a value is written into the instance,
the agent must retain the supplied value in the
entPhysicalAlias 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 network management system,
including those resulting in a change of the physical
entity's entPhysicalIndex value."
::= { entPhysicalEntry 14 }
entPhysicalAssetID OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current
entPhysicalAssetID对象类型语法SnmpAdminString（大小（0..32））最大访问读写状态当前
DESCRIPTION "This object is a user-assigned asset tracking identifier (as specified by a network manager) for the physical entity and provides non-volatile storage of this information.
描述“此对象是用户为物理实体分配的资产跟踪标识符（由网络管理器指定），并提供此信息的非易失性存储。
On the first instantiation of a physical entity, the value of entPhysicalAssetID associated with that entity is set to the zero-length string.
在物理实体的第一次实例化时，与该实体关联的entPhysicalAssetID的值设置为零长度字符串。
Not every physical component will have an asset tracking identifier or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities and may instead return a zero-length string.
并非每个物理组件都有资产跟踪标识符，甚至不需要。entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体（例如，中继器模块中的中继器端口）不需要自己的唯一资产跟踪标识符。代理不必为这些实体提供写访问，而是可以返回长度为零的字符串。
If write access is implemented for an instance of entPhysicalAssetID and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAssetID 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 network management system, including those resulting in a change of the physical entity's entPhysicalIndex value.
如果对entPhysicalAssetID实例实现了写访问，并且向该实例中写入了一个值，则代理必须在entPhysicalAssetID实例（与同一物理实体关联）中保留提供的值，只要该实体保持实例化状态。这包括网络管理系统的所有重新初始化/重新启动的实例化，包括导致物理实体的entPhysicalIndex值发生更改的实例化。
If no asset tracking information is associated with the
physical component, then this object will contain a
zero-length string."
::= { entPhysicalEntry 15 }
If no asset tracking information is associated with the
physical component, then this object will contain a
zero-length string."
::= { entPhysicalEntry 15 }
entPhysicalIsFRU OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this physical entity
is considered a 'field replaceable unit' by the vendor.
If this object contains the value 'true(1)', then this
entPhysicalEntry identifies a field replaceable unit. For
all entPhysicalEntries that represent components
permanently contained within a field replaceable unit, the
value 'false(2)' should be returned for this object."
::= { entPhysicalEntry 16 }
entPhysicalIsFRU OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this physical entity
is considered a 'field replaceable unit' by the vendor.
If this object contains the value 'true(1)', then this
entPhysicalEntry identifies a field replaceable unit. For
all entPhysicalEntries that represent components
permanently contained within a field replaceable unit, the
value 'false(2)' should be returned for this object."
::= { entPhysicalEntry 16 }
entPhysicalMfgDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the date of manufacturing of the
managed entity. If the manufacturing date is unknown or
not supported, the object is not instantiated. The special
value '0000000000000000'H may also be returned in this
case."
::= { entPhysicalEntry 17 }
entPhysicalMfgDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the date of manufacturing of the
managed entity. If the manufacturing date is unknown or
not supported, the object is not instantiated. The special
value '0000000000000000'H may also be returned in this
case."
::= { entPhysicalEntry 17 }
entPhysicalUris OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS current DESCRIPTION "This object contains identification information about the physical entity. The object contains URIs; therefore, the syntax of this object must conform to RFC 3986, Section 3.
EntPhysicalURI对象类型语法八位字符串MAX-ACCESS读写状态当前描述“此对象包含有关物理实体的标识信息。此对象包含URI；因此，此对象的语法必须符合RFC 3986第3节的要求。
Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored.
Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored.translate error, please retry
If no URI identification information is known about the physical entity, the object is not instantiated. A zero-length octet string may also be returned in this case." REFERENCE "RFC 3986, Uniform Resource Identifiers (URI): Generic Syntax, Section 2, August 1998."
如果不知道有关物理实体的URI标识信息，则不会实例化该对象。在这种情况下，也可以返回零长度的八位字节字符串。“参考”RFC 3986，统一资源标识符（URI）：通用语法，第2节，1998年8月
::= { entPhysicalEntry 18 }
::= { entPhysicalEntry 18 }
entPhysicalUUID OBJECT-TYPE SYNTAX UUIDorZero MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains identification information about the physical entity. The object contains a Universally Unique Identifier, the syntax of this object must conform to RFC 4122, Section 4.1.
entPhysicalUUID对象类型语法UUIDorZero MAX-ACCESS只读状态当前描述“此对象包含有关物理实体的标识信息。此对象包含通用唯一标识符，此对象的语法必须符合RFC 4122第4.1节的要求。
A zero-length octet string is returned if no UUID information is known."
如果不知道UUID信息，则返回长度为零的八位字节字符串。”
REFERENCE "RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace, Section 4.1, July 2005."
参考“RFC 4122，通用唯一标识符（UUID）URN命名空间，第4.1节，2005年7月。”
::= { entPhysicalEntry 19 }
::= { entPhysicalEntry 19 }
-- The Logical Entity Table
entLogicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLogicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains one row per logical entity. For agents
that implement more than one naming scope, at least one
entry must exist. Agents that instantiate all MIB objects
within a single naming scope are not required to implement
this table."
::= { entityLogical 1 }
-- The Logical Entity Table
entLogicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLogicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains one row per logical entity. For agents
that implement more than one naming scope, at least one
entry must exist. Agents that instantiate all MIB objects
within a single naming scope are not required to implement
this table."
::= { entityLogical 1 }
entLogicalEntry OBJECT-TYPE
SYNTAX EntLogicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular logical entity. Entities
may be managed by this agent or other SNMP agents (possibly)
in the same chassis."
INDEX { entLogicalIndex }
::= { entLogicalTable 1 }
entLogicalEntry OBJECT-TYPE
SYNTAX EntLogicalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular logical entity. Entities
may be managed by this agent or other SNMP agents (possibly)
in the same chassis."
INDEX { entLogicalIndex }
::= { entLogicalTable 1 }
EntLogicalEntry ::= SEQUENCE {
entLogicalIndex Integer32,
entLogicalDescr SnmpAdminString,
entLogicalType AutonomousType,
entLogicalCommunity OCTET STRING,
entLogicalTAddress TAddress,
entLogicalTDomain TDomain,
entLogicalContextEngineID SnmpEngineIdOrNone,
entLogicalContextName SnmpAdminString
}
EntLogicalEntry ::= SEQUENCE {
entLogicalIndex Integer32,
entLogicalDescr SnmpAdminString,
entLogicalType AutonomousType,
entLogicalCommunity OCTET STRING,
entLogicalTAddress TAddress,
entLogicalTDomain TDomain,
entLogicalContextEngineID SnmpEngineIdOrNone,
entLogicalContextName SnmpAdminString
}
entLogicalIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current
entLogicalIndex对象类型语法整数32（1..2147483647）MAX-ACCESS不可访问状态当前
DESCRIPTION
"The value of this object uniquely identifies the logical
entity. The value should be a small positive integer; index
values for different logical entities are not necessarily
contiguous."
::= { entLogicalEntry 1 }
DESCRIPTION
"The value of this object uniquely identifies the logical
entity. The value should be a small positive integer; index
values for different logical entities are not necessarily
contiguous."
::= { entLogicalEntry 1 }
entLogicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the logical entity. This object
should contain a string that identifies the manufacturer's
name for the logical entity and should be set to a distinct
value for each version of the logical entity."
::= { entLogicalEntry 2 }
entLogicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the logical entity. This object
should contain a string that identifies the manufacturer's
name for the logical entity and should be set to a distinct
value for each version of the logical entity."
::= { entLogicalEntry 2 }
entLogicalType OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the type of logical entity. This will
typically be the OBJECT IDENTIFIER name of the node in the
SMI's naming hierarchy that represents the major MIB
module, or the majority of the MIB modules, supported by the
logical entity. For example:
a logical entity of a regular host/router -> mib-2
a logical entity of a 802.1d bridge -> dot1dBridge
a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
If an appropriate node in the SMI's naming hierarchy cannot
be identified, the value 'mib-2' should be used."
::= { entLogicalEntry 3 }
entLogicalType OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the type of logical entity. This will
typically be the OBJECT IDENTIFIER name of the node in the
SMI's naming hierarchy that represents the major MIB
module, or the majority of the MIB modules, supported by the
logical entity. For example:
a logical entity of a regular host/router -> mib-2
a logical entity of a 802.1d bridge -> dot1dBridge
a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
If an appropriate node in the SMI's naming hierarchy cannot
be identified, the value 'mib-2' should be used."
::= { entLogicalEntry 3 }
entLogicalCommunity OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..255)) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a
entLogicalCommunity对象类型语法八位字节字符串（大小（0..255））MAX-ACCESS只读状态不推荐的说明“SNMPv1或SNMPv2c社区字符串，可用于访问此逻辑实体的详细管理信息。代理应允许使用此社区字符串进行读取访问（所有托管对象的适当子集）并可能根据用于读取此对象的请求权限返回社区字符串。请注意，代理可能返回具有只读权限的社区字符串，即使使用
read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object.
读写社区字符串。但是，代理必须注意不要返回比用于访问此对象的社区字符串具有更多权限的社区字符串。
A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'.
兼容的SNMP代理可能希望通过在单个“默认”命名范围中表示多个逻辑实体来保留命名范围。当由entLogicalCommunity的相同值表示的逻辑实体没有共同的对象实例时，这是可能的。例如，“bridge1”和“repeater1”可能是主命名范围的一部分，但至少需要一个额外的社区字符串来表示“bridge2”和“repeater2”。
Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope.
逻辑实体“bridge1”和“repeater1”将由与“默认”命名范围关联的sysOREntries表示。
For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request.
对于无法通过SNMPv1或SNMPv2c访问的代理，此对象的值为空字符串。如果代理尚未分配社区字符串，或者无法为特定SNMP请求返回具有适当访问权限的社区字符串，则此对象还可能包含空字符串。
Note that this object is deprecated. Agents that implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object or may continue
to return a community string (e.g., tri-lingual agent
support)."
::= { entLogicalEntry 4 }
Note that this object is deprecated. Agents that implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object or may continue
to return a community string (e.g., tri-lingual agent
support)."
::= { entLogicalEntry 4 }
entLogicalTAddress OBJECT-TYPE SYNTAX TAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The transport service address by which the logical entity receives network management traffic, formatted according to the corresponding value of entLogicalTDomain.
EntLogicalAddress对象类型语法TadAddress MAX-ACCESS只读状态当前描述“逻辑实体接收网络管理通信的传输服务地址，根据EntLogicalDomain的相应值格式化。
For snmpUDPDomain, a TAddress is 6 octets long: the initial 4 octets contain the IP-address in network-byte order, and the last 2 contain the UDP port in network-byte order. Consult RFC 3417 for further information on snmpUDPDomain."
对于snmpUDPDomain，地址长度为6个八位字节：最初的4个八位字节包含网络字节顺序的IP地址，最后2个八位字节包含网络字节顺序的UDP端口。有关snmpUDPDomain的更多信息，请咨询RFC 3417。”
REFERENCE
"Transport Mappings for the Simple Network Management
Protocol (SNMP), STD 62, RFC 3417."
::= { entLogicalEntry 5 }
REFERENCE
"Transport Mappings for the Simple Network Management
Protocol (SNMP), STD 62, RFC 3417."
::= { entLogicalEntry 5 }
entLogicalTDomain OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the kind of transport service by which the
logical entity receives network management traffic.
Possible values for this object are presently found in
RFC 3417."
REFERENCE
"Transport Mappings for the Simple Network Management
Protocol (SNMP), STD 62, RFC 3417."
::= { entLogicalEntry 6 }
entLogicalTDomain OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the kind of transport service by which the
logical entity receives network management traffic.
Possible values for this object are presently found in
RFC 3417."
REFERENCE
"Transport Mappings for the Simple Network Management
Protocol (SNMP), STD 62, RFC 3417."
::= { entLogicalEntry 6 }
entLogicalContextEngineID OBJECT-TYPE SYNTAX SnmpEngineIdOrNone MAX-ACCESS read-only STATUS current DESCRIPTION "The authoritative contextEngineID that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair.
entLogicalContextEngineID对象类型语法SnmpEngineIdOrNone MAX-ACCESS只读状态当前描述“可用于将有关此逻辑实体持有的信息的SNMP消息发送到关联的“EntLogicalAddress/EntLogicalDomain”对指定的地址的权威contextEngineID。
This object, together with the associated entLogicalContextName object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair.
此对象与关联的entLogicalContextName对象一起定义与特定逻辑实体关联的上下文，并允许访问由contextEngineID和contextName对标识的SNMP引擎。
If no value has been configured by the agent, a zero-length
string is returned, or the agent may choose not to
instantiate this object at all."
::= { entLogicalEntry 7 }
If no value has been configured by the agent, a zero-length
string is returned, or the agent may choose not to
instantiate this object at all."
::= { entLogicalEntry 7 }
entLogicalContextName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current
entLogicalContextName对象类型语法SNMPAdministring MAX-ACCESS只读状态当前
DESCRIPTION "The contextName that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair.
DESCRIPTION“可用于将有关此逻辑实体持有的信息的SNMP消息发送到关联的“EntLogicalAddress/EntLogicalDomain”对指定的地址的contextName。
This object, together with the associated entLogicalContextEngineID object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair.
此对象与关联的entLogicalContextEngineID对象一起定义与特定逻辑实体关联的上下文，并允许访问由contextEngineID和contextName对标识的SNMP引擎。
If no value has been configured by the agent, a zero-length
string is returned, or the agent may choose not to
instantiate this object at all."
::= { entLogicalEntry 8 }
If no value has been configured by the agent, a zero-length
string is returned, or the agent may choose not to
instantiate this object at all."
::= { entLogicalEntry 8 }
entLPMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF EntLPMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources, which are used to realize that logical entity.
entLPMappingTable ENTRY的EntLPMappingEntry对象类型语法序列MAX-ACCESS不可访问状态当前说明“此表包含零行或多行逻辑实体与物理设备的关联。对于此代理已知的每个逻辑实体，都有零个或多个到物理资源的映射，这些映射用于实现该逻辑实体。
An agent should limit the number and nature of entries in this table such that only meaningful and non-redundant information is returned. For example, in a system that contains a single power supply, mappings between logical entities and the power supply are not useful and should not be included.
代理应限制此表中条目的数量和性质，以便只返回有意义的非冗余信息。例如，在包含单个电源的系统中，逻辑实体和电源之间的映射没有用处，不应包括在内。
Also, only the most appropriate physical component, which is closest to the root of a particular containment tree, should be identified in an entLPMapping entry.
此外，在entLPMapping条目中只应标识最合适的物理组件，它最接近特定容器树的根。
For example, suppose a bridge is realized on a particular module, and all ports on that module are ports on this bridge. A mapping between the bridge and the module would be useful, but additional mappings between the bridge and each of the ports on that module would be redundant (because the entPhysicalContainedIn hierarchy can provide the same information). On the other hand, if more than one bridge were utilizing ports on this module, then mappings between each bridge and the ports it used would be appropriate.
例如，假设在一个特定模块上实现了一个网桥，该模块上的所有端口都是该网桥上的端口。网桥和模块之间的映射很有用，但网桥和该模块上的每个端口之间的其他映射是多余的（因为entPhysicalContainedIn层次结构可以提供相同的信息）。另一方面，如果有多个网桥使用此模块上的端口，则每个网桥与其使用的端口之间的映射是合适的。
Also, in the case of a single backplane repeater, a mapping
for the backplane to the single repeater entity is not
necessary."
::= { entityMapping 1 }
Also, in the case of a single backplane repeater, a mapping
for the backplane to the single repeater entity is not
necessary."
::= { entityMapping 1 }
entLPMappingEntry OBJECT-TYPE
SYNTAX EntLPMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular logical-entity-to-physical-
equipment association. Note that the nature of the
association is not specifically identified in this entry.
It is expected that sufficient information exists in the
MIB modules used to manage a particular logical entity to
infer how physical component information is utilized."
INDEX { entLogicalIndex, entLPPhysicalIndex }
::= { entLPMappingTable 1 }
entLPMappingEntry OBJECT-TYPE
SYNTAX EntLPMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular logical-entity-to-physical-
equipment association. Note that the nature of the
association is not specifically identified in this entry.
It is expected that sufficient information exists in the
MIB modules used to manage a particular logical entity to
infer how physical component information is utilized."
INDEX { entLogicalIndex, entLPPhysicalIndex }
::= { entLPMappingTable 1 }
EntLPMappingEntry ::= SEQUENCE {
entLPPhysicalIndex PhysicalIndex
}
EntLPMappingEntry ::= SEQUENCE {
entLPPhysicalIndex PhysicalIndex
}
entLPPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object identifies the index value of a
particular entPhysicalEntry associated with the indicated
entLogicalEntity."
::= { entLPMappingEntry 1 }
entLPPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object identifies the index value of a
particular entPhysicalEntry associated with the indicated
entLogicalEntity."
::= { entLPMappingEntry 1 }
-- logical entity/component to alias table entAliasMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF EntAliasMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains zero or more rows, representing mappings of logical entities and physical components to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical
--逻辑实体/组件到别名表entAliasMappingTable对象类型EntAliasMappingEntry MAX-ACCESS的语法序列不可访问状态当前描述此表包含零行或多行，表示逻辑实体和物理组件到外部MIB标识符的映射。系统中的每个物理端口可以与到外部标识符的映射相关联，外部标识符本身与特定逻辑端口相关联
entity's naming scope. A 'wildcard' mechanism is provided
to indicate that an identifier is associated with more than
one logical entity."
::= { entityMapping 2 }
entity's naming scope. A 'wildcard' mechanism is provided
to indicate that an identifier is associated with more than
one logical entity."
::= { entityMapping 2 }
entAliasMappingEntry OBJECT-TYPE SYNTAX EntAliasMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular binding between a logical entity/physical component pair and an external identifier. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.)
entAliasMappingEntry对象类型语法entAliasMappingEntry MAX-ACCESS不可访问状态当前描述“有关逻辑实体/物理组件对和外部标识符之间的特定绑定的信息。每个逻辑实体/物理组件对可能与一个别名映射相关联。逻辑实体索引也可用作“通配符”（有关详细信息，请参阅entaliasLogicIndexorZero对象描述子句）
Note that only entPhysicalIndex values that represent
physical ports (i.e., associated entPhysicalClass value is
'port(10)') are permitted to exist in this table."
INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
::= { entAliasMappingTable 1 }
Note that only entPhysicalIndex values that represent
physical ports (i.e., associated entPhysicalClass value is
'port(10)') are permitted to exist in this table."
INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
::= { entAliasMappingTable 1 }
EntAliasMappingEntry ::= SEQUENCE {
entAliasLogicalIndexOrZero Integer32,
entAliasMappingIdentifier RowPointer
}
EntAliasMappingEntry ::= SEQUENCE {
entAliasLogicalIndexOrZero Integer32,
entAliasMappingIdentifier RowPointer
}
entAliasLogicalIndexOrZero OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the logical entity that defines the naming scope for the associated instance of the entAliasMappingIdentifier object.
EntaliasLogicIndexorZero对象类型语法整数32（0..2147483647）MAX-ACCESS不可访问状态当前描述“此对象的值标识定义entAliasMappingIdentifier对象关联实例命名范围的逻辑实体。
If this object has a non-zero value, then it identifies the logical entity named by the same value of entLogicalIndex.
如果此对象具有非零值，则它标识由entLogicalIndex的相同值命名的逻辑实体。
If this object has a value of zero, then the mapping between the physical component and the alias identifier for this entAliasMapping entry is associated with all unspecified logical entities. That is, a value of zero (the default mapping) identifies any logical entity that does not have an explicit entry in this table for a particular entPhysicalIndex/entAliasMappingIdentifier pair.
如果此对象的值为零，则物理组件与此entAliasMapping条目的别名标识符之间的映射与所有未指定的逻辑实体相关联。也就是说，值为零（默认映射）标识此表中没有特定entPhysicalIndex/entAliasMappingIdentifier对的显式条目的任何逻辑实体。
For example, to indicate that a particular interface (e.g., physical component 33) is identified by the same value of ifIndex for all logical entities, the following instance might exist:
例如，为了指示特定接口（例如，物理组件33）由所有逻辑实体的相同ifIndex值标识，可能存在以下实例：
entAliasMappingIdentifier.33.0 = ifIndex.5
entAliasMappingIdentifier.33.0 = ifIndex.5translate error, please retry
In the event an entPhysicalEntry is associated differently for some logical entities, additional entAliasMapping entries may exist, e.g.:
如果某些逻辑实体的entPhysicalEntry关联方式不同，则可能存在其他entAliasMapping条目，例如：
entAliasMappingIdentifier.33.0 = ifIndex.6 entAliasMappingIdentifier.33.4 = ifIndex.1 entAliasMappingIdentifier.33.5 = ifIndex.1 entAliasMappingIdentifier.33.10 = ifIndex.12
EntaliasMappingDentifier.33.0=ifIndex.6 EntaliasMappingDentifier.33.4=ifIndex.1 EntaliasMappingDentifier.33.5=ifIndex.1 EntaliasMappingDentifier.33.10=ifIndex.12
Note that entries with non-zero entAliasLogicalIndexOrZero
index values have precedence over zero-indexed entries. In
this example, all logical entities except 4, 5, and 10
associate physical entity 33 with ifIndex.6."
::= { entAliasMappingEntry 1 }
Note that entries with non-zero entAliasLogicalIndexOrZero
index values have precedence over zero-indexed entries. In
this example, all logical entities except 4, 5, and 10
associate physical entity 33 with ifIndex.6."
::= { entAliasMappingEntry 1 }
entAliasMappingIdentifier OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies a particular conceptual row associated with the indicated entPhysicalIndex and entLogicalIndex pair.
entAliasMappingIdentifier对象类型语法RowPointer MAX-ACCESS只读状态当前描述“此对象的值标识与指示的entPhysicalIndex和entLogicalIndex对关联的特定概念行。
Because only physical ports are modeled in this table, only entries that represent interfaces or ports are allowed. If an ifEntry exists on behalf of a particular physical port, then this object should identify the associated ifEntry. For repeater ports, the appropriate row in the 'rptrPortGroupTable' should be identified instead.
因为此表中只对物理端口进行建模，所以只允许表示接口或端口的条目。如果存在代表特定物理端口的ifEntry，则此对象应标识关联的ifEntry。对于中继器端口，应改为标识“rptportgrouptable”中的相应行。
For example, suppose a physical port was represented by entPhysicalEntry.3, entLogicalEntry.15 existed for a repeater, and entLogicalEntry.22 existed for a bridge. Then there might be two related instances of entAliasMappingIdentifier:
例如，假设物理端口由entPhysicalEntry.3表示，中继器存在entLogicalEntry.15，网桥存在entLogicalEntry.22。然后可能有两个相关的entAliasMappingIdentifier实例：
entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
entAliasMappingIdentifier.3.22 == ifIndex.17
entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
entAliasMappingIdentifier.3.22 == ifIndex.17
It is possible that other mappings (besides interfaces and repeater ports) may be defined in the future, as required.
将来可能会根据需要定义其他映射（除了接口和中继器端口）。
Bridge ports are identified by examining the Bridge MIB and
appropriate ifEntries associated with each 'dot1dBasePort'
and are thus not represented in this table."
::= { entAliasMappingEntry 2 }
Bridge ports are identified by examining the Bridge MIB and
appropriate ifEntries associated with each 'dot1dBasePort'
and are thus not represented in this table."
::= { entAliasMappingEntry 2 }
-- physical mapping table entPhysicalContainsTable OBJECT-TYPE SYNTAX SEQUENCE OF EntPhysicalContainsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that exposes the container/'containee' relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format.
--物理映射表entPhysicalContainsTable EntPhysicalContainsEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“公开物理实体之间的容器/容器对象关系的表。此表提供了通过为给定entPhysicalTable构建虚拟包含树而找到的所有信息，但格式更直接。
In the event a physical entity is contained by more than one
other physical entity (e.g., double-wide modules), this
table should include these additional mappings, which cannot
be represented in the entPhysicalTable virtual containment
tree."
::= { entityMapping 3 }
In the event a physical entity is contained by more than one
other physical entity (e.g., double-wide modules), this
table should include these additional mappings, which cannot
be represented in the entPhysicalTable virtual containment
tree."
::= { entityMapping 3 }
entPhysicalContainsEntry OBJECT-TYPE
SYNTAX EntPhysicalContainsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single container/'containee' relationship."
INDEX { entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 }
entPhysicalContainsEntry OBJECT-TYPE
SYNTAX EntPhysicalContainsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single container/'containee' relationship."
INDEX { entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 }
EntPhysicalContainsEntry ::= SEQUENCE {
entPhysicalChildIndex PhysicalIndex
}
EntPhysicalContainsEntry ::= SEQUENCE {
entPhysicalChildIndex PhysicalIndex
}
entPhysicalChildIndex OBJECT-TYPE SYNTAX PhysicalIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The value of entPhysicalIndex for the contained physical entity."
entPhysicalChildIndex对象类型语法PhysicalIndex MAX-ACCESS只读状态当前描述“包含的物理实体的entPhysicalIndex值。”
::= { entPhysicalContainsEntry 1 }
::= { entPhysicalContainsEntry 1 }
-- last change time stamp for the whole MIB
entLastChangeTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time a conceptual row is
created, modified, or deleted in any of these tables:
- entPhysicalTable
- entLogicalTable
- entLPMappingTable
- entAliasMappingTable
- entPhysicalContainsTable
"
::= { entityGeneral 1 }
-- last change time stamp for the whole MIB
entLastChangeTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time a conceptual row is
created, modified, or deleted in any of these tables:
- entPhysicalTable
- entLogicalTable
- entLPMappingTable
- entAliasMappingTable
- entPhysicalContainsTable
"
::= { entityGeneral 1 }
-- Entity MIB Trap Definitions
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 }
-- Entity MIB Trap Definitions
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 }
entConfigChange NOTIFICATION-TYPE STATUS current DESCRIPTION "An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls.
entConfigChange NOTIFICATION-TYPE STATUS current DESCRIPTION“当entLastChangeTime的值更改时，将生成entConfigChange通知。NMS可利用该通知触发逻辑/物理实体表维护轮询。
An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations.
代理在给定的时间间隔内不应生成多个entConfigChange“通知事件”（建议默认为5秒）。“通知事件”是将单个陷阱或通知PDU传输到通知目的地列表。
If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away.
如果在限制期内发生其他配置更改，则代理应禁止这些更改的通知事件，直到当前限制期到期。在限制期结束时，如果自限制期开始以来发生任何配置更改，则应生成一个通知事件。在这种情况下，立即开始另一个节流周期。
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= { entityMIBTrapPrefix 1 }
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."
::= { entityMIBTrapPrefix 1 }
-- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
-- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
-- compliance statements
entityCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 1 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityLogicalGroup,
entityMappingGroup,
entityGeneralGroup,
entityNotificationsGroup
}
::= { entityCompliances 1 }
-- compliance statements
entityCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 1 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityLogicalGroup,
entityMappingGroup,
entityGeneralGroup,
entityNotificationsGroup
}
::= { entityCompliances 1 }
entity2Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 2 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityGeneralGroup,
entityNotificationsGroup
}
GROUP entityLogical2Group
DESCRIPTION
"Implementation of this group is not mandatory for agents
that model all MIB object instances within a single naming
scope."
entity2Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 2 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityGeneralGroup,
entityNotificationsGroup
}
GROUP entityLogical2Group
DESCRIPTION
"Implementation of this group is not mandatory for agents
that model all MIB object instances within a single naming
scope."
GROUP entityMappingGroup DESCRIPTION "Implementation of the entPhysicalContainsTable is mandatory for all agents. Implementation of the entLPMappingTable and entAliasMappingTables are not mandatory for agents that model all MIB object instances within a single naming scope.
GROUP entityMappingGroup DESCRIPTION“entPhysicalContainsTable的实现对于所有代理都是强制性的。EntlMappingTable和entAliasMappingTables的实现对于在单个命名范围内为所有MIB对象实例建模的代理都不是强制性的。
Note that the entAliasMappingTable may be useful for all agents; however, implementation of the entityLogicalGroup or entityLogical2Group is required to support this table."
请注意，恩他利阿玛可用于所有药剂；但是，需要实现entityLogicalGroup或entityLogical2Group来支持此表。”
OBJECT entPhysicalSerialNum MIN-ACCESS not-accessible DESCRIPTION "Read and write access is not required for agents that cannot identify serial number information for physical entities and/or cannot provide non-volatile storage for NMS-assigned serial numbers.
对象entPhysicalSerialNum MIN-ACCESS不可访问描述“对于无法识别物理实体序列号信息和/或无法为NMS分配的序列号提供非易失性存储的代理，不需要读写访问权限。
Write access is not required for agents that can identify serial number information for physical entities but cannot provide non-volatile storage for NMS-assigned serial numbers.
Write access is not required for agents that can identify serial number information for physical entities but cannot provide non-volatile storage for NMS-assigned serial numbers.translate error, please retry
Write access is not required for physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)'."
entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体不需要写访问权限。”
OBJECT entPhysicalAlias MIN-ACCESS read-only DESCRIPTION "Write access is required only if the associated entPhysicalClass value is equal to 'chassis(3)'."
对象entPhysicalAlias MIN-ACCESS只读说明“仅当关联的entPhysicalClass值等于“机箱（3）”时，才需要写访问权限。”
OBJECT entPhysicalAssetID MIN-ACCESS not-accessible DESCRIPTION "Read and write access is not required for agents that cannot provide non-volatile storage for NMS-assigned asset identifiers.
对象entPhysicalAssetID MIN-ACCESS不可访问描述“对于无法为NMS分配的资产标识符提供非易失性存储的代理，不需要读写访问权限。
Write access is not required for physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)'."
entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体不需要写访问权限。”
OBJECT entPhysicalClass SYNTAX INTEGER { other(1),
对象entPhysicalClass语法整数{other（1），
unknown(2),
chassis(3),
backplane(4),
container(5),
powerSupply(6),
fan(7),
sensor(8),
module(9),
port(10),
stack(11)
}
DESCRIPTION
"Implementation of the 'cpu(12)' enumeration is not
required."
::= { entityCompliances 2 }
unknown(2),
chassis(3),
backplane(4),
container(5),
powerSupply(6),
fan(7),
sensor(8),
module(9),
port(10),
stack(11)
}
DESCRIPTION
"Implementation of the 'cpu(12)' enumeration is not
required."
::= { entityCompliances 2 }
entity3Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 3 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup,
entityNotificationsGroup
}
GROUP entityLogical2Group
DESCRIPTION
"Implementation of this group is not mandatory for agents
that model all MIB object instances within a single naming
scope."
entity3Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 3 of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup,
entityNotificationsGroup
}
GROUP entityLogical2Group
DESCRIPTION
"Implementation of this group is not mandatory for agents
that model all MIB object instances within a single naming
scope."
GROUP entityMappingGroup DESCRIPTION "Implementation of the entPhysicalContainsTable is mandatory for all agents. Implementation of the entLPMappingTable and entAliasMappingTables are not mandatory for agents that model all MIB object instances within a single naming scope.
GROUP entityMappingGroup DESCRIPTION“entPhysicalContainsTable的实现对于所有代理都是强制性的。EntlMappingTable和entAliasMappingTables的实现对于在单个命名范围内为所有MIB对象实例建模的代理都不是强制性的。
Note that the entAliasMappingTable may be useful for all agents; however, implementation of the entityLogicalGroup or entityLogical2Group is required to support this table."
请注意，恩他利阿玛可用于所有药剂；但是，需要实现entityLogicalGroup或entityLogical2Group来支持此表。”
OBJECT entPhysicalSerialNum MIN-ACCESS not-accessible
对象entPhysicalSerialNum最小访问权限不可访问
DESCRIPTION "Read and write access is not required for agents that cannot identify serial number information for physical entities and/or cannot provide non-volatile storage for NMS-assigned serial numbers.
DESCRIPTION "Read and write access is not required for agents that cannot identify serial number information for physical entities and/or cannot provide non-volatile storage for NMS-assigned serial numbers.translate error, please retry
Write access is not required for agents that can identify serial number information for physical entities but cannot provide non-volatile storage for NMS-assigned serial numbers.
可以识别物理实体序列号信息但不能为NMS分配的序列号提供非易失性存储的代理不需要写访问。
Write access is not required for physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)'."
entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体不需要写访问权限。”
OBJECT entPhysicalAlias MIN-ACCESS read-only DESCRIPTION "Write access is required only if the associated entPhysicalClass value is equal to 'chassis(3)'."
对象entPhysicalAlias MIN-ACCESS只读说明“仅当关联的entPhysicalClass值等于“机箱（3）”时，才需要写访问权限。”
OBJECT entPhysicalAssetID MIN-ACCESS not-accessible DESCRIPTION "Read and write access is not required for agents that cannot provide non-volatile storage for NMS-assigned asset identifiers.
对象entPhysicalAssetID MIN-ACCESS不可访问描述“对于无法为NMS分配的资产标识符提供非易失性存储的代理，不需要读写访问权限。
Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to
'false(2)'."
::= { entityCompliances 3 }
Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to
'false(2)'."
::= { entityCompliances 3 }
entity4Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement
the full version 4 (full compliance) of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup,
entityNotificationsGroup,
entityPhysical4Group
}
GROUP entityLogical2Group
entity4Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement
the full version 4 (full compliance) of the Entity MIB."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup,
entityNotificationsGroup,
entityPhysical4Group
}
GROUP entityLogical2Group
DESCRIPTION "Implementation of this group is not mandatory for agents that model all MIB object instances within a single naming scope."
DESCRIPTION“对于在单个命名范围内为所有MIB对象实例建模的代理，此组的实现不是强制性的。”
GROUP entityMappingGroup DESCRIPTION "Implementation of the entPhysicalContainsTable is mandatory for all agents. Implementation of the entLPMappingTable and entAliasMappingTables are not mandatory for agents that model all MIB object instances within a single naming scope.
GROUP entityMappingGroup DESCRIPTION“entPhysicalContainsTable的实现对于所有代理都是强制性的。EntlMappingTable和entAliasMappingTables的实现对于在单个命名范围内为所有MIB对象实例建模的代理都不是强制性的。
Note that the entAliasMappingTable may be useful for all agents; however, implementation of the entityLogicalGroup or entityLogical2Group is required to support this table."
请注意，恩他利阿玛可用于所有药剂；但是，需要实现entityLogicalGroup或entityLogical2Group来支持此表。”
OBJECT entPhysicalSerialNum MIN-ACCESS not-accessible DESCRIPTION "Read and write access is not required for agents that cannot identify serial number information for physical entities and/or cannot provide non-volatile storage for NMS-assigned serial numbers.
对象entPhysicalSerialNum MIN-ACCESS不可访问描述“对于无法识别物理实体序列号信息和/或无法为NMS分配的序列号提供非易失性存储的代理，不需要读写访问权限。
Write access is not required for agents that can identify serial number information for physical entities but cannot provide non-volatile storage for NMS-assigned serial numbers.
可以识别物理实体序列号信息但不能为NMS分配的序列号提供非易失性存储的代理不需要写访问。
Write access is not required for physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)'."
entPhysicalIsFRU对象的关联值等于“false（2）”的物理实体不需要写访问权限。”
OBJECT entPhysicalAlias MIN-ACCESS read-only DESCRIPTION "Write access is required only if the associated entPhysicalClass value is equal to 'chassis(3)'."
对象entPhysicalAlias MIN-ACCESS只读说明“仅当关联的entPhysicalClass值等于“机箱（3）”时，才需要写访问权限。”
OBJECT entPhysicalAssetID MIN-ACCESS not-accessible DESCRIPTION "Read and write access is not required for agents that cannot provide non-volatile storage for NMS-assigned asset identifiers.
对象entPhysicalAssetID MIN-ACCESS不可访问描述“对于无法为NMS分配的资产标识符提供非易失性存储的代理，不需要读写访问权限。
Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to
'false(2)'."
::= { entityCompliances 4 }
Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to
'false(2)'."
::= { entityCompliances 4 }
entity4CRCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 4 of the Entity MIB on devices with constrained
resources."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalCRGroup,
entityPhysical4Group
}
::= { entityCompliances 5 }
entity4CRCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement
version 4 of the Entity MIB on devices with constrained
resources."
MODULE -- this module
MANDATORY-GROUPS {
entityPhysicalCRGroup,
entityPhysical4Group
}
::= { entityCompliances 5 }
-- MIB groupings
entityPhysicalGroup OBJECT-GROUP
OBJECTS {
entPhysicalDescr,
entPhysicalVendorType,
entPhysicalContainedIn,
entPhysicalClass,
entPhysicalParentRelPos,
entPhysicalName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information."
::= { entityGroups 1 }
-- MIB groupings
entityPhysicalGroup OBJECT-GROUP
OBJECTS {
entPhysicalDescr,
entPhysicalVendorType,
entPhysicalContainedIn,
entPhysicalClass,
entPhysicalParentRelPos,
entPhysicalName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information."
::= { entityGroups 1 }
entityLogicalGroup OBJECT-GROUP
OBJECTS {
entLogicalDescr,
entLogicalType,
entLogicalCommunity,
entLogicalTAddress,
entLogicalTDomain
}
STATUS deprecated
entityLogicalGroup OBJECT-GROUP
OBJECTS {
entLogicalDescr,
entLogicalType,
entLogicalCommunity,
entLogicalTAddress,
entLogicalTDomain
}
STATUS deprecated
DESCRIPTION
"The collection of objects used to represent the list of
logical entities for which a single agent provides
management information."
::= { entityGroups 2 }
DESCRIPTION
"The collection of objects used to represent the list of
logical entities for which a single agent provides
management information."
::= { entityGroups 2 }
entityMappingGroup OBJECT-GROUP
OBJECTS {
entLPPhysicalIndex,
entAliasMappingIdentifier,
entPhysicalChildIndex
}
STATUS current
DESCRIPTION
"The collection of objects used to represent the
associations between multiple logical entities, physical
components, interfaces, and port identifiers for which a
single agent provides management information."
::= { entityGroups 3 }
entityMappingGroup OBJECT-GROUP
OBJECTS {
entLPPhysicalIndex,
entAliasMappingIdentifier,
entPhysicalChildIndex
}
STATUS current
DESCRIPTION
"The collection of objects used to represent the
associations between multiple logical entities, physical
components, interfaces, and port identifiers for which a
single agent provides management information."
::= { entityGroups 3 }
entityGeneralGroup OBJECT-GROUP
OBJECTS {
entLastChangeTime
}
STATUS current
DESCRIPTION
"The collection of objects used to represent general entity
information for which a single agent provides management
information."
::= { entityGroups 4 }
entityGeneralGroup OBJECT-GROUP
OBJECTS {
entLastChangeTime
}
STATUS current
DESCRIPTION
"The collection of objects used to represent general entity
information for which a single agent provides management
information."
::= { entityGroups 4 }
entityNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { entConfigChange }
STATUS current
DESCRIPTION
"The collection of notifications used to indicate Entity MIB
data consistency and general status information."
::= { entityGroups 5 }
entityNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { entConfigChange }
STATUS current
DESCRIPTION
"The collection of notifications used to indicate Entity MIB
data consistency and general status information."
::= { entityGroups 5 }
entityPhysical2Group OBJECT-GROUP OBJECTS { entPhysicalHardwareRev, entPhysicalFirmwareRev, entPhysicalSoftwareRev, entPhysicalSerialNum, entPhysicalMfgName, entPhysicalModelName, entPhysicalAlias,
entityPhysical2Group对象组对象{entPhysicalHardwareRev、entPhysicalFirmwareRev、entPhysicalSoftwareRev、entPhysicalSerialNum、EntPhysicalFGName、entPhysicalModelName、entPhysicalAlias、，
entPhysicalAssetID,
entPhysicalIsFRU
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup."
::= { entityGroups 6 }
entPhysicalAssetID,
entPhysicalIsFRU
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup."
::= { entityGroups 6 }
entityLogical2Group OBJECT-GROUP
OBJECTS {
entLogicalDescr,
entLogicalType,
entLogicalTAddress,
entLogicalTDomain,
entLogicalContextEngineID,
entLogicalContextName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent the
list of logical entities for which a single SNMP entity
provides management information."
::= { entityGroups 7 }
entityLogical2Group OBJECT-GROUP
OBJECTS {
entLogicalDescr,
entLogicalType,
entLogicalTAddress,
entLogicalTDomain,
entLogicalContextEngineID,
entLogicalContextName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent the
list of logical entities for which a single SNMP entity
provides management information."
::= { entityGroups 7 }
entityPhysical3Group OBJECT-GROUP
OBJECTS {
entPhysicalMfgDate,
entPhysicalUris
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup."
::= { entityGroups 8 }
entityPhysical3Group OBJECT-GROUP
OBJECTS {
entPhysicalMfgDate,
entPhysicalUris
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup."
::= { entityGroups 8 }
entityPhysical4Group OBJECT-GROUP
OBJECTS {
entPhysicalUUID
}
STATUS current
entityPhysical4Group OBJECT-GROUP
OBJECTS {
entPhysicalUUID
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup and
entityPhysicalCRGroup."
::= { entityGroups 9 }
DESCRIPTION
"The collection of objects used to represent physical
system components for which a single agent provides
management information. This group augments the objects
contained in the entityPhysicalGroup and
entityPhysicalCRGroup."
::= { entityGroups 9 }
entityPhysicalCRGroup OBJECT-GROUP
OBJECTS {
entPhysicalClass,
entPhysicalName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for constrained resourced devices,
for which a single agent provides management
information."
::= { entityGroups 10 }
entityPhysicalCRGroup OBJECT-GROUP
OBJECTS {
entPhysicalClass,
entPhysicalName
}
STATUS current
DESCRIPTION
"The collection of objects used to represent physical
system components for constrained resourced devices,
for which a single agent provides management
information."
::= { entityGroups 10 }
END
终止
IANA-ENTITY-MIB DEFINITIONS ::= BEGIN
IANA-ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION FROM SNMPv2-TC -- RFC 2579 ;
从SNMPv2 SMI--RFC 2578从SNMPv2 TC--RFC 2579导入模块标识、mib-2；
ianaEntityMIB MODULE-IDENTITY LAST-UPDATED "201304050000Z" -- April 5, 2013 ORGANIZATION "IANA" CONTACT-INFO "Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536
ianaEntityMIB MODULE-IDENTITY最后一次更新“201304050000Z”--2013年4月5日组织“IANA”联系方式“互联网分配号码管理局邮政：ICANN 12025 Waterfront Drive，加利福尼亚州洛杉矶300号套房90094-2536
Phone: +1-310-301-5800
EMail: iana@iana.org"
Phone: +1-310-301-5800
EMail: iana@iana.org"
DESCRIPTION "This MIB module defines a TEXTUAL-CONVENTION that provides an indication of the general hardware type of a particular physical entity.
DESCRIPTION“此MIB模块定义一个文本约定，该约定提供特定物理实体的通用硬件类型指示。
Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2013 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).
The initial version of this MIB module was published in RFC 6933; for full legal notices see the RFC itself."
该MIB模块的初始版本发布在RFC 6933中；有关完整的法律通知，请参见RFC本身。”
REVISION "201304050000Z" -- April 5, 2013 DESCRIPTION "Initial version of this MIB as published in RFC 6933."
修订版“201304050000Z”-2013年4月5日描述“RFC 6933中发布的本MIB初始版本”
::= { mib-2 216 }
::= { mib-2 216 }
-- Textual Conventions
--文本约定
IANAPhysicalClass ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value that provides an indication of the
general hardware type of a particular physical entity.
There are no restrictions as to the number of
entPhysicalEntries of each entPhysicalClass, which must
be instantiated by an agent.
IANAPhysicalClass ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value that provides an indication of the
general hardware type of a particular physical entity.
There are no restrictions as to the number of
entPhysicalEntries of each entPhysicalClass, which must
be instantiated by an agent.
The enumeration 'other' is applicable if the physical entity class is known but does not match any of the supported values.
如果物理实体类已知但与任何支持的值都不匹配，则枚举“other”适用。
The enumeration 'unknown' is applicable if the physical entity class is unknown to the agent.
如果代理未知物理实体类，则枚举“未知”适用。
The enumeration 'chassis' is applicable if the physical entity class is an overall container for networking equipment. Any class of physical entity, except a stack, may be contained within a chassis; a chassis may only be contained within a stack.
如果物理实体类是网络设备的总体容器，则枚举“机箱”适用。任何类别的物理实体（堆栈除外）都可以包含在机箱中；机箱只能包含在堆栈中。
The enumeration 'backplane' is applicable if the physical entity class is some sort of device for aggregating and forwarding networking traffic, such as a shared backplane in a modular ethernet switch. Note that an agent may model a backplane as a single physical entity, which is actually implemented as multiple discrete physical components (within a chassis or stack).
如果物理实体类是用于聚合和转发网络流量的某种设备，例如模块化以太网交换机中的共享背板，则枚举“背板”适用。请注意，代理可以将背板建模为单个物理实体，实际实现为多个离散物理组件（在机箱或堆栈中）。
The enumeration 'container' is applicable if the physical entity class is capable of containing one or more removable physical entities, possibly of different types. For example, each (empty or full) slot in a chassis will be modeled as a container. Note that all removable physical entities should be modeled within a container entity, such as field-replaceable modules, fans, or power supplies. Note that all known containers should be modeled by the agent, including empty containers.
如果物理实体类能够包含一个或多个可移动物理实体（可能是不同类型的），则枚举“容器”适用。例如，机箱中的每个（空或满）插槽都将建模为一个容器。请注意，所有可移动物理实体都应在容器实体内建模，如现场可更换模块、风扇或电源。请注意，所有已知容器都应由代理建模，包括空容器。
The enumeration 'powerSupply' is applicable if the physical entity class is a power-supplying component.
如果物理实体类是电源供应组件，则枚举“powerSupply”适用。
The enumeration 'fan' is applicable if the physical entity class is a fan or other heat-reduction component.
如果物理实体类是风扇或其他散热组件，则枚举“风扇”适用。
The enumeration 'sensor' is applicable if the physical entity class is some sort of sensor, such as a temperature sensor within a router chassis.
如果物理实体类是某种传感器，例如路由器机箱内的温度传感器，则枚举“传感器”适用。
The enumeration 'module' is applicable if the physical entity class is some sort of self-contained sub-system. If the enumeration 'module' is removable, then it should be modeled within a container entity; otherwise, it should be modeled directly within another physical entity (e.g., a chassis or another module).
如果物理实体类是某种自包含子系统，则枚举“模块”适用。如果枚举“模块”是可移动的，那么它应该在容器实体中建模；否则，应直接在另一个物理实体（例如机箱或另一个模块）内对其进行建模。
The enumeration 'port' is applicable if the physical entity class is some sort of networking port, capable of receiving and/or transmitting networking traffic.
如果物理实体类是某种网络端口，能够接收和/或发送网络流量，则枚举“端口”适用。
The enumeration 'stack' is applicable if the physical entity class is some sort of super-container (possibly virtual) intended to group together multiple chassis entities. A stack may be realized by a 'virtual' cable, a real interconnect cable attached to multiple chassis, or multiple interconnect cables. A stack should not be
如果物理实体类是某种超级容器（可能是虚拟的），用于将多个机箱实体组合在一起，则枚举“堆栈”适用。堆栈可以通过“虚拟”电缆、连接到多个机箱的真实互连电缆或多个互连电缆来实现。堆栈不应被删除
modeled within any other physical entities, but a stack may be contained within another stack. Only chassis entities should be contained within a stack.
在任何其他物理实体中建模，但堆栈可能包含在另一个堆栈中。堆栈中只应包含机箱实体。
The enumeration 'cpu' is applicable if the physical entity class is some sort of central processing unit.
如果物理实体类是某种中央处理器，则枚举“cpu”适用。
The enumeration 'energyObject' is applicable if the physical entity is some sort of energy object, i.e., a piece of equipment that is part of or attached to a communications network that is monitored, controlled, or aids in the management of another device for Energy Management.
如果物理实体是某种能源对象，即作为通信网络的一部分或连接到通信网络的设备，该通信网络被监控、控制或有助于管理另一个用于能源管理的设备，则枚举“energyObject”适用。
The enumeration 'battery' is applicable if the physical entity class is some sort of battery."
如果物理实体类是某种电池，则枚举“电池”适用。”
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
container(5), -- e.g., chassis slot or daughter-card holder
powerSupply(6),
fan(7),
sensor(8),
module(9), -- e.g., plug-in card or daughter-card
port(10),
stack(11), -- e.g., stack of multiple chassis entities
cpu(12),
energyObject(13),
battery (14)
}
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
container(5), -- e.g., chassis slot or daughter-card holder
powerSupply(6),
fan(7),
sensor(8),
module(9), -- e.g., plug-in card or daughter-card
port(10),
stack(11), -- e.g., stack of multiple chassis entities
cpu(12),
energyObject(13),
battery (14)
}
END
终止
UUID-TC-MIB DEFINITIONS ::= BEGIN
UUID-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION FROM SNMPv2-TC -- RFC 2579 ;
从SNMPv2 SMI--RFC 2578从SNMPv2 TC--RFC 2579导入模块标识、mib-2；
uuidTCMIB MODULE-IDENTITY
uuidTCMIB模块标识
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IETF Energy Management Working Group"
CONTACT-INFO "WG Email: eman@ietf.org
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/eman
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IETF Energy Management Working Group"
CONTACT-INFO "WG Email: eman@ietf.org
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/eman
Dan Romascanu Avaya Park Atidim, Bldg. #3 Tel Aviv, 61581 Israel Phone: +972-3-6458414 Email: dromasca@avaya.com
Dan Romascanu Avaya Park Atidim，特拉维夫3号楼，61581以色列电话：+972-3-6458414电子邮件：dromasca@avaya.com
Juergen Quittek NEC Europe Ltd. Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany Phone: +49 6221 4342-115 Email: quittek@neclab.eu
Juergen Quittek NEC欧洲有限公司网络研究部Kurfuersten Anlage 36 Heidelberg 69115德国电话：+49 6221 4342-115电子邮件：quittek@neclab.eu
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 "This MIB module defines TEXTUAL-CONVENTIONs representing Universally Unique IDentifiers (UUIDs).
DESCRIPTION“此MIB模块定义表示通用唯一标识符（UUID）的文本约定。
Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2013 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)."
REVISION "201304050000Z" -- April 5, 2013 DESCRIPTION "Initial version of this MIB as published in RFC 6933."
REVISION "201304050000Z" -- April 5, 2013 DESCRIPTION "Initial version of this MIB as published in RFC 6933."translate error, please retry
::= { mib-2 217 }
::= { mib-2 217 }
-- Textual Conventions
--文本约定
UUID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1."
UUID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1."
SYNTAX OCTET STRING (SIZE (16))
语法八位字节字符串（大小（16））
UUIDorZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1.
UUIDorZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1.
The semantics of the value zero-length OCTET STRING are object-specific and must therefore be defined as part of the description of any object that uses this syntax."
值零长度八位字节字符串的语义是特定于对象的，因此必须定义为使用此语法的任何对象描述的一部分。”
SYNTAX OCTET STRING (SIZE (0|16))
语法八位字符串（大小（0 | 16））
END
终止
The following sections iterate the instance values for two example networking devices. These examples are kept simple to make them more understandable. Auxiliary components such as fans, sensors, empty slots, and sub-modules are not shown but might be modeled in real implementations.
以下各节迭代两个示例网络设备的实例值。这些例子保持简单，以便更容易理解。未显示辅助组件，如风扇、传感器、空插槽和子模块，但可以在实际实现中建模。
The first example is a router containing two slots. Each slot contains a 3-port router/bridge module. Each port is represented in the ifTable. There are two logical instances of OSPF running and two logical bridges:
第一个示例是包含两个插槽的路由器。每个插槽包含一个3端口路由器/网桥模块。每个端口都在ifTable中表示。OSPF运行的逻辑实例有两个，逻辑桥有两个：
Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 100'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '100-A'
entPhysicalHardwareRev.1 == 'A(1.00.02)'
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'C100076544'
entPhysicalMfgName.1 == 'Acme'
entPhysicalModelName.1 == '100'
entPhysicalAlias.1 == 'cl-SJ17-3-006:rack1:rtr-U3'
entPhysicalAssetID.1 == '0007372293'
entPhysicalIsFRU.1 == true(1)
entPhysicalMfgDate.1 == '2002-5-26,13:30:30.0,-4:0'
entPhysicalUris.1 == 'URN:CLEI:CNME120ARA'
2 slots within the chassis:
entPhysicalDescr.2 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == container(5)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'S1'
entPhysicalHardwareRev.2 == 'B(1.00.01)'
entPhysicalSoftwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'Acme'
entPhysicalModelName.2 == 'AA'
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
entPhysicalMfgDate.2 == '2002-7-26,12:22:12.0,-4:0'
entPhysicalUris.2 == 'URN:CLEI:CNME123ARA'
Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 100'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '100-A'
entPhysicalHardwareRev.1 == 'A(1.00.02)'
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'C100076544'
entPhysicalMfgName.1 == 'Acme'
entPhysicalModelName.1 == '100'
entPhysicalAlias.1 == 'cl-SJ17-3-006:rack1:rtr-U3'
entPhysicalAssetID.1 == '0007372293'
entPhysicalIsFRU.1 == true(1)
entPhysicalMfgDate.1 == '2002-5-26,13:30:30.0,-4:0'
entPhysicalUris.1 == 'URN:CLEI:CNME120ARA'
2 slots within the chassis:
entPhysicalDescr.2 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == container(5)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'S1'
entPhysicalHardwareRev.2 == 'B(1.00.01)'
entPhysicalSoftwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'Acme'
entPhysicalModelName.2 == 'AA'
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
entPhysicalMfgDate.2 == '2002-7-26,12:22:12.0,-4:0'
entPhysicalUris.2 == 'URN:CLEI:CNME123ARA'
entPhysicalDescr.3 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.3 = acmeProducts.slotTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == container(5)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'S2'
entPhysicalHardwareRev.3 == '1.00.07'
entPhysicalSoftwareRev.3 == ''
entPhysicalFirmwareRev.3 == ''
entPhysicalSerialNum.3 == ''
entPhysicalDescr.3 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.3 = acmeProducts.slotTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == container(5)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'S2'
entPhysicalHardwareRev.3 == '1.00.07'
entPhysicalSoftwareRev.3 == ''
entPhysicalFirmwareRev.3 == ''
entPhysicalSerialNum.3 == ''
entPhysicalMfgName.3 == 'Acme'
entPhysicalModelName.3 == 'AA'
entPhysicalAlias.3 == ''
entPhysicalAssetID.3 == ''
entPhysicalIsFRU.3 == false(2)
entPhysicalMfgDate.3 == '2002-7-26,12:12:12.0,-4:0'
entPhysicalUris.3 == 'URN:CLEI:CNME123ARA'
entPhysicalMfgName.3 == 'Acme'
entPhysicalModelName.3 == 'AA'
entPhysicalAlias.3 == ''
entPhysicalAssetID.3 == ''
entPhysicalIsFRU.3 == false(2)
entPhysicalMfgDate.3 == '2002-7-26,12:12:12.0,-4:0'
entPhysicalUris.3 == 'URN:CLEI:CNME123ARA'
2 Field-replaceable modules:
Slot 1 contains a module with 3 ports:
entPhysicalDescr.4 == 'Acme Router-100'
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'M1'
entPhysicalHardwareRev.4 == '1.00.07'
entPhysicalSoftwareRev.4 == '1.4.1'
entPhysicalFirmwareRev.4 == 'A(1.1)'
entPhysicalSerialNum.4 == 'C100087363'
entPhysicalMfgName.4 == 'Acme'
entPhysicalModelName.4 == 'R100-FE'
entPhysicalAlias.4 == 'rtr-U3:m1:SJ17-3-eng'
entPhysicalAssetID.4 == '0007372462'
entPhysicalIsFRU.4 == true(1)
entPhysicalMfgDate.4 == '2003-7-18,13:30:30.0,-4:0'
entPhysicalUris.4 == 'URN:CLEI:CNRU123CAA'
2 Field-replaceable modules:
Slot 1 contains a module with 3 ports:
entPhysicalDescr.4 == 'Acme Router-100'
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'M1'
entPhysicalHardwareRev.4 == '1.00.07'
entPhysicalSoftwareRev.4 == '1.4.1'
entPhysicalFirmwareRev.4 == 'A(1.1)'
entPhysicalSerialNum.4 == 'C100087363'
entPhysicalMfgName.4 == 'Acme'
entPhysicalModelName.4 == 'R100-FE'
entPhysicalAlias.4 == 'rtr-U3:m1:SJ17-3-eng'
entPhysicalAssetID.4 == '0007372462'
entPhysicalIsFRU.4 == true(1)
entPhysicalMfgDate.4 == '2003-7-18,13:30:30.0,-4:0'
entPhysicalUris.4 == 'URN:CLEI:CNRU123CAA'
entPhysicalDescr.5 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4
entPhysicalClass.5 == port(10)
entPhysicalParentRelPos.5 == 1
entPhysicalName.5 == 'P1'
entPhysicalHardwareRev.5 == 'G(1.02)'
entPhysicalSoftwareRev.5 == ''
entPhysicalFirmwareRev.5 == '1.1'
entPhysicalSerialNum.5 == ''
entPhysicalMfgName.5 == 'Acme'
entPhysicalModelName.5 == 'FE-100'
entPhysicalAlias.5 == ''
entPhysicalAssetID.5 == ''
entPhysicalIsFRU.5 == false(2)
entPhysicalMfgDate.5 == '2003-7-18,14:20:22.0,-4:0'
entPhysicalUris.5 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.5 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4
entPhysicalClass.5 == port(10)
entPhysicalParentRelPos.5 == 1
entPhysicalName.5 == 'P1'
entPhysicalHardwareRev.5 == 'G(1.02)'
entPhysicalSoftwareRev.5 == ''
entPhysicalFirmwareRev.5 == '1.1'
entPhysicalSerialNum.5 == ''
entPhysicalMfgName.5 == 'Acme'
entPhysicalModelName.5 == 'FE-100'
entPhysicalAlias.5 == ''
entPhysicalAssetID.5 == ''
entPhysicalIsFRU.5 == false(2)
entPhysicalMfgDate.5 == '2003-7-18,14:20:22.0,-4:0'
entPhysicalUris.5 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.6 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.6 == acmeProducts.portTypes.2
entPhysicalDescr.6 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.6 == acmeProducts.portTypes.2
entPhysicalContainedIn.6 == 4
entPhysicalClass.6 == port(10)
entPhysicalParentRelPos.6 == 2
entPhysicalName.6 == 'P2'
entPhysicalHardwareRev.6 == 'G(1.02)'
entPhysicalSoftwareRev.6 == ''
entPhysicalFirmwareRev.6 == '1.1'
entPhysicalSerialNum.6 == ''
entPhysicalMfgName.6 == 'Acme'
entPhysicalModelName.6 == 'FE-100'
entPhysicalAlias.6 == ''
entPhysicalAssetID.6 == ''
entPhysicalIsFRU.6 == false(2)
entPhysicalMfgDate.6 == '2003-7-19,10:15:15.0,-4:0'
entPhysicalUris.6 == 'URN:CLEI:CNMES23ARA'
entPhysicalContainedIn.6 == 4
entPhysicalClass.6 == port(10)
entPhysicalParentRelPos.6 == 2
entPhysicalName.6 == 'P2'
entPhysicalHardwareRev.6 == 'G(1.02)'
entPhysicalSoftwareRev.6 == ''
entPhysicalFirmwareRev.6 == '1.1'
entPhysicalSerialNum.6 == ''
entPhysicalMfgName.6 == 'Acme'
entPhysicalModelName.6 == 'FE-100'
entPhysicalAlias.6 == ''
entPhysicalAssetID.6 == ''
entPhysicalIsFRU.6 == false(2)
entPhysicalMfgDate.6 == '2003-7-19,10:15:15.0,-4:0'
entPhysicalUris.6 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.7 == 'Acme Router-100 FDDI-Port'
entPhysicalVendorType.7 == acmeProducts.portTypes.3
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == port(10)
entPhysicalParentRelPos.7 == 3
entPhysicalName.7 == 'P3'
entPhysicalHardwareRev.7 == 'B(1.03)'
entPhysicalSoftwareRev.7 == '2.5.1'
entPhysicalFirmwareRev.7 == '2.5F'
entPhysicalSerialNum.7 == ''
entPhysicalMfgName.7 == 'Acme'
entPhysicalModelName.7 == 'FDDI-100'
entPhysicalAlias.7 == ''
entPhysicalAssetID.7 == ''
entPhysicalIsFRU.7 == false(2)
entPhysicalDescr.7 == 'Acme Router-100 FDDI-Port'
entPhysicalVendorType.7 == acmeProducts.portTypes.3
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == port(10)
entPhysicalParentRelPos.7 == 3
entPhysicalName.7 == 'P3'
entPhysicalHardwareRev.7 == 'B(1.03)'
entPhysicalSoftwareRev.7 == '2.5.1'
entPhysicalFirmwareRev.7 == '2.5F'
entPhysicalSerialNum.7 == ''
entPhysicalMfgName.7 == 'Acme'
entPhysicalModelName.7 == 'FDDI-100'
entPhysicalAlias.7 == ''
entPhysicalAssetID.7 == ''
entPhysicalIsFRU.7 == false(2)
Slot 2 contains another 3-port module:
entPhysicalDescr.8 == 'Acme Router-100 Comm Module'
entPhysicalVendorType.8 == acmeProducts.moduleTypes.15
entPhysicalContainedIn.8 == 3
entPhysicalClass.8 == module(9)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'M2'
entPhysicalHardwareRev.8 == '2.01.00'
entPhysicalSoftwareRev.8 == '3.0.7'
entPhysicalFirmwareRev.8 == 'A(1.2)'
entPhysicalSerialNum.8 == 'C100098732'
entPhysicalMfgName.8 == 'Acme'
entPhysicalModelName.8 == 'C100'
entPhysicalAlias.8 == 'rtr-U3:m2:SJ17-2-eng'
entPhysicalAssetID.8 == '0007373982'
entPhysicalIsFRU.8 == true(1)
Slot 2 contains another 3-port module:
entPhysicalDescr.8 == 'Acme Router-100 Comm Module'
entPhysicalVendorType.8 == acmeProducts.moduleTypes.15
entPhysicalContainedIn.8 == 3
entPhysicalClass.8 == module(9)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'M2'
entPhysicalHardwareRev.8 == '2.01.00'
entPhysicalSoftwareRev.8 == '3.0.7'
entPhysicalFirmwareRev.8 == 'A(1.2)'
entPhysicalSerialNum.8 == 'C100098732'
entPhysicalMfgName.8 == 'Acme'
entPhysicalModelName.8 == 'C100'
entPhysicalAlias.8 == 'rtr-U3:m2:SJ17-2-eng'
entPhysicalAssetID.8 == '0007373982'
entPhysicalIsFRU.8 == true(1)
entPhysicalMfgDate.8 == '2002-5-26,13:30:15.0,-4:0'
entPhysicalUris.8 == 'URN:CLEI:CNRT321MAA'
entPhysicalMfgDate.8 == '2002-5-26,13:30:15.0,-4:0'
entPhysicalUris.8 == 'URN:CLEI:CNRT321MAA'
entPhysicalDescr.9 == 'Acme Fddi-100 Port'
entPhysicalVendorType.9 == acmeProducts.portTypes.5
entPhysicalContainedIn.9 == 8
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 1
entPhysicalName.9 == 'FDDI Primary'
entPhysicalHardwareRev.9 == 'CC(1.07)'
entPhysicalSoftwareRev.9 == '2.0.34'
entPhysicalFirmwareRev.9 == '1.1'
entPhysicalSerialNum.9 == ''
entPhysicalMfgName.9 == 'Acme'
entPhysicalModelName.9 == 'FDDI-100'
entPhysicalAlias.9 == ''
entPhysicalAssetID.9 == ''
entPhysicalIsFRU.9 == false(2)
entPhysicalDescr.9 == 'Acme Fddi-100 Port'
entPhysicalVendorType.9 == acmeProducts.portTypes.5
entPhysicalContainedIn.9 == 8
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 1
entPhysicalName.9 == 'FDDI Primary'
entPhysicalHardwareRev.9 == 'CC(1.07)'
entPhysicalSoftwareRev.9 == '2.0.34'
entPhysicalFirmwareRev.9 == '1.1'
entPhysicalSerialNum.9 == ''
entPhysicalMfgName.9 == 'Acme'
entPhysicalModelName.9 == 'FDDI-100'
entPhysicalAlias.9 == ''
entPhysicalAssetID.9 == ''
entPhysicalIsFRU.9 == false(2)
entPhysicalDescr.10 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.10 == acmeProducts.portTypes.2
entPhysicalContainedIn.10 == 8
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 2
entPhysicalName.10 == 'Ethernet A'
entPhysicalHardwareRev.10 == 'G(1.04)'
entPhysicalSoftwareRev.10 == ''
entPhysicalFirmwareRev.10 == '1.3'
entPhysicalSerialNum.10 == ''
entPhysicalMfgName.10 == 'Acme'
entPhysicalModelName.10 == 'FE-100'
entPhysicalAlias.10 == ''
entPhysicalAssetID.10 == ''
entPhysicalIsFRU.10 == false(2)
entPhysicalMfgDate.10 == '2002-7-26,13:30:15.0,-4:0'
entPhysicalUris.10 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.10 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.10 == acmeProducts.portTypes.2
entPhysicalContainedIn.10 == 8
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 2
entPhysicalName.10 == 'Ethernet A'
entPhysicalHardwareRev.10 == 'G(1.04)'
entPhysicalSoftwareRev.10 == ''
entPhysicalFirmwareRev.10 == '1.3'
entPhysicalSerialNum.10 == ''
entPhysicalMfgName.10 == 'Acme'
entPhysicalModelName.10 == 'FE-100'
entPhysicalAlias.10 == ''
entPhysicalAssetID.10 == ''
entPhysicalIsFRU.10 == false(2)
entPhysicalMfgDate.10 == '2002-7-26,13:30:15.0,-4:0'
entPhysicalUris.10 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.11 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.11 == acmeProducts.portTypes.2
entPhysicalContainedIn.11 == 8
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 3
entPhysicalName.11 == 'Ethernet B'
entPhysicalHardwareRev.11 == 'G(1.04)'
entPhysicalSoftwareRev.11 == ''
entPhysicalFirmwareRev.11 == '1.3'
entPhysicalSerialNum.11 == ''
entPhysicalMfgName.11 == 'Acme'
entPhysicalDescr.11 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.11 == acmeProducts.portTypes.2
entPhysicalContainedIn.11 == 8
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 3
entPhysicalName.11 == 'Ethernet B'
entPhysicalHardwareRev.11 == 'G(1.04)'
entPhysicalSoftwareRev.11 == ''
entPhysicalFirmwareRev.11 == '1.3'
entPhysicalSerialNum.11 == ''
entPhysicalMfgName.11 == 'Acme'
entPhysicalModelName.11 == 'FE-100'
entPhysicalAlias.11 == ''
entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2)
entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0'
entPhysicalUris.11 == 'URN:CLEI:CNMES23ARA'
entPhysicalModelName.11 == 'FE-100'
entPhysicalAlias.11 == ''
entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2)
entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0'
entPhysicalUris.11 == 'URN:CLEI:CNMES23ARA'
Logical entities -- entLogicalTable; no SNMPv3 support
2 OSPF instances:
entLogicalDescr.1 == 'Acme OSPF v1.1'
entLogicalType.1 == ospf
entLogicalCommunity.1 == 'public-ospf1'
entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == ''
entLogicalContextName.1 == ''
Logical entities -- entLogicalTable; no SNMPv3 support
2 OSPF instances:
entLogicalDescr.1 == 'Acme OSPF v1.1'
entLogicalType.1 == ospf
entLogicalCommunity.1 == 'public-ospf1'
entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == ''
entLogicalContextName.1 == ''
entLogicalDescr.2 == 'Acme OSPF v1.1'
entLogicalType.2 == ospf
entLogicalCommunity.2 == 'public-ospf2'
entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == ''
entLogicalContextName.2 == ''
entLogicalDescr.2 == 'Acme OSPF v1.1'
entLogicalType.2 == ospf
entLogicalCommunity.2 == 'public-ospf2'
entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == ''
entLogicalContextName.2 == ''
2 logical bridges:
entLogicalDescr.3 == 'Acme Bridge v2.1.1'
entLogicalType.3 == dot1dBridge
entLogicalCommunity.3 == 'public-bridge1'
entLogicalTAddress.3 == 192.0.2.1:161
entLogicalTDomain.3 == snmpUDPDomain
entLogicalContextEngineID.3 == ''
entLogicalContextName.3 == ''
2 logical bridges:
entLogicalDescr.3 == 'Acme Bridge v2.1.1'
entLogicalType.3 == dot1dBridge
entLogicalCommunity.3 == 'public-bridge1'
entLogicalTAddress.3 == 192.0.2.1:161
entLogicalTDomain.3 == snmpUDPDomain
entLogicalContextEngineID.3 == ''
entLogicalContextName.3 == ''
entLogicalDescr.4 == 'Acme Bridge v2.1.1'
entLogicalType.4 == dot1dBridge
entLogicalCommunity.4 == 'public-bridge2'
entLogicalTAddress.4 == 192.0.2.1:161
entLogicalTDomain.4 == snmpUDPDomain
entLogicalContextEngineID.4 == ''
entLogicalContextName.4 == ''
entLogicalDescr.4 == 'Acme Bridge v2.1.1'
entLogicalType.4 == dot1dBridge
entLogicalCommunity.4 == 'public-bridge2'
entLogicalTAddress.4 == 192.0.2.1:161
entLogicalTDomain.4 == snmpUDPDomain
entLogicalContextEngineID.4 == ''
entLogicalContextName.4 == ''
Logical to Physical Mappings: 1st OSPF instance: uses module 1-port 1 entLPPhysicalIndex.1.5 == 5
逻辑到物理映射：第一个OSPF实例：使用模块1-port 1 entLPPhysicalIndex.1.5==5
2nd OSPF instance: uses module 2-port 1 entLPPhysicalIndex.2.9 == 9
第二个OSPF实例：使用模块2端口1 entLPPhysicalIndex.2.9==9
1st bridge group: uses module 1, all ports
第一网桥组：使用模块1，所有端口
Note that these mappings are included in the table because another logical entity (1st OSPF) utilizes one of the ports. If this were not the case, then a single mapping to the module (e.g., entLPPhysicalIndex.3.4) would be present instead.
请注意，这些映射包含在表中，因为另一个逻辑实体（第一个OSPF）使用其中一个端口。如果不是这种情况，则会出现到模块的单个映射（例如entLPPhysicalIndex.3.4）。
entLPPhysicalIndex.3.5 == 5
entLPPhysicalIndex.3.6 == 6
entLPPhysicalIndex.3.7 == 7
entLPPhysicalIndex.3.5 == 5
entLPPhysicalIndex.3.6 == 6
entLPPhysicalIndex.3.7 == 7
2nd bridge group: uses module 2, all ports
entLPPhysicalIndex.4.9 == 9
entLPPhysicalIndex.4.10 == 10
entLPPhysicalIndex.4.11 == 11
2nd bridge group: uses module 2, all ports
entLPPhysicalIndex.4.9 == 9
entLPPhysicalIndex.4.10 == 10
entLPPhysicalIndex.4.11 == 11
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable:
Example 1: ifIndex values are global to all logical entities
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.11.0 == ifIndex.6
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable:
Example 1: ifIndex values are global to all logical entities
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.11.0 == ifIndex.6
Example 2: ifIndex values are not shared by all logical entities;
(Bridge-1 uses ifIndex values 101 - 103 and Bridge-2 uses
ifIndex values 204-206.)
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.5.3 == ifIndex.101
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.6.3 == ifIndex.102
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.7.3 == ifIndex.103
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.9.4 == ifIndex.204
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.10.4 == ifIndex.205
entAliasMappingIdentifier.11.0 == ifIndex.6
entAliasMappingIdentifier.11.4 == ifIndex.206
Example 2: ifIndex values are not shared by all logical entities;
(Bridge-1 uses ifIndex values 101 - 103 and Bridge-2 uses
ifIndex values 204-206.)
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.5.3 == ifIndex.101
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.6.3 == ifIndex.102
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.7.3 == ifIndex.103
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.9.4 == ifIndex.204
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.10.4 == ifIndex.205
entAliasMappingIdentifier.11.0 == ifIndex.6
entAliasMappingIdentifier.11.4 == ifIndex.206
Physical Containment Tree -- entPhysicalContainsTable
chassis has two containers:
entPhysicalChildIndex.1.2 == 2
entPhysicalChildIndex.1.3 == 3
Physical Containment Tree -- entPhysicalContainsTable
chassis has two containers:
entPhysicalChildIndex.1.2 == 2
entPhysicalChildIndex.1.3 == 3
container 1 has a module: entPhysicalChildIndex.2.4 == 4
容器1有一个模块：entPhysicalChildIndex.2.4==4
container 2 has a module: entPhysicalChildIndex.3.8 == 8
容器2有一个模块：entPhysicalChildIndex.3.8==8
module 1 has 3 ports:
entPhysicalChildIndex.4.5 == 5
entPhysicalChildIndex.4.6 == 6
entPhysicalChildIndex.4.7 == 7
module 1 has 3 ports:
entPhysicalChildIndex.4.5 == 5
entPhysicalChildIndex.4.6 == 6
entPhysicalChildIndex.4.7 == 7
module 2 has 3 ports:
entPhysicalChildIndex.8.9 == 9
entPhysicalChildIndex.8.10 == 10
entPhysicalChildIndex.8.11 == 11
module 2 has 3 ports:
entPhysicalChildIndex.8.9 == 9
entPhysicalChildIndex.8.10 == 10
entPhysicalChildIndex.8.11 == 11
The second example is a 3-slot hub with 2 backplane ethernet segments. Slot three is empty, and the remaining slots contain ethernet repeater modules.
第二个示例是具有2个背板以太网段的3插槽集线器。插槽3为空，其余插槽包含以太网中继器模块。
Note that this example assumes an older Repeater MIB implementation [RFC1516] rather than the new Repeater MIB [RFC2108]. The new version contains an object called 'rptrPortRptrId', which should be used to identify repeater port groupings, rather than using community strings or contexts.
请注意，此示例假定旧的中继器MIB实现[RFC1516]，而不是新的中继器MIB[RFC2108]。新版本包含一个名为“rportrptrid”的对象，该对象应用于标识中继器端口分组，而不是使用社区字符串或上下文。
Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 110'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 ==0
entPhysicalName.1 == '110-B'
entPhysicalHardwareRev.1 == 'A(1.02.00)'
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'C100079294'
entPhysicalMfgName.1 == 'Acme'
entPhysicalModelName.1 == '110'
entPhysicalAlias.1 == 'bldg09:floor1:rptr18:0067eea0229f'
Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 110'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 ==0
entPhysicalName.1 == '110-B'
entPhysicalHardwareRev.1 == 'A(1.02.00)'
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'C100079294'
entPhysicalMfgName.1 == 'Acme'
entPhysicalModelName.1 == '110'
entPhysicalAlias.1 == 'bldg09:floor1:rptr18:0067eea0229f'
entPhysicalAssetID.1 == '0007386327'
entPhysicalIsFRU.1 == true(1)
entPhysicalAssetID.1 == '0007386327'
entPhysicalIsFRU.1 == true(1)
2 Chassis Ethernet Backplanes:
entPhysicalDescr.2 == 'Acme Ethernet Backplane Type A'
entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == backplane(4)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'B1'
entPhysicalHardwareRev.2 == 'A(2.04.01)'
entPhysicalSoftwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'Acme'
entPhysicalModelName.2 == 'BK-A'
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
2 Chassis Ethernet Backplanes:
entPhysicalDescr.2 == 'Acme Ethernet Backplane Type A'
entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == backplane(4)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'B1'
entPhysicalHardwareRev.2 == 'A(2.04.01)'
entPhysicalSoftwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'Acme'
entPhysicalModelName.2 == 'BK-A'
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
entPhysicalDescr.3 == 'Acme Ethernet Backplane Type A'
entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == backplane(4)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'B2'
entPhysicalHardwareRev.3 == 'A(2.04.01)'
entPhysicalSoftwareRev.3 == ''
entPhysicalFirmwareRev.3 == ''
entPhysicalSerialNum.3 == ''
entPhysicalMfgName.3 == 'Acme'
entPhysicalModelName.3 == 'BK-A'
entPhysicalAlias.3 == ''
entPhysicalAssetID.3 == ''
entPhysicalIsFRU.3 == false(2)
entPhysicalDescr.3 == 'Acme Ethernet Backplane Type A'
entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == backplane(4)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'B2'
entPhysicalHardwareRev.3 == 'A(2.04.01)'
entPhysicalSoftwareRev.3 == ''
entPhysicalFirmwareRev.3 == ''
entPhysicalSerialNum.3 == ''
entPhysicalMfgName.3 == 'Acme'
entPhysicalModelName.3 == 'BK-A'
entPhysicalAlias.3 == ''
entPhysicalAssetID.3 == ''
entPhysicalIsFRU.3 == false(2)
3 slots within the chassis:
entPhysicalDescr.4 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.4 == acmeProducts.slotTypes.5
entPhysicalContainedIn.4 == 1
entPhysicalClass.4 == container(5)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'Slot 1'
entPhysicalHardwareRev.4 == 'B(1.00.03)'
entPhysicalSoftwareRev.4 == ''
entPhysicalFirmwareRev.4 == ''
entPhysicalSerialNum.4 == ''
entPhysicalMfgName.4 == 'Acme'
3 slots within the chassis:
entPhysicalDescr.4 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.4 == acmeProducts.slotTypes.5
entPhysicalContainedIn.4 == 1
entPhysicalClass.4 == container(5)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'Slot 1'
entPhysicalHardwareRev.4 == 'B(1.00.03)'
entPhysicalSoftwareRev.4 == ''
entPhysicalFirmwareRev.4 == ''
entPhysicalSerialNum.4 == ''
entPhysicalMfgName.4 == 'Acme'
entPhysicalModelName.4 == 'RB'
entPhysicalAlias.4 == ''
entPhysicalAssetID.4 == ''
entPhysicalIsFRU.4 == false(2)
entPhysicalModelName.4 == 'RB'
entPhysicalAlias.4 == ''
entPhysicalAssetID.4 == ''
entPhysicalIsFRU.4 == false(2)
entPhysicalDescr.5 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.5 == acmeProducts.slotTypes.5
entPhysicalContainedIn.5 == 1
entPhysicalClass.5 == container(5)
entPhysicalParentRelPos.5 == 2
entPhysicalName.5 == 'Slot 2'
entPhysicalHardwareRev.5 == 'B(1.00.03)'
entPhysicalSoftwareRev.5 == ''
entPhysicalFirmwareRev.5 == ''
entPhysicalSerialNum.5 == ''
entPhysicalMfgName.5 == 'Acme'
entPhysicalModelName.5 == 'RB'
entPhysicalAlias.5 == ''
entPhysicalAssetID.5 == ''
entPhysicalIsFRU.5 == false(2)
entPhysicalDescr.5 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.5 == acmeProducts.slotTypes.5
entPhysicalContainedIn.5 == 1
entPhysicalClass.5 == container(5)
entPhysicalParentRelPos.5 == 2
entPhysicalName.5 == 'Slot 2'
entPhysicalHardwareRev.5 == 'B(1.00.03)'
entPhysicalSoftwareRev.5 == ''
entPhysicalFirmwareRev.5 == ''
entPhysicalSerialNum.5 == ''
entPhysicalMfgName.5 == 'Acme'
entPhysicalModelName.5 == 'RB'
entPhysicalAlias.5 == ''
entPhysicalAssetID.5 == ''
entPhysicalIsFRU.5 == false(2)
entPhysicalDescr.6 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.6 == acmeProducts.slotTypes.5
entPhysicalContainedIn.6 == 1
entPhysicalClass.6 == container(5)
entPhysicalParentRelPos.6 == 3
entPhysicalName.6 == 'Slot 3'
entPhysicalHardwareRev.6 == 'B(1.00.03)'
entPhysicalSoftwareRev.6 == ''
entPhysicalFirmwareRev.6 == ''
entPhysicalSerialNum.6 == ''
entPhysicalMfgName.6 == 'Acme'
entPhysicalModelName.6 == 'RB'
entPhysicalAlias.6 == ''
entPhysicalAssetID.6 == ''
entPhysicalIsFRU.6 == false(2)
entPhysicalDescr.6 == 'Acme Hub Slot Type RB'
entPhysicalVendorType.6 == acmeProducts.slotTypes.5
entPhysicalContainedIn.6 == 1
entPhysicalClass.6 == container(5)
entPhysicalParentRelPos.6 == 3
entPhysicalName.6 == 'Slot 3'
entPhysicalHardwareRev.6 == 'B(1.00.03)'
entPhysicalSoftwareRev.6 == ''
entPhysicalFirmwareRev.6 == ''
entPhysicalSerialNum.6 == ''
entPhysicalMfgName.6 == 'Acme'
entPhysicalModelName.6 == 'RB'
entPhysicalAlias.6 == ''
entPhysicalAssetID.6 == ''
entPhysicalIsFRU.6 == false(2)
Slot 1 contains a plug-in module with 4 10-BaseT ports:
entPhysicalDescr.7 == 'Acme 10Base-T Module 114'
entPhysicalVendorType.7 == acmeProducts.moduleTypes.32
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == module(9)
entPhysicalParentRelPos.7 == 1
entPhysicalName.7 == 'M1'
entPhysicalHardwareRev.7 == 'A(1.02.01)'
entPhysicalSoftwareRev.7 == '1.7.2'
entPhysicalFirmwareRev.7 == 'A(1.5)'
entPhysicalSerialNum.7 == 'C100096244'
Slot 1 contains a plug-in module with 4 10-BaseT ports:
entPhysicalDescr.7 == 'Acme 10Base-T Module 114'
entPhysicalVendorType.7 == acmeProducts.moduleTypes.32
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == module(9)
entPhysicalParentRelPos.7 == 1
entPhysicalName.7 == 'M1'
entPhysicalHardwareRev.7 == 'A(1.02.01)'
entPhysicalSoftwareRev.7 == '1.7.2'
entPhysicalFirmwareRev.7 == 'A(1.5)'
entPhysicalSerialNum.7 == 'C100096244'
entPhysicalMfgName.7 == 'Acme'
entPhysicalModelName.7 = '114'
entPhysicalAlias.7 == 'bldg09:floor1:eng'
entPhysicalAssetID.7 == '0007962951'
entPhysicalIsFRU.7 == true(1)
entPhysicalMfgName.7 == 'Acme'
entPhysicalModelName.7 = '114'
entPhysicalAlias.7 == 'bldg09:floor1:eng'
entPhysicalAssetID.7 == '0007962951'
entPhysicalIsFRU.7 == true(1)
entPhysicalDescr.8 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.8 == acmeProducts.portTypes.10
entPhysicalContainedIn.8 == 7
entPhysicalClass.8 == port(10)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'Ethernet-A'
entPhysicalHardwareRev.8 == 'A(1.04F)'
entPhysicalSoftwareRev.8 == ''
entPhysicalFirmwareRev.8 == '1.4'
entPhysicalSerialNum.8 == ''
entPhysicalMfgName.8 == 'Acme'
entPhysicalModelName.8 == 'RB'
entPhysicalAlias.8 == ''
entPhysicalAssetID.8 == ''
entPhysicalIsFRU.8 == false(2)
entPhysicalDescr.8 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.8 == acmeProducts.portTypes.10
entPhysicalContainedIn.8 == 7
entPhysicalClass.8 == port(10)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'Ethernet-A'
entPhysicalHardwareRev.8 == 'A(1.04F)'
entPhysicalSoftwareRev.8 == ''
entPhysicalFirmwareRev.8 == '1.4'
entPhysicalSerialNum.8 == ''
entPhysicalMfgName.8 == 'Acme'
entPhysicalModelName.8 == 'RB'
entPhysicalAlias.8 == ''
entPhysicalAssetID.8 == ''
entPhysicalIsFRU.8 == false(2)
entPhysicalDescr.9 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.9 == acmeProducts.portTypes.10
entPhysicalContainedIn.9 == 7
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 2
entPhysicalName.9 == 'Ethernet-B'
entPhysicalHardwareRev.9 == 'A(1.04F)'
entPhysicalSoftwareRev.9 == ''
entPhysicalFirmwareRev.9 == '1.4'
entPhysicalSerialNum.9 == ''
entPhysicalMfgName.9 == 'Acme'
entPhysicalModelName.9 = 'RB'
entPhysicalAlias.9 == ''
entPhysicalAssetID.9 == ''
entPhysicalIsFRU.9 == false(2)
entPhysicalDescr.9 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.9 == acmeProducts.portTypes.10
entPhysicalContainedIn.9 == 7
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 2
entPhysicalName.9 == 'Ethernet-B'
entPhysicalHardwareRev.9 == 'A(1.04F)'
entPhysicalSoftwareRev.9 == ''
entPhysicalFirmwareRev.9 == '1.4'
entPhysicalSerialNum.9 == ''
entPhysicalMfgName.9 == 'Acme'
entPhysicalModelName.9 = 'RB'
entPhysicalAlias.9 == ''
entPhysicalAssetID.9 == ''
entPhysicalIsFRU.9 == false(2)
entPhysicalDescr.10 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.10 == acmeProducts.portTypes.10
entPhysicalContainedIn.10 == 7
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 3
entPhysicalName.10 == 'Ethernet-C'
entPhysicalHardwareRev.10 == 'B(1.02.07)'
entPhysicalSoftwareRev.10 == ''
entPhysicalFirmwareRev.10 == '1.4'
entPhysicalSerialNum.10 == ''
entPhysicalDescr.10 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.10 == acmeProducts.portTypes.10
entPhysicalContainedIn.10 == 7
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 3
entPhysicalName.10 == 'Ethernet-C'
entPhysicalHardwareRev.10 == 'B(1.02.07)'
entPhysicalSoftwareRev.10 == ''
entPhysicalFirmwareRev.10 == '1.4'
entPhysicalSerialNum.10 == ''
entPhysicalMfgName.10 == 'Acme'
entPhysicalModelName.10 == 'RB'
entPhysicalAlias.10 == ''
entPhysicalAssetID.10 == ''
entPhysicalIsFRU.10 == false(2)
entPhysicalMfgName.10 == 'Acme'
entPhysicalModelName.10 == 'RB'
entPhysicalAlias.10 == ''
entPhysicalAssetID.10 == ''
entPhysicalIsFRU.10 == false(2)
entPhysicalDescr.11 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 4
entPhysicalName.11 == 'Ethernet-D'
entPhysicalHardwareRev.11 == 'B(1.02.07)'
entPhysicalSoftwareRev.11 == ''
entPhysicalFirmwareRev.11 == '1.4'
entPhysicalSerialNum.11 == ''
entPhysicalMfgName.11 == 'Acme'
entPhysicalModelName.11 == 'RB'
entPhysicalAlias.11 == ''
entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2)
entPhysicalDescr.11 == 'Acme 10Base-T Port RB'
entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 4
entPhysicalName.11 == 'Ethernet-D'
entPhysicalHardwareRev.11 == 'B(1.02.07)'
entPhysicalSoftwareRev.11 == ''
entPhysicalFirmwareRev.11 == '1.4'
entPhysicalSerialNum.11 == ''
entPhysicalMfgName.11 == 'Acme'
entPhysicalModelName.11 == 'RB'
entPhysicalAlias.11 == ''
entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2)
Slot 2 contains another ethernet module with 2 ports.
entPhysicalDescr.12 == 'Acme 10Base-T Module Model 4'
entPhysicalVendorType.12 == acmeProducts.moduleTypes.30
entPhysicalContainedIn.12 = 5
entPhysicalClass.12 == module(9)
entPhysicalParentRelPos.12 == 1
entPhysicalName.12 == 'M2'
entPhysicalHardwareRev.12 == 'A(1.01.07)'
entPhysicalSoftwareRev.12 == '1.8.4'
entPhysicalFirmwareRev.12 == 'A(1.8)'
entPhysicalSerialNum.12 == 'C100102384'
entPhysicalMfgName.12 == 'Acme'
entPhysicalModelName.12 == '4'
entPhysicalAlias.12 == 'bldg09:floor1:devtest'
entPhysicalAssetID.12 == '0007968462'
entPhysicalIsFRU.12 == true(1)
Slot 2 contains another ethernet module with 2 ports.
entPhysicalDescr.12 == 'Acme 10Base-T Module Model 4'
entPhysicalVendorType.12 == acmeProducts.moduleTypes.30
entPhysicalContainedIn.12 = 5
entPhysicalClass.12 == module(9)
entPhysicalParentRelPos.12 == 1
entPhysicalName.12 == 'M2'
entPhysicalHardwareRev.12 == 'A(1.01.07)'
entPhysicalSoftwareRev.12 == '1.8.4'
entPhysicalFirmwareRev.12 == 'A(1.8)'
entPhysicalSerialNum.12 == 'C100102384'
entPhysicalMfgName.12 == 'Acme'
entPhysicalModelName.12 == '4'
entPhysicalAlias.12 == 'bldg09:floor1:devtest'
entPhysicalAssetID.12 == '0007968462'
entPhysicalIsFRU.12 == true(1)
entPhysicalDescr.13 == 'Acme 802.3 AUI Port'
entPhysicalVendorType.13 == acmeProducts.portTypes.11
entPhysicalContainedIn.13 == 12
entPhysicalClass.13 == port(10)
entPhysicalParentRelPos.13 == 1
entPhysicalName.13 == 'AUI'
entPhysicalHardwareRev.13 == 'A(1.06F)'
entPhysicalSoftwareRev.13 == ''
entPhysicalFirmwareRev.13 == '1.5'
entPhysicalDescr.13 == 'Acme 802.3 AUI Port'
entPhysicalVendorType.13 == acmeProducts.portTypes.11
entPhysicalContainedIn.13 == 12
entPhysicalClass.13 == port(10)
entPhysicalParentRelPos.13 == 1
entPhysicalName.13 == 'AUI'
entPhysicalHardwareRev.13 == 'A(1.06F)'
entPhysicalSoftwareRev.13 == ''
entPhysicalFirmwareRev.13 == '1.5'
entPhysicalSerialNum.13 == ''
entPhysicalMfgName.13 == 'Acme'
entPhysicalModelName.13 == ''
entPhysicalAlias.13 == ''
entPhysicalAssetID.13 == ''
entPhysicalIsFRU.13 == false(2)
entPhysicalSerialNum.13 == ''
entPhysicalMfgName.13 == 'Acme'
entPhysicalModelName.13 == ''
entPhysicalAlias.13 == ''
entPhysicalAssetID.13 == ''
entPhysicalIsFRU.13 == false(2)
entPhysicalDescr.14 == 'Acme 10Base-T Port RD'
entPhysicalVendorType.14 == acmeProducts.portTypes.14
entPhysicalContainedIn.14 == 12
entPhysicalClass.14 == port(10)
entPhysicalParentRelPos.14 == 2
entPhysicalName.14 == 'E2'
entPhysicalHardwareRev.14 == 'B(1.01.02)'
entPhysicalSoftwareRev.14 == ''
entPhysicalFirmwareRev.14 == '2.1'
entPhysicalSerialNum.14 == ''
entPhysicalMfgName.14 == 'Acme'
entPhysicalModelName.14 == ''
entPhysicalAlias.14 == ''
entPhysicalAssetID.14 == ''
entPhysicalIsFRU.14 == false(2)
entPhysicalDescr.14 == 'Acme 10Base-T Port RD'
entPhysicalVendorType.14 == acmeProducts.portTypes.14
entPhysicalContainedIn.14 == 12
entPhysicalClass.14 == port(10)
entPhysicalParentRelPos.14 == 2
entPhysicalName.14 == 'E2'
entPhysicalHardwareRev.14 == 'B(1.01.02)'
entPhysicalSoftwareRev.14 == ''
entPhysicalFirmwareRev.14 == '2.1'
entPhysicalSerialNum.14 == ''
entPhysicalMfgName.14 == 'Acme'
entPhysicalModelName.14 == ''
entPhysicalAlias.14 == ''
entPhysicalAssetID.14 == ''
entPhysicalIsFRU.14 == false(2)
Logical entities -- entLogicalTable; with SNMPv3 support
Repeater 1--comprised of any ports attached to backplane 1
entLogicalDescr.1 == 'Acme repeater v3.1'
entLogicalType.1 == snmpDot3RptrMgt
entLogicalCommunity.1 'public-repeater1'
entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == '80000777017c7d7e7f'H
entLogicalContextName.1 == 'repeater1'
Logical entities -- entLogicalTable; with SNMPv3 support
Repeater 1--comprised of any ports attached to backplane 1
entLogicalDescr.1 == 'Acme repeater v3.1'
entLogicalType.1 == snmpDot3RptrMgt
entLogicalCommunity.1 'public-repeater1'
entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == '80000777017c7d7e7f'H
entLogicalContextName.1 == 'repeater1'
Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == 'Acme repeater v3.1'
entLogicalType.2 == snmpDot3RptrMgt
entLogicalCommunity.2 == 'public-repeater2'
entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == '80000777017c7d7e7f'H
entLogicalContextName.2 == 'repeater2'
Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == 'Acme repeater v3.1'
entLogicalType.2 == snmpDot3RptrMgt
entLogicalCommunity.2 == 'public-repeater2'
entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == '80000777017c7d7e7f'H
entLogicalContextName.2 == 'repeater2'
Logical to Physical Mappings -- entLPMappingTable:
逻辑到物理映射--entLPMappingTable:
repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1
中继器1使用背板1、插槽1-端口1和2、插槽2-端口1
Note that a mapping to the module is not included, because this example represents a port-switchable hub. Even though all ports on the module could belong to the same repeater as a matter of configuration, the LP port mappings should not be replaced dynamically with a single mapping for the module (e.g., entLPPhysicalIndex.1.7). If all ports on the module shared a single backplane connection, then a single mapping for the module would be more appropriate.
请注意，不包括到模块的映射，因为此示例表示端口可切换集线器。即使模块上的所有端口在配置上可能属于同一中继器，LP端口映射也不应动态替换为模块的单个映射（例如，entLPPhysicalIndex.1.7）。如果模块上的所有端口共享一个背板连接，则模块的单个映射更合适。
entLPPhysicalIndex.1.2 == 2
entLPPhysicalIndex.1.8 == 8
entLPPhysicalIndex.1.9 == 9
entLPPhysicalIndex.1.13 == 13
entLPPhysicalIndex.1.2 == 2
entLPPhysicalIndex.1.8 == 8
entLPPhysicalIndex.1.9 == 9
entLPPhysicalIndex.1.13 == 13
repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
entLPPhysicalIndex.2.3 == 3
entLPPhysicalIndex.2.10 == 10
entLPPhysicalIndex.2.11 == 11
entLPPhysicalIndex.2.14 == 14
repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
entLPPhysicalIndex.2.3 == 3
entLPPhysicalIndex.2.10 == 10
entLPPhysicalIndex.2.11 == 11
entLPPhysicalIndex.2.14 == 14
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable:
Repeater Port Identifier values are shared by both repeaters:
entAliasMappingIdentifier.8.0 == rptrPortGroupIndex.1.1
entAliasMappingIdentifier.9.0 == rptrPortGroupIndex.1.2
entAliasMappingIdentifier.10.0 == rptrPortGroupIndex.1.3
entAliasMappingIdentifier.11.0 == rptrPortGroupIndex.1.4
entAliasMappingIdentifier.13.0 == rptrPortGroupIndex.2.1
entAliasMappingIdentifier.14.0 == rptrPortGroupIndex.2.2
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable:
Repeater Port Identifier values are shared by both repeaters:
entAliasMappingIdentifier.8.0 == rptrPortGroupIndex.1.1
entAliasMappingIdentifier.9.0 == rptrPortGroupIndex.1.2
entAliasMappingIdentifier.10.0 == rptrPortGroupIndex.1.3
entAliasMappingIdentifier.11.0 == rptrPortGroupIndex.1.4
entAliasMappingIdentifier.13.0 == rptrPortGroupIndex.2.1
entAliasMappingIdentifier.14.0 == rptrPortGroupIndex.2.2
Physical Containment Tree -- entPhysicalContainsTable
chassis has two backplanes and three containers:
entPhysicalChildIndex.1.2 == 2
entPhysicalChildIndex.1.3 == 3
entPhysicalChildIndex.1.4 == 4
entPhysicalChildIndex.1.5 == 5
entPhysicalChildIndex.1.6 == 6
Physical Containment Tree -- entPhysicalContainsTable
chassis has two backplanes and three containers:
entPhysicalChildIndex.1.2 == 2
entPhysicalChildIndex.1.3 == 3
entPhysicalChildIndex.1.4 == 4
entPhysicalChildIndex.1.5 == 5
entPhysicalChildIndex.1.6 == 6
container 1 has a module: entPhysicalChildIndex.4.7 == 7
容器1有一个模块：entPhysicalChildIndex.4.7==7
container 2 has a module entPhysicalChildIndex.5.12 == 12
容器2有一个模块entPhysicalChildIndex.5.12==12
Note that in this example, container 3 is empty.
注意，在本例中，容器3是空的。
module 1 has 4 ports:
entPhysicalChildIndex.7.8 == 8
entPhysicalChildIndex.7.9 == 9
module 1 has 4 ports:
entPhysicalChildIndex.7.8 == 8
entPhysicalChildIndex.7.9 == 9
entPhysicalChildIndex.7.10 == 10
entPhysicalChildIndex.7.11 == 11
entPhysicalChildIndex.7.10 == 10
entPhysicalChildIndex.7.11 == 11
module 2 has 2 ports:
entPhysicalChildIndex.12.13 == 13
entPhysicalChildIndex.12.14 == 14
module 2 has 2 ports:
entPhysicalChildIndex.12.13 == 13
entPhysicalChildIndex.12.14 == 14
As an example, to illustrate the use of the MIB objects introduced with Energy Management (EMAN) applications, consider a router that has 16 slots with line cards. An example of the entPhysicalTable is given for 3 components of the router, a chassis, a slot, and a line card in that slot. The chassis contains the slot, and the slot contains the line card.
作为一个例子，为了说明使用能量管理（MAN）应用的MIB对象的使用，考虑具有线卡的16个时隙的路由器。entPhysicalTable的一个示例用于路由器的3个组件、机箱、插槽和该插槽中的线路卡。机箱包含插槽，插槽包含线路卡。
entPhysicalDescr.1 == 'ACME Series 16 Slots'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == -1
entPhysicalName.1 == 'Router 0 Chassis'
entPhysicalHardwareRev.1 == ''
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'abcd1234'
entPhysicalMfgName.1 == 'ACME'
entPhysicalModelName.1 == 'ACME-16-LCC'
entPhysicalAlias.1 == ''
entPhysicalAssetID.1 == ''
entPhysicalIsFRU.1 == true(1)
entPhysicalMfgDate.1 == '2008-7-28,13:30:30.0,-4:0'
entPhysicalUris.1 == 'urn:f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
entPhysicalUUID.1 == 'f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
entPhysicalDescr.1 == 'ACME Series 16 Slots'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == -1
entPhysicalName.1 == 'Router 0 Chassis'
entPhysicalHardwareRev.1 == ''
entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'abcd1234'
entPhysicalMfgName.1 == 'ACME'
entPhysicalModelName.1 == 'ACME-16-LCC'
entPhysicalAlias.1 == ''
entPhysicalAssetID.1 == ''
entPhysicalIsFRU.1 == true(1)
entPhysicalMfgDate.1 == '2008-7-28,13:30:30.0,-4:0'
entPhysicalUris.1 == 'urn:f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
entPhysicalUUID.1 == 'f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
entPhysicalDescr.2 == 'ACME Line Card Slot'
entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 = container(5)
entPhysicalParentRelPos.2 == 6
entPhysicalName.2 == 'Slot 6'
entPhysicalHardwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSoftwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'ACME'
entPhysicalModelName.2 == ''
entPhysicalDescr.2 == 'ACME Line Card Slot'
entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 = container(5)
entPhysicalParentRelPos.2 == 6
entPhysicalName.2 == 'Slot 6'
entPhysicalHardwareRev.2 == ''
entPhysicalFirmwareRev.2 == ''
entPhysicalSoftwareRev.2 == ''
entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'ACME'
entPhysicalModelName.2 == ''
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
entPhysicalUris.2 == ''urn:7dc53df5-703e-49b3-8670-b1c468f47f1f'
entPhysicalUUID.2 == '7dc53df5-703e-49b3-8670-b1c468f47f1f'
entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2)
entPhysicalUris.2 == ''urn:7dc53df5-703e-49b3-8670-b1c468f47f1f'
entPhysicalUUID.2 == '7dc53df5-703e-49b3-8670-b1c468f47f1f'
entPhysicalDescr.4 == 'ACME Series1 Line Card'
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 0
entPhysicalName.4 == 'Series1 Linecard'
entPhysicalHardwareRev.4 == ''
entPhysicalFirmwareRev.4 == ''
entPhysicalSoftwareRev.4 == ''
entPhysicalSerialNum.4 == ''
entPhysicalMfgName.4 == 'ACME'
entPhysicalModelName.4 == ''
entPhysicalAlias.4 == ''
entPhysicalAssetID.4 == ''
entPhysicalIsFRU.4 == true(1)
entPhysicalUris.4 == 'urn:01c47915-4777-11d8-bc70-0090272ff725'
entPhysicalUUID.4 == '01c47915-4777-11d8-bc70-0090272ff725'
entPhysicalDescr.4 == 'ACME Series1 Line Card'
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 0
entPhysicalName.4 == 'Series1 Linecard'
entPhysicalHardwareRev.4 == ''
entPhysicalFirmwareRev.4 == ''
entPhysicalSoftwareRev.4 == ''
entPhysicalSerialNum.4 == ''
entPhysicalMfgName.4 == 'ACME'
entPhysicalModelName.4 == ''
entPhysicalAlias.4 == ''
entPhysicalAssetID.4 == ''
entPhysicalIsFRU.4 == true(1)
entPhysicalUris.4 == 'urn:01c47915-4777-11d8-bc70-0090272ff725'
entPhysicalUUID.4 == '01c47915-4777-11d8-bc70-0090272ff725'
There are a number of management objects defined in these MIB modules with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
在这些MIB模块中定义了许多管理对象，其中MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
entPhysicalSerialNum entPhysicalAlias entPhysicalAssetID entPhysicalUris
entPhysicalSerialNum entPhysicalAlias entPhysicalAssetID entPhysicalUris
These objects contain information about the physical entities within a managed system, which may be used to identify the serial number, identification of assets and managed components, and handling of the managed objects. Their mis-configuration or disclosure may reveal sensitive information on assets, perturb the management of entities, or cause privacy issues if they allow tracking of values that are personally identifying.
这些对象包含有关受管系统内物理实体的信息，这些信息可用于标识序列号、资产和受管组件的标识以及受管对象的处理。他们的错误配置或披露可能会泄露资产的敏感信息，扰乱实体的管理，或者如果他们允许跟踪个人识别的价值，则会导致隐私问题。
Some of the readable objects in these MIB modules (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，这些MIB模块中的一些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
entPhysicalDescr entPhysicalVendorType entPhysicalHardwareRev entPhysicalFirmwareRev entPhysicalSoftwareRev entPhysicalMfgName entPhysicalModelName entPhysicalUUID
EntPhysicalDescrr entPhysicalVendorType entPhysicalHardwareRev entPhysicalFirmwareRev entPhysicalSoftwareRev EntPhysicalFGName entPhysicalModelName entPhysicalUUID
These objects expose information about the physical entities within a managed system, which may be used to identify the vendor, model, version, and specific device-identification information of each system component.
这些对象公开有关受管系统内物理实体的信息，这些信息可用于标识每个系统组件的供应商、型号、版本和特定设备标识信息。
entLogicalDescr entLogicalType
EntLogicalDeskr entLogicalType
These objects expose the type of logical entities present in the managed system.
这些对象公开托管系统中存在的逻辑实体的类型。
entLogicalCommunity
内部逻辑社区
This object exposes community names associated with particular logical entities within the system.
此对象公开与系统中特定逻辑实体关联的团体名称。
entLogicalTAddress entLogicalTDomain
EntLogicalAddress EntLogicalDomain
These objects expose network addresses that can be used to communicate with an SNMP agent on behalf of particular logical entities within the system.
这些对象公开可用于代表系统内特定逻辑实体与SNMP代理通信的网络地址。
entLogicalContextEngineID entLogicalContextName
entLogicalContextEngineID entLogicalContextName
These objects identify the authoritative SNMP engine that contains information on behalf of particular logical entities within the system.
这些对象标识包含代表系统内特定逻辑实体的信息的权威SNMP引擎。
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 these MIB modules.
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 these MIB modules.translate error, please retry
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 these MIB modules 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实体进行了正确配置，以便仅向那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）授予对对象的访问权。
This document defines the first version of the IANA-maintained IANA-ENTITY-MIB module, which allows new physical classes to be added to the enumeration in IANAPhysicalClass. An Expert Review, as defined in RFC 5226 [RFC5226], is REQUIRED for each modification.
本文档定义了IANA维护的IANA-ENTITY-MIB模块的第一个版本，该模块允许向IANAPhysicalClass中的枚举添加新的物理类。根据RFC 5226[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
---------- -----------------------
entityMIB { mib-2 47 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
entityMIB { mib-2 47 }
IANA has allocated two OBJECT IDENTIFIERS under mib-2 for:
IANA已在mib-2下为以下对象分配了两个对象标识符：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
ianaEntityMIB { mib-2 216 }
uuidTCMIB { mib-2 217 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
ianaEntityMIB { mib-2 216 }
uuidTCMIB { mib-2 217 }
The first three versions of RFCs on the ENTITY MIB modules were authored by A. Bierman and K. McCloghrie. The authors would like to thank A. Bierman and K. McCloghrie for the earlier versions of the ENTITY MIB.
实体MIB模块上RFC的前三个版本由A.Bierman和K.McCloghrie编写。作者要感谢A.Bierman和K.McCloghrie提供了实体MIB的早期版本。
The motivation for the extension to RFC 4133 stems from the requirements of the EMAN WG of the IETF.
扩展到RFC 4133的动机来自IETF的EMAN工作组的要求。
The authors also thank Juergen Schoenwaelder for his review and comments for improving this document.
作者还感谢Juergen Schoenwaeld对改进本文件的评论和评论。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年12月。
[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.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月。
[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.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，2004年6月。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005.translate error, please retry
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", RFC 5591, June 2009.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，RFC 55912009年6月。
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 55922009年6月。
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", RFC 6353, July 2011.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，RFC 63532011年7月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol (SNMP)", RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.，和J.Davin，“简单网络管理协议（SNMP）”，RFC 1157，1990年5月。
[RFC1516] McMaster, D. and K. McCloghrie, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices", RFC 1516, September 1993.
[RFC1516]McMaster，D.和K.McCloghrie，“IEEE 802.3中继器设备的受管对象定义”，RFC 1516，1993年9月。
[RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. McCloghrie, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, February 1997.
[RFC2108]de Graaf，K.，Romascan，D.，McMaster，D.，和K.McCloghrie，“使用SMIv2的IEEE 802.3中继器设备的受管对象定义”，RFC 2108，1997年2月。
[RFC2037] McCloghrie, K. and A. Bierman, "Entity MIB using SMIv2", RFC 2037, October 1996.
[RFC2037]McCloghrie，K.和A.Bierman，“使用SMIv2的实体MIB”，RFC 2037，1996年10月。
[RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 2)", RFC 2737, December 1999.
[RFC2737]McCloghrie，K.和A.Bierman，“实体MIB（版本2）”，RFC 27371999年12月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005.
[RFC4133]Bierman，A.和K.McCloghrie，“实体MIB（版本3）”，RFC 41332005年8月。
[RFC4152] Tesink, K. and R. Fox, "A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code", RFC 4152, August 2005.
[RFC4152]Tesink，K.和R.Fox，“公共语言设备标识符（CLEI）代码的统一资源名称（URN）命名空间”，RFC 4152，2005年8月。
[RFC4188] Norseth, K., Ed., and E. Bell, Ed., "Definitions of Managed Objects for Bridges", RFC 4188, September 2005.
[RFC4188]Norseth，K.，Ed.，和E.Bell，Ed.，“网桥托管对象的定义”，RFC 4188，2005年9月。
[T1.213] ATIS T1.213-2001, "Coded Identification of Equipment Entities in the North American Telecommunications System for Information Exchange", 2001, <www.ansi.org>.
[T1.213]ATIS T1.213-2001，“北美电信系统中用于信息交换的设备实体的编码标识”，2001年，<www.ansi.org>。
[T1.213a] ATIS T1.213a, "Supplement to T1.213-2001, Coded Identification of Equipment Entities in the North American Telecommunications System for Information Exchange, to Correct the Representation of the Basic Code in Figure B.1", 2001, <www.ansi.org>.
[T1.213a] ATIS T1.213a, "Supplement to T1.213-2001, Coded Identification of Equipment Entities in the North American Telecommunications System for Information Exchange, to Correct the Representation of the Basic Code in Figure B.1", 2001, <www.ansi.org>.translate error, please retry
Authors' Addresses
Authors' Addressestranslate error, please retry
Andy Bierman YumaWorks, Inc. 274 Redwood Shores Parkway, #133 Redwood City, CA 94065 USA
Andy Bierman YumaWorks，Inc.美国加利福尼亚州红木市133号红木海岸公园路274号，邮编94065
Phone: +1 408-716-0466
EMail: andy@yumaworks.com
Phone: +1 408-716-0466
EMail: andy@yumaworks.com
Dan Romascanu Avaya Park Atidim, Bldg. #3 Tel Aviv, 61581 Israel
Dan Romascanu Avaya Park Atidim，特拉维夫3号楼，以色列61581
Phone: +972-3-6458414
EMail: dromasca@avaya.com
Phone: +972-3-6458414
EMail: dromasca@avaya.com
Juergen Quittek NEC Europe Ltd. Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany
Juergen Quittek NEC欧洲有限公司网络研究部Kurfuersten Anlage 36德国海德堡69115
Phone: +49 6221 4342-115
EMail: quittek@neclab.eu
Phone: +49 6221 4342-115
EMail: quittek@neclab.eu
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