Internet Engineering Task Force (IETF) M. Venkatesan
Request for Comments: 7453 Dell Inc.
Category: Standards Track K. Sampath
ISSN: 2070-1721 Redeem
S. Aldrin
Huawei Technologies
T. Nadeau
Brocade
February 2015
Internet Engineering Task Force (IETF) M. Venkatesan
Request for Comments: 7453 Dell Inc.
Category: Standards Track K. Sampath
ISSN: 2070-1721 Redeem
S. Aldrin
Huawei Technologies
T. Nadeau
Brocade
February 2015
MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)
MPLS传输配置文件（MPLS-TP）流量工程（TE）管理信息库（MIB）
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes additional managed objects and textual conventions for tunnels, identifiers, and Label Switching Routers to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了隧道、标识符和标签交换路由器的其他托管对象和文本约定，以支持传输网络的多协议标签交换（MPLS）MIB模块。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7453.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7453.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................4
2. The Internet-Standard Management Framework ......................5
3. Overview ........................................................5
3.1. Conventions Used in This Document ..........................5
3.2. Terminology ................................................6
3.3. Acronyms ...................................................6
4. Motivations .....................................................6
5. Feature List ....................................................7
6. Outline .........................................................7
6.1. MIB Module Extensions ......................................8
6.1.1. Summary of MIB Module Changes .......................8
6.2. MPLS-TE-EXT-STD-MIB ........................................9
6.2.1. mplsTunnelExtNodeConfigTable ........................9
6.2.2. mplsTunnelExtNodeIpMapTable .........................9
6.2.3. mplsTunnelExtNodeIccMapTable .......................10
6.2.4. mplsTunnelExtTable .................................10
6.3. MPLS-TC-EXT-STD-MIB .......................................10
6.4. MPLS-ID-STD-MIB ...........................................10
6.5. MPLS-LSR-EXT-STD-MIB ......................................11
6.6. The Use of RowPointer .....................................11
7. MIB Modules' Interdependencies .................................11
8. Dependencies between MIB Module Tables .........................13
9. Example of MPLS-TP Tunnel Setup ................................13
9.1. Example of MPLS-TP Static Co-routed Bidirectional
Tunnel Setup ..............................................15
9.1.1. mplsTunnelEntry ....................................15
9.1.2. mplsTunnelExtEntry .................................16
9.1.3. Forward-Direction mplsOutSegmentEntry ..............16
9.1.4. Reverse-Direction mplsInSegmentEntry ...............16
9.1.5. Forward-Direction mplsXCEntry ......................17
9.1.6. Reverse-Direction mplsXCEntry ......................17
1. Introduction ....................................................4
2. The Internet-Standard Management Framework ......................5
3. Overview ........................................................5
3.1. Conventions Used in This Document ..........................5
3.2. Terminology ................................................6
3.3. Acronyms ...................................................6
4. Motivations .....................................................6
5. Feature List ....................................................7
6. Outline .........................................................7
6.1. MIB Module Extensions ......................................8
6.1.1. Summary of MIB Module Changes .......................8
6.2. MPLS-TE-EXT-STD-MIB ........................................9
6.2.1. mplsTunnelExtNodeConfigTable ........................9
6.2.2. mplsTunnelExtNodeIpMapTable .........................9
6.2.3. mplsTunnelExtNodeIccMapTable .......................10
6.2.4. mplsTunnelExtTable .................................10
6.3. MPLS-TC-EXT-STD-MIB .......................................10
6.4. MPLS-ID-STD-MIB ...........................................10
6.5. MPLS-LSR-EXT-STD-MIB ......................................11
6.6. The Use of RowPointer .....................................11
7. MIB Modules' Interdependencies .................................11
8. Dependencies between MIB Module Tables .........................13
9. Example of MPLS-TP Tunnel Setup ................................13
9.1. Example of MPLS-TP Static Co-routed Bidirectional
Tunnel Setup ..............................................15
9.1.1. mplsTunnelEntry ....................................15
9.1.2. mplsTunnelExtEntry .................................16
9.1.3. Forward-Direction mplsOutSegmentEntry ..............16
9.1.4. Reverse-Direction mplsInSegmentEntry ...............16
9.1.5. Forward-Direction mplsXCEntry ......................17
9.1.6. Reverse-Direction mplsXCEntry ......................17
9.1.7. Forward-Direction mplsXCExtEntry ...................18
9.1.8. Reverse-Direction mplsXCExtEntry ...................18
9.2. Example of MPLS-TP Static Associated Bidirectional
Tunnel Setup ..............................................18
9.2.1. Forward-Direction mplsTunnelEntry ..................18
9.2.2. Forward-Direction mplsTunnelExtEntry ...............19
9.2.3. Forward-Direction mplsOutSegmentTable ..............20
9.2.4. Forward-Direction mplsXCEntry ......................20
9.2.5. Forward-Direction mplsXCExtEntry ...................20
9.2.6. Reverse-Direction mplsTunnelEntry ..................21
9.2.7. Reverse-Direction mplsTunnelExtEntry ...............22
9.2.8. Reverse-Direction mplsInSegmentEntry ...............22
9.2.9. Reverse-Direction mplsXCEntry ......................22
9.2.10. Reverse-Direction mplsXCExtEntry ..................23
9.3. Example of MPLS-TP Signaled Co-routed
Bidirectional Tunnel Setup ................................23
9.3.1. mplsTunnelEntry ....................................23
9.3.2. mplsTunnelExtEntry .................................24
9.3.3. Forward-Direction mplsOutSegmentEntry ..............24
9.3.4. Reverse-Direction mplsInSegmentEntry ...............25
9.3.5. Forward-Direction mplsXCEntry ......................25
9.3.6. Reverse-Direction mplsXCEntry ......................25
9.3.7. Forward-Direction mplsXCExtEntry ...................25
9.3.8. Reverse-Direction mplsXCExtEntry ...................25
10. MPLS Textual Convention Extension MIB Definitions .............26
11. MPLS Identifier MIB Definitions ...............................29
12. MPLS LSR Extension MIB Definitions ............................34
13. MPLS Tunnel Extension MIB Definitions .........................39
14. Security Considerations .......................................57
15. IANA Considerations ...........................................58
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB ..............58
15.2. IANA Considerations for MPLS-ID-STD-MIB ..................58
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB .............58
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB ..............59
16. References ....................................................59
16.1. Normative References .....................................59
16.2. Informative References ...................................60
Acknowledgments ...................................................62
Authors' Addresses ................................................62
9.1.7. Forward-Direction mplsXCExtEntry ...................18
9.1.8. Reverse-Direction mplsXCExtEntry ...................18
9.2. Example of MPLS-TP Static Associated Bidirectional
Tunnel Setup ..............................................18
9.2.1. Forward-Direction mplsTunnelEntry ..................18
9.2.2. Forward-Direction mplsTunnelExtEntry ...............19
9.2.3. Forward-Direction mplsOutSegmentTable ..............20
9.2.4. Forward-Direction mplsXCEntry ......................20
9.2.5. Forward-Direction mplsXCExtEntry ...................20
9.2.6. Reverse-Direction mplsTunnelEntry ..................21
9.2.7. Reverse-Direction mplsTunnelExtEntry ...............22
9.2.8. Reverse-Direction mplsInSegmentEntry ...............22
9.2.9. Reverse-Direction mplsXCEntry ......................22
9.2.10. Reverse-Direction mplsXCExtEntry ..................23
9.3. Example of MPLS-TP Signaled Co-routed
Bidirectional Tunnel Setup ................................23
9.3.1. mplsTunnelEntry ....................................23
9.3.2. mplsTunnelExtEntry .................................24
9.3.3. Forward-Direction mplsOutSegmentEntry ..............24
9.3.4. Reverse-Direction mplsInSegmentEntry ...............25
9.3.5. Forward-Direction mplsXCEntry ......................25
9.3.6. Reverse-Direction mplsXCEntry ......................25
9.3.7. Forward-Direction mplsXCExtEntry ...................25
9.3.8. Reverse-Direction mplsXCExtEntry ...................25
10. MPLS Textual Convention Extension MIB Definitions .............26
11. MPLS Identifier MIB Definitions ...............................29
12. MPLS LSR Extension MIB Definitions ............................34
13. MPLS Tunnel Extension MIB Definitions .........................39
14. Security Considerations .......................................57
15. IANA Considerations ...........................................58
15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB ..............58
15.2. IANA Considerations for MPLS-ID-STD-MIB ..................58
15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB .............58
15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB ..............59
16. References ....................................................59
16.1. Normative References .....................................59
16.2. Informative References ...................................60
Acknowledgments ...................................................62
Authors' Addresses ................................................62
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes additional textual conventions and managed objects for tunnels, identifiers, and Label Switching Routers to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks. MIB modules defined in this document extend the existing MPLS MIB objects in such a way that they support the MPLS Transport Profile (MPLS-TP) but also other MPLS networks. Hence, "MPLS-TP" is not included in the MIB module names.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了隧道、标识符和标签交换路由器的其他文本约定和托管对象，以支持传输网络的多协议标签交换（MPLS）MIB模块。本文档中定义的MIB模块扩展了现有的MPLS MIB对象，使其不仅支持MPLS传输配置文件（MPLS-TP），还支持其他MPLS网络。因此，“MPLS-TP”不包括在MIB模块名称中。
As described in the MPLS Traffic Engineering (TE) MIB definition [RFC3812], MPLS traffic engineering is concerned with the creation and management of MPLS tunnels. This term is a shorthand for a combination of one or more LSPs linking an ingress and an egress LSR. Several types of point-to-point MPLS tunnels may be constructed between a pair of LSRs A and B:
如MPLS流量工程（TE）MIB定义[RFC3812]所述，MPLS流量工程涉及MPLS隧道的创建和管理。该术语是链接入口和出口LSR的一个或多个LSP的组合的缩写。可以在一对lsr a和B之间构建几种类型的点对点MPLS隧道：
- Unidirectional with a single LSP (say, from A to B).
- 具有单个LSP的单向（例如，从a到B）。
- Associated bidirectional consisting of two separately routed LSPs, one linking A to B and the other linking B to A. Together, the pair provides a single logical bidirectional transport path.
- 由两个单独路由的LSP组成的关联双向LSP，一个链接A到B，另一个链接B到A。这对LSP一起提供单个逻辑双向传输路径。
- Co-routed bidirectional consisting of an associated bidirectional tunnel but with the second LSP from B to A following the reverse of the path of the LSP from A to B, in terms of both nodes and links.
- 双向共路由，包括相关联的双向隧道，但在节点和链路方面，第二个LSP从B到A，其路径与LSP从A到B的路径相反。
Tunnels may be either statically configured by management action or dynamically created using an LSP management protocol.
隧道可以由管理操作静态配置，也可以使用LSP管理协议动态创建。
The existing MPLS TE MIB [RFC3812] and the GMPLS TE MIB [RFC4802] address only a subset of the combinations of statically and dynamically configured tunnel types, catering to statically configured unidirectional tunnels together with dynamically configured unidirectional and co-routed bidirectional tunnels. They are also restricted to two endpoint LSRs identified by IP addresses.
现有的MPLS TE MIB[RFC3812]和GMPLS TE MIB[RFC4802]仅解决静态和动态配置的隧道类型组合的子集，以满足静态配置的单向隧道以及动态配置的单向和共路由双向隧道的需要。它们还限于由IP地址标识的两个端点LSR。
The MPLS-TP TE MIB defined in this document extends the MIB modules defined in [RFC3812] to cover all six combinations (that is, adding support for statically configured associated and co-routed bidirectional plus dynamically configured associated bidirectional tunnels). It also extends support to endpoints that have identifiers other than IP addresses.
本文档中定义的MPLS-TP TE MIB扩展了[RFC3812]中定义的MIB模块，以涵盖所有六种组合（即，增加对静态配置的关联双向和共路由双向以及动态配置的关联双向隧道的支持）。它还扩展了对具有除IP地址以外的标识符的端点的支持。
This support is provided by a suite of four MIB modules that are to be used in conjunction with the MIB modules defined in [RFC3812] and the companion document [RFC3813] for MPLS-TP tunnel management.
该支持由一套四个MIB模块提供，这些模块将与[RFC3812]和配套文件[RFC3813]中定义的用于MPLS-TP隧道管理的MIB模块一起使用。
At the time of writing, SNMP SET is no longer recommended as a way to configure MPLS networks as described in [RFC3812]. However, since the MIB modules specified in this document extend and are intended to work in parallel with the MIB modules for MPLS specified in [RFC3812], certain objects defined here are specified with MAX-ACCESS of read-write or read-create so that specifications of the base tables in [RFC3812] and the extensions in this document are consistent. Although the examples described in Section 9 specify means to configure MPLS-TP Tunnels in a similar way to the examples in [RFC3812], this should be seen as indicating how the MIB values would be returned if the specified circumstances were configured by alternative means.
在撰写本文时，不再建议将SNMP集作为配置MPLS网络的一种方式，如[RFC3812]所述。然而，由于本文件中指定的MIB模块扩展并打算与[RFC3812]中指定的MPLS的MIB模块并行工作，因此此处定义的某些对象指定为读写或读创建的最大访问权限，以便[RFC3812]中的基表规范本文档中的扩展是一致的。尽管第9节中描述的示例指定了以与[RFC3812]中示例类似的方式配置MPLS-TP隧道的方法，但这应被视为指示如果通过替代方法配置指定情况，MIB值将如何返回。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照[RFC2119]中的说明进行解释。
This document uses terminology from the "Multiprotocol Label Switching Architecture" [RFC3031], "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)" [RFC3812], "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)" [RFC3813], and"MPLS Transport Profile (MPLS-TP) Identifiers" [RFC6370].
本文档使用了“多协议标签交换体系结构”[RFC3031]、“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”[RFC3812]、“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”[RFC3813]和“MPLS传输配置文件”中的术语（MPLS-TP）标识符“[RFC6370]。
CC: Country Code ICC: ITU Carrier Code LSP: Label Switched Path LSR: Label Switching Router MPLS-TP: MPLS Transport Profile TE: Traffic Engineering TP: Transport Profile
CC：国家代码ICC:ITU载波代码LSP:标签交换路径LSR:标签交换路由器MPLS-TP:MPLS传输配置文件TE:流量工程TP:传输配置文件
"Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)" [RFC3812] provides support for Traffic Engineering tunnels. In MPLS, the actual transport of packets is provided by Label Switched Paths (LSPs). A transport service may be composed of multiple LSPs. In order to clearly identify the MPLS-TP service, as defined in [RFC6370], we use the term "MPLS-TP Tunnel" or simply "tunnel". However, with MPLS-TP, the characteristics of the tunnels were enhanced. For example, MPLS-TP Tunnels are bidirectional in nature and could be used with non-IP identifiers for the tunnel endpoints. As the existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to support unidirectional tunnels and signaled co-routed bidirectional tunnel definitions, respectively, these existing MIB modules are not sufficient to capture all the characteristics of the tunnels. Hence, enhancing the MIB modules to support MPLS-TP Tunnels is required. As most of the attributes of MPLS Traffic Engineering tunnels are also applicable to MPLS-TP Tunnels, it is optimal to reuse and extend the existing MIB module definition instead of defining a new MIB module.
“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”[RFC3812]为流量工程隧道提供支持。在MPLS中，数据包的实际传输由标签交换路径（LSP）提供。传输服务可以由多个lsp组成。为了清楚地识别MPLS-TP服务，如[RFC6370]中所定义，我们使用术语“MPLS-TP隧道”或简称“隧道”。然而，通过MPLS-TP，隧道的特性得到了增强。例如，MPLS-TP隧道本质上是双向的，可以与隧道端点的非IP标识符一起使用。由于现有MPLS-TE-STD-MIB和GMPLS-TE-STD-MIB的定义主要是分别支持单向隧道和信号共路由双向隧道定义，因此这些现有MIB模块不足以捕获隧道的所有特征。因此，需要增强MIB模块以支持MPLS-TP隧道。由于MPLS流量工程隧道的大多数属性也适用于MPLS-TP隧道，因此最好重用和扩展现有的MIB模块定义，而不是定义新的MIB模块。
This document defines four additional MIB modules, namely, MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and MPLS-LSR-EXT-STD-MIB. As these additional MIB modules are required for MPLS-TP functionality, these are all defined in this document, instead of being documented separately.
本文档定义了四个附加MIB模块，即MPLS-TE-EXT-STD-MIB、MPLS-TC-EXT-STD-MIB、MPLS-ID-STD-MIB和MPLS-LSR-EXT-STD-MIB。由于MPLS-TP功能需要这些额外的MIB模块，因此这些模块都在本文档中定义，而不是单独记录。
The MIBs in this document satisfy the following requirements and constraints:
本文件中的MIB满足以下要求和约束：
The MIB modules, taken together, support statically configured and dynamically signaled point-to-point, co-routed bidirectional and associated bidirectional tunnels.
MIB模块一起支持静态配置和动态信号点对点、共路由双向和相关双向隧道。
- The MPLS tunnels need not be interfaces, but it is possible to configure an MPLS-TP Tunnel as an interface. The same ifType 150, as defined in Section 8 of [RFC3812], will be used for MPLS-TP Tunnels as well.
- MPLS隧道不需要是接口，但可以将MPLS-TP隧道配置为接口。[RFC3812]第8节中定义的相同ifType 150也将用于MPLS-TP隧道。
- The mplsTunnelTable [RFC3812] is also to be used for MPLS-TP Tunnels.
- mplsTunnelTable[RFC3812]也将用于MPLS-TP隧道。
- New MPLS-TP-specific textual conventions and identifiers are required.
- 需要新的MPLS TP特定文本约定和标识符。
- The mplsTunnelTable is sparsely extended to support objects specific to MPLS-TP Tunnels.
- mplsTunnelTable很少扩展以支持特定于MPLS-TP隧道的对象。
- A node configuration table (mplsTunnelExtNodeConfigTable), as detailed in Section 6.2.1, below, is used to translate the Global_ID::Node_ID or ICC_Operator_ID::Node_ID to the local identifier in order to index the mplsTunnelTable.
- 如下文第6.2.1节所述，节点配置表（mplsTunnelExtNodeConfigTable）用于将全局_ID:：node_ID或ICC_操作符_ID:：node_ID转换为本地标识符，以便索引mplsTunnelTable。
- The mplsXCTable is sparsely extended to support objects specific to MPLS-TP XC (Cross Connect).
- mplsXCTable被稀疏地扩展以支持特定于MPLS-TP XC（交叉连接）的对象。
- The MIB module supports persistent, as well as non-persistent, tunnels.
- MIB模块支持持久和非持久隧道。
Traffic Engineering support for the MPLS-TP Tunnels requires the setup of the co-routed or associated bidirectional tunnel. The tables and MIB modules that are mentioned in the below subsections support the functionality described in [RFC5654] and [RFC6370]. These tables support both IP-compatible and ICC-based tunnel configurations.
MPLS-TP隧道的流量工程支持需要设置共路由或相关的双向隧道。以下小节中提到的表格和MIB模块支持[RFC5654]和[RFC6370]中描述的功能。这些表支持IP兼容和基于ICC的隧道配置。
Figure 1, below, depicts how the table references are followed in this MIB.
下面的图1描述了在这个MIB中如何遵循表引用。
Tunnel1-->XC1<--------------
^ ^ | | |
| | | |-->InSeg1 |
| | | |-->OutSeg1 |
| | v |
| ------XCext1 |
| | |
V v |
Tunnel2-->XC1 |
^ | | |
| | |-->InSeg2 |
| | |-->OutSeg2 |
| v |
------XCext2------------
Tunnel1-->XC1<--------------
^ ^ | | |
| | | |-->InSeg1 |
| | | |-->OutSeg1 |
| | v |
| ------XCext1 |
| | |
V v |
Tunnel2-->XC1 |
^ | | |
| | |-->InSeg2 |
| | |-->OutSeg2 |
| v |
------XCext2------------
Figure 1: Table References of MIB Modules
图1:MIB模块的表引用
Four MIB modules are extended to support MPLS-TP Tunnels, namely, MPLS-TE-EXT-STD-MIB, MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB, and MPLS-LSR-EXT-STD-MIB. The following section provides the summary of changes.
扩展了四个MIB模块以支持MPLS-TP隧道，即MPLS-TE-EXT-STD-MIB、MPLS-TC-EXT-STD-MIB、MPLS-ID-STD-MIB和MPLS-LSR-EXT-STD-MIB。以下部分提供了更改的摘要。
- Node configuration table (mplsTunnelExtNodeConfigTable) for setting the local identifier for Tunnel Ingress and Egress identifiers.
- 用于设置隧道入口和出口标识符的本地标识符的节点配置表（mplsTunnelExtNodeConfigTable）。
- Node IP map table (mplsTunnelExtNodeIpMapTable) for querying the local identifier for a given Global_ID and Node_ID.
- 节点IP映射表（mplsTunnelExtNodeIpMapTable），用于查询给定全局\u ID和节点\u ID的本地标识符。
- Node ICC map table (mplsTunnelExtNodeIccMapTable) for querying the local identifier for a given ICC_Operator_ID and Node_ID.
- 节点ICC映射表（mplsTunnelExtNodeIccMapTable），用于查询给定ICC_运算符_ID和节点_ID的本地标识符。
- Tunnel extension table (mplsTunnelExtTable) for setting up MPLS-TP Tunnels with sparse extension of mplsTunnelTable.
- 隧道扩展表（mplsTunnelExtTable），用于设置具有MPLStunneltTable稀疏扩展的MPLS-TP隧道。
- Textual conventions and object definitions for MPLS-TP Tunnels.
- MPLS-TP隧道的文本约定和对象定义。
- Cross-connect extension table (mplsXCExtTable) for setting up the MPLS-TP LSPs.
- 用于设置MPLS-TP LSP的交叉连接扩展表（mplsXCExtTable）。
These tables are described in the subsequent sections.
这些表格将在后续章节中介绍。
The TE MIB module extensions and details of the tables are described in the following sections.
TE MIB模块扩展和表的详细信息将在以下部分中描述。
The mplsTunnelExtNodeConfigTable is used to assign a local identifier for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID combination as defined in [RFC6923] and [RFC6370], respectively. The CC is a string of two characters, each being an uppercase Basic Latin alphabetic (i.e., A-Z). The ICC is a string of one to six characters, each an uppercase Basic Latin alphabetic (i.e., A-Z) or numeric (i.e., 0-9). All of the characters are encoded using [T.50] as described in [RFC6370].
mplsTunnelExtNodeConfigTable用于分别为[RFC6923]和[RFC6370]中定义的给定ICC_运算符_ID:：Node_ID或全局_ID:：Node_ID组合分配本地标识符。CC是由两个字符组成的字符串，每个字符都是大写的基本拉丁字母（即a-Z）。ICC是一个由一到六个字符组成的字符串，每个字符都是大写的基本拉丁字母（即a-Z）或数字（即0-9）。所有字符都使用[RFC6370]中所述的[T.50]进行编码。
In the IP-compatible mode, Global_ID::Node_ID, is used to uniquely identify a node. For each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a unique entry in the table representing a node. As the regular TE tunnels use the IP address as the LSR ID, the local identifier should be below the first valid IP address, which is 16777216[1.0.0.0]. Every node is assigned a local identifier within a range of 0 to 16777215. This local identifier is used for indexing into mplsTunnelTable as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId.
在IP兼容模式下，全局_ID:：节点_ID用于唯一标识节点。对于每个ICC_运算符_ID:：Node_ID或Global_ID:：Node_ID，表中有一个表示节点的唯一条目。由于常规TE隧道使用IP地址作为LSR ID，因此本地标识符应低于第一个有效IP地址，即16777216[1.0.0.0]。在0到16777215的范围内，为每个节点分配一个本地标识符。此本地标识符用于索引到mplsTunnelTable，即MPLStunneLingResslId和MPLStunneleGreslId。
For IP-compatible environments, an MPLS-TP Tunnel is indexed by Tunnel Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination Global_ID, and Destination Node_ID.
对于IP兼容环境，MPLS-TP隧道通过隧道索引、隧道实例、源全局\u ID、源节点\u ID、目标全局\u ID和目标节点\u ID进行索引。
For ICC-based environments, an MPLS-TP Tunnel is indexed by Tunnel Index, Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination CC, Destination ICC, and Destination Node_ID.
对于基于ICC的环境，MPLS-TP隧道通过隧道索引、隧道实例、源CC、源ICC、源节点ID、目标CC、目标ICC和目标节点ID进行索引。
As mplsTunnelTable is indexed by mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be used directly.
由于mplsTunnelTable由mplsTunnelIndex、MPLStunnelinInstance、MPLStunneLingResslrid和MPLStunneleResslrid编制索引，因此不能直接使用MPLS-TP隧道标识符。
The mplsTunnelExtNodeConfigTable will be used to store an entry for ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local identifier to be used as the LSR ID in mplsTunnelTable.
mplsTunnelExtNodeConfigTable将用于存储ICC_操作员_ID:：Node_ID或全局_ID:：Node_ID的条目，其本地标识符将用作mplsTunnelTable中的LSR ID。
The read-only mplsTunnelExtNodeIpMapTable is used to query the local identifier assigned and stored in mplsTunnelExtNodeConfigTable for a given Global_ID::Node_ID. In order to query the local identifier, in
只读mplsTunnelExtNodeIpMapTable用于查询分配并存储在mplsTunnelExtNodeConfigTable中的给定全局\u ID:：节点\u ID的本地标识符
the IP-compatible mode, this table is indexed with Global_ID::Node_ID. In the IP-compatible mode for a TP tunnel, Global_ID::Node_ID is used.
在IP兼容模式下，此表使用全局_ID:：Node_ID编制索引。在TP隧道的IP兼容模式下，使用全局_ID:：Node_ID。
A separate query is made to get the local identifier of both Ingress and Egress Global_ID::Node_ID identifiers. These local identifiers are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when indexing mplsTunnelTable.
进行单独的查询以获取入口和出口全局_ID：：节点_ID标识符的本地标识符。在索引mplsTunnelTable时，这些本地标识符用作MPLStunneLingResslId和MPLStunneleResslId。
The read-only mplsTunnelExtNodeIccMapTable is used to query the local identifier assigned and stored in the mplsTunnelExtNodeConfigTable for a given ICC_Operator_ID::Node_ID.
只读mplsTunnelExtNodeIccMapTable用于查询分配并存储在mplsTunnelExtNodeConfigTable中的给定ICC_运算符_ID:：Node_ID的本地标识符。
A separate query is made to get the local identifier of both Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId when indexing mplsTunnelTable.
进行单独的查询以获取入口和出口ICC_操作员_ID:：节点_ID的本地标识符。在索引mplsTunnelTable时，这些本地标识符用作MPLStunneLingResslrid和MPLStunnelegressrid。
This table sparsely extends the mplsTunnelTable in order to support MPLS-TP Tunnels with additional objects. All the additional attributes specific to supporting a TP tunnel are contained in this extended table and could be accessed with the mplsTunnelTable indices.
该表稀疏地扩展了mplsTunnelTable，以支持带有附加对象的MPLS-TP隧道。所有特定于支持TP隧道的附加属性都包含在此扩展表中，可以使用mplsTunnelTable索引进行访问。
The gmplsTunnelReversePerfTable [RFC4802] should be used 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.
应使用GMPLSTunnelReverseperTable[RFC4802]为双向隧道的反向提供每个隧道数据包的性能信息。它可以被看作是对mplsTunnelPerfTable的补充，它增强了mplsTunnelTable。
This MIB module contains textual conventions for LSPs of MPLS-based transport networks.
此MIB模块包含基于MPLS的传输网络的LSP的文本约定。
This MIB module contains identifier object definitions for MPLS Traffic Engineering in transport networks.
此MIB模块包含传输网络中MPLS流量工程的标识符对象定义。
This MIB module contains generic object definitions (including the mplsXCExtTable -- cross-connect extension table -- for setting up the MPLS-TP LSPs with sparse extension of mplsXCTable) for MPLS LSRs in transport networks.
此MIB模块包含传输网络中MPLS LSR的通用对象定义（包括mplsXCExtTable——交叉连接扩展表——用于设置具有mplsXCTable稀疏扩展的MPLS-TP LSP）。
This document follows the RowPointer usage as described in Section 10 of [RFC3812].
本文档遵循[RFC3812]第10节所述的行指针用法。
A new RowPointer object, mplsTunnelExtOppositeDirPtr, is added to mplsTunnelExtTable of MPLS-TE-EXT-STD-MIB module. This RowPointer object points to the tunnel entry in the opposite direction.
MPLS-TE-EXT-STD-MIB模块的MPLStunneLextTopPositeDirpter中添加了一个新的行指针对象。此RowPointer对象指向相反方向的隧道入口。
Two additional RowPointers objects, mplsXCExtTunnelPointer and mplsXCExtOppositeDirXCPtr, are added to the mplsXCExtTable of MPLS-LSR-EXT-STD-MIB. The RowPointer mplsXCExtTunnelPointer is a read-only object used to indicate the back pointer to the tunnel entry. The RowPointer mplsXCExtOppositeDirXCPtr object points to the opposite-direction XC entry.
MPLS-LSR-EXT-STD-MIB的mplsXCExtTable中添加了两个额外的行指针对象mplsXCExtTunnelPointer和MPLSXCEXTantipiteDirXCPTR。行指针mplsXCExtTunnelPointer是一个只读对象，用于指示隧道条目的后指针。行指针mplsxcextopposititedirxcptr对象指向相反方向的XC条目。
If either of these RowPointers return zeroDotZero, it implies that there is no entry associated with the RowPointer object.
如果这些行指针中的任何一个返回zeroDotZero，则表示没有与RowPointer对象关联的条目。
This section provides an overview of the relationships between the MPLS-TP TE MIB module and other MPLS MIB modules.
本节概述了MPLS-TP TE MIB模块与其他MPLS MIB模块之间的关系。
The arrows in the following diagram show a "depends on" relationship. A relationship of "MIB module A depends on MIB module B" means that MIB module A uses an object, object identifier, or textual convention defined in MIB module B, or that MIB module A contains a pointer (index or RowPointer) to an object in MIB module B.
下图中的箭头显示了“依赖”关系。“MIB模块A依赖于MIB模块B”的关系表示MIB模块A使用MIB模块B中定义的对象、对象标识符或文本约定，或者MIB模块A包含指向MIB模块B中对象的指针（索引或行指针）。
MPLS-TC-EXT-STD-MIB
^
|
|
+<---- MPLS-ID-STD-MIB
^
| |
+<---- MPLS-TE-EXT-STD-MIB
| |
| V
| MPLS-TE-STD-MIB
| |
| |
| V
| MPLS-LSR-STD-MIB
| ^
| |
| |
+------MPLS-LSR-EXT-STD-MIB
MPLS-TC-EXT-STD-MIB
^
|
|
+<---- MPLS-ID-STD-MIB
^
| |
+<---- MPLS-TE-EXT-STD-MIB
| |
| V
| MPLS-TE-STD-MIB
| |
| |
| V
| MPLS-LSR-STD-MIB
| ^
| |
| |
+------MPLS-LSR-EXT-STD-MIB
Figure 2: MIB Modules' Interdependencies
图2:MIB模块的相互依赖关系
Thus:
因此：
- All the new MPLS extension MIB modules depend on MPLS-TC-EXT-STD-MIB.
- 所有新的MPLS扩展MIB模块都依赖于MPLS-TC-EXT-STD-MIB。
- MPLS-ID-STD-MIB contains references to objects in MPLS-TE-STD-MIB [RFC3812].
- MPLS-ID-STD-MIB包含对MPLS-TE-STD-MIB[RFC3812]中对象的引用。
- MPLS-TE-EXT-STD-MIB contains references to objects in MPLS-TE-STD-MIB [RFC3812].
- MPLS-TE-EXT-STD-MIB包含对MPLS-TE-STD-MIB[RFC3812]中对象的引用。
- MPLS-LSR-EXT-STD-MIB contains references to objects in MPLS-LSR-STD-MIB [RFC3813].
- MPLS-LSR-EXT-STD-MIB包含对MPLS-LSR-STD-MIB[RFC3813]中对象的引用。
The mplsTunnelExtTable sparsely extends the mplsTunnelTable of MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse-direction tunnel information.
mplsTunnelExtTable稀疏地扩展了MPLS-TE-STD-MIB的MPLStunneltTable[RFC3812]。这有助于关联反向通道信息。
The mplsXCExtTable sparsely extends the mplsXCTable of MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the tunnel entry for easy tunnel access from the XC entry.
MPLSXcextable稀疏地扩展了MPLS-LSR-STD-MIB[RFC3813]的mplsXCTable。这有助于指向隧道入口，便于从XC入口进入隧道。
Note that all of the MIB modules shown above in the figure also have a dependency on MPLS-TC-STD-MIB.
请注意，上图中显示的所有MIB模块也依赖于MPLS-TC-STD-MIB。
The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another.
MPLS-TE-EXT-STD-MIB中的表格如下图所示。箭头表示从一个表到另一个表的引用。
mplsTunnelExtNodeConfigTable
^ ^ ^
| | |
| | |
| | |
| | +----------------------+
| | |
| mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable
|
| mplsXCExtTable
| | ^
| +---------+ |
| | |
| | |
| V V
mplsTunnelTable ---->mplsXCTable
^
|
|
|
mplsTunnelExtTable
mplsTunnelExtNodeConfigTable
^ ^ ^
| | |
| | |
| | |
| | +----------------------+
| | |
| mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable
|
| mplsXCExtTable
| | ^
| +---------+ |
| | |
| | |
| V V
mplsTunnelTable ---->mplsXCTable
^
|
|
|
mplsTunnelExtTable
Figure 3: Dependencies between MIB Module Tables
图3:MIB模块表之间的依赖关系
An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID with the local number in order to accommodate in the existing tunnel table's ingress/egress LSR ID.
现有mplsTunnelTable使用mplsTunnelExtNodeConfigTable表将全局_ID:：Node_ID和/或ICC_Operator_ID:：Node_ID映射到本地编号，以便在现有隧道表中容纳入口/出口LSR ID。
The new mplsTunnelExtTable provides the reverse-direction LSP information for the existing tunnel table so that bidirectional LSPs can be created.
新的mplsTunnelExtTable为现有隧道表提供反向LSP信息，以便可以创建双向LSP。
The mplsXCExtTable sparsely extends the mplsLsrXCTable to provide backward reference to tunnel entry.
mplsXCExtTable稀疏地扩展了MPLSSRXCTABLE，以提供对隧道入口的向后引用。
In this section, we provide an example of configuring MPLS-TP bidirectional tunnels with IP tunnel identifiers. This example provides the usage of the MPLS-TP Tunnel MIB along with the extended MIB modules introduced in this document.
在本节中，我们提供了一个使用IP隧道标识符配置MPLS-TP双向隧道的示例。此示例提供了MPLS-TP隧道MIB以及本文介绍的扩展MIB模块的用法。
Do note that a MPLS-TP Tunnel could be set up statically as well as signaled via the control plane. This example considers accessing MIB objects on a head-end for static and signaled MPLS-TP Tunnels. This section shows the configuration of the forward- and reverse-direction MPLS-TP LSPs that run between East and West, and vice versa. Only objects relevant to MPLS-TP Tunnels are illustrated here.
请注意，MPLS-TP隧道可以静态设置，也可以通过控制平面发出信号。本例考虑访问静态和信号MPLS-TP隧道前端的MIB对象。本节显示了在东西方向之间运行的正向和反向MPLS-TP LSP的配置，反之亦然。此处仅说明与MPLS-TP隧道相关的对象。
In mplsTunnelExtNodeConfigTable:
在mplsTunnelExtNodeConfigTable中：
{ -- Non-IP Ingress LSR_ID (Index to the table)
{--非IP入口LSR_ID（表的索引）
mplsTunnelExtNodeConfigLocalId = 1,
mplsTunnelExtNodeConfigLocalId=1，
mplsTunnelExtNodeConfigGlobalId = 1234, mplsTunnelExtNodeConfigNodeId = 10, -- Mandatory parameters needed to activate the row go here mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
mplsTunnelExtNodeConfigGlobalId=1234，mplsTunnelExtNodeConfigNodeId=10，--激活行所需的必需参数转到此处mplsTunnelExtNodeConfigRowStatus=createAndGo（4）
-- Non-IP Egress LSR ID (Index to the table)
mplsTunnelExtNodeConfigLocalId = 2,
mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 20,
-- Mandatory parameters needed to activate the row go here
mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
}
-- Non-IP Egress LSR ID (Index to the table)
mplsTunnelExtNodeConfigLocalId = 2,
mplsTunnelExtNodeConfigGlobalId = 1234,
mplsTunnelExtNodeConfigNodeId = 20,
-- Mandatory parameters needed to activate the row go here
mplsTunnelExtNodeConfigRowStatus = createAndGo (4)
}
This will create an entry in the mplsTunnelExtNodeConfigTable for a Global_ID::Node_ID. The Ingress and Egress LSR are represented by separate entries.
这将在mplsTunnelExtNodeConfigTable中为全局_ID:：节点_ID创建一个条目。入口和出口LSR由单独的条目表示。
The following read-only mplsTunnelExtNodeIpMapTable table is populated automatically upon creating an entry in mplsTunnelExtNodeConfigTable, and this table is used to retrieve the local identifier for the given Global_ID::Node_ID.
在mplsTunnelExtNodeConfigTable中创建条目时，将自动填充以下只读mplsTunnelExtNodeIpMapTable表，该表用于检索给定全局\u ID:：节点\u ID的本地标识符。
In mplsTunnelExtNodeIpMapTable:
在mplsTunnelExtNodeIpMapTable中：
{
-- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 10,
mplsTunnelExtNodeIpMapLocalId = 1
{
-- Global_ID (Index to the table)
mplsTunnelExtNodeIpMapGlobalId = 1234,
-- Node Identifier (Index to the table)
mplsTunnelExtNodeIpMapNodeId = 10,
mplsTunnelExtNodeIpMapLocalId = 1
-- Global_ID (Index to the table) mplsTunnelExtNodeIpMapGlobalId = 1234,
--全局_ID（表的索引）mplsTunnelExtNodeIpMapGlobalId=1234，
-- Node Identifier (Index to the table) mplsTunnelExtNodeIpMapNodeId = 20, mplsTunnelExtNodeIpMapLocalId = 2 }
--节点标识符（表的索引）mplstunnelextnodeippanodeid=20，mplsTunnelExtNodeIpMapLocalId=2}
The following denotes the co-routed bidirectional tunnel "head" entry.
以下为同向双向隧道“头部”入口。
In mplsTunnelTable:
在mplsTunnelTable中：
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 1,
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
-- An MPLS extension table
In mplsTunnelExtTable:
{
-- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel
-- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
-- An MPLS extension table
In mplsTunnelExtTable:
{
-- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by single tunnel
-- entry
mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
Next, we must create the appropriate in-segment and out-segment entries. These are done in [RFC3813] using the mplsInSegmentTable and mplsOutSegmentTable.
接下来，我们必须创建适当的段内和段外条目。这些都是在[RFC3813]中使用mplsInSegmentTable和mplsOutSegmentTable完成的。
For the forward direction:
前进方向：
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label
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) }
--行指针必须指向第一个可访问的列。mplsOutSegmentTrafficParamPtr=0.0，mplsOutSegmentRowStatus=createAndGo（4）}
For the reverse direction:
对于反向：
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentRowStatus = createAndGo (4) }
--行指针必须指向第一个可访问的列。mplsInSegmentTrafficParamPtr=0.0，mplsInSegmentRowStatus=createAndGo（4）}
Next, two cross-connect entries are created in the mplsXCTable of the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created segments together.
接下来，在MPLS-LSR-STD-MIB[RFC3813]的mplsXCTable中创建两个交叉连接条目，从而将新创建的段关联在一起。
In mplsXCTable: { mplsXCIndex = 0x01, mplsXCInSegmentIndex = 0x00000000, mplsXCOutSegmentIndex = 0x00000001, mplsXCLspId = 0x0102 -- unique ID
在mplsXCTable中：{mplsXCIndex=0x01，MPLSXCINSectionIndex=0x00000000，mplsXCOutSegmentIndex=0x00000001，mplsXCLspId=0x0102--唯一ID
-- only a single outgoing label mplsXCLabelStackIndex = 0x00, mplsXCRowStatus = createAndGo(4)
--只有一个传出标签mplsXCLabelStackIndex=0x00，mplsXCRowStatus=createAndGo（4）
}
}
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000001,
mplsXCOutSegmentIndex = 0x00000000,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
This table entry is extended by an 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.
此表条目由mplsXCExtTable中的一个条目扩展。请注意，“extends”关系的本质是稀疏扩充，因此mplsXCExtTable中的项与mplsXCTable中的项具有相同的索引值。
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
Next, for the reverse direction:
接下来，对于反向：
In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
The MPLS-TP associated bidirectional tunnel is implemented by two different unidirectional tunnels (Forward and Reverse LSPs), and these are associated together using mplsTunnelExtTable. Two different tunnel entries to provide the forward and reverse directions MAY be used for co-routed bidirectional tunnels as well.
MPLS-TP关联的双向隧道由两个不同的单向隧道（前向和反向LSP）实现，它们使用mplsTunnelExtTable关联在一起。提供正向和反向的两个不同隧道入口也可用于同向双向隧道。
The following denotes the associated bidirectional forward tunnel "head" entry:
以下表示相关的双向前方隧道“头部”入口：
In mplsTunnelTable:
在mplsTunnelTable中：
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 1,
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP associated bidirectional
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,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP associated bidirectional
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) }
mplstunnecludelaffinity=0，mplstunnelexcludeanaffinity=0，mplsTunnelRole=head（1），--激活行go here所需的强制参数mplsTunnelRowStatus=createAndGo（4）}
For the associated bidirectional forward LSP, in mplsTunnelExtTable:
对于关联的双向转发LSP，在mplsTunnelExtTable中：
{
mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
{
mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
For the forward direction:
前进方向：
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x0000001,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label
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) }
--行指针必须指向第一个可访问的列。mplsOutSegmentTrafficParamPtr=0.0，mplsOutSegmentRowStatus=createAndGo（4）}
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000000,
mplsXCOutSegmentIndex = 0x00000001,
mplsXCLspId = 0x0102 -- unique ID
-- only a single outgoing label
mplsXCLabelStackIndex = 0x00,
mplsXCRowStatus = createAndGo(4)
}
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
In mplsXCExtTable (0x01, 0x00000000, 0x00000001)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0
}
The following denotes the configured associated bidirectional reverse tunnel "tail" entry:
以下表示配置的相关双向反向隧道“尾部”入口：
In mplsTunnelTable:
在mplsTunnelTable中：
{
mplsTunnelIndex = 2,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 1,
mplsTunnelName = "TP associated bidirectional
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),
{
mplsTunnelIndex = 2,
mplsTunnelInstance = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR ID
mplsTunnelIngressLSRId = 2,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 1,
mplsTunnelName = "TP associated bidirectional
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
-- 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) }
mplsTunnelRowStatus=createAndGo（4）}
For the associated bidirectional reverse LSP, in mplsTunnelExtTable:
对于关联的双向反向LSP，在mplsTunnelExtTable中：
{
mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
{
mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
Next, we must create the appropriate in-segment and out-segment entries. These are done in [RFC3813] using the mplsInSegmentTable and mplsOutSegmentTable.
接下来，我们必须创建适当的段内和段外条目。这些都是在[RFC3813]中使用mplsInSegmentTable和mplsOutSegmentTable完成的。
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x0000001
mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentRowStatus = createAndGo (4) }
--行指针必须指向第一个可访问的列。mplsInSegmentTrafficParamPtr=0.0，mplsInSegmentRowStatus=createAndGo（4）}
Next, two cross-connect entries are created in the mplsXCTable of the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created segments together.
接下来，在MPLS-LSR-STD-MIB[RFC3813]的mplsXCTable中创建两个交叉连接条目，从而将新创建的段关联在一起。
In mplsXCTable: { mplsXCIndex = 0x01, mplsXCInSegmentIndex = 0x00000001, mplsXCOutSegmentIndex = 0x00000000, mplsXCLspId = 0x0102 -- unique ID -- only a single outgoing label mplsXCLabelStackIndex = 0x00,
在mplsXCTable中：{mplsXCIndex=0x01，MPLSXCINSectionIndex=0x00000001，mplsXCOutSegmentIndex=0x00000000，mplsXCLspId=0x0102--唯一ID--仅一个传出标签mplsXCLabelStackIndex=0x00，
mplsXCRowStatus = createAndGo(4) }
mplsXCRowStatus=createAndGo（4）}
This table entry is extended by an 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.
此表条目由mplsXCExtTable中的一个条目扩展。请注意，“extends”关系的本质是稀疏扩充，因此mplsXCExtTable中的项与mplsXCTable中的项具有相同的索引值。
Next, for the reverse direction:
接下来，对于反向：
In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
In mplsXCExtTable (0x01, 0x00000001, 0x00000000)
{
-- Back pointer from XC table to Tunnel table
mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1
mplsXCExtOppositeDirXCPtr =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1
}
The following denotes the co-routed bidirectional tunnel "head" entry. In intermediate and tail-end nodes, the tunnel table and its associated tables are created by the local management subsystem (e.g., agent) when the MPLS-TP Tunnel is signaled successfully. Refer to [RFC3812] and [RFC4802] for examples of signaled tunnel table configuration.
以下为同向双向隧道“头部”入口。在中间和终端节点中，当MPLS-TP隧道成功发出信号时，本地管理子系统（例如，代理）将创建隧道表及其关联表。参考[RFC3812]和[RFC4802]了解信号隧道表配置示例。
In mplsTunnelTable:
在mplsTunnelTable中：
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 0,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id. For the intermediate and tail-end nodes,
-- the local management entity is expected to pick the first
-- available local identifier that is not used in mplsTunnelTable.
mplsTunnelIngressLSRId = 1,
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 0,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Ingress LSR-Id. For the intermediate and tail-end nodes,
-- the local management entity is expected to pick the first
-- available local identifier that is not used in mplsTunnelTable.
mplsTunnelIngressLSRId = 1,
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- Local map number created in mplsTunnelExtNodeConfigTable for
-- Egress LSR ID
mplsTunnelEgressLSRId = 2,
mplsTunnelName = "TP co-routed bidirectional LSP",
mplsTunnelDescr = "East to West",
mplsTunnelIsIf = true (1),
-- RowPointer MUST point to the first accessible column
mplsTunnelXCPointer =
mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1,
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (0),
-- RowPointer MUST point to the first accessible column
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelRole = head (1),
-- Mandatory parameters needed to activate the row go here
mplsTunnelRowStatus = createAndGo (4)
}
-- 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)
}
-- An MPLS extension table
In mplsTunnelExtTable:
{
-- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by a single
-- tunnel entry
mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
-- An MPLS extension table
In mplsTunnelExtTable:
{
-- This opposite-direction tunnel pointer may point to 0.0
-- if co-routed bidirectional tunnel is managed by a single
-- tunnel entry
mplsTunnelExtOppositeDirTnlPtr = 0.0
-- Set both the Ingress and Egress LocalId objects to TRUE, as
-- this tunnel entry uses the local identifiers.
mplsTunnelExtIngressLSRLocalIdValid = true,
mplsTunnelExtEgressLSRLocalIdValid = true
}
Next, we must create the appropriate in-segment and out-segment entries. These are done in [RFC3813] using the mplsInSegmentTable and mplsOutSegmentTable.
接下来，我们必须创建适当的段内和段外条目。这些都是在[RFC3813]中使用mplsInSegmentTable和mplsOutSegmentTable完成的。
The forward-direction mplsOutSegmentTable will be populated automatically based on the information received from the signaling protocol.
将根据从信令协议接收到的信息自动填充前进方向MPLSOUTSEGENTTABLE。
The reverse-direction mplsOutSegmentTable will be populated automatically based on the information received from the signaling protocol.
反向MPLSOUTSEGENTTABLE将根据从信令协议接收到的信息自动填充。
Next, two cross-connect entries are created in the mplsXCTable of the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created segments together.
接下来，在MPLS-LSR-STD-MIB[RFC3813]的mplsXCTable中创建两个交叉连接条目，从而将新创建的段关联在一起。
The forward-direction mplsXCEntry will be populated as soon as the forward-path label information is available.
前进方向mplsXCEntry将在前进路径标签信息可用时立即填充。
The reverse-direction mplsXCEntry will be populated as soon as the reverse-path label information is available.
一旦反向路径标签信息可用，将立即填充反向mplsXCEntry。
This table entry is extended by an 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.
此表条目由mplsXCExtTable中的一个条目扩展。请注意，“extends”关系的本质是稀疏扩充，因此mplsXCExtTable中的项与mplsXCTable中的项具有相同的索引值。
Once the forward path information is negotiated using the signaling protocol, the forward-direction mplsXCExtEntry will be created for associating the opposite-direction XC entry and tunnel table entry.
使用信令协议协商前向路径信息后，将创建前向mplsXCExtEntry，用于关联反向XC条目和隧道表条目。
Once the reverse path information is negotiated using the signaling protocol, the reverse-direction mplsXCExtEntry will be created for associating the opposite-direction XC entry and tunnel table entry.
一旦使用信令协议协商反向路径信息，将创建反向mplsXCExtEntry，用于关联反向XC条目和隧道表条目。
MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN
MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, Unsigned32 FROM SNMPv2-SMI -- RFC 2578
从SNMPv2 SMI--RFC 2578导入模块标识，未签名32
TEXTUAL-CONVENTION FROM SNMPv2-TC -- RFC 2579
SNMPv2 TC的文本约定——RFC2579
mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811
来自MPLS-TC-STD-MIB的mplsStdMIB——RFC 3811
;
;
mplsTcExtStdMIB MODULE-IDENTITY
mplsTcExtStdMIB模块标识
LAST-UPDATED "201502020000Z" -- February 2, 2015 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com
最后更新的“201502020000Z”-2015年2月2日组织“多协议标签交换（MPLS）工作组”联系方式“Venkatesan Mahalingam Dell Inc.，地址：美国加利福尼亚州圣克拉拉大美洲大道5450号，邮编：95054，电子邮件：venkat。mahalingams@gmail.com
Kannan KV Sampath Redeem, India Email: kannankvs@gmail.com
Kannan KV Sampath兑换，印度电子邮件：kannankvs@gmail.com
Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com
山姆·奥尔德林华为技术公司，美国加利福尼亚州圣克拉拉中央快速路2330号，邮编95051，电子邮件：奥尔德林。ietf@gmail.com
Thomas D. Nadeau Email: tnadeau@lucidvision.com " DESCRIPTION "This MIB module contains Textual Conventions for LSPs of MPLS-based transport networks.
Thomas D.Nadeau电子邮件：tnadeau@lucidvision.com“说明”此MIB模块包含基于MPLS的传输网络的LSP的文本约定。
Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2015 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
-- Revision history.
--修订历史。
REVISION "201502020000Z" -- February 2, 2015 DESCRIPTION "MPLS Textual Convention Extensions"
修订版“201502020000Z”-2015年2月2日说明“MPLS文本约定扩展”
::= { mplsStdMIB 17 }
::= { mplsStdMIB 17 }
MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This object contains the Textual Convention for an IP-based
operator-unique identifier (Global_ID). The Global_ID can
contain the 2-octet or 4-octet value of the operator's
Autonomous System Number (ASN).
MplsGlobalId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This object contains the Textual Convention for an IP-based
operator-unique identifier (Global_ID). The Global_ID can
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 ASN, the two high-order octets of this 4-octet identifier MUST be set to zero (0x00). Further, ASN 0 is reserved. The size of the Global_ID string MUST be zero if the Global_ID is invalid.
当全局_ID从2-八位字节ASN派生时，此4-八位字节标识符的两个高阶八位字节必须设置为零（0x00）。此外，ASN 0是保留的。如果全局\u ID无效，则全局\u ID字符串的大小必须为零。
Note that a Global_ID of zero is limited to entities contained within a single operator and MUST NOT be used across a Network-to-Network Interface (NNI). A non-zero Global_ID MUST be derived from an ASN owned by the operator." REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370, Section 3" SYNTAX OCTET STRING (SIZE (4))
请注意，全局_ID为零仅限于包含在单个运营商中的实体，不得在网络到网络接口（NNI）中使用。非零全局_ID必须从运营商拥有的ASN派生。“参考”MPLS传输配置文件（MPLS-TP）标识符，RFC 6370，第3节“语法八位字符串（大小（4））
MplsCcId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CC (Country Code) is a string of two characters, each
being an uppercase Basic Latin alphabetic (i.e., A-Z).
MplsCcId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CC (Country Code) is a string of two characters, each
being an uppercase Basic Latin alphabetic (i.e., A-Z).
The characters are encoded using ITU-T Recommendation T.50. The size of the CC string MUST be zero if the CC identifier is invalid." REFERENCE "MPLS-TP Identifiers Following ITU-T Conventions, RFC 6923, Section 3. International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information exchange, ITU-T Recommendation T.50, September 1992." SYNTAX OCTET STRING (SIZE (0|2))
使用ITU-T建议T.50对字符进行编码。如果CC标识符无效，CC字符串的大小必须为零。“参考”MPLS-TP标识符遵循ITU-T公约，RFC 6923，第3节。国际参考字母表（IRA）（前国际字母表5或IA5）-信息技术-信息交换用7位编码字符集，ITU-T建议T.50，1992年9月。“语法八位字符串（大小（0 | 2））
MplsIccId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ICC is a string of one to six characters, each
an uppercase Basic Latin alphabetic (i.e., A-Z) or
numeric (i.e., 0-9). The characters are encoded
using ITU-T Recommendation T.50. The size of
the ICC string MUST be zero if the ICC identifier
is invalid."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3.
International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992."
SYNTAX OCTET STRING (SIZE (0|1..6))
MplsIccId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ICC is a string of one to six characters, each
an uppercase Basic Latin alphabetic (i.e., A-Z) or
numeric (i.e., 0-9). The characters are encoded
using ITU-T Recommendation T.50. The size of
the ICC string MUST be zero if the ICC identifier
is invalid."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3.
International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) - Information
technology - 7-bit coded character set for information
exchange, ITU-T Recommendation T.50, September 1992."
SYNTAX OCTET STRING (SIZE (0|1..6))
MplsNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID.
MplsNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The Node_ID is assigned within the scope of
the Global_ID/ICC_Operator_ID.
When IPv4 addresses are in use, the value of this object can be derived from the LSR's IPv4 loopback address. When IPv6 addresses are in use, the value of this object can be a 32-bit value unique within the scope of a Global_ID.
当使用IPv4地址时，此对象的值可以从LSR的IPv4环回地址派生。当使用IPv6地址时，此对象的值可以是全局\u ID范围内唯一的32位值。
Note that, when IP reachability is not needed, the 32-bit Node_ID is not required to have any association with the IPv4 address space. The value of 0 indicates an invalid Node_ID."
请注意，当不需要IP可达性时，32位节点_ID不需要与IPv4地址空间有任何关联。值0表示节点ID无效。“
REFERENCE "MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370, Section 4" SYNTAX Unsigned32 (0|1..4294967295)
参考“MPLS传输配置文件（MPLS-TP）标识符，RFC 6370，第4节”语法Unsigned32（0 | 1..4294967295）
-- MPLS-TC-EXT-STD-MIB module ends END
--MPLS-TC-EXT-STD-MIB模块结束
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId FROM MPLS-TC-EXT-STD-MIB ;
从SNMPv2 SMI导入模块标识、对象类型——从SNMPv2 CONF导入RFC 2578模块符合性、从MPLS-TC-STD-MIB导入对象组——从MPLS-TC-STD-MIB导入RFC 2580 MPLSTDMIB——从MPLS-TC-EXT-STD-MIB导入RFC 3811 MplsGlobalId、MplsCcId、MPLSICID、MplsNodeId；
mplsIdStdMIB MODULE-IDENTITY LAST-UPDATED "201502020000Z" -- February 2, 2015 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
mplsIdStdMIB模块标识最后更新“201502020000Z”--2015年2月2日组织“多协议标签交换（MPLS）工作组”
CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com
联系信息“Venkatesan Mahalingam Dell Inc.，5450 Great America Parkway，Santa Clara，CA 95054，美国电子邮件：venkat。mahalingams@gmail.com
Kannan KV Sampath Redeem, India Email: kannankvs@gmail.com
Kannan KV Sampath兑换，印度电子邮件：kannankvs@gmail.com
Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com
山姆·奥尔德林华为技术公司，美国加利福尼亚州圣克拉拉中央快速路2330号，邮编95051，电子邮件：奥尔德林。ietf@gmail.com
Thomas D. Nadeau Email: tnadeau@lucidvision.com " DESCRIPTION "This MIB module contains identifier object definitions for MPLS Traffic Engineering in transport networks.
Thomas D.Nadeau电子邮件：tnadeau@lucidvision.com“说明”此MIB模块包含传输网络中MPLS流量工程的标识符对象定义。
Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2015 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
-- Revision history.
--修订历史。
REVISION "201502020000Z" -- February 2, 2015 DESCRIPTION "This MIB modules defines the MIB objects for MPLS-TP identifiers"
修订版“201502020000Z”-2015年2月2日描述“此MIB模块为MPLS-TP标识符定义MIB对象”
::= { mplsStdMIB 18 }
::= { mplsStdMIB 18 }
-- notifications
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- notifications
mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 }
-- tables, scalars
mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 }
-- conformance
mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 }
-- MPLS common objects
--公共对象
mplsIdGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique operator identifier, also called the MPLS-TP
Global_ID.
If this value is used in mplsTunnelExtNodeConfigGlobalId
for mapping Global_ID::Node_ID with the local identifier,
then this object value MUST NOT be changed."
::= { mplsIdObjects 1 }
mplsIdGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a unique operator identifier, also called the MPLS-TP
Global_ID.
If this value is used in mplsTunnelExtNodeConfigGlobalId
for mapping Global_ID::Node_ID with the local identifier,
then this object value MUST NOT be changed."
::= { mplsIdObjects 1 }
mplsIdNodeId OBJECT-TYPE
SYNTAX MplsNodeId
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/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier,
then this object value SHOULD NOT be changed.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
::= { mplsIdObjects 2 }
mplsIdNodeId OBJECT-TYPE
SYNTAX MplsNodeId
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/ICC_Operator_ID.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping Global_ID::Node_ID with the local identifier,
then this object value SHOULD NOT be changed.
If this value is used in mplsTunnelExtNodeConfigNodeId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
::= { mplsIdObjects 2 }
mplsIdCc OBJECT-TYPE
SYNTAX MplsCcId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a Country Code (CC) to the node. Global
uniqueness of ICC is assured by concatenating the ICC
with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsIdObjects 3 }
mplsIdCc OBJECT-TYPE
SYNTAX MplsCcId
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows the operator or service provider to
assign a Country Code (CC) to the node. Global
uniqueness of ICC is assured by concatenating the ICC
with a Country Code (CC).
If this value is used in mplsTunnelExtNodeConfigCcId
for mapping ICC_Operator_ID::Node_ID with the local
identifier, then this object value MUST NOT be changed."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsIdObjects 3 }
mplsIdIcc OBJECT-TYPE SYNTAX MplsIccId MAX-ACCESS read-write STATUS current DESCRIPTION "This object allows the operator or service provider to assign a unique MPLS-TP ITU-T Carrier Code (ICC) to the node. Together, the CC and the ICC form the ICC_Operator_ID as CC::ICC. If this value is used in mplsTunnelExtNodeConfigIccId for mapping ICC_Operator_ID::Node_ID with the local identifier, then this object value MUST NOT be changed." REFERENCE "MPLS-TP Identifiers Following ITU-T Conventions, RFC 6923, Section 3"
mplsIdIcc对象类型语法MPLSICID MAX-ACCESS读写状态当前描述“此对象允许运营商或服务提供商分配唯一的MPLS-TP ITU-T载波代码（ICC）到节点。CC和ICC一起形成ICC_操作员_ID为CC:：ICC。如果此值在mplsTunnelExtNodeConfigIccId中用于将ICC_操作员_ID:：node_ID与本地标识符映射，则此对象值不得更改。“参考“遵循ITU-T约定的MPLS-TP标识符，RFC 6923，第3节”
::= { mplsIdObjects 4 }
::= { mplsIdObjects 4 }
-- Module compliance.
--模块合规性。
mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdCompliances
OBJECT IDENTIFIER ::= { mplsIdConformance 1 }
mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
mplsIdGroups
OBJECT IDENTIFIER ::= { mplsIdConformance 2 }
-- Compliance requirement for fully compliant implementations.
--完全合规实施的合规性要求。
mplsIdModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support of the MPLS-ID-STD-MIB module."
MPLSIDModulelCompliance MODULE-COMPLIANCE STATUS当前描述“提供MPLS-ID-STD-MIB模块完全支持的代理的符合性声明。”
MODULE -- this module
模块——这个模块
-- The mandatory group has to be implemented by all LSRs that
-- originate, terminate, or act as transit for MPLS-TP Tunnels.
-- The mandatory group has to be implemented by all LSRs that
-- originate, terminate, or act as transit for MPLS-TP Tunnels.
GROUP mplsIdIpOperatorGroup DESCRIPTION "This group is mandatory for devices that support IP-based identifier configuration."
GROUP mplsIdIpOperatorGroup DESCRIPTION“对于支持基于IP的标识符配置的设备，此组是必需的。”
GROUP mplsIdIccOperatorGroup DESCRIPTION "This group is mandatory for devices that support ICC-based identifier configuration."
组MPLSIDicCoperatGroup DESCRIPTION“对于支持基于ICC的标识符配置的设备，此组是必需的。”
::= { mplsIdCompliances 1 }
::= { mplsIdCompliances 1 }
-- Compliance requirement for read-only implementations.
--只读实现的法规遵从性要求。
mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that only provide read-only support for the MPLS-ID-STD-MIB module."
MPLSIDModuleRadonlyCompliance MODULE-COMPLIANCE状态当前描述“仅为MPLS-ID-STD-MIB模块提供只读支持的代理的符合性声明。”
MODULE -- this module
模块——这个模块
GROUP mplsIdIpOperatorGroup DESCRIPTION "This group is mandatory for devices that support IP-based identifier configuration."
GROUP mplsIdIpOperatorGroup DESCRIPTION“对于支持基于IP的标识符配置的设备，此组是必需的。”
GROUP mplsIdIccOperatorGroup DESCRIPTION "This group is mandatory for devices that support ICC-based identifier configuration."
组MPLSIDicCoperatGroup DESCRIPTION“对于支持基于ICC的标识符配置的设备，此组是必需的。”
OBJECT mplsIdGlobalId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsIdGlobalId最小访问只读描述“不需要写访问。”
OBJECT mplsIdNodeId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsIdNodeId MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsIdCc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsIdCc MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsIdIcc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsIdIcc最小访问只读描述“不需要写访问。”
::= { mplsIdCompliances 2 }
::= { mplsIdCompliances 2 }
-- Units of conformance.
--一致性单位。
mplsIdIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsIdGlobalId,
mplsIdNodeId
}
STATUS current
DESCRIPTION
"The objects in this group are optional for an
ICC-based node."
::= { mplsIdGroups 1 }
mplsIdIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsIdGlobalId,
mplsIdNodeId
}
STATUS current
DESCRIPTION
"The objects in this group are optional for an
ICC-based node."
::= { mplsIdGroups 1 }
mplsIdIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsIdNodeId,
mplsIdCc,
mplsIdIcc
}
STATUS current
DESCRIPTION
"The objects in this group are optional for an
IP-based node."
::= { mplsIdGroups 2 }
mplsIdIccOperatorGroup OBJECT-GROUP
OBJECTS { mplsIdNodeId,
mplsIdCc,
mplsIdIcc
}
STATUS current
DESCRIPTION
"The objects in this group are optional for an
IP-based node."
::= { mplsIdGroups 2 }
-- MPLS-ID-STD-MIB module ends END
--MPLS-ID-STD-MIB模块结束
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 RowPointer FROM SNMPv2-TC -- RFC 2579 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, mplsLsrNotificationGroup FROM MPLS-LSR-STD-MIB; -- RFC 3813
从SNMPv2 SMI导入模块标识、对象类型——从SNMPv2 CONF导入RFC 2578模块符合性、从SNMPv2 CONF导入对象组——从MPLS-TC-STD-MIB导入RFC 2580 mplsStdMIB——从SNMPv2 TC导入RFC 3811行指针——从RFC 2579 mplsXCIndex、MPLSXCINSSEGMENTINDEX、mplsXCOutSegmentIndex、MPLSINTERFACE组、mplsInSegmentGroup、mplsXCGroup、，来自MPLS-LSR-STD-MIB的MPLSSRNotificationGroup；——RFC3813
mplsLsrExtStdMIB MODULE-IDENTITY LAST-UPDATED "201502020000Z" -- February 2, 2015 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com
MPLSLRextstDMIB模块-身份最后更新“201502020000Z”--2015年2月2日组织“多协议标签交换（MPLS）工作组”联系方式“Venkatesan Mahalingam Dell Inc.，5450 Great America Parkway，Santa Clara，CA 95054，美国电子邮件：venkat。mahalingams@gmail.com
Kannan KV Sampath Redeem, India Email: kannankvs@gmail.com
Kannan KV Sampath兑换，印度电子邮件：kannankvs@gmail.com
Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com
山姆·奥尔德林华为技术公司，美国加利福尼亚州圣克拉拉中央快速路2330号，邮编95051，电子邮件：奥尔德林。ietf@gmail.com
Thomas D. Nadeau Email: tnadeau@lucidvision.com " DESCRIPTION "This MIB module contains generic object definitions for MPLS LSRs in transport networks.
Thomas D.Nadeau电子邮件：tnadeau@lucidvision.com“说明”此MIB模块包含传输网络中MPLS LSR的通用对象定义。
Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2015 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
-- Revision history.
--修订历史。
REVISION "201502020000Z" -- February 2, 2015 DESCRIPTION "MPLS LSR-specific MIB objects extension"
修订版“201502020000Z”-2015年2月2日说明“MPLS LSR特定MIB对象扩展”
::= { mplsStdMIB 19 }
::= { mplsStdMIB 19 }
-- notifications
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- notifications
mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 }
-- tables, scalars
mplsLsrExtObjects OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 1 }
-- conformance
mplsLsrExtConformance OBJECT IDENTIFIER
::= { mplsLsrExtStdMIB 2 }
-- MPLS LSR common objects
--公共对象
mplsXCExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB (RFC 3813) to provide MPLS-TP-specific
information about associated tunnel information"
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 }
mplsXCExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsXCExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsXCTable of
MPLS-LSR-STD-MIB (RFC 3813) to provide MPLS-TP-specific
information about associated tunnel information"
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsLsrExtObjects 1 }
mplsXCExtEntry OBJECT-TYPE SYNTAX MplsXCExtEntry MAX-ACCESS not-accessible
mplsXCExtEntry对象类型语法mplsXCExtEntry MAX-ACCESS不可访问
STATUS current DESCRIPTION "An entry in this table sparsely extends the cross-connect information represented by an entry in the mplsXCTable in MPLS-LSR-STD-MIB (RFC 3813) through a sparse augmentation. An entry can be created by a network operator via SNMP SET commands or in response to signaling protocol events." REFERENCE "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB), RFC 3813."
状态当前描述“此表中的条目通过稀疏扩充稀疏扩展MPLS-LSR-STD-MIB（RFC 3813）中mplsXCTable中的条目表示的交叉连接信息。网络运营商可通过SNMP SET命令或响应信令协议事件创建条目。”参考多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB），RFC 3813
INDEX { mplsXCIndex, mplsXCInSegmentIndex,
mplsXCOutSegmentIndex }
::= { mplsXCExtTable 1 }
INDEX { mplsXCIndex, mplsXCInSegmentIndex,
mplsXCOutSegmentIndex }
::= { mplsXCExtTable 1 }
MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTunnelPointer RowPointer,
mplsXCExtOppositeDirXCPtr RowPointer
}
MplsXCExtEntry ::= SEQUENCE {
mplsXCExtTunnelPointer RowPointer,
mplsXCExtOppositeDirXCPtr RowPointer
}
mplsXCExtTunnelPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This read-only object indicates the back pointer to the tunnel entry segment. The only valid value for Tunnel Pointer is mplsTunnelTable entry."
mplsXCExtTunnelPointer对象类型语法RowPointer MAX-ACCESS只读状态当前描述“此只读对象表示指向隧道入口段的后指针。隧道指针的唯一有效值是mplsTunnelTable入口。”
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 }
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 1 }
mplsXCExtOppositeDirXCPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the pointer to the opposite-
direction XC entry. This object cannot be modified if
mplsXCRowStatus for the corresponding entry in the
mplsXCTable is active(1). If this pointer is not set or
removed, mplsXCOperStatus should be set to down(2)."
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 2 }
mplsXCExtOppositeDirXCPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the pointer to the opposite-
direction XC entry. This object cannot be modified if
mplsXCRowStatus for the corresponding entry in the
mplsXCTable is active(1). If this pointer is not set or
removed, mplsXCOperStatus should be set to down(2)."
REFERENCE
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { mplsXCExtEntry 2 }
mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
mplsLsrExtCompliances
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
mplsLsrExtGroups
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
mplsLsrExtGroups
OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
-- Compliance requirement for fully compliant implementations.
--完全合规实施的合规性要求。
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."
MPLSRSExtModulelCompliance模块符合性状态当前说明“为MPLS-LSR-EXT-STD-MIB提供全面支持的代理的合规性声明。强制组必须由发起、终止或作为TE LSP/隧道中转的所有LSR实施。此外，根据支持的隧道类型，其他组成为强制性组，如下所述。”
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC 3813
模块MPLS-LSR-STD-MIB——MPLS-LSR-STD-MIB，RFC 3813
MANDATORY-GROUPS {
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsLsrNotificationGroup
}
MANDATORY-GROUPS {
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsLsrNotificationGroup
}
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
mplsXCExtGroup
}
MANDATORY-GROUPS {
mplsXCExtGroup
}
::= { mplsLsrExtCompliances 1 }
::= { mplsLsrExtCompliances 1 }
-- Compliance requirement for implementations that provide
-- read-only access.
-- Compliance requirement for implementations that provide
-- read-only access.
mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module."
mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS当前描述“仅为MPLS-LSR-EXT-STD-MIB提供只读支持的实现的符合性要求。然后可以监视此类设备，但不能使用此MIB模块进行配置。”
MODULE MPLS-LSR-STD-MIB
模块MPLS-LSR-STD-MIB
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup
}
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup
}
MODULE -- this module
模块——这个模块
GROUP mplsXCExtReadOnlyObjectsGroup DESCRIPTION "This group is mandatory for devices that support opposite-direction XC configuration of tunnels."
组mplsXCExtReadOnlyObjectsGroup DESCRIPTION“此组对于支持隧道反向XC配置的设备是必需的。”
-- mplsXCExtTable
OBJECT mplsXCExtOppositeDirXCPtr
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required.
This object indicates the pointer to the opposite-
direction XC entry. The only valid value for XC
Pointer is mplsXCTable entry."
::= { mplsLsrExtCompliances 2 }
-- mplsXCExtTable
OBJECT mplsXCExtOppositeDirXCPtr
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required.
This object indicates the pointer to the opposite-
direction XC entry. The only valid value for XC
Pointer is mplsXCTable entry."
::= { mplsLsrExtCompliances 2 }
-- Units of conformance.
--一致性单位。
mplsXCExtGroup OBJECT-GROUP
OBJECTS {
mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr
}
STATUS current
DESCRIPTION
"This object should be supported in order to access
the tunnel entry from the XC entry."
::= { mplsLsrExtGroups 1 }
mplsXCExtGroup OBJECT-GROUP
OBJECTS {
mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr
}
STATUS current
DESCRIPTION
"This object should be supported in order to access
the tunnel entry from the XC entry."
::= { mplsLsrExtGroups 1 }
mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP
OBJECTS {
mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr
}
STATUS current
DESCRIPTION
"This Object is needed to associate the opposite-direction
(forward/reverse) XC entry."
::= { mplsLsrExtGroups 2 }
mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP
OBJECTS {
mplsXCExtTunnelPointer,
mplsXCExtOppositeDirXCPtr
}
STATUS current
DESCRIPTION
"This Object is needed to associate the opposite-direction
(forward/reverse) XC entry."
::= { mplsLsrExtGroups 2 }
-- MPLS-LSR-EXT-STD-MIB module ends END
--MPLS-LSR-EXT-STD-MIB模块结束
This MIB module imports from [RFC2578], [RFC2579], [RFC2580], [RFC3289], [RFC3811], and [RFC3812].
此MIB模块从[RFC2578]、[RFC2579]、[RFC2580]、[RFC3289]、[RFC3811]和[RFC3812]导入。
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 TruthValue, RowStatus, RowPointer, StorageType FROM SNMPv2-TC -- RFC 2579 IndexIntegerNextFree FROM DIFFSERV-MIB -- RFC 3289 MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId FROM MPLS-TC-EXT-STD-MIB mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, MplsExtendedTunnelId FROM MPLS-TC-STD-MIB -- RFC 3811 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId
从SNMPv2 SMI导入模块标识、对象类型——从SNMPv2 CONF导入RFC 2578模块符合性、对象组——从SNMPv2 TC导入RFC 2580 TruthValue、RowStatus、RowPointer、StorageType——从DIFFSERV-MIB导入RFC 2579 IndexIntegerNextFree——从MPLS-TC-EXT-STD-MIB导入RFC 3289 MplsGlobalId、MplsNodeId、MplsCcId、MplsCcId、MplsCcId，MplsTunnelInstanceIndex，来自MPLS-TC-STD-MIB的MPLStunnelinedTunelId——RFC 3811 mplsTunnelIndex，mplsTunnelInstance，MPLStunnelingResslrid，MPLStunneleResslrid
FROM MPLS-TE-STD-MIB -- RFC 3812 ;
来自MPLS-TE-STD-MIB——RFC 3812；
mplsTeExtStdMIB MODULE-IDENTITY LAST-UPDATED "201502020000Z" -- February 2, 2015 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Venkatesan Mahalingam Dell Inc, 5450 Great America Parkway, Santa Clara, CA 95054, USA Email: venkat.mahalingams@gmail.com
MPLSTEXTSTDMIB MODULE-IDENTITY最后更新的“201502020000Z”--2015年2月2日组织“多协议标签交换（MPLS）工作组”联系方式“Venkatesan Mahalingam Dell Inc.，5450 Great America Parkway，Santa Clara，CA 95054，美国电子邮件：venkat。mahalingams@gmail.com
Kannan KV Sampath Redeem, India Email: kannankvs@gmail.com
Kannan KV Sampath兑换，印度电子邮件：kannankvs@gmail.com
Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051, USA Email: aldrin.ietf@gmail.com
山姆·奥尔德林华为技术公司，美国加利福尼亚州圣克拉拉中央快速路2330号，邮编95051，电子邮件：奥尔德林。ietf@gmail.com
Thomas D. Nadeau Email: tnadeau@lucidvision.com " DESCRIPTION "This MIB module contains generic object definitions for extending the MPLS Traffic Engineering tunnels in transport networks.
Thomas D.Nadeau电子邮件：tnadeau@lucidvision.com“说明”此MIB模块包含用于扩展传输网络中MPLS流量工程隧道的通用对象定义。
Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2015 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
-- Revision history.
--修订历史。
REVISION "201502020000Z" -- February 2, 2015
修订版“201502020000Z”-2015年2月2日
DESCRIPTION "MPLS TE MIB objects extension"
说明“MPLS TE MIB对象扩展”
::= { mplsStdMIB 20 }
::= { mplsStdMIB 20 }
-- Top-level components of this MIB module.
--此MIB模块的顶级组件。
-- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 0 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
-- tables, scalars
mplsTeExtObjects OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 0 }
-- conformance
mplsTeExtConformance OBJECT IDENTIFIER
::= { mplsTeExtStdMIB 1 }
-- Start of MPLS Transport Profile Node configuration table
--开始MPLS传输配置文件节点配置表
mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..16777215)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelExtNodeConfigLocalId, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelExtNodeConfigLocalId."
::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..16777215)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsTunnelExtNodeConfigLocalId, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelExtNodeConfigLocalId."
::= { mplsTeExtObjects 1 }
mplsTunnelExtNodeConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table allows the operator to map a node or LSR identifier (IP-compatible [Global_ID::Node_ID] or ICC-based [ICC_Operator_ID::Node_ID]) with a local identifier.
mplsTunnelExtNodeConfigTable对象类型MplsTunnelExtNodeConfigEntry MAX-ACCESS不可访问状态当前描述“此表允许操作员将节点或LSR标识符（IP兼容的[Global_ID:：node_ID]或基于ICC的[ICC_operator_ID:：node_ID]）映射到本地标识符。
This table is created to reuse the existing mplsTunnelTable for MPLS-based transport network tunnels also.
创建此表的目的是将现有的mplsTunnelTable重新用于基于MPLS的传输网络隧道。
Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for
MPLS-TP Tunnel, i.e., Global_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
with the local identifier of size 4 bytes (Unsigned32) value
in order to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for
MPLS-TP Tunnel, i.e., Global_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
with the local identifier of size 4 bytes (Unsigned32) value
in order to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable."
::= { mplsTeExtObjects 2 }
::= { mplsTeExtObjects 2 }
mplsTunnelExtNodeConfigEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping identification for the operator or service provider to a node or an LSR.
mplsTunnelExtNodeConfigEntry对象类型语法mplsTunnelExtNodeConfigEntry MAX-ACCESS not accessible STATUS current DESCRIPTION“此表中的条目表示操作员或服务提供商到节点或LSR的映射标识。
As per RFC 6370, IP-compatible mapping is represented as Global_ID::Node_ID.
根据RFC6370，IP兼容映射表示为全局_ID:：节点_ID。
As per RFC 6923, the CC and the ICC form the ICC_Operator_ID as CC::ICC, and ICC-compatible mapping is represented as ICC_Operator_ID::Node_ID.
根据RFC 6923，CC和ICC将ICC_运算符_ID表示为CC:：ICC，ICC兼容映射表示为ICC_运算符_ID:：节点_ID。
Note: Each entry in this table should have a unique
[Global_ID and Node_ID] or [CC::ICC and Node_ID] combination."
INDEX { mplsTunnelExtNodeConfigLocalId }
::= { mplsTunnelExtNodeConfigTable 1 }
Note: Each entry in this table should have a unique
[Global_ID and Node_ID] or [CC::ICC and Node_ID] combination."
INDEX { mplsTunnelExtNodeConfigLocalId }
::= { mplsTunnelExtNodeConfigTable 1 }
MplsTunnelExtNodeConfigEntry ::= SEQUENCE {
mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId,
mplsTunnelExtNodeConfigGlobalId MplsGlobalId,
mplsTunnelExtNodeConfigCcId MplsCcId,
mplsTunnelExtNodeConfigIccId MplsIccId,
mplsTunnelExtNodeConfigNodeId MplsNodeId,
mplsTunnelExtNodeConfigIccValid TruthValue,
mplsTunnelExtNodeConfigStorageType StorageType,
mplsTunnelExtNodeConfigRowStatus RowStatus
MplsTunnelExtNodeConfigEntry ::= SEQUENCE {
mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId,
mplsTunnelExtNodeConfigGlobalId MplsGlobalId,
mplsTunnelExtNodeConfigCcId MplsCcId,
mplsTunnelExtNodeConfigIccId MplsIccId,
mplsTunnelExtNodeConfigNodeId MplsNodeId,
mplsTunnelExtNodeConfigIccValid TruthValue,
mplsTunnelExtNodeConfigStorageType StorageType,
mplsTunnelExtNodeConfigRowStatus RowStatus
}
}
mplsTunnelExtNodeConfigLocalId OBJECT-TYPE SYNTAX MplsExtendedTunnelId MAX-ACCESS not-accessible STATUS current
mplsTunnelExtNodeConfigLocalId对象类型语法mplsextendedtunelid MAX-ACCESS不可访问状态当前
DESCRIPTION "This object is used in accommodating the bigger-size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID with the smaller-size LSR identifier in order to index the mplsTunnelTable.
DESCRIPTION“此对象用于容纳较大尺寸的全局_ID:：Node_ID和/或ICC_操作符_ID:：Node_ID和较小尺寸的LSR标识符，以便索引mplsTunnelTable。
The local identifier is configured between 0 and 16777215, as the valid IP address range starts from 16777216(01.00.00.00). This range is chosen to determine whether the mplsTunnelTable's Ingress/Egress LSR ID is an IP address or local identifier. If the configured range is not an IP address, the operator is expected to retrieve the complete information (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from mplsTunnelExtNodeConfigTable. This way, the existing mplsTunnelTable is reused for bidirectional tunnel extensions for MPLS-based transport networks.
本地标识符配置在0和16777215之间，因为有效IP地址范围从16777216（01.00.00.00）开始。选择此范围以确定mplsTunnelTable的入口/出口LSR ID是IP地址还是本地标识符。如果配置的范围不是IP地址，则操作员需要从mplsTunnelExtNodeConfigTable检索完整信息（全局\u ID:：节点\u ID或ICC\u操作员\u ID:：节点\u ID）。通过这种方式，现有的mplsTunnelTable被重新用于基于MPLS的传输网络的双向隧道扩展。
The local identifier allows the operator to assign
a unique identifier to map Global_ID::Node_ID and/or
ICC_Operator_ID::Node_ID. As this local identifier is unique
within the node and the same syntax of this object can be
used for MPLS-TE tunnel also, it is up to the operator/local
management entity to choose a non-conflicting value for
indexing the MPLS and MPLS-TP tunnel entries."
::= { mplsTunnelExtNodeConfigEntry 1 }
The local identifier allows the operator to assign
a unique identifier to map Global_ID::Node_ID and/or
ICC_Operator_ID::Node_ID. As this local identifier is unique
within the node and the same syntax of this object can be
used for MPLS-TE tunnel also, it is up to the operator/local
management entity to choose a non-conflicting value for
indexing the MPLS and MPLS-TP tunnel entries."
::= { mplsTunnelExtNodeConfigEntry 1 }
mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 3."
::= { mplsTunnelExtNodeConfigEntry 2 }
mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Global Operator Identifier.
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set true."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 3."
::= { mplsTunnelExtNodeConfigEntry 2 }
mplsTunnelExtNodeConfigCcId OBJECT-TYPE SYNTAX MplsCcId MAX-ACCESS read-create STATUS current
mplsTunnelExtNodeConfigCcId对象类型语法MplsCcId MAX-ACCESS读取创建状态当前
DESCRIPTION "This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress ID or Egress ID.
描述“此对象允许运营商或服务提供商为入口ID或出口ID配置唯一的MPLS-TP ITU-T国家代码（CC）。
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set to false."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsTunnelExtNodeConfigEntry 3 }
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set to false."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsTunnelExtNodeConfigEntry 3 }
mplsTunnelExtNodeConfigIccId OBJECT-TYPE SYNTAX MplsIccId MAX-ACCESS read-create 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.
mplsTunnelExtNodeConfigIccId对象类型语法MplsIccId MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许运营商或服务提供商为入口ID或出口ID配置唯一的MPLS-TP ITU-T载波代码（ICC）。
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set to false."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsTunnelExtNodeConfigEntry 4 }
This object has no meaning when
mplsTunnelExtNodeConfigIccValid is set to false."
REFERENCE
"MPLS-TP Identifiers Following ITU-T Conventions,
RFC 6923, Section 3"
::= { mplsTunnelExtNodeConfigEntry 4 }
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the scope
of a Global_ID or ICC_Operator_ID."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 4."
::= { mplsTunnelExtNodeConfigEntry 5 }
mplsTunnelExtNodeConfigNodeId OBJECT-TYPE
SYNTAX MplsNodeId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the Node_ID within the scope
of a Global_ID or ICC_Operator_ID."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370,
Section 4."
::= { mplsTunnelExtNodeConfigEntry 5 }
mplsTunnelExtNodeConfigIccValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this entry uses mplsTunnelExtNodeConfigCcId, mplsTunnelExtNodeConfigIccId, and
mplsTunnelExtNodeConfigIccValid对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION”表示此条目是否使用mplsTunnelExtNodeConfigCcId、mplsTunnelExtNodeConfigIccId和
mplsTunnelExtNodeConfigNodeId for mapping
the ICC-based identifiers with the local identifier.
Note that if this variable is set to false, then the
mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId objects should have
the valid information."
DEFVAL { false }
::= { mplsTunnelExtNodeConfigEntry 6 }
mplsTunnelExtNodeConfigNodeId for mapping
the ICC-based identifiers with the local identifier.
Note that if this variable is set to false, then the
mplsTunnelExtNodeConfigGlobalId and
mplsTunnelExtNodeConfigNodeId objects should have
the valid information."
DEFVAL { false }
::= { mplsTunnelExtNodeConfigEntry 6 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
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 }
::= { mplsTunnelExtNodeConfigEntry 7 }
mplsTunnelExtNodeConfigStorageType OBJECT-TYPE
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 }
::= { mplsTunnelExtNodeConfigEntry 7 }
mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the operator to create, modify,
and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 8 }
mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows the operator to create, modify,
and/or delete a row in this table."
::= { mplsTunnelExtNodeConfigEntry 8 }
-- End of MPLS Transport Profile Node configuration table
--结束MPLS传输配置文件节点配置表
-- Start of MPLS Transport Profile Node IP-compatible
-- mapping table
-- Start of MPLS Transport Profile Node IP-compatible
-- mapping table
mplsTunnelExtNodeIpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry
MplsTunnelExtNodeIpMapEntry的mplsTunnelExtNodeIpMapTable对象类型语法序列
MAX-ACCESS not-accessible STATUS current DESCRIPTION "This read-only table allows the operator to retrieve the local identifier for a given Global_ID::Node_ID in an IP-compatible operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier
MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此只读表允许操作员在IP兼容的操作员环境中检索给定全局\u ID:：节点\u ID的本地标识符。此表可用于按需和/或主动OAM操作，以获取入口/出口LSR标识符
(local identifier) from Src-Global_Node_ID or Dst-Global_Node_ID. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry.
（本地标识符）来自Src-Global_Node_ID或Dst-Global_Node_ID。入口和出口LSR标识符用于检索隧道入口。
This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 3 }
This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 3 }
mplsTunnelExtNodeIpMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping of Global_ID::Node_ID with the local identifier.
mplsTunnelExtNodeIpMapEntry对象类型语法mplsTunnelExtNodeIpMapEntry MAX-ACCESS不可访问状态当前描述“此表中的一个条目表示全局_ID:：节点_ID与本地标识符的映射。
An entry in this table is created automatically when the local identifier is associated with Global_ID and Node_Id in the mplsTunnelExtNodeConfigTable.
当本地标识符与mplsTunnelExtNodeConfigTable中的全局_ID和节点_ID关联时，将自动创建此表中的条目。
Note: Each entry in this table should have a unique
Global_ID and Node_ID combination."
INDEX { mplsTunnelExtNodeIpMapGlobalId,
mplsTunnelExtNodeIpMapNodeId
}
::= { mplsTunnelExtNodeIpMapTable 1 }
Note: Each entry in this table should have a unique
Global_ID and Node_ID combination."
INDEX { mplsTunnelExtNodeIpMapGlobalId,
mplsTunnelExtNodeIpMapNodeId
}
::= { mplsTunnelExtNodeIpMapTable 1 }
MplsTunnelExtNodeIpMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIpMapGlobalId MplsGlobalId,
mplsTunnelExtNodeIpMapNodeId MplsNodeId,
mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId
}
MplsTunnelExtNodeIpMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIpMapGlobalId MplsGlobalId,
mplsTunnelExtNodeIpMapNodeId MplsNodeId,
mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Global_ID."
::= { mplsTunnelExtNodeIpMapEntry 1 }
mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE
SYNTAX MplsGlobalId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the Global_ID."
::= { mplsTunnelExtNodeIpMapEntry 1 }
mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS not-accessible STATUS current
mplstunnelextnodeipmpnodeid对象类型语法MplsNodeId MAX-ACCESS不可访问状态当前
DESCRIPTION
"This object indicates the Node_ID within the
operator."
::= { mplsTunnelExtNodeIpMapEntry 2 }
DESCRIPTION
"This object indicates the Node_ID within the
operator."
::= { mplsTunnelExtNodeIpMapEntry 2 }
mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an IP-compatible local identifier
that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIpMapEntry 3 }
mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an IP-compatible local identifier
that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIpMapEntry 3 }
-- End MPLS Transport Profile Node IP compatible table
--结束MPLS传输配置文件节点IP兼容表
-- Start of MPLS Transport Profile Node ICC based table
--开始MPLS传输配置文件节点基于ICC的表
mplsTunnelExtNodeIccMapTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This read-only table allows the operator to retrieve the local identifier for a given ICC_Operator_ID::Node_ID in an ICC operator environment.
mplstunnelextnodeiccmaperty的MplsTunnelExtNodeIccMapEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此只读表允许操作员在ICC操作员环境中检索给定ICC_操作员_ID:：Node_ID的本地标识符。
This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR
identifier (local identifier) from Src-ICC
or Dst-ICC. The Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 4 }
This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR
identifier (local identifier) from Src-ICC
or Dst-ICC. The Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry
is not defined in mplsTunnelExtNodeConfigTable."
::= { mplsTeExtObjects 4 }
mplsTunnelExtNodeIccMapEntry OBJECT-TYPE SYNTAX MplsTunnelExtNodeIccMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a mapping of ICC_Operator_ID::Node_ID with the local identifier.
mplsTunnelExtNodeIccMapEntry对象类型语法mplsTunnelExtNodeIccMapEntry MAX-ACCESS not accessible STATUS current DESCRIPTION“此表中的一个条目表示ICC_Operator_ID:：Node_ID与本地标识符的映射。
An entry in this table is created automatically when the local identifier is associated with ICC_Operator_ID::Node_ID in the mplsTunnelExtNodeConfigTable."
当本地标识符与mplsTunnelExtNodeConfigTable中的ICC_Operator_ID:：Node_ID关联时，将自动创建此表中的条目。”
INDEX { mplsTunnelExtNodeIccMapCcId,
mplsTunnelExtNodeIccMapIccId,
mplsTunnelExtNodeIccMapNodeId }
::= { mplsTunnelExtNodeIccMapTable 1 }
INDEX { mplsTunnelExtNodeIccMapCcId,
mplsTunnelExtNodeIccMapIccId,
mplsTunnelExtNodeIccMapNodeId }
::= { mplsTunnelExtNodeIccMapTable 1 }
MplsTunnelExtNodeIccMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIccMapCcId MplsCcId,
mplsTunnelExtNodeIccMapIccId MplsIccId,
mplsTunnelExtNodeIccMapNodeId MplsNodeId,
mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
}
MplsTunnelExtNodeIccMapEntry ::= SEQUENCE {
mplsTunnelExtNodeIccMapCcId MplsCcId,
mplsTunnelExtNodeIccMapIccId MplsIccId,
mplsTunnelExtNodeIccMapNodeId MplsNodeId,
mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId
}
mplsTunnelExtNodeIccMapCcId OBJECT-TYPE SYNTAX MplsCcId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress or Egress LSR ID.
mplstunnelextnodeiccmapcid对象类型语法MplsCcId MAX-ACCESS not accessible STATUS current DESCRIPTION“此对象允许运营商或服务提供商为入口或出口LSR ID配置唯一的MPLS-TP ITU-T国家代码（CC）。
The CC is a string of two alphabetic characters
represented with uppercase letters (i.e., A-Z)."
::= { mplsTunnelExtNodeIccMapEntry 1 }
The CC is a string of two alphabetic characters
represented with uppercase letters (i.e., A-Z)."
::= { mplsTunnelExtNodeIccMapEntry 1 }
mplsTunnelExtNodeIccMapIccId 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.
mplsTunnelExtNodeIccMapIccId对象类型语法MplsIccId MAX-ACCESS not accessible STATUS current DESCRIPTION“此对象允许运营商或服务提供商为入口或出口LSR ID配置唯一的MPLS-TP ITU-T载波代码（ICC）。
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 uppercase
letters."
::= { mplsTunnelExtNodeIccMapEntry 2 }
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 uppercase
letters."
::= { mplsTunnelExtNodeIccMapEntry 2 }
mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE SYNTAX MplsNodeId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object indicates the Node_ID within the ICC-based operator."
mplsTunnelExtNodeIccMapNodeId对象类型语法MplsNodeId MAX-ACCESS不可访问状态当前描述“此对象表示基于ICC的运算符内的节点ID。”
::= { mplsTunnelExtNodeIccMapEntry 3}
::= { mplsTunnelExtNodeIccMapEntry 3}
mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an ICC-based local identifier
that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapEntry 4 }
mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE
SYNTAX MplsExtendedTunnelId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an ICC-based local identifier
that is defined in mplsTunnelExtNodeConfigTable."
::= { mplsTunnelExtNodeIccMapEntry 4 }
-- End MPLS Transport Profile Node ICC-based table
--端MPLS传输配置文件节点基于ICC的表
-- Start of MPLS Tunnel table extension
--开始MPLS隧道表扩展
mplsTunnelExtTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents extensions to mplsTunnelTable in order to support MPLS-TP Tunnels.
MPLStunnelextable对象类型语法MPLStunnelextery MAX-ACCESS不可访问状态当前描述“此表表示对mplsTunnelTable的扩展，以支持MPLS-TP隧道。
As per MPLS-TP Identifiers (RFC 6370), LSP_ID for IP-based co-routed bidirectional tunnel:
根据MPLS-TP标识符（RFC 6370），基于IP的共路由双向隧道的LSP_ID：
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num
LSP_ID for IP based associated bidirectional tunnel:
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
LSP_ID for IP based associated bidirectional tunnel:
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
mplsTunnelTable is reused for forming the LSP_ID as follows:
mplsTunnelTable被重新用于形成LSP_ID，如下所示：
Source Tunnel_Num is mapped with mplsTunnelIndex, Source Node_ID is mapped with mplsTunnelIngressLSRId, Destination Node_ID is mapped with mplsTunnelEgressLSRId, and LSP_Num is mapped with mplsTunnelInstance.
源隧道_Num与mplsTunnelIndex映射，源节点_ID与MPLStunneLingResslId映射，目标节点_ID与MPLStunneleResslId映射，LSP_Num与MPLStunneLinInstance映射。
Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
are maintained in the mplsTunnelExtNodeConfigTable.
mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable."
Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
are maintained in the mplsTunnelExtNodeConfigTable.
mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable."
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370."
::= { mplsTeExtObjects 5 }
REFERENCE
"MPLS Transport Profile (MPLS-TP) Identifiers, RFC 6370."
::= { mplsTeExtObjects 5 }
mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents additional MPLS-TP-
specific tunnel configurations."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
mplsTunnelExtEntry OBJECT-TYPE
SYNTAX MplsTunnelExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents additional MPLS-TP-
specific tunnel configurations."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { mplsTunnelExtTable 1 }
MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelExtOppositeDirPtr RowPointer,
mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue,
mplsTunnelExtIngressLSRLocalIdValid TruthValue,
mplsTunnelExtEgressLSRLocalIdValid TruthValue
}
MplsTunnelExtEntry ::= SEQUENCE {
mplsTunnelExtOppositeDirPtr RowPointer,
mplsTunnelExtOppositeDirTnlValid TruthValue,
mplsTunnelExtDestTnlIndex MplsTunnelIndex,
mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex,
mplsTunnelExtDestTnlValid TruthValue,
mplsTunnelExtIngressLSRLocalIdValid TruthValue,
mplsTunnelExtEgressLSRLocalIdValid TruthValue
}
mplsTunnelExtOppositeDirPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object points to the opposite-direction tunnel entry."
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtOppositeDirPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object points to the opposite-direction tunnel entry."
::= { mplsTunnelExtEntry 1 }
mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel uses mplsTunnelExtOppositeDirPtr for identifying the opposite-direction tunnel information. Note that if this variable is set to true, then the mplsTunnelExtOppositeDirPtr should point to the first accessible row of the valid opposite-direction tunnel."
mplsTunnelExtOppositeDirTnlValid对象类型语法TruthValue MAX-ACCESS读取创建状态当前说明“表示此隧道是否使用mplsTunnelExtOppositeDirPtr来标识反向隧道信息。请注意，如果此变量设置为true，则mplsTunnelExtOppositeDirPtr应指向有效反向隧道的第一个可访问行。”
DEFVAL { false }
::= { mplsTunnelExtEntry 2 }
DEFVAL { false }
::= { mplsTunnelExtEntry 2 }
mplsTunnelExtDestTnlIndex OBJECT-TYPE SYNTAX MplsTunnelIndex MAX-ACCESS read-create STATUS current DESCRIPTION "This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries.
mplsTunnelExtDestTnlIndex对象类型语法MplsTunnelIndex MAX-ACCESS read create STATUS current DESCRIPTION“此对象仅适用于在不同隧道条目中具有正向和反向LSP的双向隧道。
The values of this object and the mplsTunnelExtDestTnlLspIndex object together can be used to identify an opposite-direction LSP, i.e., if the mplsTunnelIndex and mplsTunnelInstance hold the value for forward LSP, this object and mplsTunnelExtDestTnlLspIndex can be used to retrieve the reverse-direction LSP and vice versa.
此对象和mplsTunnelExtDestTnlLspIndex对象的值一起可用于标识反向LSP，即，如果mplsTunnelIndex和MPlstunneLinInstance保持正向LSP的值，则此对象和mplsTunnelExtDestTnlLspIndex可用于检索反向LSP，反之亦然。
This object and mplsTunnelExtDestTnlLspIndex values
provide the first two indices of tunnel entry, and
the remaining indices can be derived as follows:
the Ingress and Egress Identifiers should be
swapped in order to index the other direction tunnel."
::= { mplsTunnelExtEntry 3 }
This object and mplsTunnelExtDestTnlLspIndex values
provide the first two indices of tunnel entry, and
the remaining indices can be derived as follows:
the Ingress and Egress Identifiers should be
swapped in order to index the other direction tunnel."
::= { mplsTunnelExtEntry 3 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE
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
different tunnel entries. This object holds
the instance index of the opposite-direction tunnel."
::= { mplsTunnelExtEntry 4 }
mplsTunnelExtDestTnlLspIndex OBJECT-TYPE
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
different tunnel entries. This object holds
the instance index of the opposite-direction tunnel."
::= { mplsTunnelExtEntry 4 }
mplsTunnelExtDestTnlValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel uses mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex for identifying the opposite-direction tunnel information. Note that if this variable is set to true, then the
mplsTunnelExtDestTnlValid对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION”表示此隧道是否使用mplsTunnelExtDestTnlIndex和mplstunnelextdesttnlspindex来标识反向隧道信息。请注意，如果此变量设置为true，则
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite-direction tunnel indices."
DEFVAL { false }
::= { mplsTunnelExtEntry 5 }
mplsTunnelExtDestTnlIndex and
mplsTunnelExtDestTnlLspIndex objects should have
the valid opposite-direction tunnel indices."
DEFVAL { false }
::= { mplsTunnelExtEntry 5 }
mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object denotes whether the mplsTunnelIngressLSRId contains the local value that is used to reference the complete Ingress Global_ID::Node_ID or ICC_Operator_ID from the mplsTunnelExtNodeConfigTable.
mplstunnelextingresslocalidavid对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION“此对象表示mplstunnelingresslrid是否包含用于从mplsTunnelExtNodeConfigTable引用完整入口全局\u ID:：Node\u ID或ICC\u Operator\u ID的本地值。
If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
如果此对象设置为FALSE，则mplsTunnelExtNodeConfigTable将不包含引用具有全局\u ID:：Node\u ID或ICC\u运算符\u ID:：Node\u ID值的本地标识符的条目。
This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelIngressId itself provides
the complete Ingress LSR ID."
REFERENCE
"MPLS-TE-STD-MIB (RFC 3812), Section 11.
mplsTunnelIngressLSRId object in mplsTunnelTable."
DEFVAL { false }
::= { mplsTunnelExtEntry 6 }
This object is set to FALSE for legacy implementations like
MPLS TE tunnels where mplsTunnelIngressId itself provides
the complete Ingress LSR ID."
REFERENCE
"MPLS-TE-STD-MIB (RFC 3812), Section 11.
mplsTunnelIngressLSRId object in mplsTunnelTable."
DEFVAL { false }
::= { mplsTunnelExtEntry 6 }
mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This object denotes whether the mplsTunnelEgressLSRId contains the local value, which is used to reference the complete Egress Global_ID::Node_ID or ICC_Operator_ID::Node_ID from the mplsTunnelExtNodeConfigTable.
mplstunnelextegresslsrlocalidavid对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION“此对象表示mplstunnelegressrid是否包含本地值，该本地值用于从mplsTunnelExtNodeConfigTable引用完整的出口全局_ID:：Node_ID或ICC_操作符_ID:：Node_ID。
If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value.
如果此对象设置为FALSE，则mplsTunnelExtNodeConfigTable将不包含引用具有全局\u ID:：Node\u ID或ICC\u运算符\u ID:：Node\u ID值的本地标识符的条目。
This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelEgressId itself provides the complete Egress LSR ID."
对于传统实现（如MPLS TE隧道），此对象设置为FALSE，其中MPLStunnelePressed本身提供完整的出口LSR ID。”
REFERENCE
"MPLS-TE-STD-MIB (RFC 3812), Section 11.
mplsTunnelEgressLSRId object in mplsTunnelTable."
DEFVAL { false }
::= { mplsTunnelExtEntry 7 }
REFERENCE
"MPLS-TE-STD-MIB (RFC 3812), Section 11.
mplsTunnelEgressLSRId object in mplsTunnelTable."
DEFVAL { false }
::= { mplsTunnelExtEntry 7 }
-- End of MPLS Tunnel table extension
--MPLS隧道表扩展结束
-- Module compliance.
--模块合规性。
mplsTeExtCompliances
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
mplsTeExtCompliances
OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 }
mplsTeExtGroups
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
mplsTeExtGroups
OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 }
-- Compliance requirement for fully compliant implementations.
--完全合规实施的合规性要求。
mplsTeExtModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support the MPLS-TE-EXT-STD-MIB module."
MPLSTEXTMODULIELLCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“提供完全支持MPLS-TE-EXT-STD-MIB模块的代理的符合性声明。”
MODULE -- this module
模块——这个模块
-- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP Tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
-- The mandatory group has to be implemented by all
-- LSRs that originate/terminate MPLS-TP Tunnels.
-- In addition, depending on the type of tunnels
-- supported, other groups become mandatory as
-- explained below.
MANDATORY-GROUPS {
mplsTunnelExtGroup
}
MANDATORY-GROUPS {
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup DESCRIPTION "This group is mandatory for devices that support configuration of IP-based identifier tunnels."
组mplsTunnelExtIpOperatorGroup DESCRIPTION“此组对于支持基于IP的标识符隧道配置的设备是必需的。”
GROUP mplsTunnelExtIccOperatorGroup DESCRIPTION "This group is mandatory for devices that support configuration of ICC based tunnels."
组mplsTunnelExtIccOperatorGroup DESCRIPTION“此组对于支持基于ICC的隧道配置的设备是必需的。”
::= { mplsTeExtCompliances 1 }
::= { mplsTeExtCompliances 1 }
-- Compliance requirement for read-only implementations.
--只读实现的法规遵从性要求。
mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that only provide read-only support for the MPLS-TE-EXT-STD-MIB module."
MPLSTEXTModuleRadonlyCompliance MODULE-COMPLIANCE状态当前描述“仅为MPLS-TE-EXT-STD-MIB模块提供只读支持的代理的符合性声明。”
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
mplsTunnelExtGroup
}
MANDATORY-GROUPS {
mplsTunnelExtGroup
}
GROUP mplsTunnelExtIpOperatorGroup DESCRIPTION "This group is mandatory for devices that support configuration of IP-based identifier tunnels."
组mplsTunnelExtIpOperatorGroup DESCRIPTION“此组对于支持基于IP的标识符隧道配置的设备是必需的。”
GROUP mplsTunnelExtIccOperatorGroup DESCRIPTION "This group is mandatory for devices that support configuration of ICC-based tunnels."
组mplsTunnelExtIccOperatorGroup DESCRIPTION“此组对于支持基于ICC的隧道配置的设备是必需的。”
-- mplsTunnelExtTable
--mplsTunnelExtTable
OBJECT mplsTunnelExtOppositeDirPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplstunnelextoppositedrptr MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtOppositeDirTnlValid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtOppositeDirTnlValid最小访问只读描述“不需要写访问。”
OBJECT mplsTunnelExtDestTnlIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtDestTnlIndex MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtDestTnlLspIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtDestTnlLspIndex MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtDestTnlValid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtDestTnlValid MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtIngressLSRLocalIdValid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLStunneLextingResslLocalidValid最小访问只读描述“不需要写访问。”
OBJECT mplsTunnelExtEgressLSRLocalIdValid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplstunnelextegresslsrlocalidavalid MIN-ACCESS只读描述“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigGlobalId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigGlobalId最小访问只读说明“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigNodeId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigNodeId MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigStorageType最小访问只读说明“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigRowStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigCcId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigCcId MIN-ACCESS只读描述“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigIccId MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigIccId MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsTunnelExtNodeConfigIccValid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsTunnelExtNodeConfigIccValid MIN-ACCESS只读说明“不需要写访问。”
::= { mplsTeExtCompliances 2 }
::= { mplsTeExtCompliances 2 }
-- Units of conformance.
--一致性单位。
mplsTunnelExtGroup OBJECT-GROUP
OBJECTS {
mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid,
mplsTunnelExtIngressLSRLocalIdValid,
mplsTunnelExtEgressLSRLocalIdValid
}
mplsTunnelExtGroup OBJECT-GROUP
OBJECTS {
mplsTunnelExtOppositeDirPtr,
mplsTunnelExtOppositeDirTnlValid,
mplsTunnelExtDestTnlIndex,
mplsTunnelExtDestTnlLspIndex,
mplsTunnelExtDestTnlValid,
mplsTunnelExtIngressLSRLocalIdValid,
mplsTunnelExtEgressLSRLocalIdValid
}
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 }
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 { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigGlobalId,
mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP-compatible tunnels."
::= { mplsTeExtGroups 2 }
mplsTunnelExtIpOperatorGroup OBJECT-GROUP
OBJECTS { mplsTunnelExtNodeConfigLocalIdNext,
mplsTunnelExtNodeConfigGlobalId,
mplsTunnelExtNodeConfigNodeId,
mplsTunnelExtNodeIpMapLocalId,
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement IP-compatible tunnels."
::= { mplsTeExtGroups 2 }
mplsTunnelExtIccOperatorGroup OBJECT-GROUP OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, mplsTunnelExtNodeConfigCcId, mplsTunnelExtNodeConfigIccId, mplsTunnelExtNodeConfigNodeId, mplsTunnelExtNodeConfigIccValid, mplsTunnelExtNodeIccMapLocalId,
mplstunnelextNicorGroup对象组对象{mplsTunnelExtNodeConfigLocalIdNext，mplsTunnelExtNodeConfigCcId，mplsTunnelExtNodeConfigIccId，mplsTunnelExtNodeConfigNodeId，mplsTunnelExtNodeConfigIccValid，mplstunnelextNodeICPlopolid，
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC-based tunnels."
::= { mplsTeExtGroups 3 }
mplsTunnelExtNodeConfigStorageType,
mplsTunnelExtNodeConfigRowStatus
}
STATUS current
DESCRIPTION
"Object(s) needed to implement ICC-based tunnels."
::= { mplsTeExtGroups 3 }
-- MPLS-TE-EXT-STD-MIB module ends END
--MPLS-TE-EXT-STD-MIB模块结束
This document follows the security considerations mentioned in Section 12 of [RFC3812]. These security considerations are also applicable to the MIB objects and tables defined in this document, which are identified as below.
本文件遵循[RFC3812]第12节中提到的安全注意事项。这些安全注意事项也适用于本文档中定义的MIB对象和表，如下所示。
- The common objects mplsIdGlobalId, mplsIdNodeId, mplsIdCc, and mplsIdIcc are used to define the identity of an MPLS-TP node for OAM purposes. If write-access is allowed to these objects it offers the possibility for incorrect values to be entered that will confuse the information returned by OAM functions and possibly prevent OAM from operating correctly. Furthermore, there is the possibility of inducing one node to impersonate another with confusing results.
- 公共对象mplsIdGlobalId、mplsIdNodeId、mplsIdCc和mplsIdIcc用于定义用于OAM的MPLS-TP节点的标识。如果允许对这些对象进行写访问，则可能会输入不正确的值，这将混淆OAM函数返回的信息，并可能阻止OAM正常运行。此外，还可能导致一个节点模仿另一个节点，从而产生混乱的结果。
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and mplsXCExtTable collectively contain objects to provision MPLS-TP Tunnels, tunnel hops, and tunnel resources.
- mplsTunnelExtNodeConfigTable、mplsTunnelExtTable和mplsXCExtTable共同包含用于提供MPLS-TP隧道、隧道跃点和隧道资源的对象。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
- mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, and mplsXCExtTable collectively show the characteristics of the MPLS-TP tunnel network topology. If an Administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable.
- mplsTunnelExtNodeConfigTable、mplsTunnelExtTable和mplsXCExtTable共同显示了MPLS-TP隧道网络拓扑的特征。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），也无法控制安全网络上的用户
access and GET/SET (read/change/create/delete) the objects in this MIB module.
访问并获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
As described in [RFC4221] and [RFC6639], and as requested in the MPLS-TC-STD-MIB [RFC3811], MPLS-related Standards Track MIB modules should be rooted under the mplsStdMIB subtree. There are four MPLS MIB modules contained in this document; each of the following subsections lists a new assignment made by IANA under the mplsStdMIB subtree. New assignments can only be made via a Standards Action as specified in [RFC5226].
如[RFC4221]和[RFC6639]所述，以及MPLS-TC-STD-MIB[RFC3811]中的要求，MPLS相关标准跟踪MIB模块应在mplsStdMIB子树下扎根。本文件包含四个MPLS MIB模块；以下各小节列出了IANA在MPLSTDMIB子树下进行的新分配。新分配只能通过[RFC5226]中规定的标准操作进行。
IANA has assigned the OID { mplsStdMIB 17 } to the MPLS-TC-EXT-STD-MIB module specified in this document.
IANA已将OID{mplsStdMIB 17}分配给本文档中指定的MPLS-TC-EXT-STD-MIB模块。
IANA has assigned the OID { mplsStdMIB 18 } to the MPLS-ID-STD-MIB module specified in this document.
IANA已将OID{mplsStdMIB 18}分配给本文档中指定的MPLS-ID-STD-MIB模块。
IANA has assigned the OID { mplsStdMIB 19 } to the MPLS-LSR-EXT-STD-MIB module specified in this document.
IANA已将OID{MPLSTDMIB 19}分配给本文档中指定的MPLS-LSR-EXT-STD-MIB模块。
IANA has assigned the OID { mplsStdMIB 20 } to the MPLS-TE-EXT-STD-MIB module specified in this document.
IANA已将OID{mplsStdMIB 20}分配给本文档中指定的MPLS-TE-EXT-STD-MIB模块。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999, <http://www.rfc-editor.org/info/rfc2578>.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月<http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999, <http://www.rfc-editor.org/info/rfc2579>.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 25801999年4月<http://www.rfc-editor.org/info/rfc2580>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001, <http://www.rfc-editor.org/info/rfc3031>.
[RFC3031]Rosen，E.，Viswanathan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月<http://www.rfc-editor.org/info/rfc3031>.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002, <http://www.rfc-editor.org/info/rfc3289>.
[RFC3289]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月<http://www.rfc-editor.org/info/rfc3289>.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004, <http://www.rfc-editor.org/info/rfc3811>.
[RFC3811]Nadeau，T.，Ed.，和J.Cucchiara，Ed.，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，2004年6月<http://www.rfc-editor.org/info/rfc3811>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004, <http://www.rfc-editor.org/info/rfc3812>.
[RFC3812]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”，RFC 3812，2004年6月<http://www.rfc-editor.org/info/rfc3812>.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004, <http://www.rfc-editor.org/info/rfc3813>.
[RFC3813]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 38132004年6月<http://www.rfc-editor.org/info/rfc3813>.
[RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", RFC 4802, February 2007, <http://www.rfc-editor.org/info/rfc4802>.
[RFC4802]Nadeau，T.，Ed.，和A.Farrel，Ed.，“通用多协议标签交换（GMPLS）流量工程管理信息库”，RFC 48022007年2月<http://www.rfc-editor.org/info/rfc4802>.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile (MPLS-TP) Identifiers", RFC 6370, September 2011, <http://www.rfc-editor.org/info/rfc6370>.
[RFC6370]Bocci，M.，Swallow，G.和E.Gray，“MPLS传输配置文件（MPLS-TP）标识符”，RFC 63702011年9月<http://www.rfc-editor.org/info/rfc6370>.
[RFC6923] Winter, R., Gray, E., van Helvoort, H., and M. Betts, "MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions", RFC 6923, May 2013, <http://www.rfc-editor.org/info/rfc6923>.
[RFC6923]Winter，R.，Gray，E.，van Helvoort，H.，和M.Betts，“遵循ITU-T公约的MPLS传输配置文件（MPLS-TP）标识符”，RFC 69232013年5月<http://www.rfc-editor.org/info/rfc6923>.
[T.50] ITU-T, "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information exchange", ITU-T Recommendation T.50, September 1992.
[T.50]ITU-T，“国际参考字母表（IRA）（原国际字母表5或IA5）-信息技术-用于信息交换的7位编码字符集”，ITU-T建议T.50，1992年9月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002, <http://www.rfc-editor.org/info/rfc3410>.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月<http://www.rfc-editor.org/info/rfc3410>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002, <http://www.rfc-editor.org/info/rfc3414>.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, June 2004, <http://www.rfc-editor.org/info/rfc3826>.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，2004年6月<http://www.rfc-editor.org/info/rfc3826>.
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol Label Switching (MPLS) Management Overview", RFC 4221, November 2005, <http://www.rfc-editor.org/info/rfc4221>.
[RFC4221]Nadeau，T.，Srinivasan，C.，和A.Farrel，“多协议标签交换（MPLS）管理概述”，RFC 42212005年11月<http://www.rfc-editor.org/info/rfc4221>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, June 2009, <http://www.rfc-editor.org/info/rfc5591>.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，STD 78，RFC 5591，2009年6月<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 55922009年6月<http://www.rfc-editor.org/info/rfc5592>.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009, <http://www.rfc-editor.org/info/rfc5654>.
[RFC5654]Niven Jenkins，B.，Ed.，Brungard，D.，Ed.，Betts，M.，Ed.，Sprecher，N.，和S.Ueno，“MPLS传输配置文件的要求”，RFC 56542009年9月<http://www.rfc-editor.org/info/rfc5654>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, July 2011, <http://www.rfc-editor.org/info/rfc6353>.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，STD 78，RFC 63532011年7月<http://www.rfc-editor.org/info/rfc6353>.
[RFC6639] King, D., Ed., and M. Venkatesan, Ed., "Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview", RFC 6639, June 2012, <http://www.rfc-editor.org/info/rfc6639>.
[RFC6639]King，D.，Ed.，和M.Venkatesan，Ed.，“基于MIB的多协议标签交换传输配置文件（MPLS-TP）管理概述”，RFC 66392012年6月<http://www.rfc-editor.org/info/rfc6639>.
Acknowledgments
致谢
The authors would like to thank Francesco Fondelli, Josh Littlefield, Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn, Elwyn Davies, Tom Taylor, and Pete Resnick for their valuable reviews and comments. A special thanks to Joan Cucchiara and Adrian Farrel for really getting the MIB modules into shape.
作者要感谢Francesco Fondelli、Josh Littlefield、Agrahara Kiran Koushik、Metrri Jain、Muly Ilan、Randy Presohn、Elwyn Davies、Tom Taylor和Pete Resnick的宝贵评论和评论。特别感谢Joan Cucchiara和Adrian Farrel使MIB模块真正成形。
Authors' Addresses
作者地址
Venkatesan Mahalingam Dell Inc. 5450 Great America Parkway, Santa Clara, CA 95054 United States EMail: venkat.mahalingams@gmail.com
Venkatesan Mahalingam Dell Inc.美国加利福尼亚州圣克拉拉大美洲大道5450号，邮编95054电子邮件：venkat。mahalingams@gmail.com
Sam Aldrin Huawei Technologies 2330 Central Express Way, Santa Clara, CA 95051 United States EMail: aldrin.ietf@gmail.com
Sam Aldrin华为技术公司加利福尼亚州圣克拉拉中央快速路2330号，邮编95051美国电子邮件：Aldrin。ietf@gmail.com
Thomas D. Nadeau Brocade EMail: tnadeau@lucidvision.com
Thomas D.Nadeau Brocade电子邮件：tnadeau@lucidvision.com
Kannan KV Sampath Redeem India EMail: kannankvs@gmail.com
Kannan KV Sampath兑换印度电子邮件：kannankvs@gmail.com