draft-ietf-mpls-tp-te-mib-07.txt   draft-ietf-mpls-tp-te-mib-08.txt 
Network Working Group Network Working Group
INTERNET-DRAFT M.Venkatesan INTERNET-DRAFT M.Venkatesan
Intended Status: Standards Track Dell Inc. Intended Status: Standards Track Dell Inc.
Expires: May 08, 2014 Kannan KV Sampath Expires: November 7, 2014 Kannan KV Sampath
Redeem Redeem
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Brocade
November 04, 2013 May 6, 2014
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-07.txt draft-ietf-mpls-tp-te-mib-08.txt
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects of Tunnels, Identifiers, In particular, it describes additional managed objects of Tunnels,
Label Switching Router and Textual conventions for Multiprotocol Identifiers, Label Switching Router and Textual conventions to
Label Switching (MPLS) based Transport Profile (TP). support Multiprotocol Label Switching (MPLS) MIB modules for
transport networks.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 47 skipping to change at page 1, line 48
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work 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.
This Internet-Draft will expire on May 08, 2014. This Internet-Draft will expire on November 7, 2014.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. The Internet-Standard Management Framework . . . . . . . . . . 4 2. The Internet-Standard Management Framework . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Conventions used in this document . . . . . . . . . . . . . 4 3.1. Conventions used in this document . . . . . . . . . . . . . 4
3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Brief description of MPLS-TE-EXT-STD-MIB Objects . . . . . . . 7 6. Brief description of MIB modules . . . . . . . . . . . . . . . 7
6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7
6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8
6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8
6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 8 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9
6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 8 6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9
6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9
6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9
7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 10
9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 11
9.1. Example of MPLS-TP static co-routed bidirectional tunnel 9.1. Example of MPLS-TP static co-routed bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 12 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 13
9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13
9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14
9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14
9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 14 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 15
9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15
9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15
9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15
9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 15
9.2. Example of MPLS-TP static associated bidirectional tunnel 9.2. Example of MPLS-TP static associated bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16
9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17
9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17
9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17
9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18
9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18
9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19
9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19
9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19
9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20
9.3. Example of MPLS-TP signaled co-routed bidirectional
tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 20
9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20
9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21
9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 21 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 22
9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 22
9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22
9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22
9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22
9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22
9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 22
10. MPLS Textual Convention Extension MIB definitions . . . . . . 22 10. MPLS Textual Convention Extension MIB definitions . . . . . . 22
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 55 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 56 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 54
15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 57 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 54
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 57 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 54
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 57 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55
16.1. Normative References . . . . . . . . . . . . . . . . . . . 57 16.1. Normative References . . . . . . . . . . . . . . . . . . . 55
16.2. Informative References . . . . . . . . . . . . . . . . . 57 16.2. Informative References . . . . . . . . . . . . . . . . . 55
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 58 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 56
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects of Tunnels, Identifiers, Label particular, it describes additional managed objects of Tunnels,
Switching Router and Textual conventions for Multiprotocol Label Identifiers, Label Switching Router and Textual conventions to support
Switching (MPLS) based Transport Profile (TP). These MIB modules extend Multiprotocol Label Switching (MPLS) MIB modules for transport networks.
the existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP MIB modules defined in this document extends the existing MPLS MIB
operations, so the MPLS-TP name is not included in the MIB module name. objects in such a way that they support MPLS-TP and Non-MPLS-TP networks
as well. Hence, the MPLS-TP name is not included in the MIB module name.
The existing Multiprotocol Label Switching (MPLS) Traffic Engineering The existing MPLS Traffic Engineering (TE) Management Information Base
(TE) Management Information Base (MIB) [RFC3812] and Generalized (MIB) [RFC3812] and Generalized Multiprotocol Label Switching (GMPLS)
Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Traffic Engineering Management Information Base [RFC4802] do not support
Information Base [RFC4802] do not support the transport network the management of transport network requirements of Tunnel end points
requirements of NON-IP based management and static bidirectional with non-IP based identifiers and static bidirectional tunnels. This
tunnels. These MIB modules should be used in conjunction with [RFC3812] document focuses on static bidirectional MIB modules that should be used
and companion document [RFC3813] for MPLS-TP tunnel configuration and in conjunction with [RFC3812] and companion document [RFC3813] for MPLS
management. Transport Profile (MPLS-TP) path configuration and management.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", It is understood that SNMP SET is not used for MPLS configuration these
"SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be days, however the read-write and read-create option is still specified
interpreted as described in BCP 14, RFC2119. for some objects as a way to provide the information model.
2. The Internet-Standard Management Framework 2. The Internet-Standard 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
RFC3410 [RFC3410]. 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. MIB objects are generally accessed Management Information Base or MIB. MIB objects are generally accessed
through the Simple Network Management Protocol (SNMP). Objects in the through the Simple Network Management Protocol (SNMP). Objects in the
MIB are defined using the mechanisms defined in the Structure of MIB are defined using the mechanisms defined in the Structure of
Management Information (SMI). This memo specifies a MIB module that is Management Information (SMI). This memo specifies a MIB module that is
compliant to the SMIv2, which is described in STD 58, RFC2578, STD 58, compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58
RFC2579 and STD58, RFC2580. [RFC2579] and STD 58 [RFC2580].
3. Overview 3. Overview
3.1. Conventions used in this document 3.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3.2. Terminology 3.2. Terminology
This document uses terminology from the Multiprotocol Label Switching This document uses terminology from the Multiprotocol Label Switching
Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB) [RFC3812], Engineering (TE) Management Information Base (MIB) [RFC3812],
Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Multiprotocol Label Switching (MPLS) Label Switching Router (LSR)
Management Information Base (MIB) [RFC3813] and MPLS Transport Profile Management Information Base (MIB) [RFC3813] and MPLS Transport Profile
(MPLS-TP) Identifiers [RFC6370]. (MPLS-TP) Identifiers [RFC6370].
3.3. Acronyms 3.3. Acronyms
CC: Country Code CC: Country Code
GMPLS: Generalized Multi-Protocol Label Switching
ICC: ITU Carrier Code ICC: ITU Carrier Code
IP: Internet Protocol
ITU: International Telecommunication Union
ITU-T: ITU Telecommunication Standardization Sector
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base
MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
OSPF: Open Shortest Path First
PW: Pseudowire
TE: Traffic Engineering TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
4. Motivations 4. Motivations
Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management
Information Base (MIB) [RFC3812] provides support for Traffic Information Base (MIB) [RFC3812] provides support for Traffic
Engineering tunnels. However, with MPLS-TP, the characteristics of Engineering tunnels. However, with MPLS-TP, the characteristics of
Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in Tunnels were enhanced. In MPLS, the actual transport of packets is
nature and could be used in non-IP environments. As the existing MPLS- provided by Label Switched Paths (LSPs). A transport service may be
TE-STD-MIB is not sufficient to capture all the characteristics of the composed of multiple LSPs. In order to clearly identify the service, as
tunnels, enhancing the MIB to support MPLS TP tunnels is required. As defined in [RFC6370], we use the term "MPLS-TP Tunnel" or simply
most of the attributes of MPLS Traffic Engineering tunnels are also "tunnel" For example, MPLS-TP tunnels, are bidirectional in nature and
applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB could be used with non-IP identifiers for the tunnel end points. As the
definition instead of a new MIB. existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to
support unidirectional tunnel and signaled co-routed bidirectional
tunnel definitions respectively, these existing MIBs are not sufficient
to capture all the characteristics of the tunnels. Hence, enhancing the
MIB modules to support MPLS TP tunnels is required. As most of the
attributes of MPLS Traffic Engineering tunnels are also applicable to
MPLS-TP tunnels, it is optimal to re-use the existing MIB definition
instead of a defining a new MIB.
This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB, This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB,
MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these
new MIB modules are required for MPLS-TP functionality, these are new MIB modules are required for MPLS-TP functionality, these are
retained in the same document, instead of a separate document. retained in the same document, instead of a separate document.
5. Feature List 5. Feature List
The MPLS-TE-EXT-STD-MIB is designed to satisfy the following This document identifies the following requirements and constraints:
requirements and constraints:
The MIB module supports static and signaling point-to-point, co-routed The MIB module supports static and signaled point-to-point, co-routed
bi-directional and associated bi-directional tunnels. bi-directional and associated bi-directional tunnels.
- The MPLS tunnels need not be interfaces, but it is possible - The MPLS tunnels need not be interfaces, but it is possible
to configure a TP tunnel as an interface. to configure an MPLS TP tunnel as an interface.
- The mplsTunnelTable [RFC3812] to be also used for MPLS-TP - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP
tunnels tunnels
- The mplsTunnelTable is extended to support MPLS-TP specific - New MPLS-TP specific textual conventions and identifiers
objects.
- The mplsTunnelTable is sparsely extended to support MPLS-TP
tunnel specific objects.
- A node configuration table (mplsTunnelExtNodeConfigTable) - A node configuration table (mplsTunnelExtNodeConfigTable)
is used to translate the Global_ID::Node_ID or is used to translate the Global_ID::Node_ID or
ICC_Operator_ID::Node_ID to the local identifier in order ICC_Operator_ID::Node_ID to the local identifier in order
to index mplsTunnelTable. to index mplsTunnelTable.
- The mplsXCTable is sparsely extended to support MPLS-TP
XC(Cross Connect) specific objects.
- The MIB module supports persistent, as well as non-persistent - The MIB module supports persistent, as well as non-persistent
tunnels. tunnels.
6. Brief description of MPLS-TE-EXT-STD-MIB Objects 6. Brief description of MIB modules
The objects described in this section support the functionality This section describes the MIB modules present in this document. The
described in documents [RFC5654] and [RFC6370]. The tables support tables and MIB modules that are mentioned in the below subsections
both IP compatible and ICC based tunnel configurations. support the functionality described in documents [RFC5654] and
[RFC6370]. The tables support both IP compatible and ICC based
tunnel configurations.
The below diagram depicts how the table references are followed in
this MIB.
Tunnel1-->XC1<--------------
^ ^ | | |
| | | |-->InSeg1 |
| | | |-->OutSeg1 |
| | v |
| ------XCext1 |
| | |
V v |
Tunnel2-->XC1 |
^ | | |
| | |-->InSeg2 |
| | |-->OutSeg2 |
| v |
------XCext2------------
6.1. mplsTunnelExtNodeConfigTable 6.1. mplsTunnelExtNodeConfigTable
The mplsTunnelExtNodeConfigTable is used to assign a local identifier The mplsTunnelExtNodeConfigTable is used to assign a local identifier
for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID
combination as defined in [RFC6923] and [RFC6370] respectively. combination as defined in [RFC6923] and [RFC6370] respectively. The
The CC is a string of two alphabetic characters represented with CC is a string of two alphabetic characters represented with upper
upper case letters (i.e., A-Z). The ICC is a string of one to six case letters (i.e., A-Z). The ICC is a string of one to six
characters, each character being either alphabetic (i.e. A-Z) characters, each character being either alphabetic (i.e. A-Z) or
or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC numeric (i.e. 0-9) characters. Alphabetic characters in the ICC
should be represented with upper case letters. In the IP compatible should be represented with upper case letters. In the IP compatible
mode, Global_ID::Node_ID, is used to uniquely identify a node. mode, Global_ID::Node_ID, is used to uniquely identify a node. For
each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a
Each ICC_Operator_ID::Node_ID or Global_ID::Node_ID contains one
unique entry in the table representing a node. Every node is assigned unique entry in the table representing a node. Every node is assigned
a local identifier within a range of 0 to 16777215. This local a local identifier within a range of 0 to 16777215. This local
identifier is used for indexing into mplsTunnelTable as identifier is used for indexing into mplsTunnelTable as
mplsTunnelIngressLSRId and mplsTunnelEgressLSRId. mplsTunnelIngressLSRId and mplsTunnelEgressLSRId.
For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel
Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination
Global_ID and Destination Node_ID. Global_ID and Destination Node_ID.
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,
skipping to change at page 8, line 15 skipping to change at page 8, line 38
used directly. used directly.
The mplsTunnelExtNodeConfigTable will be used to store an entry for The mplsTunnelExtNodeConfigTable will be used to store an entry for
ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local
identifier to be used as LSR ID in mplsTunnelTable. As the regular TE identifier to be used as LSR ID in mplsTunnelTable. As the regular TE
tunnels use IP address as LSR ID, the local identifier should be tunnels use IP address as LSR ID, the local identifier should be
below the first valid IP address, which is 16777216[1.0.0.0]. below the first valid IP address, which is 16777216[1.0.0.0].
6.2. mplsTunnelExtNodeIpMapTable 6.2. mplsTunnelExtNodeIpMapTable
The read-only mplsTunnelExtNodeIpMaptable is used to query the local The read-only mplsTunnelExtNodeIpMapTable is used to query the local
identifier assigned and stored in mplsTunnelExtNodeConfigTable for identifier assigned and stored in mplsTunnelExtNodeConfigTable for
a given Global_ID::Node_ID. In order to query the local identifier, a given Global_ID::Node_ID. In order to query the local identifier,
in the IP compatible mode, this table is indexed with in the IP compatible mode, this table is indexed with
Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, Global_ID::Node_ID. In the IP compatible mode for a TP tunnel,
Global_ID::Node_ID is used. Global_ID::Node_ID is used.
A separate query is made to get the local identifier of both A separate query is made to get the local identifier of both
Ingress and Egress Global_ID::Node_ID identifiers. These local Ingress and Egress Global_ID::Node_ID identifiers. These local
identifiers are used as mplsTunnelIngressLSRId and identifiers are used as mplsTunnelIngressLSRId and
mplsTunnelEgressLSRId, while indexing mplsTunnelTable. mplsTunnelEgressLSRId, while indexing mplsTunnelTable.
skipping to change at page 8, line 40 skipping to change at page 9, line 15
identifier assigned and stored in the mplsTunnelExtNodeConfigTable identifier assigned and stored in the mplsTunnelExtNodeConfigTable
for a given ICC_Operator_ID::Node_ID. for a given ICC_Operator_ID::Node_ID.
A separate query is made to get the local identifier of both A separate query is made to get the local identifier of both
Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers
are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId,
while indexing mplsTunnelTable. while indexing mplsTunnelTable.
6.4. mplsTunnelExtTable 6.4. mplsTunnelExtTable
mplsTunnelExtTable extends the mplsTunnelTable in order to support This table sparsely extends the mplsTunnelTable in order to support
MPLS-TP tunnels with additional objects. All the additional MPLS-TP tunnels with additional objects. All the additional
attributes specific to supporting TP tunnel are contained in this attributes specific to supporting TP tunnel are contained in this
extended table and could be accessed with the mplsTunnelTable extended table and could be accessed with the mplsTunnelTable
indices. indices.
6.5. mplsTunnelExtReversePerfTable 6.5 MPLS-TC-EXT-STD-MIB
This table sparse augments the mplsTunnelTable to provide per-tunnel This MIB module contains Textual Conventions for LSPs of MPLS based
packet performance information for the reverse direction of a transport networks.
bidirectional tunnel. It can be seen as supplementing the
mplsTunnelPerfTable, which augments the mplsTunnelTable. 6.6 MPLS-ID-STD-MIB
This MIB module contains generic object definitions for MPLS Traffic
Engineering in transport networks.
6.7 MPLS-LSR-EXT-STD-MIB
This MIB module contains generic object definitions for MPLS LSR in
transport networks.
7. MIB Module Interdependencies 7. MIB Module Interdependencies
This section provides an overview of the relationship between the This section provides an overview of the relationship between the
MPLS-TP TE MIB module and other MPLS MIB modules. MPLS-TP TE MIB module and other MPLS MIB modules.
The arrows in the following diagram show a 'depends on' The arrows in the following diagram show a 'depends on'
relationship. A relationship "MIB module A depends on MIB module B" relationship. A relationship "MIB module A depends on MIB module B"
means that MIB module A uses an object, object identifier, or means that MIB module A uses an object, object identifier, or
textual convention defined in MIB module B, or that MIB module A textual convention defined in MIB module B, or that MIB module A
skipping to change at page 10, line 39 skipping to change at page 10, line 39
- MPLS-ID-STD-MIB contains references to objects in - MPLS-ID-STD-MIB contains references to objects in
MPLS-TE-STD-MIB [RFC3812]. MPLS-TE-STD-MIB [RFC3812].
- MPLS-TE-EXT-STD-MIB contains references to objects in - MPLS-TE-EXT-STD-MIB contains references to objects in
MPLS-TE-STD-MIB [RFC3812]. MPLS-TE-STD-MIB [RFC3812].
- MPLS-LSR-EXT-STD-MIB contains references to objects in - MPLS-LSR-EXT-STD-MIB contains references to objects in
MPLS-LSR-STD-MIB [RFC3813]. MPLS-LSR-STD-MIB [RFC3813].
MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB The mplsTunnelExtTable sparsely extends the mplsTunnelTable of
MIB module for associating the reverse direction tunnel MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse
information. direction tunnel information.
Note that the nature of the 'extends' relationship
is a sparse augmentation so that the entry in the
mplsTunnelExtTable has the same index values as the in the
mplsTunnelTable.
MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB The mplsXCExtTable sparsely extends the mplsXCTable of
MIB module for pointing back to the tunnel entry for easy tunnel MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the tunnel
access from XC entry. entry for easy tunnel access from XC entry.
Note that the nature of the 'extends' relationship Note that all of the MIB modules shown above in the figure also
is a sparse augmentation so that the entry in the have a dependency on MPLS-TC-STD-MIB.
mplsXCExtTable has the same index values as the in the mplsXCTable.
8. Dependencies between MIB Module Tables 8. Dependencies between MIB Module Tables
The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram
below. The arrows indicate a reference from one table to another. below. The arrows indicate a reference from one table to another.
mplsTunnelExtNodeConfigTable mplsTunnelExtNodeConfigTable
^ mplsXCExtTable ^ ^ ^
| | ^ | | |
| +---------+ | | | |
| | | | | |
| V V | | +----------------------+
mplsTunnelTable ---->mplsXCTable | | |
^ | mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable
| |
| | mplsXCExtTable
mplsTunnelExtTable | | ^
| +---------+ |
| | |
| | |
| V V
mplsTunnelTable ---->mplsXCTable
^
|
|
|
mplsTunnelExtTable
An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable
table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID
with the local number in order to accommodate in the existing tunnel with the local number in order to accommodate in the existing tunnel
table's ingress/egress LSR-id. table's ingress/egress LSR-id.
New mplsTunnelExtTable table provides the reverse direction LSP New mplsTunnelExtTable table provides the reverse direction LSP
information for the existing tunnel table in order to achieve information for the existing tunnel table in order to achieve
bidirectional LSPs. bidirectional LSPs.
mplsXCExtTable is extended from mplsLsrXCTable to provide mplsXCExtTable sparsely extends the mplsLsrXCTable to provide
backward reference to tunnel entry. backward reference to tunnel entry.
9. Example of MPLS-TP Tunnel Setup 9. Example of MPLS-TP Tunnel Setup
In this section, we provide an example of the IP based MPLS-TP
bidirectional tunnel setup. This example provides the usage of In this section, we provide an example to configure MPLS-TP
MPLS-TP Tunnel MIB along with the extended new MIB modules introduced bidirectional tunnels with IP tunnel identifiers. This example
in this document. provides the usage of MPLS-TP Tunnel MIB along with the extended new
MIB modules introduced in this document.
Do note that a MPLS-TP tunnel could be setup statically as well as Do note that a MPLS-TP tunnel could be setup statically as well as
signaled via control plane. This example considers accessing MIB signaled via control plane. This example considers accessing MIB
objects on a head-end for a static and signaling MPLS-TP tunnels. objects on a head-end for a static and signaled MPLS-TP tunnels. This
Only relevant objects which are applicable for MPLS-TP tunnel are section shows the configuration of the forward and reverse direction
MPLS-TP LSPs that runs between East and West and vice-versa. Only
relevant objects which are applicable for MPLS-TP tunnel are
illustrated here. illustrated here.
In mplsTunnelExtNodeConfigTable: In mplsTunnelExtNodeConfigTable:
{ {
-- Non-IP Ingress LSR-Id (Index to the table) -- Non-IP Ingress LSR-Id (Index to the table)
mplsTunnelExtNodeConfigLocalId = 1, mplsTunnelExtNodeConfigLocalId = 1,
mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 10, mplsTunnelExtNodeConfigNodeId = 10,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelExtNodeConfigRowStatus = createAndGo (4) mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
-- Non-IP Egress LSR-Id (Index to the table) -- Non-IP Egress LSR-Id (Index to the table)
mplsTunnelExtNodeConfigLocalId = 2, mplsTunnelExtNodeConfigLocalId = 2,
mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigGlobalId = 1234,
skipping to change at page 12, line 46 skipping to change at page 13, line 7
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 20, mplsTunnelExtNodeIpMapNodeId = 20,
mplsTunnelExtNodeIpMapLocalId = 2 mplsTunnelExtNodeIpMapLocalId = 2
} }
9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup
The following denotes the configured co-routed bidirectional The following denotes the co-routed bidirectional tunnel "head"
tunnel "head" entry: entry.
9.1.1. mplsTunnelEntry 9.1.1. mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR-Id
skipping to change at page 13, line 43 skipping to change at page 13, line 52
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.1.2. mplsTunnelExtEntry 9.1.2. mplsTunnelExtEntry
-- An MPLS extension table -- An MPLS extension table
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
-- This opposite direction tunnel pointer MAY be point to 0.0 -- This opposite direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel -- if co-routed bidirectional tunnel is managed by single tunnel
-- entry -- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0 mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
We must next create the appropriate in-segment and out-segment We must next create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable and
mplsOutSegmentTable. mplsOutSegmentTable.
9.1.3. Forward direction mplsOutSegmentEntry 9.1.3. Forward direction mplsOutSegmentEntry
For the forward direction. For the forward direction,
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x0000001, mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentRowStatus = createAndGo (4) mplsOutSegmentRowStatus = createAndGo (4)
} }
9.1.4. Reverse direction mplsInSegmentEntry 9.1.4. Reverse direction mplsInSegmentEntry
For the reverse direction. For the reverse direction,
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x0000001 mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
skipping to change at page 15, line 51 skipping to change at page 16, line 14
Next for the reverse direction: Next for the reverse direction:
In mplsXCExtTable (0x01, 0x00000001, 0x00000000) In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
} }
9.1.9. mplsTunnelExtReversePerfTable
The mplsTunnelExtReversePerfTable SHOULD be populated incase
the single tunnel entry is used for co-routed bidirectional tunnel
setup. The mplsTunnelPerfTable will have the forward direction
LSP performance counters and mplsTunnelExtReversePerfTable will have
the reverse direction LSP performance counters.
9.2. Example of MPLS-TP static associated bidirectional tunnel setup 9.2. Example of MPLS-TP static associated bidirectional tunnel setup
The MPLS-TP associated bidirectional tunnel has two different The MPLS-TP associated bidirectional tunnel has two different
direction tunnels[Forward and Reverse LSPs] and these are direction tunnels[Forward and Reverse LSPs] and these are
associated together using mplsTunnelExtTable. Two different associated together using mplsTunnelExtTable. Two different
tunnel entries for both forward and reverse direction MAY be used tunnel entries for both forward and reverse direction MAY be used
for co-routed bidirectional tunnel as well. for co-routed bidirectional tunnel as well.
The following denotes the configured associated bidirectional forward The following denotes the associated bidirectional forward tunnel
tunnel "head" entry: "head" entry:
9.2.1. Forward direction mplsTunnelEntry 9.2.1. Forward direction mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR-Id
skipping to change at page 20, line 25 skipping to change at page 20, line 34
Next for the reverse direction: Next for the reverse direction:
In mplsXCExtTable (0x01, 0x00000001, 0x00000000) In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1
mplsXCExtOppositeDirXCPtr = mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
} }
9.3. Example of MPLS-TP signaling co-routed bidirectional tunnel setup 9.3. Example of MPLS-TP signaled co-routed bidirectional tunnel setup
The following denotes the configured co-routed bidirectional The following denotes the co-routed bidirectional tunnel "head" entry
tunnel "head" entry and in intermediate and tail-end nodes, and in intermediate and tail-end nodes, the tunnel table and its
the tunnel table and its associated tables are created associated tables are created by the local management subsystem
by the local management subsystem (e.g. agent) when the MPLS TP (e.g. agent) when the MPLS TP tunnel is signaled successfully.
tunnel is signaled successfully. Refer [RFC3812] and [RFC4802] Refer [RFC3812] and [RFC4802] for signaled tunnel table
for signaling tunnel table configuration examples. configuration examples.
9.3.1. mplsTunnelEntry 9.3.1. mplsTunnelEntry
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 0, mplsTunnelInstance = 0,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id, for the intermediate and tail-end nodes, -- Ingress LSR-Id, for the intermediate and tail-end nodes,
skipping to change at page 21, line 31 skipping to change at page 21, line 39
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
9.3.2. mplsTunnelExtEntry 9.3.2. mplsTunnelExtEntry
-- An MPLS extension table -- An MPLS extension table
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
-- This opposite direction tunnel pointer MAY be point to 0.0 -- This opposite direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel -- if co-routed bidirectional tunnel is managed by single tunnel
-- entry -- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0 mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE as -- Set both the Ingress and Egress LocalId objects to TRUE as
-- this tunnel entry uses the local identifiers. -- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true, mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true mplsTunnelExtEgressLSRLocalIdValid = true
} }
We must next create the appropriate in-segment and out-segment We must next create the appropriate in-segment and out-segment
skipping to change at page 22, line 39 skipping to change at page 22, line 48
Once the forward path information is negotiated using signaling Once the forward path information is negotiated using signaling
protocol, the forward direction mplsXCExtEntry will be created for protocol, the forward direction mplsXCExtEntry will be created for
associating the opposite direction XC entry and tunnel table entry. associating the opposite direction XC entry and tunnel table entry.
9.3.8. Reverse direction mplsXCExtEntry 9.3.8. Reverse direction mplsXCExtEntry
Once the reverse path information is negotiated using signaling Once the reverse path information is negotiated using signaling
protocol, the reverse direction mplsXCExtEntry will be created for protocol, the reverse direction mplsXCExtEntry will be created for
associating the opposite direction XC entry and tunnel table entry. associating the opposite direction XC entry and tunnel table entry.
9.3.9. mplsTunnelExtReversePerfTable
The mplsTunnelExtReversePerfTable SHOULD be populated incase the
single tunnel entry is used for co-routed bidirectional tunnel setup.
The mplsTunnelPerfTable will have the forward direction LSP
performance counters and mplsTunnelExtReversePerfTable will have the
reverse direction LSP performance counters.
10. MPLS Textual Convention Extension MIB definitions 10. MPLS Textual Convention Extension MIB definitions
MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN
MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32 MODULE-IDENTITY, Unsigned32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
mplsTcExtStdMIB MODULE-IDENTITY mplsTcExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc, Dell Inc,
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com
10 Technology Park Drive,
Westford, MA 01886
Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2014 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains Textual Conventions for This MIB module contains Textual Conventions for LSPs of MPLS
LSPs and PWs of MPLS based transport networks." based transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
DESCRIPTION DESCRIPTION
"MPLS Textual Convention Extensions" "MPLS Textual Convention Extensions"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
MplsGlobalId ::= TEXTUAL-CONVENTION MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the Textual Convention of IP based "This object contains the Textual Convention of IP based
operator unique identifier (Global_ID), the Global_ID can operator unique identifier (Global_ID), the Global_ID can
contain the 2-octet or 4-octet value of the operator's contain the 2-octet or 4-octet value of the operator's
Autonomous System Number (ASN). Autonomous System Number (ASN).
It is expected that the Global_ID will be derived from
the globally unique ASN of the autonomous system hosting
the PEs containing the actual AIIs.
The presence of a Global_ID based on the operator's
ASN ensures that the AII will be globally unique.
When the Global_ID is derived from a 2-octet AS number, When the Global_ID is derived from a 2-octet AS number,
the two high-order octets of this 4-octet identifier the two high-order octets of this 4-octet identifier
MUST be set to zero. MUST be set to zero(0x00). Further ASN 0 is reserved.
Further ASN 0 is reserved. A Global_ID of zero means The size of the Global_ID string MUST be zero if
that no Global_ID is present. Note that a Global_ID of the Global_ID is invalid.
zero is limited to entities contained within a single
operator and MUST NOT be used across an NNI. Note that a Global_ID of zero is limited to entities
A non-zero Global_ID MUST be derived from an ASN owned by contained within a single operator and MUST NOT be used
across an Network-to-Network Interface (NNI). A non-zero
Global_ID MUST be derived from an ASN owned by
the operator." the operator."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370]
Section 3" Section 3"
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
MplsCcId ::= TEXTUAL-CONVENTION MplsCcId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The CC (Country Code) is a string of two alphabetic "The CC (Country Code) is a string of two alphabetic
characters represented with upper case characters represented with upper case
letters (i.e., A-Z)." letters (i.e., A-Z). The size of the CC string MUST be
zero if the CC identifier is invalid."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MplsIccId ::= TEXTUAL-CONVENTION MplsIccId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ICC is a string of one to six characters, each "The ICC is a string of one to six characters, each
character being either alphabetic (i.e. A-Z) or character being either alphabetic (i.e. A-Z) or
numeric (i.e. 0-9) characters. numeric (i.e. 0-9) characters.
Alphabetic characters in the ICC SHOULD be represented Alphabetic characters in the ICC SHOULD be represented
with upper case letters. The size of the ICC string MUST be with upper case letters. The size of the ICC string MUST
zero if the ICC identifier is invalid." be zero if the ICC identifier is invalid."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
SYNTAX OCTET STRING (SIZE (0|1..6)) SYNTAX OCTET STRING (SIZE (0|1..6))
MplsNodeId ::= TEXTUAL-CONVENTION MplsNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Node_ID is assigned within the scope of "The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID. the Global_ID/ICC_Operator_ID.
The value 0(or 0.0.0.0 in dotted decimal notation) is
reserved and MUST NOT be used.
When IPv4 addresses are in use, the value of this object When IPv4 addresses are in use, the value of this object
can be derived from the LSR's IPv4 loop back address. can be derived from the LSR's IPv4 loop back address.
When IPv6 addresses are in use, the value of this object When IPv6 addresses are in use, the value of this object
can be a 32-bit value unique within the scope of can be a 32-bit value unique within the scope of
a Global_ID. a Global_ID.
Note that, when IP reach ability is not needed, the 32-bit Note that, when IP reach ability is not needed, the 32-bit
Node_ID is not required to have any association Node_ID is not required to have any association
with the IPv4 address space." with the IPv4 address space. The value of 0 indicates
the invalid Node identifier."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370]
Section 4" Section 4"
SYNTAX Unsigned32 (0|1..4294967295) SYNTAX Unsigned32 (0|1..4294967295)
-- MPLS-TC-EXT-STD-MIB module ends -- MPLS-TC-EXT-STD-MIB module ends
END END
11. MPLS Identifier MIB definitions 11. MPLS Identifier MIB definitions
skipping to change at page 26, line 9 skipping to change at page 26, line 4
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB FROM MPLS-TC-EXT-STD-MIB
; ;
mplsIdStdMIB MODULE-IDENTITY mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc, Dell Inc,
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com
10 Technology Park Drive,
Westford, MA 01886
Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2014 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
DESCRIPTION DESCRIPTION
"This MIB modules defines the MIB objects for MPLS-TP "This MIB modules defines the MIB objects for MPLS-TP
identifiers" identifiers"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
-- notifications -- notifications
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance -- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects -- MPLS common objects
mplsIdGlobalId OBJECT-TYPE mplsIdGlobalId OBJECT-TYPE
skipping to change at page 27, line 27 skipping to change at page 27, line 18
-- conformance -- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects -- MPLS common objects
mplsIdGlobalId OBJECT-TYPE mplsIdGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId SYNTAX MplsGlobalId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator to assign a unique "This object allows the operator or service provider to
operator identifier also called MPLS-TP Global_ID. assign a unique operator identifier also called MPLS-TP
Global_ID.
If this value is used in mplsTunnelExtNodeConfigGlobalId If this value is used in mplsTunnelExtNodeConfigGlobalId
for mapping Global_ID::Node_ID with the local identifier for mapping Global_ID::Node_ID with the local identifier
then this object value SHOULD NOT be changed." then this object value MUST NOT be changed."
::= { mplsIdObjects 1 } ::= { mplsIdObjects 1 }
mplsIdNodeId OBJECT-TYPE mplsIdNodeId OBJECT-TYPE
SYNTAX MplsNodeId SYNTAX MplsNodeId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
assign a unique MPLS-TP Node_ID. assign a unique MPLS-TP Node_ID. The Node_ID is assigned
within the scope of the Global_ID/ICC_Operator_ID.
The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier for mapping Global_ID::Node_ID with the local identifier
then this object value SHOULD NOT be changed. then this object value SHOULD NOT be changed.
If this value is used in mplsTunnelExtNodeConfigNodeId If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value SHOULD NOT be changed." identifier then this object value MUST NOT be changed."
::= { mplsIdObjects 2 } ::= { mplsIdObjects 2 }
mplsIdCc OBJECT-TYPE mplsIdCc OBJECT-TYPE
SYNTAX MplsCcId SYNTAX MplsCcId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
assign a unique Country Code (CC). Global uniqueness is assign a Country Code (CC) to the node. Global
assured by concatenating the ICC with a uniqueness of ICC is assured by concatenating the ICC
Country Code (CC). with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value SHOULD NOT be changed." identifier then this object value MUST NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
::= { mplsIdObjects 3 } ::= { mplsIdObjects 3 }
mplsIdIcc OBJECT-TYPE mplsIdIcc OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsIccId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a assign a unique MPLS-TP ITU-T Carrier Code (ICC) to
network. Together, the CC and the ICC form the node. Together, the CC and the ICC form
the ICC_Operator_ID as CC::ICC. the ICC_Operator_ID as CC::ICC.
If this value is used in mplsTunnelExtNodeConfigIccId If this value is used in mplsTunnelExtNodeConfigIccId
for mapping ICC_Operator_ID::Node_ID with the local for mapping ICC_Operator_ID::Node_ID with the local
identifier then this object value SHOULD NOT be changed." identifier then this object value MUST NOT be changed."
REFERENCE REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions, "MPLS-TP Identifiers Following ITU-T Conventions,
[RFC6923] Section 3" [RFC6923] Section 3"
::= { mplsIdObjects 4 } ::= { mplsIdObjects 4 }
-- Module compliance. -- Module compliance.
mplsIdCompliances mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 1 } OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdGroups mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 } OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
mplsIdModuleFullCompliance MODULE-COMPLIANCE mplsIdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module." support of the MPLS-ID-STD-MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory group has to be implemented by all -- The mandatory group has to be implemented by all LSRs that
-- LSRs that originate/terminate MPLS-TP paths. -- originate, terminate, or act as transit for MPLS-TP tunnels.
MANDATORY-GROUPS { GROUP mplsIdIpOperatorGroup
mplsIdScalarGroup DESCRIPTION
} "This group is mandatory for devices which support
IP based identifier configuration."
GROUP mplsIdIccOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
ICC based identifier configuration."
::= { mplsIdCompliances 1 } ::= { mplsIdCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that only provide "Compliance statement for agents that only provide
read-only support for the MPLS-ID-STD-MIB module." read-only support for the MPLS-ID-STD-MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { GROUP mplsIdIpOperatorGroup
mplsIdScalarGroup DESCRIPTION
} "This group is mandatory for devices which support
IP based identifier configuration."
GROUP mplsIdIccOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
ICC based identifier configuration."
OBJECT mplsIdGlobalId OBJECT mplsIdGlobalId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsIdNodeId OBJECT mplsIdNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsIdIcc OBJECT mplsIdCc
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsIdCc OBJECT mplsIdIcc
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsIdCompliances 2 } ::= { mplsIdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsIdScalarGroup OBJECT-GROUP mplsIdIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsIdGlobalId, OBJECTS { mplsIdGlobalId,
mplsIdNodeId, mplsIdNodeId
mplsIdIcc, }
mplsIdCc STATUS current
DESCRIPTION
"The objects in this group are optional for ICC based
node."
::= { mplsIdGroups 1 }
} mplsIdIccOperatorGroup OBJECT-GROUP
STATUS current OBJECTS { mplsIdNodeId,
DESCRIPTION mplsIdCc,
"Scalar object needed to implement MPLS TP path." mplsIdIcc
::= { mplsIdGroups 1 }
}
STATUS current
DESCRIPTION
"The objects in this group are optional for IP based
node."
::= { mplsIdGroups 2 }
-- MPLS-ID-STD-MIB module ends -- MPLS-ID-STD-MIB module ends
END END
12. MPLS LSR Extension MIB definitions 12. MPLS LSR Extension MIB definitions
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup mplsXCGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813] FROM MPLS-LSR-STD-MIB; -- [RFC3813]
mplsLsrExtStdMIB MODULE-IDENTITY mplsLsrExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc, Dell Inc,
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com
10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2014 IETF Trust and the persons identified
"Copyright (c) 2013 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS LSR in transport networks." MPLS LSR in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
DESCRIPTION DESCRIPTION
"MPLS LSR specific MIB objects extension" "MPLS LSR specific MIB objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
-- notifications -- notifications
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER mplsLsrExtObjects OBJECT IDENTIFIER
skipping to change at page 32, line 28 skipping to change at page 32, line 36
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 } ::= { mplsLsrExtObjects 1 }
mplsXCExtEntry OBJECT-TYPE mplsXCExtEntry OBJECT-TYPE
SYNTAX MplsXCExtEntry SYNTAX MplsXCExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table extends the cross connect "An entry in this table sparsely extends the cross connect
information represented by an entry in information represented by an entry in
the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through
a sparse augmentation. An entry can be created by a sparse augmentation. An entry can be created by
a network operator via SNMP SET commands, or in a network operator via SNMP SET commands, or in
response to signaling protocol events." response to signaling protocol events."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching "1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsXCIndex, mplsXCInSegmentIndex, INDEX { mplsXCIndex, mplsXCInSegmentIndex,
skipping to change at page 34, line 5 skipping to change at page 34, line 12
TE-LSPs/tunnels. TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, In addition, depending on the type of tunnels supported,
other groups become mandatory as explained below." other groups become mandatory as explained below."
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup mplsLsrNotificationGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsXCExtGroup mplsXCExtGroup
} }
::= { mplsLsrExtCompliances 1 } ::= { mplsLsrExtCompliances 1 }
skipping to change at page 34, line 33 skipping to change at page 34, line 39
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for MPLS-LSR-EXT-STD-MIB. provide read-only support for MPLS-LSR-EXT-STD-MIB.
Such devices can then be monitored but cannot be Such devices can then be monitored but cannot be
configured using this MIB module." configured using this MIB module."
MODULE MPLS-LSR-STD-MIB MODULE MPLS-LSR-STD-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup
mplsPerfGroup
} }
MODULE -- this module MODULE -- this module
GROUP mplsXCExtReadOnlyObjectsGroup GROUP mplsXCExtReadOnlyObjectsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
Opposite direction XC configuration of tunnels." Opposite direction XC configuration of tunnels."
-- mplsXCExtTable -- mplsXCExtTable
skipping to change at page 35, line 46 skipping to change at page 36, line 4
13. MPLS Tunnel Extension MIB definitions 13. MPLS Tunnel Extension MIB definitions
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Counter64, zeroDotZero Counter64, zeroDotZero
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowStatus, RowPointer, StorageType TruthValue, RowStatus, RowPointer, StorageType
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
IndexIntegerNextFree
FROM DIFFSERV-MIB -- [RFC3289]
MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsExtendedTunnelId MplsExtendedTunnelId
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812] FROM MPLS-TE-STD-MIB -- [RFC3812]
; ;
mplsTeExtStdMIB MODULE-IDENTITY mplsTeExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc, Dell Inc,
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Redeem, Redeem,
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Email: tnadeau@lucidvision.com
10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2013 IETF Trust and the persons identified "Copyright (c) 2014 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201311010000Z" -- November 01, 2013 "201405050000Z" -- May 05, 2014
DESCRIPTION DESCRIPTION
"MPLS TE MIB objects extension" "MPLS TE MIB objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced ::= { mplsStdMIB xxx } -- xxx to be replaced
-- with correct value -- with correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- notifications
mplsTeExtNotifications OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 } ::= { mplsTeExtStdMIB 0 }
-- conformance -- conformance
mplsTeExtConformance OBJECT IDENTIFIER mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 2 } ::= { mplsTeExtStdMIB 1 }
-- Start of MPLS Transport Profile Node configuration table -- Start of MPLS Transport Profile Node configuration table
mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..16777215)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelExtNodeConfigLocalId, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelExtNodeConfigLocalId."
::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigTable OBJECT-TYPE mplsTunnelExtNodeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table allows the operator to map a node or "This table allows the operator to map a node or
LSR Identifier (IP compatible [Global_ID::Node_ID] or LSR Identifier (IP compatible [Global_ID::Node_ID] or
ICC based [ICC_Operator_ID::Node_ID]) with a local ICC based [ICC_Operator_ID::Node_ID]) with a local
identifier. identifier.
skipping to change at page 37, line 50 skipping to change at page 38, line 18
Since the MPLS tunnel's Ingress/Egress LSR identifiers' Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for size (Unsigned32) value is not compatible for
MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
with the local identifier of size 4 bytes (Unsigned32) value with the local identifier of size 4 bytes (Unsigned32) value
in order to index (Ingress/Egress LSR identifier) in order to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable." the existing mplsTunnelTable."
::= { mplsTeExtObjects 1 } ::= { mplsTeExtObjects 2 }
mplsTunnelExtNodeConfigEntry OBJECT-TYPE mplsTunnelExtNodeConfigEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeConfigEntry SYNTAX MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping "An entry in this table represents a mapping
identification for the operator or service provider identification for the operator or service provider
with node or LSR. with node or LSR.
skipping to change at page 41, line 45 skipping to change at page 42, line 14
This table MAY be used in on-demand and/or proactive This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR identifier OAM operations to get the Ingress/Egress LSR identifier
(Local Identifier) from Src-Global_Node_ID (Local Identifier) from Src-Global_Node_ID
or Dst-Global_Node_ID and the Ingress and Egress LSR or Dst-Global_Node_ID and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry. identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable." is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 2 } ::= { mplsTeExtObjects 3 }
mplsTunnelExtNodeIpMapEntry OBJECT-TYPE mplsTunnelExtNodeIpMapEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIpMapEntry SYNTAX MplsTunnelExtNodeIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping of "An entry in this table represents a mapping of
Global_ID::Node_ID with the local identifier. Global_ID::Node_ID with the local identifier.
An entry in this table is created automatically when An entry in this table is created automatically when
skipping to change at page 43, line 25 skipping to change at page 43, line 39
the local identifier for a given ICC_Operator_ID::Node_ID the local identifier for a given ICC_Operator_ID::Node_ID
in an ICC operator environment. in an ICC operator environment.
This table MAY be used in on-demand and/or proactive This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR OAM operations to get the Ingress/Egress LSR
identifier (Local Identifier) from Src-ICC identifier (Local Identifier) from Src-ICC
or Dst-ICC and the Ingress and Egress LSR or Dst-ICC and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry. identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable." is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 3 } ::= { mplsTeExtObjects 4 }
mplsTunnelExtNodeIccMapEntry OBJECT-TYPE mplsTunnelExtNodeIccMapEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIccMapEntry SYNTAX MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping of "An entry in this table represents a mapping of
ICC_Operator_ID::Node_ID with the local identifier. ICC_Operator_ID::Node_ID with the local identifier.
An entry in this table is created automatically when An entry in this table is created automatically when
skipping to change at page 45, line 40 skipping to change at page 46, line 8
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance. mplsTunnelInstance.
Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
are maintained in the mplsTunnelExtNodeConfigTable and are maintained in the mplsTunnelExtNodeConfigTable and
mplsTunnelExtNodeConfigLocalId is used to create an entry mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable." in mplsTunnelTable."
REFERENCE REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]."
::= { mplsTeExtObjects 4 } ::= { mplsTeExtObjects 5 }
mplsTunnelExtEntry OBJECT-TYPE mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelExtEntry SYNTAX MplsTunnelExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents MPLS-TP "An entry in this table represents MPLS-TP
specific additional tunnel configurations." specific additional tunnel configurations."
INDEX { INDEX {
mplsTunnelIndex, mplsTunnelIndex,
skipping to change at page 46, line 26 skipping to change at page 46, line 41
mplsTunnelExtIngressLSRLocalIdValid TruthValue, mplsTunnelExtIngressLSRLocalIdValid TruthValue,
mplsTunnelExtEgressLSRLocalIdValid TruthValue mplsTunnelExtEgressLSRLocalIdValid TruthValue
} }
mplsTunnelExtOppositeDirPtr OBJECT-TYPE mplsTunnelExtOppositeDirPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "This object points to the opposite direction tunnel entry."
tunnel that has the forward and reverse LSPs in the ::= { mplsTunnelExtEntry 1 }
same tunnel or in the different tunnels.
This object holds the opposite direction tunnel entry
if the bidirectional tunnel is setup by configuring two
tunnel entries in mplsTunnelTable.
The value of zeroDotZero indicates single tunnel entry
is used for bidirectional tunnel setup."
DEFVAL { zeroDotZero }
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel uses "Denotes whether or not this tunnel uses
mplsTunnelExtOppositeDirPtr for identifying the opposite mplsTunnelExtOppositeDirPtr for identifying the opposite
direction tunnel information. Note that if this variable direction tunnel information. Note that if this variable
is set to true then the mplsTunnelExtOppositeDirPtr should is set to true then the mplsTunnelExtOppositeDirPtr should
point to the first accessible row of the opposite point to the first accessible row of the valid opposite
direction tunnel." direction tunnel."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 2 } ::= { mplsTunnelExtEntry 2 }
mplsTunnelExtDestTnlIndex OBJECT-TYPE mplsTunnelExtDestTnlIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels. different tunnel entries.
This object holds the same value as that of the
mplsTunnelIndex of mplsTunnelEntry if the forward and
reverse LSPs are in the same tunnel. Otherwise,
this object holds the value of the other direction
associated LSP's mplsTunnelIndex from a different
tunnel.
The values of this object and the The values of this object and the
mplsTunnelExtDestTnlLspIndex object together can be used mplsTunnelExtDestTnlLspIndex object together can be used
to identify an opposite direction LSP i.e. if the to identify an opposite direction LSP i.e. if the
mplsTunnelIndex and mplsTunnelInstance hold the value mplsTunnelIndex and mplsTunnelInstance hold the value
for forward LSP, this object and for forward LSP, this object and
mplsTunnelExtDestTnlLspIndex can be used to retrieve mplsTunnelExtDestTnlLspIndex can be used to retrieve
the reverse direction LSP and vice versa. the reverse direction LSP and vice versa.
This object and mplsTunnelExtDestTnlLspIndex values This object and mplsTunnelExtDestTnlLspIndex values
provide the first two indices of tunnel entry and provide the first two indices of tunnel entry and
the remaining indices can be derived as follows, the remaining indices can be derived as follows,
if both the forward and reverse LSPs are present in the Ingress and Egress Identifiers should be
the same tunnel, the opposite direction LSP's Ingress
and Egress Identifier will be same for both the LSPs,
else the Ingress and Egress Identifiers should be
swapped in order to index the other direction tunnel." swapped in order to index the other direction tunnel."
::= { mplsTunnelExtEntry 3 } ::= { mplsTunnelExtEntry 3 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE mplsTunnelExtDestTnlLspIndex OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels. different tunnel entries. This object holds
the instance index of the opposite direction tunnel."
This object should contain different value if both the
forward and reverse LSPs present in the same tunnel.
This object can contain same value or different values
if the forward and reverse LSPs present in the different
tunnels."
::= { mplsTunnelExtEntry 4 } ::= { mplsTunnelExtEntry 4 }
mplsTunnelExtDestTnlValid OBJECT-TYPE mplsTunnelExtDestTnlValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel uses "Denotes whether or not this tunnel uses
mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex for identifying mplsTunnelExtDestTnlLspIndex for identifying
skipping to change at page 49, line 26 skipping to change at page 49, line 13
This object is set to FALSE for legacy implementations like This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelEgressId itself provides MPLS TE tunnels where mplsTunnelEgressId itself provides
complete Egress LSRId." complete Egress LSRId."
REFERENCE REFERENCE
"MPLS-TE-STD-MIB [RFC3812], Section 11. "MPLS-TE-STD-MIB [RFC3812], Section 11.
mplsTunnelEgressLSRId object in mplsTunnelTable." mplsTunnelEgressLSRId object in mplsTunnelTable."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 7 } ::= { mplsTunnelExtEntry 7 }
-- End of MPLS Tunnel table extension -- End of MPLS Tunnel table extension
mplsTunnelExtReversePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table extends the mplsTunnelTable to provide
per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE)Management Information Base (MIB),
RFC 3812."
::= { mplsTeExtObjects 5 }
mplsTunnelExtReversePerfEntry OBJECT-TYPE
SYNTAX MplsTunnelExtReversePerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the LSR for every
bidirectional MPLS tunnel where packets are visible to the
LSR."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtReversePerfTable 1 }
MplsTunnelExtReversePerfEntry ::= SEQUENCE {
mplsTunnelExtReversePerfPackets Counter32,
mplsTunnelExtReversePerfHCPackets Counter64,
mplsTunnelExtReversePerfErrors Counter32,
mplsTunnelExtReversePerfBytes Counter32,
mplsTunnelExtReversePerfHCBytes Counter64
}
mplsTunnelExtReversePerfPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of packets forwarded on the tunnel in the reverse
direction if it is bidirectional.
This object represents the 32-bit value of the least
significant part of the 64-bit value if both
mplsTunnelExtReversePerfHCPackets and this object
are returned."
::= { mplsTunnelExtReversePerfEntry 1 }
mplsTunnelExtReversePerfHCPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High-capacity counter for number of packets forwarded on
the tunnel in the reverse direction if it is
bidirectional."
::= { mplsTunnelExtReversePerfEntry 2 }
mplsTunnelExtReversePerfErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of errored packets received on the tunnel in
the reverse direction if it is bidirectional."
::= { mplsTunnelExtReversePerfEntry 3 }
mplsTunnelExtReversePerfBytes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of bytes forwarded on the tunnel in the reverse
direction if it is bidirectional.
This object represents the 32-bit value of the least
significant part of the 64-bit value if both
mplsTunnelExtReversePerfHCBytes and this object are
returned."
::= { mplsTunnelExtReversePerfEntry 4 }
mplsTunnelExtReversePerfHCBytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High-capacity counter for number of bytes forwarded on the
tunnel in the reverse direction if it is bidirectional."
::= { mplsTunnelExtReversePerfEntry 5 }
-- Module compliance. -- Module compliance.
mplsTeExtCompliances mplsTeExtCompliances
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
mplsTeExtGroups mplsTeExtGroups
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
skipping to change at page 52, line 9 skipping to change at page 49, line 43
-- LSRs that originate/terminate MPLS-TP tunnels. -- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels -- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as -- supported, other groups become mandatory as
-- explained below. -- explained below.
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTunnelExtGroup mplsTunnelExtGroup
} }
GROUP mplsTunnelExtIpOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
configuration of IP based identifier tunnels."
GROUP mplsTunnelExtIccOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
configuration of ICC based tunnels."
::= { mplsTeExtCompliances 1 } ::= { mplsTeExtCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that only provide "Compliance statement for agents that only provide
read-only support for MPLS-TE-EXT-STD-MIB module." read-only support for MPLS-TE-EXT-STD-MIB module."
skipping to change at page 54, line 23 skipping to change at page 52, line 19
-- Units of conformance. -- Units of conformance.
mplsTunnelExtGroup OBJECT-GROUP mplsTunnelExtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsTunnelExtOppositeDirPtr, mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid, mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex, mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex, mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid, mplsTunnelExtDestTnlValid,
mplsTunnelExtIngressLSRLocalIdValid, mplsTunnelExtIngressLSRLocalIdValid,
mplsTunnelExtEgressLSRLocalIdValid, mplsTunnelExtEgressLSRLocalIdValid
mplsTunnelExtReversePerfPackets, }
mplsTunnelExtReversePerfHCPackets,
mplsTunnelExtReversePerfErrors,
mplsTunnelExtReversePerfBytes,
mplsTunnelExtReversePerfHCBytes
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to "Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the implement tunnels. In addition, depending on the
operating environment, the following groups are operating environment, the following groups are
mandatory." mandatory."
::= { mplsTeExtGroups 1 } ::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP mplsTunnelExtIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsTunnelExtNodeConfigGlobalId, OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigGlobalId,
mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeIpMapLocalId, mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus mplsTunnelExtNodeConfigRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement IP compatible tunnels." "Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 } ::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP mplsTunnelExtIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsTunnelExtNodeConfigCcId, OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigCcId,
mplsTunnelExtNodeConfigIccId, mplsTunnelExtNodeConfigIccId,
mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeConfigIccValid, mplsTunnelExtNodeConfigIccValid,
mplsTunnelExtNodeIccMapLocalId, mplsTunnelExtNodeIccMapLocalId,
mplsTunnelExtNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus mplsTunnelExtNodeConfigRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement ICC based tunnels." "Object(s) needed to implement ICC based tunnels."
skipping to change at page 55, line 31 skipping to change at page 53, line 24
14. Security Consideration 14. Security Consideration
It is clear that this MIB module is potentially useful for the It is clear that this MIB module is potentially useful for the
monitoring of MPLS TE tunnels. This MIB module can also be used for monitoring of MPLS TE tunnels. This MIB module can also be used for
the configuration of certain objects, and anything that can be the configuration of certain objects, and anything that can be
configured can be incorrectly configured, with potentially disastrous configured can be incorrectly configured, with potentially disastrous
results. results.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. Such objects may be with a MAX-ACCESS clause of read-write and/or read-create. Such
considered sensitive or vulnerable in some network environments. The objects may be considered sensitive or vulnerable in some network
support for SET operations in a non-secure environment without proper environments. The support for SET operations in a non-secure
protection can have a negative effect on network operations. These environment without proper protection can have a negative effect on
are the tables and objects and their sensitivity/vulnerability: network operations. These are the tables and objects and their
sensitivity/vulnerability:
- the tables specified in [RFC3812], [RFC3813] and this document - the tables specified in [RFC3812], [RFC3813] and this document
MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and
mplsXCExtTable collectively contain objects to provision MPLS-TP mplsXCExtTable collectively contain objects to provision MPLS-TP
tunnels, tunnel hops, and tunnel resources. tunnels, tunnel hops, and tunnel resources.
Unauthorized access to objects in these tables, could result in Unauthorized access to objects in these tables, could result in
disruption of traffic on the network. This is especially true if disruption of traffic on the network. This is especially true if
a tunnel has been established. The use of stronger mechanisms, a tunnel has been established. The use of stronger mechanisms,
such as SNMPv3 security, should be considered where possible. such as SNMPv3 security, should be considered where possible.
Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent
skipping to change at page 56, line 4 skipping to change at page 53, line 47
a tunnel has been established. The use of stronger mechanisms, a tunnel has been established. The use of stronger mechanisms,
such as SNMPv3 security, should be considered where possible. such as SNMPv3 security, should be considered where possible.
Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent
which implements this MIB. Administrators should consider whether which implements this MIB. Administrators should consider whether
read access to these objects should be allowed, since read access read access to these objects should be allowed, since read access
may be undesirable under certain circumstances. may be undesirable under certain circumstances.
Some of the readable objects in this MIB module (i.e., objects Some of the readable objects in this MIB module (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. sensitive or vulnerable in some network environments.
It is thus important to control even GET and/or NOTIFY access to It is thus important to control even GET and/or NOTIFY access to
these objects and possibly to even encrypt the values of these these objects and possibly to even encrypt the values of these
objects when sending them over the network via SNMP. These are objects when sending them over the network via SNMP. These are
the tables and objects and their sensitivity/vulnerability: the tables and objects and their sensitivity/vulnerability:
- the tables specified in [RFC3812], [RFC3813] and this document - the tables specified in [RFC3812], [RFC3813] and this document
MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable,
mplsXCExtTable and mplsTunnelExtReversePerfTable collectively and mplsXCExtTable collectively show the MPLS-TP tunnel network
show the MPLS-TP tunnel network topology and its performance topology characteristics. If an Administrator does not want to
characteristics. If an Administrator does not want to reveal reveal this information, then these tables should be considered
this information, then these tables should be considered
sensitive/vulnerable. sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) allowed to access and GET/SET (read/change/create/delete)
the objects in this MIB module. the objects in this MIB module.
It is recommended that implementers consider the security features as It is recommended that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
skipping to change at page 57, line 41 skipping to change at page 55, line 34
"Textual Conventions for SMIv2", STD 58, RFC 2579, April "Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, January 2001. Label Switching Architecture", RFC 3031, January 2001.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management
Information Base for the Differentiated Services
Architecture", RFC 3289, May 2002.
16.2. Informative References 16.2. Informative References
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
and Applicability Statement for Internet Standard and Applicability Statement for Internet Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, June 2004. Switching (MPLS) Management", RFC 3811, June 2004.
skipping to change at page 58, line 43 skipping to change at page 56, line 41
Transport Profile (MPLS-TP) MIB-Based Management Transport Profile (MPLS-TP) MIB-Based Management
Overview", RFC 6639, June 2012 Overview", RFC 6639, June 2012
[RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP
Identifiers Following ITU-T Conventions", RFC 6923, May Identifiers Following ITU-T Conventions", RFC 6923, May
2013 2013
17. Acknowledgments 17. Acknowledgments
The authors would like to thank Francesco Fondelli, Josh Littlefield, The authors would like to thank Francesco Fondelli, Josh Littlefield,
Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Randy Presuhn for Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn and
their valuable comments. A special thanks to Joan Cucchiara for Adrian Farrel for their valuable comments. A special thanks to Joan
really getting the MIB modules into shape. Cucchiara for really getting the MIB modules into shape.
18. Authors' Addresses 18. Authors' Addresses
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Inc.
350 Holger way, San Jose, CA, USA 5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Brocade
10 Technology Park Drive, Westford, MA 01886 Email: tnadeau@lucidvision.com
Email: tnadeau@juniper.net
Kannan KV Sampath Kannan KV Sampath
Redeem Redeem
India India
Email: kannankvs@gmail.com Email: kannankvs@gmail.com
 End of changes. 141 change blocks. 
420 lines changed or deleted 352 lines changed or added

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