Network Working Group K. White
Request for Comments: 2925 IBM Corp.
Category: Standards Track September 2000
Network Working Group K. White
Request for Comments: 2925 IBM Corp.
Category: Standards Track September 2000
Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
远程Ping、Traceroute和查找操作的托管对象定义
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote host. When managing a network it is useful to be able to initiate and retrieve the results of ping or traceroute operations when performed at a remote host. A Lookup capability is defined in order to enable resolving of either an IP address to an DNS name or an DNS name to an IP address at a remote host.
此备忘录定义了用于在远程主机上执行远程ping、traceroute和查找操作的管理信息库（MIB）。在管理网络时，在远程主机上执行ping或traceroute操作时，能够启动和检索ping或traceroute操作的结果非常有用。定义查找功能是为了能够在远程主机上将IP地址解析为DNS名称或将DNS名称解析为IP地址。
Currently, there are several enterprise-specific MIBs for performing remote ping or traceroute operations. The purpose of this memo is to define a standards-based solution to enable interoperability.
目前，有几个特定于企业的MIB用于执行远程ping或traceroute操作。本备忘录旨在定义基于标准的解决方案，以实现互操作性。
Table of Contents
目录
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . . 4
3.0 Structure of the MIBs . . . . . . . . . . . . . . . . . . . 5
3.1 Ping MIB . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1.1 pingMaxConcurrentRequests . . . . . . . . . . . . . . . 6
3.1.2 pingCtlTable . . . . . . . . . . . . . . . . . . . . . . 6
3.1.3 pingResultsTable . . . . . . . . . . . . . . . . . . . . 7
3.1.4 pingProbeHistoryTable . . . . . . . . . . . . . . . . . 7
3.2 Traceroute MIB . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1 traceRouteMaxConcurrentRequests . . . . . . . . . . . . 8
3.2.2 traceRouteCtlTable . . . . . . . . . . . . . . . . . . . 8
3.2.3 traceRouteResultsTable . . . . . . . . . . . . . . . . . 9
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . . 4
3.0 Structure of the MIBs . . . . . . . . . . . . . . . . . . . 5
3.1 Ping MIB . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1.1 pingMaxConcurrentRequests . . . . . . . . . . . . . . . 6
3.1.2 pingCtlTable . . . . . . . . . . . . . . . . . . . . . . 6
3.1.3 pingResultsTable . . . . . . . . . . . . . . . . . . . . 7
3.1.4 pingProbeHistoryTable . . . . . . . . . . . . . . . . . 7
3.2 Traceroute MIB . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1 traceRouteMaxConcurrentRequests . . . . . . . . . . . . 8
3.2.2 traceRouteCtlTable . . . . . . . . . . . . . . . . . . . 8
3.2.3 traceRouteResultsTable . . . . . . . . . . . . . . . . . 9
3.2.4 traceRouteProbeHistoryTable . . . . . . . . . . . . . . 9
3.2.5 traceRouteHopsTable . . . . . . . . . . . . . . . . . . 10
3.3 Lookup MIB . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3.1 lookupMaxConcurrentRequests and lookupPurgeTime . . . . 10
3.3.2 lookupCtlTable . . . . . . . . . . . . . . . . . . . . . 10
3.3.3 lookupResultsTable . . . . . . . . . . . . . . . . . . . 11
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 DISMAN-PING-MIB . . . . . . . . . . . . . . . . . . . . . . 12
4.2 DISMAN-TRACEROUTE-MIB . . . . . . . . . . . . . . . . . . . 36
4.3 DISMAN-NSLOOKUP-MIB . . . . . . . . . . . . . . . . . . . . 63
5.0 Security Considerations . . . . . . . . . . . . . . . . . . 73
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . 74
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 74
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . 76
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . 77
3.2.4 traceRouteProbeHistoryTable . . . . . . . . . . . . . . 9
3.2.5 traceRouteHopsTable . . . . . . . . . . . . . . . . . . 10
3.3 Lookup MIB . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3.1 lookupMaxConcurrentRequests and lookupPurgeTime . . . . 10
3.3.2 lookupCtlTable . . . . . . . . . . . . . . . . . . . . . 10
3.3.3 lookupResultsTable . . . . . . . . . . . . . . . . . . . 11
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 DISMAN-PING-MIB . . . . . . . . . . . . . . . . . . . . . . 12
4.2 DISMAN-TRACEROUTE-MIB . . . . . . . . . . . . . . . . . . . 36
4.3 DISMAN-NSLOOKUP-MIB . . . . . . . . . . . . . . . . . . . . 63
5.0 Security Considerations . . . . . . . . . . . . . . . . . . 73
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . 74
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 74
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . 76
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . 77
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119, reference [13].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119，参考文献[13]中的描述进行解释。
This document is a product of the Distributed Management (DISMAN) Working Group. Its purpose is to define standards-based MIB modules for performing specific remote operations. The remote operations defined by this document consist of the ping, traceroute and lookup functions.
本文档是分布式管理（DISMAN）工作组的产品。其目的是定义用于执行特定远程操作的基于标准的MIB模块。本文档定义的远程操作包括ping、traceroute和lookup功能。
Ping and traceroute are two very useful functions for managing networks. Ping is typically used to determine if a path exists between two hosts while traceroute shows an actual path. Ping is usually implemented using the Internet Control Message Protocol (ICMP) "ECHO" facility. It is also possible to implement a ping capability using alternate methods, some of which are:
Ping和traceroute是管理网络的两个非常有用的功能。Ping通常用于确定两台主机之间是否存在路径，而traceroute显示实际路径。Ping通常使用Internet控制消息协议（ICMP）“ECHO”功能实现。还可以使用替代方法实现ping功能，其中一些方法包括：
o Using the UDP echo port (7), if supported.
o 如果支持，请使用UDP回显端口（7）。
This is defined by RFC 862 [2].
这是由RFC 862[2]定义的。
o Timing an SNMP query.
o 为SNMP查询计时。
o Timing a TCP connect attempt.
o 为TCP连接尝试计时。
In general, almost any request/response flow can be used to generate a round-trip time. Often many of the non-ICMP ECHO facility methods stand a better chance of yielding a good response (not timing out for
通常，几乎任何请求/响应流都可以用来生成往返时间。通常，许多非ICMP ECHO facility方法更有可能产生良好的响应（而不是超时）
example) since some routers don't honor Echo Requests (timeout situation) or they are handled at lower priority, hence possibly giving false indications of round trip times.
例如）由于一些路由器不接受回送请求（超时情况），或者它们以较低的优先级处理，因此可能给出错误的往返时间指示。
It must be noted that almost any of the various methods used for generating a round-trip time can be considered a form of system attack when used excessively. Sending a system requests too often can negatively effect its performance. Attempting to connect to what is supposed to be an unused port can be very unpredictable. There are tools that attempt to connect to a range of TCP ports to test that any receiving server can handle erroneous connection attempts.
必须注意的是，当过度使用时，几乎所有用于生成往返时间的各种方法都可以被视为系统攻击的一种形式。过于频繁地发送系统请求可能会对其性能产生负面影响。尝试连接到本应未使用的端口可能非常不可预测。有一些工具尝试连接到一系列TCP端口，以测试任何接收服务器是否可以处理错误的连接尝试。
It also is important to the management application using a remote ping capability to know which method is being used. Different methods will yield different response times since the protocol and resulting processing will be different. It is RECOMMENDED that the ping capability defined within this memo be implemented using the ICMP Echo Facility.
对于使用远程ping功能的管理应用程序来说，了解所使用的方法也很重要。不同的方法将产生不同的响应时间，因为协议和结果处理将不同。建议使用ICMP回显设施实现本备忘录中定义的ping功能。
Traceroute is usually implemented by transmitting a series of probe packets with increasing time-to-live values. A probe packet is a UDP datagram encapsulated into an IP packet. Each hop in a path to the target (destination) host rejects the probe packet (probe's TTL too small) until its time-to-live value becomes large enough for the probe to be forwarded. Each hop in a traceroute path returns an ICMP message that is used to discover the hop and to calculate a round trip time. Some systems use ICMP probes (ICMP Echo request packets) instead of UDP ones to implement traceroute. In both cases traceroute relies on the probes being rejected via an ICMP message to discover the hops taken along a path to the final destination. Both probe types, UDP and ICMP, are encapsulated into an IP packet and thus have a TTL field that can be used to cause a path rejection.
Traceroute通常是通过发送一系列探测包来实现的，探测包的生存时间值不断增加。探测数据包是封装在IP数据包中的UDP数据报。到达目标（目的地）主机的路径中的每个跃点都会拒绝探测数据包（探测的TTL太小），直到其生存时间值变大，足以转发探测。跟踪路由路径中的每个跃点返回一条ICMP消息，该消息用于发现跃点和计算往返时间。一些系统使用ICMP探测（ICMP回显请求包）而不是UDP探测来实现跟踪路由。在这两种情况下，跟踪路由都依赖于通过ICMP消息拒绝的探测来发现沿路径到达最终目的地的跳数。UDP和ICMP这两种探测类型都封装在IP数据包中，因此具有一个TTL字段，可用于导致路径拒绝。
Implementations of the remote traceroute capability as defined within this memo SHOULD be done using UDP packets to a (hopefully) unused port. ICMP probes (ICMP Echo Request packets) SHOULD NOT be used. Many PC implementations of traceroute use the ICMP probe method, which they should not, since this implementation method has been known to have a high probability of failure. Intermediate hops become invisible when a router either refuses to send an ICMP TTL expired message in response to an incoming ICMP packet or simply tosses ICMP echo requests altogether.
本备忘录中定义的远程跟踪路由功能的实现应该使用UDP数据包（希望是）未使用的端口来完成。不应使用ICMP探测（ICMP回显请求数据包）。跟踪路由的许多PC实现都使用ICMP探测方法，但它们不应该使用这种方法，因为已知这种实现方法有很高的失败概率。当路由器拒绝发送ICMP TTL过期消息以响应传入的ICMP数据包或干脆完全抛出ICMP回显请求时，中间跳变为不可见。
The behavior of some routers not to return a TTL expired message in response to an ICMP Echo request is due in part to the following text extracted from RFC 792 [20]:
某些路由器不返回TTL过期消息以响应ICMP回显请求的行为部分是由于从RFC 792[20]中提取的以下文本：
"The ICMP messages typically report errors in the processing of datagrams. To avoid the infinite regress of messages about messages etc., no ICMP messages are sent about ICMP messages."
ICMP消息通常报告数据报处理过程中的错误。为了避免消息等的无限回归，不发送关于ICMP消息的ICMP消息
Both ping and traceroute yield round-trip times measured in milliseconds. These times can be used as a rough approximation for network transit time.
ping和traceroute都产生以毫秒为单位的往返时间。这些时间可用作网络传输时间的粗略近似值。
The Lookup operation enables the equivalent of either a gethostbyname() or a gethostbyaddr() call being performed at a remote host. The Lookup gethostbyname() capability can be used to determine the symbolic name of a hop in a traceroute path.
查找操作启用在远程主机上执行的gethostbyname（）或gethostbyaddr（）调用的等效项。Lookup gethostbyname（）功能可用于确定跟踪路由路径中跃点的符号名称。
Consider the following diagram:
考虑下面的图表：
+--------------------------------------------------------------------+
| |
| Remote ping, traceroute, Actual ping, traceroute, |
| +-----+or Lookup op. +------+or Lookup op. +------+ |
| |Local|---------------->|Remote|---------------->|Target| |
| | Host| | Host | | Host | |
| +-----+ +------+ +------+ |
| |
| |
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| |
| Remote ping, traceroute, Actual ping, traceroute, |
| +-----+or Lookup op. +------+or Lookup op. +------+ |
| |Local|---------------->|Remote|---------------->|Target| |
| | Host| | Host | | Host | |
| +-----+ +------+ +------+ |
| |
| |
+--------------------------------------------------------------------+
A local host is the host from which the remote ping, traceroute, or Lookup operation is initiated using an SNMP request. The remote host is a host where the MIBs defined by this memo are implemented that receives the remote operation via SNMP and performs the actual ping, traceroute, or lookup function.
本地主机是使用SNMP请求启动远程ping、traceroute或查找操作的主机。远程主机是实现此备忘录定义的MIB的主机，它通过SNMP接收远程操作，并执行实际的ping、traceroute或查找功能。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [7].
o RFC 2571[7]中描述的总体架构。
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 [14], STD 16, RFC 1212 [15] and RFC 1215 [16]. The second version, called SMIv2, is described in STD 58, RFC 2578 [3], STD 58, RFC 2579 [4] and STD 58, RFC 2580 [5].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[14]、STD 16、RFC 1212[15]和RFC 1215[16]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[3]、STD 58、RFC 2579[4]和STD 58、RFC 2580[5]中进行了描述。
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 [1]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [17] and RFC 1906 [18]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [18], RFC 2572 [8] and RFC 2574 [10].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15 RFC 1157[1]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[17]和RFC 1906[18]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[18]、RFC 2572[8]和RFC 2574[10]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [1]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [6].
o 访问管理信息的协议操作。STD 15、RFC 1157[1]中描述了第一组协议操作和相关PDU格式。RFC 1905[6]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [9] and the view-based access control mechanism described in RFC 2575 [11].
o RFC 2573[9]中描述的一组基本应用程序和RFC 2575[11]中描述的基于视图的访问控制机制。
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 MIB modules that are 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的语义。
This document defines three MIB modules:
本文档定义了三个MIB模块：
o DISMAN-PING-MIB
o DISMAN-PING-MIB
Defines a ping MIB.
定义ping MIB。
o DISMAN-TRACEROUTE-MIB
o DISMAN-TRACEROUTE-MIB
Defines a traceroute MIB.
定义跟踪路由MIB。
o DISMAN-NSLOOKUP-MIB
o DISMAN-NSLOOKUP-MIB
Provides access to the resolver gethostbyname() and gethostbyaddr() functions at a remote host.
提供对远程主机上的解析程序gethostbyname（）和gethostbyaddr（）函数的访问。
The ping and traceroute MIBs are structured to allow creation of ping or traceroute tests that can be set up to periodically issue a series of operations and generate NOTIFICATIONs to report on test results. Many network administrators have in the past written UNIX shell scripts or command batch files to operate in fashion similar to the functionality provided by the ping and traceroute MIBs defined within this memo. The intent of this document is to acknowledge the importance of these functions and to provide a standards-based solution.
ping和traceroute mib的结构允许创建ping或traceroute测试，这些测试可以设置为定期发布一系列操作并生成通知以报告测试结果。过去，许多网络管理员编写了UNIX shell脚本或命令批处理文件，以类似于本备忘录中定义的ping和traceroute MIB提供的功能的方式进行操作。本文件旨在确认这些功能的重要性，并提供基于标准的解决方案。
The DISMAN-PING-MIB consists of the following components:
DISAN-PING-MIB由以下组件组成：
o pingMaxConcurrentRequests
o pingMaxConcurrentRequests
o pingCtlTable
o PingCtlable
o pingResultsTable
o pingResultsTable
o pingProbeHistoryTable
o pingProbeHistoryTable
The object pingMaxConcurrentRequests enables control of the maximum number of concurrent active requests that an agent implementation supports. It is permissible for an agent either to limit the maximum upper range allowed for this object or to implement this object as read-only with an implementation limit expressed as its value.
对象pingMaxConcurrentRequests允许控制代理实现支持的最大并发活动请求数。允许代理限制此对象允许的最大上限范围，或者以只读方式实现此对象，实现限制以其值表示。
A remote ping test is started by setting pingCtlAdminStatus to enabled(1). The corresponding pingCtlEntry MUST have been created and its pingCtlRowStatus set to active(1) prior to starting the test. A single SNMP PDU can be used to create and start a remote ping test. Within the PDU, pingCtlTargetAddress should be set to the target host's address (pingCtlTargetAddressType will default to ipv4(1)), pingCtlAdminStatus to enabled(1), and pingCtlRowStatus to createAndGo(4).
通过将pingCtlAdminStatus设置为enabled（1），可以启动远程ping测试。在开始测试之前，必须已创建相应的pingCtlEntry并将其pingCtlRowStatus设置为active（1）。单个SNMP PDU可用于创建和启动远程ping测试。在PDU中，pingCtlTargetAddress应设置为目标主机的地址（pingCtlTargetAddressType默认为ipv4（1）），pingCtlAdminStatus设置为enabled（1），pingCtlRowStatus设置为createAndGo（4）。
The first index element, pingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The send index, pingCtlTestName (also an SnmpAdminString), enables the same management application to have multiple requests outstanding.
第一个索引元素pingCtlOwnerIndex属于SnmpAdminString类型，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 2575[11]，VACM），并允许管理应用程序识别其条目。发送索引pingCtlTestName（也是一个SnmpAdminString）允许同一管理应用程序有多个未完成的请求。
Using the maximum value for the parameters defined within a pingEntry can result in a single remote ping test taking at most 15 minutes (pingCtlTimeOut times pingCtlProbeCount) plus whatever time it takes to send the ping request and receive its response over the network from the target host. Use of the defaults for pingCtlTimeOut and pingCtlProbeCount yields a maximum of 3 seconds to perform a "normal" ping test.
使用pingEntry中定义的参数的最大值可能导致单个远程ping测试最多需要15分钟（pingCtlTimeOut times pingCtlProbeCount）加上发送ping请求并通过网络从目标主机接收响应所需的时间。使用pingCtlTimeOut和pingCtlProbeCount的默认值会产生最多3秒的时间来执行“正常”ping测试。
A management application can delete an active remote ping request by setting the corresponding pingCtlRowStatus object to destroy(6).
管理应用程序可以通过将相应的pingCtlRowStatus对象设置为destroy（6），删除活动的远程ping请求。
The contents of the pingCtlTable is preserved across reIPLs (Initial Program Loads) of its agent according the values of each of the pingCtlStorageType objects.
pingCtlTable的内容根据每个pingCtlStorageType对象的值在其代理的reIPLs（初始程序加载）中保留。
An entry in the pingResultsTable is created for a corresponding pingCtlEntry once the test defined by this entry is started.
启动由该条目定义的测试后，将为相应的pingCtlEntry创建pingResultsTable中的条目。
The results of past ping probes can be stored in this table on a per pingCtlEntry basis. This table is initially indexed by pingCtlOwnerIndex and pingCtlTestName in order for the results of a probe to relate to the pingCtlEntry that caused it. The maximum number of entries stored in this table per pingCtlEntry is determined by the value of pingCtlMaxRows.
过去ping探测的结果可以按每个pingCtlEntry存储在此表中。该表最初由pingCtlOwnerIndex和pingCtlTestName索引，以便探测结果与导致它的pingCtlEntry相关。每个pingCtlEntry在此表中存储的最大条目数由pingCtlMaxRows的值确定。
An implementation of this MIB will remove the oldest entry in the pingProbeHistoryTable to allow the addition of an new entry once the number of rows in the pingProbeHistoryTable reaches the value specified by pingCtlMaxRows. An implementation MUST start assigning pingProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h).
此MIB的实现将删除pingProbeHistoryTable中最旧的条目，以允许在pingProbeHistoryTable中的行数达到pingCtlMaxRows指定的值时添加新条目。实现必须开始将pingProbeHistoryIndex值赋值为1，并在超出此对象的限制（'FFFFFFFFFF'h）定义的最大可能值后换行。
The DISMAN-TRACEROUTE-MIB consists of the following components:
DISAN-TRACEROUTE-MIB由以下组件组成：
o traceRouteMaxConcurrentRequests
o traceRouteMaxConcurrentRequests
o traceRouteCtlTable
o 跟踪表
o traceRouteResultsTable
o 跟踪结果表
o traceRouteProbeHistoryTable
o 跟踪路由ProbeHistorytable
o traceRouteHopsTable
o 示踪剂
The object traceRouteMaxConcurrentRequests enables control of the maximum number of concurrent active requests that an agent implementation supports. It is permissible for an agent either to limit the maximum upper range allowed for this object or to implement this object as read-only with an implementation limit expressed as its value.
对象traceRouteMaxConcurrentRequests允许控制代理实现支持的最大并发活动请求数。允许代理限制此对象允许的最大上限范围，或者以只读方式实现此对象，实现限制以其值表示。
A remote traceroute test is started by setting traceRouteCtlAdminStatus to enabled(1). The corresponding traceRouteCtlEntry MUST have been created and its traceRouteCtlRowStatus set to active(1) prior to starting the test. A single SNMP PDU can be used to create and start a remote traceroute test. Within the PDU, traceRouteCtlTargetAddress should be set to the target host's address (traceRouteCtlTargetAddressType will default to ipv4(1)), traceRouteCtlAdminStatus to enabled(1), and traceRouteCtlRowStatus to createAndGo(4).
通过将TracerOuteClAdminStatus设置为enabled（1），可以启动远程跟踪路由测试。在开始测试之前，必须已创建相应的traceRouteCtlEntry，并将其traceRouteCtlRowStatus设置为active（1）。单个SNMP PDU可用于创建和启动远程跟踪路由测试。在PDU中，traceRouteCtlTargetAddress应设置为目标主机的地址（traceRouteCtlTargetAddressType默认为ipv4（1）），traceRouteCtlAdminStatus设置为enabled（1），traceRouteCtlRowStatus设置为createAndGo（4）。
The first index element, traceRouteCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, traceRouteCtlTestName (also an SnmpAdminString), enables the same management application to have multiple requests outstanding.
第一个索引元素traceRouteCtlOwnerIndex属于SNMPAdministring类型，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 2575[11]，VACM），并允许管理应用程序识别其条目。第二个索引TRACEROUTCTLTESTNAME（也是一个SNMPAdministring）允许同一管理应用程序有多个未完成的请求。
Traceroute has a much longer theoretical maximum time for completion than ping. Basically 42 hours and 30 minutes (the product of traceRouteCtlTimeOut, traceRouteCtlProbesPerHop, and traceRouteCtlMaxTtl) plus some network transit time! Use of the defaults defined within an traceRouteCtlEntry yields a maximum of 4 minutes and 30 seconds for a default traceroute operation. Clearly
Traceroute的理论最长完成时间比ping长得多。基本上是42小时30分钟（traceRouteCtlTimeOut、traceRouteCtlProbesPerHop和traceRouteCtlMaxTtl的乘积）加上一些网络传输时间！使用traceRouteCtlEntry中定义的默认值，默认traceroute操作的最大时间为4分30秒。清晰地
42 plus hours is too long to wait for a traceroute operation to complete.
42个多小时太长，无法等待跟踪路由操作完成。
The maximum TTL value in effect for traceroute determines how long the traceroute function will keep increasing the TTL value in the probe it transmits hoping to reach the target host. The function ends whenever the maximum TTL is exceeded or the target host is reached. The object traceRouteCtlMaxFailures was created in order to impose a throttle for how long traceroute continues to increase the TTL field in a probe without receiving any kind of response (timeouts). It is RECOMMENDED that agent implementations impose a time limit for how long it allows a traceroute operation to take relative to how the function is implemented. For example, an implementation that can't process multiple traceroute operations at the same time SHOULD impose a shorter maximum allowed time period.
traceroute有效的最大TTL值决定了traceroute函数在其发送的探测器中持续增加TTL值以到达目标主机的时间。当超过最大TTL或达到目标主机时，该函数结束。创建对象traceRouteCtlMaxFailures是为了限制traceroute在不接收任何响应（超时）的情况下继续增加探测中的TTL字段的时间。建议代理实现对跟踪路由操作相对于函数实现方式的允许时间设置一个时间限制。例如，不能同时处理多个跟踪路由操作的实现应该施加较短的最大允许时间段。
A management application can delete an active remote traceroute request by setting the corresponding traceRouteCtlRowStatus object to destroy(6).
管理应用程序可以通过将相应的traceRouteCtlRowStatus对象设置为destroy（6），删除活动的远程跟踪路由请求。
The contents of the traceRouteCtlTable is preserved across reIPLs (Initial Program Loads) of its agent according to the values of each of the traceRouteCtlStorageType objects.
traceRouteCtlTable的内容根据每个traceRouteCtlStorageType对象的值在其代理的REIPL（初始程序加载）中保留。
An entry in the traceRouteResultsTable is created upon determining the results of a specific traceroute operation. Entries in this table relate back to the traceRouteCtlEntry that caused the corresponding traceroute operation to occur. The objects traceRouteResultsCurHopCount and traceRouteResultsCurProbeCount can be examined to determine how far the current remote traceroute operation has reached.
在确定特定跟踪路由操作的结果时，将创建跟踪路由结果表中的条目。此表中的条目与导致相应跟踪路由操作发生的跟踪路由CtlEntry相关。可以检查对象TracerOutResultsCurhopCount和TracerOutResultsCurProbeCount，以确定当前远程跟踪路由操作已达到的程度。
The results of past traceroute probes can be stored in this table on a per traceRouteCtlEntry basis. This table is initially indexed by traceRouteCtlOwnerIndex and traceRouteCtlTestName in order for the results of a probe to relate to the traceRouteCtlEntry that caused it. The number of entries stored in this table per traceRouteCtlEntry is determined by the value of traceRouteCtlMaxRows.
过去跟踪路由探测的结果可以按每个跟踪路由条目存储在此表中。此表最初由traceRouteCtlOwnerIndex和traceRouteCtlTestName索引，以便探测结果与导致它的traceRouteCtlEntry相关。每个traceRouteCtlEntry在此表中存储的条目数由traceRouteCtlMaxRows的值确定。
An implementation of this MIB will remove the oldest entry in the traceRouteProbeHistoryTable to allow the addition of an new entry once the number of rows in the traceRouteProbeHistoryTable reaches the value of traceRouteCtlMaxRows. An implementation MUST start
此MIB的实现将删除traceRouteProbeHistoryTable中最旧的条目，以允许在traceRouteProbeHistoryTable中的行数达到traceRouteCtlMaxRows的值时添加新条目。必须开始实施
assigning traceRouteProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h).
将traceRouteProbeHistoryIndex值指定为1，并在超过此对象的限制（'ffffffff'h）定义的最大可能值后进行换行。
The current traceroute path can be stored in this table on a per traceRouteCtlEntry basis. This table is initially indexed by traceRouteCtlOwnerIndex and traceRouteCtlTestName in order for a traceroute path to relate to the traceRouteCtlEntry that caused it. A third index, traceRouteHopsHopIndex, enables keeping one traceRouteHopsEntry per traceroute hop. Creation of traceRouteHopsTable entries is enabled by setting the corresponding traceRouteCtlCreateHopsEntries object to true(1).
当前跟踪路由路径可以按每个跟踪路由条目存储在此表中。此表最初由traceRouteCtlOwnerIndex和traceRouteCtlTestName索引，以便traceroute路径与导致它的traceRouteCtlEntry相关。第三个索引tracerouthopshopIndex允许每个traceroute跃点保留一个tracerouthopsentry。通过将相应的traceRouteCtlCreateHopsEntries对象设置为true（1），可以启用traceRouteHopsTable项的创建。
The DISMAN-NSLOOKUP-MIB consists of the following components:
DISAN-NSLOOKUP-MIB由以下组件组成：
o lookupMaxConcurrentRequests, and lookupPurgeTime
o lookupMaxConcurrentRequests和lookupPurgeTime
o lookupCtlTable
o 查找表
o lookupResultsTable
o 查找结果稳定
The object lookupMaxConcurrentRequests enables control of the maximum number of concurrent active requests that an agent implementation is structured to support. It is permissible for an agent either to limit the maximum upper range allowed for this object or to implement this object as read-only with an implementation limit expressed as its value.
对象lookupMaxConcurrentRequests允许控制代理实现结构化支持的最大并发活动请求数。允许代理限制此对象允许的最大上限范围，或者以只读方式实现此对象，实现限制以其值表示。
The object lookupPurgeTime provides a method for entries in the lookupCtlTable and lookupResultsTable to be automatically deleted after the corresponding operation completes.
对象lookupPurgeTime为lookupCtlTable和lookupResultsTable中的条目提供了一种方法，以便在相应操作完成后自动删除。
A remote lookup operation is initiated by performing an SNMP SET request on lookupCtlRowStatus. A single SNMP PDU can be used to create and start a remote lookup operation. Within the PDU, lookupCtlTargetAddress should be set to the entity to be resolved (lookupCtlTargetAddressType will default to ipv4(1)) and lookupCtlRowStatus to createAndGo(4). The object lookupCtlOperStatus
远程查找操作是通过对lookupCtlRowStatus执行SNMP设置请求来启动的。单个SNMP PDU可用于创建和启动远程查找操作。在PDU中，lookupCtlTargetAddress应设置为要解析的实体（lookupCtlTargetAddressType将默认为ipv4（1）），lookupCtlRowStatus应设置为createAndGo（4）。对象查找状态
can be examined to determine the state of an lookup operation. A management application can delete an active remote lookup request by setting the corresponding lookupCtlRowStatus object to destroy(6).
可以检查以确定查找操作的状态。管理应用程序可以通过将相应的lookupCtlRowStatus对象设置为destroy（6），删除活动的远程查找请求。
An lookupCtlEntry is initially indexed by lookupCtlOwnerIndex, which is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and also allows for a management application to identify its entries. The lookupCtlOwnerIndex portion of the index is then followed by lookupCtlOperationName. The lookupCtlOperationName index enables the same lookupCtlOwnerIndex entity to have multiple outstanding requests.
lookupCtlEntry最初由lookupCtlOwnerIndex编制索引，该索引类型为SNMPAdministring，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 2575[11]，VACM），还允许管理应用程序识别其条目。然后，索引的lookupCtlOwnerIndex部分后跟lookupCtlOperationName。lookupCtlOperationName索引允许同一lookupCtlOwnerIndex实体具有多个未完成的请求。
The value of lookupCtlTargetAddressType determines which lookup function to perform. Specification of dns(16) as the value of this index implies that the gethostbyname function should be performed to determine the numeric addresses associated with a symbolic name via lookupResultsTable entries. Use of a value of either ipv4(1) or ipv6(2) implies that the gethostbyaddr function should be performed to determine the symbolic name(s) associated with a numeric address at a remote host.
lookupCtlTargetAddressType的值确定要执行的查找函数。将dns（16）指定为该索引的值意味着应执行gethostbyname函数，以通过lookupResultsTable条目确定与符号名关联的数字地址。使用ipv4（1）或ipv6（2）的值意味着应执行gethostbyaddr函数以确定与远程主机上的数字地址关联的符号名。
The lookupResultsTable is used to store the results of lookup operations. The lookupResultsTable is initially indexed by the same index elements that the lookupCtlTable contains (lookupCtlOwnerIndex and lookupCtlOperationName) but has a third index element, lookupResultsIndex (Unsigned32 textual convention), in order to associate multiple results with the same lookupCtlEntry.
lookupResultsTable用于存储查找操作的结果。lookupResultsTable最初由lookupCtlTable包含的相同索引元素（lookupCtlOwnerIndex和lookupCtlOperationName）索引，但有第三个索引元素lookupResultsIndex（Unsigned32文本约定），以便将多个结果与同一lookupCtlEntry关联。
Both the gethostbyname and gethostbyaddr functions typically return a pointer to a hostent structure after being called. The hostent structure is defined as:
gethostbyname和gethostbyaddr函数通常在被调用后返回指向hostent结构的指针。主机结构定义为：
struct hostent {
char *h_name; /* official host name */
char *h_aliases[]; /* list of other aliases */
int h_addrtype; /* host address type */
int h_length; /* length of host address */
char **h_addr_list; /* list of address for host */
};
struct hostent {
char *h_name; /* official host name */
char *h_aliases[]; /* list of other aliases */
int h_addrtype; /* host address type */
int h_length; /* length of host address */
char **h_addr_list; /* list of address for host */
};
The hostent structure is listed here in order to address the fact that a remote host can be multi-homed and can have multiple symbolic (DNS) names. It is not intended to imply that implementations of the DISMAN-LOOKUP-MIB are limited to systems where the hostent structure is supported.
此处列出hostent结构是为了解决远程主机可以是多主机且可以有多个符号（DNS）名称的问题。这并不意味着DISAN-LOOKUP-MIB的实现仅限于支持hostent结构的系统。
The gethostbyaddr function is called with a host address as its parameter and is used primarily to determine a symbolic name to associate with the host address. Entries in the lookupResultsTable MUST be made for each host name returned. The official host name MUST be assigned a lookupResultsIndex of 1.
gethostbyaddr函数以主机地址作为参数调用，主要用于确定要与主机地址关联的符号名。必须为返回的每个主机名创建lookupResultsTable中的条目。必须为正式主机名分配lookupResultsIndex 1。
The gethostbyname function is called with a symbolic host name and is used primarily to retrieve a host address. Normally, the first h_addr_list host address is considered to be the primary address and as such is associated with the symbolic name passed on the call.
使用符号主机名调用gethostbyname函数，该函数主要用于检索主机地址。通常，第一个h_addr_列表主机地址被认为是主地址，因此与调用中传递的符号名相关联。
Entries MUST be stored in the lookupResultsTable in the order that they are retrieved. Values assigned to lookupResultsIndex MUST start at 1 and increase in order.
条目必须按照检索顺序存储在lookupResultsTable中。分配给lookupResultsIndex的值必须从1开始，并按顺序递增。
An implementation SHOULD NOT retain SNMP-created entries in the lookupTable across reIPLs (Initial Program Loads) of its agent, since management applications need to see consistent behavior with respect to the persistence of the table entries that they create.
实现不应在其代理的REIPL（初始程序加载）的可查找表中保留SNMP创建的条目，因为管理应用程序需要看到它们创建的表条目的持久性的一致行为。
DISMAN-PING-MIB DEFINITIONS ::= BEGIN
DISMAN-PING-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, mib-2, NOTIFICATION-TYPE, OBJECT-IDENTITY FROM SNMPv2-SMI -- RFC2578 TEXTUAL-CONVENTION, RowStatus, StorageType, DateAndTime, TruthValue FROM SNMPv2-TC -- RFC2579 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC2580 InterfaceIndexOrZero -- RFC2863 FROM IF-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC2571 InetAddressType, InetAddress FROM INET-ADDRESS-MIB; -- RFC2851
从SNMPv2 SMI中导入模块标识、对象类型、整数32、未签名32、mib-2、通知类型、对象标识——从SNMPv2 TC中导入RFC2578文本约定、行状态、存储类型、日期和时间、TruthValue——RFC2579模块合规性、对象组、，SNMPv2 CONF中的通知组--RFC2580 InterfaceIndexOrZero--IF-MIB中的RFC2863 SNMPAdminInstalling FROM SNMP-FRAMEWORK-MIB--RFC2571 InetAddressType，InetAddress FROM INET-ADDRESS-MIB；--RFC2851
pingMIB MODULE-IDENTITY LAST-UPDATED "200009210000Z" -- 21 September 2000 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO
pingMIB模块标识最后更新的“200009210000Z”-2000年9月21日组织“IETF分布式管理工作组”联系方式
"Kenneth White
“肯尼斯·怀特
International Business Machines Corporation Network Computing Software Division Research Triangle Park, NC, USA
国际商用机器公司网络计算软件部美国北卡罗来纳州三角研究园
E-mail: wkenneth@us.ibm.com" DESCRIPTION "The Ping MIB (DISMAN-PING-MIB) provides the capability of controlling the use of the ping function at a remote host."
电邮：wkenneth@us.ibm.com“DESCRIPTION”Ping MIB（DISMAN-Ping-MIB）提供在远程主机上控制Ping功能使用的功能
-- Revision history
--修订历史
REVISION "200009210000Z" -- 21 September 2000 DESCRIPTION "Initial version, published as RFC 2925."
修订版“2000092100Z”-2000年9月21日描述“初始版本，发布为RFC 2925。”
::= { mib-2 80 }
::= { mib-2 80 }
-- Textual Conventions
--文本约定
OperationResponseStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Used to report the result of an operation:
OperationResponseStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Used to report the result of an operation:
responseReceived(1) - Operation completes successfully. unknown(2) - Operation failed due to unknown error. internalError(3) - An implementation detected an error in its own processing that caused an operation to fail. requestTimedOut(4) - Operation failed to receive a valid reply within the time limit imposed on it. unknownDestinationAddress(5) - Invalid destination address. noRouteToTarget(6) - Could not find a route to target. interfaceInactiveToTarget(7) - The interface to be used in sending a probe is inactive without an alternate route existing. arpFailure(8) - Unable to resolve a target address to a media specific address. maxConcurrentLimitReached(9) - The maximum number of concurrent active operations would have been exceeded if the corresponding operation was allowed. unableToResolveDnsName(10) - The DNS name specified was unable to be mapped to an IP address. invalidHostAddress(11) - The IP address for a host
responseReceived（1）-操作成功完成。未知（2）-由于未知错误，操作失败。internalError（3）-实现在其自身处理中检测到导致操作失败的错误。requestTimedOut（4）-操作未能在规定的时间限制内收到有效答复。unknownDestinationAddress（5）-目标地址无效。noRouteToTarget（6）-找不到到到目标的路由。interfaceInactiveToTarget（7）-发送探测器时使用的接口处于非活动状态，且不存在备用路由。arpFailure（8）-无法将目标地址解析为媒体特定地址。MaxConcurrentLimitReach（9）-如果允许相应的操作，则会超过并发活动操作的最大数量。无法解析DNS名称（10）-指定的DNS名称无法映射到IP地址。invalidHostAddress（11）-主机的IP地址
has been determined to be invalid. Examples of this
are broadcast or multicast addresses."
SYNTAX INTEGER {
responseReceived(1),
unknown(2),
internalError(3),
requestTimedOut(4),
unknownDestinationAddress(5),
noRouteToTarget(6),
interfaceInactiveToTarget(7),
arpFailure(8),
maxConcurrentLimitReached(9),
unableToResolveDnsName(10),
invalidHostAddress(11)
}
has been determined to be invalid. Examples of this
are broadcast or multicast addresses."
SYNTAX INTEGER {
responseReceived(1),
unknown(2),
internalError(3),
requestTimedOut(4),
unknownDestinationAddress(5),
noRouteToTarget(6),
interfaceInactiveToTarget(7),
arpFailure(8),
maxConcurrentLimitReached(9),
unableToResolveDnsName(10),
invalidHostAddress(11)
}
-- Top level structure of the MIB
--MIB的顶层结构
pingNotifications OBJECT IDENTIFIER ::= { pingMIB 0 }
pingObjects OBJECT IDENTIFIER ::= { pingMIB 1 }
pingConformance OBJECT IDENTIFIER ::= { pingMIB 2 }
pingNotifications OBJECT IDENTIFIER ::= { pingMIB 0 }
pingObjects OBJECT IDENTIFIER ::= { pingMIB 1 }
pingConformance OBJECT IDENTIFIER ::= { pingMIB 2 }
-- The registration node (point) for ping implementation types
--ping实现类型的注册节点（点）
pingImplementationTypeDomains OBJECT IDENTIFIER ::= { pingMIB 3 }
pingImplementationTypeDomains OBJECT IDENTIFIER ::= { pingMIB 3 }
pingIcmpEcho OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using the Internet
Control Message Protocol (ICMP) 'ECHO' facility."
::= { pingImplementationTypeDomains 1 }
pingIcmpEcho OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using the Internet
Control Message Protocol (ICMP) 'ECHO' facility."
::= { pingImplementationTypeDomains 1 }
pingUdpEcho OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using the UDP echo
port (7)."
REFERENCE
"RFC 862, 'Echo Protocol'."
::= { pingImplementationTypeDomains 2 }
pingUdpEcho OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using the UDP echo
port (7)."
REFERENCE
"RFC 862, 'Echo Protocol'."
::= { pingImplementationTypeDomains 2 }
pingSnmpQuery OBJECT-IDENTITY STATUS current DESCRIPTION "Indicates that an implementation is an SNMP query to calculate a round trip time."
pingSnmpQuery OBJECT-IDENTITY STATUS current DESCRIPTION“表示实现是用于计算往返时间的SNMP查询。”
::= { pingImplementationTypeDomains 3 }
::= { pingImplementationTypeDomains 3 }
pingTcpConnectionAttempt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is attempting to
connect to a TCP port in order to calculate a round
trip time."
::= { pingImplementationTypeDomains 4 }
pingTcpConnectionAttempt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is attempting to
connect to a TCP port in order to calculate a round
trip time."
::= { pingImplementationTypeDomains 4 }
-- Simple Object Definitions
--简单对象定义
pingMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active ping requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { pingObjects 1 }
pingMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active ping requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { pingObjects 1 }
-- Ping Control Table
--Ping控制表
pingCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF PingCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the ping Control Table for providing, via SNMP,
the capability of performing ping operations at
a remote host. The results of these operations are
stored in the pingResultsTable and the
pingProbeHistoryTable."
::= { pingObjects 2 }
pingCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF PingCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the ping Control Table for providing, via SNMP,
the capability of performing ping operations at
a remote host. The results of these operations are
stored in the pingResultsTable and the
pingProbeHistoryTable."
::= { pingObjects 2 }
pingCtlEntry OBJECT-TYPE SYNTAX PingCtlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the pingCtlTable. The first index element, pingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3
pingCtlEntry对象类型语法pingCtlEntry MAX-ACCESS not accessible STATUS current DESCRIPTION”在pingCtlTable中定义了一个条目。第一个索引元素pingCtlOwnerIndex的类型为SNMPAdministring，这是一种允许使用SNMPv3的文本约定
View-Based Access Control Model (RFC 2575 [11], VACM)
and allows an management application to identify its
entries. The second index, pingCtlTestName (also an
SnmpAdminString), enables the same management
application to have multiple outstanding requests."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName
}
::= { pingCtlTable 1 }
View-Based Access Control Model (RFC 2575 [11], VACM)
and allows an management application to identify its
entries. The second index, pingCtlTestName (also an
SnmpAdminString), enables the same management
application to have multiple outstanding requests."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName
}
::= { pingCtlTable 1 }
PingCtlEntry ::=
SEQUENCE {
pingCtlOwnerIndex SnmpAdminString,
pingCtlTestName SnmpAdminString,
pingCtlTargetAddressType InetAddressType,
pingCtlTargetAddress InetAddress,
pingCtlDataSize Unsigned32,
pingCtlTimeOut Unsigned32,
pingCtlProbeCount Unsigned32,
pingCtlAdminStatus INTEGER,
pingCtlDataFill OCTET STRING,
pingCtlFrequency Unsigned32,
pingCtlMaxRows Unsigned32,
pingCtlStorageType StorageType,
pingCtlTrapGeneration BITS,
pingCtlTrapProbeFailureFilter Unsigned32,
pingCtlTrapTestFailureFilter Unsigned32,
pingCtlType OBJECT IDENTIFIER,
pingCtlDescr SnmpAdminString,
pingCtlSourceAddressType InetAddressType,
pingCtlSourceAddress InetAddress,
pingCtlIfIndex InterfaceIndexOrZero,
pingCtlByPassRouteTable TruthValue,
pingCtlDSField Unsigned32,
pingCtlRowStatus RowStatus
}
PingCtlEntry ::=
SEQUENCE {
pingCtlOwnerIndex SnmpAdminString,
pingCtlTestName SnmpAdminString,
pingCtlTargetAddressType InetAddressType,
pingCtlTargetAddress InetAddress,
pingCtlDataSize Unsigned32,
pingCtlTimeOut Unsigned32,
pingCtlProbeCount Unsigned32,
pingCtlAdminStatus INTEGER,
pingCtlDataFill OCTET STRING,
pingCtlFrequency Unsigned32,
pingCtlMaxRows Unsigned32,
pingCtlStorageType StorageType,
pingCtlTrapGeneration BITS,
pingCtlTrapProbeFailureFilter Unsigned32,
pingCtlTrapTestFailureFilter Unsigned32,
pingCtlType OBJECT IDENTIFIER,
pingCtlDescr SnmpAdminString,
pingCtlSourceAddressType InetAddressType,
pingCtlSourceAddress InetAddress,
pingCtlIfIndex InterfaceIndexOrZero,
pingCtlByPassRouteTable TruthValue,
pingCtlDSField Unsigned32,
pingCtlRowStatus RowStatus
}
pingCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner
pingCtlOwnerIndex对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS not accessible STATUS current DESCRIPTION“以便于安全管理员使用基于视图的访问控制模型（RFC 2575，VACM）提供访问控制对于多个用户可能需要独立创建或修改条目的表，初始索引用作“所有者”
index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy.
索引'。这样的初始索引具有snmpadmin语法，因此可以根据安全策略简单地映射到VACM中定义的securityName或groupName。
When used in conjunction with such a security policy all
entries in the table belonging to a particular user (or
group) will have the same value for this initial index.
For a given user's entries in a particular table, the
object identifiers for the information in these entries
will have the same subidentifiers (except for the 'column'
subidentifier) up to the end of the encoded owner index.
To configure VACM to permit access to this portion of the
table, one would create vacmViewTreeFamilyTable entries
with the value of vacmViewTreeFamilySubtree including
the owner index portion, and vacmViewTreeFamilyMask
'wildcarding' the column subidentifier. More elaborate
configurations are possible."
::= { pingCtlEntry 1 }
When used in conjunction with such a security policy all
entries in the table belonging to a particular user (or
group) will have the same value for this initial index.
For a given user's entries in a particular table, the
object identifiers for the information in these entries
will have the same subidentifiers (except for the 'column'
subidentifier) up to the end of the encoded owner index.
To configure VACM to permit access to this portion of the
table, one would create vacmViewTreeFamilyTable entries
with the value of vacmViewTreeFamilySubtree including
the owner index portion, and vacmViewTreeFamilyMask
'wildcarding' the column subidentifier. More elaborate
configurations are possible."
::= { pingCtlEntry 1 }
pingCtlTestName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of the ping test. This is locally unique, within
the scope of an pingCtlOwnerIndex."
::= { pingCtlEntry 2 }
pingCtlTestName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of the ping test. This is locally unique, within
the scope of an pingCtlOwnerIndex."
::= { pingCtlEntry 2 }
pingCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of host address to be used at a remote
host for performing a ping operation."
DEFVAL { unknown }
::= { pingCtlEntry 3 }
pingCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of host address to be used at a remote
host for performing a ping operation."
DEFVAL { unknown }
::= { pingCtlEntry 3 }
pingCtlTargetAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType.
pingCtlTargetAddress对象类型语法InetAddress MAX-ACCESS读取创建状态当前描述”指定远程主机上用于执行ping操作的主机地址。主机地址类型由相应pingCtlTargetAddressType的对象值确定。
A value for this object MUST be set prior to transitioning
its corresponding pingCtlEntry to active(1) via
pingCtlRowStatus."
DEFVAL { ''H }
::= { pingCtlEntry 4 }
A value for this object MUST be set prior to transitioning
its corresponding pingCtlEntry to active(1) via
pingCtlRowStatus."
DEFVAL { ''H }
::= { pingCtlEntry 4 }
pingCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping
request is usually an ICMP message encoded
into an IP packet. An IP packet has a maximum size
of 65535 octets. Subtracting the size of the ICMP
or UDP header (both 8 octets) and the size of the IP
header (20 octets) yields a maximum size of 65507
octets."
DEFVAL { 0 }
::= { pingCtlEntry 5 }
pingCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping
request is usually an ICMP message encoded
into an IP packet. An IP packet has a maximum size
of 65535 octets. Subtracting the size of the ICMP
or UDP header (both 8 octets) and the size of the IP
header (20 octets) yields a maximum size of 65507
octets."
DEFVAL { 0 }
::= { pingCtlEntry 5 }
pingCtlTimeOut OBJECT-TYPE
SYNTAX Unsigned32 (1..60)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time-out value, in seconds, for a
remote ping operation."
DEFVAL { 3 }
::= { pingCtlEntry 6 }
pingCtlTimeOut OBJECT-TYPE
SYNTAX Unsigned32 (1..60)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time-out value, in seconds, for a
remote ping operation."
DEFVAL { 3 }
::= { pingCtlEntry 6 }
pingCtlProbeCount OBJECT-TYPE
SYNTAX Unsigned32 (1..15)
UNITS "probes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of times to perform a ping
operation at a remote host."
DEFVAL { 1 }
::= { pingCtlEntry 7 }
pingCtlProbeCount OBJECT-TYPE
SYNTAX Unsigned32 (1..15)
UNITS "probes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of times to perform a ping
operation at a remote host."
DEFVAL { 1 }
::= { pingCtlEntry 7 }
pingCtlAdminStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), -- test should be started
pingCtlAdminStatus对象类型语法整数{enabled（1），--应启动测试
disabled(2) -- test should be stopped } MAX-ACCESS read-create STATUS current DESCRIPTION "Reflects the desired state that a pingCtlEntry should be in:
已禁用（2）--应停止测试}MAX-ACCESS read create STATUS current DESCRIPTION“反映PingCtlENT应处于的所需状态：
enabled(1) - Attempt to activate the test as defined by this pingCtlEntry. disabled(2) - Deactivate the test as defined by this pingCtlEntry.
已启用（1）-尝试激活此条目定义的测试。禁用（2）-根据此条目定义停用测试。
Refer to the corresponding pingResultsOperStatus to
determine the operational state of the test defined by
this entry."
DEFVAL { disabled }
::= { pingCtlEntry 8 }
Refer to the corresponding pingResultsOperStatus to
determine the operational state of the test defined by
this entry."
DEFVAL { disabled }
::= { pingCtlEntry 8 }
pingCtlDataFill OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The content of this object is used together with the
corresponding pingCtlDataSize value to determine how to
fill the data portion of a probe packet. The option of
selecting a data fill pattern can be useful when links
are compressed or have data pattern sensitivities. The
contents of pingCtlDataFill should be repeated in a ping
packet when the size of the data portion of the ping
packet is greater than the size of pingCtlDataFill."
DEFVAL { '00'H }
::= { pingCtlEntry 9 }
pingCtlDataFill OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The content of this object is used together with the
corresponding pingCtlDataSize value to determine how to
fill the data portion of a probe packet. The option of
selecting a data fill pattern can be useful when links
are compressed or have data pattern sensitivities. The
contents of pingCtlDataFill should be repeated in a ping
packet when the size of the data portion of the ping
packet is greater than the size of pingCtlDataFill."
DEFVAL { '00'H }
::= { pingCtlEntry 9 }
pingCtlFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of seconds to wait before repeating a ping test as defined by the value of the various objects in the corresponding row.
pingCtlFrequency对象类型语法Unsigned32单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“重复ping测试之前等待的秒数，由相应行中各种对象的值定义。
A single ping test consists of a series of ping probes. The number of probes is determined by the value of the corresponding pingCtlProbeCount object. After a single
单个ping测试由一系列ping探针组成。探测的数量由相应pingCtlProbeCount对象的值确定。过了一个星期
test completes the number of seconds as defined by the value of pingCtlFrequency MUST elapse before the next ping test is started.
测试完成pingCtlFrequency值定义的秒数必须在下一个ping测试开始之前经过。
A value of 0 for this object implies that the test
as defined by the corresponding entry will not be
repeated."
DEFVAL { 0 }
::= { pingCtlEntry 10 }
A value of 0 for this object implies that the test
as defined by the corresponding entry will not be
repeated."
DEFVAL { 0 }
::= { pingCtlEntry 10 }
pingCtlMaxRows OBJECT-TYPE SYNTAX Unsigned32 UNITS "rows" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of entries allowed in the pingProbeHistoryTable. An implementation of this MIB will remove the oldest entry in the pingProbeHistoryTable to allow the addition of an new entry once the number of rows in the pingProbeHistoryTable reaches this value.
pingCtlMaxRows对象类型语法无符号32个单位“行”最大访问读取创建状态当前描述“pingProbeHistoryTable中允许的最大条目数。此MIB的实现将删除pingProbeHistoryTable中最旧的条目，以允许在pingProbeHistoryTable中的行数达到此值时添加新条目。
Old entries are not removed when a new test is started. Entries are added to the pingProbeHistoryTable until pingCtlMaxRows is reached before entries begin to be removed.
启动新测试时，不会删除旧条目。条目被添加到pingProbeHistoryTable中，直到到达pingCtlMaxRows后才开始删除条目。
A value of 0 for this object disables creation of
pingProbeHistoryTable entries."
DEFVAL { 50 }
::= { pingCtlEntry 11 }
A value of 0 for this object disables creation of
pingProbeHistoryTable entries."
DEFVAL { 50 }
::= { pingCtlEntry 11 }
pingCtlStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { pingCtlEntry 12 }
pingCtlStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { pingCtlEntry 12 }
pingCtlTrapGeneration OBJECT-TYPE SYNTAX BITS { probeFailure(0), testFailure(1),
pingCtlTrapGeneration对象类型语法位{probeFailure（0），testFailure（1），
testCompletion(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object determines when and if to generate a notification for this entry:
testCompletion（2）}MAX-ACCESS read create STATUS current DESCRIPTION“此对象的值确定何时以及是否为此条目生成通知：
probeFailure(0) - Generate a pingProbeFailed notification subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of successive probe failures that are required before a pingProbeFailed notification can be generated. testFailure(1) - Generate a pingTestFailed notification. In this instance the object pingCtlTrapTestFailureFilter can be used to determine the number of probe failures that signal when a test fails. testCompletion(2) - Generate a pingTestCompleted notification.
probeFailure（0）-根据PingCtlTrappProbeFailureFilter的值生成pingProbeFailed通知。对象pingCtlTrapProbeFailureFilter可用于指定生成pingProbeFailed通知之前所需的连续探测失败数。testFailure（1）-生成pingTestFailed通知。在本例中，对象pingCtlTrapTestFailureFilter可用于确定测试失败时发出信号的探针故障数。testCompletion（2）-生成pingTestCompleted通知。
The value of this object defaults to zero, indicating
that none of the above options have been selected."
::= { pingCtlEntry 13 }
The value of this object defaults to zero, indicating
that none of the above options have been selected."
::= { pingCtlEntry 13 }
pingCtlTrapProbeFailureFilter OBJECT-TYPE SYNTAX Unsigned32 (0..15) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used to determine when to generate a pingProbeFailed NOTIFICATION.
pingCtlTrapProbeFailureFilter对象类型语法Unsigned32（0..15）MAX-ACCESS read create STATUS current DESCRIPTION“此对象的值用于确定何时生成pingProbeFailed通知。
Setting pingCtlTrapGeneration
to probeFailure(0) implies that a pingProbeFailed
NOTIFICATION is generated only when the number of
successive probe failures as indicated by the
value of pingCtlTrapPrbefailureFilter fail within
a given ping test."
DEFVAL { 1 }
::= { pingCtlEntry 14 }
Setting pingCtlTrapGeneration
to probeFailure(0) implies that a pingProbeFailed
NOTIFICATION is generated only when the number of
successive probe failures as indicated by the
value of pingCtlTrapPrbefailureFilter fail within
a given ping test."
DEFVAL { 1 }
::= { pingCtlEntry 14 }
pingCtlTrapTestFailureFilter OBJECT-TYPE SYNTAX Unsigned32 (0..15) MAX-ACCESS read-create STATUS current
pingCtlTrapTestFailureFilter对象类型语法未签名32（0..15）最大访问读取创建状态当前
DESCRIPTION "The value of this object is used to determine when to generate a pingTestFailed NOTIFICATION.
DESCRIPTION“此对象的值用于确定何时生成pingTestFailed通知。
Setting pingCtlTrapGeneration to testFailure(1)
implies that a pingTestFailed NOTIFICATION is
generated only when the number of ping failures
within a test exceed the value of
pingCtlTrapTestFailureFilter."
DEFVAL { 1 }
::= { pingCtlEntry 15 }
Setting pingCtlTrapGeneration to testFailure(1)
implies that a pingTestFailed NOTIFICATION is
generated only when the number of ping failures
within a test exceed the value of
pingCtlTrapTestFailureFilter."
DEFVAL { 1 }
::= { pingCtlEntry 15 }
pingCtlType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used to either report or select the implementation method to be used for calculating a ping response time. The value of this object MAY be selected from pingImplementationTypeDomains.
pingCtlType对象类型语法对象标识符MAX-ACCESS读取创建状态当前描述“此对象的值用于报告或选择用于计算ping响应时间的实现方法。此对象的值可以从pingImplementationTypeDomains中选择。
Additional implementation types SHOULD be allocated as
required by implementers of the DISMAN-PING-MIB under
their enterprise specific registration point and not
beneath pingImplementationTypeDomains."
DEFVAL { pingIcmpEcho }
::= { pingCtlEntry 16 }
Additional implementation types SHOULD be allocated as
required by implementers of the DISMAN-PING-MIB under
their enterprise specific registration point and not
beneath pingImplementationTypeDomains."
DEFVAL { pingIcmpEcho }
::= { pingCtlEntry 16 }
pingCtlDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The purpose of this object is to provide a
descriptive name of the remote ping test."
DEFVAL { '00'H }
::= { pingCtlEntry 17 }
pingCtlDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The purpose of this object is to provide a
descriptive name of the remote ping test."
DEFVAL { '00'H }
::= { pingCtlEntry 17 }
pingCtlSourceAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the type of the source address, pingCtlSourceAddress, to be used at a remote host when performing a ping operation." DEFVAL { ipv4 }
pingCtlSourceAddressType对象类型语法InetAddressType MAX-ACCESS读取创建状态当前描述“指定执行ping操作时在远程主机上使用的源地址pingCtlSourceAddress的类型。”DEFVAL{ipv4}
::= { pingCtlEntry 18 }
::= { pingCtlEntry 18 }
pingCtlSourceAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Use the specified IP address (which must be given in numeric form, not as a hostname) as the source address in outgoing probe packets. On hosts with more than one IP address, this option can be used to force the source address to be something other than the primary IP address of the interface the probe packet is sent on. If the IP address is not one of this machine's interface addresses, an error is returned and nothing is sent. A zero length octet string value for this object disables source address specification.
pingCtlSourceAddress对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“使用指定的IP地址（必须以数字形式提供，而不是作为主机名提供）作为传出探测数据包中的源地址。在具有多个IP地址的主机上，此选项可用于强制源地址不是发送探测数据包的接口的主IP地址。如果该IP地址不是此计算机的接口地址之一，则返回错误，且不发送任何内容。A此对象的零长度八位字节字符串值将禁用源地址规范。
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingCtlSourceAddressType."
DEFVAL { ''H }
::= { pingCtlEntry 19 }
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingCtlSourceAddressType."
DEFVAL { ''H }
::= { pingCtlEntry 19 }
pingCtlIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Setting this object to an interface's ifIndex prior
to starting a remote ping operation directs
the ping probes to be transmitted over the
specified interface. A value of zero for this object
means that this option is not enabled."
DEFVAL { 0 }
::= { pingCtlEntry 20 }
pingCtlIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Setting this object to an interface's ifIndex prior
to starting a remote ping operation directs
the ping probes to be transmitted over the
specified interface. A value of zero for this object
means that this option is not enabled."
DEFVAL { 0 }
::= { pingCtlEntry 20 }
pingCtlByPassRouteTable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "The purpose of this object is to optionally enable bypassing the route table. If enabled, the remote host will bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-attached network, an
pingCtlByPassRouteTable对象类型语法TruthValue MAX-ACCESS读取创建状态当前描述“此对象的目的是可选地启用绕过路由表。如果启用，远程主机将绕过正常路由表，直接发送到连接网络上的主机。如果主机不在直接连接的网络上，则
error is returned. This option can be used to perform
the ping operation to a local host through an
interface that has no route defined (e.g., after the
interface was dropped by routed)."
DEFVAL { false }
::= { pingCtlEntry 21 }
error is returned. This option can be used to perform
the ping operation to a local host through an
interface that has no route defined (e.g., after the
interface was dropped by routed)."
DEFVAL { false }
::= { pingCtlEntry 21 }
pingCtlDSField OBJECT-TYPE SYNTAX Unsigned32 (0..255) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the value to store in the Differentiated Services (DS) Field in the IP packet used to encapsulate the ping probe. The DS Field is defined as the Type of Service (TOS) octet in a IPv4 header or as the Traffic Class octet in a IPv6 header.
PingCtldSpield对象类型语法Unsigned32（0..255）MAX-ACCESS read create STATUS current DESCRIPTION“指定用于封装ping探测的IP数据包中差异化服务（DS）字段中要存储的值。DS字段定义为服务类型（TOS）IPv4标头中的八位字节或IPv6标头中的流量类八位字节。
The value of this object must be a decimal integer
in the range from 0 to 255. This option can be used
to determine what effect an explicit DS Field setting
has on a ping response. Not all values are legal or
meaningful. A value of 0 means that the function
represented by this option is not supported. DS Field
usage is often not supported by IP implementations and
not all values are supported. Refer to RFC 2474 for
guidance on usage of this field."
REFERENCE
"Refer to RFC 2474 for the definition of the
Differentiated Services Field and to RFC 1812
Section 5.3.2 for Type of Service (TOS)."
DEFVAL { 0 }
::= { pingCtlEntry 22 }
The value of this object must be a decimal integer
in the range from 0 to 255. This option can be used
to determine what effect an explicit DS Field setting
has on a ping response. Not all values are legal or
meaningful. A value of 0 means that the function
represented by this option is not supported. DS Field
usage is often not supported by IP implementations and
not all values are supported. Refer to RFC 2474 for
guidance on usage of this field."
REFERENCE
"Refer to RFC 2474 for the definition of the
Differentiated Services Field and to RFC 1812
Section 5.3.2 for Type of Service (TOS)."
DEFVAL { 0 }
::= { pingCtlEntry 22 }
pingCtlRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the pingCtlTable. Deletion of an entry in this table results in all corresponding (same pingCtlOwnerIndex and pingCtlTestName index values) pingResultsTable and pingProbeHistoryTable entries being deleted.
pingCtlRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在pingCtlTable中创建和删除条目。删除此表中的条目会产生所有相应的（相同的pingCtlOwnerIndex和pingCtlTestName索引值）正在删除pingResultsTable和pingProbeHistoryTable项。
A value MUST be specified for pingCtlTargetAddress prior to a transition to active(1) state being
在转换到活动（1）状态之前，必须为pingCtlTargetAddress指定一个值
accepted.
认可的。
Activation of a remote ping operation is controlled via pingCtlAdminStatus and not by changing this object's value to active(1).
远程ping操作的激活是通过pingCtlAdminStatus控制的，而不是通过将此对象的值更改为active（1）来控制的。
Transitions in and out of active(1) state are not allowed while an entry's pingResultsOperStatus is active(1) with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active ping operation.
当条目的PingResultsOperatStatus处于活动状态（1）时，不允许进入和退出活动（1）状态，除非通过将其RowStatus对象设置为destroy（6）删除此表中的条目将停止活动的ping操作。
The operational state of a ping operation
can be determined by examination of its
pingResultsOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579, 'Textual
Conventions for SMIv2.'"
::= { pingCtlEntry 23 }
The operational state of a ping operation
can be determined by examination of its
pingResultsOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579, 'Textual
Conventions for SMIv2.'"
::= { pingCtlEntry 23 }
-- Ping Results Table
--Ping结果表
pingResultsTable OBJECT-TYPE SYNTAX SEQUENCE OF PingResultsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the Ping Results Table for providing the capability of performing ping operations at a remote host. The results of these operations are stored in the pingResultsTable and the pingPastProbeTable.
pingResultsTable PingResultsEntry MAX-ACCESS不可访问状态当前描述的对象类型语法序列“定义Ping结果表，用于提供在远程主机上执行Ping操作的功能。这些操作的结果存储在pingResultsTable和pingPastProbeTable中。
An entry is added to the pingResultsTable when an
pingCtlEntry is started by successful transition
of its pingCtlAdminStatus object to enabled(1).
An entry is removed from the pingResultsTable when
its corresponding pingCtlEntry is deleted."
::= { pingObjects 3 }
An entry is added to the pingResultsTable when an
pingCtlEntry is started by successful transition
of its pingCtlAdminStatus object to enabled(1).
An entry is removed from the pingResultsTable when
its corresponding pingCtlEntry is deleted."
::= { pingObjects 3 }
pingResultsEntry OBJECT-TYPE SYNTAX PingResultsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the pingResultsTable. The pingResultsTable has the same indexing as the pingCtlTable in order for a pingResultsEntry to
pingResultsEntry对象类型语法pingResultsEntry MAX-ACCESS不可访问状态当前描述”在pingResultsTable中定义了一个条目。pingResultsTable与pingCtlTable具有相同的索引，以便pingResultsEntry
correspond to the pingCtlEntry that caused it to
be created."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName
}
::= { pingResultsTable 1 }
correspond to the pingCtlEntry that caused it to
be created."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName
}
::= { pingResultsTable 1 }
PingResultsEntry ::=
SEQUENCE {
pingResultsOperStatus INTEGER,
pingResultsIpTargetAddressType InetAddressType,
pingResultsIpTargetAddress InetAddress,
pingResultsMinRtt Unsigned32,
pingResultsMaxRtt Unsigned32,
pingResultsAverageRtt Unsigned32,
pingResultsProbeResponses Unsigned32,
pingResultsSentProbes Unsigned32,
pingResultsRttSumOfSquares Unsigned32,
pingResultsLastGoodProbe DateAndTime
}
PingResultsEntry ::=
SEQUENCE {
pingResultsOperStatus INTEGER,
pingResultsIpTargetAddressType InetAddressType,
pingResultsIpTargetAddress InetAddress,
pingResultsMinRtt Unsigned32,
pingResultsMaxRtt Unsigned32,
pingResultsAverageRtt Unsigned32,
pingResultsProbeResponses Unsigned32,
pingResultsSentProbes Unsigned32,
pingResultsRttSumOfSquares Unsigned32,
pingResultsLastGoodProbe DateAndTime
}
pingResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2) -- test has stopped
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped."
::= { pingResultsEntry 1 }
pingResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2) -- test has stopped
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped."
::= { pingResultsEntry 1 }
pingResultsIpTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding pingResultsIpTargetAddress
object."
DEFVAL { unknown }
::= { pingResultsEntry 2 }
pingResultsIpTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding pingResultsIpTargetAddress
object."
DEFVAL { unknown }
::= { pingResultsEntry 2 }
pingResultsIpTargetAddress OBJECT-TYPE SYNTAX InetAddress
pingResultsIpTargetAddress对象类型语法InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects reports the IP address associated
with a pingCtlTargetAddress value when the destination
address is specified as a DNS name. The value of
this object should be a zero length octet string
when a DNS name is not specified or when a
specified DNS name fails to resolve."
DEFVAL { ''H }
::= { pingResultsEntry 3 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects reports the IP address associated
with a pingCtlTargetAddress value when the destination
address is specified as a DNS name. The value of
this object should be a zero length octet string
when a DNS name is not specified or when a
specified DNS name fails to resolve."
DEFVAL { ''H }
::= { pingResultsEntry 3 }
pingResultsMinRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum ping round-trip-time (RTT) received. A value
of 0 for this object implies that no RTT has been received."
::= { pingResultsEntry 4 }
pingResultsMinRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum ping round-trip-time (RTT) received. A value
of 0 for this object implies that no RTT has been received."
::= { pingResultsEntry 4 }
pingResultsMaxRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum ping round-trip-time (RTT) received. A value
of 0 for this object implies that no RTT has been received."
::= { pingResultsEntry 5 }
pingResultsMaxRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum ping round-trip-time (RTT) received. A value
of 0 for this object implies that no RTT has been received."
::= { pingResultsEntry 5 }
pingResultsAverageRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current average ping round-trip-time (RTT)."
::= { pingResultsEntry 6 }
pingResultsAverageRtt OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current average ping round-trip-time (RTT)."
::= { pingResultsEntry 6 }
pingResultsProbeResponses OBJECT-TYPE SYNTAX Unsigned32 UNITS "responses" MAX-ACCESS read-only STATUS current DESCRIPTION "Number of responses received for the corresponding
pingResultsProbeResponses对象类型语法无符号32个单元“响应”最大访问只读状态当前描述“为相应的
pingCtlEntry and pingResultsEntry. The value of this object
MUST be reported as 0 when no probe responses have been
received."
::= { pingResultsEntry 7 }
pingCtlEntry and pingResultsEntry. The value of this object
MUST be reported as 0 when no probe responses have been
received."
::= { pingResultsEntry 7 }
pingResultsSentProbes OBJECT-TYPE
SYNTAX Unsigned32
UNITS "probes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object reflects the number of probes sent
for the corresponding pingCtlEntry and pingResultsEntry.
The value of this object MUST be reported as 0 when no probes
have been sent."
::= { pingResultsEntry 8 }
pingResultsSentProbes OBJECT-TYPE
SYNTAX Unsigned32
UNITS "probes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object reflects the number of probes sent
for the corresponding pingCtlEntry and pingResultsEntry.
The value of this object MUST be reported as 0 when no probes
have been sent."
::= { pingResultsEntry 8 }
pingResultsRttSumOfSquares OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the sum of the squares for all ping
responses received. Its purpose is to enable standard
deviation calculation. The value of this object MUST
be reported as 0 when no ping responses have been
received."
::= { pingResultsEntry 9 }
pingResultsRttSumOfSquares OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the sum of the squares for all ping
responses received. Its purpose is to enable standard
deviation calculation. The value of this object MUST
be reported as 0 when no ping responses have been
received."
::= { pingResultsEntry 9 }
pingResultsLastGoodProbe OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time when the last response was received for
a probe."
::= { pingResultsEntry 10 }
pingResultsLastGoodProbe OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time when the last response was received for
a probe."
::= { pingResultsEntry 10 }
-- Ping Probe History Table
--Ping探针历史记录表
pingProbeHistoryTable OBJECT-TYPE SYNTAX SEQUENCE OF PingProbeHistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines a table for storing the results of a ping operation. Entries in this table are limited by
PingProbeHistoryEntry MAX-ACCESS不可访问状态当前描述的pingProbeHistoryTable对象类型语法序列“定义了一个用于存储ping操作结果的表。此表中的条目受以下限制：
the value of the corresponding pingCtlMaxRows object.
对应pingCtlMaxRows对象的值。
An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to. An entry is removed from this table when its corresponding pingCtlEntry is deleted.
此表中的一个条目是在确定ping探测结果时创建的。初始的2个实例标识符索引值标识探测结果（pingProbeHistoryEntry）所属的pingCtlEntry。删除相应的pingCtlEntry时，将从此表中删除条目。
An implementation of this MIB will remove the oldest
entry in the pingProbeHistoryTable to allow the
addition of an new entry once the number of rows in
the pingProbeHistoryTable reaches the value specified
by pingCtlMaxRows."
::= { pingObjects 4 }
An implementation of this MIB will remove the oldest
entry in the pingProbeHistoryTable to allow the
addition of an new entry once the number of rows in
the pingProbeHistoryTable reaches the value specified
by pingCtlMaxRows."
::= { pingObjects 4 }
pingProbeHistoryEntry OBJECT-TYPE
SYNTAX PingProbeHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the pingProbeHistoryTable.
The first two index elements identify the
pingCtlEntry that a pingProbeHistoryEntry belongs
to. The third index element selects a single
probe result."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName,
pingProbeHistoryIndex
}
::= { pingProbeHistoryTable 1 }
pingProbeHistoryEntry OBJECT-TYPE
SYNTAX PingProbeHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the pingProbeHistoryTable.
The first two index elements identify the
pingCtlEntry that a pingProbeHistoryEntry belongs
to. The third index element selects a single
probe result."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName,
pingProbeHistoryIndex
}
::= { pingProbeHistoryTable 1 }
PingProbeHistoryEntry ::=
SEQUENCE {
pingProbeHistoryIndex Unsigned32,
pingProbeHistoryResponse Unsigned32,
pingProbeHistoryStatus OperationResponseStatus,
pingProbeHistoryLastRC Integer32,
pingProbeHistoryTime DateAndTime
}
PingProbeHistoryEntry ::=
SEQUENCE {
pingProbeHistoryIndex Unsigned32,
pingProbeHistoryResponse Unsigned32,
pingProbeHistoryStatus OperationResponseStatus,
pingProbeHistoryLastRC Integer32,
pingProbeHistoryTime DateAndTime
}
pingProbeHistoryIndex OBJECT-TYPE SYNTAX Unsigned32 (1..'ffffffff'h) MAX-ACCESS not-accessible STATUS current DESCRIPTION
pingProbeHistoryIndex对象类型语法Unsigned32（1..'ffffffff'h）MAX-ACCESS不可访问状态当前描述
"An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to.
“此表中的一个条目是在确定ping探测结果时创建的。初始的2个实例标识符索引值标识探测结果（pingProbeHistoryEntry）所属的pingCtlEntry。
An implementation MUST start assigning
pingProbeHistoryIndex values at 1 and wrap after
exceeding the maximum possible value as defined by
the limit of this object ('ffffffff'h)."
::= { pingProbeHistoryEntry 1 }
An implementation MUST start assigning
pingProbeHistoryIndex values at 1 and wrap after
exceeding the maximum possible value as defined by
the limit of this object ('ffffffff'h)."
::= { pingProbeHistoryEntry 1 }
pingProbeHistoryResponse OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time measured in milliseconds from when
a probe was sent to when its response was received or
when it timed out. The value of this object is reported
as 0 when it is not possible to transmit a probe."
::= { pingProbeHistoryEntry 2 }
pingProbeHistoryResponse OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time measured in milliseconds from when
a probe was sent to when its response was received or
when it timed out. The value of this object is reported
as 0 when it is not possible to transmit a probe."
::= { pingProbeHistoryEntry 2 }
pingProbeHistoryStatus OBJECT-TYPE
SYNTAX OperationResponseStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The result of a particular probe done by a remote host."
::= { pingProbeHistoryEntry 3 }
pingProbeHistoryStatus OBJECT-TYPE
SYNTAX OperationResponseStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The result of a particular probe done by a remote host."
::= { pingProbeHistoryEntry 3 }
pingProbeHistoryLastRC OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last implementation method specific reply code received.
If the ICMP Echo capability is being used then a successful
probe ends when an ICMP response is received that contains
the code ICMP_ECHOREPLY(0). The ICMP responses are defined
normally in the ip_icmp include file."
::= { pingProbeHistoryEntry 4 }
pingProbeHistoryLastRC OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last implementation method specific reply code received.
If the ICMP Echo capability is being used then a successful
probe ends when an ICMP response is received that contains
the code ICMP_ECHOREPLY(0). The ICMP responses are defined
normally in the ip_icmp include file."
::= { pingProbeHistoryEntry 4 }
pingProbeHistoryTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current
pingProbeHistoryTime对象类型语法日期和时间最大访问只读状态当前
DESCRIPTION
"Timestamp for when this probe result was determined."
::= { pingProbeHistoryEntry 5 }
DESCRIPTION
"Timestamp for when this probe result was determined."
::= { pingProbeHistoryEntry 5 }
-- Notification Definition section
--通知定义部分
pingProbeFailed NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated when a probe failure is detected when the
corresponding pingCtlTrapGeneration object is set to
probeFailure(0) subject to the value of
pingCtlTrapProbeFailureFilter. The object
pingCtlTrapProbeFailureFilter can be used to specify the
number of successive probe failures that are required
before this notification can be generated."
::= { pingNotifications 1 }
pingProbeFailed NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated when a probe failure is detected when the
corresponding pingCtlTrapGeneration object is set to
probeFailure(0) subject to the value of
pingCtlTrapProbeFailureFilter. The object
pingCtlTrapProbeFailureFilter can be used to specify the
number of successive probe failures that are required
before this notification can be generated."
::= { pingNotifications 1 }
pingTestFailed NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
pingTestFailed NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated when a ping test is determined to have failed
when the corresponding pingCtlTrapGeneration object is
set to testFailure(1). In this instance
pingCtlTrapTestFailureFilter should specify the number of
probes in a test required to have failed in order to
consider the test as failed."
::= { pingNotifications 2 }
STATUS current
DESCRIPTION
"Generated when a ping test is determined to have failed
when the corresponding pingCtlTrapGeneration object is
set to testFailure(1). In this instance
pingCtlTrapTestFailureFilter should specify the number of
probes in a test required to have failed in order to
consider the test as failed."
::= { pingNotifications 2 }
pingTestCompleted NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated at the completion of a ping test when the
corresponding pingCtlTrapGeneration object is set to
testCompletion(4)."
::= { pingNotifications 3 }
pingTestCompleted NOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated at the completion of a ping test when the
corresponding pingCtlTrapGeneration object is set to
testCompletion(4)."
::= { pingNotifications 3 }
-- Conformance information
-- Compliance statements
-- Conformance information
-- Compliance statements
pingCompliances OBJECT IDENTIFIER ::= { pingConformance 1 }
pingGroups OBJECT IDENTIFIER ::= { pingConformance 2 }
pingCompliances OBJECT IDENTIFIER ::= { pingConformance 1 }
pingGroups OBJECT IDENTIFIER ::= { pingConformance 2 }
-- Compliance statements
--合规声明
pingCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the DISMAN-PING-MIB." MODULE -- this module MANDATORY-GROUPS { pingGroup, pingNotificationsGroup
pingCompliance MODULE-COMPLIANCE STATUS当前描述“Deman-PING-MIB的符合性声明”。模块——此模块为必填的-GROUPS{pingGroup，pingNotificationsGroup
} GROUP pingTimeStampGroup DESCRIPTION "This group is mandatory for implementations that have access to a system clock and are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this group is not supported that the values for the objects in this group be reported as '0000000000000000'H."
}GROUP pingTimeStampGroup DESCRIPTION“对于可以访问系统时钟并能够设置DateAndTime对象值的实现，此组是必需的。建议在不支持此组时，将此组中对象的值报告为“000000000000”H。”
OBJECT pingMaxConcurrentRequests MIN-ACCESS read-only DESCRIPTION "The agent is not required to support set operations to this object."
对象pingMaxConcurrentRequests最小访问只读说明“不需要代理来支持对此对象的设置操作。”
OBJECT pingCtlStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required. It is also allowed for implementations to support only the volatile StorageType enumeration."
对象pingCtlStorageType MIN-ACCESS只读说明“不需要写访问权限。对于仅支持volatile StorageType枚举的实现，也允许写访问权限。”
OBJECT pingCtlType MIN-ACCESS read-only DESCRIPTION "Write access is not required. In addition, the only value that MUST be supported by an implementation is pingIcmpEcho."
对象pingCtlType MIN-ACCESS只读说明“不需要写访问权限。此外，实现必须支持的唯一值是pingIcmpEcho。”
OBJECT pingCtlByPassRouteTable MIN-ACCESS read-only DESCRIPTION "This object is not required by implementations that are not capable of its implementation. The function represented by this object is implementable if the setsockopt SOL_SOCKET SO_DONTROUTE option is supported."
OBJECT pingCtlByPassRouteTable MIN-ACCESS只读说明“无法实现此对象的实现不需要此对象。如果支持setsockopt SOL_SOCKET SO_DONTROUTE选项，则可实现此对象表示的函数。”
OBJECT pingCtlSourceAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "This object is not required by implementations that are not capable of binding the send socket with a source address. An implementation is only required to support IPv4 and IPv6 addresses."
对象pingCtlSourceAddressType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}MIN-ACCESS只读说明“无法将发送套接字与源地址绑定的实现不需要此对象。只需要支持ipv4和ipv6地址的实现。”
OBJECT pingCtlSourceAddress SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "This object is not required by implementations that are not capable of binding the send socket with a source address. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象pingCtlSourceAddress语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“无法将发送套接字与源地址绑定的实现不需要此对象。仅支持IPv4和全局唯一IPv6地址的实现才需要此实现。”
OBJECT pingCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. When write access is not supported return a 0 as the value of this object. A value of 0 means that the function represented by this option is not supported."
OBJECT PingCtliIndex MIN-ACCESS只读说明“不需要写访问。不支持写访问时，返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT pingCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. When write access is not supported return a 0 as the value of this object. A value of 0 means that the function represented by this option is not supported."
对象PingCtldField MIN-ACCESS只读说明“不需要写访问。当不支持写访问时，返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT pingResultsIpTargetAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support IPv4 and IPv6 addresses."
对象PingResultSiptTargetAddressType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“仅支持ipv4和ipv6地址才需要实现。”
OBJECT pingResultsIpTargetAddress SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象PingResultSiptTargetAddress语法InetAddress（大小（0 | 4 | 16））说明“仅支持IPv4和全局唯一IPv6地址才需要实现。”
::= { pingCompliances 1 }
::= { pingCompliances 1 }
-- MIB groupings
--MIB分组
pingGroup OBJECT-GROUP OBJECTS { pingMaxConcurrentRequests, pingCtlTargetAddressType, pingCtlTargetAddress, pingCtlDataSize, pingCtlTimeOut,
pingGroup对象组对象{pingMaxConcurrentRequests，pingCtlTargetAddressType，pingCtlTargetAddress，pingCtlDataSize，pingCtlTimeOut，
pingCtlProbeCount,
pingCtlAdminStatus,
pingCtlDataFill,
pingCtlFrequency,
pingCtlMaxRows,
pingCtlStorageType,
pingCtlTrapGeneration,
pingCtlTrapProbeFailureFilter,
pingCtlTrapTestFailureFilter,
pingCtlType,
pingCtlDescr,
pingCtlByPassRouteTable,
pingCtlSourceAddressType,
pingCtlSourceAddress,
pingCtlIfIndex,
pingCtlDSField,
pingCtlRowStatus,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingProbeHistoryResponse,
pingProbeHistoryStatus,
pingProbeHistoryLastRC
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote ping
capability."
::= { pingGroups 1 }
pingCtlProbeCount,
pingCtlAdminStatus,
pingCtlDataFill,
pingCtlFrequency,
pingCtlMaxRows,
pingCtlStorageType,
pingCtlTrapGeneration,
pingCtlTrapProbeFailureFilter,
pingCtlTrapTestFailureFilter,
pingCtlType,
pingCtlDescr,
pingCtlByPassRouteTable,
pingCtlSourceAddressType,
pingCtlSourceAddress,
pingCtlIfIndex,
pingCtlDSField,
pingCtlRowStatus,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingProbeHistoryResponse,
pingProbeHistoryStatus,
pingProbeHistoryLastRC
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote ping
capability."
::= { pingGroups 1 }
pingTimeStampGroup OBJECT-GROUP
OBJECTS {
pingResultsLastGoodProbe,
pingProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of DateAndTime objects."
::= { pingGroups 2 }
pingTimeStampGroup OBJECT-GROUP
OBJECTS {
pingResultsLastGoodProbe,
pingProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of DateAndTime objects."
::= { pingGroups 2 }
pingNotificationsGroup NOTIFICATION-GROUP NOTIFICATIONS {
pingNotificationsGroup通知—组通知{
pingProbeFailed,
pingTestFailed,
pingTestCompleted
}
STATUS current
DESCRIPTION
"The notification which are required to be supported by
implementations of this MIB."
::= { pingGroups 3 }
pingProbeFailed,
pingTestFailed,
pingTestCompleted
}
STATUS current
DESCRIPTION
"The notification which are required to be supported by
implementations of this MIB."
::= { pingGroups 3 }
END
终止
DISMAN-TRACEROUTE-MIB DEFINITIONS ::= BEGIN
DISMAN-TRACEROUTE-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32, Unsigned32, mib-2, NOTIFICATION-TYPE, OBJECT-IDENTITY FROM SNMPv2-SMI -- RFC2578 RowStatus, StorageType, TruthValue, DateAndTime FROM SNMPv2-TC -- RFC2579 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC2571 InterfaceIndexOrZero -- RFC2863 FROM IF-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC2851 OperationResponseStatus FROM DISMAN-PING-MIB; -- RFC2925
从SNMPv2 SMI--RFC2578 RowStatus、StorageType、TruthValue、DateAndTime和SNMPv2 TC--RFC2579 MODULE-COMPLIANCE、OBJECT-GROUP、，SNMPv2 CONF中的通知组--SNMP-FRAMEWORK-MIB中的RFC2580 SNMPAdministring--RFC2571接口索引零--IF-MIB中的RFC2863 InetAddressType，INET-ADDRESS-MIB中的InetAddress--DISMAN-PING-MIB中的RFC2851 OperationResponseStatus；--RFC2925
traceRouteMIB MODULE-IDENTITY LAST-UPDATED "200009210000Z" -- 21 September 2000
TRACEROTEMIB模块标识最后一次更新“200009210000Z”-2000年9月21日
ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Kenneth White
组织“IETF分布式管理工作组”联系人信息“Kenneth White”
International Business Machines Corporation Network Computing Software Division Research Triangle Park, NC, USA
国际商用机器公司网络计算软件部美国北卡罗来纳州三角研究园
E-mail: wkenneth@us.ibm.com" DESCRIPTION "The Traceroute MIB (DISMAN-TRACEROUTE-MIB) provides access to the traceroute capability at a remote host."
电邮：wkenneth@us.ibm.com“说明”跟踪路由MIB（DISAN-Traceroute-MIB）提供对远程主机上跟踪路由功能的访问
-- Revision history
--修订历史
REVISION "200009210000Z" -- 21 September 2000 DESCRIPTION "Initial version, published as RFC 2925."
修订版“2000092100Z”-2000年9月21日描述“初始版本，发布为RFC 2925。”
::= { mib-2 81 }
::= { mib-2 81 }
-- Top level structure of the MIB
--MIB的顶层结构
traceRouteNotifications OBJECT IDENTIFIER ::= { traceRouteMIB 0 }
traceRouteObjects OBJECT IDENTIFIER ::= { traceRouteMIB 1 }
traceRouteConformance OBJECT IDENTIFIER ::= { traceRouteMIB 2 }
traceRouteNotifications OBJECT IDENTIFIER ::= { traceRouteMIB 0 }
traceRouteObjects OBJECT IDENTIFIER ::= { traceRouteMIB 1 }
traceRouteConformance OBJECT IDENTIFIER ::= { traceRouteMIB 2 }
-- The registration node (point) for traceroute implementation types
--跟踪路由实现类型的注册节点（点）
traceRouteImplementationTypeDomains OBJECT IDENTIFIER
::= { traceRouteMIB 3 }
traceRouteImplementationTypeDomains OBJECT IDENTIFIER
::= { traceRouteMIB 3 }
traceRouteUsingUdpProbes OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using UDP probes to
perform the traceroute operation."
::= { traceRouteImplementationTypeDomains 1 }
traceRouteUsingUdpProbes OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using UDP probes to
perform the traceroute operation."
::= { traceRouteImplementationTypeDomains 1 }
-- Simple Object Definitions
--简单对象定义
traceRouteMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active traceroute requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { traceRouteObjects 1 }
traceRouteMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active traceroute requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { traceRouteObjects 1 }
-- Traceroute Control Table
--跟踪路由控制表
traceRouteCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF TraceRouteCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Remote Operations Traceroute Control Table for
providing the capability of invoking traceroute from a remote
host. The results of traceroute operations can be stored in
the traceRouteResultsTable, traceRouteProbeHistoryTable, and
the traceRouteHopsTable."
::= { traceRouteObjects 2 }
traceRouteCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF TraceRouteCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Remote Operations Traceroute Control Table for
providing the capability of invoking traceroute from a remote
host. The results of traceroute operations can be stored in
the traceRouteResultsTable, traceRouteProbeHistoryTable, and
the traceRouteHopsTable."
::= { traceRouteObjects 2 }
traceRouteCtlEntry OBJECT-TYPE
SYNTAX TraceRouteCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the traceRouteCtlTable. The first
index element, traceRouteCtlOwnerIndex, is of type
SnmpAdminString, a textual convention that allows for
use of the SNMPv3 View-Based Access Control Model
(RFC 2575 [11], VACM) and allows an management
application to identify its entries. The second index,
traceRouteCtlTestName (also an SnmpAdminString),
enables the same management application to have
multiple requests outstanding."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName
}
::= { traceRouteCtlTable 1 }
traceRouteCtlEntry OBJECT-TYPE
SYNTAX TraceRouteCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the traceRouteCtlTable. The first
index element, traceRouteCtlOwnerIndex, is of type
SnmpAdminString, a textual convention that allows for
use of the SNMPv3 View-Based Access Control Model
(RFC 2575 [11], VACM) and allows an management
application to identify its entries. The second index,
traceRouteCtlTestName (also an SnmpAdminString),
enables the same management application to have
multiple requests outstanding."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName
}
::= { traceRouteCtlTable 1 }
TraceRouteCtlEntry ::=
SEQUENCE {
traceRouteCtlOwnerIndex SnmpAdminString,
traceRouteCtlTestName SnmpAdminString,
traceRouteCtlTargetAddressType InetAddressType,
traceRouteCtlTargetAddress InetAddress,
traceRouteCtlByPassRouteTable TruthValue,
traceRouteCtlDataSize Unsigned32,
traceRouteCtlTimeOut Unsigned32,
traceRouteCtlProbesPerHop Unsigned32,
traceRouteCtlPort Unsigned32,
traceRouteCtlMaxTtl Unsigned32,
traceRouteCtlDSField Unsigned32,
traceRouteCtlSourceAddressType InetAddressType,
TraceRouteCtlEntry ::=
SEQUENCE {
traceRouteCtlOwnerIndex SnmpAdminString,
traceRouteCtlTestName SnmpAdminString,
traceRouteCtlTargetAddressType InetAddressType,
traceRouteCtlTargetAddress InetAddress,
traceRouteCtlByPassRouteTable TruthValue,
traceRouteCtlDataSize Unsigned32,
traceRouteCtlTimeOut Unsigned32,
traceRouteCtlProbesPerHop Unsigned32,
traceRouteCtlPort Unsigned32,
traceRouteCtlMaxTtl Unsigned32,
traceRouteCtlDSField Unsigned32,
traceRouteCtlSourceAddressType InetAddressType,
traceRouteCtlSourceAddress InetAddress, traceRouteCtlIfIndex InterfaceIndexOrZero, traceRouteCtlMiscOptions SnmpAdminString, traceRouteCtlMaxFailures Unsigned32, traceRouteCtlDontFragment TruthValue, traceRouteCtlInitialTtl Unsigned32, traceRouteCtlFrequency Unsigned32, traceRouteCtlStorageType StorageType, traceRouteCtlAdminStatus INTEGER, traceRouteCtlMaxRows Unsigned32, traceRouteCtlTrapGeneration BITS, traceRouteCtlDescr SnmpAdminString, traceRouteCtlCreateHopsEntries TruthValue, traceRouteCtlType OBJECT IDENTIFIER, traceRouteCtlRowStatus RowStatus }
traceRouteCtlSourceAddress InetAddress、TracerOuteCtliIndex InterfaceIndexOrZero、traceRouteCtlMiscOptions SNMPAdminInstalling、traceRouteCtlMaxFailures Unsigned32、traceRouteCtlDontFragment TruthValue、traceRouteCtlInitialTtl Unsigned32、traceRouteCtlFrequency Unsigned32、traceRouteCtlStorageType StorageType、TracerOuteClAdminStatus INTEGER、，traceRouteCtlMaxRows Unsigned32、traceroutectltrapggeneration位、traceRouteCtlDescr SnmpAdminString、traceRouteCtlCreateHopsEntries TruthValue、traceRouteCtlType对象标识符、traceRouteCtlRowStatus RowStatus}
traceRouteCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy.
traceRouteCtlOwnerIndex对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS not accessible STATUS current DESCRIPTION“帮助安全管理员使用基于视图的访问控制模型（RFC 2575，VACM）设置访问控制对于多个用户可能需要独立创建或修改条目的表，初始索引用作“所有者索引”。此类初始索引具有SNMPAdministring语法，因此可以根据安全策略轻松映射到VACM中定义的securityName或groupName。
When used in conjunction with such a security policy
all entries in the table belonging to a particular user
(or group) will have the same value for this initial
index. For a given user's entries in a particular
table, the object identifiers for the information in
these entries will have the same subidentifiers (except
for the 'column' subidentifier) up to the end of the
encoded owner index. To configure VACM to permit access
to this portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index
portion, and vacmViewTreeFamilyMask 'wildcarding' the
column subidentifier. More elaborate configurations
are possible."
::= { traceRouteCtlEntry 1 }
When used in conjunction with such a security policy
all entries in the table belonging to a particular user
(or group) will have the same value for this initial
index. For a given user's entries in a particular
table, the object identifiers for the information in
these entries will have the same subidentifiers (except
for the 'column' subidentifier) up to the end of the
encoded owner index. To configure VACM to permit access
to this portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index
portion, and vacmViewTreeFamilyMask 'wildcarding' the
column subidentifier. More elaborate configurations
are possible."
::= { traceRouteCtlEntry 1 }
traceRouteCtlTestName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of a traceroute test. This is locally unique,
within the scope of an traceRouteCtlOwnerIndex."
::= { traceRouteCtlEntry 2 }
traceRouteCtlTestName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of a traceroute test. This is locally unique,
within the scope of an traceRouteCtlOwnerIndex."
::= { traceRouteCtlEntry 2 }
traceRouteCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of host address to be used on the
traceroute request at the remote host."
DEFVAL { ipv4 }
::= { traceRouteCtlEntry 3 }
traceRouteCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of host address to be used on the
traceroute request at the remote host."
DEFVAL { ipv4 }
::= { traceRouteCtlEntry 3 }
traceRouteCtlTargetAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the host address used on the traceroute request at the remote host. The host address type can be determined by the examining the value of the corresponding traceRouteCtlTargetAddressType index element.
traceRouteCtlTargetAddress对象类型语法InetAddress MAX-ACCESS读取创建状态当前描述”指定远程主机上跟踪路由请求上使用的主机地址。主机地址类型可以通过检查相应的traceRouteCtlTargetAddressType索引元素的值来确定。
A value for this object MUST be set prior to
transitioning its corresponding traceRouteCtlEntry to
active(1) via traceRouteCtlRowStatus."
::= { traceRouteCtlEntry 4 }
A value for this object MUST be set prior to
transitioning its corresponding traceRouteCtlEntry to
active(1) via traceRouteCtlRowStatus."
::= { traceRouteCtlEntry 4 }
traceRouteCtlByPassRouteTable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "The purpose of this object is to optionally enable bypassing the route table. If enabled, the remote host will bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-attached network, an error is returned. This option can be used to perform the traceroute operation to a local host through an interface that has no route defined (e.g., after the
traceRouteCtlByPassRouteTable对象类型语法TruthValue MAX-ACCESS读取创建状态当前描述“此对象的目的是可选地启用绕过路由表。如果启用，远程主机将绕过正常路由表，直接发送到连接网络上的主机。如果主机不在直接连接的网络上，则返回错误。此选项可用于通过未定义路由的接口（例如，在
interface was dropped by routed)."
DEFVAL { false }
::= { traceRouteCtlEntry 5 }
interface was dropped by routed)."
DEFVAL { false }
::= { traceRouteCtlEntry 5 }
traceRouteCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion of a traceroute
request in octets. A traceroute request is essentially
transmitted by encoding a UDP datagram into a
IP packet. So subtracting the size of a UDP header
(8 octets) and the size of a IP header (20 octets)
yields a maximum of 65507 octets."
DEFVAL { 0 }
::= { traceRouteCtlEntry 6 }
traceRouteCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion of a traceroute
request in octets. A traceroute request is essentially
transmitted by encoding a UDP datagram into a
IP packet. So subtracting the size of a UDP header
(8 octets) and the size of a IP header (20 octets)
yields a maximum of 65507 octets."
DEFVAL { 0 }
::= { traceRouteCtlEntry 6 }
traceRouteCtlTimeOut OBJECT-TYPE
SYNTAX Unsigned32 (1..60)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time-out value, in seconds, for
a traceroute request."
DEFVAL { 3 }
::= { traceRouteCtlEntry 7 }
traceRouteCtlTimeOut OBJECT-TYPE
SYNTAX Unsigned32 (1..60)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time-out value, in seconds, for
a traceroute request."
DEFVAL { 3 }
::= { traceRouteCtlEntry 7 }
traceRouteCtlProbesPerHop OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
UNITS "probes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of times to reissue a traceroute
request with the same time-to-live (TTL) value."
DEFVAL { 3 }
::= { traceRouteCtlEntry 8 }
traceRouteCtlProbesPerHop OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
UNITS "probes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of times to reissue a traceroute
request with the same time-to-live (TTL) value."
DEFVAL { 3 }
::= { traceRouteCtlEntry 8 }
traceRouteCtlPort OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "UDP Port" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the UDP port to send the traceroute
traceRouteCtlPort对象类型语法Unsigned32（1..65535）单位“UDP端口”MAX-ACCESS read create STATUS current DESCRIPTION“指定要发送跟踪路由的UDP端口
request to. Need to specify a port that is not in
use at the destination (target) host. The default
value for this object is the IANA assigned port,
33434, for the traceroute function."
DEFVAL { 33434 }
::= { traceRouteCtlEntry 9 }
request to. Need to specify a port that is not in
use at the destination (target) host. The default
value for this object is the IANA assigned port,
33434, for the traceroute function."
DEFVAL { 33434 }
::= { traceRouteCtlEntry 9 }
traceRouteCtlMaxTtl OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
UNITS "time-to-live value"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum time-to-live value."
DEFVAL { 30 }
::= { traceRouteCtlEntry 10 }
traceRouteCtlMaxTtl OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
UNITS "time-to-live value"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum time-to-live value."
DEFVAL { 30 }
::= { traceRouteCtlEntry 10 }
traceRouteCtlDSField OBJECT-TYPE SYNTAX Unsigned32 (0..255) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the value to store in the Differentiated Services (DS) Field in the IP packet used to encapsulate the traceroute probe. The DS Field is defined as the Type of Service (TOS) octet in a IPv4 header or as the Traffic Class octet in a IPv6 header.
traceRouteCtlDSField对象类型语法Unsigned32（0..255）MAX-ACCESS read create STATUS current DESCRIPTION“指定要存储在用于封装traceroute探测的IP数据包中的区分服务（DS）字段中的值。DS字段定义为服务类型（TOS）IPv4标头中的八位字节或IPv6标头中的流量类八位字节。
The value of this object must be a decimal integer
in the range from 0 to 255. This option can be used
to determine what effect an explicit DS Field setting
has on a traceroute response. Not all values are legal
or meaningful. DS Field usage is often not supported
by IP implementations. A value of 0 means that the
function represented by this option is not supported.
Useful TOS octet values are probably '16' (low delay)
and '8' ( high throughput)."
REFERENCE
"Refer to RFC 2474 for the definition of the
Differentiated Services Field and to RFC 1812
Section 5.3.2 for Type of Service (TOS)."
DEFVAL { 0 }
::= { traceRouteCtlEntry 11 }
The value of this object must be a decimal integer
in the range from 0 to 255. This option can be used
to determine what effect an explicit DS Field setting
has on a traceroute response. Not all values are legal
or meaningful. DS Field usage is often not supported
by IP implementations. A value of 0 means that the
function represented by this option is not supported.
Useful TOS octet values are probably '16' (low delay)
and '8' ( high throughput)."
REFERENCE
"Refer to RFC 2474 for the definition of the
Differentiated Services Field and to RFC 1812
Section 5.3.2 for Type of Service (TOS)."
DEFVAL { 0 }
::= { traceRouteCtlEntry 11 }
traceRouteCtlSourceAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current
TracerOuteClSourceAddressType对象类型语法InetAddressType MAX-ACCESS读取创建状态当前
DESCRIPTION
"Specifies the type of the source address,
traceRouteCtlSourceAddress, to be used at a remote host
when performing a traceroute operation."
DEFVAL { unknown }
::= { traceRouteCtlEntry 12 }
DESCRIPTION
"Specifies the type of the source address,
traceRouteCtlSourceAddress, to be used at a remote host
when performing a traceroute operation."
DEFVAL { unknown }
::= { traceRouteCtlEntry 12 }
traceRouteCtlSourceAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Use the specified IP address (which must be given as an IP number, not a hostname) as the source address in outgoing probe packets. On hosts with more than one IP address, this option can be used to force the source address to be something other than the primary IP address of the interface the probe packet is sent on. If the IP address is not one of this machine's interface addresses, an error is returned and nothing is sent. A zero length octet string value for this object disables source address specification.
TracerOuteClSourceAddress对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“使用指定的IP地址（必须作为IP号码而不是主机名提供）作为传出探测数据包中的源地址。在具有多个IP地址的主机上，此选项可用于强制源地址不是发送探测数据包的接口的主IP地址。如果该IP地址不是此计算机的接口地址之一，则返回错误，且不发送任何内容。A此对象的零长度八位字节字符串值将禁用源地址规范。
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of traceRouteCtlSourceAddressType."
DEFVAL { ''H }
::= { traceRouteCtlEntry 13 }
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of traceRouteCtlSourceAddressType."
DEFVAL { ''H }
::= { traceRouteCtlEntry 13 }
traceRouteCtlIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Setting this object to an interface's ifIndex prior
to starting a remote traceroute operation directs
the traceroute probes to be transmitted over the
specified interface. A value of zero for this object
implies that this option is not enabled."
DEFVAL { 0 }
::= { traceRouteCtlEntry 14 }
traceRouteCtlIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Setting this object to an interface's ifIndex prior
to starting a remote traceroute operation directs
the traceroute probes to be transmitted over the
specified interface. A value of zero for this object
implies that this option is not enabled."
DEFVAL { 0 }
::= { traceRouteCtlEntry 14 }
traceRouteCtlMiscOptions OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION
TRACEROUTCTLMISCHOPTIONS对象类型语法SnmpAdminString MAX-ACCESS read create STATUS当前说明
"Enables an application to specify implementation
dependent options."
DEFVAL { ''H }
::= { traceRouteCtlEntry 15 }
"Enables an application to specify implementation
dependent options."
DEFVAL { ''H }
::= { traceRouteCtlEntry 15 }
traceRouteCtlMaxFailures OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "timeouts"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object indicates the maximum number
of consecutive timeouts allowed before terminating
a remote traceroute request. A value of either 255 (maximum
hop count/possible TTL value) or a 0 indicates that the
function of terminating a remote traceroute request when a
specific number of successive timeouts are detected is
disabled."
DEFVAL { 5 }
::= { traceRouteCtlEntry 16 }
traceRouteCtlMaxFailures OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "timeouts"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object indicates the maximum number
of consecutive timeouts allowed before terminating
a remote traceroute request. A value of either 255 (maximum
hop count/possible TTL value) or a 0 indicates that the
function of terminating a remote traceroute request when a
specific number of successive timeouts are detected is
disabled."
DEFVAL { 5 }
::= { traceRouteCtlEntry 16 }
traceRouteCtlDontFragment OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object enables setting of the don't fragment flag (DF)
in the IP header for a probe. Use of this object enables
performing a manual PATH MTU test."
DEFVAL { false }
::= { traceRouteCtlEntry 17 }
traceRouteCtlDontFragment OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object enables setting of the don't fragment flag (DF)
in the IP header for a probe. Use of this object enables
performing a manual PATH MTU test."
DEFVAL { false }
::= { traceRouteCtlEntry 17 }
traceRouteCtlInitialTtl OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object specifies the initial TTL value to
use. This enables bypassing the initial (often well known)
portion of a path."
DEFVAL { 1 }
::= { traceRouteCtlEntry 18 }
traceRouteCtlInitialTtl OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object specifies the initial TTL value to
use. This enables bypassing the initial (often well known)
portion of a path."
DEFVAL { 1 }
::= { traceRouteCtlEntry 18 }
traceRouteCtlFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current
traceRouteCtlFrequency对象类型语法无符号32单位“秒”最大访问读取创建状态当前
DESCRIPTION "The number of seconds to wait before repeating a traceroute test as defined by the value of the various objects in the corresponding row.
DESCRIPTION“重复跟踪路由测试之前等待的秒数，由相应行中各种对象的值定义。
The number of hops in a single traceroute test is determined by the value of the corresponding traceRouteCtlProbesPerHop object. After a single test completes the number of seconds as defined by the value of traceRouteCtlFrequency MUST elapse before the next traceroute test is started.
单个跟踪路由测试中的跳数由相应的跟踪路由CtlProbeSperHop对象的值确定。单个测试完成后，在开始下一个跟踪路由测试之前，必须经过由traceRouteCtlFrequency值定义的秒数。
A value of 0 for this object implies that the test
as defined by the corresponding entry will not be
repeated."
DEFVAL { 0 }
::= { traceRouteCtlEntry 19 }
A value of 0 for this object implies that the test
as defined by the corresponding entry will not be
repeated."
DEFVAL { 0 }
::= { traceRouteCtlEntry 19 }
traceRouteCtlStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { traceRouteCtlEntry 20 }
traceRouteCtlStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { traceRouteCtlEntry 20 }
traceRouteCtlAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- operation should be started
disabled(2) -- operation should be stopped
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Reflects the desired state that an traceRouteCtlEntry
should be in:
traceRouteCtlAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- operation should be started
disabled(2) -- operation should be stopped
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Reflects the desired state that an traceRouteCtlEntry
should be in:
enabled(1) - Attempt to activate the test as defined by this traceRouteCtlEntry. disabled(2) - Deactivate the test as defined by this traceRouteCtlEntry.
已启用（1）-尝试激活此项定义的测试。已禁用（2）-根据此条目的定义停用测试。
Refer to the corresponding traceRouteResultsOperStatus to determine the operational state of the test defined by this entry."
请参阅相应的TraceRouteResultsOperatStatus，以确定此条目定义的测试的运行状态。”
DEFVAL { disabled }
::= { traceRouteCtlEntry 21 }
DEFVAL { disabled }
::= { traceRouteCtlEntry 21 }
traceRouteCtlDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The purpose of this object is to provide a
descriptive name of the remote traceroute
test."
DEFVAL { '00'H }
::= { traceRouteCtlEntry 22 }
traceRouteCtlDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The purpose of this object is to provide a
descriptive name of the remote traceroute
test."
DEFVAL { '00'H }
::= { traceRouteCtlEntry 22 }
traceRouteCtlMaxRows OBJECT-TYPE SYNTAX Unsigned32 UNITS "rows" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of entries allowed in the traceRouteProbeHistoryTable. An implementation of this MIB will remove the oldest entry in the traceRouteProbeHistoryTable to allow the addition of an new entry once the number of rows in the traceRouteProbeHistoryTable reaches this value.
traceRouteCtlMaxRows对象类型语法无符号32个单位“行”最大访问读取创建状态当前描述“traceRouteProbeHistoryTable中允许的最大条目数。此MIB的实现将删除traceRouteProbeHistoryTable中最旧的条目，以允许在traceRouteProbeHistoryTable中的行数达到此值时添加新条目。
Old entries are not removed when a new test is started. Entries are added to the traceRouteProbeHistoryTable until traceRouteCtlMaxRows is reached before entries begin to be removed.
启动新测试时，不会删除旧条目。条目将添加到traceRouteProbeHistoryTable，直到到达traceRouteCtlMaxRows，然后才开始删除条目。
A value of 0 for this object disables creation of
traceRouteProbeHistoryTable entries."
DEFVAL { 50 }
::= { traceRouteCtlEntry 23 }
A value of 0 for this object disables creation of
traceRouteProbeHistoryTable entries."
DEFVAL { 50 }
::= { traceRouteCtlEntry 23 }
traceRouteCtlTrapGeneration OBJECT-TYPE
SYNTAX BITS {
pathChange(0),
testFailure(1),
testCompletion(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object determines when and if to
to generate a notification for this entry:
traceRouteCtlTrapGeneration OBJECT-TYPE
SYNTAX BITS {
pathChange(0),
testFailure(1),
testCompletion(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object determines when and if to
to generate a notification for this entry:
pathChange(0) - Generate a traceRoutePathChange notification when the current path varies from a previously determined path. testFailure(1) - Generate a traceRouteTestFailed notification when the full path to a target can't be determined. testCompletion(2) - Generate a traceRouteTestCompleted notification when the path to a target has been determined.
pathChange（0）-当当前路径与以前确定的路径不同时，生成TracerOutPathChange通知。testFailure（1）-当无法确定目标的完整路径时，生成TracerOutTestFailed通知。testCompletion（2）-确定目标路径后，生成跟踪路由TestCompleted通知。
The value of this object defaults to zero, indicating
that none of the above options have been selected."
::= { traceRouteCtlEntry 24 }
The value of this object defaults to zero, indicating
that none of the above options have been selected."
::= { traceRouteCtlEntry 24 }
traceRouteCtlCreateHopsEntries OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The current path for a traceroute test is kept in the
traceRouteHopsTable on a per hop basis when the value of
this object is true(1)."
DEFVAL { false }
::= { traceRouteCtlEntry 25 }
traceRouteCtlCreateHopsEntries OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The current path for a traceroute test is kept in the
traceRouteHopsTable on a per hop basis when the value of
this object is true(1)."
DEFVAL { false }
::= { traceRouteCtlEntry 25 }
traceRouteCtlType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used either to report or select the implementation method to be used for performing a traceroute operation. The value of this object may be selected from traceRouteImplementationTypeDomains.
traceRouteCtlType对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“此对象的值用于报告或选择用于执行跟踪路由操作的实现方法。此对象的值可以从traceRouteImplementationTypeDomains中选择。
Additional implementation types should be allocated as
required by implementers of the DISMAN-TRACEROUTE-MIB
under their enterprise specific registration point and
not beneath traceRouteImplementationTypeDomains."
DEFVAL { traceRouteUsingUdpProbes }
::= { traceRouteCtlEntry 26 }
Additional implementation types should be allocated as
required by implementers of the DISMAN-TRACEROUTE-MIB
under their enterprise specific registration point and
not beneath traceRouteImplementationTypeDomains."
DEFVAL { traceRouteUsingUdpProbes }
::= { traceRouteCtlEntry 26 }
traceRouteCtlRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION
TracerOuteClRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述
"This object allows entries to be created and deleted in the traceRouteCtlTable. Deletion of an entry in this table results in all corresponding (same traceRouteCtlOwnerIndex and traceRouteCtlTestName index values) traceRouteResultsTable, traceRouteProbeHistoryTable, and traceRouteHopsTable entries being deleted.
此对象允许在traceRouteCtlTable中创建和删除条目。删除此表中的条目会导致删除所有相应的（相同的traceRouteCtlOwnerIndex和traceRouteCtlTestName索引值）、TracerOutResultsTable、TracerOutProbeHistoryTable和TracerOutShopStable条目。
A value MUST be specified for traceRouteCtlTargetAddress prior to a transition to active(1) state being accepted.
在接受转换到活动（1）状态之前，必须为TracerOuteCtTargetAddress指定一个值。
Activation of a remote traceroute operation is controlled via traceRouteCtlAdminStatus and not by transitioning of this object's value to active(1).
远程跟踪路由操作的激活是通过跟踪路由CTLAMINSTATUS控制的，而不是通过将此对象的值转换为active（1）来控制的。
Transitions in and out of active(1) state are not allowed while an entry's traceRouteResultsOperStatus is active(1) with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active traceroute operation.
当条目的跟踪路由ResultsOperatStatus处于活动状态（1）时，不允许进入和退出活动（1）状态，除非通过将其RowStatus对象设置为destroy（6）删除此表中的条目将停止活动跟踪路由操作。
The operational state of an traceroute operation
can be determined by examination of the corresponding
traceRouteResultsOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579, 'Textual
Conventions for SMIv2.'"
::= { traceRouteCtlEntry 27 }
The operational state of an traceroute operation
can be determined by examination of the corresponding
traceRouteResultsOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579, 'Textual
Conventions for SMIv2.'"
::= { traceRouteCtlEntry 27 }
-- Traceroute Results Table
--跟踪路由结果表
traceRouteResultsTable OBJECT-TYPE SYNTAX SEQUENCE OF TraceRouteResultsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the Remote Operations Traceroute Results Table for keeping track of the status of a traceRouteCtlEntry.
TracerOutResultsTable对象类型TracerOutResultsEntry MAX-ACCESS的语法序列不可访问状态当前描述”定义远程操作Traceroute结果表，用于跟踪traceRouteCtlEntry的状态。
An entry is added to the traceRouteResultsTable when an
traceRouteCtlEntry is started by successful transition
of its traceRouteCtlAdminStatus object to enabled(1).
An entry is removed from the traceRouteResultsTable when
its corresponding traceRouteCtlEntry is deleted."
::= { traceRouteObjects 3 }
An entry is added to the traceRouteResultsTable when an
traceRouteCtlEntry is started by successful transition
of its traceRouteCtlAdminStatus object to enabled(1).
An entry is removed from the traceRouteResultsTable when
its corresponding traceRouteCtlEntry is deleted."
::= { traceRouteObjects 3 }
traceRouteResultsEntry OBJECT-TYPE
SYNTAX TraceRouteResultsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the traceRouteResultsTable. The
traceRouteResultsTable has the same indexing as the
traceRouteCtlTable in order for a traceRouteResultsEntry
to correspond to the traceRouteCtlEntry that caused it to
be created."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName
}
::= { traceRouteResultsTable 1 }
traceRouteResultsEntry OBJECT-TYPE
SYNTAX TraceRouteResultsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the traceRouteResultsTable. The
traceRouteResultsTable has the same indexing as the
traceRouteCtlTable in order for a traceRouteResultsEntry
to correspond to the traceRouteCtlEntry that caused it to
be created."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName
}
::= { traceRouteResultsTable 1 }
TraceRouteResultsEntry ::=
SEQUENCE {
traceRouteResultsOperStatus INTEGER,
traceRouteResultsCurHopCount Gauge32,
traceRouteResultsCurProbeCount Gauge32,
traceRouteResultsIpTgtAddrType InetAddressType,
traceRouteResultsIpTgtAddr InetAddress,
traceRouteResultsTestAttempts Unsigned32,
traceRouteResultsTestSuccesses Unsigned32,
traceRouteResultsLastGoodPath DateAndTime
}
TraceRouteResultsEntry ::=
SEQUENCE {
traceRouteResultsOperStatus INTEGER,
traceRouteResultsCurHopCount Gauge32,
traceRouteResultsCurProbeCount Gauge32,
traceRouteResultsIpTgtAddrType InetAddressType,
traceRouteResultsIpTgtAddr InetAddress,
traceRouteResultsTestAttempts Unsigned32,
traceRouteResultsTestSuccesses Unsigned32,
traceRouteResultsLastGoodPath DateAndTime
}
traceRouteResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2) -- test has stopped
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an traceRouteCtlEntry:
traceRouteResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2) -- test has stopped
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an traceRouteCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped."
::= { traceRouteResultsEntry 1 }
enabled(1) - Test is active.
disabled(2) - Test has stopped."
::= { traceRouteResultsEntry 1 }
traceRouteResultsCurHopCount OBJECT-TYPE SYNTAX Gauge32 UNITS "hops" MAX-ACCESS read-only STATUS current DESCRIPTION
TracerOutResultsCurhopCount对象类型语法量表32单位“跃点”最大访问只读状态当前说明
"Reflects the current TTL value (range from 1 to
255) for a remote traceroute operation.
Maximum TTL value is determined by
traceRouteCtlMaxTtl."
::= { traceRouteResultsEntry 2 }
"Reflects the current TTL value (range from 1 to
255) for a remote traceroute operation.
Maximum TTL value is determined by
traceRouteCtlMaxTtl."
::= { traceRouteResultsEntry 2 }
traceRouteResultsCurProbeCount OBJECT-TYPE
SYNTAX Gauge32
UNITS "probes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the current probe count (1..10) for
a remote traceroute operation. The maximum
probe count is determined by
traceRouteCtlProbesPerHop."
::= { traceRouteResultsEntry 3 }
traceRouteResultsCurProbeCount OBJECT-TYPE
SYNTAX Gauge32
UNITS "probes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the current probe count (1..10) for
a remote traceroute operation. The maximum
probe count is determined by
traceRouteCtlProbesPerHop."
::= { traceRouteResultsEntry 3 }
traceRouteResultsIpTgtAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteResultsIpTgtAddr
object."
::= { traceRouteResultsEntry 4 }
traceRouteResultsIpTgtAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteResultsIpTgtAddr
object."
::= { traceRouteResultsEntry 4 }
traceRouteResultsIpTgtAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects reports the IP address associated
with a traceRouteCtlTargetAddress value when the
destination address is specified as a DNS name.
The value of this object should be a zero length
octet string when a DNS name is not specified or
when a specified DNS name fails to resolve."
::= { traceRouteResultsEntry 5 }
traceRouteResultsIpTgtAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects reports the IP address associated
with a traceRouteCtlTargetAddress value when the
destination address is specified as a DNS name.
The value of this object should be a zero length
octet string when a DNS name is not specified or
when a specified DNS name fails to resolve."
::= { traceRouteResultsEntry 5 }
traceRouteResultsTestAttempts OBJECT-TYPE SYNTAX Unsigned32 UNITS "tests" MAX-ACCESS read-only STATUS current DESCRIPTION "The current number of attempts to determine a path
TracerOutResultsTestAttempts对象类型语法无符号32个单元“测试”最大访问只读状态当前描述“确定路径的当前尝试次数”
to a target. The value of this object MUST be started
at 0."
::= { traceRouteResultsEntry 6 }
to a target. The value of this object MUST be started
at 0."
::= { traceRouteResultsEntry 6 }
traceRouteResultsTestSuccesses OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of attempts to determine a path
to a target that have succeeded. The value of this
object MUST be reported as 0 when no attempts have
succeeded."
::= { traceRouteResultsEntry 7 }
traceRouteResultsTestSuccesses OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of attempts to determine a path
to a target that have succeeded. The value of this
object MUST be reported as 0 when no attempts have
succeeded."
::= { traceRouteResultsEntry 7 }
traceRouteResultsLastGoodPath OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time when the last complete path
was determined."
::= { traceRouteResultsEntry 8 }
traceRouteResultsLastGoodPath OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time when the last complete path
was determined."
::= { traceRouteResultsEntry 8 }
-- Trace Route Probe History Table
--跟踪路由探测历史记录表
traceRouteProbeHistoryTable OBJECT-TYPE SYNTAX SEQUENCE OF TraceRouteProbeHistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the Remote Operations Traceroute Results Table for storing the results of a traceroute operation.
traceRouteProbeHistoryTable对象类型TraceRouteProbeHistoryEntry MAX-ACCESS的语法序列不可访问状态当前描述”定义远程操作Traceroute结果表，用于存储跟踪路由操作的结果。
An implementation of this MIB will remove the oldest
entry in the traceRouteProbeHistoryTable to allow the
addition of an new entry once the number of rows in
the traceRouteProbeHistoryTable reaches the value specified
by traceRouteCtlMaxRows."
::= { traceRouteObjects 4 }
An implementation of this MIB will remove the oldest
entry in the traceRouteProbeHistoryTable to allow the
addition of an new entry once the number of rows in
the traceRouteProbeHistoryTable reaches the value specified
by traceRouteCtlMaxRows."
::= { traceRouteObjects 4 }
traceRouteProbeHistoryEntry OBJECT-TYPE SYNTAX TraceRouteProbeHistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines a table for storing the results of a traceroute
traceRouteProbeHistoryEntry对象类型语法traceRouteProbeHistoryEntry MAX-ACCESS不可访问状态当前描述”定义用于存储跟踪路由结果的表
operation. Entries in this table are limited by the value of the corresponding traceRouteCtlMaxRows object.
活动此表中的条目受相应traceRouteCtlMaxRows对象的值限制。
The first two index elements identify the
traceRouteCtlEntry that a traceRouteProbeHistoryEntry
belongs to. The third index element selects a single
traceroute operation result. The fourth and fifth indexes
select the hop and the probe for a particular
traceroute operation."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName,
traceRouteProbeHistoryIndex,
traceRouteProbeHistoryHopIndex,
traceRouteProbeHistoryProbeIndex
}
::= { traceRouteProbeHistoryTable 1 }
The first two index elements identify the
traceRouteCtlEntry that a traceRouteProbeHistoryEntry
belongs to. The third index element selects a single
traceroute operation result. The fourth and fifth indexes
select the hop and the probe for a particular
traceroute operation."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName,
traceRouteProbeHistoryIndex,
traceRouteProbeHistoryHopIndex,
traceRouteProbeHistoryProbeIndex
}
::= { traceRouteProbeHistoryTable 1 }
TraceRouteProbeHistoryEntry ::=
SEQUENCE {
traceRouteProbeHistoryIndex Unsigned32,
traceRouteProbeHistoryHopIndex Unsigned32,
traceRouteProbeHistoryProbeIndex Unsigned32,
traceRouteProbeHistoryHAddrType InetAddressType,
traceRouteProbeHistoryHAddr InetAddress,
traceRouteProbeHistoryResponse Unsigned32,
traceRouteProbeHistoryStatus OperationResponseStatus,
traceRouteProbeHistoryLastRC Integer32,
traceRouteProbeHistoryTime DateAndTime
}
TraceRouteProbeHistoryEntry ::=
SEQUENCE {
traceRouteProbeHistoryIndex Unsigned32,
traceRouteProbeHistoryHopIndex Unsigned32,
traceRouteProbeHistoryProbeIndex Unsigned32,
traceRouteProbeHistoryHAddrType InetAddressType,
traceRouteProbeHistoryHAddr InetAddress,
traceRouteProbeHistoryResponse Unsigned32,
traceRouteProbeHistoryStatus OperationResponseStatus,
traceRouteProbeHistoryLastRC Integer32,
traceRouteProbeHistoryTime DateAndTime
}
traceRouteProbeHistoryIndex OBJECT-TYPE SYNTAX Unsigned32 (1..'ffffffff'h) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created when the result of a traceroute probe is determined. The initial 2 instance identifier index values identify the traceRouteCtlEntry that a probe result (traceRouteProbeHistoryEntry) belongs to. An entry is removed from this table when its corresponding traceRouteCtlEntry is deleted.
traceRouteProbeHistoryIndex对象类型语法Unsigned32（1..'ffffffff'h）MAX-ACCESS不可访问状态当前描述“当确定跟踪路由探测的结果时，将创建此表中的一个条目。初始的2个实例标识符索引值标识探测结果所对应的跟踪路由Ctlentry（traceRouteProbeHistoryEntry）属于。删除相应的跟踪项时，将从此表中删除该项。
An implementation MUST start assigning traceRouteProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h)."
实现必须开始将traceRouteProbeHistoryIndex值指定为1，并在超过此对象的限制（'FFFFFFFFFF'h'定义的最大可能值后进行换行。”
::= { traceRouteProbeHistoryEntry 1 }
::= { traceRouteProbeHistoryEntry 1 }
traceRouteProbeHistoryHopIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates which hop in a traceroute path that the probe's
results are for. The value of this object is initially
determined by the value of traceRouteCtlInitialTtl."
::= { traceRouteProbeHistoryEntry 2 }
traceRouteProbeHistoryHopIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates which hop in a traceroute path that the probe's
results are for. The value of this object is initially
determined by the value of traceRouteCtlInitialTtl."
::= { traceRouteProbeHistoryEntry 2 }
traceRouteProbeHistoryProbeIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the index of a probe for a particular
hop in a traceroute path. The number of probes per
hop is determined by the value of the corresponding
traceRouteCtlProbesPerHop object."
::= { traceRouteProbeHistoryEntry 3 }
traceRouteProbeHistoryProbeIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the index of a probe for a particular
hop in a traceroute path. The number of probes per
hop is determined by the value of the corresponding
traceRouteCtlProbesPerHop object."
::= { traceRouteProbeHistoryEntry 3 }
traceRouteProbeHistoryHAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteProbeHistoryHAddr
object."
::= { traceRouteProbeHistoryEntry 4 }
traceRouteProbeHistoryHAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteProbeHistoryHAddr
object."
::= { traceRouteProbeHistoryEntry 4 }
traceRouteProbeHistoryHAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of a hop in a traceroute path. This object
is not allowed to be a DNS name. The value of the
corresponding object, traceRouteProbeHistoryHAddrType,
indicates this object's IP address type."
::= { traceRouteProbeHistoryEntry 5 }
traceRouteProbeHistoryHAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of a hop in a traceroute path. This object
is not allowed to be a DNS name. The value of the
corresponding object, traceRouteProbeHistoryHAddrType,
indicates this object's IP address type."
::= { traceRouteProbeHistoryEntry 5 }
traceRouteProbeHistoryResponse OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only
traceRouteProbeHistoryResponse对象类型语法无符号32单位“毫秒”最大访问只读
STATUS current
DESCRIPTION
"The amount of time measured in milliseconds from when
a probe was sent to when its response was received or
when it timed out. The value of this object is reported
as 0 when it is not possible to transmit a probe."
::= { traceRouteProbeHistoryEntry 6 }
STATUS current
DESCRIPTION
"The amount of time measured in milliseconds from when
a probe was sent to when its response was received or
when it timed out. The value of this object is reported
as 0 when it is not possible to transmit a probe."
::= { traceRouteProbeHistoryEntry 6 }
traceRouteProbeHistoryStatus OBJECT-TYPE
SYNTAX OperationResponseStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The result of a traceroute operation made by a remote
host for a particular probe."
::= { traceRouteProbeHistoryEntry 7 }
traceRouteProbeHistoryStatus OBJECT-TYPE
SYNTAX OperationResponseStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The result of a traceroute operation made by a remote
host for a particular probe."
::= { traceRouteProbeHistoryEntry 7 }
traceRouteProbeHistoryLastRC OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The last implementation method specific reply code received.
traceRouteProbeHistoryLastRC对象类型语法整数32 MAX-ACCESS只读状态当前描述“收到的最后一个实现方法特定的回复代码。
Traceroute is usually implemented by transmitting a series of
probe packets with increasing time-to-live values. A probe
packet is a UDP datagram encapsulated into an IP packet.
Each hop in a path to the target (destination) host rejects
the probe packets (probe's TTL too small, ICMP reply) until
either the maximum TTL is exceeded or the target host is
received."
::= { traceRouteProbeHistoryEntry 8 }
Traceroute is usually implemented by transmitting a series of
probe packets with increasing time-to-live values. A probe
packet is a UDP datagram encapsulated into an IP packet.
Each hop in a path to the target (destination) host rejects
the probe packets (probe's TTL too small, ICMP reply) until
either the maximum TTL is exceeded or the target host is
received."
::= { traceRouteProbeHistoryEntry 8 }
traceRouteProbeHistoryTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Timestamp for when this probe results were determined."
::= { traceRouteProbeHistoryEntry 9 }
traceRouteProbeHistoryTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Timestamp for when this probe results were determined."
::= { traceRouteProbeHistoryEntry 9 }
-- Traceroute Hop Results Table
--跟踪路由跃点结果表
traceRouteHopsTable OBJECT-TYPE SYNTAX SEQUENCE OF TraceRouteHopsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
TracerOutHopSentry MAX-ACCESS的TracerOutHopStable对象类型语法序列不可访问状态当前描述
"Defines the Remote Operations Traceroute Hop Table for
keeping track of the results of traceroute tests on a
per hop basis."
::= { traceRouteObjects 5 }
"Defines the Remote Operations Traceroute Hop Table for
keeping track of the results of traceroute tests on a
per hop basis."
::= { traceRouteObjects 5 }
traceRouteHopsEntry OBJECT-TYPE SYNTAX TraceRouteHopsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the traceRouteHopsTable.
TracerOutHopSentry对象类型语法TracerOutHopSentry MAX-ACCESS不可访问状态当前描述”在TracerOutHopStable中定义一个条目。
The first two index elements identify the
traceRouteCtlEntry that a traceRouteHopsEntry
belongs to. The third index element,
traceRouteHopsHopIndex, selects a
hop in a traceroute path."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName,
traceRouteHopsHopIndex
}
::= { traceRouteHopsTable 1 }
The first two index elements identify the
traceRouteCtlEntry that a traceRouteHopsEntry
belongs to. The third index element,
traceRouteHopsHopIndex, selects a
hop in a traceroute path."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName,
traceRouteHopsHopIndex
}
::= { traceRouteHopsTable 1 }
TraceRouteHopsEntry ::=
SEQUENCE {
traceRouteHopsHopIndex Unsigned32,
traceRouteHopsIpTgtAddressType InetAddressType,
traceRouteHopsIpTgtAddress InetAddress,
traceRouteHopsMinRtt Unsigned32,
traceRouteHopsMaxRtt Unsigned32,
traceRouteHopsAverageRtt Unsigned32,
traceRouteHopsRttSumOfSquares Unsigned32,
traceRouteHopsSentProbes Unsigned32,
traceRouteHopsProbeResponses Unsigned32,
traceRouteHopsLastGoodProbe DateAndTime
}
TraceRouteHopsEntry ::=
SEQUENCE {
traceRouteHopsHopIndex Unsigned32,
traceRouteHopsIpTgtAddressType InetAddressType,
traceRouteHopsIpTgtAddress InetAddress,
traceRouteHopsMinRtt Unsigned32,
traceRouteHopsMaxRtt Unsigned32,
traceRouteHopsAverageRtt Unsigned32,
traceRouteHopsRttSumOfSquares Unsigned32,
traceRouteHopsSentProbes Unsigned32,
traceRouteHopsProbeResponses Unsigned32,
traceRouteHopsLastGoodProbe DateAndTime
}
traceRouteHopsHopIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Specifies the hop index for a traceroute hop. Values for this object with respect to the same traceRouteCtlOwnerIndex and traceRouteCtlTestName MUST start at 1 and increase monotonically.
traceRouteHopsHopIndex对象类型语法Unsigned32 MAX-ACCESS not accessible STATUS current DESCRIPTION“指定跟踪路由跃点的跃点索引。此对象与相同的跟踪路由CtlownerIndex和跟踪路由CtlTestName的值必须从1开始，并单调递增。
The traceRouteHopsTable keeps the current traceroute path per traceRouteCtlEntry if enabled by setting the corresponding traceRouteCtlCreateHopsEntries to true(1).
如果通过将相应的TracerOuteClCreateHopSenters设置为true（1）启用，则traceRouteHopsTable将保持每个TracerOuteClEntry的当前traceroute路径。
All hops (traceRouteHopsTable entries) in a traceroute
path MUST be updated at the same time when a traceroute
operation completes. Care needs to be applied when either
a path changes or can't be determined. The initial portion
of the path, up to the first hop change, MUST retain the
same traceRouteHopsHopIndex values. The remaining portion
of the path SHOULD be assigned new traceRouteHopsHopIndex
values."
::= { traceRouteHopsEntry 1 }
All hops (traceRouteHopsTable entries) in a traceroute
path MUST be updated at the same time when a traceroute
operation completes. Care needs to be applied when either
a path changes or can't be determined. The initial portion
of the path, up to the first hop change, MUST retain the
same traceRouteHopsHopIndex values. The remaining portion
of the path SHOULD be assigned new traceRouteHopsHopIndex
values."
::= { traceRouteHopsEntry 1 }
traceRouteHopsIpTgtAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteHopsIpTargetAddress
object."
::= { traceRouteHopsEntry 2 }
traceRouteHopsIpTgtAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This objects indicates the type of address stored
in the corresponding traceRouteHopsIpTargetAddress
object."
::= { traceRouteHopsEntry 2 }
traceRouteHopsIpTgtAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reports the IP address associated with
the hop. A value for this object should be reported
as a numeric IP address and not as a DNS name."
::= { traceRouteHopsEntry 3 }
traceRouteHopsIpTgtAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reports the IP address associated with
the hop. A value for this object should be reported
as a numeric IP address and not as a DNS name."
::= { traceRouteHopsEntry 3 }
traceRouteHopsMinRtt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum traceroute round-trip-time (RTT) received for
this hop. A value of 0 for this object implies that no
RTT has been received."
::= { traceRouteHopsEntry 4 }
traceRouteHopsMinRtt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum traceroute round-trip-time (RTT) received for
this hop. A value of 0 for this object implies that no
RTT has been received."
::= { traceRouteHopsEntry 4 }
traceRouteHopsMaxRtt OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only
traceRouteHopsMaxRtt对象类型语法Unsigned32 MAX-ACCESS只读
STATUS current
DESCRIPTION
"The maximum traceroute round-trip-time (RTT) received for
this hop. A value of 0 for this object implies that no
RTT has been received."
::= { traceRouteHopsEntry 5 }
STATUS current
DESCRIPTION
"The maximum traceroute round-trip-time (RTT) received for
this hop. A value of 0 for this object implies that no
RTT has been received."
::= { traceRouteHopsEntry 5 }
traceRouteHopsAverageRtt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current average traceroute round-trip-time (RTT) for
this hop."
::= { traceRouteHopsEntry 6 }
traceRouteHopsAverageRtt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current average traceroute round-trip-time (RTT) for
this hop."
::= { traceRouteHopsEntry 6 }
traceRouteHopsRttSumOfSquares OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the sum of all traceroute responses
received for this hop. Its purpose is to enable standard
deviation calculation."
::= { traceRouteHopsEntry 7 }
traceRouteHopsRttSumOfSquares OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the sum of all traceroute responses
received for this hop. Its purpose is to enable standard
deviation calculation."
::= { traceRouteHopsEntry 7 }
traceRouteHopsSentProbes OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object reflects the number of probes sent
for this hop during this traceroute test. The value of this
object should start at 0."
::= { traceRouteHopsEntry 8 }
traceRouteHopsSentProbes OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object reflects the number of probes sent
for this hop during this traceroute test. The value of this
object should start at 0."
::= { traceRouteHopsEntry 8 }
traceRouteHopsProbeResponses OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of responses received for this hop during this
traceroute test. This value of this object should start
at 0."
::= { traceRouteHopsEntry 9 }
traceRouteHopsProbeResponses OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of responses received for this hop during this
traceroute test. This value of this object should start
at 0."
::= { traceRouteHopsEntry 9 }
traceRouteHopsLastGoodProbe OBJECT-TYPE SYNTAX DateAndTime
traceRouteHopsLastGoodProbe对象类型语法DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time was the last response was received for a probe
for this hop during this traceroute test."
::= { traceRouteHopsEntry 10 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time was the last response was received for a probe
for this hop during this traceroute test."
::= { traceRouteHopsEntry 10 }
-- Notification Definition section
--通知定义部分
traceRoutePathChange NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"The path to a target has changed."
::= { traceRouteNotifications 1 }
traceRoutePathChange NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"The path to a target has changed."
::= { traceRouteNotifications 1 }
traceRouteTestFailed NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"Could not determine the path to a target."
::= { traceRouteNotifications 2 }
traceRouteTestFailed NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"Could not determine the path to a target."
::= { traceRouteNotifications 2 }
traceRouteTestCompleted NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"The path to a target has just been determined."
::= { traceRouteNotifications 3 }
traceRouteTestCompleted NOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"The path to a target has just been determined."
::= { traceRouteNotifications 3 }
-- Conformance information
-- Compliance statements
-- Conformance information
-- Compliance statements
traceRouteCompliances OBJECT IDENTIFIER ::= { traceRouteConformance 1 }
traceRouteGroups OBJECT IDENTIFIER ::= { traceRouteConformance 2 }
traceRouteCompliances OBJECT IDENTIFIER ::= { traceRouteConformance 1 }
traceRouteGroups OBJECT IDENTIFIER ::= { traceRouteConformance 2 }
-- Compliance statements
--合规声明
traceRouteCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DISMAN-TRACEROUTE-MIB."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteGroup
}
GROUP traceRouteTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and are capable of setting
the values for DateAndTime objects."
traceRouteCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DISMAN-TRACEROUTE-MIB."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteGroup
}
GROUP traceRouteTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and are capable of setting
the values for DateAndTime objects."
GROUP traceRouteNotificationsGroup DESCRIPTION "This group defines a collection of optional notifications."
GROUP TracerOutNotificationsGroup DESCRIPTION“此组定义可选通知的集合。”
GROUP traceRouteHopsTableGroup DESCRIPTION "This group lists the objects that make up a traceRouteHopsEntry. Support of the traceRouteHopsTable is optional."
GROUP traceRouteHopsTableGroup DESCRIPTION“此组列出组成traceRouteHopsEntry的对象。对traceRouteHopsTable的支持是可选的。”
OBJECT traceRouteMaxConcurrentRequests MIN-ACCESS read-only DESCRIPTION "The agent is not required to support SET operations to this object."
对象跟踪路由MaxConcurrentRequests最小访问只读说明“不需要代理来支持对此对象的设置操作。”
OBJECT traceRouteCtlByPassRouteTable MIN-ACCESS read-only DESCRIPTION "This object is not required by implementations that are not capable of its implementation. The function represented by this object is implementable if the setsockopt SOL_SOCKET SO_DONTROUTE option is supported."
OBJECT TraceRouteTable MIN-ACCESS只读说明“无法实现此对象的实现不需要此对象。如果支持setsockopt SOL_SOCKET SO_DONTROUTE选项，则此对象表示的函数是可实现的。”
OBJECT traceRouteCtlSourceAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
OBJECT traceRouteCtlSourceAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "This object is not required by implementations that are not capable of binding the send socket with a source address. An implementation is only required to support IPv4 and IPv6 addresses."
DESCRIPTION“无法将发送套接字与源地址绑定的实现不需要此对象。只需要支持IPv4和IPv6地址的实现。”
OBJECT traceRouteCtlSourceAddress SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "This object is not required by implementations that are not capable of binding the send socket with a source address. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
OBJECT TracerOuteClSourceAddress语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“无法将发送套接字绑定到源地址的实现不需要此对象。仅支持IPv4和全局唯一IPv6地址的实现才需要此实现。”
OBJECT traceRouteCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. When write access is not supported return a 0 as the value of this object. A value of 0 implies that the function represented by this option is not supported."
OBJECT TracerOuteCtLiIndex MIN-ACCESS只读说明“不需要写访问。不支持写访问时，将0作为此对象的值返回。值0表示不支持此选项表示的函数。”
OBJECT traceRouteCtlMiscOptions MIN-ACCESS read-only DESCRIPTION "Support of this object is optional. When not supporting do not allow write access and return a zero length octet string as the value of the object."
OBJECT traceRouteCtlMiscOptions MIN-ACCESS只读说明“此对象的支持是可选的。不支持时，不允许写访问并返回零长度八位字节字符串作为对象的值。”
OBJECT traceRouteCtlStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required. It is also allowed for implementations to support only the volatile StorageType enumeration."
对象跟踪路由CTLStorageType MIN-ACCESS只读说明“不需要写访问权限。对于仅支持volatile StorageType枚举的实现，也允许写访问权限。”
OBJECT traceRouteCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. When write access is not supported return a 0 as the value of this object. A value of 0 implies that the function represented by this option is not supported."
OBJECT traceRouteCtlDSField MIN-ACCESS只读说明“不需要写访问。不支持写访问时，返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT traceRouteCtlType MIN-ACCESS read-only DESCRIPTION
对象跟踪类型最小访问只读描述
"Write access is not required. In addition, the only value that is RECOMMENDED to be supported by an implementation is traceRouteUsingUdpProbes."
不需要写访问权限。此外，建议实现支持的唯一值是TraceOutUsingUpProbe
OBJECT traceRouteResultsIpTgtAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由结果IPTGTADDRTYPE语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现应仅支持此对象的ipv4和全局唯一ipv6地址值。”
OBJECT traceRouteResultsIpTgtAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由结果iptgtaddr语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteProbeHistoryHAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object." OBJECT traceRouteProbeHistoryHAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由ProbeHistoryAddrType语法InetAddressType{unknown（0），ipv4（1），ipv6（2）}说明“实现应仅支持此对象的ipv4和全局唯一ipv6地址值。”对象跟踪路由ProbeHistoryAddr语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteHopsIpTgtAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由SIPTGTADDressType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现应仅支持此对象的ipv4和全局唯一ipv6地址值。”
OBJECT traceRouteHopsIpTgtAddress
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION
"An implementation should only support IPv4 and
globally unique IPv6 address values for this object."
::= { traceRouteCompliances 1 }
OBJECT traceRouteHopsIpTgtAddress
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION
"An implementation should only support IPv4 and
globally unique IPv6 address values for this object."
::= { traceRouteCompliances 1 }
-- MIB groupings
--MIB分组
traceRouteGroup OBJECT-GROUP OBJECTS { traceRouteMaxConcurrentRequests, traceRouteCtlTargetAddressType, traceRouteCtlTargetAddress, traceRouteCtlByPassRouteTable,
traceRouteGroup对象组对象{traceRouteMaxConcurrentRequests，tracerouteCtTargetAddressType，tracerouteCtTargetAddress，tracerouteCtBypassRouteTable，
traceRouteCtlDataSize,
traceRouteCtlTimeOut,
traceRouteCtlProbesPerHop,
traceRouteCtlPort,
traceRouteCtlMaxTtl,
traceRouteCtlDSField,
traceRouteCtlSourceAddressType,
traceRouteCtlSourceAddress,
traceRouteCtlIfIndex,
traceRouteCtlMiscOptions,
traceRouteCtlMaxFailures,
traceRouteCtlDontFragment,
traceRouteCtlInitialTtl,
traceRouteCtlFrequency,
traceRouteCtlStorageType,
traceRouteCtlAdminStatus,
traceRouteCtlMaxRows,
traceRouteCtlTrapGeneration,
traceRouteCtlDescr,
traceRouteCtlCreateHopsEntries,
traceRouteCtlType,
traceRouteCtlRowStatus,
traceRouteResultsOperStatus,
traceRouteResultsCurHopCount,
traceRouteResultsCurProbeCount,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr,
traceRouteResultsTestAttempts,
traceRouteResultsTestSuccesses,
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote traceroute
operation."
::= { traceRouteGroups 1 }
traceRouteCtlDataSize,
traceRouteCtlTimeOut,
traceRouteCtlProbesPerHop,
traceRouteCtlPort,
traceRouteCtlMaxTtl,
traceRouteCtlDSField,
traceRouteCtlSourceAddressType,
traceRouteCtlSourceAddress,
traceRouteCtlIfIndex,
traceRouteCtlMiscOptions,
traceRouteCtlMaxFailures,
traceRouteCtlDontFragment,
traceRouteCtlInitialTtl,
traceRouteCtlFrequency,
traceRouteCtlStorageType,
traceRouteCtlAdminStatus,
traceRouteCtlMaxRows,
traceRouteCtlTrapGeneration,
traceRouteCtlDescr,
traceRouteCtlCreateHopsEntries,
traceRouteCtlType,
traceRouteCtlRowStatus,
traceRouteResultsOperStatus,
traceRouteResultsCurHopCount,
traceRouteResultsCurProbeCount,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr,
traceRouteResultsTestAttempts,
traceRouteResultsTestSuccesses,
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote traceroute
operation."
::= { traceRouteGroups 1 }
traceRouteTimeStampGroup OBJECT-GROUP
OBJECTS {
traceRouteResultsLastGoodPath,
traceRouteProbeHistoryTime
}
STATUS current
DESCRIPTION
traceRouteTimeStampGroup OBJECT-GROUP
OBJECTS {
traceRouteResultsLastGoodPath,
traceRouteProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of DateAndTime objects."
::= { traceRouteGroups 2 }
"The group of DateAndTime objects."
::= { traceRouteGroups 2 }
traceRouteNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
traceRoutePathChange,
traceRouteTestFailed,
traceRouteTestCompleted
}
STATUS current
DESCRIPTION
"The notifications which are required to be supported by
implementations of this MIB."
::= { traceRouteGroups 3 }
traceRouteNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
traceRoutePathChange,
traceRouteTestFailed,
traceRouteTestCompleted
}
STATUS current
DESCRIPTION
"The notifications which are required to be supported by
implementations of this MIB."
::= { traceRouteGroups 3 }
traceRouteHopsTableGroup OBJECT-GROUP
OBJECTS {
traceRouteHopsIpTgtAddressType,
traceRouteHopsIpTgtAddress,
traceRouteHopsMinRtt,
traceRouteHopsMaxRtt,
traceRouteHopsAverageRtt,
traceRouteHopsRttSumOfSquares,
traceRouteHopsSentProbes,
traceRouteHopsProbeResponses,
traceRouteHopsLastGoodProbe
}
STATUS current
DESCRIPTION
"The group of objects that comprise the traceRouteHopsTable."
::= { traceRouteGroups 4 }
traceRouteHopsTableGroup OBJECT-GROUP
OBJECTS {
traceRouteHopsIpTgtAddressType,
traceRouteHopsIpTgtAddress,
traceRouteHopsMinRtt,
traceRouteHopsMaxRtt,
traceRouteHopsAverageRtt,
traceRouteHopsRttSumOfSquares,
traceRouteHopsSentProbes,
traceRouteHopsProbeResponses,
traceRouteHopsLastGoodProbe
}
STATUS current
DESCRIPTION
"The group of objects that comprise the traceRouteHopsTable."
::= { traceRouteGroups 4 }
END
终止
DISMAN-NSLOOKUP-MIB DEFINITIONS ::= BEGIN
DISMAN-NSLOOKUP-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2, Integer32 FROM SNMPv2-SMI -- RFC2578 RowStatus FROM SNMPv2-TC -- RFC2579 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC2571
从SNMPv2 SMI导入模块标识、对象类型、未签名32、mib-2、整数32——从SNMPv2 TC导入RFC2578行状态——从SNMPv2 CONF导入RFC2579模块符合性、从SNMPv2 CONF导入对象组——从SNMP-FRAMEWORK-mib导入RFC2580 SnmpAdminString——RFC2571
InetAddressType, InetAddress FROM INET-ADDRESS-MIB; -- RFC2851
InetAddressType，INET-ADDRESS-MIB中的InetAddress；--RFC2851
lookupMIB MODULE-IDENTITY LAST-UPDATED "200009210000Z" -- 21 September 2000 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Kenneth White
lookupMIB模块标识最后更新的“200009210000Z”-2000年9月21日组织“IETF分布式管理工作组”联系方式“Kenneth White”
International Business Machines Corporation Network Computing Software Division Research Triangle Park, NC, USA
国际商用机器公司网络计算软件部美国北卡罗来纳州三角研究园
E-mail: wkenneth@us.ibm.com" DESCRIPTION "The Lookup MIB (DISMAN-NSLOOKUP-MIB) enables determination of either the name(s) corresponding to a host address or of the address(es) associated with a host name at a remote host."
电邮：wkenneth@us.ibm.com“说明”查找MIB（DISAN-NSLOOKUP-MIB）允许确定与主机地址对应的名称或与远程主机上的主机名关联的地址
-- Revision history
--修订历史
REVISION "200009210000Z" -- 21 September 2000 DESCRIPTION "Initial version, published as RFC 2925."
修订版“2000092100Z”-2000年9月21日描述“初始版本，发布为RFC 2925。”
::= { mib-2 82 }
::= { mib-2 82 }
-- Top level structure of the MIB
--MIB的顶层结构
lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 }
lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 }
lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 }
lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 }
-- Simple Object Definitions
--简单对象定义
lookupMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active lookup requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { lookupObjects 1 }
lookupMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active lookup requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect."
DEFVAL { 10 }
::= { lookupObjects 1 }
lookupPurgeTime OBJECT-TYPE SYNTAX Unsigned32 (0..86400) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The amount of time to wait before automatically deleting an entry in the lookupCtlTable and any dependent lookupResultsTable entries after the lookup operation represented by an lookupCtlEntry has completed.
lookupPurgeTime对象类型语法Unsigned32（0..86400）单位“秒”最大访问读写状态当前描述“lookupCtlEntry表示的查找操作完成后，自动删除lookupCtlTable中的项和任何依赖lookupResultsTable项之前等待的时间量。
An lookupCtEntry is considered complete
when its lookupCtlOperStatus object has a
value of completed(3)."
DEFVAL { 900 } -- 15 minutes as default
::= { lookupObjects 2 }
An lookupCtEntry is considered complete
when its lookupCtlOperStatus object has a
value of completed(3)."
DEFVAL { 900 } -- 15 minutes as default
::= { lookupObjects 2 }
-- Lookup Control Table
--查找控制表
lookupCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF LookupCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Lookup Control Table for providing
the capability of performing a lookup operation,
gethostbyname or gethostbyaddr, from a remote host."
::= { lookupObjects 3 }
lookupCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF LookupCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Lookup Control Table for providing
the capability of performing a lookup operation,
gethostbyname or gethostbyaddr, from a remote host."
::= { lookupObjects 3 }
lookupCtlEntry OBJECT-TYPE SYNTAX LookupCtlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the lookupCtlTable. A lookupCtlEntry is initially indexed by lookupCtlOwnerIndex, which is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and also allows an management application to identify its entries. The second index element, lookupCtlOperationName, enables the same lookupCtlOwnerIndex entity to have multiple outstanding requests.
lookupCtlEntry对象类型语法lookupCtlEntry MAX-ACCESS not accessible STATUS current DESCRIPTION“定义lookupCtlTable中的一个条目。lookupCtlEntry最初由lookupCtlOwnerIndex索引，该索引类型为SnmpAdminString，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 2575[11]，VACM）第二个索引元素lookupCtlOwnerIndex允许同一个lookupCtlOwnerIndex实体有多个未完成的请求。
The value of lookupCtlTargetAddressType determines which lookup function to perform. Specification of dns(16)
lookupCtlTargetAddressType的值确定要执行的查找函数。dns规范（16）
as the value of this index implies that the gethostbyname
function should be performed to determine the numeric
addresses associated with a symbolic name via
lookupResultsTable entries. Use of a value of either
ipv4(1) or ipv6(2) implies that the gethostbyaddr function
should be performed to determine the symbolic name(s)
associated with a numeric address at a remote host."
INDEX {
lookupCtlOwnerIndex,
lookupCtlOperationName
}
::= { lookupCtlTable 1 }
as the value of this index implies that the gethostbyname
function should be performed to determine the numeric
addresses associated with a symbolic name via
lookupResultsTable entries. Use of a value of either
ipv4(1) or ipv6(2) implies that the gethostbyaddr function
should be performed to determine the symbolic name(s)
associated with a numeric address at a remote host."
INDEX {
lookupCtlOwnerIndex,
lookupCtlOperationName
}
::= { lookupCtlTable 1 }
LookupCtlEntry ::=
SEQUENCE {
lookupCtlOwnerIndex SnmpAdminString,
lookupCtlOperationName SnmpAdminString,
lookupCtlTargetAddressType InetAddressType,
lookupCtlTargetAddress InetAddress,
lookupCtlOperStatus INTEGER,
lookupCtlTime Unsigned32,
lookupCtlRc Integer32,
lookupCtlRowStatus RowStatus
}
LookupCtlEntry ::=
SEQUENCE {
lookupCtlOwnerIndex SnmpAdminString,
lookupCtlOperationName SnmpAdminString,
lookupCtlTargetAddressType InetAddressType,
lookupCtlTargetAddress InetAddress,
lookupCtlOperStatus INTEGER,
lookupCtlTime Unsigned32,
lookupCtlRc Integer32,
lookupCtlRowStatus RowStatus
}
lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy.
lookupCtlOwnerIndex对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS not accessible STATUS current DESCRIPTION“帮助安全管理员使用基于视图的访问控制模型（RFC 2575，VACM）设置访问控制对于多个用户可能需要独立创建或修改条目的表，初始索引用作“所有者索引”。此类初始索引具有SNMPAdministring语法，因此可以根据安全策略轻松映射到VACM中定义的securityName或groupName。
When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this
当与此类安全策略结合使用时，表中属于特定用户（或组）的所有条目将具有与此初始索引相同的值。对于特定表中的给定用户项，这些项中信息的对象标识符将具有相同的子标识符（除了“列”子标识符），直到编码所有者索引的末尾。将VACM配置为允许访问此
portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index
portion, and vacmViewTreeFamilyMask 'wildcarding' the
column subidentifier. More elaborate configurations
are possible."
::= { lookupCtlEntry 1 }
portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index
portion, and vacmViewTreeFamilyMask 'wildcarding' the
column subidentifier. More elaborate configurations
are possible."
::= { lookupCtlEntry 1 }
lookupCtlOperationName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of a lookup operation. This is locally unique,
within the scope of an lookupCtlOwnerIndex."
::= { lookupCtlEntry 2 }
lookupCtlOperationName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of a lookup operation. This is locally unique,
within the scope of an lookupCtlOwnerIndex."
::= { lookupCtlEntry 2 }
lookupCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of address for either performing a
gethostbyname or a gethostbyaddr function at a remote host.
Specification of dns(16) as the value for this object
means that the gethostbyname function should be performed
to return one or more numeric addresses. Use of a value
of either ipv4(1) or ipv6(2) means that the gethostbyaddr
function should be used to return the symbolic names
associated with a remote host."
::= { lookupCtlEntry 3 }
lookupCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of address for either performing a
gethostbyname or a gethostbyaddr function at a remote host.
Specification of dns(16) as the value for this object
means that the gethostbyname function should be performed
to return one or more numeric addresses. Use of a value
of either ipv4(1) or ipv6(2) means that the gethostbyaddr
function should be used to return the symbolic names
associated with a remote host."
::= { lookupCtlEntry 3 }
lookupCtlTargetAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the address used for a resolver lookup at a remote host. The corresponding lookupCtlAddressType objects determines its type as well as the function that can be requested.
lookupCtlTargetAddress对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“指定用于远程主机上解析程序查找的地址。相应的lookupCtlAddressType对象确定其类型以及可以请求的函数。
A value for this object MUST be set prior to
transitioning its corresponding lookupCtlEntry to
active(1) via lookupCtlRowStatus."
::= { lookupCtlEntry 4 }
A value for this object MUST be set prior to
transitioning its corresponding lookupCtlEntry to
active(1) via lookupCtlRowStatus."
::= { lookupCtlEntry 4 }
lookupCtlOperStatus OBJECT-TYPE
lookupCtlOperStatus对象类型
SYNTAX INTEGER {
notStarted(2), -- operation has not started
completed(3) -- operation is done
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an lookupCtlEntry:
SYNTAX INTEGER {
notStarted(2), -- operation has not started
completed(3) -- operation is done
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an lookupCtlEntry:
enabled(1) - Operation is active. notStarted(2) - Operation has not been enabled. completed(3) - Operation has completed.
已启用（1）-操作处于激活状态。notStarted（2）-尚未启用操作。已完成（3）-操作已完成。
An operation is automatically enabled(1) when its
lookupCtlRowStatus object is transitioned to active(1)
status. Until this occurs lookupCtlOperStatus MUST
report a value of notStarted(2). After the lookup
operation completes (success or failure) the value
for lookupCtlOperStatus MUST be transitioned to
completed(3)."
::= { lookupCtlEntry 5 }
An operation is automatically enabled(1) when its
lookupCtlRowStatus object is transitioned to active(1)
status. Until this occurs lookupCtlOperStatus MUST
report a value of notStarted(2). After the lookup
operation completes (success or failure) the value
for lookupCtlOperStatus MUST be transitioned to
completed(3)."
::= { lookupCtlEntry 5 }
lookupCtlTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the number of milliseconds that a lookup
operation required to be completed at a remote host.
Completed means operation failure as well as
success."
::= { lookupCtlEntry 6 }
lookupCtlTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the number of milliseconds that a lookup
operation required to be completed at a remote host.
Completed means operation failure as well as
success."
::= { lookupCtlEntry 6 }
lookupCtlRc OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system specific return code from a lookup
operation. All implementations MUST return a value
of 0 for this object when the remote lookup
operation succeeds. A non-zero value for this
objects indicates failure. It is recommended that
implementations that support errno use it as the
value of this object to aid a management
application in determining the cause of failure."
::= { lookupCtlEntry 7 }
lookupCtlRc OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system specific return code from a lookup
operation. All implementations MUST return a value
of 0 for this object when the remote lookup
operation succeeds. A non-zero value for this
objects indicates failure. It is recommended that
implementations that support errno use it as the
value of this object to aid a management
application in determining the cause of failure."
::= { lookupCtlEntry 7 }
lookupCtlRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the lookupCtlTable.
lookupCtlRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在lookupCtlTable中创建和删除条目。
A remote lookup operation is started when an entry in this table is created via an SNMP SET request and the entry is activated. This occurs by setting the value of this object to CreateAndGo(4) during row creation or by setting this object to active(1) after the row is created.
通过SNMP SET请求创建此表中的条目并激活该条目时，将启动远程查找操作。通过在创建行期间将此对象的值设置为CreateAndGo（4），或在创建行后将此对象设置为active（1），可以实现此目的。
A value MUST be specified for lookupCtlTargetAddress prior to a transition to active(1) state being accepted.
在接受转换到活动（1）状态之前，必须为lookupCtlTargetAddress指定一个值。
A remote lookup operation starts when its entry first becomes active(1). Transitions in and out of active(1) state have no effect on the operational behavior of a remote lookup operation, with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active remote lookup operation.
远程查找操作在其条目第一次变为活动状态时开始（1）。进入和退出活动（1）状态的转换对远程查找操作的操作行为没有影响，但通过将该表的RowStatus对象设置为destroy（6）删除该表中的条目将停止活动的远程查找操作。
The operational state of a remote lookup operation
can be determined by examination of its
lookupCtlOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579,
'Textual Conventions for SMIv2.'"
::= { lookupCtlEntry 8 }
The operational state of a remote lookup operation
can be determined by examination of its
lookupCtlOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579,
'Textual Conventions for SMIv2.'"
::= { lookupCtlEntry 8 }
-- Lookup Results Table
--查找结果表
lookupResultsTable OBJECT-TYPE SYNTAX SEQUENCE OF LookupResultsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the Lookup Results Table for providing the capability of determining the results of a operation at a remote host.
lookupResultsTable对象类型LookupResultsEntry MAX-ACCESS不可访问状态当前描述的语法序列“定义查找结果表，以提供在远程主机上确定操作结果的功能。
One or more entries are added to the lookupResultsTable when a lookup operation, as reflected by an lookupCtlEntry, completes successfully. All entries related to a successful lookup operation MUST be added to the lookupResultsTable at the same time that the associating lookupCtlOperStatus object is transitioned to completed(2).
当lookupCtlEntry所反映的查找操作成功完成时，将向lookupResultsTable添加一个或多个条目。必须在关联的lookupCtlOperStatus对象转换为completed（2）的同时，将与成功查找操作相关的所有条目添加到lookupResultsTable。
The number of entries added depends on the results determined for a particular lookup operation. All entries associated with an lookupCtlEntry are removed when the lookupCtlEntry is deleted.
添加的条目数取决于为特定查找操作确定的结果。删除lookupCtlEntry时，将删除与lookupCtlEntry关联的所有条目。
A remote host can be multi-homed and have more than one IP address associated with it (gethostbyname results) and/or it can have more than one symbolic name (gethostbyaddr results).
远程主机可以是多宿主的，并且具有多个与其关联的IP地址（gethostbyname结果）和/或具有多个符号名（gethostbyaddr结果）。
The gethostbyaddr function is called with a host address as its parameter and is used primarily to determine a symbolic name to associate with the host address. Entries in the lookupResultsTable MUST be made for each host name returned. The official host name MUST be assigned a lookupResultsIndex of 1.
gethostbyaddr函数以主机地址作为参数调用，主要用于确定要与主机地址关联的符号名。必须为返回的每个主机名创建lookupResultsTable中的条目。必须为正式主机名分配lookupResultsIndex 1。
The gethostbyname function is called with a
symbolic host name and is used primarily to
retrieve a host address. If possible the
primary host address SHOULD be assigned a
lookupResultsIndex of 1."
::= { lookupObjects 4 }
The gethostbyname function is called with a
symbolic host name and is used primarily to
retrieve a host address. If possible the
primary host address SHOULD be assigned a
lookupResultsIndex of 1."
::= { lookupObjects 4 }
lookupResultsEntry OBJECT-TYPE SYNTAX LookupResultsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the lookupResultsTable. The first two index elements identify the lookupCtlEntry that a lookupResultsEntry belongs to. The third index element selects a single lookup operation result." INDEX { lookupCtlOwnerIndex, lookupCtlOperationName,
lookupResultsEntry对象类型语法lookupResultsEntry MAX-ACCESS不可访问状态当前描述“定义lookupResultsTable中的条目。前两个索引元素标识lookupResultsEntry所属的lookupCtlEntry。第三个索引元素选择单个查找操作结果。”索引{lookupCtlOwnerIndex，lookupCtlOperationName，
lookupResultsIndex
}
::= { lookupResultsTable 1 }
lookupResultsIndex
}
::= { lookupResultsTable 1 }
LookupResultsEntry ::=
SEQUENCE {
lookupResultsIndex Unsigned32,
lookupResultsAddressType InetAddressType,
lookupResultsAddress InetAddress
}
LookupResultsEntry ::=
SEQUENCE {
lookupResultsIndex Unsigned32,
lookupResultsAddressType InetAddressType,
lookupResultsAddress InetAddress
}
lookupResultsIndex OBJECT-TYPE SYNTAX Unsigned32 (1..'ffffffff'h) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries in the lookupResultsTable are created when the result of a lookup operation is determined.
lookupResultsIndex对象类型语法Unsigned32（1..'ffffffff'h）MAX-ACCESS not accessible STATUS current DESCRIPTION“在确定查找操作的结果时，将创建lookupResultsTable中的条目。
Entries MUST be stored in the lookupResultsTable in
the order that they are retrieved. Values assigned
to lookupResultsIndex MUST start at 1 and increase
in order."
::= { lookupResultsEntry 1 }
Entries MUST be stored in the lookupResultsTable in
the order that they are retrieved. Values assigned
to lookupResultsIndex MUST start at 1 and increase
in order."
::= { lookupResultsEntry 1 }
lookupResultsAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the type of result of a remote lookup
operation. A value of unknown(0) implies that
either the operation hasn't been started or that
it has failed."
::= { lookupResultsEntry 2 }
lookupResultsAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the type of result of a remote lookup
operation. A value of unknown(0) implies that
either the operation hasn't been started or that
it has failed."
::= { lookupResultsEntry 2 }
lookupResultsAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects a result for a remote lookup operation
as per the value of lookupResultsAddressType."
::= { lookupResultsEntry 3 }
lookupResultsAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects a result for a remote lookup operation
as per the value of lookupResultsAddressType."
::= { lookupResultsEntry 3 }
-- Conformance information
-- Compliance statements
-- Conformance information
-- Compliance statements
lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 }
lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 }
lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 }
lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 }
-- Compliance statements
--合规声明
lookupCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DISMAN-NSLOOKUP-MIB."
MODULE -- this module
MANDATORY-GROUPS {
lookupGroup
}
lookupCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DISMAN-NSLOOKUP-MIB."
MODULE -- this module
MANDATORY-GROUPS {
lookupGroup
}
OBJECT lookupMaxConcurrentRequests MIN-ACCESS read-only DESCRIPTION "The agent is not required to support SET operations to this object."
对象查找MaxConcurrentRequests MIN-ACCESS只读说明“不需要代理来支持对此对象的设置操作。”
OBJECT lookupPurgeTime
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support a SET
operation to this object."
::= { lookupCompliances 1 }
OBJECT lookupPurgeTime
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support a SET
operation to this object."
::= { lookupCompliances 1 }
-- MIB groupings
--MIB分组
lookupGroup OBJECT-GROUP
OBJECTS {
lookupMaxConcurrentRequests,
lookupPurgeTime,
lookupCtlOperStatus,
lookupCtlTargetAddressType,
lookupCtlTargetAddress,
lookupCtlTime,
lookupCtlRc,
lookupCtlRowStatus,
lookupResultsAddressType,
lookupResultsAddress
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote
Lookup operation."
::= { lookupGroups 1 }
lookupGroup OBJECT-GROUP
OBJECTS {
lookupMaxConcurrentRequests,
lookupPurgeTime,
lookupCtlOperStatus,
lookupCtlTargetAddressType,
lookupCtlTargetAddress,
lookupCtlTime,
lookupCtlRc,
lookupCtlRowStatus,
lookupResultsAddressType,
lookupResultsAddress
}
STATUS current
DESCRIPTION
"The group of objects that comprise the remote
Lookup operation."
::= { lookupGroups 1 }
END
终止
Certain management information in the MIBs defined by this document may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information SHOULD be employed in such environments. The method for this authentication is a function of the SNMP Administrative Framework, and has not been expanded by this MIB.
本文档定义的MIB中的某些管理信息在某些网络环境中可能被视为敏感信息。因此，在这样的环境中，应该对接收到的SNMP请求进行身份验证，并控制对管理信息的访问。此身份验证的方法是SNMP管理框架的一个功能，此MIB未对此进行扩展。
To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (VACM) defined in RFC 2575 [11] for tables in which multiple users may need to independently create or modify entries, the initial index is used as an "owner index". Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy.
为了方便安全管理员使用RFC 2575[11]中定义的基于视图的访问控制模型（VACM）对多个用户可能需要独立创建或修改条目的表进行访问控制，初始索引用作“所有者索引”。这样的初始索引具有snmpadmin语法，因此可以根据安全策略简单地映射到VACM中定义的securityName或groupName。
All entries in related tables belonging to a particular user will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the "column" subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask "wildcarding" the column subidentifier. More elaborate configurations are possible. The VACM access control mechanism described above provides control.
相关表中属于特定用户的所有条目对此初始索引具有相同的值。对于特定表中的给定用户项，这些项中信息的对象标识符在编码的所有者索引结束之前将具有相同的子标识符（除了“列”子标识符）。要将VACM配置为允许访问表的这一部分，可以创建vacmViewTreeFamilyTable条目，其值为vacmViewTreeFamilySubtree，包括所有者索引部分，以及VACMVIEWTREEFAMILYMAK“通配符”列子标识符。更复杂的配置是可能的。上述VACM访问控制机制提供控制。
In general, both the ping and traceroute functions when used excessively are considered a form of system attack. In the case of ping sending a system requests too often can negatively effect its performance or attempting to connect to what is supposed to be an unused port can be very unpredictable. Excessive use of the
通常，ping和traceroute功能在过度使用时都被视为一种系统攻击形式。在ping的情况下，过于频繁地发送系统请求可能会对其性能产生负面影响，或者尝试连接到本应未使用的端口可能非常不可预测。过度使用
traceroute capability can like ping negatively affect system performance. In insecure environments it is RECOMMENDED that the MIBs defined within this memo not be supported.
跟踪路由功能可能会对系统性能产生负面影响。在不安全的环境中，建议不支持此备忘录中定义的MIB。
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 implementers 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 this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This document is a product of the DISMAN Working Group.
本文件是DEMAN工作组的成果。
[1] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[1] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[2] Postel, J., "Echo Protocol", STD 20, RFC 862, May 1983.
[2] 《回声协议》，标准20，RFC 862，1983年5月。
[3] 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.
[3] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[4] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[5] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[6] 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.
[6] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[7] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[7] Harrington D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[8] Case, J., Harrington D., Presuhn, R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[8] Case，J.，Harrington D.，Presohn，R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[9] Levi D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[9] Levi D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 25731999年4月。
[10] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[10] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[11] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[11] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC2575，1999年4月。
[12] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[12] Hovey，R.和S.Bradner，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[13] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[14] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, May 1990.
[14] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，RFC 1155，1990年5月。
[15] Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212, March 1991.
[15] Rose，M.和K.McCloghrie，“简明MIB定义”，RFC 1212，1991年3月。
[16] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[16] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[17] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[17] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[18] 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.
[18] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[19] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, BCP 9, October 1996.
[19] Bradner，S.，“互联网标准过程——第3版”，RFC 2026，BCP 9，1996年10月。
[20] Postel, J., "Internet Control Message Protocol", RFC 792, September 1981.
[20] Postel，J.，“互联网控制消息协议”，RFC 792，1981年9月。
[21] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[21] Nichols，K.，Blake，S.，Baker，F.和D.Black，“IPv4和IPv6标头中区分服务字段（DS字段）的定义”，RFC 2474，1998年12月。
[22] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 2851, June 2000.
[22] Daniele，M.，Haberman，B.，Routhier，S.和J.Schoenwaeld，“因特网网络地址的文本约定”，RFC 28512000年6月。
[23] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[23] McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
Kenneth D. White Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
Kenneth D.White部门BRQA/Bldg.501/G114 IBM公司邮箱12195 3039美国北卡罗来纳州康沃利斯三角研究园，邮编27709
EMail: wkenneth@us.ibm.com
EMail: wkenneth@us.ibm.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编辑功能的资金目前由互联网协会提供。