draft-ietf-mpls-te-mib-03.txt   draft-ietf-mpls-te-mib-04.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Tachion Networks, Inc. Internet Draft Tachion Networks, Inc.
Expires: September 2000 Expires: January 2001
Arun Viswanathan Arun Viswanathan
Force10 Networks Force10 Networks, Inc.
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
MPLS Traffic Engineering Management Information Base July 14, 2000
Using SMIv2
draft-ietf-mpls-te-mib-03.txt MPLS Traffic Engineering Management Information Base Using
SMIv2
draft-ietf-mpls-te-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full
conformance with all provisions of Section 10 of conformance with all provisions of Section 10 of RFC2026.
RFC2026.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its Engineering Task Force (IETF), its areas, and its working
working groups. Note that other groups may also groups. Note that other groups may also distribute working
distribute working documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a Internet-Drafts are draft documents valid for a maximum of
maximum of six months and may be updated, replaced, or six months and may be updated, replaced, or obsoleted by
obsoleted by other documents at any time. It is other documents at any time. It is inappropriate to use
inappropriate to use Internet-Drafts as reference Internet-Drafts as reference material or to cite them other
material or to cite them other than as "work in than as "work in progress."
progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html. accessed at http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines an experimental portion of the This memo defines an experimental portion of the Management
Management Information Base (MIB) for use with Information Base (MIB) for use with network management
network management protocols in the Internet protocols in the Internet community. In particular, it
community. In particular, it describes managed describes managed objects for Multi-Protocol Label
objects for Multi-Protocol Label Switching (MPLS) Switching (MPLS) [MPLSArch] [MPLSFW] based traffic
[MPLSArch] [MPLSFW] based traffic engineering. engineering.
1. Introduction 1. Introduction
This memo defines an experimental portion of the This memo defines an experimental portion of the Management
Management Information Base (MIB) for use with network Information Base (MIB) for use with network management
management protocols in the Internet community. In protocols in the Internet community. In particular, it
particular, it describes managed objects for modeling describes managed objects for modeling a Multi-Protocol
a Multi-Protocol Label Switching (MPLS) Label Switching (MPLS) [MPLSArch][MPLSFW] based traffic
[MPLSArch][MPLSFW] based traffic engineering. This MIB engineering. This MIB should be used in conjunction with
should be used in conjunction with the companion the companion document [LSRMIB] for MPLS based traffic
document [LSRMIB] for MPLS based traffic engineering engineering configuration and management.
configuration and management.
Comments should be made directly to the MPLS mailing Comments should be made directly to the MPLS mailing list
list at mpls@uu.net. at mpls@uu.net.
This memo does not, in its draft form, specify a This memo does not, in its draft form, specify a standard
standard for the Internet community. for the Internet community.
2. Terminology 2. Terminology
This document uses terminology from the MPLS This document uses terminology from the MPLS architecture
architecture document [MPLSArch] and MPLS Label Switch document [MPLSArch] and MPLS Label Switch Router MIB
Router MIB [LSRMIB]. Some frequently used terms are [LSRMIB]. Some frequently used terms are described next.
described next.
An explicitly routed LSP (ERLSP) is referred to as an An explicitly routed LSP (ERLSP) is referred to as an MPLS
MPLS tunnel. It consists of one in-segment and/or one tunnel. It consists of one in-segment and/or one out-
out-segment at the ingress/egress LSRs, each segment segment at the ingress/egress LSRs, each segment being
being associated with one MPLS interface. These are associated with one MPLS interface. These are also
also referred to as tunnel segments. Additionally, at referred to as tunnel segments. Additionally, at an
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 one or more in-segments and/or one or more out-segments.
more out-segments. The binding or interconnection The binding or interconnection between in-segments and out-
between in-segments and out-segments in performed segments in performed using a cross-connect. These objects
using a cross-connect. These objects are defined in are defined in the MPLS Label Switch Router MIB [LSRMIB].
the MPLS Label Switch Router MIB [LSRMIB].
3. The SNMP Management Framework 3. The SNMP Management Framework
The SNMP Management Framework presently consists of The SNMP Management Framework presently consists of five
five major components: major components:
- An overall architecture, described in RFC 2271 - An overall architecture, described in RFC 2271
[SNMPArch]. [SNMPArch].
- Mechanisms for describing and naming objects and - Mechanisms for describing and naming objects and events
events for the purpose of management. The first for the purpose of management. The first version of
version of this Structure of Management this Structure of Management Information (SMI) is
Information (SMI) is called SMIv1 and described in called SMIv1 and described in RFC 1155 [SMIv1], RFC
RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The
1215 [SNMPv1Traps]. The second version, called second version, called SMIv2, is described in RFC 1902
SMIv2, is described in RFC 1902 [SMIv2], RFC 1903 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf].
[SNMPv2TC] and RFC 1904 [SNMPv2Conf].
- Message protocols for transferring management - Message protocols for transferring management
information. The first version of the SNMP information. The first version of the SNMP message
message protocol is called SNMPv1 and described in protocol is called SNMPv1 and described in RFC 1157
RFC 1157 [SNMPv1]. A second version of the SNMP [SNMPv1]. A second version of the SNMP message
message protocol, which is not an Internet protocol, which is not an Internet standards track
standards track protocol, is called SNMPv2c and protocol, is called SNMPv2c and described in RFC 1901
described in RFC 1901 [SNMPv2c] and RFC 1906 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version
[SNMPv2TM]. The third version of the message of the message protocol is called SNMPv3 and described
protocol is called SNMPv3 and described in RFC in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC
1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 2574 [SNMPv3USM].
[SNMPv3USM].
- Protocol operations for accessing management - Protocol operations for accessing management
information. The first set of protocol operations information. The first set of protocol operations and
and associated PDU formats is described in RFC associated PDU formats is described in RFC 1157
1157 [SNMPv1]. A second set of protocol [SNMPv1]. A second set of protocol operations and
operations and associated PDU formats is described associated PDU formats is described in RFC 1905
in RFC 1905 [SNMPv2PO]. [SNMPv2PO].
- A set of fundamental applications described in RFC - A set of fundamental applications described in RFC 2273
2273 [SNMPv3App] and the view-based access control [SNMPv3App] and the view-based access control mechanism
mechanism described in RFC 2575 [SNMPv3VACM]. described in RFC 2575 [SNMPv3VACM].
Managed objects are accessed via a virtual information Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. store, termed the Management Information Base or MIB.
Objects in the MIB are defined using the mechanisms Objects in the MIB are defined using the mechanisms defined
defined in the SMI. This memo specifies a MIB module in the SMI. This memo specifies a MIB module that is
that is compliant to the SMIv2. A MIB conforming to compliant to the SMIv2. A MIB conforming to the SMIv1 can
the SMIv1 can be produced through the appropriate be produced through the appropriate translations. The
translations. The resulting translated MIB must be resulting translated MIB must be semantically equivalent,
semantically equivalent, except where objects or except where objects or events are omitted because no
events are omitted because no translation is possible translation is possible (use of Counter64). Some machine-
(use of Counter64). Some machine-readable information readable information in SMIv2 will be converted into
in SMIv2 will be converted into textual descriptions textual descriptions in SMIv1 during the translation
in SMIv1 during the translation process. However, process. However, this loss of machine-readable
this loss of machine-readable information is not information is not considered to change the semantics of
considered to change the semantics of the MIB. the MIB.
3.1. Object Definitions 3.1. Object Definitions
Managed objects are accessed via a virtual information Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. store, termed the Management Information Base or MIB.
Objects in the MIB are defined using the subset of Objects in the MIB are defined using the subset of Abstract
Abstract Syntax Notation One (ASN.1) defined in the Syntax Notation One (ASN.1) defined in the SMI. In
SMI. In particular, each object type is named by an particular, each object type is named by an OBJECT
OBJECT IDENTIFIER, an administratively assigned name. IDENTIFIER, an administratively assigned name. The object
The object type together with an object instance type together with an object instance serves to uniquely
serves to uniquely identify a specific instantiation identify a specific instantiation of the object. For human
of the object. For human convenience, we often use a convenience, we often use a textual string, termed the
textual string, termed the descriptor, to also refer descriptor, to also refer to the object type.
to the object type.
4. Feature Checklist
The MPLS traffic engineering MIB is designed to
satisfy the following requirements and constraints.
- The MIB must support the configuration of point-to- 4. Feature List
point unidirectional tunnels.
- The MIB should be able to support the configuration The MPLS traffic engineering MIB is designed to satisfy the
of point-to-point bi-directional tunnels. following requirements and constraints.
- The MIB should be able to support the configuration - The MIB supports configuration of point-to-point
of multi-point-to-point unidirectional tunnels. unidirectional tunnels.
- MPLS tunnels need not be interfaces, but it should - MPLS tunnels need not be interfaces, but it is possible
be possible to configure a tunnel as an interface. to configure a tunnel as an interface.
- The MIB should be able to support both manually - The MIB supports manually configured MPLS tunnels as
configured MPLS tunnels as well as those set up well as those set up via any MPLS signaling protocol.
via any MPLS signaling protocol.
- It should be possible to support persistent as well - The MIB supports persistent as well as non-persistent
as non-persistent tunnels. tunnels.
5. Outline 5. Outline
Traffic engineering support for MPLS tunnels requires Traffic engineering support for MPLS tunnels requires the
the following configuration. following configuration.
- Setting up MPLS tunnels along with appropriate - Setting up MPLS tunnels along with appropriate
configuration parameters. configuration parameters.
- Configuring tunnel loose and strict source routed - Configuring tunnel loose and strict source routed hops.
hops.
These actions may need to be accompanied with These actions may need to be accompanied with corresponding
corresponding actions using [LSRMIB] to establish and actions using [LSRMIB] to establish and configure tunnel
configure tunnel segments, if this is done manually. segments, if this is done manually. Also, the in-segment
Also, the in-segment and out-segment performance and out-segment performance tables, mplsInSegmentPerfTable
tables, mplsInSegmentPerfTable and and mplsOutSegmentPerfTable [LSRMIB], should be used to
mplsOutSegmentPerfTable [LSRMIB], should be used to determine performance of the tunnels and tunnel segments.
determine performance of the tunnels and tunnel
segments.
5.1. Summary of Traffic Engineering MIB 5.1. Summary of Traffic Engineering MIB
The MIB objects for performing these actions consist The MIB 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
the tunnel resources.
- Tunnel hop table (mplsTunnelHopTable) for configuring - Tunnel hop table (mplsTunnelHopTable) for configuring
strict and loose source routed MPLS tunnels hops. strict and loose source routed MPLS tunnels hops.
- Resource table (mplsTunnelResourceTable) for When a tunnel is signaled via a MPLS signaling protocol,
setting up the tunnel resources. the mplsTunnelARHopTable gives the actual list of hops
traversed by the tunnel as reported by the signaling
- Tunnel Actual Route Table (mplsTunnelARHopTable) protocol. These tables are described in the subsequent
for viewing the actual route used by the tunnel. 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 described in documents [RSVPTun][CR- functionality described in documents [RSVPTun][CR-LDP].
LDP]. The tables support both manually configured and The tables support both manually configured and signaled
signaled tunnels. Moreover, they provide the tunnels.
capability to associate two unidirectional tunnels to
form a single bi-directional tunnel.
6.1. mplsTunnelTable 6.1. mplsTunnelTable
The mplsTunnelTable allows new MPLS tunnels to be The mplsTunnelTable allows new MPLS tunnels to be created
created between an MPLS LSR and a remote endpoint, and between an MPLS LSR and a remote endpoint, and existing
existing tunnels to be reconfigured or removed. Note tunnels to be reconfigured or removed. Note that we only
that we only support point-to-point tunnel segments, support point-to-point tunnel segments, although multi-
although multi-point-to-point and point-to-multi-point point-to-point and point-to-multi-point connections are
connections are supported by an LSR acting as a cross- supported by an LSR acting as a cross-connect. Each MPLS
connect. Each MPLS tunnel can thus have one out- tunnel can thus have one out-segment originating at an LSR
segment originating at an LSR and/or one in-segment and/or one in-segment terminating at that LSR.
terminating at that LSR.
mplsTunnelTable does not define the in and out mplsTunnelTable does not define the in and out segments
segments forming the tunnel. Instead, these are forming the tunnel. Instead, these are defined by creating
defined by creating rows in the in-segment and out- rows in the in-segment and out-segment tables, defining
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 these rows in the mplsTunnelTable using a cross-connect
mplsTunnelTable using a cross-connect index, index, mplsTunnelXCID. These segment and cross-connect
mplsTunnelXCID. These segment and cross-connect
related objects are defined in [LSRMIB]. related objects are defined in [LSRMIB].
6.2. mplsTunnelHopTable 6.2. mplsTunnelResourceTable
mplsTunnelHopTable is used to indicate the hops, mplsTunnelResourceTable is used to indicate the resources
strict or loose, for an MPLS tunnel defined in required for a tunnel. Multiple tunnels may share the same
mplsTunnelTable, when it is established via signaling. resource by pointing to the same entry in this table.
Each row in this table is indexed primarily by the Tunnel that do not share resource must point to separate
same index mplsTunnelIndex as the row of the entries in this table.
corresponding tunnel in mplsTunnelTable. Each row
also has a secondary index, mplsTunnelHopIndex,
corresponding to the next hop of this tunnel. The
scalar mplsTunnelMaxHops indicates the maximum number
of hops that can be specified on each tunnel supported
by this LSR.
6.3. mplsTunnelResourceTable 6.3. mplsTunnelHopTable
mplsTunnelResourceTable is used to indicate the mplsTunnelHopTable is used to indicate the hops, strict or
resources required for a tunnel. Multiple tunnels may loose, for an MPLS tunnel defined in mplsTunnelTable, when
share the same resource by pointing to the same entry it is established via signaling. Multiple tunnels may
in this table. Tunnels that do not share resources share the same hops by pointing to the same entry in this
must point to separate entries in this table. table. Each row also has a secondary index,
mplsTunnelHopIndex, corresponding to the next hop of this
tunnel. The scalar mplsTunnelMaxHops indicates the maximum
number of hops that can be specified on each tunnel
supported by this LSR.
6.4. mplsTunnelARHopTable 6.4. mplsTunnelARHopTable
mplsTunnelARHopTable is used to indicate the actual mplsTunnelARHopTable is used to indicate the actual hops
route taken by a tunnel. This table is particularly traversed by a tunnel as reported by the MPLS signaling
useful in cases where tunnel hops are loosely routed. protocol after the tunnel is setup. The support of this
This table will allow the user to see the actual path table is optional since not all MPLS signaling protocol may
taken by the tunnel through the network. Support of support this feature.
this tunnel is dependent upon the MPLS signaling
protocols providing this information.
7. Example of Tunnel Setup 7. Application of the Interface Group to MPLS Tunnels
The Interfaces Group of MIB II defines generic managed
objects for managing interfaces. This memo contains the
media-specific extensions to the Interfaces Group for
managing MPLS Tunnels as logical interfaces.
This memo assumes the interpretation of the Interfaces
Group to be in accordance with [IFMIB] which states that
the interfaces table (ifTable) contains information on the
managed resource's interfaces and that each sub-layer below
the internetwork layer of a network interface is considered
an interface. Thus, the MPLS interface is represented as
an entry in the ifTable. The interrelation of entries in
the ifTable is defined by Interfaces Stack Group defined in
[IFMIB].
When using MPLS Tunnels as interfaces, the interface stack
table might appear as follows:
+------------------------------------------+
| MPLS-Tunnel-interface ifType = mpls(150) |
+------------------------------------------+
| MPLS-interface ifType = mpls(166) |
+------------------------------------------+
| Underlying Layer |
+------------------------------------------+
In the above diagram, "Underlying Layer" refers to the
ifIndex of any interface type, which has been defined for
MPLS interworking. Examples include ATM, Frame Relay,
Ethernet, etc.
7.1. Support of the MPLS Tunnel Interface by ifTable
Some specific interpretations of ifTable for those MPLS
tunnels represented as interfaces follow:
Object Use for the MPLS tunnel.
ifIndex Each MPLS tunnel is represented by an
ifEntry.
ifDescr Description of the MPLS tunnel.
ifType The value that is allocated for MPLS
tunnel is 150.
ifSpeed The total bandwidth in bits per second
for use by the MPLS tunnel.
ifPhysAddress Unused.
ifAdminStatus See [IFMIB].
ifOperStatus Assumes the value down(2) if the MPLS
tunnel is down.
ifLastChange See [IFMIB].
ifInOctets The number of octets received over the
MPLS tunnel.
ifOutOctets The number of octets transmitted over
the MPLS tunnel.
ifInErrors The number of labeled packets dropped
due to uncorrectable errors.
ifInUnknownProtos The number of received packets
discarded during packet header
validation, including packets with
unrecognized label values.
ifOutErrors See [IFMIB].
ifName Textual name (unique on this system) of
the MPLS tunnel or an octet string of
zero length.
ifLinkUpDownTrapEnable
Default is disabled (2).
ifConnectorPresent Set to false (2).
ifHighSpeed See [IFMIB].
ifHCInOctets The 64-bit version of ifInOctets;
supported if required by the compliance
statements in [IFMIB].
ifHCOutOctets The 64-bit version of ifOutOctets;
supported if required by the compliance
statements in [IFMIB].
ifAlias The non-volatile 'alias' name for the
MPLS tunnel as specified by a network
manager.
8. Example of Tunnel Setup
This section contains an example of which MIB objects This section contains an example of which MIB objects
should be modified if one would like to create should be modified if one would like to create a best
loosely routed, unidirectional traffic engineered effort, loosely routed, unidirectional traffic engineered
tunnel, which spans two hops of a simple network. tunnel, which spans two hops of a simple network. Note
Note that these objects should be created on the that these objects should be created on the "head-end"
"head-end" LSR. LSR.
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
mplsTunnelName = "My first tunnel ", mplsTunnelName = "My first tunnel ",
mplsTunnelDescr = "Here to there", mplsTunnelDescr = "Here to there",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
mplsTunnelIfIndex = 12, mplsTunnelIfIndex = 12,
mplsTunnelDirection = in (1), mplsTunnelXCPointer = mplsXCIndex.2.0.0.15,
mplsTunnelXCIndex = 15,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelLocalCookie = 123.123.123.1,
mplsTunnelRemoteCookie = 123.123.123.1,
mplsTunnelIsMergeable = false (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0, mplsTunnelHoldingPrio = 0,
mplsTunnelIsPersistent = false (1),
mplsTunnelSessionAttributes = 0, mplsTunnelSessionAttributes = 0,
mplsTunnelOwner = snmp (1), mplsTunnelOwner = snmp (1),
mplsTunnelLocalProtectInUse = false (0), mplsTunnelLocalProtectInUse = false (0),
mplsTunnelResourceEntryIndex= 5, mplsTunnelResourcePointer = mplsTunnelResourceIndex.5,
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
In mplsTunnelResourceTable: In mplsTunnelResourceTable:
{ {
mplsTunnelResourceIndex = 5, mplsTunnelResourceIndex = 5,
mplsTunnelInMaxRate = 100, mplsTunnelResourceMaxRate = 0,
mplsTunnelInMeanRate = 100, mplsTunnelResourceMeanRate = 0,
mplsTunnelInMaxBurstSize = 100, mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelOutMaxRate = 100,
mplsTunnelOutMeanRate = 100,
mplsTunnelOutMaxBurstSize = 100,
mplsTunnelResourceRowStatus = createAndGo (4) mplsTunnelResourceRowStatus = createAndGo (4)
} }
The next two instances of mplsTunnelHopEntry are used The next two instances of mplsTunnelHopEntry are used to
to denote the hops this tunnel will take across the denote the hops this tunnel will take across the network.
network. Note that mplsTunnelIndex,
mplsTunnelInstance, and mplsTunnelHopIndex are used to
index these objects. For the purposes of this example,
all entries in the MplsTunnelHopTable will use the
index of 1, which was defined for the mpslTunnelEntry
above.
The following denotes the beginning of the network, or The following denotes the beginning of the network, or the
the first hop. We have used the fictitious LSR first hop. We have used the fictitious LSR identified by
identified by "123.123.125.1" as our example head-end "123.123.125.1" as our example head-end router.
router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1,
mplsTunnelHopIndex = 1, mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = 1, mplsTunnelHopAddrType = 1,
mplsTunnelHopIpv4Addr = 123.123.125.1, mplsTunnelHopIpv4Addr = 123.123.125.1,
mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopStrictOrLoose = loose (2), mplsTunnelHopStrictOrLoose = loose (2),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
The following denotes the end of the network, or the The following denotes the end of the network, or the last
last hop in our example. We have used the fictitious hop in our example. We have used the fictitious LSR
LSR identified by "123.123.126.1" as our end router. identified by "123.123.126.1" as our end router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1,
mplsTunnelHopIndex = 2, mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = 1, mplsTunnelHopAddrType = 1,
mplsTunnelHopIpv4Addr = 123.123.126.1, mplsTunnelHopIpv4Addr = 123.123.126.1,
mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopStrictOrLoose = loose (2), mplsTunnelHopStrictOrLoose = loose (2),
mplsTunnelHopOwner = snmp (1),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
7.1. Support of the MPLS Layer by ifTable 9. The Use of RowPointer
Some specific interpretations of ifTable for the MPLS
layer follow.
Object Use for the MPLS layer.
ifIndex Each MPLS interface is represented by
an ifEntry.
ifDescr Description of the MPLS interface.
ifType The value that is allocated for MPLS is
<TBD>.
ifSpeed The total bandwidth in bits per second
for use by the MPLS layer.
ifPhysAddress Unused.
ifAdminStatus See [IFMIB].
ifOperStatus Assumes the value down(2) if the MPLS
layer is down.
ifLastChange See [IFMIB].
ifInOctets The number of received octets over
the interface, i.e., the number of
received, octets received as labeled
packets.
ifOutOctets The number of transmitted octets over
the interface, i.e., the number of
octets transmitted as labeled
packets.
ifInErrors The number of labeled packets dropped
due to uncorrectable errors.
ifInUnknownProtos The number of
received packets discarded during packet header
validation,
including packets with unrecognized label values.
ifOutErrors See [IFMIB].
ifName Textual name (unique on this system)
of the interface or an octet string
of zero length.
ifLinkUpDownTrapEnable Default is disabled (2).
ifConnectorPresent Set to false (2).
ifHighSpeed See [IFMIB].
ifHCInOctets The 64-bit version of ifInOctets;
supported if required by the
compliance statements in [IFMIB].
ifHCOutOctets The 64-bit version of ifOutOctets;
supported if required by the
compliance statements in [IFMIB].
ifAlias The non-volatile 'alias' name for the RowPointer is a textual convention used to identify a
interface as specified by a network conceptual row in an SNMP Table by pointing to one of its
manager. objects. In this MIB, 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.
8. MPLS Traffic Engineering MIB Definitions 10. MPLS Traffic Engineering MIB Definitions
MPLS-TE-MIB DEFINITIONS ::= BEGIN MPLS-TE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Counter32, Counter64, experimental, Integer32
Gauge32,
IpAddress
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus
TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer,
StorageType, DisplayString, Unsigned32
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex, InterfaceIndex, InterfaceIndexOrZero
InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
MplsBitRate, MplsBurstSize
FROM MPLS-LSR-MIB; MplsBitRate, MplsBurstSize, MplsLSPID
FROM MPLS-LSR-MIB
InetAddressIPv4, InetAddressIPv6
FROM INET-ADDRESS-MIB;
mplsTeMIB MODULE-IDENTITY mplsTeMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200003031200Z" -- 3 Mar 2000 12:00:00 EST "200007141200Z" -- 14 July 2000 12:00:00 EST
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working "Multiprotocol Label Switching (MPLS) Working Group"
Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan " Cheenu Srinivasan
Postal: Tachion Networks, Inc. Postal: Tachion Networks, Inc.
2 Meridian Road Monmouth Park Corporate Center I
Eatontown, NJ 0772 Building C, 185 Monmouth Park Highway
Tel: +1 732 542 7750 x234 West Long Branch, NJ 07764
Tel: +1-732-542-7750 x1234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Postal: Force10 Networks Postal: Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Tel: +1-408-571-3516 Tel: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
Email: tnadeau@cisco.com" Email: tnadeau@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object "This MIB module contains managed object definitions
definitions for MPLS Traffic Engineering (TE) as for MPLS Traffic Engineering (TE) as defined in:
defined in: Extensions to RSVP for LSP Tunnels, Extensions to RSVP for LSP Tunnels, Awduche et al,
Awduche et al, Internet Draft <draft-mpls-rsvp- Internet Draft <draft-mpls-rsvp-lsp-tunnel-02.txt>,
lsp-tunnel-02.txt>, March 1999; Constraint-Based March 1999; Constraint-Based LSP Setup using LDP, B.
LSP Setup using LDP, B. Jamoussi, Internet Draft Jamoussi, Internet Draft <draft-ietf-mpls-cr-ldp-
<draft-ietf-mpls-cr-ldp-01.txt>, Feb. 1999; 01.txt>, Feb. 1999; Requirements for Traffic
Requirements for Traffic Engineering Over MPLS, Engineering Over MPLS, Awduche, D., J. Malcolm, J.,
Awduche, D., J. Malcolm, J., Agogbua, J., Agogbua, J., O'Dell, M., J. McManus, <rfc2702.txt>,
O'Dell, M., J. McManus, <rfc2702.txt>, September September 1999."
1999."
-- Revision history. -- Revision history.
REVISION REVISION
"199907161200Z" -- 16 July 1999 12:00:00 EST "200007141200Z" -- 14 July 2000 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Updates based on MPLS WG feedback"
REVISION REVISION
"200003101700Z" -- 10 March 2000 17:00:00 EST "200005261200Z" -- 26 May 2000 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx." "Updates based on MPLS WG feedback"
REVISION
"200003031200Z" -- 3 March 2000 12:00:00 EST
DESCRIPTION
"Updates based on MPLS WG feedback"
REVISION
"199907161200Z" -- 16 July 1999 12:00:00 EST
DESCRIPTION
"Initial draft version."
::= { experimental 95 } ::= { experimental 95 }
-- Textual Conventions. -- Textual Conventions.
MplsLabel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents an MPLS label. Note that the
contents of a label field are interpreted in an
interface-type specific fashion. For example,
the label carried in the MPLS shim header is 20
bits wide and the top 12 bits must be zero. The
frame relay label can be either 10, 17 or 23
bits wide depending on the size of the DLCI
field size and the top 22, 15, or 9 bits must be
zero, respectively. For an ATM interface, the
lowermost 16 bits are interpreted as the VCI,
the next 8 bits as the VPI and the remaining
bits must be zero. Also note the permissible
label values are also a function of the
interface type. For example, the value 3 has
special semantics in the control plane for an
MPLS shim header label and is not a valid label
value in the data path."
REFERENCE
"1. MPLS Label Stack Encoding, Rosen et al, draft-
ietf-mpls-label-encaps-04.txt, April 1999.
2. Use of Label Switching on Frame Relay
Networks, Conta et al, draft-ietf-mpls-fr-
03.txt, Nov. 1998."
SYNTAX Integer32
MplsTunnelIndex ::= TEXTUAL-CONVENTION MplsTunnelIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index into mplsTunnelTable." "Index into mplsTunnelTable."
SYNTAX INTEGER (0..65535) SYNTAX Integer32 (0..65535)
MplsTunnelInstance ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Instance of the tunnel; secondary index into
mplsTunnelTable."
SYNTAX INTEGER (0..65535)
MplsTunnelCookie ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A globally unique identifier that is assigned to
each ERLSP. This is assigned at the head end of
the ERLSP and can be used by all LSRs to
identify this ERLSP. At the head end this
cookie is maintained in the tunnel table as
mplsTunnelLocalCookie. For signaled tunnels
this cookie is piggybacked by the signaling
protocol to the remote end where the cookie is
stored in the remote LSR's tunnel table as
mplsTunnelRemoteCookie for the tunnel. For
creating bi-directional tunnels the cookie is
used to associate the two unidirectional ERLSPs
as belonging to the same tunnel.
It is recommended that the cookie value be
assigned by concatenating the head-end LSR's IP
address with the tunnel index. For IPv4
addresses this results in a 6-octet long
cookie."
SYNTAX OCTET STRING (SIZE (0..255))
Ipv6Address ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IPv6 address."
SYNTAX OCTET STRING (SIZE(16))
-- Top level components of this MIB. -- Top level components of this MIB.
-- tables, scalars -- tables, scalars
mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 1 } mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 1 }
-- traps -- traps
mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 2 } mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 2 }
mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 }
-- conformance -- conformance
mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 }
-- MPLS tunnel table. -- MPLS tunnel table.
mplsTunnelIndexNext OBJECT-TYPE mplsTunnelIndexNext OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the next appropriate value "This object contains the next appropriate value to
to be used for mplsTunnelIndex when creating be used for mplsTunnelIndex when creating entries in
entries in the mplsTunnelTable. If the number of mplsTunnelTable. If the number of unassigned entries
unassigned entries is exhausted, this object is exhausted, a retrival operation will return a
will take on the value of 0. To obtain the value of 0. This object may also return a value of
mplsTunnelIndex value for a new entry, the 0 when the LSR is unable to accept conceptual row
manager must first issue a management protocol creation, for example, if the mplsTunnelTable is
retrieval operation to obtain the current value implemented as read-only. To obtain the value of
of this object. The agent should modify the mplsTunnelIndex for a new entry, the manager must
value to reflect the next unassigned index after first issue a management protocol retrieval
each retrieval operation. After a manager operation to obtain the current value of this
retrieves a value the agent will determine object. The agent should modify the value to reflect
through its local policy when this index value the next unassigned index after each retrieval
will be made available for reuse." operation. After a manager retrieves a value the
agent will determine through its local policy when
this index value will be made available for reuse."
::= { mplsTeObjects 1 } ::= { mplsTeObjects 1 }
mplsTunnelTable OBJECT-TYPE mplsTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelEntry SYNTAX SEQUENCE OF MplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelTable allows new MPLS tunnels to "The mplsTunnelTable allows new MPLS tunnels to be
be created between an LSR and a remote endpoint, created between an LSR and a remote endpoint, and
and existing tunnels to be reconfigured or existing tunnels to be reconfigured or removed.
removed. Note that only point-to-point tunnel Note that only point-to-point tunnel segments are
segments are supported, although multi-point-to- supported, although multi-point-to-point and point-
point and point-to-multi-point connections are to-multi-point connections are supported by an LSR
supported by an LSR acting as a cross-connect. acting as a cross-connect. Each MPLS tunnel can
Each MPLS tunnel can thus have one out-segment thus have one out-segment originating at this LSR
originating at this LSR and/or one in-segment and/or one in-segment terminating at this LSR."
terminating at this LSR."
::= { mplsTeObjects 2 } ::= { mplsTeObjects 2 }
mplsTunnelEntry OBJECT-TYPE mplsTunnelEntry OBJECT-TYPE
SYNTAX MplsTunnelEntry SYNTAX MplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents an MPLS "An entry in this table represents an MPLS tunnel.
tunnel. An entry can be created by a network An entry can be created by a network administrator
administrator or by an SNMP agent as instructed or by an SNMP agent as instructed by an MPLS
by an MPLS signaling protocol. Whenever a new signaling protocol. Whenever a new entry is created
entry is created with mplsTunnelIsIf set to with mplsTunnelIsIf set to true(1), then a
true(1), then a corresponding entry is created corresponding entry is created in ifTable as well
in ifTable as well (see RFC 2233). The ifType of (see RFC 2233). The ifType of this entry is
this entry is mplsTunnel(150)." mplsTunnel(150)."
REFERENCE REFERENCE
"1. RFC 2233 - The Interfaces Group MIB using "1. RFC 2233 - The Interfaces Group MIB using SMIv2,
SMIv2, McCloghrie, K., and F. Kastenholtz, Nov. McCloghrie, K., and F. Kastenholtz, Nov. 1997
1997 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J.
2. RFC 1700 - Assigned Numbers, Reynolds, J. and Postel, Oct. 1994"
J. Postel, Oct. 1994" INDEX { mplsTunnelIndex, mplsTunnelInstance,
INDEX { mplsTunnelIndex, mplsTunnelInstance } mplsTunnelIngressLSRId }
::= { mplsTunnelTable 1 } ::= { mplsTunnelTable 1 }
MplsTunnelEntry ::= SEQUENCE { MplsTunnelEntry ::= SEQUENCE {
mplsTunnelIndex MplsTunnelIndex, mplsTunnelIndex MplsTunnelIndex,
mplsTunnelInstance MplsTunnelInstance, mplsTunnelInstance MplsTunnelIndex,
mplsTunnelIngressLSRId Unsigned32,
mplsTunnelName DisplayString, mplsTunnelName DisplayString,
mplsTunnelDescr DisplayString, mplsTunnelDescr DisplayString,
mplsTunnelIsIf TruthValue, mplsTunnelIsIf TruthValue,
mplsTunnelIfIndex InterfaceIndexOrZero, mplsTunnelIfIndex InterfaceIndexOrZero,
mplsTunnelDirection INTEGER, mplsTunnelXCPointer RowPointer,
mplsTunnelXCIndex Integer32,
mplsTunnelSignallingProto INTEGER, mplsTunnelSignallingProto INTEGER,
mplsTunnelLocalCookie MplsTunnelCookie,
mplsTunnelRemoteCookie MplsTunnelCookie,
mplsTunnelSetupPrio INTEGER, mplsTunnelSetupPrio INTEGER,
mplsTunnelHoldingPrio INTEGER, mplsTunnelHoldingPrio INTEGER,
mplsTunnelSessionAttributes INTEGER, mplsTunnelSessionAttributes BITS,
mplsTunnelOwner INTEGER, mplsTunnelOwner INTEGER,
mplsTunnelResourceEntryIndex INTEGER, mplsTunnelLocalProtectInUse TruthValue,
mplsTunnelResourcePointer RowPointer,
mplsTunnelInstancePriority Integer32, mplsTunnelInstancePriority Integer32,
mplsTunnelHopTableIndex Integer32,
mplsTunnelARHopTableIndex Integer32,
mplsTunnelAdminStatus INTEGER, mplsTunnelAdminStatus INTEGER,
mplsTunnelOperStatus INTEGER, mplsTunnelOperStatus INTEGER,
mplsTunnelRowStatus RowStatus mplsTunnelRowStatus RowStatus,
mplsTunnelStorageType StorageType
} }
mplsTunnelIndex OBJECT-TYPE mplsTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelIndex
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies this row." "Uniquely identifies this row."
::= { mplsTunnelEntry 1 } ::= { mplsTunnelEntry 1 }
mplsTunnelInstance OBJECT-TYPE mplsTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelIndex
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies an instance of a tunnel. It "Uniquely identifies an instance of a tunnel. It is
is useful to identify multiple instances of useful to identify multiple instances of tunnels for
tunnels for the purposes of backup and parallel the purposes of backup and parallel tunnels."
tunnels."
::= { mplsTunnelEntry 2 } ::= { mplsTunnelEntry 2 }
mplsTunnelIngressLSRId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The purpose of this object is to uniquely identity a
tunnel within a network. When the MPLS signalling
protoocol is rsvp(2) this value should mimic the
Extended Tunnel Id field in the Session object. When
the MPLS signalling protoocol is crldp(3) this value
should mimic the Ingress LSR Router ID field in the
LSPID TLV object."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
Awduche et al, Internet Draft <draft-mpls-rsvp-lsp-
tunnel-05.txt>, February 2000.,
2. Constraint-Based LSP Setup using LDP, Jamoussi,
Internet Draft <draft-ietf-mpls-cr-ldp-03.txt>,
September 1999."
::= { mplsTunnelEntry 3 }
mplsTunnelName OBJECT-TYPE mplsTunnelName OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The canonical name assigned to the tunnel. This "The canonical name assigned to the tunnel. This name
name can be used to refer to the tunnel on the can be used to refer to the tunnel on the LSR’s
LSR’s console port. If mplsTunnelIsIf is set to console port. If mplsTunnelIsIf is set to true then
true then the ifName of the interface the ifName of the interface corresponding to this
corresponding to this tunnel should have a value tunnel should have a value equal to mplsTunnelName.
equal to mplsTunnelName. Also see the Also see the description of ifName in RFC 2233."
description of ifName in RFC 2233."
REFERENCE REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2, "RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997" McCloghrie, K., and F. Kastenholtz, Nov. 1997"
::= { mplsTunnelEntry 3 } ::= { mplsTunnelEntry 4 }
mplsTunnelDescr OBJECT-TYPE mplsTunnelDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about "A textual string containing information about the
the tunnel. If there is no description this tunnel. If there is no description this object
object contains a zero length string." contains a zero length string."
::= { mplsTunnelEntry 4 } ::= { mplsTunnelEntry 5 }
mplsTunnelIsIf OBJECT-TYPE mplsTunnelIsIf OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel corresponds "Denotes whether or not this tunnel corresponds to an
to an interface represented in the interfaces interface represented in the interfaces group table.
group table. Note that if this variable is set Note that if this variable is set to true then the
to true then the ifName of the interface ifName of the interface corresponding to this tunnel
corresponding to this tunnel should have a value should have a value equal to mplsTunnelName. Also
equal to mplsTunnelName. Also see the see the description of ifName in RFC 2233."
description of ifName in RFC 2233."
REFERENCE REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2, "RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997" McCloghrie, K., and F. Kastenholtz, Nov. 1997"
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelEntry 5 } ::= { mplsTunnelEntry 6 }
mplsTunnelIfIndex OBJECT-TYPE mplsTunnelIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelIsIf is set to true, then this "If mplsTunnelIsIf is set to true, then this value
value contains the LSR-assigned ifIndex which contains the LSR-assigned ifIndex which corresponds
corresponds to an entry in the interfaces table. to an entry in the interfaces table. Otherwise this
variable should contain the value of zero indicating
Otherwise this variable should contain the value that a valid ifIndex was not assigned to this tunnel
of zero indicating that a valid ifIndex was not interface."
assigned to this tunnel interface."
REFERENCE REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2, "RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997" McCloghrie, K., and F. Kastenholtz, Nov. 1997"
::= { mplsTunnelEntry 6 }
mplsTunnelDirection OBJECT-TYPE
SYNTAX INTEGER { in(1), out(2), in-out(3) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates whether this tunnel is unidirectional-
incoming, unidirectional-outgoing, or bi-
directional."
::= { mplsTunnelEntry 7 } ::= { mplsTunnelEntry 7 }
mplsTunnelXCIndex OBJECT-TYPE mplsTunnelXCPointer OBJECT-TYPE
SYNTAX Integer32 SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents an index into the "This variable points to a row in the mplsXCTable.
mplsXCTable. This table identifies the segments This table identifies the segments that compose this
that compose this tunnel, their characteristics, tunnel, their characteristics, and relationships to
and relationships to each other." each other. A value of zeroDotZero indicates that no
LSP has been associated with this tunnel yet."
REFERENCE REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS
MPLS Label Switch Router Management Information Label Switch Router Management Information Base
Base Using SMIv2, Internet Draft <draft-ietf- Using SMIv2, Internet Draft <draft-ietf-mpls-lsr-mib-
mpls-lsr-mib-01.txt>, March 2000." 04.txt>, April 26, 2000."
DEFVAL { 0 }
::= { mplsTunnelEntry 8 } ::= { mplsTunnelEntry 8 }
mplsTunnelSignallingProto OBJECT-TYPE mplsTunnelSignallingProto OBJECT-TYPE
SYNTAX INTEGER { none(1), ldp(2), rsvp(3), SYNTAX INTEGER {
other(4) } none(1),
rsvp(2),
crldp(3),
other(4)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The signaling protocol, if any, which was used "The signaling protocol, if any, which was used to
to setup this tunnel." setup this tunnel."
DEFVAL { none } DEFVAL { none }
::= { mplsTunnelEntry 9 } ::= { mplsTunnelEntry 9 }
mplsTunnelLocalCookie OBJECT-TYPE
SYNTAX MplsTunnelCookie
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local cookie assigned to the outgoing
direction of this tunnel at this LSR."
::= { mplsTunnelEntry 10 }
mplsTunnelRemoteCookie OBJECT-TYPE
SYNTAX MplsTunnelCookie
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The remote cookie assigned to the incoming
direction of tunnel by the remote (head-end)
LSR."
::= { mplsTunnelEntry 11 }
mplsTunnelSetupPrio OBJECT-TYPE mplsTunnelSetupPrio OBJECT-TYPE
SYNTAX INTEGER (0..7) SYNTAX INTEGER (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. Extensions to RSVP for LSP Tunnels, Awduche "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
et al, Internet Draft <draft-mpls-rsvp-lsp- Awduche et al, Internet Draft <draft-mpls-rsvp-lsp-
tunnel-02.txt>, March 1999., tunnel-05.txt>, February 2000.,
2. Constraint-Based LSP Setup using LDP, 2. Constraint-Based LSP Setup using LDP, Jamoussi,
Jamoussi, Internet Draft <draft-ietf-mpls-cr-ldp- Internet Draft <draft-ietf-mpls-cr-ldp-03.txt>,
01.txt>, Feb. 1999." September 1999."
::= { mplsTunnelEntry 12 } ::= { mplsTunnelEntry 10 }
mplsTunnelHoldingPrio OBJECT-TYPE mplsTunnelHoldingPrio OBJECT-TYPE
SYNTAX INTEGER (0..7) SYNTAX INTEGER (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. Extensions to RSVP for LSP Tunnels, Awduche "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
et al, Internet Draft <draft-mpls-rsvp-lsp- Awduche et al, Internet Draft <draft-mpls-rsvp-lsp-
tunnel-02.txt>, March 1999. tunnel-05.txt>, February 2000.,
2. Constraint-Based LSP Setup using LDP, B. 2. Constraint-Based LSP Setup using LDP, Jamoussi,
Jamoussi, Internet Draft <draft-ietf-mpls-cr-ldp- Internet Draft <draft-ietf-mpls-cr-ldp-03.txt>,
01.txt>, Feb. 1999." September 1999."
::= { mplsTunnelEntry 13 } ::= { mplsTunnelEntry 11 }
mplsTunnelSessionAttributes OBJECT-TYPE mplsTunnelSessionAttributes OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
ingressMayReroute (0), fastReroute (0),
mergingPermitted (1), mergingPermitted (1),
isPersistent (2), isPersistent (2),
localProtectionAvailable (3), localProtectionAvailable (3),
isPinned (4) isPinned (4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates optional session values "This bitmask indicates optional session values for
for this tunnel. The following describes these this tunnel. The following describes these
bitfields: bitfields:
fastReroute: This flag indicates that the tunnel fastReroute This flag indicates that the
ingress node may choose to reroute this tunnel any tunnel hop may choose to
without tearing it down. reroute this tunnel without
tearing it down.
mergingPermitted: This flag permits transit mergingPermitted This flag permits transit
routers to merge this session with other RSVP routers to merge this session
sessions for the purpose of reducing resource with other RSVP sessions for
overhead on downstream transit routers, thereby the purpose of reducing
providing better network scalability. resource overhead on
downstream transit routers,
thereby providing better
network scalability.
isPersistent: Indicates whether this tunnel isPersistant Indicates whether this tunnel
should be restored automatically after a failure should be restored
automatically after a failure
occurs. occurs.
localProtectionAvailable: This flag permits localProtectionAvailable This flag permits transit
transit routers to use a local repair mechanism routers to use a local repair
which may result in violation of the explicit mechanism which may result in
routing of this tunnel. When a fault is violation of the explicit
det4ected on an adjacent downstream link or routing of this tunnel. When a
node, a transit router can reroute traffic for fault is detected on an
fast service restoration. adjacent downstream link or
node, a transit router can
reroute traffic for fast
service restoration.
isPinned: This flag Indicates whether the loose- isPinned This flag indicates whether
routed hops of this tunnel are to be pinned." the loose-routed hops of this
tunnel are to be pinned."
REFERENCE REFERENCE
"Extensions to RSVP for LSP Tunnels, Awduche et "1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
al, Internet Draft <draft-mpls-rsvp-lsp-tunnel- Awduche et al, Internet Draft <draft-mpls-rsvp-lsp-
02.txt>, March 1999." tunnel-05.txt>, February 2000."
::= { mplsTunnelEntry 14 } DEFVAL { 0 }
::= { mplsTunnelEntry 12 }
mplsTunnelOwner OBJECT-TYPE mplsTunnelOwner OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
snmp (1), admin(1), -- represents all management entities
ldp (2), rsvp(2),
rsvp (3), crldp(3),
policyAgent (4), policyAgent (4),
other (5) other (5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates which protocol created and is "Indicates which protocol created and is responsible
responsible for managing this tunnel." for managing this tunnel. Values rsvp(2) and
crldp(3) should not be used at the head-end of a
MPLS tunnel."
::= { mplsTunnelEntry 13 }
mplsTunnelLocalProtectInUse OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates that the local repair mechanism is in use
to maintain this tunnel (usually in the face of an
outage of the link it was previously routed over)."
::= { mplsTunnelEntry 14 }
mplsTunnelResourcePointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable represents a pointer to the traffic
parameter specification for this tunnel. This value
may point at an entry in the mplsTunnelResourceEntry
to indicate which mplsTunnelResourceEntry is to be
assigned to this segment. This value may optionally
point at an externally defined traffic parameter
specification table. A value of zeroDotZero
indicates best-effort treatment. By having the same
value of this object, two or more segments can
indicate resource sharing."
::= { mplsTunnelEntry 15 } ::= { mplsTunnelEntry 15 }
mplsTunnelResourceEntryIndex OBJECT-TYPE mplsTunnelInstancePriority OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates which entry from the "This value indicates which priority, in descending
mplsTunnelResourceTable is currently in use by order with 0 indicating the lowest priority, within
this tunnel." a group of tunnel instances. A group of tunnel
instances is defined as a set of tunnels with the
same mplsTunnelIndex in this table, but with a
different mplsTunnelInstance. Tunnel group
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 16 } ::= { mplsTunnelEntry 16 }
mplsTunnelInstancePriority OBJECT-TYPE mplsTunnelHopTableIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates which priority, in "Index into the mplsTunnelHopTable entry that
descending order with 0 indicating the lowest specifies the explicit route hops for this tunnel."
priority, within a group of tunnel instances. A
group of tunnel instances is defined as a set of
tunnels with the same mplsTunnelIndex in this
table, but with a different mplsTunnelInstance.
Tunnel group priorities are used to denote the
priority at which particular a tunnel instance
will supercede another. Instances of tunnels
containing the same mplsTunnelInstancePriority
will be used for load sharing."
::= { mplsTunnelEntry 17 } ::= { mplsTunnelEntry 17 }
mplsTunnelARHopTableIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index into the mplsTunnelARHopTable entry that
specifies the actual hops traversed by the tunnel."
::= { mplsTunnelEntry 18 }
mplsTunnelAdminStatus OBJECT-TYPE mplsTunnelAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- ready to pass packets up(1), -- ready to pass packets
down(2), down(2),
testing(3) -- in some test mode testing(3) -- in some test mode
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the desired operational status of this "Indicates the desired operational status of this
tunnel." tunnel."
::= { mplsTunnelEntry 18 } ::= { mplsTunnelEntry 19 }
mplsTunnelOperStatus OBJECT-TYPE mplsTunnelOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- ready to pass packets up(1), -- ready to pass packets
down(2), down(2),
testing(3), -- in some test mode testing(3), -- in some test mode
unknown(4), -- status cannot be determined unknown(4), -- status cannot be determined
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerDown(7) -- down due to the state of lowerLayerDown(7) -- down due to the state of
-- lower layer interfaces -- lower layer interfaces
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the actual operational status of this "Indicates the actual operational status of this
tunnel, which is typically but not limited to, a tunnel, which is typically but not limited to, a
function of the state of individual segments of function of the state of individual segments of this
this tunnel." tunnel."
::= { mplsTunnelEntry 19 } ::= { mplsTunnelEntry 20 }
mplsTunnelRowStatus OBJECT-TYPE mplsTunnelRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table."
::= { mplsTunnelEntry 20 } ::= { mplsTunnelEntry 21 }
mplsTunnelResourceIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the next appropriate value
to be used for mplsTunnelResourceIndex when
creating entries in the mplsTunnelResourceTable.
If the number of unassigned entries is
exhausted, this object will take on the value of
0. 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. The
agent should modify the value to reflect the
next unassigned index after each retrieval
operation. After a manager retrieves a value the
agent will determine through its local policy
when this index value will be made available for
reuse."
::= { mplsTeObjects 3 }
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 4 }
mplsTunnelResourceEntry OBJECT-TYPE
SYNTAX MplsTunnelResourceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a set of
resources for an MPLS tunnel. An entry can be
created by a network administrator or by an SNMP
agent as instructed by any MPLS signaling
protocol."
INDEX { mplsTunnelResourceIndex }
::= { mplsTunnelResourceTable 1 }
MplsTunnelResourceEntry ::= SEQUENCE {
mplsTunnelResourceIndex Unsigned32,
mplsTunnelResourceInMaxRate MplsBitRate,
mplsTunnelResourceInMeanRate MplsBitRate,
mplsTunnelResourceInMaxBurstSize MplsBurstSize,
mplsTunnelResourceOutMaxRate MplsBitRate,
mplsTunnelResourceOutMeanRate MplsBitRate,
mplsTunnelResourceOutMaxBurstSize MplsBurstSize,
mplsTunnelResourceRowStatus RowStatus
}
mplsTunnelResourceIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Uniquely identifies this row."
::= { mplsTunnelResourceEntry 1 }
mplsTunnelResourceInMaxRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum incoming rate in bits/second. Note
that setting mplsTunnelInMaxRate,
mplsTunnelInMeanRate, and
mplsTunnelInMaxBurstSize to 0 indicates best-
effort treatment.
This object is copied to an instance of
mplsTSpecMaxRate in mplsTSpecTable the index of
which is copied into the corresponding
mplsInSegmentTSpecIndex."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, March 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 2 }
mplsTunnelResourceInMeanRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is copied into an instance of
mplsTSpecMeanRate in the mplsTSpecTable. The
index of this table is then copied into the
corresponding mplsInSegmentTSpecIndex.
When resource allocation is performed as
requested by this TSpec object, it is copied
into an entry in mplsTSpecTable [LSRMIB]:
mplsTunnelInMeanRate to mplsTSpecMeanRate. The
mplsTSpecDirection of this entry is set to
‘in’(1). The mplsTSpecIndex value of this entry
is copied to mplsInSegmentTSpecIndex of the
corresponding in-segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, Feb. 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 3 }
mplsTunnelResourceInMaxBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum burst size in bytes. This object is
copied to mplsInSegmentMaxBurstSize of the
corresponding in-segment.
When resource allocation is performed as
requested by this TSpec object, it is copied
into an entry in mplsTSpecTable [LSRMIB]:
mplsTunnelInMaxBurstSize to
mplsTSpecMaxBurstSize. The mplsTSpecDirection of
this entry is set to ‘in’ (1). The
mplsTSpecIndex value of this entry is copied to
mplsInSegmentTSpecIndex of the corresponding in-
segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, March 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 4 }
mplsTunnelResourceOutMaxRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum outgoing rate in bits/second. Note
that setting mplsTunnelOutMaxRate to 0 indicates
best-effort treatment. This object is copied to
mplsOutSegmentMaxRate of the corresponding out-
segment.
When resource allocation is performed as
requested by the following outgoing TSpec
object, it is copied into an entry in
mplsTSpecTable [LSRMIB] as follows:
mplsTunnelOutMaxRate to mplsTSpecMaxRate. Also
note that the mplsTSpecDirection of this entry
is set to out (2). The mplsTSpecIndex value of
this entry is copied to mplsOutSegmentTSpecIndex
of the corresponding out-segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and Nadeau, T.,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, March 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 5 }
mplsTunnelResourceOutMeanRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The mean outgoing rate in bits/second. Note that
setting mplsTunnelOutMeanRate to 0 indicates
best-effort treatment. This object is copied to
mplsOutSegmentMeanRate of the corresponding out-
segment.
When resource allocation is performed as
requested by the following outgoing TSpec
object, it is copied into an entry in
mplsTSpecTable [LSRMIB] as follows:
mplsTunnelOutMeanRate to mplsTSpecMeanRate. Also
note that the mplsTSpecDirection of this entry
is set to out (2). The mplsTSpecIndex value of
this entry is copied to mplsOutSegmentTSpecIndex
of the corresponding out-segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, March 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 6 }
mplsTunnelResourceOutMaxBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum burst size in bytes. This object is
copied to mplsOutSegmentMaxBurstSize of the
corresponding out-segment. Note that setting
mplsTunnelOutMaxBurstSize to 0 indicates best-
effort treatment.
When resource allocation is performed as
requested by the following outgoing TSpec
object, it is copied into an entry in
mplsTSpecTable [LSRMIB] as follows:
mplsTunnelOutMaxBurstSize to
mplsTSpecMaxBurstSize. Also note that the
mplsTSpecDirection of this entry is set to out
(2). The mplsTSpecIndex value of this entry is
copied to mplsOutSegmentTSpecIndex of the
corresponding out-segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau,
MPLS Label Switch Router Management Information
Base Using SMIv2, Internet Draft <draft-ietf-
mpls-lsr-mib-01.txt>, March 2000."
DEFVAL { 0 }
::= { mplsTunnelResourceEntry 7 }
mplsTunnelResourceRowStatus OBJECT-TYPE mplsTunnelStorageType OBJECT-TYPE
SYNTAX RowStatus SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable indicates the storage type for this
delete a row in this table." object."
::= { mplsTunnelResourceEntry 8 } ::= { mplsTunnelEntry 22 }
-- End of mplsTunnelTable
-- Maximum number of tunnel hops supported. -- Maximum number of tunnel hops supported.
mplsTunnelMaxHops OBJECT-TYPE mplsTunnelMaxHops OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of hops that can be specified "The maximum number of hops that can be specified for
for a tunnel on this device." a tunnel on this device."
::= { mplsTeObjects 5 } ::= { mplsTeObjects 3 }
-- Tunnel hop table. -- Tunnel hop table.
mplsTunnelHopIndexNext OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to be used
for mplsTunnelHopListIndex when creating entries in
the mplsTunnelHopTable. If the number of unassigned
entries is exhausted, a retrival operation will
return a value of 0. This object may also return a
value of 0 when the LSR is unable to accept
conceptual row creation, for example, if the
mplsTunnelHopTable is implemented as read-only. To
obtain the value of mplsTunnelHopListIndex for a new
entry in the mplsTunnelHopTable, the manager issues
a management protocol retrieval operation to obtain
the current value of mplsTunnelHopIndex. After each
retrieval operation, the agent should modify the
value to reflect the next unassigned index. After a
manager retrieves a value the agent will determine
through its local policy when this index value will
be made available for reuse."
::= { mplsTeObjects 4 }
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 "The mplsTunnelHopTable is used to indicate the hops,
hops, strict or loose, for an MPLS tunnel strict or loose, for an MPLS tunnel defined in
defined in mplsTunnelTable, when it is mplsTunnelTable, when it is established via
established via signaling, for the outgoing signaling, for the outgoing direction of the tunnel.
direction of the tunnel. Each row in this table Each row in this table is indexed primarily by the
is indexed primarily by the same index, same index, mplsTunnelIndex, as the row of the
mplsTunnelIndex, as the row of the corresponding corresponding tunnel in mplsTunnelTable. Each row
tunnel in mplsTunnelTable. Each row also has a also has a secondary index mplsTunnelHopIndex
secondary index mplsTunnelHopIndex corresponding corresponding to the next hop that this row
to the next hop that this row corresponds to. corresponds to. The first row in the table is the
The first row in the table is the first hop first hop after the origination point of the tunnel.
after the origination point of the tunnel. In In case we want to specify a particular interface on
case we want to specify a particular interface the originating LSR of an outgoing tunnel by which
on the originating LSR of an outgoing tunnel by we want packets to exit the LSR, we specify this as
which we want packets to exit the LSR, we the first hop for this tunnel in
specify this as the first hop for this tunnel in
mplsTunnelHopTable." mplsTunnelHopTable."
::= { mplsTeObjects 6 } ::= { mplsTeObjects 5 }
mplsTunnelHopEntry OBJECT-TYPE mplsTunnelHopEntry OBJECT-TYPE
SYNTAX MplsTunnelHopEntry SYNTAX MplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a tunnel hop. "An entry in this table represents a tunnel hop. An
An entry is created by a network administrator entry is created by a network administrator for
for signaled ERLSP set up by an MPLS signaling signaled ERLSP set up by an MPLS signaling
protocol." protocol."
INDEX { mplsTunnelIndex, mplsTunnelInstance, INDEX { mplsTunnelHopListIndex, mplsTunnelHopIndex }
mplsTunnelHopIndex }
::= { mplsTunnelHopTable 1 } ::= { mplsTunnelHopTable 1 }
MplsTunnelHopEntry ::= SEQUENCE { MplsTunnelHopEntry ::= SEQUENCE {
mplsTunnelHopListIndex Integer32,
mplsTunnelHopIndex Integer32, mplsTunnelHopIndex Integer32,
mplsTunnelHopAddrType INTEGER, mplsTunnelHopAddrType INTEGER,
mplsTunnelHopIpv4Addr IpAddress, mplsTunnelHopIpv4Addr InetAddressIPv4,
mplsTunnelHopIpv4PrefixLen INTEGER, mplsTunnelHopIpv4PrefixLen INTEGER,
mplsTunnelHopIpv6Addr Ipv6Address, mplsTunnelHopIpv6Addr InetAddressIPv6,
mplsTunnelHopIpv6PrefixLen INTEGER, mplsTunnelHopIpv6PrefixLen INTEGER,
mplsTunnelHopAsNumber INTEGER, mplsTunnelHopAsNumber INTEGER,
mplsTunnelHopLspId MplsLSPID,
mplsTunnelHopStrictOrLoose INTEGER, mplsTunnelHopStrictOrLoose INTEGER,
mplsTunnelHopRowStatus RowStatus mplsTunnelHopRowStatus RowStatus,
mplsTunnelHopStorageType StorageType
} }
mplsTunnelHopListIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Primary index into this table identifying a
particular explicit route object."
::= { mplsTunnelHopEntry 1 }
mplsTunnelHopIndex OBJECT-TYPE mplsTunnelHopIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Secondary index into this table identifying the "Secondary index into this table identifying a
particular hop." particular hop."
::= { mplsTunnelHopEntry 1 } ::= { mplsTunnelHopEntry 2 }
mplsTunnelHopAddrType OBJECT-TYPE mplsTunnelHopAddrType OBJECT-TYPE
SYNTAX INTEGER { ipV4(1), ipV6(2), asNumber(3) SYNTAX INTEGER {
ipV4(1),
ipV6(2),
asNumber(3),
lspid(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the address type of this tunnel hop." "Denotes the address type of this tunnel hop."
DEFVAL { ipV4 } DEFVAL { ipV4 }
::= { mplsTunnelHopEntry 2 } ::= { mplsTunnelHopEntry 3 }
mplsTunnelHopIpv4Addr OBJECT-TYPE mplsTunnelHopIpv4Addr OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is set to ipV4(1), then "If mplsTunnelHopAddrType is set to ipV4(1), then
this value will contain the IPv4 address of this this value will contain the IPv4 address of this
hop. This object is otherwise insignificant and hop. This object is otherwise insignificant and
should contain a value of 0." should contain a value of 0."
::= { mplsTunnelHopEntry 3 } ::= { mplsTunnelHopEntry 4 }
mplsTunnelHopIpv4PrefixLen OBJECT-TYPE mplsTunnelHopIpv4PrefixLen OBJECT-TYPE
SYNTAX INTEGER (1..32) SYNTAX INTEGER (1..32)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is ipV4(1), then the "If mplsTunnelHopAddrType is ipV4(1), then the prefix
prefix length for this hop's IPv4 address is length for this hop's IPv4 address is contained
contained herein. This object is otherwise herein. This object is otherwise insignificant and
insignificant and should contain a value of 0." should contain a value of 0."
::= { mplsTunnelHopEntry 4 } ::= { mplsTunnelHopEntry 5 }
mplsTunnelHopIpv6Addr OBJECT-TYPE mplsTunnelHopIpv6Addr OBJECT-TYPE
SYNTAX Ipv6Address SYNTAX InetAddressIPv6
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the mplsTunnelHopAddrType is set to ipV6(2), "If the mplsTunnelHopAddrType is set to ipV6(2), then
then this variable contains the IPv6 address of this variable contains the IPv6 address of this hop.
this hop. This object is otherwise This object is otherwise insignificant and should
insignificant and should contain a value of 0." contain a value of 0."
::= { mplsTunnelHopEntry 5 } ::= { mplsTunnelHopEntry 6 }
mplsTunnelHopIpv6PrefixLen OBJECT-TYPE mplsTunnelHopIpv6PrefixLen OBJECT-TYPE
SYNTAX INTEGER (1..128) SYNTAX INTEGER (1..128)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is set to ipV6(2), this "If mplsTunnelHopAddrType is set to ipV6(2), this
value will contain the prefix length for this value will contain the prefix length for this hop's
hop's IPv6 address. This object is otherwise IPv6 address. This object is otherwise insignificant
insignificant and should contain a value of 0." and should contain a value of 0."
::= { mplsTunnelHopEntry 6 } ::= { mplsTunnelHopEntry 7 }
mplsTunnelHopAsNumber OBJECT-TYPE mplsTunnelHopAsNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelHopAddrType is set to asNumber(3), "If mplsTunnelHopAddrType is set to asNumber(3), then
then this value will contain the AS number of this value will contain the AS number of this hop.
this hop. This object is otherwise insignificant This object is otherwise insignificant and should
and should contain a value of 0 to indicate this contain a value of 0 to indicate this fact."
fact." ::= { mplsTunnelHopEntry 8 }
::= { mplsTunnelHopEntry 7 }
mplsTunnelHopLspId OBJECT-TYPE
SYNTAX MplsLSPID
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If mplsTunnelHopAddrType is set to lspid(4), then
this value will contain the LSPID of a tunnel of
this hop. The present tuunel being configured is
‘tunneled’ through this hop (using label stacking).
This object is otherwise insignificant and should
contain a value of 0 to indicate this fact."
::= { mplsTunnelHopEntry 9 }
mplsTunnelHopStrictOrLoose OBJECT-TYPE mplsTunnelHopStrictOrLoose OBJECT-TYPE
SYNTAX INTEGER { strict(1), loose(2) } SYNTAX INTEGER {
strict(1),
loose(2)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether this is tunnel hop is routed in "Denotes whether this tunnel hop is routed in a
a strict or loose fashion." strict or loose fashion."
::= { mplsTunnelHopEntry 8 } ::= { mplsTunnelHopEntry 10 }
mplsTunnelHopRowStatus OBJECT-TYPE mplsTunnelHopRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table."
::= { mplsTunnelHopEntry 9 } ::= { mplsTunnelHopEntry 11 }
mplsTunnelHopStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { mplsTunnelHopEntry 12 }
-- End of mplsTunnelHopTable -- End of mplsTunnelHopTable
-- Begin of mplsTunnelResourceTable
mplsTunnelResourceIndexNext OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the next appropriate value to
be used for mplsTunnelResourceIndex when creating
entries in the mplsTunnelResourceTable. If the
number of unassigned entries is exhausted, a
retrival operation will return a value of 0. This
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. The agent should
modify the value to reflect the next unassigned
index after each retrieval operation. After a
manager retrieves a value the agent will determine
through its local policy when this index value will
be made available for reuse."
::= { mplsTeObjects 6 }
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 7 }
mplsTunnelResourceEntry OBJECT-TYPE
SYNTAX MplsTunnelResourceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a set of resources
for an MPLS tunnel. An entry can be created by a
network administrator or by an SNMP agent as
instructed by any MPLS signaling protocol."
INDEX { mplsTunnelResourceIndex }
::= { mplsTunnelResourceTable 1 }
MplsTunnelResourceEntry ::= SEQUENCE {
mplsTunnelResourceIndex Integer32,
mplsTunnelResourceMaxRate MplsBitRate,
mplsTunnelResourceMeanRate MplsBitRate,
mplsTunnelResourceMaxBurstSize MplsBurstSize,
mplsTunnelResourceRowStatus RowStatus,
mplsTunnelResourceStorageType StorageType
}
mplsTunnelResourceIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Uniquely identifies this row."
::= { mplsTunnelResourceEntry 1 }
mplsTunnelResourceMaxRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum rate in bits/second. Note that setting
mplsTunnelResourceMaxRate,
mplsTunnelResourceMeanRate, and
mplsTunnelResourceMaxBurstSize to 0 indicates best-
effort treatment.
This object is copied to an instance of
mplsTSpecMaxRate in mplsTSpecTable the index of
which is copied into the corresponding
mplsInSegmentTSpecIndex."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS
Label Switch Router Management Information Base
Using SMIv2, Internet Draft <draft-ietf-mpls-lsr-mib-
04.txt>, April 26, 2000."
::= { mplsTunnelResourceEntry 2 }
mplsTunnelResourceMeanRate OBJECT-TYPE
SYNTAX MplsBitRate
UNITS "bits per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is copied into an instance of
mplsTSpecMeanRate in the mplsTSpecTable. The index
of this table is then copied into the corresponding
mplsInSegmentTSpecIndex.
When resource allocation is performed as requested
by this TSpec object, it is copied into an entry in
mplsTSpecTable [LSRMIB]: mplsTunnelInMeanRate to
mplsTSpecMeanRate. The mplsTSpecDirection of this
entry is set to ‘in’(1). The mplsTSpecIndex value
of this entry is copied to mplsInSegmentTSpecIndex
of the corresponding in-segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS
Label Switch Router Management Information Base
Using SMIv2, Internet Draft <draft-ietf-mpls-lsr-mib-
04.txt>, April 26, 2000."
::= { mplsTunnelResourceEntry 3 }
mplsTunnelResourceMaxBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum burst size in bytes. This object is
copied to mplsInSegmentMaxBurstSize of the
corresponding in-segment.
When resource allocation is performed as requested
by this TSpec object, it is copied into an entry in
mplsTSpecTable [LSRMIB]: mplsTunnelInMaxBurstSize to
mplsTSpecMaxBurstSize. The mplsTSpecDirection of
this entry is set to ‘in’(1). The mplsTSpecIndex
value of this entry is copied to
mplsInSegmentTSpecIndex of the corresponding in-
segment entry."
REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS
Label Switch Router Management Information Base
Using SMIv2, Internet Draft <draft-ietf-mpls-lsr-mib-
04.txt>, April 26, 2000."
::= { mplsTunnelResourceEntry 4 }
mplsTunnelResourceRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { mplsTunnelResourceEntry 5 }
mplsTunnelResourceStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { mplsTunnelResourceEntry 6 }
-- End mplsTunnelResourceTable
-- Tunnel Actual Route Hop table. -- Tunnel Actual Route Hop table.
mplsTunnelARHopTable OBJECT-TYPE mplsTunnelARHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelARHopEntry SYNTAX SEQUENCE OF MplsTunnelARHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mplsTunnelARHopTable is used to indicate the "The mplsTunnelARHopTable is used to indicate the
(A)ctual (R)oute hops, for an MPLS tunnel hops, strict or loose, for an MPLS tunnel defined in
defined in mplsTunnelTable, as set up by the mplsTunnelTable, as reported by the MPLS signaling
specified MPLS signaling protocol, for the protocol, for the outgoing direction of the tunnel.
outgoing direction of the tunnel. Each row in Each row in this table is indexed primarily by the
this table is indexed primarily by the same same indices, mplsTunnelIndex and
indices, mplsTunnelIndex and mplsTunnelInstance, mplsTunnelInstance, as the row of the corresponding
as the row of the corresponding tunnel in tunnel in mplsTunnelTable. Each row also has a
mplsTunnelTable. Each row also has a third third index mplsTunnelARHopIndex, corresponding to
index mplsTunnelARHopIndex, corresponding to the the next hop that this row corresponds to. The
next hop that this row corresponds to. The first row in the table is the first hop after the
first row in the table is the first hop after origination point of the tunnel. In case we want to
the origination point of the tunnel. 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 mplsTunnelARHopTable.
Please note that since the information necessary Please note that since the information necessary to
to build entries within this table are not build entries within this table are not provided by
provided by some MPLS signaling protocols; hence some MPLS signaling protocols, implementation of
implementation of this table is optional. The this table is optional. Furthermore, since the
information in this table is available from the information in this table is actually provided by
MPLS signaling protocol after the path has been the MPLS signaling protocol after the path has been
set-up." set-up, the entries in this table are provided only
::= { mplsTeObjects 7 } for observation, and hence, all variables in this
table are accessible exclusively as read-only."
::= { mplsTeObjects 8 }
mplsTunnelARHopEntry OBJECT-TYPE mplsTunnelARHopEntry OBJECT-TYPE
SYNTAX MplsTunnelARHopEntry SYNTAX MplsTunnelARHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents an currently "An entry in this table represents a tunnel hop. An
active tunnel hop. An entry is created in this entry is created by a network administrator for
table by the MPLS signaling protocol when the signaled ERLSP set up by an MPLS signaling
active path for this tunnel is known." protocol."
INDEX { mplsTunnelIndex, mplsTunnelInstance, INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex }
mplsTunnelARHopIndex }
::= { mplsTunnelARHopTable 1 } ::= { mplsTunnelARHopTable 1 }
MplsTunnelARHopEntry ::= SEQUENCE { MplsTunnelARHopEntry ::= SEQUENCE {
mplsTunnelARHopListIndex Integer32,
mplsTunnelARHopIndex Integer32, mplsTunnelARHopIndex Integer32,
mplsTunnelARHopAddrType INTEGER, mplsTunnelARHopAddrType INTEGER,
mplsTunnelARHopIpv4Addr IpAddress, mplsTunnelARHopIpv4Addr InetAddressIPv4,
mplsTunnelARHopIpv4PrefixLen INTEGER, mplsTunnelARHopIpv4PrefixLen INTEGER,
mplsTunnelARHopIpv6Addr Ipv6Address, mplsTunnelARHopIpv6Addr InetAddressIPv6,
mplsTunnelARHopIpv6PrefixLen INTEGER, mplsTunnelARHopIpv6PrefixLen INTEGER,
mplsTunnelARHopAsNumber INTEGER mplsTunnelARHopAsNumber INTEGER,
mplsTunnelARHopStrictOrLoose INTEGER
} }
mplsTunnelARHopListIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Primary index into this table identifying a
particular recorded hop list."
::= { mplsTunnelARHopEntry 1 }
mplsTunnelARHopIndex OBJECT-TYPE mplsTunnelARHopIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Secondary index into this table identifying the "Secondary index into this table identifying the
particular hop." particular hop."
::= { mplsTunnelARHopEntry 1 } ::= { mplsTunnelARHopEntry 2 }
mplsTunnelARHopAddrType OBJECT-TYPE mplsTunnelARHopAddrType OBJECT-TYPE
SYNTAX INTEGER { ipV4(1), ipV6(2), asNumber(3) SYNTAX INTEGER {
ipV4(1),
ipV6(2),
asNumber(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the address type of this tunnel hop." "Denotes the address type of this tunnel hop."
DEFVAL { ipV4 } DEFVAL { ipV4 }
::= { mplsTunnelARHopEntry 2 } ::= { mplsTunnelARHopEntry 3 }
mplsTunnelARHopIpv4Addr OBJECT-TYPE mplsTunnelARHopIpv4Addr OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelARHopAddrType is set to ipV4(1), "If mplsTunnelARHopAddrType is set to ipV4(1), then
then this value will contain the IPv4 address of this value will contain the IPv4 address of this
this hop. This object is otherwise insignificant hop. This object is otherwise insignificant and
and should contain a value of 0." should contain a value of 0."
::= { mplsTunnelARHopEntry 3 } ::= { mplsTunnelARHopEntry 4 }
mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE
SYNTAX INTEGER (1..32) SYNTAX INTEGER (1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelARHopAddrType is ipV4(1), then the "If mplsTunnelARHopAddrType is ipV4(1), then the
prefix length for this hop's IPv4 address is prefix length for this hop's IPv4 address is
contained herein. This object is otherwise contained herein. This object is otherwise
insignificant and should contain a value of 0." insignificant and should contain a value of 0."
::= { mplsTunnelARHopEntry 4 } ::= { mplsTunnelARHopEntry 5 }
mplsTunnelARHopIpv6Addr OBJECT-TYPE mplsTunnelARHopIpv6Addr OBJECT-TYPE
SYNTAX Ipv6Address SYNTAX InetAddressIPv6
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the mplsTunnelARHopAddrType is set to "If the mplsTunnelARHopAddrType is set to ipV6(2),
ipV6(2), then this variable contains the IPv6 then this variable contains the IPv6 address of this
address of this hop. This object is otherwise hop. This object is otherwise insignificant and
insignificant and should contain a value of 0." should contain a value of 0."
::= { mplsTunnelARHopEntry 5 } ::= { mplsTunnelARHopEntry 6 }
mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE
SYNTAX INTEGER (1..128) SYNTAX INTEGER (1..128)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelARHopAddrType is set to ipV6(2), "If mplsTunnelARHopAddrType is set to ipV6(2), this
this value will contain the prefix length for value will contain the prefix length for this hop's
this hop's IPv6 address. This object is IPv6 address. This object is otherwise insignificant
otherwise insignificant and should contain a and should contain a value of 0."
value of 0." ::= { mplsTunnelARHopEntry 7 }
::= { mplsTunnelARHopEntry 6 }
mplsTunnelARHopAsNumber OBJECT-TYPE mplsTunnelARHopAsNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsTunnelARHopAddrType is set to "If mplsTunnelARHopAddrType is set to asNumber(3),
asNumber(3), then this value will contain the AS then this value will contain the AS number of this
number of this hop. This object is otherwise hop. This object is otherwise insignificant and
insignificant and should contain a value of 0 to should contain a value of 0 to indicate this fact."
indicate this fact." ::= { mplsTunnelARHopEntry 8 }
::= { mplsTunnelARHopEntry 7 }
mplsTunnelARHopStrictOrLoose OBJECT-TYPE
SYNTAX INTEGER {
strict(1),
loose(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Denotes whether this is tunnel hop is routed in a
strict or loose fashion."
::= { mplsTunnelARHopEntry 9 }
-- End of mplsTunnelARHopTable -- End of mplsTunnelARHopTable
-- Notifications. -- Notifications.
mplsTunnelTrapEnable 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 9 }
mplsTunnelUp NOTIFICATION-TYPE mplsTunnelUp NOTIFICATION-TYPE
OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, OBJECTS { mplsTunnelIndex,
mplsTunnelOperStatus } mplsTunnelInstance,
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsTunnelOperStatus object for one of the mplsTunnelOperStatus object for one of the
configured tunnels is about to leave the down configured tunnels is about to leave the down state
state and transition into some other state (but and transition into some other state (but not into
not into the notPresent state). This other the notPresent state). This other state is
state is indicated by the included value of indicated by the included value of
mplsTunnelOperStatus." mplsTunnelOperStatus."
::= { mplsTeNotifications 1 } ::= { mplsTeNotifyPrefix 1 }
mplsTunnelDown NOTIFICATION-TYPE mplsTunnelDown NOTIFICATION-TYPE
OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, OBJECTS { mplsTunnelIndex,
mplsTunnelOperStatus } mplsTunnelInstance,
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsTunnelOperStatus object for one of the mplsTunnelOperStatus object for one of the
configured tunnels is about to enter the down configured tunnels is about to enter the down state
state from some other state (but not from the from some other state (but not from the notPresent
notPresent state). This other state is state). This other state is indicated by the
indicated by the included value of included value of mplsTunnelOperStatus."
mplsTunnelOperStatus." ::= { mplsTeNotifyPrefix 2 }
::= { mplsTeNotifications 2 }
mplsTunnelRerouted NOTIFICATION-TYPE
OBJECTS { mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelAdminStatus,
mplsTunnelOperStatus
}
STATUS current
DESCRIPTION
"This notification is generated when a tunnel is
rerouted or re-optimized. If the Actual Path is
used, then this object MAY contain the new path for
this tunnel some time after this trap is issued by
the agent."
::= { mplsTeNotifyPrefix 3 }
-- End of notifications. -- End of notifications.
-- Module compliance. -- Module compliance.
mplsTeGroups mplsTeGroups
OBJECT IDENTIFIER ::= { mplsTeConformance 1 } OBJECT IDENTIFIER ::= { mplsTeConformance 1 }
mplsTeCompliances mplsTeCompliances
OBJECT IDENTIFIER ::= { mplsTeConformance 2 } OBJECT IDENTIFIER ::= { mplsTeConformance 2 }
skipping to change at page 50, line 23 skipping to change at page 35, line 4
MPLS TE MIB." MPLS TE MIB."
MODULE -- this module MODULE -- this module
-- The mandatory group has to be implemented by all -- The mandatory group has to be implemented by all
-- LSRs that originate/terminate ESLSPs/tunnels. -- LSRs that originate/terminate ESLSPs/tunnels.
-- In addition, depending on the type of tunnels -- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as -- supported, other groups become mandatory as
-- explained below. -- explained below.
MANDATORY-GROUPS { mplsTunnelGroup } MANDATORY-GROUPS { mplsTunnelGroup }
GROUP mplsTunnelManualGroup GROUP mplsTunnelManualGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which support
support manual configuration of tunnels, in manual configuration of tunnels, in addition to
addition to mplsTunnelGroup. The following mplsTunnelGroup. The following constraints apply:
constraints apply: mplsTunnelSignallingProto mplsTunnelSignallingProto should be at least read-
should be at least read-only with a value of only with a value of none(1)."
none(1)."
GROUP mplsTunnelSignaledGroup GROUP mplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which support
support signaled tunnel set up, in addition signaled tunnel set up, in addition to
to mplsTunnelGroup. The following mplsTunnelGroup. The following constraints apply:
constraints apply: mplsTunnelSignallingProto mplsTunnelSignallingProto should be at least read-
should be at least read-only returning a only returning a value of ldp(2), or rsvp(3)."
value of ldp(2), or rsvp(3)."
GROUP mplsTunnelIsNotIntfcGroup GROUP mplsTunnelIsNotIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which support
support tunnels that are not interfaces, in tunnels that are not interfaces, in addition to
addition to mplsTunnelGroup. The following mplsTunnelGroup. The following constraints apply:
constraints apply: mplsTunnelIsIf must at mplsTunnelIsIf must at least be read-only
least be read-only returning false(1)." returning false(1)."
GROUP mplsTunnelIsIntfcGroup GROUP mplsTunnelIsIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which support
support tunnels that are interfaces, in tunnels that are interfaces, in addition to
addition to mplsTunnelGroup. The following mplsTunnelGroup. The following constraints apply:
constraints apply: mplsTunnelIsIf must at mplsTunnelIsIf must at least be read-only
least be read-only returning true(2)." returning true(2)."
-- mplsTunnelTable
OBJECT mplsTunnelIndex GROUP mplsTunnelOptionalGroup
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Objects in this group are optional."
OBJECT mplsTunnelInstance -- mplsTunnelTable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelName OBJECT mplsTunnelName
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelDescr OBJECT mplsTunnelDescr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelIsIf OBJECT mplsTunnelIsIf
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelIfIndex OBJECT mplsTunnelIfIndex
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelDirection OBJECT mplsTunnelXCPointer
SYNTAX INTEGER { out(2) }
MIN-ACCESS read-only
DESCRIPTION
"The values in(1) and in-out(3) need not be
supported."
OBJECT mplsTunnelXCIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSignallingProto OBJECT mplsTunnelSignallingProto
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelLocalCookie OBJECT mplsTunnelSetupPrio
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelRemoteCookie OBJECT mplsTunnelHoldingPrio
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSetupPrio OBJECT mplsTunnelSessionAttributes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelHoldingPrio OBJECT mplsTunnelOwner
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelSessionAttributes OBJECT mplsTunnelLocalProtectInUse
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelOwner OBJECT mplsTunnelResourcePointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelLocalProtectInUse OBJECT mplsTunnelInstancePriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelResourceEntryIndex OBJECT mplsTunnelHopTableIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelInstancePriority OBJECT mplsTunnelARHopTableIndex
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelAdminStatus OBJECT mplsTunnelAdminStatus
SYNTAX INTEGER { up (1), down (2) } SYNTAX INTEGER { up (1), down (2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only up and down states must be supported. "Only up and down states must be supported. Write
Write access is not required." access is not required."
OBJECT mplsTunnelOperStatus OBJECT mplsTunnelOperStatus
SYNTAX INTEGER { up (1), down (2) } SYNTAX INTEGER { up (1), down (2) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only up and down states must be supported. "Only up and down states must be supported. Write
Write access is not required." access is not required."
OBJECT mplsTunnelRowStatus OBJECT mplsTunnelRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states "The notReady(3) and createAndWait(5) states need
need not be supported. Write access is not not be supported. Write access is not required."
required."
-- mplsTunnelHopTable
OBJECT mplsTunnelHopIndex OBJECT mplsTunnelStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Only other (1) needs to be supported."
-- mplsTunnelHopTable
OBJECT mplsTunnelHopAddrType OBJECT mplsTunnelHopAddrType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelHopIpv4Addr OBJECT mplsTunnelHopIpv4Addr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 56, line 23 skipping to change at page 38, line 32
OBJECT mplsTunnelHopIpv6PrefixLen OBJECT mplsTunnelHopIpv6PrefixLen
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelHopAsNumber OBJECT mplsTunnelHopAsNumber
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelHopLspId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelHopStrictOrLoose OBJECT mplsTunnelHopStrictOrLoose
SYNTAX INTEGER { strict(1) } SYNTAX INTEGER { strict(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"loose(2) need not be supported. Write access "loose(2) need not be supported. Write access is
is not required." not required."
OBJECT mplsTunnelHopRowStatus OBJECT mplsTunnelHopRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states "The notReady(3) and createAndWait(5) states need
need not be supported. Write access is not not be supported. Write access is not required."
required." OBJECT mplsTunnelHopStorageType
SYNTAX INTEGER { other(1) }
-- mplsTunnelResourceTable
OBJECT mplsTunnelResourceInMaxRate
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelResourceInMeanRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Only other (1) needs to be supported."
OBJECT mplsTunnelResourceInMaxBurstSize -- mplsTunnelResourceTable
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsTunnelResourceOutMaxRate OBJECT mplsTunnelResourceMaxRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelResourceOutMeanRate OBJECT mplsTunnelResourceMeanRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelResourceOutMaxBurstSize OBJECT mplsTunnelResourceMaxBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsTunnelResourceRowStatus OBJECT mplsTunnelResourceRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states "The notReady(3) and createAndWait(5) states need
need not be supported. Write access is not not be supported. Write access is not required."
required."
OBJECT mplsTunnelResourceStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other (1) needs to be supported."
::= { mplsTeCompliances 1 } ::= { mplsTeCompliances 1 }
-- Units of conformance. -- Units of conformance.
mplsTunnelGroup OBJECT-GROUP mplsTunnelGroup OBJECT-GROUP
OBJECTS { mplsTunnelIndexNext, mplsTunnelIndex, OBJECTS { mplsTunnelIndexNext,
mplsTunnelInstance, mplsTunnelName,
mplsTunnelName, mplsTunnelDirection, mplsTunnelDescr,
mplsTunnelXCIndex, mplsTunnelOwner,
mplsTunnelIfIndex, mplsTunnelAdminStatus, mplsTunnelXCPointer,
mplsTunnelOperStatus, mplsTunnelRowStatus } mplsTunnelIfIndex,
mplsTunnelHopTableIndex,
mplsTunnelARHopTableIndex,
mplsTunnelAdminStatus,
mplsTunnelOperStatus,
mplsTunnelRowStatus,
mplsTunnelTrapEnable,
mplsTunnelStorageType,
mplsTunnelMaxHops,
mplsTunnelResourcePointer,
mplsTunnelInstancePriority
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to "Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on implement tunnels. In addition, depending on the
the type of the tunnels supported (for example, type of the tunnels supported (for example, manually
manually configured or signaled, persistent or configured or signaled, persistent or non-
non-persistent, etc.), the following other persistent, etc.), the following other groups
groups defined below are mandatory: defined below are mandatory: mplsTunnelManualGroup
mplsTunnelManualGroup and/or and/or mplsTunnelSignaledGroup,
mplsTunnelSignaledGroup,
mplsTunnelIsNotIntfcGroup and/or mplsTunnelIsNotIntfcGroup and/or
mplsTunnelIsIntfcGroup." mplsTunnelIsIntfcGroup."
::= { mplsTeGroups 1 } ::= { mplsTeGroups 1 }
mplsTunnelManualGroup OBJECT-GROUP mplsTunnelManualGroup OBJECT-GROUP
OBJECTS { mplsTunnelSignallingProto } OBJECTS { mplsTunnelSignallingProto }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement manually "Object(s) needed to implement manually configured
configured tunnels." tunnels."
::= { mplsTeGroups 2 } ::= { mplsTeGroups 2 }
mplsTunnelSignaledGroup OBJECT-GROUP mplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS { mplsTunnelSignallingProto, OBJECTS { mplsTunnelSetupPrio,
mplsTunnelLocalCookie, mplsTunnelHoldingPrio,
mplsTunnelRemoteCookie, mplsTunnelSignallingProto,
mplsTunnelHopIndex, mplsTunnelHopAddrType, mplsTunnelLocalProtectInUse,
mplsTunnelSessionAttributes,
mplsTunnelHopIndexNext,
mplsTunnelHopAddrType,
mplsTunnelHopIpv4Addr, mplsTunnelHopIpv4Addr,
mplsTunnelHopIpv4PrefixLen, mplsTunnelHopIpv4PrefixLen,
mplsTunnelHopIpv6Addr, mplsTunnelHopIpv6Addr,
mplsTunnelHopIpv6PrefixLen, mplsTunnelHopIpv6PrefixLen,
mplsTunnelHopAsNumber,
mplsTunnelHopLspId,
mplsTunnelHopStrictOrLoose, mplsTunnelHopStrictOrLoose,
mplsTunnelHopRowStatus, mplsTunnelHopRowStatus,
mplsTunnelResourceEntryIndex } mplsTunnelHopStorageType
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement signaled tunnels." "Object needed to implement signaled tunnels."
::= { mplsTeGroups 3 } ::= { mplsTeGroups 3 }
mplsTunnelIsIntfcGroup OBJECT-GROUP mplsTunnelIsIntfcGroup OBJECT-GROUP
OBJECTS { mplsTunnelIsIf } OBJECTS { mplsTunnelIsIf }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement tunnels that are "Objects needed to implement tunnels that are
skipping to change at page 60, line 21 skipping to change at page 41, line 28
::= { mplsTeGroups 4 } ::= { mplsTeGroups 4 }
mplsTunnelIsNotIntfcGroup OBJECT-GROUP mplsTunnelIsNotIntfcGroup OBJECT-GROUP
OBJECTS { mplsTunnelIsIf } OBJECTS { mplsTunnelIsIf }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement tunnels that are not "Objects needed to implement tunnels that are not
interfaces." interfaces."
::= { mplsTeGroups 5 } ::= { mplsTeGroups 5 }
mplsTunnelOptionalGroup OBJECT-GROUP
OBJECTS { mplsTunnelResourceIndexNext,
mplsTunnelResourceMaxRate,
mplsTunnelResourceMeanRate,
mplsTunnelResourceMaxBurstSize,
mplsTunnelResourceRowStatus,
mplsTunnelResourceStorageType,
mplsTunnelARHopAddrType,
mplsTunnelARHopIpv4Addr,
mplsTunnelARHopIpv4PrefixLen,
mplsTunnelARHopIpv6Addr,
mplsTunnelARHopIpv6PrefixLen,
mplsTunnelARHopAsNumber,
mplsTunnelARHopStrictOrLoose
}
STATUS current
DESCRIPTION
"The objects in this group are optional."
::= { mplsTeGroups 6 }
mplsTeNotificationGroup NOTIFICATION-GROUP mplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsTunnelUp, mplsTunnelDown } NOTIFICATIONS { mplsTunnelUp,
mplsTunnelDown,
mplsTunnelRerouted
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { mplsTeGroups 6 } ::= { mplsTeGroups 7 }
-- End of MPLS-TE-MIB -- End of MPLS-TE-MIB
END END
9. Security Considerations 11. Security Considerations
There are a number of management objects defined in There are a number of management objects defined in this
this MIB that have a MAX-ACCESS clause of read-write MIB that have a MAX-ACCESS clause of read-write and/or
and/or read-create. Such objects may be considered read-create. Such objects may be considered sensitive or
sensitive or vulnerable in some network environments. vulnerable in some network environments. The support for
The support for SET operations in a non-secure SET operations in a non-secure environment without proper
environment without proper protection can have a protection can have a negative effect on network
negative effect on network operations. operations.
It is thus important to control even GET access to It is thus important to control even GET access to these
these objects and possibly to even encrypt the values objects and possibly to even encrypt the values of these
of these object when sending them over the network object when sending them over the network via SNMP. Not
via SNMP. Not all versions of SNMP provide features all versions of SNMP provide features for such a secure
for such a secure environment. environment.
SNMPv1 by itself is not a secure environment. Even if SNMPv1 by itself is not a secure environment. Even if the
the network itself is secure (for example by using network itself is secure (for example by using IPSec
IPSec [IPSEC]), there is no control as to who on the [IPSEC]), there is no control as to who on the secure
secure network is allowed to access and GET/SET network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB. It is
It is recommended that the implementers consider the recommended that the implementers consider the security
security features as provided by the SNMPv3 features as provided by the SNMPv3 framework.
framework. Specifically, the use of the User-based Specifically, the use of the User-based Security Model
Security Model [SNMPv3USM] and the View- based Access [SNMPv3USM] and the View- based Access Control
Control [SNMPv3VACM] is recommended. It is then a [SNMPv3VACM] is recommended. It is then a customer/user
customer/user responsibility to ensure that the SNMP responsibility to ensure that the SNMP entity giving
entity giving access to an instance of this MIB, is access to an instance of this MIB, is properly configured
properly configured to give access to the objects to give access to the objects only to those principals
only to those principals (users) that have legitimate (users) that have legitimate rights to indeed GET or SET
rights to indeed GET or SET (change/create/delete) (change/create/delete) them.
them.
10. Acknowledgments 12. Acknowledgments
We wish to thank Eric Gray, Patrick Kerharo, and
Pramod Koppol for their comments on this draft.
11. References We wish to thank Adrian Farrel, Eric Gray, Patrick
Kerharo, and Pramod Koppol for their comments on this
draft.
[MPLSArch] Rosen, E., Viswanathan, A., and R. 13. References
Callon, "Multiprotocol Label Switching
Architecture", Internet Draft <draft- [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
ietf-mpls-arch-05.txt>, August 1999. "Multiprotocol Label Switching
Architecture", Internet Draft <draft-ietf-
mpls-arch-06.txt>, August 1999.
[MPLSFW] Callon, R., Doolan, P., Feldman, N., [MPLSFW] Callon, R., Doolan, P., Feldman, N.,
Fredette, A., Swallow, G., and A. Fredette, A., Swallow, G., and A.
Viswanathan, "A Framework for Viswanathan, "A Framework for Multiprotocol
Multiprotocol Label Switching", Label Switching", Internet Draft <draft-ietf-
Internet Draft <draft-ietf-mpls- mpls-framework-05.txt>, September 1999.
framework-05.txt>, September 1999.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Label Switch Router Nadeau, "MPLS Label Switch Router Management
Management Information Base Using Information Base Using SMIv2", Internet
SMIv2", Internet Draft <draft-ietf-mpls- Draft <draft-ietf-mpls-lsr-mib-04.txt>,
lsr-mib-01.txt>, February 2000. April 26, 2000.
[LDPMIB] Cucchiara, J., Sjostrand, H., and J.
Luciani, "Definitions of Managed
Objects for the Multiprotocol Label
Switching, Label Distribution Protocol
(LDP)", Internet Draft <draft-ietf-mpls-
ldp-mib-04.txt>, February 2000.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., [LblStk] Rosen, E., Rekhter, Y., Tappan, D.,
Farinacci, D., Federokow, G., Li, T., Farinacci, D., Federokow, G., Li, T., and A.
and A. Conta, "MPLS Label Stack Conta, "MPLS Label Stack Encoding", Internet
Encoding", Internet Draft <draft-ietf- Draft <draft-ietf-mpls-label-encaps-07.txt>,
mpls-label-encaps-07.txt>, September September 1999.
1999.
[RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li,
Li, T., Swallow, G., and V. Srinivasan, T., Swallow, G., and V. Srinivasan,
"Extensions to RSVP for LSP Tunnels", "Extensions to RSVP for LSP Tunnels",
Internet Draft <draft-mpls-rsvp-lsp- Internet Draft <draft-mpls-rsvp-lsp-tunnel-
tunnel-04.txt>, September 1999. 05.txt>, February 2000.
[CR-LDP] B. Jamoussi (Editor), "Constraint-Based [CR-LDP] B. Jamoussi (Editor), "Constraint-Based LSP
LSP Setup using LDP", Internet Draft Setup using LDP", Internet Draft <draft-ietf-
<draft-ietf-mpls-cr-ldp-03.txt>, mpls-cr-ldp-03.txt>, September 1999.
September 1999.
[Assigned] Reynolds, J., and J. Postel, "Assigned [Assigned] Reynolds, J., and J. Postel, "Assigned
Numbers", RFC 1700, October 1994. See Numbers", RFC 1700, October 1994. See also:
also: http://www.isi.edu/in- http://www.isi.edu/in-
notes/iana/assignments/smi-numbers notes/iana/assignments/smi-numbers
[SNMPArch] Harrington, D., Presuhn, R., and B. [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen,
Wijnen, "An Architecture for Describing "An Architecture for Describing SNMP
SNMP Management Frameworks", RFC 2271, Management Frameworks", RFC 2271, January
January 1998. 1998.
[SMIv1] Rose, M., and K. McCloghrie, "Structure [SMIv1] Rose, M., and K. McCloghrie, "Structure and
and Identification of Management Identification of Management Information for
Information for TCP/IP-based TCP/IP-based Internets", RFC 1155, May 1990.
Internets", RFC 1155, May 1990.
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB
MIB Definitions", RFC 1212, March 1991. Definitions", RFC 1212, March 1991.
[SNMPv1Traps] M. Rose, "A Convention for Defining [SNMPv1Traps] M. Rose, "A Convention for Defining Traps
Traps for use with the SNMP", RFC 1215, for use with the SNMP", RFC 1215, March
March 1991. 1991.
[SMIv2] Case, J., McCloghrie, K., Rose, M., and [SMIv2] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Structure of Management Waldbusser, "Structure of Management
Information for Version 2 of the Simple Information for Version 2 of the Simple
Network Management Protocol (SNMPv2)", Network Management Protocol (SNMPv2)", RFC
RFC 1902, January 1996. 1902, January 1996.
[SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Textual Conventions for Waldbusser, "Textual Conventions for Version
Version 2 of the Simple Network 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC (SNMPv2)", RFC 1903, SNMP Research, Inc.,
1903, SNMP Research, Inc., Cisco Cisco Systems, Inc., January 1996.
Systems, Inc., January 1996.
[SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Conformance Statements Waldbusser, "Conformance Statements for
for Version 2 of the Simple Network Version 2 of the Simple Network Management
Management Protocol (SNMPv2)", RFC Protocol (SNMPv2)", RFC 1904, January 1996.
1904, January 1996.
[SNMPv1] Case, J., Fedor, M., Schoffstall, M., [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J.
and J. Davin, "Simple Network Davin, "Simple Network Management Protocol",
Management Protocol", RFC 1157, May RFC 1157, May 1990.
1990.
[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Introduction to Waldbusser, "Introduction to Community-based
Community-based SNMPv2", RFC 1901, SNMPv2", RFC 1901, January 1996.
January 1996.
[SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Transport Mappings for Waldbusser, "Transport Mappings for Version
Version 2 of the Simple Network 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC (SNMPv2)", RFC 1906, January 1996.
1906, January 1996.
[SNMPv3MP] Case, J., Harrington D., Presuhn R., [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B.
and B. Wijnen, "Message Processing and Wijnen, "Message Processing and Dispatching
Dispatching for the Simple Network for the Simple Network Management Protocol
Management Protocol (SNMP)", RFC 2272, (SNMP)", RFC 2272, January 1998.
January 1998.
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User- [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based
based Security Model (USM) for version Security Model (USM) for version 3 of the
3 of the Simple Network Management Simple Network Management Protocol
Protocol (SNMPv3)", RFC 2574, April (SNMPv3)", RFC 2574, April 1999.
1999.
[SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Protocol Operations for Waldbusser, "Protocol Operations for Version
Version 2 of the Simple Network 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC (SNMPv2)", RFC 1905, January 1996.
1905, January 1996.
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
"SNMPv3 Applications", RFC 2273, Applications", RFC 2273, January 1998.
January 1998.
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie,
McCloghrie, "View-based Access Control "View-based Access Control Model (VACM) for
Model (VACM) for the Simple Network the Simple Network Management Protocol
Management Protocol (SNMP)", RFC 2575, (SNMP)", RFC 2575, April 1999.
April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security [IPSEC] Kent, S., and Atkinson, R., "Security
Architecture for the Internet Architecture for the Internet Protocol", RFC
Protocol", RFC 2401, November 1998. 2401, November 1998.
[IFMIB] McCloghrie, K., and F. Kastenholtz, [IFMIB] McCloghrie, K., and F. Kastenholtz, "The
"The Interfaces Group MIB using SMIv2", Interfaces Group MIB using SMIv2", RFC 2233,
RFC 2233, Nov. 1997 Nov. 1997.
12. Authors' Addresses 14. Authors' Addresses
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Tachion Networks, Inc.
2 Meridian Road Monmouth Park Corporate Center I
Eatontown, NJ 07724 Building C, 185 Monmouth Park Highway
Phone: +1-732-542-7750 x234 West Long Branch, NJ 07764
Phone: +1-732-542-7750 x1234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Force10 Networks Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Phone: +1-408-571-3516 Phone: +1-408-571-3516
Email: arun@force10networks.com Email: arun@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 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
13. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Copyright (C) The Internet Society (2000). All Rights
Reserved. Reserved.
This document and translations of it may be copied and This document and translations of it may be copied and
furnished to others, and derivative works that comment furnished to others, and derivative works that comment on
on or otherwise explain it or assist in its or otherwise explain it or assist in its implementation may
implementation may be prepared, copied, published and be prepared, copied, published and distributed, in whole or
distributed, in whole or in part, without restriction in part, without restriction of any kind, provided that the
of any kind, provided that the above copyright notice above copyright notice and this paragraph are included on
and this paragraph are included on all such copies and all such copies and derivative works. However, this
derivative works. However, this document itself may document itself may not be modified in any way, such as by
not be modified in any way, such as by removing the removing the copyright notice or references to the Internet
copyright notice or references to the Internet Society Society or other Internet organizations, except as needed
or other Internet organizations, except as needed for for the purpose of developing Internet standards in which
the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet
case the procedures for copyrights defined in the Standards process must be followed, or as required to
Internet Standards process must be followed, or as translate it into languages other than English.
required to translate it into languages other than
English.
The limited permissions granted above are perpetual The limited permissions granted above are perpetual and
and will not be revoked by the Internet Society or its will not be revoked by the Internet Society or its
successors or assigns. This document and the successors or assigns. This document and the information
information contained herein is provided on an "AS IS" contained herein is provided on an "AS IS" basis and THE
basis and THE INTERNET SOCIETY AND THE INTERNET INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. PURPOSE.
 End of changes. 

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