draft-ietf-diffserv-mib-07.txt   draft-ietf-diffserv-mib-08.txt 
Internet Engineering Task Force F. Baker | Internet Engineering Task Force F. Baker
Diffserv Working Group Cisco Systems Diffserv Working Group Cisco Systems
INTERNET-DRAFT K. Chan INTERNET-DRAFT K. Chan
Expires August 2001 Nortel Networks | Expires August 2001 Nortel Networks
draft-ietf-diffserv-mib-07.txt A. Smith | draft-ietf-diffserv-mib-08.txt A. Smith
Allegro Networks Allegro Networks
February 2001 | February 2001
Management Information Base for the Management Information Base for the
Differentiated Services Architecture Differentiated Services Architecture
Status of this Memo | Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet Drafts as reference material time. It is inappropriate to use Internet Drafts as reference material
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Group. Comments should be addressed to WG's mailing list at Group. Comments should be addressed to WG's mailing list at
diffserv@ietf.org. The charter for Differentiated Services may be found diffserv@ietf.org. The charter for Differentiated Services may be found
at http://www.ietf.org/html.charters/diffserv-charter.html at http://www.ietf.org/html.charters/diffserv-charter.html
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
Abstract Abstract
This memo describes a SMIv2 MIB for a device implementing the This memo describes a SMIv2 MIB for a device implementing the
Differentiated Services Architecture [DSARCH], described in detail by | Differentiated Services Architecture [DSARCH], described in detail by
the Informal Management Model for Diffserv Routers [MODEL]. the Informal Management Model for Diffserv Routers [MODEL].
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
skipping to change at page 3, line 4 skipping to change at page 2, line 50
Management Information Base or MIB. Objects in the MIB are defined using Management Information Base or MIB. Objects in the MIB are defined using
the mechanisms defined in the SMI. the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Introduction | 2. Introduction
2.1. Relationship to the Informal Management Model for Diffserv | 2.1. Relationship to the Informal Management Model for Diffserv
Router Router
This MIB is designed according to [MODEL]. The model describes the way | This MIB is designed according to [MODEL]. The model describes the way
that ingress and egress interfaces of an 'n'-port router are modeled. It | that ingress and egress interfaces of an 'n'-port router are modeled. It
describes the configuration and management of a Diffserv interface in | describes the configuration and management of a Diffserv interface in
terms of one or more Traffic Conditioning Block (TCB), each containing, | terms of one or more Traffic Conditioning Block (TCB), each containing,
arranged in the specified order, by definition, zero or more | arranged in the specified order, by definition, zero or more
classifiers, meters, actions, algorithmic droppers, queues and | classifiers, meters, actions, algorithmic droppers, queues and
schedulers. Traffic may be classified; classified traffic may be | schedulers. Traffic may be classified; classified traffic may be
metered; each stream of traffic identified by a combination of metered; each stream of traffic identified by a combination of
classifiers and meters may have some set of actions performed on it; it classifiers and meters may have some set of actions performed on it; it
may have dropping algorithms applied and it may ultimately be stored may have dropping algorithms applied and it may ultimately be stored
into a queue before being scheduled out to its next destination, either into a queue before being scheduled out to its next destination, either
onto a link or to another TCB. When the treatment for a given packet onto a link or to another TCB. When the treatment for a given packet
must have any of those elements repeated in a way that breaks the must have any of those elements repeated in a way that breaks the
permitted sequence {classifier, meter, action, algorithmic dropper, permitted sequence {classifier, meter, action, algorithmic dropper,
queue, scheduler}, this must be modeled by cascading multiple TCBs. | queue, scheduler}, this must be modeled by cascading multiple TCBs.
The MIB represents this cascade by following the "Next" attributes of The MIB represents this cascade by following the "Next" attributes of
the various elements. They indicate what the next step in Diffserv the various elements. They indicate what the next step in Diffserv
processing will be, whether it be a classifier, meter, action, processing will be, whether it be a classifier, meter, action,
algorithmic dropper, queue, scheduler or a decision to now forward a algorithmic dropper, queue, scheduler or a decision to now forward a
packet. packet.
The MIB models the individual elements that make up the TCBs. The The MIB models the individual elements that make up the TCBs. The
higher level concept of a TCB is not required in the parameterization or 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 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 | in the MIB itself and is only mentioned in the text for relating the MIB
with the [MODEL]. The actual distinguishing of which TCB a specific with the [MODEL]. The actual distinguishing of which TCB a specific
element is a part of is not needed for the instrumentation of a device | element is a part of is not needed for the instrumentation of a device
to support the functionality of Diffserv, but it is useful for | to support the functionality of Diffserv, but it is useful for
conceptual reasons. By not using the TCB concept, this MIB allows any | conceptual reasons. By not using the TCB concept, this MIB allows any
grouping of elements to construct TCBs using the rules defined by | grouping of elements to construct TCBs using the rules defined by
[MODEL]: that document should be consulted for the allowed combinations | [MODEL]: that document should be consulted for the allowed combinations
of elements that make up a TCB. This will minimize changes to this MIB of elements that make up a TCB. This will minimize changes to this MIB
if rules in [MODEL] changes. if rules in [MODEL] changes.
The notion of a Data Path is used in this MIB to indicate the Diffserv | The notion of a Data Path is used in this MIB to indicate the Diffserv
processing a packet may experience. This Data Path is distinguished | processing a packet may experience. This Data Path is distinguished
based on the Interface and the Direction of the flow the packet is part | based on the Interface and the Direction of the flow the packet is part
of. A Data Path Table Entry indicates the first of possibly multiple | of. A Data Path Table Entry indicates the first of possibly multiple
elements that will apply Diffserv treatment to the packet. elements that will apply Diffserv treatment to the packet.
2.2. Relationship to other MIBs and Policy Management 2.2. Relationship to other MIBs and Policy Management
This MIB provides for direct reporting and manipulation of the most This MIB provides for direct reporting and manipulation of the most
detailed functional elements described by [MODEL]. These elements are | detailed functional elements described by [MODEL]. These elements are
designed with their parameterization tables separated from their data designed with their parameterization tables separated from their data
path linkage tables, allowing reuse of each table as much as possible. | path linkage tables, allowing reuse of each table as much as possible.
The data path linkage in this MIB is coupled with an interface through | The data path linkage in this MIB is coupled with an interface through
the use of the diffServDataPathTable. The concept of "interface" is as | the use of the diffServDataPathTable. The concept of "interface" is as
defined by InterfaceIndex/ifIndex of the IETF Interfaces MIB [IFMIB]. defined by InterfaceIndex/ifIndex of the IETF Interfaces MIB [IFMIB].
Other MIBs and data structure definitions for policy management Other MIBs and data structure definitions for policy management
mechanisms other than SNMP/SMIv2 are likely to exist in the future for mechanisms other than SNMP/SMIv2 are likely to exist in the future for
the purposes of abstracting the model in other ways. the purposes of abstracting the model in other ways.
In particular, abstractions in the direction of less detailed In particular, abstractions in the direction of less detailed
definitions of Diffserv functionality are likely e.g. some form of | definitions of Diffserv functionality are likely e.g. some form of
"Per-Hop Behavior"-based definition involving a template of detailed "Per-Hop Behavior"-based definition involving a template of detailed
object values which is applied to specific instances of objects in this object values which is applied to specific instances of objects in this
MIB semi-automatically. MIB semi-automatically.
Another possible direction of abstraction is one using a concept of Another possible direction of abstraction is one using a concept of
"roles" (often, but not always, applied to interfaces). In this case, it "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 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 the parameterization tables. The Data Path table will help in the reuse
of the data path linkage tables by having the interface specific of the data path linkage tables by having the interface specific
information centralized, allowing easier mechanical replacement of information centralized, allowing easier mechanical replacement of
ifIndex by some sort of "roleIndex". Work is ongoing in this area. ifIndex by some sort of "roleIndex". Work is ongoing in this area.
2.3. MIB Overview 2.3. MIB Overview
This MIB is structured based on the need to describe the sequential | This MIB is structured based on the need to describe the sequential
Diffserv treatments being applied to a packet, and the parameterization Diffserv treatments being applied to a packet, and the parameterization
of these treatments. These two requirements are kept separate | of these treatments. These two requirements are kept separate
throughout the design of this MIB, and are fulfilled using separate | throughout the design of this MIB, and are fulfilled using separate
tables and data definitions. tables and data definitions.
In this MIB, we model the ingress and egress portions of a Diffserv | In this MIB, we model the ingress and egress portions of a Diffserv
network device identically, making the distinction between them an index network device identically, making the distinction between them an index
variable. Each interface then performs some or all of the following variable. Each interface then performs some or all of the following
high-level functions: high-level functions:
o Classify each packet according to some set of rules o Classify each packet according to some set of rules
o Determine whether the packet's data stream is conforming or not o Determine whether the packet's data stream is conforming or not
conforming to its permitted rates conforming to its permitted rates
o Perform a set of resulting actions, possibly including counting the o Perform a set of resulting actions, possibly including counting the
skipping to change at page 6, line 17 skipping to change at page 5, line 17
the traffic with a Differentiated Services Code Point (DSCP) as the traffic with a Differentiated Services Code Point (DSCP) as
defined in [DSFIELD]. defined in [DSFIELD].
o Enqueue the traffic for output in the appropriate queue, whose o Enqueue the traffic for output in the appropriate queue, whose
scheduler may shape the traffic or simply forward it with some scheduler may shape the traffic or simply forward it with some
minimum rate or maximum latency. minimum rate or maximum latency.
The MIB therefore contains the following elements: The MIB therefore contains the following elements:
Data Path Table Data Path Table
This is the starting point of Diffserv data paths within a single | This is the starting point of Diffserv data paths within a single
Diffserv device. Data paths defined by this table are interface Diffserv device. Data paths defined by this table are interface
and interface direction specific. and interface direction specific.
Classifier and Filter Tables Classifier and Filter Tables
A general extensible framework and one example of a filter table | A general extensible framework and one example of a filter table
(an IP Six-Tuple Multi-Field Classification Table). (an IP Six-Tuple Multi-Field Classification Table).
Meter Tables Meter Tables
A general extensible framework and one example of a A general extensible framework and one example of a
parameterization table - TBMeter table, applicable for Simple Token parameterization table - TBMeter table, applicable for Simple Token
Bucket Meter, Average Rate Meter, Single Rate Three Color Meter, Bucket Meter, Average Rate Meter, Single Rate Three Color Meter,
Two Rate Three Color Meter, and Sliding Window Three Color Meter. Two Rate Three Color Meter, and Sliding Window Three Color Meter.
Action Tables Action Tables
A general extensible framework and examples of parameterization A general extensible framework and examples of parameterization
tables for Absolute Drop, Mark and Count actions. The | tables for Absolute Drop, Mark and Count actions. The
"multiplexer" and "null" actions described in [MODEL] are "multiplexer" and "null" actions described in [MODEL] are
accomplished implicitly by means of the RowPointer structures of accomplished implicitly by means of the RowPointer structures of
the other elements. the other elements.
Queue, Scheduler and Algorithmic Dropper Tables Queue, Scheduler and Algorithmic Dropper Tables
A general extensible framework for parameterizing queuing and A general extensible framework for parameterizing queuing and
scheduler systems. The queue measurement dependent algorithmic scheduler systems. The queue measurement dependent algorithmic
droppers are also described here. droppers are also described here.
3. Structure of this MIB 3. Structure of this MIB
This MIB is structured with separate tables for purpose of Diffserv data | This MIB is structured with separate tables for purpose of Diffserv data
path description and Diffserv treatment parameterization of the Diffserv | path description and Diffserv treatment parameterization of the Diffserv
device. The data path description and/or the treatment parameterization | device. The data path description and/or the treatment parameterization
tables can each be reused independently, allowing the flexibility to | tables can each be reused independently, allowing the flexibility to
maintain a common data construct for Diffserv device configuration and | maintain a common data construct for Diffserv device configuration and
provisioning, independent of the configuration method used. The | provisioning, independent of the configuration method used. The
definitions in this MIB are intended to be reusable by other future | definitions in this MIB are intended to be reusable by other future
standards. The treatment parameters can also be reused by other IP standards. The treatment parameters can also be reused by other IP
based technologies. For example, IP packet filtering parameters most | based technologies. For example, IP packet filtering parameters most
likely can be reused by other IP based technologies that rely on packet | likely can be reused by other IP based technologies that rely on packet
classification. | classification.
3.1. Diffserv Data Paths 3.1. Diffserv Data Paths
This part of the MIB provides instrumentation for connecting the | This part of the MIB provides instrumentation for connecting the
Diffserv Functional Data path Elements within a single Diffserv device. | Diffserv Functional Data path Elements within a single Diffserv device.
Please refer to the [MODEL] for discussions on the valid sequencing and | Please refer to the [MODEL] for discussions on the valid sequencing and
grouping of Diffserv Functional Data path Elements. Given some basic grouping of Diffserv Functional Data path Elements. Given some basic
information, e.g. ifIndex and interface direction, the first Diffserv | information, e.g. ifIndex and interface direction, the first Diffserv
Functional Data path Element applied to a given packet on a given | Functional Data path Element applied to a given packet on a given
interface is determined. Subsequent Diffserv Functional Elements are interface is determined. Subsequent Diffserv Functional Elements are
provided by the "Next" pointer attribute of each entry of data path provided by the "Next" pointer attribute of each entry of data path
tables. Description of how this "Next" pointer is used in each table is tables. Description of how this "Next" pointer is used in each table is
provided in their respective DESCRIPTION clause. * provided in their respective DESCRIPTION clause.
3.1.1. Data Path Table 3.1.1. Data Path Table
Entries in the Data Path Table provide the Diffserv treatment starting | Entries in the Data Path Table provide the Diffserv treatment starting
points for all packets of Diffserv interfaces on this device. Not all | points for all packets of Diffserv interfaces on this device. Not all
interfaces on this device need to be Diffserv interfaces, hence not all | interfaces on this device need to be Diffserv interfaces, hence not all
entries in the ifTable need to have corresponding entries in the Data entries in the ifTable need to have corresponding entries in the Data
Path Table. Each entry in this table is indexed by ifIndex and the Path Table. Each entry in this table is indexed by ifIndex and the
direction of the packet flow. There should be at most two entries for direction of the packet flow. There should be at most two entries for
each interface, one for ingress and one for egress. Each entry provides | each interface, one for ingress and one for egress. Each entry provides
the first Diffserv Functional Data path Element each packet at a | the first Diffserv Functional Data path Element each packet at a
specific interface traveling a specific relative direction should specific interface traveling a specific relative direction should
experience. NOTE: this table is interface specific, with the use of | experience. NOTE: this table is interface specific, with the use of
ifIndex. Entries may be created with zeroDotZero in the ifIndex. Entries may be created with zeroDotZero in the
diffServDataPathStart attribute to indicate that there are no further | diffServDataPathStart attribute to indicate that there are no further
diffserv elements in that data path. For example, a classifier that | diffserv elements in that data path. For example, a classifier that
should never match anything but is present to debug or detect traffic | should never match anything but is present to debug or detect traffic
might use this, although one could argue that it should transit to a | might use this, although one could argue that it should transit to a
dropper. The non-existence of any Diffserv treatment on an | dropper. The non-existence of any Diffserv treatment on an
interface/direction is indicated implicitly by having no corresponding | interface/direction is indicated implicitly by having no corresponding
entry in this table. This means allowing normal IP device processing | entry in this table. This means allowing normal IP device processing
when zeroDotZero is used in the diffServDataPathStart attribute, or when when zeroDotZero is used in the diffServDataPathStart attribute, or when
the entry does not exist. Normal IP device processing will depend on the entry does not exist. Normal IP device processing will depend on
the device, for example, this can be forwarding the packet. the device, for example, this can be forwarding the packet.
3.2. Classifiers 3.2. Classifiers
The classifier, classifier element, and filter tables determine how The classifier, classifier element, and filter tables determine how
traffic is sorted out. They identify separable classes of traffic, by traffic is sorted out. They identify separable classes of traffic, by
reference to an appropriate filter, which may select anything from an reference to an appropriate filter, which may select anything from an
individual micro-flow to aggregates identified by DSCP. individual micro-flow to aggregates identified by DSCP.
The classification is used to send these separate streams to appropriate The classification is used to send these separate streams to appropriate
Meter, Action, Algorithmic Dropper, Queue, and Scheduler elements. For | Meter, Action, Algorithmic Dropper, Queue, and Scheduler elements. For
example, sub-classes of traffic may be sent to different meter stages: | example, sub-classes of traffic may be sent to different meter stages:
e.g. in an implementation of the Assured Forwarding (AF) PHB [AF-PHB], | e.g. in an implementation of the Assured Forwarding (AF) PHB [AF-PHB],
AF11 traffic might be sent to the first meter, AF12 traffic might be AF11 traffic might be sent to the first meter, AF12 traffic might be
sent to the second and AF13 traffic sent to the second meter stage's sent to the second and AF13 traffic sent to the second meter stage's
out-of-profile action. out-of-profile action.
The concept of a classifier is the same as described in [MODEL]. The The concept of a classifier is the same as described in [MODEL]. The
structure of the classifier and classifier element tables, is the same structure of the classifier and classifier element tables, is the same
as the classifier described in [MODEL]. Within each classifier, it must as the classifier described in [MODEL]. Within each classifier, it must
not be important in which order the filters are applied. This is to | not be important in which order the filters are applied. This is to
facilitate optimized implementations such as index trees. Precedence is | facilitate optimized implementations such as index trees. Precedence is
used only to resolve ambiguity, as described in [MODEL]. Filter with | used only to resolve ambiguity, as described in [MODEL]. Filter with
higher values of precedence are compared first; the order of tests for | higher values of precedence are compared first; the order of tests for
entries of the same precedence is unimportant. entries of the same precedence is unimportant.
A data path may consist of more than one classifier. There may be | A data path may consist of more than one classifier. There may be
overlap of filter specification between filters of different overlap of filter specification between filters of different
classifiers. The first classifier functional data path element | classifiers. The first classifier functional data path element
encountered, as determined by the sequencing of diffserv functional data | encountered, as determined by the sequencing of diffserv functional data
path elements, will be used first. path elements, will be used first.
An important form of classification is "everything else": the final An important form of classification is "everything else": the final
stage of the classifier i.e. the one with the lowest order, must be stage of the classifier i.e. the one with the lowest order, must be
"complete" since the result of an incomplete classifier is not "complete" since the result of an incomplete classifier is not
necessarily deterministic - see [MODEL] section 4.1.2. necessarily deterministic - see [MODEL] section 4.1.2.
The definition of the actual filter to be used by the classifier is The definition of the actual filter to be used by the classifier is
referenced via a StaticRowPointer: this enables the use of any sort of referenced via a RowPointer: this enables the use of any sort of filter
filter table that one might wish to design, standard or proprietary. The | table that one might wish to design, standard or proprietary. The filter
filter table may be, but does not need to be, defined in this MIB | table may be, but does not need to be, defined in this MIB module.
module.
Classifiers, used in various ingress and egress interfaces, are | Classifiers, used in various ingress and egress interfaces, are
organized by the classifier table. Each classifier will isolate a number | organized by the classifier table. Each classifier will isolate a number
of classes of traffic, identified by various kinds of filters. To | of classes of traffic, identified by various kinds of filters. To
enumerate this, we define the classifier table, the classifier element | enumerate this, we define the classifier table, the classifier element
table, and the filter table. A data path entry points to a classifier | table, and the filter table. A data path entry points to a classifier
entry. A classifier entry identifies a list of classifier elements. A | entry. A classifier entry identifies a list of classifier elements. A
classifier element effectively includes the filter entry, and points to | classifier element effectively includes the filter entry, and points to
a "next" classifier entry or other data path functional element. There | a "next" classifier entry or other data path functional element. There
are potentially many types of filters, only one of which is specified in | are potentially many types of filters, only one of which is specified in
this MIB Module. this MIB Module.
3.2.1. Classifier Table 3.2.1. Classifier Table
The classifier table, therefore, identifies the classifiers that are | The classifier table, therefore, identifies the classifiers that are
used in various interfaces. It organizes the list of classifier elements | used in various interfaces. It organizes the list of classifier elements
that identify the various classes. that identify the various classes.
3.2.2. Classifier Element Table 3.2.2. Classifier Element Table
Classifier elements point to the filters which identify various classes | Classifier elements point to the filters which identify various classes
of traffic. The separation between the "classifier element" and the | of traffic. The separation between the "classifier element" and the
"filter" allows us to use many different kinds of filters with the same | "filter" allows us to use many different kinds of filters with the same
essential semantics of "an identified set of traffic". The traffic | essential semantics of "an identified set of traffic". The traffic
matching the filter corresponding to a classifier element is given to | matching the filter corresponding to a classifier element is given to
the "next" data path functional element identified in the classifier | the "next" data path functional element identified in the classifier
element. element.
3.2.3. Filter Table - IP Six-Tuple Classifier Table 3.2.3. Filter Table - IP Six-Tuple Classifier Table
This MIB includes one Filter Table, a definition for an IP Six-Tuple This MIB includes one Filter Table, a definition for an IP Six-Tuple
Classifier, used for IP traffic classification. Entries in this filter Classifier, used for IP traffic classification. Entries in this filter
table are referenced from the StaticRowPointer table are referenced from the RowPointer diffServClfrElementSpecific
diffServClfrElementSpecific attributes of classifier element table attributes of classifier element table entries.
entries.
For example, a Behavior Aggregate (BA) Classifier, acting only on DSCPs, For example, a Behavior Aggregate (BA) Classifier, acting only on DSCPs,
is a simple form of the IP Six-Tuple Classifier. It is represented by is a simple form of the IP Six-Tuple Classifier. It is represented by
having the diffServSixTupleClfrDscp attribute set to the desired DSCP having the diffServSixTupleClfrDscp attribute set to the desired DSCP
and all other classification attributes set to match-all, their default and all other classification attributes set to match-all, their default
settings. settings.
Each entry in the IP Six-Tuple Classifier Table defines a single filter. Each entry in the IP Six-Tuple Classifier Table defines a single filter.
The textual convention of InetAddress [INETADDR] is used for both IPv4 The textual convention of InetAddress [INETADDR] is used for both IPv4
and IPv6 addressing. The use of IP Six-Tuple Classifiers is discussed and IPv6 addressing. The use of IP Six-Tuple Classifiers is discussed
skipping to change at page 9, line 50 skipping to change at page 8, line 49
3.3. Meters 3.3. Meters
A meter, according to [MODEL] section 5, measures the rate at which A meter, according to [MODEL] section 5, measures the rate at which
packets making up a stream of traffic pass it, compares this rate to packets making up a stream of traffic pass it, compares this rate to
some set of thresholds and produces some number (two or more) of some set of thresholds and produces some number (two or more) of
potential results. A given packet is said to "conform" to the meter if, potential results. A given packet is said to "conform" to the meter if,
at the time that the packet is being looked at, the stream appears to be at the time that the packet is being looked at, the stream appears to be
within the meter's profile. MIB syntax makes it easiest to define this within the meter's profile. MIB syntax makes it easiest to define this
as a sequence of one or more cascaded pass/fail tests, modeled here as as a sequence of one or more cascaded pass/fail tests, modeled here as
if-then-else constructs. It is important to understand that this way of | if-then-else constructs. It is important to understand that this way of
modeling does not imply anything about the implementation being
modeling does not imply anything about the implementation being |
"sequential": multi-rate/multi-profile meters e.g. those designed to "sequential": multi-rate/multi-profile meters e.g. those designed to
support [SRTCM], [TRTCM], or [TSWTCM] can still be modeled this way even | support [SRTCM], [TRTCM], or [TSWTCM] can still be modeled this way even
if they, of necessity, share information between the stages: the stages if they, of necessity, share information between the stages: the stages
are introduced merely as a notational convenience in order to simplify are introduced merely as a notational convenience in order to simplify
the MIB structure. the MIB structure.
3.3.1. Meter Table 3.3.1. Meter Table
The generic meter table is used as a base for all more specific forms of The generic meter table is used as a base for all more specific forms of
meter. The definition of parameters specific to the type of meter used meter. The definition of parameters specific to the type of meter used
is referenced via a pointer to a table containing those specifics. This is referenced via a pointer to a table containing those specifics. This
enables the use of any sort of specific meter table that one might wish enables the use of any sort of specific meter table that one might wish
to design, standard or proprietary. The specific meter table may be, but to design, standard or proprietary. The specific meter table may be, but
does not need to be, defined in this MIB module. does not need to be, defined in this MIB module.
3.3.2. Token-Bucket Meter Table 3.3.2. Token-Bucket Meter Table
This is included as an example of a common type of meter. Entries in This is included as an example of a common type of meter. Entries in
this table are referenced from the StaticRowPointer this table are referenced from the RowPointer diffServMeterSpecific
diffServMeterSpecific attributes of meter table entries. The parameters attributes of meter table entries. The parameters are represented by a
are represented by a rate diffServTBMeterRate, a burst size rate diffServTBMeterRate, a burst size diffServTBMeterBurstSize, and an
diffServTBMeterBurstSize, and an interval diffServTBMeterInterval. How interval diffServTBMeterInterval. How these parameters are used depends
these parameters are used depends on the type of meter being on the type of meter being parameterized, this is provided by the
parameterized, this is provided by the diffServTBMeterType attribute. diffServTBMeterType attribute. Additional meter parameterization tables
Additional meter parameterization tables can be defined in other MIBs can be defined in other MIBs when necessary.
when necessary.
3.4. Actions 3.4. Actions
Actions include "no action", "mark the traffic with a DSCP", "drop the Actions include "no action", "mark the traffic with a DSCP", "drop the
traffic" or "count it". Other tasks such as "shape the traffic" or "drop | traffic" or "count it". Other tasks such as "shape the traffic" or "drop
based on some algorithm" are handled elsewhere as queuing mechanisms, based on some algorithm" are handled elsewhere as queuing mechanisms,
rather than actions, consistent with [MODEL]. The "multiplexer", rather than actions, consistent with [MODEL]. The "multiplexer",
"replicator" and "null" actions described in [MODEL] are accomplished "replicator" and "null" actions described in [MODEL] are accomplished
implicitly by means of the RowPointer structures of the other elements. implicitly by means of the RowPointer structures of the other elements.
This MIB uses the Action Table diffServActionTable to organize one This MIB uses the Action Table diffServActionTable to organize one
Action's relationship with the element(s) before and after it. It allows Action's relationship with the element(s) before and after it. It allows
Actions to be cascaded to enable multiple Actions be applied to a single Actions to be cascaded to enable multiple Actions be applied to a single
traffic stream by using each entry's diffServActionNext attribute. The traffic stream by using each entry's diffServActionNext attribute. The
diffServActionNext attribute of the last action entry in the chain diffServActionNext attribute of the last action entry in the chain
points to the next element in the TCB, if any, e.g. a Queuing element. | points to the next element in the TCB, if any, e.g. a Queuing element.
It may also point at a next TCB. It may also point at a next TCB.
The parameters needed for each Action element will depend on the type of The parameters needed for each Action element will depend on the type of
Action to be taken. Hence there are specific Action Tables for all the Action to be taken. Hence there are specific Action Tables for all the
different Action types. This flexibility allows additional Actions be different Action types. This flexibility allows additional Actions be
specified in future revisions of this MIB, or in other MIBs and also specified in future revisions of this MIB, or in other MIBs and also
allows for the use of proprietary Actions without impact on those allows for the use of proprietary Actions without impact on those
defined here. defined here.
3.4.1. DSCP Mark Action Table 3.4.1. DSCP Mark Action Table
This Action is applied to traffic in order to mark it with a Diffserv This Action is applied to traffic in order to mark it with a Diffserv
Codepoint (DSCP) value, specified in the diffServDscpMarkActTable. Other Codepoint (DSCP) value, specified in the diffServDscpMarkActTable. Other
marking actions might be specified elsewhere - these are outside the marking actions might be specified elsewhere - these are outside the
scope of this MIB. scope of this MIB.
skipping to change at page 11, line 27 skipping to change at page 10, line 25
3.4.2. Count Action Table 3.4.2. Count Action Table
Count Actions are used to count the traffic passing along a particular Count Actions are used to count the traffic passing along a particular
path through the model. If specified, they are likely to be placed path through the model. If specified, they are likely to be placed
first, before other types of Action. For example, when both a Count and first, before other types of Action. For example, when both a Count and
an Absolute Dropper Action are specified, the Count Action needs to an Absolute Dropper Action are specified, the Count Action needs to
count the traffic stream before any traffic gets dropped. Note that count the traffic stream before any traffic gets dropped. Note that
there are counters contained directly in Algorithmic Dropper elements to there are counters contained directly in Algorithmic Dropper elements to
indicate the amount of traffic dropped by those elements. indicate the amount of traffic dropped by those elements.
Since count actions are defined in this way, they are inherently | Since count actions are defined in this way, they are inherently
optional. However, the management information necessary to demonstrate | optional. However, the management information necessary to demonstrate
SLA compliance or non-compliance is not available from any other source. | SLA compliance or non-compliance is not available from any other source.
Therefore, practically, count actions may be expected to be included in | Therefore, practically, count actions may be expected to be included in
each set of actions that a network manager configures. each set of actions that a network manager configures.
Counters are arranged in a single table but with separate conformance Counters are arranged in a single table but with separate conformance
statements for low-speed and high-speed interfaces, consistent with statements for low-speed and high-speed interfaces, consistent with
[IFMIB]. [IFMIB].
3.4.3. Absolute Drop Action 3.4.3. Absolute Drop Action
This action just silently discards all traffic presented to it, without This action just silently discards all traffic presented to it, without
counting it. This action has no additional parameters and so is counting it. This action has no additional parameters and so is
represented only within diffServActionType without its specific table. | represented only within diffServActionType without its specific table.
3.5. Queuing Elements 3.5. Queuing Elements
These include Algorithmic Droppers, Queues and Schedulers which are all These include Algorithmic Droppers, Queues and Schedulers which are all
inter-related in their use of queuing techniques. | inter-related in their use of queuing techniques.
3.5.1. Algorithmic Dropper Table 3.5.1. Algorithmic Dropper Table
Algorithmic Droppers are represented in this MIB by entries in an | Algorithmic Droppers are represented in this MIB by entries in an
Algorithmic Dropper Table. An Algorithmic Dropper is assumed to operate | Algorithmic Dropper Table. An Algorithmic Dropper is assumed to operate
indiscriminately on all packets that are presented at its input, all
traffic separation should be done by classifiers and meters preceding
indiscriminately on all packets that are presented at its input, all |
traffic separation should be done by classifiers and meters preceding |
it. it.
Algorithmic Droppers have a close relationship with queuing, each | Algorithmic Droppers have a close relationship with queuing, each
Algorithmic Dropper Table entry contains a diffServAlgDropQMeasure | Algorithmic Dropper Table entry contains a diffServAlgDropQMeasure
attribute, indicating which queue's state affects the calculation of the | attribute, indicating which queue's state affects the calculation of the
Algorithmic Dropper. Each entry also contains a diffServAlgDropNext | Algorithmic Dropper. Each entry also contains a diffServAlgDropNext
attribute which indicates to which queue the Algorithmic Dropper sinks | attribute which indicates to which queue the Algorithmic Dropper sinks
its traffic. its traffic.
Algorithmic Droppers may also contain a pointer to specific detail of | Algorithmic Droppers may also contain a pointer to specific detail of
the drop algorithm, diffServAlgDropSpecific. This MIB defines the detail | the drop algorithm, diffServAlgDropSpecific. This MIB defines the detail
for three drop algorithms: Tail Drop, Head Drop and Random Drop; other | for three drop algorithms: Tail Drop, Head Drop and Random Drop; other
algorithms are outside the scope of this MIB module but the general | algorithms are outside the scope of this MIB module but the general
framework is intended to allow for their inclusion via other MIB | framework is intended to allow for their inclusion via other MIB
modules. modules.
One generally-applicable parameter of a dropper is the specification of One generally-applicable parameter of a dropper is the specification of
a queue-depth threshold at which some drop action is to start. This is | a queue-depth threshold at which some drop action is to start. This is
represented in this MIB, as a base attribute, diffServAlgDropQThreshold, | represented in this MIB, as a base attribute, diffServAlgDropQThreshold,
of the Algorithmic Dropper entry. The attribute, | of the Algorithmic Dropper entry. The attribute,
diffServAlgDropQMeasure, specifies which queue's depth | diffServAlgDropQMeasure, specifies which queue's depth
diffServAlgDropQThreshold is to compare against. diffServAlgDropQThreshold is to compare against.
o A Tail Dropper requires the specification of a maximum queue depth o A Tail Dropper requires the specification of a maximum queue depth
threshold: when the queue pointed at by diffServAlgDropQMeasure threshold: when the queue pointed at by diffServAlgDropQMeasure
reaches that depth threshold, diffServAlgDropQThresh, any new reaches that depth threshold, diffServAlgDropQThresh, any new
traffic arriving at the dropper is discarded. This algorithm uses traffic arriving at the dropper is discarded. This algorithm uses
only parameters that are part of the diffServAlgDropEntry. only parameters that are part of the diffServAlgDropEntry.
o A Head Dropper requires the specification of a maximum queue depth o A Head Dropper requires the specification of a maximum queue depth
threshold: when the queue pointed at by diffServAlgDropQMeasure threshold: when the queue pointed at by diffServAlgDropQMeasure
reaches that depth threshold, diffServAlgDropQThresh, traffic reaches that depth threshold, diffServAlgDropQThresh, traffic
currently at the head of the queue is discarded. This algorithm currently at the head of the queue is discarded. This algorithm
uses only parameters that are part of the diffServAlgDropEntry. uses only parameters that are part of the diffServAlgDropEntry.
o Random Droppers are recommended as a way to control congestion, in o Random Droppers are recommended as a way to control congestion, in
[QUEUEMGMT] and called for in the [AF-PHB]. Various implementations [QUEUEMGMT] and called for in the [AF-PHB]. Various implementations
exist, which agree on marking or dropping just enough traffic to exist, which agree on marking or dropping just enough traffic to
communicate with TCP-like protocols about congestion avoidance, but communicate with TCP-like protocols about congestion avoidance, but
differ markedly on their specific parameters. This MIB attempts to differ markedly on their specific parameters. This MIB attempts to
offer a minimal set of controls for any random dropper, but expects offer a minimal set of controls for any random dropper, but expects
that vendors will augment the table with additional controls and | that vendors will augment the table with additional controls and
status in accordance with their implementation. This algorithm | status in accordance with their implementation. This algorithm
requires additional parameters on top of those in | requires additional parameters on top of those in
diffServAlgDropEntry: these are discussed below. diffServAlgDropEntry: these are discussed below.
3.5.2. Random Dropper Table 3.5.2. Random Dropper Table
One example of a random dropper is a RED-like dropper. An example of the | One example of a random dropper is a RED-like dropper. An example of the
representation chosen in this MIB for this element is shown in Figure 1. representation chosen in this MIB for this element is shown in Figure 1.
Random droppers often have their drop probability function described as Random droppers often have their drop probability function described as
a plot of drop probability (P) against averaged queue length (Q). a plot of drop probability (P) against averaged queue length (Q).
(Qmin,Pmin) then defines the start of the characteristic plot. Normally (Qmin,Pmin) then defines the start of the characteristic plot. Normally
Pmin=0, meaning with average queue length below Qmin, there will be no 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 drops. (Qmax,Pmax) defines a "knee" on the plot, after which point the
drop probability become more progressive (greater slope). (Qclip,1) drop probability become more progressive (greater slope). (Qclip,1)
defines the queue length at which all packets will be dropped. Notice defines the queue length at which all packets will be dropped. Notice
this is different from Tail Drop because this uses an averaged queue this is different from Tail Drop because this uses an averaged queue
length. Although it is possible for Qclip = Qmax. | length. Although it is possible for Qclip = Qmax.
In the MIB module, diffServRandomDropMinThreshBytes and In the MIB module, diffServRandomDropMinThreshBytes and
diffServRandomDropMinThreshPkts represent Qmin. diffServRandomDropMinThreshPkts represent Qmin.
diffServRandomDropMaxThreshBytes and diffServRandomDropMaxThreshPkts diffServRandomDropMaxThreshBytes and diffServRandomDropMaxThreshPkts
represent Qmax. diffServAlgDropQThreshold represents Qclip. | represent Qmax. diffServAlgDropQThreshold represents Qclip.
diffServRandomDropInvProbMax represents Pmax (inverse). This MIB does | diffServRandomDropInvProbMax represents Pmax (inverse). This MIB does
not represent Pmin (assumed to be zero unless otherwise represented). | not represent Pmin (assumed to be zero unless otherwise represented).
In addition, since message memory is finite, queues generally have some | In addition, since message memory is finite, queues generally have some
upper bound above which they are incapable of storing additional | upper bound above which they are incapable of storing additional
traffic. Normally this number is equal to Qclip, specified by | traffic. Normally this number is equal to Qclip, specified by
diffServeAlgDropQThreshold. diffServeAlgDropQThreshold.
Each random dropper specification is associated with a queue. This Each random dropper specification is associated with a queue. This
allows multiple drop processes (of same or different types) to be | allows multiple drop processes (of same or different types) to be
associated with the same queue, as different PHB implementations may associated with the same queue, as different PHB implementations may
require. This also allows for sequences of multiple droppers if require. This also allows for sequences of multiple droppers if
AlgDrop Queue | AlgDrop Queue
+-----------------+ +-------+ | +-----------------+ +-------+
--->| Next ---------+--+------------------->| Next -+--> ... | --->| Next ---------+--+------------------->| Next -+--> ...
| QMeasure -------+--+ | ... | | | QMeasure -------+--+ | ... |
| QThreshold | RandomDrop +-------+ | | QThreshold | RandomDrop +-------+
| Type=randomDrop | +----------------+ | | Type=randomDrop | +----------------+
| Specific -------+---->| MinThreshBytes | | | Specific -------+---->| MinThreshBytes |
+-----------------+ | MaxThreshBytes | | +-----------------+ | MaxThreshBytes |
| InvProbMax | | | InvProbMax |
| InvWeight | | | InvWeight |
| SamplingRate | | | SamplingRate |
+----------------+ | +----------------+
Figure 1: Example Use of the RandomDropTable for Random Droppers * Figure 1: Example Use of the RandomDropTable for Random Droppers
necessary. necessary.
The calculation of a smoothed queue length may also have an important | The calculation of a smoothed queue length may also have an important
bearing on the behavior of the dropper: parameters may include the | bearing on the behavior of the dropper: parameters may include the
sampling interval or rate, and the weight of each sample. The | sampling interval or rate, and the weight of each sample. The
performance may be very sensitive to the values of these parameters and 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 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 link speeds. Most algorithms include a sample weight, represented here
by diffServRandomDropInvWeight. The availability of by diffServRandomDropInvWeight. The availability of
diffServRandomDropSamplingRate as readable is important, the information diffServRandomDropSamplingRate as readable is important, the information
provided by Sampling Rate is essential to the configuration of provided by Sampling Rate is essential to the configuration of
diffServRandomDropInvWeight. Having Sampling Rate be configurable is diffServRandomDropInvWeight. Having Sampling Rate be configurable is
also helpful, as line speed increases, the ability to have queue also helpful, as line speed increases, the ability to have queue
sampling be less frequent than packet arrival is needed. Note however sampling be less frequent than packet arrival is needed. Note however
that there is ongoing research on this topic, see e.g. [ACTQMGMT] and that there is ongoing research on this topic, see e.g. [ACTQMGMT] and
[AQMROUTER]. [AQMROUTER].
Additional parameters may be added in an enterprise MIB module, e.g. by Additional parameters may be added in an enterprise MIB module, e.g. by
using AUGMENTS on this table, to handle aspects of random drop | using AUGMENTS on this table, to handle aspects of random drop
algorithms that are not standardized here. algorithms that are not standardized here.
NOTE: Deterministic Droppers can be viewed as a special case of Random NOTE: Deterministic Droppers can be viewed as a special case of Random
Droppers with the drop probability restricted to 0 and 1. Hence Droppers with the drop probability restricted to 0 and 1. Hence
Deterministic Droppers might be described by a Random Dropper with Pmin Deterministic Droppers might be described by a Random Dropper with Pmin
= 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which = 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which
dropping occurs. dropping occurs.
3.5.3. Queues and Schedulers 3.5.3. Queues and Schedulers
The Queue Table models simple FIFO queues, as described in [MODEL] The Queue Table models simple FIFO queues, as described in [MODEL]
section 7.1.1. The Scheduler Table allows flexibility in constructing section 7.1.1. The Scheduler Table allows flexibility in constructing
both simple and somewhat more complex queuing hierarchies from those | both simple and somewhat more complex queuing hierarchies from those
queues. Of course, since TCBs can be cascaded multiple times on an queues. Of course, since TCBs can be cascaded multiple times on an
interface, even more complex hierarchies can be constructed that way interface, even more complex hierarchies can be constructed that way
also. also.
Queue Table entries are pointed at by the "next" attributes of the Queue Table entries are pointed at by the "next" attributes of the
upstream elements e.g. diffServMeterSucceedNext. Note that multiple upstream elements e.g. diffServMeterSucceedNext. Note that multiple
upstream elements may direct their traffic to the same Queue Table upstream elements may direct their traffic to the same Queue Table
entry. For example, the Assured Forwarding PHB suggests that all traffic entry. For example, the Assured Forwarding PHB suggests that all traffic
marked AF11, AF12 or AF13 be placed in the same queue, after metering, marked AF11, AF12 or AF13 be placed in the same queue, after metering,
without reordering. This would be represented by having the without reordering. This would be represented by having the
diffServMeterSucceedNext of each upstream meter point at the same entry diffServMeterSucceedNext of each upstream meter point at the same entry
in the Queue Table. in the Queue Table.
NOTE: Queue Table and Scheduler Table entries are for data path | NOTE: Queue Table and Scheduler Table entries are for data path
description, they both uses Scheduler Parameterization Table entries for description, they both uses Scheduler Parameterization Table entries for
diffserv treatment parameterization. diffserv treatment parameterization.
Queue Table entries specify the scheduler it wants service from by use Queue Table entries specify the scheduler it wants service from by use
of its Next pointer. of its Next pointer.
Each Scheduler Table entry represents the algorithm in use for servicing Each Scheduler Table entry represents the algorithm in use for servicing
the one or more queues that feed it. The [MODEL] section 7.1.2 describes the one or more queues that feed it. The [MODEL] section 7.1.2 describes
a scheduler with multiple inputs: this is represented in the MIB by a scheduler with multiple inputs: this is represented in the MIB by
having the scheduling parameters be associated with each input. In this having the scheduling parameters be associated with each input. In this
way, sets of Queues can be grouped together as inputs to the same way, sets of Queues can be grouped together as inputs to the same
Scheduler. This table serves to represent the example scheduler Scheduler. This table serves to represent the example scheduler
described in the [MODEL]. More complex queuing and scheduling described in the [MODEL]. More complex queuing and scheduling
structures are possible using the tables defined in this MIB. When structures are possible using the tables defined in this MIB. When
necessary, more complex constructs may be created outside of this MIB. necessary, more complex constructs may be created outside of this MIB.
Scheduler Parameter Table entries are used to parameterize each input | Scheduler Parameter Table entries are used to parameterize each input
that feeds into a scheduler. The inputs can be a mixture of Queue Table that feeds into a scheduler. The inputs can be a mixture of Queue Table
and Scheduler Table entries. Scheduler Parameter Table entries can be and Scheduler Table entries. Scheduler Parameter Table entries can be
used/reused by one or more Queue and/or Scheduler Table entries. used/reused by one or more Queue and/or Scheduler Table entries.
For representing a Strict Priority scheduler, each scheduler input is For representing a Strict Priority scheduler, each scheduler input is
assigned a priority with respect to all the other inputs feeding the assigned a priority with respect to all the other inputs feeding the
same scheduler, with default values for the other parameters. A | same scheduler, with default values for the other parameters. Higher-
higher-priority input which contains traffic that is not being delayed | priority traffic that is not being delayed for shaping will be serviced
for shaping will be serviced before a lower-priority input. before a lower-priority input.
For Weighted Queuing methods e.g. WFQ, WRR, the "weight" of a given | For Weighted Queuing methods e.g. WFQ, WRR, the "weight" of a given
scheduler input is represented with a Minimum Service Rate leaky-bucket | scheduler input is represented with a Minimum Service Rate leaky-bucket
profile which provides guaranteed bandwidth to that input, if required. | profile which provides guaranteed bandwidth to that input, if required.
This is represented, as were token-bucket meters, by a rate | This is represented, as were token-bucket meters, by a rate
diffServSchdParamMinRateAbs and a burst size | diffServSchdParamMinRateAbs and a burst size
diffServSchdParamMinBurstSize. The rate may, alternatively, be | diffServSchdParamMinBurstSize. The rate may, alternatively, be
represented by a relative value, as a fraction of the interface's | represented by a relative value, as a fraction of the interface's
current line rate, diffServSchdParamMinRateRel to assist in cases where | current line rate, diffServSchdParamMinRateRel to assist in cases where
line rates are variable or where a higher-level policy might be | line rates are variable or where a higher-level policy might be
expressed in terms of fractions of network resources. The two rate | expressed in terms of fractions of network resources. The two rate
parameters are inter-related and changes in one may be reflected in the | parameters are inter-related and changes in one may be reflected in the
other. other.
For weighted scheduling methods, one can say loosely, that WRR focuses For weighted scheduling methods, one can say loosely, that WRR focuses
on meeting bandwidth sharing, without concern for relative delay amongst on meeting bandwidth sharing, without concern for relative delay amongst
the queues; where WFQ control both queue service order and amount of the queues; where WFQ control both queue service order and amount of
traffic serviced, providing meeting bandwidth sharing and relative delay traffic serviced, providing meeting bandwidth sharing and relative delay
ordering amongst the queues. ordering amongst the queues.
A queue or scheduled set of queues (which is an input to a scheduler) | 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 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 shaper: this is done by defining a Maximum Service Rate leaky-bucket
profile in order to limit the scheduler bandwidth available to that profile in order to limit the scheduler bandwidth available to that
input. This is represented, similarly to the minimum rate, by a rate | input. This is represented, similarly to the minimum rate, by a rate
diffServSchdParamMaxRateAbs and a burst size | diffServSchdParamMaxRateAbs and a burst size
diffServSchdParamMaxBurstSize. The rate may, alternatively, be diffServSchdParamMaxBurstSize. The rate may, alternatively, be
represented by a relative value, as a fraction of the interface's represented by a relative value, as a fraction of the interface's
current line rate, diffServSchdParamMaxRateRel. There was discussion in | current line rate, diffServSchdParamMaxRateRel. There was discussion in
the working group about alternative modeling approaches, such as | the working group about alternative modeling approaches, such as
defining a shaping action or a shaping element. We did not take this | defining a shaping action or a shaping element. We did not take this
approach because shaping is in fact something a scheduler does to its | approach because shaping is in fact something a scheduler does to its
inputs, and we felt it was simpler and more elegant to simply describe | inputs, and we felt it was simpler and more elegant to simply describe
it in that context. it in that context.
Other types of priority and weighted scheduling methods can be defined | Other types of priority and weighted scheduling methods can be defined
using existing parameters in diffServSchdParamEntry. NOTE: using existing parameters in diffServSchdParamEntry. NOTE:
diffServSchedulerMethod uses OBJECT IDENTIFIER syntax, with the diffServSchedulerMethod uses OBJECT IDENTIFIER syntax, with the
different types of scheduling methods defined as OBJECT-IDENTITY. | different types of scheduling methods defined as OBJECT-IDENTITY.
Future scheduling methods may be defined in other MIBs. This require an | Future scheduling methods may be defined in other MIBs. This requires
OBJECT-IDENTITY definition, a description of how the existing objects | an OBJECT-IDENTITY definition, a description of how the existing objects
are reused, if they are, and any new objects they require. are reused, if they are, and any new objects they require.
NOTE: hierarchical schedulers can be parameterized using this MIB by | NOTE: hierarchical schedulers can be parameterized using this MIB by
having Scheduler Table entries feeds into Scheduler Table entry. | having Scheduler Table entries feeds into Scheduler Table entry.
4. MIB Usage Example 4. MIB Usage Example
This section provides some examples on how the different table entries | This section provides some examples on how the different table entries
of this MIB may be used together for a Diffserv Device, with the usage of this MIB may be used together for a Diffserv Device, with the usage
of each individual attribute be defined within the MIB module itself. of each individual attribute be defined within the MIB module itself.
For the figures, all the MIB table entry and attribute names assumes to For the figures, all the MIB table entry and attribute names assumes to
have "diffServ" as their first common initial part of name, with the have "diffServ" as their first common initial part of name, with the
table entry name assumed to be their second common initial part of name. table entry name assumed to be their second common initial part of name.
"0.0" is being used to mean zeroDotZero. And for Scheduler Method "= X" "0.0" is being used to mean zeroDotZero. And for Scheduler Method "= X"
means "using the OID of diffServSchedulerX". means "using the OID of diffServSchedulerX".
4.1. Model's Example 4.1. Model's Example
As an example, when this MIB's structures are used for the hypothetical As an example, when this MIB's structures are used for the hypothetical
configuration in [MODEL] section 8.1, the result is shown in Figure 2, configuration in [MODEL] section 8.1, the result is shown in Figure 2,
3, and 4. The parameterization table entries' values are not specified 3, and 4. The parameterization table entries' values are not specified
in detail here, they can be obtained from [MODEL] section 8.1. * in detail here, they can be obtained from [MODEL] section 8.1.
+---------------------+ +------------------------> Q_EF +---------------------+ +------------------------> Q_EF
|DataPath | | |DataPath | |
| ifIndex=1 | | +--------------+ | ifIndex=1 | | +--------------+
| IfDirection=Ingress | +------+ | +--->|Action | | IfDirection=Ingress | +------+ | +--->|Action |
| Start --------------+--->|Clfr | | | | Id=EF2 | | Start --------------+--->|Clfr | | | | Id=EF2 |
+---------------------+ | Id=1 | | | | Next=0.0 | +---------------------+ | Id=1 | | | | Next=0.0 |
+------+ | | | Specific=0.0 | +------+ | | | Specific=0.0 |
| | | Type=AbsDrop | | | | Type=AbsDrop |
| | +--------------+ | | +--------------+
skipping to change at page 17, line 35 skipping to change at page 16, line 35
| | +-------+ | | +-------+
| | | | | |
| +--------+ | +---------+ | +--------------+ | +--------+ | +---------+ | +--------------+
+-->|FilterEF| +-->|TBMeterEF| +->|CountActEFDrop| +-->|FilterEF| +-->|TBMeterEF| +->|CountActEFDrop|
+--------+ +---------+ +--------------+ +--------+ +---------+ +--------------+
+------------+ +----------+ +--------------+ +------------+ +----------+ +--------------+
|ClfrElement | +-->|Action | +-->|AlgDrop | |ClfrElement | +-->|Action | +-->|AlgDrop |
| Id=AF11 | | | Id=AF11 | | | Id=AF11 | | Id=AF11 | | | Id=AF11 | | | Id=AF11 |
| ClfrId=1 | | | Next ----+--+ | Type=tailDrop| | ClfrId=1 | | | Next ----+--+ | Type=tailDrop|
| Order=NA | | | Specific +-+ | Next --------+--+-> Q_AF1 | | Order=NA | | | Specific +-+ | Next --------+--+-> Q_AF1
| Next ------+--+ | Type=Spcf| | | QMeasure ----+--+ | Next ------+--+ | Type=Spcf| | | QMeasure ----+--+
| Specific --+-+ +----------+ | | QThreshold | | Specific --+-+ +----------+ | | QThreshold |
+------------+ | | | Specific=0.0 | +------------+ | | | Specific=0.0 |
| | +--------------+ | | +--------------+
| | | |
| +----------+ | +------------+ | +----------+ | +------------+
+->|FilterAF11| +->|CountActAF11| +->|FilterAF11| +->|CountActAF11|
+----------+ +------------+ +----------+ +------------+
Figure 2: Example from Model Section 8.1 part 1 Figure 2: Example from Model Section 8.1 part 1
+------------+ +--------------+ +-------------+ +------------+ +--------------+ +-------------+
|ClfrElement | +-->|Meter | +-->|Action | |ClfrElement | +-->|Meter | +-->|Action |
| Id=AF21 | | | Id=AF21 | | | Id=AF21S | | Id=AF21 | | | Id=AF21 | | | Id=AF21S |
| ClfrId=1 | | | SucceedNext -+--+ | Next -------+----> Q_AF2 | | ClfrId=1 | | | SucceedNext -+--+ | Next -------+----> Q_AF2
| Order=NA | | | FailNext + | | Specific -+ | | Order=NA | | | FailNext + | | Specific -+ |
| Next ------+--+ | Specific --+ | | Type=Spcf | | | Next ------+--+ | Specific --+ | | Type=Spcf | |
| Specific --+-+ +----------+-+-+ +-----------+-+ | Specific --+-+ +----------+-+-+ +-----------+-+
+------------+ | | | | +------------+ | | | |
| | | +---+ | | | +---+
| | | | | | | |
| +----------+ | | +-----------+ | +-------------+ | +----------+ | | +-----------+ | +-------------+
+->|FilterAF21| | +->|TBMeterAF21| +->|CountActAF21S| +->|FilterAF21| | +->|TBMeterAF21| +->|CountActAF21S|
+----------+ | +-----------+ +-------------+ +----------+ | +-----------+ +-------------+
| |
+--------------------+ | +--------------------+
|
| +-----------+ +-----------+
+-->|Action | +-->|Action |
| Id=AF21F1 | | | Id=AF21F2 |
| Next -----+--+ | Next -----+------> Q_AF2
| Specific -+-+ | Specific -+-+
| Type=Spcf | | | Type=Spcf | |
+-----------+ | +-----------+ |
| | | |
| +-----------+ +-----------+ | | +-------------+ | +---------------+
+-->|Action | +-->|Action | | +->|CountActAF21F| +->|DscpMarkActAF22|
| Id=AF21F1 | | | Id=AF21F2 | | +-------------+ +---------------+
| Next -----+--+ | Next -----+------> Q_AF2 |
| Specific -+-+ | Specific -+-+ |
| Type=Spcf | | | Type=Spcf | | |
+-----------+ | +-----------+ | |
| | |
| +-------------+ | +---------------+ |
+->|CountActAF21F| +->|DscpMarkActAF22| |
+-------------+ +---------------+ |
+------------+ +------------+
|ClfrElement | +-----------------------------------------> Q_BE |ClfrElement | +-----------------------------------------> Q_BE
| Id=WildCard| | | Id=WildCard| |
| ClfrId=1 | | | ClfrId=1 | |
| Order=NA | | | Order=NA | |
| Next ------+--+ +--------------+ | Next ------+--+ +--------------+
| Specific --+------>|FilterMatchAll| | Specific --+------>|FilterMatchAll|
+------------+ +--------------+ +------------+ +--------------+
Figure 3: Example from Model Section 8.1 part 2 Figure 3: Example from Model Section 8.1 part 2
+-------------+ +-------------+
Q_EF--->|Q | Q_EF--->|Q |
| Id=EF +--+--------------------------+ | Id=EF +--+--------------------------+
| Next ----+ | +-----------+ | | Next ----+ | +-----------+ |
| SchdParam --+-->|SchdParamEF| | | SchdParam --+-->|SchdParamEF| |
+-------------+ +-----------+ | +-------------+ +-----------+ |
| |
+-------------+ | +----------------+ | +-------------+ | +----------------+
Q_AF1-->|Q | +->|Scheduler | | Q_AF1-->|Q | +->|Scheduler |
| Id=AF1 +--+--------------------------+ | Id=Diffserv | | | Id=AF1 +--+--------------------------+ | Id=Diffserv |
| Next ----+ | +------------+ | | Next=0.0 | | | Next ----+ | +------------+ | | Next=0.0 |
| SchdParam --+-->|SchdParamAF1| | | Method=Priority| | | SchdParam --+-->|SchdParamAF1| | | Method=Priority|
+-------------+ +------------+ | | SchdParam=0.0 | | +-------------+ +------------+ | | SchdParam=0.0 |
| +----------------+ | | +----------------+
+-------------+ | +-------------+ |
Q_AF2-->|Q | | | Q_AF2-->|Q | |
| Id=AF2 +--+--------------------------+ | | Id=AF2 +--+--------------------------+
| Next ----+ | +------------+ | | | Next ----+ | +------------+ |
| SchdParam --+-->|SchdParamAF2| | | | SchdParam --+-->|SchdParamAF2| |
+-------------+ +------------+ | | +-------------+ +------------+ |
| |
+-------------+ | +-------------+ |
Q_BE--->|Q | | Q_BE--->|Q | |
| Id=BE +--+--------------------------+ | Id=BE +--+--------------------------+
| Next ----+ | +-----------+ | Next ----+ | +-----------+
| SchdParam --+-->|SchdParamBE| | SchdParam --+-->|SchdParamBE|
+-------------+ +-----------+ +-------------+ +-----------+
Figure 4: Example from Model Section 8.1 part 3 Figure 4: Example from Model Section 8.1 part 3
4.2. Additional Data Path Example 4.2. Additional Data Path Example
4.2.1. Data Path and Classifier Example Discussion 4.2.1. Data Path and Classifier Example Discussion
The example in Figure 5 shows a single diffServDataPathTable entry | The example in Figure 5 shows a single diffServDataPathTable entry
feeding into a single Classifier entry, with three Classifier Element | feeding into a single Classifier entry, with three Classifier Element
and Filter Table entry pairs belonging to this Classifier 1. Notice the and Filter Table entry pairs belonging to this Classifier 1. Notice the
three Filters used here must completely classify all the traffic three Filters used here must completely classify all the traffic
presented to this data path. presented to this data path.
Another level of classification can be defined that follows the Action | Another level of classification can be defined that follows the Action
functional DataPath elements in Figure 5. This multi-level functional DataPath elements in Figure 5. This multi-level
classification allow the construction of traffic separations and | classification allow the construction of traffic separations and
specific actions at each level, like: specific actions at each level, like:
if (dept1) then take dept1-action if (dept1) then take dept1-action
{ {
if (appl1) then take dept1-appl1-action.
+---------------------+ +---------------------+
|DataPath | |DataPath |
| ifIndex=1 | | ifIndex=1 |
| IfDirection=Ingress | +------+ | IfDirection=Ingress | +------+
| Start --------------+--->|Clfr | | Start --------------+--->|Clfr |
+---------------------+ | Id=1 | +---------------------+ | Id=1 |
+------+ +------+
+------------+ +--------------+ +-----------+ +------------+ +--------------+ +-----------+
skipping to change at page 21, line 4 skipping to change at page 20, line 4
| ClfrId=1 | | | SucceedNext -+--+ | Next -----+---->... | ClfrId=1 | | | SucceedNext -+--+ | Next -----+---->...
| Order=NA | | | FailNext ----+->... | Specific -+-+ | Order=NA | | | FailNext ----+->... | Specific -+-+
| Next ------+--+ | Specific -+ | | Type=Spcf | | | Next ------+--+ | Specific -+ | | Type=Spcf | |
| Specific --+-+ +-----------+--+ +-----------+ | | Specific --+-+ +-----------+--+ +-----------+ |
+------------+ | | +-------+ +------------+ | | +-------+
| +-------+ | +--------+ | +---------+ | +-------+ | +--------+ | +---------+
+-->|Filter3| +-->|TBMeter3| +-->|CountAct3| +-->|Filter3| +-->|TBMeter3| +-->|CountAct3|
+-------+ +--------+ +---------+ +-------+ +--------+ +---------+
Figure 5: Additional Data Path Example Part 1 Figure 5: Additional Data Path Example Part 1
+-------------+ +-----------------+ | +-------------+ +-----------------+
| Id=EF | | | Id=Diffserv | | ---->|Q | +->|Scheduler |
| Next -------+-----------------------+ | Next=0.0 | | | Id=EF | | | Id=Diffserv |
| SchdParam -+| | | Method=Priority | | | Next -------+-----------------------+ | Next=0.0 |
+------------++ | | SchdParam=0.0 | | | SchdParam -+| | | Method=Priority |
| | +-----------------+ | +------------++ | | SchdParam=0.0 |
+------------+ | | | | +-----------------+
| | | +------------+ |
| +-----------+ | | | |
+->|SchdParamEF| | | | +-----------+ |
+-----------+ +---------------------+ | +->|SchdParamEF| |
+-----------+ +---------------------+
| |
+----------------+ +-------------+ | +----------------+ +-------------+ |
--->|AlgDrop | +->|Q | | --->|AlgDrop | +->|Q | |
| Id=AF11 | | | Id=AF1 | +-------------+ | | | Id=AF11 | | | Id=AF1 | +-------------+ |
| Type=randomDrop| | | Next -------+--->|Scheduler | | | Type=randomDrop| | | Next -------+--->|Scheduler | |
| Next ----------+-+--+ | SchdParam -+| | Id=AF | | | Next ----------+-+--+ | SchdParam -+| | Id=AF | |
| QMeasure ------+-+ | +------------++ | Next -------+--+ | QMeasure ------+-+ | +------------++ | Next -------+--+
| QThreshold | | | | Method=WFQ | | QThreshold | | | | Method=WFQ |
| Specific -+ | | +------------+ | SchdParam --+--+ | Specific -+ | | +------------+ | SchdParam --+--+
+-----------+----+ | | +-------------+ | +-----------+----+ | | +-------------+ |
| | | +------------+ | | | | | +------------+ |
+-----------+ | +->|SchdParamAF1| +----------------+ | +-----------+ | +->|SchdParamAF1| +----------------+
| +--------------+ | +------------+ | | | +--------------+ | +------------+ |
+->|RandomDropAF11| | | +-----------+ +->|RandomDropAF11| | | +-----------+
+--------------+ | +->|SchdParamAF| +--------------+ | +->|SchdParamAF|
| +-----------+ | +-----------+
+----------------+ | +----------------+ |
--->|AlgDrop | | --->|AlgDrop | |
| Id=AF12 | | | Id=AF12 | |
| Type=randomDrop| | | Type=randomDrop| |
| Next ----------+-+--+ | Next ----------+-+--+
| QMeasure ------+-+ | QMeasure ------+-+
| QThreshold | | QThreshold |
| Specific -+ | | Specific -+ |
+-----------+----+ +-----------+----+
| |
+-----------+ +-----------+
| +--------------+ | +--------------+
+->|RandomDropAF12| +->|RandomDropAF12|
+--------------+ +--------------+
Figure 6: Additional Data Path Example Part 2 Figure 6: Additional Data Path Example Part 2
if (appl1) then take dept1-appl1-action.
if (appl2) then take dept1-appl2-action. if (appl2) then take dept1-appl2-action.
if (appl3) then take dept1-appl3-action. if (appl3) then take dept1-appl3-action.
} }
if (dept2) then take dept2-action if (dept2) then take dept2-action
{ {
if (appl1) then take dept2-appl1-action. if (appl1) then take dept2-appl1-action.
if (appl2) then take dept2-appl2-action. if (appl2) then take dept2-appl2-action.
if (appl3) then take dept2-appl3-action. if (appl3) then take dept2-appl3-action.
} }
if (dept3) then take dept3-action if (dept3) then take dept3-action
{ {
if (appl1) then take dept3-appl1-action. if (appl1) then take dept3-appl1-action.
skipping to change at page 22, line 20 skipping to change at page 21, line 19
if (appl2) then take dept2-appl2-action. if (appl2) then take dept2-appl2-action.
if (appl3) then take dept2-appl3-action. if (appl3) then take dept2-appl3-action.
} }
if (dept3) then take dept3-action if (dept3) then take dept3-action
{ {
if (appl1) then take dept3-appl1-action. if (appl1) then take dept3-appl1-action.
if (appl2) then take dept3-appl2-action. if (appl2) then take dept3-appl2-action.
if (appl3) then take dept3-appl3-action. if (appl3) then take dept3-appl3-action.
} }
Minimally, the filters for appl1, appl2, appl3 may be reused for the | Minimally, the filters for appl1, appl2, appl3 may be reused for the
above setup. above setup.
4.2.2. Meter and Action Example Discussion 4.2.2. Meter and Action Example Discussion
A simple Meter that can be parameterized by a single TBMeter entry is | A simple Meter that can be parameterized by a single TBMeter entry is
shown here. For Metering types that require multiple TBMeter entries shown here. For Metering types that require multiple TBMeter entries
for parameterization, a second level Meter and TBMeter table entries may for parameterization, a second level Meter and TBMeter table entries may
be used. For example, for [TRTCM], with the first level TBMeter entry | be used. For example, for [TRTCM], with the first level TBMeter entry
used for Peak Information Token Bucket, the first level SucceedNext used for Peak Information Token Bucket, the first level SucceedNext
points to the second level Meter entry, with second level TBMeter entry points to the second level Meter entry, with second level TBMeter entry
used for Committed Information Token Bucket. used for Committed Information Token Bucket.
Notice the CountAct Action is shown in Figure 5. This is purposely done | Notice the CountAct Action is shown in Figure 5. This is purposely done
to indicates that all DataPath should have at least one CountAct Action. to indicate that every DataPath should have at least one CountAct
Other actions can be pointed to by the Next pointer of the CountAct Action. Other actions can be pointed to by the Next pointer of the
action, like DscpMarkAct action. CountAct action, like DscpMarkAct action.
4.2.3. Queue and Scheduler Example Discussion 4.2.3. Queue and Scheduler Example Discussion
Example in Figure 6 shows three classified input traffic streams, EF, Example in Figure 6 shows three classified input traffic streams, EF,
AF11, and AF12, feeding into their respective queue and algorithmic AF11, and AF12, feeding into their respective queue and algorithmic
droppers. After their respective dropping process, the AF traffic droppers. After their respective dropping process, the AF traffic
streams feed into the same queue, QAF1X. streams feed into the same queue, QAF1X.
A Scheduler, AF, is shown in Figure 6, as the sink for AF1X queue A Scheduler, AF, is shown in Figure 6, as the sink for AF1X queue
traffic, servicing AF1X queue with scheduling parameters indicated by traffic, servicing AF1X queue with scheduling parameters indicated by
SchdParamAF1X. This scheduler is used to service traffic from AF1X, SchdParamAF1X. This scheduler is used to service traffic from AF1X,
AF2X, AF3X queues using weighted fair queuing method. The AF2X and AF3X | AF2X, AF3X queues using weighted fair queuing method. The AF2X and AF3X
queues are not shown in Figure 6, they can be very much like AF1X queue queues are not shown in Figure 6, they can be very much like AF1X queue
setup. setup.
Another traffic stream, EF, is handled by the EF queue. Scheduler | Another traffic stream, EF, is handled by the EF queue. Scheduler
Diffserv services output of EF queue using SchdParamEF, and output of AF Diffserv services output of EF queue using SchdParamEF, and output of AF
scheduler using SchdParamAF, with Priority Queue scheduling method. scheduler using SchdParamAF, with Priority Queue scheduling method.
Notice all the diffserv traffic may go out on a link with traffic Notice all the diffserv traffic may go out on a link with traffic
shaping. The traffic shaping can be parameterize using the Shaping shaping. The traffic shaping can be parameterize using the Shaping
Scheduler in Figure 6. For shaping, the diffServSchdParamMaxRate Scheduler in Figure 6. For shaping, the diffServSchdParamMaxRate
attributes should be used. The Shaping Scheduler is indicated as the attributes should be used. The Shaping Scheduler is indicated as the
last diffserv functional element of this data path by using its Next last diffserv functional element of this data path by using its Next
pointer with value of zeroDotZero. pointer with value of zeroDotZero.
5. Conventions used in this MIB 5. Conventions used in this MIB
5.1. The use of RowPointer 5.1. The use of RowPointer to indicate data path linkage
RowPointer is a textual convention used to identify a conceptual row in RowPointer is a textual convention used to identify a conceptual row in
an SNMP Table by pointing to one of its objects. In this MIB, it is used an SNMP Table by pointing to one of its objects. One of the ways it is
to indicate succession, for pointing to data path linkage table entries. used in this MIB is to indicate succession, pointing to data path
linkage table entries.
For succession, it answers the question "what happens next?". Rather For succession, it answers the question "what happens next?". Rather
than presume that the next table must be as specified in the conceptual 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 model [MODEL] and providing its index, the RowPointer takes you to the
MIB row representing that thing. In the diffServMeterTable, for example, MIB row representing that thing. In the diffServMeterTable, for example,
the diffServMeterFailNext RowPointer might take you to another meter, the diffServMeterFailNext RowPointer might take you to another meter,
while the diffServMeterSucceedNext RowPointer would take you to an while the diffServMeterSucceedNext RowPointer would take you to an
action. action.
NOTE -- the RowPointer construct is used to build the TCBs NOTE -- the RowPointer construct is used to build the TCBs
described in [MODEL]: this MIB does not model TCBs directly - it described in [MODEL]: this MIB does not model TCBs directly - it
operates at a lower level of abstraction using only individual operates at a lower level of abstraction using only individual
elements, connected in succession by RowPointers. Therefore, the | elements, connected in succession by RowPointers. Therefore, the
concept of TCBs enclosing individual functional DataPath elements | concept of TCBs enclosing individual functional DataPath elements
is not applicable to this MIB, although such a concept may be is not applicable to this MIB, although such a concept may be
employed by management tools that use this MIB. employed by management tools that use this MIB.
It is possible that a path through a device following a set of It is possible that a path through a device following a set of
RowPointers is indeterminate i.e. it ends in a dangling RowPointer. RowPointers is indeterminate i.e. it ends in a dangling RowPointer.
Guidance is provided in the MIB module's DESCRIPTION-clause for each of Guidance is provided in the MIB module's DESCRIPTION-clause for each of
the linkage attribute. In general, for both zeroDotZero and dangling the linkage attribute. In general, for both zeroDotZero and dangling
RowPointer, it is assumed the data path ends and the traffic should be RowPointer, it is assumed the data path ends and the traffic should be
given to the none-diffserv part of the device. Any variation from this given to the next logical part of the device, usually a forwarding
usage is indicated by the attribute affected. process or a transmission engine, or the proverbial bit-bucket. Any
variation from this usage is indicated by the attribute affected.
5.2. The use of StaticRowPointer 5.2. The use of RowPointer to indicate parameters
StaticRowPointer, like RowPointer, is a textual convention used to RowPointer is also used in this MIB to indicate parameterization, for
identify a conceptual row in an SNMP Table by pointing to one of its
objects. In this MIB, it is used to indicate parameterization, for
pointing to parameterization table entries. pointing to parameterization table entries.
For indirection as in the diffServClfrElementTable, the idea is to allow For indirection (as in the diffServClfrElementTable), the idea is to
other MIBs, including proprietary ones, to define new and arcane filters allow other MIBs, including proprietary ones, to define new and arcane
- MAC headers, IPv4 and IPv6 headers, BGP Communities and all sorts of | filters - MAC headers, IPv4 and IPv6 headers, BGP Communities and all
other things - whilst still utilizing the structures of this MIB. This sorts of other things - whilst still utilizing the structures of this
is a form of class inheritance (in "object oriented" language): it MIB. This is a form of class inheritance (in "object oriented"
allows base object definitions ("classes") to be extended in proprietary language): it allows base object definitions ("classes") to be extended
or standard ways, in the future, by other documents. in proprietary or standard ways, in the future, by other documents.
StaticRowPointer also clearly indicate the identified conceptual row's RowPointer also clearly indicates the identified conceptual row's
content does not change, hence they can be simultaneously used, pointed content does not change, hence they can be simultaneously used, pointed
to, by more than one data path linkage table entries. The to, by more than one data path linkage table entries. The
identification of StaticRowPointer allows higher level policy mechanisms identification of RowPointer allows higher level policy mechanisms to
to take advantage of this characteristic. take advantage of this characteristic.
5.3. Conceptual row creation and deletion 5.3. Conceptual row creation and deletion
A number of conceptual tables defined in this MIB use as an index an 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 arbitrary integer value, unique across the scope of the agent. In order
to help with multi-manager row-creation problems, a mechanism must be 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 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 and to ensure that, when used, the manager knows whether it got what it
wanted or not. wanted or not.
Typically, such a table has an associated NextFree variable e.g. Typically, such a table has an associated NextFree variable e.g.
diffServClfrNextFree which provides a suitable value for the index of diffServClfrNextFree which provides a suitable value for the index of
the next row to be created e.g. diffServClfrId. A special value, 0, is the next row to be created e.g. diffServClfrId. A special value, 0, is
used to indicate that no more entries can be configured by the agent. | used to indicate that no more entries can be configured by the agent.
The table also has a columnar Status attribute with RowStatus syntax The table also has a columnar Status attribute with RowStatus syntax
[6]. [6].
If a manager attempts to create a conceptual row in the table (by a SET If a manager attempts to create a conceptual row in the table (by a SET
operation that contains a varbind setting the Status to a value of operation that contains a varbind setting the Status to a value of
either createAndGo or createAndWait) and if the agent has sufficient either createAndGo or createAndWait) and if the agent has sufficient
resources and has no other conceptual row with the same indices, the resources and has no other conceptual row with the same indices, the
agent will create the row and return success. If the agent has agent will create the row and return success. If the agent has
insufficient resources or such a row is already existent then it returns insufficient resources or such a row is already existent then it returns
an error. A manager must be prepared to try again in such circumstances, an error. A manager must be prepared to try again in such circumstances,
skipping to change at page 25, line 4 skipping to change at page 23, line 49
If a manager attempts to create a conceptual row in the table (by a SET If a manager attempts to create a conceptual row in the table (by a SET
operation that contains a varbind setting the Status to a value of operation that contains a varbind setting the Status to a value of
either createAndGo or createAndWait) and if the agent has sufficient either createAndGo or createAndWait) and if the agent has sufficient
resources and has no other conceptual row with the same indices, the resources and has no other conceptual row with the same indices, the
agent will create the row and return success. If the agent has agent will create the row and return success. If the agent has
insufficient resources or such a row is already existent then it returns insufficient resources or such a row is already existent then it returns
an error. A manager must be prepared to try again in such circumstances, 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 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 a second manager had got in between the first manager's read of the
NextFree value and the first manager's row-creation attempt. The use of NextFree value and the first manager's row-creation attempt. The use of
RowStatus is covered in more detail in [6]. RowStatus is covered in more detail in [6].
6. Extending this MIB 6. Extending this MIB
With the structures of this MIB divided into data path linkage tables With the structures of this MIB divided into data path linkage tables
and parameterization tables, and with the use of RowPointer and and parameterization tables, and with the use of RowPointer, new data
StaticRowPointer, new data path linkage and parameterization tables can path linkage and parameterization tables can be defined in other MIB
be defined in other MIB modules, and used with tables defined in this modules, and used with tables defined in this MIB. This MIB does not
MIB. This MIB does not limit on the type of entries its RowPointer limit on the type of entries its RowPointer attributes can point to,
attributes can point to, hence new functional data path elements can be hence new functional data path elements can be defined in other MIBs and
defined in other MIBs and integrated with functional data path elements integrated with functional data path elements of this MIB. For example,
of this MIB. For example, new Action functional data path element can new Action functional data path element can be defined for Traffic
be defined for Traffic Engineering and be integrated with Diffserv | Engineering and be integrated with Diffserv functional data path
functional data path elements, possibly used within the same data path elements, possibly used within the same data path sharing the same
sharing the same classifiers and meters. classifiers and meters.
It is more likely that new parameterization tables will be created in It is more likely that new parameterization tables will be created in
other MIBs as new methods or proprietary methods get deployed for other MIBs as new methods or proprietary methods get deployed for
existing diffserv functional data path elements. For example, different existing diffserv functional data path elements. For example, different
kinds of filters can be defined by using new filter parameterization kinds of filters can be defined by using new filter parameterization
tables. New scheduling methods can be deployed by defining new tables. New scheduling methods can be deployed by defining new
scheduling method OIDs and new scheduling parameter tables. scheduling method OIDs and new scheduling parameter tables.
Notice both new data path linkage tables and parameterization tables can Notice both new data path linkage tables and parameterization tables can
be added without needing to change this MIB document or affect existing be added without needing to change this MIB document or affect existing
tables and their usage. tables and their usage.
7. MIB Definition | 7. MIB Definition
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN |
|
IMPORTS IMPORTS
Integer32, MODULE-IDENTITY, mib-2 | Integer32, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI | FROM SNMPv2-SMI
TEXTUAL-CONVENTION | TEXTUAL-CONVENTION
FROM SNMPv2-TC; | FROM SNMPv2-TC;
|
|
diffServDSCPTC MODULE-IDENTITY |
LAST-UPDATED "200101080000Z" |
ORGANIZATION "IETF Diffserv WG" |
CONTACT-INFO |
" Fred Baker |
Cisco Systems |
519 Lado Drive |
Santa Barbara, CA 93111, USA |
E-mail: fred@cisco.com |
|
|
Kwok Ho Chan |
Nortel Networks |
600 Technology Park Drive |
Billerica, MA 01821, USA |
E-mail: khchan@nortelnetworks.com |
|
|
Andrew Smith |
Allegro Networks |
6399 San Ignacio Ave |
San Jose, CA 95119, USA |
E-mail: andrew@allegronetworks.com" |
DESCRIPTION |
"The Textual Conventions defined in this module should be used |
whenever the Diffserv Code Point is used in a MIB." |
REVISION "200101080000Z" |
DESCRIPTION |
"Initial version, published as RFC xxxx." |
::= { mib-2 12344 } -- to be assigned by IANA |
|
|
Dscp ::= TEXTUAL-CONVENTION |
DISPLAY-HINT "d" |
STATUS current |
DESCRIPTION |
"The IP header Diffserv Code-Point that may be used for |
discriminating or 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 Diffserv Code-Point that may be used for |
discriminating or marking a traffic stream. The value -1 is used |
to indicate a wildcard i.e. any value." |
REFERENCE |
"RFC 2474, RFC 2780" |
SYNTAX Integer32 (-1 | 0..63) |
END | diffServDSCPTC MODULE-IDENTITY
LAST-UPDATED "200101080000Z"
ORGANIZATION "IETF Diffserv WG"
CONTACT-INFO
" Fred Baker
Cisco Systems
519 Lado Drive
Santa Barbara, CA 93111, USA
E-mail: fred@cisco.com
SNMP-ROWPOINTER-TC-MIB DEFINITIONS ::= BEGIN | Kwok Ho Chan
Nortel Networks
600 Technology Park Drive
Billerica, MA 01821, USA
E-mail: khchan@nortelnetworks.com
IMPORTS | Andrew Smith
MODULE-IDENTITY, mib-2 | Allegro Networks
FROM SNMPv2-SMI | 6399 San Ignacio Ave
TEXTUAL-CONVENTION | San Jose, CA 95119, USA
FROM SNMPv2-TC; | E-mail: andrew@allegronetworks.com"
| DESCRIPTION
| "The Textual Conventions defined in this module should be used
snmpRowPointerTCMIB MODULE-IDENTITY | whenever the Diffserv Code Point is used in a MIB."
LAST-UPDATED "200012150000Z" | REVISION "200101080000Z"
ORGANIZATION "IETF Diffserv WG" | DESCRIPTION
CONTACT-INFO | "Initial version, published as RFC xxxx."
" Bob Moore | ::= { mib-2 12344 } -- to be assigned by IANA
IBM Corporation, BRQA/502 |
PO Box 12195 |
Research Triangle Park, NC 27709, USA |
Phone: +1 919 254 4436 |
E-Mail: remoore@us.ibm.com |
|
|
Kwok Ho Chan |
Nortel Networks |
600 Technology Park Drive |
Billerica, MA 01821, USA |
E-Mail: khchan@nortelnetworks.com" |
DESCRIPTION |
"This MIB module defines textual conventions similar to the |
RowPointer textual convention, with additional sementics." |
REVISION "200012150000Z" |
DESCRIPTION |
"Initial version, published as RFC xxxx." |
::= { mib-2 12343 } -- to be assigned by IANA |
| Dscp ::= TEXTUAL-CONVENTION
StaticRowPointer ::= TEXTUAL-CONVENTION | DISPLAY-HINT "d"
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Like a RowPointer, this textual convention represents a pointer | "The IP header Diffserv Code-Point that may be used for
to a conceptual row. The value is the name of the instance of the | discriminating or marking a traffic stream."
first accessible columnar object in the conceptual row. | REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (0..63)
The additional semantics of this textual convention, relative to | DscpOrAny ::= TEXTUAL-CONVENTION
RowPointer, are related to the object the pointer is pointing to. | DISPLAY-HINT "d"
The pointed-to object may have more than one parent object | STATUS current
pointing to it, indicating the pointed-to object can be shared by | DESCRIPTION
one or more parent objects. "The IP header Diffserv Code-Point that may be used for
discriminating or marking a traffic stream. The value -1 is used
to indicate a wild card i.e. any value."
REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (-1 | 0..63)
END
This textual convention allows a clearer definition of | DIFFSERV-MIB DEFINITIONS ::= BEGIN
parameterization table entries, as compared to datapath linking |
table entries. Objects pointed to by StaticRowPointers, |
parameterization table entries, can be reused by one or more data |
path functional elements, belonging to one or more data paths.
This textual convention also allow easier reuse of data | IMPORTS
definitions in this MIB by higher level configuration and | Unsigned32, Counter32, Counter64,
provisioning mechanisms. MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
zeroDotZero, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, RowPointer, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
ifIndex
FROM IF-MIB
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
BurstSize
FROM INTEGRATED-SERVICES-MIB
Dscp, DscpOrAny
FROM DIFFSERV-DSCP-TC;
This additional semantics facilitates the creation of instance- | diffServMib MODULE-IDENTITY
specific objects by cloning, used by higher level | LAST-UPDATED "200102140000Z"
configuration/provisioning mechanisms. The objects being cloned | ORGANIZATION "IETF Diffserv WG"
may either be special ones that express configuration information | CONTACT-INFO
at the mechanism-specific level, or simply instance-specific ones | " Fred Baker
that already exist at the time the cloning is done. When an | Cisco Systems
object with the syntax StaticRowPointer is cloned, the | 519 Lado Drive
StaticRowPointer in the newly cloned object is set to point to | Santa Barbara, CA 93111, USA
the same conceptual row that the StaticRowPointer in the cloned- | E-mail: fred@cisco.com
from object pointed to. The cloning operations may be |
accomplished either with the script-based technique defined by |
SNMP Configuration, or by ordinary SNMP Get and Set operations, |
or other mechanisms. |
Support of this additional semantics and cloning functionality is | Kwok Ho Chan
not required for conformance to this MIB. When the additional | Nortel Networks
semantics is not supported, this textual convention behaves | 600 Technology Park Drive
identically to the RowPointer textual convention." | Billerica, MA 01821, USA
SYNTAX OBJECT IDENTIFIER | E-mail: khchan@nortelnetworks.com
|
END |
DIFFSERV-MIB DEFINITIONS ::= BEGIN | Andrew Smith
Allegro Networks
6399 San Ignacio Ave
San Jose, CA 95119, USA
E-mail: andrew@allegronetworks.com"
DESCRIPTION
"This MIB defines the objects necessary to manage a device that
uses the Differentiated Services Architecture described in RFC
2475 and the Informal Management Model for Diffserv Routers in
draft-ietf-diffserv-model-06.txt."
REVISION "200102140000Z"
DESCRIPTION
"Initial version, published as RFC xxxx."
::= { mib-2 12345 } -- anybody who uses this unassigned
-- number deserves the wrath of IANA
| diffServMIBObjects OBJECT IDENTIFIER ::= { diffServMib 1 }
IMPORTS | diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 2 }
Unsigned32, Counter32, Counter64, |
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, | -- These textual conventions have no effect on either the syntax
zeroDotZero, mib-2 | -- nor the semantics of any managed object. Objects defined
FROM SNMPv2-SMI | -- using this convention are always encoded by means of the
TEXTUAL-CONVENTION, RowStatus, RowPointer, TimeStamp | -- rules that define their primitive type.
FROM SNMPv2-TC |
MODULE-COMPLIANCE, OBJECT-GROUP | SixTupleClfrL4Port ::= TEXTUAL-CONVENTION
FROM SNMPv2-CONF | DISPLAY-HINT "d"
ifIndex | STATUS current
FROM IF-MIB | DESCRIPTION
InetAddressType, InetAddress | "A value indicating a Layer-4 protocol port number."
FROM INET-ADDRESS-MIB | SYNTAX Unsigned32 (0..65535)
BurstSize |
FROM INTEGRATED-SERVICES-MIB; | IfDirection ::= TEXTUAL-CONVENTION
Dscp, DscpOrAny | STATUS current
FROM DIFFSERV-DSCP-TC; | DESCRIPTION
StaticRowPointer | "Specifies a direction of data travel on an interface. 'inbound'
FROM SNMP-ROWPOINTER-TC-MIB; | 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
}
| --
diffServMib MODULE-IDENTITY | -- Data Path
LAST-UPDATED "200012150000Z" |
ORGANIZATION "IETF Diffserv WG" |
CONTACT-INFO |
" Fred Baker |
Cisco Systems |
519 Lado Drive |
Santa Barbara, CA 93111, USA |
E-mail: fred@cisco.com |
|
|
Kwok Ho Chan |
Nortel Networks |
600 Technology Park Drive |
Billerica, MA 01821, USA |
E-mail: khchan@nortelnetworks.com |
|
|
Andrew Smith |
Allegro Networks |
6399 San Ignacio Ave |
San Jose, CA 95119, USA |
E-mail: andrew@allegronetworks.com" |
DESCRIPTION |
"This MIB defines the objects necessary to manage a device that |
uses the Differentiated Services Architecture described in RFC |
2475 and the Informal Management Model for Diffserv Routers in |
draft-ietf-diffserv-model-05.txt." |
REVISION "200012150000Z" |
DESCRIPTION |
"Initial version, published as RFC xxxx." |
::= { mib-2 12345 } -- anybody who uses this unassigned |
-- number deserves the wrath of IANA |
|
|
diffServMIBObjects OBJECT IDENTIFIER ::= { diffServMib 1 } |
diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 2 } |
|
|
|
|
|
SixTupleClfrL4Port ::= TEXTUAL-CONVENTION |
DISPLAY-HINT "d" |
STATUS current |
DESCRIPTION |
"A value indicating a Layer-4 protocol port number." |
SYNTAX Unsigned32 (0..65535) |
|
|
IfDirection ::= TEXTUAL-CONVENTION |
STATUS current |
DESCRIPTION |
"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 |
} |
|
|
-- --
- <span class="insert">Data Path</span>
diffServDataPath OBJECT IDENTIFIER ::= { diffServMIBObjects 1 } | diffServDataPath OBJECT IDENTIFIER ::= { diffServMIBObjects 1 }
|
--
-- Data Path Table
--
-- The Data Path Table enumerates the Differentiated Services
-- Data Paths within this device. Each entry in this table
-- is indexed by ifIndex and ifDirection. Each entry provides
-- the first diffserv functional data path element to process data
-- flow for each specific data path. This table should have at most
-- two entries for each DiffServ capable interface on this device;
-- ingress and egress.
--
-- Notice all diffserv functional data path elements linked together
-- using their individual next pointers and anchored by an entry
-- of the diffServDataPathTable must belong to the same data path.
-- The use of next pointer to point to diffserv functional data path
-- element of a different data path is not allowed.
-- --
|
|
diffServDataPathTable OBJECT-TYPE |
SYNTAX SEQUENCE OF DiffServDataPathEntry |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"The data path table defines the data paths in this device. Each |
data path is defined by the interface and traffic direction. The |
first diffserv functional datapath element to handle traffic for |
this data path is defined by a RowPointer, diffServDataPathStart, |
in the entries of this table." |
::= { diffServDataPath 1 } |
|
|
diffServDataPathEntry OBJECT-TYPE |
SYNTAX DiffServDataPathEntry |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"An entry in the data path table describes a single diffserv |
datapath in this device." |
INDEX { ifIndex, diffServDataPathIfDirection } |
::= { diffServDataPathTable 1 } |
|
|
DiffServDataPathEntry ::= SEQUENCE { |
diffServDataPathIfDirection IfDirection, |
diffServDataPathStart RowPointer, |
diffServDataPathStatus RowStatus |
} |
|
|
diffServDataPathIfDirection OBJECT-TYPE |
SYNTAX IfDirection |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"Specifies the direction for which this data path entry applies |
on this interface." |
::= { diffServDataPathEntry 1 } |
|
|
diffServDataPathStart OBJECT-TYPE |
SYNTAX RowPointer |
MAX-ACCESS read-create |
STATUS current |
DESCRIPTION |
"This selects the first diffserv functional datapath element to |
handle traffic for this data path. This RowPointer should point |
to an instance of one of: |
diffServClfrEntry |
diffServMeterEntry |
diffServActionEntry |
diffServAlgDropEntry |
diffServQEntry |
A value of zeroDotZero in this attribute indicates no further | diffServDataPathTable OBJECT-TYPE
Diffserv treatment is performed on traffic of this datapath. The | SYNTAX SEQUENCE OF DiffServDataPathEntry
use of zeroDotZero is the normal usage for the last functional | MAX-ACCESS not-accessible
datapath element of the current data path. | STATUS current
DESCRIPTION
"The data path table defines the data paths in this device. Each
data path is defined by the interface and traffic direction. The
first diffserv functional data path element to handle traffic for
this data path is defined by a RowPointer, diffServDataPathStart,
in the entries of this table."
::= { diffServDataPath 1 }
If the row pointed to does not exist, the treatment is as if this | diffServDataPathEntry OBJECT-TYPE
attribute contains a value of zeroDotZero." | SYNTAX DiffServDataPathEntry
::= { diffServDataPathEntry 2 } | MAX-ACCESS not-accessible
| STATUS current
| DESCRIPTION
"An entry in the data path table describes a single diffserv data
path in this device."
INDEX { ifIndex, diffServDataPathIfDirection }
::= { diffServDataPathTable 1 }
DiffServDataPathEntry ::= SEQUENCE {
diffServDataPathIfDirection IfDirection,
diffServDataPathStart RowPointer,
diffServDataPathStatus RowStatus
}
diffServDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Specifies the direction for which this data path entry applies
on this interface."
::= { diffServDataPathEntry 1 }
diffServDataPathStart OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This selects the first diffserv 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
A value of zeroDotZero in this attribute indicates no further
Diffserv 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.
If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServDataPathEntry 2 }
diffServDataPathStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or
deletion of a row/entry. Any writable variable may be modified
whether the row is active or notInService."
::= { diffServDataPathEntry 3 }
diffServDataPathStatus OBJECT-TYPE |
SYNTAX RowStatus |
MAX-ACCESS read-create |
STATUS current |
DESCRIPTION |
"The RowStatus variable controls the activation, deactivation, or |
deletion of a row/entry. Any writable variable may be modified |
whether the row is active or notInService." |
::= { diffServDataPathEntry 3 } |
|
|
-- --
| -- Classifiers
diffServClassifier OBJECT IDENTIFIER ::= { diffServMIBObjects 2 } | --
|
|
|
diffServClfrNextFree OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS read-only |
STATUS current |
DESCRIPTION |
"This object yields a value when read that is currently unused |
for a diffServClfrId instance. If a configuring system attempts |
to create a new row in the diffServClfrTable using this value, |
that operation will fail if the value has, in the meantime, been |
used to create another row that is currently valid." |
::= { diffServClassifier 1 } |
|
|
diffServClfrTable OBJECT-TYPE | diffServClassifier OBJECT IDENTIFIER ::= { diffServMIBObjects 2 }
SYNTAX SEQUENCE OF DiffServClfrEntry |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"This table enumerates all the diffserv classifier functional |
datapath elements of this device. The actual classification |
definitions are defined in diffServClfrElementTable entries |
belonging to each classifier." |
REFERENCE |
"[MODEL] section 4.1" |
::= { 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 uses the |
classifier's diffServClfrId in thier diffServClfrElementClfrId |
attribute." |
INDEX { diffServClfrId } |
::= { diffServClfrTable 1 } |
|
|
DiffServClfrEntry ::= SEQUENCE { |
diffServClfrId Unsigned32, |
diffServClfrStatus RowStatus |
} |
|
|
diffServClfrId OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"An index that enumerates the classifier entries. The set of such |
identifiers spans the whole agent. Managers should obtain new |
values for row creation in this table by reading |
diffServClfrNextFree." |
::= { diffServClfrEntry 1 } |
|
|
diffServClfrStatus OBJECT-TYPE |
SYNTAX RowStatus |
MAX-ACCESS read-create |
STATUS current |
DESCRIPTION |
"The RowStatus variable controls the activation, deactivation, or |
deletion of a classifier. Any writable variable may be modified |
whether the row is active or notInService." |
::= { diffServClfrEntry 2 } |
|
|
|
|
diffServClfrElementNextFree OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS read-only |
STATUS current |
DESCRIPTION |
"This object yields a value when read that is currently |
unused for a diffServClfrElementId instance. If a configuring |
system attempts to create a new row in the |
diffServClfrElementTable using this value, that opera- tion will |
fail if the value has, in the meantime, been used to |
create another row that is currently valid." |
::= { 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 diffserv |
functional datapath elements. Classification parameters are |
defined by entries of filter tables pointed to by |
diffServClfrElementSpecific. There can be filter tables of |
different types, and they can be inter-mixed and used within a |
classifier. An example of a filter table defined in this MIB is |
diffServSixTupleClfrTable, for IP Multi-Field Classifiers (MFCs). |
Filter tables for other filter types may be defined elsewhere." |
REFERENCE |
"[MODEL] section 4.1" |
::= { 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 { diffServClfrElementClfrId, diffServClfrElementId } |
::= { diffServClfrElementTable 1 } |
|
|
DiffServClfrElementEntry ::= SEQUENCE { |
diffServClfrElementId Unsigned32, |
diffServClfrElementClfrId Unsigned32, |
diffServClfrElementPrecedence Unsigned32, |
diffServClfrElementNext RowPointer, |
diffServClfrElementSpecific StaticRowPointer, |
diffServClfrElementPkts Counter32, |
diffServClfrElementHCPkts Counter64, |
diffServClfrElementStatus RowStatus |
} |
|
|
diffServClfrElementId OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"An index that enumerates the Classifier Element entries. The set |
of such identifiers spans the whole agent. Managers should obtain |
new values for row creation in this table by reading |
diffServClfrElementNextFree." |
::= { diffServClfrElementEntry 1 } |
|
|
diffServClfrElementClfrId OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"A classifier Id identifies which classifier this classifier |
element is a part of. This needs to be the value of |
diffServClfrId attribute for an existing row in |
diffServClfrTable." |
::= { diffServClfrElementEntry 2 } |
|
|
diffServClfrElementPrecedence OBJECT-TYPE |
SYNTAX Unsigned32 |
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. Clas- sifier elements with different order may overlap |
in their filters: the classifier element with the highest order |
that matches is taken. |
On a given interface, there must be a complete clas- sifier in | --
place at all times in the ingress direction. This means | -- Classifier Table
that there will always be one or more filters that match every | --
possible pat- tern that could be presented in an incoming | -- Classifier allows multiple classifier elements, of same or different
packet. There is no such requirement in the egress direction." | -- types, to be used together.
DEFVAL { 0 } | -- A classifier must completely classify all packets presented to it,
::= { diffServClfrElementEntry 3 } | -- this means all traffic handled by a classifier must match
| -- at least one classifier element within the classifier,
| -- with the classifier element parameters specified by a filter.
diffServClfrElementNext OBJECT-TYPE | --
SYNTAX RowPointer | -- If there is ambiguity between classifier elements of different
MAX-ACCESS read-create | -- classifier, the precedence is indicated by the order the classifiers
STATUS current | -- are linked, the first classifier in the link is applied to the
DESCRIPTION | -- traffic first.
"This attribute provides one branch of the fan-out functionality | --
of a classifier described in [MODEL] section 4.1. |
This selects the next diffserv functional datapath element to | diffServClfrNextFree OBJECT-TYPE
handle traffic for this data path. This RowPointer should point | SYNTAX Unsigned32
to an instance of one of: | MAX-ACCESS read-only
diffServClfrEntry | STATUS current
diffServMeterEntry | DESCRIPTION
diffServActionEntry | "This object yields a value when read that is currently unused
diffServAlgDropEntry | for a diffServClfrId instance. If a configuring system attempts
diffServQEntry | to create a new row in the diffServClfrTable using this value,
that operation will fail if the value has, in the meantime, been
used to create another row that is currently valid."
::= { diffServClassifier 1 }
A value of zeroDotZero in this attribute indicates no further | diffServClfrTable OBJECT-TYPE
Diffserv treatment is performed on traffic of this datapath. The | SYNTAX SEQUENCE OF DiffServClfrEntry
use of zeroDotZero is the normal usage for the last functional | MAX-ACCESS not-accessible
datapath element of the current data path. | 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."
REFERENCE
"[MODEL] section 4.1"
::= { diffServClassifier 2 }
If the row pointed to does not exist, the treatment is as if this | diffServClfrEntry OBJECT-TYPE
attribute contains a value of zeroDotZero." | SYNTAX DiffServClfrEntry
::= { diffServClfrElementEntry 4 } | MAX-ACCESS not-accessible
| STATUS current
| DESCRIPTION
diffServClfrElementSpecific OBJECT-TYPE | "An entry in the classifier table describes a single classifier.
SYNTAX StaticRowPointer | All classifier elements belonging to the same classifier uses the
MAX-ACCESS read-create | classifier's diffServClfrId in their diffServClfrElementClfrId
STATUS current | attribute."
DESCRIPTION | INDEX { diffServClfrId }
"A pointer to a valid entry in another table, filter table, | ::= { diffServClfrTable 1 }
that describes the applicable classification parameters, e.g. an |
entry in diffServSixTupleClfrTable. |
If the row pointed to does not exist, the classifier element is | DiffServClfrEntry ::= SEQUENCE {
ignored. | diffServClfrId Unsigned32,
diffServClfrStatus RowStatus
}
The value zeroDotZero is interpreted to match anything not | diffServClfrId OBJECT-TYPE
matched by another classifier element - only one such entry may | SYNTAX Unsigned32
exist for each classifier." | MAX-ACCESS not-accessible
DEFVAL { zeroDotZero } | STATUS current
::= { diffServClfrElementEntry 5 } | DESCRIPTION
| "An index that enumerates the classifier entries. The set of such
| identifiers spans the whole agent. Managers should obtain new
diffServClfrElementPkts OBJECT-TYPE | values for row creation in this table by reading
SYNTAX Counter32 | diffServClfrNextFree."
MAX-ACCESS read-only | ::= { diffServClfrEntry 1 }
STATUS current |
DESCRIPTION |
"The number of packets that have passed throught this process. On |
high speed devices, this object implements the least significant |
32 bits of diffServClfrElementHCPkts. |
Discontinuities in the value of this counter can occur at re- | diffServClfrStatus OBJECT-TYPE
initialization of the management system and at other times as | SYNTAX RowStatus
indicated by the value of ifCounterDiscontinuityTime appropriate | MAX-ACCESS read-create
to this interface." | STATUS current
::= { diffServClfrElementEntry 6 } | DESCRIPTION
| "The RowStatus variable controls the activation, deactivation, or
| deletion of a classifier. Any writable variable may be modified
diffServClfrElementHCPkts OBJECT-TYPE | whether the row is active or notInService."
SYNTAX Counter64 | ::= { diffServClfrEntry 2 }
MAX-ACCESS read-only |
STATUS current |
DESCRIPTION |
"The number of packets that have been dropped by this drop |
process. This object should be used on high speed interfaces. |
Discontinuities in the value of this counter can occur at re- | --
initialization of the management system and at other times as | -- Classifier Element Table
indicated by the value of ifCounterDiscontinuityTime appropriate | --
to this interface." | -- Entries in the classifier element table serves as
::= { diffServClfrElementEntry 7 } | -- the anchor for each classification pattern, defined
| -- in filter table entries. Each classifier element
| -- table entry also specifies the subsequent downstream
diffServClfrElementStatus OBJECT-TYPE | -- diffserv functional data path element when the
SYNTAX RowStatus | -- classification pattern is satisfied.
MAX-ACCESS read-create |
STATUS current | -- Each entry in the classifier element table describes
DESCRIPTION | -- one branch of the fan-out characteristic of a classifier
"The RowStatus variable controls the activation, | -- indicated in [MODEL] section 4.1. A classifier is made up
deactivation, or deletion of a classifier element. Any writ- | -- of one or more classifier elements.
able variable may be modified whether the row is active or | --
notInService." |
::= { diffServClfrElementEntry 8 } | diffServClfrElementNextFree OBJECT-TYPE
| SYNTAX Unsigned32
| MAX-ACCESS read-only
| STATUS current
| DESCRIPTION
diffServSixTupleClfrNextFree OBJECT-TYPE | "This object yields a value when read that is currently
SYNTAX Unsigned32 | unused for a diffServClfrElementId instance. If a configuring
MAX-ACCESS read-only | system attempts to create a new row in the
STATUS current | diffServClfrElementTable using this value, that opera- tion will
DESCRIPTION | fail if the value has, in the meantime, been used to
"This object yields a value when read that is currently unused | create another row that is currently valid."
for a diffServSixTupleClfrId instance. | ::= { diffServClassifier 3 }
If a configuring system attempts to create a new row |
in the diffServSixTupleClfrTable using this value, that operation | diffServClfrElementTable OBJECT-TYPE
will fail if the value has, in the meantime, been used | SYNTAX SEQUENCE OF DiffServClfrElementEntry
to create another row that is currently valid." | MAX-ACCESS not-accessible
::= { diffServClassifier 5 } | STATUS current
| DESCRIPTION
| "The classifier element table enumerates the relationship between
diffServSixTupleClfrTable OBJECT-TYPE | classification patterns and subsequent downstream diffserv
SYNTAX SEQUENCE OF DiffServSixTupleClfrEntry | functional data path elements. Classification parameters are
MAX-ACCESS not-accessible | defined by entries of filter tables pointed to by
STATUS current | diffServClfrElementSpecific. There can be filter tables of
DESCRIPTION | different types, and they can be inter-mixed and used within a
"A table of IP Six-Tuple Classifier filter entries that a system | classifier. An example of a filter table defined in this MIB is
may use to identify IP traffic." | diffServSixTupleClfrTable, for IP Multi-Field Classifiers (MFCs).
REFERENCE | Filter tables for other filter types may be defined elsewhere."
"[MODEL] section 4.2.2" | REFERENCE
::= { diffServClassifier 6 } | "[MODEL] section 4.1"
| ::= { diffServClassifier 4 }
|
diffServSixTupleClfrEntry OBJECT-TYPE | diffServClfrElementEntry OBJECT-TYPE
SYNTAX DiffServSixTupleClfrEntry | SYNTAX DiffServClfrElementEntry
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"An IP Six-Tuple Classifier entry describes a single filter." | "An entry in the classifier element table describes a single
INDEX { diffServSixTupleClfrId } | element of the classifier."
::= { diffServSixTupleClfrTable 1 } | INDEX { diffServClfrElementClfrId, diffServClfrElementId }
| ::= { diffServClfrElementTable 1 }
|
DiffServSixTupleClfrEntry ::= SEQUENCE { | DiffServClfrElementEntry ::= SEQUENCE {
diffServSixTupleClfrId Unsigned32, | diffServClfrElementId Unsigned32,
diffServSixTupleClfrDstAddrType InetAddressType, | diffServClfrElementClfrId Unsigned32,
diffServSixTupleClfrDstAddr InetAddress, | diffServClfrElementPrecedence Unsigned32,
diffServSixTupleClfrDstAddrMask Unsigned32, | diffServClfrElementNext RowPointer,
diffServSixTupleClfrSrcAddrType InetAddressType, | diffServClfrElementSpecific RowPointer,
diffServSixTupleClfrSrcAddr InetAddress, | diffServClfrElementStatus RowStatus
diffServSixTupleClfrSrcAddrMask Unsigned32, | }
diffServSixTupleClfrDscp DscpOrAny, |
diffServSixTupleClfrProtocol Unsigned32, | diffServClfrElementId OBJECT-TYPE
diffServSixTupleClfrDstL4PortMin SixTupleClfrL4Port, | SYNTAX Unsigned32
diffServSixTupleClfrDstL4PortMax SixTupleClfrL4Port, | MAX-ACCESS not-accessible
diffServSixTupleClfrSrcL4PortMin SixTupleClfrL4Port, | STATUS current
diffServSixTupleClfrSrcL4PortMax SixTupleClfrL4Port, | DESCRIPTION
diffServSixTupleClfrStatus RowStatus | "An index that enumerates the Classifier Element entries. The set
} | of such identifiers spans the whole agent. Managers should obtain
| new values for row creation in this table by reading
| diffServClfrElementNextFree."
::= { diffServClfrElementEntry 1 }
diffServClfrElementClfrId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A classifier Id identifies which classifier this classifier
element is a part of. This needs to be the value of
diffServClfrId attribute for an existing row in
diffServClfrTable."
::= { diffServClfrElementEntry 2 }
diffServClfrElementPrecedence OBJECT-TYPE
SYNTAX Unsigned32
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. Clas- sifier elements with different order may overlap
in their filters: the classifier element with the highest order
that matches is taken.
On a given interface, there must be a complete clas- sifier in
place at all times in the ingress direction. This means
that there will always be one or more filters that match every
possible pat- tern that could be presented in an incoming
packet. There is no such requirement in the egress direction."
DEFVAL { 0 }
::= { diffServClfrElementEntry 3 }
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 [MODEL] section 4.1.
This selects the next diffserv 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
A value of zeroDotZero in this attribute indicates no further
Diffserv 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.
If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero."
::= { diffServClfrElementEntry 4 }
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 diffServSixTupleClfrTable.
If the row pointed to does not exist, the classifier element is
ignored.
The value zeroDotZero is interpreted to match anything not
matched by another classifier element - only one such entry may
exist for each classifier."
DEFVAL { zeroDotZero }
::= { diffServClfrElementEntry 5 }
diffServClfrElementStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The RowStatus variable controls the activation,
deactivation, or deletion of a classifier element. Any writ-
able variable may be modified whether the row is active or
notInService."
::= { diffServClfrElementEntry 6 }
--
-- IP Six-Tuple Classification Table
--
-- Classification based on 6 different fields in the IP
-- header. This is intended to be IP-version-independent.
-- Filters, entries in this table, may be shared, pointed to,
-- by multiple diffServClfrElementEntry, of same or different
-- data paths in the same system.
--
diffServSixTupleClfrNextFree OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object yields a value when read that is currently unused
for a diffServSixTupleClfrId instance.
If a configuring system attempts to create a new row
in the diffServSixTupleClfrTable using this value, that operation
will fail if the value has, in the meantime, been used
to create another row that is currently valid."
::= { diffServClassifier 5 }
diffServSixTupleClfrTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServSixTupleClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of IP Six-Tuple Classifier filter entries that a system
may use to identify IP traffic."
REFERENCE
"[MODEL] section 4.2.2"
::= { diffServClassifier 6 }
diffServSixTupleClfrEntry OBJECT-TYPE
SYNTAX DiffServSixTupleClfrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An IP Six-Tuple Classifier entry describes a single filter."
INDEX { diffServSixTupleClfrId }
::= { diffServSixTupleClfrTable 1 }
DiffServSixTupleClfrEntry ::= SEQUENCE {
diffServSixTupleClfrId Unsigned32,
diffServSixTupleClfrDstAddrType InetAddressType,
diffServSixTupleClfrDstAddr InetAddress,
diffServSixTupleClfrDstPrefixLength INTEGER,
diffServSixTupleClfrSrcAddrType InetAddressType,
diffServSixTupleClfrSrcAddr InetAddress,
diffServSixTupleClfrSrcPrefixLength INTEGER,
diffServSixTupleClfrDscp DscpOrAny,
diffServSixTupleClfrProtocol Unsigned32,
diffServSixTupleClfrDstL4PortMin SixTupleClfrL4Port,
diffServSixTupleClfrDstL4PortMax SixTupleClfrL4Port,
diffServSixTupleClfrSrcL4PortMin SixTupleClfrL4Port,
diffServSixTupleClfrSrcL4PortMax SixTupleClfrL4Port,
diffServSixTupleClfrStatus RowStatus
}
diffServSixTupleClfrId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that enumerates the Six Tuple Classifier filter
entries. The set of such identifiers spans the whole agent.
Managers should obtain new values for row creation in this table
by reading diffServSixTupleClfrNextFree."
::= { diffServSixTupleClfrEntry 1 }
diffServSixTupleClfrDstAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of IP destination address used by this classifier
entry."
::= { diffServSixTupleClfrEntry 2 }
diffServSixTupleClfrId OBJECT-TYPE |
SYNTAX Unsigned32 |
MAX-ACCESS not-accessible |
STATUS current |
DESCRIPTION |
"An index that enumerates the Six Tuple Classifier filter |
entries. The set of such identifiers spans the whole agent. |
Managers should obtain new values for row creation in this table |
by reading diffServSixTupleClfrNextFree." |
::= { diffServSixTupleClfrEntry 1 } |
|
|
diffServSixTupleClfrDstAddrType OBJECT-TYPE |
SYNTAX InetAddressType |
MAX-ACCESS read-create |
STATUS current |
DESCRIPTION |
"The type of IP destination address used by this classifier |
entry." |
::= { diffServSixTupleClfrEntry 2 } |
|
|
diffServSixTupleClfrDstAddr OBJECT-TYPE diffServSixTupleClfrDstAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address to match against the packet's destination IP "The IP address to match against the packet's destination IP
address." address. diffServSixTupleClfrDstPrefixLength indicates the
number of bits that are relevant."
::= { diffServSixTupleClfrEntry 3 } ::= { diffServSixTupleClfrEntry 3 }
diffServSixTupleClfrDstAddrMask OBJECT-TYPE diffServSixTupleClfrDstPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER (0..128)
UNITS "bits" UNITS "bits"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of a mask for the matching of the destination IP "The length of the CIDR Prefix carried in
address. Masks are constructed by setting bits in sequence from diffServSixTupleClfrDstAddr. In IPv4 addresses, a length of 0
the most-significant bit downwards for indicates a match of any address; a length of 32 indicates a
diffServSixTupleClfrDstAddrMask bits length. All other bits in match of a single host address, and a length between 0 and 32
the mask, up to the number needed to fill the length of the indicates the use of a CIDR Prefix. IPv6 is similar, except that
address diffServSixTupleClfrDstAddr are cleared to zero. A zero prefix lengths range from 0..128."
bit in the mask then means that the corresponding bit in the
address always matches."
DEFVAL {0} DEFVAL {0}
::= { diffServSixTupleClfrEntry 4 } ::= { diffServSixTupleClfrEntry 4 }
diffServSixTupleClfrSrcAddrType OBJECT-TYPE diffServSixTupleClfrSrcAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of IP source address used by this classifier entry." "The type of IP source address used by this classifier entry."
::= { diffServSixTupleClfrEntry 5 } ::= { diffServSixTupleClfrEntry 5 }
diffServSixTupleClfrSrcAddr OBJECT-TYPE diffServSixTupleClfrSrcAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address to match against the source IP address of each "The IP address to match against the packet's source IP address.
packet." diffServSixTupleClfrSrcPrefixLength indicates the number of bits
that are relevant."
::= { diffServSixTupleClfrEntry 6 } ::= { diffServSixTupleClfrEntry 6 }
diffServSixTupleClfrSrcAddrMask OBJECT-TYPE diffServSixTupleClfrSrcPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER (0..128)
UNITS "bits" UNITS "bits"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of a mask for the matching of the source IP address. "The length of the CIDR Prefix carried in
Masks are constructed by setting bits in sequence from the most- diffServSixTupleClfrSrcAddr. In IPv4 addresses, a length of 0
significant bit downwards for diffServSixTupleClfrSrcAddrMask indicates a match of any address; a length of 32 indicates a
bits length. All other bits in the mask, up to the number needed match of a single host address, and a length between 0 and 32
to fill the length of the address diffServSixTupleClfrSrcAddr are indicates the use of a CIDR Prefix. IPv6 is similar, except that
cleared to zero. A zero bit in the mask then means that the prefix lengths range from 0..128."
corresponding bit in the address always matches."
DEFVAL {0} DEFVAL {0}
::= { diffServSixTupleClfrEntry 7 } ::= { diffServSixTupleClfrEntry 7 }
diffServSixTupleClfrDscp OBJECT-TYPE diffServSixTupleClfrDscp OBJECT-TYPE
SYNTAX DscpOrAny | SYNTAX DscpOrAny
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value that the DSCP in the packet must have to match this "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 entry. A value of -1 indicates that a specific DSCP value has not
been defined and thus all DSCP values are considered a match." been defined and thus all DSCP values are considered a match."
DEFVAL {-1} DEFVAL {-1}
::= { diffServSixTupleClfrEntry 8 } ::= { diffServSixTupleClfrEntry 8 }
diffServSixTupleClfrProtocol OBJECT-TYPE diffServSixTupleClfrProtocol OBJECT-TYPE
skipping to change at page 44, line 30 skipping to change at page 41, line 5
diffServSixTupleClfrStatus OBJECT-TYPE diffServSixTupleClfrStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of a classifier. Any writable variable may be modified deletion of a classifier. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServSixTupleClfrEntry 14 } ::= { diffServSixTupleClfrEntry 14 }
--
-- Meters -- Meters
-- --
diffServMeter OBJECT IDENTIFIER ::= { diffServMIBObjects 3 } diffServMeter OBJECT IDENTIFIER ::= { diffServMIBObjects 3 }
-- --
-- This MIB supports a variety of Meters. It includes a -- This MIB supports a variety of Meters. It includes a
-- specific definition for Meters whose parameter set can -- specific definition for Meters whose parameter set can
-- be modeled using Token Bucket parameters.
-- Other metering parameter sets can be defined and used -- Other metering parameter sets can be defined and used
-- when necessary. -- when necessary.
-- --
-- Multiple meter elements may be logically cascaded using -- Multiple meter elements may be logically cascaded using
-- their diffServMeterSucceedNext and diffServMeterFailNext -- their diffServMeterSucceedNext and diffServMeterFailNext
-- pointers if required. -- pointers if required.
-- One example of this might be for an AF PHB implementation -- One example of this might be for an AF PHB implementation
-- that uses multiple level conformance meters. -- that uses multiple level conformance meters.
-- --
-- Cascading of individual meter elements in the MIB is -- Cascading of individual meter elements in the MIB is
-- intended to be functionally equivalent to multiple level -- intended to be functionally equivalent to multiple level
-- conformance determination of a packet. The sequential -- conformance determination of a packet. The sequential
-- nature of the representation is merely a notational -- nature of the representation is merely a notational
-- convenience for this MIB. -- convenience for this MIB.
-- --
-- For example: -- For example:
-- Conforming to RFC 2697, srTCM can be parameterized using -- Conforming to RFC 2697, srTCM can be parameterized using
-- two sets of diffServMeterEntry and diffServTBParamEntry.
-- With the first set parameterizing the Committed Burst Size -- With the first set parameterizing the Committed Burst Size
-- token-bucket, second set parameterizing the Excess Burst Size -- token-bucket, second set parameterizing the Excess Burst Size
-- token-bucket. With both set's diffServTBParamRate parameters
-- being used to reflect the Committed Information Rate value. -- being used to reflect the Committed Information Rate value.
-- --
-- Conforming to RFC 2698, trTCM can be parameterized using -- Conforming to RFC 2698, trTCM can be parameterized using
-- two sets of diffServMeterEntry and diffServTBParamEntry.
-- With the first set parameterizing the Peak Information Rate -- With the first set parameterizing the Peak Information Rate
-- and Peak Burst Size token-bucket, second set parameterizing -- and Peak Burst Size token-bucket, second set parameterizing
-- the Committed Information Rate and Committed Burst Size -- the Committed Information Rate and Committed Burst Size
-- token-bucket. -- token-bucket.
-- --
-- Conforming to RFC 2859, tswTCM can be parameterized using -- Conforming to RFC 2859, tswTCM can be parameterized using
-- two sets of diffServMeterEntry and diffServTBParamEntry.
-- With the first set parameterizing the Committed Target Rate, -- With the first set parameterizing the Committed Target Rate,
-- second set parametering the Peak Target Rate. -- second set parametering the Peak Target Rate.
-- With both set's diffServTBParamInterval being used to
-- reflect the Average Interval as specified by RFC 2859. -- reflect the Average Interval as specified by RFC 2859.
-- --
diffServMeterNextFree OBJECT-TYPE diffServMeterNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object yields a value when read that is currently unused "This object yields a value when read that is currently unused
for a diffServMeterId instance. If a configuring system attempts for a diffServMeterId instance. If a configuring system attempts
skipping to change at page 46, line 33 skipping to change at page 42, line 49
DESCRIPTION DESCRIPTION
"An entry in the meter table describes a single conformance level "An entry in the meter table describes a single conformance level
of a meter." of a meter."
INDEX { diffServMeterId } INDEX { diffServMeterId }
::= { diffServMeterTable 1 } ::= { diffServMeterTable 1 }
DiffServMeterEntry ::= SEQUENCE { DiffServMeterEntry ::= SEQUENCE {
diffServMeterId Unsigned32, diffServMeterId Unsigned32,
diffServMeterSucceedNext RowPointer, diffServMeterSucceedNext RowPointer,
diffServMeterFailNext RowPointer, diffServMeterFailNext RowPointer,
diffServMeterSpecific StaticRowPointer, diffServMeterSpecific RowPointer,
diffServMeterStatus RowStatus diffServMeterStatus RowStatus
} }
diffServMeterId OBJECT-TYPE diffServMeterId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the Meter entries. The set of such "An index that enumerates the Meter entries. The set of such
identifiers spans the whole agent. Managers should obtain new identifiers spans the whole agent. Managers should obtain new
values for row creation in this table by reading values for row creation in this table by reading
diffServMeterNextFree." diffServMeterNextFree."
::= { diffServMeterEntry 1 } ::= { diffServMeterEntry 1 }
diffServMeterSucceedNext OBJECT-TYPE diffServMeterSucceedNext OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the traffic does conform, this selects the next diffserv "If the traffic does conform, this selects the next diffserv
functional datapath element to handle traffic for this data path. functional data path element to handle traffic for this data
This RowPointer should point to an instance of one of: path. This RowPointer should point to an instance of one of:
diffServClfrEntry diffServClfrEntry
diffServMeterEntry diffServMeterEntry
diffServActionEntry diffServActionEntry
diffServAlgDropEntry diffServAlgDropEntry
diffServQEntry diffServQEntry
A value of zeroDotZero in this attribute indicates no further A value of zeroDotZero in this attribute indicates no further
Diffserv treatment is performed on traffic of this datapath. The Diffserv treatment is performed on traffic of this data path.
use of zeroDotZero is the normal usage for the last functional The use of zeroDotZero is the normal usage for the last
datapath element of the current data path. functional data path element of the current data path.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServMeterEntry 2 } ::= { diffServMeterEntry 2 }
diffServMeterFailNext OBJECT-TYPE diffServMeterFailNext OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the traffic does not conform, this selects the next diffserv "If the traffic does not conform, this selects the next diffserv
functional datapath element to handle traffic for this data path. functional data path element to handle traffic for this data
This RowPointer should point to an instance of one of: path. This RowPointer should point to an instance of one of:
diffServClfrEntry diffServClfrEntry
diffServMeterEntry diffServMeterEntry
diffServActionEntry diffServActionEntry
diffServAlgDropEntry diffServAlgDropEntry
diffServQEntry diffServQEntry
A value of zeroDotZero in this attribute indicates no further A value of zeroDotZero in this attribute indicates no further
Diffserv treatment is performed on traffic of this datapath. The Diffserv treatment is performed on traffic of this data path.
use of zeroDotZero is the normal usage for the last functional The use of zeroDotZero is the normal usage for the last
datapath element of the current data path. functional data path element of the current data path.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServMeterEntry 3 } ::= { diffServMeterEntry 3 }
diffServMeterSpecific OBJECT-TYPE diffServMeterSpecific OBJECT-TYPE
SYNTAX StaticRowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the behaviour of the meter by pointing to an "This indicates the behavior of the meter by pointing to an entry
entry containing detailed parameters. Note that entries in that containing detailed parameters. Note that entries in that
specific table must be managed explicitly. specific table must be managed explicitly.
For example, diffServMeterSpecific may point to an entry in | For example, diffServMeterSpecific may point to an entry in
diffServTBParamTable, which contains an instance of a single set diffServTBParamTable, which contains an instance of a single set
of Token Bucket parameters." of Token Bucket parameters."
::= { diffServMeterEntry 4 } ::= { diffServMeterEntry 4 }
diffServMeterStatus OBJECT-TYPE diffServMeterStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of a meter. Any writable variable may be modified deletion of a meter. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServMeterEntry 5 } ::= { diffServMeterEntry 5 }
-- --
-- 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 -- a single token bucket. Multiple token buckets can be
-- used together to parameterize multiple levels of -- used together to parameterize multiple levels of
-- conformance. -- conformance.
-- --
-- Entries of this table are used for both policing, as token
-- bucket parameters, and shaping, as leaky bucket parameters.
--
-- Note that an entry in the Token Bucket Parameter Table can
-- be shared, pointed to, by multiple diffServMeterTable -- be shared, pointed to, by multiple diffServMeterTable
-- and diffServSchedulerTable entries.
-- --
diffServTBParamNextFree OBJECT-TYPE | diffServTBParamNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object yields a value when read that is currently unused | "This object yields a value when read that is currently unused
for a diffServTBParamId instance. If a configuring system for a diffServTBParamId instance. If a configuring system
attempts to create a new row in the diffServTBParamTable using | attempts to create a new row in the diffServTBParamTable using
this value, that operation will fail if the value has, in the this value, that operation will fail if the value has, in the
meantime, been used to create another row that is currently meantime, been used to create another row that is currently
valid." valid."
::= { diffServTBParam 1 } | ::= { diffServTBParam 1 }
diffServTBParamTable OBJECT-TYPE | diffServTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServTBParamEntry | SYNTAX SEQUENCE OF DiffServTBParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates a single set of token bucket meter "This table enumerates a single set of token bucket meter
parameters that a system may use to police or shape a stream of | parameters that a system may use to police or shape a stream of
traffic. Such meters are modelled here as having a single rate | traffic. Such meters are modeled here as having a single rate
and a single burst size. Multiple entries are used when multiple | and a single burst size. Multiple entries are used when multiple
rates/burst sizes are needed." rates/burst sizes are needed."
REFERENCE REFERENCE
"[MODEL] section 5.1" "[MODEL] section 5.1"
::= { diffServTBParam 2 } | ::= { diffServTBParam 2 }
diffServTBParamEntry OBJECT-TYPE | diffServTBParamEntry OBJECT-TYPE
SYNTAX DiffServTBParamEntry | SYNTAX DiffServTBParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry that describes a single set of token bucket | "An entry that describes a single set of token bucket
parameters." parameters."
INDEX { diffServTBParamId } | INDEX { diffServTBParamId }
::= { diffServTBParamTable 1 } | ::= { diffServTBParamTable 1 }
DiffServTBParamEntry ::= SEQUENCE { |
diffServTBParamId Unsigned32, |
diffServTBParamType OBJECT IDENTIFIER, |
diffServTBParamRate Unsigned32, |
diffServTBParamBurstSize BurstSize, |
diffServTBParamInterval Unsigned32, |
diffServTBParamStatus RowStatus |
DiffServTBParamEntry ::= SEQUENCE {
diffServTBParamId Unsigned32,
diffServTBParamType OBJECT IDENTIFIER,
diffServTBParamRate Unsigned32,
diffServTBParamBurstSize BurstSize,
diffServTBParamInterval Unsigned32,
diffServTBParamStatus RowStatus
} }
diffServTBParamId OBJECT-TYPE | diffServTBParamId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the TBParam entries. The set of such | "An index that enumerates the TBParam entries. The set of such
identifiers spans the whole agent. Managers should obtain new identifiers spans the whole agent. Managers should obtain new
values for row creation in this table by reading | values for row creation in this table by reading
diffServTBParamNextFree." diffServTBParamNextFree."
::= { diffServTBParamEntry 1 } | ::= { diffServTBParamEntry 1 }
diffServTBParamType OBJECT-TYPE | diffServTBParamType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Metering/Shaping algorithm associated with the Token/Leaky | "The Metering/Shaping algorithm associated with the Token/Leaky
Bucket parameters. Bucket parameters.
{0 0} indicates this is unknown. | { 0 0 } indicates this is unknown.
Standard values for generic algorithms: | Standard values for generic algorithms:
diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, | diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate,
diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, | diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware,
diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, | diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware,
diffServTBParamTswTCM diffServTBParamTswTCM
are specified in this MIB as OBJECT-IDENTITYS; additional values | are specified in this MIB as OBJECT-IDENTITYS; additional values
may be further specified in other MIBs." may be further specified in other MIBs."
REFERENCE REFERENCE
"[MODEL] section 5" "[MODEL] section 5"
::= { diffServTBParamEntry 2 } | ::= { diffServTBParamEntry 2 }
diffServTBParamRate OBJECT-TYPE | diffServTBParamRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The token-bucket rate, in kilobits per second (kbps). This "The token-bucket rate, in kilobits per second (kbps). This
attribute is used for: 1. CIR in RFC 2697 for srTCM 2. PIR and attribute is used for: 1. CIR in RFC 2697 for srTCM 2. PIR and
CIR in RFC 2698 for trTCM 3. CTR and PTR in RFC 2859 for TSWTCM CIR in RFC 2698 for trTCM 3. CTR and PTR in RFC 2859 for TSWTCM
4. AverageRate used in [MODEL] section 5." 4. AverageRate used in [MODEL] section 5."
::= { diffServTBParamEntry 3 } | ::= { diffServTBParamEntry 3 }
diffServTBParamBurstSize OBJECT-TYPE | diffServTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize SYNTAX BurstSize
UNITS "Bytes" UNITS "Bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of bytes in a single transmission burst. "The maximum number of bytes in a single transmission burst.
This attribute is used for: 1. CBS and EBS in RFC 2697 for srTCM 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 used in 2. CBS and PBS in RFC 2698 for trTCM 3. Burst Size used in
[MODEL] section 5." [MODEL] section 5."
::= { diffServTBParamEntry 4 } | ::= { diffServTBParamEntry 4 }
diffServTBParamInterval OBJECT-TYPE | diffServTBParamInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time interval used with the token bucket. For: 1. Average "The time interval used with the token bucket. For: 1. Average
Rate Meter, [MODEL] section 5.2.1, - Delta. 2. Simple Token Rate Meter, [MODEL] section 5.2.1, - Delta. 2. Simple Token
Bucket Meter, [MODEL] section 5.1, Bucket Meter, [MODEL] section 5.1,
- time interval t. 3. RFC 2859 TSWTCM, - AVG_INTERVAL. 4. - time interval t. 3. RFC 2859 TSWTCM, - AVG_INTERVAL. 4.
RFC 2697 srTCM, RFC 2698 trTCM, - token bucket RFC 2697 srTCM, RFC 2698 trTCM, - token bucket
update time interval." update time interval."
::= { diffServTBParamEntry 5 } | ::= { diffServTBParamEntry 5 }
diffServTBParamStatus OBJECT-TYPE | diffServTBParamStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of a meter. Any writable variable may be modified deletion of a meter. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServTBParamEntry 6 } | ::= { diffServTBParamEntry 6 }
diffServTBParamSimpleTokenBucket OBJECT-IDENTITY | diffServTBParamSimpleTokenBucket OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of tokenBucket(2) indicates the use of Two Parameter Token | "Value of tokenBucket(2) indicates the use of Two Parameter Token
Bucket Meter as described in [MODEL] section 5.2.3." | Bucket Meter as described in [MODEL] section 5.2.3."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 3 } | ::= { diffServTBParam 3 }
diffServTBParamAvgRate OBJECT-IDENTITY | diffServTBParamAvgRate OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of avgRate(3) indicates the use of Average Rate Meter as | "Value of avgRate(3) indicates the use of Average Rate Meter as
described in [MODEL] section 5.2.1." | described in [MODEL] section 5.2.1."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 4 } | ::= { diffServTBParam 4 }
diffServTBParamSrTCMBlind OBJECT-IDENTITY | diffServTBParamSrTCMBlind OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of srTCMBlind(4) and srTCMAware(5) indicates the use of | "Value of srTCMBlind(4) and srTCMAware(5) indicates the use of
Single Rate Three Color Marker Metering as defined by RFC 2697, | Single Rate Three Color Marker Metering as defined by RFC 2697,
with `Color Blind' and `Color Aware' mode as described by the | with `Color Blind' and `Color Aware' mode as described by the
RFC." | RFC."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 5 } | ::= { diffServTBParam 5 }
diffServTBParamSrTCMAware OBJECT-IDENTITY | diffServTBParamSrTCMAware OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of srTCMBlind(4) and srTCMAware(5) indicates the use of | "Value of srTCMBlind(4) and srTCMAware(5) indicates the use of
Single Rate Three Color Marker Metering as defined by RFC 2697, | Single Rate Three Color Marker Metering as defined by RFC 2697,
with `Color Blind' and `Color Aware' mode as described by the | with `Color Blind' and `Color Aware' mode as described by the
RFC." | RFC."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 6 } | ::= { diffServTBParam 6 }
diffServTBParamTrTCMBlind OBJECT-IDENTITY | diffServTBParamTrTCMBlind OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of trTCMBlind(6) and trTCMAware(7) indicates the use of | "Value of trTCMBlind(6) and trTCMAware(7) indicates the use of
Two Rate Three Color Marker Metering as defined by RFC 2698, with | Two Rate Three Color Marker Metering as defined by RFC 2698, with
`Color Blind' and `Color Aware' mode as described by the RFC." | `Color Blind' and `Color Aware' mode as described by the RFC."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 7 } | ::= { diffServTBParam 7 }
diffServTBParamTrTCMAware OBJECT-IDENTITY | diffServTBParamTrTCMAware OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of trTCMBlind(6) and trTCMAware(7) indicates the use of | "Value of trTCMBlind(6) and trTCMAware(7) indicates the use of
Two Rate Three Color Marker Metering as defined by RFC 2698, with | Two Rate Three Color Marker Metering as defined by RFC 2698, with
`Color Blind' and `Color Aware' mode as described by the RFC." | `Color Blind' and `Color Aware' mode as described by the RFC."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 8 } | ::= { diffServTBParam 8 }
diffServTBParamTswTCM OBJECT-IDENTITY | diffServTBParamTswTCM OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"Value of tswTCM(8) indicates the use of Time Sliding Window | "Value of tswTCM(8) indicates the use of Time Sliding Window
Three Color Marker Metering as defined by RFC 2859." | Three Color Marker Metering as defined by RFC 2859."
REFERENCE | REFERENCE
"[MODEL] sections 5 and 7.1.2" | "[MODEL] sections 5 and 7.1.2"
::= { diffServTBParam 9 } | ::= { diffServTBParam 9 }
-- --
-- Actions -- Actions
-- --
diffServAction OBJECT IDENTIFIER ::= { diffServMIBObjects 5 } | diffServAction OBJECT IDENTIFIER ::= { diffServMIBObjects 5 }
-- --
-- The Action Table allows enumeration of the different -- The Action Table allows enumeration of the different
-- types of actions to be applied to a traffic flow. -- types of actions to be applied to a traffic flow.
-- --
diffServActionNextFree OBJECT-TYPE diffServActionNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 54, line 39 skipping to change at page 51, line 12
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry in the action table allows description of one "Each entry in the action table allows description of one
specific action to be applied to traffic." specific action to be applied to traffic."
INDEX { diffServActionId } INDEX { diffServActionId }
::= { diffServActionTable 1 } ::= { diffServActionTable 1 }
DiffServActionEntry ::= SEQUENCE { DiffServActionEntry ::= SEQUENCE {
diffServActionId Unsigned32, diffServActionId Unsigned32,
diffServActionNext RowPointer, diffServActionNext RowPointer,
diffServActionSpecific StaticRowPointer, diffServActionSpecific RowPointer,
diffServActionType INTEGER, diffServActionType INTEGER,
diffServActionStatus RowStatus diffServActionStatus RowStatus
} }
diffServActionId OBJECT-TYPE diffServActionId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the Action entries. The set of such "An index that enumerates the Action entries. The set of such
skipping to change at page 55, line 27 skipping to change at page 51, line 43
"This selects the next diffserv functional datapath element to "This selects the next diffserv functional datapath element to
handle traffic for this data path. This RowPointer should point handle traffic for this data path. This RowPointer should point
to an instance of one of: to an instance of one of:
diffServClfrEntry diffServClfrEntry
diffServMeterEntry diffServMeterEntry
diffServActionEntry diffServActionEntry
diffServAlgDropEntry diffServAlgDropEntry
diffServQEntry diffServQEntry
A value of zeroDotZero in this attribute indicates no further A value of zeroDotZero in this attribute indicates no further
Diffserv treatment is performed on traffic of this datapath. The Diffserv treatment is performed on traffic of this data path.
use of zeroDotZero is the normal usage for the last functional The use of zeroDotZero is the normal usage for the last
datapath element of the current data path. functional data path element of the current data path.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServActionEntry 2 } ::= { diffServActionEntry 2 }
diffServActionSpecific OBJECT-TYPE diffServActionSpecific OBJECT-TYPE
SYNTAX StaticRowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to an object instance providing additional information "A pointer to an object instance providing additional information
for the type of action indicated by this action table entry. for the type of action indicated by this action table entry.
For the standard actions defined by this MIB module, this should For the standard actions defined by this MIB module, this should
point to one of the following: a diffServDscpMarkActEntry, a point to one of the following: a diffServDscpMarkActEntry, a
diffServCountActEntry. For other actions, it may point to an diffServCountActEntry. For other actions, it may point to an
object instance defined in some other MIB." object instance defined in some other MIB."
skipping to change at page 61, line 17 skipping to change at page 58, line 5
diffServCountActStatus OBJECT-TYPE diffServCountActStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of this entry. Any writable variable may be modified deletion of this entry. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServCountActEntry 7 } ::= { diffServCountActEntry 7 }
--
-- Algorithmic Drop Table -- Algorithmic Drop Table
-- --
diffServAlgDrop OBJECT IDENTIFIER ::= { diffServMIBObjects 6 } | diffServAlgDrop OBJECT IDENTIFIER ::= { diffServMIBObjects 6 }
diffServAlgDropNextFree OBJECT-TYPE diffServAlgDropNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object yields a value when read that is currently unused "This object yields a value when read that is currently unused
for a diffServAlgDropId instance. If a configuring system for a diffServAlgDropId instance. If a configuring system
attempts to create a new row in the diffServAlgDropTable using attempts to create a new row in the diffServAlgDropTable using
this value, that operation will fail if the value has, in the this value, that operation will fail if the value has, in the
skipping to change at page 62, line 23 skipping to change at page 59, line 5
pointed to by diffServAlgDropSpecific when necessary." pointed to by diffServAlgDropSpecific when necessary."
INDEX { diffServAlgDropId } INDEX { diffServAlgDropId }
::= { diffServAlgDropTable 1 } ::= { diffServAlgDropTable 1 }
DiffServAlgDropEntry ::= SEQUENCE { DiffServAlgDropEntry ::= SEQUENCE {
diffServAlgDropId Unsigned32, diffServAlgDropId Unsigned32,
diffServAlgDropType INTEGER, diffServAlgDropType INTEGER,
diffServAlgDropNext RowPointer, diffServAlgDropNext RowPointer,
diffServAlgDropQMeasure RowPointer, diffServAlgDropQMeasure RowPointer,
diffServAlgDropQThreshold Unsigned32, diffServAlgDropQThreshold Unsigned32,
diffServAlgDropSpecific StaticRowPointer, diffServAlgDropSpecific RowPointer,
diffServAlgDropOctets Counter32, diffServAlgDropOctets Counter32,
diffServAlgDropHCOctets Counter64, diffServAlgDropHCOctets Counter64,
diffServAlgDropPkts Counter32, diffServAlgDropPkts Counter32,
diffServAlgDropHCPkts Counter64, diffServAlgDropHCPkts Counter64,
diffServAlgDropStatus RowStatus diffServAlgDropStatus RowStatus
} }
diffServAlgDropId OBJECT-TYPE diffServAlgDropId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 63, line 49 skipping to change at page 60, line 29
"This selects the next diffserv functional datapath element to "This selects the next diffserv functional datapath element to
handle traffic for this data path. This RowPointer should point handle traffic for this data path. This RowPointer should point
to an instance of one of: to an instance of one of:
diffServClfrEntry diffServClfrEntry
diffServMeterEntry diffServMeterEntry
diffServActionEntry diffServActionEntry
diffServAlgDropEntry diffServAlgDropEntry
diffServQEntry diffServQEntry
A value of zeroDotZero in this attribute indicates no further A value of zeroDotZero in this attribute indicates no further
Diffserv treatment is performed on traffic of this datapath. The Diffserv treatment is performed on traffic of this data path.
use of zeroDotZero is the normal usage for the last functional The use of zeroDotZero is the normal usage for the last
datapath element of the current data path. functional data path element of the current data path.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
::= { diffServAlgDropEntry 3 } ::= { diffServAlgDropEntry 3 }
diffServAlgDropQMeasure OBJECT-TYPE diffServAlgDropQMeasure OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 64, line 38 skipping to change at page 61, line 17
"A threshold on the depth in bytes of the queue being measured at "A threshold on the depth in bytes of the queue being measured at
which a trigger is generated to the dropping algorithm. which a trigger is generated to the dropping algorithm.
For the tailDrop(2) or headDrop(3) algorithms, this represents For the tailDrop(2) or headDrop(3) algorithms, this represents
the depth of the queue, pointed to by diffServAlgDropQMeasure, at the depth of the queue, pointed to by diffServAlgDropQMeasure, at
which the drop action will take place. Other algorithms will need which the drop action will take place. Other algorithms will need
to define their own semantics for this threshold." to define their own semantics for this threshold."
::= { diffServAlgDropEntry 5 } ::= { diffServAlgDropEntry 5 }
diffServAlgDropSpecific OBJECT-TYPE diffServAlgDropSpecific OBJECT-TYPE
SYNTAX StaticRowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Points to a table entry that provides further detail regarding a "Points to a table entry that provides further detail regarding a
drop algorithm. drop algorithm.
Entries with diffServAlgDropType equal to other(1) may have this Entries with diffServAlgDropType equal to other(1) may have this
point to a table defined in another MIB module. point to a table defined in another MIB module.
Entries with diffServAlgDropType equal to randomDrop(4) must have Entries with diffServAlgDropType equal to randomDrop(4) must have
skipping to change at page 67, line 36 skipping to change at page 64, line 6
random algorithm." random algorithm."
INDEX { diffServRandomDropId } INDEX { diffServRandomDropId }
::= { diffServRandomDropTable 1 } ::= { diffServRandomDropTable 1 }
DiffServRandomDropEntry ::= SEQUENCE { DiffServRandomDropEntry ::= SEQUENCE {
diffServRandomDropId Unsigned32, diffServRandomDropId Unsigned32,
diffServRandomDropMinThreshBytes Unsigned32, diffServRandomDropMinThreshBytes Unsigned32,
diffServRandomDropMinThreshPkts Unsigned32, diffServRandomDropMinThreshPkts Unsigned32,
diffServRandomDropMaxThreshBytes Unsigned32, diffServRandomDropMaxThreshBytes Unsigned32,
diffServRandomDropMaxThreshPkts Unsigned32, diffServRandomDropMaxThreshPkts Unsigned32,
diffServRandomDropInvProbMax Unsigned32, diffServRandomDropProbMax Unsigned32,
diffServRandomDropInvWeight Unsigned32, diffServRandomDropInvWeight Unsigned32,
diffServRandomDropSamplingRate Unsigned32, diffServRandomDropSamplingRate Unsigned32,
diffServRandomDropStatus RowStatus diffServRandomDropStatus RowStatus
} }
diffServRandomDropId OBJECT-TYPE diffServRandomDropId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 68, line 41 skipping to change at page 65, line 7
diffServRandomDropMinThreshBytes." diffServRandomDropMinThreshBytes."
::= { diffServRandomDropEntry 3 } ::= { diffServRandomDropEntry 3 }
diffServRandomDropMaxThreshBytes OBJECT-TYPE diffServRandomDropMaxThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth beyond which traffic has a probability "The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropInvProbMax of being dropped or indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit, marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshPkts." diffServRandomDropMaxThreshPkts."
::= { diffServRandomDropEntry 4 } ::= { diffServRandomDropEntry 4 }
diffServRandomDropMaxThreshPkts OBJECT-TYPE diffServRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth beyond which traffic has a probability "The average queue depth beyond which traffic has a probability
indicated by diffServRandomDropInvProbMax of being dropped or indicated by diffServRandomDropProbMax of being dropped or
marked. Note that this differs from the physical queue limit, marked. Note that this differs from the physical queue limit,
which is stored in diffServAlgDropQThreshold. Changes in this which is stored in diffServAlgDropQThreshold. Changes in this
variable may or may not be reflected in the reported value of variable may or may not be reflected in the reported value of
diffServRandomDropMaxThreshBytes." diffServRandomDropMaxThreshBytes."
::= { diffServRandomDropEntry 5 } ::= { diffServRandomDropEntry 5 }
diffServRandomDropInvProbMax OBJECT-TYPE diffServRandomDropProbMax OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The worst case random drop probability, expressed as the inverse "The worst case random drop probability, expressed in drops per
of the drop probability. With special case of the value zero thousand packets.
meaning zero probability of drop.
For example, if every packet may be dropped in the worst case For example, if every packet may be dropped in the worst case
(100%), this has the value of 4,294,967,295." (100%), this has the value 1000. Alternatively, if in the worst
case one percent (1%) of traffic may be dropped, it has the value
10."
::= { diffServRandomDropEntry 6 } ::= { diffServRandomDropEntry 6 }
diffServRandomDropInvWeight OBJECT-TYPE diffServRandomDropInvWeight OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The weighting of past history in affecting the calculation of "The weighting of past history in affecting the calculation of
the current queue average. The moving average of the queue depth the current queue average. The moving average of the queue depth
uses the inverse of this value as the factor for the new queue uses the inverse of this value as the factor for the new queue
skipping to change at page 70, line 22 skipping to change at page 67, line 5
diffServRandomDropStatus OBJECT-TYPE diffServRandomDropStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of this entry. Any writable variable may be modified deletion of this entry. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServRandomDropEntry 9 } ::= { diffServRandomDropEntry 9 }
--
-- Queue Table -- Queue Table
-- --
diffServQueue OBJECT IDENTIFIER ::= { diffServMIBObjects 7 } | diffServQueue OBJECT IDENTIFIER ::= { diffServMIBObjects 7 }
-- --
-- An entry of diffServQTable represents a FIFO queue diffserv -- An entry of diffServQTable represents a FIFO queue diffserv
-- functional datapath element as described in [MODEL] section -- functional datapath element as described in [MODEL] section
-- 7.1.1. -- 7.1.1.
-- Notice the specification of scheduling parameters for a queue -- Notice the specification of scheduling parameters for a queue
-- as part of the input to a scheduler functional datapath -- as part of the input to a scheduler functional datapath
-- element as described in [MODEL] section 7.1.2. This allows -- element as described in [MODEL] section 7.1.2. This allows
-- building of hierarchical queuing/scheduling.
-- A queue therefore is parameterized by: -- A queue therefore is parameterized by:
-- 1. Which scheduler will service this queue, diffServQNext. -- 1. Which scheduler will service this queue, diffServQNext.
-- 2. How the scheduler will service this queue, with respect -- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service, -- to all the other queues the same scheduler needs to service,
-- diffServQSchdParam. -- diffServQSchdParam.
-- --
-- Notice one or more upstream diffserv datapath element may share, -- Notice one or more upstream diffserv datapath element may share,
-- point to, a diffServQTable entry as described in [MODEL] section -- point to, a diffServQTable entry as described in [MODEL] section
-- 7.1.1. -- 7.1.1.
-- --
skipping to change at page 71, line 40 skipping to change at page 68, line 20
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Queue Table describes a single queue. With each "An entry in the Queue Table describes a single queue. With each
entry belonging to one and only one datapath." entry belonging to one and only one datapath."
INDEX { diffServQId } INDEX { diffServQId }
::= { diffServQTable 1 } ::= { diffServQTable 1 }
DiffServQEntry ::= SEQUENCE { DiffServQEntry ::= SEQUENCE {
diffServQId Unsigned32, diffServQId Unsigned32,
diffServQNext RowPointer, diffServQNext RowPointer,
diffServQSchdParam StaticRowPointer, diffServQSchdParam RowPointer,
diffServQStatus RowStatus diffServQStatus RowStatus
} }
diffServQId OBJECT-TYPE diffServQId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the Queue entries. The set of such "An index that enumerates the Queue entries. The set of such
identifiers spans the whole agent. Managers should obtain new identifiers spans the whole agent. Managers should obtain new
skipping to change at page 72, line 29 skipping to change at page 69, line 6
diffServSchedulerEntry diffServSchedulerEntry
A value of zeroDotZero in this attribute indicates an incomplete A value of zeroDotZero in this attribute indicates an incomplete
diffServQEntry instance. An illegal configuration. diffServQEntry instance. An illegal configuration.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
::= { diffServQEntry 2 } ::= { diffServQEntry 2 }
diffServQSchdParam OBJECT-TYPE diffServQSchdParam OBJECT-TYPE
SYNTAX StaticRowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This StaticRowPointer indicates the entry in "This RowPointer indicates the entry in diffServRateControlTable
diffServSchdParamTable the scheduler, pointed to by the scheduler, pointed to by diffServQNext, should use to service
diffServQNext, should use to service this queue. this queue.
A value of zeroDotZero in this attribute indicates an incomplete A value of zeroDotZero in this attribute indicates an incomplete
diffServQEntry instance. An illegal configuration. diffServQEntry instance. An illegal configuration.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." attribute contains a value of zeroDotZero."
::= { diffServQEntry 3 } ::= { diffServQEntry 3 }
diffServQStatus OBJECT-TYPE diffServQStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
skipping to change at page 73, line 14 skipping to change at page 69, line 35
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of a queue. Any writable variable may be modified deletion of a queue. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServQEntry 4 } ::= { diffServQEntry 4 }
-- --
-- Scheduler Table -- Scheduler Table
-- --
diffServScheduler OBJECT IDENTIFIER ::= { diffServMIBObjects 8 } | diffServScheduler OBJECT IDENTIFIER ::= { diffServMIBObjects 8 }
-- --
-- The Scheduler Table is used for representing packet schedulers: -- The Scheduler Table is used for representing packet schedulers:
-- it provides flexibility for multiple scheduling algorithms, each -- it provides flexibility for multiple scheduling algorithms, each
-- servicing multiple queues, to be used on the same logical/physical -- servicing multiple queues, to be used on the same logical/physical
-- interface. -- interface.
-- Notice the servicing parameters the scheduler uses is -- Notice the servicing parameters the scheduler uses is
-- specified by each of its upstream functional datapath elements, -- specified by each of its upstream functional datapath elements,
-- most likely queues or schedulers. -- most likely queues or schedulers.
-- The coordination and coherency between the servicing parameters -- The coordination and coherency between the servicing parameters
-- of the scheduler's upstream functional datapath elements must -- of the scheduler's upstream functional datapath elements must
-- be maintained for the scheduler to function correctly. -- be maintained for the scheduler to function correctly.
-- --
-- The diffServSchedulerSpecific attribute is used for specifying
-- the servicing parameters for output of a scheduler when its -- the servicing parameters for output of a scheduler when its
-- downstream functional datapath element is another scheduler. -- downstream functional datapath element is another scheduler.
-- This is used for building hierarchical queue/scheduler. -- This is used for building hierarchical queue/scheduler.
-- --
-- Scheduler Table entries can be used to configure a shaper.
-- When diffServSchedulerMethod contains the OBJECT IDENTIFIER
-- diffServSchedulerShaper, the diffServSchedulerEntry is used
-- as a shaper. As a shaper, diffServSchedulerSpecific will
-- reference a diffServTBParamTable entry to specify the
-- Leaky Bucket parameters used for the shaper.
--
-- More discussion of the scheduler functional datapath element -- More discussion of the scheduler functional datapath element
-- is in [MODEL] section 7.1.2. -- is in [MODEL] section 7.1.2.
-- --
diffServSchedulerNextFree OBJECT-TYPE * diffServSchedulerNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object yields a value when read that is currently unused "This object yields a value when read that is currently unused
for a diffServSchedulerId instance. If a configuring system for a diffServSchedulerId instance. If a configuring system
attempts to create a new row in the diffServSchedulerTable using attempts to create a new row in the diffServSchedulerTable using
this value, that operation will fail if the value has, in the this value, that operation will fail if the value has, in the
meantime, been used to create another row that is currently meantime, been used to create another row that is currently
valid." valid."
::= { diffServScheduler 1 } | ::= { diffServScheduler 1 }
diffServSchedulerTable OBJECT-TYPE diffServSchedulerTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServSchedulerEntry SYNTAX SEQUENCE OF DiffServSchedulerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduler Table enumerates packet schedulers. Multiple "The Scheduler Table enumerates packet schedulers. Multiple
scheduling algorithms can be used on a given datapath, with each scheduling algorithms can be used on a given datapath, with each
algorithm described by one diffServSchedulerEntry." algorithm described by one diffServSchedulerEntry."
REFERENCE REFERENCE
"[MODEL] section 7.1.2" "[MODEL] section 7.1.2"
::= { diffServScheduler 2 } | ::= { diffServScheduler 2 }
diffServSchedulerEntry OBJECT-TYPE diffServSchedulerEntry OBJECT-TYPE
SYNTAX DiffServSchedulerEntry SYNTAX DiffServSchedulerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Scheduler Table describing a single instance of "An entry in the Scheduler Table describing a single instance of
a scheduling algorithm." a scheduling algorithm."
INDEX { diffServSchedulerId } INDEX { diffServSchedulerId }
::= { diffServSchedulerTable 1 } ::= { diffServSchedulerTable 1 }
DiffServSchedulerEntry ::= SEQUENCE { DiffServSchedulerEntry ::= SEQUENCE {
diffServSchedulerId Unsigned32, diffServSchedulerId Unsigned32,
diffServSchedulerSucceedNext RowPointer, | diffServSchedulerNext RowPointer,
diffServSchedulerFailNext RowPointer, |
diffServSchedulerMethod OBJECT IDENTIFIER, diffServSchedulerMethod OBJECT IDENTIFIER,
diffServSchedulerSpecific StaticRowPointer, | diffServSchedulerSpecific RowPointer,
diffServSchedulerStatus RowStatus diffServSchedulerStatus RowStatus
} }
diffServSchedulerId OBJECT-TYPE diffServSchedulerId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the Scheduler entries. The set of such "An index that enumerates the Scheduler entries. The set of such
identifiers spans the whole agent. Managers should obtain new identifiers spans the whole agent. Managers should obtain new
values for row creation in this table by reading values for row creation in this table by reading
diffServSchedulerNextFree." diffServSchedulerNextFree."
::= { diffServSchedulerEntry 1 } ::= { diffServSchedulerEntry 1 }
diffServSchedulerSucceedNext OBJECT-TYPE | diffServSchedulerNext OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This selects the next diffserv functional datapath element to "This selects the next diffserv functional datapath element to
handle traffic for this data path. This RowPointer should point handle traffic for this data path. This RowPointer should point
to an instance of one of: to an instance of one of:
diffServSchedulerEntry diffServSchedulerEntry
diffServQEntry As indicated by [MODEL] section 7.1.4. diffServQEntry As indicated by [MODEL] section 7.1.4.
But this RowPointer can also point to an instance of: But this RowPointer can also point to an instance of:
diffServClfrEntry diffServClfrEntry
diffServMeterEntry diffServMeterEntry
diffServActionEntry diffServActionEntry
diffServAlgDropEntry For building of multiple TCBs for the same diffServAlgDropEntry For building of multiple TCBs for the same
data path. data path.
This should point to another diffServSchedulerEntry for This should point to another diffServSchedulerEntry for
implementation of multiple scheduler methods for the same implementation of multiple scheduler methods for the same data
datapath, and for implementation of hierarchical schedulers. path, and for implementation of hierarchical schedulers.
A value of zeroDotZero in this attribute indicates no further A value of zeroDotZero in this attribute indicates no further
Diffserv treatment is performed on traffic of this datapath. The Diffserv treatment is performed on traffic of this data path.
use of zeroDotZero is the normal usage for the last functional The use of zeroDotZero is the normal usage for the last
datapath element of the current data path. functional data path element of the current data path.
If the row pointed to does not exist, the treatment is as if this If the row pointed to does not exist, the treatment is as if this
attribute contains a value of zeroDotZero." | attribute contains a value of zeroDotZero."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 2 } ::= { diffServSchedulerEntry 2 }
diffServSchedulerFailNext OBJECT-TYPE |
SYNTAX RowPointer |
MAX-ACCESS read-create |
STATUS current |
DESCRIPTION |
"Used when the Scheduler functions as a multi-rate shaper, in |
non-work conserving manner. When the traffic does not conform to |
the leaky bucket parameter indicated by |
diffServSchedulerSchdParam, this selects the next diffserv |
functional datapath element to handle traffic for this data path. |
This RowPointer should point to an instance of one of: |
diffServSchedulerEntry |
diffServQEntry As indicated by [MODEL] section 7.1.4. |
But this RowPointer can also point to an instance of: |
diffServClfrEntry |
diffServMeterEntry |
diffServActionEntry |
diffServAlgDropEntry For building of multiple TCBs for the same |
data path. |
This should point to another diffServSchedulerEntry for |
implementation of multi-rate shaper. |
A value of zeroDotZero in this attribute indicates no further |
Diffserv treatment is performed on traffic of this datapath. The |
use of zeroDotZero is the normal usage for the last functional |
datapath element of the current data path. |
If the row pointed to does not exist, the treatment is as if this |
attribute contains a value of zeroDotZero." |
DEFVAL { zeroDotZero } |
::= { diffServSchedulerEntry 3 } |
diffServSchedulerMethod OBJECT-TYPE diffServSchedulerMethod OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scheduling algorithm used by this Scheduler. {0 0} "The scheduling algorithm used by this Scheduler. {0 0}
indicates this is unknown. Standard values for generic indicates this is unknown. Standard values for generic
algorithms: diffServSchedulerPriority, diffServSchedulerWRR, and algorithms: diffServSchedulerPriority, diffServSchedulerWRR,
diffServSchedulerWFQ are specified in this MIB; additional values diffServSchedulerWFQ, and diffServSchedulerShaper are specified
may be further specified in other MIBs." in this MIB; additional values may be further specified in other
MIBs."
REFERENCE REFERENCE
"[MODEL] section 7.1.2" "[MODEL] section 7.1.2"
::= { diffServSchedulerEntry 4 } | ::= { diffServSchedulerEntry 4 }
diffServSchedulerSpecific OBJECT-TYPE | diffServSchedulerSpecific OBJECT-TYPE
SYNTAX StaticRowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This StaticRowPointer indicates the entry in "This RowPointer indicates the entry in diffServRateControlTable
diffServSchdParamTable the higher level scheduler, pointed to by | which indicates the minimum and maximum rate of output from this
diffServSchedulerSucceedNext, should use to service the output of scheduler. This attribute is only used when there is more than
this scheduler. This attribute is only used when there is more one level of scheduler. It should have the value of zeroDotZero
than one level of scheduler. And should have the value of when not used."
zeroDotZero when not used."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServSchedulerEntry 5 } | ::= { diffServSchedulerEntry 5 }
diffServSchedulerStatus OBJECT-TYPE | diffServSchedulerStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or "The RowStatus variable controls the activation, deactivation, or
deletion of a queue. Any writable variable may be modified deletion of a scheduler. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServSchedulerEntry 6 } | ::= { diffServSchedulerEntry 6 }
--
-- Scheduling Parameter Table -- Scheduling Parameter Table
-- --
-- The scheduling parameters are separate from the Queue Entries -- The scheduling parameters are separate from the Queue Entries
-- for reusability and for usage by both queues and schedulers, -- for reusability and for usage by both queues and schedulers,
-- and this follows the separation of datapath elements from -- and this follows the separation of datapath elements from
-- parameterization approach used through out this MIB.
-- Usage of scheduling parameter table entry by schedulers allow -- Usage of scheduling parameter table entry by schedulers allow
-- building of hierarchical scheduling. -- building of hierarchical scheduling.
-- --
-- The diffServRateControlMaxRateAbs/Rel attributes are used to
-- construct non-work-conserving scheduler for the purpose of -- construct non-work-conserving scheduler for the purpose of
-- traffic shaping. These attributes limits the servicing of -- traffic shaping. These attributes limits the servicing of
-- the queue/scheduler, in affect, shaping the output of the -- the queue/scheduler, in affect, shaping the output of the
-- queue/scheduler, as described in [MODEL] section 7.2. -- queue/scheduler, as described in [MODEL] section 7.2.
-- --
diffServSchdParamNextFree OBJECT-TYPE diffServRateControlNextFree OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object yields a value when read that is currently unused "This object yields a value when read that is currently unused
for a diffServSchdParamId instance. If a configuring system for a diffServRateControlId instance. If a configuring system
attempts to create a new row in the diffServSchdParamTable using attempts to create a new row in the diffServRateControlTable
this value, that operation will fail if the value has, in the using this value, that operation will fail if the value has, in
meantime, been used to create another row that is currently the meantime, been used to create another row that is currently
valid." valid."
::= { diffServScheduler 3 } | ::= { diffServScheduler 3 }
diffServSchdParamTable OBJECT-TYPE diffServRateControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServSchdParamEntry SYNTAX SEQUENCE OF DiffServRateControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduling Parameter Table enumerates individual sets of "The Scheduling Parameter Table enumerates individual sets of
scheduling parameter that can be used/reused by Queues and scheduling parameter that can be used/reused by Queues and
Schedulers." Schedulers."
::= { diffServScheduler 4 } | ::= { diffServScheduler 4 }
diffServSchdParamEntry OBJECT-TYPE diffServRateControlEntry OBJECT-TYPE
SYNTAX DiffServSchdParamEntry SYNTAX DiffServRateControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Scheduling Parameter Table describes a single "An entry in the Scheduling Parameter Table describes a single
set of scheduling parameter for use by queues and schedulers. set of scheduling parameters for use by one or more queues or
schedulers."
Notice multiple inter-mixed of Queue and Scheduler entries can INDEX { diffServRateControlId }
use the same Scheduler Parameter entry." ::= { diffServRateControlTable 1 }
INDEX { diffServSchdParamId }
::= { diffServSchdParamTable 1 }
DiffServSchdParamEntry ::= SEQUENCE { DiffServRateControlEntry ::= SEQUENCE {
diffServSchdParamId Unsigned32, diffServRateControlId Unsigned32,
diffServSchdParamPriority Unsigned32, diffServRateControlPriority Unsigned32,
diffServSchdParamMinRateAbs Unsigned32, diffServRateControlMinRateAbs Unsigned32,
diffServSchdParamMinRateRel Unsigned32, diffServRateControlMinRateRel Unsigned32,
diffServSchdParamMaxRateAbs Unsigned32, diffServRateControlMaxRateAbs Unsigned32,
diffServSchdParamMaxRateRel Unsigned32, diffServRateControlMaxRateRel Unsigned32,
diffServSchdParamStatus RowStatus | diffServRateControlStatus RowStatus
} }
diffServSchdParamId OBJECT-TYPE diffServRateControlId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that enumerates the Scheduler Parameter entries. The "An index that enumerates the Scheduler Parameter entries. The
set of such identifiers spans the whole agent. Managers should set of such identifiers spans the whole agent. Managers should
obtain new values for row creation in this table by reading obtain new values for row creation in this table by reading
diffServSchdParamNextFree." diffServRateControlNextFree."
::= { diffServSchdParamEntry 1 } ::= { diffServRateControlEntry 1 }
diffServSchdParamPriority OBJECT-TYPE diffServRateControlPriority OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority of this input to the associated scheduler, relative | "The priority of this input to the associated scheduler, relative
to the scheduler's other inputs." to the scheduler's other inputs."
::= { diffServSchdParamEntry 2 } ::= { diffServRateControlEntry 2 }
diffServSchdParamMinRateAbs OBJECT-TYPE diffServRateControlMinRateAbs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum absolute rate, in kilobits/sec, that a downstream "The minimum absolute rate, in kilobits/sec, that a downstream
scheduler element should allocate to this queue. If the value is scheduler element should allocate to this queue. If the value is
zero, then there is effectively no minimum rate guarantee. If zero, then there is effectively no minimum rate guarantee. If
the value is non-zero, the scheduler will assure the servicing of the value is non-zero, the scheduler will assure the servicing of
this queue to at least this rate. this queue to at least this rate.
Note that this attribute's value is coupled to that of Note that this attribute's value is coupled to that of
diffServSchdParamMinRateRel: changes to one will affect the diffServRateControlMinRateRel: changes to one will affect the
value of the other. They are linked by the following equation: value of the other. They are linked by the following equation:
diffServSchdParamMinRateRel = diffServSchdParamMinRateAbs * 10,000,000/ifSpeed diffServRateControlMinRateRel =
diffServRateControlMinRateAbs * 10,000,000/ifSpeed
or, if appropriate: or, if appropriate:
diffServSchdParamMinRateRel = diffServSchdParamMinRateAbs * 10 / ifHighSpeed" diffServRateControlMinRateRel =
diffServRateControlMinRateAbs * 10 / ifHighSpeed"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { diffServSchdParamEntry 3 } ::= { diffServRateControlEntry 3 }
diffServSchdParamMinRateRel OBJECT-TYPE diffServRateControlMinRateRel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum rate that a downstream scheduler element should "The minimum rate that a downstream scheduler element should
allocate to this queue, relative to the maximum rate of the allocate to this queue, relative to the maximum rate of the
interface as reported by ifSpeed or ifHighSpeed, in units of interface as reported by ifSpeed or ifHighSpeed, in units of
1/10,000 of 1. If the value is zero, then there is effectively 1/10,000 of 1. If the value is zero, then there is effectively
no minimum rate guarantee. If the value is non-zero, the no minimum rate guarantee. If the value is non-zero, the
scheduler will assure the servicing of this queue to at least scheduler will assure the servicing of this queue to at least
this rate. this rate.
Note that this attribute's value is coupled to that of Note that this attribute's value is coupled to that of
diffServSchdParamMinRateAbs: changes to one will affect the diffServRateControlMinRateAbs: changes to one will affect the
value of the other. They are linked by the following equation: value of the other. They are linked by the following equation:
diffServSchdParamMinRateAbs = ifSpeed * diffServSchdParamMinRateRel/10,000,000 diffServRateControlMinRateAbs =
ifSpeed * diffServRateControlMinRateRel/10,000,000
or, if appropriate: or, if appropriate:
diffServSchdParamMinRateAbs = ifHighSpeed * diffServSchdParamMinRateRel / 10" diffServRateControlMinRateAbs =
ifHighSpeed * diffServRateControlMinRateRel / 10"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { diffServSchdParamEntry 4 } ::= { diffServRateControlEntry 4 }
diffServSchdParamMaxRateAbs OBJECT-TYPE diffServRateControlMaxRateAbs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate in kilobits/sec that a downstream scheduler "The maximum rate in kilobits/sec that a downstream scheduler
element should allocate to this queue. If the value is zero, then element should allocate to this queue. If the value is zero, then
there is effectively no maximum rate limit and that the scheduler there is effectively no maximum rate limit and that the scheduler
should attempt to be work-conserving for this queue. If the should attempt to be work-conserving for this queue. If the
value is non-zero, the scheduler will limit the servicing of this value is non-zero, the scheduler will limit the servicing of this
queue to, at most, this rate in a non-work-conserving manner. queue to, at most, this rate in a non-work-conserving manner.
Note that this attribute's value is coupled to that of Note that this attribute's value is coupled to that of
diffServSchdParamMaxRateRel: changes to one will affect the diffServRateControlMaxRateRel: changes to one will affect the
value of the other. They are linked by the following equation: value of the other. They are linked by the following equation:
diffServSchdParamMaxRateRel = diffServSchdParamMaxRateAbs * 10,000,000/ifSpeed diffServRateControlMaxRateRel =
diffServRateControlMaxRateAbs * 10,000,000/ifSpeed
or, if appropriate: or, if appropriate:
diffServSchdParamMaxRateRel = diffServSchdParamMaxRateAbs * 10 / ifHighSpeed" diffServRateControlMaxRateRel =
diffServRateControlMaxRateAbs * 10 / ifHighSpeed"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { diffServSchdParamEntry 5 } ::= { diffServRateControlEntry 5 }
diffServSchdParamMaxRateRel OBJECT-TYPE diffServRateControlMaxRateRel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate that a downstream scheduler element should "The maximum rate that a downstream scheduler element should
allocate to this queue, relative to the maximum rate of the allocate to this queue, relative to the maximum rate of the
interface as reported by ifSpeed or ifHighSpeed, in units of interface as reported by ifSpeed or ifHighSpeed, in units of
1/10,000 of 1. If the value is zero, then there is effectively 1/10,000 of 1. If the value is zero, then there is effectively
no maximum rate limit and the scheduler should attempt to be no maximum rate limit and the scheduler should attempt to be
work-conserving for this queue. If the value is non-zero, the work-conserving for this queue. If the value is non-zero, the
scheduler will limit the servicing of this queue to, at most, scheduler will limit the servicing of this queue to, at most,
this rate in a non-work-conserving manner. this rate in a non-work-conserving manner.
Note that this attribute's value is coupled to that of Note that this attribute's value is coupled to that of
diffServSchdParamMaxRateAbs: changes to one will affect the diffServRateControlMaxRateAbs: changes to one will affect the
value of the other. They are linked by the following equation: value of the other. They are linked by the following equation:
diffServSchdParamMaxRateAbs = ifSpeed * diffServSchdParamMaxRateRel/10,000,000 diffServRateControlMaxRateAbs =
ifSpeed * diffServRateControlMaxRateRel/10,000,000
or, if appropriate: or, if appropriate:
diffServSchdParamMaxRateAbs = ifHighSpeed * diffServSchdParamMaxRateRel / 10" diffServRateControlMaxRateAbs =
ifHighSpeed * diffServRateControlMaxRateRel / 10"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { diffServSchdParamEntry 6 } ::= { diffServRateControlEntry 6 }
diffServSchdParamStatus OBJECT-TYPE | diffServRateControlStatus OBJECT-TYPE
SYNTAX RowStatus | SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, deactivation, or | "The RowStatus variable controls the activation, deactivation, or
deletion of a queue. Any writable variable may be modified | deletion of a queue. Any writable variable may be modified
whether the row is active or notInService." whether the row is active or notInService."
::= { diffServSchdParamEntry 7 } ::= { diffServRateControlEntry 7 }
diffServSchedulerPriority OBJECT-IDENTITY | diffServSchedulerPriority OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For use with diffServSchedulerMethod to indicate Priority | "For use with diffServSchedulerMethod to indicate Priority
scheduling method, defined as an algorithm in which the presence | scheduling method, defined as an algorithm in which the presence
of data in a queue or set of queues absolutely precludes dequeue | of data in a queue or set of queues absolutely precludes dequeue
from another queue or set of queues. Notice attributes from | from another queue or set of queues. Notice attributes from
diffServSchdParamEntry of the queues/schedulers feeding this | diffServRateControlEntry of the queues/schedulers feeding this
scheduler are used when determining the next packet to schedule." scheduler are used when determining the next packet to schedule."
REFERENCE | REFERENCE
"[MODEL] section 7.1.2" | "[MODEL] section 7.1.2"
::= { diffServScheduler 5 } | ::= { diffServScheduler 5 }
diffServSchedulerWRR OBJECT-IDENTITY | diffServSchedulerWRR OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"For use with diffServSchedulerMethod to indicate Weighted Round | "For use with diffServSchedulerMethod to indicate Weighted Round
Robin scheduling method, defined as any algorithm in which a set | Robin scheduling method, defined as any algorithm in which a set
of queues are visited in a fixed order, and varying amounts of | of queues are visited in a fixed order, and varying amounts of
traffic are removed from each queue in turn to implement an | traffic are removed from each queue in turn to implement an
average output rate by class. Notice attributes from | average output rate by class. Notice attributes from
diffServSchdParamEntry of the queues/schedulers feeding this | diffServRateControlEntry of the queues/schedulers feeding this
scheduler are used when determining the next packet to schedule." | scheduler are used when determining the next packet to schedule."
REFERENCE | REFERENCE
"[MODEL] section 7.1.2" | "[MODEL] section 7.1.2"
::= { diffServScheduler 6 } | ::= { diffServScheduler 6 }
diffServSchedulerWFQ OBJECT-IDENTITY | diffServSchedulerWFQ OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"For use with diffServSchedulerMethod to indicate Weighted Fair | "For use with diffServSchedulerMethod to indicate Weighted Fair
Queueing scheduling method, defined as any algorithm in which a | Queuing scheduling method, defined as any algorithm in which a
set of queues are conceptually visited in some order, to | set of queues are conceptually visited in some order, to
implement an average output rate by class. Notice attributes | implement an average output rate by class. Notice attributes
from diffServSchdParamEntry of the queues/schedulers feeding this | from diffServRateControlEntry of the queues/schedulers feeding
scheduler are used when determining the next packet to schedule." | this scheduler are used when determining the next packet to
REFERENCE | schedule."
"[MODEL] section 7.1.2" | REFERENCE
::= { diffServScheduler 7 } | "[MODEL] section 7.1.2"
::= { diffServScheduler 7 }
diffServSchedulerShaper OBJECT-IDENTITY | diffServSchedulerShaper OBJECT-IDENTITY
STATUS current | STATUS current
DESCRIPTION | DESCRIPTION
"For use with diffServSchedulerMethod to indicate the | "For use with diffServSchedulerMethod to indicate the
diffServSchedulerEntry is being used to describe a Shaper. The | diffServSchedulerEntry is being used to describe a Shaper. The
diffServSchedulerSpecific attribute for a Shaper will point to an | diffServSchedulerSpecific attribute for a Shaper will point to an
entry in the diffServTBParamTable for the shaper's Leaky Bucket | entry in the diffServTBParamTable for the shaper's Leaky Bucket
parameters. Notice multi-rate, multi-color shapers can be | parameters."
parameterized by use of diffServSchedulerSucceedNext and | REFERENCE
diffServSchedulerFailNext the same way multi-rate, multi-color | "[MODEL] section 7.1.2"
meters are parameterized with diffServMeterSucceedNext and | ::= { diffServScheduler 8 }
diffServMeterFailNext parameters." |
REFERENCE |
"[MODEL] section 7.1.2" |
::= { diffServScheduler 8 } |
-- --
-- MIB Compliance statements. -- MIB Compliance statements.
-- --
diffServMIBCompliances OBJECT IDENTIFIER ::= { diffServMIBConformance 1 } diffServMIBCompliances OBJECT IDENTIFIER ::= { diffServMIBConformance 1 }
diffServMIBGroups OBJECT IDENTIFIER ::= { diffServMIBConformance 2 } diffServMIBGroups OBJECT IDENTIFIER ::= { diffServMIBConformance 2 }
diffServMIBCompliance MODULE-COMPLIANCE diffServMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This MIB may be implemented as a read-only or as a read-create "This MIB may be implemented as a read-only or as a read-create
MIB. As a result, it may be used for monitoring or for MIB. As a result, it may be used for monitoring or for
configuration." configuration."
MODULE -- This Module MODULE -- This Module
MANDATORY-GROUPS { MANDATORY-GROUPS {
diffServMIBDataPathGroup, diffServMIBDataPathGroup,
diffServMIBClfrGroup, diffServMIBClfrGroup,
diffServMIBClfrElementGroup, diffServMIBClfrElementGroup,
diffServMIBSixTupleClfrGroup, diffServMIBSixTupleClfrGroup,
diffServMIBActionGroup, | diffServMIBActionGroup,
diffServMIBAlgDropGroup, diffServMIBAlgDropGroup,
diffServMIBQGroup, diffServMIBSchedulerGroup, diffServMIBQGroup, diffServMIBSchedulerGroup,
diffServMIBSchdParamGroup } diffServMIBSchdParamGroup }
-- The groups: -- The groups:
-- diffServMIBCounterGroup -- diffServMIBCounterGroup
-- diffServMIBHCCounterGroup -- diffServMIBHCCounterGroup
-- diffServMIBVHCCounterGroup -- diffServMIBVHCCounterGroup
-- --
-- are mutually exclusive; at most one of these groups is implemented -- are mutually exclusive; at most one of these groups is implemented
skipping to change at page 84, line 32 skipping to change at page 80, line 18
DESCRIPTION DESCRIPTION
"This group is mandatory for table objects indexed by ifIndex for "This group is mandatory for table objects indexed by ifIndex for
which the value of the corresponding instance of ifSpeed is which the value of the corresponding instance of ifSpeed is
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP diffServMIBMeterGroup GROUP diffServMIBMeterGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement metering "This group is mandatory for devices that implement metering
functions." functions."
GROUP diffServMIBTBParamGroup | GROUP diffServMIBTBParamGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement token-bucket "This group is mandatory for devices that implement token-bucket
metering functions." metering functions."
GROUP diffServMIBDscpMarkActGroup GROUP diffServMIBDscpMarkActGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement DSCP-Marking "This group is mandatory for devices that implement DSCP-Marking
functions." functions."
GROUP diffServMIBRandomDropGroup GROUP diffServMIBRandomDropGroup
skipping to change at page 85, line 16 skipping to change at page 80, line 43
GROUP diffServMIBStaticGroup GROUP diffServMIBStaticGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that allow creation of rows "This group is mandatory for devices that allow creation of rows
in any of the writable tables of this MIB." in any of the writable tables of this MIB."
OBJECT diffServClfrStatus OBJECT diffServClfrStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServClfrElementPrecedence | OBJECT diffServClfrElementPrecedence
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServClfrElementNext OBJECT diffServClfrElementNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServClfrElementSpecific OBJECT diffServClfrElementSpecific
skipping to change at page 86, line 7 skipping to change at page 81, line 27
OBJECT diffServSixTupleClfrDstAddrType OBJECT diffServSixTupleClfrDstAddrType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrDstAddr OBJECT diffServSixTupleClfrDstAddr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrDstAddrMask OBJECT diffServSixTupleClfrDstPrefixLength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrSrcAddrType OBJECT diffServSixTupleClfrSrcAddrType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrSrcAddr OBJECT diffServSixTupleClfrSrcAddr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrSrcAddrMask OBJECT diffServSixTupleClfrSrcPrefixLength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrDscp OBJECT diffServSixTupleClfrDscp
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrProtocol OBJECT diffServSixTupleClfrProtocol
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSixTupleClfrSrcL4PortMin OBJECT diffServSixTupleClfrSrcL4PortMin
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 88, line 4 skipping to change at page 83, line 6
OBJECT diffServMeterSpecific OBJECT diffServMeterSpecific
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServMeterStatus OBJECT diffServMeterStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBParamType |
OBJECT diffServTBParamType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBParamRate | OBJECT diffServTBParamRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBParamBurstSize | OBJECT diffServTBParamBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBParamInterval | OBJECT diffServTBParamInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBParamStatus | OBJECT diffServTBParamStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionNext OBJECT diffServActionNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionSpecific OBJECT diffServActionSpecific
skipping to change at page 90, line 24 skipping to change at page 85, line 12
OBJECT diffServRandomDropMaxThreshBytes OBJECT diffServRandomDropMaxThreshBytes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServRandomDropMaxThreshPkts OBJECT diffServRandomDropMaxThreshPkts
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServRandomDropInvProbMax OBJECT diffServRandomDropProbMax
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServRandomDropInvWeight OBJECT diffServRandomDropInvWeight
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServRandomDropSamplingRate OBJECT diffServRandomDropSamplingRate
skipping to change at page 91, line 19 skipping to change at page 85, line 47
OBJECT diffServQSchdParam OBJECT diffServQSchdParam
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQStatus OBJECT diffServQStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchedulerSucceedNext | OBJECT diffServSchedulerNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchedulerMethod
OBJECT diffServSchedulerFailNext |
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchedulerMethod | OBJECT diffServSchedulerSpecific
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchedulerSchdParam | OBJECT diffServSchedulerStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchedulerStatus | OBJECT diffServRateControlPriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchdParamPriority |
OBJECT diffServRateControlMinRateAbs
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchdParamMinRateAbs | OBJECT diffServRateControlMinRateRel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchdParamMinRateRel | OBJECT diffServRateControlMaxRateAbs
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchdParamTBParam | OBJECT diffServRateControlMaxRateRel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServSchdParamStatus * OBJECT diffServRateControlStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { diffServMIBCompliances 1 } ::= { diffServMIBCompliances 1 }
diffServMIBDataPathGroup OBJECT-GROUP | diffServMIBDataPathGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServDataPathStart, diffServDataPathStatus diffServDataPathStart, diffServDataPathStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Data Path Group defines the MIB Objects that describe a data "The Data Path Group defines the MIB Objects that describe a data
path." path."
::= { diffServMIBGroups 1 } ::= { diffServMIBGroups 1 }
diffServMIBClfrGroup OBJECT-GROUP diffServMIBClfrGroup OBJECT-GROUP
skipping to change at page 93, line 13 skipping to change at page 87, line 27
diffServClfrStatus diffServClfrStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Classifier Group defines the MIB Objects that describe a "The Classifier Group defines the MIB Objects that describe a
generic classifier." generic classifier."
::= { diffServMIBGroups 2 } ::= { diffServMIBGroups 2 }
diffServMIBClfrElementGroup OBJECT-GROUP diffServMIBClfrElementGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClfrElementPrecedence, diffServClfrElementNext, | diffServClfrElementPrecedence, diffServClfrElementNext,
diffServClfrElementSpecific, diffServClfrElementStatus diffServClfrElementSpecific, diffServClfrElementStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Classifier Element Group defines the MIB Objects that "The Classifier Element Group defines the MIB Objects that
describe the classifier elements that make up a generic describe the classifier elements that make up a generic
classifier." classifier."
::= { diffServMIBGroups 3 } ::= { diffServMIBGroups 3 }
diffServMIBSixTupleClfrGroup OBJECT-GROUP diffServMIBSixTupleClfrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServSixTupleClfrDstAddrType, diffServSixTupleClfrDstAddr, diffServSixTupleClfrDstAddrType, diffServSixTupleClfrDstAddr,
diffServSixTupleClfrDstAddrMask, diffServSixTupleClfrDstPrefixLength,
diffServSixTupleClfrSrcAddrType, diffServSixTupleClfrSrcAddr, diffServSixTupleClfrSrcAddrType, diffServSixTupleClfrSrcAddr,
diffServSixTupleClfrSrcAddrMask, diffServSixTupleClfrSrcPrefixLength, diffServSixTupleClfrDscp,
diffServSixTupleClfrDscp, diffServSixTupleClfrProtocol, diffServSixTupleClfrProtocol, diffServSixTupleClfrDstL4PortMin,
diffServSixTupleClfrDstL4PortMin,
diffServSixTupleClfrDstL4PortMax, diffServSixTupleClfrDstL4PortMax,
diffServSixTupleClfrSrcL4PortMin, diffServSixTupleClfrSrcL4PortMin,
diffServSixTupleClfrSrcL4PortMax, diffServSixTupleClfrSrcL4PortMax, diffServSixTupleClfrStatus
diffServSixTupleClfrStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Six-tuple Classifier Group defines the MIB Objects that "The Six-tuple Classifier Group defines the MIB Objects that
describe a classifier element for matching on 6 fields of an IP describe a classifier element for matching on 6 fields of an IP
and upper-layer protocol header." and upper-layer protocol header."
::= { diffServMIBGroups 4 } ::= { diffServMIBGroups 4 }
diffServMIBMeterGroup OBJECT-GROUP diffServMIBMeterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServMeterSucceedNext, diffServMeterFailNext, diffServMeterSucceedNext, diffServMeterFailNext,
diffServMeterSpecific, diffServMeterStatus diffServMeterSpecific, diffServMeterStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Meter Group defines the objects used in describing a generic "The Meter Group defines the objects used in describing a generic
meter element." meter element."
::= { diffServMIBGroups 5 } ::= { diffServMIBGroups 5 }
diffServMIBTBParamGroup OBJECT-GROUP | diffServMIBTBParamGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServTBParamType, | diffServTBParamType, diffServTBParamRate,
diffServTBParamRate, diffServTBParamBurstSize, | diffServTBParamBurstSize, diffServTBParamInterval,
diffServTBParamInterval, diffServTBParamStatus | diffServTBParamStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Token-Bucket Meter Group defines the objects used in "The Token-Bucket Meter Group defines the objects used in
describing a token bucket meter element." describing a token bucket meter element."
::= { diffServMIBGroups 6 } ::= { diffServMIBGroups 6 }
diffServMIBActionGroup OBJECT-GROUP diffServMIBActionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServActionNext, diffServActionSpecific, diffServActionNext, diffServActionSpecific,
skipping to change at page 94, line 45 skipping to change at page 89, line 7
diffServDscpMarkActDscp diffServDscpMarkActDscp
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DSCP Mark Action Group defines the objects used in "The DSCP Mark Action Group defines the objects used in
describing a DSCP Marking Action element." describing a DSCP Marking Action element."
::= { diffServMIBGroups 8 } ::= { diffServMIBGroups 8 }
diffServMIBCounterGroup OBJECT-GROUP diffServMIBCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClfrElementPkts, | diffServCountActOctets, diffServCountActPkts,
diffServCountActOctets, diffServCountActDiscontTime, diffServCountActStatus,
diffServCountActPkts, diffServAlgDropOctets, diffServAlgDropPkts
diffServCountActDiscontTime,
diffServCountActStatus,
diffServAlgDropOctets,
diffServAlgDropPkts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information specific to non- "A collection of objects providing information specific to non-
high speed (non-high speed interfaces transmit and receive at high speed (non-high speed interfaces transmit and receive at
speeds less than or equal to 20,000,000 bits/second) packet- speeds less than or equal to 20,000,000 bits/second) packet-
oriented network interfaces." oriented network interfaces."
::= { diffServMIBGroups 9 } ::= { diffServMIBGroups 9 }
diffServMIBHCCounterGroup OBJECT-GROUP diffServMIBHCCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClfrElementPkts, |
diffServCountActOctets, diffServCountActHCOctets, diffServCountActOctets, diffServCountActHCOctets,
diffServCountActPkts, diffServCountActPkts, diffServCountActDiscontTime,
diffServCountActDiscontTime, diffServCountActStatus, diffServAlgDropOctets,
diffServCountActStatus, diffServAlgDropHCOctets, diffServAlgDropPkts
diffServAlgDropOctets, diffServAlgDropHCOctets,
diffServAlgDropPkts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information specific to high "A collection of objects providing information specific to high
speed (high speed interfaces transmit and receive at speeds speed (high speed interfaces transmit and receive at speeds
greater than 20,000,000 but less than or equals to 650,000,000 greater than 20,000,000 but less than or equals to 650,000,000
bits/second) packet-oriented network interfaces." bits/second) packet-oriented network interfaces."
::= { diffServMIBGroups 10 } ::= { diffServMIBGroups 10 }
diffServMIBVHCCounterGroup OBJECT-GROUP diffServMIBVHCCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClfrElementPkts, diffServClfrElementHCPkts, |
diffServCountActOctets, diffServCountActHCOctets, diffServCountActOctets, diffServCountActHCOctets,
diffServCountActPkts, diffServCountActHCPkts, diffServCountActPkts, diffServCountActHCPkts,
diffServCountActDiscontTime, diffServCountActDiscontTime, diffServCountActStatus,
diffServCountActStatus,
diffServAlgDropOctets, diffServAlgDropHCOctets, diffServAlgDropOctets, diffServAlgDropHCOctets,
diffServAlgDropPkts, diffServAlgDropHCPkts diffServAlgDropPkts, diffServAlgDropHCPkts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information specific to very- "A collection of objects providing information specific to very-
high speed (very-high speed interfaces transmit and receive at high speed (very-high speed interfaces transmit and receive at
speeds greater than 650,000,000 bits/second) packet-oriented speeds greater than 650,000,000 bits/second) packet-oriented
network interfaces." network interfaces."
::= { diffServMIBGroups 11 } ::= { diffServMIBGroups 11 }
skipping to change at page 96, line 27 skipping to change at page 90, line 20
"The Algorithmic Drop Group contains the objects that describe "The Algorithmic Drop Group contains the objects that describe
algorithmic dropper operation and configuration." algorithmic dropper operation and configuration."
::= { diffServMIBGroups 12 } ::= { diffServMIBGroups 12 }
diffServMIBRandomDropGroup OBJECT-GROUP diffServMIBRandomDropGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServRandomDropMinThreshBytes, diffServRandomDropMinThreshBytes,
diffServRandomDropMinThreshPkts, diffServRandomDropMinThreshPkts,
diffServRandomDropMaxThreshBytes, diffServRandomDropMaxThreshBytes,
diffServRandomDropMaxThreshPkts, diffServRandomDropMaxThreshPkts,
diffServRandomDropInvProbMax, diffServRandomDropProbMax,
diffServRandomDropInvWeight, diffServRandomDropInvWeight,
diffServRandomDropSamplingRate, diffServRandomDropSamplingRate,
diffServRandomDropStatus diffServRandomDropStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group for "The Random Drop Group augments the Algorithmic Drop Group for
random dropper operation and configuration." random dropper operation and configuration."
::= { diffServMIBGroups 13 } ::= { diffServMIBGroups 13 }
diffServMIBQGroup OBJECT-GROUP diffServMIBQGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServQNext, diffServQSchdParam, diffServQNext, diffServQSchdParam, diffServQStatus
diffServQStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Queue Group contains the objects that describe an "The Queue Group contains the objects that describe an
interface's queues." interface's queues."
::= { diffServMIBGroups 14 } ::= { diffServMIBGroups 14 }
diffServMIBSchedulerGroup OBJECT-GROUP diffServMIBSchedulerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServSchedulerSucceedNext, diffServSchedulerFailNext, | diffServSchedulerNext, diffServSchedulerMethod,
diffServSchedulerMethod, diffServSchedulerSchdParam, | diffServSchedulerSpecific, diffServSchedulerStatus
diffServSchedulerStatus |
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduler Group contains the objects that describe packet "The Scheduler Group contains the objects that describe packet
schedulers on interfaces." schedulers on interfaces."
::= { diffServMIBGroups 15 } ::= { diffServMIBGroups 15 }
diffServMIBSchdParamGroup OBJECT-GROUP diffServMIBSchdParamGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServSchdParamPriority, diffServRateControlPriority, diffServRateControlMinRateAbs,
diffServSchdParamMinRateAbs, diffServSchdParamMinRateRel, diffServRateControlMinRateRel, diffServRateControlMaxRateAbs,
diffServSchdParamTBParam, diffServSchdParamStatus | diffServRateControlMaxRateRel, diffServRateControlStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduler Parameter Group contains the objects that describe "The Scheduler Parameter Group contains the objects that describe
packet schedulers' parameters on interfaces." packet schedulers' parameters on interfaces."
::= { diffServMIBGroups 16 } ::= { diffServMIBGroups 16 }
diffServMIBStaticGroup OBJECT-GROUP diffServMIBStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClfrNextFree, diffServClfrElementNextFree, diffServClfrNextFree, diffServClfrElementNextFree,
diffServSixTupleClfrNextFree, diffServSixTupleClfrNextFree,
diffServMeterNextFree, diffServTBParamNextFree, | diffServMeterNextFree, diffServTBParamNextFree,
diffServActionNextFree, diffServCountActNextFree, diffServActionNextFree, diffServCountActNextFree,
diffServAlgDropNextFree, diffServRandomDropNextFree, diffServAlgDropNextFree, diffServRandomDropNextFree,
diffServQNextFree, diffServSchedulerNextFree, diffServQNextFree, diffServSchedulerNextFree,
diffServSchdParamNextFree diffServRateControlNextFree
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Static Group contains readable scalar objects used in "The Static Group contains readable scalar objects used in
creating unique identifiers for classifiers, meters, actions and creating unique identifiers for classifiers, meters, actions and
queues. These are required whenever row creation operations on queues. These are required whenever row creation operations on
such tables are supported." such tables are supported."
::= { diffServMIBGroups 17 } ::= { diffServMIBGroups 17 }
END END
8. Acknowledgments 8. Acknowledgments
This MIB builds on all the work that has gone into the Informal This MIB builds on all the work that has gone into the Informal
Management Model for Diffserv Routers, Diffserv PIB, and Diffserv Policy | Management Model for Diffserv Routers, Diffserv PIB, and Diffserv Policy
MIB (SNMPCONF WG). It has been developed with the active involvement of MIB (SNMPCONF WG). It has been developed with the active involvement of
many people, but most notably Yoram Bernet, Steve Blake, Brian many people, but most notably Yoram Bernet, Steve Blake, Brian
Carpenter, Dave Durham, Michael Fine, Victor Firoiu, Jeremy Greene, Dan | Carpenter, Dave Durham, Michael Fine, Victor Firoiu, Jeremy Greene, Dan
Grossman, Roch Guerin, Scott Hahn, Joel Halpern, Harrie Hazewinkel, Van | Grossman, Roch Guerin, Scott Hahn, Joel Halpern, Harrie Hazewinkel, Van
Jacobsen, Keith McCloghrie, Bob Moore, Kathleen Nichols, Ping Pan, Nabil Jacobsen, Keith McCloghrie, Bob Moore, Kathleen Nichols, Ping Pan, Nabil
Seddigh, John Seligson, Walter Weiss, and Bert Wijnen. | Seddigh, John Seligson, Walter Weiss, and Bert Wijnen.
9. Security Considerations 9. Security Considerations
It is clear that this MIB is potentially useful for configuration, and It is clear that this MIB is potentially useful for configuration, and
anything that can be configured can be misconfigured, with potentially anything that can be configured can be misconfigured, with potentially
disastrous effect. disastrous effect.
At this writing, no security holes have been identified beyond those At this writing, no security holes have been identified beyond those
that SNMP Security is itself intended to address. These relate primarily that SNMP Security is itself intended to address. These relate primarily
to controlled access to sensitive information and the ability to to controlled access to sensitive information and the ability to
skipping to change at page 103, line 4 skipping to change at page 96, line 41
W. Fang, N. Seddigh, B. Nandy "A Time Sliding Window Three Colour W. Fang, N. Seddigh, B. Nandy "A Time Sliding Window Three Colour
Marker", RFC 2859, June 2000. Marker", RFC 2859, June 2000.
11. Authors' Addresses 11. Authors' Addresses
Fred Baker Fred Baker
Cisco Systems Cisco Systems
519 Lado Drive 519 Lado Drive
Santa Barbara, California 93111 Santa Barbara, California 93111
fred@cisco.com fred@cisco.com
Kwok Ho Chan Kwok Ho Chan
Nortel Networks Nortel Networks
600 Technology Park Drive 600 Technology Park Drive
Billerica, MA 01821 Billerica, MA 01821
khchan@nortelnetworks.com khchan@nortelnetworks.com
Andrew Smith Andrew Smith
Allegro Networks Allegro Networks
6399 San Ignacio Ave 6399 San Ignacio Ave
San Jose, CA 95119 San Jose, CA 95119
andrew@allegronetworks.com andrew@allegronetworks.com
Table of Contents Table of Contents
1 The SNMP Management Framework ................................... 2 1 The SNMP Management Framework ................................... 2
2 Introduction .................................................... 4 2 Introduction .................................................... 3
2.1 Relationship to the Informal Management Model for Diffserv 2.1 Relationship to the Informal Management Model for Diffserv
Router ....................................................... 4 Router ....................................................... 3
2.2 Relationship to other MIBs and Policy Management .............. 5 2.2 Relationship to other MIBs and Policy Management .............. 4
2.3 MIB Overview .................................................. 5 2.3 MIB Overview .................................................. 4
3 Structure of this MIB ........................................... 6 3 Structure of this MIB ........................................... 5
3.1 Diffserv Data Paths ........................................... 7 3.1 Diffserv Data Paths ........................................... 6
3.1.1 Data Path Table ............................................. 7 3.1.1 Data Path Table ............................................. 6
3.2 Classifiers ................................................... 7 3.2 Classifiers ................................................... 6
3.2.1 Classifier Table ............................................ 9 3.2.1 Classifier Table ............................................ 8
3.2.2 Classifier Element Table .................................... 9 3.2.2 Classifier Element Table .................................... 8
3.2.3 Filter Table - IP Six-Tuple Classifier Table ................ 9 3.2.3 Filter Table - IP Six-Tuple Classifier Table ................ 8
3.3 Meters ........................................................ 9 3.3 Meters ........................................................ 8
3.3.1 Meter Table ................................................. 10 3.3.1 Meter Table ................................................. 9
3.3.2 Token-Bucket Meter Table .................................... 10 3.3.2 Token-Bucket Meter Table .................................... 9
3.4 Actions ....................................................... 10 3.4 Actions ....................................................... 9
3.4.1 DSCP Mark Action Table ...................................... 11 3.4.1 DSCP Mark Action Table ...................................... 10
3.4.2 Count Action Table .......................................... 11 3.4.2 Count Action Table .......................................... 10
3.4.3 Absolute Drop Action ........................................ 11 3.4.3 Absolute Drop Action ........................................ 10
3.5 Queuing Elements .............................................. 11 3.5 Queuing Elements .............................................. 10
3.5.1 Algorithmic Dropper Table ................................... 11 3.5.1 Algorithmic Dropper Table ................................... 10
3.5.2 Random Dropper Table ........................................ 13 3.5.2 Random Dropper Table ........................................ 12
3.5.3 Queues and Schedulers ....................................... 14 3.5.3 Queues and Schedulers ....................................... 13
4 MIB Usage Example ............................................... 16 4 MIB Usage Example ............................................... 15
4.1 Model's Example ............................................... 16 4.1 Model's Example ............................................... 15
4.2 Additional Data Path Example .................................. 19 4.2 Additional Data Path Example .................................. 18
4.2.1 Data Path and Classifier Example Discussion ................. 19 4.2.1 Data Path and Classifier Example Discussion ................. 18
4.2.2 Meter and Action Example Discussion ......................... 22 4.2.2 Meter and Action Example Discussion ......................... 21
4.2.3 Queue and Scheduler Example Discussion ...................... 21
5 Conventions used in this MIB .................................... 22
5.1 The use of RowPointer to indicate data path linkage ........... 22
5.2 The use of RowPointer to indicate parameters .................. 23
5.3 Conceptual row creation and deletion .......................... 23
6 Extending this MIB .............................................. 24
7 MIB Definition .................................................. 25
8 Acknowledgments ................................................. 92
9 Security Considerations ......................................... 92
4.2.3 Queue and Scheduler Example Discussion ...................... 22 10 References ..................................................... 93
5 Conventions used in this MIB .................................... 23 11 Authors' Addresses ............................................. 96
5.1 The use of RowPointer ......................................... 23
5.2 The use of StaticRowPointer ................................... 24
5.3 Conceptual row creation and deletion .......................... 24
6 Extending this MIB .............................................. 25
7 MIB Definition .................................................. 26
8 Acknowledgments ................................................. 98
9 Security Considerations ......................................... 98
10 References ..................................................... 99
11 Authors' Addresses ............................................. 102
12. Full Copyright 12. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it | others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
 End of changes. 348 change blocks. 
1378 lines changed or deleted 1252 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/