Network Working Group Martin Dubuc
Internet Draft edgeflow, Inc.
Expires: August 2001
Sudheer Dharanikota
Nayna Networks, Inc.
Thomas D. Nadeau
Cisco Systems, Inc.
Link Bundling Information Base Using SMIv2
draft-dubuc-mpls-bundle-mib-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026.
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.
Table of Contents
1. Abstract ..................................................... 2
2. Introduction ................................................. 2
3. Terminology .................................................. 3
4. The SNMP Management Framework ................................ 3
4.1. Object Definitions ........................................... 4
5. Feature Checklist ............................................ 4
6. Outline ...................................................... 4
6.1. Summary of Link Bundling MIB ................................. 5
7. Brief Description of MIB Objects ............................. 6
Dubuc et al. Expires August 2001 [Page 1]
Internet Draft MPLS Link Bundling MIB February 23, 2001
7.1. linkBundlingTable ............................................ 6
7.2. linkBundlingOspfTeTable ...................................... 6
7.3. linkBundlingIsisTeTable ...................................... 6
7.4. linkBundlingSrlgTable ........................................ 6
7.5. linkBundlingBandwidthTable ................................... 6
7.6. componentLinkTable ........................................... 7
7.7. compLinkOspfTeTable .......................................... 7
7.8. compLinkIsisTeTable .......................................... 7
7.9. compLinkBandwidthTable ....................................... 7
8. Example of Bundled Link Setup ................................ 7
9. Link Bundling MIB Definitions ................................ 10
10. Security Considerations ...................................... 37
11. Acknowledgments .............................................. 38
12. References ................................................... 38
13. Authors' Addresses ........................................... 41
14. Full Copyright Statement ..................................... 42
1. Abstract
This memo defines an experimental portion of the Management Informa-
tion Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes managed objects for
modeling link bundling as described in [BUNDLING].
2. Introduction
This memo defines an experimental portion of the Management Informa-
tion Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes managed objects for
modeling link bundling as described in [BUNDLING].
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].
Dubuc et al. Expires August 2001 [Page 2]
Internet Draft MPLS Link Bundling MIB February 23, 2001
3. Terminology
This document uses terminology from the document describing link bun-
dling [BUNDLING].
The link bundling feature is designed to aggregate one or more simi-
lar entities between a node pair into a bundled link [BUNDLING]. In
the document, those entities are referred to as component links.
A bundled link is just another kind of Traffic Engineering (TE) link
(see [GMPLS-OSPF]).
4. The SNMP Management Framework
The SNMP Management Framework presently consists of five major com-
ponents:
- 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 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].
Dubuc et al. Expires August 2001 [Page 3]
Internet Draft MPLS Link Bundling MIB February 23, 2001
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 possi-
ble (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 informa-
tion is not considered to change the semantics of the MIB.
4.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 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.
5. Feature Checklist
The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the
following requirements and constraints:
- The MIB supports the management of bundled links.
- Support is provided for configuration of traffic engineering
parameters associated with component links and link bundles.
- The MIB allows the configuration of the mapping between the
component links and the bundled links.
- The MIB is used to monitor the priority-based component link
and bundled link bandwidth values.
Dubuc et al. Expires August 2001 [Page 4]
Internet Draft MPLS Link Bundling MIB February 23, 2001
6. Outline
Configuring bundle links involves the following steps:
- Creating a bundled link.
- Optionally specifying the shared risk link groups.
- Configuring the component links including the traffic engineering
parameters and associating the componet links with the
appropriate link bundle.
6.1. Summary of Link Bundling MIB
The MIB objects for performing these actions consist of the following
tables:
- The link bundling table (linkBundlingTable), which is used to
specify bundled links and their generic traffic engineering
parameters.
- The link bundling OSPF traffic engineering table
(linkBundlingOspfTeTable), which is used for configuring OSPF
traffic engineering parameters associated with bundled links.
- The link bundling IS-IS traffic engineering table
(linkBundlingIsisTeTable), which is used for configuring IS-IS
traffic engineering parameters associated with bundled links.
- The shared risk link group (SRLG) table (linkBundlingSrlgTable),
which is used to specify the SRLGs associated with a bundled link.
- The link bundling bandwidth table (linkBundlingBandwidthTable),
which is used for reporting priority-based bandwidth values
associated with bundled links.
- The component link table (componentLinkTable), which is
used to identify the component links that are associated with
the bundled links and specify the componnet link generic traffic
engineering parameters.
- The component link OSPF traffic engineering table
(compLinkOspfTeTable), which is used to identify the OSPF traffic
engineering parameters that are associated with component links.
- The component link IS-IS traffic engineering table
Dubuc et al. Expires August 2001 [Page 5]
Internet Draft MPLS Link Bundling MIB February 23, 2001
(compLinkIsisTeTable), which is used to identify the IS-IS traffic
engineering parameters that are associated with component links.
- The component link bandwidth table (componentLinkBandwidthTable),
which is used to report priority-based bandwidth values associated
with component links.
These tables are described in the subsequent sections.
7. Brief Description of MIB Objects
Sections 7.1-7.6 describe objects pertaining to link bundling. The
MIB objects were derived from the link bundling document [BUNDLING].
7.1. linkBundlingTable
This table represents the bundled links.
7.2. linkBundlingOspfTeTable
This table represents the OSPF traffic engineering parameters that
are associated with the bundled links.
7.3. linkBundlingIsisTeTable
This table represents the IS-IS traffic engineering parameters that
are associated with the bundled links.
7.4. linkBundlingSrlgTable
This table represents the shared risk link groups (SRLGs) associated
with bundled links.
7.5. linkBundlingBandwidthTable
This table specifies the priority-based bandwidth traffic engineering
parameters associated with bundled links.
Dubuc et al. Expires August 2001 [Page 6]
Internet Draft MPLS Link Bundling MIB February 23, 2001
7.6. componentLinkTable
This table enumerates the component links and their association with
bundled link. It also describes the traffic engineering parameters
associated with the component links.
7.7. compLinkOspfTeTable
This table represents the OSPF traffic engineering parameters that
are associated with the component links.
7.8. compLinkIsisTeTable
This table represents the IS-IS traffic engineering parameters that
are associated with the component links.
7.9. compLinkBandwidthTable
The component link bandwidth table specifies the priority-based
bandwidth values associated with the component links.
8. Example of Bundled Link Setup
In this section we provide a brief example of using the MIB
objects described in section 9 to set up a bundled link.
While this example is not meant to illustrate every
nuance of the MIB, it is intended as an aid to understanding some
of the key concepts. It is meant to be read after going through the
MIB itself.
Suppose that one would like to manually create a bundled link
out of three component links, two primary and one secondary. Assume
that the bundled link is associated with SRLGs 10 and 50. Finally,
let the component links be port entity interfaces (lambdas). The
following example illustrates which rows and corresponding objects
might be created to accomplish this.
First, a bundled link entry is created.
In linkBundlingTable:
Dubuc et al. Expires August 2001 [Page 7]
Internet Draft MPLS Link Bundling MIB February 23, 2001
{
linkBundleId = 20,
linkBundleIdParent = 0,
linkBundleIdType = unnumbered(1),
linkBundlingTeMetric = 5,
linkBundlingMuxCapability = lambdaSwitch(150),
linkBundlingIncomingIfId = 48,
linkBundlingOutgoingIfId = 43,
linkBundlingMinReservableBandwidth = 100000000,
linkBundlingMaxReservableBandwidth = 100000000,
linkBundlingRowStatus = createAndWait(5)
}
The OSPF traffic engineering parameters are configured for the
bundled link.
In linkBundlingOspfTeTable:
{
linkBundleId = 20,
linkBundlingOspfLinkType = pointToPoint(1),
linkBundlingOspfLinkId = 'c0010101'H, -- 192.1.1.2
linkBundlingOspfResourceClass = '00000003'H,
linkBundlingRowStatus = createAndGo(4)
}
We then associate SRLGs 10 and 50 with the bundled link.
In the linkBundlingSrlgTable:
{
linkBundleId = 20,
srlg = 10,
srlgRowStatus = createAndGo(4)
}
{
linkBundleId = 20,
srlg = 50,
srlgRowStatus = createAndGo(4)
}
Next, the three component links are created. The
association between the component link and the bundled link
is stored in the linkBundleId field.
In componentLinkTable:
{
compLinkEntityIfId = 40,
compLinkBundleId = 20,
Dubuc et al. Expires August 2001 [Page 8]
Internet Draft MPLS Link Bundling MIB February 23, 2001
compLinkrafficEngineeringMetric = 5,
compLinkMuxCapability = lambdaSwitch(150),
compLinkEncodingType = clear(5),
compLinkMinimumReservableBandwidth = 100000000,
compLinkMaximumReservableBandwidth = 100000000,
compLinkProtectionType = primary(1),
compLinkRowStatus = createAndWait(5)
}
In compLinkOspfTable:
{
compLinkEntityIfId = 40,
compLinkOspfLinkType = pointToPoint(1),
compLinkOspfLinkId = 'c0010101'H, -- 192.1.1.2
compLinkOspfResourceClass = '00000003'H
compLinkRowStatus = createAndGo(4)
}
In componentLinkTable:
{
compLinkEntityIfId = 43,
compLinkBundleId = 20,
compLinkrafficEngineeringMetric = 5,
compLinkMuxCapability = lambdaSwitch(150),
compLinkEncodingType = clear(5),
compLinkMinimumReservableBandwidth = 100000000,
compLinkMaximumReservableBandwidth = 100000000,
compLinkProtectionType = primary(1),
compLinkRowStatus = createAndWait(5)
}
In compLinkOspfTable:
{
compLinkEntityIfId = 43,
compLinkOspfLinkType = pointToPoint(1),
compLinkOspfLinkId = 'c0010101'H, -- 192.1.1.2
compLinkOspfResourceClass = '00000003'H
compLinkRowStatus = createAndGo(4)
}
In componentLinkTable:
{
compLinkEntityIfId = 44,
compLinkBundleId = 20,
compLinkrafficEngineeringMetric = 5,
compLinkMuxCapability = lambdaSwitch(150),
compLinkEncodingType = clear(5),
compLinkMinimumReservableBandwidth = 100000000,
Dubuc et al. Expires August 2001 [Page 9]
Internet Draft MPLS Link Bundling MIB February 23, 2001
compLinkMaximumReservableBandwidth = 100000000,
compLinkProtectionType = secondary(1),
compLinkRowStatus = createAndWait(5)
}
In compLinkOspfTable:
{
compLinkEntityIfId = 44,
compLinkOspfLinkType = pointToPoint(1),
compLinkOspfLinkId = 'c0010101'H, -- 192.1.1.2
compLinkOspfResourceClass = '00000003'H
compLinkRowStatus = createAndGo(4)
}
Note that the bandwidth attributes in linkBundlingBandwidthTable
and compLinkBandwidthTable are maintained by the
device according to LSP creation/deletion at different priorities.
The values in the linkBundlingBandwidthTable are an aggregation
of the values for the component links of the bundled link.
9. Link Bundling MIB Definitions
LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Unsigned32
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
RouterID
FROM OSPF-MIB;
linkBundlingMIB MODULE-IDENTITY
LAST-UPDATED "200102151200Z" -- 23 February 2001 12:00:00 EST
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
Dubuc et al. Expires August 2001 [Page 10]
Internet Draft MPLS Link Bundling MIB February 23, 2001
" Martin Dubuc
Postal: edgeflow, Inc.
329 March Rd.
Kanata, ON, CANADA K2K 2E1
Tel: +1-613-270-9279 x253
Email: martin.dubuc@edgeflow.com
Sudheer Dharanikota
Postal: Nayna Networks, Inc.
157 Topaz Street
Milipitas, CA 95035
Tel: +1-408-956-8000 x357
Email: sudheer@nayna.com
Thomas D. Nadeau
Postal: Cisco Systems, Inc.
350 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com"
DESCRIPTION
"This MIB contains managed object definitions for
MPLS traffic engineering link bundling as
defined in: Kompella, K., Rekhter, Y., Berger, L.,
Link Bundling in MPLS Traffic Engineering
Internet Draft <draft-ietf-mpls-bundling-04.txt>,
November 2000."
-- Revision history.
REVISION
"200102231200Z" -- 23 February 2001 12:00:00 EST
DESCRIPTION
"Initial draft version." -- Experimental number TBA - To be
assigned by the IANA
::= { experimental 98 }
-- Textual Conventions
LinkBundleId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This value represents a link bundle identifier."
SYNTAX Unsigned32 (1..4294967295)
LinkBundleIdOrZero ::= TEXTUAL-CONVENTION
STATUS current
Dubuc et al. Expires August 2001 [Page 11]
Internet Draft MPLS Link Bundling MIB February 23, 2001
DESCRIPTION
"This value represents the identifier of the bundled link.
A value of zero means that the bundled link identifier is
unassigned."
SYNTAX Unsigned32 (0..4294967295)
-- Top level components of this MIB
-- Traps linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundling-
MIB 0 } -- Tables, Scalars linkBundlingObjects OBJECT IDENTIFIER
::= { linkBundlingMIB 1 } -- Conformance linkBundlingConformance
OBJECT IDENTIFIER ::= { linkBundlingMIB 2 }
-- Bundled Link Table
linkBundlingTable OBJECT-TYPE
SYNTAX SEQUENCE OF LinkBundlingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the grouping of component links into
bundled links."
::= { linkBundlingObjects 1 }
linkBundlingEntry OBJECT-TYPE
SYNTAX LinkBundlingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created for every bundled link."
INDEX { linkBundleId }
::= { linkBundlingTable 1 }
LinkBundlingEntry ::= SEQUENCE {
linkBundleId LinkBundleId,
linkBundleType Unsigned32,
linkBundleParent LinkBundleId,
linkBundlingTeMetric Unsigned32,
linkBundlingMuxCapability Unsigned32,
linkBundlingProtectionType Unsigned32,
linkBundlingIncomingIfId InterfaceIndexOrZero,
linkBundlingOutgoingIfId InterfaceIndexOrZero,
linkBundlingMinReservableBandwidth Unsigned32,
linkBundlingMaxReservableBandwidth Unsigned32,
linkBundlingCompLinkFlooding InterfaceIndexOrZero,
linkBundlingAdminStatus Unsigned32,
linkBundlingOperStatus Unsigned32,
Dubuc et al. Expires August 2001 [Page 12]
Internet Draft MPLS Link Bundling MIB February 23, 2001
linkBundlingRowStatus RowStatus,
linkBundlingStorageType StorageType }
linkBundleId OBJECT-TYPE
SYNTAX LinkBundleId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is a unique index for an entry in the linkBundlingTable.
The index also points to an entry in the lmpLinkBundleTable."
REFERENCE
"draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin,
A. Banerjee, February 2001."
::= { linkBundlingEntry 1 }
linkBundleType OBJECT-TYPE
SYNTAX INTEGER {
numbered(0),
unnumbered(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The link bundle identifier type (numbered or unnumbered)."
::= { linkBundlingEntry 2 }
linkBundleParent OBJECT-TYPE
SYNTAX LinkBundleIdOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the identifier of the parent of the link
bundle. This is used to represent containment hierarchy of link
bundles. An identifier of zero is used when then there is no
parent to the link bundle."
::= { linkBundlingEntry 3 }
linkBundlingTeMetric OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The traffic engineering metric for the link bundle is
derived from its component links. All component links
within the link bundle must have the same traffic engineering
metric."
Dubuc et al. Expires August 2001 [Page 13]
Internet Draft MPLS Link Bundling MIB February 23, 2001
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingEntry 4 }
linkBundlingMuxCapability OBJECT-TYPE
SYNTAX INTEGER {
packetSwitch1(1),
packetSwitch2(2),
packetSwitch3(3),
packetSwitch4(4),
layer2Switch(51),
tdm(100),
lambdaSwitch(150),
fiberSwitch(200)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies link multiplex capability of the
link bundle, which is derived from its component links. All
component links within the same bundle must have the same
link multiplex capability."
REFERENCE
"draft-ietf-mpls-lsp-hierarchy-01.txt - LSP Hierarchy with
MPLS TE, K. Kompella, Y. Rekhter, September 2000."
::= { linkBundlingEntry 5 }
linkBundlingProtectionType OBJECT-TYPE
SYNTAX INTEGER {
unprotected(0),
shared(1),
dedicated1For1(2),
dedicated1Plus1(3),
enhanced(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies link protection type of the
link bundle, which is derived from its component links. All
component links within the same bundle must have the same
link protection type."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
Dubuc et al. Expires August 2001 [Page 14]
Internet Draft MPLS Link Bundling MIB February 23, 2001
D. Saha, V. Sharma, November 2000."
::= { linkBundlingEntry 6 }
linkBundlingIncomingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The incoming interface is set to the outgoing interface
identifier chosen by the neighboring LSR for the reverse
link corresponding to this bundle."
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingEntry 7 }
linkBundlingOutgoingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the link is unnumbered, the outgoing interface identifier is
set to the outgoing interface identifier chosen for the bundle
by the advertising LSR."
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingEntry 8 }
linkBundlingMinReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute specifies the minimum reservable bandwidth on
the link bundle. This is derived from the union of the
minimum reservable bandwidth of all component links
associated with the link bundle."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { linkBundlingEntry 9 }
linkBundlingMaxReservableBandwidth OBJECT-TYPE
Dubuc et al. Expires August 2001 [Page 15]
Internet Draft MPLS Link Bundling MIB February 23, 2001
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute specifies the maximum reservable bandwidth on
the link bundle. This is the union of the maximum reservable
bandwidth of all the component links within the link bundle."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { linkBundlingEntry 10 }
linkBundlingCompLinkFlooding OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object identifies the component link that is used for
flooding if flooding is restricted to only one component
link. If the value is zero, then flooding must be done on
all component links within the bundle."
REFERENCE
"draft-ietf-ospf-isis-flood-opt-00.txt - Flooding optimization
in link-state routing protocols, A. Zinin, M. Shand,
October 2000."
::= { linkBundlingEntry 11 }
linkBundlingAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The desired operational status of this bundled link."
::= { linkBundlingEntry 12 }
linkBundlingOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2), degraded(3) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual operational status of this bundled link. A degraded
status indicates that the bundled link cannot provide the
provisioned protection level, but yet, there is no disruption
of service. For instance, if the protection type is 1+1 and
one link is down, the link bundle still carries the requested
amount of data traffic, but this traffic is not protected
Dubuc et al. Expires August 2001 [Page 16]
Internet Draft MPLS Link Bundling MIB February 23, 2001
anymore."
::= { linkBundlingEntry 13 }
linkBundlingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { linkBundlingEntry 14 }
linkBundlingStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { linkBundlingEntry 15 }
-- End of linkBundlingTable
-- OSPF Traffic Engineering Parameters for Bundled Links
linkBundlingOspfTeTable OBJECT-TYPE
SYNTAX SEQUENCE OF LinkBundlingOspfTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the OSPF traffic engineering information
associated with the MPLS bundled link."
::= { linkBundlingObjects 2 }
linkBundlingOspfTeEntry OBJECT-TYPE
SYNTAX LinkBundlingOspfTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created for every link bundle."
AUGMENTS { linkBundlingEntry }
::= { linkBundlingOspfTeTable 1 }
LinkBundlingOspfTeEntry ::= SEQUENCE {
linkBundlingOspfLinkType Unsigned32,
linkBundlingOspfLinkId RouterID,
linkBundlingOspfResourceClass OCTET STRING }
Dubuc et al. Expires August 2001 [Page 17]
Internet Draft MPLS Link Bundling MIB February 23, 2001
linkBundlingOspfLinkType OBJECT-TYPE
SYNTAX INTEGER {
pointToPoint(1),
multiAccess(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the OSPF link type for the link
bundle. It is derived from the component links link type.
All component link within the same bundle must have the same
link type."
::= { linkBundlingOspfTeEntry 1 }
linkBundlingOspfLinkId OBJECT-TYPE
SYNTAX RouterID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"On point-to-point link, the link identifier is the Router ID
of the neighbor. It is derived from the link identifier
associated with its component links."
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingOspfTeEntry 2 }
linkBundlingOspfResourceClass OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the link bundle resource class. It
is derived from the component link resource class. The resource
class is a 32 bit bitfield. All component links within a link
bundle must have the same resource class."
::= { linkBundlingOspfTeEntry 3 }
-- End of linkBundlingOspfTeTable
-- IS-IS Traffic Engineering Parameters for Bundled Links
linkBundlingIsisTeTable OBJECT-TYPE
SYNTAX SEQUENCE OF LinkBundlingIsisTeEntry
MAX-ACCESS not-accessible
STATUS current
Dubuc et al. Expires August 2001 [Page 18]
Internet Draft MPLS Link Bundling MIB February 23, 2001
DESCRIPTION
"This table specifies the IS-IS traffic engineering information
associated with the MPLS bundled link."
::= { linkBundlingObjects 3 }
linkBundlingIsisTeEntry OBJECT-TYPE
SYNTAX LinkBundlingOspfTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created for every link bundle."
AUGMENTS { linkBundlingEntry }
::= { linkBundlingIsisTeTable 1 }
LinkBundlingIsisTeEntry ::= SEQUENCE {
linkBundlingIsisAdminColor Unsigned32 -- To be extended }
linkBundlingIsisAdminColor OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the IS-IS administrative color."
::= { linkBundlingIsisTeEntry 1 }
-- end of linkBundlingIsisTeTable
-- Link Bundling Shared Risk Link Group Table
linkBundlingSrlgTable OBJECT-TYPE
SYNTAX SEQUENCE OF LinkBundlingSrlgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the SRLGs associated with link
bundles."
::= { linkBundlingObjects 4 }
linkBundlingSrlgEntry OBJECT-TYPE
SYNTAX LinkBundlingSrlgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table contains information about a
SRLG associated with a link bundle."
INDEX { linkBundleId, srlg }
::= { linkBundlingSrlgTable 1 }
Dubuc et al. Expires August 2001 [Page 19]
Internet Draft MPLS Link Bundling MIB February 23, 2001
LinkBundlingSrlgEntry ::= SEQUENCE {
srlg Unsigned32,
srlgRowStatus RowStatus,
srlgStorageType StorageType }
srlg OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This identifies a SRLG supported by the link bundle."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { linkBundlingSrlgEntry 1 }
srlgRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { linkBundlingSrlgEntry 2 }
srlgStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { linkBundlingSrlgEntry 3 }
-- End of linkBundlingSrlgTable
-- Link Bundling Bandwidth Table
linkBundlingBandwidthTable OBJECT-TYPE
SYNTAX SEQUENCE OF LinkBundlingBandwidthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the priority-based bandwidth table
for bundled links."
Dubuc et al. Expires August 2001 [Page 20]
Internet Draft MPLS Link Bundling MIB February 23, 2001
::= { linkBundlingObjects 5 }
linkBundlingBandwidthEntry OBJECT-TYPE
SYNTAX LinkBundlingBandwidthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table contains information about
the priority-based bandwidth of link bundles."
INDEX { linkBundleId, linkBundlingPriority }
::= { linkBundlingBandwidthTable 1 }
LinkBundlingBandwidthEntry ::= SEQUENCE {
linkBundlingPriority Unsigned32,
linkBundlingUnreservedBandwidth Unsigned32,
linkBundlingMaximumLspBandwidth Unsigned32,
linkBundlingBandwidthRowStatus RowStatus,
linkBundlingBandwidthStorageType StorageType }
linkBundlingPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..8)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This attribute specifies the priority. It should be mapped
to a number between 0 and 7"
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { linkBundlingBandwidthEntry 1 }
linkBundlingUnreservedBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the link bundle unreserved
bandwidth at priority p. It is the sum of the unreserved
bandwidths at priority p of all component links associated
with the link bundle."
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingBandwidthEntry 2 }
Dubuc et al. Expires August 2001 [Page 21]
Internet Draft MPLS Link Bundling MIB February 23, 2001
linkBundlingMaximumLspBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the link bundle maximum
LSP bandwidth at priority p. It is the maximum of all
maximum LSP bandwidth at priority p of the component links
associated with the link bundle."
REFERENCE
"draft-kompella-mpls-bundle-04.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
November 2000."
::= { linkBundlingBandwidthEntry 3 }
linkBundlingBandwidthRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { linkBundlingBandwidthEntry 4 }
linkBundlingBandwidthStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { linkBundlingBandwidthEntry 5 }
-- End of linkBundlingBandwidthTable
-- Component Link Table
componentLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF ComponentLinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the component links traffic engineering
parameters."
::= { linkBundlingObjects 6 }
componentLinkEntry OBJECT-TYPE
Dubuc et al. Expires August 2001 [Page 22]
Internet Draft MPLS Link Bundling MIB February 23, 2001
SYNTAX ComponentLinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table contains traffic engineering information
about a specific component link. Note that compLinkBundleId
is not an index because a component link can exist
independently of a bundled link."
INDEX { compLinkEntityIfId }
::= { componentLinkTable 1 }
ComponentLinkEntry ::= SEQUENCE {
compLinkEntityIfId InterfaceIndex,
compLinkBundleId LinkBundleIdOrZero,
compLinkTrafficEngineeringMetric Unsigned32,
compLinkMuxCapability Unsigned32,
compLinkEncodingType Unsigned32,
compLinkMinimumReservableBandwidth Unsigned32,
compLinkMaximumReservableBandwidth Unsigned32,
compLinkProtectionType Unsigned32,
compLinkActivityStatus Unsigned32,
compLinkRowStatus RowStatus,
compLinkStorageType StorageType }
compLinkEntityIfId OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is a unique index for an entry in the
componentLinkTable. This value represents the
interface index for the component link. It points
to an interface in the ifTable and a data-bearing
link in the lmpDataBearingLinkTable."
::= { componentLinkEntry 1 }
compLinkBundleId OBJECT-TYPE
SYNTAX LinkBundleIdOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The link bundle identifier shows the association between
the componenent link and a bundled link defined in the
linkBundlingTable. The index also points to an entry in the
lmpTeLinkTable. A value of zero indicates that the component
link has not been assigned to any bundled link."
REFERENCE
"draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),
Dubuc et al. Expires August 2001 [Page 23]
Internet Draft MPLS Link Bundling MIB February 23, 2001
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin,
A. Banerjee, February 2001."
::= { componentLinkEntry 2 }
compLinkTrafficEngineeringMetric OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies the traffic engineering metric for
the component link."
::= { componentLinkEntry 5 }
compLinkMuxCapability OBJECT-TYPE
SYNTAX INTEGER {
packetSwitch1(1),
packetSwitch2(2),
packetSwitch3(3),
packetSwitch4(4),
layer2Switch(51),
tdm(100),
lambdaSwitch(150),
fiberSwitch(200)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies link multiplexing capabilities of the
component link."
REFERENCE
"draft-ietf-mpls-lsp-hierarchy-01.txt - LSP Hierarchy with
MPLS TE, K. Kompella, Y. Rekhter, September 2000."
::= { componentLinkEntry 7 }
compLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER {
standardSonet(1),
arbitrarySonet(2),
standardSdh(3),
arbitrarySdh(4),
clear(5),
gigE(6),
tenGigE(7)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
Dubuc et al. Expires August 2001 [Page 24]
Internet Draft MPLS Link Bundling MIB February 23, 2001
"This attribute specifies the component link encoding type."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { componentLinkEntry 8 }
compLinkMinimumReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the minimum reservable bandwidth on
the component link."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { componentLinkEntry 9 }
compLinkMaximumReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the maximum reservable bandwidth on
the component link."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { componentLinkEntry 10 }
compLinkProtectionType OBJECT-TYPE
SYNTAX INTEGER {
primary(1),
secondary(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies whether this data-bearing link is
a primary or secondary entity."
::= { componentLinkEntry 11 }
Dubuc et al. Expires August 2001 [Page 25]
Internet Draft MPLS Link Bundling MIB February 23, 2001
compLinkActivityStatus OBJECT-TYPE
SYNTAX INTEGER {
active(1),
standby(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies whether this component link is
currently active or in standby mode."
::= { componentLinkEntry 12 }
compLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { componentLinkEntry 13 }
compLinkStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { componentLinkEntry 14 }
-- End of componentLinkTable
-- Component Link OSPF Traffic Engineering Table
compLinkOspfTeTable OBJECT-TYPE
SYNTAX SEQUENCE OF CompLinkOspfTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the OSPF traffic engineering parameters
for component links."
::= { linkBundlingObjects 7 }
compLinkOspfTeEntry OBJECT-TYPE
SYNTAX CompLinkOspfTeEntry
MAX-ACCESS not-accessible
STATUS current
Dubuc et al. Expires August 2001 [Page 26]
Internet Draft MPLS Link Bundling MIB February 23, 2001
DESCRIPTION
"An entry in this table contains information about
OSPF taffic engineering parameters for component links."
AUGMENTS { componentLinkEntry }
::= { compLinkOspfTeTable 1 }
CompLinkOspfTeEntry ::= SEQUENCE {
compLinkOspfLinkType Unsigned32,
compLinkOspfLinkId RouterID,
compLinkOspfResourceClass OCTET STRING }
compLinkOspfLinkType OBJECT-TYPE
SYNTAX INTEGER {
pointToPoint(1),
multiAccess(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies the OSPF link type."
::= { compLinkOspfTeEntry 1 }
compLinkOspfLinkId OBJECT-TYPE
SYNTAX RouterID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"On point-to-point link, the link identifier is the Router ID
of the neighbor."
REFERENCE
"draft-ietf-mpls-lsp-hierarchy-01.txt - LSP Hierarchy with
MPLS TE, K. Kompella, Y. Rekhter, September 2000."
::= { compLinkOspfTeEntry 2 }
compLinkOspfResourceClass OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies the component link resource class.
It is a 32 bit bitfield. A link that is member of multiple
groups will have multiple bits set."
REFERENCE
"draft-katz-leung-ospf-traffic-02.txt - Traffic Engineering
Extensions to OSPF, D. Katz, D. Leung, September 2000."
::= { compLinkOspfTeEntry 3 }
-- end of Component Link OSPF Traffic Engineering Table
Dubuc et al. Expires August 2001 [Page 27]
Internet Draft MPLS Link Bundling MIB February 23, 2001
-- Component Link IS-IS Traffic Engineering Table
compLinkIsisTeTable OBJECT-TYPE
SYNTAX SEQUENCE OF CompLinkIsisTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the IS-IS traffic engineering parameters
for component links."
::= { linkBundlingObjects 8 }
compLinkIsisTeEntry OBJECT-TYPE
SYNTAX CompLinkIsisTeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table contains information about
IS-IS taffic engineering parameters for component links."
AUGMENTS { componentLinkEntry }
::= { compLinkIsisTeTable 1 }
CompLinkIsisTeEntry ::= SEQUENCE {
compLinkIsisAdminColor Unsigned32 -- To be extended }
compLinkIsisAdminColor OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute specifies the IS-IS administrative color."
::= { compLinkIsisTeEntry 1 }
-- end of Component Link OSPF Traffic Engineering Table
-- Component Link Bandwidth Table
compLinkBandwidthTable OBJECT-TYPE
SYNTAX SEQUENCE OF CompLinkBandwidthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the priority-based bandwidth
for component links."
::= { linkBundlingObjects 9 }
compLinkBandwidthEntry OBJECT-TYPE
SYNTAX CompLinkBandwidthEntry
Dubuc et al. Expires August 2001 [Page 28]
Internet Draft MPLS Link Bundling MIB February 23, 2001
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table contains information about
the priority-based bandwidth on component links."
INDEX { compLinkEntityIfId, compLinkBwPriority }
::= { compLinkBandwidthTable 1 }
CompLinkBandwidthEntry ::= SEQUENCE {
compLinkBwPriority Unsigned32,
compLinkBwUnreservedBandwidth Unsigned32,
compLinkBwMaximumLspBandwidth Unsigned32,
compLinkBwRowStatus RowStatus,
compLinkBwStorageType StorageType }
compLinkBwPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..8)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This attribute specifies the priority. It should be mapped
to a number between 0 and 7."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { compLinkBandwidthEntry 1 }
compLinkBwUnreservedBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies the component link unreserved
bandwidth at priority p."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { compLinkBandwidthEntry 2 }
compLinkBwMaximumLspBandwidth OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Dubuc et al. Expires August 2001 [Page 29]
Internet Draft MPLS Link Bundling MIB February 23, 2001
"This attribute specifies the component link maximum
LSP bandwidth at priority p."
REFERENCE
"draft-kompella-ospf-gmpls-extensions-00.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, November 2000."
::= { compLinkBandwidthEntry 3 }
compLinkBwRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { compLinkBandwidthEntry 4 }
compLinkBwStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { compLinkBandwidthEntry 5 }
-- End of compLinkBandwidthTable
-- Notification Configuration
linkBundlingTrapEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, then it enables the
generation of the link bundling traps,
otherwise these traps are not emitted."
DEFVAL { false }
::= { linkBundlingObjects 10 }
-- Notifications
linkBundlingNotifyPrefix OBJECT IDENTIFIER ::= { linkBundlingNotifica-
tions 0 }
Dubuc et al. Expires August 2001 [Page 30]
Internet Draft MPLS Link Bundling MIB February 23, 2001
-- Bundled Link Traps
linkBundleUp NOTIFICATION-TYPE
OBJECTS { linkBundleId }
STATUS current
DESCRIPTION
"This notification is generated when a bundled link goes up.
A bundle link is considered to be up if it has enough
operational component links to serve the number of primary
component links that it contains."
::= { linkBundlingNotifyPrefix 1 }
linkBundleDown NOTIFICATION-TYPE
OBJECTS { linkBundleId }
STATUS current
DESCRIPTION
"This notification is generated when a bundled link goes down.
A bundle link is considered to be down if it cannot service
the number of primary component links that it contains."
::= { linkBundlingNotifyPrefix 2 }
-- End of notifications
-- Module compliance
linkBundlingGroups
OBJECT IDENTIFIER ::= { linkBundlingConformance 1 }
linkBundlingCompliances
OBJECT IDENTIFIER ::= { linkBundlingConformance 2 }
linkBundlingModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that support the
link bundling MIB."
MODULE -- this module
-- The mandatory groups have to be implemented
-- by all devices supporting link bundling. However, they may all
-- be supported as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { linkBundlingGroup,
linkBundlingOspfTeGroup,
linkBundlingIsisTeGroup,
linkBundlingBandwidthGroup }
Dubuc et al. Expires August 2001 [Page 31]
Internet Draft MPLS Link Bundling MIB February 23, 2001
GROUP linkBundlingOspfTeGroup
DESCRIPTION
"This group is mandatory for OSPF enabled devices."
GROUP linkBundlingIsisTeGroup
DESCRIPTION
"This group is mandatory for IS-IS enabled devices."
GROUP linkBundlingSrlgGroup
DESCRIPTION
"This group is mandatory for G-MPLS enabled devices."
-- linkBundlingTable
OBJECT linkBundleParent
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT linkBundlingCompLinkFlooding
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT linkBundlingRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) state need not be supported."
OBJECT linkBundlingStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- linkBundlingOspfTeTable
OBJECT linkBundlingOspfLinkId
SYNTAX INTEGER { pointToPoint(1) }
MIN-ACCESS read-only
DESCRIPTION
"A value of multiAccess(2) need not be supported."
-- linkBundlingSrlgTable
OBJECT srlgRowStatus
Dubuc et al. Expires August 2001 [Page 32]
Internet Draft MPLS Link Bundling MIB February 23, 2001
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT srlgStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- linkBundlingBandwidthTable
OBJECT linkBundlingBandwidthRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT linkBundlingBandwidthStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- componentLinkTable
OBJECT compLinkTrafficEngineeringMetric
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT compLinkProtectionType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT compLinkOspfLinkId
SYNTAX INTEGER { pointToPoint(1) }
MIN-ACCESS read-only
DESCRIPTION
"A value of multiAccess(2) need not be supported."
OBJECT compLinkOspfResourceClass
Dubuc et al. Expires August 2001 [Page 33]
Internet Draft MPLS Link Bundling MIB February 23, 2001
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT compLinkIsisAdminColor
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT compLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT compLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- compLinkBandwidthTable
OBJECT compLinkBwRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT compLinkBwStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
::= { linkBundlingCompliances 1 }
-- Units of conformance
linkBundlingGroup OBJECT-GROUP
OBJECTS { linkBundleType,
linkBundleParent,
linkBundlingTeMetric,
linkBundlingMuxCapability,
Dubuc et al. Expires August 2001 [Page 34]
Internet Draft MPLS Link Bundling MIB February 23, 2001
linkBundlingProtectionType,
linkBundlingIncomingIfId,
linkBundlingOutgoingIfId,
linkBundlingMinReservableBandwidth,
linkBundlingMaxReservableBandwidth,
linkBundlingCompLinkFlooding,
linkBundlingAdminStatus,
linkBundlingOperStatus,
linkBundlingRowStatus,
linkBundlingStorageType,
compLinkTrafficEngineeringMetric,
compLinkMuxCapability,
compLinkEncodingType,
compLinkMinimumReservableBandwidth,
compLinkMaximumReservableBandwidth,
compLinkProtectionType,
compLinkActivityStatus,
compLinkOspfLinkType,
compLinkOspfLinkId,
compLinkOspfResourceClass,
compLinkIsisAdminColor,
compLinkRowStatus,
compLinkStorageType,
linkBundlingTrapEnable
}
STATUS current
DESCRIPTION
"Collection of objects needed for the monitoring of
resources associated with bundled links."
::= { linkBundlingGroups 1 }
linkBundlingOspfTeGroup OBJECT-GROUP
OBJECTS { linkBundlingOspfLinkType,
linkBundlingOspfLinkId,
linkBundlingOspfResourceClass,
compLinkOspfLinkType,
compLinkOspfLinkId,
compLinkOspfResourceClass
}
STATUS current
DESCRIPTION
"Collection of objects needed for the OSPF traffic
engineering parameters of bundled links and component
links."
::= { linkBundlingGroups 2 }
Dubuc et al. Expires August 2001 [Page 35]
Internet Draft MPLS Link Bundling MIB February 23, 2001
linkBundlingIsisTeGroup OBJECT-GROUP
OBJECTS { linkBundlingIsisAdminColor,
compLinkIsisAdminColor }
STATUS current
DESCRIPTION
"Collection of objects needed for the IS-IS traffic
engineering parameters of bundled links and component
links."
::= { linkBundlingGroups 3 }
linkBundlingSrlgGroup OBJECT-GROUP
OBJECTS { srlgRowStatus,
srlgStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the monitoring of
SRLG resources associated with link bundle."
::= { linkBundlingGroups 4 }
linkBundlingBandwidthGroup OBJECT-GROUP
OBJECTS { linkBundlingUnreservedBandwidth,
linkBundlingMaximumLspBandwidth,
linkBundlingBandwidthRowStatus,
linkBundlingBandwidthStorageType,
compLinkBwUnreservedBandwidth,
compLinkBwMaximumLspBandwidth,
compLinkBwRowStatus,
compLinkBwStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the monitoring of
the priority-based bandwidth resources associated with
link bundles and component links."
::= { linkBundlingGroups 5 }
linkBundlingNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { linkBundleUp,
linkBundleDown }
STATUS current
DESCRIPTION
"Set of notifications implemented in this module.
None is mandatory."
::= { linkBundlingGroups 6 }
Dubuc et al. Expires August 2001 [Page 36]
Internet Draft MPLS Link Bundling MIB February 23, 2001
-- End of LINK-BUNDLING-MIB END
10. Security Considerations
It is clear that this MIB is potentially useful for monitoring of
link bundling enabled devices. This MIB can also be used for confi-
guration of certain objects, and anything that can be configured can
be incorrectly configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond those
that SNMP Security [SNMPArch] is itself intended to address. These
relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera-
tor error, which is beyond the scope of any security architecture.
There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network
operations. The use of SNMP Version 3 is recommended over prior ver-
sions, for configuration control, as its security model is improved.
SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if
the network itself is secure (for example by using IPSec [IPSEC]),
there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this
MIB. It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [SNMPv3USM] and the View-based
Access Control [SNMPv3VACM] is recommended. It is then a
customer/user responsibility to ensure that the SNMP entity giving
access to an instance of this MIB is properly configured to give
access to the objects only to those principals (users) that have leg-
itimate rights to indeed GET or SET (change/create/delete) them.
There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in
that they represent a customer's interface to the OSPF/MPLS network.
Allowing uncontrolled access to these objects could result in mali-
cious and unwanted disruptions of network traffic or incorrect confi-
gurations for these customers. There are no objects that are particu-
larly sensitive in their own right, such as passwords or monetary
amounts.
Dubuc et al. Expires August 2001 [Page 37]
Internet Draft MPLS Link Bundling MIB February 23, 2001
11. Acknowledgments
The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt.
12. References
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-kompella-mpls-bundle-04.txt>,
November 2000.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B.,
Basak, D., Sandick, H., Zinin, A., and
Banarjee, A., "Link Management Protocol",
Internet Draft <draft-ietf-mpls-lmp-02.txt>,
February 2001.
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Function Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-00.txt>,
October 2000.
[OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to
OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-03.txt>, September 2000.
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", Internet
Draft
<draft-kompella-ospf-gmpls-extensions-00.txt>,
November 2000.
[LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE,
Internet Draft <draft-ietf-mpls-lsp-hierarchy-01.txt>,
September 2000.
[ZININ] Zinin, A., SHand, M., "Flooding optimizations in link-
state routing protocols", Internet Draft,
<draft-ietf-ospf-isis-flood-opt-00.txt>, October 2000.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
Dubuc et al. Expires August 2001 [Page 38]
Internet Draft MPLS Link Bundling MIB February 23, 2001
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.
[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,
Dubuc et al. Expires August 2001 [Page 39]
Internet Draft MPLS Link Bundling MIB February 23, 2001
"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
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.
Dubuc et al. Expires August 2001 [Page 40]
Internet Draft MPLS Link Bundling MIB February 23, 2001
[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 Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
13. Authors' Addresses
Martin Dubuc Sudheer Dharanikota
edgeflow, Inc. Nayna Networks, Inc.
329 March Rd. 157 Topaz Street
Kanata, ON, CANADA K2K 2E1 Milipitas, CA 95035
Phone: +1-613-270-9279 x253 Phone: +1-408-956-8000 x357
Email: martin.dubuc@edgeflow.com Email: sudheer@nayna.com
Thomas D. Nadeau
Cisco Systems, Inc.
350 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
14. 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
Dubuc et al. Expires August 2001 [Page 41]
Internet Draft MPLS Link Bundling MIB February 23, 2001
included on all such copies and derivative works. However, this docu-
ment 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 develop-
ing 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.
Dubuc et al. Expires August 2001 [Page 42]