Network Working Group S. Waldbusser
Request for Comments: 2819 Lucent Technologies
STD: 59 May 2000
Obsoletes: 1757
Category: Standards Track
Network Working Group S. Waldbusser
Request for Comments: 2819 Lucent Technologies
STD: 59 May 2000
Obsoletes: 1757
Category: Standards Track
Remote Network Monitoring Management Information Base
远程网络监控管理信息库
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices.
此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于管理远程网络监控设备的对象。
This memo obsoletes RFC 1757. This memo extends that specification by documenting the RMON MIB in SMIv2 format while remaining semantically identical to the existing SMIv1-based MIB.
本备忘录废除了RFC 1757。本备忘录通过以SMIv2格式记录RMON MIB扩展了该规范，同时在语义上与现有的基于SMIv1的MIB保持一致。
Table of Contents
目录
1 The SNMP Management Framework .............................. 2
2 Overview ................................................... 3
2.1 Remote Network Management Goals .......................... 4
2.2 Textual Conventions ...................................... 5
2.3 Structure of MIB ......................................... 5
2.3.1 The Ethernet Statistics Group .......................... 6
2.3.2 The History Control Group .............................. 6
2.3.3 The Ethernet History Group ............................. 6
2.3.4 The Alarm Group ........................................ 7
2.3.5 The Host Group ......................................... 7
2.3.6 The HostTopN Group ..................................... 7
2.3.7 The Matrix Group ....................................... 7
2.3.8 The Filter Group ....................................... 7
2.3.9 The Packet Capture Group ............................... 8
2.3.10 The Event Group ....................................... 8
3 Control of Remote Network Monitoring Devices ............... 8
3.1 Resource Sharing Among Multiple Management Stations ... 9
3.2 Row Addition Among Multiple Management Stations .......... 10
4 Conventions ................................................ 11
5 Definitions ................................................ 12
6 Security Considerations .................................... 94
7 Acknowledgments ............................................ 95
8 Author's Address ........................................... 95
9 References ................................................. 95
10 Intellectual Property ..................................... 97
11 Full Copyright Statement .................................. 98
1 The SNMP Management Framework .............................. 2
2 Overview ................................................... 3
2.1 Remote Network Management Goals .......................... 4
2.2 Textual Conventions ...................................... 5
2.3 Structure of MIB ......................................... 5
2.3.1 The Ethernet Statistics Group .......................... 6
2.3.2 The History Control Group .............................. 6
2.3.3 The Ethernet History Group ............................. 6
2.3.4 The Alarm Group ........................................ 7
2.3.5 The Host Group ......................................... 7
2.3.6 The HostTopN Group ..................................... 7
2.3.7 The Matrix Group ....................................... 7
2.3.8 The Filter Group ....................................... 7
2.3.9 The Packet Capture Group ............................... 8
2.3.10 The Event Group ....................................... 8
3 Control of Remote Network Monitoring Devices ............... 8
3.1 Resource Sharing Among Multiple Management Stations ... 9
3.2 Row Addition Among Multiple Management Stations .......... 10
4 Conventions ................................................ 11
5 Definitions ................................................ 12
6 Security Considerations .................................... 94
7 Acknowledgments ............................................ 95
8 Author's Address ........................................... 95
9 References ................................................. 95
10 Intellectual Property ..................................... 97
11 Full Copyright Statement .................................. 98
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [1].
o RFC 2571[1]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[5]、RFC 2579[6]和RFC 2580[7]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是Internet标准跟踪协议，称为SNMPv2c，并在RFC 1901[9]和RFC中进行了描述
1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
1906 [10]. 消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2572[11]和RFC 2574[12]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
o RFC 2573[14]中描述的一组基本应用程序和RFC 2575[15]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [22].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[22]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. Often these remote probes are stand-alone devices and devote significant internal resources for the sole purpose of managing a network. An organization may employ many of these devices, one per network segment, to manage its internet. In addition, these devices may be used for a network management service provider to access a client network, often geographically remote.
远程网络监视设备，通常称为监视器或探测器，是用于管理网络的仪器。这些远程探测器通常是独立的设备，并将大量的内部资源专门用于管理网络。一个组织可以使用许多这样的设备来管理其互联网，每个网段一个。此外，这些设备可用于网络管理服务提供商访问通常在地理上远程的客户端网络。
The objects defined in this document are intended as an interface between an RMON agent and an RMON management application and are not intended for direct manipulation by humans. While some users may tolerate the direct display of some of these objects, few will
本文档中定义的对象旨在作为RMON代理和RMON管理应用程序之间的接口，不用于人工直接操作。虽然有些用户可能会容忍直接显示其中一些对象，但很少有人会容忍
tolerate the complexity of manually manipulating objects to accomplish row creation. These functions should be handled by the management application.
容忍手动操作对象以完成行创建的复杂性。这些功能应由管理应用程序处理。
While most of the objects in this document are suitable for the management of any type of network, there are some which are specific to managing Ethernet networks. These are the objects in the etherStatsTable, the etherHistoryTable, and some attributes of the filterPktStatus and capturBufferPacketStatus objects. The design of this MIB allows similar objects to be defined for other network types. It is intended that future versions of this document and additional documents will define extensions for other network types.
虽然本文档中的大多数对象适用于管理任何类型的网络，但也有一些特定于管理以太网网络。这些是etherStatsTable、etherHistoryTable中的对象，以及filterPktStatus和capturBufferPacketStatus对象的一些属性。此MIB的设计允许为其他网络类型定义类似的对象。本文档和其他文档的未来版本将定义其他网络类型的扩展。
There are a number of companion documents to the RMON MIB. The Token Ring RMON MIB [19] provides objects specific to managing Token Ring networks. The RMON-2 MIB [20] extends RMON by providing RMON analysis up to the application layer. The SMON MIB [21] extends RMON by providing RMON analysis for switched networks.
RMON MIB有许多附带文档。令牌环RMON MIB[19]提供特定于管理令牌环网络的对象。RMON-2 MIB[20]通过向应用层提供RMON分析来扩展RMON。SMON MIB[21]通过提供交换网络的RMON分析来扩展RMON。
o Offline Operation There are sometimes conditions when a management station will not be in constant contact with its remote monitoring devices. This is sometimes by design in an attempt to lower communications costs (especially when communicating over a WAN or dialup link), or by accident as network failures affect the communications between the management station and the probe.
o 脱机操作有时会出现管理站无法与其远程监控设备保持持续接触的情况。这有时是为了降低通信成本而设计的（特别是在通过WAN或拨号链路进行通信时），或者是由于网络故障影响管理站和探测器之间的通信而造成的。
For this reason, this MIB allows a probe to be configured to perform diagnostics and to collect statistics continuously, even when communication with the management station may not be possible or efficient. The probe may then attempt to notify the management station when an exceptional condition occurs. Thus, even in circumstances where communication between management station and probe is not continuous, fault, performance, and configuration information may be continuously accumulated and communicated to the management station conveniently and efficiently.
因此，此MIB允许配置探测器以执行诊断并连续收集统计数据，即使与管理站的通信可能不可能或效率不高。当出现异常情况时，探测器可尝试通知管理站。因此，即使在管理站和探测器之间的通信不连续的情况下，故障、性能和配置信息也可以连续地累积并方便而高效地传送给管理站。
o Proactive Monitoring Given the resources available on the monitor, it is potentially helpful for it continuously to run diagnostics and to log network performance. The monitor is always available at the onset of any failure. It can notify the management station of the failure and can store historical statistical information
o 主动监控由于监控器上有可用的资源，它可能有助于它持续运行诊断和记录网络性能。在出现任何故障时，监控器始终可用。它可以将故障通知管理站，并可以存储历史统计信息
about the failure. This historical information can be played back by the management station in an attempt to perform further diagnosis into the cause of the problem.
关于失败。管理站可以回放此历史信息，以便对故障原因进行进一步诊断。
o Problem Detection and Reporting The monitor can be configured to recognize conditions, most notably error conditions, and continuously to check for them. When one of these conditions occurs, the event may be logged, and management stations may be notified in a number of ways.
o 问题检测和报告监视器可配置为识别条件，尤其是错误条件，并持续检查它们。当其中一种情况发生时，可记录事件，并以多种方式通知管理站。
o Value Added Data Because a remote monitoring device represents a network resource dedicated exclusively to network management functions, and because it is located directly on the monitored portion of the network, the remote network monitoring device has the opportunity to add significant value to the data it collects. For instance, by highlighting those hosts on the network that generate the most traffic or errors, the probe can give the management station precisely the information it needs to solve a class of problems.
o 增值数据因为远程监控设备代表专用于网络管理功能的网络资源，并且因为它直接位于网络的受监控部分，所以远程网络监控设备有机会为其收集的数据增加重要价值。例如，通过突出显示网络上产生最多流量或错误的主机，探测器可以准确地向管理站提供解决一类问题所需的信息。
o Multiple Managers An organization may have multiple management stations for different units of the organization, for different functions (e.g. engineering and operations), and in an attempt to provide disaster recovery. Because environments with multiple management stations are common, the remote network monitoring device has to deal with more than own management station, potentially using its resources concurrently.
o 多个经理一个组织可能有多个管理站，用于组织的不同单位、不同职能（如工程和运营），并试图提供灾难恢复。由于具有多个管理站的环境是常见的，因此远程网络监控设备必须处理多个管理站，可能同时使用其资源。
Two new data types are introduced as a textual convention in this MIB document, OwnerString and EntryStatus.
在这个MIB文档中，作为文本约定引入了两种新的数据类型：OwnerString和EntryStatus。
The objects are arranged into the following groups:
对象被排列为以下组：
- ethernet statistics
- 以太网统计
- history control
- 历史控制
- ethernet history
- 以太网历史
- alarm
- 惊恐
- host
- 主办
- hostTopN
- 主机
- matrix
- 矩阵
- filter
- 滤器
- packet capture
- 数据包捕获
- event
- 事件
These groups are the basic unit of conformance. If a remote monitoring device implements a group, then it must implement all objects in that group. For example, a managed agent that implements the host group must implement the hostControlTable, the hostTable and the hostTimeTable. While this section provides an overview of grouping and conformance information for this MIB, the authoritative reference for such information is contained in the MODULE-COMPLIANCE and OBJECT-GROUP macros later in this MIB.
这些组是一致性的基本单位。如果远程监控设备实现了一个组，那么它必须实现该组中的所有对象。例如，实现主机组的托管代理必须实现hostControlTable、hostTable和HostTimeline。虽然本节概述了此MIB的分组和一致性信息，但此类信息的权威参考包含在本MIB后面的MODULE-COMPLIANCE和OBJECT-GROUP宏中。
All groups in this MIB are optional. Implementations of this MIB must also implement the system group of MIB-II [16] and the IF-MIB [17]. MIB-II may also mandate the implementation of additional groups.
此MIB中的所有组都是可选的。该MIB的实现还必须实现MIB-II[16]和IF-MIB[17]的系统组。MIB-II还可授权实施其他组。
These groups are defined to provide a means of assigning object identifiers, and to provide a method for implementors of managed agents to know which objects they must implement.
定义这些组是为了提供一种分配对象标识符的方法，并为托管代理的实现者提供一种方法，让他们知道必须实现哪些对象。
The ethernet statistics group contains statistics measured by the probe for each monitored Ethernet interface on this device. This group consists of the etherStatsTable.
ethernet statistics（以太网统计信息）组包含探测器为此设备上的每个受监控以太网接口测量的统计信息。此组由EtherstStatsTable组成。
The history control group controls the periodic statistical sampling of data from various types of networks. This group consists of the historyControlTable.
历史控制组控制来自各种类型网络的数据的定期统计采样。此组由historyControlTable组成。
The ethernet history group records periodic statistical samples from an ethernet network and stores them for later retrieval. This group consists of the etherHistoryTable.
ethernet history（以太网历史记录）组记录来自以太网网络的定期统计样本，并将其存储起来以供以后检索。该组由etherHistoryTable组成。
The alarm group periodically takes statistical samples from variables in the probe and compares them to previously configured thresholds. If the monitored variable crosses a threshold, an event is generated.
报警组定期从探测器中的变量中获取统计样本，并将其与以前配置的阈值进行比较。如果监控变量超过阈值，则生成事件。
A hysteresis mechanism is implemented to limit the generation of alarms. This group consists of the alarmTable and requires the implementation of the event group.
采用滞后机制来限制报警的产生。此组由alarmTable组成，需要实现事件组。
The host group contains statistics associated with each host discovered on the network. This group discovers hosts on the network by keeping a list of source and destination MAC Addresses seen in good packets promiscuously received from the network. This group consists of the hostControlTable, the hostTable, and the hostTimeTable.
主机组包含与网络上发现的每个主机相关的统计信息。该组通过保存源和目标MAC地址的列表来发现网络上的主机，这些MAC地址可以在从网络上随意接收的良好数据包中看到。此组由hostControlTable、hostTable和HostTimeline组成。
The hostTopN group is used to prepare reports that describe the hosts that top a list ordered by one of their statistics. The available statistics are samples of one of their base statistics over an interval specified by the management station. Thus, these statistics are rate based. The management station also selects how many such hosts are reported. This group consists of the hostTopNControlTable and the hostTopNTable, and requires the implementation of the host group.
hostTopN组用于准备报告，描述按其统计信息排序的列表中排名靠前的主机。可用统计信息是管理站指定的时间间隔内其基本统计信息之一的样本。因此，这些统计数据是基于比率的。管理站还选择报告的此类主机的数量。此组由hostTopNControlTable和HostTopContable组成，需要实现主机组。
The matrix group stores statistics for conversations between sets of two addresses. As the device detects a new conversation, it creates a new entry in its tables. This group consists of the matrixControlTable, the matrixSDTable and the matrixDSTable.
矩阵组存储两个地址集之间对话的统计信息。当设备检测到新对话时，它会在其表中创建一个新条目。该组由matrixControlTable、matrixSDTable和MatrixDataStable组成。
The filter group allows packets to be matched by a filter equation. These matched packets form a data stream that may be captured or may generate events. This group consists of the filterTable and the channelTable.
过滤器组允许通过过滤器方程匹配数据包。这些匹配的分组形成可被捕获或可生成事件的数据流。此组由filterTable和channelTable组成。
The Packet Capture group allows packets to be captured after they flow through a channel. This group consists of the bufferControlTable and the captureBufferTable, and requires the implementation of the filter group.
数据包捕获组允许在数据包流经通道后捕获数据包。此组由bufferControlTable和captureBufferTable组成，需要实现筛选器组。
The event group controls the generation and notification of events from this device. This group consists of the eventTable and the logTable.
事件组控制此设备事件的生成和通知。此组由eventTable和logTable组成。
Due to the complex nature of the available functions in these devices, the functions often need user configuration. In many cases, the function requires parameters to be set up for a data collection operation. The operation can proceed only after these parameters are fully set up.
由于这些设备中可用功能的复杂性，这些功能通常需要用户配置。在许多情况下，该函数要求为数据采集操作设置参数。只有在完全设置这些参数后，才能继续操作。
Many functional groups in this MIB have one or more tables in which to set up control parameters, and one or more data tables in which to place the results of the operation. The control tables are typically read-write in nature, while the data tables are typically read-only. Because the parameters in the control table often describe resulting data in the data table, many of the parameters can be modified only when the control entry is invalid. Thus, the method for modifying these parameters is to invalidate the control entry, causing its deletion and the deletion of any associated data entries, and then create a new control entry with the proper parameters. Deleting the control entry also gives a convenient method for reclaiming the resources used by the associated data.
此MIB中的许多功能组都有一个或多个用于设置控制参数的表，以及一个或多个用于放置操作结果的数据表。控制表通常是读写性质的，而数据表通常是只读的。由于控制表中的参数通常描述数据表中的结果数据，因此只有当控制项无效时，才能修改许多参数。因此，修改这些参数的方法是使控件条目无效，导致其删除和任何相关数据条目的删除，然后使用适当的参数创建新的控件条目。删除控件条目还提供了一种方便的方法来回收关联数据所使用的资源。
Some objects in this MIB provide a mechanism to execute an action on the remote monitoring device. These objects may execute an action as a result of a change in the state of the object. For those objects in this MIB, a request to set an object to the same value as it currently holds would thus cause no action to occur.
此MIB中的某些对象提供了在远程监控设备上执行操作的机制。这些对象可能由于对象状态的更改而执行操作。对于此MIB中的那些对象，将对象设置为其当前持有的相同值的请求将不会导致任何操作发生。
To facilitate control by multiple managers, resources have to be shared among the managers. These resources are typically the memory and computation resources that a function requires.
为了便于多个管理者进行控制，资源必须在管理者之间共享。这些资源通常是函数所需的内存和计算资源。
When multiple management stations wish to use functions that compete for a finite amount of resources on a device, a method to facilitate this sharing of resources is required. Potential conflicts include:
当多个管理站希望使用在设备上争夺有限资源的功能时，需要一种促进资源共享的方法。潜在冲突包括：
o Two management stations wish to simultaneously use resources that together would exceed the capability of the device. o A management station uses a significant amount of resources for a long period of time. o A management station uses resources and then crashes, forgetting to free the resources so others may use them.
o 两个管理站希望同时使用超过设备能力的资源。o管理站长期使用大量资源。o管理站使用资源，然后崩溃，忘记释放资源以便其他人使用。
A mechanism is provided for each management station initiated function in this MIB to avoid these conflicts and to help resolve them when they occur. Each function has a label identifying the initiator (owner) of the function. This label is set by the initiator to provide for the following possibilities:
此MIB中为每个管理站启动的功能提供了一种机制，以避免这些冲突，并在冲突发生时帮助解决这些冲突。每个函数都有一个标签，标识函数的发起方（所有者）。该标签由启动器设置，以提供以下可能性：
o A management station may recognize resources it owns and no longer needs. o A network operator can find the management station that owns the resource and negotiate for it to be freed. o A network operator may decide to unilaterally free resources another network operator has reserved. o Upon initialization, a management station may recognize resources it had reserved in the past. With this information it may free the resources if it no longer needs them.
o 管理站可以识别其拥有的资源，而不再需要这些资源。o网络运营商可以找到拥有资源的管理站，并协商释放资源。o网络运营商可决定单方面释放另一网络运营商保留的资源。o初始化时，管理站可能会识别其过去保留的资源。有了这些信息，如果不再需要资源，它可能会释放这些资源。
Management stations and probes should support any format of the owner string dictated by the local policy of the organization. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. This information will help users to share the resources more effectively.
管理站和探测器应支持组织的本地策略规定的所有者字符串的任何格式。建议此名称包含以下一个或多个内容：IP地址、管理站名称、网络管理器名称、位置或电话号码。这些信息将帮助用户更有效地共享资源。
There is often default functionality that the device or the administrator of the probe (often the network administrator) wishes to set up. The resources associated with this functionality are then owned by the device itself or by the network administrator, and are intended to be long-lived. In this case, the device or the administrator will set the relevant owner object to a string starting with 'monitor'. Indiscriminate modification of the monitor-owned configuration by network management stations is discouraged. In fact, a network management station should only modify these objects under the direction of the administrator of the probe.
设备或探测器管理员（通常是网络管理员）通常希望设置默认功能。然后，与此功能相关联的资源由设备本身或网络管理员拥有，并打算长期使用。在这种情况下，设备或管理员将相关所有者对象设置为以“monitor”开头的字符串。不鼓励随意修改网络管理站拥有的监视器配置。事实上，网络管理站只能在探测器管理员的指导下修改这些对象。
Resources on a probe are scarce and are typically allocated when control rows are created by an application. Since many applications may be using a probe simultaneously, indiscriminate allocation of resources to particular applications is very likely to cause resource shortages in the probe.
探测上的资源很少，通常在应用程序创建控制行时进行分配。由于许多应用程序可能同时使用探测器，不加选择地将资源分配给特定应用程序很可能会导致探测器中的资源短缺。
When a network management station wishes to utilize a function in a monitor, it is encouraged to first scan the control table of that function to find an instance with similar parameters to share. This is especially true for those instances owned by the monitor, which can be assumed to change infrequently. If a management station decides to share an instance owned by another management station, it should understand that the management station that owns the instance may indiscriminately modify or delete it.
当网络管理站希望利用监视器中的功能时，建议首先扫描该功能的控制表，以找到具有类似参数的实例进行共享。对于监控器所拥有的实例尤其如此，可以假定这些实例很少发生更改。如果一个管理站决定共享另一个管理站拥有的实例，它应该理解拥有该实例的管理站可能会不加区别地修改或删除它。
It should be noted that a management application should have the most trust in a monitor-owned row because it should be changed very infrequently. A row owned by the management application is less long-lived because a network administrator is more likely to re-assign resources from a row that is in use by one user than from a monitor-owned row that is potentially in use by many users. A row owned by another application would be even less long-lived because the other application may delete or modify that row completely at its discretion.
应该注意的是，管理应用程序应该在监视器拥有的行中拥有最多的信任，因为它应该很少被更改。管理应用程序拥有的行寿命较短，因为网络管理员更可能从一个用户正在使用的行中重新分配资源，而不是从多个用户可能正在使用的监视器拥有的行中重新分配资源。另一个应用程序拥有的行的寿命甚至更短，因为另一个应用程序可以自行决定完全删除或修改该行。
The addition of new rows is achieved using the method described in RFC 1905 [13]. In this MIB, rows are often added to a table in order to configure a function. This configuration usually involves parameters that control the operation of the function. The agent must check these parameters to make sure they are appropriate given restrictions defined in this MIB as well as any implementation specific restrictions such as lack of resources. The agent implementor may be confused as to when to check these parameters and when to signal to the management station that the parameters are invalid. There are two opportunities:
使用RFC 1905[13]中描述的方法实现新行的添加。在这个MIB中，行通常被添加到表中以配置函数。此配置通常涉及控制功能操作的参数。代理必须检查这些参数，以确保它们在给定此MIB中定义的限制以及任何特定于实现的限制（如缺少资源）时是适当的。代理实现者可能会混淆何时检查这些参数以及何时向管理站发出参数无效的信号。有两个机会：
o When the management station sets each parameter object.
o 当管理站设置每个参数对象时。
o When the management station sets the entry status object to valid.
o 当管理站将条目状态对象设置为有效时。
If the latter is chosen, it would be unclear to the management station which of the several parameters was invalid and caused the badValue error to be emitted. Thus, wherever possible, the implementor should choose the former as it will provide more information to the management station.
如果选择后者，管理站将不清楚几个参数中的哪一个无效，并导致发出badValue错误。因此，只要可能，实施者应选择前者，因为它将向管理站提供更多信息。
A problem can arise when multiple management stations attempt to set configuration information simultaneously using SNMP. When this involves the addition of a new conceptual row in the same control table, the managers may collide, attempting to create the same entry. To guard against these collisions, each such control entry contains a status object with special semantics that help to arbitrate among the managers. If an attempt is made with the row addition mechanism to create such a status object and that object already exists, an error is returned. When more than one manager simultaneously attempts to create the same conceptual row, only the first can succeed. The others will receive an error.
当多个管理站试图同时使用SNMP设置配置信息时，可能会出现问题。当这涉及到在同一控制表中添加新的概念行时，管理者可能会发生冲突，试图创建相同的条目。为了防止这些冲突，每个这样的控件条目都包含一个具有特殊语义的状态对象，该语义有助于在管理器之间进行仲裁。如果试图使用行添加机制创建这样的状态对象，并且该对象已经存在，则返回错误。当多个管理器同时尝试创建同一概念行时，只有第一个可以成功。其他人将收到一个错误。
When a manager wishes to create a new control entry, it needs to choose an index for that row. It may choose this index in a variety of ways, hopefully minimizing the chances that the index is in use by another manager. If the index is in use, the mechanism mentioned previously will guard against collisions. Examples of schemes to choose index values include random selection or scanning the control table looking for the first unused index. Because index values may be any valid value in the range and they are chosen by the manager, the agent must allow a row to be created with any unused index value if it has the resources to create a new row.
当管理器希望创建新控件项时，需要为该行选择索引。它可以通过多种方式选择该索引，希望最大限度地减少该索引被其他经理使用的可能性。如果索引正在使用，前面提到的机制将防止冲突。选择索引值的方案示例包括随机选择或扫描控制表以查找第一个未使用的索引。由于索引值可以是范围内的任何有效值，并且由管理器选择，因此如果代理具有创建新行的资源，则必须允许使用任何未使用的索引值创建行。
Some tables in this MIB reference other tables within this MIB. When creating or deleting entries in these tables, it is generally allowable for dangling references to exist. There is no defined order for creating or deleting entries in these tables.
此MIB中的某些表引用此MIB中的其他表。在这些表中创建或删除条目时，通常允许存在悬挂引用。在这些表中，没有定义创建或删除条目的顺序。
The following conventions are used throughout the RMON MIB and its companion documents.
以下约定在RMON MIB及其配套文档中使用。
Good Packets
好包
Good packets are error-free packets that have a valid frame length. For example, on Ethernet, good packets are error-free packets that are between 64 octets long and 1518 octets long. They follow the form defined in IEEE 802.3 section 3.2.all.
好数据包是具有有效帧长度的无错误数据包。例如，在以太网上，好的数据包是长度在64个八位字节到1518个八位字节之间的无错误数据包。它们遵循IEEE 802.3第3.2.1节中定义的形式。
Bad Packets
坏包
Bad packets are packets that have proper framing and are therefore recognized as packets, but contain errors within the packet or have an invalid length. For example, on Ethernet, bad packets have a valid preamble and SFD, but have a bad CRC, or are either shorter than 64 octets or longer than 1518 octets.
坏数据包是具有正确帧的数据包，因此被识别为数据包，但数据包中包含错误或长度无效。例如，在以太网上，坏数据包具有有效的前导码和SFD，但具有坏的CRC，或者短于64个八位字节或长于1518个八位字节。
RMON-MIB DEFINITIONS ::= BEGIN
RMON-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE, mib-2, Counter32, Integer32, TimeTicks FROM SNMPv2-SMI
从SNMPv2 SMI导入模块标识、对象类型、对象标识、通知类型、mib-2、计数器32、整数32、时间标记
TEXTUAL-CONVENTION, DisplayString FROM SNMPv2-TC
文本约定，来自SNMPv2 TC的显示字符串
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF;
来自SNMPv2 CONF的MODULE-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUP；
-- Remote Network Monitoring MIB
--远程网络监控MIB
rmonMibModule MODULE-IDENTITY LAST-UPDATED "200005110000Z" -- 11 May, 2000 ORGANIZATION "IETF RMON MIB Working Group" CONTACT-INFO "Steve Waldbusser Phone: +1-650-948-6500 Fax: +1-650-745-0671 Email: waldbusser@nextbeacon.com" DESCRIPTION "Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. This MIB defines objects for managing remote network monitoring devices."
rmonMibModule MODULE-IDENTITY上次更新的“2000051110000Z”-2000年5月11日组织“IETF RMON MIB工作组”联系方式“Steve Waldbusser电话：+1-650-948-6500传真：+1-650-745-0671电子邮件：waldbusser@nextbeacon.com“说明“远程网络监控设备，通常称为监视器或探测器，是用于管理网络的仪器。此MIB定义用于管理远程网络监控设备的对象。”
REVISION "200005110000Z" -- 11 May, 2000 DESCRIPTION "Reformatted into SMIv2 format.
修订版“2000051110000Z”-2000年5月11日“说明”重新格式化为SMIv2格式。
This version published as RFC 2819."
此版本发布为RFC 2819。”
REVISION "199502010000Z" -- 1 Feb, 1995 DESCRIPTION "Bug fixes, clarifications and minor changes based on implementation experience, published as RFC1757 [18].
修订版“19950210000Z”-1995年2月1日描述“基于实施经验的错误修复、澄清和微小更改”，发布为RFC1757[18]。
Two changes were made to object definitions:
对对象定义进行了两项更改：
1) A new status bit has been defined for the captureBufferPacketStatus object, indicating that the packet order within the capture buffer may not be identical to the packet order as received off the wire. This bit may only
1) 已为captureBufferPacketStatus对象定义了一个新的状态位，表示捕获缓冲区内的数据包顺序可能与线下接收的数据包顺序不同。这一点可能只有
be used for packets transmitted by the probe. Older NMS applications can safely ignore this status bit, which might be used by newer agents.
用于探测器传输的数据包。较旧的NMS应用程序可以安全地忽略此状态位，较新的代理可能会使用此状态位。
2) The packetMatch trap has been removed. This trap was never actually 'approved' and was not added to this document along with the risingAlarm and fallingAlarm traps. The packetMatch trap could not be throttled, which could cause disruption of normal network traffic under some circumstances. An NMS should configure a risingAlarm threshold on the appropriate channelMatches instance if a trap is desired for a packetMatch event. Note that logging of packetMatch events is still supported--only trap generation for such events has been removed.
2) packetMatch陷阱已被移除。该陷阱从未实际“批准”，也未与risingAlarm和fallingAlarm陷阱一起添加到本文件中。packetMatch陷阱无法节流，在某些情况下可能会导致正常网络流量中断。如果packetMatch事件需要陷阱，NMS应在适当的channelMatches实例上配置risingAlarm阈值。请注意，仍然支持记录packetMatch事件——仅删除了此类事件的陷阱生成。
In addition, several clarifications to individual object definitions have been added to assist agent and NMS implementors:
此外，还对单个对象定义添加了一些澄清，以帮助代理和NMS实施者：
- global definition of 'good packets' and 'bad packets'
- “好数据包”和“坏数据包”的全局定义
- more detailed text governing conceptual row creation and modification
- 控制概念行创建和修改的更详细文本
- instructions for probes relating to interface changes and disruptions
- 与接口更改和中断相关的探头说明
- clarification of some ethernet counter definitions
- 一些以太网计数器定义的澄清
- recommended formula for calculating network utilization
- 计算网络利用率的推荐公式
- clarification of channel and captureBuffer behavior for some unusual conditions
- 澄清某些异常情况下的通道和captureBuffer行为
- examples of proper instance naming for each table"
- 每个表的正确实例命名示例”
REVISION "199111010000Z" -- 1 Nov, 1991
DESCRIPTION
"The original version of this MIB, published as RFC1271."
::= { rmonConformance 8 }
REVISION "199111010000Z" -- 1 Nov, 1991
DESCRIPTION
"The original version of this MIB, published as RFC1271."
::= { rmonConformance 8 }
rmon OBJECT IDENTIFIER ::= { mib-2 16 }
rmon OBJECT IDENTIFIER ::= { mib-2 16 }
-- textual conventions
--文本约定
OwnerString ::= TEXTUAL-CONVENTION
STATUS current
OwnerString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences.
DESCRIPTION“此数据类型用于为资源所有者的管理分配名称建模。实现必须接受由格式良好的NVT ASCII序列组成的值。此外，实现应接受由格式良好的UTF-8序列组成的值。
It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'.
建议此名称包含以下一个或多个内容：IP地址、管理站名称、网络管理器名称、位置或电话号码。在某些情况下，代理本身将是条目的所有者。在这些情况下，该字符串应设置为以“监视器”开头的字符串。
SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties." SYNTAX OCTET STRING (SIZE (0..127))
SNMP访问控制完全根据MIB视图的内容进行阐述；对特定SNMP对象实例的访问仅取决于其在特定MIB视图中的存在与否，而不取决于其值或相关对象实例的值。因此，这种类型的对象只能解决协作管理者之间的资源争用；对于不合作方，它们没有实现访问控制功能。”语法八位字节字符串（大小（0..127））
EntryStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The status of a table entry.
EntryStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The status of a table entry.
Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant EntryStatus object.
将此对象设置为值invalid（4）会使相应的条目无效。也就是说，它有效地解除了与所述条目标识的映射的关联。代理是否从表中删除无效项是实现特有的问题。因此，管理站必须准备好从代理处接收与当前未使用的条目相对应的表格信息。正确解释这些条目需要检查相关EntryStatus对象。
An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances with default values to complete a conceptual row in this table. Because the
无法将此对象的现有实例设置为createRequest（2）。只有在创建此实例时，才能将此对象设置为createRequest（2）。创建此对象时，代理可能希望使用默认值创建补充对象实例，以完成此表中的概念行。因为
creation of these default objects is entirely at the option of the agent, the manager must not assume that any will be created, but may make use of any that are created. Immediately after completing the create operation, the agent must set this object to underCreation(3).
创建这些默认对象完全由代理选择，管理者不得假设将创建任何对象，但可以使用创建的任何对象。完成创建操作后，代理必须立即将此对象设置为创建不足（3）。
When in the underCreation(3) state, an entry is allowed to exist in a possibly incomplete, possibly inconsistent state, usually to allow it to be modified in multiple PDUs. When in this state, an entry is not fully active. Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period.
当处于创建不足（3）状态时，允许条目以可能不完整、可能不一致的状态存在，通常允许在多个PDU中对其进行修改。处于此状态时，条目未完全激活。在管理站完成对条目的配置并将该对象设置为有效（1）或中止（将该对象设置为无效（4）之前，条目应处于欠创建（3）状态。如果代理确定某个条目在异常长的时间内处于未创建（3）状态，则可能会确定管理站已崩溃。如果代理做出此决定，它可能会将此对象设置为无效（4）以回收条目。谨慎的代理人应了解管理站可能需要等待人力投入，并在确定这一异常长的时间时考虑到这种可能性。
An entry in the valid(1) state is fully configured and consistent and fully represents the configuration or operation such a row is intended to represent. For example, it could be a statistical function that is configured and active, or a filter that is available in the list of filters processed by the packet capture process.
处于有效（1）状态的条目是完全配置和一致的，并且完全表示该行打算表示的配置或操作。例如，它可以是已配置且处于活动状态的统计函数，或者在由包捕获过程处理的过滤器列表中可用的过滤器。
A manager is restricted to changing the state of an entry in the following ways:
管理器仅限于通过以下方式更改条目的状态：
To: valid createRequest underCreation invalid From: valid OK NO OK OK createRequest N/A N/A N/A N/A underCreation OK NO OK OK invalid NO NO NO OK nonExistent NO OK NO OK
收件人：创建下的有效createRequest无效发件人：有效确定否确定确定创建请求N/A N/A N/A N/A创建下的无效确定否确定无效不确定不存在确定否确定
In the table above, it is not applicable to move the state from the createRequest state to any other state because the manager will never find the variable in that state. The nonExistent state is not a value of the enumeration, rather it means that the entryStatus variable does not exist at all.
在上表中，不适用于将状态从createRequest状态移动到任何其他状态，因为管理器将永远找不到处于该状态的变量。不存在状态不是枚举的值，而是表示entryStatus变量根本不存在。
An agent may allow an entryStatus variable to change state in
additional ways, so long as the semantics of the states are
followed. This allowance is made to ease the implementation of
the agent and is made despite the fact that managers should
never exercise these additional state transitions."
SYNTAX INTEGER {
valid(1),
createRequest(2),
underCreation(3),
invalid(4)
}
An agent may allow an entryStatus variable to change state in
additional ways, so long as the semantics of the states are
followed. This allowance is made to ease the implementation of
the agent and is made despite the fact that managers should
never exercise these additional state transitions."
SYNTAX INTEGER {
valid(1),
createRequest(2),
underCreation(3),
invalid(4)
}
statistics OBJECT IDENTIFIER ::= { rmon 1 }
history OBJECT IDENTIFIER ::= { rmon 2 }
alarm OBJECT IDENTIFIER ::= { rmon 3 }
hosts OBJECT IDENTIFIER ::= { rmon 4 }
hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
matrix OBJECT IDENTIFIER ::= { rmon 6 }
filter OBJECT IDENTIFIER ::= { rmon 7 }
capture OBJECT IDENTIFIER ::= { rmon 8 }
event OBJECT IDENTIFIER ::= { rmon 9 }
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
statistics OBJECT IDENTIFIER ::= { rmon 1 }
history OBJECT IDENTIFIER ::= { rmon 2 }
alarm OBJECT IDENTIFIER ::= { rmon 3 }
hosts OBJECT IDENTIFIER ::= { rmon 4 }
hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
matrix OBJECT IDENTIFIER ::= { rmon 6 }
filter OBJECT IDENTIFIER ::= { rmon 7 }
capture OBJECT IDENTIFIER ::= { rmon 8 }
event OBJECT IDENTIFIER ::= { rmon 9 }
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
-- The Ethernet Statistics Group
--
-- Implementation of the Ethernet Statistics group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The ethernet statistics group contains statistics measured by the
-- probe for each monitored interface on this device. These
-- statistics take the form of free running counters that start from
-- zero when a valid entry is created.
--
-- This group currently has statistics defined only for
-- Ethernet interfaces. Each etherStatsEntry contains statistics
-- for one Ethernet interface. The probe must create one
-- etherStats entry for each monitored Ethernet interface
-- on the device.
-- The Ethernet Statistics Group
--
-- Implementation of the Ethernet Statistics group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The ethernet statistics group contains statistics measured by the
-- probe for each monitored interface on this device. These
-- statistics take the form of free running counters that start from
-- zero when a valid entry is created.
--
-- This group currently has statistics defined only for
-- Ethernet interfaces. Each etherStatsEntry contains statistics
-- for one Ethernet interface. The probe must create one
-- etherStats entry for each monitored Ethernet interface
-- on the device.
etherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Ethernet statistics entries."
::= { statistics 1 }
etherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Ethernet statistics entries."
::= { statistics 1 }
etherStatsEntry OBJECT-TYPE
SYNTAX EtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics kept for a particular
Ethernet interface. As an example, an instance of the
etherStatsPkts object might be named etherStatsPkts.1"
INDEX { etherStatsIndex }
::= { etherStatsTable 1 }
etherStatsEntry OBJECT-TYPE
SYNTAX EtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics kept for a particular
Ethernet interface. As an example, an instance of the
etherStatsPkts object might be named etherStatsPkts.1"
INDEX { etherStatsIndex }
::= { etherStatsTable 1 }
EtherStatsEntry ::= SEQUENCE {
etherStatsIndex Integer32,
etherStatsDataSource OBJECT IDENTIFIER,
etherStatsDropEvents Counter32,
etherStatsOctets Counter32,
etherStatsPkts Counter32,
etherStatsBroadcastPkts Counter32,
etherStatsMulticastPkts Counter32,
etherStatsCRCAlignErrors Counter32,
etherStatsUndersizePkts Counter32,
etherStatsOversizePkts Counter32,
etherStatsFragments Counter32,
etherStatsJabbers Counter32,
etherStatsCollisions Counter32,
etherStatsPkts64Octets Counter32,
etherStatsPkts65to127Octets Counter32,
etherStatsPkts128to255Octets Counter32,
etherStatsPkts256to511Octets Counter32,
etherStatsPkts512to1023Octets Counter32,
etherStatsPkts1024to1518Octets Counter32,
etherStatsOwner OwnerString,
etherStatsStatus EntryStatus
}
EtherStatsEntry ::= SEQUENCE {
etherStatsIndex Integer32,
etherStatsDataSource OBJECT IDENTIFIER,
etherStatsDropEvents Counter32,
etherStatsOctets Counter32,
etherStatsPkts Counter32,
etherStatsBroadcastPkts Counter32,
etherStatsMulticastPkts Counter32,
etherStatsCRCAlignErrors Counter32,
etherStatsUndersizePkts Counter32,
etherStatsOversizePkts Counter32,
etherStatsFragments Counter32,
etherStatsJabbers Counter32,
etherStatsCollisions Counter32,
etherStatsPkts64Octets Counter32,
etherStatsPkts65to127Octets Counter32,
etherStatsPkts128to255Octets Counter32,
etherStatsPkts256to511Octets Counter32,
etherStatsPkts512to1023Octets Counter32,
etherStatsPkts1024to1518Octets Counter32,
etherStatsOwner OwnerString,
etherStatsStatus EntryStatus
}
etherStatsIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object uniquely identifies this
etherStats entry."
::= { etherStatsEntry 1 }
etherStatsIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object uniquely identifies this
etherStats entry."
::= { etherStatsEntry 1 }
etherStatsDataSource OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current
EtherstStatsDataSource对象类型语法对象标识符MAX-ACCESS读取创建状态当前
DESCRIPTION "This object identifies the source of the data that this etherStats entry is configured to analyze. This source can be any ethernet interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1.
DESCRIPTION“此对象标识此etherStats条目配置为分析的数据源。此源可以是此设备上的任何以太网接口。为了标识特定接口，此对象应标识RFC 2233[17]中定义的ifIndex对象实例，用于所需的接口。例如，如果一个条目要从接口#1接收数据，则此对象将设置为ifIndex.1。
The statistics in this group reflect all packets on the local network segment attached to the identified interface.
此组中的统计信息反映连接到标识接口的本地网段上的所有数据包。
An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry.
代理可能知道，也可能不知道接口的媒体是否发生了根本性的更改，是否需要对此条目进行失效处理。例如，一个可热插拔的以太网卡可以被拔出并替换为令牌环卡。在这种情况下，如果代理知道该更改，建议其使该条目无效。
This object may not be modified if the associated
etherStatsStatus object is equal to valid(1)."
::= { etherStatsEntry 2 }
This object may not be modified if the associated
etherStatsStatus object is equal to valid(1)."
::= { etherStatsEntry 2 }
etherStatsDropEvents OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of events in which packets
were dropped by the probe due to lack of resources.
Note that this number is not necessarily the number of
packets dropped; it is just the number of times this
condition has been detected."
::= { etherStatsEntry 3 }
etherStatsDropEvents OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of events in which packets
were dropped by the probe due to lack of resources.
Note that this number is not necessarily the number of
packets dropped; it is just the number of times this
condition has been detected."
::= { etherStatsEntry 3 }
etherStatsOctets OBJECT-TYPE SYNTAX Counter32 UNITS "Octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
EtherstStatsOctets对象类型语法计数器32单元“Octets”MAX-ACCESS只读状态当前描述“网络上接收的数据（包括坏数据包中的数据）的八位字节总数（不包括帧位，但包括FCS八位字节）。
This object can be used as a reasonable estimate of 10-Megabit ethernet utilization. If greater precision is desired, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows:
该对象可作为10兆以太网利用率的合理估计。如果需要更高的精度，则应在公共间隔前后对etherStatsPkts和etherStatsOctets对象进行采样。采样值的差异分别为PKT和八位字节，间隔中的秒数为interval。这些值用于计算利用率，如下所示：
Pkts * (9.6 + 6.4) + (Octets * .8)
Utilization = -------------------------------------
Interval * 10,000
Pkts * (9.6 + 6.4) + (Octets * .8)
Utilization = -------------------------------------
Interval * 10,000
The result of this equation is the value Utilization which
is the percent utilization of the ethernet segment on a
scale of 0 to 100 percent."
::= { etherStatsEntry 4 }
The result of this equation is the value Utilization which
is the percent utilization of the ethernet segment on a
scale of 0 to 100 percent."
::= { etherStatsEntry 4 }
etherStatsPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad packets,
broadcast packets, and multicast packets) received."
::= { etherStatsEntry 5 }
etherStatsPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad packets,
broadcast packets, and multicast packets) received."
::= { etherStatsEntry 5 }
etherStatsBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of good packets received that were
directed to the broadcast address. Note that this
does not include multicast packets."
::= { etherStatsEntry 6 }
etherStatsBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of good packets received that were
directed to the broadcast address. Note that this
does not include multicast packets."
::= { etherStatsEntry 6 }
etherStatsMulticastPkts OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast
EtherstStatsMulticastPKTS对象类型语法计数器32个单元“数据包”MAX-ACCESS只读状态当前描述“接收到的定向到多播地址的良好数据包总数。请注意，此数字不包括定向到广播的数据包
address."
::= { etherStatsEntry 7 }
address."
::= { etherStatsEntry 7 }
etherStatsCRCAlignErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that
had a length (excluding framing bits, but
including FCS octets) of between 64 and 1518
octets, inclusive, but had either a bad
Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with
a non-integral number of octets (Alignment Error)."
::= { etherStatsEntry 8 }
etherStatsCRCAlignErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that
had a length (excluding framing bits, but
including FCS octets) of between 64 and 1518
octets, inclusive, but had either a bad
Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with
a non-integral number of octets (Alignment Error)."
::= { etherStatsEntry 8 }
etherStatsUndersizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that were
less than 64 octets long (excluding framing bits,
but including FCS octets) and were otherwise well
formed."
::= { etherStatsEntry 9 }
etherStatsUndersizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that were
less than 64 octets long (excluding framing bits,
but including FCS octets) and were otherwise well
formed."
::= { etherStatsEntry 9 }
etherStatsOversizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that were
longer than 1518 octets (excluding framing bits,
but including FCS octets) and were otherwise
well formed."
::= { etherStatsEntry 10 }
etherStatsOversizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets received that were
longer than 1518 octets (excluding framing bits,
but including FCS octets) and were otherwise
well formed."
::= { etherStatsEntry 10 }
etherStatsFragments OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION
EtherstStatsFragments对象类型语法计数器32个单元“数据包”最大访问只读状态当前说明
"The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
“接收到的长度小于64个八位字节（不包括帧位，但包括FCS八位字节）且具有具有整数个八位字节（FCS错误）的坏帧检查序列（FCS）或具有非整数个八位字节（对齐错误）的坏FCS的数据包总数。
Note that it is entirely normal for etherStatsFragments to
increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits."
::= { etherStatsEntry 11 }
Note that it is entirely normal for etherStatsFragments to
increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits."
::= { etherStatsEntry 11 }
etherStatsJabbers OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
EtherstStatsJabbers对象类型语法计数器32单元“数据包”MAX-ACCESS只读状态当前描述“接收的数据包总数超过1518个八位字节（不包括帧位，但包括FCS八位字节），并且具有坏帧检查序列（FCS）和整数个八位字节（FCS错误）或具有非整数八位字节数的坏FCS（对齐错误）。
Note that this definition of jabber is different
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition where any
packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms."
::= { etherStatsEntry 12 }
Note that this definition of jabber is different
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition where any
packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms."
::= { etherStatsEntry 12 }
etherStatsCollisions OBJECT-TYPE SYNTAX Counter32 UNITS "Collisions" MAX-ACCESS read-only STATUS current DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment.
etherStatsCollisions对象类型语法计数器32个单元“冲突”最大访问只读状态当前描述“此以太网段上冲突总数的最佳估计值”。
The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more
返回的值将取决于RMON探测器的位置。IEEE标准802.3第8.2.1.3节（10BASE-5）和第10.3.1.3节（10BASE-2）规定，如果三个或更多站点同时传输，则站点必须在接收模式下检测碰撞。中继器端口必须在两个或多个端口发生冲突时检测冲突
stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would.
电台正在同步发射。因此，放置在中继器端口上的探针可以记录比连接到同一段上的站点上的探针更多的碰撞。
Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions.
当考虑10BASE-T时，探头位置的作用要小得多。IEEE标准802.3的14.2.1.4（10BASE-T）将冲突定义为DO和RD电路上同时存在信号（同时发送和接收）。10BASE-T站只能在传输时检测碰撞。因此，放置在工作站和中继器上的探测器应报告相同数量的碰撞。
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected."
::= { etherStatsEntry 13 }
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected."
::= { etherStatsEntry 13 }
etherStatsPkts64Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were 64 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 14 }
etherStatsPkts64Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were 64 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 14 }
etherStatsPkts65to127Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 15 }
etherStatsPkts65to127Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 15 }
etherStatsPkts128to255Octets OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only
etherStatsPkts128to255Octets对象类型语法计数器32个单元“数据包”最大访问只读
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
128 and 255 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 16 }
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
128 and 255 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 16 }
etherStatsPkts256to511Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
256 and 511 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 17 }
etherStatsPkts256to511Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
256 and 511 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 17 }
etherStatsPkts512to1023Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
512 and 1023 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 18 }
etherStatsPkts512to1023Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
512 and 1023 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 18 }
etherStatsPkts1024to1518Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
1024 and 1518 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 19 }
etherStatsPkts1024to1518Octets OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets (including bad
packets) received that were between
1024 and 1518 octets in length inclusive
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 19 }
etherStatsOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current
EtherstStatsOwner对象类型语法OwnerString MAX-ACCESS读取创建状态当前
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { etherStatsEntry 20 }
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { etherStatsEntry 20 }
etherStatsStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this etherStats entry."
::= { etherStatsEntry 21 }
etherStatsStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this etherStats entry."
::= { etherStatsEntry 21 }
-- The History Control Group
--历史对照组
-- Implementation of the History Control group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The history control group controls the periodic statistical
-- sampling of data from various types of networks. The
-- historyControlTable stores configuration entries that each
-- define an interface, polling period, and other parameters.
-- Once samples are taken, their data is stored in an entry
-- in a media-specific table. Each such entry defines one
-- sample, and is associated with the historyControlEntry that
-- caused the sample to be taken. Each counter in the
-- etherHistoryEntry counts the same event as its similarly-named
-- counterpart in the etherStatsEntry, except that each value here
-- is a cumulative sum during a sampling period.
--
-- If the probe keeps track of the time of day, it should start
-- the first sample of the history at a time such that
-- when the next hour of the day begins, a sample is
-- started at that instant. This tends to make more
-- user-friendly reports, and enables comparison of reports
-- from different probes that have relatively accurate time
-- of day.
--
-- The probe is encouraged to add two history control entries
-- per monitored interface upon initialization that describe a short
-- term and a long term polling period. Suggested parameters are 30
-- seconds for the short term polling period and 30 minutes for
-- the long term period.
-- Implementation of the History Control group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The history control group controls the periodic statistical
-- sampling of data from various types of networks. The
-- historyControlTable stores configuration entries that each
-- define an interface, polling period, and other parameters.
-- Once samples are taken, their data is stored in an entry
-- in a media-specific table. Each such entry defines one
-- sample, and is associated with the historyControlEntry that
-- caused the sample to be taken. Each counter in the
-- etherHistoryEntry counts the same event as its similarly-named
-- counterpart in the etherStatsEntry, except that each value here
-- is a cumulative sum during a sampling period.
--
-- If the probe keeps track of the time of day, it should start
-- the first sample of the history at a time such that
-- when the next hour of the day begins, a sample is
-- started at that instant. This tends to make more
-- user-friendly reports, and enables comparison of reports
-- from different probes that have relatively accurate time
-- of day.
--
-- The probe is encouraged to add two history control entries
-- per monitored interface upon initialization that describe a short
-- term and a long term polling period. Suggested parameters are 30
-- seconds for the short term polling period and 30 minutes for
-- the long term period.
historyControlTable OBJECT-TYPE SYNTAX SEQUENCE OF HistoryControlEntry MAX-ACCESS not-accessible
HistoryControlEntry MAX-ACCESS的historyControlTable对象类型语法序列不可访问
STATUS current
DESCRIPTION
"A list of history control entries."
::= { history 1 }
STATUS current
DESCRIPTION
"A list of history control entries."
::= { history 1 }
historyControlEntry OBJECT-TYPE
SYNTAX HistoryControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up a periodic sampling of
statistics. As an example, an instance of the
historyControlInterval object might be named
historyControlInterval.2"
INDEX { historyControlIndex }
::= { historyControlTable 1 }
historyControlEntry OBJECT-TYPE
SYNTAX HistoryControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up a periodic sampling of
statistics. As an example, an instance of the
historyControlInterval object might be named
historyControlInterval.2"
INDEX { historyControlIndex }
::= { historyControlTable 1 }
HistoryControlEntry ::= SEQUENCE {
historyControlIndex Integer32,
historyControlDataSource OBJECT IDENTIFIER,
historyControlBucketsRequested Integer32,
historyControlBucketsGranted Integer32,
historyControlInterval Integer32,
historyControlOwner OwnerString,
historyControlStatus EntryStatus
}
HistoryControlEntry ::= SEQUENCE {
historyControlIndex Integer32,
historyControlDataSource OBJECT IDENTIFIER,
historyControlBucketsRequested Integer32,
historyControlBucketsGranted Integer32,
historyControlInterval Integer32,
historyControlOwner OwnerString,
historyControlStatus EntryStatus
}
historyControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
historyControl table. Each such entry defines a
set of samples at a particular interval for an
interface on the device."
::= { historyControlEntry 1 }
historyControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
historyControl table. Each such entry defines a
set of samples at a particular interval for an
interface on the device."
::= { historyControlEntry 1 }
historyControlDataSource OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies the source of the data for which historical data was collected and placed in a media-specific table on behalf of this historyControlEntry. This source can be any interface on this device. In order to identify
historyControlDataSource对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“此对象标识为其收集历史数据的数据源，并代表此historyControlEntry将其放置在媒体特定表中。此源可以是此设备上的任何接口。为了识别
a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1.
对于特定接口，该对象应识别RFC 2233[17]中定义的所需接口的ifIndex对象实例。例如，如果一个条目要从接口#1接收数据，则该对象将设置为ifIndex.1。
The statistics in this group reflect all packets on the local network segment attached to the identified interface.
此组中的统计信息反映连接到标识接口的本地网段上的所有数据包。
An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry.
代理可能知道，也可能不知道接口的媒体是否发生了根本性的更改，是否需要对此条目进行失效处理。例如，一个可热插拔的以太网卡可以被拔出并替换为令牌环卡。在这种情况下，如果代理知道该更改，建议其使该条目无效。
This object may not be modified if the associated
historyControlStatus object is equal to valid(1)."
::= { historyControlEntry 2 }
This object may not be modified if the associated
historyControlStatus object is equal to valid(1)."
::= { historyControlEntry 2 }
historyControlBucketsRequested OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry.
HistoryControlBuckets请求的对象类型语法整数32（1..65535）MAX-ACCESS read create STATUS current DESCRIPTION“请求的离散时间间隔数，在此时间间隔内，数据将保存在与此historyControlEntry关联的媒体特定表的部分中。
When this object is created or modified, the probe
should set historyControlBucketsGranted as closely to
this object as is possible for the particular probe
implementation and available resources."
DEFVAL { 50 }
::= { historyControlEntry 3 }
When this object is created or modified, the probe
should set historyControlBucketsGranted as closely to
this object as is possible for the particular probe
implementation and available resources."
DEFVAL { 50 }
::= { historyControlEntry 3 }
historyControlBucketsGranted OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of discrete sampling intervals over which data shall be saved in the part of the media-specific table associated with this historyControlEntry.
historyControlBucketsGranted对象类型语法整数32（1..65535）MAX-ACCESS只读状态当前描述“应在与此historyControlEntry关联的媒体特定表部分保存数据的离散采样间隔数。
When the associated historyControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated historyControlBucketsRequested object.
创建或修改关联的historyControlBucketsRequested对象时，探测器应将该对象设置为尽可能接近特定探测器实现和可用资源所请求的值。探头不得降低该值，除非是修改相关historyControlBucketsRequested对象的结果。
There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the media-specific table.
有时，与此条目关联的实际桶数小于此对象的值。在这种情况下，在每个采样间隔结束时，将向特定于介质的表中添加一个新的存储桶。
When the number of buckets reaches the value of this object and a new bucket is to be added to the media-specific table, the oldest bucket associated with this historyControlEntry shall be deleted by the agent so that the new bucket can be added.
当bucket数量达到此对象的值，并且要向媒体特定表中添加新bucket时，代理应删除与此historyControlEntry关联的最旧bucket，以便添加新bucket。
When the value of this object changes to a value less than the current value, entries are deleted from the media-specific table associated with this historyControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object.
当此对象的值更改为小于当前值的值时，将从与此historyControlEntry关联的媒体特定表中删除条目。代理应删除这些条目中足够多的最早条目，以便其数量保持小于或等于该对象的新值。
When the value of this object changes to a value greater
than the current value, the number of associated media-
specific entries may be allowed to grow."
::= { historyControlEntry 4 }
When the value of this object changes to a value greater
than the current value, the number of associated media-
specific entries may be allowed to grow."
::= { historyControlEntry 4 }
historyControlInterval OBJECT-TYPE SYNTAX Integer32 (1..3600) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour).
historyControlInterval对象类型语法整数32（1..3600）单位“秒”最大读取创建状态当前描述“在与此historyControlEntry关联的媒体特定表部分中，为每个存储桶采样数据的间隔（秒）。此间隔可设置为1到3600（1小时）之间的任意秒数。
Because the counters in a bucket may overflow at their
因为桶中的计数器可能会在其
maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the historyControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the etherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization.
在没有任何指示的情况下，谨慎的管理者将考虑任何相关计数器溢出的可能性。考虑任何计数器在特定媒体类型上溢出的最小时间，并将SyryCuffic TimeObjt对象设置为小于该间隔的值是很重要的。对于任何媒体特定表中的“八位字节”计数器，这通常是最重要的。例如，在以太网网络上，etherHistoryOctets计数器可能在以太网最大利用率的情况下在大约一小时内溢出。
This object may not be modified if the associated
historyControlStatus object is equal to valid(1)."
DEFVAL { 1800 }
::= { historyControlEntry 5 }
This object may not be modified if the associated
historyControlStatus object is equal to valid(1)."
DEFVAL { 1800 }
::= { historyControlEntry 5 }
historyControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { historyControlEntry 6 }
historyControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { historyControlEntry 6 }
historyControlStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this historyControl entry.
historyControlStatus对象类型语法EntryStatus MAX-ACCESS读取创建状态当前描述“此historyControl条目的状态。
Each instance of the media-specific table associated
with this historyControlEntry will be deleted by the agent
if this historyControlEntry is not equal to valid(1)."
::= { historyControlEntry 7 }
Each instance of the media-specific table associated
with this historyControlEntry will be deleted by the agent
if this historyControlEntry is not equal to valid(1)."
::= { historyControlEntry 7 }
-- The Ethernet History Group
--以太网历史组
-- Implementation of the Ethernet History group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Ethernet History group records periodic statistical samples
-- from a network and stores them for later retrieval.
-- Once samples are taken, their data is stored in an entry
-- in a media-specific table. Each such entry defines one
-- Implementation of the Ethernet History group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Ethernet History group records periodic statistical samples
-- from a network and stores them for later retrieval.
-- Once samples are taken, their data is stored in an entry
-- in a media-specific table. Each such entry defines one
-- sample, and is associated with the historyControlEntry that
-- caused the sample to be taken. This group defines the
-- etherHistoryTable, for Ethernet networks.
--
-- sample, and is associated with the historyControlEntry that
-- caused the sample to be taken. This group defines the
-- etherHistoryTable, for Ethernet networks.
--
etherHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Ethernet history entries."
::= { history 2 }
etherHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Ethernet history entries."
::= { history 2 }
etherHistoryEntry OBJECT-TYPE
SYNTAX EtherHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An historical sample of Ethernet statistics on a particular
Ethernet interface. This sample is associated with the
historyControlEntry which set up the parameters for
a regular collection of these samples. As an example, an
instance of the etherHistoryPkts object might be named
etherHistoryPkts.2.89"
INDEX { etherHistoryIndex , etherHistorySampleIndex }
::= { etherHistoryTable 1 }
etherHistoryEntry OBJECT-TYPE
SYNTAX EtherHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An historical sample of Ethernet statistics on a particular
Ethernet interface. This sample is associated with the
historyControlEntry which set up the parameters for
a regular collection of these samples. As an example, an
instance of the etherHistoryPkts object might be named
etherHistoryPkts.2.89"
INDEX { etherHistoryIndex , etherHistorySampleIndex }
::= { etherHistoryTable 1 }
EtherHistoryEntry ::= SEQUENCE {
etherHistoryIndex Integer32,
etherHistorySampleIndex Integer32,
etherHistoryIntervalStart TimeTicks,
etherHistoryDropEvents Counter32,
etherHistoryOctets Counter32,
etherHistoryPkts Counter32,
etherHistoryBroadcastPkts Counter32,
etherHistoryMulticastPkts Counter32,
etherHistoryCRCAlignErrors Counter32,
etherHistoryUndersizePkts Counter32,
etherHistoryOversizePkts Counter32,
etherHistoryFragments Counter32,
etherHistoryJabbers Counter32,
etherHistoryCollisions Counter32,
etherHistoryUtilization Integer32
}
EtherHistoryEntry ::= SEQUENCE {
etherHistoryIndex Integer32,
etherHistorySampleIndex Integer32,
etherHistoryIntervalStart TimeTicks,
etherHistoryDropEvents Counter32,
etherHistoryOctets Counter32,
etherHistoryPkts Counter32,
etherHistoryBroadcastPkts Counter32,
etherHistoryMulticastPkts Counter32,
etherHistoryCRCAlignErrors Counter32,
etherHistoryUndersizePkts Counter32,
etherHistoryOversizePkts Counter32,
etherHistoryFragments Counter32,
etherHistoryJabbers Counter32,
etherHistoryCollisions Counter32,
etherHistoryUtilization Integer32
}
etherHistoryIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only
etherHistoryIndex对象类型语法整数32（1..65535）MAX-ACCESS只读
STATUS current
DESCRIPTION
"The history of which this entry is a part. The
history identified by a particular value of this
index is the same history as identified
by the same value of historyControlIndex."
::= { etherHistoryEntry 1 }
STATUS current
DESCRIPTION
"The history of which this entry is a part. The
history identified by a particular value of this
index is the same history as identified
by the same value of historyControlIndex."
::= { etherHistoryEntry 1 }
etherHistorySampleIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies the particular
sample this entry represents among all samples
associated with the same historyControlEntry.
This index starts at 1 and increases by one
as each new sample is taken."
::= { etherHistoryEntry 2 }
etherHistorySampleIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies the particular
sample this entry represents among all samples
associated with the same historyControlEntry.
This index starts at 1 and increases by one
as each new sample is taken."
::= { etherHistoryEntry 2 }
etherHistoryIntervalStart OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the start of the interval
over which this sample was measured. If the probe
keeps track of the time of day, it should start
the first sample of the history at a time such that
when the next hour of the day begins, a sample is
started at that instant. Note that following this
rule may require the probe to delay collecting the
first sample of the history, as each sample must be
of the same interval. Also note that the sample which
is currently being collected is not accessible in this
table until the end of its interval."
::= { etherHistoryEntry 3 }
etherHistoryIntervalStart OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the start of the interval
over which this sample was measured. If the probe
keeps track of the time of day, it should start
the first sample of the history at a time such that
when the next hour of the day begins, a sample is
started at that instant. Note that following this
rule may require the probe to delay collecting the
first sample of the history, as each sample must be
of the same interval. Also note that the sample which
is currently being collected is not accessible in this
table until the end of its interval."
::= { etherHistoryEntry 3 }
etherHistoryDropEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been
etherHistoryDropEvents对象类型语法计数器32 MAX-ACCESS只读状态当前说明“在此采样间隔内，由于资源不足，探测器丢弃数据包的事件总数。请注意，这个数字不一定是丢弃的数据包的数量，它只是该条件被丢弃的次数
detected."
::= { etherHistoryEntry 4 }
detected."
::= { etherHistoryEntry 4 }
etherHistoryOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets of data (including
those in bad packets) received on the
network (excluding framing bits but including
FCS octets)."
::= { etherHistoryEntry 5 }
etherHistoryOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets of data (including
those in bad packets) received on the
network (excluding framing bits but including
FCS octets)."
::= { etherHistoryEntry 5 }
etherHistoryPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets (including bad packets)
received during this sampling interval."
::= { etherHistoryEntry 6 }
etherHistoryPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets (including bad packets)
received during this sampling interval."
::= { etherHistoryEntry 6 }
etherHistoryBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets received during this
sampling interval that were directed to the
broadcast address."
::= { etherHistoryEntry 7 }
etherHistoryBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets received during this
sampling interval that were directed to the
broadcast address."
::= { etherHistoryEntry 7 }
etherHistoryMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets received during this
sampling interval that were directed to a
multicast address. Note that this number does not
include packets addressed to the broadcast address."
::= { etherHistoryEntry 8 }
etherHistoryMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets received during this
sampling interval that were directed to a
multicast address. Note that this number does not
include packets addressed to the broadcast address."
::= { etherHistoryEntry 8 }
etherHistoryCRCAlignErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that had a length (excluding
framing bits but including FCS octets) between
64 and 1518 octets, inclusive, but had either a bad Frame
Check Sequence (FCS) with an integral number of octets
(FCS Error) or a bad FCS with a non-integral number
of octets (Alignment Error)."
::= { etherHistoryEntry 9 }
etherHistoryCRCAlignErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that had a length (excluding
framing bits but including FCS octets) between
64 and 1518 octets, inclusive, but had either a bad Frame
Check Sequence (FCS) with an integral number of octets
(FCS Error) or a bad FCS with a non-integral number
of octets (Alignment Error)."
::= { etherHistoryEntry 9 }
etherHistoryUndersizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that were less than 64 octets
long (excluding framing bits but including FCS
octets) and were otherwise well formed."
::= { etherHistoryEntry 10 }
etherHistoryUndersizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that were less than 64 octets
long (excluding framing bits but including FCS
octets) and were otherwise well formed."
::= { etherHistoryEntry 10 }
etherHistoryOversizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that were longer than 1518
octets (excluding framing bits but including
FCS octets) but were otherwise well formed."
::= { etherHistoryEntry 11 }
etherHistoryOversizePkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received during this
sampling interval that were longer than 1518
octets (excluding framing bits but including
FCS octets) but were otherwise well formed."
::= { etherHistoryEntry 11 }
etherHistoryFragments OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS
etherHistoryFragments对象类型语法计数器32个单元“数据包”MAX-ACCESS只读状态当前描述“在此采样间隔内接收的长度小于64个八位字节的数据包总数（不包括帧位，但包括FCS
octets) had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
八位字节）具有坏帧检查序列（FCS）和整数个八位字节（FCS错误），或具有非整数个八位字节（对齐错误）。
Note that it is entirely normal for etherHistoryFragments to
increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits."
::= { etherHistoryEntry 12 }
Note that it is entirely normal for etherHistoryFragments to
increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits."
::= { etherHistoryEntry 12 }
etherHistoryJabbers OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
etherHistoryJabbers对象类型语法计数器32个单元“数据包”最大访问只读状态当前描述“在此采样间隔内接收的数据包数超过1518个八位字节（不包括帧位，但包括FCS八位字节），并且具有整数个八位字节的坏帧检查序列（FCS）（FCS错误）或具有非整数八位字节数的坏FCS（对齐错误）。
Note that this definition of jabber is different
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition where any
packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms."
::= { etherHistoryEntry 13 }
Note that this definition of jabber is different
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition where any
packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms."
::= { etherHistoryEntry 13 }
etherHistoryCollisions OBJECT-TYPE SYNTAX Counter32 UNITS "Collisions" MAX-ACCESS read-only STATUS current DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment during this sampling interval.
etherHistoryCollisions对象类型语法计数器32个单元“碰撞”最大访问只读状态当前描述“此采样间隔内此以太网段上的碰撞总数的最佳估计值”。
The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more
返回的值将取决于RMON探测器的位置。IEEE标准802.3第8.2.1.3节（10BASE-5）和第10.3.1.3节（10BASE-2）规定，如果三个或更多站点同时传输，则站点必须在接收模式下检测碰撞。中继器端口必须在两个或多个端口发生冲突时检测冲突
stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would.
电台正在同步发射。因此，放置在中继器端口上的探针可以记录比连接到同一段上的站点上的探针更多的碰撞。
Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions.
当考虑10BASE-T时，探头位置的作用要小得多。IEEE标准802.3的14.2.1.4（10BASE-T）将冲突定义为DO和RD电路上同时存在信号（同时发送和接收）。10BASE-T站只能在传输时检测碰撞。因此，放置在工作站和中继器上的探测器应报告相同数量的碰撞。
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected."
::= { etherHistoryEntry 14 }
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected."
::= { etherHistoryEntry 14 }
etherHistoryUtilization OBJECT-TYPE
SYNTAX Integer32 (0..10000)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The best estimate of the mean physical layer
network utilization on this interface during this
sampling interval, in hundredths of a percent."
::= { etherHistoryEntry 15 }
etherHistoryUtilization OBJECT-TYPE
SYNTAX Integer32 (0..10000)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The best estimate of the mean physical layer
network utilization on this interface during this
sampling interval, in hundredths of a percent."
::= { etherHistoryEntry 15 }
-- The Alarm Group
--警报组
-- Implementation of the Alarm group is optional. The Alarm Group
-- requires the implementation of the Event group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Alarm group periodically takes statistical samples from
-- variables in the probe and compares them to thresholds that have
-- been configured. The alarm table stores configuration
-- entries that each define a variable, polling period, and
-- threshold parameters. If a sample is found to cross the
-- threshold values, an event is generated. Only variables that
-- resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32,
-- Counter32, Counter64, Gauge32, or TimeTicks) may be monitored in
-- this way.
--
-- Implementation of the Alarm group is optional. The Alarm Group
-- requires the implementation of the Event group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Alarm group periodically takes statistical samples from
-- variables in the probe and compares them to thresholds that have
-- been configured. The alarm table stores configuration
-- entries that each define a variable, polling period, and
-- threshold parameters. If a sample is found to cross the
-- threshold values, an event is generated. Only variables that
-- resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32,
-- Counter32, Counter64, Gauge32, or TimeTicks) may be monitored in
-- this way.
--
-- This function has a hysteresis mechanism to limit the generation
-- of events. This mechanism generates one event as a threshold
-- is crossed in the appropriate direction. No more events are
-- generated for that threshold until the opposite threshold is
-- crossed.
--
-- In the case of a sampling a deltaValue, a probe may implement
-- this mechanism with more precision if it takes a delta sample
-- twice per period, each time comparing the sum of the latest two
-- samples to the threshold. This allows the detection of threshold
-- crossings that span the sampling boundary. Note that this does
-- not require any special configuration of the threshold value.
-- It is suggested that probes implement this more precise algorithm.
-- This function has a hysteresis mechanism to limit the generation
-- of events. This mechanism generates one event as a threshold
-- is crossed in the appropriate direction. No more events are
-- generated for that threshold until the opposite threshold is
-- crossed.
--
-- In the case of a sampling a deltaValue, a probe may implement
-- this mechanism with more precision if it takes a delta sample
-- twice per period, each time comparing the sum of the latest two
-- samples to the threshold. This allows the detection of threshold
-- crossings that span the sampling boundary. Note that this does
-- not require any special configuration of the threshold value.
-- It is suggested that probes implement this more precise algorithm.
alarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of alarm entries."
::= { alarm 1 }
alarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of alarm entries."
::= { alarm 1 }
alarmEntry OBJECT-TYPE
SYNTAX AlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up a periodic checking
for alarm conditions. For example, an instance of the
alarmValue object might be named alarmValue.8"
INDEX { alarmIndex }
::= { alarmTable 1 }
alarmEntry OBJECT-TYPE
SYNTAX AlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up a periodic checking
for alarm conditions. For example, an instance of the
alarmValue object might be named alarmValue.8"
INDEX { alarmIndex }
::= { alarmTable 1 }
AlarmEntry ::= SEQUENCE {
alarmIndex Integer32,
alarmInterval Integer32,
alarmVariable OBJECT IDENTIFIER,
alarmSampleType INTEGER,
alarmValue Integer32,
alarmStartupAlarm INTEGER,
alarmRisingThreshold Integer32,
alarmFallingThreshold Integer32,
alarmRisingEventIndex Integer32,
alarmFallingEventIndex Integer32,
alarmOwner OwnerString,
alarmStatus EntryStatus
}
AlarmEntry ::= SEQUENCE {
alarmIndex Integer32,
alarmInterval Integer32,
alarmVariable OBJECT IDENTIFIER,
alarmSampleType INTEGER,
alarmValue Integer32,
alarmStartupAlarm INTEGER,
alarmRisingThreshold Integer32,
alarmFallingThreshold Integer32,
alarmRisingEventIndex Integer32,
alarmFallingEventIndex Integer32,
alarmOwner OwnerString,
alarmStatus EntryStatus
}
alarmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
alarm table. Each such entry defines a
diagnostic sample at a particular interval
for an object on the device."
::= { alarmEntry 1 }
alarmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
alarm table. Each such entry defines a
diagnostic sample at a particular interval
for an object on the device."
::= { alarmEntry 1 }
alarmInterval OBJECT-TYPE SYNTAX Integer32 UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be taken in the case of deltaValue sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2^31 - 1 during a single sampling interval.
alarmInterval对象类型语法整数32单位“秒”最大读取创建状态当前描述“对数据进行采样并与上升和下降阈值进行比较的间隔（秒）。设置此变量时，应注意deltaValue采样的情况-间隔应设置得足够短，以使采样变量在单个采样间隔内不太可能增加或减少2^31-1以上。
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 2 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 2 }
alarmVariable OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled.
alarmVariable对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“要采样的特定变量的对象标识符。只能对解析为ASN.1整数基元类型（整数、整数32、计数器32、计数器64、仪表或时间刻度）的变量进行采样。
Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in
由于SNMP访问控制完全根据MIB视图的内容进行阐述，因此不存在可以限制此对象的值以仅识别特定MIB视图中存在的那些对象的访问控制机制。由于没有可接受的方法限制通过报警机制获得的读取访问，因此探测器必须只授予对该对象的写入访问权限
those views that have read access to all objects on the probe.
对探测器上的所有对象具有读取权限的视图。
During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. If at any time the variable name of an established alarmEntry is no longer available in the selected MIB view, the probe must change the status of this alarmEntry to invalid(4).
在set操作期间，如果提供的变量名在所选MIB视图中不可用，则必须返回badValue错误。如果在任何时候，已建立alarmEntry的变量名在所选MIB视图中不再可用，探测器必须将此alarmEntry的状态更改为无效（4）。
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 3 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 3 }
alarmSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable and
calculating the value to be compared against the
thresholds. If the value of this object is
absoluteValue(1), the value of the selected variable
will be compared directly with the thresholds at the
end of the sampling interval. If the value of this
object is deltaValue(2), the value of the selected
variable at the last sample will be subtracted from
the current value, and the difference compared with
the thresholds.
alarmSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable and
calculating the value to be compared against the
thresholds. If the value of this object is
absoluteValue(1), the value of the selected variable
will be compared directly with the thresholds at the
end of the sampling interval. If the value of this
object is deltaValue(2), the value of the selected
variable at the last sample will be subtracted from
the current value, and the difference compared with
the thresholds.
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 4 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 4 }
alarmValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the statistic during the last sampling period. For example, if the sample type is deltaValue, this value will be the difference between the samples at the beginning and end of the period. If the sample type is absoluteValue, this value will be the sampled value at the end of the period.
alarmValue对象类型语法整数32 MAX-ACCESS只读状态当前说明“上次采样期间的统计值。例如，如果样本类型为deltaValue，则该值将是时段开始和结束时样本之间的差值。如果采样类型为absoluteValue，则该值将是周期结束时的采样值。
This is the value that is compared with the rising and falling thresholds.
这是与上升和下降阈值进行比较的值。
The value during the current sampling period is not
made available until the period is completed and will
remain available until the next period completes."
::= { alarmEntry 5 }
The value during the current sampling period is not
made available until the period is completed and will
remain available until the next period completes."
::= { alarmEntry 5 }
alarmStartupAlarm OBJECT-TYPE
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The alarm that may be sent when this entry is first
set to valid. If the first sample after this entry
becomes valid is greater than or equal to the
risingThreshold and alarmStartupAlarm is equal to
risingAlarm(1) or risingOrFallingAlarm(3), then a single
rising alarm will be generated. If the first sample
after this entry becomes valid is less than or equal
to the fallingThreshold and alarmStartupAlarm is equal
to fallingAlarm(2) or risingOrFallingAlarm(3), then a
single falling alarm will be generated.
alarmStartupAlarm OBJECT-TYPE
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The alarm that may be sent when this entry is first
set to valid. If the first sample after this entry
becomes valid is greater than or equal to the
risingThreshold and alarmStartupAlarm is equal to
risingAlarm(1) or risingOrFallingAlarm(3), then a single
rising alarm will be generated. If the first sample
after this entry becomes valid is less than or equal
to the fallingThreshold and alarmStartupAlarm is equal
to fallingAlarm(2) or risingOrFallingAlarm(3), then a
single falling alarm will be generated.
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 6 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 6 }
alarmRisingThreshold OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3).
alarmRisingThreshold对象类型语法整数32 MAX-ACCESS读取创建状态当前描述“抽样统计的阈值。当当前采样值大于或等于此阈值，且上次采样间隔的值小于此阈值时，将生成单个事件。如果此条目生效后的第一个样本大于或等于此阈值，并且关联的报警StartupAlarm等于risingAlarm（1）或risingOrAllingAlarm（3），则也将生成单个事件。
After a rising event is generated, another such event
在一个上升事件产生后，另一个这样的事件
will not be generated until the sampled value falls below this threshold and reaches the alarmFallingThreshold.
直到采样值低于此阈值并达到alarmFallingThreshold，才会生成。
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 7 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 7 }
alarmFallingThreshold OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3).
alarmFallingThreshold对象类型语法整数32 MAX-ACCESS读取创建状态当前描述“抽样统计的阈值。当当前采样值小于或等于此阈值，且上次采样间隔的值大于此阈值时，将生成单个事件。如果此条目生效后的第一个样本小于或等于此阈值，且相关报警StartupAlarm等于fallingAlarm（2）或RisingorAllingAlarm（3），则也将生成单个事件。
After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the alarmRisingThreshold.
在产生下降事件后，在采样值上升到该阈值以上并达到报警阈值之前，不会产生另一个此类事件。
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 8 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 8 }
alarmRisingEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index.
alarmRisingEventIndex对象类型语法整数32（0..65535）MAX-ACCESS读取创建状态当前说明“超过上升阈值时使用的eventEntry索引。由该索引的特定值标识的eventEntry与由eventIndex对象的相同值标识的eventEntry相同。如果eventTable中没有相应的条目，则不存在关联。特别是，如果该值为零，则不会生成关联事件，因为零不是有效的事件索引。
This object may not be modified if the associated
如果关联的
alarmStatus object is equal to valid(1)."
::= { alarmEntry 9 }
alarmStatus object is equal to valid(1)."
::= { alarmEntry 9 }
alarmFallingEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index.
alarmFallingEventIndex对象类型语法整数32（0..65535）MAX-ACCESS读取创建状态当前描述“超过下降阈值时使用的eventEntry索引。由该索引的特定值标识的eventEntry与由eventIndex对象的相同值标识的eventEntry相同。如果eventTable中没有相应的条目，则不存在关联。特别是，如果该值为零，则不会生成关联事件，因为零不是有效的事件索引。
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 10 }
This object may not be modified if the associated
alarmStatus object is equal to valid(1)."
::= { alarmEntry 10 }
alarmOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { alarmEntry 11 }
alarmOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { alarmEntry 11 }
alarmStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this alarm entry."
::= { alarmEntry 12 }
alarmStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this alarm entry."
::= { alarmEntry 12 }
-- The Host Group
--主机组
-- Implementation of the Host group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The host group discovers new hosts on the network by
-- keeping a list of source and destination MAC Addresses seen
-- in good packets. For each of these addresses, the host group
-- Implementation of the Host group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The host group discovers new hosts on the network by
-- keeping a list of source and destination MAC Addresses seen
-- in good packets. For each of these addresses, the host group
-- keeps a set of statistics. The hostControlTable controls
-- which interfaces this function is performed on, and contains
-- some information about the process. On behalf of each
-- hostControlEntry, data is collected on an interface and placed
-- in both the hostTable and the hostTimeTable. If the
-- monitoring device finds itself short of resources, it may
-- delete entries as needed. It is suggested that the device
-- delete the least recently used entries first.
-- keeps a set of statistics. The hostControlTable controls
-- which interfaces this function is performed on, and contains
-- some information about the process. On behalf of each
-- hostControlEntry, data is collected on an interface and placed
-- in both the hostTable and the hostTimeTable. If the
-- monitoring device finds itself short of resources, it may
-- delete entries as needed. It is suggested that the device
-- delete the least recently used entries first.
-- The hostTable contains entries for each address discovered on
-- a particular interface. Each entry contains statistical
-- data about that host. This table is indexed by the
-- MAC address of the host, through which a random access
-- may be achieved.
-- The hostTable contains entries for each address discovered on
-- a particular interface. Each entry contains statistical
-- data about that host. This table is indexed by the
-- MAC address of the host, through which a random access
-- may be achieved.
-- The hostTimeTable contains data in the same format as the
-- hostTable, and must contain the same set of hosts, but is
-- indexed using hostTimeCreationOrder rather than hostAddress.
-- The hostTimeCreationOrder is an integer which reflects
-- the relative order in which a particular entry was discovered
-- and thus inserted into the table. As this order, and thus
-- the index, is among those entries currently in the table,
-- the index for a particular entry may change if an
-- (earlier) entry is deleted. Thus the association between
-- hostTimeCreationOrder and hostTimeEntry may be broken at
-- any time.
-- The hostTimeTable contains data in the same format as the
-- hostTable, and must contain the same set of hosts, but is
-- indexed using hostTimeCreationOrder rather than hostAddress.
-- The hostTimeCreationOrder is an integer which reflects
-- the relative order in which a particular entry was discovered
-- and thus inserted into the table. As this order, and thus
-- the index, is among those entries currently in the table,
-- the index for a particular entry may change if an
-- (earlier) entry is deleted. Thus the association between
-- hostTimeCreationOrder and hostTimeEntry may be broken at
-- any time.
-- The hostTimeTable has two important uses. The first is the
-- fast download of this potentially large table. Because the
-- index of this table runs from 1 to the size of the table,
-- inclusive, its values are predictable. This allows very
-- efficient packing of variables into SNMP PDU's and allows
-- a table transfer to have multiple packets outstanding.
-- These benefits increase transfer rates tremendously.
-- The hostTimeTable has two important uses. The first is the
-- fast download of this potentially large table. Because the
-- index of this table runs from 1 to the size of the table,
-- inclusive, its values are predictable. This allows very
-- efficient packing of variables into SNMP PDU's and allows
-- a table transfer to have multiple packets outstanding.
-- These benefits increase transfer rates tremendously.
-- The second use of the hostTimeTable is the efficient discovery
-- by the management station of new entries added to the table.
-- After the management station has downloaded the entire table,
-- it knows that new entries will be added immediately after the
-- end of the current table. It can thus detect new entries there
-- and retrieve them easily.
-- The second use of the hostTimeTable is the efficient discovery
-- by the management station of new entries added to the table.
-- After the management station has downloaded the entire table,
-- it knows that new entries will be added immediately after the
-- end of the current table. It can thus detect new entries there
-- and retrieve them easily.
-- Because the association between hostTimeCreationOrder and
-- hostTimeEntry may be broken at any time, the management
-- station must monitor the related hostControlLastDeleteTime
-- object. When the management station thus detects a deletion,
-- it must assume that any such associations have been broken,
-- and invalidate any it has stored locally. This includes
-- Because the association between hostTimeCreationOrder and
-- hostTimeEntry may be broken at any time, the management
-- station must monitor the related hostControlLastDeleteTime
-- object. When the management station thus detects a deletion,
-- it must assume that any such associations have been broken,
-- and invalidate any it has stored locally. This includes
-- restarting any download of the hostTimeTable that may have been
-- in progress, as well as rediscovering the end of the
-- hostTimeTable so that it may detect new entries. If the
-- management station does not detect the broken association,
-- it may continue to refer to a particular host by its
-- creationOrder while unwittingly retrieving the data associated
-- with another host entirely. If this happens while downloading
-- the host table, the management station may fail to download
-- all of the entries in the table.
-- restarting any download of the hostTimeTable that may have been
-- in progress, as well as rediscovering the end of the
-- hostTimeTable so that it may detect new entries. If the
-- management station does not detect the broken association,
-- it may continue to refer to a particular host by its
-- creationOrder while unwittingly retrieving the data associated
-- with another host entirely. If this happens while downloading
-- the host table, the management station may fail to download
-- all of the entries in the table.
hostControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of host table control entries."
::= { hosts 1 }
hostControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of host table control entries."
::= { hosts 1 }
hostControlEntry OBJECT-TYPE
SYNTAX HostControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up the discovery of hosts
on a particular interface and the collection of statistics
about these hosts. For example, an instance of the
hostControlTableSize object might be named
hostControlTableSize.1"
INDEX { hostControlIndex }
::= { hostControlTable 1 }
hostControlEntry OBJECT-TYPE
SYNTAX HostControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that set up the discovery of hosts
on a particular interface and the collection of statistics
about these hosts. For example, an instance of the
hostControlTableSize object might be named
hostControlTableSize.1"
INDEX { hostControlIndex }
::= { hostControlTable 1 }
HostControlEntry ::= SEQUENCE {
HostControlEntry ::= SEQUENCE {
hostControlIndex Integer32, hostControlDataSource OBJECT IDENTIFIER, hostControlTableSize Integer32, hostControlLastDeleteTime TimeTicks, hostControlOwner OwnerString, hostControlStatus EntryStatus }
hostControlIndex整数32、hostControlDataSource对象标识符、hostControlTableSize整数32、HostControlAstDeleteTime时间标记、hostControlOwner所有者字符串、hostControlStatus EntryStatus}
hostControlIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that uniquely identifies an entry in the
hostControlIndex对象类型语法整数32（1..65535）MAX-ACCESS只读状态当前描述“唯一标识
hostControl table. Each such entry defines
a function that discovers hosts on a particular interface
and places statistics about them in the hostTable and
the hostTimeTable on behalf of this hostControlEntry."
::= { hostControlEntry 1 }
hostControl table. Each such entry defines
a function that discovers hosts on a particular interface
and places statistics about them in the hostTable and
the hostTimeTable on behalf of this hostControlEntry."
::= { hostControlEntry 1 }
hostControlDataSource OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies the source of the data for this instance of the host function. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1.
hostControlDataSource对象类型语法对象标识符MAX-ACCESS读取创建状态当前描述“此对象标识此主机函数实例的数据源。此源可以是此设备上的任何接口。为了识别特定接口，该对象应识别RFC 2233[17]中定义的所需接口的ifIndex对象实例。例如，如果一个条目要从接口#1接收数据，则该对象将设置为ifIndex.1。
The statistics in this group reflect all packets on the local network segment attached to the identified interface.
此组中的统计信息反映连接到标识接口的本地网段上的所有数据包。
An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry.
代理可能知道，也可能不知道接口的媒体是否发生了根本性的更改，是否需要对此条目进行失效处理。例如，一个可热插拔的以太网卡可以被拔出并替换为令牌环卡。在这种情况下，如果代理知道该更改，建议其使该条目无效。
This object may not be modified if the associated
hostControlStatus object is equal to valid(1)."
::= { hostControlEntry 2 }
This object may not be modified if the associated
hostControlStatus object is equal to valid(1)."
::= { hostControlEntry 2 }
hostControlTableSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of hostEntries in the hostTable and the
hostTimeTable associated with this hostControlEntry."
::= { hostControlEntry 3 }
hostControlTableSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of hostEntries in the hostTable and the
hostTimeTable associated with this hostControlEntry."
::= { hostControlEntry 3 }
hostControlLastDeleteTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only
hostControlLastDeleteTime对象类型语法TimeTicks MAX-ACCESS只读
STATUS current
DESCRIPTION
"The value of sysUpTime when the last entry
was deleted from the portion of the hostTable
associated with this hostControlEntry. If no
deletions have occurred, this value shall be zero."
::= { hostControlEntry 4 }
STATUS current
DESCRIPTION
"The value of sysUpTime when the last entry
was deleted from the portion of the hostTable
associated with this hostControlEntry. If no
deletions have occurred, this value shall be zero."
::= { hostControlEntry 4 }
hostControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hostControlEntry 5 }
hostControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hostControlEntry 5 }
hostControlStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this hostControl entry.
hostControlStatus对象类型语法EntryStatus MAX-ACCESS读取创建状态当前描述“此hostControl条目的状态。
If this object is not equal to valid(1), all associated
entries in the hostTable, hostTimeTable, and the
hostTopNTable shall be deleted by the agent."
::= { hostControlEntry 6 }
If this object is not equal to valid(1), all associated
entries in the hostTable, hostTimeTable, and the
hostTopNTable shall be deleted by the agent."
::= { hostControlEntry 6 }
hostTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of host entries."
::= { hosts 2 }
hostTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of host entries."
::= { hosts 2 }
hostEntry OBJECT-TYPE
SYNTAX HostEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for a particular host that has
been discovered on an interface of this device. For example,
an instance of the hostOutBroadcastPkts object might be
named hostOutBroadcastPkts.1.6.8.0.32.27.3.176"
INDEX { hostIndex, hostAddress }
::= { hostTable 1 }
hostEntry OBJECT-TYPE
SYNTAX HostEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for a particular host that has
been discovered on an interface of this device. For example,
an instance of the hostOutBroadcastPkts object might be
named hostOutBroadcastPkts.1.6.8.0.32.27.3.176"
INDEX { hostIndex, hostAddress }
::= { hostTable 1 }
HostEntry ::= SEQUENCE {
hostAddress OCTET STRING,
hostCreationOrder Integer32,
hostIndex Integer32,
hostInPkts Counter32,
hostOutPkts Counter32,
hostInOctets Counter32,
hostOutOctets Counter32,
hostOutErrors Counter32,
hostOutBroadcastPkts Counter32,
hostOutMulticastPkts Counter32
}
HostEntry ::= SEQUENCE {
hostAddress OCTET STRING,
hostCreationOrder Integer32,
hostIndex Integer32,
hostInPkts Counter32,
hostOutPkts Counter32,
hostInOctets Counter32,
hostOutOctets Counter32,
hostOutErrors Counter32,
hostOutBroadcastPkts Counter32,
hostOutMulticastPkts Counter32
}
hostAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostEntry 1 }
hostAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostEntry 1 }
hostCreationOrder OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that defines the relative ordering of the creation time of hosts captured for a particular hostControlEntry. This index shall be between 1 and N, where N is the value of the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later.
hostCreationOrder对象类型语法整数32（1..65535）最大访问只读状态当前说明定义为特定hostControlEntry捕获的主机创建时间的相对顺序的索引。该索引应介于1和N之间，其中N是相关hostControlTableSize的值。索引的顺序是基于每个条目插入表中的顺序，在表中，较早添加的条目的索引值低于较晚添加的条目的索引值。
It is important to note that the order for a
particular entry may change as an (earlier) entry
is deleted from the table. Because this order may
change, management stations should make use of the
hostControlLastDeleteTime variable in the
hostControlEntry associated with the relevant
portion of the hostTable. By observing
this variable, the management station may detect
the circumstances where a previous association
between a value of hostCreationOrder
and a hostEntry may no longer hold."
::= { hostEntry 2 }
It is important to note that the order for a
particular entry may change as an (earlier) entry
is deleted from the table. Because this order may
change, management stations should make use of the
hostControlLastDeleteTime variable in the
hostControlEntry associated with the relevant
portion of the hostTable. By observing
this variable, the management station may detect
the circumstances where a previous association
between a value of hostCreationOrder
and a hostEntry may no longer hold."
::= { hostEntry 2 }
hostIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected host statistics of which
this entry is a part. The set of hosts
identified by a particular value of this
index is associated with the hostControlEntry
as identified by the same value of hostControlIndex."
::= { hostEntry 3 }
hostIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected host statistics of which
this entry is a part. The set of hosts
identified by a particular value of this
index is associated with the hostControlEntry
as identified by the same value of hostControlIndex."
::= { hostEntry 3 }
hostInPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted to this
address since it was added to the hostTable."
::= { hostEntry 4 }
hostInPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted to this
address since it was added to the hostTable."
::= { hostEntry 4 }
hostOutPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, including bad packets, transmitted
by this address since it was added to the hostTable."
::= { hostEntry 5 }
hostOutPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets, including bad packets, transmitted
by this address since it was added to the hostTable."
::= { hostEntry 5 }
hostInOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted to this address since
it was added to the hostTable (excluding framing
bits but including FCS octets), except for those
octets in bad packets."
::= { hostEntry 6 }
hostInOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted to this address since
it was added to the hostTable (excluding framing
bits but including FCS octets), except for those
octets in bad packets."
::= { hostEntry 6 }
hostOutOctets OBJECT-TYPE SYNTAX Counter32 UNITS "Octets" MAX-ACCESS read-only
hostOutOctets对象类型语法计数器32个单位“八位字节”最大访问权限只读
STATUS current
DESCRIPTION
"The number of octets transmitted by this address since
it was added to the hostTable (excluding framing
bits but including FCS octets), including those
octets in bad packets."
::= { hostEntry 7 }
STATUS current
DESCRIPTION
"The number of octets transmitted by this address since
it was added to the hostTable (excluding framing
bits but including FCS octets), including those
octets in bad packets."
::= { hostEntry 7 }
hostOutErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted by this address
since this host was added to the hostTable."
::= { hostEntry 8 }
hostOutErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted by this address
since this host was added to the hostTable."
::= { hostEntry 8 }
hostOutBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to the broadcast address
since this host was added to the hostTable."
::= { hostEntry 9 }
hostOutBroadcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to the broadcast address
since this host was added to the hostTable."
::= { hostEntry 9 }
hostOutMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to a multicast address
since this host was added to the hostTable.
Note that this number does not include packets
directed to the broadcast address."
::= { hostEntry 10 }
hostOutMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to a multicast address
since this host was added to the hostTable.
Note that this number does not include packets
directed to the broadcast address."
::= { hostEntry 10 }
-- host Time Table
--主持人时间表
hostTimeTable OBJECT-TYPE SYNTAX SEQUENCE OF HostTimeEntry MAX-ACCESS not-accessible STATUS current
HostTimeName对象类型语法HostTimeEntry MAX-ACCESS的序列不可访问状态当前
DESCRIPTION
"A list of time-ordered host table entries."
::= { hosts 3 }
DESCRIPTION
"A list of time-ordered host table entries."
::= { hosts 3 }
hostTimeEntry OBJECT-TYPE
SYNTAX HostTimeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for a particular host that has
been discovered on an interface of this device. This
collection includes the relative ordering of the creation
time of this object. For example, an instance of the
hostTimeOutBroadcastPkts object might be named
hostTimeOutBroadcastPkts.1.687"
INDEX { hostTimeIndex, hostTimeCreationOrder }
::= { hostTimeTable 1 }
hostTimeEntry OBJECT-TYPE
SYNTAX HostTimeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for a particular host that has
been discovered on an interface of this device. This
collection includes the relative ordering of the creation
time of this object. For example, an instance of the
hostTimeOutBroadcastPkts object might be named
hostTimeOutBroadcastPkts.1.687"
INDEX { hostTimeIndex, hostTimeCreationOrder }
::= { hostTimeTable 1 }
HostTimeEntry ::= SEQUENCE {
hostTimeAddress OCTET STRING,
hostTimeCreationOrder Integer32,
hostTimeIndex Integer32,
hostTimeInPkts Counter32,
hostTimeOutPkts Counter32,
hostTimeInOctets Counter32,
hostTimeOutOctets Counter32,
hostTimeOutErrors Counter32,
hostTimeOutBroadcastPkts Counter32,
hostTimeOutMulticastPkts Counter32
}
HostTimeEntry ::= SEQUENCE {
hostTimeAddress OCTET STRING,
hostTimeCreationOrder Integer32,
hostTimeIndex Integer32,
hostTimeInPkts Counter32,
hostTimeOutPkts Counter32,
hostTimeInOctets Counter32,
hostTimeOutOctets Counter32,
hostTimeOutErrors Counter32,
hostTimeOutBroadcastPkts Counter32,
hostTimeOutMulticastPkts Counter32
}
hostTimeAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostTimeEntry 1 }
hostTimeAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostTimeEntry 1 }
hostTimeCreationOrder OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that uniquely identifies an entry in the hostTime table among those entries associated with the same hostControlEntry. This index shall be between 1 and N, where N is the value of
hostTimeCreationOrder对象类型语法整数32（1..65535）MAX-ACCESS只读状态当前描述“在与同一hostControlEntry关联的条目中唯一标识hostTime表中条目的索引。此索引应介于1和N之间，其中N是
the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later. Thus the management station has the ability to learn of new entries added to this table without downloading the entire table.
关联的hostControlTableSize。索引的顺序是基于每个条目插入表中的顺序，在表中，较早添加的条目的索引值低于较晚添加的条目的索引值。因此，管理站能够了解添加到此表中的新条目，而无需下载整个表。
It is important to note that the index for a
particular entry may change as an (earlier) entry
is deleted from the table. Because this order may
change, management stations should make use of the
hostControlLastDeleteTime variable in the
hostControlEntry associated with the relevant
portion of the hostTimeTable. By observing
this variable, the management station may detect
the circumstances where a download of the table
may have missed entries, and where a previous
association between a value of hostTimeCreationOrder
and a hostTimeEntry may no longer hold."
::= { hostTimeEntry 2 }
It is important to note that the index for a
particular entry may change as an (earlier) entry
is deleted from the table. Because this order may
change, management stations should make use of the
hostControlLastDeleteTime variable in the
hostControlEntry associated with the relevant
portion of the hostTimeTable. By observing
this variable, the management station may detect
the circumstances where a download of the table
may have missed entries, and where a previous
association between a value of hostTimeCreationOrder
and a hostTimeEntry may no longer hold."
::= { hostTimeEntry 2 }
hostTimeIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected host statistics of which
this entry is a part. The set of hosts
identified by a particular value of this
index is associated with the hostControlEntry
as identified by the same value of hostControlIndex."
::= { hostTimeEntry 3 }
hostTimeIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected host statistics of which
this entry is a part. The set of hosts
identified by a particular value of this
index is associated with the hostControlEntry
as identified by the same value of hostControlIndex."
::= { hostTimeEntry 3 }
hostTimeInPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted to this
address since it was added to the hostTimeTable."
::= { hostTimeEntry 4 }
hostTimeInPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted to this
address since it was added to the hostTimeTable."
::= { hostTimeEntry 4 }
hostTimeOutPkts OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only
hostTimeOutPkts对象类型语法计数器32个单位“数据包”最大访问权限只读
STATUS current
DESCRIPTION
"The number of packets, including bad packets, transmitted
by this address since it was added to the hostTimeTable."
::= { hostTimeEntry 5 }
STATUS current
DESCRIPTION
"The number of packets, including bad packets, transmitted
by this address since it was added to the hostTimeTable."
::= { hostTimeEntry 5 }
hostTimeInOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted to this address since
it was added to the hostTimeTable (excluding framing
bits but including FCS octets), except for those
octets in bad packets."
::= { hostTimeEntry 6 }
hostTimeInOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted to this address since
it was added to the hostTimeTable (excluding framing
bits but including FCS octets), except for those
octets in bad packets."
::= { hostTimeEntry 6 }
hostTimeOutOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted by this address since
it was added to the hostTimeTable (excluding framing
bits but including FCS octets), including those
octets in bad packets."
::= { hostTimeEntry 7 }
hostTimeOutOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted by this address since
it was added to the hostTimeTable (excluding framing
bits but including FCS octets), including those
octets in bad packets."
::= { hostTimeEntry 7 }
hostTimeOutErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted by this address
since this host was added to the hostTimeTable."
::= { hostTimeEntry 8 }
hostTimeOutErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted by this address
since this host was added to the hostTimeTable."
::= { hostTimeEntry 8 }
hostTimeOutBroadcastPkts OBJECT-TYPE SYNTAX Counter32 UNITS "Packets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of good packets transmitted by this address that were directed to the broadcast address
hostTimeOutBroadcastPkts对象类型语法计数器32单元“数据包”最大访问只读状态当前描述“此地址发送到广播地址的良好数据包数
since this host was added to the hostTimeTable."
::= { hostTimeEntry 9 }
since this host was added to the hostTimeTable."
::= { hostTimeEntry 9 }
hostTimeOutMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to a multicast address
since this host was added to the hostTimeTable.
Note that this number does not include packets directed
to the broadcast address."
::= { hostTimeEntry 10 }
hostTimeOutMulticastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of good packets transmitted by this
address that were directed to a multicast address
since this host was added to the hostTimeTable.
Note that this number does not include packets directed
to the broadcast address."
::= { hostTimeEntry 10 }
-- The Host Top "N" Group
--主机前“N”组
-- Implementation of the Host Top N group is optional. The Host Top N
-- group requires the implementation of the host group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Host Top N group is used to prepare reports that describe
-- the hosts that top a list ordered by one of their statistics.
-- The available statistics are samples of one of their
-- base statistics, over an interval specified by the management
-- station. Thus, these statistics are rate based. The management
-- station also selects how many such hosts are reported.
-- Implementation of the Host Top N group is optional. The Host Top N
-- group requires the implementation of the host group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Host Top N group is used to prepare reports that describe
-- the hosts that top a list ordered by one of their statistics.
-- The available statistics are samples of one of their
-- base statistics, over an interval specified by the management
-- station. Thus, these statistics are rate based. The management
-- station also selects how many such hosts are reported.
-- The hostTopNControlTable is used to initiate the generation of
-- such a report. The management station may select the parameters
-- of such a report, such as which interface, which statistic,
-- how many hosts, and the start and stop times of the sampling.
-- When the report is prepared, entries are created in the
-- hostTopNTable associated with the relevant hostTopNControlEntry.
-- These entries are static for each report after it has been
-- prepared.
-- The hostTopNControlTable is used to initiate the generation of
-- such a report. The management station may select the parameters
-- of such a report, such as which interface, which statistic,
-- how many hosts, and the start and stop times of the sampling.
-- When the report is prepared, entries are created in the
-- hostTopNTable associated with the relevant hostTopNControlEntry.
-- These entries are static for each report after it has been
-- prepared.
hostTopNControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of top N host control entries."
::= { hostTopN 1 }
hostTopNControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of top N host control entries."
::= { hostTopN 1 }
hostTopNControlEntry OBJECT-TYPE
hostTopNControlEntry对象类型
SYNTAX HostTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that control the creation of a report
of the top N hosts according to several metrics. For
example, an instance of the hostTopNDuration object might
be named hostTopNDuration.3"
INDEX { hostTopNControlIndex }
::= { hostTopNControlTable 1 }
SYNTAX HostTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that control the creation of a report
of the top N hosts according to several metrics. For
example, an instance of the hostTopNDuration object might
be named hostTopNDuration.3"
INDEX { hostTopNControlIndex }
::= { hostTopNControlTable 1 }
HostTopNControlEntry ::= SEQUENCE {
hostTopNControlIndex Integer32,
hostTopNHostIndex Integer32,
hostTopNRateBase INTEGER,
hostTopNTimeRemaining Integer32,
hostTopNDuration Integer32,
hostTopNRequestedSize Integer32,
hostTopNGrantedSize Integer32,
hostTopNStartTime TimeTicks,
hostTopNOwner OwnerString,
hostTopNStatus EntryStatus
}
HostTopNControlEntry ::= SEQUENCE {
hostTopNControlIndex Integer32,
hostTopNHostIndex Integer32,
hostTopNRateBase INTEGER,
hostTopNTimeRemaining Integer32,
hostTopNDuration Integer32,
hostTopNRequestedSize Integer32,
hostTopNGrantedSize Integer32,
hostTopNStartTime TimeTicks,
hostTopNOwner OwnerString,
hostTopNStatus EntryStatus
}
hostTopNControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the hostTopNControl table. Each such
entry defines one top N report prepared for
one interface."
::= { hostTopNControlEntry 1 }
hostTopNControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the hostTopNControl table. Each such
entry defines one top N report prepared for
one interface."
::= { hostTopNControlEntry 1 }
hostTopNHostIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The host table for which a top N report will be prepared on behalf of this entry. The host table identified by a particular value of this index is associated with the same host table as identified by the same value of hostIndex.
hostTopNHostIndex对象类型语法整数32（1..65535）MAX-ACCESS read create STATUS current DESCRIPTION“将为此条目准备top N报告的主机表。由此索引的特定值标识的主机表与由相同hostIndex值标识的相同主机表相关联。
This object may not be modified if the associated hostTopNStatus object is equal to valid(1)."
如果关联的HostTopStatus对象等于valid（1），则不能修改此对象。“
::= { hostTopNControlEntry 2 }
::= { hostTopNControlEntry 2 }
hostTopNRateBase OBJECT-TYPE
SYNTAX INTEGER {
hostTopNInPkts(1),
hostTopNOutPkts(2),
hostTopNInOctets(3),
hostTopNOutOctets(4),
hostTopNOutErrors(5),
hostTopNOutBroadcastPkts(6),
hostTopNOutMulticastPkts(7)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The variable for each host that the hostTopNRate
variable is based upon.
hostTopNRateBase OBJECT-TYPE
SYNTAX INTEGER {
hostTopNInPkts(1),
hostTopNOutPkts(2),
hostTopNInOctets(3),
hostTopNOutOctets(4),
hostTopNOutErrors(5),
hostTopNOutBroadcastPkts(6),
hostTopNOutMulticastPkts(7)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The variable for each host that the hostTopNRate
variable is based upon.
This object may not be modified if the associated
hostTopNStatus object is equal to valid(1)."
::= { hostTopNControlEntry 3 }
This object may not be modified if the associated
hostTopNStatus object is equal to valid(1)."
::= { hostTopNControlEntry 3 }
hostTopNTimeRemaining OBJECT-TYPE SYNTAX Integer32 UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated hostTopNDuration object.
hostTopNTimeRemaining对象类型语法整数32单位“秒”最大访问读取创建状态当前描述“当前正在收集的报告中剩余的秒数。当管理工作站修改此对象时，将启动一个新集合，可能会中止当前正在运行的报告。新值用作此报告的请求持续时间，该报告将加载到关联的HostToPenduration对象中。
When this object is set to a non-zero value, any
associated hostTopNEntries shall be made
inaccessible by the monitor. While the value of this
object is non-zero, it decrements by one per second until
it reaches zero. During this time, all associated
hostTopNEntries shall remain inaccessible. At the time
that this object decrements to zero, the report is made
accessible in the hostTopNTable. Thus, the hostTopN
table needs to be created only at the end of the collection
interval."
DEFVAL { 0 }
::= { hostTopNControlEntry 4 }
When this object is set to a non-zero value, any
associated hostTopNEntries shall be made
inaccessible by the monitor. While the value of this
object is non-zero, it decrements by one per second until
it reaches zero. During this time, all associated
hostTopNEntries shall remain inaccessible. At the time
that this object decrements to zero, the report is made
accessible in the hostTopNTable. Thus, the hostTopN
table needs to be created only at the end of the collection
interval."
DEFVAL { 0 }
::= { hostTopNControlEntry 4 }
hostTopNDuration OBJECT-TYPE SYNTAX Integer32 UNITS "Seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval.
hostTopNDuration对象类型语法整数32个单位“秒”MAX-ACCESS只读状态当前描述“此报告在上次采样间隔内采集的秒数，或者如果当前正在采集此报告，则在此采样间隔内采集此报告的秒数。
When the associated hostTopNTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the hostTopNTimeRemaining is set.
当设置了关联的hostTopNTimeRemaining对象时，探测器应将该对象设置为相同的值，并且在下次设置hostTopNTimeRemaining之前不得修改该对象。
This value shall be zero if no reports have been
requested for this hostTopNControlEntry."
DEFVAL { 0 }
::= { hostTopNControlEntry 5 }
This value shall be zero if no reports have been
requested for this hostTopNControlEntry."
DEFVAL { 0 }
::= { hostTopNControlEntry 5 }
hostTopNRequestedSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of hosts requested for the top N table.
hostTopNRequestedSize对象类型语法整数32 MAX-ACCESS read create STATUS current DESCRIPTION“为top N表请求的最大主机数。
When this object is created or modified, the probe
should set hostTopNGrantedSize as closely to this
object as is possible for the particular probe
implementation and available resources."
DEFVAL { 10 }
::= { hostTopNControlEntry 6 }
When this object is created or modified, the probe
should set hostTopNGrantedSize as closely to this
object as is possible for the particular probe
implementation and available resources."
DEFVAL { 10 }
::= { hostTopNControlEntry 6 }
hostTopNGrantedSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of hosts in the top N table.
hostTopNGrantedSize对象类型语法Integer32 MAX-ACCESS只读状态当前说明“top N表中的最大主机数。
When the associated hostTopNRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available
创建或修改关联的hostTopNRequestedSize对象时，探测器应将该对象设置为尽可能接近特定实现和可用的请求值
resources. The probe must not lower this value except as a result of a set to the associated hostTopNRequestedSize object.
资源。探测器不得降低此值，除非设置为关联的hostTopNRequestedSize对象。
Hosts with the highest value of hostTopNRate shall be
placed in this table in decreasing order of this rate
until there is no more room or until there are no more
hosts."
::= { hostTopNControlEntry 7 }
Hosts with the highest value of hostTopNRate shall be
placed in this table in decreasing order of this rate
until there is no more room or until there are no more
hosts."
::= { hostTopNControlEntry 7 }
hostTopNStartTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this top N report was
last started. In other words, this is the time that
the associated hostTopNTimeRemaining object was
modified to start the requested report."
::= { hostTopNControlEntry 8 }
hostTopNStartTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this top N report was
last started. In other words, this is the time that
the associated hostTopNTimeRemaining object was
modified to start the requested report."
::= { hostTopNControlEntry 8 }
hostTopNOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hostTopNControlEntry 9 }
hostTopNOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hostTopNControlEntry 9 }
hostTopNStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this hostTopNControl entry.
hostTopNStatus对象类型语法EntryStatus MAX-ACCESS读取创建状态当前描述“此hostTopNControl条目的状态。
If this object is not equal to valid(1), all associated
hostTopNEntries shall be deleted by the agent."
::= { hostTopNControlEntry 10 }
If this object is not equal to valid(1), all associated
hostTopNEntries shall be deleted by the agent."
::= { hostTopNControlEntry 10 }
hostTopNTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of top N host entries."
::= { hostTopN 2 }
hostTopNTable OBJECT-TYPE
SYNTAX SEQUENCE OF HostTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of top N host entries."
::= { hostTopN 2 }
hostTopNEntry OBJECT-TYPE
SYNTAX HostTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of statistics for a host that is part of a top N
report. For example, an instance of the hostTopNRate
object might be named hostTopNRate.3.10"
INDEX { hostTopNReport, hostTopNIndex }
::= { hostTopNTable 1 }
hostTopNEntry OBJECT-TYPE
SYNTAX HostTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of statistics for a host that is part of a top N
report. For example, an instance of the hostTopNRate
object might be named hostTopNRate.3.10"
INDEX { hostTopNReport, hostTopNIndex }
::= { hostTopNTable 1 }
HostTopNEntry ::= SEQUENCE {
hostTopNReport Integer32,
hostTopNIndex Integer32,
hostTopNAddress OCTET STRING,
hostTopNRate Integer32
}
HostTopNEntry ::= SEQUENCE {
hostTopNReport Integer32,
hostTopNIndex Integer32,
hostTopNAddress OCTET STRING,
hostTopNRate Integer32
}
hostTopNReport OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the top N report of which
this entry is a part. The set of hosts
identified by a particular value of this
object is part of the same report as identified
by the same value of the hostTopNControlIndex object."
::= { hostTopNEntry 1 }
hostTopNReport OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the top N report of which
this entry is a part. The set of hosts
identified by a particular value of this
object is part of the same report as identified
by the same value of the hostTopNControlIndex object."
::= { hostTopNEntry 1 }
hostTopNIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in
the hostTopN table among those in the same report.
This index is between 1 and N, where N is the
number of entries in this table. Increasing values
of hostTopNIndex shall be assigned to entries with
decreasing values of hostTopNRate until index N
is assigned to the entry with the lowest value of
hostTopNRate or there are no more hostTopNEntries."
::= { hostTopNEntry 2 }
hostTopNIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in
the hostTopN table among those in the same report.
This index is between 1 and N, where N is the
number of entries in this table. Increasing values
of hostTopNIndex shall be assigned to entries with
decreasing values of hostTopNRate until index N
is assigned to the entry with the lowest value of
hostTopNRate or there are no more hostTopNEntries."
::= { hostTopNEntry 2 }
hostTopNAddress OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only
HostTopNadAddress对象类型语法八位字符串最大访问权限只读
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostTopNEntry 3 }
STATUS current
DESCRIPTION
"The physical address of this host."
::= { hostTopNEntry 3 }
hostTopNRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of change in the selected variable
during this sampling interval. The selected
variable is this host's instance of the object
selected by hostTopNRateBase."
::= { hostTopNEntry 4 }
hostTopNRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of change in the selected variable
during this sampling interval. The selected
variable is this host's instance of the object
selected by hostTopNRateBase."
::= { hostTopNEntry 4 }
-- The Matrix Group
--矩阵群
-- Implementation of the Matrix group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Matrix group consists of the matrixControlTable, matrixSDTable
-- and the matrixDSTable. These tables store statistics for a
-- particular conversation between two addresses. As the device
-- detects a new conversation, including those to a non-unicast
-- address, it creates a new entry in both of the matrix tables.
-- It must only create new entries based on information
-- received in good packets. If the monitoring device finds
-- itself short of resources, it may delete entries as needed.
-- It is suggested that the device delete the least recently used
-- entries first.
-- Implementation of the Matrix group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Matrix group consists of the matrixControlTable, matrixSDTable
-- and the matrixDSTable. These tables store statistics for a
-- particular conversation between two addresses. As the device
-- detects a new conversation, including those to a non-unicast
-- address, it creates a new entry in both of the matrix tables.
-- It must only create new entries based on information
-- received in good packets. If the monitoring device finds
-- itself short of resources, it may delete entries as needed.
-- It is suggested that the device delete the least recently used
-- entries first.
matrixControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of information entries for the
traffic matrix on each interface."
::= { matrix 1 }
matrixControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of information entries for the
traffic matrix on each interface."
::= { matrix 1 }
matrixControlEntry OBJECT-TYPE SYNTAX MatrixControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a traffic matrix on a particular
matrixControlEntry对象类型语法matrixControlEntry MAX-ACCESS不可访问状态当前描述“有关特定网络上流量矩阵的信息”
interface. For example, an instance of the
matrixControlLastDeleteTime object might be named
matrixControlLastDeleteTime.1"
INDEX { matrixControlIndex }
::= { matrixControlTable 1 }
interface. For example, an instance of the
matrixControlLastDeleteTime object might be named
matrixControlLastDeleteTime.1"
INDEX { matrixControlIndex }
::= { matrixControlTable 1 }
MatrixControlEntry ::= SEQUENCE {
matrixControlIndex Integer32,
matrixControlDataSource OBJECT IDENTIFIER,
matrixControlTableSize Integer32,
matrixControlLastDeleteTime TimeTicks,
matrixControlOwner OwnerString,
matrixControlStatus EntryStatus
}
MatrixControlEntry ::= SEQUENCE {
matrixControlIndex Integer32,
matrixControlDataSource OBJECT IDENTIFIER,
matrixControlTableSize Integer32,
matrixControlLastDeleteTime TimeTicks,
matrixControlOwner OwnerString,
matrixControlStatus EntryStatus
}
matrixControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
matrixControl table. Each such entry defines
a function that discovers conversations on a particular
interface and places statistics about them in the
matrixSDTable and the matrixDSTable on behalf of this
matrixControlEntry."
::= { matrixControlEntry 1 }
matrixControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
matrixControl table. Each such entry defines
a function that discovers conversations on a particular
interface and places statistics about them in the
matrixSDTable and the matrixDSTable on behalf of this
matrixControlEntry."
::= { matrixControlEntry 1 }
matrixControlDataSource OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies the source of the data from which this entry creates a traffic matrix. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1.
matrixControlDataSource对象类型语法对象标识符MAX-ACCESS读取创建状态当前描述“此对象标识此条目创建流量矩阵的数据源。此源可以是此设备上的任何接口。为了识别特定接口，该对象应识别RFC 2233[17]中定义的所需接口的ifIndex对象实例。例如，如果一个条目要从接口#1接收数据，则该对象将设置为ifIndex.1。
The statistics in this group reflect all packets on the local network segment attached to the identified interface.
此组中的统计信息反映连接到标识接口的本地网段上的所有数据包。
An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and
代理可能知道也可能无法知道接口的介质是否发生了根本性的更改，并且
necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry.
必须使该条目无效。例如，一个可热插拔的以太网卡可以被拔出并替换为令牌环卡。在这种情况下，如果代理知道该更改，建议其使该条目无效。
This object may not be modified if the associated
matrixControlStatus object is equal to valid(1)."
::= { matrixControlEntry 2 }
This object may not be modified if the associated
matrixControlStatus object is equal to valid(1)."
::= { matrixControlEntry 2 }
matrixControlTableSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of matrixSDEntries in the matrixSDTable
for this interface. This must also be the value of
the number of entries in the matrixDSTable for this
interface."
::= { matrixControlEntry 3 }
matrixControlTableSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of matrixSDEntries in the matrixSDTable
for this interface. This must also be the value of
the number of entries in the matrixDSTable for this
interface."
::= { matrixControlEntry 3 }
matrixControlLastDeleteTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the last entry
was deleted from the portion of the matrixSDTable
or matrixDSTable associated with this matrixControlEntry.
If no deletions have occurred, this value shall be
zero."
::= { matrixControlEntry 4 }
matrixControlLastDeleteTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the last entry
was deleted from the portion of the matrixSDTable
or matrixDSTable associated with this matrixControlEntry.
If no deletions have occurred, this value shall be
zero."
::= { matrixControlEntry 4 }
matrixControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { matrixControlEntry 5 }
matrixControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { matrixControlEntry 5 }
matrixControlStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this matrixControl entry.
matrixControl状态对象类型语法EntryStatus MAX-ACCESS读取创建状态当前描述“此matrixControl条目的状态。
If this object is not equal to valid(1), all associated
entries in the matrixSDTable and the matrixDSTable
shall be deleted by the agent."
::= { matrixControlEntry 6 }
If this object is not equal to valid(1), all associated
entries in the matrixSDTable and the matrixDSTable
shall be deleted by the agent."
::= { matrixControlEntry 6 }
matrixSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixSDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of traffic matrix entries indexed by
source and destination MAC address."
::= { matrix 2 }
matrixSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixSDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of traffic matrix entries indexed by
source and destination MAC address."
::= { matrix 2 }
matrixSDEntry OBJECT-TYPE
SYNTAX MatrixSDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for communications between
two addresses on a particular interface. For example,
an instance of the matrixSDPkts object might be named
matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113"
INDEX { matrixSDIndex,
matrixSDSourceAddress, matrixSDDestAddress }
::= { matrixSDTable 1 }
matrixSDEntry OBJECT-TYPE
SYNTAX MatrixSDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for communications between
two addresses on a particular interface. For example,
an instance of the matrixSDPkts object might be named
matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113"
INDEX { matrixSDIndex,
matrixSDSourceAddress, matrixSDDestAddress }
::= { matrixSDTable 1 }
MatrixSDEntry ::= SEQUENCE {
matrixSDSourceAddress OCTET STRING,
matrixSDDestAddress OCTET STRING,
matrixSDIndex Integer32,
matrixSDPkts Counter32,
matrixSDOctets Counter32,
matrixSDErrors Counter32
}
MatrixSDEntry ::= SEQUENCE {
matrixSDSourceAddress OCTET STRING,
matrixSDDestAddress OCTET STRING,
matrixSDIndex Integer32,
matrixSDPkts Counter32,
matrixSDOctets Counter32,
matrixSDErrors Counter32
}
matrixSDSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The source physical address."
::= { matrixSDEntry 1 }
matrixSDSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The source physical address."
::= { matrixSDEntry 1 }
matrixSDDestAddress OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current
MatrixSDestAddress对象类型语法八位字符串最大访问只读状态当前
DESCRIPTION
"The destination physical address."
::= { matrixSDEntry 2 }
DESCRIPTION
"The destination physical address."
::= { matrixSDEntry 2 }
matrixSDIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected matrix statistics of which
this entry is a part. The set of matrix statistics
identified by a particular value of this index
is associated with the same matrixControlEntry
as identified by the same value of matrixControlIndex."
::= { matrixSDEntry 3 }
matrixSDIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected matrix statistics of which
this entry is a part. The set of matrix statistics
identified by a particular value of this index
is associated with the same matrixControlEntry
as identified by the same value of matrixControlIndex."
::= { matrixSDEntry 3 }
matrixSDPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets transmitted from the source
address to the destination address (this number includes
bad packets)."
::= { matrixSDEntry 4 }
matrixSDPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets transmitted from the source
address to the destination address (this number includes
bad packets)."
::= { matrixSDEntry 4 }
matrixSDOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets (excluding framing bits but
including FCS octets) contained in all packets
transmitted from the source address to the
destination address."
::= { matrixSDEntry 5 }
matrixSDOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets (excluding framing bits but
including FCS octets) contained in all packets
transmitted from the source address to the
destination address."
::= { matrixSDEntry 5 }
matrixSDErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted from
the source address to the destination address."
::= { matrixSDEntry 6 }
matrixSDErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted from
the source address to the destination address."
::= { matrixSDEntry 6 }
-- Traffic matrix tables from destination to source
--从目标到源的流量矩阵表
matrixDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of traffic matrix entries indexed by
destination and source MAC address."
::= { matrix 3 }
matrixDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF MatrixDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of traffic matrix entries indexed by
destination and source MAC address."
::= { matrix 3 }
matrixDSEntry OBJECT-TYPE
SYNTAX MatrixDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for communications between
two addresses on a particular interface. For example,
an instance of the matrixSDPkts object might be named
matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176"
INDEX { matrixDSIndex,
matrixDSDestAddress, matrixDSSourceAddress }
::= { matrixDSTable 1 }
matrixDSEntry OBJECT-TYPE
SYNTAX MatrixDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A collection of statistics for communications between
two addresses on a particular interface. For example,
an instance of the matrixSDPkts object might be named
matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176"
INDEX { matrixDSIndex,
matrixDSDestAddress, matrixDSSourceAddress }
::= { matrixDSTable 1 }
MatrixDSEntry ::= SEQUENCE {
matrixDSSourceAddress OCTET STRING,
matrixDSDestAddress OCTET STRING,
matrixDSIndex Integer32,
matrixDSPkts Counter32,
matrixDSOctets Counter32,
matrixDSErrors Counter32
}
MatrixDSEntry ::= SEQUENCE {
matrixDSSourceAddress OCTET STRING,
matrixDSDestAddress OCTET STRING,
matrixDSIndex Integer32,
matrixDSPkts Counter32,
matrixDSOctets Counter32,
matrixDSErrors Counter32
}
matrixDSSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The source physical address."
::= { matrixDSEntry 1 }
matrixDSSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The source physical address."
::= { matrixDSEntry 1 }
matrixDSDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination physical address."
::= { matrixDSEntry 2 }
matrixDSDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination physical address."
::= { matrixDSEntry 2 }
matrixDSIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected matrix statistics of which
this entry is a part. The set of matrix statistics
identified by a particular value of this index
is associated with the same matrixControlEntry
as identified by the same value of matrixControlIndex."
::= { matrixDSEntry 3 }
matrixDSIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of collected matrix statistics of which
this entry is a part. The set of matrix statistics
identified by a particular value of this index
is associated with the same matrixControlEntry
as identified by the same value of matrixControlIndex."
::= { matrixDSEntry 3 }
matrixDSPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets transmitted from the source
address to the destination address (this number includes
bad packets)."
::= { matrixDSEntry 4 }
matrixDSPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets transmitted from the source
address to the destination address (this number includes
bad packets)."
::= { matrixDSEntry 4 }
matrixDSOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets (excluding framing bits
but including FCS octets) contained in all packets
transmitted from the source address to the
destination address."
::= { matrixDSEntry 5 }
matrixDSOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets (excluding framing bits
but including FCS octets) contained in all packets
transmitted from the source address to the
destination address."
::= { matrixDSEntry 5 }
matrixDSErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted from
the source address to the destination address."
::= { matrixDSEntry 6 }
matrixDSErrors OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bad packets transmitted from
the source address to the destination address."
::= { matrixDSEntry 6 }
-- The Filter Group
--过滤器组
-- Implementation of the Filter group is optional.
--过滤器组的实现是可选的。
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Filter group allows packets to be captured with an
-- arbitrary filter expression. A logical data and
-- event stream or "channel" is formed by the packets
-- that match the filter expression.
--
-- This filter mechanism allows the creation of an arbitrary
-- logical expression with which to filter packets. Each
-- filter associated with a channel is OR'ed with the others.
-- Within a filter, any bits checked in the data and status are
-- AND'ed with respect to other bits in the same filter. The
-- NotMask also allows for checking for inequality. Finally,
-- the channelAcceptType object allows for inversion of the
-- whole equation.
--
-- If a management station wishes to receive a trap to alert it
-- that new packets have been captured and are available for
-- download, it is recommended that it set up an alarm entry that
-- monitors the value of the relevant channelMatches instance.
--
-- The channel can be turned on or off, and can also
-- generate events when packets pass through it.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Filter group allows packets to be captured with an
-- arbitrary filter expression. A logical data and
-- event stream or "channel" is formed by the packets
-- that match the filter expression.
--
-- This filter mechanism allows the creation of an arbitrary
-- logical expression with which to filter packets. Each
-- filter associated with a channel is OR'ed with the others.
-- Within a filter, any bits checked in the data and status are
-- AND'ed with respect to other bits in the same filter. The
-- NotMask also allows for checking for inequality. Finally,
-- the channelAcceptType object allows for inversion of the
-- whole equation.
--
-- If a management station wishes to receive a trap to alert it
-- that new packets have been captured and are available for
-- download, it is recommended that it set up an alarm entry that
-- monitors the value of the relevant channelMatches instance.
--
-- The channel can be turned on or off, and can also
-- generate events when packets pass through it.
filterTable OBJECT-TYPE
SYNTAX SEQUENCE OF FilterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packet filter entries."
::= { filter 1 }
filterTable OBJECT-TYPE
SYNTAX SEQUENCE OF FilterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packet filter entries."
::= { filter 1 }
filterEntry OBJECT-TYPE
SYNTAX FilterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters for a packet filter applied on a
particular interface. As an example, an instance of the
filterPktData object might be named filterPktData.12"
INDEX { filterIndex }
::= { filterTable 1 }
filterEntry OBJECT-TYPE
SYNTAX FilterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters for a packet filter applied on a
particular interface. As an example, an instance of the
filterPktData object might be named filterPktData.12"
INDEX { filterIndex }
::= { filterTable 1 }
FilterEntry ::= SEQUENCE {
filterIndex Integer32,
filterChannelIndex Integer32,
filterPktDataOffset Integer32,
FilterEntry ::= SEQUENCE {
filterIndex Integer32,
filterChannelIndex Integer32,
filterPktDataOffset Integer32,
filterPktData OCTET STRING, filterPktDataMask OCTET STRING, filterPktDataNotMask OCTET STRING, filterPktStatus Integer32, filterPktStatusMask Integer32, filterPktStatusNotMask Integer32, filterOwner OwnerString, filterStatus EntryStatus }
filterPktData八位字符串、filterPktDataMask八位字符串、filterPktDataNotMask八位字符串、filterPktStatus整数32、filterPktStatusMask整数32、filterPktStatusNotMask整数32、filterOwner OwnersString、filterStatus EntryStatus}
filterIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the filter table. Each such entry defines
one filter that is to be applied to every packet
received on an interface."
::= { filterEntry 1 }
filterIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the filter table. Each such entry defines
one filter that is to be applied to every packet
received on an interface."
::= { filterEntry 1 }
filterChannelIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object identifies the channel of which this filter
is a part. The filters identified by a particular value
of this object are associated with the same channel as
identified by the same value of the channelIndex object."
::= { filterEntry 2 }
filterChannelIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object identifies the channel of which this filter
is a part. The filters identified by a particular value
of this object are associated with the same channel as
identified by the same value of the channelIndex object."
::= { filterEntry 2 }
filterPktDataOffset OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-create STATUS current DESCRIPTION "The offset from the beginning of each packet where a match of packet data will be attempted. This offset is measured from the point in the physical layer packet after the framing bits, if any. For example, in an Ethernet frame, this point is at the beginning of the destination MAC address.
filterPktDataOffset对象类型语法整数32个单位“八位字节”最大访问读取创建状态当前说明“从试图匹配数据包数据的每个数据包开始的偏移量。该偏移量是从帧位（如果有的话）之后的物理层分组中的点开始测量的。例如，在以太网帧中，该点位于目标MAC地址的开头。
This object may not be modified if the associated filterStatus object is equal to valid(1)." DEFVAL { 0 }
如果关联的filterStatus对象等于valid（1），则不能修改此对象。“DEFVAL{0}”
::= { filterEntry 3 }
::= { filterEntry 3 }
filterPktData OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The data that is to be matched with the input packet. For each packet received, this filter and the accompanying filterPktDataMask and filterPktDataNotMask will be adjusted for the offset. The only bits relevant to this match algorithm are those that have the corresponding filterPktDataMask bit equal to one. The following three rules are then applied to every packet:
filterPktData对象类型语法八位字符串MAX-ACCESS读取创建状态当前描述“要与输入数据包匹配的数据。对于接收到的每个数据包，该过滤器以及附带的filterPktDataMask和filterPktDataNotMask将根据偏移量进行调整。与此匹配算法相关的唯一位是那些相应的filterPktDataMask位等于1的位。然后对每个数据包应用以下三条规则：
(1) If the packet is too short and does not have data corresponding to part of the filterPktData, the packet will fail this data match.
(1) 如果数据包太短并且没有与部分filterPktData对应的数据，则该数据包将使该数据匹配失败。
(2) For each relevant bit from the packet with the corresponding filterPktDataNotMask bit set to zero, if the bit from the packet is not equal to the corresponding bit from the filterPktData, then the packet will fail this data match.
(2) 对于对应filterPktDataNotMask位设置为零的数据包中的每个相关位，如果数据包中的位不等于filterPktData中的对应位，则数据包将使该数据匹配失败。
(3) If for every relevant bit from the packet with the corresponding filterPktDataNotMask bit set to one, the bit from the packet is equal to the corresponding bit from the filterPktData, then the packet will fail this data match.
(3) 如果对应的filterPktDataNotMask位设置为1的数据包中的每个相关位，数据包中的位等于filterPktData中的对应位，则数据包将使该数据匹配失败。
Any packets that have not failed any of the three matches above have passed this data match. In particular, a zero length filter will match any packet.
上述三个匹配中未失败的任何数据包都已通过此数据匹配。特别是，零长度过滤器将匹配任何数据包。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 4 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 4 }
filterPktDataMask OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The mask that is applied to the match process. After adjusting this mask for the offset, only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the
filterPktDataMask对象类型语法八位字符串MAX-ACCESS read create STATUS current DESCRIPTION“应用于匹配过程的掩码。调整此掩码的偏移量后，只有接收数据包中与此掩码中设置的位相对应的位才与应用程序的进一步处理相关
match algorithm. The offset is applied to filterPktDataMask in the same way it is applied to the filter. For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the length of the filterPktData object.
匹配算法。偏移量应用于filterPktDataMask的方式与应用于过滤器的方式相同。出于匹配算法的目的，如果关联的filterPktData对象长于此掩码，则此掩码在概念上用“1”位扩展，直到达到filterPktData对象的长度。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 5 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 5 }
filterPktDataNotMask OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The inversion mask that is applied to the match process. After adjusting this mask for the offset, those relevant bits in the received packet that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktData object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet that correspond to bits set in this mask must be different to its corresponding bit in the filterPktData object.
filterPktDataNotMask对象类型语法八位字符串MAX-ACCESS读取创建状态当前描述“应用于匹配过程的反转掩码。调整此掩码的偏移量后，接收数据包中与此掩码中清除的位相对应的那些相关位必须全部等于要接受数据包的filterPktData对象中相应的位。此外，接收数据包中与此掩码中设置的位对应的那些相关位中的至少一个必须不同于其在filterPktData对象中的对应位。
For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the length of the filterPktData object.
出于匹配算法的目的，如果关联的filterPktData对象长于此掩码，则此掩码在概念上用“0”位扩展，直到达到filterPktData对象的长度。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 6 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 6 }
filterPktStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The status that is to be matched with the input packet. The only bits relevant to this match algorithm are those that have the corresponding filterPktStatusMask bit equal to one. The following two rules are then applied to every packet:
filterPktStatus对象类型语法Integer32 MAX-ACCESS read create STATUS current DESCRIPTION“要与输入数据包匹配的状态。与此匹配算法相关的唯一位是对应的filterPktStatusMask位等于1的位。然后对每个数据包应用以下两条规则：
(1) For each relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to zero, if the bit from the packet status is not equal to the
(1) 如果来自数据包状态的位不等于
corresponding bit from the filterPktStatus, then the packet will fail this status match.
来自filterPktStatus的相应位，则数据包将使此状态匹配失败。
(2) If for every relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to one, the bit from the packet status is equal to the corresponding bit from the filterPktStatus, then the packet will fail this status match.
(2) 如果对应filterPktStatusNotMask位设置为1的数据包状态中的每个相关位，数据包状态中的位等于filterPktStatus中的对应位，则数据包将无法通过此状态匹配。
Any packets that have not failed either of the two matches above have passed this status match. In particular, a zero length status filter will match any packet's status.
以上两个匹配都未失败的任何数据包都已通过此状态匹配。特别是，零长度状态过滤器将匹配任何数据包的状态。
The value of the packet status is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum. The errors and the bits that represent them are dependent on the media type of the interface that this channel is receiving packets from.
数据包状态的值为总和。这个总和最初取零值。然后，对于在该分组中发现的每个错误E，将提升到表示E的值的2添加到总和中。错误和表示错误的位取决于此通道接收数据包的接口的媒体类型。
The errors defined for a packet captured off of an Ethernet interface are as follows:
为从以太网接口捕获的数据包定义的错误如下：
bit # Error 0 Packet is longer than 1518 octets 1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error
位#错误0数据包长于1518个八位字节1数据包短于64个八位字节2数据包遇到CRC或对齐错误
For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2).
例如，以太网片段的值为6（2^1+2^2）。
As this MIB is expanded to new media types, this object will have other media-specific errors defined.
当此MIB扩展到新的媒体类型时，此对象将定义其他特定于媒体的错误。
For the purposes of this status matching algorithm, if the packet status is longer than this filterPktStatus object, this object is conceptually extended with '0' bits until it reaches the size of the packet status.
出于此状态匹配算法的目的，如果数据包状态长于此filterPktStatus对象，则此对象在概念上用“0”位扩展，直到达到数据包状态的大小。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 7 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 7 }
filterPktStatusMask OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current
filterPktStatusMask对象类型语法整数32 MAX-ACCESS读取创建当前状态
DESCRIPTION "The mask that is applied to the status match process. Only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the status match algorithm. For the purposes of the matching algorithm, if the associated filterPktStatus object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the size of the filterPktStatus. In addition, if a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the size of the packet status.
描述“应用于状态匹配过程的掩码。只有接收数据包中与此掩码中设置的位相对应的位与状态匹配算法的进一步处理相关。出于匹配算法的目的，如果关联的filterPktStatus对象长于此掩码，则此掩码在概念上用“1”位扩展，直到达到filterPktStatus的大小。此外，如果数据包状态长于此掩码，则此掩码在概念上用“0”位扩展，直到达到数据包状态的大小。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 8 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 8 }
filterPktStatusNotMask OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The inversion mask that is applied to the status match process. Those relevant bits in the received packet status that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktStatus object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet status that correspond to bits set in this mask must be different to its corresponding bit in the filterPktStatus object for the packet to be accepted.
filterPktStatusNotMask对象类型语法整数32 MAX-ACCESS读取创建状态当前说明“应用于状态匹配过程的反转掩码。接收数据包状态中与此掩码中清除的位相对应的那些相关位必须全部等于要接受数据包的filterPktStatus对象中相应的位。此外，接收包状态中与此掩码中设置的位相对应的那些相关位中的至少一个必须与其在filterPktStatus对象中的对应位不同，以便接受包。
For the purposes of the matching algorithm, if the associated filterPktStatus object or a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the longer of the lengths of the filterPktStatus object and the packet status.
出于匹配算法的目的，如果关联的filterPktStatus对象或数据包状态长于此掩码，则此掩码在概念上用“0”位扩展，直到达到filterPktStatus对象和数据包状态的较长长度。
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 9 }
This object may not be modified if the associated
filterStatus object is equal to valid(1)."
::= { filterEntry 9 }
filterOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it."
filterOwner对象类型语法OwnerString MAX-ACCESS read create STATUS current DESCRIPTION“配置此条目并因此使用分配给它的资源的实体。”
::= { filterEntry 10 }
::= { filterEntry 10 }
filterStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this filter entry."
::= { filterEntry 11 }
filterStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this filter entry."
::= { filterEntry 11 }
channelTable OBJECT-TYPE
SYNTAX SEQUENCE OF ChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packet channel entries."
::= { filter 2 }
channelTable OBJECT-TYPE
SYNTAX SEQUENCE OF ChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packet channel entries."
::= { filter 2 }
channelEntry OBJECT-TYPE
SYNTAX ChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters for a packet channel applied on a
particular interface. As an example, an instance of the
channelMatches object might be named channelMatches.3"
INDEX { channelIndex }
::= { channelTable 1 }
channelEntry OBJECT-TYPE
SYNTAX ChannelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters for a packet channel applied on a
particular interface. As an example, an instance of the
channelMatches object might be named channelMatches.3"
INDEX { channelIndex }
::= { channelTable 1 }
ChannelEntry ::= SEQUENCE {
channelIndex Integer32,
channelIfIndex Integer32,
channelAcceptType INTEGER,
channelDataControl INTEGER,
channelTurnOnEventIndex Integer32,
channelTurnOffEventIndex Integer32,
channelEventIndex Integer32,
channelEventStatus INTEGER,
channelMatches Counter32,
channelDescription DisplayString,
channelOwner OwnerString,
channelStatus EntryStatus
}
ChannelEntry ::= SEQUENCE {
channelIndex Integer32,
channelIfIndex Integer32,
channelAcceptType INTEGER,
channelDataControl INTEGER,
channelTurnOnEventIndex Integer32,
channelTurnOffEventIndex Integer32,
channelEventIndex Integer32,
channelEventStatus INTEGER,
channelMatches Counter32,
channelDescription DisplayString,
channelOwner OwnerString,
channelStatus EntryStatus
}
channelIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current
channelIndex对象类型语法整数32（1..65535）最大访问只读状态当前
DESCRIPTION "An index that uniquely identifies an entry in the channel table. Each such entry defines one channel, a logical data and event stream.
DESCRIPTION“唯一标识通道表中一个条目的索引。每个这样的条目定义一个通道、一个逻辑数据和事件流。
It is suggested that before creating a channel, an
application should scan all instances of the
filterChannelIndex object to make sure that there are no
pre-existing filters that would be inadvertently be linked
to the channel."
::= { channelEntry 1 }
It is suggested that before creating a channel, an
application should scan all instances of the
filterChannelIndex object to make sure that there are no
pre-existing filters that would be inadvertently be linked
to the channel."
::= { channelEntry 1 }
channelIfIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object uniquely identifies the interface on this remote network monitoring device to which the associated filters are applied to allow data into this channel. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in RFC 2233 [17].
ChanneliIndex对象类型语法整数32（1..65535）MAX-ACCESS读取创建状态当前说明“此对象的值唯一标识此远程网络监控设备上的接口，相关筛选器应用于该接口，以允许数据进入此通道。该对象的特定值标识的接口与RFC 2233[17]中定义的ifIndex对象的相同值标识的接口相同。
The filters in this group are applied to all packets on the local network segment attached to the identified interface.
此组中的筛选器应用于连接到标识接口的本地网段上的所有数据包。
An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry.
代理可能知道，也可能不知道接口的媒体是否发生了根本性的更改，是否需要对此条目进行失效处理。例如，一个可热插拔的以太网卡可以被拔出并替换为令牌环卡。在这种情况下，如果代理知道该更改，建议其使该条目无效。
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 2 }
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 2 }
channelAcceptType OBJECT-TYPE
SYNTAX INTEGER {
acceptMatched(1),
acceptFailed(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
channelAcceptType OBJECT-TYPE
SYNTAX INTEGER {
acceptMatched(1),
acceptFailed(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls the action of the filters associated with this channel. If this object is equal to acceptMatched(1), packets will be accepted to this channel if they are accepted by both the packet data and packet status matches of an associated filter. If this object is equal to acceptFailed(2), packets will be accepted to this channel only if they fail either the packet data match or the packet status match of each of the associated filters.
此对象控制与此通道关联的筛选器的操作。如果此对象等于acceptMatched（1），则如果关联筛选器的数据包数据和数据包状态匹配都接受数据包，则数据包将被接受到此通道。如果此对象等于acceptFailed（2），只有当每个相关过滤器的数据包数据匹配或数据包状态匹配失败时，数据包才会被接收到此通道。
In particular, a channel with no associated filters will match no packets if set to acceptMatched(1) case and will match all packets in the acceptFailed(2) case.
特别是，如果设置为acceptMatched（1）情况，没有相关筛选器的通道将不匹配任何数据包，并且将匹配acceptFailed（2）情况下的所有数据包。
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 3 }
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 3 }
channelDataControl OBJECT-TYPE
SYNTAX INTEGER {
on(1),
off(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls the flow of data through this channel.
If this object is on(1), data, status and events flow
through this channel. If this object is off(2), data,
status and events will not flow through this channel."
DEFVAL { off }
::= { channelEntry 4 }
channelDataControl OBJECT-TYPE
SYNTAX INTEGER {
on(1),
off(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls the flow of data through this channel.
If this object is on(1), data, status and events flow
through this channel. If this object is off(2), data,
status and events will not flow through this channel."
DEFVAL { off }
::= { channelEntry 4 }
channelTurnOnEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the event that is configured to turn the associated channelDataControl from off to on when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOnEventIndex must be set to zero, a non-existent event index.
channelTurnOnEventIndex对象类型语法整数32（0..65535）最大访问读取创建状态当前说明“此对象的值标识了配置为在生成事件时将关联的channelDataControl从关闭转到打开的事件。此对象的特定值标识的事件与eventIndex对象的相同值标识的事件相同。如果eventTable中没有相应的条目，则不存在关联。事实上，如果没有针对该通道的事件，那么channelTurnOnEventIndex必须设置为零，这是一个不存在的事件索引。
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 5 }
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 5 }
channelTurnOffEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the event that is configured to turn the associated channelDataControl from on to off when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOffEventIndex must be set to zero, a non-existent event index.
channelTurnOffEventIndex对象类型语法整数32（0..65535）MAX-ACCESS读取创建状态当前说明“此对象的值标识事件，该事件被配置为在生成事件时将关联的channelDataControl从on转到off。此对象的特定值标识的事件与eventIndex对象的相同值标识的事件相同。如果eventTable中没有相应的条目，则不存在关联。事实上，如果此通道没有事件，那么channelTurnOffEventIndex必须设置为零，这是一个不存在的事件索引。
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 6 }
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 6 }
channelEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the event that is configured to be generated when the associated channelDataControl is on and a packet is matched. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelEventIndex must be set to zero, a non-existent event index.
channelEventIndex对象类型语法整数32（0..65535）MAX-ACCESS读取创建状态当前说明“此对象的值标识配置为在关联的channelDataControl打开且数据包匹配时生成的事件。此对象的特定值标识的事件与eventIndex对象的相同值标识的事件相同。如果eventTable中没有相应的条目，则不存在关联。事实上，如果没有事件用于此通道，那么channelEventIndex必须设置为零，这是一个不存在的事件索引。
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 7 }
This object may not be modified if the associated
channelStatus object is equal to valid(1)."
::= { channelEntry 7 }
channelEventStatus OBJECT-TYPE SYNTAX INTEGER { eventReady(1), eventFired(2),
channelEventStatus对象类型语法整数{eventReady（1），eventFired（2），
eventAlwaysReady(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The event status of this channel.
eventAlwaysReady（3）}MAX-ACCESS读取创建状态当前描述“此通道的事件状态。
If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object.
如果将此通道配置为在数据包匹配时生成事件，则通常需要控制这些事件流的方法。当此对象等于eventReady（1）时，可能会生成单个事件，之后探测器会将此对象设置为eventFired（2）。处于eventFired（2）状态时，在将对象修改为eventReady（1）（或eventAlwaysReady（3））之前，不会生成任何事件。因此，管理站可以通过重新启用此对象轻松响应事件通知。
If the management station wishes to disable this
flow control and allow events to be generated
at will, this object may be set to
eventAlwaysReady(3). Disabling the flow control
is discouraged as it can result in high network
traffic or other performance problems."
DEFVAL { eventReady }
::= { channelEntry 8 }
If the management station wishes to disable this
flow control and allow events to be generated
at will, this object may be set to
eventAlwaysReady(3). Disabling the flow control
is discouraged as it can result in high network
traffic or other performance problems."
DEFVAL { eventReady }
::= { channelEntry 8 }
channelMatches OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this channel has matched a packet.
Note that this object is updated even when
channelDataControl is set to off."
::= { channelEntry 9 }
channelMatches OBJECT-TYPE
SYNTAX Counter32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this channel has matched a packet.
Note that this object is updated even when
channelDataControl is set to off."
::= { channelEntry 9 }
channelDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A comment describing this channel."
::= { channelEntry 10 }
channelDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A comment describing this channel."
::= { channelEntry 10 }
channelOwner OBJECT-TYPE
channelOwner对象类型
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { channelEntry 11 }
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { channelEntry 11 }
channelStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this channel entry."
::= { channelEntry 12 }
channelStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this channel entry."
::= { channelEntry 12 }
-- The Packet Capture Group
--数据包捕获组
-- Implementation of the Packet Capture group is optional. The Packet
-- Capture Group requires implementation of the Filter Group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Packet Capture group allows packets to be captured
-- upon a filter match. The bufferControlTable controls
-- the captured packets output from a channel that is
-- associated with it. The captured packets are placed
-- in entries in the captureBufferTable. These entries are
-- associated with the bufferControlEntry on whose behalf they
-- were stored.
-- Implementation of the Packet Capture group is optional. The Packet
-- Capture Group requires implementation of the Filter Group.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Packet Capture group allows packets to be captured
-- upon a filter match. The bufferControlTable controls
-- the captured packets output from a channel that is
-- associated with it. The captured packets are placed
-- in entries in the captureBufferTable. These entries are
-- associated with the bufferControlEntry on whose behalf they
-- were stored.
bufferControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF BufferControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of buffers control entries."
::= { capture 1 }
bufferControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF BufferControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of buffers control entries."
::= { capture 1 }
bufferControlEntry OBJECT-TYPE SYNTAX BufferControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of parameters that control the collection of a stream of packets that have matched filters. As an example, an instance of the bufferControlCaptureSliceSize object might be named bufferControlCaptureSliceSize.3"
bufferControlEntry对象类型语法bufferControlEntry MAX-ACCESS不可访问状态当前描述“控制具有匹配筛选器的数据包流集合的一组参数。例如，BufferControlCaptureSicleSize对象的实例可能命名为BufferControlCaptureSicleSize.3”
INDEX { bufferControlIndex }
::= { bufferControlTable 1 }
INDEX { bufferControlIndex }
::= { bufferControlTable 1 }
BufferControlEntry ::= SEQUENCE {
bufferControlIndex Integer32,
bufferControlChannelIndex Integer32,
bufferControlFullStatus INTEGER,
bufferControlFullAction INTEGER,
bufferControlCaptureSliceSize Integer32,
bufferControlDownloadSliceSize Integer32,
bufferControlDownloadOffset Integer32,
bufferControlMaxOctetsRequested Integer32,
bufferControlMaxOctetsGranted Integer32,
bufferControlCapturedPackets Integer32,
bufferControlTurnOnTime TimeTicks,
bufferControlOwner OwnerString,
bufferControlStatus EntryStatus
}
BufferControlEntry ::= SEQUENCE {
bufferControlIndex Integer32,
bufferControlChannelIndex Integer32,
bufferControlFullStatus INTEGER,
bufferControlFullAction INTEGER,
bufferControlCaptureSliceSize Integer32,
bufferControlDownloadSliceSize Integer32,
bufferControlDownloadOffset Integer32,
bufferControlMaxOctetsRequested Integer32,
bufferControlMaxOctetsGranted Integer32,
bufferControlCapturedPackets Integer32,
bufferControlTurnOnTime TimeTicks,
bufferControlOwner OwnerString,
bufferControlStatus EntryStatus
}
bufferControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the bufferControl table. The value of this
index shall never be zero. Each such
entry defines one set of packets that is
captured and controlled by one or more filters."
::= { bufferControlEntry 1 }
bufferControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the bufferControl table. The value of this
index shall never be zero. Each such
entry defines one set of packets that is
captured and controlled by one or more filters."
::= { bufferControlEntry 1 }
bufferControlChannelIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "An index that identifies the channel that is the source of packets for this bufferControl table. The channel identified by a particular value of this index is the same as identified by the same value of the channelIndex object.
bufferControlChannelIndex对象类型语法整数32（1..65535）MAX-ACCESS read create STATUS current DESCRIPTION“标识作为此缓冲控制表数据包源的通道的索引。由此索引的特定值标识的通道与由channelIndex对象的相同值标识的通道相同。
This object may not be modified if the associated
bufferControlStatus object is equal to valid(1)."
::= { bufferControlEntry 2 }
This object may not be modified if the associated
bufferControlStatus object is equal to valid(1)."
::= { bufferControlEntry 2 }
bufferControlFullStatus OBJECT-TYPE SYNTAX INTEGER {
bufferControlFullStatus对象类型语法整数{
spaceAvailable(1), full(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object shows whether the buffer has room to accept new packets or if it is full.
spaceAvailable（1），full（2）}MAX-ACCESS只读状态current DESCRIPTION“此对象显示缓冲区是否有空间接受新数据包，或者缓冲区是否已满。
If the status is spaceAvailable(1), the buffer is accepting new packets normally. If the status is full(2) and the associated bufferControlFullAction object is wrapWhenFull, the buffer is accepting new packets by deleting enough of the oldest packets to make room for new ones as they arrive. Otherwise, if the status is full(2) and the bufferControlFullAction object is lockWhenFull, then the buffer has stopped collecting packets.
如果状态为spaceAvailable（1），则缓冲区正常接受新数据包。如果状态为“已满”（2），且关联的bufferControlFullAction对象为wrapWhenFull，则缓冲区将通过删除足够多的最旧数据包来接受新数据包，以便在新数据包到达时为其腾出空间。否则，如果状态为full（2）且bufferControlFullAction对象为lockWhenFull，则缓冲区已停止收集数据包。
When this object is set to full(2) the probe must
not later set it to spaceAvailable(1) except in the
case of a significant gain in resources such as
an increase of bufferControlOctetsGranted. In
particular, the wrap-mode action of deleting old
packets to make room for newly arrived packets
must not affect the value of this object."
::= { bufferControlEntry 3 }
When this object is set to full(2) the probe must
not later set it to spaceAvailable(1) except in the
case of a significant gain in resources such as
an increase of bufferControlOctetsGranted. In
particular, the wrap-mode action of deleting old
packets to make room for newly arrived packets
must not affect the value of this object."
::= { bufferControlEntry 3 }
bufferControlFullAction OBJECT-TYPE
SYNTAX INTEGER {
lockWhenFull(1),
wrapWhenFull(2) -- FIFO
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Controls the action of the buffer when it
reaches the full status. When in the lockWhenFull(1)
state and a packet is added to the buffer that
fills the buffer, the bufferControlFullStatus will
be set to full(2) and this buffer will stop capturing
packets."
::= { bufferControlEntry 4 }
bufferControlFullAction OBJECT-TYPE
SYNTAX INTEGER {
lockWhenFull(1),
wrapWhenFull(2) -- FIFO
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Controls the action of the buffer when it
reaches the full status. When in the lockWhenFull(1)
state and a packet is added to the buffer that
fills the buffer, the bufferControlFullStatus will
be set to full(2) and this buffer will stop capturing
packets."
::= { bufferControlEntry 4 }
bufferControlCaptureSliceSize OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-create
bufferControlCaptureSliceSize对象类型语法整数32个单位“八位字节”最大访问读取创建
STATUS current DESCRIPTION "The maximum number of octets of each packet that will be saved in this capture buffer. For example, if a 1500 octet packet is received by the probe and this object is set to 500, then only 500 octets of the packet will be stored in the associated capture buffer. If this variable is set to 0, the capture buffer will save as many octets as is possible.
状态当前描述“将保存在此捕获缓冲区中的每个数据包的最大八位字节数。例如，如果探测器接收到1500个八位字节的数据包，并且该对象被设置为500，则只有500个八位字节的数据包将存储在相关的捕获缓冲区中。如果此变量设置为0，则捕获缓冲区将保存尽可能多的八位字节。
This object may not be modified if the associated
bufferControlStatus object is equal to valid(1)."
DEFVAL { 100 }
::= { bufferControlEntry 5 }
This object may not be modified if the associated
bufferControlStatus object is equal to valid(1)."
DEFVAL { 100 }
::= { bufferControlEntry 5 }
bufferControlDownloadSliceSize OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of octets of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. For example, if 500 octets of a packet have been stored in the associated capture buffer, the associated bufferControlDownloadOffset is 0, and this object is set to 100, then the captureBufferPacket object that contains the packet will contain only the first 100 octets of the packet.
bufferControlDownloadSliceSize对象类型语法整数32个单位“八位字节”MAX-ACCESS读取创建状态当前描述“此捕获缓冲区中每个数据包在SNMP检索该数据包时返回的最大八位字节数。例如，如果一个数据包的500个八位字节已存储在关联的捕获缓冲区中，关联的bufferControlDownloadOffset为0，并且该对象设置为100，则包含该数据包的captureBufferPacket对象将仅包含该数据包的前100个八位字节。
A prudent manager will take into account possible
interoperability or fragmentation problems that may
occur if the download slice size is set too large.
In particular, conformant SNMP implementations are not
required to accept messages whose length exceeds 484
octets, although they are encouraged to support larger
datagrams whenever feasible."
DEFVAL { 100 }
::= { bufferControlEntry 6 }
A prudent manager will take into account possible
interoperability or fragmentation problems that may
occur if the download slice size is set too large.
In particular, conformant SNMP implementations are not
required to accept messages whose length exceeds 484
octets, although they are encouraged to support larger
datagrams whenever feasible."
DEFVAL { 100 }
::= { bufferControlEntry 6 }
bufferControlDownloadOffset OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-create STATUS current DESCRIPTION
bufferControlDownloadOffset对象类型语法整数32个单位“八位字节”MAX-ACCESS读取创建状态当前描述
"The offset of the first octet of each packet
in this capture buffer that will be returned in
an SNMP retrieval of that packet. For example,
if 500 octets of a packet have been stored in the
associated capture buffer and this object is set to
100, then the captureBufferPacket object that
contains the packet will contain bytes starting
100 octets into the packet."
DEFVAL { 0 }
::= { bufferControlEntry 7 }
"The offset of the first octet of each packet
in this capture buffer that will be returned in
an SNMP retrieval of that packet. For example,
if 500 octets of a packet have been stored in the
associated capture buffer and this object is set to
100, then the captureBufferPacket object that
contains the packet will contain bytes starting
100 octets into the packet."
DEFVAL { 0 }
::= { bufferControlEntry 7 }
bufferControlMaxOctetsRequested OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-create STATUS current DESCRIPTION "The requested maximum number of octets to be saved in this captureBuffer, including any implementation-specific overhead. If this variable is set to -1, the capture buffer will save as many octets as is possible.
bufferControlMaxOctetsRequested OBJECT-TYPE语法整数32 UNITS“Octets”MAX-ACCESS read create STATUS current DESCRIPTION“请求保存在此captureBuffer中的最大八位字节数，包括任何特定于实现的开销。如果此变量设置为-1，捕获缓冲区将保存尽可能多的八位字节。
When this object is created or modified, the probe
should set bufferControlMaxOctetsGranted as closely
to this object as is possible for the particular probe
implementation and available resources. However, if
the object has the special value of -1, the probe
must set bufferControlMaxOctetsGranted to -1."
DEFVAL { -1 }
::= { bufferControlEntry 8 }
When this object is created or modified, the probe
should set bufferControlMaxOctetsGranted as closely
to this object as is possible for the particular probe
implementation and available resources. However, if
the object has the special value of -1, the probe
must set bufferControlMaxOctetsGranted to -1."
DEFVAL { -1 }
::= { bufferControlEntry 8 }
bufferControlMaxOctetsGranted OBJECT-TYPE SYNTAX Integer32 UNITS "Octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of octets that can be saved in this captureBuffer, including overhead. If this variable is -1, the capture buffer will save as many octets as possible.
bufferControlMaxOctetsGranted对象类型语法整数32个单位“八位字节”MAX-ACCESS只读状态当前描述“此captureBuffer中可保存的最大八位字节数，包括开销。如果此变量为-1，则捕获缓冲区将保存尽可能多的八位字节。
When the bufferControlMaxOctetsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. However, if the request object has the special value
创建或修改bufferControlMaxOctetsRequested对象时，探测器应将该对象设置为尽可能接近特定探测器实现和可用资源所请求的值。但是，如果请求对象具有特殊值
of -1, the probe must set this object to -1.
对于-1，探测器必须将此对象设置为-1。
The probe must not lower this value except as a result of a modification to the associated bufferControlMaxOctetsRequested object.
探测不得降低此值，除非是由于修改了关联的bufferControlMaxOctetsRequested对象。
When this maximum number of octets is reached and a new packet is to be added to this capture buffer and the corresponding bufferControlFullAction is set to wrapWhenFull(2), enough of the oldest packets associated with this capture buffer shall be deleted by the agent so that the new packet can be added. If the corresponding bufferControlFullAction is set to lockWhenFull(1), the new packet shall be discarded. In either case, the probe must set bufferControlFullStatus to full(2).
当达到此最大八位字节数且新数据包将添加到此捕获缓冲区且相应的bufferControlFullAction设置为wrapWhenFull（2）时，代理应删除与此捕获缓冲区相关的足够多的最旧数据包，以便添加新数据包。如果相应的bufferControlFullAction设置为lockWhenFull（1），则应丢弃新数据包。无论哪种情况，探测器都必须将bufferControlFullStatus设置为full（2）。
When the value of this object changes to a value less than the current value, entries are deleted from the captureBufferTable associated with this bufferControlEntry. Enough of the oldest of these captureBufferEntries shall be deleted by the agent so that the number of octets used remains less than or equal to the new value of this object.
当此对象的值更改为小于当前值的值时，将从与此bufferControlEntry关联的captureBufferTable中删除条目。代理应删除这些captureBufferEntries中足够多的最旧条目，以便使用的八位字节数保持小于或等于此对象的新值。
When the value of this object changes to a value greater
than the current value, the number of associated
captureBufferEntries may be allowed to grow."
::= { bufferControlEntry 9 }
When the value of this object changes to a value greater
than the current value, the number of associated
captureBufferEntries may be allowed to grow."
::= { bufferControlEntry 9 }
bufferControlCapturedPackets OBJECT-TYPE
SYNTAX Integer32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets currently in this captureBuffer."
::= { bufferControlEntry 10 }
bufferControlCapturedPackets OBJECT-TYPE
SYNTAX Integer32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets currently in this captureBuffer."
::= { bufferControlEntry 10 }
bufferControlTurnOnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this capture buffer was first turned on."
bufferControlTurnOnTime对象类型语法TimeTicks MAX-ACCESS只读状态当前描述“首次打开此捕获缓冲区时的系统正常运行时间值。”
::= { bufferControlEntry 11 }
::= { bufferControlEntry 11 }
bufferControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { bufferControlEntry 12 }
bufferControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { bufferControlEntry 12 }
bufferControlStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this buffer Control Entry."
::= { bufferControlEntry 13 }
bufferControlStatus OBJECT-TYPE
SYNTAX EntryStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this buffer Control Entry."
::= { bufferControlEntry 13 }
captureBufferTable OBJECT-TYPE
SYNTAX SEQUENCE OF CaptureBufferEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packets captured off of a channel."
::= { capture 2 }
captureBufferTable OBJECT-TYPE
SYNTAX SEQUENCE OF CaptureBufferEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of packets captured off of a channel."
::= { capture 2 }
captureBufferEntry OBJECT-TYPE
SYNTAX CaptureBufferEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A packet captured off of an attached network. As an
example, an instance of the captureBufferPacketData
object might be named captureBufferPacketData.3.1783"
INDEX { captureBufferControlIndex, captureBufferIndex }
::= { captureBufferTable 1 }
captureBufferEntry OBJECT-TYPE
SYNTAX CaptureBufferEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A packet captured off of an attached network. As an
example, an instance of the captureBufferPacketData
object might be named captureBufferPacketData.3.1783"
INDEX { captureBufferControlIndex, captureBufferIndex }
::= { captureBufferTable 1 }
CaptureBufferEntry ::= SEQUENCE {
captureBufferControlIndex Integer32,
captureBufferIndex Integer32,
captureBufferPacketID Integer32,
captureBufferPacketData OCTET STRING,
captureBufferPacketLength Integer32,
captureBufferPacketTime Integer32,
captureBufferPacketStatus Integer32
}
CaptureBufferEntry ::= SEQUENCE {
captureBufferControlIndex Integer32,
captureBufferIndex Integer32,
captureBufferPacketID Integer32,
captureBufferPacketData OCTET STRING,
captureBufferPacketLength Integer32,
captureBufferPacketTime Integer32,
captureBufferPacketStatus Integer32
}
captureBufferControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index of the bufferControlEntry with which
this packet is associated."
::= { captureBufferEntry 1 }
captureBufferControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index of the bufferControlEntry with which
this packet is associated."
::= { captureBufferEntry 1 }
captureBufferIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that uniquely identifies an entry in the captureBuffer table associated with a particular bufferControlEntry. This index will start at 1 and increase by one for each new packet added with the same captureBufferControlIndex.
captureBufferIndex对象类型语法整数32（1..2147483647）MAX-ACCESS只读状态当前描述“唯一标识captureBuffer表中与特定bufferControlEntry关联的项的索引。该索引将从1开始，并为添加了相同captureBufferControlIndex的每个新数据包增加1。
Should this value reach 2147483647, the next packet
added with the same captureBufferControlIndex shall
cause this value to wrap around to 1."
::= { captureBufferEntry 2 }
Should this value reach 2147483647, the next packet
added with the same captureBufferControlIndex shall
cause this value to wrap around to 1."
::= { captureBufferEntry 2 }
captureBufferPacketID OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that describes the order of packets
that are received on a particular interface.
The packetID of a packet captured on an
interface is defined to be greater than the
packetID's of all packets captured previously on
the same interface. As the captureBufferPacketID
object has a maximum positive value of 2^31 - 1,
any captureBufferPacketID object shall have the
value of the associated packet's packetID mod 2^31."
::= { captureBufferEntry 3 }
captureBufferPacketID OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that describes the order of packets
that are received on a particular interface.
The packetID of a packet captured on an
interface is defined to be greater than the
packetID's of all packets captured previously on
the same interface. As the captureBufferPacketID
object has a maximum positive value of 2^31 - 1,
any captureBufferPacketID object shall have the
value of the associated packet's packetID mod 2^31."
::= { captureBufferEntry 3 }
captureBufferPacketData OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The data inside the packet, starting at the beginning of the packet plus any offset specified in the
captureBufferPacketData对象类型语法八位字符串MAX-ACCESS只读状态当前描述“数据包内的数据，从数据包的开头开始，加上
associated bufferControlDownloadOffset, including any
link level headers. The length of the data in this object
is the minimum of the length of the captured packet minus
the offset, the length of the associated
bufferControlCaptureSliceSize minus the offset, and the
associated bufferControlDownloadSliceSize. If this minimum
is less than zero, this object shall have a length of zero."
::= { captureBufferEntry 4 }
associated bufferControlDownloadOffset, including any
link level headers. The length of the data in this object
is the minimum of the length of the captured packet minus
the offset, the length of the associated
bufferControlCaptureSliceSize minus the offset, and the
associated bufferControlDownloadSliceSize. If this minimum
is less than zero, this object shall have a length of zero."
::= { captureBufferEntry 4 }
captureBufferPacketLength OBJECT-TYPE
SYNTAX Integer32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual length (off the wire) of the packet stored
in this entry, including FCS octets."
::= { captureBufferEntry 5 }
captureBufferPacketLength OBJECT-TYPE
SYNTAX Integer32
UNITS "Octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual length (off the wire) of the packet stored
in this entry, including FCS octets."
::= { captureBufferEntry 5 }
captureBufferPacketTime OBJECT-TYPE
SYNTAX Integer32
UNITS "Milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of milliseconds that had passed since
this capture buffer was first turned on when this
packet was captured."
::= { captureBufferEntry 6 }
captureBufferPacketTime OBJECT-TYPE
SYNTAX Integer32
UNITS "Milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of milliseconds that had passed since
this capture buffer was first turned on when this
packet was captured."
::= { captureBufferEntry 6 }
captureBufferPacketStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A value which indicates the error status of this packet.
captureBufferPacketStatus对象类型语法Integer32 MAX-ACCESS只读状态当前描述“指示此数据包错误状态的值。
The value of this object is defined in the same way as filterPktStatus. The value is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum.
此对象的值的定义方式与filterPktStatus相同。该值是一个总和。这个总和最初取零值。然后，对于在该分组中发现的每个错误E，将提升到表示E的值的2添加到总和中。
The errors defined for a packet captured off of an Ethernet interface are as follows:
为从以太网接口捕获的数据包定义的错误如下：
bit # Error 0 Packet is longer than 1518 octets
位#错误0数据包长于1518个八位字节
1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error 3 First packet in this capture buffer after it was detected that some packets were not processed correctly. 4 Packet's order in buffer is only approximate (May only be set for packets sent from the probe)
1个数据包比64个八位字节短2个数据包遇到CRC或对齐错误3检测到某些数据包未正确处理后，此捕获缓冲区中的第一个数据包。4数据包在缓冲区中的顺序仅为近似值（只能为从探测器发送的数据包设置）
For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2).
例如，以太网片段的值为6（2^1+2^2）。
As this MIB is expanded to new media types, this object
will have other media-specific errors defined."
::= { captureBufferEntry 7 }
As this MIB is expanded to new media types, this object
will have other media-specific errors defined."
::= { captureBufferEntry 7 }
-- The Event Group
--活动组
-- Implementation of the Event group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Event group controls the generation and notification
-- of events from this device. Each entry in the eventTable
-- describes the parameters of the event that can be triggered.
-- Each event entry is fired by an associated condition located
-- elsewhere in the MIB. An event entry may also be associated
-- with a function elsewhere in the MIB that will be executed
-- when the event is generated. For example, a channel may
-- be turned on or off by the firing of an event.
--
-- Each eventEntry may optionally specify that a log entry
-- be created on its behalf whenever the event occurs.
-- Each entry may also specify that notification should
-- occur by way of SNMP trap messages. In this case, the
-- community for the trap message is given in the associated
-- eventCommunity object. The enterprise and specific trap
-- fields of the trap are determined by the condition that
-- triggered the event. Two traps are defined: risingAlarm and
-- fallingAlarm. If the eventTable is triggered by a condition
-- specified elsewhere, the enterprise and specific trap fields
-- must be specified for traps generated for that condition.
-- Implementation of the Event group is optional.
-- Consult the MODULE-COMPLIANCE macro for the authoritative
-- conformance information for this MIB.
--
-- The Event group controls the generation and notification
-- of events from this device. Each entry in the eventTable
-- describes the parameters of the event that can be triggered.
-- Each event entry is fired by an associated condition located
-- elsewhere in the MIB. An event entry may also be associated
-- with a function elsewhere in the MIB that will be executed
-- when the event is generated. For example, a channel may
-- be turned on or off by the firing of an event.
--
-- Each eventEntry may optionally specify that a log entry
-- be created on its behalf whenever the event occurs.
-- Each entry may also specify that notification should
-- occur by way of SNMP trap messages. In this case, the
-- community for the trap message is given in the associated
-- eventCommunity object. The enterprise and specific trap
-- fields of the trap are determined by the condition that
-- triggered the event. Two traps are defined: risingAlarm and
-- fallingAlarm. If the eventTable is triggered by a condition
-- specified elsewhere, the enterprise and specific trap fields
-- must be specified for traps generated for that condition.
eventTable OBJECT-TYPE SYNTAX SEQUENCE OF EventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
EventEntry MAX-ACCESS的eventTable对象类型语法序列不可访问状态当前描述
"A list of events to be generated."
::= { event 1 }
"A list of events to be generated."
::= { event 1 }
eventEntry OBJECT-TYPE
SYNTAX EventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that describe an event to be generated
when certain conditions are met. As an example, an instance
of the eventLastTimeSent object might be named
eventLastTimeSent.6"
INDEX { eventIndex }
::= { eventTable 1 }
eventEntry OBJECT-TYPE
SYNTAX EventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that describe an event to be generated
when certain conditions are met. As an example, an instance
of the eventLastTimeSent object might be named
eventLastTimeSent.6"
INDEX { eventIndex }
::= { eventTable 1 }
EventEntry ::= SEQUENCE {
eventIndex Integer32,
eventDescription DisplayString,
eventType INTEGER,
eventCommunity OCTET STRING,
eventLastTimeSent TimeTicks,
eventOwner OwnerString,
eventStatus EntryStatus
}
EventEntry ::= SEQUENCE {
eventIndex Integer32,
eventDescription DisplayString,
eventType INTEGER,
eventCommunity OCTET STRING,
eventLastTimeSent TimeTicks,
eventOwner OwnerString,
eventStatus EntryStatus
}
eventIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
event table. Each such entry defines one event that
is to be generated when the appropriate conditions
occur."
::= { eventEntry 1 }
eventIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
event table. Each such entry defines one event that
is to be generated when the appropriate conditions
occur."
::= { eventEntry 1 }
eventDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A comment describing this event entry."
::= { eventEntry 2 }
eventDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A comment describing this event entry."
::= { eventEntry 2 }
eventType OBJECT-TYPE SYNTAX INTEGER { none(1), log(2),
eventType对象类型语法整数{none（1），log（2），
snmptrap(3), -- send an SNMP trap
logandtrap(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of notification that the probe will make
about this event. In the case of log, an entry is
made in the log table for each event. In the case of
snmp-trap, an SNMP trap is sent to one or more
management stations."
::= { eventEntry 3 }
snmptrap(3), -- send an SNMP trap
logandtrap(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of notification that the probe will make
about this event. In the case of log, an entry is
made in the log table for each event. In the case of
snmp-trap, an SNMP trap is sent to one or more
management stations."
::= { eventEntry 3 }
eventCommunity OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If an SNMP trap is to be sent, it will be sent to
the SNMP community specified by this octet string."
::= { eventEntry 4 }
eventCommunity OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..127))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If an SNMP trap is to be sent, it will be sent to
the SNMP community specified by this octet string."
::= { eventEntry 4 }
eventLastTimeSent OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this event
entry last generated an event. If this entry has
not generated any events, this value will be
zero."
::= { eventEntry 5 }
eventLastTimeSent OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this event
entry last generated an event. If this entry has
not generated any events, this value will be
zero."
::= { eventEntry 5 }
eventOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it.
eventOwner对象类型语法OwnerString MAX-ACCESS read create STATUS current DESCRIPTION“配置此条目的实体，因此正在使用分配给它的资源。
If this object contains a string starting with 'monitor'
and has associated entries in the log table, all connected
management stations should retrieve those log entries,
as they may have significance to all management stations
connected to this device"
::= { eventEntry 6 }
If this object contains a string starting with 'monitor'
and has associated entries in the log table, all connected
management stations should retrieve those log entries,
as they may have significance to all management stations
connected to this device"
::= { eventEntry 6 }
eventStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this event entry.
eventStatus对象类型语法EntryStatus MAX-ACCESS读取创建状态当前描述“此事件条目的状态。
If this object is not equal to valid(1), all associated
log entries shall be deleted by the agent."
::= { eventEntry 7 }
If this object is not equal to valid(1), all associated
log entries shall be deleted by the agent."
::= { eventEntry 7 }
--
logTable OBJECT-TYPE
SYNTAX SEQUENCE OF LogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of events that have been logged."
::= { event 2 }
--
logTable OBJECT-TYPE
SYNTAX SEQUENCE OF LogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of events that have been logged."
::= { event 2 }
logEntry OBJECT-TYPE
SYNTAX LogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of data describing an event that has been
logged. For example, an instance of the logDescription
object might be named logDescription.6.47"
INDEX { logEventIndex, logIndex }
::= { logTable 1 }
logEntry OBJECT-TYPE
SYNTAX LogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of data describing an event that has been
logged. For example, an instance of the logDescription
object might be named logDescription.6.47"
INDEX { logEventIndex, logIndex }
::= { logTable 1 }
LogEntry ::= SEQUENCE {
logEventIndex Integer32,
logIndex Integer32,
logTime TimeTicks,
logDescription DisplayString
}
LogEntry ::= SEQUENCE {
logEventIndex Integer32,
logIndex Integer32,
logTime TimeTicks,
logDescription DisplayString
}
logEventIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The event entry that generated this log entry. The log identified by a particular value of this index is associated with the same eventEntry as identified by the same value of eventIndex."
logEventIndex对象类型语法Integer32（1..65535）MAX-ACCESS只读状态当前描述“生成此日志项的事件项。由此索引的特定值标识的日志与由相同eventIndex值标识的相同eventEntry相关联。”
::= { logEntry 1 }
::= { logEntry 1 }
logIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the log table amongst those generated by the
same eventEntries. These indexes are
assigned beginning with 1 and increase by one
with each new log entry. The association
between values of logIndex and logEntries
is fixed for the lifetime of each logEntry.
The agent may choose to delete the oldest
instances of logEntry as required because of
lack of memory. It is an implementation-specific
matter as to when this deletion may occur."
::= { logEntry 2 }
logIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry
in the log table amongst those generated by the
same eventEntries. These indexes are
assigned beginning with 1 and increase by one
with each new log entry. The association
between values of logIndex and logEntries
is fixed for the lifetime of each logEntry.
The agent may choose to delete the oldest
instances of logEntry as required because of
lack of memory. It is an implementation-specific
matter as to when this deletion may occur."
::= { logEntry 2 }
logTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this log entry was created."
::= { logEntry 3 }
logTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this log entry was created."
::= { logEntry 3 }
logDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An implementation dependent description of the
event that activated this log entry."
::= { logEntry 4 }
logDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An implementation dependent description of the
event that activated this log entry."
::= { logEntry 4 }
-- Remote Network Monitoring Traps
--远程网络监控陷阱
rmonEventsV2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "Definition point for RMON notifications."
::= { rmon 0 }
rmonEventsV2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "Definition point for RMON notifications."
::= { rmon 0 }
risingAlarm NOTIFICATION-TYPE OBJECTS { alarmIndex, alarmVariable, alarmSampleType, alarmValue, alarmRisingThreshold } STATUS current
risingAlarm通知类型对象{alarmIndex，alarmVariable，alarmSampleType，alarmValue，alarmRisingThreshold}当前状态
DESCRIPTION
"The SNMP trap that is generated when an alarm
entry crosses its rising threshold and generates
an event that is configured for sending SNMP
traps."
::= { rmonEventsV2 1 }
DESCRIPTION
"The SNMP trap that is generated when an alarm
entry crosses its rising threshold and generates
an event that is configured for sending SNMP
traps."
::= { rmonEventsV2 1 }
fallingAlarm NOTIFICATION-TYPE
OBJECTS { alarmIndex, alarmVariable, alarmSampleType,
alarmValue, alarmFallingThreshold }
STATUS current
DESCRIPTION
"The SNMP trap that is generated when an alarm
entry crosses its falling threshold and generates
an event that is configured for sending SNMP
traps."
::= { rmonEventsV2 2 }
fallingAlarm NOTIFICATION-TYPE
OBJECTS { alarmIndex, alarmVariable, alarmSampleType,
alarmValue, alarmFallingThreshold }
STATUS current
DESCRIPTION
"The SNMP trap that is generated when an alarm
entry crosses its falling threshold and generates
an event that is configured for sending SNMP
traps."
::= { rmonEventsV2 2 }
-- Conformance information
--一致性信息
rmonCompliances OBJECT IDENTIFIER ::= { rmonConformance 9 }
rmonGroups OBJECT IDENTIFIER ::= { rmonConformance 10 }
rmonCompliances OBJECT IDENTIFIER ::= { rmonConformance 9 }
rmonGroups OBJECT IDENTIFIER ::= { rmonConformance 10 }
-- Compliance Statements rmonCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The requirements for conformance to the RMON MIB. At least one of the groups in this module must be implemented to conform to the RMON MIB. Implementations of this MIB must also implement the system group of MIB-II [16] and the IF-MIB [17]." MODULE -- this module
--符合性声明rmonCompliance MODULE-Compliance STATUS current DESCRIPTION“符合RMON MIB的要求。必须实现此模块中至少一个组以符合RMON MIB。此MIB的实现还必须实现MIB-II[16]和IF-MIB[17]的系统组。”模块——此模块
GROUP rmonEtherStatsGroup DESCRIPTION "The RMON Ethernet Statistics Group is optional."
组rmonEtherStatsGroup DESCRIPTION“RMON以太网统计组是可选的。”
GROUP rmonHistoryControlGroup DESCRIPTION "The RMON History Control Group is optional."
组rmonHistoryControlGroup DESCRIPTION“RMON历史记录控制组是可选的。”
GROUP rmonEthernetHistoryGroup DESCRIPTION "The RMON Ethernet History Group is optional."
组rmonEthernetHistoryGroup DESCRIPTION“RMON以太网历史记录组是可选的。”
GROUP rmonAlarmGroup DESCRIPTION
组描述
"The RMON Alarm Group is optional."
“RMON报警组是可选的。”
GROUP rmonHostGroup DESCRIPTION "The RMON Host Group is mandatory when the rmonHostTopNGroup is implemented."
GROUP rmonHostGroup DESCRIPTION“在实现rmonHostTopNGroup时，RMON主机组是必需的。”
GROUP rmonHostTopNGroup DESCRIPTION "The RMON Host Top N Group is optional."
组rmonHostTopNGroup DESCRIPTION“RMON主机TOPN组是可选的。”
GROUP rmonMatrixGroup DESCRIPTION "The RMON Matrix Group is optional."
组rmonMatrixGroup DESCRIPTION“RMON矩阵组是可选的。”
GROUP rmonFilterGroup DESCRIPTION "The RMON Filter Group is mandatory when the rmonPacketCaptureGroup is implemented."
GROUP rmonFilterGroup DESCRIPTION“在实现rmonPacketCaptureGroup时，RMON筛选器组是必需的。”
GROUP rmonPacketCaptureGroup DESCRIPTION "The RMON Packet Capture Group is optional."
GROUP rmonPacketCaptureGroup DESCRIPTION“RMON数据包捕获组是可选的。”
GROUP rmonEventGroup
DESCRIPTION
"The RMON Event Group is mandatory when the
rmonAlarmGroup is implemented."
::= { rmonCompliances 1 }
GROUP rmonEventGroup
DESCRIPTION
"The RMON Event Group is mandatory when the
rmonAlarmGroup is implemented."
::= { rmonCompliances 1 }
rmonEtherStatsGroup OBJECT-GROUP
OBJECTS {
etherStatsIndex, etherStatsDataSource,
etherStatsDropEvents, etherStatsOctets, etherStatsPkts,
etherStatsBroadcastPkts, etherStatsMulticastPkts,
etherStatsCRCAlignErrors, etherStatsUndersizePkts,
etherStatsOversizePkts, etherStatsFragments,
etherStatsJabbers, etherStatsCollisions,
etherStatsPkts64Octets, etherStatsPkts65to127Octets,
etherStatsPkts128to255Octets,
etherStatsPkts256to511Octets,
etherStatsPkts512to1023Octets,
etherStatsPkts1024to1518Octets,
etherStatsOwner, etherStatsStatus
}
STATUS current
DESCRIPTION
"The RMON Ethernet Statistics Group."
rmonEtherStatsGroup OBJECT-GROUP
OBJECTS {
etherStatsIndex, etherStatsDataSource,
etherStatsDropEvents, etherStatsOctets, etherStatsPkts,
etherStatsBroadcastPkts, etherStatsMulticastPkts,
etherStatsCRCAlignErrors, etherStatsUndersizePkts,
etherStatsOversizePkts, etherStatsFragments,
etherStatsJabbers, etherStatsCollisions,
etherStatsPkts64Octets, etherStatsPkts65to127Octets,
etherStatsPkts128to255Octets,
etherStatsPkts256to511Octets,
etherStatsPkts512to1023Octets,
etherStatsPkts1024to1518Octets,
etherStatsOwner, etherStatsStatus
}
STATUS current
DESCRIPTION
"The RMON Ethernet Statistics Group."
::= { rmonGroups 1 }
::= { rmonGroups 1 }
rmonHistoryControlGroup OBJECT-GROUP
OBJECTS {
historyControlIndex, historyControlDataSource,
historyControlBucketsRequested,
historyControlBucketsGranted, historyControlInterval,
historyControlOwner, historyControlStatus
}
STATUS current
DESCRIPTION
"The RMON History Control Group."
::= { rmonGroups 2 }
rmonHistoryControlGroup OBJECT-GROUP
OBJECTS {
historyControlIndex, historyControlDataSource,
historyControlBucketsRequested,
historyControlBucketsGranted, historyControlInterval,
historyControlOwner, historyControlStatus
}
STATUS current
DESCRIPTION
"The RMON History Control Group."
::= { rmonGroups 2 }
rmonEthernetHistoryGroup OBJECT-GROUP
OBJECTS {
etherHistoryIndex, etherHistorySampleIndex,
etherHistoryIntervalStart, etherHistoryDropEvents,
etherHistoryOctets, etherHistoryPkts,
etherHistoryBroadcastPkts, etherHistoryMulticastPkts,
etherHistoryCRCAlignErrors, etherHistoryUndersizePkts,
etherHistoryOversizePkts, etherHistoryFragments,
etherHistoryJabbers, etherHistoryCollisions,
etherHistoryUtilization
}
STATUS current
DESCRIPTION
"The RMON Ethernet History Group."
::= { rmonGroups 3 }
rmonEthernetHistoryGroup OBJECT-GROUP
OBJECTS {
etherHistoryIndex, etherHistorySampleIndex,
etherHistoryIntervalStart, etherHistoryDropEvents,
etherHistoryOctets, etherHistoryPkts,
etherHistoryBroadcastPkts, etherHistoryMulticastPkts,
etherHistoryCRCAlignErrors, etherHistoryUndersizePkts,
etherHistoryOversizePkts, etherHistoryFragments,
etherHistoryJabbers, etherHistoryCollisions,
etherHistoryUtilization
}
STATUS current
DESCRIPTION
"The RMON Ethernet History Group."
::= { rmonGroups 3 }
rmonAlarmGroup OBJECT-GROUP
OBJECTS {
alarmIndex, alarmInterval, alarmVariable,
alarmSampleType, alarmValue, alarmStartupAlarm,
alarmRisingThreshold, alarmFallingThreshold,
alarmRisingEventIndex, alarmFallingEventIndex,
alarmOwner, alarmStatus
}
STATUS current
DESCRIPTION
"The RMON Alarm Group."
::= { rmonGroups 4 }
rmonAlarmGroup OBJECT-GROUP
OBJECTS {
alarmIndex, alarmInterval, alarmVariable,
alarmSampleType, alarmValue, alarmStartupAlarm,
alarmRisingThreshold, alarmFallingThreshold,
alarmRisingEventIndex, alarmFallingEventIndex,
alarmOwner, alarmStatus
}
STATUS current
DESCRIPTION
"The RMON Alarm Group."
::= { rmonGroups 4 }
rmonHostGroup OBJECT-GROUP OBJECTS { hostControlIndex, hostControlDataSource, hostControlTableSize, hostControlLastDeleteTime, hostControlOwner, hostControlStatus,
rmonHostGroup对象组对象{hostControlIndex，hostControlDataSource，hostControlTableSize，HostControlAstDeleteTime，hostControlOwner，hostControlStatus，
hostAddress, hostCreationOrder, hostIndex,
hostInPkts, hostOutPkts, hostInOctets,
hostOutOctets, hostOutErrors, hostOutBroadcastPkts,
hostOutMulticastPkts, hostTimeAddress,
hostTimeCreationOrder, hostTimeIndex,
hostTimeInPkts, hostTimeOutPkts, hostTimeInOctets,
hostTimeOutOctets, hostTimeOutErrors,
hostTimeOutBroadcastPkts, hostTimeOutMulticastPkts
}
STATUS current
DESCRIPTION
"The RMON Host Group."
::= { rmonGroups 5 }
hostAddress, hostCreationOrder, hostIndex,
hostInPkts, hostOutPkts, hostInOctets,
hostOutOctets, hostOutErrors, hostOutBroadcastPkts,
hostOutMulticastPkts, hostTimeAddress,
hostTimeCreationOrder, hostTimeIndex,
hostTimeInPkts, hostTimeOutPkts, hostTimeInOctets,
hostTimeOutOctets, hostTimeOutErrors,
hostTimeOutBroadcastPkts, hostTimeOutMulticastPkts
}
STATUS current
DESCRIPTION
"The RMON Host Group."
::= { rmonGroups 5 }
rmonHostTopNGroup OBJECT-GROUP
OBJECTS {
hostTopNControlIndex, hostTopNHostIndex,
hostTopNRateBase, hostTopNTimeRemaining,
hostTopNDuration, hostTopNRequestedSize,
hostTopNGrantedSize, hostTopNStartTime,
hostTopNOwner, hostTopNStatus,
hostTopNReport, hostTopNIndex,
hostTopNAddress, hostTopNRate
}
STATUS current
DESCRIPTION
"The RMON Host Top 'N' Group."
::= { rmonGroups 6 }
rmonHostTopNGroup OBJECT-GROUP
OBJECTS {
hostTopNControlIndex, hostTopNHostIndex,
hostTopNRateBase, hostTopNTimeRemaining,
hostTopNDuration, hostTopNRequestedSize,
hostTopNGrantedSize, hostTopNStartTime,
hostTopNOwner, hostTopNStatus,
hostTopNReport, hostTopNIndex,
hostTopNAddress, hostTopNRate
}
STATUS current
DESCRIPTION
"The RMON Host Top 'N' Group."
::= { rmonGroups 6 }
rmonMatrixGroup OBJECT-GROUP
OBJECTS {
matrixControlIndex, matrixControlDataSource,
matrixControlTableSize, matrixControlLastDeleteTime,
matrixControlOwner, matrixControlStatus,
matrixSDSourceAddress, matrixSDDestAddress,
matrixSDIndex, matrixSDPkts,
matrixSDOctets, matrixSDErrors,
matrixDSSourceAddress, matrixDSDestAddress,
matrixDSIndex, matrixDSPkts,
matrixDSOctets, matrixDSErrors
}
STATUS current
DESCRIPTION
"The RMON Matrix Group."
::= { rmonGroups 7 }
rmonMatrixGroup OBJECT-GROUP
OBJECTS {
matrixControlIndex, matrixControlDataSource,
matrixControlTableSize, matrixControlLastDeleteTime,
matrixControlOwner, matrixControlStatus,
matrixSDSourceAddress, matrixSDDestAddress,
matrixSDIndex, matrixSDPkts,
matrixSDOctets, matrixSDErrors,
matrixDSSourceAddress, matrixDSDestAddress,
matrixDSIndex, matrixDSPkts,
matrixDSOctets, matrixDSErrors
}
STATUS current
DESCRIPTION
"The RMON Matrix Group."
::= { rmonGroups 7 }
rmonFilterGroup OBJECT-GROUP OBJECTS {
rmonFilterGroup对象组对象{
filterIndex, filterChannelIndex, filterPktDataOffset,
filterPktData, filterPktDataMask,
filterPktDataNotMask, filterPktStatus,
filterPktStatusMask, filterPktStatusNotMask,
filterOwner, filterStatus,
channelIndex, channelIfIndex, channelAcceptType,
channelDataControl, channelTurnOnEventIndex,
channelTurnOffEventIndex, channelEventIndex,
channelEventStatus, channelMatches,
channelDescription, channelOwner, channelStatus
}
STATUS current
DESCRIPTION
"The RMON Filter Group."
::= { rmonGroups 8 }
filterIndex, filterChannelIndex, filterPktDataOffset,
filterPktData, filterPktDataMask,
filterPktDataNotMask, filterPktStatus,
filterPktStatusMask, filterPktStatusNotMask,
filterOwner, filterStatus,
channelIndex, channelIfIndex, channelAcceptType,
channelDataControl, channelTurnOnEventIndex,
channelTurnOffEventIndex, channelEventIndex,
channelEventStatus, channelMatches,
channelDescription, channelOwner, channelStatus
}
STATUS current
DESCRIPTION
"The RMON Filter Group."
::= { rmonGroups 8 }
rmonPacketCaptureGroup OBJECT-GROUP
OBJECTS {
bufferControlIndex, bufferControlChannelIndex,
bufferControlFullStatus, bufferControlFullAction,
bufferControlCaptureSliceSize,
bufferControlDownloadSliceSize,
bufferControlDownloadOffset,
bufferControlMaxOctetsRequested,
bufferControlMaxOctetsGranted,
bufferControlCapturedPackets,
bufferControlTurnOnTime,
bufferControlOwner, bufferControlStatus,
captureBufferControlIndex, captureBufferIndex,
captureBufferPacketID, captureBufferPacketData,
captureBufferPacketLength, captureBufferPacketTime,
captureBufferPacketStatus
}
STATUS current
DESCRIPTION
"The RMON Packet Capture Group."
::= { rmonGroups 9 }
rmonPacketCaptureGroup OBJECT-GROUP
OBJECTS {
bufferControlIndex, bufferControlChannelIndex,
bufferControlFullStatus, bufferControlFullAction,
bufferControlCaptureSliceSize,
bufferControlDownloadSliceSize,
bufferControlDownloadOffset,
bufferControlMaxOctetsRequested,
bufferControlMaxOctetsGranted,
bufferControlCapturedPackets,
bufferControlTurnOnTime,
bufferControlOwner, bufferControlStatus,
captureBufferControlIndex, captureBufferIndex,
captureBufferPacketID, captureBufferPacketData,
captureBufferPacketLength, captureBufferPacketTime,
captureBufferPacketStatus
}
STATUS current
DESCRIPTION
"The RMON Packet Capture Group."
::= { rmonGroups 9 }
rmonEventGroup OBJECT-GROUP
OBJECTS {
eventIndex, eventDescription, eventType,
eventCommunity, eventLastTimeSent,
eventOwner, eventStatus,
logEventIndex, logIndex, logTime,
logDescription
}
STATUS current
DESCRIPTION
rmonEventGroup OBJECT-GROUP
OBJECTS {
eventIndex, eventDescription, eventType,
eventCommunity, eventLastTimeSent,
eventOwner, eventStatus,
logEventIndex, logIndex, logTime,
logDescription
}
STATUS current
DESCRIPTION
"The RMON Event Group."
::= { rmonGroups 10 }
"The RMON Event Group."
::= { rmonGroups 10 }
rmonNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { risingAlarm, fallingAlarm }
STATUS current
DESCRIPTION
"The RMON Notification Group."
::= { rmonGroups 11 }
END
rmonNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { risingAlarm, fallingAlarm }
STATUS current
DESCRIPTION
"The RMON Notification Group."
::= { rmonGroups 11 }
END
In order to implement this MIB, a probe must capture all packets on the locally-attached network, including packets between third parties. These packets are analyzed to collect network addresses, protocol usage information, and conversation statistics. Data of this nature may be considered sensitive in some environments. In such environments the administrator may wish to restrict SNMP access to the probe.
为了实现此MIB，探测器必须捕获本地连接网络上的所有数据包，包括第三方之间的数据包。对这些数据包进行分析，以收集网络地址、协议使用信息和会话统计信息。在某些环境中，这种性质的数据可能被视为敏感数据。在这种环境中，管理员可能希望限制对探测器的SNMP访问。
This MIB also includes functions for returning the contents of captured packets, potentially including sensitive user data or passwords. It is recommended that SNMP access to these functions be restricted.
此MIB还包括用于返回捕获数据包内容的函数，可能包括敏感用户数据或密码。建议限制对这些功能的SNMP访问。
There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
此MIB中定义了许多管理对象，它们的MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is recommended that the implementors consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [12] and the View-based Access Control Model RFC 2575 [15] is recommended.
建议执行者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2574[12]和基于视图的访问控制模型RFC 2575[15]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
This document was produced by the IETF Remote Network Monitoring Working Group.
本文件由IETF远程网络监控工作组编制。
Steve Waldbusser
史蒂夫·瓦尔德布瑟
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.com
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.com
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[1] Harrington，D.，Presuhn，R.，和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[5] 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.
[5] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[11] Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC2573，1999年4月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC2575，1999年4月。
[16] McCloghrie, K. and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
[16] McCloghrie，K.和M.Rose，编辑，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, November 1997.
[17] McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 2233，1997年11月。
[18] Waldbusser, S., "Remote Network Monitoring MIB", RFC 1757, February 1995.
[18] Waldbusser，S.，“远程网络监控MIB”，RFC 1757，1995年2月。
[19] Waldbusser, S., "Token Ring Extensions to the Remote Network Monitoring MIB", RFC 1513, September 1993.
[19] Waldbusser，S.，“远程网络监控MIB的令牌环扩展”，RFC 1513，1993年9月。
[20] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[20] Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，RFC 2021，1997年1月。
[21] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser, "Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0", RFC 2613, June 1999.
[21] Waterman，R.，Lahaye，B.，Romascanu，D.和S.Waldbusser，“交换网络1.0版的远程网络监控MIB扩展”，RFC 2613，1999年6月。
[22] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[22] Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。