RFC 4631 - Link Management Protocol (LMP) Management Information Base (MIB) 日本語訳

URL : https://tools.ietf.org/html/rfc4631
タイトル : RFC 4631 - リンク管理プロトコル（LMP）管理情報ベース（MIB）
翻訳編集 : 自動生成

Network Working Group                                           M. Dubuc
Request for Comments: 4631                                     T. Nadeau
Obsoletes: 4327                                            Cisco Systems
Category: Standards Track                                        J. Lang
                                                             Sonos, Inc.
                                                             E. McGinnis
                                                      Hammerhead Systems
                                                               A. Farrel
                                                      Old Dog Consulting
                                                          September 2006

    Link Management Protocol (LMP) Management Information Base (MIB)

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）の最新版を参照してください。このメモの配布は無制限です。

著作権表示

著作権（C）インターネット協会（2006）。

Abstract

抽象

This document provides minor corrections to and obsoletes RFC 4327.

この文書では、マイナーな修正を提供し、RFC 4327を廃止します。

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP).

このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、それはリンク管理プロトコル（LMP）をモデル化するための管理オブジェクトについて説明します。

Table of Contents

   1. The Internet-Standard Management Framework ......................3
   2. Introduction ....................................................3
   3. Terminology .....................................................3
   4. Feature Checklist ...............................................4
   5. Outline .........................................................4
   6. Brief Description of MIB Objects ................................5
      6.1. lmpNbrTable ................................................5
      6.2. lmpControlChannelTable .....................................5
      6.3. lmpControlChannelPerfTable .................................5
      6.4. lmpTeLinkTable .............................................5
      6.5. lmpLinkVerificationTable ...................................5
      6.6. lmpTeLinkPerfTable .........................................6
      6.7. lmpDataLinkTable ...........................................6
      6.8. lmpDataLinkPerfTable .......................................6
   7. Example of LMP Control Channel Setup ............................6
   8. Application of the Interfaces Group to LMP ......................9
      8.1. Support of the LMP Layer by ifTable .......................10
   9. LMP MIB Module Definitions .....................................11
   10. Security Considerations .......................................78
   11. Contributors ..................................................79
   12. Acknowledgements ..............................................79
   13. IANA Considerations ...........................................79
      13.1. IANA Considerations for LMP ifType .......................79
      13.2. IANA Considerations for LMP-MIB ..........................79
   14. Changes from RFC 4327 to RFC 4631 .............................79
   15. References ....................................................80
      15.1. Normative References .....................................80
      15.2. Informative References ...................................81

1. The Internet-Standard Management Framework

1.インターネット標準管理フレームワーク

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）の構造で定義されたメカニズムを使用して定義されています。このメモは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]とSTD 58、RFC 2580 [RFC2580]に記載されているSMIv2のに準拠しているMIBモジュールを指定します。

2. Introduction

2.はじめに

Current work is under way in the IETF to specify a suite of protocols to be used as a common control plane and a separate common measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link Management Protocol [RFC4204] are key components of this standardization activity. The primary purpose of LMP is to manage traffic engineering (TE) links. Primary goals of LMP are the maintenance of the control channel connectivity, correlation of link properties, verification of data-bearing links, and detection and isolation of link faults.

現在の研究は、共通の制御プレーンと別の一般的な測定面として使用されるプロトコルのスイートを指定するIETFで進行中です。一般化MPLS（GMPLS）[RFC3471]とリンク管理プロトコル[RFC4204]は、この標準化活動の重要なコンポーネントです。 LMPの主な目的は、トラフィックエンジニアリング（TE）リンクを管理することです。 LMPの主な目標は、制御チャネルの接続性の維持、リンク特性の相関、データ担持リンクの検証、およびリンク障害の検出および単離であります。

We describe in this document a MIB module that can be used to manage LMP implementations. This MIB module covers both configuration and performance-monitoring aspects of LMP.

私たちは、この文書でLMPの実装を管理するために使用することができMIBモジュールを記述します。このMIBモジュールは、LMPの設定およびパフォーマンス監視の両方の側面をカバーしています。

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].

この文書のキーワード "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", および "OPTIONAL" はRFC 2119 [RFC2119]に記載されているように解釈されます。

3. Terminology

3.用語

This document uses terminology from the document describing the Link Management Protocol [RFC4204]. An "LMP adjacency" is formed between two nodes that support the same capabilities, and LMP messages are exchanged between the node pair over control channels that form this adjacency. Several control channels can be active at the same time. With the exception of messages related to control channel management, anytime an LMP message needs to be transferred to a neighbor node, it can be sent on any of the active control channels. The control channels can also be used to exchange MPLS control plane information or routing information.

この文書では、リンク管理プロトコル[RFC4204]を記述した文書から専門用語を使用しています。「LMP隣接」は、同じ機能をサポートする2つのノードの間に形成され、そしてLMPメッセージは、この隣接関係を形成する制御チャネルを介してノード対の間で交換されます。いくつかの制御チャネルを同時にアクティブにすることができます。チャネル管理を制御するために、関連するメッセージを除き、いつでもLMPメッセージが隣接ノードに転送する必要があり、それがアクティブ制御チャネルのいずれかに送信することができます。制御チャネルはまた、MPLSコントロールプレーン情報やルーティング情報を交換するために使用することができます。

LMP is designed to support aggregation of one or more data-bearing links into a traffic-engineering (TE) link. The data-bearing links can be either component links or ports, depending on their multiplexing capability (see [RFC4204] for the distinction between port and component link).

LMPは、トラフィックエンジニアリング（TE）リンクに一つ以上のデータ・ベアリング・リンクの集約をサポートするように設計されています。データ担持リンクが（ポートとコンポーネントリンクとの間の区別のために[RFC4204]を参照）、それらの多重化能力に応じて、コンポーネントリンクまたはポートのいずれかとすることができます。

Each TE link is associated with an LMP adjacency, and one or more control channels are used to exchange LMP messages for a particular adjacency. In turn, control channels are used to manage the TE links associated with the LMP adjacency.

各TEリンクは、LMP隣接関連付けられている、および1つまたは複数の制御チャネルは、特定の隣接にLMPメッセージを交換するために使用されます。ターンでは、制御チャネルは、LMP隣接に関連付けられたTEリンクを管理するために使用されています。

4. Feature Checklist

4.機能のチェックリスト

The Link Management Protocol MIB module (LMP-MIB) is designed to satisfy the following requirements and constraints:

リンク管理プロトコルMIBモジュール（LMP-MIB）は、次の要件と制約を満たすように設計されています。

- The MIB module supports the enabling and disabling of LMP capability on LMP-capable interfaces of a photonic switch, optical cross-connect, or router.

- MIBモジュールは、フォトニックスイッチのLMP-可能なインターフェイス、光クロスコネクト、またはルータ上のLMP機能の有効化および無効化をサポートします。

- The MIB module is used to provide information about LMP adjacencies.

- MIBモジュールは、LMP隣接関係に関する情報を提供するために使用されます。

- Support is provided for configuration of the keep-alive and link verification parameters.

- サポートは、キープアライブとリンク検証パラメータの設定のために提供されます。

- The MIB module is used to express the mapping between local and remote TE links, as well as local and remote interface identifiers for port or component link.

- MIBモジュールは、ローカルおよびリモートTEリンク、ならびにポートまたはコンポーネントリンクのローカルおよびリモートのインタフェース識別子との間のマッピングを表現するために使用されます。

- Performance counters are provided for measuring LMP performance on a per-control channel basis. Performance counters are also provided for measuring LMP performance on the data-bearing links.

- パフォーマンスカウンタがあたり、制御チャネルごとにLMP性能を測定するために設けられています。パフォーマンスカウンタは、データ・ベアリング・リンク上でLMP性能を測定するために設けられています。

Note that the LMP MIB module goes hand-in-hand with the TE Link (TE-LINK-STD-MIB) MIB module [RFC4220]. The TE link table, which is used to associate data-bearing links to TE links, is defined in the TE Link MIB. The TE link table in the LMP MIB module contains TE link information specific to LMP.

LMP MIBモジュールは、TEリンク（TE-LINK-STD-MIB）MIBモジュール[RFC4220]と手に手を行くことに留意されたいです。 TEリンクへのデータ・ベアリング・リンクを関連付けるために使用されるTEリンクテーブルは、TEリンクMIBで定義されています。 LMP MIBモジュールのTEリンクテーブルはLMPに固有のTEリンク情報が含まれています。

5. Outline

5.概要

Configuring LMP through an optical device involves the following steps:

光学デバイスを介してLMPの設定は、次の手順を実行します。

- Enabling LMP on LMP-capable interfaces through control channel configuration.

- 制御チャネル構成を介してLMP-可能なインターフェイスでLMPを有効にします。

- Optionally, specifying link verification parameters.

- 必要に応じて、リンク検証パラメータを指定します。

- Configuring the data-bearing links and associating them to the appropriate TE link (this association is stored in the ifStackTable of the Interfaces Group MIB).

- データ・ベアリング・リンクを設定すると（この関連付けは、インタフェースグループMIBののifStackTableに格納されている）適切なTEリンクにそれらを関連付けます。

TE links are managed by the control channels that run between the same pair of nodes (LMP adjacency).

TEリンクは、ノードの同じペア（LMP隣接）との間に実行の制御チャネルによって管理されています。

6. Brief Description of MIB Objects

MIBオブジェクトの6簡単な説明

Sections 6.1 - 6.8 describe objects pertaining to LMP. The MIB objects were derived from the LMP document [RFC4204].

セクション6.1から6.8は、LMPに関連するオブジェクトについて説明します。 MIBオブジェクトは、LMP文献[RFC4204]に由来しました。

6.1. lmpNbrTable

The remote node table is used to identify the pair of nodes that exchange LMP messages over control channels.

リモートノードテーブルは、制御チャネルを介してLMPメッセージを交換ノードの対を識別するために使用されます。

6.2. lmpControlChannelTable

The control channel table is used for enabling the LMP protocol on LMP-capable interfaces. A photonic switch, optical cross-connect, or router creates an entry in this table for every LMP-capable interface in that device.

制御チャネルテーブルは、LMP-可能なインターフェイス上のLMPプロトコルを可能にするために使用されます。光スイッチ、光クロスコネクト、又はルータは、そのデバイス内のすべてのLMP-可能なインターフェイスのためのこの表のエントリを作成します。

6.3. lmpControlChannelPerfTable

The control channel performance table is used for collecting LMP performance counts on a per-control channel basis. Each entry in the lmpControlChannelTable has a corresponding entry in the lmpControlChannelPerfTable.

制御チャネル性能テーブルごとの制御チャネル毎にLMP性能カウントを収集するために使用されています。 lmpControlChannelTableの各エントリはlmpControlChannelPerfTable内の対応するエントリがあります。

6.4. lmpTeLinkTable

The TE link table is used for specifying LMP information associated with TE links.

TEリンクテーブルはTEリンクに関連したLMP情報を指定するために使用されます。

6.5. lmpLinkVerificationTable

The link verification table is used for configuring the LMP link verification parameters of TE links. For every TE link entry in the lmpTeLinkTable that supports the link verification procedure, there is a corresponding entry in the lmpLinkVerificationTable.

リンクの検証テーブルはTEリンクのLMPリンク検証パラメータを設定するために使用されます。リンク検証手続をサポートしていlmpTeLinkTable内のすべてのTEリンクエントリーの場合は、lmpLinkVerificationTable内の対応するエントリがあります。

6.6. lmpTeLinkPerfTable

The TE link performance table is used for collecting LMP performance counts on a per-TE link basis. Each entry in the lmpTeLinkTable has a corresponding entry in the lmpTeLinkPerfTable.

TEリンク性能テーブルごとのTEリンク基づきLMP性能カウントを収集するために使用されています。 lmpTeLinkTableの各エントリはlmpTeLinkPerfTable内の対応するエントリがあります。

6.7. lmpDataLinkTable

The data-bearing link table is used to specify the data-bearing links that are associated with TE links.

データ担持リンクテーブルはTEリンクに関連付けられているデータ・ベアリング・リンクを指定するために使用されます。

6.8. lmpDataLinkPerfTable

The data-bearing link performance table is used for collecting LMP performance counts on data-bearing links.

データ・ベアリングリンク性能テーブルは、データ・ベアリング・リンク上でLMP性能カウントを収集するために使用されています。

7. Example of LMP Control Channel Setup

LMP制御チャネルのセットアップの7例

In this section, we provide a brief example of using the MIB objects described in Section 9 to set up an LMP control channel. This example is not meant to illustrate every nuance of the MIB module, but it is intended as an aid to understanding some of the key concepts. It is meant to be read after one goes through the MIB itself.

このセクションでは、我々は、LMP制御チャネルを設定する第9項に記載のMIBオブジェクトを使用しての簡単な例を提供します。この例では、MIBモジュールのあらゆるニュアンスを説明するためのものではありませんが、それは重要な概念のいくつかを理解するための助けとして意図されます。 1 MIB自体を通過した後に読まれることを意図しています。

Suppose that one would like to form an LMP adjacency between two nodes using two control channels. Suppose also that there are three data-bearing links. We also assume that the data-bearing links are ports (lambdas) and that the link verification procedure is not enabled. The following example illustrates which rows and corresponding objects might be created to accomplish this.

一つは二つの制御チャネルを使用して、2つのノード間のLMP隣接関係を形成したいと仮定する。また、3つのデータ・ベアリング・リンクがあると仮定します。また、データ・ベアリング・リンクがポート（ラムダ）とリンク検証手続が有効になっていないことであることを前提としています。次の例では、これを実現するために作成されるかもしれない行と対応するオブジェクトを示します。

First, LMP must be enabled between the pair of nodes.

まず、LMPは、一対のノード間で有効にする必要があります。

In lmpNbrTable: { lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1 lmpNbrAdminStatus = up(1), lmpNbrRowStatus = createAndGo(4), lmpNbrStorageType = nonVolatile(3) }

