Network Working Group J. Cucchiara
Request for Comments: 3815 Marconi Communications, Inc.
Category: Standards Track H. Sjostrand
ipUnplugged
J. Luciani
Marconi Communications, Inc.
June 2004
Network Working Group J. Cucchiara
Request for Comments: 3815 Marconi Communications, Inc.
Category: Standards Track H. Sjostrand
ipUnplugged
J. Luciani
Marconi Communications, Inc.
June 2004
Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)
多协议标签交换（MPLS）、标签分发协议（LDP）的受管对象定义
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 Internet Society (2004).
版权所有（C）互联网协会（2004年）。
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 the Multiprotocol Label Switching, Label Distribution Protocol (LDP).
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了多协议标签交换的托管对象，即标签分发协议（LDP）。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework. . . . . . . . . . 3
3. Structure of the MIB Modules. . . . . . . . . . . . . . . . . 3
3.1. Overview. . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Future Considerations . . . . . . . . . . . . . . . . . 4
3.3. Interface Indexing. . . . . . . . . . . . . . . . . . . 4
3.4. Differences from the LDP Specification. . . . . . . . . 4
3.5. The MPLS-LDP-STD-MIB Module . . . . . . . . . . . . . . 5
3.5.1. LDP Scalar Objects. . . . . . . . . . . . . . . 5
3.5.2. The LDP Entity Table. . . . . . . . . . . . . . 6
3.5.2.1. Changing Values After Session
Establishment . . . . . . . . . . . . 6
3.5.3. The LDP Entity Statistics Table . . . . . . . . 7
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework. . . . . . . . . . 3
3. Structure of the MIB Modules. . . . . . . . . . . . . . . . . 3
3.1. Overview. . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Future Considerations . . . . . . . . . . . . . . . . . 4
3.3. Interface Indexing. . . . . . . . . . . . . . . . . . . 4
3.4. Differences from the LDP Specification. . . . . . . . . 4
3.5. The MPLS-LDP-STD-MIB Module . . . . . . . . . . . . . . 5
3.5.1. LDP Scalar Objects. . . . . . . . . . . . . . . 5
3.5.2. The LDP Entity Table. . . . . . . . . . . . . . 6
3.5.2.1. Changing Values After Session
Establishment . . . . . . . . . . . . 6
3.5.3. The LDP Entity Statistics Table . . . . . . . . 7
3.5.4. The LDP Peer Table. . . . . . . . . . . . . . . 7
3.5.5. The LDP Session Table . . . . . . . . . . . . . 8
3.5.6. The LDP Session Statistics Table. . . . . . . . 8
3.5.7. The LDP Hello Adjacency Table . . . . . . . . . 8
3.5.8. The LDP LSP Tables. . . . . . . . . . . . . . . 8
3.5.9. The FEC Tables. . . . . . . . . . . . . . . . . 9
3.5.10. The LDP Session Peer Address Table. . . . . . . 9
3.6. LDP Notifications . . . . . . . . . . . . . . . . . . . 9
3.7. LDP Notification Frequency. . . . . . . . . . . . . . . 10
4. MPLS Label Distribution Protocol MIB Definitions. . . . . . . 10
4.1. The MPLS-LDP-ATM-STD-MIB Module . . . . . . . . . . . . 60
4.1.1. The LDP Entity ATM Table. . . . . . . . . . . . 61
4.1.2. The LDP Entity ATM Label Range Table. . . . . . 61
4.1.3. The LDP ATM Session Table . . . . . . . . . . . 61
4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module . . . . . . . . 77
4.2.1. The LDP Entity Frame Relay Table. . . . . . . . 77
4.2.2. The LDP Entity Frame Relay Label Range Table. . 77
4.2.3. The LDP Frame Relay Session Table . . . . . . . 77
4.3. The MPLS-LDP-GENERIC-STD-MIB Module . . . . . . . . . . 91
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 98
6. References. . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.1. Normative References. . . . . . . . . . . . . . . . . . 98
6.2. Informative References. . . . . . . . . . . . . . . . .100
7. Security Considerations . . . . . . . . . . . . . . . . . . .100
7.1. Security Considerations for MPLS-LDP-STD-MIB. . . . . .100
7.2. Security Considerations for MPLS-LDP-ATM-STD-MIB. . . .101
7.3. Security Considerations for
MPLS-LDP-FRAME-RELAY-STD-MIB. . . . . . . . . . . . . .102
7.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB. .103
7.5. Additional Security Considerations. . . . . . . . . . .103
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . .104
8.1. IANA Considerations for MPLS-LDP-STD-MIB. . . . . . . .104
8.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB. . . . . .104
8.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB. .104
8.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB. . . .104
9. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . .105
10. Full Copyright Statement. . . . . . . . . . . . . . . . . . .106
3.5.4. The LDP Peer Table. . . . . . . . . . . . . . . 7
3.5.5. The LDP Session Table . . . . . . . . . . . . . 8
3.5.6. The LDP Session Statistics Table. . . . . . . . 8
3.5.7. The LDP Hello Adjacency Table . . . . . . . . . 8
3.5.8. The LDP LSP Tables. . . . . . . . . . . . . . . 8
3.5.9. The FEC Tables. . . . . . . . . . . . . . . . . 9
3.5.10. The LDP Session Peer Address Table. . . . . . . 9
3.6. LDP Notifications . . . . . . . . . . . . . . . . . . . 9
3.7. LDP Notification Frequency. . . . . . . . . . . . . . . 10
4. MPLS Label Distribution Protocol MIB Definitions. . . . . . . 10
4.1. The MPLS-LDP-ATM-STD-MIB Module . . . . . . . . . . . . 60
4.1.1. The LDP Entity ATM Table. . . . . . . . . . . . 61
4.1.2. The LDP Entity ATM Label Range Table. . . . . . 61
4.1.3. The LDP ATM Session Table . . . . . . . . . . . 61
4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module . . . . . . . . 77
4.2.1. The LDP Entity Frame Relay Table. . . . . . . . 77
4.2.2. The LDP Entity Frame Relay Label Range Table. . 77
4.2.3. The LDP Frame Relay Session Table . . . . . . . 77
4.3. The MPLS-LDP-GENERIC-STD-MIB Module . . . . . . . . . . 91
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 98
6. References. . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.1. Normative References. . . . . . . . . . . . . . . . . . 98
6.2. Informative References. . . . . . . . . . . . . . . . .100
7. Security Considerations . . . . . . . . . . . . . . . . . . .100
7.1. Security Considerations for MPLS-LDP-STD-MIB. . . . . .100
7.2. Security Considerations for MPLS-LDP-ATM-STD-MIB. . . .101
7.3. Security Considerations for
MPLS-LDP-FRAME-RELAY-STD-MIB. . . . . . . . . . . . . .102
7.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB. .103
7.5. Additional Security Considerations. . . . . . . . . . .103
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . .104
8.1. IANA Considerations for MPLS-LDP-STD-MIB. . . . . . . .104
8.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB. . . . . .104
8.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB. .104
8.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB. . . .104
9. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . .105
10. Full Copyright Statement. . . . . . . . . . . . . . . . . . .106
This document defines 4 MIB Modules which together support the configuration and monitoring of the Label Distribution Protocol (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type of Multiprotocol Label Switching (MPLS) protocols described in [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an operator to configure LDP sessions using 3 different Layer 2 media. The Layer 2 media supported by the MIB Modules are Ethernet, ATM and Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035].
本文件定义了4个MIB模块，它们共同支持标签分发协议（LDP）的配置和监控。标签分发协议（LDP）[RFC3036]是[RFC3031]和[RFC3032]中描述的一种多协议标签交换（MPLS）协议。利用所有4个MIB模块，操作员可以使用3种不同的第2层介质配置LDP会话。MIB模块支持的第2层介质为[RFC3036]、[RFC3034]和[RFC3035]中所述的以太网、ATM和帧中继。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
For an introduction to the concepts of MPLS, see [RFC3031]. For further on LDP refer to [RFC3037] and [RFC3215].
有关MPLS概念的介绍，请参见[RFC3031]。有关LDP的更多信息，请参阅[RFC3037]和[RFC3215]。
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]所述。
This section describes the structure of the LDP MIB Modules.
本节介绍LDP MIB模块的结构。
There are 4 MIB Modules in this document. These MIB Modules are the MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD-MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB defines objects which are common to all LDP implementations. The MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB.
本文档中有4个MIB模块。这些MIB模块是MPLS-LDP-STD-MIB、MPLS-LDP-GENERIC-STD-MIB、MPLS-LDP-ATM-STD-MIB和MPLS-LDP-FRAME-RELAY-STD-MIB。MPLS-LDP-STD-MIB定义了所有LDP实现所共有的对象。MPLS-LDP-GENERIC-STD-MIB定义了与MPLS-LDP-STD-MIB一起使用的每平台第2层标签空间对象。MPLS-LDP-ATM-STD-MIB定义了用于MPLS-LDP-STD-MIB的第2层异步传输模式（ATM）对象。MPLS-LDP-FRAME-RELAY-STD-MIB定义了与MPLS-LDP-STD-MIB一起使用的第2层帧中继对象。
The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of the Layer 2 MIB Modules MUST be implemented by an Agent developer on an Label Switching Router (LSR) or Label Edge Router (LER). As an example, if a Label Switching Router (LSR) or Label Edge Router (LER) implementation intends to support LDP utilizing a Layer 2 of Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB Modules MUST implemented. If an LSR/LER implementation intends to support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an LSR/LER implementation intends to support LDP utilizing a Layer 2 of
MPLS-LDP-STD-MIB模块必须由标签交换路由器（LSR）或标签边缘路由器（LER）上的代理开发人员实现，并且第2层MIB模块中至少有一个必须由代理开发人员实现。例如，如果标签交换路由器（LSR）或标签边缘路由器（LER）实现打算支持利用以太网第2层的LDP，则必须实现MPLS-LDP-STD-MIB和MPLS-LDP-GENERIC-STD-MIB模块。如果LSR/LER实现打算支持利用ATM第2层的LDP，则必须实现MPLS-LDP-STD-MIB模块和MPLS-LDP-ATM-MIB模块。如果LSR/LER实现打算支持利用LDP的第2层
FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME-RELAY-STD-MIB Module MUST be implemented. An LDP implementation that utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST support all 4 MIB Modules. Each of the Modules will be discussed in detail in the following sections.
帧中继，则必须实现MPLS-LDP-STD-MIB模块和MPLS-LDP-FRAME-RELAY-STD-MIB模块。使用所有三层2介质（以太网、帧中继、ATM）的LDP实现必须支持所有4个MIB模块。以下各节将详细讨论每个模块。
There are 2 compliance statements for each MIB Module. One compliance statement is for full compliance which allows both configuration and monitoring via SNMP. The other compliance statement is for read-only compliance which allows only monitoring via SNMP.
每个MIB模块有2个符合性声明。一个符合性声明是完全符合性的，它允许通过SNMP进行配置和监控。另一个符合性声明用于只读符合性，它只允许通过SNMP进行监视。
The LDP Specification [RFC3036] does not specify the use of VPNs or multicast for LDP, and thus, objects related to these areas have not been included.
LDP规范[RFC3036]未规定对LDP使用VPN或多播，因此未包括与这些区域相关的对象。
[RFC2684] does not describe VP merge capability and so this feature has not been included.
[RFC2684]未描述VP合并功能，因此未包含此功能。
These areas need to be specified in the LDP Specification or other specifications prior to being added in this or any other MIB document.
在添加到本文件或任何其他MIB文件中之前，需要在LDP规范或其他规范中规定这些区域。
Interface Indexes as specified in [RFC2863] are used in these MIB Modules. The descriptions of the ifIndexes denote which ifIndex is being used. The use of ifIndex is for actual existing connections.
[RFC2863]中规定的接口索引用于这些MIB模块。ifIndex的描述表示正在使用哪个ifIndex。ifIndex用于实际的现有连接。
Currently, there are 3 differences between this specification and the LDP Specification. As described in the Introduction, this document is almost entirely based on the LDP specification. The differences are documented here.
目前，本规范与LDP规范之间存在3个差异。如引言所述，本文档几乎完全基于LDP规范。这里记录了这些差异。
The first difference is that the LDP Entity Table contains some DEFVAL clauses which are not specified explicitly in the LDP Specification. These values, although not documented in the LDP Specification, are widely used by existing LDP MIB implementations and thus, have been adopted within this MPLS-LDP-STD-MIB module. Please note, they can certainly be changed during row creation or a subsequent SET request.
第一个区别是LDP实体表包含一些在LDP规范中没有明确指定的DEFVAL子句。这些值虽然未在LDP规范中记录，但被现有LDP MIB实现广泛使用，因此已在该MPLS-LDP-STD-MIB模块中采用。请注意，它们当然可以在行创建或后续集合请求期间更改。
A second difference is the mplsLdpEntityGenericLRTable in the MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a way to reserve a range of generic labels, does not exist in the LDP Specification. It was added to the MIB due to a request from the working group and because this table was considered useful for reserving a range of generic labels.
第二个区别是MPLS-LDP-GENERIC-STD-MIB模块中的MPLSLDEntityGenericlrTable。该表虽然作为保留一系列通用标签的方式提供，但在LDP规范中不存在。由于工作组的请求以及该表被认为对保留一系列通用标签有用，因此将其添加到MIB中。
The third difference is documented by the TEXTUAL-CONVENTION, MplsAtmVcIdentifier which is in the MPLS-TC-STD-MIB [RFC3811]. This TC was added to restrict vci values to be greater than 31 as described in RFC 3035 [RFC3035].
第三个差异由文本约定MplsAtmVcIdentifier记录，它位于MPLS-TC-STD-MIB[RFC3811]中。如RFC 3035[RFC3035]所述，增加该TC是为了限制vci值大于31。
This MIB Module contains objects which are common to all LDP implementations. This MIB Module MUST always be implemented along with one or more of the Layer 2 MIB Modules. This MIB Module IMPORTS IndexInteger and IndexIntegerNextFree TEXTUAL-CONVENTIONs from [RFC3289], and IMPORTS InetAddressPrefixLength, InetAddressType, InetAddressInetPortNumber TEXTUAL-CONVENTIONs from [RFC3291].
此MIB模块包含所有LDP实现所共有的对象。此MIB模块必须始终与一个或多个第2层MIB模块一起实现。此MIB模块从[RFC3289]导入IndexIntegrater和IndexIntegraterExtFree文本约定，并从[RFC3291]导入InetAddressPrefixLength、InetAddressType、InetAddressInetPortNumber文本约定。
The mplsLdpEntityTable table allows the Label Edge Router (LER) or the Label Switching Router (LSR) to initiate and/or receive requests to establish LDP sessions. As the LDP protocol distributes labels and establishes sessions with Peers most of the tables in this module are populated by the agent as instructed by the LDP protocol. The exception is the mplsFecTable and the mplsLdpLspFecTable which can be configured by the operator to specify Forwarding Equivalence Class information for an LSP.
MPLSLDEntityTable表允许标签边缘路由器（LER）或标签交换路由器（LSR）发起和/或接收建立LDP会话的请求。由于LDP协议分发标签并与对等方建立会话，此模块中的大多数表由代理按照LDP协议的指示填充。例外情况是mplsFecTable和mplsLdpLspFecTable，操作员可以对其进行配置，以指定LSP的转发等价类信息。
Some scalars and each table in the MPLS-LDP-STD-MIB Module are described in the following subsections.
MPLS-LDP-STD-MIB模块中的一些标量和每个表将在以下小节中描述。
There are several scalar objects in the LDP MIB module. The mplsLdpLsrId is a read-only scalar object which reports Label Switching Router's (LSR's) Identifier. This MUST be a globally unique value, such as the 32-bit router ID assigned to the LSR.
LDP MIB模块中有几个标量对象。mplsLdpLsrId是一个只读标量对象，它报告标签交换路由器（LSR）的标识符。这必须是全局唯一的值，例如分配给LSR的32位路由器ID。
The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the LSR is capable of supporting loop detection and if so, which form of loop detection.
MPLSLPLSRLoopDetectionCapable标量对象表示LSR是否能够支持循环检测，如果能够，则表示哪种形式的循环检测。
There are two LastChange scalar objects, mplsLdpEntityLastChange and mplsLdpPeerLastChange. These objects give an indication of there was a change in the number of entries in the table, or if any of the values in the respective tables changed. Please see the object's description for more details.
有两个LastChange标量对象，MPLSLDEntityLastChange和MPLSLDPeerLastChange。这些对象表示表中的条目数发生了变化，或者相应表中的任何值是否发生了变化。有关详细信息，请参见对象的描述。
The mplsLdpEntityIndexNext scalar object is described in the next section.
下一节将介绍MPLSLDEntityIndexNext标量对象。
The MPLS-LDP-STD-MIB provides objects to configure/set-up potential LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used to configure information which is used by the LDP protocol to setup potential LDP Sessions.
MPLS-LDP-STD-MIB提供用于在特定LSR/LER上配置/设置潜在LDP会话的对象。MPLSLDEntityTable用于配置LDP协议用于设置潜在LDP会话的信息。
Each entry/row in this table represents a single LDP Entity. There is no maximum number of LDP Entities specified. However, there is an mplsLdpEntityIndexNext object which should be retrieved by the command generator prior to creating an LDP Entity. If the mplsLdpEntityIndexNext object is zero, this indicates that the LSR/LER is not able to create another LDP Entity at that time.
此表中的每个条目/行表示一个LDP实体。没有指定LDP实体的最大数量。但是，在创建LDP实体之前，命令生成器应该检索MPLSLDEntityIndexNext对象。如果MPLSLDEntityIndexNext对象为零，则表示LSR/LER当时无法创建另一个LDP实体。
One way to manually modify a session's parameters is by using SNMP to change the MIB objects related to that session. Please note, special care should be taken if MIB objects which are used in the MPLS LDP Session Initialization need to be modified. If the modification of any of these MIB variables takes place anytime after the start of session intialization, then the entire session must be halted. Any information learned by that session must be discarded. The objects should then be modified, and session initialization started. Assuming that the configuration was done correctly, then a new session will be created.
手动修改会话参数的一种方法是使用SNMP更改与该会话相关的MIB对象。请注意，如果需要修改MPLS LDP会话初始化中使用的MIB对象，应特别小心。如果在会话初始化开始后的任何时间修改这些MIB变量，则整个会话必须停止。必须丢弃该会话学习到的任何信息。然后应修改对象，并启动会话初始化。假设配置正确完成，则将创建一个新会话。
For example, assume that an operator wishes to change the configuration of a Label Range which is used by a Session that has already been established. The operator should change the mplsLdpEntityAdminStatus to "disable(2)". Setting the mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be torn down (i.e., this will signal to LDP that it should send out tear down messages for that session). Also, all information related to that session should be removed from this MIB by the Agent. This includes Peer information (i.e., relevant row in the mplsPeerTable) and Session statistics (i.e., relevant row in the mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [RFC3813] is implemented and the optional Mapping Table objects are
例如，假设操作员希望更改已建立会话使用的标签范围的配置。操作员应将MPLSLDEntityAdminStatus更改为“禁用（2）”。将MPLSLDEntityAdminStatus设置为“disable（2）”将导致会话中断（即，这将向LDP发出信号，表明它应该为该会话发送中断消息）。此外，代理还应从此MIB中删除与该会话相关的所有信息。这包括对等信息（即mplspertable中的相关行）和会话统计信息（即mplsLdpSessionTable中的相关行）。此外，如果实现了MPLS-LSR-STD-MIB模块[RFC3813]，并且选择了映射表对象
implemented, then all information related to the LSPs in this session should be removed from these MIB modules. [For more information please see the section on "The Mapping Tables".] At this point, the operator could modify the Label Range. Lastly, the operator should set the mplsLdpEntityAdminStatus to "enable(1)". At this point session initialization should occur. The LDP Entity goes through the Session Initialization in order to communicate the new Label Ranges to the Peer and establish new LSPs.
如果已实现，则应从这些MIB模块中删除此会话中与LSP相关的所有信息。[有关更多信息，请参阅“映射表”部分]。此时，操作员可以修改标签范围。最后，操作员应将MPLSLDEntityAdminStatus设置为“启用（1）”。此时应进行会话初始化。LDP实体进行会话初始化，以便将新的标签范围传送给对等方并建立新的LSP。
The mplsLpdEntityStatsTable is a read-only table which contains statistical information related to failed attempts to establish sessions. Each row in this table AUGMENTS an mplsLdpEntityEntry. This table could be used to give insight into how to reconfigure values so that a session could be successfully established. For example, if the mplsLdpEntityStatsSessionRejectedLRErrors Counter object was increasing, then this would indicate that the Label Range (LR) may need to be adjusted.
MPLSLPEntityStatsTable是一个只读表，其中包含与建立会话失败尝试相关的统计信息。此表中的每一行增加一个MPLSLDEntityEntry。此表可用于深入了解如何重新配置值，以便成功建立会话。例如，如果MPLSLDEntityStatsSessionRejectedLRErrors计数器对象正在增加，则这将表明可能需要调整标签范围（LR）。
The mplsLdpPeerTable is a read-only table which contains information about LDP Peers known to LDP Entities. In other words, the Peer information is learned by LDP through initialization or discovery. This table should be populated by the agent as directed by the LDP protocol.
MPLSLDPeerTable是一个只读表，其中包含LDP实体已知的LDP对等点的信息。也就是说，LDP通过初始化或发现来学习对等信息。此表应由LDP协议指示的代理填充。
A row in this table is related to one or more rows in the Hello Adjacency Table and related to a single row in the Session Table. The values in the Peer table are specific to a Peer and may or may not be the same values used in the session. The reason is that the Peer and Entity negotiate certain values. The Entity's values are configured in the mplsLdpEntityTable and the Peer's values are learned (and placed into the mplsLdpPeerTable). The mplsLdpSessionTable shows the values used in establishing the session.
此表中的一行与Hello邻接表中的一行或多行相关，并与会话表中的一行相关。对等表中的值特定于对等，可能与会话中使用的值相同，也可能不同。原因是对等体和实体协商某些值。实体的值在mplsLdpEntityTable中配置，对等方的值被学习（并放入MPLSLDPEERTABLE）。mplsLdpSessionTable显示用于建立会话的值。
One example, of when the Peer's values and the Session's values may differ is with the Peer's Path Limit information. The Peer's Path Limit information is learned from the session initialization phase. The actual value for the Path Vector Limit is the Peer's value and may not be the same value that appears in the session. There could be a mismatch in this value between the Entity and the Peer. In the event of a mismatch, then the session will use the Path Limit set by the Entity (and not the Peer).
对等方的值和会话的值可能不同的一个例子是对等方的路径限制信息。对等方的路径限制信息从会话初始化阶段学习。路径向量限制的实际值是对等方的值，可能与会话中出现的值不同。实体和对等方之间的此值可能不匹配。在不匹配的情况下，会话将使用实体（而不是对等方）设置的路径限制。
The Peer Table information was placed in a separate table from the Session information to allow for a more comprehensive and coherent MIB model.
对等表信息与会话信息放在一个单独的表中，以实现更全面和一致的MIB模型。
The mplsLdpSessionTable is a read-only table. Each entry in this table represents a single session between an LDP Entity and a Peer. The mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry.
mplsLdpSessionTable是一个只读表。此表中的每个条目表示LDP实体和对等实体之间的单个会话。mplsLdpSessionEntry扩展了MPLSLDPeerEntry。
The information in this table is learned during session establishment. NOTE: rows in this table will appear during session intialization.
此表中的信息在会话建立过程中学习。注意：此表中的行将在会话初始化期间显示。
The mplsLdpSessionStatsTable is a read-only table which contains statistical information on sessions. This table AUGMENTS the mplsLdpPeerTable.
mplsLdpSessionStatsTable是一个只读表，其中包含会话的统计信息。此表扩充了MPLSLDPEERTABLE。
This is a table of all adjacencies between all LDP Entities and all LDP Peers. A Session may have one or more adjacencies. A session should not have zero adjacencies, because this indicates that the session has lost contact with the Peer. A session which has zero Hello Adjacencies should be removed.
这是所有LDP实体和所有LDP对等点之间的所有邻接的表。会话可以有一个或多个相邻。会话不应具有零邻接，因为这表示会话已与对等方失去联系。应删除具有零Hello邻接的会话。
The Label Information Base (LIB) contains information about labels learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e., all currently defined MPLS protocols) is represented in the LSR MIB [RFC3813]. The LIB is represented by the LSR MIB's mplsXCTable (mpls Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable models the cross-connection of the incoming label with a specific outgoing label. The mplsInSegmentTable stores the incoming label's information, and the mplsOutSegmentTable stores the outgoing label's information.
标签信息库（LIB）包含有关LSR学习的标签的信息。LDP、CR-LDP和MPLS-RSVP（即所有当前定义的MPLS协议）的LIB在LSR MIB[RFC3813]中表示。LIB由LSR MIB的mplsXCTable（mpls交叉连接表）、mplsInSegmentTable（mpls段内表）和mplsOutSegmentTable（mpls段外表）表示。mplsXCTable为传入标签与特定传出标签的交叉连接建模。mplsInSegmentTable存储传入标签的信息，MPLSOUTSEGENTTable存储传出标签的信息。
The LDP Session that created the LSP and the LSP's (incoming label, outgoing label) pair along with other information is contained in the MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the mplsOutSegmentTable.
创建LSP和LSP（传入标签、传出标签）对的LDP会话以及其他信息包含在MPLS-LSR-STD-MIB模块的mplsXCTable、mplsInSegmentTable和MPLSSoutSegmentTable中。
In order to utilize the MPLS-LSR-STD-MIB module's mplsXCTable, mplsInSegmentTable and mplsOutSegmentTable for LDP LSPs, there needs to be a mechanism to associate LDP sessions with LDP LSPs created as a result of those LDP sessions. The mplsInSegmentLdpLspTable and mplsOutSegmentLdpLspTable in this MIB contain information to find the LDP LSP entries in the mplsInSegmentTable, mplsOutSegmentTable and the mplsXCTable.
为了为LDP LSP利用MPLS-LSR-STD-MIB模块的mplsXCTable、mplsInSegmentTable和MPLSSoutSegmentTable，需要有一种机制将LDP会话与由于这些LDP会话而创建的LDP LSP相关联。此MIB中的MPLSINSegmentLplsPtable和MPLSSoutSegmentLplsPtable包含在mplsInSegmentTable、MPLSSoutSegmentTable和mplsXCTable中查找LDP LSP项的信息。
These two tables, the mplsInSegmentLdpLspTable and mplsOutSegmentLdpLspTable, have been made optional in the conformance section of the MIB. They only need to be supported if the LSR MIBs mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are implemented.
这两个表，即mplsInSegmentLdpLspTable和MPLSOUTSEMENTLDPLSPTABLE，在MIB的一致性部分中是可选的。只有在实现了LSR MIB mplsInSegmentTable、mplsOutSegmentTable和mplsXCTable时，才需要支持它们。
As discussed in the section, "Changing Values after Session Establishment", if a session is torn down, then all the information related to this session, must be removed from the both LDP MIB and, if implemented, from the LSR MIB.
如“会话建立后更改值”一节所述，如果会话被中断，则必须从LDP MIB和LSR MIB（如果实现）中删除与此会话相关的所有信息。
The mplsLdpFecTable is a table which contains FEC (Forwarding Equivalence Class) information. Each entry/row represents a single FEC Element. There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which associates FECs with the LSPs.
mplsLdpFecTable是一个包含FEC（转发等价类）信息的表。每个条目/行表示一个FEC元素。还有一个LDP LSP FEC表MPLSDPLSPFECTABLE，它将FEC与LSP相关联。
The mplsLdpSessionPeerAddrTable is a table which extends the mplsLdpSessionTable. This table is a read-only table which stores Addresses learned after session initialization via Address Message advertisement.
mplsLdpSessionPeerAddrTable是一个扩展mplsLdpSessionTable的表。此表为只读表，存储会话初始化后通过地址消息播发获得的地址。
Currently, there are several notifications which are specific for LDP. These are described in this section. There are no objects which enable or disable notifications from being generated. RFC 3413 [RFC3413] contains MIB modules which can be implemented that will enable or disable these notifications from being generated.
目前，有几种特定于LDP的通知。本节将对其进行描述。没有启用或禁用生成通知的对象。RFC 3413[RFC3413]包含MIB模块，可以实现这些模块，以启用或禁用这些通知的生成。
The mplsLdpInitSessionThresholdExceeded notification indicates to the operator that there may be a misconfigured mplsLdpEntityEntry because the session associated with this Entity is not being established, and the Entity keeps trying to establish the session. A side effect of this situation is that a row in the mplsLdpSessionTable may not be reaching the operational state as indicated by the mplsLdpSessionState object. If the value of
MPLSLDPINITINTSESSIONTHRESHOLDEXCEEDED通知向操作员指示可能存在配置错误的mplsLdpEntityEntry条目，因为未建立与此实体关联的会话，并且该实体一直尝试建立会话。这种情况的一个副作用是，mplsLdpSessionTable中的一行可能未达到mplsLdpSessionState对象所指示的操作状态。如果
mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to specifying the value of infinity for the threshold, and the mplsLdpInitSessionThresholdExceeded notification will never be sent.
MPLSLDEntityInitSessionReshold为0（零），则这等于为阈值指定无穷大的值，并且将永远不会发送MPLSLDInitSessionResholdExcepted通知。
The mplsLdpPathVectorLimitMismatch notification is generated when there is a mismatch in the Path Vector Limits between the Entity and Peer during session initialization. The session uses the value which is configured as the Entity's Path Vector Limit. However, a notification should be generated to indicate that a mismatch occurred. For further details, please see Section 3.5.3 of the LDP Specification [RFC3036].
在会话初始化过程中，当实体和对等方之间的路径向量限制不匹配时，将生成MPLSLPPathVectorLimitMitch通知。会话使用配置为实体路径向量限制的值。但是，应生成一个通知，指示发生了不匹配。有关更多详细信息，请参见LDP规范[RFC3036]第3.5.3节。
The mplsLdpSessionUp and mplsLdpSessionDown notifications are generated when there is an appropriate change in the mplsLdpSessionState object, e.g., when sessions change state (Up to Down for the mplsLdpSessionDown notification, or Down to Up for the mplsLdpSessionUp notification). There was discussion about combining these two notifications into a single notification, however, some NMS applications can utilize two different notifications, rather than having to parse the varbind list of a single notification. For example, the SessionDown is matched to a SessionUp notification more easily by some NMS applications, than having to parse a Varbind list in a SessionChange type of notification.
当mplsLdpSessionState对象中存在适当的更改时，例如，当会话更改状态时（对于mplsLdpSessionDown通知，从上到下，或者对于mplsLdpSessionUp通知，从下到上），将生成mplsLdpSessionUp和mplsLdpSessionDown通知。曾经讨论过将这两个通知合并为一个通知，但是，一些NMS应用程序可以使用两个不同的通知，而不必解析单个通知的varbind列表。例如，与解析SessionChange类型通知中的Varbind列表相比，某些NMS应用程序更容易将SessionDown与SessionUp通知匹配。
LDP Notifications are expected to be few in number when LDP is ubiquitously deployed in a relatively stable network. A notification receiver, e.g., an NMS, that receives these notifications should not be overwhelmed by the frequency of LDP notifications. If this assertion proves to be inaccurate, then a throttling object to throttle these notifications may be added to future versions of the MPLS-LDP-STD-MIB.
当LDP普遍部署在相对稳定的网络中时，LDP通知的数量预计会很少。接收这些通知的通知接收器（例如NMS）不应被LDP通知的频率所淹没。如果这个断言被证明是不准确的，那么可以在未来版本的MPLS-LDP-STD-MIB中添加一个限制这些通知的限制对象。
MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN
MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, Integer32, Counter32, Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
从SNMPv2 SMI--[RFC2578]导入对象类型、模块标识、通知类型、整数32、计数器32、无符号32
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580]
来自SNMPv2 CONF的模块遵从性、对象组、通知组--[RFC2580]
RowStatus, TimeInterval, TruthValue, TimeStamp, StorageType
行状态、时间间隔、真实值、时间戳、存储类型
FROM SNMPv2-TC -- [RFC2579]
来自SNMPv2 TC--[RFC2579]
InetAddressPrefixLength, InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC3291]
INET-ADDRESS-MIB中的InetAddressPrefixLength、InetAddressType、InetAddress、InetPortNumber--[RFC3291]
IndexInteger, IndexIntegerNextFree FROM DIFFSERV-MIB -- [RFC3289]
IndexIntegrater，IndexIntegraterExtFree FROM DIFFSERV-MIB--[RFC3289]
mplsStdMIB, MplsLabelDistributionMethod, MplsLdpIdentifier, MplsLdpLabelType, MplsLspType, MplsLsrIdentifier, MplsRetentionMode FROM MPLS-TC-STD-MIB -- [RFC3811]
来自MPLS-TC-STD-MIB的MPLSTDMIB、MplsLabelDistributionMethod、MPLSLDPDIdentifier、MplsLdpLabelType、MPLSLSSPType、MPLSSRIdentifier、MPLSREtensionMode--[RFC3811]
MplsIndexType FROM MPLS-LSR-STD-MIB; -- [RFC3813]
MPLS-LSR-STD-MIB中的MplsIndexType；--[RFC3813]
mplsLdpStdMIB MODULE-IDENTITY LAST-UPDATED "200406030000Z" -- June 3, 2004 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" CONTACT-INFO
MPLSLDPSTMIB模块标识最后更新的“200406030000Z”-2004年6月3日组织“多协议标签交换（mpls）工作组”联系方式
"Joan Cucchiara (jcucchiara@mindspring.com) Marconi Communications, Inc.
“琼·库奇亚拉(jcucchiara@mindspring.com)马可尼通讯公司。
Hans Sjostrand (hans@ipunplugged.com) ipUnplugged
汉斯·索斯特兰德(hans@ipunplugged.com)拔下插头
James V. Luciani (james_luciani@mindspring.com) Marconi Communications, Inc.
詹姆斯诉卢西亚尼（詹姆斯）_luciani@mindspring.com)马可尼通讯公司。
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net"
MPLS工作组，电子邮件：mpls@uu.net"
DESCRIPTION "Copyright (C) The Internet Society (2004). The initial version of this MIB module was published
描述“版权所有（C）互联网协会（2004）。此MIB模块的初始版本已发布
in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
in RFC 3815. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for the 'Multiprotocol Label Switching, Label Distribution Protocol, LDP' document."
此MIB包含“多协议标签交换、标签分发协议、LDP”文档的托管对象定义。”
REVISION "200406030000Z" -- June 3, 2004 DESCRIPTION "Initial version published as part of RFC 3815."
修订版“200406030000Z”-2004年6月3日描述“作为RFC 3815的一部分发布的初始版本”
::= { mplsStdMIB 4 }
::= { mplsStdMIB 4 }
--****************************************************************
--****************************************************************
mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 }
mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 }
mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 }
mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 }
mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 }
mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 }
--****************************************************************
-- MPLS LDP Objects
--****************************************************************
--****************************************************************
-- MPLS LDP Objects
--****************************************************************
mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 }
mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 }
mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 }
mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 }
--
-- The MPLS Label Distribution Protocol's
-- Label Switching Router Objects
--
--
-- The MPLS Label Distribution Protocol's
-- Label Switching Router Objects
--
mplsLdpLsrId OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Label Switching Router's Identifier."
::= { mplsLdpLsrObjects 1 }
mplsLdpLsrId OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Label Switching Router's Identifier."
::= { mplsLdpLsrObjects 1 }
mplsLdpLsrLoopDetectionCapable OBJECT-TYPE SYNTAX INTEGER { none(1), other(2), hopCount(3), pathVector(4), hopCountAndPathVector(5)
mplsldplsrloopdetectionable对象类型语法整数{none（1），other（2），hopCount（3），pathVector（4），hopCountAndPathVector（5）
} MAX-ACCESS read-only STATUS current DESCRIPTION "A indication of whether this Label Switching Router supports loop detection.
}MAX-ACCESS只读状态当前描述“此标签交换路由器是否支持环路检测的指示。
none(1) -- Loop Detection is not supported on this LSR.
无（1）--此LSR不支持循环检测。
other(2) -- Loop Detection is supported but by a method other than those listed below.
other（2）--支持循环检测，但方法不同于下面列出的方法。
hopCount(3) -- Loop Detection is supported by Hop Count only.
跃点计数（3）——循环检测仅由跃点计数支持。
pathVector(4) -- Loop Detection is supported by Path Vector only.
pathVector（4）--循环检测仅由路径向量支持。
hopCountAndPathVector(5) -- Loop Detection is supported by both Hop Count And Path Vector.
hopCountAndPathVector（5）——跳数和路径向量都支持循环检测。
Since Loop Detection is determined during Session Initialization, an individual session may not be running with loop detection. This object simply gives an indication of whether or not the LSR has the ability to support Loop Detection and which types."
由于循环检测是在会话初始化期间确定的，因此单个会话可能不会使用循环检测运行。该对象只是指示LSR是否有能力支持环路检测以及支持哪种类型。”
::= { mplsLdpLsrObjects 2 }
::= { mplsLdpLsrObjects 2 }
-- -- The MPLS Label Distribution Protocol Entity Objects --
----MPLS标签分发协议实体对象--
mplsLdpEntityLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the most recent addition or deletion of an entry to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or the most recent change in value of any objects in the mplsLdpEntityTable.
MPLSLDPTEntityLastChange对象类型语法时间戳MAX-ACCESS只读状态当前描述“在最近向MPLSLDPTEntityTable/MPLSLDPTEntityStatsTable添加或删除条目时，或在最近更改MPLSLDPTEntityTable中任何对象的值时，系统正常运行时间的值。
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsLdpEntityObjects 1 }
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsLdpEntityObjects 1 }
mplsLdpEntityIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to
be used for mplsLdpEntityIndex when creating
entries in the mplsLdpEntityTable. The value
0 indicates that no unassigned entries are
available."
::= { mplsLdpEntityObjects 2 }
mplsLdpEntityIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to
be used for mplsLdpEntityIndex when creating
entries in the mplsLdpEntityTable. The value
0 indicates that no unassigned entries are
available."
::= { mplsLdpEntityObjects 2 }
mplsLdpEntityTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the
MPLS Label Distribution Protocol Entities which
exist on this Label Switching Router (LSR)
or Label Edge Router (LER)."
::= { mplsLdpEntityObjects 3 }
mplsLdpEntityTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the
MPLS Label Distribution Protocol Entities which
exist on this Label Switching Router (LSR)
or Label Edge Router (LER)."
::= { mplsLdpEntityObjects 3 }
mplsLdpEntityEntry OBJECT-TYPE
SYNTAX MplsLdpEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents an LDP entity.
An entry can be created by a network administrator
or by an SNMP agent as instructed by LDP."
INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex }
::= { mplsLdpEntityTable 1 }
mplsLdpEntityEntry OBJECT-TYPE
SYNTAX MplsLdpEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents an LDP entity.
An entry can be created by a network administrator
or by an SNMP agent as instructed by LDP."
INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex }
::= { mplsLdpEntityTable 1 }
MplsLdpEntityEntry ::= SEQUENCE {
mplsLdpEntityLdpId MplsLdpIdentifier,
mplsLdpEntityIndex IndexInteger,
mplsLdpEntityProtocolVersion Unsigned32,
mplsLdpEntityAdminStatus INTEGER,
mplsLdpEntityOperStatus INTEGER,
mplsLdpEntityTcpPort InetPortNumber,
mplsLdpEntityUdpDscPort InetPortNumber,
MplsLdpEntityEntry ::= SEQUENCE {
mplsLdpEntityLdpId MplsLdpIdentifier,
mplsLdpEntityIndex IndexInteger,
mplsLdpEntityProtocolVersion Unsigned32,
mplsLdpEntityAdminStatus INTEGER,
mplsLdpEntityOperStatus INTEGER,
mplsLdpEntityTcpPort InetPortNumber,
mplsLdpEntityUdpDscPort InetPortNumber,
mplsLdpEntityMaxPduLength Unsigned32, mplsLdpEntityKeepAliveHoldTimer Unsigned32, mplsLdpEntityHelloHoldTimer Unsigned32, mplsLdpEntityInitSessionThreshold Integer32, mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, mplsLdpEntityLabelRetentionMode MplsRetentionMode, mplsLdpEntityPathVectorLimit Integer32, mplsLdpEntityHopCountLimit Integer32, mplsLdpEntityTransportAddrKind INTEGER, mplsLdpEntityTargetPeer TruthValue, mplsLdpEntityTargetPeerAddrType InetAddressType, mplsLdpEntityTargetPeerAddr InetAddress, mplsLdpEntityLabelType MplsLdpLabelType, mplsLdpEntityDiscontinuityTime TimeStamp, mplsLdpEntityStorageType StorageType, mplsLdpEntityRowStatus RowStatus }
mplsLdpEntityMaxPduLength Unsigned32、mplsLdpEntityKeepAliveHoldTimer Unsigned32、mplsLdpEntityHelloHoldTimer Unsigned32、MPLSLDPEntityInitSessionReshold Integer 32、MPLSLDPEntityLabelDistributionMethod、mplsLdpEntityLabelRetentionMode、mplsLdpEntityPathVectorLimit Integer32、，MPLSLDPTEntityHopCountLimit整数32、MPLSLDPTEntityTransportAddRkind整数、MPLSLDPTEntityTargetPeer TruthValue、MPLSLDPTEntityTargetPeeraddrType InetAddressType、MPLSLDPTEntityTargetPeeraddr InetAddressType、MPLSLDPTEntityLabelType、MPLSLDPTEntityInterruptityTime时间戳、MPLSLDPTEntityStorageType StorageType、，mplsLdpEntityRowStatus}
mplsLdpEntityLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP identifier."
REFERENCE
"RFC3036, LDP Specification, Section on LDP Identifiers."
::= { mplsLdpEntityEntry 1 }
mplsLdpEntityLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP identifier."
REFERENCE
"RFC3036, LDP Specification, Section on LDP Identifiers."
::= { mplsLdpEntityEntry 1 }
mplsLdpEntityIndex OBJECT-TYPE SYNTAX IndexInteger MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is used as a secondary index to uniquely identify this row. Before creating a row in this table, the 'mplsLdpEntityIndexNext' object should be retrieved. That value should be used for the value of this index when creating a row in this table. NOTE: if a value of zero (0) is retrieved, that indicates that no rows can be created in this table at this time.
MPLSLDEntityIndex对象类型语法索引集成器MAX-ACCESS不可访问状态当前说明“此索引用作唯一标识此行的辅助索引。在此表中创建行之前，应检索“MPLSLDEntityIndexNext”对象。在该表中创建行时，该值应用于该索引的值。注意：如果检索到的值为零（0），则表示此时无法在此表中创建任何行。
A secondary index (this object) is meaningful to some but not all, LDP implementations. For example an LDP implementation which uses PPP would use this index to differentiate PPP sub-links.
二级索引（这个对象）对一些但不是所有的LDP实现都有意义。例如，使用PPP的LDP实现将使用该索引来区分PPP子链路。
Another way to use this index is to give this the value of ifIndex. However, this is dependant
使用此索引的另一种方法是为其指定ifIndex的值。然而，这取决于
on the implementation."
::= { mplsLdpEntityEntry 2 }
on the implementation."
::= { mplsLdpEntityEntry 2 }
mplsLdpEntityProtocolVersion OBJECT-TYPE SYNTAX Unsigned32(1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The version number of the LDP protocol which will be used in the session initialization message.
MPLSLPentityProtocolVersion对象类型语法Unsigned32（1..65535）MAX-ACCESS read create STATUS current DESCRIPTION“会话初始化消息中将使用的LDP协议的版本号。
Section 3.5.3 in the LDP Specification specifies
that the version of the LDP protocol is negotiated during
session establishment. The value of this object
represents the value that is sent in the initialization
message."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization
Message."
DEFVAL { 1 }
::= { mplsLdpEntityEntry 3 }
Section 3.5.3 in the LDP Specification specifies
that the version of the LDP protocol is negotiated during
session establishment. The value of this object
represents the value that is sent in the initialization
message."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3 Initialization
Message."
DEFVAL { 1 }
::= { mplsLdpEntityEntry 3 }
mplsLdpEntityAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enable(1),
disable(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The administrative status of this LDP Entity.
If this object is changed from 'enable' to 'disable'
and this entity has already attempted to establish
contact with a Peer, then all contact with that
Peer is lost and all information from that Peer
needs to be removed from the MIB. (This implies
that the network management subsystem should clean
up any related entry in the mplsLdpPeerTable. This
further implies that a 'tear-down' for that session
is issued and the session and all information related
to that session cease to exist).
mplsLdpEntityAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enable(1),
disable(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The administrative status of this LDP Entity.
If this object is changed from 'enable' to 'disable'
and this entity has already attempted to establish
contact with a Peer, then all contact with that
Peer is lost and all information from that Peer
needs to be removed from the MIB. (This implies
that the network management subsystem should clean
up any related entry in the mplsLdpPeerTable. This
further implies that a 'tear-down' for that session
is issued and the session and all information related
to that session cease to exist).
At this point the operator is able to change values which are related to this entity.
此时，操作员可以更改与此实体相关的值。
When the admin status is set back to 'enable', then this Entity will attempt to establish a new session with the Peer."
当管理员状态设置回“启用”时，此实体将尝试与对等方建立新会话。“
DEFVAL { enable }
::= { mplsLdpEntityEntry 4 }
DEFVAL { enable }
::= { mplsLdpEntityEntry 4 }
mplsLdpEntityOperStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
enabled(2),
disabled(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of this LDP Entity.
mplsLdpEntityOperStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
enabled(2),
disabled(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of this LDP Entity.
The value of unknown(1) indicates that the
operational status cannot be determined at
this time. The value of unknown should be
a transient condition before changing
to enabled(2) or disabled(3)."
::= { mplsLdpEntityEntry 5 }
The value of unknown(1) indicates that the
operational status cannot be determined at
this time. The value of unknown should be
a transient condition before changing
to enabled(2) or disabled(3)."
::= { mplsLdpEntityEntry 5 }
mplsLdpEntityTcpPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TCP Port for
LDP. The default value is the well-known
value of this port."
REFERENCE
"RFC3036, LDP Specification, Section 3.10, Well-known
Numbers, and Section 3.10.1. UDP and TCP Ports."
DEFVAL { 646 }
::= { mplsLdpEntityEntry 6 }
mplsLdpEntityTcpPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TCP Port for
LDP. The default value is the well-known
value of this port."
REFERENCE
"RFC3036, LDP Specification, Section 3.10, Well-known
Numbers, and Section 3.10.1. UDP and TCP Ports."
DEFVAL { 646 }
::= { mplsLdpEntityEntry 6 }
mplsLdpEntityUdpDscPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP Discovery Port for LDP. The default value is the well-known value for this port." REFERENCE "RFC3036, LDP Specification, Section 2.4.1, Basic Discovery Mechanism, Section 2.4.2, Extended Discovery Mechanism, Section 3.10, Well-known Numbers, and Section 3.10.1.
MPLSLDEntityUDPDSCPort对象类型语法InetPortNumber MAX-ACCESS读取创建状态当前描述“LDP的UDP发现端口。默认值是此端口的已知值。”参考“RFC3036，LDP规范，第2.4.1节，基本发现机制，第2.4.2节，扩展发现机制，第3.10节，已知编号，以及第3.10.1节。
UDP and TCP Ports."
DEFVAL { 646 }
::= { mplsLdpEntityEntry 7 }
UDP and TCP Ports."
DEFVAL { 646 }
::= { mplsLdpEntityEntry 7 }
mplsLdpEntityMaxPduLength OBJECT-TYPE SYNTAX Unsigned32 (256..65535) UNITS "octets" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum PDU Length that is sent in the Common Session Parameters of an Initialization Message. According to the LDP Specification [RFC3036] a value of 255 or less specifies the default maximum length of 4096 octets, this is why the value of this object starts at 256. The operator should explicitly choose the default value (i.e., 4096), or some other value.
MPLSLDEntityMaxPDuleLength对象类型语法Unsigned32（256..65535）单位“八位字节”最大访问读取创建状态当前描述“在初始化消息的公共会话参数中发送的最大PDU长度。根据LDP规范[RFC3036]255或更小的值指定默认最大长度4096个八位字节，这就是为什么此对象的值从256开始。运算符应显式选择默认值（即4096）或其他值。
The receiving LSR MUST calculate the maximum PDU
length for the session by using the smaller of its and
its peer's proposals for Max PDU Length."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3.
Initialization Message."
DEFVAL { 4096 }
::= { mplsLdpEntityEntry 8 }
The receiving LSR MUST calculate the maximum PDU
length for the session by using the smaller of its and
its peer's proposals for Max PDU Length."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3.
Initialization Message."
DEFVAL { 4096 }
::= { mplsLdpEntityEntry 8 }
mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 16-bit integer value which is the proposed keep
alive hold timer for this LDP Entity."
DEFVAL { 40 }
::= { mplsLdpEntityEntry 9 }
mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 16-bit integer value which is the proposed keep
alive hold timer for this LDP Entity."
DEFVAL { 40 }
::= { mplsLdpEntityEntry 9 }
mplsLdpEntityHelloHoldTimer OBJECT-TYPE SYNTAX Unsigned32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The 16-bit integer value which is the proposed Hello hold timer for this LDP Entity. The Hello Hold time in seconds.
MPLSLDEntityHelloHoldTimer对象类型语法Unsigned32（0..65535）单位“秒”最大访问读取创建状态当前描述“16位整数值，它是此LDP实体的建议Hello保持计时器。Hello保持时间以秒为单位。
An LSR maintains a record of Hellos received from potential peers. This object represents the Hold Time in the Common Hello Parameters TLV of the Hello Message.
LSR维护从潜在对等方收到的HELOS记录。此对象表示Hello消息的公共Hello参数TLV中的保持时间。
A value of 0 is a default value and should be interpretted in conjunction with the mplsLdpEntityTargetPeer object.
值0是默认值，应与MPLSLDEntityTargetPeer对象一起解释。
If the value of this object is 0: if the value of the mplsLdpEntityTargetPeer object is false(2), then this specifies that the Hold Time's actual default value is 15 seconds (i.e., the default Hold time for Link Hellos is 15 seconds). Otherwise if the value of the mplsLdpEntityTargetPeer object is true(1), then this specifies that the Hold Time's actual default value is 45 seconds (i.e., the default Hold time for Targeted Hellos is 45 seconds).
如果此对象的值为0：如果MPLSLDEntityTargetPeer对象的值为false（2），则这将指定保持时间的实际默认值为15秒（即，链接Hello的默认保持时间为15秒）。否则，如果MPLSLDEntityTargetPeer对象的值为true（1），则这将指定保持时间的实际默认值为45秒（即，目标Hello的默认保持时间为45秒）。
A value of 65535 means infinite (i.e., wait forever).
值65535表示无限（即永远等待）。
All other values represent the amount of time in
seconds to wait for a Hello Message. Setting the
hold time to a value smaller than 15 is not
recommended, although not forbidden according
to RFC3036."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.2.,
Hello Message."
DEFVAL { 0 }
::= { mplsLdpEntityEntry 10 }
All other values represent the amount of time in
seconds to wait for a Hello Message. Setting the
hold time to a value smaller than 15 is not
recommended, although not forbidden according
to RFC3036."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.2.,
Hello Message."
DEFVAL { 0 }
::= { mplsLdpEntityEntry 10 }
mplsLdpEntityInitSessionThreshold OBJECT-TYPE SYNTAX Integer32(0..100) MAX-ACCESS read-create STATUS current DESCRIPTION "When attempting to establish a session with a given Peer, the given LDP Entity should send out the SNMP notification, 'mplsLdpInitSessionThresholdExceeded', when the number of Session Initialization messages sent exceeds this threshold.
MPLSLDEntityInitSessionReshold对象类型语法整数32（0..100）MAX-ACCESS读取创建状态当前说明“当尝试与给定对等方建立会话时，当发送的会话初始化消息数超过此阈值时，给定LDP实体应发送SNMP通知“MPLSLDPInitSessionResholdExceeded”。
The notification is used to notify an operator when this Entity and its Peer are possibly engaged in an endless sequence of messages as each NAKs the other's
该通知用于通知操作员，当该实体及其对等方可能在一个无休止的消息序列中相互NAK时
Initialization messages with Error Notification messages. Setting this threshold which triggers the notification is one way to notify the operator. The notification should be generated each time this threshold is exceeded and for every subsequent Initialization message which is NAK'd with an Error Notification message after this threshold is exceeded.
带有错误通知消息的初始化消息。设置触发通知的阈值是通知操作员的一种方法。每次超过此阈值时，以及在超过此阈值后与错误通知消息一起出现的每个后续初始化消息，都应生成通知。
A value of 0 (zero) for this object
indicates that the threshold is infinity, thus
the SNMP notification will never be generated."
REFERENCE
"RFC3036, LDP Specification,
Section 2.5.3 Session Initialization."
DEFVAL { 8 }
::= { mplsLdpEntityEntry 11 }
A value of 0 (zero) for this object
indicates that the threshold is infinity, thus
the SNMP notification will never be generated."
REFERENCE
"RFC3036, LDP Specification,
Section 2.5.3 Session Initialization."
DEFVAL { 8 }
::= { mplsLdpEntityEntry 11 }
mplsLdpEntityLabelDistMethod OBJECT-TYPE
SYNTAX MplsLabelDistributionMethod
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
::= { mplsLdpEntityEntry 12 }
mplsLdpEntityLabelDistMethod OBJECT-TYPE
SYNTAX MplsLabelDistributionMethod
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
::= { mplsLdpEntityEntry 12 }
mplsLdpEntityLabelRetentionMode OBJECT-TYPE SYNTAX MplsRetentionMode MAX-ACCESS read-create STATUS current DESCRIPTION "The LDP Entity can be configured to use either conservative or liberal label retention mode.
MPLSLDEntityLabelRetentionMode对象类型语法MplsRetentionMode MAX-ACCESS读取创建状态当前描述“LDP实体可以配置为使用保守或自由标签保留模式。
If the value of this object is conservative(1) then advertized label mappings are retained only if they will be used to forward packets, i.e., if label came from a valid next hop.
如果此对象的值为保守值（1），则仅当广告标签映射将用于转发数据包时（即，如果标签来自有效的下一跳），才会保留广告标签映射。
If the value of this object is liberal(2)
then all advertized label mappings are retained
whether they are from a valid next hop or not."
::= { mplsLdpEntityEntry 13 }
If the value of this object is liberal(2)
then all advertized label mappings are retained
whether they are from a valid next hop or not."
::= { mplsLdpEntityEntry 13 }
mplsLdpEntityPathVectorLimit OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-create
MPLSLPEntityPathVectorLimit对象类型语法整数32（0..255）最大访问读取创建
STATUS current DESCRIPTION "If the value of this object is 0 (zero) then Loop Detection for Path Vectors is disabled.
状态当前描述“如果此对象的值为0（零），则禁用路径向量的循环检测。
Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors is enabled,
and the Path Vector Limit is this value.
Also, the value of the object,
'mplsLdpLsrLoopDetectionCapable', must be set to
either 'pathVector(4)' or 'hopCountAndPathVector(5)',
if this object has a value greater than 0 (zero),
otherwise it is ignored."
REFERENCE
"RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV."
::= { mplsLdpEntityEntry 14 }
Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors is enabled,
and the Path Vector Limit is this value.
Also, the value of the object,
'mplsLdpLsrLoopDetectionCapable', must be set to
either 'pathVector(4)' or 'hopCountAndPathVector(5)',
if this object has a value greater than 0 (zero),
otherwise it is ignored."
REFERENCE
"RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV."
::= { mplsLdpEntityEntry 14 }
mplsLdpEntityHopCountLimit OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is 0 (zero), then Loop Detection using Hop Counters is disabled.
MPLSLDEntityHopCountLimit对象类型语法整数32（0..255）MAX-ACCESS read create STATUS current DESCRIPTION“如果此对象的值为0（零），则禁用使用跃点计数器的循环检测。
If the value of this object is greater than
0 (zero) then Loop Detection using Hop
Counters is enabled, and this object
specifies this Entity's maximum allowable
value for the Hop Count.
Also, the value of the object
mplsLdpLsrLoopDetectionCapable must be set
to either 'hopCount(3)' or
'hopCountAndPathVector(5)' if this object
has a value greater than 0 (zero), otherwise
it is ignored."
DEFVAL { 0 }
::= { mplsLdpEntityEntry 15 }
If the value of this object is greater than
0 (zero) then Loop Detection using Hop
Counters is enabled, and this object
specifies this Entity's maximum allowable
value for the Hop Count.
Also, the value of the object
mplsLdpLsrLoopDetectionCapable must be set
to either 'hopCount(3)' or
'hopCountAndPathVector(5)' if this object
has a value greater than 0 (zero), otherwise
it is ignored."
DEFVAL { 0 }
::= { mplsLdpEntityEntry 15 }
mplsLdpEntityTransportAddrKind OBJECT-TYPE
SYNTAX INTEGER {
interface(1),
loopback(2)
}
MAX-ACCESS read-create
STATUS current
mplsLdpEntityTransportAddrKind OBJECT-TYPE
SYNTAX INTEGER {
interface(1),
loopback(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION "This specifies whether the loopback or interface address is to be used as the transport address in the transport address TLV of the hello message.
DESCRIPTION“指定环回地址或接口地址是否用作hello消息的传输地址TLV中的传输地址。
If the value is interface(1), then the IP address of the interface from which hello messages are sent is used as the transport address in the hello message.
如果该值为interface（1），则发送hello消息的接口的IP地址将用作hello消息中的传输地址。
Otherwise, if the value is loopback(2), then the IP
address of the loopback interface is used as the
transport address in the hello message."
DEFVAL { loopback }
::= { mplsLdpEntityEntry 16 }
Otherwise, if the value is loopback(2), then the IP
address of the loopback interface is used as the
transport address in the hello message."
DEFVAL { loopback }
::= { mplsLdpEntityEntry 16 }
mplsLdpEntityTargetPeer OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If this LDP entity uses targeted peer then set
this to true."
DEFVAL { false }
::= { mplsLdpEntityEntry 17 }
mplsLdpEntityTargetPeer OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If this LDP entity uses targeted peer then set
this to true."
DEFVAL { false }
::= { mplsLdpEntityEntry 17 }
mplsLdpEntityTargetPeerAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the internetwork layer address used for
the Extended Discovery. This object indicates how
the value of mplsLdpEntityTargetPeerAddr is to
be interpreted."
::= { mplsLdpEntityEntry 18 }
mplsLdpEntityTargetPeerAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the internetwork layer address used for
the Extended Discovery. This object indicates how
the value of mplsLdpEntityTargetPeerAddr is to
be interpreted."
::= { mplsLdpEntityEntry 18 }
mplsLdpEntityTargetPeerAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of the internetwork layer address
used for the Extended Discovery. The value of
mplsLdpEntityTargetPeerAddrType specifies how
this address is to be interpreted."
::= { mplsLdpEntityEntry 19 }
mplsLdpEntityTargetPeerAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of the internetwork layer address
used for the Extended Discovery. The value of
mplsLdpEntityTargetPeerAddrType specifies how
this address is to be interpreted."
::= { mplsLdpEntityEntry 19 }
mplsLdpEntityLabelType OBJECT-TYPE SYNTAX MplsLdpLabelType MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the optional parameters for the LDP Initialization Message.
mplsldEntityLabelType对象类型语法mplsldLabelType MAX-ACCESS读取创建状态当前描述”指定LDP初始化消息的可选参数。
If the value is generic(1) then no optional parameters will be sent in the LDP Initialization message associated with this Entity.
如果该值为通用值（1），则与该实体关联的LDP初始化消息中不会发送可选参数。
If the value is atmParameters(2) then a row must be created in the mplsLdpEntityAtmTable, which corresponds to this entry.
如果值为atmParameters（2），则必须在MPLSLDEntityATMTable中创建一行，该行对应于此条目。
If the value is frameRelayParameters(3) then
a row must be created in the
mplsLdpEntityFrameRelayTable, which
corresponds to this entry."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3.,
Initialization Message."
::= { mplsLdpEntityEntry 20 }
If the value is frameRelayParameters(3) then
a row must be created in the
mplsLdpEntityFrameRelayTable, which
corresponds to this entry."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3.,
Initialization Message."
::= { mplsLdpEntityEntry 20 }
mplsLdpEntityDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion
at which any one or more of this entity's counters
suffered a discontinuity. The relevant counters
are the specific instances associated with this
entity of any Counter32 object contained
in the 'mplsLdpEntityStatsTable'. If no such
discontinuities have occurred since the last
re-initialization of the local management
subsystem, then this object contains a zero
value."
::= { mplsLdpEntityEntry 21 }
mplsLdpEntityDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion
at which any one or more of this entity's counters
suffered a discontinuity. The relevant counters
are the specific instances associated with this
entity of any Counter32 object contained
in the 'mplsLdpEntityStatsTable'. If no such
discontinuities have occurred since the last
re-initialization of the local management
subsystem, then this object contains a zero
value."
::= { mplsLdpEntityEntry 21 }
mplsLdpEntityStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current
MPLSLDEntityStorageType对象类型语法StorageType MAX-ACCESS读取创建状态当前
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL{ nonVolatile }
::= { mplsLdpEntityEntry 22 }
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL{ nonVolatile }
::= { mplsLdpEntityEntry 22 }
mplsLdpEntityRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any
time, however, as described in detail in
the section entitled, 'Changing Values After
Session Establishment', and again described
in the DESCRIPTION clause of the
mplsLdpEntityAdminStatus object, if a session
has been initiated with a Peer, changing objects
in this table will wreak havoc with the session
and interrupt traffic. To repeat again:
the recommended procedure is to
set the mplsLdpEntityAdminStatus to down, thereby
explicitly causing a session to be torn down. Then,
change objects in this entry, then set
the mplsLdpEntityAdminStatus to enable,
which enables a new session to be initiated."
::= { mplsLdpEntityEntry 23 }
mplsLdpEntityRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any
time, however, as described in detail in
the section entitled, 'Changing Values After
Session Establishment', and again described
in the DESCRIPTION clause of the
mplsLdpEntityAdminStatus object, if a session
has been initiated with a Peer, changing objects
in this table will wreak havoc with the session
and interrupt traffic. To repeat again:
the recommended procedure is to
set the mplsLdpEntityAdminStatus to down, thereby
explicitly causing a session to be torn down. Then,
change objects in this entry, then set
the mplsLdpEntityAdminStatus to enable,
which enables a new session to be initiated."
::= { mplsLdpEntityEntry 23 }
-- -- The MPLS LDP Entity Statistics Table --
--——MPLS LDP实体统计表--
mplsLdpEntityStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is a read-only table which augments
the mplsLdpEntityTable. The purpose of this
table is to keep statistical information about
the LDP Entities on the LSR."
::= { mplsLdpEntityObjects 4 }
mplsLdpEntityStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is a read-only table which augments
the mplsLdpEntityTable. The purpose of this
table is to keep statistical information about
the LDP Entities on the LSR."
::= { mplsLdpEntityObjects 4 }
mplsLdpEntityStatsEntry OBJECT-TYPE SYNTAX MplsLdpEntityStatsEntry
MPLSLDEntityStatEntry对象类型语法MPLSLDEntityStatEntry
MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in this table contains statistical information about an LDP Entity. Some counters contained in a row are for fatal errors received during a former LDP Session associated with this entry. For example, an LDP PDU received on a TCP connection during an LDP Session contains a fatal error. That error is counted here, because the session is terminated.
MAX-ACCESS不可访问状态当前描述“此表中的一行包含LDP实体的统计信息。行中包含的某些计数器用于在与此条目关联的前LDP会话期间接收到的致命错误。例如，在LDP会话期间通过TCP连接接收的LDP PDU包含致命错误。由于会话已终止，因此该错误在此处计数。
If the error is NOT fatal (i.e., the Session
remains), then the error is counted in the
mplsLdpSessionStatsEntry."
AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 }
If the error is NOT fatal (i.e., the Session
remains), then the error is counted in the
mplsLdpSessionStatsEntry."
AUGMENTS { mplsLdpEntityEntry }
::= { mplsLdpEntityStatsTable 1 }
MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEntityStatsSessionAttempts Counter32,
mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32,
mplsLdpEntityStatsSessionRejectedAdErrors Counter32,
mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32,
mplsLdpEntityStatsSessionRejectedLRErrors Counter32,
mplsLdpEntityStatsBadLdpIdentifierErrors Counter32,
mplsLdpEntityStatsBadPduLengthErrors Counter32,
mplsLdpEntityStatsBadMessageLengthErrors Counter32,
mplsLdpEntityStatsBadTlvLengthErrors Counter32,
mplsLdpEntityStatsMalformedTlvValueErrors Counter32,
mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32,
mplsLdpEntityStatsShutdownReceivedNotifications Counter32,
mplsLdpEntityStatsShutdownSentNotifications Counter32
}
MplsLdpEntityStatsEntry ::= SEQUENCE {
mplsLdpEntityStatsSessionAttempts Counter32,
mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32,
mplsLdpEntityStatsSessionRejectedAdErrors Counter32,
mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32,
mplsLdpEntityStatsSessionRejectedLRErrors Counter32,
mplsLdpEntityStatsBadLdpIdentifierErrors Counter32,
mplsLdpEntityStatsBadPduLengthErrors Counter32,
mplsLdpEntityStatsBadMessageLengthErrors Counter32,
mplsLdpEntityStatsBadTlvLengthErrors Counter32,
mplsLdpEntityStatsMalformedTlvValueErrors Counter32,
mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32,
mplsLdpEntityStatsShutdownReceivedNotifications Counter32,
mplsLdpEntityStatsShutdownSentNotifications Counter32
}
mplsLdpEntityStatsSessionAttempts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the Session Initialization messages which were sent or received by this LDP Entity and were NAK'd. In other words, this counter counts the number of session initializations that failed.
MPLSLDEntityStatsSessionAttents对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此LDP实体发送或接收且未签名的会话初始化消息的计数。换句话说，此计数器统计失败的会话初始化数。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime."
此计数器值的不连续性可能在管理系统重新初始化时出现，也可能在其他时间出现，如MPLSLDEntityIntercontinuctionTime值所示。”
::= { mplsLdpEntityStatsEntry 1 }
::= { mplsLdpEntityStatsEntry 1 }
mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the Session Rejected/No Hello Error Notification Messages sent or received by this LDP Entity.
MPLSLDEntityStatsSessionRejectedNoHelloErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此LDP实体发送或接收的会话拒绝/无Hello错误通知消息的计数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 2 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 2 }
mplsLdpEntityStatsSessionRejectedAdErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the Session Rejected/Parameters Advertisement Mode Error Notification Messages sent or received by this LDP Entity.
MPLSLDEntityStatsSessionRejectedDerrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此LDP实体发送或接收的会话拒绝/参数播发模式错误通知消息的计数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 3 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 3 }
mplsLdpEntityStatsSessionRejectedMaxPduErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the Session Rejected/Parameters
MPLSLDEntityStatsSessionRejectedMaxPDuerrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“会话被拒绝的计数/参数”
Max Pdu Length Error Notification Messages sent or received by this LDP Entity.
此LDP实体发送或接收的最大Pdu长度错误通知消息。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 4 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 4 }
mplsLdpEntityStatsSessionRejectedLRErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the Session Rejected/Parameters Label Range Notification Messages sent or received by this LDP Entity.
MPLSLDEntityStatsSessionRejectedLRErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此LDP实体发送或接收的会话拒绝/参数标签范围通知消息的计数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 5 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 5 }
mplsLdpEntityStatsBadLdpIdentifierErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Bad LDP Identifier Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDPTEntityStatsBaddldpIdentifierErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的坏LDP标识符致命错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 6 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 6 }
mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Bad PDU Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsBadPDulengErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的错误PDU长度致命错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 7 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 7 }
mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Bad Message Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsBadMessageLengtherRors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的错误消息长度致命错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 8 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 8 }
mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Bad TLV Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsBadtlvLengtherRors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的错误TLV长度致命错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 9 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 9 }
mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Malformed TLV Value Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsMalformedTlvValueErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的格式错误TLV值致命错误数。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime."
此计数器值的不连续性可能在管理系统重新初始化时出现，也可能在其他时间出现，如MPLSLDEntityIntercontinuctionTime值所示。”
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 10 }
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 10 }
mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Session Keep Alive Timer Expired Errors detected by the session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsKeepaliveTimeRexperrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计与此LDP实体关联的会话（过去和现在）检测到的会话保持活动计时器过期错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 11 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.1.2."
::= { mplsLdpEntityStatsEntry 11 }
mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Shutdown Notifications received related to session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsShutdownReceivedNotifications对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计收到的与此LDP实体关联的会话（过去和现在）相关的关机通知数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 12 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 12 }
mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Shutdown Notfications sent related to session(s) (past and present) associated with this LDP Entity.
MPLSLDEntityStatsShutdownsentNotifications对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计发送的与此LDP实体关联的会话（过去和现在）相关的关机通知数。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of
该计数器的值可能在管理系统重新初始化时出现不连续，也可能在管理系统的值指示的其他时间出现不连续
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 13 }
mplsLdpEntityDiscontinuityTime."
::= { mplsLdpEntityStatsEntry 13 }
-- -- The MPLS LDP Peer Table --
----MPLS LDP对等表--
mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 }
mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 }
mplsLdpPeerLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most
recent addition or deletion to/from the
mplsLdpPeerTable/mplsLdpSessionTable."
::= { mplsLdpSessionObjects 1 }
mplsLdpPeerLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most
recent addition or deletion to/from the
mplsLdpPeerTable/mplsLdpSessionTable."
::= { mplsLdpSessionObjects 1 }
mplsLdpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about LDP peers known by Entities in
the mplsLdpEntityTable. The information in this table
is based on information from the Entity-Peer interaction
during session initialization but is not appropriate
for the mplsLdpSessionTable, because objects in this
table may or may not be used in session establishment."
::= { mplsLdpSessionObjects 2 }
mplsLdpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about LDP peers known by Entities in
the mplsLdpEntityTable. The information in this table
is based on information from the Entity-Peer interaction
during session initialization but is not appropriate
for the mplsLdpSessionTable, because objects in this
table may or may not be used in session establishment."
::= { mplsLdpSessionObjects 2 }
mplsLdpPeerEntry OBJECT-TYPE
SYNTAX MplsLdpPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single Peer which is related
to a Session. This table is augmented by
the mplsLdpSessionTable."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId }
::= { mplsLdpPeerTable 1 }
mplsLdpPeerEntry OBJECT-TYPE
SYNTAX MplsLdpPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single Peer which is related
to a Session. This table is augmented by
the mplsLdpSessionTable."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId }
::= { mplsLdpPeerTable 1 }
MplsLdpPeerEntry ::= SEQUENCE {
mplsLdpPeerLdpId MplsLdpIdentifier,
mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod,
MplsLdpPeerEntry ::= SEQUENCE {
mplsLdpPeerLdpId MplsLdpIdentifier,
mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod,
mplsLdpPeerPathVectorLimit Integer32, mplsLdpPeerTransportAddrType InetAddressType, mplsLdpPeerTransportAddr InetAddress }
MPLSLPpeerPathVectorLimit整数32，MPLSLPpeerTransportAddrType InetAddressType，MPLSLPpeerTransportAddr InetAddress}
mplsLdpPeerLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP identifier of this LDP Peer."
::= { mplsLdpPeerEntry 1 }
mplsLdpPeerLdpId OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The LDP identifier of this LDP Peer."
::= { mplsLdpPeerEntry 1 }
mplsLdpPeerLabelDistMethod OBJECT-TYPE
SYNTAX MplsLabelDistributionMethod
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
::= { mplsLdpPeerEntry 2 }
mplsLdpPeerLabelDistMethod OBJECT-TYPE
SYNTAX MplsLabelDistributionMethod
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For any given LDP session, the method of
label distribution must be specified."
::= { mplsLdpPeerEntry 2 }
mplsLdpPeerPathVectorLimit OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "If the value of this object is 0 (zero) then Loop Dection for Path Vectors for this Peer is disabled.
MPLSLPpeerPathVectorLimit对象类型语法整数32（0..255）MAX-ACCESS只读状态当前说明“如果此对象的值为0（零），则禁用此对等方路径向量的循环检测。
Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors for this
Peer is enabled and the Path Vector Limit is this value."
REFERENCE
"RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV."
::= { mplsLdpPeerEntry 3 }
Otherwise, if this object has a value greater than
zero, then Loop Dection for Path Vectors for this
Peer is enabled and the Path Vector Limit is this value."
REFERENCE
"RFC3036, LDP Specification, Section 2.8 Loop Dection,
Section 3.4.5 Path Vector TLV."
::= { mplsLdpPeerEntry 3 }
mplsLdpPeerTransportAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the Internet address for the mplsLdpPeerTransportAddr object. The LDP specification describes this as being either an IPv4 Transport Address or IPv6 Transport
MPLSLDPeerTransportAddRType对象类型语法InetAddressType MAX-ACCESS只读状态当前描述“MPLSLDPeerTransportAddR对象的Internet地址类型。LDP规范将其描述为IPv4传输地址或IPv6传输地址
Address which is used in opening the LDP session's TCP connection, or if the optional TLV is not present, then this is the IPv4/IPv6 source address for the UPD packet carrying the Hellos.
用于打开LDP会话的TCP连接的地址，或者如果可选TLV不存在，则这是承载Hellos的UPD数据包的IPv4/IPv6源地址。
This object specifies how the value of the
mplsLdpPeerTransportAddr object should be
interpreted."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 4 }
This object specifies how the value of the
mplsLdpPeerTransportAddr object should be
interpreted."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 4 }
mplsLdpPeerTransportAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Internet address advertised by the peer in the Hello Message or the Hello source address.
MPLSLDPeerTransportAddr对象类型语法InetAddress MAX-ACCESS只读状态当前描述“对等方在Hello消息或Hello源地址中播发的Internet地址。
The type of this address is specified by the
value of the mplsLdpPeerTransportAddrType
object."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 5 }
The type of this address is specified by the
value of the mplsLdpPeerTransportAddrType
object."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.2
Transport Connection Establishment and
Section 3.5.2.1 Hello Message Procedures."
::= { mplsLdpPeerEntry 5 }
-- -- The MPLS LDP Sessions Table --
----MPLS LDP会话表--
mplsLdpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Sessions between the LDP Entities
and LDP Peers. This table AUGMENTS the
mplsLdpPeerTable. Each row in this table
represents a single session."
::= { mplsLdpSessionObjects 3 }
mplsLdpSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Sessions between the LDP Entities
and LDP Peers. This table AUGMENTS the
mplsLdpPeerTable. Each row in this table
represents a single session."
::= { mplsLdpSessionObjects 3 }
mplsLdpSessionEntry OBJECT-TYPE SYNTAX MplsLdpSessionEntry
mplsLdpSessionEntry对象类型语法mplsLdpSessionEntry
MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single session between an LDP Entity and LDP Peer. The information contained in a row is read-only.
MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表中的条目表示LDP实体和LDP对等方之间单个会话的信息。行中包含的信息是只读的。
Please note: the Path Vector Limit for the Session is the value which is configured in the corresponding mplsLdpEntityEntry. The Peer's Path Vector Limit is in the mplsLdpPeerPathVectorLimit object in the mplsLdpPeerTable.
请注意：会话的路径向量限制是在相应的MPLSLDEntityEntry中配置的值。对等方的路径向量限制位于MPLSLDPeerTable中的MPLSLDPeerPathVectorLimit对象中。
Values which may differ from those configured are
noted in the objects of this table, the
mplsLdpAtmSessionTable and the
mplsLdpFrameRelaySessionTable. A value will
differ if it was negotiated between the
Entity and the Peer. Values may or may not
be negotiated. For example, if the values
are the same then no negotiation takes place.
If they are negotiated, then they may differ."
AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSessionTable 1 }
Values which may differ from those configured are
noted in the objects of this table, the
mplsLdpAtmSessionTable and the
mplsLdpFrameRelaySessionTable. A value will
differ if it was negotiated between the
Entity and the Peer. Values may or may not
be negotiated. For example, if the values
are the same then no negotiation takes place.
If they are negotiated, then they may differ."
AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSessionTable 1 }
MplsLdpSessionEntry ::= SEQUENCE {
mplsLdpSessionStateLastChange TimeStamp,
mplsLdpSessionState INTEGER,
mplsLdpSessionRole INTEGER,
mplsLdpSessionProtocolVersion Unsigned32,
mplsLdpSessionKeepAliveHoldTimeRem TimeInterval,
mplsLdpSessionKeepAliveTime Unsigned32,
mplsLdpSessionMaxPduLength Unsigned32,
mplsLdpSessionDiscontinuityTime TimeStamp
}
MplsLdpSessionEntry ::= SEQUENCE {
mplsLdpSessionStateLastChange TimeStamp,
mplsLdpSessionState INTEGER,
mplsLdpSessionRole INTEGER,
mplsLdpSessionProtocolVersion Unsigned32,
mplsLdpSessionKeepAliveHoldTimeRem TimeInterval,
mplsLdpSessionKeepAliveTime Unsigned32,
mplsLdpSessionMaxPduLength Unsigned32,
mplsLdpSessionDiscontinuityTime TimeStamp
}
mplsLdpSessionStateLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this
Session entered its current state as
denoted by the mplsLdpSessionState
object."
::= { mplsLdpSessionEntry 1 }
mplsLdpSessionStateLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this
Session entered its current state as
denoted by the mplsLdpSessionState
object."
::= { mplsLdpSessionEntry 1 }
mplsLdpSessionState OBJECT-TYPE
SYNTAX INTEGER {
nonexistent(1),
initialized(2),
openrec(3),
opensent(4),
operational(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current state of the session, all of the
states 1 to 5 are based on the state machine
for session negotiation behavior."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.4,
Initialization State Machine."
::= { mplsLdpSessionEntry 2 }
mplsLdpSessionState OBJECT-TYPE
SYNTAX INTEGER {
nonexistent(1),
initialized(2),
openrec(3),
opensent(4),
operational(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current state of the session, all of the
states 1 to 5 are based on the state machine
for session negotiation behavior."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.4,
Initialization State Machine."
::= { mplsLdpSessionEntry 2 }
mplsLdpSessionRole OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
active(2),
passive(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"During session establishment the LSR/LER takes either
the active role or the passive role based on address
comparisons. This object indicates whether this LSR/LER
was behaving in an active role or passive role during
this session's establishment.
mplsLdpSessionRole OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
active(2),
passive(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"During session establishment the LSR/LER takes either
the active role or the passive role based on address
comparisons. This object indicates whether this LSR/LER
was behaving in an active role or passive role during
this session's establishment.
The value of unknown(1), indicates that the role is not
able to be determined at the present time."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.3.,
Session Initialization"
::= { mplsLdpSessionEntry 3 }
The value of unknown(1), indicates that the role is not
able to be determined at the present time."
REFERENCE
"RFC3036, LDP Specification, Section 2.5.3.,
Session Initialization"
::= { mplsLdpSessionEntry 3 }
mplsLdpSessionProtocolVersion OBJECT-TYPE SYNTAX Unsigned32(1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The version of the LDP Protocol which this session is using. This is the version of
mplsLdpSessionProtocolVersion对象类型语法Unsigned32（1..65535）MAX-ACCESS只读状态当前说明“此会话正在使用的LDP协议的版本。这是的版本
the LDP protocol which has been negotiated
during session initialization."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 4 }
the LDP protocol which has been negotiated
during session initialization."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 4 }
mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The keep alive hold time remaining for
this session."
::= { mplsLdpSessionEntry 5 }
mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The keep alive hold time remaining for
this session."
::= { mplsLdpSessionEntry 5 }
mplsLdpSessionKeepAliveTime OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated KeepAlive Time which represents the amount of seconds between keep alive messages. The mplsLdpEntityKeepAliveHoldTimer related to this Session is the value that was proposed as the KeepAlive Time for this session.
mplsLdpSessionKeepAliveTime对象类型语法无符号32（1..65535）单位“秒”最大访问只读状态当前说明“协商的KeepAlive时间，表示保持活动消息之间的秒数。与此会话相关的MPLSLDEntityKeepAliveHoldTimer是建议用作此会话的KeepAlive时间的值。
This value is negotiated during
session initialization between
the entity's proposed value
(i.e., the value configured in
mplsLdpEntityKeepAliveHoldTimer)
and the peer's proposed
KeepAlive Hold Timer value.
This value is the smaller
of the two proposed values."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 6 }
This value is negotiated during
session initialization between
the entity's proposed value
(i.e., the value configured in
mplsLdpEntityKeepAliveHoldTimer)
and the peer's proposed
KeepAlive Hold Timer value.
This value is the smaller
of the two proposed values."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 6 }
mplsLdpSessionMaxPduLength OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "octets" MAX-ACCESS read-only
MPLSLDPSessionMaxPDuleLength对象类型语法无符号32（1..65535）单位“八位字节”最大访问只读
STATUS current
DESCRIPTION
"The value of maximum allowable length for LDP PDUs for
this session. This value may have been negotiated
during the Session Initialization. This object is
related to the mplsLdpEntityMaxPduLength object. The
mplsLdpEntityMaxPduLength object specifies the requested
LDP PDU length, and this object reflects the negotiated
LDP PDU length between the Entity and
the Peer."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 7 }
STATUS current
DESCRIPTION
"The value of maximum allowable length for LDP PDUs for
this session. This value may have been negotiated
during the Session Initialization. This object is
related to the mplsLdpEntityMaxPduLength object. The
mplsLdpEntityMaxPduLength object specifies the requested
LDP PDU length, and this object reflects the negotiated
LDP PDU length between the Entity and
the Peer."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3,
Initialization Message."
::= { mplsLdpSessionEntry 7 }
mplsLdpSessionDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. The relevant counters are the specific instances associated with this session of any Counter32 object contained in the mplsLdpSessionStatsTable.
mplsLdpSessionDiscontinuityTime对象类型语法时间戳MAX-ACCESS只读状态当前说明“此会话的任何一个或多个计数器最近中断时的sysUpTime值。相关计数器是与mplsLdpSessionStatsTable中包含的任何Counter32对象的此会话相关联的特定实例。
The initial value of this object is the value of sysUpTime when the entry was created in this table.
此对象的初始值是在该表中创建条目时的sysUpTime值。
Also, a command generator can distinguish when a session
between a given Entity and Peer goes away and a new
session is established. This value would change and
thus indicate to the command generator that this is a
different session."
::= { mplsLdpSessionEntry 8 }
Also, a command generator can distinguish when a session
between a given Entity and Peer goes away and a new
session is established. This value would change and
thus indicate to the command generator that this is a
different session."
::= { mplsLdpSessionEntry 8 }
-- -- The MPLS LDP Session Statistics Table --
----MPLS LDP会话统计表--
mplsLdpSessionStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of statistics for Sessions between LDP Entities and LDP Peers. This table AUGMENTS
mplsLdpSessionStatsTable MplsLdpSessionStatsEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“LDP实体和LDP对等方之间会话的统计表。此表扩充了
the mplsLdpPeerTable."
::= { mplsLdpSessionObjects 4 }
the mplsLdpPeerTable."
::= { mplsLdpSessionObjects 4 }
mplsLdpSessionStatsEntry OBJECT-TYPE SYNTAX MplsLdpSessionStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents statistical information on a single session between an LDP Entity and LDP Peer."
mplsLdpSessionStatsEntry对象类型语法mplsLdpSessionStatsEntry MAX-ACCESS不可访问状态当前描述“此表中的一个条目表示LDP实体和LDP对等方之间单个会话的统计信息。”
AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSessionStatsTable 1 }
AUGMENTS { mplsLdpPeerEntry }
::= { mplsLdpSessionStatsTable 1 }
MplsLdpSessionStatsEntry ::= SEQUENCE {
mplsLdpSessionStatsUnknownMesTypeErrors Counter32,
mplsLdpSessionStatsUnknownTlvErrors Counter32
}
MplsLdpSessionStatsEntry ::= SEQUENCE {
mplsLdpSessionStatsUnknownMesTypeErrors Counter32,
mplsLdpSessionStatsUnknownTlvErrors Counter32
}
mplsLdpSessionStatsUnknownMesTypeErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Unknown Message Type Errors detected by this LSR/LER during this session.
MPLSLDPSessionStatsUnknownMessageErrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“此对象统计此LSR/LER在此会话期间检测到的未知消息类型错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSessionStatsEntry 1 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSessionStatsEntry 1 }
mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of Unknown TLV Errors detected by this LSR/LER during this session.
MPLSLDPSessionStatsUnknownTlvers对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此对象统计此LSR/LER在此会话期间检测到的未知TLV错误数。
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSessionStatsEntry 2 }
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
mplsLdpSessionDiscontinuityTime."
::= { mplsLdpSessionStatsEntry 2 }
-- -- The MPLS LDP Hello Adjacency Table --
----MPLS LDP Hello邻接表--
mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::=
{ mplsLdpSessionObjects 5 }
mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::=
{ mplsLdpSessionObjects 5 }
mplsLdpHelloAdjacencyTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Hello Adjacencies for Sessions."
::= { mplsLdpHelloAdjacencyObjects 1 }
mplsLdpHelloAdjacencyTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Hello Adjacencies for Sessions."
::= { mplsLdpHelloAdjacencyObjects 1 }
mplsLdpHelloAdjacencyEntry OBJECT-TYPE
SYNTAX MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each row represents a single LDP Hello Adjacency.
An LDP Session can have one or more Hello
Adjacencies."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpHelloAdjacencyIndex }
::= { mplsLdpHelloAdjacencyTable 1 }
mplsLdpHelloAdjacencyEntry OBJECT-TYPE
SYNTAX MplsLdpHelloAdjacencyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each row represents a single LDP Hello Adjacency.
An LDP Session can have one or more Hello
Adjacencies."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpHelloAdjacencyIndex }
::= { mplsLdpHelloAdjacencyTable 1 }
MplsLdpHelloAdjacencyEntry ::= SEQUENCE {
mplsLdpHelloAdjacencyIndex Unsigned32,
mplsLdpHelloAdjacencyHoldTimeRem TimeInterval,
mplsLdpHelloAdjacencyHoldTime Unsigned32,
mplsLdpHelloAdjacencyType INTEGER
}
MplsLdpHelloAdjacencyEntry ::= SEQUENCE {
mplsLdpHelloAdjacencyIndex Unsigned32,
mplsLdpHelloAdjacencyHoldTimeRem TimeInterval,
mplsLdpHelloAdjacencyHoldTime Unsigned32,
mplsLdpHelloAdjacencyType INTEGER
}
mplsLdpHelloAdjacencyIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An identifier for this specific adjacency."
::= { mplsLdpHelloAdjacencyEntry 1 }
mplsLdpHelloAdjacencyIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An identifier for this specific adjacency."
::= { mplsLdpHelloAdjacencyEntry 1 }
mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE SYNTAX TimeInterval UNITS "seconds" MAX-ACCESS read-only
MPLSLDHelloadJacyHoldTimeREM对象类型语法时间间隔单位“秒”最大访问只读
STATUS current DESCRIPTION "If the value of this object is 65535, this means that the hold time is infinite (i.e., wait forever).
STATUS current DESCRIPTION“如果该对象的值为65535，则表示保持时间是无限的（即永远等待）。
Otherwise, the time remaining for this Hello Adjacency to receive its next Hello Message.
否则，此Hello邻居接收其下一条Hello消息的剩余时间。
This interval will change when the 'next'
Hello Message which corresponds to this
Hello Adjacency is received unless it
is infinite."
::= { mplsLdpHelloAdjacencyEntry 2 }
This interval will change when the 'next'
Hello Message which corresponds to this
Hello Adjacency is received unless it
is infinite."
::= { mplsLdpHelloAdjacencyEntry 2 }
mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The Hello hold time which is negotiated between the Entity and the Peer. The entity associated with this Hello Adjacency issues a proposed Hello Hold Time value in the mplsLdpEntityHelloHoldTimer object. The peer also proposes a value and this object represents the negotiated value.
MPLSLDHelloadJacyHoldTime对象类型语法Unsigned32（0..65535）最大访问只读状态当前说明“实体和对等方之间协商的Hello保持时间。与此Hello邻接关联的实体在MPLSLDEntityHelloHoldTimer对象中发出建议的Hello保持时间值。对等方还提出一个值，该对象表示协商的值。
A value of 0 means the default,
which is 15 seconds for Link Hellos
and 45 seconds for Targeted Hellos.
A value of 65535 indicates an
infinite hold time."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.2 Hello Message"
::= { mplsLdpHelloAdjacencyEntry 3 }
A value of 0 means the default,
which is 15 seconds for Link Hellos
and 45 seconds for Targeted Hellos.
A value of 65535 indicates an
infinite hold time."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.2 Hello Message"
::= { mplsLdpHelloAdjacencyEntry 3 }
mplsLdpHelloAdjacencyType OBJECT-TYPE
SYNTAX INTEGER {
link(1),
targeted(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This adjacency is the result of a 'link'
hello if the value of this object is link(1).
mplsLdpHelloAdjacencyType OBJECT-TYPE
SYNTAX INTEGER {
link(1),
targeted(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This adjacency is the result of a 'link'
hello if the value of this object is link(1).
Otherwise, it is a result of a 'targeted'
hello, targeted(2)."
::= { mplsLdpHelloAdjacencyEntry 4 }
Otherwise, it is a result of a 'targeted'
hello, targeted(2)."
::= { mplsLdpHelloAdjacencyEntry 4 }
--
-- Session Label (LSP) Mapping to LSR MIB's
-- In Segment LIB Information.
--
--
-- NOTE: the next 2 tables map to the
-- MPLS-LSR-STD-MIB's MplsInSegmentTable
-- and MplsOutSegmentTable. The
-- cross-connect (XC) information is not
-- represented here as it can be gleaned
-- from the MPLS-LSR-STD-MIB.
--
--
-- Session Label (LSP) Mapping to LSR MIB's
-- In Segment LIB Information.
--
--
-- NOTE: the next 2 tables map to the
-- MPLS-LSR-STD-MIB's MplsInSegmentTable
-- and MplsOutSegmentTable. The
-- cross-connect (XC) information is not
-- represented here as it can be gleaned
-- from the MPLS-LSR-STD-MIB.
--
mplsInSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of LDP LSP's which
map to the mplsInSegmentTable in the
MPLS-LSR-STD-MIB module."
::= { mplsLdpSessionObjects 6 }
mplsInSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of LDP LSP's which
map to the mplsInSegmentTable in the
MPLS-LSR-STD-MIB module."
::= { mplsLdpSessionObjects 6 }
mplsInSegmentLdpLspEntry OBJECT-TYPE SYNTAX MplsInSegmentLdpLspEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index for the mplsInSegmentTable (mplsInSegmentLdpLspLabelIndex) from the MPLS-LSR-STD-MIB.
MPLSINSECTIONLDPLSPENTRY对象类型语法MPLSINSECTIONLDPLSPENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表中的一个条目表示单个LDP LSP的信息，该信息由会话的索引三元组（MPLSDPENTITYLDPID、MPLSDPENTITYINDEX、MPLSDPPEERLDPID）和MPLSINSECTIONTABLE的索引表示（MPLS-LSR-STD-MIB中的MPLSINSECTIONLDPLSPLABELINDEX）。
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsInSegmentLdpLspIndex
}
::= { mplsInSegmentLdpLspTable 1 }
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsInSegmentLdpLspIndex
}
::= { mplsInSegmentLdpLspTable 1 }
MplsInSegmentLdpLspEntry ::= SEQUENCE {
mplsInSegmentLdpLspIndex MplsIndexType,
mplsInSegmentLdpLspLabelType MplsLdpLabelType,
mplsInSegmentLdpLspType MplsLspType
}
MplsInSegmentLdpLspEntry ::= SEQUENCE {
mplsInSegmentLdpLspIndex MplsIndexType,
mplsInSegmentLdpLspLabelType MplsLdpLabelType,
mplsInSegmentLdpLspType MplsLspType
}
mplsInSegmentLdpLspIndex OBJECT-TYPE
SYNTAX MplsIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains the same value as the
mplsInSegmentIndex in the
MPLS-LSR-STD-MIB's mplsInSegmentTable."
::= { mplsInSegmentLdpLspEntry 1 }
mplsInSegmentLdpLspIndex OBJECT-TYPE
SYNTAX MplsIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains the same value as the
mplsInSegmentIndex in the
MPLS-LSR-STD-MIB's mplsInSegmentTable."
::= { mplsInSegmentLdpLspEntry 1 }
mplsInSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Layer 2 Label Type."
::= { mplsInSegmentLdpLspEntry 2 }
mplsInSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Layer 2 Label Type."
::= { mplsInSegmentLdpLspEntry 2 }
mplsInSegmentLdpLspType OBJECT-TYPE
SYNTAX MplsLspType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of LSP connection."
::= { mplsInSegmentLdpLspEntry 3 }
mplsInSegmentLdpLspType OBJECT-TYPE
SYNTAX MplsLspType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of LSP connection."
::= { mplsInSegmentLdpLspEntry 3 }
--
-- Session Label (LSP) Mapping to LSR MIB's
-- Out Segment LIB Information.
--
--
-- Session Label (LSP) Mapping to LSR MIB's
-- Out Segment LIB Information.
--
mplsOutSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of LDP LSP's which
map to the mplsOutSegmentTable in the
MPLS-LSR-STD-MIB."
::= { mplsLdpSessionObjects 7 }
mplsOutSegmentLdpLspTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of LDP LSP's which
map to the mplsOutSegmentTable in the
MPLS-LSR-STD-MIB."
::= { mplsLdpSessionObjects 7 }
mplsOutSegmentLdpLspEntry OBJECT-TYPE
mplsOutSegmentLdpLspEntry对象类型
SYNTAX MplsOutSegmentLdpLspEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index (mplsOutSegmentLdpLspIndex) for the mplsOutSegmentTable.
语法MPLSOUTSEGENTLDPLSPENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表中的一个条目表示单个LDP LSP的信息，该LDP由会话的索引三元组（MPLSDPENTITYLDPID、MPLSDPENTITYINDEX、MPLSDPPEERLDPID）和MPLSOUTSEGENTTABLE的索引（MPLSOUTSEGENTLDLPPINDEX）表示。
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsOutSegmentLdpLspIndex
}
::= { mplsOutSegmentLdpLspTable 1 }
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsOutSegmentLdpLspIndex
}
::= { mplsOutSegmentLdpLspTable 1 }
MplsOutSegmentLdpLspEntry ::= SEQUENCE {
mplsOutSegmentLdpLspIndex MplsIndexType,
mplsOutSegmentLdpLspLabelType MplsLdpLabelType,
mplsOutSegmentLdpLspType MplsLspType
}
MplsOutSegmentLdpLspEntry ::= SEQUENCE {
mplsOutSegmentLdpLspIndex MplsIndexType,
mplsOutSegmentLdpLspLabelType MplsLdpLabelType,
mplsOutSegmentLdpLspType MplsLspType
}
mplsOutSegmentLdpLspIndex OBJECT-TYPE
SYNTAX MplsIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains the same value as the
mplsOutSegmentIndex in the
MPLS-LSR-STD-MIB's mplsOutSegmentTable."
::= { mplsOutSegmentLdpLspEntry 1 }
mplsOutSegmentLdpLspIndex OBJECT-TYPE
SYNTAX MplsIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains the same value as the
mplsOutSegmentIndex in the
MPLS-LSR-STD-MIB's mplsOutSegmentTable."
::= { mplsOutSegmentLdpLspEntry 1 }
mplsOutSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Layer 2 Label Type."
::= { mplsOutSegmentLdpLspEntry 2 }
mplsOutSegmentLdpLspLabelType OBJECT-TYPE
SYNTAX MplsLdpLabelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Layer 2 Label Type."
::= { mplsOutSegmentLdpLspEntry 2 }
mplsOutSegmentLdpLspType OBJECT-TYPE SYNTAX MplsLspType MAX-ACCESS read-only STATUS current DESCRIPTION
MPLSSoutSegmentLDPLSPTYPE对象类型语法MPLSSPTYPE MAX-ACCESS只读状态当前说明
"The type of LSP connection."
::= { mplsOutSegmentLdpLspEntry 3 }
"The type of LSP connection."
::= { mplsOutSegmentLdpLspEntry 3 }
-- -- Mpls FEC Table --
----Mpls FEC表--
mplsFecObjects OBJECT IDENTIFIER ::=
{ mplsLdpSessionObjects 8 }
mplsFecObjects OBJECT IDENTIFIER ::=
{ mplsLdpSessionObjects 8 }
mplsFecLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpFectTable or the most recent change in values to any objects in the mplsLdpFecTable.
mplsFecLastChange对象类型语法时间戳MAX-ACCESS只读状态当前描述“在最近向MPLSLDPECTTABLE添加/删除条目时或在最近更改MPLSLDPECTTABLE中任何对象的值时，sysUpTime的值。
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsFecObjects 1 }
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsFecObjects 1 }
mplsFecIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to
be used for mplsFecIndex when creating
entries in the mplsFecTable. The value
0 indicates that no unassigned entries are
available."
::= { mplsFecObjects 2 }
mplsFecIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to
be used for mplsFecIndex when creating
entries in the mplsFecTable. The value
0 indicates that no unassigned entries are
available."
::= { mplsFecObjects 2 }
mplsFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the FEC
(Forwarding Equivalence Class)
Information associated with an LSP."
::= { mplsFecObjects 3 }
mplsFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the FEC
(Forwarding Equivalence Class)
Information associated with an LSP."
::= { mplsFecObjects 3 }
mplsFecEntry OBJECT-TYPE
SYNTAX MplsFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each row represents a single FEC Element."
INDEX { mplsFecIndex }
::= { mplsFecTable 1 }
mplsFecEntry OBJECT-TYPE
SYNTAX MplsFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each row represents a single FEC Element."
INDEX { mplsFecIndex }
::= { mplsFecTable 1 }
MplsFecEntry ::= SEQUENCE {
mplsFecIndex IndexInteger,
mplsFecType INTEGER,
mplsFecAddrType InetAddressType,
mplsFecAddr InetAddress,
mplsFecAddrPrefixLength InetAddressPrefixLength,
mplsFecStorageType StorageType,
mplsFecRowStatus RowStatus
}
MplsFecEntry ::= SEQUENCE {
mplsFecIndex IndexInteger,
mplsFecType INTEGER,
mplsFecAddrType InetAddressType,
mplsFecAddr InetAddress,
mplsFecAddrPrefixLength InetAddressPrefixLength,
mplsFecStorageType StorageType,
mplsFecRowStatus RowStatus
}
mplsFecIndex OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index which uniquely identifies this entry."
::= { mplsFecEntry 1 }
mplsFecIndex OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index which uniquely identifies this entry."
::= { mplsFecEntry 1 }
mplsFecType OBJECT-TYPE
SYNTAX INTEGER {
prefix(1),
hostAddress(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the FEC. If the value of this object
is 'prefix(1)' then the FEC type described by this
row is an address prefix.
mplsFecType OBJECT-TYPE
SYNTAX INTEGER {
prefix(1),
hostAddress(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the FEC. If the value of this object
is 'prefix(1)' then the FEC type described by this
row is an address prefix.
If the value of this object is 'hostAddress(2)' then
the FEC type described by this row is a host address."
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 2 }
If the value of this object is 'hostAddress(2)' then
the FEC type described by this row is a host address."
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 2 }
mplsFecAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create
mplsFecAddrType对象类型语法InetAddressType MAX-ACCESS读取创建
STATUS current
DESCRIPTION
"The value of this object is the type of the
Internet address. The value of this object,
decides how the value of the mplsFecAddr object
is interpreted."
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 4 }
STATUS current
DESCRIPTION
"The value of this object is the type of the
Internet address. The value of this object,
decides how the value of the mplsFecAddr object
is interpreted."
REFERENCE
"RFC3036, Section 3.4.1. FEC TLV."
::= { mplsFecEntry 4 }
mplsFecAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is interpreted based on the value of the 'mplsFecAddrType' object.
mplsFecAddr对象类型语法InetAddress MAX-ACCESS read create STATUS current DESCRIPTION“此对象的值基于“mplsFecAddrType”对象的值进行解释。
This address is then further interpretted as
an being used with the address prefix,
or as the host address. This further interpretation
is indicated by the 'mplsFecType' object.
In other words, the FEC element is populated
according to the Prefix FEC Element value encoding, or
the Host Address FEC Element encoding."
REFERENCE
"RFC3036, Section 3.4.1 FEC TLV."
::= { mplsFecEntry 5 }
This address is then further interpretted as
an being used with the address prefix,
or as the host address. This further interpretation
is indicated by the 'mplsFecType' object.
In other words, the FEC element is populated
according to the Prefix FEC Element value encoding, or
the Host Address FEC Element encoding."
REFERENCE
"RFC3036, Section 3.4.1 FEC TLV."
::= { mplsFecEntry 5 }
mplsFecAddrPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of the 'mplsFecType' is 'hostAddress(2)' then this object is undefined.
mplsFecAddrPrefixLength对象类型语法InetAddressPrefixLength MAX-ACCESS读取创建状态当前描述“如果“mplsFecType”的值为“hostAddress（2）”，则此对象未定义。
If the value of 'mplsFecType' is 'prefix(1)' then the value of this object is the length in bits of the address prefix represented by 'mplsFecAddr', or zero. If the value of this object is zero, this indicates that the prefix matches all addresses. In this case the address prefix MUST also be zero (i.e., 'mplsFecAddr' should have the value of zero.)" REFERENCE "RFC3036, Section 3.4.1. FEC TLV." DEFVAL { 0 }
如果“mplsFecType”的值是“prefix（1）”，则此对象的值是由“mplsFecAddr”表示的地址前缀的位长度，或零。如果此对象的值为零，则表示前缀与所有地址匹配。在这种情况下，地址前缀也必须为零（即，“mplsFecAddr”的值应为零。）“参考”RFC3036，第3.4.1节。FEC TLV.“定义{0}”
::= { mplsFecEntry 3 }
::= { mplsFecEntry 3 }
mplsFecStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsFecEntry 6 }
mplsFecStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsFecEntry 6 }
mplsFecRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. If the value of this object is 'active(1)', then none of the writable objects of this entry can be modified, except to set this object to 'destroy(6)'.
mplsFecRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此概念行的状态。如果此对象的值为“active（1）”，则无法修改此项的任何可写对象，除非将此对象设置为“destroy（6）”。
NOTE: if this row is being referenced by any entry in
the mplsLdpLspFecTable, then a request to destroy
this row, will result in an inconsistentValue error."
::= { mplsFecEntry 7 }
NOTE: if this row is being referenced by any entry in
the mplsLdpLspFecTable, then a request to destroy
this row, will result in an inconsistentValue error."
::= { mplsFecEntry 7 }
-- -- LDP LSP FEC Table --
----LDP LSP FEC表--
mplsLdpLspFecLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpLspFecTable or the most recent change in values to any objects in the mplsLdpLspFecTable.
MPLSDPLSPFECLASTCHANGE对象类型语法时间戳MAX-ACCESS只读状态当前描述“最近向MPLSDPLSPFECTABLE添加/删除条目时或最近向MPLSDPLSPFECTABLE中的任何对象更改值时的系统正常运行时间值。
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsLdpSessionObjects 9 }
If no such changes have occurred since the last
re-initialization of the local management subsystem,
then this object contains a zero value."
::= { mplsLdpSessionObjects 9 }
mplsLdpLspFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpLspFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table which shows the relationship between
LDP LSPs and FECs. Each row represents
a single LDP LSP to FEC association."
::= { mplsLdpSessionObjects 10 }
mplsLdpLspFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLdpLspFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table which shows the relationship between
LDP LSPs and FECs. Each row represents
a single LDP LSP to FEC association."
::= { mplsLdpSessionObjects 10 }
mplsLdpLspFecEntry OBJECT-TYPE
SYNTAX MplsLdpLspFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry represents a LDP LSP
to FEC association."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpLspFecSegment,
mplsLdpLspFecSegmentIndex,
mplsLdpLspFecIndex
}
::= { mplsLdpLspFecTable 1 }
mplsLdpLspFecEntry OBJECT-TYPE
SYNTAX MplsLdpLspFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry represents a LDP LSP
to FEC association."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpLspFecSegment,
mplsLdpLspFecSegmentIndex,
mplsLdpLspFecIndex
}
::= { mplsLdpLspFecTable 1 }
MplsLdpLspFecEntry ::= SEQUENCE {
mplsLdpLspFecSegment INTEGER,
mplsLdpLspFecSegmentIndex MplsIndexType,
mplsLdpLspFecIndex IndexInteger,
mplsLdpLspFecStorageType StorageType,
mplsLdpLspFecRowStatus RowStatus
}
MplsLdpLspFecEntry ::= SEQUENCE {
mplsLdpLspFecSegment INTEGER,
mplsLdpLspFecSegmentIndex MplsIndexType,
mplsLdpLspFecIndex IndexInteger,
mplsLdpLspFecStorageType StorageType,
mplsLdpLspFecRowStatus RowStatus
}
mplsLdpLspFecSegment OBJECT-TYPE
SYNTAX INTEGER {
inSegment(1),
outSegment(2)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"If the value is inSegment(1), then this
indicates that the following index,
mplsLdpLspFecSegmentIndex, contains the same
value as the mplsInSegmentLdpLspIndex.
mplsLdpLspFecSegment OBJECT-TYPE
SYNTAX INTEGER {
inSegment(1),
outSegment(2)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"If the value is inSegment(1), then this
indicates that the following index,
mplsLdpLspFecSegmentIndex, contains the same
value as the mplsInSegmentLdpLspIndex.
Otherwise, if the value of this object is
否则，如果此对象的值为
outSegment(2), then this
indicates that following index,
mplsLdpLspFecSegmentIndex, contains the same
value as the mplsOutSegmentLdpLspIndex."
::= { mplsLdpLspFecEntry 1 }
outSegment(2), then this
indicates that following index,
mplsLdpLspFecSegmentIndex, contains the same
value as the mplsOutSegmentLdpLspIndex."
::= { mplsLdpLspFecEntry 1 }
mplsLdpLspFecSegmentIndex OBJECT-TYPE SYNTAX MplsIndexType MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is interpretted by using the value of the mplsLdpLspFecSegment.
MPLSDPLSPFECSEGMENTINDEX对象类型语法MplsIndexType MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此索引使用MPLSDPLSPFECSEGMENT的值进行解释。
If the mplsLdpLspFecSegment is inSegment(1), then this index has the same value as mplsInSegmentLdpLspIndex.
如果MPLSDPLSPFECSegment为插入段（1），则该索引的值与mplsInSegmentLdpLspIndex的值相同。
If the mplsLdpLspFecSegment is outSegment(2),
then this index has the same value as
mplsOutSegmentLdpLspIndex."
::= { mplsLdpLspFecEntry 2 }
If the mplsLdpLspFecSegment is outSegment(2),
then this index has the same value as
mplsOutSegmentLdpLspIndex."
::= { mplsLdpLspFecEntry 2 }
mplsLdpLspFecIndex OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index identifies the FEC entry in the
mplsFecTable associated with this session.
In other words, the value of this index
is the same as the value of the mplsFecIndex
that denotes the FEC associated with this
Session."
::= { mplsLdpLspFecEntry 3 }
mplsLdpLspFecIndex OBJECT-TYPE
SYNTAX IndexInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index identifies the FEC entry in the
mplsFecTable associated with this session.
In other words, the value of this index
is the same as the value of the mplsFecIndex
that denotes the FEC associated with this
Session."
::= { mplsLdpLspFecEntry 3 }
mplsLdpLspFecStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpLspFecEntry 4 }
mplsLdpLspFecStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpLspFecEntry 4 }
mplsLdpLspFecRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. If the value of this object is 'active(1)', then none of the writable objects of this entry can be modified.
mplsLdpLspFecRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此概念行的状态。如果此对象的值为“active（1）”，则无法修改此条目的任何可写对象。
The Agent should delete this row when the session ceases to exist. If an operator wants to associate the session with a different FEC, the recommended procedure is (as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object) is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. This will also cause this entry to be deleted.
当会话不再存在时，代理应删除此行。如果操作员希望将会话与不同的FEC相关联，建议的步骤是（如标题为“会话建立后更改值”一节中详细描述的，并在MPLSLDEntityAdminStatus对象的描述子句中再次描述）将MPLSLDEntityAdminStatus设置为down，从而明确地导致会话被中断。这也将导致删除此条目。
Then, set the mplsLdpEntityAdminStatus
to enable which enables a new session to be initiated.
Once the session is initiated, an entry may be
added to this table to associate the new session
with a FEC."
::= { mplsLdpLspFecEntry 5 }
Then, set the mplsLdpEntityAdminStatus
to enable which enables a new session to be initiated.
Once the session is initiated, an entry may be
added to this table to associate the new session
with a FEC."
::= { mplsLdpLspFecEntry 5 }
--
-- Address Message/Address Withdraw Message Information
--
-- This information is associated with a specific Session
-- because Label Address Messages are sent after session
-- initialization has taken place.
--
--
-- Address Message/Address Withdraw Message Information
--
-- This information is associated with a specific Session
-- because Label Address Messages are sent after session
-- initialization has taken place.
--
mplsLdpSessionPeerAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table 'extends' the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated
mplsLdpSessionPeerAddrTable mplsLdpSessionPeerAddrTable对象类型语法序列MplsLdpSessionPeerAddrEntry MAX-ACCESS不可访问状态当前描述“此表“扩展”mplsLdpSessionTable。此表用于存储此LSR从对等方接收的标签地址消息中的标签地址信息。此表为只读表，应进行更新
when Label Withdraw Address Messages are received, i.e., Rows should be deleted as appropriate.
当收到标签撤销地址消息时，即应酌情删除行。
NOTE: since more than one address may be contained
in a Label Address Message, this table 'sparse augments',
the mplsLdpSessionTable's information."
::= { mplsLdpSessionObjects 11 }
NOTE: since more than one address may be contained
in a Label Address Message, this table 'sparse augments',
the mplsLdpSessionTable's information."
::= { mplsLdpSessionObjects 11 }
mplsLdpSessionPeerAddrEntry OBJECT-TYPE
SYNTAX MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents information on
a session's single next hop address which was
advertised in an Address Message from the LDP peer.
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpSessionPeerAddrIndex
}
::= { mplsLdpSessionPeerAddrTable 1 }
mplsLdpSessionPeerAddrEntry OBJECT-TYPE
SYNTAX MplsLdpSessionPeerAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents information on
a session's single next hop address which was
advertised in an Address Message from the LDP peer.
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpSessionPeerAddrIndex
}
::= { mplsLdpSessionPeerAddrTable 1 }
MplsLdpSessionPeerAddrEntry ::= SEQUENCE {
mplsLdpSessionPeerAddrIndex Unsigned32,
mplsLdpSessionPeerNextHopAddrType InetAddressType,
mplsLdpSessionPeerNextHopAddr InetAddress
}
MplsLdpSessionPeerAddrEntry ::= SEQUENCE {
mplsLdpSessionPeerAddrIndex Unsigned32,
mplsLdpSessionPeerNextHopAddrType InetAddressType,
mplsLdpSessionPeerNextHopAddr InetAddress
}
mplsLdpSessionPeerAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index which uniquely identifies this entry within
a given session."
::= { mplsLdpSessionPeerAddrEntry 1 }
mplsLdpSessionPeerAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index which uniquely identifies this entry within
a given session."
::= { mplsLdpSessionPeerAddrEntry 1 }
mplsLdpSessionPeerNextHopAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The internetwork layer address type of this Next Hop Address as specified in the Label Address Message associated with this Session. The value of this object indicates how to interpret the value of
mplsLdpSessionPeerNextHopAddrType对象类型语法InetAddressType MAX-ACCESS只读状态当前描述“在与此会话关联的标签地址消息中指定的此下一个跃点地址的网络层地址类型。此对象的值指示如何解释
mplsLdpSessionPeerNextHopAddr."
::= { mplsLdpSessionPeerAddrEntry 2 }
mplsLdpSessionPeerNextHopAddr."
::= { mplsLdpSessionPeerAddrEntry 2 }
mplsLdpSessionPeerNextHopAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The next hop address. The type of this address
is specified by the value of the
mplsLdpSessionPeerNextHopAddrType."
REFERENCE
"RFC3036, Section 2.7. LDP Identifiers
and Next Hop Addresses"
::= { mplsLdpSessionPeerAddrEntry 3 }
mplsLdpSessionPeerNextHopAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The next hop address. The type of this address
is specified by the value of the
mplsLdpSessionPeerNextHopAddrType."
REFERENCE
"RFC3036, Section 2.7. LDP Identifiers
and Next Hop Addresses"
::= { mplsLdpSessionPeerAddrEntry 3 }
---
--- Notifications
---
---
--- Notifications
---
mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE
OBJECTS {
mplsLdpEntityInitSessionThreshold
}
STATUS current
DESCRIPTION
"This notification is generated when the value of
the 'mplsLdpEntityInitSessionThreshold' object
is not zero, and the number of Session
Initialization messages exceeds the value
of the 'mplsLdpEntityInitSessionThreshold' object."
::= { mplsLdpNotifications 1 }
mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE
OBJECTS {
mplsLdpEntityInitSessionThreshold
}
STATUS current
DESCRIPTION
"This notification is generated when the value of
the 'mplsLdpEntityInitSessionThreshold' object
is not zero, and the number of Session
Initialization messages exceeds the value
of the 'mplsLdpEntityInitSessionThreshold' object."
::= { mplsLdpNotifications 1 }
mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE
OBJECTS {
mplsLdpEntityPathVectorLimit,
mplsLdpPeerPathVectorLimit
}
STATUS current
DESCRIPTION
"This notification is sent when the
'mplsLdpEntityPathVectorLimit' does NOT match
the value of the 'mplsLdpPeerPathVectorLimit' for
a specific Entity."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3."
::= { mplsLdpNotifications 2 }
mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE
OBJECTS {
mplsLdpEntityPathVectorLimit,
mplsLdpPeerPathVectorLimit
}
STATUS current
DESCRIPTION
"This notification is sent when the
'mplsLdpEntityPathVectorLimit' does NOT match
the value of the 'mplsLdpPeerPathVectorLimit' for
a specific Entity."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3."
::= { mplsLdpNotifications 2 }
mplsLdpSessionUp NOTIFICATION-TYPE
OBJECTS {
mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors
}
STATUS current
DESCRIPTION
"If this notification is sent when the
value of 'mplsLdpSessionState' enters
the 'operational(5)' state."
::= { mplsLdpNotifications 3 }
mplsLdpSessionUp NOTIFICATION-TYPE
OBJECTS {
mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors
}
STATUS current
DESCRIPTION
"If this notification is sent when the
value of 'mplsLdpSessionState' enters
the 'operational(5)' state."
::= { mplsLdpNotifications 3 }
mplsLdpSessionDown NOTIFICATION-TYPE
OBJECTS {
mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors
mplsLdpSessionDown NOTIFICATION-TYPE
OBJECTS {
mplsLdpSessionState,
mplsLdpSessionDiscontinuityTime,
mplsLdpSessionStatsUnknownMesTypeErrors,
mplsLdpSessionStatsUnknownTlvErrors
}
STATUS current
DESCRIPTION
"This notification is sent when the
value of 'mplsLdpSessionState' leaves
the 'operational(5)' state."
::= { mplsLdpNotifications 4 }
}
STATUS current
DESCRIPTION
"This notification is sent when the
value of 'mplsLdpSessionState' leaves
the 'operational(5)' state."
::= { mplsLdpNotifications 4 }
--****************************************************************
-- Module Conformance Statement
--****************************************************************
--****************************************************************
-- Module Conformance Statement
--****************************************************************
mplsLdpGroups
OBJECT IDENTIFIER ::= { mplsLdpConformance 1 }
mplsLdpGroups
OBJECT IDENTIFIER ::= { mplsLdpConformance 1 }
mplsLdpCompliances
OBJECT IDENTIFIER ::= { mplsLdpConformance 2 }
mplsLdpCompliances
OBJECT IDENTIFIER ::= { mplsLdpConformance 2 }
-- -- Full Compliance --
----完全遵守--
mplsLdpModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The Module is implemented with support for read-create and read-write. In other
MPLSLDPModulelCompliance MODULE-COMPLIANCE状态当前描述“该模块的实现支持读创建和读写。其他
words, both monitoring and configuration are available when using this MODULE-COMPLIANCE."
换句话说，使用此模块时，监控和配置都可用。”
MODULE -- this module MANDATORY-GROUPS { mplsLdpGeneralGroup, mplsLdpNotificationsGroup } GROUP mplsLdpLspGroup DESCRIPTION "This group must be supported if the LSR MIB is implemented, specifically the mplsInSegmentTable, the mplsOutSegmentTable or the mplsXCTable."
MODULE--此模块强制-GROUPS{mplsLdpGeneralGroup，mplsLdpNotificationsGroup}组mplsldplsgroup DESCRIPTION“如果实现了LSR MIB，特别是mplsInSegmentTable、mplsOutSegmentTable或mplsXCTable，则必须支持此组。”
OBJECT mplsLdpEntityTargetPeerAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象MPLSLDEntityTargetPeeraddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现仅需要支持“unknown（0）”、ipv4和全局唯一的ipv6地址。”
OBJECT mplsLdpEntityTargetPeerAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象MPLSLDEntityTargetPeeraddr语法InetAddress（大小（0 | 4 | 16））说明“仅需要实现来支持IPv4和全局唯一IPv6地址。”
OBJECT mplsLdpEntityRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT mplsLdpEntityRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT mplsFecAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象mplsFecAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现仅需要支持‘unknown（0）’、ipv4和全局唯一的ipv6地址。”
OBJECT mplsFecAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象mplsFecAddr语法InetAddress（大小（0 | 4 | 16））说明“仅支持IPv4和全局唯一IPv6地址才需要实现。”
OBJECT mplsFecRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
OBJECT mplsFecRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
“不需要对createAndWait和notInService的支持。”
OBJECT mplsLdpLspFecRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT mplsLdpLspFecRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT mplsLdpSessionPeerNextHopAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象mplsLdpSessionPeerNextHopAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现仅需要支持“unknown（0）”、ipv4和全局唯一的ipv6地址。”
OBJECT mplsLdpSessionPeerNextHopAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象mplsLdpSessionPeerNextHopAddr语法InetAddress（大小（0 | 4 | 16））说明“仅支持IPv4和全局唯一IPv6地址才需要实现。”
::= { mplsLdpCompliances 1 }
::= { mplsLdpCompliances 1 }
-- -- Read-Only Compliance --
----只读遵从性--
mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE."
MPLSLDPModuleRadonlyCompliance MODULE-COMPLIANCE状态当前描述“该模块是在支持只读的情况下实现的。换言之，通过实现该模块-COMPLIANCE只能进行监控。”
MODULE -- this module MANDATORY-GROUPS { mplsLdpGeneralGroup, mplsLdpNotificationsGroup }
MODULE--此模块为必填组{mplsLdpGeneralGroup，MPLSLDNotificationsGroup}
GROUP mplsLdpLspGroup DESCRIPTION "This group must be supported if the LSR MIB is implemented, specifically the mplsInSegmentTable, the mplsOutSegmentTable or the mplsXCTable."
GROUP MPLSDPLSPGroup DESCRIPTION“如果实现了LSR MIB，特别是mplsInSegmentTable、mplsOutSegmentTable或mplsXCTable，则必须支持此组。”
OBJECT mplsLdpEntityProtocolVersion MIN-ACCESS read-only
对象MPLSLDEntityProtocolVersion最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT mplsLdpEntityAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityAdminStatus最小访问只读描述“不需要写访问。”
OBJECT mplsLdpEntityTcpPort MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityTcport MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityUdpDscPort MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityUDPDSCPort最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityMaxPduLength MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsLdpEntityMaxPduLength最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityKeepAliveHoldTimer MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityKeepAliveHoldTimer最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityHelloHoldTimer MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityHelloHoldTimer最小访问只读描述“不需要写访问。”
OBJECT mplsLdpEntityInitSessionThreshold MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityInitSessionReshold MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityLabelDistMethod MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityLabelDistMethod最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityLabelRetentionMode MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityLabelRetentionMode最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityPathVectorLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityPathVectorLimit最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityHopCountLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityHopCountLimit最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityTransportAddrKind MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityTransportAddRkind最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityTargetPeer MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityTargetPeer最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityTargetPeerAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象MPLSLDEntityTargetPeeraddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}MIN-ACCESS只读说明“不需要写访问。只需要实现来支持“unknown（0）”、ipv4和全局唯一的ipv6地址。”
OBJECT mplsLdpEntityTargetPeerAddr SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象MPLSLDEntityTargetPeeradDR语法InetAddress（大小（0 | 4 | 16））最小访问只读说明“不需要写访问。只需要实现来支持IPv4和全局唯一的IPv6地址。”
OBJECT mplsLdpEntityLabelType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityLabelType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityStorageType最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityRowStatus SYNTAX RowStatus { active(1) }
对象mplsLdpEntityRowStatus语法行状态{active（1）}
MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
MIN-ACCESS只读说明“不需要写访问，并且活动是唯一需要支持的状态。”
OBJECT mplsFecType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsFecType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsFecAddrPrefixLength MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsFecAddrPrefixLength最小访问只读描述“不需要写访问。”
OBJECT mplsFecAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象mplsFecAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}MIN-ACCESS只读说明“不需要写访问。只需要实现来支持“unknown（0）”、ipv4和全局唯一的ipv6地址。”
OBJECT mplsFecAddr SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象mplsFecAddr语法InetAddress（大小（0 | 4 | 16））MIN-ACCESS只读说明“不需要写访问。只需要实现来支持IPv4和全局唯一的IPv6地址。”
OBJECT mplsFecStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsFecStorageType最小访问只读描述“不需要写访问。”
OBJECT mplsFecRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象mplsFecRowStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，并且active是唯一需要支持的状态。”
OBJECT mplsLdpLspFecStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSDPLSPFECStorageType最小访问只读说明“不需要写访问。”
OBJECT mplsLdpLspFecRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象MPLSDPLSPFECROWSTATUS语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，并且active是需要支持的唯一状态。”
OBJECT mplsLdpSessionPeerNextHopAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support 'unknown(0)', IPv4 and globally unique IPv6 addresses."
对象mplsLdpSessionPeerNextHopAddrType语法InetAddressType{unknown（0）、ipv4（1）、ipv6（2）}说明“实现仅需要支持“unknown（0）”、ipv4和全局唯一的ipv6地址。”
OBJECT mplsLdpSessionPeerNextHopAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
对象mplsLdpSessionPeerNextHopAddr语法InetAddress（大小（0 | 4 | 16））说明“仅支持IPv4和全局唯一IPv6地址才需要实现。”
::= { mplsLdpCompliances 2 }
::= { mplsLdpCompliances 2 }
-- units of conformance
--一致性单位
mplsLdpGeneralGroup OBJECT-GROUP OBJECTS { mplsLdpLsrId, mplsLdpLsrLoopDetectionCapable, mplsLdpEntityLastChange, mplsLdpEntityIndexNext, mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, mplsLdpEntityOperStatus, mplsLdpEntityTcpPort, mplsLdpEntityUdpDscPort, mplsLdpEntityMaxPduLength, mplsLdpEntityKeepAliveHoldTimer, mplsLdpEntityHelloHoldTimer, mplsLdpEntityInitSessionThreshold, mplsLdpEntityLabelDistMethod, mplsLdpEntityLabelRetentionMode, mplsLdpEntityPathVectorLimit, mplsLdpEntityHopCountLimit, mplsLdpEntityTransportAddrKind, mplsLdpEntityTargetPeer, mplsLdpEntityTargetPeerAddrType, mplsLdpEntityTargetPeerAddr, mplsLdpEntityLabelType,
MPLSLDGeneralGroup对象组对象{mplsLdpLsrId，mplsldplsrloopdetectionable，mplsldpentityllastchange，mplsldpentitylindexnext，mplsldpentitylprotocollversion，mplsldpentitylAdminStatus，mplsldpentityloperStatus，mplsldpentityltcport，mplsldpentityludpdscport，mplsldpentitylaxpdulelength，mplsldpentitylkeepaliveholdTimer，mplsldpentitylhelloholdTimer，mplsldpentitylinitionsessionreshold，mplsldEntityLabelDistMethod、mplsldEntityLabelRetentionMode、mplsldEntityPathVectorLimit、mplsldEntityHopCountLimit、mplsldEntityTransportAddRkind、mplsldEntityTargetPeer、mplsldEntityTargetPeeraddrType、mplsldEntityTargetPeeraddr、mplsldEntityLabelType、，
mplsLdpEntityDiscontinuityTime, mplsLdpEntityStorageType, mplsLdpEntityRowStatus, mplsLdpEntityStatsSessionAttempts, mplsLdpEntityStatsSessionRejectedNoHelloErrors, mplsLdpEntityStatsSessionRejectedAdErrors, mplsLdpEntityStatsSessionRejectedMaxPduErrors, mplsLdpEntityStatsSessionRejectedLRErrors, mplsLdpEntityStatsBadLdpIdentifierErrors, mplsLdpEntityStatsBadPduLengthErrors, mplsLdpEntityStatsBadMessageLengthErrors, mplsLdpEntityStatsBadTlvLengthErrors, mplsLdpEntityStatsMalformedTlvValueErrors, mplsLdpEntityStatsKeepAliveTimerExpErrors, mplsLdpEntityStatsShutdownReceivedNotifications, mplsLdpEntityStatsShutdownSentNotifications, mplsLdpPeerLastChange, mplsLdpPeerLabelDistMethod, mplsLdpPeerPathVectorLimit, mplsLdpPeerTransportAddrType, mplsLdpPeerTransportAddr, mplsLdpHelloAdjacencyHoldTimeRem, mplsLdpHelloAdjacencyHoldTime, mplsLdpHelloAdjacencyType, mplsLdpSessionStateLastChange, mplsLdpSessionState, mplsLdpSessionRole, mplsLdpSessionProtocolVersion, mplsLdpSessionKeepAliveHoldTimeRem, mplsLdpSessionKeepAliveTime, mplsLdpSessionMaxPduLength, mplsLdpSessionDiscontinuityTime, mplsLdpSessionStatsUnknownMesTypeErrors, mplsLdpSessionStatsUnknownTlvErrors, mplsLdpSessionPeerNextHopAddrType, mplsLdpSessionPeerNextHopAddr, mplsFecLastChange, mplsFecIndexNext, mplsFecType, mplsFecAddrType, mplsFecAddr, mplsFecAddrPrefixLength, mplsFecStorageType, mplsFecRowStatus } STATUS current DESCRIPTION "Objects that apply to all MPLS LDP implementations."
MPLSLDPTEntityInteractionTime、MPLSLDPTEntityStorageType、MPLSLDPTEntityStatus、MPLSLDPTEntityStatsSessionAttents、MPLSLDPTEntityStatsSessionRejectedNoHelloErrors、MPLSLDPTEntityStatsSessionRejectedDerrors、MPLSLDPTEntityStatsSessionRejectedMaxPduerrors、MPLSLDPTEntityStatsSessionRejectedLRErrors、MPLSLDPTEntityStatsBaddldpIdentifierErrors、，MPLSLDEntityStatsBadPDulengErrors、MPLSLDEntityStatsBadMessageLength Errors、MPLSLDEntityStatsBadTllLength Errors、MPLSLDEntityStats格式错误的LvValueErrors、MPLSLDEntityStatsKeepaliveTimeRexperrors、MPLSLDEntityStatsShutdownReceivedNotifications、MPLSLDEntityStatsShutdownEntityNotifications、MPLSLDPeerLastChange、MPLSLDPeerLabelDistmethod、，MPLSLPpeerPathVectorLimit、MPLSDPpeerTransportAddRtype、MPLSDPpeerTransportAddR、MPLSDPhelloadJacyHoldTimeRem、MPLSDPhelloadJacyHoldTime、MPLSDPhelloadJacyCycyType、MPLSDPSessionStateLastChange、MPLSDPSessionState、MPLSDPSessionRole、MPLSLPSessionProtocolVersion、MPLSDPSessionKeepAliveHoldTimeRem、MPLSDPSessionKeepAliveTime、，MPLSLDPSessionMaxPDuleLength、mplsLdpSessionDiscontinuityTime、MPLSLDPSessionStatsUnknownMeshPeerrors、mplsLdpSessionStatsUnknownTlvErrors、mplsLdpSessionPeerNextHopAddrType、mplsLdpSessionPeerNextHopAddr、MPLSEclastChange、mplsFecIndexNext、MPLSFecAddressType、MPLSFecAddress、MPLSFecAddressPrefixLength、mplsFecStorageType、，mplsFecRowStatus}状态当前描述“应用于所有MPLS LDP实现的对象。”
::= { mplsLdpGroups 1 }
::= { mplsLdpGroups 1 }
mplsLdpLspGroup OBJECT-GROUP
OBJECTS {
mplsInSegmentLdpLspLabelType,
mplsInSegmentLdpLspType,
mplsOutSegmentLdpLspLabelType,
mplsOutSegmentLdpLspType,
mplsLdpLspFecLastChange,
mplsLdpLspFecStorageType,
mplsLdpLspFecRowStatus
}
STATUS current
DESCRIPTION
"These objects are for LDP implementations
which interface to the Label Information Base (LIB)
in the MPLS-LSR-STD-MIB. The LIB is
represented in the mplsInSegmentTable,
mplsOutSegmentTable and mplsXCTable."
::= { mplsLdpGroups 2 }
mplsLdpLspGroup OBJECT-GROUP
OBJECTS {
mplsInSegmentLdpLspLabelType,
mplsInSegmentLdpLspType,
mplsOutSegmentLdpLspLabelType,
mplsOutSegmentLdpLspType,
mplsLdpLspFecLastChange,
mplsLdpLspFecStorageType,
mplsLdpLspFecRowStatus
}
STATUS current
DESCRIPTION
"These objects are for LDP implementations
which interface to the Label Information Base (LIB)
in the MPLS-LSR-STD-MIB. The LIB is
represented in the mplsInSegmentTable,
mplsOutSegmentTable and mplsXCTable."
::= { mplsLdpGroups 2 }
mplsLdpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded,
mplsLdpPathVectorLimitMismatch,
mplsLdpSessionUp,
mplsLdpSessionDown
}
STATUS current
DESCRIPTION
"The notification for an MPLS LDP implementation."
::= { mplsLdpGroups 3 }
mplsLdpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded,
mplsLdpPathVectorLimitMismatch,
mplsLdpSessionUp,
mplsLdpSessionDown
}
STATUS current
DESCRIPTION
"The notification for an MPLS LDP implementation."
::= { mplsLdpGroups 3 }
END
终止
This MIB Module MUST be supported if LDP uses ATM as the Layer 2 medium. There are three tables in this MIB Module. Two tables are for configuring LDP to use ATM. These tables are the mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third table is the mplsLdpAtmSessionTable which is a read-only table. This MIB Module IMPORTS the AtmVpIdentifier TEXTUAL-CONVENTION from [RFC2514].
如果LDP使用ATM作为第2层介质，则必须支持此MIB模块。此MIB模块中有三个表。两个表用于配置LDP以使用ATM。这些表是MPLSLDEntityATMTable和MPLSLDEntityATMLRTable。第三个表是mplsLdpAtmSessionTable，它是一个只读表。此MIB模块从[RFC2514]导入AtmVpIdentifier文本约定。
The mplsLdpEntityAtmTable provides a way to configure information which would be contained in the "Optional Parameter" portion of an LDP PDU Initialization Message.
MPLSLDEntityAtmTable提供了一种配置信息的方法，这些信息将包含在LDP PDU初始化消息的“可选参数”部分中。
The mplsLdpEntityAtmLRTable provides a way to configure information which would be contained in the "ATM Label Range Components" portion of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036].
MPLSLDEntityATMLRTable提供了一种配置信息的方法，这些信息将包含在LDP PDU初始化消息的“ATM标签范围组件”部分中，请参见[RFC3035]和[RFC3036]。
The MPLS LDP ATM Session Table is a read-only table which contains session information specific to ATM.
MPLS LDP ATM会话表是一个只读表，其中包含特定于ATM的会话信息。
MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN
MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE, MODULE-IDENTITY,
Unsigned32
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
RowStatus,
StorageType
FROM SNMPv2-TC -- [RFC2579]
IMPORTS
OBJECT-TYPE, MODULE-IDENTITY,
Unsigned32
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
RowStatus,
StorageType
FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero FROM IF-MIB -- [RFC2020]
来自IF-MIB的接口索引或零--[RFC2020]
AtmVpIdentifier FROM ATM-TC-MIB -- [RFC2514]
来自ATM-TC-MIB的ATMVP标识符--[RFC2514]
mplsStdMIB, MplsAtmVcIdentifier FROM MPLS-TC-STD-MIB -- [RFC3811]
来自MPLS-TC-STD-MIB的MPLSSDDMIB、MplsAtmVcIdentifier--[RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId FROM MPLS-LDP-STD-MIB -- [RFC3813]
MPLS-LDP-STD-MIB中的MPLSLDEntityLDPID、MPLSLDEntityIndex、MPLSLDPeerldPID--[RFC3813]
;
;
mplsLdpAtmStdMIB MODULE-IDENTITY LAST-UPDATED "200406030000Z" -- June 3, 2004
mplsLdpAtmStdMIB模块标识最后一次更新“200406030000Z”-2004年6月3日
ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" CONTACT-INFO "Joan Cucchiara (jcucchiara@mindspring.com) Marconi Communications, Inc.
组织“多协议标签交换（mpls）工作组”联系人信息“Joan Cucchiara(jcucchiara@mindspring.com)马可尼通讯公司。
Hans Sjostrand (hans@ipunplugged.com) ipUnplugged
汉斯·索斯特兰德(hans@ipunplugged.com)拔下插头
James V. Luciani (james_luciani@mindspring.com) Marconi Communications, Inc.
詹姆斯诉卢西亚尼（詹姆斯）_luciani@mindspring.com)马可尼通讯公司。
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net " DESCRIPTION "Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
MPLS工作组，电子邮件：mpls@uu.net“说明”版权所有（C）互联网协会（2004年）。该MIB模块的初始版本发布在RFC 3815中。有关完整的法律通知，请参阅RFC本身或参阅：http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 media." REVISION "200406030000Z" -- June 3, 2004 DESCRIPTION "Initial version published as part of RFC 3815."
此MIB包含用于配置和监控多协议标签交换（MPLS）、标签分发协议（LDP）的托管对象定义，该协议使用异步传输模式（ATM）作为第2层介质。“修订版”200406030000Z--2004年6月3日描述“作为RFC 3815的一部分发布的初始版本”
::= { mplsStdMIB 5 }
::= { mplsStdMIB 5 }
--****************************************************************
--****************************************************************
mplsLdpAtmObjects OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 1 }
mplsLdpAtmConformance OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 2 }
mplsLdpAtmObjects OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 1 }
mplsLdpAtmConformance OBJECT IDENTIFIER
::= { mplsLdpAtmStdMIB 2 }
--****************************************************************
-- MPLS LDP ATM Objects
--****************************************************************
--
-- Ldp Entity Objects for ATM
--****************************************************************
-- MPLS LDP ATM Objects
--****************************************************************
--
-- Ldp Entity Objects for ATM
--
--
mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 1 }
mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 1 }
mplsLdpEntityAtmTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM specific information which could be used in the 'Optional Parameters' and other ATM specific information.
MPLSLDEntityAtmTable对象类型MPLSLDEntityAtmentry MAX-ACCESS的语法序列不可访问状态当前描述“此表包含ATM特定信息，可用于“可选参数”和其他ATM特定信息。
This table 'sparse augments' the mplsLdpEntityTable
when ATM is the Layer 2 medium."
::= { mplsLdpEntityAtmObjects 1 }
This table 'sparse augments' the mplsLdpEntityTable
when ATM is the Layer 2 medium."
::= { mplsLdpEntityAtmObjects 1 }
mplsLdpEntityAtmEntry OBJECT-TYPE
SYNTAX MplsLdpEntityAtmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents the ATM parameters
and ATM information for this LDP entity."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex
}
::= { mplsLdpEntityAtmTable 1 }
mplsLdpEntityAtmEntry OBJECT-TYPE
SYNTAX MplsLdpEntityAtmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents the ATM parameters
and ATM information for this LDP entity."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex
}
::= { mplsLdpEntityAtmTable 1 }
MplsLdpEntityAtmEntry ::= SEQUENCE {
mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero,
mplsLdpEntityAtmMergeCap INTEGER,
mplsLdpEntityAtmLRComponents Unsigned32,
mplsLdpEntityAtmVcDirectionality INTEGER,
mplsLdpEntityAtmLsrConnectivity INTEGER,
mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier,
mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier,
mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier,
mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier,
mplsLdpEntityAtmStorageType StorageType,
mplsLdpEntityAtmRowStatus RowStatus
}
MplsLdpEntityAtmEntry ::= SEQUENCE {
mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero,
mplsLdpEntityAtmMergeCap INTEGER,
mplsLdpEntityAtmLRComponents Unsigned32,
mplsLdpEntityAtmVcDirectionality INTEGER,
mplsLdpEntityAtmLsrConnectivity INTEGER,
mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier,
mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier,
mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier,
mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier,
mplsLdpEntityAtmStorageType StorageType,
mplsLdpEntityAtmRowStatus RowStatus
}
mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE SYNTAX InterfaceIndexOrZero
MPLSLDEntityAtMifIndexorZero对象类型语法接口IndexorZero
MAX-ACCESS read-create STATUS current DESCRIPTION "This value represents either the InterfaceIndex or 0 (zero). The value of zero means that the InterfaceIndex is not known.
MAX-ACCESS read create STATUS current DESCRIPTION“此值表示接口索引或0（零）。零值表示接口索引未知。
However, if the InterfaceIndex is known, then it must be represented by this value.
但是，如果InterfaceIndex已知，则必须用该值表示。
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an ATM Label is
being used in forwarding data, then the value of this
object MUST be the InterfaceIndex."
::= { mplsLdpEntityAtmEntry 1 }
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an ATM Label is
being used in forwarding data, then the value of this
object MUST be the InterfaceIndex."
::= { mplsLdpEntityAtmEntry 1 }
mplsLdpEntityAtmMergeCap OBJECT-TYPE
SYNTAX INTEGER {
notSupported(0),
vpMerge(1),
vcMerge(2),
vpAndVcMerge(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes the Merge Capability of this Entity.
This is the EXACT value for the ATM Session
Parameter, field M (for ATM Merge Capabilities).
The ATM Session Parameter is an optional
parameter in the Initialization Message.
mplsLdpEntityAtmMergeCap OBJECT-TYPE
SYNTAX INTEGER {
notSupported(0),
vpMerge(1),
vcMerge(2),
vpAndVcMerge(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes the Merge Capability of this Entity.
This is the EXACT value for the ATM Session
Parameter, field M (for ATM Merge Capabilities).
The ATM Session Parameter is an optional
parameter in the Initialization Message.
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification:
'M，ATM合并功能指定ATM交换机的合并功能。此版本的规范支持以下值：
Value Meaning
价值意义
0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported
不支持0合并1支持VP合并2支持VC合并3支持VP和VC合并
If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate.
如果LSR的合并功能不同，则：-非合并和VC合并LSR可以自由互操作。
- The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.'
- 支持VP合并的交换机与不支持VP合并的交换机的互操作性是未来研究的主题。当LSR在VP merge的使用上存在差异时，将建立会话，但不使用VP merge。”
Please refer to the following reference for a complete description of this feature."
有关此功能的完整说明，请参阅以下参考。”
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 2 }
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 2 }
mplsLdpEntityAtmLRComponents OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityAtmLRTable which correspond to this entry.
MPLSLDEntityATMLRComponents对象类型语法Unsigned32（1..65535）MAX-ACCESS只读状态当前描述“初始化消息中标签范围组件的数量。这还表示MPLSLDEntityATMLRTable中与此条目对应的条目数。
This is the EXACT value for the ATM Session Parameter, field N (for Number of label range components). The ATM Session Parameter is an optional parameter in the Initialization Message.
这是ATM会话参数字段N（用于标签范围组件的数量）的精确值。ATM会话参数是初始化消息中的可选参数。
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'N, Number of label range components Specifies the number of ATM Label Range Components included in the TLV.'
'N，Number of label range components指定TLV中包含的ATM标签范围组件的数量。'
Please refer to the following reference for
a complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 3 }
Please refer to the following reference for
a complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 3 }
mplsLdpEntityAtmVcDirectionality OBJECT-TYPE SYNTAX INTEGER { bidirectional(0),
MPLSLDEntityATMVCD方向性对象类型语法整数{双向（0），
unidirectional(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is 'bidirectional(0)', a given VCI, within a given VPI, is used as a label for both directions independently.
单向（1）}MAX-ACCESS read create STATUS current DESCRIPTION“如果此对象的值为“双向（0）”，则给定VPI内的给定VCI将独立用作两个方向的标签。
If the value of this object is 'unidirectional(1)', a given VCI within a VPI designates one direction.
如果此对象的值为“单向（1）”，则VPI中的给定VCI指定一个方向。
This is the EXACT value for the ATM Session Parameter, field D (for VC Directionality). The ATM Session Parameter is an optional parameter in the Initialization Message.
这是ATM会话参数字段D（VC方向性）的精确值。ATM会话参数是初始化消息中的可选参数。
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can (within a given VPI) support the use of a given VCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning (within a given VPI) a given VCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered VCIs in the VPI/VCI range as labels. The system with the smaller LDP Identifier may assign only even-numbered VCIs in the VPI/VCI range as labels.'
'D，VC方向性值0指定双向VC能力，这意味着LSR可以（在给定VPI内）支持将给定VCI作为两个链路方向的标签单独使用。值1指定单向VC能力，这意味着（在给定的VPI内）给定的VCI可能仅出现在链接上一个方向的标签映射中。当其中一个或两个对等点指定单向VC功能时，两个LSR对链路使用单向VC标签分配，如下所示。LSR将其LDP标识符作为无符号整数进行比较。具有较大LDP标识符的LSR可仅将VPI/VCI范围内的奇数编号VCI分配为标签。具有较小LDP标识符的系统只能将VPI/VCI范围内的偶数编号VCI指定为标签。”
Please refer to the following reference
for a complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 4 }
Please refer to the following reference
for a complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityAtmEntry 4 }
mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE SYNTAX INTEGER { direct(1),
MPLSLDEntityATMLSRConnection对象类型语法整数{direct（1），
indirect(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The peer LSR may be connected indirectly by means
of an ATM VP so that the VPI values may be different
on either endpoint so the label MUST be encoded
entirely within the VCI field."
DEFVAL { direct }
::= { mplsLdpEntityAtmEntry 5 }
indirect(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The peer LSR may be connected indirectly by means
of an ATM VP so that the VPI values may be different
on either endpoint so the label MUST be encoded
entirely within the VCI field."
DEFVAL { direct }
::= { mplsLdpEntityAtmEntry 5 }
mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The default VPI value for the non-MPLS connection. The
default value of this is 0 (zero) but other values may
be configured. This object allows a different value
to be configured."
DEFVAL { 0 }
::= { mplsLdpEntityAtmEntry 6 }
mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The default VPI value for the non-MPLS connection. The
default value of this is 0 (zero) but other values may
be configured. This object allows a different value
to be configured."
DEFVAL { 0 }
::= { mplsLdpEntityAtmEntry 6 }
mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Default VCI value for a non-MPLS connection. The
default value of this is 32 but other values may be
configured. This object allows a different value to
be configured."
DEFVAL { 32 }
::= { mplsLdpEntityAtmEntry 7 }
mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Default VCI value for a non-MPLS connection. The
default value of this is 32 but other values may be
configured. This object allows a different value to
be configured."
DEFVAL { 32 }
::= { mplsLdpEntityAtmEntry 7 }
mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"VPI value of the VCC supporting unlabeled traffic. This
non-MPLS connection is used to carry unlabeled (IP)
packets. The default value is the same as the default
value of the 'mplsLdpEntityAtmDefaultControlVpi', however
another value may be configured."
DEFVAL { 0 }
::= { mplsLdpEntityAtmEntry 8 }
mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"VPI value of the VCC supporting unlabeled traffic. This
non-MPLS connection is used to carry unlabeled (IP)
packets. The default value is the same as the default
value of the 'mplsLdpEntityAtmDefaultControlVpi', however
another value may be configured."
DEFVAL { 0 }
::= { mplsLdpEntityAtmEntry 8 }
mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"VCI value of the VCC supporting unlabeled traffic.
This non-MPLS connection is used to carry unlabeled (IP)
packets. The default value is the same as the default
value of the 'mplsLdpEntityAtmDefaultControlVci', however
another value may be configured."
DEFVAL { 32 }
::= { mplsLdpEntityAtmEntry 9 }
mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"VCI value of the VCC supporting unlabeled traffic.
This non-MPLS connection is used to carry unlabeled (IP)
packets. The default value is the same as the default
value of the 'mplsLdpEntityAtmDefaultControlVci', however
another value may be configured."
DEFVAL { 32 }
::= { mplsLdpEntityAtmEntry 9 }
mplsLdpEntityAtmStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmEntry 10 }
mplsLdpEntityAtmStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmEntry 10 }
mplsLdpEntityAtmRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus
object, if a session has been initiated with a Peer,
changing objects in this table will wreak havoc
with the session and interrupt traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to down, thereby explicitly
causing a session to be torn down. Then,
change objects in this entry, then set the
mplsLdpEntityAdminStatus to enable
which enables a new session to be initiated."
::= { mplsLdpEntityAtmEntry 11 }
mplsLdpEntityAtmRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the mplsLdpEntityAdminStatus
object, if a session has been initiated with a Peer,
changing objects in this table will wreak havoc
with the session and interrupt traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to down, thereby explicitly
causing a session to be torn down. Then,
change objects in this entry, then set the
mplsLdpEntityAdminStatus to enable
which enables a new session to be initiated."
::= { mplsLdpEntityAtmEntry 11 }
--
--
-- The MPLS LDP Entity ATM Label Range Table --
--MPLS LDP实体ATM标签范围表--
mplsLdpEntityAtmLRTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The MPLS LDP Entity ATM Label Range (LR) Table. The purpose of this table is to provide a mechanism for configuring a contiguous range of vpi's with a contiguous range of vci's, or a 'label range' for LDP Entities.
MPLSLDPTEntityATMLRTABLE MPLSLDPTEntityATMLENTRY MAX-ACCESS的对象类型语法序列不可访问状态当前描述“MPLS LDP实体ATM标签范围（LR）表。此表的目的是提供一种机制，用于将vpi的连续范围配置为vci的连续范围，或配置LDP实体的“标签范围”。
LDP Entities which use ATM must have at least one entry in this table.
使用ATM的LDP实体在此表中必须至少有一个条目。
There must exist at least one entry in this
table for every LDP Entity that has
'mplsLdpEntityOptionalParameters' object with
a value of 'atmSessionParameters'."
::= { mplsLdpEntityAtmObjects 2 }
There must exist at least one entry in this
table for every LDP Entity that has
'mplsLdpEntityOptionalParameters' object with
a value of 'atmSessionParameters'."
::= { mplsLdpEntityAtmObjects 2 }
mplsLdpEntityAtmLREntry OBJECT-TYPE SYNTAX MplsLdpEntityAtmLREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the LDP Entity ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message.
MPLSLDEntityATMLrentry对象类型语法MPLSLDEntityATMLrentry MAX-ACCESS不可访问状态当前说明“LDP实体ATM标签范围表中的一行。此表中的一个条目包含由配置的上限和下限VPI/VCI对表示的单个标签范围的信息。这些数据与初始化消息中使用的数据相同。
NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having LowerBound vpi/vci == 0/32, and UpperBound vpi/vci == 0/100, and a second entry for this same interface with LowerBound vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. However, there could not be a third entry with LowerBound vpi/vci == 0/200 and UpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e., both entries now have 0/200).
注：特定LDP实体的范围是唯一且不重叠的。例如，对于一个特定的LDP实体索引，可能有一个条目的下限vpi/vci==0/32，上限vpi/vci==0/100，并且该接口的第二个条目的下限vpi/vci==0/101，上限vpi/vci==0/200。但是，不可能有第三个条目的下限vpi/vci==0/200和上限vpi/vci==0/300，因为此标签范围与第二个条目重叠（即，两个条目现在都有0/200）。
A row will not become active unless a unique and non-overlapping range is specified.
除非指定了唯一且不重叠的范围，否则行将不会处于活动状态。
At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table.
特定LDP实体的至少一个标签范围条目必须包括LDP实体表中表示的默认VPI/VCI值。
A request to create a row with an overlapping
range should result in an inconsistentValue
error."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityAtmLRMinVpi,
mplsLdpEntityAtmLRMinVci
}
::= { mplsLdpEntityAtmLRTable 1 }
A request to create a row with an overlapping
range should result in an inconsistentValue
error."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityAtmLRMinVpi,
mplsLdpEntityAtmLRMinVci
}
::= { mplsLdpEntityAtmLRTable 1 }
MplsLdpEntityAtmLREntry ::= SEQUENCE {
mplsLdpEntityAtmLRMinVpi AtmVpIdentifier,
mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier,
mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier,
mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier,
mplsLdpEntityAtmLRStorageType StorageType,
mplsLdpEntityAtmLRRowStatus RowStatus
}
MplsLdpEntityAtmLREntry ::= SEQUENCE {
mplsLdpEntityAtmLRMinVpi AtmVpIdentifier,
mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier,
mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier,
mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier,
mplsLdpEntityAtmLRStorageType StorageType,
mplsLdpEntityAtmLRRowStatus RowStatus
}
mplsLdpEntityAtmLRMinVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VPI number configured for this range.
The value of zero is a valid value for the VPI portion
of the label."
::= { mplsLdpEntityAtmLREntry 1 }
mplsLdpEntityAtmLRMinVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VPI number configured for this range.
The value of zero is a valid value for the VPI portion
of the label."
::= { mplsLdpEntityAtmLREntry 1 }
mplsLdpEntityAtmLRMinVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VCI number configured for this range."
::= { mplsLdpEntityAtmLREntry 2 }
mplsLdpEntityAtmLRMinVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VCI number configured for this range."
::= { mplsLdpEntityAtmLREntry 2 }
mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS read-create
MPLSLDEntityATMLRMAXVPI对象类型语法AtmVpIdentifier MAX-ACCESS read create
STATUS current
DESCRIPTION
"The maximum VPI number configured for this range."
::= { mplsLdpEntityAtmLREntry 3 }
STATUS current
DESCRIPTION
"The maximum VPI number configured for this range."
::= { mplsLdpEntityAtmLREntry 3 }
mplsLdpEntityAtmLRMaxVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum VCI number configured for this range."
::= { mplsLdpEntityAtmLREntry 4 }
mplsLdpEntityAtmLRMaxVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum VCI number configured for this range."
::= { mplsLdpEntityAtmLREntry 4 }
mplsLdpEntityAtmLRStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmLREntry 5 }
mplsLdpEntityAtmLRStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityAtmLREntry 5 }
mplsLdpEntityAtmLRRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt traffic.
To repeat again: the recommended procedure
is to set the mplsLdpEntityAdminStatus to
down, thereby explicitly causing a session
to be torn down. Then, change objects in this
entry, then set the mplsLdpEntityAdminStatus
to enable which enables a new session
to be initiated."
::= { mplsLdpEntityAtmLREntry 6 }
mplsLdpEntityAtmLRRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt traffic.
To repeat again: the recommended procedure
is to set the mplsLdpEntityAdminStatus to
down, thereby explicitly causing a session
to be torn down. Then, change objects in this
entry, then set the mplsLdpEntityAdminStatus
to enable which enables a new session
to be initiated."
::= { mplsLdpEntityAtmLREntry 6 }
-- -- MPLS LDP ATM Session Information --
----MPLS LDP ATM会话信息--
mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 2 }
mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpAtmObjects 2 }
mplsLdpAtmSessionTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table which relates sessions in the 'mplsLdpSessionTable' and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection.
mplsLdpAtmSessionTable MplsLdpAtmSessionEntry MAX-ACCESS的对象类型语法序列不可访问状态当前说明“一个表，用于关联“mplsLdpSessionTable”中的会话及其标签范围交点。LDP实体和使用ATM作为底层介质的LDP对等方之间可能存在一个或多个标签范围交叉点。每行表示一个标签范围交点。
This table cannot use the 'AUGMENTS'
clause because there is not necessarily
a one-to-one mapping between this table
and the mplsLdpSessionTable."
::= { mplsLdpAtmSessionObjects 1 }
This table cannot use the 'AUGMENTS'
clause because there is not necessarily
a one-to-one mapping between this table
and the mplsLdpSessionTable."
::= { mplsLdpAtmSessionObjects 1 }
mplsLdpAtmSessionEntry OBJECT-TYPE SYNTAX MplsLdpAtmSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer.
mplsLdpAtmSessionEntry对象类型语法mplsLdpAtmSessionEntry MAX-ACCESS not accessible STATUS current DESCRIPTION“此表中的条目表示LDP实体和LDP对等方之间单个标签范围交叉点的信息。
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpSessionAtmLRLowerBoundVpi,
mplsLdpSessionAtmLRLowerBoundVci
}
::= { mplsLdpAtmSessionTable 1 }
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpSessionAtmLRLowerBoundVpi,
mplsLdpSessionAtmLRLowerBoundVci
}
::= { mplsLdpAtmSessionTable 1 }
MplsLdpAtmSessionEntry ::= SEQUENCE {
mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier,
mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier,
mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier,
MplsLdpAtmSessionEntry ::= SEQUENCE {
mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier,
mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier,
mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier,
mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier }
MPLSLDPSessionAMLRUPPERBONDVCI MplsAtmVcIdentifier}
mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VPI number for this range."
::= { mplsLdpAtmSessionEntry 1 }
mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VPI number for this range."
::= { mplsLdpAtmSessionEntry 1 }
mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VCI number for this range."
::= { mplsLdpAtmSessionEntry 2 }
mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum VCI number for this range."
::= { mplsLdpAtmSessionEntry 2 }
mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum VPI number for this range."
::= { mplsLdpAtmSessionEntry 3 }
mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum VPI number for this range."
::= { mplsLdpAtmSessionEntry 3 }
mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum VCI number for this range."
::= { mplsLdpAtmSessionEntry 4 }
mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum VCI number for this range."
::= { mplsLdpAtmSessionEntry 4 }
--**************************************************************
-- Module Conformance Statement
--**************************************************************
--**************************************************************
-- Module Conformance Statement
--**************************************************************
mplsLdpAtmGroups
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 }
mplsLdpAtmGroups
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 }
mplsLdpAtmCompliances
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 }
mplsLdpAtmCompliances
OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 }
-- -- Full Compliance --
----完全遵守--
mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpAtmGroup
}
mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpAtmGroup
}
OBJECT mplsLdpEntityAtmRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityAtmRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityAtmLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityAtmLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
::= { mplsLdpAtmCompliances 1 }
::= { mplsLdpAtmCompliances 1 }
-- -- Read-Only Compliance --
----只读遵从性--
mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpAtmGroup
}
mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpAtmGroup
}
OBJECT mplsLdpEntityAtmIfIndexOrZero MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityAtMiFindexorZero最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmMergeCap
对象MPLSLDEntityATMMERGECAP
MIN-ACCESS read-only DESCRIPTION "Write access is not required."
MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmVcDirectionality MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMVCD方向性最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmLsrConnectivity MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMLSRConnectivity最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmDefaultControlVpi MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityAtMDefaultControlVPI最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmDefaultControlVci MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMDefaultControlVCI最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmUnlabTrafVpi MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityAtMunlab Traffpi最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmUnlabTrafVci MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityAtMunlab TravCI最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMStorageType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象MPLSLDEntityAtmRowstatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT mplsLdpEntityAtmLRMaxVpi MIN-ACCESS read-only
对象MPLSLDEntityATMLRMAXVPI最小访问只读
DESCRIPTION "Write access is not required."
说明“不需要写访问权限。”
OBJECT mplsLdpEntityAtmLRMaxVci MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMLRMAXVCI最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmLRStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityATMLRStorageType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityAtmLRRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象MPLSLDEntityATMLRROWSTATUS语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，并且active是需要支持的唯一状态。”
::= { mplsLdpAtmCompliances 2 }
::= { mplsLdpAtmCompliances 2 }
-- -- units of conformance --
----一致性单位--
mplsLdpAtmGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityAtmIfIndexOrZero,
mplsLdpEntityAtmMergeCap,
mplsLdpEntityAtmLRComponents,
mplsLdpEntityAtmVcDirectionality,
mplsLdpEntityAtmLsrConnectivity,
mplsLdpEntityAtmDefaultControlVpi,
mplsLdpEntityAtmDefaultControlVci,
mplsLdpEntityAtmUnlabTrafVpi,
mplsLdpEntityAtmUnlabTrafVci,
mplsLdpEntityAtmStorageType,
mplsLdpEntityAtmRowStatus,
mplsLdpEntityAtmLRMaxVpi,
mplsLdpEntityAtmLRMaxVci,
mplsLdpEntityAtmLRStorageType,
mplsLdpEntityAtmLRRowStatus,
mplsLdpSessionAtmLRUpperBoundVpi,
mplsLdpSessionAtmLRUpperBoundVci
mplsLdpAtmGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityAtmIfIndexOrZero,
mplsLdpEntityAtmMergeCap,
mplsLdpEntityAtmLRComponents,
mplsLdpEntityAtmVcDirectionality,
mplsLdpEntityAtmLsrConnectivity,
mplsLdpEntityAtmDefaultControlVpi,
mplsLdpEntityAtmDefaultControlVci,
mplsLdpEntityAtmUnlabTrafVpi,
mplsLdpEntityAtmUnlabTrafVci,
mplsLdpEntityAtmStorageType,
mplsLdpEntityAtmRowStatus,
mplsLdpEntityAtmLRMaxVpi,
mplsLdpEntityAtmLRMaxVci,
mplsLdpEntityAtmLRStorageType,
mplsLdpEntityAtmLRRowStatus,
mplsLdpSessionAtmLRUpperBoundVpi,
mplsLdpSessionAtmLRUpperBoundVci
} STATUS current
}现状
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using ATM as the Layer 2."
::= { mplsLdpAtmGroups 1 }
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using ATM as the Layer 2."
::= { mplsLdpAtmGroups 1 }
END
终止
This MIB Module MUST be supported if LDP uses FRAME RELAY as the Layer 2 medium. There are three tables in this MIB Module. Two tables are to configure LDP for using Frame Relay. These tables are the mplsLdpEntityFrameRelayTable and the mplsLdpEntityFrameRelayLRTable. The third table, mplsLdpFrameRelaySessionTable, is a read-only table. This MIB Module IMPORTS the DLCI TEXTUAL-CONVENTION from [RFC2115].
如果LDP使用帧中继作为第2层介质，则必须支持此MIB模块。此MIB模块中有三个表。两个表用于配置LDP以使用帧中继。这些表是MPLSLDEntityFrameRelayTable和MPLSLDEntityFrameRelayTable。第三个表mplsLdpFrameRelaySessionTable是只读表。此MIB模块从[RFC2115]导入DLCI文本约定。
The mplsLdpEntityFrameRelayTable provides a way to configure information which would be contained in the "Optional Parameter" portion of an LDP PDU Initialization Message.
MPLSLDEntityFrameRelayTable提供了一种配置信息的方法，这些信息将包含在LDP PDU初始化消息的“可选参数”部分中。
The mplsLdpEntityFrameRelayLRTable provides a way to configure information which would be contained in the "Frame Relay Label Range Components" portion of an LDP PDU Intialization Message, see [RFC3034] and [RFC3036].
MPLSLDEntityFrameRelaylTable提供了一种配置信息的方法，这些信息将包含在LDP PDU初始化消息的“帧中继标签范围组件”部分中，请参阅[RFC3034]和[RFC3036]。
The mplsLdpFrameRelaySessionTable is a table which contains session information specific to Frame Relay.
mplsLdpFrameRelaySessionTable是一个包含特定于帧中继的会话信息的表。
MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, MODULE-IDENTITY, Unsigned32 FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
从SNMPv2 SMI中导入对象类型、模块标识、未签名32--[RFC2578]模块符合性、从SNMPv2 CONF中导入对象组--[RFC2580]
RowStatus, StorageType
行状态，存储类型
FROM SNMPv2-TC -- [RFC2579]
来自SNMPv2 TC--[RFC2579]
DLCI FROM FRAME-RELAY-DTE-MIB -- [RFC2115]
来自帧中继DTE-MIB的DLCI--[RFC2115]
InterfaceIndexOrZero FROM IF-MIB -- [RFC2020]
来自IF-MIB的接口索引或零--[RFC2020]
mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811]
来自MPLS-TC-STD-MIB的mplsStdMIB--[RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId FROM MPLS-LDP-STD-MIB -- [RFC3813] ;
MPLS-LDP-STD-MIB中的MPLSLDEntityLDPID、MPLSLDEntityIndex、MPLSLDPeerldPID--[RFC3813]；
mplsLdpFrameRelayStdMIB MODULE-IDENTITY LAST-UPDATED "200406030000Z" -- June 3, 2004 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" CONTACT-INFO "Joan Cucchiara (jcucchiara@mindspring.com) Marconi Communications, Inc.
MPLSDLDPFrameRelaysAdmin模块标识最后更新的“200406030000Z”-2004年6月3日组织“多协议标签交换（mpls）工作组”联系人信息“Joan Cucchiara”(jcucchiara@mindspring.com)马可尼通讯公司。
Hans Sjostrand (hans@ipunplugged.com) ipUnplugged
汉斯·索斯特兰德(hans@ipunplugged.com)拔下插头
James V. Luciani (james_luciani@mindspring.com) Marconi Communications, Inc.
詹姆斯诉卢西亚尼（詹姆斯）_luciani@mindspring.com)马可尼通讯公司。
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net " DESCRIPTION "Copyright (C) The Internet Society (year). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
MPLS工作组，电子邮件：mpls@uu.net“说明”版权所有（C）互联网协会（年）。该MIB模块的初始版本发布在RFC 3815中。有关完整的法律通知，请参阅RFC本身或参阅：http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing Frame Relay as the Layer 2 media."
此MIB包含用于配置和监视多协议标签交换（MPLS）、标签分发协议（LDP）的托管对象定义，使用帧中继作为第2层介质。”
REVISION "200406030000Z" -- June 6, 2004 DESCRIPTION "Initial version published as part of RFC 3815."
修订版“200406030000Z”-2004年6月6日描述“作为RFC 3815的一部分发布的初始版本”
::= { mplsStdMIB 6 }
::= { mplsStdMIB 6 }
--****************************************************************
--****************************************************************
mplsLdpFrameRelayObjects OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 1 }
mplsLdpFrameRelayObjects OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 1 }
mplsLdpFrameRelayConformance OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 2 }
mplsLdpFrameRelayConformance OBJECT IDENTIFIER
::= { mplsLdpFrameRelayStdMIB 2 }
--****************************************************************
-- MPLS LDP Frame Relay Objects
--****************************************************************
--****************************************************************
-- MPLS LDP Frame Relay Objects
--****************************************************************
-- -- Ldp Entity Objects for Frame Relay --
----帧中继的Ldp实体对象--
mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 1 }
mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 1 }
mplsLdpEntityFrameRelayTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains Frame Relay specific information which could be used in the 'Optional Parameters' and other Frame Relay specific information.
MPLSLDEntityFrameRelayTable对象类型语法MPLSLDEntry MAX-ACCESS不可访问状态当前说明“此表包含帧中继特定信息，可用于“可选参数”和其他帧中继特定信息。
This table 'sparse augments' the mplsLdpEntityTable
when Frame Relay is the Layer 2 medium."
::= { mplsLdpEntityFrameRelayObjects 1 }
This table 'sparse augments' the mplsLdpEntityTable
when Frame Relay is the Layer 2 medium."
::= { mplsLdpEntityFrameRelayObjects 1 }
mplsLdpEntityFrameRelayEntry OBJECT-TYPE SYNTAX MplsLdpEntityFrameRelayEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents the Frame Relay optional parameters associated with the LDP entity." INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex
MPLSLDEntityFrameRelayEntry对象类型语法MPLSLDEntityFrameRelayEntry MAX-ACCESS不可访问状态当前描述“此表中的一个条目表示与LDP实体关联的帧中继可选参数。”索引{MPLSLDEntityLDPID，MPLSLDEntityIndex
}
::= { mplsLdpEntityFrameRelayTable 1 }
}
::= { mplsLdpEntityFrameRelayTable 1 }
MplsLdpEntityFrameRelayEntry ::= SEQUENCE {
mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero,
mplsLdpEntityFrameRelayMergeCap INTEGER,
mplsLdpEntityFrameRelayLRComponents Unsigned32,
mplsLdpEntityFrameRelayVcDirectionality INTEGER,
mplsLdpEntityFrameRelayStorageType StorageType,
mplsLdpEntityFrameRelayRowStatus RowStatus
}
MplsLdpEntityFrameRelayEntry ::= SEQUENCE {
mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero,
mplsLdpEntityFrameRelayMergeCap INTEGER,
mplsLdpEntityFrameRelayLRComponents Unsigned32,
mplsLdpEntityFrameRelayVcDirectionality INTEGER,
mplsLdpEntityFrameRelayStorageType StorageType,
mplsLdpEntityFrameRelayRowStatus RowStatus
}
mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "This value represents either the InterfaceIndex of the 'ifLayer' where the Frame Relay Labels 'owned' by this entry were created, or 0 (zero). The value of zero means that the InterfaceIndex is not known. For example, if the InterfaceIndex is created subsequent to the Frame Relay Label's creation, then it would not be known. However, if the InterfaceIndex is known, then it must be represented by this value.
MPLSLDEntityFrameRelayFindExorZero对象类型语法InterfaceIndexOrZero MAX-ACCESS读取创建状态当前描述“此值表示创建此条目“拥有”的帧中继标签的“iLayer”的InterfaceIndex或0（零）。零的值表示InterfaceIndex未知。例如，如果InterfaceIndex是在帧中继标签创建之后创建的，则它将未知。但是，如果InterfaceIndex已知，则它必须由该值表示。
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an Frame Relay Label is
being used in forwarding data, then the value of this
object MUST be the InterfaceIndex."
::= { mplsLdpEntityFrameRelayEntry 1 }
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex. If an Frame Relay Label is
being used in forwarding data, then the value of this
object MUST be the InterfaceIndex."
::= { mplsLdpEntityFrameRelayEntry 1 }
mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE
SYNTAX INTEGER {
notSupported(0),
supported(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This represents whether or not the Frame Relay merge
capability is supported. This is the EXACT value for the
Frame Relay Session Parameter, field M (for Frame Relay
Merge Capabilities). The Frame Relay Session Parameter
is an optional parameter in the Initialization Message.
mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE
SYNTAX INTEGER {
notSupported(0),
supported(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This represents whether or not the Frame Relay merge
capability is supported. This is the EXACT value for the
Frame Relay Session Parameter, field M (for Frame Relay
Merge Capabilities). The Frame Relay Session Parameter
is an optional parameter in the Initialization Message.
The description from rfc3036.txt is: 'M, Frame Relay Merge Capabilities Specifies the merge capabilities of a Frame Relay switch. The following values are supported in this version of the specification:
rfc3036.txt中的描述是：“M，帧中继合并功能指定帧中继交换机的合并功能。此版本的规范支持以下值：
Value Meaning
价值意义
0 Merge not supported 1 Merge supported
不支持0合并不支持1合并
Non-merge and merge Frame Relay LSRs may freely interoperate.'
非合并和合并帧中继LSR可以自由互操作。”
Please refer to the following reference for a
complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 2 }
Please refer to the following reference for a
complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 2 }
mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityFrameRelayLRTable which correspond to this entry.
MPLSLDEntityFrameRelaylRComponents对象类型语法Unsigned32（1..65535）MAX-ACCESS只读状态当前描述“初始化消息中标签范围组件的数量。这还表示MPLSLDEntityFrameRelaylTable中与此条目对应的条目数。
This is the EXACT value for the Frame Relay Session Parameter, field N (for Number of label range components). The Frame Relay Session Parameter is an optional parameter in the Initialization Message.
这是帧中继会话参数字段N（用于标签范围组件的数量）的精确值。帧中继会话参数是初始化消息中的可选参数。
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'N, Number of label range components Specifies the number of Frame Relay Label Range Components included in the TLV.'
'N，Number of label range components指定TLV中包含的帧中继标签范围组件的数量。'
Please refer to the following reference for a complete description of this feature." REFERENCE "RFC3036, LDP Specification, Section 3.5.3
有关此功能的完整说明，请参考以下参考。“参考”RFC3036，LDP规范，第3.5.3节
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 3 }
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 3 }
mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
SYNTAX INTEGER {
bidirectional(0),
unidirection(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the value of this object is 'bidirectional(0)', then
the LSR supports the use of a given DLCI as a label for
both directions independently. If the value of
this object is 'unidirectional(1)', then the LSR
uses the given DLCI as a label in only one direction.
mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
SYNTAX INTEGER {
bidirectional(0),
unidirection(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the value of this object is 'bidirectional(0)', then
the LSR supports the use of a given DLCI as a label for
both directions independently. If the value of
this object is 'unidirectional(1)', then the LSR
uses the given DLCI as a label in only one direction.
This is the EXACT value for the Frame Relay Session Parameter, field D (for VC Directionality). The Frame Relay Session Parameter is an optional parameter in the Initialization Message.
这是帧中继会话参数字段D（用于VC方向性）的精确值。帧中继会话参数是初始化消息中的可选参数。
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can support the use of a given DLCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning a given DLCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered DLCIs in the range as labels. The system with the smaller LDP Identifier may assign only even-numbered DLCIs in the range as labels.'
'D，VC Directionality值0指定双向VC功能，这意味着LSR可以支持将给定的DLCI单独用作两个链路方向的标签。值1指定单向VC功能，这意味着给定的DLCI可能仅出现在链接上一个方向的标签映射中。当其中一个或两个对等点指定单向VC功能时，两个LSR对链路使用单向VC标签分配，如下所示。LSR将其LDP标识符作为无符号整数进行比较。具有较大LDP标识符的LSR可以仅将范围内的奇数编号DLCI分配为标签。具有较小LDP标识符的系统只能将范围内的偶数DLCI指定为标签。”
Please refer to the following reference for a
complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 4 }
Please refer to the following reference for a
complete description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayEntry 4 }
mplsLdpEntityFrameRelayStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayEntry 5 }
mplsLdpEntityFrameRelayStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayEntry 5 }
mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt
traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to
down, thereby explicitly causing a
session to be torn down. Then,
change objects in this entry, then set
the mplsLdpEntityAdminStatus
to enable which enables a new session
to be initiated."
::= { mplsLdpEntityFrameRelayEntry 6 }
mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt
traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to
down, thereby explicitly causing a
session to be torn down. Then,
change objects in this entry, then set
the mplsLdpEntityAdminStatus
to enable which enables a new session
to be initiated."
::= { mplsLdpEntityFrameRelayEntry 6 }
-- -- Frame Relay Label Range Components --
----帧中继标签范围组件--
mplsLdpEntityFrameRelayLRTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about the
MPLSLDEntityFrameRelaylRTable对象类型语法MPLSLDEntityFrameRelaylRentry MAX-ACCESS不可访问状态当前描述“此表包含有关
Optional Parameters for the Frame Relay Session in the LDP Initialization Message, specifically it contains information about the Frame Relay Label Range Components.
LDP初始化消息中帧中继会话的可选参数，特别是它包含有关帧中继标签范围组件的信息。
If the value of the object
'mplsLdpEntityOptionalParameters' contains the
value of 'frameRelaySessionParameters(3)' then
there must be at least one corresponding entry
in this table."
::= { mplsLdpEntityFrameRelayObjects 2 }
If the value of the object
'mplsLdpEntityOptionalParameters' contains the
value of 'frameRelaySessionParameters(3)' then
there must be at least one corresponding entry
in this table."
::= { mplsLdpEntityFrameRelayObjects 2 }
mplsLdpEntityFrameRelayLREntry OBJECT-TYPE
SYNTAX MplsLdpEntityFrameRelayLREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents the Frame Relay
Label Range Component associated with the LDP entity."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityFrameRelayLRMinDlci
}
::= { mplsLdpEntityFrameRelayLRTable 1 }
mplsLdpEntityFrameRelayLREntry OBJECT-TYPE
SYNTAX MplsLdpEntityFrameRelayLREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents the Frame Relay
Label Range Component associated with the LDP entity."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityFrameRelayLRMinDlci
}
::= { mplsLdpEntityFrameRelayLRTable 1 }
MplsLdpEntityFrameRelayLREntry ::= SEQUENCE {
mplsLdpEntityFrameRelayLRMinDlci DLCI,
mplsLdpEntityFrameRelayLRMaxDlci DLCI,
mplsLdpEntityFrameRelayLRLen INTEGER,
mplsLdpEntityFrameRelayLRStorageType StorageType,
mplsLdpEntityFrameRelayLRRowStatus RowStatus
}
MplsLdpEntityFrameRelayLREntry ::= SEQUENCE {
mplsLdpEntityFrameRelayLRMinDlci DLCI,
mplsLdpEntityFrameRelayLRMaxDlci DLCI,
mplsLdpEntityFrameRelayLRLen INTEGER,
mplsLdpEntityFrameRelayLRStorageType StorageType,
mplsLdpEntityFrameRelayLRRowStatus RowStatus
}
mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The lower bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Minimum DLCI field. The value
of zero is valid for the minimum DLCI field of
the label."
REFERENCE
"RFC3034, Use of Label Switching on Frame Relay
Networks Specification."
::= { mplsLdpEntityFrameRelayLREntry 1 }
mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The lower bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Minimum DLCI field. The value
of zero is valid for the minimum DLCI field of
the label."
REFERENCE
"RFC3034, Use of Label Switching on Frame Relay
Networks Specification."
::= { mplsLdpEntityFrameRelayLREntry 1 }
mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upper bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Maximum DLCI field."
::= { mplsLdpEntityFrameRelayLREntry 2 }
mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upper bound which is supported. This value
should be the same as that in the Frame Relay Label
Range Component's Maximum DLCI field."
::= { mplsLdpEntityFrameRelayLREntry 2 }
mplsLdpEntityFrameRelayLRLen OBJECT-TYPE
SYNTAX INTEGER {
tenDlciBits(0),
twentyThreeDlciBits(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the length of the DLCI bits.
mplsLdpEntityFrameRelayLRLen OBJECT-TYPE
SYNTAX INTEGER {
tenDlciBits(0),
twentyThreeDlciBits(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the length of the DLCI bits.
This is the EXACT value for the Len field of the Frame Relay Label Range Component.
这是帧中继标签范围组件的Len字段的精确值。
The description from rfc3036.txt is:
rfc3036.txt中的说明如下：
'Len This field specifies the number of bits of the DLCI. The following values are supported:
'Len此字段指定DLCI的位数。支持以下值：
Len DLCI bits
Len-DLCI位
0 10 2 23
0 10 2 23
Len values 1 and 3 are reserved.'
保留Len值1和3。”
Please refer to the following reference for a complete
description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayLREntry 3 }
Please refer to the following reference for a complete
description of this feature."
REFERENCE
"RFC3036, LDP Specification, Section 3.5.3
Initialization Message."
::= { mplsLdpEntityFrameRelayLREntry 3 }
mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION
MPLSLDEntityFrameRelaylRStorageType对象类型语法StorageType MAX-ACCESS读取创建状态当前说明
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayLREntry 4 }
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityFrameRelayLREntry 4 }
mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt
traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to down, thereby
explicitly causing a session to be torn down. Then,
change objects in this entry, then set the
mplsLdpEntityAdminStatus to enable which enables
a new session to be initiated."
::= { mplsLdpEntityFrameRelayLREntry 5 }
mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any time,
however, as described in detail in the section
entitled, 'Changing Values After Session
Establishment', and again described in the
DESCRIPTION clause of the
mplsLdpEntityAdminStatus object,
if a session has been initiated with a Peer,
changing objects in this table will
wreak havoc with the session and interrupt
traffic. To repeat again:
the recommended procedure is to set the
mplsLdpEntityAdminStatus to down, thereby
explicitly causing a session to be torn down. Then,
change objects in this entry, then set the
mplsLdpEntityAdminStatus to enable which enables
a new session to be initiated."
::= { mplsLdpEntityFrameRelayLREntry 5 }
-- -- MPLS LDP Frame Relay Session Information --
----MPLS LDP帧中继会话信息--
mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 2 }
mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::=
{ mplsLdpFrameRelayObjects 2 }
mplsLdpFrameRelaySessionTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Frame Relay label range intersections between the LDP Entities and LDP Peers. Each row represents a single label range intersection.
mplsLdpFrameRelaySessionTable对象类型语法MplsLdpFrameRelaySessionEntry MAX-ACCESS不可访问状态当前描述“LDP实体和LDP对等方之间帧中继标签范围交叉点的表。每行表示单个标签范围交叉点。
NOTE: this table cannot use the 'AUGMENTS'
注意：此表不能使用“增强”
clause because there is not necessarily a one-to-one
mapping between this table and the
mplsLdpSessionTable."
::= { mplsLdpFrameRelaySessionObjects 1 }
clause because there is not necessarily a one-to-one
mapping between this table and the
mplsLdpSessionTable."
::= { mplsLdpFrameRelaySessionObjects 1 }
mplsLdpFrameRelaySessionEntry OBJECT-TYPE SYNTAX MplsLdpFrameRelaySessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer.
MPLSLPFrameRelaysessionEntry对象类型语法MPLSDPFrameRelaysessionEntry MAX-ACCESS不可访问状态当前描述“此表中的条目表示LDP实体和LDP对等方之间单个标签范围交叉点的信息。
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpFrameRelaySessionMinDlci
}
::= { mplsLdpFrameRelaySessionTable 1 }
The information contained in a row is read-only."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpPeerLdpId,
mplsLdpFrameRelaySessionMinDlci
}
::= { mplsLdpFrameRelaySessionTable 1 }
MplsLdpFrameRelaySessionEntry ::= SEQUENCE {
mplsLdpFrameRelaySessionMinDlci DLCI,
mplsLdpFrameRelaySessionMaxDlci DLCI,
mplsLdpFrameRelaySessionLen INTEGER
}
MplsLdpFrameRelaySessionEntry ::= SEQUENCE {
mplsLdpFrameRelaySessionMinDlci DLCI,
mplsLdpFrameRelaySessionMaxDlci DLCI,
mplsLdpFrameRelaySessionLen INTEGER
}
mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The lower bound of DLCIs which are supported.
The value of zero is a valid value for the
minimum DLCI field of the label."
REFERENCE
"RFC3034, Use of Label Switching on Frame Relay
Networks Specification."
::= { mplsLdpFrameRelaySessionEntry 1 }
mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The lower bound of DLCIs which are supported.
The value of zero is a valid value for the
minimum DLCI field of the label."
REFERENCE
"RFC3034, Use of Label Switching on Frame Relay
Networks Specification."
::= { mplsLdpFrameRelaySessionEntry 1 }
mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The upper bound of DLCIs which are supported."
::= { mplsLdpFrameRelaySessionEntry 2 }
mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE
SYNTAX DLCI
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The upper bound of DLCIs which are supported."
::= { mplsLdpFrameRelaySessionEntry 2 }
mplsLdpFrameRelaySessionLen OBJECT-TYPE
SYNTAX INTEGER {
tenDlciBits(0),
twentyThreeDlciBits(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the DLCI bits."
::= { mplsLdpFrameRelaySessionEntry 3 }
mplsLdpFrameRelaySessionLen OBJECT-TYPE
SYNTAX INTEGER {
tenDlciBits(0),
twentyThreeDlciBits(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the DLCI bits."
::= { mplsLdpFrameRelaySessionEntry 3 }
--****************************************************************
-- Module Conformance Statement
--****************************************************************
--****************************************************************
-- Module Conformance Statement
--****************************************************************
mplsLdpFrameRelayGroups
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 }
mplsLdpFrameRelayGroups
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 }
mplsLdpFrameRelayCompliances
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 }
mplsLdpFrameRelayCompliances
OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 }
-- -- Full Compliance --
----完全遵守--
mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpFrameRelayGroup
}
mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpFrameRelayGroup
}
OBJECT mplsLdpEntityFrameRelayRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityFrameRelayRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityFrameRelayLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityFrameRelayLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
::= { mplsLdpFrameRelayCompliances 1 }
::= { mplsLdpFrameRelayCompliances 1 }
-- -- Read-Only Compliance --
----只读遵从性--
mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpFrameRelayGroup
}
mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpFrameRelayGroup
}
OBJECT mplsLdpEntityFrameRelayIfIndexOrZero MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelayFindExorZero最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayMergeCap MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelayMergeCap最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayVcDirectionality MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelayVCD方向性最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelayStorageType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象MPLSLDEntityFrameRelayRowstatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
OBJECT mplsLdpEntityFrameRelayLRMaxDlci MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelaylRMAXDLCI最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayLRLen MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelaylRLEN最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayLRStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityFrameRelaylRStorageType最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityFrameRelayLRRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active is the
only status that needs to be supported."
::= { mplsLdpFrameRelayCompliances 2 }
OBJECT mplsLdpEntityFrameRelayLRRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active is the
only status that needs to be supported."
::= { mplsLdpFrameRelayCompliances 2 }
-- -- units of conformance --
----一致性单位--
mplsLdpFrameRelayGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityFrameRelayIfIndexOrZero,
mplsLdpEntityFrameRelayMergeCap,
mplsLdpEntityFrameRelayLRComponents,
mplsLdpEntityFrameRelayVcDirectionality,
mplsLdpEntityFrameRelayStorageType,
mplsLdpEntityFrameRelayRowStatus,
mplsLdpEntityFrameRelayLRMaxDlci,
mplsLdpEntityFrameRelayLRLen,
mplsLdpEntityFrameRelayLRStorageType,
mplsLdpEntityFrameRelayLRRowStatus,
mplsLdpFrameRelaySessionMaxDlci,
mplsLdpFrameRelaySessionLen
}
STATUS current
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using Frame Relay as the Layer 2."
::= { mplsLdpFrameRelayGroups 1 }
mplsLdpFrameRelayGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityFrameRelayIfIndexOrZero,
mplsLdpEntityFrameRelayMergeCap,
mplsLdpEntityFrameRelayLRComponents,
mplsLdpEntityFrameRelayVcDirectionality,
mplsLdpEntityFrameRelayStorageType,
mplsLdpEntityFrameRelayRowStatus,
mplsLdpEntityFrameRelayLRMaxDlci,
mplsLdpEntityFrameRelayLRLen,
mplsLdpEntityFrameRelayLRStorageType,
mplsLdpEntityFrameRelayLRRowStatus,
mplsLdpFrameRelaySessionMaxDlci,
mplsLdpFrameRelaySessionLen
}
STATUS current
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using Frame Relay as the Layer 2."
::= { mplsLdpFrameRelayGroups 1 }
END
终止
This MIB Module MUST be supported if LDP uses a Per Platform Label Space. This MIB Module contains a Label Range (LR) table for configuring MPLS Generic Label Ranges. This table is mplsLdpEntityGenericLRTable. Although the LDP Specification does not provide a way for configuring Label Ranges for Generic Labels, the MIB does provide a way to reserve a range of generic labels because this was thought to be useful by the working group.
如果LDP使用每平台标签空间，则必须支持此MIB模块。此MIB模块包含用于配置MPLS通用标签范围的标签范围（LR）表。此表是MPLSLDEntityGenericlrTable。尽管LDP规范没有提供为通用标签配置标签范围的方法，但MIB确实提供了保留一系列通用标签的方法，因为工作组认为这是有用的。
MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN
MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, MODULE-IDENTITY, Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
从SNMPv2 SMI--[RFC2578]导入对象类型、模块标识、无符号32
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
SNMPv2配置文件[RFC2580]中的模块合规性、对象组
RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579]
SNMPv2 TC中的行状态、存储类型--[RFC2579]
InterfaceIndexOrZero FROM IF-MIB -- [RFC2020]
来自IF-MIB的接口索引或零--[RFC2020]
mplsStdMIB FROM MPLS-TC-STD-MIB -- [RFC3811]
来自MPLS-TC-STD-MIB的mplsStdMIB--[RFC3811]
mplsLdpEntityLdpId, mplsLdpEntityIndex FROM MPLS-LDP-STD-MIB -- [RFC3813] ;
来自MPLS-LDP-STD-MIB的MPLSLDEntityLDPID、MPLSLDEntityIndex--[RFC3813]；
mplsLdpGenericStdMIB MODULE-IDENTITY LAST-UPDATED "200406030000Z" -- June 6, 2004 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" CONTACT-INFO "Joan Cucchiara (jcucchiara@mindspring.com) Marconi Communications, Inc.
MPLSLDGenericsTDMIB MODULE-IDENTITY上次更新的“200406030000Z”-2004年6月6日组织“多协议标签交换（mpls）工作组”联系人信息“Joan Cucchiara”(jcucchiara@mindspring.com)马可尼通讯公司。
Hans Sjostrand (hans@ipunplugged.com) ipUnplugged
汉斯·索斯特兰德(hans@ipunplugged.com)拔下插头
James V. Luciani (james_luciani@mindspring.com) Marconi Communications, Inc.
詹姆斯诉卢西亚尼（詹姆斯）_luciani@mindspring.com)马可尼通讯公司。
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
Working Group Chairs:
George Swallow, email: swallow@cisco.com
Loa Andersson, email: loa@pi.se
MPLS Working Group, email: mpls@uu.net " DESCRIPTION "Copyright (C) The Internet Society (year). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
MPLS工作组，电子邮件：mpls@uu.net“说明”版权所有（C）互联网协会（年）。该MIB模块的初始版本发布在RFC 3815中。有关完整的法律通知，请参阅RFC本身或参阅：http://www.ietf.org/copyrights/ianamib.html
This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing ethernet as the Layer 2 media." REVISION "200406030000Z" -- June 6, 2004 DESCRIPTION "Initial version published as part of RFC 3815."
此MIB包含用于配置和监控多协议标签交换（MPLS）、标签分发协议（LDP）的托管对象定义，使用以太网作为第2层介质。“修订版”200406030000Z--2004年6月6日描述“作为RFC 3815的一部分发布的初始版本”
::= { mplsStdMIB 7 }
::= { mplsStdMIB 7 }
--****************************************************************
--****************************************************************
mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 }
mplsLdpGenericObjects
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 }
mplsLdpGenericConformance
OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 }
--****************************************************************
-- MPLS LDP GENERIC Objects
--****************************************************************
--****************************************************************
-- MPLS LDP GENERIC Objects
--****************************************************************
-- -- Ldp Entity Objects for Generic Labels --
----通用标签的Ldp实体对象--
mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::=
{ mplsLdpGenericObjects 1 }
mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::=
{ mplsLdpGenericObjects 1 }
-- -- The MPLS LDP Entity Generic Label Range Table --
----MPLS LDP实体通用标签范围表--
mplsLdpEntityGenericLRTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLdpEntityGenericLREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The MPLS LDP Entity Generic Label Range (LR) Table.
MPLSLDPTEntityGenericlrTable对象类型语法MPLSLDPTEntityGenericlrEntry MAX-ACCESS不可访问状态当前描述“MPLS LDP实体通用标签范围（LR）表”。
The purpose of this table is to provide a mechanism for configurating a contiguous range of generic labels, or a 'label range' for LDP Entities.
本表的目的是提供一种机制，用于配置连续范围的通用标签，或LDP实体的“标签范围”。
LDP Entities which use Generic Labels must have at least
one entry in this table. In other words, this table
'extends' the mpldLdpEntityTable for Generic Labels."
::= { mplsLdpEntityGenericObjects 1 }
LDP Entities which use Generic Labels must have at least
one entry in this table. In other words, this table
'extends' the mpldLdpEntityTable for Generic Labels."
::= { mplsLdpEntityGenericObjects 1 }
mplsLdpEntityGenericLREntry OBJECT-TYPE SYNTAX MplsLdpEntityGenericLREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the LDP Entity Generic Label Range (LR) Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds pairs. NOTE: there is NO corresponding LDP message which relates to the information in this table, however, this table does provide a way for a user to 'reserve' a generic label range.
MPLSLDEntityGenericlRentry对象类型语法MPLSLDEntityGenericlRentry MAX-ACCESS不可访问状态当前描述“LDP实体通用标签范围（LR）中的一行”表。此表中的一个条目包含由配置的上限和下限对表示的单个标签范围的信息。注意：没有与此表中的信息相关的相应LDP消息，但是，此表确实为用户“保留”通用标签范围提供了一种方法。
NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping.
注：特定LDP实体的范围是唯一且不重叠的。
A row will not be created unless a unique and
non-overlapping range is specified."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityGenericLRMin,
mplsLdpEntityGenericLRMax
}
::= { mplsLdpEntityGenericLRTable 1 }
A row will not be created unless a unique and
non-overlapping range is specified."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityGenericLRMin,
mplsLdpEntityGenericLRMax
}
::= { mplsLdpEntityGenericLRTable 1 }
MplsLdpEntityGenericLREntry ::= SEQUENCE {
mplsLdpEntityGenericLRMin Unsigned32,
mplsLdpEntityGenericLRMax Unsigned32,
mplsLdpEntityGenericLabelSpace INTEGER,
MplsLdpEntityGenericLREntry ::= SEQUENCE {
mplsLdpEntityGenericLRMin Unsigned32,
mplsLdpEntityGenericLRMax Unsigned32,
mplsLdpEntityGenericLabelSpace INTEGER,
mplsLdpEntityGenericIfIndexOrZero InterfaceIndexOrZero, mplsLdpEntityGenericLRStorageType StorageType, mplsLdpEntityGenericLRRowStatus RowStatus }
mplsldEntityGenericFindExorZero接口索引零，mplsldEntityGenericlStorageType存储类型，mplsldEntityGenericlRowStatus行状态}
mplsLdpEntityGenericLRMin OBJECT-TYPE
SYNTAX Unsigned32(0..1048575)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum label configured for this range."
::= { mplsLdpEntityGenericLREntry 1 }
mplsLdpEntityGenericLRMin OBJECT-TYPE
SYNTAX Unsigned32(0..1048575)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The minimum label configured for this range."
::= { mplsLdpEntityGenericLREntry 1 }
mplsLdpEntityGenericLRMax OBJECT-TYPE
SYNTAX Unsigned32(0..1048575)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The maximum label configured for this range."
::= { mplsLdpEntityGenericLREntry 2 }
mplsLdpEntityGenericLRMax OBJECT-TYPE
SYNTAX Unsigned32(0..1048575)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The maximum label configured for this range."
::= { mplsLdpEntityGenericLREntry 2 }
mplsLdpEntityGenericLabelSpace OBJECT-TYPE
SYNTAX INTEGER {
perPlatform(1),
perInterface(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value of this object is perPlatform(1), then
this means that the label space type is
per platform.
mplsLdpEntityGenericLabelSpace OBJECT-TYPE
SYNTAX INTEGER {
perPlatform(1),
perInterface(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value of this object is perPlatform(1), then
this means that the label space type is
per platform.
If this object is perInterface(2), then this
means that the label space type is per Interface."
REFERENCE
"RFC3036, LDP Specification, Section 2.2.1,
Label Spaces."
DEFVAL { perPlatform }
::= { mplsLdpEntityGenericLREntry 3 }
If this object is perInterface(2), then this
means that the label space type is per Interface."
REFERENCE
"RFC3036, LDP Specification, Section 2.2.1,
Label Spaces."
DEFVAL { perPlatform }
::= { mplsLdpEntityGenericLREntry 3 }
mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "This value represents either the InterfaceIndex of the 'ifLayer' where these Generic Label would be created,
MPLSLDEntityGenericFindExorZero对象类型语法InterfaceIndexOrZero MAX-ACCESS读取创建状态当前描述“此值表示将在其中创建这些通用标签的“iLayer”的InterfaceIndex，
or 0 (zero). The value of zero means that the InterfaceIndex is not known.
或0（零）。值为零表示接口索引未知。
However, if the InterfaceIndex is known, then it must be represented by this value.
但是，如果InterfaceIndex已知，则必须用该值表示。
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex."
::= { mplsLdpEntityGenericLREntry 4 }
If an InterfaceIndex becomes known, then the
network management entity (e.g., SNMP agent) responsible
for this object MUST change the value from 0 (zero) to the
value of the InterfaceIndex."
::= { mplsLdpEntityGenericLREntry 4 }
mplsLdpEntityGenericLRStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityGenericLREntry 5 }
mplsLdpEntityGenericLRStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { mplsLdpEntityGenericLREntry 5 }
mplsLdpEntityGenericLRRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated.
MPLSLDEntityGenericlRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前说明“此概念行的状态。但是，如标题为“会话建立后更改值”一节中详细描述的，以及MPLSLDEntityAdminStatus对象的DESCRIPTION子句中再次描述的，如果已与对等方启动会话，则可以随时修改此行中的所有可写对象，更改此表中的对象将严重破坏会话并中断通信。再次重复：建议的过程是将MPLSLDEntityAdminStatus设置为down，从而显式地导致会话中断。然后，更改此条目中的对象，然后将MPLSLDEntityAdminStatus设置为enable，以启动新会话。
There must exist at least one entry in this table for every LDP Entity that has a generic label configured."
对于配置了通用标签的每个LDP实体，此表中必须至少存在一个条目。”
::= { mplsLdpEntityGenericLREntry 6 }
::= { mplsLdpEntityGenericLREntry 6 }
--****************************************************************
-- Module Conformance Statement
--****************************************************************
--****************************************************************
-- Module Conformance Statement
--****************************************************************
mplsLdpGenericGroups
OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 }
mplsLdpGenericGroups
OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 }
mplsLdpGenericCompliances
OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 }
mplsLdpGenericCompliances
OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 }
-- -- Full Compliance --
----完全遵守--
mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpGenericGroup
}
mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support for
read-create and read-write. In other words,
both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
mplsLdpGenericGroup
}
OBJECT mplsLdpEntityGenericLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT mplsLdpEntityGenericLRRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
::= { mplsLdpGenericCompliances 1 }
::= { mplsLdpGenericCompliances 1 }
-- -- Read-Only Compliance --
----只读遵从性--
mplsLdpGenericModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE." MODULE -- this module MANDATORY-GROUPS {
MPLSLDGenericModuleReadOnlyCompliance MODULE-COMPLIANCE状态当前描述“该模块是在支持只读的情况下实现的。换句话说，只有通过实现此MODULE-COMPLIANCE才能进行监视。”模块--此模块是必需的{
mplsLdpGenericGroup }
mplsLdpGenericGroup}
OBJECT mplsLdpEntityGenericLabelSpace MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityGenericLabelSpace最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityGenericIfIndexOrZero MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityGenericFindExorZero最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityGenericLRStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSLDEntityGenericlrStorageType最小访问只读说明“不需要写访问。”
OBJECT mplsLdpEntityGenericLRRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
对象MPLSLDEntityGenericlRowStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，active是唯一需要支持的状态。”
::= { mplsLdpGenericCompliances 2 }
::= { mplsLdpGenericCompliances 2 }
-- -- units of conformance --
----一致性单位--
mplsLdpGenericGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityGenericLabelSpace,
mplsLdpEntityGenericIfIndexOrZero,
mplsLdpEntityGenericLRStorageType,
mplsLdpEntityGenericLRRowStatus
}
STATUS current
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using Generic Labels as the Layer 2."
::= { mplsLdpGenericGroups 1 }
mplsLdpGenericGroup OBJECT-GROUP
OBJECTS {
mplsLdpEntityGenericLabelSpace,
mplsLdpEntityGenericIfIndexOrZero,
mplsLdpEntityGenericLRStorageType,
mplsLdpEntityGenericLRRowStatus
}
STATUS current
DESCRIPTION
"Objects that apply to all MPLS LDP implementations
using Generic Labels as the Layer 2."
::= { mplsLdpGenericGroups 1 }
END
终止
This document is a product of the MPLS Working Group. The authors would like to thank Mike MacFadden and Adrian Farrel for their helpful comments on several reviews. Also, the authors would like to give a special acknowledgement to Bert Wijnen for his many detailed reviews. Bert's assistance and guidance is greatly appreciated.
本文件是MPLS工作组的产品。作者要感谢迈克·麦克法登和阿德里安·法雷尔对几篇评论的有益评论。此外，作者还想特别感谢Bert Wijnen的许多详细评论。非常感谢伯特的帮助和指导。
We would also like to thank Cheenu Srinivasan, Arun Viswanathan and Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [RFC3813], for their assistance.
我们还要感谢MPLS-LSR-STD-MIB[RFC3813]的作者Cheenu Srinivasan、Arun Viswanathan和Thomas D.Nadeau提供的帮助。
Additionally, there have been other members of the working group that have been very helpful: Alan Kullberg from NetPlane Systems gave input on earlier versions of this document, and more recently, Riza Cetin of Alcatel and Neil Jerram of Data Connection who both provided MIB objects.
此外，工作组的其他成员也很有帮助：NetPlane Systems的Alan Kullberg提供了本文档早期版本的信息，最近，Alcatel的Riza Cetin和Data Connection的Neil Jerram提供了MIB对象。
Early versions of this document were also reviewed by colleagues at Nortel Networks and Ericsson. The authors would like to thank the following people: Leigh McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo Augustsson from Ericsson.
Nortel Networks和爱立信的同事也对本文件的早期版本进行了审查。作者要感谢以下人士：北电网络的Leigh McLellan、Geetha Brown、陈格平和周夏兰，以及爱立信的Zoltan Takacs和Bo Augustsson。
[RFC2115] Brown, C. and F. Baker, "Management Information Base for Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[RFC2115]Brown，C.和F.Baker，“使用SMIv2的帧中继DTE的管理信息库”，RFC 2115，1997年9月。
[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月。
[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月。
[RFC2514] Noto, M., Spiegel, E., and K. Tesink, editors, "Definition of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999.
[RFC2514]Noto，M.，Spiegel，E.，和K.Tesink，编辑，“ATM管理的文本约定和对象标识的定义”，RFC 2514，1999年2月。
[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月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001.
[RFC3031]Rosen，E.，Viswananthan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月。
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001.
[RFC3032]Rosen，E.，Tappan，D.，Fedorkow，G.，Rekhter，Y.，Farinaci，D.，Li，T.，和A.Conta，“MPLS标签堆栈编码”，RFC 3032，2001年1月。
[RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching on Frame Relay Networks Specification", RFC 3034, January 2001.
[RFC3034]Conta，A.，Doolan，P.，和A.Malis，“帧中继网络上标签切换的使用规范”，RFC 3034，2001年1月。
[RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, G., Rekhter, Y., and P. Doolan, "MPLS using LDP and ATM VC Switching", RFC 3035, January 2001.
[RFC3035]Davie，B.，Lawrence，J.，McCloghrie，K.，Rosen，E.，Swallow，G.，Rekhter，Y.，和P.Doolan，“使用LDP和ATM VC交换的MPLS”，RFC 3035，2001年1月。
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. Thomas, "LDP Specification", RFC 3036, January 2001.
[RFC3036]Andersson，L.，Doolan，P.，Feldman，N.，Fredette，A.，和B.Thomas，“LDP规范”，RFC 3036，2001年1月。
[RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, January 2001.
[RFC3037]Thomas，B.和E.Gray，“LDP适用性”，RFC 3037，2001年1月。
[RFC3215] Boscher, C., Cheval, P., Wu, L., and E. Gray, "LDP State Machine", RFC 3215, January 2002.
[RFC3215]Boscher，C.，Cheval，P.，Wu，L.，和E.Gray，“LDP状态机”，RFC 32152002年1月。
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002.
[RFC3289]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月。
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Coventions for Internet Network Addresses", RFC 3291, May 2002.
[RFC3291]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 3291，2002年5月。
[RFC3413] Levi, D., Meyers, P. and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.
[RFC3413]Levi，D.，Meyers，P.和B.Stewart，“简单网络管理协议（SNMP）应用”，STD 62，RFC 3413，2002年12月。
[RFC3811] Nadeau, T. and J. Cucchiara, Editors "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月。
[RFC3813] Srinivansan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004
[RFC3813]Srinivansan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 38132004年6月
[MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol Label Switching (MPLS) Management Overview", Work in Progress, September 2003.
[MPLSMGMT]Nadeau，T.，Srinivasan，C.，和A.Farrel，“多协议标签交换（MPLS）管理概述”，正在进行的工作，2003年9月。
[RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
[RFC2684]Grossman，D.和J.Heinanen，“ATM适配层5上的多协议封装”，RFC 2684，1999年9月。
[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月。
This Security Considerations section consists of 4 subsections, one for each of the MIB Modules in this document.
本安全注意事项部分由4个子部分组成，本文档中的每个MIB模块各有一个子部分。
There are a number of management objects defined in this MIB module 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 mplsLdpEntityTable contains objects to provision potential LDP sessions on the Label Switching Router (LSR) or Label Edge Router (LER). The mplsLdpLspFecTable contains objects which associate an LSP with a FEC. Unauthorized access to objects in these tables, could result in disruption of traffic on the network. This is especially true if an LDP session has been established. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent which implements this MIB. Administrators should consider whether
o MPLSLDEntityTable包含用于在标签交换路由器（LSR）或标签边缘路由器（LER）上提供潜在LDP会话的对象。MPLSDPLSPFectable包含将LSP与FEC关联的对象。未经授权访问这些表中的对象可能会导致网络流量中断。如果建立了自民党会议，情况尤其如此。在可能的情况下，应考虑使用更强的机制，如SNMPv3安全性。具体来说，SNMPv3 VACM和USM必须与实现此MIB的任何v3代理一起使用。管理员应考虑是否
read access to these objects should be allowed, since read access may be undesirable under certain circumstances.
应该允许对这些对象进行读访问，因为在某些情况下可能不需要读访问。
Some of the readable objects in this MIB module i.e., (objects with a MAX-ACCESS other than not-accessible), may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中的一些可读对象，即（具有MAX-ACCESS而非not ACCESS的对象），在某些网络环境中可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSessionTable and mplsLdpSessionStatsTable collectively show the LDP LSP network topology. If an Administrator does not want to reveal the LDP LSP topology of the network, then these tables should be considered sensitive/vulnerable.
o MPLSDPEntityTable、MPLSDPPeertable、MPLSDPSessionTable和MPLSDPSessionStatStable共同显示LDP LSP网络拓扑。如果管理员不想透露网络的LDP LSP拓扑，则应将这些表视为敏感/易受攻击。
There are a number of management objects defined in this MIB module 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 mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain objects to provision potential LDP sessions on the Label Switching Router (LSR) or Label Edge Router (LER) over Layer 2 of ATM. These tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. Unauthorized access to objects in these tables, could result in disruption of traffic on the network. This is especially true if an LDP session has been established. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent which implements this MIB. Administrators should consider whether read access to these objects should be allowed, since read access may be undesirable under certain circumstances.
o MPLSLDEntityATMTable和MPLSLDEntityATMLRTable包含用于在ATM第2层上的标签交换路由器（LSR）或标签边缘路由器（LER）上提供潜在LDP会话的对象。这些表扩展了MPLS-LDP-MIB中的mplsLdpEntityTable。未经授权访问这些表中的对象可能会导致网络流量中断。如果建立了自民党会议，情况尤其如此。在可能的情况下，应考虑使用更强的机制，如SNMPv3安全性。具体来说，SNMPv3 VACM和USM必须与实现此MIB的任何v3代理一起使用。管理员应该考虑是否应该允许对这些对象的读访问，因为在某些情况下读访问可能是不可取的。
Some of the readable objects in this MIB module i.e., (objects with a MAX-ACCESS other than not-accessible), may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中的一些可读对象，即（具有MAX-ACCESS而非not ACCESS的对象），在某些网络环境中可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the Label Ranges for ATM. If an Administrator does not want to reveal this information then these tables should be considered sensitive/vulnerable and treated accordingly.
o MPLSLDEntityATMTable和MPLSLDEntityATMLRTable显示ATM的标签范围。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击，并进行相应处理。
There are a number of management objects defined in this MIB module 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 mplsLdpEntityFrameRelayTable and mplsLdpEntityFrameRelayLRTable contain objects to provision potential LDP sessions on the Label Switching Router (LSR) or Label Edge Router (LER) over Layer 2 of Frame Relay. These tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. Unauthorized access to objects in these tables, could result in disruption of traffic on the network. This is especially true if an LDP session has been established. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent which implements this MIB. Administrators should consider whether read access to these objects should be allowed, since read access may be undesirable under certain circumstances.
o MPLSLDEntityFrameRelayTable和MPLSLDEntityFrameRelayTable包含用于在帧中继的第2层上的标签交换路由器（LSR）或标签边缘路由器（LER）上提供潜在LDP会话的对象。这些表扩展了MPLS-LDP-MIB中的mplsLdpEntityTable。未经授权访问这些表中的对象可能会导致网络流量中断。如果建立了自民党会议，情况尤其如此。在可能的情况下，应考虑使用更强的机制，如SNMPv3安全性。具体来说，SNMPv3 VACM和USM必须与实现此MIB的任何v3代理一起使用。管理员应该考虑是否应该允许对这些对象的读访问，因为在某些情况下读访问可能是不可取的。
Some of the readable objects in this MIB module i.e., (objects with a MAX-ACCESS other than not-accessible), may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中的一些可读对象，即（具有MAX-ACCESS而非not ACCESS的对象），在某些网络环境中可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the mplsLdpEntityFrameRelayTable and mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame Relay. If an Administrator does not want to reveal this information then these tables should be considered sensitive/vulnerable and treated accordingly.
o MPLSLDEntityFrameRelayTable和MPLSLDEntityFrameRelayTable显示帧中继的标签范围。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击，并进行相应处理。
There are a number of management objects defined in this MIB module 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 mplsLdpEntityGenericLRTable contains objects to provision potential LDP sessions on the Label Switching Router (LSR) or Label Edge Router (LER) over Layer 2 of Ethernet. This table extends the mplsLdpEntityTable in the MPLS-LDP-MIB. Unauthorized access to objects in these tables, could result in disruption of traffic on the network. This is especially true if an LDP session has been established. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent which implements this MIB. Administrators should consider whether read access to these objects should be allowed, since read access may be undesirable under certain circumstances.
o MPLSLDEntityGenericlTable包含用于在以太网第2层上的标签交换路由器（LSR）或标签边缘路由器（LER）上提供潜在LDP会话的对象。此表扩展了MPLS-LDP-MIB中的MPLSLDPTEntityTable。未经授权访问这些表中的对象可能会导致网络流量中断。如果建立了自民党会议，情况尤其如此。在可能的情况下，应考虑使用更强的机制，如SNMPv3安全性。具体来说，SNMPv3 VACM和USM必须与实现此MIB的任何v3代理一起使用。管理员应该考虑是否应该允许对这些对象的读访问，因为在某些情况下读访问可能是不可取的。
Some of the readable objects in this MIB module i.e., (objects with a MAX-ACCESS other than not-accessible), may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中的一些可读对象，即（具有MAX-ACCESS而非not ACCESS的对象），在某些网络环境中可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the mplsLdpEntityGenericLRTable shows the Label Ranges for ethernet. If an Administrator does not want to reveal this information then these tables should be considered sensitive/vulnerable and treated accordingly.
o MPLSLDEntityGenericlR表显示以太网的标签范围。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击，并进行相应处理。
The following paragraphs describe additional security considerations which are applicable to all 4 of the MIB Modules in this document.
以下段落描述了适用于本文档中所有4个MIB模块的其他安全注意事项。
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 this MIB module.
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实体正确配置为仅授予那些拥有合法权限来获取或设置（更改/创建/删除）对象的主体（用户）访问对象的权限。
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB [MPLSTCMIB], MPLS related standards track MIB modules should be rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained in this document, each of the following "IANA Considerations" subsections lists new IANA assignments under the mplsStdMIB subtree. New assignments can only be made via a Standards Action as specified in [RFC2434].
如[MPLSMGMT]中所述，并根据MPLS-TC-STD-MIB[MPLSTCMIB]中的要求，与MPLS相关的标准跟踪MIB模块应根在MPLSTDMIB子树下。本文档包含4个MPLS MIB模块，以下每个“IANA注意事项”小节在MPLSTDMIB子树下列出了新的IANA分配。新分配只能通过[RFC2434]中规定的标准行动进行。
The IANA has assigned { mplsStdMIB 4 } to the MPLS-LDP-STD-MIB module specified in this document.
IANA已将{mplsStdMIB 4}分配给本文件中指定的MPLS-LDP-STD-MIB模块。
The IANA has assigned { mplsStdMIB 5 } to the MPLS-LDP-ATM-STD-MIB module specified in this document.
IANA已将{mplsStdMIB 5}分配给本文件中指定的MPLS-LDP-ATM-STD-MIB模块。
The IANA has assigned { mplsStdMIB 6 } to the MPLS-LDP-FRAME-RELAY-STD-MIB module specified in this document.
IANA已将{mplsStdMIB 6}分配给本文件中指定的MPLS-LDP-FRAME-RELAY-STD-MIB模块。
The IANA has assigned { mplsStdMIB 7 } to the MPLS-LDP-GENERIC-STD-MIB module specified in this document.
IANA已将{mplsStdMIB 7}分配给本文档中指定的MPLS-LDP-GENERIC-STD-MIB模块。
James V. Luciani Marconi Communications, Inc. 900 Chelmsford Street Lowell, MA 01851
詹姆斯诉卢西亚尼·马可尼通信公司，马萨诸塞州洛厄尔切姆斯福德街900号，邮编01851
EMail: james_luciani@mindspring.com
EMail: james_luciani@mindspring.com
Hans Sjostrand ipUnplugged P.O. Box 101 60 S-121 28 Stockholm, Sweden
Hans Sjostrand Ipo，瑞典斯德哥尔摩，邮政信箱101 60 S-121 28
Phone: +46 8 725 5900
EMail: hans@ipunplugged.com
Phone: +46 8 725 5900
EMail: hans@ipunplugged.com
Joan E. Cucchiara Marconi Communications, Inc. 900 Chelmsford Street Lowell, MA 01851
Joan E.Cucchiara Marconi通信有限公司，马萨诸塞州洛厄尔切姆斯福德街900号，邮编01851
Phone: +1 978 275 7400
EMail: jcucchiara@mindspring.com
Phone: +1 978 275 7400
EMail: jcucchiara@mindspring.com
Copyright (C) The Internet Society (2004). 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.
版权所有（C）互联网协会（2004年）。本文件受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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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编辑功能的资金目前由互联网协会提供。