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