lmpNbrTableで：{lmpNbrNodeId =「c0000201'H、 - 192.0.2.1 lmpNbrAdminStatus =最大（1）、lmpNbrRowStatus = createAndGo（4）、lmpNbrStorageType =不揮発性（3）}

Then, the control channels must be set up. These are created in the lmpControlChannelTable.

その後、制御チャネルを設定する必要があります。これらはlmpControlChannelTableに作成されます。

In lmpControlChannelTable: { lmpCcId = 1, lmpCcUnderlyingIfIndex = 1, lmpCcIsIf = false(2), lmpCcAuthentication = false(2), lmpCcHelloInterval = 15, lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMax = 1000, lmpCcHelloDeadInterval = 45, lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMax = 1000, lmpCcAdminStatus = up(1), lmpCcRowStatus = createAndGo(4), lmpCcStorageType = nonVolatile(3) }

lmpControlChannelTableで：{lmpCcId = 1、lmpCcUnderlyingIfIndex = 1、lmpCcIsIf =偽（2）、lmpCcAuthentication =偽（2）、lmpCcHelloInterval = 15、lmpCcHelloIntervalMin = 15、lmpCcHelloIntervalMax = 1000、lmpCcHelloDeadInterval = 45、lmpCcHelloDeadIntervalMin = 45、lmpCcHelloDeadIntervalMax = 1000、 lmpCcAdminStatus =最大（1）、lmpCcRowStatus = createAndGo（4）、lmpCcStorageType =不揮発性（3）}

{ lmpCcId = 2, lmpCcUnderlyingIfIndex = 2, lmpCcIsIf = false(2), lmpCcAuthentication = false(2), lmpCcHelloInterval = 15, lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMax = 1000, lmpCcHelloDeadInterval = 45, lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMax = 1000, lmpCcAdminStatus = up(1), lmpCcRowStatus = createAndGo(4), lmpCcStorageType = nonVolatile(3) }

{lmpCcId = 2、lmpCcUnderlyingIfIndex = 2、lmpCcIsIf =偽（2）、lmpCcAuthentication =偽（2）、lmpCcHelloInterval = 15、lmpCcHelloIntervalMin = 15、lmpCcHelloIntervalMax = 1000、lmpCcHelloDeadInterval = 45、lmpCcHelloDeadIntervalMin = 45、lmpCcHelloDeadIntervalMax = 1000、lmpCcAdminStatus =最大（1）、lmpCcRowStatus = createAndGo（4）、lmpCcStorageType =不揮発性（3）}

Next, the three data-bearing links are created. For each data-bearing link, an ifEntry with the same ifIndex needs to be created beforehand.

次に、3つのデータ・ベアリング・リンクが作成されます。各データ担持リンクについて、同じifIndexのとのifEntryを予め作成する必要があります。

In lmpDataLinkTable: { ifIndex = 41, lmpDataLinkAddressType = unknown(0), lmpDataLinkIpAddr = ''H, lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIfId = 47, lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkStorageType = nonVolatile(3) }

lmpDataLinkTableで：{ifIndexの= 41、lmpDataLinkAddressType =不明（0）、lmpDataLinkIpAddr = '' H、lmpDataLinkRemoteIpAddress = '' H、lmpDataLinkRemoteIfId = 47、lmpDataLinkRowStatus = createAndGo（4）、lmpDataLinkStorageType =不揮発性（3）}

{ ifIndex = 43, lmpDataLinkAddressType = unknown(0), lmpDataLinkIpAddr = ''H, lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIfId = 42, lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkStorageType = nonVolatile(3) } { ifIndex = 44, lmpDataLinkAddressType = unknown(0), lmpDataLinkIpAddr = ''H, lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIfId = 48, lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkStorageType = nonVolatile(3) }

{ifIndexの= 43、lmpDataLinkAddressType =不明（0）、lmpDataLinkIpAddr = '' H、lmpDataLinkRemoteIpAddress = '' H、lmpDataLinkRemoteIfId = 42、lmpDataLinkRowStatus = createAndGo（4）、lmpDataLinkStorageType =不揮発性（3）} {のifIndex = 44、lmpDataLinkAddressType =不明（0）、lmpDataLinkIpAddr = '' H、lmpDataLinkRemoteIpAddress = '' H、lmpDataLinkRemoteIfId = 48、lmpDataLinkRowStatus = createAndGo（4）、lmpDataLinkStorageType =不揮発性（3）}

Note that the data-bearing link type (lmpDataLinkType) does not need to be provisioned, as it is automatically populated by the node. The definition of the protection role (primary or secondary) for the data-bearing links is stored in the componentLinkTable of the TE Link MIB module [RFC4220].

それは自動的にノードによって移入されるデータ担持リンクタイプ（lmpDataLinkType）は、プロビジョニングする必要がないことに留意されたいです。データ担持リンクの保護の役割（プライマリまたはセカンダリ）の定義は、TEリンクMIBモジュールのcomponentLinkTable [RFC4220]に格納されています。

Then, a TE link is created as an ifEntry with ifType teLink in the ifTable.

その後、TEリンクはifTableにifTypeがteLinkとのifEntryとして作成されます。

Once the TE link is created in the ifTable, a TE link entry is created in the LMP MIB module to specify TE link information specific to LMP.

TEリンクがifTableで作成されると、TEリンクエントリーはLMPに固有のTEリンク情報を指定するには、LMP MIBモジュールで作成されます。

In lmpTeLinkTable: { ifIndex = 20, lmpTeLinkVerification = true(1), lmpTeLinkFaultManagement = true(1), lmpTeLinkDwdm = false(2), lmpTeLinkRowStatus = createAndGo(4), lmpTeLinkStorageType = nonVolatile(3) }

lmpTeLinkTableで：{ifIndexの= 20、lmpTeLinkVerification =真（1）、lmpTeLinkFaultManagement =真（1）、lmpTeLinkDwdm =偽（2）、lmpTeLinkRowStatus = createAndGo（4）、lmpTeLinkStorageType =不揮発性（3）}

and in lmpLinkVerificationTable: { ifIndex = 20, lmpLinkVerifyInterval = 100, lmpLinkVerifyDeadInterval = 300, lmpLinkVerifyTransportMechanism = j0Trace(3), lmpLinkVerifyAllLinks = true(1), lmpLinkVerifyTransmissionRate = 100000, lmpLinkVerifyWavelength = 0, lmpLinkVerifyRowStatus = createAndGo(4), lmpLinkVerifyStorageType = nonVolatile(3) }

そしてlmpLinkVerificationTableで：{のifIndex = 20、lmpLinkVerifyInterval = 100、lmpLinkVerifyDeadInterval = 300、lmpLinkVerifyTransportMechanism = j0Trace（3）、lmpLinkVerifyAllLinks =真（1）、lmpLinkVerifyTransmissionRate = 100000、lmpLinkVerifyWavelength = 0、lmpLinkVerifyRowStatus = createAndGo（4）、lmpLinkVerifyStorageType =不揮発性（ 3）}

The association between the data-bearing links and the TE links is stored in the ifStackTable [RFC2863].

データ・ベアリング・リンクとTEリンクとの間の関連付けは、のifStackTable [RFC2863]に格納されています。

In parallel with the entry created in the lmpTeLinkTable, an entry may be created in the teLinkTable of the TE Link MIB module [RFC4220].

lmpTeLinkTableで作成されたエントリと並行して、エントリがTEリンクMIBモジュールのteLinkTable [RFC4220]で作成してもよいです。

8. Application of the Interfaces Group to LMP

LMPへのインタフェースグループの8応用

The Interfaces Group [RFC2863] defines generic managed objects for managing interfaces. This memo contains the media-specific extensions to the Interfaces Group for managing LMP control channels that are modeled as interfaces. If the control channel as defined in the lmpControlChannelTable is modeled as an ifEntry, then the following definition applies. An lmpControlChannelTable entry is designated as being represented as an Interfaces MIB ifEntry if the lmpControlChannelEntry object lmpCcIsIf is set to true (1). In this case, the control channel SHOULD be modeled as an ifEntry and provide appropriate interface stacking, as defined below.

インタフェースグループ[RFC2863]はインターフェイスを管理するための一般的な管理オブジェクトを定義します。このメモは、インターフェースとしてモデル化されているLMP制御チャネルを管理するためのインターフェイスグループへのメディア固有の拡張機能が含まれています。 lmpControlChannelTableで定義されている制御チャネルはますifEntryとしてモデル化される場合は、次の定義が適用されます。 lmpControlChannelEntryオブジェクトlmpCcIsIfがtrueに設定されている場合lmpControlChannelTableエントリは、インターフェイスMIBのifEntryとして表現されるものとして指定されている（1）。この場合、制御チャネルはますifEntryとしてモデル化されるべきであり、以下に定義されるように、適切なインターフェイススタックを提供します。

This memo assumes the interpretation of the Interfaces Group to be in accordance with [RFC2863], which states that the interfaces table (ifTable) contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered an interface. Since the LMP interface only carries control traffic, it is considered to be below the internetwork layer. Thus, the LMP interface may be represented as an entry in the ifTable. The interrelation of entries in the ifTable is defined by Interfaces Stack Group defined in [RFC2863].

このメモは、インターフェイステーブル（ifTableの）は、管理対象リソースのインターフェイスに関する情報が含まれていることと、ネットワークインターフェースのインターネットワーク層の下の各副層があると考えられると述べている[RFC2863]に従ってことがインタフェースグループの解釈を前提とインタフェース。 LMPインタフェースのみ制御トラフィックを運ぶので、インターネットワーク層の下にあると考えられます。したがって、LMPインタフェースはifTableのエントリとして表されてもよいです。 ifTableのエントリーの相互関係は[RFC2863]で定義されたインタフェーススタックグループによって定義されます。

When LMP control channels are modeled as interfaces, the interface stack table must appear as follows for the LMP control channel interfaces:

LMP制御チャネルをインターフェースとしてモデル化される場合LMP制御チャネルインターフェイスのため、以下のように、インタフェーススタックテーブルが表示されなければなりません。

      +----------------------------------------+
      | LMP-interface ifType = lmp(227)        +
      +----------------------------------------+
      | Underlying Layer...                    +
      +----------------------------------------+

In the above diagram, "Underlying Layer..." refers to the ifIndex of any interface type over which the LMP interface will transmit its traffic. Note that if the underlying layer provides multiple access to its media (i.e., Ethernet), then it is possible to stack multiple LMP interfaces on top of this interface in parallel.

上記の図では、「下地層...」LMPインタフェースは、そのトラフィックを送信しますその上に任意のインターフェイスタイプのifIndexのを指します。下地層は、そのメディア（すなわち、イーサネット）への複数のアクセスを提供する場合、並列に、このインターフェイス上に複数LMPインタフェースを積層することが可能であることに留意されたいです。

Note that it is not a requirement that LMP control channels be modeled as interfaces. It is acceptable that control channels simply exist as logical connections between adjacent LMP-capable nodes. In this case, lmpCcIsIf is set to false(2), and no corresponding entry is made in the ifTable.

それはLMP制御チャネルをインターフェースとしてモデル化することが必要条件ではないことに留意されたいです。なお、制御チャネルは、単に隣接LMP-可能なノード間の論理接続が存在することが許容されます。この場合、lmpCcIsIfはifTableで行われる偽（2）、及び対応するエントリに設定されています。

8.1. Support of the LMP Layer by ifTable

8.1. ifTableのことでLMP層のサポート

Some specific interpretations of ifTable for the LMP layer follow.

LMP層のフォローのためのifTableのいくつかの特定の解釈。

Object Use for the LMP layer.

LMP層のオブジェクトを使用します。

ifIndex Each LMP interface may be represented by an ifEntry.

ifIndexの各LMPインタフェースはifEntryをで表すことができます。

ifDescr Description of the LMP interface.

LMPインタフェースののifDescr説明。

ifType The value that is allocated for LMP is 227. This number has been assigned by the IANA.

LMPのために割り当てられるifTypeの値がこの数値は、IANAによって割り当てられた227です。

ifSpeed The total bandwidth in bits per second for use by the LMP layer.

LMP層による使用のために秒あたりのビット数の総帯域幅のifSpeed。

ifPhysAddress Unused.

ますifPhysAddress未使用。

ifAdminStatus This variable indicates the administrator's intent as to whether LMP should be enabled, disabled, or running in some diagnostic testing mode on this interface. Also see [RFC2863].

この変数のifAdminStatus LMPが無効、有効、またはこのインターフェイス上でいくつかの診断テスト・モードで実行するか否かを管理者の意図を示しています。また、[RFC2863]を参照してください。

ifOperStatus This value reflects the actual or operational status of LMP on this interface.

この値のifOperStatusこのインターフェイス上のLMPの実際や動作状態を反映しています。

ifLastChange See [RFC2863].

[RFC2863]を参照してくださいifLastChange。

ifInOctets The number of received octets over the interface; i.e., the number of octets received as LMP packets.

ifInOctetsインタフェースを介して受信されたオクテットの数。即ち、オクテットの数は、LMPパケットとして受け取りました。

ifOutOctets The number of transmitted octets over the interface; i.e., the number of octets transmitted as LMP packets.

ifOutOctetsインタフェースを介して送信されたオクテットの数。すなわち、LMPパケットとして送信されるオクテットの数。

ifInErrors The number of LMP packets dropped due to uncorrectable errors.

ifInErrorsはLMPパケットの数は、訂正不可能なエラーに起因する低下しました。

ifInUnknownProtos The number of received packets discarded during packet header validation, including packets with unrecognized label values.

認識されていないラベル値を有するパケットを含むパケットヘッダの検証中に廃棄された受信パケットの数ifInUnknownProtos。

ifOutErrors See [RFC2863].

ifOutErrorsは、[RFC2863]を参照してください。

ifName Textual name (unique on this system) of the interface or an octet string of zero length.

インターフェイスまたはゼロ長のオクテット列のテキストのifName名（このシステム上で一意）。

ifLinkUpDownTrapEnable Default is disabled (2).

ifLinkUpDownTrapEnableデフォルトは無効になっています（2）。

ifConnectorPresent Set to false (2).

falseにifConnectorPresentセット（2）。

ifHighSpeed See [RFC2863].

[RFC2863]を参照してくださいifHighSpeed。

ifHCInOctets The 64-bit version of ifInOctets; supported if required by the compliance statements in [RFC2863].

ifHCInOctetsのifInOctetsの64ビット版。 [RFC2863]でのコンプライアンスステートメントで必要な場合サポートされています。

ifHCOutOctets The 64-bit version of ifOutOctets; supported if required by the compliance statements in [RFC2863].

ifHCOutOctets ifOutOctetsの64ビットバージョン。 [RFC2863]でのコンプライアンスステートメントで必要な場合サポートされています。

ifAlias The nonvolatile 'alias' name for the interface, as specified by a network manager.

インターフェイスのための不揮発性「エイリアス」名ifAlias、ネットワーク管理者によって指定されました。

ifCounterDiscontinuityTime See [RFC2863].

ifCounterDiscontinuityTimeは、[RFC2863]を参照してください。

9. LMP MIB Module Definitions

9. LMP MIBモジュール定義

This MIB module IMPORTs objects from [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC4220], and it has REFERENCE clauses to [RFC4204], [RFC4207], [RFC4209], [RFC3471], and [RFC2914].

[RFC2578]、[RFC2579]、[RFC2580]、[RFC2863]、[RFC4001]、およびからこのMIBモジュールは、インポートオブジェクト[RFC4220]、そしてそれは[RFC4204]を参照句、[RFC4207]、[RFC4209]を、[有しますRFC3471]、および[RFC2914]。

LMP-MIB DEFINITIONS ::= BEGIN

IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, transmission, Unsigned32, Counter32, TimeTicks FROM SNMPv2-SMI -- RFC 2578

輸入MODULE-IDENTITY、OBJECT-TYPE、NOTIFICATION-TYPE、トランスミッション、Unsigned32の、Counter32の、SNMPv2の-SMIからの時間刻み - RFC 2578

MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580

MODULE-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUPのSNMPv2-CONF FROM - RFC 2580

TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TimeStamp

TEXTUAL-CONVENTION、のTruthValue、RowStatusの、StorageType、タイムスタンプ

FROM SNMPv2-TC -- RFC 2579

SNMPv2の-TC FROM - RFC 2579

InterfaceIndexOrZero, ifIndex FROM IF-MIB -- RFC 2863

InterfaceIndexOrZeroの、ifIndexのFROM IF-MIB - RFC 2863

InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC 4001

INET-ADDRESS-MIBからのInetAddressType、InetAddressの - RFC 4001

teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType FROM TE-LINK-STD-MIB; -- RFC 4220

teLinkRemoteIpAddr、teLinkIncomingIfId、TE-LINK-STD-MIBからTeLinkEncodingType。 - RFC 4220

lmpMIB MODULE-IDENTITY LAST-UPDATED "200608140000Z" -- 14 August 2006 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) Working Group" CONTACT-INFO " Martin Dubuc Email: dubuc.consulting@sympatico.ca

lmpMIBのMODULE-IDENTITY LAST-UPDATED "200608140000Z" - 2006年8月14日ORGANIZATION "共通コントロールおよび測定プロトコル（CCAMP）ワーキンググループ" CONTACT-INFO「マーティンDubuc電子メール：dubuc.consulting@sympatico.ca

                Thomas D. Nadeau
        Email:  tnadeau@cisco.com

Jonathan P. Lang Email: jplang@ieee.org

ジョナサンP.ラングEメール：jplang@ieee.org

Evan McGinnis Email: emcginnis@hammerheadsystems.com

エヴァンマクギニスEメール：emcginnis@hammerheadsystems.com

Adrian Farrel Email: adrian@olddog.co.uk"

エードリアンファレルメール：adrian@olddog.co.uk "

。DESCRIPTION「著作権（C）2006ザ・インターネット協会MIBモジュールのこのバージョンはRFC 4631の一部です;完全な適法な通知についてはRFC自体を参照してください。

        This MIB module contains managed object definitions for
        the Link Management Protocol (LMP) as
        defined in 'Link Management Protocol'."

-- Revision history. REVISION "200608140000Z" -- 14 August 2006 DESCRIPTION "Revised version: - Fixes textual descriptions of TruthValue settings such that True is always 1 and False is always 2. - Adds punctuation to REFERENCE clauses.

- 改訂履歴。 REVISION「200608140000Z」 - 2006年8月14日DESCRIPTION「改訂版： - 真のは常に1であるとFalseようTruthValueの設定の修正のテキスト記述は常に2です - 節を参照するために句読点を追加します。

        This revision published as RFC 4631"
   REVISION
       "200601110000Z"  -- 11 January 2006
   DESCRIPTION
       "Initial version published as RFC 4327"
   ::= { transmission 227 }

