Network Working Group D. Romascanu
Request for Comments: 3144 Avaya, Inc.
Category: Standards Track August 2001
Network Working Group D. Romascanu
Request for Comments: 3144 Avaya, Inc.
Category: Standards Track August 2001
Remote Monitoring MIB Extensions for Interface Parameters Monitoring
用于接口参数监控的远程监控MIB扩展
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 (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Remote Monitoring MIB with a method of sorting the interfaces of a monitored device according to values of parameters specific to this interface.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。该文件提出了对远程监控MIB的扩展，该扩展采用了一种根据特定于该接口的参数值对受监控设备的接口进行排序的方法。
Table of Contents
目录
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . 2
2 The SNMP Management Framework . . . . . . . . . . . . . . . 2
3 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 MIB Structure . . . . . . . . . . . . . . . . . . . . . . . 4
5 Evolution of the Document, Limitations and Future Work. . . 4
6 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5
7 References. . . . . . . . . . . . . . . . . . . . . . . . . 26
8 Intellectual Property . . . . . . . . . . . . . . . . . . . 28
9 Security Considerations . . . . . . . . . . . . . . . . . . 29
10 Author's Address . . . . . . . . . . . . . . . . . . . . . 29
11 Full Copyright Statement . . . . . . . . . . . . . . . . . 30
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . 2
2 The SNMP Management Framework . . . . . . . . . . . . . . . 2
3 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 MIB Structure . . . . . . . . . . . . . . . . . . . . . . . 4
5 Evolution of the Document, Limitations and Future Work. . . 4
6 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5
7 References. . . . . . . . . . . . . . . . . . . . . . . . . 26
8 Intellectual Property . . . . . . . . . . . . . . . . . . . 28
9 Security Considerations . . . . . . . . . . . . . . . . . . 29
10 Author's Address . . . . . . . . . . . . . . . . . . . . . 29
11 Full Copyright Statement . . . . . . . . . . . . . . . . . 30
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a method of sorting the interfaces of a monitored device according to values of parameters specific to this interface.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了一种根据特定于该接口的参数值对受监控设备的接口进行排序的方法。
This memo also includes a MIB module. This MIB module extends the list of managed objects specified in [RFC2819] and [RFC2613].
此备忘录还包括一个MIB模块。此MIB模块扩展了[RFC2819]和[RFC2613]中指定的托管对象列表。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMEND", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“推荐”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [RFC2571].
o RFC 2571[RFC2571]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[RFC1155]、STD 16、RFC 1212[RFC1212]和RFC 1215[RFC1215]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15 RFC 1157[RFC1157]中进行了描述。SNMP消息协议的第二个版本不是Internet标准跟踪协议，称为SNMPv2c，在RFC 1901[RFC1901]和RFC 1906[RFC1906]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[RFC1906]、RFC 2572[RFC2572]和RFC 2574[RFC2574]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905].
o 访问管理信息的协议操作。STD 15、RFC 1157[RFC1157]中描述了第一组协议操作和相关PDU格式。RFC 1905[RFC1905]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575].
o RFC 2573[RFC2573]中描述的一组基本应用程序和RFC 2575[RFC2575]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[RFC2570]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
This document continues the architecture created in the RMON MIB [RFC2819] and extended by the SMON MIB [RFC2613] by providing a method of ordering the interfaces of a device according to the value of a specific parameter that characterizes the interfaces.
本文档通过提供一种根据接口特征的特定参数值对设备接口进行排序的方法，延续了RMON MIB[RFC2819]中创建并由SMON MIB[RFC2613]扩展的体系结构。
The need for such a technique derives from the evolution of the network devices - bridges, routers, etc., into complex entities with a large number of interfaces and with many parameters that need to be monitored on each interface. It is common for certain classes of switching devices to contain hundred of ports, and for each port to instrument and support tens of parameters - usually expressed as counters - for each interface. As a result, it becomes impossible for applications that monitor these devices to provide a view that would allow the user to understand easily what is the status of the device, whether the behavior of a port or interface is in normal boundaries or not, and which are the most congested or problematic interfaces of the device.
对这种技术的需求源于网络设备（网桥、路由器等）的演变，这些设备演变为具有大量接口和需要在每个接口上监控的许多参数的复杂实体。某些类型的交换设备通常包含数百个端口，每个端口为每个接口检测和支持数十个参数（通常表示为计数器）。因此，监控这些设备的应用程序不可能提供一个视图，该视图将允许用户轻松了解设备的状态，端口或接口的行为是否在正常边界内，以及哪些是设备最拥挤或有问题的接口。
This document tries to answer this problem by proposing a method of providing a sorted list of interfaces according to programmable criteria. The result of applying this method will be a shorter list, that includes the most significant interfaces sorted according to the selected criteria. One possible action that can be taken by a network manager could be applying to this interface a copy port operation to a destination port that has a dedicated monitoring device (e.g., a network analyzer) connected to it. A standard MIB interface for performing this operation is described in [RFC2613].
本文试图通过提出一种根据可编程标准提供接口排序列表的方法来回答这个问题。应用此方法的结果将是一个较短的列表，其中包括根据所选标准排序的最重要接口。网络管理器可以采取的一种可能的操作是将复制端口操作应用于连接有专用监控设备（如网络分析仪）的目标端口。[RFC2613]中描述了用于执行此操作的标准MIB接口。
This MIB contains one MIB group:
此MIB包含一个MIB组：
- The interfaceTopNObjects
- 接口对象
The interfaceTopNObjects includes one capability object and two tables:
interfaceTopNObjects包括一个功能对象和两个表：
- The interfaceControlTable - The interfaceTopNTable
- interfaceControlTable-InterfaceTopTable
The interfaceControlTable is an RMON-style control table, allowing for the creation of interfaceTopN reports. The parameters specific for each report, like the duration of the report, the number of reports, start time and the characteristics of the variables that are sorted (absolute, 'deltas' or percentage of the total bandwidth) are set in this table. An optional operation that is controlled from this table is the normalization of values of the variables, which allows for sorting of variables on the interfaces, despite the basic speed of the interfaces being different on different interfaces.
interfaceControlTable是一个RMON样式的控制表，允许创建interfaceTopN报告。此表中设置了每个报告的特定参数，如报告持续时间、报告数量、开始时间和已排序变量的特征（绝对值、“增量”或总带宽的百分比）。从该表控制的一个可选操作是变量值的标准化，它允许对接口上的变量进行排序，尽管不同接口上的接口基本速度不同。
The RMON MIB Working Group included in its Charter a MIB document that would offer a solution to the problem of quickly determining the most congested (highest utilized) physical ports and links in an RMON-capable device with multiple interfaces.
RMON MIB工作组在其章程中包括一份MIB文件，该文件将为快速确定具有多个接口的支持RMON的设备中最拥挤（利用率最高）的物理端口和链路的问题提供解决方案。
An initial solution, proposed in the first version of this document included a limited approach. The objects whose values are used as criteria for sorting are elements in tables indexed by an InterfaceIndex type of object, as defined in [RFC2863]. This approach simplifies the search algorithm and the result table, but restricts the method to interface parameters. A more generic ' usrTopN' function was initially considered out of the scope of this work.
本文件第一版中提出的初步解决方案包括有限的方法。其值用作排序标准的对象是由[RFC2863]中定义的InterfaceIndex类型的对象索引的表中的元素。这种方法简化了搜索算法和结果表，但将方法限制在接口参数上。一个更通用的“usrTopN”函数最初被认为不在本工作范围内。
At the Working Group meeting in Adelaide in March 2000, it was decided to try to define the more generic function of usrTopN. Under this approach, variables belonging to tables with any type of index can be sorted, but at expense of extra processing and sanity checking by the agent.
2000年3月在阿德莱德举行的工作组会议上，决定尝试定义usrTopN的更通用功能。在这种方法下，可以对属于具有任何类型索引的表的变量进行排序，但需要代理进行额外的处理和健全性检查。
At the interim meeting of the RMON Working Group in San Francisco, in May 2000, it was decided that the usrTopN solution would not be continued in this phase of the work. One of the reasons is that it is difficult to achieve a normalization factor for a generic
在2000年5月的RMON工作组在旧金山的临时会议上，决定UrtoPn解决方案不会在这一工作阶段继续进行。其中一个原因是很难为泛型实现标准化因子
approach. The group agreed it is not desirable to require the application to plug-in the scaling factor for every instance that might be included in a TopN report.
方法工作组一致认为，不需要要求应用程序为可能包含在TopN报告中的每个实例插入比例因子。
INTERFACETOPN-MIB DEFINITIONS ::= BEGIN
INTERFACETOPN-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32 FROM SNMPv2-SMI RowStatus, TimeStamp, TruthValue FROM SNMPv2-TC rmon, OwnerString FROM RMON-MIB CounterBasedGauge64 FROM HCNUM-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
从SNMPv2 SMI RowStatus导入模块标识、对象类型、整数32、量规32，从SNMPv2 TC rmon导入时间戳、TruthValue，从rmon-MIB CounterBasedGauge64导入所有者字符串，从HCNUM-TC MODULE-COMPLIANCE导入对象组，从SNMPv2 CONF导入对象组；
interfaceTopNMIB MODULE-IDENTITY LAST-UPDATED "200103270000Z" ORGANIZATION "IETF RMON MIB Working Group" CONTACT-INFO "
interfaceTopNMIB模块标识最后更新“200103270000Z”组织“IETF RMON MIB工作组”联系方式
Dan Romascanu Avaya Inc. Tel: +972-3-645-8414 Email: dromasca@avaya.com"
Dan Romascanu Avaya Inc.电话：+972-3-645-8414电子邮件：dromasca@avaya.com"
DESCRIPTION
"The MIB module for sorting device interfaces for RMON and
SMON monitoring in a multiple device implementation."
::= { rmon 27 }
interfaceTopNObjects OBJECT IDENTIFIER ::= { interfaceTopNMIB 1 }
interfaceTopNNotifications OBJECT IDENTIFIER ::= { interfaceTopNMIB 2 }
interfaceTopNConformance OBJECT IDENTIFIER ::= { interfaceTopNMIB 3 }
DESCRIPTION
"The MIB module for sorting device interfaces for RMON and
SMON monitoring in a multiple device implementation."
::= { rmon 27 }
interfaceTopNObjects OBJECT IDENTIFIER ::= { interfaceTopNMIB 1 }
interfaceTopNNotifications OBJECT IDENTIFIER ::= { interfaceTopNMIB 2 }
interfaceTopNConformance OBJECT IDENTIFIER ::= { interfaceTopNMIB 3 }
-- The Interface Top N group is used to prepare reports that
-- describe a list of interfaces (data sources)
-- ordered by the values of one
-- of the objects that apply to the interfaces of the respective device.
-- Those objects are defined by standard MIBs. The exact objects that
-- are supported by the agent are described by interfaceTopNCaps
-- The objects must be elements in tables indexed only by an
-- InterfaceIndex object.
-- The objects chosen by the
-- The Interface Top N group is used to prepare reports that
-- describe a list of interfaces (data sources)
-- ordered by the values of one
-- of the objects that apply to the interfaces of the respective device.
-- Those objects are defined by standard MIBs. The exact objects that
-- are supported by the agent are described by interfaceTopNCaps
-- The objects must be elements in tables indexed only by an
-- InterfaceIndex object.
-- The objects chosen by the
-- management station may be sampled over a management
-- station-specified time interval, making the report rate based.
-- The management station also specifies the number of interfaces
-- that are reported.
--
-- The interfaceTopNControlTable is used to initiate the generation
-- of a report. The management station may select the parameters
-- of such a report, such as which object, how
-- many interfaces, and the start & stop times of the sampling. When
-- the report is prepared, entries are created in the
-- interfaceTopNTable associated with the relevant
-- interfaceTopNControlEntry. These entries are static for
-- each report after it has been prepared.
-- management station may be sampled over a management
-- station-specified time interval, making the report rate based.
-- The management station also specifies the number of interfaces
-- that are reported.
--
-- The interfaceTopNControlTable is used to initiate the generation
-- of a report. The management station may select the parameters
-- of such a report, such as which object, how
-- many interfaces, and the start & stop times of the sampling. When
-- the report is prepared, entries are created in the
-- interfaceTopNTable associated with the relevant
-- interfaceTopNControlEntry. These entries are static for
-- each report after it has been prepared.
interfaceTopNCaps OBJECT-TYPE SYNTAX BITS { ifInOctets(0), ifInUcastPkts(1), ifInNUcastPkts(2), ifInDiscards(3), ifInErrors(4), ifInUnknownProtos(5), ifOutOctets(6), ifOutUcastPkts(7), ifOutNUcastPkts(8), ifOutDiscards(9), ifOutErrors(10), ifInMulticastPkts(11), ifInBroadcastPkts(12), ifOutMulticastPkts(13), ifOutBroadcastPkts(14), ifHCInOctets(15), ifHCInUcastPkts(16), ifHCInMulticastPkts(17), ifHCInBroadcastPkts(18), ifHCOutOctets(19), ifHCOutUcastPkts(20), ifHCOutMulticastPkts(21), ifHCOutBroadcastPkts(22), dot3StatsAlignmentErrors(23), dot3StatsFCSErrors(24), dot3StatsSingleCollisionFrames(25), dot3StatsMultipleCollisionFrames(26), dot3StatsSQETestErrors(27), dot3StatsDeferredTransmissions(28), dot3StatsLateCollisions(29), dot3StatsExcessiveCollisions(30), dot3StatsInternalMacTxErrors(31),
interfaceTopNCaps对象类型语法位{ifInOctets（0）、ifInUcastPkts（1）、ifInNUcastPkts（2）、ifInDiscards（3）、ifInErrors（4）、IFinknownprotos（5）、ifOutOctets（6）、ifOutUcastPkts（7）、ifOutNUcastPkts（8）、ifOutDiscards（9）、ifOutErrors（10）、ifInMulticastPkts（11）、ifInBroadcastPkts（12）、ifOutMulticastPkts（13）、IFoutPKTs（14）、ifHCInOctets（15），ifHCInUcastPkts（16），ifHCInMulticastPkts（17），ifHCInBroadcastPkts（18），ifHCOutOctets（19），ifHCOutUcastPkts（20），ifHCOutMulticastPkts（21），ifHCOutBroadcastPkts（22），dot3StatsAlignmentErrors（23），dot3statsfcerrors（24），dot3StatsSingleCollisionFrames（25），dot3StatsMultipleCollisionFrames（26），dot3statssqeterrors（27），Dot3StatsDeferredTransmission（28），Dot3StatsSlateCollisions（29），Dot3StatsAccessiveCollisions（30），Dot3StatsInternalActxerRors（31），
dot3StatsCarrierSenseErrors(32), dot3StatsFrameTooLongs(33), dot3StatsInternalMacRxErrors(34), dot3StatsSymbolErrors(35), dot3InPauseFrames(36), dot3OutPauseFrames(37), dot5StatsLineErrors(38), dot5StatsBurstErrors(39), dot5StatsACErrors(40), dot5StatsAbortTransErrors(41), dot5StatsInternalErrors(42), dot5StatsLostFrameErrors(43), dot5StatsReceiveCongestions(44), dot5StatsFrameCopiedErrors(45), dot5StatsTokenErrors(46), dot5StatsSoftErrors(47), dot5StatsHardErrors(48), dot5StatsSignalLoss(49), dot5StatsTransmitBeacons(50), dot5StatsRecoverys(51), dot5StatsLobeWires(52), dot5StatsRemoves(53), dot5StatsSingles(54), dot5StatsFreqErrors(55), etherStatsDropEvents(56), etherStatsOctets(57), etherStatsPkts(58), etherStatsBroadcastPkts(59), etherStatsMulticastPkts(60), etherStatsCRCAlignErrors(61), etherStatsUndersizePkts(62), etherStatsOversizePkts(63), etherStatsFragments(64), etherStatsJabbers(65), etherStatsCollisions(66), etherStatsPkts64Octets(67), etherStatsPkts65to127Octets(68), etherStatsPkts128to255Octets(69), etherStatsPkts256to511Octets(70), etherStatsPkts512to1023Octets(71), etherStatsPkts1024to1518Octets(72), dot1dTpPortInFrames(73), dot1dTpPortOutFrames(74), dot1dTpPortInDiscards(75) } MAX-ACCESS read-only STATUS current DESCRIPTION
DOT3STATSCARRIERSENSERERRORS（32）、DOT3STATSFRAMETOLONGS（33）、dot3StatsInternalMacRxErrors（34）、dot3StatsSymbolErrors（35）、DOT3INPUSEFRAMES（36）、dot3OutPauseFrames（37）、DOT5STATSLINERRORS（38）、DOT5STATSBURTERRORS（39）、dot5StatsACErrors（40）、DOT5STATSABORTTTRANSERRORS（41）、DOT5STATSINTERNALERRRORS（42）、DOT5STATSLOSTFRAMERRORS（43），Dot5StatsReceiveCongressions（44）、dot5StatsFrameCopiedErrors（45）、dot5StatsTokenErrors（46）、dot5StatsSoftErrors（47）、dot5StatsHardErrors（48）、dot5StatsSignalLoss（49）、dot5StatsTransmitBeacons（50）、Dot5StatsRecovery（51）、dot5StatsLobeWires（52）、dot5StatsRemoves（53）、dot5StatsSingles（54）、Dot5StatsFrequerErrors（55）、EtherstDropEvents（56），以太八位元（57）、以太八位元（58）、以太八位元（59）、以太八位元（60）、以太八位元（61）、以太八位元（62）、以太八位元（63）、以太六位元（64）、以太六位元（65）、以太六位元（66）、以太六位元（67）、以太六位元（65）到127位元（68），EtherstStatsPKTS128to255Octets（69）、EtherstStatsPKTS256to511Octets（70）、EtherstStatsPKTS512to1023Octets（71）、EtherstStatsPKTS1024to1518Octets（72）、Dot1DTPortinFrames（73）、Dot1DTPortOutFrames（74）、Dot1DTPortInDiscards（75）}MAX-ACCESS只读状态当前说明
"The type(s) of sorting capabilities supported by the agent.
“代理支持的排序功能的类型。
If the agent can perform sorting of interfaces according to the values of ifInOctets, as defined in [RFC2863], then the 'ifInOctets' bit will be set.
如果代理可以根据[RFC2863]中定义的IFinoctes值对接口进行排序，则将设置“IFinoctes”位。
If the agent can perform sorting of interfaces according to the values of ifInUcastPkts, as defined in [RFC2863], then the 'ifInUcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifInUcastPkts的值对接口进行排序，则将设置“ifInUcastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifInNUcastPkts, as defined in [RFC2863], then the 'ifInNUcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的IFinNucastPts值对接口进行排序，则将设置“IFinNucastPts”位。
If the agent can perform sorting of interfaces according to the values of ifInDiscards, as defined in [RFC2863], then the 'ifInDiscards' bit will be set.
如果代理可以根据[RFC2863]中定义的ifInDiscards值对接口进行排序，则将设置“ifInDiscards”位。
If the agent can perform sorting of interfaces according to the values of ifInErrors, as defined in [RFC2863], then the 'ifInErrors' bit will be set.
如果代理可以根据[RFC2863]中定义的IFinerror值对接口进行排序，则将设置“IFinerror”位。
If the agent can perform sorting of interfaces according to the values of ifInUnknownProtocols, as defined in [RFC2863], then the 'ifInUnknownProtocols' bit will be set.
如果代理可以根据[RFC2863]中定义的ifInUnknownProtocols的值对接口进行排序，则将设置“ifInUnknownProtocols”位。
If the agent can perform sorting of interfaces according to the values of ifOutOctets, as defined in [RFC2863], then the 'ifOutOctets' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutOctets值对接口进行排序，则将设置“ifOutOctets”位。
If the agent can perform sorting of interfaces according to the values of ifOutUcastPackets, as defined in [RFC2863], then the 'ifOutUcastPackets' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutUcastPackets的值对接口进行排序，则将设置“ifOutUcastPackets”位。
If the agent can perform sorting of interfaces according to the values of ifOutNUcastPackets, as defined in [RFC2863], then the 'ifOutNUcastPackets' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutNUcastPackets的值对接口进行排序，则将设置“ifOutNUcastPackets”位。
If the agent can perform sorting of interfaces according to the values of ifOutDiscards, as defined in [RFC2863], then the 'ifOutDiscards' bit will be set.
如果代理可以根据[RFC2863]中定义的IFOUTDARDS值对接口进行排序，则将设置“IFOUTDARDS”位。
If the agent can perform sorting of interfaces according to the values of ifOutErrors, as defined in [RFC2863], then the 'ifOutErrors' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutErrors值对接口进行排序，则将设置“ifOutErrors”位。
If the agent can perform sorting of interfaces according to the values of ifInMulticastPkts, as defined in [RFC2863],
如果代理可以根据[RFC2863]中定义的ifInMulticastPkts的值对接口进行排序，
then the 'ifInMulticastPkts' bit will be set.
然后将设置“ifInMulticastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifInBroadcastPkts, as defined in [RFC2863], then the 'ifInBroadcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifInBroadcastPkts的值对接口进行排序，则将设置“ifInBroadcastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifOutMulticastPkts, as defined in [RFC2863], then the 'ifOutMulticastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutMulticastPkts的值对接口进行排序，则将设置“ifOutMulticastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifOutBroadcastPkts, as defined in [RFC2863], then the 'ifOutBroadcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifOutBroadcastPkts的值对接口进行排序，则将设置“ifOutBroadcastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifHCInOctets, as defined in [RFC2863], then the 'ifHCInOctets' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCInOctets值对接口进行排序，则将设置“ifHCInOctets”位。
If the agent can perform sorting of interfaces according to the values of ifHCInMulticastPkts, as defined in [RFC2863], then the 'ifHCInMulticastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCInMulticastPkts的值对接口进行排序，则将设置“ifHCInMulticastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifHCInBroadcastPkts, as defined in [RFC2863], then the 'ifHCInBroadcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCInBroadcastPkts的值对接口进行排序，则将设置“ifHCInBroadcastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifHCOutOctets, as defined in [RFC2863], then the 'ifHCOutOctets' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCOutOctets值对接口进行排序，则将设置“ifHCOutOctets”位。
If the agent can perform sorting of interfaces according to the values of ifHCOutUcastPkts, as defined in [RFC2863], then the 'ifHCOutUcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCOutUcastPkts的值对接口进行排序，则将设置“ifHCOutUcastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifHCOutMulticastPkts, as defined in [RFC2863], then the 'ifHCOutMulticastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCOutMulticastPkts的值对接口进行排序，则将设置“ifHCOutMulticastPkts”位。
If the agent can perform sorting of interfaces according to the values of ifHCOutBroadcastPkts, as defined in [RFC2863], then the 'ifHCOutBroadcastPkts' bit will be set.
如果代理可以根据[RFC2863]中定义的ifHCOutBroadcastPkts的值对接口进行排序，则将设置“ifHCOutBroadcastPkts”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsAlignmentErrors, as defined in [RFC2665], then the 'dot3StatsAlignmentErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsAlignmentErrors的值对接口进行排序，则将设置“dot3StatsAlignmentErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsFCSErrors, as defined in [RFC2665],
如果代理可以根据[RFC2665]中定义的DOT3STATSCSERRORS值对接口进行排序，
then the 'dot3StatsFCSErrors' bit will be set.
然后将设置“dot3StatsFCSErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsSingleCollisionFrames, as defined in [RFC2665],then the 'dot3StatsSingleCollisionFrames' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsSingleCollisionFrames的值对接口进行排序，则将设置“dot3StatsSingleCollisionFrames”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsSQETestErrors, as defined in [RFC2665], then the 'dot3StatsSQETestErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsSQETestErrors的值对接口进行排序，则将设置“dot3StatsSQETestErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsDeferredTransmissions, as defined in [RFC2665], then the 'dot3StatsDeferredTransmissions' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsDeferredTransmissions的值对接口进行排序，则将设置“dot3StatsDeferredTransmissions”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsLateCollisions, as defined in [RFC2665], then the 'dot3StatsLateCollisions' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsLateCollisions的值对接口进行排序，则将设置“dot3StatsLateCollisions”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsExcessiveCollisions, as defined in [RFC2665], then the 'dot3StatsExcessiveCollisions' bit will be set.
如果代理可以根据[RFC2665]中定义的Dot3StatsAccessiveCollisions的值对接口进行排序，则将设置“Dot3StatsAccessiveCollisions”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsInternalMacTxErrors, as defined in [RFC2665],then the 'dot3StatsInternalMacTxErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsInternalMacTxErrors值对接口进行排序，则将设置“dot3StatsInternalMacTxErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsCarrierSenseErrors, as defined in [RFC2665], then the 'dot3StatsCarrierSenseErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsCarrierSenseErrors值对接口进行排序，则将设置“dot3StatsCarrierSenseErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsFrameTooLongs, as defined in [RFC2665], then the 'dot3StatsFrameTooLongs' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsFrameTooLongs的值对接口进行排序，则将设置“dot3StatsFrameTooLongs”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsInternalMacRxErrors, as defined in [RFC2665], then the 'dot3StatsInternalMacRxErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsInternalMacRxErrors的值对接口进行排序，则将设置“dot3StatsInternalMacRxErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3StatsSymbolErrors, as defined in [RFC2665], then the 'dot3StatsSymbolErrors' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3StatsSymbolErrors值对接口进行排序，则将设置“dot3StatsSymbolErrors”位。
If the agent can perform sorting of interfaces according to the values of dot3InPauseFrames, as defined in [RFC2665],
如果代理可以根据[RFC2665]中定义的dot3InPauseFrames值对接口进行排序，
then the 'dot3InPauseFrames' bit will be set.
然后将设置“dot3inpuseframes”位。
If the agent can perform sorting of interfaces according to the values of dot3OutPauseFrames, as defined in [RFC2665], then the 'dot3OutPauseFrames' bit will be set.
如果代理可以根据[RFC2665]中定义的dot3OutPauseFrames值对接口进行排序，则将设置“dot3OutPauseFrames”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsLineErrors, as defined in [RFC1748], then the 'dot5StatsLineErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的DOT5STATSLINERRORS值对接口进行排序，则将设置“DOT5STATSLINERRORS”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsBurstErrors, as defined in [RFC1748], then the 'dot5StatsBurstErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsBurstErrors值对接口进行排序，则将设置“dot5StatsBurstErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsACErrors, as defined in [RFC1748], then the 'dot5StatsACErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsACErrors值对接口进行排序，则将设置“dot5StatsACErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsAbortTransErrors, as defined in [RFC1748], then the 'dot5StatsAbortTransErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsAbortTransErrors值对接口进行排序，则将设置“dot5StatsAbortTransErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsInternalErrors, as defined in [RFC1748], then the 'dot5StatsInternalErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsInternalErrors值对接口进行排序，则将设置“dot5StatsInternalErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsLostFrameErrors, as defined in [RFC1748], then the 'dot5StatsLostFrameErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsLostFrameErrors的值对接口进行排序，则将设置“dot5StatsLostFrameErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsReceiveCongestionErrors, as defined in [RFC1748], then the 'dot5StatsReceiveCongestionErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的Dot5StatsReceive充血Errors的值对接口进行排序，则将设置“Dot5StatsReceive充血Errors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsFrameCopiedErrors, as defined in [RFC1748], then the 'dot5StatsFrameCopiedErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsFrameCopiedErrors的值对接口进行排序，则将设置“dot5StatsFrameCopiedErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsTokenErrors, as defined in [RFC1748], then the 'dot5StatsTokenErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsTokenErrors的值对接口进行排序，则将设置“dot5StatsTokenErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsSoftErrors, as defined in [RFC1748], then the 'dot5StatsSoftErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsSoftErrors值对接口进行排序，则将设置“dot5StatsSoftErrors”位。
If the agent can perform sorting of interfaces according to the
如果代理可以根据
values of dot5StatsHardErrors, as defined in [RFC1748], then the 'dot5StatsHardErrors' bit will be set.
dot5StatsHardErrors的值，如[RFC1748]中所定义，则将设置“dot5StatsHardErrors”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsSignalLoss, as defined in [RFC1748], then the 'dot5StatsSignalLoss' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsSignalLoss的值对接口进行排序，则将设置“dot5StatsSignalLoss”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsTransmitBeacons, as defined in [RFC1748], then the 'dot5StatsTransmitBeacons' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsTransmitBeacons值对接口进行排序，则将设置“dot5StatsTransmitBeacons”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsRecoverys, as defined in [RFC1748], then the 'dot5StatsRecoverys' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsRecoverys值对接口进行排序，则将设置“dot5StatsRecoverys”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsLobeWires, as defined in [RFC1748], then the 'dot5StatsLobeWires' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsLobeWires的值对接口进行排序，则将设置“dot5StatsLobeWires”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsRemoves, as defined in [RFC1748], then the 'dot5StatsRemoves' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsRemoves的值对接口进行排序，则将设置“dot5StatsRemoves”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsSingles, as defined in [RFC1748], then the 'dot5StatsSingles' bit will be set.
如果代理可以根据[RFC1748]中定义的dot5StatsSingles值对接口进行排序，则将设置“dot5StatsSingles”位。
If the agent can perform sorting of interfaces according to the values of dot5StatsFreqErrors, as defined in [RFC1748], then the 'dot5StatsFreqErrors' bit will be set.
如果代理可以根据[RFC1748]中定义的DOT5STATSFREKERRORS值对接口进行排序，则将设置“DOT5STATSFREKERRORS”位。
If the agent can perform sorting of interfaces according to the values of etherStatsDropEvents, as defined in [RFC2819], then the 'etherStatsDropEvents' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsDropEvents的值对接口进行排序，则将设置“etherStatsDropEvents”位。
If the agent can perform sorting of interfaces according to the values of etherStatsOctets, as defined in [RFC2819], then the 'etherStatsOctets' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsOctets值对接口进行排序，则将设置“etherStatsOctets”位。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts, as defined in [RFC2819], then the 'etherStatsPkts' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsPkts的值对接口进行排序，则将设置“etherStatsPkts”位。
If the agent can perform sorting of interfaces according to the values of etherStatsBroadcastPkts, as defined in [RFC2819], then the 'etherStatsBroadcastPkts' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherstStatsBroadcastPKTS的值对接口进行排序，则将设置“EtherstStatsBroadcastPKTS”位。
If the agent can perform sorting of interfaces according to the
如果代理可以根据
values of etherStatsMulticastPkts, as defined in [RFC2819], then the 'etherStatsMulticastPkts' bit will be set.
EtherstStatsMulticastPKTS的值，如[RFC2819]中所定义，则将设置“EtherstStatsMulticastPKTS”位。
If the agent can perform sorting of interfaces according to the values of etherStatsCRCAlignErrors, as defined in [RFC2819], then the 'etherStatsCRCAlignErrors' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherStatSCarAlignErrors的值对接口进行排序，则将设置“EtherStatSCarAlignErrors”位。
If the agent can perform sorting of interfaces according to the values of etherStatsUndersizePkts, as defined in [RFC2819], then the 'etherStatsUndersizePkts' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherstStatsUnderSizePkts的值对接口进行排序，则将设置“EtherstStatsUnderSizePkts”位。
If the agent can perform sorting of interfaces according to the values of etherStatsOversizePkts, as defined in [RFC2819], then the 'etherStatsOversizePkts' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherStatsOverbesPKTS的值对接口进行排序，则将设置“EtherStatsOverbesPKTS”位。
If the agent can perform sorting of interfaces according to the values of etherStatsFragments, as defined in [RFC2819], then the 'etherStatsFragments' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsFragments值对接口进行排序，则将设置“etherStatsFragments”位。
If the agent can perform sorting of interfaces according to the values of etherStatsJabbers, as defined in [RFC2819], then the 'etherStatsJabbers' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsJabbers值对接口进行排序，则将设置“etherStatsJabbers”位。
If the agent can perform sorting of interfaces according to the values of etherStatsCollisions, as defined in [RFC2819], then the 'etherStatsCollisions' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsCollisions值对接口进行排序，则将设置“etherStatsCollisions”位。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts64Octets, as defined in [RFC2819], then the 'etherStatsPkts64Octets' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsPkts64Octets值对接口进行排序，则将设置“etherStatsPkts64Octets”位。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts65to127Octets, as defined in [RFC2819], then the 'etherStatsPkts65to127Octets' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherStatsPKTS65到127八位字节的值对接口进行排序，则将设置“EtherStatsPKTS65到127八位字节”。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts128to255Octets, as defined in [RFC2819], then the 'etherStatsPkts128to255Octets' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsPkts128to255Octets值对接口进行排序，则将设置“etherStatsPkts128to255Octets”位。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts256to511Octets, as defined in [RFC2819], then the 'etherStatsPkts256to511Octets' bit will be set.
如果代理可以根据[RFC2819]中定义的etherStatsPkts256to511Octets值对接口进行排序，则将设置“etherStatsPkts256to511Octets”位。
If the agent can perform sorting of interfaces according to the values of etherStatsPkts512to1023Octets, as defined in [RFC2819], then the 'etherStatsPkts512to1023Octets' bit will be set.
如果代理可以根据[RFC2819]中定义的EtherStatsPKTS512to1023八位字节的值对接口进行排序，则将设置“EtherStatsPKTS512to1023八位字节”。
If the agent can perform sorting of interfaces according to the
如果代理可以根据
values of etherStatsPkts1024to1518Octets, as defined in [RFC2819], then the 'etherStatsPkts1024to1518Octets' bit will be set.
如[RFC2819]中定义的EtherstStatsPKTS1024to1518Octets的值，则将设置“EtherstStatsPKTS1024to1518Octets”位。
If the agent can perform sorting of interfaces according to the values of dot1dTpPortInFrames, as defined in [RFC1493], then the 'dot1dTpPortInFrames' bit will be set.
如果代理可以根据[RFC1493]中定义的dot1dTpPortInFrames的值对接口进行排序，则将设置“dot1dTpPortInFrames”位。
If the agent can perform sorting of interfaces according to the values of dot1dTpPortOutFrames, as defined in [RFC1493], then the 'dot1dTpPortOutFrames' bit will be set.
如果代理可以根据[RFC1493]中定义的dot1dTpPortOutFrames的值对接口进行排序，则将设置“dot1dTpPortOutFrames”位。
If the agent can perform sorting of interfaces according to the values of dot1dTpPortInDiscards, as defined in [RFC1493], then the 'dot1dTpPortInDiscards' bit will be set."
如果代理可以根据[RFC1493]中定义的dot1dTpPortInDiscards值对接口进行排序，则将设置“dot1dTpPortInDiscards”位。”
::= { interfaceTopNObjects 1 }
::= { interfaceTopNObjects 1 }
interfaceTopNControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF InterfaceTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of control records for reports on the top `N'
interfaces for the value or rate of a selected object.
The number of entries depends on the configuration of the agent.
The maximum number of entries is implementation
dependent."
::= { interfaceTopNObjects 2 }
interfaceTopNControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF InterfaceTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of control records for reports on the top `N'
interfaces for the value or rate of a selected object.
The number of entries depends on the configuration of the agent.
The maximum number of entries is implementation
dependent."
::= { interfaceTopNObjects 2 }
interfaceTopNControlEntry OBJECT-TYPE
SYNTAX InterfaceTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that control the creation of a
report of the top N ports according to several metrics."
INDEX { interfaceTopNControlIndex }
::= { interfaceTopNControlTable 1 }
interfaceTopNControlEntry OBJECT-TYPE
SYNTAX InterfaceTopNControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that control the creation of a
report of the top N ports according to several metrics."
INDEX { interfaceTopNControlIndex }
::= { interfaceTopNControlTable 1 }
InterfaceTopNControlEntry ::= SEQUENCE {
interfaceTopNControlIndex
Integer32,
interfaceTopNObjectVariable
INTEGER,
InterfaceTopNControlEntry ::= SEQUENCE {
interfaceTopNControlIndex
Integer32,
interfaceTopNObjectVariable
INTEGER,
interfaceTopNObjectSampleType INTEGER, interfaceTopNNormalizationReq TruthValue, interfaceTopNNormalizationFactor Integer32, interfaceTopNTimeRemaining Integer32, interfaceTopNDuration Integer32, interfaceTopNRequestedSize Integer32, interfaceTopNGrantedSize Integer32, interfaceTopNStartTime TimeStamp, interfaceTopNOwner OwnerString, interfaceTopNLastCompletionTime TimeStamp, interfaceTopNRowStatus RowStatus }
interfaceTopNObjectSampleType整数、interfaceTopNNormalizationReq TruthValue、interfaceTopNNormalizationFactor整数32、InterfaceTopnTime剩余整数32、interfaceTopNDuration整数32、interfaceTopNRequestedSize整数32、interfaceTopNGrantedSize整数32、interfaceTopNStartTime时间戳、interfaceTopNOwner OwnerString、，InterfaceTopLastCompletionTime时间戳，InterfaceTopRowStatus RowStatus}
interfaceTopNControlIndex OBJECT-TYPE
SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
interfaceTopNControl table. Each such entry defines
one top N report prepared for a probe."
::= { interfaceTopNControlEntry 1 }
interfaceTopNControlIndex OBJECT-TYPE
SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that uniquely identifies an entry in the
interfaceTopNControl table. Each such entry defines
one top N report prepared for a probe."
::= { interfaceTopNControlEntry 1 }
interfaceTopNObjectVariable OBJECT-TYPE SYNTAX INTEGER { ifInOctets(0), ifInUcastPkts(1), ifInNUcastPkts(2), ifInDiscards(3), ifInErrors(4), ifInUnknownProtos(5), ifOutOctets(6), ifOutUcastPkts(7), ifOutNUcastPkts(8), ifOutDiscards(9), ifOutErrors(10),
interfaceTopNObjectVariable对象类型语法整数{ifInOctets（0）、ifInUcastPkts（1）、ifInUcastPkts（2）、ifInDiscards（3）、ifInErrors（4）、ifInUnknownProtos（5）、IFOUTPOctets（6）、IFOUTUUCASTPKTS（7）、ifOutNUcastPkts（8）、IFOUTDARDS（9）、ifOutErrors（10），
ifInMulticastPkts(11), ifInBroadcastPkts(12), ifOutMulticastPkts(13), ifOutBroadcastPkts(14), ifHCInOctets(15), ifHCInUcastPkts(16), ifHCInMulticastPkts(17), ifHCInBroadcastPkts(18), ifHCOutOctets(19), ifHCOutUcastPkts(20), ifHCOutMulticastPkts(21), ifHCOutBroadcastPkts(22), dot3StatsAlignmentErrors(23), dot3StatsFCSErrors(24), dot3StatsSingleCollisionFrames(25), dot3StatsMultipleCollisionFrames(26), dot3StatsSQETestErrors(27), dot3StatsDeferredTransmissions(28), dot3StatsLateCollisions(29), dot3StatsExcessiveCollisions(30), dot3StatsInternalMacTxErrors(31), dot3StatsCarrierSenseErrors(32), dot3StatsFrameTooLongs(33), dot3StatsInternalMacRxErrors(34), dot3StatsSymbolErrors(35), dot3InPauseFrames(36), dot3OutPauseFrames(37), dot5StatsLineErrors(38), dot5StatsBurstErrors(39), dot5StatsACErrors(40), dot5StatsAbortTransErrors(41), dot5StatsInternalErrors(42), dot5StatsLostFrameErrors(43), dot5StatsReceiveCongestions(44), dot5StatsFrameCopiedErrors(45), dot5StatsTokenErrors(46), dot5StatsSoftErrors(47), dot5StatsHardErrors(48), dot5StatsSignalLoss(49), dot5StatsTransmitBeacons(50), dot5StatsRecoverys(51), dot5StatsLobeWires(52), dot5StatsRemoves(53), dot5StatsSingles(54), dot5StatsFreqErrors(55), etherStatsDropEvents(56), etherStatsOctets(57), etherStatsPkts(58),
ifInMulticastPkts（11）、ifInBroadcastPkts（12）、ifOutMulticastPkts（13）、ifOutBroadcastPkts（14）、ifHCInOctets（15）、IFhcinCastPKTs（16）、ifHCInMulticastPkts（17）、ifHCInBroadcastPkts（18）、ifHCOutOctets（19）、ifHCOutUcastPkts（20）、ifHCOutMulticastPkts（21）、ifHCOutBroadcastPkts（22）、Dot3StatementSalignmentErrors（23）、Dot3StatsfSerrors（24），dot3StatsSingleCollisionFrames（25）、dot3StatsMultipleCollisionFrames（26）、Dot3StatsQetesterrors（27）、Dot3StatsFerredTransmission（28）、Dot3StatsSlateCollisions（29）、Dot3StatsAccessiveCollisions（30）、Dot3StatsInternalActor（31）、Dot3StatsCrariersensErrors（32）、dot3StatsFrameTooLongs（33）、Dot3StatsInternalMacErrors（34），DOT3StatssSymbolErrors（35）、dot3InPauseFrames（36）、DOT3OutPauseFrameErrors（37）、dot5StatsLineErrors（38）、dot5StatsBurstErrors（39）、DOT5StatsAsserErrors（40）、DOT5StatsBortTransformErrors（41）、dot5StatsInternalErrors（42）、dot5StatsLostFrameErrors（43）、DOT5StatsReceiveContractures（44）、dot5StatsFrameCopiedErrors（45）、dot5StatsTokenErrors（46）、dot5StatsSoftErrors（47）、dot5StatsHardErrors（48）、dot5StatsSignalLoss（49）、dot5StatsTransmitBeacons（50）、Dot5StatsRecovery（51）、dot5StatsLobeWires（52）、dot5StatsRemoves（53）、dot5StatsSingles（54）、dot5StatsFreqErrors（55）、etherStatsDropEvents（56）、etherStatsOctets（57）、etherStatsPkts（58），
etherStatsBroadcastPkts(59), etherStatsMulticastPkts(60), etherStatsCRCAlignErrors(61), etherStatsUndersizePkts(62), etherStatsOversizePkts(63), etherStatsFragments(64), etherStatsJabbers(65), etherStatsCollisions(66), etherStatsPkts64Octets(67), etherStatsPkts65to127Octets(68), etherStatsPkts128to255Octets(69), etherStatsPkts256to511Octets(70), etherStatsPkts512to1023Octets(71), etherStatsPkts1024to1518Octets(72), dot1dTpPortInFrames(73), dot1dTpPortOutFrames(74), dot1dTpPortInDiscards(75) } MAX-ACCESS read-create STATUS current DESCRIPTION "The particular variable to be sampled.
EtherstStatsBroadcastPKTs（59）、EtherstStatsMulticastPKTs（60）、EtherstStatsRCalignErrors（61）、EtherstStatsUnderSizePkts（62）、EtherstStatsOversePKTs（63）、EtherstStatsFragments（64）、EtherstStatsJabbers（65）、EtherstStatsCollisions（66）、EtherstStatsPKTs64个八位字节（67）、EtherstStatsPKTs65to127个八位字节（68）、EtherstStatsPKTs128to255个八位字节（69）、EtherstStatsPKTs256to511个八位字节（70），EtherstStatsPKTS512To1023八位字节（71）、EtherstStatsPKTS1024To1518八位字节（72）、dot1dTpPortInFrames（73）、dot1dTpPortOutFrames（74）、dot1dTpPortInDiscards（75）}MAX-ACCESS读取创建状态当前描述“要采样的特定变量”。
Values between 0 and 22, point to MIB objects defined in IF-MIB [RFC2863].
值介于0和22之间，指向IF-MIB[RFC2863]中定义的MIB对象。
Values between 23 and 37, point to MIB objects defined in EtherLike-MIB [RFC2665].
值介于23和37之间，指向类以太MIB[RFC2665]中定义的MIB对象。
Values between 38 and 55, point to MIB objects defined in TOKENRING-MIB [RFC1748].
值介于38和55之间，指向TOKENRING-MIB[RFC1748]中定义的MIB对象。
Values between 56 and 72, point to MIB objects defined in RMON-MIB [RFC2819].
值介于56和72之间，指向RMON-MIB[RFC2819]中定义的MIB对象。
Values between 73 and 75, point to MIB objects defined in BRIDGE-MIB [RFC1493].
值介于73和75之间，指向BRIDGE-MIB[RFC1493]中定义的MIB对象。
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 TopN mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe.
由于SNMP访问控制完全根据MIB视图的内容进行阐述，因此不存在可以限制此对象的值以仅识别特定MIB视图中存在的那些对象的访问控制机制。由于没有可接受的方式限制通过TopN机制获得的读取访问，因此探测器必须仅在对探测器上的所有对象具有读取访问权限的视图中授予对此对象的写入访问权限。
During a set operation, if the supplied variable name is not available in the selected MIB view, or does not conform the other conditions mentioned above, a badValue error must be returned.
在set操作期间，如果提供的变量名在所选MIB视图中不可用，或者不符合上述其他条件，则必须返回badValue错误。
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 2 }
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 2 }
interfaceTopNObjectSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2),
bandwidthPercentage(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable for storage in
the interfaceTopNTable.
interfaceTopNObjectSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2),
bandwidthPercentage(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable for storage in
the interfaceTopNTable.
If the value of this object is absoluteValue(1), the value of the selected variable will be copied directly into the topNValue.
如果此对象的值为absoluteValue（1），则所选变量的值将直接复制到topNValue中。
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 will be stored in topNValue.
如果此对象的值为deltaValue（2），则将从当前值中减去上次采样时选定变量的值，差值将存储在topNValue中。
If the value of this object is bandwidthPercentage(3), the agent records the total number of octets sent over an interval divided by the total number of octets that represent '100% bandwidth' for that interface. This ratio is multiplied by 1000 to retain a 3 digit integer (0..1000) in units of 'tenth of one percent'. This type of computation is accurate for the octet counters. The usage of this option with respect to packets or error counters is not recommended.
如果此对象的值为bandwidthPercentage（3），则代理会记录在某个时间间隔内发送的八位字节总数除以表示该接口“100%带宽”的八位字节总数。此比率乘以1000，以“百分之十分之一”为单位保留一个3位整数（0..1000）。这种类型的计算对于八位字节计数器是精确的。不建议对数据包或错误计数器使用此选项。
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 3 }
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 3 }
interfaceTopNNormalizationReq OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates whether normalization is required in the
interfaceTopNNormalizationReq对象类型语法TruthValue MAX-ACCESS读取创建状态当前描述“此对象指示在
computation of the selected value.
计算选定值。
If the value of this object is 'true', the value of the selected variable will be multiplied by a factor equal to the interfaceTopNNormalizationFactor divided by the value of effective speed of the interface
如果该对象的值为“真”，则所选变量的值将乘以等于interfaceTopNNormalizationFactor除以界面有效速度值的系数
If the value of this object is 'false', the value of the selected variable will be taken 'as is' in the TopN computation.
如果此对象的值为“false”，则所选变量的值将在TopN计算中采用“原样”。
If the value of the object interfaceTopNSampleType is bandwidthPercentage(3), the object interfaceTopNNormalizationReq cannot take the value 'true'.
如果对象interfaceTopNSampleType的值为带宽百分比（3），则对象interfaceTopNNormalizationReq不能采用值“true”。
The value of this object MUST be false if the effective speed of the interface sub-layer as determined from ifSpeed is zero. This conforms to the ifSpeed definition in [RFC2863]for a sub-layer that has no concept of bandwidth.
如果根据ifSpeed确定的界面子层的有效速度为零，则此对象的值必须为false。这符合[RFC2863]中关于没有带宽概念的子层的ifSpeed定义。
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 4 }
This object may not be modified if the associated
interfaceTopNControlStatus object is equal to active(1)."
::= { interfaceTopNControlEntry 4 }
interfaceTopNNormalizationFactor OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The value used for normalization if interfaceTopNNormalizationReq has the value 'true'.
interfaceTopNNormalizationFactor对象类型语法整数32（1..2147483647）MAX-ACCESS读取创建状态当前描述“如果interfaceTopNNormalizationReq的值为“true”，则用于规范化的值。
Example: The following set of values is applied to a device with multiple Ethernet interfaces running at 10 Mbps, 100 Mbps, and 1 Gbps. interfaceTopNObjectVariable = 'ifInOctets' interfaceTopNObjectSampleType = 'deltaValue' interfaceTopNNormalizationReq = 'true' interfaceTopNNormalizationFactor = 1000000000 Applying this set of values will result in the sampled delta values to be multiplied by 100 for the 10 Mbps interfaces, and by 10 for the 100 Mbps interfaces, while the sample values for the 1 Gbps interface are left unchanged. The effective speed of the interface is taken from the value of ifSpeed for each interface, if ifSpeed is less than 4,294,967,295, or from ifHighSpeed multiplied by 1,000,000 otherwise.
示例：以下一组值应用于具有以10 Mbps、100 Mbps和1 Gbps速度运行的多个以太网接口的设备。interfaceTopNObjectVariable='ifInOctets'interfaceTopNObjectSampleType='deltaValue'interfaceTopNNormalizationReq='true'interfaceTopNNormalizationFactor=100000000应用这组值将导致10 Mbps接口的采样增量值乘以100，100 Mbps接口的采样增量值乘以10，而1 Gbps接口的采样值保持不变。如果ifSpeed小于4294967295，则接口的有效速度取自每个接口的ifSpeed值，否则取自ifHighSpeed乘以1000000。
At row creation the agent SHOULD set the value of this object to
在创建行时，代理应将此对象的值设置为
the effective speed of the interface."
::= { interfaceTopNControlEntry 5 }
the effective speed of the interface."
::= { interfaceTopNControlEntry 5 }
interfaceTopNTimeRemaining OBJECT-TYPE SYNTAX Integer32 (0..2147483647) 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 interfaceTopNDuration object.
InterfaceTopnPTime剩余对象类型语法整数32（0..2147483647）MAX-ACCESS读取创建状态当前说明“当前正在收集的报告中剩余的秒数。当管理工作站修改此对象时，将启动一个新集合，可能会中止当前正在运行的报告。新值用作此报告的请求持续时间，该报告将加载到关联的interfaceTopNDuration对象中。
When this object is set to a non-zero value, any associated interfaceTopNEntries shall be made inaccessible by the agent. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated interfaceTopNEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the interfaceTopNTable. Thus, the interfaceTopN table needs to be created only at the end of the collection interval.
当该对象设置为非零值时，代理应使任何相关的interfaceTopNEntries不可访问。虽然此对象的值不是零，但它每秒递减一次，直到达到零。在这段时间内，所有相关的InterfaceTopnPEntry都将无法访问。当此对象递减为零时，可以在InterfaceTopnPTable中访问报告。因此，只需在收集间隔结束时创建interfaceTopN表。
If the value of this object is set to zero
while the associated report is running, the
running report is aborted and no associated
interfaceTopNEntries are created."
DEFVAL { 0 }
::= { interfaceTopNControlEntry 6 }
If the value of this object is set to zero
while the associated report is running, the
running report is aborted and no associated
interfaceTopNEntries are created."
DEFVAL { 0 }
::= { interfaceTopNControlEntry 6 }
interfaceTopNDuration OBJECT-TYPE SYNTAX Integer32 (0..2147483647) 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.
interfaceTopNDuration对象类型语法整数32（0..2147483647）MAX-ACCESS只读状态当前描述“此报告在上次采样间隔内采集的秒数，或者如果当前正在采集此报告，则在此采样间隔内采集此报告的秒数。
When the associated interfaceTopNTimeRemaining
当关联的InterfaceTopnTime剩余时
object is set, this object shall be set by the agent to the same value and shall not be modified until the next time the interfaceTopNTimeRemaining is set.
对象设置后，代理应将此对象设置为相同的值，并且在下次设置interfaceTopNTimeRemaining之前不得修改。
This value shall be zero if no reports have been
requested for this interfaceTopNControlEntry."
::= { interfaceTopNControlEntry 7 }
This value shall be zero if no reports have been
requested for this interfaceTopNControlEntry."
::= { interfaceTopNControlEntry 7 }
interfaceTopNRequestedSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of interfaces requested for the Top N Table.
InterfaceTopnPRequestedSize对象类型语法整数32 MAX-ACCESS read create STATUS current DESCRIPTION“为Top N表请求的最大接口数。
When this object is created or modified, the
agent should set interfaceTopNGrantedSize as close
to this object as is possible for the particular
implementation and available resources."
DEFVAL { 10 }
::= { interfaceTopNControlEntry 8 }
When this object is created or modified, the
agent should set interfaceTopNGrantedSize as close
to this object as is possible for the particular
implementation and available resources."
DEFVAL { 10 }
::= { interfaceTopNControlEntry 8 }
interfaceTopNGrantedSize OBJECT-TYPE SYNTAX Integer32 (0.. 2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of interfaces in the top N table.
InterfaceTopnPrantedSize对象类型语法整数32（0..2147483647）MAX-ACCESS只读状态当前说明“top N表中的最大接口数。
When the associated interfaceTopNRequestedSize object is
created or modified, the agent should set this object as
closely to the requested value as is possible for the
particular implementation and available resources. The
agent must not lower this value except as a result of a
set to the associated interfaceTopNRequestedSize object."
::= { interfaceTopNControlEntry 9 }
When the associated interfaceTopNRequestedSize object is
created or modified, the agent should set this object as
closely to the requested value as is possible for the
particular implementation and available resources. The
agent must not lower this value except as a result of a
set to the associated interfaceTopNRequestedSize object."
::= { interfaceTopNControlEntry 9 }
interfaceTopNStartTime OBJECT-TYPE SYNTAX TimeStamp 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 interfaceTopNTimeRemaining object was
interfaceTopNStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“上次启动此top N报告时的系统正常运行时间值。换句话说，这是关联InterfaceTopnStime剩余对象的运行时间
modified to start the requested report.
已修改以启动请求的报告。
If the report has not yet been started, the value
of this object is zero."
::= { interfaceTopNControlEntry 10 }
If the report has not yet been started, the value
of this object is zero."
::= { interfaceTopNControlEntry 10 }
interfaceTopNOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is
using the resources assigned to it."
::= { interfaceTopNControlEntry 11 }
interfaceTopNOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is
using the resources assigned to it."
::= { interfaceTopNControlEntry 11 }
interfaceTopNLastCompletionTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this top N report was
last completed. If no report was yet completed, the value
of this object is zero."
::= { interfaceTopNControlEntry 12 }
interfaceTopNLastCompletionTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this top N report was
last completed. If no report was yet completed, the value
of this object is zero."
::= { interfaceTopNControlEntry 12 }
interfaceTopNRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row.
interfaceTopNRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述“此行的状态。
If the value of this object is not equal to
active(1), all associated entries in the
interfaceTopNTable shall be deleted by the
agent."
::= { interfaceTopNControlEntry 13 }
If the value of this object is not equal to
active(1), all associated entries in the
interfaceTopNTable shall be deleted by the
agent."
::= { interfaceTopNControlEntry 13 }
-- Interface Top "N" reports
--界面前“N”个报告
interfaceTopNTable OBJECT-TYPE SYNTAX SEQUENCE OF InterfaceTopNEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of reports for the top `N' ports based on
InterfaceTopTable对象类型InterfaceTopNEntry MAX-ACCESS的语法序列不可访问状态当前描述“基于
setting of associated control table entries. The maximum number of entries depends on the number of entries in table interfaceTopNControlTable and the value of object interfaceTopNGrantedSize for each entry.
设置关联的控制表条目。最大条目数取决于表interfaceTopNControlTable中的条目数以及每个条目的对象InterfaceTopnPGrantedSize的值。
For each entry in the interfaceTopNControlTable,
interfaces with the highest value of
interfaceTopNValue shall be placed in this table
in decreasing order of that rate until there is
no more room or until there are no more ports."
::= { interfaceTopNObjects 3 }
For each entry in the interfaceTopNControlTable,
interfaces with the highest value of
interfaceTopNValue shall be placed in this table
in decreasing order of that rate until there is
no more room or until there are no more ports."
::= { interfaceTopNObjects 3 }
interfaceTopNEntry OBJECT-TYPE
SYNTAX InterfaceTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of statistics for an interface that is
part of a top N report."
INDEX { interfaceTopNControlIndex,
interfaceTopNIndex }
::= { interfaceTopNTable 1 }
interfaceTopNEntry OBJECT-TYPE
SYNTAX InterfaceTopNEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of statistics for an interface that is
part of a top N report."
INDEX { interfaceTopNControlIndex,
interfaceTopNIndex }
::= { interfaceTopNTable 1 }
InterfaceTopNEntry ::= SEQUENCE {
interfaceTopNIndex
Integer32,
interfaceTopNDataSourceIndex
Integer32,
interfaceTopNValue
Gauge32,
interfaceTopNValue64
CounterBasedGauge64
}
InterfaceTopNEntry ::= SEQUENCE {
interfaceTopNIndex
Integer32,
interfaceTopNDataSourceIndex
Integer32,
interfaceTopNValue
Gauge32,
interfaceTopNValue64
CounterBasedGauge64
}
interfaceTopNIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index that uniquely identifies an entry in the interfaceTopN table among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Increasing values of interfaceTopNIndex shall be assigned to entries with decreasing values of interfaceTopNValue or interfaceTopNValue64, whichever applies, until index N is assigned to the entry with the
interfaceTopNIndex对象类型语法整数32（1..65535）MAX-ACCESS不可访问状态当前说明“在同一报表中唯一标识interfaceTopN表项的索引。此索引介于1和N之间，其中N是此报告中的条目数。应将interfaceTopNIndex的递增值分配给interfaceTopNValue或interfaceTopNValue64（以适用者为准）值递减的条目，直到将索引N分配给具有
lowest value of interfaceTopNValue / interfaceTopNValue64 or there are no more interfaceTopNEntries.
interfaceTopNValue/interfaceTopNValue64的最低值或没有更多interfaceTopNEntries。
No ports are included in a report where their
value of interfaceTopNValue would be zero."
::= { interfaceTopNEntry 1 }
No ports are included in a report where their
value of interfaceTopNValue would be zero."
::= { interfaceTopNEntry 1 }
interfaceTopNDataSourceIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the index corresponding to the dataSource for this entry.
InterfaceTopnPDataSourceIndex对象类型语法整数32（1..2147483647）MAX-ACCESS只读状态当前描述“此对象标识与此条目的数据源对应的索引。
For sorted values of variables belonging to the IF-MIB, EtherLike-MIB or TOKENRING-MIB, this value equals the ifIndex of the interface.
对于属于IF-MIB、EtherLike MIB或TOKENRING-MIB的变量的排序值，该值等于接口的ifIndex。
For sorted values of variables belonging to the RMON-MIB, this value equals the interface corresponding to the data source, pointed to by the value of etherStatsDataSource.
对于属于RMON-MIB的变量的排序值，该值等于数据源对应的接口，由EtherstStatsDataSource的值指向。
For sorted values of variables belonging to the
BRIDGE-MIB, this value equals the interface corresponding
to the bridge port, pointed to by the value
of dot1dBasePortIfIndex."
::= { interfaceTopNEntry 2 }
For sorted values of variables belonging to the
BRIDGE-MIB, this value equals the interface corresponding
to the bridge port, pointed to by the value
of dot1dBasePortIfIndex."
::= { interfaceTopNEntry 2 }
interfaceTopNValue OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value at the end of the sampling interval, or the amount of change in the selected variable during this sampling interval for the identified interface. The selected variable is that interfaces's instance of the object selected by interfaceTopNObjectVariable. This value may be normalized if interfaceTopNNormalization required equals 'true'. This value of this object will be computed for all cases when interfaceTopNObjectVariable points to a 32-bit counter or Gauge or when interfaceTopNObjectSampleType equals bandwidthPercentage(3), and will be zero for all other cases."
interfaceTopNValue对象类型语法量表32 MAX-ACCESS只读状态当前说明“采样间隔结束时的值，或已识别接口在此采样间隔期间所选变量的变化量。所选变量是interfaceTopNObjectVariable所选对象的接口实例。如果interfaceTopNNormalization required等于“true”，则可以对该值进行规范化。当InterfaceTopnPObjectVariable指向32位计数器或仪表或InterfaceTopnPObjectSampleType等于带宽百分比（3）时，将针对所有情况计算此对象的此值，对于所有其他情况，此值将为零。”
::= { interfaceTopNEntry 3 }
::= { interfaceTopNEntry 3 }
interfaceTopNValue64 OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value at the end of the sampling interval, or
the amount of change in the selected variable
during this sampling interval for the identified
interface. The selected variable is that interfaces's
instance of the object selected by
interfaceTopNObjectVariable. This value may be normalized
if interfaceTopNNormalization required equals 'true'.
This value of this object will be computed for all
cases when interfaceTopNObjectVariable points to
a 64-bit counter, and will be zero for all other cases."
::= { interfaceTopNEntry 4 }
interfaceTopNValue64 OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value at the end of the sampling interval, or
the amount of change in the selected variable
during this sampling interval for the identified
interface. The selected variable is that interfaces's
instance of the object selected by
interfaceTopNObjectVariable. This value may be normalized
if interfaceTopNNormalization required equals 'true'.
This value of this object will be computed for all
cases when interfaceTopNObjectVariable points to
a 64-bit counter, and will be zero for all other cases."
::= { interfaceTopNEntry 4 }
--
-- Notifications Section
-- (none defined)
--
--
-- Notifications Section
-- (none defined)
--
-- -- Conformance Section --
----合规部分--
interfaceTopNCompliances OBJECT IDENTIFIER ::=
{interfaceTopNConformance 1 }
interfaceTopNGroups OBJECT IDENTIFIER ::=
{interfaceTopNConformance 2 }
interfaceTopNCompliances OBJECT IDENTIFIER ::=
{interfaceTopNConformance 1 }
interfaceTopNGroups OBJECT IDENTIFIER ::=
{interfaceTopNConformance 2 }
interfaceTopNCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the
InterfaceTopN MIB."
MODULE -- this module
MANDATORY-GROUPS { interfaceTopNGroup }
::= { interfaceTopNCompliances 1 }
interfaceTopNCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the
InterfaceTopN MIB."
MODULE -- this module
MANDATORY-GROUPS { interfaceTopNGroup }
::= { interfaceTopNCompliances 1 }
interfaceTopNGroup OBJECT-GROUP OBJECTS { interfaceTopNCaps, interfaceTopNObjectVariable, interfaceTopNObjectSampleType,
interfaceTopNGroup对象组对象{interfaceTopNCaps，interfaceTopNObjectVariable，interfaceTopNObjectSampleType，
interfaceTopNNormalizationReq,
interfaceTopNNormalizationFactor,
interfaceTopNTimeRemaining,
interfaceTopNDuration,
interfaceTopNRequestedSize,
interfaceTopNGrantedSize,
interfaceTopNStartTime,
interfaceTopNOwner,
interfaceTopNLastCompletionTime,
interfaceTopNRowStatus,
interfaceTopNDataSourceIndex,
interfaceTopNValue,
interfaceTopNValue64
}
STATUS current
DESCRIPTION
"A collection of objects providing interfaceTopN data for
a multiple interfaces device."
::= { interfaceTopNGroups 1 }
interfaceTopNNormalizationReq,
interfaceTopNNormalizationFactor,
interfaceTopNTimeRemaining,
interfaceTopNDuration,
interfaceTopNRequestedSize,
interfaceTopNGrantedSize,
interfaceTopNStartTime,
interfaceTopNOwner,
interfaceTopNLastCompletionTime,
interfaceTopNRowStatus,
interfaceTopNDataSourceIndex,
interfaceTopNValue,
interfaceTopNValue64
}
STATUS current
DESCRIPTION
"A collection of objects providing interfaceTopN data for
a multiple interfaces device."
::= { interfaceTopNGroups 1 }
END
终止
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC2571]Harrington，D.，Presohn，R.，和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC1212]Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[RFC1215]M.Rose，“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.，和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[RFC1901]Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC1906]Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2572]Case，J.，Harrington D.，Presohn R.，和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2574]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1905]Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[RFC2573]Levi，D.，Meyer，P.，和B.Stewart，“SNMPv3应用”，RFC 2573，1999年4月。
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2575]Wijnen，B.，Presuhn，R.，和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1999年4月。
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[RFC2570]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2819] Waldbusser, S., "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000.
[RFC2819]Waldbusser，S.，“远程网络监控管理信息库”，STD 59，RFC 2819，2000年5月。
[RFC2613] Waterman, R., Lahaye, B., Romascanu, D., and S. Waldbusser, "Remote Network Monitoring MIB Extensions for Switched Networks, Version 1.0", RFC 2613, June 1999.
[RFC2613]Waterman，R.，Lahaye，B.，Romascanu，D.，和S.Waldbusser，“交换网络的远程网络监控MIB扩展，版本1.0”，RFC 2613，1999年6月。
[RFC1213] 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.
[RFC1213]McCloghrie，K.和M.Rose，编辑，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和Kastenholtz，F.，“接口组MIB”，RFC 28632000年6月。
[RFC2982] Kavasseri, R., Stewart B., "Distributed Management Expression MIB", RFC 2982, October 2000
[RFC2982]Kavasseri，R.，Stewart B.，“分布式管理表达式MIB”，RFC 2982，2000年10月
[RFC2856] Bierman, A., McCloghrie, K., and Presuhn R., "Textual Conventions for Additional High Capacity Data Types", RFC 2856, June 2000.
[RFC2856]Bierman，A.，McCloghrie，K.，和Presuhn R.，“附加高容量数据类型的文本约定”，RFC 28562000年6月。
[RFC2665] Flick, J., and Johnson, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 2665, August 1999.
[RFC2665]Flick，J.和Johnson，J.，“类似以太网接口类型的托管对象定义”，RFC 2665，1999年8月。
[RFC1748] McCloghrie, K., and Decker E., "IEEE802.5 MIB Using SMIv2", RFC 1748, December 1994.
[RFC1748]McCloghrie，K.和Decker E.，“使用SMIv2的IEEE802.5 MIB”，RFC 17481994年12月。
[RFC1493] E. Decker, P. Langille, A. Rijsinghani, and McCloghrie, K., "Definition of Managed Objects for Bridges", RFC 1493, July 1993.
[RFC1493]E.Decker，P.Langille，A.Rijsinghani和McCloghrie，K.，“桥梁管理对象的定义”，RFC 1493，1993年7月。
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执行董事。
There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
此MIB中定义了许多管理对象，它们的MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
There are a number of managed objects in this MIB that may contain sensitive information. These are:
此MIB中有许多托管对象可能包含敏感信息。这些是：
interfaceTopNDataSourceIndex interfaceTopNValue
interfaceTopNDataSourceIndex interfaceTopNValue
It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment.
因此，在通过SNMP通过网络发送这些对象时，控制甚至访问这些对象，甚至可能加密这些对象的值，这一点非常重要。并非所有版本的SNMP都为这种安全环境提供功能。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is RECOMMENDED that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model [RFC2274] and the View-based Access Control Model [RFC2275] is RECOMMENDED.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型[RFC2274]和基于视图的访问控制模型[RFC2275]。
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实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
Dan Romascanu Avaya Inc. Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel
Dan Romascanu Avaya Inc.以色列特拉维夫3号楼Atidim技术园，61131
Phone: +972-3-645-8414
EMail: dromasca@avaya.com
Phone: +972-3-645-8414
EMail: dromasca@avaya.com
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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编辑功能的资金目前由互联网协会提供。