draft-ietf-mpls-te-mib-14.txt   rfc3812.txt 
Network Working Group Cheenu Srinivasan Network Working Group C. Srinivasan
Internet Draft Bloomberg L.P. Request for Comments: 3812 Bloomberg L.P.
Expires: May 2004 Category: Standards Track A. Viswanathan
Arun Viswanathan Force10 Networks, Inc.
Force10 Networks, Inc. T. Nadeau
Cisco Systems, Inc.
Thomas D. Nadeau June 2004
Cisco Systems, Inc.
November 2003
Multiprotocol Label Switching (MPLS) Traffic Engineering
Management Information Base
draft-ietf-mpls-te-mib-14.txt Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document specifies an Internet standards track protocol for the
conformance with all provisions of Section 10 of RFC 2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Official Protocol Standards" (STD 1) for the standardization state
Engineering Task Force (IETF), its areas, and its working and status of this protocol. Distribution of this memo is unlimited.
groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by
other documents at any time. It is inappropriate to use
Internet-Drafts as reference material or to cite them other
than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be Copyright (C) The Internet Society (2004).
accessed at http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information This memo defines a portion of the Management Information Base (MIB)
Base (MIB) for use with network management protocols in for use with network management protocols in the Internet community.
the Internet community. In particular, it describes In particular, it describes managed objects for Multiprotocol Label
managed objects for Multiprotocol Label Switching (MPLS) Switching (MPLS) based traffic engineering (TE).
based traffic engineering.
Table of Contents Table of Contents
1. Introduction ........................................... 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology ............................................ 3 2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. The Internet-Standard Management Framework ............. 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Feature List ........................................... 3 4. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Outline ................................................ 4 5. Outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Summary of Traffic Engineering MIB module ............ 4 5.1. Summary of Traffic Engineering MIB Module. . . . . . . . 4
6. Brief Description of MIB Objects ....................... 5 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . 4
6.1. mplsTunnelTable ...................................... 5 6.1. mplsTunnelTable. . . . . . . . . . . . . . . . . . . . . 4
6.2. mplsTunnelResourceTable .............................. 5 6.2. mplsTunnelResourceTable. . . . . . . . . . . . . . . . . 5
6.3. mplsTunnelHopTable ................................... 5 6.3. mplsTunnelHopTable . . . . . . . . . . . . . . . . . . . 5
6.4. mplsTunnelARHopTable ................................. 6 6.4. mplsTunnelARHopTable . . . . . . . . . . . . . . . . . . 5
6.5. mplsTunnelCHoptable .................................. 6 6.5. mplsTunnelCHoptable. . . . . . . . . . . . . . . . . . . 5
6.6. mplsTunnelPerfTable .................................. 6 6.6. mplsTunnelPerfTable. . . . . . . . . . . . . . . . . . . 6
6.7. mplsTunnelCRLDPResTable .............................. 6 6.7. mplsTunnelCRLDPResTable. . . . . . . . . . . . . . . . . 6
7. Use of 32-bit and 64-bit Counters ...................... 7 7. Use of 32-bit and 64-bit Counters. . . . . . . . . . . . . . . 6
8. Application of the Interface Group to MPLS Tunnels ..... 7 8. Application of the Interface Group to MPLS Tunnels . . . . . . 6
8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 8.1. Support of the MPLS Tunnel Interface by ifTable. . . . . 7
9. Example of Tunnel Setup ................................ 9 9. Example of Tunnel Setup. . . . . . . . . . . . . . . . . . . . 8
10. The Use of RowPointer ................................ 11 10. The Use of RowPointer. . . . . . . . . . . . . . . . . . . . . 11
11. MPLS Traffic Engineering MIB Definitions ............. 12 11. MPLS Traffic Engineering MIB Definitions . . . . . . . . . . . 11
12. Security Considerations .............................. 62 12. Security Considerations. . . . . . . . . . . . . . . . . . . . 63
13. Acknowledgments ...................................... 63 13. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 64
14. References ........................................... 64 14. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 64
14.1. Normative References ............................... 64 14.1. IANA Considerations for MPLS-TE-STD-MIB. . . . . . . . . 65
14.2. Informative References ............................. 65 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15. Authors' Addresses ................................... 65 15.1. Normative References . . . . . . . . . . . . . . . . . . 65
16. Full Copyright Statement ............................. 66 15.2. Informative References . . . . . . . . . . . . . . . . . 66
17. Intellectual Property Notice ......................... 66 16. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 67
18. IANA Considerations ................................ 67 17. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 68
18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 67
1. Introduction 1. Introduction
This memo defines a portion of the Management Information This memo defines a portion of the Management Information Base (MIB)
Base (MIB) for use with network management protocols in the for use with network management protocols in the Internet community.
Internet community. In particular, it describes managed In particular, it describes managed objects for modeling a
objects for modeling a Multi-Protocol Label Switching Multiprotocol Label Switching (MPLS) [RFC3031] based traffic
(MPLS) [RFC3031] based traffic engineering. This MIB module engineering. This MIB module should be used in conjunction with the
should be used in conjunction with the companion document companion document [RFC3813] for MPLS based traffic engineering
[LSRMIB] for MPLS based traffic engineering configuration configuration and management.
and management.
Comments should be made directly to the MPLS mailing list The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
at mpls@uu.net. "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119,
reference [RFC2119].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 2. Terminology
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119, reference [RFC2119].
2. Terminology This document uses terminology from the MPLS architecture document
This document uses terminology from the MPLS architecture [RFC3031] and MPLS Label Switch Router MIB [RFC3813]. Some
document [RFC3031] and MPLS Label Switch Router MIB frequently used terms are described next.
[LSRMIB]. Some frequently used terms are described next.
An explicitly routed LSP (ERLSP) is referred to as an MPLS An explicitly routed LSP (ERLSP) is referred to as an MPLS tunnel.
tunnel. It consists of in-segment(s) and/or out- It consists of in-segment(s) and/or out-segment(s) at the
segment(s) at the egress/ingress LSRs, each segment being egress/ingress LSRs, each segment being associated with one MPLS
associated with one MPLS interface. These are also interface. These are also referred to as tunnel segments.
referred to as tunnel segments. Additionally, at an Additionally, at an intermediate LSR, we model a connection as
intermediate LSR, we model a connection as consisting of consisting of one or more in-segments and/or one or more out-
one or more in-segments and/or one or more out-segments. segments. The binding or interconnection between in-segments and
The binding or interconnection between in-segments and out- out-segments is performed using a cross-connect. These objects are
segments in performed using a cross-connect. These objects defined in the MPLS Label Switch Router MIB [RFC3813].
are defined in the MPLS Label Switch Router MIB [LSRMIB].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the current
current Internet-Standard Management Framework, please Internet-Standard Management Framework, please refer to section 7 of
refer to section 7 of RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information Managed objects are accessed via a virtual information store, termed
store, termed the Management Information Base or MIB. MIB the Management Information Base or MIB. MIB objects are generally
objects are generally accessed through the Simple Network accessed through the Simple Network Management Protocol (SNMP).
Management Protocol (SNMP). Objects in the MIB are defined Objects in the MIB are defined using the mechanisms defined in the
using the mechanisms defined in the Structure of Management Structure of Management Information (SMI). This memo specifies a MIB
Information (SMI). This memo specifies a MIB module that module that is compliant to the SMIv2, which is described in STD 58,
is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, [RFC2580].
RFC 2580 [RFC2580].
4. Feature List 4. Feature List
The MPLS traffic engineering MIB module is designed to The MPLS traffic engineering MIB module is designed to satisfy the
satisfy the following requirements and constraints. following requirements and constraints:
- The MIB module supports configuration of point-to-point - The MIB module supports configuration of point-to-point
unidirectional tunnels. unidirectional tunnels.
- MPLS tunnels need not be interfaces, but it is possible - MPLS tunnels need not be interfaces, but it is possible to
to configure a tunnel as an interface. configure a tunnel as an interface.
- The MIB module supports tunnel establishment via an MPLS - The MIB module supports tunnel establishment via an MPLS
signalling protocol wherein the tunnel parameters are signalling protocol wherein the tunnel parameters are specified
specified using this MIB module at the head end of the using this MIB module at the head end of the LSP, and end-to-end
LSP and end-to-end tunnel LSP establishment is tunnel LSP establishment is accomplished via signalling. The MIB
accomplished via signalling. The MIB module also module also supports manually configured tunnels, i.e., those for
supports manually configured tunnels, i.e. those for which label associations at each hop of the tunnel LSP are
which label associations at each hop of the tunnel LSP provisioned by the administrator via the LSR MIB [RFC3813].
are provisioned by the administrator via the LSR MIB
[LSRMIB].
- The MIB module supports persistent as well as non- - The MIB module supports persistent, as well as non-persistent
persistent tunnels. tunnels.
5. Outline 5. Outline
Traffic engineering support for MPLS tunnels requires the Traffic engineering support for MPLS tunnels requires the following
following configuration. configuration:
- Setting up MPLS tunnels along with appropriate - Setting up MPLS tunnels along with appropriate configuration
configuration parameters. parameters.
- Configuring tunnel loose and strict source routed hops. - Configuring tunnel for loose and strict source routed hops.
These actions may need to be accompanied by corresponding These actions may need to be accompanied by corresponding actions
actions using [LSRMIB] to establish and configure tunnel using [RFC3813] to establish and configure tunnel segments, if this
segments, if this is done manually. Also, the in-segment is done manually. Also, the in-segment and out-segment performance
and out-segment performance tables, mplsInSegmentPerfTable tables, mplsInSegmentPerfTable, and mplsOutSegmentPerfTable
and mplsOutSegmentPerfTable [LSRMIB], should be used to [RFC3813], should be used to determine performance of the tunnels and
determine performance of the tunnels and tunnel segments in tunnel segments, in addition to mplsTunnelPerfTable in this MIB
addition to mplsTunnelPerfTable in this MIB module. module.
5.1. Summary of Traffic Engineering MIB module 5.1. Summary of Traffic Engineering MIB Module
The MIB module objects for performing these actions consist The MIB module objects for performing these actions consist of the
of the following tables. following tables:
- Tunnel table (mplsTunnelTable) for setting up MPLS - Tunnel table (mplsTunnelTable) for setting up MPLS tunnels.
tunnels.
- Resource table (mplsTunnelResourceTable) for setting up - Resource table (mplsTunnelResourceTable) for setting up the tunnel
the tunnel resources. resources.
- Tunnel specified, actual, and computed hop tables - Tunnel specified, actual, and computed hop tables
(mplsTunnelHopTable, mplsTunnelARHopTable, and (mplsTunnelHopTable, mplsTunnelARHopTable, and
mplsTunnelCHopTable) for strict and loose source routed mplsTunnelCHopTable) for strict and loose source routed MPLS
MPLS tunnel hops. tunnel hops.
- Tunnel performance table (mplsTunnelPerfTable) for - Tunnel performance table (mplsTunnelPerfTable) for measuring
measuring tunnel performance. tunnel performance.
- CRLDP resource table (mplsTunnelCRLDPResTable) for - CRLDP resource table (mplsTunnelCRLDPResTable) for specifying
specifying resource objects applicable to tunnels resource objects applicable to tunnels signaled using CRLDP.
signaled using CRLDP.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
The objects described in this section support the The objects described in this section support the functionality
functionality described in documents [RSVPTE] and [CRLDP]. described in documents [RFC3209] and [RFC3212]. The tables support
The tables support both manually configured and signaled both manually configured and signaled tunnels.
tunnels.
6.1. mplsTunnelTable 6.1. mplsTunnelTable
The mplsTunnelTable allows new MPLS tunnels to be created The mplsTunnelTable allows new MPLS tunnels to be created between an
between an MPLS LSR and a remote endpoint, and existing MPLS LSR and a remote endpoint, and existing tunnels to be
tunnels to be reconfigured or removed. Note that we only reconfigured or removed. Note that we only support point-to-point
support point-to-point tunnels, although multi- tunnels, although multipoint-to-point and point-to-multipoint
point-to-point and point-to-multi-point connections are connections are supported by an LSR acting as a cross-connect. Each
supported by an LSR acting as a cross-connect. Each MPLS MPLS tunnel can thus have one out-segment originating at an LSR
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.
mplsTunnelTable does not define the in and out segments mplsTunnelTable does not define the in and out segments forming the
forming the tunnel. Instead, these are defined by creating tunnel. Instead, these are defined by creating rows in the in-
rows in the in-segment and out-segment tables, defining segment and out-segment tables, defining relationships in the cross-
relationships in the cross-connect table and referring to connect table, and referring to these rows in the mplsTunnelTable
these rows in the mplsTunnelTable using a cross-connect using a cross-connect index, mplsTunnelXCIndex. These segment and
index, mplsTunnelXCIndex. These segment and cross-connect cross-connect related objects are defined in [RFC3813].
related objects are defined in [LSRMIB].
6.2. mplsTunnelResourceTable 6.2. mplsTunnelResourceTable
mplsTunnelResourceTable is used to indicate the resources mplsTunnelResourceTable is used to indicate the resources required
required for a tunnel. Multiple tunnels may share the same for a tunnel. Multiple tunnels may share the same resources by
resources by pointing to the same entry in this table. pointing to the same entry in this table. Tunnels that do not share
Tunnels that do not share resources must point to separate resources must point to separate entries in this table.
entries in this table.
6.3. mplsTunnelHopTable 6.3. mplsTunnelHopTable
mplsTunnelHopTable is used to indicate the hops, strict or mplsTunnelHopTable is used to indicate the hops, strict or loose, for
loose, for an MPLS tunnel defined in mplsTunnelTable, when an MPLS tunnel defined in mplsTunnelTable, when it is established via
it is established via signalling. Multiple tunnels may signalling. Multiple tunnels may share the same hops by pointing to
share the same hops by pointing to the same entry in this the same entry in this table. Each row also has a secondary index,
table. Each row also has a secondary index, mplsTunnelHopIndex, corresponding to the next hop of this tunnel.
mplsTunnelHopIndex, corresponding to the next hop of this The scalar mplsTunnelMaxHops indicates the maximum number of hops
tunnel. The scalar mplsTunnelMaxHops indicates the maximum that can be specified on each tunnel supported by this LSR.
number of hops that can be specified on each tunnel
supported by this LSR.
At transit LSRs this table contains the hops, strict or At transit LSRs, this table contains the hops, strict or loose, that
loose, that apply to the downstream part of this tunnel apply to the downstream part of this tunnel only. This corresponds
only. This corresponds to the requested path received to the requested path received through the signaling protocol.
through the signaling protocol.
6.4. mplsTunnelARHopTable 6.4. mplsTunnelARHopTable
mplsTunnelARHopTable is used to indicate the actual hops mplsTunnelARHopTable is used to indicate the actual hops traversed by
traversed by a tunnel as reported by the MPLS signalling a tunnel as reported by the MPLS signalling protocol after the tunnel
protocol after the tunnel is setup. The support of this is setup. The support of this table is optional since not all MPLS
table is optional since not all MPLS signalling protocol signalling protocols may support this feature.
may support this feature.
At transit LSRs this table contains the actual hops At transit LSRs, this table contains the actual hops traversed by the
traversed by the tunnel along its entire length if that tunnel along its entire length if that information is available.
information is available. This corresponds to the recorded This corresponds to the recorded path reported by the MPLS signalling
path reported by the MPLS signalling protocol, possibly protocol, possibly derived from multiple signaling messages.
derived from multiple signaling messages.
6.5. mplsTunnelCHoptable 6.5. mplsTunnelCHoptable
mplsTunnelCHopTable lists the actual hops computed by a mplsTunnelCHopTable lists the actual hops computed by a constraint-
constraint-based routing algorithm based on the based routing algorithm based on the mplsTunnelHopTable for the MPLS
mplsTunnelHopTable for the MPLS signalling protocol in use. signalling protocol in use. The support of this table is optional
The support of this table is optional since not all since not all implementations may support computation of hop lists
implementations may support computation of hop list using a using a constraint-based routing protocol.
constraint-based routing protocol.
At transit LSRs this table contains the hops computed to At transit LSRs, this table contains the hops computed to apply to
apply to the downstream part of this tunnel. This the downstream part of this tunnel. This corresponds to the
corresponds to the requested path signaled from this LSR requested path signaled from this LSR through the signaling protocol.
through the signaling protocol.
6.6. mplsTunnelPerfTable 6.6. mplsTunnelPerfTable
mplsTunnelPerfTable provides several counters to measure mplsTunnelPerfTable provides several counters to measure the
the performance of the MPLS tunnels. This table augments performance of the MPLS tunnels. This table augments
mplsTunnelTable. mplsTunnelTable.
6.7. mplsTunnelCRLDPResTable 6.7. mplsTunnelCRLDPResTable
mplsTunnelCRLDPResTable contains resource information for mplsTunnelCRLDPResTable contains resource information for those
those tunnels that are signaled using CRLDP [CRLDP]. This tunnels that are signaled using CRLDP [RFC3212]. This is a sparse
is a sparse extension to mplsTunnelResourceTable and is extension to mplsTunnelResourceTable and is also indexed by
also indexed by mplsTunnelResourceIndex. As with mplsTunnelResourceIndex. As with mplsTunnelResourceTable, multiple
mplsTunnelResourceTable, multiple tunnels may share the tunnels may share the same resources by pointing to the same entry in
same resources by pointing to the same entry in this table. this table. Tunnels that do not share resources must point to
Tunnels that do not share resources must point to separate separate entries in this table. The mplsTunnelCRLDPResTable may be
entries in this table. The mplsTunnelCRLDPResTable may be supported only by implementations that support the CR-LDP signaling
supported only by implementations that support the CR-LDP protocol.
signaling protocol.
7. Use of 32-bit and 64-bit Counters 7. Use of 32-bit and 64-bit Counters
64-bit counters are provided in this MIB module for high- 64-bit counters are provided in this MIB module for high-speed
speed interfaces where the use of 32-bit counters might be interfaces where the use of 32-bit counters might be impractical.
impractical. The requirements on the use of 32-bit and 64- The requirements on the use of 32-bit and 64-bit counters (copied
bit counters (copied verbatim from [RFC2863]) are as verbatim from [RFC2863]) are as follows:
follows.
For interfaces that operate at 20,000,000 (20 million) bits For interfaces that operate at 20,000,000 (20 million) bits per
per second or less, 32-bit byte and packet counters MUST be second or less, 32-bit byte and packet counters MUST be supported.
supported. For interfaces that operate faster than For interfaces that operate faster than 20,000,000 bits/second, and
20,000,000 bits/second, and slower than 650,000,000 slower than 650,000,000 bits/second, 32-bit packet counters MUST be
bits/second, 32-bit packet counters MUST be supported and supported and 64-bit octet counters MUST be supported. For
64-bit octet counters MUST be supported. For interfaces interfaces that operate at 650,000,000 bits/second or faster, 64-bit
that operate at 650,000,000 bits/second or faster, 64-bit packet counters AND 64-bit octet counters MUST be supported.
packet counters AND 64-bit octet counters MUST be
supported.
8. Application of the Interface Group to MPLS Tunnels 8. Application of the Interface Group to MPLS Tunnels
The Interfaces Group of MIB II defines generic managed The Interfaces Group of MIB II defines generic managed objects for
objects for managing interfaces. This memo contains the managing interfaces. This memo contains the media-specific
media-specific extensions to the Interfaces Group for extensions to the Interfaces Group for managing MPLS Tunnels as
managing MPLS Tunnels as logical interfaces. logical interfaces.
This memo assumes the interpretation of the Interfaces This memo assumes the interpretation of the Interfaces Group to be in
Group to be in accordance with [RFC2863] which states that accordance with [RFC2863] which states that the interfaces table
the interfaces table (ifTable) contains information on the (ifTable) contains information on the managed resource's interfaces
managed resource's interfaces and that each sub-layer below and that each sub-layer below the internetwork layer of a network
the internetwork layer of a network interface is considered interface is considered an interface. Thus, the MPLS interface is
an interface. Thus, the MPLS interface is represented as represented as an entry in the ifTable. The inter-relation of
an entry in the ifTable. The interrelation of entries in entries in the ifTable is defined by the Interfaces Stack Group
the ifTable is defined by the Interfaces Stack Group
defined in [RFC2863]. defined in [RFC2863].
When using MPLS Tunnels as interfaces, the interface stack When using MPLS Tunnels as interfaces, the interface stack table
table might appear as follows: might appear as follows:
+------------------------------------------------+ +------------------------------------------------+
| MPLS tunnel interface ifType = mplsTunnel(150) | | MPLS tunnel interface ifType = mplsTunnel(150) |
+------------------------------------------------+ +------------------------------------------------+
| MPLS interface ifType = mpls(166) | | MPLS interface ifType = mpls(166) |
+------------------------------------------------+ +------------------------------------------------+
| Underlying layer | | Underlying layer |
+------------------------------------------------+ +------------------------------------------------+
In the above diagram, "Underlying Layer" refers to the In the above diagram, "Underlying Layer" refers to the ifIndex of any
ifIndex of any interface type for which MPLS interface type for which MPLS internetworking has been defined.
internetworking has been defined. Examples include ATM, Examples include ATM, Frame Relay, and Ethernet.
Frame Relay, and Ethernet.
8.1. Support of the MPLS Tunnel Interface by ifTable 8.1. Support of the MPLS Tunnel Interface by ifTable
Some specific interpretations of ifTable for those MPLS Some specific interpretations of the ifTable for those MPLS tunnels
tunnels represented as interfaces follow: represented as interfaces follow:
Object Use for the MPLS tunnel. Object Use for the MPLS tunnel.
ifIndex Each MPLS tunnel is represented by an ifIndex Each MPLS tunnel is represented by an
ifEntry. ifEntry.
ifDescr Description of the MPLS tunnel. ifDescr Description of the MPLS tunnel.
ifType The value that is allocated for MPLS ifType The value that is allocated for the MPLS
tunnel is 150. tunnel is 150.
ifSpeed The total bandwidth in bits per second ifSpeed The total bandwidth in bits per second
for use by the MPLS tunnel. for use by the MPLS tunnel.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus See [RFC2863]. ifAdminStatus See [RFC2863].
ifOperStatus This value reflects the actual ifOperStatus This value reflects the actual
operational status of MPLS tunnel. operational status of the MPLS tunnel.
Assumes the value down(2) if the MPLS Assumes the value down(2) if the MPLS
tunnel is down. tunnel is down.
ifLastChange See [RFC2863]. ifLastChange See [RFC2863].
ifInOctets The number of octets received over the ifInOctets The number of octets received over the
MPLS tunnel. MPLS tunnel.
ifOutOctets The number of octets transmitted over ifOutOctets The number of octets transmitted over
the MPLS tunnel. the MPLS tunnel.
skipping to change at page 9, line 36 skipping to change at page 8, line 44
statements in [RFC2863]. statements in [RFC2863].
ifHCOutOctets The 64-bit version of ifOutOctets; ifHCOutOctets The 64-bit version of ifOutOctets;
supported if required by the compliance supported if required by the compliance
statements in [RFC2863]. statements in [RFC2863].
ifAlias The non-volatile 'alias' name for the ifAlias The non-volatile 'alias' name for the
MPLS tunnel as specified by a network MPLS tunnel as specified by a network
manager. manager.
9. Example of Tunnel Setup 9. Example of Tunnel Setup
This section contains an example of which MIB objects This section contains an example of which MIB objects should be
should be modified if one would like to create a best modified if one would like to create a best effort, loosely routed,
effort, loosely routed, unidirectional traffic engineered unidirectional traffic engineered tunnel, which spans two hops of a
tunnel, which spans two hops of a simple network. Note simple network. Note that these objects should be created on the
that these objects should be created on the "head-end" "head-end" LSR. Those objects relevant to illustrating the
LSR. Those objects relevant to illustrating the relationships amongst different tables are shown here. Other objects
relationships amongst different tables are shown here. may be needed before conceptual row activation can happen.
Other objects may be needed before conceptual row
activation can happen.
The RowStatus values shown in this section are those to be The RowStatus values shown in this section are those to be used in
used in the set request, typically createAndGo(4) which is the set request, typically createAndGo(4) which is used to create the
used to create the conceptual row and have its status conceptual row and have its status immediately set to active. A
immediately set to active. A subsequent retrieval subsequent retrieval operation on the conceptual row will return a
operation on the conceptual row will return a different different value, such as active(1). Please see [RFC2579] for a
value, such as active(1). Please see [RFC2579] for a
detailed discussion on the use of RowStatus. detailed discussion on the use of RowStatus.
In mplsTunnelResourceTable: In mplsTunnelResourceTable:
{ {
mplsTunnelResourceIndex = 5, mplsTunnelResourceIndex = 5,
mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0, mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceMeanBurstSize = 0, mplsTunnelResourceMeanBurstSize = 0,
mplsTunnelResourceExBurstSize = 0, mplsTunnelResourceExBurstSize = 0,
mplsTunnelResourceExBurstSize = unspecified (1), mplsTunnelResourceExBurstSize = unspecified (1),
mplsTunnelResourceWeight = 0, mplsTunnelResourceWeight = 0,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
skipping to change at page 10, line 21 skipping to change at page 9, line 27
mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0, mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceMeanBurstSize = 0, mplsTunnelResourceMeanBurstSize = 0,
mplsTunnelResourceExBurstSize = 0, mplsTunnelResourceExBurstSize = 0,
mplsTunnelResourceExBurstSize = unspecified (1), mplsTunnelResourceExBurstSize = unspecified (1),
mplsTunnelResourceWeight = 0, mplsTunnelResourceWeight = 0,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelResourceRowStatus = createAndGo (4) mplsTunnelResourceRowStatus = createAndGo (4)
} }
The next two instances of mplsTunnelHopEntry are used to The next two instances of mplsTunnelHopEntry are used to denote the
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 tunnel, or the The following denotes the beginning of the tunnel, or the first hop.
first hop. We have used the fictitious LSR identified by We have used the fictitious LSR identified by "192.168.100.1" as our
"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),
mplsTunnelHopIpAddr = "192.168.100.1", mplsTunnelHopIpAddr = "192.168.100.1",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2), mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
skipping to change at page 10, line 43 skipping to change at page 10, line 4
mplsTunnelHopAddrType = ipv4 (1), mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.100.1", mplsTunnelHopIpAddr = "192.168.100.1",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2), mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2), mplsTunnelHopEntryPathComp = explicit (2),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
The following denotes the end of the tunnel, or the last hop in our
The following denotes the end of the tunnel, or the last example. We have used the fictitious LSR identified by
hop in our example. We have used the fictitious LSR "192.168.101.1" as our end router.
identified by "192.168.101.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),
mplsTunnelHopIpAddr = "192.168.101.1", mplsTunnelHopIpAddr = "192.168.101.1",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = loose (2), mplsTunnelHopType = loose (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
skipping to change at page 11, line 14 skipping to change at page 10, line 25
mplsTunnelHopIpAddr = "192.168.101.1", mplsTunnelHopIpAddr = "192.168.101.1",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = loose (2), mplsTunnelHopType = loose (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2), mplsTunnelHopEntryPathComp = explicit (2),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
The following denotes the configured tunnel "head" The following denotes the configured tunnel "head" entry:
entry:
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 0, mplsTunnelInstance = 0,
mplsTunnelIngressLSRId = 192.168.100.1, mplsTunnelIngressLSRId = 192.168.100.1,
mplsTunnelEgressLSRId = 192.168.101.1, mplsTunnelEgressLSRId = 192.168.101.1,
mplsTunnelName = "My first tunnel", mplsTunnelName = "My first tunnel",
mplsTunnelDescr = "Here to there", mplsTunnelDescr = "Here to there",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = 0.0, mplsTunnelXCPointer = 0.0,
skipping to change at page 11, line 46 skipping to change at page 11, line 9
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1, mplsTunnelPathInUse = 1,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
Note that any active or signaled instances of the Note that any active or signaled instances of the above tunnel would
above tunnel would appear with the same primary appear with the same primary mplsTunnelIndex, but would have values
mplsTunnelIndex, but would have values greater than greater than 0 for mplsTunnelInstance. They would also have other
0 for mplsTunnelInstance. They would also have other
objects such as the mplsTunnelXCPointer set accordingly. objects such as the mplsTunnelXCPointer set accordingly.
10. The Use of RowPointer 10. The Use of RowPointer
RowPointer is a textual convention used to identify a
conceptual row in a conceptual table in a MIB by pointing
to the first accessible object. In this MIB module, in
mplsTunnelTable, the objects mplsTunnelXCPointer and
mplsTunnelResourcePointer are of type RowPointer. The
object mplsTunnelXCPointer points to a specific entry in
the mplsXCTable [LSRMIB]. This entry in the mplsXCTable is
the associated LSP for the given MPLS tunnel entry. The
object mplsTunnelResourcePointer points to a specific entry
in a traffic parameter table. An example of such a traffic
parameter table is mplsTunnelResourceTable. It indicates a
specific instance of a traffic parameter entry that is
associated with a given MPLS tunnel entry. These
RowPointer objects MUST point to the first instance of the
first accessible columnar object in the appropriate
conceptual row in order to allow the manager to find the
appropriate corresponding entry in either MPLS-LSR-STD-MIB
[LSRMIB] or MPLS-TE-STD-MIB [TEMIB]. If object
mplsTunnelXCPointer returns zeroDotZero it implies that
there is no LSP associated with that particular instance of
tunnel entry. If object mplsTunnelResourcePointer returns
zeroDotZero it implies that there is no QoS resource
associated with that particular instance of tunnel entry.
11. MPLS Traffic Engineering MIB Definitions
MPLS-TE-STD-MIB DEFINITIONS ::= BEGIN RowPointer is a textual convention used to identify a conceptual row
in a conceptual table in a MIB by pointing to the first accessible
object. In this MIB module, in mplsTunnelTable, the objects
mplsTunnelXCPointer and mplsTunnelResourcePointer are of type
RowPointer. The object mplsTunnelXCPointer points to a specific
entry in the mplsXCTable [RFC3813]. This entry in the mplsXCTable is
the associated LSP for the given MPLS tunnel entry. The object
mplsTunnelResourcePointer points to a specific entry in a traffic
parameter table. An example of such a traffic parameter table is
mplsTunnelResourceTable. It indicates a specific instance of a
traffic parameter entry that is associated with a given MPLS tunnel
entry. These RowPointer objects MUST point to the first instance of
the first accessible columnar object in the appropriate conceptual
row in order to allow the manager to find the appropriate
corresponding entry in either MPLS-LSR-STD-MIB [RFC3813] or MPLS-TE-
STD-MIB. If object mplsTunnelXCPointer returns zeroDotZero, it
implies that there is no LSP associated with that particular instance
of tunnel entry. If object mplsTunnelResourcePointer returns
zeroDotZero, it implies that there is no QoS resource associated with
that particular instance of tunnel entry.
IMPORTS 11. MPLS Traffic Engineering MIB Definitions
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Unsigned32, Counter32, Counter64, TimeTicks,
zeroDotZero
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
TruthValue, RowStatus, RowPointer, StorageType,
TimeStamp
FROM SNMPv2-TC
InterfaceIndexOrZero, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
FROM IF-MIB
mplsStdMIB, MplsBitRate, MplsBurstSize, MplsLSPID,
MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsTunnelAffinity, MplsExtendedTunnelId, MplsPathIndex,
MplsPathIndexOrZero, MplsOwner, TeHopAddressType,
TeHopAddress, TeHopAddressAS, TeHopAddressUnnum
FROM MPLS-TC-STD-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
IndexIntegerNextFree
FROM DIFFSERV-MIB
InetAddressPrefixLength
FROM INET-ADDRESS-MIB
;
mplsTeStdMIB MODULE-IDENTITY MPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
LAST-UPDATED
"200310191200Z" -- 19 October 2003 12:00:00 GMT
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
" Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Arun Viswanathan IMPORTS
Force10 Networks, Inc. MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Email: arunv@force10networks.com Integer32, Unsigned32, Counter32, Counter64, TimeTicks,
zeroDotZero
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowStatus, RowPointer, StorageType,
TimeStamp
FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
FROM IF-MIB -- [RFC2863]
mplsStdMIB, MplsBitRate, MplsBurstSize, MplsLSPID,
MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsTunnelAffinity, MplsExtendedTunnelId, MplsPathIndex,
MplsPathIndexOrZero, MplsOwner, TeHopAddressType,
TeHopAddress, TeHopAddressAS, TeHopAddressUnnum
FROM MPLS-TC-STD-MIB -- [RFC3811]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
IndexIntegerNextFree
FROM DIFFSERV-MIB -- [RFC3289]
InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC3291]
;
Thomas D. Nadeau mplsTeStdMIB MODULE-IDENTITY
Cisco Systems, Inc. LAST-UPDATED
Email: tnadeau@cisco.com "200406030000Z" -- June 3, 2004
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
" Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Comments about this document should be emailed Arun Viswanathan
directly to the MPLS working group mailing list at Force10 Networks, Inc.
mpls@uu.net." Email: arunv@force10networks.com
DESCRIPTION
"Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC xxxx; see
the RFC itself for full legal notices.
This MIB module contains managed object definitions Thomas D. Nadeau
for MPLS Traffic Engineering (TE) as defined in: Cisco Systems, Inc.
1. Extensions to RSVP for LSP Tunnels, Awduche et Email: tnadeau@cisco.com
al, RFC 3209, December 2001
2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002
3. Requirements for Traffic Engineering Over MPLS,
Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,
and J. McManus, RFC 2702, September 1999"
-- Revision history. Comments about this document should be emailed
directly to the MPLS working group mailing list at
mpls@uu.net."
DESCRIPTION
"Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3812. For full legal notices see the RFC
itself or see: http://www.ietf.org/copyrights/ianamib.html
REVISION This MIB module contains managed object definitions
"200310191200Z" -- 19 October 2003 12:00:00 GMT for MPLS Traffic Engineering (TE) as defined in:
DESCRIPTION 1. Extensions to RSVP for LSP Tunnels, Awduche et
"Initial draft version issued as part of RFC XXXX." al, RFC 3209, December 2001
2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002
3. Requirements for Traffic Engineering Over MPLS,
Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,
and J. McManus, [RFC2702], September 1999"
::= { mplsStdMIB XXX } -- Please see IANA considerations section -- Revision history.
-- the requested mplsStdMIB subId is 3.
REVISION
"200406030000Z" -- June 3, 2004
DESCRIPTION
"Initial version issued as part of RFC 3812."
mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 } ::= { mplsStdMIB 3 }
mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 }
mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 }
mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 }
-- Top level components of this MIB module.
mplsTunnelConfigured OBJECT-TYPE -- traps
SYNTAX Unsigned32 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 }
MAX-ACCESS read-only -- tables, scalars
STATUS current mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 }
DESCRIPTION mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 }
"The number of tunnels configured on this device. A -- conformance
tunnel is considered configured if the mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 }
mplsTunnelRowStatus is active(1)."
::= { mplsTeScalars 1 }
mplsTunnelActive OBJECT-TYPE -- MPLS Tunnel scalars.
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of tunnels active on this device. A
tunnel is considered active if the
mplsTunnelOperStatus is up(1)."
::= { mplsTeScalars 2 }
mplsTunnelTEDistProto OBJECT-TYPE mplsTunnelConfigured OBJECT-TYPE
SYNTAX BITS { SYNTAX Unsigned32
other (0), MAX-ACCESS read-only
ospf (1), STATUS current
isis (2) DESCRIPTION
} "The number of tunnels configured on this device. A
MAX-ACCESS read-only tunnel is considered configured if the
STATUS current mplsTunnelRowStatus is active(1)."
DESCRIPTION ::= { mplsTeScalars 1 }
"The traffic engineering distribution protocol(s)
used by this LSR. Note that an LSR may support more
than one distribution protocol simultaneously."
::= { mplsTeScalars 3 }
mplsTunnelMaxHops OBJECT-TYPE mplsTunnelActive OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of hops that can be specified for "The number of tunnels active on this device. A
a tunnel on this device." tunnel is considered active if the
::= { mplsTeScalars 4 } mplsTunnelOperStatus is up(1)."
::= { mplsTeScalars 2 }
mplsTunnelNotificationMaxRate OBJECT-TYPE mplsTunnelTEDistProto OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX BITS {
MAX-ACCESS read-write other (0),
STATUS current ospf (1),
DESCRIPTION isis (2)
"This variable indicates the maximum number of }
notifications issued per second. If events occur MAX-ACCESS read-only
more rapidly, the implementation may simply fail to STATUS current
emit these notifications during that period, or may DESCRIPTION
queue them until an appropriate time. A value of 0 "The traffic engineering distribution protocol(s)
means no throttling is applied and events may be used by this LSR. Note that an LSR may support more
notified at the rate at which they occur." than one distribution protocol simultaneously."
DEFVAL { 0 } ::= { mplsTeScalars 3 }
::= { mplsTeScalars 5 }
mplsTunnelMaxHops OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of hops that can be specified for
a tunnel on this device."
::= { mplsTeScalars 4 }
mplsTunnelNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum number of
notifications issued per second. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period, or may
queue them until an appropriate time. A value of 0
means no throttling is applied and events may be
notified at the rate at which they occur."
DEFVAL { 0 }
::= { mplsTeScalars 5 }
mplsTunnelIndexNext OBJECT-TYPE -- End of MPLS Tunnel scalars.
SYNTAX IndexIntegerNextFree (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelIndex.
Note that this object offers an unused value -- MPLS tunnel table.
for an mplsTunnelIndex value at the ingress
side of a tunnel. At other LSRs the value
of mplsTunnelIndex SHOULD be taken from the
value signaled by the MPLS signaling protocol.
"
::= { mplsTeObjects 1 }
mplsTunnelTable OBJECT-TYPE mplsTunnelIndexNext OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelEntry SYNTAX IndexIntegerNextFree (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelTable allows new MPLS tunnels to be "This object contains an unused value for
created between an LSR and a remote endpoint, and mplsTunnelIndex, or a zero to indicate
existing tunnels to be reconfigured or removed. that none exist. Negative values are not allowed,
Note that only point-to-point tunnel segments are as they do not correspond to valid values of
supported, although multi-point-to-point and point- mplsTunnelIndex.
to-multi-point connections are supported by an LSR
acting as a cross-connect. Each MPLS tunnel can
thus have one out-segment originating at this LSR
and/or one in-segment terminating at this LSR."
::= { mplsTeObjects 2 }
mplsTunnelEntry OBJECT-TYPE Note that this object offers an unused value
SYNTAX MplsTunnelEntry for an mplsTunnelIndex value at the ingress
MAX-ACCESS not-accessible side of a tunnel. At other LSRs the value
STATUS current of mplsTunnelIndex SHOULD be taken from the
DESCRIPTION value signaled by the MPLS signaling protocol.
"An entry in this table represents an MPLS tunnel. "
An entry can be created by a network administrator ::= { mplsTeObjects 1 }
or by an SNMP agent as instructed by an MPLS
signalling protocol. Whenever a new entry is
created with mplsTunnelIsIf set to true(1), then a
corresponding entry is created in ifTable as well
(see RFC 2863). The ifType of this entry is
mplsTunnel(150).
A tunnel entry needs to be uniquely identified across mplsTunnelTable OBJECT-TYPE
a MPLS network. Indices mplsTunnelIndex and SYNTAX SEQUENCE OF MplsTunnelEntry
mplsTunnelInstance uniquely identify a tunnel on MAX-ACCESS not-accessible
the LSR originating the tunnel. To uniquely STATUS current
identify a tunnel across an MPLS network requires DESCRIPTION
index mplsTunnelIngressLSRId. The last index "The mplsTunnelTable allows new MPLS tunnels to be
mplsTunnelEgressLSRId is useful in identifying all created between an LSR and a remote endpoint, and
instances of a tunnel that terminate on the same existing tunnels to be reconfigured or removed.
egress LSR." Note that only point-to-point tunnel segments are
REFERENCE supported, although multipoint-to-point and point-
"1. RFC 2863 - The Interfaces Group MIB, McCloghrie, to-multipoint connections are supported by an LSR
K., and F. Kastenholtz, June 2000 " acting as a cross-connect. Each MPLS tunnel can
INDEX { mplsTunnelIndex, thus have one out-segment originating at this LSR
mplsTunnelInstance, and/or one in-segment terminating at this LSR."
mplsTunnelIngressLSRId, ::= { mplsTeObjects 2 }
mplsTunnelEgressLSRId
}
::= { mplsTunnelTable 1 }
MplsTunnelEntry ::= SEQUENCE { mplsTunnelEntry OBJECT-TYPE
mplsTunnelIndex MplsTunnelIndex, SYNTAX MplsTunnelEntry
mplsTunnelInstance MplsTunnelInstanceIndex, MAX-ACCESS not-accessible
mplsTunnelIngressLSRId MplsExtendedTunnelId, STATUS current
mplsTunnelEgressLSRId MplsExtendedTunnelId, DESCRIPTION
mplsTunnelName SnmpAdminString, "An entry in this table represents an MPLS tunnel.
mplsTunnelDescr SnmpAdminString, An entry can be created by a network administrator
mplsTunnelIsIf TruthValue, or by an SNMP agent as instructed by an MPLS
mplsTunnelIfIndex InterfaceIndexOrZero, signalling protocol. Whenever a new entry is
mplsTunnelOwner MplsOwner, created with mplsTunnelIsIf set to true(1), then a
mplsTunnelRole INTEGER, corresponding entry is created in ifTable as well
mplsTunnelXCPointer RowPointer, (see RFC 2863). The ifType of this entry is
mplsTunnelSignallingProto INTEGER, mplsTunnel(150).
mplsTunnelSetupPrio Integer32,
mplsTunnelHoldingPrio Integer32,
mplsTunnelSessionAttributes BITS,
mplsTunnelLocalProtectInUse TruthValue,
mplsTunnelResourcePointer RowPointer,
mplsTunnelPrimaryInstance MplsTunnelInstanceIndex,
mplsTunnelInstancePriority Unsigned32,
mplsTunnelHopTableIndex MplsPathIndexOrZero,
mplsTunnelPathInUse MplsPathIndexOrZero,
mplsTunnelARHopTableIndex MplsPathIndexOrZero,
mplsTunnelCHopTableIndex MplsPathIndexOrZero,
mplsTunnelIncludeAnyAffinity MplsTunnelAffinity,
mplsTunnelIncludeAllAffinity MplsTunnelAffinity,
mplsTunnelExcludeAnyAffinity MplsTunnelAffinity,
mplsTunnelTotalUpTime TimeTicks,
mplsTunnelInstanceUpTime TimeTicks,
mplsTunnelPrimaryUpTime TimeTicks,
mplsTunnelPathChanges Counter32,
mplsTunnelLastPathChange TimeTicks,
mplsTunnelCreationTime TimeStamp,
mplsTunnelStateTransitions Counter32,
mplsTunnelAdminStatus INTEGER,
mplsTunnelOperStatus INTEGER,
mplsTunnelRowStatus RowStatus,
mplsTunnelStorageType StorageType
}
mplsTunnelIndex OBJECT-TYPE A tunnel entry needs to be uniquely identified across
SYNTAX MplsTunnelIndex a MPLS network. Indices mplsTunnelIndex and
MAX-ACCESS not-accessible mplsTunnelInstance uniquely identify a tunnel on
STATUS current the LSR originating the tunnel. To uniquely
DESCRIPTION identify a tunnel across an MPLS network requires
"Uniquely identifies a set of tunnel instances index mplsTunnelIngressLSRId. The last index
between a pair of ingress and egress LSRs. mplsTunnelEgressLSRId is useful in identifying all
Managers should obtain new values for row instances of a tunnel that terminate on the same
creation in this table by reading egress LSR."
mplsTunnelIndexNext. When REFERENCE
the MPLS signalling protocol is rsvp(2) this value "1. RFC 2863 - The Interfaces Group MIB, McCloghrie,
SHOULD be equal to the value signaled in the K., and F. Kastenholtz, June 2000 "
Tunnel Id of the Session object. When the MPLS INDEX { mplsTunnelIndex,
signalling protocol is crldp(3) this value mplsTunnelInstance,
SHOULD be equal to the value signaled in the mplsTunnelIngressLSRId,
LSP ID." mplsTunnelEgressLSRId
::= { mplsTunnelEntry 1 } }
::= { mplsTunnelTable 1 }
mplsTunnelInstance OBJECT-TYPE MplsTunnelEntry ::= SEQUENCE {
SYNTAX MplsTunnelInstanceIndex mplsTunnelIndex MplsTunnelIndex,
MAX-ACCESS not-accessible mplsTunnelInstance MplsTunnelInstanceIndex,
STATUS current mplsTunnelIngressLSRId MplsExtendedTunnelId,
DESCRIPTION mplsTunnelEgressLSRId MplsExtendedTunnelId,
"Uniquely identifies a particular instance of a mplsTunnelName SnmpAdminString,
tunnel between a pair of ingress and egress LSRs. mplsTunnelDescr SnmpAdminString,
It is useful to identify multiple instances of mplsTunnelIsIf TruthValue,
tunnels for the purposes of backup and parallel mplsTunnelIfIndex InterfaceIndexOrZero,
tunnels. When the MPLS signaling protocol is mplsTunnelOwner MplsOwner,
rsvp(2) this value SHOULD be equal to the LSP Id mplsTunnelRole INTEGER,
of the Sender Template object. When the signaling mplsTunnelXCPointer RowPointer,
protocol is crldp(3) there is no equivalent mplsTunnelSignallingProto INTEGER,
signaling object." mplsTunnelSetupPrio Integer32,
::= { mplsTunnelEntry 2 } mplsTunnelHoldingPrio Integer32,
mplsTunnelSessionAttributes BITS,
mplsTunnelLocalProtectInUse TruthValue,
mplsTunnelResourcePointer RowPointer,
mplsTunnelPrimaryInstance MplsTunnelInstanceIndex,
mplsTunnelInstancePriority Unsigned32,
mplsTunnelHopTableIndex MplsPathIndexOrZero,
mplsTunnelPathInUse MplsPathIndexOrZero,
mplsTunnelARHopTableIndex MplsPathIndexOrZero,
mplsTunnelCHopTableIndex MplsPathIndexOrZero,
mplsTunnelIncludeAnyAffinity MplsTunnelAffinity,
mplsTunnelIncludeAllAffinity MplsTunnelAffinity,
mplsTunnelExcludeAnyAffinity MplsTunnelAffinity,
mplsTunnelTotalUpTime TimeTicks,
mplsTunnelInstanceUpTime TimeTicks,
mplsTunnelPrimaryUpTime TimeTicks,
mplsTunnelPathChanges Counter32,
mplsTunnelLastPathChange TimeTicks,
mplsTunnelCreationTime TimeStamp,
mplsTunnelStateTransitions Counter32,
mplsTunnelAdminStatus INTEGER,
mplsTunnelOperStatus INTEGER,
mplsTunnelRowStatus RowStatus,
mplsTunnelStorageType StorageType
}
mplsTunnelIngressLSRId OBJECT-TYPE mplsTunnelIndex OBJECT-TYPE
SYNTAX MplsExtendedTunnelId SYNTAX MplsTunnelIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identity of the ingress LSR associated with this "Uniquely identifies a set of tunnel instances
tunnel instance. When the MPLS signalling protocol between a pair of ingress and egress LSRs.
is rsvp(2) this value SHOULD be equal to the Tunnel Managers should obtain new values for row
Sender Address in the Sender Template object and MAY creation in this table by reading
be equal to the Extended Tunnel Id field in the mplsTunnelIndexNext. When
SESSION object. When the MPLS signalling protocol is the MPLS signalling protocol is rsvp(2) this value
crldp(3) this value SHOULD be equal to the Ingress SHOULD be equal to the value signaled in the
LSR Router ID field in the LSPID TLV object." Tunnel Id of the Session object. When the MPLS
REFERENCE signalling protocol is crldp(3) this value
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, SHOULD be equal to the value signaled in the
Awduche et al, RFC 3209, December 2001 LSP ID."
2. Constraint-Based LSP Setup using LDP, Jamoussi ::= { mplsTunnelEntry 1 }
(Editor), RFC 3212, January 2002"
::= { mplsTunnelEntry 3 }
mplsTunnelEgressLSRId OBJECT-TYPE mplsTunnelInstance OBJECT-TYPE
SYNTAX MplsExtendedTunnelId SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identity of the egress LSR associated with this "Uniquely identifies a particular instance of a
tunnel instance." tunnel between a pair of ingress and egress LSRs.
::= { mplsTunnelEntry 4 } It is useful to identify multiple instances of
tunnels for the purposes of backup and parallel
tunnels. When the MPLS signaling protocol is
rsvp(2) this value SHOULD be equal to the LSP Id
of the Sender Template object. When the signaling
protocol is crldp(3) there is no equivalent
signaling object."
::= { mplsTunnelEntry 2 }
mplsTunnelName OBJECT-TYPE mplsTunnelIngressLSRId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The canonical name assigned to the tunnel. This name "Identity of the ingress LSR associated with this
can be used to refer to the tunnel on the LSR's tunnel instance. When the MPLS signalling protocol
console port. If mplsTunnelIsIf is set to true is rsvp(2) this value SHOULD be equal to the Tunnel
then the ifName of the interface corresponding to Sender Address in the Sender Template object and MAY
this tunnel should have a value equal to be equal to the Extended Tunnel Id field in the
mplsTunnelName. Also see the description of ifName SESSION object. When the MPLS signalling protocol is
in RFC 2863." crldp(3) this value SHOULD be equal to the Ingress
REFERENCE LSR Router ID field in the LSPID TLV object."
"RFC 2863 - The Interfaces Group MIB, McCloghrie, K., REFERENCE
and F. Kastenholtz, June 2000" "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
DEFVAL {""} Awduche et al, RFC 3209, December 2001
::= { mplsTunnelEntry 5 } 2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002"
::= { mplsTunnelEntry 3 }
mplsTunnelDescr OBJECT-TYPE mplsTunnelEgressLSRId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about the "Identity of the egress LSR associated with this
tunnel. If there is no description this object tunnel instance."
contains a zero length string. This object is may ::= { mplsTunnelEntry 4 }
not be signaled by MPLS signaling protocols,
consequentally the value of this object at transit
and egress LSRs MAY be automatically generated or
absent."
DEFVAL {""}
::= { mplsTunnelEntry 6 }
mplsTunnelIsIf OBJECT-TYPE mplsTunnelName OBJECT-TYPE
SYNTAX TruthValue SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel corresponds to an "The canonical name assigned to the tunnel. This name
interface represented in the interfaces group can be used to refer to the tunnel on the LSR's
table. Note that if this variable is set to true console port. If mplsTunnelIsIf is set to true
then the ifName of the interface corresponding to then the ifName of the interface corresponding to
this tunnel should have a value equal to this tunnel should have a value equal to
mplsTunnelName. Also see the description of ifName mplsTunnelName. Also see the description of ifName
in RFC 2863. This object is meaningful only at the in RFC 2863."
ingress and egress LSRs." REFERENCE
REFERENCE "RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
"RFC 2863 - The Interfaces Group MIB, McCloghrie, K., and F. Kastenholtz, June 2000"
and F. Kastenholtz, June 2000" DEFVAL {""}
::= { mplsTunnelEntry 5 }
DEFVAL { false } mplsTunnelDescr OBJECT-TYPE
::= { mplsTunnelEntry 7 } SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about the
tunnel. If there is no description this object
contains a zero length string. This object is may
not be signaled by MPLS signaling protocols,
consequentally the value of this object at transit
and egress LSRs MAY be automatically generated or
absent."
DEFVAL {""}
::= { mplsTunnelEntry 6 }
mplsTunnelIfIndex OBJECT-TYPE mplsTunnelIsIf OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelIsIf is set to true, then this value "Denotes whether or not this tunnel corresponds to an
contains the LSR-assigned ifIndex which corresponds interface represented in the interfaces group
to an entry in the interfaces table. Otherwise table. Note that if this variable is set to true
this variable should contain the value of zero then the ifName of the interface corresponding to
indicating that a valid ifIndex was not assigned to this tunnel should have a value equal to
this tunnel interface." mplsTunnelName. Also see the description of ifName
REFERENCE in RFC 2863. This object is meaningful only at the
"RFC 2863 - The Interfaces Group MIB, McCloghrie, K., ingress and egress LSRs."
and F. Kastenholtz, June 2000" REFERENCE
DEFVAL { 0 } "RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
::= { mplsTunnelEntry 8 } and F. Kastenholtz, June 2000"
DEFVAL { false }
::= { mplsTunnelEntry 7 }
mplsTunnelOwner OBJECT-TYPE mplsTunnelIfIndex OBJECT-TYPE
SYNTAX MplsOwner SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the entity that created and is responsible "If mplsTunnelIsIf is set to true, then this value
for managing this tunnel. This column is contains the LSR-assigned ifIndex which corresponds
automatically filled by the agent on creation of a to an entry in the interfaces table. Otherwise
row." this variable should contain the value of zero
::= { mplsTunnelEntry 9 } indicating that a valid ifIndex was not assigned to
this tunnel interface."
REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
and F. Kastenholtz, June 2000"
DEFVAL { 0 }
::= { mplsTunnelEntry 8 }
mplsTunnelRole OBJECT-TYPE mplsTunnelOwner OBJECT-TYPE
SYNTAX INTEGER { head(1), SYNTAX MplsOwner
transit(2), MAX-ACCESS read-only
tail(3), STATUS current
headTail(4) } DESCRIPTION
MAX-ACCESS read-create "Denotes the entity that created and is responsible
STATUS current for managing this tunnel. This column is
DESCRIPTION automatically filled by the agent on creation of a
"This value signifies the role that this tunnel row."
entry/instance represents. This value MUST be set ::= { mplsTunnelEntry 9 }
to head(1) at the originating point of the tunnel.
This value MUST be set to transit(2) at transit
points along the tunnel, if transit points are
supported. This value MUST be set to tail(3) at the
terminating point of the tunnel if tunnel tails are
supported.
The value headTail(4) is provided for tunnels that mplsTunnelRole OBJECT-TYPE
begin and end on the same LSR." SYNTAX INTEGER { head(1),
transit(2),
tail(3),
headTail(4) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value signifies the role that this tunnel
entry/instance represents. This value MUST be set
to head(1) at the originating point of the tunnel.
This value MUST be set to transit(2) at transit
points along the tunnel, if transit points are
supported. This value MUST be set to tail(3) at the
terminating point of the tunnel if tunnel tails are
supported.
DEFVAL { head } The value headTail(4) is provided for tunnels that
::= { mplsTunnelEntry 10 } begin and end on the same LSR."
DEFVAL { head }
::= { mplsTunnelEntry 10 }
mplsTunnelXCPointer OBJECT-TYPE mplsTunnelXCPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable points to a row in the mplsXCTable. "This variable points to a row in the mplsXCTable.
This table identifies the segments that compose This table identifies the segments that compose
this tunnel, their characteristics, and this tunnel, their characteristics, and
relationships to each other. A value of zeroDotZero relationships to each other. A value of zeroDotZero
indicates that no LSP has been associated with this indicates that no LSP has been associated with this
tunnel yet." tunnel yet."
REFERENCE REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS "Srinivasan, C., Viswanathan, A., and T. Nadeau,
Label Switch Router Management Information Base, Multiprotocol Label Switching (MPLS) Label Switching
Internet Draft <draft-ietf-mpls-lsr-mib-14.txt>, Router (LSR) Management Information Base (MIB), RFC 3813,
June 2003." June 2004"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { mplsTunnelEntry 11 } ::= { mplsTunnelEntry 11 }
mplsTunnelSignallingProto OBJECT-TYPE mplsTunnelSignallingProto OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
rsvp(2), rsvp(2),
crldp(3), crldp(3),
other(4) other(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The signalling protocol, if any, used to setup this "The signalling protocol, if any, used to setup this
tunnel." tunnel."
DEFVAL { none } DEFVAL { none }
::= { mplsTunnelEntry 12 } ::= { mplsTunnelEntry 12 }
mplsTunnelSetupPrio OBJECT-TYPE mplsTunnelSetupPrio OBJECT-TYPE
SYNTAX Integer32 (0..7) SYNTAX Integer32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the setup priority of this tunnel." "Indicates the setup priority of this tunnel."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001 Awduche et al, RFC 3209, December 2001
2. Constraint-Based LSP Setup using LDP, Jamoussi 2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002" (Editor), RFC 3212, January 2002"
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 13 } ::= { mplsTunnelEntry 13 }
mplsTunnelHoldingPrio OBJECT-TYPE mplsTunnelHoldingPrio OBJECT-TYPE
SYNTAX Integer32 (0..7) SYNTAX Integer32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the holding priority for this tunnel." "Indicates the holding priority for this tunnel."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC3209, December 2001 Awduche et al, RFC 3209, December 2001
2. Constraint-Based LSP Setup using LDP, Jamoussi 2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002" (Editor), RFC 3212, January 2002"
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 14 } ::= { mplsTunnelEntry 14 }
mplsTunnelSessionAttributes OBJECT-TYPE mplsTunnelSessionAttributes OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
fastReroute (0), fastReroute (0),
mergingPermitted (1), mergingPermitted (1),
isPersistent (2), isPersistent (2),
isPinned (3), isPinned (3),
recordRoute(4) recordRoute(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bit mask indicates optional session values for "This bit mask indicates optional session values for
this tunnel. The following describes these bit this tunnel. The following describes these bit
fields: fields:
fastRerouteThis flag indicates that the any tunnel fastRerouteThis flag indicates that the any tunnel
hop may choose to reroute this tunnel without hop may choose to reroute this tunnel without
tearing it down. This flag permits transit routers tearing it down. This flag permits transit routers
to use a local repair mechanism which may result in to use a local repair mechanism which may result in
violation of the explicit routing of this tunnel. violation of the explicit routing of this tunnel.
When a fault is detected on an adjacent downstream When a fault is detected on an adjacent downstream
link or node, a transit router can re-route traffic link or node, a transit router can re-route traffic
for fast service restoration. for fast service restoration.
mergingPermitted This flag permits transit routers mergingPermitted This flag permits transit routers
to merge this session with other RSVP sessions for to merge this session with other RSVP sessions for
the purpose of reducing resource overhead on the purpose of reducing resource overhead on
downstream transit routers, thereby providing downstream transit routers, thereby providing
better network scaling. better network scaling.
isPersistent Indicates whether this tunnel should isPersistent Indicates whether this tunnel should
be restored automatically after a failure occurs. be restored automatically after a failure occurs.
isPinned This flag indicates whether the loose- isPinned This flag indicates whether the loose-
routed hops of this tunnel are to be pinned. routed hops of this tunnel are to be pinned.
recordRouteThis flag indicates whether or not the recordRouteThis flag indicates whether or not the
signalling protocol should remember the tunnel path signalling protocol should remember the tunnel path
after it has been signaled." after it has been signaled."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001." Awduche et al, RFC 3209, December 2001."
::= { mplsTunnelEntry 15 } ::= { mplsTunnelEntry 15 }
mplsTunnelLocalProtectInUse OBJECT-TYPE mplsTunnelLocalProtectInUse OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates that the local repair mechanism is in use "Indicates that the local repair mechanism is in use
to maintain this tunnel (usually in the face of an to maintain this tunnel (usually in the face of an
outage of the link it was previously routed over)." outage of the link it was previously routed over)."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelEntry 16 } ::= { mplsTunnelEntry 16 }
mplsTunnelResourcePointer OBJECT-TYPE mplsTunnelResourcePointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents a pointer to the traffic "This variable represents a pointer to the traffic
parameter specification for this tunnel. This parameter specification for this tunnel. This
value may point at an entry in the value may point at an entry in the
mplsTunnelResourceEntry to indicate which mplsTunnelResourceEntry to indicate which
mplsTunnelResourceEntry is to be assigned to this mplsTunnelResourceEntry is to be assigned to this
LSP instance. This value may optionally point at LSP instance. This value may optionally point at
an externally defined traffic parameter an externally defined traffic parameter
specification table. A value of zeroDotZero specification table. A value of zeroDotZero
indicates best-effort treatment. By having the indicates best-effort treatment. By having the
same value of this object, two or more LSPs can same value of this object, two or more LSPs can
indicate resource sharing." indicate resource sharing."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { mplsTunnelEntry 17 } ::= { mplsTunnelEntry 17 }
mplsTunnelPrimaryInstance OBJECT-TYPE mplsTunnelPrimaryInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the instance index of the primary instance "Specifies the instance index of the primary instance
of this tunnel. More details of the definition of of this tunnel. More details of the definition of
tunnel instances and the primary tunnel instance tunnel instances and the primary tunnel instance
can be found in the description of the textual can be found in the description of the TEXTUAL-CONVENTION
convention MplsTunnelInstanceIndex." MplsTunnelInstanceIndex."
DEFVAL { 0 }
::= { mplsTunnelEntry 18 }
DEFVAL { 0 } mplsTunnelInstancePriority OBJECT-TYPE
::= { mplsTunnelEntry 18 } SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates which priority, in descending
order, with 0 indicating the lowest priority,
within a group of tunnel instances. A group of
tunnel instances is defined as a set of LSPs with
the same mplsTunnelIndex in this table, but with a
different mplsTunnelInstance. Tunnel instance
priorities are used to denote the priority at which
a particular tunnel instance will supercede
another. Instances of tunnels containing the same
mplsTunnelInstancePriority will be used for load
sharing."
mplsTunnelInstancePriority OBJECT-TYPE DEFVAL { 0 }
SYNTAX Unsigned32 ::= { mplsTunnelEntry 19 }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value indicates which priority, in descending
order, with 0 indicating the lowest priority,
within a group of tunnel instances. A group of
tunnel instances is defined as a set of LSPs with
the same mplsTunnelIndex in this table, but with a
different mplsTunnelInstance. Tunnel instance
priorities are used to denote the priority at which
a particular tunnel instance will supercede
another. Instances of tunnels containing the same
mplsTunnelInstancePriority will be used for load
sharing."
DEFVAL { 0 }
::= { mplsTunnelEntry 19 }
mplsTunnelHopTableIndex OBJECT-TYPE mplsTunnelHopTableIndex OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into the mplsTunnelHopTable entry that "Index into the mplsTunnelHopTable entry that
specifies the explicit route hops for this tunnel. specifies the explicit route hops for this tunnel.
This object is meaningful only at the head-end of This object is meaningful only at the head-end of
the tunnel." the tunnel."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 20 } ::= { mplsTunnelEntry 20 }
mplsTunnelPathInUse OBJECT-TYPE mplsTunnelPathInUse OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value denotes the configured path that was "This value denotes the configured path that was
chosen for this tunnel. This value reflects the chosen for this tunnel. This value reflects the
secondary index into mplsTunnelHopTable. This path secondary index into mplsTunnelHopTable. This path
may not exactly match the one in may not exactly match the one in
mplsTunnelARHopTable due to the fact that some CSPF mplsTunnelARHopTable due to the fact that some CSPF
modification may have taken place. See modification may have taken place. See
mplsTunnelARHopTable for the actual path being mplsTunnelARHopTable for the actual path being
taken by the tunnel. A value of zero denotes that taken by the tunnel. A value of zero denotes that
no path is currently in use or available." no path is currently in use or available."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 21 } ::= { mplsTunnelEntry 21 }
mplsTunnelARHopTableIndex OBJECT-TYPE mplsTunnelARHopTableIndex OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into the mplsTunnelARHopTable entry that "Index into the mplsTunnelARHopTable entry that
specifies the actual hops traversed by the tunnel. specifies the actual hops traversed by the tunnel.
This is automatically updated by the agent when the This is automatically updated by the agent when the
actual hops becomes available." actual hops becomes available."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 22 } ::= { mplsTunnelEntry 22 }
mplsTunnelCHopTableIndex OBJECT-TYPE mplsTunnelCHopTableIndex OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into the mplsTunnelCHopTable entry that "Index into the mplsTunnelCHopTable entry that
specifies the computed hops traversed by the specifies the computed hops traversed by the
tunnel. This is automatically updated by the agent tunnel. This is automatically updated by the agent
when computed hops become available or when when computed hops become available or when
computed hops get modified." computed hops get modified."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTunnelEntry 23 } ::= { mplsTunnelEntry 23 }
mplsTunnelIncludeAnyAffinity OBJECT-TYPE mplsTunnelIncludeAnyAffinity OBJECT-TYPE
SYNTAX MplsTunnelAffinity SYNTAX MplsTunnelAffinity
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A link satisfies the include-any constraint if and "A link satisfies the include-any constraint if and
only if the constraint is zero, or the link and the only if the constraint is zero, or the link and the
constraint have a resource class in common." constraint have a resource class in common."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001." Awduche et al, RFC 3209, December 2001."
::= { mplsTunnelEntry 24 } ::= { mplsTunnelEntry 24 }
mplsTunnelIncludeAllAffinity OBJECT-TYPE mplsTunnelIncludeAllAffinity OBJECT-TYPE
SYNTAX MplsTunnelAffinity SYNTAX MplsTunnelAffinity
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A link satisfies the include-all constraint if and "A link satisfies the include-all constraint if and
only if the link contains all of the administrative only if the link contains all of the administrative
groups specified in the constraint." groups specified in the constraint."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001." Awduche et al, RFC 3209, December 2001."
::= { mplsTunnelEntry 25 }
::= { mplsTunnelEntry 25 } mplsTunnelExcludeAnyAffinity OBJECT-TYPE
SYNTAX MplsTunnelAffinity
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A link satisfies the exclude-any constraint if and
only if the link contains none of the
administrative groups specified in the constraint."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001."
DEFVAL { 0 }
::= { mplsTunnelEntry 26 }
mplsTunnelExcludeAnyAffinity OBJECT-TYPE mplsTunnelTotalUpTime OBJECT-TYPE
SYNTAX MplsTunnelAffinity SYNTAX TimeTicks
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A link satisfies the exclude-any constraint if and "This value represents the aggregate up time for all
only if the link contains none of the instances of this tunnel, if available. If this
administrative groups specified in the constraint." value is unavailable, it MUST return a value of 0."
REFERENCE ::= { mplsTunnelEntry 27 }
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, RFC 3209, December 2001."
DEFVAL { 0 }
::= { mplsTunnelEntry 26 }
mplsTunnelTotalUpTime OBJECT-TYPE mplsTunnelInstanceUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the aggregate up time for all "This value identifies the total time that this
instances of this tunnel, if available. If this tunnel instance's operStatus has been Up(1)."
value is unavailable, it MUST return a value of 0." ::= { mplsTunnelEntry 28 }
::= { mplsTunnelEntry 27 }
mplsTunnelInstanceUpTime OBJECT-TYPE mplsTunnelPrimaryUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value identifies the total time that this "Specifies the total time the primary instance of
tunnel instance's operStatus has been Up(1)." this tunnel has been active. The primary instance
::= { mplsTunnelEntry 28 } of this tunnel is defined in
mplsTunnelPrimaryInstance."
::= { mplsTunnelEntry 29 }
mplsTunnelPrimaryUpTime OBJECT-TYPE mplsTunnelPathChanges OBJECT-TYPE
SYNTAX TimeTicks SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the total time the primary instance of "Specifies the number of times the actual path for
this tunnel has been active. The primary instance this tunnel instance has changed."
of this tunnel is defined in ::= { mplsTunnelEntry 30 }
mplsTunnelPrimaryInstance."
::= { mplsTunnelEntry 29 }
mplsTunnelPathChanges OBJECT-TYPE mplsTunnelLastPathChange OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the number of times the actual path for "Specifies the time since the last change to the
this tunnel instance has changed." actual path for this tunnel instance."
::= { mplsTunnelEntry 30 } ::= { mplsTunnelEntry 31 }
mplsTunnelLastPathChange OBJECT-TYPE mplsTunnelCreationTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the time since the last change to the "Specifies the value of SysUpTime when the first
actual path for this tunnel instance." instance of this tunnel came into existence.
::= { mplsTunnelEntry 31 } That is, when the value of mplsTunnelOperStatus
was first set to up(1)."
::= { mplsTunnelEntry 32 }
mplsTunnelCreationTime OBJECT-TYPE mplsTunnelStateTransitions OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the value of SysUpTime when the first "Specifies the number of times the state
instance of this tunnel came into existence. (mplsTunnelOperStatus) of this tunnel instance has
That is, when the value of mplsTunnelOperStatus changed."
was first set to up(1)." ::= { mplsTunnelEntry 33 }
::= { mplsTunnelEntry 32 }
mplsTunnelStateTransitions OBJECT-TYPE mplsTunnelAdminStatus OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only -- ready to pass packets
STATUS current up(1),
DESCRIPTION down(2),
"Specifies the number of times the state -- in some test mode
(mplsTunnelOperStatus) of this tunnel instance has testing(3)
changed." }
::= { mplsTunnelEntry 33 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the desired operational status of this
tunnel."
::= { mplsTunnelEntry 34 }
mplsTunnelAdminStatus OBJECT-TYPE mplsTunnelOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
-- ready to pass packets -- ready to pass packets
up(1), up(1),
down(2), down(2),
-- in some test mode -- in some test mode
testing(3) testing(3),
} -- status cannot be determined
MAX-ACCESS read-create unknown(4),
STATUS current dormant(5),
DESCRIPTION -- some component is missing
"Indicates the desired operational status of this notPresent(6),
tunnel." -- down due to the state of
::= { mplsTunnelEntry 34 } -- lower layer interfaces
lowerLayerDown(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the actual operational status of this
tunnel, which is typically but not limited to, a
function of the state of individual segments of
this tunnel."
::= { mplsTunnelEntry 35 }
mplsTunnelOperStatus OBJECT-TYPE mplsTunnelRowStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX RowStatus
-- ready to pass packets MAX-ACCESS read-create
up(1), STATUS current
down(2), DESCRIPTION
-- in some test mode "This variable is used to create, modify, and/or
testing(3), delete a row in this table. When a row in this
-- status cannot be determined table is in active(1) state, no objects in that row
unknown(4), can be modified by the agent except
dormant(5), mplsTunnelAdminStatus, mplsTunnelRowStatus and
-- some component is missing mplsTunnelStorageType."
notPresent(6), ::= { mplsTunnelEntry 36 }
-- down due to the state of
-- lower layer interfaces
lowerLayerDown(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the actual operational status of this
tunnel, which is typically but not limited to, a
function of the state of individual segments of
this tunnel."
::= { mplsTunnelEntry 35 }
mplsTunnelRowStatus OBJECT-TYPE mplsTunnelStorageType OBJECT-TYPE
SYNTAX RowStatus SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The storage type for this tunnel entry.
"This variable is used to create, modify, and/or Conceptual rows having the value 'permanent'
delete a row in this table. When a row in this need not allow write-access to any columnar
table is in active(1) state, no objects in that row objects in the row."
can be modified by the agent except DEFVAL { volatile }
mplsTunnelAdminStatus, mplsTunnelRowStatus and ::= { mplsTunnelEntry 37 }
mplsTunnelStorageType."
::= { mplsTunnelEntry 36 }
mplsTunnelStorageType OBJECT-TYPE -- End of mplsTunnelTable
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The storage type for this tunnel entry.
Conceptual rows having the value 'permanent'
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsTunnelEntry 37 }
mplsTunnelHopListIndexNext OBJECT-TYPE mplsTunnelHopListIndexNext OBJECT-TYPE
SYNTAX MplsPathIndexOrZero SYNTAX MplsPathIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to be used "This object contains an appropriate value to be used
for mplsTunnelHopListIndex when creating entries in for mplsTunnelHopListIndex when creating entries in
the mplsTunnelHopTable. If the number of the mplsTunnelHopTable. If the number of
unassigned entries is exhausted, a retrieval unassigned entries is exhausted, a retrieval
operation will return a value of 0. This object operation will return a value of 0. This object
may also return a value of 0 when the LSR is unable may also return a value of 0 when the LSR is unable
to accept conceptual row creation, for example, if to accept conceptual row creation, for example, if
the mplsTunnelHopTable is implemented as read-only. the mplsTunnelHopTable is implemented as read-only.
To obtain the value of mplsTunnelHopListIndex for a To obtain the value of mplsTunnelHopListIndex for a
new entry in the mplsTunnelHopTable, the manager new entry in the mplsTunnelHopTable, the manager
issues a management protocol retrieval operation to issues a management protocol retrieval operation to
obtain the current value of mplsTunnelHopIndex. obtain the current value of mplsTunnelHopIndex.
When the SET is performed to create a row in the When the SET is performed to create a row in the
mplsTunnelHopTable, the Command Responder (agent) mplsTunnelHopTable, the Command Responder (agent)
must determine whether the value is indeed still must determine whether the value is indeed still
unused; Two Network Management Applications may unused; Two Network Management Applications may
attempt to create a row (configuration entry) attempt to create a row (configuration entry)
simultaneously and use the same value. If it is simultaneously and use the same value. If it is
currently unused, the SET succeeds and the Command currently unused, the SET succeeds and the Command
Responder (agent) changes the value of this object, Responder (agent) changes the value of this object,
according to an implementation-specific algorithm. according to an implementation-specific algorithm.
If the value is in use, however, the SET fails. The If the value is in use, however, the SET fails. The
Network Management Application must then re-read Network Management Application must then re-read
this variable to obtain a new usable value." this variable to obtain a new usable value."
::= { mplsTeObjects 3 } ::= { mplsTeObjects 3 }
mplsTunnelHopTable OBJECT-TYPE mplsTunnelHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelHopEntry SYNTAX SEQUENCE OF MplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelHopTable is used to indicate the hops, "The mplsTunnelHopTable is used to indicate the hops,
strict or loose, for an instance of an MPLS tunnel strict or loose, for an instance of an MPLS tunnel
defined in mplsTunnelTable, when it is established defined in mplsTunnelTable, when it is established
via signalling, for the outgoing direction of the via signalling, for the outgoing direction of the
tunnel. Thus at a transit LSR, this table contains tunnel. Thus at a transit LSR, this table contains
the desired path of the tunnel from this LSR the desired path of the tunnel from this LSR
onwards. Each row in this table is indexed by onwards. Each row in this table is indexed by
mplsTunnelHopListIndex which corresponds to a group mplsTunnelHopListIndex which corresponds to a group
of hop lists or path options. Each row also has a of hop lists or path options. Each row also has a
secondary index mplsTunnelHopIndex, which indicates secondary index mplsTunnelHopIndex, which indicates
a group of hops (also known as a path option). a group of hops (also known as a path option).
Finally, the third index, mplsTunnelHopIndex
indicates the specific hop information for a path
option. In case we want to specify a particular
interface on the originating LSR of an outgoing
tunnel by which we want packets to exit the LSR,
we specify this as the first hop for this tunnel in
mplsTunnelHopTable."
::= { mplsTeObjects 4 }
Finally, the third index, mplsTunnelHopIndex mplsTunnelHopEntry OBJECT-TYPE
indicates the specific hop information for a path SYNTAX MplsTunnelHopEntry
option. In case we want to specify a particular MAX-ACCESS not-accessible
interface on the originating LSR of an outgoing STATUS current
tunnel by which we want packets to exit the LSR, DESCRIPTION
we specify this as the first hop for this tunnel in "An entry in this table represents a tunnel hop. An
mplsTunnelHopTable." entry is created by a network administrator for
::= { mplsTeObjects 4 } signaled ERLSP set up by an MPLS signalling
protocol."
INDEX {
mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex
}
::= { mplsTunnelHopTable 1 }
mplsTunnelHopEntry OBJECT-TYPE MplsTunnelHopEntry ::= SEQUENCE {
SYNTAX MplsTunnelHopEntry mplsTunnelHopListIndex MplsPathIndex,
MAX-ACCESS not-accessible mplsTunnelHopPathOptionIndex MplsPathIndex,
STATUS current mplsTunnelHopIndex MplsPathIndex,
DESCRIPTION mplsTunnelHopAddrType TeHopAddressType,
"An entry in this table represents a tunnel hop. An mplsTunnelHopIpAddr TeHopAddress,
entry is created by a network administrator for mplsTunnelHopIpPrefixLen InetAddressPrefixLength,
signaled ERLSP set up by an MPLS signalling mplsTunnelHopAsNumber TeHopAddressAS,
protocol." mplsTunnelHopAddrUnnum TeHopAddressUnnum,
INDEX { mplsTunnelHopLspId MplsLSPID,
mplsTunnelHopListIndex, mplsTunnelHopType INTEGER,
mplsTunnelHopPathOptionIndex, mplsTunnelHopInclude TruthValue,
mplsTunnelHopIndex mplsTunnelHopPathOptionName SnmpAdminString,
} mplsTunnelHopEntryPathComp INTEGER,
::= { mplsTunnelHopTable 1 } mplsTunnelHopRowStatus RowStatus,
mplsTunnelHopStorageType StorageType
}
MplsTunnelHopEntry ::= SEQUENCE { mplsTunnelHopListIndex OBJECT-TYPE
mplsTunnelHopListIndex MplsPathIndex, SYNTAX MplsPathIndex
mplsTunnelHopPathOptionIndex MplsPathIndex, MAX-ACCESS not-accessible
mplsTunnelHopIndex MplsPathIndex, STATUS current
mplsTunnelHopAddrType TeHopAddressType, DESCRIPTION
mplsTunnelHopIpAddr TeHopAddress, "Primary index into this table identifying a
mplsTunnelHopIpPrefixLen InetAddressPrefixLength, particular explicit route object."
mplsTunnelHopAsNumber TeHopAddressAS, ::= { mplsTunnelHopEntry 1 }
mplsTunnelHopAddrUnnum TeHopAddressUnnum,
mplsTunnelHopLspId MplsLSPID,
mplsTunnelHopType INTEGER,
mplsTunnelHopInclude TruthValue,
mplsTunnelHopPathOptionName SnmpAdminString,
mplsTunnelHopEntryPathComp INTEGER,
mplsTunnelHopRowStatus RowStatus,
mplsTunnelHopStorageType StorageType
}
mplsTunnelHopListIndex OBJECT-TYPE mplsTunnelHopPathOptionIndex OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX MplsPathIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index into this table identifying a "Secondary index into this table identifying a
particular explicit route object." particular group of hops representing a particular
configured path. This is otherwise known as a path
option."
::= { mplsTunnelHopEntry 2 }
::= { mplsTunnelHopEntry 1 } mplsTunnelHopIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Tertiary index into this table identifying a
particular hop."
::= { mplsTunnelHopEntry 3 }
mplsTunnelHopPathOptionIndex OBJECT-TYPE mplsTunnelHopAddrType OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX TeHopAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The Hop Address Type of this tunnel hop.
"Secondary index into this table identifying a
particular group of hops representing a particular
configured path. This is otherwise known as a path
option."
::= { mplsTunnelHopEntry 2 }
mplsTunnelHopIndex OBJECT-TYPE The value of this object cannot be changed
SYNTAX MplsPathIndex if the value of the corresponding
MAX-ACCESS not-accessible mplsTunnelHopRowStatus object is 'active'.
STATUS current
DESCRIPTION
"Tertiary index into this table identifying a
particular hop."
::= { mplsTunnelHopEntry 3 }
mplsTunnelHopAddrType OBJECT-TYPE Note that lspid(5) is a valid option only
SYNTAX TeHopAddressType for tunnels signaled via CRLDP.
MAX-ACCESS read-create "
STATUS current DEFVAL { ipv4 }
DESCRIPTION "The Hop Address Type of this tunnel hop. ::= { mplsTunnelHopEntry 4 }
The value of this object cannot be changed mplsTunnelHopIpAddr OBJECT-TYPE
if the value of the corresponding SYNTAX TeHopAddress
mplsTunnelHopRowStatus object is 'active'. MAX-ACCESS read-create
STATUS current
DESCRIPTION "The Tunnel Hop Address for this tunnel hop.
Note that lspid(5) is a valid option only The type of this address is determined by the
for tunnels signaled via CRLDP. value of the corresponding mplsTunnelHopAddrType.
"
DEFVAL { ipv4 }
::= { mplsTunnelHopEntry 4 }
mplsTunnelHopIpAddr OBJECT-TYPE The value of this object cannot be changed
SYNTAX TeHopAddress if the value of the corresponding
MAX-ACCESS read-create mplsTunnelHopRowStatus object is 'active'.
STATUS current "
DESCRIPTION "The Tunnel Hop Address for this tunnel hop. DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0
::= { mplsTunnelHopEntry 5 }
The type of this address is determined by the mplsTunnelHopIpPrefixLen OBJECT-TYPE
value of the corresponding mplsTunnelHopAddrType. SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION "If mplsTunnelHopAddrType is set to ipv4(1) or
ipv6(2), then this value will contain an
appropriate prefix length for the IP address in
object mplsTunnelHopIpAddr. Otherwise this value
is irrelevant and should be ignored.
"
DEFVAL { 32 }
::= { mplsTunnelHopEntry 6 }
The value of this object cannot be changed mplsTunnelHopAsNumber OBJECT-TYPE
if the value of the corresponding SYNTAX TeHopAddressAS
mplsTunnelHopRowStatus object is 'active'. MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If mplsTunnelHopAddrType is set to asnumber(3), then
this value will contain the AS number of this hop.
Otherwise the agent should set this object to zero-
length string and the manager should ignore this."
::= { mplsTunnelHopEntry 7 }
" mplsTunnelHopAddrUnnum OBJECT-TYPE
DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 SYNTAX TeHopAddressUnnum
::= { mplsTunnelHopEntry 5 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If mplsTunnelHopAddrType is set to unnum(4), then
this value will contain the interface identifier of
the unnumbered interface for this hop. This object
should be used in conjunction with
mplsTunnelHopIpAddress which would contain the LSR
Router ID in this case. Otherwise the agent should
set this object to zero-length string and the
manager should ignore this."
::= { mplsTunnelHopEntry 8 }
mplsTunnelHopIpPrefixLen OBJECT-TYPE mplsTunnelHopLspId OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX MplsLSPID
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION "If mplsTunnelHopAddrType is set to ipv4(1) or DESCRIPTION
ipv6(2), then this value will contain an "If mplsTunnelHopAddrType is set to lspid(5), then
appropriate prefix length for the IP address in this value will contain the LSPID of a tunnel of
object mplsTunnelHopIpAddr. Otherwise this value this hop. The present tunnel being configured is
is irrelevant and should be ignored. tunneled through this hop (using label stacking).
" This object is otherwise insignificant and should
DEFVAL { 32 } contain a value of 0 to indicate this fact."
::= { mplsTunnelHopEntry 6 } ::= { mplsTunnelHopEntry 9 }
mplsTunnelHopAsNumber OBJECT-TYPE mplsTunnelHopType OBJECT-TYPE
SYNTAX TeHopAddressAS SYNTAX INTEGER {
MAX-ACCESS read-create strict(1),
STATUS current loose(2)
DESCRIPTION }
"If mplsTunnelHopAddrType is set to asnumber(3), then MAX-ACCESS read-create
this value will contain the AS number of this hop. STATUS current
Otherwise the agent should set this object to zero- DESCRIPTION
length string and the manager should ignore this." "Denotes whether this tunnel hop is routed in a
::= { mplsTunnelHopEntry 7 } strict or loose fashion. The value of this object
has no meaning if the mplsTunnelHopInclude object
is set to 'false'."
::= { mplsTunnelHopEntry 10 }
mplsTunnelHopAddrUnnum OBJECT-TYPE mplsTunnelHopInclude OBJECT-TYPE
SYNTAX TeHopAddressUnnum SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is set to unnum(4), then "If this value is set to true, then this indicates
this value will contain the interface identifier of that this hop must be included in the tunnel's
the unnumbered interface for this hop. This object path. If this value is set to 'false', then this hop
should be used in conjunction with must be avoided when calculating the path for this
mplsTunnelHopIpAddress which would contain the LSR tunnel. The default value of this object is 'true',
Router ID in this case. Otherwise the agent should so that by default all indicated hops are included
set this object to zero-length string and the in the CSPF path computation. If this object is set
manager should ignore this." to 'false' the value of mplsTunnelHopType should be
::= { mplsTunnelHopEntry 8 } ignored."
DEFVAL { true }
::= { mplsTunnelHopEntry 11 }
mplsTunnelHopLspId OBJECT-TYPE mplsTunnelHopPathOptionName OBJECT-TYPE
SYNTAX MplsLSPID SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is set to lspid(5), then "The description of this series of hops as they
this value will contain the LSPID of a tunnel of relate to the specified path option. The
this hop. The present tunnel being configured is value of this object SHOULD be the same for
tunneled through this hop (using label stacking). each hop in the series that comprises a
This object is otherwise insignificant and should path option."
contain a value of 0 to indicate this fact." ::= { mplsTunnelHopEntry 12 }
::= { mplsTunnelHopEntry 9 }
mplsTunnelHopType OBJECT-TYPE mplsTunnelHopEntryPathComp OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
strict(1), dynamic(1), -- CSPF computed
loose(2) explicit(2) -- strict hop
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether this tunnel hop is routed in a "If this value is set to dynamic, then the user
strict or loose fashion. The value of this object should only specify the source and destination of
has no meaning if the mplsTunnelHopInclude object the path and expect that the CSPF will calculate
is set to 'false'." the remainder of the path. If this value is set to
::= { mplsTunnelHopEntry 10 } explicit, the user should specify the entire path
for the tunnel to take. This path may contain
strict or loose hops. Each hop along a specific
path SHOULD have this object set to the same value"
::= { mplsTunnelHopEntry 13 }
mplsTunnelHopInclude OBJECT-TYPE mplsTunnelHopRowStatus OBJECT-TYPE
SYNTAX TruthValue SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this value is set to true, then this indicates "This variable is used to create, modify, and/or
that this hop must be included in the tunnel's delete a row in this table. When a row in this
path. If this value is set to 'false', then this hop table is in active(1) state, no objects in that row
must be avoided when calculating the path for this can be modified by the agent except
tunnel. The default value of this object is 'true', mplsTunnelHopRowStatus and
so that by default all indicated hops are included mplsTunnelHopStorageType."
in the CSPF path computation. If this object is set ::= { mplsTunnelHopEntry 14 }
to 'false' the value of mplsTunnelHopType should be
ignored."
DEFVAL { true }
::= { mplsTunnelHopEntry 11 }
mplsTunnelHopPathOptionName OBJECT-TYPE mplsTunnelHopStorageType OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of this series of hops as they "The storage type for this Hop entry. Conceptual
relate to the specified path option. The rows having the value 'permanent' need not
value of this object SHOULD be the same for allow write-access to any columnar objects
each hop in the series that comprises a in the row."
path option." DEFVAL { volatile }
::= { mplsTunnelHopEntry 12 } ::= { mplsTunnelHopEntry 15 }
mplsTunnelHopEntryPathComp OBJECT-TYPE -- End of mplsTunnelHopTable
SYNTAX INTEGER {
dynamic(1), -- CSPF computed
explicit(2) -- strict hop
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If this value is set to dynamic, then the user
should only specify the source and destination of
the path and expect that the CSPF will calculate
the remainder of the path. If this value is set to
explicit, the user should specify the entire path
for the tunnel to take. This path may contain
strict or loose hops. Each hop along a specific
path SHOULD have this object set to the same value"
::= { mplsTunnelHopEntry 13 }
mplsTunnelHopRowStatus OBJECT-TYPE -- Begin of mplsTunnelResourceTable
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table. When a row in this
table is in active(1) state, no objects in that row
can be modified by the agent except
mplsTunnelHopRowStatus and
mplsTunnelHopStorageType."
::= { mplsTunnelHopEntry 14 }
mplsTunnelHopStorageType OBJECT-TYPE mplsTunnelResourceIndexNext OBJECT-TYPE
SYNTAX StorageType SYNTAX Unsigned32 (0.. 2147483647)
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this Hop entry. Conceptual "This object contains the next appropriate value to
rows having the value 'permanent' need not be used for mplsTunnelResourceIndex when creating
allow write-access to any columnar objects entries in the mplsTunnelResourceTable. If the
in the row." number of unassigned entries is exhausted, a
DEFVAL { volatile } retrieval operation will return a value of 0. This
::= { mplsTunnelHopEntry 15 } object may also return a value of 0 when the LSR is
unable to accept conceptual row creation, for
example, if the mplsTunnelTable is implemented as
read-only. To obtain the mplsTunnelResourceIndex
value for a new entry, the manager must first issue
a management protocol retrieval operation to obtain
the current value of this object.
When the SET is performed to create a row in the
mplsTunnelResourceTable, the Command Responder
(agent) must determine whether the value is indeed
still unused; Two Network Management Applications
may attempt to create a row (configuration entry)
simultaneously and use the same value. If it is
currently unused, the SET succeeds and the Command
Responder (agent) changes the value of this object,
according to an implementation-specific algorithm.
If the value is in use, however, the SET fails. The
Network Management Application must then re-read
this variable to obtain a new usable value."
::= { mplsTeObjects 5 }
mplsTunnelResourceTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelResourceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The mplsTunnelResourceTable allows a manager to
specify which resources are desired for an MPLS
tunnel. This table also allows several tunnels to
point to a single entry in this table, implying
that these tunnels should share resources."
::= { mplsTeObjects 6 }
mplsTunnelResourceIndexNext OBJECT-TYPE mplsTunnelResourceEntry OBJECT-TYPE
SYNTAX Unsigned32 (0.. 2147483647) SYNTAX MplsTunnelResourceEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the next appropriate value to "An entry in this table represents a set of resources
be used for mplsTunnelResourceIndex when creating for an MPLS tunnel. An entry can be created by a
entries in the mplsTunnelResourceTable. If the network administrator or by an SNMP agent as
number of unassigned entries is exhausted, a instructed by any MPLS signalling protocol.
retrieval operation will return a value of 0. This An entry in this table referenced by a tunnel instance
object may also return a value of 0 when the LSR is with zero mplsTunnelInstance value indicates a
unable to accept conceptual row creation, for configured set of resource parameter. An entry
example, if the mplsTunnelTable is implemented as referenced by a tunnel instance with a non-zero
read-only. To obtain the mplsTunnelResourceIndex mplsTunnelInstance reflects the in-use resource
value for a new entry, the manager must first issue parameters for the tunnel instance which may have
a management protocol retrieval operation to obtain been negotiated or modified by the MPLS signaling
the current value of this object. protocols."
INDEX { mplsTunnelResourceIndex }
::= { mplsTunnelResourceTable 1 }
When the SET is performed to create a row in the MplsTunnelResourceEntry ::= SEQUENCE {
mplsTunnelResourceTable, the Command Responder mplsTunnelResourceIndex Unsigned32,
(agent) must determine whether the value is indeed mplsTunnelResourceMaxRate MplsBitRate,
still unused; Two Network Management Applications mplsTunnelResourceMeanRate MplsBitRate,
may attempt to create a row (configuration entry) mplsTunnelResourceMaxBurstSize MplsBurstSize,
simultaneously and use the same value. If it is mplsTunnelResourceMeanBurstSize MplsBurstSize,
currently unused, the SET succeeds and the Command mplsTunnelResourceExBurstSize MplsBurstSize,
Responder (agent) changes the value of this object, mplsTunnelResourceFrequency INTEGER,
according to an implementation-specific algorithm. mplsTunnelResourceWeight Unsigned32,
If the value is in use, however, the SET fails. The mplsTunnelResourceRowStatus RowStatus,
Network Management Application must then re-read mplsTunnelResourceStorageType StorageType
this variable to obtain a new usable value." }
::= { mplsTeObjects 5 }
mplsTunnelResourceTable OBJECT-TYPE mplsTunnelResourceIndex OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelResourceEntry SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelResourceTable allows a manager to "Uniquely identifies this row."
specify which resources are desired for an MPLS ::= { mplsTunnelResourceEntry 1 }
tunnel. This table also allows several tunnels to
point to a single entry in this table, implying
that these tunnels should share resources."
::= { mplsTeObjects 6 }
mplsTunnelResourceEntry OBJECT-TYPE mplsTunnelResourceMaxRate OBJECT-TYPE
SYNTAX MplsTunnelResourceEntry SYNTAX MplsBitRate
MAX-ACCESS not-accessible UNITS "kilobits per second"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"An entry in this table represents a set of resources DESCRIPTION
for an MPLS tunnel. An entry can be created by a "The maximum rate in bits/second. Note that setting
network administrator or by an SNMP agent as mplsTunnelResourceMaxRate,
instructed by any MPLS signalling protocol. mplsTunnelResourceMeanRate, and
mplsTunnelResourceMaxBurstSize to 0 indicates best-
effort treatment."
::= { mplsTunnelResourceEntry 2 }
An entry in this table referenced by a tunnel instance mplsTunnelResourceMeanRate OBJECT-TYPE
with zero mplsTunnelInstance value indicates a SYNTAX MplsBitRate
configured set of resource parameter. An entry UNITS "kilobits per second"
referenced by a tunnel instance with a non-zero MAX-ACCESS read-create
mplsTunnelInstance reflects the in-use resource STATUS current
parameters for the tunnel instance which may have DESCRIPTION
been negotiated or modified by the MPLS signaling "This object is copied into an instance of
protocols." mplsTrafficParamMeanRate in the
INDEX { mplsTunnelResourceIndex } mplsTrafficParamTable. The OID of this table entry
::= { mplsTunnelResourceTable 1 } is then copied into the corresponding
mplsInSegmentTrafficParamPtr."
::= { mplsTunnelResourceEntry 3 }
MplsTunnelResourceEntry ::= SEQUENCE { mplsTunnelResourceMaxBurstSize OBJECT-TYPE
mplsTunnelResourceIndex Unsigned32, SYNTAX MplsBurstSize
mplsTunnelResourceMaxRate MplsBitRate, UNITS "bytes"
mplsTunnelResourceMeanRate MplsBitRate, MAX-ACCESS read-create
mplsTunnelResourceMaxBurstSize MplsBurstSize, STATUS current
mplsTunnelResourceMeanBurstSize MplsBurstSize, DESCRIPTION
mplsTunnelResourceExBurstSize MplsBurstSize, "The maximum burst size in bytes."
mplsTunnelResourceFrequency INTEGER, ::= { mplsTunnelResourceEntry 4 }
mplsTunnelResourceWeight Unsigned32,
mplsTunnelResourceRowStatus RowStatus,
mplsTunnelResourceStorageType StorageType
}
mplsTunnelResourceIndex OBJECT-TYPE mplsTunnelResourceMeanBurstSize OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX MplsBurstSize
MAX-ACCESS not-accessible UNITS "bytes"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"Uniquely identifies this row." DESCRIPTION
::= { mplsTunnelResourceEntry 1 } "The mean burst size in bytes. The implementations
which do not implement this variable must return
a noSuchObject exception for this object and must
not allow a user to set this object."
::= { mplsTunnelResourceEntry 5 }
mplsTunnelResourceMaxRate OBJECT-TYPE mplsTunnelResourceExBurstSize OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBurstSize
UNITS "kilobits per second" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate in bits/second. Note that setting "The Excess burst size in bytes. The implementations
mplsTunnelResourceMaxRate, which do not implement this variable must return
mplsTunnelResourceMeanRate, and noSuchObject exception for this object and must
mplsTunnelResourceMaxBurstSize to 0 indicates best- not allow a user to set this value."
effort treatment." REFERENCE
::= { mplsTunnelResourceEntry 2 } "CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 6 }
mplsTunnelResourceMeanRate OBJECT-TYPE mplsTunnelResourceFrequency OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX INTEGER { unspecified(1),
UNITS "kilobits per second" frequent(2),
MAX-ACCESS read-create veryFrequent(3)
STATUS current }
DESCRIPTION MAX-ACCESS read-create
"This object is copied into an instance of STATUS current
mplsTrafficParamMeanRate in the DESCRIPTION
mplsTrafficParamTable. The OID of this table entry "The granularity of the availability of committed
is then copied into the corresponding rate. The implementations which do not implement
mplsInSegmentTrafficParamPtr." this variable must return unspecified(1) for this
::= { mplsTunnelResourceEntry 3 } value and must not allow a user to set this value."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 7 }
mplsTunnelResourceMaxBurstSize OBJECT-TYPE mplsTunnelResourceWeight OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX Unsigned32(0..255)
UNITS "bytes" MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The relative weight for using excess bandwidth above
"The maximum burst size in bytes." its committed rate. The value of 0 means that
::= { mplsTunnelResourceEntry 4 } weight is not applicable for the CR-LSP."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 8 }
mplsTunnelResourceMeanBurstSize OBJECT-TYPE mplsTunnelResourceRowStatus OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX RowStatus
UNITS "bytes" MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This variable is used to create, modify, and/or
"The mean burst size in bytes. The implementations delete a row in this table. When a row in this
which do not implement this variable must return table is in active(1) state, no objects in that row
a noSuchObject exception for this object and must can be modified by the agent except
not allow a user to set this object." mplsTunnelResourceRowStatus and
::= { mplsTunnelResourceEntry 5 } mplsTunnelResourceStorageType."
::= { mplsTunnelResourceEntry 9 }
mplsTunnelResourceExBurstSize OBJECT-TYPE mplsTunnelResourceStorageType OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX StorageType
UNITS "bytes" MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The storage type for this Hop entry. Conceptual
"The Excess burst size in bytes. The implementations rows having the value 'permanent' need not
which do not implement this variable must return allow write-access to any columnar objects
noSuchObject exception for this object and must in the row."
not allow a user to set this value." DEFVAL { volatile }
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 6 }
mplsTunnelResourceFrequency OBJECT-TYPE ::= { mplsTunnelResourceEntry 10 }
SYNTAX INTEGER { unspecified(1),
frequent(2),
veryFrequent(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The granularity of the availability of committed
rate. The implementations which do not implement
this variable must return unspecified(1) for this
value and must not allow a user to set this value."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 7 }
mplsTunnelResourceWeight OBJECT-TYPE -- End mplsTunnelResourceTable
SYNTAX Unsigned32(0..255) -- Tunnel Actual Route Hop table.
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The relative weight for using excess bandwidth above
its committed rate. The value of 0 means that
weight is not applicable for the CR-LSP."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelResourceEntry 8 }
mplsTunnelResourceRowStatus OBJECT-TYPE mplsTunnelARHopTable OBJECT-TYPE
SYNTAX RowStatus SYNTAX SEQUENCE OF MplsTunnelARHopEntry
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "The mplsTunnelARHopTable is used to indicate the
delete a row in this table. When a row in this hops for an MPLS tunnel defined in mplsTunnelTable,
table is in active(1) state, no objects in that row as reported by the MPLS signalling protocol. Thus at
can be modified by the agent except a transit LSR, this table (if the table is supported
mplsTunnelResourceRowStatus and and if the signaling protocol is recording actual
mplsTunnelResourceStorageType." route information) contains the actual route of the
::= { mplsTunnelResourceEntry 9 } whole tunnel. If the signaling protocol is not
recording the actual route, this table MAY report
the information from the mplsTunnelHopTable or the
mplsTunnelCHopTable.
mplsTunnelResourceStorageType OBJECT-TYPE Each row in this table is indexed by
SYNTAX StorageType mplsTunnelARHopListIndex. Each row also has a
MAX-ACCESS read-create secondary index mplsTunnelARHopIndex, corresponding
STATUS current to the next hop that this row corresponds to.
DESCRIPTION
"The storage type for this Hop entry. Conceptual
rows having the value 'permanent' need not
allow write-access to any columnar objects
in the row."
DEFVAL { volatile }
::= { mplsTunnelResourceEntry 10 } Please note that since the information necessary to
build entries within this table is not provided by
some MPLS signalling protocols, implementation of
this table is optional. Furthermore, since the
information in this table is actually provided by
the MPLS signalling protocol after the path has
been set-up, the entries in this table are provided
only for observation, and hence, all variables in
this table are accessible exclusively as read-
only.
Note also that the contents of this table may change
while it is being read because of re-routing
activities. A network administrator may verify that
the actual route read is consistent by reference to
the mplsTunnelLastPathChange object."
::= { mplsTeObjects 7 }
mplsTunnelARHopTable OBJECT-TYPE mplsTunnelARHopEntry OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelARHopEntry SYNTAX MplsTunnelARHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelARHopTable is used to indicate the "An entry in this table represents a tunnel hop. An
hops for an MPLS tunnel defined in mplsTunnelTable, entry is created by the agent for signaled ERLSP
as reported by the MPLS signalling protocol. Thus at set up by an MPLS signalling protocol."
a transit LSR, this table (if the table is supported INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex }
and if the signaling protocol is recording actual ::= { mplsTunnelARHopTable 1 }
route information) contains the actual route of the
whole tunnel. If the signaling protocol is not
recording the actual route, this table MAY report
the information from the mplsTunnelHopTable or the
mplsTunnelCHopTable.
Each row in this table is indexed by MplsTunnelARHopEntry ::= SEQUENCE {
mplsTunnelARHopListIndex. Each row also has a mplsTunnelARHopListIndex MplsPathIndex,
secondary index mplsTunnelARHopIndex, corresponding mplsTunnelARHopIndex MplsPathIndex,
to the next hop that this row corresponds to. mplsTunnelARHopAddrType TeHopAddressType,
mplsTunnelARHopIpAddr TeHopAddress,
mplsTunnelARHopAddrUnnum TeHopAddressUnnum,
mplsTunnelARHopLspId MplsLSPID
}
Please note that since the information necessary to mplsTunnelARHopListIndex OBJECT-TYPE
build entries within this table is not provided by SYNTAX MplsPathIndex
some MPLS signalling protocols, implementation of MAX-ACCESS not-accessible
this table is optional. Furthermore, since the STATUS current
information in this table is actually provided by DESCRIPTION
the MPLS signalling protocol after the path has "Primary index into this table identifying a
been set-up, the entries in this table are provided particular recorded hop list."
only for observation, and hence, all variables in ::= { mplsTunnelARHopEntry 1 }
this table are accessible exclusively as read-
only.
Note also that the contencts of this table may change mplsTunnelARHopIndex OBJECT-TYPE
while it is being read because of re-routing SYNTAX MplsPathIndex
activities. A network administrator may verify that MAX-ACCESS not-accessible
the actual route read is consistent by reference to STATUS current
the mplsTunnelLastPathChange object." DESCRIPTION
::= { mplsTeObjects 7 } "Secondary index into this table identifying the
particular hop."
::= { mplsTunnelARHopEntry 2 }
mplsTunnelARHopEntry OBJECT-TYPE mplsTunnelARHopAddrType OBJECT-TYPE
SYNTAX MplsTunnelARHopEntry SYNTAX TeHopAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a tunnel hop. An "The Hop Address Type of this tunnel hop.
entry is created by the agent for signaled ERLSP
set up by an MPLS signalling protocol."
INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex }
::= { mplsTunnelARHopTable 1 }
MplsTunnelARHopEntry ::= SEQUENCE { Note that lspid(5) is a valid option only
mplsTunnelARHopListIndex MplsPathIndex, for tunnels signaled via CRLDP."
mplsTunnelARHopIndex MplsPathIndex, DEFVAL { ipv4 }
mplsTunnelARHopAddrType TeHopAddressType, ::= { mplsTunnelARHopEntry 3 }
mplsTunnelARHopIpAddr TeHopAddress,
mplsTunnelARHopAddrUnnum TeHopAddressUnnum,
mplsTunnelARHopLspId MplsLSPID
}
mplsTunnelARHopListIndex OBJECT-TYPE mplsTunnelARHopIpAddr OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX TeHopAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index into this table identifying a "The Tunnel Hop Address for this tunnel hop.
particular recorded hop list."
::= { mplsTunnelARHopEntry 1 }
mplsTunnelARHopIndex OBJECT-TYPE The type of this address is determined by the
SYNTAX MplsPathIndex value of the corresponding mplsTunnelARHopAddrType.
MAX-ACCESS not-accessible If mplsTunnelARHopAddrType is set to unnum(4),
STATUS current then this value contains the LSR Router ID of the
DESCRIPTION unnumbered interface. Otherwise the agent SHOULD
"Secondary index into this table identifying the set this object to the zero-length string and the
particular hop." manager should ignore this object."
::= { mplsTunnelARHopEntry 2 } DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0
::= { mplsTunnelARHopEntry 4 }
mplsTunnelARHopAddrType OBJECT-TYPE mplsTunnelARHopAddrUnnum OBJECT-TYPE
SYNTAX TeHopAddressType SYNTAX TeHopAddressUnnum
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Hop Address Type of this tunnel hop. "If mplsTunnelARHopAddrType is set to unnum(4), then
this value will contain the interface identifier of
the unnumbered interface for this hop. This object
should be used in conjunction with
mplsTunnelARHopIpAddr which would contain the LSR
Router ID in this case. Otherwise the agent should
set this object to zero-length string and the
manager should ignore this."
::= { mplsTunnelARHopEntry 5 }
Note that lspid(5) is a valid option only mplsTunnelARHopLspId OBJECT-TYPE
for tunnels signaled via CRLDP." SYNTAX MplsLSPID
DEFVAL { ipv4 } MAX-ACCESS read-only
::= { mplsTunnelARHopEntry 3 } STATUS current
DESCRIPTION
"If mplsTunnelARHopAddrType is set to lspid(5), then
this value will contain the LSP ID of this hop.
This object is otherwise insignificant and should
contain a value of 0 to indicate this fact."
::= { mplsTunnelARHopEntry 6 }
mplsTunnelARHopIpAddr OBJECT-TYPE -- End of mplsTunnelARHopTable
SYNTAX TeHopAddress -- Tunnel Computed Hop table.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Tunnel Hop Address for this tunnel hop.
The type of this address is determined by the mplsTunnelCHopTable OBJECT-TYPE
value of the corresponding mplsTunnelARHopAddrType. SYNTAX SEQUENCE OF MplsTunnelCHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The mplsTunnelCHopTable is used to indicate the
hops, strict or loose, for an MPLS tunnel defined
in mplsTunnelTable, as computed by a constraint-
based routing protocol, based on the
mplsTunnelHopTable for the outgoing direction of
the tunnel. Thus at a transit LSR, this table (if
the table is supported) MAY contain the path
computed by the CSPF engine on (or on behalf of)
this LSR. Each row in this table is indexed by
mplsTunnelCHopListIndex. Each row also has a
secondary index mplsTunnelCHopIndex, corresponding
to the next hop that this row corresponds to. In
case we want to specify a particular interface on
the originating LSR of an outgoing tunnel by which
we want packets to exit the LSR, we specify this as
the first hop for this tunnel in
mplsTunnelCHopTable.
If mplsTunnelARHopAddrType is set to unnum(4), Please note that since the information necessary to
then this value contains the LSR Router ID of the build entries within this table may not be
unnumbered interface. Otherwise the agent SHOULD supported by some LSRs, implementation of this
set this object to the zero-length string and the table is optional. Furthermore, since the
manager should ignore this object." information in this table describes the path
DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 computed by the CSPF engine the entries in this
::= { mplsTunnelARHopEntry 4 } table are read-only."
::= { mplsTeObjects 8 }
mplsTunnelARHopAddrUnnum OBJECT-TYPE mplsTunnelCHopEntry OBJECT-TYPE
SYNTAX TeHopAddressUnnum SYNTAX MplsTunnelCHopEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelARHopAddrType is set to unnum(4), then "An entry in this table represents a tunnel hop. An
this value will contain the interface identifier of entry in this table is created by a path
the unnumbered interface for this hop. This object computation engine using CSPF techniques applied to
should be used in conjunction with the information collected by routing protocols and
mplsTunnelARHopIpAddr which would contain the LSR the hops specified in the corresponding
Router ID in this case. Otherwise the agent should mplsTunnelHopTable."
set this object to zero-length string and the INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex }
manager should ignore this." ::= { mplsTunnelCHopTable 1 }
::= { mplsTunnelARHopEntry 5 }
mplsTunnelARHopLspId OBJECT-TYPE MplsTunnelCHopEntry ::= SEQUENCE {
SYNTAX MplsLSPID mplsTunnelCHopListIndex MplsPathIndex,
MAX-ACCESS read-only mplsTunnelCHopIndex MplsPathIndex,
STATUS current mplsTunnelCHopAddrType TeHopAddressType,
DESCRIPTION mplsTunnelCHopIpAddr TeHopAddress,
"If mplsTunnelARHopAddrType is set to lspid(5), then mplsTunnelCHopIpPrefixLen InetAddressPrefixLength,
this value will contain the LSP ID of this hop. mplsTunnelCHopAsNumber TeHopAddressAS,
This object is otherwise insignificant and should mplsTunnelCHopAddrUnnum TeHopAddressUnnum,
contain a value of 0 to indicate this fact." mplsTunnelCHopLspId MplsLSPID,
::= { mplsTunnelARHopEntry 6 } mplsTunnelCHopType INTEGER
}
mplsTunnelCHopListIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Primary index into this table identifying a
particular computed hop list."
::= { mplsTunnelCHopEntry 1 }
mplsTunnelCHopIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Secondary index into this table identifying the
particular hop."
::= { mplsTunnelCHopEntry 2 }
mplsTunnelCHopTable OBJECT-TYPE mplsTunnelCHopAddrType OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelCHopEntry SYNTAX TeHopAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelCHopTable is used to indicate the "The Hop Address Type of this tunnel hop.
hops, strict or loose, for an MPLS tunnel defined
in mplsTunnelTable, as computed by a constraint-
based routing protocol, based on the
mplsTunnelHopTable for the outgoing direction of
the tunnel. Thus at a transit LSR, this table (if
the table is supported) MAY contain the path
computed by the CSPF engine on (or on behalf of)
this LSR. Each row in this table is indexed by
mplsTunnelCHopListIndex. Each row also has a
secondary index mplsTunnelCHopIndex, corresponding
to the next hop that this row corresponds to. In
case we want to specify a particular interface on
the originating LSR of an outgoing tunnel by which
we want packets to exit the LSR, we specify this as
the first hop for this tunnel in
mplsTunnelCHopTable.
Please note that since the information necessary to Note that lspid(5) is a valid option only
build entries within this table may not be for tunnels signaled via CRLDP."
supported by some LSRs, implementation of this DEFVAL { ipv4 }
table is optional. Furthermore, since the ::= { mplsTunnelCHopEntry 3 }
information in this table describes the path
computed by the CSPF engine the entries in this
table are read-only."
::= { mplsTeObjects 8 }
mplsTunnelCHopEntry OBJECT-TYPE mplsTunnelCHopIpAddr OBJECT-TYPE
SYNTAX MplsTunnelCHopEntry SYNTAX TeHopAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a tunnel hop. An "The Tunnel Hop Address for this tunnel hop.
entry in this table is created by a path
computation engine using CSPF techniques applied to
the information collected by routing protocols and
the hops specified in the corresponding
mplsTunnelHopTable."
INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex }
::= { mplsTunnelCHopTable 1 }
MplsTunnelCHopEntry ::= SEQUENCE { The type of this address is determined by the
mplsTunnelCHopListIndex MplsPathIndex, value of the corresponding mplsTunnelCHopAddrType.
mplsTunnelCHopIndex MplsPathIndex,
mplsTunnelCHopAddrType TeHopAddressType,
mplsTunnelCHopIpAddr TeHopAddress,
mplsTunnelCHopIpPrefixLen InetAddressPrefixLength,
mplsTunnelCHopAsNumber TeHopAddressAS,
mplsTunnelCHopAddrUnnum TeHopAddressUnnum,
mplsTunnelCHopLspId MplsLSPID,
mplsTunnelCHopType INTEGER
}
mplsTunnelCHopListIndex OBJECT-TYPE If mplsTunnelCHopAddrType is set to unnum(4), then
SYNTAX MplsPathIndex this value will contain the LSR Router ID of the
MAX-ACCESS not-accessible unnumbered interface. Otherwise the agent should
STATUS current set this object to the zero-length string and the
DESCRIPTION manager SHOULD ignore this object."
"Primary index into this table identifying a DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0
particular computed hop list." ::= { mplsTunnelCHopEntry 4 }
::= { mplsTunnelCHopEntry 1 }
mplsTunnelCHopIndex OBJECT-TYPE mplsTunnelCHopIpPrefixLen OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Secondary index into this table identifying the "If mplsTunnelCHopAddrType is set to ipv4(1) or
particular hop." ipv6(2), then this value will contain an
::= { mplsTunnelCHopEntry 2 } appropriate prefix length for the IP address in
object mplsTunnelCHopIpAddr. Otherwise this value
is irrelevant and should be ignored.
"
DEFVAL { 32 }
::= { mplsTunnelCHopEntry 5 }
mplsTunnelCHopAddrType OBJECT-TYPE mplsTunnelCHopAsNumber OBJECT-TYPE
SYNTAX TeHopAddressType SYNTAX TeHopAddressAS
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Hop Address Type of this tunnel hop. "If mplsTunnelCHopAddrType is set to asnumber(3),
then this value will contain the AS number of this
hop. Otherwise the agent should set this object to
zero-length string and the manager should ignore
this."
::= { mplsTunnelCHopEntry 6 }
Note that lspid(5) is a valid option only mplsTunnelCHopAddrUnnum OBJECT-TYPE
for tunnels signaled via CRLDP." SYNTAX TeHopAddressUnnum
DEFVAL { ipv4 } MAX-ACCESS read-only
::= { mplsTunnelCHopEntry 3 } STATUS current
DESCRIPTION
"If mplsTunnelCHopAddrType is set to unnum(4), then
this value will contain the unnumbered interface
identifier of this hop. This object should be used
in conjunction with mplsTunnelCHopIpAddr which
would contain the LSR Router ID in this case.
mplsTunnelCHopIpAddr OBJECT-TYPE Otherwise the agent should set this object to zero-
SYNTAX TeHopAddress length string and the manager should ignore this."
MAX-ACCESS read-only ::= { mplsTunnelCHopEntry 7 }
STATUS current
DESCRIPTION
"The Tunnel Hop Address for this tunnel hop.
The type of this address is determined by the mplsTunnelCHopLspId OBJECT-TYPE
value of the corresponding mplsTunnelCHopAddrType. SYNTAX MplsLSPID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If mplsTunnelCHopAddrType is set to lspid(5), then
this value will contain the LSP ID of this hop.
This object is otherwise insignificant and should
contain a value of 0 to indicate this fact."
::= { mplsTunnelCHopEntry 8 }
If mplsTunnelCHopAddrType is set to unnum(4), then mplsTunnelCHopType OBJECT-TYPE
this value will contain the LSR Router ID of the SYNTAX INTEGER { strict(1),
unnumbered interface. Otherwise the agent should loose(2)
set this object to the zero-length string and the }
manager SHOULD ignore this object." MAX-ACCESS read-only
DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 STATUS current
::= { mplsTunnelCHopEntry 4 } DESCRIPTION
"Denotes whether this is tunnel hop is routed in a
strict or loose fashion."
::= { mplsTunnelCHopEntry 9 }
mplsTunnelCHopIpPrefixLen OBJECT-TYPE -- End of mplsTunnelCHopTable
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If mplsTunnelCHopAddrType is set to ipv4(1) or
ipv6(2), then this value will contain an
appropriate prefix length for the IP address in
object mplsTunnelCHopIpAddr. Otherwise this value
is irrelevant and should be ignored.
"
DEFVAL { 32 }
::= { mplsTunnelCHopEntry 5 }
mplsTunnelCHopAsNumber OBJECT-TYPE -- MPLS Tunnel Performance Table.
SYNTAX TeHopAddressAS
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If mplsTunnelCHopAddrType is set to asnumber(3),
then this value will contain the AS number of this
hop. Otherwise the agent should set this object to
zero-length string and the manager should ignore
this."
::= { mplsTunnelCHopEntry 6 }
mplsTunnelCHopAddrUnnum OBJECT-TYPE mplsTunnelPerfTable OBJECT-TYPE
SYNTAX TeHopAddressUnnum SYNTAX SEQUENCE OF MplsTunnelPerfEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelCHopAddrType is set to unnum(4), then "This table provides per-tunnel instance MPLS
this value will contain the unnumbered interface performance information."
identifier of this hop. This object should be used ::= { mplsTeObjects 9 }
in conjunction with mplsTunnelCHopIpAddr which
would contain the LSR Router ID in this case.
Otherwise the agent should set this object to zero-
length string and the manager should ignore this."
::= { mplsTunnelCHopEntry 7 }
mplsTunnelCHopLspId OBJECT-TYPE mplsTunnelPerfEntry OBJECT-TYPE
SYNTAX MplsLSPID SYNTAX MplsTunnelPerfEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelCHopAddrType is set to lspid(5), then "An entry in this table is created by the LSR for
this value will contain the LSP ID of this hop. every tunnel. Its is an extension to
This object is otherwise insignificant and should mplsTunnelEntry."
contain a value of 0 to indicate this fact."
::= { mplsTunnelCHopEntry 8 }
mplsTunnelCHopType OBJECT-TYPE AUGMENTS { mplsTunnelEntry }
SYNTAX INTEGER { strict(1), ::= { mplsTunnelPerfTable 1 }
loose(2)
} MplsTunnelPerfEntry ::= SEQUENCE {
MAX-ACCESS read-only mplsTunnelPerfPackets Counter32,
STATUS current mplsTunnelPerfHCPackets Counter64,
DESCRIPTION mplsTunnelPerfErrors Counter32,
"Denotes whether this is tunnel hop is routed in a mplsTunnelPerfBytes Counter32,
strict or loose fashion." mplsTunnelPerfHCBytes Counter64
::= { mplsTunnelCHopEntry 9 } }
mplsTunnelPerfPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of packets forwarded by the tunnel.
This object should represents the 32-bit
value of the least significant part of the
64-bit value if both mplsTunnelPerfHCPackets
is returned."
::= { mplsTunnelPerfEntry 1 }
mplsTunnelPerfHCPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High capacity counter for number of packets
forwarded by the tunnel. "
::= { mplsTunnelPerfEntry 2 }
mplsTunnelPerfTable OBJECT-TYPE mplsTunnelPerfErrors OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelPerfEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides per-tunnel instance MPLS "Number of packets dropped because of errors or for
performance information." other reasons."
::= { mplsTeObjects 9 } ::= { mplsTunnelPerfEntry 3 }
mplsTunnelPerfEntry OBJECT-TYPE mplsTunnelPerfBytes OBJECT-TYPE
SYNTAX MplsTunnelPerfEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for "Number of bytes forwarded by the tunnel.
every tunnel. Its is an extension to This object should represents the 32-bit
mplsTunnelEntry." value of the least significant part of the
AUGMENTS { mplsTunnelEntry } 64-bit value if both mplsTunnelPerfHCBytes
::= { mplsTunnelPerfTable 1 } is returned."
::= { mplsTunnelPerfEntry 4 }
MplsTunnelPerfEntry ::= SEQUENCE { mplsTunnelPerfHCBytes OBJECT-TYPE
mplsTunnelPerfPackets Counter32, SYNTAX Counter64
mplsTunnelPerfHCPackets Counter64, MAX-ACCESS read-only
mplsTunnelPerfErrors Counter32, STATUS current
mplsTunnelPerfBytes Counter32, DESCRIPTION
mplsTunnelPerfHCBytes Counter64 "High capacity counter for number of bytes forwarded
} by the tunnel."
::= { mplsTunnelPerfEntry 5 }
mplsTunnelPerfPackets OBJECT-TYPE -- End of mplsTunnelPerfTable
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of packets forwarded by the tunnel.
This object should represents the 32-bit
value of the least significant part of the
64-bit value if both mplsTunnelPerfHCPackets
is returned."
::= { mplsTunnelPerfEntry 1 }
mplsTunnelPerfHCPackets OBJECT-TYPE -- CR-LDP Tunnel Resource Table
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High capacity counter for number of packets
forwarded by the tunnel. "
::= { mplsTunnelPerfEntry 2 }
mplsTunnelPerfErrors OBJECT-TYPE mplsTunnelCRLDPResTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets dropped because of errors or for "The mplsTunnelCRLDPResTable allows a manager to
other reasons." specify which CR-LDP-specific resources are desired
::= { mplsTunnelPerfEntry 3 } for an MPLS tunnel if that tunnel is signaled using
CR-LDP. Note that these attributes are in addition
to those specified in mplsTunnelResourceTable. This
table also allows several tunnels to point to a
single entry in this table, implying that these
tunnels should share resources."
::= { mplsTeObjects 10 }
mplsTunnelPerfBytes OBJECT-TYPE mplsTunnelCRLDPResEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX MplsTunnelCRLDPResEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of bytes forwarded by the tunnel. "An entry in this table represents a set of resources
This object should represents the 32-bit for an MPLS tunnel established using CRLDP
value of the least significant part of the (mplsTunnelSignallingProto equal to crldp (3)). An
64-bit value if both mplsTunnelPerfHCBytes entry can be created by a network administrator or
is returned." by an SNMP agent as instructed by any MPLS
::= { mplsTunnelPerfEntry 4 } signalling protocol."
INDEX { mplsTunnelResourceIndex }
::= { mplsTunnelCRLDPResTable 1 }
mplsTunnelPerfHCBytes OBJECT-TYPE MplsTunnelCRLDPResEntry ::= SEQUENCE {
SYNTAX Counter64 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize,
MAX-ACCESS read-only mplsTunnelCRLDPResExBurstSize MplsBurstSize,
STATUS current mplsTunnelCRLDPResFrequency INTEGER,
DESCRIPTION mplsTunnelCRLDPResWeight Unsigned32,
"High capacity counter for number of bytes forwarded mplsTunnelCRLDPResFlags Unsigned32,
by the tunnel." mplsTunnelCRLDPResRowStatus RowStatus,
::= { mplsTunnelPerfEntry 5 } mplsTunnelCRLDPResStorageType StorageType
}
mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The mean burst size in bytes."
::= { mplsTunnelCRLDPResEntry 1 }
mplsTunnelCRLDPResExBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Excess burst size in bytes."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelCRLDPResEntry 2 }
mplsTunnelCRLDPResTable OBJECT-TYPE mplsTunnelCRLDPResFrequency OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible unspecified(1),
STATUS current frequent(2),
DESCRIPTION veryFrequent(3)
"The mplsTunnelCRLDPResTable allows a manager to }
specify which CR-LDP-specific resources are desired MAX-ACCESS read-create
for an MPLS tunnel if that tunnel is signaled using STATUS current
CR-LDP. Note that these attributes are in addition DESCRIPTION
to those specified in mplsTunnelResourceTable. This "The granularity of the availability of committed
table also allows several tunnels to point to a rate."
single entry in this table, implying that these REFERENCE
tunnels should share resources." "CR-LDP Specification, Section 4.3."
::= { mplsTeObjects 10 } ::= { mplsTunnelCRLDPResEntry 3 }
mplsTunnelCRLDPResEntry OBJECT-TYPE mplsTunnelCRLDPResWeight OBJECT-TYPE
SYNTAX MplsTunnelCRLDPResEntry SYNTAX Unsigned32(0..255)
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a set of resources "The relative weight for using excess bandwidth above
for an MPLS tunnel established using CRLDP its committed rate. The value of 0 means that
(mplsTunnelSignallingProto equal to crldp (3)). An weight is not applicable for the CR-LSP."
entry can be created by a network administrator or REFERENCE
by an SNMP agent as instructed by any MPLS "CR-LDP Specification, Section 4.3."
signalling protocol." DEFVAL { 0 }
INDEX { mplsTunnelResourceIndex } ::= { mplsTunnelCRLDPResEntry 4 }
::= { mplsTunnelCRLDPResTable 1 }
MplsTunnelCRLDPResEntry ::= SEQUENCE { mplsTunnelCRLDPResFlags OBJECT-TYPE
mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, SYNTAX Unsigned32 (0..63)
mplsTunnelCRLDPResExBurstSize MplsBurstSize, MAX-ACCESS read-create
mplsTunnelCRLDPResFrequency INTEGER, STATUS current
mplsTunnelCRLDPResWeight Unsigned32, DESCRIPTION
mplsTunnelCRLDPResFlags Unsigned32, "The value of the 1 byte Flags conveyed as part of
mplsTunnelCRLDPResRowStatus RowStatus, the traffic parameters during the establishment of
mplsTunnelCRLDPResStorageType StorageType the CRLSP. The bits in this object are to be
} interpreted as follows.
mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE +--+--+--+--+--+--+--+--+
SYNTAX MplsBurstSize | Res |F6|F5|F4|F3|F2|F1|
UNITS "bytes" +--+--+--+--+--+--+--+--+
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The mean burst size in bytes."
::= { mplsTunnelCRLDPResEntry 1 }
mplsTunnelCRLDPResExBurstSize OBJECT-TYPE Res - These bits are reserved. Zero on transmission.
SYNTAX MplsBurstSize Ignored on receipt.
UNITS "bytes" F1 - Corresponds to the PDR.
MAX-ACCESS read-create F2 - Corresponds to the PBS.
STATUS current F3 - Corresponds to the CDR.
DESCRIPTION F4 - Corresponds to the CBS.
"The Excess burst size in bytes." F5 - Corresponds to the EBS.
REFERENCE F6 - Corresponds to the Weight.
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelCRLDPResEntry 2 }
mplsTunnelCRLDPResFrequency OBJECT-TYPE Each flag if is a Negotiable Flag corresponding to a
SYNTAX INTEGER { Traffic Parameter. The Negotiable Flag value zero
unspecified(1), denotes Not Negotiable and value one denotes
frequent(2), Negotiable."
veryFrequent(3) REFERENCE
} "1. Section 4.3, Constraint-Based LSP Setup using
MAX-ACCESS read-create LDP, Jamoussi (Editor), RFC 3212, January 2002"
STATUS current DEFVAL { 0 }
DESCRIPTION ::= { mplsTunnelCRLDPResEntry 5 }
"The granularity of the availability of committed
rate."
REFERENCE
"CR-LDP Specification, Section 4.3."
::= { mplsTunnelCRLDPResEntry 3 }
mplsTunnelCRLDPResWeight OBJECT-TYPE mplsTunnelCRLDPResRowStatus OBJECT-TYPE
SYNTAX Unsigned32(0..255) SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The relative weight for using excess bandwidth above "This variable is used to create, modify, and/or
its committed rate. The value of 0 means that delete a row in this table. When a row in this
weight is not applicable for the CR-LSP." table is in active(1) state, no objects in that row
REFERENCE can be modified by the agent except
"CR-LDP Specification, Section 4.3." mplsTunnelCRLDPResRowStatus and
DEFVAL { 0 } mplsTunnelCRLDPResStorageType."
::= { mplsTunnelCRLDPResEntry 4 } ::= { mplsTunnelCRLDPResEntry 6 }
mplsTunnelCRLDPResFlags OBJECT-TYPE mplsTunnelCRLDPResStorageType OBJECT-TYPE
SYNTAX Unsigned32 (0..63) SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the 1 byte Flags conveyed as part of "The storage type for this CR-LDP Resource entry.
the traffic parameters during the establishment of Conceptual rows having the value 'permanent'
the CRLSP. The bits in this object are to be need not allow write-access to any columnar
interpreted as follows. objects in the row."
DEFVAL { volatile }
::= { mplsTunnelCRLDPResEntry 7 }
+--+--+--+--+--+--+--+--+ -- Notifications.
| Res |F6|F5|F4|F3|F2|F1|
+--+--+--+--+--+--+--+--+
Res - These bits are reserved. Zero on transmission. mplsTunnelNotificationEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, then it enables the
generation of mplsTunnelUp and mplsTunnelDown
traps, otherwise these traps are not emitted."
DEFVAL { false }
::= { mplsTeObjects 11 }
Ignored on receipt. mplsTunnelUp NOTIFICATION-TYPE
F1 - Corresponds to the PDR. OBJECTS {
F2 - Corresponds to the PBS. mplsTunnelAdminStatus,
F3 - Corresponds to the CDR. mplsTunnelOperStatus
F4 - Corresponds to the CBS. }
F5 - Corresponds to the EBS. STATUS current
F6 - Corresponds to the Weight. DESCRIPTION
"This notification is generated when a
mplsTunnelOperStatus object for one of the
configured tunnels is about to leave the down state
and transition into some other state (but not into
the notPresent state). This other state is
indicated by the included value of
mplsTunnelOperStatus."
Each flag if is a Negotiable Flag corresponding to a ::= { mplsTeNotifications 1 }
Traffic Parameter. The Negotiable Flag value zero
denotes Not Negotiable and value one denotes
Negotiable."
REFERENCE
"1. Section 4.3, Constraint-Based LSP Setup using
LDP, Jamoussi (Editor), RFC 3212, January 2002"
DEFVAL { 0 }
::= { mplsTunnelCRLDPResEntry 5 }
mplsTunnelCRLDPResRowStatus OBJECT-TYPE mplsTunnelDown NOTIFICATION-TYPE
SYNTAX RowStatus OBJECTS {
MAX-ACCESS read-create mplsTunnelAdminStatus,
STATUS current mplsTunnelOperStatus
DESCRIPTION }
"This variable is used to create, modify, and/or STATUS current
delete a row in this table. When a row in this DESCRIPTION
table is in active(1) state, no objects in that row "This notification is generated when a
can be modified by the agent except mplsTunnelOperStatus object for one of the
mplsTunnelCRLDPResRowStatus and configured tunnels is about to enter the down state
mplsTunnelCRLDPResStorageType." from some other state (but not from the notPresent
::= { mplsTunnelCRLDPResEntry 6 } state). This other state is indicated by the
included value of mplsTunnelOperStatus."
::= { mplsTeNotifications 2 }
mplsTunnelCRLDPResStorageType OBJECT-TYPE mplsTunnelRerouted NOTIFICATION-TYPE
SYNTAX StorageType OBJECTS {
MAX-ACCESS read-create mplsTunnelAdminStatus,
STATUS current mplsTunnelOperStatus
DESCRIPTION }
"The storage type for this CR-LDP Resource entry. STATUS current
Conceptual rows having the value 'permanent' DESCRIPTION
need not allow write-access to any columnar "This notification is generated when a tunnel is
objects in the row." rerouted. If the mplsTunnelARHopTable is used, then
DEFVAL { volatile } this tunnel instance's entry in the
::= { mplsTunnelCRLDPResEntry 7 } mplsTunnelARHopTable MAY contain the new path for
this tunnel some time after this trap is issued by
the agent."
::= { mplsTeNotifications 3 }
mplsTunnelReoptimized NOTIFICATION-TYPE
OBJECTS {
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a tunnel is
reoptimized. If the mplsTunnelARHopTable is used,
then this tunnel instance's entry in the
mplsTunnelARHopTable MAY contain the new path for
this tunnel some time after this trap is issued by
the agent."
::= { mplsTeNotifications 4 }
mplsTunnelNotificationEnable OBJECT-TYPE -- End of notifications.
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, then it enables the
generation of mplsTunnelUp and mplsTunnelDown
traps, otherwise these traps are not emitted."
DEFVAL { false }
::= { mplsTeObjects 11 }
mplsTunnelUp NOTIFICATION-TYPE -- Module compliance.
OBJECTS {
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a
mplsTunnelOperStatus object for one of the
configured tunnels is about to leave the down state
and transition into some other state (but not into
the notPresent state). This other state is
indicated by the included value of
mplsTunnelOperStatus."
::= { mplsTeNotifications 1 }
mplsTunnelDown NOTIFICATION-TYPE mplsTeGroups
OBJECTS { OBJECT IDENTIFIER ::= { mplsTeConformance 1 }
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a
mplsTunnelOperStatus object for one of the
configured tunnels is about to enter the down state
from some other state (but not from the notPresent
state). This other state is indicated by the
included value of mplsTunnelOperStatus."
::= { mplsTeNotifications 2 }
mplsTunnelRerouted NOTIFICATION-TYPE mplsTeCompliances
OBJECTS { OBJECT IDENTIFIER ::= { mplsTeConformance 2 }
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a tunnel is
rerouted. If the mplsTunnelARHopTable is used, then
this tunnel instance's entry in the
mplsTunnelARHopTable MAY contain the new path for
this tunnel some time after this trap is issued by
the agent."
::= { mplsTeNotifications 3 }
mplsTunnelReoptimized NOTIFICATION-TYPE -- Compliance requirement for fully compliant implementations.
OBJECTS {
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a tunnel is
reoptimized. If the mplsTunnelARHopTable is used,
then this tunnel instance's entry in the
mplsTunnelARHopTable MAY contain the new path for
this tunnel some time after this trap is issued by
the agent."
::= { mplsTeNotifications 4 }
mplsTeModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-TE-STD-MIB module."
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
mplsTeGroups MODULE -- this module
OBJECT IDENTIFIER ::= { mplsTeConformance 1 }
mplsTeCompliances -- The mandatory group has to be implemented by all
OBJECT IDENTIFIER ::= { mplsTeConformance 2 } -- LSRs that originate/terminate ESLSPs/tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS {
mplsTunnelGroup,
mplsTunnelScalarGroup
}
mplsTeModuleFullCompliance MODULE-COMPLIANCE GROUP mplsTunnelManualGroup
STATUS current DESCRIPTION
DESCRIPTION "This group is mandatory for devices which support
"Compliance statement for agents that provide full manual configuration of tunnels."
support the MPLS-TE-STD-MIB module."
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. GROUP mplsTunnelSignaledGroup
MANDATORY-GROUPS { DESCRIPTION
ifGeneralInformationGroup, "This group is mandatory for devices which support
ifCounterDiscontinuityGroup signaled tunnel set up."
}
MODULE -- this module GROUP mplsTunnelIsNotIntfcGroup
DESCRIPTION
"This group is mandatory for devices which support
tunnels that are not interfaces."
-- The mandatory group has to be implemented by all GROUP mplsTunnelIsIntfcGroup
-- LSRs that originate/terminate ESLSPs/tunnels. DESCRIPTION
-- In addition, depending on the type of tunnels "This group is mandatory for devices which support
-- supported, other groups become mandatory as tunnels that are interfaces."
-- explained below.
MANDATORY-GROUPS { GROUP mplsTunnelCRLDPResOptionalGroup
mplsTunnelGroup, DESCRIPTION
mplsTunnelScalarGroup "Objects in this group are required by
} implementations supporting the CR-LDP protocol for
signalling of TE tunnels."
GROUP mplsTunnelManualGroup GROUP mplsTeNotificationGroup
DESCRIPTION DESCRIPTION "This group is mandatory for those implementations
"This group is mandatory for devices which support which can implement the notifications
manual configuration of tunnels." contained in this group."
GROUP mplsTunnelSignaledGroup OBJECT mplsTunnelRowStatus
DESCRIPTION SYNTAX RowStatus { active(1), notInService(2) }
"This group is mandatory for devices which support WRITE-SYNTAX RowStatus { active(1), notInService(2),
signaled tunnel set up." createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required."
GROUP mplsTunnelIsNotIntfcGroup OBJECT mplsTunnelHopRowStatus
DESCRIPTION SYNTAX RowStatus { active(1), notInService(2) }
"This group is mandatory for devices which support WRITE-SYNTAX RowStatus { active(1), notInService(2),
tunnels that are not interfaces." createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not
required."
GROUP mplsTunnelIsIntfcGroup OBJECT mplsTunnelCRLDPResRowStatus
DESCRIPTION SYNTAX RowStatus { active(1), notInService(2) }
"This group is mandatory for devices which support WRITE-SYNTAX RowStatus { active(1), notInService(2),
tunnels that are interfaces." createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
GROUP mplsTunnelCRLDPResOptionalGroup ::= { mplsTeCompliances 1 }
DESCRIPTION
"Objects in this group are required by
implementations supporting the CR-LDP protocol for
signalling of TE tunnels."
GROUP mplsTeNotificationGroup -- Compliance requirement for read-only implementations.
DESCRIPTION "This group is mandatory for those implementations
which can implement the notifications
contained in this group."
OBJECT mplsTunnelRowStatus mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE
SYNTAX RowStatus { active(1), notInService(2) } STATUS current
WRITE-SYNTAX RowStatus { active(1), notInService(2), DESCRIPTION
createAndGo(4), destroy(6) "Compliance requirement for implementations that only
} provide read-only support for MPLS-TE-STD-MIB.
DESCRIPTION "Support for createAndWait and notReady is not Such devices can then be monitored but cannot be
required." configured using this MIB modules."
OBJECT mplsTunnelHopRowStatus MODULE -- this module
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is not -- mplsTunnelTable
required."
OBJECT mplsTunnelCRLDPResRowStatus MANDATORY-GROUPS {
SYNTAX RowStatus { active(1), notInService(2) } mplsTunnelGroup,
WRITE-SYNTAX RowStatus { active(1), notInService(2), mplsTunnelScalarGroup
createAndGo(4), destroy(6) }
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
::= { mplsTeCompliances 1 } GROUP mplsTunnelManualGroup
DESCRIPTION
"This group is mandatory for devices which support
manual configuration of tunnels."
GROUP mplsTunnelSignaledGroup
DESCRIPTION
"This group is mandatory for devices which support
signaled tunnel set up."
mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE GROUP mplsTunnelIsNotIntfcGroup
STATUS current DESCRIPTION
DESCRIPTION "This group is mandatory for devices which support
"Compliance requirement for implementations that only tunnels that are not interfaces."
provide read-only support for MPLS-TE-STD-MIB.
Such devices can then be monitored but cannot be
configured using this MIB modules."
MODULE -- this module GROUP mplsTunnelIsIntfcGroup
DESCRIPTION
"This group is mandatory for devices which support
tunnels that are interfaces."
-- mplsTunnelTable GROUP mplsTunnelCRLDPResOptionalGroup
DESCRIPTION
"Objects in this group are required by
implementations supporting the CR-LDP protocol for
signalling of TE tunnels."
MANDATORY-GROUPS { GROUP mplsTeNotificationGroup
mplsTunnelGroup, DESCRIPTION "This group is mandatory for those implementations
mplsTunnelScalarGroup which can implement the notifications
} contained in this group."
GROUP mplsTunnelManualGroup -- mplsTunnelTable
DESCRIPTION OBJECT mplsTunnelName
"This group is mandatory for devices which support MIN-ACCESS read-only
manual configuration of tunnels." DESCRIPTION
"Write access is not required."
GROUP mplsTunnelSignaledGroup OBJECT mplsTunnelDescr
DESCRIPTION MIN-ACCESS read-only
"This group is mandatory for devices which support DESCRIPTION
signaled tunnel set up." "Write access is not required."
GROUP mplsTunnelIsNotIntfcGroup OBJECT mplsTunnelIsIf
DESCRIPTION MIN-ACCESS read-only
"This group is mandatory for devices which support DESCRIPTION
tunnels that are not interfaces." "Write access is not required."
GROUP mplsTunnelIsIntfcGroup OBJECT mplsTunnelIfIndex
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "Write access is not required."
tunnels that are interfaces."
GROUP mplsTunnelCRLDPResOptionalGroup OBJECT mplsTunnelXCPointer
DESCRIPTION MIN-ACCESS read-only
"Objects in this group are required by DESCRIPTION
implementations supporting the CR-LDP protocol for "Write access is not required."
signalling of TE tunnels."
GROUP mplsTeNotificationGroup OBJECT mplsTunnelSignallingProto
DESCRIPTION "This group is mandatory for those implementations MIN-ACCESS read-only
which can implement the notifications DESCRIPTION
contained in this group." "Write access is not required."
-- mplsTunnelTable OBJECT mplsTunnelSetupPrio
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelName OBJECT mplsTunnelHoldingPrio
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelDescr OBJECT mplsTunnelSessionAttributes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelIsIf OBJECT mplsTunnelLocalProtectInUse
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelIfIndex OBJECT mplsTunnelResourcePointer
DESCRIPTION MIN-ACCESS read-only
"Write access is not required." DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelXCPointer OBJECT mplsTunnelInstancePriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSignallingProto OBJECT mplsTunnelHopTableIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSetupPrio OBJECT mplsTunnelIncludeAnyAffinity
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelHoldingPrio OBJECT mplsTunnelIncludeAllAffinity
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSessionAttributes OBJECT mplsTunnelExcludeAnyAffinity
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelLocalProtectInUse OBJECT mplsTunnelPathInUse
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelResourcePointer OBJECT mplsTunnelRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelInstancePriority OBJECT mplsTunnelAdminStatus
MIN-ACCESS read-only SYNTAX INTEGER { up (1), down (2) }
DESCRIPTION MIN-ACCESS read-only
"Write access is not required." DESCRIPTION
"Only up and down states must be supported. Write
access is not required."
OBJECT mplsTunnelHopTableIndex OBJECT mplsTunnelRowStatus
MIN-ACCESS read-only SYNTAX RowStatus { active(1) }
DESCRIPTION MIN-ACCESS read-only
"Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelIncludeAnyAffinity -- mplsTunnelHopTable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelIncludeAllAffinity OBJECT mplsTunnelHopAddrType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelExcludeAnyAffinity OBJECT mplsTunnelHopIpAddr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelPathInUse OBJECT mplsTunnelHopIpPrefixLen
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelRole OBJECT mplsTunnelHopAddrUnnum
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelAdminStatus OBJECT mplsTunnelHopAsNumber
SYNTAX INTEGER { up (1), down (2) } MIN-ACCESS read-only
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "Write access is not required."
"Only up and down states must be supported. Write
access is not required."
OBJECT mplsTunnelRowStatus OBJECT mplsTunnelHopLspId
SYNTAX RowStatus { active(1) } MIN-ACCESS read-only
MIN-ACCESS read-only DESCRIPTION
DESCRIPTION "Write access is not required." "Write access is not required."
-- mplsTunnelHopTable OBJECT mplsTunnelHopType
SYNTAX INTEGER { strict(1) }
MIN-ACCESS read-only
DESCRIPTION
"loose(2) need not be supported. Write access is
not required."
OBJECT mplsTunnelHopAddrType OBJECT mplsTunnelHopInclude
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopIpAddr OBJECT mplsTunnelHopPathOptionName
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopEntryPathComp
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopIpPrefixLen OBJECT mplsTunnelHopRowStatus
MIN-ACCESS read-only SYNTAX RowStatus { active(1) }
DESCRIPTION MIN-ACCESS read-only
"Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopAddrUnnum OBJECT mplsTunnelHopStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelHopAsNumber -- mplsTunnelResourceTable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelHopLspId OBJECT mplsTunnelResourceMaxRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelHopType OBJECT mplsTunnelResourceMeanRate
SYNTAX INTEGER { strict(1) } MIN-ACCESS read-only
MIN-ACCESS read-only DESCRIPTION "Write access is not required."
DESCRIPTION
"loose(2) need not be supported. Write access is
not required."
OBJECT mplsTunnelHopInclude OBJECT mplsTunnelResourceMaxBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopPathOptionName OBJECT mplsTunnelResourceMeanBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopEntryPathComp OBJECT mplsTunnelResourceExBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelHopRowStatus OBJECT mplsTunnelResourceFrequency
SYNTAX RowStatus { active(1) } MIN-ACCESS read-only
MIN-ACCESS read-only DESCRIPTION "Write access is not required."
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelHopStorageType OBJECT mplsTunnelResourceWeight
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
-- mplsTunnelResourceTable OBJECT mplsTunnelResourceRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceMaxRate -- mplsTunnelCRLDPResTable
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceMeanRate OBJECT mplsTunnelCRLDPResMeanBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceMaxBurstSize OBJECT mplsTunnelCRLDPResExBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceMeanBurstSize OBJECT mplsTunnelCRLDPResFrequency
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceExBurstSize OBJECT mplsTunnelCRLDPResWeight
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION "Write access is not required."
"Write access is not required."
OBJECT mplsTunnelResourceFrequency OBJECT mplsTunnelCRLDPResFlags
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceWeight
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceRowStatus OBJECT mplsTunnelCRLDPResRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsTunnelResourceStorageType OBJECT mplsTunnelCRLDPResStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
-- mplsTunnelCRLDPResTable ::= { mplsTeCompliances 2 }
OBJECT mplsTunnelCRLDPResMeanBurstSize -- Units of conformance.
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT mplsTunnelCRLDPResExBurstSize mplsTunnelGroup OBJECT-GROUP
MIN-ACCESS read-only OBJECTS {
DESCRIPTION "Write access is not required." mplsTunnelIndexNext,
mplsTunnelName,
mplsTunnelDescr,
mplsTunnelOwner,
mplsTunnelXCPointer,
mplsTunnelIfIndex,
mplsTunnelHopTableIndex,
mplsTunnelARHopTableIndex,
mplsTunnelCHopTableIndex,
mplsTunnelAdminStatus,
mplsTunnelOperStatus,
mplsTunnelRowStatus,
mplsTunnelNotificationEnable,
mplsTunnelStorageType,
mplsTunnelConfigured,
mplsTunnelActive,
mplsTunnelPrimaryInstance,
mplsTunnelPrimaryUpTime,
mplsTunnelPathChanges,
mplsTunnelLastPathChange,
mplsTunnelCreationTime,
mplsTunnelStateTransitions,
mplsTunnelIncludeAnyAffinity,
mplsTunnelIncludeAllAffinity,
mplsTunnelExcludeAnyAffinity,
mplsTunnelPerfPackets,
mplsTunnelPerfHCPackets,
mplsTunnelPerfErrors,
mplsTunnelPerfBytes,
mplsTunnelPerfHCBytes,
mplsTunnelResourcePointer,
mplsTunnelInstancePriority,
mplsTunnelPathInUse,
mplsTunnelRole,
mplsTunnelTotalUpTime,
mplsTunnelInstanceUpTime,
mplsTunnelResourceIndexNext,
mplsTunnelResourceMaxRate,
mplsTunnelResourceMeanRate,
mplsTunnelResourceMaxBurstSize,
mplsTunnelResourceMeanBurstSize,
mplsTunnelResourceExBurstSize,
mplsTunnelResourceFrequency,
mplsTunnelResourceWeight,
mplsTunnelResourceRowStatus,
mplsTunnelResourceStorageType,
mplsTunnelARHopAddrType,
mplsTunnelARHopIpAddr,
mplsTunnelARHopAddrUnnum,
mplsTunnelARHopLspId,
mplsTunnelCHopAddrType,
mplsTunnelCHopIpAddr,
mplsTunnelCHopIpPrefixLen,
mplsTunnelCHopAsNumber,
mplsTunnelCHopAddrUnnum,
mplsTunnelCHopLspId,
mplsTunnelCHopType
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the
type of the tunnels supported (for example,
manually configured or signaled, persistent or non-
persistent, etc.), the following other groups
defined below are mandatory: mplsTunnelManualGroup
and/or mplsTunnelSignaledGroup,
mplsTunnelIsNotIntfcGroup and/or
mplsTunnelIsIntfcGroup."
::= { mplsTeGroups 1 }
OBJECT mplsTunnelCRLDPResFrequency mplsTunnelManualGroup OBJECT-GROUP
MIN-ACCESS read-only OBJECTS { mplsTunnelSignallingProto }
DESCRIPTION "Write access is not required." STATUS current
DESCRIPTION
"Object(s) needed to implement manually configured
tunnels."
::= { mplsTeGroups 2 }
OBJECT mplsTunnelCRLDPResWeight mplsTunnelSignaledGroup OBJECT-GROUP
MIN-ACCESS read-only OBJECTS {
DESCRIPTION "Write access is not required." mplsTunnelSetupPrio,
mplsTunnelHoldingPrio,
mplsTunnelSignallingProto,
mplsTunnelLocalProtectInUse,
mplsTunnelSessionAttributes,
mplsTunnelHopListIndexNext,
mplsTunnelHopAddrType,
mplsTunnelHopIpAddr,
mplsTunnelHopIpPrefixLen,
mplsTunnelHopAddrUnnum,
mplsTunnelHopAsNumber,
mplsTunnelHopLspId,
mplsTunnelHopType,
mplsTunnelHopInclude,
mplsTunnelHopPathOptionName,
mplsTunnelHopEntryPathComp,
mplsTunnelHopRowStatus,
mplsTunnelHopStorageType
}
STATUS current
DESCRIPTION
"Objects needed to implement signaled tunnels."
::= { mplsTeGroups 3 }
OBJECT mplsTunnelCRLDPResFlags mplsTunnelScalarGroup OBJECT-GROUP
MIN-ACCESS read-only OBJECTS {
DESCRIPTION "Write access is not required." mplsTunnelConfigured,
mplsTunnelActive,
mplsTunnelTEDistProto,
mplsTunnelMaxHops,
mplsTunnelNotificationMaxRate
}
STATUS current
DESCRIPTION
"Scalar object needed to implement MPLS tunnels."
::= { mplsTeGroups 4 }
OBJECT mplsTunnelCRLDPResRowStatus mplsTunnelIsIntfcGroup OBJECT-GROUP
SYNTAX RowStatus { active(1) } OBJECTS { mplsTunnelIsIf }
MIN-ACCESS read-only STATUS current
DESCRIPTION "Write access is not required." DESCRIPTION
"Objects needed to implement tunnels that are
interfaces."
::= { mplsTeGroups 5 }
OBJECT mplsTunnelCRLDPResStorageType mplsTunnelIsNotIntfcGroup OBJECT-GROUP
MIN-ACCESS read-only OBJECTS { mplsTunnelIsIf }
DESCRIPTION "Write access is not required." STATUS current
DESCRIPTION
"Objects needed to implement tunnels that are not
interfaces."
::= { mplsTeGroups 6 }
::= { mplsTeCompliances 2 } mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP
OBJECTS {
mplsTunnelCRLDPResMeanBurstSize,
mplsTunnelCRLDPResExBurstSize,
mplsTunnelCRLDPResFrequency,
mplsTunnelCRLDPResWeight,
mplsTunnelCRLDPResFlags,
mplsTunnelCRLDPResRowStatus,
mplsTunnelCRLDPResStorageType
}
STATUS current
DESCRIPTION
"Set of objects implemented for resources applicable
for tunnels signaled using CR-LDP."
::= { mplsTeGroups 7 }
mplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mplsTunnelUp,
mplsTunnelDown,
mplsTunnelRerouted,
mplsTunnelReoptimized
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module.
None is mandatory."
::= { mplsTeGroups 8 }
mplsTunnelGroup OBJECT-GROUP END
OBJECTS {
mplsTunnelIndexNext,
mplsTunnelName,
mplsTunnelDescr,
mplsTunnelOwner,
mplsTunnelXCPointer,
mplsTunnelIfIndex,
mplsTunnelHopTableIndex,
mplsTunnelARHopTableIndex,
mplsTunnelCHopTableIndex,
mplsTunnelAdminStatus,
mplsTunnelOperStatus,
mplsTunnelRowStatus,
mplsTunnelNotificationEnable,
mplsTunnelStorageType,
mplsTunnelConfigured,
mplsTunnelActive,
mplsTunnelPrimaryInstance,
mplsTunnelPrimaryUpTime,
mplsTunnelPathChanges,
mplsTunnelLastPathChange,
mplsTunnelCreationTime,
mplsTunnelStateTransitions,
mplsTunnelIncludeAnyAffinity,
mplsTunnelIncludeAllAffinity,
mplsTunnelExcludeAnyAffinity,
mplsTunnelPerfPackets,
mplsTunnelPerfHCPackets,
mplsTunnelPerfErrors,
mplsTunnelPerfBytes,
mplsTunnelPerfHCBytes,
mplsTunnelResourcePointer,
mplsTunnelInstancePriority,
mplsTunnelPathInUse,
mplsTunnelRole,
mplsTunnelTotalUpTime,
mplsTunnelInstanceUpTime,
mplsTunnelResourceIndexNext,
mplsTunnelResourceMaxRate,
mplsTunnelResourceMeanRate,
mplsTunnelResourceMaxBurstSize,
mplsTunnelResourceMeanBurstSize,
mplsTunnelResourceExBurstSize,
mplsTunnelResourceFrequency,
mplsTunnelResourceWeight,
mplsTunnelResourceRowStatus,
mplsTunnelResourceStorageType,
mplsTunnelARHopAddrType,
mplsTunnelARHopIpAddr,
mplsTunnelARHopAddrUnnum,
mplsTunnelARHopLspId,
mplsTunnelCHopAddrType,
mplsTunnelCHopIpAddr,
mplsTunnelCHopIpPrefixLen,
mplsTunnelCHopAsNumber,
mplsTunnelCHopAddrUnnum,
mplsTunnelCHopLspId,
mplsTunnelCHopType
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the
type of the tunnels supported (for example,
manually configured or signaled, persistent or non-
persistent, etc.), the following other groups
defined below are mandatory: mplsTunnelManualGroup
and/or mplsTunnelSignaledGroup,
mplsTunnelIsNotIntfcGroup and/or
mplsTunnelIsIntfcGroup."
::= { mplsTeGroups 1 }
mplsTunnelManualGroup OBJECT-GROUP 12. Security Considerations
OBJECTS { mplsTunnelSignallingProto }
STATUS current
DESCRIPTION
"Object(s) needed to implement manually configured
tunnels."
::= { mplsTeGroups 2 }
mplsTunnelSignaledGroup OBJECT-GROUP It is clear that this MIB module is potentially useful for the
OBJECTS { monitoring of MPLS TE tunnels. This MIB module can also be used for
mplsTunnelSetupPrio, the configuration of certain objects, and anything that can be
mplsTunnelHoldingPrio, configured can be incorrectly configured, with potentially disastrous
mplsTunnelSignallingProto, results.
mplsTunnelLocalProtectInUse,
mplsTunnelSessionAttributes,
mplsTunnelHopListIndexNext,
mplsTunnelHopAddrType,
mplsTunnelHopIpAddr,
mplsTunnelHopIpPrefixLen,
mplsTunnelHopAddrUnnum,
mplsTunnelHopAsNumber,
mplsTunnelHopLspId,
mplsTunnelHopType,
mplsTunnelHopInclude,
mplsTunnelHopPathOptionName,
mplsTunnelHopEntryPathComp,
mplsTunnelHopRowStatus,
mplsTunnelHopStorageType
}
STATUS current
DESCRIPTION
"Objects needed to implement signaled tunnels."
::= { mplsTeGroups 3 }
mplsTunnelScalarGroup OBJECT-GROUP There are a number of management objects defined in this MIB module
OBJECTS { with a MAX-ACCESS clause of read-write and/or read-create. Such
mplsTunnelConfigured, objects may be considered sensitive or vulnerable in some network
mplsTunnelActive, environments. The support for SET operations in a non-secure
mplsTunnelTEDistProto, environment without proper protection can have a negative effect on
mplsTunnelMaxHops, network operations. These are the tables and objects and their
mplsTunnelNotificationMaxRate sensitivity/vulnerability:
}
STATUS current
DESCRIPTION
"Scalar object needed to implement MPLS tunnels."
::= { mplsTeGroups 4 }
mplsTunnelIsIntfcGroup OBJECT-GROUP - the mplsTunnelTable, mplsTunnelHopTable, mplsTunnelResourceTable,
OBJECTS { mplsTunnelIsIf } and mplsTunnelCRLDPResTable collectively contain objects to
STATUS current provision MPLS tunnels, tunnel hops, and tunnel resources.
DESCRIPTION Unauthorized access to objects in these tables, could result in
"Objects needed to implement tunnels that are disruption of traffic on the network. This is especially true if
interfaces." a tunnel has been established. The use of stronger mechanisms,
::= { mplsTeGroups 5 } such as SNMPv3 security, should be considered where possible.
Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent
which implements this MIB. Administrators should consider whether
read access to these objects should be allowed, since read access
may be undesirable under certain circumstances.
mplsTunnelIsNotIntfcGroup OBJECT-GROUP Some of the readable objects in this MIB module (i.e., objects with a
OBJECTS { mplsTunnelIsIf } MAX-ACCESS other than not-accessible) may be considered sensitive or
STATUS current vulnerable in some network environments. It is thus important to
DESCRIPTION control even GET and/or NOTIFY access to these objects and possibly
"Objects needed to implement tunnels that are not to even encrypt the values of these objects when sending them over
interfaces." the network via SNMP. These are the tables and objects and their
::= { mplsTeGroups 6 } sensitivity/vulnerability:
mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP - the mplsTunnelTable, mplsTunnelHopTable, mplsTunnelResourceTable,
OBJECTS { mplsTunnelARHopTable, mplsTunnelCHopTable, mplsTunnelPerfTable,
mplsTunnelCRLDPResMeanBurstSize, and mplsTunnelCRLDPResTable collectively show the MPLS-TE tunnel
mplsTunnelCRLDPResExBurstSize, network topology and its performance characteristics. If an
mplsTunnelCRLDPResFrequency, Administrator does not want to reveal this information, then these
mplsTunnelCRLDPResWeight, tables should be considered sensitive/vulnerable.
mplsTunnelCRLDPResFlags,
mplsTunnelCRLDPResRowStatus,
mplsTunnelCRLDPResStorageType
}
STATUS current
DESCRIPTION
"Set of objects implemented for resources applicable
for tunnels signaled using CR-LDP."
::= { mplsTeGroups 7 } SNMP versions prior to SNMPv3 did not include adequate security.
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 to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
mplsTeNotificationGroup NOTIFICATION-GROUP It is RECOMMENDED that implementers consider the security features as
NOTIFICATIONS { provided by the SNMPv3 framework (see [RFC3410], section 8),
mplsTunnelUp, including full support for the SNMPv3 cryptographic mechanisms (for
mplsTunnelDown, authentication and privacy).
mplsTunnelRerouted,
mplsTunnelReoptimized
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module.
None is mandatory."
::= { mplsTeGroups 8 }
END Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED that SNMPv3 be deployed and
cryptographic security enabled. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
only those principals (users) that have legitimate rights to those
objects.
12. Security Considerations 13. Acknowledgments
It is clear that this MIB module is potentially useful for We wish to thank Adrian Farrel, Bert Wijnen, Eric Gray, Joan
monitoring of MPLS TE tunnels. This MIB module can also Cucchiara, Patrick Kerharo, Paul Langille, Marcus Brunner, Mike
be used for configuration of certain objects, and anything MacFaden, and Mike Piecuch for their comments on this document.
that can be configured can be incorrectly configured, with
potentially disastrous results.
There are a number of management objects defined in this Comments should be made directly to the MPLS mailing list at
MIB module with a MAX-ACCESS clause of read-write and/or mpls@uu.net.
read-create. Such objects may be considered sensitive or
vulnerable in some network environments. The support for
SET operations in a non-secure environment without proper
protection can have a negative effect on network
operations. These are the tables and objects and their
sensitivity/vulnerability:
- the mplsTunnelTable, mplsTunnelHopTable, 14. IANA Considerations
mplsTunnelResourceTable, and
mplsTunnelCRLDPResTable collectively contain
objects to provision MPLS tunnels, tunnel hops, and
tunnel resources. Unauthorized access to objects
in these tables, could result in disruption of
traffic on the network. This is especially true if
a tunnel has been established. The use of stronger
mechanisms such as SNMPv3 security should be
considered where possible. Specifically, SNMPv3
VACM and USM MUST be used with any v3 agent which
implements this MIB. Administrators should
consider whether read access to these objects
should be allowed, since read access may be
undesirable under certain circumstances.
Some of the readable objects in this MIB module "i.e., As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
objects with a MAX-ACCESS other than not-accessible" may [RFC3811], MPLS related standards track MIB modules should be rooted
be considered sensitive or vulnerable in some network under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained
environments. It is thus important to control even GET in this document, each of the following "IANA Considerations"
and/or NOTIFY access to these objects and possibly to even subsections requests IANA for a new assignment under the mplsStdMIB
encrypt the values of these objects when sending them over subtree. New assignments can only be made via a Standards Action as
the network via SNMP. These are the tables and objects specified in [RFC2434].
and their sensitivity/vulnerability:
- the mplsTunnelTable, mplsTunnelHopTable, 14.1. IANA Considerations for MPLS-TE-STD-MIB
mplsTunnelResourceTable, mplsTunnelARHopTable,
mplsTunnelCHopTable, mplsTunnelPerfTable, and
mplsTunnelCRLDPResTable collectively show the MPLE-
TE tunnel network topology and its performance
characteristics. If an Administrator does not want
to reveal this information, then these tables
should be considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate The IANA has assigned { mplsStdMIB 3 } to the MPLS-TE-STD-MIB module
security. Even if the network itself is secure "for specified in this document.
example by using IPSec", even 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 this
MIB module.
It is RECOMMENDED that implementers consider the security 15. References
features as 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 15.1. Normative References
NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy
SNMPv3 and to enable cryptographic security. It is then a
customer/operator responsibility to ensure that the SNMP
entity giving access to an instance of this MIB module, is
properly configured to give access to the objects only to
those principals "users" that have legitimate.
13. Acknowledgments [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
We wish to thank Adrian Farrel, Bert Wijnen, Eric Gray, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Joan Cucchiara, Patrick Kerharo, Paul Langille, Marcus "Structure of Management Information Version 2 (SMIv2)",
Brunner, Mike MacFaden and Mike Piecuch for their comments STD 58, RFC 2578, April 1999.
on this document.
14. References [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
14.1. Normative References "Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC2119] S. Bradner, "Key Words for use in RFCs to [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Indicate Requirement Levels", RFC 2119, BCP "Conformance Statements for SMIv2", STD 58, RFC 2580,
14, March 1997. April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
J., Case, J., Rose, M., and S. Waldbusser, McManus, "Requirements for Traffic Engineering Over MPLS",
"Structure of Management Information Version RFC 2702, September 1999.
2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group
J., Case, J., Rose, M., and S. Waldbusser, MIB ", RFC 2863, June 2000.
"Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
J., Case, J., Rose, M., and S. Waldbusser, Label Switching Architecture", RFC 3031, January 2001.
"Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
O'Dell, M., and J. McManus, "Requirements and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
for Traffic Engineering Over MPLS", RFC Tunnels", RFC 3209, December 2001.
2702, September 1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The [RFC3212] Jamoussi, B., Ed., Andersson, L., Callon, R, Dantu, R.,
Interfaces Group MIB ", RFC 2863, June 2000. Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette,
A., Girish, M., Gray, E., Heinanen, J., Kilty, T., and A.
Malis, "Constraint-Based LSP Setup using LDP", RFC 3212,
January 2002.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information
"Multiprotocol Label Switching Base for the Differentiated Services Architecture", RFC
Architecture", RFC 3031, January 2001. 3289, May 2002.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Srinivasan, V., and G. Swallow, "RSVP-TE: Schoenwaelder, "TextualConventions for Internet Network
Extensions to RSVP for LSP Tunnels", RFC Addresses", RFC 3291, May 2002.
3209, December 2001.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
J. Schoenwaelder, "Textual Conventions for Architecture for Describing Simple Network Management
Internet Network Addresses", RFC 3291, May Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
"An Architecture for Describing Simple Conventions and for Multiprotocol Label Switching (MPLS)
Network Management Protocol (SNMP) Management", RFC 3811, June 2004.
Management Frameworks", RFC 3411, December
2002.
[TCMIB] Nadeau, T. and J. Cucchiara (Editors), [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Definition of Textual Conventions and "Multiprotocol Label Switching (MPLS) Label Switching
OBJECT-IDENTITIES for Multi-Protocol Label (LSR) Router Management Information Base (MIB)", RFC 3813,
Switching (MPLS) Management", Internet Draft June 2004.
<draft-ietf-mpls-tc-mib-08.txt>, June 2003.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. 15.2. Informative References
Nadeau, "MPLS Multiprotocol Label Switching
(MPLS) Label Switch Router Management
Information Base ", Internet Draft <draft-
ietf-mpls-lsr-mib-14.txt>, November 2003.
[CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Setup using LDP", RFC 3212, January 2002. Label Switching (MPLS) Management Overview", Work in
Progress, September 2003.
14.2. Informative References [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2026] S. Bradner, "The Internet Standards Process [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
-- Revision 3", RFC 2026, October 1996. "Introduction and Applicability Statement for Internet
Standard Management Framework", RFC 3410, December 2002.
[RFC2401] Kent, S., and R. Atkinson, "Security 16. Authors' Addresses
Architecture for the Internet Protocol", RFC
2401, November 1998.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Cheenu Srinivasan
Stewart, "Introduction and Applicability Bloomberg L.P.
Statement for Internet Standard Management 499 Park Ave., New York, NY 10022
Framework", RFC 3410, December 2002.
15. Authors' Addresses Phone: +1-212-893-3682
EMail: cheenu@bloomberg.net
Cheenu Srinivasan Arun Viswanathan
Bloomberg L.P. Force10 Networks, Inc.
499 Park Ave., New York, NY 10022 1440 McCarthy Blvd
Phone: +1-212-893-3682 Milpitas, CA 95035
Email: cheenu@bloomberg.net
Arun Viswanathan Phone: +1-408-571-3516
Force10 Networks, Inc. EMail: arunv@force10networks.com
1440 McCarthy Blvd
Milpitas, CA 95035
Phone: +1-408-571-3516
Email: arunv@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
16. Full Copyright Statement Phone: +1-978-244-3051
EMail: tnadeau@cisco.com
Copyright (C) The Internet Society (2003). All Rights 17. Full Copyright Statement
Reserved.
This document and translations of it may be copied and Copyright (C) The Internet Society (2004). This document is subject
furnished to others, and derivative works that comment on to the rights, licenses and restrictions contained in BCP 78, and
or otherwise explain it or assist in its implementation may except as set forth therein, the authors retain all their rights.
be prepared, copied, published and distributed, in whole or
in part, without restriction of any kind, provided that the
above copyright notice and this paragraph are included on
all such copies and derivative works. However, this
document itself may not be modified in any way, such as by
removing the copyright notice or references to the Internet
Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which
case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to
translate it into languages other than English.
The limited permissions granted above are perpetual and This document and the information contained herein are provided on an
will not be revoked by the Internet Society or its "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
successors or assigns. This document and the information REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
contained herein is provided on an "AS IS" basis and THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
17. Intellectual Property Notice Intellectual Property
The IETF takes no position regarding the validity or scope The IETF takes no position regarding the validity or scope of any
of any intellectual property or other rights that might be Intellectual Property Rights or other rights that might be claimed
claimed to pertain to the implementation or use of the to pertain to the implementation or use of the technology
technology described in this document or the extent to described in this document or the extent to which any license
which any license under such rights might or might not be under such rights might or might not be available; nor does it
available; neither does it represent that it has made any represent that it has made any independent effort to identify any
effort to identify any such rights. Information on the such rights. Information on the procedures with respect to
IETF's procedures with respect to rights in standards-track rights in RFC documents can be found in BCP 78 and BCP 79.
and standards-related documentation can be found in BCP-11
[RFC2028]. Copies of claims of rights made available for
publication and any assurances of licenses to be made
available, or the result of an attempt made to obtain a
general license or permission for the use of such
proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its
attention any copyrights, patents or patent applications,
or other proprietary rights that may cover technology that
may be required to practice this standard. Please address
the information to the IETF Executive Director.
18. IANA Considerations Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB The IETF invites any interested party to bring to its attention
[MPLSTCMIB], MPLS related standards track MIB modules should be any copyrights, patents or patent applications, or other
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules proprietary rights that may cover technology that may be required
contained in this document, each of the following "IANA to implement this standard. Please address the information to the
Considerations" subsections requests IANA for a new assignment under IETF at ietf-ipr@ietf.org.
the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434].
18.1. IANA Considerations for MPLS-TE-STD-MIB Acknowledgement
The IANA is requested to assign { mplsStdMIB 3 } to the Funding for the RFC Editor function is currently provided by the
MPLS-TE-STD-MIB module specified in this document. Internet Society.
 End of changes. 397 change blocks. 
2703 lines changed or deleted 2649 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/