Network Working Group T. Nadeau, Ed.
Request for Comment: 4802 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Network Working Group T. Nadeau, Ed.
Request for Comment: 4802 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base
通用多协议标签交换（GMPLS）流量工程管理信息库
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
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 managed objects for Generalized Multiprotocol Label Switching (GMPLS)-based traffic engineering.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了基于通用多协议标签交换（GMPLS）的流量工程的托管对象。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Migration Strategy .........................................3
2. Terminology .....................................................3
3. The Internet-Standard Management Framework ......................4
4. Outline .........................................................4
4.1. Summary of GMPLS Traffic Engineering MIB Module ............4
5. Brief Description of GMPLS TE MIB Objects .......................5
5.1. gmplsTunnelTable ...........................................5
5.2. gmplsTunnelHopTable ........................................6
5.3. gmplsTunnelARHopTable ......................................6
5.4. gmplsTunnelCHopTable .......................................6
5.5. gmplsTunnelErrorTable ......................................6
5.6. gmplsTunnelReversePerfTable ................................6
5.7. Use of 32-bit and 64-bit Counters ..........................7
6. Cross-referencing to the gmplsLabelTable ........................7
7. Example of GMPLS Tunnel Setup ...................................8
8. GMPLS Traffic Engineering MIB Module ...........................11
9. Security Considerations ........................................47
10. Acknowledgments ...............................................48
11. IANA Considerations ...........................................49
11.1. IANA Considerations for GMPLS-TE-STD-MIB .................49
11.2. Dependence on IANA MIB Modules ...........................49
11.2.1. IANA-GMPLS-TC-MIB Definition ......................50
12. References ....................................................56
12.1. Normative References .....................................56
12.2. Informative References ...................................58
1. Introduction ....................................................2
1.1. Migration Strategy .........................................3
2. Terminology .....................................................3
3. The Internet-Standard Management Framework ......................4
4. Outline .........................................................4
4.1. Summary of GMPLS Traffic Engineering MIB Module ............4
5. Brief Description of GMPLS TE MIB Objects .......................5
5.1. gmplsTunnelTable ...........................................5
5.2. gmplsTunnelHopTable ........................................6
5.3. gmplsTunnelARHopTable ......................................6
5.4. gmplsTunnelCHopTable .......................................6
5.5. gmplsTunnelErrorTable ......................................6
5.6. gmplsTunnelReversePerfTable ................................6
5.7. Use of 32-bit and 64-bit Counters ..........................7
6. Cross-referencing to the gmplsLabelTable ........................7
7. Example of GMPLS Tunnel Setup ...................................8
8. GMPLS Traffic Engineering MIB Module ...........................11
9. Security Considerations ........................................47
10. Acknowledgments ...............................................48
11. IANA Considerations ...........................................49
11.1. IANA Considerations for GMPLS-TE-STD-MIB .................49
11.2. Dependence on IANA MIB Modules ...........................49
11.2.1. IANA-GMPLS-TC-MIB Definition ......................50
12. References ....................................................56
12.1. Normative References .....................................56
12.2. Informative References ...................................58
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 managed objects for modeling Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based traffic engineering (TE). The tables and objects defined in this document extend those defined in the equivalent document for MPLS traffic engineering [RFC3812], and management of GMPLS traffic engineering is built on management of MPLS traffic engineering.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于建模基于通用多协议标签交换（GMPLS）[RFC3945]的流量工程（TE）的托管对象。本文档中定义的表和对象扩展了MPLS流量工程等效文档[RFC3812]中定义的表和对象，GMPLS流量工程的管理建立在MPLS流量工程的管理之上。
The MIB modules in this document should be used in conjunction with the companion document [RFC4803] for GMPLS-based traffic engineering configuration and management.
本文件中的MIB模块应与配套文件[RFC4803]一起用于基于GMPLS的交通工程配置和管理。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、[RFC2119]中所述进行解释。
MPLS-TE Label Switched paths (LSPs) may be modeled and managed using the MPLS-TE-STD-MIB module [RFC3812].
可以使用MPLS-TE-STD-MIB模块[RFC3812]对MPLS-TE标签交换路径（LSP）进行建模和管理。
Label Switching Routers (LSRs) may be migrated to model and manage their TE LSPs using the MIB modules in this document in order to migrate the LSRs to GMPLS support, or to take advantage of additional MIB objects defined in these MIB modules that are applicable to MPLS-TE.
标签交换路由器（LSR）可以迁移，以便使用本文档中的MIB模块对其TE LSP进行建模和管理，以便将LSR迁移到GMPLS支持，或者利用这些MIB模块中定义的适用于MPLS-TE的附加MIB对象。
The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document extends the MPLS-TE-STD-MIB module [RFC3812] through a series of augmentations and sparse augmentations of the MIB tables. The only additions are for support of GMPLS or to support the increased complexity of MPLS and GMPLS systems.
本文件中定义的GMPLS TE MIB模块（GMPLS-TE-STD-MIB）通过MIB表的一系列扩充和稀疏扩充扩展了MPLS-TE-STD-MIB模块[RFC3812]。唯一的补充是支持GMPLS或支持MPLS和GMPLS系统的复杂性增加。
In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB support, an implementation needs only to add support for the additional tables and objects defined in GMPLS-TE-STD-MIB. The gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an MPLS-TE LSP tunnel to benefit from the additional objects and tables of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols.
为了从MPLS-TE-STD-MIB支持迁移到GMPLS-TE-STD-MIB支持，实现只需添加对GMPLS-TE-STD-MIB中定义的附加表和对象的支持。GMPLSTunnellsencoding可设置为tunnelLspNotGmpls，以允许MPLS-TE LSP隧道受益于GMPLS-LSR-STD-MIB的附加对象和表，而不支持GMPLS协议。
The companion document for modeling and managing GMPLS-based LSRs [RFC4803] extends the MPLS-LSR-STD-MIB module [RFC3813] with the same intentions.
用于建模和管理基于GMPLS的LSR的配套文件[RFC4803]以同样的意图扩展了MPLS-LSR-STD-MIB模块[RFC3813]。
Textual conventions are defined in [RFC3811] and the IANA-GMPLS-TC-MIB module.
[RFC3811]和IANA-GMPLS-TC-MIB模块中定义了文本约定。
This document uses terminology from the MPLS architecture document [RFC3031], from the GMPLS architecture document [RFC3945], and from the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used terms are described next.
本文件使用MPLS体系结构文件[RFC3031]、GMPLS体系结构文件[RFC3945]和MPLS流量工程MIB[RFC3812]中的术语。下面介绍一些常用术语。
An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It consists of in-segment(s) and/or out-segment(s) at the egress/ingress LSRs, each segment being associated with one GMPLS-enabled interface. These are also referred to as tunnel segments.
显式路由LSP（ERLSP）称为GMPLS隧道。它包括出口/入口LSR处的入段和/或出段，每个段与一个启用GMPLS的接口相关联。这些也被称为隧道段。
Additionally, at an intermediate LSR, we model a connection as consisting of one or more in-segments and/or one or more out-segments. The binding or interconnection between in-segments and out-segments is performed using a cross-connect.
此外，在中间LSR中，我们将连接建模为由一个或多个in段和/或一个或多个out段组成。使用交叉连接执行in段和out段之间的绑定或互连。
These segment and cross-connect objects are defined in the MPLS Label Switching Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the GMPLS Label Switching Router MIB (GMPLS-LSR-STD-MIB) [RFC4803] for the GMPLS-specific extensions to these objects.
这些段和交叉连接对象在MPLS标签交换路由器MIB（MPLS-LSR-STD-MIB）[RFC3813]中定义，但有关这些对象的GMPLS特定扩展，请参见GMPLS标签交换路由器MIB（GMPLS-LSR-STD-MIB）[RFC4803]。
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]所述。
Support for GMPLS traffic-engineered tunnels requires the following configuration.
支持GMPLS交通工程隧道需要以下配置。
- Setting up tunnels with appropriate MPLS configuration parameters using [RFC3812].
- 使用[RFC3812]设置具有适当MPLS配置参数的隧道。
- Extending the tunnel definitions with GMPLS configuration parameters.
- 使用GMPLS配置参数扩展隧道定义。
- Configuring loose and strict source routed tunnel hops.
- 配置松散和严格的源路由隧道跃点。
These actions may need to be accompanied with corresponding actions using [RFC3813] and [RFC4803] to establish and configure tunnel segments, if this is done manually. Also, the in-segment and out-segment performance tables, mplsInSegmentPerfTable and mplsOutSegmentPerfTable [RFC3813], should be used to determine performance of the tunnels and tunnel segments, although it should be noted that those tables may not be appropriate for measuring performance on some types of GMPLS links.
这些操作可能需要与使用[RFC3813]和[RFC4803]建立和配置隧道段的相应操作一起进行，如果这是手动完成的。此外，应使用段内和段外性能表MPLSINSECTIONPERFTABLE和MPLSOUTSEMENTSECTIONPERFTABLE[RFC3813]确定隧道和隧道段的性能，尽管应注意，这些表可能不适合测量某些类型的GMPLS链路的性能。
The following tables contain MIB objects for performing the actions listed above when they cannot be performed solely using MIB objects defined in MPLS-TE-STD-MIB [RFC3812].
下表包含用于执行上述操作的MIB对象，但不能单独使用MPLS-TE-STD-MIB[RFC3812]中定义的MIB对象执行这些操作。
- Tunnel table (gmplsTunnelTable) for providing GMPLS-specific tunnel configuration parameters.
- 隧道表（gmplsTunnelTable），用于提供GMPLS特定隧道配置参数。
- Tunnel hop, actual tunnel hop, and computed tunnel hop tables (gmplsTunnelHopTable, gmplsTunnelARHopTable, and gmplsTunnelCHopTable) for providing additional configuration of strict and loose source routed tunnel hops.
- 隧道跃点、实际隧道跃点和计算隧道跃点表（gmplsTunnelHopTable、gmplsTunnelHopTable和gmplsTunnelHopTable），用于提供严格和松散源路由隧道跃点的附加配置。
- Performance and error reporting tables (gmplsTunnelReversePerfTable and gmplsTunnelErrorTable).
- 性能和错误报告表（GMPLSTunnelReverseperTable和gmplsTunnelErrorTable）。
These tables are described in the subsequent sections.
这些表格将在后续章节中介绍。
Additionally, the GMPLS-TE-STD-MIB module contains a new notification.
此外，GMPLS-TE-STD-MIB模块包含一个新通知。
- The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used for all GMPLS tunnels in place of the mplsTunnelDown notification defined in [RFC3812]. An implementation must not issue both the gmplsTunnelDown and the mplsTunnelDown notifications for the same event. As well as indicating that a tunnel has transitioned to operational down state, this new notification indicates the cause of the failure.
- GMPLS隧道关闭通知（gmplsTunnelDown）应用于所有GMPLS隧道，以代替[RFC3812]中定义的MPLSunneldown通知。实现不能为同一事件同时发出gmplsTunnelDown和MPLSunnelDown通知。除了指示隧道已转换为运行停机状态外，此新通知还指示故障原因。
The objects described in this section support the functionality described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables support both manually configured and signaled tunnels.
本节中描述的对象支持[RFC3473]和[RFC3472]中描述的GMPLS隧道功能。这些表格支持手动配置和信号隧道。
The gmplsTunnelTable extends the MPLS traffic engineering MIB module (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created between an LSR and a remote endpoint, and existing GMPLS tunnels to be reconfigured or removed.
gmplsTunnelTable扩展了MPLS流量工程MIB模块（MPLS-TE-STD-MIB[RFC3812]），允许在LSR和远程端点之间创建GMPLS隧道，并重新配置或删除现有的GMPLS隧道。
Note that we only support point-to-point tunnel segments, although multipoint-to-point and point-to-multipoint connections are supported by an LSR acting as a cross-connect.
请注意，我们仅支持点对点隧道段，尽管作为交叉连接的LSR支持多点对点和点对多点连接。
Each tunnel can thus have one out-segment originating at an LSR and/or one in-segment terminating at that LSR.
因此，每个隧道可以有一个起始于LSR的out段和/或一个终止于该LSR的in段。
Three objects within this table utilize enumerations in order to map to enumerations that are used in GMPLS signaling. In order to protect the GMPLS-TE-STD-MIB module from changes (in particular, extensions) to the range of enumerations supported by the signaling
此表中的三个对象利用枚举映射到GMPLS信令中使用的枚举。为了保护GMPLS-TE-STD-MIB模块不受信令支持的枚举范围变化（特别是扩展）的影响
protocols, these MIB objects use textual conventions with values maintained by IANA. For further details, see the IANA Considerations section of this document.
在协议中，这些MIB对象使用文本约定和IANA维护的值。有关更多详细信息，请参阅本文档的IANA注意事项部分。
The gmplsTunnelHopTable is used to indicate additional parameters for the hops, strict or loose, of a GMPLS tunnel defined in the gmplsTunnelTable, when it is established using signaling. Multiple tunnels may share hops by pointing to the same entry in this table.
当使用信令建立gmplsTunnelTable时，GMPLSTunnelHolTable用于指示gmplsTunnelTable中定义的GMPLS隧道的严格或松散跃点的附加参数。通过指向此表中的同一条目，多个隧道可以共享跃点。
The gmplsTunnelARHopTable is used to indicate the actual hops traversed by a tunnel as reported by the signaling protocol after the tunnel is set up. The support of this table is optional since not all GMPLS signaling protocols support this feature.
gmplsTunnelARHopTable用于指示隧道建立后信令协议报告的隧道所经过的实际跳数。此表的支持是可选的，因为并非所有GMPLS信令协议都支持此功能。
The gmplsTunnelCHopTable lists the actual hops computed by a constraint-based routing algorithm based on the gmplsTunnelHopTable. The support of this table is optional since not all implementations support computation of hop lists using a constraint-based routing protocol.
gmplsTunnelHopTable列出了基于gmplsTunnelHopTable的基于约束的路由算法计算的实际跳数。此表的支持是可选的，因为并非所有实现都支持使用基于约束的路由协议计算跃点列表。
The gmplsTunnelErrorTable provides access to information about the last error that occurred on each tunnel known about by the MIB. It indicates the nature of the error and when and how it was reported, and it can give recovery advice through an admin string.
gmplsTunnelErrorTable提供对MIB已知的每个隧道上发生的上一个错误的信息的访问。它指示错误的性质以及报告错误的时间和方式，并且可以通过管理字符串提供恢复建议。
The gmplsTunnelReversePerfTable provides additional counters to measure the performance of bidirectional GMPLS tunnels in which packets are visible. It supplements the counters in mplsTunnelPerfTable and augments gmplsTunnelTable.
GMPLSTunnelReverseperTable提供了额外的计数器，用于测量包可见的双向GMPLS隧道的性能。它补充了mplsTunnelPerfTable中的计数器，并扩展了gmplsTunnelTable。
Note that not all counters may be appropriate or available for some types of tunnel.
请注意，并非所有计数器都适用于或可用于某些类型的隧道。
64-bit counters are provided in the GMPLS-TE-STD-MIB module for high-speed interfaces where the use of 32-bit counters might be impractical. The requirements on the use of 32-bit and 64-bit counters (copied verbatim from [RFC2863]) are as follows:
GMPLS-TE-STD-MIB模块中提供了64位计数器，用于可能无法使用32位计数器的高速接口。32位和64位计数器（从[RFC2863]逐字复制）的使用要求如下：
For interfaces that operate at 20,000,000 (20 million) bits per second or less, 32-bit byte and packet counters MUST be supported. For interfaces that operate faster than 20,000,000 bits/second, and slower than 650,000,000 bits/second, 32-bit packet counters MUST be supported and 64-bit octet counters MUST be supported. For interfaces that operate at 650,000,000 bits/second or faster, 64-bit packet counters AND 64-bit octet counters MUST be supported.
对于每秒运行20000000（2000万）位或更少的接口，必须支持32位字节和数据包计数器。对于操作速度超过20000000位/秒、速度低于650000000位/秒的接口，必须支持32位数据包计数器，并且必须支持64位八位字节计数器。对于以650000000位/秒或更快速度运行的接口，必须支持64位数据包计数器和64位八位字节计数器。
The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in [RFC4803] and provides a way to model labels in a GMPLS system where labels might not be simple 32-bit integers.
gmplsLabelTable位于[RFC4803]中的GMPLS-LABEL-STD-MIB模块中，它提供了一种在GMPLS系统中建模标签的方法，其中标签可能不是简单的32位整数。
The hop tables in this document (gmplsTunnelHopTable, gmplsTunnelCHopTable, and gmplsTunnelARHopTable) and the segment tables in [RFC3813] (mplsInSegmentTable and mplsOutSegmentTable) contain objects with syntax MplsLabel.
本文档中的跃点表（gmplsTunnelHopTable、gmplsTunnelCHopTable和gmplsTunnelARHopTable）和[RFC3813]（mplsInSegmentTable和mplsOutSegmentTable）中的段表包含语法为MplsLabel的对象。
MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable of representing any MPLS Label and most GMPLS Labels. However, some GMPLS Labels are larger than 32 bits and may be of arbitrary length. Furthermore, some labels that may be safely encoded in 32 bits are constructed from multiple sub-fields. Additionally, some GMPLS technologies support the concatenation of individual labels to represent a data flow carried as multiple sub-flows.
MplsLabel（在[RFC3811]中定义）是一个32位整数，能够表示任何MPLS标签和大多数GMPLS标签。然而，一些GMPLS标签大于32位，并且可能具有任意长度。此外，一些可安全编码为32位的标签由多个子字段构成。此外，一些GMPLS技术支持单个标签的串联，以表示作为多个子流承载的数据流。
These GMPLS cases require that something other than a simple 32-bit integer be made available to represent the labels. This is achieved through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB [RFC4803].
这些GMPLS案例要求提供除简单32位整数之外的其他内容来表示标签。这是通过GMPLS-LABEL-STD-MIB[RFC4803]中包含的GMPLS标签表实现的。
The tables in this document and [RFC3813] that include objects with syntax MplsLabel also include companion objects that are row pointers. If the row pointer is set to zeroDotZero (0.0), then an object of syntax MplsLabel contains the label encoded as a 32-bit integer. But otherwise the row pointer indicates a row in another MIB table that includes the label. In these cases, the row pointer may indicate a row in the gmplsLabelTable.
本文档和[RFC3813]中包含语法为MplsLabel的对象的表还包括作为行指针的伴随对象。如果行指针设置为zeroDotZero（0.0），则语法为MplsLabel的对象包含编码为32位整数的标签。但除此之外，行指针指示另一个MIB表中包含标签的行。在这些情况下，行指针可能指示gmplsLabelTable中的一行。
This provides both a good way to support legacy systems that implement MPLS-TE-STD-MIB [RFC3812], and a significant simplification in GMPLS systems that are limited to a single, simple label type.
这为支持实现MPLS-TE-STD-MIB[RFC3812]的传统系统提供了一种很好的方法，并且大大简化了仅限于单一简单标签类型的GMPLS系统。
Note that gmplsLabelTable supports concatenated labels through the use of a label sub-index (gmplsLabelSubindex).
请注意，通过使用标签子索引（gmplsLabelSubindex），gmplsLabelTable支持连接标签。
This section contains an example of which MIB objects should be modified to create a GMPLS tunnel. This example shows a best effort, loosely routed, bidirectional traffic engineered tunnel, which spans two hops of a simple network, uses Generalized Label requests with Lambda encoding, has label recording and shared link layer protection. Note that these objects should be created on the "head-end" LSR.
本节包含应修改哪些MIB对象以创建GMPLS隧道的示例。此示例显示了一个尽力而为、松散路由的双向流量工程隧道，它跨越简单网络的两个跃点，使用具有Lambda编码的通用标签请求，具有标签记录和共享链路层保护。请注意，应在“前端”LSR上创建这些对象。
First in the mplsTunnelTable:
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 192.0.2.1,
mplsTunnelEgressLSRId = 192.0.2.2,
mplsTunnelName = "My first tunnel",
mplsTunnelDescr = "Here to there and back again",
mplsTunnelIsIf = true(1),
mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
mplsTunnelSignallingProto = none(1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = recordRoute(4),
mplsTunnelOwner = snmp(2),
mplsTunnelLocalProtectInUse = false(2),
mplsTunnelResourcePointer = mplsTunnelResourceIndex.6,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelPrimaryInstance = 0,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1,
mplsTunnelRole = head(1),
mplsTunnelRowStatus = createAndWait(5),
}
First in the mplsTunnelTable:
{
mplsTunnelIndex = 1,
mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 192.0.2.1,
mplsTunnelEgressLSRId = 192.0.2.2,
mplsTunnelName = "My first tunnel",
mplsTunnelDescr = "Here to there and back again",
mplsTunnelIsIf = true(1),
mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
mplsTunnelSignallingProto = none(1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 0,
mplsTunnelSessionAttributes = recordRoute(4),
mplsTunnelOwner = snmp(2),
mplsTunnelLocalProtectInUse = false(2),
mplsTunnelResourcePointer = mplsTunnelResourceIndex.6,
mplsTunnelInstancePriority = 1,
mplsTunnelHopTableIndex = 1,
mplsTunnelPrimaryInstance = 0,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1,
mplsTunnelRole = head(1),
mplsTunnelRowStatus = createAndWait(5),
}
In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2):
{
gmplsTunnelUnnumIf = true(1),
gmplsTunnelAttributes = labelRecordingRequired(1),
gmplsTunnelLSPEncoding = tunnelLspLambda,
gmplsTunnelSwitchingType = lsc,
gmplsTunnelLinkProtection = shared(2),
gmplsTunnelGPid = lambda,
gmplsTunnelSecondary = false(2),
gmplsTunnelDirection = bidirectional(1)
gmplsTunnelPathComp = explicit(2),
gmplsTunnelSendPathNotifyRecipientType = ipv4(1),
gmplsTunnelSendPathNotifyRecipient = 'C0000201'H,
gmplsTunnelAdminStatusFlags = 0,
gmplsTunnelExtraParamsPtr = 0.0
}
In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2):
{
gmplsTunnelUnnumIf = true(1),
gmplsTunnelAttributes = labelRecordingRequired(1),
gmplsTunnelLSPEncoding = tunnelLspLambda,
gmplsTunnelSwitchingType = lsc,
gmplsTunnelLinkProtection = shared(2),
gmplsTunnelGPid = lambda,
gmplsTunnelSecondary = false(2),
gmplsTunnelDirection = bidirectional(1)
gmplsTunnelPathComp = explicit(2),
gmplsTunnelSendPathNotifyRecipientType = ipv4(1),
gmplsTunnelSendPathNotifyRecipient = 'C0000201'H,
gmplsTunnelAdminStatusFlags = 0,
gmplsTunnelExtraParamsPtr = 0.0
}
Entries in the mplsTunnelResourceTable, mplsTunnelHopTable, and gmplsTunnelHopTable are created and activated at this time.
此时将创建并激活mplsTunnelResourceTable、mplsTunnelHopTable和gmplsTunnelHopTable中的条目。
In mplsTunnelResourceTable:
{
mplsTunnelResourceIndex = 6,
mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceRowStatus = createAndGo(4)
}
In mplsTunnelResourceTable:
{
mplsTunnelResourceIndex = 6,
mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceRowStatus = createAndGo(4)
}
The next two instances of mplsTunnelHopEntry are used to denote the hops this tunnel will take across the network.
接下来的两个mplsTunnelHopEntry实例用于表示此隧道将通过网络进行的跃点。
The following denotes the beginning of the network, or the first hop in our example. We have used the fictitious LSR identified by "192.0.2.1" as our head-end router.
下面表示网络的开始，或者我们示例中的第一个跃点。我们使用了由“192.0.2.1”标识的虚拟LSR作为我们的前端路由器。
In mplsTunnelHopTable:
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpv4Addr = 192.0.2.1,
mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = strict(1),
mplsTunnelHopRowStatus = createAndWait(5),
}
In mplsTunnelHopTable:
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpv4Addr = 192.0.2.1,
mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = strict(1),
mplsTunnelHopRowStatus = createAndWait(5),
}
The following denotes the end of the network, or the last hop in our example. We have used the fictitious LSR identified by "192.0.2.2" as our tail-end router.
下面表示网络的结束，或者我们示例中的最后一个跃点。我们使用了由“192.0.2.2”标识的虚拟LSR作为我们的终端路由器。
In mplsTunnelHopTable:
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpv4Addr = 192.0.2.2,
mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = loose(2),
mplsTunnelHopRowStatus = createAndGo(4)
}
In mplsTunnelHopTable:
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpv4Addr = 192.0.2.2,
mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = loose(2),
mplsTunnelHopRowStatus = createAndGo(4)
}
Now an associated entry in the gmplsTunnelHopTable is created to provide additional GMPLS hop configuration indicating that the first hop is an unnumbered link using Explicit Forward and Reverse Labels.
现在，在gmplsTunnelHopTable中创建一个相关条目，以提供额外的GMPLS跃点配置，指示第一个跃点是使用显式正向和反向标签的未编号链路。
An entry in the gmplsLabelTable is created first to include the Explicit Label.
首先在gmplsLabelTable中创建一个条目以包含显式标签。
In gmplsLabelTable:
{
gmplsLabelInterface = 2,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4)
}
In gmplsLabelTable:
{
gmplsLabelInterface = 2,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4)
}
In gmplsTunnelHopTable(1,1,1):
{
gmplsTunnelHopLabelStatuses = forwardPresent(0)
+reversePresent(1),
gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable(2,1,0)
gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable(2,1,0)
}
In gmplsTunnelHopTable(1,1,1):
{
gmplsTunnelHopLabelStatuses = forwardPresent(0)
+reversePresent(1),
gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable(2,1,0)
gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable(2,1,0)
}
The first hop is now activated:
第一个跃点现在已激活：
In mplsTunnelHopTable(1,1,1):
{
mplsTunnelHopRowStatus = active(1)
}
In mplsTunnelHopTable(1,1,1):
{
mplsTunnelHopRowStatus = active(1)
}
No gmplsTunnelHopEntry is created for the second hop as it contains no special GMPLS features.
没有为第二个跃点创建GMPLSTunnelOpenTry，因为它不包含特殊的GMPLS功能。
Finally, the mplsTunnelEntry is activated:
最后，mplsTunnelEntry被激活：
In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2)
{
mplsTunnelRowStatus = active(1)
}
In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2)
{
mplsTunnelRowStatus = active(1)
}
This MIB module makes reference to the following documents: [RFC2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], and [RFC4202].
此MIB模块参考以下文档：[RFC2205]、[RFC2578]、[RFC2579]、[RFC2580]、[RFC3209]、[RFC3411]、[RFC3471]、[RFC3473]、[RFC3477]、[RFC3812]、[RFC4001]和[RFC4202]。
GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580 TruthValue, TimeStamp, RowPointer FROM SNMPv2-TC -- RFC 2579 InetAddress, InetAddressType FROM INET-ADDRESS-MIB -- RFC 4001 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId, mplsTunnelHopListIndex, mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, mplsTunnelARHopListIndex, mplsTunnelARHopIndex, mplsTunnelCHopListIndex, mplsTunnelCHopIndex, mplsTunnelEntry, mplsTunnelAdminStatus, mplsTunnelOperStatus, mplsTunnelGroup, mplsTunnelScalarGroup FROM MPLS-TE-STD-MIB -- RFC3812 IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC, IANAGmplsGeneralizedPidTC, IANAGmplsAdminStatusInformationTC FROM IANA-GMPLS-TC-MIB mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 ;
从SNMPv2 SMI导入MODULE-IDENTITY、OBJECT-TYPE、NOTIFICATION-TYPE、Unsigned32、Counter32、Counter64、zeroDotZero、Gauge32--从SNMPv2 CONF导入RFC 2578 MODULE-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUP--从SNMPv2 TC导入RFC 2580 TruthValue、TimeStamp、RowPointer--RFC 2579 InetAddress，INET-ADDRESS-MIB中的InetAddressType——SNMP-FRAMEWORK-MIB中的RFC 4001 SNMPAdministring——RFC 3411 mplsTunnelIndex、MPlstunnelinInstance、MPlstunneLingRessRid、MPlstunnelegressRid、MPlstunnelOppthIndex、MPlstunnelOppthIndex、mplsTunnelHopListIndex、mplsTunnelHopListIndex、mplsTunnelHopListIndex、，MPLS-TE-STD-MIB中的mplsTunnelCHopIndex、mplsTunnelEntry、mplsTunnelAdminStatus、mplsTunnelOperStatus、mplsTunnelGroup、MPLS-STD-MIB中的mplsTunnelScalarGroup——RFC3812 IANAGMPLSSpencodingTypeTC、IANAGMPLS通用PIDTC、IANAGMPLS-TC-MIB中的IANAGMPLSSTDMIB信息TC——RFC 3811；
gmplsTeStdMIB MODULE-IDENTITY LAST-UPDATED "200702270000Z" -- 27 February 2007 00:00:00 GMT ORGANIZATION "IETF Common Control and Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk
gmplsTeStdMIB模块标识最后更新“200702270000Z”-2007年2月27日00:00:00 GMT组织“IETF通用控制和测量平面（CCAMP）工作组”联系方式“Thomas D.Nadeau Cisco Systems，Inc.电子邮件：tnadeau@cisco.comAdrian Farrel老狗咨询电子邮件：adrian@olddog.co.uk
Comments about this document should be emailed directly to the CCAMP working group mailing list at ccamp@ops.ietf.org."
有关本文件的意见应通过电子邮件直接发送至CCAMP工作组邮件列表，地址为ccamp@ops.ietf.org."
DESCRIPTION "Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4802; see the RFC itself for full legal notices.
描述“IETF信托（2007）版权所有。此MIB模块的此版本是RFC 4802的一部分；有关完整的法律通知，请参阅RFC本身。
This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003.
"
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4802."
::= { mplsStdMIB 13 }
This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003.
"
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4802."
::= { mplsStdMIB 13 }
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 }
gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 }
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 }
gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 }
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
gmplsTunnelsConfigured OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of GMPLS tunnels configured on this device. A GMPLS
gmplsTunnelsConfigured对象类型语法量表32 MAX-ACCESS只读状态当前描述“此设备上配置的GMPLS隧道数。A GMPLS
tunnel is considered configured if an entry for the tunnel
exists in the gmplsTunnelTable and the associated
mplsTunnelRowStatus is active(1)."
::= { gmplsTeScalars 1 }
tunnel is considered configured if an entry for the tunnel
exists in the gmplsTunnelTable and the associated
mplsTunnelRowStatus is active(1)."
::= { gmplsTeScalars 1 }
gmplsTunnelsActive OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of GMPLS tunnels active on this device. A GMPLS
tunnel is considered active if there is an entry in the
gmplsTunnelTable and the associated mplsTunnelOperStatus for the
tunnel is up(1)."
::= { gmplsTeScalars 2 }
gmplsTunnelsActive OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of GMPLS tunnels active on this device. A GMPLS
tunnel is considered active if there is an entry in the
gmplsTunnelTable and the associated mplsTunnelOperStatus for the
tunnel is up(1)."
::= { gmplsTeScalars 2 }
gmplsTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The gmplsTunnelTable sparsely extends the mplsTunnelTable of MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed.
gmplsTunnelTable GMPLSTunnelLentry MAX-ACCESS不可访问状态当前描述的gmplsTunnelTable对象类型语法序列“gmplsTunnelTable稀疏地扩展了MPLS-TE-STD-MIB的MPLSSTunnelTable。它允许在LSR和远程端点之间创建GMPLS隧道，并重新配置或删除现有隧道。
Note that only point-to-point tunnel segments are supported, although multipoint-to-point and point-to-multipoint connections are supported by an LSR acting as a cross-connect. Each tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR.
请注意，尽管作为交叉连接的LSR支持多点对点和点对多点连接，但仅支持点对点隧道段。因此，每个隧道可以有一个起始于此LSR的out段和/或一个终止于此LSR的in段。
The row status of an entry in this table is controlled by the mplsTunnelRowStatus in the corresponding entry in the mplsTunnelTable. When the corresponding mplsTunnelRowStatus has value active(1), a row in this table may not be created or modified.
此表中条目的行状态由mplsTunnelRowStatus控制，该状态位于mplsTunnelTable中相应条目中。当对应的mplsTunnelRowStatus的值为active（1）时，可能无法创建或修改此表中的行。
The exception to this rule is the
gmplsTunnelAdminStatusInformation object, which can be modified
while the tunnel is active."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 1 }
The exception to this rule is the
gmplsTunnelAdminStatusInformation object, which can be modified
while the tunnel is active."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 1 }
gmplsTunnelEntry OBJECT-TYPE SYNTAX GmplsTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table in association with the corresponding entry in the mplsTunnelTable represents a GMPLS tunnel.
gmplsTunnelEntry对象类型语法gmplsTunnelEntry MAX-ACCESS不可访问状态当前描述“此表中的条目与mplsTunnelTable中的相应条目关联表示GMPLS隧道。
An entry can be created by a network administrator via SNMP SET
commands, or in response to signaling protocol events."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { gmplsTunnelTable 1 }
An entry can be created by a network administrator via SNMP SET
commands, or in response to signaling protocol events."
INDEX {
mplsTunnelIndex,
mplsTunnelInstance,
mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId
}
::= { gmplsTunnelTable 1 }
GmplsTunnelEntry ::= SEQUENCE {
gmplsTunnelUnnumIf TruthValue,
gmplsTunnelAttributes BITS,
gmplsTunnelLSPEncoding IANAGmplsLSPEncodingTypeTC,
gmplsTunnelSwitchingType IANAGmplsSwitchingTypeTC,
gmplsTunnelLinkProtection BITS,
gmplsTunnelGPid IANAGmplsGeneralizedPidTC,
gmplsTunnelSecondary TruthValue,
gmplsTunnelDirection INTEGER,
gmplsTunnelPathComp INTEGER,
gmplsTunnelUpstreamNotifyRecipientType InetAddressType,
gmplsTunnelUpstreamNotifyRecipient InetAddress,
gmplsTunnelSendResvNotifyRecipientType InetAddressType,
gmplsTunnelSendResvNotifyRecipient InetAddress,
gmplsTunnelDownstreamNotifyRecipientType InetAddressType,
gmplsTunnelDownstreamNotifyRecipient InetAddress,
gmplsTunnelSendPathNotifyRecipientType InetAddressType,
gmplsTunnelSendPathNotifyRecipient InetAddress,
gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformationTC,
gmplsTunnelExtraParamsPtr RowPointer
}
GmplsTunnelEntry ::= SEQUENCE {
gmplsTunnelUnnumIf TruthValue,
gmplsTunnelAttributes BITS,
gmplsTunnelLSPEncoding IANAGmplsLSPEncodingTypeTC,
gmplsTunnelSwitchingType IANAGmplsSwitchingTypeTC,
gmplsTunnelLinkProtection BITS,
gmplsTunnelGPid IANAGmplsGeneralizedPidTC,
gmplsTunnelSecondary TruthValue,
gmplsTunnelDirection INTEGER,
gmplsTunnelPathComp INTEGER,
gmplsTunnelUpstreamNotifyRecipientType InetAddressType,
gmplsTunnelUpstreamNotifyRecipient InetAddress,
gmplsTunnelSendResvNotifyRecipientType InetAddressType,
gmplsTunnelSendResvNotifyRecipient InetAddress,
gmplsTunnelDownstreamNotifyRecipientType InetAddressType,
gmplsTunnelDownstreamNotifyRecipient InetAddress,
gmplsTunnelSendPathNotifyRecipientType InetAddressType,
gmplsTunnelSendPathNotifyRecipient InetAddress,
gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformationTC,
gmplsTunnelExtraParamsPtr RowPointer
}
gmplsTunnelUnnumIf OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel corresponds to an unnumbered interface represented by an entry in the interfaces group table (the ifTable) with ifType set to mpls(166).
GMPLSTunenelunnumif对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION“表示此隧道是否对应于由接口组表（ifTable）中的条目表示的未编号接口，ifType设置为mpls（166）。
This object is only used if mplsTunnelIsIf is set to 'true'.
仅当mplsTunnelIsIf设置为“true”时，才使用此对象。
If both this object and the mplsTunnelIsIf object are set to 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID object to the outgoing Path message.
如果此对象和mplsTunnelIsIf对象都设置为“true”，则原始LSR会将LSP_TUNNEL_INTERFACE_ID对象添加到传出路径消息中。
This object contains information that is only used by the
terminating LSR."
REFERENCE
"1. Signalling Unnumbered Links in RSVP-TE, RFC 3477."
DEFVAL { false }
::= { gmplsTunnelEntry 1 }
This object contains information that is only used by the
terminating LSR."
REFERENCE
"1. Signalling Unnumbered Links in RSVP-TE, RFC 3477."
DEFVAL { false }
::= { gmplsTunnelEntry 1 }
gmplsTunnelAttributes OBJECT-TYPE
SYNTAX BITS {
labelRecordingDesired(0)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This bitmask indicates optional parameters for this tunnel.
These bits should be taken in addition to those defined in
mplsTunnelSessionAttributes in order to determine the full set
of options to be signaled (for example SESSION_ATTRIBUTES flags
in RSVP-TE). The following describes these bitfields:
gmplsTunnelAttributes OBJECT-TYPE
SYNTAX BITS {
labelRecordingDesired(0)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This bitmask indicates optional parameters for this tunnel.
These bits should be taken in addition to those defined in
mplsTunnelSessionAttributes in order to determine the full set
of options to be signaled (for example SESSION_ATTRIBUTES flags
in RSVP-TE). The following describes these bitfields:
labelRecordingDesired
This flag is set to indicate that label information should be
included when doing a route record. This bit is not valid
unless the recordRoute bit is set."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
sections 4.4.3, 4.7.1, and 4.7.2."
DEFVAL { { } }
::= { gmplsTunnelEntry 2 }
labelRecordingDesired
This flag is set to indicate that label information should be
included when doing a route record. This bit is not valid
unless the recordRoute bit is set."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
sections 4.4.3, 4.7.1, and 4.7.2."
DEFVAL { { } }
::= { gmplsTunnelEntry 2 }
gmplsTunnelLSPEncoding OBJECT-TYPE SYNTAX IANAGmplsLSPEncodingTypeTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the encoding of the LSP being requested.
gmplsTunnelLSPEncoding对象类型语法IANAGmplsLSPEncodingTypeTC MAX-ACCESS read create STATUS current DESCRIPTION“此对象表示所请求LSP的编码。
A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is not in use. Some objects in this MIB module may be of use for MPLS signaling extensions that do not use GMPLS signaling. By setting this object to 'tunnelLspNotGmpls', an application may
“tunnelLspNotGmpls”的值表示GMPLS信令未被使用。此MIB模块中的某些对象可能用于不使用GMPLS信令的MPLS信令扩展。通过将此对象设置为“tunnelLspNotGmpls”，应用程序可以
indicate that only those objects meaningful in MPLS should be examined.
指示只应检查那些在MPLS中有意义的对象。
The values to use are defined in the TEXTUAL-CONVENTION
IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB
module."
DEFVAL { tunnelLspNotGmpls }
::= { gmplsTunnelEntry 3 }
The values to use are defined in the TEXTUAL-CONVENTION
IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB
module."
DEFVAL { tunnelLspNotGmpls }
::= { gmplsTunnelEntry 3 }
gmplsTunnelSwitchingType OBJECT-TYPE SYNTAX IANAGmplsSwitchingTypeTC MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the type of switching that should be performed on a particular link. This field is needed for links that advertise more than one type of switching capability.
gmplsTunnelSwitchingType对象类型语法IANAGMPLSSSwitchingTypeTC MAX-ACCESS read create STATUS current DESCRIPTION”表示应在特定链路上执行的切换类型。对于播发多种切换功能的链路，需要此字段。
The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsSwitchingTypeTC found in the IANA-GMPLS-TC-MIB module.
要使用的值在IANA-GMPLS-TC-MIB模块中的文本约定IANAGMPLSSSwitchingTypeTC中定义。
This object is only meaningful if gmplsTunnelLSPEncodingType
is not set to 'tunnelLspNotGmpls'."
DEFVAL { unknown }
::= { gmplsTunnelEntry 4 }
This object is only meaningful if gmplsTunnelLSPEncodingType
is not set to 'tunnelLspNotGmpls'."
DEFVAL { unknown }
::= { gmplsTunnelEntry 4 }
gmplsTunnelLinkProtection OBJECT-TYPE
SYNTAX BITS {
extraTraffic(0),
unprotected(1),
shared(2),
dedicatedOneToOne(3),
dedicatedOnePlusOne(4),
enhanced(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This bitmask indicates the level of link protection required. A
value of zero (no bits set) indicates that any protection may be
used. The following describes these bitfields:
gmplsTunnelLinkProtection OBJECT-TYPE
SYNTAX BITS {
extraTraffic(0),
unprotected(1),
shared(2),
dedicatedOneToOne(3),
dedicatedOnePlusOne(4),
enhanced(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This bitmask indicates the level of link protection required. A
value of zero (no bits set) indicates that any protection may be
used. The following describes these bitfields:
extraTraffic This flag is set to indicate that the LSP should use links that are protecting other (primary) traffic. Such LSPs may be preempted when the links carrying the (primary) traffic being protected fail.
extraTraffic此标志设置为指示LSP应使用保护其他（主）流量的链路。当承载被保护的（主要）业务的链路发生故障时，这种lsp可以被抢占。
unprotected This flag is set to indicate that the LSP should not use any link layer protection.
未保护此标志设置为指示LSP不应使用任何链路层保护。
shared This flag is set to indicate that a shared link layer protection scheme, such as 1:N protection, should be used to support the LSP.
shared此标志设置为指示应使用共享链路层保护方案（如1:N保护）来支持LSP。
dedicatedOneToOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1:1 protection, should be used to support the LSP.
专用链路层保护方案，即1:1保护，用于支持LSP。
dedicatedOnePlusOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1+1 protection, should be used to support the LSP.
专用链路层保护方案，即1+1保护，用于支持LSP。
enhanced This flag is set to indicate that a protection scheme that is more reliable than Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING.
增强型此标志用于指示应使用比专用1+1更可靠的保护方案，例如4光纤BLSR/MS-SPRING。
This object is only meaningful if gmplsTunnelLSPEncoding is
not set to 'tunnelLspNotGmpls'."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 7.1."
DEFVAL { { } }
::= { gmplsTunnelEntry 5 }
This object is only meaningful if gmplsTunnelLSPEncoding is
not set to 'tunnelLspNotGmpls'."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 7.1."
DEFVAL { { } }
::= { gmplsTunnelEntry 5 }
gmplsTunnelGPid OBJECT-TYPE SYNTAX IANAGmplsGeneralizedPidTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the payload carried by the LSP. It is only required when GMPLS will be used for this LSP.
GMPLSTuneLGPID对象类型语法IANAGPMPLSGeneralizedPIDTC MAX-ACCESS read create STATUS current DESCRIPTION“此对象表示LSP承载的有效负载。仅当GMPLS将用于此LSP时才需要此对象。
The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsGeneralizedPidTC found in the IANA-GMPLS-TC-MIB module.
要使用的值在IANA-GMPLS-TC-MIB模块中的文本约定IANAGMMPLSGeneralizedPIDTC中定义。
This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'."
DEFVAL { unknown }
::= { gmplsTunnelEntry 6 }
This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'."
DEFVAL { unknown }
::= { gmplsTunnelEntry 6 }
gmplsTunnelSecondary OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates that the requested LSP is a secondary LSP.
gmplsTunnelSecondary对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION”表示请求的LSP是辅助LSP。
This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 7.1."
DEFVAL { false }
::= { gmplsTunnelEntry 7 }
This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 7.1."
DEFVAL { false }
::= { gmplsTunnelEntry 7 }
gmplsTunnelDirection OBJECT-TYPE
SYNTAX INTEGER {
forward(0),
bidirectional(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Whether this tunnel carries forward data only (is
unidirectional) or is bidirectional.
gmplsTunnelDirection OBJECT-TYPE
SYNTAX INTEGER {
forward(0),
bidirectional(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Whether this tunnel carries forward data only (is
unidirectional) or is bidirectional.
Values of this object other than 'forward' are meaningful
only if gmplsTunnelLSPEncoding is not set to
'tunnelLspNotGmpls'."
DEFVAL { forward }
::= { gmplsTunnelEntry 8 }
Values of this object other than 'forward' are meaningful
only if gmplsTunnelLSPEncoding is not set to
'tunnelLspNotGmpls'."
DEFVAL { forward }
::= { gmplsTunnelEntry 8 }
gmplsTunnelPathComp OBJECT-TYPE
SYNTAX INTEGER {
dynamicFull(1), -- CSPF fully computed
explicit(2), -- fully specified path
dynamicPartial(3) -- CSPF partially computed
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value instructs the source node on how to perform path
computation on the explicit route specified by the associated
entries in the gmplsTunnelHopTable.
gmplsTunnelPathComp OBJECT-TYPE
SYNTAX INTEGER {
dynamicFull(1), -- CSPF fully computed
explicit(2), -- fully specified path
dynamicPartial(3) -- CSPF partially computed
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value instructs the source node on how to perform path
computation on the explicit route specified by the associated
entries in the gmplsTunnelHopTable.
dynamicFull The user specifies at least the source and destination of the path and expects that the Constrained
dynamicFull用户至少指定路径的源和目标，并希望受约束的
Shortest Path First (CSPF) will calculate the remainder of the path.
最短路径优先（CSPF）将计算路径的剩余部分。
explicit The user specifies the entire path for the tunnel to take. This path may contain strict or loose hops. Evaluation of the explicit route will be performed hop by hop through the network.
explicit用户指定隧道要采用的整个路径。此路径可能包含严格的跃点或松散的跃点。显式路由的评估将通过网络逐跳执行。
dynamicPartial The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. The path computed by CSPF is allowed to be only partially computed allowing the remainder of the path to be filled in across the network.
dynamicPartial用户至少指定路径的源和目标，并期望CSPF计算路径的其余部分。CSPF计算的路径只允许部分计算，允许在整个网络中填充路径的其余部分。
When an entry is present in the gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set.
当隧道的gmplsTunnelTable中存在条目时，必须使用gmplsTunnelPathComp，并且必须忽略且不应设置MPLSunneLhopTable中的任何相应MPLSunnelOpenTrypathComp对象。
mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of MPLS-TE-STD-MIB.
mplsTunnelHopTable和MPLStunnelOpenThrypathComp是MPLS-TE-STD-MIB的一部分。
This object should be ignored if the value of
gmplsTunnelLSPEncoding is 'tunnelLspNotGmpls'."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
DEFVAL { dynamicFull }
::= { gmplsTunnelEntry 9 }
This object should be ignored if the value of
gmplsTunnelLSPEncoding is 'tunnelLspNotGmpls'."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
DEFVAL { dynamicFull }
::= { gmplsTunnelEntry 9 }
gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelUpstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 10 }
gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelUpstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 10 }
gmplsTunnelUpstreamNotifyRecipient OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION
GMPLSTuneLupStreamNotifyRecipient对象类型语法InetAddress MAX-ACCESS读取创建状态当前说明
"Indicates the address of the upstream recipient for Notify messages relating to this tunnel and issued by this LSR. This information is typically received from an upstream LSR in a Path message.
“表示与此隧道相关并由此LSR发出的通知消息的上游收件人的地址。此信息通常从Path消息中的上游LSR接收。
This object is only valid when signaling a tunnel using RSVP.
此对象仅在使用RSVP向隧道发送信号时有效。
It is also not valid at the head end of a tunnel since there are no upstream LSRs to which to send a Notify message.
它在隧道的前端也无效，因为没有上游LSR向其发送通知消息。
This object is interpreted in the context of the value of
gmplsTunnelUpstreamNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelUpstreamNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 11 }
This object is interpreted in the context of the value of
gmplsTunnelUpstreamNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelUpstreamNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 11 }
gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelSendResvNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 12 }
gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelSendResvNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 12 }
gmplsTunnelSendResvNotifyRecipient OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates to an upstream LSR the address to which it should send downstream Notify messages relating to this tunnel.
GMPLSTunnelsAndresvNotifyRecipient对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“向上游LSR指示其应向其发送与此隧道相关的下游通知消息的地址。
This object is only valid when signaling a tunnel using RSVP.
此对象仅在使用RSVP向隧道发送信号时有效。
It is also not valid at the head end of the tunnel since no Resv messages are sent from that LSR for this tunnel.
它在隧道的前端也无效，因为没有从该LSR为此隧道发送Resv消息。
If set to 0, no Notify Request object will be included in the outgoing Resv messages.
如果设置为0，则传出的Resv消息中将不包括Notify Request对象。
This object is interpreted in the context of the value of gmplsTunnelSendResvNotifyRecipientType. If this object is set to
此对象在gmplsTunnelSendResvNotifyRecipientType值的上下文中解释。如果此对象设置为
0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 13 }
0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 13 }
gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelDownstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 14 }
gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to aid in interpretation of
gmplsTunnelDownstreamNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 14 }
gmplsTunnelDownstreamNotifyRecipient OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the address of the downstream recipient for Notify messages relating to this tunnel and issued by this LSR. This information is typically received from an upstream LSR in a Resv message. This object is only valid when signaling a tunnel using RSVP.
gmplsTunnelDownstreamNotifyRecipient对象类型语法InetAddress MAX-ACCESS读取创建状态当前描述“表示与此隧道相关并由此LSR发出的通知消息的下游收件人的地址。该信息通常在Resv消息中从上游LSR接收。此对象仅在使用RSVP向隧道发送信号时有效。
It is also not valid at the tail end of a tunnel since there are no downstream LSRs to which to send a Notify message.
由于没有下游LSR可向其发送通知消息，因此它在隧道的尾部也无效。
This object is interpreted in the context of the value of
gmplsTunnelDownstreamNotifyRecipientType. If this object is set
to 0, the value of gmplsTunnelDownstreamNotifyRecipientType MUST
be set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2.
"
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 15 }
This object is interpreted in the context of the value of
gmplsTunnelDownstreamNotifyRecipientType. If this object is set
to 0, the value of gmplsTunnelDownstreamNotifyRecipientType MUST
be set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2.
"
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 15 }
gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION
gmplsTunnelSendPathNotifyRecipientType对象类型语法InetAddressType MAX-ACCESS读取创建状态当前说明
"This object is used to aid in interpretation of
gmplsTunnelSendPathNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 16 }
"This object is used to aid in interpretation of
gmplsTunnelSendPathNotifyRecipient."
DEFVAL { unknown }
::= { gmplsTunnelEntry 16 }
gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates to a downstream LSR the address to which it should send upstream Notify messages relating to this tunnel.
gmplsTunnelSendPathNotifyRecipient对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“向下游LSR指示其应向其发送与此隧道相关的上游通知消息的地址。
This object is only valid when signaling a tunnel using RSVP.
此对象仅在使用RSVP向隧道发送信号时有效。
It is also not valid at the tail end of the tunnel since no Path messages are sent from that LSR for this tunnel.
它在隧道的末尾也无效，因为没有从该LSR为此隧道发送路径消息。
If set to 0, no Notify Request object will be included in the outgoing Path messages.
如果设置为0，则传出路径消息中将不包括Notify请求对象。
This object is interpreted in the context of the value of
gmplsTunnelSendPathNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 17 }
This object is interpreted in the context of the value of
gmplsTunnelSendPathNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be
set to unknown(0)."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 17 }
gmplsTunnelAdminStatusFlags OBJECT-TYPE SYNTAX IANAGmplsAdminStatusInformationTC MAX-ACCESS read-create STATUS current DESCRIPTION "Determines the setting of the Admin Status flags in the Admin Status object or TLV, as described in RFC 3471. Setting this field to a non-zero value will result in the inclusion of the Admin Status object on signaling messages.
gmplsTunnelAdminStatusFlags对象类型语法IANANGMPLSADMINSTATUSINFormationTC MAX-ACCESS read create STATUS当前说明确定管理状态对象或TLV中管理状态标志的设置，如RFC 3471中所述。将此字段设置为非零值将导致在信令消息中包含Admin Status对象。
The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsAdminStatusInformationTC found in the IANA-GMPLS-TC-MIB module.
要使用的值在IANA-GMPLS-TC-MIB模块中的文本约定IANAGMPLSSAdminStatusInformation TC中定义。
This value of this object can be modified when the corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus is active(1). By doing so, a new signaling message will be
当相应的mplsTunnelRowStatus和mplsTunnelAdminStatus处于活动状态（1）时，可以修改此对象的此值。这样，将生成一条新的信令消息
triggered including the requested Admin Status object or
TLV."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 8."
DEFVAL { { } }
::= { gmplsTunnelEntry 18 }
triggered including the requested Admin Status object or
TLV."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 8."
DEFVAL { { } }
::= { gmplsTunnelEntry 18 }
gmplsTunnelExtraParamsPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, Synchronous Optical Network (SONET) resource usage). Such parameters can be supplied in an external table and referenced from here.
GMPLSTunenelextraparamsptr对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“一些隧道将运行在可有效支持特定于技术的附加参数的传输上（例如，同步光网络（SONET）资源使用）。这些参数可以在外部表格中提供，并从此处引用。
A value of zeroDotzero in this attribute indicates that there
is no such additional information."
DEFVAL { zeroDotZero }
::= { gmplsTunnelEntry 19 }
A value of zeroDotzero in this attribute indicates that there
is no such additional information."
DEFVAL { zeroDotZero }
::= { gmplsTunnelEntry 19 }
gmplsTunnelHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable of MPLS-TE-STD-MIB. It is used to indicate the Explicit Labels to be used in an explicit path for a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, when it is established using signaling. It does not insert new hops, but does define new values for hops defined in the mplsTunnelHopTable.
gmplsTunnelHopTable gmplsTunnelHopTable对象类型语法GMPLSTunnelHOPTERY MAX-ACCESS的序列不可访问状态当前描述“gmplsTunnelHopTable稀疏地扩展了MPLS-TE-STD-MIB的mplsTunnelHopTable。当使用信令建立GMPLS隧道时，它用于指示在mplsTunnelTable和gmplsTunnelTable中定义的GMPLS隧道的显式路径中使用的显式标签。它不会插入新的跃点，但会为mplsTunnelHopTable中定义的跃点定义新值。
Each row in this table is indexed by the same indexes as in the mplsTunnelHopTable. It is acceptable for some rows in the mplsTunnelHopTable to have corresponding entries in this table and some to have no corresponding entry in this table.
此表中的每一行都由与mplsTunnelHopTable中相同的索引索引。mplsTunnelHopTable中的某些行在此表中具有相应的条目，而某些行在此表中没有相应的条目是可以接受的。
The storage type for this entry is given by the value of mplsTunnelHopStorageType in the corresponding entry in the mplsTunnelHopTable.
此条目的存储类型由mplsTunnelHopTable中相应条目中的mplsTunnelHopStorageType值给出。
The row status of an entry in this table is controlled by mplsTunnelHopRowStatus in the corresponding entry in the mplsTunnelHopTable. That is, it is not permitted to create a row
此表中条目的行状态由mplsTunnelHopRowStatus在mplsTunnelHopTable的相应条目中控制。也就是说，不允许创建行
in this table, or to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has the value active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
"
::= { gmplsTeObjects 2 }
in this table, or to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has the value active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
"
::= { gmplsTeObjects 2 }
gmplsTunnelHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents additions to a tunnel hop
defined in mplsTunnelHopEntry. At an ingress to a tunnel, an
entry in this table is created by a network administrator for an
ERLSP to be set up by a signaling protocol. At transit and
egress nodes, an entry in this table may be used to represent the
explicit path instructions received using the signaling
protocol."
INDEX {
mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex
}
::= { gmplsTunnelHopTable 1 }
gmplsTunnelHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents additions to a tunnel hop
defined in mplsTunnelHopEntry. At an ingress to a tunnel, an
entry in this table is created by a network administrator for an
ERLSP to be set up by a signaling protocol. At transit and
egress nodes, an entry in this table may be used to represent the
explicit path instructions received using the signaling
protocol."
INDEX {
mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex
}
::= { gmplsTunnelHopTable 1 }
GmplsTunnelHopEntry ::= SEQUENCE {
gmplsTunnelHopLabelStatuses BITS,
gmplsTunnelHopExplicitForwardLabel Unsigned32,
gmplsTunnelHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelHopExplicitReverseLabel Unsigned32,
gmplsTunnelHopExplicitReverseLabelPtr RowPointer
}
GmplsTunnelHopEntry ::= SEQUENCE {
gmplsTunnelHopLabelStatuses BITS,
gmplsTunnelHopExplicitForwardLabel Unsigned32,
gmplsTunnelHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelHopExplicitReverseLabel Unsigned32,
gmplsTunnelHopExplicitReverseLabelPtr RowPointer
}
gmplsTunnelHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This bitmask indicates the presence of labels indicated by the
gmplsTunnelHopExplicitForwardLabel or
gmplsTunnelHopExplicitForwardLabelPtr, and
gmplsTunnelHopExplicitReverseLabel or
gmplsTunnelHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This bitmask indicates the presence of labels indicated by the
gmplsTunnelHopExplicitForwardLabel or
gmplsTunnelHopExplicitForwardLabelPtr, and
gmplsTunnelHopExplicitReverseLabel or
gmplsTunnelHopExplicitReverseLabelPtr objects.
EverxpelOplelHbtr。
For the Present bits, a set bit indicates that a label is
present for this hop in the route. This allows zero to be a
valid label value."
DEFVAL { { } }
::= { gmplsTunnelHopEntry 1 }
For the Present bits, a set bit indicates that a label is
present for this hop in the route. This allows zero to be a
valid label value."
DEFVAL { { } }
::= { gmplsTunnelHopEntry 1 }
gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If gmplsTunnelHopLabelStatuses object indicates that a Forward
Label is present and gmplsTunnelHopExplicitForwardLabelPtr
contains the value zeroDotZero, then the label to use on this
hop is represented by the value of this object."
::= { gmplsTunnelHopEntry 2 }
gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If gmplsTunnelHopLabelStatuses object indicates that a Forward
Label is present and gmplsTunnelHopExplicitForwardLabelPtr
contains the value zeroDotZero, then the label to use on this
hop is represented by the value of this object."
::= { gmplsTunnelHopEntry 2 }
gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If the gmplsTunnelHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the forward direction.
GMPLSTunnelOpExplicitForwardLabelPtr对象类型语法RowPointer MAX-ACCESS读取创建状态当前描述“如果GMPLSTunnelOplabelStates对象指示存在前向标签，则此对象包含指向另一MIB表（如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针包含要在此向前跳跃上使用的标签的。
If the gmplsTunnelHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExplicitForwardLabel object."
DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 3 }
If the gmplsTunnelHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExplicitForwardLabel object."
DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 3 }
gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the gmplsTunnelHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in
this object encoded as a 32-bit integer."
::= { gmplsTunnelHopEntry 4 }
gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the gmplsTunnelHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in
this object encoded as a 32-bit integer."
::= { gmplsTunnelHopEntry 4 }
gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If the gmplsTunnelHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction.
gmplsTunnelHopExplicitReverseLabelPtr对象类型语法RowPointer MAX-ACCESS读取创建状态当前描述“如果GMPLSTunnelHoplLabelStates对象指示存在反向标签，则此对象包含指向另一MIB表（例如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针包含要在此跃点上反向使用的标签的。
If the gmplsTunnelHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExplicitReverseLabel object."
DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 5 }
If the gmplsTunnelHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelHopExplicitReverseLabel object."
DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 5 }
gmplsTunnelARHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The gmplsTunnelARHopTable sparsely extends the mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate the labels currently in use for a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, as reported by the signaling protocol. It does not insert new hops, but does define new values for hops defined in the mplsTunnelARHopTable.
gmplsTunnelARHopTable GmplsTunnelARHopEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“GMPLSTunnelahoptable稀疏地扩展了MPLS-TE-STD-MIB的MPLSunnelahoptable。它用于指示当前用于mplsTunnelTable和gmplsTunnelTable中定义的GMPLS隧道的标签，如信令协议所报告的。它不会插入新的跃点，但会为mplsTunnelARHopTable中定义的跃点定义新值。
Each row in this table is indexed by the same indexes as in the mplsTunnelARHopTable. It is acceptable for some rows in the mplsTunnelARHopTable to have corresponding entries in this table and some to have no corresponding entry in this table.
此表中的每一行都由与mplsTunnelARHopTable中相同的索引索引。mplsTunnelARHopTable中的某些行在此表中具有相应的条目，而某些行在此表中没有相应的条目是可以接受的。
Note that since the information necessary to build entries within this table is not provided by some signaling protocols and might not be returned in all cases of other signaling protocols, implementation of this table and the mplsTunnelARHopTable is optional. Furthermore, since the information in this table is actually provided by the signaling protocol after the path has been set up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only." REFERENCE "1. Extensions to RSVP for LSP Tunnels, RFC 3209.
注意，由于某些信令协议不提供在该表中构建条目所需的信息，并且在其他信令协议的所有情况下可能不会返回该信息，因此该表和mplsTunnelARHopTable的实现是可选的。此外，由于此表中的信息实际上是在路径设置后由信令协议提供的，因此此表中的条目仅用于观察，因此，此表中的所有变量都是只读的。“参考”1。LSP隧道RSVP的扩展，RFC 3209。
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 3 }
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 3 }
gmplsTunnelARHopEntry OBJECT-TYPE SYNTAX GmplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents additions to a tunnel hop visible in mplsTunnelARHopEntry. An entry is created by the signaling protocol for a signaled ERLSP set up by the signaling protocol.
gmplsTunnelARHopEntry对象类型语法gmplsTunnelARHopEntry MAX-ACCESS不可访问状态当前描述“此表中的一个条目表示添加到MPLSunneLarHopEntry中可见的隧道跃点。一个条目由信令协议为信令协议设置的信令ERLSP创建。
At any node on the LSP (ingress, transit, or egress), this table and the mplsTunnelARHopTable (if the tables are supported and if the signaling protocol is recording actual route information) contain the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the gmplsTunnelHopTable or the gmplsTunnelCHopTable.
在LSP上的任何节点（入口、中转或出口），此表和mplsTunnelARHopTable（如果支持这些表并且信令协议正在记录实际路由信息）包含整个隧道的实际路由。如果信令协议未记录实际路由，此表可能会报告来自gmplsTunnelHopTable或gmplsTunnelCHopTable的信息。
Note that the recording of actual labels is distinct from the
recording of the actual route in some signaling protocols. This
feature is enabled using the gmplsTunnelAttributes object."
INDEX {
mplsTunnelARHopListIndex,
mplsTunnelARHopIndex
}
::= { gmplsTunnelARHopTable 1 }
Note that the recording of actual labels is distinct from the
recording of the actual route in some signaling protocols. This
feature is enabled using the gmplsTunnelAttributes object."
INDEX {
mplsTunnelARHopListIndex,
mplsTunnelARHopIndex
}
::= { gmplsTunnelARHopTable 1 }
GmplsTunnelARHopEntry ::= SEQUENCE {
gmplsTunnelARHopLabelStatuses BITS,
gmplsTunnelARHopExplicitForwardLabel Unsigned32,
gmplsTunnelARHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelARHopExplicitReverseLabel Unsigned32,
gmplsTunnelARHopExplicitReverseLabelPtr RowPointer,
gmplsTunnelARHopProtection BITS
}
GmplsTunnelARHopEntry ::= SEQUENCE {
gmplsTunnelARHopLabelStatuses BITS,
gmplsTunnelARHopExplicitForwardLabel Unsigned32,
gmplsTunnelARHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelARHopExplicitReverseLabel Unsigned32,
gmplsTunnelARHopExplicitReverseLabelPtr RowPointer,
gmplsTunnelARHopProtection BITS
}
gmplsTunnelARHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1),
forwardGlobal(2),
reverseGlobal(3)
}
gmplsTunnelARHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1),
forwardGlobal(2),
reverseGlobal(3)
}
MAX-ACCESS read-only STATUS current DESCRIPTION "This bitmask indicates the presence and status of labels indicated by the gmplsTunnelARHopExplicitForwardLabel or gmplsTunnelARHopExplicitForwardLabelPtr, and gmplsTunnelARHopExplicitReverseLabel or gmplsTunnelARHopExplicitReverseLabelPtr objects.
MAX-ACCESS只读状态当前描述“此位掩码表示gmplsTunnelARHopExplicitForwardLabel或gmplsTunnelARHopExplicitForwardLabelPtr以及GMPLSTunnelarHopExplicitTreeVerseLabel或GMPLSTunnelarHopExplicitTreeVerseLabelPtr对象指示的标签的存在和状态。
For the Present bits, a set bit indicates that a label is present for this hop in the route.
对于当前位，设置位表示路由中此跃点存在标签。
For the Global bits, a set bit indicates that the label comes
from the Global Label Space; a clear bit indicates that this is
a Per-Interface label. A Global bit only has meaning if the
corresponding Present bit is set."
::= { gmplsTunnelARHopEntry 1 }
For the Global bits, a set bit indicates that the label comes
from the Global Label Space; a clear bit indicates that this is
a Per-Interface label. A Global bit only has meaning if the
corresponding Present bit is set."
::= { gmplsTunnelARHopEntry 1 }
gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a
Forward Label is present and
gmplsTunnelARHopExplicitForwardLabelPtr contains the value
zeroDotZero, then the label in use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 2 }
gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a
Forward Label is present and
gmplsTunnelARHopExplicitForwardLabelPtr contains the value
zeroDotZero, then the label in use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 2 }
gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "If the gmplsTunnelARHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label in use on this hop in the forward direction.
gmplsTunnelARHopExplicitForwardLabelPtr对象类型语法RowPointer MAX-ACCESS只读状态当前描述“如果GMPLSTunnelarHopLabelStatus对象指示存在前向标签，则此对象包含指向另一MIB表（如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针包含前进方向上此跃点上使用的标签的。
If the gmplsTunnelARHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitForwardLabel object."
::= { gmplsTunnelARHopEntry 3 }
If the gmplsTunnelARHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitForwardLabel object."
::= { gmplsTunnelARHopEntry 3 }
gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelARHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label in use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 4 }
gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelARHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label in use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 4 }
gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "If the gmplsTunnelARHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label in use on this hop in the reverse direction.
GMPLSTunnelarHopExplicitReterVerseLabelPtr对象类型语法RowPointer MAX-ACCESS只读状态当前描述“如果GMPLSTunnelarHopLabelStatus对象指示存在反向标签，则此对象包含指向另一MIB表（如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针包含此跃点上反向使用的标签的。
If the gmplsTunnelARHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitReverseLabel object."
::= { gmplsTunnelARHopEntry 5 }
If the gmplsTunnelARHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitReverseLabel object."
::= { gmplsTunnelARHopEntry 5 }
gmplsTunnelARHopProtection OBJECT-TYPE
SYNTAX BITS {
localAvailable(0),
localInUse(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Availability and usage of protection on the reported link.
gmplsTunnelARHopProtection OBJECT-TYPE
SYNTAX BITS {
localAvailable(0),
localInUse(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Availability and usage of protection on the reported link.
localAvailable This flag is set to indicate that the link downstream of this node is protected via a local repair mechanism.
localAvailable此标志设置为指示此节点下游的链路通过本地修复机制受到保护。
localInUse This flag is set to indicate that a local repair mechanism is in use to maintain this tunnel (usually in the face of an outage of the link it was previously routed over)." REFERENCE
LocalUse设置此标志表示正在使用本地修复机制来维护此隧道（通常是在之前路由的链路中断时）。“参考
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 4.4.1."
::= { gmplsTunnelARHopEntry 6 }
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 4.4.1."
::= { gmplsTunnelARHopEntry 6 }
gmplsTunnelCHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelCHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The gmplsTunnelCHopTable sparsely extends the mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate additional information about the hops of a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, as computed by a constraint-based routing protocol, based on the mplsTunnelHopTable and the gmplsTunnelHopTable.
gmplsTunnelCHopTable对象类型语法GmplsTunnelCHopEntry MAX-ACCESS的序列不可访问状态当前描述“gmplsTunnelCHopTable稀疏地扩展了MPLS-TE-STD-MIB的mplsTunnelCHopTable。它用于指示有关mplsTunnelTable和gmplsTunnelTable中定义的GMPLS隧道的跃点的附加信息，该跃点由基于约束的路由协议根据mplsTunnelHopTable和gmplsTunnelHopTable计算。
Each row in this table is indexed by the same indexes as in the mplsTunnelCHopTable. It is acceptable for some rows in the mplsTunnelCHopTable to have corresponding entries in this table and some to have no corresponding entry in this table.
此表中的每一行都由与mplsTunnelCHopTable中相同的索引索引。mplsTunnelCHopTable中的某些行在此表中具有相应的条目，而某些行在此表中没有相应的条目是可以接受的。
Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional.
请注意，由于某些LSR可能不支持在此表中生成条目所需的信息，因此此表的实现是可选的。
Furthermore, since the information in this table is actually
provided by a path computation component after the path has been
computed, the entries in this table are provided only for
observation, and hence, all objects in this table are accessible
exclusively as read-only."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
::= { gmplsTeObjects 4 }
Furthermore, since the information in this table is actually
provided by a path computation component after the path has been
computed, the entries in this table are provided only for
observation, and hence, all objects in this table are accessible
exclusively as read-only."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
::= { gmplsTeObjects 4 }
gmplsTunnelCHopEntry OBJECT-TYPE SYNTAX GmplsTunnelCHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents additions to a computed tunnel hop visible in mplsTunnelCHopEntry. An entry is created by a path computation component based on the hops specified in the corresponding mplsTunnelHopTable and gmplsTunnelHopTable.
gmplsTunnelCHopEntry对象类型语法gmplsTunnelCHopEntry MAX-ACCESS不可访问状态当前描述“此表中的条目表示对mplsTunnelCHopEntry中可见的计算隧道跃点的添加。路径计算组件根据相应mplsTunnelHopTable和gmplsTunnelHopTable中指定的跃点创建条目。
At a transit LSR, this table (if the table is supported) MAY contain the path computed by a path computation engine on (or on
在运输LSR中，此表（如果支持该表）可能包含路径计算引擎on（或on）计算的路径
behalf of) the transit LSR."
INDEX {
mplsTunnelCHopListIndex,
mplsTunnelCHopIndex
}
::= { gmplsTunnelCHopTable 1 }
behalf of) the transit LSR."
INDEX {
mplsTunnelCHopListIndex,
mplsTunnelCHopIndex
}
::= { gmplsTunnelCHopTable 1 }
GmplsTunnelCHopEntry ::= SEQUENCE {
gmplsTunnelCHopLabelStatuses BITS,
gmplsTunnelCHopExplicitForwardLabel Unsigned32,
gmplsTunnelCHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelCHopExplicitReverseLabel Unsigned32,
gmplsTunnelCHopExplicitReverseLabelPtr RowPointer
}
GmplsTunnelCHopEntry ::= SEQUENCE {
gmplsTunnelCHopLabelStatuses BITS,
gmplsTunnelCHopExplicitForwardLabel Unsigned32,
gmplsTunnelCHopExplicitForwardLabelPtr RowPointer,
gmplsTunnelCHopExplicitReverseLabel Unsigned32,
gmplsTunnelCHopExplicitReverseLabelPtr RowPointer
}
gmplsTunnelCHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This bitmask indicates the presence of labels indicated by the
gmplsTunnelCHopExplicitForwardLabel or
gmplsTunnelCHopExplicitForwardLabelPtr and
gmplsTunnelCHopExplicitReverseLabel or
gmplsTunnelCHopExplicitReverseLabelPtr objects.
gmplsTunnelCHopLabelStatuses OBJECT-TYPE
SYNTAX BITS {
forwardPresent(0),
reversePresent(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This bitmask indicates the presence of labels indicated by the
gmplsTunnelCHopExplicitForwardLabel or
gmplsTunnelCHopExplicitForwardLabelPtr and
gmplsTunnelCHopExplicitReverseLabel or
gmplsTunnelCHopExplicitReverseLabelPtr objects.
A set bit indicates that a label is present for this hop in the
route, thus allowing zero to be a valid label value."
::= { gmplsTunnelCHopEntry 1 }
A set bit indicates that a label is present for this hop in the
route, thus allowing zero to be a valid label value."
::= { gmplsTunnelCHopEntry 1 }
gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a
Forward Label is present and
gmplsTunnelCHopExplicitForwardLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 2 }
gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a
Forward Label is present and
gmplsTunnelCHopExplicitForwardLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 2 }
gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only
GMPLSTuneLChopExplicitForwardLabelPtr对象类型语法行指针最大访问只读
STATUS current DESCRIPTION "If the gmplsTunnelCHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the forward direction.
STATUS current DESCRIPTION“如果GMPLSTuneLChopLabelStatuses对象指示存在前向标签，则此对象包含指向另一个MIB表（如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针，该MIB表包含要在此前向跃点上使用的标签。
If the gmplsTunnelCHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExplicitForwardLabel object."
::= { gmplsTunnelCHopEntry 3 }
If the gmplsTunnelCHopLabelStatuses object indicates that a
Forward Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExplicitForwardLabel object."
::= { gmplsTunnelCHopEntry 3 }
gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelCHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 4 }
gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the gmplsTunnelCHopLabelStatuses object indicates that a
Reverse Label is present and
gmplsTunnelCHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 4 }
gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "If the gmplsTunnelCHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction.
GMPLSTunnelLChopExplicitiTreverselabelptr对象类型语法RowPointer MAX-ACCESS只读状态当前描述“如果GMPLSTunnelLChopLabelStatus对象指示存在反向标签，则此对象包含指向另一MIB表（例如GMPLS-Label-STD-MIB的gmplsLabelTable）中的行的指针包含要在此跃点上反向使用的标签的。
If the gmplsTunnelCHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExplicitReverseLabel object."
::= { gmplsTunnelCHopEntry 5 }
If the gmplsTunnelCHopLabelStatuses object indicates that a
Reverse Label is present and this object contains the value
zeroDotZero, then the label to use on this hop is found in the
gmplsTunnelCHopExplicitReverseLabel object."
::= { gmplsTunnelCHopEntry 5 }
gmplsTunnelReversePerfTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
gmplsTunnelReversePerfTable GmplsTunnelReversePerfEntry的对象类型语法序列MAX-ACCESS不可访问状态当前描述
"This table augments the gmplsTunnelTable 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.
“此表扩展了gmplsTunnelTable，以提供双向隧道反向的每个隧道数据包性能信息。它可以看作是对MPLSunnelPerfTable的补充，它扩展了MPLSunnelTable。
For links that do not transport packets, these packet counters cannot be maintained. For such links, attempts to read the objects in this table will return noSuchInstance.
对于不传输数据包的链路，无法维护这些数据包计数器。对于此类链接，尝试读取此表中的对象将返回noSuchInstance。
A tunnel can be known to be bidirectional by inspecting the
gmplsTunnelDirection object."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 5 }
A tunnel can be known to be bidirectional by inspecting the
gmplsTunnelDirection object."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 5 }
gmplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the LSR for every
bidirectional GMPLS tunnel where packets are visible to the
LSR."
AUGMENTS { gmplsTunnelEntry }
::= { gmplsTunnelReversePerfTable 1 }
gmplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the LSR for every
bidirectional GMPLS tunnel where packets are visible to the
LSR."
AUGMENTS { gmplsTunnelEntry }
::= { gmplsTunnelReversePerfTable 1 }
GmplsTunnelReversePerfEntry ::= SEQUENCE {
gmplsTunnelReversePerfPackets Counter32,
gmplsTunnelReversePerfHCPackets Counter64,
gmplsTunnelReversePerfErrors Counter32,
gmplsTunnelReversePerfBytes Counter32,
gmplsTunnelReversePerfHCBytes Counter64
}
GmplsTunnelReversePerfEntry ::= SEQUENCE {
gmplsTunnelReversePerfPackets Counter32,
gmplsTunnelReversePerfHCPackets Counter64,
gmplsTunnelReversePerfErrors Counter32,
gmplsTunnelReversePerfBytes Counter32,
gmplsTunnelReversePerfHCBytes Counter64
}
gmplsTunnelReversePerfPackets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of packets forwarded on the tunnel in the reverse direction if it is bidirectional.
gmplsTunnelReversePerfPackets对象类型语法计数器32 MAX-ACCESS只读状态当前描述“隧道上反向转发的数据包数（如果是双向的）。
This object represents the 32-bit value of the least significant part of the 64-bit value if both gmplsTunnelReversePerfHCPackets and this object are returned.
如果同时返回gmplstunneleverseperfhcpackets和此对象，则此对象表示64位值最低有效部分的32位值。
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 1 }
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 1 }
gmplsTunnelReversePerfHCPackets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "High-capacity counter for number of packets forwarded on the tunnel in the reverse direction if it is bidirectional.
gmplsTunnelReversePerfHCPackets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“隧道上反向转发的数据包数的高容量计数器（如果是双向的）。
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 2 }
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 2 }
gmplsTunnelReversePerfErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of errored packets received on the tunnel in the reverse
direction if it is bidirectional. For links that do not
transport packets, this packet counter cannot be maintained. For
such links, this value will return noSuchInstance."
::= { gmplsTunnelReversePerfEntry 3 }
gmplsTunnelReversePerfErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of errored packets received on the tunnel in the reverse
direction if it is bidirectional. For links that do not
transport packets, this packet counter cannot be maintained. For
such links, this value will return noSuchInstance."
::= { gmplsTunnelReversePerfEntry 3 }
gmplsTunnelReversePerfBytes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional.
gmplsTunnelReversePerfBytes对象类型语法计数器32 MAX-ACCESS只读状态当前描述“隧道上反向转发的字节数（如果是双向的）。
This object represents the 32-bit value of the least significant part of the 64-bit value if both gmplsTunnelReversePerfHCBytes and this object are returned.
如果同时返回gmplstunneleverseperfhcbytes和此对象，则此对象表示64位值最低有效部分的32位值。
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 4 }
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 4 }
gmplsTunnelReversePerfHCBytes OBJECT-TYPE SYNTAX Counter64
gmplsTunnelReversePerfHCBytes对象类型语法计数器64
MAX-ACCESS read-only STATUS current
最大访问只读状态当前
DESCRIPTION "High-capacity counter for number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional.
DESCRIPTION“高容量计数器，用于隧道上反向转发的字节数（如果是双向的）。
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 5 }
For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return
noSuchInstance."
::= { gmplsTunnelReversePerfEntry 5 }
gmplsTunnelErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table augments the mplsTunnelTable.
gmplsTunnelErrorTable GmplsTunnelErrorEntry的对象类型语法序列MAX-ACCESS不可访问状态当前描述“此表扩展了MPLSunnelTable。
This table provides per-tunnel information about errors. Errors may be detected locally or reported through the signaling protocol. Error reporting is not exclusive to GMPLS, and this table may be applied in MPLS systems.
此表提供了每个通道有关错误的信息。错误可以在本地检测或通过信令协议报告。错误报告不是GMPLS独有的，此表可应用于MPLS系统。
Entries in this table are not persistent over system resets
or re-initializations of the management system."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 6 }
Entries in this table are not persistent over system resets
or re-initializations of the management system."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812."
::= { gmplsTeObjects 6 }
gmplsTunnelErrorEntry OBJECT-TYPE SYNTAX GmplsTunnelErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by the LSR for every tunnel where error information is visible to the LSR.
gmplsTunnelErrorEntry对象类型语法gmplsTunnelErrorEntry MAX-ACCESS不可访问状态当前描述“此表中的条目由LSR为每个隧道创建，其中错误信息对LSR可见。
Note that systems that read the objects in this table one at a time and do not perform atomic operations to read entire instantiated table rows at once, should, for each conceptual column with valid data, read gmplsTunnelErrorLastTime prior to the other objects in the row and again subsequent to reading the last object of the row. They should verify that the value of gmplsTunnelErrorLastTime did not change and thereby ensure that all data read belongs to the same error event."
请注意，如果系统一次读取一个表中的对象，而不执行原子操作来一次性读取整个实例化表行，则对于每个具有有效数据的概念列，应在读取行中其他对象之前读取GMPLSTuneNelerRorLastTime，并在读取行的最后一个对象之后再次读取GMPLSTuneNelerRorLastTime。他们应该验证gmplsTunnelErrorLastTime的值没有更改，从而确保所有读取的数据都属于同一错误事件。”
AUGMENTS { mplsTunnelEntry }
::= { gmplsTunnelErrorTable 1 }
AUGMENTS { mplsTunnelEntry }
::= { gmplsTunnelErrorTable 1 }
GmplsTunnelErrorEntry ::= SEQUENCE {
gmplsTunnelErrorLastErrorType INTEGER,
gmplsTunnelErrorLastTime TimeStamp,
gmplsTunnelErrorReporterType InetAddressType,
gmplsTunnelErrorReporter InetAddress,
gmplsTunnelErrorCode Unsigned32,
gmplsTunnelErrorSubcode Unsigned32,
gmplsTunnelErrorTLVs OCTET STRING,
gmplsTunnelErrorHelpString SnmpAdminString
}
GmplsTunnelErrorEntry ::= SEQUENCE {
gmplsTunnelErrorLastErrorType INTEGER,
gmplsTunnelErrorLastTime TimeStamp,
gmplsTunnelErrorReporterType InetAddressType,
gmplsTunnelErrorReporter InetAddress,
gmplsTunnelErrorCode Unsigned32,
gmplsTunnelErrorSubcode Unsigned32,
gmplsTunnelErrorTLVs OCTET STRING,
gmplsTunnelErrorHelpString SnmpAdminString
}
gmplsTunnelErrorLastErrorType OBJECT-TYPE
SYNTAX INTEGER {
noError(0),
unknown(1),
protocol(2),
pathComputation(3),
localConfiguration(4),
localResources(5),
localOther(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The nature of the last error. Provides interpretation context
for gmplsTunnelErrorProtocolCode and
gmplsTunnelErrorProtocolSubcode.
gmplsTunnelErrorLastErrorType OBJECT-TYPE
SYNTAX INTEGER {
noError(0),
unknown(1),
protocol(2),
pathComputation(3),
localConfiguration(4),
localResources(5),
localOther(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The nature of the last error. Provides interpretation context
for gmplsTunnelErrorProtocolCode and
gmplsTunnelErrorProtocolSubcode.
A value of noError(0) shows that there is no error associated with this tunnel and means that the other objects in this table entry (conceptual row) have no meaning.
noError（0）的值表示没有与此隧道相关的错误，并且表示此表条目（概念行）中的其他对象没有意义。
A value of unknown(1) shows that there is an error but that no additional information about the cause is known. The error may have been received in a signaled message or generated locally.
值unknown（1）表示存在错误，但不知道有关原因的其他信息。该错误可能已在信号消息中接收或在本地生成。
A value of protocol(2) or pathComputation(3) indicates the cause of an error and identifies an error that has been received through signaling or will itself be signaled.
协议（2）或路径计算（3）的值指示错误的原因，并标识通过信令接收到的错误或其本身将被信令接收到的错误。
A value of localConfiguration(4), localResources(5) or
localOther(6) identifies an error that has been detected
by the local node but that will not be reported through
signaling."
::= { gmplsTunnelErrorEntry 1 }
A value of localConfiguration(4), localResources(5) or
localOther(6) identifies an error that has been detected
by the local node but that will not be reported through
signaling."
::= { gmplsTunnelErrorEntry 1 }
gmplsTunnelErrorLastTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time at which the last error occurred. This is presented as the value of SysUpTime when the error occurred or was reported to this node.
gmplsTunnelErrorLastTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“上次错误发生的时间。这表示为错误发生或报告到此节点时的SysUpTime值。
If gmplsTunnelErrorLastErrorType has the value noError(0), then this object is not valid and should be ignored.
如果gmplsTunnelErrorLastErrorType的值为noError（0），则此对象无效，应忽略。
Note that entries in this table are not persistent over system
resets or re-initializations of the management system."
::= { gmplsTunnelErrorEntry 2 }
Note that entries in this table are not persistent over system
resets or re-initializations of the management system."
::= { gmplsTunnelErrorEntry 2 }
gmplsTunnelErrorReporterType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The address type of the error reported.
gmplsTunnelErrorReporterType对象类型语法InetAddressType MAX-ACCESS只读状态当前描述“报告的错误的地址类型。
This object is used to aid in interpretation of
gmplsTunnelErrorReporter."
::= { gmplsTunnelErrorEntry 3 }
This object is used to aid in interpretation of
gmplsTunnelErrorReporter."
::= { gmplsTunnelErrorEntry 3 }
gmplsTunnelErrorReporter OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The address of the node reporting the last error, or the address of the resource (such as an interface) associated with the error.
gmplsTunnelErrorReporter对象类型语法InetAddress MAX-ACCESS只读状态当前描述“报告上次错误的节点的地址，或与错误关联的资源（如接口）的地址。
If gmplsTunnelErrorLastErrorType has the value noError(0), then this object is not valid and should be ignored.
如果gmplsTunnelErrorLastErrorType的值为noError（0），则此对象无效，应忽略。
If gmplsTunnelErrorLastErrorType has the value unknown(1), localConfiguration(4), localResources(5), or localOther(6), this object MAY contain a zero value.
如果gmplsTunnelErrorLastErrorType的值为unknown（1）、localConfiguration（4）、localResources（5）或localOther（6），则此对象可能包含零值。
This object should be interpreted in the context of the value of the object gmplsTunnelErrorReporterType." REFERENCE "1. Textual Conventions for Internet Network Addresses, RFC 4001, section 4, Usage Hints."
应在对象gmplsTunnelErrorReporterType.“REFERENCE”1的值的上下文中解释此对象。Internet网络地址的文本约定，RFC 4001，第4节，使用提示。”
::= { gmplsTunnelErrorEntry 4 }
::= { gmplsTunnelErrorEntry 4 }
gmplsTunnelErrorCode OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The primary error code associated with the last error.
gmplsTunnelErrorCode对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“与上一个错误关联的主要错误代码。
The interpretation of this error code depends on the value of
gmplsTunnelErrorLastErrorType. If the value of
gmplsTunnelErrorLastErrorType is noError(0), the value of this
object should be 0 and should be ignored. If the value of
gmplsTunnelErrorLastErrorType is protocol(2), the error should
be interpreted in the context of the signaling protocol
identified by the mplsTunnelSignallingProto object."
REFERENCE
"1. Resource ReserVation Protocol -- Version 1 Functional
Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 7.3.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 13.1."
::= { gmplsTunnelErrorEntry 5 }
The interpretation of this error code depends on the value of
gmplsTunnelErrorLastErrorType. If the value of
gmplsTunnelErrorLastErrorType is noError(0), the value of this
object should be 0 and should be ignored. If the value of
gmplsTunnelErrorLastErrorType is protocol(2), the error should
be interpreted in the context of the signaling protocol
identified by the mplsTunnelSignallingProto object."
REFERENCE
"1. Resource ReserVation Protocol -- Version 1 Functional
Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 7.3.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 13.1."
::= { gmplsTunnelErrorEntry 5 }
gmplsTunnelErrorSubcode OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The secondary error code associated with the last error and the
protocol used to signal this tunnel. This value is interpreted
in the context of the value of gmplsTunnelErrorCode.
If the value of gmplsTunnelErrorLastErrorType is noError(0), the
value of this object should be 0 and should be ignored."
REFERENCE
"1. Resource ReserVation Protocol -- Version 1 Functional
Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 7.3.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 13.1. "
::= { gmplsTunnelErrorEntry 6 }
gmplsTunnelErrorSubcode OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The secondary error code associated with the last error and the
protocol used to signal this tunnel. This value is interpreted
in the context of the value of gmplsTunnelErrorCode.
If the value of gmplsTunnelErrorLastErrorType is noError(0), the
value of this object should be 0 and should be ignored."
REFERENCE
"1. Resource ReserVation Protocol -- Version 1 Functional
Specification, RFC 2205, section B.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 7.3.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 13.1. "
::= { gmplsTunnelErrorEntry 6 }
gmplsTunnelErrorTLVs OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..65535)) MAX-ACCESS read-only STATUS current
GMPLSTunenelerrortlvs对象类型语法八位字节字符串（大小（0..65535））最大访问只读状态当前
DESCRIPTION
"The sequence of interface identifier TLVs reported with the
error by the protocol code. The interpretation of the TLVs and
the encoding within the protocol are described in the
references. A value of zero in the first octet indicates that no
TLVs are present."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 8.2."
::= { gmplsTunnelErrorEntry 7 }
DESCRIPTION
"The sequence of interface identifier TLVs reported with the
error by the protocol code. The interpretation of the TLVs and
the encoding within the protocol are described in the
references. A value of zero in the first octet indicates that no
TLVs are present."
REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 8.2."
::= { gmplsTunnelErrorEntry 7 }
gmplsTunnelErrorHelpString OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual string containing information about the last error,
recovery actions, and support advice. If there is no help string,
this object contains a zero length string.
If the value of gmplsTunnelErrorLastErrorType is noError(0),
this object should contain a zero length string, but may contain
a help string indicating that there is no error."
::= { gmplsTunnelErrorEntry 8 }
gmplsTunnelErrorHelpString OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual string containing information about the last error,
recovery actions, and support advice. If there is no help string,
this object contains a zero length string.
If the value of gmplsTunnelErrorLastErrorType is noError(0),
this object should contain a zero length string, but may contain
a help string indicating that there is no error."
::= { gmplsTunnelErrorEntry 8 }
-- -- Notifications --
----通知--
gmplsTunnelDown NOTIFICATION-TYPE
OBJECTS {
mplsTunnelAdminStatus,
mplsTunnelOperStatus,
gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter,
gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode
}
STATUS current
DESCRIPTION
"This notification is generated when an mplsTunnelOperStatus
object for a tunnel in the gmplsTunnelTable is about to enter
the down state from some other state (but not from the
notPresent state). This other state is indicated by the
included value of mplsTunnelOperStatus.
gmplsTunnelDown NOTIFICATION-TYPE
OBJECTS {
mplsTunnelAdminStatus,
mplsTunnelOperStatus,
gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter,
gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode
}
STATUS current
DESCRIPTION
"This notification is generated when an mplsTunnelOperStatus
object for a tunnel in the gmplsTunnelTable is about to enter
the down state from some other state (but not from the
notPresent state). This other state is indicated by the
included value of mplsTunnelOperStatus.
The objects in this notification provide additional error information that indicates the reason why the tunnel has
此通知中的对象提供其他错误信息，指示隧道失败的原因
transitioned to down(2).
转换为向下（2）。
Note that an implementation MUST only issue one of mplsTunnelDown and gmplsTunnelDown for any single event on a single tunnel. If the tunnel has an entry in the gmplsTunnelTable, an implementation SHOULD use gmplsTunnelDown for all tunnel-down events and SHOULD NOT use mplsTunnelDown.
请注意，对于单个隧道上的任何单个事件，实现只能发出mplsTunnelDown和gmplsTunnelDown中的一个。如果隧道在gmplsTunnelTable中有一个条目，则实现应该对所有隧道关闭事件使用gmplsTunnelDown，而不应该使用MPLSunnelDown。
This notification is subject to the control of mplsTunnelNotificationEnable. When that object is set to false(2), then the notification must not be issued.
此通知受mplsTunnelNotificationEnable的控制。当该对象设置为false（2）时，则不得发出通知。
Further, this notification is also subject to mplsTunnelNotificationMaxRate. That object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit some notifications during that period, or may queue them until an appropriate time. The notification rate applies to the sum of all notifications in the MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB modules applied across the whole of the reporting device.
此外，此通知还受mplsTunnelNotificationMaxRate的约束。该对象表示每秒发出的最大通知数。如果事件发生得更快，则实现可能只是无法在该期间发出某些通知，或者可能会将它们排队等待到适当的时间。通知率适用于在整个报告设备上应用的MPLS-TE-STD-MIB和GMPLS-TE-STD-MIB模块中所有通知的总和。
mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown,
mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate
objects are found in MPLS-TE-STD-MIB."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB), RFC 3812."
::= { gmplsTeNotifications 1 }
mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown,
mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate
objects are found in MPLS-TE-STD-MIB."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB), RFC 3812."
::= { gmplsTeNotifications 1 }
gmplsTeGroups
OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
gmplsTeGroups
OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
gmplsTeCompliances
OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
gmplsTeCompliances
OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
-- Compliance requirement for fully compliant implementations.
--完全合规实施的合规性要求。
gmplsTeModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for GMPLS-TE-STD-MIB. Such devices can then be monitored and also be configured using this MIB module.
GMPLSTEModulelCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“为GMPLS-TE-STD-MIB提供完全支持的代理的符合性声明。然后可以使用此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
强制组必须由发起、终止或作为TE LSP/隧道中转的所有LSR实施。此外，根据支持的隧道类型，其他
groups become mandatory as explained below."
如下文所述，团体成为强制性团体。”
MODULE MPLS-TE-STD-MIB -- The MPLS-TE-STD-MIB, RFC 3812
模块MPLS-TE-STD-MIB——MPLS-TE-STD-MIB，RFC 3812
MANDATORY-GROUPS {
mplsTunnelGroup,
mplsTunnelScalarGroup
}
MANDATORY-GROUPS {
mplsTunnelGroup,
mplsTunnelScalarGroup
}
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
gmplsTunnelGroup,
gmplsTunnelScalarGroup
}
MANDATORY-GROUPS {
gmplsTunnelGroup,
gmplsTunnelScalarGroup
}
GROUP gmplsTunnelSignaledGroup DESCRIPTION "This group is mandatory for devices that support signaled tunnel set up, in addition to gmplsTunnelGroup. The following constraints apply: mplsTunnelSignallingProto should be at least read-only returning a value of ldp(2) or rsvp(3)."
GROUP GMPLSTUNNELSignalGroup DESCRIPTION“除了gmplsTunnelGroup外，此组对于支持信号隧道设置的设备是必需的。适用以下约束：MPLSUNNELSignalingProto应至少为只读，返回ldp（2）或rsvp（3）的值。”
GROUP gmplsTunnelOptionalGroup DESCRIPTION "Objects in this group are optional."
GROUP GMPLSTuneLocalGroup DESCRIPTION“此组中的对象是可选的。”
GROUP gmplsTeNotificationGroup DESCRIPTION "This group is mandatory for those implementations that can implement the notifications contained in this group."
GROUP gmplsTeNotificationGroup DESCRIPTION“对于可以实现此组中包含的通知的实现，此组是必需的。”
::= { gmplsTeCompliances 1 }
::= { gmplsTeCompliances 1 }
-- Compliance requirement for read-only compliant implementations.
--只读兼容实现的法规遵从性要求。
gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for GMPLS-TE-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module."
GMPLSTEModuleRadonlyCompliance MODULE-COMPLIANCE STATUS当前描述“仅为GMPLS-TE-STD-MIB提供只读支持的实施的合规性要求。然后可以监控此类设备，但不能使用此MIB模块进行配置。”
MODULE -- this module
模块——这个模块
-- The mandatory group has to be implemented by all LSRs that
-- originate, terminate, or act as transit for TE-LSPs/tunnels.
-- 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.
-- In addition, depending on the type of tunnels supported, other
-- groups become mandatory as explained below.
MANDATORY-GROUPS {
gmplsTunnelGroup,
gmplsTunnelScalarGroup
}
MANDATORY-GROUPS {
gmplsTunnelGroup,
gmplsTunnelScalarGroup
}
GROUP gmplsTunnelSignaledGroup DESCRIPTION "This group is mandatory for devices that support signaled tunnel set up, in addition to gmplsTunnelGroup. The following constraints apply: mplsTunnelSignallingProto should be at least read-only returning a value of ldp(2) or rsvp(3)."
GROUP GMPLSTUNNELSignalGroup DESCRIPTION“除了gmplsTunnelGroup外，此组对于支持信号隧道设置的设备是必需的。适用以下约束：MPLSUNNELSignalingProto应至少为只读，返回ldp（2）或rsvp（3）的值。”
GROUP gmplsTunnelOptionalGroup DESCRIPTION "Objects in this group are optional."
GROUP GMPLSTuneLocalGroup DESCRIPTION“此组中的对象是可选的。”
GROUP gmplsTeNotificationGroup DESCRIPTION "This group is mandatory for those implementations that can implement the notifications contained in this group."
GROUP gmplsTeNotificationGroup DESCRIPTION“对于可以实现此组中包含的通知的实现，此组是必需的。”
OBJECT gmplsTunnelUnnumIf MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSTunenelunnumif MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsTunnelAttributes MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSTunenalat提供最小访问只读描述“不需要写访问”
OBJECT gmplsTunnelLSPEncoding MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelLSPEncoding MIN-ACCESS只读描述“不需要写访问。”
OBJECT gmplsTunnelSwitchingType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelSwitchingType MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsTunnelLinkProtection MIN-ACCESS read-only DESCRIPTION
对象GMPLSTunnelLink保护最小访问只读描述
"Write access is not required."
“不需要写访问权限。”
OBJECT gmplsTunnelGPid MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelGPid MIN-ACCESS只读描述“不需要写访问。”
OBJECT gmplsTunnelSecondary MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelSecondary MIN-ACCESS只读描述“不需要写访问。”
OBJECT gmplsTunnelDirection MIN-ACCESS read-only DESCRIPTION "Only forward(0) is required."
对象gmplsTunnelDirection MIN-ACCESS只读描述“仅需要转发（0）”
OBJECT gmplsTunnelPathComp MIN-ACCESS read-only DESCRIPTION "Only explicit(2) is required."
对象gmplsTunnelPathComp MIN-ACCESS只读描述“仅需要显式（2）”
OBJECT gmplsTunnelUpstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelUpstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelUpstreamNotifyRecipient SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes."
对象GMPLSTuneLupStreamNotifyRecipient语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“只需要实现支持未知（0）、ipv4（1）和ipv6（2）大小。”
OBJECT gmplsTunnelSendResvNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelSendResvNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelSendResvNotifyRecipient SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes."
对象gmplsTunnelSendResvNotifyRecipient语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“实现仅需要支持未知（0）、ipv4（1）和ipv6（2）大小。”
OBJECT gmplsTunnelDownstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
OBJECT gmplsTunnelDownstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support is required."
MIN-ACCESS只读说明“仅需要未知（0）、ipv4（1）和ipv6（2）支持。”
OBJECT gmplsTunnelDownstreamNotifyRecipient SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes."
对象gmplsTunnelDownstreamNotifyRecipient语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“只需要实现支持未知（0）、ipv4（1）和ipv6（2）大小。”
OBJECT gmplsTunnelSendPathNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelSendPathNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelSendPathNotifyRecipient SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes."
对象gmplsTunnelSendPathNotifyRecipient语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“仅支持未知（0）、ipv4（1）和ipv6（2）大小的实现是必需的。”
OBJECT gmplsTunnelAdminStatusFlags MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplstuneneladminstatusflags MIN-ACCESS只读描述“不需要写访问。”
OBJECT gmplsTunnelExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplstunenelextraparamsptr MIN-ACCESS只读描述“不需要写访问。”
-- gmplsTunnelHopLabelStatuses has max access read-only
--GMPLSTunnelHollabelStates具有只读的最大访问权限
OBJECT gmplsTunnelHopExplicitForwardLabel MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelHopExplicitForwardLabel MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsTunnelHopExplicitForwardLabelPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelHopExplicitForwardLabelPtr MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsTunnelHopExplicitReverseLabel MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelHopExplicitReverseLabel MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsTunnelHopExplicitReverseLabelPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsTunnelHopExplicitReverseLabelPtr MIN-ACCESS只读说明“不需要写访问。”
-- gmplsTunnelARHopTable
-- all objects have max access read-only
-- gmplsTunnelARHopTable
-- all objects have max access read-only
-- gmplsTunnelCHopTable
-- all objects have max access read-only
-- gmplsTunnelCHopTable
-- all objects have max access read-only
-- gmplsTunnelReversePerfTable
-- all objects have max access read-only
-- gmplsTunnelReversePerfTable
-- all objects have max access read-only
-- gmplsTunnelErrorTable
-- all objects have max access read-only
-- gmplsTunnelErrorTable
-- all objects have max access read-only
OBJECT gmplsTunnelErrorReporterType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelErrorReporterType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required."
OBJECT gmplsTunnelErrorReporter
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), and ipv6(2)."
::= { gmplsTeCompliances 2 }
OBJECT gmplsTunnelErrorReporter
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), and ipv6(2)."
::= { gmplsTeCompliances 2 }
gmplsTunnelGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelDirection,
gmplsTunnelReversePerfPackets,
gmplsTunnelReversePerfHCPackets,
gmplsTunnelReversePerfErrors,
gmplsTunnelReversePerfBytes,
gmplsTunnelReversePerfHCBytes,
gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorLastTime,
gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter,
gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode,
gmplsTunnelErrorTLVs,
gmplsTunnelErrorHelpString,
gmplsTunnelUnnumIf
}
STATUS current
DESCRIPTION
gmplsTunnelGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelDirection,
gmplsTunnelReversePerfPackets,
gmplsTunnelReversePerfHCPackets,
gmplsTunnelReversePerfErrors,
gmplsTunnelReversePerfBytes,
gmplsTunnelReversePerfHCBytes,
gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorLastTime,
gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter,
gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode,
gmplsTunnelErrorTLVs,
gmplsTunnelErrorHelpString,
gmplsTunnelUnnumIf
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of objects to implement
tunnels. In addition, depending on the type of the tunnels
supported (for example, manually configured or signaled,
persistent or non-persistent, etc.), the
gmplsTunnelSignaledGroup group is mandatory."
::= { gmplsTeGroups 1 }
"Necessary, but not sufficient, set of objects to implement
tunnels. In addition, depending on the type of the tunnels
supported (for example, manually configured or signaled,
persistent or non-persistent, etc.), the
gmplsTunnelSignaledGroup group is mandatory."
::= { gmplsTeGroups 1 }
gmplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelAttributes,
gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType,
gmplsTunnelLinkProtection,
gmplsTunnelGPid,
gmplsTunnelSecondary,
gmplsTunnelPathComp,
gmplsTunnelUpstreamNotifyRecipientType,
gmplsTunnelUpstreamNotifyRecipient,
gmplsTunnelSendResvNotifyRecipientType,
gmplsTunnelSendResvNotifyRecipient,
gmplsTunnelDownstreamNotifyRecipientType,
gmplsTunnelDownstreamNotifyRecipient,
gmplsTunnelSendPathNotifyRecipientType,
gmplsTunnelSendPathNotifyRecipient,
gmplsTunnelAdminStatusFlags,
gmplsTunnelHopLabelStatuses,
gmplsTunnelHopExplicitForwardLabel,
gmplsTunnelHopExplicitForwardLabelPtr,
gmplsTunnelHopExplicitReverseLabel,
gmplsTunnelHopExplicitReverseLabelPtr
}
STATUS current
DESCRIPTION
"Objects needed to implement signaled tunnels."
::= { gmplsTeGroups 2 }
gmplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelAttributes,
gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType,
gmplsTunnelLinkProtection,
gmplsTunnelGPid,
gmplsTunnelSecondary,
gmplsTunnelPathComp,
gmplsTunnelUpstreamNotifyRecipientType,
gmplsTunnelUpstreamNotifyRecipient,
gmplsTunnelSendResvNotifyRecipientType,
gmplsTunnelSendResvNotifyRecipient,
gmplsTunnelDownstreamNotifyRecipientType,
gmplsTunnelDownstreamNotifyRecipient,
gmplsTunnelSendPathNotifyRecipientType,
gmplsTunnelSendPathNotifyRecipient,
gmplsTunnelAdminStatusFlags,
gmplsTunnelHopLabelStatuses,
gmplsTunnelHopExplicitForwardLabel,
gmplsTunnelHopExplicitForwardLabelPtr,
gmplsTunnelHopExplicitReverseLabel,
gmplsTunnelHopExplicitReverseLabelPtr
}
STATUS current
DESCRIPTION
"Objects needed to implement signaled tunnels."
::= { gmplsTeGroups 2 }
gmplsTunnelScalarGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelsConfigured,
gmplsTunnelsActive
}
STATUS current
DESCRIPTION
"Scalar objects needed to implement MPLS tunnels."
::= { gmplsTeGroups 3 }
gmplsTunnelScalarGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelsConfigured,
gmplsTunnelsActive
}
STATUS current
DESCRIPTION
"Scalar objects needed to implement MPLS tunnels."
::= { gmplsTeGroups 3 }
gmplsTunnelOptionalGroup OBJECT-GROUP OBJECTS {
GMPLSTunelopationalGroup对象组对象{
gmplsTunnelExtraParamsPtr,
gmplsTunnelARHopLabelStatuses,
gmplsTunnelARHopExplicitForwardLabel,
gmplsTunnelARHopExplicitForwardLabelPtr,
gmplsTunnelARHopExplicitReverseLabel,
gmplsTunnelARHopExplicitReverseLabelPtr,
gmplsTunnelARHopProtection,
gmplsTunnelCHopLabelStatuses,
gmplsTunnelCHopExplicitForwardLabel,
gmplsTunnelCHopExplicitForwardLabelPtr,
gmplsTunnelCHopExplicitReverseLabel,
gmplsTunnelCHopExplicitReverseLabelPtr
}
STATUS current
DESCRIPTION
"The objects in this group are optional."
::= { gmplsTeGroups 4 }
gmplsTunnelExtraParamsPtr,
gmplsTunnelARHopLabelStatuses,
gmplsTunnelARHopExplicitForwardLabel,
gmplsTunnelARHopExplicitForwardLabelPtr,
gmplsTunnelARHopExplicitReverseLabel,
gmplsTunnelARHopExplicitReverseLabelPtr,
gmplsTunnelARHopProtection,
gmplsTunnelCHopLabelStatuses,
gmplsTunnelCHopExplicitForwardLabel,
gmplsTunnelCHopExplicitForwardLabelPtr,
gmplsTunnelCHopExplicitReverseLabel,
gmplsTunnelCHopExplicitReverseLabelPtr
}
STATUS current
DESCRIPTION
"The objects in this group are optional."
::= { gmplsTeGroups 4 }
gmplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gmplsTunnelDown
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module. None is
mandatory."
::= { gmplsTeGroups 5 }
gmplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gmplsTunnelDown
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module. None is
mandatory."
::= { gmplsTeGroups 5 }
END
终止
It is clear that the MIB modules described in this document in association with MPLS-TE-STD-MIB [RFC3812] are potentially useful for monitoring of MPLS and GMPLS tunnels. These MIB modules can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results.
很明显，本文件中描述的与MPLS-TE-STD-MIB[RFC3812]相关的MIB模块对于监控MPLS和GMPLS隧道可能有用。这些MIB模块还可以用于配置某些对象，任何可以配置的东西都可能被错误配置，从而导致潜在的灾难性后果。
There are a number of management objects defined in these MIB modules with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
在这些MIB模块中定义了许多管理对象，其中MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain objects to provision GMPLS tunnels interfaces at their ingress LSRs. Unauthorized write access to objects in these tables could result in disruption of traffic on the network. This is especially true if a tunnel has already been established.
o gmplsTunnelTable和GMPLSTunnelHolTable共同包含在其入口LSR处提供GMPLS隧道接口的对象。对这些表中的对象进行未经授权的写访问可能会导致网络流量中断。如果已经建立了隧道，则尤其如此。
Some of the readable objects in these MIB modules (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通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and gmplsTunnelErrorTable collectively show the tunnel network topology and status. If an administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable.
o gmplsTunnelTable、gmplsTunnelHopTable、GMPLSTunnelLarHopTable、gmplsTunnelHopTable、GMPLSTunnelVerseperTable和gmplsTunnelErrorTable共同显示隧道网络拓扑和状态。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in these MIB modules.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）这些MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
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实体正确配置为仅授予那些拥有合法权限来获取或设置（更改/创建/删除）对象的主体（用户）访问对象的权限。
This document is a product of the CCAMP Working Group.
本文件是CCAMP工作组的成果。
This document extends [RFC3812]. The authors would like to express their gratitude to all those who worked on that earlier MIB document. Thanks also to Tony Zinicola and Jeremy Crossen for their valuable contributions during an early implementation, and to Lars Eggert,
本文件扩展了[RFC3812]。作者要向所有在早期MIB文档中工作的人表示感谢。还要感谢Tony Zinicola和Jeremy Crossen在早期实施过程中做出的宝贵贡献，以及Lars Eggert，
Baktha Muralidharan, Tom Petch, Dan Romascanu, Dave Thaler, and Bert Wijnen for their review comments.
感谢Baktha Muralidharan、Tom Petch、Dan Romascanu、Dave Thaler和Bert Wijnen的评论。
Special thanks to Joan Cucchiara and Len Nieman for their help with compilation issues.
特别感谢Joan Cucchiara和Len Nieman在编译问题上提供的帮助。
Joan Cucchiara provided a helpful and very thorough MIB Doctor review.
琼·库奇亚拉（Joan Cucchiara）提供了一份有用且非常彻底的MIB医生评估报告。
IANA has rooted MIB objects in the MIB modules contained in this document according to the sections below.
根据以下章节，IANA在本文档中包含的MIB模块中拥有根MIB对象。
IANA has rooted MIB objects in the GMPLS-TE-STD-MIB module contained in this document under the mplsStdMIB subtree.
IANA在本文档中包含的MPLSTDMIB子树下的GMPLS-TE-STD-MIB模块中拥有根MIB对象。
IANA has made the following assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located at http://www.iana.org/assignments/ smi-numbers in table:
IANA在位于的“网络管理参数”注册表中进行了以下分配：http://www.iana.org/assignments/ 表中的smi编号：
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
…mib-2.transmission.mplsStdMIB（1.3.6.1.2.1.10.166）
Decimal Name References
------- ----- ----------
13 GMPLS-TE-STD-MIB [RFC4802]
Decimal Name References
------- ----- ----------
13 GMPLS-TE-STD-MIB [RFC4802]
In the future, GMPLS-related standards-track MIB modules should be rooted under the mplsStdMIB (sic) subtree. IANA has been requested to manage that namespace in the SMI Numbers registry [RFC3811]. New assignments can only be made via a Standards Action as specified in [RFC2434].
将来，GMPLS相关标准跟踪MIB模块应植根于MPLSTDMIB（sic）子树下。已请求IANA在SMI编号注册表[RFC3811]中管理该命名空间。新分配只能通过[RFC2434]中规定的标准行动进行。
Three MIB objects in the GMPLS-TE-STD-MIB module defined in this document (gmplsTunnelLSPEncoding, gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual conventions imported from the IANA-GMPLS-TC-MIB module. The purpose of defining these textual conventions in a separate MIB module is to allow additional values to be defined without having to issue a new version of this document. The Internet Assigned Numbers Authority (IANA) is responsible for the assignment of all Internet numbers; it will administer the values associated with these textual conventions.
本文档中定义的GMPLS-TE-STD-MIB模块中的三个MIB对象（GMPLSTunnellspencode、gmplsTunnelSwitchingType和GMPLSTunnellgpid）使用从IANA-GMPLS-TC-MIB模块导入的文本约定。在单独的MIB模块中定义这些文本约定的目的是允许定义附加值，而无需发布本文档的新版本。互联网分配号码管理局（IANA）负责分配所有互联网号码；它将管理与这些文本约定关联的值。
The rules for additions or changes to IANA-GMPLS-TC-MIB are outlined in the DESCRIPTION clause associated with its MODULE-IDENTITY statement.
IANA-GMPLS-TC-MIB的添加或更改规则在与其模块标识声明相关的描述条款中概述。
The current version of IANA-GMPLS-TC-MIB can be accessed from the IANA home page at: http://www.iana.org/.
IANA-GMPLS-TC-MIB的当前版本可从IANA主页访问，网址为：http://www.iana.org/.
This section provides the base definition of the IANA GMPLS TC MIB module. This MIB module is under the direct control of IANA. Please see the most updated version of this MIB at <http://www.iana.org/assignments/ianagmplstc-mib>.
本节提供IANA GMPLS TC MIB模块的基本定义。该MIB模块由IANA直接控制。请查看此MIB的最新版本，网址为<http://www.iana.org/assignments/ianagmplstc-mib>.
This MIB makes reference to the following documents: [RFC2578], [RFC2579], [RFC3471], [RFC3473], [RFC4202], [RFC4328], and [RFC4783].
本MIB参考了以下文件：[RFC2578]、[RFC2579]、[RFC3471]、[RFC3473]、[RFC4202]、[RFC4328]和[RFC4783]。
IANA assigned an OID to the IANA-GMPLS-TC-MIB module specified in this document as { mib-2 152 }.
IANA为本文档中指定为{MIB-2 152}的IANA-GMPLS-TC-MIB模块分配了一个OID。
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC 2579
从SNMPv2 SMI导入模块标识mib-2——从SNMPv2 TC导入RFC 2578文本约定；——RFC2579
ianaGmpls MODULE-IDENTITY LAST-UPDATED "200702270000Z" -- 27 February 2007 00:00:00 GMT ORGANIZATION "IANA" CONTACT-INFO "Internet Assigned Numbers Authority Postal: 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Tel: +1 310 823 9358 E-Mail: iana@iana.org" DESCRIPTION "Copyright (C) The IETF Trust (2007). The initial version of this MIB module was published in RFC 4802. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html"
ianaGmpls模块标识最后一次更新“200702270000Z”-2007年2月27日00:00:00 GMT组织“IANA”联系方式“互联网分配号码管理局邮政：4676金钟路330号，加利福尼亚州马里纳德雷，邮编90292电话：+1 310 823 9358电子邮件：iana@iana.org“说明”版权（C）IETF信托基金（2007年）。此MIB模块的初始版本已在RFC 4802中发布。有关完整的法律通知，请参阅RFC本身。有关补充信息，请访问：http://www.ietf.org/copyrights/ianamib.html"
REVISION "200702270000Z" -- 27 February 2007 00:00:00 GMT DESCRIPTION "Initial version issued as part of RFC 4802."
修订版“200702270000Z”-2007年2月27日00:00:00 GMT说明“作为RFC 4802的一部分发布的初始版本。”
::= { mib-2 152 }
::= { mib-2 152 }
IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol.
IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol.
This textual convention is strongly tied to the LSP Encoding Types sub-registry of the GMPLS Signaling Parameters registry managed by IANA. Values should be assigned by IANA in step with the LSP Encoding Types sub-registry and using the same registry management rules. However, the actual values used in this textual convention are solely within the purview of IANA and do not necessarily match the values in the LSP Encoding Types sub-registry.
此文本约定与IANA管理的GMPLS信令参数注册表的LSP编码类型子注册表紧密相关。IANA应与LSP编码类型子注册表同步分配值，并使用相同的注册表管理规则。但是，本文本约定中使用的实际值仅在IANA的权限内，不一定与LSP编码类型子注册表中的值匹配。
The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
IANA定期以指定号码RFC或特定于Internet网络管理号码分配的某些衍生版本的形式发布添加了新指定值的文本约定的定义。（可联系IANA获得最新安排。）
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.1."
SYNTAX INTEGER {
tunnelLspNotGmpls(0), -- GMPLS is not in use
tunnelLspPacket(1), -- Packet
tunnelLspEthernet(2), -- Ethernet
tunnelLspAnsiEtsiPdh(3), -- PDH
-- the value 4 is deprecated
tunnelLspSdhSonet(5), -- SDH or SONET
-- the value 6 is deprecated
tunnelLspDigitalWrapper(7), -- Digital Wrapper
tunnelLspLambda(8), -- Lambda
tunnelLspFiber(9), -- Fiber
-- the value 10 is deprecated
tunnelLspFiberChannel(11), -- Fiber Channel
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.1."
SYNTAX INTEGER {
tunnelLspNotGmpls(0), -- GMPLS is not in use
tunnelLspPacket(1), -- Packet
tunnelLspEthernet(2), -- Ethernet
tunnelLspAnsiEtsiPdh(3), -- PDH
-- the value 4 is deprecated
tunnelLspSdhSonet(5), -- SDH or SONET
-- the value 6 is deprecated
tunnelLspDigitalWrapper(7), -- Digital Wrapper
tunnelLspLambda(8), -- Lambda
tunnelLspFiber(9), -- Fiber
-- the value 10 is deprecated
tunnelLspFiberChannel(11), -- Fiber Channel
tunnelDigitalPath(12), -- Digital Path
tunnelOpticalChannel(13) -- Optical Channel
}
tunnelDigitalPath(12), -- Digital Path
tunnelOpticalChannel(13) -- Optical Channel
}
IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol.
IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol.
This textual convention is strongly tied to the Switching Types sub-registry of the GMPLS Signaling Parameters registry managed by IANA. Values should be assigned by IANA in step with the Switching Types sub-registry and using the same registry management rules. However, the actual values used in this textual convention are solely within the purview of IANA and do not necessarily match the values in the Switching Types sub-registry.
该文本约定与IANA管理的GMPLS信令参数注册表的交换类型子注册表紧密相关。IANA应与Switching Types子注册表同步分配值，并使用相同的注册表管理规则。但是，本文本约定中使用的实际值仅在IANA的权限范围内，不一定与开关类型子注册表中的值匹配。
The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
IANA定期以指定号码RFC或特定于Internet网络管理号码分配的某些衍生版本的形式发布添加了新指定值的文本约定的定义。（可联系IANA获得最新安排。）
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Routing Extensions in Support of Generalized
Multi-Protocol Label Switching, RFC 4202, section 2.4.
2. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1."
SYNTAX INTEGER {
unknown(0), -- none of the following, or not known
psc1(1), -- Packet-Switch-Capable 1
psc2(2), -- Packet-Switch-Capable 2
psc3(3), -- Packet-Switch-Capable 3
psc4(4), -- Packet-Switch-Capable 4
l2sc(51), -- Layer-2-Switch-Capable
tdm(100), -- Time-Division-Multiplex
lsc(150), -- Lambda-Switch-Capable
fsc(200) -- Fiber-Switch-Capable
}
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Routing Extensions in Support of Generalized
Multi-Protocol Label Switching, RFC 4202, section 2.4.
2. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1."
SYNTAX INTEGER {
unknown(0), -- none of the following, or not known
psc1(1), -- Packet-Switch-Capable 1
psc2(2), -- Packet-Switch-Capable 2
psc3(3), -- Packet-Switch-Capable 3
psc4(4), -- Packet-Switch-Capable 4
l2sc(51), -- Layer-2-Switch-Capable
tdm(100), -- Time-Division-Multiplex
lsc(150), -- Lambda-Switch-Capable
fsc(200) -- Fiber-Switch-Capable
}
IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol.
IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol.
This textual convention is strongly tied to the Generalized PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters registry managed by IANA. Values should be assigned by IANA in step with the Generalized PIDs (G-PID) sub-registry and using the same registry management rules. However, the actual values used in this textual convention are solely within the purview of IANA and do not necessarily match the values in the Generalized PIDs (G-PID) sub-registry.
该文本约定与IANA管理的GMPLS信令参数注册表的广义PID（G-PID）子注册表紧密相关。IANA应与通用PID（G-PID）子注册表同步分配值，并使用相同的注册表管理规则。然而，本文本约定中使用的实际值仅在IANA的权限范围内，不一定与通用PID（G-PID）子注册表中的值匹配。
The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
IANA定期以指定号码RFC或特定于Internet网络管理号码分配的某些衍生版本的形式发布添加了新指定值的文本约定的定义。（可联系IANA获得最新安排。）
Requests for new values should be made to IANA via email (iana@iana.org)." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 3.1.1. 2. Generalized MPLS Signalling Extensions for G.709 Optical Transport Networks Control, RFC 4328, section 3.1.3." SYNTAX INTEGER { unknown(0), -- unknown or none of the following -- the values 1, 2, 3 and 4 are reserved in RFC 3471 asynchE4(5), asynchDS3T3(6), asynchE3(7), bitsynchE3(8), bytesynchE3(9), asynchDS2T2(10), bitsynchDS2T2(11), reservedByRFC3471first(12), asynchE1(13), bytesynchE1(14), bytesynch31ByDS0(15), asynchDS1T1(16), bitsynchDS1T1(17),
应通过电子邮件向IANA请求新值(iana@iana.org)“参考”1。通用多协议标签交换（GMPLS）信令功能描述，RFC 3471，第3.1.1节。2.G.709光传输网络控制的通用MPLS信令扩展，RFC 4328，第3.1.3节。“语法整数{未知（0），--未知或无以下值--值1、2、3和4保留在RFC 3471 asynchE4（5）、asynchDS3T3（6）、asynchE3（7）、bitsynchE3（8）、bytesynchE3（9）、asynchDS2T2（10）、bitsynchDS2T2（11）中。”，保留YRFC3471First（12）、asynchE1（13）、bytesynchE1（14）、bytesynch31ByDS0（15）、asynchDS1T1（16）、bitsynchDS1T1（17），
bytesynchDS1T1(18), vc1vc12(19), reservedByRFC3471second(20), reservedByRFC3471third(21), ds1SFAsynch(22), ds1ESFAsynch(23), ds3M23Asynch(24), ds3CBitParityAsynch(25), vtLovc(26), stsSpeHovc(27), posNoScramble16BitCrc(28), posNoScramble32BitCrc(29), posScramble16BitCrc(30), posScramble32BitCrc(31), atm(32), ethernet(33), sdhSonet(34), digitalwrapper(36), lambda(37), ansiEtsiPdh(38), lapsSdh(40), fddi(41), dqdb(42), fiberChannel3(43), hdlc(44), ethernetV2DixOnly(45), ethernet802dot3Only(46), g709ODUj(47), g709OTUk(48), g709CBRorCBRa(49), g709CBRb(50), g709BSOT(51), g709BSNT(52), gfpIPorPPP(53), gfpEthernetMAC(54), gfpEthernetPHY(55), g709ESCON(56), g709FICON(57), g709FiberChannel(58) }
字节同步DS1T1（18）、vc1vc12（19）、预留YRFC3471second（20）、预留YRFC3471third（21）、ds1SFAsynch（22）、ds1ESFAsynch（23）、ds3M23Asynch（24）、ds3CBitParityAsynch（25）、vtLovc（26）、stsSpeHovc（27）、posNoScramble16BitCrc（28）、posNoScramble32BitCrc（29）、posScramble16BitCrc（30）、posScramble32BitCrc（31）、atm（32）、以太网（33）、sdhSonet（34），digitalwrapper（36）、lambda（37）、ansiEtsiPdh（38）、lapsSdh（40）、fddi（41）、dqdb（42）、光纤通道3（43）、hdlc（44）、ethernetV2DixOnly（45）、ethernet802dot3Only（46）、g709ODUj（47）、g709OTUk（48）、g709CBRorCBRa（49）、g709CBRb（50）、g709BSOT（51）、g709BSNT（52）、GFPiorppp（53）、gfpEthernetMAC（54）、GFPetherneticon（55）、G709CBRORCON（57），G709光纤通道（58）}
IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471. Setting this object to a non-zero
value will result in the inclusion of the Admin Status
IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471. Setting this object to a non-zero
value will result in the inclusion of the Admin Status
object or TLV on signaling messages.
对象或TLV在信令消息上。
This textual convention is strongly tied to the Administrative Status Information Flags sub-registry of the GMPLS Signaling Parameters registry managed by IANA. Values should be assigned by IANA in step with the Administrative Status Flags sub-registry and using the same registry management rules. However, the actual values used in this textual convention are solely within the purview of IANA and do not necessarily match the values in the Administrative Status Information Flags sub-registry.
该文本约定与IANA管理的GMPLS信令参数注册表的管理状态信息标志子注册表紧密相关。IANA应与管理状态标志子注册表同步分配值，并使用相同的注册表管理规则。但是，本文本约定中使用的实际值仅在IANA的权限范围内，不一定与管理状态信息标志子注册表中的值匹配。
The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
IANA定期以指定号码RFC或特定于Internet网络管理号码分配的某些衍生版本的形式发布添加了新指定值的文本约定的定义。（可联系IANA获得最新安排。）
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section 8.
2. Generalized MPLS Signaling - RSVP-TE Extensions,
RFC 3473, section 7.
3. GMPLS - Communication of Alarm Information,
RFC 4783, section 3.2.1."
SYNTAX BITS {
reflect(0), -- Reflect bit (RFC 3471)
reserved1(1), -- reserved
reserved2(2), -- reserved
reserved3(3), -- reserved
reserved4(4), -- reserved
reserved5(5), -- reserved
reserved6(6), -- reserved
reserved7(7), -- reserved
reserved8(8), -- reserved
reserved9(9), -- reserved
reserved10(10), -- reserved
reserved11(11), -- reserved
reserved12(12), -- reserved
reserved13(13), -- reserved
reserved14(14), -- reserved
reserved15(15), -- reserved
reserved16(16), -- reserved
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section 8.
2. Generalized MPLS Signaling - RSVP-TE Extensions,
RFC 3473, section 7.
3. GMPLS - Communication of Alarm Information,
RFC 4783, section 3.2.1."
SYNTAX BITS {
reflect(0), -- Reflect bit (RFC 3471)
reserved1(1), -- reserved
reserved2(2), -- reserved
reserved3(3), -- reserved
reserved4(4), -- reserved
reserved5(5), -- reserved
reserved6(6), -- reserved
reserved7(7), -- reserved
reserved8(8), -- reserved
reserved9(9), -- reserved
reserved10(10), -- reserved
reserved11(11), -- reserved
reserved12(12), -- reserved
reserved13(13), -- reserved
reserved14(14), -- reserved
reserved15(15), -- reserved
reserved16(16), -- reserved
reserved17(17), -- reserved
reserved18(18), -- reserved
reserved19(19), -- reserved
reserved20(20), -- reserved
reserved21(21), -- reserved
reserved22(22), -- reserved
reserved23(23), -- reserved
reserved24(24), -- reserved
reserved25(25), -- reserved
reserved26(26), -- reserved
reserved27(27), -- Inhibit Alarm bit (RFC 4783)
reserved28(28), -- reserved
testing(29), -- Testing bit (RFC 3473)
administrativelyDown(30), -- Admin down (RFC 3473)
deleteInProgress(31) -- Delete bit (RFC 3473)
}
END
reserved17(17), -- reserved
reserved18(18), -- reserved
reserved19(19), -- reserved
reserved20(20), -- reserved
reserved21(21), -- reserved
reserved22(22), -- reserved
reserved23(23), -- reserved
reserved24(24), -- reserved
reserved25(25), -- reserved
reserved26(26), -- reserved
reserved27(27), -- Inhibit Alarm bit (RFC 4783)
reserved28(28), -- reserved
testing(29), -- Testing bit (RFC 3473)
administrativelyDown(30), -- Admin down (RFC 3473)
deleteInProgress(31) -- Delete bit (RFC 3473)
}
END
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997.
[RFC2205]Braden，R.，Zhang，L.，Berson，S.，Herzog，S.，和S.Jamin，“资源预留协议（RSVP）——第1版功能规范”，RFC 22052997年9月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001.
[RFC3031]Rosen，E.，Viswanathan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月。
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001.
[RFC3209]Awduche，D.，Berger，L.，Gan，D.，Li，T.，Srinivasan，V.，和G.Swallow，“RSVP-TE：LSP隧道RSVP的扩展”，RFC 3209，2001年12月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年12月。
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003.
[RFC3471]Berger，L.“通用多协议标签交换（GMPLS）信令功能描述”，RFC 3471，2003年1月。
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3473]Berger，L.“通用多协议标签交换（GMPLS）信令资源预留协议流量工程（RSVP-TE）扩展”，RFC 3473，2003年1月。
[RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)", RFC 3477, January 2003.
[RFC3477]Kompella，K.和Y.Rekhter，“资源预留协议中未编号链路的信令-流量工程（RSVP-TE）”，RFC 3477，2003年1月。
[RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004.
[RFC3811]Nadeau，T.和J.Cucchiara，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，2004年6月。
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004.
[RFC3812]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”，RFC 3812，2004年6月。
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004.
[RFC3813]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 38132004年6月。
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC3945]Mannie，E.“通用多协议标签交换（GMPLS）体系结构”，RFC 39452004年10月。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 4001，2005年2月。
[RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4202, October 2005.
[RFC4202]Kompella，K.和Y.Rekhter，“支持通用多协议标签交换（GMPLS）的路由扩展”，RFC 4202，2005年10月。
[RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control", RFC 4328, January 2006.
[RFC4328]Papadimitriou，D.，“G.709光传输网络控制的通用多协议标签交换（GMPLS）信令扩展”，RFC 4328，2006年1月。
[RFC4783] Berger, L., "GMPLS - Communication of Alarm Information", RFC 4783, December 2006.
[RFC4783]Berger，L.，“GMPLS-报警信息通信”，RFC 4783，2006年12月。
[RFC4803] Nadeau, T., Ed. and A. Farrel, Ed., "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", RFC 4803, February 2007.
[RFC4803]Nadeau，T.，Ed.和A.Farrel，Ed.，“通用多协议标签交换（GMPLS）标签交换路由器（LSR）管理信息库”，RFC 4803，2007年2月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3472]Ashwood Smith，P.和L.Berger，“基于广义多协议标签交换（GMPLS）信令约束的路由标签分发协议（CR-LDP）扩展”，RFC 3472，2003年1月。
Contact Information
联系方式
Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719
Thomas D.Nadeau Cisco Systems，Inc.马萨诸塞州Boxborough大道1414号，邮编01719
EMail: tnadeau@cisco.com
EMail: tnadeau@cisco.com
Cheenu Srinivasan Bloomberg L.P. 731 Lexington Ave. New York, NY 10022
Cheenu Srinivasan Bloomberg L.P.纽约州纽约市列克星敦大道731号，邮编10022
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Adrian Farrel Old Dog Consulting
阿德里安·法雷尔老狗咨询公司
Phone: +44-(0)-1978-860944
EMail: adrian@olddog.co.uk
Phone: +44-(0)-1978-860944
EMail: adrian@olddog.co.uk
Tim Hall Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK
蒂姆·霍尔数据连接有限公司，英国米德尔塞克斯郡恩菲尔德教堂街100号，EN2 6BQ
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Ed Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK
英国米德尔塞克斯郡恩菲尔德教堂街100号Ed Harrison数据连接有限公司EN2 6BQ
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。