[要約] RFC 5833は、無線アクセスポイントの制御とプロビジョニングを行うためのCAPWAPプロトコルの基本MIBに関するものです。このRFCの目的は、CAPWAPプロトコルの実装と管理を支援するためのMIBオブジェクトを定義することです。
Internet Engineering Task Force (IETF) Y. Shi, Ed.
Request for Comments: 5833 Hangzhou H3C Tech. Co., Ltd.
Category: Informational D. Perkins, Ed.
ISSN: 2070-1721 C. Elliott, Ed.
Y. Zhang, Ed. Fortinet, Inc. May 2010
Y.チャン、編Fortinet、Inc。2010年5月
Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB
ワイヤレスアクセスポイント（CAPWAP）プロトコルベースMIBの制御とプロビジョニング
Abstract
概要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it describes the managed objects for modeling the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB module is presented as a basis for future work on the SNMP management of the CAPWAP protocol.
このメモは、ネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、ワイヤレスアクセスポイント（CAPWAP）プロトコルの制御とプロビジョニングをモデル化するための管理されたオブジェクトを説明します。このMIBモジュールは、CAPWAPプロトコルのSNMP管理に関する将来の作業の基礎として提示されます。
Status of This Memo
本文書の位置付け
This document is not an Internet Standards Track specification; it is published for informational purposes.
このドキュメントは、インターネット標準の追跡仕様ではありません。情報目的で公開されています。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
このドキュメントは、インターネットエンジニアリングタスクフォース（IETF）の製品です。IETFコミュニティのコンセンサスを表しています。公開レビューを受けており、インターネットエンジニアリングステアリンググループ（IESG）からの出版が承認されています。IESGによって承認されたすべてのドキュメントが、あらゆるレベルのインターネット標準の候補者ではありません。RFC 5741のセクション2を参照してください。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5833.
このドキュメントの現在のステータス、任意のERRATA、およびそのフィードバックを提供する方法に関する情報は、http：//www.rfc-editor.org/info/rfc5833で取得できます。
Copyright Notice
著作権表示
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
Copyright（c）2010 IETF Trustおよび文書著者として特定された人。全著作権所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
このドキュメントは、BCP 78およびIETFドキュメント（http://trustee.ietf.org/license-info）に関連するIETF Trustの法的規定の対象となります。この文書に関するあなたの権利と制限を説明するので、これらの文書を注意深く確認してください。このドキュメントから抽出されたコードコンポーネントには、セクション4.Eで説明されている法的規定のセクション4.Eで説明されており、単純化されたBSDライセンスで説明されているように保証なしで提供される簡略化されたBSDライセンステキストを含める必要があります。
Table of Contents
目次
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5
5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5
5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6
5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6
5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7
5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 8
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9
7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 10
7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 69
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70
11.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 70
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 70
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 70
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 71
14.1. Normative References . . . . . . . . . . . . . . . . . . . 71
14.2. Informative References . . . . . . . . . . . . . . . . . . 72
The CAPWAP Protocol [RFC5415] defines a standard, interoperable protocol, which enables an Access Controller (AC) to manage a collection of Wireless Termination Points (WTPs).
CAPWAPプロトコル[RFC5415]は、標準の相互運用可能なプロトコルを定義します。これにより、アクセスコントローラー（AC）がワイヤレス終端ポイント（WTPS）のコレクションを管理できます。
This document defines a MIB module that can be used to manage the CAPWAP implementations. This MIB module covers both configuration and WTP status-monitoring aspects of CAPWAP, and provides a way to reuse MIB modules for any wireless technology. It presented as a basis for future work on a SNMP management of the CAPWAP protocol.
このドキュメントでは、CAPWAP実装の管理に使用できるMIBモジュールを定義します。このMIBモジュールは、CAPWAPの構成とWTPステータスモニタリングの両方の側面をカバーし、ワイヤレステクノロジーのMIBモジュールを再利用する方法を提供します。CAPWAPプロトコルのSNMP管理に関する将来の作業の基礎として提示されました。
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モジュールを指定します。
This document uses terminology from the CAPWAP Protocol specification [RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118].
このドキュメントでは、CAPWAPプロトコル仕様[RFC5415]の用語とCAPWAP [RFC4118]のアーキテクチャ分類法を使用しています。
Access Controller (AC): The network entity that provides WTP access to the network infrastructure in the data plane, control plane, management plane, or a combination therein.
Access Controller（AC）：データプレーン、コントロールプレーン、管理プレーン、またはその組み合わせのネットワークインフラストラクチャへのWTPアクセスを提供するネットワークエンティティ。
Wireless Termination Point (WTP): The physical or network entity that contains an radio frequency (RF) antenna and wireless physical layer (PHY) to transmit and receive station traffic for wireless access networks.
ワイヤレス終端ポイント（WTP）：無線周波数（RF）アンテナとワイヤレス物理層（PHY）を含む物理またはネットワークエンティティは、ワイヤレスアクセスネットワークのステーショントラフィックを送信および受信します。
Control And Provisioning of Wireless Access Points (CAPWAP): It is a generic protocol defining AC and WTP control and data plane communication via a CAPWAP protocol transport mechanism. CAPWAP control messages, and optionally CAPWAP data messages, are secured using Datagram Transport Layer Security (DTLS) [RFC4347].
ワイヤレスアクセスポイントの制御とプロビジョニング（CAPWAP）：CAPWAPプロトコル輸送メカニズムを介したACおよびWTP制御およびデータプレーン通信を定義する汎用プロトコルです。CapWap Controlメッセージ、およびオプションでCapWapデータメッセージは、データグラムトランスポートレイヤーセキュリティ（DTLS）[RFC4347]を使用して保護されます。
CAPWAP Control Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC control port, WTP control port, and the transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control packets are sent and received.
CAPWAP制御チャネル：AC IPアドレス、WTP IPアドレス、ACコントロールポート、WTP制御ポート、およびCAPWAP制御パケットが送信および受信される輸送層プロトコル（UDPまたはUDP-Lite）によって定義された双方向フロー。
CAPWAP Data Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC data port, WTP data port, and the transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data packets are sent and received.
CAPWAPデータチャネル：AC IPアドレス、WTP IPアドレス、ACデータポート、WTPデータポート、およびCAPWAPデータパケットが送信および受信される輸送層プロトコル（UDPまたはUDP-Lite）によって定義された双方向フロー。
Station (STA): A device that contains an interface to a wireless medium (WM).
ステーション（STA）：ワイヤレスメディア（WM）へのインターフェイスを含むデバイス。
Split and Local MAC: The CAPWAP protocol supports two modes of operation: Split and Local MAC (medium access control). In Split MAC mode, all Layer 2 wireless data and management frames are encapsulated via the CAPWAP protocol and exchanged between the AC and the WTPs. The Local MAC mode allows the data frames to be either locally bridged or tunneled as 802.3 frames.
分割およびローカルMAC：CapWapプロトコルは、SplitとLocal Mac（中程度のアクセス制御）の2つの動作モードをサポートしています。スプリットMACモードでは、すべてのレイヤー2ワイヤレスデータと管理フレームがCAPWAPプロトコルを介してカプセル化され、ACとWTPSの間で交換されます。ローカルMACモードを使用すると、データフレームを802.3フレームとして局所的にブリッジまたはトンネル化できます。
Wireless Binding: The CAPWAP protocol is independent of a specific WTP radio technology, as well its associated wireless link-layer protocol. Elements of the CAPWAP protocol are designed to accommodate the specific needs of each wireless technology in a standard way. Implementation of the CAPWAP protocol for a particular wireless technology MUST define a binding protocol for it, e.g., the binding for IEEE 802.11, provided in [RFC5416].
ワイヤレスバインディング：CAPWAPプロトコルは、特定のWTP無線テクノロジーと関連するワイヤレスリンク層プロトコルとは無関係です。CAPWAPプロトコルの要素は、各ワイヤレステクノロジーの特定のニーズに標準的な方法で対応するように設計されています。特定のワイヤレステクノロジー用のCAPWAPプロトコルの実装は、[RFC5416]で提供されるIEEE 802.11のバインディングなどの結合プロトコルを定義する必要があります。
Autonomous Wireless Local Area Network (WLAN) Architecture: It is the traditional autonomous WLAN architecture, in which each WTP is a single physical device that implements all the wireless services.
自律ワイヤレスローカルエリアネットワーク（WLAN）アーキテクチャ：それは従来の自律WLANアーキテクチャであり、各WTPはすべてのワイヤレスサービスを実装する単一の物理デバイスです。
Centralized WLAN Architecture: It is an emerging hierarchical architecture utilizing one or more centralized controllers for managing a large number of WTP devices. It can be said that the full wireless functions are implemented across multiple physical network devices, namely, the WTPs and ACs.
集中WLANアーキテクチャ：多数のWTPデバイスを管理するために1つ以上の集中コントローラーを利用した新興の階層アーキテクチャです。完全なワイヤレス関数は、複数の物理ネットワークデバイス、つまりWTPSとACSにわたって実装されていると言えます。
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]で説明されているように解釈されます。
The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to:
CAPWAPプロトコルMIBモジュール（CAPWAP-Base-MIB）は、次のように設計されています。
- Support centralized management and monitoring of WTPs from the AC in combination with the CAPWAP protocol;
- CAPWAPプロトコルと組み合わせて、ACからのWTPの集中管理と監視をサポートします。
- Allow operators to make configurations for WTPs before and after they connect to the AC;
- オペレーターがACに接続する前後にWTPSの構成を作成できるようにします。
- Support querying of CAPWAP protocol parameters;
- CAPWAPプロトコルパラメーターのクエリのサポート。
- Support displaying of WTPs' current states and configurations;
- WTPSの現在の状態と構成の表示をサポートします。
- Provide basic property information about the AC, WTPs, radios, and stations, and their relationships;
- AC、WTPS、ラジオ、ステーション、およびその関係に関する基本的なプロパティ情報を提供します。
- Provide counters for events on WTPs and radios such as reboot and hardware failure;
- 再起動やハードウェア障害などのWTPSおよびラジオに関するイベントのカウンターを提供します。
- Provide various notifications such as channel up and join failure.
- Channel Upと結合障害などのさまざまな通知を提供します。
Other Standards Development Organizations (SDOs), such as IEEE, have already defined MIB modules for a specific wireless technology, e.g., IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are called wireless binding MIB modules.
IEEEなどのその他の標準開発組織（SDO）は、特定のワイヤレステクノロジーのMIBモジュールを既に定義しています。たとえば、IEEE 802.11 MIBモジュール[IEEE.802-11.2007]。このようなMIBモジュールは、ワイヤレスバインディングMIBモジュールと呼ばれます。
This document introduces a mechanism to avoid redefining MIB objects in the existing MIB modules for a specific wireless technology, in other words, a mechanism to reuse wireless binding MIB modules defined by other SDOs.
このドキュメントでは、特定のワイヤレステクノロジーの既存のMIBモジュールのMIBオブジェクトの再定義を避けるメカニズムを紹介します。つまり、他のSDOによって定義されたワイヤレスバインドMIBモジュールを再利用するメカニズムです。
In summary, the CAPWAP-BASE-MIB module has the following design objectives:
要約すると、CapWap-Base-MIBモジュールには次の設計目標があります。
- To implement an architecture that uses SNMP for the management and control of wireless networks, and answering the operator's requirements for centralized management, whatever the wireless devices are configured and deployed (centralized, autonomous, or some mix);
- ワイヤレスネットワークの管理と制御にSNMPを使用するアーキテクチャを実装し、ワイヤレスデバイスが構成および展開されていても、集中管理のオペレーターの要件に応答する（集中、自律、またはミックス）。
- To be consistent with the CAPWAP protocol;
- CapWapプロトコルと一致すること。
- To be independent of any wireless technologies and be able to reuse wireless binding MIB modules defined by other SDOs;
- ワイヤレステクノロジーから独立し、他のSDOによって定義されたワイヤレスバインディングMIBモジュールを再利用できるようにすること。
- To enable interoperability between vendors;
- ベンダー間の相互運用性を有効にする。
- To meet the management requirements for the centralized WLAN architecture.
- 集中化されたWLANアーキテクチャの管理要件を満たすため。
The basic design idea of the CAPWAP-BASE-MIB module is:
CapWap-Base-Mibモジュールの基本的なデザインのアイデアは次のとおりです。
- The SNMP agent MUST be run on the AC devices and is not REQUIRED on the WTP devices. It follows the same model as the CAPWAP protocol: Centralized Control.
- SNMPエージェントはACデバイスで実行する必要があり、WTPデバイスでは必要ありません。CapWapプロトコルと同じモデル：集中制御に従います。
- It is designed to accommodate the specific needs of each wireless technology in a standard way. It is independent of any wireless technologies.
- 各ワイヤレステクノロジーの特定のニーズに標準的な方法で対応するように設計されています。ワイヤレステクノロジーとは無関係です。
- The ifIndex [RFC2863] is used as a common index for corresponding interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific wireless technologies.
- IFINDEX [RFC2863]は、特定のワイヤレステクノロジーのCapWap-Base-MIBおよびMIBモジュールの対応するインターフェイスの共通インデックスとして使用されます。
- The operator could manage and control the centralized WLAN architectures using multiple MIB modules defined by multiple SDOs, while keeping them loosely coupled.
- オペレーターは、複数のSDOで定義された複数のMIBモジュールを使用して、それらをゆるく結合したままにしながら、集中化されたWLANアーキテクチャを管理および制御できます。
For any wireless technology, the configuration and management of radios are very important. As usual, wireless binding MIB modules support radio management on their own. For example, the MIB tables such as the dot11OperationTable [IEEE.802-11.2007] are able to support WTP radio configuration. These tables use the ifIndex as the index, and work well under autonomous WLAN architecture.
ワイヤレステクノロジーでは、無線の構成と管理が非常に重要です。いつものように、ワイヤレスバインディングMIBモジュールは、それ自体でラジオ管理をサポートします。たとえば、dot11operationTable [IEEE.802-11.2007]などのMIBテーブルは、WTP無線構成をサポートできます。これらのテーブルは、Ifindexをインデックスとして使用し、自律的なWLANアーキテクチャの下でうまく機能します。
To reuse such wireless binding MIB modules is very important to centralized WLAN architectures. According to [RFC5415], a specific PHY radio could be identified by the combination of the identifiers of the WTP and radio (WTP ID + Radio ID), so the key point is to make use of the ifIndex idea and find a way to maintain the mappings between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism, an ifIndex can identify an interface in an abstract way, and it does NOT care for the interface's PHY location (either on the WTP or AC). The AC can have WTP Virtual Radio Interfaces to logically represent PHY radios on the WTP. From the operator's perspective, it appears that PHY radios are located on the AC, and the PHY location of the WTP (radio) is hidden. The operator can operate radios through MIB tables with the ifIndex of a WTP Virtual Radio Interface. As a type of abstract interface, the WTP Virtual Radio Interface could be used by any wireless technology such as IEEE 802.11 and 802.16. The capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used to store the mappings between the 'WTP ID + Radio ID' and the ifIndex.
このようなワイヤレスバインドMIBモジュールを再利用することは、集中型WLANアーキテクチャにとって非常に重要です。[RFC5415]によると、特定のPHY無線は、WTPと無線（WTP ID Radio ID）の識別子の組み合わせによって識別されるため、重要なポイントはIfindexのアイデアを利用して、維持する方法を見つけることです。「WTP ID Radio ID」とIFIndexの間のマッピング。一般的なメカニズムとして、Ifindexはインターフェイスを抽象的な方法で識別でき、インターフェイスのPHYの場所（WTPまたはACのいずれか）を気にしません。ACには、WTPのPHYラジオを論理的に表すWTP仮想無線インターフェイスを持つことができます。オペレーターの観点から見ると、Phy RadiosはACに位置し、WTP（無線）のPHY位置が隠されているようです。オペレーターは、WTP仮想無線インターフェイスのIFINDEXを使用して、MIBテーブルを介してラジオを操作できます。抽象インターフェイスの一種として、WTP仮想無線インターフェイスは、IEEE 802.11や802.16などのワイヤレステクノロジーで使用できます。capwap-base-mibモジュールのcapwapbasewirelessbindingtableは、「wtp id無線ID」とifindexの間のマッピングを保存するために使用されます。
According to the CAPWAP Protocol specification [RFC5415], when defining a binding for wireless technologies, the authors MUST include any necessary definitions for technology-specific messages and all technology-specific message elements for those messages. A CAPWAP binding protocol is required for a specific wireless binding technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding.
CAPWAPプロトコル仕様[RFC5415]によれば、ワイヤレステクノロジーのバインディングを定義する場合、著者は、テクノロジー固有のメッセージに必要な定義とそれらのメッセージにすべてのテクノロジー固有のメッセージ要素を含める必要があります。IEEE 802.11バインディングの[RFC5416]のプロトコルなど、特定のワイヤレスバインディングテクノロジーには、CAPWAP結合プロトコルが必要です。
Sometimes, not all the technology-specific message elements in a CAPWAP binding protocol have MIB objects defined by other SDOs. For example, the protocol of [RFC5416] defines WLAN management. The WLAN refers to a logical component instantiated on a WTP device. A single physical WTP MAY operate a number of WLANs. Also, Local or Split MAC modes could be specified for a WLAN. The MAC mode for a WLAN is not in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in addition to the existing wireless binding MIB modules defined by other SDOs, a CAPWAP protocol wireless binding MIB module is required to be defined for a wireless binding, e.g, the CAPWAP Protocol Binding MIB for IEEE 802.11 [RFC5834].
CAPWAPバインディングプロトコル内のすべてのテクノロジー固有のメッセージ要素が他のSDOによって定義されたMIBオブジェクトを持っているわけではない場合があります。たとえば、[RFC5416]のプロトコルはWLAN管理を定義します。WLANは、WTPデバイスにインスタンス化された論理コンポーネントを指します。単一の物理WTPが多数のWLANを動作させる場合があります。また、WLANにローカルまたはスプリットMACモードを指定できます。WLANのMACモードは、IEEE 802.11 [IEEE.802-11.2007]の範囲内ではありません。このような場合、他のSDOによって定義された既存のワイヤレスバインディングMIBモジュールに加えて、CAPWAPプロトコルワイヤレスバインディングMIBモジュールは、IEEE 802.11 [RFC5834]のCAPWAPプロトコル結合MIBなど、ワイヤレスバインディングのために定義する必要があります。
In a centralized WLAN architecture, a WTP profile is used to make configurations such as a static IP address for a WTP before and after it connects to the AC. It MUST contain the Base MAC address [RFC5415] of the WTP because the CAPWAP message received from the WTP contains the Base MAC address and the AC uses this Base MAC address to find the corresponding WTP profile.
集中化されたWLANアーキテクチャでは、WTPプロファイルを使用して、ACに接続する前後にWTPの静的IPアドレスなどの構成を作成します。WTPから受信したCAPWAPメッセージにはベースMACアドレスが含まれており、ACはこのベースMACアドレスを使用して対応するWTPプロファイルを見つけて、WTPのベースMACアドレス[RFC5415]を含める必要があります。
Section 4.6.40 of [RFC5415] omits indicating that the WTP's Base MAC address MUST be included in the WTP Board Data message element. This is a known errata item [Err1832] and should be fixed in any future revision of RFC 5415.
[RFC5415]のセクション4.6.40は、WTPのベースMACアドレスをWTPボードデータメッセージ要素に含める必要があることを示しています。これは既知のerrataアイテム[ERR1832]であり、RFC 5415の将来の改訂で修正する必要があります。
Another important function of WTP profile is to trigger the creation of WTP Virtual Radio Interfaces on the AC. To implement this function, a WTP profile MUST include the WTP's model number [RFC5415], which reflects the number of PHY radios on the WTP. In this way, the creation of a WTP profile triggers the AC to automatically create the same number of WTP Virtual Radio Interfaces corresponding to the WTP's PHY radios without manual intervention. With the ifIndexes of WTP Virtual Radio Interfaces, the operator could configure and manage the WTP's PHY radios through the wireless binding MIB modules.
WTPプロファイルのもう1つの重要な機能は、AC上のWTP仮想無線インターフェイスの作成をトリガーすることです。この関数を実装するには、WTPプロファイルにWTPのモデル番号[RFC5415]を含める必要があります。これは、WTPのPHYラジオの数を反映しています。このようにして、WTPプロファイルの作成により、ACがトリガーされ、手動介入なしにWTPのPHYラジオに対応する同じ数のWTP仮想無線インターフェイスが自動的に作成されます。WTP仮想無線インターフェイスのIFINDEXESを使用すると、オペレーターはワイヤレスバインディングMIBモジュールを介してWTPのPHYラジオを構成および管理できます。
The MIB objects are derived from the CAPWAP protocol document [RFC5415].
MIBオブジェクトは、CAPWAPプロトコルドキュメント[RFC5415]から派生しています。
1) capwapBaseAcNameListTable
1) capwapbaseacnameListtable
The AC name list table is used to configure the AC name list.
AC名リストテーブルは、AC名リストの構成に使用されます。
2) capwapBaseMacAclTable
2) capwapbasemacacltable
The ACL table is used to configure stations' Access Control Lists (ACLs).
ACLテーブルは、ステーションのアクセス制御リスト（ACLS）の構成に使用されます。
3) capwapBaseWtpProfileTable
3) capwapbasewtpprofiletable
The WTP profile table is used to configure WTP profiles for WTPs to be managed before they connect to the AC. An operator could change a WTP's current configuration by changing the values of parameters in the corresponding WTP profile, then the WTP could get the new configuration through the CAPWAP control channel.
WTPプロファイルテーブルは、ACに接続する前に管理するWTPのWTPプロファイルを構成するために使用されます。オペレーターは、対応するWTPプロファイルのパラメーターの値を変更することにより、WTPの現在の構成を変更でき、WTPはCapWap Controlチャネルを介して新しい構成を取得できます。
4) capwapBaseWtpStateTable
4) capwapbasewtpstateTable
The state table of WTPs is used to indicate the AC's CAPWAP FSM state for each WTP, and helps the operator to query a WTP's current configuration.
WTPの状態表は、各WTPのACのCAPWAP FSM状態を示すために使用され、オペレーターがWTPの現在の構成を照会するのに役立ちます。
5) capwapBaseWtpTable
5) capwapbasewtptable
The WTP table is used to display properties of the WTPs in running state.
WTPテーブルは、実行状態にWTPのプロパティを表示するために使用されます。
6) capwapBaseWirelessBindingTable
6) capwapbasewirelessbindingtable
The wireless binding table is used to display the mappings between WTP Virtual Radio Interfaces and PHY radios, and the wireless binding type for each PHY radio.
ワイヤレスバインディングテーブルは、WTP仮想無線インターフェイスとPhy Radiosの間のマッピングを表示するために使用され、各Phy無線のワイヤレスバインディングタイプを表示します。
7) capwapBaseStationTable
7) capwapbasestationTable
The station table is used for providing stations' basic property information.
ステーションテーブルは、ステーションの基本的なプロパティ情報を提供するために使用されます。
8) capwapBaseWtpEventsStatsTable
8) capwapbasewtpeventsStatStable
The WTP events statistic table is used for collecting WTP reboot count, link failure count, hardware failure count and so on.
WTPイベント統計テーブルは、WTPの再起動カウント、リンク障害カウント、ハードウェア障害カウントなどの収集に使用されます。
9) capwapBaseRadioEventsStatsTable
9) capwapbaseradioeventsStatStable
The radio events statistic table is used for collecting radio reset count, channel change count, hardware failure count, and so on.
ラジオイベントの統計表は、ラジオリセット数、チャネルの変更カウント、ハードウェアの障害カウントなどの収集に使用されます。
The CAPWAP-BASE-MIB module does not duplicate the objects of the 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being mandatory for all systems, and the objects apply to the entity as a whole. The 'system' group provides identification of the management entity and certain other system-wide data.
CapWap-Base-MIBモジュールは、すべてのシステムに必須であると定義されるSNMPV2-MIB [RFC3418]の「システム」グループのオブジェクトを複製しません。オブジェクトはエンティティ全体に適用されます。「システム」グループは、管理エンティティと特定の他のシステム全体のデータの識別を提供します。
The Interfaces Group [RFC2863] defines generic managed objects for managing interfaces. This memo contains the media-specific extensions to the Interfaces Group for managing WTP PHY radios that are modeled as interfaces.
インターフェイスグループ[RFC2863]は、インターフェイスを管理するための汎用管理オブジェクトを定義します。このメモには、インターフェイスとしてモデル化されたWTP Phy Radioを管理するためのインターフェイスグループへのメディア固有の拡張が含まれています。
The IF-MIB module is required to be supported on the AC. Each PHY radio on the WTP corresponds to a WTP Virtual Radio Interface on the AC. The WTP Virtual Radio Interface provides a way to configure the radio's parameters and query radio's traffic statistics, and reuse wireless binding modules defined by other SDOs. The interface MUST be modeled as an ifEntry, and ifEntry objects such as ifIndex, ifDescr, ifName, and ifAlias are to be used as per [RFC2863].
IF-MIBモジュールは、ACでサポートする必要があります。WTP上の各PHY無線は、ACのWTP仮想無線インターフェイスに対応しています。WTP仮想ラジオインターフェイスは、無線のパラメーターを構成し、無線のトラフィック統計をクエリする方法を提供し、他のSDOによって定義されたワイヤレスバインディングモジュールを再利用します。インターフェイスは、ifentryとしてモデル化され、ifindex、ifdescr、ifname、ifaliasなどのifentryオブジェクトを使用する必要があります[RFC2863]。
Also, as an ifIndex [RFC2863] is used as a common index for corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless technologies MIB modules, the AC MUST have a mechanism that preserves the values of the ifIndexes in the ifTable at AC reboot.
また、Ifindex [RFC2863]は、CapWap-Base-MIBおよび特定のワイヤレステクノロジーMIBモジュールの対応するインターフェイスの共通インデックスとして使用されているため、ACには、ACリブートのIfTableのIFINDEXESの値を保持するメカニズムが必要です。。
The ENTITY-MIB module [RFC4133] meets the need for a standardized way of representing a single agent that supports multiple instances of one MIB. It could express a certain relationship between multiple entities and provide entity properties for each entity.
Entity-MIBモジュール[RFC4133]は、1つのMIBの複数のインスタンスをサポートする単一のエージェントを表す標準化された方法の必要性を満たしています。複数のエンティティ間で特定の関係を表現し、各エンティティにエンティティプロパティを提供できます。
In a centralized WLAN architecture, the SNMP agent runs on the AC and is not required on the WTP. With the ENTITY-MIB module on the AC, it could keep entity information such as firmware revision and software revision of the AC and WTPs. From the ENTITY-MIB module's perspective, the overall physical entity (AC) is a 'compound' of multiple physical entities (that is, the WTPs connected to AC), and all entities are each identified by a physical index. The capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the capwapBaseWtpPhyIndex object to store the mappings of WTP object between CAPWAP-BASE-MIB and ENTITY-MIB modules.
集中化されたWLANアーキテクチャでは、SNMPエージェントはACで実行され、WTPでは必要ありません。AC上にエンティティMIBモジュールを使用すると、ACおよびWTPSのファームウェアリビジョンやソフトウェアリビジョンなどのエンティティ情報を保持できます。エンティティMIBモジュールの観点から見ると、全体的な物理エンティティ（AC）は複数の物理エンティティ（つまり、ACに接続されたWTP）の「化合物」であり、すべてのエンティティはそれぞれ物理インデックスによって識別されます。capwap-base-mibモジュールのcapwapbasewtptableは、capwapbasewtpphyindexオブジェクトを使用して、capwap-base-mibとentity-mibモジュールの間にWTPオブジェクトのマッピングを保存します。
By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules, operators could query the status and properties of the AC and WTPs. For example, they could get a WTP's current status through the CAPWAP-BASE-MIB module, and a WTP's software revision information through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not duplicate those objects defined in the ENTITY-MIB module.
CapWap-Base-MIBとEntity-MIBモジュールの両方を照会することにより、演算子はACおよびWTPSのステータスとプロパティを照会できます。たとえば、CapWap-Base-MIBモジュールを介してWTPの現在のステータスと、Entity-MIBモジュールを介したWTPのソフトウェアリビジョン情報を取得できます。CapWap-Base-MIBモジュールは、Entity-MIBモジュールで定義されているオブジェクトを複製しません。
The wireless binding MIB module of a wireless technology (such as [IEEE.802-11.2007]) is required to be supported on the AC. The CAPWAP-BASE-MIB module is able to support any wireless binding. Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a consistent and abstract way of reusing MIB objects in the wireless binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate those objects defined in the wireless binding MIB modules.
ワイヤレステクノロジーのワイヤレスバインドMIBモジュール（[IEEE.802-11.2007]など）は、ACでサポートする必要があります。CapWap-Base-MIBモジュールは、ワイヤレスバインディングをサポートできます。WTP仮想無線インターフェイスのIFINDEXESを通じて、ワイヤレスバインディングMIBモジュールでMIBオブジェクトを再利用する一貫した抽象的な方法を提供します。CapWap-Base-MIBモジュールは、ワイヤレスバインディングMIBモジュールで定義されているオブジェクトを複製しません。
The following MIB module IMPORTS objects from SYSAPPL-MIB [RFC2287], SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001], and ENTITY-MIB [RFC4133].
次のMIBモジュールは、SYSAPPL-MIB [RFC2287]、SNMPV2-SMI [RFC2578]、SNMPV2-TC [RFC2579]、SNMPV2-CONF [RFC2580]、IF-MIB [RFC2863]、SNMP-FRamework-MIB [RFC3411]からオブジェクトをインポートします。、inet-address-mib [rfc4001]、およびentity-mib [rfc4133]。
Below, the IEEE 802.11 binding is used as an example of how the MIB modules operate.
以下では、IEEE 802.11バインディングは、MIBモジュールの動作方法の例として使用されます。
1) Create a WTP profile.
1) WTPプロファイルを作成します。
Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create the WTP profile as follows:
WTPのベースMACアドレスが「00：01：01：01：01：00」であるとします。次のようにWTPプロファイルを作成します。
In capwapBaseWtpProfileTable
{
capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWtpMacAddress = '00:01:01:01:01:00',
capwapBaseWtpProfileWtpModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 123456',
capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIpAddress = '192.0.2.10',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.0.2.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
capwapBaseWtpProfileWtpReportInterval = 120,
capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpEcnSupport = limited(0)
}
Suppose the WTP with model number 'WTP123' has one PHY radio, which is identified by ID 1. The creation of this WTP profile triggers the AC to automatically create a WTP Virtual Radio Interface and add a new row object to the capwapBaseWirelessBindingTable without manual intervention. Suppose the ifIndex of the WTP Virtual Radio Interface is 10. The following information is stored in the capwapBaseWirelessBindingTable.
モデル番号「WTP123」があるWTPに1つのPHY無線があるとします。これはID 1で識別されます。このWTPプロファイルの作成により、ACが自動的にWTP仮想無線インターフェイスを作成し、手動介入なしにCapWapBaseWirelessBindingTableに新しい行オブジェクトを追加するとします。。WTP仮想無線インターフェイスのifindexが10であると仮定します。次の情報は、capwapbasewirelessbindingtableに保存されています。
In capwapBaseWirelessBindingTable
{
capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2)
}
The WTP Virtual Radio Interfaces on the AC correspond to the PHY radios on the WTP. The WTP Virtual Radio Interface is modeled by ifTable [RFC2863].
AC上のWTP仮想無線インターフェイスは、WTPのPHYラジオに対応しています。WTP仮想無線インターフェイスは、IFTable [RFC2863]によってモデル化されています。
In ifTable
{
ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface',
ifType = 254,
ifMtu = 0,
ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1),
ifOperStatus = false(0),
ifLastChange = 0,
ifInOctets = 0,
ifInUcastPkts = 0,
ifInDiscards = 0,
ifInErrors = 0,
ifInUnknownProtos = 0,
ifOutOctets = 0,
ifOutUcastPkts = 0,
ifOutDiscards = 0,
ifOutErrors = 0
}
2) Query the ifIndexes of WTP Virtual Radio Interfaces.
2) WTP仮想無線インターフェイスのifindexesをクエリします。
Before configuring PHY radios, the operator needs to get the ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY radios.
Phy Radioを構成する前に、オペレーターはPhy Radiosに対応するWTP仮想無線インターフェイスのIfindexesを取得する必要があります。
As capwapBaseWirelessBindingTable already stores the mappings between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio Interfaces, the operator can get the ifIndex information by querying this table. Such a query operation SHOULD run from radio ID 1 to radio ID 31 according to [RFC5415]), and stop when an invalid ifIndex value (0) is returned.
CapWapBaseWirelessBindingTableは、Phy Radio（無線ID）とWTP仮想無線インターフェイスのIFIndexes間のマッピングをすでに保存しているため、オペレーターはこのテーブルをクエリしてIFINDEX情報を取得できます。このようなクエリ操作は、[RFC5415]に従ってラジオID 1からラジオID 31に実行され、無効なifindex値（0）が返された場合に停止する必要があります。
This example uses capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 1 as inputs to query the capwapBaseWirelessBindingTable, and gets capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, and gets an invalid ifIndex value (0), so the query operation ends. This method gets not only the ifIndexes of WTP Virtual Radio Interfaces, but also the numbers of PHY radios. Besides checking whether the ifIndex value is valid, the operator SHOULD check whether the capwapBaseWirelessBindingType is the desired binding type.
この例では、capwapbasewtpprofileid = 1およびcapwapbasewirelessbindioid = 1を使用して、capwapbasewirelessbindingtableをクエリするための入力として使用し、capwapbasewireladioifindex = 10を取得します。この方法は、WTP仮想無線インターフェイスのIfindexesだけでなく、Phy Radioの数も取得します。Ifindex値が有効かどうかを確認することに加えて、演算子はCapWapBaseWirelessBindingTypeが目的のバインディングタイプであるかどうかを確認する必要があります。
3) Configure specific wireless binding parameters for a WTP Virtual Radio Interface.
3) WTP仮想無線インターフェイスの特定のワイヤレスバインディングパラメーターを構成します。
This configuration is made on the AC through a specific wireless binding MIB module such as the IEEE 802.11 MIB module.
この構成は、IEEE 802.11 MIBモジュールなどの特定のワイヤレスバインドMIBモジュールを介してACで作成されます。
The following shows an example of configuring parameters for a WTP Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 dot11OperationTable [IEEE.802-11.2007].
以下は、IEEE 802.11 Dot11operationTable [IEEE.802-11.2007]を介してIfindex 10を使用したWTP仮想無線インターフェイスのパラメーターを構成する例を示しています。
In dot11OperationTable
{
ifIndex = 10,
dot11MACAddress = '00:00:00:00:00:00',
dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = 'capwap',
dot11ProductID = 'capwap',
dot11CAPLimit = 2,
dot11HCCWmin = 0,
dot11HCCWmax = 0,
dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1,
dot11EDCAAveragingPeriod = 5
}
4) Get the current configuration status report from the WTP to the AC.
4) WTPからACへの現在の構成ステータスレポートを取得します。
According to [RFC5415], before a WTP that has joined the AC gets configuration from the AC, it needs to report its current configuration status by sending a configuration status request message to the AC, which uses the message to update MIB objects on the AC. For example, for IEEE 802.11 binding, the AC updates data in the ifTable [RFC2863] and IEEE 802.11 MIB module, and so on, according to the message. For ifIndex 10, its ifOperStatus in ifTable is updated according to the current radio operational status in the CAPWAP message.
[RFC5415]によれば、ACからACの取得構成に結合したWTPの前に、ACにメッセージを使用してMIBオブジェクトを更新するためにメッセージを使用する構成ステータス要求メッセージをACに送信して、現在の構成ステータスを報告する必要があります。。たとえば、IEEE 802.11バインディングの場合、ACはメッセージに従って、IFTable [RFC2863]およびIEEE 802.11 MIBモジュールなどのデータを更新します。Ifindex 10の場合、IftableのIfoperstatusは、CapWapメッセージの現在の無線運用ステータスに従って更新されます。
5) Query WTP and radio statistical data.
5) クエリWTPおよび無線統計データ。
After WTPs start to run, the operator could query WTP and radio statistical data through CAPWAP-BASE-MIB and the specific binding MIB module on the AC. For example, through dot11CountersTable in the IEEE 802.11 MIB module, the operator could query the counter data of a radio using the ifIndex of the corresponding WTP Virtual Radio Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB module, the operator could query the properties of running WTPs.
WTPSが実行を開始した後、オペレーターはACのCapWap-Base-MIBおよび特定のバインディングMIBモジュールを介してWTPおよび無線統計データをクエリすることができました。たとえば、IEEE 802.11 MIBモジュールのDOT11CounterStableを介して、オペレーターは、対応するWTP仮想無線インターフェイスのIFINDEXを使用して無線のカウンターデータを照会できます。capwap-base-mibモジュールにcapwapbasewtptableテーブルを使用すると、オペレーターはWTPSの実行プロパティを照会できます。
6) Run MIB operations through a CAPWAP protocol wireless binding MIB module.
6) CAPWAPプロトコルワイヤレスバインディングMIBモジュールを介してMIB操作を実行します。
For example, for the CAPWAP IEEE 802.11 binding protocol [RFC5416], some MIB operations such as MAC mode configuration for a WLAN depend on the CAPWAP Protocol Binding MIB for IEEE 802.11 [RFC5834]. For more information, refer to [RFC5834].
たとえば、CAPWAP IEEE 802.11結合プロトコル[RFC5416]の場合、WLANのMACモード構成などのMIB操作は、IEEE 802.11 [RFC5834]のCAPWAPプロトコル結合MIBに依存します。詳細については、[RFC5834]を参照してください。
7) Query other properties of a WTP.
7) WTPの他のプロパティをクエリします。
The Operator could query MIB objects in the ENTITY-MIB [RFC4133] module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB module. The properties of a WTP such as software version, hardware version are available in the ENTITY-MIB module.
オペレーターは、capwap-base-mibモジュールのcapwapbasewtptableのcapwapbasewtpphyindexを使用して、エンティティミブ[RFC4133]モジュールのMIBオブジェクトをクエリすることができます。ソフトウェアバージョン、ハードウェアバージョンなどのWTPのプロパティは、Entity-MIBモジュールで利用できます。
CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN
IMPORTS
輸入
PhysAddress, TEXTUAL-CONVENTION, TruthValue, DateAndTime, RowStatus FROM SNMPv2-TC LongUtf8String FROM SYSAPPL-MIB InterfaceIndex, ifGeneralInformationGroup FROM IF-MIB PhysicalIndex FROM ENTITY-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32, Unsigned32, Counter32, Gauge32, TimeTicks
PhysAddress、Textual Convention、TruthValue、dateandtime、rowstatus snmpv2-tc longutf8string from Sysappl-mib interfaceindex、ifgeneralInformationgroup from if-mib snmpadminstring from snmp-framework-mib cositification-group、オブジェクトグループ、オブジェクトグループ、モッフル - グラウングからのif-mib snmpadminstringSNMPV2-CONFモジュールアイデンティティ、オブジェクトタイプ、通知タイプ、MIB-2、Integer32、unsigned32、Counter32、Gauge32、Timeticksから
FROM SNMPv2-SMI InetAddressType, InetAddress FROM INET-ADDRESS-MIB;
snmpv2-smi inetaddresstypeから、inet-address-mibからのinetAddressから。
capwapBaseMIB MODULE-IDENTITY LAST-UPDATED "201004300000Z" -- 30 April 2010 ORGANIZATION "IETF Control And Provisioning of Wireless Access Points (CAPWAP) Working Group http://www.ietf.org/html.charters/capwap-charter.html" CONTACT-INFO "General Discussion: capwap@frascone.com To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
capwapbasemibモジュールのアイデンティティ最後の「201004300000z」 - 2010年4月30日組織 "ワイヤレスアクセスポイント（capwap）ワーキンググループhttp://www.ietf.org/html.charters/capwap-charter.html"contact-info "一般的なディスカッション：capwap@frascone.comを購読する：http：//lists.frascone.com/mailman/listinfo/capwap
Yang Shi (editor) Hangzhou H3C Tech. Co., Ltd. Beijing R&D Center of H3C, Digital Technology Plaza NO. 9 Shangdi 9th Street, Haidian District Beijing 100085 China Phone: +86 010 82775276 Email: rishyang@gmail.com
Yang Shi（編集者）Hangzhou H3c Tech。Co.、Ltd。BeijingR＆D Center of H3C、Digital Technology Plaza No。9 Shangdi 9th Street、Haidian District Beijing 100085 China電話：86 010 82775276電子メール：rishyang@gmail.com
David T. Perkins (editor) 228 Bayview Dr. San Carlos, CA 94070 USA Phone: +1 408 394-8702 Email: dperkins@dsperkins.com
David T. Perkins（編集者）228 Bayview Dr. San Carlos、CA 94070 USA電話：1 408 394-8702メール：dperkins@dsperkins.com
Chris Elliott (editor) 1516 Kent St. Durham, NC 27707 USA Phone: +1 919-308-1216 Email: chelliot@pobox.com
クリス・エリオット（編集者）1516 Kent St. Durham、NC 27707 USA電話：1 919-308-1216メール：chelliot@pobox.com
Yong Zhang (editor) Fortinet, Inc. 1090 Kifer Road Sunnyvale, CA 94086 USA Email: yzhang@fortinet.com"
Yong Zhang（編集者）Fortinet、Inc。1090 Kifer Road Sunnyvale、CA 94086 USAメール：Yzhang@fortinet.com "
DESCRIPTION "Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved.
説明 "Copyright（c）2010 IETF TrustおよびCodeの著者として特定された人。すべての権利は予約されています。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
変更とバイナリ形式での再配布と使用は、変更の有無にかかわらず、IETF Trustの法的規定（IETFドキュメントに関する法的規定）のセクション4.Cに記載されている簡略化されたBSDライセンスに基づいて許可されており、ライセンス条件に従うことが許可されています。http://trustee.ietf.org/license-info）。
This version of this MIB module is part of RFC 5833; see the RFC itself for full legal notices.
このMIBモジュールのこのバージョンは、RFC 5833の一部です。完全な法的通知については、RFC自体を参照してください。
This MIB module contains managed object definitions for
the CAPWAP Protocol."
REVISION "201004300000Z"
DESCRIPTION
"Initial version published as RFC 5833"
::= { mib-2 196 }
-- Textual Conventions
- テキストの慣習
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP profile."
SYNTAX Unsigned32 (0..4096)
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP instance.
As usual, the Base MAC address of the WTP is used."
SYNTAX OCTET STRING (SIZE(6|8))
CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"Represents the unique identifier of a station instance.
As usual, the MAC address of the station is used."
SYNTAX OCTET STRING (SIZE(6|8))
CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a radio on a WTP."
SYNTAX Unsigned32 (1..31)
CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the tunneling modes of operation that are
supported by a WTP.
The WTP MAY support more than one option, represented by
the bit field below:
localBridging(0) - Local bridging mode
dot3Tunnel(1) - 802.3 frame tunnel mode
nativeTunnel(2) - Native frame tunnel mode"
REFERENCE
"Section 4.6.43 of CAPWAP Protocol Specification, RFC 5415."
SYNTAX BITS {
localBridging(0),
dot3Tunnel(1),
nativeTunnel(2)
}
CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the MAC mode of operation supported by a WTP.
The following enumerated values are supported:
localMAC(0) - Local-MAC mode
splitMAC(1) - Split-MAC mode
both(2) - Both Local-MAC and Split-MAC
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object
follows that rule."
REFERENCE
"Section 4.6.44 of CAPWAP Protocol Specification, RFC 5415."
SYNTAX INTEGER {
localMAC(0),
splitMAC(1),
both(2)
}
CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the channel type for CAPWAP protocol.
The following enumerated values are supported:
data(1) - Data channel
control(2) - Control channel"
SYNTAX INTEGER {
data(1),
control(2)
}
CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the authentication credential type for a WTP.
The following enumerated values are supported:
other(1) - Other method, for example, vendor specific
clear(2) - Clear text and no authentication
x509(3) - X.509 certificate authentication
psk(4) - Pre-Shared secret authentication
As a mandatory requirement, CAPWAP control channel
authentication SHOULD use DTLS, either by certificate or
PSK. For data channel authentication, DTLS is optional."
SYNTAX INTEGER {
other(1),
clear(2),
x509(3),
psk(4)
}
-- Top-level components of this MIB module
- このMIBモジュールのトップレベルコンポーネント
-- Notifications
capwapBaseNotifications OBJECT IDENTIFIER
::= { capwapBaseMIB 0 }
-- Tables, Scalars
capwapBaseObjects OBJECT IDENTIFIER
::= { capwapBaseMIB 1 }
-- Conformance
capwapBaseConformance OBJECT IDENTIFIER
::= { capwapBaseMIB 2 }
-- AC Objects Group
-ACオブジェクトグループ
capwapBaseAc OBJECT IDENTIFIER
::= { capwapBaseObjects 1 }
capwapBaseWtpSessions OBJECT-TYPE
SYNTAX Gauge32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the total number of WTPs that are connecting to
the AC."
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 1 }
capwapBaseWtpSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum number of WTP sessions configured on
the AC.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 2 }
capwapBaseStationSessions OBJECT-TYPE
SYNTAX Gauge32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the total number of stations that are accessing
the wireless service provided by the AC."
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 3 }
capwapBaseStationSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum number of station sessions configured
on the AC.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 4 }
capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE
SYNTAX BITS {
other(0),
clear(1),
dtls(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The AC communicates its policy on the use of DTLS for
the CAPWAP data channel.
The AC MAY support more than one option, represented by the bit
field below:
other(0) - Other method, for example, vendor specific
clear(1) - Clear text
dtls(2) - DTLS"
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 5 }
capwapBaseControlChannelAuthenOptions OBJECT-TYPE
SYNTAX BITS {
x509(0),
psk(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the authentication credential type supported by the
AC for CAPWAP control channel.
The AC MAY support more than one option, represented by the bit
field below:
x509(0) - X.509 certificate based
psk(1) - Pre-Shared secret"
REFERENCE
"Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 6 }
-- capwapBaseAcNameListTable table
-capwapbaseacnameListtableテーブル
capwapBaseAcNameListTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that configure the AC name list.
Values of all read-create objects in this table are
persistent at restart/reboot."
REFERENCE
"Section 4.6.5 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 9 }
capwapBaseAcNameListEntry OBJECT-TYPE
SYNTAX CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that configures the AC name list."
INDEX { capwapBaseAcNameListId }
::= { capwapBaseAcNameListTable 1 }
CapwapBaseAcNameListEntry ::= SEQUENCE {
capwapBaseAcNameListId Unsigned32,
capwapBaseAcNameListName LongUtf8String,
capwapBaseAcNameListPriority Unsigned32,
capwapBaseAcNameListRowStatus RowStatus
}
capwapBaseAcNameListId OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of an AC Name list."
::= { capwapBaseAcNameListEntry 1 }
capwapBaseAcNameListName OBJECT-TYPE
SYNTAX LongUtf8String (SIZE(1..512))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the name of an AC, and it is expected to be
an UTF-8 encoded string."
REFERENCE
"Section 4.6.5 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAcNameListEntry 2 }
capwapBaseAcNameListPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the priority order of the preferred AC.
For instance, the value of one (1) is used to set the primary
AC, the value of two (2) is used to set the secondary AC, etc."
REFERENCE
"Section 4.6.5 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAcNameListEntry 3 }
capwapBaseAcNameListRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create, modify, and/or delete a row in this table. The value of capwapBaseAcNameListName and capwapBaseAcNameListPriority can be changed when this object is in state 'active' or in 'notInService'.
capwapbaseacnamelistrowstatus object-type syntax rowstatus max-access read-createステータス現在の説明 "このオブジェクトは、このテーブルの行の作成、変更、および/または削除に使用されます。「アクティブ」または「notinservice」。
The capwapBaseAcNameListRowStatus may be changed to 'active'
if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values."
::= { capwapBaseAcNameListEntry 4 }
-- End of capwapBaseAcNameListTable table
-CapWapBaseAcNameListTableテーブルの終わり
-- capwapBaseMacAclTable table
-capwapbasemacacltableテーブル
capwapBaseMacAclTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseMacAclEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that configure station Access Control
Lists (ACLs).
The WTP will not provide service to the MAC addresses
configured in this table.
Values of all read-create objects in this table are persistent
at AC restart/reboot."
REFERENCE
"Section 4.6.7 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 10 }
capwapBaseMacAclEntry OBJECT-TYPE
SYNTAX CapwapBaseMacAclEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that configures station Access Control
Lists (ACLs)."
INDEX { capwapBaseMacAclId }
::= { capwapBaseMacAclTable 1 }
CapwapBaseMacAclEntry ::= SEQUENCE {
capwapBaseMacAclId Unsigned32,
capwapBaseMacAclStationId CapwapBaseStationIdTC,
capwapBaseMacAclRowStatus RowStatus
}
capwapBaseMacAclId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of an ACL."
::= { capwapBaseMacAclEntry 1 }
capwapBaseMacAclStationId OBJECT-TYPE
SYNTAX CapwapBaseStationIdTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the MAC address of a station to which WTPs will
no longer provides service."
REFERENCE
"Section 4.6.7 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseMacAclEntry 2 }
capwapBaseMacAclRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create, modify, and/or delete a row
in this table.
The value of capwapBaseMacAclStationId can be changed when
this object is in state 'active' or in 'notInService'.
The capwapBaseMacAclRowStatus may be changed to 'active'
if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values."
::= { capwapBaseMacAclEntry 3 }
-- End of capwapBaseMacAclTable table
- capwapbasemacacltableテーブルの終わり
-- End of AC Objects Group
-ACオブジェクトグループの終わり
-- WTP Objects Group
-WTPオブジェクトグループ
capwapBaseWtps OBJECT IDENTIFIER
::= { capwapBaseObjects 2 }
-- capwapBaseWtpProfileTable Table
-capwapbasewtpprofileTableテーブル
capwapBaseWtpProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that configure WTP profiles for WTPs to be managed before they connect to the AC. An operator could change a WTP's configuration by changing the values of parameters in the corresponding WTP profile, then the WTP could get the new configuration through the CAPWAP control channel.
capwapbasewtpprofileTableオブジェクトタイプcapwapbasewtpprofileentry max-access not-accessable accessable current current current current current "wtpプロファイルを構成するWTPプロファイルを構成するオブジェクトのテーブルのテーブルのテーブルのテーブルをACに接続する前に、WTPの構成を変更することでWTPの構成を変更することでWTPの構成を変更することができます。対応するWTPプロファイルのパラメーターでは、WTPはCAPWAP制御チャネルを介して新しい構成を取得できます。
Values of all read-create objects in this table are
persistent at restart/reboot."
::= { capwapBaseWtps 1 }
capwapBaseWtpProfileEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that configures and displays a WTP profile."
INDEX { capwapBaseWtpProfileId }
::= { capwapBaseWtpProfileTable 1 }
CapwapBaseWtpProfileEntry ::= SEQUENCE {
capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC,
capwapBaseWtpProfileName SnmpAdminString,
capwapBaseWtpProfileWtpMacAddress CapwapBaseWtpIdTC,
capwapBaseWtpProfileWtpModelNumber SnmpAdminString,
capwapBaseWtpProfileWtpName LongUtf8String,
capwapBaseWtpProfileWtpLocation LongUtf8String,
capwapBaseWtpProfileWtpStaticIpEnable TruthValue,
capwapBaseWtpProfileWtpStaticIpType InetAddressType,
capwapBaseWtpProfileWtpStaticIpAddress InetAddress,
capwapBaseWtpProfileWtpNetmask InetAddress,
capwapBaseWtpProfileWtpGateway InetAddress,
capwapBaseWtpProfileWtpFallbackEnable INTEGER,
capwapBaseWtpProfileWtpEchoInterval Unsigned32,
capwapBaseWtpProfileWtpIdleTimeout Unsigned32,
capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32,
capwapBaseWtpProfileWtpReportInterval Unsigned32,
capwapBaseWtpProfileWtpStatisticsTimer Unsigned32,
capwapBaseWtpProfileWtpEcnSupport INTEGER,
capwapBaseWtpProfileRowStatus RowStatus
}
capwapBaseWtpProfileId OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP profile."
::= { capwapBaseWtpProfileEntry 1 }
capwapBaseWtpProfileName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION
capwapbasewtpprofilename object-type sntax snmpadminstring max-access read-createステータス現在の説明
"Represents the name of a WTP profile."
::= { capwapBaseWtpProfileEntry 2 }
capwapBaseWtpProfileWtpMacAddress OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the Base MAC address of a WTP.
A WTP profile MUST contain the Base MAC address of the WTP
because the CAPWAP message received from the WTP contains
its Base MAC address and the AC uses the Base MAC address to
find the corresponding WTP profile.
Section 4.6.40 of [RFC5415] omits indicating that the WTP's
Base MAC address must be included in the WTP Board Data
message element. This is a known errata item and should be
fixed in any future revision of the RFC 5415."
REFERENCE
"Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 3 }
capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the model number of a WTP.
A WTP profile MUST include the WTP's model number, which
reflects the number of Physical Layer (PHY) radios on the WTP.
In this way, the creation of a WTP profile triggers the AC
to automatically create the same number of WTP Virtual Radio
Interfaces corresponding to the WTP's PHY radios without
manual intervention. With the ifIndexes of WTP Virtual
Radio Interfaces, the operator could configure and manage
the WTP's PHY radios through the wireless binding MIB
modules."
REFERENCE
"Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 4 }
capwapBaseWtpProfileWtpName OBJECT-TYPE SYNTAX LongUtf8String (SIZE(1..512)) MAX-ACCESS read-create STATUS current DESCRIPTION "Represents the name of the WTP." REFERENCE "Section 4.6.45 of CAPWAP Protocol Specification, RFC 5415."
capwapbasewtpprofilewtpname object-type syntax longutf8string（size（1..512））max-access read-createステータス現在の説明「wtpの名前を表します。」参照「CAPWAPプロトコル仕様のセクション4.6.45、RFC5415。」
::= { capwapBaseWtpProfileEntry 5 }
capwapBaseWtpProfileWtpLocation OBJECT-TYPE
SYNTAX LongUtf8String (SIZE(1..1024))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the location of the WTP."
REFERENCE
"Section 4.6.30 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 6 }
capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether the WTP SHOULD use a static IP address
or not. A value of false disables the static IP address,
while a value of true enables it."
REFERENCE
"Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 7 }
capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType {ipv4(1)}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the static IP address type used by the WTP.
Only ipv4(1) is supported by the object.
Although the CAPWAP protocol [RFC5415] supports both IPv4
and IPv6, note that the CAPWAP field modeled by this
object does not support IPv6, so the object does not
support ipv6(2)."
REFERENCE
"Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 8 }
capwapBaseWtpProfileWtpStaticIpAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the static IP address to be assigned to the WTP.
The format of this IP address is determined by the
corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType."
REFERENCE
"Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 9 }
capwapBaseWtpProfileWtpNetmask OBJECT-TYPE
SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the netmask to be assigned to the WTP.
The format of this netmask is determined by the
corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType."
REFERENCE
"Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 10 }
capwapBaseWtpProfileWtpGateway OBJECT-TYPE
SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the gateway to be assigned to the WTP.
The format of this IP address is determined by the
corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType."
REFERENCE
"Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 11 }
capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether to enable or disable automatic CAPWAP
fallback in the event that a WTP detects its preferred AC
and is not currently connected to it.
The following enumerated values are supported:
enabled(1) - The fallback mode is enabled
disabled(2) - The fallback mode is disabled"
REFERENCE
"Section 4.6.42 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { enabled }
::= { capwapBaseWtpProfileEntry 12 }
capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo
Request messages to the AC that the WTP has joined."
REFERENCE
"Section 4.7.7 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseWtpProfileEntry 13 }
capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the idle timeout value that the WTP SHOULD enforce
for its active stations."
REFERENCE
"Section 4.7.8 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 300 }
::= { capwapBaseWtpProfileEntry 14 }
capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32 (2..180)
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the maximum time allowed between sending Discovery
Request messages, in seconds."
REFERENCE
"Section 4.7.10 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 20 }
::= { capwapBaseWtpProfileEntry 15 }
capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the interval for WTP to send the Decryption Error
report."
REFERENCE
"Section 4.7.11 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 16 }
capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the interval the WTP uses between the WTP Event
Requests it transmits to the AC to communicate its statistics,
in seconds."
REFERENCE
"Section 4.7.14 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 17 }
capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE
SYNTAX INTEGER {
limited(0),
fullAndLimited(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the support for the Explicit Congestion Notification
(ECN) bits, as defined in [RFC3168].
The following enumerated values are supported:
limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object follows
that rule."
REFERENCE
"Section 4.6.25 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 18 }
capwapBaseWtpProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create, modify, and/or delete a row
capwapbasewtpprofilerowstatus object-type syntax rowstatus max-access read-createステータス現在の説明 "このオブジェクトは、行の作成、変更、および/または削除に使用されます
in this table. The value of capwapBaseWtpProfileName, capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation can be changed when this object is in state 'active' or in 'notInService'. The other objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row: a. change the row status to 'notInService' b. change the values of the row c. change the row status to 'active' The capwapBaseWtpProfileRowStatus may be changed to 'active' if the managed objects capwapBaseWtpProfileName, capwapBaseWtpProfileWtpMacAddress, capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpName, and capwapBaseWtpProfileWtpLocation in the conceptual row have been assigned valid values.
この表で。このオブジェクトが状態「アクティブ」または「notinservice」にあるときに、capwapbasewtpprofilename、capwapbasewtpprofilewtpnameおよびcapwapbasewtpprofilewtplocationの値を変更できます。連続した他のオブジェクトは、対応する概念行のこのオブジェクトの値が「アクティブ」ではない場合にのみ変更できます。したがって、この概念的行の1つ以上のオブジェクトを変更するには、a。行のステータスを「notinservice」に変更しますb。行の値を変更c。行のステータスを「アクティブ」に変更します。CapWapBaseWTPPROFILEROWSTATUSは、マネージドオブジェクトCapWapBaseWtppRofileName、CapwapBaseWtppRofilewtpmacAddress、capwapbasewtpprofilewtpmodelnummurnummunmunmunmunmunmunmumnumnummunmummunmummunmunmunmunmunmunmunmunmunmunmunmunmunmunmunmunmangの場合、capwapbasewtpprofilewtpmacaddressの場合、「アクティブ」に変更される場合があります。
Deleting a WTP profile in use will disconnect the WTP from
the AC. So the network management system SHOULD
ask the operator to confirm such an operation.
When a WTP profile entry is removed from the table,
the corresponding WTP Virtual Radio Interfaces are also
removed from the capwapBaseWirelessBindingTable and
ifTable [RFC2863].
Also, the related object instances SHOULD be removed from
the wireless binding MIB modules such as the IEEE 802.11
MIB module [IEEE.802-11.2007]."
::= { capwapBaseWtpProfileEntry 19 }
-- End of capwapBaseWtpProfileTable table
-capwapbasewtpprofileTableテーブルの終わり
-- capwapBaseWtpStateTable table
-capwapbasewtpstateTableテーブル
capwapBaseWtpStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that indicate the AC's CAPWAP FSM state
for each WTP, and helps the operator to query a WTP's
current configuration."
::= { capwapBaseWtps 2 }
capwapBaseWtpStateEntry OBJECT-TYPE
capwapbasewtpStateEntryオブジェクトタイプ
SYNTAX CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays the AC's CAPWAP FSM state
for each WTP.
Also, the operator could query the current configuration
of a WTP by using the identifier of the corresponding
WTP profile."
INDEX { capwapBaseWtpStateWtpId }
::= { capwapBaseWtpStateTable 1 }
CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpStateWtpIpAddressType InetAddressType,
capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpStateWtpLocalIpAddressType InetAddressType,
capwapBaseWtpStateWtpLocalIpAddress InetAddress,
capwapBaseWtpStateWtpBaseMacAddress PhysAddress,
capwapBaseWtpState INTEGER,
capwapBaseWtpStateWtpUpTime TimeTicks,
capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC
}
capwapBaseWtpStateWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP."
::= { capwapBaseWtpStateEntry 1 }
capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the IP address type of a WTP.
Only ipv4(1) and ipv6(2) are supported by the object."
::= { capwapBaseWtpStateEntry 2 }
capwapBaseWtpStateWtpIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the IP address of a WTP that corresponds to the IP address in the IP packet header.
capwapbasewtpstatewtpipaddress object-type syntax inetaddress max-access読み取り専用ステータス現在の説明 "ipパケットヘッダーのIPアドレスに対応するWTPのIPアドレスを表します。
The format of this IP address is determined by
the corresponding instance of object
capwapBaseWtpStateWtpIpAddressType."
REFERENCE
"Section 4 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 3 }
capwapBaseWtpStateWtpLocalIpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the local IP address type of a WTP.
Only ipv4(1) and ipv6(2) are supported by the object."
::= { capwapBaseWtpStateEntry 4 }
capwapBaseWtpStateWtpLocalIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the local IP address of a WTP and models the
CAPWAP Local IPv4 Address or CAPWAP Local IPv6 Address fields
[RFC5415].
If a Network Address Translation (NAT) device is present
between WTP and AC, the value of
capwapBaseWtpStateWtpLocalIpAddress will be different from the
value of capwapBaseWtpStateWtpIpAddress.
The format of this IP address is determined by
the corresponding instance of object
capwapBaseWtpStateWtpLocalIpAddressType."
REFERENCE
"Sections 4.6.11 and 4.6.12 of CAPWAP Protocol Specification,
RFC 5415."
::= { capwapBaseWtpStateEntry 5 }
capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6|8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the WTP's Base MAC Address, which MAY be
assigned to the primary Ethernet interface.
The instance of the object corresponds to the Base MAC Address
sub-element in the CAPWAP protocol [RFC5415]."
REFERENCE
"Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 6 }
capwapBaseWtpState OBJECT-TYPE
SYNTAX INTEGER {
dtls(1),
join(2),
image(3),
configure(4),
dataCheck(5),
run(6),
reset(7),
dtlsTeardown(8),
unknown(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the various possibilities of the AC's CAPWAP FSM
state for each WTP.
The following enumerated values are supported:
dtls(1) - DTLS negotiation states, which include
DTLS setup, authorize, DTLS connect
join(2) - The WTP is joining with the AC
image(3) - The WTP is downloading software
configure(4) - The WTP is getting configuration from
the AC
dataCheck(5) - The AC is waiting for the Data Channel Keep
Alive Packet
run(6) - The WTP enters the running state
reset(7) - The AC transmits a reset request message
to the WTP
dtlsTeardown(8) - DTLS session is torn down
unknown(9) - Operator already prepared configuration
for the WTP, while the WTP has not
contacted the AC until now"
REFERENCE
"Section 2.3.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 7 }
capwapBaseWtpStateWtpUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the time (in hundredths of a second) since the
WTP has been in the running state (corresponding to the
value run(6) of capwapBaseWtpState)."
::= { capwapBaseWtpStateEntry 8 }
capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE
capwapbasewtpstatewtpcurrwtpprofileid object-type
SYNTAX CapwapBaseWtpProfileIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the current identifier of a WTP profile.
The operator could query a WTP's current configuration
with the identifier of a WTP profile."
::= { capwapBaseWtpStateEntry 9 }
-- End of capwapBaseWtpStateTable Table
-capwapbasewtpstateTableテーブルの終わり
-- capwapBaseWtpTable Table
-capwapbasewtptableテーブル
capwapBaseWtpTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display properties of the WTPs
in running state."
::= { capwapBaseWtps 3 }
capwapBaseWtpEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays properties of the WTPs
in running state."
INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpTable 1 }
CapwapBaseWtpEntry ::= SEQUENCE {
capwapBaseWtpCurrId CapwapBaseWtpIdTC,
capwapBaseWtpPhyIndex PhysicalIndex,
capwapBaseWtpBaseMacAddress PhysAddress,
capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC,
capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC,
capwapBaseWtpDiscoveryType INTEGER,
capwapBaseWtpRadiosInUseNum Gauge32,
capwapBaseWtpRadioNumLimit Unsigned32,
capwapBaseWtpRetransmitCount Counter32
}
capwapBaseWtpCurrId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP in running state."
::= { capwapBaseWtpEntry 1 }
capwapBaseWtpPhyIndex OBJECT-TYPE
SYNTAX PhysicalIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the unique physical index of a physical entity
in the ENTITY-MIB module [RFC4133].
Information about a specific WTP such as its software version
could be accessed through this index."
::= { capwapBaseWtpEntry 2 }
capwapBaseWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6|8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the WTP's Base MAC Address, which MAY be assigned
to the primary Ethernet interface.
The instance of the object corresponds to the Base MAC Address
sub-element in the CAPWAP protocol [RFC5415]."
REFERENCE
"Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 3 }
capwapBaseWtpTunnelModeOptions OBJECT-TYPE
SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the tunneling modes of operation supported by
the WTP."
REFERENCE
"Section 4.6.43 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 4 }
capwapBaseWtpMacTypeOptions OBJECT-TYPE SYNTAX CapwapBaseMacTypeTC MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the MAC mode of operation supported by the WTP." REFERENCE "Section 4.6.44 of CAPWAP Protocol Specification, RFC 5415."
capwapbasewtpmactypeoptions object-type syntax capwapbasemactypetc max-access read-only status current current "wtpでサポートされている操作のMacモードを表します。」参照「CAPWAPプロトコル仕様のセクション4.6.44、RFC5415。」
::= { capwapBaseWtpEntry 5 }
capwapBaseWtpDiscoveryType OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
staticConfig(1),
dhcp(2),
dns(3),
acRef(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents how the WTP discovers the AC.
The following enumerated values are supported:
unknown(0) - Unknown
staticConfig(1) - Static configuration
dhcp(2) - DHCP
dns(3) - DNS
acRef(4) - AC referral
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object
follows that rule."
REFERENCE
"Section 4.6.21 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 6 }
capwapBaseWtpRadiosInUseNum OBJECT-TYPE
SYNTAX Gauge32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of radios in use on the WTP."
REFERENCE
"Section 4.6.41 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 7 }
capwapBaseWtpRadioNumLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the maximum radio number supported by the WTP."
REFERENCE
"Section 4.6.41 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 8 }
capwapBaseWtpRetransmitCount OBJECT-TYPE
capwapbasewtpretransmitcountオブジェクトタイプ
SYNTAX Counter32
UNITS "retransmissions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of retransmissions for a given
CAPWAP packet."
REFERENCE
"Section 4.8.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 9 }
-- End of capwapBaseWtpTable table
- capwapbasewtptableテーブルの終わり
-- capwapBaseWirelessBindingTable Table
-capwapbasewirelessbindingtableテーブル
capwapBaseWirelessBindingTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the mappings between
WTP Virtual Radio Interfaces and PHY radios, and the
wireless binding type for each PHY radio.
As capwapBaseWirelessBindingTable stores the mappings between
PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio
Interfaces, the operator can get the ifIndex information by
querying this table. Such a query operation SHOULD run from
radio ID 1 to radio ID 31 according to [RFC5415],
and stop when an invalid ifIndex value (0) is returned.
Values of all objects in this table are persistent at
restart/reboot."
::= { capwapBaseWtps 4 }
capwapBaseWirelessBindingEntry OBJECT-TYPE
SYNTAX CapwapBaseWirelessBindingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays the mapping between
a specific WTP Virtual Radio Interface and a PHY
radio, and the wireless binding type for the PHY radio."
INDEX {
capwapBaseWtpProfileId,
capwapBaseWirelessBindingRadioId
}
::= { capwapBaseWirelessBindingTable 1 }
CapwapBaseWirelessBindingEntry ::= SEQUENCE {
capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC,
capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex,
capwapBaseWirelessBindingType INTEGER
}
capwapBaseWirelessBindingRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of
capwapBaseWirelessBindingRadioId for their first radio."
REFERENCE
"Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWirelessBindingEntry 1 }
capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the index value that uniquely identifies a
WLAN Virtual Radio Interface. The interface identified by
a particular value of this index is the same interface as
identified by the same value of the ifIndex.
Before WTPs contact the AC to get configuration,
the operator configures WTP profiles for them.
The creation of a WTP profile triggers the system to
automatically create a specific number of WTP Virtual Radio
Interfaces and add a new row object in the
capwapBaseWirelessBindingTable without manual intervention.
As most MIB modules use the ifIndex to identify an interface
for configuration and statistical data (for example, the IEEE
802.11 MIB module [IEEE.802-11.2007]), it will be easy to
reuse other wireless binding MIB modules through the WTP
Virtual Radio Interface in the Centralized WLAN
Architecture."
::= { capwapBaseWirelessBindingEntry 2 }
capwapBaseWirelessBindingType OBJECT-TYPE
SYNTAX INTEGER {
dot11(1),
epc(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the wireless binding type for the radio.
The following enumerated values are supported:
dot11(1) - IEEE 802.11
epc(3) - EPCGlobal"
REFERENCE
"Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWirelessBindingEntry 3 }
-- End of capwapBaseWirelessBindingTable Table
- capwapbasewirelessbindingtableテーブルの終わり
-- capwapBaseStationTable Table
-capwapbasestationtableテーブル
capwapBaseStationTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseStationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display stations that are accessing
the wireless service provided by the AC."
REFERENCE
"Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 5 }
capwapBaseStationEntry OBJECT-TYPE
SYNTAX CapwapBaseStationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays a station that is
associated with the specific radio on the WTP.
Note that in some cases such as roaming that a station may
simultaneously associate with two WTPs for some (short) time.
The MIB implementation MUST ensure there is only one valid
and meaningful entry for a specific station."
INDEX { capwapBaseStationId }
::= { capwapBaseStationTable 1 }
CapwapBaseStationEntry ::= SEQUENCE {
capwapBaseStationId CapwapBaseStationIdTC,
capwapBaseStationWtpId CapwapBaseWtpIdTC,
capwapBaseStationWtpRadioId CapwapBaseRadioIdTC,
capwapBaseStationAddedTime DateAndTime,
capwapBaseStationVlanName SnmpAdminString
}
capwapBaseStationId OBJECT-TYPE
SYNTAX CapwapBaseStationIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of the station."
REFERENCE
"Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 1 }
capwapBaseStationWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP in running state."
::= { capwapBaseStationEntry 2 }
capwapBaseStationWtpRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of
capwapBaseStationWtpRadioId for their first radio."
REFERENCE
"Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 3 }
capwapBaseStationAddedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the time when the station is added."
REFERENCE
"Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 4 }
capwapBaseStationVlanName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "Represents VLAN name to which the station is associated." REFERENCE
capwapbasestationvlanname object-type syntax snmpadminstring（size（0..32））max-access読み取り専用ステータス現在の説明「ステーションが関連付けられているVLAN名を表します。」参照
"Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 5 }
-- End of capwapBaseStationTable Table
-CapWapBasestationTableテーブルの終わり
-- capwapBaseWtpEventsStatsTable
-capwapbasewtpeventsStatStable
capwapBaseWtpEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the WTPs' events statistics."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 6 }
capwapBaseWtpEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpEventsStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays the events statistics
of a WTP."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpEventsStatsTable 1 }
CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
capwapBaseWtpEventsStatsRebootCount Counter32,
capwapBaseWtpEventsStatsInitCount Counter32,
capwapBaseWtpEventsStatsLinkFailureCount Counter32,
capwapBaseWtpEventsStatsSwFailureCount Counter32,
capwapBaseWtpEventsStatsHwFailureCount Counter32,
capwapBaseWtpEventsStatsOtherFailureCount Counter32,
capwapBaseWtpEventsStatsUnknownFailureCount Counter32,
capwapBaseWtpEventsStatsLastFailureType INTEGER
}
capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the number of reboots that have occurred due to a WTP crash.
capwapbasewteventsstatsrebootcount object-type syntax counter32 max-access読み取り専用ステータス現在の説明 "wtpクラッシュのために発生した再起動の数を表します。
Note that the CAPWAP field [RFC5415] modeled by this counter
takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this
behavior, which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate
the object."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 1 }
capwapBaseWtpEventsStatsInitCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of reboots that have occurred at the
request of a CAPWAP protocol message, such as a change in
configuration that requires a reboot or an explicit CAPWAP
protocol reset request.
Note that the CAPWAP field [RFC5415] modeled by this counter
takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this
behavior, which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate
the object."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 2 }
capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to link failures."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 3 }
capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the number of times that a CAPWAP protocol connection with an AC has failed due to software-related reasons."
capwapbasewteventsSwaTATSSWFAILURECOUNTオブジェクトタイプの構文カウンター32 MAX-ACCESS読み取り専用ステータス現在の説明 "ソフトウェア関連の理由によりACとのCAPWAPプロトコル接続が失敗した回数を表します。」
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 4 }
capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to hardware-related
reasons."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 5 }
capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to known reasons, other
than the AC-initiated, link, software or hardware failures."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 6 }
capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that a CAPWAP protocol
connection with an AC has failed for unknown reasons."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 7 }
capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE SYNTAX INTEGER { unsupported(0), acInit(1), linkFailure(2), swFailure(3), hwFailure(4), otherFailure(5), unknown(255)
capwapbasewteventsStatSlastFailureTypeオブジェクトタイプの構文integer {Unsupported（0）、acinit（1）、linkfailure（2）、swfailure（3）、hwfailure（4）、otherfailure（5）、unknown（255）
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the failure type of the most recent WTP failure.
The following enumerated values are supported:
unsupported(0) - Not supported
acInit(1) - The AC initiated
linkFailure(2) - Link failure
swFailure(3) - Software failure
hwFailure(4) - Hardware failure
otherFailure(5) - Other failure
unknown(255) - Unknown (e.g., WTP doesn't keep track
of info)
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object
follows that rule."
REFERENCE
"Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 8 }
-- End of capwapBaseWtpEventsStatsTable table
-capwapbasewtpeventsStatStableテーブルの終わり
-- capwapBaseRadioEventsStatsTable table
-capwapbaseradioeventsStatStableテーブル
capwapBaseRadioEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display statistics on the radios'
behaviors and reasons why the WTP radio has been reset.
To get the events statistics of all radios on a specific WTP
(identified by the capwapBaseWtpCurrId), a query
operation SHOULD run from radio ID 1 to radio ID 31 until there
is no data returned. The radio ID here corresponds to the
object capwapBaseRadioEventsWtpRadioId. If the previous MIB
operations such as query on the capwapBaseWirelessBindingTable
know the exact value of each radio ID, the query operation on
the capwapBaseRadioEventsStatsTable could use that value
of Radio IDs."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 7 }
capwapBaseRadioEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseRadioEventsStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that displays the statistical data of
events that happened on a specific radio of a WTP."
INDEX { capwapBaseWtpCurrId, capwapBaseRadioEventsWtpRadioId }
::= { capwapBaseRadioEventsStatsTable 1 }
CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
capwapBaseRadioEventsWtpRadioId CapwapBaseRadioIdTC,
capwapBaseRadioEventsStatsResetCount Counter32,
capwapBaseRadioEventsStatsSwFailureCount Counter32,
capwapBaseRadioEventsStatsHwFailureCount Counter32,
capwapBaseRadioEventsStatsOtherFailureCount Counter32,
capwapBaseRadioEventsStatsUnknownFailureCount Counter32,
capwapBaseRadioEventsStatsConfigUpdateCount Counter32,
capwapBaseRadioEventsStatsChannelChangeCount Counter32,
capwapBaseRadioEventsStatsBandChangeCount Counter32,
capwapBaseRadioEventsStatsCurrNoiseFloor Integer32,
capwapBaseRadioEventsStatsDecryptErrorCount Counter32,
capwapBaseRadioEventsStatsLastFailureType INTEGER
}
capwapBaseRadioEventsWtpRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP.
For example, WTP A and WTP B use the same value of
capwapBaseRadioEventsWtpRadioId for their first radio."
REFERENCE
"Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 1 }
capwapBaseRadioEventsStatsResetCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has been
reset."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 2 }
capwapBaseRadioEventsStatsSwFailureCount OBJECT-TYPE
capwapbaseradioeventsstatsswfailurecount object-type
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has failed due
to software-related reasons."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 3 }
capwapBaseRadioEventsStatsHwFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has failed due
to hardware-related reasons."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 4 }
capwapBaseRadioEventsStatsOtherFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has failed due to
known reasons, other than software or hardware failure."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 5 }
capwapBaseRadioEventsStatsUnknownFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has failed for
unknown reasons."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 6 }
capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION
capwapbaseradioeventsStatSconfigupdatecountオブジェクトタイプの構文Counter32 max-access読み取り専用ステータス現在の説明
"Represents the number of times that the radio configuration has
been updated."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 7 }
capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio channel has
been changed."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 8 }
capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of times that the radio has changed
frequency bands."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 9 }
capwapBaseRadioEventsStatsCurrNoiseFloor OBJECT-TYPE
SYNTAX Integer32
UNITS "dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the noise floor of the radio receiver in units of
dBm."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 10 }
capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the number of decryption errors that have occurred on the WTP. Note that this field is only valid in cases where the WTP provides encryption/decryption services."
capwapbaseradioeventsStatsdecrypterrorcountオブジェクトタイプの構文Counter32 Max-Access読み取り専用ステータス現在の説明 "WTPで発生した復号化エラーの数を表します。このフィールドは、WTPが暗号化/復号化サービスを提供する場合にのみ有効であることに注意してください。
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 11 }
capwapBaseRadioEventsStatsLastFailureType OBJECT-TYPE
SYNTAX INTEGER {
unsupported(0),
swFailure(1),
hwFailure(2),
otherFailure(3),
unknown(255)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the failure type of the most recent radio failure.
The following enumerated values are supported:
unsupported(0) - Not supported
swFailure(1) - Software failure
hwFailure(2) - Hardware failure
otherFailure(3) - Other failure
unknown(255) - Unknown
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object follows
that rule."
REFERENCE
"Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 12 }
-- End of capwapBaseRadioEventsStatsTable table
- capwapbaseradioeventsStatStableテーブルの終わり
-- End of WTP Objects Group
-WTPオブジェクトグループの終了
-- CAPWAP Base Parameters Group
-CapWapベースパラメータグループ
capwapBaseParameters OBJECT IDENTIFIER
::= { capwapBaseObjects 3 }
capwapBaseAcMaxRetransmit OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Represents the maximum number of retransmissions for a given CAPWAP packet before the link layer considers the peer dead. The value of the object is persistent at restart/reboot." REFERENCE
capwapbaseacmaxretransmitオブジェクトタイプの構文unstax untigned32 max-access read-writeステータス現在の説明 "リンクレイヤーがピアデッドと見なす前に、特定のCapWapパケットの再送信の最大数を表します。オブジェクトの値は再起動/リブートで持続します。参照
"Section 4.8.7 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 5 }
::= { capwapBaseParameters 1 }
capwapBaseAcChangeStatePendingTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, the AC will wait
for the Change State Event Request from the WTP after having
transmitted a successful Configuration Status Response
message.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.1 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 25 }
::= { capwapBaseParameters 2 }
capwapBaseAcDataCheckTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents The number of seconds the AC will wait for
the Data Channel Keep Alive, which is required by the
CAPWAP state machine's Data Check state.
The AC resets the state machine if this timer expires
prior to transitioning to the next state.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.4 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseParameters 3 }
capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE SYNTAX Unsigned32 UNITS "second" MAX-ACCESS read-write STATUS current DESCRIPTION "Represents the minimum time, in seconds, the AC MUST wait for DTLS session deletion. The value of the object is persistent at restart/reboot." REFERENCE "Section 4.7.6 of CAPWAP Protocol Specification, RFC 5415."
capwapbaseacdtlssessiondeleteTimerオブジェクトタイプの構文untigned32ユニット "2番目の"最大アクセス読み取りろいステータス現在の説明 "を表します。参照「CAPWAPプロトコル仕様のセクション4.7.6、RFC5415。」
DEFVAL { 5 }
::= { capwapBaseParameters 4 }
capwapBaseAcEchoInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo
Request messages to the AC with which the WTP has joined.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.7 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseParameters 5 }
capwapBaseAcRetransmitInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, in which a
non-acknowledged CAPWAP packet will be retransmitted.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.12 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 3 }
::= { capwapBaseParameters 6 }
capwapBaseAcSilentInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, during which the AC
SHOULD ignore all CAPWAP and DTLS packets received from the
WTP that is in the Sulking state.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.13 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseParameters 7 }
capwapBaseAcWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 (30..4294967295)
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, the AC MUST wait
without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.15 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 60 }
::= { capwapBaseParameters 8 }
capwapBaseAcWaitJoinTimer OBJECT-TYPE
SYNTAX Unsigned32 (20..4294967295)
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, the AC will wait
after the DTLS session has been established until it receives
the Join Request from the WTP. This timer MUST be greater
than 20 seconds.
The value of the object is persistent at restart/reboot."
REFERENCE
"Section 4.7.16 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 60 }
::= { capwapBaseParameters 9 }
capwapBaseAcEcnSupport OBJECT-TYPE
SYNTAX INTEGER {
limited(0),
fullAndLimited(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the support for the Explicit Congestion Notification
(ECN) bits, as defined in [RFC3168].
The value of the object is persistent at restart/reboot.
The following enumerated values are supported:
limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object follows
that rule."
REFERENCE
"Section 4.6.25 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseParameters 10 }
-- End of CAPWAP Base Parameters Group
- capwapベースパラメータグループの終わり
-- CAPWAP Statistics Group
-CapWap Statistics Group
capwapBaseStats OBJECT IDENTIFIER
::= { capwapBaseObjects 4 }
capwapBaseFailedDTLSAuthFailureCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of failed DTLS session establishment
attempts due to authentication failures."
REFERENCE
"Section 4.8.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStats 1 }
capwapBaseFailedDTLSSessionCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of failed DTLS session
establishment attempts."
REFERENCE
"Section 4.8.4 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStats 2 }
-- Notifications
- 通知
capwapBaseChannelUp NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod
}
STATUS current
DESCRIPTION
"This notification is sent by the AC when a CAPWAP channel
is established.
The notification is separated for data or control channel."
::= { capwapBaseNotifications 1 }
capwapBaseChannelDown NOTIFICATION-TYPE
capwapbasechanneldown通知タイプ
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfChannelType,
capwapBaseNtfChannelDownReason
}
STATUS current
DESCRIPTION
"This notification is sent by the AC when a CAPWAP channel
is down.
The notification is separated for data or control channel."
::= { capwapBaseNotifications 2 }
capwapBaseDecryptErrorReport NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfRadioId,
capwapBaseNtfStationIdList
}
STATUS current
DESCRIPTION
"This notification is generated when a WTP has had a
decryption error since the last report."
REFERENCE
"Section 4.6.17 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 3 }
capwapBaseJoinFailure NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfJoinFailureReason
}
STATUS current
DESCRIPTION
"This notification is generated when a WTP fails to join."
REFERENCE
"Section 4.6.35 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 4 }
capwapBaseImageUpgradeFailure NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfImageFailureReason
}
STATUS current
DESCRIPTION
"This notification is generated when a WTP fails to update
the firmware image."
REFERENCE
"Section 4.6.35 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 5 }
capwapBaseConfigMsgError NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements
}
STATUS current
DESCRIPTION
"This notification is generated when a WTP receives message
elements in the configuration management messages that it
is unable to apply locally."
REFERENCE
"Section 4.6.35 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 6 }
capwapBaseRadioOperableStatus NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfRadioId,
capwapBaseNtfRadioOperStatusFlag,
capwapBaseNtfRadioStatusCause
}
STATUS current
DESCRIPTION
"The notification is generated when a radio's operational state
has changed."
REFERENCE
"Section 4.6.34 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 7 }
capwapBaseAuthenFailure NOTIFICATION-TYPE
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod,
capwapBaseNtfAuthenFailureReason
}
STATUS current
DESCRIPTION
"This is notification of an authentication failure event
and provides the reason for it."
::= { capwapBaseNotifications 8 }
-- Objects used only in notifications
- 通知でのみ使用されるオブジェクト
-- Notification Objects
capwapBaseNotifyVarObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 5 }
capwapBaseNtfWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP."
::= { capwapBaseNotifyVarObjects 1 }
capwapBaseNtfRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which is
only required to be unique on a WTP.
For example, WTP A and WTP B can use the same value of
capwapBaseNtfRadioId for their first radio."
REFERENCE
"Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 2 }
capwapBaseNtfChannelType OBJECT-TYPE
SYNTAX CapwapBaseChannelTypeTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the channel type for the CAPWAP protocol."
::= { capwapBaseNotifyVarObjects 3 }
capwapBaseNtfAuthenMethod OBJECT-TYPE
SYNTAX CapwapBaseAuthenMethodTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the authentication method for the CAPWAP Channel."
::= { capwapBaseNotifyVarObjects 4 }
capwapBaseNtfChannelDownReason OBJECT-TYPE SYNTAX INTEGER { timeout(1), rekeyFailure(2), acRebootWtp(3), dtlsError(4), maxRetransmit(5)
capwapbasentfchanneldownReason object-type syntax integer {timeout（1）、rekeyfailure（2）、acrebootwtp（3）、dtlserror（4）、maxretransmit（5）
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the reason the channel is down.
The following enumerated values are supported:
timeout(1) - The keepalive timed out
rekeyFailure(2) - Rekey process failed; channel will be
broken
acRebootWtp(3) - The AC rebooted the WTP
dtlsError(4) - DTLS notifications: DTLSAborted,
DTLSReassemblyFailure, DTLSPeerDisconnect,
or frequent DTLSDecapFailure
maxRetransmit(5) - The underlying reliable transport's
RetransmitCount counter has reached the
MaxRetransmit variable"
::= { capwapBaseNotifyVarObjects 5 }
capwapBaseNtfStationIdList OBJECT-TYPE
SYNTAX LongUtf8String (SIZE (6..1024))
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents a list of station MAC addresses separated by
semicolons."
REFERENCE
"Section 4.6.17 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 6 }
capwapBaseNtfAuthenFailureReason OBJECT-TYPE
SYNTAX INTEGER {
keyMismatch(1),
invalidCert(2),
reassemblyFailure(3),
decapFailure(4),
encapFailure(5),
timeout(6),
unknown(8)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the reason for WTP authorization failure.
The following enumerated values are supported:
keyMismatch(1) - WTP's and AC's keys did not match
invalidCert(2) - Certification is not valid
reassemblyFailure(3) - Fragment reassembly failure
decapFailure(4) - Decapsulation error
encapFailure(5) - Encapsulation error
timeout(6) - WaitDTLS timer timeout
unknown(8) - Unknown reason"
REFERENCE
"Section 2.3.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 7 }
capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE
SYNTAX INTEGER {
operable(0),
inoperable(1)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the operation status of a radio.
The following enumerated values are supported:
operable(0) - The radio is operable
inoperable(1) - The radio is inoperable, and the
capwapBaseNtfRadioStatusCause object
gives the reason in detail
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object
follows that rule."
REFERENCE
"Section 4.6.34 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 8 }
capwapBaseNtfRadioStatusCause OBJECT-TYPE
SYNTAX INTEGER {
normal(0),
hwError(1),
swError(2),
adminSet(3)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the reason why the radio is out of service.
The following enumerated values are supported:
normal(0) - Normal status
hwError(1) - Radio failure
swError(2) - Software failure
adminSet(3) - Administratively set
Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value; this MIB object
follows that rule."
REFERENCE
"Section 4.6.34 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 9 }
capwapBaseNtfJoinFailureReason OBJECT-TYPE
SYNTAX INTEGER {
unspecified(1),
resDepletion(2),
unknownSource(3),
incorrectData(4),
sessionIdInUse(5),
unsupportedHw(6),
unsupportedBinding(7)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the reason of join failure.
The following enumerated values are supported:
unspecified(1) - Unspecified failure
resDepletion(2) - Resource depletion
unknownSource(3) - Unknown source
incorrectData(4) - Incorrect data
sessionIdInUse(5) - Session ID already in use
unsupportedHw(6) - WTP hardware not supported
unsupportedBinding(7) - Binding not supported"
REFERENCE
"Section 4.6.35 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 10 }
capwapBaseNtfImageFailureReason OBJECT-TYPE
SYNTAX INTEGER {
invalidChecksum(1),
invalidLength(2),
other(3),
inStorage(4)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the reason of image failure.
The following enumerated values are supported:
invalidChecksum(1) - Invalid checksum
invalidLength(2) - Invalid data length
other(3) - Other error
inStorage(4) - Image already present"
REFERENCE
"Section 4.6.35 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 11 }
capwapBaseNtfConfigMsgErrorType OBJECT-TYPE
SYNTAX INTEGER {
unknownElement(1),
unsupportedElement(2),
unknownValue(3),
unsupportedValue(4)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the type of configuration message error.
The following enumerated values are supported:
unknownElement(1) - Unknown message element
unsupportedElement(2) - Unsupported message element
unknownValue(3) - Unknown message element value
unsupportedValue(4) - Unsupported message element value"
REFERENCE
"Section 4.6.36 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 12 }
capwapBaseNtfMsgErrorElements OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the message elements sent by the AC in the
Configuration Status Response message that caused the error."
REFERENCE
"Section 4.6.36 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 13 }
-- Notification Control
capwapBaseNotifyControlObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 6 }
capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the Channel Up / Channel Down notification
should be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 1 }
capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the decryption error notification should
be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 2 }
capwapBaseJoinFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of a WTP join failure
should be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 3 }
capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of a WTP image upgrade
failure should be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 4 }
capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Represents whether the notification of configuration message error should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled.
capwapbaseconfigmsgerRornotifyEnable object-type struthvalue max-access read-writeステータス現在の説明 "構成メッセージエラーの通知を生成する必要があるかどうかを表します。通知が無効になっていること。
The value of the object is persistent at restart/reboot."
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 5 }
capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of a radio's operational
state change should be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 6 }
capwapBaseAuthenFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of authentication failure
should be generated.
A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot."
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 7 }
-- Module compliance
- モジュールコンプライアンス
capwapBaseCompliances OBJECT IDENTIFIER
::= { capwapBaseConformance 1 }
capwapBaseGroups OBJECT IDENTIFIER
::= { capwapBaseConformance 2 }
capwapBaseCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance to the CAPWAP-BASE-MIB module."
CapWapBaseComplianceモジュールコンプライアンスステータス現在の説明「CapWap-Base-MIBモジュールへの適合の要件を説明しています。」
MODULE IF-MIB -- The Interfaces MIB, RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup
}
MODULE -- this module
MANDATORY-GROUPS {
capwapBaseAcNodeGroup,
capwapBaseWtpProfileGroup,
capwapBaseWtpStateGroup,
capwapBaseWtpGroup,
capwapBaseRadioGroup,
capwapBaseStationGroup
}
GROUP capwapBaseAcNodeGroup2 DESCRIPTION "The capwapBaseAcNodeGroup2 group is optional."
グループcapwapbaseacnodegroup2説明「capwapbaseacnodegroup2グループはオプションです。」
GROUP capwapBaseAcNameListGroup DESCRIPTION "The capwapBaseAcNameListGroup group is optional."
グループcapwapbaseacnameListgroup説明「capwapbaseacnameListgroupグループはオプションです。」
GROUP capwapBaseMacAclsGroup DESCRIPTION "The capwapBaseMacAclsGroup group is optional."
グループcapwapbasemaclsgloup説明「Capwapbasemacalsgloupグループはオプションです。」
GROUP capwapBaseWtpProfileGroup2 DESCRIPTION "The capwapBaseWtpProfileGroup2 group is optional."
グループcapwapbasewtpprofilegroup2説明「capwapbasewtpprofilegroup2グループはオプションです。」
GROUP capwapBaseWtpGroup2 DESCRIPTION "The capwapBaseWtpGroup2 group is optional."
グループcapwapbasewtpgroup2説明「capwapbasewtpgroup2グループはオプションです。」
GROUP capwapBaseWtpEventsStatsGroup DESCRIPTION "The capwapBaseWtpEventsStatsGroup group is optional."
グループcapwapbasewtpeventsstatsStatsStatsStatsの説明「CapwapbasewtpeventsStatsgroupグループはオプションです。」
GROUP capwapBaseRadioEventsStatsGroup DESCRIPTION "The capwapBaseRadioEventsStatsGroup group is optional."
Group CapwapbaseradioeventsStatsStatsStatsStatsの説明「CapwapbaseradioEventsStatsStatsSgroup Groupはオプションです。」
GROUP capwapBaseParametersGroup DESCRIPTION "The capwapBaseParametersGroup group is optional."
グループCapwapbaseparametersGroup説明「CapwapbaseparametersGroupグループはオプションです。」
GROUP capwapBaseStatsGroup DESCRIPTION "The capwapBaseStatsGroup group is optional."
グループCapwapbasestatsgroup説明「Capwapbasestatsgroupグループはオプションです。」
GROUP capwapBaseNotificationsGroup DESCRIPTION
グループcapwapbasenotificationsgroupの説明
"The capwapBaseNotificationsGroup group is optional."
「CapWapBaseNotificationsGroupグループはオプションです。」
GROUP capwapBaseNotifyVarsGroup DESCRIPTION "The capwapBaseNotifyVarsGroup group is optional. If capwapBaseNotificationsGroup is supported, this group must be implemented."
グループcapwapbasenotifyvarsgroup説明「capwapbasenotifyvarsgroupグループはオプションです。capwapbasenotificationsgroupがサポートされている場合、このグループを実装する必要があります。」
GROUP capwapBaseNotifyControlGroup
DESCRIPTION
"The capwapBaseNotifyControlGroup group is optional.
If capwapBaseNotificationsGroup is supported,
this group must be implemented."
::= { capwapBaseCompliances 1 }
capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpSessions,
capwapBaseWtpSessionsLimit,
capwapBaseStationSessions,
capwapBaseStationSessionsLimit
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the basic properties of the AC from the CAPWAP
protocol perspective."
::= { capwapBaseGroups 1 }
capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS {
capwapBaseDataChannelDTLSPolicyOptions,
capwapBaseControlChannelAuthenOptions
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the other properties (such as security) of the AC from
the CAPWAP protocol perspective."
::= { capwapBaseGroups 2 }
capwapBaseAcNameListGroup OBJECT-GROUP
OBJECTS {
capwapBaseAcNameListName,
capwapBaseAcNameListPriority,
capwapBaseAcNameListRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to configure
the AC name list."
::= { capwapBaseGroups 3 }
capwapBaseMacAclsGroup OBJECT-GROUP
OBJECTS {
capwapBaseMacAclStationId,
capwapBaseMacAclRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to configure
the stations ACL."
::= { capwapBaseGroups 4 }
capwapBaseWtpProfileGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpProfileName,
capwapBaseWtpProfileWtpMacAddress,
capwapBaseWtpProfileWtpModelNumber,
capwapBaseWtpProfileWtpName,
capwapBaseWtpProfileWtpLocation,
capwapBaseWtpProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that is used to configure
the WTP profile."
::= { capwapBaseGroups 5 }
capwapBaseWtpProfileGroup2 OBJECT-GROUP
OBJECTS {
capwapBaseWtpProfileWtpStaticIpEnable,
capwapBaseWtpProfileWtpStaticIpType,
capwapBaseWtpProfileWtpStaticIpAddress,
capwapBaseWtpProfileWtpNetmask,
capwapBaseWtpProfileWtpGateway,
capwapBaseWtpProfileWtpFallbackEnable,
capwapBaseWtpProfileWtpEchoInterval,
capwapBaseWtpProfileWtpIdleTimeout,
capwapBaseWtpProfileWtpMaxDiscoveryInterval,
capwapBaseWtpProfileWtpReportInterval,
capwapBaseWtpProfileWtpStatisticsTimer,
capwapBaseWtpProfileWtpEcnSupport
}
STATUS current
DESCRIPTION
"A collection of optional objects that is used to
configure the WTP profile."
::= { capwapBaseGroups 6 }
capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpStateWtpIpAddressType,
capwapBaseWtpStateWtpIpAddress,
capwapBaseWtpStateWtpLocalIpAddressType,
capwapBaseWtpStateWtpLocalIpAddress,
capwapBaseWtpStateWtpBaseMacAddress,
capwapBaseWtpState,
capwapBaseWtpStateWtpUpTime,
capwapBaseWtpStateWtpCurrWtpProfileId
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the WTP's state information."
::= { capwapBaseGroups 7 }
capwapBaseWtpGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpBaseMacAddress,
capwapBaseWtpTunnelModeOptions,
capwapBaseWtpMacTypeOptions,
capwapBaseWtpDiscoveryType,
capwapBaseWtpRadiosInUseNum,
capwapBaseWtpRadioNumLimit
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the properties information for the WTPs in running state."
::= { capwapBaseGroups 8 }
capwapBaseWtpGroup2 OBJECT-GROUP
OBJECTS {
capwapBaseWtpPhyIndex,
capwapBaseWtpRetransmitCount
}
STATUS current
DESCRIPTION
"A collection of optional objects that is used to represent
the properties of the WTPs in running state."
::= { capwapBaseGroups 9 }
capwapBaseRadioGroup OBJECT-GROUP
capwapbaseradiogroupオブジェクトグループ
OBJECTS {
capwapBaseWirelessBindingVirtualRadioIfIndex,
capwapBaseWirelessBindingType
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the wireless binding type and the mappings between the
ifIndexes of WLAN Virtual Radio Interfaces and PHY radios."
::= { capwapBaseGroups 10 }
capwapBaseStationGroup OBJECT-GROUP
OBJECTS {
capwapBaseStationWtpId,
capwapBaseStationWtpRadioId,
capwapBaseStationAddedTime,
capwapBaseStationVlanName
}
STATUS current
DESCRIPTION
"A collection of objects that is used to represent
the stations' basic properties."
::= { capwapBaseGroups 11 }
capwapBaseWtpEventsStatsGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpEventsStatsRebootCount,
capwapBaseWtpEventsStatsInitCount,
capwapBaseWtpEventsStatsLinkFailureCount,
capwapBaseWtpEventsStatsSwFailureCount,
capwapBaseWtpEventsStatsHwFailureCount,
capwapBaseWtpEventsStatsOtherFailureCount,
capwapBaseWtpEventsStatsUnknownFailureCount,
capwapBaseWtpEventsStatsLastFailureType
}
STATUS current
DESCRIPTION
"A collection of objects that is used for collecting
WTP reboot count, link failure count, hardware failure
count, and so on."
::= { capwapBaseGroups 12 }
capwapBaseRadioEventsStatsGroup OBJECT-GROUP
OBJECTS {
capwapBaseRadioEventsStatsResetCount,
capwapBaseRadioEventsStatsSwFailureCount,
capwapBaseRadioEventsStatsHwFailureCount,
capwapBaseRadioEventsStatsOtherFailureCount,
capwapBaseRadioEventsStatsUnknownFailureCount,
capwapBaseRadioEventsStatsConfigUpdateCount,
capwapBaseRadioEventsStatsChannelChangeCount,
capwapBaseRadioEventsStatsBandChangeCount,
capwapBaseRadioEventsStatsCurrNoiseFloor,
capwapBaseRadioEventsStatsDecryptErrorCount,
capwapBaseRadioEventsStatsLastFailureType
}
STATUS current
DESCRIPTION
"A collection of objects that is used for collecting
radio reset count, channel change count, hardware failure
count, and so on"
::= { capwapBaseGroups 13 }
capwapBaseParametersGroup OBJECT-GROUP
OBJECTS {
capwapBaseAcMaxRetransmit,
capwapBaseAcChangeStatePendingTimer,
capwapBaseAcDataCheckTimer,
capwapBaseAcDTLSSessionDeleteTimer,
capwapBaseAcEchoInterval,
capwapBaseAcRetransmitInterval,
capwapBaseAcSilentInterval,
capwapBaseAcWaitDTLSTimer,
capwapBaseAcWaitJoinTimer,
capwapBaseAcEcnSupport
}
STATUS current
DESCRIPTION
"Objects used for the CAPWAP protocol's parameters."
::= { capwapBaseGroups 14 }
capwapBaseStatsGroup OBJECT-GROUP
OBJECTS {
capwapBaseFailedDTLSAuthFailureCount,
capwapBaseFailedDTLSSessionCount
}
STATUS current
DESCRIPTION
"Objects used for collecting the CAPWAP protocol's statistics."
::= { capwapBaseGroups 15 }
capwapBaseNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
capwapBaseChannelUp,
capwapBaseChannelDown,
capwapBaseDecryptErrorReport,
capwapBaseJoinFailure,
capwapBaseImageUpgradeFailure,
capwapBaseConfigMsgError,
capwapBaseRadioOperableStatus,
capwapBaseAuthenFailure
}
STATUS current
DESCRIPTION
"A collection of notifications in this MIB module."
::= { capwapBaseGroups 16 }
capwapBaseNotifyVarsGroup OBJECT-GROUP
OBJECTS {
capwapBaseNtfWtpId,
capwapBaseNtfRadioId,
capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod,
capwapBaseNtfChannelDownReason,
capwapBaseNtfStationIdList,
capwapBaseNtfAuthenFailureReason,
capwapBaseNtfRadioOperStatusFlag,
capwapBaseNtfRadioStatusCause,
capwapBaseNtfJoinFailureReason,
capwapBaseNtfImageFailureReason,
capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements
}
STATUS current
DESCRIPTION
"Objects used for notifications."
::= { capwapBaseGroups 17 }
capwapBaseNotifyControlGroup OBJECT-GROUP
OBJECTS {
capwapBaseChannelUpDownNotifyEnable,
capwapBaseDecryptErrorNotifyEnable,
capwapBaseJoinFailureNotifyEnable,
capwapBaseImageUpgradeFailureNotifyEnable,
capwapBaseConfigMsgErrorNotifyEnable,
capwapBaseRadioOperableStatusNotifyEnable,
capwapBaseAuthenFailureNotifyEnable
}
STATUS current
DESCRIPTION
"Objects used to enable or disable notifications."
::= { capwapBaseGroups 18 }
END10. 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. The followings are the tables and objects and their sensitivity/vulnerability:
このMIBモジュールには、読み取りワイトおよび/またはread-Createの最大アクセス句を持つ多くの管理オブジェクトが定義されています。このようなオブジェクトは、一部のネットワーク環境で敏感または脆弱と見なされる場合があります。適切な保護なしの非セクター環境でのセット操作のサポートは、ネットワーク操作に悪影響を与える可能性があります。次のものは、テーブルとオブジェクトであり、その感度/脆弱性です。
- Unauthorized changes to the capwapBaseWtProfileTable and writable objects under capwapBaseAcs group MAY disrupt allocation of resources in the network. For example, a WTP's static IP address could be changed by setting the capwapBaseWtpProfileWtpStaticIpAddress object.
- CapwapBaseWtprofileTableオブジェクトのCapwapbaseAcsグループの下での不正な変更は、ネットワーク内のリソースの割り当てを中断する可能性があります。たとえば、WTPの静的IPアドレスは、CapWapBaseWTPPROFILEWTPSTATICADDRESSオブジェクトを設定することで変更できます。
- Unauthorized changes to writable objects under the capwapBaseAc group MAY disrupt allocation of resources in the network. For example, an invalid value for the capwapBaseWtpSessionsLimit object will increase the AC's traffic burden.
- CapwapbaseAcグループの下での書き込みオブジェクトへの不正な変更は、ネットワーク内のリソースの割り当てを中断する可能性があります。たとえば、capwapbasewtpsessionslimitオブジェクトの無効な値は、ACのトラフィック負担を増加させます。
- Unauthorized changes to the capwapBaseMacAclTable MAY prevent legal stations from being able to access the network, while illegal stations are able to access it.
- Capwapbasemacacltableの不正な変更により、法務局がネットワークにアクセスすることができなくなる可能性があり、違法なステーションはそれにアクセスできます。
- Unauthorized changes to writable objects under the capwapBaseParameters group MAY influence CAPWAP protocol behavior and status. For example, an invalid value set for the capwapBaseAcDataCheckTimer MAY influence the CAPWAP state machine.
- Capwapbaseparametersグループの下での書き込みオブジェクトへの不正な変更は、CapWapプロトコルの動作とステータスに影響を与える可能性があります。たとえば、Capwapbaseacdatachecktimerに設定された無効な値は、CapWap状態マシンに影響を与える可能性があります。
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. The followings are the tables and objects and their sensitivity/vulnerability:
このMIBモジュールの読み取り可能なオブジェクトの一部（つまり、アクセスできないもの以外の最大アクセスを備えたオブジェクト）は、一部のネットワーク環境で敏感または脆弱と見なされる場合があります。したがって、これらのオブジェクトへのアクセスを取得および/または通知することさえ制御し、SNMPを介してネットワーク上に送信するときにこれらのオブジェクトの値を暗号化することも重要です。次のものは、テーブルとオブジェクトであり、その感度/脆弱性です。
- The capwapBaseDataChannelDTLSPolicyOptions and capwapBaseControlChannelAuthenOptions under the capwapBaseAc group expose the current security option for CAPWAP data and control channels.
- capwapbasedatachanneldtlspolicyoptionsとcapwapbasecontrolchannelauthenoptions capwapbaseacグループの下でのCapwapbasecontrolchannelauthenoptionsは、CapWapデータと制御チャネルの現在のセキュリティオプションを公開します。
- The capwapBaseWtpTable exposes a WTP's important information like tunnel mode, MAC type, and so on.
- capwapbasewtptableは、トンネルモード、Macタイプなど、WTPの重要な情報を公開します。
- The capwapBaseWtpEventsStatsTable exposes a WTP's failure information.
- capwapbasewtpeventsStatStableは、WTPの障害情報を公開します。
- The capwapBaseRadioEventsStatsTable exposes a radio's failure information.
- CapWapBaseradioEventsStatStableは、無線の障害情報を公開します。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPV3以前のSNMPバージョンには、適切なセキュリティが含まれていませんでした。ネットワーク自体が（たとえばIPSECを使用して）安全である場合でも、それでもセキュアネットワークで誰がアクセスして取得/セット（読み取り/変更/作成/削除/削除）を制御することはできません。MIBモジュール。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
実装者は、SNMPV3暗号化メカニズム（認証とプライバシーのため）の完全なサポートを含む、SNMPV3フレームワーク（[RFC3410]、セクション8を参照）で提供されるセキュリティ機能を考慮することをお勧めします。
Further, the 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エンティティが、実際に取得または設定する正当な権利を持つプリンシパル（ユーザー）にのみオブジェクトにアクセスできるように適切に構成されていることを保証するのは、顧客/オペレーターの責任です（変更（変更）（変更）/作成/削除）それら。
11.1. IANA Considerations for CAPWAP-BASE-MIB Module The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
11.1. CapWap-Base-MIBモジュールのIANAの考慮事項このドキュメントのMIBモジュールは、SMI番号レジストリに記録された次のIANA異議オブジェクト識別子値を使用します。
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapBaseMIB { mib-2 196 }
IANA has assigned the following ifType:
IANAは次のIFTypeを割り当てました。
Decimal Name Description
------- ------------ -------------------------------
254 capwapWtpVirtualRadio WTP Virtual Radio Interface
This MIB module is based on contributions from Long Gao.
このMIBモジュールは、Long GAOからの貢献に基づいています。
Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, Bert Wijnen, and David L. Black for helpful comments on this document and guiding some technical solutions.
David Harrington、Dan Romascanu、Abhijit Choudhury、Bert Wijnen、およびDavid L. Blackに感謝し、この文書に関する有益なコメントといくつかの技術的なソリューションを導いてくれました。
The authors also thank the following friends and coworkers: Fei Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Hao Wang, Yujin Zhao, Haitao Zhang, Xiansen Cai, and Xiaolan Wan.
著者は、Fei Fang、Xubin Zhu、Hao Song、Yu Liu、Sachin Dutta、Ju Wang、Hao Wang、Hao Wang、Yujin Zhao、Haitao Zhang、Xiansen Cai、Xiaolan Wanにも感謝します。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] Bradner、S。、「要件レベルを示すためにRFCで使用するためのキーワード」、BCP 14、RFC 2119、1997年3月。
[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level Managed Objects for Applications", RFC 2287, February 1998.
[RFC2287] Krupczak、C。およびJ. Saperia、「アプリケーション用のシステムレベルの管理オブジェクトの定義」、RFC 2287、1998年2月。
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578] McCloghrie、K.、Ed。、Perkins、D.、ed。、およびJ. Schoenwaelder、ed。、「管理情報の構造バージョン2（SMIV2）」、STD 58、RFC 2578、1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579] McCloghrie、K.、Ed。、Perkins、D.、ed。、およびJ. Schoenwaelder、ed。、「Smiv2のテキストコンベンション」、STD 58、RFC 2579、1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580] McCloghrie、K.、Perkins、D。、およびJ. Schoenwaelder、「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、「The Interfaces Group MIB」、RFC 2863、2000年6月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411] Harrington、D.、Presuhn、R。、およびB. Wijnen、「単純なネットワーク管理プロトコル（SNMP）管理フレームワークを説明するためのアーキテクチャ」、STD 62、RFC 3411、2002年12月。
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002.
[RFC3418] Presuhn、R。、「単純なネットワーク管理プロトコル（SNMP）の管理情報ベース（MIB）」、STD 62、RFC 3418、2002年12月。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001] Daniele、M.、Haberman、B.、Routhier、S。、およびJ. Schoenwaelder、「インターネットネットワークアドレスのテキストコンベンション」、RFC 4001、2005年2月。
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005.
[RFC4133] Bierman、A。およびK. McCloghrie、「Entity MIB（バージョン3）」、RFC 4133、2005年8月。
[RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification", RFC 5415, March 2009.
[RFC5415] Calhoun、P.、Montemurro、M。、およびD. Stanley、「ワイヤレスアクセスポイント（CAPWAP）プロトコル仕様の制御とプロビジョニング」、RFC 5415、2009年3月。
[Err1832] RFC Errata, "Errata ID 1832", for RFC 5415, <http://www.rfc-editor.org>.
[ERR1832] RFC ERRATA、「Errata ID 1832」、RFC 5415、<http://www.rfc-editor.org>。
[IEEE.802-11.2007] "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications", IEEE Standard 802.11, 2007, <htt p://standards.ieee.org/getieee802/download/ 802.11-2007.pdf>.
[IEEE.802-11.2007]「情報技術 - システム間の通信と情報交換 - ローカルおよびメトロポリタンエリアネットワーク - 特定の要件 - パート11：ワイヤレスLANメディアアクセス制御（MAC）および物理層（PHY）仕様」、IEEE標準802.1111111111111111111111111111、2007、<htt p：//standards.ieee.org/getieee802/download/ 802.11-2007.pdf>。
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition of Explicit Congestion Notification (ECN) to IP", RFC 3168, September 2001.
[RFC3168] Ramakrishnan、K.、Floyd、S。、およびD. Black、「IPへの明示的な混雑通知（ECN）の追加」、RFC 3168、2001年9月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410] Case、J.、Mundy、R.、Partain、D。、およびB. Stewart、「インターネット標準管理フレームワークの紹介と適用声明」、RFC 3410、2002年12月。
[RFC4118] Yang, L., Zerfos, P., and E. Sadot, "Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP)", RFC 4118, June 2005.
[RFC4118] Yang、L.、Zerfos、P。、およびE. Sadot、「ワイヤレスアクセスポイントの制御とプロビジョニングのための建築分類（CAPWAP）」、RFC 4118、2005年6月。
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer Security", RFC 4347, April 2006.
[RFC4347] Rescorla、E。およびN. Modadugu、「Datagram Transport Layer Security」、RFC 4347、2006年4月。
[RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416, March 2009.
[RFC5416] Calhoun、P.、Montemurro、M。、およびD. Stanley、「IEEE 802.11のワイヤレスアクセスポイント（CAPWAP）プロトコルバインディングの制御とプロビジョニング」、RFC 5416、2009年3月。
[RFC5834] Shi, Y., Ed., Perkins, D., Ed., Elliott, C., Ed., and Y. Zhang, Ed., "Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding MIB for IEEE 802.11", RFC 5834, May 2010.
[RFC5834] Shi、Y.、Ed。、Perkins、D.、Ed。、Elliott、C.、ed。、およびY. Zhang、ed。、「ワイヤレスアクセスポイントの制御とプロビジョニング（CAPWAP）プロトコルバインディングMIBIEEE 802.11 "、RFC 5834、2010年5月。
Authors' Addresses
著者のアドレス
Yang Shi (editor) Hangzhou H3C Tech. Co., Ltd. Beijing R&D Center of H3C, Digital Technology Plaza NO. 9 Shangdi 9th Street, Haidian District Beijing 100085 China
Yang Shi（編集者）Hangzhou H3c Tech。Co.、Ltd。BeijingR＆D Center of H3C、Digital Technology Plaza No。9 Shangdi 9th Street、Haidian District Beijing 100085 China
Phone: +86 010 82775276
EMail: rishyang@gmail.com
David T. Perkins (editor) 228 Bayview Dr. San Carlos, CA 94070 USA
David T. Perkins（編集者）228 Bayview Dr. San Carlos、CA 94070 USA
Phone: +1 408 394-8702
EMail: dperkins@dsperkins.com
Chris Elliott (editor) 1516 Kent St. Durham, NC 27707 USA
クリス・エリオット（編集者）1516 Kent St. Durham、NC 27707 USA
Phone: +1 919-308-1216
EMail: chelliot@pobox.com
Yong Zhang (editor) Fortinet, Inc. 1090 Kifer Road Sunnyvale, CA 94086 USA
Yong Zhang（編集者）Fortinet、Inc。1090 Kifer Road Sunnyvale、CA 94086 USA
EMail: yzhang@fortinet.com