draft-ietf-mpls-tp-te-mib-01.txt   draft-ietf-mpls-tp-te-mib-02.txt 
Network Working Group Network Working Group
INTERNET-DRAFT M.Venkatesan INTERNET-DRAFT M.Venkatesan
Intended Status: Standards Track Kannan KV Sampath Intended Status: Standards Track Dell Inc.
Expires: June 15, 2012 Aricent Expires: September 13, 2012 Kannan KV Sampath
Aricent
Sam K. Aldrin Sam K. Aldrin
Huawei Technologies Huawei Technologies
Thomas D. Nadeau Thomas D. Nadeau
CA Technologies CA Technologies
December 15, 2011 March 12, 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-01.txt draft-ietf-mpls-tp-te-mib-02.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 46 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 June 15, 2012. This Internet-Draft will expire on September 13, 2012.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 19 skipping to change at page 3, line 19
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 This MIB module should be used in conjunction with the MPLS traffic
Engineering MIB [RFC3812] and companion document MPLS Label Switch Engineering MIB [RFC3812] and companion document MPLS Label Switch
Router MIB [RFC3813] for MPLS based traffic engineering configuration Router MIB [RFC3813] for MPLS based traffic engineering configuration
and management. 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", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to
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].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 42 skipping to change at page 3, line 42
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC2578, STD 58, RFC2579 and STD58, RFC2580. RFC2578, STD 58, RFC2579 and STD58, RFC2580.
3. Overview 3. Overview
3.1 Conventions used in this document 3.1 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in [RFC2119].
3.2 Terminology 3.2 Terminology
This document uses terminology from the MPLS architecture document This document uses terminology from the MPLS architecture document
[RFC3031], MPLS Traffic Engineering Management information [RFC3812], [RFC3031], MPLS Traffic Engineering Management information [RFC3812],
MPLS Label Switch Router MIB [RFC3813] and MPLS-TP Identifiers MPLS Label Switch Router MIB [RFC3813] and MPLS-TP Identifiers
document [TPIDS]. document [RFC6370].
3.3 Acronyms 3.3 Acronyms
GMPLS: Generalized Multi-Protocol Label Switching GMPLS: Generalized Multi-Protocol Label Switching
ICC: ITU Carrier Code ICC: ITU Carrier Code
IP: Internet Protocol IP: Internet Protocol
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
MPLS: Multi-Protocol Label Switching MPLS: Multi-Protocol Label Switching
MPLS-TP: MPLS Transport Profile MPLS-TP: MPLS Transport Profile
skipping to change at page 4, line 50 skipping to change at page 4, line 50
- A node configuration table (mplsNodeConfigTable) is used to - A node configuration table (mplsNodeConfigTable) is used to
translate the Global_Node_ID or ICC to the local identifier translate the Global_Node_ID or ICC to the local identifier
in order to index mplsTunnelTable. 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 [TPIDS]. 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. mplsNodeConfigTable
The mplsNodeConfigTable is used to assign a local identifier for a The mplsNodeConfigTable is used to assign a local identifier for a
given ICC or Global_Node_ID combination as defined in [TPIDS]. given ICC or Global_Node_ID combination as defined in [RFC6370].
An ICC is a string of one to six characters, each character being An ICC is a string of one to six characters, each character being
either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. either alphabetic (i.e. A-Z) or 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. 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
skipping to change at page 6, line 25 skipping to change at page 6, line 25
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
This table augments 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.
7. MIB Module Interdependencies 7. MIB Module Interdependencies
This section provides an overview of the relationship between the This section provides an overview of the relationship between the
MPLS-TP TE MIB module and other MPLS MIB modules. MPLS-TP TE MIB module and other MPLS MIB modules.
The arrows in the following diagram show a 'depends on' The arrows in the following diagram show a 'depends on'
relationship. A relationship "MIB module A depends on MIB module B" relationship. A relationship "MIB module A depends on MIB module B"
means that MIB module A uses an object, object identifier, or means that MIB module A uses an object, object identifier, or
textual convention defined in MIB module B, or that MIB module A textual convention defined in MIB module B, or that MIB module A
contains a pointer (index or RowPointer) to an object in contains a pointer (index or RowPointer) to an object in
skipping to change at page 7, line 39 skipping to change at page 7, line 39
- MPLS-TE-STD-MIB [RFC3812] contains references to objects in - MPLS-TE-STD-MIB [RFC3812] contains references to objects in
MPLS-ID-STD-MIB. MPLS-ID-STD-MIB.
- 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 [RFC 3812] 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 [RFC 3813] 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
skipping to change at page 8, line 35 skipping to change at page 8, line 35
the Global_Node_ID and/or ICC with the local number in order to the Global_Node_ID and/or ICC with the local number in order to
accommodate in the existing tunnel table's ingress/egress LSR-id. 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
co-routed bidirectional tunnel setup. This example provides bidirectional tunnel setup. This example provides the usage of
the usage of MPLS-TP Tunnel MIB along with the extended new MIB MPLS-TP Tunnel MIB along with the extended new MIB modules introduced
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 configuration signaled via control plane. This example considers accessing mib
on a head-end LSR to setup a static MPLS-TP tunnel. Only relevant objects on a head-end for a static MPLS-TP tunnel.
objects which are applicable for MPLS-TP tunnel are illustrated here. Only relevant objects which are applicable for MPLS-TP tunnel are
illustrated here.
In mplsNodeConfigTable: In mplsNodeConfigTable:
{ {
-- Non-IP Ingress LSR-Id (Index to the table) -- Non-IP Ingress LSR-Id (Index to the table)
mplsNodeConfigLocalId = 1, mplsNodeConfigLocalId = 1,
mplsNodeConfigGlobalId = 1234, mplsNodeConfigGlobalId = 1234,
mplsNodeConfigNodeId = 10, mplsNodeConfigNodeId = 10,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsNodeConfigRowStatus = createAndGo (4) mplsNodeConfigRowStatus = createAndGo (4)
-- Non-IP Egress LSR-Id (Index to the table) -- Non-IP Egress LSR-Id (Index to the table)
mplsNodeConfigLocalId = 2, mplsNodeConfigLocalId = 2,
mplsNodeConfigGlobalId = 1234, mplsNodeConfigGlobalId = 1234,
mplsNodeConfigNodeId = 20, mplsNodeConfigNodeId = 20,
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsNodeConfigRowStatus = createAndGo (4) mplsNodeConfigRowStatus = createAndGo (4)
} }
This will create an entry in the mplsNodeConfigTable for a This will create an entry in the mplsNodeConfigTable 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 mplsNodeIpMapTable table is populated
automatically upon creating an entry in mplsNodeConfigTable and automatically upon creating an entry in mplsNodeConfigTable and
this table is used to retrieve the local identifier for the given this table is used to retrieve the local identifier for the given
Global_Node_ID. Global_Node_ID.
In mplsNodeIpMapTable: In mplsNodeIpMapTable:
{ {
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsNodeIpMapGlobalId = 1234, mplsNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsNodeIpMapNodeId = 10, mplsNodeIpMapNodeId = 10,
mplsNodeIpMapLocalId = 1 mplsNodeIpMapLocalId = 1
-- Global_ID (Index to the table) -- Global_ID (Index to the table)
mplsNodeIpMapGlobalId = 1234, mplsNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table) -- Node Identifier (Index to the table)
mplsNodeIpMapNodeId = 20, mplsNodeIpMapNodeId = 20,
mplsNodeIpMapLocalId = 2 mplsNodeIpMapLocalId = 2
} }
The following denotes the configured tunnel "head" entry: 9.1 Example of MPLS-TP co-routed bidirectional tunnel setup
The following denotes the configured co-routed bidirectional
tunnel "head" entry:
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 mplsNodeConfigTable for Ingress
LSR-Id LSR-Id
mplsTunnelIngressLSRId = 1, mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsNodeConfigTable for Egress -- Local map number created in mplsNodeConfigTable for Egress
LSR-Id LSR-Id
mplsTunnelEgressLSRId = 2, mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP forward 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.12, 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,
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)
} }
In mplsTunnelTable: 9.1.2 mplsTunnelExtEntry
{ -- An MPLS extension table
mplsTunnelIndex = 1, In mplsTunnelExtTable:
mplsTunnelInstance = 2, {
-- Local map number created in mplsNodeConfigTable for Ingress -- This opposite direction tunnel pointer MAY be point to 0.0
LSR-Id -- if co-routed bidirectional tunnel is managed by single tunnel
mplsTunnelIngressLSRId = 1, -- entry
-- Local map number created in mplsNodeConfigTable for Egress mplsTunnelOppositeDirTnlPtr = 0.0
LSR-Id }
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP reverse LSP",
mplsTunnelDescr = "West to East",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.4.0.0.0.16.1.0,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column We must next create the appropriate in-segment and out-segment
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, entries. These are done in [RFC3813] using the mplsInSegmentTable
mplsTunnelInstancePriority = 1, and mplsOutSegmentTable.
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
Now the TP specific Tunnel parameters are configured in 9.1.3 Forward direction mplsOutSegmentEntry
the extended Tunnel table For the forward direction.
In mplsTunnelExtTable: In mplsOutSegmentTable:
{ {
Index = same as one used for mplsTunnelTable, mplsOutSegmentIndex = 0x0000001,
-- As per [TPIDS] LSP_ID is defined as follows, mplsOutSegmentInterface = 13, -- outgoing interface
-- For corouted bidirectional tunnel mplsOutSegmentPushTopLabel = true(1),
-- LSP_ID => East-Global_Node_ID::East-Tunnel_Num:: mplsOutSegmentTopLabel = 22, -- outgoing label
-- West-Global_Node_ID::West-Tunnel_Num::LSP_Num
-- LSP_ID of this tunnel: 1234_10::1::1234_20::1::0
-- Where,
-- LSP_Num - 0 indicates the configured head end tunnel.
-- West tunnel number is assigned in the destination -- RowPointer MUST point to the first accessible column.
-- tunnel index, mplsOutSegmentTrafficParamPtr = 0.0,
-- single LSP number is common for both forward and reverse mplsOutSegmentRowStatus = createAndGo (4)
-- directions, as the single tunnel head entry originates }
-- both the forward and reverse LSPs.
-- mplsTunnelExtDestTnlIndex = West-Tunnel_Num
-- mplsTunnelExtDestTnlLspIndex = LSP_Num
mplsTunnelExtDestTnlIndex = 1, 9.1.4 Reverse direction mplsInSegmentEntry
mplsTunnelExtDestTnlLspIndex = 0
-- For associated bidirectional tunnel For the reverse direction.
-- LSP_ID => East-Global_Node_ID::East-Tunnel_Num::
-- East-LSP_Num::West-Global_Node_ID::
-- West-Tunnel_Num::West-LSP_Num
-- West tunnel number is assigned in the destination
-- tunnel index, since the head end tunnel is different for
-- both the forward and reverse direction LSPs,
-- Destination LSP index points the reverse direction LSP
-- in a different tunnel.
-- mplsTunnelExtDestTnlIndex = West-Tunnel_Num
-- mplsTunnelExtDestTnlLspIndex = West-LSP_Num
} In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
We must next create the appropriate in-segment and out-segment -- RowPointer MUST point to the first accessible column.
entries. These are done in [RFC3813] using the mplsInSegmentTable mplsInSegmentTrafficParamPtr = 0.0,
and mplsOutSegmentTable. mplsInSegmentRowStatus = createAndGo (4)
}
For the forward direction. Next, two cross-connect entries are created in the mplsXCTable of the
MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together.
In mplsOutSegmentTable: 9.1.5 Forward direction mplsXCEntry
{
mplsOutSegmentIndex = 0x00000012,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accessible column. In mplsXCTable:
mplsOutSegmentTrafficParamPtr = 0.0, {
mplsOutSegmentRowStatus = createAndGo (4) mplsXCIndex = 0x01,
} mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
For the reverse direction. }
In mplsInSegmentTable: 9.1.6 Reverse direction mplsXCEntry
{
mplsInSegmentIndex = 0x00000016 In mplsXCTable:
mplsInSegmentLabel = 21, -- incoming label {
mplsInSegmentNPop = 1, mplsXCIndex = 0x01,
mplsInSegmentInterface = 13, -- incoming interface mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
This table entry is extended by entry in the
mplsXCExtTable. Note that the nature of the 'extends'
relationship is a sparse augmentation so that the entry in the
mplsXCExtTable has the same index values as the entry in
the mplsXCTable.
9.1.5 Forward direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
9.1.6 Reverse direction mplsXCExtEntry
Next for the reverse direction:
In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
9.1.7 mplsTunnelReversePerfTable
The mplsTunnelReversePerfTable SHOULD be populated incase
the single tunnel entry is used for co-routed bidirectional tunnel
setup. The mplsTunnelPerfTable will have the forward direction
LSP performance counters and mplsTunnelReversePerfTable will have
the reverse direction LSP performance counters.
9.2 Example of MPLS-TP associated bidirectional tunnel setup
The MPLS-TP associated bidirectional tunnel has two different
direction tunnels[Forward and Reverse LSPs] and these are
associated together using mplsTunnelExtTable. Two different
tunnel entries for both forward and reverse direction MAY be used
for co-routed bidirectional tunnel as well.
The following denotes the configured associated bidirectional
forward tunnel "head" entry:
9.2.1 Forward direction mplsTunnelEntry
In mplsTunnelTable:
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
-- Local map number created in mplsNodeConfigTable for Ingress
LSR-Id
mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsNodeConfigTable for Egress
LSR-Id
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP associated bi-directional
forward LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
9.2.2 Forward direction mplsTunnelExtEntry
For Associated bidirectional forward LSP,
In mplsTunnelExtTable:
{
mplsTunnelOppositeDirPtr.1.1.1.2 = mplsTunnelName.2.1.2.1
}
9.2.3 Forward direction mplsOutSegmentTable
For the forward direction.
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentRowStatus = createAndGo (4)
}
9.2.4 Forward direction mplsXCEntry
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
9.2.5 Forward direction mplsXCExtEntry
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
9.2.6 Forward direction mplsTunnelEntry
The following denotes the configured associated bidirectional
reverse tunnel "tail" entry:
In mplsTunnelTable:
{
mplsTunnelIndex = 2,
mplsTunnelInstance = 1,
-- Local map number created in mplsNodeConfigTable for Ingress
LSR-Id
mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsNodeConfigTable for Egress
LSR-Id
mplsTunnelEgressLSRId = 1,
mplsTunnelName = "TP associated bi-directional
reverse LSP",
mplsTunnelDescr = "West to East",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
9.2.7 Reverse direction mplsTunnelExtEntry
For Associated bidirectional reverse LSP,
In mplsTunnelExtTable:
{
mplsTunnelOppositeDirPtr.2.1.2.1 = mplsTunnelName.1.1.1.2
}
9.2.8 Reverse direction mplsInSegmentEntry
We must next create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable
and mplsOutSegmentTable.
In mplsInSegmentTable: { mplsInSegmentIndex =
0x0000001 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, mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentRowStatus
mplsInSegmentRowStatus = createAndGo (4) = 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 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly
created segments together. created segments together.
In mplsXCTable: 9.2.9 Reverse direction mplsXCEntry
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000012,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000016, 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.
First for the forward direction: 9.2.10 Reverse direction mplsXCExtEntry
In mplsXCExtTable
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
}
Next for the reverse direction: Next for the reverse direction:
In mplsXCExtTable In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{ {
-- Back pointer from XC table to Tunnel table -- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.2.1.2 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
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]
IMPORTS TEXTUAL-CONVENTION
MODULE-IDENTITY, Unsigned32 FROM SNMPv2-TC -- [RFC2579]
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION mplsStdMIB
FROM SNMPv2-TC -- [RFC2579] FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsStdMIB ;
FROM MPLS-TC-STD-MIB -- [RFC3811]
; mplsTcExtStdMIB MODULE-IDENTITY
mplsTcExtStdMIB MODULE-IDENTITY LAST-UPDATED
"201202220000Z" -- February 22, 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
LAST-UPDATED Kannan KV Sampath
"201106160000Z" -- June 16, 2011
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
"
Venkatesan Mahalingam
Aricent,
India
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Aricent,
Aricent, India
India Email: Kannan.Sampath@aricent.com
Email: Kannan.Sampath@aricent.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
CA Technologies CA Technologies
273 Corporate Drive, Portsmouth, NH, USA 273 Corporate Drive, Portsmouth, NH, USA
Email: thomas.nadeau@ca.com
"
DESCRIPTION
"Copyright (c) 2011 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains Textual Conventions for Email: thomas.nadeau@ca.com
MPLS based transport networks." "
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
-- Revision history. This MIB module contains Textual Conventions for
MPLS based transport networks."
REVISION -- Revision history.
"201106160000Z" -- June 16, 2011
DESCRIPTION
"MPLS Textual Convention Extensions"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value REVISION
"201202220000Z" -- February 22, 2012
DESCRIPTION
"MPLS Textual Convention Extensions"
MplsGlobalId ::= TEXTUAL-CONVENTION ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
STATUS current
DESCRIPTION
"This object contains the Textual Convention of IP based
operator unique identifier (Global_ID), the Global_ID
can contain the 2-octet or 4-octet value of the operator's MplsGlobalId ::= TEXTUAL-CONVENTION
Autonomous System Number (ASN).
It is expected that the Global_ID will be derived from STATUS current
the globally unique ASN of the autonomous system hosting DESCRIPTION
the PEs containing the actual AIIs. "This object contains the Textual Convention of IP based
The presence of a Global_ID based on the operator's operator unique identifier (Global_ID), the Global_ID can
ASN ensures that the AII will be globally unique. contain the 2-octet or 4-octet value of the operator's
Autonomous System Number (ASN).
When the Global_ID is derived from a 2-octet AS number, It is expected that the Global_ID will be derived from
the two high-order octets of this 4-octet identifier the globally unique ASN of the autonomous system hosting
MUST be set to zero. the PEs containing the actual AIIs.
Further ASN 0 is reserved. A Global_ID of zero means that The presence of a Global_ID based on the operator's
no Global_ID is present. Note that a Global_ID of zero ASN ensures that the AII will be globally unique.
is limited to entities contained within a single operator
and MUST NOT be used across an NNI.
A non-zero Global_ID MUST be derived from an ASN owned by
the operator."
SYNTAX OCTET STRING (SIZE (4))
MplsNodeId ::= TEXTUAL-CONVENTION When the Global_ID is derived from a 2-octet AS number,
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"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
reserved and MUST NOT be used.
When IPv4 addresses are in use, the value of this object can the two high-order octets of this 4-octet identifier
be derived from the LSR's /32 IPv4 loop back address. When MUST be set to zero.
IPv6 addresses are in use, the value of this object can be a Further ASN 0 is reserved. A Global_ID of zero means
32-bit value unique within the scope of a Global_ID. that no Global_ID is present. Note that a Global_ID of
zero is limited to entities contained within a single
operator and MUST NOT be used across an NNI.
A non-zero Global_ID MUST be derived from an ASN owned by
the operator."
SYNTAX OCTET STRING (SIZE (4))
Note that, when IP reach ability is not needed, the 32-bit MplsNodeId ::= TEXTUAL-CONVENTION
Node_ID is not required to have any association DISPLAY-HINT "d"
with the IPv4 address space." STATUS current
SYNTAX Unsigned32 DESCRIPTION
"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
reserved and MUST NOT be used.
MplsIccId ::= TEXTUAL-CONVENTION When IPv4 addresses are in use, the value of this object
STATUS current can be derived from the LSR's /32 IPv4 loop back address.
DESCRIPTION When IPv6 addresses are in use, the value of this object
"The ICC is a string of one to six characters, each can be a 32-bit value unique within the scope of
character being either alphabetic (i.e. A-Z) or a Global_ID.
numeric (i.e. 0-9) characters.
Alphabetic characters in the ICC SHOULD be represented
with upper case letters." Note that, when IP reach ability is not needed, the 32-bit
SYNTAX OCTET STRING (SIZE (1..6)) Node_ID is not required to have any association
with the IPv4 address space."
SYNTAX Unsigned32
MplsLocalId ::= TEXTUAL-CONVENTION MplsIccId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The ICC is a string of one to six characters, each
"This textual convention is used in accommodating the bigger character being either alphabetic (i.e. A-Z) or
size Global_Node_ID and/or ICC with lower size LSR identifier numeric (i.e. 0-9) characters.
in order to index the mplsTunnelTable. Alphabetic characters in the ICC SHOULD be represented
The Local Identifier is configured between 1 and 16777215, with upper case letters."
as valid IP address range starts from 16777216 (01.00.00.00). SYNTAX OCTET STRING (SIZE (1..6))
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 MplsLocalId ::= TEXTUAL-CONVENTION
a unique identifier to map Global_Node_ID and/or ICC." DISPLAY-HINT "d"
SYNTAX Unsigned32(1..16777215) 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.
-- MPLS-TC-EXT-STD-MIB module ends The Local Identifier is configured between 1 and 16777215,
END 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.
11. MPLS Identifier MIB definitions This Local Identifier allows the administrator to assign
a unique identifier to map Global_Node_ID and/or ICC."
SYNTAX Unsigned32(1..16777215)
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN -- MPLS-TC-EXT-STD-MIB module ends
END
IMPORTS 11. MPLS Identifier MIB definitions
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
mplsIdStdMIB MODULE-IDENTITY MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
LAST-UPDATED
"201106160000Z" -- June 16, 2011
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO IMPORTS
" MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
Venkatesan Mahalingam FROM SNMPv2-SMI -- [RFC2578]
Aricent, MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
India FROM SNMPv2-CONF -- [RFC2580]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsGlobalId, MplsIccId, MplsNodeId
FROM MPLS-TC-EXT-STD-MIB
;
Email: venkat.mahalingams@gmail.com mplsIdStdMIB MODULE-IDENTITY
LAST-UPDATED
"201202220000Z" -- February 22, 2012
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group"
Kannan KV Sampath CONTACT-INFO
Aricent, "
India Venkatesan Mahalingam
Email: Kannan.Sampath@aricent.com 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
CA Technologies Huawei Technologies
273 Corporate Drive, Portsmouth, NH, USA 2330 Central Express Way,
Email: thomas.nadeau@ca.com Santa Clara, CA 95051, USA
" Email: aldrin.ietf@gmail.com
DESCRIPTION
"Copyright (c) 2011 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for Thomas D. Nadeau
MPLS Traffic Engineering in transport networks." CA Technologies
273 Corporate Drive, Portsmouth, NH, USA
Email: thomas.nadeau@ca.com
"
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
-- Revision history. This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks."
REVISION -- Revision history.
"201106160000Z" -- June 16, 2011
DESCRIPTION
"MPLS identifiers mib object extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value REVISION
"201202220000Z" -- February 22, 2012
DESCRIPTION
"MPLS identifiers mib object extension"
-- traps ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects -- traps
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
mplsGlobalId OBJECT-TYPE -- MPLS common objects
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the administrator to assign a unique mplsGlobalId OBJECT-TYPE
operator identifier also called MPLS-TP Global_ID." SYNTAX MplsGlobalId
REFERENCE MAX-ACCESS read-write
"MPLS-TP Identifiers [TPIDS]." STATUS current
::= { mplsIdObjects 1 } DESCRIPTION
mplsIcc OBJECT-TYPE "This object allows the administrator to assign a unique
SYNTAX MplsIccId operator identifier also called MPLS-TP Global_ID."
MAX-ACCESS read-write REFERENCE
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 [TPIDS]."
::= { mplsIdObjects 2 }
mplsNodeId OBJECT-TYPE "MPLS-TP Identifiers [RFC6370]."
SYNTAX MplsNodeId ::= { mplsIdObjects 1 }
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 the Global_ID." mplsIcc 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 }
REFERENCE mplsNodeId OBJECT-TYPE
"MPLS-TP Identifiers [TPIDS]." SYNTAX MplsNodeId
::= { mplsIdObjects 3 } MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique MPLS-TP Node_ID.
-- Module compliance. The Node_ID is assigned within the scope of
the Global_ID."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsIdObjects 3 }
mplsIdGroups -- Module compliance.
OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdCompliances mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 } OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
-- Compliance requirement for fully compliant implementations. mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
mplsIdModuleFullCompliance MODULE-COMPLIANCE -- Compliance requirement for fully compliant implementations.
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
MODULE -- this module mplsIdModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
-- The mandatory group has to be implemented by all MODULE -- this module
-- LSRs that originate/terminate MPLS-TP paths.
MANDATORY-GROUPS { -- The mandatory group has to be implemented by all
mplsIdScalarGroup -- LSRs that originate/terminate MPLS-TP paths.
}
::= { mplsIdCompliances 1 } MANDATORY-GROUPS {
mplsIdScalarGroup
}
-- Compliance requirement for read-only implementations. ::= { mplsIdCompliances 1 }
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE -- Compliance requirement for read-only implementations.
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
MODULE -- this module mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support the MPLS-ID-STD-MIB module."
-- The mandatory group has to be implemented by all MODULE -- this module
-- LSRs that originate/terminate MPLS-TP paths.
MANDATORY-GROUPS { -- The mandatory group has to be implemented by all
mplsIdScalarGroup -- LSRs that originate/terminate MPLS-TP paths.
}
::= { mplsIdCompliances 2 } MANDATORY-GROUPS {
mplsIdScalarGroup
}
-- Units of conformance. ::= { mplsIdCompliances 2 }
mplsIdScalarGroup OBJECT-GROUP -- Units of conformance.
OBJECTS { mplsGlobalId,
mplsNodeId,
mplsIcc
} mplsIdScalarGroup OBJECT-GROUP
STATUS current OBJECTS { mplsGlobalId,
DESCRIPTION mplsNodeId,
"Scalar object needed to implement MPLS TP path." mplsIcc
::= { mplsIdGroups 1 }
-- MPLS-ID-STD-MIB module ends }
END STATUS current
DESCRIPTION
"Scalar object needed to implement MPLS TP path."
::= { mplsIdGroups 1 }
-- MPLS-ID-STD-MIB module ends
END
12. MPLS LSR Extension MIB definitions 12. MPLS LSR Extension MIB definitions
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
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 MODULE-COMPLIANCE, OBJECT-GROUP
LAST-UPDATED FROM SNMPv2-CONF -- [RFC2580]
"201106160000Z" -- June 16, 2011 mplsStdMIB
ORGANIZATION FROM MPLS-TC-STD-MIB -- [RFC3811]
"Multiprotocol Label Switching (MPLS) Working Group" RowPointer
CONTACT-INFO FROM SNMPv2-TC -- [RFC2579]
" mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex,
Venkatesan Mahalingam mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup,
Aricent, mplsPerfGroup, mplsLsrNotificationGroup
India FROM MPLS-LSR-STD-MIB; -- [RFC3813]
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath mplsLsrExtStdMIB MODULE-IDENTITY
Aricent, LAST-UPDATED
India "201202220000Z" -- February 22, 2012
Email: Kannan.Sampath@aricent.com ORGANIZATION
Sam Aldrin "Multiprotocol Label Switching (MPLS) Working Group"
Huawei Technologies CONTACT-INFO
2330 Central Express Way, "
Santa Clara, CA 95051, USA Venkatesan Mahalingam
Dell Inc,
350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com
Email: aldrin.ietf@gmail.com Kannan KV Sampath
Aricent,
India
Email: Kannan.Sampath@aricent.com
Thomas D. Nadeau Sam Aldrin
CA Technologies Huawei Technologies
273 Corporate Drive, Portsmouth, NH, USA 2330 Central Express Way,
Email: thomas.nadeau@ca.com Santa Clara, CA 95051, USA
"
DESCRIPTION
"Copyright (c) 2011 IETF Trust and the persons identified
as the document authors. All rights reserved.
This MIB module contains generic object definitions for Email: aldrin.ietf@gmail.com
MPLS LSR in transport networks."
-- Revision history. Thomas D. Nadeau
CA Technologies
273 Corporate Drive, Portsmouth, NH, USA
Email: thomas.nadeau@ca.com
"
DESCRIPTION
"Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved.
REVISION This MIB module contains generic object definitions for
"201106160000Z" -- June 16, 2011
DESCRIPTION
"MPLS LSR specific mib objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value MPLS LSR in transport networks."
-- traps -- Revision history.
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 2 }
-- MPLS LSR common objects REVISION
mplsXCExtTable OBJECT-TYPE "201202220000Z" -- February 22, 2012
SYNTAX SEQUENCE OF MplsXCExtEntry DESCRIPTION
MAX-ACCESS not-accessible "MPLS LSR specific mib objects extension"
STATUS current
DESCRIPTION
"This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB [RFC 3813] 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 } ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value
mplsXCExtEntry OBJECT-TYPE -- traps
SYNTAX MplsXCExtEntry mplsLsrExtNotifications OBJECT IDENTIFIER
MAX-ACCESS not-accessible ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 }
STATUS current -- MPLS LSR common objects
DESCRIPTION mplsXCExtTable OBJECT-TYPE
"An entry in this table extends the cross connect SYNTAX SEQUENCE OF MplsXCExtEntry
information represented by an entry in MAX-ACCESS not-accessible
the mplsXCTable in MPLS-LSR-STD-MIB [RFC 3813] through STATUS current
a sparse augmentation. An entry can be created by a network DESCRIPTION
administrator via SNMP SET commands, or in "This table sparse augments the mplsXCTable of
response to signaling protocol events." MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific
REFERENCE information about associated tunnel information"
"1. Multiprotocol Label Switching (MPLS) Label Switching REFERENCE
Router (LSR) Management Information Base (MIB), RFC 3813." "1. Multiprotocol Label Switching (MPLS) Label Switching
INDEX { mplsXCIndex, mplsXCInSegmentIndex, Router (LSR) Management Information Base (MIB), RFC 3813."
mplsXCOutSegmentIndex } ::= { mplsLsrExtObjects 1 }
::= { mplsXCExtTable 1 }
MplsXCExtEntry ::= SEQUENCE { mplsXCExtEntry OBJECT-TYPE
mplsXCExtTunnelPointer RowPointer SYNTAX MplsXCExtEntry
} MAX-ACCESS not-accessible
mplsXCExtTunnelPointer OBJECT-TYPE STATUS current
SYNTAX RowPointer DESCRIPTION
MAX-ACCESS read-create "An entry in this table extends the cross connect
STATUS current information represented by an entry in
DESCRIPTION the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through
"This object indicates the back pointer to the tunnel entry a sparse augmentation. An entry can be created by
segment. This object cannot be modified if a network administrator via SNMP SET commands, or in
mplsXCRowStatus for the corresponding entry in the response to signaling protocol events."
mplsXCTable is active(1)." REFERENCE
REFERENCE "1. Multiprotocol Label Switching (MPLS) Label Switching
"1. Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB), RFC 3813."
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 }
mplsLsrExtGroups INDEX { mplsXCIndex, mplsXCInSegmentIndex,
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } mplsXCOutSegmentIndex }
mplsLsrExtCompliances ::= { mplsXCExtTable 1 }
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
-- Compliance requirement for fully compliant implementations. MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTunnelPointer RowPointer,
mplsXCOppositeDirXCPtr RowPointer
}
mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE mplsXCExtTunnelPointer OBJECT-TYPE
STATUS current SYNTAX RowPointer
DESCRIPTION MAX-ACCESS read-create
"Compliance statement for agents that provide full support STATUS current
for MPLS-LSR-EXT-STD-MIB. DESCRIPTION
"This object indicates the back pointer to the tunnel
entry segment. 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 1 }
The mandatory group has to be implemented by all LSRs that mplsXCOppositeDirXCPtr OBJECT-TYPE
originate, terminate, or act as transit for TE-LSPs/tunnels. SYNTAX RowPointer
In addition, depending on the type of tunnels supported, MAX-ACCESS read-create
other groups become mandatory as explained below." 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 }
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 mplsLsrExtGroups
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
MANDATORY-GROUPS { -- Compliance requirement for fully compliant implementations.
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
MODULE -- this module mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE
STATUS current
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."
MANDATORY-GROUPS { MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
mplsXCExtGroup
}
OBJECT mplsXCExtTunnelPointer MANDATORY-GROUPS {
SYNTAX RowPointer mplsInSegmentGroup,
MIN-ACCESS read-only mplsOutSegmentGroup,
DESCRIPTION mplsXCGroup,
"The only valid value for Tunnel Pointer is mplsTunnelTable mplsPerfGroup,
entry." mplsLsrNotificationGroup
}
::= { mplsLsrExtCompliances 1 } MODULE -- this module
-- Compliance requirement for implementations that provide read-only MANDATORY-GROUPS {
-- access. mplsXCExtGroup
}
mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE OBJECT mplsXCExtTunnelPointer
STATUS current SYNTAX RowPointer
DESCRIPTION MIN-ACCESS read-only
"Compliance requirement for implementations that only provide DESCRIPTION
read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can "The only valid value for Tunnel Pointer is mplsTunnelTable
then be monitored but cannot be configured using this entry."
MIB module."
MODULE MPLS-LSR-STD-MIB ::= { mplsLsrExtCompliances 1 }
MANDATORY-GROUPS { -- Compliance requirement for implementations that provide
mplsInterfaceGroup, -- read-only access.
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup, mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE
mplsPerfGroup 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."
MODULE -- this module MODULE MPLS-LSR-STD-MIB
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup
}
MANDATORY-GROUPS { MODULE -- this module
mplsXCExtGroup
}
OBJECT mplsXCExtTunnelPointer MANDATORY-GROUPS {
SYNTAX RowPointer mplsXCExtGroup
MIN-ACCESS read-only }
DESCRIPTION
"The only valid value for Tunnel Pointer is mplsTunnelTable
entry."
::= { mplsLsrExtCompliances 2 } OBJECT mplsXCExtTunnelPointer
SYNTAX RowPointer
MIN-ACCESS read-only
DESCRIPTION
"The only valid value for Tunnel Pointer is mplsTunnelTable
entry."
mplsXCExtGroup OBJECT-GROUP OBJECT mplsXCOppositeDirXCPtr
OBJECTS { SYNTAX RowPointer
mplsXCExtTunnelPointer MIN-ACCESS read-only
} DESCRIPTION
STATUS current "The only valid value for Tunnel Pointer is mplsXCTable
DESCRIPTION entry."
"This object should be supported in order to access
the tunnel entry from XC entry."
::= { mplsLsrExtGroups 1 }
-- MPLS-LSR-EXT-STD-MIB module ends ::= { mplsLsrExtCompliances 2 }
END
mplsXCExtGroup OBJECT-GROUP
OBJECTS {
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
END
13. MPLS Tunnel Extension MIB definitions 13. MPLS Tunnel Extension MIB definitions
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32,
Counter64, Gauge32, zeroDotZero, NOTIFICATION-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
IMPORTS RowStatus, RowPointer, StorageType
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Gauge32, FROM SNMPv2-TC -- [RFC2579]
NOTIFICATION-TYPE MplsLocalId, MplsGlobalId, MplsNodeId, MplsIccId
FROM SNMPv2-SMI -- [RFC2578] FROM MPLS-TC-EXT-STD-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
RowStatus, StorageType
FROM SNMPv2-TC -- [RFC2579]
MplsLocalId, MplsGlobalId, MplsNodeId, MplsIccId
FROM MPLS-TC-EXT-STD-MIB
mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- [RFC3812] FROM MPLS-TE-STD-MIB -- [RFC3812]
; ;
mplsTeExtStdMIB MODULE-IDENTITY mplsTeExtStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201106160000Z" -- June 16, 2011 "201203020000Z" -- March 02, 2012
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Venkatesan Mahalingam Venkatesan Mahalingam
Aricent, Dell Inc,
India 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent, Aricent,
India India
Email: Kannan.Sampath@aricent.com Email: Kannan.Sampath@aricent.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Express Way, 2330 Central Express Way,
Santa Clara, CA 95051, USA Santa Clara, CA 95051, USA
Email: aldrin.ietf@gmail.com Email: aldrin.ietf@gmail.com
Thomas D. Nadeau Thomas D. Nadeau
CA Technologies CA Technologies
273 Corporate Drive, Portsmouth, NH, USA 273 Corporate Drive, Portsmouth, NH, USA
Email: thomas.nadeau@ca.com Email: thomas.nadeau@ca.com
" "
DESCRIPTION DESCRIPTION
"Copyright (c) 2011 IETF Trust and the persons identified "Copyright (c) 2012 IETF Trust and the persons identified
as the document authors. All rights reserved. as the document authors. All rights reserved.
This MIB module contains generic object definitions for This MIB module contains generic object definitions for
MPLS Traffic Engineering in transport networks." MPLS Traffic Engineering in transport networks."
-- Revision history. -- Revision history.
REVISION REVISION
"201106160000Z" -- June 16, 2011 "201203020000Z" -- March 02, 2012
DESCRIPTION DESCRIPTION
"MPLS TE mib objects extension" "MPLS TE mib objects extension"
::= { mplsStdMIB xxx } -- xxx to be replaced with correct value ::= { mplsStdMIB xxx } -- xxx to be replaced
-- with correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- traps -- traps
mplsTeExtNotifications OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 } mplsTeExtNotifications OBJECT IDENTIFIER
-- tables, scalars ::= { mplsTeExtStdMIB 0 }
mplsTeExtObjects OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 1 } -- tables, scalars
-- conformance mplsTeExtObjects OBJECT IDENTIFIER
mplsTeExtConformance OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 2 } ::= { mplsTeExtStdMIB 1 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 2 }
-- Start of MPLS Transport Profile Node configuration table -- Start of MPLS Transport Profile Node configuration table
mplsNodeConfigTable OBJECT-TYPE mplsNodeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsNodeConfigEntry SYNTAX SEQUENCE OF MplsNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table allows the administrator to map a node or LSR "This table allows the administrator to map a node or
Identifier (IP compatible [Global_Node_ID] or ICC) with LSR Identifier (IP compatible [Global_Node_ID] or ICC)
a local identifier. with a local identifier.
This table is created to reuse the existing This table is created to reuse the existing
mplsTunnelTable for MPLS based transport network mplsTunnelTable for MPLS based transport network
tunnels also. tunnels also.
Since the MPLS tunnel's Ingress/Egress LSR identifiers' Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for size (Unsigned32) value is not compatible for
MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and
ICC of size 6 bytes, there exists a need to map the ICC of size 6 bytes, there exists a need to map the
Global_Node_ID or ICC with the local identifier of size Global_Node_ID or ICC with the local identifier of size
4 bytes (Unsigned32) value in order 4 bytes (Unsigned32) value in order
to index (Ingress/Egress LSR identifier) to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable." the existing mplsTunnelTable."
::= { mplsTeExtObjects 1 } ::= { mplsTeExtObjects 1 }
mplsNodeConfigEntry OBJECT-TYPE mplsNodeConfigEntry OBJECT-TYPE
SYNTAX MplsNodeConfigEntry SYNTAX MplsNodeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a mapping
identification for the operator or service provider
with node or LSR.
As per [TPIDS], this mapping is "An entry in this table represents a mapping
identification for the operator or service provider
with node or LSR.
represented as Global_Node_ID or ICC. As per [RFC6370], this mapping is
Note: Each entry in this table should have a unique represented as Global_Node_ID or ICC.
Global_ID and Node_ID combination."
INDEX { mplsNodeConfigLocalId }
::= { mplsNodeConfigTable 1 }
MplsNodeConfigEntry ::= SEQUENCE { Note: Each entry in this table should have a unique
mplsNodeConfigLocalId MplsLocalId, Global_ID and Node_ID combination."
mplsNodeConfigGlobalId MplsGlobalId, INDEX { mplsNodeConfigLocalId }
mplsNodeConfigNodeId MplsNodeId, ::= { mplsNodeConfigTable 1 }
mplsNodeConfigIccId MplsIccId,
mplsNodeConfigRowStatus RowStatus,
mplsNodeConfigStorageType StorageType
} MplsNodeConfigEntry ::= SEQUENCE {
mplsNodeConfigLocalId MplsLocalId,
mplsNodeConfigGlobalId MplsGlobalId,
mplsNodeConfigNodeId MplsNodeId,
mplsNodeConfigIccId MplsIccId,
mplsNodeConfigRowStatus RowStatus,
mplsNodeConfigStorageType StorageType
mplsNodeConfigLocalId OBJECT-TYPE }
SYNTAX MplsLocalId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object allows the administrator to assign a unique
local identifier to map Global_Node_ID or ICC."
::= { mplsNodeConfigEntry 1 }
mplsNodeConfigGlobalId OBJECT-TYPE mplsNodeConfigLocalId OBJECT-TYPE
SYNTAX MplsGlobalId SYNTAX MplsLocalId
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Global Operator Identifier. "This object allows the administrator to assign a unique
This object value should be zero when local identifier to map Global_Node_ID or ICC."
mplsNodeConfigIccId is configured with non-null value."
REFERENCE
"MPLS-TP Identifiers [TPIDS]."
::= { mplsNodeConfigEntry 2 }
mplsNodeConfigNodeId OBJECT-TYPE ::= { mplsNodeConfigEntry 1 }
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 [TPIDS]." mplsNodeConfigGlobalId OBJECT-TYPE
::= { mplsNodeConfigEntry 3 } SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object value should be zero when
mplsNodeConfigIccId is configured with non-null value."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsNodeConfigEntry 2 }
mplsNodeConfigIccId OBJECT-TYPE mplsNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsIccId SYNTAX MplsNodeId
MAX-ACCESS read-write MAX-ACCESS read-write
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 ID or Egress ID.
This object value should be zero when STATUS current
mplsNodeConfigGlobalId and mplsNodeConfigNodeId are DESCRIPTION
assigned with non-zero value." "This object indicates the Node_ID within the operator.
REFERENCE This object value should be zero when mplsNodeConfigIccId
"MPLS-TP Identifiers [TPIDS]." is configured with non-null value."
::= { mplsNodeConfigEntry 4 } REFERENCE
mplsNodeConfigRowStatus OBJECT-TYPE "MPLS-TP Identifiers [RFC6370]."
SYNTAX RowStatus ::= { mplsNodeConfigEntry 3 }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the administrator to create, modify,
and/or delete a row in this table."
::= { mplsNodeConfigEntry 5 }
mplsNodeConfigStorageType OBJECT-TYPE mplsNodeConfigIccId OBJECT-TYPE
SYNTAX StorageType SYNTAX MplsIccId
MAX-ACCESS read-create MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This object allows the operator or service provider to
object. configure a unique MPLS-TP ITU-T Carrier Code (ICC)
Conceptual rows having the value 'permanent' either for Ingress ID or Egress ID.
need not allow write-access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsNodeConfigEntry 6 }
-- End of MPLS Transport Profile Node configuration table This object value should be zero when
mplsNodeConfigGlobalId and mplsNodeConfigNodeId are
assigned with non-zero value."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsNodeConfigEntry 4 }
-- Start of MPLS Transport Profile Node IP compatible mapping table mplsNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the administrator to create, modify,
and/or delete a row in this table."
::= { mplsNodeConfigEntry 5 }
mplsNodeIpMapTable OBJECT-TYPE mplsNodeConfigStorageType OBJECT-TYPE
SYNTAX SEQUENCE OF MplsNodeIpMapEntry SYNTAX StorageType
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 }
MAX-ACCESS not-accessible -- End of MPLS Transport Profile Node configuration table
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.
This table MAY be used in on-demand and/or proactive -- Start of MPLS Transport Profile Node IP compatible
OAM operations to get the Ingress/Egress LSR -- mapping table
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.
This table returns nothing when the associated entry mplsNodeIpMapTable OBJECT-TYPE
is not defined in mplsNodeConfigTable." SYNTAX SEQUENCE OF MplsNodeIpMapEntry
::= { mplsTeExtObjects 2 }
mplsNodeIpMapEntry OBJECT-TYPE MAX-ACCESS not-accessible
SYNTAX MplsNodeIpMapEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "This read-only table allows the administrator to retrieve
DESCRIPTION the local identifier for a given Global_Node_ID in an IP
"An entry in this table represents a mapping of compatible operator environment.
Global_Node_ID with the local identifier.
An entry in this table is created automatically when This table MAY be used in on-demand and/or proactive
the Local identifier is associated with Global_ID and
Node_Id in the mplsNodeConfigTable.
Note: Each entry in this table should have a unique OAM operations to get the Ingress/Egress LSR identifier
Global_ID and Node_ID combination." (Local Identifier) from Src-Global_Node_ID
INDEX { mplsNodeIpMapGlobalId, or Dst-Global_Node_ID and the Ingress and Egress LSR
mplsNodeIpMapNodeId identifiers are used to retrieve the tunnel entry.
}
::= { mplsNodeIpMapTable 1 } This table returns nothing when the associated entry
is not defined in mplsNodeConfigTable."
::= { mplsTeExtObjects 2 }
MplsNodeIpMapEntry ::= SEQUENCE { mplsNodeIpMapEntry OBJECT-TYPE
mplsNodeIpMapGlobalId MplsGlobalId, SYNTAX MplsNodeIpMapEntry
mplsNodeIpMapNodeId MplsNodeId, MAX-ACCESS not-accessible
mplsNodeIpMapLocalId MplsLocalId STATUS current
} DESCRIPTION
"An entry in this table represents a mapping of
Global_Node_ID with the local identifier.
mplsNodeIpMapGlobalId OBJECT-TYPE An entry in this table is created automatically when
SYNTAX MplsGlobalId the Local identifier is associated with Global_ID and
MAX-ACCESS not-accessible Node_Id in the mplsNodeConfigTable.
STATUS current Note: Each entry in this table should have a unique
DESCRIPTION Global_ID and Node_ID combination."
"This object indicates the Global_ID." INDEX { mplsNodeIpMapGlobalId,
::= { mplsNodeIpMapEntry 1 } mplsNodeIpMapNodeId
}
::= { mplsNodeIpMapTable 1 }
mplsNodeIpMapNodeId OBJECT-TYPE MplsNodeIpMapEntry ::= SEQUENCE {
SYNTAX MplsNodeId mplsNodeIpMapGlobalId MplsGlobalId,
MAX-ACCESS not-accessible mplsNodeIpMapNodeId MplsNodeId,
STATUS current mplsNodeIpMapLocalId MplsLocalId
DESCRIPTION }
"This object indicates the Node_ID within the
operator."
::= { mplsNodeIpMapEntry 2 }
mplsNodeIpMapLocalId OBJECT-TYPE mplsNodeIpMapGlobalId OBJECT-TYPE
SYNTAX MplsLocalId SYNTAX MplsGlobalId
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object contains an IP compatible local identifier
which is defined in mplsNodeConfigTable."
::= { mplsNodeIpMapEntry 3 }
-- End MPLS Transport Profile Node IP compatible table STATUS current
DESCRIPTION
"This object indicates the Global_ID."
::= { mplsNodeIpMapEntry 1 }
-- Start of MPLS Transport Profile Node ICC based table mplsNodeIpMapNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the
operator."
::= { mplsNodeIpMapEntry 2 }
mplsNodeIccMapTable OBJECT-TYPE mplsNodeIpMapLocalId OBJECT-TYPE
SYNTAX SEQUENCE OF MplsNodeIccMapEntry SYNTAX MplsLocalId
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an IP compatible local identifier
which is defined in mplsNodeConfigTable."
::= { mplsNodeIpMapEntry 3 }
-- End MPLS Transport Profile Node IP compatible table
-- Start of MPLS Transport Profile Node ICC based table
mplsNodeIccMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsNodeIccMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This read-only table allows the administrator to retrieve "This read-only table allows the administrator to retrieve
the local identifier for a given ICC operator in an ICC the local identifier for a given ICC operator in an ICC
operator environment. operator environment.
This table MAY be used in on-demand and/or proactive This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR OAM operations to get the Ingress/Egress LSR
identifier (Local Identifier) from Src-ICC identifier (Local Identifier) from Src-ICC
or Dst-ICC and the Ingress and Egress LSR or Dst-ICC and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry. identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry This table returns nothing when the associated entry
is not defined in mplsNodeConfigTable." is not defined in mplsNodeConfigTable."
::= { mplsTeExtObjects 3 } ::= { mplsTeExtObjects 3 }
mplsNodeIccMapEntry OBJECT-TYPE
SYNTAX MplsNodeIccMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a mapping of ICC with
the local identifier.
An entry in this table is created automatically when
the Local identifier is associated with ICC in
the mplsNodeConfigTable."
INDEX { mplsNodeIccMapIccId }
::= { mplsNodeIccMapTable 1 }
MplsNodeIccMapEntry ::= SEQUENCE { mplsNodeIccMapEntry OBJECT-TYPE
mplsNodeIccMapIccId MplsIccId, SYNTAX MplsNodeIccMapEntry
mplsNodeIccMapLocalId MplsLocalId
}
mplsNodeIccMapIccId OBJECT-TYPE MAX-ACCESS not-accessible
SYNTAX MplsIccId STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "An entry in this table represents a mapping of ICC with
DESCRIPTION the local identifier.
"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 An entry in this table is created automatically when
character being either alphabetic (i.e. A-Z) or the Local identifier is associated with ICC in
numeric (i.e. 0-9) characters. Alphabetic characters in the mplsNodeConfigTable."
the ICC should be represented with upper case letters." INDEX { mplsNodeIccMapIccId }
::= { mplsNodeIccMapEntry 1 } ::= { mplsNodeIccMapTable 1 }
mplsNodeIccMapLocalId OBJECT-TYPE MplsNodeIccMapEntry ::= SEQUENCE {
SYNTAX MplsLocalId mplsNodeIccMapIccId MplsIccId,
MAX-ACCESS read-only mplsNodeIccMapLocalId MplsLocalId
STATUS current }
DESCRIPTION
"This object contains an ICC based local identifier
which is defined in mplsNodeConfigTable."
::= { mplsNodeIccMapEntry 2 }
-- End MPLS Transport Profile Node ICC based table mplsNodeIccMapIccId OBJECT-TYPE
SYNTAX MplsIccId
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.
-- Start of MPLS Tunnel table extension The ICC is a string of one to six characters, each
character being either alphabetic (i.e. A-Z) or
numeric (i.e. 0-9) characters. Alphabetic characters
in the ICC should be represented with upper case
letters."
::= { mplsNodeIccMapEntry 1 }
mplsTunnelExtTable OBJECT-TYPE mplsNodeIccMapLocalId OBJECT-TYPE
SYNTAX SEQUENCE OF MplsTunnelExtEntry SYNTAX MplsLocalId
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an ICC based local identifier
which is defined in mplsNodeConfigTable."
STATUS current ::= { mplsNodeIccMapEntry 2 }
DESCRIPTION
"This table represents MPLS-TP specific extensions to
mplsTunnelTable.
As per MPLS-TP Identifiers [TPIDS] draft, LSP_ID is -- End MPLS Transport Profile Node ICC based table
Src-Global_Node_ID::Src-Tunnel_Num::Dst-Global_Node_ID:: -- Start of MPLS Tunnel table extension
Dst-Tunnel_Num::LSP_Num for IP operator and
Src-ICC::Src-Tunnel_Num::Dst-ICC::Dst-Tunnel_Num::LSP_Num mplsTunnelExtTable OBJECT-TYPE
for ICC operator, SYNTAX SEQUENCE OF MplsTunnelExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents MPLS-TP specific extensions to
mplsTunnelTable.
mplsTunnelTable is reused for forming the LSP_ID As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based
as follows, co-routed bidirectional tunnel,
Source Tunnel_Num is mapped with mplsTunnelIndex, A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Source Node_ID is mapped with Node_ID::Tunnel_Num}::LSP_Num
mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance.
Source Global_Node_ID and/or ICC and Destination LSP_ID for IP based associated bidirectional tunnel,
Global_Node_ID and/or ICC are maintained in the A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
mplsNodeConfigTable and mplsNodeConfigLocalId is Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
used to create an entry in mplsTunnelTable." mplsTunnelTable is reused for forming the LSP_ID
REFERENCE as follows,
"MPLS-TP Identifiers [TPIDS]."
::= { mplsTeExtObjects 4 }
mplsTunnelExtEntry OBJECT-TYPE Source Tunnel_Num is mapped with mplsTunnelIndex,
SYNTAX 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.
"An entry in this table represents MPLS-TP
specific additional tunnel configurations."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
MplsTunnelExtEntry ::= SEQUENCE { Source Global_Node_ID and/or ICC and Destination
mplsTunnelExtDestTnlIndex MplsTunnelIndex, Global_Node_ID and/or ICC are maintained in the
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex mplsNodeConfigTable and mplsNodeConfigLocalId is
} used to create an entry in mplsTunnelTable."
REFERENCE
"MPLS-TP Identifiers [RFC6370]."
::= { mplsTeExtObjects 4 }
mplsTunnelExtDestTnlIndex OBJECT-TYPE mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelExtEntry
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is applicable only for the bidirectional "An entry in this table represents MPLS-TP
tunnel that has the forward and reverse LSPs in the specific additional tunnel configurations."
same tunnel or in the different tunnels. INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
This object holds the same value as that of the MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelIndex of mplsTunnelEntry if the forward and mplsTunnelOppositeDirPtr RowPointer
reverse LSPs are in the same tunnel. Otherwise, }
this object holds the value of the other direction
associated LSP's mplsTunnelIndex from a different tunnel.
The values of this object and the mplsTunnelOppositeDirPtr OBJECT-TYPE
mplsTunnelExtDestTnlLspIndex object together can be used SYNTAX RowPointer
to identify an opposite direction LSP i.e. if the MAX-ACCESS read-create
mplsTunnelIndex and mplsTunnelInstance hold the value for STATUS current
forward LSP, this object and mplsTunnelExtDestTnlLspIndex DESCRIPTION
can be used to retrieve the reverse direction LSP and "This object is applicable only for the bidirectional
vice versa. tunnel that has the forward and reverse LSPs in the
same tunnel or in the different tunnels.
This object and mplsTunnelExtDestTnlLspIndex values This object holds the opposite direction tunnel entry
provide the first two indices of tunnel entry and if the bidirectional tunnel is setup by configuring two
the remaining indices can be derived as follows, tunnel entries in mplsTunnelTable.
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.
The value of zero for this object is invalid." The value of zeroDotZero indicates single tunnel entry
::= { mplsTunnelExtEntry 1 } is used for bidirectional tunnel setup."
DEFVAL { zeroDotZero }
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE -- End of MPLS Tunnel table extension
SYNTAX MplsTunnelInstanceIndex
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 should contain different value if both the mplsTunnelReversePerfTable OBJECT-TYPE
forward and reverse LSPs present in the same tunnel. SYNTAX SEQUENCE OF MplsTunnelReversePerfEntry
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.
This object can contain same value or different values if For links that do not transport packets, these packet
the forward and reverse LSPs present in the different counters cannot be maintained. For such links, attempts
tunnels. to read the objects in this table will return
The value of zero for this object is valid for the noSuchInstance."
configured tunnel." REFERENCE
::= { mplsTunnelExtEntry 2 } "1. Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE)Management Information Base (MIB),
RFC 3812."
::= { mplsTeExtObjects 5 }
-- End of MPLS Tunnel table extension mplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX MplsTunnelReversePerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the LSR for every
bidirectional MPLS tunnel where packets are visible to the
LSR."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelReversePerfTable 1 }
-- Notifications. MplsTunnelReversePerfEntry ::= SEQUENCE {
-- Notifications objects need to be added here. mplsTunnelReversePerfPackets Counter32,
-- End of notifications. mplsTunnelReversePerfHCPackets Counter64,
mplsTunnelReversePerfErrors Counter32,
mplsTunnelReversePerfBytes Counter32,
mplsTunnelReversePerfHCBytes Counter64
}
-- Module compliance. mplsTunnelReversePerfPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of packets forwarded on the tunnel in the reverse
direction if it is bidirectional.
mplsTeExtGroups This object represents the 32-bit value of the least
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } significant part of the 64-bit value if both
mplsTunnelReversePerfHCPackets and this object
are returned.
mplsTeExtCompliances For links that do not transport packets, this packet
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } counter cannot be maintained. For such links, this value
will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 1 }
-- Compliance requirement for fully compliant implementations. 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.
mplsTeExtModuleFullCompliance MODULE-COMPLIANCE For links that do not transport packets, this packet
STATUS current counter cannot be maintained. For such links, this value
DESCRIPTION will return noSuchInstance."
"Compliance statement for agents that provide full ::= { mplsTunnelReversePerfEntry 2 }
support the MPLS-TE-EXT-STD-MIB module."
MODULE -- this module mplsTunnelReversePerfErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of errored packets received on the tunnel in
the reverse direction if it is bidirectional. For links
that do not transport packets, this packet counter cannot
be maintained. For such links, this value will return
noSuchInstance."
::= { mplsTunnelReversePerfEntry 3 }
-- The mandatory group has to be implemented by all mplsTunnelReversePerfBytes OBJECT-TYPE
-- LSRs that originate/terminate MPLS-TP tunnels. SYNTAX Counter32
-- In addition, depending on the type of tunnels MAX-ACCESS read-only
-- supported, other groups become mandatory as STATUS current
-- explained below. DESCRIPTION
"Number of bytes forwarded on the tunnel in the reverse
direction if it is bidirectional.
MANDATORY-GROUPS { This object represents the 32-bit value of the least
mplsTunnelExtGroup significant part of the 64-bit value if both
} mplsTunnelReversePerfHCBytes and this object are returned.
GROUP mplsTunnelExtIpOperatorGroup For links that do not transport packets, this packet
counter cannot be maintained. For such links, this value
will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 4 }
mplsTunnelReversePerfHCBytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "High-capacity counter for number of bytes forwarded on the
configuration of IP based identifier tunnels." tunnel in the reverse direction if it is bidirectional.
GROUP mplsTunnelExtIccOperatorGroup For links that do not transport packets, this packet
counter cannot be maintained. For such links, this value
will return noSuchInstance."
::= { mplsTunnelReversePerfEntry 5 }
-- Notifications.
-- Notifications objects need to be added here.
-- End of notifications.
-- Module compliance.
mplsTeExtGroups
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
mplsTeExtCompliances
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
-- Compliance requirement for fully compliant implementations.
mplsTeExtModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "Compliance statement for agents that provide full
configuration of ICC based tunnels." support the MPLS-TE-EXT-STD-MIB module."
::= { mplsTeExtCompliances 1 } MODULE -- this module
-- Compliance requirement for read-only implementations. -- 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.
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE MANDATORY-GROUPS {
STATUS current mplsTunnelExtGroup
DESCRIPTION }
"Compliance statement for agents that provide full
support the MPLS-TE-EXT-STD-MIB module."
MODULE -- this module GROUP mplsTunnelExtIpOperatorGroup
-- 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 IP based identifier tunnels."
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS { GROUP mplsTunnelExtIccOperatorGroup
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup 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 IP based identifier tunnels."
GROUP mplsTunnelExtIccOperatorGroup ::= { mplsTeExtCompliances 1 }
-- Compliance requirement for read-only implementations.
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "Compliance statement for agents that provide full
configuration of ICC based tunnels." support the MPLS-TE-EXT-STD-MIB module."
::= { mplsTeExtCompliances 2 } MODULE -- this module
-- Units of conformance. -- 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.
mplsTunnelExtGroup OBJECT-GROUP MANDATORY-GROUPS {
OBJECTS { mplsTunnelExtGroup
mplsTunnelExtDestTnlIndex, }
mplsTunnelExtDestTnlLspIndex
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the
operating environment, the following groups are
mandatory."
::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP GROUP mplsTunnelExtIpOperatorGroup
OBJECTS { mplsNodeConfigGlobalId, DESCRIPTION
mplsNodeConfigNodeId, "This group is mandatory for devices which support
mplsNodeConfigRowStatus, configuration of IP based identifier tunnels."
mplsNodeConfigStorageType,
mplsNodeIpMapLocalId
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP GROUP mplsTunnelExtIccOperatorGroup
OBJECTS { mplsNodeConfigIccId,
mplsNodeConfigRowStatus,
mplsNodeConfigStorageType,
mplsNodeIccMapLocalId
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC based tunnels."
::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends DESCRIPTION
END "This group is mandatory for devices which support
configuration of ICC based tunnels."
::= { mplsTeExtCompliances 2 }
-- Units of conformance.
mplsTunnelExtGroup OBJECT-GROUP
OBJECTS {
mplsTunnelOppositeDirPtr,
mplsTunnelReversePerfPackets,
mplsTunnelReversePerfHCPackets,
mplsTunnelReversePerfErrors,
mplsTunnelReversePerfBytes,
mplsTunnelReversePerfHCBytes
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to
implement tunnels. In addition, depending on the
operating environment, the following groups are
mandatory."
::= { mplsTeExtGroups 1 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsNodeConfigGlobalId,
mplsNodeConfigNodeId,
mplsNodeConfigRowStatus,
mplsNodeConfigStorageType,
mplsNodeIpMapLocalId
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP compatible tunnels."
::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsNodeConfigIccId,
mplsNodeConfigRowStatus,
mplsNodeConfigStorageType,
mplsNodeIccMapLocalId
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC based tunnels."
::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends
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 37, line 35 skipping to change at page 43, line 50
these objects and possibly to even encrypt the values of these these objects and possibly to even encrypt the values of these
objects when sending them over the network via SNMP. These are objects when sending them over the network via SNMP. These are
the tables and objects and their sensitivity/vulnerability: the tables and objects and their sensitivity/vulnerability:
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) allowed to access and GET/SET (read/change/create/delete)
the objects in this MIB module. the objects in this MIB module.
It is RECOMMENDED that implementers consider the security features It is recommended that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8), as provided by the SNMPv3 framework (see [RFC3410], section 8),
including full supports for the SNMPv3 cryptographic mechanisms including full supports for the SNMPv3 cryptographic mechanisms
(for authentication and privacy). (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is not
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to recommended. Instead, it is recommended to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give instance of this MIB module is properly configured to give
access to the objects only to those principles (users) that access to the objects only to those principles (users) that
have legitimate rights to indeed GET or SET (change/create/delete) have legitimate rights to indeed GET or SET (change/create/delete)
them. them.
15. IANA Considerations 15. IANA Considerations
To be added in a later version of this document. To be added in a later version of this document.
16. References 16. References
16.1 Normative References 16.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
skipping to change at page 38, line 49 skipping to change at page 45, line 16
June 2004. June 2004.
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction
and Applicability Statement for Internet Standard and Applicability Statement for Internet Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, June 2004. Switching (MPLS) Management", RFC 3811, June 2004.
[RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base", RFC
4802, February 2007.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Sprecher, N., and S. Ueno, "Requirements of an MPLS Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", RFC 5654, September 2009. Transport Profile", RFC 5654, September 2009.
[TPIDS] M. Bocci, et al, "MPLS-TP Identifiers", [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
draft-ietf-mpls-tp-identifiers-03, October 25, 2010 Profile (MPLS-TP) Identifiers", RFC 6370, September
2011.
17. Acknowledgments 17. Acknowledgments
To be added in a later version of this document. The authors would like to thank Francesco Fondelli, Josh Littlefield,
Agrahara Kiran Koushik and Metrri Jain 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
CA Technologies CA Technologies
273 Corporate Drive, Portsmouth, NH, USA 273 Corporate Drive, Portsmouth, NH, USA
Email: thomas.nadeau@ca.com Email: thomas.nadeau@ca.com
Venkatesan Mahalingam Venkatesan Mahalingam
Aricent Dell Inc.
India 350 Holger way, San Jose, CA, USA
Email: venkat.mahalingams@gmail.com Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Kannan KV Sampath
Aricent Aricent
India India
Email: Kannan.Sampath@aricent.com Email: Kannan.Sampath@aricent.com
 End of changes. 271 change blocks. 
1082 lines changed or deleted 1382 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/