draft-ietf-mpls-lsr-mib-00.txt   draft-ietf-mpls-lsr-mib-01.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Tachion Network Technologies Internet Draft Tachion Networks, Inc.
Expires: December 1999 Expires: August 2000
Arun Viswanathan Arun Viswanathan
Lucent Technologies Force10 Networks
Thomas D. Nadeau
Cisco Systems, Inc.
MPLS Label Switch Router Management Information Base Using SMIv2 MPLS Label Switch Router Management Information Base Using SMIv2
draft-ietf-mpls-lsr-mib-00.txt draft-ietf-mpls-lsr-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 42
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 accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols Information Base (MIB) for use with network management protocols
in the Internet community. In particular, it describes managed in the Internet community. In particular, it describes managed
objects for modeling an Multi-Protocol Label Switching (MPLS) objects for modeling a Multi-Protocol Label Switching (MPLS)
[MPLSArch, MPLSFW] Label Switch Router (LSR). [MPLSArch, MPLSFW] Label Switch Router (LSR).
Open Issues Open Issues
- Does mplsTSpecTable belong in this document? Still waiting for new IANA ifType for MPLS interface layer.
- Support for signalled COS value.
- Do we need objects to keep track of ownership of entries in
various tables?
- More descriptive text and detailed example.
- Reconcile mplsInterfaceConfTable with the interface related
objects in the LDP MIB [LDPMIB] including objects for
negotiated label ranges.
- Address multipath related issues.
- Introduce a scalar to indicate the maximum supported label
stack depth.
- For each MPLS capable interface, we need objects in
mplsInterfaceConfTable that indicate the resource availability
for MPLS, such as total bandwidth, available bandwidth for
each priority level, available buffer etc.
- Fragmentation counter in mplsInterfacePerfTable.
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols Information Base (MIB) for use with network management protocols
in the Internet community. In particular, it describes managed in the Internet community. In particular, it describes managed
objects for modeling an Multi-Protocol Label Switching (MPLS) objects for modeling a Multi-Protocol Label Switching (MPLS)
[MPLSArch, MPLSFW] Label Switch Router (LSR). [MPLSArch, MPLSFW] Label Switch Router (LSR).
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@uu.net. mpls@uu.net.
This memo does not, in its draft form, specify a standard for the This memo does not, in its draft form, specify a standard for the
Internet community. Internet community.
2. Terminology 2. Terminology
This document uses terminology from the MPLS architecture document This document uses terminology from the document describing the
[MPLSArch]. MPLS architecture [MPLSArch]. A label switched path (LSP) is
modeled as a connection consisting of one or more incoming
A label switched path (LSP) is modelled as a connection consisting segments (in-segments) and/or one or more outgoing segments (out-
of one or more in-segments and/or one or more out-segments at a segments) at a label switch router (LSR). The association or
label switch router (LSR). The binding or interconnection between interconnection of the in-segments and out-segments is
in-segments and out-segments in performed using a cross-connect. accomplished by using a cross-connect. We use the terminology
We use the terms connection and LSP interchangeably where the "connection" and "LSP" interchangeably where the meaning is clear
meaning is clear from the context. from the context.
3. The SNMP Management Framework 3. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
- An overall architecture, described in RFC 2271 [SNMPArch]. - An overall architecture, described in RFC 2271 [SNMPArch].
- Mechanisms for describing and naming objects and events for the - Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 3, line 28 skipping to change at page 2, line 50
in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904
[SNMPv2Conf]. [SNMPv2Conf].
- Message protocols for transferring management information. The - Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 first version of the SNMP message protocol is called SNMPv1
and described in RFC 1157 [SNMPv1]. A second version of the and described in RFC 1157 [SNMPv1]. A second version of the
SNMP message protocol, which is not an Internet standards SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906 message protocol is called SNMPv3 and described in RFC 1906
[SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2274 [SNMPv3USM]. [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM].
- Protocol operations for accessing management information. The - Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [SNMPv1]. A second set of protocol described in RFC 1157 [SNMPv1]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 operations and associated PDU formats is described in RFC 1905
[SNMPv2PO]. [SNMPv2PO].
- A set of fundamental applications described in RFC 2273 - A set of fundamental applications described in RFC 2273
[SNMPv3App] and the view-based access control mechanism [SNMPv3App] and the view-based access control mechanism
described in RFC 2275 [SNMPv3VACM]. Managed objects are described in RFC 2575 [SNMPv3VACM].
accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are Managed objects are accessed via a virtual information store,
defined using the mechanisms defined in the SMI. This memo termed the Management Information Base or MIB. Objects in the MIB
are defined using the mechanisms defined in the SMI. This memo
specifies a MIB module that is compliant to the SMIv2. A MIB specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the conforming to the SMIv1 can be produced through the appropriate
appropriate translations. The resulting translated MIB must translations. The resulting translated MIB must be semantically
be semantically equivalent, except where objects or events are equivalent, except where objects or events are omitted because no
omitted because no translation is possible (use of Counter64). translation is possible (use of Counter64). Some machine-readable
Some machine readable information in SMIv2 will be converted information in SMIv2 will be converted into textual descriptions
into textual descriptions in SMIv1 during the translation in SMIv1 during the translation process. However, this loss of
process. However, this loss of machine readable information machine-readable information is not considered to change the
is not considered to change the semantics of the MIB. semantics of the MIB.
3.1. Object Definitions 3.1. Object Definitions
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the MIB termed the Management Information Base or MIB. Objects in the MIB
are defined using the subset of Abstract Syntax Notation One are defined using the subset of Abstract Syntax Notation One
(ASN.1) defined in the SMI. In particular, each object type is (ASN.1) defined in the SMI. In particular, each object type is
named by an OBJECT IDENTIFIER, an administratively assigned name. named by an OBJECT IDENTIFIER, an administratively assigned name.
The object type together with an object instance serves to The object type together with an object instance serves to
uniquely identify a specific instantiation of the object. For uniquely identify a specific instantiation of the object. For
human convenience, we often use a textual string, termed the human convenience, we often use a textual string, termed the
descriptor, to also refer to the object type. descriptor, to also refer to the object type.
4. Feature Checklist 4. Feature Checklist
The MPLS label switch router (LSR) MIB is designed to satisfy the The MPLS label switch router MIB (LSR-MIB) is designed to satisfy
following requirements and constraints. the following requirements and constraints:
- The MIB should be able to support both manually configured LSPs - The MIB should be able to support both manually configured LSPs
as well as via LDP and/or RSVP signaling. as well as those configured via CR-LDP and/or RSVP signaling.
- The MIB must support enabling and disabling of MPLS capability - The MIB must support the enabling and disabling of MPLS
on MPLS capable interfaces of an LSR. capability on MPLS capable interfaces of an LSR.
- The MIB should allow resource sharing between two or more LSPs. - The MIB should allow resource sharing between two or more LSPs.
- Both per-platform and per-interface label spaces must be - Both per-platform and per-interface label spaces must be
supported. supported.
- MPLS packets must be forwarded solely based on an incoming top - MPLS packets must be forwarded solely based on an incoming top
label [MPLSArch, LblStk]. label [MPLSArch, LblStk].
- Support must be provided for next-hop resolution when the - Support must be provided for next-hop resolution when the
outgoing interface is a shared media interface. In the point- outgoing interface is a shared media interface. In the point-
to-multipoint case, each outgoing segment can be on a to-multipoint case, each outgoing segment can reside on a
different shared media interface. different shared media interface.
- The MIB must support point-to-point, point-to-multipoint and - The MIB must support point-to-point, point-to-multipoint and
multipoint-to-point connections at an LSR. multipoint-to-point connections at an LSR.
- For multipoint-to-point connections all the outgoing packets - For multipoint-to-point connections all outgoing packets must
must have the same top label. have the same top label.
- For multipoint-to-point connections the outgoing resources of - For multipoint-to-point connections, the outgoing resources of
the merged connections must be shared. the merged connections must be shared.
- For multipoint-to-point connections, packets from different - For multipoint-to-point connections, packets from different
incoming connections may have distinct outgoing label stacks, incoming connections may have distinct outgoing label stacks
beneath the (identical) top label. beneath the (identical) top label.
- In the point-to-multipoint case each outgoing connection can - In the point-to-multipoint case each outgoing connection can
have a distinct label stack including the top label. have a distinct label stack including the top label.
- In a point-to-multipoint connection the ingress resources are - All the members of a point-to-multipoint connection share the
shared by all the members of the connection. resources allocated for the ingress segments.
- The MIB must provide cross-connect capability to "pop" an - The MIB must provide cross-connect capability to "pop" an
incoming label and forward the packet with the rest of the incoming label and forward the packet with the remainder of
label stack unchanged and without pushing any labels ("pop-and- the label stack unchanged and without pushing any labels ("pop-
go") [LblStk]. and-go") [LblStk].
- It must be possible to assign or remap COS bits [LblStk] on the - It must be possible to assign or re-map the Class of Service
outgoing label. In the multipoint-to-point case, each in- (COS) bits [LblStk] on the outgoing label. In the multipoint-
segment can have a different outgoing COS value. In the point- to-point case, each in-segment can have a different outgoing
to-multipoint case, each out-segment can have a different COS value. In the point-to-multipoint case, each out-segment
outgoing COS value. can have a different outgoing COS value.
- It should be possible to support persistent as well as non- - It should be possible to support persistent as well as non-
persistent LSPs. persistent LSPs.
- Performance counters must be provided for in-segments and out- - Performance counters must be provided for in-segments and out-
segments as well as for measuring MPLS performance on a per- segments as well as for measuring MPLS performance on a per-
interface basis. interface basis.
5. Outline 5. Outline
Configuring LSPs through an LSR involves the following steps:
Configuring LSPs through an LSR involves the following steps.
- Enabling MPLS on MPLS capable interfaces. - Enabling MPLS on MPLS capable interfaces.
- Configuring in and out segments. - Configuring in-segments and out-segments.
- Setting up the cross-connect table to switch between segments - Setting up the cross-connect table to associate segments and/or
and/or to indicate connection origination and termination. to indicate connection origination and termination.
- (Optionally) specifying label stack actions. - Optionally specifying label stack actions.
- (Optionally) specifying segment traffic parameters.
- Optionally specifying segment traffic parameters.
5.1. Summary of LSR MIB 5.1. Summary of LSR MIB
The MIB objects for performing these actions consist of the The MIB objects for performing these actions consist of the
following tables. following tables:
- Interface configuration table (mplsInterfaceConfTable) for - The interface configuration table (mplsInterfaceConfTable),
enabling MPLS on MPLS capable interfaces. which is used for enabling the MPLS protocol on MPLS-capable
interfaces.
- In-segment (mplsInSegmentTable) and out-segment - The in-segment (mplsInSegmentTable) and out-segment
(mplsOutSegmentTable) tables for configuring LSP segments at (mplsOutSegmentTable) tables, which are used for configuring
an LSR. LSP segments at an LSR.
- Cross-connect table (mplsXCTable) for creating relationships - The cross-connect table (mplsXCTable), which is used to
between in and out segments constituting a cross-connect. associate in and out segments together, in order to form a
cross-connect.
- Label stack table (mplsLabelStackTable) for specifying label - The label stack table (mplsLabelStackTable), which is used for
stack operations. specifying label stack operations.
- TSpec table (mplsTSpecTable) for specifying LSP related - The TSpec table (mplsTSpecTable), which is used for specifying
traffic parameters. LSP-related traffic parameters.
Further, the MPLS in-segment and out-segment performance tables, Further, the MPLS in-segment and out-segment performance tables,
mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the
objects necessary to measure the performance of LSPs, and objects necessary to measure the performance of LSPs, and
mplsInterfacePerfTable has objects to measure MPLS performance on mplsInterfacePerfTable has objects to measure MPLS performance on
a per-interface basis. a per-interface basis.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
Sections 6.1-6.2 describe objects pertaining to MPLS capable Sections 6.1-6.3 describe objects pertaining to MPLS capable
interfaces of an LSR. The objects described in Sections 6.3-6.8, interfaces of an LSR. The objects described in Sections 6.4-6.9,
when considered together, are equivalent to the tables described when considered together, are equivalent to the tables described
in the MPLS architecture document [MPLSArch], that is, the in the MPLS architecture document [MPLSArch], that is, the
Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry
(NHLFE) tables. Section 6.9 describes objects for specifying (NHLFE) tables. Section 6.10 describes objects for specifying
traffic parameters for in and out segments. traffic parameters for in and out segments.
6.1. mplsInterfaceConfTable 6.1. mplsInterfaceConfTable
This table represents the interfaces that are MPLS capable. An This table represents the interfaces that are MPLS capable. An
LSR creates an entry in this table for every MPLS capable LSR creates an entry in this table for every MPLS capable
interface on that LSR. Each entry contains information about per- interface on that LSR. Each entry contains information about per-
interface label ranges. The administrator can specify the desired interface label ranges. The administrator can specify the desired
MPLS status (enable/up, disable/down, testing) of an interface by MPLS status (enable/up, disable/down, testing) of an interface by
writing the object mplsInterfaceAdminStatus. The actual status is writing the object mplsInterfaceAdminStatus. The actual status is
indicated by the object mplsInterfaceOperStatus. indicated by the object mplsInterfaceOperStatus.
6.2. mplsInterfacePerfTable 6.2. mplsInterfaceResTable
This table provides resource information such as available and
allocated bandwidth and buffers on each MPLS capable interface for
each priority level.
6.3. mplsInterfacePerfTable
This table contains objects to measure the MPLS performance of This table contains objects to measure the MPLS performance of
MPLS capable interfaces and is an AUGMENT to MPLS capable interfaces and is an AUGMENT to
mplsInterfaceConfTable. High capacity counters are provided for mplsInterfaceConfTable. High capacity counters are provided for
objects that are likely to wrap around quickly on high-speed objects that are likely to wrap around quickly on high-speed
interfaces. interfaces.
6.3. mplsInSegmentTable 6.4. mplsInSegmentTable
This table contains a description of the incoming MPLS segments to This table contains a description of the incoming MPLS segments to
an LSR and their associated parameters. an LSR and their associated parameters.
6.4. mplsInSegmentPerfTable 6.5. mplsInSegmentPerfTable
The MPLS In-Segment Performance Table has objects to measure the The MPLS In-Segment Performance Table has objects to measure the
performance of an incoming segment configured on an LSR. It is an performance of an incoming segment configured on an LSR. It is an
AUGMENT to mplsInSegmentTable. High capacity counters are AUGMENT to mplsInSegmentTable. High capacity counters are
provided for objects that are likely to wrap around quickly on provided for objects that are likely to wrap around quickly on
high-speed interfaces. high-speed interfaces.
6.5. mplsOutSegmentTable 6.6. mplsOutSegmentTable
The Out-Segment Table contains a description of the outgoing MPLS The Out-Segment Table contains a description of the outgoing MPLS
segments at an LSR and their associated parameters. segments at an LSR and their associated parameters.
6.6. mplsOutSegmentPerfTable 6.7. mplsOutSegmentPerfTable
The MPLS Out-Segment Table contains objects to measure the The MPLS Out-Segment Table contains objects to measure the
performance of an outgoing segment configured on an LSR. It is an performance of an outgoing segment configured on an LSR. It is an
AUGMENT to mplsOutSegmentTable. High capacity counters are AUGMENT to mplsOutSegmentTable. High capacity counters are
provided for objects that are likely to wrap around quickly on provided for objects that are likely to wrap around quickly on
high-speed interfaces. high-speed interfaces.
6.7. mplsXCTable 6.8. mplsXCTable
mplsXCTable specifies information for switching between segments. The mplsXCTable specifies information for associating segments
It supports point-to-point, point-to-multipoint and multipoint-to- together in order to instruct the LSR to switch between the
point connections. specified segments. It supports point-to-point, point-to-multi-
point and multi-point-to-point connections.
6.8. mplsLabelStackTable 6.9. mplsLabelStackTable
mplsLabelStackTable specifies the label stack to be pushed onto a The mplsLabelStackTable specifies the label stack to be pushed
packet, beneath the top label. Entries to this table are referred onto a packet, beneath the top label. Entries to this table are
to from mplsXCTable. referred to from mplsXCTable.
6.9. mplsTSpecTable 6.10. mplsTSpecTable
mplsTSpecTable contains objects for specifying the traffic The mplsTSpecTable contains objects for specifying the traffic
parameters of in and out segments. Entries in this table are parameters of in-segments and out-segments. Entries in this table
referred to from mplsInSegmentTable and mplsOutSegmentTable. are referred to from mplsInSegmentTable and mplsOutSegmentTable.
7. Specifying the Segments of an LSR 7. Example of LSP Setup
Suppose that we want to manually create a best-effort bi- In this section we provide a brief example of using the MIB
directional LSP, consisting of an in-segment and an out-segment on objects described in Section 8 to set up an LSP. While this
an LSR (with no label stack beneath the top label on the outgoing example is not meant to illustrate every nuance of the MIB, it is
labeled packets). The following rows and corresponding objects intended as an aid to understanding some of the key concepts. It
need to be created to do this. is meant to be read after going through the MIB itself.
First, the in-segment and the out-segment are created with the Suppose that one would like to manually create a best-effort,
appropriate traffic parameters. unidirectional LSP. Assume that the LSP enters the LSR via MPLS
interface A with ifIndex 12 and exits the LSR via MPLS interface B
with ifIndex 13. Let us assume that we do not wish to have a label
stack beneath the top label on the outgoing labeled packets. The
following example illustrates which rows and corresponding objects
might be created to accomplish this.
First, the TSpec entries must be set-up for both segments.
In mplsTSpecTable for the incoming direction:
{
mplsTSpecIndex = 5
mplsTSpecDirection = in(1),
mplsTSpecMaxRate = 100000,
mplsTSpecMeanRate = 100000,
mplsTSpecMaxBurstSize = 2000,
mplsTSpecRowStatus = createAndGo(4)
}
In mplsTSpecTable for the outgoing direction:
{
mplsTSpecIndex = 6
mplsTSpecDirection = out(2),
mplsTSpecMaxRate = 100000,
mplsTSpecMeanRate = 100000,
mplsTSpecMaxBurstSize = 2000,
mplsTSpecRowStatus = createAndGo(4)
}
Note that if we were setting up a bi-directional LSP, the segments
in the reverse direction can share the TSpec entries (and hence
resources) with the segments in the forward direction.
We must next create the appropriate in-segment and out-segment
entries with suitable traffic parameters by pointing to the
appropriate TSpec entries that we have just created.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIfIndex = i1, mplsInSegmentIfIndex = 12, -- incoming interface
mplsInSegmentLabel = l1, mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentTSpecIndex = 0, mplsInSegmentTSpecIndex = 5,
mplsInSegmentRowStatus = createAndGo(3) mplsInSegmentRowStatus = createAndGo(4)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = o, mplsOutSegmentIndex = 1,
mplsOutSegmentIfIndex = i2, mplsOutSegmentIfIndex = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = l2, mplsOutSegmentTopLabel = 22, -- outgoing label
mplsOutSegmentTSpecIndex = 0, mplsOutSegmentTSpecIndex = 6,
mplsOutSegmentRowStatus = createAndGo(3) mplsOutSegmentRowStatus = createAndGo(4)
} }
Next, two cross-connect entries associating these two segments by Next, a cross-connect entry is created thereby associating the
sharing the same mplsXCIndex are created. newly created segments together.
In mplsXCTable, for the in-segment: In mplsXCTable:
{ {
mplsXCIndex = x, mplsXCIndex = 2,
mplsInSegmentIfIndex = i1, mplsXCLspId = "1.2.3.4-2",
mplsInSegmentLabel = l1, mplsInSegmentIfIndex = 12,
mplsOutSegmentIndex = 0, mplsInSegmentLabel = 21,
mplsLabelStackIndex = 0, mplsOutSegmentIndex = 1,
mplsXCRowStatus = createAndGo(3) mplsXCCOS = 0,
mplsXCIsPersistent = false (1),
mplsLabelStackIndex = 0, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4)
} }
In mplsXCTable, for the out-segment: Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex
{ objects will automatically be populated with the value 2 when
mplsXCIndex = x, these segments are referred to from the corresponding cross-
mplsInSegmentIfIndex = 0, connect entry.
mplsInSegmentLabel = 0,
mplsOutSegmentIndex = o,
mplsXCLabelStackIndex = 0,
mplsXCRowStatus = createAndGo(3)
}
Note that the objects mplsInSegmentXCIndex and 8. Application of the Interface Group to MPLS
mplsOutSegmentXCIndex will automatically get populated with the
value "x" when these segments are referred to from the
corresponding cross-connect entries.
8. MPLS Label Switch Router MIB Definitions 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 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
layer interface is represented as an entry in the ifTable. This
entry is concerned with the MPLS layer as a whole, and not with
individual LSPs/tunnels which are managed via the MPLS-specific
managed objects specified in this memo and [TEMIB]. The inter-
relation of entries in the ifTable is defined by Interfaces Stack
Group defined in [IFMIB].
8.1. Support of the MPLS Layer by ifTable
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 interface as
specified by a network manager.
9. MPLS Label Switch Router MIB Definitions
MPLS-LSR-MIB DEFINITIONS ::= BEGIN MPLS-LSR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Counter32, Counter64, Gauge32, IpAddress experimental, Integer32, Unsigned32, Counter32,
Counter64, 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
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex, InterfaceIndex, InterfaceIndexOrZero ifIndex, InterfaceIndex, InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB;
BitRate, BurstSize
FROM INTEGRATED-SERVICES-MIB;
mplsLsrMIB MODULE-IDENTITY mplsLsrMIB MODULE-IDENTITY
LAST-UPDATED "9906161200Z" -- 16 June 1999 12:00:00 EST LAST-UPDATED "200002161200Z" -- 16 February 2000 12:00:00 EST
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan " Cheenu Srinivasan
Postal: Tachion Network Technologies Postal: Tachion Networks, Inc.
2 Meridian Road 2 Meridian Road
Eatontown, NJ 07724 Eatontown, NJ 0772
Tel: +1 732 542 7750 x234 Tel: +1 732 542 7750 x234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Postal: Lucent Technologies Postal: Force10 Networks
4D537, 101 Crawfords Corner Road 1440 McCarthy Blvd
Holmdel, NJ 07733 Milpitas, CA 95035
Tel: +1 732 332 5163 Tel: +1-408-571-3516
Email: arunv@lucent.com" Email: arun@force10networks.com
Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com"
DESCRIPTION DESCRIPTION
"Proposed MIB module for MPLS Label Switch Router. "This MIB contains managed object definitions for the
See: Rosen, E., Viswanathan, A., and R. Callon, Multiprotocol Label Switching (MPLS) Router as
Multiprotocol Label Switching Architecture, Internet defined in: Rosen, E., Viswanathan, A., and R.
Draft <draft-ietf-mpls-arch-05.txt>, February 1999." Callon, Multiprotocol Label Switching Architecture,
Internet Draft <draft-ietf-mpls-arch-06.txt>,
February 2000."
-- Revision history.
REVISION
"199907161200Z" -- 16 July 1999 12:00:00 EST
DESCRIPTION
"Initial draft version."
REVISION
"200002161200Z" -- 16 February 2000 12:00:00 EST
DESCRIPTION
"Second draft version."
::= { experimental 96 } ::= { experimental 96 }
-- Textual Conventions. -- Textual Conventions.
MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An identifier that is assigned to each LSP and is
used to uniquely identify it. This is assigned at
the head end of the LSP and can be used by all LSRs
to identify this LSP. This value is piggybacked by
the signaling protocol when this LSP is signaled
within the network. This identifier can then be used
at each LSR to identify which labels are being
swapped to other labels for this LSP. For IPv4
addresses this results in a 6-octet long cookie."
SYNTAX OCTET STRING (SIZE (0..63))
MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An address family. Values are defined in RFC 1700 - "An address family. These values are defined in RFC
Assigned Numbers. All values may not be relevant in 1700 and are maintained by The IANA. All values may
all contexts when used in this MIB, but are included not be relevant in all contexts when used in this
for completeness." MIB, but are included for completeness."
REFERENCE REFERENCE
"RFC 1700 - Assigned Numbers, Reynolds and Postel, "RFC 1700 - Assigned Numbers, Reynolds, J. and J.
Oct. 1994" Postel, Oct. 1994"
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
ipv4(1), ipv4(1),
ipv6(2), ipv6(2),
nsap(3), nsap(3),
hdlc(4), hdlc(4),
bbn1822(5), bbn1822(5),
ieee802(6), ieee802(6),
e163(7), e163(7),
e164(8), e164(8),
skipping to change at page 10, line 44 skipping to change at page 13, line 26
banyanVines(14), banyanVines(14),
e164WithNsap(15) e164WithNsap(15)
} }
-- An MPLS label. -- An MPLS label.
MplsLabel ::= TEXTUAL-CONVENTION MplsLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an MPLS label. Note that the contents of "Represents an MPLS label. Note that the contents of
a label field are interpreted in an interface-type a label field are interpreted in an interface-type
specific fashion. For example, the label carried in specific fashion. For example, the 20-bit wide
the MPLS shim header is 20 bits wide and the top 12 label carried in the MPLS shim header is contained
bits must be zero. The frame relay label can be in bits 0-19 and bits 20-31 must be zero. The frame
either 10, 17 or 23 bits wide depending on the size relay label can be either 10, 17 or 23 bits wide
of the DLCI field size and the top 22, 15, or 9 bits depending on the size of the DLCI field and bits 10-
must be zero, respectively. For an ATM interface, 31, 17-31 or 23-31 must be zero, respectively. For
the lowermost 16 bits are interpreted as the VCI, an ATM interface, bits 0-15 must be interpreted as
the next 8 bits as the VPI and the remaining bits the VCI, bits 16-23 as the VPI and bits 24-31 must
must be zero. Also note the permissible label be zero. Note that the permissible label values are
values are also a function of the interface type. also a function of the interface type. For example,
For example, the value 3 has special semantics in the value 3 has special semantics in the control
the control plane for an MPLS shim header label and plane for an MPLS shim header label and is not a
is not a valid label value in the datapath." valid label value in the data path."
REFERENCE REFERENCE
"1. MPLS Label Stack Encoding, Rosen et al, draft- "1. MPLS Label Stack Encoding, Rosen et al, draft-
ietf-mpls-label-encaps-04.txt, April 1999. ietf-mpls-label-encaps-07.txt, March 2000.
2. Use of Label Switching on Frame Relay Networks, 2. Use of Label Switching on Frame Relay Networks,
Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998."
SYNTAX Integer32 SYNTAX Integer32
Ipv6Address ::= TEXTUAL-CONVENTION Ipv6Address ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IPv6 address." "IPv6 address."
SYNTAX OCTET STRING (SIZE(16)) SYNTAX OCTET STRING (SIZE(16))
BitRate ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
" The rate in bits/second."
SYNTAX INTEGER (0..'7FFFFFFF'h)
BurstSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The number of octets of.MPLS data that the stream
may send without concern for policing."
SYNTAX INTEGER (0..'7FFFFFFF'h)
BufferSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Size of buffer in octets of.MPLS data."
SYNTAX INTEGER (0..'7FFFFFFF'h)
-- Top level components of this MIB. -- Top level components of this MIB.
-- tables, scalars -- tables, scalars
mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 }
-- traps -- traps
mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 }
-- conformance -- conformance
mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 }
-- MPLS Interface Configuration Table. -- MPLS Interface Configuration Table.
skipping to change at page 11, line 47 skipping to change at page 14, line 50
"This table specifies per-interface MPLS capability "This table specifies per-interface MPLS capability
and associated information." and associated information."
::= { mplsLsrObjects 1 } ::= { mplsLsrObjects 1 }
mplsInterfaceConfEntry OBJECT-TYPE mplsInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsInterfaceConfEntry SYNTAX MplsInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR for "An entry in this table is created by an LSR for
every interface capable of supporting MPLS and every interface capable of supporting MPLS."
represents the label space of that interface. A row
with index 0 represents the global label space."
INDEX { mplsInterfaceConfIndex } INDEX { mplsInterfaceConfIndex }
::= { mplsInterfaceConfTable 1 } ::= { mplsInterfaceConfTable 1 }
MplsInterfaceConfEntry ::= SEQUENCE { MplsInterfaceConfEntry ::= SEQUENCE {
mplsInterfaceConfIndex InterfaceIndexOrZero, mplsInterfaceConfIndex InterfaceIndexOrZero,
mplsInterfaceLabelMinIn MplsLabel, mplsInterfaceLabelMinIn MplsLabel,
mplsInterfaceLabelMaxIn MplsLabel, mplsInterfaceLabelMaxIn MplsLabel,
mplsInterfaceLabelMinOut MplsLabel, mplsInterfaceLabelMinOut MplsLabel,
mplsInterfaceLabelMaxOut MplsLabel, mplsInterfaceLabelMaxOut MplsLabel,
mplsInterfaceTotalBandwidth BitRate,
mplsInterfaceAvailableBandwidth BitRate,
mplsInterfaceTotalBuffer BufferSize,
mplsInterfaceAvailableBuffer BufferSize,
mplsInterfaceIsGlobalLabelSpace TruthValue,
mplsInterfaceAdminStatus INTEGER, mplsInterfaceAdminStatus INTEGER,
mplsInterfaceOperStatus INTEGER mplsInterfaceOperStatus INTEGER
} }
mplsInterfaceConfIndex OBJECT-TYPE mplsInterfaceConfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index for this row of the table. A value of 0 "This is a unique index for an entry in the
indicates the global label space and this entry is MplsInterfaceConfTable. A non-zero index for an
created by the LSR if it supports a global label entry indicates the ifIndex for the corresponding
space. A non-zero index is also the interface interface entry in of the MPLS-layer in the ifTable.
index, ifIndex, for the corresponding interface Note that the global label space may apply to
entry in ifTable." several interfaces, and therefore the configuration
of the global label space interface parameters will
apply to all of the interfaces that are
participating in the global label space."
REFERENCE REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2, "RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie and Kastenholtz, Nov. 1997" McCloghrie, K., and F. Kastenholtz, Nov. 1997"
::= { mplsInterfaceConfEntry 1 } ::= { mplsInterfaceConfEntry 1 }
mplsInterfaceLabelMinIn OBJECT-TYPE mplsInterfaceLabelMinIn OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Minimum value of MPLS label that this LSR is willing "This is the minimum value of an MPLS label that this
to receive on this interface." LSR is willing to receive on this interface."
::= { mplsInterfaceConfEntry 2 } ::= { mplsInterfaceConfEntry 2 }
mplsInterfaceLabelMaxIn OBJECT-TYPE mplsInterfaceLabelMaxIn OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum value of MPLS label that this LSR is willing "This is the maximum value of an MPLS label that this
to receive on this interface." LSR is willing to receive on this interface."
::= { mplsInterfaceConfEntry 3 } ::= { mplsInterfaceConfEntry 3 }
mplsInterfaceLabelMinOut OBJECT-TYPE mplsInterfaceLabelMinOut OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Minimum value of MPLS label that this LSR is willing "This is the minimum value of an MPLS label that this
to send on this interface." LSR is willing to send on this interface."
::= { mplsInterfaceConfEntry 4 } ::= { mplsInterfaceConfEntry 4 }
mplsInterfaceLabelMaxOut OBJECT-TYPE mplsInterfaceLabelMaxOut OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum value of MPLS label that this LSR is willing "This is the maximum value of an MPLS label that this
to send on this interface." LSR is willing to send on this interface."
::= { mplsInterfaceConfEntry 5 } ::= { mplsInterfaceConfEntry 5 }
mplsInterfaceTotalBandwidth OBJECT-TYPE
SYNTAX BitRate
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value indicates the total amount of usable
bandwidth on this interface and is specified in
kilobytes per second (Kbps/sec)."
::= { mplsInterfaceConfEntry 6 }
mplsInterfaceAvailableBandwidth OBJECT-TYPE
SYNTAX BitRate
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value indicates the total amount of available
bandwidth available on this interface and is
specified in kilobytes per second (Kbps/sec). This
value is calculated as the difference between the
amount of bandwidth currently in use and that
specified in mplsInterfaceTotalBandwidth."
::= { mplsInterfaceConfEntry 7 }
mplsInterfaceTotalBuffer OBJECT-TYPE
SYNTAX BufferSize
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value indicates the total amount of buffer
space allocated for this interface."
::= { mplsInterfaceConfEntry 8 }
mplsInterfaceAvailableBuffer OBJECT-TYPE
SYNTAX BufferSize
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value reflects the total amount of buffer space
available on this interface."
::= { mplsInterfaceConfEntry 9 }
mplsInterfaceIsGlobalLabelSpace OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value indicates whether or not this interface
participates in the global label space. If this
interface participates in the platform-specific
label space, then this value will be set to false."
::= { mplsInterfaceConfEntry 10 }
mplsInterfaceAdminStatus OBJECT-TYPE mplsInterfaceAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- enable MPLS on this interface up(1), -- enable MPLS on this interface
down(2), -- disable MPLS on this interface down(2), -- disable MPLS on this interface
testing(3) -- in some test mode testing(3) -- in some test mode
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the administrator's intent as to whether "This variable indicates the administrator's intent
MPLS should be enabled or disabled on this as to whether MPLS should be enabled, disabled, or
running in some diagnostic testing mode on this
interface." interface."
DEFVAL { down } DEFVAL { down }
::= { mplsInterfaceConfEntry 6 } ::= { mplsInterfaceConfEntry 11 }
mplsInterfaceOperStatus OBJECT-TYPE mplsInterfaceOperStatus 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 for some unknown(4), -- status cannot be determined for some
-- reason -- reason
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerNotPresent(7) lowerLayerDown(7)
-- down due to the state of -- 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 status of MPLS on this "This value reflects the actual or operational status
interface." of MPLS on this interface."
::= { mplsInterfaceConfEntry 7 } ::= { mplsInterfaceConfEntry 12 }
-- End of mplsInterfaceConfTable -- End of mplsInterfaceConfTable
-- MPLS Interface Performance Table. -- MPLS Interface Performance Table.
mplsInterfacePerfTable OBJECT-TYPE mplsInterfacePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInterfacePerfEntry SYNTAX SEQUENCE OF MplsInterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides per-interface MPLS performance "This table provides MPLS performance information on
information." a per-interface basis."
::= { mplsLsrObjects 2 } ::= { mplsLsrObjects 2 }
mplsInterfacePerfEntry OBJECT-TYPE mplsInterfacePerfEntry OBJECT-TYPE
SYNTAX MplsInterfacePerfEntry SYNTAX MplsInterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for "An entry in this table is created by the LSR for
every interface capable of supporting MPLS. Its is every interface capable of supporting MPLS. Its is
an extension to mplsInterfaceConfEntry." an extension to the mplsInterfaceConfEntry table."
AUGMENTS { mplsInterfaceConfEntry } AUGMENTS { mplsInterfaceConfEntry }
::= { mplsInterfacePerfTable 1 } ::= { mplsInterfacePerfTable 1 }
MplsInterfacePerfEntry ::= SEQUENCE { MplsInterfacePerfEntry ::= SEQUENCE {
-- incoming direction -- incoming direction
mplsInterfaceInLabelsUsed Gauge32, mplsInterfaceInLabelsUsed Gauge32,
mplsInterfaceInOctets Counter32,
mplsInterfaceInPackets Counter32, mplsInterfaceInPackets Counter32,
mplsInterfaceInErrors Counter32,
mplsInterfaceInDiscards Counter32, mplsInterfaceInDiscards Counter32,
mplsInterfaceFailedLabelLookup Counter32, mplsInterfaceFailedLabelLookup Counter32,
-- outgoing direction -- outgoing direction
mplsInterfaceOutLabelsUsed Gauge32, mplsInterfaceOutLabelsUsed Gauge32,
mplsInterfaceOutOctets Counter32,
mplsInterfaceOutPackets Counter32, mplsInterfaceOutPackets Counter32,
mplsInterfaceOutErrors Counter32,
mplsInterfaceOutDiscards Counter32, mplsInterfaceOutDiscards Counter32,
mplsInterfaceOutFragments Counter32
-- high capacity counters
mplsInterfaceInHCOctets Counter64,
mplsInterfaceOutHCOctets Counter64
} }
mplsInterfaceInLabelsUsed OBJECT-TYPE mplsInterfaceInLabelsUsed OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labels that are in use at this point "This value indicates the specific number of labels
on this interface in the incoming direction." that are in use at this point in time on this
interface in the incoming direction."
::= { mplsInterfacePerfEntry 1 } ::= { mplsInterfacePerfEntry 1 }
mplsInterfaceInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that have been received in
labeled packets on this interface."
::= { mplsInterfacePerfEntry 2 }
mplsInterfaceInPackets OBJECT-TYPE mplsInterfaceInPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labeled packets that have been "This variable reflects the number of labeled packets
received on this interface." that have been received on this interface."
::= { mplsInterfacePerfEntry 3 } ::= { mplsInterfacePerfEntry 2 }
mplsInterfaceInErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of labeled packets that have been
received on this interface that were errored."
::= { mplsInterfacePerfEntry 4 }
mplsInterfaceInDiscards OBJECT-TYPE mplsInterfaceInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labeled packets that have been "The number of inbound labeled packets, which were
received on this interface that were discarded." chosen to be discarded even though no errors had
::= { mplsInterfacePerfEntry 5 } been detected to prevent their being transmitted.
One possible reason for discarding such a labeled
packet could be to free up buffer space."
::= { mplsInterfacePerfEntry 3 }
mplsInterfaceFailedLabelLookup OBJECT-TYPE mplsInterfaceFailedLabelLookup OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labeled packets that have been "This value indicates the number of labeled packets
received on this interface that were discarded that have been received on this interface and were
because no matching entries were found in discarded because there were no matching entries
mplsInSegmentTable." found for them in mplsInSegmentTable."
::= { mplsInterfacePerfEntry 6 } ::= { mplsInterfacePerfEntry 4 }
mplsInterfaceOutLabelsUsed OBJECT-TYPE mplsInterfaceOutLabelsUsed OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labels that are in use at this point "Indicates the number of top-most labels in the
on this interface in the outgoing direction." outgoing label stacks that are in use at this point
::= { mplsInterfacePerfEntry 7 } in time on this interface."
::= { mplsInterfacePerfEntry 5 }
mplsInterfaceOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that have been sent as labeled
packets on this interface."
::= { mplsInterfacePerfEntry 8 }
mplsInterfaceOutPackets OBJECT-TYPE mplsInterfaceOutPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labeled packets that have been sent on "This variable contains the number of labeled packets
this interface." that have been transmitted on this interface."
::= { mplsInterfacePerfEntry 9 } ::= { mplsInterfacePerfEntry 6 }
mplsInterfaceOutErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of labeled packets that could not be sent
on this interface due to errors."
::= { mplsInterfacePerfEntry 10 }
mplsInterfaceOutDiscards OBJECT-TYPE mplsInterfaceOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outgoing labeled packets on this "The number of outbound labeled packets, which were
interface that had to be discarded due to errors or chosen to be discarded even though no errors had
other conditions such as buffer overflows." been detected to prevent their being transmitted.
::= { mplsInterfacePerfEntry 11 } One possible reason for discarding such a labeled
packet could be to free up buffer space."
mplsInterfaceInHCOctets OBJECT-TYPE ::= { mplsInterfacePerfEntry 7 }
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that have been received in
labeled packets on this interface. This is the 64
bit version of mplsInterfaceInOctets."
::= { mplsInterfacePerfEntry 15 }
mplsInterfaceOutHCOctets OBJECT-TYPE mplsInterfaceOutFragments OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that have been sent in labeled "This variable indicates the number of outgoing MPLS
packets on this interface. This is the 64 bit packets that were fragmented before transmission on
version of mplsInterfaceOutOctets." this interface."
::= { mplsInterfacePerfEntry 16 } ::= { mplsInterfacePerfEntry 8 }
-- End of mplsInterfacePerfTable -- End of mplsInterfacePerfTable
-- In-segment table. -- In-segment table.
mplsInSegmentTable OBJECT-TYPE mplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentEntry SYNTAX SEQUENCE OF MplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a description of the incoming "This table contains a collection of incoming
segments to a LSR." segments to an LSR."
::= { mplsLsrObjects 3 } ::= { mplsLsrObjects 3 }
mplsInSegmentEntry OBJECT-TYPE mplsInSegmentEntry OBJECT-TYPE
SYNTAX MplsInSegmentEntry SYNTAX MplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents one incoming "An entry in this table represents one incoming
segment. An entry can be created by a network segment. An entry can be created by a network
administrator or by an SNMP agent as instructed by administrator or by an SNMP agent as instructed by
LDP or RSVP. It is indexed by the incoming CR-LDP or RSVP. The creator of the entry is denoted
interface index and (top) label. Note that some of by mplsInSegmentOwner. An entry in this table is
the segments are associated with a tunnel, the indexed by the ifIndex of the incoming interface and
traffic parameters of these rows are supported as the (top) label. Note that some segments are
read-only objects and their modification can be done associated with a tunnel, so the traffic parameters
only via the tunnel table, mplsTunnelTable. This of these rows are supported as read-only objects and
issue will be addressed more naturally when their modification can be done only via the tunnel
ownership related objects are introduced into these table, mplsTunnelTable."
tables."
REFERENCE REFERENCE
"MPLS Traffic Engineering Management Information Base "MPLS Traffic Engineering Management Information Base
Using SMIv2, Srinivasan and Viswanathan, draft-ietf- Using SMIv2, Srinivasan, Viswanathan and Nadeau,
mpls-te-mib-01.txt, June 1999." draft-ietf-mpls-te-mib-02.txt, February 2000."
INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel }
::= { mplsInSegmentTable 1 } ::= { mplsInSegmentTable 1 }
MplsInSegmentEntry ::= SEQUENCE { MplsInSegmentEntry ::= SEQUENCE {
mplsInSegmentIfIndex InterfaceIndex, mplsInSegmentIfIndex InterfaceIndex,
mplsInSegmentLabel MplsLabel, mplsInSegmentLabel MplsLabel,
mplsInSegmentNPop Integer32, mplsInSegmentNPop Integer32,
mplsInSegmentAddrFamily MplsLsrIANAAddrFamily, mplsInSegmentAddrFamily MplsLsrIANAAddrFamily,
mplsInSegmentXCIndex Integer32, mplsInSegmentXCIndex Integer32,
mplsInSegmentTSpecIndex Unsigned32, mplsInSegmentTSpecIndex Unsigned32,
mplsInSegmentOwner INTEGER,
mplsInSegmentAdminStatus INTEGER, mplsInSegmentAdminStatus INTEGER,
mplsInSegmentOperStatus INTEGER, mplsInSegmentOperStatus INTEGER,
mplsInSegmentRowStatus RowStatus mplsInSegmentRowStatus RowStatus
} }
mplsInSegmentIfIndex OBJECT-TYPE mplsInSegmentIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Incoming interface index. A value of zero "This is a unique index for an entry in the
represents an incoming label from the per-platform MplsInSegmentTable. This value represents the
label space. In this case, the mplsInSegmentLabel interface index for the incoming MPLS interface. A
is interpreted to be an MPLS-type label." value of zero represents an incoming label from the
per-platform label space. In this case, the
mplsInSegmentLabel is interpreted to be an MPLS-type
label."
::= { mplsInSegmentEntry 1 } ::= { mplsInSegmentEntry 1 }
mplsInSegmentLabel OBJECT-TYPE mplsInSegmentLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The incoming label." "The incoming label for this segment."
::= { mplsInSegmentEntry 2 } ::= { mplsInSegmentEntry 2 }
mplsInSegmentNPop OBJECT-TYPE mplsInSegmentNPop OBJECT-TYPE
SYNTAX Integer32 SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of labels to pop from the incoming "The number of labels to pop from the incoming
packet. Normally only the top label is popped packet. Normally only the top label is popped from
(based on which all switching decisions are taken)." the packet and used for all switching decisions for
that packet."
DEFVAL { 1 } DEFVAL { 1 }
::= { mplsInSegmentEntry 3 } ::= { mplsInSegmentEntry 3 }
mplsInSegmentAddrFamily OBJECT-TYPE mplsInSegmentAddrFamily OBJECT-TYPE
SYNTAX MplsLsrIANAAddrFamily SYNTAX MplsLsrIANAAddrFamily
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IANA address family of the incoming packet. A "The IANA address family of the incoming packet. A
value of zero indicates that the family type is value of zero indicates that the family type is
either unknown or undefined (which could happen for either unknown or undefined. This latter case is
example when streams of different types are merged possible for example, when packet streams of
in a multipoint-to-point connection)." different types are merged in a multipoint-to-point
connection."
REFERENCE REFERENCE
"RFC 1700 - Assigned Numbers, Reynolds and Postel, "RFC 1700 - Assigned Numbers, Reynolds and Postel,
October 1994." October 1994."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsInSegmentEntry 4 } ::= { mplsInSegmentEntry 4 }
mplsInSegmentXCIndex OBJECT-TYPE mplsInSegmentXCIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into mplsXCTable to identify which cross- "The index into mplsXCTable is used to identify which
connect entry this segment is part of. A value of cross-connect entry this segment is part of. Note
zero indicates that it is not being referred to by that a value of zero indicates that it is not being
any cross-connect entry." referred to by any cross-connect entry."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsInSegmentEntry 5 } ::= { mplsInSegmentEntry 5 }
mplsInSegmentTSpecIndex OBJECT-TYPE mplsInSegmentTSpecIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Pointer into mplsTSpecTable indicating the TSpec to "This variable represents a pointer into the
be assigned for this segment. A value of zero mplsTSpecTable and indicates the TSpec which is to
be assigned to this segment. A value of zero
indicates best-effort treatment. Two or more indicates best-effort treatment. Two or more
segments can indicate resource sharing by pointing segments can indicate resource sharing by pointing
to the same entry in mplsTSpecTable." to the same entry in mplsTSpecTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsInSegmentEntry 6 } ::= { mplsInSegmentEntry 6 }
mplsInSegmentOwner OBJECT-TYPE
SYNTAX INTEGER {
snmp(1),
crldp(2),
rsvp(3),
policyAgent(4),
other(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes the entity that created and is responsible
for managing this segment."
::= { mplsInSegmentEntry 7 }
mplsInSegmentAdminStatus OBJECT-TYPE mplsInSegmentAdminStatus 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
"Desired status of this segment." "This value is used to represent the managerĘs
::= { mplsInSegmentEntry 7 } desired operational status of this segment."
::= { mplsInSegmentEntry 8 }
mplsInSegmentOperStatus OBJECT-TYPE mplsInSegmentOperStatus 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 for unknown(4), -- status cannot be determined for
-- some reason -- some reason
dormant(5), domant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerNotPresent(7) lowerLayerDown(7)
-- down due to the state of -- 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
"The operational status of this segment." "This value represents the actual operational status
::= { mplsInSegmentEntry 8 } of this segment."
::= { mplsInSegmentEntry 9 }
mplsInSegmentRowStatus OBJECT-TYPE mplsInSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row." "This variable is used to create, modify, and/or
::= { mplsInSegmentEntry 9 } delete a row in this table."
::= { mplsInSegmentEntry 10 }
-- End of mplsInSegmentTable -- End of mplsInSegmentTable
-- In-segment performance table. -- In-segment performance table.
mplsInSegmentPerfTable OBJECT-TYPE mplsInSegmentPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentPerfEntry SYNTAX SEQUENCE OF MplsInSegmentPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains statistical information about "This table contains statistical information for
incoming MPLS segments to an LSR." incoming MPLS segments to an LSR."
::= { mplsLsrObjects 4 } ::= { mplsLsrObjects 4 }
mplsInSegmentPerfEntry OBJECT-TYPE mplsInSegmentPerfEntry OBJECT-TYPE
SYNTAX MplsInSegmentPerfEntry SYNTAX MplsInSegmentPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains statistical "An entry in this table contains statistical
information about one incoming segment configured in information about one incoming segment which was
mplsInSegmentTable." configured in the mplsInSegmentTable."
AUGMENTS { mplsInSegmentEntry } AUGMENTS { mplsInSegmentEntry }
::= { mplsInSegmentPerfTable 1 } ::= { mplsInSegmentPerfTable 1 }
MplsInSegmentPerfEntry ::= SEQUENCE { MplsInSegmentPerfEntry ::= SEQUENCE {
mplsInSegmentOctets Counter32, mplsInSegmentOctets Counter32,
mplsInSegmentPackets Counter32, mplsInSegmentPackets Counter32,
mplsInSegmentErrors Counter32, mplsInSegmentErrors Counter32,
mplsInSegmentDiscards Counter32, mplsInSegmentDiscards Counter32,
-- high capacity counter -- high capacity counter
mplsInSegmentHCOctets Counter64 mplsInSegmentHCOctets Counter64
} }
mplsInSegmentOctets OBJECT-TYPE mplsInSegmentOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of octets received." "This value represents the total number of octets
received by this segment."
::= { mplsInSegmentPerfEntry 1 } ::= { mplsInSegmentPerfEntry 1 }
mplsInSegmentPackets OBJECT-TYPE mplsInSegmentPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of packets received." "Total number of packets received by this segment."
::= { mplsInSegmentPerfEntry 2 } ::= { mplsInSegmentPerfEntry 2 }
mplsInSegmentErrors OBJECT-TYPE mplsInSegmentErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of errored packets received." "The number of packets received in error by this
LSR."
::= { mplsInSegmentPerfEntry 3 } ::= { mplsInSegmentPerfEntry 3 }
mplsInSegmentDiscards OBJECT-TYPE mplsInSegmentDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets received that had to be dropped "The number of labeled packets received on this in-
either because of errors or for other reasons such segment, which were chosen to be discarded even
as buffer overflows." though no errors had been detected to prevent their
being transmitted. One possible reason for
discarding such a labeled packet could be to free up
buffer space."
::= { mplsInSegmentPerfEntry 4 } ::= { mplsInSegmentPerfEntry 4 }
mplsInSegmentHCOctets OBJECT-TYPE mplsInSegmentHCOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of octets received. This is the 64 bit "The total number of octets received. This is the 64
version of mplsInSegmentOctets." bit version of mplsInSegmentOctets."
::= { mplsInSegmentPerfEntry 5 } ::= { mplsInSegmentPerfEntry 5 }
-- End of mplsInSegmentPerfTable. -- End of mplsInSegmentPerfTable.
-- Out-segment table. -- Out-segment table.
mplsOutSegmentIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the next appropriate value to
be used for mplsOutSegmentIndex when creating
entries in the mplsOutSegmentTable. If the number of
unassigned entries is exhausted, this object will
take on the value of 0. To obtain the
mplsOutSegmentIndex 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."
::= { mplsLsrObjects 5 }
mplsOutSegmentTable OBJECT-TYPE mplsOutSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentEntry SYNTAX SEQUENCE OF MplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a description of the outgoing "This table contains a representation of the outgoing
segments from an LSR." segments from an LSR."
::= { mplsLsrObjects 5 } ::= { mplsLsrObjects 6 }
mplsOutSegmentEntry OBJECT-TYPE mplsOutSegmentEntry OBJECT-TYPE
SYNTAX MplsOutSegmentEntry SYNTAX MplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents one outgoing "An entry in this table represents one incoming
segment. An entry can be created by a network segment. An entry can be created by a network
administrator or by an SNMP agent as instructed by administrator or by an SNMP agent as instructed by
LDP or RSVP. Note that some of the segments are CR-LDP or RSVP. The creator of the entry is denoted
associated with a tunnel, the traffic parameters of by mplsOutSegmentOwner. An entry in this table is
these rows are supported as read-only objects and indexed by the ifIndex of the incoming interface and
their modification can be done only via the tunnel the (top) label. Note that since it is possible
table, mplsTunnelTable. This issue will be addressed that some segments are associated with a tunnel,
more naturally when ownership related objects are traffic parameters of these rows are supported as
introduced into these tables." read-only objects and their modification can be done
only via the tunnel table, mplsTunnelTable."
REFERENCE REFERENCE
"MPLS Traffic Engineering Management Information Base "MPLS Traffic Engineering Management Information Base
Using SMIv2, Srinivasan and Viswanathan, draft-ietf- Using SMIv2, Srinivasan, Viswanathan and Nadeau,
mpls-te-mib-01.txt, June 1999." draft-ietf-mpls-te-mib-02.txt, February 2000."
INDEX { mplsOutSegmentIndex } INDEX { mplsOutSegmentIndex }
::= { mplsOutSegmentTable 1 } ::= { mplsOutSegmentTable 1 }
MplsOutSegmentEntry ::= SEQUENCE { MplsOutSegmentEntry ::= SEQUENCE {
mplsOutSegmentIndex Integer32, mplsOutSegmentIndex Integer32,
mplsOutSegmentIfIndex InterfaceIndex, mplsOutSegmentIfIndex InterfaceIndex,
mplsOutSegmentPushTopLabel TruthValue, mplsOutSegmentPushTopLabel TruthValue,
mplsOutSegmentTopLabel MplsLabel, mplsOutSegmentTopLabel MplsLabel,
mplsOutSegmentNextHopIpAddrType INTEGER, mplsOutSegmentNextHopIpAddrType INTEGER,
mplsOutSegmentNextHopIpv4Addr IpAddress, mplsOutSegmentNextHopIpv4Addr IpAddress,
mplsOutSegmentNextHopIpv6Addr Ipv6Address, mplsOutSegmentNextHopIpv6Addr Ipv6Address,
mplsOutSegmentXCIndex Integer32, mplsOutSegmentXCIndex Integer32,
mplsOutSegmentTSpecIndex Unsigned32, mplsOutSegmentTSpecIndex Unsigned32,
mplsOutSegmentOwner INTEGER,
mplsOutSegmentAdminStatus INTEGER, mplsOutSegmentAdminStatus INTEGER,
mplsOutSegmentOperStatus INTEGER, mplsOutSegmentOperStatus INTEGER,
mplsOutSegmentRowStatus RowStatus mplsOutSegmentRowStatus RowStatus
} }
mplsOutSegmentIndex OBJECT-TYPE mplsOutSegmentIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unique index for this row. While a value of 0 is "This value contains a unique index for this row.
not valid as an index for this row it can be While a value of 0 is not valid as an index for this
supplied as a valid value to index mplsXCTable to row it can be supplied as a valid value to index
access entries for which no out-segment has been mplsXCTable to access entries for which no out-
configured." segment has been configured."
::= { mplsOutSegmentEntry 1 } ::= { mplsOutSegmentEntry 1 }
mplsOutSegmentIfIndex OBJECT-TYPE mplsOutSegmentIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Interface index of the outgoing interface." "This value contains the interface index of the
outgoing interface."
::= { mplsOutSegmentEntry 2 } ::= { mplsOutSegmentEntry 2 }
mplsOutSegmentPushTopLabel OBJECT-TYPE mplsOutSegmentPushTopLabel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether a top label should be pushed onto the "This value indicates whether or not a top label
outgoing packet's label stack. Its value has to be should be pushed onto the outgoing packet's label
true if the outgoing interface is ATM (which does stack. The value of this variable must be set to
not support `pop-and-go') or if it is a tunnel true if the outgoing interface is ATM, which does
origination. Note also that the case where not support pop-and-go, or if it is a tunnel
mplsOutSegmentPushTopLabel is set to false but the origination. Note that it is considered an error in
cross-connect entry that refers to this out-segment the case that mplsOutSegmentPushTopLabel is set to
has a non-zero mplsLabelStackIndex is an error which false, but the cross-connect entry which refers to
the LSR should ensure doesn't happen." this out-segment has a non-zero mplsLabelStackIndex.
The LSR should ensure that this situation cannot
happen "
::= { mplsOutSegmentEntry 3 } ::= { mplsOutSegmentEntry 3 }
mplsOutSegmentTopLabel OBJECT-TYPE mplsOutSegmentTopLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If mplsOutSegmentPushTopLabel is true then this is "If mplsOutSegmentPushTopLabel is true then this is
the label that should be pushed onto the outgoing the label that should be pushed onto the outgoing
packet's label stack. Note that the contents of the packet's label stack. Note that the contents of the
skipping to change at page 24, line 18 skipping to change at page 28, line 42
For ATM interfaces the lowermost 16 bits are For ATM interfaces the lowermost 16 bits are
interpreted as the VCI, the next 8 bits as the VPI interpreted as the VCI, the next 8 bits as the VPI
and the remaining bits must be zero." and the remaining bits must be zero."
::= { mplsOutSegmentEntry 4 } ::= { mplsOutSegmentEntry 4 }
mplsOutSegmentNextHopIpAddrType OBJECT-TYPE mplsOutSegmentNextHopIpAddrType OBJECT-TYPE
SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) } SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether the next hop address is IPv4 or IPv6. A "Indicates whether the next hop address is IPv4 or
value of none (1) is valid (only) when the outgoing IPv6. Note that a value of none (1) is valid only
interface is of type point-to-point." when the outgoing interface is of type point-to-
point."
DEFVAL { none } DEFVAL { none }
::= { mplsOutSegmentEntry 5 } ::= { mplsOutSegmentEntry 5 }
mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IPv4 Address of the next hop. Its value is "IPv4 Address of the next hop. Its value is
significant only when significant only when
skipping to change at page 24, line 51 skipping to change at page 29, line 26
significant only when significant only when
mplsOutSegmentNextHopIpAddrType is ipV6 (3), mplsOutSegmentNextHopIpAddrType is ipV6 (3),
otherwise it should return a value of 0." otherwise it should return a value of 0."
::= { mplsOutSegmentEntry 7 } ::= { mplsOutSegmentEntry 7 }
mplsOutSegmentXCIndex OBJECT-TYPE mplsOutSegmentXCIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into mplsXCTable to identify which cross- "Index into mplsXCTable which identifies which cross-
connect entry this segment is part of. A value of connect entry this segment is part of. A value of
zero indicates that it is not being referred to by zero indicates that this entry is not referred to by
any cross-connect entry." any cross-connect entry."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOutSegmentEntry 8 } ::= { mplsOutSegmentEntry 8 }
mplsOutSegmentTSpecIndex OBJECT-TYPE mplsOutSegmentTSpecIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Pointer into mplsTSpecTable indicating the TSpec to "A pointer into the mplsTSpecTable indicating the
be assigned for this segment. A value of zero TSpec to be assigned for this segment. A value of
indicates best-effort treatment. Two or more zero indicates best-effort treatment. Two or more
segments can indicate resource sharing by pointing segments can indicate resource sharing by pointing
to the same entry in mplsTSpecTable." to the same entry in mplsTSpecTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOutSegmentEntry 9 } ::= { mplsOutSegmentEntry 9 }
mplsOutSegmentOwner OBJECT-TYPE
SYNTAX INTEGER {
snmp(1),
crldp(2),
rsvp(3),
policyAgent(4),
other(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes the entity which created and is responsible
for managing this segment."
::= { mplsOutSegmentEntry 10 }
mplsOutSegmentAdminStatus OBJECT-TYPE mplsOutSegmentAdminStatus 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
"Desired status of this segment." "The desired operational status of this segment."
::= { mplsOutSegmentEntry 10 } ::= { mplsOutSegmentEntry 11 }
mplsOutSegmentOperStatus OBJECT-TYPE mplsOutSegmentOperStatus 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 for unknown(4), -- status cannot be determined for
-- some reason -- some reason
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerNotPresent(7) lowerLayerDown(7)
-- down due to the state of -- 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
"The operational status of this segment." "The actual operational status of this segment."
::= { mplsOutSegmentEntry 11 } ::= { mplsOutSegmentEntry 12 }
mplsOutSegmentRowStatus OBJECT-TYPE mplsOutSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row." "For creating, modifying, and deleting this row."
::= { mplsOutSegmentEntry 12 } ::= { mplsOutSegmentEntry 13 }
-- End of mplsOutSegmentTable -- End of mplsOutSegmentTable
-- Out-segment performance table. -- Out-segment performance table.
mplsOutSegmentPerfTable OBJECT-TYPE mplsOutSegmentPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains statistical information about "This table contains statistical information about
incoming segments to an LSR." incoming segments to an LSR."
::= { mplsLsrObjects 6 } ::= { mplsLsrObjects 7 }
mplsOutSegmentPerfEntry OBJECT-TYPE mplsOutSegmentPerfEntry OBJECT-TYPE
SYNTAX MplsOutSegmentPerfEntry SYNTAX MplsOutSegmentPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains statistical "An entry in this table contains statistical
information about one incoming segment configured in information about one incoming segment configured in
mplsOutSegmentTable." mplsOutSegmentTable."
AUGMENTS { mplsOutSegmentEntry } AUGMENTS { mplsOutSegmentEntry }
skipping to change at page 26, line 49 skipping to change at page 31, line 42
-- HC counter -- HC counter
mplsOutSegmentHCOctets Counter64 mplsOutSegmentHCOctets Counter64
} }
mplsOutSegmentOctets OBJECT-TYPE mplsOutSegmentOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of octets sent." "This value contains the total number of octets sent
on this segment."
::= { mplsOutSegmentPerfEntry 1 } ::= { mplsOutSegmentPerfEntry 1 }
mplsOutSegmentPackets OBJECT-TYPE mplsOutSegmentPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of packets sent." "This value contains the total number of packets sent
on this segment."
::= { mplsOutSegmentPerfEntry 2 } ::= { mplsOutSegmentPerfEntry 2 }
mplsOutSegmentErrors OBJECT-TYPE mplsOutSegmentErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets that could not be sent due to "Number of packets that could not be sent due to
errors." errors."
::= { mplsOutSegmentPerfEntry 3 } ::= { mplsOutSegmentPerfEntry 3 }
mplsOutSegmentDiscards OBJECT-TYPE mplsOutSegmentDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of outgoing packets that had to be dropped "The number of labeled packets received on this out-
either because of errors or for other reasons such segment, which were chosen to be discarded even
as buffer overflows." though no errors had been detected to prevent their
being transmitted. One possible reason for
discarding such a labeled packet could be to free up
buffer space."
::= { mplsOutSegmentPerfEntry 4 } ::= { mplsOutSegmentPerfEntry 4 }
mplsOutSegmentHCOctets OBJECT-TYPE mplsOutSegmentHCOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of octets sent. This is the 64 bit "Total number of octets sent. This is the 64 bit
version of mplsOutSegmentOctets." version of mplsOutSegmentOctets."
::= { mplsOutSegmentPerfEntry 5 } ::= { mplsOutSegmentPerfEntry 5 }
-- End of mplsOutSegmentPerfTable. -- End of mplsOutSegmentPerfTable.
-- Cross-connect table. -- Cross-connect table.
mplsXCIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to be used
for mplsXCIndex when creating entries in the
mplsXCTable. The value 0 indicates that no
unassigned entries are available. To obtain the
value of mplsXCIndex for a new entry in the
mplsXCTable, the manager issues a management
protocol retrieval operation to obtain the current
value of mplsXCIndex. 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."
::= { mplsLsrObjects 8 }
mplsXCTable OBJECT-TYPE mplsXCTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCEntry SYNTAX SEQUENCE OF MplsXCEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies information for switching "This table specifies information for switching
between LSP segments. It supports point-to-point, between LSP segments. It supports point-to-point,
point-to-multipoint and multipoint-to-point point-to-multipoint and multipoint-to-point
connections. mplsLabelStackTable specifies the connections. mplsLabelStackTable specifies the
label stack information for a cross-connect LSR and label stack information for a cross-connect LSR and
is referred to from mplsXCTable." is referred to from mplsXCTable."
::= { mplsLsrObjects 7 } ::= { mplsLsrObjects 9 }
mplsXCEntry OBJECT-TYPE mplsXCEntry OBJECT-TYPE
SYNTAX MplsXCEntry SYNTAX MplsXCEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents one cross-connect "A row in this table represents one cross-connect
entry. It is indexed by the following objects: entry. The following objects index it:
- cross-connect index mplsXCIndex that uniquely - cross-connect index mplsXCIndex that uniquely
identifies a group of cross-connect entries identifies a group of cross-connect entries
- interface index of the in-segment, - interface index of the in-segment,
mplsInSegmentIfIndex mplsInSegmentIfIndex
- incoming label(s), mplsInSegmentLabel - incoming label(s), mplsInSegmentLabel
- out-segment index, mplsOutSegmentIndex - out-segment index, mplsOutSegmentIndex
Originating LSPs: Originating LSPs:
These are represented by using the special These are represented by using the special
skipping to change at page 28, line 37 skipping to change at page 34, line 5
Terminating LSPs: Terminating LSPs:
These are represented by using the special value These are represented by using the special value
mplsOutSegmentIndex=0 as index. mplsOutSegmentIndex=0 as index.
Special labels: Special labels:
Entries indexed by reserved MPLS label values 0 Entries indexed by reserved MPLS label values 0
through 15 imply terminating LSPs and MUST have through 15 imply terminating LSPs and MUST have
mplsOutSegmentIndex=0. mplsOutSegmentIndex=0.
An entry can be created by a network administrator An entry can be created by a network administrator or
or by an SNMP agent as instructed by LDP or RSVP." by an SNMP agent as instructed by CR-LDP or RSVP."
INDEX { mplsXCIndex, mplsInSegmentIfIndex, INDEX { mplsXCIndex, mplsInSegmentIfIndex,
mplsInSegmentLabel, mplsOutSegmentIndex } mplsInSegmentLabel, mplsOutSegmentIndex }
::= { mplsXCTable 1 } ::= { mplsXCTable 1 }
MplsXCEntry ::= SEQUENCE { MplsXCEntry ::= SEQUENCE {
mplsXCIndex INTEGER, mplsXCIndex INTEGER,
mplsXCLspId MplsLSPID,
mplsXCLabelStackIndex Integer32, mplsXCLabelStackIndex Integer32,
mplsXCCOS Integer32, mplsXCCOS Integer32,
mplsXCIsPersistent TruthValue, mplsXCIsPersistent TruthValue,
mplsXCAdminStatus INTEGER, mplsXCAdminStatus INTEGER,
mplsXCOperStatus INTEGER, mplsXCOperStatus INTEGER,
mplsXCRowStatus RowStatus mplsXCRowStatus RowStatus
} }
mplsXCIndex OBJECT-TYPE mplsXCIndex OBJECT-TYPE
SYNTAX INTEGER (0..4294967295) SYNTAX INTEGER (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index for the row identifying a group of "Primary index for the row identifying a group of
cross-connect segments." cross-connect segments."
::= { mplsXCEntry 1 } ::= { mplsXCEntry 1 }
mplsXCLspId OBJECT-TYPE
SYNTAX MplsLSPID
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value identifies the label switched path that
this cross-connect entry belongs to."
::= { mplsXCEntry 2 }
mplsXCLabelStackIndex OBJECT-TYPE mplsXCLabelStackIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index into mplsLabelStackTable identifying a "Primary index into mplsLabelStackTable identifying a
stack of labels to be pushed beneath the top label. stack of labels to be pushed beneath the top label.
Note that the top label is identified in the out- Note that the top label identified by the out-
segment which ensures that all the components of a segment ensures that all the components of a
multipoint-to-point connection have the same multipoint-to-point connection have the same
outgoing label. A value of 0 indicates that no outgoing label. A value of 0 indicates that no
labels are to be stacked beneath the top label." labels are to be stacked beneath the top label."
::= { mplsXCEntry 2 } ::= { mplsXCEntry 3 }
mplsXCCOS OBJECT-TYPE mplsXCCOS OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Value to override the incoming COS field with for a "This value is used to override the incoming COS
cross-connect or the value to assign to outgoing field for a cross-connect. It may also be used as a
packets for an outgoing segment of a tunnel." value to assign to outgoing packets for an outgoing
::= { mplsXCEntry 3 } segment of a tunnel. Note that packet treatment at
this LSR is determined by the incoming COS value and
the new COS value only impacts packet treatment at a
downstream LSR."
::= { mplsXCEntry 4 }
mplsXCIsPersistent OBJECT-TYPE mplsXCIsPersistent OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether this cross-connect entry and associated in- "Denotes whether or not this cross-connect entry and
and out-segments should be restored automatically associated in- and out-segments should be restored
after failures." automatically after failures."
DEFVAL { false } DEFVAL { false }
::= { mplsXCEntry 4 } ::= { mplsXCEntry 5 }
mplsXCAdminStatus OBJECT-TYPE mplsXCAdminStatus 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
"Desired status of this segment." "The desired operational status of this segment."
::= { mplsXCEntry 5 } ::= { mplsXCEntry 6 }
mplsXCOperStatus OBJECT-TYPE mplsXCOperStatus 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 for unknown(4), -- status cannot be determined for
-- some reason -- some reason
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerNotPresent(7) lowerLayerDown(7)
-- down due to the state of -- 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
"The operational status of this segment." "The actual operational status of this cross-
::= { mplsXCEntry 6 } connect."
::= { mplsXCEntry 7 }
mplsXCRowStatus OBJECT-TYPE mplsXCRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row." "For creating, modifying, and deleting this row."
::= { mplsXCEntry 7 } ::= { mplsXCEntry 8 }
-- End of mplsXCTable -- End of mplsXCTable
-- Label stack table. -- Label stack table.
mplsMaxLabelStackDepth OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum stack depth supported by this LSR."
::= { mplsLsrObjects 10 }
mplsLabelStackIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to be used
for mplsLabelStackIndex when creating entries in the
mplsLabelStackTable. The value 0 indicates that no
unassigned entries are available. To obtain an
mplsLabelStackIndex value for a new entry, the
manager issues a management protocol retrieval
operation to obtain the current value of this
object. 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."
::= { mplsLsrObjects 11 }
mplsLabelStackTable OBJECT-TYPE mplsLabelStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLabelStackEntry SYNTAX SEQUENCE OF MplsLabelStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the label stack to be pushed "This table specifies the label stack to be pushed
onto a packet, beneath the top label. Entries into onto a packet, beneath the top label. Entries into
this table are referred to from mplsXCTable." this table are referred to from mplsXCTable."
::= { mplsLsrObjects 8 } ::= { mplsLsrObjects 12 }
mplsLabelStackEntry OBJECT-TYPE mplsLabelStackEntry OBJECT-TYPE
SYNTAX MplsLabelStackEntry SYNTAX MplsLabelStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents one label to be "An entry in this table represents one label which is
pushed onto an outgoing packets beneath the top to be pushed onto an outgoing packet, beneath the
label. An entry can be created by a network top label. An entry can be created by a network
administrator or by an SNMP agent as instructed by administrator or by an SNMP agent as instructed by
LDP or RSVP." CR-LDP or RSVP."
INDEX { mplsLabelStackIndex } INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex }
::= { mplsLabelStackTable 1 } ::= { mplsLabelStackTable 1 }
MplsLabelStackEntry ::= SEQUENCE { MplsLabelStackEntry ::= SEQUENCE {
mplsLabelStackIndex Integer32, mplsLabelStackIndex Integer32,
mplsLabelStackLabelIndex Integer32, mplsLabelStackLabelIndex Integer32,
mplsLabelStackLabel MplsLabel, mplsLabelStackLabel MplsLabel,
mplsLabelStackRowStatus RowStatus mplsLabelStackRowStatus RowStatus
} }
mplsLabelStackIndex OBJECT-TYPE mplsLabelStackIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary index for this row identifying a stack of "Primary index for this row identifying a stack of
labels to be pushed on an outgoing packet beneath labels to be pushed on an outgoing packet, beneath
the top label." the top label."
::= { mplsLabelStackEntry 1 } ::= { mplsLabelStackEntry 1 }
mplsLabelStackLabelIndex OBJECT-TYPE mplsLabelStackLabelIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Secondary index for this row identifying one label "Secondary index for this row identifying one label
of the stack." of the stack. Note that an entry with a smaller
mplsLabelStackLabelIndex would refer to a label
higher up the label stack and would be popped before
a label represented by a higher
mplsLabelStackLabelIndex at a downstream LSR."
::= { mplsLabelStackEntry 2 } ::= { mplsLabelStackEntry 2 }
mplsLabelStackLabel OBJECT-TYPE mplsLabelStackLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Label to pushed." "The label to pushed."
::= { mplsLabelStackEntry 3 } ::= { mplsLabelStackEntry 3 }
mplsLabelStackRowStatus OBJECT-TYPE mplsLabelStackRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row." "For creating, modifying, and deleting this row."
::= { mplsLabelStackEntry 4 } ::= { mplsLabelStackEntry 4 }
-- End of mplsLabelStackTable -- End of mplsLabelStackTable
-- TSpec table. -- TSpec table.
mplsTSpecIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value which will
be used for mplsTSpecIndex when creating entries in
the mplsTSpecTable. The value 0 indicates that no
unassigned entries are available. To obtain the
mplsTSpecIndex value for a new entry, the manager
issues a management protocol retrieval operation to
obtain the current value of this object. 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."
::= { mplsLsrObjects 13 }
mplsTSpecTable OBJECT-TYPE mplsTSpecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTSpecEntry SYNTAX SEQUENCE OF MplsTSpecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies TSpec objects for in and out- "This table specifies the Traffic Specification
segments." (TSpec) objects for in and out-segments."
::= { mplsLsrObjects 9 } ::= { mplsLsrObjects 14 }
mplsTSpecEntry OBJECT-TYPE mplsTSpecEntry OBJECT-TYPE
SYNTAX MplsTSpecEntry SYNTAX MplsTSpecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents the TSpec objects "An entry in this table represents the TSpec objects
for one or more in or out segments. A single entry for one or more in or out segments. A single entry
can be pointed to by multiple segments indicating can be pointed to by multiple segments indicating
resource sharing." resource sharing."
INDEX { mplsTSpecIndex } INDEX { mplsTSpecIndex }
::= { mplsTSpecTable 1 } ::= { mplsTSpecTable 1 }
MplsTSpecEntry ::= SEQUENCE { MplsTSpecEntry ::= SEQUENCE {
mplsTSpecIndex Unsigned32, mplsTSpecIndex Unsigned32,
mplsTSpecIfIndex InterfaceIndex,
mplsTSpecDirection INTEGER, mplsTSpecDirection INTEGER,
mplsTSpecMaxRate BitRate, mplsTSpecMaxRate BitRate,
mplsTSpecMeanRate BitRate, mplsTSpecMeanRate BitRate,
mplsTSpecMaxBurstSize BurstSize, mplsTSpecMaxBurstSize BurstSize,
mplsTSpecRowStatus RowStatus mplsTSpecRowStatus RowStatus
} }
mplsTSpecIndex OBJECT-TYPE mplsTSpecIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies this row of the table. Zero is "Uniquely identifies this row of the table. Note
not a valid index." that zero represents an invalid index."
::= { mplsTSpecEntry 1 } ::= { mplsTSpecEntry 1 }
mplsTSpecIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Identifies the interface that this entry refers to."
::= { mplsTSpecEntry 2 }
mplsTSpecDirection OBJECT-TYPE mplsTSpecDirection OBJECT-TYPE
SYNTAX INTEGER { in(1), out(2) } SYNTAX INTEGER { in(1), out(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Direction that these objects pertain to, incoming or "The direction that these objects pertain to. Valid
outgoing." values specify either incoming or outgoing
::= { mplsTSpecEntry 3 } directions."
::= { mplsTSpecEntry 2 }
mplsTSpecMaxRate OBJECT-TYPE mplsTSpecMaxRate OBJECT-TYPE
SYNTAX BitRate SYNTAX BitRate
UNITS "bits per second" UNITS "bits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum rate in bits/second." "Maximum rate in bits/second."
::= { mplsTSpecEntry 4 } ::= { mplsTSpecEntry 3 }
mplsTSpecMeanRate OBJECT-TYPE mplsTSpecMeanRate OBJECT-TYPE
SYNTAX BitRate SYNTAX BitRate
UNITS "bits per second" UNITS "bits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Mean rate in bits/second." "Mean rate in bits/second."
::= { mplsTSpecEntry 5 } ::= { mplsTSpecEntry 4 }
mplsTSpecMaxBurstSize OBJECT-TYPE mplsTSpecMaxBurstSize OBJECT-TYPE
SYNTAX BurstSize SYNTAX BurstSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum burst size in bytes." "Maximum burst size in bytes."
::= { mplsTSpecEntry 6 } ::= { mplsTSpecEntry 5 }
mplsTSpecRowStatus OBJECT-TYPE mplsTSpecRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row." "For creating, modifying, and deleting this row."
::= { mplsTSpecEntry 7 } ::= { mplsTSpecEntry 6 }
-- End of mplsTSpecTable -- End of mplsTSpecTable
-- Notifications. -- Notifications.
-- Interface configuration. -- Interface configuration.
mplsInterfaceUp NOTIFICATION-TYPE mplsInterfaceUp NOTIFICATION-TYPE
OBJECTS { mplsInterfaceConfIndex, OBJECTS { mplsInterfaceConfIndex,
mplsInterfaceAdminStatus, mplsInterfaceOperStatus } mplsInterfaceAdminStatus, mplsInterfaceOperStatus }
skipping to change at page 36, line 47 skipping to change at page 43, line 22
mplsLsrModuleCompliance MODULE-COMPLIANCE mplsLsrModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
MPLS LSR MIB." MPLS LSR MIB."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented by all LSRs. -- The mandatory groups have to be implemented by all LSRs.
-- However, they may all be supported as read-only objects -- However, they may all be supported as read-only objects
-- in the case where manual configuration is not -- in the case where manual configuration is unsupported.
-- supported.
MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsInterfaceGroup, mplsXCGroup, mplsInterfaceGroup,
mplsPerfGroup } mplsPerfGroup }
GROUP mplsHCInterfacePerfGroup GROUP mplsHCInterfacePerfGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for high-speed MPLS "This group is mandatory for high-speed MPLS
capable interfaces for which the objects capable interfaces for which the objects
mplsInterfaceInOctets and mplsInterfaceOutOctets mplsInterfaceInOctets and mplsInterfaceOutOctets
wrap around too quickly." wrap around too quickly."
GROUP mplsHCInSegmentPerfGroup GROUP mplsHCInSegmentPerfGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those in-segment "This group is mandatory for those in-segment
skipping to change at page 37, line 27 skipping to change at page 43, line 51
GROUP mplsHCOutSegmentPerfGroup GROUP mplsHCOutSegmentPerfGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those out-segment "This group is mandatory for those out-segment
entries for which the object entries for which the object
mplsOutSegmentOctets wraps around too quickly." mplsOutSegmentOctets wraps around too quickly."
GROUP mplsTSpecGroup GROUP mplsTSpecGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those LSRs that "This group is mandatory for those LSRs that
support int-serv style resource reservation." support Int-Serv style resource reservation."
-- Depending on whether the device implements persistent -- Depending on whether the device implements persistent
-- cross-connects or not one of the following two groups -- cross-connects or not one of the following two groups
-- is mandatory. -- is mandatory.
GROUP mplsXCIsPersistentGroup GROUP mplsXCIsPersistentGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which
support persistent cross-connects. The support persistent cross-connects. The
following constraints apply: mplsXCIsPersistent following constraints apply: mplsXCIsPersistent
skipping to change at page 39, line 16 skipping to change at page 45, line 40
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only up(1) and down(2) need to be supported." "Only up(1) and down(2) need to be supported."
OBJECT mplsInSegmentRowStatus OBJECT mplsInSegmentRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), createAndGo(4),
destroy(6) } destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need not "The notReady(3) and createAndWait(5) states need
be supported." not be supported."
-- mplsOutSegmentTable -- mplsOutSegmentTable
OBJECT mplsOutSegmentIndexNext
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsOutSegmentIndex OBJECT mplsOutSegmentIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsOutSegmentIfIndex OBJECT mplsOutSegmentIfIndex
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 40, line 33 skipping to change at page 47, line 11
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT mplsOutSegmentOperStatus OBJECT mplsOutSegmentOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only up(1) and down(2) need to be supported." "Only up(1) and down(2) need to be supported."
OBJECT mplsOutSegmentRowStatus OBJECT mplsOutSegmentRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), createAndGo(4), destroy(6) }
destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
-- mplsXCTable -- mplsXCTable
OBJECT mplsXCIndexNext
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsXCIndex OBJECT mplsXCIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsXCLabelStackIndexNext
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsXCLabelStackIndex OBJECT mplsXCLabelStackIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsXCCOS OBJECT mplsXCCOS
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 41, line 27 skipping to change at page 48, line 14
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT mplsXCOperStatus OBJECT mplsXCOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only up(1) and down(2) need to be supported." "Only up(1) and down(2) need to be supported."
OBJECT mplsXCRowStatus OBJECT mplsXCRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), createAndGo(4), destroy(6) }
destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
::= { mplsLsrCompliances 1 } ::= { mplsLsrCompliances 1 }
-- Units of conformance. -- Units of conformance.
mplsInterfaceGroup OBJECT-GROUP mplsInterfaceGroup OBJECT-GROUP
OBJECTS { mplsInterfaceConfIndex, OBJECTS { mplsInterfaceConfIndex,
mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,
mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut, mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut,
mplsInterfaceAdminStatus, mplsInterfaceOperStatus, mplsInterfaceAdminStatus, mplsInterfaceOperStatus,
mplsInterfaceInLabelsUsed, mplsInterfaceOutLabelsUsed } mplsInterfaceInLabelsUsed,
mplsInterfaceOutLabelsUsed }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS interface "Collection of objects needed for MPLS interface
configuration and performance information." configuration and performance information."
::= { mplsLsrGroups 1 } ::= { mplsLsrGroups 1 }
mplsInSegmentGroup OBJECT-GROUP mplsInSegmentGroup OBJECT-GROUP
OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel,
mplsInSegmentNPop, mplsInSegmentAddrFamily, mplsInSegmentNPop, mplsInSegmentAddrFamily,
mplsInSegmentXCIndex, mplsInSegmentTSpecIndex, mplsInSegmentXCIndex, mplsInSegmentTSpecIndex,
mplsInSegmentAdminStatus, mplsInSegmentOperStatus, mplsInSegmentAdminStatus, mplsInSegmentOperStatus,
mplsInSegmentRowStatus, mplsInSegmentRowStatus,
mplsInSegmentOctets, mplsInSegmentDiscards } mplsInSegmentOctets, mplsInSegmentDiscards }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement an in- "Collection of objects needed to implement an in-
segment." segment."
::= { mplsLsrGroups 2 } ::= { mplsLsrGroups 2 }
mplsOutSegmentGroup OBJECT-GROUP mplsOutSegmentGroup OBJECT-GROUP
OBJECTS { mplsOutSegmentIndex, mplsOutSegmentIfIndex, OBJECTS { mplsOutSegmentIndexNext,
mplsOutSegmentIndex, mplsOutSegmentIfIndex,
mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel, mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel,
mplsOutSegmentNextHopIpAddrType, mplsOutSegmentNextHopIpAddrType,
mplsOutSegmentNextHopIpv4Addr, mplsOutSegmentNextHopIpv4Addr,
mplsOutSegmentNextHopIpv6Addr, mplsOutSegmentNextHopIpv6Addr,
mplsOutSegmentXCIndex, mplsOutSegmentTSpecIndex, mplsOutSegmentXCIndex, mplsOutSegmentTSpecIndex,
mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus, mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus,
mplsOutSegmentRowStatus, mplsOutSegmentRowStatus,
mplsOutSegmentOctets, mplsOutSegmentDiscards } mplsOutSegmentOctets, mplsOutSegmentDiscards }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement an out- "Collection of objects needed to implement an out-
segment." segment."
::= { mplsLsrGroups 3 } ::= { mplsLsrGroups 3 }
mplsXCGroup OBJECT-GROUP mplsXCGroup OBJECT-GROUP
OBJECTS { mplsXCIndex, mplsXCLabelStackIndex, OBJECTS { mplsXCIndexNext,
mplsXCAdminStatus, mplsXCOperStatus, mplsXCRowStatus } mplsXCIndex, mplsXCLabelStackIndex,
mplsXCAdminStatus, mplsXCOperStatus,
mplsXCRowStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a cross- "Collection of objects needed to implement a
connect entry." cross-connect entry."
::= { mplsLsrGroups 4 } ::= { mplsLsrGroups 4 }
mplsPerfGroup OBJECT-GROUP mplsPerfGroup OBJECT-GROUP
OBJECTS { mplsInterfaceInOctets, mplsInterfaceInPackets, OBJECTS { mplsInterfaceInPackets, mplsInterfaceInDiscards,
mplsInterfaceInDiscards, mplsInterfaceOutPackets, mplsInterfaceOutDiscards,
mplsInterfaceOutOctets, mplsInterfaceOutPackets,
mplsInterfaceOutDiscards,
mplsInSegmentOctets, mplsInSegmentPackets, mplsInSegmentOctets, mplsInSegmentPackets,
mplsInSegmentDiscards, mplsInSegmentDiscards,
mplsOutSegmentOctets, mplsOutSegmentPackets, mplsOutSegmentOctets, mplsOutSegmentPackets,
mplsOutSegmentDiscards } mplsOutSegmentDiscards }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects providing performance "Collection of objects providing performance
information about an LSR." information
about an LSR."
::= { mplsLsrGroups 5 } ::= { mplsLsrGroups 5 }
mplsHCInterfacePerfGroup OBJECT-GROUP
OBJECTS { mplsInterfaceInHCOctets, mplsInterfaceOutHCOctets }
STATUS current
DESCRIPTION
"Collection of objects providing performance
information specific to high-speed interfaces for
which the objects mplsInterfaceInOctets and
mplsInterfaceOutOctets wrap-around too quickly."
::= { mplsLsrGroups 6 }
mplsHCInSegmentPerfGroup OBJECT-GROUP mplsHCInSegmentPerfGroup OBJECT-GROUP
OBJECTS { mplsInSegmentHCOctets } OBJECTS { mplsInSegmentHCOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) providing performance information specific "Object(s) providing performance information
to out-segments for which the object specific to out-segments for which the object
mplsInterfaceInOctets wraps around too quickly." mplsInterfaceInOctets wraps around too quickly."
::= { mplsLsrGroups 7 } ::= { mplsLsrGroups 6 }
mplsHCOutSegmentPerfGroup OBJECT-GROUP mplsHCOutSegmentPerfGroup OBJECT-GROUP
OBJECTS { mplsOutSegmentHCOctets } OBJECTS { mplsOutSegmentHCOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) providing performance information specific "Object(s) providing performance information
to out-segments for which the object specific to out-segments for which the object
mplsInterfaceOutOctets wraps around too quickly." mplsInterfaceOutOctets wraps around too
::= { mplsLsrGroups 8 } quickly."
::= { mplsLsrGroups 7 }
mplsTSpecGroup OBJECT-GROUP mplsTSpecGroup OBJECT-GROUP
OBJECTS { mplsTSpecIndex, mplsTSpecIfIndex, mplsTSpecDirection, OBJECTS { mplsTSpecIndex, mplsTSpecDirection,
mplsTSpecMaxRate, mplsTSpecMeanRate, mplsTSpecMaxRate, mplsTSpecMeanRate,
mplsTSpecMaxBurstSize, mplsTSpecRowStatus } mplsTSpecMaxBurstSize, mplsTSpecRowStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) required for supporting int-serv style "Object(s) required for supporting Int-Serv style
resource reservation." resource reservation."
::= { mplsLsrGroups 9 } ::= { mplsLsrGroups 8 }
mplsXCIsPersistentGroup OBJECT-GROUP mplsXCIsPersistentGroup OBJECT-GROUP
OBJECTS { mplsXCIsPersistent } OBJECTS { mplsXCIsPersistent }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to support persistent cross- "Objects needed to support persistent cross-
connects." connects."
::= { mplsLsrGroups 10 } ::= { mplsLsrGroups 9 }
mplsXCIsNotPersistentGroup OBJECT-GROUP mplsXCIsNotPersistentGroup OBJECT-GROUP
OBJECTS { mplsXCIsPersistent } OBJECTS { mplsXCIsPersistent }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to support non-persistent cross- "Objects needed to support non-persistent cross-
connects." connects."
::= { mplsLsrGroups 11 } ::= { mplsLsrGroups 10 }
mplsLsrNotificationGroup NOTIFICATION-GROUP mplsLsrNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsInterfaceUp, mplsInterfaceDown, NOTIFICATIONS { mplsInterfaceUp, mplsInterfaceDown,
mplsInSegmentUp, mplsInSegmentDown, mplsInSegmentUp, mplsInSegmentDown,
mplsOutSegmentUp, mplsOutSegmentDown, mplsOutSegmentUp, mplsOutSegmentDown,
mplsXCUp, mplsXCDown } mplsXCUp, mplsXCDown }
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."
::= { mplsLsrGroups 12 } ::= { mplsLsrGroups 11 }
-- End of MPLS-LSR-MIB -- End of MPLS-LSR-MIB
END END
9. Security Considerations 10. Security Considerations
It is clear that this MIB is potentially useful for monitoring of
MPLS LSRs. This MIB can also be used for configuration of certain
objects, and anything that can be configured can be incorrectly
configured, with potentially disastrous results.
The MIB specified in this document does not raise any security At this writing, no security holes have been identified beyond
issues other than those present in the MPLS architecture those that SNMP Security [SNMPArch] is itself intended to address.
[MPLSArch] or those imposed by SNMP itself. These relate to primarily controlled access to sensitive
information and the ability to configure a device - or which might
result from operator error, which is beyond the scope of any
security architecture.
10. Acknowledgments There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect
on network operations. The use of SNMP Version 3 is recommended
over prior versions, for configuration control, as its security
model is improved.
We wish to thank Ron Bonica, Eric Gray, and Dan Tappan for their SNMPv1 or SNMPv2 are by themselves not a secure environment. Even
comments on this draft. if the network itself is secure (for example by using IPSec
[IPSEC]), there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the
objects in this MIB. It is recommended that the implementers
consider the security features as provided by the SNMPv3
framework. Specifically, the use of the User-based Security Model
[SNMPv3USM] and the View- based Access Control [SNMPv3VACM] is
recommended. It is then a customer/user responsibility to ensure
that the SNMP entity giving access to an instance of this MIB is
properly configured to give access to the objects only to those
principals (users) that have legitimate rights to indeed GET or
SET (change/create/delete) them.
11. References There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in
that they represent a customer's interface to the MPLS network.
Allowing uncontrolled access to these objects could result in
malicious and unwanted disruptions of network traffic or incorrect
configurations for these customers. There are no objects that are
particularly sensitive in their own right, such as passwords or
monetary amounts.
11. Acknowledgments
We wish to thank Ron Bonica of MCI, Dan Tappan of Cisco Systems,
Bala Rajagopalan of NEC CCRL, and Eric Gray and Vasanthi
Thirumalai of Lucent Technogies for their comments and input on
this document.
12. References
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", "Multiprotocol Label Switching Architecture",
Internet Draft <draft-ietf-mpls-arch-05.txt>, Internet Draft <draft-ietf-mpls-arch-06.txt>,
February 1999. August 1999.
[MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A.,
Swallow, G., and A. Viswanathan, "A Framework for Swallow, G., and A. Viswanathan, "A Framework for
Multiprotocol Label Switching", Internet Draft Multiprotocol Label Switching", Internet Draft
<draft-ietf-mpls-framework-02.txt>, November 1997. <draft-ietf-mpls-framework-05.txt>, September 1999.
[TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T.,
"MPLS Traffic Engineering Management Information
Base Using SMIv2", Internet Draft <draft-ietf-mpls-
te-mib-02.txt>, February 2000.
[LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, " [LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, "
Definitions of Managed Objects for the Definitions of Managed Objects for the
Multiprotocol Label Switching, Label Distribution Multiprotocol Label Switching, Label Distribution
Protocol (LDP)", Internet Draft <draft-ietf-mpls- Protocol (LDP)", Internet Draft <draft-ietf-mpls-
ldp-mib-00.txt>, August 1998. ldp-mib-04.txt>, February 2000.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
Federokow, G., Li, T., and A. Conta, "MPLS Label Federokow, G., Li, T., and A. Conta, "MPLS Label
Stack Encoding", Internet Draft <draft-ietf-mpls- Stack Encoding", Internet Draft <draft-ietf-mpls-
label-encaps-04.txt>, April 1999. label-encaps-07.txt>, September 1999.
[RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T., [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T.,
Swallow, G., and V. Srinivasan, "Extensions to RSVP Swallow, G., and V. Srinivasan, "Extensions to RSVP
for LSP Tunnels", Internet Draft <draft-mpls-rsvp- for LSP Tunnels", Internet Draft <draft-mpls-rsvp-
lsp-tunnel-02.txt>, March 1999. lsp-tunnel-04.txt>, September 1999.
[CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup
using LDP", Internet Draft <draft-ietf-mpls-cr-ldp- using LDP", Internet Draft <draft-ietf-mpls-cr-ldp-
01.txt>, February 1999. 03.txt>, September 1999.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also: RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi- http://www.isi.edu/in-notes/iana/assignments/smi-
numbers numbers
[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Architecture for Describing SNMP Management
Frameworks", RFC 2271, January 1998. Frameworks", RFC 2271, January 1998.
skipping to change at page 46, line 23 skipping to change at page 53, line 52
the Simple Network Management Protocol (SNMPv2)", the Simple Network Management Protocol (SNMPv2)",
RFC 1906, January 1996. RFC 1906, January 1996.
[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2272, Network Management Protocol (SNMP)", RFC 2272,
January 1998. January 1998.
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2274, January Management Protocol (SNMPv3)", RFC 2574, April
1998. 1999.
[SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for Version 2 of Waldbusser, "Protocol Operations for Version 2 of
the Simple Network Management Protocol (SNMPv2)", the Simple Network Management Protocol (SNMPv2)",
RFC 1905, January 1996. RFC 1905, January 1996.
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2273, January 1998 Applications", RFC 2273, January 1998.
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
based Access Control Model (VACM) for the Simple based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)", RFC 2275, Network Management Protocol (SNMP)", RFC 2575,
January 1998 April 1999.
12. Authors's Addresses [IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces
Group MIB using SMIv2", RFC 2233, Nov. 1997
13. Authors' Addresses
Cheenu Srinivasan Cheenu Srinivasan
Tachion Network Technologies Tachion Networks, Inc.
2 Meridian Road 2 Meridian Road
Eatontown, NJ 07724 Eatontown, NJ 07724
Phone: +1-732-542-7750 x234 Phone: +1-732-542-7750 x234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Lucent Technologies Force10 Networks
4D537, 101 Crawfords Corner Road 1440 McCarthy Blvd
Holmdel, NJ 07733 Milpitas, CA 95035
Phone: +1-408-571-3516
Email: arun@force10networks.com
Phone: +1-732-332-5163 Thomas D. Nadeau
Email: arunv@lucent.com Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
14. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which case
the procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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