-- Textual Conventions

- テキストの表記法

LmpInterval ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "d"
   STATUS        current
   DESCRIPTION
       "The interval delay, in milliseconds."
   SYNTAX        Unsigned32 (1..65535)

LmpRetransmitInterval ::= TEXTUAL-CONVENTION
   DISPLAY-HINT "d"
   STATUS        current
   DESCRIPTION
       "The retransmission interval delay in milliseconds."
   SYNTAX        Unsigned32 (1..4294967295)

LmpNodeId ::= TEXTUAL-CONVENTION
   DISPLAY-HINT  "1d.1d.1d.1d"
   STATUS        current
   DESCRIPTION
       "Represents a Node ID in network byte order.  Node ID is an
        address of type IPv4."
   REFERENCE
       "Section 1.1 of Link Management Protocol, RFC 4204."
   SYNTAX        OCTET STRING(SIZE(4))

-- Top level components of this MIB

- このMIBのトップレベルのコンポーネント

-- Notifications
lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 }
-- Tables, Scalars
lmpObjects       OBJECT IDENTIFIER ::= { lmpMIB 1 }
-- Conformance
lmpConformance   OBJECT IDENTIFIER ::= { lmpMIB 2 }

lmpAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The desired operational status of LMP on the node.

lmpAdminStatusのOBJECT-TYPE SYNTAX INTEGER {アップ（1）、ダウン（2）} MAX-ACCESS読み取りと書き込みステータス現在の説明「ノード上のLMPの所望の動作状態。

        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."

   DEFVAL        { up }
   ::= { lmpObjects 1 }

lmpOperStatus OBJECT-TYPE
   SYNTAX        INTEGER { up(1), down(2) }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of LMP on the node."
   ::= { lmpObjects 2 }

-- LMP Neighbor Table

- LMPネイバーテーブル

lmpNbrTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpNbrEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies the neighbor node(s) to which control
        channels may be established."
   ::= { lmpObjects 3 }

lmpNbrEntry OBJECT-TYPE
   SYNTAX        LmpNbrEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by a LMP-enabled device for
        every pair of nodes that can establish control channels."
   INDEX         { lmpNbrNodeId }
   ::= { lmpNbrTable 1 }

LmpNbrEntry ::= SEQUENCE {
  lmpNbrNodeId              LmpNodeId,
  lmpNbrRetransmitInterval  LmpRetransmitInterval,
  lmpNbrRetryLimit          Unsigned32,
  lmpNbrRetransmitDelta     Unsigned32,
  lmpNbrAdminStatus         INTEGER,
  lmpNbrOperStatus          INTEGER,
  lmpNbrRowStatus           RowStatus,
  lmpNbrStorageType         StorageType
}

lmpNbrNodeId OBJECT-TYPE SYNTAX LmpNodeId

lmpNbrNodeIdのOBJECT-TYPE SYNTAX LmpNodeId

   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This is a unique index for an entry in the LmpNbrTable.
        This value represents the remote Node ID."
   ::= { lmpNbrEntry 1 }

lmpNbrRetransmitInterval OBJECT-TYPE SYNTAX LmpRetransmitInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the initial retransmission interval that is used for the retransmission of messages that require acknowledgement. This object, along with lmpNbrRetryLimit, is used to implement the congestion-handling mechanism defined in Section 10 of the Link Management Protocol specification, which is based on RFC 2914." REFERENCE "Link Management Protocol, RFC 4204.

lmpNbrRetransmitInterval OBJECT-TYPE SYNTAX LmpRetransmitInterval MAX-ACCESSはリード作成しますステータス現在の説明は「このオブジェクトは確認応答を必要とするメッセージの再送信のために使用される初期再送間隔を指定します。このオブジェクトは、lmpNbrRetryLimitとともに、輻輳処理を実装するために使用されますRFC 2914に基づいているリンク管理プロトコル仕様のセクション10で定義されたメカニズム」 REFERENCE「リンク管理プロトコル、RFC 4204。

        Congestion Control Principles, RFC 2914."
   DEFVAL        { 500 }
   ::= { lmpNbrEntry 2 }

lmpNbrRetryLimit OBJECT-TYPE
   SYNTAX        Unsigned32
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the maximum number of times a message
        is transmitted without being acknowledged.  A value of 0 is used
        to indicate that a node should never stop retransmission.
        This object, along with lmpNbrRetransmitInterval, is
        used to implement the congestion-handling mechanism as defined
        in Section 10 of the Link Management Protocol specification,
        which is based on RFC 2914."
   REFERENCE
       "Link Management Protocol, RFC 4204.
        Congestion Control Principles, RFC 2914."
   DEFVAL        { 3 }
   ::= { lmpNbrEntry 3 }

lmpNbrRetransmitDelta OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION

lmpNbrRetransmitDeltaのOBJECT-TYPE構文Unsigned32 MAX-ACCESSはリード作成しますステータス現在の説明

       "This object governs the speed with which the sender increases
        the retransmission interval, as explained in Section 10 of the
        Link Management Protocol specification, which is based on
        RFC 2914.  This value is a power used to express the
        exponential backoff.  The ratio of two successive retransmission
        intervals is (1 + Delta)."
   REFERENCE
       "Link Management Protocol, RFC 4204.
        Congestion Control Principles, RFC 2914."
   DEFVAL        { 1 }
   ::= { lmpNbrEntry 4 }

lmpNbrAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER { up(1), down(2) }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The desired operational status of LMP to this remote node."
   ::= { lmpNbrEntry 5 }

lmpNbrOperStatus OBJECT-TYPE
   SYNTAX        INTEGER { up(1), down(2) }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of LMP to this remote node."
   ::= { lmpNbrEntry 6 }

lmpNbrRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table.  None of the writable objects
        in a row can be changed if the status is active(1).
        All read-create objects must have valid and consistent
        values before the row can be activated."
   ::= { lmpNbrEntry 7 }

lmpNbrStorageType OBJECT-TYPE
   SYNTAX        StorageType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The storage type for this conceptual row in the
        lmpNbrTable.  Conceptual rows having the value
        'permanent' need not allow write-access to any columnar object in the row."
   DEFVAL        { nonVolatile }
   ::= { lmpNbrEntry 8 }

-- End of lmpNbrTable

- lmpNbrTableの終わり

lmpCcHelloIntervalDefault OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object specifies the default value for the HelloInterval
        parameter used in the Hello protocol keep-alive phase.  It
        indicates how frequently LMP Hello messages will be sent.  It
        is used as the default value for lmpCcHelloInterval.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpObjects 4 }

lmpCcHelloIntervalDefaultMin OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object specifies the default minimum value for the
        HelloInterval parameter.  It is used as a default value
        for lmpCcHelloIntervalMin.  Implementations should save the
        value of this object in persistent memory so that it survives
        restarts or reboot."
   ::= { lmpObjects 5 }

lmpCcHelloIntervalDefaultMax OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object specifies the default maximum value for the
        HelloInterval parameter.  It is used as a default value
        for lmpCcHelloIntervalMax.  Implementations should save the
        value of this object in persistent memory so that it survives
        restarts or reboot."
   ::= { lmpObjects 6 }

lmpCcHelloDeadIntervalDefault OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write

lmpCcHelloDeadIntervalDefaultのOBJECT-TYPE SYNTAX LmpInterval MAX-ACCESSの読み取りと書き込み

   STATUS        current
   DESCRIPTION
       "This object specifies the default HelloDeadInterval parameter
        to use in the Hello protocol keep-alive phase.  It indicates
        how long a device should wait before declaring the control
        channel dead.  The HelloDeadInterval parameter should be at
        least three times the value of HelloInterval.  It is used as
        a default value for lmpCcHelloDeadInterval.  Implementations
        should save the value of this object in persistent memory so
        that it survives restarts or reboot."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpObjects 7 }

lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object specifies the default minimum value for the
        HelloDeadInterval parameter.  It is used as a default value
        for lmpCcHelloDeadIntervalMin.  Implementations should save
        the value of this object in persistent memory so that it
        survives restarts or reboot."
   ::= { lmpObjects 8 }

lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object specifies the default maximum value for the
        HelloDeadInterval parameter.  It is used as a default value
        for lmpCcHelloDeadIntervalMax.  Implementations should save the
        value of this object in persistent memory so that it survives
        restarts or reboot."
   ::= { lmpObjects 9 }

-- LMP Control Channel Table

- LMP制御チャネル表

lmpControlChannelTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpControlChannelEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies LMP control channel information."
   ::= { lmpObjects 10 }

lmpControlChannelEntry OBJECT-TYPE
   SYNTAX        LmpControlChannelEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by an LMP-enabled device for
        every control channel.  Whenever a new entry is created with
        lmpCcIsIf set to true(1), a corresponding entry is
        created in ifTable as well (see RFC 2863)."
   INDEX         { lmpCcId }
   ::= { lmpControlChannelTable 1 }

LmpControlChannelEntry ::= SEQUENCE {
  lmpCcId                            Unsigned32,
  lmpCcUnderlyingIfIndex             InterfaceIndexOrZero,
  lmpCcIsIf                          TruthValue,
  lmpCcNbrNodeId                     LmpNodeId,
  lmpCcRemoteId                      Unsigned32,
  lmpCcRemoteAddressType             InetAddressType,
  lmpCcRemoteIpAddr                  InetAddress,
  lmpCcSetupRole                     INTEGER,
  lmpCcAuthentication                TruthValue,
  lmpCcHelloInterval                 LmpInterval,
  lmpCcHelloIntervalMin              LmpInterval,
  lmpCcHelloIntervalMax              LmpInterval,
  lmpCcHelloIntervalNegotiated       LmpInterval,
  lmpCcHelloDeadInterval             LmpInterval,
  lmpCcHelloDeadIntervalMin          LmpInterval,
  lmpCcHelloDeadIntervalMax          LmpInterval,
  lmpCcHelloDeadIntervalNegotiated   LmpInterval,
  lmpCcLastChange                    TimeTicks,
  lmpCcAdminStatus                   INTEGER,
  lmpCcOperStatus                    INTEGER,
  lmpCcRowStatus                     RowStatus,
  lmpCcStorageType                   StorageType
}

lmpCcId OBJECT-TYPE
   SYNTAX        Unsigned32 (1..4294967295)
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This value represents the local control channel identifier.
        The control channel identifier is a non-zero 32-bit number."
   ::= { lmpControlChannelEntry 1 }

lmpCcUnderlyingIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero

lmpCcUnderlyingIfIndexのOBJECT-TYPE SYNTAX InterfaceIndexOrZeroの

   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "If lmpCcIsIf is set to true(1), this object carries the
        index into the ifTable of the entry that represents the
        LMP interface over which LMP will transmit its traffic.
        If this object is set to zero but lmpCcIsIf is set to
        true(1), the control channel is not currently associated
        with any underlying interface, and the control channel's
        operational status must not be up(1); nor should the
        control channel forward or receive traffic.
        If lmpCcIsIf is set to false(2), this object should be set
        to zero and ignored."
   ::= { lmpControlChannelEntry 2 }

lmpCcIsIf OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "In implementations where the control channels are modeled
        as interfaces, the value of this object is true(1), and
        this control channel is represented by an interface in
        the interfaces group table as indicated by the value of
        lmpCcUnderlyingIfIndex.  If control channels are not
        modeled as interfaces, the value of this object is
        false(2), and there is no corresponding interface for
        this control channel in the interfaces group table;
        the value of lmpCcUnderlyingIfIndex should be
        ignored."
   ::= { lmpControlChannelEntry 3 }

lmpCcNbrNodeId OBJECT-TYPE
   SYNTAX        LmpNodeId
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This is the Node ID of the control channel remote node.
        This value either is configured or gets created by the node
        when a Config message is received or when an outgoing Config
        message is acknowledged by the remote node."
   ::= { lmpControlChannelEntry 4 }

lmpCcRemoteId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION

lmpCcRemoteId OBJECT-TYPE構文Unsigned32 MAX-ACCESS read-onlyステータス現在の説明

       "This value represents the remote control channel identifier
        (32-bit number).  It is determined during the negotiation
        phase.  A value of zero means that the remote control channel
        identifier has not yet been learned."
   ::= { lmpControlChannelEntry 5 }

lmpCcRemoteAddressType OBJECT-TYPE
   SYNTAX        InetAddressType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This value represents the remote control channel IP address
        type.  In point-to-point configuration, this value can be set
        to unknown(0)."
   ::= { lmpControlChannelEntry 6 }

lmpCcRemoteIpAddr OBJECT-TYPE
   SYNTAX        InetAddress
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This value represents the remote control channel Internet
        address for numbered control channel.  The type of this
        address is determined by lmpCcRemoteAddressType.
        The control channel must be numbered on non-point-to-point
        configuration.  For point-to-point configuration, the
        remote control channel address can be of type unknown,
        in which case this object must be a zero-length string.  The
        lmpCcRemoteId object then identifies the unnumbered
        address."
   ::= { lmpControlChannelEntry 7 }

lmpCcSetupRole OBJECT-TYPE
   SYNTAX        INTEGER { active(1), passive(2) }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The role that this node should take during establishment
        of this control channel.  An active node will initiate
        establishment.  A passive node will wait for the remote node
        to initiate.  A pair of nodes that both take the passive role
        will never establish communications."
   DEFVAL        { active }
   ::= { lmpControlChannelEntry 8 }

lmpCcAuthentication OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create

lmpCcAuthentication OBJECT-TYPE構文のTruthValue MAX-ACCESSはリード作成します

   STATUS        current
   DESCRIPTION
       "This object indicates whether the control channel must use
        authentication."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpControlChannelEntry 9 }

lmpCcHelloInterval OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the value of the HelloInterval
        parameter.  The default value for this object should be
        set to lmpCcHelloIntervalDefault."
   ::= { lmpControlChannelEntry 10 }

lmpCcHelloIntervalMin OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the minimum value for the
        HelloInterval parameter.  The default value for this
        object should be set to lmpCcHelloIntervalMinDefault."
   ::= { lmpControlChannelEntry 11 }

lmpCcHelloIntervalMax OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the maximum value for the
        HelloInterval parameter.  The default value for this
        object should be set to lmpCcHelloIntervalMaxDefault."
   ::= { lmpControlChannelEntry 12 }

lmpCcHelloIntervalNegotiated OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Once the control channel is active, this object represents
        the negotiated HelloInterval value."
   ::= { lmpControlChannelEntry 13 }

lmpCcHelloDeadInterval OBJECT-TYPE

   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the value of the HelloDeadInterval
        parameter.  The default value for this object should be
        set to lmpCcHelloDeadIntervalDefault."
   ::= { lmpControlChannelEntry 14 }

lmpCcHelloDeadIntervalMin OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the minimum value for the
        HelloDeadInterval parameter.  The default value for this
        object should be set to lmpCcHelloDeadIntervalMinDefault."
   ::= { lmpControlChannelEntry 15 }

lmpCcHelloDeadIntervalMax OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the maximum value for the
        HelloDeadInterval parameter.  The default value for this
        object should be set to lmpCcHelloIntervalMaxDefault."
   ::= { lmpControlChannelEntry 16 }

lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "Once the control channel is active, this object represents
        the negotiated HelloDeadInterval value."
   ::= { lmpControlChannelEntry 17 }

lmpCcLastChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time the control channel entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value."

lmpCcLastChangeのOBJECT-TYPE SYNTAX TimeTicksのMAX-ACCESS read-onlyステータス現在の説明「制御チャネルは、現在の動作状態に入った時のsysUpTimeの値。現在の状態がローカルネットワーク管理の最後の再初期設定前に入力された場合サブシステムは、このオブジェクトはゼロ値が含まれています。」

   ::= { lmpControlChannelEntry 18 }

lmpCcAdminStatus OBJECT-TYPE
   SYNTAX        INTEGER { up(1), down(2) }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The desired operational status of this control channel."
   ::= { lmpControlChannelEntry 19 }

lmpCcOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
                     up(1),
                     down(2),
                     configSnd(3),
                     configRcv(4),
                     active(5),
                     goingDown(6)
                 }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of this control channel."
   ::= { lmpControlChannelEntry 20 }

lmpCcRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table.  None of the writable objects
        in a row can be changed if the status is active(1).
        All read-create objects must have valid and consistent
        values before the row can be activated."
   ::= { lmpControlChannelEntry 21 }

lmpCcStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this conceptual row in the lmpControlChannelTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row."

lmpCcStorageType OBJECT-TYPE構文StorageType MAX-ACCESS読作成ステータス現在の説明「lmpControlChannelTableにおけるこの概念的な列のためのストレージタイプを。概念的な行は行の任意の円柱状のオブジェクトへの書き込みアクセスを許可する必要がない『永久的な』値を有します。」

DEFVAL { nonVolatile }

DEFVAL {} nonVolatileの

   ::= { lmpControlChannelEntry 22 }

-- End of lmpControlChannelTable

- lmpControlChannelTableの終わり

-- LMP Control Channel Performance Table

- LMP制御チャネルの性能表

lmpControlChannelPerfTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpControlChannelPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies LMP control channel performance
        counters."
   ::= { lmpObjects 11 }

lmpControlChannelPerfEntry OBJECT-TYPE
   SYNTAX        LmpControlChannelPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by a LMP-enabled device for
        every control channel.  lmpCcCounterDiscontinuityTime is used
        to indicate potential discontinuity for all counter objects
        in this table."
   INDEX         { lmpCcId }
   ::= { lmpControlChannelPerfTable 1 }

LmpControlChannelPerfEntry ::= SEQUENCE {
  lmpCcInOctets                    Counter32,
  lmpCcInDiscards                  Counter32,
  lmpCcInErrors                    Counter32,
  lmpCcOutOctets                   Counter32,
  lmpCcOutDiscards                 Counter32,
  lmpCcOutErrors                   Counter32,
  lmpCcConfigReceived              Counter32,
  lmpCcConfigSent                  Counter32,
  lmpCcConfigRetransmit            Counter32,
  lmpCcConfigAckReceived           Counter32,
  lmpCcConfigAckSent               Counter32,
  lmpCcConfigNackReceived          Counter32,
  lmpCcConfigNackSent              Counter32,
  lmpCcHelloReceived               Counter32,
  lmpCcHelloSent                   Counter32,
  lmpCcBeginVerifyReceived         Counter32,
  lmpCcBeginVerifySent             Counter32,
  lmpCcBeginVerifyRetransmit       Counter32,
  lmpCcBeginVerifyAckReceived      Counter32, lmpCcBeginVerifyAckSent          Counter32,
  lmpCcBeginVerifyNackReceived     Counter32,
  lmpCcBeginVerifyNackSent         Counter32,
  lmpCcEndVerifyReceived           Counter32,
  lmpCcEndVerifySent               Counter32,
  lmpCcEndVerifyRetransmit         Counter32,
  lmpCcEndVerifyAckReceived        Counter32,
  lmpCcEndVerifyAckSent            Counter32,
  lmpCcTestStatusSuccessReceived   Counter32,
  lmpCcTestStatusSuccessSent       Counter32,
  lmpCcTestStatusSuccessRetransmit Counter32,
  lmpCcTestStatusFailureReceived   Counter32,
  lmpCcTestStatusFailureSent       Counter32,
  lmpCcTestStatusFailureRetransmit Counter32,
  lmpCcTestStatusAckReceived       Counter32,
  lmpCcTestStatusAckSent           Counter32,
  lmpCcLinkSummaryReceived         Counter32,
  lmpCcLinkSummarySent             Counter32,
  lmpCcLinkSummaryRetransmit       Counter32,
  lmpCcLinkSummaryAckReceived      Counter32,
  lmpCcLinkSummaryAckSent          Counter32,
  lmpCcLinkSummaryNackReceived     Counter32,
  lmpCcLinkSummaryNackSent         Counter32,
  lmpCcChannelStatusReceived       Counter32,
  lmpCcChannelStatusSent           Counter32,
  lmpCcChannelStatusRetransmit     Counter32,
  lmpCcChannelStatusAckReceived    Counter32,
  lmpCcChannelStatusAckSent        Counter32,
  lmpCcChannelStatusReqReceived    Counter32,
  lmpCcChannelStatusReqSent        Counter32,
  lmpCcChannelStatusReqRetransmit  Counter32,
  lmpCcChannelStatusRspReceived    Counter32,
  lmpCcChannelStatusRspSent        Counter32,
  lmpCcCounterDiscontinuityTime    TimeStamp
}

lmpCcInOctets OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The total number of LMP message octets received on the
             control channel."
    ::= { lmpControlChannelPerfEntry 1 }

lmpCcInDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only

lmpCcInDiscardsのOBJECT-TYPE SYNTAXカウンタACCESS read-only

    STATUS      current
    DESCRIPTION
            "The number of inbound packets that were chosen to be
             discarded even though no errors had been detected.  One
             possible reason for discarding such a packet could be to
             free up buffer space."
    ::= { lmpControlChannelPerfEntry 2 }

lmpCcInErrors OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The number of inbound packets that contained errors
             preventing them from being processed by LMP."
    ::= { lmpControlChannelPerfEntry 3 }

lmpCcOutOctets OBJECT-TYPE
    SYNTAX       Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The total number of LMP message octets transmitted out of
             the control channel."
    ::= { lmpControlChannelPerfEntry 4 }

lmpCcOutDiscards OBJECT-TYPE
    SYNTAX       Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The number of outbound packets that were chosen to be
             discarded even though no errors had been detected to
             prevent their being transmitted.  One possible reason
             for discarding such a packet could be to free up buffer
             space."
    ::= { lmpControlChannelPerfEntry 5 }

lmpCcOutErrors OBJECT-TYPE
    SYNTAX       Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The number of outbound packets that could not be
             transmitted because of errors."
    ::= { lmpControlChannelPerfEntry 6 }

lmpCcConfigReceived OBJECT-TYPE

   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Config messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 7 }

lmpCcConfigSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Config messages that have
        been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 8 }

lmpCcConfigRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Config messages that
        have been retransmitted over this control channel."
   ::= { lmpControlChannelPerfEntry 9 }

lmpCcConfigAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ConfigAck messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 10 }

lmpCcConfigAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ConfigAck messages that have
        been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 11 }

lmpCcConfigNackReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current

lmpCcConfigNackReceived OBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在

   DESCRIPTION
       "This object counts the number of ConfigNack messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 12 }

lmpCcConfigNackSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ConfigNack messages that have
        been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 13 }

lmpCcHelloReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Hello messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 14 }

lmpCcHelloSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Hello messages that have
        been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 15 }

lmpCcBeginVerifyReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerify messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 16 }

lmpCcBeginVerifySent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of BeginVerify messages that have been sent on this control channel."

lmpCcBeginVerifySentのOBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトはこの制御チャンネルで送られたBeginVerifyメッセージの数をカウントします。」

   ::= { lmpControlChannelPerfEntry 17 }

lmpCcBeginVerifyRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerify messages that
        have been retransmitted over this control channel."
   ::= { lmpControlChannelPerfEntry 18 }

lmpCcBeginVerifyAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyAck messages that
        have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 19 }

lmpCcBeginVerifyAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyAck messages that
        have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 20 }

lmpCcBeginVerifyNackReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyNack messages that
        have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 21 }

lmpCcBeginVerifyNackSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyNack messages that
        have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 22 }

lmpCcEndVerifyReceived OBJECT-TYPE

   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that have
        been received on this control channel."
   ::= { lmpControlChannelPerfEntry 23 }

lmpCcEndVerifySent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that have
        been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 24 }

lmpCcEndVerifyRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that
        have been retransmitted over this control channel."
   ::= { lmpControlChannelPerfEntry 25 }

lmpCcEndVerifyAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerifyAck messages that
        have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 26 }

lmpCcEndVerifyAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerifyAck messages that
        have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 27 }

lmpCcTestStatusSuccessReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current

lmpCcTestStatusSuccessReceived OBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在

   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 28 }

lmpCcTestStatusSuccessSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 29 }

lmpCcTestStatusSuccessRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been retransmitted over this control channel."
   ::= { lmpControlChannelPerfEntry 30 }

lmpCcTestStatusFailureReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusFailure messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 31 }

lmpCcTestStatusFailureSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusFailure messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 32 }

lmpCcTestStatusFailureRetransmit OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of TestStatusFailure messages that have been retransmitted over this control channel."

lmpCcTestStatusFailureRetransmitのOBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトはこの制御チャネルを介して再送されたTestStatusFailureメッセージの数をカウントします。」

   ::= { lmpControlChannelPerfEntry 33 }

lmpCcTestStatusAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusAck messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 34 }

lmpCcTestStatusAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusAck messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 35 }

lmpCcLinkSummaryReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 36 }

lmpCcLinkSummarySent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 37 }

lmpCcLinkSummaryRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages that
        have been retransmitted over this control channel."
   ::= { lmpControlChannelPerfEntry 38 }

lmpCcLinkSummaryAckReceived OBJECT-TYPE

   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryAck messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 39 }

lmpCcLinkSummaryAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryAck messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 40 }

lmpCcLinkSummaryNackReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryNack messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 41 }

lmpCcLinkSummaryNackSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryNack messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 42 }

lmpCcChannelStatusReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 43 }

lmpCcChannelStatusSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current

lmpCcChannelStatusSentのOBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在

   DESCRIPTION
       "This object counts the number of ChannelStatus messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 44 }

lmpCcChannelStatusRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages
        that have been retransmitted on this control channel."
   ::= { lmpControlChannelPerfEntry 45 }

lmpCcChannelStatusAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusAck messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 46 }

lmpCcChannelStatusAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 47 }

lmpCcChannelStatusReqReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusRequest messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 48 }

lmpCcChannelStatusReqSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of ChannelStatusRequest messages that have been sent on this control channel."

lmpCcChannelStatusReqSentのOBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトはこの制御チャンネルで送られたChannelStatusRequestメッセージの数をカウントします。」

   ::= { lmpControlChannelPerfEntry 49 }

lmpCcChannelStatusReqRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusRequest messages
        that have been retransmitted on this control channel."
   ::= { lmpControlChannelPerfEntry 50 }

lmpCcChannelStatusRspReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusResponse messages
        that have been received on this control channel."
   ::= { lmpControlChannelPerfEntry 51 }

lmpCcChannelStatusRspSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusResponse messages
        that have been sent on this control channel."
   ::= { lmpControlChannelPerfEntry 52 }

lmpCcCounterDiscontinuityTime OBJECT-TYPE
    SYNTAX       TimeStamp
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The value of sysUpTime on the most recent occasion at which
         one or more of this control channel's counters suffered a
         discontinuity.  The relevant counters are the specific
         instances associated with this control channel of any
         Counter32 object contained in the lmpControlChannelPerfTable.
         If no such discontinuities have occurred since the last re-
         initialization of the local management subsystem, then this
         object contains a zero value."
    ::= { lmpControlChannelPerfEntry 53 }

-- End of lmpControlChannelPerfTable

- lmpControlChannelPerfTableの終わり

-- LMP TE Link Table lmpTeLinkTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpTeLinkEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies the LMP-specific TE link information.
        Overall TE link information is kept in three separate tables:
        ifTable for interface-specific information, lmpTeLinkTable
        for LMP specific information, and teLinkTable for generic
        TE link information.  ifIndex is the common index to all
        tables."
   ::= { lmpObjects 12 }

lmpTeLinkEntry OBJECT-TYPE
   SYNTAX        LmpTeLinkEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table exists for each ifEntry with an
        ifType of teLink(200) that is managed by LMP.  An ifEntry with
        an ifIndex must exist before the corresponding lmpTeLinkEntry is
        created.  If a TE link entry in the ifTable is destroyed, then
        so is the corresponding entry in the lmpTeLinkTable.  The
        administrative status value is controlled from the ifEntry.
        Setting the administrative status to testing prompts LMP to
        start link verification on the TE link.  Information about the
        TE link that is not LMP specific is contained in the
        teLinkTable of the TE-LINK-STD-MIB MIB module."
   INDEX         { ifIndex }
   ::= { lmpTeLinkTable 1 }

LmpTeLinkEntry ::= SEQUENCE {
  lmpTeLinkNbrRemoteNodeId  LmpNodeId,
  lmpTeLinkVerification     TruthValue,
  lmpTeLinkFaultManagement  TruthValue,
  lmpTeLinkDwdm             TruthValue,
  lmpTeLinkOperStatus       INTEGER,
  lmpTeLinkRowStatus        RowStatus,
  lmpTeLinkStorageType      StorageType
}

lmpTeLinkNbrRemoteNodeId OBJECT-TYPE
   SYNTAX        LmpNodeId
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This is the Node ID of the TE link remote node.  This value
        may be learned during the control channel parameter negotiation phase (in the Config message).  Node ID is an address whose
        type must be IPv4."
   ::= { lmpTeLinkEntry 1 }

lmpTeLinkVerification OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object indicates whether the LMP link verification
        procedure is enabled for this TE link."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpTeLinkEntry 2 }

lmpTeLinkFaultManagement OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object indicates whether the LMP fault management procedure
        is enabled on this TE link."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpTeLinkEntry 3 }

lmpTeLinkDwdm OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object indicates whether the LMP DWDM procedure is enabled
        on this TE link."
   REFERENCE
       "Link Management Protocol (LMP) for Dense Wavelength Division
        Multiplexing (DWDM) Optical Line Systems, RFC 4209."
   ::= { lmpTeLinkEntry 4 }

lmpTeLinkOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
                   up(1), down(2), testing(3), init(4), degraded(5)
                 }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of this TE link.  The status
        is set to testing when the TE link is performing link
        verification.  A degraded state indicates that there is no active control channel between the pair of nodes that
        form the endpoints of the TE link, but that at least one
        data-bearing link on the TE link is allocated."
   ::= { lmpTeLinkEntry 5 }

lmpTeLinkRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table.  None of the writable objects
        in a row can be changed if the status is active(1).
        All read-create objects must have valid and consistent
        values before the row can be activated."
   ::= { lmpTeLinkEntry 6 }

lmpTeLinkStorageType OBJECT-TYPE
   SYNTAX        StorageType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The storage type for this conceptual row in the
        lmpTeLinkTable.  Conceptual rows having the value
        'permanent' need not allow write-access to any
        columnar object in the row."
   DEFVAL        { nonVolatile }
   ::= { lmpTeLinkEntry 7 }

-- End of lmpTeLinkTable

- lmpTeLinkTableの終わり

lmpGlobalLinkVerificationInterval OBJECT-TYPE
   SYNTAX        Unsigned32
   UNITS         "milliseconds"
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "This object indicates how often the link verification
        procedure is executed.  The interval is in milliseconds.
        A value of 0 is used to indicate that the link
        verification procedure should not be executed.  The
        interval specified in this object should be large enough
        to allow the verification procedure to be completed
        before the start of the next interval.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   ::= { lmpObjects 13 }

-- LMP Link Verification Table

- LMPリンク検証表

lmpLinkVerificationTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpLinkVerificationEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies TE link information associated with the
        LMP verification procedure."
   ::= { lmpObjects 14 }

lmpLinkVerificationEntry OBJECT-TYPE
   SYNTAX        LmpLinkVerificationEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by an LMP-enabled device for
        every TE link that supports the LMP verification
        procedure."
   INDEX         { ifIndex }
   ::= { lmpLinkVerificationTable 1 }

LmpLinkVerificationEntry ::= SEQUENCE {
  lmpLinkVerifyInterval           LmpInterval,
  lmpLinkVerifyDeadInterval       LmpInterval,
  lmpLinkVerifyTransportMechanism BITS,
  lmpLinkVerifyAllLinks           TruthValue,
  lmpLinkVerifyTransmissionRate   Unsigned32,
  lmpLinkVerifyWavelength         Unsigned32,
  lmpLinkVerifyRowStatus          RowStatus,
  lmpLinkVerifyStorageType        StorageType
}

lmpLinkVerifyInterval OBJECT-TYPE
   SYNTAX        LmpInterval
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This object specifies the VerifyInterval parameter used
        in the LMP link verification process.  It indicates the
        interval at which the Test messages are sent."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpLinkVerificationEntry 1 }

lmpLinkVerifyDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-create

lmpLinkVerifyDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESSはリード作成します

   STATUS        current
   DESCRIPTION
       "This object specifies the VerifyDeadInterval parameter used
        in the verification of the physical connectivity of data-
        bearing links.  It specifies the observation period used to
        detect a Test message at the remote node."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpLinkVerificationEntry 2 }

lmpLinkVerifyTransportMechanism OBJECT-TYPE
   SYNTAX        BITS {
                     -- All encoding types:
                     payload(0),
                     -- SONET/SDH encoding type:
                     dccSectionOverheadBytes(1),
                     dccLineOverheadBytes(2),
                     j0Trace(3),
                     j1Trace(4),
                     j2Trace(5)
                 }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This defines the transport mechanism for the Test messages.  The
        scope of this bit mask is restricted to each link encoding
        type.  The local node will set the bits corresponding to the
        various mechanisms it can support for transmitting LMP Test
        messages.  The receiver chooses the appropriate mechanism in the
        BeginVerifyAck message."
   REFERENCE
       "Link Management Protocol, RFC 4204
        Synchronous Optical Network (SONET)/Synchronous Digital
        Hierarchy (SDH) Encoding for Link Management Protocol (LMP)
        Test Messages, RFC 4207."
   ::= { lmpLinkVerificationEntry 3 }

lmpLinkVerifyAllLinks OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "A value of true(1) for this object indicates that the
        verification process checks all unallocated links; otherwise,
        only the new ports or component links that have been added to
        this TE link are verified."
   ::= { lmpLinkVerificationEntry 4 }

lmpLinkVerifyTransmissionRate OBJECT-TYPE
   SYNTAX        Unsigned32
   UNITS         "bytes per second"
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This is the transmission rate of the data link over which
        the Test messages will be transmitted and is expressed in
        bytes per second."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpLinkVerificationEntry 5 }

lmpLinkVerifyWavelength OBJECT-TYPE
   SYNTAX        Unsigned32
   UNITS         "nanometers"
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This value corresponds to the wavelength at
        which the Test messages will be transmitted and is
        measured in nanometers (nm).  If each data-bearing link
        corresponds to a separate wavelength, then this value should
        be set to 0."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpLinkVerificationEntry 6 }

lmpLinkVerifyRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table.  None of the writable objects
        in a row can be changed if the status is active(1).
        All read-create objects must have valid and consistent
        values before the row can be activated."
   ::= { lmpLinkVerificationEntry 7 }

lmpLinkVerifyStorageType OBJECT-TYPE
   SYNTAX        StorageType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The storage type for this conceptual row in the
        lmpLinkVerificationTable.  Conceptual rows having the value
        'permanent' need not allow write-access to any columnar object in the row."
   DEFVAL        { nonVolatile }
   ::= { lmpLinkVerificationEntry 8 }

-- End of lmpLinkVerificationTable

- lmpLinkVerificationTableの終わり

-- LMP TE Link Performance Table

- LMP TEリンク性能表

lmpTeLinkPerfTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpTeLinkPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies LMP TE link performance counters."
   ::= { lmpObjects 15 }

lmpTeLinkPerfEntry OBJECT-TYPE
   SYNTAX        LmpTeLinkPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table is created by an LMP-enabled device for
        every TE link.  lmpTeCounterDiscontinuityTime is used
        to indicate potential discontinuity for all counter objects
        in this table."
   INDEX         { ifIndex }
   ::= { lmpTeLinkPerfTable 1 }

LmpTeLinkPerfEntry ::= SEQUENCE {
  lmpTeInOctets                    Counter32,
  lmpTeOutOctets                   Counter32,
  lmpTeBeginVerifyReceived         Counter32,
  lmpTeBeginVerifySent             Counter32,
  lmpTeBeginVerifyRetransmit       Counter32,
  lmpTeBeginVerifyAckReceived      Counter32,
  lmpTeBeginVerifyAckSent          Counter32,
  lmpTeBeginVerifyNackReceived     Counter32,
  lmpTeBeginVerifyNackSent         Counter32,
  lmpTeEndVerifyReceived           Counter32,
  lmpTeEndVerifySent               Counter32,
  lmpTeEndVerifyRetransmit         Counter32,
  lmpTeEndVerifyAckReceived        Counter32,
  lmpTeEndVerifyAckSent            Counter32,
  lmpTeTestStatusSuccessReceived   Counter32,
  lmpTeTestStatusSuccessSent       Counter32,
  lmpTeTestStatusSuccessRetransmit Counter32,
  lmpTeTestStatusFailureReceived   Counter32, lmpTeTestStatusFailureSent       Counter32,
  lmpTeTestStatusFailureRetransmit Counter32,
  lmpTeTestStatusAckReceived       Counter32,
  lmpTeTestStatusAckSent           Counter32,
  lmpTeLinkSummaryReceived         Counter32,
  lmpTeLinkSummarySent             Counter32,
  lmpTeLinkSummaryRetransmit       Counter32,
  lmpTeLinkSummaryAckReceived      Counter32,
  lmpTeLinkSummaryAckSent          Counter32,
  lmpTeLinkSummaryNackReceived     Counter32,
  lmpTeLinkSummaryNackSent         Counter32,
  lmpTeChannelStatusReceived       Counter32,
  lmpTeChannelStatusSent           Counter32,
  lmpTeChannelStatusRetransmit     Counter32,
  lmpTeChannelStatusAckReceived    Counter32,
  lmpTeChannelStatusAckSent        Counter32,
  lmpTeChannelStatusReqReceived    Counter32,
  lmpTeChannelStatusReqSent        Counter32,
  lmpTeChannelStatusReqRetransmit  Counter32,
  lmpTeChannelStatusRspReceived    Counter32,
  lmpTeChannelStatusRspSent        Counter32,
  lmpTeCounterDiscontinuityTime    TimeStamp
}

lmpTeInOctets OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The total number of LMP message octets received for
             this TE link."
    ::= { lmpTeLinkPerfEntry 1 }

lmpTeOutOctets OBJECT-TYPE
    SYNTAX       Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The total number of LMP message octets transmitted out
             for this TE link."
    ::= { lmpTeLinkPerfEntry 2 }

lmpTeBeginVerifyReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of BeginVerify messages that have

lmpTeBeginVerifyReceived OBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトが持つBeginVerifyメッセージの数を数え

        been received for this TE link."
   ::= { lmpTeLinkPerfEntry 3 }

lmpTeBeginVerifySent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerify messages that have
        been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 4 }

lmpTeBeginVerifyRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerify messages that
        have been retransmitted for this TE link."
   ::= { lmpTeLinkPerfEntry 5 }

lmpTeBeginVerifyAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyAck messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 6 }

lmpTeBeginVerifyAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyAck messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 7 }

lmpTeBeginVerifyNackReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyNack messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 8 }

lmpTeBeginVerifyNackSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of BeginVerifyNack messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 9 }

lmpTeEndVerifyReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that have
        been received for this TE link."
   ::= { lmpTeLinkPerfEntry 10 }

lmpTeEndVerifySent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that have
        been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 11 }

lmpTeEndVerifyRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerify messages that
        have been retransmitted over this control channel."
   ::= { lmpTeLinkPerfEntry 12 }

lmpTeEndVerifyAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerifyAck messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 13 }

lmpTeEndVerifyAckSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only

lmpTeEndVerifyAckSentのOBJECT-TYPE SYNTAXカウンタACCESS read-only

   STATUS        current
   DESCRIPTION
       "This object counts the number of EndVerifyAck messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 14 }

lmpTeTestStatusSuccessReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 15 }

lmpTeTestStatusSuccessSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 16 }

lmpTeTestStatusSuccessRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusSuccess messages
        that have been retransmitted for this TE link."
   ::= { lmpTeLinkPerfEntry 17 }

lmpTeTestStatusFailureReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusFailure messages
        that have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 18 }

lmpTeTestStatusFailureSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of TestStatusFailure messages

lmpTeTestStatusFailureSentのOBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトTestStatusFailureメッセージの数を数え

        that have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 19 }

lmpTeTestStatusFailureRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusFailure messages
        that have been retransmitted on this TE link."
   ::= { lmpTeLinkPerfEntry 20 }

lmpTeTestStatusAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusAck messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 21 }

lmpTeTestStatusAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of TestStatusAck messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 22 }

lmpTeLinkSummaryReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 23 }

lmpTeLinkSummarySent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 24 }

lmpTeLinkSummaryRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummary messages that
        have been retransmitted over this control channel."
   ::= { lmpTeLinkPerfEntry 25 }

lmpTeLinkSummaryAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryAck messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 26 }

lmpTeLinkSummaryAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryAck messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 27 }

lmpTeLinkSummaryNackReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryNack messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 28 }

lmpTeLinkSummaryNackSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of LinkSummaryNack messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 29 }

lmpTeChannelStatusReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only

lmpTeChannelStatusReceived OBJECT-TYPE SYNTAXカウンタACCESS read-only

   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages that
        have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 30 }

lmpTeChannelStatusSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages that
        have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 31 }

lmpTeChannelStatusRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages that
        have been retransmitted for this TE link."
   ::= { lmpTeLinkPerfEntry 32 }

lmpTeChannelStatusAckReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusAck messages
        that have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 33 }

lmpTeChannelStatusAckSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatus messages
        that have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 34 }

lmpTeChannelStatusReqReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of ChannelStatusRequest messages

lmpTeChannelStatusReqReceived OBJECT-TYPE SYNTAXカウンタACCESS read-onlyステータス現在の説明は「このオブジェクトChannelStatusRequestメッセージの数を数え

        that have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 35 }

lmpTeChannelStatusReqSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusRequest messages
        that have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 36 }

lmpTeChannelStatusReqRetransmit OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusRequest messages
        that have been retransmitted for this TE link."
   ::= { lmpTeLinkPerfEntry 37 }

lmpTeChannelStatusRspReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusResponse messages
        that have been received for this TE link."
   ::= { lmpTeLinkPerfEntry 38 }

lmpTeChannelStatusRspSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of ChannelStatusResponse messages
        that have been sent for this TE link."
   ::= { lmpTeLinkPerfEntry 39 }

lmpTeCounterDiscontinuityTime OBJECT-TYPE
    SYNTAX       TimeStamp
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The value of sysUpTime on the most recent occasion at which
         one or more of this TE link's counters suffered a
         discontinuity.  The relevant counters are the specific
         instances associated with this TE link of any Counter32 object contained in the lmpTeLinkPerfTable.  If
         no such discontinuities have occurred since the last re-
         initialization of the local management subsystem, then this
         object contains a zero value."
    ::= { lmpTeLinkPerfEntry 40 }

-- End of lmpTeLinkPerfTable

- lmpTeLinkPerfTableの終わり

-- LMP Data Link Table

- LMPデータリンクテーブル

lmpDataLinkTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpDataLinkEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies the data-bearing links managed by the
        LMP."
   ::= { lmpObjects 16 }

lmpDataLinkEntry OBJECT-TYPE
   SYNTAX        LmpDataLinkEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table exists for each ifEntry that represents
        a data-bearing link.  An ifEntry with an ifIndex must exist
        before the corresponding lmpDataLinkEntry is created.
        If an entry representing the data-bearing link is destroyed in
        the ifTable, then so is the corresponding entry in the
        lmpDataLinkTable.  The administrative status value is
        controlled from the ifEntry.  The index to this table is also
        used to get information in the componentLinkTable
        of the TE-LINK-STD-MIB MIB module."
   INDEX         { ifIndex }
   ::= { lmpDataLinkTable 1 }

LmpDataLinkEntry ::= SEQUENCE {
  lmpDataLinkType               INTEGER,
  lmpDataLinkAddressType        InetAddressType,
  lmpDataLinkIpAddr             InetAddress,
  lmpDataLinkRemoteIpAddress    InetAddress,
  lmpDataLinkRemoteIfId         InterfaceIndexOrZero,
  lmpDataLinkEncodingType       TeLinkEncodingType,
  lmpDataLinkActiveOperStatus   INTEGER,
  lmpDataLinkPassiveOperStatus  INTEGER,
  lmpDataLinkRowStatus          RowStatus,
  lmpDataLinkStorageType        StorageType

}

｝

lmpDataLinkType OBJECT-TYPE
   SYNTAX        INTEGER {
                     port(1),
                     componentLink(2)
                 }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This attribute specifies whether this data-bearing link is
        a port or a component link.  Component links are multiplex
        capable, whereas ports are not multiplex capable."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpDataLinkEntry 1 }

lmpDataLinkAddressType OBJECT-TYPE
   SYNTAX        InetAddressType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This attribute specifies the data-bearing link IP address
        type.  If the data-bearing link is unnumbered, the address
        type must be set to unknown(0)."
   ::= { lmpDataLinkEntry 2 }

lmpDataLinkIpAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The local Internet address for numbered links. The type of this address is determined by the value of lmpDataLinkAddressType object.

lmpDataLinkIpAddr OBJECT-TYPE構文InetAddress MAX-ACCESSはリード作成しますステータス現在の説明「番号のリンクのためのローカルのインターネットアドレスを。このアドレスの種類はlmpDataLinkAddressTypeオブジェクトの値によって決定されます。

        For IPv4 and IPv6 numbered links, this object represents
        the local IP address associated with the data-bearing
        link.  For an unnumbered link, the local address is
        of type unknown, and this object is set to the zero-length
        string; the ifIndex object then identifies the
        unnumbered address."
   ::= { lmpDataLinkEntry 3 }

lmpDataLinkRemoteIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current

lmpDataLinkRemoteIpAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSはリード作成しますステータス現在

DESCRIPTION "The remote Internet address for numbered data-bearing links. The type of this address is determined by the lmpDataLinkAddressType object.

DESCRIPTION「番データ担持リンクのリモートのインターネットアドレス。このアドレスのタイプはlmpDataLinkAddressTypeオブジェクトによって決定されます。

        For IPv4 and IPv6 numbered links, this object represents the
        remote IP address associated with the data-bearing link.  For
        an unnumbered link, the remote address is of type unknown,
        and this object is set to the zero-length string; the
        lmpDataLinkRemoteIfId object then identifies the unnumbered
        address.

        This information is either configured manually or
        communicated by the remote node during the link verification
        procedure."
   ::= { lmpDataLinkEntry 4 }

lmpDataLinkRemoteIfId OBJECT-TYPE
   SYNTAX        InterfaceIndexOrZero
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Interface identifier of the remote end point.  This
        information is either configured manually or
        communicated by the remote node during the link verification
        procedure."
   ::= { lmpDataLinkEntry 5 }

lmpDataLinkEncodingType OBJECT-TYPE
   SYNTAX        TeLinkEncodingType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The encoding type of the data-bearing link."
   REFERENCE
       "Generalized MPLS Signaling Functional Description, RFC 3471."
   ::= { lmpDataLinkEntry 6 }

