Network Working Group A. Bierman
Request for Comments: 2922 Cisco Systems, Inc.
Category: Informational K. Jones
Nortel Networks
September 2000
Network Working Group A. Bierman
Request for Comments: 2922 Cisco Systems, Inc.
Category: Informational K. Jones
Nortel Networks
September 2000
Physical Topology MIB
物理拓扑MIB
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
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 physical topology identification and discovery.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于管理物理拓扑标识和发现的托管对象。
Table of Contents
目录
1 The SNMP Network Management Framework ............................2
2 Overview .........................................................3
2.1 Terms ..........................................................3
2.2 Design Goals ...................................................5
3 Topology Framework ...............................................6
3.1 Devices and Topology Agents ....................................6
3.2 Topology Mechanisms ............................................7
3.3 Future Considerations ..........................................7
4 Physical Topology MIB ............................................7
4.1 Persistent Identifiers .........................................8
4.2 Relationship to Entity MIB .....................................8
4.3 Relationship to Interfaces MIB .................................9
4.4 Relationship to RMON-2 MIB .....................................9
4.5 Relationship to Bridge MIB .....................................9
4.6 Relationship to Repeater MIB ...................................9
4.7 MIB Structure .................................................10
4.7.1 ptopoData Group .............................................10
4.7.2 ptopoGeneral Group ..........................................10
4.7.3 ptopoConfig Group ...........................................10
4.8 Physical Topology MIB Definitions .............................10
1 The SNMP Network Management Framework ............................2
2 Overview .........................................................3
2.1 Terms ..........................................................3
2.2 Design Goals ...................................................5
3 Topology Framework ...............................................6
3.1 Devices and Topology Agents ....................................6
3.2 Topology Mechanisms ............................................7
3.3 Future Considerations ..........................................7
4 Physical Topology MIB ............................................7
4.1 Persistent Identifiers .........................................8
4.2 Relationship to Entity MIB .....................................8
4.3 Relationship to Interfaces MIB .................................9
4.4 Relationship to RMON-2 MIB .....................................9
4.5 Relationship to Bridge MIB .....................................9
4.6 Relationship to Repeater MIB ...................................9
4.7 MIB Structure .................................................10
4.7.1 ptopoData Group .............................................10
4.7.2 ptopoGeneral Group ..........................................10
4.7.3 ptopoConfig Group ...........................................10
4.8 Physical Topology MIB Definitions .............................10
5 Intellectual Property ...........................................27
6 Acknowledgements ................................................28
7 References ......................................................28
8 Security Considerations .........................................30
9 Authors' Addresses ..............................................31
10 Full Copyright Statement .......................................32
5 Intellectual Property ...........................................27
6 Acknowledgements ................................................28
7 References ......................................................28
8 Security Considerations .........................................30
9 Authors' Addresses ..............................................31
10 Full Copyright Statement .......................................32
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [RFC2571].
o RFC 2571[RFC2571]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[RFC1155]、STD 16、RFC 1212[RFC1212]和RFC 1215[RFC1215]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15 RFC 1157[RFC1157]中进行了描述。SNMP消息协议的第二个版本不是Internet标准跟踪协议，称为SNMPv2c，在RFC 1901[RFC1901]和RFC 1906[RFC1906]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[RFC1906]、RFC 2572[RFC2572]和RFC 2574[RFC2574]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905].
o 访问管理信息的协议操作。STD 15、RFC 1157[RFC1157]中描述了第一组协议操作和相关PDU格式。RFC 1905[RFC1905]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575].
o RFC 2573[RFC2573]中描述的一组基本应用程序和RFC 2575[RFC2575]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[RFC2570]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
There is a need for a standardized means of representing the physical network connections pertaining to a given management domain. The Physical Topology MIB (PTOPO-MIB) provides a standard way to identify connections between network ports and to discover network addresses of SNMP agents containing management information associated with each port.
需要一种标准化的方法来表示与给定管理域相关的物理网络连接。物理拓扑MIB（PTOPO-MIB）提供了一种标准方法来识别网络端口之间的连接，并发现包含与每个端口相关的管理信息的SNMP代理的网络地址。
A topology mechanism is used to discover the information required by the PTOPO-MIB. There is a need for a standardized topology mechanism to increase the likelihood of multi-vendor interoperability of such physical topology management information. The PTOPO-MIB does not, however, specify or restrict the discovery mechanism(s) used for an implementation of the PTOPO-MIB. Topology mechanisms exist for certain media types (such as FDDI) and proprietary mechanisms exist for other media such as shared media Ethernet, switched Ethernet, and Token Ring. Rather than specifying mechanisms for each type of technology, the PTOPO-MIB allows co-existence of multiple topology mechanisms. The required objects of the PTOPO-MIB define the core requirements for any topology mechanism.
拓扑机制用于发现PTOPO-MIB所需的信息。需要一种标准化的拓扑机制来增加这种物理拓扑管理信息的多供应商互操作性的可能性。但是，PTOPO-MIB并未指定或限制用于实现PTOPO-MIB的发现机制。拓扑机制适用于某些媒体类型（如FDDI），专有机制适用于其他媒体，如共享媒体以太网、交换以太网和令牌环。PTOPO-MIB允许多个拓扑机制共存，而不是为每种类型的技术指定机制。PTOPO-MIB所需的对象定义了任何拓扑机制的核心需求。
The scope of the physical topology (PTOPO) mechanism is the identification of connections between two network ports. Network addresses of SNMP agents containing management information associated with each port can also be identified.
物理拓扑（PTOPO）机制的范围是识别两个网络端口之间的连接。还可以识别包含与每个端口关联的管理信息的SNMP代理的网络地址。
Some terms are used throughout this document:
本文件中使用了一些术语：
Physical Topology Physical topology represents the topology model for layer 1 of the OSI stack - the physical layer. Physical topology consists of identifying the devices on the network and how they are physically interconnected. By definition of this document, physical topology does not imply a physical relationship between ports on the same device. Other means exist for
物理拓扑物理拓扑表示OSI堆栈第1层（物理层）的拓扑模型。物理拓扑包括识别网络上的设备以及它们如何进行物理互连。根据本文档的定义，物理拓扑并不意味着同一设备上的端口之间存在物理关系。还有其他方法可供选择
determining these relationships (e.g., Entity MIB [RFC2737]) exist for determining these relationships. Note that physical topology is independent of logical topology, which associates ports based on higher layer attributes, such as network layer address.
确定这些关系（例如，实体MIB[RFC2737]）可用于确定这些关系。请注意，物理拓扑独立于逻辑拓扑，逻辑拓扑基于更高层属性（如网络层地址）关联端口。
Chassis A chassis is a physical component which contains other physical components. It is identified by an entPhysicalEntry with an entPhysicalClass value of 'chassis(3)' and an entPhysicalContainedIn value of zero. A chassis identifier consists of a globally unique SnmpAdminString.
机箱机箱是包含其他物理组件的物理组件。它由entPhysicalEntry标识，entPhysicalClass值为“机箱（3）”，entPhysicalContainedIn值为零。机箱标识符由全局唯一的SNMPAdministring组成。
Local Chassis The particular chassis containing the SNMP agent implementing the PTOPO MIB.
本地机箱包含实现PTOPO MIB的SNMP代理的特定机箱。
Port A port is a physical component which can be connected to another port through some medium. It is identified by an entPhysicalEntry with an entPhysicalClass value of 'port(10)'. A port identifier consists of an SnmpAdminString which must be unique within the context of the chassis which contains the port.
端口端口是一个物理组件，可以通过某种介质连接到另一个端口。它由entPhysicalEntry标识，entPhysicalClass值为“端口（10）”。端口标识符由SnmpAdminString组成，该SnmpAdminString在包含端口的机箱上下文中必须是唯一的。
Connection Endpoint A connection endpoint consists of a physical port, which is contained within a single physical chassis.
连接端点连接端点由物理端口组成，该端口包含在单个物理机箱中。
Connection Endpoint Identifier A connection endpoint is identified by a globally unique chassis identifier and a port identifier unique within the associated chassis.
连接端点标识符连接端点由全局唯一的机箱标识符和关联机箱内唯一的端口标识符标识。
Connection A connection consists of two physical ports, and the attached physical medium, configured for the purpose of transferring network traffic between the ports. A connection is identified by its endpoint identifiers.
连接连接由两个物理端口和连接的物理介质组成，配置用于在端口之间传输网络流量。连接由其端点标识符标识。
Non-local Connection A connection for which neither endpoint is located on the local chassis.
非本地连接两个端点都不在本地机箱上的连接。
Cloud A cloud identifies a portion of the topology for which insufficient information is known to completely infer the interconnection of devices that make up that portion of the topology.
云：云标识拓扑的一部分，已知的信息不足，无法完全推断构成该部分拓扑的设备的互连。
Several factors influenced the design of this physical topology function:
影响此物理拓扑功能设计的几个因素：
- Simplicity The physical topology discovery function should be as simple as possible, exposing only the information needed to identify connection endpoints and the SNMP agent(s) associated with each connection endpoint.
- 简单性物理拓扑发现功能应尽可能简单，只公开标识连接端点和与每个连接端点关联的SNMP代理所需的信息。
- Completeness At least one standard discovery protocol capable of supporting the standard physical topology MIB must be defined. Multi-vendor interoperability will not be achievable unless a simple and extensible discovery protocol is available. However, the PTOPO MIB should not specify or restrict the topology discovery mechanisms an agent can use.
- 完整性必须至少定义一个能够支持标准物理拓扑MIB的标准发现协议。除非有一个简单且可扩展的发现协议可用，否则无法实现多供应商互操作性。但是，PTOPO MIB不应指定或限制代理可以使用的拓扑发现机制。
- No Functional Overlap Existing standard MIBs should be utilized whenever possible. Physical topology information is tightly coupled to functionality found in the Interfaces MIB [RFC2233] and Entity MIB [RFC2737]. New physical topology MIB objects should not duplicate these MIBs.
- 尽可能不使用现有标准MIB的功能重叠。物理拓扑信息与接口MIB[RFC2233]和实体MIB[RFC2737]中的功能紧密耦合。新的物理拓扑MIB对象不应与这些MIB重复。
- Identifier Stability Connection endpoint identifiers must be persistent (i.e. stable across device reboots). Dynamic primary key objects like ifIndex and entPhysicalIndex are not suitable for table indices in a physical topology MIB that is replicated and distributed throughout a managed system.
- 标识符稳定性连接端点标识符必须是持久性的（即在设备重新启动时保持稳定）。像ifIndex和entPhysicalIndex这样的动态主键对象不适用于在整个托管系统中复制和分布的物理拓扑MIB中的表索引。
- Identifier Flexibility Persistent string-based component identifiers should be supported from many sources. Chassis identifiers may be found in the Entity MIB [RFC2737], and port identifiers may be found in the Interfaces MIB [RFC2233] or Entity MIB [RFC2737].
- 标识符灵活性基于字符串的持久化组件标识符应该受到许多来源的支持。机箱标识符可以在实体MIB[RFC2737]中找到，端口标识符可以在接口MIB[RFC2233]或实体MIB[RFC2737]中找到。
- Partial Topology Support Physical topology data for remote components may only be partially available to an agent. An enumerated INTEGER hierarchy of component identifier types allows for incomplete physical connection identifier information to be substituted with secondary information such as unicast source MAC address or network address associated with a particular port. A PTOPO Agent maintains information derived from the 'best' source of information for each connection. If a 'better' identifier source is detected, the PTOPO entries are updated accordingly. It is an implementation specific matter whether a PTOPO agent replaces 'old' entries or retains them, however an agent must remove information known to be incorrect.
- 部分拓扑支持远程组件的物理拓扑数据只能部分用于代理。组件标识符类型的枚举整数层次结构允许将不完整的物理连接标识符信息替换为辅助信息，如单播源MAC地址或与特定端口关联的网络地址。PTOPO代理维护来自每个连接的“最佳”信息源的信息。如果检测到“更好”的标识符源，则相应地更新PTOPO条目。PTOPO代理是替换“旧”条目还是保留它们是实现特有的问题，但是代理必须删除已知不正确的信息。
- Low Polling Impact Physical topology polling should be minimized through techniques such as TimeFiltered data tables (from RMON-2 [RFC2021]), and last-change notifications.
- 低轮询影响物理拓扑轮询应通过时间过滤数据表（来自RMON-2[RFC2021]）和最后更改通知等技术最小化。
This section describes the physical topology framework in detail.
本节详细介绍物理拓扑框架。
The network devices, along with their physical connectivity, make up the physical topology. Some of these devices (but maybe not all) provide management agents that report their local physical topology information to a manager via the physical topology MIB.
网络设备及其物理连接构成了物理拓扑。其中一些设备（但可能不是全部）提供管理代理，这些代理通过物理拓扑MIB向管理器报告其本地物理拓扑信息。
These devices include communication infrastructure devices, such as hubs, switches, and routers, as well as 'leaf' devices such as workstations, printers, and servers. Generally, user data passes through infrastructure devices while leaf devices are sources and sinks of data. Both types of devices may implement the physical topology MIB, although implementation within leaf devices is much less critical.
这些设备包括通信基础设施设备，如集线器、交换机和路由器，以及“叶子”设备，如工作站、打印机和服务器。通常，用户数据通过基础设施设备传递，而叶设备是数据的源和汇。这两种类型的设备都可以实现物理拓扑MIB，尽管在叶设备中实现的重要性要小得多。
Each managed device collects physical topology information from the network, based on the topology mechanism(s) it is configured to use. The data represents this agent's local view of the physical network. Part of the topology data collected must include the identification of other local agents which may contain additional topology information. The definition of 'local' varies based on the topology mechanism or mechanisms being used.
每个受管设备根据其配置使用的拓扑机制从网络收集物理拓扑信息。数据表示此代理对物理网络的本地视图。收集的部分拓扑数据必须包括可能包含其他拓扑信息的其他本地代理的标识。“局部”的定义因所使用的拓扑机制而异。
A topology mechanism is a means, possibly requiring some sort of protocol, by which devices determine topology information. The topology mechanism must provide sufficient information to populate the MIB described later in this document.
拓扑机制是一种手段，可能需要某种协议，设备通过它确定拓扑信息。拓扑机制必须提供足够的信息来填充本文档后面描述的MIB。
Topology mechanisms can be active or passive. Active mechanisms require a device to send and receive topology protocol packets. These packets provide the device ID of the source of the packet and may also indicate out which port the packet was transmitted. When receiving these packets, devices typically are required to identify on which port that packet was received.
拓扑机制可以是主动的，也可以是被动的。主动机制要求设备发送和接收拓扑协议数据包。这些分组提供分组源的设备ID，并且还可以指示分组被发送到哪个端口。当接收这些数据包时，设备通常需要识别在哪个端口上接收到该数据包。
Passive mechanisms take advantage of data on the network to populate the topology MIB. By maintaining a list of device identifiers seen on each port of all devices in a network, it is possible to populate the PTOPO-MIB.
被动机制利用网络上的数据填充拓扑MIB。通过维护网络中所有设备的每个端口上的设备标识符列表，可以填充PTOPO-MIB。
Many instances of a particular topology mechanism may be in use on a given network, and many different mechanisms may be employed. In some cases, multiple mechanisms may overlap across part of the physical topology with individual ports supporting more than one topology mechanism. In general, this simply allows the port to collect more robust topology information. Agents may need to be configured so that they know which mechanism(s) are in use on any given portion of the network.
特定拓扑机制的许多实例可在给定网络上使用，并且可采用许多不同的机制。在某些情况下，多个机制可能会在部分物理拓扑上重叠，单个端口支持多个拓扑机制。通常，这只允许端口收集更健壮的拓扑信息。可能需要对代理进行配置，以便它们知道在网络的任何给定部分上正在使用哪些机制。
Most topology mechanisms need to be bounded to a subset of the network to contain their impact on the network and limit the size of topology tables maintained by the agent. Topology mechanisms are often naturally bounded by the media on which they run (e.g. FDDI topology mechanism) or by routers in the network that intentionally block the mechanism from crossing into other parts of the network.
大多数拓扑机制需要绑定到网络的子集，以包含它们对网络的影响，并限制代理维护的拓扑表的大小。拓扑机制通常由其运行的介质（例如FDDI拓扑机制）或网络中的路由器（有意阻止该机制进入网络的其他部分）自然限定。
While the framework presented here is focused on physical topology, it may well be that the topology mechanisms and MIB described could be extended to include logical topology information as well. That is not a focus of this memo.
虽然本文介绍的框架侧重于物理拓扑，但很可能描述的拓扑机制和MIB也可以扩展到包括逻辑拓扑信息。这不是这份备忘录的重点。
This section describes and defines the Physical Topology MIB.
本节描述并定义物理拓扑MIB。
The PTOPO MIB utilizes non-volatile identifiers to distinguish individual chassis and port components. These identifiers are associated with external objects in order to relate topology information to the existing managed objects.
PTOPO MIB利用非易失性标识符来区分各个机箱和端口组件。这些标识符与外部对象关联，以便将拓扑信息与现有托管对象关联。
In particular, an object from the Entity MIB [RFC2737] or Interfaces MIB [RFC2233] can be used as the 'reference-point' for a connection component identifier.
具体而言，来自实体MIB[RFC2737]或接口MIB[RFC2233]的对象可以用作连接组件标识符的“参考点”。
The Physical Topology MIB uses two identifier types pertaining to the PTOPO MIB:
物理拓扑MIB使用两种与PTOPO MIB相关的标识符类型：
- globally unique chassis identifiers.
- 全局唯一的机箱标识符。
- port identifiers; unique only within the chassis which contains the port.
- 端口标识符；仅在包含端口的机箱中唯一。
Identifiers are stored as OCTET STRINGs, which are limited to 32 bytes in length, This supports flexible naming conventions and constrains the non-volatile storage requirements for an agent.
标识符存储为八位字符串，长度限制为32字节，这支持灵活的命名约定，并限制了代理的非易失性存储要求。
The first version of the Entity MIB [RFC2037] allows the physical component inventory and hierarchy to be identified. However, this MIB does not provide persistent component identifiers, which are required for the PTOPO MIB. Therefore, version 2 of the Entity MIB [RFC2737] is required to support that feature. Specifically, the entPhysicalAlias object is utilized as a persistent chassis identifier.
实体MIB的第一个版本[RFC2037]允许识别物理组件清单和层次结构。但是，此MIB不提供PTOPO MIB所需的持久组件标识符。因此，需要实体MIB[RFC2737]的版本2来支持该特性。具体而言，entPhysicalAlias对象用作持久化机箱标识符。
For agents implementing the PTOPO MIB, this new object must be used to represent the chassis identifier. Port identifiers can be based on the entPhysicalAlias object associated with the port, but only if the port is not represented as an interface in the ifXTable.
对于实现PTOPO MIB的代理，必须使用此新对象来表示机箱标识符。端口标识符可以基于与端口关联的entPhysicalAlias对象，但前提是该端口未在ifXTable中表示为接口。
Implementation of the entPhysicalGroup [RFC2737] and the entPhysicalAlias object [RFC2737] are mandatory for SNMP agents which implement the PTOPO MIB. No other objects must be implemented from these MIBs to support the physical topology function.
对于实现PTOPO MIB的SNMP代理，必须实现entPhysicalGroup[RFC2737]和entPhysicalAlias对象[RFC2737]。为了支持物理拓扑功能，不必从这些MIB实现其他对象。
The PTOPO MIB requires a persistent identifier for each port. The Interfaces MIB [RFC2233] provides a standard mechanism for managing network interfaces. Unfortunately, not all ports which may be represented in the PTOPO MIB are also represented in the Interfaces MIB (e.g., repeater ports).
PTOPO MIB需要每个端口的持久标识符。接口MIB[RFC2233]提供了一种管理网络接口的标准机制。不幸的是，并非所有可能在PTOPO MIB中表示的端口也在接口MIB中表示（例如，中继器端口）。
For agents which implement the PTOPO MIB, for each port also represented in the Interfaces MIB, the agent must use the associated ifAlias value for the port identifier. For each port not represented in the Interfaces MIB, the associated entPhysicalAlias value must be used for the port identifier. Note that the PTOPO MIB requires only minimal support from the Interfaces MIB. Specifically, the ' ifGeneralInformationGroup' level of conformance must be provided for each port also identified in the PTOPO MIB. The agent may choose to support these objects with read-only access, as specified in the conformance section of the Interfaces MIB.
对于实现PTOPO MIB的代理，对于接口MIB中表示的每个端口，代理必须使用关联的ifAlias值作为端口标识符。对于接口MIB中未表示的每个端口，端口标识符必须使用关联的entPhysicalAlias值。注意，PTOPO MIB只需要接口MIB的最小支持。具体而言，必须为PTOPO MIB中标识的每个端口提供“ifGeneralInformationGroup”一致性级别。代理可以选择以只读访问方式支持这些对象，如接口MIB的一致性部分所述。
The RMON-2 MIB [RFC2021] contains address mapping information which can be integrated with physical topology information. The physical ports identified in a physical topology MIB can be related to the MAC and network layer addresses found in the addressMapTable.
RMON-2 MIB[RFC2021]包含可以与物理拓扑信息集成的地址映射信息。物理拓扑MIB中标识的物理端口可以与addressMapTable中的MAC和网络层地址相关。
The Bridge MIB [RFC1493] contains information which may relate to physical ports represented in the ptopoConnTable. Entries in the dot1dBasePortTable and dot1dStpPortTable can by related to physical ports represented in the PTOPO MIB. Also, bridge port MAC addresses may be used as chassis and port identifiers in some situations.
网桥MIB[RFC1493]包含可能与ptopocontable中表示的物理端口相关的信息。dot1dBasePortTable和DOT1DSTPortTable中的条目可以与PTOPO MIB中表示的物理端口相关。此外，在某些情况下，网桥端口MAC地址可用作机箱和端口标识符。
The Repeater MIB [RFC2108] contains information which may relate to physical ports represented in the PTOPO MIB. Entries in the rptrPortTable and rptrMonitorPortTable can by related to physical ports represented in the ptopoConnTable. Entries in the rptrInfoTable and rptrMonTable can be related to repeater backplanes possibly represented in the ptopoConnTable.
中继器MIB[RFC2108]包含可能与PTOPO MIB中表示的物理端口相关的信息。rptrPortTable和rptrMonitorPortTable中的条目可以与ptopocontable中表示的物理端口相关。rptrInfoTable和rptrMonTable中的条目可能与PTOPOCONTABLE中可能表示的中继器背板相关。
The PTOPO MIB contains three MIB object groups:
PTOPO MIB包含三个MIB对象组：
- ptopoData Exposes physical topology data learned from discovery protocols and/or manual configuration.
- ptopoData公开从发现协议和/或手动配置中学习到的物理拓扑数据。
- ptopoGeneral Contains general information regarding PTOPO MIB status.
- PTOPO概述包含有关PTOPO MIB状态的一般信息。
- ptopoConfig Contains configuration variables for the PTOPO MIB agent function.
- ptopoConfig包含PTOPO MIB代理函数的配置变量。
This group contains a single table to identity physical topology data.
此组包含用于标识物理拓扑数据的单个表。
The ptopoConnTable contains information about the connections learned or configured on behalf of the PTOPO MIB SNMP Agent.
ptopoConnTable包含关于代表PTOPO MIB SNMP代理学习或配置的连接的信息。
This group contains some scalar objects to report the status of the PTOPO MIB information currently known to the SNMP Agent. The global last change time, and table add and delete counters allow an NMS to set threshold alarms to trigger PTOPO polling.
此组包含一些标量对象，用于报告SNMP代理当前已知的PTOPO MIB信息的状态。全局上次更改时间以及表添加和删除计数器允许NMS设置阈值报警以触发PTOPO轮询。
This group contains tables to configure the behavior of the physical topology function. The transmission of ptopoLastChange notifications can be configured using the ptopoConfigTrapInterval scalar MIB object.
此组包含用于配置物理拓扑功能行为的表。可以使用ptopoConfigTrapInterval标量MIB对象配置ptopoLastChange通知的传输。
PTOPO-MIB DEFINITIONS ::= BEGIN
PTOPO-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, Counter32, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, AutonomousType, RowStatus, TimeStamp, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
从SNMPv2 SMI文本约定导入模块标识、对象类型、通知类型、整数32、计数器32、mib-2、自治类型、行状态、时间戳、SNMPv2 TC模块符合性的TruthValue、对象组、通知组
FROM SNMPv2-CONF TimeFilter FROM RMON2-MIB PhysicalIndex FROM ENTITY-MIB AddressFamilyNumbers FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB;
来自SNMPv2 CONF TimeFilter，来自RMON2-MIB物理索引，来自ENTITY-MIB AddressFamilyNumber，来自IANA-ADDRESS-FAMILY-Number-MIB；
ptopoMIB MODULE-IDENTITY LAST-UPDATED "200009210000Z" ORGANIZATION "IETF; PTOPOMIB Working Group" CONTACT-INFO "PTOPOMIB WG Discussion: ptopo@3com.com Subscription: majordomo@3com.com msg body: [un]subscribe ptopomib
ptopoMIB模块标识最后更新“2000092100Z”组织“IETF”；ptopoMIB工作组“联系方式”ptopoMIB工作组讨论：ptopo@3com.com订阅：majordomo@3com.com消息正文：[un]订阅ptopomib
Andy Bierman Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 408-527-3711 abierman@cisco.com
安迪·比尔曼思科系统公司，加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134 408-527-3711abierman@cisco.com
Kendall S. Jones
Nortel Networks
4401 Great America Parkway
Santa Clara, CA 95054
408-495-7356
kejones@nortelnetworks.com"
DESCRIPTION
"The MIB module for physical topology information."
REVISION "200009210000Z"
DESCRIPTION
"Initial Version of the Physical Topology MIB. This version
published as RFC 2922."
::= { mib-2 79 }
Kendall S. Jones
Nortel Networks
4401 Great America Parkway
Santa Clara, CA 95054
408-495-7356
kejones@nortelnetworks.com"
DESCRIPTION
"The MIB module for physical topology information."
REVISION "200009210000Z"
DESCRIPTION
"Initial Version of the Physical Topology MIB. This version
published as RFC 2922."
::= { mib-2 79 }
ptopoMIBObjects OBJECT IDENTIFIER ::= { ptopoMIB 1 }
ptopoMIBObjects OBJECT IDENTIFIER ::= { ptopoMIB 1 }
-- MIB groups
ptopoData OBJECT IDENTIFIER ::= { ptopoMIBObjects 1 }
ptopoGeneral OBJECT IDENTIFIER ::= { ptopoMIBObjects 2 }
ptopoConfig OBJECT IDENTIFIER ::= { ptopoMIBObjects 3 }
-- MIB groups
ptopoData OBJECT IDENTIFIER ::= { ptopoMIBObjects 1 }
ptopoGeneral OBJECT IDENTIFIER ::= { ptopoMIBObjects 2 }
ptopoConfig OBJECT IDENTIFIER ::= { ptopoMIBObjects 3 }
-- textual conventions
--文本约定
PtopoGenAddr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of an address."
SYNTAX OCTET STRING (SIZE (0..20))
PtopoGenAddr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of an address."
SYNTAX OCTET STRING (SIZE (0..20))
PtopoChassisIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a chassis identifier.
PtopoChassisIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a chassis identifier.
The enumeration 'chasIdEntPhysicalAlias(1)' represents a chassis identifier based on the value of entPhysicalAlias for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
枚举“chasIdEntPhysicalAlias（1）”表示基于机箱组件的entPhysicalAlias值的机箱标识符（即“机箱（3）”的entPhysicalClass值）。
The enumeration 'chasIdIfAlias(2)' represents a chassis identifier based on the value of ifAlias for an interface on the containing chassis.
枚举“chasIdIfAlias（2）”表示基于包含机箱上接口的ifAlias值的机箱标识符。
The enumeration 'chasIdPortEntPhysicalAlias(3)' represents a chassis identifier based on the value of entPhysicalAlias for a port or backplane component (i.e., entPhysicalClass value of 'port(10)' or 'backplane(4)'), within the containing chassis.
枚举“chasIdPortEntPhysicalAlias（3）”表示基于包含机箱内端口或背板组件的entPhysicalAlias值（即entPhysicalClass值“port（10）”或“backplane（4）”的机箱标识符。
The enumeration 'chasIdMacAddress(4)' represents a chassis identifier based on the value of a unicast source MAC address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis.
枚举“chasIdMacAddress（4）”表示基于包含机箱上端口的单播源MAC地址（以网络字节顺序和IEEE 802.3规范位顺序编码）值的机箱标识符。
The enumeration 'chasIdPtopoGenAddr(5)' represents a
chassis identifier based on a network address, associated
with a particular chassis. The encoded address is actually
composed of two fields. The first field is a single octet,
representing the IANA AddressFamilyNumbers value for the
specific address type, and the second field is the
PtopoGenAddr address value."
SYNTAX INTEGER {
chasIdEntPhysicalAlias(1),
chasIdIfAlias(2),
chasIdPortEntPhysicalAlias(3),
chasIdMacAddress(4),
chasIdPtopoGenAddr(5)
}
The enumeration 'chasIdPtopoGenAddr(5)' represents a
chassis identifier based on a network address, associated
with a particular chassis. The encoded address is actually
composed of two fields. The first field is a single octet,
representing the IANA AddressFamilyNumbers value for the
specific address type, and the second field is the
PtopoGenAddr address value."
SYNTAX INTEGER {
chasIdEntPhysicalAlias(1),
chasIdIfAlias(2),
chasIdPortEntPhysicalAlias(3),
chasIdMacAddress(4),
chasIdPtopoGenAddr(5)
}
PtopoChassisId ::= TEXTUAL-CONVENTION
STATUS current
PtopoChassisId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This TC describes the format of a chassis identifier string. Objects of this type are always used with an associated PtopoChassisIdType object, which identifies the format of the particular PtopoChassisId object instance.
DESCRIPTION“此TC描述机箱标识符字符串的格式。此类型的对象始终与关联的ptopochassidtype对象一起使用，该对象标识特定ptopochassid对象实例的格式。
If the associated PtopoChassisIdType object has a value of 'chasIdEntPhysicalAlias(1)', then the octet string identifies a particular instance of the entPhysicalAlias object for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
如果关联的ptopochassidtype对象的值为“chasIdEntPhysicalAlias（1）”，则八位字节字符串标识机箱组件的entPhysicalAlias对象的特定实例（即entPhysicalClass值为“chassis（3）”。
If the associated PtopoChassisIdType object has a value of 'chasIdIfAlias(2)', then the octet string identifies a particular instance of the ifAlias object for an interface on the containing chassis.
如果关联的ptopochassidtype对象的值为“chasIdIfAlias（2）”，则八进制字符串为包含机箱上的接口标识ifAlias对象的特定实例。
If the associated PtopoChassisIdType object has a value of 'chasIdPortEntPhysicalAlias(3)', then the octet string identifies a particular instance of the entPhysicalAlias object for a port or backplane component within the containing chassis.
如果关联的PtopochassidType对象的值为“chasIdPortEntPhysicalAlias（3）”，则八位字节字符串为包含机箱内的端口或背板组件标识entPhysicalAlias对象的特定实例。
If the associated PtopoChassisIdType object has a value of 'chasIdMacAddress(4)', then this string identifies a particular unicast source MAC address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis.
如果关联的ptopochassidtype对象的值为“chasIdMacAddress（4）”，则此字符串标识包含机箱上端口的特定单播源MAC地址（以网络字节顺序和IEEE 802.3规范位顺序编码）。
If the associated PtopoChassisIdType object has a value of 'chasIdPtopoGenAddr(5)', then this string identifies a particular network address, encoded in network byte order, associated with one or more ports on the containing chassis. The first octet contains the IANA Address Family Numbers enumeration value for the specific address type, and octets 2 through N contain the PtopoGenAddr address value in network byte order." SYNTAX OCTET STRING (SIZE (1..32))
如果关联的ptopochassidtype对象的值为“chasidTopogenaddr（5）”，则此字符串标识以网络字节顺序编码的特定网络地址，该地址与包含机箱上的一个或多个端口关联。第一个八位组包含特定地址类型的IANA地址系列号枚举值，第2到N个八位组包含网络字节顺序的PtopoGenAddr地址值。“语法八位组字符串（大小（1..32））
PtopoPortIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a particular type of port
identifier used in the PTOPO MIB.
PtopoPortIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a particular type of port
identifier used in the PTOPO MIB.
The enumeration 'portIdIfAlias(1)' represents a port identifier based on the ifAlias MIB object.
枚举“portIdIfAlias（1）”表示基于ifAlias MIB对象的端口标识符。
The enumeration 'portIdPortEntPhysicalAlias(2)' represents a port identifier based on the value of entPhysicalAlias for a port or backplane component (i.e., entPhysicalClass value of 'port(10)' or 'backplane(4)'), within the containing chassis.
枚举“portIdPortEntPhysicalAlias（2）”表示基于包含机箱内端口或背板组件的entPhysicalAlias值（即entPhysicalClass值“port（10）”或“backplane（4）”的端口标识符。
The enumeration 'portIdMacAddr(3)' represents a port identifier based on a unicast source MAC address, which has been detected by the agent and associated with a particular port.
枚举“portIdMacAddr（3）”表示基于单播源MAC地址的端口标识符，该地址已由代理检测并与特定端口关联。
The enumeration 'portIdPtopoGenAddr(4)' represents a port
identifier based on a network address, detected by the agent
and associated with a particular port."
SYNTAX INTEGER {
portIdIfAlias(1),
portIdEntPhysicalAlias(2),
portIdMacAddr(3),
portIdPtopoGenAddr(4)
}
The enumeration 'portIdPtopoGenAddr(4)' represents a port
identifier based on a network address, detected by the agent
and associated with a particular port."
SYNTAX INTEGER {
portIdIfAlias(1),
portIdEntPhysicalAlias(2),
portIdMacAddr(3),
portIdPtopoGenAddr(4)
}
PtopoPortId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the format of a port identifier string.
Objects of this type are always used with an associated
PtopoPortIdType object, which identifies the format of the
particular PtopoPortId object instance.
PtopoPortId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the format of a port identifier string.
Objects of this type are always used with an associated
PtopoPortIdType object, which identifies the format of the
particular PtopoPortId object instance.
If the associated PtopoPortIdType object has a value of 'portIdIfAlias(1)', then the octet string identifies a particular instance of the ifAlias object.
如果关联的ptoportidType对象的值为“portIdIfAlias（1）”，则八进制字符串标识ifAlias对象的特定实例。
If the associated PtopoPortIdType object has a value of 'portIdEntPhysicalAlias(2)', then the octet string identifies a particular instance of the entPhysicalAlias object for a port component (i.e., entPhysicalClass value of 'port(10)').
如果关联的PtopoPortIdType对象的值为“portIdEntPhysicalAlias（2）”，则八进制字符串标识端口组件的entPhysicalAlias对象的特定实例（即entPhysicalClass值为“port（10）”。
If the associated PtopoPortIdType object has a value of 'portIdMacAddr(3)', then this string identifies a particular unicast source MAC address associated with the port.
如果关联的ptoportidType对象的值为“portIdMacAddr（3）”，则此字符串标识与端口关联的特定单播源MAC地址。
If the associated PtopoPortIdType object has a value of 'portIdPtopoGenAddr(4)', then this string identifies a network address associated with the port. The first octet contains the IANA AddressFamilyNumbers enumeration value for the specific address type, and octets 2 through N contain
如果关联的ptoportidType对象的值为“portIdPtopoGenAddr（4）”，则此字符串标识与端口关联的网络地址。第一个八位组包含特定地址类型的IANA AddressFamilyNumber枚举值，八位组2到N包含
the PtopoGenAddr address value in network byte order." SYNTAX OCTET STRING (SIZE (1..32))
以网络字节顺序表示的PtopoGenAddr地址值。“语法八位字节字符串（大小（1..32））
PtopoAddrSeenState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the state of address detection for a
particular type of port identifier used in the PTOPO MIB.
PtopoAddrSeenState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the state of address detection for a
particular type of port identifier used in the PTOPO MIB.
The enumeration 'notUsed(1)' represents an entry for which the particular MIB object is not applicable to the remote connection endpoint,
枚举“notUsed（1）”表示特定MIB对象不适用于远程连接端点的条目，
The enumeration 'unknown(2)' represents an entry for which the particular address collection state is not known.
枚举“未知（2）”表示特定地址集合状态未知的条目。
The enumeration 'oneAddr(3)' represents an entry for which exactly one source address (of the type indicated by the particular MIB object), has been detected.
枚举“oneAddr（3）”表示仅检测到一个源地址（特定MIB对象指示的类型）的条目。
The enumeration 'multiAddr(4)' represents an entry for which more than one source address (of the type indicated by the particular MIB object), has been detected.
枚举“multiAddr（4）”表示已检测到多个源地址（由特定MIB对象指示的类型）的条目。
An agent is expected to set the initial state of the PtopoAddrSeenState to 'notUsed(1)' or 'unknown(2)'.
代理应将ptopoAddrSenState的初始状态设置为“未使用（1）”或“未知（2）”。
Note that the PTOPO MIB does not restrict or specify the
means in which the PtopoAddrSeenState is known to an agent.
In particular, an agent may detect this information through
configuration data, or some means other than directly
monitoring all port traffic."
SYNTAX INTEGER {
notUsed(1),
unknown(2),
oneAddr(3),
multiAddr(4)
}
Note that the PTOPO MIB does not restrict or specify the
means in which the PtopoAddrSeenState is known to an agent.
In particular, an agent may detect this information through
configuration data, or some means other than directly
monitoring all port traffic."
SYNTAX INTEGER {
notUsed(1),
unknown(2),
oneAddr(3),
multiAddr(4)
}
-- ***********************************************************
--
-- P T O P O D A T A G R O U P
--
-- ***********************************************************
-- ***********************************************************
--
-- P T O P O D A T A G R O U P
--
-- ***********************************************************
-- Connection Table
--连接表
ptopoConnTable OBJECT-TYPE SYNTAX SEQUENCE OF PtopoConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one ptopoConnEntry is present for each local port, or it may choose to maintain multiple ptopoConnEntries for the same local port.
ptopoconntry MAX-ACCESS的ptopoConnTable对象类型语法序列不可访问状态当前描述“此表包含此代理已知的每个物理网络连接的一行或多行。代理可能希望确保每个本地端口只存在一个ptopoConnEntry，或者可以选择为同一本地端口维护多个ptopoConnEntry。
Entries based on lower numbered identifier types are
preferred over higher numbered identifier types, i.e., lower
values of the ptopoConnRemoteChassisType and
ptopoConnRemotePortType objects."
::= { ptopoData 1 }
Entries based on lower numbered identifier types are
preferred over higher numbered identifier types, i.e., lower
values of the ptopoConnRemoteChassisType and
ptopoConnRemotePortType objects."
::= { ptopoData 1 }
ptopoConnEntry OBJECT-TYPE
SYNTAX PtopoConnEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular physical network connection.
Entries may be created and deleted in this table, either
manually or by the agent, if a physical topology discovery
process is active."
INDEX {
ptopoConnTimeMark,
ptopoConnLocalChassis,
ptopoConnLocalPort,
ptopoConnIndex
}
::= { ptopoConnTable 1 }
ptopoConnEntry OBJECT-TYPE
SYNTAX PtopoConnEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular physical network connection.
Entries may be created and deleted in this table, either
manually or by the agent, if a physical topology discovery
process is active."
INDEX {
ptopoConnTimeMark,
ptopoConnLocalChassis,
ptopoConnLocalPort,
ptopoConnIndex
}
::= { ptopoConnTable 1 }
PtopoConnEntry ::= SEQUENCE {
ptopoConnTimeMark TimeFilter,
ptopoConnLocalChassis PhysicalIndex,
ptopoConnLocalPort PhysicalIndex,
ptopoConnIndex Integer32,
ptopoConnRemoteChassisType PtopoChassisIdType,
ptopoConnRemoteChassis PtopoChassisId,
ptopoConnRemotePortType PtopoPortIdType,
ptopoConnRemotePort PtopoPortId,
ptopoConnDiscAlgorithm AutonomousType,
ptopoConnAgentNetAddrType AddressFamilyNumbers,
ptopoConnAgentNetAddr PtopoGenAddr,
ptopoConnMultiMacSASeen PtopoAddrSeenState,
ptopoConnMultiNetSASeen PtopoAddrSeenState,
PtopoConnEntry ::= SEQUENCE {
ptopoConnTimeMark TimeFilter,
ptopoConnLocalChassis PhysicalIndex,
ptopoConnLocalPort PhysicalIndex,
ptopoConnIndex Integer32,
ptopoConnRemoteChassisType PtopoChassisIdType,
ptopoConnRemoteChassis PtopoChassisId,
ptopoConnRemotePortType PtopoPortIdType,
ptopoConnRemotePort PtopoPortId,
ptopoConnDiscAlgorithm AutonomousType,
ptopoConnAgentNetAddrType AddressFamilyNumbers,
ptopoConnAgentNetAddr PtopoGenAddr,
ptopoConnMultiMacSASeen PtopoAddrSeenState,
ptopoConnMultiNetSASeen PtopoAddrSeenState,
ptopoConnIsStatic TruthValue, ptopoConnLastVerifyTime TimeStamp, ptopoConnRowStatus RowStatus }
ptopoConnIsStatic TruthValue，ptopoconnllastVerifyTime时间戳，ptopoConnRowStatus RowStatus}
ptopoConnTimeMark OBJECT-TYPE
SYNTAX TimeFilter
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A TimeFilter for this entry. See the TimeFilter textual
convention in RFC 2021 to see how this works."
::= { ptopoConnEntry 1 }
ptopoConnTimeMark OBJECT-TYPE
SYNTAX TimeFilter
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A TimeFilter for this entry. See the TimeFilter textual
convention in RFC 2021 to see how this works."
::= { ptopoConnEntry 1 }
ptopoConnLocalChassis OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entPhysicalIndex value used to identify the chassis
component associated with the local connection endpoint."
::= { ptopoConnEntry 2 }
ptopoConnLocalChassis OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entPhysicalIndex value used to identify the chassis
component associated with the local connection endpoint."
::= { ptopoConnEntry 2 }
ptopoConnLocalPort OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entPhysicalIndex value used to identify the port
component associated with the local connection endpoint."
::= { ptopoConnEntry 3 }
ptopoConnLocalPort OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entPhysicalIndex value used to identify the port
component associated with the local connection endpoint."
::= { ptopoConnEntry 3 }
ptopoConnIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated local connection endpoint.
ptopoConnIndex对象类型语法Integer32（1..2147483647）MAX-ACCESS not accessible STATUS current DESCRIPTION“此对象表示此代理用于标识特定连接实例的任意本地整数值，仅对指定的本地连接端点唯一。
A particular ptopoConnIndex value may be reused in the event an entry is aged out and later re-learned with the same (or different) remote chassis and port identifiers.
如果某个条目过时，然后使用相同（或不同）的远程机箱和端口标识符重新读入，则可以重用特定的ptopoConnIndex值。
An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each
鼓励代理将单调递增的索引值分配给新条目，从一个开始，在每个条目之后
reboot. It is considered unlikely that the ptopoConnIndex
will wrap between reboots."
::= { ptopoConnEntry 4 }
reboot. It is considered unlikely that the ptopoConnIndex
will wrap between reboots."
::= { ptopoConnEntry 4 }
ptopoConnRemoteChassisType OBJECT-TYPE SYNTAX PtopoChassisIdType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of encoding used to identify the chassis associated with the remote connection endpoint.
ptopoConnRemoteChassisType对象类型语法ptopochassidType MAX-ACCESS读取创建状态当前描述“用于标识与远程连接端点关联的机箱的编码类型。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 5 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 5 }
ptopoConnRemoteChassis OBJECT-TYPE SYNTAX PtopoChassisId MAX-ACCESS read-create STATUS current DESCRIPTION "The string value used to identify the chassis component associated with the remote connection endpoint.
ptopoConnRemoteChassis对象类型语法ptopochassid MAX-ACCESS read create STATUS current DESCRIPTION“用于标识与远程连接端点关联的机箱组件的字符串值。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 6 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 6 }
ptopoConnRemotePortType OBJECT-TYPE SYNTAX PtopoPortIdType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of port identifier encoding used in the associated 'ptopoConnRemotePort' object.
ptopoConnRemotePortType对象类型语法ptoportidType MAX-ACCESS读取创建状态当前描述“关联的“ptopoConnRemotePort”对象中使用的端口标识符编码类型。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 7 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 7 }
ptopoConnRemotePort OBJECT-TYPE SYNTAX PtopoPortId MAX-ACCESS read-create STATUS current DESCRIPTION "The string value used to identify the port component associated with the remote connection endpoint.
ptopoConnRemotePort对象类型语法ptoportid MAX-ACCESS read create STATUS current DESCRIPTION“用于标识与远程连接端点关联的端口组件的字符串值。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 8 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 8 }
ptopoConnDiscAlgorithm OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of the algorithm used to discover the information contained in this conceptual row.
ptopoConnDiscAlgorithm OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS只读状态current DESCRIPTION“用于发现此概念行中包含的信息的算法的指示。
A value of ptopoDiscoveryLocal indicates this entry was configured by the local agent, without use of a discovery protocol.
ptopoDiscoveryLocal的值表示此条目是由本地代理配置的，不使用发现协议。
A value of { 0 0 } indicates this entry was created manually
by an NMS via the associated RowStatus object. "
::= { ptopoConnEntry 9 }
A value of { 0 0 } indicates this entry was created manually
by an NMS via the associated RowStatus object. "
::= { ptopoConnEntry 9 }
ptopoConnAgentNetAddrType OBJECT-TYPE SYNTAX AddressFamilyNumbers MAX-ACCESS read-create STATUS current DESCRIPTION "This network address type of the associated ptopoConnNetAddr object, unless that object contains a zero length string. In such a case, an NMS application should ignore any returned value for this object.
PtopoconNagentNetAddressType对象类型语法AddressFamilyNumbers MAX-ACCESS read create STATUS current DESCRIPTION“关联的ptopoConnNetAddr对象的此网络地址类型，除非该对象包含零长度字符串。在这种情况下，NMS应用程序应忽略此对象的任何返回值。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 10 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
::= { ptopoConnEntry 10 }
ptopoConnAgentNetAddr OBJECT-TYPE SYNTAX PtopoGenAddr MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies a network address which may be used to reach an SNMP agent entity containing information for the chassis and port components represented by the associated 'ptopoConnRemoteChassis' and 'ptopoConnRemotePort' objects. If no such address is known, then this object shall contain an empty string.
ptopoConnAgentNetAddr对象类型语法PtopoGenAddr MAX-ACCESS读取创建状态当前说明“此对象标识网络地址，该地址可用于访问SNMP代理实体，该实体包含由关联的'ptopoConnRemoteChassis'和'ptopoconnRemoteReport'对象表示的机箱和端口组件的信息。如果不知道这样的地址，那么这个对象应该包含一个空字符串。
This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1)."
如果关联的ptopoConnRowStatus对象的值为active（1），则不能修改此对象。”
::= { ptopoConnEntry 11 }
::= { ptopoConnEntry 11 }
ptopoConnMultiMacSASeen OBJECT-TYPE SYNTAX PtopoAddrSeenState MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates if multiple unicast source MAC addresses have been detected by the agent from the remote connection endpoint, since the creation of this entry.
ptopoConnMultiMacSASeen对象类型语法PtopoAddrSeenState MAX-ACCESS只读状态当前描述“此对象表示自创建此条目以来，代理是否已从远程连接端点检测到多个单播源MAC地址。
If this entry has an associated ptopoConnRemoteChassisType and/or ptopoConnRemotePortType value other than 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned.
如果此条目具有除“portIdMacAddr（3）”之外的关联ptopoConnRemoteChassisType和/或ptopoConnRemotePortType值，则返回值“notUsed（1）”。
Otherwise, one of the following conditions must be true:
否则，以下条件之一必须为真：
If the agent has not yet detected any unicast source MAC addresses from the remote port, then the value 'unknown(2)' is returned.
如果代理尚未从远程端口检测到任何单播源MAC地址，则返回值“未知（2）”。
If the agent has detected exactly one unicast source MAC address from the remote port, then the value 'oneAddr(3)' is returned.
如果代理从远程端口恰好检测到一个单播源MAC地址，则返回值“oneAddr（3）”。
If the agent has detected more than one unicast source MAC
address from the remote port, then the value 'multiAddr(4)'
is returned."
::= { ptopoConnEntry 12 }
If the agent has detected more than one unicast source MAC
address from the remote port, then the value 'multiAddr(4)'
is returned."
::= { ptopoConnEntry 12 }
ptopoConnMultiNetSASeen OBJECT-TYPE SYNTAX PtopoAddrSeenState MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates if multiple network layer source addresses have been detected by the agent from the remote connection endpoint, since the creation of this entry.
ptopoconnmultinessaseen对象类型语法PtopoAddrSeenState MAX-ACCESS只读状态当前描述“此对象表示自创建此条目以来，代理是否已从远程连接端点检测到多个网络层源地址。
If this entry has an associated ptopoConnRemoteChassisType or ptopoConnRemotePortType value other than 'portIdGenAddr(4)' then the value 'notUsed(1)' is returned.
如果此条目具有除“portIdGenAddr（4）”之外的关联ptopoConnRemoteChassisType或ptopoConnRemotePortType值，则返回值“notUsed（1）”。
Otherwise, one of the following conditions must be true:
否则，以下条件之一必须为真：
If the agent has not yet detected any network source addresses of the appropriate type from the remote port, then the value 'unknown(2)' is returned.
如果代理尚未从远程端口检测到任何适当类型的网络源地址，则返回值“未知（2）”。
If the agent has detected exactly one network source address of the appropriate type from the remote port, then the value 'oneAddr(3)' is returned.
如果代理从远程端口恰好检测到一个适当类型的网络源地址，则返回值“oneAddr（3）”。
If the agent has detected more than one network source
address (of the same appropriate type) from the remote port,
this the value 'multiAddr(4)' is returned."
::= { ptopoConnEntry 13 }
If the agent has detected more than one network source
address (of the same appropriate type) from the remote port,
this the value 'multiAddr(4)' is returned."
::= { ptopoConnEntry 13 }
ptopoConnIsStatic OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies static ptopoConnEntries. If this object has the value 'true(1)', then this entry is not subject to any age-out mechanisms implemented by the agent.
ptopoConnIsStatic对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION“此对象标识静态ptopoconentries。如果此对象的值为“true（1）”，则此项不受代理实现的任何过期机制的约束。
If this object has the value 'false(2)', then this entry is subject to all age-out mechanisms implemented by the agent.
如果此对象的值为“false（2）”，则此条目受代理实现的所有过期机制的约束。
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
DEFVAL { false }
::= { ptopoConnEntry 14 }
This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)."
DEFVAL { false }
::= { ptopoConnEntry 14 }
ptopoConnLastVerifyTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "If the associated value of ptopoConnIsStatic is equal to 'false(2)', then this object contains the value of sysUpTime at the time the conceptual row was last verified by the agent, e.g., via reception of a topology protocol message, pertaining to the associated remote chassis and port.
ptopoConnLastVerifyTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“如果ptopoConnIsStatic的关联值等于”false（2），则此对象包含代理上次验证概念行时的sysUpTime值，例如，通过接收拓扑协议消息，该消息与关联的远程机箱和端口有关。
If the associated value of ptopoConnIsStatic is equal to
'true(1)', then this object shall contain the value of
sysUpTime at the time this entry was last activated (i.e.,
ptopoConnRowStatus set to 'active(1)')."
::= { ptopoConnEntry 15 }
If the associated value of ptopoConnIsStatic is equal to
'true(1)', then this object shall contain the value of
sysUpTime at the time this entry was last activated (i.e.,
ptopoConnRowStatus set to 'active(1)')."
::= { ptopoConnEntry 15 }
ptopoConnRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION
ptopoConnRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述
"The status of this conceptual row."
::= { ptopoConnEntry 16 }
"The status of this conceptual row."
::= { ptopoConnEntry 16 }
-- ***********************************************************
--
-- P T O P O G E N E R A L G R O U P
--
-- ***********************************************************
-- ***********************************************************
--
-- P T O P O G E N E R A L G R O U P
--
-- ***********************************************************
-- last change time stamp for the whole MIB
--整个MIB的上次更改时间戳
ptopoLastChangeTime 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 the ptopoConnTable.
ptopoLastChangeTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“在ptopocontable中创建、修改或删除概念行时的系统正常运行时间值。
An NMS can use this object to reduce polling of the
ptopoData group objects."
::= { ptopoGeneral 1 }
An NMS can use this object to reduce polling of the
ptopoData group objects."
::= { ptopoGeneral 1 }
ptopoConnTabInserts OBJECT-TYPE
SYNTAX Counter32
UNITS "table entries"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an entry has been inserted into the
ptopoConnTable."
::= { ptopoGeneral 2 }
ptopoConnTabInserts OBJECT-TYPE
SYNTAX Counter32
UNITS "table entries"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an entry has been inserted into the
ptopoConnTable."
::= { ptopoGeneral 2 }
ptopoConnTabDeletes OBJECT-TYPE SYNTAX Counter32 UNITS "table entries" MAX-ACCESS read-only STATUS current
ptopoConnTabDeletes对象类型语法计数器32个单位“表条目”MAX-ACCESS只读状态当前
DESCRIPTION
"The number of times an entry has been deleted from the
ptopoConnTable."
::= { ptopoGeneral 3 }
DESCRIPTION
"The number of times an entry has been deleted from the
ptopoConnTable."
::= { ptopoGeneral 3 }
ptopoConnTabDrops OBJECT-TYPE SYNTAX Counter32 UNITS "table entries" MAX-ACCESS read-only
ptopoConnTabDrops对象类型语法计数器32个单位“表条目”MAX-ACCESS只读
STATUS current
DESCRIPTION
"The number of times an entry would have been added to the
ptopoConnTable, (e.g., via information learned from a
topology protocol), but was not because of insufficient
resources."
::= { ptopoGeneral 4 }
STATUS current
DESCRIPTION
"The number of times an entry would have been added to the
ptopoConnTable, (e.g., via information learned from a
topology protocol), but was not because of insufficient
resources."
::= { ptopoGeneral 4 }
ptopoConnTabAgeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an entry has been deleted from the
ptopoConnTable because the information timeliness interval
for that entry has expired."
::= { ptopoGeneral 5 }
ptopoConnTabAgeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an entry has been deleted from the
ptopoConnTable because the information timeliness interval
for that entry has expired."
::= { ptopoGeneral 5 }
-- ***********************************************************
--
-- P T O P O C O N F I G G R O U P
--
-- ***********************************************************
-- ***********************************************************
--
-- P T O P O C O N F I G G R O U P
--
-- ***********************************************************
ptopoConfigTrapInterval OBJECT-TYPE SYNTAX Integer32 (0 | 5..3600) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the transmission of PTOPO notifications.
ptopoConfigTrapInterval对象类型语法整数32（0 | 5..3600）单位“秒”最大访问读写状态当前描述“此对象控制PTOPO通知的传输。
If this object has a value of zero, then no ptopoConfigChange notifications will be transmitted by the agent.
如果此对象的值为零，则代理不会传输ptopoConfigChange通知。
If this object has a non-zero value, then the agent must not generate more than one ptopoConfigChange trap-event in the indicated period, where a 'trap-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional configuration changes occur within the indicated throttling period, then these trap-events must be suppressed by the agent. An NMS should periodically check the value of ptopoLastChangeTime to detect any missed ptopoConfigChange trap-events, e.g. due to throttling or transmission loss.
如果此对象具有非零值，则代理在指定的时间段内不得生成多个ptopoConfigChange陷阱事件，其中“陷阱事件”是将单个通知PDU类型传输到通知目标列表。如果在指定的节流周期内发生其他配置更改，则代理必须抑制这些陷阱事件。NMS应定期检查ptopoLastChangeTime的值，以检测任何遗漏的ptopoConfigChange陷阱事件，例如由于节流或传输损耗引起的事件。
If notification transmission is enabled, the suggested default throttling period is 60 seconds, but transmission should be disabled by default.
如果启用了通知传输，建议的默认限制时间为60秒，但默认情况下应禁用传输。
If the agent is capable of storing non-volatile
configuration, then the value of this object must be
restored after a re-initialization of the management
system."
DEFVAL { 0 }
::= { ptopoConfig 1 }
If the agent is capable of storing non-volatile
configuration, then the value of this object must be
restored after a re-initialization of the management
system."
DEFVAL { 0 }
::= { ptopoConfig 1 }
ptopoConfigMaxHoldTime OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the desired time interval for which an agent will maintain dynamic ptopoConnEntries.
ptopoConfigMaxHoldTime对象类型语法整数32（1..2147483647）单位“秒”最大访问读写状态当前描述“此对象指定代理将维护动态ptopoconnentry的所需时间间隔。
After the specified number of seconds since the last time an entry was verified, in the absence of new verification (e.g., receipt of a topology protocol message), the agent shall remove the entry. Note that entries may not always be removed immediately, but may possibly be removed at periodic garbage collection intervals. This object only affects dynamic ptopoConnEntries, i.e. for which ptopoConnIsStatic equals 'false(2)'. Static entries are not aged out.
自上次验证条目以来的指定秒数之后，在没有新的验证（例如，收到拓扑协议消息）的情况下，代理应删除该条目。请注意，条目可能不会总是立即删除，但可能会在定期的垃圾收集间隔中删除。此对象仅影响动态ptopoconntries，即ptopoConnIsStatic等于“false（2）”。静态条目不会过期。
Note that dynamic ptopoConnEntries may also be removed by the agent due to the expired timeliness of learned topology information (e.g., timeliness interval for a remote port expires). The actual age-out interval for a given entry is defined by the following formula:
注意，由于学习到的拓扑信息的时效性过期（例如，远程端口的时效性间隔过期），代理也可能删除动态ptoponnentry。给定条目的实际过期时间间隔由以下公式定义：
age-out-time =
min(ptopoConfigMaxHoldTime, <entry-specific hold-time>)
age-out-time =
min(ptopoConfigMaxHoldTime, <entry-specific hold-time>)
where <entry-specific hold-time> is determined by the
discovery algorithm, and may be different for each entry."
DEFVAL { 300 }
::= { ptopoConfig 2 }
where <entry-specific hold-time> is determined by the
discovery algorithm, and may be different for each entry."
DEFVAL { 300 }
::= { ptopoConfig 2 }
-- PTOPO MIB Notification Definitions
ptopoMIBNotifications OBJECT IDENTIFIER ::= { ptopoMIB 2 }
ptopoMIBTrapPrefix OBJECT IDENTIFIER ::=
-- PTOPO MIB Notification Definitions
ptopoMIBNotifications OBJECT IDENTIFIER ::= { ptopoMIB 2 }
ptopoMIBTrapPrefix OBJECT IDENTIFIER ::=
{ ptopoMIBNotifications 0 }
{ptopomib0}
ptopoConfigChange NOTIFICATION-TYPE
OBJECTS {
ptopoConnTabInserts,
ptopoConnTabDeletes,
ptopoConnTabDrops,
ptopoConnTabAgeouts
}
STATUS current
DESCRIPTION
"A ptopoConfigChange notification is sent when the value of
ptopoLastChangeTime changes. It can be utilized by an NMS to
trigger physical topology table maintenance polls.
ptopoConfigChange NOTIFICATION-TYPE
OBJECTS {
ptopoConnTabInserts,
ptopoConnTabDeletes,
ptopoConnTabDrops,
ptopoConnTabAgeouts
}
STATUS current
DESCRIPTION
"A ptopoConfigChange notification is sent when the value of
ptopoLastChangeTime changes. It can be utilized by an NMS to
trigger physical topology table maintenance polls.
Note that transmission of ptopoConfigChange notifications
are throttled by the agent, as specified by the
'ptopoConfigTrapInterval' object."
::= { ptopoMIBTrapPrefix 1 }
Note that transmission of ptopoConfigChange notifications
are throttled by the agent, as specified by the
'ptopoConfigTrapInterval' object."
::= { ptopoMIBTrapPrefix 1 }
-- PTOPO Registration Points
ptopoRegistrationPoints OBJECT IDENTIFIER ::= { ptopoMIB 3 }
-- PTOPO Registration Points
ptopoRegistrationPoints OBJECT IDENTIFIER ::= { ptopoMIB 3 }
-- values used with ptopoConnDiscAlgorithm object
ptopoDiscoveryMechanisms OBJECT IDENTIFIER ::=
{ ptopoRegistrationPoints 1 }
-- values used with ptopoConnDiscAlgorithm object
ptopoDiscoveryMechanisms OBJECT IDENTIFIER ::=
{ ptopoRegistrationPoints 1 }
ptopoDiscoveryLocal OBJECT IDENTIFIER ::=
{ ptopoDiscoveryMechanisms 1 }
ptopoDiscoveryLocal OBJECT IDENTIFIER ::=
{ ptopoDiscoveryMechanisms 1 }
-- conformance information
ptopoConformance OBJECT IDENTIFIER ::= { ptopoMIB 4 }
-- conformance information
ptopoConformance OBJECT IDENTIFIER ::= { ptopoMIB 4 }
ptopoCompliances OBJECT IDENTIFIER ::= { ptopoConformance 1 }
ptopoGroups OBJECT IDENTIFIER ::= { ptopoConformance 2 }
ptopoCompliances OBJECT IDENTIFIER ::= { ptopoConformance 1 }
ptopoGroups OBJECT IDENTIFIER ::= { ptopoConformance 2 }
-- compliance statements ptopoCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which implement the PTOPO MIB." MODULE -- this module MANDATORY-GROUPS { ptopoDataGroup,
--合规性声明ptopoCompliance MODULE-compliance STATUS当前描述“实现PTOPO MIB的SNMP实体的合规性声明”。MODULE--此模块为必填项-GROUPS{ptopoDataGroup，
ptopoGeneralGroup,
ptopoConfigGroup,
ptopoNotificationsGroup
}
::= { ptopoCompliances 1 }
ptopoGeneralGroup,
ptopoConfigGroup,
ptopoNotificationsGroup
}
::= { ptopoCompliances 1 }
-- MIB groupings
ptopoDataGroup OBJECT-GROUP
OBJECTS {
ptopoConnRemoteChassisType,
ptopoConnRemoteChassis,
ptopoConnRemotePortType,
ptopoConnRemotePort,
ptopoConnDiscAlgorithm,
ptopoConnAgentNetAddrType,
ptopoConnAgentNetAddr,
ptopoConnMultiMacSASeen,
ptopoConnMultiNetSASeen,
ptopoConnIsStatic,
ptopoConnLastVerifyTime,
ptopoConnRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to represent
physical topology information for which a single agent
provides management information.
-- MIB groupings
ptopoDataGroup OBJECT-GROUP
OBJECTS {
ptopoConnRemoteChassisType,
ptopoConnRemoteChassis,
ptopoConnRemotePortType,
ptopoConnRemotePort,
ptopoConnDiscAlgorithm,
ptopoConnAgentNetAddrType,
ptopoConnAgentNetAddr,
ptopoConnMultiMacSASeen,
ptopoConnMultiNetSASeen,
ptopoConnIsStatic,
ptopoConnLastVerifyTime,
ptopoConnRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to represent
physical topology information for which a single agent
provides management information.
This group is mandatory for all implementations of the PTOPO
MIB."
::= { ptopoGroups 1 }
This group is mandatory for all implementations of the PTOPO
MIB."
::= { ptopoGroups 1 }
ptopoGeneralGroup OBJECT-GROUP
OBJECTS {
ptopoLastChangeTime,
ptopoConnTabInserts,
ptopoConnTabDeletes,
ptopoConnTabDrops,
ptopoConnTabAgeouts
}
STATUS current
DESCRIPTION
"The collection of objects which are used to report the
general status of the PTOPO MIB implementation.
ptopoGeneralGroup OBJECT-GROUP
OBJECTS {
ptopoLastChangeTime,
ptopoConnTabInserts,
ptopoConnTabDeletes,
ptopoConnTabDrops,
ptopoConnTabAgeouts
}
STATUS current
DESCRIPTION
"The collection of objects which are used to report the
general status of the PTOPO MIB implementation.
This group is mandatory for all agents which implement the
PTOPO MIB."
::= { ptopoGroups 2 }
This group is mandatory for all agents which implement the
PTOPO MIB."
::= { ptopoGroups 2 }
ptopoConfigGroup OBJECT-GROUP
OBJECTS {
ptopoConfigTrapInterval,
ptopoConfigMaxHoldTime
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure the
PTOPO MIB implementation behavior.
ptopoConfigGroup OBJECT-GROUP
OBJECTS {
ptopoConfigTrapInterval,
ptopoConfigMaxHoldTime
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure the
PTOPO MIB implementation behavior.
This group is mandatory for agents which implement the PTOPO
MIB."
::= { ptopoGroups 3 }
This group is mandatory for agents which implement the PTOPO
MIB."
::= { ptopoGroups 3 }
ptopoNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
ptopoConfigChange
}
STATUS current
DESCRIPTION
"The collection of notifications used to indicate PTOPO MIB
data consistency and general status information.
ptopoNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
ptopoConfigChange
}
STATUS current
DESCRIPTION
"The collection of notifications used to indicate PTOPO MIB
data consistency and general status information.
This group is mandatory for agents which implement the PTOPO
MIB."
::= { ptopoGroups 4 }
This group is mandatory for agents which implement the PTOPO
MIB."
::= { ptopoGroups 4 }
END
终止
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实践所需技术的专有权
this standard. Please address the information to the IETF Executive Director.
这个标准。请将信息发送给IETF执行董事。
The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights.
IETF已收到关于本文件所含部分或全部规范的知识产权声明。有关更多信息，请查阅在线权利主张列表。
The PTOPO Discovery Protocol is a product of the IETF PTOPOMIB Working Group.
PTOPO发现协议是IETF PTOPOMIB工作组的产品。
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC1212]Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[RFC1215]Rose，M.，“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie, "Definitions of Managed Objects for Bridges", RFC 1493, July 1993.
[RFC1493]Decker，E.，Langille，P.，Rijsinghani，A.和K.McCloghrie，“桥梁管理对象的定义”，RFC 1493，1993年7月。
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994.
[RFC1700]Reynolds，J.和J.Postel，“分配的数字”，标准2，RFC 1700，1994年10月。
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", January 1996.
[RFC1901]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，1996年1月。
[RFC1902] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[RFC1902]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[RFC1903]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[RFC1904] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[RFC1904]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1905]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC1906]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[RFC2021] Waldbusser, S., "Remote Network Monitoring MIB (RMON-2)", RFC 2021, January 1997.
[RFC2021]Waldbusser，S.，“远程网络监控MIB（RMON-2）”，RFC 20211997年1月。
[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月。
[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月。
[RFC2233] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group MIB using SMIv2", RFC 2233, November 1997.
[RFC2233]McCloghrie，K.和F.Kastenholtz，“使用SMIv2的接口组MIB”，RFC 2233，1997年11月。
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[RFC2570]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC2571]Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2572]Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[RFC2573]Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 2573，1999年4月。
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2574]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2575]Wijnen，B.，Presohn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1999年4月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 2)", RFC 2737, Cisco Systems, December 1999.
[RFC2737]McCloghrie，K.和A.Bierman，“实体MIB（版本2）”，RFC 2737，思科系统，1999年12月。
There are a number of management objects defined in this MIB that have 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.
此MIB中定义了许多管理对象，它们的MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
There are a number of managed objects in this MIB that may contain sensitive information. These are:
此MIB中有许多托管对象可能包含敏感信息。这些是：
read-create objects: ptopoConnRemoteChassisType ptopoConnRemoteChassis ptopoConnRemotePortType ptopoConnRemotePort ptopoConnAgentNetAddrType ptopoConnAgentNetAddr ptopoConnIsStatic ptopoConfigTrapInterval ptopoConfigMaxHoldTime
读取创建对象：ptopoconnRemoteChasisType ptopoConnRemoteChassis ptopoConnRemotePortType ptopoconnRemoteReport ptopoconNagentNetAddressType ptopoconNagentNetAddress ptopoconnStatic ptopoconConfigGTRAPInterval ptopoconConfigMaxHoldTime
read-only objects: ptopoConnDiscAlgorithm ptopoConnMultiMacSASeen ptopoConnMultiNetSASeen ptopoConnLastVerifyTime ptopoLastChangeTime
只读对象：ptopoConnDiscAlgorithm ptopoConnMultiMacSASeen ptopoConnMultiNetSASeen ptopoConnLastVerifyTime ptopoLastChangeTime
notifications: ptopoConfigChange
通知：ptopoConfigChange
These MIB objects expose information about the physical connectivity for a particular portion of a network.
这些MIB对象公开有关网络特定部分的物理连接的信息。
A network administrator may also wish to inhibit transmission of any ptopoConfigChange notification by setting the ptopoConfigTrapInterval object to zero.
网络管理员还可能希望通过将ptopoConfigTrapInterval对象设置为零来禁止任何ptopoConfigChange通知的传输。
It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment.
因此，在通过SNMP通过网络发送这些对象时，控制甚至访问这些对象，甚至可能加密这些对象的值，这一点非常重要。并非所有版本的SNMP都为这种安全环境提供功能。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [RFC2574] and the View-based Access Control Model RFC 2575 [RFC2575] is recommended.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2574[RFC2574]和基于视图的访问控制模型RFC 2575[RFC2575]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, 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.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
Andy Bierman Cisco Systems 170 West Tasman Drive San Jose, CA USA 95134
美国加利福尼亚州圣何塞市西塔斯曼大道170号安迪·比尔曼思科系统公司95134
Phone: +1 408-527-3711
EMail: abierman@cisco.com
Phone: +1 408-527-3711
EMail: abierman@cisco.com
Kendall S. Jones Nortel Networks 4401 Great America Parkway Santa Clara, CA USA 95054
Kendall S.Jones Nortel Networks 4401美国加利福尼亚州圣克拉拉大美洲大道95054
Phone: +1 408-495-7356
EMail: kejones@nortelnetworks.com
Phone: +1 408-495-7356
EMail: kejones@nortelnetworks.com
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。