draft-ietf-mpls-telink-mib-01.txt   draft-ietf-mpls-telink-mib-02.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Internet Draft
Category: Standards Track Sudheer Dharanikota Category: Standards Track Sudheer Dharanikota
Expires: October 2003 Avici Systems Expires: November 2003 Avici Systems
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
April 2003 May 2003
Traffic Engineering Link Management Information Base Traffic Engineering Link Management Information Base
draft-ietf-mpls-telink-mib-01.txt draft-ietf-mpls-telink-mib-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 15 skipping to change at page 2, line 15
1. The Internet-Standard Management Framework . . . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4
6.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4 6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4
6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4 6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4
6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4
6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 4
6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5
6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5
7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5
8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9
8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9
8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11
9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 12 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13
10. Intellectual Property Considerations . . . . . . . . . . . . . . 43 10. Intellectual Property Considerations . . . . . . . . . . . . . . 42
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 43 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 42
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 44 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 43
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 44 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 43
13.2 Informative References . . . . . . . . . . . . . . . . . . . . 45 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 44
14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 46 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 45
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 27 skipping to change at page 4, line 27
the TE links. the TE links.
- Configuring the component links including the bandwidth - Configuring the component links including the bandwidth
parameters and associating the component links with the parameters and associating the component links with the
appropriate TE link. appropriate TE link.
- Associating the TE links with the appropriate bundled link. - Associating the TE links with the appropriate bundled link.
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
Sections 6.1-6.5 describe objects pertaining to TE links. The MIB Sections 6.1-6.4 describe objects pertaining to TE links. The MIB
objects were derived from the link bundling document [BUNDLING]. objects were derived from the link bundling document [BUNDLING].
6.1. teLinkTable 6.1. teLinkTable
This table represents the TE links, including bundled links, and This table represents the TE links, including bundled links, and
their generic traffic engineering parameters. their generic traffic engineering parameters.
6.2. teLinkDescriptorTable 6.2. teLinkDescriptorTable
This table represents the TE link descriptors. This table represents the TE link descriptors.
skipping to change at page 5, line 39 skipping to change at page 5, line 39
widthTable (maximum/minimum reservable bandwidth and unreserved band- widthTable (maximum/minimum reservable bandwidth and unreserved band-
width). width).
7. Example of Bundled Link Setup 7. Example of Bundled Link Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in section 10 to set up a bundled link. objects described in section 10 to set up a bundled link.
While this example is not meant to illustrate every nuance of the While this example is not meant to illustrate every nuance of the
MIB module, it is intended as an aid to understanding some MIB module, it is intended as an aid to understanding some
of the key concepts. It is meant to be read after going through the of the key concepts. It is meant to be read after going through the
MIB module itself. MIB module itself. More details on the use of the ifStackTable
to establish relationship between bundled links, TE links and
component links are given in Section 8.2.
Suppose that one would like to manually create a bundled link Suppose that one would like to manually create a bundled link
out of two 1:1 TE links. Assume that the bundled link is associated out of two 1:1 TE links as depicted on the figure in Section 8.2.
with SRLGs 10 and 50. Finally, let the component links be port Assume that the bundled link is associated with SRLGs 10 and 50.
entity interfaces (lambdas). The following example illustrates which Finally, let the component links be port entity interfaces
rows and corresponding objects might be created to accomplish this. (lambdas). The following example illustrates which rows and
corresponding objects might be created to accomplish this.
First, a bundled link entry is created. An ifEntry with the same First, a bundled link entry is created. An ifEntry with the same
ifIndex and with ifType teLink needs to be created beforehand. ifIndex and with ifType teLink needs to be created beforehand.
In teLinkTable: In teLinkTable:
{ {
ifIndex = 25, ifIndex = 2,
teLinkAddressType = unknown(0), teLinkAddressType = unknown(0),
teLinkRowStatus = createAndGo(4) teLinkLocalIpAddr = ''H,
teLinkRemoteIpAddr = ''H,
teLinkMetric = 5,
teLinkMuxCapability = lambdaSwitch(150),
teLinkProtectionType = dedicated1For1(4),
teLinkWorkingPriority = 7,
teLinkResourceClass = 3,
teLinkIncomingIfId = 0,
teLinkOutgoingIfId = 2,
teLinkRowStatus = createAndGo(4),
teLinkStorageType = nonVolatile(3)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 0, ifStackHigherLayer = 0,
ifStackLowerLayer = 25, ifStackLowerLayer = 2,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
Next, the two TE links are created. Next, the two TE links are created.
In teLinkTable: In teLinkTable:
{ {
ifIndex = 20, ifIndex = 3,
teLinkAddressType = unknown(0), teLinkAddressType = unknown(0),
teLinkLocalIpAddr = ''H,
teLinkRemoteIpAddr = ''H,
teLinkMetric = 5, teLinkMetric = 5,
teLinkMuxCapability = lambdaSwitch(150),
teLinkProtectionType = unprotected(2),
teLinkWorkingPriority = 7,
teLinkResourceClass = 3, teLinkResourceClass = 3,
teLinkRowStatus = createAndWait(5) teLinkIncomingIfId = 0,
teLinkOutgoingIfId = 3,
teLinkRowStatus = createAndGo(4),
teLinkStorageType = nonVolatile(3)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 25, ifStackHigherLayer = 2,
ifStackLowerLayer = 20, ifStackLowerLayer = 3,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In teLinkTable: In teLinkTable:
{ {
ifIndex = 21, ifIndex = 4,
teLinkAddressType = unknown(0), teLinkAddressType = unknown(0),
teLinkLocalIpAddr = ''H,
teLinkRemoteIpAddr = ''H,
teLinkMetric = 5, teLinkMetric = 5,
teLinkMuxCapability = lambdaSwitch(150),
teLinkProtectionType = unprotected(2),
teLinkWorkingPriority = 7,
teLinkResourceClass = 3, teLinkResourceClass = 3,
teLinkRowStatus = createAndWait(5) teLinkIncomingIfId = 0,
teLinkOutgoingIfId = 4,
teLinkRowStatus = createAndGo(4),
teLinkStorageType = nonVolatile(3)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 25, ifStackHigherLayer = 2,
ifStackLowerLayer = 21, ifStackLowerLayer = 4,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
We assign SRLGs to the TE links. We assign SRLGs to the TE links.
In the teLinkSrlgTable: In the teLinkSrlgTable:
{ {
ifIndex = 20, ifIndex = 3,
srlg = 10, teSrlg = 10,
srlgRowStatus = createAndGo(4) teSrlgRowStatus = createAndGo(4),
teSrlgStorageType = nonVolatile(3)
} }
In the teLinkSrlgTable: In the teLinkSrlgTable:
{ {
ifIndex = 21, ifIndex = 4,
srlg = 50, teSrlg = 50,
srlgRowStatus = createAndGo(4) teSrlgRowStatus = createAndGo(4),
teSrlgStorageType = nonVolatile(3)
} }
The bundled link inherits the SRLG properties from the The bundled link inherits the SRLG properties from the
associated TE links. associated TE links.
Next, for each TE link, two component links are created. Next, for each unbundled TE link, a component link is created.
An ifEntry with the same ifIndex needs to be created beforehand.
In componentLinkTable:
{
ifIndex = 40,
componentLinkPreferredProtection = primary(1),
componentLinkRowStatus = createAndGo(4)
}
In ifStackTable:
{
ifStackHigherLayer = 20,
ifStackLowerLayer = 40,
ifStackStatus = createAndGo(4)
}
In componentLinkTable:
{
ifIndex = 43,
componentLinkPreferredProtection = secondary(2),
componentLinkRowStatus = createAndGo(4)
}
In ifStackTable: An ifEntry with the same ifIndex needs to be created beforehand.
{
ifStackHigherLayer = 20,
ifStackLowerLayer = 43,
ifStackStatus = createAndGo(4)
}
In componentLinkTable: In componentLinkTable:
{ {
ifIndex = 44, ifIndex = 5,
componentLinkMuxCapability = lambdaSwitch(150),
componentLinkPreferredProtection = primary(1), componentLinkPreferredProtection = primary(1),
componentLinkRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4),
componentLinkStorageType = nonVolatile(3)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 21, ifStackHigherLayer = 3,
ifStackLowerLayer = 44, ifStackLowerLayer = 5,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In componentLinkTable: In componentLinkTable:
{ {
ifIndex = 48, ifIndex = 6,
componentLinkMuxCapability = lambdaSwitch(150),
componentLinkPreferredProtection = secondary(2), componentLinkPreferredProtection = secondary(2),
componentLinkRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4)
componentLinkStorageType = nonVolatile(3)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 21, ifStackHigherLayer = 4,
ifStackLowerLayer = 48, ifStackLowerLayer = 6,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In this example, once a component link is added to the In this example, once a component link is added to the
componentLinkTable, the associated link descriptors are componentLinkTable, the associated link descriptors are
implicitly added to the componentLinkDescriptorTable. implicitly added to the componentLinkDescriptorTable.
TE link link descriptors are derived from their component link TE link link descriptors are derived from their component link
descriptors. descriptors.
skipping to change at page 11, line 23 skipping to change at page 11, line 32
Example: MPLS is being carried on a bundled TE links. Example: MPLS is being carried on a bundled TE links.
The bundled TE link represents a 1:1 optical The bundled TE link represents a 1:1 optical
transport interface. transport interface.
In this example, the component link is a TE link. The two component In this example, the component link is a TE link. The two component
links/TE links are grouped in a bundled link. links/TE links are grouped in a bundled link.
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
| MPLS interface ifType = mpls(166) | | MPLS interface ifType = mpls(166) |
| ifIndex = 1 |
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
| TE link (bundled link) ifType = teLink(200) | | TE link (bundled link) ifType = teLink(200) |
| ifIndex = 2 |
+--------------------------------+-+--------------------------------+ +--------------------------------+-+--------------------------------+
| TE link ifType = teLink(200) | | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | | TE link ifType = teLink(200) |
| ifIndex = 3 | | ifIndex = 4 |
+--------------------------------+ +--------------------------------+ +--------------------------------+ +--------------------------------+
| Component link | | Component link | | Component link | | Component link |
| ifType = opticalTransport(196) | | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | | ifType = opticalTransport(196) |
| ifIndex = 5 | | ifIndex = 6 |
+--------------------------------+ +--------------------------------+ +--------------------------------+ +--------------------------------+
The assignment of the index values could for example be: The assignment of the index values could for example be:
ifIndex Description ifIndex Description
1 mpls (type 166) 1 mpls (type 166)
2 teLink (type 200) 2 teLink (type 200)
3 teLink (type 200) 3 teLink (type 200)
4 teLink (type 200) 4 teLink (type 200)
5 opticalTransport (type 196) 5 opticalTransport (type 196)
skipping to change at page 12, line 40 skipping to change at page 13, line 7
ifStackTable Entries ifStackTable Entries
HigherLayer LowerLayer HigherLayer LowerLayer
0 1 0 1
1 2 1 2
2 3 2 3
3 0 3 0
9. TE Link MIB Module Definitions 9. TE Link MIB Module Definitions
TE-LINK-MIB DEFINITIONS ::= BEGIN TE-LINK-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, transmission, Unsigned32
mib-2, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType TEXTUAL-CONVENTION, RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
teLinkMIB MODULE-IDENTITY teLinkStdMIB MODULE-IDENTITY
LAST-UPDATED "200304291200Z" -- 29 April 2003 12:00:00 EST LAST-UPDATED "200305211200Z" -- 21 May 2003 12:00:00 EST
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@rogers.com
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@avici.com Email: sudheer@avici.com
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 13, line 39 skipping to change at page 14, line 4
the MPLS working group mailing list at mpls@uu.net." the MPLS working group mailing list at mpls@uu.net."
DESCRIPTION DESCRIPTION
"Copyright (C) 2003 The Internet Society. This version of "Copyright (C) 2003 The Internet Society. This version of
this MIB module is part of RFCXXXX; see the RFC this MIB module is part of RFCXXXX; see the RFC
itself for full legal notices. itself for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
MPLS traffic engineering links as defined in MPLS traffic engineering links as defined in
'Link Bundling in MPLS Traffic Engineering'." 'Link Bundling in MPLS Traffic Engineering'."
-- Revision history. -- Revision history.
REVISION REVISION
"200304291200Z" -- 29 April 2003 12:00:00 EST "200305211200Z" -- 21 May 2003 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC Editor)" "Initial version published as RFC xxxx (to be assigned by RFC
::= { mib-2 xxx } -- To be assigned by IANA (experimental 114 can be used Editor)"
-- in the interim) ::= { transmission xxx } -- To be assigned by IANA (experimental 114
-- can be used in the interim)
-- Textual Conventions -- Textual Conventions
Priority ::= TEXTUAL-CONVENTION TeLinkPriority ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to represent a priority. Each connection is "This type is used to represent a priority. Each connection is
assigned a priority. This priority is used when accounting for assigned a priority. This priority is used when accounting for
bandwidth on TE links or component links, for resource allocation bandwidth on TE links or component links, for resource
and for rerouting purposes. Value 0 is the highest priority. allocation and for rerouting purposes. Value 0 is the highest
Value 7 is the lowest priority." priority. Value 7 is the lowest priority."
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
LinkProtection ::= TEXTUAL-CONVENTION TeLinkProtection ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Link protection." "Link protection."
SYNTAX INTEGER { SYNTAX INTEGER {
primary(1), primary(1),
secondary(2) secondary(2)
} }
SwitchingCapability ::= TEXTUAL-CONVENTION TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Switching capability as specified in the 'OSPF Extensions in "Switching capability as specified in the 'OSPF Extensions in
Support of Generalized MPLS' document. The values specified in Support of Generalized MPLS' document. The values specified in
this document are not contiguous." this document are not contiguous."
SYNTAX INTEGER { SYNTAX INTEGER {
packetSwitch1(1), packetSwitch1(1),
packetSwitch2(2), packetSwitch2(2),
packetSwitch3(3), packetSwitch3(3),
packetSwitch4(4), packetSwitch4(4),
layer2Switch(51), layer2Switch(51),
tdm(100), tdm(100),
lambdaSwitch(150), lambdaSwitch(150),
fiberSwitch(200) fiberSwitch(200)
} }
LinkEncodingType ::= TEXTUAL-CONVENTION TeLinkEncodingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Link encoding type as specified in 'GMPLS Signaling Functional "Link encoding type as specified in 'GMPLS Signaling Functional
Description' document. The values specified in this document are Description' document. The values specified in this document are
not contiguous." not contiguous."
SYNTAX INTEGER { SYNTAX INTEGER {
packet(1), packet(1),
ethernet(2), ethernet(2),
ansiEtsiPdh(3), ansiEtsiPdh(3),
sdhItuSonetAnsi(5), sdhItuSonetAnsi(5),
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
-- Top level components of this MIB module -- Top level components of this MIB module
-- Notifications -- Notifications
teLinkNotifications OBJECT IDENTIFIER ::= { teLinkMIB 0 } teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 }
-- Tables, Scalars -- Tables, Scalars
teLinkObjects OBJECT IDENTIFIER ::= { teLinkMIB 1 } teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 }
-- Conformance -- Conformance
teLinkConformance OBJECT IDENTIFIER ::= { teLinkMIB 2 } teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 }
-- TE Link Table -- TE Link Table
teLinkTable OBJECT-TYPE teLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkEntry SYNTAX SEQUENCE OF TeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the grouping of component links into "This table specifies the grouping of component links into
TE links and grouping of TE links into bundled links." TE links and grouping of TE links into bundled links."
skipping to change at page 15, line 50 skipping to change at page 16, line 13
teLinkTable. The administrative and operational status values teLinkTable. The administrative and operational status values
are controlled from the ifEntry." are controlled from the ifEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { teLinkTable 1 } ::= { teLinkTable 1 }
TeLinkEntry ::= SEQUENCE { TeLinkEntry ::= SEQUENCE {
teLinkAddressType InetAddressType, teLinkAddressType InetAddressType,
teLinkLocalIpAddr InetAddress, teLinkLocalIpAddr InetAddress,
teLinkRemoteIpAddr InetAddress, teLinkRemoteIpAddr InetAddress,
teLinkMetric Unsigned32, teLinkMetric Unsigned32,
teLinkMuxCapability SwitchingCapability, teLinkMuxCapability TeLinkSwitchingCapability,
teLinkProtectionType INTEGER, teLinkProtectionType INTEGER,
teLinkWorkingPriority Priority, teLinkWorkingPriority TeLinkPriority,
teLinkResourceClass Unsigned32, teLinkResourceClass Unsigned32,
teLinkIncomingIfId InterfaceIndexOrZero, teLinkIncomingIfId InterfaceIndexOrZero,
teLinkOutgoingIfId InterfaceIndexOrZero, teLinkOutgoingIfId InterfaceIndexOrZero,
teLinkRowStatus RowStatus, teLinkRowStatus RowStatus,
teLinkStorageType StorageType teLinkStorageType StorageType
} }
teLinkAddressType OBJECT-TYPE teLinkAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 16, line 26 skipping to change at page 16, line 37
DESCRIPTION DESCRIPTION
"The type of Internet address for the TE link. Only IPv4, "The type of Internet address for the TE link. Only IPv4,
IPv6 and unknown (for unnumbered links) need to be supported." IPv6 and unknown (for unnumbered links) need to be supported."
::= { teLinkEntry 1 } ::= { teLinkEntry 1 }
teLinkLocalIpAddr OBJECT-TYPE teLinkLocalIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For IPv4 and IPv6 numbered links, this object represents the "The local Internet address for numbered links. The type of this
local IP address associated with the TE link. For unnumbered address is determined by the value of the teLinkAddressType
link, the local address is not stored in this object, but object.
rather in the teLinkOutgoingIfId object."
For IPv4 and IPv6 numbered links, this object represents the
local IP address associated with the TE link. For an
unnumbered link, the local address is of type unknown and this
object is set to the zero length string and the
teLinkOutgoingIfId object then identifies the unnumbered
address."
::= { teLinkEntry 2 } ::= { teLinkEntry 2 }
teLinkRemoteIpAddr OBJECT-TYPE teLinkRemoteIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote IP address associated with the TE link (IPv4 and "The remote Internet address for numbered links. The type of
IPv6 numbered links). For unnumbered links, the remote address this address is determined by the value of the
is not stored in this object, but rather in the teLinkAddressType object.
teLinkIncomingIfId object."
The remote IP address associated with the TE link (IPv4 and
IPv6 numbered links). For an unnumbered link, the remote
address is of type unknown and this object is set to the
zero length string and the teLinkIncomingIfId object then
identifies the unnumbered address."
::= { teLinkEntry 3 } ::= { teLinkEntry 3 }
teLinkMetric OBJECT-TYPE teLinkMetric OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The traffic engineering metric for the TE link is "The traffic engineering metric for the TE link is
derived from its component links. All component links derived from its component links. All component links
within the TE link must have the same traffic within the TE link must have the same traffic
engineering metric." engineering metric."
REFERENCE REFERENCE
"Link Bundling in MPLS Traffic Engineering, RFC xxxx" "Link Bundling in MPLS Traffic Engineering, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [BUNDLING] -- [BUNDLING]
::= { teLinkEntry 4 } ::= { teLinkEntry 4 }
teLinkMuxCapability OBJECT-TYPE teLinkMuxCapability OBJECT-TYPE
SYNTAX SwitchingCapability SYNTAX TeLinkSwitchingCapability
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link multiplex capability of the "This attribute specifies link multiplex capability of the
TE link, which is derived from its component links. All TE link, which is derived from its component links. All
component links within the same TE link must have the component links within the same TE link must have the
same link multiplex capability." same link multiplex capability."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
skipping to change at page 17, line 49 skipping to change at page 18, line 23
found in the 'Routing Extensions in Support of Generalized found in the 'Routing Extensions in Support of Generalized
MPLS' document." MPLS' document."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and
Routing Extensions in Support of Generalized MPLS, RFC xxxx" Routing Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] and [ROUTING] -- [GMPLS-OSPF] and [ROUTING]
::= { teLinkEntry 6 } ::= { teLinkEntry 6 }
teLinkWorkingPriority OBJECT-TYPE teLinkWorkingPriority OBJECT-TYPE
SYNTAX Priority SYNTAX TeLinkPriority
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents a priority value such that a new "This object represents a priority value such that a new
connection with a higher priority, i.e. numerically lower than connection with a higher priority, i.e. numerically lower than
this value, is guaranteed to be setup on a primary link and this value, is guaranteed to be setup on a primary link and
not on a secondary link." not on a secondary link."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
skipping to change at page 20, line 22 skipping to change at page 20, line 43
teLinkDescriptorEntry using the same ifIndex is created. teLinkDescriptorEntry using the same ifIndex is created.
ifType of ifEntry must be teLink(200). ifType of ifEntry must be teLink(200).
If a TE link entry in the ifTable is destroyed, then so are all If a TE link entry in the ifTable is destroyed, then so are all
entries in the teLinkDescriptorTable that use the ifIndex of entries in the teLinkDescriptorTable that use the ifIndex of
this TE link." this TE link."
INDEX { ifIndex, teLinkDescriptorId } INDEX { ifIndex, teLinkDescriptorId }
::= { teLinkDescriptorTable 1 } ::= { teLinkDescriptorTable 1 }
TeLinkDescriptorEntry ::= SEQUENCE { TeLinkDescriptorEntry ::= SEQUENCE {
teLinkDescriptorId Unsigned32, teLinkDescriptorId Unsigned32,
teLinkDescrEncodingType LinkEncodingType, teLinkDescrEncodingType TeLinkEncodingType,
teLinkDescrPriority Priority, teLinkDescrPriority TeLinkPriority,
teLinkDescrMinResBandwidth Unsigned32, teLinkDescrMinResBandwidth Unsigned32,
teLinkDescrMaxResBandwidth Unsigned32, teLinkDescrMaxResBandwidth Unsigned32,
teLinkDescrRowStatus RowStatus, teLinkDescrRowStatus RowStatus,
teLinkDescrStorageType StorageType teLinkDescrStorageType StorageType
} }
teLinkDescriptorId OBJECT-TYPE teLinkDescriptorId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the link descriptor identifier." "This object specifies the link descriptor identifier."
::= { teLinkDescriptorEntry 1 } ::= { teLinkDescriptorEntry 1 }
teLinkDescrEncodingType OBJECT-TYPE teLinkDescrEncodingType OBJECT-TYPE
SYNTAX LinkEncodingType SYNTAX TeLinkEncodingType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link encoding type." "This attribute specifies the TE link encoding type."
REFERENCE REFERENCE
"Generalized MPLS Signaling Functional Description, RFC 3471" "Generalized MPLS Signaling Functional Description, RFC 3471"
::= { teLinkDescriptorEntry 2 } ::= { teLinkDescriptorEntry 2 }
teLinkDescrPriority OBJECT-TYPE teLinkDescrPriority OBJECT-TYPE
SYNTAX Priority SYNTAX TeLinkPriority
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lowest priority at which that link "This object specifies the lowest priority at which that link
encoding type is available." encoding type is available."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] -- [GMPLS-OSPF]
::= { teLinkDescriptorEntry 3 } ::= { teLinkDescriptorEntry 3 }
skipping to change at page 22, line 45 skipping to change at page 23, line 20
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about a "An entry in this table contains information about a
SRLG associated with a TE link. SRLG associated with a TE link.
An ifEntry in the ifTable must exist before a An ifEntry in the ifTable must exist before a
teLinkSrlgEntry using the same ifIndex is created. teLinkSrlgEntry using the same ifIndex is created.
ifType of ifEntry must be teLink(200). ifType of ifEntry must be teLink(200).
If a TE link entry in the ifTable is destroyed, then so are all If a TE link entry in the ifTable is destroyed, then so are all
entries in the teLinkSrlgTable that use the ifIndex of entries in the teLinkSrlgTable that use the ifIndex of
this TE link." this TE link."
INDEX { ifIndex, srlg } INDEX { ifIndex, teSrlg }
::= { teLinkSrlgTable 1 } ::= { teLinkSrlgTable 1 }
TeLinkSrlgEntry ::= SEQUENCE { TeLinkSrlgEntry ::= SEQUENCE {
srlg Unsigned32, teSrlg Unsigned32,
srlgRowStatus RowStatus, teSrlgRowStatus RowStatus,
srlgStorageType StorageType teSrlgStorageType StorageType
} }
srlg OBJECT-TYPE teSrlg OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This identifies a SRLG supported by the TE link. An SRLG is "This identifies a SRLG supported by the TE link. An SRLG is
identified with a 32 bit number that is unique within an IGP identified with a 32 bit number that is unique within an IGP
domain. Zero is a valid SRLG number." domain. Zero is a valid SRLG number."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] -- [GMPLS-OSPF]
::= { teLinkSrlgEntry 1 } ::= { teLinkSrlgEntry 1 }
srlgRowStatus OBJECT-TYPE teSrlgRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. No read-create object can delete a row in this table. No read-create object can
be modified if srlgRowStatus is active(1)." be modified if teSrlgRowStatus is active(1)."
::= { teLinkSrlgEntry 2 } ::= { teLinkSrlgEntry 2 }
srlgStorageType OBJECT-TYPE teSrlgStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
teLinkSrlgTable. Conceptual rows having the value teLinkSrlgTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
::= { teLinkSrlgEntry 3 } ::= { teLinkSrlgEntry 3 }
skipping to change at page 24, line 20 skipping to change at page 24, line 41
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about "An entry in this table contains information about
the priority-based bandwidth of TE links. An ifEntry in the the priority-based bandwidth of TE links. An ifEntry in the
ifTable must exist before a teLinkBandwidthEntry using the ifTable must exist before a teLinkBandwidthEntry using the
same ifIndex is created. ifType of ifEntry must be teLink(200). same ifIndex is created. ifType of ifEntry must be teLink(200).
If a TE link entry in the ifTable is destroyed, then so are If a TE link entry in the ifTable is destroyed, then so are
all entries in the teLinkBandwidthTable that use the ifIndex of all entries in the teLinkBandwidthTable that use the ifIndex of
this TE link." this TE link."
INDEX { ifIndex, teLinkPriority } INDEX { ifIndex, teLinkBandwidthPriority }
::= { teLinkBandwidthTable 1 } ::= { teLinkBandwidthTable 1 }
TeLinkBandwidthEntry ::= SEQUENCE { TeLinkBandwidthEntry ::= SEQUENCE {
teLinkPriority Priority, teLinkBandwidthPriority TeLinkPriority,
teLinkUnreservedBandwidth Unsigned32, teLinkUnreservedBandwidth Unsigned32,
teLinkMaximumLspBandwidth Unsigned32, teLinkMaximumLspBandwidth Unsigned32,
teLinkBandwidthRowStatus RowStatus, teLinkBandwidthRowStatus RowStatus,
teLinkBandwidthStorageType StorageType teLinkBandwidthStorageType StorageType
} }
teLinkPriority OBJECT-TYPE teLinkBandwidthPriority OBJECT-TYPE
SYNTAX Priority SYNTAX TeLinkPriority
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the priority. A value of 0 is valid "This attribute specifies the priority. A value of 0 is valid
as specified in the 'Traffic Engineering Extensions to OSPF as specified in the 'Traffic Engineering Extensions to OSPF
Version 2' document." Version 2' document."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and
Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" Traffic Engineering Extensions to OSPF Version 2, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
skipping to change at page 26, line 30 skipping to change at page 27, line 4
SYNTAX ComponentLinkEntry SYNTAX ComponentLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a component link. An ifEntry must exist in the ifTable a component link. An ifEntry must exist in the ifTable
before a componentLinkEntry is created with the before a componentLinkEntry is created with the
corresponding ifIndex. ifEntry's ifType can be corresponding ifIndex. ifEntry's ifType can be
of any interface type which has been defined for TE Link of any interface type which has been defined for TE Link
interworking. Examples include ATM, Frame Relay, Ethernet, etc. interworking. Examples include ATM, Frame Relay, Ethernet, etc.
If an entry representing a component link is destroyed in the If an entry representing a component link is destroyed in the
ifTable, then so is the corresponding entry in the ifTable, then so is the corresponding entry in the
componentLinkTable. The administrative and operational status componentLinkTable. The administrative and operational status
values are controlled from the ifEntry." values are controlled from the ifEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { componentLinkTable 1 } ::= { componentLinkTable 1 }
ComponentLinkEntry ::= SEQUENCE { ComponentLinkEntry ::= SEQUENCE {
componentLinkMuxCapability SwitchingCapability, componentLinkMuxCapability TeLinkSwitchingCapability,
componentLinkPreferredProtection LinkProtection, componentLinkPreferredProtection TeLinkProtection,
componentLinkCurrentProtection LinkProtection, componentLinkCurrentProtection TeLinkProtection,
componentLinkRowStatus RowStatus, componentLinkRowStatus RowStatus,
componentLinkStorageType StorageType componentLinkStorageType StorageType
} }
componentLinkMuxCapability OBJECT-TYPE componentLinkMuxCapability OBJECT-TYPE
SYNTAX SwitchingCapability SYNTAX TeLinkSwitchingCapability
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link multiplexing capabilities of the "This attribute specifies link multiplexing capabilities of the
component link." component link."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] -- [GMPLS-OSPF]
::= { componentLinkEntry 1 } ::= { componentLinkEntry 1 }
componentLinkPreferredProtection OBJECT-TYPE componentLinkPreferredProtection OBJECT-TYPE
SYNTAX LinkProtection SYNTAX TeLinkProtection
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this component link is "This attribute specifies whether this component link is
a primary or secondary entity." a primary or secondary entity."
::= { componentLinkEntry 2 } ::= { componentLinkEntry 2 }
componentLinkCurrentProtection OBJECT-TYPE componentLinkCurrentProtection OBJECT-TYPE
SYNTAX LinkProtection SYNTAX TeLinkProtection
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this component link is "This attribute specifies whether this component link is
currently used as primary or secondary link." currently used as primary or secondary link."
::= { componentLinkEntry 3 } ::= { componentLinkEntry 3 }
componentLinkRowStatus OBJECT-TYPE componentLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 28, line 35 skipping to change at page 29, line 8
defined for TE Link interworking. Examples include ATM, Frame defined for TE Link interworking. Examples include ATM, Frame
Relay, Ethernet, etc. If a component link entry in the ifTable Relay, Ethernet, etc. If a component link entry in the ifTable
is destroyed, then so are all entries in the is destroyed, then so are all entries in the
componentLinkDescriptorTable that use the ifIndex of this componentLinkDescriptorTable that use the ifIndex of this
component link." component link."
INDEX { ifIndex, componentLinkDescrId } INDEX { ifIndex, componentLinkDescrId }
::= { componentLinkDescriptorTable 1 } ::= { componentLinkDescriptorTable 1 }
ComponentLinkDescriptorEntry ::= SEQUENCE { ComponentLinkDescriptorEntry ::= SEQUENCE {
componentLinkDescrId Unsigned32, componentLinkDescrId Unsigned32,
componentLinkDescrEncodingType LinkEncodingType, componentLinkDescrEncodingType TeLinkEncodingType,
componentLinkDescrPriority Priority, componentLinkDescrPriority TeLinkPriority,
componentLinkDescrMinBandwidth Unsigned32, componentLinkDescrMinBandwidth Unsigned32,
componentLinkDescrMaxBandwidth Unsigned32, componentLinkDescrMaxBandwidth Unsigned32,
componentLinkDescrRowStatus RowStatus, componentLinkDescrRowStatus RowStatus,
componentLinkDescrStorageType StorageType componentLinkDescrStorageType StorageType
} }
componentLinkDescrId OBJECT-TYPE componentLinkDescrId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the link descriptor identifier." "This object specifies the link descriptor identifier."
::= { componentLinkDescriptorEntry 1 } ::= { componentLinkDescriptorEntry 1 }
componentLinkDescrEncodingType OBJECT-TYPE componentLinkDescrEncodingType OBJECT-TYPE
SYNTAX LinkEncodingType SYNTAX TeLinkEncodingType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the component link encoding type." "This attribute specifies the component link encoding type."
REFERENCE REFERENCE
"Generalized MPLS Signaling Functional Description, RFC 3471" "Generalized MPLS Signaling Functional Description, RFC 3471"
::= { componentLinkDescriptorEntry 2 } ::= { componentLinkDescriptorEntry 2 }
componentLinkDescrPriority OBJECT-TYPE componentLinkDescrPriority OBJECT-TYPE
SYNTAX Priority SYNTAX TeLinkPriority
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lowest priority at which that link "This object specifies the lowest priority at which that link
encoding type is available for the component link." encoding type is available for the component link."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] -- [GMPLS-OSPF]
::= { componentLinkDescriptorEntry 3 } ::= { componentLinkDescriptorEntry 3 }
skipping to change at page 31, line 14 skipping to change at page 31, line 35
created. ifEntry's ifType can be of any interface type which created. ifEntry's ifType can be of any interface type which
has been defined for TE Link interworking. Examples include has been defined for TE Link interworking. Examples include
ATM, Frame Relay, Ethernet, etc. If a component link entry in ATM, Frame Relay, Ethernet, etc. If a component link entry in
the ifTable is destroyed, then so are all entries in the the ifTable is destroyed, then so are all entries in the
componentLinkBandwidthTable that use the ifIndex of componentLinkBandwidthTable that use the ifIndex of
this component link." this component link."
INDEX { ifIndex, componentLinkPriority } INDEX { ifIndex, componentLinkPriority }
::= { componentLinkBandwidthTable 1 } ::= { componentLinkBandwidthTable 1 }
ComponentLinkBandwidthEntry ::= SEQUENCE { ComponentLinkBandwidthEntry ::= SEQUENCE {
componentLinkPriority Priority, componentLinkPriority TeLinkPriority,
componentLinkUnreservedBandwidth Unsigned32, componentLinkUnreservedBandwidth Unsigned32,
componentLinkMaximumLspBandwidth Unsigned32, componentLinkMaximumLspBandwidth Unsigned32,
componentLinkBandwidthRowStatus RowStatus, componentLinkBandwidthRowStatus RowStatus,
componentLinkBwStorageType StorageType componentLinkBwStorageType StorageType
} }
componentLinkPriority OBJECT-TYPE componentLinkPriority OBJECT-TYPE
SYNTAX Priority SYNTAX TeLinkPriority
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the priority. A value of 0 is valid "This attribute specifies the priority. A value of 0 is valid
as specified in the 'Traffic Engineering Extensions to OSPF as specified in the 'Traffic Engineering Extensions to OSPF
Version 2' document." Version 2' document."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and
Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" Traffic Engineering Extensions to OSPF Version 2, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
skipping to change at page 32, line 42 skipping to change at page 33, line 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
componentLinkBandwidthTable. Conceptual rows componentLinkBandwidthTable. Conceptual rows
having the value 'permanent' need not allow write-access having the value 'permanent' need not allow write-access
to any columnar object in the row." to any columnar object in the row."
::= { componentLinkBandwidthEntry 5 } ::= { componentLinkBandwidthEntry 5 }
-- End of componentLinkBandwidthTable -- End of componentLinkBandwidthTable
teLinkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, then it enables the
generation of the TE link notifications,
otherwise these notifications are not emitted."
DEFVAL { false }
::= { teLinkObjects 8 }
linkBundleMismatch NOTIFICATION-TYPE
OBJECTS { teLinkAddressType,
teLinkLocalIpAddr, teLinkRemoteIpAddr,
teLinkIncomingIfId, teLinkOutgoingIfId }
STATUS current
DESCRIPTION
"This notification is generated when a mismatch is found on a
bundled link. Such mismatch can be detected for instance if one
of the traffic engineering parameters is not consistent across
all TE links within a bundled link (resource class, etc.)."
::= { teLinkNotifications 1 }
-- Module compliance -- Module compliance
teLinkGroups teLinkGroups
OBJECT IDENTIFIER ::= { teLinkConformance 1 } OBJECT IDENTIFIER ::= { teLinkConformance 1 }
teLinkCompliances teLinkCompliances
OBJECT IDENTIFIER ::= { teLinkConformance 2 } OBJECT IDENTIFIER ::= { teLinkConformance 2 }
teLinkModuleFullCompliance MODULE-COMPLIANCE teLinkModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
configuration and monitoring of TE Link MIB module." configuration and monitoring of TE Link MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented
-- by all devices supporting TE links. However, they may all
-- be supported as read-only objects in the case where automatic
-- configuration is supported.
MANDATORY-GROUPS { teLinkGroup, MANDATORY-GROUPS { teLinkGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
componentLinkBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
GROUP teLinkNotificationGroup
DESCRIPTION
"This group is mandatory for equipment that support
TE link notifications."
-- teLinkTable -- teLinkTable
OBJECT teLinkAddressType OBJECT teLinkAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for numbered links. For unnumbered links, the supported for numbered links. For unnumbered links, the
unknown(0) address type needs to be supported." unknown(0) address type needs to be supported."
OBJECT teLinkLocalIpAddr OBJECT teLinkLocalIpAddr
skipping to change at page 35, line 13 skipping to change at page 34, line 38
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT teLinkDescrStorageType OBJECT teLinkDescrStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- teLinkSrlgTable -- teLinkSrlgTable
OBJECT srlgRowStatus OBJECT teSrlgRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
-- teLinkBandwidthTable -- teLinkBandwidthTable
OBJECT teLinkBandwidthRowStatus OBJECT teLinkBandwidthRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
skipping to change at page 36, line 30 skipping to change at page 36, line 7
-- configuration is unsupported. -- configuration is unsupported.
MANDATORY-GROUPS { teLinkGroup, MANDATORY-GROUPS { teLinkGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
componentLinkBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
GROUP teLinkNotificationGroup
DESCRIPTION
"This group is optional."
-- teLinkTable -- teLinkTable
OBJECT teLinkAddressType OBJECT teLinkAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for numbered links. For unnumbered links, the supported for numbered links. For unnumbered links, the
unknown(0) address type needs to be supported." unknown(0) address type needs to be supported."
skipping to change at page 38, line 28 skipping to change at page 37, line 50
"Write access is not required and active(1) is the "Write access is not required and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT teLinkDescrStorageType OBJECT teLinkDescrStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- teLinkSrlgTable -- teLinkSrlgTable
OBJECT srlgRowStatus OBJECT teSrlgRowStatus
SYNTAX INTEGER { active(1) } SYNTAX INTEGER { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT srlgStorageType OBJECT teSrlgStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- teLinkBandwidthTable -- teLinkBandwidthTable
OBJECT teLinkMaximumLspBandwidth OBJECT teLinkMaximumLspBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 41, line 19 skipping to change at page 40, line 41
teLinkDescrEncodingType, teLinkDescrEncodingType,
teLinkDescrPriority, teLinkDescrPriority,
teLinkDescrMinResBandwidth, teLinkDescrMinResBandwidth,
teLinkDescrMaxResBandwidth, teLinkDescrMaxResBandwidth,
teLinkDescrRowStatus, teLinkDescrRowStatus,
teLinkDescrStorageType, teLinkDescrStorageType,
componentLinkMuxCapability, componentLinkMuxCapability,
componentLinkPreferredProtection, componentLinkPreferredProtection,
componentLinkCurrentProtection, componentLinkCurrentProtection,
componentLinkRowStatus, componentLinkRowStatus,
componentLinkStorageType, componentLinkStorageType
teLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
resources associated with TE links." resources associated with TE links."
::= { teLinkGroups 1 } ::= { teLinkGroups 1 }
teLinkSrlgGroup OBJECT-GROUP teLinkSrlgGroup OBJECT-GROUP
OBJECTS { srlgRowStatus, OBJECTS { teSrlgRowStatus,
srlgStorageType teSrlgStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
SRLG resources associated with TE links." SRLG resources associated with TE links."
::= { teLinkGroups 2 } ::= { teLinkGroups 2 }
teLinkBandwidthGroup OBJECT-GROUP teLinkBandwidthGroup OBJECT-GROUP
OBJECTS { teLinkUnreservedBandwidth, OBJECTS { teLinkUnreservedBandwidth,
skipping to change at page 42, line 25 skipping to change at page 41, line 46
componentLinkBandwidthRowStatus, componentLinkBandwidthRowStatus,
componentLinkBwStorageType componentLinkBwStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
bandwidth parameters associated with component links." bandwidth parameters associated with component links."
::= { teLinkGroups 4 } ::= { teLinkGroups 4 }
teLinkNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { linkBundleMismatch }
STATUS current
DESCRIPTION
"Set of notifications implemented in this module.
None is mandatory."
::= { teLinkGroups 5 }
-- End of TE-LINK-MIB -- End of TE-LINK-MIB
END END
10. Intellectual Property Considerations 10. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per- intellectual property or other rights that might be claimed to per-
tain to the implementation or use of the technology described in this tain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might document or the extent to which any license under such rights might
or might not be available; neither does it represent that it has made or might not be available; neither does it represent that it has made
skipping to change at page 43, line 21 skipping to change at page 42, line 37
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ- environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network ment without proper protection can have a negative effect on network
operations. These are the tables and objects and their sensitiv- operations. These are the tables and objects and their sensitiv-
ity/vulnerability: ity/vulnerability:
- Tables in this MIB module are used for routing purposes. - All the tables in this MIB module have routing information in
them and so they all have the same security attributes.
Unauthorized changes to attributes of these tables can disrupt Unauthorized changes to attributes of these tables can disrupt
resource allocation in the network. resource allocation in the network.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to con- vulnerable in some network environments. It is thus important to con-
trol even GET and/or NOTIFY access to these objects and possibly to trol even GET and/or NOTIFY access to these objects and possibly to
even encrypt the values of these objects when sending them over the even encrypt the values of these objects when sending them over the
network via SNMP. These are the tables and objects and their sensi- network via SNMP. These are the tables and objects and their sensi-
tivity/vulnerability: tivity/vulnerability:
skipping to change at page 45, line 12 skipping to change at page 44, line 30
"Link Bundling in MPLS Traffic Engineering", "Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>, Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002. July 2002.
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", Internet Extensions in Support of Generalized MPLS", Internet
Draft <draft-ietf-ccamp-ospf-gmpls-extensions-09.txt>, Draft <draft-ietf-ccamp-ospf-gmpls-extensions-09.txt>,
December 2002. December 2002.
[IANAifType] "IANAifType MIB Module", [IANAifType] "IANAifType MIB Module",
http://www.iana.org/assignments/ianatype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B., Rekhter, Y., Berger, L., Rajagopalan, B.,
Basak, D., Sandick, H., Zinin, A., Basak, D., Sandick, H., Zinin, A.,
Rajagopalan, B., and Ramamoorthi, S., Rajagopalan, B., and Ramamoorthi, S.,
"Link Management Protocol", "Link Management Protocol",
Internet Draft <draft-ccamp-lmp-08.txt>, Internet Draft <draft-ccamp-lmp-08.txt>,
March 2003. March 2003.
[OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/