lmpDataLinkActiveOperStatus OBJECT-TYPE SYNTAX INTEGER { upAlloc(1), upFree(2), down(3), testing(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this data-bearing link

lmpDataLinkActiveOperStatusのOBJECT-TYPE SYNTAX INTEGER {upAlloc（1）、upFree（2）、下（3）、（4）テスト} MAX-ACCESS read-only説明「このデータベアリングリンクの実際の動作状態を

        (active FSM)."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpDataLinkEntry 7 }

lmpDataLinkPassiveOperStatus OBJECT-TYPE
   SYNTAX        INTEGER {
                     upAlloc(1),
                     upFree(2),
                     down(3),
                     psvTst(4) }
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "The actual operational status of this data-bearing link
        (passive FSM)."
   REFERENCE
       "Link Management Protocol, RFC 4204."
   ::= { lmpDataLinkEntry 8 }

lmpDataLinkRowStatus OBJECT-TYPE
   SYNTAX        RowStatus
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "This variable is used to create, modify, and/or
        delete a row in this table.  None of the writable objects
        in a row can be changed if the status is active(1).
        All read-create objects must have valid and consistent
        values before the row can be activated."
   ::= { lmpDataLinkEntry 9 }

lmpDataLinkStorageType OBJECT-TYPE
   SYNTAX        StorageType
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "The storage type for this conceptual row in the
        lmpDataLinkTable.  Conceptual rows having the value
        'permanent' need not allow write-access to any
        columnar object in the row."
   DEFVAL        { nonVolatile }
   ::= { lmpDataLinkEntry 10 }

-- End of lmpDataLinkTable

- lmpDataLinkTableの終わり

-- LMP Data Link Performance Table lmpDataLinkPerfTable OBJECT-TYPE
   SYNTAX        SEQUENCE OF LmpDataLinkPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "This table specifies the data-bearing links LMP performance
        counters."
   ::= { lmpObjects 17 }

lmpDataLinkPerfEntry OBJECT-TYPE
   SYNTAX        LmpDataLinkPerfEntry
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION
       "An entry in this table contains information about
        the LMP performance counters for the data-bearing links.
        lmpDataLinkDiscontinuityTime is used to indicate potential
        discontinuity for all counter objects in this table."
   INDEX         { ifIndex }
   ::= { lmpDataLinkPerfTable 1 }

LmpDataLinkPerfEntry ::= SEQUENCE {
  lmpDataLinkTestReceived        Counter32,
  lmpDataLinkTestSent            Counter32,
  lmpDataLinkActiveTestSuccess   Counter32,
  lmpDataLinkActiveTestFailure   Counter32,
  lmpDataLinkPassiveTestSuccess  Counter32,
  lmpDataLinkPassiveTestFailure  Counter32,
  lmpDataLinkDiscontinuityTime   TimeStamp
}

lmpDataLinkTestReceived OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Test messages that have
        been received on this data-bearing link."
   ::= { lmpDataLinkPerfEntry 1 }

lmpDataLinkTestSent OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of Test messages that have
        been sent on this data-bearing link."
   ::= { lmpDataLinkPerfEntry 2 }

lmpDataLinkActiveTestSuccess OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of data-bearing link tests
        that were successful on the active side of this data-
        bearing link."
   ::= { lmpDataLinkPerfEntry 3 }

lmpDataLinkActiveTestFailure OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of data-bearing link tests
        that failed on the active side of this data-bearing link."
   ::= { lmpDataLinkPerfEntry 4 }

lmpDataLinkPassiveTestSuccess OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of data-bearing link tests
        that were successful on the passive side of this data-
        bearing link."
   ::= { lmpDataLinkPerfEntry 5 }

lmpDataLinkPassiveTestFailure OBJECT-TYPE
   SYNTAX        Counter32
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This object counts the number of data-bearing link tests
        that failed on the passive side of this data-bearing link."
   ::= { lmpDataLinkPerfEntry 6 }

lmpDataLinkDiscontinuityTime OBJECT-TYPE
    SYNTAX       TimeStamp
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The value of sysUpTime on the most recent occasion at which
         one or more of this data-bearing link's counters suffered
         a discontinuity.  The relevant counters are the specific
         instances associated with this data-bearing link of any
         Counter32 object contained in the lmpDataLinkPerfTable.  If no such discontinuities have occurred since the last re-
         initialization of the local management subsystem, then this
         object contains a zero value."
    ::= { lmpDataLinkPerfEntry 7 }

-- End of lmpDataLinkPerfTable

- lmpDataLinkPerfTableの終わり

-- Notification Configuration

- 通知の設定

lmpNotificationMaxRate OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "The LMP notification rate depends on the size of the network, the type of links, the network configuration, the reliability of the network, etc.

lmpNotificationMaxRateのOBJECT-TYPEの構文Unsigned32 MAX-ACCESS読み取りと書き込みステータス現在の説明「LMP通知速度等、ネットワークの大きさ、リンクのタイプ、ネットワーク構成、ネットワークの信頼性に依存します

        When this MIB was designed, care was taken to minimize the
        amount of notifications generated for LMP purposes.  Wherever
        possible, notifications are state driven, meaning that the
        notifications are sent only when the system changes state.
        The only notifications that are repeated and that could cause a
        problem as far as congestion is concerned are the ones
        associated with data link verification.
        Without any considerations to handling of these
        notifications, a problem may arise if the number of data
        links is high.  Since the data link verification notifications
        can happen only once per data link per link verification
        interval, the notification rate should be sustainable if one
        chooses an appropriate link verification interval for a given
        network configuration.  For instance, a network of 100 nodes
        with 5 links of 128 wavelengths each and a link verification
        of 1 minute, where no more than 10% of the links failed at any
        given time, would have 1 notification per second sent from
        each node, or 100 notifications per second for the whole
        network.  The rest of the notifications are negligible
        compared to this number.

To alleviate the congestion problem, the lmpNotificationMaxRate object can be used to implement a throttling mechanism. It is also possible to enable/disable certain type of notifications.

輻輳問題を軽減するために、lmpNotificationMaxRateオブジェクトは、絞り機構を実装するために使用することができます。通知の特定のタイプを有効/無効にすることも可能です。

        This variable indicates the maximum number of
        notifications issued per minute.  If events occur
        more rapidly, the implementation may simply fail to emit these notifications during that period or may
        queue them until an appropriate time.  A value of 0
        means that no throttling is applied and events may be
        notified at the rate at which they occur.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   ::= { lmpObjects 18 }

lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "If this object is true(1), then it enables the
        generation of lmpTeLinkPropertyMismatch
        and lmpDataLinkPropertyMismatch notifications;
        otherwise, these notifications are not emitted.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   DEFVAL        { false }
   ::= { lmpObjects 19 }

lmpUnprotectedNotificationsEnabled OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "If this object is true(1), then it enables the
        generation of lmpUnprotected notifications;
        otherwise, these notifications are not emitted.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   DEFVAL        { false }
   ::= { lmpObjects 20 }

lmpCcUpDownNotificationsEnabled OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "If this object is true(1), then it enables the generation of
        lmpControlChannelUp and lmpControlChannelDown notifications;
        otherwise, these notifications are not emitted.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   DEFVAL        { false }
   ::= { lmpObjects 21 }

lmpTeLinkNotificationsEnabled OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "If this object is true(1), then it enables the
        generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
        notifications; otherwise, these notifications are not emitted.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   DEFVAL        { false }
   ::= { lmpObjects 22 }

lmpDataLinkNotificationsEnabled OBJECT-TYPE
   SYNTAX        TruthValue
   MAX-ACCESS    read-write
   STATUS        current
   DESCRIPTION
       "If this object is true(1), then it enables the
        generation of lmpDataLinkVerificationFailure
        notification; otherwise, these notifications are not emitted.
        Implementations should save the value of this object in
        persistent memory so that it survives restarts or reboot."
   DEFVAL        { false }
   ::= { lmpObjects 23 }

-- Notifications

- 通知

-- Link Property Mismatch Notifications

- リンクプロパティの不一致通知

lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
   OBJECTS       { teLinkRemoteIpAddr,
                   teLinkIncomingIfId }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a TE link property
        mismatch is detected on the node.  The received remote TE link
        ID of the misconfigured TE link is represented by either
        teLinkRemoteIpAddr or teLinkIncomingIfId, depending on whether
        the TE link is numbered or unnumbered.  This notification
        should not be sent unless lmpLinkPropertyNotificationsEnabled
        is true(1).  It is recommended that this notification be
        reported only the first time a mismatch is detected.
        Otherwise, for a given TE link, this notification can occur
        no more than once per verification interval
        (lmpGlobalLinkVerificationInterval)."
   ::= { lmpNotifications 1 }

lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
   OBJECTS       { lmpDataLinkType, lmpDataLinkRemoteIfId }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a data-bearing link
        property mismatch is detected on the node.  lmpDataLinkType
        is used to identify the local identifiers associated with
        the data link.  (The data link interface index can be used
        to determine the TE link interface index, as this
        relationship is captured in the interface stack table.)
        The remote entity interface ID is the remote entity
        interface ID received in the LinkSummary message.
        This notification should not be sent unless
        lmpLinkPropertyNotificationsEnabled is true(1).  It is
        recommended that this notification be reported only the
        first time a mismatch is detected.  Otherwise, for a given
        data link, this notification can occur no more than once
        per verification interval (lmpGlobalLinkVerificationInterval)."
   ::= { lmpNotifications 2 }

-- Neighbor Notification

- 近隣通知

lmpUnprotected NOTIFICATION-TYPE
   OBJECTS       { lmpCcNbrNodeId }
   STATUS        current
   DESCRIPTION
       "This notification is generated when there is more than one
        control channel between LMP neighbors and the last redundant
        control channel has failed.  If the remaining operational
        control channel fails, then there will be no more control
        channels between the pair of nodes and all the TE links
        between the pair of nodes, will go to degraded state.  This
        notification should not be sent unless
        lmpUnprotectedNotificationsEnabled is set to true(1)."
   ::= { lmpNotifications 3 }

-- Control Channel Notifications

- 制御チャネルの通知

lmpControlChannelUp NOTIFICATION-TYPE
   OBJECTS       { lmpCcAdminStatus, lmpCcOperStatus }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a control
        channel transitions to the up operational state.  This
        notification should not be sent unless
        lmpCcUpDownNotificationsEnabled is true(1)."
   ::= { lmpNotifications 4 }

lmpControlChannelDown NOTIFICATION-TYPE
   OBJECTS       { lmpCcAdminStatus, lmpCcOperStatus }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a control channel
        transitions out of the up operational state.  This
        notification should not be sent unless
        lmpCcUpDownNotificationsEnabled is true(1)."
   ::= { lmpNotifications 5 }

-- TE Link Notification

- TEリンク通知

lmpTeLinkDegraded NOTIFICATION-TYPE
   OBJECTS       { lmpTeLinkOperStatus }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a lmpTeLinkOperStatus
        object for a TE link enters the degraded state.  This
        notification should not be sent unless
        lmpTeLinkNotificationsEnabled is true(1)."
   ::= { lmpNotifications 6 }

lmpTeLinkNotDegraded NOTIFICATION-TYPE
   OBJECTS       { lmpTeLinkOperStatus }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a lmpTeLinkOperStatus
        object for a TE link leaves the degraded state.  This
        notification should not be sent unless
        lmpTeLinkNotificationsEnabled is true(1)."
   ::= { lmpNotifications 7 }

-- Data-bearing Link Notification

- データ・ベアリング・リンク通知

lmpDataLinkVerificationFailure NOTIFICATION-TYPE
   OBJECTS       { lmpDataLinkActiveOperStatus,
                   lmpDataLinkPassiveOperStatus }
   STATUS        current
   DESCRIPTION
       "This notification is generated when a data-bearing
        link verification fails.  This notification should not be sent
        unless lmpDataLinkNotificationsEnabled is true(1).  For a given
        data link, this notification can occur no more than once per
        verification interval (lmpGlobalLinkVerificationInterval)."
   ::= { lmpNotifications 8 }

-- End of notifications

- 通知の終わり

-- Module compliance

- モジュールの遵守

lmpCompliances
   OBJECT IDENTIFIER ::= { lmpConformance 1 }

lmpGroups
   OBJECT IDENTIFIER ::= { lmpConformance 2 }

lmpModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the configuration and monitoring of LMP MIB." MODULE -- this module

lmpModuleFullCompliance MODULE-COMPLIANCEステータス現在の説明「LMP MIBの設定と監視をサポートするエージェントのための準拠宣言。」 MODULE - このモジュール

      MANDATORY-GROUPS    { lmpNodeGroup,
                            lmpControlChannelGroup,
                            lmpLinkPropertyCorrelationGroup,
                            lmpPerfGroup,
                            lmpTeLinkGroup,
                            lmpDataLinkGroup }

GROUP lmpCcIsNotInterfaceGroup DESCRIPTION "This group is mandatory for devices that support control channels that are not interfaces, in addition to lmpControlChannelGroup. The following constraint applies: lmpCcIsIf must at least be read-only, returning false(2)."

GROUP lmpCcIsNotInterfaceGroup DESCRIPTION「このグループはlmpControlChannelGroupに加えて、インターフェースない制御チャネルをサポートするデバイスのために必須であり、以下の制約が適用されます。lmpCcIsIfは、少なくとも読み取り専用されなければならない、（2）偽を返します」

GROUP lmpCcIsInterfaceGroup DESCRIPTION "This group is mandatory for devices that support control channels that are interfaces, in addition to lmpControlChannelGroup. The following constraint applies: lmpCcIsIf must at least be read-only, returning true(1)."

GROUP lmpCcIsInterfaceGroup DESCRIPTION「このグループはlmpControlChannelGroupに加えて、インタフェースである制御チャネルをサポートするデバイスのために必須であり、以下の制約が適用されます。lmpCcIsIf少なくとも読み取り専用、trueを返す必要があります（1）。」

GROUP lmpLinkVerificationGroup DESCRIPTION "This group is mandatory for devices that support the link verification procedure."

GROUP lmpLinkVerificationGroup DESCRIPTION「このグループはリンク検証手続をサポートするデバイスのために必須です。」

GROUP lmpNotificationGroup DESCRIPTION "This group is optional."

GROUP lmpNotificationGroup DESCRIPTION "このグループはオプションです。"

-- lmpNbrTable

- lmpNbrTable

OBJECT lmpNbrRowStatus

SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for notReady(3) and createAndWait(5) is not required."

構文RowStatus {活性は、（1）、notInServiceの（2）} WRITE-構文RowStatus {活性は、（1）、notInServiceの（2）、createAndGo（4）、破壊（6）} DESCRIPTION「準備中（3）とcreateAndWaitにサポート（5 ）必須ではありません。"

-- lmpControlChannelTable

- lmpControlChannelTable

OBJECT lmpCcRemoteAddressType SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "Only ipv4(1) and ipv6(2) address types need to be supported for non-point-to-point configurations."

OBJECT lmpCcRemoteAddressType SYNTAX INTEGER {不明（0）、IPv4の（1）、IPv6の（2）} DESCRIPTION "IPv4のみ（1）およびIPv6（2）アドレス・タイプは、非ポイントツーポイント構成のためにサポートされる必要があります。"

OBJECT lmpCcRemoteIpAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "The size of the IP address depends on the address type."

OBJECT lmpCcRemoteIpAddr構文InetAddress（SIZE（0 | 4 | 16））DESCRIPTION "IPアドレスのサイズは、アドレスの種類に依存します。"

OBJECT lmpCcRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for notReady(3) and createAndWait(5) is not required."

OBJECT lmpCcRowStatus構文RowStatus {アクティブ（1）、notInServiceの（2）} WRITE-構文RowStatus {アクティブ（1）、notInServiceの（2）、createAndGo（4）、（6）を破壊} NOTREADYの説明「サポート（3）とcreateAndWaitに（5）必要とされていません。」

OBJECT lmpCcOperStatus SYNTAX INTEGER { up(1), down(2) } DESCRIPTION "A value of configSnd(3), configRcv(4), active(5), or goingDown(6) need not be supported."

OBJECT lmpCcOperStatus SYNTAX INTEGER {アップ（1）、ダウン（2）} DESCRIPTION "configSndの値（3）、configRcv（4）、（5）活性、又はgoingDown（6）をサポートする必要はありません。"

-- lmpTeLinkTable

- lmpTeLinkTable

OBJECT lmpTeLinkOperStatus SYNTAX INTEGER { up(1), down(2), degraded(5) } DESCRIPTION "The testing(3) and init(4) state need not be supported."

OBJECT lmpTeLinkOperStatus SYNTAX INTEGER {アップ（1）、ダウン（2）、分解（5）} DESCRIPTION "試験（3）とinit（4）状態がサポートされる必要はありません。"

OBJECT lmpTeLinkRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for notReady(3) and createAndWait(5) is not required."

OBJECT lmpTeLinkRowStatus構文RowStatus {アクティブ（1）、notInServiceの（2）} WRITE-構文RowStatus {アクティブ（1）、notInServiceの（2）、createAndGo（4）、（6）を破壊} NOTREADYの説明「サポート（3）とcreateAndWaitに（5）必要とされていません。」

-- lmpDataLinkTable

- lmpDataLinkTable

OBJECT lmpDataLinkActiveOperStatus SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } DESCRIPTION "A value of testing(4) need not be supported." OBJECT lmpDataLinkPassiveOperStatus SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } DESCRIPTION "A value of psvTst(4) need not be supported."

OBJECT lmpDataLinkActiveOperStatus SYNTAX INTEGER {upAlloc（1）、upFree（2）、下（3）} DESCRIPTION "テストの値が（4）がサポートする必要はありません。" OBJECT lmpDataLinkPassiveOperStatus SYNTAX INTEGER {upAlloc（1）、upFree（2）、下（3）} DESCRIPTION "psvTstの値が（4）がサポートする必要はありません。"

