draft-ietf-mpls-mgmt-overview-04.txt   draft-ietf-mpls-mgmt-overview-05.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Category: Informational Category: Informational
Expires: October 2003 Cheenu Srinivasan Expires: October 2003 Cheenu Srinivasan
Parama Networks, Inc. Parama Networks, Inc.
Adrian Farrel Adrian Farrel
Movaz Networks, Inc. Movaz Networks, Inc.
April 2003 May 2003
Multiprotocol Label Switching (MPLS) Management Overview Multiprotocol Label Switching (MPLS) Management Overview
draft-ietf-mpls-mgmt-overview-04.txt draft-ietf-mpls-mgmt-overview-05.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full
conformance with all provisions of Section 10 of RFC 2026 conformance with all provisions of Section 10 of RFC 2026
[RFC2026]. [RFC2026].
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
skipping to change at page 2, line 11 skipping to change at page 2, line 11
This memo describes the management architecture for MPLS This memo describes the management architecture for MPLS
and indicates the inter-relationships between the different and indicates the inter-relationships between the different
MIB modules used for MPLS network management. MIB modules used for MPLS network management.
Table of Contents Table of Contents
1. Introduction 3 1. Introduction 3
2. Terminology 3 2. Terminology 3
3. The SNMP Management Framework 4 3. The SNMP Management Framework 4
4. An Introduction to the MPLS Working Group MIB Modules 4 4. An Introduction to the MPLS Working Group MIB Modules 4
4.1. Structure of the MPLS MIB OID Tree 5 4.1. Structure of the MPLS MIB OID Tree 5
4.2. MPLS-TC-MIB 5 4.2. MPLS-TC-STD-MIB 5
4.3. MPLS-LSR-MIB 5 4.3. MPLS-LSR-STD-MIB 5
4.4. MPLS-LDP-MIB 6 4.4. MPLS-LDP-STD-MIB 6
4.5. MPLS-LDP-GENERIC-MIB 6 4.5. MPLS-LDP-GENERIC-STD-MIB 6
4.6. MPLS-LDP-ATM-MIB 6 4.6. MPLS-LDP-ATM-STD-MIB 6
4.7. MPLS-LDP-FRAME-RELAY-MIB 7 4.7. MPLS-LDP-FRAME-RELAY-STD-MIB 7
4.8. MPLS-TE-MIB 7 4.8. MPLS-TE-STD-MIB 7
4.9. MPLS-FTN-MIB 7 4.9. MPLS-FTN-STD-MIB 7
4.10. TE-LINK-MIB 7 4.10. TE-LINK-STD-MIB 7
4.11. MIB Module Interdependencies 8 4.11. MIB Module Interdependencies 8
4.12. Dependencies on External MIB Modules 8 4.12. Dependencies on External MIB Modules 8
5. Tables, Scalars and Notifications in MPLS-LSR-MIB 9 5. Tables, Scalars and Notifications in MPLS-LSR-STD-MIB 9
5.1. Tables 9 5.1. Tables 9
5.2. Scalars 10 5.2. Scalars 10
5.3. Notifications 10 5.3. Notifications 10
5.4. Dependencies Between MIB Module Tables 10 5.4. Dependencies Between MIB Module Tables 10
6. Tables, Scalars and Notifications in the LDP MIB 11 6. Tables, Scalars and Notifications in the LDP MIB 11
6.1. MIB Modules 11 6.1. MIB Modules 11
6.2. Tables 11 6.2. Tables 11
6.3. Scalars 12 6.3. Scalars 12
6.4. Notifications 12 6.4. Notifications 12
6.5. Dependencies Between MIB Module Tables 13 6.5. Dependencies Between MIB Module Tables 13
7. Tables, Scalars and Notifications in MPLS-TE-MIB 13 7. Tables, Scalars and Notifications in MPLS-TE-STD-MIB 13
7.1. Tables 13 7.1. Tables 13
7.2. Scalars 14 7.2. Scalars 14
7.3. Notifications 15 7.3. Notifications 15
7.4. Dependencies Between MIB Module Tables 15 7.4. Dependencies Between MIB Module Tables 15
8. Tables, Scalars and Notifications in MPLS-FTN-MIB 15 8. Tables, Scalars and Notifications in MPLS-FTN-STD-MIB 15
8.1. Tables 15 8.1. Tables 15
8.2. Scalars 16 8.2. Scalars 16
8.3. Notifications 16 8.3. Notifications 16
8.4. Dependencies Between MIB Module Tables 16 8.4. Dependencies Between MIB Module Tables 16
9. Tables and Objects in TE-LINK-MIB 16 9. Tables and Objects in TE-LINK-STD-MIB 16
9.1. Tables 16 9.1. Tables 16
9.2. Scalars 17 9.2. Scalars 17
9.3. Notifications 17 9.3. Notifications 17
9.4. Dependencies Between MIB Module Tables 17 9.4. Dependencies Between MIB Module Tables 17
10. Table Dependencies Between MPLS MIB Modules 18 10. Table Dependencies Between MPLS MIB Modules 18
11. A Note on Interfaces 18 11. A Note on Interfaces 18
11.1. MPLS Tunnels as Interfaces 18 11.1. MPLS Tunnels as Interfaces 18
11.2. Application of the Interfaces Group to TE Links 19 11.2. Application of the Interfaces Group to TE Links 19
11.3. References to Interface MIB Objects from MPLS MIB Modules 20 11.3. References to Interface MIB Objects from MPLS MIB Modules 20
12. Management Options 21 12. Management Options 21
13. Related IETF MIB Modules 22 13. Related IETF MIB Modules 22
13.1. pwe3 Working Group MIB Modules 22 13.1. pwe3 Working Group MIB Modules 22
13.2. ppvpn Working Group MIB Modules 22 13.2. ppvpn Working Group MIB Modules 22
13.2.1. PPVPN-MPLS-VPN-MIB 22 13.2.1. PPVPN-MPLS-VPN-STD-MIB 22
13.3. ccamp Working Group MIB Modules 23 13.3. ccamp Working Group MIB Modules 23
14. Traffic Engineering Working Group TE MIB 23 14. Traffic Engineering Working Group TE MIB 23
14.1. Choosing Between TE MIB Modules 23 14.1. Choosing Between TE MIB Modules 23
15. Security Considerations 24 15. Security Considerations 24
16. Acknowledgements 25 16. Acknowledgements 25
17. Intellectual Property Consideration 25 17. Intellectual Property Consideration 25
18. Normative References 25 18. Normative References 25
19. Informative References 26 19. Informative References 26
20. Authors' Addresses 28 20. Authors' Addresses 28
21. Full Copyright Statement 28 21. Full Copyright Statement 28
skipping to change at page 3, line 54 skipping to change at page 3, line 54
2. Terminology 2. Terminology
This document uses terminology from the MPLS architecture This document uses terminology from the MPLS architecture
document [RFC3031] and the following MPLS related MIB document [RFC3031] and the following MPLS related MIB
modules: MPLS TC MIB [TCMIB], MPLS LSR MIB [LSRMIB], modules: MPLS TC MIB [TCMIB], MPLS LSR MIB [LSRMIB],
MPLS TE MIB [TEMIB], MPLS LDP MIB [LDPMIB], MPLS TE MIB [TEMIB], MPLS LDP MIB [LDPMIB],
MPLS FTN MIB [FTNMIB], TE LINK MIB [TELMIB], and MPLS FTN MIB [FTNMIB], TE LINK MIB [TELMIB], and
PPVPN MPLS VPN MIB [VPNMIB]. PPVPN MPLS VPN MIB [VPNMIB].
Throughout this document hyphenated MIB names (such as MPLS- Throughout this document hyphenated MIB names (such as MPLS-
TE-MIB) should be taken to refer to specific MIB modules. TE-STD-MIB) should be taken to refer to specific MIB modules.
Non-hyphenated MIB names (such as MPLS LDP MIB) indicate Non-hyphenated MIB names (such as MPLS LDP MIB) indicate
MIB documents. MIB documents.
3. The SNMP Management Framework 3. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
skipping to change at page 5, line 11 skipping to change at page 5, line 11
support for the different MIB modules and objects is, therefore support for the different MIB modules and objects is, therefore
beyond the scope of this document although some recommendations beyond the scope of this document although some recommendations
are included in the sections that follow. are included in the sections that follow.
4.1. Structure of the MPLS MIB OID Tree 4.1. Structure of the MPLS MIB OID Tree
The MPLS MIB OID tree has the following structure. The MPLS MIB OID tree has the following structure.
transmission -- RFC 2578 [RFC2578] transmission -- RFC 2578 [RFC2578]
| |
+- mplsMIB -- MPLS-TC-MIB +- mplsStdMIB -- MPLS-TC-STD-MIB
| | | |
| +- mplsTCMIB -- MPLS-TC-MIB | +- mplsTCStdMIB -- MPLS-TC-STD-MIB
| | | |
| +- mplsLsrMIB -- MPLS-LSR-MIB | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB
| | | |
| +- mplsTeMIB -- MPLS-TE-MIB | +- mplsTeStdMIB -- MPLS-TE-STD-MIB
| | | |
| +- mplsLdpMIB -- MPLS-LDP-MIB | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB
| | | |
| +- mplsLdpAtmMIB -- MPLS-LDP-ATM-MIB | +- mplsLdpAtmStdMIB -- MPLS-LDP-ATM-STD-MIB
| | | |
| +- mplsLdpFrameRelayMIB -- MPLS-LDP-FRAME-RELAY-MIB | +- mplsLdpFrameRelayStdMIB -- MPLS-LDP-FRAME-RELAY-STD-MIB
| | | |
| +- mplsLdpGenericMIB -- MPLS-LDP-GENERIC-MIB | +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB
| | | |
| +- mplsFTNMIB -- MPLS-FTN-MIB | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB
| |
+- teLinkMIB -- TE-LINK-MIB +- teLinkStdMIB -- TE-LINK-STD-MIB
Note: The OIDs for MIB modules are assigned and managed by IANA. Note: The OIDs for MIB modules are assigned and managed by IANA.
They can be found in the referenced MIB documents. They can be found in the referenced MIB documents.
4.2. MPLS-TC-MIB 4.2. MPLS-TC-STD-MIB
MPLS-TC-MIB defines textual conventions [RFC2579] that may be MPLS-TC-STD-MIB defines textual conventions [RFC2579] that may be
common to MPLS related MIB modules. These conventions allow common to MPLS related MIB modules. These conventions allow
multiple MIB modules to use the same syntax and format for a multiple MIB modules to use the same syntax and format for a
concept that is shared between the MIB modules. concept that is shared between the MIB modules.
For example, labels are a central part of MPLS and need to For example, labels are a central part of MPLS and need to
be presented in many of the MIB modules. The textual be presented in many of the MIB modules. The textual
convention for representing an MPLS label is defined in convention for representing an MPLS label is defined in
MPLS-TC-MIB. MPLS-TC-STD-MIB.
All of the other MPLS MIB modules import textual convetions All of the other MPLS MIB modules import textual convetions
from this MIB module. from this MIB module.
4.3. MPLS-LSR-MIB 4.3. MPLS-LSR-STD-MIB
MPLS-LSR-MIB describes managed objects for modeling a MPLS MPLS-LSR-STD-MIB describes managed objects for modeling a MPLS
Label Switching Router (LSR). This puts it at the heart of Label Switching Router (LSR). This puts it at the heart of
the management architecture for MPLS. the management architecture for MPLS.
This MIB module is used to model and manage the basic label This MIB module is used to model and manage the basic label
switching behavior of an MPLS LSR. It represents the label switching behavior of an MPLS LSR. It represents the label
forwarding information base (LFIB) of the LSR and provides forwarding information base (LFIB) of the LSR and provides
a view of the LSPs that are being switched by the LSR in a view of the LSPs that are being switched by the LSR in
question. question.
Since basic MPLS label switching is common to all MPLS Since basic MPLS label switching is common to all MPLS
applications, this MIB module is referenced by many of the applications, this MIB module is referenced by many of the
other MPLS MIB modules. other MPLS MIB modules.
In general, MPLS-LSR-MIB provides a model of incoming In general, MPLS-LSR-STD-MIB provides a model of incoming
labels on MPLS-enabled interfaces being mapped to outgoing labels on MPLS-enabled interfaces being mapped to outgoing
labels on MPLS-enabled interfaces via a conceptual object labels on MPLS-enabled interfaces via a conceptual object
called an MPLS cross-connect. MPLS cross-connect entries called an MPLS cross-connect. MPLS cross-connect entries
and their properties are represented in MPLS-LSR-MIB and and their properties are represented in MPLS-LSR-STD-MIB and
are typically referenced by other MIB modules in order to are typically referenced by other MIB modules in order to
refer to the underlying MPLS LSP. refer to the underlying MPLS LSP.
For example, MPLS-TE-MIB models traffic engineered tunnels. For example, MPLS-TE-STD-MIB models traffic engineered tunnels.
These tunnels map to one or more underlying MPLS LSPs. These tunnels map to one or more underlying MPLS LSPs.
MPLS-TE-MIB refers to the underlying LSP by pointing to MPLS-TE-STD-MIB refers to the underlying LSP by pointing to
cross-connect entries in MPLS-LSR-MIB. cross-connect entries in MPLS-LSR-STD-MIB.
4.4. MPLS-LDP-MIB 4.4. MPLS-LDP-STD-MIB
MPLS-LDP-MIB describes managed objects used to model and MPLS-LDP-STD-MIB describes managed objects used to model and
manage the MPLS Label Distribution Protocol (LDP) manage the MPLS Label Distribution Protocol (LDP)
[RFC3036]. LDP is one of the MPLS protocols used to [RFC3036]. LDP is one of the MPLS protocols used to
distribute labels and establish LSPs. distribute labels and establish LSPs.
This MIB module contains objects common to all LDP This MIB module contains objects common to all LDP
implementations. For an LDP implementation, that provides implementations. For an LDP implementation, that provides
standard MIB support, this MIB module provides the core standard MIB support, this MIB module provides the core
set of objects that are needed along with one or more of set of objects that are needed along with one or more of
the other LDP MIB modules from the following sections. the other LDP MIB modules from the following sections.
4.5. MPLS-LDP-GENERIC-MIB 4.5. MPLS-LDP-GENERIC-STD-MIB
This MIB module provides objects for managing the LDP Per This MIB module provides objects for managing the LDP Per
Platform Label Space and is typically implemented along Platform Label Space and is typically implemented along
with the MPLS-LDP-MIB module. This MIB Module contains with the MPLS-LDP-STD-MIB module. This MIB Module contains
tables for configuring MPLS Generic Label Ranges. Although tables for configuring MPLS Generic Label Ranges. Although
the LDP Specification does not provide a way for configuring the LDP Specification does not provide a way for configuring
Label Ranges for Generic Labels, the MIB module does provide Label Ranges for Generic Labels, the MIB module does provide
a way to reserve a range of generic labels because this was a way to reserve a range of generic labels because this was
thought to be useful by the working group. thought to be useful by the working group.
4.6. MPLS-LDP-ATM-MIB 4.6. MPLS-LDP-ATM-STD-MIB
This MIB module is typically supported along with the This MIB module is typically supported along with the
MPLS-LDP-MIB by LDP implementations if LDP uses ATM as MPLS-LDP-STD-MIB by LDP implementations if LDP uses ATM as
the Layer 2 medium. Tables in this MIB module allow for the Layer 2 medium. Tables in this MIB module allow for
configuring LDP to use ATM. configuring LDP to use ATM.
4.7. MPLS-LDP-FRAME-RELAY-MIB 4.7. MPLS-LDP-FRAME-RELAY-STD-MIB
This MIB module is typically supported along with the This MIB module is typically supported along with the
MPLS-LDP-MIB by LDP implementations if LDP uses Frame Relay MPLS-LDP-STD-MIB by LDP implementations if LDP uses Frame Relay
as the Layer 2 medium. Tables in this MIB module allow for as the Layer 2 medium. Tables in this MIB module allow for
configuration of LDP to use Frame Relay. configuration of LDP to use Frame Relay.
4.8. MPLS-TE-MIB 4.8. MPLS-TE-STD-MIB
MPLS-TE-MIB describes managed objects that are used to MPLS-TE-STD-MIB describes managed objects that are used to
model and manage MPLS Traffic Engineered (TE) Tunnels. model and manage MPLS Traffic Engineered (TE) Tunnels.
This MIB module is based around a table that represents TE This MIB module is based around a table that represents TE
tunnels that either originate from, traverse via or tunnels that either originate from, traverse via or
terminate on the LSR in question or. The MIB module terminate on the LSR in question or. The MIB module
provides configuration and statistics objects needed for TE provides configuration and statistics objects needed for TE
tunnels. tunnels.
4.9. MPLS-FTN-MIB 4.9. MPLS-FTN-STD-MIB
MPLS-FTN-MIB describes managed objects that are used to MPLS-FTN-STD-MIB describes managed objects that are used to
model and manage the MPLS FEC-to-NHLFE (FTN) mappings that model and manage the MPLS FEC-to-NHLFE (FTN) mappings that
take place at an ingress LER. take place at an ingress Label Edge Router (LER).
A Label Edge Router (LER) is an LSR placed at the edge of A LER is an LSR placed at the edge of an MPLS domain and
an MPLS domain and passes traffic into and out of the MPLS passes traffic into and out of the MPLS domain. An ingress
domain. An ingress LER is responsible for classifying data LER is responsible for classifying data and assigning it to
and assigning it to a suitable LSP. a suitable LSP.
This classification is done using Forwarding Equivalency This classification is done using Forwarding Equivalency
Classes (FECs) that define the common attributes of data Classes (FECs) that define the common attributes of data
(usually packets) that will be treated in the same way. (usually packets) that will be treated in the same way.
Once data has been classified it can be handed off to an Once data has been classified it can be handed off to an
LSP through the Next Hop Label Forwarding Entry (NHLFE). LSP through the Next Hop Label Forwarding Entry (NHLFE).
In the case of an IP-to-MPLS mapping, the FEC objects In the case of an IP-to-MPLS mapping, the FEC objects
describe IP 6-tuples representing source and destination describe IP 6-tuples representing source and destination
address ranges, source and destination port ranges, IPv4 address ranges, source and destination port ranges, IPv4
Protocol field or IPv6 next-header field and the DiffServ Protocol field or IPv6 next-header field and the DiffServ
Code Point (DSCP). Code Point (DSCP).
4.10. TE-LINK-MIB 4.10. TE-LINK-STD-MIB
TE-LINK-MIB describes managed objects that are used to model TE-LINK-STD-MIB describes managed objects that are used to model
and manage bundling of TE links in an MPLS network. and manage bundling of TE links in an MPLS network.
The link bundling feature is designed to aggregate one or The link bundling feature is designed to aggregate one or
more similar data channels between a pair of LSRs into a more similar data channels between a pair of LSRs into a
bundled link. The data channel is referred to as a TE link bundled link. The data channel is referred to as a TE link
and is a sub-interface capable of carrying traffic engineered and is a sub-interface capable of carrying traffic engineered
MPLS traffic. MPLS traffic.
A link bundle is a sub-interface that bonds the traffic of A link bundle is a sub-interface that bonds the traffic of
a group of one or more TE links. a group of one or more TE links.
skipping to change at page 8, line 19 skipping to change at page 8, line 19
of these relationships are given below once the MIB modules of these relationships are given below once the MIB modules
have been discussed in more detail. have been discussed in more detail.
The arrows in the following diagram show a 'depends on' The arrows in the following diagram show a 'depends on'
relationship. A "MIB module A depends on MIB module B" relationship. A "MIB module A depends on MIB module B"
relationship means that MIB module A uses a structure or relationship means that MIB module A uses a structure or
textual convention defined in MIB module B, or that MIB textual convention defined in MIB module B, or that MIB
module A contains a pointer (index or RowPointer) to an module A contains a pointer (index or RowPointer) to an
object in MIB module B. object in MIB module B.
+-------> MPLS-TC-MIB +-------> MPLS-TC-STD-MIB
| ^ | ^
| | | |
| MPLS-LSR-MIB <-----------------+ | MPLS-LSR-STD-MIB <-----------------+
| | | |
+<------- MPLS-LDP-MIB ----------------->+ +<------- MPLS-LDP-STD-MIB ----------------->+
| ^ | | ^ |
| | | | | |
| +<-- MPLS-LDP-GENERIC-MIB | | +<-- MPLS-LDP-GENERIC-STD-MIB |
| | | | | |
| +<-- MPLS-LDP-ATM-MIB | | +<-- MPLS-LDP-ATM-STD-MIB |
| | | | | |
| +<-- MPLS-LDP-FRAME-RELAY-MIB | | +<-- MPLS-LDP-FRAME-RELAY-STD-MIB |
| | | |
+<------- MPLS-TE-MIB ------------------>+ +<------- MPLS-TE-STD-MIB ------------------>+
| ^ | | ^ |
| | | | | |
+<------- MPLS-FTN-MIB ----------------->+ +<------- MPLS-FTN-STD-MIB ----------------->+
Thus: Thus:
- All the MPLS MIB modules depend on MPLS-TC-MIB. - All the MPLS MIB modules depend on MPLS-TC-STD-MIB.
- MPLS-LDP-MIB, MPLS-TE-MIB and MPLS-FTN-MIB contain - MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB and MPLS-FTN-STD-MIB contain
references to objects in MPLS-LSR-MIB. references to objects in MPLS-LSR-STD-MIB.
- MPLS-LDP-GENERIC-MIB, MPLS-LDP-ATM-MIB and MPLS-LDP- - MPLS-LDP-GENERIC-STD-MIB, MPLS-LDP-ATM-STD-MIB and MPLS-LDP-
FRAME-RELAY-MIB contain references to objects in MPLS- FRAME-RELAY-STD-MIB contain references to objects in MPLS-
LDP-MIB. LDP-STD-MIB.
- MPLS-FTN-MIB contains references to objects in MPLS-TE- - MPLS-FTN-STD-MIB contains references to objects in MPLS-TE-
MIB. STD-MIB.
4.12. Dependencies on External MIB Modules 4.12. Dependencies on External MIB Modules
With the exception of MPLS-TC-MIB, all the MPLS MIB modules With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules
have dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-MIB have dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-STD-MIB
references IP-capable interfaces on which received traffic is to references IP-capable interfaces on which received traffic is to
be classified using indexes in the Interface Table (ifTable) of be classified using indexes in the Interface Table (ifTable) of
this MIB module. The other MPLS MIB modules reference MPLS- this MIB module. The other MPLS MIB modules reference MPLS-
capable interfaces in ifTable capable interfaces in ifTable.
The Interfaces Group of the IF-MIB [RFC2863] defines generic The Interfaces Group of the IF-MIB [RFC2863] defines generic
managed objects for managing interfaces. The MPLS MIB modules managed objects for managing interfaces. The MPLS MIB modules
contain media-specific extensions to the Interfaces Group contain media-specific extensions to the Interfaces Group
for managing MPLS interfaces. for managing MPLS interfaces.
The MPLS MIB modules assume the interpretation of the The MPLS MIB modules assume the interpretation of the
Interfaces Group to be in accordance with [RFC2863] which Interfaces Group to be in accordance with [RFC2863] which
states that ifTable contains information on the managed states that ifTable contains information on the managed
resource's interfaces and that each sub-layer below the resource's interfaces and that each sub-layer below the
internetwork layer of a network interface is considered an internetwork layer of a network interface is considered an
interface. interface.
Thus, the MPLS interface is represented as an entry in Thus, the MPLS interface is represented as an entry in
ifTable. ifTable.
The inter-relation of entries in ifTable is defined by the The inter-relation of entries in ifTable is defined by the
Interfaces Stack Group defined in [RFC2863]. Interfaces Stack Group defined in [RFC2863].
5. Tables, Scalars and Notifications in MPLS-LSR-MIB 5. Tables, Scalars and Notifications in MPLS-LSR-STD-MIB
5.1. Tables 5.1. Tables
MPLS-LSR-MIB contains the following tables. MPLS-LSR-STD-MIB contains the following tables.
- The interface configuration table - The interface configuration table
(mplsInterfaceConfTable) is used for enabling MPLS on (mplsInterfaceConfTable) is used for enabling MPLS on
MPLS-capable interfaces. MPLS-capable interfaces.
- The in-segment (mplsInSegmentTable) and out-segment - The in-segment (mplsInSegmentTable) and out-segment
(mplsOutSegmentTable) tables are used to configure and (mplsOutSegmentTable) tables are used to configure and
monitor LSP segments carrying data into and out of the monitor LSP segments carrying data into and out of the
LSR, respectively. LSR, respectively.
skipping to change at page 10, line 16 skipping to change at page 10, line 16
Where tables in the MIB module have arbitrary indexes, Where tables in the MIB module have arbitrary indexes,
scalars are provided to supply the next available index. scalars are provided to supply the next available index.
This applies to mplsOutSegmentTable, mplsXCTable, This applies to mplsOutSegmentTable, mplsXCTable,
mplsLabelStackTable and mplsTrafficParamTable. mplsLabelStackTable and mplsTrafficParamTable.
mplsMaxLabelStackDepth defines the maximum size of a mplsMaxLabelStackDepth defines the maximum size of a
imposed label stack supported at this LSR. imposed label stack supported at this LSR.
mplsXCTrapEnable is used to enable and disable mplsXCTrapEnable is used to enable and disable
notifications from MPLS-LSR-MIB. notifications from MPLS-LSR-STD-MIB.
5.3. Notifications 5.3. Notifications
MPLS-LSR-MIB can issue two notifications (if notifications MPLS-LSR-STD-MIB can issue two notifications (if notifications
are enabled). are enabled).
- mplsXCUp reports when a cross-connect becomes active. - mplsXCUp reports when a cross-connect becomes active.
- mplsXCDown reports when a cross-connect becomes - mplsXCDown reports when a cross-connect becomes
inactive. inactive.
5.4. Dependencies Between MIB Module Tables 5.4. Dependencies Between MIB Module Tables
The tables in MPLS-LSR-MIB are related as shown on the The tables in MPLS-LSR-STD-MIB are related as shown on the
diagram below. The arrows indicate a reference from one diagram below. The arrows indicate a reference from one
table to another. table to another.
mplsInterfacePerfTable mplsInterfacePerfTable
^ ^
| |
mplsInterfaceConfTable mplsInterfaceConfTable
^ ^ ^ ^
| | | |
+----+ +----+ +----+ +----+
skipping to change at page 11, line 12 skipping to change at page 11, line 12
V V V V
mplsInSegmentPerfTable mplsOutSegmentPerfTable mplsInSegmentPerfTable mplsOutSegmentPerfTable
6. Tables, Scalars and Notifications in the LDP MIB 6. Tables, Scalars and Notifications in the LDP MIB
6.1. MIB Modules 6.1. MIB Modules
The MIB document for LDP contains four MIB modules. This The MIB document for LDP contains four MIB modules. This
structure makes it easier for an implementation to select structure makes it easier for an implementation to select
only those modules that are relevant to it. The MIB Modules only those modules that are relevant to it. The MIB Modules
are the MPLS-LDP-MIB, the MPLS-LDP-GENERIC-MIB, the MPLS- are the MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-
LDP-ATM-MIB and the MPLS-LDP-FRAME-RELAY-MIB. LDP-ATM-STD-MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB.
The MPLS-LDP-MIB defines objects which are specific to LDP The MPLS-LDP-STD-MIB defines objects which are specific to LDP
without any Layer 2 objects. The MPLS-LDP-GENERIC-MIB without any Layer 2 objects. The MPLS-LDP-GENERIC-STD-MIB
defines Layer 2 Per Platform Label Space objects for use defines Layer 2 Per Platform Label Space objects for use
with the MPLS-LDP-MIB and for use on Ehternet. The MPLS- with the MPLS-LDP-STD-MIB and for use on Ehternet. The MPLS-
LDP-ATM-MIB defines Layer 2 Asynchronous Transfer Mode LDP-ATM-STD-MIB defines Layer 2 Asynchronous Transfer Mode
(ATM) objects for use with the MPLS-LDP-MIB. The MPLS-LDP- (ATM) objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-
FRAME-RELAY-MIB defines Layer 2 FRAME-RELAY objects for use FRAME-RELAY-STD-MIB defines Layer 2 FRAME-RELAY objects for use
with the MPLS-LDP-MIB. with the MPLS-LDP-STD-MIB.
The MPLS-LDP-MIB module provides the core support and is The MPLS-LDP-STD-MIB module provides the core support and is
typically supported along with at least one of the Layer 2 typically supported along with at least one of the Layer 2
MIB modules. MIB modules.
6.2. Tables 6.2. Tables
The tables in the LDP MIB for configuring the LDP behavior The tables in the LDP MIB for configuring the LDP behavior
of an LSR are as follows. of an LSR are as follows.
- The LDP Entity Table (mplsLdpEntityTable) provides a - The LDP Entity Table (mplsLdpEntityTable) provides a
way to configure the LSR for using LDP. There must be way to configure the LSR for using LDP. There must be
skipping to change at page 12, line 22 skipping to change at page 12, line 22
(mplsLdpSesPeerAddrTable) stores addresses learned (mplsLdpSesPeerAddrTable) stores addresses learned
after session initialization via Address Message after session initialization via Address Message
advertisement. advertisement.
- The LDP FEC Table (mplsFecTable) represents FEC - The LDP FEC Table (mplsFecTable) represents FEC
(Forwarding Equivalence Class) information that may be (Forwarding Equivalence Class) information that may be
in use on one or more LSPs. The LDP LSP FEC Table in use on one or more LSPs. The LDP LSP FEC Table
(mplsLdpLspFecTable) shows the FECs associated with (mplsLdpLspFecTable) shows the FECs associated with
each LSP. each LSP.
- MPLS-LDP-MIB has a mapping table (mplsLdpLspTable) - MPLS-LDP-STD-MIB has a mapping table (mplsLdpLspTable)
which maps the LDP MIB's representation of LDP sessions which maps the LDP MIB's representation of LDP sessions
to the underlying LSR MIB's representation of the LSPs to the underlying LSR MIB's representation of the LSPs
created by these sessions by pointing to created by these sessions by pointing to
mplsInSegmentTable, mplsOutSegmentTable and mplsInSegmentTable, mplsOutSegmentTable and
mplsXCTable, respectively. mplsXCTable, respectively.
- Statistics may be gathered through the LDP Entity - Statistics may be gathered through the LDP Entity
Statistics Table (mplsLdpEntityStatsTable) and the LDP Statistics Table (mplsLdpEntityStatsTable) and the LDP
Session Statistics Table (mplsLdpSesStatsTable) Session Statistics Table (mplsLdpSesStatsTable)
skipping to change at page 12, line 45 skipping to change at page 12, line 45
Where tables in the MIB modules have arbitrary indexes, Where tables in the MIB modules have arbitrary indexes,
scalars are provided to supply the next available index. scalars are provided to supply the next available index.
This applies to the mplsLdpEntityTable and the mplsFecTable. This applies to the mplsLdpEntityTable and the mplsFecTable.
Two scalars exist to configure the LSR. The LSR ID is set in Two scalars exist to configure the LSR. The LSR ID is set in
mplsLdpLsrId, and the loop detection capabilities are reported mplsLdpLsrId, and the loop detection capabilities are reported
in mplsLdpLsrLoopDetectionCapable in mplsLdpLsrLoopDetectionCapable
6.4. Notifications 6.4. Notifications
MPLS-LDP-MIB defines four notifications that a device can MPLS-LDP-STD-MIB defines four notifications that a device can
issue. issue.
- mplsLdpInitSesThresholdExceeded is reported when the - mplsLdpInitSesThresholdExceeded is reported when the
number of Session Initialization messages exceeds a number of Session Initialization messages exceeds a
configured threshold. configured threshold.
- mplsLdpPVLMismatch is issued if the Path Vector Limit - mplsLdpPVLMismatch is issued if the Path Vector Limit
for a configured Entity and Peer do not match. for a configured Entity and Peer do not match.
- mplsLdpSessionUp and mplsLdpSessionDown report the - mplsLdpSessionUp and mplsLdpSessionDown report the
transition of Session state. transition of Session state.
No scalar object is provided to enable and disable No scalar object is provided to enable and disable
notifications from MPLS-LDP-MIB. Instead, the implementer notifications from MPLS-LDP-STD-MIB. Instead, the implementer
is referred to [RFC3413]. is referred to [RFC3413].
6.5. Dependencies Between MIB Module Tables 6.5. Dependencies Between MIB Module Tables
The many tables in the four LDP MIB modules are related as The many tables in the four LDP MIB modules are related as
shown on the diagram below. The arrows indicate a shown on the diagram below. The arrows indicate a
reference from one table to another. Note that in many reference from one table to another. Note that in many
cases the reference is through an augmentation of the cases the reference is through an augmentation of the
referenced table. referenced table.
skipping to change at page 13, line 42 skipping to change at page 13, line 42
mplsLdpSessionTable mplsLdpSessionTable
^ ^ ^ ^
| | | |
mplsLdpSesStatsTable ------+ +-- mplsLdpLspFecTable mplsLdpSesStatsTable ------+ +-- mplsLdpLspFecTable
mplsLdpAtmSesTable --------+ | | | mplsLdpAtmSesTable --------+ | | |
mplsLdpFrameRelaySesTable--+ | | V mplsLdpFrameRelaySesTable--+ | | V
| | mplsFecTable | | mplsFecTable
| V | V
+-- mplsLdpLspTable +-- mplsLdpLspTable
7. Tables, Scalars and Notifications in MPLS-TE-MIB 7. Tables, Scalars and Notifications in MPLS-TE-STD-MIB
7.1. Tables 7.1. Tables
MPLS-TE-MIB contains the following tables. MPLS-TE-STD-MIB contains the following tables.
- The Tunnel table (mplsTunnelTable) is used to configure - The Tunnel table (mplsTunnelTable) is used to configure
and report MPLS tunnels. Note that reporting of and report MPLS tunnels. Note that reporting of
tunnels in this table at transit LSRs is optional. tunnels in this table at transit LSRs is optional.
Entries in the mplsTunnelTable are indexed by four Entries in the mplsTunnelTable are indexed by four
objects. The source and destination LSR Ids give objects. The source and destination LSR Ids give
context to the entry, and an index context to the entry, and an index
(mplsTunnelIndexIndex) identifies the tunnel itself. (mplsTunnelIndexIndex) identifies the tunnel itself.
However, the fourth index (mplsTunnelInstance) may give However, the fourth index (mplsTunnelInstance) may give
skipping to change at page 15, line 6 skipping to change at page 15, line 6
Two scalars exist to configure the support for MPLS tunnels Two scalars exist to configure the support for MPLS tunnels
on the LSR. mplsTunnelTEDistProto lists the signaling on the LSR. mplsTunnelTEDistProto lists the signaling
methods and protocols supported. mplsTunnelMaxHops defines methods and protocols supported. mplsTunnelMaxHops defines
the size of route that may be configured on the LSR. the size of route that may be configured on the LSR.
Two further scalars enhance the statistics on the LSR by Two further scalars enhance the statistics on the LSR by
counting the number of configured (mplsTunnelConfigured) counting the number of configured (mplsTunnelConfigured)
and active (mplsTunnelActive) tunnels. and active (mplsTunnelActive) tunnels.
The scalar mplsTunnelTrapEnable is used to enable and The scalar mplsTunnelTrapEnable is used to enable and
disable notifications from MPLS-TE-MIB. disable notifications from MPLS-TE-STD-MIB.
7.3. Notifications 7.3. Notifications
MPLS-TE-MIB defines four notifications that a device can MPLS-TE-STD-MIB defines four notifications that a device can
issue. issue.
- mplsTunnelUp and mplsTunnelDown report the transition - mplsTunnelUp and mplsTunnelDown report the transition
of Tunnel state. of Tunnel state.
- Rerouting and re-optimization of Tunnels paths are - Rerouting and re-optimization of Tunnels paths are
reported by mplsTunnelRerouted and reported by mplsTunnelRerouted and
mplsTunnelReoptimized. mplsTunnelReoptimized.
7.4. Dependencies Between MIB Module Tables 7.4. Dependencies Between MIB Module Tables
The tables in MPLS-TE-MIB are related as shown on the The tables in MPLS-TE-STD-MIB are related as shown on the
diagram below. The arrows indicate a reference from one diagram below. The arrows indicate a reference from one
table to another. table to another.
mplsTunnelPerfTable mplsTunnelPerfTable
| |
V V
mplsTunnelTable mplsTunnelTable
^ ^ ^ ^
| | | |
mplsTunnelResourceTable +---mplsTunnelHopTable mplsTunnelResourceTable +---mplsTunnelHopTable
^ | ^ |
| +---mplsTunnelCHopTable | +---mplsTunnelCHopTable
mplsTunnelCRLDPResTable | mplsTunnelCRLDPResTable |
+---mplsTunnelARHopTable +---mplsTunnelARHopTable
8. Tables, Scalars and Notifications in MPLS-FTN-MIB 8. Tables, Scalars and Notifications in MPLS-FTN-STD-MIB
8.1. Tables 8.1. Tables
MPLS-FTN-MIB contains the following tables. MPLS-FTN-STD-MIB contains the following tables.
- The FEC to NHLFE Table (mplsFTNTable) defines the FEC - The FEC to NHLFE Table (mplsFTNTable) defines the FEC
to NHLFE rules to be applied to incoming packets, and to NHLFE rules to be applied to incoming packets, and
the actions to be taken on matching packets. the actions to be taken on matching packets.
- The FEC to NHLFE Map Table (mplsFTNMapTable) provides - The FEC to NHLFE Map Table (mplsFTNMapTable) provides
the capability to activate FTN rules defined in the the capability to activate FTN rules defined in the
mplsFTNTable on specific interfaces in the system. mplsFTNTable on specific interfaces in the system.
- Performance statistics for FTN rules are found in the - Performance statistics for FTN rules are found in the
skipping to change at page 16, line 20 skipping to change at page 16, line 20
respectively. Another scalar, mplsFTNIndexNext, is used to respectively. Another scalar, mplsFTNIndexNext, is used to
supply the next valid index for creating new conceptual rows supply the next valid index for creating new conceptual rows
in mplsFTNTable. in mplsFTNTable.
8.3. Notifications 8.3. Notifications
There are no notifications in this MIB module. There are no notifications in this MIB module.
8.4. Dependencies Between MIB Module Tables 8.4. Dependencies Between MIB Module Tables
The tables in MPLS-FTN-MIB are related as shown on the The tables in MPLS-FTN-STD-MIB are related as shown on the
diagram below. The arrows indicate a reference from one diagram below. The arrows indicate a reference from one
table to another. table to another.
mplsFTNTable mplsFTNTable
^ ^ ^ ^
| | | |
mplsFTNMapTable mplsFTNPerfTable mplsFTNMapTable mplsFTNPerfTable
9. Tables and Objects in TE-LINK-MIB 9. Tables and Objects in TE-LINK-STD-MIB
9.1. Tables 9.1. Tables
TE-LINK-MIB contains the following tables. TE-LINK-STD-MIB contains the following tables.
- The TE link table (teLinkTable) is used to specify TE - The TE link table (teLinkTable) is used to specify TE
links, including bundled links, and their generic links, including bundled links, and their generic
traffic engineering parameters. traffic engineering parameters.
- The TE link descriptor table (teLinkDescriptorTable) is - The TE link descriptor table (teLinkDescriptorTable) is
used to list the TE link descriptors. used to list the TE link descriptors.
- The TE link OSPF traffic engineering table - The TE link OSPF traffic engineering table
(teLinkOspfTeTable) is used for configuring OSPF (teLinkOspfTeTable) is used for configuring OSPF
skipping to change at page 17, line 29 skipping to change at page 17, line 29
9.3. Notifications 9.3. Notifications
A single notification is defined. A single notification is defined.
- linkBundleMismatch is generated when a mismatch of TE - linkBundleMismatch is generated when a mismatch of TE
parameters between members of a bundled link is found. parameters between members of a bundled link is found.
9.4. Dependencies Between MIB Module Tables 9.4. Dependencies Between MIB Module Tables
The tables in TE-LINK-MIB are related as shown on the The tables in TE-LINK-STD-MIB are related as shown on the
diagram below. The arrows indicate a reference from one diagram below. The arrows indicate a reference from one
table to another. table to another.
Note that many of the associations between tables are Note that many of the associations between tables are
through a common index that is the ifIndex of the related through a common index that is the ifIndex of the related
interface. interface.
teLinkTable teLinkTable
^ ^
| |
skipping to change at page 18, line 12 skipping to change at page 18, line 12
| |
dataBearingChannelBandwidthTable ----+ dataBearingChannelBandwidthTable ----+
10. Table Dependencies Between MPLS MIB Modules 10. Table Dependencies Between MPLS MIB Modules
Section 4.11 gave an overview of how the MPLS MIB modules Section 4.11 gave an overview of how the MPLS MIB modules
are related. Now that the tables in the MIB modules have are related. Now that the tables in the MIB modules have
been introduced, it is possible to give a more detailed been introduced, it is possible to give a more detailed
diagram of these relationships. diagram of these relationships.
MPLS-TC-MIB is left off the diagram since so many of the MPLS-TC-STD-MIB is left off the diagram since so many of the
MIB module tables use textual conventions from that MIB MIB module tables use textual conventions from that MIB
module. module.
mplsLsrXCTable mplsLsrInSegmentTable mplsLsrXCTable mplsLsrInSegmentTable
^ ^ ^ ^
| | | |
+---- mplsLdpLspTable +---- mplsLdpLspTable
| | | |
mplsTunnelTable ------+ V mplsTunnelTable ------+ V
^ | mplsLsrOutSegmentTable ^ | mplsLsrOutSegmentTable
| | | |
mplsFTNTable ---------+ mplsFTNTable ---------+
11. A Note on Interfaces 11. A Note on Interfaces
The Interfaces Group of the IF-MIB [RFC2863] defines generic The Interfaces Group of the IF-MIB [RFC2863] defines generic
managed objects for managing interfaces. The MPLS MIB modules managed objects for managing interfaces. The MPLS MIB modules
make references to interfaces in order that it can be clearly make references to interfaces in order that it can be clearly
determined where the procedures managed by the MIB modules determined where the procedures managed by the MIB modules
should be performed. Additionally, the MPLS MIB modules should be performed. Additionally, the MPLS MIB modules
(notably MPLS-TE-MIB and TE-LINK-MIB) utilize interface (notably MPLS-TE-STD-MIB and TE-LINK-STD-MIB) utilize interface
stacking within the Interface Group. stacking within the Interface Group.
11.1. MPLS Tunnels as Interfaces 11.1. MPLS Tunnels as Interfaces
The MPLS-TE-MIB builds on the concept of managing MPLS The MPLS-TE-STD-MIB builds on the concept of managing MPLS
Tunnels as logical interfaces. [RFC2863] states that the Tunnels as logical interfaces. [RFC2863] states that the
interfaces table (ifTable) contains information on the interfaces table (ifTable) contains information on the
managed resource's interfaces, and that each sub-layer managed resource's interfaces, and that each sub-layer
below the internetwork layer of a network interface is below the internetwork layer of a network interface is
considered an interface. Thus, an MPLS Tunnel managed as considered an interface. Thus, an MPLS Tunnel managed as
an interface is represented as an entry in the ifTable. an interface is represented as an entry in the ifTable.
The interrelation of entries in the ifTable is defined by The interrelation of entries in the ifTable is defined by
the Interfaces Stack Group defined in [RFC2863]. the Interfaces Stack Group defined in [RFC2863].
When using MPLS Tunnels as interfaces, the interface stack When using MPLS Tunnels as interfaces, the interface stack
skipping to change at page 19, line 31 skipping to change at page 19, line 31
The ifOperStatus object reflects the actual operational The ifOperStatus object reflects the actual operational
status of MPLS tunnel and may be mapped from the status of MPLS tunnel and may be mapped from the
mplsTunnelOperStatus object. mplsTunnelOperStatus object.
It may be considered convenient and good management to set It may be considered convenient and good management to set
the ifName object to reflect the name of the MPLS tunnel as the ifName object to reflect the name of the MPLS tunnel as
contained in the mplsTunnelName object. contained in the mplsTunnelName object.
11.2. Application of the Interfaces Group to TE Links 11.2. Application of the Interfaces Group to TE Links
The TE-LINK-MIB also uses interface stacking to manage TE The TE-LINK-STD-MIB also uses interface stacking to manage TE
Link interfaces as logical interfaces. The TE Link interface Link interfaces as logical interfaces. The TE Link interface
is represented as an entry in the ifTable. The inter-relation is represented as an entry in the ifTable. The inter-relation
of entries in the ifTable is defined by Interfaces Stack Group of entries in the ifTable is defined by Interfaces Stack Group
defined in [RFC2863]. When using TE Link interfaces, the defined in [RFC2863]. When using TE Link interfaces, the
interface stack table might appear as follows: interface stack table might appear as follows:
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| MPLS interface ifType = mpls(166) | | MPLS interface ifType = mpls(166) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| TE link-interface (bundle) ifType = teLink(200) | | TE link-interface (bundle) ifType = teLink(200) |
skipping to change at page 20, line 19 skipping to change at page 20, line 19
Each TE Link interface is represented by a separate entry Each TE Link interface is represented by a separate entry
in the ifTable with a unique ifIndex. in the ifTable with a unique ifIndex.
The type of an interface represented by an entry in the The type of an interface represented by an entry in the
ifTable is indicated by the ifType object. The value that ifTable is indicated by the ifType object. The value that
is allocated to identify a TE Link 200. is allocated to identify a TE Link 200.
11.3. References to Interface MIB Objects from MPLS MIB Modules 11.3. References to Interface MIB Objects from MPLS MIB Modules
The MPLS-TE-MIB contains two objects that reference the The MPLS-TE-STD-MIB contains two objects that reference the
management of an MPLS tunnel as an interface. management of an MPLS tunnel as an interface.
mplsTunnelIsIf is a TRuthValue that indicates whether the mplsTunnelIsIf is a TRuthValue that indicates whether the
tunnel is present in the ifTable. If the tunnel is managed tunnel is present in the ifTable. If the tunnel is managed
as an interface, the mplsTunnelIfIndex object contains the as an interface, the mplsTunnelIfIndex object contains the
ifIndex that identifies the corresponding entry in the ifIndex that identifies the corresponding entry in the
ifTable. ifTable.
The MPLS-LSR-MIB includes a table (mplsInterfaceConfTable) The MPLS-LSR-STD-MIB includes a table (mplsInterfaceConfTable)
for configuring the support for MPLS on specific for configuring the support for MPLS on specific
interfaces. A conceptual row in this table is created interfaces. A conceptual row in this table is created
automatically by an LSR for every interface that is capable automatically by an LSR for every interface that is capable
of and configured for support of MPLS. A conceptual row in of and configured for support of MPLS. A conceptual row in
this table will exist if and only if a corresponding entry this table will exist if and only if a corresponding entry
in ifTable exists with ifType = mpls(166). The fate of the in ifTable exists with ifType = mpls(166). The fate of the
entries in the two tables are closely linked so that if the entries in the two tables are closely linked so that if the
entry in the ifTable is operationally disabled, the entry entry in the ifTable is operationally disabled, the entry
in the mplsInterfaceConfTable is deleted. During the life in the mplsInterfaceConfTable is deleted. During the life
of an entry in the mplsInterfaceConfTable a corresponding of an entry in the mplsInterfaceConfTable a corresponding
entry is managed in the mplsInterfacePerfTable to show entry is managed in the mplsInterfacePerfTable to show
performance counters for the MPLS-capable interface. performance counters for the MPLS-capable interface.
The ifIndex that identifies MPLS-capable interfaces also The ifIndex that identifies MPLS-capable interfaces also
plays an important indexing role in the MPLS-LSR-MIB. In- plays an important indexing role in the MPLS-LSR-STD-MIB. In-
segments (that is incoming LSP labels) are represented in segments (that is incoming LSP labels) are represented in
the mplsInSegmentTable which is indexed by the the mplsInSegmentTable which is indexed by the
mplsInSegmentIfIndex and mplsInSegmentLabel objects. mplsInSegmentIfIndex and mplsInSegmentLabel objects.
mplsInSegmentIfIndex is set to the ifIndex of the incoming mplsInSegmentIfIndex is set to the ifIndex of the incoming
MPLS-capable interface. mplsInSegmentLabel identifies the MPLS-capable interface. mplsInSegmentLabel identifies the
incoming MPLS label. Note that the corresponding incoming MPLS label. Note that the corresponding
mplsOutSegmentTable contains an mplsOutSegmentIfIndex mplsOutSegmentTable contains an mplsOutSegmentIfIndex
object to identify the outgoing MPLS-capable interface, but object to identify the outgoing MPLS-capable interface, but
that this does not form part of the index of the table. that this does not form part of the index of the table.
The MPLS-LDP-MIB use ifIndex extensively to identify the The MPLS-LDP-STD-MIB use ifIndex extensively to identify the
interface over which MPLS is active. interface over which MPLS is active.
Within the MPLS-FTN-MIB, the mplsFTNMapTable maps entries Within the MPLS-FTN-STD-MIB, the mplsFTNMapTable maps entries
in the mplsFTNTable to interfaces on which the mplsFTNTable in the mplsFTNTable to interfaces on which the mplsFTNTable
entries should be used. Interfaces are identified using entries should be used. Interfaces are identified using
their ifIndex values. their ifIndex values.
12. Management Options 12. Management Options
It is not the intention of this document to provide It is not the intention of this document to provide
instructions or advice to implementers of Management instructions or advice to implementers of Management
Stations, Management Agents or managed entities. It is, Stations, Management Agents or managed entities. It is,
however, useful to make some observations about how the MIB however, useful to make some observations about how the MIB
modules described above might be used to manage MPLS modules described above might be used to manage MPLS
systems. systems.
All MPLS LSPs may appear in the MPLS-LSR-MIB. At transit All MPLS LSPs may appear in the MPLS-LSR-STD-MIB. At transit
nodes they are seen as full cross-connects between incoming nodes they are seen as full cross-connects between incoming
labels on incoming interfaces and outgoing labels on labels on incoming interfaces and outgoing labels on
outgoing interfaces. At ingress or egress points the cross- outgoing interfaces. At ingress or egress points the cross-
connections are unbalanced having spoof upstream or connections are unbalanced having spoof upstream or
downstream legs respectively. downstream legs respectively.
Split and merge points of LSPs may be represented as more Split and merge points of LSPs may be represented as more
complex cross-connects in the MPLS-LSR-MIB. Similarly, complex cross-connects in the MPLS-LSR-STD-MIB. Similarly,
bidirectional LSPs can be represented by using the same bidirectional LSPs can be represented by using the same
cross-connect index for each of the forward and reverse cross-connect index for each of the forward and reverse
cross-connections. cross-connections.
The modules in the LDP MIB are intended solely for use with The modules in the LDP MIB are intended solely for use with
LDP and CR-LDP. LSPs that are signaled through other means LDP and CR-LDP. LSPs that are signaled through other means
may conveniently be stored in the mplsLdpLspTable for may conveniently be stored in the mplsLdpLspTable for
consistency with LSPs set up using LDP, but there is little consistency with LSPs set up using LDP, but there is little
further value to this since the table gives only pointers further value to this since the table gives only pointers
into the MPLS-LSR-MIB. If, however, the LSPs are into the MPLS-LSR-STD-MIB. If, however, the LSPs are
established with associated FECs using some signaling established with associated FECs using some signaling
method other than LDP (for example, BGP) it may be method other than LDP (for example, BGP) it may be
advantageous to use the mplsLdpLspTable, mplsFecTable and advantageous to use the mplsLdpLspTable, mplsFecTable and
mplsLdpLspFecTable to correlate the LSPs. mplsLdpLspFecTable to correlate the LSPs.
Note that if CR-LDP is the signaling protocol there is no Note that if CR-LDP is the signaling protocol there is no
requirement to use the LSP-related tables in the LDP MIB requirement to use the LSP-related tables in the LDP MIB
since the LSP will be adequately represented in the MPLS-TE- since the LSP will be adequately represented in the MPLS-TE-
MIB and the MPLS-LSR-MIB. MIB and the MPLS-LSR-STD-MIB.
MPLS tunnels may be represented in the MPLS-TE-MIB with MPLS tunnels may be represented in the MPLS-TE-STD-MIB with
their cross-connects indicated in the MPLS-LSR-MIB. their cross-connects indicated in the MPLS-LSR-STD-MIB.
Tunnels are often (although not always) set up with a Tunnels are often (although not always) set up with a
series of constraints that may be represented in the MPLS- series of constraints that may be represented in the MPLS-
TE-MIB. Note that a distinguishing feature of a tunnel is TE-STD-MIB. Note that a distinguishing feature of a tunnel is
that it has an ingress and an egress, where LSPs that it has an ingress and an egress, where LSPs
established through LDP may be end-to-end or may be hop-by- established through LDP may be end-to-end or may be hop-by-
hop. hop.
All LSPs (tunnels and non-tunnels) may be established as a All LSPs (tunnels and non-tunnels) may be established as a
result of signaling protocols already defined or for future result of signaling protocols already defined or for future
study. In addition, LSPs may be manually set up by issuing study. In addition, LSPs may be manually set up by issuing
configuration commands to each of the LSRs on the LSP. configuration commands to each of the LSRs on the LSP.
These commands may utilize SNMP by performing SET These commands may utilize SNMP by performing SET
operations to the MIB module tables and objects described operations to the MIB module tables and objects described
skipping to change at page 22, line 41 skipping to change at page 22, line 41
13.2. ppvpn Working Group MIB Modules 13.2. ppvpn Working Group MIB Modules
At present, the ppvpn working group has not included a At present, the ppvpn working group has not included a
discussion of how the MPLS MIB modules interact with the MIB discussion of how the MPLS MIB modules interact with the MIB
modules being produced by that working group. The authors of modules being produced by that working group. The authors of
this document hope to make a forthcoming addition to the ppvpn this document hope to make a forthcoming addition to the ppvpn
framework document [PPVPNFW] detailing these interactions. framework document [PPVPNFW] detailing these interactions.
At the moment, there are two MIB modules [VPNMIB] and [VPNTCMIB] At the moment, there are two MIB modules [VPNMIB] and [VPNTCMIB]
which are discussed next. which are discussed next.
13.2.1. PPVPN-MPLS-VPN-MIB 13.2.1. PPVPN-MPLS-VPN-STD-MIB
PPVPN-MPLS-VPN-MIB describes managed objects that are used PPVPN-MPLS-VPN-STD-MIB describes managed objects that are used
to model and manage RFC2547bis MPLS VPNs [RFC2547Bis]. to model and manage RFC2547bis MPLS VPNs [RFC2547Bis].
This MIB module contains tables which model virtual routing This MIB module contains tables which model virtual routing
forwarding entries (VRFs), as well as the interfaces forwarding entries (VRFs), as well as the interfaces
associated with those VRFs. associated with those VRFs.
13.2.1.1. Position in the OID Tree 13.2.1.1. Position in the OID Tree
transmission -- RFC 2578 [RFC2578] transmission -- RFC 2578 [RFC2578]
| |
+- vpnMIB -- PPVPN-MPLS-VPN-MIB +- vpnMIB -- PPVPN-MPLS-VPN-STD-MIB
13.2.1.2. Dependencies 13.2.1.2. Dependencies
This MIB module currently has no direct dependencies to any This MIB module currently has no direct dependencies to any
of the MPLS MIB modules. This MIB module models MPLS VPN of the MPLS MIB modules. This MIB module models MPLS VPN
interfaces as entries in the Interfaces MIB's Interfaces interfaces as entries in the Interfaces MIB's Interfaces
Table (ifTable). This MIB module may be modified in the Table (ifTable). This MIB module may be modified in the
future to import textual conventions from MPLS-TC-MIB. future to import textual conventions from MPLS-TC-STD-MIB.
A specific textual conventions MIB module [VPNTCMIB] defines A specific textual conventions MIB module [VPNTCMIB] defines
textual conventions that are imported into PPVPN-MPLS-VPN-MIB. textual conventions that are imported into PPVPN-MPLS-VPN-STD-MIB.
13.3. ccamp Working Group MIB Modules 13.3. ccamp Working Group MIB Modules
The ccamp working group is developing MIB modules in support of The ccamp working group is developing MIB modules in support of
GMPLS that interact directly with the MPLS MIB modules. Along GMPLS that interact directly with the MPLS MIB modules. Along
with any MIB modules produced by the ccamp working group, a with any MIB modules produced by the ccamp working group, a
separate ccamp-specific Management Framework document is expected separate ccamp-specific Management Framework document is expected
to be issued describing the relationship between these MIB to be issued describing the relationship between these MIB
modules and the existing MPLS (and other) MIB modules. modules and the existing MPLS (and other) MIB modules.
14. Traffic Engineering Working Group TE MIB 14. Traffic Engineering Working Group TE MIB
The tewg has produced a traffic engineering MIB (the TE-MIB) The tewg has produced a traffic engineering MIB (the TE-MIB)
[TEWGMIB] containing objects for monitoring traffic engineered [TEWGMIB] containing objects for monitoring traffic engineered
at their ingress points. at their ingress points.
In many senses the TE-MIB contains the same information as In many senses the TE-MIB contains the same information as
MPLS-TE-MIB. Both MIB modules can be used to monitor MPLS MPLS-TE-STD-MIB. Both MIB modules can be used to monitor MPLS
tunnels; however, the TE-MIB is minimalistic and caters best to tunnels; however, the TE-MIB is minimalistic and caters best to
TE tunnels as tunnels, at the expense of not having many advanced TE tunnels as tunnels, at the expense of not having many advanced
features of the MPLS-TE-MIB, whereas the MPLS-TE-MIB can features of the MPLS-TE-STD-MIB, whereas the MPLS-TE-STD-MIB can
deconstruct tunnels into hop-by-hop cross-connects, at the deconstruct tunnels into hop-by-hop cross-connects, at the
expense of more complexity. expense of more complexity.
The TE-MIB module imports textual conventions from the MPLS-TC-MIB The TE-MIB module imports textual conventions from the MPLS-TC-
module and so is dependent on that document. STD-MIB module and so is dependent on that document.
14.1. Choosing Between TE MIB Modules 14.1. Choosing Between TE MIB Modules
The TE-MIB is a flexible MIB module designed to manage traffic The TE-MIB is a flexible MIB module designed to manage traffic
engineering tunnels regardless of the implementation engineering tunnels regardless of the implementation
technology. This flexibility and a focus on simplicity leads technology. This flexibility and a focus on simplicity leads
to some compromises. to some compromises.
- Some MPLS configuration parameters are left out. For example, - Some MPLS configuration parameters are left out. For example,
the resource management in TE-MIB is confined to bandwidth, so the resource management in TE-MIB is confined to bandwidth, so
skipping to change at page 24, line 15 skipping to change at page 24, line 15
- Some of the objects in the TE-MIB are encoded as octet strings. - Some of the objects in the TE-MIB are encoded as octet strings.
Type discrimination is provided by a separate object and it is Type discrimination is provided by a separate object and it is
left to the Management System to decode the octet string for left to the Management System to decode the octet string for
display purposes according to the display hint, and encode the display purposes according to the display hint, and encode the
string in the same way for SET operations. This is in contrast string in the same way for SET operations. This is in contrast
to the MPLS MIB modules which have individual objects with to the MPLS MIB modules which have individual objects with
explicit encodings. explicit encodings.
Extensibility of the TE-MIB to related concepts such as Extensibility of the TE-MIB to related concepts such as
DiffServ and Fast Reroute, and integrations with other MIB DiffServ and Fast Reroute, and integrations with other MIB
modules such as that in the MPLS-LSR-MIB is not a work item modules such as that in the MPLS-LSR-STD-MIB is not a work item
at the time of writing. The MPLS MIB modules are more closely at the time of writing. The MPLS MIB modules are more closely
integrated as described in this document. integrated as described in this document.
Write/create access to the TE-MIB is only available at the ingress, Write/create access to the TE-MIB is only available at the ingress,
where it can be used to configure an ingress to signal a tunnel where it can be used to configure an ingress to signal a tunnel
with constraints. It cannot be used to configure hop-by-hop with constraints. It cannot be used to configure hop-by-hop
cross-connects to build a tunnel. cross-connects to build a tunnel.
15. Security Considerations 15. Security Considerations
skipping to change at page 25, line 53 skipping to change at page 25, line 53
other proprietary rights which may cover technology that may other proprietary rights which may cover technology that may
be required to practice this standard. Please address the be required to practice this standard. Please address the
information to the IETF Executive Director. information to the IETF Executive Director.
18. Normative References 18. Normative References
[FTNMIB] Nadeau, T., Srinivasan, C., and A. [FTNMIB] Nadeau, T., Srinivasan, C., and A.
Viswanathan, "Multiprotocol Label Switching Viswanathan, "Multiprotocol Label Switching
(MPLS) FEC-To-NHLFE (FTN) Management (MPLS) FEC-To-NHLFE (FTN) Management
Information Base", Internet Draft <draft- Information Base", Internet Draft <draft-
ietf-mpls-ftn-mib-05.txt>, November 2002 ietf-mpls-ftn-mib-06.txt>, April 2003
(work in progress). (work in progress).
[LDPMIB] J. Cucchiara, et al., "Definitions of [LDPMIB] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol Switching, Label Distribution Protocol
(LDP)", <draft-ietf-mpls-ldp-mib-09.txt>, (LDP)", <draft-ietf-mpls-ldp-mib-10.txt>,
October 2002 (work in progress). April 2003 (work in progress).
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [LSRMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Label Switching Router Nadeau, "MPLS Label Switching Router
Management Information Base", Internet Management Information Base", Internet
Draft <draft-ietf-mpls-lsr-mib-09.txt>, Draft <draft-ietf-mpls-lsr-mib-09.txt>,
October 2002 (work in progress). October 2002 (work in progress).
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The [RFC2863] McCloghrie, K. and F. Kastenholtz, "The
Interfaces Group MIB ", RFC 2863, June 2000. Interfaces Group MIB ", RFC 2863, June 2000.
[TCMIB] Nadeau, T., Cucchiara, J., (Editors) [TCMIB] Nadeau, T., Cucchiara, J., (Editors)
"Definitions of Textual Conventions for "Definitions of Textual Conventions for
Multiprotocol Label Switching (MPLS) Multiprotocol Label Switching (MPLS)
Management", Internet Draft <draft-ietf- Management", Internet Draft <draft-ietf-
mpls-tc-mib-06.txt>, March 2003 (work in mpls-tc-mib-06.txt>, March 2003 (work in
progress). progress).
[TELMIB] Dubuc, M., Dharanikota, S., Nadeau, T., J. [TELMIB] Dubuc, M., Dharanikota, S., Nadeau, T., J.
Lang, "Traffic Engineering Management Lang, "Traffic Engineering Management
Information Base", Internet Draft <draft- Information Base", Internet Draft <draft-
ietf-mpls-telink-mib-00.txt>, April 2003 ietf-mpls-telink-mib-02.txt>, May 2003
(work in progress). (work in progress).
[TEMIB] Srinivasan, C., Viswanathan, A. and T. [TEMIB] Srinivasan, C., Viswanathan, A. and T.
Nadeau, "MPLS Traffic Engineering Management Nadeau, "MPLS Traffic Engineering Management
Information Base Using SMIv2", Internet Information Base Using SMIv2", Internet
Draft <draft-ietf-mpls-te-mib-09.txt>, Draft <draft-ietf-mpls-te-mib-09.txt>,
November 2002 (work in progress). November 2002 (work in progress).
19. Informative References 19. Informative References
 End of changes. 

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