Network Working Group R. Waterman
Request for Comments: 2613 Allot Networks Inc.
Category: Standards Track B. Lahaye
Xylan Corp.
D. Romascanu
Lucent Technologies
S. Waldbusser
INS
June 1999
Network Working Group R. Waterman
Request for Comments: 2613 Allot Networks Inc.
Category: Standards Track B. Lahaye
Xylan Corp.
D. Romascanu
Lucent Technologies
S. Waldbusser
INS
June 1999
Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0
用于交换网络的远程网络监控MIB扩展版本1.0
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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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 in switched networks environments.
此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于在交换网络环境中管理远程网络监控设备的对象。
Table of Contents
目录
1 The Network Management Framework 2 2 Overview 3 2.1 Remote Network Management Goals 3 2.2 Switched Networks Monitoring 5 2.3 Mechanisms for Monitoring Switched Networks 5 2.3.1 DataSource Objects 6 2.3.2 Copy Port 7 2.3.3 VLAN Monitoring 7 2.4 Relationship to Other MIBs 8 2.4.1 The RMON and RMON 2 MIBs 8 2.4.2 The Interfaces Group MIB 8 2.4.3 The Entity MIB 8 2.4.4 The Bridge MIB 9
1网络管理框架2概述3 2.1远程网络管理目标3 2.2交换网络监控5 2.3监控交换网络的机制5 2.3.1数据源对象6 2.3.2复制端口7 2.3.3 VLAN监控7 2.4与其他MIB的关系8 2.4.1 RMON和RMON 2 MIB 8 2.4.2接口组MIB 8 2.4.3实体MIB 8 2.4.4桥MIB 9
2.5 Relationship with IEEE 802.1 Standards 9 3 SMON/RMON Groups 9 3.1 SMON ProbeCapabilities 9 3.2 smonVlanStats 10 3.3 smonPrioStats 10 3.4 dataSourceCaps 10 3.5 portCopyConfig 11 4 Control of Remote Network Monitoring Devices 12 5 Definitions 13 6 References 39 7 Intellectual Property 41 8 Security Considerations 41 9 Authors' Addresses 44 A Full Copyright Statement 44
2.5与IEEE 802.1标准的关系9 3 SMON/RMON组9 3.1 SMON可能性9 3.2 SMONLAN状态10 3.3 smonPrioStats 10 3.4数据源CAPS 10 3.5 portCopyConfig 11 4远程网络监控设备的控制12 5定义13 6参考文献39 7知识产权41 8安全注意事项41 9作者地址44 A版权声明全文44
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
- An overall architecture, described in RFC 2571 [1].
- RFC 2571[1]中描述的总体架构。
- 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].
- 为管理目的描述和命名对象和事件的机制。这种管理信息结构（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]中进行了描述。
- 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 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].
- 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2572[11]和RFC 2574[12]中进行了描述。
- 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].
- 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
- A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
- RFC 2573[14]中描述的一组基本应用程序和RFC 2575[15]中描述的基于视图的访问控制机制。
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 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在语义上必须是等效的，除非在翻译过程中忽略了对象或事件，因为SMIv2中的任何信息都不会转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [24].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[24]中所述进行解释。
This document continues the architecture created in the RMON MIB [17] by providing RMON analysis for switched networks (SMON).
本文档通过提供交换网络（SMON）的RMON分析，延续了RMON MIB[17]中创建的体系结构。
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 tolerate the complexity of manually manipulating objects to accomplish row creation. These functions should be handled by the management application.
本文档中定义的对象旨在作为RMON代理和RMON管理应用程序之间的接口，不用于人工直接操作。虽然有些用户可能会容忍直接显示其中一些对象，但很少有人会容忍手动操作对象以完成行创建的复杂性。这些功能应由管理应用程序处理。
o Offline Operation
o 脱机操作
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.
（尤其是在通过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
o 主动监测
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 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
o 问题检测和报告
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 Value Added Data
o 增值数据
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 Multiple Managers
o 多位经理
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 one management station, potentially using its resources concurrently.
恢复由于具有多个管理站的环境是常见的，因此远程网络监视设备必须处理多个管理站，可能同时使用其资源。
This document addresses issues related to applying "Remote Technology" to Switch Networks. Switches today differ from standard shared media protocols:
本文档介绍了将“远程技术”应用于交换机网络的相关问题。今天的交换机不同于标准的共享媒体协议：
1) Data is not, in general, broadcast. This MAY be caused by the switch architecture or by the connection-oriented nature of the data. This means, therefore, that monitoring non-broadcast traffic needs to be considered.
1) 一般来说，数据不是广播的。这可能是由交换机体系结构或数据面向连接的特性造成的。因此，这意味着需要考虑监控非广播流量。
2) Monitoring the multiple entry and exit points from a switching device requires a vast amount of resources - memory and CPU, and aggregation of the data in logical packets of information, determined by the application needs.
2) 监控一个交换设备的多个入口和出口需要大量的资源——内存和CPU，以及由应用程序需求决定的逻辑信息包中的数据聚合。
3) Switching incorporates logical segmentation such as Virtual LANs (VLANs).
3) 交换包含逻辑分段，如虚拟局域网（VLAN）。
4) Switching incorporates packet prioritization.
4) 交换结合了分组优先级。
5) Data across the switch fabric can be in the form of cells. Like RMON, SMON is only concerned with the monitoring of packets.
5) 交换结构中的数据可以是单元的形式。与RMON一样，SMON只关注数据包的监视。
Differences such as these make monitoring difficult. The current RMON and RMON 2 standards do not provide for things that are unique to switches or switched environments.
诸如此类的差异使监控变得困难。当前的RMON和RMON 2标准没有提供交换机或交换环境特有的功能。
In order to overcome the limitations of the existing standards, new monitoring mechanisms have been implemented by vendors of switching equipment. All these monitoring strategies are currently proprietary in nature.
为了克服现有标准的局限性，开关设备供应商实施了新的监测机制。所有这些监控策略目前都是专有的。
This document provides the framework to include different switching strategies and allow for monitoring operations consistent with the RMON framework. This MIB is limited to monitoring and control operations aimed at providing monitoring data for RMON probes.
本文件提供了包括不同交换策略的框架，并允许监控与RMON框架一致的操作。该MIB仅限于旨在为RMON探测器提供监控数据的监控操作。
The following mechanisms are used by SMON devices, for the purpose of monitoring switched networks.
SMON设备使用以下机制来监控交换网络。
The RMON MIB standard [17] defines data source objects which point to MIB-II interfaces, identified by instances of ifIndex objects.
RMON MIB标准[17]定义了指向MIB-II接口的数据源对象，这些接口由ifIndex对象的实例标识。
The SMON MIB extends this concept and allows for other types of objects to be defined as data sources for RMON and/or SMON data. Three forms of dataSources are described:
SMON MIB扩展了这一概念，并允许将其他类型的对象定义为RMON和/或SMON数据的数据源。描述了三种形式的数据源：
ifIndex.<I>
I指数。<I>
Traditional RMON dataSources. Called 'port-based' for ifType.<I> not equal to 'propVirtual(53)'. <I> is the ifIndex value (see [22]).
传统的RMON数据源。为ifType调用“基于端口”。<I>不等于“propVirtual（53）”<一> 是ifIndex值（见[22]）。
smonVlanDataSource.<V>
smonVlanDataSource.<V>
A dataSource of this form refers to a 'Packet-based VLAN' and is called a 'VLAN-based' dataSource. <V> is the VLAN ID as defined by the IEEE 802.1Q standard [19]. The value is between 1 and 4094 inclusive, and it represents an 802.1Q VLAN-ID with global scope within a given bridged domain, as defined by [19].
这种形式的数据源指“基于数据包的VLAN”，称为“基于VLAN的”数据源<五> 是IEEE 802.1Q标准定义的VLAN ID[19]。该值介于1和4094（含1和4094）之间，表示给定桥接域内具有全局作用域的802.1Q VLAN-ID，如[19]所定义。
entPhysicalEntry.<N>
entPhysicalEntry.<N>
A dataSource of this form refers to a physical entity within the agent and is called an 'entity-based' dataSource. <N> is the value of the entPhysicalIndex in the entPhysicalTable (see [18]).
这种形式的数据源是指代理中的物理实体，称为“基于实体的”数据源<N> 是entPhysicalTable中entPhysicalIndex的值（请参见[18]）。
In addition to these new dataSource types, SMON introduces a new group called dataSourceCapsTable to aid an NMS in discovering dataSource identity and attributes.
除了这些新的数据源类型之外，SMON还引入了一个名为dataSourceCapsTable的新组，以帮助NMS发现数据源标识和属性。
The extended data source mechanism supported by the SMON MIB allows for the use of external collection points, similar to the one defined and supported by the RMON and RMON 2 MIBs, as well as internal collection points (e.g. propVirtual ifTable entry, entPhysicalEntry). The latter reflects either data sources which MAY be the result of aggregation (e.g. switch-wide) or internal channels of physical entities, which have the capability of being monitored by an SMON probe.
SMON MIB支持的扩展数据源机制允许使用外部收集点（类似于RMON和RMON 2 MIB定义和支持的收集点）以及内部收集点（例如propVirtual ifTable entry、entPhysicalEntry）。后者反映的数据源可能是聚合（例如交换机范围）的结果，也可能是物理实体的内部通道，这些物理实体具有被SMON探测器监视的能力。
In order to make the switching devices support RMON statistics, many vendors have implemented a port copy feature, allowing traffic to be replicated from switch port to switch port. Several levels of configuration are possible:
为了使交换设备支持RMON统计，许多供应商已经实现了端口复制功能，允许将通信量从交换机端口复制到交换机端口。可以使用多个级别的配置：
1) 1 source port to 1 destination port 2) N source ports to 1 destination port 3) N source ports to M destination ports
1) 1个源端口到1个目标端口2）N个源端口到1个目标端口3）N个源端口到M个目标端口
The SMON standard presents a standard MIB interface which allows for the control of this function.
SMON标准提供了一个标准MIB接口，允许控制此功能。
Note that this function can apply to devices that have no other SMON or RMON functionality than copy port. The agent of such a device would support only the portCopyCaps and the portCopyConfig MIB groups, out of the whole SMON MIB. Switch vendors are encouraged to implement this subset of the SMON MIB, as it would allow for standard port copy configuration from the same NMS application that does RMON or SMON.
请注意，此功能可应用于除复制端口之外没有其他SMON或RMON功能的设备。这种设备的代理只支持整个SMON MIB中的portCopyCaps和portCopyConfig MIB组。鼓励交换机供应商实现SMON MIB的这一子集，因为它允许从与RMON或SMON相同的NMS应用程序进行标准端口复制配置。
Port copy may cause congestion problems on the SMON device. This situation is more likely occur when copying from a port of higher speed to a port of lower speed or copy from multiple port to a single port.
端口复制可能会导致SMON设备出现拥塞问题。当从高速端口复制到低速端口或从多个端口复制到单个端口时，更可能发生这种情况。
Particular implementations MAY chose to build protection mechanisms that would prevent creation of new port copy links when the capacity of the destination port is exceeded. The MIB allows for implementations to (if supported) instrument a destination drop count on port copy to provide NMS applications a sense of the quality of data presented at the destination port.
特定的实现可能会选择构建保护机制，以防止在超过目标端口的容量时创建新的端口副本链接。MIB允许实现（如果支持的话）在端口拷贝上检测目标丢弃计数，以便为NMS应用程序提供在目标端口上显示的数据质量。
VLAN monitoring can be accomplished by using a VLAN-based dataSource and/or by configuring smonVlanIdStats and/or smonPrioStats collections. These functions allow VLAN-ID or user priority distributions per dataSource. VLAN monitoring provides a high-level view of total VLAN usages and relative non-unicast traffic usage as well as a profile of VLAN priority as defined in the 3-bit user_priority field.
VLAN监控可以通过使用基于VLAN的数据源和/或通过配置SMonPlanidStats和/或smonPrioStats集合来完成。这些函数允许每个数据源分配VLAN-ID或用户优先级。VLAN监控提供了VLAN总使用量和相对非单播流量使用量的高级视图，以及3位用户_优先级字段中定义的VLAN优先级配置文件。
NOTE: priority statistics reflect what was parsed from the packet, not what priority, if any, was necessarily granted by the switch.
注意：优先级统计信息反映从数据包解析的内容，而不是交换机必须授予的优先级（如果有）。
The Remote Monitoring MIB (RMON) [17] provides several management functions that MAY be directly or indirectly applicable to switched networks.
远程监控MIB（RMON）[17]提供了几种可直接或间接适用于交换网络的管理功能。
The port copy mechanisms defined by the SMON MIB allow for the destination ports to become a data source for any RMON statistics. However, an NMS application SHOULD check whether it is in the device capability (portCopyCap) to filter errors from a source to a destination port and whether this capability is enabled, in order to provide a correct interpretation of the copied port traffic.
SMON MIB定义的端口复制机制允许目标端口成为任何RMON统计数据的数据源。但是，NMS应用程序应检查其是否具有从源端口到目标端口过滤错误的设备功能（portCopyCap），以及该功能是否已启用，以便对复制的端口流量提供正确的解释。
RMON host and matrix group statistics entries MAY be aggregated by use of the extended dataSource capability defined in SMON. RMON 2 groups are similarly extended through the use of SMON's dataSource definition.
RMON主机和矩阵组统计项可以通过使用SMON中定义的扩展数据源功能进行聚合。RMON2组通过使用SMON的数据源定义进行了类似的扩展。
RMON also defines a simple thresholding monitoring mechanism, event-logging and event-notification for any MIB instance; SMON utilizes the alarms and events groups from RMON without modification. These groups SHOULD be implemented on SMON devices if a simple thresholding mechanism is desired.
RMON还为任何MIB实例定义了一个简单的阈值监控机制、事件日志和事件通知；SMON使用RMON的报警和事件组，无需修改。如果需要简单的阈值机制，则应在SMON设备上实现这些组。
The RMON 2 usrHistory group (user-defined history collection) SHOULD be implemented by an SMON device if a history collection mechanism is desired for smonStats entries.
如果smonStats条目需要历史收集机制，则RMON 2 usrHistory组（用户定义的历史收集）应由SMON设备实现。
The SMON MIB utilizes the propVirtual(53) ifType defined in the Interfaces Group MIB [22] to provide SMON and RMON with new dataSources such as VLANs and internal monitoring points. NMS applications SHOULD consult the SMON dataSource capabilities group (dataSourceCap) for a description of these virtual interfaces.
SMON MIB利用接口组MIB[22]中定义的propVirtual（53）ifType为SMON和RMON提供新的数据源，如VLAN和内部监控点。NMS应用程序应咨询SMON数据源能力组（dataSourceCap），以了解这些虚拟接口的描述。
The SMON MIB does not mandate Entity MIB [18] support, but allows for physical entities, as defined by this MIB to be defined as SMON data sources. For such cases, the support for the entPhysicalTable is required.
SMON MIB不强制要求实体MIB[18]支持，但允许将此MIB定义的物理实体定义为SMON数据源。对于这种情况，需要对entPhysicalTable的支持。
One of the important indicators for measuring the effectiveness of a switching device is the ratio between the number of forwarded frames and the number of dropped frames at the switch port.
衡量交换设备有效性的一个重要指标是交换机端口转发帧数和丢弃帧数之间的比率。
It is out of the scope of this MIB to provide instrumentation information relative to switching devices. However, such indication may be part of other MIB modules.
提供与交换设备相关的仪表信息超出了本MIB的范围。然而，此类指示可能是其他MIB模块的一部分。
For instance the Bridge MIB [23] provides such MIB objects, for the 802.1 bridges (dot1dTpPortInFrames, dot1dTpPortInDiscards) and switches managed according to the 802.1 bridge model MAY provide this information.
例如，网桥MIB[23]为802.1网桥（dot1dtpportinframe、dot1dtpportindiscard）提供此类MIB对象，并且根据802.1网桥模型管理的交换机可以提供此信息。
The SMON MIB provides simple statistics per VLAN and priority levels. Those two categories of statistics are important to managers of switched networks. Interoperability for those features is ensured by the use of the IEEE 802.1 p/Q standards ([19], [20]) defined by the IEEE 802.1 WG. Interoperability from the SMON MIB point of view is ensured by referencing the IEEE definition of VLANs and priority levels for the SMON statistics.
SMON MIB提供每个VLAN和优先级的简单统计信息。这两类统计数据对交换网络的管理者很重要。通过使用IEEE 802.1工作组定义的IEEE 802.1 p/Q标准（[19]、[20]），可确保这些功能的互操作性。通过参考IEEE VLAN定义和SMON统计数据的优先级级别，从SMON MIB的角度确保了互操作性。
The SMON probeCapabilities BITS object covers the following four capabilities.
SMON probeCapabilities BITS对象包含以下四种功能。
- smonVlanStats(0) The probe supports the smonVlanStats object group.
- smonVlanStats（0）探测器支持smonVlanStats对象组。
- smonPrioStats(1) The probe supports the smonPrioStats object group.
- smonPrioStats（1）探测器支持smonPrioStats对象组。
- dataSource(2) The probe supports the dataSourceCaps object group.
- dataSource（2）探测器支持dataSourceCaps对象组。
- portCopy(4) The probe supports the portCopyConfig object group.
- portCopy（4）探测器支持portCopyConfig对象组。
The smonVlanStats MIB group includes the control and statistics objects related to 802.1Q VLANs. Specific statistics per 802.1Q virtual LAN are supported. The group provides a high level view of total VLAN usage, and relative non-unicast traffic usage.
smonVlanStats MIB组包括与802.1Q VLAN相关的控制和统计对象。支持每个802.1Q虚拟LAN的特定统计信息。该组提供了总VLAN使用情况和相对非单播流量使用情况的高级视图。
It is an implementation-specific matter as to how the agent determines the proper default-VLAN for untagged or priority-tagged frames.
代理如何为未标记或优先级标记的帧确定适当的默认VLAN是实现特定的问题。
The smonPrioStatsTable provides a distribution based on the user_priority field in the VLAN header.
smonPrioStatsTable根据VLAN标头中的用户优先级字段提供分发。
Note that this table merely reports priority as encoded in VLAN headers, not the priority (if any) given the frame for actual switching purposes.
请注意，此表仅报告VLAN头中编码的优先级，而不是为实际交换目的给定帧的优先级（如果有）。
The dataSourceCaps MIB group identifies all supported data sources on an SMON device. An NMS MAY use this table to discover the RMON and Copy Port attributes of each data source.
dataSourceCaps MIB组标识SMON设备上所有受支持的数据源。NMS可以使用此表来发现每个数据源的RMON和复制端口属性。
Upon restart of the agent, the dataSourceTable, ifTable and entPhysicalTable are initialized for the available data sources. The agent MAY modify these tables as data sources become known or are removed (e.g. hot swap of interfaces, chassis cards or the discovery of VLAN usage). It is understood that dataSources representing VLANs may not always be instantiated immediately upon restart, but rather as VLAN usage is detected by the agent. The agent SHOULD attempt to create dataSource and interface entries for all dataSources as soon as possible.
重新启动代理后，将为可用数据源初始化dataSourceTable、ifTable和entPhysicalTable。当数据源已知或被删除时（例如，热插拔接口、机箱卡或发现VLAN使用情况），代理可以修改这些表。可以理解的是，代表VLAN的数据源并不总是在重启时立即实例化，而是在代理检测到VLAN使用情况时实例化。代理应尝试尽快为所有数据源创建数据源和接口条目。
For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry, the agent MUST create an associated ifEntry with a ifType value of associated dataSourceCapsIfIndex object.
对于表示VLAN或entPhysicalEntry的每个dataSourceCapsEntry，代理必须创建一个关联的ifEntry，其ifType值为关联的DataSourceCapsiIndex对象。
The rationale of the above derives from the fact that according to [16] and [17] an RMON dataSource MUST be associated with an ifEntry. Specifically, the dataSourceCapsTable allows for an agent to map Entity MIB physical entities (e.g., switch backplanes) and entire VLANs to ifEntries with ifType "propVirtual(53)". This ifEntry values will be used as the actual values in RMON control table dataSource objects. This allows for physical entities and VLANs to be treated as RMON data sources, and RMON functions to be applied to this type
根据[16]和[17]的规定，RMON数据源必须与ifEntry关联，这是上述理由的基础。具体而言，dataSourceCapsTable允许代理将实体MIB物理实体（例如交换机背板）和整个VLAN映射到ifType为“propVirtual（53）”的ifEntries。此ifEntry值将用作RMON控制表数据源对象中的实际值。这允许将物理实体和VLAN视为RMON数据源，并将RMON功能应用于此类型
of data sources.
对数据源的管理。
The portCopyConfig MIB group includes the objects defined for the control of the port copy functionality in a device.
portCopyConfig MIB组包括为控制设备中的端口复制功能而定义的对象。
The standard does not place a limit on the mode in which this copy function may be used:
本标准未对该复制功能的使用模式进行限制：
Mode 1 -- 1:1 Copy
模式1——1:1拷贝
Single dataSource copied to a single destination dataSource. Agent MAY limit configuration based on ifTypes, ifSpeeds, half-duplex/full-duplex, or agent resources. In this mode the single instance of the portCopyDestDropEvents object refers to dropped frames on the portCopyDest interface.
单个数据源复制到单个目标数据源。代理可以基于IFTYPE、IFSPEED、半双工/全双工或代理资源限制配置。在此模式下，portCopyDestDropEvents对象的单个实例引用portCopyDest接口上丢弃的帧。
Mode 2 -- N:1 Copy
模式2——N:1份
Multiple dataSources copied to a single destination dataSource. Agent MAY limit configuration based on ifTypes, ifSpeeds, half-duplex/full-duplex, portCopyDest over-subscription, or agent resources. In this mode all N instances of the portCopyDestDropEvents object SHOULD contain the same value, and refer to dropped frames on the portCopyDest interface.
多个数据源复制到单个目标数据源。代理可以基于IFTYPE、IFSPEED、半双工/全双工、portCopyDest over subscription或代理资源限制配置。在此模式下，portCopyDestDropEvents对象的所有N个实例都应包含相同的值，并引用portCopyDest接口上丢弃的帧。
Mode 3 -- N:M Copy
模式3——N:M拷贝
Multiple dataSources copied to multiple destination dataSources. Agent MAY limit configuration based on ifTypes, ifSpeeds, half-duplex/full-duplex, portCopyDest over-subscription, or agent resources. Since portCopyDestDropEvents is kept per destination port, all instances of the portCopyDestDropEvents object associated with (indexed by) a given portCopyDest SHOULD have the same value (i.e. replicated or aliased for each instance associated with a given portCopyDest).
多个数据源复制到多个目标数据源。代理可以基于IFTYPE、IFSPEED、半双工/全双工、portCopyDest over subscription或代理资源限制配置。由于portCopyDestDropEvents是按目标端口保存的，因此与给定portCopyDest关联（由其索引）的portCopyDestDropEvents对象的所有实例都应具有相同的值（即，与给定portCopyDest关联的每个实例的复制值或别名值）。
The rows do not have an OwnerString, since multiple rows MAY be part of the same portCopy operation. The agent is expected to activate or deactivate entries one at a time, based on the rowStatus for the given row. This can lead to unpredictable results in Modes 2 and 3 in applications utilizing the portCopy target traffic, if multiple PDUs are used to fully configure the operation. It is RECOMMENDED that an entire portCopy operation be configured in one SetRequest PDU if possible.
这些行没有OwnerString，因为多行可能是同一portCopy操作的一部分。代理将根据给定行的行状态，一次激活或停用一个条目。如果使用多个PDU完全配置操作，则在使用portCopy目标流量的应用程序中，这可能导致模式2和3中出现不可预测的结果。如果可能，建议在一个SetRequest PDU中配置整个portCopy操作。
The portCopyDest object MAY NOT reference an interface associated with a packet-based VLAN (smonVlanDataSource.<V>), but this dataSource type MAY be used as a portCopySource.
portCopyDest对象可能不会引用与基于数据包的VLAN（SMONVLANDATASURCE.<V>）关联的接口，但此数据源类型可以用作portCopySource。
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 not active. Thus, the method for modifying these parameters is to de-activate the entry, perform the SNMP Set operations to modify the entry, and then re-activate the entry. Deleting the control entry causes the deletion of any associated data entries, which also gives a convenient method for reclaiming the resources used by the associated data.
此MIB中的许多功能组都有一个或多个用于设置控制参数的表，以及一个或多个用于放置操作结果的数据表。控制表通常是读/写性质的，而数据表通常是只读的。由于控制表中的参数通常描述数据表中的结果数据，因此许多参数只能在控制项未激活时修改。因此，修改这些参数的方法是取消激活条目，执行SNMP设置操作以修改条目，然后重新激活条目。删除控制项会导致删除任何关联的数据项，这也为回收关联数据使用的资源提供了一种方便的方法。
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.
为了便于多个管理者进行控制，资源必须在管理者之间共享。这些资源通常是函数所需的内存和计算资源。
The control mechanisms defined and used in this MIB are the same as those defined in the RMON MIB [17], for control functionality and interaction with multiple managers.
此MIB中定义和使用的控制机制与RMON MIB[17]中定义的控制机制相同，用于控制功能和与多个管理器的交互。
SMON-MIB DEFINITIONS ::= BEGIN
SMON-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, Counter64 FROM SNMPv2-SMI RowStatus, TEXTUAL-CONVENTION FROM SNMPv2-TC rmon, OwnerString FROM RMON-MIB LastCreateTime, DataSource, rmonConformance, probeConfig FROM RMON2-MIB InterfaceIndex FROM IF-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
从SNMPv2 SMI RowStatus导入模块标识、对象类型、计数器32、整数32、计数器64、从SNMPv2 TC rmon导入文本约定、从rmon-MIB LastCreateTime导入所有者字符串、从IF-MIB MODULE-COMPRESSION导入数据源、从RMON2-MIB InterfaceIndex导入RMONCONCONCONCONCONFORMATION、从SNMPv2 CONF导入对象组；
switchRMON MODULE-IDENTITY LAST-UPDATED "9812160000Z" ORGANIZATION "IETF RMON MIB Working Group" CONTACT-INFO "IETF RMONMIB WG Mailing list: rmonmib@cisco.com
switchRMON模块标识最后更新的“9812160000Z”组织“IETF RMON MIB工作组”联系人信息“IETF RMONMIB工作组邮件列表：rmonmib@cisco.com
Rich Waterman Allot Networks Inc. Tel: +1-408-559-0253 Email: rich@allot.com
Rich Waterman Allot Networks Inc.电话：+1-408-559-0253电子邮件：rich@allot.com
Bill Lahaye Xylan Corp. Tel: +1-800-995-2612 Email: lahaye@ctron.com
Bill Lahaye Xylan公司电话：+1-800-995-2612电子邮件：lahaye@ctron.com
Dan Romascanu Lucent Technologies Tel: +972-3-645-8414 Email: dromasca@lucent.com
Dan Romascanu Lucent Technologies电话：+972-3-645-8414电子邮件：dromasca@lucent.com
Steven Waldbusser International Network Services (INS) Tel: +1-650-318-1251 Email: waldbusser@ins.com"
Steven Waldbusser国际网络服务（INS）电话：+1-650-318-1251电子邮件：waldbusser@ins.com"
DESCRIPTION "The MIB module for managing remote monitoring device implementations for Switched Networks"
描述“用于管理交换网络远程监控设备实现的MIB模块”
-- revision history
--修订历史
REVISION "9812160000Z" -- 16 Dec 1998 midemight DESCRIPTION "Initial Version, published as RFC 2613."
修订版“9812160000Z”-1998年12月16日中期说明“初始版本，作为RFC 2613出版。”
::= { rmon 22 }
::= { rmon 22 }
smonMIBObjects OBJECT IDENTIFIER ::= { switchRMON 1 }
smonMIBObjects OBJECT IDENTIFIER ::= { switchRMON 1 }
dataSourceCaps OBJECT IDENTIFIER ::= {smonMIBObjects 1}
smonStats OBJECT IDENTIFIER ::= {smonMIBObjects 2}
portCopyConfig OBJECT IDENTIFIER ::= {smonMIBObjects 3}
smonRegistrationPoints OBJECT IDENTIFIER ::= {smonMIBObjects 4}
dataSourceCaps OBJECT IDENTIFIER ::= {smonMIBObjects 1}
smonStats OBJECT IDENTIFIER ::= {smonMIBObjects 2}
portCopyConfig OBJECT IDENTIFIER ::= {smonMIBObjects 3}
smonRegistrationPoints OBJECT IDENTIFIER ::= {smonMIBObjects 4}
-- Textual Conventions --
--文本约定--
SmonDataSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the source of the data that the associated function
is configured to analyze. This Textual Convention
extends the DataSource Textual Convention defined by RMON 2
to the following data source types:
SmonDataSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the source of the data that the associated function
is configured to analyze. This Textual Convention
extends the DataSource Textual Convention defined by RMON 2
to the following data source types:
- ifIndex.<I> DataSources of this traditional form are called 'port-based', but only if ifType.<I> is not equal to 'propVirtual(53)'.
- 这种传统形式的iIndex.<I>数据源称为“基于端口”，但前提是iType.<I>不等于“propVirtual（53）”。
- smonVlanDataSource.<V> A dataSource of this form refers to a 'Packet-based VLAN' and is called a 'VLAN-based' dataSource. <V> is the VLAN ID as defined by the IEEE 802.1Q standard [19]. The value is between 1 and 4094 inclusive, and it represents an 802.1Q VLAN-ID with global scope within a given bridged domain, as defined by [19].
- smonVlanDataSource.<V>这种形式的数据源指的是“基于数据包的VLAN”，称为“基于VLAN的”数据源<五> 是IEEE 802.1Q标准定义的VLAN ID[19]。该值介于1和4094（含1和4094）之间，表示给定桥接域内具有全局作用域的802.1Q VLAN-ID，如[19]所定义。
- entPhysicalEntry.<N> A dataSource of this form refers to a physical entity within the agent (e.g. entPhysicalClass = backplane(4)) and is called an 'entity-based' dataSource." SYNTAX OBJECT IDENTIFIER
-entPhysicalEntry.<N>此表单的数据源指代理内的物理实体（例如entPhysicalClass=backplane（4）），称为“基于实体的”数据源。“语法对象标识符”
-- The smonCapabilities object describes SMON agent capabilities.
--smonCapabilities对象描述SMON代理功能。
smonCapabilities OBJECT-TYPE SYNTAX BITS { smonVlanStats(0),
smonCapabilities对象类型语法位{smonVlanStats（0），
smonPrioStats(1),
dataSource(2),
smonUnusedBit(3),
portCopy(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the SMON MIB groups supported
by this agent."
::= { probeConfig 15 }
smonPrioStats(1),
dataSource(2),
smonUnusedBit(3),
portCopy(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the SMON MIB groups supported
by this agent."
::= { probeConfig 15 }
-- dataSourceCaps MIB group - defines SMON data source and port
-- copy capabilities for devices supporting SMON.
-- dataSourceCaps MIB group - defines SMON data source and port
-- copy capabilities for devices supporting SMON.
-- A NMS application will check this MIB group and retrieve
-- information about the SMON capabilities of the device before
-- applying SMON control operations to the device.
-- A NMS application will check this MIB group and retrieve
-- information about the SMON capabilities of the device before
-- applying SMON control operations to the device.
-- dataSourceCapsTable: defines capabilities of RMON data sources
--dataSourceCapsTable：定义RMON数据源的功能
dataSourceCapsTable OBJECT-TYPE SYNTAX SEQUENCE OF DataSourceCapsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes RMON data sources and port copy capabilities. An NMS MAY use this table to discover the identity and attributes of the data sources on a given agent implementation. Similar to the probeCapabilities object, actual row-creation operations will succeed or fail based on the resources available and parameter values used in each row-creation operation.
dataSourceCapsTable对象类型语法DataSourceCapsEntry的序列MAX-ACCESS不可访问状态当前描述“此表介绍了RMON数据源和端口复制功能。NMS可以使用此表来发现给定代理实现上数据源的标识和属性。与probeCapabilities对象类似，实际的行创建操作将根据每个行创建操作中使用的可用资源和参数值成功或失败。
Upon restart of the RMON agent, the dataSourceTable, ifTable, and perhaps entPhysicalTable are initialized for the available dataSources.
在重新启动RMON代理时，将针对可用数据源初始化dataSourceTable、ifTable以及entPhysicalTable。
For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry the agent MUST create an associated ifEntry with a ifType value of 'propVirtual(53)'. This ifEntry will be used as the actual value in RMON control table dataSource objects. The assigned ifIndex value is copied into the associated dataSourceCapsIfIndex object.
对于表示VLAN或entPhysicalEntry的每个dataSourceCapsEntry，代理必须创建ifType值为“propVirtual（53）”的关联ifEntry。此ifEntry将用作RMON控制表数据源对象中的实际值。指定的ifIndex值将复制到关联的DataSourceCapsiIndex对象中。
It is understood that dataSources representing VLANs may not always be instantiated immediately upon restart, but rather as
可以理解的是，代表VLAN的数据源并不总是在重启时立即实例化，而是作为
VLAN usage is detected by the agent. The agent SHOULD attempt
to create dataSource and interface entries for all dataSources
as soon as possible."
::= { dataSourceCaps 1 }
VLAN usage is detected by the agent. The agent SHOULD attempt
to create dataSource and interface entries for all dataSources
as soon as possible."
::= { dataSourceCaps 1 }
dataSourceCapsEntry OBJECT-TYPE
SYNTAX DataSourceCapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries per data source containing descriptions of data
source and port copy capabilities. This table is populated by
the SMON agent with one entry for each supported data
source."
INDEX { IMPLIED dataSourceCapsObject }
::= { dataSourceCapsTable 1 }
dataSourceCapsEntry OBJECT-TYPE
SYNTAX DataSourceCapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries per data source containing descriptions of data
source and port copy capabilities. This table is populated by
the SMON agent with one entry for each supported data
source."
INDEX { IMPLIED dataSourceCapsObject }
::= { dataSourceCapsTable 1 }
DataSourceCapsEntry ::= SEQUENCE {
dataSourceCapsObject
SmonDataSource,
dataSourceRmonCaps
BITS,
dataSourceCopyCaps
BITS,
dataSourceCapsIfIndex
InterfaceIndex
}
DataSourceCapsEntry ::= SEQUENCE {
dataSourceCapsObject
SmonDataSource,
dataSourceRmonCaps
BITS,
dataSourceCopyCaps
BITS,
dataSourceCapsIfIndex
InterfaceIndex
}
dataSourceCapsObject OBJECT-TYPE
SYNTAX SmonDataSource
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an object that can be a SMON data source or a
source or a destination for a port copy operation."
::= { dataSourceCapsEntry 1 }
dataSourceCapsObject OBJECT-TYPE
SYNTAX SmonDataSource
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an object that can be a SMON data source or a
source or a destination for a port copy operation."
::= { dataSourceCapsEntry 1 }
dataSourceRmonCaps OBJECT-TYPE
SYNTAX BITS {
countErrFrames(0),
countAllGoodFrames(1),
countAnyRmonTables(2),
babyGiantsCountAsGood(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
dataSourceRmonCaps OBJECT-TYPE
SYNTAX BITS {
countErrFrames(0),
countAllGoodFrames(1),
countAnyRmonTables(2),
babyGiantsCountAsGood(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" General attributes of the specified dataSource. Note that these are static attributes, which SHOULD NOT be adjusted because of current resources or configuration.
指定数据源的常规属性。请注意，这些是静态属性，不应因为当前资源或配置而进行调整。
- countErrFrames(0) The agent sets this bit for the dataSource if errored frames received on this dataSource can actually be monitored by the agent The agent clears this bit if any errored frames are not visible to the RMON data collector.
- 计数器帧（0）如果代理可以实际监视在此数据源上接收的错误帧，则代理为数据源设置此位。如果RMON数据采集器看不到任何错误帧，则代理清除此位。
- countAllGoodFrames(1) The agent sets this bit for the dataSource if all good frames received on this dataSource can actually be monitored by the agent. The agent clears this bit if any good frames are not visible for RMON collection, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function.
- countAllGoodFrames（1）如果代理可以实际监视在此数据源上接收的所有好帧，则代理为数据源设置此位。如果RMON收集中看不到任何良好的帧，例如，数据源是非混杂接口或内部交换机接口，该接口可能不会接收硬件中切换的帧或网桥转发功能丢弃的帧，则代理将清除该位。
- countAnyRmonTables(2) The agent sets this bit if this dataSource can actually be used in any of the implemented RMON tables, resources notwithstanding. The agent clears this bit if this dataSourceCapsEntry is present simply to identify a dataSource that may only be used as portCopySource and/or a portCopyDest, but not the source of an actual RMON data collection.
- countAnyRmonTables（2）如果此数据源实际上可以在任何已实现的RMON表中使用，则代理将设置此位，尽管有资源限制。如果存在此dataSourceCapsEntry只是为了标识只能用作portCopySource和/或portCopyDest的数据源，而不是实际RMON数据收集的源，则代理将清除此位。
- babyGiantsCountAsGood(3) The agent sets this bit if it can distinguish, for counting purposes, between true giant frames and frames that exceed Ethernet maximum frame size 1518 due to VLAN tagging ('baby giants'). Specifically, this BIT means that frames up to 1522 octets are counted as good.
- BABYGIANTSCONTASGOOD（3）如果出于计数目的，代理可以区分真正的巨型帧和由于VLAN标记而超过以太网最大帧大小1518的帧（“巨型婴儿”），则设置此位。具体而言，该位意味着最多1522个八位字节的帧被视为良好。
Agents not capable of detecting 'baby giants' will clear this bit and will view all frames less than or equal to 1518 octets as 'good frames' and all frames larger than 1518 octets as 'bad frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables.
无法检测“巨型婴儿”的代理将清除此位，并将所有小于或等于1518个八位字节的帧视为“好帧”，大于1518个八位字节的所有帧视为“坏帧”，以便在SmonPlanidStats和smonPrioStats表中计数。
Agents capable of detecting 'baby giants' SHALL consider them as 'good frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables."
能够检测“婴儿巨人”的药物应该认为它们是“好的框架”，用于在SMOVLANIDESTATS和SMONPROSTOSTS表中计数。
::= { dataSourceCapsEntry 2 }
::= { dataSourceCapsEntry 2 }
dataSourceCopyCaps OBJECT-TYPE
dataSourceCopyCaps对象类型
SYNTAX BITS {
copySourcePort(0),
copyDestPort(1),
copySrcTxTraffic(2),
copySrcRxTraffic(3),
countDestDropEvents(4),
copyErrFrames(5),
copyUnalteredFrames(6),
copyAllGoodFrames(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PortCopy function capabilities of the specified dataSource.
Note that these are static capabilities, which SHOULD NOT be
adjusted because of current resources or configuration.
SYNTAX BITS {
copySourcePort(0),
copyDestPort(1),
copySrcTxTraffic(2),
copySrcRxTraffic(3),
countDestDropEvents(4),
copyErrFrames(5),
copyUnalteredFrames(6),
copyAllGoodFrames(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PortCopy function capabilities of the specified dataSource.
Note that these are static capabilities, which SHOULD NOT be
adjusted because of current resources or configuration.
- copySourcePort(0) The agent sets this bit if this dataSource is capable of acting as a source of a portCopy operation. The agent clears this bit otherwise.
- copySourcePort（0）如果此数据源能够充当portCopy操作的源，则代理将设置此位。否则代理将清除此位。
- copyDestPort(1) The agent sets this bit if this dataSource is capable of acting as a destination of a portCopy operation. The agent clears this bit otherwise.
- copyDestPort（1）如果此数据源能够充当portCopy操作的目标，则代理将设置此位。否则代理将清除此位。
- copySrcTxTraffic(2) If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames transmitted out this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared.
- copySrcTxTraffic（2）如果设置了copySourcePort位：如果此数据源能够复制从此portCopy源传输的帧，则代理将设置此位。否则代理将清除此位。支持全双工端口需要此功能。否则：应清除此位。
- copySrcRxTraffic(3) If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames received on this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared.
- CopyScrxtraffic（3）如果设置了copySourcePort位：如果此数据源能够复制此portCopy源上接收的帧，则代理将设置此位。否则代理将清除此位。支持全双工端口需要此功能。否则：应清除此位。
- countDestDropEvents(4) If the copyDestPort bit is set: The agent sets this bit if it is capable of incrementing
- countDestDropEvents（4）如果设置了copyDestPort位：如果代理能够递增，则设置此位
portCopyDestDropEvents, when this dataSource is the target of a portCopy operation and a frame destined to this dataSource is dropped (for RMON counting purposes). Else: this BIT SHOULD be cleared.
portCopyDestDropEvents，当此数据源是portCopy操作的目标并且删除了指向此数据源的帧时（出于RMON计数目的）。否则：应清除此位。
- copyErrFrames(5) If the copySourcePort bit is set: The agent sets this bit if it is capable of copying all errored frames from this portCopy source-port, for errored frames received on this dataSource. Else: this BIT SHOULD be cleared.
- CopyerFrames（5）如果设置了copySourcePort位：如果代理能够从此portCopy源端口复制此数据源上接收的错误帧的所有错误帧，则设置此位。否则：应清除此位。
- copyUnalteredFrames(6) If the copySourcePort bit is set: The agent sets the copyUnalteredFrames bit If it is capable of copying all frames from this portCopy source-port without alteration in any way; Else: this bit SHOULD be cleared.
- copyUnalteredFrames（6）如果设置了copySourcePort位：如果代理能够从该portCopy源端口复制所有帧而不进行任何更改，则设置copyUnalteredFrames位；否则：应清除此位。
- copyAllGoodFrames(7) If the copySourcePort bit is set: The agent sets this bit for the dataSource if all good frames received on this dataSource are normally capable of being copied by the agent. The agent clears this bit if any good frames are not visible for the RMON portCopy operation, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function. Else: this bit SHOULD be cleared."
- copyAllGoodFrames（7）如果设置了copySourcePort位：如果在此数据源上接收的所有好帧通常都能够被代理复制，则代理将为数据源设置此位。如果RMON portCopy操作看不到任何良好的帧，则代理将清除此位，例如，数据源是非混杂接口或内部交换机接口，该接口可能不会接收硬件中切换的帧或网桥转发功能丢弃的帧。否则：应清除此位。“
::= { dataSourceCapsEntry 3 }
::= { dataSourceCapsEntry 3 }
dataSourceCapsIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the ifIndex value of the ifEntry associated with this smonDataSource. The agent MUST create 'propVirtual' ifEntries for each dataSourceCapsEntry of type VLAN or entPhysicalEntry."
DataSourceCapsiIndex对象类型语法接口Index MAX-ACCESS只读状态当前描述“此对象包含与此smonDataSource关联的ifEntry的ifIndex值。代理必须为VLAN或entPhysicalEntry类型的每个DataSourceCapsiIndex创建'propVirtual'ifEntries。”
::= { dataSourceCapsEntry 4 }
::= { dataSourceCapsEntry 4 }
-- The SMON Statistics MIB Group
--SMON统计MIB组
-- aggregated statistics for IEEE 802.1Q VLAN environments.
--IEEE 802.1Q VLAN环境的聚合统计信息。
-- VLAN statistics can be gathered by configuring smonVlanIdStats
-- and/or smonPrioStats collections. These functions allow a
-- VLAN-ID or user priority distributions per dataSource,
-- auto-populated by the agent in a manner similar to the RMON
-- hostTable.
-- VLAN statistics can be gathered by configuring smonVlanIdStats
-- and/or smonPrioStats collections. These functions allow a
-- VLAN-ID or user priority distributions per dataSource,
-- auto-populated by the agent in a manner similar to the RMON
-- hostTable.
-- Only good frames are counted in the tables described in this
-- section.
-- Only good frames are counted in the tables described in this
-- section.
-- VLAN ID Stats
--VLAN ID统计
-- smonVlanStatsControlTable allows configuration of VLAN-ID
-- collections.
-- smonVlanStatsControlTable allows configuration of VLAN-ID
-- collections.
smonVlanStatsControlTable OBJECT-TYPE SYNTAX SEQUENCE OF SmonVlanStatsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
smonVlanStatsControlTable对象类型语法序列SmonVlanStatsControlEntry MAX-ACCESS不可访问状态当前说明
"Controls the setup of VLAN statistics tables.
“控制VLAN统计表的设置。
The statistics collected represent a distribution based on
the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed
to the data source for the collection."
::= { smonStats 1 }
The statistics collected represent a distribution based on
the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed
to the data source for the collection."
::= { smonStats 1 }
smonVlanStatsControlEntry OBJECT-TYPE
SYNTAX SmonVlanStatsControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the smonVlanStatsControlTable."
INDEX { smonVlanStatsControlIndex }
::= { smonVlanStatsControlTable 1 }
smonVlanStatsControlEntry OBJECT-TYPE
SYNTAX SmonVlanStatsControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the smonVlanStatsControlTable."
INDEX { smonVlanStatsControlIndex }
::= { smonVlanStatsControlTable 1 }
SmonVlanStatsControlEntry ::= SEQUENCE {
smonVlanStatsControlIndex Integer32,
smonVlanStatsControlDataSource DataSource,
smonVlanStatsControlCreateTime LastCreateTime,
smonVlanStatsControlOwner OwnerString,
smonVlanStatsControlStatus RowStatus
}
SmonVlanStatsControlEntry ::= SEQUENCE {
smonVlanStatsControlIndex Integer32,
smonVlanStatsControlDataSource DataSource,
smonVlanStatsControlCreateTime LastCreateTime,
smonVlanStatsControlOwner OwnerString,
smonVlanStatsControlStatus RowStatus
}
smonVlanStatsControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique arbitrary index for this smonVlanStatsControlEntry."
::= { smonVlanStatsControlEntry 1 }
smonVlanStatsControlIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique arbitrary index for this smonVlanStatsControlEntry."
::= { smonVlanStatsControlEntry 1 }
smonVlanStatsControlDataSource OBJECT-TYPE SYNTAX DataSource MAX-ACCESS read-create STATUS current DESCRIPTION "The source of data for this set of VLAN statistics.
smonVlanStatsControlDataSource对象类型语法DataSource MAX-ACCESS read create STATUS current DESCRIPTION“此VLAN统计数据集的数据源。
This object MAY NOT be modified if the associated
smonVlanStatsControlStatus object is equal to active(1)."
::= { smonVlanStatsControlEntry 2 }
This object MAY NOT be modified if the associated
smonVlanStatsControlStatus object is equal to active(1)."
::= { smonVlanStatsControlEntry 2 }
smonVlanStatsControlCreateTime OBJECT-TYPE
SYNTAX LastCreateTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this control entry was last
activated. This object allows to a management station to
detect deletion and recreation cycles between polls."
::= { smonVlanStatsControlEntry 3 }
smonVlanStatsControlCreateTime OBJECT-TYPE
SYNTAX LastCreateTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this control entry was last
activated. This object allows to a management station to
detect deletion and recreation cycles between polls."
::= { smonVlanStatsControlEntry 3 }
smonVlanStatsControlOwner OBJECT-TYPE
SMONVLANSTATSCONTROLNER对象类型
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Administratively assigned named of the owner of this entry.
It usually defines the entity that created this entry and is
therefore using the resources assigned to it, though there is
no enforcement mechanism, nor assurance that rows created are
ever used."
::= { smonVlanStatsControlEntry 4 }
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Administratively assigned named of the owner of this entry.
It usually defines the entity that created this entry and is
therefore using the resources assigned to it, though there is
no enforcement mechanism, nor assurance that rows created are
ever used."
::= { smonVlanStatsControlEntry 4 }
smonVlanStatsControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row.
smonVlanStatsControlStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此行的状态。
An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value.
除非条目中的所有对象都具有适当的值，否则条目可能不存在于活动状态。
If this object is not equal to active(1), all associated
entries in the smonVlanIdStatsTable SHALL be deleted."
::= { smonVlanStatsControlEntry 5 }
If this object is not equal to active(1), all associated
entries in the smonVlanIdStatsTable SHALL be deleted."
::= { smonVlanStatsControlEntry 5 }
-- The VLAN Statistics Table
--VLAN统计表
smonVlanIdStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF SmonVlanIdStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Contains the VLAN statistics data. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection.
SMONVLANIDStateSTABLE SmonVlanIdStatsEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“的对象类型语法序列包含VLAN统计数据。收集到的统计数据表示基于IEEE 802.1Q VLAN-ID（VID）的分布，每个良好的帧归因于收集的数据源。
This function applies the same rules for attributing frames to VLAN-based collections. RMON VLAN statistics are collected after the Ingress Rules defined in section 3.13 of the VLAN Specification [20] are applied.
此函数应用相同的规则将帧归因于基于VLAN的集合。在应用VLAN规范[20]第3.13节中定义的入口规则后，收集RMON VLAN统计信息。
It is possible that entries in this table will be
garbage-collected, based on agent resources, and VLAN
configuration. Agents are encouraged to support all 4094
index values and not garbage collect this table."
::= { smonStats 2 }
It is possible that entries in this table will be
garbage-collected, based on agent resources, and VLAN
configuration. Agents are encouraged to support all 4094
index values and not garbage collect this table."
::= { smonStats 2 }
smonVlanIdStatsEntry OBJECT-TYPE
SYNTAX SmonVlanIdStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in smonVlanIdStatsTable."
INDEX { smonVlanStatsControlIndex, smonVlanIdStatsId }
::= { smonVlanIdStatsTable 1 }
smonVlanIdStatsEntry OBJECT-TYPE
SYNTAX SmonVlanIdStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in smonVlanIdStatsTable."
INDEX { smonVlanStatsControlIndex, smonVlanIdStatsId }
::= { smonVlanIdStatsTable 1 }
SmonVlanIdStatsEntry ::= SEQUENCE {
smonVlanIdStatsId Integer32,
smonVlanIdStatsTotalPkts Counter32,
smonVlanIdStatsTotalOverflowPkts Counter32,
smonVlanIdStatsTotalHCPkts Counter64,
smonVlanIdStatsTotalOctets Counter32,
smonVlanIdStatsTotalOverflowOctets Counter32,
smonVlanIdStatsTotalHCOctets Counter64,
smonVlanIdStatsNUcastPkts Counter32,
SmonVlanIdStatsEntry ::= SEQUENCE {
smonVlanIdStatsId Integer32,
smonVlanIdStatsTotalPkts Counter32,
smonVlanIdStatsTotalOverflowPkts Counter32,
smonVlanIdStatsTotalHCPkts Counter64,
smonVlanIdStatsTotalOctets Counter32,
smonVlanIdStatsTotalOverflowOctets Counter32,
smonVlanIdStatsTotalHCOctets Counter64,
smonVlanIdStatsNUcastPkts Counter32,
smonVlanIdStatsNUcastOverflowPkts Counter32, smonVlanIdStatsNUcastHCPkts Counter64, smonVlanIdStatsNUcastOctets Counter32, smonVlanIdStatsNUcastOverflowOctets Counter32, smonVlanIdStatsNUcastHCOctets Counter64, smonVlanIdStatsCreateTime LastCreateTime }
smonVlanIdStatsNUcastOverflowPkts计数器32、smonVlanIdStatsNUcastHCPkts计数器64、smonVlanIdStatsNUcastOctets计数器32、smonVlanIdStatsNUcastOverflowOctets计数器32、SMONVLANIDStatSNUCASTHctets计数器64、smonVlanIdStatsCreateTime LastCreateTime}
smonVlanIdStatsId OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The unique identifier of the VLAN monitored for this specific statistics collection.
smonVlanIdStatsId对象类型语法Integer32（1..4094）MAX-ACCESS not ACCESS STATUS current DESCRIPTION“为此特定统计信息集合监视的VLAN的唯一标识符。
Tagged packets match the VID for the range between 1 and 4094.
An external RMON probe MAY detect VID=0 on an Inter Switch
Link, in which case the packet belongs to a VLAN determined by
the PVID of the ingress port. The VLAN to which such a packet
belongs can be determined only by a RMON probe internal to the
switch."
REFERENCE
"Draft Standard for Virtual Bridged Local Area Networks,
P802.1Q/D10, chapter 3.13"
::= { smonVlanIdStatsEntry 1 }
Tagged packets match the VID for the range between 1 and 4094.
An external RMON probe MAY detect VID=0 on an Inter Switch
Link, in which case the packet belongs to a VLAN determined by
the PVID of the ingress port. The VLAN to which such a packet
belongs can be determined only by a RMON probe internal to the
switch."
REFERENCE
"Draft Standard for Virtual Bridged Local Area Networks,
P802.1Q/D10, chapter 3.13"
::= { smonVlanIdStatsEntry 1 }
smonVlanIdStatsTotalPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on this VLAN."
::= { smonVlanIdStatsEntry 2 }
smonVlanIdStatsTotalPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on this VLAN."
::= { smonVlanIdStatsEntry 2 }
smonVlanIdStatsTotalOverflowPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsTotalPkts
counter has overflowed."
::= { smonVlanIdStatsEntry 3 }
smonVlanIdStatsTotalOverflowPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsTotalPkts
counter has overflowed."
::= { smonVlanIdStatsEntry 3 }
smonVlanIdStatsTotalHCPkts OBJECT-TYPE SYNTAX Counter64
smonVlanIdStatsTotalHCPkts对象类型语法计数器64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on this VLAN."
::= { smonVlanIdStatsEntry 4 }
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on this VLAN."
::= { smonVlanIdStatsEntry 4 }
smonVlanIdStatsTotalOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on this VLAN."
::= { smonVlanIdStatsEntry 5 }
smonVlanIdStatsTotalOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on this VLAN."
::= { smonVlanIdStatsEntry 5 }
smonVlanIdStatsTotalOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsTotalOctets
counter has overflowed."
::= { smonVlanIdStatsEntry 6 }
smonVlanIdStatsTotalOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsTotalOctets
counter has overflowed."
::= { smonVlanIdStatsEntry 6 }
smonVlanIdStatsTotalHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on this VLAN."
::= { smonVlanIdStatsEntry 7 }
smonVlanIdStatsTotalHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on this VLAN."
::= { smonVlanIdStatsEntry 7 }
smonVlanIdStatsNUcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast packets counted on this
VLAN."
::= { smonVlanIdStatsEntry 8 }
smonVlanIdStatsNUcastPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast packets counted on this
VLAN."
::= { smonVlanIdStatsEntry 8 }
smonVlanIdStatsNUcastOverflowPkts OBJECT-TYPE SYNTAX Counter32 UNITS "packets"
smonVlanIdStatsNUcastOverflowPkts对象类型语法计数器32个单位“数据包”
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsNUcastPkts
counter has overflowed."
::= { smonVlanIdStatsEntry 9 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonVlanIdStatsNUcastPkts
counter has overflowed."
::= { smonVlanIdStatsEntry 9 }
smonVlanIdStatsNUcastHCPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast packets counted on
this VLAN."
::= { smonVlanIdStatsEntry 10 }
smonVlanIdStatsNUcastHCPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast packets counted on
this VLAN."
::= { smonVlanIdStatsEntry 10 }
smonVlanIdStatsNUcastOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast octets counted on
this VLAN."
::= { smonVlanIdStatsEntry 11 }
smonVlanIdStatsNUcastOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of non-unicast octets counted on
this VLAN."
::= { smonVlanIdStatsEntry 11 }
smonVlanIdStatsNUcastOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
smonVlanIdStatsNUcastOctets counter has overflowed."
::= { smonVlanIdStatsEntry 12 }
smonVlanIdStatsNUcastOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
smonVlanIdStatsNUcastOctets counter has overflowed."
::= { smonVlanIdStatsEntry 12 }
smonVlanIdStatsNUcastHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Non-unicast octets counted on
this VLAN."
::= { smonVlanIdStatsEntry 13 }
smonVlanIdStatsNUcastHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Non-unicast octets counted on
this VLAN."
::= { smonVlanIdStatsEntry 13 }
smonVlanIdStatsCreateTime OBJECT-TYPE
smonVlanIdStatsCreateTime对象类型
SYNTAX LastCreateTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this entry was last
activated. This object allows to a management station to
detect deletion and recreation cycles between polls."
::= { smonVlanIdStatsEntry 14 }
SYNTAX LastCreateTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this entry was last
activated. This object allows to a management station to
detect deletion and recreation cycles between polls."
::= { smonVlanIdStatsEntry 14 }
-- smonPrioStatsControlTable
--SmonPriostatsControl表
smonPrioStatsControlTable OBJECT-TYPE SYNTAX SEQUENCE OF SmonPrioStatsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Controls the setup of priority statistics tables.
SMONPriosStatsControlTable对象类型SMONPriosStatsControlEntry MAX-ACCESS不可访问状态当前描述”的语法序列控制优先级统计表的设置。
The smonPrioStatsControlTable allows configuration of collections based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19],[20].
smonPrioStatsControlTable允许根据[19]、[20]在标记控制信息（TCI）字段中编码的3位用户优先级字段的值配置集合。
Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes."
请注意，此表仅报告VLAN报头中编码的优先级，而不是为实际交换目的赋予帧的优先级（如果有）。”
::= { smonStats 3 }
::= { smonStats 3 }
smonPrioStatsControlEntry OBJECT-TYPE
SYNTAX SmonPrioStatsControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the smonPrioStatsControlTable."
INDEX { smonPrioStatsControlIndex }
::= { smonPrioStatsControlTable 1 }
smonPrioStatsControlEntry OBJECT-TYPE
SYNTAX SmonPrioStatsControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the smonPrioStatsControlTable."
INDEX { smonPrioStatsControlIndex }
::= { smonPrioStatsControlTable 1 }
SmonPrioStatsControlEntry ::= SEQUENCE {
smonPrioStatsControlIndex Integer32,
smonPrioStatsControlDataSource DataSource,
smonPrioStatsControlCreateTime LastCreateTime,
smonPrioStatsControlOwner OwnerString,
smonPrioStatsControlStatus RowStatus
}
SmonPrioStatsControlEntry ::= SEQUENCE {
smonPrioStatsControlIndex Integer32,
smonPrioStatsControlDataSource DataSource,
smonPrioStatsControlCreateTime LastCreateTime,
smonPrioStatsControlOwner OwnerString,
smonPrioStatsControlStatus RowStatus
}
smonPrioStatsControlIndex OBJECT-TYPE
smonPrioStatsControlIndex对象类型
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique arbitrary index for this smonPrioStatsControlEntry."
::= { smonPrioStatsControlEntry 1 }
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique arbitrary index for this smonPrioStatsControlEntry."
::= { smonPrioStatsControlEntry 1 }
smonPrioStatsControlDataSource OBJECT-TYPE SYNTAX DataSource MAX-ACCESS read-create STATUS current DESCRIPTION "The source of data for this set of VLAN statistics.
smonPrioStatsControlDataSource对象类型语法DataSource MAX-ACCESS读取创建状态当前描述“此VLAN统计数据集的数据源。
This object MAY NOT be modified if the associated
smonPrioStatsControlStatus object is equal to active(1)."
::= { smonPrioStatsControlEntry 2 }
This object MAY NOT be modified if the associated
smonPrioStatsControlStatus object is equal to active(1)."
::= { smonPrioStatsControlEntry 2 }
smonPrioStatsControlCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this entry was created. This object allows to a management station to detect deletion and recreation cycles between polls."
smonPrioStatsControlCreateTime对象类型语法LastCreateTime MAX-ACCESS只读状态当前描述“创建此项时的系统正常运行时间值。此对象允许管理站检测轮询之间的删除和重新创建周期。”
::= { smonPrioStatsControlEntry 3 }
::= { smonPrioStatsControlEntry 3 }
smonPrioStatsControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Administratively assigned named of the owner of this entry.
It usually defines the entity that created this entry and is
therefore using the resources assigned to it, though there is
no enforcement mechanism, nor assurance that rows created are
ever used."
::= { smonPrioStatsControlEntry 4 }
smonPrioStatsControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Administratively assigned named of the owner of this entry.
It usually defines the entity that created this entry and is
therefore using the resources assigned to it, though there is
no enforcement mechanism, nor assurance that rows created are
ever used."
::= { smonPrioStatsControlEntry 4 }
smonPrioStatsControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row.
smonPrioStatsControlStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此行的状态。
An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value.
除非条目中的所有对象都具有适当的值，否则条目可能不存在于活动状态。
If this object is not equal to active(1), all associated
entries in the smonPrioStatsTable SHALL be deleted."
::= { smonPrioStatsControlEntry 5 }
If this object is not equal to active(1), all associated
entries in the smonPrioStatsTable SHALL be deleted."
::= { smonPrioStatsControlEntry 5 }
-- The Priority Statistics Table
--优先级统计表
smonPrioStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF SmonPrioStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Contains the priority statistics. The collections are based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19], [20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes.
SmonPrioStatsEntry MAX-ACCESS不可访问状态当前描述”的smonPrioStatsTable对象类型语法序列包含优先级统计信息。集合基于根据[19]、[20]在标记控制信息（TCI）字段中编码的3位用户优先级字段的值。请注意，此表仅报告VLAN报头中编码的优先级，而不是为实际交换目的赋予帧的优先级（如果有）。
No garbage collection is designed for this table, as there
always are at most eight rows per statistical set, and the
low memory requirements do not justify the implementation of
such a mechanism."
::= { smonStats 4 }
No garbage collection is designed for this table, as there
always are at most eight rows per statistical set, and the
low memory requirements do not justify the implementation of
such a mechanism."
::= { smonStats 4 }
smonPrioStatsEntry OBJECT-TYPE
SYNTAX SmonPrioStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in smonPrioStatsTable."
INDEX { smonPrioStatsControlIndex, smonPrioStatsId }
::= { smonPrioStatsTable 1 }
smonPrioStatsEntry OBJECT-TYPE
SYNTAX SmonPrioStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in smonPrioStatsTable."
INDEX { smonPrioStatsControlIndex, smonPrioStatsId }
::= { smonPrioStatsTable 1 }
SmonPrioStatsEntry ::= SEQUENCE {
smonPrioStatsId Integer32,
smonPrioStatsPkts Counter32,
smonPrioStatsOverflowPkts Counter32,
smonPrioStatsHCPkts Counter64,
smonPrioStatsOctets Counter32,
smonPrioStatsOverflowOctets Counter32,
smonPrioStatsHCOctets Counter64
}
SmonPrioStatsEntry ::= SEQUENCE {
smonPrioStatsId Integer32,
smonPrioStatsPkts Counter32,
smonPrioStatsOverflowPkts Counter32,
smonPrioStatsHCPkts Counter64,
smonPrioStatsOctets Counter32,
smonPrioStatsOverflowOctets Counter32,
smonPrioStatsHCOctets Counter64
}
smonPrioStatsId OBJECT-TYPE SYNTAX Integer32 (0..7)
smonPrioStatsId对象类型语法整数32（0..7）
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique identifier of the priority level monitored for
this specific statistics collection."
REFERENCE
" Draft Standard for Virtual Bridged Local Area Networks,
P802.1Q/D10, chapter 4.3.2.1"
::= { smonPrioStatsEntry 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique identifier of the priority level monitored for
this specific statistics collection."
REFERENCE
" Draft Standard for Virtual Bridged Local Area Networks,
P802.1Q/D10, chapter 4.3.2.1"
::= { smonPrioStatsEntry 1 }
smonPrioStatsPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on
this priority level."
::= { smonPrioStatsEntry 2 }
smonPrioStatsPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on
this priority level."
::= { smonPrioStatsEntry 2 }
smonPrioStatsOverflowPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonPrioStatsPkts
counter has overflowed."
::= { smonPrioStatsEntry 3 }
smonPrioStatsOverflowPkts OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonPrioStatsPkts
counter has overflowed."
::= { smonPrioStatsEntry 3 }
smonPrioStatsHCPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on
this priority level."
::= { smonPrioStatsEntry 4 }
smonPrioStatsHCPkts OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets counted on
this priority level."
::= { smonPrioStatsEntry 4 }
smonPrioStatsOctets OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of octets counted on this priority level."
smonPrioStatsOctets对象类型语法计数器32个单位“八位字节”最大访问只读状态当前描述“此优先级上计数的八位字节总数。”
::= { smonPrioStatsEntry 5 }
::= { smonPrioStatsEntry 5 }
smonPrioStatsOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonPrioStatsOctets
counter has overflowed."
::= { smonPrioStatsEntry 6 }
smonPrioStatsOverflowOctets OBJECT-TYPE
SYNTAX Counter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated smonPrioStatsOctets
counter has overflowed."
::= { smonPrioStatsEntry 6 }
smonPrioStatsHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on
this priority level."
::= { smonPrioStatsEntry 7 }
smonPrioStatsHCOctets OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets counted on
this priority level."
::= { smonPrioStatsEntry 7 }
portCopyTable OBJECT-TYPE SYNTAX SEQUENCE OF PortCopyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Port Copy provides the ability to copy all frames from a specified source to specified destination within a switch. Source and destinations MUST be ifEntries, as defined by [22]. One to one, one to many, many to one and many to many source to destination relationships may be configured.
portCopyTable对象类型PortCopyEntry MAX-ACCESS不可访问状态的语法序列当前描述“端口复制提供了将所有帧从指定源复制到交换机内指定目标的能力。源和目标必须是[22]定义的ifEntries。可以配置一对一、一对多、多对一和多对多源到目标的关系。
Applicable counters on the destination will increment for all packets transiting the port, be it by normal bridging/switching or due to packet copy. Note that this table manages no RMON data collection by itself, and an agent may possibly implement no RMON objects except objects related to the port copy operation defined by the portCopyCompliance conformance macro. That allows for a switch with no other embedded RMON capability to perform port copy operations to a destination port at which a different external RMON probe is connected.
对于通过端口传输的所有数据包，无论是通过正常桥接/交换还是由于数据包复制，目的地上的适用计数器都将增加。请注意，此表本身不管理RMON数据收集，代理可能不实现任何RMON对象，但与portCopyCompliance宏定义的端口复制操作相关的对象除外。这允许没有其他嵌入式RMON功能的交换机执行端口复制操作，将端口复制到连接不同外部RMON探测器的目标端口。
One to one, many to one and one to many source to destination relationships may be configured.
可以配置一对一、多对一和一对多源到目标的关系。
Each row that exists in this table defines such a relationship. By disabling a row in this table the port copy relationship no longer exists.
此表中存在的每一行都定义了这种关系。通过禁用此表中的行，端口复制关系不再存在。
The number of entries and the types of port copies (1-1, many-1, 1-many) are implementation specific and could possibly be dynamic due to changing resource availability.
条目的数量和端口副本的类型（1-1、多-1、1-多）是特定于实现的，并且可能由于资源可用性的变化而动态变化。
In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'.
为了配置源到目标portCopy关系，源和目标接口必须作为ifTable中的ifEntry出现，并且它们各自的ifAdminStatus和ifOperStatus值必须等于“up（1）”。如果在激活portCopyEntry后这两个对象中的任何一个的值发生更改，portCopyStatus将转换为“notReady（3）”。
The capability of an interface to be source or destination of a port copy operation is described by the 'copySourcePort(0)' and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created.
接口作为端口复制操作的源或目标的能力由dataSourceCopyCaps中的“copySourcePort（0）”和“copyDestPort（1）”位描述。代理应适当设置这些位，以便创建portCopyEntry。
Applicable counters on the destination will increment for all
packets transmitted, be it by normal bridging/switching or
due to packet copy."
::= { portCopyConfig 1 }
Applicable counters on the destination will increment for all
packets transmitted, be it by normal bridging/switching or
due to packet copy."
::= { portCopyConfig 1 }
portCopyEntry OBJECT-TYPE
SYNTAX PortCopyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Describes a particular port copy entry."
INDEX { portCopySource, portCopyDest }
::= { portCopyTable 1 }
portCopyEntry OBJECT-TYPE
SYNTAX PortCopyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Describes a particular port copy entry."
INDEX { portCopySource, portCopyDest }
::= { portCopyTable 1 }
PortCopyEntry ::= SEQUENCE {
portCopySource
InterfaceIndex,
portCopyDest
InterfaceIndex,
portCopyDestDropEvents
Counter32,
portCopyDirection
INTEGER,
portCopyStatus
RowStatus
}
PortCopyEntry ::= SEQUENCE {
portCopySource
InterfaceIndex,
portCopyDest
InterfaceIndex,
portCopyDestDropEvents
Counter32,
portCopyDirection
INTEGER,
portCopyStatus
RowStatus
}
portCopySource OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex of the source which will have all packets
redirected to the destination as defined by portCopyDest."
::= { portCopyEntry 1 }
portCopySource OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex of the source which will have all packets
redirected to the destination as defined by portCopyDest."
::= { portCopyEntry 1 }
portCopyDest OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the ifIndex destination for the copy operation."
::= { portCopyEntry 2 }
portCopyDest OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the ifIndex destination for the copy operation."
::= { portCopyEntry 2 }
portCopyDestDropEvents OBJECT-TYPE SYNTAX Counter32 UNITS "events" MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of events in which port copy packets were dropped by the switch at the destination port due to lack of resources.
portCopyDestDropEvents对象类型语法计数器32个单元“事件”MAX-ACCESS只读状态当前描述“由于缺少资源，交换机在目标端口丢弃端口副本数据包的事件总数。
Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
注意，这个数字不一定是丢弃的数据包的数量；这只是检测到这种情况的次数。
A single dropped event counter is maintained for each
portCopyDest. Thus all instances associated with a given
portCopyDest will have the same portCopyDestDropEvents
value."
::= { portCopyEntry 3 }
A single dropped event counter is maintained for each
portCopyDest. Thus all instances associated with a given
portCopyDest will have the same portCopyDestDropEvents
value."
::= { portCopyEntry 3 }
portCopyDirection OBJECT-TYPE
SYNTAX INTEGER {
copyRxOnly(1),
copyTxOnly(2),
copyBoth(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object affects the way traffic is copied from a switch
source port, for the indicated port copy operation.
portCopyDirection OBJECT-TYPE
SYNTAX INTEGER {
copyRxOnly(1),
copyTxOnly(2),
copyBoth(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object affects the way traffic is copied from a switch
source port, for the indicated port copy operation.
If this object has the value 'copyRxOnly(1)', then only traffic received on the indicated source port will be copied to the indicated destination port.
如果此对象的值为“copyRxOnly（1）”，则只有在指定的源端口上接收到的流量才会复制到指定的目标端口。
If this object has the value 'copyTxOnly(2)', then only traffic transmitted out the indicated source port will be copied to the indicated destination port.
如果此对象的值为“copyTxOnly（2）”，则只有从指示的源端口传输的流量才会复制到指示的目标端口。
If this object has the value 'copyBoth(3)', then all traffic received or transmitted on the indicated source port will be copied to the indicated destination port.
如果此对象的值为“copyBoth（3）”，则在指定的源端口上接收或传输的所有通信量都将复制到指定的目标端口。
The creation and deletion of instances of this object is
controlled by the portCopyRowStatus object. Note that there
is no guarantee that changes in the value of this object
performed while the associated portCopyRowStatus object is
equal to active will not cause traffic discontinuities in the
packet stream."
DEFVAL { copyBoth }
::= { portCopyEntry 4 }
The creation and deletion of instances of this object is
controlled by the portCopyRowStatus object. Note that there
is no guarantee that changes in the value of this object
performed while the associated portCopyRowStatus object is
equal to active will not cause traffic discontinuities in the
packet stream."
DEFVAL { copyBoth }
::= { portCopyEntry 4 }
portCopyStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Defines the status of the port copy entry.
portCopyStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“定义端口复制条目的状态。
In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'.
为了配置源到目标portCopy关系，源和目标接口必须作为ifTable中的ifEntry出现，并且它们各自的ifAdminStatus和ifOperStatus值必须等于“up（1）”。如果在激活portCopyEntry后这两个对象中的任何一个的值发生更改，portCopyStatus将转换为“notReady（3）”。
The capability of an interface to be source or destination of
a port copy operation is described by the 'copySourcePort(0)'
and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits
SHOULD be appropriately set by the agent, in order to allow
for a portCopyEntry to be created."
::= { portCopyEntry 5 }
The capability of an interface to be source or destination of
a port copy operation is described by the 'copySourcePort(0)'
and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits
SHOULD be appropriately set by the agent, in order to allow
for a portCopyEntry to be created."
::= { portCopyEntry 5 }
-- smonRegistrationPoints
-- defines a set of OIDs for registration purposes of entities
-- supported by the SMON MIB.
-- smonRegistrationPoints
-- defines a set of OIDs for registration purposes of entities
-- supported by the SMON MIB.
smonVlanDataSource
smonVlanDataSource
OBJECT IDENTIFIER ::= { smonRegistrationPoints 1}
OBJECT IDENTIFIER ::= { smonRegistrationPoints 1}
-- Defined for use as an SmonDataSource. A single integer parameter
-- is appended to the end of this OID when actually encountered in
-- the dataSourceCapsTable, which represents a positive, non-zero
-- VLAN identifier value.
-- Defined for use as an SmonDataSource. A single integer parameter
-- is appended to the end of this OID when actually encountered in
-- the dataSourceCapsTable, which represents a positive, non-zero
-- VLAN identifier value.
-- Conformance Macros
--一致性宏
smonMIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 3}
smonMIBGroups OBJECT IDENTIFIER ::= { rmonConformance 4}
smonMIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 3}
smonMIBGroups OBJECT IDENTIFIER ::= { rmonConformance 4}
smonMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for full conformance with the SMON MIB" MODULE -- this module MANDATORY-GROUPS {dataSourceCapsGroup, smonVlanStatsGroup, smonPrioStatsGroup, portCopyConfigGroup, smonInformationGroup}
SMONMIB COMPLIANCE MODULE-COMPLIANCE STATUS current DESCRIPTION“描述与SMON MIB完全一致性的要求”模块——此模块为必填组{dataSourceCapsGroup、smonVlanStatsGroup、smonPrioStatsGroup、portCopyConfigGroup、smonInformationGroup}
GROUP smonHcTo100mbGroup DESCRIPTION "This group of VLAN statistics counter are mandatory only for those network interfaces for which the corresponding ifSpeed can be greater than 10MB/sec and less than or equal to 100MB/sec."
GROUP smonHcTo100mbGroup DESCRIPTION“此组VLAN统计计数器仅对相应的ifSpeed可以大于10MB/sec且小于或等于100MB/sec的网络接口是必需的。”
GROUP smonHc100mbPlusGroup DESCRIPTION "This group of VLAN statistics counters are mandatory only for those network interfaces for which the corresponding ifSpeed can be more than 100MB/sec. This group of VLAN statistics is also mandatory for smonDataSources of type VLAN or entPhysicalEntry."
GROUP smonHc100mbPlusGroup DESCRIPTION“此组VLAN统计计数器仅对于相应的ifSpeed可以超过100MB/sec的网络接口是必需的。此组VLAN统计数据对于VLAN或entPhysicalEntry类型的SMONDataSource也是必需的。”
::= { smonMIBCompliances 1 }
::= { smonMIBCompliances 1 }
smonMIBVlanStatsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance with the SMON MIB with support for VLAN Statistics. Mandatory for a SMON probe in environment where IEEE 802.1Q bridging is implemented." MODULE -- this module
smonMIBVlanStatsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“描述与SMON MIB的一致性要求，并支持VLAN统计信息。对于实施IEEE 802.1Q桥接的环境中的SMON探测器来说，这是强制性的。”MODULE——此模块
MANDATORY-GROUPS {dataSourceCapsGroup, smonVlanStatsGroup, smonInformationGroup} GROUP hcVlanTo100mbGroup DESCRIPTION "This group of VLAN statistics counter are mandatory only for those network interfaces for which the corresponding ifSpeed can be up to and including 100MB/sec."
MANDATORY-GROUPS{dataSourceCapsGroup，smonVlanStatsGroup，smonInformationGroup}grouphcvlanto100mbgroup DESCRIPTION“这组VLAN统计计数器仅对于相应的ifSpeed可以达到并包括100MB/sec的网络接口是必需的。”
GROUP hcVlan100mbPlusGroup DESCRIPTION "This group of VLAN statistics counters are mandatory only for those network interfaces for which the corresponding ifSpeed is greater than 100MB/sec. This group of VLAN statistics is also mandatory for smonDataSources of type VLAN or entPhysicalEntry."
组hcVlan100mbPlusGroup DESCRIPTION“此组VLAN统计计数器仅对相应的ifSpeed大于100MB/sec的网络接口是必需的。此组VLAN统计数据对VLAN或entPhysicalEntry类型的Smondatasource也是必需的。”
::= { smonMIBCompliances 2 }
::= { smonMIBCompliances 2 }
smonMIBPrioStatsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance with the SMON MIB with support for priority level Statistics. Mandatory for a SMON probe in a environment where IEEE 802.1p priority-switching is implemented." MODULE -- this module MANDATORY-GROUPS {dataSourceCapsGroup, smonPrioStatsGroup, smonInformationGroup}
smonMIBPrioStatsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“描述了与SMON MIB的一致性要求，并支持优先级统计信息。在实施IEEE 802.1p优先级切换的环境中，SMON探测器必须满足此要求。”MODULE--此模块必须满足以下条件：{dataSourceCapsGroup，smonPrioStatsGroup，smonInformationGroup}
GROUP hcPrioTo100mbGroup DESCRIPTION "This group of VLAN priority statistics counters are mandatory only for those network interfaces for which the corresponding ifSpeed can be up to and including 100MB/sec."
GROUP hcPrioTo100mbGroup DESCRIPTION“这组VLAN优先级统计计数器仅对于相应的ifSpeed可以达到并包括100MB/sec的网络接口是必需的。”
GROUP hcPrio100mbPlusGroup DESCRIPTION "This group is mandatory only for those network interfaces for which the corresponding ifSpeed is greater than 100MB/sec. This group of VLAN priority statistics is also mandatory for smonDataSources of type VLAN or entPhysicalEntry"
GROUP hcPrio100mbPlusGroup DESCRIPTION“此组仅对相应ifSpeed大于100MB/sec的网络接口是必需的。此组VLAN优先级统计信息对于VLAN或entPhysicalEntry类型的Smondatasource也是必需的”
::= { smonMIBCompliances 3 }
::= { smonMIBCompliances 3 }
portCopyCompliance MODULE-COMPLIANCE
portCopyCompliance模块-符合性
STATUS current DESCRIPTION "Describes the requirements for conformance with the port copy functionality defined by the SMON MIB" MODULE -- this module MANDATORY-GROUPS {dataSourceCapsGroup, portCopyConfigGroup, smonInformationGroup}
STATUS current DESCRIPTION“描述了与SMON MIB模块定义的端口复制功能一致性的要求——此模块是必需的—组{dataSourceCapsGroup、portCopyConfigGroup、smonInformationGroup}
::= { smonMIBCompliances 4}
::= { smonMIBCompliances 4}
dataSourceCapsGroup OBJECT-GROUP
OBJECTS { dataSourceRmonCaps,
dataSourceCopyCaps,
dataSourceCapsIfIndex}
STATUS current
DESCRIPTION
"Defines the objects that describe the capabilities of RMON
data sources."
::= {smonMIBGroups 1 }
dataSourceCapsGroup OBJECT-GROUP
OBJECTS { dataSourceRmonCaps,
dataSourceCopyCaps,
dataSourceCapsIfIndex}
STATUS current
DESCRIPTION
"Defines the objects that describe the capabilities of RMON
data sources."
::= {smonMIBGroups 1 }
smonVlanStatsGroup OBJECT-GROUP
OBJECTS { smonVlanStatsControlDataSource,
smonVlanStatsControlCreateTime,
smonVlanStatsControlOwner,
smonVlanStatsControlStatus,
smonVlanIdStatsTotalPkts,
smonVlanIdStatsTotalOctets,
smonVlanIdStatsNUcastPkts,
smonVlanIdStatsCreateTime}
STATUS current
DESCRIPTION
"Defines the switch monitoring specific statistics - per VLAN
Id on interfaces of 10MB or less."
::= { smonMIBGroups 2 }
smonVlanStatsGroup OBJECT-GROUP
OBJECTS { smonVlanStatsControlDataSource,
smonVlanStatsControlCreateTime,
smonVlanStatsControlOwner,
smonVlanStatsControlStatus,
smonVlanIdStatsTotalPkts,
smonVlanIdStatsTotalOctets,
smonVlanIdStatsNUcastPkts,
smonVlanIdStatsCreateTime}
STATUS current
DESCRIPTION
"Defines the switch monitoring specific statistics - per VLAN
Id on interfaces of 10MB or less."
::= { smonMIBGroups 2 }
smonPrioStatsGroup OBJECT-GROUP OBJECTS { smonPrioStatsControlDataSource, smonPrioStatsControlCreateTime, smonPrioStatsControlOwner, smonPrioStatsControlStatus, smonPrioStatsPkts, smonPrioStatsOctets} STATUS current DESCRIPTION "Defines the switch monitoring specific statistics - per VLAN Id on interface."
smonPrioStatsGroup对象组对象{smonPrioStatsControlDataSource，smonPrioStatsControlCreateTime，smonPrioStatsControlOwner，smonPrioStatsControlStatus，smonPrioStatsPkts，SMonPriostatsSoctes}状态当前描述“定义交换机监控特定的统计信息-每个接口上的VLAN Id。”
::= { smonMIBGroups 3 }
::= { smonMIBGroups 3 }
smonHcTo100mbGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity statistics needed to be
kept on interfaces with ifSpeed greater than 10MB/sec and
less than or equal to 100MB/sec."
::= { smonMIBGroups 4 }
smonHcTo100mbGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity statistics needed to be
kept on interfaces with ifSpeed greater than 10MB/sec and
less than or equal to 100MB/sec."
::= { smonMIBGroups 4 }
smonHc100mbPlusGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowPkts,
smonVlanIdStatsTotalHCPkts,
smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets,
smonVlanIdStatsNUcastOverflowPkts,
smonVlanIdStatsNUcastHCPkts,
smonPrioStatsOverflowPkts,
smonPrioStatsHCPkts,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity statistics needed to be
kept on interfaces with ifSpeed of more than 100MB/sec. These
statistics MUST also be kept on smonDataSources of type VLAN
or entPhysicalEntry."
::= { smonMIBGroups 5 }
smonHc100mbPlusGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowPkts,
smonVlanIdStatsTotalHCPkts,
smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets,
smonVlanIdStatsNUcastOverflowPkts,
smonVlanIdStatsNUcastHCPkts,
smonPrioStatsOverflowPkts,
smonPrioStatsHCPkts,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity statistics needed to be
kept on interfaces with ifSpeed of more than 100MB/sec. These
statistics MUST also be kept on smonDataSources of type VLAN
or entPhysicalEntry."
::= { smonMIBGroups 5 }
hcVlanTo100mbGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN statistics
needed to be kept on interfaces with ifSpeed greater than
10MB/sec and less than or equal to 100MB/sec."
::= { smonMIBGroups 6 }
hcVlanTo100mbGroup OBJECT-GROUP
OBJECTS { smonVlanIdStatsTotalOverflowOctets,
smonVlanIdStatsTotalHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN statistics
needed to be kept on interfaces with ifSpeed greater than
10MB/sec and less than or equal to 100MB/sec."
::= { smonMIBGroups 6 }
hcVlan100mbPlusGroup OBJECT-GROUP OBJECTS { smonVlanIdStatsTotalOverflowPkts, smonVlanIdStatsTotalHCPkts, smonVlanIdStatsTotalOverflowOctets, smonVlanIdStatsTotalHCOctets,
hcVlan100mbPlusGroup对象组对象{smonVlanIdStatsTotalOverflowPkts，smonVlanIdStatsTotalHCPkts，smonVlanIdStatsTotalOverflowOctets，SMONVLANIDStatsTotalHctets，
smonVlanIdStatsNUcastOverflowPkts,
smonVlanIdStatsNUcastHCPkts}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN statistics
needed to be kept on interfaces with ifSpeed of more than
100MB/sec. These statistics MUST also be kept on
smonDataSources of type VLAN or entPhysicalEntry."
::= { smonMIBGroups 7 }
smonVlanIdStatsNUcastOverflowPkts,
smonVlanIdStatsNUcastHCPkts}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN statistics
needed to be kept on interfaces with ifSpeed of more than
100MB/sec. These statistics MUST also be kept on
smonDataSources of type VLAN or entPhysicalEntry."
::= { smonMIBGroups 7 }
hcPrioTo100mbGroup OBJECT-GROUP
OBJECTS { smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets }
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN priority
statistics needed to be kept on interfaces with
ifSpeed of greater than 10MB/sec and less than or equal
to 100MB/sec."
::= { smonMIBGroups 8 }
hcPrioTo100mbGroup OBJECT-GROUP
OBJECTS { smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets }
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN priority
statistics needed to be kept on interfaces with
ifSpeed of greater than 10MB/sec and less than or equal
to 100MB/sec."
::= { smonMIBGroups 8 }
hcPrio100mbPlusGroup OBJECT-GROUP
OBJECTS { smonPrioStatsOverflowPkts,
smonPrioStatsHCPkts,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN priority
statistics needed to be kept on interfaces with
ifSpeed of greater than 100MB/sec. These statistics MUST
also be kept on smonDataSources of type VLAN or
entPhysicalEntry."
::= { smonMIBGroups 9 }
hcPrio100mbPlusGroup OBJECT-GROUP
OBJECTS { smonPrioStatsOverflowPkts,
smonPrioStatsHCPkts,
smonPrioStatsOverflowOctets,
smonPrioStatsHCOctets}
STATUS current
DESCRIPTION
"Defines the additional high capacity VLAN priority
statistics needed to be kept on interfaces with
ifSpeed of greater than 100MB/sec. These statistics MUST
also be kept on smonDataSources of type VLAN or
entPhysicalEntry."
::= { smonMIBGroups 9 }
smonVlanStatsExtGroup OBJECT-GROUP
OBJECTS {smonVlanIdStatsNUcastOctets,
smonVlanIdStatsNUcastOverflowOctets,
smonVlanIdStatsNUcastHCOctets}
STATUS current
DESCRIPTION
"Defines the switch monitoring specific statistics for systems
capable of counting non-unicast octets for a given dataSource
(as described in the dataSourceRmonCaps object)."
::= { smonMIBGroups 10 }
smonVlanStatsExtGroup OBJECT-GROUP
OBJECTS {smonVlanIdStatsNUcastOctets,
smonVlanIdStatsNUcastOverflowOctets,
smonVlanIdStatsNUcastHCOctets}
STATUS current
DESCRIPTION
"Defines the switch monitoring specific statistics for systems
capable of counting non-unicast octets for a given dataSource
(as described in the dataSourceRmonCaps object)."
::= { smonMIBGroups 10 }
smonInformationGroup OBJECT-GROUP OBJECTS { smonCapabilities }
smonInformationGroup对象组对象{smonCapabilities}
STATUS current
DESCRIPTION
"An indication of the SMON capabilities supported by this
agent."
::= { smonMIBGroups 11 }
STATUS current
DESCRIPTION
"An indication of the SMON capabilities supported by this
agent."
::= { smonMIBGroups 11 }
portCopyConfigGroup OBJECT-GROUP
OBJECTS { portCopyDestDropEvents,
portCopyDirection,
portCopyStatus
}
STATUS current
DESCRIPTION
"Defines the control objects for copy port operations."
::= { smonMIBGroups 12 }
portCopyConfigGroup OBJECT-GROUP
OBJECTS { portCopyDestDropEvents,
portCopyDirection,
portCopyStatus
}
STATUS current
DESCRIPTION
"Defines the control objects for copy port operations."
::= { smonMIBGroups 12 }
END
终止
[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] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] SNMPv2 Working Group, 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] SNMPv2工作组，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 for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型”，RFC 2574，1999年4月。
[13] SNMPv2 Working Group, 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] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[14] Levi，D.，Meyer，P.，和B.Stewart，“SNMP应用”，RFC2573，1999年4月。
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[15] Wijnen，B.，Presuhn，R.，和K.McCloghrie，“简单网络管理协议（SNMP）基于视图的访问控制模型”，RFC2575，1999年4月。
[16] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[16] Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，RFC 2021，1997年1月。
[17] Waldbusser, S., "Remote Network Monitoring Management Information Base", RFC 1757, February 1995.
[17] Waldbusser，S.，“远程网络监控管理信息库”，RFC 1757，1995年2月。
[18] McCloghrie, K. and A. Bierman, "Entity MIB", RFC 2037, October 1996.
[18] McCloghrie，K.和A.Bierman，“实体MIB”，RFC 2037，1996年10月。
[19] ISO/IEC Final CD 15802-3, ANSI/IEEE Std 802.1D-1998 "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Media Access Control (MAC) Bridges: Revision (Incorporating IEEE P802.1p: Traffic Class Expediting and Dynamic Multicast Filtering)", March 1998.
[19] ISO/IEC最终CD 15802-3，ANSI/IEEE Std 802.1D-1998“信息技术-系统间电信和信息交换-局域网和城域网-通用规范-第3部分：媒体访问控制（MAC）网桥：修订版（包括IEEE P802.1p：流量等级加速和动态多播过滤）”，1998年3月。
[20] ANSI/IEEE Draft Standard P802.1Q/D10, "IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks", March 1998.
[20] ANSI/IEEE标准草案P802.1Q/D10，“局域网和城域网的IEEE标准：虚拟桥接局域网”，1998年3月。
[21] De Graaf, K., Romascanu, D., McMaster, D. and K. McCloghrie, "Definition of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, February 1997.
[21] De Graaf，K.，Romascan，D.，McMaster，D.和K.McCloghrie，“使用SMIv2的IEEE 802.3中继器设备的管理对象定义”，RFC 2108，1997年2月。
[22] McCloghrie, K. and F. Kastenholz," The Interfaces Group MIB using SMIv2", RFC 2233, November 1997.
[22] McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 2233，1997年11月。
[23] Decker, E. Langille, P., Rijsinghani, A. and K. McCloghrie.. - "Definitions of Managed Objects for Bridges", RFC 1493, July 1993
[23] Decker、E.Langille、P.Rijsinghani、A.和K.McCloghrie.——“桥梁管理对象的定义”，RFC 1493，1993年7月
[24] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[24] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[25] 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.
[25] McCloghrie，K.和M.Rose，编辑，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
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中有许多托管对象可能包含敏感信息。这些是：
smonCapabilities dataSourceCapsTable portCopyTable
smonCapabilities数据源CapsTable portCopyTable
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 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实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
Richard Waterman Allot Communications 292 E. Main St. Los Gatos, CA. 95030 USA
Richard Waterman Allot Communications 292 E.Main St.Los Gatos，约美国95030
Phone: +1-408-399-3154
EMail: rich@allot.com
Phone: +1-408-399-3154
EMail: rich@allot.com
Bill Lahaye Xylan Corporation 26707 W. Agoura Rd. Calabasas, CA 91302 USA
美国加利福尼亚州卡拉巴萨斯市阿古拉西路26707号比尔·拉哈耶·西兰公司，邮编：91302
Phone: +1-800-995-2612 EMail bill.lahaye@xylan.com
电话：+1-800-995-2612电子邮件账单。lahaye@xylan.com
Dan Romascanu Lucent Technologies Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel
Dan Romascanu Lucent Technologies Atidim技术园，特拉维夫3号楼，以色列61131
Phone: +972-3-645-8414
EMail: dromasca@lucent.com
Phone: +972-3-645-8414
EMail: dromasca@lucent.com
Steven Waldbusser International Network Services (INS) 1213 Innsbruck Dr. Sunnyvale, CA 94089
Steven Waldbusser国际网络服务（INS）1213因斯布鲁克Sunnyvale博士，加利福尼亚州94089
Phone: +1-650-318-1251
EMail: waldbusser@ins.com
Phone: +1-650-318-1251
EMail: waldbusser@ins.com
A. Full Copyright Statement
A.完整的版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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编辑功能的资金目前由互联网协会提供。