Network Working Group J. Quittek, Ed.
Request for Comments: 4560 NEC
Obsoletes: 2925 K. White, Ed.
Category: Standards Track IBM Corp.
June 2006
Network Working Group J. Quittek, Ed.
Request for Comments: 4560 NEC
Obsoletes: 2925 K. White, Ed.
Category: Standards Track IBM Corp.
June 2006
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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This memo defines Management Information Bases (MIBs) for performing ping, traceroute, and lookup operations at a host. When managing a network, it is useful to be able to initiate and retrieve the results of ping or traceroute operations when they are performed at a remote host. A lookup capability is defined in order to enable resolution of either an IP address to an DNS name or a DNS name to an IP address at a remote host.
此备忘录定义了用于在主机上执行ping、traceroute和查找操作的管理信息库（MIB）。在管理网络时，在远程主机上执行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. Introduction ....................................................3
1.1. Ping .......................................................3
1.2. Traceroute .................................................4
1.3. Lookup .....................................................5
1.4. Remote Operations ..........................................5
2. The Internet-Standard Management Framework ......................5
3. Structure of the MIBs ...........................................6
3.1. Ping MIB ...................................................6
3.1.1. pingMaxConcurrentRequests ...........................7
3.1.2. pingCtlTable ........................................7
3.1.3. pingResultsTable ....................................7
3.1.4. pingProbeHistoryTable ...............................8
3.2. Traceroute MIB .............................................8
3.2.1. traceRouteMaxConcurrentRequests .....................8
3.2.2. traceRouteCtlTable ..................................8
3.2.3. traceRouteResultsTable ..............................9
3.2.4. traceRouteProbeHistoryTable ........................10
3.2.5. traceRouteHopsTable ................................10
3.3. Lookup MIB ................................................10
3.3.1. lookupMaxConcurrentRequests and lookupPurgeTime ....11
3.3.2. lookupCtlTable .....................................11
3.3.3. lookupResultsTable .................................12
3.4. Conformance ...............................................12
4. Definitions ....................................................13
4.1. DISMAN-PING-MIB ...........................................13
4.2. DISMAN-TRACEROUTE-MIB .....................................46
4.3. DISMAN-NSLOOKUP-MIB .......................................84
5. Security Considerations ........................................95
6. Acknowledgements ...............................................97
7. References .....................................................97
7.1. Normative References ......................................97
7.2. Informative References ....................................98
1. Introduction ....................................................3
1.1. Ping .......................................................3
1.2. Traceroute .................................................4
1.3. Lookup .....................................................5
1.4. Remote Operations ..........................................5
2. The Internet-Standard Management Framework ......................5
3. Structure of the MIBs ...........................................6
3.1. Ping MIB ...................................................6
3.1.1. pingMaxConcurrentRequests ...........................7
3.1.2. pingCtlTable ........................................7
3.1.3. pingResultsTable ....................................7
3.1.4. pingProbeHistoryTable ...............................8
3.2. Traceroute MIB .............................................8
3.2.1. traceRouteMaxConcurrentRequests .....................8
3.2.2. traceRouteCtlTable ..................................8
3.2.3. traceRouteResultsTable ..............................9
3.2.4. traceRouteProbeHistoryTable ........................10
3.2.5. traceRouteHopsTable ................................10
3.3. Lookup MIB ................................................10
3.3.1. lookupMaxConcurrentRequests and lookupPurgeTime ....11
3.3.2. lookupCtlTable .....................................11
3.3.3. lookupResultsTable .................................12
3.4. Conformance ...............................................12
4. Definitions ....................................................13
4.1. DISMAN-PING-MIB ...........................................13
4.2. DISMAN-TRACEROUTE-MIB .....................................46
4.3. DISMAN-NSLOOKUP-MIB .......................................84
5. Security Considerations ........................................95
6. Acknowledgements ...............................................97
7. References .....................................................97
7.1. Normative References ......................................97
7.2. Informative References ....................................98
This document defines standards-based MIB modules for performing specific remote operations. The remote operations defined by this document consist of the ping, traceroute, and lookup functions.
本文档定义了用于执行特定远程操作的基于标准的MIB模块。本文档定义的远程操作包括ping、traceroute和lookup函数。
Ping and traceroute are two very useful functions for managing networks. Ping is typically used to determine whether a path exists between two hosts, whereas traceroute shows an actual path.
Ping和traceroute是管理网络的两个非常有用的功能。Ping通常用于确定两台主机之间是否存在路径，而traceroute显示实际路径。
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 functions considered in this document are the equivalents of name to address conversion functions such as gethostbyname()/gethostbyaddr() and getaddrinfo()/getnameinfo().
本文档中考虑的查找函数等效于名称到地址的转换函数，如gethostbyname（）/gethostbyaddr（）和getaddrinfo（）/getnameinfo（）。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
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, including the following:
Ping通常使用Internet控制消息协议（ICMP）“ECHO”功能实现。还可以使用替代方法实现ping功能，包括以下方法：
o Using the UDP echo port (7), if supported.
o 如果支持，请使用UDP回显端口（7）。
This is defined by RFC 862 [RFC862].
这是由RFC 862[RFC862]定义的。
o Timing a Simple Network Management Protocol (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 example) since some routers don't honor Echo Requests (timeout situation) or are handled at lower priority, thus possibly giving false indications of round trip times.
通常，几乎任何请求/响应流都可以用来生成往返时间。通常，许多非ICMP ECHO facility方法有更好的机会产生良好的响应（例如，不超时），因为一些路由器不接受ECHO请求（超时情况）或以较低的优先级处理，因此可能给出错误的往返时间指示。
Note 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 request 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 is also important to a 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 [RFC792]:
某些路由器在响应ICMP回送请求时不返回TTL过期消息的行为部分是由于从RFC 792[RFC792]提取的以下文本：
"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消息
The Lookup operation enables remote lookup of addresses for a symbolic name as it is, for example, performed by functions getnameinfo() or gethostbyaddr() and lookup of symbolic names for an address as it is, for example, performed by functions getaddrinfo() or gethostbyname(). Note that whatever lookup function is chosen, results are not necessarily consistent with the results of a pure Domain Name Service (DNS) lookup, but may be influenced by local lookup tables or other sources of information. The lookup capability can be used to determine the symbolic name of a hop in a traceroute path. Also, the reverse lookup can be used, for example, for analyzing name lookup problems.
查找操作允许远程查找符号名称的地址（例如，由函数getnameinfo（）或gethostbyaddr（）执行），以及查找地址的符号名称（例如，由函数getaddrinfo（）或gethostbyname（）执行）。请注意，无论选择何种查找功能，结果都不一定与纯域名服务（DNS）查找的结果一致，但可能会受到本地查找表或其他信息源的影响。查找功能可用于确定跟踪路由路径中跃点的符号名称。此外，例如，可以使用反向查找来分析名称查找问题。
The MIB modules defined in this document allow a management station to initiate ping, traceroute, and lookup operations remotely. The basic scenario is illustrated by the following diagram.
本文档中定义的MIB模块允许管理站远程启动ping、traceroute和查找操作。下图说明了基本场景。
+-------+ +-------+ +-------+
| |---------->| | | |
| | initiate | |---------->| |
| Mgmt. | operation |Managed| perform |Target |
|Station| remotely | Node | operation | Host |
| | | | | |
| |<----------| | | |
+-------+ receive +-------+ +-------+
result of
operation
+-------+ +-------+ +-------+
| |---------->| | | |
| | initiate | |---------->| |
| Mgmt. | operation |Managed| perform |Target |
|Station| remotely | Node | operation | Host |
| | | | | |
| |<----------| | | |
+-------+ receive +-------+ +-------+
result of
operation
A management station is the local host from which the remote ping, traceroute, or Lookup operation is initiated using an SNMP request. The managed node is a remote host where the MIBs defined by this memo are implemented. It receives the remote operation via SNMP and performs the actual ping, traceroute, or lookup function.
管理站是使用SNMP请求启动远程ping、traceroute或查找操作的本地主机。托管节点是一个远程主机，在此主机上实现此备忘录定义的MIB。它通过SNMP接收远程操作，并执行实际的ping、traceroute或查找功能。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
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 lookup functions for symbolic names and addresses at a remote host provided, for example, by functions getaddrinfo()/getnameinfo() and gethostbyname()/gethostbyaddr().
提供对远程主机上符号名和地址的查找函数的访问，例如，由函数getaddrinfo（）/getnameinfo（）和gethostbyname（）/gethostbyaddr（）提供。
The ping and traceroute MIBs are structured to allow creation of ping or traceroute tests that can be set up to issue a series of operations periodically and to 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 a 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 3415 [RFC3415], VACM) and that allows a management application to identify its entries. The second index, pingCtlTestName (also an SnmpAdminString), enables the same management application to have multiple requests outstanding.
第一个索引元素pingCtlOwnerIndex属于SnmpAdminString类型，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 3415[RFC3415]，VACM），并允许管理应用程序识别其条目。第二个索引pingCtlTestName（也是一个SnmpAdminString）允许同一管理应用程序有多个未完成的请求。
Using the maximum value for the parameters defined within a pingEntry can result in a single remote ping test's taking at most 15 minutes (pingCtlTimeOut times pingCtlProbeCount), plus whatever time it takes to send the ping request and to 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 are 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 are stored in this table on a per-pingCtlEntry basis. This table is initially indexed by pingCtlOwnerIndex and pingCtlTestName so that the results of a probe 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 of the corresponding entry in the pingCtlTable to allow the addition of a new entry once the number of rows in the pingProbeHistoryTable reaches the value specified by pingCtlMaxRows for the corresponding entry in the pingCtlTable. 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中最早的项，以允许在pingProbeHistoryTable中的行数达到pingCtlMaxRows为pingCtlTable中对应项指定的值时添加新项。实现必须开始将pingProbeHistoryIndex值赋值为1，并在超出此对象的限制（'ffffffffffh'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
通过将TracerOuteClAdminStatus设置为enabled（1），可以启动远程跟踪路由测试。在开始测试之前，必须已创建相应的traceRouteCtlEntry，并将其traceRouteCtlRowStatus设置为active（1）。单个SNMP PDU可用于创建和启动远程跟踪路由
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).
测验在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 3415 [RFC3415], VACM) and that 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.
第一个索引元素tracerouteClownerIndex的类型为SNMPAdministring，这是一种文本约定，允许使用基于SNMPv3视图的访问控制模型（RFC 3415[RFC3415]，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, 42 plus hours is too long to wait for a traceroute operation to be completed.
Traceroute的理论最长完成时间比ping长得多：基本上是42小时30分钟（traceRouteCtlTimeOut、traceRouteCtlProbesPerHop和traceRouteCtlMaxTtl的乘积）加上一些网络传输时间！使用traceRouteCtlEntry中定义的默认值，默认traceroute操作的最大时间为4分30秒。显然，等待traceroute操作完成42个多小时太长了。
The maximum Time to Live (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 are 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.
将发生相应的跟踪路由操作。可以检查对象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 so that the results of a probe 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 of the corresponding entry in the traceRouteCtlTable to allow the addition of an new entry once the number of rows in the traceRouteProbeHistoryTable reaches the value of traceRouteCtlMaxRows for the corresponding entry in the traceRouteCtlTable. 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).
此MIB的实现将删除traceRouteProbeHistoryTable中对应项的traceRouteProbeHistoryTable中最早的项，以允许在traceRouteProbeHistoryTable中的行数达到traceRouteCtlTable中对应项的traceRouteCtlMaxRows值时添加新项。实现必须开始将traceRouteProbeHistoryIndex值指定为1，并在超过此对象的限制（'FFFFFFFFFF'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 so that a traceroute path relates 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 is completed.
对象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 can be examined to determine the state of a lookup operation. A management application can delete an active remote lookup request by setting the corresponding lookupCtlRowStatus object to destroy(6).
远程查找操作是通过对lookupCtlRowStatus执行SNMP设置请求来启动的。单个SNMP PDU可用于创建和启动远程查找操作。在PDU中，lookupCtlTargetAddress应设置为要解析的实体（lookupCtlTargetAddressType将默认为ipv4（1）），lookupCtlRowStatus应设置为createAndGo（4）。可以检查对象lookupCtlOperStatus以确定查找操作的状态。管理应用程序可以通过将相应的lookupCtlRowStatus对象设置为destroy（6），删除活动的远程查找请求。
An lookupCtlEntry is initially indexed by lookupCtlOwnerIndex, which is a type of SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 3415 [RFC3415],
lookupCtlEntry最初由lookupCtlOwnerIndex编制索引，lookupCtlOwnerIndex是一种SNMPAdministring，一种允许使用基于SNMPv3视图的访问控制模型（RFC 3415[RFC3415]）的文本约定，
VACM) and that 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.
这也允许管理应用程序识别其条目。然后，索引的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 a function such as getaddrinfo() or gethostbyname() 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 a function such as getnameinfo() or gethostbyaddr() should be performed to determine the symbolic name(s) associated with a numeric address at a remote host.
lookupCtlTargetAddressType的值确定要执行的查找函数。将dns（16）指定为该索引的值意味着应执行诸如getaddrinfo（）或gethostbyname（）之类的函数，以通过lookupResultsTable条目确定与符号名关联的数字地址。使用ipv4（1）或ipv6（2）的值意味着应该执行诸如getnameinfo（）或gethostbyaddr（）之类的函数来确定与远程主机上的数字地址关联的符号名。
The lookupResultsTable is used to store the results of lookup operations. Results to be reported here SHOULD be results of a lookup function that is commonly used by applications at the managed node. This implies that results are not necessarily consistent with the results of a pure DNS lookup at the managed node, but may be influenced by local lookup tables or other sources of information, depending on the configuration of the managed node.
lookupResultsTable用于存储查找操作的结果。此处要报告的结果应该是托管节点上的应用程序常用的查找函数的结果。这意味着结果不一定与托管节点上的纯DNS查找结果一致，但可能受本地查找表或其他信息源的影响，具体取决于托管节点的配置。
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最初由lookupCtlTable包含的相同索引元素（lookupCtlOwnerIndex和lookupCtlOperationName）索引，但有第三个索引元素lookupResultsIndex（Unsigned32文本约定），以便将多个结果与同一lookupCtlEntry关联。
A remote host can be multi-homed and can have multiple symbolic (DNS) names. Therefore, a lookup operation can return multiple IP addresses and multiple symbolic names.
远程主机可以是多主机，并且可以有多个符号（DNS）名称。因此，查找操作可以返回多个IP地址和多个符号名。
If the lookup operation was performed for a certain address by using getnameinfo() or gethostbyaddr(), for example, then entries in the lookupResultsTable MUST be made for each host name returned. If the lookup operation identifies one hostname as the host's 'official host name', then this name MUST be assigned a lookupResultsIndex of 1.
例如，如果使用getnameinfo（）或gethostbyaddr（）对特定地址执行查找操作，则必须为返回的每个主机名在lookupResultsTable中创建条目。如果查找操作将一个主机名标识为主机的“正式主机名”，则必须为该名称分配lookupResultsIndex 1。
If a lookup operation was performed for a certain symbolic name by using getaddrinfo() or gethostbyname(), for example, then entries in the lookupResultsTable MUST be made for each address returned. The entries MUST be stored in the order that they are retrieved. Values assigned to lookupResultsIndex MUST start at 1 and increase in order.
例如，如果使用getaddrinfo（）或gethostbyname（）对某个符号名执行查找操作，则必须为返回的每个地址创建lookupResultsTable中的条目。条目必须按检索顺序存储。分配给lookupResultsIndex的值必须从1开始，并按顺序递增。
An implementation SHOULD NOT retain SNMP-created entries in the lookupResultsTable 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（初始程序加载）中的lookupResultsTable中保留SNMP创建的条目，因为管理应用程序需要看到它们创建的表条目的持久性的一致行为。
Each of the three MIB modules defined in this document has two current compliance statements, one for full compliance and one for minimum compliance. The minimum compliance statements are intended to be applied to implementation for devices with very limited resources. The main difference between full and minimum compliance is that for minimum compliance, dynamic creation and deletion of table entries is not required, whereas it is required for full compliance.
本文档中定义的三个MIB模块中的每一个都有两个当前合规性声明，一个用于完全合规性，另一个用于最低合规性。最低合规性声明旨在适用于资源非常有限的设备的实施。完全遵从性和最小遵从性之间的主要区别在于，对于最小遵从性，不需要动态创建和删除表项，而对于完全遵从性则需要动态创建和删除表项。
In addition, the DISMAN-PING-MIB module and the DISMAN-TRACEROUTE-MIB modules each have a deprecated compliance statement that was current in RFC 2925. Semantically, the new full compliance statements are identical to the deprecated ones. But some of the object groups used in the old compliance statements needed to be split in order to support the new minimal compliance statements.
此外，DISAN-PING-MIB模块和DISAN-TRACEROUTE-MIB模块都有一个在RFC 2925中最新的弃用合规性声明。从语义上讲，新的完全符合性声明与不推荐的完全符合性声明相同。但是，为了支持新的最低合规性声明，需要拆分旧合规性声明中使用的一些对象组。
The following MIB modules import from [RFC2863], [RFC3411], and [RFC4001]. They also use the REFERENCE clause to reference [RFC1812], [RFC2474], and [RFC3260].
以下MIB模块从[RFC2863]、[RFC3411]和[RFC4001]导入。他们还使用REFERENCE子句来引用[RFC1812]、[RFC2474]和[RFC3260]。
DISMAN-PING-MIB DEFINITIONS ::= BEGIN
DISMAN-PING-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32, 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 -- RFC3411 InetAddressType, InetAddress FROM INET-ADDRESS-MIB; -- RFC4001
从SNMPv2 SMI导入模块标识、对象类型、整数32、无符号32、仪表32、mib-2、通知类型、对象标识--RFC2578文本约定、行状态、存储类型、日期和时间、SNMPv2 TC的TruthValue--RFC2579模块符合性、对象组、，SNMPv2 CONF中的通知组--RFC2580 InterfaceIndexOrZero--IF-MIB中的RFC2863 SNMPAdminInstalling FROM SNMP-FRAMEWORK-MIB--RFC3411 InetAddressType，InetAddress FROM INET-ADDRESS-MIB；--RFC4001
pingMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" -- 13 June 2006 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Juergen Quittek
pingMIB模块标识最后一次更新“200606130000Z”-2006年6月13日组织“IETF分布式管理工作组”联系方式“Juergen Quitek”
NEC Europe Ltd. Network Laboratories Kurfuersten-Anlage 36 69115 Heidelberg Germany
NEC欧洲有限公司网络实验室Kurfuersten Anlage 36 69115德国海德堡
Phone: +49 6221 4342-115
电话：+4962214342-115
Email: quittek@netlab.nec.de" DESCRIPTION "The Ping MIB (DISMAN-PING-MIB) provides the capability of controlling the use of the ping function at a remote host.
电邮：quittek@netlab.nec.de“说明”Ping MIB（DISMAN-Ping-MIB）提供了在远程主机上控制Ping功能使用的功能。
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2006年）。此版本的MIB模块是RFC 4560的一部分；有关完整的法律通知，请参见RFC本身。”
-- Revision history
--修订历史
REVISION "200606130000Z" -- 13 June 2006
DESCRIPTION
"Updated version, published as RFC 4560.
- Correctly considered IPv6 in DESCRIPTION
clause of pingCtlDataSize
- Replaced references to RFC 2575 by RFC 3415
- Replaced references to RFC 2571 by RFC 3411
- Replaced references to RFC 2851 by RFC 4001
- Added DEFVAL { {} } to definition of
pingCtlTrapGeneration
- Changed DEFVAL of object pingCtlDescr from
DEFVAL { '00'H } to DEFVAL { ''H }
- Changed DEFVAL of object pingCtlSourceAddressType
from DEFVAL { ipv4 } to DEFVAL { unknown }
- Extended DESCRIPTION clause of pingResultsTable
describing re-initialization of entries
- Changed SYNTAX of pingResultsProbeResponses and
pingResultsSentProbes from Unsigned32 to Gauge32
- Changed status of pingCompliance to deprecated
- Added pingFullCompliance and pingMinimumCompliance
- Changed status of pingGroup and pingTimeStampGroup
to deprecated
- Added pingMinimumGroup, pingCtlRowStatusGroup,
and pingHistoryGroup"
REVISION "200606130000Z" -- 13 June 2006
DESCRIPTION
"Updated version, published as RFC 4560.
- Correctly considered IPv6 in DESCRIPTION
clause of pingCtlDataSize
- Replaced references to RFC 2575 by RFC 3415
- Replaced references to RFC 2571 by RFC 3411
- Replaced references to RFC 2851 by RFC 4001
- Added DEFVAL { {} } to definition of
pingCtlTrapGeneration
- Changed DEFVAL of object pingCtlDescr from
DEFVAL { '00'H } to DEFVAL { ''H }
- Changed DEFVAL of object pingCtlSourceAddressType
from DEFVAL { ipv4 } to DEFVAL { unknown }
- Extended DESCRIPTION clause of pingResultsTable
describing re-initialization of entries
- Changed SYNTAX of pingResultsProbeResponses and
pingResultsSentProbes from Unsigned32 to Gauge32
- Changed status of pingCompliance to deprecated
- Added pingFullCompliance and pingMinimumCompliance
- Changed status of pingGroup and pingTimeStampGroup
to deprecated
- Added pingMinimumGroup, pingCtlRowStatusGroup,
and pingHistoryGroup"
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
OperationResponseStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Used to report the result of an operation:
“用于报告操作结果：
responseReceived(1) - Operation is completed 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, and an
alternate route does not exist.
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
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)
}
responseReceived(1) - Operation is completed 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, and an
alternate route does not exist.
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
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)."
pingUdpEcho OBJECT-IDENTITY STATUS current DESCRIPTION“表示实现正在使用UDP回显端口（7）”
REFERENCE
"RFC 862, 'Echo Protocol'."
::= { pingImplementationTypeDomains 2 }
REFERENCE
"RFC 862, 'Echo Protocol'."
::= { pingImplementationTypeDomains 2 }
pingSnmpQuery OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using an SNMP query
to calculate a round trip time."
::= { pingImplementationTypeDomains 3 }
pingSnmpQuery OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Indicates that an implementation is using an SNMP query
to calculate a round trip time."
::= { 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.
pingMaxConcurrentRequests对象类型语法Unsigned32 UNITS“requests”MAX-ACCESS read-write STATUS current DESCRIPTION“代理实现中允许的最大并发活动ping请求数。此对象的值为0表示对有效的并发活动请求数没有限制。
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceeds the limit just imposed."
DEFVAL { 10 }
::= { pingObjects 1 }
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceeds the limit just imposed."
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
View-Based Access Control Model (RFC 3415, VACM)
and that allows a 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 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
View-Based Access Control Model (RFC 3415, VACM)
and that allows a 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,
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 }
pingCtlProbeCount Unsigned32、pingCtlAdminStatus整数、pingCtlDataFill八位字符串、pingCtlFrequency Unsigned32、pingCtlMaxRows Unsigned32、pingCtlStorageType StorageType、pingCtlTrapGeneration位、pingCtlTrapProbeFailureFilter Unsigned32、pingCtlTrapTestFailureFilter Unsigned32、pingCtlType对象标识符、PingCtlDestr SNMPAdminInstalling、，pingCtlSourceAddressType InetAddressType、pingCtlSourceAddress InetAddress、PingCtliIndex InterfaceIndexOrZero、pingCtlByPassRouteTable TruthValue、PingCtldField 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 create or modify entries independently, 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 defined in VACM, in accordance with a security policy.
pingCtlOwnerIndex对象类型语法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."
::= { 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 a 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 a 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
pingCtlTargetAddress对象类型
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 value of the corresponding pingCtlTargetAddressType.
语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“指定要在远程主机上用于执行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. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained
pingCtlDataSize对象类型语法无符号32（0..65507）单位“八位字节”最大访问读取创建状态当前说明指定在ping操作中要传输的数据部分的大小，以八位字节为单位。是否可以应用此值取决于执行ping操作所选的实现方法，由同一概念行中的pingCtlType指示。如果使用的方法允许应用包含的值
in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size.
在此对象中，则必须应用它。如果指定的大小不适合所选的ping方法，则实现应使用最接近指定大小的大小（适合该方法）。
The maximum value for this object was computed by
subtracting the smallest possible IP header size of
20 octets (IPv4 header with no options) and the UDP
header size of 8 octets from the maximum IP packet size.
An IP packet has a maximum size of 65535 octets
(excluding IPv6 Jumbograms)."
DEFVAL { 0 }
::= { pingCtlEntry 5 }
The maximum value for this object was computed by
subtracting the smallest possible IP header size of
20 octets (IPv4 header with no options) and the UDP
header size of 8 octets from the maximum IP packet size.
An IP packet has a maximum size of 65535 octets
(excluding IPv6 Jumbograms)."
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 }
pingCtlTimeOut对象类型语法Unsigned32（1..60）单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“指定远程ping操作的超时值（以秒为单位）。”
::= { pingCtlEntry 6 }
::= { 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 as part of a single ping test."
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 as part of a single ping test."
DEFVAL { 1 }
::= { pingCtlEntry 7 }
pingCtlAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test should be started
disabled(2) -- test should be stopped
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Reflects the desired state that a pingCtlEntry should be
in:
pingCtlAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test should be started
disabled(2) -- test should be stopped
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Reflects the desired state that a pingCtlEntry should be
in:
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 test is completed the number of seconds as defined by the value of pingCtlFrequency MUST elapse before the next ping test is started.
单个ping测试由一系列ping探针组成。探测的数量由相应pingCtlProbeCount对象的值确定。完成单个测试后，在开始下一个ping测试之前，pingCtlFrequency值定义的秒数必须经过。
A value of 0 for this object implies that the test as defined by the corresponding entry will not be repeated." DEFVAL { 0 }
此对象的值为0表示将不会重复由相应项定义的测试。“deffal{0}
::= { pingCtlEntry 10 }
::= { pingCtlEntry 10 }
pingCtlMaxRows OBJECT-TYPE SYNTAX Unsigned32 UNITS "rows" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of corresponding entries allowed in the pingProbeHistoryTable. An implementation of this MIB will remove the oldest corresponding entry in the pingProbeHistoryTable to allow the addition of an new entry once the number of corresponding 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
pingCtlStorageType对象类型语法StorageType MAX-ACCESS读取创建状态当前
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 }
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),
testCompletion(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object determines when and whether
to generate a notification for this entry:
pingCtlTrapGeneration OBJECT-TYPE
SYNTAX BITS {
probeFailure(0),
testFailure(1),
testCompletion(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object determines when and whether
to generate a notification for this entry:
probeFailure(0) - Generate a pingProbeFailed notification subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of consecutive 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通知。
By default, no bits are set, indicating that
none of the above options is selected."
DEFVAL { {} } -- no bits set.
::= { pingCtlEntry 13 }
By default, no bits are set, indicating that
none of the above options is selected."
DEFVAL { {} } -- no bits set.
::= { 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 BIT probeFailure(0) of object pingCtlTrapGeneration to '1' implies that a pingProbeFailed NOTIFICATION is generated only when
将对象pingCtlTrapGeneration的位probeFailure（0）设置为“1”意味着仅当
a number of consecutive ping probes equal to the
value of pingCtlTrapProbeFailureFilter fail within
a given ping test. After triggering the notification,
the probe failure counter is reset to zero."
DEFVAL { 1 }
::= { pingCtlEntry 14 }
a number of consecutive ping probes equal to the
value of pingCtlTrapProbeFailureFilter fail within
a given ping test. After triggering the notification,
the probe failure counter is reset to zero."
DEFVAL { 1 }
::= { pingCtlEntry 14 }
pingCtlTrapTestFailureFilter 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 pingTestFailed NOTIFICATION.
pingCtlTrapTestFailureFilter对象类型语法Unsigned32（0..15）MAX-ACCESS read create STATUS current DESCRIPTION“此对象的值用于确定何时生成pingTestFailed通知。
Setting BIT testFailure(1) of object
设置对象的位testFailure（1）
pingCtlTrapGeneration to '1' implies that a
pingTestFailed NOTIFICATION is generated only when
a number of consecutive ping tests equal to the
value of pingCtlTrapProbeFailureFilter fail.
After triggering the notification, the test failure
counter is reset to zero."
DEFVAL { 1 }
::= { pingCtlEntry 15 }
pingCtlTrapGeneration to '1' implies that a
pingTestFailed NOTIFICATION is generated only when
a number of consecutive ping tests equal to the
value of pingCtlTrapProbeFailureFilter fail.
After triggering the notification, the test failure
counter is reset to zero."
DEFVAL { 1 }
::= { pingCtlEntry 15 }
pingCtlType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used either to report or to 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 { ''H }
pingCtlDescr对象类型语法SNMPAdministring MAX-ACCESS read create STATUS current DESCRIPTION“此对象的目的是提供远程ping测试的描述性名称。”DEFVAL{“H}
::= { pingCtlEntry 17 }
::= { 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 a ping operation is performed."
DEFVAL { unknown }
::= { pingCtlEntry 18 }
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 a ping operation is performed."
DEFVAL { unknown }
::= { 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 select the address to be used. 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地址不是此计算机的接口地址之一，则返回错误且不发送任何内容。此对象的零长度八位字节字符串值将禁用源地址规范。
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
pingCtlByPassRouteTable对象类型语法TruthValue MAX-ACCESS读取创建状态当前
DESCRIPTION "The purpose of this object is to enable optional 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 ping operation to a local host through an interface that has no route defined (e.g., after the interface was dropped by the routing daemon at the host)."
描述“此对象的目的是启用可选的绕过路由表。如果启用，远程主机将绕过正常路由表，直接发送到连接网络上的主机。如果主机不在直接连接的网络上，则返回错误。此选项可用于通过未定义路由的接口对本地主机执行ping操作（例如，在主机上的路由守护程序删除该接口之后）。”
DEFVAL { false }
::= { pingCtlEntry 21 }
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 Type of Service (TOS) octet in the IPv4 header or in the Traffic Class octet in the IPv6 header, respectively, of the IP packet used to encapsulate the ping probe.
PingCtldField对象类型语法Unsigned32（0..255）MAX-ACCESS read create STATUS current DESCRIPTION“指定分别存储在用于封装ping探测的IP数据包的IPv4报头中的服务类型（TOS）八位字节或IPv6报头中的流量类八位字节中的值。
The octet to be set in the IP header contains the Differentiated Services (DS) Field in the six most significant bits.
要在IP报头中设置的八位字节在六个最高有效位中包含区分服务（DS）字段。
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 and RFC 3260 for guidance on usage of
this field."
REFERENCE
"Refer to RFC 1812 for the definition of the IPv4 TOS
octet and to RFC 2460 for the definition of the IPv6
Traffic Class octet. Refer to RFC 2474 and RFC 3260
for the definition of the Differentiated Services Field."
DEFVAL { 0 }
::= { pingCtlEntry 22 }
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 and RFC 3260 for guidance on usage of
this field."
REFERENCE
"Refer to RFC 1812 for the definition of the IPv4 TOS
octet and to RFC 2460 for the definition of the IPv6
Traffic Class octet. Refer to RFC 2474 and RFC 3260
for the definition of the Differentiated Services Field."
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 the deletion of all corresponding (same pingCtlOwnerIndex and pingCtlTestName index values) pingResultsTable and pingProbeHistoryTable entries.
pingCtlRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在pingCtlTable中创建和删除条目。删除此表中的条目会导致删除所有相应的（相同的pingCtlOwnerIndex和pingCtlTestName索引值）pingResultsTable和pingProbeHistoryTable条目。
A value MUST be specified for pingCtlTargetAddress prior to acceptance of a transition to active(1) state.
在接受转换到活动（1）状态之前，必须为pingCtlTargetAddress指定一个值。
When a value for pingCtlTargetAddress is set,
设置pingCtlTargetAddress的值时，
the value of object pingCtlRowStatus changes from notReady(3) to notInService(2).
对象pingCtlRowStatus的值从notReady（3）更改为notInService（2）。
Activation of a remote ping operation is controlled via pingCtlAdminStatus, 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 pingProbeHistoryTable.
pingResultsTable PingResultsEntry MAX-ACCESS不可访问状态当前描述的对象类型语法序列“定义Ping结果表，用于提供在远程主机上执行Ping操作的功能。这些操作的结果存储在pingResultsTable和pingProbeHistoryTable中。
An entry is added to the pingResultsTable when an pingCtlEntry is started by successful transition of its pingCtlAdminStatus object to enabled(1).
当通过将pingCtlAdminStatus对象成功转换为enabled（1）启动pingCtlEntry时，将向pingResultsTable添加一个条目。
If the object pingCtlAdminStatus already has the value enabled(1), and if the corresponding pingResultsOperStatus object has the value completed(3), then successfully writing enabled(1) to object pingCtlAdminStatus re-initializes the already existing entry in the pingResultsTable. The values of objects in the re-initialized entry are the same as the values of objects in a new entry would be.
如果对象pingCtlAdminStatus的值已启用（1），并且对应的PingResultsOperatStatus对象的值已完成（3），则成功将启用（1）写入对象pingCtlAdminStatus将重新初始化pingResultsTable中已存在的条目。重新初始化的条目中的对象值与新条目中的对象值相同。
An entry is removed from the pingResultsTable when its corresponding pingCtlEntry is deleted."
删除相应的pingCtlEntry时，将从pingResultsTable中删除条目。“
::= { pingObjects 3 }
::= { 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 so that a pingResultsEntry
corresponds to the pingCtlEntry that caused it to
be created."
INDEX {
pingCtlOwnerIndex,
pingCtlTestName
}
::= { pingResultsTable 1 }
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 so that a pingResultsEntry
corresponds 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 Gauge32,
pingResultsSentProbes Gauge32,
pingResultsRttSumOfSquares Unsigned32,
pingResultsLastGoodProbe DateAndTime
}
PingResultsEntry ::=
SEQUENCE {
pingResultsOperStatus INTEGER,
pingResultsIpTargetAddressType InetAddressType,
pingResultsIpTargetAddress InetAddress,
pingResultsMinRtt Unsigned32,
pingResultsMaxRtt Unsigned32,
pingResultsAverageRtt Unsigned32,
pingResultsProbeResponses Gauge32,
pingResultsSentProbes Gauge32,
pingResultsRttSumOfSquares Unsigned32,
pingResultsLastGoodProbe DateAndTime
}
pingResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2), -- test has stopped
completed(3) -- test is completed
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of a pingCtlEntry:
pingResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2), -- test has stopped
completed(3) -- test is completed
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
completed(3) - Test is completed."
::= { pingResultsEntry 1 }
enabled(1) - Test is active.
disabled(2) - Test has stopped.
completed(3) - Test is completed."
::= { pingResultsEntry 1 }
pingResultsIpTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object 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 object indicates the type of address stored
in the corresponding pingResultsIpTargetAddress
object."
DEFVAL { unknown }
::= { pingResultsEntry 2 }
pingResultsIpTargetAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object 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.
pingResultsIpTargetAddress对象类型语法InetAddress MAX-ACCESS只读状态当前说明“当目标地址指定为DNS名称时，此对象报告与pingCtlTargetAddress值关联的IP地址。当未指定DNS名称或指定的DNS名称解析失败时，此对象的值应为零长度八位字符串。
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingResultsIpTargetAddressType."
DEFVAL { ''H }
::= { pingResultsEntry 3 }
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingResultsIpTargetAddressType."
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
pingResultsMaxRtt对象类型语法无符号32单位“毫秒”最大访问只读状态当前说明
"The maximum ping round-trip-time (RTT) received. A value of 0 for this object implies that no RTT has been received."
“收到的最大ping往返时间（RTT）。此对象的值为0表示未收到RTT。”
::= { pingResultsEntry 5 }
::= { 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 Gauge32
UNITS "responses"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of responses received for the corresponding
pingCtlEntry and pingResultsEntry. The value of this object
MUST be reported as 0 when no probe responses have been
received."
::= { pingResultsEntry 7 }
pingResultsProbeResponses OBJECT-TYPE
SYNTAX Gauge32
UNITS "responses"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of responses received for the corresponding
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 Gauge32
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 Gauge32
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 ping operations. The number of entries in this table is limited per entry in the pingCtlTable by the value of the corresponding pingCtlMaxRows object.
pingProbeHistoryTable对象类型PingProbeHistoryEntry MAX-ACCESS不可访问状态当前描述”的语法序列定义了一个用于存储ping操作结果的表。此表中的条目数受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 of the
corresponding entry in the pingCtlTable to allow
the addition of an new entry once the number of rows
in the pingProbeHistoryTable reaches the value
specified by pingCtlMaxRows for the corresponding
entry in the pingCtlTable."
::= { pingObjects 4 }
An implementation of this MIB will remove the oldest
entry in the pingProbeHistoryTable of the
corresponding entry in the pingCtlTable to allow
the addition of an new entry once the number of rows
in the pingProbeHistoryTable reaches the value
specified by pingCtlMaxRows for the corresponding
entry in the pingCtlTable."
::= { 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 {
pingProbeHistoryEntry对象类型语法pingProbeHistoryEntry MAX-ACCESS不可访问状态当前描述“定义pingProbeHistoryTable中的条目。前两个索引元素标识pingProbeHistoryEntry所属的pingCtlEntry。第三个索引元素选择单个探测结果。”索引{
pingCtlOwnerIndex,
pingCtlTestName,
pingProbeHistoryIndex
}
::= { pingProbeHistoryTable 1 }
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 "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.
pingProbeHistoryIndex对象类型语法Unsigned32（1..'ffffffff'h）MAX-ACCESS不可访问状态当前描述“当确定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
pingProbeHistoryStatus对象类型语法操作ResponseStatus MAX-ACCESS只读状态当前
DESCRIPTION
"The result of a particular probe done by a remote host."
::= { pingProbeHistoryEntry 3 }
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 codes are maintained
by IANA. Standardized ICMP codes are listed at
http://www.iana.org/assignments/icmp-parameters.
The ICMPv6 codes are listed at
http://www.iana.org/assignments/icmpv6-parameters."
::= { 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 codes are maintained
by IANA. Standardized ICMP codes are listed at
http://www.iana.org/assignments/icmp-parameters.
The ICMPv6 codes are listed at
http://www.iana.org/assignments/icmpv6-parameters."
::= { pingProbeHistoryEntry 4 }
pingProbeHistoryTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Timestamp for when this probe result was determined."
::= { pingProbeHistoryEntry 5 }
pingProbeHistoryTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
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
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 consecutive probe failures that are required before this notification can be generated."
对应的pingCtlTrapGeneration对象设置为ProbeFiure（0），取决于pingCtlTrapProbeFailureFilter的值。对象pingCtlTrapProbeFailureFilter可用于指定生成此通知之前所需的连续探测失败数。”
::= { pingNotifications 1 }
::= { pingNotifications 1 }
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 failed."
::= { pingNotifications 2 }
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 failed."
::= { pingNotifications 2 }
pingTestCompleted NOTIFICATION-TYPE OBJECTS { pingCtlTargetAddressType, pingCtlTargetAddress, pingResultsOperStatus, pingResultsIpTargetAddressType, pingResultsIpTargetAddress, pingResultsMinRtt, pingResultsMaxRtt, pingResultsAverageRtt, pingResultsProbeResponses, pingResultsSentProbes, pingResultsRttSumOfSquares, pingResultsLastGoodProbe
pingTestCompleted通知类型对象{PingCttTargetAddressType，PingCttTargetAddress，PingResultsOperatStatus，pingResultsIpTargetAddressType，pingResultsIpTargetAddress，pingResultsMinRtt，pingResultsMaxRtt，pingResultsAverageRtt，PingResultsProberResponse，PingResultsSentProbesProbesSquares，pingResultsLastGoodProbe
}
STATUS current
DESCRIPTION
"Generated at the completion of a ping test when the
corresponding pingCtlTrapGeneration object has the
testCompletion(2) bit set."
::= { pingNotifications 3 }
}
STATUS current
DESCRIPTION
"Generated at the completion of a ping test when the
corresponding pingCtlTrapGeneration object has the
testCompletion(2) bit set."
::= { pingNotifications 3 }
-- 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
--合规声明
pingFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
fully implement the DISMAN-PING-MIB."
MODULE -- this module
MANDATORY-GROUPS {
pingMinimumGroup,
pingCtlRowStatusGroup,
pingHistoryGroup,
pingNotificationsGroup
}
pingFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
fully implement the DISMAN-PING-MIB."
MODULE -- this module
MANDATORY-GROUPS {
pingMinimumGroup,
pingCtlRowStatusGroup,
pingHistoryGroup,
pingNotificationsGroup
}
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."
对象pingCtlStorageType MIN-ACCESS只读说明“不需要写访问。”
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 pingCtlSourceAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access to 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
对象pingCtlSourceAddress语法InetAddress（大小（0 | 4 | 16））最小访问只读
DESCRIPTION "Write access to 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 pingCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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 pingCtlByPassRouteTable MIN-ACCESS read-only DESCRIPTION "Write access to 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 pingCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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 PingCtldField MIN-ACCESS只读说明“不需要写访问。如果不支持写访问，则返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT pingResultsIpTargetAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to
对象PingResultSiptTargetAddressType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现只需要
support IPv4 and IPv6 addresses."
支持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地址才需要实现。”
OBJECT pingResultsLastGoodProbe DESCRIPTION "This object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT pingResultsLastGoodProbe DESCRIPTION“对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
OBJECT pingProbeHistoryTime
DESCRIPTION
"This object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values
be reported as '0000000000000000'H."
::= { pingCompliances 2 }
OBJECT pingProbeHistoryTime
DESCRIPTION
"This object is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this object is not supported its values
be reported as '0000000000000000'H."
::= { pingCompliances 2 }
pingMinimumCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The minimum compliance statement for SNMP entities that implement the minimal subset of the DISMAN-PING-MIB. Implementors might choose this subset for small devices with limited resources." MODULE -- this module MANDATORY-GROUPS { pingMinimumGroup }
pingMinimumCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“实现DISAN-PING-MIB最小子集的SNMP实体的最小符合性声明。实现者可以为资源有限的小型设备选择此子集。”模块--此模块为必填项-GROUPS{pingMinimumGroup}
GROUP pingCtlRowStatusGroup DESCRIPTION "A compliant implementation does not have to implement the pingCtlRowStatusGroup."
GROUP pingCtlRowStatusGroup DESCRIPTION“符合要求的实现不必实现pingCtlRowStatusGroup。”
GROUP pingHistoryGroup DESCRIPTION "A compliant implementation does not have to implement the pingHistoryGroup."
GROUP pingHistoryGroup DESCRIPTION“兼容的实现不必实现pingHistoryGroup。”
GROUP pingNotificationsGroup DESCRIPTION "A compliant implementation does not have to implement
GROUP pingNotificationsGroup DESCRIPTION“兼容的实现不必实现
the pingNotificationsGroup."
pingNotificationsGroup。“
OBJECT pingMaxConcurrentRequests MIN-ACCESS read-only DESCRIPTION "The agent is not required to support set operations to this object."
对象pingMaxConcurrentRequests最小访问只读说明“不需要代理来支持对此对象的设置操作。”
OBJECT pingCtlDataFill MIN-ACCESS read-only DESCRIPTION "The agent is not required to support set operations to this object."
对象pingCtlDataFill MIN-ACCESS只读说明“代理不需要支持对此对象的设置操作。”
OBJECT pingCtlFrequency MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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."
对象pingCtlFrequency MIN-ACCESS只读说明“不需要写访问。如果不支持写访问，则返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT pingCtlMaxRows MIN-ACCESS read-only DESCRIPTION "Write access is not required. If the pingHistoryGroup is not implemented, then write access to this object MUST be disabled, and the object MUST return a value of 0 when retrieved."
对象pingCtlMaxRows MIN-ACCESS只读说明“不需要写访问权限。如果未实现pingHistoryGroup，则必须禁用对此对象的写访问权限，并且检索对象时必须返回值0。”
OBJECT pingCtlStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象pingCtlStorageType MIN-ACCESS只读说明“不需要写访问。”
OBJECT pingCtlTrapGeneration MIN-ACCESS read-only DESCRIPTION "Write access is not required. If the pingNotificationsGroup is not implemented, then write access to this object MUST be disabled, and the object MUST return a value with no bit set when retrieved. No bit set indicates that not notification is generated."
对象pingCtlTrapGeneration MIN-ACCESS只读说明“不需要写访问。如果未实现pingNotificationsGroup，则必须禁用对此对象的写访问，并且检索对象时必须返回未设置位的值。未设置位表示未生成通知。”
OBJECT pingCtlTrapProbeFailureFilter MIN-ACCESS read-only DESCRIPTION
对象pingCtlTrapProbeFailureFilter最小访问只读说明
"If write access to pingCtlTrapGeneration is not supported, then write access to this object must also not be supported. In this case, return 0 as the value of this object."
如果不支持对pingCtlTrapGeneration的写入访问，则也必须不支持对此对象的写入访问。在这种情况下，请将0作为此对象的值返回
OBJECT pingCtlTrapTestFailureFilter MIN-ACCESS read-only DESCRIPTION "If write access to pingCtlTrapGeneration is not supported, then write access to this object must also not be supported. In this case, return 0 as the value of this object."
对象pingCtlTrapTestFailureFilter最小访问只读说明“如果不支持对pingCtlTrapGeneration的写入访问，则也必须不支持对此对象的写入访问。在这种情况下，请将0作为此对象的值返回。”
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 pingCtlDescr MIN-ACCESS read-only DESCRIPTION "The agent is not required to support set operations to this object."
对象pingCtlDescr MIN-ACCESS只读说明“代理不需要支持对此对象的设置操作。”
OBJECT pingCtlSourceAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access to 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 "Write access to 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."
对象pingCtlSourceAddress语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“无法将发送套接字与源地址绑定的实现不需要对此对象的写访问权限。只需要支持IPv4和IPv6地址的实现。”
OBJECT pingCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. If write access is
对象PingCtliIndex MIN-ACCESS只读说明“不需要写访问。如果需要写访问
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."
不支持，返回0作为此对象的值。值为0表示不支持此选项表示的函数。“
OBJECT pingCtlByPassRouteTable MIN-ACCESS read-only DESCRIPTION "Write access is not required. If write access is not supported, return false(2) as the value of this object. A value of false(2) means that the function represented by this option is not supported."
OBJECT pingCtlByPassRouteTable MIN-ACCESS只读说明“不需要写访问。如果不支持写访问，则返回false（2）作为此对象的值。false（2）表示不支持此选项表示的函数。”
OBJECT pingCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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 PingCtldField MIN-ACCESS只读说明“不需要写访问。如果不支持写访问，则返回0作为此对象的值。值0表示不支持此选项表示的函数。”
OBJECT pingResultsIpTargetAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
OBJECT pingResultsIpTargetAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "An implementation is only required to support IPv4 and IPv6 addresses."
DESCRIPTION“实现仅需要支持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地址才需要实现。”
OBJECT pingResultsLastGoodProbe DESCRIPTION "This object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT pingResultsLastGoodProbe DESCRIPTION“对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
OBJECT pingProbeHistoryTime DESCRIPTION "If the pingHistoryGroup is implemented, then this object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values
OBJECT pingProbeHistoryTime DESCRIPTION“如果实现了pingHistoryGroup，那么对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，使用其值
be reported as '0000000000000000'H."
报告为“0000000000000000”小时。”
::= { pingCompliances 3 }
::= { pingCompliances 3 }
pingCompliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "The compliance statement for the DISMAN-PING-MIB. This compliance statement has been deprecated because the group pingGroup and the pingTimeStampGroup have been split and deprecated. The pingFullCompliance statement is semantically identical to the deprecated pingCompliance statement."
pingCompliance MODULE-COMPLIANCE STATUS已弃用描述“DISMAN-PING-MIB的符合性声明。此符合性声明已弃用，因为组pingGroup和pingTimeStampGroup已拆分并弃用。pingFullCompliance声明在语义上与弃用的pingCompliance声明相同。”
MODULE -- this module
MANDATORY-GROUPS {
pingGroup,
pingNotificationsGroup
}
GROUP pingTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this group is not supported the values
for the objects in this group be reported as
'0000000000000000'H."
MODULE -- this module
MANDATORY-GROUPS {
pingGroup,
pingNotificationsGroup
}
GROUP pingTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects. It is RECOMMENDED
that when this group is not supported the values
for the objects in this group be reported as
'0000000000000000'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 that implementations 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."
对象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."
OBJECT 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."
::= { pingCompliances 1 }
OBJECT pingResultsIpTargetAddress
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION
"An implementation is only required to
support IPv4 and globally unique IPv6 addresses."
::= { pingCompliances 1 }
-- MIB groupings
--MIB分组
pingMinimumGroup OBJECT-GROUP OBJECTS { pingMaxConcurrentRequests, pingCtlTargetAddressType, pingCtlTargetAddress, pingCtlDataSize, pingCtlTimeOut, pingCtlProbeCount, pingCtlAdminStatus, pingCtlDataFill, pingCtlFrequency, pingCtlMaxRows, pingCtlStorageType, pingCtlTrapGeneration, pingCtlTrapProbeFailureFilter, pingCtlTrapTestFailureFilter, pingCtlType, pingCtlDescr,
pingMinimumGroup对象组对象{pingMaxConcurrentRequests、pingCtlTargetAddressType、pingCtlTargetAddress、pingCtlDataSize、pingCtlTimeOut、pingCtlProbeCount、pingCtlAdminStatus、pingCtlDataFill、pingCtlFrequency、pingCtlMaxRows、pingCtlStorageType、pingCtlTrapProbeFailureFilter、pingCtlTrapTestFailureFilter、PingCtldDescr、，
pingCtlByPassRouteTable, pingCtlSourceAddressType, pingCtlSourceAddress, pingCtlIfIndex, pingCtlDSField, pingResultsOperStatus, pingResultsIpTargetAddressType, pingResultsIpTargetAddress, pingResultsMinRtt, pingResultsMaxRtt, pingResultsAverageRtt, pingResultsProbeResponses, pingResultsSentProbes, pingResultsRttSumOfSquares, pingResultsLastGoodProbe } STATUS current DESCRIPTION "The group of objects that constitute the remote ping capability."
pingCtlByPassRouteTable、pingCtlSourceAddressType、pingCtlSourceAddress、PingCtliIndex、PingCtldField、PingResultsOperatStatus、pingResultsIpTargetAddressType、pingResultsMinRtt、pingResultsMaxRtt、pingResultsAverageRtt、PingResultsProberResponses、pingResultsSentProbes、pingResultsRttSumOfSquares、，pingResultsLastGoodProbe}状态当前描述“构成远程ping功能的对象组。”
::= { pingGroups 4 }
::= { pingGroups 4 }
pingCtlRowStatusGroup OBJECT-GROUP
OBJECTS {
pingCtlRowStatus
}
STATUS current
DESCRIPTION
"The RowStatus object of the pingCtlTable."
::= { pingGroups 5 }
pingCtlRowStatusGroup OBJECT-GROUP
OBJECTS {
pingCtlRowStatus
}
STATUS current
DESCRIPTION
"The RowStatus object of the pingCtlTable."
::= { pingGroups 5 }
pingHistoryGroup OBJECT-GROUP
OBJECTS {
pingProbeHistoryResponse,
pingProbeHistoryStatus,
pingProbeHistoryLastRC,
pingProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of objects that constitute the history
capability."
::= { pingGroups 6 }
pingHistoryGroup OBJECT-GROUP
OBJECTS {
pingProbeHistoryResponse,
pingProbeHistoryStatus,
pingProbeHistoryLastRC,
pingProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of objects that constitute the history
capability."
::= { pingGroups 6 }
pingNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
pingProbeFailed,
pingTestFailed,
pingTestCompleted
}
pingNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
pingProbeFailed,
pingTestFailed,
pingTestCompleted
}
STATUS current
DESCRIPTION
"The notification that are required to be supported by
implementations of this MIB."
::= { pingGroups 3 }
STATUS current
DESCRIPTION
"The notification that are required to be supported by
implementations of this MIB."
::= { pingGroups 3 }
pingGroup OBJECT-GROUP OBJECTS { pingMaxConcurrentRequests, pingCtlTargetAddressType, pingCtlTargetAddress, pingCtlDataSize, pingCtlTimeOut, pingCtlProbeCount, pingCtlAdminStatus, pingCtlDataFill, pingCtlFrequency,
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 deprecated
DESCRIPTION
"The group of objects that constitute the remote ping
capability."
::= { pingGroups 1 }
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 deprecated
DESCRIPTION
"The group of objects that constitute the remote ping
capability."
::= { pingGroups 1 }
pingTimeStampGroup OBJECT-GROUP
PingGroup对象组
OBJECTS {
pingResultsLastGoodProbe,
pingProbeHistoryTime
}
STATUS deprecated
DESCRIPTION
"The group of DateAndTime objects."
::= { pingGroups 2 }
OBJECTS {
pingResultsLastGoodProbe,
pingProbeHistoryTime
}
STATUS deprecated
DESCRIPTION
"The group of DateAndTime objects."
::= { pingGroups 2 }
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 -- RFC3411 InterfaceIndexOrZero -- RFC2863 FROM IF-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC4001 OperationResponseStatus FROM DISMAN-PING-MIB; -- RFC4560
从SNMPv2 SMI--RFC2578 RowStatus、StorageType、TruthValue、DateAndTime和SNMPv2 TC--RFC2579 MODULE-COMPLIANCE、OBJECT-GROUP、，SNMPv2 CONF中的通知组——SNMP-FRAMEWORK-MIB中的RFC2580 SNMPAdministring——RFC3411接口索引零——IF-MIB中的RFC2863 InetAddressType，INET-ADDRESS-MIB中的InetAddress——DISMAN-PING-MIB中的RFC4001操作响应状态；——RFC4560
traceRouteMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" -- 13 June 2006 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Juergen Quittek
TRACEROTEMIB模块标识最后一次更新“200606130000Z”-2006年6月13日组织“IETF分布式管理工作组”联系方式“Juergen Quitek”
NEC Europe Ltd. Network Laboratories Kurfuersten-Anlage 36 69115 Heidelberg Germany
NEC欧洲有限公司网络实验室Kurfuersten Anlage 36 69115德国海德堡
Phone: +49 6221 4342-115 Email: quittek@netlab.nec.de" DESCRIPTION "The Traceroute MIB (DISMAN-TRACEROUTE-MIB) provides access to the traceroute capability at a remote host.
电话：+49 6221 4342-115电子邮件：quittek@netlab.nec.de“说明”跟踪路由MIB（DISAN-Traceroute-MIB）提供对远程主机上跟踪路由功能的访问。
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2006年）。此版本的MIB模块是RFC 4560的一部分；有关完整的法律通知，请参见RFC本身。”
-- Revision history
--修订历史
REVISION "200606130000Z" -- 13 June 2006
DESCRIPTION
"Updated version, published as RFC 4560.
- Correctly considered IPv6 in DESCRIPTION clause of
object traceRouteCtlDataSize
- Replaced references to RFC 2575 by RFC 3415
- Replaced references to RFC 2571 by RFC 3411
- Replaced references to RFC 2851 by RFC 4001
- Clarified DESCRIPTION clause of object
traceRouteResultsLastGoodPath
- Changed range of object traceRouteCtlInitialTtl
from (0..255) to (1..255)
- Extended DESCRIPTION clause of traceRouteResultsTable
describing re-initialization of entries
- Changed SYNTAX of traceRouteResultsTestAttempts and
traceRouteResultsTestSuccesses from Unsigned32 to
Gauge32
- Changed status of traceRouteCompliance to deprecated
- Added traceRouteFullCompliance and
traceRouteMinimumCompliance
- Changed status of traceRouteGroup and
traceRouteTimeStampGroup to deprecated
- Added traceRouteMinimumGroup,
traceRouteCtlRowStatusGroup, and
traceRouteHistoryGroup
- Changed DEFVAL of object
traceRouteCtlTargetAddressType from { ipv4 }
to { unknown }
- Changed DEFVAL of object traceRouteCtlDescr
from { '00'H } to { ''H }
- Added DEFVAL for object traceRouteCtlTrapGeneration
of DEFVAL { { } }"
REVISION "200009210000Z" -- 21 September 2000
DESCRIPTION
"Initial version, published as RFC 2925."
REVISION "200606130000Z" -- 13 June 2006
DESCRIPTION
"Updated version, published as RFC 4560.
- Correctly considered IPv6 in DESCRIPTION clause of
object traceRouteCtlDataSize
- Replaced references to RFC 2575 by RFC 3415
- Replaced references to RFC 2571 by RFC 3411
- Replaced references to RFC 2851 by RFC 4001
- Clarified DESCRIPTION clause of object
traceRouteResultsLastGoodPath
- Changed range of object traceRouteCtlInitialTtl
from (0..255) to (1..255)
- Extended DESCRIPTION clause of traceRouteResultsTable
describing re-initialization of entries
- Changed SYNTAX of traceRouteResultsTestAttempts and
traceRouteResultsTestSuccesses from Unsigned32 to
Gauge32
- Changed status of traceRouteCompliance to deprecated
- Added traceRouteFullCompliance and
traceRouteMinimumCompliance
- Changed status of traceRouteGroup and
traceRouteTimeStampGroup to deprecated
- Added traceRouteMinimumGroup,
traceRouteCtlRowStatusGroup, and
traceRouteHistoryGroup
- Changed DEFVAL of object
traceRouteCtlTargetAddressType from { ipv4 }
to { unknown }
- Changed DEFVAL of object traceRouteCtlDescr
from { '00'H } to { ''H }
- Added DEFVAL for object traceRouteCtlTrapGeneration
of DEFVAL { { } }"
REVISION "200009210000Z" -- 21 September 2000
DESCRIPTION
"Initial version, published as 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.
traceRouteMaxConcurrentRequests对象类型语法无符号32个单元“请求”最大访问读写状态当前说明“代理实现中允许的最大并发活动跟踪路由请求数。此对象的值为0表示有效的并发活动请求数没有限制。
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceeds the limit just imposed."
DEFVAL { 10 }
::= { traceRouteObjects 1 }
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceeds the limit just imposed."
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
traceRouteCtlEntry对象类型语法traceRouteCtlEntry MAX-ACCESS不可访问状态当前描述
"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 3415, VACM) and that 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."
INDEX {
traceRouteCtlOwnerIndex,
traceRouteCtlTestName
}
::= { traceRouteCtlTable 1 }
"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 3415, VACM) and that 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."
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,
traceRouteCtlSourceAddress InetAddress,
traceRouteCtlIfIndex InterfaceIndexOrZero,
traceRouteCtlMiscOptions SnmpAdminString,
traceRouteCtlMaxFailures Unsigned32,
traceRouteCtlDontFragment TruthValue,
traceRouteCtlInitialTtl Unsigned32,
traceRouteCtlFrequency Unsigned32,
traceRouteCtlStorageType StorageType,
traceRouteCtlAdminStatus INTEGER,
traceRouteCtlDescr SnmpAdminString,
traceRouteCtlMaxRows Unsigned32,
traceRouteCtlTrapGeneration BITS,
traceRouteCtlCreateHopsEntries TruthValue,
traceRouteCtlType OBJECT IDENTIFIER,
traceRouteCtlRowStatus RowStatus
}
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,
traceRouteCtlDescr SnmpAdminString,
traceRouteCtlMaxRows Unsigned32,
traceRouteCtlTrapGeneration BITS,
traceRouteCtlCreateHopsEntries TruthValue,
traceRouteCtlType OBJECT IDENTIFIER,
traceRouteCtlRowStatus RowStatus
}
traceRouteCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32))
traceRouteCtlOwnerIndex对象类型语法SnmpAdminString（大小（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 3415, VACM) for tables in which multiple users may need to create or modify entries independently, 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 defined in VACM, in accordance with a security policy.
MAX-ACCESS not ACCESS STATUS current DESCRIPTION“帮助安全管理员使用基于视图的访问控制模型（RFC 3415，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 a 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 a 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 { unknown }
::= { 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 { unknown }
::= { 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 examining the value of the corresponding traceRouteCtlTargetAddressType.
traceRouteCtlTargetAddress对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“指定在远程主机的跟踪路由请求上使用的主机地址。可以通过检查相应的跟踪路由CtlTargetAddressType的值来确定主机地址类型。
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 enable optional
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
interface was dropped by the routing daemon at the host)."
DEFVAL { false }
::= { traceRouteCtlEntry 5 }
traceRouteCtlByPassRouteTable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The purpose of this object is to enable optional
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
interface was dropped by the routing daemon at the host)."
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. If the RECOMMENDED traceroute method (UDP datagrams as probes) is used, then the value contained in this object MUST be applied. If another traceroute method is used for which the specified size is not appropriate, then the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size.
traceRouteCtlDataSize对象类型语法Unsigned32（0..65507）单位“八位字节”MAX-ACCESS read create STATUS current DESCRIPTION“指定跟踪路由请求的数据部分大小，以八位字节为单位。如果推荐的跟踪路由方法（UDP数据报作为探测）则必须应用此对象中包含的值。如果使用了另一个traceroute方法，但指定的大小不适合该方法，则实现应使用与指定大小最接近的大小（适合该方法）。
The maximum value for this object was computed by
subtracting the smallest possible IP header size of
20 octets (IPv4 header with no options) and the UDP
header size of 8 octets from the maximum IP packet size.
An IP packet has a maximum size of 65535 octets
(excluding IPv6 Jumbograms)."
DEFVAL { 0 }
::= { traceRouteCtlEntry 6 }
The maximum value for this object was computed by
subtracting the smallest possible IP header size of
20 octets (IPv4 header with no options) and the UDP
header size of 8 octets from the maximum IP packet size.
An IP packet has a maximum size of 65535 octets
(excluding IPv6 Jumbograms)."
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 (initial) UDP port to send the traceroute
request to. A port needs to be specified 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 }
traceRouteCtlPort OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "UDP Port"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the (initial) UDP port to send the traceroute
request to. A port needs to be specified 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"
traceRouteCtlMaxTtl对象类型语法Unsigned32（1..255）单位“生存时间值”
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum time-to-live value."
DEFVAL { 30 }
::= { traceRouteCtlEntry 10 }
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
traceRouteCtlDSField对象类型语法Unsigned32（0..255）MAX-ACCESS读取创建状态当前
DESCRIPTION "Specifies the value to store in the Type of Service (TOS) octet in the IPv4 header or in the Traffic Class octet in the IPv6 header, respectively, of the IP packet used to encapsulate the traceroute probe.
DESCRIPTION“指定分别存储在用于封装跟踪路由探测的IP数据包的IPv4报头中的服务类型（TOS）八位字节或IPv6报头中的流量类八位字节中的值。
The octet to be set in the IP header contains the Differentiated Services (DS) Field in the six most significant bits.
要在IP报头中设置的八位字节在六个最高有效位中包含区分服务（DS）字段。
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. 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 and RFC 3260 for guidance on usage of
this field."
REFERENCE
"Refer to RFC 1812 for the definition of the IPv4 TOS
octet and to RFC 2460 for the definition of the IPv6
Traffic Class octet. Refer to RFC 2474 and RFC 3260
for the definition of the Differentiated Services Field."
DEFVAL { 0 }
::= { traceRouteCtlEntry 11 }
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. 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 and RFC 3260 for guidance on usage of
this field."
REFERENCE
"Refer to RFC 1812 for the definition of the IPv4 TOS
octet and to RFC 2460 for the definition of the IPv6
Traffic Class octet. Refer to RFC 2474 and RFC 3260
for the definition of the Differentiated Services Field."
DEFVAL { 0 }
::= { traceRouteCtlEntry 11 }
traceRouteCtlSourceAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of the source address,
traceRouteCtlSourceAddress, to be used at a remote host
when a traceroute operation is performed."
DEFVAL { unknown }
::= { traceRouteCtlEntry 12 }
traceRouteCtlSourceAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of the source address,
traceRouteCtlSourceAddress, to be used at a remote host
when a traceroute operation is performed."
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 select the address
to be used. 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.
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of traceRouteCtlSourceAddressType."
DEFVAL { ''H }
::= { traceRouteCtlEntry 13 }
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 select the address
to be used. 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.
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
"Enables an application to specify implementation-dependent
options."
DEFVAL { ''H }
::= { traceRouteCtlEntry 15 }
traceRouteCtlMiscOptions OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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
traceRouteCtlMaxFailures对象类型语法Unsigned32（0..255）单位“超时”最大访问读取创建状态当前描述
"The value of this object indicates the maximum number
of consecutive timeouts allowed before a remote traceroute
request is terminated. A value of either 255 (maximum
hop count/possible TTL value) or 0 indicates that the
function of terminating a remote traceroute request when a
specific number of consecutive timeouts are detected is
disabled."
DEFVAL { 5 }
::= { traceRouteCtlEntry 16 }
"The value of this object indicates the maximum number
of consecutive timeouts allowed before a remote traceroute
request is terminated. A value of either 255 (maximum
hop count/possible TTL value) or 0 indicates that the
function of terminating a remote traceroute request when a
specific number of consecutive 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
a manual PATH MTU test is performed."
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
a manual PATH MTU test is performed."
DEFVAL { false }
::= { traceRouteCtlEntry 17 }
traceRouteCtlInitialTtl OBJECT-TYPE
SYNTAX Unsigned32 (1..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 (1..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 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.
traceRouteCtlFrequency对象类型语法Unsigned32个单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“重复跟踪路由测试之前等待的秒数，由相应行中各种对象的值定义。
After a single test is completed the number of seconds as defined by the value of traceRouteCtlFrequency MUST elapse before the next traceroute test is started.
单个测试完成后，在开始下一个跟踪路由测试之前，必须经过由traceRouteCtlFrequency值定义的秒数。
A value of 0 for this object implies that the test as defined by the corresponding entry will not be
此对象的值为0意味着由相应条目定义的测试将不会被执行
repeated."
DEFVAL { 0 }
::= { traceRouteCtlEntry 19 }
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 {
traceRouteCtlAdminStatus对象类型语法整数{
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:
已启用（1），--应启动操作已禁用（2）--应停止操作}MAX-ACCESS read create STATUS current DESCRIPTION“反映了traceRouteCtlEntry应处于的所需状态：
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."
DEFVAL { disabled }
::= { traceRouteCtlEntry 21 }
Refer to the corresponding traceRouteResultsOperStatus to
determine the operational state of the test defined by
this entry."
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 { ''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 { ''H }
::= { traceRouteCtlEntry 22 }
traceRouteCtlMaxRows OBJECT-TYPE SYNTAX Unsigned32 UNITS "rows" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of corresponding entries allowed in the traceRouteProbeHistoryTable. An implementation of this MIB will remove the oldest corresponding entry in the traceRouteProbeHistoryTable to allow the addition of an new entry once the number of corresponding 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.
A value of 0 for this object disables creation of
traceRouteProbeHistoryTable entries."
DEFVAL { 50 }
::= { traceRouteCtlEntry 23 }
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.
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 whether 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 whether 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 an empty set, indicating that none of the above options has been selected."
此对象的值默认为空集，表示未选择任何上述选项。”
DEFVAL { { } }
::= { traceRouteCtlEntry 24 }
DEFVAL { { } }
::= { 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 to select the implementation method to be used for performing a traceroute operation. The value of this object may be selected from traceRouteImplementationTypeDomains.
TracerOuteCltType对象类型语法对象标识符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,
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,
not beneath traceRouteImplementationTypeDomains."
DEFVAL { traceRouteUsingUdpProbes }
::= { traceRouteCtlEntry 26 }
traceRouteCtlRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the traceRouteCtlTable. Deletion of an entry in this table results in a deletion of all corresponding (same traceRouteCtlOwnerIndex and traceRouteCtlTestName index values) traceRouteResultsTable, traceRouteProbeHistoryTable, and traceRouteHopsTable entries.
traceRouteCtlRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在traceRouteCtlTable中创建和删除条目。删除此表中的条目会导致删除所有相应的（相同的traceRouteCtlOwnerIndex和traceRouteCtlTestName索引值）traceRouteResultsTable、traceRouteProbeHistoryTable和traceRouteHopsTable条目。
A value MUST be specified for traceRouteCtlTargetAddress prior to acceptance of a transition to active(1) state.
在接受转换到活动（1）状态之前，必须为TracerOuteCtTargetAddress指定一个值。
When a value for pingCtlTargetAddress is set, the value of object pingCtlRowStatus changes from notReady(3) to notInService(2).
设置pingCtlTargetAddress的值时，对象pingCtlRowStatus的值将从notReady（3）更改为notInService（2）。
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).
当通过将traceRouteCtlAdminStatus对象成功转换为enabled（1）启动traceRouteCtlEntry时，将向TracerOutResultsTable添加一个条目。
If the object traceRouteCtlAdminStatus already has the value enabled(1), and if the corresponding traceRouteResultsOperStatus object has the value completed(3), then successfully writing enabled(1) to the object traceRouteCtlAdminStatus re-initializes the already existing entry in the traceRouteResultsTable. The values of objects in the re-initialized entry are the same as the values of objects in a new entry would be.
如果对象traceRouteCtlAdminStatus已启用值（1），并且相应的TracerOutResultsOperatStatus对象已完成值（3），则成功将启用值（1）写入对象traceRouteCtlAdminStatus将重新初始化TracerOutResultsTable中已存在的条目。重新初始化的条目中的对象值与新条目中的对象值相同。
An entry is removed from the traceRouteResultsTable when
当发生以下情况时，将从traceroutResultsTable中删除一个条目：
its corresponding traceRouteCtlEntry is deleted."
::= { traceRouteObjects 3 }
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 so that a traceRouteResultsEntry
corresponds 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 so that a traceRouteResultsEntry
corresponds 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 Gauge32,
traceRouteResultsTestSuccesses Gauge32,
traceRouteResultsLastGoodPath DateAndTime
}
TraceRouteResultsEntry ::=
SEQUENCE {
traceRouteResultsOperStatus INTEGER,
traceRouteResultsCurHopCount Gauge32,
traceRouteResultsCurProbeCount Gauge32,
traceRouteResultsIpTgtAddrType InetAddressType,
traceRouteResultsIpTgtAddr InetAddress,
traceRouteResultsTestAttempts Gauge32,
traceRouteResultsTestSuccesses Gauge32,
traceRouteResultsLastGoodPath DateAndTime
}
traceRouteResultsOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- test is in progress
disabled(2), -- test has stopped
completed(3) -- test is completed
}
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
completed(3) -- test is completed
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an traceRouteCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
completed(3) - Test is completed."
::= { traceRouteResultsEntry 1 }
enabled(1) - Test is active.
disabled(2) - Test has stopped.
completed(3) - Test is completed."
::= { traceRouteResultsEntry 1 }
traceRouteResultsCurHopCount OBJECT-TYPE
TracerOutResultsCurhopCount对象类型
SYNTAX Gauge32
UNITS "hops"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the current TTL value (from 1 to
255) for a remote traceroute operation.
Maximum TTL value is determined by
traceRouteCtlMaxTtl."
::= { traceRouteResultsEntry 2 }
SYNTAX Gauge32
UNITS "hops"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the current TTL value (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
TracerOutResultsIPTGTADDRTYPE对象类型语法InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the type of address stored
in the corresponding traceRouteResultsIpTgtAddr
object."
::= { traceRouteResultsEntry 4 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object 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 object 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 object 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
TracerOutResultsTestAttempts对象类型
SYNTAX Gauge32
UNITS "tests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of attempts to determine a path
to a target. The value of this object MUST be started
at 0."
::= { traceRouteResultsEntry 6 }
SYNTAX Gauge32
UNITS "tests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of attempts to determine a path
to a target. The value of this object MUST be started
at 0."
::= { traceRouteResultsEntry 6 }
traceRouteResultsTestSuccesses OBJECT-TYPE
SYNTAX Gauge32
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 Gauge32
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. A path is complete if responses
were received or timeout occurred for each hop on
the path; i.e., for each TTL value from the value
of the corresponding traceRouteCtlInitialTtl object
up to the end of the path or (if no reply from the
target IP address was received) up to the value of
the corresponding traceRouteCtlMaxTtl object."
::= { 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. A path is complete if responses
were received or timeout occurred for each hop on
the path; i.e., for each TTL value from the value
of the corresponding traceRouteCtlInitialTtl object
up to the end of the path or (if no reply from the
target IP address was received) up to the value of
the corresponding traceRouteCtlMaxTtl object."
::= { 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
此MIB的实现将删除最旧的
entry in the traceRouteProbeHistoryTable of the
corresponding entry in the traceRouteCtlTable to allow
the addition of a new entry once the number of rows in
the traceRouteProbeHistoryTable reaches the value specified
by traceRouteCtlMaxRows for the corresponding entry in the
traceRouteCtlTable."
::= { traceRouteObjects 4 }
entry in the traceRouteProbeHistoryTable of the
corresponding entry in the traceRouteCtlTable to allow
the addition of a new entry once the number of rows in
the traceRouteProbeHistoryTable reaches the value specified
by traceRouteCtlMaxRows for the corresponding entry in the
traceRouteCtlTable."
::= { traceRouteObjects 4 }
traceRouteProbeHistoryEntry OBJECT-TYPE SYNTAX TraceRouteProbeHistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines a table for storing the results of a traceroute operation. Entries in this table are limited by the value of the corresponding traceRouteCtlMaxRows object.
traceRouteProbeHistoryEntry对象类型语法traceRouteProbeHistoryEntry MAX-ACCESS不可访问状态当前描述”定义用于存储跟踪路由操作结果的表。此表中的条目受相应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
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 }
}
::= { 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
traceRouteProbeHistoryIndex对象类型
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.
语法Unsigned32（1..'ffffffff'h）MAX-ACCESS不可访问状态当前描述“当确定跟踪路由探测的结果时，将创建此表中的一个条目。初始的2个实例标识符索引值标识探测结果（traceRouteProbeHistoryEntry）的跟踪路由Ctlentry属于。删除相应的跟踪项时，将从此表中删除该项。
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)."
::= { traceRouteProbeHistoryEntry 1 }
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)."
::= { traceRouteProbeHistoryEntry 1 }
traceRouteProbeHistoryHopIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates which hop in a traceroute path 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 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
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 }
traceRouteProbeHistoryResponse 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."
::= { 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
traceRouteProbeHistoryLastRC对象类型语法整数32 MAX-ACCESS只读
STATUS current DESCRIPTION "The last implementation-method-specific reply code received.
STATUS current DESCRIPTION“收到的最后一个特定于实施方法的回复代码。
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's results were determined."
::= { traceRouteProbeHistoryEntry 9 }
traceRouteProbeHistoryTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Timestamp for when this probe's results were determined."
::= { traceRouteProbeHistoryEntry 9 }
-- Traceroute Hop Results Table
--跟踪路由跃点结果表
traceRouteHopsTable OBJECT-TYPE
SYNTAX SEQUENCE OF TraceRouteHopsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Remote Operations Traceroute Hop Table for
keeping track of the results of traceroute tests on a
per-hop basis."
::= { traceRouteObjects 5 }
traceRouteHopsTable OBJECT-TYPE
SYNTAX SEQUENCE OF TraceRouteHopsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
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
}
traceRouteHopsEntry OBJECT-TYPE
SYNTAX TraceRouteHopsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the traceRouteHopsTable.
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 }
::= { traceRouteHopsTable 1 }
TraceRouteHopsEntry ::=
SEQUENCE {
traceRouteHopsHopIndex Unsigned32,
traceRouteHopsIpTgtAddressType InetAddressType,
traceRouteHopsIpTgtAddress InetAddress,
traceRouteHopsMinRtt Unsigned32,
traceRouteHopsMaxRtt Unsigned32,
traceRouteHopsAverageRtt Unsigned32,
traceRouteHopsRttSumOfSquares Unsigned32,
TraceRouteHopsEntry ::=
SEQUENCE {
traceRouteHopsHopIndex Unsigned32,
traceRouteHopsIpTgtAddressType InetAddressType,
traceRouteHopsIpTgtAddress InetAddress,
traceRouteHopsMinRtt Unsigned32,
traceRouteHopsMaxRtt Unsigned32,
traceRouteHopsAverageRtt Unsigned32,
traceRouteHopsRttSumOfSquares Unsigned32,
traceRouteHopsSentProbes Unsigned32, traceRouteHopsProbeResponses Unsigned32, traceRouteHopsLastGoodProbe DateAndTime }
tracerouthopsentprobes Unsigned32，tracerouthopsproberesponses Unsigned32，tracerouthopsslastgoodprobe DateAndTime}
traceRouteHopsHopIndex OBJECT-TYPE SYNTAX Unsigned32 (1..'ffffffff'h) 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 be given increasing values for subsequent hops. The value of traceRouteHopsHopIndex is not necessarily the number of the hop on the traced path.
traceRouteHopsHopIndex对象类型语法Unsigned32（1..'ffffffff'h）MAX-ACCESS不可访问状态当前描述“指定跟踪路由跃点的跃点索引。对于相同的traceRouteCtlOwnerIndex和traceRouteCtlTestName，此对象的值必须从1开始，并为后续跃点提供递增的值。traceRouteHopsHopIndex的值不一定是跟踪路径上的跃点数。
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 is completed. Care needs to be applied when a path
either 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 is completed. Care needs to be applied when a path
either 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 object indicates the type of address stored
in the corresponding traceRouteHopsIpTgtAddress
object."
::= { traceRouteHopsEntry 2 }
traceRouteHopsIpTgtAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the type of address stored
in the corresponding traceRouteHopsIpTgtAddress
object."
::= { traceRouteHopsEntry 2 }
traceRouteHopsIpTgtAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object reports the IP address associated with
traceRouteHopsIpTgtAddress对象类型语法InetAddress MAX-ACCESS只读状态当前描述“此对象报告与
the hop. A value for this object should be reported as a numeric IP address, not as a DNS name.
跳跃。此对象的值应报告为数字IP地址，而不是DNS名称。
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingCtlSourceAddressType."
::= { traceRouteHopsEntry 3 }
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of pingCtlSourceAddressType."
::= { 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
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 }
traceRouteHopsMaxRtt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
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 the squares of all
round-trip-times 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 the squares of all
round-trip-times received for this hop. Its purpose is
to enable standard deviation calculation."
::= { traceRouteHopsEntry 7 }
traceRouteHopsSentProbes OBJECT-TYPE
tracerouthopsentprobe对象类型
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 }
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
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time at which the last response was received for a
probe for this hop during this traceroute test."
::= { traceRouteHopsEntry 10 }
traceRouteHopsLastGoodProbe OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Date and time at which 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
traceRouteTestFailed通知类型对象{TracerOuteTlTargetAddressType，TracerOuteTlTargetAddress，traceRouteResultsIpTgtAddrType，traceRouteResultsIpTgtAddr
}
STATUS current
DESCRIPTION
"Could not determine the path to a target."
::= { traceRouteNotifications 2 }
}
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
--合规声明
traceRouteFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
fully implement the DISMAN-TRACEROUTE-MIB."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteMinimumGroup,
traceRouteCtlRowStatusGroup,
traceRouteHistoryGroup
}
traceRouteFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
fully implement the DISMAN-TRACEROUTE-MIB."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteMinimumGroup,
traceRouteCtlRowStatusGroup,
traceRouteHistoryGroup
}
GROUP traceRouteHopsTableGroup DESCRIPTION "This group lists the objects that make up a traceRouteHopsEntry. Support of the traceRouteHopsTable is optional."
GROUP traceRouteHopsTableGroup DESCRIPTION“此组列出组成traceRouteHopsEntry的对象。对traceRouteHopsTable的支持是可选的。”
GROUP traceRouteNotificationsGroup DESCRIPTION
组跟踪路由通知组描述
"This group defines a collection of optional notifications."
“此组定义可选通知的集合。”
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 "Write access to 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 traceRouteCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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 traceRouteCtlSourceAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access to 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."
对象TracerOuteClSourceAddressType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}MIN-ACCESS只读说明“无法将发送套接字与源地址绑定的实现不需要对此对象的写访问权限。只需要支持ipv4和ipv6地址的实现。”
OBJECT traceRouteCtlSourceAddress SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "Write access to 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."
OBJECT TracerOuteClSourceAddress语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“无法将发送套接字与源地址绑定的实现不需要对此对象的写访问权限。只需要支持IPv4和IPv6地址的实现。”
OBJECT traceRouteCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. If write access is
对象traceRouteCtlIfIndex最小访问只读描述“不需要写访问。如果需要写访问
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."
不支持，返回0作为此对象的值。值为0表示不支持此选项表示的函数。”
OBJECT traceRouteCtlMiscOptions MIN-ACCESS read-only DESCRIPTION "Support of this object is optional. If 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 that implementations support only the volatile(2) StorageType enumeration."
对象跟踪路由CTLStorageType MIN-ACCESS只读描述“不需要写访问。还允许实现仅支持volatile（2）StorageType枚举。”
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."
对象tracerouteclttype MIN-ACCESS只读说明“不需要写访问权限。此外，建议实现支持的唯一值是tracerouteusingudpprobe。”
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 traceRouteResultsLastGoodPath DESCRIPTION "If the traceRouteHopsTableGroup is implemented, then this object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
对象traceroutResultsLastGoodPath描述“如果实现了TracerOutshopStableGroup，那么对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。“
OBJECT traceRouteProbeHistoryHAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
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."
描述“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteProbeHistoryHAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由ProbeHistoryAddr语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteProbeHistoryTime DESCRIPTION "This object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT TracerOutProbeHistorytime DESCRIPTION“对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
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."
对象跟踪路由SIPTGTAddress语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteHopsLastGoodProbe DESCRIPTION "This object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT TracerOutHopSlastGoodProbe DESCRIPTION“对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
::= { traceRouteCompliances 2 }
::= { traceRouteCompliances 2 }
traceRouteMinimumCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The minimum compliance statement for SNMP entities which implement the minimal subset of the DISMAN-TRACEROUTE-MIB. Implementors might choose this subset for small devices with limited resources." MODULE -- this module
TracerOuteMimumCompliance MODULE-COMPLIANCE STATUS当前描述“实现DISAN-TRACEROUTE-MIB最小子集的SNMP实体的最小符合性声明。实现者可以为资源有限的小型设备选择此子集。”模块--此模块
MANDATORY-GROUPS { traceRouteMinimumGroup }
强制组{traceroutemimumgroup}
GROUP traceRouteCtlRowStatusGroup DESCRIPTION "A compliant implementation does not have to implement the traceRouteCtlRowStatusGroup."
GROUP TracerOuteClRowStatusGroup DESCRIPTION“符合要求的实现不必实现TracerOuteClRowStatusGroup。”
GROUP traceRouteHistoryGroup DESCRIPTION "A compliant implementation does not have to implement the traceRouteHistoryGroup."
GROUP traceRouteHistoryGroup DESCRIPTION“符合要求的实现不必实现traceRouteHistoryGroup。”
GROUP traceRouteHopsTableGroup DESCRIPTION "This group lists the objects that make up a traceRouteHopsEntry. Support of the traceRouteHopsTable is optional."
GROUP traceRouteHopsTableGroup DESCRIPTION“此组列出组成traceRouteHopsEntry的对象。对traceRouteHopsTable的支持是可选的。”
GROUP traceRouteNotificationsGroup DESCRIPTION "This group defines a collection of optional notifications."
GROUP TracerOutNotificationsGroup DESCRIPTION“此组定义可选通知的集合。”
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 "Write access is not required. If write access is not supported, return a false(2) as the value of this object. A value of false(2) means that the function represented by this option is not supported."
OBJECT TraceRouteTable MIN-ACCESS只读描述“不需要写访问权限。如果不支持写访问权限，则返回false（2）作为此对象的值。false（2）表示不支持此选项表示的函数。”
OBJECT traceRouteCtlDSField MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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 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 "Write access to 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
对象TracerOuteClSourceAddress语法InetAddress（大小（0 | 4 | 16））最小访问只读
DESCRIPTION "Write access to 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 traceRouteCtlIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. If 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. If 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 traceRouteCtlDontFragment MIN-ACCESS read-only DESCRIPTION "Write access is not required. If write access is not supported, return a false(2) as the value of this object. A value of false(2) means that the function represented by this option is not supported."
OBJECT TracerOuteCltDontFragment MIN-ACCESS只读描述“不需要写访问。如果不支持写访问，则返回false（2）作为此对象的值。false（2）表示不支持此选项表示的函数。”
OBJECT traceRouteCtlInitialTtl MIN-ACCESS read-only DESCRIPTION "Write access is not required. If write access is not supported, return a 1 as the value of this object."
对象traceRouteCtlInitialTtl MIN-ACCESS只读说明“不需要写访问。如果不支持写访问，请将1作为此对象的值返回。”
OBJECT traceRouteCtlFrequency MIN-ACCESS read-only DESCRIPTION
对象跟踪器最小访问频率只读描述
"Write access is not required. If 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."
不需要写访问。如果不支持写访问，则返回0作为此对象的值。值0表示不支持此选项表示的函数
OBJECT traceRouteCtlStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required. It is also allowed that implementations support only the volatile(2) StorageType enumeration."
对象跟踪路由CTLStorageType MIN-ACCESS只读描述“不需要写访问。还允许实现仅支持volatile（2）StorageType枚举。”
OBJECT traceRouteCtlDescr MIN-ACCESS read-only DESCRIPTION "The agent is not required to support set operations to this object."
OBJECT traceRouteCtlDescr MIN-ACCESS只读说明“代理不需要支持对此对象的设置操作。”
OBJECT traceRouteCtlMaxRows MIN-ACCESS read-only DESCRIPTION "Write access is not required. If the traceRouteHistoryGroup is not implemented, then write access to this object MUST be disabled, and the object MUST return a value of 0 when retrieved."
对象traceRouteCtlMaxRows MIN-ACCESS只读说明“不需要写访问。如果未实现traceRouteHistoryGroup，则必须禁用对此对象的写访问，并且检索对象时必须返回值0。”
OBJECT traceRouteCtlTrapGeneration MIN-ACCESS read-only DESCRIPTION "Write access is not required. If the traceRouteNotificationsGroup is not implemented, then write access to this object MUST be disabled, and the object MUST return a value with no bit set when retrieved. No bit set indicates that no notification is generated."
对象TracerOuteCttrapGeneration MIN-ACCESS只读说明“不需要写访问。如果没有实现TracerOutNotificationsGroup，则必须禁用对此对象的写访问，并且检索对象时必须返回一个未设置位的值。未设置位表示未生成通知。”
OBJECT traceRouteCtlCreateHopsEntries MIN-ACCESS read-only DESCRIPTION "Write access is not required. If the traceRouteHopsTableGroup is not implemented, then write access to this object MUST be disabled, and the object MUST return a value of false(2) when retrieved."
对象TracerOuteClCreateHopSentries MIN-ACCESS只读描述“不需要写访问权限。如果没有实现traceRouteHopsTableGroup，则必须禁用对此对象的写访问权限，并且检索对象时必须返回false（2）值。”
OBJECT traceRouteCtlType MIN-ACCESS read-only DESCRIPTION "Write access is not required. In addition, the only
对象traceRouteCtlType MIN-ACCESS只读说明“不需要写访问权限。此外，只有
value that is RECOMMENDED to be supported by an implementation is traceRouteUsingUdpProbes."
建议实现支持的值是TracerOutUsingUpProbe。“
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 traceRouteResultsLastGoodPath DESCRIPTION "This object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT TracerOutResultsLastGoodPath DESCRIPTION“对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
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."
对象跟踪路由ProbeHistoryHaddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现应仅支持此对象的ipv4和全局唯一ipv6地址值。”
OBJECT traceRouteProbeHistoryHAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由ProbeHistoryAddr语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteProbeHistoryTime DESCRIPTION "If the traceRouteHistoryGroup is implemented, then this object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
OBJECT traceRouteProbeHistoryTime DESCRIPTION“如果实现了traceRouteHistoryGroup，则此对象对于能够访问系统时钟并能够设置DateAndTime对象值的实现是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。”
OBJECT traceRouteHopsIpTgtAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation should only support IPv4 and
对象跟踪路由SIPTGTADDessType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现应仅支持ipv4和ipv6
globally unique IPv6 address values for this object."
此对象的全局唯一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."
对象跟踪路由SIPTGTAddress语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteHopsLastGoodProbe DESCRIPTION "If the traceRouteHopsTableGroup is implemented, then this object is mandatory for implementations that have access to a system clock and that are capable of setting the values for DateAndTime objects. It is RECOMMENDED that when this object is not supported its values be reported as '0000000000000000'H."
对象跟踪outHopSlastGoodProbe描述“如果实现了TracerOutshopStableGroup，那么对于能够访问系统时钟并能够设置DateAndTime对象值的实现，此对象是必需的。建议在不支持此对象时，将其值报告为“0000000000000000”H。“
::= { traceRouteCompliances 3 }
::= { traceRouteCompliances 3 }
traceRouteCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for the DISMAN-TRACEROUTE-MIB.
This compliance statement has been deprecated because
the traceRouteGroup and the traceRouteTimeStampGroup
have been split and deprecated. The
traceRouteFullCompliance is semantically identical to the
deprecated traceRouteCompliance statement."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteGroup
}
GROUP traceRouteTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and that are capable of setting
the values for DateAndTime objects."
traceRouteCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for the DISMAN-TRACEROUTE-MIB.
This compliance statement has been deprecated because
the traceRouteGroup and the traceRouteTimeStampGroup
have been split and deprecated. The
traceRouteFullCompliance is semantically identical to the
deprecated traceRouteCompliance statement."
MODULE -- this module
MANDATORY-GROUPS {
traceRouteGroup
}
GROUP traceRouteTimeStampGroup
DESCRIPTION
"This group is mandatory for implementations that have
access to a system clock and that 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 that implementations 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."
对象tracerouteclttype MIN-ACCESS只读说明“不需要写访问权限。此外，建议实现支持的唯一值是tracerouteusingudpprobe。”
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."
对象跟踪路由ProbeHistoryHaddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现应仅支持此对象的ipv4和全局唯一ipv6地址值。”
OBJECT traceRouteProbeHistoryHAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation should only support IPv4 and globally unique IPv6 address values for this object."
对象跟踪路由ProbeHistoryAddr语法InetAddress（大小（0 | 4 | 16））说明“实现应仅支持此对象的IPv4和全局唯一IPv6地址值。”
OBJECT traceRouteHopsIpTgtAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
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."
描述“实现应仅支持此对象的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分组
traceRouteMinimumGroup OBJECT-GROUP OBJECTS { traceRouteMaxConcurrentRequests, traceRouteCtlTargetAddressType, traceRouteCtlTargetAddress, traceRouteCtlByPassRouteTable, traceRouteCtlDataSize, traceRouteCtlTimeOut, traceRouteCtlProbesPerHop, traceRouteCtlPort, traceRouteCtlMaxTtl, traceRouteCtlDSField, traceRouteCtlSourceAddressType, traceRouteCtlSourceAddress, traceRouteCtlIfIndex, traceRouteCtlMiscOptions, traceRouteCtlMaxFailures, traceRouteCtlDontFragment, traceRouteCtlInitialTtl, traceRouteCtlFrequency, traceRouteCtlStorageType, traceRouteCtlAdminStatus, traceRouteCtlMaxRows, traceRouteCtlTrapGeneration, traceRouteCtlDescr, traceRouteCtlCreateHopsEntries, traceRouteCtlType, traceRouteResultsOperStatus, traceRouteResultsCurHopCount, traceRouteResultsCurProbeCount, traceRouteResultsIpTgtAddrType, traceRouteResultsIpTgtAddr, traceRouteResultsTestAttempts, traceRouteResultsTestSuccesses, traceRouteResultsLastGoodPath
TracerOuteMimumGroup对象组对象{traceRouteMaxConcurrentRequests、tracerouteCtTargetAddressType、tracerouteCtTargetAddress、tracerouteCtBypassRouteTable、tracerouteCtDataSize、tracerouteCtTimeout、tracerouteCtProbesPerhop、tracerouteCtPort、tracerouteCtMaxTTL、tracerouteCtLdField、tracerouteCtSourceAddressType、traceRouteCtlSourceAddress、tracerouteCtIfindex、traceRoUTECTLMISCHOPTIONS、TRACETROUTECTLMAXFAILURES、TRACETROUTECTLDONTFRAPTENT、TRACETROUTECTLinitialTTL、TRACETROUTECTLFORCENCE、TRACETROUTECTLSTOAGENT、TRACETROUTECTLMAXROWS、TRACETROUTECTLTRAPGGENERATION、TRACETROUTECTLDESCREATEHOPSENTRIES、TRACERTOUTECTLROUTECTRESULTSCURCHOPCOunt，traceroutResultsCurProbeCount，traceroutResultsIPTGTAddrType，traceroutResultsIPTGTAddr，traceroutResultsTestAttempts，traceroutResultsTestSuccessfulls，traceroutResultsLastGoodPath
}
STATUS current
DESCRIPTION
"The group of objects that constitute the remote traceroute
operation."
::= { traceRouteGroups 5 }
}
STATUS current
DESCRIPTION
"The group of objects that constitute the remote traceroute
operation."
::= { traceRouteGroups 5 }
traceRouteCtlRowStatusGroup OBJECT-GROUP
OBJECTS {
traceRouteCtlRowStatus
}
STATUS current
DESCRIPTION
"The RowStatus object of the traceRouteCtlTable."
::= { traceRouteGroups 6 }
traceRouteCtlRowStatusGroup OBJECT-GROUP
OBJECTS {
traceRouteCtlRowStatus
}
STATUS current
DESCRIPTION
"The RowStatus object of the traceRouteCtlTable."
::= { traceRouteGroups 6 }
traceRouteHistoryGroup OBJECT-GROUP
OBJECTS {
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC,
traceRouteProbeHistoryTime
}
traceRouteHistoryGroup OBJECT-GROUP
OBJECTS {
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC,
traceRouteProbeHistoryTime
}
STATUS current
DESCRIPTION
"The group of objects that constitute the history
capability."
::= { traceRouteGroups 7 }
STATUS current
DESCRIPTION
"The group of objects that constitute the history
capability."
::= { traceRouteGroups 7 }
traceRouteNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
traceRoutePathChange,
traceRouteTestFailed,
traceRouteTestCompleted
}
STATUS current
DESCRIPTION
"The notifications that are required to be supported by
implementations of this MIB."
::= { traceRouteGroups 3 }
traceRouteNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
traceRoutePathChange,
traceRouteTestFailed,
traceRouteTestCompleted
}
STATUS current
DESCRIPTION
"The notifications that are required to be supported by
implementations of this MIB."
::= { traceRouteGroups 3 }
traceRouteHopsTableGroup OBJECT-GROUP OBJECTS { traceRouteHopsIpTgtAddressType, traceRouteHopsIpTgtAddress,
traceRouteHopsTableGroup对象组对象{traceRouteHopsIpTgtAddressType，traceRouteHopsIpTgtAddress，
traceRouteHopsMinRtt,
traceRouteHopsMaxRtt,
traceRouteHopsAverageRtt,
traceRouteHopsRttSumOfSquares,
traceRouteHopsSentProbes,
traceRouteHopsProbeResponses,
traceRouteHopsLastGoodProbe
}
STATUS current
DESCRIPTION
"The group of objects that constitute the
traceRouteHopsTable."
::= { traceRouteGroups 4 }
traceRouteHopsMinRtt,
traceRouteHopsMaxRtt,
traceRouteHopsAverageRtt,
traceRouteHopsRttSumOfSquares,
traceRouteHopsSentProbes,
traceRouteHopsProbeResponses,
traceRouteHopsLastGoodProbe
}
STATUS current
DESCRIPTION
"The group of objects that constitute the
traceRouteHopsTable."
::= { traceRouteGroups 4 }
traceRouteGroup OBJECT-GROUP OBJECTS { traceRouteMaxConcurrentRequests, traceRouteCtlTargetAddressType, traceRouteCtlTargetAddress, traceRouteCtlByPassRouteTable, 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,
traceRouteGroup对象组对象{traceRouteMaxConcurrentRequests、tracerouteCtTargetAddressType、tracerouteCtTargetAddress、tracerouteCtBypassRouteTable、tracerouteCtDataSize、tracerouteCtTimeout、tracerouteCtProbesPerhop、tracerouteCtPort、tracerouteCtMaxTTL、tracerouteCtLdField、tracerouteCtSourceAddressType、traceRouteCtlSourceAddress、tracerouteCtIfindex、traceRoUTECTLMISCHOPTIONS、TRACETROUTECTLMAXFAILURES、TRACETROUTECTLDONTFRAPTENT、TRACETROUTECTLinitialTTL、TRACETROUTECTLFORCENCE、TRACETROUTECTL存储类型、TRACETROUTECTLAdminStatus、TRACETROUTECTLMAXROWS、TRACETROUTECTLTRAPGGENERATION、TRACETROUTECTLDESCR、TRACECTLCCreateHopSentries、TRACETROUTECTLTYPE、TRACETROURaceRouteResultsCrhopCount、traceRouteResultsCurProbeCount、TraceRouteResultsIPTGAddRtype、TraceRouteResultsIPTGAddR、traceRouteResultsTestAttempts、，
traceRouteResultsTestSuccesses,
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC
}
STATUS deprecated
DESCRIPTION
"The group of objects that constitute the remote traceroute
operation."
::= { traceRouteGroups 1 }
traceRouteResultsTestSuccesses,
traceRouteProbeHistoryHAddrType,
traceRouteProbeHistoryHAddr,
traceRouteProbeHistoryResponse,
traceRouteProbeHistoryStatus,
traceRouteProbeHistoryLastRC
}
STATUS deprecated
DESCRIPTION
"The group of objects that constitute the remote traceroute
operation."
::= { traceRouteGroups 1 }
traceRouteTimeStampGroup OBJECT-GROUP
OBJECTS {
traceRouteResultsLastGoodPath,
traceRouteProbeHistoryTime
}
STATUS deprecated
DESCRIPTION
"The group of DateAndTime objects."
::= { traceRouteGroups 2 }
traceRouteTimeStampGroup OBJECT-GROUP
OBJECTS {
traceRouteResultsLastGoodPath,
traceRouteProbeHistoryTime
}
STATUS deprecated
DESCRIPTION
"The group of DateAndTime objects."
::= { traceRouteGroups 2 }
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 -- RFC3411 InetAddressType, InetAddress FROM INET-ADDRESS-MIB; -- RFC4001
从SNMPv2 SMI导入模块标识、对象类型、未签名32、mib-2、整数32——从SNMPv2 TC导入RFC2578行状态——从SNMPv2 CONF导入RFC2579模块符合性、对象组——从SNMP-FRAMEWORK-mib导入RFC2580 SNMPAdministring——从INET-ADDRESS-mib导入RFC3411 InetAddressType、从INET-ADDRESS-mib导入InetAddress；——RFC4001
lookupMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" -- 13 June 2006 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Juergen Quittek
lookupMIB模块标识最后更新“200606130000Z”-2006年6月13日组织“IETF分布式管理工作组”联系方式“Juergen Quitek”
NEC Europe Ltd. Network Laboratories Kurfuersten-Anlage 36 69115 Heidelberg Germany
NEC欧洲有限公司网络实验室Kurfuersten Anlage 36 69115德国海德堡
Phone: +49 6221 4342-115 Email: quittek@netlab.nec.de" 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.
电话：+49 6221 4342-115电子邮件：quittek@netlab.nec.de“说明”查找MIB（DISAN-NSLOOKUP-MIB）允许确定与主机地址对应的名称或与远程主机上的主机名关联的地址。
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2006年）。此版本的MIB模块是RFC 4560的一部分；有关完整的法律通知，请参见RFC本身。”
-- Revision history
--修订历史
REVISION "200606130000Z" -- 13 June 2006 DESCRIPTION "Updated version, published as RFC 4560. - Replaced references to RFC 2575 by RFC 3415 - Replaced references to RFC 2571 by RFC 3411 - Replaced references to RFC 2851 by RFC 4001 - Added value enabled(1) to SYNTAX clause of lookupCtlOperStatus - Added lookupMinimumCompliance - Defined semantics of value 0 for object lookupPurgeTime - Added DEFVAL { unknown } to object lookupCtlTargetAddressType OBJECT-TYPE"
修订版“200606130000Z”-2006年6月13日描述“更新版本，发布为RFC 4560。-将RFC 2575的参考替换为RFC 3415-将RFC 2571的参考替换为RFC 3411-将RFC 2851的参考替换为RFC 4001-启用增值（1）to lookupCtlOperStatus的语法子句-添加lookupMinimumCompliance-为对象lookupPurgeTime定义值0的语义-向对象lookupCtlTargetAddressType object-TYPE添加DEFVAL{unknown}”
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
lookupMaxConcurrentRequests对象类型
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.
SYNTAX Unsigned32 UNITS“requests”MAX-ACCESS read-write STATUS current DESCRIPTION“代理实现中允许的最大并发活动查找请求数。此对象的值为0表示对有效的并发活动请求数没有限制。
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceed the limit just imposed."
DEFVAL { 10 }
::= { lookupObjects 1 }
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceed the limit just imposed."
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 a lookupCtlEntry has been completed. A lookupCtEntry is considered complete when its lookupCtlOperStatus object has a value of completed(3).
lookupPurgeTime对象类型语法无符号32（0..86400）单位“秒”最大访问读写状态当前说明“lookupCtlEntry表示的查找操作完成后，自动删除lookupCtlTable中的条目和任何相关lookupResultsTable条目之前等待的时间量。lookupCtEntry的LookupCtOperStatus对象的值为completed（3）时，它被视为已完成。
A value of 0 indicates that automatic deletion
of entries is disabled."
DEFVAL { 900 } -- 15 minutes as default
::= { lookupObjects 2 }
A value of 0 indicates that automatic deletion
of entries is disabled."
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 for a symbolic host name or for a host address from a remote host."
lookupCtlTable对象类型LookupCtlEntry MAX-ACCESS不可访问状态的语法序列当前描述“定义查找控制表，用于提供对符号主机名或远程主机的主机地址执行查找操作的功能。”
::= { lookupObjects 3 }
::= { 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 a type of SnmpAdminString,
a textual convention that allows for the use of the SNMPv3
View-Based Access Control Model (RFC 3415, VACM)
and that also allows a management application to identify
its entries. The second index element,
lookupCtlOperationName, enables the same
lookupCtlOwnerIndex entity to have multiple outstanding
requests. The value of lookupCtlTargetAddressType
determines which lookup function to perform."
INDEX {
lookupCtlOwnerIndex,
lookupCtlOperationName
}
::= { lookupCtlTable 1 }
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 a type of SnmpAdminString,
a textual convention that allows for the use of the SNMPv3
View-Based Access Control Model (RFC 3415, VACM)
and that also allows a management application to identify
its entries. The second index element,
lookupCtlOperationName, enables the same
lookupCtlOwnerIndex entity to have multiple outstanding
requests. The value of lookupCtlTargetAddressType
determines which lookup function to perform."
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 create or modify entries independently, 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
lookupCtlOwnerIndex对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS not accessible STATUS current DESCRIPTION“帮助安全管理员使用基于视图的访问控制模型（RFC 2575，VACM）设置访问控制对于多个用户可能需要独立创建或修改条目的表，初始索引用作“所有者索引”。此类初始索引的语法为SnmpAdminString，因此可以简单地映射到
securityName or groupName defined in VACM, in accordance with a security policy.
根据安全策略在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."
::= { lookupCtlEntry 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."
::= { 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
lookupCtlTargetAddressType对象类型语法InetAddressType MAX-ACCESS读取创建状态当前
DESCRIPTION "Specifies the type of address for performing a lookup operation for a symbolic host name or for a host address from a remote host.
DESCRIPTION“指定用于对符号主机名或远程主机的主机地址执行查找操作的地址类型。
Specification of dns(16) as the value for this object
means that a function such as, for example, getaddrinfo()
or gethostbyname() should be performed to return one or
more numeric addresses. Use of a value of either ipv4(1)
or ipv6(2) means that a functions such as, for example,
getnameinfo() or gethostbyaddr() should be used to return
the symbolic names associated with a host."
DEFVAL { unknown }
::= { lookupCtlEntry 3 }
Specification of dns(16) as the value for this object
means that a function such as, for example, getaddrinfo()
or gethostbyname() should be performed to return one or
more numeric addresses. Use of a value of either ipv4(1)
or ipv6(2) means that a functions such as, for example,
getnameinfo() or gethostbyaddr() should be used to return
the symbolic names associated with a host."
DEFVAL { unknown }
::= { 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 lookupCtlTargetAddressType objects determines its type, as well as the function that can be requested.
lookupCtlTargetAddress对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“指定用于远程主机上解析程序查找的地址。相应的lookupCtlTargetAddressType对象确定其类型以及可以请求的函数。
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
SYNTAX INTEGER {
enabled(1), -- operation is active
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:
lookupCtlOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- operation is active
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 been 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 is completed (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 is completed (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
lookupCtlTime对象类型语法Unsigned32单位“毫秒”最大访问只读状态当前描述“报告在远程主机上完成查找操作所需的毫秒数。完成意味着操作失败以及
success."
::= { lookupCtlEntry 6 }
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 return the error codes that are
generated by the lookup function used."
::= { 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 return the error codes that are
generated by the lookup function used."
::= { 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 the acceptance of a transition to active(1) state. 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）状态之前，必须为lookupCtlTargetAddress指定一个值。远程查找操作在其条目第一次变为活动状态时开始（1）。进入和退出活动（1）状态的转换对远程查找操作的操作行为没有影响，但通过将该表的RowStatus对象设置为destroy（6）删除该表中的条目将停止活动的远程查找操作。
The operational state of a remote lookup operation can be determined by examination of its lookupCtlOperStatus object." REFERENCE
远程查找操作的操作状态可以通过检查其lookupCtlOperStatus对象来确定。“参考
"See definition of RowStatus in RFC 2579,
'Textual Conventions for SMIv2.'"
::= { lookupCtlEntry 8 }
"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, is completed 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 (returned by lookup function), or it can have more than one symbolic name (returned by lookup function).
远程主机可以是多主机，并且具有多个与其关联的IP地址（由查找函数返回），也可以具有多个符号名（由查找函数返回）。
A function such as, for example, getnameinfo() or gethostbyaddr() 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. If the function identifies an 'official host name,' then this symbolic name MUST be assigned a lookupResultsIndex of 1.
以主机地址作为参数调用函数，例如getnameinfo（）或gethostbyaddr（），主要用于确定要与主机地址关联的符号名。必须为返回的每个主机名创建lookupResultsTable中的条目。如果函数标识“正式主机名”，则必须为该符号名分配lookupResultsIndex 1。
A function such as, for example, getaddrinfo() or gethostbyname() is called with a symbolic host name and is used primarily to retrieve a host address. The entries
例如，使用符号主机名调用getaddrinfo（）或gethostbyname（）等函数，主要用于检索主机地址。参赛作品
MUST be stored in the order that they are retrieved from
the lookup function. lookupResultsIndex 1 MUST be
assigned to the first entry."
::= { lookupObjects 4 }
MUST be stored in the order that they are retrieved from
the lookup function. lookupResultsIndex 1 MUST be
assigned to the first entry."
::= { 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,
lookupResultsIndex
}
::= { lookupResultsTable 1 }
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,
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
consecutively."
::= { 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
consecutively."
::= { lookupResultsEntry 1 }
lookupResultsAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION
LookupResultsAdressType对象类型语法InetAddressType MAX-ACCESS只读状态当前说明
"Indicates the type of result of a remote lookup
operation. A value of unknown(0) implies either that
the operation hasn't been started or that
it has failed."
::= { lookupResultsEntry 2 }
"Indicates the type of result of a remote lookup
operation. A value of unknown(0) implies either that
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.
lookupResultsAddress对象类型语法InetAddress MAX-ACCESS只读状态当前描述”根据lookupResultsAddressType的值反映远程查找操作的结果。
The address type (InetAddressType) that relates to this object is specified by the corresponding value of lookupResultsAddress."
与此对象相关的地址类型（InetAddressType）由lookupResultsAddress的相应值指定。“
::= { lookupResultsEntry 3 }
::= { 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 SNMP entities that fully implement the DISMAN-NSLOOKUP-MIB." MODULE -- this module MANDATORY-GROUPS { lookupGroup }
lookupCompliance MODULE-COMPLIANCE STATUS当前描述“完全实现DISMAN-NSLOOKUP-MIB的SNMP实体的符合性声明。”模块--此模块为必填模块-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."
OBJECT lookupPurgeTime MIN-ACCESS只读说明“代理不需要支持此对象的设置操作。”
::= { lookupCompliances 1 }
::= { lookupCompliances 1 }
lookupMinimumCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The minimum compliance statement for SNMP entities that implement the minimal subset of the DISMAN-NSLOOKUP-MIB. Implementors might choose this subset for small devices with limited resources." MODULE -- this module MANDATORY-GROUPS { lookupGroup }
lookupMinimumCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“实现DISAN-NSLOOKUP-MIB最小子集的SNMP实体的最小符合性声明。实现者可以为资源有限的小型设备选择此子集。”MODULE--此模块为必填项-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."
OBJECT lookupPurgeTime MIN-ACCESS只读说明“代理不需要支持此对象的设置操作。”
OBJECT lookupCtlRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required. If write access is
not supported, then at least one entry in the
lookupCtlTable MUST be established already when the SNMP
agent starts offering access to the NSLOOKUP-MIB module.
If, in such a case, only a single entry is offered, then
it is RECOMMENDED that this entry use strings with a
length of 0 for both of its two index objects."
::= { lookupCompliances 2 }
OBJECT lookupCtlRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required. If write access is
not supported, then at least one entry in the
lookupCtlTable MUST be established already when the SNMP
agent starts offering access to the NSLOOKUP-MIB module.
If, in such a case, only a single entry is offered, then
it is RECOMMENDED that this entry use strings with a
length of 0 for both of its two index objects."
::= { lookupCompliances 2 }
-- MIB groupings
--MIB分组
lookupGroup OBJECT-GROUP OBJECTS { lookupMaxConcurrentRequests, lookupPurgeTime, lookupCtlOperStatus, lookupCtlTargetAddressType, lookupCtlTargetAddress, lookupCtlTime, lookupCtlRc, lookupCtlRowStatus,
lookupGroup对象组对象{lookupMaxConcurrentRequests，lookupPurgeTime，LookupCtlOpertStatus，lookupCtlTargetAddressType，lookupCtlTargetAddress，lookupCtlTime，lookupCtlRc，lookupCtlRowStatus，
lookupResultsAddressType,
lookupResultsAddress
}
STATUS current
DESCRIPTION
"The group of objects that constitute the remote
Lookup operation."
::= { lookupGroups 1 }
lookupResultsAddressType,
lookupResultsAddress
}
STATUS current
DESCRIPTION
"The group of objects that constitute the remote
Lookup operation."
::= { lookupGroups 1 }
END
终止
There are a number of management objects defined in the three MIB modules with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
在三个MIB模块中定义了许多管理对象，其中MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o pingMaxConcurrentRequests o traceRouteMaxConcurrentRequests o lookupMaxConcurrentRequests The MIB modules limit their maximum numbers of concurrent requests by the values of these objects. Unauthorized access to them may lead to an overload of the managed node and to a disruption of other functions of the managed node.
o pingMaxConcurrentRequests o TracerOutMaxConcurrentRequests o lookupMaxConcurrentRequests MIB模块通过这些对象的值限制其最大并发请求数。未经授权的访问可能会导致受管节点过载，并中断受管节点的其他功能。
o pingCtlTable o traceRouteCtlTable o lookupCtlTable All objects in entries of these tables (except index objects) have a MAX-ACCESS clause of read-create. Unauthorized access to these objects can disturb the measurements controlled by the tables. Also, the functions offered by the MIB modules can be misused for illegal data retrieval and for attacking other systems by floods of ping probes, traceroute probes or lookup requests, respectively.
o pingCtlTable o traceroutectlable o lookupCtlTable这些表的条目中的所有对象（索引对象除外）都具有read create的MAX-ACCESS子句。未经授权访问这些对象可能会干扰由表格控制的测量。此外，MIB模块提供的功能可能被误用于非法数据检索，以及分别通过大量ping探测、traceroute探测或查找请求攻击其他系统。
In general, all three, the ping, traceroute, and lookup functions, when used excessively are considered a form of system attack. In the case of ping, sending a system request too often can negatively effect its performance and attempting to connect to what is supposed to be an unused port can be very unpredictable. Excessive use of the traceroute capability can, like ping, negatively affect system performance. The same applies to excessive use of the lookup service, particularly if the lookup cannot be resolved locally. In
通常，ping、traceroute和lookup这三个函数在过度使用时都被认为是一种系统攻击。在ping的情况下，过于频繁地发送系统请求可能会对其性能产生负面影响，并且尝试连接到假定为未使用的端口可能非常不可预测。过度使用traceroute功能会像ping一样对系统性能产生负面影响。这同样适用于过度使用查找服务，尤其是当无法在本地解析查找时。在里面
insecure environments, it is RECOMMENDED that the MIBs defined within this memo not be supported.
如果环境不安全，建议不支持此备忘录中定义的MIB。
o lookupPurgeTime Unauthorized access to this object can lead to the deletion of results of lookup operations before they are read by a management system, if the object is set to 0 or small values close to 0. If the object is set to very high values, unauthorized access can lead to a high consumption of resources for storing lookup results.
o lookupPurgeTime未经授权访问此对象可能会导致在管理系统读取查找操作的结果之前删除这些结果（如果对象设置为0或接近0的小值）。如果将对象设置为非常高的值，则未经授权的访问可能会导致存储查找结果的资源消耗过高。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. However, the only information that can be disclosed without encryption is the configuration and results of measurements that are performed by implementations of the MIB modules.
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。然而，在没有加密的情况下可以公开的唯一信息是由MIB模块的实现执行的测量的配置和结果。
To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (VACM), defined in RFC 3415 [RFC3415], for tables in which multiple users may need to create or modify entries independently, 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 defined in VACM, in accordance with a security policy.
为了便于安全管理员使用RFC 3415[RFC3415]中定义的基于视图的访问控制模型（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访问控制机制提供控制。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），也无法控制安全网络上的用户
allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
允许访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
This document is a product of the DISMAN Working Group. Thanks to Eduardo Cardona for suggesting the minimum compliance statements and to Juergen Schoenwaelder for the very detailed and constructive MIB review.
本文件是DEMAN工作组的成果。感谢Eduardo Cardona提出最低合规性声明，感谢Juergen Schoenwaeld进行非常详细和建设性的MIB审查。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年12月。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 4001，2005年2月。
[RFC792] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981.
[RFC792]Postel，J.，“互联网控制消息协议”，STD 5，RFC 792，1981年9月。
[RFC862] Postel, J., "Echo Protocol", STD 20, RFC 862, May 1983.
[RFC862]Postel，J.，“回波协议”，STD 20，RFC 862，1983年5月。
[RFC1812] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812, June 1995.
[RFC1812]Baker，F.，“IP版本4路由器的要求”，RFC1812，1995年6月。
[RFC2474] 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.
[RFC2474]Nichols，K.，Blake，S.，Baker，F.，和D.Black，“IPv4和IPv6头中区分服务字段（DS字段）的定义”，RFC 2474，1998年12月。
[RFC3260] Grossman, D., "New Terminology and Clarifications for Diffserv", RFC 3260, April 2002.
[RFC3260]Grossman，D.“区分服务的新术语和澄清”，RFC 3260，2002年4月。
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
[RFC3415]Wijnen，B.，Presuhn，R.，和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
Authors' Addresses
作者地址
Juergen Quittek NEC Europe Ltd. Network Laboratories Kurfuersten-Anlage 36 69115 Heidelberg Germany
德国海德堡Juergen Quittek NEC欧洲有限公司网络实验室Kurfuersten Anlage 36 69115
Phone: +49 6221 4342-115
EMail: quittek@netlab.nec.de
Phone: +49 6221 4342-115
EMail: quittek@netlab.nec.de
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
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat 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 on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。