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

张勇,Ed.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.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问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.

版权所有(c)2010 IETF信托基金和确定为文件作者的人员。版权所有。

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  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
        
   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
        
1. Introduction
1. 介绍

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)能够管理无线终端点(WTP)的集合。

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管理工作的基础。

2. The Internet-Standard Management Framework
2. 因特网标准管理框架

For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].

有关描述当前互联网标准管理框架的文件的详细概述,请参阅RFC 3410[RFC3410]第7节。

Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580 [RFC2580].

托管对象通过虚拟信息存储(称为管理信息库或MIB)进行访问。MIB对象通常通过简单网络管理协议(SNMP)进行访问。MIB中的对象是使用管理信息结构(SMI)中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块,如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。

3. Terminology
3. 术语

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.

访问控制器(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控制消息和可选的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控制端口和传输层协议(UDP或UDP Lite)定义的双向流,通过该协议发送和接收CAPWAP控制数据包。

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数据端口和传输层协议(UDP或UDP Lite)定义的双向流,通过该协议发送和接收CAPWAP数据包。

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协议支持两种操作模式:拆分和本地MAC(介质访问控制)。在拆分MAC模式下,所有第2层无线数据和管理帧通过CAPWAP协议封装,并在AC和WTP之间交换。本地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设备。可以说,完整的无线功能是跨多个物理网络设备实现的,即WTP和ACs。

4. Conventions
4. 习俗

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。

5. Overview
5. 概述
5.1. Requirements and Constraints
5.1. 要求和限制

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;

- 支持AC结合CAPWAP协议对WTP进行集中管理和监控;

- Allow operators to make configurations for WTPs before and after they connect to the AC;

- 允许操作员在WTP连接到AC之前和之后对其进行配置;

- Support querying of CAPWAP protocol parameters;

- 支持CAPWAP协议参数查询;

- Support displaying of WTPs' current states and configurations;

- 支持显示WTP的当前状态和配置;

- Provide basic property information about the AC, WTPs, radios, and stations, and their relationships;

- 提供有关AC、WTP、无线电和电台及其关系的基本属性信息;

- Provide counters for events on WTPs and radios such as reboot and hardware failure;

- 为WTP和无线电上的事件(如重新启动和硬件故障)提供计数器;

- Provide various notifications such as channel up and join failure.

- 提供各种通知,如通道启动和连接失败。

5.2. Wireless Binding MIB Modules
5.2. 无线绑定MIB模块

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.

其他标准开发组织(SDO),例如IEEE,已经为特定无线技术定义了MIB模块,例如IEEE 802.11 MIB模块[IEEE.802-11.2007]。这种MIB模块称为无线绑定MIB模块。

5.3. Design Objectives
5.3. 设计目标

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架构的管理要求。

5.4. Design Idea
5.4. 设计理念

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架构,同时保持它们松散耦合。

5.5. Mechanism of Reusing Wireless Binding MIB Modules
5.5. 无线绑定MIB模块的复用机制

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模块本身支持无线电管理。例如,MIB表,如dot11OperationTable[IEEE.802-11.2007]能够支持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

重用这样的无线绑定MIB模块对于集中式WLAN架构非常重要。根据[RFC5415],特定的PHY无线电可以通过WTP和无线电的标识符(WTP ID+无线电ID)的组合来识别,因此关键点是利用ifIndex思想并找到一种方法来维护“WTP ID+无线电ID”和ifIndex之间的映射。作为一种通用机制,ifIndex可以抽象地标识接口,它不关心接口的PHY位置(在WTP或AC上)。AC可以具有WTP虚拟无线电接口,以逻辑方式表示WTP上的PHY无线电。从运营商的角度来看,PHY无线电似乎位于AC上,并且

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.

WTP(收音机)已隐藏。操作员可以使用WTP虚拟无线电接口的ifIndex通过MIB表操作无线电。作为一种抽象接口,WTP虚拟无线电接口可用于任何无线技术,如IEEE 802.11和802.16。CAPWAP-BASE-MIB模块中的capwapBaseWirelessBindingTable用于存储“WTP ID+无线电ID”和ifIndex之间的映射。

5.6. CAPWAP Protocol Wireless Binding MIB Module
5.6. CAPWAP协议无线绑定MIB模块

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],在定义无线技术的绑定时,作者必须包括技术特定消息的任何必要定义以及这些消息的所有技术特定消息元素。特定无线绑定技术需要CAPWAP绑定协议,例如用于IEEE 802.11绑定的[RFC5416]协议。

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的CAPWAP协议绑定MIB[RFC5834]。

