draft-ietf-mpls-lsr-mib-02.txt   draft-ietf-mpls-lsr-mib-03.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Tachion Networks, Inc. Internet Draft Tachion Networks, Inc.
Expires: September 2000 Expires: October 2000
Arun Viswanathan Arun Viswanathan
Force10 Networks Force10 Networks, Inc.
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. 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-02.txt draft-ietf-mpls-lsr-mib-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that 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 2, line 9 skipping to change at page 1, line 37
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be 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 Table of Contents
1.Abstract..............................................2
2. Introduction.........................................2
3. Terminology..........................................2
4. The SNMP Management Framework........................3
4.1. Object Definitions.................................4
5. Feature Checklist....................................4
6. Outline..............................................4
6.1. Summary of LSR MIB.................................5
7. Brief Description of MIB Objects.....................5
7.1. mplsInterfaceConfTable.............................5
7.2. mplsInterfacePerfTable.............................5
7.3. mplsInSegmentTable.................................5
7.4. mplsInSegmentPerfTable.............................7
7.5. mplsOutSegmentTable................................6
7.6. mplsOutSegmentPerfTable............................6
7.7. mplsXCTable........................................7
7.8. mplsLabelStackTable................................7
7.9. mplsTrafficParamTable..............................7
8. Example of LSP Setup.................................7
9. Application of the Interface Group to MPLS...........9
9.1. Support of the MPLS Layer by ifTable...............9
10. The Use of RowPointer..............................12
11. MPLS Label Switch Router MIB Definitions...........12
12. Security Considerations............................52
13. Acknowledgments....................................53
14. References.........................................54
15. Authors' Addresses.................................56
16. Full Copyright Statement...........................58
1. 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 a 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).
1. Introduction 2. 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 a 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 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119, reference [BCP14].
3. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the
MPLS architecture [MPLSArch]. A label switched path (LSP) is MPLS architecture [MPLSArch]. A label switched path (LSP) is
modeled as a connection consisting of one or more incoming modeled as a connection consisting of one or more incoming
segments (in-segments) and/or one or more outgoing segments (out- segments (in-segments) and/or one or more outgoing segments (out-
segments) at a label switch router (LSR). The association or segments) at a label switch router (LSR). The association or
interconnection of the in-segments and out-segments is interconnection of the in-segments and out-segments is
accomplished by using a cross-connect. We use the terminology accomplished by using a cross-connect. We use the terminology
"connection" and "LSP" interchangeably where the meaning is clear "connection" and "LSP" interchangeably where the meaning is clear
from the context. from the context.
3. The SNMP Management Framework 4. 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
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215
skipping to change at page 4, line 30 skipping to change at page 4, line 7
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 appropriate conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions information in SMIv2 will be converted into textual descriptions
in SMIv1 during the translation process. However, this loss of in SMIv1 during the translation process. However, this loss of
machine-readable information is not considered to change the machine-readable information is not considered to change the
semantics of the MIB. semantics of the MIB.
3.1. Object Definitions 4.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 5. Feature Checklist
The MPLS label switch router MIB (LSR-MIB) is designed to satisfy The MPLS label switch router MIB (LSR-MIB) is designed to satisfy
the following requirements and constraints: the following requirements and constraints:
- The MIB should be able to support both manually configured LSPs - The MIB supports both manually configured LSPs as well as those
as well as those configured via LDP and/or RSVP signaling. configured via any MPLS signaling protocol.
- The MIB must support the enabling and disabling of MPLS - The MIB supports the enabling and disabling of MPLS capability
capability on MPLS capable interfaces of an LSR. on MPLS capable interfaces of an LSR.
- The MIB should allow resource sharing between two or more LSPs. - The MIB allows 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 are supported.
supported.
- MPLS packets must be forwarded solely based on an incoming top - MPLS packets can 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 is provided for next-hop resolution when the outgoing
outgoing interface is a shared media interface. In the point- interface is a shared media interface. In the point-to-
to-multipoint case, each outgoing segment can reside on a 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 supports 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 outgoing packets must - For multipoint-to-point connections all outgoing packets can
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 can 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 can 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.
- All the members of a point-to-multipoint connection share the - All the members of a point-to-multipoint connection can share
resources allocated for the ingress segments. the resources allocated for the ingress segments.
- The MIB must provide cross-connect capability to "pop" an
incoming label and forward the packet with the remainder of
the label stack unchanged and without pushing any labels ("pop-
and-go") [LblStk].
- It must be possible to assign or re-map the Class of Service - The MIB provides cross-connect capability to "pop" an incoming
(COS) bits [LblStk] on the outgoing label. In the multipoint- label and forward the packet with the remainder of the label
to-point case, each in-segment can have a different outgoing stack unchanged and without pushing any labels ("pop-and-go")
COS value. In the point-to-multipoint case, each out-segment [LblStk].
can have a different outgoing COS value.
- It should be possible to support persistent as well as non- - The MIB supports persistent as well as non-persistent LSPs.
persistent LSPs.
- Performance counters must be provided for in-segments and out- - Performance counters are 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 6. 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-segments and out-segments. - Configuring in-segments and out-segments.
- Setting up the cross-connect table to associate segments and/or - Setting up the cross-connect table to associate segments 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 6.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:
- The interface configuration table (mplsInterfaceConfTable), - The interface configuration table (mplsInterfaceConfTable),
which is used for enabling the MPLS protocol on MPLS-capable which is used for enabling the MPLS protocol on MPLS-capable
interfaces. interfaces.
- The in-segment (mplsInSegmentTable) and out-segment - The in-segment (mplsInSegmentTable) and out-segment
(mplsOutSegmentTable) tables, which are used for configuring (mplsOutSegmentTable) tables, which are used for configuring
LSP segments at an LSR. LSP segments at an LSR.
- The cross-connect table (mplsXCTable), which is used to - The cross-connect table (mplsXCTable), which is used to
associate in and out segments together, in order to form a associate in and out segments together, in order to form a
cross-connect. cross-connect.
- The label stack table (mplsLabelStackTable), which is used for - The label stack table (mplsLabelStackTable), which is used for
specifying label stack operations. specifying label stack operations.
- The TSpec table (mplsTSpecTable), which is used for specifying - The Traffic Parameter table (mplsTrafficParamTable), which is
LSP-related traffic parameters. used for specifying 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 7. Brief Description of MIB Objects
Sections 6.1-6.3 describe objects pertaining to MPLS capable Sections 7.1-7.2 describe objects pertaining to MPLS capable
interfaces of an LSR. The objects described in Sections 6.4-6.9, interfaces of an LSR. The objects described in Sections 7.3-7.8,
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.10 describes objects for specifying (NHLFE) tables. Section 7.9 describes objects for specifying
traffic parameters for in and out segments. traffic parameters for in and out segments. It is appropriate to
note that the in-segment, out-segment, and cross-connect tables
were modeled after similar tables found in [ATOMMIB].
6.1. mplsInterfaceConfTable 7.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.
interface label ranges. The administrator can specify the desired
MPLS status (enable/up, disable/down, testing) of an interface by
writing the object mplsInterfaceAdminStatus. The actual status is
indicated by the object mplsInterfaceOperStatus.
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 7.2. 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.4. mplsInSegmentTable 7.3. 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.5. mplsInSegmentPerfTable The administrative and operational status objects for this table
are used to control packet transmission on this segment. If
either the administrative and operational status objects for this
table are set to 'down', this implies that packets will not be
forwarded. Likewise, if the values are set to 'up' this implies
that packets are forwarded. These values are particularly useful
in cases where multi-point connections utilize a single cross-
connect and the administrator wishes to disable some, but not all
of the streams. In these cases, the administrator may set the
administrative status object to 'down' on some of the in-segments.
7.4. 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.6. mplsOutSegmentTable 7.5. 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.7. mplsOutSegmentPerfTable The administrative and operational status objects for this table
are used to control packet transmission on this segment. If
either the administrative and operational status objects are set
to 'down', this implies that packets will not be forwarded.
Likewise, if the values are set to 'up' this implies that packets
are forwarded. These values are particularly useful in cases
where multicast connections utilize a single cross-connect and the
administrator wishes to disable some, but not all of the streams.
In these cases, the administrator may set the administrative
status object to 'down' on some of the out-segments.
7.6. 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.8. mplsXCTable 7.7. mplsXCTable
The mplsXCTable specifies information for associating segments The mplsXCTable specifies information for associating segments
together in order to instruct the LSR to switch between the together in order to instruct the LSR to switch between the
specified segments. It supports point-to-point, point-to-multi- specified segments. It supports point-to-point, point-to-multi-
point and multi-point-to-point connections. point and multi-point-to-point connections.
6.9. mplsLabelStackTable The administrative and operational status objects for this table
imply control of packet forwarding to and from a XCEntry. When
the administrative and operational status objects are set to
'down' for example, this implies that the specified XCEntry will
not forward packets. Likewise, when either is set to 'up' this
implies that packets will be forwarded.
7.8. mplsLabelStackTable
The mplsLabelStackTable specifies the label stack to be pushed The mplsLabelStackTable specifies the label stack to be pushed
onto a packet, beneath the top label. Entries to this table are onto a packet, beneath the top label. Entries to this table are
referred to from mplsXCTable. referred to from mplsXCTable.
6.10. mplsTSpecTable 7.9. mplsTrafficParamTable
The mplsTSpecTable contains objects for specifying the traffic The mplsTrafficParamTable contains objects for specifying the
parameters of in-segments and out-segments. Entries in this table traffic parameters of in-segments and out-segments. Entries in
are referred to from mplsInSegmentTable and mplsOutSegmentTable. this table are referred to from mplsInSegmentTable and
mplsOutSegmentTable.
7. Example of LSP Setup 8. Example of LSP Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in Section 8 to set up an LSP. While this objects described in section 11. to set up an LSP. While this
example is not meant to illustrate every nuance of the MIB, it is example is not meant to illustrate every nuance of the MIB, it is
intended as an aid to understanding some of the key concepts. It intended as an aid to understanding some of the key concepts. It
is meant to be read after going through the MIB itself. is meant to be read after going through the MIB itself.
Suppose that one would like to manually create a best-effort, Suppose that one would like to manually create a best-effort,
unidirectional LSP. Assume that the LSP enters the LSR via MPLS unidirectional LSP. Assume that the LSP enters the LSR via MPLS
interface A with ifIndex 12 and exits the LSR via MPLS interface B 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 with ifIndex 13. Let us assume that we do not wish to have a
stack beneath the top label on the outgoing labeled packets. The label stack beneath the top label on the outgoing labeled packets.
following example illustrates which rows and corresponding objects The following example illustrates which rows and corresponding
might be created to accomplish this. objects might be created to accomplish this.
First, the TSpec entries must be set-up for both segments. First, the traffic parameter entries must be set-up for both
segments.
In mplsTSpecTable for the incoming direction: In mplsTrafficParamTable for the incoming direction:
{ {
mplsTSpecIndex = 5 mplsTrafficParamIndex = 5
mplsTSpecMaxRate = 100000, mplsTrafficParamMaxRate = 100000,
mplsTSpecMeanRate = 100000, mplsTrafficParamMeanRate = 100000,
mplsTSpecMaxBurstSize = 2000, mplsTrafficParamMaxBurstSize = 2000,
mplsTSpecRowStatus = createAndGo(4) mplsTrafficParamRowStatus = createAndGo(4)
} }
In mplsTSpecTable for the outgoing direction: In mplsTrafficParamTable for the outgoing direction:
{ {
mplsTSpecIndex = 6 mplsTrafficParamIndex = 6
mplsTSpecMaxRate = 100000, mplsTrafficParamMaxRate = 100000,
mplsTSpecMeanRate = 100000, mplsTrafficParamMeanRate = 100000,
mplsTSpecMaxBurstSize = 2000, mplsTrafficParamMaxBurstSize = 2000,
mplsTSpecRowStatus = createAndGo(4) mplsTrafficParamRowStatus = createAndGo(4)
} }
Note that if we were setting up a bi-directional LSP, the segments Note that if we were setting up a bi-directional LSP, the segments
in the reverse direction can share the TSpec entries (and hence in the reverse direction can share the traffic parameter entries
resources) with the segments in the forward direction. (and hence resources) with the segments in the forward direction.
We must next create the appropriate in-segment and out-segment We must next create the appropriate in-segment and out-segment
entries with suitable traffic parameters by pointing to the entries with suitable traffic parameters by pointing to the
appropriate TSpec entries that we have just created. appropriate traffic parameter entries that we have just created.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIfIndex = 12, -- incoming interface mplsInSegmentIfIndex = 12, -- incoming interface
mplsInSegmentLabel = 21, -- incoming label mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentTSpecIndex = 5, mplsInSegmentTrafficParamPtr = mplsTrafficParamIndex.5,
mplsInSegmentRowStatus = createAndGo(4) mplsInSegmentRowStatus = createAndGo(4)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 1, mplsOutSegmentIndex = 1,
mplsOutSegmentIfIndex = 13, -- outgoing interface mplsOutSegmentIfIndex = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label mplsOutSegmentTopLabel = 22, -- outgoing label
mplsOutSegmentTSpecIndex = 6, mplsOutSegmentTrafficParamPtr = mplsTrafficParamIndex.6,
mplsOutSegmentRowStatus = createAndGo(4) mplsOutSegmentRowStatus = createAndGo(4)
} }
Next, a cross-connect entry is created thereby associating the Next, a cross-connect entry is created thereby associating the
newly created segments together. newly created segments together.
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 2, mplsXCIndex = 2,
mplsXCLspId = "1.2.3.4-2", mplsXCLspId = 'c021041502'H, -- 192.33.4.21.2
mplsInSegmentIfIndex = 12, mplsInSegmentIfIndex = 12,
mplsInSegmentLabel = 21, mplsInSegmentLabel = 21,
mplsOutSegmentIndex = 1, mplsOutSegmentIndex = 1,
mplsXCCOS = 0,
mplsXCIsPersistent = false (1), mplsXCIsPersistent = false (1),
mplsLabelStackIndex = 0, -- only a single outgoing label mplsLabelStackIndex = 0, -- only a single
-- outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex
objects will automatically be populated with the value 2 when objects will automatically be populated with the value 2 when
these segments are referred to from the corresponding cross- these segments are referred to from the corresponding cross-
connect entry. connect entry.
8. Application of the Interface Group to MPLS 9. Application of the Interface Group to MPLS
The Interfaces Group of MIB II defines generic managed objects for The Interfaces Group of MIB II defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing MPLS interfaces. extensions to the Interfaces Group for managing MPLS interfaces.
This memo assumes the interpretation of the Interfaces Group to be This memo assumes the interpretation of the Interfaces Group to be
in accordance with [IFMIB] which states that the interfaces table in accordance with [IFMIB] which states that the interfaces table
(ifTable) contains information on the managed resource's (ifTable) contains information on the managed resource's
interfaces and that each sub-layer below the internetwork layer of interfaces and that each sub-layer below the internetwork layer of
a network interface is considered an interface. Thus, the MPLS a network interface is considered an interface. Thus, the MPLS
layer interface is represented as an entry in the ifTable. This interface is represented as an entry in the ifTable. The inter-
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 relation of entries in the ifTable is defined by Interfaces Stack
Group defined in [IFMIB]. Group defined in [IFMIB].
8.1. Support of the MPLS Layer by ifTable When using MPLS interfaces, the interface stack table might appear
as follows:
+----------------------------------------+
| MPLS-interface ifType = mpls(166) +
+----------------------------------------+
| Underlying Layer... +
+----------------------------------------+
In the above diagram, "Underlying Layer..." refers to the ifIndex
of any interface type, which has been defined for MPLS
interworking. Examples include ATM, Frame Relay, Ethernet, etc.
9.1. Support of the MPLS Layer by ifTable
Some specific interpretations of ifTable for the MPLS layer Some specific interpretations of ifTable for the MPLS layer
follow. follow.
Object Use for the MPLS layer Object Use for the MPLS layer
ifIndex Each MPLS interface is represented by an ifEntry. ifIndex Each MPLS interface is represented by an ifEntry.
ifDescr Description of the MPLS interface. ifDescr Description of the MPLS interface.
ifType The value that is allocated for MPLS is 166. ifType The value that is allocated for MPLS is 166.
ifSpeed The total bandwidth in bits per second for use by ifSpeed The total bandwidth in bits per second for use by
the MPLS layer. the MPLS layer.
ifPhysAddress Unused. ifPhysAddress Unused.
skipping to change at page 15, line 15 skipping to change at page 11, line 18
ifDescr Description of the MPLS interface. ifDescr Description of the MPLS interface.
ifType The value that is allocated for MPLS is 166. ifType The value that is allocated for MPLS is 166.
ifSpeed The total bandwidth in bits per second for use by ifSpeed The total bandwidth in bits per second for use by
the MPLS layer. the MPLS layer.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus See [IFMIB]. ifAdminStatus This variable indicates the administrator's intent
as to whether MPLS should be enabled, disabled, or
running in some diagnostic testing mode on this
interface. Also see [IFMIB].
ifOperStatus Assumes the value down(2) if the MPLS layer is ifOperStatus This value reflects the actual or operational
down. status of MPLS on this interface.
ifLastChange See [IFMIB]. ifLastChange See [IFMIB].
ifInOctets The number of received octets over the interface, ifInOctets The number of received octets over the interface,
i.e., the number of received, octets received as i.e., the number of received, octets received as
labeled packets. labeled packets.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the
interface, i.e., the number of octets transmitted interface, i.e., the number of octets transmitted
as labeled packets. as labeled packets.
skipping to change at page 16, line 29 skipping to change at page 12, line 16
ifHCInOctets The 64-bit version of ifInOctets; supported if ifHCInOctets The 64-bit version of ifInOctets; supported if
required by the compliance statements in [IFMIB]. required by the compliance statements in [IFMIB].
ifHCOutOctets The 64-bit version of ifOutOctets; supported if ifHCOutOctets The 64-bit version of ifOutOctets; supported if
required by the compliance statements in [IFMIB]. required by the compliance statements in [IFMIB].
ifAlias The non-volatile 'alias' name for the interface as ifAlias The non-volatile 'alias' name for the interface as
specified by a network manager. specified by a network manager.
9. MPLS Label Switch Router MIB Definitions ifCounterDiscontinuityTime
See [IFMIB].
10. The Use of RowPointer
RowPointer is a textual convention used to identify a conceptual
row in an SNMP Table by pointing to one of its objects. In this
MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable
for the following purposes. First, it indicates a particular
traffic parameter table. An example of such a table is
mplsTrafficParamTable. Second, it is used to indicate a specific
instance of a traffic parameter entry that is associated with a
given in-segment or out-segment entry. In the in-segment and out-
segment tables, the trafficParamPtr SHOULD point to the first
column of the appropriate conceptual row.
11. 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, Unsigned32, Counter32, experimental, Integer32, Counter32, Unsigned32,
Counter64, Gauge32, IpAddress Counter64, Gauge32, BITS
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, StorageType,
RowPointer, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex, InterfaceIndex, InterfaceIndexOrZero
FROM IF-MIB; InterfaceIndex, InterfaceIndexOrZero
FROM IF-MIB
AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
InetAddressIPv4, InetAddressIPv6, InetAddressType
FROM INET-ADDRESS-MIB;
mplsLsrMIB MODULE-IDENTITY mplsLsrMIB MODULE-IDENTITY
LAST-UPDATED "200002161200Z" -- 16 February 2000 12:00:00 EST LAST-UPDATED "200004211200Z" -- 21 April 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 Networks, Inc. Postal: Tachion Networks, Inc.
2 Meridian Road Monmouth Park Corporate Center I
Eatontown, NJ 0772 Building C, 185 Monmouth Parkway
Tel: +1 732 542 7750 x234 West Long Branch, NJ 07764
Tel: +1-732-542-7750 x1234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Postal: Force10 Networks Postal: Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Tel: +1-408-571-3516 Tel: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
skipping to change at page 18, line 17 skipping to change at page 13, line 46
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for the "This MIB contains managed object definitions for the
Multiprotocol Label Switching (MPLS) Router as Multiprotocol Label Switching (MPLS) Router as
defined in: Rosen, E., Viswanathan, A., and R. defined in: Rosen, E., Viswanathan, A., and R.
Callon, Multiprotocol Label Switching Architecture, Callon, Multiprotocol Label Switching Architecture,
Internet Draft <draft-ietf-mpls-arch-06.txt>, Internet Draft <draft-ietf-mpls-arch-06.txt>,
February 2000." February 2000."
-- Revision history. -- Revision history.
REVISION REVISION
"199907161200Z" -- 16 July 1999 12:00:00 EST "199906161200Z" -- 16 June 1999 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial draft version."
REVISION REVISION
"200002161200Z" -- 16 February 2000 12:00:00 EST "200002161200Z" -- 16 February 2000 12:00:00 EST
DESCRIPTION DESCRIPTION
"Second draft version." "Second draft version."
REVISION REVISION
"200003061200Z" -- 6 March 2000 12:00:00 EST "200003061200Z" -- 6 March 2000 12:00:00 EST
DESCRIPTION DESCRIPTION
"Third draft version." "Third draft version."
REVISION
"200004211200Z" -- 21 April 2000 12:00:00 EST
DESCRIPTION
"Fourth draft version. Made corrections from WG Last
Call comments."
::= { experimental 96 } ::= { experimental 96 }
-- Textual Conventions. -- Textual Conventions.
MplsLSPID ::= TEXTUAL-CONVENTION MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier that is assigned to each LSP and is "An identifier that is assigned to each LSP and is
used to uniquely identify it. This is assigned at used to uniquely identify it. This is assigned at
the head end of the LSP and can be used by all LSRs the head end of the LSP and can be used by all LSRs
to identify this LSP. This value is piggybacked by to identify this LSP. This value is piggybacked by
the signaling protocol when this LSP is signaled the signaling protocol when this LSP is signaled
within the network. This identifier can then be used within the network. This identifier can then be
at each LSR to identify which labels are being used at each LSR to identify which labels are being
swapped to other labels for this LSP. For IPv4 swapped to other labels for this LSP. For IPv4
addresses this results in a 6-octet long cookie." addresses this results in a 6-octet long cookie."
SYNTAX OCTET STRING (SIZE (0..63)) SYNTAX OCTET STRING (SIZE (0..31))
MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An address family. These values are defined in RFC
1700 and are maintained by The IANA. All values may
not be relevant in all contexts when used in this
MIB, but are included for completeness."
REFERENCE
"RFC 1700 - Assigned Numbers, Reynolds, J. and J.
Postel, Oct. 1994"
SYNTAX INTEGER {
other(0),
ipv4(1),
ipv6(2),
nsap(3),
hdlc(4),
bbn1822(5),
ieee802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appleTalk(12),
decnetIV(13),
banyanVines(14),
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 "This value represents an MPLS label. Note that the
a label field are interpreted in an interface-type contents of a label field are interpreted in an
specific fashion. For example, the 20-bit wide interface-type specific fashion. For example, the
label carried in the MPLS shim header is contained 20-bit wide label carried in the MPLS shim header is
in bits 0-19 and bits 20-31 must be zero. The frame contained in bits 0-19 and bits 20-31 must be zero.
relay label can be either 10, 17 or 23 bits wide The frame relay label can be either 10 or 23 bits
depending on the size of the DLCI field and bits 10- wide depending on the size of the DLCI field and
31, 17-31 or 23-31 must be zero, respectively. For bits 10-31, or 23-31 must be zero, respectively.
an ATM interface, bits 0-15 must be interpreted as For an ATM interface, bits 0-15 must be interpreted
the VCI, bits 16-23 as the VPI and bits 24-31 must as the VCI, bits 16-23 as the VPI and bits 24-31
be zero. Note that the permissible label values are must be zero. Note that the permissible label
also a function of the interface type. For example, values are also a function of the interface type.
the value 3 has special semantics in the control For example, the value 3 has special semantics in
plane for an MPLS shim header label and is not a the control plane for an MPLS shim header label and
valid label value in the data path." is not a 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-07.txt, March 2000. 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. Conta et al, draft-ietf-mpls-fr-03.txt, Nov.
1998." 1998.
SYNTAX Integer32 3. MPLS using LDP and ATM VC switching, Davie et al,
draft-ietf-mpls-atm-02.txt, April 1999."
Ipv6Address ::= TEXTUAL-CONVENTION SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"IPv6 address."
SYNTAX OCTET STRING (SIZE(16))
MplsBitRate ::= TEXTUAL-CONVENTION MplsBitRate ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An estimate of bandwidth in units of 1,000 bits per "An estimate of bandwidth in units of 1,000 bits per
second. If this object reports a value of 'n' then second. If this object reports a value of 'n' then
the rate of the object is somewhere in the range of the rate of the object is somewhere in the range of
'n-500' to 'n+499'. For objects which do not vary in 'n-500' to 'n+499'. For objects which do not vary in
bitrate, or for those where no accurate estimation bitrate, or for those where no accurate estimation
skipping to change at page 22, line 10 skipping to change at page 15, line 41
may send back-to-back without concern for policing." may send back-to-back without concern for policing."
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MplsBufferSize ::= TEXTUAL-CONVENTION MplsBufferSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Size of buffer in octets of MPLS data." "Size of buffer in octets of MPLS data."
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MplsObjectOwner ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The entity which owns the object in question."
SYNTAX INTEGER {
other(1),
snmp(2),
ldp(3),
rsvp(4),
policyAgent(5),
unknown (6)
}
-- Top level components of this MIB. -- Top level components of this MIB.
-- 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.
mplsInterfaceConfTable OBJECT-TYPE mplsInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInterfaceConfEntry SYNTAX SEQUENCE OF MplsInterfaceConfEntry
skipping to change at page 23, line 6 skipping to change at page 16, line 31
"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. When the every interface capable of supporting MPLS. The
global label space is in use, an entry with index 0 entry with index 0 represents the per-platform label
is created in this table. This entry contains space and contains parameters that apply to all
parameters that apply to all interfaces that interfaces that participate in the per-platform
participate in the global label space. Other label space. Other entries defined in this table
interfaces defined in this table indicate whether or represent additional MPLS interfaces that may
not they participate in the global label space by participate in either the per-platform or per-
setting the mplsInterfaceIsGlobalLabelSpace variable interface label spaces, or both. Additional
to true. Note that interfaces which have specified information about label space participation of an
that they participate in an interface-specific label interface is provided in the description clause of
space may also participate in the global label space mplsInterfaceLabelParticipationType."
simultaneously. In this case, the interface with
index 0 should referenced for global label space
parameters such as the label ranges. It may be
useful to configure additional interfaces in this
table for interfaces which participate in the global
label space so that parameters such as bandwidth and
buffer resources maybe specified individually.
Please note that either
mplsInterfaceIsGlobalLabelSpace or
mplsInterfaceIsLocalLabelSpace MUST be set to true
on every interface configured in this table."
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 MplsBitRate, mplsInterfaceTotalBandwidth MplsBitRate,
mplsInterfaceAvailableBandwidth MplsBitRate, mplsInterfaceAvailableBandwidth MplsBitRate,
mplsInterfaceTotalBuffer MplsBufferSize, mplsInterfaceTotalBuffer MplsBufferSize,
mplsInterfaceAvailableBuffer MplsBufferSize, mplsInterfaceAvailableBuffer MplsBufferSize,
mplsInterfaceIsGlobalLabelSpace TruthValue, mplsInterfaceLabelParticipationType BITS,
mplsInterfaceIsLocalLabelSpace TruthValue, mplsInterfaceConfStorageType StorageType
mplsInterfaceAdminStatus INTEGER,
mplsInterfaceOperStatus INTEGER
} }
mplsInterfaceConfIndex OBJECT-TYPE mplsInterfaceConfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a unique index for an entry in the "This is a unique index for an entry in the
MplsInterfaceConfTable. A non-zero index for an MplsInterfaceConfTable. A non-zero index for an
entry indicates the ifIndex for the corresponding entry indicates the ifIndex for the corresponding
interface entry in of the MPLS-layer in the ifTable. interface entry in of the MPLS-layer in the ifTable.
Note that the global label space may apply to Note that the per-platform label space may apply to
several interfaces, and therefore the configuration several interfaces, and therefore the configuration
of the global label space interface parameters will of the per-platform label space interface parameters
apply to all of the interfaces that are will apply to all of the interfaces that are
participating in the global label space." participating in the per-platform label space."
REFERENCE REFERENCE
"RFC 2233 - The Interfaces Group MIB using SMIv2, "RFC 2233 - The Interfaces Group MIB using SMIv2,
McCloghrie, K., and F. Kastenholtz, Nov. 1997" McCloghrie, K., and F. Kastenholtz, Nov. 1997"
::= { 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
"This is the minimum value of an MPLS label that this "This is the minimum value of an MPLS label that this
LSR is willing to receive on this interface. Please LSR is willing to receive on this interface."
note that in the case that the
mplsInterfaceIsLocalLabelSpace is set to true, this
value indicates the value appropriate for the per-
interface label range. If the
mplsInterfaceIsGlobalLabelSpace is true, please
refer to the interface whose index is 0 for the
value which applies to the global label space."
::= { 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
"This is the maximum value of an MPLS label that this "This is the maximum value of an MPLS label that this
LSR is willing to receive on this interface. Please LSR is willing to receive on this interface."
note that in the case that the
mplsInterfaceIsLocalLabelSpace is set to true, this
value indicates the value appropriate for the per-
interface label range. If the
mplsInterfaceIsGlobalLabelSpace is true, please
refer to the interface whose index is 0 for the
value which applies to the global label space."
::= { 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
"This is the minimum value of an MPLS label that this "This is the minimum value of an MPLS label that this
LSR is willing to send on this interface. Please LSR is willing to send on this interface."
note that in the case that the
mplsInterfaceIsLocalLabelSpace is set to true, this
value indicates the value appropriate for the per-
interface label range. If the
mplsInterfaceIsGlobalLabelSpace is true, please
refer to the interface whose index is 0 for the
value which applies to the global label space."
::= { 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
"This is the maximum value of an MPLS label that this "This is the maximum value of an MPLS label that this
LSR is willing to send on this interface. Please LSR is willing to send on this interface."
note that in the case that the
mplsInterfaceIsLocalLabelSpace is set to true, this
value indicates the value appropriate for the per-
interface label range. If the
mplsInterfaceIsGlobalLabelSpace is true, please
refer to the interface whose index is 0 for the
value which applies to the global label space."
::= { mplsInterfaceConfEntry 5 } ::= { mplsInterfaceConfEntry 5 }
mplsInterfaceTotalBandwidth OBJECT-TYPE mplsInterfaceTotalBandwidth OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates the total amount of usable "This value indicates the total amount of usable
bandwidth on this interface and is specified in bandwidth on this interface and is specified in
kilobits per second (Kbps/sec). This variable is not kilobits per second (Kbps/sec). This variable is
applicable when applied to the interface with index not applicable when applied to the interface with
0." index 0."
::= { mplsInterfaceConfEntry 6 } ::= { mplsInterfaceConfEntry 6 }
mplsInterfaceAvailableBandwidth OBJECT-TYPE mplsInterfaceAvailableBandwidth OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates the total amount of available "This value indicates the total amount of available
bandwidth available on this interface and is bandwidth available on this interface and is
specified in kilobits per second (Kbps/sec). This specified in kilobits per second (Kbps/sec). This
skipping to change at page 28, line 4 skipping to change at page 18, line 47
variable is not applicable when applied to the variable is not applicable when applied to the
interface with index 0." interface with index 0."
::= { mplsInterfaceConfEntry 7 } ::= { mplsInterfaceConfEntry 7 }
mplsInterfaceTotalBuffer OBJECT-TYPE mplsInterfaceTotalBuffer OBJECT-TYPE
SYNTAX MplsBufferSize SYNTAX MplsBufferSize
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates the total amount of buffer "This value indicates the total amount of buffer
space allocated for this interface. This variable is space allocated for this interface. This variable
not applicable when applied to the interface with is not applicable when applied to the interface with
index 0." index 0."
::= { mplsInterfaceConfEntry 8 } ::= { mplsInterfaceConfEntry 8 }
mplsInterfaceAvailableBuffer OBJECT-TYPE mplsInterfaceAvailableBuffer OBJECT-TYPE
SYNTAX MplsBufferSize SYNTAX MplsBufferSize
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value reflects the total amount of buffer space "This value reflects the total amount of buffer space
available on this interface. This variable is not available on this interface. This variable is not
applicable when applied to the interface with index applicable when applied to the interface with index
0." 0."
::= { mplsInterfaceConfEntry 9 } ::= { mplsInterfaceConfEntry 9 }
mplsInterfaceIsGlobalLabelSpace OBJECT-TYPE mplsInterfaceLabelParticipationType OBJECT-TYPE
SYNTAX TruthValue SYNTAX BITS {
perPlatform (0),
perInterface (1)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether or not this interface "Either the perPlatform(0) or perInterface(1) bit
participates in the global label space." MUST be set. If the value of the
DEFVAL { false } mplsInterfaceConfIndex for this entry is zero, then
only the perPlatform(0) bit MUST be set and the
perInterface(1) bit is meaningless. If the
perInterface(1) bit is set then the value of
mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,
mplsInterfaceLabelMinOut, and
mplsInterfaceLabelMaxOut for this entry reflect the
label ranges for this interface. If only the
perPlatform(0) bit is set, then the value of
mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,
mplsInterfaceLabelMinOut, and
mplsInterfaceLabelMaxOut for this entry must be
identical to the instance of these objects with
index 0."
REFERENCE
"Multiprotocol Label Switching, Rosen et al, draft-ietf-mpls-
arch-06.txt, August 1999."
::= { mplsInterfaceConfEntry 10 } ::= { mplsInterfaceConfEntry 10 }
mplsInterfaceIsLocalLabelSpace OBJECT-TYPE mplsInterfaceConfStorageType OBJECT-TYPE
SYNTAX TruthValue SYNTAX StorageType
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether or not this interface "The storage type for this entry."
uses in the local or per-interface label space."
DEFVAL { false }
::= { mplsInterfaceConfEntry 11 } ::= { mplsInterfaceConfEntry 11 }
mplsInterfaceAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- enable MPLS on this interface
down(2), -- disable MPLS on this interface
testing(3) -- in some test mode
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the administrator's intent
as to whether MPLS should be enabled, disabled, or
running in some diagnostic testing mode on this
interface."
DEFVAL { down }
::= { mplsInterfaceConfEntry 12 }
mplsInterfaceOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3), -- in some test mode
unknown(4), -- status cannot be determined for some
-- reason
dormant(5),
notPresent(6), -- some component is missing
lowerLayerDown(7)
-- down due to the state of
-- lower layer interfaces
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value reflects the actual or operational status
of MPLS on this interface. The operStatus MUST NOT
enter the up state unless either
mplsInterfaceIsGlobalLabelSpace or
mplsInterfaceIsLocalLabelSpace is set to true."
::= { mplsInterfaceConfEntry 13 }
-- 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 MPLS performance information on "This table provides MPLS performance information on
skipping to change at page 34, line 9 skipping to change at page 22, line 22
mplsInterfaceOutFragments OBJECT-TYPE mplsInterfaceOutFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the number of outgoing MPLS "This variable indicates the number of outgoing MPLS
packets that required fragmentation before packets that required fragmentation before
transmission on this interface." transmission on this interface."
::= { mplsInterfacePerfEntry 8 } ::= { mplsInterfacePerfEntry 8 }
-- 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 collection of incoming "This table contains a collection of incoming
segments to an LSR." segments to an LSR."
::= { mplsLsrObjects 3 } ::= { mplsLsrObjects 3 }
skipping to change at page 34, line 33 skipping to change at page 22, line 44
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 an SNMP agent, or an MPLS signaling administrator or an SNMP agent, or an MPLS signaling
protocol. The creator of the entry is denoted by protocol. The creator of the entry is denoted by
mplsInSegmentOwner. An entry in this table is mplsInSegmentOwner. An entry in this table is
indexed by the ifIndex of the incoming interface and indexed by the ifIndex of the incoming interface and
the (top) label. Note that some segments are the (top) label."
associated with a tunnel, so the traffic parameters
of these rows are supported as read-only objects and
their modification can be done only via the tunnel
table, mplsTunnelTable."
REFERENCE
"MPLS Traffic Engineering Management Information Base
Using SMIv2, Srinivasan, Viswanathan and Nadeau,
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 InterfaceIndexOrZero,
mplsInSegmentLabel MplsLabel, mplsInSegmentLabel MplsLabel,
mplsInSegmentNPop Integer32, mplsInSegmentNPop Integer32,
mplsInSegmentAddrFamily MplsLsrIANAAddrFamily, mplsInSegmentAddrFamily AddressFamilyNumbers,
mplsInSegmentXCIndex Integer32, mplsInSegmentXCIndex Integer32,
mplsInSegmentTSpecIndex Integer32, mplsInSegmentOwner MplsObjectOwner,
mplsInSegmentOwner INTEGER, mplsInSegmentTrafficParamPtr RowPointer,
mplsInSegmentRowStatus RowStatus,
mplsInSegmentStorageType StorageType,
mplsInSegmentAdminStatus INTEGER, mplsInSegmentAdminStatus INTEGER,
mplsInSegmentOperStatus INTEGER, mplsInSegmentOperStatus INTEGER
mplsInSegmentRowStatus RowStatus
} }
mplsInSegmentIfIndex OBJECT-TYPE mplsInSegmentIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a unique index for an entry in the "This is a unique index for an entry in the
MplsInSegmentTable. This value represents the MplsInSegmentTable. This value represents the
interface index for the incoming MPLS interface. A interface index for the incoming MPLS interface. A
value of zero represents an incoming label from the value of zero represents an incoming label from the
per-platform label space. In this case, the per-platform label space. In this case, the
mplsInSegmentLabel is interpreted to be an MPLS-type mplsInSegmentLabel is interpreted to be an MPLS-type
label." label."
::= { mplsInSegmentEntry 1 } ::= { mplsInSegmentEntry 1 }
mplsInSegmentLabel OBJECT-TYPE mplsInSegmentLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The incoming label for this segment." "The incoming label for this segment."
::= { mplsInSegmentEntry 2 } ::= { mplsInSegmentEntry 2 }
mplsInSegmentNPop OBJECT-TYPE mplsInSegmentNPop OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
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 from packet. Normally only the top label is popped from
the packet and used for all switching decisions for the packet and used for all switching decisions for
that packet." that packet. Note that technologies which do not
support label popping should set this value to its
default value of 1."
DEFVAL { 1 } DEFVAL { 1 }
::= { mplsInSegmentEntry 3 } ::= { mplsInSegmentEntry 3 }
mplsInSegmentAddrFamily OBJECT-TYPE mplsInSegmentAddrFamily OBJECT-TYPE
SYNTAX MplsLsrIANAAddrFamily SYNTAX AddressFamilyNumbers
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 [IANAFamily] of the incoming
value of zero indicates that the family type is packet. A value of other(0) indicates that the
either unknown or undefined. This latter case is family type is either unknown or undefined."
possible for example, when packet streams of DEFVAL { other }
different types are merged in a multipoint-to-point
connection."
REFERENCE
"RFC 1700 - Assigned Numbers, Reynolds and Postel,
October 1994."
DEFVAL { 0 }
::= { mplsInSegmentEntry 4 } ::= { mplsInSegmentEntry 4 }
mplsInSegmentXCIndex OBJECT-TYPE mplsInSegmentXCIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index into mplsXCTable is used to identify which "Index into mplsXCTable which identifies which cross-
cross-connect entry this segment is part of. Note connect entry this segment is part of. A value of
that a value of zero indicates that it is not being zero indicates that this entry is not referred to by
referred to by any cross-connect entry." any cross-connect entry. When a cross-connect entry
is created which this in-segment is a part of, this
object is automatically updated to reflect the value
of mplsXCIndex of that cross-connect entry."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsInSegmentEntry 5 } ::= { mplsInSegmentEntry 5 }
mplsInSegmentTSpecIndex OBJECT-TYPE mplsInSegmentOwner OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX MplsObjectOwner
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents a pointer into the "Denotes the entity that created and is responsible
mplsTSpecTable and indicates the TSpec which is to for managing this segment."
be assigned to this segment. A value of zero DEFVAL { unknown }
indicates best-effort treatment. Two or more
segments can indicate resource sharing by pointing
to the same entry in mplsTSpecTable."
DEFVAL { 0 }
::= { mplsInSegmentEntry 6 } ::= { mplsInSegmentEntry 6 }
mplsInSegmentOwner OBJECT-TYPE mplsInSegmentTrafficParamPtr OBJECT-TYPE
SYNTAX INTEGER { SYNTAX RowPointer
snmp(1),
ldp(2),
rsvp(3),
policyAgent(4),
other(5)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the entity that created and is responsible "This variable represents a pointer to the traffic
for managing this segment." parameter specification for this in-segment. This
value may point at an entry in the
mplsTrafficParamTable to indicate which
mplsTrafficParamEntry is to be assigned to this
segment. This value may optionally point at an
externally defined traffic parameter specification
table. A value of zero-dot-zero indicates best-effort
treatment. By having the same value of this object,
two or more segments can indicate resource sharing."
::= { mplsInSegmentEntry 7 } ::= { mplsInSegmentEntry 7 }
mplsInSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { mplsInSegmentEntry 8 }
mplsInSegmentStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { mplsInSegmentEntry 9 }
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
"This value is used to represent the managerÆs "This value is used to represent the managerÆs
desired operational status of this segment." desired operational status of this segment."
::= { mplsInSegmentEntry 8 } ::= { mplsInSegmentEntry 10 }
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), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerDown(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
"This value represents the actual operational status "This value represents the actual operational status
of this segment." of this segment."
::= { mplsInSegmentEntry 9 } ::= { mplsInSegmentEntry 11 }
mplsInSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table."
::= { 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
skipping to change at page 40, line 36 skipping to change at page 26, line 36
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,
mplsInSegmentPerfDiscontinuityTime TimeStamp
} }
mplsInSegmentOctets OBJECT-TYPE mplsInSegmentOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of octets "This value represents the total number of octets
received by this segment." received by this segment."
::= { mplsInSegmentPerfEntry 1 } ::= { mplsInSegmentPerfEntry 1 }
skipping to change at page 42, line 14 skipping to change at page 27, line 30
DESCRIPTION DESCRIPTION
"The number of labeled packets received on this in- "The number of labeled packets received on this in-
segment, which were chosen to be discarded even segment, which were chosen to be discarded even
though no errors had been detected to prevent their though no errors had been detected to prevent their
being transmitted. One possible reason for being transmitted. One possible reason for
discarding such a labeled packet could be to free up discarding such a labeled packet could be to free up
buffer space." buffer space."
::= { mplsInSegmentPerfEntry 4 } ::= { mplsInSegmentPerfEntry 4 }
mplsInSegmentHCOctets OBJECT-TYPE mplsInSegmentHCOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of octets received. This is the 64 "The total number of octets received. This is the 64
bit version of mplsInSegmentOctets." bit version of mplsInSegmentOctets."
::= { mplsInSegmentPerfEntry 5 } ::= { mplsInSegmentPerfEntry 5 }
mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at
which any one or more of this segment's Counter32 or
Counter64 suffered a discontinuity. If no such
discontinuities have occurred since the last re-
initialization of the local management subsystem, then
this object contains a zero value."
::= { mplsInSegmentPerfEntry 6 }
-- End of mplsInSegmentPerfTable. -- End of mplsInSegmentPerfTable.
-- Out-segment table. -- Out-segment table.
mplsOutSegmentIndexNext OBJECT-TYPE mplsOutSegmentIndexNext OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the next appropriate value to "This object contains the next appropriate value to
be used for mplsOutSegmentIndex when creating be used for mplsOutSegmentIndex when creating
entries in the mplsOutSegmentTable. If the number of entries in the mplsOutSegmentTable. If the number
unassigned entries is exhausted, this object will of unassigned entries is exhausted, this object will
take on the value of 0. To obtain the take on the value of 0. To obtain the
mplsOutSegmentIndex value for a new entry, the mplsOutSegmentIndex value for a new entry, the
manager must first issue a management protocol manager must first issue a management protocol
retrieval operation to obtain the current value of retrieval operation to obtain the current value of
this object. The agent should modify the value to this object. The agent should modify the value to
reflect the next unassigned index after each reflect the next unassigned index after each
retrieval operation. After a manager retrieves a retrieval operation. After a manager retrieves a
value the agent will determine through its local value the agent will determine through its local
policy when this index value will be made available policy when this index value will be made available
for reuse." for reuse."
skipping to change at page 43, line 30 skipping to change at page 28, line 42
DESCRIPTION DESCRIPTION
"This table contains a representation of the outgoing "This table contains a representation of the outgoing
segments from an LSR." segments from an LSR."
::= { mplsLsrObjects 6 } ::= { 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 incoming "An entry in this table represents one outgoing
segment. An entry can be created by a network segment. An entry can be created by a network
administrator or an SNMP agent, or an MPLS signaling administrator or an SNMP agent, or an MPLS signaling
protocol. The creator of the entry is denoted by protocol. The object mplsOutSegmentOwner indicates
mplsOutSegmentOwner. An entry in this table is the creator of this entry."
indexed by the ifIndex of the incoming interface and
the (top) label. Note that since it is possible
that some segments are associated with a tunnel,
traffic parameters of these rows are supported as
read-only objects and their modification can be done
only via the tunnel table, mplsTunnelTable."
REFERENCE
"MPLS Traffic Engineering Management Information Base
Using SMIv2, Srinivasan, Viswanathan and Nadeau,
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 InetAddressType,
mplsOutSegmentNextHopIpv4Addr IpAddress, mplsOutSegmentNextHopIpv4Addr InetAddressIPv4,
mplsOutSegmentNextHopIpv6Addr Ipv6Address, mplsOutSegmentNextHopIpv6Addr InetAddressIPv6,
mplsOutSegmentXCIndex Integer32, mplsOutSegmentXCIndex Integer32,
mplsOutSegmentTSpecIndex Unsigned32, mplsOutSegmentOwner MplsObjectOwner,
mplsOutSegmentOwner INTEGER, mplsOutSegmentTrafficParamPtr RowPointer,
mplsOutSegmentRowStatus RowStatus,
mplsOutSegmentStorageType StorageType,
mplsOutSegmentAdminStatus INTEGER, mplsOutSegmentAdminStatus INTEGER,
mplsOutSegmentOperStatus INTEGER, mplsOutSegmentOperStatus INTEGER
mplsOutSegmentRowStatus RowStatus
} }
mplsOutSegmentIndex OBJECT-TYPE mplsOutSegmentIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32(0..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value contains a unique index for this row. "This value contains a unique index for this row.
While a value of 0 is not valid as an index for this While a value of 0 is not valid as an index for this
row it can be supplied as a valid value to index row it can be supplied as a valid value to index
mplsXCTable to access entries for which no out- mplsXCTable to access entries for which no out-
segment has been configured." segment has been configured."
::= { mplsOutSegmentEntry 1 } ::= { mplsOutSegmentEntry 1 }
mplsOutSegmentIfIndex OBJECT-TYPE mplsOutSegmentIfIndex OBJECT-TYPE
skipping to change at page 45, line 31 skipping to change at page 29, line 47
::= { 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
"This value indicates whether or not a top label "This value indicates whether or not a top label
should be pushed onto the outgoing packet's label should be pushed onto the outgoing packet's label
stack. The value of this variable must be set to stack. The value of this variable must be set to
true if the outgoing interface is ATM, which does true if the outgoing interface does not support pop-
not support pop-and-go, or if it is a tunnel and-go (for example an ATM interface) or if it is a
origination. Note that it is considered an error in tunnel origination. Note that it is considered an
the case that mplsOutSegmentPushTopLabel is set to error in the case that mplsOutSegmentPushTopLabel is
false, but the cross-connect entry which refers to set to false, but the cross-connect entry which
this out-segment has a non-zero mplsLabelStackIndex. refers to this out-segment has a non-zero
The LSR should ensure that this situation cannot mplsLabelStackIndex. The LSR MUST ensure that this
happen " situation does not 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
the label that should be pushed onto the outgoing represents the label that should be pushed onto the
packet's label stack. Note that the contents of the top of the outgoing packet's label stack."
label field can be interpreted in an outgoing
interface specific fashion. For example, the label
carried in the MPLS shim header is 20 bits wide and
the top 12 bits must be zero. The Frame Relay label
is 24 bits wide and the top 8 bits must be zero.
For ATM interfaces the lowermost 16 bits are
interpreted as the VCI, the next 8 bits as the VPI
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 InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the next hop address is IPv4 or "Indicates whether the next hop address is IPv4 or
IPv6. Note that a value of none (1) is valid only IPv6. Note that a value of unknown (0) is valid
when the outgoing interface is of type point-to- only when the outgoing interface is of type point-to-
point." point."
DEFVAL { none } DEFVAL { unknown }
::= { mplsOutSegmentEntry 5 } ::= { mplsOutSegmentEntry 5 }
mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
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
mplsOutSegmentNextHopIpAddrType is ipV4 (2), mplsOutSegmentNextHopIpAddrType is ipV4 (1),
otherwise it should return a value of 0." otherwise it should return a value of 0."
::= { mplsOutSegmentEntry 6 } ::= { mplsOutSegmentEntry 6 }
mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE
SYNTAX Ipv6Address SYNTAX InetAddressIPv6
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IPv6 address of the next hop. Its value is "IPv6 address of the next hop. Its value is
significant only when significant only when
mplsOutSegmentNextHopIpAddrType is ipV6 (3), mplsOutSegmentNextHopIpAddrType is ipV6 (2),
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 (1..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into mplsXCTable which identifies 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 this entry is not referred to by zero indicates that this entry is not referred to by
any cross-connect entry." any cross-connect entry. When a cross-connect entry
is created which this out-segment is a part of, this
object is automatically updated to reflect the value
of mplsXCIndex of that cross-connect entry."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsOutSegmentEntry 8 } ::= { mplsOutSegmentEntry 8 }
mplsOutSegmentTSpecIndex OBJECT-TYPE mplsOutSegmentOwner OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX MplsObjectOwner
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer into the mplsTSpecTable indicating the "Denotes the entity which created and is responsible
TSpec to be assigned for this segment. A value of for managing this segment."
zero indicates best-effort treatment. Two or more DEFVAL { unknown }
segments can indicate resource sharing by pointing
to the same entry in mplsTSpecTable."
DEFVAL { 0 }
::= { mplsOutSegmentEntry 9 } ::= { mplsOutSegmentEntry 9 }
mplsOutSegmentOwner OBJECT-TYPE mplsOutSegmentTrafficParamPtr OBJECT-TYPE
SYNTAX INTEGER { SYNTAX RowPointer
snmp(1),
ldp(2),
rsvp(3),
policyAgent(4),
other(5)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the entity which created and is responsible "This variable represents a pointer to the traffic
for managing this segment." parameter specification for this out-segment. This
value may point at an entry in the
mplsTrafficParamTable to indicate which
mplsTrafficParamEntry is to be assigned to this
segment. This value may optionally point at an
externally defined traffic parameter specification
table. A value of zero-dot-zero indicates best-
effort treatment. By having the same value of this
object, two or more segments can indicate resource
sharing."
::= { mplsOutSegmentEntry 10 } ::= { mplsOutSegmentEntry 10 }
mplsOutSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { mplsOutSegmentEntry 11 }
mplsOutSegmentStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object."
::= { mplsOutSegmentEntry 12 }
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
"The desired operational status of this segment." "The desired operational status of this segment."
::= { mplsOutSegmentEntry 11 } ::= { mplsOutSegmentEntry 13 }
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
-- some reason -- for some reason
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerDown(7) lowerLayerDown(7) -- down due to the state
-- down due to the state of -- of lower layer interfaces
-- lower layer interfaces
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this segment." "The actual operational status of this segment."
::= { mplsOutSegmentEntry 12 } ::= { mplsOutSegmentEntry 14 }
mplsOutSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { 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. The counters in this outgoing segments from an LSR. The counters in this
entry should behave in a manner similar to that of entry should behave in a manner similar to that of
the interface." the interface."
::= { mplsLsrObjects 7 } ::= { 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 outgoing segment configured in
mplsOutSegmentTable." mplsOutSegmentTable."
AUGMENTS { mplsOutSegmentEntry } AUGMENTS { mplsOutSegmentEntry }
::= { mplsOutSegmentPerfTable 1 } ::= { mplsOutSegmentPerfTable 1 }
MplsOutSegmentPerfEntry ::= SEQUENCE { MplsOutSegmentPerfEntry ::= SEQUENCE {
mplsOutSegmentOctets Counter32, mplsOutSegmentOctets Counter32,
mplsOutSegmentPackets Counter32, mplsOutSegmentPackets Counter32,
mplsOutSegmentErrors Counter32, mplsOutSegmentErrors Counter32,
mplsOutSegmentDiscards Counter32, mplsOutSegmentDiscards Counter32,
-- HC counter -- HC counter
mplsOutSegmentHCOctets Counter64 mplsOutSegmentHCOctets Counter64,
mplsOutSegmentPerfDiscontinuityTime TimeStamp
} }
mplsOutSegmentOctets OBJECT-TYPE mplsOutSegmentOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value contains the total number of octets sent "This value contains the total number of octets sent
on this segment." on this segment."
::= { mplsOutSegmentPerfEntry 1 } ::= { mplsOutSegmentPerfEntry 1 }
skipping to change at page 52, line 36 skipping to change at page 34, line 29
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 }
mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at
which any one or more of this segment's Counter32 or
Counter64 suffered a discontinuity. If no such
discontinuities have occurred since the last re-
initialization of the local management subsystem, then
this object contains a zero value."
::= { mplsOutSegmentPerfEntry 6 }
-- End of mplsOutSegmentPerfTable. -- End of mplsOutSegmentPerfTable.
-- Cross-connect table. -- Cross-connect table.
mplsXCIndexNext OBJECT-TYPE mplsXCIndexNext OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to be used "This object contains an appropriate value to be used
for mplsXCIndex when creating entries in the for mplsXCIndex when creating entries in the
mplsXCTable. The value 0 indicates that no mplsXCTable. The value 0 indicates that no
unassigned entries are available. To obtain the unassigned entries are available. To obtain the
value of mplsXCIndex for a new entry in the value of mplsXCIndex for a new entry in the
mplsXCTable, the manager issues a management mplsXCTable, the manager issues a management
protocol retrieval operation to obtain the current protocol retrieval operation to obtain the current
skipping to change at page 55, line 19 skipping to change at page 36, line 20
to 0, should have mplsInSegmentIfIndex = 0 as well, to 0, should have mplsInSegmentIfIndex = 0 as well,
but can be distinguished from originating LSPs but can be distinguished from originating LSPs
because the mplsOutSegmentIfIndex = 0. The because the mplsOutSegmentIfIndex = 0. The
mplsOutSegmentIfIndex MUST only be set to 0 in mplsOutSegmentIfIndex MUST only be set to 0 in
cases of terminating LSPs. cases of terminating LSPs.
An entry can be created by a network administrator An entry can be created by a network administrator
or by an SNMP agent as instructed by an MPLS or by an SNMP agent as instructed by an MPLS
signaling protocol." signaling protocol."
INDEX { mplsXCIndex, mplsInSegmentIfIndex, INDEX { mplsXCIndex, mplsInSegmentIfIndex,
mplsInSegmentLabel, mplsOutSegmentIndex } mplsInSegmentLabel,
mplsOutSegmentIndex }
::= { mplsXCTable 1 } ::= { mplsXCTable 1 }
MplsXCEntry ::= SEQUENCE { MplsXCEntry ::= SEQUENCE {
mplsXCIndex Integer32, mplsXCIndex Integer32,
mplsXCLspId MplsLSPID, mplsXCLspId MplsLSPID,
mplsXCLabelStackIndex Integer32, mplsXCLabelStackIndex Integer32,
mplsXCCOS Integer32,
mplsXCIsPersistent TruthValue, mplsXCIsPersistent TruthValue,
mplsXCOwner INTEGER, mplsXCOwner MplsObjectOwner,
mplsXCRowStatus RowStatus,
mplsXCStorageType StorageType,
mplsXCAdminStatus INTEGER, mplsXCAdminStatus INTEGER,
mplsXCOperStatus INTEGER, mplsXCOperStatus INTEGER
mplsXCRowStatus RowStatus
} }
mplsXCIndex OBJECT-TYPE mplsXCIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
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 mplsXCLspId OBJECT-TYPE
SYNTAX MplsLSPID SYNTAX MplsLSPID
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value identifies the label switched path that "This value identifies the label switched path that
this cross-connect entry belongs to." this cross-connect entry belongs to."
::= { mplsXCEntry 2 } ::= { mplsXCEntry 2 }
mplsXCLabelStackIndex OBJECT-TYPE mplsXCLabelStackIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..2147483647)
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 identified by the out- Note that the top label identified by the out-
segment 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 3 } ::= { mplsXCEntry 3 }
mplsXCCOS OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value is used to override the incoming COS
field for a cross-connect. It may also be used as a
value to assign to outgoing packets for an outgoing
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
"Denotes whether or not this cross-connect entry and "Denotes whether or not this cross-connect entry and
associated in- and out-segments should be restored associated in- and out-segments should be restored
automatically after failures. This value MUST be set automatically after failures. This value MUST be
to false in cases where this cross-connect entry was set to false in cases where this cross-connect entry
created by a signaling protocol." was created by a signaling protocol."
DEFVAL { false } DEFVAL { false }
::= { mplsXCEntry 5 } ::= { mplsXCEntry 4 }
mplsXCOwner OBJECT-TYPE mplsXCOwner OBJECT-TYPE
SYNTAX INTEGER { SYNTAX MplsObjectOwner
snmp(1),
ldp(2),
rsvp(3),
policyAgent(4),
other(5)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the entity that created and is responsible "Denotes the entity that created and is responsible
for managing this cross-connect." for managing this cross-connect."
::= { mplsXCEntry 5 }
mplsXCRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { mplsXCEntry 6 } ::= { mplsXCEntry 6 }
mplsXCStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the storage type for this object."
::= { mplsXCEntry 7 }
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
"The desired operational status of this segment." "The desired operational status of this segment."
::= { mplsXCEntry 7 } ::= { mplsXCEntry 8 }
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
-- some reason -- for some reason.
dormant(5), dormant(5),
notPresent(6), -- some component is missing notPresent(6), -- some component is missing
lowerLayerDown(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 actual operational status of this cross- "The actual operational status of this cross-
connect." connect."
::= { mplsXCEntry 8 }
mplsXCRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { mplsXCEntry 9 } ::= { mplsXCEntry 9 }
-- End of mplsXCTable -- End of mplsXCTable
-- Label stack table. -- Label stack table.
mplsMaxLabelStackDepth OBJECT-TYPE mplsMaxLabelStackDepth OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum stack depth supported by this LSR." "The maximum stack depth supported by this LSR."
::= { mplsLsrObjects 10 } ::= { mplsLsrObjects 10 }
mplsLabelStackIndexNext OBJECT-TYPE mplsLabelStackIndexNext OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to be used "This object contains an appropriate value to be used
for mplsLabelStackIndex when creating entries in the for mplsLabelStackIndex when creating entries in the
mplsLabelStackTable. The value 0 indicates that no mplsLabelStackTable. The value 0 indicates that no
unassigned entries are available. To obtain an unassigned entries are available. To obtain an
mplsLabelStackIndex value for a new entry, the mplsLabelStackIndex value for a new entry, the
manager issues a management protocol retrieval manager issues a management protocol retrieval
operation to obtain the current value of this operation to obtain the current value of this
skipping to change at page 61, line 14 skipping to change at page 39, line 46
top 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
an MPLS signaling protocol." an MPLS signaling protocol."
INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 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,
mplsLabelStackStorageType StorageType
} }
mplsLabelStackIndex OBJECT-TYPE mplsLabelStackIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
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 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 62, line 25 skipping to change at page 40, line 40
::= { 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 }
mplsLabelStackStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the storage type for this object."
::= { mplsLabelStackEntry 5 }
-- End of mplsLabelStackTable -- End of mplsLabelStackTable
-- Traffic Parameter table.
mplsTSpecIndexNext OBJECT-TYPE mplsTrafficParamIndexNext OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value which will "This object contains an appropriate value which will
be used for mplsTSpecIndex when creating entries in be used for mplsTrafficParamIndex when creating
the mplsTSpecTable. The value 0 indicates that no entries in the mplsTrafficParamTable. The value 0
unassigned entries are available. To obtain the indicates that no unassigned entries are available.
mplsTSpecIndex value for a new entry, the manager To obtain the mplsTrafficParamIndex value for a new
issues a management protocol retrieval operation to entry, the manager issues a management protocol
obtain the current value of this object. After each retrieval operation to obtain the current value of
retrieval operation, the agent should modify the this object. After each retrieval operation, the
value to reflect the next unassigned index. After a agent should modify the value to reflect the next
manager retrieves a value the agent will determine unassigned index. After a manager retrieves a value
through its local policy when this index value will the agent will determine through its local policy
be made available for reuse." when this index value will be made available for
reuse."
::= { mplsLsrObjects 13 } ::= { mplsLsrObjects 13 }
mplsTSpecTable OBJECT-TYPE mplsTrafficParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTSpecEntry SYNTAX SEQUENCE OF MplsTrafficParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the Traffic Specification "This table specifies the Traffic Parameter objects
(TSpec) objects for in and out-segments." for in and out-segments."
::= { mplsLsrObjects 14 } ::= { mplsLsrObjects 14 }
mplsTSpecEntry OBJECT-TYPE mplsTrafficParamEntry OBJECT-TYPE
SYNTAX MplsTSpecEntry SYNTAX MplsTrafficParamEntry
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 TrafficParam
for one or more in or out segments. A single entry objects for one or more in or out segments. A
can be pointed to by multiple segments indicating single entry can be pointed to by multiple segments
resource sharing." indicating resource sharing."
INDEX { mplsTSpecIndex } INDEX { mplsTrafficParamIndex }
::= { mplsTSpecTable 1 } ::= { mplsTrafficParamTable 1 }
MplsTSpecEntry ::= SEQUENCE { MplsTrafficParamEntry ::= SEQUENCE {
mplsTSpecIndex Integer32, mplsTrafficParamIndex Integer32,
mplsTSpecMaxRate MplsBitRate, mplsTrafficParamMaxRate MplsBitRate,
mplsTSpecMeanRate MplsBitRate, mplsTrafficParamMeanRate MplsBitRate,
mplsTSpecMaxBurstSize MplsBurstSize, mplsTrafficParamMaxBurstSize MplsBurstSize,
mplsTSpecRowStatus RowStatus mplsTrafficParamRowStatus RowStatus,
mplsTrafficParamStorageType StorageType
} }
mplsTSpecIndex OBJECT-TYPE mplsTrafficParamIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies this row of the table. Note "Uniquely identifies this row of the table. Note
that zero represents an invalid index." that zero represents an invalid index."
::= { mplsTSpecEntry 1 } ::= { mplsTrafficParamEntry 1 }
mplsTSpecMaxRate OBJECT-TYPE mplsTrafficParamMaxRate OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
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 } ::= { mplsTrafficParamEntry 4 }
mplsTSpecMeanRate OBJECT-TYPE mplsTrafficParamMeanRate OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
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 } ::= { mplsTrafficParamEntry 5 }
mplsTSpecMaxBurstSize OBJECT-TYPE mplsTrafficParamMaxBurstSize OBJECT-TYPE
SYNTAX MplsBurstSize SYNTAX MplsBurstSize
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 } ::= { mplsTrafficParamEntry 6 }
mplsTSpecRowStatus OBJECT-TYPE mplsTrafficParamRowStatus 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 } ::= { mplsTrafficParamEntry 7 }
mplsInterfaceTrapEnable OBJECT-TYPE mplsTrafficParamStorageType OBJECT-TYPE
SYNTAX TruthValue SYNTAX StorageType
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "The storage type for this object."
generation of mplsInterfaceUp and mplsInterfaceDown ::= { mplsTrafficParamEntry 8 }
traps, otherwise these traps are not emitted."
DEFVAL { false } -- End of mplsTrafficParamTable
::= { mplsLsrObjects 15 }
-- Notification Configuration
mplsInSegmentTrapEnable OBJECT-TYPE mplsInSegmentTrapEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of mplsInSegmentUp and mplsInSegmentDown generation of mplsInSegmentUp and mplsInSegmentDown
traps, otherwise these traps are not emitted." traps, otherwise these traps are not emitted."
DEFVAL { false } DEFVAL { false }
::= { mplsLsrObjects 16 } ::= { mplsLsrObjects 15 }
mplsOutSegmentTrapEnable OBJECT-TYPE mplsOutSegmentTrapEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of mplsOutSegmentUp and generation of mplsOutSegmentUp and
mplsOutSegmentDown traps, otherwise these traps are mplsOutSegmentDown traps, otherwise these traps are
not emitted." not emitted."
DEFVAL { false } DEFVAL { false }
::= { mplsLsrObjects 17 } ::= { mplsLsrObjects 16 }
mplsXCTrapEnable OBJECT-TYPE mplsXCTrapEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of mplsXCUp and mplsXCDown traps, generation of mplsXCUp and mplsXCDown traps,
otherwise these traps are not emitted." otherwise these traps are not emitted."
DEFVAL { false } DEFVAL { false }
::= { mplsLsrObjects 18 } ::= { mplsLsrObjects 17 }
-- Interface -- Interface
mplsInterfaceUp NOTIFICATION-TYPE
OBJECTS { mplsInterfaceConfIndex,
mplsInterfaceAdminStatus, mplsInterfaceOperStatus }
STATUS current
DESCRIPTION
"This notification is generated when a
mplsInterfaceOperStatus object for one of the
entries in mplsInterfaceConfTable is about to leave
the down state and transition into some other state
(but not into the notPresent state). This other
state is indicated by the included value of
mplsInterfaceOperStatus."
::= { mplsLsrNotifications 1 }
mplsInterfaceDown NOTIFICATION-TYPE
OBJECTS { mplsInterfaceConfIndex,
mplsInterfaceAdminStatus, mplsInterfaceOperStatus }
STATUS current
DESCRIPTION
"This notification is generated when a
mplsInterfaceOperStatus object for one of the
entries in mplsInterfaceConfTable is about to enter
the down state from some other state (but not from
the notPresent state). This other state is
indicated by the included value of
mplsInterfaceOperStatus."
::= { mplsLsrNotifications 2 }
-- In-segment. -- In-segment.
mplsInSegmentUp NOTIFICATION-TYPE mplsInSegmentUp NOTIFICATION-TYPE
OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, OBJECTS { mplsInSegmentIfIndex,
mplsInSegmentAdminStatus, mplsInSegmentOperStatus } mplsInSegmentLabel,
mplsInSegmentAdminStatus,
mplsInSegmentOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsInSegmentOperStatus object for one of the mplsInSegmentOperStatus object for one of the
configured in-segments is about to leave the down configured in-segments is about to leave the down
state and transition into some other state (but not state and transition into some other state (but not
into the notPresent state). This other state is into the notPresent state). This other state is
indicated by the included value of indicated by the included value of
mplsInSegmentOperStatus." mplsInSegmentOperStatus."
::= { mplsLsrNotifications 3 } ::= { mplsLsrNotifications 1 }
mplsInSegmentDown NOTIFICATION-TYPE mplsInSegmentDown NOTIFICATION-TYPE
OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, OBJECTS { mplsInSegmentIfIndex,
mplsInSegmentAdminStatus, mplsInSegmentOperStatus } mplsInSegmentLabel,
mplsInSegmentAdminStatus,
mplsInSegmentOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsInSegmentOperStatus object for one of the mplsInSegmentOperStatus object for one of the
configured in-segments is about to enter the down configured in-segments is about to enter the down
state from some other state (but not from the state from some other state (but not from the
notPresent state). This other state is indicated by notPresent state). This other state is indicated by
the included value of mplsInSegmentOperStatus." the included value of mplsInSegmentOperStatus."
::= { mplsLsrNotifications 4 } ::= { mplsLsrNotifications 2 }
-- Out-segment. -- Out-segment.
mplsOutSegmentUp NOTIFICATION-TYPE mplsOutSegmentUp NOTIFICATION-TYPE
OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, OBJECTS { mplsOutSegmentIndex,
mplsInSegmentAdminStatus,
mplsInSegmentOperStatus } mplsInSegmentOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsOutSegmentOperStatus object for one of the mplsOutSegmentOperStatus object for one of the
configured out-segments is about to leave the down configured out-segments is about to leave the down
state and transition into some other state (but not state and transition into some other state (but not
into the notPresent state). This other state is into the notPresent state). This other state is
indicated by the included value of indicated by the included value of
mplsOutSegmentOperStatus." mplsOutSegmentOperStatus."
::= { mplsLsrNotifications 5 } ::= { mplsLsrNotifications 3 }
mplsOutSegmentDown NOTIFICATION-TYPE mplsOutSegmentDown NOTIFICATION-TYPE
OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, OBJECTS { mplsOutSegmentIndex,
mplsInSegmentAdminStatus,
mplsInSegmentOperStatus } mplsInSegmentOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsOutSegmentOperStatus object for one of the mplsOutSegmentOperStatus object for one of the
configured out-segments is about to enter the down configured out-segments is about to enter the down
state from some other state (but not from the state from some other state (but not from the
notPresent state). This other state is indicated by notPresent state). This other state is indicated by
the included value of mplsOutSegmentOperStatus." the included value of mplsOutSegmentOperStatus."
::= { mplsLsrNotifications 6 } ::= { mplsLsrNotifications 4 }
-- Cross-connect. -- Cross-connect.
mplsXCUp NOTIFICATION-TYPE mplsXCUp NOTIFICATION-TYPE
OBJECTS { mplsXCIndex, OBJECTS { mplsXCIndex,
mplsInSegmentIfIndex, mplsInSegmentLabel, mplsInSegmentIfIndex,
mplsInSegmentLabel,
mplsOutSegmentIndex, mplsOutSegmentIndex,
mplsXCAdminStatus, mplsXCOperStatus } mplsXCAdminStatus,
mplsXCOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsXCOperStatus object for one of the configured mplsXCOperStatus object for one of the configured
cross-connect entries is about to leave the down cross-connect entries is about to leave the down
state and transition into some other state (but not state and transition into some other state (but not
into the notPresent state). This other state is into the notPresent state). This other state is
indicated by the included value of indicated by the included value of
mplsXCOperStatus." mplsXCOperStatus."
::= { mplsLsrNotifications 7 } ::= { mplsLsrNotifications 5 }
mplsXCDown NOTIFICATION-TYPE mplsXCDown NOTIFICATION-TYPE
OBJECTS { mplsXCIndex, OBJECTS { mplsXCIndex,
mplsInSegmentIfIndex, mplsInSegmentLabel, mplsInSegmentIfIndex,
mplsInSegmentLabel,
mplsOutSegmentIndex, mplsOutSegmentIndex,
mplsXCAdminStatus, mplsXCOperStatus } mplsXCAdminStatus,
mplsXCOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated when a
mplsXCOperStatus object for one of the configured mplsXCOperStatus object for one of the configured
cross-connect entries is about to enter the down cross-connect entries is about to enter the down
state from some other state (but not from the state from some other state (but not from the
notPresent state). This other state is indicated by notPresent state). This other state is indicated by
the included value of mplsXCOperStatus." the included value of mplsXCOperStatus."
::= { mplsLsrNotifications 8 } ::= { mplsLsrNotifications 6 }
-- End of notifications. -- End of notifications.
-- Module compliance. -- Module compliance.
mplsLsrGroups mplsLsrGroups
OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } OBJECT IDENTIFIER ::= { mplsLsrConformance 1 }
mplsLsrCompliances mplsLsrCompliances
OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } OBJECT IDENTIFIER ::= { mplsLsrConformance 2 }
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
-- However, they may all be supported as read-only objects -- by all LSRs. However, they may all be supported
-- in the case where manual configuration is unsupported. -- as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, MANDATORY-GROUPS { mplsInSegmentGroup,
mplsXCGroup, mplsInterfaceGroup, mplsOutSegmentGroup,
mplsPerfGroup } mplsXCGroup,
mplsInterfaceGroup,
mplsPerfGroup,
mplsSegmentDiscontinuityGroup }
GROUP mplsHCInterfacePerfGroup
DESCRIPTION
"This group is mandatory for high-speed MPLS
capable interfaces for which the objects
mplsInterfaceInOctets and mplsInterfaceOutOctets
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
entries for which the object entries for which the object
mplsInSegmentOutOctets wraps around too mplsInSegmentOutOctets wraps around too
quickly." quickly."
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 mplsTrafficParamGroup
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 QoS resource reservation."
-- Depending on whether the device implements persistent -- Depending on whether the device implements
-- cross-connects or not one of the following two groups -- persistent cross-connects or not one of the
-- is mandatory. -- following two groups 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
must at least be read-only returning true(2)." must at least be read-only returning true(2)."
GROUP mplsXCIsNotPersistentGroup GROUP mplsXCIsNotPersistentGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which
support non-persistent cross-connects. The support non-persistent cross-connects. The
following constraints apply: mplsXCIsPersistent following constraints apply: mplsXCIsPersistent
must at least be read-only returning false(1)." must at least be read-only returning false(1)."
-- mplsInterfaceConfTable -- mplsInterfaceConfTable
OBJECT mplsInterfaceAdminStatus OBJECT mplsInterfaceConfStorageType
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"A value of testing(3) need not be supported."
OBJECT mplsInterfaceOperStatus
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 other(1) needs to be supported."
-- mplsInSegmentTable -- mplsInSegmentTable
OBJECT mplsInSegmentIfIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsInSegmentLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsInSegmentXCIndex OBJECT mplsInSegmentXCIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsInSegmentTSpecIndex
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsInSegmentNPop OBJECT mplsInSegmentNPop
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access if not required. This object "Write access if not required. This object
should be set to 1 if it is read-only." should be set to 1 if it is read-only."
OBJECT mplsInSegmentAddrFamily OBJECT mplsInSegmentAddrFamily
SYNTAX INTEGER { other(0) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. A value of "Write access is not required. A <value of
other(0) should be supported." other(0) should be supported because there may
be cases where the agent may not know about or
support any address types."
OBJECT mplsInSegmentAdminStatus OBJECT mplsInSegmentAdminStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT mplsInSegmentOperStatus OBJECT mplsInSegmentOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
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."
-- mplsOutSegmentTable OBJECT mplsInSegmentStorageType
SYNTAX INTEGER { other(1) }
OBJECT mplsOutSegmentIndexNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Only other(1) needs to be supported."
OBJECT mplsOutSegmentIndex -- mplsOutSegmentTable
MIN-ACCESS read-only
DESCRIPTION
"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."
OBJECT mplsOutSegmentPushTopLabel OBJECT mplsOutSegmentPushTopLabel
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 76, line 4 skipping to change at page 48, line 23
OBJECT mplsOutSegmentPushTopLabel OBJECT mplsOutSegmentPushTopLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsOutSegmentTopLabel OBJECT mplsOutSegmentTopLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsOutSegmentNextHopIpAddrType OBJECT mplsOutSegmentNextHopIpAddrType
SYNTAX INTEGER { none(1), ipV4(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"ipV6(3) need not be supported." "ipV6(3) need not be supported."
OBJECT mplsOutSegmentNextHopIpv4Addr OBJECT mplsOutSegmentNextHopIpv4Addr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsOutSegmentNextHopIpv6Addr OBJECT mplsOutSegmentNextHopIpv6Addr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsOutSegmentXCIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsOutSegmentTSpecIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsOutSegmentAdminStatus OBJECT mplsOutSegmentAdminStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"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
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), destroy(6) } createAndGo(4), 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."
OBJECT mplsOutSegmentStorageType
-- mplsXCTable SYNTAX INTEGER { other(1) }
OBJECT mplsXCIndexNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Only other(1) needs to be supported."
OBJECT mplsXCIndex -- mplsXCTable
MIN-ACCESS read-only
DESCRIPTION
"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
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mplsXCIsPersistent OBJECT mplsXCIsPersistent
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsXCAdminStatus OBJECT mplsXCAdminStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"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
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),
createAndGo(4), destroy(6) } notInService(2),
createAndGo(4),
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."
OBJECT mplsXCStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
::= { mplsLsrCompliances 1 } ::= { mplsLsrCompliances 1 }
-- Units of conformance. -- Units of conformance.
mplsInterfaceGroup OBJECT-GROUP mplsInterfaceGroup OBJECT-GROUP
OBJECTS { mplsInterfaceConfIndex, OBJECTS { mplsInterfaceLabelMinIn,
mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, mplsInterfaceLabelMaxIn,
mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut, mplsInterfaceLabelMinOut,
mplsInterfaceInLabelsUsed, mplsInterfaceOutLabelsUsed, mplsInterfaceLabelMaxOut,
mplsInterfaceIsGlobalLabelSpace, mplsInterfaceTotalBandwidth,
mplsInterfaceIsLocalLabelSpace, mplsInterfaceAvailableBandwidth,
mplsInterfaceAdminStatus, mplsInterfaceOperStatus, mplsInterfaceTotalBuffer,
mplsInterfaceTrapEnable mplsInterfaceAvailableBuffer,
mplsInterfaceLabelParticipationType,
mplsInterfaceConfStorageType
} }
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, OBJECTS { mplsInSegmentNPop,
mplsInSegmentLabel,
mplsInSegmentNPop,
mplsInSegmentAddrFamily, mplsInSegmentAddrFamily,
mplsInSegmentXCIndex, mplsInSegmentXCIndex,
mplsInSegmentTSpecIndex,
mplsInSegmentOctets, mplsInSegmentOctets,
mplsInSegmentDiscards, mplsInSegmentDiscards,
mplsInSegmentOwner, mplsInSegmentOwner,
mplsInSegmentAdminStatus, mplsInSegmentAdminStatus,
mplsInSegmentOperStatus, mplsInSegmentOperStatus,
mplsInSegmentRowStatus, mplsInSegmentRowStatus,
mplsInSegmentTrapEnable mplsInSegmentTrapEnable,
mplsInSegmentStorageType,
mplsInSegmentTrafficParamPtr
} }
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 { mplsOutSegmentIndexNext, OBJECTS { mplsOutSegmentIndexNext,
mplsOutSegmentIndex,
mplsOutSegmentIfIndex, mplsOutSegmentIfIndex,
mplsOutSegmentPushTopLabel, mplsOutSegmentPushTopLabel,
mplsOutSegmentTopLabel, mplsOutSegmentTopLabel,
mplsOutSegmentNextHopIpAddrType, mplsOutSegmentNextHopIpAddrType,
mplsOutSegmentNextHopIpv4Addr, mplsOutSegmentNextHopIpv4Addr,
mplsOutSegmentNextHopIpv6Addr, mplsOutSegmentNextHopIpv6Addr,
mplsOutSegmentXCIndex, mplsOutSegmentXCIndex,
mplsOutSegmentTSpecIndex,
mplsOutSegmentOwner, mplsOutSegmentOwner,
mplsOutSegmentOctets, mplsOutSegmentOctets,
mplsOutSegmentDiscards, mplsOutSegmentDiscards,
mplsOutSegmentErrors,
mplsOutSegmentAdminStatus, mplsOutSegmentAdminStatus,
mplsOutSegmentOperStatus, mplsOutSegmentOperStatus,
mplsOutSegmentRowStatus, mplsOutSegmentRowStatus,
mplsOutSegmentTrapEnable mplsOutSegmentTrapEnable,
mplsOutSegmentStorageType,
mplsOutSegmentTrafficParamPtr
} }
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 { mplsXCIndexNext, OBJECTS { mplsXCIndexNext,
mplsXCIndex, mplsXCLspId,
mplsXCLabelStackIndex, mplsXCLabelStackIndex,
mplsXCOwner,
mplsXCAdminStatus, mplsXCAdminStatus,
mplsXCOperStatus, mplsXCOperStatus,
mplsXCRowStatus, mplsXCRowStatus,
mplsXCTrapEnable mplsXCTrapEnable,
mplsXCStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a "Collection of objects needed to implement a
cross-connect entry." cross-connect entry."
::= { mplsLsrGroups 4 } ::= { mplsLsrGroups 4 }
mplsPerfGroup OBJECT-GROUP mplsPerfGroup OBJECT-GROUP
OBJECTS { mplsInterfaceInPackets, OBJECTS { mplsInSegmentOctets,
mplsInterfaceInDiscards,
mplsInterfaceOutPackets,
mplsInterfaceOutDiscards,
mplsInSegmentOctets,
mplsInSegmentPackets, mplsInSegmentPackets,
mplsInSegmentErrors,
mplsInSegmentDiscards, mplsInSegmentDiscards,
mplsOutSegmentOctets, mplsOutSegmentOctets,
mplsOutSegmentPackets, mplsOutSegmentPackets,
mplsOutSegmentDiscards } mplsOutSegmentDiscards,
mplsInterfaceInLabelsUsed,
mplsInterfaceInPackets,
mplsInterfaceInDiscards,
mplsInterfaceFailedLabelLookup,
mplsInterfaceOutPackets,
mplsInterfaceOutDiscards,
mplsInterfaceOutFragments,
mplsInterfaceOutLabelsUsed
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects providing performance "Collection of objects providing performance
information information
about an LSR." about an LSR."
::= { mplsLsrGroups 5 } ::= { mplsLsrGroups 5 }
mplsHCInSegmentPerfGroup OBJECT-GROUP mplsHCInSegmentPerfGroup OBJECT-GROUP
OBJECTS { mplsInSegmentHCOctets } OBJECTS { mplsInSegmentHCOctets }
STATUS current STATUS current
skipping to change at page 82, line 31 skipping to change at page 52, line 33
mplsHCOutSegmentPerfGroup OBJECT-GROUP mplsHCOutSegmentPerfGroup OBJECT-GROUP
OBJECTS { mplsOutSegmentHCOctets } OBJECTS { mplsOutSegmentHCOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) providing performance information "Object(s) providing performance information
specific to out-segments for which the object specific to out-segments for which the object
mplsInterfaceOutOctets wraps around too mplsInterfaceOutOctets wraps around too
quickly." quickly."
::= { mplsLsrGroups 7 } ::= { mplsLsrGroups 7 }
mplsTSpecGroup OBJECT-GROUP mplsTrafficParamGroup OBJECT-GROUP
OBJECTS { mplsTSpecIndex, OBJECTS { mplsTrafficParamIndexNext,
mplsTSpecMaxRate, mplsTrafficParamMaxRate,
mplsTSpecMeanRate, mplsTrafficParamMeanRate,
mplsTSpecMaxBurstSize, mplsTrafficParamMaxBurstSize,
mplsTSpecRowStatus } mplsTrafficParamRowStatus,
mplsTrafficParamStorageType
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) required for supporting Int-Serv style "Object(s) required for supporting QoS resource
resource reservation." reservation."
::= { mplsLsrGroups 8 } ::= { 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 9 } ::= { 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 10 } ::= { mplsLsrGroups 10 }
mplsLabelStackGroup OBJECT-GROUP
OBJECTS {mplsLabelStackLabel,
mplsLabelStackRowStatus,
mplsLabelStackStorageType,
mplsMaxLabelStackDepth,
mplsLabelStackIndexNext }
STATUS current
DESCRIPTION
"Objects needed to support label stacking."
::= { mplsLsrGroups 11 }
mplsSegmentDiscontinuityGroup OBJECT-GROUP
OBJECTS { mplsInSegmentPerfDiscontinuityTime,
mplsOutSegmentPerfDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects providing information
specific to segment discontinuities.."
::= { mplsLsrGroups 12 }
mplsLsrNotificationGroup NOTIFICATION-GROUP mplsLsrNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsInterfaceUp, NOTIFICATIONS { mplsInSegmentUp,
mplsInterfaceDown,
mplsInSegmentUp,
mplsInSegmentDown, mplsInSegmentDown,
mplsOutSegmentUp, mplsOutSegmentUp,
mplsOutSegmentDown,
mplsXCUp, mplsXCUp,
mplsXCDown 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 11 } ::= { mplsLsrGroups 13 }
-- End of MPLS-LSR-MIB -- End of MPLS-LSR-MIB
END END
10. Security Considerations 12. Security Considerations
It is clear that this MIB is potentially useful for monitoring of It is clear that this MIB is potentially useful for monitoring of
MPLS LSRs. This MIB can also be used for configuration of certain MPLS LSRs. This MIB can also be used for configuration of certain
objects, and anything that can be configured can be incorrectly objects, and anything that can be configured can be incorrectly
configured, with potentially disastrous results. configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond At this writing, no security holes have been identified beyond
those that SNMP Security [SNMPArch] is itself intended to address. those that SNMP Security [SNMPArch] is itself intended to address.
These relate to primarily controlled access to sensitive These relate to primarily controlled access to sensitive
information and the ability to configure a device - or which might information and the ability to configure a device - or which might
result from operator error, which is beyond the scope of any result from operator error, which is beyond the scope of any
skipping to change at page 85, line 30 skipping to change at page 54, line 48
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in information that may be sensitive from a business perspective, in
that they represent a customer's interface to the MPLS network. that they represent a customer's interface to the MPLS network.
Allowing uncontrolled access to these objects could result in Allowing uncontrolled access to these objects could result in
malicious and unwanted disruptions of network traffic or incorrect malicious and unwanted disruptions of network traffic or incorrect
configurations for these customers. There are no objects that are configurations for these customers. There are no objects that are
particularly sensitive in their own right, such as passwords or particularly sensitive in their own right, such as passwords or
monetary amounts. monetary amounts.
11. Acknowledgments 13. Acknowledgments
We wish to thank Ron Bonica, Keith McCloghrie, Dan Tappan, Bala We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim
Rajagopalan, Eric Gray, Vasanthi Thirumalai and Adrian Farrel. Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, and
Vasanthi Thirumalai.
12. References 14. 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-06.txt>, Internet Draft <draft-ietf-mpls-arch-06.txt>,
August 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-05.txt>, September 1999. <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, "
Definitions of Managed Objects for the
Multiprotocol Label Switching, Label Distribution
Protocol (LDP)", Internet Draft <draft-ietf-mpls-
ldp-mib-05.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-07.txt>, September 1999. label-encaps-07.txt>, September 1999.
[RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T.,
Swallow, G., and V. Srinivasan, "Extensions to RSVP
for LSP Tunnels", Internet Draft <draft-mpls-rsvp-
lsp-tunnel-04.txt>, September 1999.
[CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup
using LDP", Internet Draft <draft-ietf-mpls-cr-ldp-
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
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS,(http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[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.
[SMIv1] Rose, M., and K. McCloghrie, "Structure and [SMIv1] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", RFC 1155, May 1990. based Internets", RFC 1155, May 1990.
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB
Definitions", RFC 1212, March 1991. Definitions", RFC 1212, March 1991.
[SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use
with the SNMP", RFC 1215, March 1991. with the SNMP", RFC 1215, March 1991.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572,
April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April
1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for Version 2 of
the Simple Network Management Protocol (SNMPv2)",
RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)", RFC 2575,
April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April
1999.
[SMIv2] Case, J., McCloghrie, K., Rose, M., and S. [SMIv2] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Structure of Management Information Waldbusser, "Structure of Management Information
for Version 2 of the Simple Network Management for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1902, January 1996. Protocol (SNMPv2)", RFC 1902, January 1996.
[SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Textual Conventions for Version 2 of Waldbusser, "Textual Conventions for Version 2 of
the Simple Network Management Protocol (SNMPv2)", the Simple Network Management Protocol (SNMPv2)",
RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
January 1996. January 1996.
skipping to change at page 89, line 25 skipping to change at page 57, line 36
Network Management Protocol (SNMP)", RFC 2575, Network Management Protocol (SNMP)", RFC 2575,
April 1999. April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture [IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November for the Internet Protocol", RFC 2401, November
1998. 1998.
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces
Group MIB using SMIv2", RFC 2233, Nov. 1997 Group MIB using SMIv2", RFC 2233, Nov. 1997
13. Authors' Addresses [ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM
Management", RFC 2515, Feb. 1999
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
15. Authors' Addresses
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Tachion Networks, Inc.
2 Meridian Road Monmouth Park Corporate Center I
Eatontown, NJ 07724 Building C, 185 Monmouth Parkway
Phone: +1-732-542-7750 x234 West Long Branch, NJ 07764
Phone: +1-732-542-7750 x1234
Email: cheenu@tachion.com Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Force10 Networks Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
Phone: +1-408-571-3516 Phone: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
14. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
 End of changes. 

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