Network Working Group F. Baker
Request for Comments: 3289 Cisco System
Category: Standards Track K. Chan
Nortel Networks
A. Smith
Harbour Networks
May 2002
Network Working Group F. Baker
Request for Comments: 3289 Cisco System
Category: Standards Track K. Chan
Nortel Networks
A. Smith
Harbour Networks
May 2002
Management Information Base for the Differentiated Services Architecture
区分服务体系结构的管理信息库
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 (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This memo describes an SMIv2 (Structure of Management Information version 2) MIB for a device implementing the Differentiated Services Architecture. It may be used both for monitoring and configuration of a router or switch capable of Differentiated Services functionality.
本备忘录描述了用于实现区分服务体系结构的设备的SMIv2（管理信息结构版本2）MIB。它可以用于监控和配置能够实现区分服务功能的路由器或交换机。
Table of Contents
目录
1 The SNMP Management Framework ................................. 3
2 Relationship to other working group documents ................. 4
2.1 Relationship to the Informal Management Model for
Differentiated Services Router ............................. 4
2.2 Relationship to other MIBs and Policy Management ............ 5
3 MIB Overview .................................................. 6
3.1 Processing Path ............................................. 7
3.1.1 diffServDataPathTable - The Data Path Table ............... 7
3.2 Classifier .................................................. 7
3.2.1 diffServClfrElementTable - The Classifier Element Table ... 8
3.2.2 diffServMultiFieldClfrTable - The Multi-field Classifier
Table ...................................................... 9
3.3 Metering Traffic ............................................ 10
3.3.1 diffServMeterTable - The Meter Table ...................... 11
1 The SNMP Management Framework ................................. 3
2 Relationship to other working group documents ................. 4
2.1 Relationship to the Informal Management Model for
Differentiated Services Router ............................. 4
2.2 Relationship to other MIBs and Policy Management ............ 5
3 MIB Overview .................................................. 6
3.1 Processing Path ............................................. 7
3.1.1 diffServDataPathTable - The Data Path Table ............... 7
3.2 Classifier .................................................. 7
3.2.1 diffServClfrElementTable - The Classifier Element Table ... 8
3.2.2 diffServMultiFieldClfrTable - The Multi-field Classifier
Table ...................................................... 9
3.3 Metering Traffic ............................................ 10
3.3.1 diffServMeterTable - The Meter Table ...................... 11
3.3.2 diffServTBParamTable - The Token Bucket Parameters Table... 11
3.4 Actions applied to packets .................................. 12
3.4.1 diffServActionTable - The Action Table .................... 12
3.4.2 diffServCountActTable - The Count Action Table ............ 12
3.4.3 diffServDscpMarkActTable - The Mark Action Table .......... 13
3.4.4 diffServAlgDropTable - The Algorithmic Drop Table ......... 13
3.4.5 diffServRandomDropTable - The Random Drop Parameters Table 14
3.5 Queuing and Scheduling of Packets ........................... 16
3.5.1 diffServQTable - The Class or Queue Table ................. 16
3.5.2 diffServSchedulerTable - The Scheduler Table .............. 16
3.5.3 diffServMinRateTable - The Minimum Rate Table ............. 16
3.5.4 diffServMaxRateTable - The Maximum Rate Table ............. 17
3.5.5 Using queues and schedulers together ...................... 17
3.6 Example configuration for AF and EF ......................... 20
3.6.1 AF and EF Ingress Interface Configuration ................. 20
3.6.1.1 Classification In The Example ........................... 22
3.6.1.2 AF Implementation On an Ingress Edge Interface .......... 22
3.6.1.2.1 AF Metering On an Ingress Edge Interface .............. 22
3.6.1.2.2 AF Actions On an Ingress Edge Interface ............... 23
3.6.1.3 EF Implementation On an Ingress Edge Interface .......... 23
3.6.1.3.1 EF Metering On an Ingress Edge Interface .............. 23
3.6.1.3.2 EF Actions On an Ingress Edge Interface ............... 23
3.7 AF and EF Egress Edge Interface Configuration ............... 24
3.7.1 Classification On an Egress Edge Interface ................ 24
3.7.2 AF Implementation On an Egress Edge Interface ............. 26
3.7.2.1 AF Metering On an Egress Edge Interface ................. 26
3.7.2.2 AF Actions On an Egress Edge Interface .................. 29
3.7.2.3 AF Rate-based Queuing On an Egress Edge Interface ....... 30
3.7.3 EF Implementation On an Egress Edge Interface ............. 30
3.7.3.1 EF Metering On an Egress Edge Interface ................. 30
3.7.3.2 EF Actions On an Egress Edge Interface .................. 30
3.7.3.3 EF Priority Queuing On an Egress Edge Interface ......... 32
4 Conventions used in this MIB .................................. 33
4.1 The use of RowPointer to indicate data path linkage ......... 33
4.2 The use of RowPointer to indicate parameters ................ 34
4.3 Conceptual row creation and deletion ........................ 34
5 Extending this MIB ............................................ 35
6 MIB Definition ................................................ 35
7 Acknowledgments ............................................... 110
8 Security Considerations ....................................... 110
9 Intellectual Property Rights .................................. 111
10 References ................................................... 112
11 Authors' Addresses ........................................... 115
12 Full Copyright Statement ..................................... 116
3.3.2 diffServTBParamTable - The Token Bucket Parameters Table... 11
3.4 Actions applied to packets .................................. 12
3.4.1 diffServActionTable - The Action Table .................... 12
3.4.2 diffServCountActTable - The Count Action Table ............ 12
3.4.3 diffServDscpMarkActTable - The Mark Action Table .......... 13
3.4.4 diffServAlgDropTable - The Algorithmic Drop Table ......... 13
3.4.5 diffServRandomDropTable - The Random Drop Parameters Table 14
3.5 Queuing and Scheduling of Packets ........................... 16
3.5.1 diffServQTable - The Class or Queue Table ................. 16
3.5.2 diffServSchedulerTable - The Scheduler Table .............. 16
3.5.3 diffServMinRateTable - The Minimum Rate Table ............. 16
3.5.4 diffServMaxRateTable - The Maximum Rate Table ............. 17
3.5.5 Using queues and schedulers together ...................... 17
3.6 Example configuration for AF and EF ......................... 20
3.6.1 AF and EF Ingress Interface Configuration ................. 20
3.6.1.1 Classification In The Example ........................... 22
3.6.1.2 AF Implementation On an Ingress Edge Interface .......... 22
3.6.1.2.1 AF Metering On an Ingress Edge Interface .............. 22
3.6.1.2.2 AF Actions On an Ingress Edge Interface ............... 23
3.6.1.3 EF Implementation On an Ingress Edge Interface .......... 23
3.6.1.3.1 EF Metering On an Ingress Edge Interface .............. 23
3.6.1.3.2 EF Actions On an Ingress Edge Interface ............... 23
3.7 AF and EF Egress Edge Interface Configuration ............... 24
3.7.1 Classification On an Egress Edge Interface ................ 24
3.7.2 AF Implementation On an Egress Edge Interface ............. 26
3.7.2.1 AF Metering On an Egress Edge Interface ................. 26
3.7.2.2 AF Actions On an Egress Edge Interface .................. 29
3.7.2.3 AF Rate-based Queuing On an Egress Edge Interface ....... 30
3.7.3 EF Implementation On an Egress Edge Interface ............. 30
3.7.3.1 EF Metering On an Egress Edge Interface ................. 30
3.7.3.2 EF Actions On an Egress Edge Interface .................. 30
3.7.3.3 EF Priority Queuing On an Egress Edge Interface ......... 32
4 Conventions used in this MIB .................................. 33
4.1 The use of RowPointer to indicate data path linkage ......... 33
4.2 The use of RowPointer to indicate parameters ................ 34
4.3 Conceptual row creation and deletion ........................ 34
5 Extending this MIB ............................................ 35
6 MIB Definition ................................................ 35
7 Acknowledgments ............................................... 110
8 Security Considerations ....................................... 110
9 Intellectual Property Rights .................................. 111
10 References ................................................... 112
11 Authors' Addresses ........................................... 115
12 Full Copyright Statement ..................................... 116
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in [RFC 2571].
o [RFC 2571]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and is described in [RFC 1155], [RFC 1212] and [RFC 1215]. The second version, called SMIv2, is described in [RFC 2578], RFC 2579 [RFC 2579] and [RFC 2580].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在[RFC 1155]、[RFC 1212]和[RFC 1215]中进行了描述。第二个版本称为SMIv2，在[RFC 2578]、RFC 2579[RFC 2579]和[RFC 2580]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and is described in [RFC 1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and is described in [RFC 1901] and [RFC 1906]. The third version of the message protocol is called SNMPv3 and is described in [RFC 1906], [RFC 2572] and [RFC 2574].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在[RFC 1157]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，并在[RFC 1901]和[RFC 1906]中描述。消息协议的第三个版本称为SNMPv3，并在[RFC 1906]、[RFC 2572]和[RFC 2574]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in [RFC 1157]. A second set of protocol operations and associated PDU formats is described in [RFC 1905].
o 访问管理信息的协议操作。[RFC 1157]中描述了第一组协议操作和相关PDU格式。[RFC 1905]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in [RFC 2573] and the view-based access control mechanism described in [RFC 2575].
o [RFC 2573]中描述的一组基本应用程序和[RFC 2575]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in [RFC 2570].
有关当前SNMP管理框架的更详细介绍，请参见[RFC 2570]。
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 there is no translation is possible (use of Counter64). Some machine-readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法进行翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC 2119]中所述进行解释。
The Differentiated Services Working Group and related working groups developed other documents, notably the Informal Management Model and the policy configuration paradigm of SNMPCONF. The relationship between the MIB and those documents is clarified here.
差异化服务工作组和相关工作组制定了其他文件，特别是SNMPCONF的非正式管理模式和政策配置范式。MIB和这些文档之间的关系在这里得到了澄清。
2.1. Relationship to the Informal Management Model for Differentiated Services Router
2.1. 与区分服务路由器非正式管理模型的关系
This MIB is similar in design to [MODEL], although it can be used to build functional data paths that the model would not well describe. The model conceptually describes ingress and egress interfaces of an n-port router, which may find some interfaces at a network edge and others facing into the network core. It describes the configuration and management of a Differentiated Services interface in terms of one or more Traffic Conditioning Blocks (TCB), each containing, arranged in the specified order, by definition, zero or more classifiers, meters, actions, algorithmic droppers, queues and schedulers. Traffic may be classified, and classified traffic may be metered. Each stream of traffic identified by a combination of classifiers and meters may have some set of actions performed on it; it may have dropping algorithms applied and it may ultimately be stored into a queue before being scheduled out to its next destination, either onto a link or to another TCB. At times, the treatment for a given packet must have any of those elements repeated. [MODEL] models this by cascading multiple TCBs, while this MIB describes the policy by directly linking the functional data path elements.
该MIB在设计上与[MODEL]类似，尽管它可以用于构建模型无法很好描述的功能数据路径。该模型从概念上描述了n端口路由器的入口和出口接口，其中一些接口位于网络边缘，而另一些接口则朝向网络核心。它以一个或多个流量调节块（TCB）的形式描述区分服务接口的配置和管理，根据定义，每个TCB包含零个或多个分类器、仪表、动作、算法拖放器、队列和调度程序，并按指定顺序排列。可对交通进行分类，并对分类交通进行计量。由分类器和仪表组合识别的每个流量流可能具有对其执行的一些动作集；它可能应用了丢弃算法，并且在被调度到下一个目的地（链路或另一个TCB）之前，它可能最终被存储到队列中。有时，对给定数据包的处理必须重复这些元素中的任何一个。[MODEL]通过级联多个TCB对此进行建模，而此MIB通过直接链接功能数据路径元素来描述策略。
The MIB represents this cascade by following the "Next" attributes of the various elements. They indicate what the next step in Differentiated Services processing will be, whether it be a classifier, meter, action, algorithmic dropper, queue, scheduler or a decision to now forward a packet.
MIB通过遵循各个元素的“Next”属性来表示这个级联。它们指出了区分服务处理的下一步是什么，无论是分类器、计量器、操作、算法滴管、队列、调度器还是现在转发数据包的决定。
The higher level concept of a TCB is not required in the parameterization or in the linking together of the individual elements, hence it is not used in the MIB itself and is only mentioned in the text for relating the MIB with the [MODEL]. Rather, the MIB models the individual elements that make up the TCBs.
TCB的更高级别概念在参数化或单个元素的链接中不需要，因此它不用于MIB本身，仅在文本中提及，用于将MIB与[MODEL]关联。相反，MIB对组成TCB的各个元素进行建模。
This MIB uses the notion of a Data Path to indicate the Differentiated Services processing a packet may experience. The Data Path a packet will initially follow is an attribute of the interface
此MIB使用数据路径的概念来指示处理数据包可能遇到的差异化服务。数据包最初将遵循的数据路径是接口的一个属性
in question. The Data Path Table provides a starting point for each direction (ingress or egress) on each interface. A Data Path Table Entry indicates the first of possible multiple elements that will apply Differentiated Services treatment to the packet.
有疑问数据路径表为每个接口上的每个方向（入口或出口）提供了一个起点。数据路径表条目指示将对分组应用区分服务处理的多个可能元素中的第一个。
This MIB provides for direct reporting and manipulation of detailed functional elements. These elements consist of a structural element and one or more parameter-bearing elements. While this can be cumbersome, it allows the reuse of parameters. For example, a service provider may offer three varieties of contracts, and configure three parameter elements. Each such data path on the system may then refer to these sets of parameters. The diffServDataPathTable couples each direction on each interface with the specified data path linkage. The concept of "interface" is as defined by InterfaceIndex/ifIndex of the IETF Interfaces MIB [IF-MIB].
该MIB提供了详细功能元素的直接报告和操作。这些元件由一个结构元件和一个或多个参数承载元件组成。虽然这可能很麻烦，但它允许重用参数。例如，服务提供商可以提供三种类型的合同，并配置三个参数元素。然后，系统上的每个这样的数据路径可以引用这些参数集。diffServDataPathTable将每个接口上的每个方向与指定的数据路径链接进行耦合。“接口”的概念由IETF接口MIB[IF-MIB]的InterfaceIndex/ifIndex定义。
Other MIBs and data structure definitions for policy management mechanisms, other than SNMP/SMIv2 are likely to exist in the future for the purpose of abstracting the model in other ways. An example is the Differentiated Services Policy Information Base, [DSPIB].
出于以其他方式抽象模型的目的，除了SNMP/SMIv2之外，策略管理机制的其他MIB和数据结构定义将来可能存在。区分服务策略信息库[DSPIB]就是一个例子。
In particular, abstractions in the direction of less detailed definitions of Differentiated Services functionality are likely e.g. some form of "Per-Hop Behavior"-based definition involving a template of detailed object values which is applied to specific instances of objects in this MIB semi-automatically.
特别是，在区分服务功能的不太详细的定义方向上的抽象可能是，例如，某种形式的基于“每跳行为”的定义，涉及详细对象值的模板，该模板半自动应用于该MIB中对象的特定实例。
Another possible direction of abstraction is one using a concept of "roles" (often, but not always, applied to interfaces). In this case, it may be possible to re-use the object definitions in this MIB, especially the parameterization tables. The Data Path table will help in the reuse of the data path linkage tables by having the interface specific information centralized, allowing easier mechanical replacement of ifIndex by some sort of "roleIndex". This work is ongoing.
另一个可能的抽象方向是使用“角色”概念（通常，但不总是，应用于接口）。在这种情况下，可以重用此MIB中的对象定义，尤其是参数化表。数据路径表将有助于数据路径链接表的重用，因为它集中了特定于接口的信息，允许通过某种“roleIndex”更容易地机械地替换ifIndex。这项工作正在进行中。
The reuse of parameter blocks on a variety of functional data paths is intended to simplify network management. In many cases, one could also re-use the structural elements as well; this has the unfortunate side-effect of re-using the counters, so that monitoring information is lost. For this reason, the re-use of structural elements is not generally recommended.
在各种功能数据路径上重用参数块旨在简化网络管理。在许多情况下，人们也可以重复使用结构元素；这有一个不幸的副作用，即重新使用计数器，从而丢失监控信息。因此，一般不建议重复使用结构构件。
The Differentiated Services Architecture does not specify how an implementation should be assembled. The [MODEL] describes a general approach to implementation design, or to user interface design. Its components could, however, be assembled in a different way. For example, traffic conforming to a meter might be run through a second meter, or reclassified.
区分服务体系结构没有指定如何组装实现。[模型]描述了实现设计或用户界面设计的一般方法。然而，它的部件可以用不同的方式组装。例如，符合电表要求的交通可能通过第二个电表，或重新分类。
This MIB models the same functional data path elements, allowing the network manager to assemble them in any fashion that meets the relevant policy. These data path elements include Classifiers, Meters, Actions of various sorts, Queues, and Schedulers.
此MIB为相同的功能数据路径元素建模，允许网络管理器以符合相关策略的任何方式组装它们。这些数据路径元素包括分类器、仪表、各种操作、队列和调度程序。
In many of these tables, a distinction is drawn between the structure of the policy (do this, then do that) and the parameters applied to specific policy elements. This is to facilitate configuration, if the MIB is used for that. The concept is that a set of parameters, such as the values that describe a specific token bucket, might be configured once and applied to many interfaces.
在许多这些表中，在策略的结构（做这个，然后做那个）和应用于特定策略元素的参数之间进行了区分。如果MIB用于配置，这将有助于配置。其概念是，一组参数（如描述特定令牌桶的值）可以配置一次并应用于多个接口。
The RowPointer Textual Convention is therefore used in two ways in this MIB. It is defined for the purpose of connecting an object to an entry dynamically; the RowPointer object identifies the first object in the target Entry, and in so doing points to the entire entry. In this MIB, it is used as a connector between successive functional data path elements, and as the link between the policy structure and the parameters that are used. When used as a connector, it says what happens "next"; what happens to classified traffic, to traffic conforming or not conforming to a meter, and so on. When used to indicate the parameters applied in a policy, it says "specifically" what is meant; the structure points to the parameters of its policy.
因此，在这个MIB中，行指针文本约定有两种使用方式。它是为了动态地将对象连接到条目而定义的；RowPointer对象标识目标条目中的第一个对象，并指向整个条目。在此MIB中，它用作连续功能数据路径元素之间的连接器，以及策略结构和所用参数之间的链接。当用作连接器时，它表示“下一步”会发生什么；分类交通、符合或不符合仪表的交通会发生什么情况，等等。当用于指示在策略中应用的参数时，它会“具体”说明其含义；该结构指向其政策的参数。
The use of RowPointers as connectors allows for the simple extension of the MIB. The RowPointers, whether "next" or "specific", may point to Entries defined in other MIB modules. For example, the only type of meter defined in this MIB is a token bucket meter; if another type of meter is required, another MIB could be defined describing that type of meter, and diffServMeterSpecific could point to it. Similarly, if a new action is required, the "next" pointer of the previous functional datapath element could point to an Entry defined in another MIB, public or proprietary.
使用行指针作为连接器可以简单地扩展MIB。行指针，无论是“下一个”还是“特定的”，都可以指向在其他MIB模块中定义的条目。例如，此MIB中定义的唯一类型的表是令牌桶表；如果需要另一种类型的仪表，可以定义另一个MIB来描述该类型的仪表，diffServMeterSpecific可以指向它。类似地，如果需要新操作，则前一个functional datapath元素的“next”指针可以指向另一个MIB（公共或专有）中定义的条目。
An interface has an ingress and an egress direction, and will generally have a different policy in each direction. As traffic enters an edge interface, it may be classified, metered, counted, and marked. Traffic leaving the same interface might be remarked according to the contract with the next network, queued to manage the bandwidth, and so on. As [MODEL] points out, the functional datapath elements used on ingress and egress are of the same type, but may be structured in very different ways to implement the relevant policies.
接口具有入口和出口方向，并且通常在每个方向上具有不同的策略。当流量进入边缘接口时，可以对其进行分类、计量、计数和标记。离开同一接口的流量可能会根据与下一个网络的合同进行标记，排队管理带宽，等等。正如[MODEL]所指出的，入口和出口上使用的功能性数据路径元素属于同一类型，但其结构可能与实现相关策略的方式非常不同。
Therefore, when traffic arrives at an ingress or egress interface, the first step in applying the policy is determining what policy applies. This MIB does that by providing a table of pointers to the first functional data path element, indexed by interface and direction on that interface. The content of the diffServDataPathEntry is a single RowPointer, which points to that functional data path element.
因此，当流量到达入口或出口接口时，应用策略的第一步是确定应用什么策略。此MIB通过提供指向第一个功能数据路径元素的指针表来实现这一点，该表根据接口和接口上的方向进行索引。diffServDataPathEntry的内容是单个行指针，它指向该功能数据路径元素。
When diffServDataPathStart in a direction on an interface is undefined or is set to zeroDotZero, the implication is that there is no specific policy to apply.
当接口上某个方向的diffServDataPathStart未定义或设置为zeroDotZero时，意味着没有要应用的特定策略。
Classifiers are used to differentiate among types of traffic. In the Differentiated Services architecture, one usually discusses a behavior aggregate identified by the application of one or more Differentiated Services Code Points (DSCPs). However, especially at network edges (which include hosts and first hop routers serving hosts), traffic may arrive unmarked or the marks may not be trusted. In these cases, one applies a Multi-Field Classifier, which may select an aggregate as coarse as "all traffic", as fine as a specific microflow identified by IP Addresses, IP Protocol, and TCP or UDP ports, or variety of slices in between.
分类器用于区分不同类型的流量。在区分服务体系结构中，通常讨论由一个或多个区分服务代码点（DSCP）的应用程序标识的行为聚合。但是，特别是在网络边缘（包括主机和服务于主机的第一跳路由器），流量可能未经标记就到达，或者标记可能不可信。在这些情况下，可以应用多字段分类器，该分类器可以选择粗到“所有流量”的聚合，细到由IP地址、IP协议、TCP或UDP端口或其间的各种切片标识的特定微流。
Classifiers can be simple or complex. In a core interface, one would expect to find simple behavior aggregate classification to be used. However, in an edge interface, one might first ask what application is being used, meter the arriving traffic, and then apply various policies to the non-conforming traffic depending on the Autonomous System number advertising the destination address. To accomplish such a thing, traffic must be classified, metered, and then reclassified. To this end, the MIB defines separate classifiers, which may be applied at any point in processing, and may have different content as needed.
分类器可以是简单的，也可以是复杂的。在核心接口中，可以期望找到要使用的简单行为聚合分类。然而，在边缘接口中，人们可能首先询问正在使用什么应用程序，测量到达的流量，然后根据公布目的地地址的自治系统号将各种策略应用于不一致的流量。为了实现这一目标，必须对流量进行分类、计量，然后重新分类。为此，MIB定义了单独的分类器，这些分类器可以在处理过程中的任何时候应用，并且可以根据需要具有不同的内容。
The MIB also allows for ambiguous classification in a structured fashion. In the end, traffic classification must be unambiguous; one must know for certain what policy to apply to any given packet. However, writing an unambiguous specification is often tedious, while writing a specification in steps that permits and excludes various kinds of traffic may be simpler and more intuitive. In such a case, the classification "steps" are enumerated; all classification elements of one precedence are applied as if in parallel, and then all classification elements of the next precedence.
MIB还允许以结构化方式进行不明确的分类。最后，交通分类必须明确；人们必须明确知道对任何给定数据包应用什么策略。然而，编写一个明确的规范通常是乏味的，而编写一个允许和排除各种流量的规范可能更简单、更直观。在这种情况下，列举分类“步骤”；一个优先级的所有分类元素被并行应用，然后下一个优先级的所有分类元素被并行应用。
This MIB defines a single classifier parameter entry, the Multi-field Classifier. A degenerate case of this multi-field classifier is a Behavior Aggregate classifier. Other classifiers may be defined in other MIB modules, to select traffic from a given layer two neighbor or a given interface, traffic whose addresses belong to a given BGP Community or Autonomous System, and so on.
此MIB定义一个分类器参数条目，即多字段分类器。这种多场分类器的退化情况是行为聚合分类器。可以在其他MIB模块中定义其他分类器，以选择来自给定第二层邻居或给定接口的流量、其地址属于给定BGP社区或自治系统的流量，等等。
A classifier consists of classifier elements. A classifier element identifies a specific set of traffic that forms part of a behavior aggregate; other classifier elements within the same classifier may identify other traffic that also falls into the behavior aggregate. For example, in identifying AF traffic for the aggregate AF1, one might implement separate classifier elements for AF11, AF12, and AF13 within the same classifier and pointing to the same subsequent meter.
分类器由分类器元素组成。分类器元素识别构成行为集合一部分的特定流量集合；同一分类器中的其他分类器元素可以识别也属于行为聚合的其他流量。例如，在识别聚合AF1的AF业务时，可以在同一分类器内为AF11、AF12和AF13实现单独的分类器元素，并指向相同的后续计量器。
Generally, one would expect the Data Path Entry to point to a classifier (which is to say, a set of one or more classifier elements), although it may point to something else when appropriate. Reclassification in a functional data path is achieved by pointing to another Classifier Entry when appropriate.
通常，人们期望数据路径条目指向分类器（也就是说，一个或多个分类器元素的集合），尽管在适当的时候它可能指向其他内容。功能数据路径中的重新分类是通过在适当时指向另一个分类器条目来实现的。
A classifier element is a structural element, indexed by classifier ID and element ID. It has a precedence value, allowing for structured ambiguity as described above, a "specific" pointer that identifies what rule is to be applied, and a "next" pointer directing traffic matching the classifier to the next functional data path element. If the "next" pointer is zeroDotZero, the indication is that there is no further differentiated services processing for this behavior aggregate. However, if the "specific" pointer is zeroDotZero, the device is misconfigured. In such a case, the classifier element should be operationally treated as if it were not present.
分类器元素是一个结构元素，由分类器ID和元素ID索引。它有一个优先值，允许如上所述的结构化模糊性，一个“特定”指针，用于标识要应用的规则，以及一个“下一个”指针，用于将分类器与下一个功能数据路径元素相匹配的流量定向。如果“next”指针为zeroDotZero，则表示此行为聚合没有进一步的区分服务处理。但是，如果“特定”指针为zeroDotZero，则设备配置错误。在这种情况下，应在操作上将分类器元素视为不存在。
When the MIB is used for configuration, diffServClfrNextFree and diffServClfrElementNextFree always contain legal values for diffServClfrId and diffServClfrElementId that are not currently used
当MIB用于配置时，diffServClfrNextFree和diffServClfrElementNextFree始终包含当前未使用的diffServClfrId和diffServClfrElementId的合法值
in the system's configuration. The values are validated when creating diffServClfrId and diffServClfrElementId, and in the event of a failure (which would happen if two managers simultaneously attempted to create an entry) must be re-read.
在系统的配置中。在创建diffServClfrId和diffServClfrElementId时会验证这些值，如果出现故障（如果两个管理器同时尝试创建条目，则会发生这种情况），则必须重新读取这些值。
This MIB defines a single parameter type for classification, the Multi-field Classifier. As a parameter, a filter may be specified once and applied to many interfaces, using diffServClfrElementSpecific. This filter matches:
此MIB为分类定义了单个参数类型，即多字段分类器。作为一个参数，可以使用diffServClfrElementSpecific指定一次筛选器并将其应用于多个接口。此筛选器匹配：
o IP source address prefix, including host, CIDR Prefix, and "any source address"
o IP源地址前缀，包括主机、CIDR前缀和“任何源地址”
o IP destination address prefix, including host, CIDR Prefix, and "any destination address"
o IP目标地址前缀，包括主机、CIDR前缀和“任意目标地址”
o IPv6 Flow ID
o IPv6流ID
o IP protocol or "any"
o IP协议或“任何”
o TCP/UDP/SCTP source port range, including "any"
o TCP/UDP/SCTP源端口范围，包括“任意”
o TCP/UDP/SCTP destination port range, including "any"
o TCP/UDP/SCTP目标端口范围，包括“任意”
o Differentiated Services Code Point
o 区分服务代码点
Since port ranges, IP prefixes, or "any" are defined in each case, it is clear that a wide variety of filters can be constructed. The Differentiated Services Behavior Aggregate filter is a special case of this filter, in which only the DSCP is specified.
由于在每种情况下都定义了端口范围、IP前缀或“any”，因此可以构造各种各样的过滤器。区分服务行为聚合筛选器是此筛选器的一个特例，其中仅指定了DSCP。
Other MIB modules may define similar filters in the same way. For example, a filter for Ethernet information might define source and destination MAC addresses of "any", Ethernet Packet Type, IEEE 802.2 SAPs, and IEEE 802.1 priorities. A filter related to policy routing might be structured like the diffServMultiFieldClfrTable, but contain the BGP Communities of the source and destination prefix rather than the prefix itself, meaning "any prefix in this community". For such a filter, a table similar to diffServMultiFieldClfrTable is constructed, and diffServClfrElementSpecific is configured to point to it.
其他MIB模块可以以相同的方式定义类似的过滤器。例如，以太网信息的过滤器可以定义“任意”、以太网分组类型、IEEE 802.2 SAP和IEEE 802.1优先级的源MAC地址和目标MAC地址。与策略路由相关的筛选器的结构可能类似于diffServMultiFieldClfrTable，但包含源前缀和目标前缀的BGP社区，而不是前缀本身，这意味着“此社区中的任何前缀”。对于这样的筛选器，将构造一个类似于DiffServMultifiedClfRetable的表，并将diffServClfrElementSpecific配置为指向该表。
When the MIB is used for configuration, diffServMultiFieldClfrNextFree always contains a legal value for diffServMultiFieldClfrId that is not currently used in the system's configuration.
当MIB用于配置时，diffServMultiFieldClfrNextFree始终包含系统配置中当前未使用的diffServMultiFieldClfrId的合法值。
As discussed in [MODEL], a meter and a shaper are functions that operate on opposing ends of a link. A shaper schedules traffic for transmission at specific times in order to approximate a particular line speed or combination of line speeds. In its simplest form, if the traffic stream contains constant sized packets, it might transmit one packet per unit time to build the equivalent of a CBR circuit. However, various factors intervene to make the approximation inexact; multiple classes of traffic may occasionally schedule their traffic at the same time, the variable length nature of IP traffic may introduce variation, and factors in the link or physical layer may change traffic timing. A meter integrates the arrival rate of traffic and determines whether the shaper at the far end was correctly applied, or whether the behavior of the application in question is naturally close enough to such behavior to be acceptable under a given policy.
如[模型]中所述，仪表和整形器是在连杆的相对端操作的功能。整形器在特定时间安排传输流量，以近似特定线路速度或线路速度组合。在其最简单的形式中，如果业务流包含恒定大小的数据包，则它可以每单位时间发送一个数据包，以构建CBR电路的等效物。然而，各种因素的介入使得近似不精确；多个类别的业务可能偶尔同时调度它们的业务，IP业务的可变长度性质可能引入变化，链路或物理层中的因素可能改变业务定时。仪表整合流量到达率，并确定远端的整形器是否正确应用，或所讨论的应用程序的行为是否自然接近此类行为，在给定策略下是否可以接受。
A common type of meter is a Token Bucket meter, such as [srTCM] or [trTCM]. This type of meter assumes the use of a shaper at a previous node; applications which send at a constant rate when sending may conform if the token bucket is properly specified. It specifies the acceptable arrival rate and quantifies the acceptable variability, often by specifying a burst size or an interval; since rate = quantity/time, specifying any two of those parameters implies the third, and a large interval provides for a forgiving system. Multiple rates may be specified, as in AF, such that a subset of the traffic (up to one rate) is accepted with one set of guarantees, and traffic in excess of that but below another rate has a different set of guarantees. Other types of meters exist as well.
一种常见的电表类型是令牌桶电表，如[srTCM]或[trTCM]。这种类型的仪表假定在前一个节点上使用成形器；如果正确指定了令牌桶，则在发送时以恒定速率发送的应用程序可能符合要求。它指定可接受的到达率，并量化可接受的可变性，通常通过指定突发大小或间隔；由于rate=数量/时间，指定其中任何两个参数都意味着第三个参数，并且大的间隔提供了一个宽恕系统。如在AF中，可以指定多个速率，使得使用一组保证接受业务的子集（最多一个速率），并且超过该速率但低于另一速率的业务具有不同的保证集。其他类型的仪表也存在。
One use of a meter is when a service provider sells at most, a certain bit rate to one of its customers, and wants to drop the excess. In such a case, the fractal nature of normal Internet traffic must be reflected in large burst intervals, as TCP frequently sends packet pairs or larger bursts, and responds poorly when more than one packet in a round trip interval is dropped. Applications like FTP contain the effect by simply staying below the target bit rate; this type of configuration very adversely affects transaction applications like HTTP, however. Another use of a meter is in the AF specification, in which excess traffic is marked with a related DSCP and subjected to slightly more active queue depth management. The
电表的一种用途是当服务提供商最多向其客户销售某个比特率，并希望减少多余的比特率时。在这种情况下，正常互联网流量的分形性质必须在较大的突发间隔中反映出来，因为TCP经常发送数据包对或较大的突发，并且当往返间隔中有多个数据包被丢弃时，响应较差。像FTP这样的应用程序只需保持低于目标比特率就可以产生这种效果；但是，这种类型的配置会对HTTP等事务应用程序产生非常不利的影响。仪表的另一个用途是在AF规范中，在该规范中，用相关的DSCP标记多余的流量，并进行稍微更活跃的队列深度管理。这个
application is not sharply limited to a contracted rate in such a case, but can be readily contained should its traffic create a burden.
在这种情况下，应用程序不受合同费率的严格限制，但如果其流量造成负担，则可以很容易地加以控制。
The Meter Table is a structural table, specifying a specific functional data path element. Its entry consists essentially of three RowPointers - a "succeed" pointer, for traffic conforming to the meter, a "fail" pointer, for traffic not conforming to the meter, and a "specific" pointer, to identify the parameters in question. This structure is a bow to SNMP's limitations; it would be better to have a structure with N rates and N+1 "next" pointers, with a single algorithm specified. In this case, multiple meter entries connected by the "fail" link are understood to contain the parameters for a specified algorithm, and traffic conforming to a given rate follows their "succeed" paths. Within this MIB, only Token Bucket parameters are specified; other varieties of meters may be designed in other MIB modules.
仪表表是一个结构表，用于指定特定的功能数据路径元素。其条目基本上由三个行指针组成-一个“成功”指针，用于符合仪表的流量，“失败”指针，用于不符合仪表的流量，以及一个“特定”指针，用于识别相关参数。这种结构是对SNMP限制的屈服；最好有一个具有N个速率和N+1个“next”指针的结构，并指定一个算法。在这种情况下，通过“失败”链路连接的多个仪表条目被理解为包含指定算法的参数，并且符合给定速率的流量遵循其“成功”路径。在此MIB中，仅指定令牌桶参数；其他类型的仪表可在其他MIB模块中设计。
When the MIB is used for configuration, diffServMeterNextFree always contains a legal value for diffServMeterId that is not currently used in the system's configuration.
当MIB用于配置时，diffServMeterNextFree始终包含当前未在系统配置中使用的DiffServMeterRid的合法值。
The Token Bucket Parameters Table is a set of parameters that define a Token Bucket Meter. As a parameter, a token bucket may be specified once and applied to many interfaces, using diffServMeterSpecific. Specifically, several modes of [srTCM] and [trTCM] are addressed. Other varieties of meters may be specified in other MIB modules.
令牌桶参数表是定义令牌桶计量器的一组参数。作为一个参数，可以使用diffServMeterSpecific一次性指定一个令牌桶，并将其应用于多个接口。具体而言，介绍了[srTCM]和[trTCM]的几种模式。其他MIB模块中可能会指定其他类型的仪表。
In general, if a Token Bucket has N rates, it has N+1 potential outcomes - the traffic stream is slower than and therefore conforms to all of the rates, it fails the first few but is slower than and therefore conforms to the higher rates, or it fails all of them. As such, multi-rate meters should specify those rates in monotonically increasing order, passing through the diffServMeterFailNext from more committed to more excess rates, and finally falling through diffServMeterFailNext to the set of actions that apply to traffic which conforms to none of the specified rates. diffServTBParamType in the first entry indicates the algorithm being used. At each rate, diffServTBParamRate is derivable from diffServTBParamBurstSize and diffServTBParamInterval; a superior implementation will allow the
通常，如果令牌桶有N个速率，则它有N+1个潜在结果-业务流比所有速率都慢，因此符合所有速率，前几个速率失败，但比更高的速率慢，因此符合更高的速率，或者所有速率都失败。因此，多速率仪表应以单调递增的顺序指定这些速率，通过diffServMeterFailNext从更多承诺速率到更多超额速率，最后通过diffServMeterFailNext，直到应用于不符合任何指定速率的流量的操作集。第一个条目中的diffServTBParamType表示正在使用的算法。在每种速率下，diffServTBParamRate都可以从diffServTBParamBurstSize和diffServTBParamInterval派生出来；优越的实现将允许
configuration of any two of diffServTBParamRate, diffServTBParamBurstSize, and diffServTBParamInterval, and respond with the appropriate error code if all three are specified but are not mathematically related.
配置diffServTBParamRate、diffServTBParamBurstSize和diffServTBParamInterval中的任意两个，如果指定了这三个，但在数学上不相关，则使用相应的错误代码进行响应。
When the MIB is used for configuration, diffServTBParamNextFree always contains a legal value for diffServTBParamId that is not currently used in the system's configuration.
当MIB用于配置时，diffServTBParamNextFree始终包含当前未在系统配置中使用的diffServTBParamId的合法值。
"Actions" are the things a differentiated services interface PHB may do to a packet in transit. At a minimum, such a policy might calculate statistics on traffic in various configured classes, mark it with a DSCP, drop it, or enqueue it before passing it on for other processing.
“操作”是区分服务接口PHB可能对传输中的数据包执行的操作。至少，这样的策略可以计算各种配置类中的流量统计信息，使用DSCP对其进行标记、丢弃或在将其传递给其他处理之前将其排队。
Actions are composed of a structural element, the diffServActionTable, and various component action entries that may be applied. In the case of the Algorithmic Dropper, an additional parameter table may be specified to control Active Queue Management, as defined in [RED93] and other AQM specifications.
动作由结构元素、diffServActionTable和可应用的各种组件动作项组成。在算法滴管的情况下，可以指定额外的参数表来控制活动队列管理，如[RED93]和其他AQM规范中所定义。
The action table identifies sequences of actions to be applied to a packet. Successive actions are chained through diffServActionNext, ultimately resulting in zeroDotZero (indicating that the policy is complete), a pointer to a queue, or a pointer to some other functional data path element.
动作表标识要应用于数据包的动作序列。后续操作通过diffServActionNext链接，最终生成zeroDotZero（表示策略已完成）、指向队列的指针或指向其他功能数据路径元素的指针。
When the MIB is used for configuration, diffServActionNextFree always contains a legal value for diffServActionId that is not currently used in the system's configuration.
当MIB用于配置时，diffServActionNextFree始终包含当前未在系统配置中使用的diffServActionId的合法值。
The count action accumulates statistics pertaining to traffic passing through a given path through the policy. It is intended to be useful for usage-based billing, for statistical studies, or for analysis of the behavior of a policy in a given network. The objects in the Count Action are various counters and a discontinuity time. The counters display the number of packets and bytes encountered on the path since the discontinuity time. They share the same discontinuity time, which is the discontinuity time of the interface or agent.
count操作累积与通过策略的给定路径的流量相关的统计信息。它旨在用于基于使用情况的计费、统计研究或特定网络中策略行为的分析。计数操作中的对象是各种计数器和不连续时间。计数器显示自中断时间以来在路径上遇到的数据包和字节数。它们共享相同的不连续时间，即界面或代理的不连续时间。
The designers of this MIB expect that every path through a policy should have a corresponding counter. In early versions, it was impossible to configure an action without implementing a counter, although the current design makes them in effect the network manager's option, as a result of making actions consistent in structure and extensibility. The assurance of proper debugging and accounting is therefore left with the policy designer.
此MIB的设计者希望通过策略的每个路径都应该有相应的计数器。在早期版本中，不实现计数器就无法配置操作，尽管当前的设计使它们实际上成为网络管理器的选项，这是使操作在结构和可扩展性上保持一致的结果。因此，正确调试和记帐的保证留给策略设计者。
When the MIB is used for configuration, diffServCountActNextFree always contains a legal value for diffServCountActId that is not currently used in the system's configuration.
当MIB用于配置时，diffServCountActNextFree始终包含当前未在系统配置中使用的diffServCountActId的合法值。
The Mark Action table is an unusual table, both in SNMP and in this MIB. It might be viewed not so much as an array of single-object entries as an array of OBJECT-IDENTIFIER conventions, as the OID for a diffServDscpMarkActDscp instance conveys all of the necessary information: packets are to be marked with the requisite DSCP.
标记操作表在SNMP和此MIB中都是一个不寻常的表。与其说它是单个对象条目的数组，不如说它是对象标识符约定的数组，因为diffservdscmparkactdscp实例的OID传递了所有必要的信息：数据包要用必要的DSCP进行标记。
As such, contrary to common practice, the index for the table is read- only, and is both the Entry's index and its only value.
因此，与通常的做法相反，表的索引是只读的，并且是条目的索引及其唯一值。
The Algorithmic Drop Table identifies a dropping algorithm, drops packets, and counts the drops. Classified as an action, it is in effect a method which applies a packet to a queue, and may modify either. When the algorithm is "always drop", this is simple; when the algorithm calls for head-drop, tail-drop, or a variety of Active Queue Management, the queue is inspected, and in the case of Active Queue Management, additional parameters are REQUIRED.
算法丢弃表标识丢弃算法，丢弃数据包，并统计丢弃次数。它被分类为一个动作，实际上是一种将数据包应用于队列的方法，并且可以修改其中任何一个。当算法为“始终下降”时，这很简单；当算法调用头下降、尾下降或各种活动队列管理时，将检查队列，如果是活动队列管理，则需要附加参数。
What may not be clear from the name is that an Algorithmic Drop action often does not drop traffic. Algorithms other than "always drop" normally drop a few percent of packets at most. The action inspects the diffServQEntry that diffServAlgDropQMeasure points to in order to determine whether the packet should be dropped.
名称中可能不清楚的是，算法丢弃操作通常不会丢弃流量。除了“总是丢弃”以外的算法通常最多丢弃百分之几的数据包。该操作检查diffServAlgDropQMeasure指向的diffServQEntry，以确定是否应丢弃数据包。
When the MIB is used for configuration, diffServAlgDropNextFree always contains a legal value for diffServAlgDropId that is not currently used in the system's configuration.
当MIB用于配置时，diffServAlgDropNextFree始终包含当前未在系统配置中使用的diffServAlgDropId的合法值。
The Random Drop Table is an extension of the Algorithmic Drop Table intended for use on queues whose depth is actively managed. Active Queue Management algorithms are typified by [RED93], but the parameters they use vary. It was deemed for the purposes of this MIB that the proper values to represent include:
随机丢弃表是算法丢弃表的扩展，用于深度被主动管理的队列。主动队列管理算法以[RED93]为代表，但它们使用的参数各不相同。就本MIB而言，被视为代表的适当值包括：
o Target case mean queue depth, expressed in bytes or packets
o 目标案例平均队列深度，以字节或数据包表示
o Worst case mean queue depth, expressed in bytes or packets
o 最坏情况下的平均队列深度，以字节或数据包表示
o Maximum drop rate expressed as drops per thousand
o 最大下降率表示为每千次下降
o Coefficient of an exponentially weighted moving average, expressed as the numerator of a fraction whose denominator is 65536.
o 指数加权移动平均数的系数，表示为分母为65536的分数的分子。
o Sampling rate
o 抽样率
An example of the representation chosen in this MIB for this element is shown in Figure 1.
图1显示了在此MIB中为此元素选择的表示的示例。
Random droppers often have their drop probability function described as a plot of drop probability (P) against averaged queue length (Q). (Qmin,Pmin) then defines the start of the characteristic plot. Normally Pmin=0, meaning with average queue length below Qmin, there will be no drops. (Qmax,Pmax) defines a "knee" on the plot, after which point the drop probability becomes more progressive (greater slope). (Qclip,1) defines the queue length at which all packets will be dropped. Notice this is different from Tail Drop because this uses an averaged queue length, although it is possible for Qclip to equal Qmax.
随机丢弃者的丢弃概率函数通常被描述为丢弃概率（P）与平均队列长度（Q）的关系图。（Qmin，Pmin）然后定义特征图的开始。通常，Pmin=0，这意味着平均队列长度低于Qmin时，将不会有丢弃。（Qmax，Pmax）在绘图上定义了一个“拐点”，在此点之后，下降概率变得更加渐进（坡度更大）。（Qclip，1）定义所有数据包将丢弃的队列长度。请注意，这与尾部丢弃不同，因为它使用平均队列长度，尽管Qclip可能等于Qmax。
In the MIB module, diffServRandomDropMinThreshBytes and diffServRandomDropMinThreshPkts represent Qmin. diffServRandomDropMaxThreshBytes and diffServRandomDropMaxThreshPkts represent Qmax. diffServAlgDropQThreshold represents Qclip. diffServRandomDropInvProbMax represents Pmax (inverse). This MIB does not represent Pmin (assumed to be zero unless otherwise represented). In addition, since message memory is finite, queues generally have some upper bound above which they are incapable of storing additional traffic. Normally this number is equal to Qclip, specified by diffServAlgDropQThreshold.
在MIB模块中，diffServRandomDropMinThreshBytes和DiffServRandomDropMinThreshKts表示Qmin。diffServRandomDropMaxThreshBytes和DiffServRandomDropMaxThreshPKT表示Qmax。diffServAlgDropQThreshold表示Qclip。diffServRandomDropInvProbMax表示Pmax（反向）。此MIB不表示Pmin（除非另有说明，否则假定为零）。此外，由于消息内存是有限的，队列通常有一些上限，超过这个上限，它们无法存储额外的流量。通常，此数字等于diffServAlgDropQThreshold指定的Qclip。
AlgDrop Queue
+-----------------+ +-------+
--->| Next ---------+--+------------------->| Next -+--> ...
| QMeasure -------+--+ | ... |
| QThreshold | RandomDrop +-------+
| Type=randomDrop | +----------------+
| Specific -------+---->| MinThreshBytes |
+-----------------+ | MaxThreshBytes |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
AlgDrop Queue
+-----------------+ +-------+
--->| Next ---------+--+------------------->| Next -+--> ...
| QMeasure -------+--+ | ... |
| QThreshold | RandomDrop +-------+
| Type=randomDrop | +----------------+
| Specific -------+---->| MinThreshBytes |
+-----------------+ | MaxThreshBytes |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
Figure 1: Example Use of the RandomDropTable for Random Droppers
图1:RandomDropTable用于随机滴管的示例
Each random dropper specification is associated with a queue. This allows multiple drop processes (of same or different types) to be associated with the same queue, as different PHB implementations may require. This also allows for sequences of multiple droppers if necessary.
每个随机滴管规范都与一个队列相关联。这允许多个丢弃进程（相同或不同类型）与同一队列相关联，因为不同的PHB实现可能需要。如有必要，这也允许多个滴管的顺序。
The calculation of a smoothed queue length may also have an important bearing on the behavior of the dropper: parameters may include the sampling interval or rate, and the weight of each sample. The performance may be very sensitive to the values of these parameters and a wide range of possible values may be required due to a wide range of link speeds. Most algorithms include a sample weight, represented here by diffServRandomDropWeight. The availability of diffServRandomDropSamplingRate as readable is important, the information provided by Sampling Rate is essential to the configuration of diffServRandomDropWeight. Having Sampling Rate be configurable is also helpful, as line speed increases, the ability to have queue sampling be less frequent than packet arrival is needed. Note, however, that there is ongoing research on this topic, see e.g. [ACTQMGMT] and [AQMROUTER].
平滑队列长度的计算也可能对滴管的行为有重要影响：参数可能包括采样间隔或速率，以及每个样本的权重。性能可能对这些参数的值非常敏感，并且由于链路速度的范围很广，可能需要范围很广的可能值。大多数算法都包含一个样本权重，这里用diffServRandomDropWeight表示。DiffServRandomDropSampligrate的可用性很重要，因为可读性很强，采样率提供的信息对于diffServRandomDropWeight的配置至关重要。采样率可配置也很有帮助，随着线路速度的提高，需要队列采样频率低于数据包到达频率的能力。但是，请注意，关于这一主题的研究仍在进行中，请参见[ACTQMGMT]和[AQMROUTER]。
Additional parameters may be added in an enterprise MIB module, e.g. by using AUGMENTS on this table, to handle aspects of random drop algorithms that are not standardized here.
可以在企业MIB模块中添加其他参数，例如，通过使用此表上的增强来处理此处未标准化的随机丢弃算法的各个方面。
When the MIB is used for configuration, diffServRandomDropNextFree always contains a legal value for diffServRandomDropId that is not currently used in the system's configuration.
当MIB用于配置时，diffServRandomDropNextFree始终包含当前未在系统配置中使用的diffServRandomDropId的合法值。
These include Queues and Schedulers, which are inter-related in their use of queuing techniques. By doing so, it is possible to build multi-level schedulers, such as those which treat a set of queues as having priority among them, and at a specific priority find a secondary WFQ scheduler with some number of queues.
其中包括队列和调度程序，它们在使用队列技术时是相互关联的。通过这样做，可以构建多级调度程序，例如那些将一组队列视为其中具有优先级的调度程序，并以特定优先级找到具有一定数量队列的辅助WFQ调度程序。
The Queue Table models simple FIFO queues. The Scheduler Table allows flexibility in constructing both simple and somewhat more complex queuing hierarchies from those queues.
队列表为简单的FIFO队列建模。调度器表允许灵活地从这些队列构造简单的队列层次结构和稍微复杂一些的队列层次结构。
Queue Table entries are pointed at by the "next" attributes of the upstream elements, such as diffServMeterSucceedNext or diffServActionNext. Note that multiple upstream elements may direct their traffic to the same Queue Table entry. For example, the Assured Forwarding PHB suggests that all traffic marked AF11, AF12 or AF13 be placed in the same queue, after metering, without reordering. To accomplish that, the upstream diffServAlgDropNext pointers each point to the same diffServQEntry.
队列表条目由上游元素的“next”属性指向，如diffServMeterSucceedNext或diffServActionNext。请注意，多个上游元素可能会将其流量定向到同一队列表条目。例如，有保证的转发PHB建议在计量之后，所有标记为AF11、AF12或AF13的流量都放在同一队列中，而无需重新排序。为了实现这一点，上游diffServAlgDropNext将每个点指向相同的diffServQEntry。
A common requirement of a queue is that its traffic enjoy a certain minimum or maximum rate, or that it be given a certain priority. Functionally, the selection of such is a function of a scheduler. The parameter is associated with the queue, however, using the Minimum or Maximum Rate Parameters Table.
队列的一个常见要求是，它的流量享有一定的最小或最大速率，或者被赋予一定的优先级。从功能上讲，这样的选择是调度器的功能。但是，该参数使用最小或最大速率参数表与队列相关联。
When the MIB is used for configuration, diffServQNextFree always contains a legal value for diffServQId that is not currently used in the system's configuration.
当MIB用于配置时，diffServQNextFree始终包含当前未在系统配置中使用的diffServQId的合法值。
The scheduler, and therefore the Scheduler Table, accepts inputs from either queues or a preceding scheduler. The Scheduler Table allows flexibility in constructing both simple and somewhat more complex queuing hierarchies from those queues.
调度器，因此也是调度器表，接受来自队列或前面调度器的输入。调度器表允许灵活地从这些队列构造简单的队列层次结构和稍微复杂一些的队列层次结构。
When the MIB is used for configuration, diffServSchedulerNextFree always contains a legal value for diffServSchedulerId that is not currently used in the system's configuration.
当MIB用于配置时，diffServSchedulerNextFree始终包含当前未在系统配置中使用的diffServSchedulerId的合法值。
When the output rate of a queue or scheduler must be given a minimum rate or a priority, this is done using the diffServMinRateTable.
当必须为队列或调度程序的输出速率指定最小速率或优先级时，可使用diffServMinRateTable完成此操作。
Rates may be expressed as absolute rates, or as a fraction of ifSpeed, and imply the use of a rate-based scheduler such as WFQ or WRR. The use of a priority implies the use of a Priority Scheduler. Only one of the Absolute or Relative rates needs to be set; the other takes the relevant value as a result. Excess capacity is distributed proportionally among the inputs to a scheduler using the assured rate. More complex functionality may be described by augmenting this MIB.
速率可以表示为绝对速率，也可以表示为ifSpeed的一部分，这意味着使用基于速率的调度器，如WFQ或WRR。使用优先级意味着使用优先级调度程序。只需设置一个绝对或相对速率；另一个取相关值作为结果。多余的容量使用保证的速率在调度程序的输入之间按比例分配。更复杂的功能可以通过扩充这个MIB来描述。
When a priority scheduler is used, its effect is to give the queue the entire capacity of the subject interface less the capacity used by higher priorities, if there is traffic present to use it. This is true regardless of the rate specifications applied to that queue or other queues on the interface. Policing excess traffic will mitigate this behavior.
使用优先级调度器时，其效果是，如果存在要使用它的流量，则为队列提供主题接口的全部容量减去较高优先级使用的容量。无论应用于该队列或接口上的其他队列的速率规范如何，这都是正确的。监控过多的流量将缓解这种行为。
When the MIB is used for configuration, diffServMinRateNextFree always contains a legal value for diffServMinRateId that is not currently used in the system's configuration.
当MIB用于配置时，diffServMinRateNextFree始终包含当前未在系统配置中使用的diffServMinRateId的合法值。
When the output rate of a queue or scheduler must be limited to at most a specified maximum rate, this is done using the diffServMaxRateTable. Rates may be expressed as absolute rates, or as a fraction of ifSpeed. Only one of the Absolute or Relative rate needs to be set; the other takes the relevant value as a result.
当队列或计划程序的输出速率必须限制为最多指定的最大速率时，可使用diffServMaxRateTable完成此操作。速率可以表示为绝对速率，也可以表示为速度的一部分。只需设置一个绝对或相对速率；另一个取相关值作为结果。
The definition of a multirate shaper requires multiple diffServMaxRateEntries. In this case, an algorithm such as [SHAPER] is used. In that algorithm, more than one rate is specified, and at any given time traffic is shaped to the lowest specified rate which exceeds the arrival rate of traffic.
多速率整形器的定义需要多个DiffServMaxRate条目。在这种情况下，使用诸如[SHAPER]之类的算法。在该算法中，指定了一个以上的速率，并且在任何给定时间，流量被塑造为超过流量到达速率的最低指定速率。
When the MIB is used for configuration, diffServMaxRateNextFree always contains a legal value for diffServMaxRateId that is not currently used in the system's configuration.
当MIB用于配置时，diffServMaxRateNextFree始终包含当前未在系统配置中使用的diffServMaxRateId的合法值。
For representing a Strict Priority scheduler, each scheduler input is assigned a priority with respect to all the other inputs feeding the same scheduler, with default values for the other parameters. Higher-priority traffic that is not being delayed for shaping will be serviced before a lower-priority input. An example is found in Figure 2.
为了表示严格优先级的调度器，每个调度器输入都被分配了一个优先级，相对于为同一个调度器提供数据的所有其他输入，其他参数都有默认值。未延迟成形的高优先级流量将在低优先级输入之前得到服务。图2给出了一个示例。
For weighted scheduling methods, such as WFQ or WRR, the "weight" of a given scheduler input is represented with a Minimum Service Rate leaky-bucket profile which provides a guaranteed minimum bandwidth to that input, if required. This is represented by a rate diffServMinRateAbsolute; the classical weight is the ratio between that rate and the interface speed, or perhaps the ratio between that rate and the sum of the configured rates for classes. The rate may be represented by a relative value, as a fraction of the interface's current line rate, diffServMinRateRelative, to assist in cases where line rates are variable or where a higher-level policy might be expressed in terms of fractions of network resources. The two rate parameters are inter-related and changes in one may be reflected in the other. An example is found in figure 3.
对于加权调度方法，如WFQ或WRR，给定调度程序输入的“权重”用最小服务速率泄漏桶配置文件表示，该配置文件在需要时为该输入提供保证的最小带宽。这由速率diffServMinRateAbsolute表示；经典权重是该速率与接口速度之间的比率，或者可能是该速率与类的配置速率之和之间的比率。速率可由相对值表示，作为接口当前线路速率的一部分diffServMinRateRelative，以在线路速率可变或更高级别的策略可能以网络资源的一部分表示的情况下提供帮助。这两个速率参数相互关联，其中一个参数的变化可能反映在另一个参数中。图3给出了一个示例。
+-----+
+-------+ | P S |
| Queue +------------>+ r c |
+-------+-+--------+ | i h |
|Priority| | o e |
+--------+ | r d +----------->
+-------+ | i u |
| Queue +------------>+ t l |
+-------+-+--------+ | y e |
|Priority| | r |
+--------+ +-----+
+-----+
+-------+ | P S |
| Queue +------------>+ r c |
+-------+-+--------+ | i h |
|Priority| | o e |
+--------+ | r d +----------->
+-------+ | i u |
| Queue +------------>+ t l |
+-------+-+--------+ | y e |
|Priority| | r |
+--------+ +-----+
Figure 2: Priority Scheduler with two queues
图2：具有两个队列的优先级调度器
For weighted scheduling methods, one can say loosely, that WRR focuses on meeting bandwidth sharing, without concern for relative delay amongst the queues; where WFQ controls both queue the service order and the amount of traffic serviced, providing bandwidth sharing and relative delay ordering amongst the queues.
对于加权调度方法，可以粗略地说，WRR专注于满足带宽共享，而不考虑队列之间的相对延迟；其中，WFQ控制队列服务顺序和服务流量，在队列之间提供带宽共享和相对延迟顺序。
A queue or scheduled set of queues (which is an input to a scheduler) may also be capable of acting as a non-work-conserving [MODEL] traffic shaper: this is done by defining a Maximum Service Rate leaky-bucket profile in order to limit the scheduler bandwidth available to that input. This is represented by a rate, in diffServMaxRateAbsolute; the classical weight is the ratio between that rate and the interface speed, or perhaps the ratio between that rate and the sum of the configured rates for classes. The rate may be represented by a relative value, as a fraction of the interface's current line rate, diffServMaxRateRelative. This MIB presumes that shaping is something a scheduler does to its inputs, which it models as a queue with a maximum rate or a scheduler whose output has a maximum rate.
一个队列或一组调度队列（作为调度器的输入）也可以充当非工作节约[模型]流量整形器：这是通过定义最大服务速率泄漏桶配置文件来实现的，以限制该输入可用的调度器带宽。这由速率表示，以diffServMaxRateAbsolute表示；经典权重是该速率与接口速度之间的比率，或者可能是该速率与类的配置速率之和之间的比率。速率可以用相对值表示，作为接口当前线路速率diffServMaxRateRelative的一部分。此MIB假定成形是调度器对其输入所做的事情，它将其建模为具有最大速率的队列或具有最大速率的输出的调度器。
+-----+
+-------+ | W S |
| Queue +------------>+ R c |
+-------+-+--------+ | R h |
| Rate | | e |
+--------+ | o d +----------->
+-------+ | r u |
| Queue +------------>+ l |
+-------+-+--------+ | W e |
| Rate | | F r |
+--------+ | Q |
+-----+
+-----+
+-------+ | W S |
| Queue +------------>+ R c |
+-------+-+--------+ | R h |
| Rate | | e |
+--------+ | o d +----------->
+-------+ | r u |
| Queue +------------>+ l |
+-------+-+--------+ | W e |
| Rate | | F r |
+--------+ | Q |
+-----+
Figure 3: WRR or WFQ rate-based scheduler with two inputs
图3：具有两个输入的基于WRR或WFQ速率的调度器
The same may be done on a queue, if a given class is to be shaped to a maximum rate without shaping other classes, as in Figure 5.
如果给定的类要被塑造成最大速率而不塑造其他类，则可以在队列上执行相同的操作，如图5所示。
Other types of priority and weighted scheduling methods can be defined using existing parameters in diffServMinRateEntry. NOTE: diffServSchedulerMethod uses OBJECT IDENTIFIER syntax, with the different types of scheduling methods defined as OBJECT-IDENTITY.
可以使用diffServMinRateEntry中的现有参数定义其他类型的优先级和加权调度方法。注意：diffServSchedulerMethod使用对象标识符语法，不同类型的调度方法定义为对象标识。
+---+
+-------+ | S |
| Queue +------------>+ c |
+-------+-+--------+ | h |
| | | e +----------->
+--------+ | d +-+-------+
| u | |Shaping|
+-------+ | l | | Rate |
| Queue +------------>+ e | +-------+
+-------+-+--------+ | r |
| | +---+
+--------+
+---+
+-------+ | S |
| Queue +------------>+ c |
+-------+-+--------+ | h |
| | | e +----------->
+--------+ | d +-+-------+
| u | |Shaping|
+-------+ | l | | Rate |
| Queue +------------>+ e | +-------+
+-------+-+--------+ | r |
| | +---+
+--------+
Figure 4: Shaping scheduled traffic to a known rate
图4：将计划流量调整为已知速率
+---+
+-------+ | S |
| Queue +------------>+ c |
+-------+-+--------+ | h |
|Min Rate| | e +----------->
+--------+ | d |
| u |
+-------+ | l |
| Queue +------------>+ e |
+-------+-+--------+ | r |
|Min Rate| | |
+--------+ | |
|Max Rate| | |
+--------+ +---+
+---+
+-------+ | S |
| Queue +------------>+ c |
+-------+-+--------+ | h |
|Min Rate| | e +----------->
+--------+ | d |
| u |
+-------+ | l |
| Queue +------------>+ e |
+-------+-+--------+ | r |
|Min Rate| | |
+--------+ | |
|Max Rate| | |
+--------+ +---+
Figure 5: Shaping one input to a work-conserving scheduler
图5：将一个输入整形为节省工作的调度器
Future scheduling methods may be defined in other MIBs. This requires an OBJECT-IDENTITY definition, a description of how the existing objects are reused, if they are, and any new objects they require.
未来的调度方法可在其他MIB中定义。这需要一个对象标识定义，描述如何重用现有对象（如果是），以及它们需要的任何新对象。
To implement an EF and two AF classes, one must use a combination of priority and WRR/WFQ scheduling. This requires us to cascade two schedulers. If one were to additionally shape the output of the system to a rate lower than the interface rate, one must place an upper bound rate on the output of the priority scheduler. See figure 6.
要实现一个EF和两个AF类，必须结合使用优先级和WRR/WFQ调度。这需要我们级联两个调度器。如果要将系统的输出进一步调整为低于接口速率的速率，则必须在优先级调度器的输出上设置一个上限速率。参见图6。
For the sake of argument, let us build an example with one EF class and four AF classes using the constructs in this MIB.
为了便于讨论，让我们使用此MIB中的构造构建一个包含一个EF类和四个AF类的示例。
The ingress edge interface identifies traffic into classes, meters it, and ensures that any excess is appropriately dealt with according to the PHB. For AF, this means marking excess; for EF, it means dropping excess or shaping it to a maximum rate.
入口边缘接口将流量识别为类，对其进行计量，并确保根据PHB适当处理任何多余的流量。对于AF，这意味着标记过量；对于EF来说，这意味着减少多余部分或将其调整到最大速率。
+-----+
+-------+ | P S |
| Queue +---------------------------------->+ r c |
+-------+----------------------+--------+ | i h |
|Priority| | o e +----------->
+--------+ | r d +-+-------+
+------+ | i u | |Shaping|
+-------+ | W S +------------->+ t l | | Rate |
| Queue +------------>+ R c +-+--------+ | y e | +-------+
+-------+-+--------+ | R h | |Priority| | r |
|Min Rate| | e | +--------+ +-----+
+--------+ | o d |
+-------+ | r u |
| Queue +------------>+ l |
+-------+-+--------+ | W e |
|Min Rate| | F r |
+--------+ | Q |
+------+
+-----+
+-------+ | P S |
| Queue +---------------------------------->+ r c |
+-------+----------------------+--------+ | i h |
|Priority| | o e +----------->
+--------+ | r d +-+-------+
+------+ | i u | |Shaping|
+-------+ | W S +------------->+ t l | | Rate |
| Queue +------------>+ R c +-+--------+ | y e | +-------+
+-------+-+--------+ | R h | |Priority| | r |
|Min Rate| | e | +--------+ +-----+
+--------+ | o d |
+-------+ | r u |
| Queue +------------>+ l |
+-------+-+--------+ | W e |
|Min Rate| | F r |
+--------+ | Q |
+------+
Figure 6: Combined EF and AF services using cascaded schedulers.
图6：使用级联调度器的组合EF和AF服务。
+-----------------------+
| diffServDataPathStart |
+-----------+-----------+
|
+----------+
|
+--+--+ +-----+ +-----+ +-----+ +-----+
| AF1 +-----+ AF2 +-----+ AF3 +-----+ AF4 +-----+ EF |
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
| | | | |
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
|trTCM| |trTCM| |trTCM| |trTCM| |srTCM|
|Meter| |Meter| |Meter| |Meter| |Meter|
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+||---+ +-+||---+ +-+||---+ +-+||---+ +-+-|---+
|+-+|----+ |+-+|----+ |+-+|----+ |+-+|----+ |+--+----+
||+-+-----+ ||+-+-----+ ||+-+-----+ ||+-+-----+ ||Actions|
+||Actions| +||Actions| +||Actions| +||Actions| +| |
+| | +| | +| | +| | +-+-----+
+-+-----+ +-+-----+ +-+-----+ +-+-----+ |
||| ||| ||| ||| |
VVV VVV VVV VVV V
+-----------------------+
| diffServDataPathStart |
+-----------+-----------+
|
+----------+
|
+--+--+ +-----+ +-----+ +-----+ +-----+
| AF1 +-----+ AF2 +-----+ AF3 +-----+ AF4 +-----+ EF |
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
| | | | |
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
|trTCM| |trTCM| |trTCM| |trTCM| |srTCM|
|Meter| |Meter| |Meter| |Meter| |Meter|
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+||---+ +-+||---+ +-+||---+ +-+||---+ +-+-|---+
|+-+|----+ |+-+|----+ |+-+|----+ |+-+|----+ |+--+----+
||+-+-----+ ||+-+-----+ ||+-+-----+ ||+-+-----+ ||Actions|
+||Actions| +||Actions| +||Actions| +||Actions| +| |
+| | +| | +| | +| | +-+-----+
+-+-----+ +-+-----+ +-+-----+ +-+-----+ |
||| ||| ||| ||| |
VVV VVV VVV VVV V
Accepted traffic is sent to IP forwarding
接受的流量被发送到IP转发
Figure 7: combined EF and AF implementation, ingress side
图7：入口侧EF和AF组合实现
A packet arriving at an ingress interface picks up its policy from the diffServDataPathTable. This points to a classifier, which will select traffic according to some specification for each traffic class.
到达入口接口的数据包从diffServDataPathTable获取其策略。这指向一个分类器，它将根据每个流量类别的某些规范选择流量。
An example of a classifier for an AFm class would be a set of three classifier elements, each pointing to a Multi-field classification parameter block identifying one of the AFmn DSCPs. Alternatively, the filters might contain selectors for HTTP traffic or some other application.
AFm类的分类器示例为一组三个分类器元素，每个元素指向识别AFmn DSCP之一的多字段分类参数块。或者，过滤器可能包含HTTP流量或某些其他应用程序的选择器。
An example of a classifier for EF traffic might be a classifier element pointing to a filter specifying the EF code point, a collection of classifiers with parameter blocks specifying individual telephone calls, or a variety of other approaches.
EF业务的分类器的示例可以是指向指定EF码点的过滤器的分类器元素、具有指定单个电话呼叫的参数块的分类器集合或各种其他方法。
Typically, of course, a classifier identifies a variety of traffic and breaks it up into separate classes. It might very well contain fourteen classifier elements indicating the twelve AFmn DSCP values, EF, and "everything else". These would presumably direct traffic down six functional data paths: one for each AF or EF class, and one for all other traffic.
当然，通常情况下，分类器会识别各种流量并将其分解为单独的类。它很可能包含14个分类器元素，指示12个AFmn DSCP值、EF和“其他所有内容”。这可能会将流量引导到六条功能数据路径上：一条用于每个AF或EF类，另一条用于所有其他流量。
Each AFm class applies a Two Rate Three Color Meter, dividing traffic into three groups. These groups of traffic conform to both specified rates, only the higher one, or none. The intent, on the ingress interface at the edge of the network, is to measure and appropriately mark traffic.
每个AFm等级应用一个双速率三色表，将交通分为三组。这些流量组符合两个指定的速率，只有较高的速率，或者不符合。在网络边缘的入口接口上，目的是测量并适当标记流量。
Each AFm class applies a Two Rate Three Color Meter, dividing traffic into three groups. If two rates R and S, where R < S, are specified and traffic arrives at rate T, traffic comprising up to R bits per second is considered to conform to the "confirmed" rate, R. If R < T, traffic comprising up to S-R bits per second is considered to conform to the "excess" rate, S. Any further excess is non-conformant.
每个AFm等级应用一个双速率三色表，将交通分为三组。如果指定了两个速率R和S，其中R<S，并且流量达到速率T，则认为每秒最多R比特的流量符合“确认”速率R。如果R<T，每秒最多S-R比特的流量符合“超额”速率S。任何进一步的超额都是不符合的。
Two meter entries are used to configure this, one for the conforming rate and one for the excess rate. The rate parameters are stored in associated Token Bucket Parameter Entries. The "FailNext" pointer of the lower rate Meter Entry points to the other Meter Entry; both "SucceedNext" pointers and the "FailNext" pointer of the higher Meter
两个仪表条目用于配置，一个用于合格率，另一个用于超额率。速率参数存储在相关的令牌桶参数条目中。低速率仪表入口的“FailNext”指针指向另一个仪表入口；较高仪表的“成功下一步”指针和“失败下一步”指针
Entry point to lists of actions. In the color-blind mode, all three classifier "next" entries point to the lower rate meter entry. In the color-aware mode, the AFm1 classifier points to the lower rate entry, the AFm2 classifier points to the higher rate entry (as it is only compared against that rate), and the AFm3 classifier points directly to the actions taken when both rates fail.
操作列表的入口点。在色盲模式下，所有三个分类器“下一个”条目都指向低速率仪表条目。在颜色感知模式下，AFm1分类器指向低速率条目，AFm2分类器指向高速率条目（因为它仅与该速率进行比较），AFm3分类器直接指向两个速率均失败时采取的操作。
For network planning and perhaps for billing purposes, arriving traffic is normally counted. Therefore, a "count" action, consisting of an action table entry pointing to a count table entry, is configured.
对于网络规划，或者出于计费目的，通常会计算到达流量。因此，配置了“计数”操作，该操作由指向计数表项的操作表项组成。
Also, traffic is marked with the appropriate DSCP. The first R bits per second are marked AFm1, the next S-R bits per second are marked AFm2, and the rest is marked AFm3. It may be that traffic is arriving marked with the same DSCP, but in general, the additional complexity of deciding that it is being remarked to the same value is not useful. Therefore, a "mark" action, consisting of an action table entry pointing to a mark table entry, is configured.
此外，使用适当的DSCP标记通信量。每秒第一个R位标记为AFm1，每秒下一个S-R位标记为AFm2，其余标记为AFm3。可能是使用相同的DSCP标记了到达的流量，但一般来说，决定将其标记为相同值的额外复杂性是没有用的。因此，配置了一个“标记”操作，该操作由指向标记表项的操作表项组成。
At this point, the usual case is that traffic is now forwarded in the usual manner. To indicate this, the "SucceedNext" pointer of the Mark Action is set to zeroDotZero.
在这一点上，通常的情况是，现在以通常的方式转发通信量。为了表明这一点，标记操作的“SucceedNext”指针设置为zeroDotZero。
The EF class applies a Single Rate Two Color Meter, dividing traffic into "conforming" and "excess" groups. The intent, on the ingress interface at the edge of the network, is to measure and appropriately mark conforming traffic and drop the excess.
EF等级采用单速率双色表，将流量分为“合格”和“过量”两组。在网络边缘的入口接口上，目的是测量并适当标记符合要求的流量，并丢弃多余的流量。
A single rate two color (srTCM) meter requires one token bucket. It is therefore configured using a single meter entry with a corresponding Token Bucket Parameter Entry. Arriving traffic either "succeeds" or "fails".
单速率双色（srTCM）仪表需要一个令牌桶。因此，可以使用带有相应令牌桶参数条目的单个仪表条目对其进行配置。到达的流量要么“成功”，要么“失败”。
For network planning and perhaps for billing purposes, arriving traffic that conforms to the meter is normally counted. Therefore, a "count" action, consisting of an action table entry pointing to a count table entry, is configured.
对于网络规划，或者出于计费目的，通常会计算符合电表的到达流量。因此，配置了“计数”操作，该操作由指向计数表项的操作表项组成。
Also, traffic is (re)marked with the EF DSCP. Therefore, a "mark" action, consisting of an action table entry pointing to a mark table entry, is configured.
此外，使用EF DSCP（重新）标记通信量。因此，配置了一个“标记”操作，该操作由指向标记表项的操作表项组成。
At this point, the successful traffic is now forwarded in the usual manner. To indicate this, the "SucceedNext" pointer of the Mark Action is set to zeroDotZero.
此时，成功的流量现在以通常的方式转发。为了表明这一点，标记操作的“SucceedNext”指针设置为zeroDotZero。
Traffic that exceeded the arrival policy, however, is to be dropped. One can use a count action on this traffic if the several counters are interesting. However, since the drop counter in the Algorithmic Drop Entry will count packets dropped, this is not clearly necessary. An Algorithmic Drop Entry of the type "alwaysDrop" with no successor is sufficient.
但是，将丢弃超过到达策略的流量。如果多个计数器感兴趣，可以对该流量使用计数操作。然而，由于算法丢弃条目中的丢弃计数器将对丢弃的数据包进行计数，这显然不是必需的。“alwaysDrop”类型的算法删除条目（没有后继项）就足够了。
A packet arriving at an egress interface may have been classified on an ingress interface, and the egress interface may have access to that information. If it is relevant, there is no reason not to use that information. If it is not available, however, there may be a need to (re)classify on the egress interface. In any event, it picks up its "program" from the diffServDataPathTable. This points to a classifier, which will select traffic according to some specification for each traffic class.
到达出口接口的分组可以在入口接口上被分类，并且出口接口可以访问该信息。如果相关，没有理由不使用该信息。但是，如果不可用，则可能需要在出口接口上（重新）分类。在任何情况下，它都会从diffServDataPathTable中获取其“程序”。这指向一个分类器，它将根据每个流量类别的某些规范选择流量。
+-----------------------+
| diffServDataPathStart |
+-----------+-----------+
|
+----------+
|
+--+--+ +-----+ +-----+ +-----+ +-----+
| AF1 +-----+ AF2 +-----+ AF3 +-----+ AF4 +-----+ EF |
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
|trTCM| |trTCM| |trTCM| |trTCM| |srTCM|
|Meter| |Meter| |Meter| |Meter| |Meter|
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+||---+ +-+||---+ +-+||---+ +-+||---+ +-+-|---+
|+-+|----+ |+-+|----+ |+-+|----+ |+-+|----+ |+--+----+
||+-+-----+ ||+-+-----+ ||+-+-----+ ||+-+-----+ ||Actions|
+||Actions| +||Actions| +||Actions| +||Actions| +| |
+| | +| | +| | +| | +-+-----+
+-+-----+ +-+-----+ +-+-----+ +-+-----+ |
||| ||| ||| ||| |
+-+++--+ +-+++--+ +-+++--+ +-+++--+ +--+---+
| Queue| | Queue| | Queue| | Queue| | Queue|
+--+---+ +--+---+ +--+---+ +--+---+ +--+---+
| | | | |
+--+-----------+-----------+-----------+---+ |
| WFQ/WRR Scheduler | |
+--------------------------------------+---+ |
| |
+-----+-----------+----+
| Priority Scheduler |
+----------+-----------+
|
V
+-----------------------+
| diffServDataPathStart |
+-----------+-----------+
|
+----------+
|
+--+--+ +-----+ +-----+ +-----+ +-----+
| AF1 +-----+ AF2 +-----+ AF3 +-----+ AF4 +-----+ EF |
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
|trTCM| |trTCM| |trTCM| |trTCM| |srTCM|
|Meter| |Meter| |Meter| |Meter| |Meter|
+-+++-+ +-+++-+ +-+++-+ +-+++-+ +-+-+-+
||| ||| ||| ||| | |
+-+||---+ +-+||---+ +-+||---+ +-+||---+ +-+-|---+
|+-+|----+ |+-+|----+ |+-+|----+ |+-+|----+ |+--+----+
||+-+-----+ ||+-+-----+ ||+-+-----+ ||+-+-----+ ||Actions|
+||Actions| +||Actions| +||Actions| +||Actions| +| |
+| | +| | +| | +| | +-+-----+
+-+-----+ +-+-----+ +-+-----+ +-+-----+ |
||| ||| ||| ||| |
+-+++--+ +-+++--+ +-+++--+ +-+++--+ +--+---+
| Queue| | Queue| | Queue| | Queue| | Queue|
+--+---+ +--+---+ +--+---+ +--+---+ +--+---+
| | | | |
+--+-----------+-----------+-----------+---+ |
| WFQ/WRR Scheduler | |
+--------------------------------------+---+ |
| |
+-----+-----------+----+
| Priority Scheduler |
+----------+-----------+
|
V
Figure 8: combined EF and AF implementation
图8：EF和AF的组合实现
An example of a classifier for an AFm class would be a succession of three classifier elements, each pointing to a Multi-field classification parameter block identifying one of the AFmn DSCPs. Alternatively, the filter might contain selectors for HTTP traffic or some other application.
AFm类分类器的一个示例是连续的三个分类器元素，每个元素指向识别AFmn DSCP之一的多字段分类参数块。或者，过滤器可能包含HTTP流量或其他应用程序的选择器。
An example of a classifier for EF traffic might be either a classifier element pointing to a Multi-field parameter specifying the EF code point, or a collection of classifiers with parameter blocks specifying individual telephone calls, or a variety of other approaches.
EF业务的分类器的示例可以是指向指定EF码点的多字段参数的分类器元素，或者具有指定单个电话呼叫的参数块的分类器集合，或者各种其他方法。
Each classifier delivers traffic to appropriate functional data path elements.
每个分类器将流量传递到适当的功能数据路径元素。
Each AFm class applies a Two Rate Three Color Meter, dividing traffic into three groups. These groups of traffic conform to both specified rates, only the higher one, or none. The intent, on the ingress interface at the edge of the network, is to measure and appropriately mark traffic.
每个AFm等级应用一个双速率三色表，将交通分为三组。这些流量组符合两个指定的速率，只有较高的速率，或者不符合。在网络边缘的入口接口上，目的是测量并适当标记流量。
Each AFm class applies a Two Rate Three Color Meter, dividing traffic into three groups. If two rates R and S, where R < S, are specified and traffic arrives at rate T, traffic comprising up to R bits per second is considered to conform to the "confirmed" rate, R. If R < T, traffic comprising up to S-R bits per second is considered to conform to the "excess" rate, S. Any further excess is non-conformant.
每个AFm等级应用一个双速率三色表，将交通分为三组。如果指定了两个速率R和S，其中R<S，并且流量达到速率T，则认为每秒最多R比特的流量符合“确认”速率R。如果R<T，每秒最多S-R比特的流量符合“超额”速率S。任何进一步的超额都是不符合的。
Two meter entries are used to configure this, one for the conforming rate and one for the excess rate. The rate parameters are stored in associated Token Bucket Parameter Entries. The "FailNext" pointer of the lower rate Meter Entry points to the other Meter Entry; both "SucceedNext" pointers and the "FailNext" pointer of the higher Meter Entry point to lists of actions. In the color-blind mode, all three classifier "next" entries point to the lower rate meter entry. In the color-aware mode, the AFm1 classifier points to the lower rate entry, the AFm2 classifier points to the higher rate entry (as it is only compared against that rate), and the AFm3 classifier points directly to the actions taken when both rates fail.
两个仪表条目用于配置，一个用于合格率，另一个用于超额率。速率参数存储在相关的令牌桶参数条目中。低速率仪表入口的“FailNext”指针指向另一个仪表入口；较高仪表入口的“SucceedNext”指针和“FailNext”指针都指向操作列表。在色盲模式下，所有三个分类器“下一个”条目都指向低速率仪表条目。在颜色感知模式下，AFm1分类器指向低速率条目，AFm2分类器指向高速率条目（因为它仅与该速率进行比较），AFm3分类器直接指向两个速率均失败时采取的操作。
+-----------------------------------------------------+
| Classifier |
+--------+--------------------------------------------+
|Green| Yellow| Red
| | |
+--+-----+-------+--+ Fail +--------------------+
| Meter +------+ Meter |
+--+----------------+ +---+-------+--------+
| Succeed (Green) | |Fail (Red)
| +---------+ |
| | Succeed (Yellow)|
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
|Mark AFx1| |Mark AFx2| |Mark AFx3|
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
+-----------------------------------------------------+
| Classifier |
+--------+--------------------------------------------+
|Green| Yellow| Red
| | |
+--+-----+-------+--+ Fail +--------------------+
| Meter +------+ Meter |
+--+----------------+ +---+-------+--------+
| Succeed (Green) | |Fail (Red)
| +---------+ |
| | Succeed (Yellow)|
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
|Mark AFx1| |Mark AFx2| |Mark AFx3|
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
Figure 9a: Typical AF Edge egress interface configuration, using color-blind meters
图9a：使用色盲计的典型AF边缘出口接口配置
+-----------------------------------------------------+
| Classifier |
+--------+--------------------------------------------+
|Green | Yellow | Red
| | |
+----+----+ +----+----+ |
| Count | | Count | |
| Action +-------+ Action +------------+
+----+----+ Fail +----+----+ Fail |
|Succeed |Succeed |
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
|Mark AFx1| |Mark AFx2| |Mark AFx3|
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
+-----------------------------------------------------+
| Classifier |
+--------+--------------------------------------------+
|Green | Yellow | Red
| | |
+----+----+ +----+----+ |
| Count | | Count | |
| Action +-------+ Action +------------+
+----+----+ Fail +----+----+ Fail |
|Succeed |Succeed |
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
|Mark AFx1| |Mark AFx2| |Mark AFx3|
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
Figure 9b: Typical AF Edge egress interface configuration, using color-aware meters
图9b：使用颜色感知仪表的典型AF边缘出口接口配置
+-----------------------------------------------------+
| Classifier |
+--------+-----------------+-----------------+--------+
| Green | Yellow | Red
| | |
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
+-----------------------------------------------------+
| Classifier |
+--------+-----------------+-----------------+--------+
| Green | Yellow | Red
| | |
+----+----+ +----+----+ +----+----+
| Count | | Count | | Count |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+----+----+ +----+----+ +----+----+
| Random | | Random | | Random |
| Drop | | Drop | | Drop |
| Action | | Action | | Action |
+----+----+ +----+----+ +----+----+
| | |
+--------+-----------------+-----------------+--------+
| Queue |
+--------------------------+--------------------------+
|
+----+----+
| Rate |
|Scheduler|
+----+----+
|
Figure 10: Typical AF Edge core interface configuration
图10：典型的AF边缘核心接口配置
For network planning and perhaps for billing purposes, departing traffic is normally counted. Therefore, a "count" action, consisting of an action table entry pointing to a count table entry, is configured.
对于网络规划，或者出于计费目的，通常会计算离开的流量。因此，配置了“计数”操作，该操作由指向计数表项的操作表项组成。
Also, traffic may be marked with an appropriate DSCP. The first R bits per second are marked AFm1, the next S-R bits per second are marked AFm2, and the rest is marked AFm3. It may be that traffic is arriving marked with the same DSCP, but in general, the additional complexity of deciding that it is being remarked to the same value is not useful. Therefore, a "mark" action, consisting of an action table entry pointing to a mark table entry, is configured.
此外，可以使用适当的DSCP标记通信量。每秒第一个R位标记为AFm1，每秒下一个S-R位标记为AFm2，其余标记为AFm3。可能是使用相同的DSCP标记了到达的流量，但一般来说，决定将其标记为相同值的额外复杂性是没有用的。因此，配置了一个“标记”操作，该操作由指向标记表项的操作表项组成。
At this point, the usual case is that traffic is now queued for transmission. The queue uses Active Queue Management, using an algorithm such as RED. Therefore, an Algorithmic Dropper is
在这一点上，通常的情况是流量现在排队等待传输。队列使用活动队列管理，使用诸如RED之类的算法。因此，需要一种算法滴管
configured for each AFmn traffic stream, with a slightly lower min-threshold (and possibly lower max-threshold) for the excess traffic than for the committed traffic.
为每个AFmn流量流配置，与提交流量相比，额外流量的最小阈值（可能更低的最大阈值）稍低。
The queue expected by AF is normally a work-conserving queue. It usually has a specified minimum rate, and may have a maximum rate below the bandwidth of the interface. In concept, it will use as much bandwidth as is available to it, but assure the lower bound.
AF所期望的队列通常是一个保存工作的队列。它通常具有指定的最小速率，并且可能具有低于接口带宽的最大速率。在概念上，它将使用尽可能多的可用带宽，但要确保下限。
Common ways to implement this include various forms of Weighted Fair Queuing (WFQ) or Weighted Round Robin (WRR). Integrated over a longer interval, these give each class a predictable throughput rate. They differ in that over short intervals they will order traffic differently. In general, traffic classes that keep traffic in queue will tend to absorb latency from queues with lower mean occupancy, in exchange for which they make use of any available capacity.
实现这一点的常用方法包括各种形式的加权公平排队（WFQ）或加权循环（WRR）。在较长的时间间隔内进行集成，可以为每个类提供可预测的吞吐量。他们的不同之处在于，在较短的时间间隔内，他们会以不同的方式安排交通。一般来说，将流量保持在队列中的流量类别将倾向于从平均占用率较低的队列中吸收延迟，作为交换，它们将利用任何可用容量。
The EF class applies a Single Rate Two Color Meter, dividing traffic into "conforming" and "excess" groups. The intent, on the egress interface at the edge of the network, is to measure and appropriately mark conforming traffic and drop the excess.
EF等级采用单速率双色表，将流量分为“合格”和“过量”两组。在网络边缘的出口接口上，目的是测量并适当标记符合要求的流量，并丢弃多余的流量。
A single rate two color (srTCM) meter requires one token bucket. It is therefore configured using a single meter entry with a corresponding Token Bucket Parameter Entry. Arriving traffic either "succeeds" or "fails".
单速率双色（srTCM）仪表需要一个令牌桶。因此，可以使用带有相应令牌桶参数条目的单个仪表条目对其进行配置。到达的流量要么“成功”，要么“失败”。
For network planning and perhaps for billing purposes, departing traffic that conforms to the meter is normally counted. Therefore, a "count" action, consisting of an action table entry pointing to a count table entry, is configured.
对于网络规划，或者出于计费目的，通常统计符合电表要求的离开流量。因此，配置了“计数”操作，该操作由指向计数表项的操作表项组成。
Also, traffic is (re)marked with the EF DSCP. Therefore, a "mark" action, consisting of an action table entry pointing to a mark table entry, is configured.
此外，使用EF DSCP（重新）标记通信量。因此，配置了一个“标记”操作，该操作由指向标记表项的操作表项组成。
+-----------------------------------------------------+
| Classifier |
+-------------------------+---------------------------+
| Voice
|
+-------------+----------+
| Meter |
+----+-------------+-----+
| Succeed | Fail
| |
+----+----+ +----+----+
| Count | | Always |
| Action | | Drop |
+----+----+ | Action |
| +---------+
+----+---------+
| Algorithmic |
| Drop Action |
+----+---------+
|
+----------------+---------------+
| Queue |
+----------------+---------------+
|
+-----+-----+
| Priority |
| Scheduler |
+-----+-----+
+-----------------------------------------------------+
| Classifier |
+-------------------------+---------------------------+
| Voice
|
+-------------+----------+
| Meter |
+----+-------------+-----+
| Succeed | Fail
| |
+----+----+ +----+----+
| Count | | Always |
| Action | | Drop |
+----+----+ | Action |
| +---------+
+----+---------+
| Algorithmic |
| Drop Action |
+----+---------+
|
+----------------+---------------+
| Queue |
+----------------+---------------+
|
+-----+-----+
| Priority |
| Scheduler |
+-----+-----+
Figure 11: Typical EF Edge (Policing) Configuration
图11：典型EF边缘（监管）配置
+--------------------------------+
| Classifier |
+----------------+---------------+
| Voice
|
+----+----+
| Count |
| Action |
+----+----+
|
+------+-------+
| Algorithmic |
| Drop Action |
+------+-------+
|
+----------------+---------------+
| Queue |
+----------------+---------------+
|
+-----+-----+
| Priority |
| Scheduler |
+-----+-----+
+--------------------------------+
| Classifier |
+----------------+---------------+
| Voice
|
+----+----+
| Count |
| Action |
+----+----+
|
+------+-------+
| Algorithmic |
| Drop Action |
+------+-------+
|
+----------------+---------------+
| Queue |
+----------------+---------------+
|
+-----+-----+
| Priority |
| Scheduler |
+-----+-----+
Figure 12: Typical EF Core interface Configuration
图12：典型EF核心接口配置
At this point, the successful traffic is now queued for transmission, using a priority queue or perhaps a rate-based queue with significant over-provision. Since the amount of traffic present is known, one might not drop from this queue at all.
此时，成功的流量现在排队等待传输，使用优先级队列，或者可能是基于速率的队列，具有明显的过度供应。由于存在的通信量是已知的，因此可能根本不会从该队列中删除。
Traffic that exceeded the policy, however, is dropped. A count action can be used on this traffic if the several counters are interesting. However, since the drop counter in the Algorithmic Drop Entry will count packets dropped, this is not clearly necessary. An Algorithmic Drop Entry of the type "alwaysDrop" with no successor is sufficient.
但是，超过策略的流量将被丢弃。如果多个计数器感兴趣，则可以在此通信量上使用计数操作。然而，由于算法丢弃条目中的丢弃计数器将对丢弃的数据包进行计数，这显然不是必需的。“alwaysDrop”类型的算法删除条目（没有后继项）就足够了。
The normal implementation is a priority queue, to minimize induced jitter. A separate queue is used for each EF class, with a strict ordering.
通常的实现是一个优先级队列，以最小化诱导抖动。每个EF类使用一个单独的队列，并具有严格的顺序。
RowPointer is a textual convention used to identify a conceptual row in a MIB Table by pointing to one of its objects. One of the ways this MIB uses it is to indicate succession, pointing to data path linkage table entries.
RowPointer是一种文本约定，用于通过指向MIB表中的一个对象来标识概念行。此MIB使用它的方式之一是指示继承，指向数据路径链接表条目。
For succession, it answers the question "what happens next?". Rather than presume that the next table must be as specified in the conceptual model [MODEL] and providing its index, the RowPointer takes you to the MIB row representing that thing. In the diffServMeterTable, for example, the diffServMeterFailNext RowPointer might take you to another meter, while the diffServMeterSucceedNext RowPointer would take you to an action.
对于继任，它回答了“接下来会发生什么”的问题。RowPointer不会假定下一个表必须是概念模型[model]中指定的并提供其索引，而是将您带到表示该表的MIB行。例如，在diffServMeterTable中，diffServMeterFailNext行指针可能会将您带到另一个仪表，而diffServMeterSucceedNext行指针则会将您带到一个操作。
Since a RowPointer is not tied to any specific object except by the value it contains, it is possible and acceptable to use RowPointers to merge data paths. An obvious example of such a use is in the classifier: traffic matching the DSCPs AF11, AF12, and AF13 might be presented to the same meter in order to perform the processing described in the Assured Forwarding PHB. Another use would be to merge data paths from several interfaces; if they represent a single service contract, having them share a common set of counters and common policy may be a desirable configuration. Note well, however, that such configurations may have related implementation issues - if Differentiated Services processing for the interfaces is implemented in multiple forwarding engines, the engines will need to communicate if they are to implement such a feature. An implementation that fails to provide this capability is not considered to have failed the intention of this MIB or of the [MODEL]; an implementation that does provide it is not considered superior from a standards perspective.
由于行指针除了其包含的值外，不绑定到任何特定对象，因此可以使用行指针合并数据路径。这种用途的一个明显例子是在分类器中：匹配DSCPs AF11、AF12和AF13的通信量可以呈现给同一仪表，以便执行保证转发PHB中描述的处理。另一个用途是合并来自多个接口的数据路径；如果它们表示单个服务契约，那么让它们共享一组公共计数器和公共策略可能是一种理想的配置。但是，请注意，此类配置可能存在相关的实现问题-如果在多个转发引擎中实现了接口的差异化服务处理，则引擎将需要进行通信才能实现此类功能。未能提供此功能的实现不被视为未达到此MIB或[模型]的目的；从标准的角度来看，一个提供了它的实现并不被认为是优越的。
NOTE -- the RowPointer construct is used to connect the functional data paths. The [MODEL] describes these as TCBs, as an aid to understanding. This MIB, however, does not model TCBs directly. It operates at a lower level of abstraction using only individual elements, connected in succession by RowPointers. Therefore, the concept of TCBs enclosing individual Functional Data Path elements is not directly applicable to this MIB, although management tools that use this MIB may employ such a concept.
注意——RowPointer构造用于连接函数数据路径。[模型]将其描述为TCB，以帮助理解。但是，此MIB不直接为TCB建模。它只使用单个元素在较低的抽象级别上运行，这些元素通过行指针连续连接。因此，包含单个功能数据路径元素的TCB的概念并不直接适用于此MIB，尽管使用此MIB的管理工具可能采用这种概念。
It is possible that a path through a device following a set of RowPointers is indeterminate i.e. it ends in a dangling RowPointer. Guidance is provided in the MIB module's DESCRIPTION-clause for each of the linkage attribute. In general, for both zeroDotZero and dangling RowPointer, it is assumed the data path ends and the traffic
在一组RowPointer之后通过设备的路径可能是不确定的，即它以悬挂的RowPointer结束。MIB模块的DESCRIPTION子句中为每个链接属性提供了指导。通常，对于zeroDotZero和悬空行指针，都假定数据路径结束，通信量减少
should be given to the next logical part of the device, usually a forwarding process or a transmission engine, or the proverbial bit-bucket. Any variation from this usage is indicated by the attribute affected.
应该被赋予设备的下一个逻辑部分，通常是转发过程或传输引擎，或众所周知的位桶。此用法的任何变化都由受影响的属性指示。
RowPointer is also used in this MIB to indicate parameterization, for pointing to parameterization table entries.
RowPointer在这个MIB中还用于指示参数化，用于指向参数化表条目。
For indirection (as in the diffServClfrElementTable), the idea is to allow other MIBs, including proprietary ones, to define new and arcane filters - MAC headers, IPv4 and IPv6 headers, BGP Communities and all sorts of other things - while still utilizing the structures of this MIB. This is a form of class inheritance (in "object oriented" language): it allows base object definitions ("classes") to be extended in proprietary or standard ways, in the future, by other documents.
对于间接寻址（如在diffServClfrElementTable中），我们的想法是允许其他MIB（包括专有的MIB）定义新的和神秘的过滤器——MAC头、IPv4和IPv6头、BGP社区和各种其他东西——同时仍然使用此MIB的结构。这是类继承的一种形式（在“面向对象”语言中）：它允许基础对象定义（“类”）在将来通过其他文档以专有或标准的方式进行扩展。
RowPointer also clearly indicates the identified conceptual row's content does not change, hence they can be simultaneously used and pointed to, by more than one data path linkage table entries. The identification of RowPointer allows higher level policy mechanisms to take advantage of this characteristic.
RowPointer还清楚地表明标识的概念行的内容没有更改，因此可以由多个数据路径链接表条目同时使用和指向它们。RowPointer的标识允许更高级别的策略机制利用此特性。
A number of conceptual tables defined in this MIB use as an index an arbitrary integer value, unique across the scope of the agent. In order to help with multi-manager row-creation problems, a mechanism must be provided to allow a manager to obtain unique values for such an index and to ensure that, when used, the manager knows whether it got what it wanted or not.
此MIB中定义的许多概念表使用任意整数值作为索引，该值在代理范围内是唯一的。为了帮助解决多管理器行创建问题，必须提供一种机制，以允许管理器获取此类索引的唯一值，并确保在使用时，管理器知道它是否得到了想要的。
Typically, such a table has an associated NextFree variable e.g. diffServClfrNextFree which provides a suitable value for the index of the next row to be created e.g. diffServClfrId. The value zero is used to indicate that the agent can configure no more entries. The table also has a columnar Status attribute with RowStatus syntax [RFC 2579].
通常，这样的表具有相关联的NextFree变量，例如diffServClfrNextFree，该变量为要创建的下一行的索引（例如diffServClfrId）提供合适的值。值0用于指示代理无法配置更多条目。该表还有一个具有RowStatus语法[RFC2579]的列状态属性。
Generally, if a manager attempts to create a row, the agent will create the row and return success. If the agent has insufficient resources or such a row already exists, then it returns an error. A manager must be prepared to try again in such circumstances, probably by re-reading the NextFree to obtain a new index value in case a second manager had got in between the first manager's read of the NextFree value and the first manager's row-creation attempt.
通常，如果管理器尝试创建行，代理将创建该行并返回成功。如果代理没有足够的资源或者这样的行已经存在，那么它将返回一个错误。管理器必须准备在这种情况下重试，可能是通过重新读取NextFree来获得新的索引值，以防第二个管理器在第一个管理器读取NextFree值和第一个管理器尝试创建行之间出现。
To simplify management creation and deletion of rows in this MIB, the agent is expected to assist in maintaining its consistency. It may accomplish this by maintaining internal usage counters for any row that might be pointed to by a RowPointer, or by any equivalent means. When a RowPointer is created or written, and the row it points to does not exist, the SET returns an inconsistentValue error. When a RowStatus variable is set to 'destroy' but the usage counter is non-zero, the SET returns no error but the indicated row is left intact. The agent should later remove the row in the event that the usage counter becomes zero.
为了简化管理此MIB中行的创建和删除，代理将帮助维护其一致性。它可以通过维护行指针或任何等效方法指向的任何行的内部使用计数器来实现这一点。创建或写入行指针时，如果它所指向的行不存在，集合将返回一个不一致的值错误。当RowStatus变量设置为“destroy”但使用计数器为非零时，该集不会返回错误，但指示的行保持不变。如果使用率计数器变为零，代理应稍后删除该行。
The use of RowStatus is covered in more detail in [RFC 2579].
[RFC 2579]中详细介绍了RowStatus的使用。
With the structures of this MIB divided into data path linkage tables and parameterization tables, and with the use of RowPointer, new data path linkage and parameterization tables can be defined in other MIB modules, and used with tables defined in this MIB. This MIB does not limit the type of entries its RowPointer attributes can point to, hence new functional data path elements can be defined in other MIBs and integrated with functional data path elements of this MIB. For example, new Action functional data path element can be defined for Traffic Engineering and be integrated with Differentiated Services functional data path elements, possibly used within the same data path sharing the same classifiers and meters.
通过将此MIB的结构分为数据路径链接表和参数化表，并使用RowPointer，可以在其他MIB模块中定义新的数据路径链接和参数化表，并与此MIB中定义的表一起使用。此MIB不限制其RowPointer属性可以指向的条目类型，因此可以在其他MIB中定义新的功能数据路径元素，并与此MIB的功能数据路径元素集成。例如，可以为流量工程定义新的动作功能数据路径元素，并与差异化服务功能数据路径元素集成，可能在共享相同分类器和仪表的相同数据路径中使用。
It is more likely that new parameterization tables will be created in other MIBs as new methods or proprietary methods get deployed for existing Differentiated Services Functional Data Path Elements. For example, different kinds of filters can be defined by using new filter parameterization tables. New scheduling methods can be deployed by defining new scheduling method OIDs and new scheduling parameter tables.
随着为现有区分服务功能数据路径元素部署新方法或专有方法，更有可能在其他MIB中创建新的参数化表。例如，可以通过使用新的过滤器参数化表来定义不同类型的过滤器。通过定义新的调度方法OID和新的调度参数表，可以部署新的调度方法。
Notice both new data path linkage tables and parameterization tables can be added without needing to change this MIB document or affect existing tables and their usage.
请注意，可以添加新的数据路径链接表和参数化表，而无需更改此MIB文档或影响现有表及其使用。
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN
IMPORTS Integer32, MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
从SNMPv2中导入整数32、模块标识、mib-2，从SNMPv2 TC中导入SMI文本约定；
diffServDSCPTC MODULE-IDENTITY LAST-UPDATED "200205090000Z" ORGANIZATION "IETF Differentiated Services WG" CONTACT-INFO " Fred Baker Cisco Systems 1121 Via Del Rey Santa Barbara, CA 93117, USA E-mail: fred@cisco.com
diffServDSCPTC MODULE-IDENTITY最新更新的“20020509000Z”组织“IETF差异化服务工作组”联系人信息“Fred Baker Cisco Systems 1121，通过美国加利福尼亚州圣巴巴拉市Del Rey Santa Barbara发送电子邮件：fred@cisco.com
Kwok Ho Chan Nortel Networks 600 Technology Park Drive Billerica, MA 01821, USA E-mail: khchan@nortelnetworks.com
郭浩灿北电网络美国马萨诸塞州比利里卡科技园路600号邮编01821电子邮件：khchan@nortelnetworks.com
Andrew Smith Harbour Networks Jiuling Building 21 North Xisanhuan Ave. Beijing, 100089, PRC E-mail: ah_smith@acm.org
中国北京西三环北路21号安德鲁·史密斯港湾网络九陵大厦，邮编100089电子邮件：啊_smith@acm.org
Differentiated Services Working Group:
diffserv@ietf.org"
DESCRIPTION
"The Textual Conventions defined in this module should be used
whenever a Differentiated Services Code Point is used in a MIB."
REVISION "200205090000Z"
DESCRIPTION
"Initial version, published as RFC 3289."
::= { mib-2 96 }
Differentiated Services Working Group:
diffserv@ietf.org"
DESCRIPTION
"The Textual Conventions defined in this module should be used
whenever a Differentiated Services Code Point is used in a MIB."
REVISION "200205090000Z"
DESCRIPTION
"Initial version, published as RFC 3289."
::= { mib-2 96 }
Dscp ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A Differentiated Services Code-Point that may be used for
marking a traffic stream."
REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (0..63)
Dscp ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A Differentiated Services Code-Point that may be used for
marking a traffic stream."
REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (0..63)
DscpOrAny ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The IP header Differentiated Services Code-Point that may be
DscpOrAny ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The IP header Differentiated Services Code-Point that may be
used for discriminating among traffic streams. The value -1 is used to indicate a wild card i.e. any value." REFERENCE "RFC 2474, RFC 2780" SYNTAX Integer32 (-1 | 0..63)
用于区分交通流。值-1用于表示通配符，即任何值。“参考”RFC 2474，RFC 2780“语法整数32（-1 | 0..63）
END
终止
DIFFSERV-MIB DEFINITIONS ::= BEGIN
DIFFSERV-MIB DEFINITIONS ::= BEGIN
IMPORTS Unsigned32, Counter64, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, zeroDotZero, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, RowPointer, StorageType, AutonomousType FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex, InterfaceIndexOrZero FROM IF-MIB InetAddressType, InetAddress, InetAddressPrefixLength, InetPortNumber FROM INET-ADDRESS-MIB BurstSize FROM INTEGRATED-SERVICES-MIB Dscp, DscpOrAny FROM DIFFSERV-DSCP-TC;
从SNMPv2 SMI文本约定导入Unsigned32、Counter64、MODULE-IDENTITY、OBJECT-TYPE、OBJECT-IDENTITY、zeroDotZero、mib-2，从SNMPv2 TC MODULE-COMPLIANCE导入RowStatus、RowPointer、StorageType、AutonomousType，从SNMPv2 CONF iIndex导入OBJECT-GROUP，从IF-mib InetAddressType导入InterfaceIndexOrZero、InetAddress、inetAddressPrefixleth，来自INET-ADDRESS-MIB的InetPortNumber来自INTEGRATED-SERVICES-MIB Dscp的BurstSize，来自DIFFSERV-Dscp-TC的DscpOrAny；
diffServMib MODULE-IDENTITY LAST-UPDATED "200202070000Z" ORGANIZATION "IETF Differentiated Services WG" CONTACT-INFO " Fred Baker Cisco Systems 1121 Via Del Rey Santa Barbara, CA 93117, USA E-mail: fred@cisco.com
diffServMib MODULE-IDENTITY最近更新的“200202070000Z”组织“IETF差异化服务工作组”联系人信息“Fred Baker Cisco Systems 1121，通过美国加利福尼亚州圣巴巴拉市Del Rey Santa Barbara发送电子邮件：fred@cisco.com
Kwok Ho Chan Nortel Networks 600 Technology Park Drive Billerica, MA 01821, USA E-mail: khchan@nortelnetworks.com
郭浩灿北电网络美国马萨诸塞州比利里卡科技园路600号邮编01821电子邮件：khchan@nortelnetworks.com
Andrew Smith Harbour Networks Jiuling Building
安德鲁·史密斯港湾网络九陵大厦
21 North Xisanhuan Ave. Beijing, 100089, PRC E-mail: ah_smith@acm.org
中国北京西三环北路21号，100089电子邮件：啊_smith@acm.org
Differentiated Services Working Group:
diffserv@ietf.org"
DESCRIPTION
"This MIB defines the objects necessary to manage a device that
uses the Differentiated Services Architecture described in RFC
2475. The Conceptual Model of a Differentiated Services Router
provides supporting information on how such a router is modeled."
REVISION "200202070000Z"
DESCRIPTION
"Initial version, published as RFC 3289."
::= { mib-2 97 }
Differentiated Services Working Group:
diffserv@ietf.org"
DESCRIPTION
"This MIB defines the objects necessary to manage a device that
uses the Differentiated Services Architecture described in RFC
2475. The Conceptual Model of a Differentiated Services Router
provides supporting information on how such a router is modeled."
REVISION "200202070000Z"
DESCRIPTION
"Initial version, published as RFC 3289."
::= { mib-2 97 }
diffServMIBObjects OBJECT IDENTIFIER ::= { diffServMib 1 }
diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 2 }
diffServMIBAdmin OBJECT IDENTIFIER ::= { diffServMib 3 }
diffServMIBObjects OBJECT IDENTIFIER ::= { diffServMib 1 }
diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 2 }
diffServMIBAdmin OBJECT IDENTIFIER ::= { diffServMib 3 }
IndexInteger ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer which may be used as a table index."
SYNTAX Unsigned32 (1..4294967295)
IndexInteger ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer which may be used as a table index."
SYNTAX Unsigned32 (1..4294967295)
IndexIntegerNextFree ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer which may be used as a new Index in a table.
IndexIntegerNextFree ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer which may be used as a new Index in a table.
The special value of 0 indicates that no more new entries can be created in the relevant table.
特殊值0表示无法在相关表中创建更多新条目。
When a MIB is used for configuration, an object with this SYNTAX always contains a legal value (if non-zero) for an index that is not currently used in the relevant table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use,
当MIB用于配置时，具有此语法的对象始终包含当前未在相关表中使用的索引的合法值（如果非零）。命令生成器（网络管理应用程序）读取此变量，并在使用SNMP集创建新行时使用读取的（非零）值。执行设置时，命令响应程序（代理）必须确定该值是否确实仍然未使用；两个网络管理应用程序可能试图同时创建一行（配置条目），并使用相同的值。如果该对象当前未使用，则该集合将成功，并且命令响应程序（代理）将根据特定于实现的算法更改该对象的值。如果该值正在使用中，
however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value.
但是，设置失败。然后，网络管理应用程序必须重新读取此变量以获得新的可用值。
An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality." SYNTAX Unsigned32 (0..4294967295)
使用此语法的对象类型定义必须指定对象为其提供此功能的相关表。“SYNTAX Unsigned32（0..4294967295）
IfDirection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IfDirection specifies a direction of data travel on an
interface. 'inbound' traffic is operated on during reception from
the interface, while 'outbound' traffic is operated on prior to
transmission on the interface."
SYNTAX INTEGER {
inbound(1), -- ingress interface
outbound(2) -- egress interface
}
IfDirection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IfDirection specifies a direction of data travel on an
interface. 'inbound' traffic is operated on during reception from
the interface, while 'outbound' traffic is operated on prior to
transmission on the interface."
SYNTAX INTEGER {
inbound(1), -- ingress interface
outbound(2) -- egress interface
}
-- -- Data Path --
----数据路径--
diffServDataPath OBJECT IDENTIFIER ::= { diffServMIBObjects 1 }
diffServDataPath OBJECT IDENTIFIER ::= { diffServMIBObjects 1 }
--
-- Data Path Table
--
-- The Data Path Table enumerates the Differentiated Services
-- Functional Data Paths within this device. Each entry in this table
-- is indexed by ifIndex and ifDirection. Each entry provides the
-- first Differentiated Services Functional Data Path Element to
-- process data flowing along specific data path. This table should
-- have at most two entries for each interface capable of
-- Differentiated Services processing on this device: ingress and
-- egress.
--
-- Data Path Table
--
-- The Data Path Table enumerates the Differentiated Services
-- Functional Data Paths within this device. Each entry in this table
-- is indexed by ifIndex and ifDirection. Each entry provides the
-- first Differentiated Services Functional Data Path Element to
-- process data flowing along specific data path. This table should
-- have at most two entries for each interface capable of
-- Differentiated Services processing on this device: ingress and
-- egress.
-- Note that Differentiated Services Functional Data Path Elements
-- linked together using their individual next pointers and anchored by
-- an entry of the diffServDataPathTable constitute a functional data
-- path.
--
-- Note that Differentiated Services Functional Data Path Elements
-- linked together using their individual next pointers and anchored by
-- an entry of the diffServDataPathTable constitute a functional data
-- path.
--
diffServDataPathTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServDataPathEntry MAX-ACCESS not-accessible STATUS current
diffServDataPathTable DiffServDataPathEntry的对象类型语法序列MAX-ACCESS不可访问状态当前
DESCRIPTION
"The data path table contains RowPointers indicating the start of
the functional data path for each interface and traffic direction
in this device. These may merge, or be separated into parallel
data paths."
::= { diffServDataPath 1 }
DESCRIPTION
"The data path table contains RowPointers indicating the start of
the functional data path for each interface and traffic direction
in this device. These may merge, or be separated into parallel
data paths."
::= { diffServDataPath 1 }
diffServDataPathEntry OBJECT-TYPE SYNTAX DiffServDataPathEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the data path table indicates the start of a single Differentiated Services Functional Data Path in this device.
diffServDataPathEntry对象类型语法diffServDataPathEntry MAX-ACCESS不可访问状态当前描述“数据路径表中的条目表示此设备中单个区分服务功能数据路径的开始。
These are associated with individual interfaces, logical or physical, and therefore are instantiated by ifIndex. Therefore, the interface index must have been assigned, according to the procedures applicable to that, before it can be meaningfully used. Generally, this means that the interface must exist.
这些接口与单个接口（逻辑接口或物理接口）关联，因此由ifIndex实例化。因此，必须根据适用于接口索引的程序分配接口索引，然后才能有意义地使用接口索引。通常，这意味着接口必须存在。
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present."
INDEX { ifIndex, diffServDataPathIfDirection }
::= { diffServDataPathTable 1 }
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present."
INDEX { ifIndex, diffServDataPathIfDirection }
::= { diffServDataPathTable 1 }
DiffServDataPathEntry ::= SEQUENCE {
diffServDataPathIfDirection IfDirection,
diffServDataPathStart RowPointer,
diffServDataPathStorage StorageType,
diffServDataPathStatus RowStatus
}
DiffServDataPathEntry ::= SEQUENCE {
diffServDataPathIfDirection IfDirection,
diffServDataPathStart RowPointer,
diffServDataPathStorage StorageType,
diffServDataPathStatus RowStatus
}
diffServDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"IfDirection specifies whether the reception or transmission path
for this interface is in view."
::= { diffServDataPathEntry 1 }
diffServDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"IfDirection specifies whether the reception or transmission path
for this interface is in view."
::= { diffServDataPathEntry 1 }
diffServDataPathStart OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current
diffServDataPathStart对象类型语法行指针最大访问读取创建状态当前
DESCRIPTION "This selects the first Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry
DESCRIPTION“这将选择第一个区分服务功能数据路径元素来处理此数据路径的流量。此行指针应指向以下之一的实例：diffServClfrEntry diffServMeterEntry diffServActionEntry DiffServAlgProperty diffServQEntry
A value of zeroDotZero in this attribute indicates that no Differentiated Services treatment is performed on traffic of this data path. A pointer with the value zeroDotZero normally terminates a functional data path.
此属性中的值为zeroDotZero表示未对此数据路径的流量执行区分服务处理。值为zeroDotZero的指针通常终止函数数据路径。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServDataPathEntry 2 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServDataPathEntry 2 }
diffServDataPathStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServDataPathEntry 3 }
diffServDataPathStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServDataPathEntry 3 }
diffServDataPathStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time."
::= { diffServDataPathEntry 4 }
diffServDataPathStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time."
::= { diffServDataPathEntry 4 }
-- -- Classifiers --
----分类器--
diffServClassifier OBJECT IDENTIFIER ::= { diffServMIBObjects 2 }
diffServClassifier OBJECT IDENTIFIER ::= { diffServMIBObjects 2 }
--
--
-- Classifier Table
--
-- The Classifier Table allows multiple classifier elements, of same or
-- different types, to be used together. A classifier must completely
-- classify all packets presented to it. This means that all traffic
-- presented to a classifier must match at least one classifier element
-- within the classifier, with the classifier element parameters
-- specified by a filter.
-- Classifier Table
--
-- The Classifier Table allows multiple classifier elements, of same or
-- different types, to be used together. A classifier must completely
-- classify all packets presented to it. This means that all traffic
-- presented to a classifier must match at least one classifier element
-- within the classifier, with the classifier element parameters
-- specified by a filter.
-- If there is ambiguity between classifier elements of different
-- classifier, classifier linkage order indicates their precedence; the
-- first classifier in the link is applied to the traffic first.
-- If there is ambiguity between classifier elements of different
-- classifier, classifier linkage order indicates their precedence; the
-- first classifier in the link is applied to the traffic first.
-- Entries in the classifier element table serves as the anchor for
-- each classification pattern, defined in filter table entries. Each
-- classifier element table entry also specifies the subsequent
-- downstream Differentiated Services Functional Data Path Element when
-- the classification pattern is satisfied. Each entry in the
-- classifier element table describes one branch of the fan-out
-- characteristic of a classifier indicated in the Informal
-- Differentiated Services Model section 4.1. A classifier is composed
-- of one or more classifier elements.
-- Entries in the classifier element table serves as the anchor for
-- each classification pattern, defined in filter table entries. Each
-- classifier element table entry also specifies the subsequent
-- downstream Differentiated Services Functional Data Path Element when
-- the classification pattern is satisfied. Each entry in the
-- classifier element table describes one branch of the fan-out
-- characteristic of a classifier indicated in the Informal
-- Differentiated Services Model section 4.1. A classifier is composed
-- of one or more classifier elements.
diffServClfrNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServClfrId, or a
zero to indicate that none exist."
::= { diffServClassifier 1 }
diffServClfrNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServClfrId, or a
zero to indicate that none exist."
::= { diffServClassifier 1 }
diffServClfrTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServClfrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table enumerates all the diffserv classifier functional data path elements of this device. The actual classification definitions are defined in diffServClfrElementTable entries belonging to each classifier.
diffServClfrTable DiffServClfrEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此表枚举此设备的所有diffserv分类器功能数据路径元素。实际分类定义在属于每个分类器的diffServClfrElementTable条目中定义。
An entry in this table, pointed to by a RowPointer specifying an instance of diffServClfrStatus, is frequently used as the name for a set of classifier elements, which all use the index diffServClfrId. Per the semantics of the classifier element table, these entries constitute one or more unordered sets of tests which may be simultaneously applied to a message to
此表中的一个条目由指定diffServClfrStatus实例的行指针指向，经常用作一组分类器元素的名称，这些元素都使用索引diffServClfrId。根据分类器元素表的语义，这些条目构成一个或多个无序的测试集，这些测试集可同时应用于发送到的消息
classify it.
把它分类。
The primary function of this table is to ensure that the value of
diffServClfrId is unique before attempting to use it in creating
a diffServClfrElementEntry. Therefore, the diffServClfrEntry must
be created on the same SET as the diffServClfrElementEntry, or
before the diffServClfrElementEntry is created."
::= { diffServClassifier 2 }
The primary function of this table is to ensure that the value of
diffServClfrId is unique before attempting to use it in creating
a diffServClfrElementEntry. Therefore, the diffServClfrEntry must
be created on the same SET as the diffServClfrElementEntry, or
before the diffServClfrElementEntry is created."
::= { diffServClassifier 2 }
diffServClfrEntry OBJECT-TYPE
SYNTAX DiffServClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the classifier table describes a single classifier.
All classifier elements belonging to the same classifier use the
classifier's diffServClfrId as part of their index."
INDEX { diffServClfrId }
::= { diffServClfrTable 1 }
diffServClfrEntry OBJECT-TYPE
SYNTAX DiffServClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the classifier table describes a single classifier.
All classifier elements belonging to the same classifier use the
classifier's diffServClfrId as part of their index."
INDEX { diffServClfrId }
::= { diffServClfrTable 1 }
DiffServClfrEntry ::= SEQUENCE {
diffServClfrId IndexInteger,
diffServClfrStorage StorageType,
diffServClfrStatus RowStatus
}
DiffServClfrEntry ::= SEQUENCE {
diffServClfrId IndexInteger,
diffServClfrStorage StorageType,
diffServClfrStatus RowStatus
}
diffServClfrId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the classifier entries. Managers
should obtain new values for row creation in this table by
reading diffServClfrNextFree."
::= { diffServClfrEntry 1 }
diffServClfrId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the classifier entries. Managers
should obtain new values for row creation in this table by
reading diffServClfrNextFree."
::= { diffServClfrEntry 1 }
diffServClfrStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServClfrEntry 2 }
diffServClfrStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServClfrEntry 2 }
diffServClfrStatus OBJECT-TYPE
diffServClfrStatus对象类型
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServClfrEntry 3 }
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServClfrEntry 3 }
--
-- Classifier Element Table
--
diffServClfrElementNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServClfrElementId,
or a zero to indicate that none exist."
::= { diffServClassifier 3 }
--
-- Classifier Element Table
--
diffServClfrElementNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServClfrElementId,
or a zero to indicate that none exist."
::= { diffServClassifier 3 }
diffServClfrElementTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServClfrElementEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The classifier element table enumerates the relationship between classification patterns and subsequent downstream Differentiated Services Functional Data Path elements. diffServClfrElementSpecific points to a filter that specifies the classification parameters. A classifier may use filter tables of different types together.
diffServClfrElementTable DiffServClfrElementEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“分类器元素表列举了分类模式与后续下游区分服务功能数据路径元素之间的关系。diffServClfrElementSpecific指向指定分类参数的筛选器。分类器可以同时使用不同类型的过滤器表。
One example of a filter table defined in this MIB is diffServMultiFieldClfrTable, for IP Multi-Field Classifiers (MFCs). Such an entry might identify anything from a single micro-flow (an identifiable sub-session packet stream directed from one sending transport to the receiving transport or transports), or aggregates of those such as the traffic from a host, traffic for an application, or traffic between two hosts using an application and a given DSCP. The standard Behavior Aggregate used in the Differentiated Services Architecture is encoded as a degenerate case of such an aggregate - the traffic using a particular DSCP value.
此MIB中定义的筛选器表的一个示例是diffServMultiFieldClfrTable，用于IP多字段分类器（MFC）。这样的条目可以识别来自单个微流（从一个发送传输定向到一个或多个接收传输的可识别子会话分组流）的任何内容，或者这些内容的集合，例如来自主机的流量、应用程序的流量，或者使用应用程序和给定DSCP的两个主机之间的流量。区分服务体系结构中使用的标准行为聚合被编码为此类聚合的退化情况—使用特定DSCP值的流量。
Filter tables for other filter types may be defined elsewhere."
其他过滤器类型的过滤器表可在别处定义。”
::= { diffServClassifier 4 }
::= { diffServClassifier 4 }
diffServClfrElementEntry OBJECT-TYPE
SYNTAX DiffServClfrElementEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the classifier element table describes a single
element of the classifier."
INDEX { diffServClfrId, diffServClfrElementId }
::= { diffServClfrElementTable 1 }
diffServClfrElementEntry OBJECT-TYPE
SYNTAX DiffServClfrElementEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the classifier element table describes a single
element of the classifier."
INDEX { diffServClfrId, diffServClfrElementId }
::= { diffServClfrElementTable 1 }
DiffServClfrElementEntry ::= SEQUENCE {
diffServClfrElementId IndexInteger,
diffServClfrElementPrecedence Unsigned32,
diffServClfrElementNext RowPointer,
diffServClfrElementSpecific RowPointer,
diffServClfrElementStorage StorageType,
diffServClfrElementStatus RowStatus
}
DiffServClfrElementEntry ::= SEQUENCE {
diffServClfrElementId IndexInteger,
diffServClfrElementPrecedence Unsigned32,
diffServClfrElementNext RowPointer,
diffServClfrElementSpecific RowPointer,
diffServClfrElementStorage StorageType,
diffServClfrElementStatus RowStatus
}
diffServClfrElementId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Classifier Element entries.
Managers obtain new values for row creation in this table by
reading diffServClfrElementNextFree."
::= { diffServClfrElementEntry 1 }
diffServClfrElementId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Classifier Element entries.
Managers obtain new values for row creation in this table by
reading diffServClfrElementNextFree."
::= { diffServClfrElementEntry 1 }
diffServClfrElementPrecedence OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-create STATUS current DESCRIPTION "The relative order in which classifier elements are applied: higher numbers represent classifier element with higher precedence. Classifier elements with the same order must be unambiguous i.e. they must define non-overlapping patterns, and are considered to be applied simultaneously to the traffic stream. Classifier elements with different order may overlap in their filters: the classifier element with the highest order that matches is taken.
DiffServClFrelementPreference对象类型语法Unsigned32（1..4294967295）MAX-ACCESS读取创建状态当前说明应用分类器元素的相对顺序：数字越大表示优先级越高的分类器元素。具有相同顺序的分类器元素必须是明确的，即它们必须定义非重叠模式，并被视为同时应用于交通流。不同顺序的分类器元素可能在其过滤器中重叠：采用匹配的最高顺序的分类器元素。
On a given interface, there must be a complete classifier in place at all times in the ingress direction. This means one or more filters must match any possible pattern. There is no such
在给定的接口上，必须在入口方向始终有一个完整的分类器。这意味着一个或多个过滤器必须匹配任何可能的模式。没有这种情况
requirement in the egress direction."
::= { diffServClfrElementEntry 2 }
requirement in the egress direction."
::= { diffServClfrElementEntry 2 }
diffServClfrElementNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This attribute provides one branch of the fan-out functionality of a classifier described in the Informal Differentiated Services Model section 4.1.
diffServClfrElementNext对象类型语法RowPointer MAX-ACCESS读取创建状态当前描述“此属性提供非正式区分服务模型第4.1节中描述的分类器扇出功能的一个分支。
This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry
这将选择下一个区分服务功能数据路径元素来处理此数据路径的流量。此行指针应指向以下之一的实例：diffServClfrEntry diffServMeterEntry diffServActionEntry DiffServAlgProperty diffServQEntry
A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path.
此属性中的值为zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。zeroDotZero是当前数据路径的最后一个功能数据路径元素的正常用法。
Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero."
将此设置为指向不存在的目标会导致值不一致错误。如果指向的行被删除或通过其他方式变为非活动行，则处理方式与此属性包含的值zeroDotZero相同。”
::= { diffServClfrElementEntry 3 }
::= { diffServClfrElementEntry 3 }
diffServClfrElementSpecific OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "A pointer to a valid entry in another table, filter table, that describes the applicable classification parameters, e.g. an entry in diffServMultiFieldClfrTable.
diffServClfrElementSpecific对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“指向另一个表（筛选器表）中有效项的指针，该表描述了适用的分类参数，例如diffServMultiFieldClfrTable中的项。
The value zeroDotZero is interpreted to match anything not matched by another classifier element - only one such entry may exist for each classifier.
值zeroDotZero被解释为匹配任何未被另一个分类器元素匹配的内容-每个分类器只能存在一个这样的条目。
Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or
将此设置为指向不存在的目标会导致值不一致错误。如果删除或删除了指向的行
becomes inactive by other means, the element is ignored."
::= { diffServClfrElementEntry 4 }
becomes inactive by other means, the element is ignored."
::= { diffServClfrElementEntry 4 }
diffServClfrElementStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServClfrElementEntry 5 }
diffServClfrElementStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServClfrElementEntry 5 }
diffServClfrElementStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServClfrElementEntry 6 }
diffServClfrElementStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServClfrElementEntry 6 }
--
-- IP Multi-field Classification Table
--
-- Classification based on six different fields in the IP header.
-- Functional Data Paths may share definitions by using the same entry.
--
--
-- IP Multi-field Classification Table
--
-- Classification based on six different fields in the IP header.
-- Functional Data Paths may share definitions by using the same entry.
--
diffServMultiFieldClfrNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
diffServMultiFieldClfrId, or a zero to indicate that none exist."
::= { diffServClassifier 5 }
diffServMultiFieldClfrNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
diffServMultiFieldClfrId, or a zero to indicate that none exist."
::= { diffServClassifier 5 }
diffServMultiFieldClfrTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServMultiFieldClfrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of IP Multi-field Classifier filter entries that a
diffServMultiFieldClfrTable对象类型DiffServMultiFieldClfrEntry的语法序列MAX-ACCESS不可访问状态当前描述“一个IP多字段分类器筛选项表
system may use to identify IP traffic."
::= { diffServClassifier 6 }
system may use to identify IP traffic."
::= { diffServClassifier 6 }
diffServMultiFieldClfrEntry OBJECT-TYPE
SYNTAX DiffServMultiFieldClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An IP Multi-field Classifier entry describes a single filter."
INDEX { diffServMultiFieldClfrId }
::= { diffServMultiFieldClfrTable 1 }
diffServMultiFieldClfrEntry OBJECT-TYPE
SYNTAX DiffServMultiFieldClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An IP Multi-field Classifier entry describes a single filter."
INDEX { diffServMultiFieldClfrId }
::= { diffServMultiFieldClfrTable 1 }
DiffServMultiFieldClfrEntry ::= SEQUENCE {
diffServMultiFieldClfrId IndexInteger,
diffServMultiFieldClfrAddrType InetAddressType,
diffServMultiFieldClfrDstAddr InetAddress,
diffServMultiFieldClfrDstPrefixLength InetAddressPrefixLength,
diffServMultiFieldClfrSrcAddr InetAddress,
diffServMultiFieldClfrSrcPrefixLength InetAddressPrefixLength,
diffServMultiFieldClfrDscp DscpOrAny,
diffServMultiFieldClfrFlowId Unsigned32,
diffServMultiFieldClfrProtocol Unsigned32,
diffServMultiFieldClfrDstL4PortMin InetPortNumber,
diffServMultiFieldClfrDstL4PortMax InetPortNumber,
diffServMultiFieldClfrSrcL4PortMin InetPortNumber,
diffServMultiFieldClfrSrcL4PortMax InetPortNumber,
diffServMultiFieldClfrStorage StorageType,
diffServMultiFieldClfrStatus RowStatus
}
DiffServMultiFieldClfrEntry ::= SEQUENCE {
diffServMultiFieldClfrId IndexInteger,
diffServMultiFieldClfrAddrType InetAddressType,
diffServMultiFieldClfrDstAddr InetAddress,
diffServMultiFieldClfrDstPrefixLength InetAddressPrefixLength,
diffServMultiFieldClfrSrcAddr InetAddress,
diffServMultiFieldClfrSrcPrefixLength InetAddressPrefixLength,
diffServMultiFieldClfrDscp DscpOrAny,
diffServMultiFieldClfrFlowId Unsigned32,
diffServMultiFieldClfrProtocol Unsigned32,
diffServMultiFieldClfrDstL4PortMin InetPortNumber,
diffServMultiFieldClfrDstL4PortMax InetPortNumber,
diffServMultiFieldClfrSrcL4PortMin InetPortNumber,
diffServMultiFieldClfrSrcL4PortMax InetPortNumber,
diffServMultiFieldClfrStorage StorageType,
diffServMultiFieldClfrStatus RowStatus
}
diffServMultiFieldClfrId OBJECT-TYPE SYNTAX IndexInteger MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index that enumerates the MultiField Classifier filter entries. Managers obtain new values for row creation in this table by reading diffServMultiFieldClfrNextFree."
diffServMultiFieldClfrId对象类型语法IndexIntegrater MAX-ACCESS不可访问状态当前描述“枚举多字段分类器筛选项的索引。管理器通过读取diffServMultiFieldClfrNextFree获取此表中创建行的新值。”
::= { diffServMultiFieldClfrEntry 1 }
::= { diffServMultiFieldClfrEntry 1 }
diffServMultiFieldClfrAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of IP address used by this classifier entry. While other types of addresses are defined in the InetAddressType
diffServMultiFieldClfrAddrType对象类型语法InetAddressType MAX-ACCESS读取创建状态当前描述“此分类器条目使用的IP地址类型。而其他类型的地址在InetAddressType中定义
textual convention, and DNS names, a classifier can only look at
packets on the wire. Therefore, this object is limited to IPv4
and IPv6 addresses."
::= { diffServMultiFieldClfrEntry 2 }
textual convention, and DNS names, a classifier can only look at
packets on the wire. Therefore, this object is limited to IPv4
and IPv6 addresses."
::= { diffServMultiFieldClfrEntry 2 }
diffServMultiFieldClfrDstAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the packet's destination IP
address. This may not be a DNS name, but may be an IPv4 or IPv6
prefix. diffServMultiFieldClfrDstPrefixLength indicates the
number of bits that are relevant."
::= { diffServMultiFieldClfrEntry 3 }
diffServMultiFieldClfrDstAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the packet's destination IP
address. This may not be a DNS name, but may be an IPv4 or IPv6
prefix. diffServMultiFieldClfrDstPrefixLength indicates the
number of bits that are relevant."
::= { diffServMultiFieldClfrEntry 3 }
diffServMultiFieldClfrDstPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
UNITS "bits"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of the CIDR Prefix carried in
diffServMultiFieldClfrDstAddr. In IPv4 addresses, a length of 0
indicates a match of any address; a length of 32 indicates a
match of a single host address, and a length between 0 and 32
indicates the use of a CIDR Prefix. IPv6 is similar, except that
prefix lengths range from 0..128."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 4 }
diffServMultiFieldClfrDstPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
UNITS "bits"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of the CIDR Prefix carried in
diffServMultiFieldClfrDstAddr. In IPv4 addresses, a length of 0
indicates a match of any address; a length of 32 indicates a
match of a single host address, and a length between 0 and 32
indicates the use of a CIDR Prefix. IPv6 is similar, except that
prefix lengths range from 0..128."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 4 }
diffServMultiFieldClfrSrcAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the packet's source IP address.
This may not be a DNS name, but may be an IPv4 or IPv6 prefix.
diffServMultiFieldClfrSrcPrefixLength indicates the number of
bits that are relevant."
::= { diffServMultiFieldClfrEntry 5 }
diffServMultiFieldClfrSrcAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the packet's source IP address.
This may not be a DNS name, but may be an IPv4 or IPv6 prefix.
diffServMultiFieldClfrSrcPrefixLength indicates the number of
bits that are relevant."
::= { diffServMultiFieldClfrEntry 5 }
diffServMultiFieldClfrSrcPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength UNITS "bits" MAX-ACCESS read-create STATUS current DESCRIPTION
DiffServMultiFieldCfRSRCPrefixleLength对象类型语法InetAddressPrefixleLength单位“位”MAX-ACCESS读取创建状态当前描述
"The length of the CIDR Prefix carried in
diffServMultiFieldClfrSrcAddr. In IPv4 addresses, a length of 0
indicates a match of any address; a length of 32 indicates a
match of a single host address, and a length between 0 and 32
indicates the use of a CIDR Prefix. IPv6 is similar, except that
prefix lengths range from 0..128."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 6 }
"The length of the CIDR Prefix carried in
diffServMultiFieldClfrSrcAddr. In IPv4 addresses, a length of 0
indicates a match of any address; a length of 32 indicates a
match of a single host address, and a length between 0 and 32
indicates the use of a CIDR Prefix. IPv6 is similar, except that
prefix lengths range from 0..128."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 6 }
diffServMultiFieldClfrDscp OBJECT-TYPE
SYNTAX DscpOrAny
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value that the DSCP in the packet must have to match this
entry. A value of -1 indicates that a specific DSCP value has not
been defined and thus all DSCP values are considered a match."
DEFVAL { -1 }
::= { diffServMultiFieldClfrEntry 7 }
diffServMultiFieldClfrDscp OBJECT-TYPE
SYNTAX DscpOrAny
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value that the DSCP in the packet must have to match this
entry. A value of -1 indicates that a specific DSCP value has not
been defined and thus all DSCP values are considered a match."
DEFVAL { -1 }
::= { diffServMultiFieldClfrEntry 7 }
diffServMultiFieldClfrFlowId OBJECT-TYPE
SYNTAX Unsigned32 (0..1048575)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The flow identifier in an IPv6 header."
::= { diffServMultiFieldClfrEntry 8 }
diffServMultiFieldClfrFlowId OBJECT-TYPE
SYNTAX Unsigned32 (0..1048575)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The flow identifier in an IPv6 header."
::= { diffServMultiFieldClfrEntry 8 }
diffServMultiFieldClfrProtocol OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP protocol to match against the IPv4 protocol number or the
IPv6 Next- Header number in the packet. A value of 255 means
match all. Note the protocol number of 255 is reserved by IANA,
and Next-Header number of 0 is used in IPv6."
DEFVAL { 255 }
::= { diffServMultiFieldClfrEntry 9 }
diffServMultiFieldClfrProtocol OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP protocol to match against the IPv4 protocol number or the
IPv6 Next- Header number in the packet. A value of 255 means
match all. Note the protocol number of 255 is reserved by IANA,
and Next-Header number of 0 is used in IPv6."
DEFVAL { 255 }
::= { diffServMultiFieldClfrEntry 9 }
diffServMultiFieldClfrDstL4PortMin OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum value that the layer-4 destination port number in the packet must have in order to match this classifier entry." DEFVAL { 0 }
diffServMultiFieldClfrDstL4PortMin对象类型语法InetPortNumber MAX-ACCESS读取创建状态当前描述“数据包中的第4层目标端口号必须具有的最小值才能匹配此分类器条目。”定义值{0}
::= { diffServMultiFieldClfrEntry 10 }
::= { diffServMultiFieldClfrEntry 10 }
diffServMultiFieldClfrDstL4PortMax OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 destination port number in
the packet must have in order to match this classifier entry.
This value must be equal to or greater than the value specified
for this entry in diffServMultiFieldClfrDstL4PortMin."
DEFVAL { 65535 }
::= { diffServMultiFieldClfrEntry 11 }
diffServMultiFieldClfrDstL4PortMax OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 destination port number in
the packet must have in order to match this classifier entry.
This value must be equal to or greater than the value specified
for this entry in diffServMultiFieldClfrDstL4PortMin."
DEFVAL { 65535 }
::= { diffServMultiFieldClfrEntry 11 }
diffServMultiFieldClfrSrcL4PortMin OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The minimum value that the layer-4 source port number in the
packet must have in order to match this classifier entry."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 12 }
diffServMultiFieldClfrSrcL4PortMin OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The minimum value that the layer-4 source port number in the
packet must have in order to match this classifier entry."
DEFVAL { 0 }
::= { diffServMultiFieldClfrEntry 12 }
diffServMultiFieldClfrSrcL4PortMax OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 source port number in the
packet must have in order to match this classifier entry. This
value must be equal to or greater than the value specified for
this entry in diffServMultiFieldClfrSrcL4PortMin."
DEFVAL { 65535 }
::= { diffServMultiFieldClfrEntry 13 }
diffServMultiFieldClfrSrcL4PortMax OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 source port number in the
packet must have in order to match this classifier entry. This
value must be equal to or greater than the value specified for
this entry in diffServMultiFieldClfrSrcL4PortMin."
DEFVAL { 65535 }
::= { diffServMultiFieldClfrEntry 13 }
diffServMultiFieldClfrStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMultiFieldClfrEntry 14 }
diffServMultiFieldClfrStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMultiFieldClfrEntry 14 }
diffServMultiFieldClfrStatus OBJECT-TYPE
DiffServMultiFieldCfRStatus对象类型
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMultiFieldClfrEntry 15 }
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMultiFieldClfrEntry 15 }
-- -- Meters --
----米--
diffServMeter OBJECT IDENTIFIER ::= { diffServMIBObjects 3 }
diffServMeter OBJECT IDENTIFIER ::= { diffServMIBObjects 3 }
--
-- This MIB supports a variety of Meters. It includes a specific
-- definition for Token Bucket Meter, which are but one type of
-- specification. Other metering parameter sets can be defined in other
-- MIBs.
--
-- This MIB supports a variety of Meters. It includes a specific
-- definition for Token Bucket Meter, which are but one type of
-- specification. Other metering parameter sets can be defined in other
-- MIBs.
-- Multiple meter elements may be logically cascaded using their
-- diffServMeterSucceedNext and diffServMeterFailNext pointers if
-- required. One example of this might be for an AF PHB implementation
-- that uses multiple level conformance meters.
-- Multiple meter elements may be logically cascaded using their
-- diffServMeterSucceedNext and diffServMeterFailNext pointers if
-- required. One example of this might be for an AF PHB implementation
-- that uses multiple level conformance meters.
-- Cascading of individual meter elements in the MIB is intended to be
-- functionally equivalent to multiple level conformance determination
-- of a packet. The sequential nature of the representation is merely
-- a notational convenience for this MIB.
-- Cascading of individual meter elements in the MIB is intended to be
-- functionally equivalent to multiple level conformance determination
-- of a packet. The sequential nature of the representation is merely
-- a notational convenience for this MIB.
-- srTCM meters (RFC 2697) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Information Rate and Committed Burst Size
-- token-bucket. The second set specifies the Excess Burst Size
-- token-bucket.
-- srTCM meters (RFC 2697) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Information Rate and Committed Burst Size
-- token-bucket. The second set specifies the Excess Burst Size
-- token-bucket.
-- trTCM meters (RFC 2698) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Information Rate and Committed Burst Size
-- token-bucket. The second set specifies the Peak Information Rate
-- and Peak Burst Size token-bucket.
-- trTCM meters (RFC 2698) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Information Rate and Committed Burst Size
-- token-bucket. The second set specifies the Peak Information Rate
-- and Peak Burst Size token-bucket.
-- tswTCM meters (RFC 2859) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Target Rate token-bucket. The second set specifies
-- tswTCM meters (RFC 2859) can be specified using two sets of
-- diffServMeterEntry and diffServTBParamEntry. The first set specifies
-- the Committed Target Rate token-bucket. The second set specifies
-- the Peak Target Rate token-bucket. diffServTBParamInterval in each
-- token bucket reflects the Average Interval.
--
-- the Peak Target Rate token-bucket. diffServTBParamInterval in each
-- token bucket reflects the Average Interval.
--
diffServMeterNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServMeterId, or a
zero to indicate that none exist."
::= { diffServMeter 1 }
diffServMeterNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServMeterId, or a
zero to indicate that none exist."
::= { diffServMeter 1 }
diffServMeterTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServMeterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table enumerates specific meters that a system may use to police a stream of traffic. The traffic stream to be metered is determined by the Differentiated Services Functional Data Path Element(s) upstream of the meter i.e. by the object(s) that point to each entry in this table. This may include all traffic on an interface.
diffServMeterTable DiffServMeterEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此表列举了系统可用于监控流量流的特定仪表。要计量的流量流由区分服务功能数据路径元素确定仪表上游，即指向本表中每个条目的对象。这可能包括接口上的所有流量。
Specific meter details are to be found in table entry referenced
by diffServMeterSpecific."
::= { diffServMeter 2 }
Specific meter details are to be found in table entry referenced
by diffServMeterSpecific."
::= { diffServMeter 2 }
diffServMeterEntry OBJECT-TYPE
SYNTAX DiffServMeterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the meter table describes a single conformance level
of a meter."
INDEX { diffServMeterId }
::= { diffServMeterTable 1 }
diffServMeterEntry OBJECT-TYPE
SYNTAX DiffServMeterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the meter table describes a single conformance level
of a meter."
INDEX { diffServMeterId }
::= { diffServMeterTable 1 }
DiffServMeterEntry ::= SEQUENCE {
diffServMeterId IndexInteger,
diffServMeterSucceedNext RowPointer,
diffServMeterFailNext RowPointer,
diffServMeterSpecific RowPointer,
diffServMeterStorage StorageType,
diffServMeterStatus RowStatus
}
DiffServMeterEntry ::= SEQUENCE {
diffServMeterId IndexInteger,
diffServMeterSucceedNext RowPointer,
diffServMeterFailNext RowPointer,
diffServMeterSpecific RowPointer,
diffServMeterStorage StorageType,
diffServMeterStatus RowStatus
}
diffServMeterId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Meter entries. Managers obtain new
values for row creation in this table by reading
diffServMeterNextFree."
::= { diffServMeterEntry 1 }
diffServMeterId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Meter entries. Managers obtain new
values for row creation in this table by reading
diffServMeterNextFree."
::= { diffServMeterEntry 1 }
diffServMeterSucceedNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If the traffic does conform, this selects the next Differentiated Services Functional Data Path element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry
diffServMeterSucceedNext对象类型语法行指针最大访问读取创建状态当前描述“如果流量符合要求，则选择下一个区分服务功能数据路径元素来处理此数据路径的流量。此行指针应指向以下之一的实例：diffServClfrEntry diffServMeterEntry diffServActionEntry DiffServAlgProperty diffServQEntry
A value of zeroDotZero in this attribute indicates that no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path.
此属性中的值zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。zeroDotZero是当前数据路径的最后一个功能数据路径元素的正常用法。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServMeterEntry 2 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServMeterEntry 2 }
diffServMeterFailNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If the traffic does not conform, this selects the next Differentiated Services Functional Data Path element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry
diffServMeterFailNext对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“如果流量不一致，这将选择下一个区分服务功能数据路径元素来处理此数据路径的流量。此RowPointer应指向以下之一的实例：diffServClfrEntry diffServMeterEntry
diffServActionEntry diffServAlgDropEntry diffServQEntry
DiffServeActionEntry DiffServalgProperty diffServQEntry
A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path.
此属性中的值为zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。zeroDotZero是当前数据路径的最后一个功能数据路径元素的正常用法。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServMeterEntry 3 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServMeterEntry 3 }
diffServMeterSpecific OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This indicates the behavior of the meter by pointing to an entry containing detailed parameters. Note that entries in that specific table must be managed explicitly.
diffServMeterSpecific对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“这通过指向包含详细参数的条目来指示仪表的行为。请注意，必须显式管理该特定表中的条目。
For example, diffServMeterSpecific may point to an entry in diffServTBParamTable, which contains an instance of a single set of Token Bucket parameters.
例如，diffServMeterSpecific可以指向diffServTBParamTable中的一个条目，该条目包含一组令牌桶参数的实例。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the meter always succeeds."
::= { diffServMeterEntry 4 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the meter always succeeds."
::= { diffServMeterEntry 4 }
diffServMeterStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMeterEntry 5 }
diffServMeterStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMeterEntry 5 }
diffServMeterStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create
diffServMeterStatus对象类型语法RowStatus MAX-ACCESS read create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMeterEntry 6 }
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMeterEntry 6 }
-- -- Token Bucket Parameter Table --
----令牌桶参数表--
diffServTBParam OBJECT IDENTIFIER ::= { diffServMIBObjects 4 }
diffServTBParam OBJECT IDENTIFIER ::= { diffServMIBObjects 4 }
-- Each entry in the Token Bucket Parameter Table parameterize a single
-- token bucket. Multiple token buckets can be used together to
-- parameterize multiple levels of conformance.
-- Each entry in the Token Bucket Parameter Table parameterize a single
-- token bucket. Multiple token buckets can be used together to
-- parameterize multiple levels of conformance.
-- Note that an entry in the Token Bucket Parameter Table can be shared
-- by multiple diffServMeterTable entries.
--
-- Note that an entry in the Token Bucket Parameter Table can be shared
-- by multiple diffServMeterTable entries.
--
diffServTBParamNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServTBParamId, or a
zero to indicate that none exist."
::= { diffServTBParam 1 }
diffServTBParamNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServTBParamId, or a
zero to indicate that none exist."
::= { diffServTBParam 1 }
diffServTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServTBParamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table enumerates a single set of token bucket meter
parameters that a system may use to police a stream of traffic.
Such meters are modeled here as having a single rate and a single
burst size. Multiple entries are used when multiple rates/burst
sizes are needed."
::= { diffServTBParam 2 }
diffServTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServTBParamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table enumerates a single set of token bucket meter
parameters that a system may use to police a stream of traffic.
Such meters are modeled here as having a single rate and a single
burst size. Multiple entries are used when multiple rates/burst
sizes are needed."
::= { diffServTBParam 2 }
diffServTBParamEntry OBJECT-TYPE SYNTAX DiffServTBParamEntry MAX-ACCESS not-accessible STATUS current
diffServTBParamEntry对象类型语法diffServTBParamEntry MAX-ACCESS不可访问状态当前
DESCRIPTION
"An entry that describes a single set of token bucket
parameters."
INDEX { diffServTBParamId }
::= { diffServTBParamTable 1 }
DESCRIPTION
"An entry that describes a single set of token bucket
parameters."
INDEX { diffServTBParamId }
::= { diffServTBParamTable 1 }
DiffServTBParamEntry ::= SEQUENCE {
diffServTBParamId IndexInteger,
diffServTBParamType AutonomousType,
diffServTBParamRate Unsigned32,
diffServTBParamBurstSize BurstSize,
diffServTBParamInterval Unsigned32,
diffServTBParamStorage StorageType,
diffServTBParamStatus RowStatus
}
DiffServTBParamEntry ::= SEQUENCE {
diffServTBParamId IndexInteger,
diffServTBParamType AutonomousType,
diffServTBParamRate Unsigned32,
diffServTBParamBurstSize BurstSize,
diffServTBParamInterval Unsigned32,
diffServTBParamStorage StorageType,
diffServTBParamStatus RowStatus
}
diffServTBParamId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Token Bucket Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServTBParamNextFree."
::= { diffServTBParamEntry 1 }
diffServTBParamId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Token Bucket Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServTBParamNextFree."
::= { diffServTBParamEntry 1 }
diffServTBParamType OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-create STATUS current DESCRIPTION "The Metering algorithm associated with the Token Bucket parameters. zeroDotZero indicates this is unknown.
diffServTBParamType对象类型语法AutonomousType MAX-ACCESS读取创建状态当前描述“与令牌桶参数关联的计数算法。zeroDotZero表示这是未知的。
Standard values for generic algorithms:
diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate,
diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware,
diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, and
diffServTBParamTswTCM are specified in this MIB as OBJECT-
IDENTITYs; additional values may be further specified in other
MIBs."
::= { diffServTBParamEntry 2 }
Standard values for generic algorithms:
diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate,
diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware,
diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, and
diffServTBParamTswTCM are specified in this MIB as OBJECT-
IDENTITYs; additional values may be further specified in other
MIBs."
::= { diffServTBParamEntry 2 }
diffServTBParamRate OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "kilobits per second" MAX-ACCESS read-create STATUS current
diffServTBParamRate对象类型语法无符号32（1..4294967295）单位“千比特每秒”最大访问读取创建状态当前
DESCRIPTION
"The token-bucket rate, in kilobits per second (kbps). This
attribute is used for:
1. CIR in RFC 2697 for srTCM
2. CIR and PIR in RFC 2698 for trTCM
3. CTR and PTR in RFC 2859 for TSWTCM
4. AverageRate in RFC 3290."
::= { diffServTBParamEntry 3 }
DESCRIPTION
"The token-bucket rate, in kilobits per second (kbps). This
attribute is used for:
1. CIR in RFC 2697 for srTCM
2. CIR and PIR in RFC 2698 for trTCM
3. CTR and PTR in RFC 2859 for TSWTCM
4. AverageRate in RFC 3290."
::= { diffServTBParamEntry 3 }
diffServTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum number of bytes in a single transmission burst. This
attribute is used for:
1. CBS and EBS in RFC 2697 for srTCM
2. CBS and PBS in RFC 2698 for trTCM
3. Burst Size in RFC 3290."
::= { diffServTBParamEntry 4 }
diffServTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum number of bytes in a single transmission burst. This
attribute is used for:
1. CBS and EBS in RFC 2697 for srTCM
2. CBS and PBS in RFC 2698 for trTCM
3. Burst Size in RFC 3290."
::= { diffServTBParamEntry 4 }
diffServTBParamInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "microseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The time interval used with the token bucket. For:
1. Average Rate Meter, the Informal Differentiated Services Model
section 5.2.1, - Delta.
2. Simple Token Bucket Meter, the Informal Differentiated
Services Model section 5.1, - time interval t.
3. RFC 2859 TSWTCM, - AVG_INTERVAL.
4. RFC 2697 srTCM, RFC 2698 trTCM, - token bucket update time
interval."
::= { diffServTBParamEntry 5 }
diffServTBParamInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "microseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The time interval used with the token bucket. For:
1. Average Rate Meter, the Informal Differentiated Services Model
section 5.2.1, - Delta.
2. Simple Token Bucket Meter, the Informal Differentiated
Services Model section 5.1, - time interval t.
3. RFC 2859 TSWTCM, - AVG_INTERVAL.
4. RFC 2697 srTCM, RFC 2698 trTCM, - token bucket update time
interval."
::= { diffServTBParamEntry 5 }
diffServTBParamStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServTBParamEntry 6 }
diffServTBParamStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServTBParamEntry 6 }
diffServTBParamStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServTBParamEntry 7 }
diffServTBParamStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServTBParamEntry 7 }
-- -- OIDs for diffServTBParamType definitions. --
----diffServTBParamType定义的OID--
diffServTBMeters OBJECT IDENTIFIER ::= { diffServMIBAdmin 1 }
diffServTBMeters OBJECT IDENTIFIER ::= { diffServMIBAdmin 1 }
diffServTBParamSimpleTokenBucket OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Parameter Token Bucket Meter as described in the Informal
Differentiated Services Model section 5.2.3."
::= { diffServTBMeters 1 }
diffServTBParamSimpleTokenBucket OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Parameter Token Bucket Meter as described in the Informal
Differentiated Services Model section 5.2.3."
::= { diffServTBMeters 1 }
diffServTBParamAvgRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Average Rate Meter as described in the Informal Differentiated
Services Model section 5.2.1."
::= { diffServTBMeters 2 }
diffServTBParamAvgRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Average Rate Meter as described in the Informal Differentiated
Services Model section 5.2.1."
::= { diffServTBMeters 2 }
diffServTBParamSrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Single Rate Three Color Marker Metering as defined by RFC 2697,
in the `Color Blind' mode as described by the RFC."
REFERENCE
"RFC 2697"
::= { diffServTBMeters 3 }
diffServTBParamSrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Single Rate Three Color Marker Metering as defined by RFC 2697,
in the `Color Blind' mode as described by the RFC."
REFERENCE
"RFC 2697"
::= { diffServTBMeters 3 }
diffServTBParamSrTCMAware OBJECT-IDENTITY STATUS current DESCRIPTION "Single Rate Three Color Marker Metering as defined by RFC 2697, in the `Color Aware' mode as described by the RFC." REFERENCE "RFC 2697"
diffServTBParamSrTCMAware对象标识状态当前描述“RFC 2697定义的单速率三色标记测光，采用RFC描述的“颜色感知”模式。”参考“RFC 2697”
::= { diffServTBMeters 4 }
::= { diffServTBMeters 4 }
diffServTBParamTrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Rate Three Color Marker Metering as defined by RFC 2698, in
the `Color Blind' mode as described by the RFC."
REFERENCE
"RFC 2698"
::= { diffServTBMeters 5 }
diffServTBParamTrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Rate Three Color Marker Metering as defined by RFC 2698, in
the `Color Blind' mode as described by the RFC."
REFERENCE
"RFC 2698"
::= { diffServTBMeters 5 }
diffServTBParamTrTCMAware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Rate Three Color Marker Metering as defined by RFC 2698, in
the `Color Aware' mode as described by the RFC."
REFERENCE
"RFC 2698"
::= { diffServTBMeters 6 }
diffServTBParamTrTCMAware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Two Rate Three Color Marker Metering as defined by RFC 2698, in
the `Color Aware' mode as described by the RFC."
REFERENCE
"RFC 2698"
::= { diffServTBMeters 6 }
diffServTBParamTswTCM OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Time Sliding Window Three Color Marker Metering as defined by
RFC 2859."
REFERENCE
"RFC 2859"
::= { diffServTBMeters 7 }
diffServTBParamTswTCM OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Time Sliding Window Three Color Marker Metering as defined by
RFC 2859."
REFERENCE
"RFC 2859"
::= { diffServTBMeters 7 }
-- -- Actions --
----行动--
diffServAction OBJECT IDENTIFIER ::= { diffServMIBObjects 5 }
diffServAction OBJECT IDENTIFIER ::= { diffServMIBObjects 5 }
--
-- The Action Table allows enumeration of the different types of
-- actions to be applied to a traffic flow.
--
--
-- The Action Table allows enumeration of the different types of
-- actions to be applied to a traffic flow.
--
diffServActionNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServActionId, or a
zero to indicate that none exist."
::= { diffServAction 1 }
diffServActionNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServActionId, or a
zero to indicate that none exist."
::= { diffServAction 1 }
diffServActionTable OBJECT-TYPE SYNTAX SEQUENCE OF DiffServActionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Action Table enumerates actions that can be performed to a stream of traffic. Multiple actions can be concatenated. For example, traffic exiting from a meter may be counted, marked, and potentially dropped before entering a queue.
DiffServeActionEntry MAX-ACCESS的DiffServeActionTable对象类型语法序列不可访问状态当前描述“操作表列举了可以对流量流执行的操作。可以连接多个操作。例如，在进入队列之前，可能会对从计费器退出的流量进行计数、标记和潜在丢弃。
Specific actions are indicated by diffServActionSpecific which
points to an entry of a specific action type parameterizing the
action in detail."
::= { diffServAction 2 }
Specific actions are indicated by diffServActionSpecific which
points to an entry of a specific action type parameterizing the
action in detail."
::= { diffServAction 2 }
diffServActionEntry OBJECT-TYPE
SYNTAX DiffServActionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in the action table allows description of one
specific action to be applied to traffic."
INDEX { diffServActionId }
::= { diffServActionTable 1 }
diffServActionEntry OBJECT-TYPE
SYNTAX DiffServActionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in the action table allows description of one
specific action to be applied to traffic."
INDEX { diffServActionId }
::= { diffServActionTable 1 }
DiffServActionEntry ::= SEQUENCE {
diffServActionId IndexInteger,
diffServActionInterface InterfaceIndexOrZero,
diffServActionNext RowPointer,
diffServActionSpecific RowPointer,
diffServActionStorage StorageType,
diffServActionStatus RowStatus
}
DiffServActionEntry ::= SEQUENCE {
diffServActionId IndexInteger,
diffServActionInterface InterfaceIndexOrZero,
diffServActionNext RowPointer,
diffServActionSpecific RowPointer,
diffServActionStorage StorageType,
diffServActionStatus RowStatus
}
diffServActionId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Action entries. Managers obtain
new values for row creation in this table by reading
diffServActionNextFree."
::= { diffServActionEntry 1 }
diffServActionId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Action entries. Managers obtain
new values for row creation in this table by reading
diffServActionNextFree."
::= { diffServActionEntry 1 }
diffServActionInterface OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current
diffServActionInterface对象类型语法InterfaceIndexOrZero最大访问读取创建状态当前
DESCRIPTION "The interface index (value of ifIndex) that this action occurs on. This may be derived from the diffServDataPathStartEntry's index by extension through the various RowPointers. However, as this may be difficult for a network management station, it is placed here as well. If this is indeterminate, the value is zero.
DESCRIPTION“执行此操作的接口索引（ifIndex的值）。此索引可以通过各种行指针扩展从diffServDataPathStartEntry的索引派生。但是，由于这对于网络管理站来说可能很困难，因此也将其放在此处。如果此索引不确定，则该值为零。
This is of especial relevance when reporting the counters which may apply to traffic crossing an interface: diffServCountActOctets, diffServCountActPkts, diffServAlgDropOctets, diffServAlgDropPkts, diffServAlgRandomDropOctets, and diffServAlgRandomDropPkts.
当报告可能应用于通过接口的流量的计数器时，这一点特别重要：DiffServCountActeTs、diffServCountActPkts、diffServAlgDropOctets、diffServAlgDropPkts、DiffServGrandomDropOctets和DiffServGrandomDropPKts。
It is also especially relevant to the queue and scheduler which
may be subsequently applied."
::= { diffServActionEntry 2 }
It is also especially relevant to the queue and scheduler which
may be subsequently applied."
::= { diffServActionEntry 2 }
diffServActionNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry
DiffServeActionNext对象类型语法行指针最大访问读取创建状态当前描述“这将选择下一个区分服务功能数据路径元素来处理此数据路径的流量。此行指针应指向以下之一的实例：diffServClfrEntry diffServMeterEntry diffServActionEntry DiffServAlgProperty diffServQEntry
A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path.
此属性中的值为zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。zeroDotZero是当前数据路径的最后一个功能数据路径元素的正常用法。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServActionEntry 3 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServActionEntry 3 }
diffServActionSpecific OBJECT-TYPE
区分服务特定对象类型
SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "A pointer to an object instance providing additional information for the type of action indicated by this action table entry.
语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“指向对象实例的指针，该对象实例提供此操作表项指示的操作类型的附加信息。
For the standard actions defined by this MIB module, this should point to either a diffServDscpMarkActEntry or a diffServCountActEntry. For other actions, it may point to an object instance defined in some other MIB.
对于此MIB模块定义的标准操作，这应该指向DiffServDSCmparkActEntry或diffServCountActEntry。对于其他操作，它可能指向在其他MIB中定义的对象实例。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the Meter should be treated as
if it were not present. This may lead to incorrect policy
behavior."
::= { diffServActionEntry 4 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the Meter should be treated as
if it were not present. This may lead to incorrect policy
behavior."
::= { diffServActionEntry 4 }
diffServActionStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServActionEntry 5 }
diffServActionStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServActionEntry 5 }
diffServActionStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServActionEntry 6 }
diffServActionStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServActionEntry 6 }
-- DSCP Mark Action Table
--
-- Rows of this table are pointed to by diffServActionSpecific to
-- provide detailed parameters specific to the DSCP Mark action.
--
-- A single entry in this table can be shared by multiple
-- DSCP Mark Action Table
--
-- Rows of this table are pointed to by diffServActionSpecific to
-- provide detailed parameters specific to the DSCP Mark action.
--
-- A single entry in this table can be shared by multiple
-- diffServActionTable entries. --
--diffServActionTable条目--
diffServDscpMarkActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServDscpMarkActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table enumerates specific DSCPs used for marking or
remarking the DSCP field of IP packets. The entries of this table
may be referenced by a diffServActionSpecific attribute."
::= { diffServAction 3 }
diffServDscpMarkActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServDscpMarkActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table enumerates specific DSCPs used for marking or
remarking the DSCP field of IP packets. The entries of this table
may be referenced by a diffServActionSpecific attribute."
::= { diffServAction 3 }
diffServDscpMarkActEntry OBJECT-TYPE
SYNTAX DiffServDscpMarkActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DSCP mark action table that describes a single
DSCP used for marking."
INDEX { diffServDscpMarkActDscp }
::= { diffServDscpMarkActTable 1 }
diffServDscpMarkActEntry OBJECT-TYPE
SYNTAX DiffServDscpMarkActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DSCP mark action table that describes a single
DSCP used for marking."
INDEX { diffServDscpMarkActDscp }
::= { diffServDscpMarkActTable 1 }
DiffServDscpMarkActEntry ::= SEQUENCE {
diffServDscpMarkActDscp Dscp
}
DiffServDscpMarkActEntry ::= SEQUENCE {
diffServDscpMarkActDscp Dscp
}
diffServDscpMarkActDscp OBJECT-TYPE
SYNTAX Dscp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The DSCP that this Action will store into the DSCP field of the
subject. It is quite possible that the only packets subject to
this Action are already marked with this DSCP. Note also that
Differentiated Services processing may result in packet being
marked on both ingress to a network and on egress from it, and
that ingress and egress can occur in the same router."
::= { diffServDscpMarkActEntry 1 }
diffServDscpMarkActDscp OBJECT-TYPE
SYNTAX Dscp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The DSCP that this Action will store into the DSCP field of the
subject. It is quite possible that the only packets subject to
this Action are already marked with this DSCP. Note also that
Differentiated Services processing may result in packet being
marked on both ingress to a network and on egress from it, and
that ingress and egress can occur in the same router."
::= { diffServDscpMarkActEntry 1 }
--
-- Count Action Table
--
-- Because the MIB structure allows multiple cascading
-- diffServActionEntry be used to describe multiple actions for a data
-- path, the counter became an optional action type. In normal
-- implementation, either a data path has counters or it does not, as
-- opposed to being configurable. The management entity may choose to
--
-- Count Action Table
--
-- Because the MIB structure allows multiple cascading
-- diffServActionEntry be used to describe multiple actions for a data
-- path, the counter became an optional action type. In normal
-- implementation, either a data path has counters or it does not, as
-- opposed to being configurable. The management entity may choose to
-- read the counter or not. Hence it is recommended for implementation
-- that have counters to always configure the count action as the first
-- of multiple actions.
--
-- read the counter or not. Hence it is recommended for implementation
-- that have counters to always configure the count action as the first
-- of multiple actions.
--
diffServCountActNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
diffServCountActId, or a zero to indicate that none exist."
::= { diffServAction 4 }
diffServCountActNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
diffServCountActId, or a zero to indicate that none exist."
::= { diffServAction 4 }
diffServCountActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServCountActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains counters for all the traffic passing through
an action element."
::= { diffServAction 5 }
diffServCountActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServCountActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains counters for all the traffic passing through
an action element."
::= { diffServAction 5 }
diffServCountActEntry OBJECT-TYPE
SYNTAX DiffServCountActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the count action table describes a single set of
traffic counters."
INDEX { diffServCountActId }
::= { diffServCountActTable 1 }
diffServCountActEntry OBJECT-TYPE
SYNTAX DiffServCountActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the count action table describes a single set of
traffic counters."
INDEX { diffServCountActId }
::= { diffServCountActTable 1 }
DiffServCountActEntry ::= SEQUENCE {
diffServCountActId IndexInteger,
diffServCountActOctets Counter64,
diffServCountActPkts Counter64,
diffServCountActStorage StorageType,
diffServCountActStatus RowStatus
}
DiffServCountActEntry ::= SEQUENCE {
diffServCountActId IndexInteger,
diffServCountActOctets Counter64,
diffServCountActPkts Counter64,
diffServCountActStorage StorageType,
diffServCountActStatus RowStatus
}
diffServCountActId OBJECT-TYPE SYNTAX IndexInteger MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index that enumerates the Count Action entries. Managers obtain new values for row creation in this table by reading
diffServCountActId对象类型语法IndexIntegrater MAX-ACCESS不可访问状态当前描述”枚举计数操作项的索引。管理器通过读取获取此表中行创建的新值
diffServCountActNextFree."
::= { diffServCountActEntry 1 }
diffServCountActNextFree."
::= { diffServCountActEntry 1 }
diffServCountActOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets at the Action data path element.
DiffServCountActeTets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“操作数据路径元素处的八位字节数。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServCountActEntry 2 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServCountActEntry 2 }
diffServCountActPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets at the Action data path element.
diffServCountActPkts对象类型语法计数器64 MAX-ACCESS只读状态当前说明“操作数据路径元素处的数据包数。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServCountActEntry 3 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServCountActEntry 3 }
diffServCountActStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServCountActEntry 4 }
diffServCountActStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServCountActEntry 4 }
diffServCountActStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing
diffServCountActStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此概念行的状态。此行中的所有可写对象均可随时修改。当MIB包含一个或多个指向的行指针时，将此变量设置为“destroy”
to it results in destruction being delayed until the row is no
longer used."
::= { diffServCountActEntry 5 }
to it results in destruction being delayed until the row is no
longer used."
::= { diffServCountActEntry 5 }
-- -- Algorithmic Drop Table --
----算法删除表--
diffServAlgDrop OBJECT IDENTIFIER ::= { diffServMIBObjects 6 }
diffServAlgDrop OBJECT IDENTIFIER ::= { diffServMIBObjects 6 }
diffServAlgDropNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServAlgDropId, or a
zero to indicate that none exist."
::= { diffServAlgDrop 1 }
diffServAlgDropNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServAlgDropId, or a
zero to indicate that none exist."
::= { diffServAlgDrop 1 }
diffServAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServAlgDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The algorithmic drop table contains entries describing an
element that drops packets according to some algorithm."
::= { diffServAlgDrop 2 }
diffServAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServAlgDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The algorithmic drop table contains entries describing an
element that drops packets according to some algorithm."
::= { diffServAlgDrop 2 }
diffServAlgDropEntry OBJECT-TYPE
SYNTAX DiffServAlgDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a process that drops packets according to
some algorithm. Further details of the algorithm type are to be
found in diffServAlgDropType and with more detail parameter entry
pointed to by diffServAlgDropSpecific when necessary."
INDEX { diffServAlgDropId }
::= { diffServAlgDropTable 1 }
diffServAlgDropEntry OBJECT-TYPE
SYNTAX DiffServAlgDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a process that drops packets according to
some algorithm. Further details of the algorithm type are to be
found in diffServAlgDropType and with more detail parameter entry
pointed to by diffServAlgDropSpecific when necessary."
INDEX { diffServAlgDropId }
::= { diffServAlgDropTable 1 }
DiffServAlgDropEntry ::= SEQUENCE {
diffServAlgDropId IndexInteger,
diffServAlgDropType INTEGER,
diffServAlgDropNext RowPointer,
diffServAlgDropQMeasure RowPointer,
diffServAlgDropQThreshold Unsigned32,
diffServAlgDropSpecific RowPointer,
diffServAlgDropOctets Counter64,
DiffServAlgDropEntry ::= SEQUENCE {
diffServAlgDropId IndexInteger,
diffServAlgDropType INTEGER,
diffServAlgDropNext RowPointer,
diffServAlgDropQMeasure RowPointer,
diffServAlgDropQThreshold Unsigned32,
diffServAlgDropSpecific RowPointer,
diffServAlgDropOctets Counter64,
diffServAlgDropPkts Counter64, diffServAlgRandomDropOctets Counter64, diffServAlgRandomDropPkts Counter64, diffServAlgDropStorage StorageType, diffServAlgDropStatus RowStatus }
diffServAlgDropPkts计数器64，diffServAlgRandomDropOctets计数器64，diffServAlgRandomDropPkts计数器64，diffServAlgDropStorage存储类型，diffServAlgDropStatus行状态}
diffServAlgDropId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Algorithmic Dropper entries.
Managers obtain new values for row creation in this table by
reading diffServAlgDropNextFree."
::= { diffServAlgDropEntry 1 }
diffServAlgDropId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Algorithmic Dropper entries.
Managers obtain new values for row creation in this table by
reading diffServAlgDropNextFree."
::= { diffServAlgDropEntry 1 }
diffServAlgDropType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of algorithm used by this dropper. The value other(1)
requires further specification in some other MIB module.
diffServAlgDropType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of algorithm used by this dropper. The value other(1)
requires further specification in some other MIB module.
In the tailDrop(2) algorithm, diffServAlgDropQThreshold represents the maximum depth of the queue, pointed to by diffServAlgDropQMeasure, beyond which all newly arriving packets will be dropped.
在tailDrop（2）算法中，diffServAlgDropQThreshold表示队列的最大深度，由diffServAlgDropQMeasure指出，超过该深度，所有新到达的数据包都将被丢弃。
In the headDrop(3) algorithm, if a packet arrives when the current depth of the queue, pointed to by diffServAlgDropQMeasure, is at diffServAlgDropQThreshold, packets currently at the head of the queue are dropped to make room for the new packet to be enqueued at the tail of the queue.
在headDrop（3）算法中，如果数据包在diffServAlgDropQMeasure所指的队列当前深度处于diffServAlgDropQThreshold时到达，则丢弃当前位于队列头部的数据包，以便为新数据包腾出空间，使其在队列尾部排队。
In the randomDrop(4) algorithm, on packet arrival, an Active Queue Management algorithm is executed which may randomly drop a packet. This algorithm may be proprietary, and it may drop either the arriving packet or another packet in the queue. diffServAlgDropSpecific points to a diffServRandomDropEntry that describes the algorithm. For this algorithm,
在随机丢弃（4）算法中，在分组到达时，执行主动队列管理算法，该算法可以随机丢弃分组。该算法可能是专有的，它可能会丢弃到达的数据包或队列中的另一个数据包。diffServAlgDropSpecific指向描述算法的diffServRandomDropEntry。对于这个算法，
diffServAlgDropQThreshold is understood to be the absolute maximum size of the queue and additional parameters are described in diffServRandomDropTable.
diffServAlgDropQThreshold被理解为队列的绝对最大大小，其他参数在diffServRandomDropTable中描述。
The alwaysDrop(5) algorithm is as its name specifies; always
drop. In this case, the other configuration values in this Entry
are not meaningful; There is no useful 'next' processing step,
there is no queue, and parameters describing the queue are not
useful. Therefore, diffServAlgDropNext, diffServAlgDropMeasure,
and diffServAlgDropSpecific are all zeroDotZero."
::= { diffServAlgDropEntry 2 }
The alwaysDrop(5) algorithm is as its name specifies; always
drop. In this case, the other configuration values in this Entry
are not meaningful; There is no useful 'next' processing step,
there is no queue, and parameters describing the queue are not
useful. Therefore, diffServAlgDropNext, diffServAlgDropMeasure,
and diffServAlgDropSpecific are all zeroDotZero."
::= { diffServAlgDropEntry 2 }
diffServAlgDropNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServQEntry
diffServAlgDropNext对象类型语法RowPointer MAX-ACCESS读取创建状态当前描述“这将选择下一个区分服务功能数据路径元素来处理此数据路径的流量。此RowPointer应指向以下之一的实例：diffServClfrEntry diffServMeterEntry diffServActionEntry diffServQEntry
A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path.
此属性中的值为zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。zeroDotZero是当前数据路径的最后一个功能数据路径元素的正常用法。
When diffServAlgDropType is alwaysDrop(5), this object is ignored.
当diffServAlgDropType为alwaysDrop（5）时，将忽略此对象。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServAlgDropEntry 3 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServAlgDropEntry 3 }
diffServAlgDropQMeasure OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Points to an entry in the diffServQTable to indicate the queue that a drop algorithm is to monitor when deciding whether to drop a packet. If the row pointed to does not exist, the algorithmic dropper element is considered inactive.
diffServAlgDropQMeasure对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION”指向diffServQTable中的一个条目，以指示在决定是否丢弃数据包时丢弃算法要监视的队列。如果指向的行不存在，则算法丢弃元素被视为不活动。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServAlgDropEntry 4 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServAlgDropEntry 4 }
diffServAlgDropQThreshold OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "Bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "A threshold on the depth in bytes of the queue being measured at which a trigger is generated to the dropping algorithm, unless diffServAlgDropType is alwaysDrop(5) where this object is ignored.
diffServAlgDropQThreshold对象类型语法Unsigned32（1..4294967295）单位“Bytes”MAX-ACCESS read create STATUS current DESCRIPTION“正在测量的队列的字节深度阈值，在该深度上向丢弃算法生成触发器，除非diffServAlgDropType始终是忽略此对象的drop（5）。
For the tailDrop(2) or headDrop(3) algorithms, this represents
the depth of the queue, pointed to by diffServAlgDropQMeasure, at
which the drop action will take place. Other algorithms will need
to define their own semantics for this threshold."
::= { diffServAlgDropEntry 5 }
For the tailDrop(2) or headDrop(3) algorithms, this represents
the depth of the queue, pointed to by diffServAlgDropQMeasure, at
which the drop action will take place. Other algorithms will need
to define their own semantics for this threshold."
::= { diffServAlgDropEntry 5 }
diffServAlgDropSpecific OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Points to a table entry that provides further detail regarding a drop algorithm.
diffServAlgDropSpecific对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION”指向一个表项，该表项提供有关drop算法的更多详细信息。
Entries with diffServAlgDropType equal to other(1) may have this point to a table defined in another MIB module.
diffServAlgDropType等于other（1）的条目可能指向另一个MIB模块中定义的表。
Entries with diffServAlgDropType equal to randomDrop(4) must have this point to an entry in diffServRandomDropTable.
diffServAlgDropType等于randomDrop（4）的条目必须具有指向diffServRandomDropTable中某个条目的该点。
For all other algorithms specified in this MIB, this should take the value zeroDotZero.
对于此MIB中指定的所有其他算法，该值应为zeroDotZero。
The diffServAlgDropType is authoritative for the type of the drop algorithm and the specific parameters for the drop algorithm needs to be evaluated based on the diffServAlgDropType.
diffServAlgDropType是drop算法类型的权威，drop算法的具体参数需要基于diffServAlgDropType进行评估。
Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero."
将此设置为指向不存在的目标会导致值不一致错误。如果指向的行被删除或通过其他方式变为非活动行，则处理方式与此属性包含的值zeroDotZero相同。”
::= { diffServAlgDropEntry 6 }
::= { diffServAlgDropEntry 6 }
diffServAlgDropOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that have been deterministically dropped by this drop process.
diffServAlgDropOctets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此丢弃过程已确定丢弃的八位字节数。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 7 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 7 }
diffServAlgDropPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets that have been deterministically dropped by this drop process.
diffServAlgDropPkts对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此丢弃过程已确定丢弃的数据包数。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 8 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 8 }
diffServAlgRandomDropOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that have been randomly dropped by this drop process. This counter applies, therefore, only to random droppers.
diffServAlgRandomDropOctets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此丢弃过程随机丢弃的八位字节数。因此，此计数器仅适用于随机丢弃的八位字节。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 9 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 9 }
diffServAlgRandomDropPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only
diffServAlgRandomDropPkts对象类型语法计数器64 MAX-ACCESS只读
STATUS current DESCRIPTION "The number of packets that have been randomly dropped by this drop process. This counter applies, therefore, only to random droppers.
STATUS current DESCRIPTION“此丢弃过程随机丢弃的数据包数。因此，此计数器仅适用于随机丢弃的数据包。
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 10 }
Discontinuities in the value of this counter can occur at re-
initialization of the management system and at other times as
indicated by the value of ifCounterDiscontinuityTime on the
relevant interface."
::= { diffServAlgDropEntry 10 }
diffServAlgDropStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServAlgDropEntry 11 }
diffServAlgDropStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServAlgDropEntry 11 }
diffServAlgDropStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServAlgDropEntry 12 }
diffServAlgDropStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServAlgDropEntry 12 }
-- -- Random Drop Table --
----随机下降表--
diffServRandomDropNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServRandomDropId,
or a zero to indicate that none exist."
::= { diffServAlgDrop 3 }
diffServRandomDropNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServRandomDropId,
or a zero to indicate that none exist."
::= { diffServAlgDrop 3 }
diffServRandomDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServRandomDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The random drop table contains entries describing a process that
drops packets randomly. Entries in this table are pointed to by
diffServAlgDropSpecific."
::= { diffServAlgDrop 4 }
diffServRandomDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServRandomDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The random drop table contains entries describing a process that
drops packets randomly. Entries in this table are pointed to by
diffServAlgDropSpecific."
::= { diffServAlgDrop 4 }
diffServRandomDropEntry OBJECT-TYPE
SYNTAX DiffServRandomDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a process that drops packets according to a
random algorithm."
INDEX { diffServRandomDropId }
::= { diffServRandomDropTable 1 }
diffServRandomDropEntry OBJECT-TYPE
SYNTAX DiffServRandomDropEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a process that drops packets according to a
random algorithm."
INDEX { diffServRandomDropId }
::= { diffServRandomDropTable 1 }
DiffServRandomDropEntry ::= SEQUENCE {
diffServRandomDropId IndexInteger,
diffServRandomDropMinThreshBytes Unsigned32,
diffServRandomDropMinThreshPkts Unsigned32,
diffServRandomDropMaxThreshBytes Unsigned32,
diffServRandomDropMaxThreshPkts Unsigned32,
diffServRandomDropProbMax Unsigned32,
diffServRandomDropWeight Unsigned32,
diffServRandomDropSamplingRate Unsigned32,
diffServRandomDropStorage StorageType,
diffServRandomDropStatus RowStatus
}
DiffServRandomDropEntry ::= SEQUENCE {
diffServRandomDropId IndexInteger,
diffServRandomDropMinThreshBytes Unsigned32,
diffServRandomDropMinThreshPkts Unsigned32,
diffServRandomDropMaxThreshBytes Unsigned32,
diffServRandomDropMaxThreshPkts Unsigned32,
diffServRandomDropProbMax Unsigned32,
diffServRandomDropWeight Unsigned32,
diffServRandomDropSamplingRate Unsigned32,
diffServRandomDropStorage StorageType,
diffServRandomDropStatus RowStatus
}
diffServRandomDropId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Random Drop entries. Managers
obtain new values for row creation in this table by reading
diffServRandomDropNextFree."
::= { diffServRandomDropEntry 1 }
diffServRandomDropId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Random Drop entries. Managers
obtain new values for row creation in this table by reading
diffServRandomDropNextFree."
::= { diffServRandomDropEntry 1 }
diffServRandomDropMinThreshBytes OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "bytes" MAX-ACCESS read-create STATUS current
diffServRandomDropMinThreshBytes对象类型语法Unsigned32（1..4294967295）单位“字节”最大读取创建状态当前
DESCRIPTION
"The average queue depth in bytes, beyond which traffic has a
non-zero probability of being dropped. Changes in this variable
may or may not be reflected in the reported value of
diffServRandomDropMinThreshPkts."
::= { diffServRandomDropEntry 2 }
DESCRIPTION
"The average queue depth in bytes, beyond which traffic has a
non-zero probability of being dropped. Changes in this variable
may or may not be reflected in the reported value of
diffServRandomDropMinThreshPkts."
::= { diffServRandomDropEntry 2 }
diffServRandomDropMinThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth in packets, beyond which traffic has a
non-zero probability of being dropped. Changes in this variable
may or may not be reflected in the reported value of
diffServRandomDropMinThreshBytes."
::= { diffServRandomDropEntry 3 }
diffServRandomDropMinThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth in packets, beyond which traffic has a
non-zero probability of being dropped. Changes in this variable
may or may not be reflected in the reported value of
diffServRandomDropMinThreshBytes."
::= { diffServRandomDropEntry 3 }
diffServRandomDropMaxThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshPkts."
::= { diffServRandomDropEntry 4 }
diffServRandomDropMaxThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshPkts."
::= { diffServRandomDropEntry 4 }
diffServRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshBytes."
::= { diffServRandomDropEntry 5 }
diffServRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshBytes."
::= { diffServRandomDropEntry 5 }
diffServRandomDropProbMax OBJECT-TYPE
diffServRandomDropProbMax对象类型
SYNTAX Unsigned32 (0..1000) MAX-ACCESS read-create STATUS current DESCRIPTION "The worst case random drop probability, expressed in drops per thousand packets.
语法Unsigned32（0..1000）MAX-ACCESS read create STATUS current DESCRIPTION“最坏情况下的随机丢弃概率，以每千个数据包的丢弃数表示。
For example, if in the worst case every arriving packet may be
dropped (100%) for a period, this has the value 1000.
Alternatively, if in the worst case only one percent (1%) of
traffic may be dropped, it has the value 10."
::= { diffServRandomDropEntry 6 }
For example, if in the worst case every arriving packet may be
dropped (100%) for a period, this has the value 1000.
Alternatively, if in the worst case only one percent (1%) of
traffic may be dropped, it has the value 10."
::= { diffServRandomDropEntry 6 }
diffServRandomDropWeight OBJECT-TYPE SYNTAX Unsigned32 (0..65536) MAX-ACCESS read-create STATUS current DESCRIPTION "The weighting of past history in affecting the Exponentially Weighted Moving Average function that calculates the current average queue depth. The equation uses diffServRandomDropWeight/65536 as the coefficient for the new sample in the equation, and (65536 - diffServRandomDropWeight)/65536 as the coefficient of the old value.
diffServRandomDropWeight对象类型语法Unsigned32（0..65536）MAX-ACCESS读取创建状态当前说明“影响指数加权移动平均函数（计算当前平均队列深度）的过去历史的权重。该方程使用diffServRandomDropWeight/65536作为方程中新样本的系数，（65536-diffServRandomDropWeight）/65536作为旧值的系数。
Implementations may limit the values of diffServRandomDropWeight
to a subset of the possible range of values, such as powers of
two. Doing this would facilitate implementation of the
Exponentially Weighted Moving Average using shift instructions or
registers."
::= { diffServRandomDropEntry 7 }
Implementations may limit the values of diffServRandomDropWeight
to a subset of the possible range of values, such as powers of
two. Doing this would facilitate implementation of the
Exponentially Weighted Moving Average using shift instructions or
registers."
::= { diffServRandomDropEntry 7 }
diffServRandomDropSamplingRate OBJECT-TYPE
SYNTAX Unsigned32 (0..1000000)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of times per second the queue is sampled for queue
average calculation. A value of zero is used to mean that the
queue is sampled approximately each time a packet is enqueued (or
dequeued)."
::= { diffServRandomDropEntry 8 }
diffServRandomDropSamplingRate OBJECT-TYPE
SYNTAX Unsigned32 (0..1000000)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of times per second the queue is sampled for queue
average calculation. A value of zero is used to mean that the
queue is sampled approximately each time a packet is enqueued (or
dequeued)."
::= { diffServRandomDropEntry 8 }
diffServRandomDropStorage OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current
diffServRandomDropStorage对象类型语法StorageType MAX-ACCESS读取创建状态当前
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServRandomDropEntry 9 }
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServRandomDropEntry 9 }
diffServRandomDropStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServRandomDropEntry 10 }
diffServRandomDropStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServRandomDropEntry 10 }
-- -- Queue Table --
----队列表--
diffServQueue OBJECT IDENTIFIER ::= { diffServMIBObjects 7 }
diffServQueue OBJECT IDENTIFIER ::= { diffServMIBObjects 7 }
--
-- An entry of diffServQTable represents a FIFO queue Differentiated
-- Services Functional Data Path element as described in the Informal
-- Differentiated Services Model section 7.1.1. Note that the
-- specification of scheduling parameters for a queue as part of the
-- input to a scheduler functional data path element as described in
-- the Informal Differentiated Services Model section 7.1.2. This
-- allows building of hierarchical queuing/scheduling. A queue
-- therefore has these attributes:
--
-- 1. Which scheduler will service this queue, diffServQNext.
-- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service,
-- diffServQMinRate.
--
-- Note that upstream Differentiated Services Functional Data Path
-- elements may point to a shared diffServQTable entry as described
-- in the Informal Differentiated Services Model section 7.1.1.
--
--
-- An entry of diffServQTable represents a FIFO queue Differentiated
-- Services Functional Data Path element as described in the Informal
-- Differentiated Services Model section 7.1.1. Note that the
-- specification of scheduling parameters for a queue as part of the
-- input to a scheduler functional data path element as described in
-- the Informal Differentiated Services Model section 7.1.2. This
-- allows building of hierarchical queuing/scheduling. A queue
-- therefore has these attributes:
--
-- 1. Which scheduler will service this queue, diffServQNext.
-- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service,
-- diffServQMinRate.
--
-- Note that upstream Differentiated Services Functional Data Path
-- elements may point to a shared diffServQTable entry as described
-- in the Informal Differentiated Services Model section 7.1.1.
--
diffServQNextFree OBJECT-TYPE SYNTAX IndexIntegerNextFree MAX-ACCESS read-only
diffServQNextFree对象类型语法IndexIntegerNextFree最大访问权限只读
STATUS current
DESCRIPTION
"This object contains an unused value for diffServQId, or a zero
to indicate that none exist."
::= { diffServQueue 1 }
STATUS current
DESCRIPTION
"This object contains an unused value for diffServQId, or a zero
to indicate that none exist."
::= { diffServQueue 1 }
diffServQTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServQEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Queue Table enumerates the individual queues. Note that the
MIB models queuing systems as composed of individual queues, one
per class of traffic, even though they may in fact be structured
as classes of traffic scheduled using a common calendar queue, or
in other ways."
::= { diffServQueue 2 }
diffServQTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServQEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Queue Table enumerates the individual queues. Note that the
MIB models queuing systems as composed of individual queues, one
per class of traffic, even though they may in fact be structured
as classes of traffic scheduled using a common calendar queue, or
in other ways."
::= { diffServQueue 2 }
diffServQEntry OBJECT-TYPE
SYNTAX DiffServQEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Queue Table describes a single queue or class of
traffic."
INDEX { diffServQId }
::= { diffServQTable 1 }
diffServQEntry OBJECT-TYPE
SYNTAX DiffServQEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Queue Table describes a single queue or class of
traffic."
INDEX { diffServQId }
::= { diffServQTable 1 }
DiffServQEntry ::= SEQUENCE {
diffServQId IndexInteger,
diffServQNext RowPointer,
diffServQMinRate RowPointer,
diffServQMaxRate RowPointer,
diffServQStorage StorageType,
diffServQStatus RowStatus
}
DiffServQEntry ::= SEQUENCE {
diffServQId IndexInteger,
diffServQNext RowPointer,
diffServQMinRate RowPointer,
diffServQMaxRate RowPointer,
diffServQStorage StorageType,
diffServQStatus RowStatus
}
diffServQId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Queue entries. Managers obtain new
values for row creation in this table by reading
diffServQNextFree."
::= { diffServQEntry 1 }
diffServQId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Queue entries. Managers obtain new
values for row creation in this table by reading
diffServQNextFree."
::= { diffServQEntry 1 }
diffServQNext OBJECT-TYPE
diffServQNext对象类型
SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This selects the next Differentiated Services Scheduler. The RowPointer must point to a diffServSchedulerEntry.
语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“这将选择下一个区分服务计划程序。RowPointer必须指向DiffServScheduleEntry。
A value of zeroDotZero in this attribute indicates an incomplete diffServQEntry instance. In such a case, the entry has no operational effect, since it has no parameters to give it meaning.
此属性中的值zeroDotZero表示diffServQEntry实例不完整。在这种情况下，条目没有操作效果，因为它没有赋予其含义的参数。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 2 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 2 }
diffServQMinRate OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This RowPointer indicates the diffServMinRateEntry that the scheduler, pointed to by diffServQNext, should use to service this queue.
diffServQMinRate对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“此RowPointer表示调度程序（由diffServQNext指向）应用于服务此队列的diffServMinRateEntry。
If the row pointed to is zeroDotZero, the minimum rate and priority is unspecified.
如果指向的行是zeroDotZero，则未指定最小速率和优先级。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 3 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 3 }
diffServQMaxRate OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This RowPointer indicates the diffServMaxRateEntry that the scheduler, pointed to by diffServQNext, should use to service this queue.
diffServQMaxRate对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“此RowPointer表示调度程序（由diffServQNext指向）应用于服务此队列的DiffServMaxRate条目。
If the row pointed to is zeroDotZero, the maximum rate is the line speed of the interface.
如果指向的行是zeroDotZero，则最大速率是接口的线速度。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 4 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServQEntry 4 }
diffServQStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServQEntry 5 }
diffServQStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServQEntry 5 }
diffServQStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServQEntry 6 }
diffServQStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServQEntry 6 }
-- -- Scheduler Table --
----调度程序表--
diffServScheduler OBJECT IDENTIFIER ::= { diffServMIBObjects 8 }
diffServScheduler OBJECT IDENTIFIER ::= { diffServMIBObjects 8 }
--
-- A Scheduler Entry represents a packet scheduler, such as a priority
-- scheduler or a WFQ scheduler. It provides flexibility for multiple
-- scheduling algorithms, each servicing multiple queues, to be used on
-- the same logical/physical interface.
--
-- Note that upstream queues or schedulers specify several of the
-- scheduler's parameters. These must be properly specified if the
-- scheduler is to behave as expected.
--
-- The diffServSchedulerMaxRate attribute specifies the parameters when
-- a scheduler's output is sent to another scheduler. This is used in
-- building hierarchical queues or schedulers.
--
-- A Scheduler Entry represents a packet scheduler, such as a priority
-- scheduler or a WFQ scheduler. It provides flexibility for multiple
-- scheduling algorithms, each servicing multiple queues, to be used on
-- the same logical/physical interface.
--
-- Note that upstream queues or schedulers specify several of the
-- scheduler's parameters. These must be properly specified if the
-- scheduler is to behave as expected.
--
-- The diffServSchedulerMaxRate attribute specifies the parameters when
-- a scheduler's output is sent to another scheduler. This is used in
-- building hierarchical queues or schedulers.
--
-- More discussion of the scheduler functional data path element is in
-- the Informal Differentiated Services Model section 7.1.2.
--
--
-- More discussion of the scheduler functional data path element is in
-- the Informal Differentiated Services Model section 7.1.2.
--
diffServSchedulerNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServSchedulerId, or
a zero to indicate that none exist."
::= { diffServScheduler 1 }
diffServSchedulerNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServSchedulerId, or
a zero to indicate that none exist."
::= { diffServScheduler 1 }
diffServSchedulerTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServSchedulerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Scheduler Table enumerates packet schedulers. Multiple
scheduling algorithms can be used on a given data path, with each
algorithm described by one diffServSchedulerEntry."
::= { diffServScheduler 2 }
diffServSchedulerTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServSchedulerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Scheduler Table enumerates packet schedulers. Multiple
scheduling algorithms can be used on a given data path, with each
algorithm described by one diffServSchedulerEntry."
::= { diffServScheduler 2 }
diffServSchedulerEntry OBJECT-TYPE
SYNTAX DiffServSchedulerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Scheduler Table describing a single instance of
a scheduling algorithm."
INDEX { diffServSchedulerId }
::= { diffServSchedulerTable 1 }
diffServSchedulerEntry OBJECT-TYPE
SYNTAX DiffServSchedulerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Scheduler Table describing a single instance of
a scheduling algorithm."
INDEX { diffServSchedulerId }
::= { diffServSchedulerTable 1 }
DiffServSchedulerEntry ::= SEQUENCE {
diffServSchedulerId IndexInteger,
diffServSchedulerNext RowPointer,
diffServSchedulerMethod AutonomousType,
diffServSchedulerMinRate RowPointer,
diffServSchedulerMaxRate RowPointer,
diffServSchedulerStorage StorageType,
diffServSchedulerStatus RowStatus
}
DiffServSchedulerEntry ::= SEQUENCE {
diffServSchedulerId IndexInteger,
diffServSchedulerNext RowPointer,
diffServSchedulerMethod AutonomousType,
diffServSchedulerMinRate RowPointer,
diffServSchedulerMaxRate RowPointer,
diffServSchedulerStorage StorageType,
diffServSchedulerStatus RowStatus
}
diffServSchedulerId OBJECT-TYPE SYNTAX IndexInteger MAX-ACCESS not-accessible STATUS current
diffServSchedulerId对象类型语法索引整数MAX-ACCESS不可访问状态当前
DESCRIPTION
"An index that enumerates the Scheduler entries. Managers obtain
new values for row creation in this table by reading
diffServSchedulerNextFree."
::= { diffServSchedulerEntry 1 }
DESCRIPTION
"An index that enumerates the Scheduler entries. Managers obtain
new values for row creation in this table by reading
diffServSchedulerNextFree."
::= { diffServSchedulerEntry 1 }
diffServSchedulerNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This normally is null (zeroDotZero), or points to a diffServSchedulerEntry or a diffServQEntry.
diffServSchedulerNext对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“此选项选择下一个差异化服务功能数据路径元素来处理此数据路径的流量。它通常为null（zeroDotZero），或指向diffServSchedulerEntry或diffServQEntry。
However, this RowPointer may also point to an instance of: diffServClfrEntry, diffServMeterEntry, diffServActionEntry, diffServAlgDropEntry.
但是，此行指针也可能指向以下实例：diffServClfrEntry、diffServMeterEntry、diffServActionEntry、DiffServAlgProperty。
It would point another diffServSchedulerEntry when implementing multiple scheduler methods for the same data path, such as having one set of queues scheduled by WRR and that group participating in a priority scheduling system in which other queues compete with it in that way. It might also point to a second scheduler in a hierarchical scheduling system.
当为同一数据路径实现多个调度程序方法时，它将指向另一个DiffServScheduleEntry，例如，由WRR调度一组队列，并且该组参与优先级调度系统，其中其他队列以这种方式与其竞争。它还可能指向分层调度系统中的第二个调度程序。
If the row pointed to is zeroDotZero, no further Differentiated Services treatment is performed on traffic of this data path.
如果指向的行是zeroDotZero，则不对该数据路径的流量执行进一步的区分服务处理。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 2 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 2 }
diffServSchedulerMethod OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-create STATUS current DESCRIPTION "The scheduling algorithm used by this Scheduler. zeroDotZero indicates that this is unknown. Standard values for generic algorithms: diffServSchedulerPriority, diffServSchedulerWRR, and diffServSchedulerWFQ are specified in this MIB; additional values
diffServSchedulerMethod对象类型语法AutonomousType MAX-ACCESS读取创建状态当前描述“此计划程序使用的计划算法。zeroDotZero表示这是未知的。通用算法的标准值：diffServSchedulerPriority、diffServSchedulerWRR和diffServSchedulerWFQ在此MIB中指定；附加值
may be further specified in other MIBs."
::= { diffServSchedulerEntry 3 }
may be further specified in other MIBs."
::= { diffServSchedulerEntry 3 }
diffServSchedulerMinRate OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This RowPointer indicates the entry in diffServMinRateTable which indicates the priority or minimum output rate from this scheduler. This attribute is used only when there is more than one level of scheduler.
diffServSchedulerMinRate对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“此RowPointer表示DiffServMinRate表中的条目，该条目表示此计划程序的优先级或最小输出速率。此属性仅在有多个级别的计划程序时使用。
When it has the value zeroDotZero, it indicates that no minimum rate or priority is imposed.
当它的值为zeroDotZero时，表示没有施加最小速率或优先级。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 4 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 4 }
diffServSchedulerMaxRate OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This RowPointer indicates the entry in diffServMaxRateTable which indicates the maximum output rate from this scheduler. When more than one maximum rate applies (eg, when a multi-rate shaper is in view), it points to the first of those rate entries. This attribute is used only when there is more than one level of scheduler.
diffServSchedulerMaxRate对象类型语法RowPointer MAX-ACCESS读取创建状态当前描述“此RowPointer表示diffServMaxRateTable中的条目，该条目表示此计划程序的最大输出速率。当应用多个最大速率时（例如，当多速率整形器处于视图中时），它指向这些速率项中的第一个。此属性仅在存在多个级别的计划程序时使用。
When it has the value zeroDotZero, it indicates that no maximum rate is imposed.
当其值为zeroDotZero时，表示未施加最大速率。
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 5 }
Setting this to point to a target that does not exist results in
an inconsistentValue error. If the row pointed to is removed or
becomes inactive by other means, the treatment is as if this
attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 5 }
diffServSchedulerStorage OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create
diffServSchedulerStorage对象类型语法StorageType MAX-ACCESS读取创建
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServSchedulerEntry 6 }
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServSchedulerEntry 6 }
diffServSchedulerStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServSchedulerEntry 7 }
diffServSchedulerStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServSchedulerEntry 7 }
-- -- OIDs for diffServTBParamType definitions. --
----diffServTBParamType定义的OID--
diffServSchedulers OBJECT IDENTIFIER ::= { diffServMIBAdmin 2 }
diffServSchedulers OBJECT IDENTIFIER ::= { diffServMIBAdmin 2 }
diffServSchedulerPriority OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with diffServSchedulerMethod to indicate the Priority
scheduling method. This is defined as an algorithm in which the
presence of data in a queue or set of queues absolutely precludes
dequeue from another queue or set of queues of lower priority.
Note that attributes from diffServMinRateEntry of the
queues/schedulers feeding this scheduler are used when
determining the next packet to schedule."
::= { diffServSchedulers 1 }
diffServSchedulerPriority OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with diffServSchedulerMethod to indicate the Priority
scheduling method. This is defined as an algorithm in which the
presence of data in a queue or set of queues absolutely precludes
dequeue from another queue or set of queues of lower priority.
Note that attributes from diffServMinRateEntry of the
queues/schedulers feeding this scheduler are used when
determining the next packet to schedule."
::= { diffServSchedulers 1 }
diffServSchedulerWRR OBJECT-IDENTITY STATUS current DESCRIPTION "For use with diffServSchedulerMethod to indicate the Weighted Round Robin scheduling method, defined as any algorithm in which a set of queues are visited in a fixed order, and varying amounts of traffic are removed from each queue in turn to implement an average output rate by class. Notice attributes from diffServMinRateEntry of the queues/schedulers feeding this scheduler are used when determining the next packet to schedule."
diffServSchedulerWRR对象标识状态当前描述“与diffServSchedulerMethod一起使用，表示加权循环调度方法，定义为以固定顺序访问一组队列的任何算法，并依次从每个队列中移除不同数量的通信量，以按类实现平均输出速率。请注意，在确定要调度的下一个数据包时，将使用向此调度程序提供数据的队列/调度程序的diffServMinRateEntry中的属性。”
::= { diffServSchedulers 2 }
::= { diffServSchedulers 2 }
diffServSchedulerWFQ OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with diffServSchedulerMethod to indicate the Weighted
Fair Queuing scheduling method, defined as any algorithm in which
a set of queues are conceptually visited in some order, to
implement an average output rate by class. Notice attributes from
diffServMinRateEntry of the queues/schedulers feeding this
scheduler are used when determining the next packet to schedule."
::= { diffServSchedulers 3 }
diffServSchedulerWFQ OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with diffServSchedulerMethod to indicate the Weighted
Fair Queuing scheduling method, defined as any algorithm in which
a set of queues are conceptually visited in some order, to
implement an average output rate by class. Notice attributes from
diffServMinRateEntry of the queues/schedulers feeding this
scheduler are used when determining the next packet to schedule."
::= { diffServSchedulers 3 }
--
-- Minimum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries for
-- reusability reasons and so that they may be used by both queues and
-- schedulers. This follows the approach for separation of data path
-- elements from parameterization that is used throughout this MIB.
-- Use of these Minimum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a second
-- scheduler, might specify a minimum transfer rate by pointing to an
-- Minimum Rate Parameter Table entry.
--
-- The diffServMinRatePriority/Abs/Rel attributes are used as
-- parameters to the work-conserving portion of a scheduler:
-- "work-conserving" implies that the scheduler can continue to emit
-- data as long as there is data available at its input(s). This has
-- the effect of guaranteeing a certain priority relative to other
-- scheduler inputs and/or a certain minimum proportion of the
-- available output bandwidth. Properly configured, this means a
-- certain minimum rate, which may be exceeded should traffic be
-- available should there be spare bandwidth after all other classes
-- have had opportunities to consume their own minimum rates.
--
--
-- Minimum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries for
-- reusability reasons and so that they may be used by both queues and
-- schedulers. This follows the approach for separation of data path
-- elements from parameterization that is used throughout this MIB.
-- Use of these Minimum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a second
-- scheduler, might specify a minimum transfer rate by pointing to an
-- Minimum Rate Parameter Table entry.
--
-- The diffServMinRatePriority/Abs/Rel attributes are used as
-- parameters to the work-conserving portion of a scheduler:
-- "work-conserving" implies that the scheduler can continue to emit
-- data as long as there is data available at its input(s). This has
-- the effect of guaranteeing a certain priority relative to other
-- scheduler inputs and/or a certain minimum proportion of the
-- available output bandwidth. Properly configured, this means a
-- certain minimum rate, which may be exceeded should traffic be
-- available should there be spare bandwidth after all other classes
-- have had opportunities to consume their own minimum rates.
--
diffServMinRateNextFree OBJECT-TYPE SYNTAX IndexIntegerNextFree MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an unused value for diffServMinRateId, or a zero to indicate that none exist."
diffServMinRateNextFree对象类型语法IndexIntegerNextFree MAX-ACCESS只读状态当前描述“此对象包含diffServMinRateId的未使用值，或零表示不存在。”
::= { diffServScheduler 3 }
::= { diffServScheduler 3 }
diffServMinRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServMinRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Minimum Rate Parameters Table enumerates individual sets of
scheduling parameter that can be used/reused by Queues and
Schedulers."
::= { diffServScheduler 4 }
diffServMinRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServMinRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Minimum Rate Parameters Table enumerates individual sets of
scheduling parameter that can be used/reused by Queues and
Schedulers."
::= { diffServScheduler 4 }
diffServMinRateEntry OBJECT-TYPE
SYNTAX DiffServMinRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Minimum Rate Parameters Table describes a single
set of scheduling parameters for use by one or more queues or
schedulers."
INDEX { diffServMinRateId }
::= { diffServMinRateTable 1 }
diffServMinRateEntry OBJECT-TYPE
SYNTAX DiffServMinRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Minimum Rate Parameters Table describes a single
set of scheduling parameters for use by one or more queues or
schedulers."
INDEX { diffServMinRateId }
::= { diffServMinRateTable 1 }
DiffServMinRateEntry ::= SEQUENCE {
diffServMinRateId IndexInteger,
diffServMinRatePriority Unsigned32,
diffServMinRateAbsolute Unsigned32,
diffServMinRateRelative Unsigned32,
diffServMinRateStorage StorageType,
diffServMinRateStatus RowStatus
}
DiffServMinRateEntry ::= SEQUENCE {
diffServMinRateId IndexInteger,
diffServMinRatePriority Unsigned32,
diffServMinRateAbsolute Unsigned32,
diffServMinRateRelative Unsigned32,
diffServMinRateStorage StorageType,
diffServMinRateStatus RowStatus
}
diffServMinRateId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Scheduler Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServMinRateNextFree."
::= { diffServMinRateEntry 1 }
diffServMinRateId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Scheduler Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServMinRateNextFree."
::= { diffServMinRateEntry 1 }
diffServMinRatePriority OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-create STATUS current DESCRIPTION "The priority of this input to the associated scheduler, relative
diffServMinRatePriority对象类型语法Unsigned32（1..4294967295）MAX-ACCESS read create STATUS current DESCRIPTION“关联调度程序的此输入的优先级，相对
to the scheduler's other inputs. A queue or scheduler with a
larger numeric value will be served before another with a smaller
numeric value."
::= { diffServMinRateEntry 2 }
to the scheduler's other inputs. A queue or scheduler with a
larger numeric value will be served before another with a smaller
numeric value."
::= { diffServMinRateEntry 2 }
diffServMinRateAbsolute OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum absolute rate, in kilobits/sec, that a downstream scheduler element should allocate to this queue. If the value is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate.
diffServMinRateAbsolute对象类型语法无符号32（1..4294967295）单位“千比特每秒”最大访问读取创建状态当前描述下游调度程序元素应分配给此队列的最小绝对速率，单位为千比特/秒。如果该值为零，则实际上没有最低利率保证。如果该值不为零，调度程序将确保该队列的服务至少达到该速率。
Note that this attribute value and that of diffServMinRateRelative are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other:
请注意，此属性值与diffServMinRateRelative的属性值是耦合的：对一个属性值的更改将影响另一个属性值。它们通过以下等式连接，在该设置中，一个将改变另一个：
diffServMinRateRelative = (diffServMinRateAbsolute*1000000)/ifSpeed
diffServMinRateRelative=（diffServMinRateAbsolute*1000000）/ifSpeed
or, if appropriate:
或在适当情况下：
diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMinRateEntry 3 }
diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMinRateEntry 3 }
diffServMinRateRelative OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum rate that a downstream scheduler element should allocate to this queue, relative to the maximum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1000 of 1. If the value is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate.
diffServMinRateRelative对象类型语法Unsigned32（1..4294967295）MAX-ACCESS读取创建状态当前说明“相对于ifSpeed或ifHighSpeed报告的接口最大速率，下游调度程序元素应分配给此队列的最小速率，单位为1/1000/1。如果该值为零，则实际上没有最低利率保证。如果该值不为零，调度程序将确保该队列的服务至少达到该速率。
Note that this attribute value and that of diffServMinRateAbsolute are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other:
请注意，此属性值与diffServMinRateAbsolute的属性值是耦合的：对一个属性值的更改将影响另一个属性值。它们通过以下等式连接，在该设置中，一个将改变另一个：
diffServMinRateRelative = (diffServMinRateAbsolute*1000000)/ifSpeed
diffServMinRateRelative=（diffServMinRateAbsolute*1000000）/ifSpeed
or, if appropriate:
或在适当情况下：
diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMinRateEntry 4 }
diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMinRateEntry 4 }
diffServMinRateStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMinRateEntry 5 }
diffServMinRateStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMinRateEntry 5 }
diffServMinRateStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMinRateEntry 6 }
diffServMinRateStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMinRateEntry 6 }
--
-- Maximum Rate Parameter Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries for
-- reusability reasons and so that they may be used by both queues and
-- schedulers. This follows the approach for separation of data path
-- elements from parameterization that is used throughout this MIB.
-- Use of these Maximum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a second
-- scheduler, might specify a maximum transfer rate by pointing to a
-- Maximum Rate Parameter Table entry. Multi-rate shapers, such as a
--
-- Maximum Rate Parameter Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries for
-- reusability reasons and so that they may be used by both queues and
-- schedulers. This follows the approach for separation of data path
-- elements from parameterization that is used throughout this MIB.
-- Use of these Maximum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a second
-- scheduler, might specify a maximum transfer rate by pointing to a
-- Maximum Rate Parameter Table entry. Multi-rate shapers, such as a
-- Dual Leaky Bucket algorithm, specify their rates using multiple
-- Maximum Rate Parameter Entries with the same diffServMaxRateId but
-- different diffServMaxRateLevels.
--
-- The diffServMaxRateLevel/Abs/Rel attributes are used as
-- parameters to the non-work-conserving portion of a scheduler:
-- non-work-conserving implies that the scheduler may sometimes not
-- emit a packet, even if there is data available at its input(s).
-- This has the effect of limiting the servicing of the queue/scheduler
-- input or output, in effect performing shaping of the packet stream
-- passing through the queue/scheduler, as described in the Informal
-- Differentiated Services Model section 7.2.
--
-- Dual Leaky Bucket algorithm, specify their rates using multiple
-- Maximum Rate Parameter Entries with the same diffServMaxRateId but
-- different diffServMaxRateLevels.
--
-- The diffServMaxRateLevel/Abs/Rel attributes are used as
-- parameters to the non-work-conserving portion of a scheduler:
-- non-work-conserving implies that the scheduler may sometimes not
-- emit a packet, even if there is data available at its input(s).
-- This has the effect of limiting the servicing of the queue/scheduler
-- input or output, in effect performing shaping of the packet stream
-- passing through the queue/scheduler, as described in the Informal
-- Differentiated Services Model section 7.2.
--
diffServMaxRateNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServMaxRateId, or a
zero to indicate that none exist."
::= { diffServScheduler 5 }
diffServMaxRateNextFree OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for diffServMaxRateId, or a
zero to indicate that none exist."
::= { diffServScheduler 5 }
diffServMaxRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServMaxRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Maximum Rate Parameter Table enumerates individual sets of
scheduling parameter that can be used/reused by Queues and
Schedulers."
::= { diffServScheduler 6 }
diffServMaxRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServMaxRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Maximum Rate Parameter Table enumerates individual sets of
scheduling parameter that can be used/reused by Queues and
Schedulers."
::= { diffServScheduler 6 }
diffServMaxRateEntry OBJECT-TYPE
SYNTAX DiffServMaxRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Maximum Rate Parameter Table describes a single
set of scheduling parameters for use by one or more queues or
schedulers."
INDEX { diffServMaxRateId, diffServMaxRateLevel }
::= { diffServMaxRateTable 1 }
diffServMaxRateEntry OBJECT-TYPE
SYNTAX DiffServMaxRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Maximum Rate Parameter Table describes a single
set of scheduling parameters for use by one or more queues or
schedulers."
INDEX { diffServMaxRateId, diffServMaxRateLevel }
::= { diffServMaxRateTable 1 }
DiffServMaxRateEntry ::= SEQUENCE {
diffServMaxRateId IndexInteger,
diffServMaxRateLevel Unsigned32,
diffServMaxRateAbsolute Unsigned32,
DiffServMaxRateEntry ::= SEQUENCE {
diffServMaxRateId IndexInteger,
diffServMaxRateLevel Unsigned32,
diffServMaxRateAbsolute Unsigned32,
diffServMaxRateRelative Unsigned32, diffServMaxRateThreshold BurstSize, diffServMaxRateStorage StorageType, diffServMaxRateStatus RowStatus }
diffServMaxRateRelative Unsigned32，diffServMaxRateThreshold BurstSize，diffServMaxRateStorage StorageType，diffServMaxRateStatus RowStatus}
diffServMaxRateId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Maximum Rate Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServMaxRateNextFree."
::= { diffServMaxRateEntry 1 }
diffServMaxRateId OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Maximum Rate Parameter entries.
Managers obtain new values for row creation in this table by
reading diffServMaxRateNextFree."
::= { diffServMaxRateEntry 1 }
diffServMaxRateLevel OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that indicates which level of a multi-rate shaper is
being given its parameters. A multi-rate shaper has some number
of rate levels. Frame Relay's dual rate specification refers to a
'committed' and an 'excess' rate; ATM's dual rate specification
refers to a 'mean' and a 'peak' rate. This table is generalized
to support an arbitrary number of rates. The committed or mean
rate is level 1, the peak rate (if any) is the highest level rate
configured, and if there are other rates they are distributed in
monotonically increasing order between them."
::= { diffServMaxRateEntry 2 }
diffServMaxRateLevel OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that indicates which level of a multi-rate shaper is
being given its parameters. A multi-rate shaper has some number
of rate levels. Frame Relay's dual rate specification refers to a
'committed' and an 'excess' rate; ATM's dual rate specification
refers to a 'mean' and a 'peak' rate. This table is generalized
to support an arbitrary number of rates. The committed or mean
rate is level 1, the peak rate (if any) is the highest level rate
configured, and if there are other rates they are distributed in
monotonically increasing order between them."
::= { diffServMaxRateEntry 2 }
diffServMaxRateAbsolute OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum rate in kilobits/sec that a downstream scheduler element should allocate to this queue. If the value is zero, then there is effectively no maximum rate limit and that the scheduler should attempt to be work conserving for this queue. If the value is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner.
diffServMaxRateAbsolute对象类型语法无符号32（1..4294967295）单位“千比特每秒”最大访问读取创建状态当前说明“下游调度程序元素应分配到此队列的最大速率（以千比特/秒为单位）。如果该值为零，则实际上没有最大速率限制，并且调度程序应尝试为该队列节省工作量。如果该值不为零，调度程序将以非节省工时的方式将此队列的服务限制为最多此速率。
Note that this attribute value and that of diffServMaxRateRelative are coupled: changes to one will affect the value of the other. They are linked by the following
请注意，此属性值与diffServMaxRateRelative的属性值是耦合的：对一个属性值的更改将影响另一个属性值。它们由以下内容链接：
equation, in that setting one will change the other:
等式，在该设置中，一个将改变另一个：
diffServMaxRateRelative = (diffServMaxRateAbsolute*1000000)/ifSpeed
diffServMaxRateRelative=（diffServMaxRateAbsolute*1000000）/ifSpeed
or, if appropriate:
或在适当情况下：
diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMaxRateEntry 3 }
diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMaxRateEntry 3 }
diffServMaxRateRelative OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum rate that a downstream scheduler element should allocate to this queue, relative to the maximum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1000 of 1. If the value is zero, then there is effectively no maximum rate limit and the scheduler should attempt to be work conserving for this queue. If the value is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner.
diffServMaxRateRelative对象类型语法Unsigned32（1..4294967295）MAX-ACCESS读取创建状态当前说明“相对于ifSpeed或ifHighSpeed报告的接口最大速率，下游调度程序元素应分配给此队列的最大速率，单位为1/1000/1。如果该值为零，则实际上没有最大速率限制，调度程序应尝试为该队列节省工作。如果该值不为零，调度程序将以非节省工时的方式将此队列的服务限制为最多此速率。
Note that this attribute value and that of diffServMaxRateAbsolute are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other:
请注意，此属性值与diffServMaxRateAbsolute的属性值是耦合的：对一个属性值的更改将影响另一个属性值。它们通过以下等式连接，在该设置中，一个将改变另一个：
diffServMaxRateRelative = (diffServMaxRateAbsolute*1000000)/ifSpeed
diffServMaxRateRelative=（diffServMaxRateAbsolute*1000000）/ifSpeed
or, if appropriate:
或在适当情况下：
diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMaxRateEntry 4 }
diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed"
REFERENCE
"ifSpeed, ifHighSpeed, Interface MIB, RFC 2863"
::= { diffServMaxRateEntry 4 }
diffServMaxRateThreshold OBJECT-TYPE SYNTAX BurstSize UNITS "Bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of bytes of queue depth at which the rate of a
diffServMaxRateThreshold对象类型语法BurstSize UNITS“Bytes”MAX-ACCESS read create STATUS current DESCRIPTION“队列深度的字节数，其中
multi-rate scheduler will increase to the next output rate. In
the last conceptual row for such a shaper, this threshold is
ignored and by convention is zero."
REFERENCE
"Adaptive rate Shaper, RFC 2963"
::= { diffServMaxRateEntry 5 }
multi-rate scheduler will increase to the next output rate. In
the last conceptual row for such a shaper, this threshold is
ignored and by convention is zero."
REFERENCE
"Adaptive rate Shaper, RFC 2963"
::= { diffServMaxRateEntry 5 }
diffServMaxRateStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMaxRateEntry 6 }
diffServMaxRateStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access to any
columnar objects in the row."
DEFVAL { nonVolatile }
::= { diffServMaxRateEntry 6 }
diffServMaxRateStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMaxRateEntry 7 }
diffServMaxRateStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable objects in this
row may be modified at any time. Setting this variable to
'destroy' when the MIB contains one or more RowPointers pointing
to it results in destruction being delayed until the row is no
longer used."
::= { diffServMaxRateEntry 7 }
-- -- MIB Compliance statements. --
----MIB合规性声明--
diffServMIBCompliances OBJECT IDENTIFIER ::=
{ diffServMIBConformance 1 }
diffServMIBGroups OBJECT IDENTIFIER ::=
{ diffServMIBConformance 2 }
diffServMIBCompliances OBJECT IDENTIFIER ::=
{ diffServMIBConformance 1 }
diffServMIBGroups OBJECT IDENTIFIER ::=
{ diffServMIBConformance 2 }
diffServMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented with support for read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB."
diffServMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“当此MIB在支持读创建的情况下实现时，这样的实现可以声明完全符合要求。然后可以使用此MIB监视和配置此类设备。”
MODULE IF-MIB -- The interfaces MIB, RFC2863 MANDATORY-GROUPS {
模块IF-MIB——接口MIB、RFC2863-GROUPS{
ifCounterDiscontinuityGroup }
IfCounteryGroup}
MODULE -- This Module
MANDATORY-GROUPS {
diffServMIBDataPathGroup, diffServMIBClfrGroup,
diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup,
diffServMIBActionGroup, diffServMIBAlgDropGroup,
diffServMIBQGroup, diffServMIBSchedulerGroup,
diffServMIBMaxRateGroup, diffServMIBMinRateGroup,
diffServMIBCounterGroup
}
MODULE -- This Module
MANDATORY-GROUPS {
diffServMIBDataPathGroup, diffServMIBClfrGroup,
diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup,
diffServMIBActionGroup, diffServMIBAlgDropGroup,
diffServMIBQGroup, diffServMIBSchedulerGroup,
diffServMIBMaxRateGroup, diffServMIBMinRateGroup,
diffServMIBCounterGroup
}
GROUP diffServMIBMeterGroup DESCRIPTION "This group is mandatory for devices that implement metering functions."
GROUP diffServMIBMeterGroup DESCRIPTION“此组对于实现计量功能的设备是必需的。”
GROUP diffServMIBTBParamGroup DESCRIPTION "This group is mandatory for devices that implement token-bucket metering functions."
GROUP diffServMIBTBParamGroup DESCRIPTION“对于实现令牌桶计量功能的设备，此组是必需的。”
GROUP diffServMIBDscpMarkActGroup DESCRIPTION "This group is mandatory for devices that implement DSCP-Marking functions."
GROUP diffServMIBDscpMarkActGroup DESCRIPTION“此组对于实现DSCP标记功能的设备是必需的。”
GROUP diffServMIBRandomDropGroup DESCRIPTION "This group is mandatory for devices that implement Random Drop functions."
GROUP diffServMIBRandomDropGroup DESCRIPTION“对于实现随机丢弃功能的设备，此组是必需的。”
OBJECT diffServDataPathStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServDataPathStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServClfrStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServClfrStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServClfrElementStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
OBJECT diffServClfrElementStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notInService is not required."
描述“不需要对createAndWait和notInService的支持。”
OBJECT diffServMultiFieldClfrAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support IPv4 and IPv6 addresses."
对象diffServMultiFieldClfrAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“仅支持ipv4和ipv6地址才需要实现。”
OBJECT diffServMultiFieldClfrDstAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象diffServMultiFieldClfrDstAddr语法InetAddress（大小（0 | 4 | 16））说明“仅支持IPv4和全局唯一IPv6地址才需要实现。”
OBJECT diffServAlgDropStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServAlgDropStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServRandomDropStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServRandomDropStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServQStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServQStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServSchedulerStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServSchedulerStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServMinRateStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServMinRateStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT diffServMaxRateStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
OBJECT diffServMaxRateStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notInService is not required."
描述“不需要对createAndWait和notInService的支持。”
::= { diffServMIBCompliances 1 }
::= { diffServMIBCompliances 1 }
-- -- Read-Only Compliance --
----只读遵从性--
diffServMIBReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented without support for read-create (i.e. in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but can not be configured with this MIB."
diffServMIBReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“当此MIB在不支持读取创建的情况下实现（即在只读模式下），则此实现可以声明只读符合性。这样的设备可以进行监视，但不能使用此MIB进行配置。”
MODULE IF-MIB -- The interfaces MIB, RFC2863
MANDATORY-GROUPS {
ifCounterDiscontinuityGroup
}
MODULE IF-MIB -- The interfaces MIB, RFC2863
MANDATORY-GROUPS {
ifCounterDiscontinuityGroup
}
MODULE -- This Module
MANDATORY-GROUPS {
diffServMIBDataPathGroup, diffServMIBClfrGroup,
diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup,
diffServMIBActionGroup, diffServMIBAlgDropGroup,
diffServMIBQGroup, diffServMIBSchedulerGroup,
diffServMIBMaxRateGroup, diffServMIBMinRateGroup,
diffServMIBCounterGroup
}
MODULE -- This Module
MANDATORY-GROUPS {
diffServMIBDataPathGroup, diffServMIBClfrGroup,
diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup,
diffServMIBActionGroup, diffServMIBAlgDropGroup,
diffServMIBQGroup, diffServMIBSchedulerGroup,
diffServMIBMaxRateGroup, diffServMIBMinRateGroup,
diffServMIBCounterGroup
}
GROUP diffServMIBMeterGroup DESCRIPTION "This group is mandatory for devices that implement metering functions."
GROUP diffServMIBMeterGroup DESCRIPTION“此组对于实现计量功能的设备是必需的。”
GROUP diffServMIBTBParamGroup DESCRIPTION "This group is mandatory for devices that implement token-bucket metering functions."
GROUP diffServMIBTBParamGroup DESCRIPTION“对于实现令牌桶计量功能的设备，此组是必需的。”
GROUP diffServMIBDscpMarkActGroup DESCRIPTION "This group is mandatory for devices that implement DSCP-Marking functions."
GROUP diffServMIBDscpMarkActGroup DESCRIPTION“此组对于实现DSCP标记功能的设备是必需的。”
GROUP diffServMIBRandomDropGroup
组diffServMIBRandomDropGroup
DESCRIPTION "This group is mandatory for devices that implement Random Drop functions."
DESCRIPTION“此组对于实现随机丢弃功能的设备是必需的。”
OBJECT diffServDataPathStart MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServDataPathStart最小访问只读说明“不需要写入访问权限。”
OBJECT diffServDataPathStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServDataPathStorage MIN-ACCESS只读说明“不需要写访问权限。”
OBJECT diffServDataPathStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServDataPathStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServClfrNextFree MIN-ACCESS not-accessible DESCRIPTION "Object not needed when diffServClfrTable is implemented read-only"
对象diffServClfrNextFree最小访问不可访问描述“当diffServClfrTable以只读方式实现时不需要对象”
OBJECT diffServClfrStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServClfrStorage最小访问只读描述“不需要写访问。”
OBJECT diffServClfrStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServClfrStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServClfrElementNextFree MIN-ACCESS not-accessible DESCRIPTION "Object not needed when diffServClfrelementTable is implemented read-only"
对象diffServClfrElementNextFree最小访问不可访问描述“当diffServClfrelementTable以只读方式实现时不需要对象”
OBJECT diffServClfrElementPrecedence MIN-ACCESS read-only DESCRIPTION
对象DiffServClFrelementPreference最小访问只读描述
"Write access is not required."
“不需要写访问权限。”
OBJECT diffServClfrElementNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServClfrElementNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServClfrElementSpecific MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServClfrElementSpecific MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServClfrElementStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServClfrElementStorage最小访问只读说明“不需要写访问。”
OBJECT diffServClfrElementStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServClfrElementStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServMultiFieldClfrNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServMultiFieldClfrTable is implemented in read-only mode."
对象diffServMultiFieldClfrNextFree最小访问不可访问描述“当以只读模式实现diffServMultiFieldClfrTable时，不需要对象。”
OBJECT diffServMultiFieldClfrAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support IPv4 and IPv6 addresses."
对象diffServMultiFieldClfrAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}MIN-ACCESS只读说明“不需要写访问。只需要实现来支持ipv4和ipv6地址。”
OBJECT diffServMultiFieldClfrDstAddr SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象diffServMultiFieldClfrDstAddr语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“不需要写访问。只需要实现来支持IPv4和全局唯一的IPv6地址。”
OBJECT diffServMultiFieldClfrDstPrefixLength MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultiFieldCfRDSTPrefixLength最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrSrcAddr MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象DiffServMultifiedCLFRSRCADDR MIN-ACCESS只读说明“不需要写访问。只需要实现来支持IPv4和全局唯一的IPv6地址。”
OBJECT diffServMultiFieldClfrSrcPrefixLength MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultiFieldCfRSRCPrefixLength最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrDscp MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultifiedCLFRDSCP最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrFlowId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMultiFieldClfrFlowId最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrProtocol MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMultiFieldClfrProtocol最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrDstL4PortMin MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultiFieldCfRfStl4Portmin最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrDstL4PortMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultiFieldCfRfStl4PortMax最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrSrcL4PortMin MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMultiFieldClfrSrcL4PortMin最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrSrcL4PortMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMultiFieldCfRSRCL4PortMax最小访问只读说明“不需要写访问。”
OBJECT diffServMultiFieldClfrStorage MIN-ACCESS read-only
对象diffServMultiFieldClfrStorage最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT diffServMultiFieldClfrStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required, createAndWait and notInService support is not required."
对象diffServMultiFieldClfrStatus最小访问只读描述“不需要写访问，不需要createAndWait和notInService支持。”
OBJECT diffServMeterNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServMultiFieldClfrTable is implemented in read-only mode."
对象DiffServeMeterNextFree最小访问不可访问描述“当diffServMultiFieldClfrTable以只读模式实现时，不需要对象。”
OBJECT diffServMeterSucceedNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeMeterSucceedNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServMeterFailNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeMeterFailNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServMeterSpecific MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMeterSpecific最小访问只读描述“不需要写访问。”
OBJECT diffServMeterStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeMeters存储最小访问只读描述“不需要写访问。”
OBJECT diffServMeterStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象DiffServeMeterStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServTBParamNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServTBParamTable is implemented in read-only mode."
对象diffServTBParamNextFree最小访问不可访问描述“当diffServTBParamTable以只读模式实现时，不需要对象。”
OBJECT diffServTBParamType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServTBParamType最小访问只读说明“不需要写访问。”
OBJECT diffServTBParamRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServTBParamRate最小访问只读说明“不需要写访问。”
OBJECT diffServTBParamBurstSize MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServTBParamBurstSize最小访问只读说明“不需要写访问。”
OBJECT diffServTBParamInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServTBParamInterval最小访问只读说明“不需要写访问。”
OBJECT diffServTBParamStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServTBParamStorage MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServTBParamStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServTBParamStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServActionNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServActionTable is implemented in read-only mode."
对象DiffServeActionNextFree最小访问不可访问描述“当以只读模式实现DiffServeActionTable时，不需要对象。”
OBJECT diffServActionInterface MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeActionInterface最小访问只读说明“不需要写访问。”
OBJECT diffServActionNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeActionNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServActionSpecific MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeActionSpecific MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServActionStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServeActionStorage最小访问只读说明“不需要写入访问权限。”
OBJECT diffServActionStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象DiffServeActionStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServCountActNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServCountActTable is implemented in read-only mode."
对象diffServCountActNextFree最小访问不可访问描述“当diffServCountActTable以只读模式实现时，不需要对象。”
OBJECT diffServCountActStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServCountActStorage MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServCountActStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServCountActStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServAlgDropNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServAlgDropTable is implemented in read-only mode."
对象diffServAlgDropNextFree最小访问不可访问描述“当diffServAlgDropTable以只读模式实现时，不需要对象。”
OBJECT diffServAlgDropType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT diffServAlgDropType MIN-ACCESS read-only DESCRIPTION "Write access is not required."translate error, please retry
OBJECT diffServAlgDropNext MIN-ACCESS read-only
对象diffServAlgDropNext最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT diffServAlgDropQMeasure MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServAlgDropQMeasure最小访问只读说明“不需要写访问。”
OBJECT diffServAlgDropQThreshold MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServAlgDropQThreshold最小访问只读描述“不需要写访问。”
OBJECT diffServAlgDropSpecific MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServAlgDropSpecific最小访问只读描述“不需要写访问。”
OBJECT diffServAlgDropStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServAlgDropStorage MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServAlgDropStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServAlgDropStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，而active是唯一需要支持的状态。”
OBJECT diffServRandomDropNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServRandomDropTable is implemented in read-only mode."
对象diffServRandomDropNextFree最小访问不可访问描述“当diffServRandomDropTable以只读模式实现时，不需要对象。”
OBJECT diffServRandomDropMinThreshBytes MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropMinThreshBytes最小访问只读说明“不需要写访问。”
OBJECT diffServRandomDropMinThreshPkts MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropMinThreshPkts最小访问只读说明“不需要写访问。”
OBJECT diffServRandomDropMaxThreshBytes MIN-ACCESS read-only
对象diffServRandomDropMaxThreshBytes最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT diffServRandomDropMaxThreshPkts MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropMaxThreshPkts最小访问只读说明“不需要写访问。”
OBJECT diffServRandomDropProbMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropProbMax最小访问只读描述“不需要写访问。”
OBJECT diffServRandomDropWeight MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropWeight最小访问只读描述“不需要写访问。”
OBJECT diffServRandomDropSamplingRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropSamplingRate最小访问只读描述“不需要写访问。”
OBJECT diffServRandomDropStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServRandomDropStorage最小访问只读描述“不需要写访问。”
OBJECT diffServRandomDropStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServRandomDropStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServQNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServQTable is implemented in read-only mode."
对象diffServQNextFree最小访问不可访问描述“当以只读模式实现diffServQTable时，不需要对象。”
OBJECT diffServQNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServQNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServQMinRate MIN-ACCESS read-only
对象diffServQMinRate最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT diffServQMaxRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServQMaxRate最小访问只读说明“不需要写访问。”
OBJECT diffServQStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServQStorage最小访问只读描述“不需要写访问。”
OBJECT diffServQStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServQStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，而active是唯一需要支持的状态。”
OBJECT diffServSchedulerNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServSchedulerTable is implemented in read-only mode."
对象diffServSchedulerNextFree最小访问不可访问描述“当diffServSchedulerTable以只读模式实现时，不需要对象。”
OBJECT diffServSchedulerNext MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServSchedulerNext MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServSchedulerMethod MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServSchedulerMethod最小访问只读描述“不需要写访问。”
OBJECT diffServSchedulerMinRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServSchedulerMin-ACCESS只读说明“不需要写访问。”
OBJECT diffServSchedulerMaxRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServSchedulerMaxRate最小访问只读说明“不需要写访问。”
OBJECT diffServSchedulerStorage MIN-ACCESS read-only
对象diffServSchedulerStorage最小访问权限只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT diffServSchedulerStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServSchedulerStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServMinRateNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServMinRateTable is implemented in read-only mode."
对象diffServMinRateNextFree MIN-ACCESS不可访问描述“当以只读模式实现diffServMinRateTable时，不需要对象。”
OBJECT diffServMinRatePriority MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMinRatePriority MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServMinRateAbsolute MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMinRate绝对最小访问只读描述“不需要写访问。”
OBJECT diffServMinRateRelative MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMinRate相对最小访问只读描述“不需要写访问。”
OBJECT diffServMinRateStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMinRateStorage MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServMinRateStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServMinRateStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT diffServMaxRateNextFree MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when diffServMaxrateTable is implemented in read-only mode."
对象diffServMaxRateNextFree最小访问不可访问描述“当以只读模式实现diffServMaxrateTable时，不需要对象。”
OBJECT diffServMaxRateAbsolute MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象DiffServMaxRate绝对最小访问只读描述“不需要写访问。”
OBJECT diffServMaxRateRelative MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMaxRateRelative MIN-ACCESS只读说明“不需要写访问。”
OBJECT diffServMaxRateThreshold MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMaxRateThreshold最小访问只读描述“不需要写访问。”
OBJECT diffServMaxRateStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象diffServMaxRateStorage最小访问只读说明“不需要写访问。”
OBJECT diffServMaxRateStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象diffServMaxRateStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
::= { diffServMIBCompliances 2 }
::= { diffServMIBCompliances 2 }
diffServMIBDataPathGroup OBJECT-GROUP
OBJECTS {
diffServDataPathStart, diffServDataPathStorage,
diffServDataPathStatus
}
STATUS current
DESCRIPTION
"The Data Path Group defines the MIB Objects that describe a
functional data path."
::= { diffServMIBGroups 1 }
diffServMIBDataPathGroup OBJECT-GROUP
OBJECTS {
diffServDataPathStart, diffServDataPathStorage,
diffServDataPathStatus
}
STATUS current
DESCRIPTION
"The Data Path Group defines the MIB Objects that describe a
functional data path."
::= { diffServMIBGroups 1 }
diffServMIBClfrGroup OBJECT-GROUP
OBJECTS {
diffServClfrNextFree, diffServClfrStorage,
diffServClfrStatus
}
STATUS current
DESCRIPTION
"The Classifier Group defines the MIB Objects that describe the
diffServMIBClfrGroup OBJECT-GROUP
OBJECTS {
diffServClfrNextFree, diffServClfrStorage,
diffServClfrStatus
}
STATUS current
DESCRIPTION
"The Classifier Group defines the MIB Objects that describe the
list the starts of individual classifiers."
::= { diffServMIBGroups 2 }
list the starts of individual classifiers."
::= { diffServMIBGroups 2 }
diffServMIBClfrElementGroup OBJECT-GROUP
OBJECTS {
diffServClfrElementNextFree,
diffServClfrElementPrecedence, diffServClfrElementNext,
diffServClfrElementSpecific, diffServClfrElementStorage,
diffServClfrElementStatus
}
STATUS current
DESCRIPTION
"The Classifier Element Group defines the MIB Objects that
describe the classifier elements that make up a generic
classifier."
::= { diffServMIBGroups 3 }
diffServMIBClfrElementGroup OBJECT-GROUP
OBJECTS {
diffServClfrElementNextFree,
diffServClfrElementPrecedence, diffServClfrElementNext,
diffServClfrElementSpecific, diffServClfrElementStorage,
diffServClfrElementStatus
}
STATUS current
DESCRIPTION
"The Classifier Element Group defines the MIB Objects that
describe the classifier elements that make up a generic
classifier."
::= { diffServMIBGroups 3 }
diffServMIBMultiFieldClfrGroup OBJECT-GROUP
OBJECTS {
diffServMultiFieldClfrNextFree,
diffServMultiFieldClfrAddrType,
diffServMultiFieldClfrDstAddr,
diffServMultiFieldClfrDstPrefixLength,
diffServMultiFieldClfrFlowId,
diffServMultiFieldClfrSrcAddr,
diffServMultiFieldClfrSrcPrefixLength,
diffServMultiFieldClfrDscp,
diffServMultiFieldClfrProtocol,
diffServMultiFieldClfrDstL4PortMin,
diffServMultiFieldClfrDstL4PortMax,
diffServMultiFieldClfrSrcL4PortMin,
diffServMultiFieldClfrSrcL4PortMax,
diffServMultiFieldClfrStorage,
diffServMultiFieldClfrStatus
}
STATUS current
DESCRIPTION
"The Multi-field Classifier Group defines the MIB Objects that
describe a classifier element for matching on various fields of
an IP and upper-layer protocol header."
::= { diffServMIBGroups 4 }
diffServMIBMultiFieldClfrGroup OBJECT-GROUP
OBJECTS {
diffServMultiFieldClfrNextFree,
diffServMultiFieldClfrAddrType,
diffServMultiFieldClfrDstAddr,
diffServMultiFieldClfrDstPrefixLength,
diffServMultiFieldClfrFlowId,
diffServMultiFieldClfrSrcAddr,
diffServMultiFieldClfrSrcPrefixLength,
diffServMultiFieldClfrDscp,
diffServMultiFieldClfrProtocol,
diffServMultiFieldClfrDstL4PortMin,
diffServMultiFieldClfrDstL4PortMax,
diffServMultiFieldClfrSrcL4PortMin,
diffServMultiFieldClfrSrcL4PortMax,
diffServMultiFieldClfrStorage,
diffServMultiFieldClfrStatus
}
STATUS current
DESCRIPTION
"The Multi-field Classifier Group defines the MIB Objects that
describe a classifier element for matching on various fields of
an IP and upper-layer protocol header."
::= { diffServMIBGroups 4 }
diffServMIBMeterGroup OBJECT-GROUP
OBJECTS {
diffServMeterNextFree, diffServMeterSucceedNext,
diffServMeterFailNext, diffServMeterSpecific,
diffServMeterStorage, diffServMeterStatus
}
diffServMIBMeterGroup OBJECT-GROUP
OBJECTS {
diffServMeterNextFree, diffServMeterSucceedNext,
diffServMeterFailNext, diffServMeterSpecific,
diffServMeterStorage, diffServMeterStatus
}
STATUS current
DESCRIPTION
"The Meter Group defines the objects used in describing a generic
meter element."
::= { diffServMIBGroups 5 }
STATUS current
DESCRIPTION
"The Meter Group defines the objects used in describing a generic
meter element."
::= { diffServMIBGroups 5 }
diffServMIBTBParamGroup OBJECT-GROUP
OBJECTS {
diffServTBParamNextFree, diffServTBParamType,
diffServTBParamRate, diffServTBParamBurstSize,
diffServTBParamInterval, diffServTBParamStorage,
diffServTBParamStatus
}
STATUS current
DESCRIPTION
"The Token-Bucket Meter Group defines the objects used in
describing a token bucket meter element."
::= { diffServMIBGroups 6 }
diffServMIBTBParamGroup OBJECT-GROUP
OBJECTS {
diffServTBParamNextFree, diffServTBParamType,
diffServTBParamRate, diffServTBParamBurstSize,
diffServTBParamInterval, diffServTBParamStorage,
diffServTBParamStatus
}
STATUS current
DESCRIPTION
"The Token-Bucket Meter Group defines the objects used in
describing a token bucket meter element."
::= { diffServMIBGroups 6 }
diffServMIBActionGroup OBJECT-GROUP
OBJECTS {
diffServActionNextFree, diffServActionNext,
diffServActionSpecific, diffServActionStorage,
diffServActionInterface, diffServActionStatus
}
STATUS current
DESCRIPTION
"The Action Group defines the objects used in describing a
generic action element."
::= { diffServMIBGroups 7 }
diffServMIBActionGroup OBJECT-GROUP
OBJECTS {
diffServActionNextFree, diffServActionNext,
diffServActionSpecific, diffServActionStorage,
diffServActionInterface, diffServActionStatus
}
STATUS current
DESCRIPTION
"The Action Group defines the objects used in describing a
generic action element."
::= { diffServMIBGroups 7 }
diffServMIBDscpMarkActGroup OBJECT-GROUP
OBJECTS {
diffServDscpMarkActDscp
}
STATUS current
DESCRIPTION
"The DSCP Mark Action Group defines the objects used in
describing a DSCP Marking Action element."
::= { diffServMIBGroups 8 }
diffServMIBDscpMarkActGroup OBJECT-GROUP
OBJECTS {
diffServDscpMarkActDscp
}
STATUS current
DESCRIPTION
"The DSCP Mark Action Group defines the objects used in
describing a DSCP Marking Action element."
::= { diffServMIBGroups 8 }
diffServMIBCounterGroup OBJECT-GROUP OBJECTS { diffServCountActOctets, diffServCountActPkts, diffServAlgDropOctets, diffServAlgDropPkts, diffServAlgRandomDropOctets, diffServAlgRandomDropPkts, diffServCountActStorage, diffServCountActStatus, diffServCountActNextFree
diffServMIBCounterGroup对象组对象{DiffServCountActets，diffServCountActPkts，diffServAlgDropOctets，DiffServGrandomDropOctets，DiffServGrandomDropPKTs，diffServCountActStorage，diffServCountActStatus，diffServCountActNextFree
}
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
packet-oriented network interfaces."
::= { diffServMIBGroups 9 }
}
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
packet-oriented network interfaces."
::= { diffServMIBGroups 9 }
diffServMIBAlgDropGroup OBJECT-GROUP
OBJECTS {
diffServAlgDropNextFree, diffServAlgDropType,
diffServAlgDropNext, diffServAlgDropQMeasure,
diffServAlgDropQThreshold, diffServAlgDropSpecific,
diffServAlgDropStorage, diffServAlgDropStatus
}
STATUS current
DESCRIPTION
"The Algorithmic Drop Group contains the objects that describe
algorithmic dropper operation and configuration."
::= { diffServMIBGroups 10 }
diffServMIBAlgDropGroup OBJECT-GROUP
OBJECTS {
diffServAlgDropNextFree, diffServAlgDropType,
diffServAlgDropNext, diffServAlgDropQMeasure,
diffServAlgDropQThreshold, diffServAlgDropSpecific,
diffServAlgDropStorage, diffServAlgDropStatus
}
STATUS current
DESCRIPTION
"The Algorithmic Drop Group contains the objects that describe
algorithmic dropper operation and configuration."
::= { diffServMIBGroups 10 }
diffServMIBRandomDropGroup OBJECT-GROUP
OBJECTS {
diffServRandomDropNextFree,
diffServRandomDropMinThreshBytes,
diffServRandomDropMinThreshPkts,
diffServRandomDropMaxThreshBytes,
diffServRandomDropMaxThreshPkts,
diffServRandomDropProbMax,
diffServRandomDropWeight,
diffServRandomDropSamplingRate,
diffServRandomDropStorage,
diffServRandomDropStatus
}
STATUS current
DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group for
random dropper operation and configuration."
::= { diffServMIBGroups 11 }
diffServMIBRandomDropGroup OBJECT-GROUP
OBJECTS {
diffServRandomDropNextFree,
diffServRandomDropMinThreshBytes,
diffServRandomDropMinThreshPkts,
diffServRandomDropMaxThreshBytes,
diffServRandomDropMaxThreshPkts,
diffServRandomDropProbMax,
diffServRandomDropWeight,
diffServRandomDropSamplingRate,
diffServRandomDropStorage,
diffServRandomDropStatus
}
STATUS current
DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group for
random dropper operation and configuration."
::= { diffServMIBGroups 11 }
diffServMIBQGroup OBJECT-GROUP
diffServMIBQGroup对象组
OBJECTS {
diffServQNextFree, diffServQNext, diffServQMinRate,
diffServQMaxRate, diffServQStorage, diffServQStatus
}
STATUS current
DESCRIPTION
"The Queue Group contains the objects that describe an
OBJECTS {
diffServQNextFree, diffServQNext, diffServQMinRate,
diffServQMaxRate, diffServQStorage, diffServQStatus
}
STATUS current
DESCRIPTION
"The Queue Group contains the objects that describe an
interface's queues."
::= { diffServMIBGroups 12 }
interface's queues."
::= { diffServMIBGroups 12 }
diffServMIBSchedulerGroup OBJECT-GROUP
OBJECTS {
diffServSchedulerNextFree, diffServSchedulerNext,
diffServSchedulerMethod, diffServSchedulerMinRate,
diffServSchedulerMaxRate, diffServSchedulerStorage,
diffServSchedulerStatus
}
STATUS current
DESCRIPTION
"The Scheduler Group contains the objects that describe packet
schedulers on interfaces."
::= { diffServMIBGroups 13 }
diffServMIBSchedulerGroup OBJECT-GROUP
OBJECTS {
diffServSchedulerNextFree, diffServSchedulerNext,
diffServSchedulerMethod, diffServSchedulerMinRate,
diffServSchedulerMaxRate, diffServSchedulerStorage,
diffServSchedulerStatus
}
STATUS current
DESCRIPTION
"The Scheduler Group contains the objects that describe packet
schedulers on interfaces."
::= { diffServMIBGroups 13 }
diffServMIBMinRateGroup OBJECT-GROUP
OBJECTS {
diffServMinRateNextFree, diffServMinRatePriority,
diffServMinRateAbsolute, diffServMinRateRelative,
diffServMinRateStorage, diffServMinRateStatus
}
STATUS current
DESCRIPTION
"The Minimum Rate Parameter Group contains the objects that
describe packet schedulers' minimum rate or priority guarantees."
::= { diffServMIBGroups 14 }
diffServMIBMinRateGroup OBJECT-GROUP
OBJECTS {
diffServMinRateNextFree, diffServMinRatePriority,
diffServMinRateAbsolute, diffServMinRateRelative,
diffServMinRateStorage, diffServMinRateStatus
}
STATUS current
DESCRIPTION
"The Minimum Rate Parameter Group contains the objects that
describe packet schedulers' minimum rate or priority guarantees."
::= { diffServMIBGroups 14 }
diffServMIBMaxRateGroup OBJECT-GROUP
OBJECTS {
diffServMaxRateNextFree, diffServMaxRateAbsolute,
diffServMaxRateRelative, diffServMaxRateThreshold,
diffServMaxRateStorage, diffServMaxRateStatus
}
STATUS current
DESCRIPTION
"The Maximum Rate Parameter Group contains the objects that
describe packet schedulers' maximum rate guarantees."
::= { diffServMIBGroups 15 }
diffServMIBMaxRateGroup OBJECT-GROUP
OBJECTS {
diffServMaxRateNextFree, diffServMaxRateAbsolute,
diffServMaxRateRelative, diffServMaxRateThreshold,
diffServMaxRateStorage, diffServMaxRateStatus
}
STATUS current
DESCRIPTION
"The Maximum Rate Parameter Group contains the objects that
describe packet schedulers' maximum rate guarantees."
::= { diffServMIBGroups 15 }
END
终止
This MIB builds on all the work that has gone into the Informal Management Model for Differentiated Services Routers, Differentiated Services PIB, and Differentiated Services Policy MIB (SNMPCONF WG).
此MIB建立在区分服务路由器、区分服务PIB和区分服务策略MIB（SNMPCONF WG）的非正式管理模型中的所有工作的基础上。
It has been developed with the active involvement of many people, but most notably Yoram Bernet, Steve Blake, Brian Carpenter, Dave Durham, Michael Fine, Victor Firoiu, Jeremy Greene, Dan Grossman, Roch Guerin, Scott Hahn, Joel Halpern, Van Jacobsen, Keith McCloghrie, Bob Moore, Kathleen Nichols, Ping Pan, Nabil Seddigh, John Seligson, and Walter Weiss.
它是在许多人的积极参与下开发的，但最著名的是约拉姆·伯内特、史蒂夫·布莱克、布赖恩·卡彭特、戴夫·达勒姆、迈克尔·费恩、维克多·菲罗、杰里米·格林、丹·格罗斯曼、罗奇·盖林、斯科特·哈恩、乔尔·哈尔伯恩、范·雅各布森、基思·麦克洛格里、鲍勃·摩尔、凯瑟琳·尼科尔斯、潘平、纳比尔·塞迪格、约翰·塞利格森、，还有沃尔特·韦斯。
Juergen Schoenwaelder, Dave Perkins, Frank Strauss, Harrie Hazewinkel, and Bert Wijnen are especially to be noted for review comments on the structure and usage of the MIB for network management purposes, and its compliance with SMIv2.
Juergen Schoenwaeld、Dave Perkins、Frank Strauss、Harrie Hazewinkel和Bert Wijnen特别值得一提的是，他们对用于网络管理的MIB的结构和使用以及其与SMIv2的合规性提出了审查意见。
It is clear that this MIB is potentially useful for configuration. Anything that can be configured can be misconfigured, with potentially disastrous effects.
很明显，此MIB对于配置可能很有用。任何可以配置的东西都可能被错误配置，从而带来潜在的灾难性后果。
At this writing, no security holes have been identified beyond those that SNMP Security is itself intended to address. These relate primarily to controlled access to sensitive information and the ability to configure a device - or which might result from operator error, which is beyond the scope of any security architecture.
在撰写本文时，除了SNMP安全性本身打算解决的安全漏洞之外，还没有发现任何其他安全漏洞。这些主要涉及对敏感信息的受控访问和配置设备的能力，或者可能由操作员错误导致的，这超出了任何安全体系结构的范围。
There are many read-write and read-create management objects defined in this MIB. Such objects are often 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. The use of SNMP Version 3 is recommended over prior versions for configuration control as its security model is improved.
此MIB中定义了许多读写和读创建管理对象。在某些网络环境中，此类对象通常是敏感的或易受攻击的。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。与以前的版本相比，建议使用SNMP版本3进行配置控制，因为其安全模型得到了改进。
There are a number of managed objects in this MIB that may contain information that may be sensitive from a business perspective, in that they may represent a customer's service contract or the filters that the service provider chooses to apply to a customer's ingress or egress traffic. There are no objects which are sensitive in their own right, such as passwords or monetary amounts.
此MIB中有许多托管对象可能包含从业务角度看可能敏感的信息，因为它们可能表示客户的服务合同或服务提供商选择应用于客户进出流量的过滤器。没有任何对象本身是敏感的，例如密码或货币金额。
It may be important to even control GET access to these objects and possibly to even encrypt the values of these objects 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] and the View-based Access Control Model [RFC 2575] is recommended.
建议执行者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型[RFC 2574]和基于视图的访问控制模型[RFC 2575]。
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实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
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执行董事。
[RFC 2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC 2571]Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[RFC 1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC 1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC 1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC 1212]Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC 1215] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[RFC 1215]Rose，M.，“定义用于SNMP的陷阱的约定”，RFC 1215，1991年3月。
[RFC 2578] 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.
[RFC 2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC 2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC 2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC 2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC 2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC 1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC 1157]Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[RFC 1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[RFC 1901]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 1901，1996年1月。
[RFC 1906] 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.
[RFC 1906]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[RFC 2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC 2572]Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[RFC 2574] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC 2574]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[RFC 1905] 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.
[RFC 1905]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[RFC 2573] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[RFC 2573]Levi，D.，Meyer，P.和B.Stewart，“SNMP应用”，RFC 2573，1999年4月。
[RFC 2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC 2575]Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1999年4月。
[RFC 2570] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[RFC 2570]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 2570，1999年4月。
[RFC 2119] Bradner, S., "Key words to use in the RFCs", BCP 14, RFC 2119, March 1997.
[RFC 2119]Bradner，S.，“在RFC中使用的关键词”，BCP 14，RFC 2119，1997年3月。
[ACTQMGMT] V. Firoiu, M. Borden, "A Study of Active Queue
Management for Congestion Control", March 2000, In IEEE
Infocom 2000, http://www.ieee-
infocom.org/2000/papers/405.pdf
[ACTQMGMT] V. Firoiu, M. Borden, "A Study of Active Queue
Management for Congestion Control", March 2000, In IEEE
Infocom 2000, http://www.ieee-
infocom.org/2000/papers/405.pdf
[AQMROUTER] V. Misra, W. Gong, D. Towsley, "Fluid-based analysis of
a network of AQM routers supporting TCP flows with an
application to RED", In SIGCOMM
2000,http://www.acm.org/sigcomm/sigcomm2000/conf/
paper/sigcomm2000-4-3.ps.gz
[AQMROUTER] V. Misra, W. Gong, D. Towsley, "Fluid-based analysis of
a network of AQM routers supporting TCP flows with an
application to RED", In SIGCOMM
2000,http://www.acm.org/sigcomm/sigcomm2000/conf/
paper/sigcomm2000-4-3.ps.gz
[AF-PHB] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski, "Assured Forwarding PHB Group", RFC 2597, June 1999.
[AF-PHB]Heinanen，J.，Baker，F.，Weiss，W.和J.Wroclawski，“保付PHB集团”，RFC 25971999年6月。
[DSARCH] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z. and W. Weiss, "An Architecture for Differentiated Service", RFC 2475, December 1998.
[DSARCH]Blake，S.，Black，D.，Carlson，M.，Davies，E.，Wang，Z.和W.Weiss，“差异化服务架构”，RFC 24751998年12月。
[DSFIELD] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[DSFIELD]Nichols，K.，Blake，S.，Baker，F.和D.Black，“IPv4和IPv6报头中区分服务字段（DS字段）的定义”，RFC 24741998年12月。
[DSPIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., Hahn, S. and A. Smith, "Differentiated Services Quality of Service Policy Information Base", Work in Progress.
[DSPIB]Fine，M.，McCloghrie，K.，Seligson，J.，Chan，K.，Hahn，S.和A.Smith，“差异化服务质量服务政策信息库”，正在进行中。
[DSTERMS] Grossman, D., "New Terminology for Differentiated Services", RFC 3260, April 2002.
[Dterms]Grossman，D.，“差异化服务的新术语”，RFC 3260，2002年4月。
[EF-PHB] Jacobson, V., Nichols, K. and K. Poduri, "An Expedited Forwarding PHB", RFC 3246, March 2002.
[EF-PHB]Jacobson，V.，Nichols，K.和K.Poduri，“快速转发PHB”，RFC 32462002年3月。
[IF-MIB] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000.
[IF-MIB]McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 28632000年6月。
[INETADDRESS] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses.", RFC 3291, May 2002.
[INETADDRESS]Daniele，M.，Haberman，B.，Routhier，S.和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 3291，2002年5月。
[INTSERVMIB] Baker, F., Krawczyk, J. and A. Sastry, "Integrated Services Management Information Base using SMIv2", RFC 2213, September 1997.
[INTSERVMIB]Baker，F.，Krawczyk，J.和A.Sastry，“使用SMIv2的集成服务管理信息库”，RFC 2213，1997年9月。
[MODEL] Bernet, Y., Blake, S., Smith, A. and D. Grossman, "An Informal Management Model for Differentiated Services Routers", Work in Progress.
[模型]Bernet，Y.，Blake，S.，Smith，A.和D.Grossman，“区分服务路由器的非正式管理模型”，正在进行中。
[RED93] "Random Early Detection", 1993.
[RED93]“随机早期检测”，1993年。
[srTCM] Heinanen, J. and R. Guerin, "A Single Rate Three Color Marker", RFC 2697, September 1999.
[srTCM]Heinanen，J.和R.Guerin，“单速率三色标记”，RFC 26971999年9月。
[trTCM] Heinanen, J. and R. Guerin, "A Two Rate Three Color Marker", RFC 2698, September 1999.
[trTCM]Heinanen，J.和R.Guerin，“双速率三色标记”，RFC 26981999年9月。
[TSWTCM] Fang, W., Seddigh, N. and B. Nandy, "A Time Sliding Window Three Color Marker (TSWTCM)", RFC 2859, June 2000.
[TSWTCM]Fang，W.，Seddigh，N.和B.Nandy，“时间滑动窗口三色标记（TSWTCM）”，RFC 28592000年6月。
[SHAPER] Bonaventure, O. and S. De Cnodder, "A Rate Adaptive Shaper for Differentiated Services", RFC 2963, October 2000.
[SHAPER]Bonaventure，O.和S.De Cnodder，“差异化服务的速率自适应成形器”，RFC 2963，2000年10月。
Fred Baker Cisco Systems 1121 Via Del Rey Santa Barbara, California 93117
Fred Baker Cisco Systems 1121 Via Del Rey Santa Barbara，加利福尼亚93117
EMail: fred@cisco.com
EMail: fred@cisco.com
Kwok Ho Chan Nortel Networks 600 Technology Park Drive Billerica, MA 01821
郭浩灿北电网络600科技园路马州比利里卡01821
EMail: khchan@nortelnetworks.com
EMail: khchan@nortelnetworks.com
Andrew Smith Harbour Networks Jiuling Building 21 North Xisanhuan Ave. Beijing, 100089, PRC
中国北京西三环北路21号安德鲁·史密斯港湾网络九陵大厦，100089
EMail: ah_smith@acm.org
EMail: ah_smith@acm.org
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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编辑功能的资金目前由互联网协会提供。