5.7. WTP Profile
5.7. 水处理厂概况

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配置文件用于在WTP连接到AC之前和之后进行配置,例如WTP的静态IP地址。它必须包含基本MAC地址[RFC5415]因为从WTP接收的CAPWAP消息包含基本MAC地址,AC使用此基本MAC地址查找相应的WTP配置文件。

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板数据消息元素中的指示。这是一个已知的勘误表项[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

WTP配置文件的另一个重要功能是触发在AC上创建WTP虚拟无线电接口。要实现此功能,WTP配置文件必须包括WTP的型号[RFC5415],该型号反映了WTP上的PHY无线电数量。这样,WTP配置文件的创建将触发AC

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的PHY无线电对应的相同数量的WTP虚拟无线电接口,无需手动干预。通过WTP虚拟无线电接口的iIndex,操作员可以通过无线绑定MIB模块配置和管理WTP的PHY无线电。

6. Structure of the MIB Module
6. MIB模块的结构

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) CapwapBaseMaclactable

The ACL table is used to configure stations' Access Control Lists (ACLs).

ACL表用于配置站点的访问控制列表(ACL)。

3) capwapBaseWtpProfileTable

3) CAPWAPBASEWTPROFILETABLE

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配置文件表用于在WTP连接到AC之前为其配置要管理的WTP配置文件。操作员可以通过更改相应WTP配置文件中的参数值来更改WTP的当前配置,然后WTP可以通过CAPWAP控制通道获得新配置。

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) CapwapBasewTable

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无线电之间的映射,以及每个PHY无线电的无线绑定类型。

7) capwapBaseStationTable

7) capwapBaseStationTable

The station table is used for providing stations' basic property information.

桩号表用于提供桩号的基本属性信息。

8) capwapBaseWtpEventsStatsTable

8) CapwapBasetPeventsStats表

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.

无线电事件统计表用于收集无线电重置计数、频道更改计数、硬件故障计数等。

7. Relationship to Other MIB Modules
7. 与其他MIB模块的关系
7.1. Relationship to SNMPv2-MIB Module
7.1. 与SNMPv2 MIB模块的关系

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]中定义为所有系统必需的“系统”组的对象,这些对象作为一个整体应用于实体。“系统”组提供管理实体和某些其他系统范围数据的标识。

7.2. Relationship to IF-MIB Module
7.2. 与IF-MIB模块的关系

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无线电。

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

AC上需要支持IF-MIB模块。WTP上的每个PHY无线电与AC上的WTP虚拟无线电接口相对应。WTP虚拟无线电接口提供了一种配置无线电参数和查询无线电通信统计信息的方法,并重用由其他SDO定义的无线绑定模块。接口必须建模为ifEntry,并且ifEntry对象(如ifIndex、ifDescr、ifName和ifAlias)将按照[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中ifIndex值的机制。

7.3. Relationship to ENTITY-MIB Module
7.3. 与ENTITY-MIB模块的关系

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]满足了以标准方式表示支持一个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上的ENTITY-MIB模块,它可以保存AC和WTP的固件版本和软件版本等实体信息。从ENTITY-MIB模块的角度来看,整体物理实体(AC)是多个物理实体(即连接到AC的WTP)的“复合物”,所有实体均由物理索引标识。CAPWAP-BASE-MIB模块的CAPWAPBASEWTTAPTABLE使用CAPWAPBASEWTPHYINDEX对象存储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和WTP的状态和属性。例如,他们可以通过CAPWAP-BASE-MIB模块获取WTP的当前状态,并通过ENTITY-MIB模块获取WTP的软件版本信息。CAPWAP-BASE-MIB模块不复制在ENTITY-MIB模块中定义的对象。

7.4. Relationship to Wireless Binding MIB Modules
7.4. 与无线绑定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.

AC上需要支持无线技术(如[IEEE.802-11.2007])的无线绑定MIB模块。CAPWAP-BASE-MIB模块能够支持任何无线绑定。通过WTP虚拟无线电接口的IFINDEX,它提供了一种在无线绑定MIB模块中重用MIB对象的一致和抽象的方法。CAPWAP-BASE-MIB模块不会复制无线绑定MIB模块中定义的对象。

7.5. MIB Modules Required for IMPORTS
7.5. 导入所需的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]导入对象。

8. Example of CAPWAP-BASE-MIB Module Usage
8. CAPWAP-BASE-MIB模块使用示例

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配置文件,如下所示: