draft-ietf-ccamp-gmpls-te-mib-09.txt   draft-ietf-ccamp-gmpls-te-mib-10.txt 
Internet Working Group Thomas D. Nadeau, Ed. Internet Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: December 2005 Adrian Farrel, Ed. Expires: April 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
June 2005 October 2005
Generalized Multiprotocol Label Switching (GMPLS) Traffic Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base Engineering Management Information Base
draft-ietf-ccamp-gmpls-te-mib-09.txt draft-ietf-ccamp-gmpls-te-mib-10.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 10 skipping to change at page 2, line 10
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for Generalized In particular, it describes managed objects for Generalized
Multiprotocol Label Switching (GMPLS) based traffic engineering. Multiprotocol Label Switching (GMPLS) based traffic engineering.
Table of Contents Table of Contents
1. Introduction ........................................... 2 1. Introduction ........................................... 2
1.1. Migration Strategy ................................... 3 1.1. Migration Strategy ................................... 3
2. Terminology ............................................ 3 2. Terminology ............................................ 3
3. The SNMP Management Framework .......................... 3 3. The SNMP Management Framework .......................... 4
4. Outline ................................................ 4 4. Outline ................................................ 4
4.1. Summary of GMPLS Traffic Engineering MIB Module ...... 4 4.1. Summary of GMPLS Traffic Engineering MIB Module ...... 4
5. Brief Description of GMPLS TE MIB Objects .............. 5 5. Brief Description of GMPLS TE MIB Objects .............. 5
5.1. gmplsTunnelTable ..................................... 5 5.1. gmplsTunnelTable ..................................... 5
5.2. gmplsTunnelHopTable .................................. 5 5.2. gmplsTunnelHopTable .................................. 6
5.3. gmplsTunnelARHopTable ................................ 5 5.3. gmplsTunnelARHopTable ................................ 6
5.4. gmplsTunnelCHopTable ................................. 5 5.4. gmplsTunnelCHopTable ................................. 6
5.5. gmplsTunnelErrorTable ................................ 6 5.5. gmplsTunnelErrorTable ................................ 6
5.6. gmplsTunnelReversePerfTable .......................... 6 5.6. gmplsTunnelReversePerfTable .......................... 6
6. Cross-referencing to the mplsLabelTable ................ 6 5.7. Use of 32-bit and 64-bit Counters ................... 6
6. Cross-referencing to the gmplsLabelTable ............... 7
7. Example of GMPLS Tunnel Setup .......................... 7 7. Example of GMPLS Tunnel Setup .......................... 7
8. GMPLS Traffic Engineering MIB Module .... ............. 10 8. GMPLS Traffic Engineering MIB Module .................. 11
9. Security Considerations ............................... 43 9. Security Considerations ............................... 48
10. Acknowledgments ...................................... 44 10. Acknowledgments ...................................... 49
11. IANA Considerations .................................. 44 11. IANA Considerations .................................. 49
11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 44 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 50
11.2. Dependence on IANA MIB Modules ..................... 44 11.2. Dependence on IANA MIB Modules ..................... 50
11.2.1. IANA-GMPLS-MIB Definition ........................ 45 11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 50
12. References ........................................... 51 12. References ........................................... 58
12.1. Normative Refenerces ............................... 51 12.1. Normative References ............................... 59
12.2. Informational References ........................... 52 12.2. Informative References ............................. 59
13. Authors' Addresses ................................... 53 13. Contact Information .................................. 60
14. Intellectual Property Notice ......................... 54 14. Intellectual Property Considerations ................. 60
15. Full Copyright Statement ............................. 54 15. Full Copyright Statement ............................. 61
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling In particular, it describes managed objects for modeling
Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based
traffic engineering. The tables and objects defined in this document traffic engineering. The tables and objects defined in this document
extend those defined in the equivalent document for MPLS traffic extend those defined in the equivalent document for MPLS traffic
engineering [RFC3812], and management of GMPLS traffic engineering is engineering [RFC3812], and management of GMPLS traffic engineering is
built on management of MPLS traffic engineering. built on management of MPLS traffic engineering.
This MIB module should be used in conjunction with the companion The MIB modules in this document should be used in conjunction with
document [GMPLSLSRMIB] for GMPLS based traffic engineering the companion document [GMPLSLSRMIB] for GMPLS based traffic
configuration and management. engineering configuration and management.
Comments should be made direct to the CCAMP mailing list at Comments should be made direct to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119, document are to be interpreted as described in BCP 14, RFC 2119,
reference [RFC2119]. reference [RFC2119].
1.1. Migration Strategy 1.1. Migration Strategy
This MIB module extends the traffic engineering MIB module defined MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB
for use with MPLS [RFC3812]. It provides additions for support of module [RFC3812].
GMPLS tunnels.
LSRs may be migrated to model and manage their TE LSPs using the MIB
modules in this document in order to migrate the LSRs to GMPLS
support, or to take advandtage of additional MIB objects defined in
these MIB modules that are applicable to MPLS-TE.
The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document
extends the MPLS-TE-STD-MIB module [RFC3812] through a series of
augmentations and sparse augmentations of the MIB tables. The only
additions are for support of GMPLS or to support the increased
complexity of MPLS and GMPLS systems.
In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB
support an implementation needs only to add support for the
additional tables and objects defined in GMPLS-TE-STD-MIB. The
gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an
MPLS-TE LSP tunnel to benefit from the additional objects and tables
of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols.
The companion document for modeling and managing GMPLS based LSRs The companion document for modeling and managing GMPLS based LSRs
[GMPLSLSRMIB] extends MPLS LSR MIB [RFC3813] with the same [GMPLSLSRMIB] extends the MPLS-LSR-STD-MIB module [RFC3813] with the
intentions. same intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in [RFC3811] Textual conventions are defined in [RFC3811] and [GMPLSTCMIB].
and [GMPLSTCMIB].
2. Terminology 2. Terminology
This document uses terminology from the MPLS architecture document This document uses terminology from the MPLS architecture document
[RFC3031], from the GMPLS architecture document [RFC3945], and from [RFC3031], from the GMPLS architecture document [RFC3945], and from
the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used
terms are described next. terms are described next.
An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It
consists of in-segment(s) and/or out-segment(s) at the egress/ingress consists of in-segment(s) and/or out-segment(s) at the egress/ingress
LSRs, each segment being associated with one GMPLS enabled interface. LSRs, each segment being associated with one GMPLS enabled interface.
These are also referred to as tunnel segments. These are also referred to as tunnel segments.
Additionally, at an intermediate LSR, we model a connection as Additionally, at an intermediate LSR, we model a connection as
consisting of one or more in-segments and/or one or more consisting of one or more in-segments and/or one or more
out-segments. The binding or interconnection between in-segments and out-segments. The binding or interconnection between in-segments and
out-segments in performed using a cross-connect. out-segments in performed using a cross-connect.
These segment and cross-connect objects are defined in the MPLS Label These segment and cross-connect objects are defined in the MPLS Label
Switch Router MIB [RFC3813], but see also the GMPLS Label Switch Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the
Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these GMPLS Label Switch Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] for
objects. the GMPLS-specific extensions to these objects.
3. The SNMP Management Framework 3. The SNMP 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 29 skipping to change at page 4, line 47
using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel
segments, if this is done manually. Also, the in-segment and segments, if this is done manually. Also, the in-segment and
out-segment performance tables, mplsInSegmentPerfTable and out-segment performance tables, mplsInSegmentPerfTable and
mplsOutSegmentPerfTable [RFC3813], should be used to determine mplsOutSegmentPerfTable [RFC3813], should be used to determine
performance of the tunnels and tunnel segments although it should be performance of the tunnels and tunnel segments although it should be
noted that those tables may not be appropriate for measuring noted that those tables may not be appropriate for measuring
performance on some types of GMPLS links. performance on some types of GMPLS links.
4.1. Summary of GMPLS Traffic Engineering MIB Module 4.1. Summary of GMPLS Traffic Engineering MIB Module
The MIB objects for performing the actions listed above that cannot The following tables contain MIB objects for performing the actions
be performed solely using the MIB objects defined in [RFC3812] listed above when they cannot be performed solely using MIB objects
consist of the following tables. defined in MPLS-TE-STD-MIB [RFC3812].
- Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific
tunnel configuration parameters. tunnel configuration parameters.
- Tunnel specified, actual, and computed hop tables - Tunnel specified, actual, and computed hop tables
(gmplsTunnelHopTable, gmplsTunnelARHopTable, and (gmplsTunnelHopTable, gmplsTunnelARHopTable, and
gmplsTunnelCHopTable) for providing additional configuration of gmplsTunnelCHopTable) for providing additional configuration of
strict and loose source routed tunnel hops. strict and loose source routed tunnel hops.
- Performance and error reporting tables (gmplsTunnelReversePerfTable - Performance and error reporting tables (gmplsTunnelReversePerfTable
and gmplsTunnelErrorTable). and gmplsTunnelErrorTable).
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
Additionally, this MIB module contains a new Notification. Additionally, the GMPLS-TE-STD-MIB module contains a new
notification.
- The GMPLS Tunnel Down Notification (gmplsTunnelDown) is intended to - The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used
be used in place of the mplsTunnelDown Notification defined in for all GMPLS tunnels in place of the mplsTunnelDown notification
[RFC3812]. As well as indicating that a tunnel has transitioned to defined in [RFC3812]. An implementation must not issue both the
operational down state, this new Notificaiton indicates the cause gmplsTunnelDown and the mplsTunnelDown notifications for the same
event. As well as indicating that a tunnel has transitioned to
operational down state, this new notification indicates the cause
of the failure. of the failure.
5. Brief Description of GMPLS TE MIB Objects 5. Brief Description of GMPLS TE MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables
support both manually configured and signaled tunnels. support both manually configured and signaled tunnels.
5.1. gmplsTunnelTable 5.1. gmplsTunnelTable
The gmplsTunnelTable extends the MPLS traffic engineering MIB module The gmplsTunnelTable extends the MPLS traffic engineering MIB module
to allow GMPLS tunnels to be created between an LSR and a remote (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created
endpoint, and existing GMPLS tunnels to be reconfigured or removed. between an LSR and a remote endpoint, and existing GMPLS tunnels to
be reconfigured or removed.
Note that we only support point-to-point tunnel segments, although Note that we only support point-to-point tunnel segments, although
multi-point-to-point and point-to-multi-point connections are multi-point-to-point and point-to-multi-point connections are
supported by an LSR acting as a cross-connect. supported by an LSR acting as a cross-connect.
Each tunnel can thus have one out-segment originating at an LSR Each tunnel can thus have one out-segment originating at an LSR
and/or one in-segment terminating at that LSR. and/or one in-segment terminating at that LSR.
Three objects within this table utilize enumerations in order to map Three objects within this table utilize enumerations in order to map
to enumerations that are used in GMPLS signaling. In order to protect to enumerations that are used in GMPLS signaling. In order to protect
this MIB module from changes (in particular, extensions) to the range the GMPLS-TE-STD-MIB module from changes (in particular, extensions)
of enumerations supported by the signaling protocols, these MIB to the range of enumerations supported by the signaling protocols,
objects use Textual Conventions defined by IANA. For further details, these MIB objects use Textual Conventions with values maintained by
see the IANA Considerations section of this document. IANA. For further details, see the IANA Considerations section of
this document.
5.2. gmplsTunnelHopTable 5.2. gmplsTunnelHopTable
The gmplsTunnelHopTable is used to indicate additional parameters for The gmplsTunnelHopTable is used to indicate additional parameters for
the hops, strict or loose, of a GMPLS tunnel defined in the hops, strict or loose, of a GMPLS tunnel defined in
gmplsTunnelTable, when it is established using signaling. Multiple gmplsTunnelTable, when it is established using signaling. Multiple
tunnels may share hops by pointing to the same entry in this table. tunnels may share hops by pointing to the same entry in this table.
5.3. gmplsTunnelARHopTable 5.3. gmplsTunnelARHopTable
The gmplsTunnelARHopTable is used to indicate the actual hops The gmplsTunnelARHopTable is used to indicate the actual hops
traversed by a tunnel as reported by the signaling protocol after the traversed by a tunnel as reported by the signaling protocol after the
tunnel is setup. The support of this table is optional since not all tunnel is setup. The support of this table is optional since not all
GMPLS signaling protocols support this feature. GMPLS signaling protocols support this feature.
5.4. gmplsTunnelCHoptable 5.4. gmplsTunnelCHopTable
The gmplsTunnelCHopTable lists the actual hops computed by a The gmplsTunnelCHopTable lists the actual hops computed by a
constraint-based routing algorithm based on the gmplsTunnelHopTable. constraint-based routing algorithm based on the gmplsTunnelHopTable.
The support of this table is optional since not all implementations The support of this table is optional since not all implementations
support computation of hop lists using a constraint-based routing support computation of hop lists using a constraint-based routing
protocol. protocol.
5.5. gmplsTunnelErrorTable 5.5. gmplsTunnelErrorTable
The gmplsTunnelErrorTable provides access to information about the The gmplsTunnelErrorTable provides access to information about the
last error that occurred on each tunnel known about by the MIB. It last error that occurred on each tunnel known about by the MIB. It
indicates the nature of the error, when and how it was reported and indicates the nature of the error, when and how it was reported and
can give recovery advice through a display string. can give recovery advice through an admin string.
5.6. gmplsTunnelReversePerfTable 5.6. gmplsTunnelReversePerfTable
gmplsTunnelReversePerfTable provides additional counters to measure gmplsTunnelReversePerfTable provides additional counters to measure
the performance of bidirectional GMPLS tunnels in which packets are the performance of bidirectional GMPLS tunnels in which packets are
visible. It supplements the counters in mplsTunnelPerfTable and visible. It supplements the counters in mplsTunnelPerfTable and
augments gmplsTunnelTable. augments gmplsTunnelTable.
Note that not all counters may be appropriate or available for some Note that not all counters may be appropriate or available for some
types of tunnel. types of tunnel.
5.7. Use of 32-bit and 64-bit Counters
64-bit counters are provided in the GMPLS-TE-STD-MIB module for
high-speed interfaces where the use of 32-bit counters might be
impractical. The requirements on the use of 32-bit and 64-bit
counters (copied verbatim from [RFC2863]) are as follows:
For interfaces that operate at 20,000,000 (20 million) bits per
second or less, 32-bit byte and packet counters MUST be supported.
For interfaces that operate faster than 20,000,000 bits/second, and
slower than 650,000,000 bits/second, 32-bit packet counters MUST be
supported and 64-bit octet counters MUST be supported. For
interfaces that operate at 650,000,000 bits/second or faster, 64-bit
packet counters AND 64-bit octet counters MUST be supported.
6. Cross-referencing to the gmplsLabelTable 6. Cross-referencing to the gmplsLabelTable
The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in
provides a way to model labels in a GMPLS system where labels might [GMPLSLSRMIB] and provides a way to model labels in a GMPLS system
not be simple 32 bit integers. where labels might not be simple 32 bit integers.
The hop tables in this document (gmplsHopTable, gmplsCHopTable and The hop tables in this document (gmplsHopTable, gmplsCHopTable and
gmplsARHopTable) and the segment tables in the [RFC3813] gmplsARHopTable) and the segment tables in the [RFC3813]
(mplsInSegmentTable and mplsOutSegmentTable) contain objects with (mplsInSegmentTable and mplsOutSegmentTable) contain objects with
syntax MplsLabel. syntax MplsLabel.
MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable
of representing any MPLS label and most GMPLS labels. However, some of representing any MPLS label and most GMPLS labels. However, some
GMPLS labels are larger than 32 bits and may be of arbitrary length. GMPLS labels are larger than 32 bits and may be of arbitrary length.
Further, some labels that may be safely encoded in 32 bits are Further, some labels that may be safely encoded in 32 bits are
constructed from multiple sub-fields. Additionally, some GMPLS constructed from multiple sub-fields. Additionally, some GMPLS
technologies support the concatenation of individual labels to technologies support the concatenation of individual labels to
represent a data flow carried as multiple sub-flows. represent a data flow carried as multiple sub-flows.
These GMPLS cases require that something other than a simple 32-bit These GMPLS cases require that something other than a simple 32-bit
integer is made available to represent the labels. This is achieved integer is made available to represent the labels. This is achieved
through the gmplsLabelTable contained in [GMPLSLSRMIB]. through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB
[GMPLSLSRMIB].
The tables in this document and [RFC3813] that include objects with The tables in this document and [RFC3813] that include objects with
syntax MplsLabel also include companion objects that are row syntax MplsLabel also include companion objects that are row
pointers. If the row pointer is set to zeroDotZero (0.0) then object pointers. If the row pointer is set to zeroDotZero (0.0) then object
of syntax MplsLabel contains the label encoded as a 32-bit integer. of syntax MplsLabel contains the label encoded as a 32-bit integer.
But otherwise the row pointer indicates a row in another MIB table But otherwise the row pointer indicates a row in another MIB table
that includes the label. In these cases, the row pointer may indicate that includes the label. In these cases, the row pointer may indicate
a row in the gmplsLabelTable. a row in the gmplsLabelTable.
This provides both a good way to support legacy systems that This provides both a good way to support legacy systems that
implement the previous version of this MIB module [RFC3812], and a implement the MPLS-TE-STD-MIB [RFC3812], and a significant
significant simplification in GMPLS systems that are limited to a simplification in GMPLS systems that are limited to a single, simple
single, simple label type. label type.
Note that gmplsLabelTable supports concatenated labels through the Note that gmplsLabelTable supports concatenated labels through the
use of a label sub-index (gmplsLabelSubindex). use of a label sub-index (gmplsLabelSubindex).
7. Example of GMPLS Tunnel Setup 7. Example of GMPLS Tunnel Setup
This section contains an example of which MIB objects should be This section contains an example of which MIB objects should be
modified to create a GMPLS tunnel. This example shows a best effort, modified to create a GMPLS tunnel. This example shows a best effort,
loosely routed, bidirectional traffic engineered tunnel, which spans loosely routed, bidirectional traffic engineered tunnel, which spans
two hops of a simple network, uses Generalized Label requests with two hops of a simple network, uses Generalized Label requests with
skipping to change at page 7, line 20 skipping to change at page 8, line 11
This section contains an example of which MIB objects should be This section contains an example of which MIB objects should be
modified to create a GMPLS tunnel. This example shows a best effort, modified to create a GMPLS tunnel. This example shows a best effort,
loosely routed, bidirectional traffic engineered tunnel, which spans loosely routed, bidirectional traffic engineered tunnel, which spans
two hops of a simple network, uses Generalized Label requests with two hops of a simple network, uses Generalized Label requests with
Lambda encoding, has label recording and shared link layer Lambda encoding, has label recording and shared link layer
protection. Note that these objects should be created on the protection. Note that these objects should be created on the
"head-end" LSR. "head-end" LSR.
First in the mplsTunnelTable: First in the mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 123.123.125.1, mplsTunnelIngressLSRId = 192.168.100.1,
mplsTunnelEgressLSRId = 123.123.126.1, mplsTunnelEgressLSRId = 192.168.200.1,
mplsTunnelName = "My first tunnel", mplsTunnelName = "My first tunnel",
mplsTunnelDescr = "Here to there and back again", mplsTunnelDescr = "Here to there and back again",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0, mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = recordRoute (4), mplsTunnelSessionAttributes = recordRoute (4),
mplsTunnelOwner = snmp (2), mplsTunnelOwner = snmp (2),
mplsTunnelLocalProtectInUse = false (2), mplsTunnelLocalProtectInUse = false (2),
skipping to change at page 7, line 38 skipping to change at page 8, line 30
mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0, mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = recordRoute (4), mplsTunnelSessionAttributes = recordRoute (4),
mplsTunnelOwner = snmp (2), mplsTunnelOwner = snmp (2),
mplsTunnelLocalProtectInUse = false (2), mplsTunnelLocalProtectInUse = false (2),
mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, mplsTunnelResourcePointer = mplsTunnelResourceIndex.6,
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelPrimaryInstance = 0, mplsTunnelPrimaryInstance = 0,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1, mplsTunnelPathInUse = 1,
mplsTunnelRole = head(1), mplsTunnelRole = head(1),
mplsTunnelRowStatus = createAndWait (5), mplsTunnelRowStatus = createAndWait (5),
} }
In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1): In gmplsTunnelTable(1,1,192.168.100.1,192.168.200.1):
{ {
gmplsTunnelUnnumIf = true (1), gmplsTunnelUnnumIf = true (1),
gmplsTunnelAttributes = labelRecordingRequired (1), gmplsTunnelAttributes = labelRecordingRequired (1),
gmplsTunnelLSPEncoding = tunnelLspLambda, gmplsTunnelLSPEncoding = tunnelLspLambda,
gmplsTunnelSwitchingType = lsc, gmplsTunnelSwitchingType = lsc,
gmplsTunnelLinkProtection = shared (2), gmplsTunnelLinkProtection = shared (2),
gmplsTunnelGPid = lambda, gmplsTunnelGPid = lambda,
gmplsTunnelSecondary = false (2), gmplsTunnelSecondary = false (2),
gmplsTunnelDirection = bidirectional (1) gmplsTunnelDirection = bidirectional (1)
gmplsTunnelPathComp = explicit(2), gmplsTunnelPathComp = explicit(2),
gmplsTunnelUpNotRecip = 0x7B7B7D01, gmplsTunnelRequestedUpstreamNotifyRecipientType = ipv4(1),
gmplsTunnelDownNotRecip = 0x00000000, gmplsTunnelRequestedUpstreamNotifyRecipient = 'C0A86401'H,
gmplsTunnelAdminStatusFlags = 0, gmplsTunnelAdminStatusFlags = 0,
gmplsTunnelExtraParamsPtr = 0.0 gmplsTunnelExtraParamsPtr = 0.0
} }
Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and
gmplsTunnelHopTable are created and activated at this time. gmplsTunnelHopTable are created and activated at this time.
In mplsTunnelResourceTable: In mplsTunnelResourceTable:
{ {
mplsTunnelResourceIndex = 6, mplsTunnelResourceIndex = 6,
mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0, mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceRowStatus = createAndGo (4) mplsTunnelResourceRowStatus = createAndGo (4)
} }
The next two instances of mplsTunnelHopEntry are used to denote the The next two instances of mplsTunnelHopEntry are used to denote the
hops this tunnel will take across the network. hops this tunnel will take across the network.
The following denotes the beginning of the network, or the first hop. The following denotes the beginning of the network, or the first hop.
We have used the fictitious LSR identified by "123.123.125.1" as our We have used the fictitious LSR identified by "192.168.100.1" as our
example head-end router. example head-end router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1, mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipV4 (1), mplsTunnelHopAddrType = ipV4 (1),
mplsTunnelHopIpv4Addr = 123.123.125.1, mplsTunnelHopIpv4Addr = 192.168.100.1,
mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = strict (1), mplsTunnelHopType = strict (1),
mplsTunnelHopRowStatus = createAndWait (5), mplsTunnelHopRowStatus = createAndWait (5),
} }
The following denotes the end of the network, or the last hop in our The following denotes the end of the network, or the last hop in our
example. We have used the fictitious LSR identified by example. We have used the fictitious LSR identified by
"123.123.126.1" as our end router. "192.168.200.1" as our end router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2, mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipV4 (1), mplsTunnelHopAddrType = ipV4 (1),
mplsTunnelHopIpv4Addr = 123.123.126.1, mplsTunnelHopIpv4Addr = 192.168.100.1,
mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = loose (2), mplsTunnelHopType = loose (2),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
Now an associated entry in the gmplsTunnelHopTable is created to Now an associated entry in the gmplsTunnelHopTable is created to
provide additional GMPLS hop configuration indicating that the first provide additional GMPLS hop configuration indicating that the first
hop is an unnumbered link using explicit forward and reverse labels. hop is an unnumbered link using explicit forward and reverse labels.
An entry in the gmplsLabelTable is created first to include the An entry in the gmplsLabelTable is created first to include the
explicit label. explicit label.
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 2, gmplsLabelInterface = 2,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
skipping to change at page 9, line 21 skipping to change at page 10, line 15
provide additional GMPLS hop configuration indicating that the first provide additional GMPLS hop configuration indicating that the first
hop is an unnumbered link using explicit forward and reverse labels. hop is an unnumbered link using explicit forward and reverse labels.
An entry in the gmplsLabelTable is created first to include the An entry in the gmplsLabelTable is created first to include the
explicit label. explicit label.
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 2, gmplsLabelInterface = 2,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformGeneralizedLabel(3), gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210 gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
In gmplsTunnelHopTable(1,1,1): In gmplsTunnelHopTable(1,1,1):
{ {
gmplsTunnelHopLabelStatuses = forwardPresent(0) gmplsTunnelHopLabelStatuses = forwardPresent(0)
+reversePresent(1), +reversePresent(1),
gmplsTunnelHopExpLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0)
gmplsTunnelHopExpRvrsLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0)
} }
The first hop is now activated: The first hop is now activated:
In mplsTunnelHopTable(1,1,1): In mplsTunnelHopTable(1,1,1):
{ {
mplsTunnelHopRowStatus = active (1) mplsTunnelHopRowStatus = active (1)
} }
No gmplsTunnelHopEntry is created for the second hop as it contains No gmplsTunnelHopEntry is created for the second hop as it contains
no special GMPLS features. no special GMPLS features.
Finally the mplsTunnelEntry is activated: Finally the mplsTunnelEntry is activated:
In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1) In mplsTunnelTable(1,1,192.168.100.1,192.168.200.1)
{ {
mplsTunnelRowStatus = active(1) mplsTunnelRowStatus = active(1)
} }
8. GMPLS Traffic Engineering MIB Module 8. GMPLS Traffic Engineering MIB Module
This MIB module makes references to the following documents.
[RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411],
[RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202]
and [GMPLS-G709].
GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32
Counter64, IpAddress, zeroDotZero
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
TruthValue, TimeStamp, DisplayString, RowPointer TruthValue, TimeStamp, RowPointer
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- RFC4001 FROM INET-ADDRESS-MIB -- RFC4001
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId, mplsTunnelHopListIndex, mplsTunnelEgressLSRId, mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex,
mplsTunnelARHopListIndex, mplsTunnelARHopIndex, mplsTunnelARHopListIndex, mplsTunnelARHopIndex,
mplsTunnelCHopListIndex, mplsTunnelCHopIndex, mplsTunnelCHopListIndex, mplsTunnelCHopIndex,
mplsTunnelEntry, mplsTunnelEntry,
mplsTunnelAdminStatus, mplsTunnelOperStatus mplsTunnelAdminStatus, mplsTunnelOperStatus
FROM MPLS-TE-STD-MIB -- RFC3812 FROM MPLS-TE-STD-MIB -- RFC3812
IANAGmplsLSPEncoding, IANAGmplsSwitchingType,
IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation
FROM IANA-GMPLS-TC-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
IANAGmplsLSPEncoding, IANAGmplsSwitchingType, IANAGmplsGPid,
IANAGmplsAdminStatusFlags
FROM IANA-GMPLS-MIB
; ;
gmplsTeStdMIB MODULE-IDENTITY gmplsTeStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) Working
Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2005). The "Copyright (C) The Internet Society (2005). This version of
initial version of this MIB module was published this MIB module is part of RFC xxxx; see the RFC itself for
in RFC xxxx. For full legal notices see the RFC full legal notices.
itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Ed. Please replace xxxx above with the correct RFC number and
-- remove this note.
This MIB module contains managed object definitions This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in: for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS) 1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor), Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003. RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003." L. (Editor), RFC 3473, January 2003."
-- Revision history.
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC Editor: Please see the IANA Considerations Section. "Initial version issued as part of RFC xxxx."
-- RFC-editor please fill in XXXX
"Initial version issued as part of RFC XXXX."
::= { mplsStdMIB XXX } ::= { mplsStdMIB XXX }
-- RFC Editor. Please replace xxxx above with the correct RFC number and
-- remove this note.
-- Top level components of this MIB. -- RFC Editor. Please replace XXX above with the OID assigned by IANA
-- and remove this note
-- Notifications
- <span class="insert">and remove this note</span>
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
-- tables, scalars
gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 }
gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 }
-- conformance
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
-- GMPLS Tunnel scalars.
gmplsTunnelsConfigured OBJECT-TYPE gmplsTunnelsConfigured OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of GMPLS tunnels configured on this device. A GMPLS "The number of GMPLS tunnels configured on this device. A GMPLS
tunnel is considered configured if an entry for the tunnel tunnel is considered configured if an entry for the tunnel
exists in the gmplsTunnelTable and the associated exists in the gmplsTunnelTable and the associated
mplsTunnelRowStatus is active(1)." mplsTunnelRowStatus is active(1)."
::= { gmplsTeScalars 1 } ::= { gmplsTeScalars 1 }
gmplsTunnelsActive OBJECT-TYPE gmplsTunnelsActive OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of GMPLS tunnels active on this device. A GMPLS "The number of GMPLS tunnels active on this device. A GMPLS
tunnel is considered active if there is an entry in the tunnel is considered active if there is an entry in the
gmplsTunnelTable and the associated mplsTunnelOperStatus for the gmplsTunnelTable and the associated mplsTunnelOperStatus for the
tunnel is up(1)." tunnel is up(1)."
::= { gmplsTeScalars 2 } ::= { gmplsTeScalars 2 }
-- End of GMPLS Tunnel scalars.
-- GMPLS tunnel table.
gmplsTunnelTable OBJECT-TYPE gmplsTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelEntry SYNTAX SEQUENCE OF GmplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelTable 'extends' the mplsTunnelTable. It allows "The gmplsTunnelTable sparse augments the mplsTunnelTable of
GMPLS tunnels to be created between an LSR and a remote MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between
endpoint, and existing tunnels to be reconfigured or removed. an LSR and a remote endpoint, and existing tunnels to be
reconfigured or removed.
Note that only point-to-point tunnel segments are supported, Note that only point-to-point tunnel segments are supported,
although multi-point-to-point and point-to-multi-point although multi-point-to-point and point-to-multi-point
connections are supported by an LSR acting as a cross-connect. connections are supported by an LSR acting as a cross-connect.
Each tunnel can thus have one out-segment originating at this Each tunnel can thus have one out-segment originating at this
LSR and/or one in-segment terminating at this LSR. LSR and/or one in-segment terminating at this LSR.
The row status of an entry in this table is controlled by The row status of an entry in this table is controlled by
mplsTunnelRowStatus in the corresponding entry in mplsTunnelRowStatus in the corresponding entry in
mplsTunnelTable. That is, it is not permitted to create a row in mplsTunnelTable. When the corresponding mplsTunnelRowStatus has
this table, nor to modify an existing row, when the value active(1) a row in this table may not be created or
corresponding mplsTunnelRowStatus has value active(1). modified.
The exception to this rule is the gmplsTunnelAdminStatusFlags The exception to this rule is the
object, which can be modified whilst the tunnel is active." gmplsTunnelAdminStatusInformation object, which can be modified
whilst the tunnel is active."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 1 } ::= { gmplsTeObjects 1 }
gmplsTunnelEntry OBJECT-TYPE gmplsTunnelEntry OBJECT-TYPE
SYNTAX GmplsTunnelEntry SYNTAX GmplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table in association with the corresponding "An entry in this table in association with the corresponding
entry in the mplsTunnelTable represents a GMPLS tunnel. entry in the mplsTunnelTable represents a GMPLS tunnel.
An entry can be created by a network administrator or by an SNMP An entry can be created by a network administrator via SNMP SET
agent as instructed by a signaling protocol." commands, or in response to signaling protocol events."
INDEX { INDEX {
mplsTunnelIndex, mplsTunnelIndex,
mplsTunnelInstance, mplsTunnelInstance,
mplsTunnelIngressLSRId, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
} }
::= { gmplsTunnelTable 1 } ::= { gmplsTunnelTable 1 }
GmplsTunnelEntry ::= SEQUENCE { GmplsTunnelEntry ::= SEQUENCE {
gmplsTunnelUnnumIf TruthValue, gmplsTunnelUnnumIf TruthValue,
gmplsTunnelAttributes BITS, gmplsTunnelAttributes BITS,
gmplsTunnelLSPEncoding IANAGmplsLSPEncoding, gmplsTunnelLSPEncoding IANAGmplsLSPEncodingType,
gmplsTunnelSwitchingType IANAGmplsSwitchingType, gmplsTunnelSwitchingType IANAGmplsSwitchingType,
gmplsTunnelLinkProtection BITS, gmplsTunnelLinkProtection BITS,
gmplsTunnelGPid IANAGmplsGPid, gmplsTunnelGPid IANAGmplsGeneralizedPid,
gmplsTunnelSecondary TruthValue, gmplsTunnelSecondary TruthValue,
gmplsTunnelDirection INTEGER, gmplsTunnelDirection INTEGER,
gmplsTunnelPathComp INTEGER, gmplsTunnelPathComp INTEGER,
gmplsTunnelUpNotRecip IpAddress, gmplsTunnelUpstreamNotifyRecipientType InetAddressType,
gmplsTunnelDownNotRecip IpAddress, gmplsTunnelUpstreamNotifyRecipient InetAddress,
gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusFlags, gmplsTunnelSendResvNotifyRecipientType InetAddressType,
gmplsTunnelSendResvNotifyRecipient InetAddress,
gmplsTunnelDownstreamNotifyRecipientType InetAddressType,
gmplsTunnelDownstreamNotifyRecipient InetAddress,
gmplsTunnelSendPathNotifyRecipientType InetAddressType,
gmplsTunnelSendPathNotifyRecipient InetAddress,
gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformation,
gmplsTunnelExtraParamsPtr RowPointer gmplsTunnelExtraParamsPtr RowPointer
} }
gmplsTunnelUnnumIf OBJECT-TYPE gmplsTunnelUnnumIf OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel corresponds to an unnumbered "Denotes whether or not this tunnel corresponds to an unnumbered
interface represented in the interfaces group table. interface represented by an entry in the interfaces group table
(the ifTable) with ifType set to mpls (166).
This object is only used if mplsTunnelIsIf is set to 'true'. This object is only used if mplsTunnelIsIf is set to 'true'.
If both this object and the mplsTunnelIsIf object are set to If both this object and the mplsTunnelIsIf object are set to
'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID
object to the outgoing Path message. object to the outgoing Path message.
This object contains information that is only used by the This object contains information that is only used by the
terminating LSR." terminating LSR."
REFERENCE REFERENCE
"Signalling Unnumbered Links in RSVP-TE, Kompella, K. "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477."
and Rekhter, Y., RFC 3477, January 2003."
DEFVAL { false } DEFVAL { false }
::= { gmplsTunnelEntry 1 } ::= { gmplsTunnelEntry 1 }
gmplsTunnelAttributes OBJECT-TYPE gmplsTunnelAttributes OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
labelRecordingDesired (0) labelRecordingDesired (0)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates optional parameters for this tunnel. "This bitmask indicates optional parameters for this tunnel.
These bits should be taken in addition to those defined in These bits should be taken in addition to those defined in
mplsTunnelSessionAttributes in order to determine the full set mplsTunnelSessionAttributes in order to determine the full set
of options to be signaled (for example SESSION_ATTRIBUTES flags of options to be signaled (for example SESSION_ATTRIBUTES flags
in RSVP-TE). The following describes these bitfields: in RSVP-TE). The following describes these bitfields:
labelRecordingDesired labelRecordingDesired
This flag indicates that label information should be included This flag is set to indicate that label information should be
when doing a route record. This bit is not valid unless the included when doing a route record. This bit is not valid
recordRoute bit is set." unless the recordRoute bit is set."
REFERENCE REFERENCE
"RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
RFC 3209, December 2001." sections 4.4.3, 4.7.1 and 4.7.2."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelEntry 2 } ::= { gmplsTunnelEntry 2 }
gmplsTunnelLSPEncoding OBJECT-TYPE gmplsTunnelLSPEncoding OBJECT-TYPE
SYNTAX IANAGmplsLSPEncoding SYNTAX IANAGmplsLSPEncodingType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the encoding of the LSP being requested. "This object indicates the encoding of the LSP being requested.
A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is
not in use. Some objects in this MIB module may be of use for not in use. Some objects in this MIB module may be of use for
MPLS signaling extensions that do not use GMPLS signaling. By MPLS signaling extensions that do not use GMPLS signaling. By
setting this object to 'tunnelLspNotGmpls', an application may setting this object to 'tunnelLspNotGmpls', an application may
indicate that only those objects meaningful in MPLS should be indicate that only those objects meaningful in MPLS should be
examined. examined.
The values to use are defined in the textual convention The values to use are defined in the textual convention
IANAGmplsLSPEncoding found in the IANA-GMPLS-MIB MIB module." IANAGmplsLSPEncodingType found in the IANA-GMPLS-TC-MIB module."
DEFVAL { tunnelLspNotGmpls } DEFVAL { tunnelLspNotGmpls }
::= { gmplsTunnelEntry 3 } ::= { gmplsTunnelEntry 3 }
gmplsTunnelSwitchingType OBJECT-TYPE gmplsTunnelSwitchingType OBJECT-TYPE
SYNTAX IANAGmplsSwitchingType SYNTAX IANAGmplsSwitchingType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of switching that should be performed on "Indicates the type of switching that should be performed on
a particular link. This field is needed for links that a particular link. This field is needed for links that
advertise more than one type of switching capability. advertise more than one type of switching capability.
The values to use are defined in the textual convention The values to use are defined in the textual convention
IANAGmplsSwitchingType found in the IANA-GMPLS-MIB MIB module. IANAGmplsSwitchingType found in the IANA-GMPLS-TC-MIB module.
This object is only meaningful if gmplsTunnelLSPEncoding is not This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'." set to 'tunnelLspNotGmpls'."
DEFVAL { unknown } DEFVAL { unknown }
::= { gmplsTunnelEntry 4 } ::= { gmplsTunnelEntry 4 }
gmplsTunnelLinkProtection OBJECT-TYPE gmplsTunnelLinkProtection OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
extraTraffic(0), extraTraffic(0),
unprotected(1), unprotected(1),
shared (2), shared (2),
skipping to change at page 16, line 21 skipping to change at page 17, line 21
enhanced(5) enhanced(5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the level of link protection required. A "This bitmask indicates the level of link protection required. A
value of zero (no bits set) indicates that any protection may be value of zero (no bits set) indicates that any protection may be
used. The following describes these bitfields: used. The following describes these bitfields:
extraTraffic extraTraffic
Indicates that the LSP should use links that are protecting This flag is set to indicate that the LSP should use links
other (primary) traffic. Such LSPs may be preempted when the that are protecting other (primary) traffic. Such LSPs may be
links carrying the (primary) traffic being protected fail. preempted when the links carrying the (primary) traffic being
protected fail.
unprotected unprotected
Indicates that the LSP should not use any link layer This glag is set to indicate that the LSP should not use any
protection. link layer protection.
shared shared
Indicates that a shared link layer protection scheme, such as This flage is set to indicate that a shared link layer
1:N protection, should be used to support the LSP. protection scheme, such as 1:N protection, should be used to
support the LSP.
dedicatedOneToOne dedicatedOneToOne
Indicates that a dedicated link layer protection scheme, This flag is set to indicate that a dedicated link layer
i.e., 1:1 protection, should be used to support the LSP. protection scheme, i.e., 1:1 protection, should be used to
support the LSP.
dedicatedOnePlusOne dedicatedOnePlusOne
Indicates that a dedicated link layer protection scheme, This flag is set to indicate that a dedicated link layer
i.e., 1+1 protection, should be used to support the LSP. protection scheme, i.e., 1+1 protection, should be used to
support the LSP.
enhanced enhanced
Indicates that a protection scheme that is more reliable than This flag is set to indicate that a protection scheme that is
Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. more reliable than Dedicated 1+1 should be used, e.g., 4 fiber
BLSR/MS-SPRING.
This object is only meaningful if gmplsTunnelLSPEncoding is This object is only meaningful if gmplsTunnelLSPEncoding is
not set to 'tunnelLspNotGmpls'." not set to 'tunnelLspNotGmpls'."
REFERENCE REFERENCE
"Berger, L., et al., Generalized Multi-Protocol "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Label Switching (GMPLS) Signaling Functional Functional Description, RFC 3471, section 7.1."
Description, RFC 3471, January 2003."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelEntry 5 } ::= { gmplsTunnelEntry 5 }
gmplsTunnelGPid OBJECT-TYPE gmplsTunnelGPid OBJECT-TYPE
SYNTAX IANAGmplsGPid SYNTAX IANAGmplsGeneralizedPid
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the payload carried by the LSP. It is only "This object indicates the payload carried by the LSP. It is only
required when GMPLS will be used for this LSP. required when GMPLS will be used for this LSP.
The values to use are defined in the textual convention The values to use are defined in the textual convention
IANAGmplsGPid found in the IANA-GMPLS-MIB MIB module. IANAGmplsGeneralizedPid found in the IANA-GMPLS-TC-MIB module.
This object is only meaningful if gmplsTunnelLSPEncoding is not This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'." set to 'tunnelLspNotGmpls'."
DEFVAL { unknown } DEFVAL { unknown }
::= { gmplsTunnelEntry 6 } ::= { gmplsTunnelEntry 6 }
gmplsTunnelSecondary OBJECT-TYPE gmplsTunnelSecondary OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates that the requested LSP is a secondary LSP. "Indicates that the requested LSP is a secondary LSP.
This object is only meaningful if gmplsTunnelLSPEncoding is not This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'." set to 'tunnelLspNotGmpls'."
REFERENCE REFERENCE
"Berger, L., et al., Generalized Multi-Protocol "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Label Switching (GMPLS) Signaling Functional Functional Description, RFC 3471, section 7.1."
Description, RFC 3471, January 2003."
DEFVAL { false } DEFVAL { false }
::= { gmplsTunnelEntry 7 } ::= { gmplsTunnelEntry 7 }
gmplsTunnelDirection OBJECT-TYPE gmplsTunnelDirection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
forward (0), forward (0),
bidirectional (1) bidirectional (1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 18, line 36 skipping to change at page 19, line 41
hop by hop through the network. hop by hop through the network.
dynamicPartial dynamicPartial
The user specifies at least the source and The user specifies at least the source and
destination of the path and expects that the CSPF destination of the path and expects that the CSPF
will calculate the remainder of the path. The path will calculate the remainder of the path. The path
computed by CSPF is allowed to be only partially computed by CSPF is allowed to be only partially
computed allowing the remainder of the path to be computed allowing the remainder of the path to be
filled in across the network. filled in across the network.
This object deprecates mplsTunnelHopEntryPathComp." When an entry is present in gmplsTunnelTable for a tunnel,
gmplsTunnelPathComp MUST be used and any corresponding
mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable
MUST be ignored and SHOULD not be set.
mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of
MPLS-TE-STD-MIB."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
DEFVAL { dynamicFull } DEFVAL { dynamicFull }
::= { gmplsTunnelEntry 9 } ::= { gmplsTunnelEntry 9 }
gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelUpstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 10 }
gmplsTunnelUpNotRecip OBJECT-TYPE gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the upstream recipient for Notify "Indicates the address of the upstream recipient for Notify
messages relating to this tunnel. This object is only valid when messages relating to this tunnel and issued by this LSR. This
signaling a tunnel using RSVP. It is also not valid at the tail information is typically received from an upstream LSR in a Path
end of the tunnel. If set to 0, no Notify Request object will be message.
included in outgoing Path messages."
This object is only valid when signaling a tunnel using RSVP.
It is also not valid at the head end of a tunnel since there are
no upstream LSRs to which to send a Notify message.
This object is interpreted in the context of the value of
gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0,
the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to
unknown(0)."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
L. (Editor), RFC 3473, January 2003." section 4.2."
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 10 } ::= { gmplsTunnelEntry 11 }
gmplsTunnelDownNotRecip OBJECT-TYPE
SYNTAX IpAddress gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelSendResvNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 12 }
gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates to an upstream LSR the address to which it should send
downstream Notify messages relating to this tunnel.
This object is only valid when signaling a tunnel using RSVP.
It is also not valid at the head end of the tunnel since no Resv
messages are sent from that LSR for this tunnel.
If set to 0, no Notify Request object will be included in the
outgoing Resv messages.
This object is interpreted in the context of the value of
gmplsTunnelSendResvNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 13 }
gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelDownstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 14 }
gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the downstream recipient for Notify "Indicates the address of the downstream recipient for Notify
messages relating to this tunnel. messages relating to this tunnel and issued by this LSR. This
information is typically received from an upstream LSR in a Resv
message. This object is only valid when signaling a tunnel using
RSVP.
This object is only valid when signaling a tunnel using RSVP. It It is also not valid at the tail end of a tunnel since there are
is also not valid at the head end of the tunnel. no downstream LSRs to which to send a Notify message.
If set to 0, no Notify Request object will be included in This object is interpreted in the context of the value of
outgoing Resv messages." gmplsTunnelDownstreamNotifyRecipient. If this object is set to
0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set
to unknown(0)."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
(Editor), RFC 3473, January 2003." section 4.2."
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 11 } ::= { gmplsTunnelEntry 15 }
gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelSendPathNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 16 }
gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates to a downstream LSR the address to which it should
send upstream Notify messages relating to this tunnel.
This object is only valid when signaling a tunnel using RSVP.
It is also not valid at the tail end of the tunnel since no Path
messages are sent from that LSR for this tunnel.
If set to 0, no Notify Request object will be included in the
outgoing Path messages.
This object is interpreted in the context of the value of
gmplsTunnelSendPathNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 17 }
gmplsTunnelAdminStatusFlags OBJECT-TYPE gmplsTunnelAdminStatusFlags OBJECT-TYPE
SYNTAX IANAGmplsAdminStatusFlags SYNTAX IANAGmplsAdminStatusInformation
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Determines the setting of the Admin Status flags in the "Determines the setting of the Admin Status flags in the
Admin Status object or TLV, as described in RFC 3471. Setting Admin Status object or TLV, as described in RFC 3471. Setting
this field to a non-zero value will result in the inclusion of this field to a non-zero value will result in the inclusion of
the admin status object on signaling messages. the admin status object on signaling messages.
The values to use are defined in the textual convention The values to use are defined in the textual convention
IANAGmplsAdminStatusFlags found in the IANA-GMPLS-MIB MIB IANAGmplsAdminStatusInformation found in the IANA-GMPLS-TC-MIB
module. module.
This value of this object can be modified when the This value of this object can be modified when the
corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus
is active(1). By doing so, a new signaling message will be is active(1). By doing so, a new signaling message will be
triggered including the requested Admin Status object or triggered including the requested Admin Status object or
TLV." TLV."
REFERENCE REFERENCE
"Berger, L., et al., Generalized Multi-Protocol Label Switching "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
(GMPLS) Signaling Functional Description, RFC 3471, Functional Description, RFC 3471, section 8."
January 2003."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelEntry 12 } ::= { gmplsTunnelEntry 18 }
gmplsTunnelExtraParamsPtr OBJECT-TYPE gmplsTunnelExtraParamsPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some Tunnels will run over transports that can usefully support "Some Tunnels will run over transports that can usefully support
technology-specific additional parameters (for example, SONET technology-specific additional parameters (for example, SONET
resource usage). Such parameters can be supplied in an external resource usage). Such parameters can be supplied in an external
table and referenced from here. table and referenced from here.
A value of zeroDotzero in this attribute indicates that there A value of zeroDotzero in this attribute indicates that there
is no such additional information." is no such additional information."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { gmplsTunnelEntry 13 } ::= { gmplsTunnelEntry 19 }
-- End of gmplsTunnelTable
-- Begin gmplsTunnelHopTable
gmplsTunnelHopTable OBJECT-TYPE gmplsTunnelHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelHopEntry SYNTAX SEQUENCE OF GmplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelHopTable 'extends' the mplsTunnelHopTable. It is "The gmplsTunnelHopTable sparse augments the mplsTunnelHopTable
used to indicate the explicit labels to be used in an explicit of MPLS-TE-STD-MIB. It is used to indicate the explicit labels
path for a GMPLS tunnel defined in mplsTunnelTable and to be used in an explicit path for a GMPLS tunnel defined in
gmplsTunnelTable, when it is established using signaling. It mplsTunnelTable and gmplsTunnelTable, when it is established
does not insert new hops, but does define new values for hops using signaling. It does not insert new hops, but does define
defined in mplsTunnelHopTable. new values for hops defined in mplsTunnelHopTable.
Each row in this table is indexed by the same indexes as Each row in this table is indexed by the same indexes as
mplsTunnelHopTable. It is acceptable for some rows in mplsTunnelHopTable. It is acceptable for some rows in
mplsTunnelHopTable to have corresponding entries in this table mplsTunnelHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table. and some to have no corresponding entry in this table.
The storage type for an entry in this table is inherited from The storage type for this entry is given by the value
mplsTunnelHopStorageType in the corresponding entry in of mplsTunnelHopStorageType in the corresponding entry in the
mplsTunnelHopTable. mplsTunnelHopTable.
The row status of an entry in this table is controlled by The row status of an entry in this table is controlled by
mplsTunnelHopRowStatus in the corresponding entry in mplsTunnelHopRowStatus in the corresponding entry in
mplsTunnelHopTable. That is, it is not permitted to create a row mplsTunnelHopTable. That is, it is not permitted to create a row
in this table, nor to modify an existing row, when the in this table, nor to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has value active(1)." corresponding mplsTunnelHopRowStatus has value active(1)."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
(Editor), RFC 3473, January 2003." Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
::= { gmplsTeObjects 2 } ::= { gmplsTeObjects 2 }
gmplsTunnelHopEntry OBJECT-TYPE gmplsTunnelHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelHopEntry SYNTAX GmplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents additions to a tunnel hop "An entry in this table represents additions to a tunnel hop
defined in mplsTunnelHopEntry. At an ingress to a tunnel an defined in mplsTunnelHopEntry. At an ingress to a tunnel an
entry in this table is created by a network administrator for an entry in this table is created by a network administrator for an
ERLSP to be set up by a signaling protocol. At transit and ERLSP to be set up by a signaling protocol. At transit and
egress nodes an entry in this table may be used to represent the egress nodes an entry in this table may be used to represent the
skipping to change at page 21, line 25 skipping to change at page 24, line 48
protocol." protocol."
INDEX { INDEX {
mplsTunnelHopListIndex, mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex, mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex mplsTunnelHopIndex
} }
::= { gmplsTunnelHopTable 1 } ::= { gmplsTunnelHopTable 1 }
GmplsTunnelHopEntry ::= SEQUENCE { GmplsTunnelHopEntry ::= SEQUENCE {
gmplsTunnelHopLabelStatuses BITS, gmplsTunnelHopLabelStatuses BITS,
gmplsTunnelHopExpLabel Unsigned32, gmplsTunnelHopExplicitForwardLabel Unsigned32,
gmplsTunnelHopExpLabelPtr RowPointer, gmplsTunnelHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelHopExpRvrsLabel Unsigned32, gmplsTunnelHopExplicitReverseLabel Unsigned32,
gmplsTunnelHopExpRvrsLabelPtr RowPointer gmplsTunnelHopExplicitReverseLabelPtr RowPointer
} }
gmplsTunnelHopLabelStatuses OBJECT-TYPE gmplsTunnelHopLabelStatuses OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
forwardPresent (0), forwardPresent (0),
reversePresent (1) reversePresent (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels indicated by the "This bitmask indicates the presence of labels indicated by the
gmplsTunnelHopExpLabel or gmplsTunnelHopExpLabelPtr, and gmplsTunnelHopExplicitForwardLabel or
gmplsTunnelHopExpRvrsLabel or gmplsTunnelHopExpRvrsLabel gmplsTunnelHopExplicitForwardLabelPtr, and
objects. gmplsTunnelHopExplicitReverseLabel or
gmplsTunnelHopExplicitReverseLabel objects.
For the Present bits, a set bit indicates that a label is For the Present bits, a set bit indicates that a label is
present for this hop in the route. This allows zero to be a present for this hop in the route. This allows zero to be a
valid label value." valid label value."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelHopEntry 1 } ::= { gmplsTunnelHopEntry 1 }
gmplsTunnelHopExpLabel OBJECT-TYPE
gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If gmplsTunnelHopLabelStatuses object indicates that a forward "If gmplsTunnelHopLabelStatuses object indicates that a forward
label is present and gmplsTunnelHopExpLabelPtr contains the label is present and gmplsTunnelHopExplicitForwardLabelPtr
value zeroDotZero, then the label to use on this hop is found in contains the value zeroDotZero, then the label to use on this
object encoded within a 32-bit integer." hop is represented by the value of this object."
::= { gmplsTunnelHopEntry 2 } ::= { gmplsTunnelHopEntry 2 }
gmplsTunnelHopExpLabelPtr OBJECT-TYPE gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelHopLabelStatuses object indicates that a "If the gmplsTunnelHopLabelStatuses object indicates that a
forward label is present, this object contains a pointer to a forward label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of
contains the label to use on this hop in the forward direction. GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
in the forward direction.
If the gmplsTunnelHopLabelStatuses object indicates that a If the gmplsTunnelHopLabelStatuses object indicates that a
forward label is present and this object contains the value forward label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExpLabel object." gmplsTunnelHopExplicitForwardLabel object."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 3 } ::= { gmplsTunnelHopEntry 3 }
gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE
gmplsTunnelHopExpRvrsLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelHopLabelStatuses object indicates that a "If the gmplsTunnelHopLabelStatuses object indicates that a
reverse label is present and gmplsTunnelHopExpRvrsLabelPtr reverse label is present and
contains the value zeroDotZero, then the label to use on this gmplsTunnelHopExplicitReverseLabelPtr contains the value
this hop is found in this object encoded as a 32-bit integer." zeroDotZero, then the label to use on this this hop is found in
this object encoded as a 32-bit integer."
::= { gmplsTunnelHopEntry 4 } ::= { gmplsTunnelHopEntry 4 }
gmplsTunnelHopExpRvrsLabelPtr OBJECT-TYPE
gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelHopLabelStatuses object indicates that a "If the gmplsTunnelHopLabelStatuses object indicates that a
reverse label is present, this object contains a pointer to a reverse label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of the
contains the label to use on this hop in the reverse direction. GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
in the reverse direction.
If the gmplsTunnelHopLabelStatuses object indicates that a If the gmplsTunnelHopLabelStatuses object indicates that a
reverse label is present and this object contains the value reverse label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExpRvrsLabel object." gmplsTunnelHopExplicitReverseLabel object."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 5 } ::= { gmplsTunnelHopEntry 5 }
-- End of gmplsTunnelHopTable
-- Tunnel Actual Route Hop table.
gmplsTunnelARHopTable OBJECT-TYPE gmplsTunnelARHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelARHopEntry SYNTAX SEQUENCE OF GmplsTunnelARHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelARHopTable 'extends' the mplsTunnelARHopTable. It "The gmplsTunnelARHopTable sparse augments the
is used to indicate the labels currently in use for a GMPLS mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate
tunnel defined in mplsTunnelTable and gmplsTunnelTable, as the labels currently in use for a GMPLS tunnel defined in
reported by the signaling protocol. It does not insert new hops, mplsTunnelTable and gmplsTunnelTable, as reported by the
but does define new values for hops defined in signaling protocol. It does not insert new hops, but does define
mplsTunnelARHopTable. new values for hops defined in mplsTunnelARHopTable.
Each row in this table is indexed by the same indexes as Each row in this table is indexed by the same indexes as
mplsTunnelARHopTable. It is acceptable for some rows in mplsTunnelARHopTable. It is acceptable for some rows in
mplsTunnelARHopTable to have corresponding entries in this table mplsTunnelARHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table. and some to have no corresponding entry in this table.
Note that since the information necessary to build entries Note that since the information necessary to build entries
within this table is not provided by some signaling protocols within this table is not provided by some signaling protocols
and might not be returned in all cases of other signaling and might not be returned in all cases of other signaling
protocols, implementation of this table and mplsTunnelARHopTable protocols, implementation of this table and mplsTunnelARHopTable
skipping to change at page 24, line 4 skipping to change at page 27, line 11
Note that since the information necessary to build entries Note that since the information necessary to build entries
within this table is not provided by some signaling protocols within this table is not provided by some signaling protocols
and might not be returned in all cases of other signaling and might not be returned in all cases of other signaling
protocols, implementation of this table and mplsTunnelARHopTable protocols, implementation of this table and mplsTunnelARHopTable
is optional. Furthermore, since the information in this table is is optional. Furthermore, since the information in this table is
actually provided by the signaling protocol after the path has actually provided by the signaling protocol after the path has
been set-up, the entries in this table are provided only for been set-up, the entries in this table are provided only for
observation, and hence, all variables in this table are observation, and hence, all variables in this table are
accessible exclusively as read-only." accessible exclusively as read-only."
REFERENCE REFERENCE
"1. Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, "1. Extensions to RSVP for LSP Tunnels, RFC 3209.
December 2001 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
(Editor), RFC 3473, January 2003." Management Information Base (MIB), RFC 3812.
::= { gmplsTeObjects 3 } ::= { gmplsTeObjects 3 }
gmplsTunnelARHopEntry OBJECT-TYPE gmplsTunnelARHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelARHopEntry SYNTAX GmplsTunnelARHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents additions to a tunnel hop "An entry in this table represents additions to a tunnel hop
visible in mplsTunnelARHopEntry. An entry is created by the visible in mplsTunnelARHopEntry. An entry is created by the
signaling protocol for a signaled ERLSP set up by the signaling signaling protocol for a signaled ERLSP set up by the signaling
protocol. protocol.
At any node on the LSP (ingress, transit or egress) Thus at this At any node on the LSP (ingress, transit or egress), this table
table and mplsTunnelARHopTable (if the tables are supported and and mplsTunnelARHopTable (if the tables are supported and if the
if the signaling protocol is recording actual route information) signaling protocol is recording actual route information)
contains the actual route of the whole tunnel. If the signaling contain the actual route of the whole tunnel. If the signaling
protocol is not recording the actual route, this table MAY protocol is not recording the actual route, this table MAY
report the information from the gmplsTunnelHopTable or the report the information from the gmplsTunnelHopTable or the
gmplsTunnelCHopTable. gmplsTunnelCHopTable.
Note that the recording of actual labels is distinct from the Note that the recording of actual labels is distinct from the
recording of the actual route in some signaling protocols. This recording of the actual route in some signaling protocols. This
feature is enabled using the gmplsTunnelAttributes object." feature is enabled using the gmplsTunnelAttributes object."
INDEX { INDEX {
mplsTunnelARHopListIndex, mplsTunnelARHopListIndex,
mplsTunnelARHopIndex mplsTunnelARHopIndex
skipping to change at page 24, line 37 skipping to change at page 28, line 4
gmplsTunnelCHopTable. gmplsTunnelCHopTable.
Note that the recording of actual labels is distinct from the Note that the recording of actual labels is distinct from the
recording of the actual route in some signaling protocols. This recording of the actual route in some signaling protocols. This
feature is enabled using the gmplsTunnelAttributes object." feature is enabled using the gmplsTunnelAttributes object."
INDEX { INDEX {
mplsTunnelARHopListIndex, mplsTunnelARHopListIndex,
mplsTunnelARHopIndex mplsTunnelARHopIndex
} }
::= { gmplsTunnelARHopTable 1 } ::= { gmplsTunnelARHopTable 1 }
GmplsTunnelARHopEntry ::= SEQUENCE { GmplsTunnelARHopEntry ::= SEQUENCE {
gmplsTunnelARHopLabelStatuses BITS, gmplsTunnelARHopLabelStatuses BITS,
gmplsTunnelARHopExpLabel Unsigned32, gmplsTunnelARHopExplicitForwardLabel Unsigned32,
gmplsTunnelARHopExpLabelPtr RowPointer, gmplsTunnelARHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelARHopExpRvrsLabel Unsigned32, gmplsTunnelARHopExplicitReverseLabel Unsigned32,
gmplsTunnelARHopExpRvrsLabelPtr RowPointer, gmplsTunnelARHopExplicitReverseLabelPtr RowPointer,
gmplsTunnelARHopProtection BITS gmplsTunnelARHopProtection BITS
} }
gmplsTunnelARHopLabelStatuses OBJECT-TYPE gmplsTunnelARHopLabelStatuses OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
forwardPresent (0), forwardPresent (0),
reversePresent (1), reversePresent (1),
forwardGlobal (2), forwardGlobal (2),
reverseGlobal (3) reverseGlobal (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 25, line 15 skipping to change at page 28, line 24
SYNTAX BITS { SYNTAX BITS {
forwardPresent (0), forwardPresent (0),
reversePresent (1), reversePresent (1),
forwardGlobal (2), forwardGlobal (2),
reverseGlobal (3) reverseGlobal (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence and status of labels "This bitmask indicates the presence and status of labels
indicated by the gmplsTunnelARHopExpLabel or indicated by the gmplsTunnelARHopExplicitForwardLabel or
gmplsTunnelARHopExpLabelPtr, and gmplsTunnelARHopExpRvrsLabel or gmplsTunnelARHopExplicitForwardLabelPtr, and
gmplsTunnelARHopExpRvrsLabelPtr objects. gmplsTunnelARHopExplicitReverseLabel or
gmplsTunnelARHopExplicitReverseLabelPtr objects.
For the Present bits, a set bit indicates that a label is For the Present bits, a set bit indicates that a label is
present for this hop in the route. For the Global bits, a set present for this hop in the route. For the Global bits, a set
bit indicates that the label comes from the Global Label Space. bit indicates that the label comes from the Global Label Space.
A clear bit indicates that this is a Per-Interface label. A A clear bit indicates that this is a Per-Interface label. A
Global bit only has meaning if the corresponding Present bit is Global bit only has meaning if the corresponding Present bit is
set." set."
::= { gmplsTunnelARHopEntry 1 } ::= { gmplsTunnelARHopEntry 1 }
gmplsTunnelARHopExpLabel OBJECT-TYPE gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a "If the gmplsTunnelARHopLabelStatuses object indicates that a
forward label is present and gmplsTunnelARHopExpLabelPtr forward label is present and
contains the value zeroDotZero, then the label in use on this gmplsTunnelARHopExplicitForwardLabelPtr contains the value
hop is found in this object encoded within a 32-bit integer." zeroDotZero, then the label in use on this hop is found in this
object encoded within a 32-bit integer."
::= { gmplsTunnelARHopEntry 2 } ::= { gmplsTunnelARHopEntry 2 }
gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE
gmplsTunnelARHopExpLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a "If the gmplsTunnelARHopLabelStatuses object indicates that a
forward label is present, this object contains a pointer to a forward label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of the
contains the label in use on this hop in the forward direction. GMPLS-LABEL-STD-MIB) that contains the label in use on this hop
in the forward direction.
If the gmplsTunnelARHopLabelStatuses object indicates that a If the gmplsTunnelARHopLabelStatuses object indicates that a
forward label is present and this object contains the value forward label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExpLabel object." gmplsTunnelARHopExplicitForwardLabel object."
::= { gmplsTunnelARHopEntry 3 } ::= { gmplsTunnelARHopEntry 3 }
gmplsTunnelARHopExpRvrsLabel OBJECT-TYPE
gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a "If the gmplsTunnelARHopLabelStatuses object indicates that a
reverse label is present and gmplsTunnelARHopExpRvrsLabelPtr reverse label is present and
contains the value zeroDotZero, then the label in use on this gmplsTunnelARHopExplicitReverseLabelPtr contains the value
hop is found in this object encoded as a 32-bit integer." zeroDotZero, then the label in use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 4 } ::= { gmplsTunnelARHopEntry 4 }
gmplsTunnelARHopExpRvrsLabelPtr OBJECT-TYPE gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a "If the gmplsTunnelARHopLabelStatuses object indicates that a
reverse label is present, this object contains a pointer to a reverse label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of the
contains the label in use on this hop in the reverse direction. GMPLS-LABEL-STD-MIB) that contains the label in use on this hop
in the reverse direction.
If the gmplsTunnelARHopLabelStatuses object indicates that a If the gmplsTunnelARHopLabelStatuses object indicates that a
reverse label is present and this object contains the value reverse label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExpRvrsLabel object." gmplsTunnelARHopExplicitReverseLabel object."
::= { gmplsTunnelARHopEntry 5 } ::= { gmplsTunnelARHopEntry 5 }
gmplsTunnelARHopProtection OBJECT-TYPE gmplsTunnelARHopProtection OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
localAvailable (0), localAvailable (0),
localInUse (1) localInUse (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Availability and usage of protection on the reported link. "Availability and usage of protection on the reported link.
skipping to change at page 26, line 41 skipping to change at page 30, line 15
SYNTAX BITS { SYNTAX BITS {
localAvailable (0), localAvailable (0),
localInUse (1) localInUse (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Availability and usage of protection on the reported link. "Availability and usage of protection on the reported link.
localAvailable localAvailable
Indicates that the link downstream of this node is protected This flag is set to indicate that the link downstream of this
via a local repair mechanism. node is protected via a local repair mechanism.
localInUse localInUse
Indicates that a local repair mechanism is in use to maintain This flag is set to indicate that a local repair mechanism is
this tunnel (usually in the face of an outage of the link it in use to maintain this tunnel (usually in the face of an
was previously routed over)." outage of the link it was previously routed over)."
REFERENCE
1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 4.4.1."
::= { gmplsTunnelARHopEntry 6 } ::= { gmplsTunnelARHopEntry 6 }
-- End of mplsTunnelARHopTable
-- Tunnel Computed Hop table.
gmplsTunnelCHopTable OBJECT-TYPE gmplsTunnelCHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelCHopEntry SYNTAX SEQUENCE OF GmplsTunnelCHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelCHopTable 'extends' the mplsTunnelCHopTable. It "The gmplsTunnelCHopTable sparse augments the mplsTunnelCHopTable
is used to indicate additional information about the hops of a of MPLS-TE-STD-MIB. It is used to indicate additional
GMPLS tunnel defined in mplsTunnelTable and gmplsTunnelTable, as information about the hops of a GMPLS tunnel defined in
computed by a constraint-based routing protocol, based on the mplsTunnelTable and gmplsTunnelTable, as computed by a
constraint-based routing protocol, based on the
mplsTunnelHopTable and the gmplsTunnelHopTable. mplsTunnelHopTable and the gmplsTunnelHopTable.
Each row in this table is indexed by the same indexes as Each row in this table is indexed by the same indexes as
mplsTunnelCHopTable. It is acceptable for some rows in mplsTunnelCHopTable. It is acceptable for some rows in
mplsTunnelCHopTable to have corresponding entries in this table mplsTunnelCHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table. and some to have no corresponding entry in this table.
Please note that since the information necessary to build Please note that since the information necessary to build
entries within this table may not be supported by some LSRs, entries within this table may not be supported by some LSRs,
implementation of this table is optional. implementation of this table is optional.
Furthermore, since the information in this table is actually Furthermore, since the information in this table is actually
provided by a path computation component after the path has been provided by a path computation component after the path has been
computed, the entries in this table are provided only for computed, the entries in this table are provided only for
observation, and hence, all objects in this table are accessible observation, and hence, all objects in this table are accessible
exclusively as read-only." exclusively as read-only."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
(Editor), RFC 3473, January 2003." Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
::= { gmplsTeObjects 4 } ::= { gmplsTeObjects 4 }
gmplsTunnelCHopEntry OBJECT-TYPE gmplsTunnelCHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelCHopEntry SYNTAX GmplsTunnelCHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents additions to a computed tunnel "An entry in this table represents additions to a computed tunnel
hop visible in mplsTunnelCHopEntry. An entry is created by a hop visible in mplsTunnelCHopEntry. An entry is created by a
path computation component based on the hops specified in the path computation component based on the hops specified in the
skipping to change at page 28, line 4 skipping to change at page 31, line 28
corresponding mplsTunnelHopTable and gmplsTunnelHopTable. corresponding mplsTunnelHopTable and gmplsTunnelHopTable.
At a transit LSR this table (if the table is supported) MAY At a transit LSR this table (if the table is supported) MAY
contain the path computed by path computation engine on (or on contain the path computed by path computation engine on (or on
behalf of) the transit LSR." behalf of) the transit LSR."
INDEX { INDEX {
mplsTunnelCHopListIndex, mplsTunnelCHopListIndex,
mplsTunnelCHopIndex mplsTunnelCHopIndex
} }
::= { gmplsTunnelCHopTable 1 } ::= { gmplsTunnelCHopTable 1 }
GmplsTunnelCHopEntry ::= SEQUENCE { GmplsTunnelCHopEntry ::= SEQUENCE {
gmplsTunnelCHopLabelStatuses BITS, gmplsTunnelCHopLabelStatuses BITS,
gmplsTunnelCHopExpLabel Unsigned32, gmplsTunnelCHopExplicitForwardLabel Unsigned32,
gmplsTunnelCHopExpLabelPtr RowPointer, gmplsTunnelCHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelCHopExpRvrsLabel Unsigned32, gmplsTunnelCHopExplicitReverseLabel Unsigned32,
gmplsTunnelCHopExpRvrsLabelPtr RowPointer gmplsTunnelCHopExplicitReverseLabelPtr RowPointer
} }
gmplsTunnelCHopLabelStatuses OBJECT-TYPE gmplsTunnelCHopLabelStatuses OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
forwardPresent (0), forwardPresent (0),
reversePresent (1) reversePresent (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels indicated by the "This bitmask indicates the presence of labels indicated by the
gmplsTunnelCHopExpLabel or gmplsTunnelCHopExpLabelPtr and gmplsTunnelCHopExplicitForwardLabel or
gmplsTunnelCHopExpRvrsLabel or gmplsTunnelCHopExpRvrsLabelPtr gmplsTunnelCHopExplicitForwardLabelPtr and
objects. gmplsTunnelCHopExplicitReverseLabel or
gmplsTunnelCHopExplicitReverseLabelPtr objects.
A set bit indicates that a label is present for this hop in the A set bit indicates that a label is present for this hop in the
route thus allowing zero to be a valid label value." route thus allowing zero to be a valid label value."
::= { gmplsTunnelCHopEntry 1 } ::= { gmplsTunnelCHopEntry 1 }
gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE
gmplsTunnelCHopExpLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a "If the gmplsTunnelCHopLabelStatuses object indicates that a
forward label is present and gmplsTunnelCHopExpLabelPtr contains forward label is present and
the value zeroDotZero, then the label to use on this hop is gmplsTunnelCHopExplicitForwardLabelPtr contains the value
found in this object encoded within a 32-bit integer." zeroDotZero, then the label to use on this hop is found in this
object encoded within a 32-bit integer."
::= { gmplsTunnelCHopEntry 2 } ::= { gmplsTunnelCHopEntry 2 }
gmplsTunnelCHopExpLabelPtr OBJECT-TYPE gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a "If the gmplsTunnelCHopLabelStatuses object indicates that a
forward label is present, this object contains a pointer to a forward label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of the
contains the label to use on this hop in the forward direction. GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
in the forward direction.
If the gmplsTunnelCHopLabelStatuses object indicates that a If the gmplsTunnelCHopLabelStatuses object indicates that a
forward label is present and this object contains the value forward label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExpLabel object." gmplsTunnelCHopExplicitForwardLabel object."
::= { gmplsTunnelCHopEntry 3 } ::= { gmplsTunnelCHopEntry 3 }
gmplsTunnelCHopExpRvrsLabel OBJECT-TYPE
gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a "If the gmplsTunnelCHopLabelStatuses object indicates that a
reverse label is present and gmplsTunnelCHopExpRvrsLabelPtr reverse label is present and
contains the value zeroDotZero, then the label to use on this gmplsTunnelCHopExplicitReverseLabelPtr contains the value
hop is found in this object encoded as a 32-bit integer." zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 4 } ::= { gmplsTunnelCHopEntry 4 }
gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE
gmplsTunnelCHopExpRvrsLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a "If the gmplsTunnelCHopLabelStatuses object indicates that a
reverse label is present, this object contains a pointer to a reverse label is present, this object contains a pointer to a
row in another MIB table (such as the gmplsLabelTable) that row in another MIB table (such as the gmplsLabelTable of the
contains the label to use on this hop in the reverse direction. GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
in the reverse direction.
If the gmplsTunnelCHopLabelStatuses object indicates that a If the gmplsTunnelCHopLabelStatuses object indicates that a
reverse label is present and this object contains the value reverse label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExpRvrsLabel object." gmplsTunnelCHopExplicitReverseLabel object."
::= { gmplsTunnelCHopEntry 5 } ::= { gmplsTunnelCHopEntry 5 }
-- End of gmplsTunnelCHopTable
-- GMPLS Tunnel Reverse Direction Performance Table.
gmplsTunnelReversePerfTable OBJECT-TYPE gmplsTunnelReversePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table 'augments' the gmplsTunnelTable to provides "This table 'augments' the gmplsTunnelTable to provides
per-tunnel packet performance information for the reverse per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel. It can be seen as direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable which augments the supplementing the mplsTunnelPerfTable which augments the
mplsTunnelTable." mplsTunnelTable.
For links that do not transport packets, these packet counters
cannot be maintained. For such links, attempts to read the
objects in this table will return noSuchInstance.
A tunnel can be known to be bidirectional by inspecting the
gmplsTunnelDirection object."
REFERENCE REFERENCE
"Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), Srinivasan, C., Viswanathan, Management Information Base (MIB), RFC 3812."
A., Nadeau, T., RFC 3812, June 2004."
::= { gmplsTeObjects 5 } ::= { gmplsTeObjects 5 }
gmplsTunnelReversePerfEntry OBJECT-TYPE gmplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX GmplsTunnelReversePerfEntry SYNTAX GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every "An entry in this table is created by the LSR for every
bidirectional GMPLS tunnel where packets are visible to the bidirectional GMPLS tunnel where packets are visible to the
LSR." LSR."
AUGMENTS { gmplsTunnelEntry } AUGMENTS { gmplsTunnelEntry }
::= { gmplsTunnelReversePerfTable 1 } ::= { gmplsTunnelReversePerfTable 1 }
skipping to change at page 30, line 29 skipping to change at page 34, line 18
gmplsTunnelReversePerfBytes Counter32, gmplsTunnelReversePerfBytes Counter32,
gmplsTunnelReversePerfHCBytes Counter64 gmplsTunnelReversePerfHCBytes Counter64
} }
gmplsTunnelReversePerfPackets OBJECT-TYPE gmplsTunnelReversePerfPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets forwarded on the tunnel in the reverse "Number of packets forwarded on the tunnel in the reverse
direction if it is bidirectional." direction if it is bidirectional.
This object should represents the 32-bit value of the least
significant part of the 64-bit value if both
gmplsTunnelReversePerfHCPackets and this object are returned.
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return a
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 1 } ::= { gmplsTunnelReversePerfEntry 1 }
gmplsTunnelReversePerfHCPackets OBJECT-TYPE gmplsTunnelReversePerfHCPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"High capacity counter for number of packets forwarded on the "High capacity counter for number of packets forwarded on the
tunnel in the reverse direction if it is bidirectional." tunnel in the reverse direction if it is bidirectional.
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return a
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 2 } ::= { gmplsTunnelReversePerfEntry 2 }
gmplsTunnelReversePerfErrors OBJECT-TYPE gmplsTunnelReversePerfErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of errored packets received on the tunnel in the reverse "Number of errored packets received on the tunnel in the reverse
direction if it is bidirectional." direction if it is bidirectional. For links that do not
transport packets, this packet counter cannot be maintained. For
such links, this value will return a noSuchInstance."
::= { gmplsTunnelReversePerfEntry 3 } ::= { gmplsTunnelReversePerfEntry 3 }
gmplsTunnelReversePerfBytes OBJECT-TYPE gmplsTunnelReversePerfBytes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of bytes forwarded on the tunnel in the reverse direction "Number of bytes forwarded on the tunnel in the reverse direction
if it is bidirectional." if it is bidirectional.
This object should represents the 32-bit value of the least
significant part of the 64-bit value if both
gmplsTunnelReversePerfHCBytes and this object are returned.
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return a
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 4 } ::= { gmplsTunnelReversePerfEntry 4 }
gmplsTunnelReversePerfHCBytes OBJECT-TYPE gmplsTunnelReversePerfHCBytes OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"High capacity counter for number of bytes forwarded on the "High capacity counter for number of bytes forwarded on the
tunnel in the reverse direction if it is bidirectional." tunnel in the reverse direction if it is bidirectional.
::= { gmplsTunnelReversePerfEntry 5 }
-- End of gmplsTunnelReversePerfTable
-- GMPLS Tunnel Error Table. For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return a
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 5 }
gmplsTunnelErrorTable OBJECT-TYPE gmplsTunnelErrorTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelErrorEntry SYNTAX SEQUENCE OF GmplsTunnelErrorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table 'augments' the mplsTunnelTable "This table 'augments' the mplsTunnelTable
This table provides per-tunnel information about errors. Errors This table provides per-tunnel information about errors. Errors
may be detected locally or reported through the signaling may be detected locally or reported through the signaling
protocol. Error reporting is not exclusive to GMPLS and this protocol. Error reporting is not exclusive to GMPLS and this
table may be applied in MPLS systems." table may be applied in MPLS systems.
Entries in this table are not persistent over system resets
or re-initializations of the management system."
REFERENCE REFERENCE
"Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), Srinivasan, C., Viswanathan, Management Information Base (MIB), RFC 3812."
A., Nadeau, T., RFC 3812, June 2004."
::= { gmplsTeObjects 6 } ::= { gmplsTeObjects 6 }
gmplsTunnelErrorEntry OBJECT-TYPE gmplsTunnelErrorEntry OBJECT-TYPE
SYNTAX GmplsTunnelErrorEntry SYNTAX GmplsTunnelErrorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every tunnel "An entry in this table is created by the LSR for every tunnel
where error information is visible to the LSR. where error information is visible to the LSR.
Note that systems which read the objects in this table one at a Note that systems which read the objects in this table one at a
time may experience a discontinuity as the result of a new error time may experience a discontinuity as the result of a new error
occurring in between object reads. Systems that are vulnerable occurring in between object reads. Systems that are vulnerable
to this should read gmplsTunnelErrorLastTime before and after to this should read gmplsTunnelErrorLastTime before and after
reading the other objects." reading the other objects."
AUGMENTS { mplsTunnelEntry } AUGMENTS { mplsTunnelEntry }
::= { gmplsTunnelErrorTable 1 } ::= { gmplsTunnelErrorTable 1 }
GmplsTunnelErrorEntry ::= SEQUENCE { GmplsTunnelErrorEntry ::= SEQUENCE {
gmplsTunnelErrorLastErrorType INTEGER, gmplsTunnelErrorLastErrorType INTEGER,
skipping to change at page 32, line 27 skipping to change at page 36, line 28
::= { gmplsTunnelErrorTable 1 } ::= { gmplsTunnelErrorTable 1 }
GmplsTunnelErrorEntry ::= SEQUENCE { GmplsTunnelErrorEntry ::= SEQUENCE {
gmplsTunnelErrorLastErrorType INTEGER, gmplsTunnelErrorLastErrorType INTEGER,
gmplsTunnelErrorLastTime TimeStamp, gmplsTunnelErrorLastTime TimeStamp,
gmplsTunnelErrorReporterType InetAddressType, gmplsTunnelErrorReporterType InetAddressType,
gmplsTunnelErrorReporter InetAddress, gmplsTunnelErrorReporter InetAddress,
gmplsTunnelErrorCode Unsigned32, gmplsTunnelErrorCode Unsigned32,
gmplsTunnelErrorSubcode Unsigned32, gmplsTunnelErrorSubcode Unsigned32,
gmplsTunnelErrorTLVs OCTET STRING, gmplsTunnelErrorTLVs OCTET STRING,
gmplsTunnelErrorHelpString DisplayString gmplsTunnelErrorHelpString SnmpAdminString
} }
gmplsTunnelErrorLastErrorType OBJECT-TYPE gmplsTunnelErrorLastErrorType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noError (0), noError (0),
unknown (1), unknown (1),
protocol (2), protocol (2),
pathComputation (3), pathComputation (3),
localConfiguration (4), localConfiguration (4),
localResources (5), localResources (5),
skipping to change at page 33, line 5 skipping to change at page 37, line 9
gmplsTunnelErrorProtocolSubcode. gmplsTunnelErrorProtocolSubcode.
A value of noError (0) shows that there is no error associated A value of noError (0) shows that there is no error associated
with this tunnel and means that the other objects in this table with this tunnel and means that the other objects in this table
entry have no meaning. entry have no meaning.
A value of unknown (1) shows that there is an error but that no A value of unknown (1) shows that there is an error but that no
additional information about the cause is known. The error may additional information about the cause is known. The error may
have been received in a signaled message or generated locally. have been received in a signaled message or generated locally.
A value of protocol (2) or pathComputation (3) indicates that A value of protocol (2) or pathComputation (3) indicates the
the cause of an error and identifies an error that has been cause of an error and identifies an error that has been received
received through signaling or will itself be signaled. through signaling or will itself be signaled.
A value of localConfiguration (4), localResources (5) or A value of localConfiguration (4), localResources (5) or
localOther (6) identifies an error which has been detected localOther (6) identifies an error which has been detected
by the local node, but which will not be reported through by the local node, but which will not be reported through
signaling." signaling."
::= { gmplsTunnelErrorEntry 1 } ::= { gmplsTunnelErrorEntry 1 }
gmplsTunnelErrorLastTime OBJECT-TYPE gmplsTunnelErrorLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which the last error occurred. This is presented as "The time at which the last error occurred. This is presented as
the value of SysUpTime when the error occurred or was reported the value of SysUpTime when the error occurred or was reported
to this node. to this node.
If gmplsTunnelErrorLastErrorType has the value noError (0), then If gmplsTunnelErrorLastErrorType has the value noError (0), then
this object is ignored." this object is ignored.
Note that entries in this table are not persistent over system
resets or re-initializations of the management system."
::= { gmplsTunnelErrorEntry 2 } ::= { gmplsTunnelErrorEntry 2 }
gmplsTunnelErrorReporterType OBJECT-TYPE gmplsTunnelErrorReporterType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the error reported. "The address type of the error reported.
This object is used to aid in interpretation of This object is used to aid in interpretation of
skipping to change at page 34, line 8 skipping to change at page 38, line 15
If gmplsTunnelErrorLastErrorType has the value noError (0), then If gmplsTunnelErrorLastErrorType has the value noError (0), then
this object is ignored. this object is ignored.
If gmplsTunnelErrorLastErrorType has the value unknown (1), If gmplsTunnelErrorLastErrorType has the value unknown (1),
localConfiguration (4), localResources (5), or localOther (6) localConfiguration (4), localResources (5), or localOther (6)
this object MAY contain a zero value. this object MAY contain a zero value.
This object should be interpreted in the context of the value of This object should be interpreted in the context of the value of
the object gmplsTunnelErrorReporterType." the object gmplsTunnelErrorReporterType."
REFERENCE REFERENCE
"RFC4001, Textual Conventions for Internet Network Addresses, "1. Textual Conventions for Internet Network Addresses, RFC 4001,
Section 4. Usage Hints." section 4, Usage Hints."
::= { gmplsTunnelErrorEntry 4 } ::= { gmplsTunnelErrorEntry 4 }
gmplsTunnelErrorCode OBJECT-TYPE gmplsTunnelErrorCode OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The primary error code associated with the last error. "The primary error code associated with the last error.
The interpretation of this error code depends on the value of The interpretation of this error code depends on the value of
gmplsTunnelErrorLastErrorType. If the value of gmplsTunnelErrorLastErrorType. If the value of
gmplsTunnelErrorLastErrorType is noError (0) the value of this gmplsTunnelErrorLastErrorType is noError (0) the value of this
object should be 0 and should be ignored. If the value of object should be 0 and should be ignored. If the value of
gmplsTunnelErrorLastErrorType is protocol (2) the error should gmplsTunnelErrorLastErrorType is protocol (2) the error should
be interpreted in the context of the signling protocol be interpreted in the context of the signling protocol
identified by the mplsTunnelSignallingProto object. identified by the mplsTunnelSignallingProto object."
Values in excess 32767 of are not used by signaling protocols
and may safely be used as implementation-specific error codes."
REFERENCE REFERENCE
"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- "1. Resource ReserVation Protocol -- Version 1 Functional
Version 1 Functional Specification, RFC 2205, September 1997. Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
RFC 3209, December 2001. section 7.3.
3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
(Editor), RFC 3473, January 2003." section 13.1."
::= { gmplsTunnelErrorEntry 5 } ::= { gmplsTunnelErrorEntry 5 }
gmplsTunnelErrorSubcode OBJECT-TYPE gmplsTunnelErrorSubcode OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The secondary error code associated with the last error and the "The secondary error code associated with the last error and the
protocol used to signal this tunnel. This value is interpreted protocol used to signal this tunnel. This value is interpreted
in the context of the value of gmplsTunnelErrorCode. in the context of the value of gmplsTunnelErrorCode.
If the value of gmplsTunnelErrorLastErrorType is noError (0) the If the value of gmplsTunnelErrorLastErrorType is noError (0) the
value of this object should be 0 and should be ignored." value of this object should be 0 and should be ignored."
REFERENCE REFERENCE
"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- "1. Resource ReserVation Protocol -- Version 1 Functional
Version 1 Functional Specification, RFC 2205, September 1997. Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al.,
RFC 3209, December 2001. 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. section 7.3.
(Editor), RFC 3473, January 2003." 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 13.1."
::= { gmplsTunnelErrorEntry 6 } ::= { gmplsTunnelErrorEntry 6 }
gmplsTunnelErrorTLVs OBJECT-TYPE gmplsTunnelErrorTLVs OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence of interface identifier TLVs reported with the "The sequence of interface identifier TLVs reported with the
error by the protocol code. The interpretation of the TLVs and error by the protocol code. The interpretation of the TLVs and
the encoding within the protocol are described in the the encoding within the protocol are described in the
references. A value of zero in the first octet indicates that no references. A value of zero in the first octet indicates that no
TLVs are present." TLVs are present."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
(Editor), RFC 3473, January 2003." section 8.2."
::= { gmplsTunnelErrorEntry 7 } ::= { gmplsTunnelErrorEntry 7 }
gmplsTunnelErrorHelpString OBJECT-TYPE gmplsTunnelErrorHelpString OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about the last error, "A textual string containing information about the last error,
recovery actions and support advice. If there is no help string recovery actions and support advice. If there is no help string
this object contains a zero length string. this object contains a zero length string.
If the value of gmplsTunnelErrorLastErrorType is noError (0) If the value of gmplsTunnelErrorLastErrorType is noError (0)
this object should contain a zero length string, but may contain this object should contain a zero length string, but may contain
a help string indicating that there is no error." a help string indicating that there is no error."
::= { gmplsTunnelErrorEntry 8 } ::= { gmplsTunnelErrorEntry 8 }
-- GMPLS Notifications.
gmplsTunnelDown NOTIFICATION-TYPE gmplsTunnelDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsTunnelAdminStatus, mplsTunnelAdminStatus,
mplsTunnelOperStatus, mplsTunnelOperStatus,
gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorReporterType, gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter, gmplsTunnelErrorReporter,
gmplsTunnelErrorCode, gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode gmplsTunnelErrorSubcode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a mplsTunnelOperStatus "This notification is generated when a mplsTunnelOperStatus
object for one of the configured tunnels is about to enter the object for a tunnel in the gmplsTunnelTable is about to enter
down state from some other state (but not from the notPresent the down state from some other state (but not from the
state). This other state is indicated by the included value of notPresent state). This other state is indicated by the
mplsTunnelOperStatus. included value of mplsTunnelOperStatus.
The objects in this notification provide additional error The objects in this notification provide additional error
information that indicates the reason why the tunnel has information that indicates the reason why the tunnel has
transitioned down. transitioned down.
Note that an implementation SHOULD only issue one of Note that an implementation MUST only issue one of
mplsTunnelDown and gmplsTunnelDown for a single event on a mplsTunnelDown and gmplsTunnelDown for any single event on a
single tunnel." single tunnel. If the tunnel has an entry in gmplsTunnelTable
::= { gmplsTeNotifications 1 } an implementation SHOULD use gmplsTunnelDown for all tunnel
down events and SHOULD NOT use mplsTunnelDown.
-- End of notifications. This notification is subject to the control of the
mplsTunnelNotificationEnable. When that object is set to
false(2) then the notification must not be issued.
-- Module compliance. Further, this notification is also subject to
mplsTunnelNotificationMaxRate. That object indicates the
maximum number of notifications issued per second. If events
occur more rapidly, the implementation may simply fail to emit
some notifications during that period, or may queue them until
an appropriate time. The notification rate applies to the sum
of all notificaitons in the MPLS-TE-STD-MIB and
GMPLS-TE-STD-MIB modules applied across the whole of the
reporting device.
mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown,
mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate
objects are found in MPLS-TE-STD-MIB."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB), RFC 3812."
::= { gmplsTeNotifications 1 }
gmplsTeGroups gmplsTeGroups
OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
gmplsTeCompliances gmplsTeCompliances
OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
-- The mandatory group has to be implemented by all LSRs that -- The mandatory group has to be implemented by all LSRs that
-- originate, terminate or act as transit for TE-LSPs/tunnels. -- originate, terminate or act as transit for TE-LSPs/tunnels.
-- In addition, depending on the type of tunnels supported, other -- In addition, depending on the type of tunnels supported, other
-- groups become mandatory as explained below. -- groups become mandatory as explained below.
gmplsTeModuleFullCompliance MODULE-COMPLIANCE gmplsTeModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support for "Compliance statement for agents that provide full support for
skipping to change at page 37, line 15 skipping to change at page 41, line 51
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup gmplsTunnelScalarGroup
} }
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support signaled "This group is mandatory for devices which support signaled
tunnel set up, in addition to gmplsTunnelGroup. The following tunnel set up, in addition to gmplsTunnelGroup. The following
constraints apply: constraints apply:
mplsTunnelSignallingProto should be at least read-only
mplsTunnelSignallingProto should be at least read-only returning returning a value of ldp(2), or rsvp(3)."
a value of ldp(2), or rsvp(3)."
GROUP gmplsTunnelIsNotIntfcGroup GROUP gmplsTunnelIsNotIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support tunnels that "This group is mandatory for devices which support tunnels that
are not interfaces, in addition to gmplsTunnelGroup. The are not interfaces, in addition to gmplsTunnelGroup. The
following constraints apply: following constraints apply:
gmplsTunnelIsIf must at least be read-only returning no(0)." mplsTunnelIsIf must at least be read-only returning no(0)."
GROUP gmplsTunnelIsIntfcGroup GROUP gmplsTunnelIsIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support tunnels that "This group is mandatory for devices which support tunnels that
are interfaces, in addition to gmplsTunnelGroup." are interfaces, in addition to gmplsTunnelGroup."
GROUP gmplsTunnelOptionalGroup GROUP gmplsTunnelOptionalGroup
DESCRIPTION DESCRIPTION
"Objects in this group are optional." "Objects in this group are optional."
GROUP gmplsTeNotificationGroup GROUP gmplsTeNotificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those implementations which can "This group is mandatory for those implementations which can
implement the notifications contained in this group." implement the notifications contained in this group."
-- GMPLS Tunnel scalars.
-- All scalars have max access read-only -- All scalars have max access read-only
-- gmplsTunnelTable
OBJECT gmplsTunnelAttributes OBJECT gmplsTunnelAttributes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelLSPEncoding OBJECT gmplsTunnelLSPEncoding
SYNTAX IANAGmplsLSPEncoding SYNTAX IANAGmplsLSPEncodingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelSwitchingType OBJECT gmplsTunnelSwitchingType
SYNTAX IANAGmplsSwitchingType SYNTAX IANAGmplsSwitchingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelLinkProtection OBJECT gmplsTunnelLinkProtection
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 38, line 14 skipping to change at page 43, line 4
OBJECT gmplsTunnelSwitchingType OBJECT gmplsTunnelSwitchingType
SYNTAX IANAGmplsSwitchingType SYNTAX IANAGmplsSwitchingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelLinkProtection OBJECT gmplsTunnelLinkProtection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelGPid OBJECT gmplsTunnelGPid
SYNTAX IANAGmplsGPid SYNTAX IANAGmplsGeneralizedPid
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelSecondary OBJECT gmplsTunnelSecondary
SYNTAX TruthValue SYNTAX TruthValue
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 38, line 47 skipping to change at page 43, line 36
SYNTAX INTEGER { SYNTAX INTEGER {
dynamicFull(1), -- CSPF fully computed dynamicFull(1), -- CSPF fully computed
explicit(2), -- fully specified path explicit(2), -- fully specified path
dynamicPartial(3) -- CSPF partially computed dynamicPartial(3) -- CSPF partially computed
} }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only explicit (2) is required." "Only explicit (2) is required."
OBJECT gmplsTunnelUpNotRecip OBJECT gmplsTunnelUpstreamNotifyRecipientType
SYNTAX IpAddress SYNTAX InetAddressType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelDownNotRecip
SYNTAX IpAddress OBJECT gmplsTunnelUpstreamNotifyRecipient
SYNTAX InetAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelSendResvNotifyRecipientType
SYNTAX InetAddressType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelSendResvNotifyRecipient
SYNTAX InetAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelDownstreamNotifyRecipientType
SYNTAX InetAddressType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelDownstreamNotifyRecipient
SYNTAX InetAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelSendPathNotifyRecipientType
SYNTAX InetAddressType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsTunnelSendPathNotifyRecipient
SYNTAX InetAddress
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelAdminStatusFlags OBJECT gmplsTunnelAdminStatusFlags
SYNTAX IANAGmplsAdminStatusFlags SYNTAX IANAGmplsAdminStatusInformation
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelExtraParamsPtr OBJECT gmplsTunnelExtraParamsPtr
SYNTAX RowPointer SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- gmplsTunnelHopTable
-- gmplsTunnelHopLabelStatuses has max access read-only -- gmplsTunnelHopLabelStatuses has max access read-only
OBJECT gmplsTunnelHopExpLabel OBJECT gmplsTunnelHopExplicitForwardLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelHopExplicitForwardLabelPtr
OBJECT gmplsTunnelHopExpLabelPtr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelHopExpRvrsLabel OBJECT gmplsTunnelHopExplicitReverseLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelHopExpRvrsLabelPtr OBJECT gmplsTunnelHopExplicitReverseLabelPtr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- gmplsTunnelARHopTable -- gmplsTunnelARHopTable
-- all objects have max access read-only -- all objects have max access read-only
-- glmpsTunnelCHopTable -- glmpsTunnelCHopTable
-- all objects have max access read-only -- all objects have max access read-only
skipping to change at page 40, line 4 skipping to change at page 45, line 27
"Write access is not required." "Write access is not required."
-- gmplsTunnelARHopTable -- gmplsTunnelARHopTable
-- all objects have max access read-only -- all objects have max access read-only
-- glmpsTunnelCHopTable -- glmpsTunnelCHopTable
-- all objects have max access read-only -- all objects have max access read-only
-- gmplsTunnelReversePerfTable -- gmplsTunnelReversePerfTable
-- all objects have max access read-only -- all objects have max access read-only
-- gmplsTunnelErrorTable -- gmplsTunnelErrorTable
-- all objects have max access read-only -- all objects have max access read-only
::= { gmplsTeCompliances 2 } ::= { gmplsTeCompliances 2 }
-- Units of conformance.
gmplsTunnelGroup OBJECT-GROUP gmplsTunnelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelDirection, gmplsTunnelDirection,
gmplsTunnelReversePerfPackets, gmplsTunnelReversePerfPackets,
gmplsTunnelReversePerfHCPackets, gmplsTunnelReversePerfHCPackets,
gmplsTunnelReversePerfErrors, gmplsTunnelReversePerfErrors,
gmplsTunnelReversePerfBytes, gmplsTunnelReversePerfBytes,
gmplsTunnelReversePerfHCBytes, gmplsTunnelReversePerfHCBytes,
gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorLastTime, gmplsTunnelErrorLastTime,
skipping to change at page 41, line 4 skipping to change at page 46, line 14
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to implement "Necessary, but not sufficient, set of objects to implement
tunnels. In addition, depending on the type of the tunnels tunnels. In addition, depending on the type of the tunnels
supported (for example, manually configured or signaled, supported (for example, manually configured or signaled,
persistent or non-persistent, etc.), the following other persistent or non-persistent, etc.), the following other
groups defined below are mandatory: groups defined below are mandatory:
gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup
and/or gmplsTunnelIsIntfcGroup." and/or gmplsTunnelIsIntfcGroup."
::= { gmplsTeGroups 1 } ::= { gmplsTeGroups 1 }
gmplsTunnelSignaledGroup OBJECT-GROUP gmplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelAttributes, gmplsTunnelAttributes,
gmplsTunnelLSPEncoding, gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType, gmplsTunnelSwitchingType,
gmplsTunnelLinkProtection, gmplsTunnelLinkProtection,
gmplsTunnelGPid, gmplsTunnelGPid,
gmplsTunnelSecondary, gmplsTunnelSecondary,
gmplsTunnelPathComp, gmplsTunnelPathComp,
gmplsTunnelUpNotRecip, gmplsTunnelUpstreamNotifyRecipientType,
gmplsTunnelDownNotRecip, gmplsTunnelUpstreamNotifyRecipient,
gmplsTunnelSendResvNotifyRecipientType,
gmplsTunnelSendResvNotifyRecipient,
gmplsTunnelDownstreamNotifyRecipientType,
gmplsTunnelDownstreamNotifyRecipient,
gmplsTunnelSendPathNotifyRecipientType,
gmplsTunnelSendPathNotifyRecipient,
gmplsTunnelAdminStatusFlags, gmplsTunnelAdminStatusFlags,
gmplsTunnelHopLabelStatuses, gmplsTunnelHopLabelStatuses,
gmplsTunnelHopExpLabel, gmplsTunnelHopExplicitForwardLabel,
gmplsTunnelHopExpLabelPtr, gmplsTunnelHopExplicitForwardLabelPtr,
gmplsTunnelHopExpRvrsLabel, gmplsTunnelHopExplicitReverseLabel,
gmplsTunnelHopExpRvrsLabelPtr gmplsTunnelHopExplicitReverseLabelPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement signaled tunnels." "Objects needed to implement signaled tunnels."
::= { gmplsTeGroups 3 } ::= { gmplsTeGroups 2 }
gmplsTunnelScalarGroup OBJECT-GROUP gmplsTunnelScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelsConfigured, gmplsTunnelsConfigured,
gmplsTunnelsActive gmplsTunnelsActive
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Scalar objects needed to implement MPLS tunnels." "Scalar objects needed to implement MPLS tunnels."
::= { gmplsTeGroups 4 } ::= { gmplsTeGroups 3 }
gmplsTunnelIsIntfcGroup OBJECT-GROUP gmplsTunnelIsIntfcGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelUnnumIf gmplsTunnelUnnumIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement tunnels that are interfaces." "Objects needed to implement tunnels that are interfaces."
::= { gmplsTeGroups 5 } ::= { gmplsTeGroups 4 }
gmplsTunnelIsNotIntfcGroup OBJECT-GROUP gmplsTunnelIsNotIntfcGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelUnnumIf gmplsTunnelUnnumIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement tunnels that are not interfaces." "Objects needed to implement tunnels that are not interfaces."
::= { gmplsTeGroups 6 } ::= { gmplsTeGroups 5 }
gmplsTunnelOptionalGroup OBJECT-GROUP gmplsTunnelOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelExtraParamsPtr, gmplsTunnelExtraParamsPtr,
gmplsTunnelARHopLabelStatuses, gmplsTunnelARHopLabelStatuses,
gmplsTunnelARHopExpLabel, gmplsTunnelARHopExplicitForwardLabel,
gmplsTunnelARHopExpLabelPtr, gmplsTunnelARHopExplicitForwardLabelPtr,
gmplsTunnelARHopExpRvrsLabel, gmplsTunnelARHopExplicitReverseLabel,
gmplsTunnelARHopExpRvrsLabelPtr, gmplsTunnelARHopExplicitReverseLabelPtr,
gmplsTunnelARHopProtection, gmplsTunnelARHopProtection,
gmplsTunnelCHopLabelStatuses, gmplsTunnelCHopLabelStatuses,
gmplsTunnelCHopExpLabel, gmplsTunnelCHopExplicitForwardLabel,
gmplsTunnelCHopExpLabelPtr, gmplsTunnelCHopExplicitForwardLabelPtr,
gmplsTunnelCHopExpRvrsLabel, gmplsTunnelCHopExplicitReverseLabel,
gmplsTunnelCHopExpRvrsLabelPtr gmplsTunnelCHopExplicitReverseLabelPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The objects in this group are optional." "The objects in this group are optional."
::= { gmplsTeGroups 7 } ::= { gmplsTeGroups 6 }
gmplsTeNotificationGroup NOTIFICATION-GROUP gmplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
gmplsTunnelDown gmplsTunnelDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. None is "Set of notifications implemented in this module. None is
mandatory." mandatory."
::= { gmplsTeGroups 8 } ::= { gmplsTeGroups 7 }
END END
9. Security Considerations 9. Security Considerations
It is clear that the MIB modules described in this document in It is clear that the MIB modules described in this document in
association with the MPLS-TE-STD-MIB are potentially useful for association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful
monitoring of MPLS and GMPLS tunnels. These MIB modules can also be for monitoring of MPLS and GMPLS tunnels. These MIB modules can also
used for configuration of certain objects, and anything that can be be used for configuration of certain objects, and anything that can
configured can be incorrectly configured, with potentially disastrous be configured can be incorrectly configured, with potentially
results. disastrous results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
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 environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain
objects to provision GMPLS tunnels interfaces at their ingress objects to provision GMPLS tunnels interfaces at their ingress
LSRs. Unauthorized write access to objects in these tables, could LSRs. Unauthorized write access to objects in these tables, could
result in disruption of traffic on the network. This is especially result in disruption of traffic on the network. This is especially
true if a tunnel has already been established. The use of stronger true if a tunnel has already been established.
mechanisms such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used with any
SNMPv3 agent which implements these MIB modules.
Some of the readable objects in these MIB modules "i.e., objects with Some of the readable objects in these MIB modules (i.e., objects with
a MAX-ACCESS other than not-accessible" may be considered sensitive a MAX-ACCESS other than not-accessible) may be considered sensitive
or vulnerable in some network environments. It is thus important to or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable,
gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, gmplsTunnelCHopTable, gmplsTunnelReversePerfTable,
gmplsTunnelErrorTable collectively show the tunnel network gmplsTunnelErrorTable collectively show the tunnel network
topology and status. If an Administrator does not want to reveal topology and status. If an Administrator does not want to reveal
this information, then these tables should be considered this information, then these tables should be considered
sensitive/vulnerable. sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure "for example by using IPSec", even if the network itself is secure (for example by using IPSec), even
then, there is no control as to who on the secure network is allowed then, 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 to access and GET/SET (read/change/create/delete) the objects in
these MIB modules. It is RECOMMENDED that implementers consider the these MIB modules.
security features as provided by the SNMPv3 framework "see [RFC3410],
section 8", including full support for the SNMPv3 cryptographic It is RECOMMENDED that implementers consider the security features as
mechanisms "for authentication and privacy". provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET (change/create/delete) them.
10. Acknowledgments 10. Acknowledgments
This draft is the work of the five authors listed in the Authors' This document is a product of the CCAMP Working Group.
Addresses section.
This document extends [RFC3812]. The authors would like to express This document extends [RFC3812]. The authors would like to express
their gratitude to all those who worked on that earlier MIB document. their gratitude to all those who worked on that earlier MIB document.
Thanks also to Tony Zinicola and Jeremy Crossen for their valuable Thanks also to Tony Zinicola and Jeremy Crossen for their valuable
contributions during an early implementation, and to Baktha contributions during an early implementation, and to Baktha
Muralidharan and Tom Petch for their review comments. Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review
comments.
Special thanks to Joan Cucchiara and Len Nieman for their help with Special thanks to Joan Cucchiara and Len Nieman for their help with
compilation issues. compilation issues.
Joan Cucchiara provided a helpful and very thorough MIB Doctor
review.
11. IANA Considerations 11. IANA Considerations
As requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB], GMPLS related -- (Note to RFC-Editor:)
standards track MIB modules should be rooted under the mplsStdMIB -- We request that you assign contiguous RFC numbers to the three GMPLS
subtree. There is one GMPLS MIB Module contained in this document, -- MIB documents.
and the following "IANA Considerations" subsection requests IANA for -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to
a new assignment under the mplsStdMIB subtree. New assignments in -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to
the mplsStdMIB subtree can only be made via a Standards Action as -- draft-ietf-ccamp-gmpls-te-mib.
specified in [RFC2434]. -- (Please remove this note prior to publication.)
IANA is requested to root MIB objects in the MIB module contained in
this document under the mplsStdMIB subtree.
In the future, GMPLS related standards track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in
[RFC2434].
11.1. IANA Considerations for GMPLS-TE-STD-MIB 11.1. IANA Considerations for GMPLS-TE-STD-MIB
IANA is requested to assign an OID to the GMPLS-TE-STD-MIB module The IANA is requested to assign { mplsStdMIB XXX } to the
specified in this document as { mplsStdMIB XXX }. GMPLS-TE-STD-MIB module specified in this document, and to record
the assignment in the SMI Numbers registry.
-- RFC Editor. Please replace XXX above with assigned OID and remove
-- this note
11.2. Dependence on IANA MIB Modules 11.2. Dependence on IANA MIB Modules
Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, Three MIB objects in this MIB module (gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual
conventions imported from the IANA-GMPLS-MIB. The purpose of conventions imported from the IANA-GMPLS-TC-MIB. The purpose of
defining these textual conventions in a separate MIB module is to defining these textual conventions in a separate MIB module is to
allow additional values to be defined without having to issue a new allow additional values to be defined without having to issue a new
version of this document. The Internet Assigned Numbers Authority version of this document. The Internet Assigned Numbers Authority
(IANA) is responsible for the assignment of all Internet numbers; it (IANA) is responsible for the assignment of all Internet numbers; it
will administer the values associated with these textual conventions. will administer the values associated with these textual conventions.
The rules for additions or changes to the IANA-GMPLS-MIB are outlined The rules for additions or changes to the IANA-GMPLS-TC-MIB are
in the DESCRIPTION clause associated with its MODULE-IDENTITY outlined in the DESCRIPTION clause associated with its
statement. MODULE-IDENTITY statement.
The current versions of the IANA-GMPLS-MIB can be accessed from the The current versions of the IANA-GMPLS-TC-MIB can be accessed from
IANA home page at: "http://www.iana.org/". the IANA home page at: "http://www.iana.org/".
11.2.1. IANA-GMPLS-MIB Definition 11.2.1. IANA-GMPLS-TC-MIB Definition
This is a temporary section intended to supply the base definition of This is a temporary section intended to supply the base definition of
an IANA MIB module. The normal procedure is that this MIB module is an IANA MIB module. The normal procedure is that this MIB module is
moved into the direct control of IANA, at which time this section moved into the direct control of IANA, at which time this section
should be deleted from this document. should be deleted from this document.
IANA is requested to assign an OID to the IANA-GMPLS-MIB module IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module
specified in this document as { transmission YYY }. specified in this document as { transmission YYY }.
IANA-GMPLS-MIB DEFINITIONS ::= BEGIN -- RFC Editor.
-- Please replace YYY above with assigned OID and remove this note.
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579
ianaGmpls MODULE-IDENTITY ianaGmpls MODULE-IDENTITY
LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: USC/Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292 4676 Admiralty Way, Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 822 1511
E-Mail: iana@isi.edu" E-Mail: iana@isi.edu"
DESCRIPTION DESCRIPTION
skipping to change at page 45, line 34 skipping to change at page 51, line 14
ianaGmpls MODULE-IDENTITY ianaGmpls MODULE-IDENTITY
LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: USC/Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292 4676 Admiralty Way, Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 822 1511
E-Mail: iana@isi.edu" E-Mail: iana@isi.edu"
DESCRIPTION DESCRIPTION
"The MIB module which defines the GMPLS textual "Copyright (C) The Internet Society (2005). The initial version
conventions for use as enumerations within GMPLS MIB of this MIB module was published in RFC XXX. For full legal
modules, thus protecting those MIB modules from changes notices see the RFC itself. Supplementary information
to the enumerations." may be available on:
-- Revision history. http://www.ietf.org/copyrights/ianamib.html"
-- RFC Editor. Please replace XXX above with the correct RFC number
-- Your actions may vary depending on how IANA chooses to handle
-- this IANA MIB.
-- Please remove this note.
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC Editor: Please see the IANA Considerations Section. "Initial version issued as part of RFC XXX."
-- RFC-editor please fill in XXXX
"Initial version issued as part of RFC XXXX."
::= { transmission YYY } ::= { transmission YYY }
IANAGmplsLSPEncoding ::= TEXTUAL-CONVENTION -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- Please replace XXX with the real RFC number.
-- Please remove this note.
IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
gmplsTunnelLSPEncoding object in the definition of gmplsTunnelLSPEncoding object in the definition of
GMPLS-TE-MIB's gmplsTunnelTable. GMPLS-TE-STD-MIB's gmplsTunnelTable.
gmplsTunnelLSPEncoding is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol.
This textual convention is strongly tied to the LSP
Encoding Types sub-registry of the GMPLS Signaling
Parameters registry managed by IANA. Values should be
assigned by IANA in step with the LSP Encoding Types
sub-registry and using the same registry management rules.
However, the actual values used in this textual convention
are solely within the purview of IANA and do not
necessarily match the values in the values in the LSP
Encoding Types sub-registry.
The definition of this textual convention with the The definition of this textual convention with the
addition of newly assigned values is published addition of newly assigned values is published
periodically by the IANA, in either the Assigned periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu). email (iana@isi.edu)."
gmplsTunnelLSPEncoding is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol. The relationship between the
assignment of gmplsTunnelLSPEncoding values and of the
values used to represent LSP encoding types within the
GMPLS signaling protocols is solely the purview of IANA
and is subject to change without notice."
REFERENCE REFERENCE
"1. Berger, L., et al., Generalized Multi-Protocol "1. Generalized Multi-Protocol Label Switching (GMPLS)
Label Switching (GMPLS) Signaling Functional Signaling Functional Description, RFC 3471, section
Description, RFC 3471, January 2003. 3.1.1.
2. D. Papadimitriou (Editor), Generalized MPLS 2. Generalized MPLS Signalling Extensions for G.709 Optical
Signalling Extensions for G.709 Optical Transport Transport Networks Control, draft-ietf-ccamp-gmpls-g709,
Networks Control, draft-ietf-ccamp-gmpls-g709, work in progress, section 3.1.1."
work in progress." -- RFC Editor. Please update this reference to the RFC before
-- publication and remove this note
SYNTAX INTEGER { SYNTAX INTEGER {
tunnelLspNotGmpls (0), -- GMPLS is not in use tunnelLspNotGmpls (0), -- GMPLS is not in use
-- This is not part of the LSP
-- Encoding Type registry, but
-- is needed for the correct
-- functioning of the
-- GMPLS-TE-STD-MIB
tunnelLspPacket (1), -- Packet tunnelLspPacket (1), -- Packet
tunnelLspEthernet (2), -- Ethernet tunnelLspEthernet (2), -- Ethernet
tunnelLspAnsiEtsiPdh (3), -- PDH tunnelLspAnsiEtsiPdh (3), -- PDH
-- the value 4 is deprecated -- the value 4 is deprecated
tunnelLspSdhSonet (5), -- SDH or SONET tunnelLspSdhSonet (5), -- SDH or SONET
-- the value 6 is deprecated -- the value 6 is deprecated
tunnelLspDigitalWrapper (7), -- Digital Wrapper tunnelLspDigitalWrapper (7), -- Digital Wrapper
tunnelLspLambda (8), -- Lambda tunnelLspLambda (8), -- Lambda
tunnelLspFiber (9), -- Fiber tunnelLspFiber (9), -- Fiber
-- the value 10 is deprecated -- the value 10 is deprecated
tunnelLspFiberChannel (11), -- Fiber Channel tunnelLspFiberChannel (11), -- Fiber Channel
tunnelDigitalPath (12), -- Digital Path tunnelDigitalPath (12), -- Digital Path
tunnelOpticalChannel (13) -- Optical Channel tunnelOpticalChannel (13) -- Optical Channel
} }
IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
gmplsTunnelSwitchingType object in the definition of gmplsTunnelSwitchingType object in the definition of
GMPLS-TE-MIB's gmplsTunnelTable. GMPLS-TE-STD-MIB's gmplsTunnelTable.
gmplsTunnelSwitchingType is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol.
This textual convention is strongly tied to the Switching
Types sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by IANA
in step with the Switching Types sub-registry and using the
same registry management rules. However, the actual values
used in this textual convention are solely within the
purview of IANA and do not necessarily match the values in
the values in the Switching Types sub-registry.
The definition of this textual convention with the The definition of this textual convention with the
addition of newly assigned values is published addition of newly assigned values is published
periodically by the IANA, in either the Assigned periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu). email (iana@isi.edu)."
gmplsTunnelSwitchingType is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol. The relationship between the
assignment of gmplsTunnelSwitchingType values and of the
values used to represent LSP switching types within the
GMPLS signaling protocols is solely the purview of IANA
and is subject to change without notice."
REFERENCE REFERENCE
"1. Kompella, K., Rekhter, Y. (Editors), Routing Extensions "1. Routing Extensions in Support of Generalized
in Support of Generalized Multi-Protocol Label Switching Multi-Protocol Label Switching, RFC 4202, section 2.4.
draft-ietf-ccamp-gmpls-routing, work in progress. 2. Generalized Multi-Protocol Label Switching (GMPLS)
2. Berger, L., et al., Generalized Multi-Protocol Signaling Functional Description, RFC 3471, section
Label Switching (GMPLS) Signaling Functional 3.1.1."
Description, RFC 3471, January 2003."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown (0), -- none of the following, or not known unknown (0), -- none of the following, or not known
psc1 (1), -- Packet-Switch-Capable 1 psc1 (1), -- Packet-Switch-Capable 1
psc2 (2), -- Packet-Switch-Capable 2 psc2 (2), -- Packet-Switch-Capable 2
psc3 (3), -- Packet-Switch-Capable 3 psc3 (3), -- Packet-Switch-Capable 3
psc4 (4), -- Packet-Switch-Capable 4 psc4 (4), -- Packet-Switch-Capable 4
l2sc (51), -- Layer-2-Switch-Capable l2sc (51), -- Layer-2-Switch-Capable
tdm (100), -- Time-Division-Multiplex tdm (100), -- Time-Division-Multiplex
lsc (150), -- Lambda-Switch-Capable lsc (150), -- Lambda-Switch-Capable
fsc (200) -- Fiber-Switch-Capable fsc (200) -- Fiber-Switch-Capable
} }
IANAGmplsGPid ::= TEXTUAL-CONVENTION IANAGmplsGeneralizedPid ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
gmplsTunnelGPid object in the definition of gmplsTunnelGPid object in the definition of
GMPLS-TE-MIB's gmplsTunnelTable. GMPLS-TE-STD-MIB's gmplsTunnelTable.
gmplsTunnelGPid is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol.
This textual convention is strongly tied to the Generalized
PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by IANA
in step with the Generalized PIDs (G-PID) sub-registry and
using the same registry management rules. However, the
actual values used in this textual convention are solely
within the purview of IANA and do not necessarily match the
values in the values in the Generalized PIDs (G-PID)
sub-registry.
The definition of this textual convention with the The definition of this textual convention with the
addition of newly assigned values is published addition of newly assigned values is published
periodically by the IANA, in either the Assigned periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu). email (iana@isi.edu)."
gmplsTunnelGPid is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol. The relationship
between the assignment of gmplsTunnelGPid values and of
the values used to represent G-PIDs within the GMPLS
signaling protocols is solely the purview of IANA and is
subject to change without notice."
REFERENCE REFERENCE
"1. Berger, L., et al., Generalized Multi-Protocol "1. Generalized Multi-Protocol Label Switching (GMPLS)
Label Switching (GMPLS) Signaling Functional Signaling Functional Description, RFC 3471, section
Description, RFC 3471, January 2003. 3.1.1.
2. D. Papadimitriou (Editor), Generalized MPLS 2. Generalized MPLS Signalling Extensions for G.709 Optical
Signalling Extensions for G.709 Optical Transport Transport Networks Control, draft-ietf-ccamp-gmpls-g709,
Networks Control, draft-ietf-ccamp-gmpls-g709, work in progress, section 3.1.3."
work in progress." -- RFC Editor. Please update this reference to the RFC before
-- publication and remove this note
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), -- unknown or none of the following unknown(0), -- unknown or none of the following
asynchE4(5), asynchE4(5),
asynchDS3T3(6), asynchDS3T3(6),
asynchE3(7), asynchE3(7),
bitsynchE3(8), bitsynchE3(8),
bytesynchE3(9), bytesynchE3(9),
asynchDS2T2(10), asynchDS2T2(10),
bitsynchDS2T2(11), bitsynchDS2T2(11),
asynchE1(13), asynchE1(13),
skipping to change at page 50, line 4 skipping to change at page 56, line 4
g709CBRb (50), g709CBRb (50),
g709BSOT (51), g709BSOT (51),
g709BSNT (52), g709BSNT (52),
gfpIPorPPP (53), gfpIPorPPP (53),
gfpEthernetMAC (54), gfpEthernetMAC (54),
gfpEthernetPHY (55), gfpEthernetPHY (55),
g709ESCON (56), g709ESCON (56),
g709FICON (57), g709FICON (57),
g709FiberChannel (58) g709FiberChannel (58)
} }
IANAGmplsAdminStatusFlags ::= TEXTUAL-CONVENTION IANAGmplsAdminStatusInformation ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
gmplsTunnelAdminStatusFlags object in the definition of gmplsTunnelAdminStatusFlags object in the definition of
GMPLS-TE-MIB's gmplsTunnelTable. GMPLS-TE-STD-MIB's gmplsTunnelTable.
gmplsTunnelAdminStatusFlags determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471. Setting this object to a non-zero
value will result in the inclusion of the Admin Status
object or TLV on signaling messages.
This textual convention is strongly tied to the Admin
Status Flags sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by IANA
in step with the Admin Status Flags sub-registry and using
the same registry management rules. However, the actual
values used in this textual convention are solely within
the purview of IANA and do not necessarily match the values
in the values in the Admin Status Flags sub-registry.
-- RFC Editor / IANA note
-- At the time of writing, the referenced Admin Status Flags
-- sub-registry has not been created.
-- It is not requested in RFC 3471 (the base reference for this protocol
-- element). But it is requested in two I-Ds that are ahead of this MIB
-- module in the IETF process
-- draft-ietf-ccamp-gmpls-recovery-e2e-signaling
-- draft-ietf-ccamp-gmpls-alarm-spec
-- Note, however, that at this stage no request is made to IANA for the
-- definition of values in the textual convention to match any of the
-- Admin Status bits except those defined in RFC 3471. IANA is free to
-- define additional values but these will not be used by this MIB
-- module (although future MIB modules will doubtless use them).
--
-- RFC Editor. Please update the previous paragraph to use the correct
-- name for the new sub-registry as defined by IANA, and delete this
-- note.
The definition of this textual convention with the The definition of this textual convention with the
addition of newly assigned values is published addition of newly assigned values is published
periodically by the IANA, in either the Assigned periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu). email (iana@isi.edu)."
gmplsTunnelAdminStatusFlags determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471. Setting this object to a non-zero
value will result in the inclusion of the Admin Status
object or TLV on signaling messages.
The relationship between the assignment of
gmplsTunnelAdminStatusFlags values and of the bit flags
in the Admin Status object or TLV within the GMPLS
signaling protocols is solely the purview of IANA and is
subject to change without notice."
REFERENCE REFERENCE
"Berger, L., et al., Generalized Multi-Protocol Label "1. Generalized Multi-Protocol Label Switching (GMPLS)
Switching (GMPLS) Signaling Functional Description, Signaling Functional Description, RFC 3471, section 8."
RFC 3471, January 2003."
SYNTAX BITS { SYNTAX BITS {
delInProgress (0), reflect (31), -- Reflect bit (RFC 3471)
adminDown (1), reserved30 (30), -- reserved
testing (2), reserved29 (29), -- reserved
reflect (31) reserved28 (28), -- reserved
reserved27 (27), -- reserved
reserved26 (26), -- reserved
reserved25 (25), -- reserved
reserved24 (24), -- reserved
reserved23 (23), -- reserved
reserved22 (22), -- reserved
reserved21 (21), -- reserved
reserved20 (20), -- reserved
reserved19 (19), -- reserved
reserved18 (18), -- reserved
reserved17 (17), -- reserved
reserved16 (16), -- reserved
reserved15 (15), -- reserved
reserved14 (14), -- reserved
reserved13 (13), -- reserved
reserved12 (12), -- reserved
reserved11 (11), -- reserved
reserved10 (10), -- reserved
reserved9 (9), -- reserved
reserved8 (8), -- reserved
reserved7 (7), -- reserved
reserved6 (6), -- reserved
reserved5 (5), -- reserved
reserved4 (4), -- reserved
reserved3 (3), -- reserved
testing (2), -- Testing bit (RFC 3473)
administrativelyDown (1), -- Admin down (RFC 3473)
deleteInProgress (0) -- Delete bit (RFC 3473)
} }
END END
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser, "Structure
of Management Information Version 2 (SMIv2)", STD
58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Case, J., Rose, M., and S. Waldbusser, "Textual Jamin, "Resource ReSerVation Protocol (RSVP) -- Version
Conventions for SMIv2", STD 58, RFC 2579, April 1 Functional Specification", RFC 2205, September 1997.
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Case, J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Structure of
Statements for SMIv2", STD 58, RFC 2580, April 1999. Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
"Multiprotocol Label Switching Architecture", RFC J., Rose, M., and S. Waldbusser, "Textual Conventions
3031, January 2001. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Srinivasan, V., and G. Swallow, "RSVP-TE: J., Rose, M., and S. Waldbusser, "Conformance Statements
Extensions to RSVP for LSP Tunnels", RFC 3209, for SMIv2", STD 58, RFC 2580, April 1999.
December 2001.
[RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
Ashwood-Smith, P., Hellstrand, F., Sundell, K., "Multiprotocol Label Switching Architecture", RFC 3031,
Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, January 2001.
T., Feldman, N., Fredette, A., Girish, M., Gray,
E., Halpern, J., Heinanen, J., Kilty, T., Malis,
A., and P. Vaananen, "Constraint-Based LSP Setup
using LDP", RFC 3212, December 2001.
[RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
Label Switching (GMPLS) Signaling Functional V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Description", RFC 3471, January 2003. Tunnels", RFC 3209, December 2001.
[RFC3472] Ashwood-Smith, P., Berger, L. (Editors), [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
"Generalized MPLS Signaling - CR-LDP Extensions", Architecture for Describing Simple Network Management
RFC 3472, January 2003. Protocol (SNMP) Management Frameworks", STD 62, RFC
3411, December 2002.
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
RSVP-TE Extensions", RFC 3473, January 2003. (GMPLS) Signaling Functional Description", RFC 3471,
January 2003.
[RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
Links in RSVP-TE", RFC 3477, January 2003. (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January
2003.
[RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A., [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered
"Signalling Unnumbered Links in CR-LDP", RFC 3480, Links in Resource ReSerVation Protocol - Traffic
February 2003. Engineering (RSVP-TE)", RFC 3477, January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching Conventions and for Multiprotocol Label Switching (MPLS)
(MPLS) Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)", Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004. RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label "Multiprotocol Label Switching (MPLS) Label Switching
Switching (LSR) Router Management Information Base (LSR) Router Management Information Base (MIB)", RFC
(MIB)", RFC 3813, June 2004. 3813, June 2004.
[RFC3945] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", RFC 3945,
October 2004.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Schoenwaelder, J., and Braunschweig, TU, "Textual Switching (GMPLS) Architecture", RFC 3945, October 2004.
Conventions for Internet Network Addresses",
RFC 4001, February 2005.
[GMPLSLSRMIB] Nadeau, T., Farrel, A., (Editors) "Generalized [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Multiprotocol Label Switching (GMPLS) Label Schoenwaelder, "Textual Conventions for Internet Network
Switching Router (LSR) Management Information Addresses", RFC 4001, February 2005.
Base", draft-ietf-ccamp-gmpls-lsr-mib, work in
progress.
[GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in
of Generalized MPLS", Support of Generalized Multi-Protocol Label Switching",
draft-ietf-ccamp-ospf-gmpls-extensions, work in RFC 4202, October 2005.
progress.
[GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol
Textual Conventions for Multiprotocol Label Label Switching (GMPLS) Label Switching Router (LSR)
Switching (MPLS) Management", Management Information Base",
draft-ietf-ccamp-gmpls-te-mib, work in progress. draft-ietf-ccamp-gmpls-lsr-mib, work in progress.
12.2. Informational References [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual
Conventions for Multiprotocol Label Switching (MPLS)
Management", draft-ietf-ccamp-gmpls-tc-mib, work in
progress.
[RFC2026] S. Bradner, "The Internet Standards Process -- [GMPLS-G709] Papadimitriou, D., Ed., "Generalized MPLS Signalling
Revision 3", RFC 2026, October 1996. Extensions for G.709 Optical Transport Networks
Control", draft-ietf-ccamp-gmpls-g709, work in progress.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for 12.2. Informative References
Writing an IANA Considerations Section in RFCs",
BCP 26, RFC 2434, October 1998.
[RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Applications", RFC 3413, December 2002. MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized
Architecture for Describing Simple Network Multi-Protocol Label Switching (MPLS) Signaling
Management Protocol (SNMP) Management Frameworks", - Constraint-based Routed Label Distribution Protocol
RFC 3411, December 2002. (CR-LDP) Extensions", RFC 3472, January 2003.
[GMPLS-G709] D. Papadimitriou (Editor), "Generalized MPLS
Signalling Extensions for G.709 Optical Transport
Networks Control", draft-ietf-ccamp-gmpls-g709,
work in progress.
13. Authors' Addresses 13. Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 1414 Massachusetts Ave.
Chelmsford, MA 01824 Boxborough, MA 01719
Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
731 Lexington Ave. 731 Lexington Ave.
New York, NY 10022 New York, NY 10022
Phone: +1-212-617-3682 Phone: +1-212-617-3682
Email: cheenu@bloomberg.net Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
 End of changes. 277 change blocks. 
621 lines changed or deleted 950 lines changed or added

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