[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [iesg-secretary #5004] Request to publish the attach memo as an Internet Draft
Your request #5004 was resolved by jhargest:
We received your request, and this version is currently in the
system.
>>>>>>>>>>>>>>>>>> Original Message >>>>>>>>>>>>>>>>>>
>From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
>To: "'internet-drafts@ietf.org'" <internet-drafts@ietf.org>
>Subject: Request to publish the attach memo as an Internet Draft
> -----Original Message-----
> From: Choudhury, Sanjaya
> Sent: Thursday, December 12, 2002 5:21 PM
> To: 'internet-drafts@ietf.org'
> Cc: '; 'swallow@cisco.com';
> 'loa.andersson@utfors.se'
> Subject: Request to publish the attach memo as an Internet Draft
>
> Hi! I will appreciate if you can publish the attached memo
> as an Internet Draft.
>
> Title : Diff-Serv-aware MPLS Traffic
> Engineering Network
> Management Information Base Using SMIv2
> Author(s) : Thomas D. Nadeau , Sanjaya Choudhury
> Filename : draft-nadeau-mpls-dste-mib-00.txt
> Pages : 35
> Date : 2002-12-12
> Why MPLS-WG : This MIB is an extension of the
> MPLS-TE-MIB (and LSR-MIB)
> being developed in the MPLS WG
> Thanks,
> sanjay
>
> <<draft-nadeau-mpls-dste-mib-00.txt>>
------_=_NextPart_000_01C2BB5C.530B4CB0
Content-Type: text/plain;
name="draft-nadeau-mpls-dste-mib-00.txt"
Content-Disposition: attachment;
filename="draft-nadeau-mpls-dste-mib-00.txt"
Content-Transfer-Encoding: quoted-printable
Thomas D. Nadeau =0A=
Cisco Systems, =
Inc. =0A=
=0A=
Sanjaya Choudhury =0A=
Marconi Communications =0A=
=0A=
=0A=
=0A=
=0A=
IETF Internet Draft =0A=
Expires: June, 2003 =0A=
Document: draft-nadeau-mpls-dste-mib-00.txt December, =
2002 =0A=
=0A=
=0A=
=0A=
Diff-Serv-aware MPLS Traffic Engineering Network =0A=
Management Information Base Using SMIv2 =0A=
=0A=
=0A=
=0A=
=0A=
Status of this Memo =0A=
=0A=
This document is an Internet-Draft and is in full conformance with all =
=0A=
provisions of Section 10 of RFC2026. Internet-Drafts are Working =0A=
documents of the Internet Engineering Task Force (IETF), its areas, and =
=0A=
its working groups. Note that other groups may also distribute working =
=0A=
documents as Internet-Drafts. =0A=
=0A=
Internet-Drafts are draft documents valid for a maximum of six months =
=0A=
and may be updated, replaced, or obsoleted by other documents at any =
=0A=
time. It is inappropriate to use Internet-Drafts as reference material =
=0A=
or to cite them other than as "work in progress." =0A=
=0A=
The list of current Internet-Drafts can be accessed at =0A=
http://www.ietf.org/ietf/1id-abstracts.txt. =0A=
The list of Internet-Draft Shadow Directories can be accessed at =0A=
http://www.ietf.org/shadow.html. =0A=
=0A=
Abstract =0A=
=0A=
This memo defines a portion of the Management Information Base (MIB) =
for =0A=
use with network management protocols in the Internet community. In =
=0A=
particular, it describes managed objects for modeling and managing =0A=
Diff-Serv-aware MPLS Traffic Engineering [DSTE-REQ][DSTE-PROTO]. =0A=
=0A=
Table of Contents =0A=
=0A=
1.0 INTRODUCTION...........................................2 =0A=
2.0 TERMINOLOGY............................................3 =0A=
3.0 THE SNMP MANAGEMENT FRAMEWORK..........................3 =0A=
3.1 OBJECT DEFINITIONS.....................................4 =0A=
4.0 FEATURE CHECKLIST......................................4 =0A=
5.0 OUTLINE................................................4 =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
1]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
5.1 SUMMARY OF MPLS-DS-TE-MIB..............................5=0A=
5.2 Design Rational........................................6=0A=
6.0 DSTE-MIB Usage.........................................6=0A=
6.1 Configuring Bandwidth Constraint Model.................6 =0A=
6.2 Configuring the TE-Class Mapping.......................7 =0A=
6.2.1 Effect of an empty TE-Class Map........................8=0A=
6.3 Configuring Bandwidth Constraints......................8 =0A=
6.4 Configuring the Bandwidth Overbooking..................9 =0A=
6.5 Configuring DSTE MPLS Tunnels..........................9 =0A=
6.6 Configurations to support interoperability with (non-DS) TE =0A=
6.7 Configuring DSTE LSR to behave like a TE LSR...........10=0A=
7.0 Usage Example..........................................11=0A=
7.1 Scenario1: Configurations to handle voice and data.....11=0A=
7.2 Scenario2: One CT for each DiffServ Class .............13=0A=
8.0 MPLS-DS-TE-MIB DEFINITIONS.............................15 =0A=
9.0 ACKNOWLEDGMENTS........................................32 =0A=
10.0 REFERENCES.............................................32 =0A=
11.0 AUTHORS' ADDRESSES.....................................35 =0A=
12.0 FULL COPYRIGHT STATEMENT...............................36 =0A=
=0A=
1.0 Introduction =0A=
=0A=
This memo defines an experimental portion of the Management Information =
=0A=
Base (MIB) for use with network management protocols in the Internet =
=0A=
community. In particular,it describes managed objects for managing=0A=
Diff-Serv-aware MPLS Traffic Engineering [DSTE-REQ][DSTE-PROTO]. =0A=
=0A=
[DSTE-PROTO] specifies the IGP and signaling extensions to support the =
=0A=
Diff-Serv-aware Traffic Engineering (DSTE), as per the requirements =0A=
outlined in [DSTE-REQ]. In addition, it also presents the =
configurations =0A=
needed to support DSTE on a LSR. The MIB Module defined in this =
document =0A=
can be used to perform these configurations. =0A=
=0A=
This version of the DSTE-MIB, is based on version-05 of [DSTE-REQ] =
and=0A=
version-01 of [DSTE-PROTO].=0A=
=0A=
Although the proposed MIB is not tightly coupled to any specific =
Bandwidth=0A=
Constraint Models, the examples are primarily based on the Russian =
Doll=0A=
Bandwidth Constraint Model. In future, once the alternative =
Bandwidth=0A=
Constraint Models are finalized, this MIB will be updated to =
accommodate=0A=
them. =0A=
=0A=
=0A=
Comments should be made directly to the MPLS mailing list at =0A=
mpls@uu.net. =0A=
=0A=
This memo does not, in its draft form, specify a standard for the =0A=
Internet community. =0A=
=0A=
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
2]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this =
=0A=
document are to be interpreted as described in RFC 2119, =0A=
reference [BCP14]. =0A=
=0A=
2.0 Terminology =0A=
=0A=
This document uses terminology from the document describing the MPLS =
=0A=
architecture [MPLSArch] and from the documents describing =0A=
Diff-Serv-Aware Traffic Engineering [DSTE-REQ] [DSTE-PROTO]. Some of =
the =0A=
frequently used abbreviations are presented below for reference. =0A=
=0A=
DSTE Refers to Diff-Serv-aware Traffic Engineering. =0A=
CT Refers to to Class-Type =0A=
Priority Refers to (setup/holding) preemption priority. =0A=
TE-Class Refers to TE-Class =0A=
BC Refers to Bandwidth Constraints =0A=
LOM Refers to Local Overbooking Multiplier =0A=
RDBC Refers to Russian Doll Bandwidth Constraint Model=0A=
=0A=
3.0 The SNMP Management Framework =0A=
=0A=
The SNMP Management Framework presently consists of five major =0A=
components: =0A=
=0A=
- An overall architecture, described in RFC 2271 [SNMPArch]. =0A=
=0A=
- Mechanisms for describing and naming objects and events for the =0A=
purpose of management. The first version of this Structure of =0A=
Management Information (SMI) is called SMIv1 and described in RFC =
=0A=
1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. =
=0A=
The second version, called SMIv2, is described in RFC 1902 [SMIv2], =
=0A=
RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. =0A=
=0A=
- Message protocols for transferring management information. The first =
=0A=
version of the SNMP message protocol is called SNMPv1 and described =
=0A=
in RFC 1157 [SNMPv1]. A second version of the SNMP message =
protocol, =0A=
which is not an Internet standards track protocol, is called SNMPv2c =
=0A=
and described in RFC 1901 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The =
=0A=
third version of the message protocol is called SNMPv3 and described =
=0A=
in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 =
[SNMPv3USM]. =0A=
=0A=
- Protocol operations for accessing management information. The first =
=0A=
set of protocol one-readable information in SMIv2 will be converted =
=0A=
into textual descriptions in SMIv1 during the translation process. =
=0A=
However, this loss of machine-readable information is not considered =
=0A=
to change the semantics of the MIB. =0A=
=0A=
3.1 Object Definitions =0A=
Managed objects are accessed via a virtual information store, termed =
the =0A=
Management Information Base or MIB. Objects in the MIB are defined =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
3]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
using the subset of Abstract Syntax Notation One (ASN.1) defined in the =
=0A=
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, =
=0A=
an administratively assigned name. The object type together with an =0A=
object instance serves to uniquely identify a specific instantiation of =
=0A=
the object. For human convenience, we often use a textual string, =0A=
termed the descriptor, to also refer to the object type. =0A=
=0A=
4.0 Feature Checklist =0A=
=0A=
The Diff-Serv-aware Traffic Engineering MIB (DS-TE-MIB) is designed to =
=0A=
satisfy the following requirements and constraints: =0A=
=0A=
- The MIB must support the requirements set forth by Requirements for =
=0A=
support of Diff-Serv-aware MPLS Traffic Engineering[DSTE-REQ]. =0A=
=0A=
- The MIB must support the IGP and signaling extensions set forth by =
=0A=
Protocol extensions for support of Diff-Serv-aware MPLS Traffic =0A=
Engineering [DSTE-PROTO] =0A=
=0A=
- The MIB must support both configuration and monitoring of the =0A=
Diff-Serv-Aware TE features. =0A=
=0A=
5.0 Outline =0A=
=0A=
In order to deploy Diff-Serv-aware Traffic Engineering, the domain =0A=
administrator needs to perform several per-LSR, per-LINK and per-LSP =
=0A=
configurations, as presented in [DSTE-PROTO]. These steps can =
summarized =0A=
as follows: =0A=
=0A=
- Configure the Bandwidth Constraint Model to be used by the LSR. =0A=
=0A=
- Define up to 8 TE-Classes using Class-Types supported in the LSR =
and =0A=
the preemption levels within these Class-Types. =0A=
=0A=
- Configure Bandwidth Constraints on the MPLS interfaces existing =
in=0A=
the LSR. =0A=
=0A=
- If bandwidth overbooking (or underbooking) is desired, configure =
the =0A=
Local Overbooking Multiplier(LOM) for the individual MPLS =
interfaces =0A=
on a per Class-Type basis. =0A=
=0A=
- On ingress DSTE LSRs, setup MPLS tunnels with appropriate =0A=
Class-Types. =0A=
=0A=
Besides the above mentioned configurations, the administrator may also =
=0A=
need to perform other (non Diff-Serv) TE related configurations as =0A=
described in the [OSPF-TE] and [ISIS-TE]. These (non-DS)TE =
configurations =0A=
are beyond the scope of this document and are not addressed in =
DSTE-MIB.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
4]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
5.1 Summary of DSTE-MIB =0A=
=0A=
The MIB object for performing the above mentioned DSTE related =0A=
configurations consists of following tables 6 tables: =0A=
=0A=
- Per-LSR Configurations group: =0A=
=0A=
(1) TE-Class Map table (mplsDsTeClassTable) allows user to define =
=0A=
TE-Classes from Class-Type and preemption priority supported =
=0A=
within these Class-Types. =0A=
=0A=
- Per-Interface Configuration group: =0A=
=0A=
(1) Bandwidth Constraint Table (mplsDsTeIfBCTable) can be used to =
=0A=
define the different bandwidth constraints on a MPLS interface. =
=0A=
=0A=
(2) Local Overbooking Multiplier Table (mplsDsTeIfLOMTable) allows =
=0A=
user to define the overbooking (and underbooking) factors for =0A=
different Class-Types on a per interface (MPLS interface) basis. =0A=
=0A=
(3) Unreserved Bandwidth Table (mplsDsTeIfUnresBwTable) enables the =
=0A=
user to monitor the unreserved bandwidth for different =0A=
TE-Classes on a per interface basis. =0A=
=0A=
- Per-LSP Configuration group: =0A=
=0A=
(1) DS-TE Tunnel Table (mplsDsTeTunTable) extends the =0A=
mplsTunnelTable [MPLS-TE-MIB] to allow the user to configure =
the =0A=
Class-Type associated with Traffic Engineered MPLS tunnels. =
=0A=
=0A=
(2) DS-TE LSP Table (mplsDsTeLspTable) extends the [LSR-MIB] to =0A=
allow user to monitor the DS-TE related attributes associated =
=0A=
with LSPs. =0A=
=0A=
Besides these MIB tables, the DSTE-MIB also defines few Scalar MIB =0A=
variables to allow the administrator to configure the BC model to be =
=0A=
used by the DSTE LSR, when supported.=0A=
=0A=
=0A=
5.2 Design Rational=0A=
=0A=
In order to simplify the implementation and minimize the number of =
row=0A=
creations, we have used the following strategies:=0A=
=0A=
(i) We have chosen to re-use some the existing MPLS MIBs by=0A=
using the AUGMENTs SNMP construct, instead of defining a new table=0A=
with similar index. Example: mplsDsTeIfBCTable AUGMENTS the=0A=
mplsInterfaceConfTable defined in [LSR-MIB]=0A=
=0A=
(ii) We have chosen to use columns to represent the possible BCs=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
5]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
and LOMs, instead of creating rows for each of these=0A=
values. Example: The mplsDsTeIfBCTable defines 8 columns to=0A=
represent the 8 possible bandwidth constraints (BC0-BC7).=0A=
=0A=
=0A=
6.0 DSTE-MIB Usage =0A=
=0A=
This section briefly describes, the usage of the DSTE-MIB in several =
=0A=
common configuration scenarios. =0A=
=0A=
6.1 Configuring Bandwidth Constraint Model =0A=
=0A=
The [DSTE-PROTO] allows the administrator to choose the BC Model =
suitable=0A=
for his DSTE domain.=0A=
=0A=
The domain administrator can configure the BC Model to be used by a =
LSR,=0A=
using the mplsDSTeBwConstraintModel MIB variable. By default, this =
MIB=0A=
variable, is initialized to 0 (Russian Doll Bandwidth Constraint=0A=
Model). =0A=
=0A=
Usage of different Bandwidth Constraint Models will have effect on =
other=0A=
MIB tables, namely the Bandwidth Constraint Table (mplsDsTeIfBCTable) =
=0A=
and Local Overbooking Multiplier Table (mplsDsTeIfLOMTable). For =
example,=0A=
if RDBC Model is used, the LSR will be expected to enforce the =
following =0A=
rules: =0A=
=0A=
-mplsDsTeIfBCTable =0A=
(i) mplsDsTeIfBCjMaxBw <=3D mplsDsTeIfBCiMaxBw,=0A=
where i < j=0A=
=0A=
-mplsDsTeIfLOMTable =0A=
(i) mplsDsTeIfBCjMaxBw * mplsDsTeIfLOMCTj <=3D =0A=
mplsDsTeIfBCiMaxBw * mplsDsTeIfLOMCti =0A=
where i < j=0A=
=0A=
Different BC Models may have different relations between the BCs and =
=0A=
CTs. This relation for the RDBC Model, is presented in the section 9.1 =
=0A=
of [DSTE-PROTO]. Enforcing the relation between the CTs and BCs are =0A=
beyond the scope of the MIB and left to the DSTE implementations. =0A=
=0A=
Since the currently defined BC Models, work with the BCs that represent =
=0A=
an upper limit of bandwidth usage, the mplsDsTeIfBCTable defined in =
this=0A=
MIB, allows administrator to configure only the upper limit associated =
with =0A=
the bandwidth constraints. For example, mplsDsTeIfBC1MaxBw =
represents=0A=
the maximum reservable bandwidth for BC1.=0A=
=0A=
In future, if a new BC Model, needs to more configurable parameters, =
the=0A=
mplsDsTeIfBCTable should be extended to support it. =0A=
=0A=
6.2 Configuring the TE-Class Mapping =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
6]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
=0A=
The DSTE-MIB allows the user to configure up to 8 TE-Classes, by =
creating =0A=
one row for each TE-Class, in the mplsDsTeClassTable. User can define =
=0A=
any number of TE-Classes in any order. However, as per the =0A=
[DSTE-PROTO], the DSTE-MIB agents will be expected to ensure that all =
=0A=
the rows in this table are unique. i.e two rows can not have same value =
=0A=
for both mplsDsTeClassType and mplsDsTeClassPriority =0A=
=0A=
Creating a row in the mplsDsTeClassTable, activates/enables the =0A=
specified Class-Type and has following effects on the other MIB tables. =
=0A=
=0A=
-mplsDsTeIfBCTable =0A=
Based on the BC Model being used, only a subset of the BCs =0A=
defined in the mplsDsTeIfBCTable will be of significance =0A=
=0A=
For example: =0A=
If Russian Doll BC is configured and the following rows =0A=
are defined- TE-Class Class-Type Priority Description=0A=
0 0 0 gold-high=0A=
1 0 7 gold-low =0A=
2 1 0 platinum-high=0A=
3 1 7 platinum-low =0A=
Only the mplsDsTeIfBC0MaxBw and mplsDsTeIfBC1MaxBw defined in=0A=
the mplsDsTeIfBCTable will be of significance (rest of=0A=
the BC values are ignored, if present). =0A=
=0A=
-mplsDsTeIfLOMentry=0A=
Since this table allows the configuration of LOM on a per =0A=
Class-Type basis, mplsDsTeIfLOMCTj of mplsDsTeIfLOMTable will be =
=0A=
of significance, is only if the corresponding CT[i] appears in=0A=
one of the rows in the mplsDsTeClassTable. =0A=
=0A=
Besides the above mentioned effect on the DSTE-MIB tables, =0A=
addition/removal/modification of the definition of TE-Classes may have =
=0A=
significant effect on the processing of the signaling and IGP =0A=
procedures. To handle these, different MIB implementations might force =
=0A=
the administrator to take additional implementation specific actions. =
=0A=
=0A=
While configuring the TE-Class mapping, the administrator should ensure =
that =0A=
all the LSRs in the DSTE domain have the same entries in the=0A=
mplsDsTeClassTable [as per the requirement defined in the section 3.2.1 =
of=0A=
DSTE-PROTO] .=0A=
=0A=
6.2.1 Effect of an empty TE-Class Map=0A=
=0A=
When the TE-Class Map is empty, DSTE and TE are effectively disabled in =
the=0A=
LSR. Although the IGP advertisement will continue, no LSPs (DSTE or TE) =
can =0A=
be established on the LSR. This configuration of the =
mplsDsTeClassTable,=0A=
has the following effect on other MIB tables:=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
7]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
--mplsDsTeIfBCTable=0A=
Since no Class-Types are active on the LSR, all the bandwidth=0A=
constraints configured in this table are of no significance (and=0A=
should be ignored from DSTE/TE prospective).=0A=
=0A=
--mplsDsTeIfLOMTable=0A=
Since no Class-Types are active on the LSR, all the per-interface=0A=
per-CT overbooking multipliers configured in this table are of no=0A=
significance (and should be ignored from DSTE/TE prospective).=0A=
=0A=
--mplsDsTeIfUnresBwTable=0A=
Since no Class-Types are active on the LSR, all the per-interface=0A=
per-TE-Class unreserved bandwidth values will be set to 0.=0A=
=0A=
=0A=
6.3 Configuring Bandwidth Constraints =0A=
=0A=
The DSTE-MIB, allows the administrator to configure up to 8 bandwidth =
=0A=
constraints per MPLS interface, through the use of the=0A=
mplsDsTeIfBCTable. =0A=
=0A=
When the administrator creates a MPLS interface on the LSR, the =0A=
mplsInterfaceConfTable [LSR-MIB] will get populated with an entry=0A=
corresponding to the interface.=0A=
=0A=
When DSTE is supported on the LSR, creation of a row in the=0A=
mplsInterfaceConfTable, also initializes all the fields of the=0A=
mplsDsTeIfBCTable, which AUGMENTS it. This relationship exists because =
each=0A=
MPLS-enabled interface must participate in DS-TE.=0A=
=0A=
By default, the BC0 is initialized to the link bandwidth and rest of =
the=0A=
BCs are initialized to 0. The administrator can later modify these BCs =
to=0A=
appropriate values. =0A=
=0A=
When a MPLS interface is created on a DSTE LSR and BCs are =
associated=0A=
with it, the the following relation to the mplsInterfaceConfTable=0A=
[LSR-MIB] can be expected: =0A=
=0A=
mplsInterfaceConfTotalBandwidth of [LSR-MIB] =3D=3D=0A=
mplsDsTeIfBC0MaxBw of [DSTE-MIB]=0A=
=0A=
Although the bandwidth constraints and TE-Classes can be defined=0A=
independent of each other, the BCs associated with the MPLS =
interfaces=0A=
are of significance only when the corresponding Class-Type is defined =
in=0A=
the TE-Class table. =0A=
=0A=
Similarly, when a row corresponding to a new Class-Type is added to =
the=0A=
TE-Class table, the administrator is expected to configures =
appropriate=0A=
BCs for that Class-Type on different MPLS interfaces of the LSR. =0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
8]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
This MIB tables represents the BCs in Kbps.=0A=
=0A=
6.4 Configuring the Bandwidth Overbooking =0A=
=0A=
[DSTE-PROTO] allows user to configure a bandwidth overbooking factor on =
=0A=
a per Class-Type, per-Interface basis. The DSTE-MIB, supports this =0A=
through the mplsDsTeIfLOMTable. =0A=
=0A=
By default, the MIB defines the LOM for different Class-Types to be =
100% =0A=
(i.e no overbooking). The domain administrator can modify these default =
=0A=
values to specify the desired overbooking factor. In line with the =0A=
[DSTE-PROTO], the mplsDsTeIfLOMTable, assumes the following: =0A=
-A value between 0 and 100 is consider to be underbooking =0A=
-A value of 100 implies no overbooking =0A=
-A value larger that 100 is consider to be overbooking. =0A=
=0A=
Modification of the the LOM will be reflected in the per TE-Class =0A=
unreserved bandwidth table (mplsDsTeIfUnresBwTable). =0A=
=0A=
6.5 Configuring DSTE MPLS Tunnels =0A=
=0A=
The [DSTE-PROTO] draft, expects the DSTE MPLS Tunnels to be associated =
=0A=
with a Class-Type. This MIB, extends the mplsTunnelTable specified in =
=0A=
the [MPLS-TE-MIB], by defining the mplsDsTeTunTable. =0A=
=0A=
The mplsDsTeTunTable AUGMENTs the mplsTunnelTable and allows user to=0A=
specify a Class-Type associated with a tunnel. If no CT is specified =
a=0A=
value of 0 (CT0) will be assumed.[If an LSP is associated with=0A=
class-type 0, the CLASSTYPE TLV is not signalled. DSTE-PROTO Appendix =
A,=0A=
Section 3]=0A=
=0A=
While originating a DSTE MPLS Tunnel, if the administrator specifies =
a=0A=
Class-Type, that has no entries in the mplsDsTeClassTable, the entry=0A=
will remain in operationally down state. Similarly, when all the =
entries=0A=
corresponding to a Class-Type is removed from the =
mplsDsTeClassTable,=0A=
all the tunnels using that Class-Type will become operationally =
down.=0A=
=0A=
The class-type associated with a tunnel instance can not be modified, =
when=0A=
it is operationally up.=0A=
=0A=
=0A=
6.6 Configurations to support interoperability with (non-DS) TE =0A=
=0A=
In order to deploy the DSTE LSR in a hybrid network (with DSTE LSRs and =
=0A=
non-DSTE LSRs), the administrator needs to configure the TE-Class Map =
as =0A=
per the guideline in outlined in the Appendix G of =0A=
[DSTE-PROTO]. =0A=
=0A=
Specifically, when using the DSTE-MIB, the user is expected to create =
=0A=
one row for CT0 for every preemption priority actually used in the TE =
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
9]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
domain, such that the mplsDsTeClassIndex =3D=3D mplsDsTeClassPriority. =
=0A=
=0A=
For example, if the TE domain uses preemption priority 2 and 3, then =
the =0A=
administrator must configure the following: =0A=
=0A=
In mplsDsTeClassTable: =0A=
{ =0A=
mplsDsTeClassIndex =3D 2 --TE-Class Index =0A=
mplsDsTeClassType =3D 0 --CT0 =0A=
mplsDsTePriority =3D 2 --Setup/Holding priority=0A=
mplsDsTeClassDescription =3D "Legacy-2" --Description of =
TE-Class 2=0A=
mplsDsTeClassRowStatus =3D createAndGo =0A=
} =0A=
=0A=
In mplsDsTeClassTable: =0A=
{ =0A=
mplsDsTeClassIndex =3D 3 --TE-Class Index =0A=
mplsDsTeClassType =3D 0 --CT0 =0A=
mplsDsTePriority =3D 3 --Setup/Holding priority=0A=
mplsDsTeClassDescription =3D "Legacy-3" --Description of =
TE-Class 3=0A=
mplsDsTeClassRowStatus =3D createAndGo =0A=
} =0A=
=0A=
=0A=
6.7 Configuring DSTE LSR to behave like a TE LSR=0A=
=0A=
Section 8 of [DSTE-PROTO] indicates that the existing TE can viewed as =
a=0A=
particular case of DSTE. This section describes, how we can use the =
DSTE=0A=
MIB to configure a DSTE LSR as an TE LSR.=0A=
=0A=
In mplsDsTeClassTable: Create one row for each priority of CT0=0A=
{ =0A=
mplsDsTeClassIndex =3D idx --for idx =3D 0 .. 7 =0A=
mplsDsTeClassType =3D 0 --Only CT0 supported=0A=
mplsDsTePrioritype =3D pri --for pri =3D 0 .. 7=0A=
mplsDsTeClassDescription =3D description --description of TE classes =
=0A=
}=0A=
=0A=
In mplsDsTeIfBCTable: For each MPLS interface=0A=
{=0A=
mplsDsTeIfBC0MaxBw =3D linkbw --Maximum link bw =0A=
mplsDsTeIfBC1MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC2MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC3MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC4MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC5MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC6MaxBw =3D 0 --Not used=0A=
mplsDsTeIfBC7MaxBw =3D 0 --Not used=0A=
}=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
10]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
In mplsDsTeIfLOMTable: For each MPLS interface=0A=
{=0A=
mplsDsTeIfLOM0 =3D 100 --No overbooking used=0A=
mplsDsTeIfLOM1 =3D 100 --Not used=0A=
mplsDsTeIfLOM2 =3D 100 --Not used=0A=
mplsDsTeIfLOM3 =3D 100 --Not used=0A=
mplsDsTeIfLOM4 =3D 100 --Not used=0A=
mplsDsTeIfLOM5 =3D 100 --Not used=0A=
mplsDsTeIfLOM6 =3D 100 --Not used=0A=
mplsDsTeIfLOM7 =3D 100 --Not used=0A=
}=0A=
=0A=
Since in this configuration, only CT0 is supported, any tunnels =
using=0A=
Class-Type other than CT0 will remain in operationally down state.=0A=
=0A=
The DSTE-MIB is defined in way to come up with the above =
configuration=0A=
by default.=0A=
=0A=
If the administrator wishes to make a fully configured DSTE LSR behave =
like=0A=
a TE LSR, he can simply modify the TE-Class table (mplsDsTeClassTable) =
as=0A=
shown above. Although, the per interface configurations like BCs and =
LOMs=0A=
will remain configured, only the fields corresponding to the CT0 will =
be of=0A=
significance. Similarly, all the per tunnel configurations will =
remain=0A=
configured, but only the tunnels using CT0 will be remain =
operationally=0A=
up. Individual implementations might impose additional constraints on =
such=0A=
transformations (DSTE->TE->DSTE). =0A=
=0A=
7.0 Usage Example =0A=
=0A=
To clarify the usage of the DSTE-MIB presented further, this section =
=0A=
presents few example configurations. For our illustration, let us =
assume =0A=
that we are configuring a DSTE-LSR, with two MPLS interfaces. We also =
=0A=
assume that Russian Doll Bandwidth Constraint Model is suitable for our =
=0A=
applications. =0A=
=0A=
7.1 Scenario1: Configurations to handle voice and data traffic=0A=
=0A=
Consider the scenario described in section 3.4.1 of [DSTE-PROTO], where =
=0A=
the administrator wants to use two Class-Types, one for Voice (CT1) and =
=0A=
one for Data (CT0) in his network. However, he does not want the Voice =
=0A=
LSPs to preempted by the Data LSPs. =0A=
=0A=
(i) Configure the TE-Class Map =0A=
=0A=
In mplsDsTeClassTable: =0A=
{ =0A=
mplsDsTeClassIndex =3D0 --TE-Class index =0A=
mplsDsTeClassType =3D1 --CT1 (for Voice) =0A=
mplsDsTeClassPriority =3D0 --Preemption priority=0A=
mplsDsTeClassDescription =3D"Voice" --TE-Class description =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
11]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
mplsDsTeClassRowStatus =3DcreateAndGo(4) =0A=
} =0A=
In mplsDsTeClassTable: =0A=
{ =0A=
mplsDsTeClassIndex =3D1 --TE-Class index =0A=
mplsDsTeClassType =3D0 --CT0 (for Data) =0A=
mplsDsTeClassPriority =3D1 --Preemption priority=0A=
mplsDsTeClassDescription =3D"Data" --TE-Class description =0A=
mplsDsTeClassRowStatus =3DcreateAndGo(4) =0A=
} =0A=
=0A=
(ii) Configure the BCs =0A=
=0A=
since the mplsDsTeIfBCTable, AUGMENTS the mplsInterfaceConfTable,=0A=
two rows (corresponding to the two interfaces) are already created with =
=0A=
default values. In our example, the user only needs to modify the=0A=
bandwidth constraint for CT1 (i.e BC1 ). =0A=
=0A=
In mplsDsTeIfBCTable: for nplsDsTeIfConfIndex =3D 1 =0A=
{=0A=
mplsDsTeIfBC0MaxBw =3D 155 --Max link bandwidth 155Kbps=0A=
mplsDsTeIfBC1MaxBw =3D 50 --Limit the CT1 to 50Kbps=0A=
mplsDsTeIfBC2MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC3MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC4MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC5MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC6MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC7MaxBw =3D 0 --unused =0A=
} =0A=
=0A=
In mplsDsTeIfBCTable: for nplsDsTeIfConfIndex =3D 2 =0A=
{ =0A=
mplsDsTeIfBC0MaxBw =3D 155 --Max link bandwidth 155Kbps=0A=
mplsDsTeIfBC1MaxBw =3D 30 --Limit the CT1 to 30Kbps=0A=
mplsDsTeIfBC2MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC3MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC4MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC5MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC6MaxBw =3D 0 --unused =0A=
mplsDsTeIfBC7MaxBw =3D 0 --unused =0A=
} =0A=
=0A=
(iii) Configure two tunnels=0A=
=0A=
First create a Voice tunnel:=0A=
=0A=
In mplsTunnelTable:MPLS-TE-MIB=0A=
{=0A=
mplsTunnelIndex =3D1=0A=
mplsTunnelInstance =3D1=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
12]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
mplsTunnelIngressLSRId =3D123.123.125.1=0A=
mplsTunnelEgressLSRId =3D123.123.125.10=0A=
mplsTunnelName =3D"Voice Tunnel-1"=0A=
mplsTunnelSetupPrio =3D0=0A=
mplsTunnelHoldingPrio =3D0 =0A=
...=0A=
} =0A=
In mplsDsTeTunTable:DSTE-MIB[Indices {1 =
,1,123.123.125.1,123.123.125.10} =0A=
{ =0A=
mplsDsTeTunClassType =3D1 -Class-Type 1 (Voice) =0A=
} =0A=
=0A=
Now create a Data tunnel:=0A=
=0A=
In mplsTunnelTable:MPLS-TE-MIB=0A=
{=0A=
mplsTunnelIndex =3D2=0A=
mplsTunnelInstance =3D2=0A=
mplsTunnelIngressLSRId =3D123.123.125.1=0A=
mplsTunnelEgressLSRId =3D123.123.125.10=0A=
mplsTunnelName =3D"Data Tunnel-1"=0A=
mplsTunnelSetupPrio =3D1=0A=
mplsTunnelHoldingPrio =3D1 =0A=
...=0A=
} =0A=
In mplsDsTeTunTable:DSTE-MIB[Indices {2 =
,2,123.123.125.1,123.123.125.10} =0A=
{ =0A=
mplsDsTeTunClassType =3D0 -Class-Type 0 (Data) =0A=
} =0A=
=0A=
=0A=
7.2 Scenario2: One CT for each DiffServ Class =0A=
=0A=
Consider the scenario described in section 7.1 of [BW-ACCT], where =0A=
the administrator wants to map each preemption priority to a =
DiffServ=0A=
Class, while allowing multiple priorities to same class. Example, as=0A=
stated in [BW-ACCT]:=0A=
Priority grade=0A=
0 premium voice=0A=
1 premium assured=0A=
2 standard voice=0A=
3 standard assured=0A=
4 gold data=0A=
5 silver data=0A=
6 bronze data=0A=
7 best effort=0A=
=0A=
(i) Configure the TE-Class Map =0A=
=0A=
In mplsDsTeClassTable: [Create 8 Class-Types one for each priority]=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
13]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
{ =0A=
mplsDsTeClassIndex =3Didx --for idx =3D 0 .. 7=0A=
mplsDsTeClassType =3Dc --for c =3D 7 .. 0 [CT7 =3D p voice] =0A=
mplsDsTeClassPriority =3Dpri --for pri =3D 0 .. 7=0A=
mplsDsTeClassDescription=3Ddescription --grade:premium voice,...=0A=
mplsDsTeClassRowStatus =3DcreateAndGo(4) =0A=
} =0A=
=0A=
(ii) Configure the BCs =0A=
=0A=
since the mplsDsTeIfBCTable, AUGMENTS the mplsInterfaceConfTable,=0A=
two rows (corresponding to the two interfaces) are already created with =
=0A=
default values. In our example, the user only needs to modify the =0A=
bandwidth constraint for all the 8 Class-Types.=0A=
=0A=
In mplsDsTeIfConfBCTable: for nplsDsTeIfConfIndex =3D 1 =0A=
{=0A=
mplsDsTeIfBC0MaxBw =3D 155 --CT7 Best effort=0A=
mplsDsTeIfBC1MaxBw =3D 135 --CT1 bronze data=0A=
mplsDsTeIfBC2MaxBw =3D 125 --CT2 silver data=0A=
mplsDsTeIfBC3MaxBw =3D 105 --CT3 gold data=0A=
mplsDsTeIfBC4MaxBw =3D 85 --CT4 standard assured=0A=
mplsDsTeIfBC5MaxBw =3D 65 --CT5 standard voice=0A=
mplsDsTeIfBC6MaxBw =3D 45 --CT6 premium assured=0A=
mplsDsTeIfBC7MaxBw =3D 30 --CT7 premium voice=0A=
} =0A=
=0A=
In mplsDsTeIfBCTable: for nplsDsTeIfConfIndex =3D 2 =0A=
{=0A=
mplsDsTeIfBC0MaxBw =3D 155 --CT7 Best effort=0A=
mplsDsTeIfBC1MaxBw =3D 135 --CT1 bronze data=0A=
mplsDsTeIfBC2MaxBw =3D 125 --CT2 silver data=0A=
mplsDsTeIfBC3MaxBw =3D 105 --CT3 gold data=0A=
mplsDsTeIfBC4MaxBw =3D 85 --CT4 standard assured=0A=
mplsDsTeIfBC5MaxBw =3D 65 --CT5 standard voice=0A=
mplsDsTeIfBC6MaxBw =3D 45 --CT6 premium assured=0A=
mplsDsTeIfBC7MaxBw =3D 30 --CT7 premium voice=0A=
} =0A=
=0A=
(iii) Configure a gold data tunnel=0A=
=0A=
In mplsTunnelTable:MPLS-TE-MIB=0A=
{=0A=
mplsTunnelIndex =3D1=0A=
mplsTunnelInstance =3D1=0A=
mplsTunnelIngressLSRId =3D123.123.125.1=0A=
mplsTunnelEgressLSRId =3D123.123.125.10=0A=
mplsTunnelName =3D"Gold Data Tunnel-1"=0A=
mplsTunnelSetupPrio =3D4=0A=
mplsTunnelHoldingPrio =3D4 =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
14]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
...=0A=
} =0A=
In mplsDsTeTunTable:DSTE-MIB[Indices {1 =
,1,123.123.125.1,123.123.125.10} =0A=
{ =0A=
mplsDsTeTunClassType =3D3 -Class-Type 3 (Gold Data)) =0A=
} =0A=
=0A=
=0A=
8.0 MPLS-DS-TE-MIB Definitions =0A=
=0A=
MPLS-DSTE-MIB DEFINITIONS ::=3D BEGIN =0A=
=0A=
IMPORTS =0A=
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,=0A=
Unsigned32=0A=
FROM SNMPv2-SMI=0A=
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP=0A=
FROM SNMPv2-CONF=0A=
TruthValue, RowStatus, StorageType,DisplayString=0A=
FROM SNMPv2-TC=0A=
mplsMIB, MplsBitRate=0A=
FROM MPLS-TC-MIB=0A=
mplsInterfaceConfEntry, mplsXCEntry=0A=
FROM MPLS-LSR-MIB=0A=
mplsTunnelEntry=0A=
FROM MPLS-TE-MIB=0A=
=0A=
; =0A=
=0A=
mplsDsTeMIB MODULE-IDENTITY =0A=
LAST-UPDATED "200212121200Z" -- 12 December 2002 12:00:00 EST =0A=
ORGANIZATION "Internet Engineering Task Force." =0A=
=0A=
CONTACT-INFO =0A=
" Thomas D. Nadeau =0A=
Postal: Cisco Systems, Inc. =0A=
250 Apollo Drive =0A=
Chelmsford, MA 01824 =0A=
USA =0A=
Tel: +1-978-244-3051 =0A=
Email: tnadeau@cisco.com =0A=
=0A=
Sanjaya Choudhury =0A=
Postal: Marconi =0A=
1000 Marconi Drive, =0A=
Warrendale, PA 158 =0A=
Tel: +1-724-742-6720 =0A=
Email: sanjaya.choudhury@marconi.com =0A=
=0A=
General Discussion and Questions: mpls@uu.net =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
15]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
" =0A=
=0A=
=0A=
DESCRIPTION =0A=
"This MIB contains managed object definitions for =0A=
Diff-Serv-aware MPLS Traffic Engineering as described in =0A=
[DSTE-REQ][DSTE-PROTO]." =0A=
=0A=
-- Revision history. =0A=
=0A=
REVISION =0A=
"200212121200Z" -- 12 December 2002 12:00:00 EST =0A=
DESCRIPTION =0A=
"Updated draft to reflect the changes in the DiffServ =0A=
Traffic Engineering drafts, namely version-05 of [DSTE-REQ] =0A=
and version-01 of [DSTE-PROTO]" =0A=
=0A=
REVISION =0A=
"200107181200Z" -- 18 July 2001 12:00:00 EST =0A=
DESCRIPTION =0A=
"Updated draft to keep alive." =0A=
=0A=
REVISION =0A=
"200102151200Z" -- 15 February 2001 12:00:00 EST =0A=
DESCRIPTION =0A=
"Initial draft version." =0A=
::=3D { mplsMIB 8 } -- Temporary=0A=
=0A=
=0A=
-- Top level components of this MIB. =0A=
=0A=
mplsDsTeObjects OBJECT IDENTIFIER ::=3D { mplsDsTeMIB 1 } =0A=
mplsDsTeScalarObjects OBJECT IDENTIFIER ::=3D { mplsDsTeObjects 1 } =0A=
mplsDsTeNotifications OBJECT IDENTIFIER ::=3D { mplsDsTeMIB 2 } =0A=
mplsDsTeConformance OBJECT IDENTIFIER ::=3D { mplsDsTeMIB 3 } =0A=
=0A=
=0A=
-- Scalars =0A=
=0A=
mplsDsTeBwConstraintModel OBJECT-TYPE =0A=
SYNTAX INTEGER(0..127) =0A=
--Russian Doll Bandwidth Constraint Model(0) =0A=
--Reserved for specification by TEWG(1-127) =0A=
MAX-ACCESS read-write =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Bandwidth Constraint Model currently in use by this LSR. =0A=
The bandwidth constraint model used by LSRs in a single =0A=
DS-TE domain, must be same. =0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
16]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
As per the specification of the [DSTE-REQ] draft, the value =0A=
of the bandwidth constraint model specified in this variable =
=0A=
will determine the relationship between the Class-Types and =0A=
Bandwidth Bandwidth Constraint (defined else where in this =0A=
MIB)."=0A=
=0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeScalarObjects 1 } =0A=
=0A=
=0A=
-- DS TE Interface Bandwidth Constraint Table =0A=
=0A=
mplsDsTeIfBCTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeIfBCEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This table specifies bandwidth constraints associated with =
DS-TE =0A=
enabled interfaces. This table AUGMENTS the=0A=
mplsInterfaceConfTable [LSR-MIB]." =0A=
::=3D { mplsDsTeObjects 3 } =0A=
=0A=
mplsDsTeIfBCEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeIfBCEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"A row is created in this table automatically by an LSR for =
every=0A=
interface capable of supporting MPLS DS-TE if this MIB is=0A=
implemented. This relationship exists because each =
MPLS-enabled=0A=
interface must participate in DS-TE. Therefore, this table =0A=
AUGMENTS corresponding entries in the =
mplsInterfaceConfTable.=0A=
=0A=
Each entry in this table corresponds specified the bandwidth =
=0A=
constraint associated with the corresponding MPLS interface, in=0A=
Kbps. [However, if the mplsInterfaceConfTable has a conceptual=0A=
row with index 0, all of the bandwidth constraints corresponding=0A=
to that row will be no significance and will can not be modified]=0A=
=0A=
By default, all the bandwidth constraint other than BC0 is set=0A=
to 0 Kbps. The BC0 by default is set to the maximum link=0A=
bandwidth. =0A=
=0A=
Bandwidth constraints defined in this table are significant only =
if=0A=
the corresponding Class-Type is defined in the=0A=
mplsDsTeClassTable. Furthermore, the relationship of the=0A=
Class-Types with the bandwidth constraints defined in this table is=0A=
determined by the Bandwidth Constraint Model indicated in=0A=
mplsDsTeBandwidthConstraintModel.=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
17]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
For example:=0A=
If the Russian Doll Bandwidth Constraint Model is used then the=0A=
LSR must ensure that BCi is configured smaller or equal to BCj,=0A=
where i is greater than j, for all significant BCs. =0A=
=0A=
Bandwidth Constraints defined in this table are significant =
only=0A=
if their corresponding CTs appear in the mplsDsTeClassTable. " =0A=
=0A=
AUGMENTS{ mplsInterfaceConfTable } =0A=
::=3D { mplsDsTeIfBCTable 1 } =0A=
=0A=
MplsDsTeIfBCEntry ::=3D SEQUENCE { =0A=
mplsDsTeIfBC0MaxBw MplsBitRate,=0A=
mplsDsTeIfBC1MaxBw MplsBitRate, =0A=
mplsDsTeIfBC2MaxBw MplsBitRate, =0A=
mplsDsTeIfBC3MaxBw MplsBitRate, =0A=
mplsDsTeIfBC4MaxBw MplsBitRate, =0A=
mplsDsTeIfBC5MaxBw MplsBitRate, =0A=
mplsDsTeIfBC6MaxBw MplsBitRate, =0A=
mplsDsTeIfBC7MaxBw MplsBitRate =0A=
} =0A=
=0A=
mplsDsTeIfBC0MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate=0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth on this interface. As per the =
=0A=
[DSTE-PROT0] draft, this also can be interpreted as the =
Bandwidth =0A=
Constraint 0 (BC0). =0A=
=0A=
By default, the maximum reservable bandwidth associated with =0A=
this interface can be initialized to the link bandwidth. =0A=
=0A=
Modification of this variable, should be reflected in =0A=
mplsInterfaceTotalBandwidth defined in the [LSRMIB]." =0A=
=0A=
::=3D { mplsDsTeIfBCEntry 1 } =0A=
=0A=
=0A=
mplsDsTeIfBC1MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate=0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 1 =
(BC1) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 2 } =0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
18]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
=0A=
mplsDsTeIfBC2MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 2 =
(BC2) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 3} =0A=
=0A=
mplsDsTeIfBC3MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 3 =
(BC3) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 4 } =0A=
=0A=
mplsDsTeIfBC4MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 4 =
(BC4) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 5} =0A=
=0A=
mplsDsTeIfBC5MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 5 =
(BC5) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 6 } =0A=
=0A=
mplsDsTeIfBC6MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 6 =
(BC6) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D { mplsDsTeIfBCEntry 7} =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
19]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
=0A=
mplsDsTeIfBC7MaxBw OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The maximum reservable bandwidth for Bandwidth Constraint 7 =
(BC7) =0A=
on this interface, in Kbps." =0A=
DEFVAL { 0 } =0A=
::=3D {mplsDsTeIfBCEntry 8 } =0A=
=0A=
=0A=
-- Per-CT Local Overbooking Multiplier configuration Table =0A=
=0A=
mplsDsTeIfLOMTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeIfLOMEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This table allows administrator to configure a local =
overbooking =0A=
multiplier on a per link per class-type basis." =0A=
::=3D { mplsDsTeObjects 4 } =0A=
=0A=
mplsDsTeIfLOMEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeIfLOMEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"A row is created in this table automatically by an LSR for =
every=0A=
interface capable of supporting MPLS and is enable to do=0A=
so, since it AUGMENTs the mplsInterfaceConfTable.=0A=
=0A=
According to the [DSTE-REQ] draft, an administrator can deploy =0A=
upto 8 Class-Types. It also allows the tweaking of the overbooking =0A=
ratio for each of these Class-Types on a per interface basis.=0A=
=0A=
Each entry in this table allows the administrator to configure a =0A=
overbooking factor on a per-link per-class-type basis. =
[However,=0A=
if the mplsInterfaceConfTable has a conceptual row with index 0,=0A=
all of the LOMs corresponding to that row will be no=0A=
significance and will can not be modified]=0A=
=0A=
The overbooking ration defined in this entry, will be significant =0A=
for different Class-Types, only when the corresponding Class-Type =0A=
is supported in the LSR (see the mplsDsTeClassTable). =0A=
=0A=
Additionally, agent might have to enforce other requirements as =0A=
per the Bandwidth Constraint Model. =0A=
=0A=
The units of the bandwidth constraints are in terms of percentage =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
20]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
(%) of the actual bandwidth requested by the connection. =0A=
A LOM with value 100 indicates no overbooking in use =0A=
<100 indicates underbooking in use=0A=
>100 indicates overbooking in use.=0A=
=0A=
By default, all the overbooking multipliers defined in this table =0A=
will be initialized to 100 (i.e. no overbooking). "=0A=
=0A=
AUGMENTS { mplsInterfaceConfTable } =0A=
::=3D { mplsDsTeIfLOMTable 1 } =0A=
=0A=
MplsDsTeIfLOMEntry ::=3D SEQUENCE { =0A=
mplsDsTeIfLOMCT0 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT1 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT2 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT3 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT4 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT5 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT6 Unsigned32(0..65535), =0A=
mplsDsTeIfLOMCT7 Unsigned32(0..65535) =0A=
} =0A=
=0A=
mplsDsTeIfLOMCT0 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 0, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 1 } =0A=
=0A=
mplsDsTeIfLOMCT1 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 1, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 2 } =0A=
=0A=
mplsDsTeIfLOMCT2 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
21]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
for the class-type 2, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 3 } =0A=
=0A=
mplsDsTeIfLOMCT3 OBJECT-TYPE =0A=
SYNTAX Unsigned32 =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 3, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 4 } =0A=
=0A=
mplsDsTeIfLOMCT4 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 4, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 5 } =0A=
=0A=
mplsDsTeIfLOMCT5 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 5, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 6 } =0A=
=0A=
mplsDsTeIfLOMCT6 OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 6, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 7 } =0A=
=0A=
mplsDsTeIfLOMCT7 OBJECT-TYPE =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
22]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
SYNTAX Unsigned32(0..65535) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the bandwidth overbooking multiplier =0A=
for the class-type 7, on the specified interface, =0A=
in percentage." =0A=
DEFVAL { 100 } =0A=
::=3D {mplsDsTeIfLOMEntry 8 } =0A=
=0A=
=0A=
-- TE-Class Mapping Table =0A=
=0A=
mplsDsTeClassTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeClassEntry=0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This per LSR table provides the mapping between the TE-Class =
=0A=
supported on the LSR and <Class-Type,Priority> pair." =0A=
::=3D { mplsDsTeObjects 5 } =0A=
=0A=
mplsDsTeClassEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeClassEntry=0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"An entry in this table represents a mapping between the =
TE-Class =0A=
and <Class-Type,Priority> pair. =0A=
=0A=
The [DSTE-PROTO] indicates that a DS TE domain can support 8=0A=
TE-Classes defined, by the <Class-Type,Priority> pair. An=0A=
administrator must defined the TE-Class he wants to support in=0A=
the domain by creating appropriate entries in this table. All=0A=
the LSRs in the domain, must have the same set of entries. =0A=
=0A=
Besides defining the TE-Classes, the entries in this table also =0A=
indicate the active Class-Types within the LSR and the connection =0A=
priorities it can support. More specifically:- =0A=
=0A=
The LSR is considered to support a particular Class-Type =
only if =0A=
it appears in the definition of the 8 possible TE-Classes. =0A=
=0A=
A (setup/holding) priority associated with a LSP, on a LSR is =0A=
consider to be valid only if it appears as a pair with the =0A=
class-type of the connection. =0A=
=0A=
An empty mplsDsTeClassTable effectively disables DSTE and TE on=0A=
the LSR and no (DSTE/TE) LSPs can be established on the LSR.=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
23]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
There are no other restrictions on how any of the 8 Class-Types can =
=0A=
be paired up with any of the 8 preemption priorities to form a TE- =
=0A=
class[DSTE-PROTO]."=0A=
=0A=
INDEX { mplsDsTeClassIndex } =0A=
::=3D { mplsDsTeClassTable 1 } =0A=
=0A=
MplsDsTeClassEntry ::=3D SEQUENCE { =0A=
mplsDsTeClassIndex Unsigned32(0..7), =0A=
mplsDsTeClassType Unsigned32(0..7), =0A=
mplsDsTeClassPriority Unsigned32(0..7),=0A=
mplsDsTeClassDescription DisplayString,=0A=
mplsDsTeClassRowStatus RowStatus, =0A=
mplsDsTeClassStorageType StorageType =0A=
} =0A=
=0A=
mplsDsTeClassIndex OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..7) =0A=
MAX-ACCESS accessible-for-notify =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the index of the TE-Class being configured =
=0A=
on the LSR."=0A=
::=3D { mplsDsTeClassEntry 1 } =0A=
=0A=
mplsDsTeClassType OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..7) =0A=
MAX-ACCESS accessible-for-notify =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents a Class-Type supported on the LSR." =0A=
::=3D { mplsDsTeClassEntry 2 } =0A=
=0A=
mplsDsTeClassPriority OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..7) =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the preemption priority (setup or holding) =
=0A=
supported for a particular class-type, on the LSR." =0A=
::=3D { mplsDsTeClassEntry 3 } =0A=
=0A=
mplsDsTeClassDescription OBJECT-TYPE =0A=
SYNTAX DisplayString =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Textual description of the TE-Class defined by this row." =0A=
::=3D { mplsDsTeClassEntry 4 } =0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
24]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
mplsDsTeClassRowStatus OBJECT-TYPE =0A=
SYNTAX RowStatus =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The row status for a row in this table." =0A=
::=3D { mplsDsTeClassEntry 5 } =0A=
=0A=
mplsDsTeClassStorageType OBJECT-TYPE =0A=
SYNTAX StorageType =0A=
MAX-ACCESS read-create =0A=
STATUS current =0A=
DESCRIPTION =0A=
"The storage type for this entry." =0A=
::=3D { mplsDsTeClassEntry 6 } =0A=
=0A=
=0A=
-- Unreserved Bandwidth Table =0A=
=0A=
mplsDsTeIfUnresBwTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeIfUnresBwEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This table presents the unreserved bandwidth available on =0A=
each interface for each TE-Class." =0A=
::=3D { mplsDsTeObjects 6 } =0A=
=0A=
mplsDsTeIfUnresBwEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeIfUnresBwEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"A row is created in this table automatically by an LSR for =
every=0A=
interface capable of supporting MPLS and is enable to do=0A=
so, since it AUGMENTs the mplsInterfaceConfTable.=0A=
=0A=
Each entry in this table presents the unreserved / available =0A=
bandwidth for different TE-Classes on this interface. [However,=0A=
if the mplsInterfaceConfTable has a conceptual row with index 0,=0A=
all of the LOMs corresponding to that row will be no=0A=
significance and will can not be modified] =0A=
=0A=
When the TE-Class is not supported on the LSR, the corresponding=0A=
unreserved bandwidth will be set to zero."=0A=
=0A=
AUGMENTS { mplsDsTeIfConfTable } =0A=
::=3D { mplsDsTeIfUnresBwTable 1 } =0A=
=0A=
MplsDsTeIfUnresBwEntry ::=3D SEQUENCE { =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
25]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
mplsDsTeIfUnresBwTEClass0 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass1 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass2 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass3 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass4 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass5 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass6 MplsBitRate, =0A=
mplsDsTeIfUnresBwTEClass7 MplsBitRate =0A=
} =0A=
=0A=
mplsDsTeIfUnresBwTEClass0 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 0, on the specified interface." =0A=
::=3D {mplsDsTeIfUnresBwEntry 1 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass1 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 1, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 2 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass2 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 2, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 3 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass3 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 3, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 4 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass4 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
26]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 4, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 5 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass5 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 5, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 6 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass6 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 6, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 7 } =0A=
=0A=
mplsDsTeIfUnresBwTEClass7 OBJECT-TYPE =0A=
SYNTAX MplsBitRate =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This value represents the unreserved bandwidth =0A=
for the TE-Class 7, on the specified interface" =0A=
::=3D {mplsDsTeIfUnresBwEntry 8 } =0A=
=0A=
=0A=
=0A=
-- Tunnel Table (Applies only to tunnel heads at this LSR) =0A=
=0A=
mplsDsTeTunTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeTunEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This table indicates which DiffServ Class-Type the particular =
=0A=
Traffic Engineering tunnels have been assigned to. This table =
=0A=
extends the mplsTunnelTable from the MPLS-TE-MIB[TE-MIB], by=0A=
augmenting it. "=0A=
::=3D { mplsDsTeObjects 7 } =0A=
=0A=
=0A=
mplsDsTeTunEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeTunEntry =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
27]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"An entry in this table is created by an LSR for every traffic =
=0A=
engineering tunnel instance capable of supporting MPLS =0A=
DiffServ-Aware Traffic Engineering."=0A=
=0A=
AUGMENTS { mplsTunnelTable }=0A=
::=3D { mplsDsTeTunTable 1 } =0A=
=0A=
MplsDsTeTunEntry ::=3D SEQUENCE { =0A=
mplsDsTeTunTunnelClassType Unsigned32(0..7)=0A=
} =0A=
=0A=
mplsDsTeTunTunnelClassType OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..7) =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This object indicates the DiffServ-Aware TE class to which this =
=0A=
tunnel instance has been assigned.=0A=
=0A=
If the specified class-type does not appear in the=0A=
mplsDsTeClassTable, the tunnel instance corresponding to this =
row=0A=
will remain down.=0A=
=0A=
When user does not specify a specific class-type, a default =
value=0A=
representing CT0 is assumed. "=0A=
=0A=
DEFVAL { 0 }=0A=
::=3D { mplsDsTeTunEntry 5 } =0A=
=0A=
=0A=
-- LSP Table =0A=
=0A=
mplsDsTeLspTable OBJECT-TYPE =0A=
SYNTAX SEQUENCE OF MplsDsTeLspEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This table indicates which DiffServ-Aware TE class particular =
=0A=
LSPs. This table AUGMENTS the mplsXCTable." =0A=
::=3D { mplsDsTeObjects 8 } =0A=
=0A=
mplsDsTeLspEntry OBJECT-TYPE =0A=
SYNTAX MplsDsTeLspEntry =0A=
MAX-ACCESS not-accessible =0A=
STATUS current =0A=
DESCRIPTION =0A=
"An entry in this table is created by an LSR for every LSP =
capable of =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
28]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
supporting MPLS DiffServ-Aware Traffic Engineering. Specifically, an =
=0A=
entry in this table must correspond to an entry in the mplsXCTable =
=0A=
from the MPLS-LSR-MIB [MPLS-LSR-MIB]." =0A=
AUGMENTS { mplsXCEntry } =0A=
::=3D { mplsDsTeLspTable 1 } =0A=
=0A=
MplsDsTeLspEntry ::=3D SEQUENCE { =0A=
mplsDsTeLspClassType Unsigned32(0..7)=0A=
} =0A=
=0A=
mplsDsTeLspClassType OBJECT-TYPE =0A=
SYNTAX Unsigned32(0..7) =0A=
MAX-ACCESS read-only =0A=
STATUS current =0A=
DESCRIPTION =0A=
"This object indicates the DiffServ-Aware TE class to which =0A=
this LSP has been assigned."=0A=
=0A=
DEFVAL { 0 }=0A=
::=3D { mplsDsTeLspEntry 1 } =0A=
=0A=
=0A=
=0A=
-- Notifications =0A=
=0A=
-- TBD. =0A=
=0A=
-- Conformance Statement =0A=
=0A=
mplsDsTeGroups =0A=
OBJECT IDENTIFIER ::=3D { mplsDsTeConformance 1 } =0A=
=0A=
mplsDsTeCompliances =0A=
OBJECT IDENTIFIER ::=3D { mplsDsTeConformance 2 } =0A=
=0A=
=0A=
-- Module Compliance =0A=
=0A=
mplsDsTeModuleCompliance MODULE-COMPLIANCE =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Compliance statement for agents that support MPLS Diff-Serv =
=0A=
Aware Traffic Engineering." =0A=
MODULE -- this module =0A=
=0A=
-- The mandatory groups have to be implemented =0A=
-- by all LSRs supporting MPLS DS TE. However, =0A=
-- they may all be supported =0A=
-- as read-only objects in the case where =0A=
-- configuration through this MIB is unsupported. =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
29]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
=0A=
MANDATORY-GROUPS { mplsDsTeScalarGroup, =0A=
mplsDsTeIfBCGroup,=0A=
mplsDsTeIfLOMGroup, =0A=
mplsDsTeClassGroup, =0A=
mplsDsTeTunGroup=0A=
}=0A=
=0A=
-- Note: The following MIB Tables defined in this MIB MODULE=0A=
-- are not mandatory tables=0A=
-- (i) mplsDsTeIfUnresBwTable=0A=
-- (ii) mplsDsTeLspTable=0A=
=0A=
::=3D { mplsDsTeCompliances 1 } =0A=
=0A=
-- Units of conformance. =0A=
=0A=
mplsDsTeScalarGroup OBJECT-GROUP =0A=
OBJECTS { mplsDsTeBwConstraintModel } =0A=
=0A=
STATUS current =0A=
DESCRIPTION =0A=
"Collection of scalar objects required for DS TE =0A=
management." =0A=
::=3D { mplsDsTeGroups 1 }=0A=
=0A=
=0A=
mplsDsTeIfBCGroup OBJECT-GROUP =0A=
OBJECTS {=0A=
mplsDsTeIfBC0MaxBw,=0A=
mplsDsTeIfBC1MaxBw,=0A=
mplsDsTeIfBC2MaxBw,=0A=
mplsDsTeIfBC3MaxBw,=0A=
mplsDsTeIfBC4MaxBw,=0A=
mplsDsTeIfBC5MaxBw,=0A=
mplsDsTeIfBC6MaxBw,=0A=
mplsDsTeIfBC7MaxBw=0A=
} =0A=
=0A=
STATUS current =0A=
DESCRIPTION =0A=
"Collection of objects needed for managing the Bandwidth=0A=
constraints on a per MPLS Interface basis." =0A=
::=3D { mplsDsTeGroups 2 } =0A=
=0A=
=0A=
mplsDsTeIfLOMGroup OBJECT-GROUP =0A=
OBJECTS {=0A=
mplsDsTeIfLOMCT0,=0A=
mplsDsTeIfLOMCT1,=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
30]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
mplsDsTeIfLOMCT2,=0A=
mplsDsTeIfLOMCT3,=0A=
mplsDsTeIfLOMCT4,=0A=
mplsDsTeIfLOMCT5,=0A=
mplsDsTeIfLOMCT6,=0A=
mplsDsTeIfLOMCT7=0A=
} =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Collection of objects needed for managing the Local =
Overbooking=0A=
Multiplier on a per Class-Type per MPLS interface basis."=0A=
=0A=
::=3D { mplsDsTeGroups 3 } =0A=
=0A=
=0A=
mplsDsTeClassGroup OBJECT-GROUP =0A=
OBJECTS {=0A=
mplsDsTeClassIndex,=0A=
mplsDsTeClassType,=0A=
mplsDsTeClassPriority,=0A=
mplsDsTeClassDescription,=0A=
mplsDsTeClassRowStatus,=0A=
mplsDsTeClassStorageType=0A=
} =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Collection of objects needed for managing the TE-Class=0A=
definitions within the DSTE LSR."=0A=
::=3D { mplsDsTeGroups 4 } =0A=
=0A=
mplsDsTeTunGroup OBJECT-GROUP=0A=
OBJECTS {=0A=
mplsDsTeTunClassType=0A=
} =0A=
STATUS current =0A=
DESCRIPTION =0A=
"Collection of objects needed for MPLS DS TE Tunnel =
management." =0A=
::=3D { mplsDsTeGroups 5 } =0A=
=0A=
END=0A=
=0A=
-- End of MPLS-DS-TE-MIB =0A=
=0A=
9.0 Acknowledgments =0A=
=0A=
TBD. =0A=
=0A=
=0A=
10.0 References =0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
31]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
[DSTE-REQ] Le Faucheur et al, Requirements for support of =0A=
Diff-Serv-aware MPLS Traffic Engineering, =0A=
draft-ietf-tewg-diff-te-reqts-05.txt, June 2002. =0A=
=0A=
[DSTE-PROTO] Le Faucheur et al, Protocol extensions for support of =
=0A=
Diff-Serv-aware MPLS Traffic Engineering, =0A=
draft-ietf-tewg-diff-te-proto-01.txt, June 2002 =0A=
=0A=
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, =0A=
"Multiprotocol Label Switching Architecture", RFC2702, =
=0A=
September 1999. =0A=
=0A=
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. =0A=
Nadeau, "MPLS Label Switch Router Management =0A=
Information Base Using SMIv2", Internet =0A=
Draft <draft-ietf-mpls-lsr-mib-09.txt>, October=0A=
2000. =0A=
=0A=
[TEMIB] Srinivasan, C., Viswanathan, A. and T. =0A=
Nadeau, "MPLS Traffic Engineering Management =0A=
Information Base Using SMIv2", Internet =0A=
Draft <draft-ietf-mpls-te-mib-09.txt>, November =0A=
2002.=0A=
=0A=
[TCMIB] Nadeau et al,"Definitions of Textual Conventions =
for=0A=
Multiprotocol Label Switching (MPLS) Management",=0A=
Internet Draft<draft-ietf-mpls-tc-mib-05.txt>,=0A=
November 2002=0A=
=0A=
[BW-ACCT] Kompella,Kireeti=0A=
"Bandwidth Accounting for Traffic Engineering",=0A=
Internet Draft <draft-kompella-tewg-bw-acct-00.txt>,=0A=
=0A=
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", =0A=
RFC 1700, October 1994. See also: =0A=
http://www.isi.edu/in-notes/iana/assignments/smi- =0A=
numbers =0A=
=0A=
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS =
=0A=
FAMILY NUMBERS,(http://www.isi.edu/in- =0A=
notes/iana/assignements/address-family-numbers), =0A=
for MIB see: =0A=
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib =0A=
=0A=
[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An =0A=
Architecture for Describing SNMP Management =0A=
Frameworks", RFC 2271, January 1998. =0A=
=0A=
[SMIv1] Rose, M., and K. McCloghrie, "Structure and =0A=
Identification of Management Information for =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
32]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
TCP/IP-based Internets", RFC 1155, May 1990. =0A=
=0A=
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB =0A=
Definitions", RFC 1212, March 1991. =0A=
=0A=
[SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use =0A=
with the SNMP", RFC 1215, March 1991. =0A=
=0A=
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, =
=0A=
"Message Processing and Dispatching for the Simple =0A=
Network Management Protocol (SNMP)", RFC 2572, =0A=
April 1999. =0A=
=0A=
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security =
=0A=
Model (USM) for version 3 of the Simple Network =0A=
Management Protocol (SNMPv3)", RFC 2574, April =0A=
1999. =0A=
=0A=
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Protocol Operations for Version 2 of =0A=
the Simple Network Management Protocol (SNMPv2)", =0A=
RFC 1905, January 1996. =0A=
=0A=
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 =0A=
Applications", RFC 2573, April 1999. =0A=
=0A=
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- =0A=
based Access Control Model (VACM) for the Simple =0A=
Network Management Protocol (SNMP)", RFC 2575, =0A=
April 1999. =0A=
=0A=
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, =0A=
"Introduction to Version 3 of the Internet-standard =
=0A=
Network Management Framework", RFC 2570, April =0A=
1999. =0A=
=0A=
[SMIv2] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Structure of Management Information =0A=
for Version 2 of the Simple Network Management =0A=
Protocol (SNMPv2)", RFC 1902, January 1996. =0A=
=0A=
[SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Textual Conventions for Version 2 of =0A=
the Simple Network Management Protocol (SNMPv2)", =0A=
RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., =
=0A=
January 1996. =0A=
=0A=
[SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Conformance Statements for Version 2 =0A=
of the Simple Network Management Protocol =0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
33]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
(SNMPv2)", RFC 1904, January 1996. =0A=
=0A=
[SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, =
=0A=
"Simple Network Management Protocol", RFC 1157, May =
=0A=
1990. =0A=
=0A=
[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Introduction to Community-based =0A=
SNMPv2", RFC 1901, January 1996. =0A=
=0A=
[SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Transport Mappings for Version 2 of =0A=
the Simple Network Management Protocol (SNMPv2)", =0A=
RFC 1906, January 1996. =0A=
=0A=
[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, =
=0A=
"Message Processing and Dispatching for the Simple =0A=
Network Management Protocol (SNMP)", RFC 2272, =0A=
January 1998. =0A=
=0A=
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security =
=0A=
Model (USM) for version 3 of the Simple Network =0A=
Management Protocol (SNMPv3)", RFC 2574, April =0A=
1999. =0A=
=0A=
[SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. =0A=
Waldbusser, "Protocol Operations for Version 2 of =0A=
the Simple Network Management Protocol (SNMPv2)", =0A=
RFC 1905, January 1996. =0A=
=0A=
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 =0A=
Applications", RFC 2273, January 1998. =0A=
=0A=
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- =0A=
based Access Control Model (VACM) for the Simple =0A=
Network Management Protocol (SNMP)", RFC 2575, =0A=
April 1999. =0A=
=0A=
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture =0A=
for the Internet Protocol", RFC 2401, November =0A=
1998. =0A=
=0A=
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces =
=0A=
Group MIB using SMIv2", RFC 2233, Nov. 1997 =0A=
=0A=
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate =
=0A=
Requirement Levels", BCP 14, RFC 2119, March 1997. =0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
34]=0A=
=0C=0A=
Internet Draft MPLS DSTE MIB December 12, =
2002=0A=
=0A=
=0A=
=0A=
11.0 Authors' Addresses =0A=
=0A=
Thomas D. Nadeau =0A=
Cisco Systems, Inc. =0A=
250 Apollo Drive =0A=
Chelmsford, MA 01824 =0A=
Phone: +1-978-244-3051 =0A=
Email: tnadeau@cisco.com =0A=
=0A=
Sanjaya Choudhury =0A=
Marconi =0A=
1000 Marconi Drive, =0A=
Warrendale, PA 158 =0A=
Phone: +1-724-742-6720 =0A=
Email: sanjaya.choudhury@marconi.com =0A=
=0A=
12.0 Full Copyright Statement =0A=
=0A=
Copyright (C) The Internet Society (2000). All Rights Reserved. =0A=
This document and translations of it may be copied and furnished to =
=0A=
others, and derivative works that comment on or otherwise explain it =
=0A=
or assist in its implementation may be prepared, copied, published =0A=
and distributed, in whole or in part, without restriction of any =0A=
kind, provided that the above copyright notice and this paragraph =0A=
are included on all such copies and derivative works. However, this =0A=
document itself may not be modified in any way, such as by removing =
=0A=
the copyright notice or references to the Internet Society or other =
=0A=
Internet organizations, except as needed for the purpose of =0A=
developing Internet standards in which case the procedures for =0A=
copyrights defined in the Internet Standards process must be followed, =
=0A=
or as required to translate it into languages other than English. =0A=
=0A=
The limited permissions granted above are perpetual and will not be =
=0A=
revoked by the Internet Society or its successors or assigns. This =0A=
document and the information contained herein is provided on an "AS =
=0A=
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK =
=0A=
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT =
=0A=
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL =0A=
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY =
=0A=
OR FITNESS FOR A PARTICULAR PURPOSE. =0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Nadeau et al. Expires June 2003 [Page =
35]=0A=
------_=_NextPart_000_01C2BB5C.530B4CB0--