draft-ietf-mpls-tp-te-mib-04.txt   draft-ietf-mpls-tp-te-mib-05.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: January 16, 2013 Kannan KV Sampath Expires: July 18, 2013 Kannan KV Sampath
Aricent Redeem
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
July 15, 2012 January 14, 2013
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-04.txt draft-ietf-mpls-tp-te-mib-05.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 managed objects of Tunnels, Identifiers,
Label Switch Router and Textual conventions for Multiprotocol Label Label Switch Router and Textual conventions for Multiprotocol Label
Switching (MPLS) based Transport Profile (TP). Switching (MPLS) based Transport Profile (TP).
Status of this Memo Status of this Memo
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 January 16, 2013. This Internet-Draft will expire on July 18, 2013.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 Conventions used in this document . . . . . . . . . . . . . 3 3.1. Conventions used in this document . . . . . . . . . . . . . 4
3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 5
6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 5 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 6
6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . 5 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 6
6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 6 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 7
6.4.mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . . 6 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 7
7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 6 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 7
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 8 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 7
9. Example of MPLS-TP tunnel setup . . . . . . . . . . . . . . . . 8 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 9
10. MPLS Textual Convention Extension MIB definitions . . . . . . 13 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 9
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 16 9.1. Example of MPLS-TP static co-routed bidirectional tunnel
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 20 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 24 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 10
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 36 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 11
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 12
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 12
16.1 Normative References . . . . . . . . . . . . . . . . . . . 37 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 12
16.2 Informative References . . . . . . . . . . . . . . . . . . 38 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 13
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 13
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 38 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 13
9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 13
1 Introduction 9.2. Example of MPLS-TP static associated bidirectional tunnel
setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 14
9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 15
9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 15
9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 15
9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 16
9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 16
9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 17
9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 17
9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 17
9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 18
9.3. Example of MPLS-TP signaling co-routed bidirectional
tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 18
9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 18
9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 19
9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 19
9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 19
9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 20
9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20
9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 20
9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20
9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 20
10. MPLS Textual Convention Extension MIB definitions . . . . . . 20
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 23
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 27
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 31
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 49
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
16.1. Normative References . . . . . . . . . . . . . . . . . . . 50
16.2. Informative References . . . . . . . . . . . . . . . . . 50
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 51
This memo defines a portion of the Management Information Base (MIB) 1. Introduction
for use with network management protocols in the Internet community.
In particular, it describes managed objects of Tunnels, Identifiers,
Label Switch Router and Textual conventions for Multiprotocol Label
Switching (MPLS) based Transport Profile (TP).
The existing MPLS TE [RFC3812] and GMPLS MIBs [RFC4802] do not This memo defines a portion of the Management Information Base (MIB) for
support the transport network requirements of NON-IP based management use with network management protocols in the Internet community. In
and static bidirectional tunnels. This MIB module should be used in particular, it describes managed objects of Tunnels, Identifiers, Label
conjunction with the MPLS traffic Engineering MIB [RFC3812] and Switch Router and Textual conventions for Multiprotocol Label Switching
companion document MPLS Label Switch Router MIB [RFC3813] for MPLS (MPLS) based Transport Profile (TP). This draft extends the existing
based traffic engineering configuration and management. MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, so the
MPLS-TP name is not included in the MIB module name.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The existing Multiprotocol Label Switching (MPLS) Traffic Engineering
"SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to (TE) Management Information Base (MIB) [RFC3812] and Generalized
be interpreted as described in BCP 14, RFC2119. Multiprotocol Label Switching (GMPLS) Traffic Engineering Management
Information Base [RFC4802] do not support the transport network
requirements of NON-IP based management and static bidirectional
tunnels. This MIB module should be used in conjunction with [RFC3812]
and companion document [RFC3813] for MPLS based traffic engineering
configuration and management.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in BCP 14, RFC2119.
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
RFC3410 [RFC3410]. RFC3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed the
the Management Information Base or MIB. MIB objects are generally Management Information Base or MIB. MIB objects are generally accessed
accessed through the Simple Network Management Protocol (SNMP). through the Simple Network Management Protocol (SNMP). Objects in the
Objects in the MIB are defined using the mechanisms defined in the MIB are defined using the mechanisms defined in the Structure of
Structure of Management Information (SMI). This memo specifies a MIB Management Information (SMI). This memo specifies a MIB module that is
module that is compliant to the SMIv2, which is described in STD 58, compliant to the SMIv2, which is described in STD 58, RFC2578, STD 58,
RFC2578, STD 58, RFC2579 and STD58, RFC2580. RFC2579 and STD58, 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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3.2 Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
This document uses terminology from the MPLS architecture document 3.2. Terminology
[RFC3031], MPLS Traffic Engineering Management information [RFC3812], This document uses terminology from the Multiprotocol Label Switching
MPLS Label Switch Router MIB [RFC3813] and MPLS-TP Identifiers Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic
document [RFC6370]. Engineering (TE) Management Information Base (MIB) [RFC3812],
Multiprotocol Label Switching (MPLS) Label Switching Router (LSR)
Management Information Base (MIB) [RFC3813] and MPLS Transport Profile
(MPLS-TP) Identifiers [RFC6370].
3.3 Acronyms 3.3. Acronyms
GMPLS: Generalized Multi-Protocol Label Switching GMPLS: Generalized Multi-Protocol Label Switching
ICC: ITU Carrier Code ICC: ITU Carrier Code
IP: Internet Protocol IP: Internet Protocol
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
MPLS: Multi-Protocol Label Switching MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
OSPF: Open Shortest Path First OSPF: Open Shortest Path First
PW: Pseudowire PW: Pseudowire
TE: Traffic Engineering TE: Traffic Engineering
TP: Transport Profile TP: Transport Profile
4. Motivations 4. Motivations
This document provide extensions to existing MPLS MIB modules in Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management
order to support configuration of MPLS-TP tunnels in IP and NON-IP Information Base (MIB) [RFC3812] provides support for Traffic
environments. Engineering tunnels. However, with MPLS-TP, the characteristics of
Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in
nature and could be used in non-IP environment. As the existing MPLS-TE-
STD-MIB is not sufficient to capture all the characteristics of the
tunnels, enhancing the MIB 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 new MIB.
This MIB also defines three other MIB modules within this document. As
these new MIB modules are small in size, MPLS-TC-EXT-STD-MIB, MPLS-ID-
STD-MIB and MPLS-LSR-EXT-STD-MIB are retained in the same document,
instead of a separate document.
5. Feature List 5. Feature List
The MPLS transport profile MIB module is designed to satisfy the The MPLS transport profile MIB module is designed to satisfy the
following requirements and constraints: following requirements and constraints:
The MIB module supports point-to-point, co-routed bi-directional The MIB module supports static and signaling point-to-point, co-routed
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 a 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 - The mplsTunnelTable is extended to support MPLS-TP specific
objects. objects.
skipping to change at page 5, line 4 skipping to change at page 7, line 14
objects. objects.
- A node configuration table (mplsTunnelExtNodeConfigTable) - A node configuration table (mplsTunnelExtNodeConfigTable)
is used to translate the Global_Node_ID or ICC to the local is used to translate the Global_Node_ID or ICC to the local
identifier in order to index mplsTunnelTable. identifier in order to index mplsTunnelTable.
- 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 MIB Objects 6. Brief description of MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in documents [RFC5654] and [RFC6370]. The tables support described in documents [RFC5654] and [RFC6370]. The tables support
both IP compatible and ICC based tunnel configurations. both IP compatible and ICC based tunnel configurations.
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 or Global_Node_ID combination as defined in for a given ICC or Global_Node_ID combination as defined in
[RFC6370]. An ICC is a string of one to six characters, each [RFC6370]. An ICC is a string of one to six characters, each
character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9)
characters. Alphabetic characters in the ICC should be represented characters. Alphabetic characters in the ICC should be represented
with upper case letters. In the IP compatible mode, with upper case letters. In the IP compatible mode,
Global_Node_ID, is used to uniquely identify a node. Global_Node_ID, is used to uniquely identify a node.
Each ICC or Global_Node_ID contains one unique entry in the Each ICC or Global_Node_ID contains one unique entry in the
skipping to change at page 5, line 37 skipping to change at page 7, line 48
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,
Tunnel Instance, Source ICC and Destination ICC. Tunnel Instance, Source ICC and Destination ICC.
As mplsTunnelTable is indexed by mplsTunnelIndex, As mplsTunnelTable is indexed by mplsTunnelIndex,
mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelInstance, mplsTunnelIngressLSRId, and
mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be
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 or Global_Node_ID with a local identifier to be used as LSR ID ICC or Global_Node_ID with a local identifier to be used as LSR ID in
in mplsTunnelTable. As the regular TE tunnels use IP address as LSR mplsTunnelTable. As the regular TE tunnels use IP address as LSR ID,
ID, the local identifier should be below the first valid IP address, the local identifier should be below the first valid IP address,
which is 16777216[1.0.0.0]. 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_Node_ID. In order to query the local identifier, a given Global_Node_ID. In order to query the local identifier,
in the IP compatible mode, this table is indexed with Global_Node_ID. in the IP compatible mode, this table is indexed with Global_Node_ID.
In the IP compatible mode for a TP tunnel, Global_Node_ID In the IP compatible mode for a TP tunnel, Global_Node_ID
is used. 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_Node_ID identifiers. These local Ingress and Egress Global_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.
6.3. mplsTunnelExtNodeIccMapTable 6.3. mplsTunnelExtNodeIccMapTable
The read-only mplsTunnelExtNodeIccMapTable is used to query the local The read-only mplsTunnelExtNodeIccMapTable is used to query the local
identifier assigned and stored in the mplsTunnelExtNodeConfigTable identifier assigned and stored in the mplsTunnelExtNodeConfigTable
for a given ICC. for a given ICC.
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. These local identifiers are used as Ingress and Egress ICC. These local identifiers are used as
mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, mplsTunnelIngressLSRId and mplsTunnelEgressLSRId,
while indexing mplsTunnelTable. while indexing mplsTunnelTable.
6.4.mplsTunnelExtTable 6.4. mplsTunnelExtTable
mplsTunnelExtTable extends the mplsTunnelTable to add MPLS-TP tunnel mplsTunnelExtTable extends the mplsTunnelTable in order to support
specific additional objects. All the additional attributes specific MPLS-TP tunnels with additional objects. All the additional
to TP tunnel are contained in this extended table and could be attributes specific to supporting TP tunnel are contained in this
accessed with the mplsTunnelTable indices. extended table and could be accessed with the mplsTunnelTable
indices.
6.5 mplsTunnelExtReversePerfTable 6.5. mplsTunnelExtReversePerfTable
This table augments the mplsTunnelTable to provide per-tunnel packet This table augments the mplsTunnelTable to provide per-tunnel packet
performance information for the reverse direction of a bidirectional performance information for the reverse direction of a bidirectional
tunnel. It can be seen as supplementing the mplsTunnelPerfTable, tunnel. It can be seen as supplementing the mplsTunnelPerfTable,
which augments the mplsTunnelTable. which augments the mplsTunnelTable.
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.
skipping to change at page 8, line 44 skipping to change at page 11, line 44
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 In this section, we provide an example of the IP based MPLS-TP
bidirectional tunnel setup. This example provides the usage of bidirectional tunnel setup. This example provides the usage of
MPLS-TP Tunnel MIB along with the extended new MIB modules introduced MPLS-TP Tunnel MIB along with the extended new MIB modules introduced
in this document. 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 MPLS-TP tunnel. objects on a head-end for a static and signaling MPLS-TP tunnels.
Only relevant objects which are applicable for MPLS-TP tunnel are 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,
skipping to change at page 9, line 44 skipping to change at page 12, line 44
mplsTunnelExtNodeIpMapNodeId = 10, mplsTunnelExtNodeIpMapNodeId = 10,
mplsTunnelExtNodeIpMapLocalId = 1 mplsTunnelExtNodeIpMapLocalId = 1
-- 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 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 configured co-routed bidirectional
tunnel "head" entry: tunnel "head" 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
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
skipping to change at page 10, line 38 skipping to change at page 13, line 38
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
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 be 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
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = 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 entries. These are done in [RFC3813] using the mplsInSegmentTable and
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,
mplsInSegmentRowStatus = createAndGo (4) mplsInSegmentRowStatus = createAndGo (4)
} }
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
9.1.5 Forward direction mplsXCEntry 9.1.5. Forward direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000, mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
9.1.6 Reverse direction mplsXCEntry 9.1.6. Reverse direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001, mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000, mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
This table entry is extended by entry in the This table entry is extended by entry in the
mplsXCExtTable. Note that the nature of the 'extends' mplsXCExtTable. Note that the nature of the 'extends'
relationship is a sparse augmentation so that the entry in the relationship is a sparse augmentation so that the entry in the
mplsXCExtTable has the same index values as the entry in mplsXCExtTable has the same index values as the entry in
the mplsXCTable. the mplsXCTable.
9.1.5 Forward direction mplsXCExtEntry 9.1.7. Forward direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001) In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{ {
-- 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.4.0.0.0.1.1.0 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
} }
9.1.6 Reverse direction mplsXCExtEntry 9.1.8. Reverse direction mplsXCExtEntry
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.7 mplsTunnelExtReversePerfTable 9.1.9. mplsTunnelExtReversePerfTable
The mplsTunnelExtReversePerfTable SHOULD be populated incase The mplsTunnelExtReversePerfTable SHOULD be populated incase
the single tunnel entry is used for co-routed bidirectional tunnel the single tunnel entry is used for co-routed bidirectional tunnel
setup. The mplsTunnelPerfTable will have the forward direction setup. The mplsTunnelPerfTable will have the forward direction
LSP performance counters and mplsTunnelExtReversePerfTable will have LSP performance counters and mplsTunnelExtReversePerfTable will have
the reverse direction LSP performance counters. the reverse direction LSP performance counters.
9.2 Example of MPLS-TP 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 The following denotes the configured associated bidirectional forward
forward tunnel "head" entry: tunnel "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
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
skipping to change at page 14, line 4 skipping to change at page 17, line 7
mplsTunnelSessionAttributes = 0, mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0), mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
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.2.2 Forward direction mplsTunnelExtEntry 9.2.2. Forward direction mplsTunnelExtEntry
For Associated bidirectional forward LSP, For Associated bidirectional forward LSP,
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
mplsTunnelExtOppositeDirPtr.1.1.1.2 = mplsTunnelName.2.1.2.1 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1
-- Set both the Ingress and Egress LocalId objects to TRUE as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
} }
9.2.3 Forward direction mplsOutSegmentTable 9.2.3. Forward direction mplsOutSegmentTable
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.2.4 Forward direction mplsXCEntry 9.2.4. Forward direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000, mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
9.2.5 Forward direction mplsXCExtEntry 9.2.5. Forward direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001) In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{ {
-- 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.4.0.0.0.1.1.0 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
} }
9.2.6 Forward direction mplsTunnelEntry 9.2.6. Reverse direction mplsTunnelEntry
The following denotes the configured associated bidirectional The following denotes the configured associated bidirectional reverse
reverse tunnel "tail" entry: tunnel "tail" entry:
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 2, mplsTunnelIndex = 2,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id -- Ingress LSR-Id
mplsTunnelIngressLSRId = 2, mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsTunnelExtNodeConfigTable for -- Local map number created in mplsTunnelExtNodeConfigTable for
skipping to change at page 15, line 49 skipping to change at page 19, line 7
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1, mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
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.2.7 Reverse direction mplsTunnelExtEntry 9.2.7. Reverse direction mplsTunnelExtEntry
For Associated bidirectional reverse LSP, For Associated bidirectional reverse LSP,
In mplsTunnelExtTable: In mplsTunnelExtTable:
{ {
mplsTunnelExtOppositeDirPtr.2.1.2.1 = mplsTunnelName.1.1.1.2 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2
-- Set both the Ingress and Egress LocalId objects to TRUE as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
} }
9.2.8 Reverse direction mplsInSegmentEntry 9.2.8. Reverse direction mplsInSegmentEntry
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 entries. These are done in [RFC3813] using the mplsInSegmentTable and
and mplsOutSegmentTable. mplsOutSegmentTable.
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,
mplsInSegmentRowStatus = createAndGo (4) mplsInSegmentRowStatus = createAndGo (4)
} }
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
9.2.9 Reverse direction mplsXCEntry 9.2.9. Reverse direction mplsXCEntry
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001, mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000, mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label -- only a single outgoing label
mplsXCLabelStackIndex = 0x00, mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
This table entry is extended by entry in the This table entry is extended by entry in the
mplsXCExtTable. Note that the nature of the 'extends' mplsXCExtTable. Note that the nature of the 'extends'
relationship is a sparse augmentation so that the entry in the relationship is a sparse augmentation so that the entry in the
mplsXCExtTable has the same index values as the entry in mplsXCExtTable has the same index values as the entry in
the mplsXCTable. the mplsXCTable.
9.2.10 Reverse direction mplsXCExtEntry 9.2.10. Reverse direction mplsXCExtEntry
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.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
The following denotes the configured co-routed bidirectional
tunnel "head" entry and in intermediate and tail-end nodes,
the tunnel table and its associated tables are created
by the local management subsystem (e.g. agent) when the MPLS TP
tunnel is signaled successfully. Refer [RFC3812] and [RFC4802]
for signaling tunnel table configuration examples.
9.3.1. mplsTunnelEntry
In mplsTunnelTable:
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 0,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id, for the intermediate and tail-end nodes,
-- the local management entity is expected to pick a first available
-- local identifier which is not used in mplsTunnelTable.
mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR-Id
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
9.3.2. mplsTunnelExtEntry
-- An MPLS extension table
In mplsTunnelExtTable:
{
-- This opposite direction tunnel pointer MAY be point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel
-- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
We must next create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and
mplsOutSegmentTable.
9.3.3. Forward direction mplsOutSegmentEntry
The forward direction mplsOutSegmentTable will be populated
automatically based on the information received from the signaling
protocol.
9.3.4. Reverse direction mplsInSegmentEntry
The reverse direction mplsOutSegmentTable will be populated
automatically based on the information received from the signaling
protocol.
Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together.
9.3.5. Forward direction mplsXCEntry
The forward direction mplsXCEntry will be populated as soon as the
forward path label information is available.
9.3.6. Reverse direction mplsXCEntry
The reverse direction mplsXCEntry will be populated as soon as the
reverse path label information is available.
This table entry is extended by entry in the mplsXCExtTable. Note
that the nature of the 'extends' relationship is a sparse
augmentation so that the entry in the mplsXCExtTable has the same
index values as the entry in the mplsXCTable.
9.3.7. Forward direction mplsXCExtEntry
Once the forward path information is negotiated using signaling
protocol, the forward direction mplsXCExtEntry will be created for
associating the opposite direction XC entry and tunnel table entry.
9.3.8. Reverse direction mplsXCExtEntry
Once the reverse path information is negotiated using signaling
protocol, the reverse direction mplsXCExtEntry will be created for
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
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent, Redeem,
India India
Email: Kannan.Sampath@aricent.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 Juniper Networks
10 Technology Park Drive, 10 Technology Park Drive,
Westford, MA 01886 Westford, MA 01886
Email: tnadeau@juniper.net Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2012 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 Textual Conventions for This MIB module contains Textual Conventions for
MPLS based transport networks." MPLS based transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201207150000Z" -- July 15, 2012
"201301140000Z" -- January 14, 2013
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
skipping to change at page 19, line 5 skipping to change at page 24, line 38
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.
Further ASN 0 is reserved. A Global_ID of zero means Further ASN 0 is reserved. A Global_ID of zero means
that no Global_ID is present. Note that a Global_ID of that no Global_ID is present. Note that a Global_ID of
zero is limited to entities contained within a single zero is limited to entities contained within a single
operator and MUST NOT be used across an NNI. operator and MUST NOT be used across an NNI.
A non-zero Global_ID MUST be derived from an ASN owned by A non-zero Global_ID MUST be derived from an ASN owned by
the operator." the operator."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370]
Section 3 Uniquely Identifying an Operator - the Global_ID"
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
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 Global_ID. "The Node_ID is assigned within the scope of the Global_ID.
The value 0(or 0.0.0.0 in dotted decimal notation) is The value 0(or 0.0.0.0 in dotted decimal notation) is
reserved and MUST NOT be used. 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."
SYNTAX Unsigned32 REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370],
Section 4. Node and Interface Identifiers"
SYNTAX Unsigned32 -- the default range: (0..4294967295)
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." with upper case letters."
SYNTAX OCTET STRING (SIZE (1..6)) REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
[I-D.ietf-mpls-tp-itu-t-identifiers], Section 3.
Uniquely Identifying an Operator - the ICC_Operator_ID"
SYNTAX OCTET STRING (SIZE (1..6))
-- 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
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
skipping to change at page 20, line 9 skipping to change at page 26, line 4
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, MplsIccId, MplsNodeId MplsGlobalId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB FROM MPLS-TC-EXT-STD-MIB
; ;
mplsIdStdMIB MODULE-IDENTITY mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent,
Redeem,
India India
Email: Kannan.Sampath@aricent.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 Juniper Networks
10 Technology Park Drive, 10 Technology Park Drive,
Westford, MA 01886 Westford, MA 01886
Email: tnadeau@juniper.net Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2012 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 Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
DESCRIPTION DESCRIPTION
"MPLS identifiers MIB object extension" "This MIB modules defines the MIB objects for MPLS-TP
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
SYNTAX MplsGlobalId SYNTAX MplsGlobalId
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the administrator to assign a unique
"This object allows the operator to assign a unique
operator identifier also called MPLS-TP Global_ID." operator identifier also called MPLS-TP Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 1 } ::= { mplsIdObjects 1 }
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 a
network." network."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 2 } ::= { mplsIdObjects 2 }
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 Node_ID is assigned within the scope of
the Global_ID." the Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 3 } ::= { mplsIdObjects 3 }
-- Module compliance. -- Module compliance.
mplsIdGroups mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 1 } OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdCompliances mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 2 } OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
skipping to change at page 23, line 35 skipping to change at page 30, line 19
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,
mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsPerfGroup, mplsLsrNotificationGroup mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813] FROM MPLS-LSR-STD-MIB; -- [RFC3813]
mplsLsrExtStdMIB MODULE-IDENTITY mplsLsrExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent, Redeem,
India India
Email: Kannan.Sampath@aricent.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 Juniper Networks
10 Technology Park Drive, Westford, MA 01886 10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2012 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
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 mplsLsrExtNotifications OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 0 } ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER mplsLsrExtObjects OBJECT IDENTIFIER
skipping to change at page 25, line 12 skipping to change at page 31, line 41
mplsXCExtTable OBJECT-TYPE mplsXCExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCExtEntry SYNTAX SEQUENCE OF MplsXCExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table sparse augments the mplsXCTable of "This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific
information about associated tunnel information" information about associated tunnel information"
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,
Section 5.7. mplsXCTable"
::= { 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 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 administrator 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,
Section 10. mplsXCTable"
INDEX { mplsXCIndex, mplsXCInSegmentIndex, INDEX { mplsXCIndex, mplsXCInSegmentIndex,
mplsXCOutSegmentIndex } mplsXCOutSegmentIndex }
::= { mplsXCExtTable 1 } ::= { mplsXCExtTable 1 }
MplsXCExtEntry ::= SEQUENCE { MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTunnelPointer RowPointer, mplsXCExtTunnelPointer RowPointer,
mplsXCExtOppositeDirXCPtr RowPointer mplsXCExtOppositeDirXCPtr RowPointer
} }
mplsXCExtTunnelPointer OBJECT-TYPE mplsXCExtTunnelPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only object indicates the back pointer to "This read-only object indicates the back pointer to
the tunnel entry segment." the tunnel entry segment."
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,
Section 10. mplsXCTable"
::= { mplsXCExtEntry 1 } ::= { mplsXCExtEntry 1 }
mplsXCExtOppositeDirXCPtr OBJECT-TYPE mplsXCExtOppositeDirXCPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the pointer to the opposite "This object indicates the pointer to the opposite
direction XC entry. This object cannot be modified if direction XC entry. This object cannot be modified if
mplsXCRowStatus for the corresponding entry in the mplsXCRowStatus for the corresponding entry in the
mplsXCTable is active(1)." mplsXCTable is active(1)."
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,
Section 10. mplsXCTable"
::= { mplsXCExtEntry 2 } ::= { mplsXCExtEntry 2 }
mplsLsrExtGroups mplsLsrExtGroups
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
mplsLsrExtCompliances mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support "Compliance statement for agents that provide full support
for MPLS-LSR-EXT-STD-MIB. for MPLS-LSR-EXT-STD-MIB.
skipping to change at page 27, line 40 skipping to change at page 34, line 30
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsXCExtGroup mplsXCExtGroup
} }
OBJECT mplsXCExtTunnelPointer OBJECT mplsXCExtTunnelPointer
SYNTAX RowPointer SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The only valid value for Tunnel Pointer is mplsTunnelTable "The only valid value for Tunnel Pointer is
entry." mplsTunnelTable entry."
::= { mplsLsrExtCompliances 2 } OBJECT mplsXCExtOppositeDirXCPtr
SYNTAX RowPointer
MIN-ACCESS read-only
DESCRIPTION
"The only valid value for XC Pointer is
mplsXCTable entry."
::= { mplsLsrExtCompliances 2 }
mplsXCExtGroup OBJECT-GROUP mplsXCExtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsXCExtTunnelPointer, mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr mplsXCExtOppositeDirXCPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object should be supported in order to access "This object should be supported in order to access
the tunnel entry from XC entry." the tunnel entry from XC entry."
skipping to change at page 28, line 36 skipping to change at page 35, line 35
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
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent, Redeem,
India India
Email: kannankvs@gmail.com
Email: Kannan.Sampath@aricent.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 Juniper Networks
10 Technology Park Drive, Westford, MA 01886 10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net Email: tnadeau@juniper.net
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2012 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 Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201207150000Z" -- July 15, 2012 "201301140000Z" -- January 14, 2013
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 -- Notifications
skipping to change at page 30, line 6 skipping to change at page 36, line 49
-- conformance -- conformance
mplsTeExtConformance OBJECT IDENTIFIER mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 2 } ::= { mplsTeExtStdMIB 2 }
-- Start of MPLS Transport Profile Node configuration table -- Start of MPLS Transport Profile Node configuration table
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 administrator to map a node or "This table allows the operator to map a node or
LSR Identifier (IP compatible [Global_Node_ID] or ICC) LSR Identifier (IP compatible [Global_Node_ID] or ICC)
with a local identifier. with a local identifier.
This table is created to reuse the existing This table is created to reuse the existing
mplsTunnelTable for MPLS based transport network mplsTunnelTable for MPLS based transport network
tunnels also. tunnels also.
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_Node_Id of size 8 bytes and MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and
ICC of size 6 bytes, there exists a need to map the ICC of size 6 bytes, there exists a need to map the
skipping to change at page 31, line 16 skipping to change at page 38, line 12
mplsTunnelExtNodeConfigLocalId OBJECT-TYPE mplsTunnelExtNodeConfigLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId SYNTAX MplsExtendedTunnelId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used in accommodating the bigger "This object is used in accommodating the bigger
size Global_Node_ID and/or ICC with lower size LSR size Global_Node_ID and/or ICC with lower size LSR
identifier in order to index the mplsTunnelTable. identifier in order to index the mplsTunnelTable.
The Local Identifier is configured between 1 and 16777215, The Local Identifier is configured between 0 and 16777215,
as valid IP address range starts from 16777216(01.00.00.00). as valid IP address range starts from 16777216(01.00.00.00).
This range is chosen to identify the mplsTunnelTable's This range is chosen to identify the mplsTunnelTable's
Ingress/Egress LSR-id is IP address or Local identifier, Ingress/Egress LSR-id is IP address or Local identifier,
if the configured range is not IP address, administrator is if the configured range is not IP address, operator is
expected to retrieve the complete information expected to retrieve the complete information
(Global_Node_ID or ICC) from mplsTunnelExtNodeConfigTable. (Global_Node_ID or ICC) from mplsTunnelExtNodeConfigTable.
This way, existing mplsTunnelTable is reused for This way, existing mplsTunnelTable is reused for
bidirectional bidirectional tunnel extensions for MPLS based transport
tunnel extensions for MPLS based transport networks. networks.
This Local Identifier allows the administrator to assign This Local Identifier allows the operator to assign
a unique identifier to map Global_Node_ID and/or ICC." a unique identifier to map Global_Node_ID and/or ICC.
As this Local Identifier is unique within the node and
the same syntax of this object can be used for MPLS TE
tunnel also, it is up to the operator/local management
entity to choose the non-conflicting value for indexing
the MPLS and MPLS-TP tunnel entries."
::= { mplsTunnelExtNodeConfigEntry 1 } ::= { mplsTunnelExtNodeConfigEntry 1 }
mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId SYNTAX MplsGlobalId
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Global Operator Identifier. "This object indicates the Global Operator Identifier.
This object value should be zero when This object value should be zero when
mplsTunnelExtNodeConfigIccId is configured with non-null mplsTunnelExtNodeConfigIccId is configured with non-null
value." value."
REFERENCE REFERENCE
"MPLS-TP Identifiers [RFC6370]." "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 3. Uniquely Identifying an Operator -
the Global_ID"
::= { mplsTunnelExtNodeConfigEntry 2 } ::= { mplsTunnelExtNodeConfigEntry 2 }
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId SYNTAX MplsNodeId
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Node_ID within the operator. "This object indicates the Node_ID within the operator.
This object value should be zero when This object value should be zero when
mplsTunnelExtNodeConfigIccId is configured with non-null mplsTunnelExtNodeConfigIccId is configured with non-null
value." value."
REFERENCE REFERENCE
"MPLS-TP Identifiers [RFC6370]." "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]
Section 4, Node and Interface Identifiers"
::= { mplsTunnelExtNodeConfigEntry 3 } ::= { mplsTunnelExtNodeConfigEntry 3 }
mplsTunnelExtNodeConfigIccId OBJECT-TYPE mplsTunnelExtNodeConfigIccId OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsIccId
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the operator or service provider to "This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Carrier Code (ICC) configure a unique MPLS-TP ITU-T Carrier Code (ICC)
either for Ingress ID or Egress ID. either for Ingress ID or Egress ID.
This object value should be zero when This object value should be zero when
mplsTunnelExtNodeConfigGlobalId and mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId are assigned with non-zero mplsTunnelExtNodeConfigNodeId are assigned with non-zero
value." value."
REFERENCE REFERENCE
"MPLS-TP Identifiers [RFC6370]." "MPLS-TP Identifiers Following ITU-T Conventions,
[I-D.ietf-mpls-tp-itu-t-identifiers], August 2012,
Section 3. Uniquely Identifying an Operator - the
ICC_Operator_ID"
::= { mplsTunnelExtNodeConfigEntry 4 } ::= { mplsTunnelExtNodeConfigEntry 4 }
mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the administrator to create, modify, "This object allows the operator to create, modify,
and/or delete a row in this table." and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 5 } ::= { mplsTunnelExtNodeConfigEntry 5 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. object.
skipping to change at page 33, line 4 skipping to change at page 40, line 10
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. object.
Conceptual rows having the value 'permanent' Conceptual rows having the value 'permanent'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { volatile } DEFVAL { volatile }
::= { mplsTunnelExtNodeConfigEntry 6 } ::= { mplsTunnelExtNodeConfigEntry 6 }
-- End of MPLS Transport Profile Node configuration table -- End of MPLS Transport Profile Node configuration table
-- Start of MPLS Transport Profile Node IP compatible -- Start of MPLS Transport Profile Node IP compatible
-- mapping table -- mapping table
mplsTunnelExtNodeIpMapTable OBJECT-TYPE mplsTunnelExtNodeIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only table allows the administrator to retrieve "This read-only table allows the operator to retrieve
the local identifier for a given Global_Node_ID in an IP the local identifier for a given Global_Node_ID in an IP
compatible operator environment. compatible 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 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 2 }
mplsTunnelExtNodeIpMapEntry OBJECT-TYPE mplsTunnelExtNodeIpMapEntry OBJECT-TYPE
skipping to change at page 34, line 39 skipping to change at page 41, line 50
-- End MPLS Transport Profile Node IP compatible table -- End MPLS Transport Profile Node IP compatible table
-- Start of MPLS Transport Profile Node ICC based table -- Start of MPLS Transport Profile Node ICC based table
mplsTunnelExtNodeIccMapTable OBJECT-TYPE mplsTunnelExtNodeIccMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This read-only table allows the administrator to retrieve "This read-only table allows the operator to retrieve
the local identifier for a given ICC operator in an ICC the local identifier for a given ICC operator in an ICC
operator environment. 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."
skipping to change at page 36, line 4 skipping to change at page 43, line 12
SYNTAX MplsExtendedTunnelId SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an ICC based local identifier "This object contains an ICC based local identifier
which is defined in mplsTunnelExtNodeConfigTable." which is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapEntry 2 } ::= { mplsTunnelExtNodeIccMapEntry 2 }
-- End MPLS Transport Profile Node ICC based table -- End MPLS Transport Profile Node ICC based table
-- Start of MPLS Tunnel table extension -- Start of MPLS Tunnel table extension
mplsTunnelExtTable OBJECT-TYPE mplsTunnelExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtEntry SYNTAX SEQUENCE OF MplsTunnelExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents MPLS-TP specific extensions to "This table represents extensions to mplsTunnelTable
mplsTunnelTable. in order to support MPLS-TP tunnels.
As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based
co-routed bidirectional tunnel, co-routed bidirectional tunnel,
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num Node_ID::Tunnel_Num}::LSP_Num
LSP_ID for IP based associated bidirectional tunnel, LSP_ID for IP based associated bidirectional tunnel,
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
skipping to change at page 36, line 39 skipping to change at page 43, line 48
mplsTunnelIngressLSRId, Destination Node_ID is mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance. mplsTunnelInstance.
Source Global_Node_ID and/or ICC and Destination Source Global_Node_ID and/or ICC and Destination
Global_Node_ID and/or ICC are maintained in the Global_Node_ID and/or ICC are maintained in the
mplsTunnelExtNodeConfigTable and mplsTunnelExtNodeConfigTable and
mplsTunnelExtNodeConfigLocalId is used to create an entry mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable." in mplsTunnelTable."
REFERENCE REFERENCE
"MPLS-TP Identifiers [RFC6370]." "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370],
Section 3 and 4."
::= { mplsTeExtObjects 4 } ::= { mplsTeExtObjects 4 }
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 {
skipping to change at page 37, line 14 skipping to change at page 44, line 27
mplsTunnelIngressLSRId, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
} }
::= { mplsTunnelExtTable 1 } ::= { mplsTunnelExtTable 1 }
MplsTunnelExtEntry ::= SEQUENCE { MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelExtOppositeDirPtr RowPointer, mplsTunnelExtOppositeDirPtr RowPointer,
mplsTunnelExtOppositeDirTnlValid TruthValue, mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex, mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue mplsTunnelExtDestTnlValid TruthValue,
mplsTunnelExtIngressLSRLocalIdValid 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 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. same tunnel or in the different tunnels.
This object holds the opposite direction tunnel entry This object holds the opposite direction tunnel entry
if the bidirectional tunnel is setup by configuring two if the bidirectional tunnel is setup by configuring two
tunnel entries in mplsTunnelTable. tunnel entries in mplsTunnelTable.
Note that there are two different ways to represent the
opposite direction tunnel entry. One method is to use this
object mplsTunnelExtOppositeDirPtr as RowPointer and make
it point to the other direction tunnel. Other method is to
use the mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex instead of using this
mplsTunnelExtOppositeDirPtr. Implementation can choose
either one of the method to represent the opposite
direction tunnel. Duplicate methods are provided to provide
easy ways for different implementations.
The value of zeroDotZero indicates single tunnel entry The value of zeroDotZero indicates single tunnel entry
is used for bidirectional tunnel setup." is used for bidirectional tunnel setup."
DEFVAL { zeroDotZero }
::= { mplsTunnelExtEntry 1 } 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
skipping to change at page 39, line 23 skipping to change at page 46, line 51
mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex for identifying mplsTunnelExtDestTnlLspIndex for identifying
the opposite direction tunnel information. Note that if the opposite direction tunnel information. Note that if
this variable is set to true then the this variable is set to true then the
mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite direction tunnel indices." the valid opposite direction tunnel indices."
DEFVAL { false } DEFVAL { false }
::= { mplsTunnelExtEntry 5 } ::= { mplsTunnelExtEntry 5 }
-- End of MPLS Tunnel table extension mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object denotes whether the mplsTunnelIngressLSRId
contains the local value, which is used to reference
the complete Ingress Global_ID::Node_ID or ICC from
the mplsTunnelExtNodeConfigTable."
REFERENCE
"MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelIngressLSRId
object in mplsTunnelTable.
If this object is set to FALSE, mplsTunnelExtNodeConfigTable
will not contain an entry to reference local identifier with
Global_ID::Node_ID or ICC value.
This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelIngressId itself provides
complete Ingress LSRId."
DEFVAL { false }
::= { mplsTunnelExtEntry 6 }
mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object denotes whether the mplsTunnelEgressLSRId
contains the local value, which is used to reference
the complete Egress Global_ID::Node_ID or ICC from
the mplsTunnelExtNodeConfigTable."
REFERENCE
"MPLS-TE-STD-MIB [RFC3812], Section 11. mplsTunnelEgressLSRId
object in mplsTunnelTable.
If this object is set to FALSE, mplsTunnelExtNodeConfigTable
will not contain an entry to reference local identifier with
Global_ID::Node_ID or ICC value.
This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelEgressId itself provides
complete Egress LSRId."
DEFVAL { false }
::= { mplsTunnelExtEntry 7 }
-- End of MPLS Tunnel table extension
mplsTunnelExtReversePerfTable OBJECT-TYPE mplsTunnelExtReversePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends the mplsTunnelTable to provide "This table extends the mplsTunnelTable to provide
per-tunnel packet performance information for the reverse per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel. It can be seen as direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable, which augments the supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable. mplsTunnelTable.
For links that do not transport packets, these packet For links that do not transport packets, these packet
counters cannot be maintained. For such links, attempts counters cannot be maintained. For such links, attempts
to read the objects in this table will return to read the objects in this table will return
noSuchInstance." noSuchInstance."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic "1. Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE)Management Information Base (MIB), Engineering (TE)Management Information Base (MIB),
RFC 3812." RFC 3812. Section 6.6. mplsTunnelPerfTable"
::= { mplsTeExtObjects 5 } ::= { mplsTeExtObjects 5 }
mplsTunnelExtReversePerfEntry OBJECT-TYPE mplsTunnelExtReversePerfEntry OBJECT-TYPE
SYNTAX MplsTunnelExtReversePerfEntry SYNTAX MplsTunnelExtReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every "An entry in this table is created by the LSR for every
bidirectional MPLS tunnel where packets are visible to the bidirectional MPLS tunnel where packets are visible to the
LSR." LSR."
skipping to change at page 43, line 40 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,
mplsTunnelExtEgressLSRLocalIdValid,
mplsTunnelExtReversePerfPackets, mplsTunnelExtReversePerfPackets,
mplsTunnelExtReversePerfHCPackets, mplsTunnelExtReversePerfHCPackets,
mplsTunnelExtReversePerfErrors, mplsTunnelExtReversePerfErrors,
mplsTunnelExtReversePerfBytes, mplsTunnelExtReversePerfBytes,
mplsTunnelExtReversePerfHCBytes mplsTunnelExtReversePerfHCBytes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to "Necessary, but not sufficient, set of objects to
skipping to change at page 45, line 31 skipping to change at page 54, line 11
access to the objects only to those principles (users) that access to the objects only to those principles (users) that
have legitimate rights to indeed GET or SET (change/create/delete) have legitimate rights to indeed GET or SET (change/create/delete)
them. them.
15. IANA Considerations 15. IANA Considerations
To be added in a later version of this document. To be added in a later version of this document.
16. References 16. References
16.1 Normative References 16.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"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.
16.2 Informative References 16.2. Informative References
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering "Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, June (TE) Management Information Base (MIB)", RFC 3812, June
2004. 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC 3813, (LSR) Router Management Information Base (MIB)", RFC 3813,
June 2004. June 2004.
skipping to change at page 46, line 35 skipping to change at page 55, line 15
Engineering Management Information Base", RFC Engineering Management Information Base", RFC
4802, February 2007. 4802, February 2007.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Sprecher, N., and S. Ueno, "Requirements of an MPLS Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009. Transport Profile", RFC 5654, September 2009.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
Profile (MPLS-TP) Identifiers", RFC 6370, September Profile (MPLS-TP) Identifiers", RFC 6370, September
2011. 2011.
[I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort,
H., and M. Betts, "MPLS-TP Identifiers Following ITU-T
Conventions", draft-ietf-mpls-tp-itu-t-identifiers-07
(work in progress), August 2012.
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 Joan Cucchiara Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Joan Cucchiara and
for their valuable comments. Randy Presuhn for their valuable comments.
18. Authors' Addresses 18. Authors' Addresses
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
skipping to change at page 47, line 4 skipping to change at page 55, line 38
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 Juniper Networks
10 Technology Park Drive, Westford, MA 01886 10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net Email: tnadeau@juniper.net
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Inc.
350 Holger way, San Jose, CA, USA 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent Redeem
India India
Email: Kannan.Sampath@aricent.com Email: kannankvs@gmail.com
 End of changes. 134 change blocks. 
209 lines changed or deleted 495 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/