OBJECT lmpDataLinkRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for notReady(3) and createAndWait(5) is not required."

OBJECT lmpDataLinkRowStatus構文RowStatus {アクティブ（1）、notInServiceの（2）} WRITE-構文RowStatus {アクティブ（1）、notInServiceの（2）、createAndGo（4）、（6）を破壊} NOTREADYの説明「サポート（3）とcreateAndWaitに（5）必要とされていません。」

   ::= { lmpCompliances 1 }

lmpModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the monitoring of the LMP MIB." MODULE -- this module

lmpModuleReadOnlyCompliance MODULE-COMPLIANCEステータス現在の説明「LMP MIBの監視をサポートするエージェントのための準拠宣言。」 MODULE - このモジュール

      -- The mandatory groups have to be implemented
      -- by all LMP-enabled devices.  However, they may all be supported
      -- as read-only objects in the case where manual
      -- configuration is not supported.

MANDATORY-GROUPS { lmpNodeGroup, lmpControlChannelGroup, lmpLinkPropertyCorrelationGroup, lmpPerfGroup, lmpTeLinkGroup, lmpDataLinkGroup }

MANDATORY-GROUPS {lmpNodeGroup、lmpControlChannelGroup、lmpLinkPropertyCorrelationGroup、lmpPerfGroup、lmpTeLinkGroup、lmpDataLinkGroup}

GROUP lmpCcIsInterfaceGroup

DESCRIPTION "This group is mandatory for devices that support control channels that are interfaces, in addition to lmpControlChannelGroup. The following constraint applies: lmpCcIsIf must at least be read-only, returning true(1)."

DESCRIPTION「このグループはlmpControlChannelGroupに加えて、インタフェースである制御チャネルをサポートするデバイスのために必須であり、以下の制約が適用されます。lmpCcIsIf少なくとも読み取り専用、trueを返す必要があります（1）。」

GROUP lmpLinkVerificationGroup DESCRIPTION "This group is mandatory for devices that support the link verification procedure."

GROUP lmpLinkVerificationGroup DESCRIPTION「このグループはリンク検証手続をサポートするデバイスのために必須です。」

GROUP lmpNotificationGroup DESCRIPTION "This group is optional."

GROUP lmpNotificationGroup DESCRIPTION "このグループはオプションです。"

-- Scalars

- スカラー

OBJECT lmpAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpAdminStatus MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpGlobalLinkVerificationInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpGlobalLinkVerificationInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloIntervalDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloIntervalDefault MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloIntervalDefaultMin MIN-ACCESS read-only DESCRIPTION "Write access is not required."

MIN-ACCESS lmpCcHelloIntervalDefaultMinオブジェクトは読み取り専用説明「書き込みアクセスが必要とされていません。」

OBJECT lmpCcHelloIntervalDefaultMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloIntervalDefaultMax MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloDeadIntervalDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloDeadIntervalDefault MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloDeadIntervalDefaultMin

OBJECTのlmpCcHelloDeadIntervalDefaultMin

MIN-ACCESS read-only DESCRIPTION "Write access is not required."

MIN-ACCESS読み取り専用説明「書き込みアクセスが必要とされていません。」

OBJECT lmpCcHelloDeadIntervalDefaultMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloDeadIntervalDefaultMax MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpNotificationMaxRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpNotificationMaxRate MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

-- lmpNbrTable

- lmpNbrTable

OBJECT lmpNbrRetransmitInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpNbrRetransmitInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpNbrRetryLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpNbrRetryLimit MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpNbrRetransmitDelta MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpNbrRetransmitDelta MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpNbrRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."

