Thomas D. Nadeau
Francois Le Faucheur
Cisco Systems, Inc.
Angela Chiu
Celion Networks
William Townsend
Tenor Networks
Darek Skalecki
Nortel Networks
Martin Tatham
British Telecom
IETF Internet Draft
Expires: January, 2001
Document: draft-nadeau-mpls-ds-te-mib-01.txt July, 2001
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.
Contents
1.0 ABSTRACT...............................................2
2.0 INTRODUCTION...........................................2
3.0 TERMINOLOGY............................................3
4.0 THE SNMP MANAGEMENT FRAMEWORK..........................3
5.0 OBJECT DEFINITIONS.....................................4
Nadeau et al. Expires January 2002 [Page 1]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
6.0 FEATURE CHECKLIST......................................4
7.0 OUTLINE................................................4
8.0 SUMMARY OF MPLS-DS-TE-MIB..............................4
9.0 BRIEF DESCRIPTION OF MIB OBJECTS.......................5
10.0 EXAMPLE CONFIGURATION..................................5
11.0 MPLS-DS-TE-MIB DEFINITIONS.............................5
12.0 ACKNOWLEDGMENTS.......................................21
13.0 REFERENCES............................................21
14.0 AUTHORS' ADDRESSES....................................24
15.0 FULL COPYRIGHT STATEMENT..............................24
1.0 Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community. In particular, in response to customer
demands and strong input from vendors, it describes managed objects
for modeling and managing Diff-Serv-aware MPLS Traffic Engineering
[DSTEREQS][DSTEEXTS].
2.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 modeling and managing Diff-Serv-aware MPLS Traffic Engineering
[DSTEREQS][DSTEEXTS].
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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference [BCP14].
3.0 Terminology
This document uses terminology from the document describing the MPLS
architecture [MPLSArch] and from the documents describing
Diff-Serv-Aware Traffic Engineering [DSTEREQS][DSTEEXTS][DSTEISIS]
[DSTEOSPF].
4.0 The SNMP Management Framework
The SNMP Management Framework presently consists of five major components:
- An overall architecture, described in RFC 2271 [SNMPArch].
Nadeau et al. Expires January 2002 [Page 2]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
- 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 operations and associated PDU formats is
described in RFC 1157 [SNMPv1]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[SNMPv2PO].
- A set of fundamental applications described in RFC 2273 [SNMPv3App]
and the view-based access control mechanism described in RFC 2575
[SNMPv3VACM].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. This memo specifies
a MIB module that is compliant to the SMIv2. A MIB conforming to the
SMIv1 can be produced through the appropriate translations. The
resulting translated MIB must be semantically equivalent, except where
objects or events are omitted because no translation is possible (use
of Counter64). Some machine-readable information in SMIv2 will be
converted into textual descriptions in SMIv1 during the translation
process. However, this loss of machine-readable information is not
considered to change the semantics of the MIB.
5.0 Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined 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.
Nadeau et al. Expires January 2002 [Page 3]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
6.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[].
- The MIB must support the extensions set forth by Extensions to
RSVP and CR-LDP for support of Diff-Serv-aware MPLS Traffic
Engineering[], Extensions to OSPF for support of
Diff-Serv-aware MPLS Traffic Engineering[], and Extensions to
IS-IS for support of Diff-Serv-aware MPLS Traffic Engineering[].
- The MIB must support both configuration and monitoring of the
Diff-Serv-Aware TE features.
7.0 Outline
T.B.D. ...
8.0 Summary of MPLS-DS-TE-MIB
The MIB objects for performing these actions consist of the following
tables:
T.B.D.
9.0 Brief Description of MIB Objects
The following subsections describe the purpose of each of the objects
contained in the MPLS-DS-TE-MIB.
10.0 Example Configuration
11.0 MPLS-DS-TE-MIB Definitions
MPLS-DS-TE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Counter32, Unsigned32,
Nadeau et al. Expires January 2002 [Page 4]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
Counter64, Gauge32, TimeTicks
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
RowPointer, TimeStamp
FROM SNMPv2-TC
InterfaceIndex, InterfaceIndexOrZero
FROM IF-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
MplsLabel
FROM MPLS-LSR-MIB
InetAddress, InetAddressType
FROM INET-ADDRESS-MIB;
mplsDsTeMIB MODULE-IDENTITY
LAST-UPDATED "200107181200Z" -- 18 July 2001 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
Francois Le Faucheur
Postal: Cisco Systems, Inc.
Petra B - Les Lucioles - 291,
rue Albert Caquot - 06560 Valbonne
France
Tel: +33 4 92 96 75 64
Email: flefauch@cisco.com
Angela Chiu
Postal: Celion Networks
1 Sheila Drive, Suite 2
Nadeau et al. Expires January 2002 [Page 5]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
Tinton Falls, NJ 07724
Tel: +1-732-747-9987
Email: angela.chiu@celion.com
William Townsend
Postal: Tenor Networks
100 Nagog Park
Acton, MA 01720
USA
Tel: +1-978-264-4900
Email: btownsend@tenornetworks.com
Postal: Darek Skalecki
Nortel Networks
3500 Carling Ave,
Nepean K2H 8E9
CANADA
Tel: +1-613-765-2252
Email: dareks@nortelnetworks.com
General Discussion and Questions: mpls@uu.net
"
DESCRIPTION
"This MIB contains managed object definitions for
Diff-Serv-aware MPLS Traffic Engineering as described in
[DSTEREQS][DSTEEXTS]."
-- Revision history.
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."
::= { experimental 9999 } -- To be assigned
-- Textual Conventions.
-- Top level components of this MIB.
mplsDsTeNotifications OBJECT IDENTIFIER ::= { mplsDsTeMIB 0 }
mplsDsTeObjects OBJECT IDENTIFIER ::= { mplsDsTeMIB 1 }
mplsDsTeScalarObjects OBJECT IDENTIFIER ::= { mplsDsTeObjects 1 }
mplsDsTeConformance OBJECT IDENTIFIER ::= { mplsDsTeMIB 2 }
-- Scalars
mplsDsTeNumConfIfs OBJECT-TYPE
Nadeau et al. Expires January 2002 [Page 6]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the number of interfaces which are configured for
DiffServ-Aware TE MPLS capability on this device."
::= { mplsDsTeScalarObjects 1 }
-- DiffServ-Aware TE Interface Configuration Table
mplsDsTeIfConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsDsTeIfConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface DiffServ-Aware TE MPLS
capability and associated information. The entries in this
table correspond to MPLS-enabled interfaces which must also be
present in the mplsInterfaceConfTable [LSR-MIB]."
::= { mplsDsTeObjects 2 }
mplsDsTeIfConfEntry OBJECT-TYPE
SYNTAX MplsDsTeIfConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by an LSR for every
interface capable of supporting MPLS DiffServ-Aware Traffic
Engineering. Each entry in this table should correspond to an
entry in the mplsInterfaceConfTable [LSR-MIB], and will have a
corresponding Interfaces MIB entry as well. Administrators
wishing to enable the DS-TE feature on an interface without
this feature already enabled should first create entries in
the MPLS interface conf table in the MPLS-LSR-MIB. Next, the
agent should create a corresponding entry in this table to
specifically enable the DS-TE feature on the MPLS
interface. This order or operation should be enforced by the
agent to preserve consistency and interoperability. This table
'extends' the Interfaces MIB in that each entry in this table
MUST correspond to an entry in the Interfaces MIB. Therefore
the index used in this table must correspond to one found in
the Interfaces MIB."
INDEX { mplsDsTeIfConfIndex }
::= { mplsDsTeIfConfTable 1 }
MplsDsTeIfConfEntry ::= SEQUENCE {
mplsDsTeIfConfIndex InterfaceIndex,
mplsDsTeIfMaxAggrResBw Unsigned32,
mplsDsTeIfMaxAddrUnresBw Unsigned32,
Nadeau et al. Expires January 2002 [Page 7]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeIfAggrResBwUsed Unsigned32,
mplsDsTeIfAggrUnresBwUsed Unsigned32,
mplsDsTeIfDsTeAdminStatus INTEGER,
mplsDsTeIfDsTeOperStatus INTEGER,
mplsDsTeIfRowStatus RowStatus,
mplsDsTeIfConfStorageType StorageType
}
mplsDsTeIfConfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This is a unique index for an entry in the
MplsDsTeIfConfTable. A non-zero index for an entry indicates
the ifIndex for the corresponding Interfaces MIB entry. Note
that this table does not necessarily correspond one-to-one with
all entries in the Interface MIB having an ifType of
MPLS-layer; rather, only those which are enabled for MPLS
DiffServ-Aware TE functionality."
REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997"
::= { mplsDsTeIfConfEntry 1 }
mplsDsTeIfMaxAggrResBw OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum bandwidth reservable on an aggregated basis among all
bandwidth classes. Note that overbooking of this value is
allowed, and sometimes desirable."
::= { mplsDsTeIfConfEntry 2 }
mplsDsTeIfMaxAddrUnresBw OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum bandwidth which is un-reservable on an aggregated basis
among all bandwidth classes. Note that overbooking of this value
is allowed, and sometimes desirable."
::= { mplsDsTeIfConfEntry 3 }
mplsDsTeIfAggrResBwUsed OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
Nadeau et al. Expires January 2002 [Page 8]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
STATUS current
DESCRIPTION
"The amount of reservable bandwidth which currently in use an
aggregated basis among all bandwidth classes."
::= { mplsDsTeIfConfEntry 4 }
mplsDsTeIfAggrUnresBwUsed OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of un-reservable bandwidth which currently in use an
aggregated basis among all bandwidth classes."
::= { mplsDsTeIfConfEntry 5 }
mplsDsTeIfAdminStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), -- enables the feature
disabled(2), -- disables the feature
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to indicate the desired DiffServ-Aware TE
functionality status (i.e.: enable/disable) on the corresponding
MPLS interface."
::= { mplsDsTeIfConfEntry 6 }
mplsDsTeIfOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), -- ready to pass packets
down(2),
testing(3), -- in some test mode
unknown(4), -- status cannot be determined
dormant(5),
notPresent(6), -- some component is missing
lowerLayerDown(7) -- down due to the state of
-- lower layer interfaces
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is used to indicate the actual status of the
DiffServ-Aware TE feature on this interface."
::= { mplsDsTeIfConfEntry 7 }
mplsDsTeIfConfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
Nadeau et al. Expires January 2002 [Page 9]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
DESCRIPTION
"The row status for a row in this table."
::= { mplsDsTeIfConfEntry 8 }
mplsDsTeIfConfStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { mplsDsTeIfConfEntry 9 }
-- DS TE Interface Class Type Table
mplsDsTeIfClassTypeTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsDsTeIfClassTypeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface DiffServ-Aware TE class
type information. This table AUGMENTS the
mplsDsTeIfConfTable."
::= { mplsDsTeObjects 3 }
mplsDsTeIfClassTypeEntry OBJECT-TYPE
SYNTAX MplsDsTeIfClassTypeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by an LSR for every
interface capable of supporting MPLS DiffServ-Aware Traffic
Engineering. Specifically, an entry in this table must
correspond to an entry in the mplsDsTeIfConfTable. Each entry
in this table corresponds to a specific class type associated
with an interface. The entries in this table are used to
expose the bandwidth classes associated with each
interface. At the moment, only 4 bandwidth classes are
supported."
AUGMENTS { mplsDsTeIfConfTable }
::= { mplsDsTeClassTypeTable 1 }
MplsDsTeIfClassTypeEntry ::= SEQUENCE {
mplsDsTeIfClassTypeZeroMaxResBw Unsigned32,
mplsDsTeIfClassTypeZeroUnresBw Unsigned32,
mplsDsTeIfClassTypeOneMaxResBw Unsigned32,
mplsDsTeIfClassTypeOneUnresBw Unsigned32,
mplsDsTeIfClassTypeTwoMaxResBw Unsigned32,
mplsDsTeIfClassTypeTwoUnresBw Unsigned32,
mplsDsTeIfClassTypeThreeMaxResBw Unsigned32,
Nadeau et al. Expires January 2002 [Page 10]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeIfClassTypeThreeUnresBw Unsigned32,
}
mplsDsTeIfClassTypeZeroMaxResBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum reservable bandwidth for
class type 0."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 1 }
mplsDsTeIfClassTypeZeroUnresBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum unreservable bandwidth for
class type 0."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 2 }
mplsDsTeIfClassTypeOneMaxResBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum reservable bandwidth for
class type 1."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 3 }
mplsDsTeIfClassTypeOneUnresBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum unreservable bandwidth for
class type 1."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 4 }
mplsDsTeIfClassTypeTwoMaxResBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum reservable bandwidth for
class type 2."
Nadeau et al. Expires January 2002 [Page 11]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 5 }
mplsDsTeIfClassTypeTwoUnresBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum unreservable bandwidth for
class type 2."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 6 }
mplsDsTeIfClassTypeThreeMaxResBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum reservable bandwidth for class
type 3."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 7 }
mplsDsTeIfClassTypeThreeUnresBw OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the maximum unreservable bandwidth for
class type 3."
DEFVAL { 0 }
::= { mplsDsTeIfClassTypeEntry 8 }
-- 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 'extends' the mplsXCTable, as it uses the
same indexing scheme utilized therein."
::= { mplsDsTeObjects 4 }
mplsDsTeLspEntry OBJECT-TYPE
SYNTAX MplsDsTeLspEntry
MAX-ACCESS not-accessible
STATUS current
Nadeau et al. Expires January 2002 [Page 12]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
DESCRIPTION
"An entry in this table is created by an LSR for every LSP
capable of 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]."
INDEX { mplsDsTeLspXCIndex, mplsDsTeLspInSegmentIfIndex,
mplsDsTeLspInSegmentLabel, mplsDsTeLspOutSegmentIndex }
::= { mplsDsTeLspTable 1 }
MplsDsTeIfClassTypeEntry ::= SEQUENCE {
mplsDsTeLspXCIndex Integer32,
mplsDsTeLspInSegmentIfIndex InterfaceIndex,
mplsDsTeLspInSegmentLabel MplsLabel,
mplsDsTeLspOutSegmentIndex Integer32,
mplsDsTeLspClassType Integer32,
mplsDsTeLspAdminStatus INTEGER,
mplsDsTeLspOperStatus INTEGER,
mplsDsTeLspRowStatus RowStatus,
mplsDsTeLspStorageType StorageType
}
mplsDsTeLspXCIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the primary index of the LSP which can be
found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST
exist in the MPLS-LSR-MIB before an entry in this table may be
transition into the operStatus of up(1). If the entry is not
ready or has not yet been created in the MPLS-LSR-MIB, the
operStatus of this value must contain the value notPresent(6)
to indicate that this entry will be activated as soon as the
entry is available in the MPLS-LSR-MIB."
::= { mplsDsTeLspEntry 1 }
mplsDsTeLspInSegmentIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the secondary index of the LSP which can be
found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST
exist in the MPLS-LSR-MIB before an entry in this table may be
transition into the operStatus of up(1). If the entry is not
ready or has not yet been created in the MPLS-LSR-MIB, the
operStatus of this value must contain the value notPresent(6)
to indicate that this entry will be activated as soon as the
entry is available in the MPLS-LSR-MIB."
Nadeau et al. Expires January 2002 [Page 13]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
::= { mplsDsTeLspEntry 2 }
mplsDsTeLspInSegmentLabel OBJECT-TYPE
SYNTAX MplsLabel
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the tertiary index of the LSP which can be
found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST
exist in the MPLS-LSR-MIB before an entry in this table may be
transition into the operStatus of up(1). If the entry is not
ready or has not yet been created in the MPLS-LSR-MIB, the
operStatus of this value must contain the value notPresent(6)
to indicate that this entry will be activated as soon as the
entry is available in the MPLS-LSR-MIB."
::= { mplsDsTeLspEntry 3 }
mplsDsTeLspOutSegmentIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the fourth index of the LSP which can be
found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST
exist in the MPLS-LSR-MIB before an entry in this table may be
transition into the operStatus of up(1). If the entry is not
ready or has not yet been created in the MPLS-LSR-MIB, the
operStatus of this value must contain the value notPresent(6)
to indicate that this entry will be activated as soon as the
entry is available in the MPLS-LSR-MIB."
::= { mplsDsTeLspEntry 4 }
mplsDsTeLspClassType OBJECT-TYPE
SYNTAX Integer32 (0..3)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the DiffServ-Aware TE class to which
this LSP has been assigned."
::= { mplsDsTeLspEntry 5 }
mplsDsTeLspAdminStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), -- enables the feature
disabled(2), -- disables the feature
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to indicate the desired DiffServ-Aware
TE functionality status (i.e.: enable/disable) on this LSP."
Nadeau et al. Expires January 2002 [Page 14]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
::= { mplsDsTeLspEntry 6 }
mplsDsTeLspOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), -- ready to pass packets
down(2),
testing(3), -- in some test mode
unknown(4), -- status cannot be determined
dormant(5),
notPresent(6), -- some component is missing
lowerLayerDown(7) -- down due to the state of
-- lower layer interfaces
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is used to indicate the actual status of the
DiffServ-Aware TE feature on this LSP."
::= { mplsDsTeLspEntry 7 }
mplsDsTeLspRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status for a row in this table."
::= { mplsDsTeLspEntry 8 }
mplsDsTeLspStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { mplsDsTeLspEntry 9 }
-- 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-Aware TE class particular
Traffic Engineering tunnels have been assigned to. This table
'extends' the mplsTunnelTable from the MPLS-TE-MIB[TEMIB], as
it uses the same indexing scheme utilized therein."
::= { mplsDsTeObjects 5 }
Nadeau et al. Expires January 2002 [Page 15]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeTunEntry OBJECT-TYPE
SYNTAX MplsDsTeTunEntry
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. We must include all
indexes here to indicate which instances of tunnels are in
which bandwidth class, as it is entirely possible (and
sometimes desirable) to include different instances in
different classes."
INDEX { mplsDsTeTunTunnelIndex, mplsDsTeTunTunnelInstance,
mplsDsTeTunTunnelIngressLSRId, mplsDsTeTunTunnelEgressLSRId }
::= { mplsDsTeTunTable 1 }
MplsDsTeTunEntry ::= SEQUENCE {
mplsDsTeTunTunnelIndex MplsTunnelIndex,
mplsDsTeTunTunnelInstance MplsTunnelInstanceIndex,
mplsDsTeTunTunnelIngressLSRId MplsLsrId,
mplsDsTeTunTunnelEgressLSRId MplsLsrId,
mplsDsTeTunClassType Integer32,
mplsDsTeTunAdminStatus INTEGER,
mplsDsTeTunOperStatus INTEGER,
mplsDsTeTunRowStatus RowStatus,
mplsDsTeTunStorageType StorageType
}
mplsDsTeTunTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the primary index of the tunnel entry
which can be found in the MPLS-TE-MIB's [TEMIB]
mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before
an entry in this table may be transition into the operStatus of
up(1). If the entry is not ready or has not yet been created in
the MPLS-TE-MIB, the operStatus of this value must contain the
value notPresent(6) to indicate that this entry will be
activated as soon as the entry is available in the MPLS-TE-MIB."
::= { mplsDsTeTunEntry 1 }
mplsDsTeTunTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the secondary index of the tunnel entry
Nadeau et al. Expires January 2002 [Page 16]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
which can be found in the MPLS-TE-MIB's [TEMIB]
mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before
an entry in this table may be transition into the operStatus of
up(1). If the entry is not ready or has not yet been created in
the MPLS-TE-MIB, the operStatus of this value must contain the
value notPresent(6) to indicate that this entry will be
activated as soon as the entry is available in the
MPLS-TE-MIB."
::= { mplsDsTeTunEntry 2 }
mplsDsTeTunTunnelIngressLSRId OBJECT-TYPE
SYNTAX MplsLsrId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the third index of the tunnel entry
which can be found in the MPLS-TE-MIB's [TEMIB]
mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before
an entry in this table may be transition into the operStatus of
up(1). If the entry is not ready or has not yet been created in
the MPLS-TE-MIB, the operStatus of this value must contain the
value notPresent(6) to indicate that this entry will be
activated as soon as the entry is available in the
MPLS-TE-MIB."
::= { mplsDsTeTunEntry 3 }
mplsDsTeTunTunnelEgressLSRId OBJECT-TYPE
SYNTAX MplsLsrId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates the fourth index of the tunnel entry
which can be found in the MPLS-TE-MIB's [TEMIB]
mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before
an entry in this table may be transition into the operStatus of
up(1). If the entry is not ready or has not yet been created in
the MPLS-TE-MIB, the operStatus of this value must contain the
value notPresent(6) to indicate that this entry will be
activated as soon as the entry is available in the
MPLS-TE-MIB."
::= { mplsDsTeTunEntry 4 }
mplsDsTeLspClassType OBJECT-TYPE
SYNTAX Integer32 (0..3)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the DiffServ-Aware TE class to which this
LSP has been assigned."
::= { mplsDsTeTunEntry 5 }
Nadeau et al. Expires January 2002 [Page 17]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeLspAdminStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), -- enables the feature
disabled(2), -- disables the feature
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to indicate the desired DiffServ-Aware
TE functionality status (i.e.: enable/disable) on this LSP."
::= { mplsDsTeTunEntry 6 }
mplsDsTeLspOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), -- ready to pass packets
down(2),
testing(3), -- in some test mode
unknown(4), -- status cannot be determined
dormant(5),
notPresent(6), -- some component is missing
lowerLayerDown(7) -- down due to the state of
-- lower layer interfaces
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is used to indicate the actual status of the
DiffServ-Aware TE feature on this LSP."
::= { mplsDsTeTunEntry 7 }
mplsDsTeLspRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status for a row in this table."
::= { mplsDsTeTunEntry 8 }
mplsDsTeLspStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this entry."
::= { mplsDsTeTunEntry 9 }
-- Notifications
-- TBD.
Nadeau et al. Expires January 2002 [Page 18]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
-- 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.
MANDATORY-GROUPS { mplsDsTeScalarGroup,
mplsDsTeIfGroup,
mplsDsTeIfClassGroup,
mplsDsTeLspGroup,
mplsDsTeTunGroup
}
::= { mplsDsTeCompliances 1 }
-- Units of conformance.
mplsDsTeScalarGroup OBJECT-GROUP
OBJECTS { mplsDsTeNumConfIfs }
STATUS current
DESCRIPTION
"Collection of scalar objects required for DS TE
management."
::= { mplsDsTeGroups 1 }
mplsDsTeIfGroup OBJECT-GROUP
OBJECTS { mplsDsTeIfConfIndex,
MplsDsTeIfMaxAggrResBw,
mplsDsTeIfMaxAddrUnresBw,
mplsDsTeIfAggrResBwUsed,
Nadeau et al. Expires January 2002 [Page 19]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeIfAggrUnresBwUsed
MplsDsTeIfDsTeAdminStatus,
MplsDsTeIfDsTeOperStatus,
MplsDsTeIfRowStatus,
mplsDsTeIfConfStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS DS TE interface
management."
::= { mplsDsTeGroups 2 }
mplsDsTeIfClassGroup OBJECT-GROUP
OBJECTS { mplsDsTeIfClassTypeZeroMaxResBw,
mplsDsTeIfClassTypeZeroUnresBw,
mplsDsTeIfClassTypeOneMaxResBw,
mplsDsTeIfClassTypeOneUnresBw,
mplsDsTeIfClassTypeTwoMaxResBw,
mplsDsTeIfClassTypeTwoUnresBw,
mplsDsTeIfClassTypeThreeMaxResBw,
mplsDsTeIfClassTypeThreeUnresBw
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS DS TE interface
class management."
::= { mplsDsTeGroups 3 }
mplsDsTeLspGroup OBJECT-GROUP
OBJECTS { mplsDsTeLspXCIndex,
mplsDsTeLspInSegmentIfIndex,
mplsDsTeLspInSegmentLabel,
mplsDsTeLspOutSegmentIndex,
mplsDsTeLspClassType,
mplsDsTeLspAdminStatus,
mplsDsTeLspOperStatus,
mplsDsTeLspRowStatus,
mplsDsTeLspStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS DS TE LSP management."
::= { mplsDsTeGroups 4 }
mplsDsTeTunGroup OBJECT-GROUP
OBJECTS { mplsDsTeTunTunnelIndex,
Nadeau et al. Expires January 2002 [Page 20]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
mplsDsTeTunTunnelInstance,
mplsDsTeTunTunnelIngressLSRId,
mplsDsTeTunTunnelEgressLSRId,
mplsDsTeTunClassType,
mplsDsTeTunAdminStatus,
mplsDsTeTunOperStatus,
mplsDsTeTunRowStatus,
mplsDsTeTunStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS DS TE Tunnel management."
::= { mplsDsTeGroups 5 }
-- End of MPLS-DS-TE-MIB
END
12.0 Acknowledgments
TBD.
13.0 References
[DSTEREQS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend ,
W., Skalecki, D., "Requirements for support of
Diff-Serv-aware MPLS Traffic Engineering", Internet
Draft <draft-ietf-mpls-diff-te-ext-00.txt>, November 2000.
[DSTEEXTS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend ,
W., Skalecki, D., "Extensions to RSVP-TE and CR-LDP
for support of Diff-Serv-aware MPLS Traffic
Engineering", Internet Draft
<draft-ietf-mpls-diff-te-ext-00.txt>, November 2000.
[DSTEISIS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend ,
W., Skalecki, D., "Extensions to ISIS for support of
Diff-Serv-aware MPLS Traffic Engineering", Internet
Draft <draft-ietf-mpls-diff-te-isis-00.txt>, November 2000.
[DSTEOSPF] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend ,
W., Skalecki, D., "Extensions to OSPF for support of
Diff-Serv-aware MPLS Traffic Engineering ", Internet
Draft <draft-ietf-mpls-diff-te-ospf-00.txt>, November 2000.
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC2702,
September 1999.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau et al. Expires January 2002 [Page 21]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
Nadeau, "MPLS Label Switch Router Management
Information Base Using SMIv2", Internet
Draft <draft-ietf-mpls-lsr-mib-05.txt>, July
2000.
[TEMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Traffic Engineering Management
Information Base Using SMIv2", Internet
Draft <draft-ietf-mpls-te-mib-05.txt>, November
2000.
[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
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.
Nadeau et al. Expires January 2002 [Page 22]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
[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
(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
Nadeau et al. Expires January 2002 [Page 23]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
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.
14.0 Authors' Addresses
Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
Francois Le Faucheur
Cisco Systems, Inc.
Petra B - Les Lucioles - 291, rue Albert Caquot - 06560 Valbonne - France
Phone: +33 4 92 96 75 64
Email: flefauch@cisco.com
Angela Chiu
Celion Networks
1 Sheila Drive, Suite 2
Tinton Falls, NJ 07724
Phone: 732 747 9987 tel
Email: angela.chiu@celion.com
Nadeau et al. Expires January 2002 [Page 24]
Internet Draft MPLS-DS-TE-MIB February 20, 2001
William Townsend
Tenor Networks
100 Nagog Park
Acton, MA 01720
Phone: +1-978-264-4900
Email: btownsend@tenornetworks.com
Darek Skalecki
Nortel Networks
3500 Carling Ave,
Nepean K2H 8E9
Phone: +1-613-765-2252
Email: dareks@nortelnetworks.com
Martin Tatham
British Telecom
BT Adastal Park,
Martlesham Heath,
Ipswich, IP5 3RE
UK
Tel: +44 1473 606349
Fax: +44 1473 606727
Email: martin.tatham@bt.com
15.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 January 2002 [Page 25]