draft-ietf-mpls-tp-te-mib-03.txt   draft-ietf-mpls-tp-te-mib-04.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: October 15, 2012 Kannan KV Sampath Expires: January 16, 2013 Kannan KV Sampath
Aricent Aricent
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
April 13, 2012 July 15, 2012
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
draft-ietf-mpls-tp-te-mib-03.txt draft-ietf-mpls-tp-te-mib-04.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 October 15, 2012. This Internet-Draft will expire on January 16, 2013.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 Conventions used in this document . . . . . . . . . . . . . 3 3.1 Conventions used in this document . . . . . . . . . . . . . 3
3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 4
6.1. mplsNodeConfigTable . . . . . . . . . . . . . . . . . . . 5 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . 5
6.2. mplsNodeIpMapTable . . . . . . . . . . . . . . . . . . . . 5 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . 5
6.3. mplsNodeIccMapTable . . . . . . . . . . . . . . . . . . . 6 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . 6
6.4.mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . . 6 6.4.mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . . 6
7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 6 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 6
8. Dependencies between MIB Module Tables . . . . . . . . . . . . 8 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 8
9. Example of MPLS-TP tunnel setup . . . . . . . . . . . . . . . . 8 9. Example of MPLS-TP tunnel setup . . . . . . . . . . . . . . . . 8
10. MPLS Textual Convention Extension MIB definitions . . . . . . 13 10. MPLS Textual Convention Extension MIB definitions . . . . . . 13
11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 16 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 16
12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 20 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 20
13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 24 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 24
14. Security Consideration . . . . . . . . . . . . . . . . . . . . 36 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 36
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
skipping to change at page 3, line 13 skipping to change at page 3, line 13
18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 38 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 38
1 Introduction 1 Introduction
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).
This MIB module should be used in conjunction with the MPLS traffic The existing MPLS TE [RFC3812] and GMPLS MIBs [RFC4802] do not
Engineering MIB [RFC3812] and companion document MPLS Label Switch support the transport network requirements of NON-IP based management
Router MIB [RFC3813] for MPLS based traffic engineering configuration and static bidirectional tunnels. This MIB module should be used in
and management. conjunction with the MPLS traffic Engineering MIB [RFC3812] and
companion document MPLS Label Switch Router MIB [RFC3813] for MPLS
based traffic engineering configuration and management.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to
be interpreted as described in BCP 14, RFC2119. 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].
skipping to change at page 4, line 19 skipping to change at page 4, line 22
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
The existing MPLS TE [RFC3812] and GMPLS MIBs [RFC4802] do not This document provide extensions to existing MPLS MIB modules in
support the transport network requirements of NON-IP based management order to support configuration of MPLS-TP tunnels in IP and NON-IP
and static bidirectional tunnels. environments.
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 point-to-point, co-routed bi-directional
associated bi-directional tunnels. 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.
- A node configuration table (mplsNodeConfigTable) is used to - A node configuration table (mplsTunnelExtNodeConfigTable)
translate the Global_Node_ID or ICC to the local identifier is used to translate the Global_Node_ID or ICC to the local
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. mplsNodeConfigTable 6.1. mplsTunnelExtNodeConfigTable
The mplsNodeConfigTable is used to assign a local identifier for a The mplsTunnelExtNodeConfigTable is used to assign a local identifier
given ICC or Global_Node_ID combination as defined in [RFC6370]. for a given ICC or Global_Node_ID combination as defined in
An ICC is a string of one to six characters, each character being [RFC6370]. An ICC is a string of one to six characters, each
either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9)
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
table representing a node. Every node is assigned a local identifier table representing a node. Every node is assigned a local identifier
within a range of 0 to 16777215. This local identifier is used for within a range of 0 to 16777215. This local identifier is used for
indexing into mplsTunnelTable as mplsTunnelIngressLSRId and indexing into mplsTunnelTable as mplsTunnelIngressLSRId and
mplsTunnelEgressLSRId. mplsTunnelEgressLSRId.
For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel
skipping to change at page 5, line 34 skipping to change at page 5, line 36
Global_ID and Destination Node_ID. Global_ID and Destination Node_ID.
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,
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 mplsNodeConfigTable will be used to store an entry for ICC or The mplsTunnelExtNodeConfigTable will be used to store an entry for
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 mplsTunnelTable. As the regular TE tunnels use IP address as LSR in mplsTunnelTable. As the regular TE tunnels use IP address as LSR
ID, the local identifier should be below the first valid IP address, ID, 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. mplsNodeIpMapTable 6.2. mplsTunnelExtNodeIpMapTable
The read-only mplsNodeIpMaptable is used to query the local The read-only mplsTunnelExtNodeIpMaptable is used to query the local
identifier assigned and stored in mplsNodeConfigTable for a given identifier assigned and stored in mplsTunnelExtNodeConfigTable for
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. mplsNodeIccMapTable 6.3. mplsTunnelExtNodeIccMapTable
The read-only mplsNodeIccMapTable is used to query the local The read-only mplsTunnelExtNodeIccMapTable is used to query the local
identifier assigned and stored in the mplsNodeConfigTable 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 to add MPLS-TP tunnel
specific additional objects. All the additional attributes specific specific additional objects. All the additional attributes specific
to TP tunnel are contained in this extended table and could be to TP tunnel are contained in this extended table and could be
accessed with the mplsTunnelTable indices. accessed with the mplsTunnelTable indices.
6.5 mplsTunnelReversePerfTable 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 7, line 30 skipping to change at page 7, line 30
| ^ | ^
| | | |
| | | |
+------MPLS-LSR-EXT-STD-MIB +------MPLS-LSR-EXT-STD-MIB
Thus: Thus:
- All the new MPLS extension MIB modules depend on - All the new MPLS extension MIB modules depend on
MPLS-TC-EXT-STD-MIB. MPLS-TC-EXT-STD-MIB.
- MPLS-TE-STD-MIB [RFC3812] contains references to objects in - MPLS-ID-STD-MIB contains references to objects in
MPLS-ID-STD-MIB. MPLS-TE-STD-MIB [RFC3812].
- MPLS-TE-EXT-STD-MIB contains references to objects in - MPLS-TE-EXT-STD-MIB contains references to objects in
MPLS-TE-STD-MIB [RFC3812]. MPLS-TE-STD-MIB [RFC3812].
- MPLS-LSR-EXT-STD-MIB contains references to objects in - MPLS-LSR-EXT-STD-MIB contains references to objects in
MPLS-LSR-STD-MIB [RFC3813]. MPLS-LSR-STD-MIB [RFC3813].
MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB
mib module for associating the reverse direction tunnel MIB module for associating the reverse direction tunnel
information. information.
Note that the nature of the 'extends' relationship Note that the nature of the 'extends' relationship
is a sparse augmentation so that the entry in the is a sparse augmentation so that the entry in the
mplsTunnelExtTable has the same index values as the in the mplsTunnelExtTable has the same index values as the in the
mplsTunnelTable. mplsTunnelTable.
MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB
mib module for pointing back to the tunnel entry for easy tunnel MIB module for pointing back to the tunnel entry for easy tunnel
access from XC entry. access from XC entry.
Note that the nature of the 'extends' relationship Note that the nature of the 'extends' relationship
is a sparse augmentation so that the entry in the is a sparse augmentation so that the entry in the
mplsXCExtTable has the same index values as the in the mplsXCTable. mplsXCExtTable has the same index values as the in the mplsXCTable.
8. Dependencies between MIB Module Tables 8. Dependencies between MIB Module Tables
The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram
below. The arrows indicate a reference from one table to another. below. The arrows indicate a reference from one table to another.
mplsNodeConfigTable mplsTunnelExtNodeConfigTable
^ mplsXCExtTable ^ mplsXCExtTable
| | ^ | | ^
| +---------+ | | +---------+ |
| | | | | |
| V V | V V
mplsTunnelTable ---->mplsXCTable mplsTunnelTable ---->mplsXCTable
^ ^
| |
| |
mplsTunnelExtTable mplsTunnelExtTable
An existing mplsTunnelTable uses the mplsNodeConfigTable table to map An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable
the Global_Node_ID and/or ICC with the local number in order to table to map the Global_Node_ID and/or ICC with the local number in
accommodate in the existing tunnel table's ingress/egress LSR-id. order to accommodate in the existing tunnel table's ingress/egress
LSR-id.
New mplsTunnelExtTable table provides the reverse direction LSP New mplsTunnelExtTable table provides the reverse direction LSP
information for the existing tunnel table in order to achieve information for the existing tunnel table in order to achieve
bidirectional LSPs. bidirectional LSPs.
mplsXCExtTable is extended from mplsLsrXCTable to provide mplsXCExtTable is extended from mplsLsrXCTable to provide
backward reference to tunnel entry. backward reference to tunnel entry.
9. Example of MPLS-TP Tunnel Setup 9. Example of MPLS-TP Tunnel Setup
In this section, we provide an example of the IP based MPLS-TP 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 MPLS-TP tunnel.
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 mplsNodeConfigTable: In mplsTunnelExtNodeConfigTable:
{ {
-- Non-IP Ingress LSR-Id (Index to the table) -- Non-IP Ingress LSR-Id (Index to the table)
mplsNodeConfigLocalId = 1, mplsTunnelExtNodeConfigLocalId = 1,
mplsNodeConfigGlobalId = 1234,
mplsNodeConfigNodeId = 10, mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 10,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsNodeConfigRowStatus = createAndGo (4) mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
-- Non-IP Egress LSR-Id (Index to the table) -- Non-IP Egress LSR-Id (Index to the table)
mplsNodeConfigLocalId = 2, mplsTunnelExtNodeConfigLocalId = 2,
mplsNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigGlobalId = 1234,
mplsNodeConfigNodeId = 20, mplsTunnelExtNodeConfigNodeId = 20,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsNodeConfigRowStatus = createAndGo (4) mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
} }
This will create an entry in the mplsNodeConfigTable for a This will create an entry in the mplsTunnelExtNodeConfigTable for a
Global_Node_ID. A separate entry is made for both Ingress LSR Global_Node_ID. A separate entry is made for both Ingress LSR
and Egress LSR. and Egress LSR.
The following read-only mplsNodeIpMapTable table is populated The following read-only mplsTunnelExtNodeIpMapTable table is
automatically upon creating an entry in mplsNodeConfigTable and populated automatically upon creating an entry in
this table is used to retrieve the local identifier for the given mplsTunnelExtNodeConfigTable and this table is used to retrieve
Global_Node_ID. the local identifier for the given Global_Node_ID.
In mplsNodeIpMapTable: In mplsTunnelExtNodeIpMapTable:
{ {
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsNodeIpMapNodeId = 10, mplsTunnelExtNodeIpMapNodeId = 10,
mplsNodeIpMapLocalId = 1 mplsTunnelExtNodeIpMapLocalId = 1
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsNodeIpMapGlobalId = 1234, mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsNodeIpMapNodeId = 20, mplsTunnelExtNodeIpMapNodeId = 20,
mplsNodeIpMapLocalId = 2 mplsTunnelExtNodeIpMapLocalId = 2
} }
9.1 Example of MPLS-TP co-routed bidirectional tunnel setup 9.1 Example of MPLS-TP 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 mplsNodeConfigTable for Ingress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Ingress LSR-Id
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsNodeConfigTable for Egress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Egress LSR-Id
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP", mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West", mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
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,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0, mplsTunnelHoldingPrio = 0,
skipping to change at page 10, line 44 skipping to change at page 10, line 46
} }
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
mplsTunnelOppositeDirTnlPtr = 0.0 mplsTunnelExtOppositeDirTnlPtr = 0.0
} }
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 mplsOutSegmentTable. and 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.
skipping to change at page 12, line 30 skipping to change at page 12, line 32
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.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
mplsXCOppositeDirXCPtr = 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.6 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
mplsXCOppositeDirXCPtr = 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 mplsTunnelReversePerfTable 9.1.7 mplsTunnelExtReversePerfTable
The mplsTunnelReversePerfTable 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 mplsTunnelReversePerfTable 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 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 tunnel "head" entry: forward 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 mplsNodeConfigTable for Ingress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Ingress LSR-Id
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsNodeConfigTable for Egress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Egress LSR-Id
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP associated bi-directional mplsTunnelName = "TP associated bi-directional
forward LSP", forward LSP",
mplsTunnelDescr = "East to West", mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
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,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
skipping to change at page 13, line 50 skipping to change at page 14, line 4
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:
{ {
mplsTunnelOppositeDirPtr.1.1.1.2 = mplsTunnelName.2.1.2.1 mplsTunnelExtOppositeDirPtr.1.1.1.2 = mplsTunnelName.2.1.2.1
} }
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
skipping to change at page 14, line 49 skipping to change at page 15, line 4
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
mplsXCOppositeDirXCPtr = 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 Forward direction mplsTunnelEntry
The following denotes the configured associated bidirectional The following denotes the configured associated bidirectional
reverse tunnel "tail" entry: reverse tunnel "tail" entry:
In mplsTunnelTable: In mplsTunnelTable:
{ {
mplsTunnelIndex = 2, mplsTunnelIndex = 2,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
-- Local map number created in mplsNodeConfigTable for Ingress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Ingress LSR-Id
mplsTunnelIngressLSRId = 2, mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsNodeConfigTable for Egress -- Local map number created in mplsTunnelExtNodeConfigTable for
LSR-Id -- Egress LSR-Id
mplsTunnelEgressLSRId = 1, mplsTunnelEgressLSRId = 1,
mplsTunnelName = "TP associated bi-directional mplsTunnelName = "TP associated bi-directional
reverse LSP", reverse LSP",
mplsTunnelDescr = "West to East", mplsTunnelDescr = "West to East",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column -- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer = mplsTunnelXCPointer =
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,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
skipping to change at page 15, line 51 skipping to change at page 16, line 6
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:
{ {
mplsTunnelOppositeDirPtr.2.1.2.1 = mplsTunnelName.1.1.1.2 mplsTunnelExtOppositeDirPtr.2.1.2.1 = mplsTunnelName.1.1.1.2
} }
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 mplsOutSegmentTable. and mplsOutSegmentTable.
In mplsInSegmentTable: { mplsInSegmentIndex = In mplsInSegmentTable:
0x0000001 mplsInSegmentLabel = 21, -- incoming label {
mplsInSegmentNPop = 1, mplsInSegmentInterface = mplsInSegmentIndex = 0x0000001
13, -- incoming interface mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentRowStatus mplsInSegmentTrafficParamPtr = 0.0,
= createAndGo (4) } mplsInSegmentRowStatus = createAndGo (4)
}
Next, two cross-connect entries are created in the mplsXCTable of Next, two cross-connect entries are created in the mplsXCTable of the
the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
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
{ mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
-- Back pointer from XC table to Tunnel table mplsXCExtOppositeDirXCPtr =
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
mplsXCOppositeDirXCPtr = }
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
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
MODULE-IDENTITY, Unsigned32
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION IMPORTS
FROM SNMPv2-TC -- [RFC2579] MODULE-IDENTITY, Unsigned32
FROM SNMPv2-SMI -- [RFC2578]
mplsStdMIB TEXTUAL-CONVENTION
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM SNMPv2-TC -- [RFC2579]
; mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTcExtStdMIB MODULE-IDENTITY ;
LAST-UPDATED mplsTcExtStdMIB MODULE-IDENTITY
"201204080000Z" -- April 08, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath LAST-UPDATED
Aricent, "201207150000Z" -- July 15, 2012
India ORGANIZATION
Email: Kannan.Sampath@aricent.com "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
Sam Aldrin Kannan KV Sampath
Huawei Technologies Aricent,
2330 Central Express Way, India
Santa Clara, CA 95051, USA Email: Kannan.Sampath@aricent.com
Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Sam Aldrin
Juniper Networks Huawei Technologies
10 Technology Park Drive, Westford, MA 01886 2330 Central Express Way,
Email: tnadeau@juniper.net Santa Clara, CA 95051, USA
" Email: aldrin.ietf@gmail.com
DESCRIPTION Thomas D. Nadeau
"Copyright (c) 2012 IETF Trust and the persons identified Juniper Networks
as the document authors. All rights reserved. 10 Technology Park Drive,
Westford, MA 01886
Email: tnadeau@juniper.net
"
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
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
"201204080000Z" -- April 08, 2012 "201207150000Z" -- July 15, 2012
DESCRIPTION DESCRIPTION
"MPLS Textual Convention Extensions" "MPLS Textual Convention Extensions"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
MplsGlobalId ::= TEXTUAL-CONVENTION MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the Textual Convention of IP based "This object contains the Textual Convention of IP based
operator unique identifier (Global_ID), the Global_ID can operator unique identifier (Global_ID), the Global_ID can
contain the 2-octet or 4-octet value of the operator's contain the 2-octet or 4-octet value of the operator's
Autonomous System Number (ASN). Autonomous System Number (ASN).
It is expected that the Global_ID will be derived from It is expected that the Global_ID will be derived from
the globally unique ASN of the autonomous system hosting the globally unique ASN of the autonomous system hosting
the PEs containing the actual AIIs. the PEs containing the actual AIIs.
The presence of a Global_ID based on the operator's The presence of a Global_ID based on the operator's
ASN ensures that the AII will be globally unique. ASN ensures that the AII will be globally unique.
When the Global_ID is derived from a 2-octet AS number, When the Global_ID is derived from a 2-octet AS number,
the two high-order octets of this 4-octet identifier the two high-order octets of this 4-octet identifier
MUST be set to zero. MUST be set to zero.
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."
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 /32 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 SYNTAX Unsigned32
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)) SYNTAX OCTET STRING (SIZE (1..6))
MplsLocalId ::= TEXTUAL-CONVENTION -- MPLS-TC-EXT-STD-MIB module ends
DISPLAY-HINT "d" END
STATUS current
DESCRIPTION
"This textual convention is used in accommodating the bigger
size Global_Node_ID and/or ICC with lower size LSR
identifier in order to index the mplsTunnelTable.
The Local Identifier is configured between 1 and 16777215, 11. MPLS Identifier MIB definitions
as valid IP address range starts from 16777216(01.00.00.00).
This range is chosen to identify the mplsTunnelTable's
Ingress/Egress LSR-id is IP address or Local identifier,
if the configured range is not IP address, administrator is
expected to retrieve the complete information
(Global_Node_ID or ICC) from mplsNodeConfigTable. This way,
existing mplsTunnelTable is reused for bidirectional tunnel
extensions for MPLS based transport networks.
This Local Identifier allows the administrator to assign MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
a unique identifier to map Global_Node_ID and/or ICC."
SYNTAX Unsigned32(1..16777215)
-- MPLS-TC-EXT-STD-MIB module ends IMPORTS
END MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
11. MPLS Identifier MIB definitions mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED
"201207150000Z" -- July 15, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
IMPORTS Kannan KV Sampath
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE Aricent,
FROM SNMPv2-SMI -- [RFC2578] India
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP Email: Kannan.Sampath@aricent.com
FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
mplsIdStdMIB MODULE-IDENTITY Sam Aldrin
LAST-UPDATED Huawei Technologies
"201204080000Z" -- April 08, 2012 2330 Central Express Way,
ORGANIZATION Santa Clara, CA 95051, USA
"Multiprotocol Label Switching (MPLS) Working Group" Email: aldrin.ietf@gmail.com
CONTACT-INFO Thomas D. Nadeau
" Juniper Networks
Venkatesan Mahalingam 10 Technology Park Drive,
Dell Inc, Westford, MA 01886
350 Holger way, San Jose, CA, USA Email: tnadeau@juniper.net
Email: venkat.mahalingams@gmail.com "
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
Kannan KV Sampath This MIB module contains generic object definitions for
Aricent, MPLS Traffic Engineering in transport networks."
India
Email: Kannan.Sampath@aricent.com
Sam Aldrin -- Revision history.
Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
Thomas D. Nadeau REVISION
Juniper Networks "201207150000Z" -- July 15, 2012
10 Technology Park Drive, Westford, MA 01886 DESCRIPTION
Email: tnadeau@juniper.net "MPLS identifiers MIB object extension"
"
DESCRIPTION ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for -- Notifications
MPLS Traffic Engineering in transport networks." mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- Revision history. -- MPLS common objects
REVISION mplsIdGlobalId OBJECT-TYPE
"201204080000Z" -- April 08, 2012 SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION DESCRIPTION
"MPLS identifiers mib object extension" "This object allows the administrator to assign a unique
operator identifier also called MPLS-TP Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 1 }
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value mplsIdIcc OBJECT-TYPE
SYNTAX MplsIccId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a
network."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 2 }
-- traps mplsIdNodeId OBJECT-TYPE
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } SYNTAX MplsNodeId
-- tables, scalars MAX-ACCESS read-write
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } STATUS current
-- conformance DESCRIPTION
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } "This object allows the operator or service provider to
assign a unique MPLS-TP Node_ID.
-- MPLS common objects The Node_ID is assigned within the scope of
the Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 3 }
mplsGlobalId OBJECT-TYPE -- Module compliance.
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the administrator to assign a unique
operator identifier also called MPLS-TP Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 1 }
mplsIcc OBJECT-TYPE mplsIdGroups
SYNTAX MplsIccId OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a
network."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 2 }
mplsNodeId OBJECT-TYPE mplsIdCompliances
SYNTAX MplsNodeId OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP Node_ID.
The Node_ID is assigned within the scope of -- Compliance requirement for fully compliant implementations.
the Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 3 }
-- Module compliance. mplsIdModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
mplsIdGroups MODULE -- this module
OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdCompliances -- The mandatory group has to be implemented by all
OBJECT IDENTIFIER ::= { mplsIdConformance 2 } -- LSRs that originate/terminate MPLS-TP paths.
-- Compliance requirement for fully compliant implementations. MANDATORY-GROUPS {
mplsIdScalarGroup
}
mplsIdModuleFullCompliance MODULE-COMPLIANCE ::= { mplsIdCompliances 1 }
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
MODULE -- this module -- Compliance requirement for read-only implementations.
-- The mandatory group has to be implemented by all mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE
-- LSRs that originate/terminate MPLS-TP paths. STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
MANDATORY-GROUPS { MODULE -- this module
mplsIdScalarGroup
}
::= { mplsIdCompliances 1 } -- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP paths.
-- Compliance requirement for read-only implementations. MANDATORY-GROUPS {
mplsIdScalarGroup
}
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE ::= { mplsIdCompliances 2 }
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
MODULE -- this module -- Units of conformance.
-- The mandatory group has to be implemented by all mplsIdScalarGroup OBJECT-GROUP
-- LSRs that originate/terminate MPLS-TP paths. OBJECTS { mplsIdGlobalId,
mplsIdNodeId,
mplsIdIcc
MANDATORY-GROUPS { }
mplsIdScalarGroup STATUS current
} DESCRIPTION
"Scalar object needed to implement MPLS TP path."
::= { mplsIdGroups 1 }
::= { mplsIdCompliances 2 } -- MPLS-ID-STD-MIB module ends
END
-- Units of conformance. 12. MPLS LSR Extension MIB definitions
mplsIdScalarGroup OBJECT-GROUP MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
OBJECTS { mplsGlobalId,
mplsNodeId,
mplsIcc
} IMPORTS
STATUS current MODULE-IDENTITY, OBJECT-TYPE
DESCRIPTION FROM SNMPv2-SMI -- [RFC2578]
"Scalar object needed to implement MPLS TP path." MODULE-COMPLIANCE, OBJECT-GROUP
::= { mplsIdGroups 1 } FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
RowPointer
FROM SNMPv2-TC -- [RFC2579]
mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup,
mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813]
-- MPLS-ID-STD-MIB module ends mplsLsrExtStdMIB MODULE-IDENTITY
END LAST-UPDATED
"201207150000Z" -- July 15, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
12. MPLS LSR Extension MIB definitions Kannan KV Sampath
Aricent,
India
Email: Kannan.Sampath@aricent.com
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN Sam Aldrin
Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
IMPORTS Email: aldrin.ietf@gmail.com
MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
RowPointer
FROM SNMPv2-TC -- [RFC2579]
mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup,
mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB; -- [RFC3813]
mplsLsrExtStdMIB MODULE-IDENTITY Thomas D. Nadeau
LAST-UPDATED Juniper Networks
"201204080000Z" -- April 08, 2012 10 Technology Park Drive, Westford, MA 01886
ORGANIZATION Email: tnadeau@juniper.net
"Multiprotocol Label Switching (MPLS) Working Group" "
CONTACT-INFO DESCRIPTION
" "Copyright (c) 2012 IETF Trust and the persons identified
Venkatesan Mahalingam as the document authors. All rights reserved.
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath This MIB module contains generic object definitions for
Aricent,
India
Email: Kannan.Sampath@aricent.com
Sam Aldrin MPLS LSR in transport networks."
Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com -- Revision history.
Thomas D. Nadeau REVISION
Juniper Networks "201207150000Z" -- July 15, 2012
10 Technology Park Drive, Westford, MA 01886 DESCRIPTION
Email: tnadeau@juniper.net "MPLS LSR specific MIB objects extension"
"
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
MPLS LSR in transport networks." -- Notifications
mplsLsrExtNotifications OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 0 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 }
-- Revision history. -- MPLS LSR common objects
mplsXCExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific
information about associated tunnel information"
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 }
REVISION mplsXCExtEntry OBJECT-TYPE
"201204080000Z" -- April 08, 2012 SYNTAX MplsXCExtEntry
DESCRIPTION MAX-ACCESS not-accessible
"MPLS LSR specific mib objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value STATUS current
DESCRIPTION
"An entry in this table extends the cross connect
information represented by an entry in
the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through
a sparse augmentation. An entry can be created by
a network administrator via SNMP SET commands, or in
response to signaling protocol events."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
-- traps INDEX { mplsXCIndex, mplsXCInSegmentIndex,
mplsLsrExtNotifications OBJECT IDENTIFIER mplsXCOutSegmentIndex }
::= { mplsLsrExtStdMIB 0 } ::= { mplsXCExtTable 1 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 }
-- MPLS LSR common objects MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTable OBJECT-TYPE mplsXCExtTunnelPointer RowPointer,
SYNTAX SEQUENCE OF MplsXCExtEntry mplsXCExtOppositeDirXCPtr RowPointer
MAX-ACCESS not-accessible }
STATUS current
DESCRIPTION
"This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific
information about associated tunnel information"
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 }
mplsXCExtEntry OBJECT-TYPE mplsXCExtTunnelPointer OBJECT-TYPE
SYNTAX MplsXCExtEntry SYNTAX RowPointer
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This read-only object indicates the back pointer to
the tunnel entry segment."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 }
STATUS current mplsXCExtOppositeDirXCPtr OBJECT-TYPE
DESCRIPTION SYNTAX RowPointer
"An entry in this table extends the cross connect MAX-ACCESS read-create
information represented by an entry in STATUS current
the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through DESCRIPTION
a sparse augmentation. An entry can be created by "This object indicates the pointer to the opposite
a network administrator via SNMP SET commands, or in direction XC entry. This object cannot be modified if
response to signaling protocol events." mplsXCRowStatus for the corresponding entry in the
REFERENCE mplsXCTable is active(1)."
"1. Multiprotocol Label Switching (MPLS) Label Switching REFERENCE
Router (LSR) Management Information Base (MIB), RFC 3813." "1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 2 }
INDEX { mplsXCIndex, mplsXCInSegmentIndex, mplsLsrExtGroups
mplsXCOutSegmentIndex } OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
::= { mplsXCExtTable 1 } mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
MplsXCExtEntry ::= SEQUENCE { -- Compliance requirement for fully compliant implementations.
mplsXCExtTunnelPointer RowPointer,
mplsXCOppositeDirXCPtr RowPointer
}
mplsXCExtTunnelPointer OBJECT-TYPE mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE
SYNTAX RowPointer STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "Compliance statement for agents that provide full support
DESCRIPTION for MPLS-LSR-EXT-STD-MIB.
"This read-only object indicates the back pointer to The mandatory group has to be implemented by all LSRs
the tunnel entry segment. This object cannot be modified that originate, terminate, or act as transit for
if mplsXCRowStatus for the corresponding entry in the TE-LSPs/tunnels.
mplsXCTable is active(1)." In addition, depending on the type of tunnels supported,
REFERENCE other groups become mandatory as explained below."
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 }
mplsXCOppositeDirXCPtr OBJECT-TYPE MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the pointer to the opposite
direction XC entry. This object cannot be modified if
mplsXCRowStatus for the corresponding entry in the
mplsXCTable is active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 2 }
mplsLsrExtGroups MANDATORY-GROUPS {
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } mplsInSegmentGroup,
mplsLsrExtCompliances mplsOutSegmentGroup,
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
-- Compliance requirement for fully compliant implementations. MODULE -- this module
mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE MANDATORY-GROUPS {
STATUS current mplsXCExtGroup
DESCRIPTION }
"Compliance statement for agents that provide full support
for MPLS-LSR-EXT-STD-MIB.
The mandatory group has to be implemented by all LSRs
that originate, terminate, or act as transit for
TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported,
other groups become mandatory as explained below."
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 ::= { mplsLsrExtCompliances 1 }
MANDATORY-GROUPS { -- Compliance requirement for implementations that provide
mplsInSegmentGroup, -- read-only access.
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
MODULE -- this module mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance requirement for implementations that only
provide read-only support for MPLS-LSR-EXT-STD-MIB.
Such devices can then be monitored but cannot be
configured using this MIB module."
MANDATORY-GROUPS { MODULE MPLS-LSR-STD-MIB
mplsXCExtGroup
}
OBJECT mplsXCExtTunnelPointer MANDATORY-GROUPS {
SYNTAX RowPointer mplsInterfaceGroup,
MIN-ACCESS read-only mplsInSegmentGroup,
DESCRIPTION mplsOutSegmentGroup,
"The only valid value for Tunnel Pointer is mplsTunnelTable mplsXCGroup,
entry." mplsPerfGroup
}
::= { mplsLsrExtCompliances 1 } MODULE -- this module
-- Compliance requirement for implementations that provide MANDATORY-GROUPS {
-- read-only access. mplsXCExtGroup
}
mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE OBJECT mplsXCExtTunnelPointer
STATUS current SYNTAX RowPointer
DESCRIPTION MIN-ACCESS read-only
"Compliance requirement for implementations that only DESCRIPTION
provide read-only support for MPLS-LSR-EXT-STD-MIB. "The only valid value for Tunnel Pointer is mplsTunnelTable
Such devices can then be monitored but cannot be entry."
configured using this MIB module."
MODULE MPLS-LSR-STD-MIB ::= { mplsLsrExtCompliances 2 }
MANDATORY-GROUPS { mplsXCExtGroup OBJECT-GROUP
mplsInterfaceGroup, OBJECTS {
mplsInSegmentGroup, mplsXCExtTunnelPointer,
mplsOutSegmentGroup, mplsXCExtOppositeDirXCPtr
mplsXCGroup, }
mplsPerfGroup STATUS current
} DESCRIPTION
"This object should be supported in order to access
the tunnel entry from XC entry."
::= { mplsLsrExtGroups 1 }
MODULE -- this module -- MPLS-LSR-EXT-STD-MIB module ends
END
MANDATORY-GROUPS { 13. MPLS Tunnel Extension MIB definitions
mplsXCExtGroup
}
OBJECT mplsXCExtTunnelPointer MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
SYNTAX RowPointer
MIN-ACCESS read-only
DESCRIPTION
"The only valid value for Tunnel Pointer is mplsTunnelTable
entry."
OBJECT mplsXCOppositeDirXCPtr IMPORTS
SYNTAX RowPointer MODULE-IDENTITY, OBJECT-TYPE, Counter32,
MIN-ACCESS read-only Counter64, zeroDotZero
DESCRIPTION FROM SNMPv2-SMI -- [RFC2578]
"The only valid value for Tunnel Pointer is mplsXCTable MODULE-COMPLIANCE, OBJECT-GROUP
entry." FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowStatus, RowPointer, StorageType
FROM SNMPv2-TC -- [RFC2579]
MplsGlobalId, MplsNodeId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsExtendedTunnelId
FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812]
;
::= { mplsLsrExtCompliances 2 } mplsTeExtStdMIB MODULE-IDENTITY
LAST-UPDATED
"201207150000Z" -- July 15, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
mplsXCExtGroup OBJECT-GROUP Kannan KV Sampath
OBJECTS { Aricent,
mplsXCExtTunnelPointer,
mplsXCOppositeDirXCPtr
}
STATUS current
DESCRIPTION
"This object should be supported in order to access
the tunnel entry from XC entry."
::= { mplsLsrExtGroups 1 }
-- MPLS-LSR-EXT-STD-MIB module ends India
END
13. MPLS Tunnel Extension MIB definitions Email: Kannan.Sampath@aricent.com
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN Sam Aldrin
Huawei Technologies
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
IMPORTS Thomas D. Nadeau
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Juniper Networks
Counter64, Gauge32, zeroDotZero, NOTIFICATION-TYPE 10 Technology Park Drive, Westford, MA 01886
FROM SNMPv2-SMI -- [RFC2578] Email: tnadeau@juniper.net
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP "
FROM SNMPv2-CONF -- [RFC2580] DESCRIPTION
TruthValue, RowStatus, RowPointer, StorageType "Copyright (c) 2012 IETF Trust and the persons identified
FROM SNMPv2-TC -- [RFC2579] as the document authors. All rights reserved.
MplsLocalId, MplsGlobalId, MplsNodeId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex
FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812]
;
mplsTeExtStdMIB MODULE-IDENTITY This MIB module contains generic object definitions for
LAST-UPDATED MPLS Traffic Engineering in transport networks."
"201204080000Z" -- April 08, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath -- Revision history.
Aricent,
India REVISION
Email: Kannan.Sampath@aricent.com "201207150000Z" -- July 15, 2012
Sam Aldrin DESCRIPTION
Huawei Technologies "MPLS TE MIB objects extension"
2330 Central Express Way,
Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com
Thomas D. Nadeau ::= { mplsStdMIB xxx } -- xxx to be replaced
Juniper Networks -- with correct value
10 Technology Park Drive, Westford, MA 01886
Email: tnadeau@juniper.net
"
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for -- Top level components of this MIB module.
MPLS Traffic Engineering in transport networks."
-- Revision history. -- Notifications
mplsTeExtNotifications OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 0 }
-- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 2 }
REVISION -- Start of MPLS Transport Profile Node configuration table
"201204080000Z" -- April 08, 2012 mplsTunnelExtNodeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table allows the administrator to map a node or
LSR Identifier (IP compatible [Global_Node_ID] or ICC)
with a local identifier.
DESCRIPTION This table is created to reuse the existing
"MPLS TE mib objects extension" mplsTunnelTable for MPLS based transport network
tunnels also.
Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for
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
Global_Node_ID or ICC with the local identifier of size
4 bytes (Unsigned32) value in order
to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
::= { mplsTeExtObjects 1 }
::= { mplsStdMIB xxx } -- xxx to be replaced mplsTunnelExtNodeConfigEntry OBJECT-TYPE
-- with correct value SYNTAX MplsTunnelExtNodeConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
-- Top level components of this MIB module. "An entry in this table represents a mapping
identification for the operator or service provider
with node or LSR.
-- traps As per [RFC6370], this mapping is
mplsTeExtNotifications OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 0 }
-- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 2 }
-- Start of MPLS Transport Profile Node configuration table represented as Global_Node_ID or ICC.
mplsNodeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsNodeConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table allows the administrator to map a node or
LSR Identifier (IP compatible [Global_Node_ID] or ICC)
with a local identifier.
This table is created to reuse the existing Note: Each entry in this table should have a unique
mplsTunnelTable for MPLS based transport network Global_ID and Node_ID combination."
tunnels also. INDEX { mplsTunnelExtNodeConfigLocalId }
Since the MPLS tunnel's Ingress/Egress LSR identifiers' ::= { mplsTunnelExtNodeConfigTable 1 }
size (Unsigned32) value is not compatible for
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
Global_Node_ID or ICC with the local identifier of size
4 bytes (Unsigned32) value in order
to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
::= { mplsTeExtObjects 1 }
mplsNodeConfigEntry OBJECT-TYPE MplsTunnelExtNodeConfigEntry ::= SEQUENCE {
SYNTAX MplsNodeConfigEntry mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId,
MAX-ACCESS not-accessible mplsTunnelExtNodeConfigGlobalId MplsGlobalId,
STATUS current mplsTunnelExtNodeConfigNodeId MplsNodeId,
DESCRIPTION mplsTunnelExtNodeConfigIccId MplsIccId,
mplsTunnelExtNodeConfigRowStatus RowStatus,
mplsTunnelExtNodeConfigStorageType StorageType
"An entry in this table represents a mapping }
identification for the operator or service provider
with node or LSR.
As per [RFC6370], this mapping is mplsTunnelExtNodeConfigLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is used in accommodating the bigger
size Global_Node_ID and/or ICC with lower size LSR
identifier in order to index the mplsTunnelTable.
represented as Global_Node_ID or ICC. The Local Identifier is configured between 1 and 16777215,
as valid IP address range starts from 16777216(01.00.00.00).
This range is chosen to identify the mplsTunnelTable's
Ingress/Egress LSR-id is IP address or Local identifier,
if the configured range is not IP address, administrator is
expected to retrieve the complete information
(Global_Node_ID or ICC) from mplsTunnelExtNodeConfigTable.
This way, existing mplsTunnelTable is reused for
bidirectional
tunnel extensions for MPLS based transport networks.
Note: Each entry in this table should have a unique This Local Identifier allows the administrator to assign
Global_ID and Node_ID combination." a unique identifier to map Global_Node_ID and/or ICC."
INDEX { mplsNodeConfigLocalId } ::= { mplsTunnelExtNodeConfigEntry 1 }
::= { mplsNodeConfigTable 1 }
MplsNodeConfigEntry ::= SEQUENCE { mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
mplsNodeConfigLocalId MplsLocalId, SYNTAX MplsGlobalId
mplsNodeConfigGlobalId MplsGlobalId, MAX-ACCESS read-write
mplsNodeConfigNodeId MplsNodeId, STATUS current
mplsNodeConfigIccId MplsIccId, DESCRIPTION
mplsNodeConfigRowStatus RowStatus, "This object indicates the Global Operator Identifier.
mplsNodeConfigStorageType StorageType This object value should be zero when
mplsTunnelExtNodeConfigIccId is configured with non-null
value."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsTunnelExtNodeConfigEntry 2 }
} mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the operator.
This object value should be zero when
mplsTunnelExtNodeConfigIccId is configured with non-null
value."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsTunnelExtNodeConfigEntry 3 }
mplsNodeConfigLocalId OBJECT-TYPE mplsTunnelExtNodeConfigIccId OBJECT-TYPE
SYNTAX MplsLocalId SYNTAX MplsIccId
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows the administrator to assign a unique "This object allows the operator or service provider to
local identifier to map Global_Node_ID or ICC." configure a unique MPLS-TP ITU-T Carrier Code (ICC)
::= { mplsNodeConfigEntry 1 } either for Ingress ID or Egress ID.
mplsNodeConfigGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object value should be zero when This object value should be zero when
mplsNodeConfigIccId is configured with non-null value." mplsTunnelExtNodeConfigGlobalId and
REFERENCE mplsTunnelExtNodeConfigNodeId are assigned with non-zero
"MPLS-TP Identifiers [RFC6370]." value."
::= { mplsNodeConfigEntry 2 } REFERENCE
"MPLS-TP Identifiers [RFC6370]."
mplsNodeConfigNodeId OBJECT-TYPE ::= { mplsTunnelExtNodeConfigEntry 4 }
SYNTAX MplsNodeId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the operator.
This object value should be zero when mplsNodeConfigIccId
is configured with non-null value."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsNodeConfigEntry 3 }
mplsNodeConfigIccId OBJECT-TYPE mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX MplsIccId SYNTAX RowStatus
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 administrator to create, modify,
configure a unique MPLS-TP ITU-T Carrier Code (ICC) and/or delete a row in this table."
either for Ingress ID or Egress ID. ::= { mplsTunnelExtNodeConfigEntry 5 }
This object value should be zero when mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
mplsNodeConfigGlobalId and mplsNodeConfigNodeId are SYNTAX StorageType
assigned with non-zero value." MAX-ACCESS read-create
REFERENCE STATUS current
"MPLS-TP Identifiers [RFC6370]." DESCRIPTION
::= { mplsNodeConfigEntry 4 } "This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsTunnelExtNodeConfigEntry 6 }
mplsNodeConfigRowStatus OBJECT-TYPE -- End of MPLS Transport Profile Node configuration table
SYNTAX RowStatus -- Start of MPLS Transport Profile Node IP compatible
MAX-ACCESS read-create -- mapping table
STATUS current
DESCRIPTION
"This object allows the administrator to create, modify,
and/or delete a row in this table."
::= { mplsNodeConfigEntry 5 }
mplsNodeConfigStorageType OBJECT-TYPE mplsTunnelExtNodeIpMapTable OBJECT-TYPE
SYNTAX StorageType SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsNodeConfigEntry 6 }
-- End of MPLS Transport Profile Node configuration table MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This read-only table allows the administrator to retrieve
the local identifier for a given Global_Node_ID in an IP
compatible operator environment.
-- Start of MPLS Transport Profile Node IP compatible This table MAY be used in on-demand and/or proactive
-- mapping table OAM operations to get the Ingress/Egress LSR identifier
(Local Identifier) from Src-Global_Node_ID
or Dst-Global_Node_ID and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
mplsNodeIpMapTable OBJECT-TYPE This table returns nothing when the associated entry
SYNTAX SEQUENCE OF MplsNodeIpMapEntry is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 2 }
MAX-ACCESS not-accessible mplsTunnelExtNodeIpMapEntry OBJECT-TYPE
STATUS current SYNTAX MplsTunnelExtNodeIpMapEntry
DESCRIPTION MAX-ACCESS not-accessible
"This read-only table allows the administrator to retrieve STATUS current
the local identifier for a given Global_Node_ID in an IP DESCRIPTION
compatible operator environment. "An entry in this table represents a mapping of
Global_Node_ID with the local identifier.
This table MAY be used in on-demand and/or proactive An entry in this table is created automatically when
OAM operations to get the Ingress/Egress LSR identifier the Local identifier is associated with Global_ID and
(Local Identifier) from Src-Global_Node_ID Node_Id in the mplsTunnelExtNodeConfigTable.
or Dst-Global_Node_ID and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry Note: Each entry in this table should have a unique
is not defined in mplsNodeConfigTable." Global_ID and Node_ID combination."
::= { mplsTeExtObjects 2 } INDEX { mplsTunnelExtNodeIpMapGlobalId,
mplsTunnelExtNodeIpMapNodeId
}
::= { mplsTunnelExtNodeIpMapTable 1 }
mplsNodeIpMapEntry OBJECT-TYPE MplsTunnelExtNodeIpMapEntry ::= SEQUENCE {
SYNTAX MplsNodeIpMapEntry mplsTunnelExtNodeIpMapGlobalId MplsGlobalId,
MAX-ACCESS not-accessible mplsTunnelExtNodeIpMapNodeId MplsNodeId,
STATUS current mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId
DESCRIPTION }
"An entry in this table represents a mapping of mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE
Global_Node_ID with the local identifier. SYNTAX MplsGlobalId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Global_ID."
::= { mplsTunnelExtNodeIpMapEntry 1 }
An entry in this table is created automatically when mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE
the Local identifier is associated with Global_ID and SYNTAX MplsNodeId
Node_Id in the mplsNodeConfigTable. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the
operator."
::= { mplsTunnelExtNodeIpMapEntry 2 }
Note: Each entry in this table should have a unique mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE
Global_ID and Node_ID combination." SYNTAX MplsExtendedTunnelId
INDEX { mplsNodeIpMapGlobalId, MAX-ACCESS read-only
mplsNodeIpMapNodeId STATUS current
} DESCRIPTION
::= { mplsNodeIpMapTable 1 } "This object contains an IP compatible local identifier
which is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIpMapEntry 3 }
MplsNodeIpMapEntry ::= SEQUENCE { -- End MPLS Transport Profile Node IP compatible table
mplsNodeIpMapGlobalId MplsGlobalId,
mplsNodeIpMapNodeId MplsNodeId,
mplsNodeIpMapLocalId MplsLocalId
}
mplsNodeIpMapGlobalId OBJECT-TYPE -- Start of MPLS Transport Profile Node ICC based table
SYNTAX MplsGlobalId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Global_ID."
::= { mplsNodeIpMapEntry 1 }
mplsNodeIpMapNodeId OBJECT-TYPE mplsTunnelExtNodeIccMapTable OBJECT-TYPE
SYNTAX MplsNodeId SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Node_ID within the "This read-only table allows the administrator to retrieve
operator." the local identifier for a given ICC operator in an ICC
::= { mplsNodeIpMapEntry 2 } operator environment.
mplsNodeIpMapLocalId OBJECT-TYPE This table MAY be used in on-demand and/or proactive
SYNTAX MplsLocalId OAM operations to get the Ingress/Egress LSR
MAX-ACCESS read-only identifier (Local Identifier) from Src-ICC
STATUS current or Dst-ICC and the Ingress and Egress LSR
DESCRIPTION identifiers are used to retrieve the tunnel entry.
"This object contains an IP compatible local identifier This table returns nothing when the associated entry
which is defined in mplsNodeConfigTable." is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsNodeIpMapEntry 3 } ::= { mplsTeExtObjects 3 }
-- End MPLS Transport Profile Node IP compatible table mplsTunnelExtNodeIccMapEntry OBJECT-TYPE
SYNTAX MplsTunnelExtNodeIccMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a mapping of ICC with
the local identifier.
-- Start of MPLS Transport Profile Node ICC based table An entry in this table is created automatically when
the Local identifier is associated with ICC in
the mplsTunnelExtNodeConfigTable."
INDEX { mplsTunnelExtNodeIccMapIccId }
::= { mplsTunnelExtNodeIccMapTable 1 }
mplsNodeIccMapTable OBJECT-TYPE MplsTunnelExtNodeIccMapEntry ::= SEQUENCE {
SYNTAX SEQUENCE OF MplsNodeIccMapEntry mplsTunnelExtNodeIccMapIccId MplsIccId,
MAX-ACCESS not-accessible mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
STATUS current }
DESCRIPTION
"This read-only table allows the administrator to retrieve
the local identifier for a given ICC operator in an ICC
operator environment.
This table MAY be used in on-demand and/or proactive mplsTunnelExtNodeIccMapIccId OBJECT-TYPE
OAM operations to get the Ingress/Egress LSR SYNTAX MplsIccId
identifier (Local Identifier) from Src-ICC MAX-ACCESS not-accessible
or Dst-ICC and the Ingress and Egress LSR STATUS current
identifiers are used to retrieve the tunnel entry. DESCRIPTION
This table returns nothing when the associated entry "This object allows the operator or service provider to
is not defined in mplsNodeConfigTable." configure a unique MPLS-TP ITU-T Carrier Code (ICC)
::= { mplsTeExtObjects 3 } either for Ingress or Egress LSR ID.
mplsNodeIccMapEntry OBJECT-TYPE The ICC is a string of one to six characters, each
SYNTAX MplsNodeIccMapEntry character being either alphabetic (i.e. A-Z) or
MAX-ACCESS not-accessible numeric (i.e. 0-9) characters. Alphabetic characters
STATUS current in the ICC should be represented with upper case
DESCRIPTION letters."
"An entry in this table represents a mapping of ICC with ::= { mplsTunnelExtNodeIccMapEntry 1 }
the local identifier.
An entry in this table is created automatically when mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE
the Local identifier is associated with ICC in SYNTAX MplsExtendedTunnelId
the mplsNodeConfigTable." MAX-ACCESS read-only
INDEX { mplsNodeIccMapIccId } STATUS current
::= { mplsNodeIccMapTable 1 } DESCRIPTION
"This object contains an ICC based local identifier
which is defined in mplsTunnelExtNodeConfigTable."
MplsNodeIccMapEntry ::= SEQUENCE { ::= { mplsTunnelExtNodeIccMapEntry 2 }
mplsNodeIccMapIccId MplsIccId,
mplsNodeIccMapLocalId MplsLocalId
}
mplsNodeIccMapIccId OBJECT-TYPE -- End MPLS Transport Profile Node ICC based table
SYNTAX MplsIccId -- Start of MPLS Tunnel table extension
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
configure a unique MPLS-TP ITU-T Carrier Code (ICC)
either for Ingress or Egress LSR ID.
The ICC is a string of one to six characters, each mplsTunnelExtTable OBJECT-TYPE
character being either alphabetic (i.e. A-Z) or SYNTAX SEQUENCE OF MplsTunnelExtEntry
numeric (i.e. 0-9) characters. Alphabetic characters MAX-ACCESS not-accessible
in the ICC should be represented with upper case STATUS current
letters." DESCRIPTION
::= { mplsNodeIccMapEntry 1 } "This table represents MPLS-TP specific extensions to
mplsTunnelTable.
mplsNodeIccMapLocalId OBJECT-TYPE As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based
SYNTAX MplsLocalId co-routed bidirectional tunnel,
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an ICC based local identifier
which is defined in mplsNodeConfigTable."
::= { mplsNodeIccMapEntry 2 } A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num
-- End MPLS Transport Profile Node ICC based table LSP_ID for IP based associated bidirectional tunnel,
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
-- Start of MPLS Tunnel table extension mplsTunnelTable is reused for forming the LSP_ID
as follows,
mplsTunnelExtTable OBJECT-TYPE Source Tunnel_Num is mapped with mplsTunnelIndex,
SYNTAX SEQUENCE OF MplsTunnelExtEntry Source Node_ID is mapped with
MAX-ACCESS not-accessible mplsTunnelIngressLSRId, Destination Node_ID is
STATUS current mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
DESCRIPTION mplsTunnelInstance.
"This table represents MPLS-TP specific extensions to
mplsTunnelTable.
As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based Source Global_Node_ID and/or ICC and Destination
co-routed bidirectional tunnel, Global_Node_ID and/or ICC are maintained in the
mplsTunnelExtNodeConfigTable and
mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsTeExtObjects 4 }
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: mplsTunnelExtEntry OBJECT-TYPE
Node_ID::Tunnel_Num}::LSP_Num SYNTAX MplsTunnelExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents MPLS-TP
specific additional tunnel configurations."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
LSP_ID for IP based associated bidirectional tunnel, MplsTunnelExtEntry ::= SEQUENCE {
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: mplsTunnelExtOppositeDirPtr RowPointer,
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue
}
mplsTunnelTable is reused for forming the LSP_ID mplsTunnelExtOppositeDirPtr OBJECT-TYPE
as follows, SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels.
Source Tunnel_Num is mapped with mplsTunnelIndex, This object holds the opposite direction tunnel entry
Source Node_ID is mapped with if the bidirectional tunnel is setup by configuring two
mplsTunnelIngressLSRId, Destination Node_ID is tunnel entries in mplsTunnelTable.
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance.
Source Global_Node_ID and/or ICC and Destination The value of zeroDotZero indicates single tunnel entry
Global_Node_ID and/or ICC are maintained in the is used for bidirectional tunnel setup."
mplsNodeConfigTable and mplsNodeConfigLocalId is DEFVAL { zeroDotZero }
used to create an entry in mplsTunnelTable." ::= { mplsTunnelExtEntry 1 }
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsTeExtObjects 4 }
mplsTunnelExtEntry OBJECT-TYPE mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE
SYNTAX MplsTunnelExtEntry SYNTAX TruthValue
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents MPLS-TP "Denotes whether or not this tunnel uses
specific additional tunnel configurations." mplsTunnelExtOppositeDirPtr for identifying the opposite
INDEX { direction tunnel information. Note that if this variable
mplsTunnelIndex, is set to true then the mplsTunnelExtOppositeDirPtr should
mplsTunnelInstance, point to the first accessible row of the opposite
mplsTunnelIngressLSRId, direction tunnel."
mplsTunnelEgressLSRId DEFVAL { false }
} ::= { mplsTunnelExtEntry 2 }
::= { mplsTunnelExtTable 1 }
MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelOppositeDirPtr RowPointer,
mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue
}
mplsTunnelOppositeDirPtr OBJECT-TYPE mplsTunnelExtDestTnlIndex OBJECT-TYPE
SYNTAX RowPointer SYNTAX MplsTunnelIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels. same tunnel or in the different tunnels.
This object holds the opposite direction tunnel entry This object holds the same value as that of the
if the bidirectional tunnel is setup by configuring two mplsTunnelIndex of mplsTunnelEntry if the forward and
tunnel entries in mplsTunnelTable. reverse LSPs are in the same tunnel. Otherwise,
this object holds the value of the other direction
associated LSP's mplsTunnelIndex from a different
tunnel.
The value of zeroDotZero indicates single tunnel entry The values of this object and the
is used for bidirectional tunnel setup." mplsTunnelExtDestTnlLspIndex object together can be used
DEFVAL { zeroDotZero } to identify an opposite direction LSP i.e. if the
::= { mplsTunnelExtEntry 1 } mplsTunnelIndex and mplsTunnelInstance hold the value
for forward LSP, this object and
mplsTunnelExtDestTnlLspIndex can be used to retrieve
the reverse direction LSP and vice versa.
mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE This object and mplsTunnelExtDestTnlLspIndex values
SYNTAX TruthValue provide the first two indices of tunnel entry and
MAX-ACCESS read-create the remaining indices can be derived as follows,
STATUS current if both the forward and reverse LSPs are present in
DESCRIPTION the same tunnel, the opposite direction LSP's Ingress
"Denotes whether or not this tunnel uses and Egress Identifier will be same for both the LSPs,
mplsTunnelOppositeDirPtr for identifying the opposite else the Ingress and Egress Identifiers should be
direction tunnel information. Note that if this variable swapped in order to index the other direction tunnel."
is set to true then the mplsTunnelOppositeDirPtr should
point to the first accessible row of the opposite
direction tunnel."
DEFVAL { false }
::= { mplsTunnelExtEntry 2 }
mplsTunnelExtDestTnlIndex OBJECT-TYPE ::= { mplsTunnelExtEntry 3 }
SYNTAX MplsTunnelIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels.
This object holds the same value as that of the mplsTunnelExtDestTnlLspIndex OBJECT-TYPE
mplsTunnelIndex of mplsTunnelEntry if the forward and SYNTAX MplsTunnelInstanceIndex
reverse LSPs are in the same tunnel. Otherwise, MAX-ACCESS read-create
this object holds the value of the other direction STATUS current
associated LSP's mplsTunnelIndex from a different DESCRIPTION
tunnel. "This object is applicable only for the bidirectional
tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels.
The values of this object and the This object should contain different value if both the
mplsTunnelExtDestTnlLspIndex object together can be used forward and reverse LSPs present in the same tunnel.
to identify an opposite direction LSP i.e. if the
mplsTunnelIndex and mplsTunnelInstance hold the value
for forward LSP, this object and
mplsTunnelExtDestTnlLspIndex can be used to retrieve
the reverse direction LSP and vice versa.
This object and mplsTunnelExtDestTnlLspIndex values This object can contain same value or different values
provide the first two indices of tunnel entry and if the forward and reverse LSPs present in the different
the remaining indices can be derived as follows, tunnels."
if both the forward and reverse LSPs are present in
the same tunnel, the opposite direction LSP's Ingress
and Egress Identifier will be same for both the LSPs,
else the Ingress and Egress Identifiers should be
swapped in order to index the other direction tunnel."
::= { mplsTunnelExtEntry 3 } ::= { mplsTunnelExtEntry 4 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE mplsTunnelExtDestTnlValid OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "Denotes whether or not this tunnel uses
tunnel that has the forward and reverse LSPs in the mplsTunnelExtDestTnlIndex and
same tunnel or in the different tunnels. mplsTunnelExtDestTnlLspIndex for identifying
the opposite direction tunnel information. Note that if
this variable is set to true then the
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite direction tunnel indices."
DEFVAL { false }
::= { mplsTunnelExtEntry 5 }
This object should contain different value if both the -- End of MPLS Tunnel table extension
forward and reverse LSPs present in the same tunnel.
This object can contain same value or different values mplsTunnelExtReversePerfTable OBJECT-TYPE
if the forward and reverse LSPs present in the different SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry
tunnels." MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table extends the mplsTunnelTable to provide
per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable.
::= { mplsTunnelExtEntry 4 } For links that do not transport packets, these packet
counters cannot be maintained. For such links, attempts
to read the objects in this table will return
noSuchInstance."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE)Management Information Base (MIB),
RFC 3812."
::= { mplsTeExtObjects 5 }
mplsTunnelExtDestTnlValid OBJECT-TYPE mplsTunnelExtReversePerfEntry OBJECT-TYPE
SYNTAX TruthValue SYNTAX MplsTunnelExtReversePerfEntry
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel uses "An entry in this table is created by the LSR for every
mplsTunnelExtDestTnlIndex and bidirectional MPLS tunnel where packets are visible to the
mplsTunnelExtDestTnlLspIndex for identifying LSR."
the opposite direction tunnel information. Note that if INDEX {
this variable is set to true then the mplsTunnelIndex,
mplsTunnelExtDestTnlIndex and mplsTunnelInstance,
mplsTunnelExtDestTnlLspIndex objects should have mplsTunnelIngressLSRId,
the valid opposite direction tunnel indices." mplsTunnelEgressLSRId
DEFVAL { false } }
::= { mplsTunnelExtEntry 5 } ::= { mplsTunnelExtReversePerfTable 1 }
-- End of MPLS Tunnel table extension MplsTunnelExtReversePerfEntry ::= SEQUENCE {
mplsTunnelExtReversePerfPackets Counter32,
mplsTunnelExtReversePerfHCPackets Counter64,
mplsTunnelExtReversePerfErrors Counter32,
mplsTunnelExtReversePerfBytes Counter32,
mplsTunnelExtReversePerfHCBytes Counter64
}
mplsTunnelReversePerfTable OBJECT-TYPE mplsTunnelExtReversePerfPackets OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelReversePerfEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends the mplsTunnelTable to provide "Number of packets forwarded on the tunnel in the reverse
per-tunnel packet performance information for the reverse direction if it is bidirectional.
direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable.
For links that do not transport packets, these packet This object represents the 32-bit value of the least
counters cannot be maintained. For such links, attempts significant part of the 64-bit value if both
to read the objects in this table will return mplsTunnelExtReversePerfHCPackets and this object
noSuchInstance." are returned.
REFERENCE For links that do not transport packets, this packet
"1. Multiprotocol Label Switching (MPLS) Traffic counter cannot be maintained. For such links, this value
Engineering (TE)Management Information Base (MIB), will return noSuchInstance."
RFC 3812." ::= { mplsTunnelExtReversePerfEntry 1 }
::= { mplsTeExtObjects 5 }
mplsTunnelReversePerfEntry OBJECT-TYPE mplsTunnelExtReversePerfHCPackets OBJECT-TYPE
SYNTAX MplsTunnelReversePerfEntry SYNTAX Counter64
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every "High-capacity counter for number of packets forwarded on
bidirectional MPLS tunnel where packets are visible to the the tunnel in the reverse direction if it is
LSR." bidirectional.
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelReversePerfTable 1 }
MplsTunnelReversePerfEntry ::= SEQUENCE { For links that do not transport packets, this packet
mplsTunnelReversePerfPackets Counter32, counter cannot be maintained. For such links, this value
mplsTunnelReversePerfHCPackets Counter64, will return noSuchInstance."
mplsTunnelReversePerfErrors Counter32, ::= { mplsTunnelExtReversePerfEntry 2 }
mplsTunnelReversePerfBytes Counter32, mplsTunnelExtReversePerfErrors OBJECT-TYPE
mplsTunnelReversePerfHCBytes Counter64 SYNTAX Counter32
} MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of errored packets received on the tunnel in
the reverse direction if it is bidirectional. For links
that do not transport packets, this packet counter cannot
be maintained. For such links, this value will return
noSuchInstance."
::= { mplsTunnelExtReversePerfEntry 3 }
mplsTunnelReversePerfPackets OBJECT-TYPE mplsTunnelExtReversePerfBytes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets forwarded on the tunnel in the reverse "Number of bytes forwarded on the tunnel in the reverse
direction if it is bidirectional. direction if it is bidirectional.
This object represents the 32-bit value of the least This object represents the 32-bit value of the least
significant part of the 64-bit value if both significant part of the 64-bit value if both
mplsTunnelReversePerfHCPackets and this object mplsTunnelExtReversePerfHCBytes and this object are returned.
are returned.
For links that do not transport packets, this packet For links that do not transport packets, this packet
counter cannot be maintained. For such links, this value counter cannot be maintained. For such links, this value
will return noSuchInstance." will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 1 } ::= { mplsTunnelExtReversePerfEntry 4 }
mplsTunnelReversePerfHCPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High-capacity counter for number of packets forwarded on
the tunnel in the reverse direction if it is
bidirectional.
For links that do not transport packets, this packet mplsTunnelExtReversePerfHCBytes OBJECT-TYPE
counter cannot be maintained. For such links, this value SYNTAX Counter64
will return noSuchInstance." MAX-ACCESS read-only
::= { mplsTunnelReversePerfEntry 2 } STATUS current
DESCRIPTION
"High-capacity counter for number of bytes forwarded on the
tunnel in the reverse direction if it is bidirectional.
mplsTunnelReversePerfErrors OBJECT-TYPE For links that do not transport packets, this packet
SYNTAX Counter32 counter cannot be maintained. For such links, this value
MAX-ACCESS read-only will return noSuchInstance."
STATUS current ::= { mplsTunnelExtReversePerfEntry 5 }
DESCRIPTION
"Number of errored packets received on the tunnel in
the reverse direction if it is bidirectional. For links
that do not transport packets, this packet counter cannot
be maintained. For such links, this value will return
noSuchInstance."
::= { mplsTunnelReversePerfEntry 3 }
mplsTunnelReversePerfBytes OBJECT-TYPE -- Notifications.
SYNTAX Counter32 -- Notification objects need to be added here.
MAX-ACCESS read-only -- End of notifications.
STATUS current
DESCRIPTION
"Number of bytes forwarded on the tunnel in the reverse
direction if it is bidirectional.
This object represents the 32-bit value of the least -- Module compliance.
significant part of the 64-bit value if both
mplsTunnelReversePerfHCBytes and this object are returned.
For links that do not transport packets, this packet mplsTeExtGroups
counter cannot be maintained. For such links, this value OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 4 }
mplsTunnelReversePerfHCBytes OBJECT-TYPE mplsTeExtCompliances
SYNTAX Counter64 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"High-capacity counter for number of bytes forwarded on the
tunnel in the reverse direction if it is bidirectional.
For links that do not transport packets, this packet -- Compliance requirement for fully compliant implementations.
counter cannot be maintained. For such links, this value
will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 5 }
-- Notifications. mplsTeExtModuleFullCompliance MODULE-COMPLIANCE
-- Notifications objects need to be added here. STATUS current
-- End of notifications. DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-TE-EXT-STD-MIB module."
-- Module compliance. MODULE -- this module
mplsTeExtGroups -- The mandatory group has to be implemented by all
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } -- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
mplsTeExtCompliances MANDATORY-GROUPS {
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } mplsTunnelExtGroup
}
-- Compliance requirement for fully compliant implementations. GROUP mplsTunnelExtIpOperatorGroup
mplsTeExtModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "This group is mandatory for devices which support
support the MPLS-TE-EXT-STD-MIB module." configuration of IP based identifier tunnels."
MODULE -- this module GROUP mplsTunnelExtIccOperatorGroup
-- The mandatory group has to be implemented by all DESCRIPTION
-- LSRs that originate/terminate MPLS-TP tunnels. "This group is mandatory for devices which support
-- In addition, depending on the type of tunnels configuration of ICC based tunnels."
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS { ::= { mplsTeExtCompliances 1 }
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup -- Compliance requirement for read-only implementations.
DESCRIPTION mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
"This group is mandatory for devices which support STATUS current
configuration of IP based identifier tunnels." DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-TE-EXT-STD-MIB module."
GROUP mplsTunnelExtIccOperatorGroup MODULE -- this module
DESCRIPTION
"This group is mandatory for devices which support
configuration of ICC based tunnels."
::= { mplsTeExtCompliances 1 } -- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
-- Compliance requirement for read-only implementations. MANDATORY-GROUPS {
mplsTunnelExtGroup
}
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE GROUP mplsTunnelExtIpOperatorGroup
STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "This group is mandatory for devices which support
support the MPLS-TE-EXT-STD-MIB module." configuration of IP based identifier tunnels."
MODULE -- this module
-- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS {
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup
DESCRIPTION
"This group is mandatory for devices which support
configuration of IP based identifier tunnels."
GROUP mplsTunnelExtIccOperatorGroup GROUP mplsTunnelExtIccOperatorGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
configuration of ICC based tunnels." configuration of ICC based tunnels."
::= { mplsTeExtCompliances 2 } ::= { mplsTeExtCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsTunnelExtGroup OBJECT-GROUP mplsTunnelExtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsTunnelOppositeDirPtr, mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid, mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex, mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex, mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid, mplsTunnelExtDestTnlValid,
mplsTunnelReversePerfPackets, mplsTunnelExtReversePerfPackets,
mplsTunnelReversePerfHCPackets, mplsTunnelExtReversePerfHCPackets,
mplsTunnelReversePerfErrors, mplsTunnelExtReversePerfErrors,
mplsTunnelReversePerfBytes, mplsTunnelExtReversePerfBytes,
mplsTunnelReversePerfHCBytes mplsTunnelExtReversePerfHCBytes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to "Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the implement tunnels. In addition, depending on the
operating environment, the following groups are operating environment, the following groups are
mandatory." mandatory."
::= { mplsTeExtGroups 1 } ::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP mplsTunnelExtIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsNodeConfigGlobalId, OBJECTS { mplsTunnelExtNodeConfigGlobalId,
mplsNodeConfigNodeId, mplsTunnelExtNodeConfigNodeId,
mplsNodeConfigRowStatus, mplsTunnelExtNodeConfigRowStatus,
mplsNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsNodeIpMapLocalId mplsTunnelExtNodeIpMapLocalId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement IP compatible tunnels." "Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 } ::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP mplsTunnelExtIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsNodeConfigIccId, OBJECTS { mplsTunnelExtNodeConfigIccId,
mplsNodeConfigRowStatus, mplsTunnelExtNodeConfigRowStatus,
mplsNodeConfigStorageType, mplsTunnelExtNodeConfigStorageType,
mplsNodeIccMapLocalId mplsTunnelExtNodeIccMapLocalId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object(s) needed to implement ICC based tunnels." "Object(s) needed to implement ICC based tunnels."
::= { mplsTeExtGroups 3 } ::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends -- MPLS-TE-EXT-STD-MIB module ends
END END
14. Security Consideration 14. Security Consideration
There is a number of management objects defined in this MIB module There is a number of management objects defined in this MIB module
that has a MAX-ACCESS clause of read-write.. Such objects may be that has a MAX-ACCESS clause of read-write.. Such objects may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
The support for SET operations in a non-secure environment without The support for SET operations in a non-secure environment without
proper protection can have a negative effect on network proper protection can have a negative effect on network
operations. operations.
skipping to change at page 46, line 52 skipping to change at page 46, line 38
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.
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 and Muly Ilan for their valuable Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Joan Cucchiara
comments. 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
 End of changes. 290 change blocks. 
1203 lines changed or deleted 1190 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/