OBJECT lmpNbrRowStatus構文RowStatusは{アクティブ（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要とアクティブ（1）されていないサポートされる必要がある唯一の状態です。」

OBJECT lmpNbrStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpNbrStorageType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

-- lmpControlChannelTable

- lmpControlChannelTable

OBJECT lmpCcUnderlyingIfIndex MIN-ACCESS read-only DESCRIPTION

OBJECT lmpCcUnderlyingIfIndex MIN-ACCESS読み取り専用説明

"Write access is not required."

「書き込みアクセスが必要とされていません。」

OBJECT lmpCcIsIf MIN-ACCESS read-only DESCRIPTION "Write access is not required."

MIN-ACCESS lmpCcIsIfオブジェクトは読み取り専用説明「書き込みアクセスが必要とされていません。」

OBJECT lmpCcNbrNodeId MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECTは、MIN-ACCESS読み取り専用説明は "書く、アクセスは必要でない。" lmpCcNbrNodeId

OBJECT lmpCcRemoteAddressType SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Only ipv4(1) and ipv6(2) address types need to be supported for non-point-to-point configurations."

OBJECT lmpCcRemoteAddressType SYNTAX INTEGER {不明（0）、IPv4の（1）、IPv6の（2）} MIN-ACCESS読み取り専用説明「IPv4のみ（1）およびIPv6（2）アドレス・タイプは、非点までのためにサポートされる必要があります - ポイント構成。」

OBJECT lmpCcRemoteIpAddr SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "The size of the IP address depends on the address type."

OBJECT lmpCcRemoteIpAddr構文InetAddress（SIZE（0 | 4 | 16））MIN-ACCESS読み取り専用説明 "IPアドレスのサイズは、アドレスの種類に依存します。"

OBJECT lmpCcSetupRole MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcSetupRole MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcAuthentication MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcAuthentication MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloIntervalMin MIN-ACCESS read-only DESCRIPTION "Write access is not required."

MIN-ACCESS lmpCcHelloIntervalMinオブジェクトは読み取り専用説明「書き込みアクセスが必要とされていません。」

OBJECT lmpCcHelloIntervalMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloIntervalMax MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcHelloDeadIntervalMin MIN-ACCESS read-only DESCRIPTION

MIN-ACCESS読み取り専用説明lmpCcHelloDeadIntervalMin OBJECT

"Write access is not required."

「書き込みアクセスが必要とされていません。」

OBJECT lmpCcHelloDeadIntervalMax MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcHelloDeadIntervalMax MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpCcRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."

OBJECT lmpCcRowStatus構文RowStatusは{アクティブ（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要とアクティブ（1）されていないサポートされる必要がある唯一の状態です。」

OBJECT lmpCcOperStatus SYNTAX INTEGER { up(1), down(2) } DESCRIPTION "A value of configSnd(3), configRcv(4), active(5), or goingDown(6) need not be supported."

OBJECT lmpCcStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpCcStorageType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

-- lmpLinkVerificationTable

- lmpLinkVerificationTable

OBJECT lmpLinkVerifyInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpLinkVerifyInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpLinkVerifyDeadInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpLinkVerifyDeadInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpLinkVerifyAllLinks MIN-ACCESS read-only DESCRIPTION "Write access is not required."

MIN-ACCESS読み取り専用説明がオブジェクトlmpLinkVerifyAllLinks「書き込みアクセスが必要とされていません。」

-- lmpTeLinkTable

- lmpTeLinkTable

OBJECT lmpTeLinkNbrRemoteNodeId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification

OBJECTは、リンク検証場合MIN-ACCESS読み取り専用説明「書き込みアクセスが必要とされていないlmpTeLinkNbrRemoteNodeId

procedure is enabled."

手順が有効になっています。」

OBJECT lmpTeLinkVerification MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpTeLinkVerification MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpTeLinkFaultManagement MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpTeLinkFaultManagement MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpTeLinkDwdm MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpTeLinkDwdm MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpTeLinkOperStatus SYNTAX INTEGER { up(1), down(2), degraded(5) } DESCRIPTION "The testing(3) and init(4) state need not be supported."

OBJECT lmpTeLinkOperStatus SYNTAX INTEGER {アップ（1）、ダウン（2）、分解（5）} DESCRIPTION "試験（3）とinit（4）状態がサポートされる必要はありません。"

OBJECT lmpTeLinkRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."

OBJECT lmpTeLinkRowStatus構文RowStatusは{アクティブ（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要とアクティブ（1）されていないサポートされる必要がある唯一の状態です。」

OBJECT lmpTeLinkStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpTeLinkStorageType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

-- lmpTeLinkVerificationTable

- lmpTeLinkVerificationTable

OBJECT lmpLinkVerifyTransmissionRate MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpLinkVerifyTransmissionRate MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpLinkVerifyWavelength MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpLinkVerifyWavelength MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpLinkVerifyRowStatus SYNTAX RowStatus { active(1) }

OBJECT lmpLinkVerifyRowStatus構文RowStatus {アクティブ（1）}

MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."

MIN-ACCESS読み取り専用説明「書き込みアクセスが必要とされていないし、アクティブは、（1）サポートされる必要がある唯一のステータスです。」

OBJECT lmpLinkVerifyStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpLinkVerifyStorageType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

-- lmpDataLinkTable

- lmpDataLinkTable

OBJECT lmpDataLinkAddressType SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only DESCRIPTION "Only ipv4(1) and ipv6(2) address types need to be supported for numbered links. For unnumbered links, the unknown(0) address type needs to be supported."

OBJECT lmpDataLinkAddressType SYNTAX INTEGER {不明（0）、IPv4の（1）、IPv6の（2）} MIN-ACCESS読み取り専用説明「IPv4のみ（1）およびIPv6（2）アドレス・タイプは番号付きのリンクのためにサポートされる必要がある。無数のためリンクは、不明（0）アドレスタイプがサポートされる必要があります。」

OBJECT lmpDataLinkIpAddr SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "The size of the data-bearing link IP address depends on the type of data-bearing link. Data-bearing link IP address size is zero if the link is unnumbered, four if the link IP address is IPv4, and sixteen if the link IP address is IPv6."

OBJECT lmpDataLinkIpAddr構文InetAddress（SIZE（0 | 4 | 16））MIN-ACCESS読み取り専用説明「データ・ベアリングリンクIPアドレスのサイズは、データ・ベアリング・リンクのタイプに依存データ・ベアリング・リンクIPアドレスのサイズがあります。ゼロリンクIPアドレスがIPv6の場合は、リンクのIPアドレスがIPv4で、16あればリンクは4、番号なしの場合。」

OBJECT lmpDataLinkRemoteIpAddress SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled."

OBJECT lmpDataLinkRemoteIpAddress構文InetAddress（SIZE（0 | 4 | 16））MIN-ACCESS読み取り専用説明 "リンク検証手続が有効になっている場合、アクセスを書く必要はありません。"

OBJECT lmpDataLinkRemoteIfId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled."

OBJECTは、MIN-ACCESS読み取り専用説明「リンク検証手続が有効になっている場合、アクセスを書くが必要とされていません。」lmpDataLinkRemoteIfId

OBJECT lmpDataLinkEncodingType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpDataLinkEncodingType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

OBJECT lmpDataLinkActiveOperStatus SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } DESCRIPTION "A value of testing(4) need not be supported."

OBJECT lmpDataLinkActiveOperStatus SYNTAX INTEGER {upAlloc（1）、upFree（2）、下（3）} DESCRIPTION "テストの値が（4）がサポートする必要はありません。"

OBJECT lmpDataLinkPassiveOperStatus SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } DESCRIPTION "A value of psvTst(4) need not be supported."

OBJECT lmpDataLinkPassiveOperStatus SYNTAX INTEGER {upAlloc（1）、upFree（2）、下（3）} DESCRIPTION "psvTstの値が（4）がサポートする必要はありません。"

OBJECT lmpDataLinkRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."

OBJECT lmpDataLinkRowStatus構文RowStatusは{アクティブ（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要とアクティブ（1）されていないサポートされる必要がある唯一の状態です。」

OBJECT lmpDataLinkStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."

OBJECT lmpDataLinkStorageType MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"

   ::= { lmpCompliances 2 }

-- Units of conformance

- 適合の単位

lmpNodeGroup OBJECT-GROUP
   OBJECTS { lmpAdminStatus,
             lmpOperStatus,
             lmpNbrAdminStatus,
             lmpNbrOperStatus,
             lmpNbrRowStatus,
             lmpNbrStorageType,
             lmpUnprotectedNotificationsEnabled,
             lmpNotificationMaxRate
           }
   STATUS  current
   DESCRIPTION
          "Collection of objects that represent LMP node
           configuration."
   ::= { lmpGroups 1 }

lmpControlChannelGroup OBJECT-GROUP
   OBJECTS {
             lmpNbrRetransmitInterval,
             lmpNbrRetryLimit,
             lmpNbrRetransmitDelta,
             lmpNbrAdminStatus, lmpNbrOperStatus,
             lmpNbrRowStatus,
             lmpNbrStorageType,
             lmpCcHelloIntervalDefault,
             lmpCcHelloIntervalDefaultMin,
             lmpCcHelloIntervalDefaultMax,
             lmpCcHelloDeadIntervalDefault,
             lmpCcHelloDeadIntervalDefaultMin,
             lmpCcHelloDeadIntervalDefaultMax,
             lmpCcNbrNodeId,
             lmpCcRemoteId,
             lmpCcRemoteAddressType,
             lmpCcRemoteIpAddr,
             lmpCcSetupRole,
             lmpCcAuthentication,
             lmpCcHelloInterval,
             lmpCcHelloIntervalMin,
             lmpCcHelloIntervalMax,
             lmpCcHelloIntervalNegotiated,
             lmpCcHelloDeadInterval,
             lmpCcHelloDeadIntervalMin,
             lmpCcHelloDeadIntervalMax,
             lmpCcHelloDeadIntervalNegotiated,
             lmpCcOperStatus,
             lmpCcRowStatus,
             lmpCcStorageType,
             lmpCcUpDownNotificationsEnabled
           }
   STATUS  current
   DESCRIPTION
          "Objects that can be used to configure LMP interface."
   ::= { lmpGroups 2 }

lmpCcIsInterfaceGroup OBJECT-GROUP
   OBJECTS { lmpCcIsIf }
   STATUS  current
   DESCRIPTION
          "Objects that can be used to configure control channels
           that are interfaces."
   ::= { lmpGroups 3 }

lmpCcIsNotInterfaceGroup OBJECT-GROUP OBJECTS { lmpCcUnderlyingIfIndex, lmpCcIsIf, lmpCcLastChange, lmpCcAdminStatus } STATUS current

lmpCcIsNotInterfaceGroupオブジェクト・グループオブジェクト{lmpCcUnderlyingIfIndex、lmpCcIsIf、lmpCcLastChange、lmpCcAdminStatus} STATUS電流

   DESCRIPTION
          "Objects that can be used to configure control channels
           that are not interfaces."
   ::= { lmpGroups 4 }

lmpLinkPropertyCorrelationGroup OBJECT-GROUP
   OBJECTS { lmpLinkPropertyNotificationsEnabled }
   STATUS  current
   DESCRIPTION
          "Collection of objects used to configure the link
           property correlation procedure."
   ::= { lmpGroups 5 }

lmpLinkVerificationGroup OBJECT-GROUP
   OBJECTS { lmpGlobalLinkVerificationInterval,
             lmpLinkVerifyInterval,
             lmpLinkVerifyDeadInterval,
             lmpLinkVerifyTransportMechanism,
             lmpLinkVerifyAllLinks,
             lmpLinkVerifyTransmissionRate,
             lmpLinkVerifyWavelength,
             lmpLinkVerifyRowStatus,
             lmpLinkVerifyStorageType,
             lmpDataLinkNotificationsEnabled
           }
   STATUS  current
   DESCRIPTION
          "Collection of objects that represent the link
           verification procedure configuration."
   ::= { lmpGroups 6 }

lmpPerfGroup OBJECT-GROUP
   OBJECTS { lmpCcInOctets,
             lmpCcInDiscards,
             lmpCcInErrors,
             lmpCcOutOctets,
             lmpCcOutDiscards,
             lmpCcOutErrors,
             lmpCcConfigReceived,
             lmpCcConfigSent,
             lmpCcConfigRetransmit,
             lmpCcConfigAckReceived,
             lmpCcConfigAckSent,
             lmpCcConfigNackSent,
             lmpCcConfigNackReceived,
             lmpCcHelloReceived,
             lmpCcHelloSent,
             lmpCcBeginVerifyReceived, lmpCcBeginVerifySent,
             lmpCcBeginVerifyRetransmit,
             lmpCcBeginVerifyAckReceived,
             lmpCcBeginVerifyAckSent,
             lmpCcBeginVerifyNackReceived,
             lmpCcBeginVerifyNackSent,
             lmpCcEndVerifyReceived,
             lmpCcEndVerifySent,
             lmpCcEndVerifyRetransmit,
             lmpCcEndVerifyAckReceived,
             lmpCcEndVerifyAckSent,
             lmpCcTestStatusSuccessReceived,
             lmpCcTestStatusSuccessSent,
             lmpCcTestStatusSuccessRetransmit,
             lmpCcTestStatusFailureReceived,
             lmpCcTestStatusFailureSent,
             lmpCcTestStatusFailureRetransmit,
             lmpCcTestStatusAckReceived,
             lmpCcTestStatusAckSent,
             lmpCcLinkSummaryReceived,
             lmpCcLinkSummarySent,
             lmpCcLinkSummaryRetransmit,
             lmpCcLinkSummaryAckReceived,
             lmpCcLinkSummaryAckSent,
             lmpCcLinkSummaryNackReceived,
             lmpCcLinkSummaryNackSent,
             lmpCcChannelStatusReceived,
             lmpCcChannelStatusSent,
             lmpCcChannelStatusRetransmit,
             lmpCcChannelStatusAckReceived,
             lmpCcChannelStatusAckSent,
             lmpCcChannelStatusReqReceived,
             lmpCcChannelStatusReqSent,
             lmpCcChannelStatusReqRetransmit,
             lmpCcChannelStatusRspReceived,
             lmpCcChannelStatusRspSent,
             lmpCcCounterDiscontinuityTime,
             lmpTeInOctets,
             lmpTeOutOctets,
             lmpTeBeginVerifyReceived,
             lmpTeBeginVerifySent,
             lmpTeBeginVerifyRetransmit,
             lmpTeBeginVerifyAckReceived,
             lmpTeBeginVerifyAckSent,
             lmpTeBeginVerifyNackReceived,
             lmpTeBeginVerifyNackSent,
             lmpTeEndVerifyReceived,
             lmpTeEndVerifySent, lmpTeEndVerifyRetransmit,
             lmpTeEndVerifyAckReceived,
             lmpTeEndVerifyAckSent,
             lmpTeTestStatusSuccessReceived,
             lmpTeTestStatusSuccessSent,
             lmpTeTestStatusSuccessRetransmit,
             lmpTeTestStatusFailureReceived,
             lmpTeTestStatusFailureSent,
             lmpTeTestStatusFailureRetransmit,
             lmpTeTestStatusAckReceived,
             lmpTeTestStatusAckSent,
             lmpTeLinkSummaryReceived,
             lmpTeLinkSummarySent,
             lmpTeLinkSummaryRetransmit,
             lmpTeLinkSummaryAckReceived,
             lmpTeLinkSummaryAckSent,
             lmpTeLinkSummaryNackReceived,
             lmpTeLinkSummaryNackSent,
             lmpTeChannelStatusReceived,
             lmpTeChannelStatusSent,
             lmpTeChannelStatusRetransmit,
             lmpTeChannelStatusAckReceived,
             lmpTeChannelStatusAckSent,
             lmpTeChannelStatusReqReceived,
             lmpTeChannelStatusReqSent,
             lmpTeChannelStatusReqRetransmit,
             lmpTeChannelStatusRspSent,
             lmpTeChannelStatusRspReceived,
             lmpTeCounterDiscontinuityTime,
             lmpDataLinkTestReceived,
             lmpDataLinkTestSent,
             lmpDataLinkActiveTestSuccess,
             lmpDataLinkActiveTestFailure,
             lmpDataLinkPassiveTestSuccess,
             lmpDataLinkPassiveTestFailure,
             lmpDataLinkDiscontinuityTime
           }
   STATUS  current
   DESCRIPTION
          "Collection of objects used to provide performance
           information about LMP interfaces and data-bearing links."
   ::= { lmpGroups 7 }

lmpTeLinkGroup OBJECT-GROUP
   OBJECTS { lmpTeLinkNbrRemoteNodeId,
             lmpTeLinkVerification,
             lmpTeLinkFaultManagement,
             lmpTeLinkDwdm, lmpTeLinkOperStatus,
             lmpTeLinkRowStatus,
             lmpTeLinkStorageType,
             lmpTeLinkNotificationsEnabled
           }
   STATUS  current
   DESCRIPTION
          "Objects that can be used to configure TE links."
   ::= { lmpGroups 8 }

lmpDataLinkGroup OBJECT-GROUP
   OBJECTS { lmpDataLinkType,
             lmpDataLinkAddressType,
             lmpDataLinkIpAddr,
             lmpDataLinkRemoteIpAddress,
             lmpDataLinkRemoteIfId,
             lmpDataLinkEncodingType,
             lmpDataLinkActiveOperStatus,
             lmpDataLinkPassiveOperStatus,
             lmpDataLinkRowStatus,
             lmpDataLinkStorageType
           }
   STATUS  current
   DESCRIPTION
          "Collection of objects that represent data-bearing link
           configuration."
   ::= { lmpGroups 9 }

lmpNotificationGroup NOTIFICATION-GROUP
   NOTIFICATIONS { lmpTeLinkPropertyMismatch,
                   lmpDataLinkPropertyMismatch,
                   lmpUnprotected,
                   lmpControlChannelUp,
                   lmpControlChannelDown,
                   lmpTeLinkDegraded,
                   lmpTeLinkNotDegraded,
                   lmpDataLinkVerificationFailure }
   STATUS  current
   DESCRIPTION
          "Set of notifications defined in this module."
   ::= { lmpGroups 10 }

-- End of LMP-MIB END

- LMP-MIBのENDの終了

10. Security Considerations

10.セキュリティの考慮事項

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:

読み書きおよび/またはリード作成のMAX-ACCESS句でこのMIBモジュールで定義された管理オブジェクトの数があります。そのようなオブジェクトは、いくつかのネットワーク環境に敏感又は脆弱と考えることができます。適切な保護のない非安全な環境におけるSET操作のサポートはネットワーク操作のときにマイナスの影響を与える可能性があります。これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です：

- Unauthorized changes to the lmpNbrTable, lmpControlChannelTable, lmpTeLinkTable, and lmpDataLinkTable may disrupt allocation of resources in the network.

- lmpNbrTable、lmpControlChannelTable、lmpTeLinkTable、およびlmpDataLinkTableへの不正な変更は、ネットワーク内のリソースの割り当てを中断される場合があります。

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持つオブジェクト）は、いくつかのネットワーク環境に敏感又は脆弱と考えることができます。 GETおよび/またはこれらのオブジェクトへのアクセスを通知し、おそらくSNMPを通してネットワークの上にそれらを送信する場合でも、これらのオブジェクトの値を暗号化するためにも、制御することが重要です。これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です：

- The lmpNbrTable exposes the network provider's node IP addresses.

- lmpNbrTableは、ネットワークプロバイダのノードのIPアドレスを公開します。

- lmpControlChannelTable exposes the network provider's control network.

- lmpControlChannelTableは、ネットワークプロバイダの制御ネットワークを公開します。

- lmpDataLinkTable exposes the network provider's data network.

- lmpDataLinkTableは、ネットワークプロバイダのデータネットワークを公開します。

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を使用することにより、例えば）安全であっても、その後も、安全なネットワーク上で/ SETにアクセスし、GETだれに許容されているかのように何の制御（読み取り/変更/作成/削除）この内のオブジェクトが存在しません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フレームワークで提供するようにセキュリティ機能を考えることが推奨される（認証とプライバシーのために）SNMPv3の暗号化メカニズムの完全なサポートを含む、（[RFC3410]セクション8を参照）。

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実体が適切にのみプリンシパル（ユーザ）にオブジェクトへのアクセスを提供するように設定されていることを確認するために、顧客/オペレータ責任実際にGETまたはSET（変化への正当な権利を有することです/）/削除、それらを作成します。

11. Contributors

11.協力者

Sudheer Dharanikota

Sudhir Dharanikota

EMail: sudheer@ieee.org

メールアドレス：sudheer@ieee.org

12. Acknowledgements

12.謝辞

The general structure of this document has been modeled around the MPLS Label Switching Router (LSR) MIB [RFC3813].

このドキュメントの一般的な構造は、ルータ（LSR）MIB [RFC3813]をスイッチングMPLSラベルを中心にモデル化されています。

The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and George Wang.

著者はドミトリーRyumkin、Baktha Muralidharanとジョージ王に感謝したいです。

Thanks to Tom Petch for spotting inconsistencies in RFC 4327 and to Bert Wijnen for document review.

書類審査のためのRFC 4327にし、バートWijnenに不整合をスポッティングためのトム・ペッチに感謝します。

13. IANA Considerations

13. IANAの考慮事項

No new IANA actions are requested in this document. All IANA actions from RFC 4327 still hold and are reproduced here for information.

新しいIANAのアクションは、この文書で要求されていません。 RFC 4327からのすべてのIANAのアクションはまだ保持し、情報のためにここに再現されています。

Note that new assignments can only be made via a Standards Action as specified in [RFC2434].

[RFC2434]で指定されたように、新しい割り当てが唯一の標準化アクションを経由して行うことができることに注意してください。

13.1. IANA Considerations for LMP ifType

13.1. LMPのifTypeのためのIANAの考慮事項

The IANA has assigned 227 ifType for LMP interfaces.

IANAは、LMPインターフェイスの227のifTypeが割り当てられています。

13.2. IANA Considerations for LMP-MIB

13.2. LMP-MIBのためのIANAの考慮事項

The IANA has assigned { transmission 227 } to the LMP-MIB module specified in this document.

IANAは、この文書で指定されたLMP-MIBモジュールに送信{227}を割り当てました。

14. Changes from to

へ〜14の変更点

The following changes have been made relative to RFC 4327.

次の変更は、RFC 4327に比べて行われています。

a. Show that this document obsoletes RFC 4327. b. Indicate in Abstract that this document provides minor corrections to RFC 4327. c. Correct use of TruthValue settings such that True is always 1, and False is always 2. d. Update to acknowledgements section. e. Note in IANA section to show no further action required. f. Remove identification of RFC 4327 and request RFC Editor to insert new RFC number. g. Update timestamps.

A。この文書はRFC 4327. Bを廃止することを示しています。この文書は4327. CをRFCするマイナーな修正を提供することを要約して示しています。真は常に1であるように、とFalseのTruthValueの設定を正しく使用するには、常に2 dとします。謝辞セクションに更新します。電子。必要な更なる動作を示さないためにIANAのセクションに注意してください。 F。 RFC 4327の識別を取り外し、新しいRFC番号を挿入するためにRFC Editorを要求します。グラム。タイムスタンプを更新します。

h. Update author information. i. Added punctuation to REFERENCE clauses. j. Update Revision History clause. k. Add this section. l. Remove square braces from references to external documents from within the MIB module itself. m. Minor editorial corrections to text and DESCRIPTIONS clauses.

時間。著者情報を更新します。私。 REFERENCE句に句読点を追加しました。 J。改訂履歴句を更新します。 K。このセクションを追加します。リットル。 MIBモジュール自体の内部から外部ドキュメントへの参照から角括弧を削除します。メートル。テキストと説明句にマイナーな編集上の訂正。

15. References

15.参考文献

15.1. Normative References

15.1. 引用規格

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2119]ブラドナーの、S.、 "要件レベルを示すためにRFCsにおける使用のためのキーワード"、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月。

[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[RFC2578] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "経営情報バージョン2（SMIv2）の構造"、STD 58、RFC 2578 、1999年4月。

[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.

[RFC2579] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "SMIv2のためのテキストの表記法"、STD 58、RFC 2579、1999年4月。

[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.

[RFC2580] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "SMIv2のための適合性宣言"、STD 58、RFC 2580、1999年4月。

[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.

[RFC2863] McCloghrie、K.およびF. Kastenholzと、 "インターフェイスグループMIB"、RFC 2863、2000年6月。

[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC 2914, September 2000.

[RFC2914]フロイド、S.、 "輻輳制御の原理"、BCP 41、RFC 2914、2000年9月。

[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003.

[RFC3471]バーガー、L.、 "一般化されたマルチプロトコルラベルスイッチング（GMPLS）機能説明シグナリング"、RFC 3471、2003年1月。

[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.

[RFC4001]ダニエル、M.、ハーバーマン、B.、Routhier、S.、およびJ. Schoenwaelder、 "インターネットネットワークアドレスのためのテキストの表記法"、RFC 4001、2005年2月。

[RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204, October 2005.

[RFC4204]ラング、J.、 "リンク管理プロトコル（LMP）"、RFC 4204、2005年10月。

[RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages", RFC 4207, October 2005.

[RFC4207]ラング、J.とD. Papadimitriou、 "同期光ネットワーク（SONET）リンク管理プロトコル（LMP）テストメッセージ用/同期デジタル階層（SDH）エンコーディング"、RFC 4207、2005年10月。

[RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems", RFC 4209, October 2005.

[RFC4209] Fredette、A.と、RFC 4209、2005年10月 "高密度波長分割多重（DWDM）光回線システムのリンク管理プロトコル（LMP）" J.ラング、。

[RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering Link Management Information Base", RFC 4220, November 2005.

[RFC4220] Dubuc、M.、ナドー、T.、およびJ.ラング、 "トラフィックエンジニアリングリンク管理情報ベース"、RFC 4220、2005年11月。

15.2. Informative References

15.2. 参考文献

[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.

[RFC3410]ケース、J.、マンディ、R.、パーテイン、D.、およびB.スチュワート、 "インターネット標準の管理フレームワークのための序論と適用性声明"、RFC 3410、2002年12月。

[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004.

[RFC3813]スリニバサン、C.、Viswanathanの、A.、およびT.ナドーは、 "マルチプロトコルラベルスイッチング（MPLS）ラベルスイッチングルータ（LSR）管理情報ベース（MIB）"、RFC 3813、2004年6月。

Authors' Addresses

著者のアドレス

Martin Dubuc

マーティンDubuc

EMail: dubuc.consulting@sympatico.ca

メールアドレス：dubuc.consulting@sympatico.ca

Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719

トーマスD.ナドー、シスコシステムズ、株式会社1414年マサチューセッツアベニュー。ボックスボロー、MA 01719

EMail: tnadeau@cisco.com

メールアドレス：tnadeau@cisco.com

Jonathan P. Lang Sonos, Inc. 223 E. De La Guerra St. Santa Barbara, CA 93101

ジョナサンP.ラングSonosの、株式会社223 E.デ・ラ・ゲラセントサンタバーバラ、CA 93101

EMail: jplang@ieee.org

メールアドレス：jplang@ieee.org

Evan McGinnis Hammerhead Systems 640 Clyde Court Mountain View, CA 94043

エヴァンマクギニスハンマーシステム640クライド法廷マウンテンビュー、CA 94043

EMail: emcginnis@hammerheadsystems.com

メールアドレス：emcginnis@hammerheadsystems.com

Adrian Farrel Old Dog Consulting

エードリアンファレル古い犬のコンサルティング

EMail: adrian@olddog.co.uk

メールアドレス：adrian@olddog.co.uk

Full Copyright Statement

完全な著作権声明

著作権（C）インターネット協会（2006）。

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

この文書では、BCP 78に含まれる権利と許可と制限の適用を受けており、その中の記載を除いて、作者は彼らのすべての権利を保有します。

This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY 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.

この文書とここに含まれている情報は、基礎とCONTRIBUTOR「そのまま」、ORGANIZATION HE / SHEが表すまたはインターネットソサエティおよびインターネット・エンジニアリング・タスク・フォース放棄すべての保証、明示または、（もしあれば）後援ISに設けられています。黙示、情報の利用は、特定の目的に対する権利または商品性または適合性の黙示の保証を侵害しない任意の保証含むがこれらに限定されません。

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.

IPRの開示のコピーが利用できるようにIETF事務局とライセンスの保証に行われた、または本仕様の実装者または利用者がそのような所有権の使用のための一般的なライセンスまたは許可を取得するために作られた試みの結果を得ることができますhttp://www.ietf.org/iprのIETFのオンライン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-ipr@ietf.orgのIETFに情報を記述してください。

Acknowledgement

謝辞

Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).

RFCエディタ機能のための資金は、IETF管理サポート活動（IASA）によって提供されます。