draft-ietf-capwap-802dot11-mib-00.txt   draft-ietf-capwap-802dot11-mib-01.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: December 30, 2008 SNMPinfo Expires: April 14, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
P. Puneet, Ed. Y. Zhang, Ed.
Broadcom, Inc. Fortinet, Inc.
June 28, 2008 October 11, 2008
CAPWAP Protocol Binding MIB for IEEE 802.11 CAPWAP Protocol Binding MIB for IEEE 802.11
draft-ietf-capwap-802dot11-mib-00 draft-ietf-capwap-802dot11-mib-01
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 30, 2008. This Internet-Draft will expire on April 14, 2009.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless of Wireless Access Points (CAPWAP) Protocol for IEEE 802.11 wireless
binding. binding.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 6.1. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5
6.2. The capwapDot11Objects Subtree . . . . . . . . . . . . . . 5 6.2. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5
6.3. The capwapDot11Conformance Subtree . . . . . . . . . . . . 5 6.3. Brief Description of MIB Objects . . . . . . . . . . . . . 5
6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 5
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 6
7.3. Relationship to CAPWAP Base MIB . . . . . . . . . . . . . 8 7.3. Relationship to CAPWAP-BASE-MIB . . . . . . . . . . . . . 8
7.4. Relationship to IEEE 802.11 MIB . . . . . . . . . . . . . 8 7.4. Relationship to the MIBs defined in IEEE 802.11
standard and its amendments . . . . . . . . . . . . . . . 8
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8 8. Example of CAPWAP-DOT11-MIB Usage . . . . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 19 11.1. IANA Considerations for CAPWAP-DOT11-MIB . . . . . . . . . 20
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 19 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 20
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
14.1. Normative References . . . . . . . . . . . . . . . . . . . 19 14.1. Normative References . . . . . . . . . . . . . . . . . . . 20
14.2. Informative References . . . . . . . . . . . . . . . . . . 21 14.2. Informative References . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Current work is under way in the IETF to specify the CAPWAP Protocol The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines
[I-D.ietf-capwap-protocol-specification], which enables an Access a standard, interoperable protocol, which enables an Access
Controller (AC) to manage a collection of Wireless Termination Points Controller (AC) to manage a collection of Wireless Termination
(WTPs). CAPWAP supports the use of various wireless technologies by Points(WTPs). CAPWAP supports the use of various wireless
the WTPs, with one being specified in the 802.11 binding document technologies by the WTPs, with one being specified in the 802.11
[I-D.ietf-capwap-protocol-binding-ieee80211]. binding document [I-D.ietf-capwap-protocol-binding-ieee80211].
This document defines a MIB module that can be used to manage CAPWAP This document defines a MIB module that can be used to manage CAPWAP
implementations for IEEE 802.11 wireless binding. This MIB module implementations for IEEE 802.11 wireless binding. This MIB module
covers both configuration for WLAN and a way to reuse IEEE 802.11 MIB covers both configuration for WLAN and a way to reuse the MIBs
standard in series defined by IEEE 802.11 WG. defined in IEEE 802.11 standard and its amendments.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 44 skipping to change at page 3, line 44
3. Terminology 3. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the
CAPWAP Protocol specification for 802.11 binding CAPWAP Protocol specification for 802.11 binding
[I-D.ietf-capwap-protocol-binding-ieee80211]. Besides terminology [I-D.ietf-capwap-protocol-binding-ieee80211]. Besides terminology
defined in the IEEE 802.11 standard and CAPWAP specification, an defined in the IEEE 802.11 standard and CAPWAP specification, an
important conception is WLAN service. In the document, WLAN service important conception is WLAN service. In the document, WLAN service
refers to a logical component instantiated on a WTP device. A single refers to a logical component instantiated on a WTP device. A single
physical WTP may operate a number of WLAN services, and the way is physical WTP may operate a number of WLAN services, and the way is
called as virtual AP. Each Basic Service Set Identifier (BSSID) and called as virtual AP. Each Basic Service Set Identifier (BSSID) and
its constituent wireless terminal radios is denoted as a distinct its constituent wireless terminal radios are denoted as a distinct
WLAN on a physical WTP. To support physical WTP with multiple WLANs WLAN on a physical WTP. To support physical WTP with multiple WLANs
is an important feature for CAPWAP protocol's 802.11 binding, and it is an important feature for CAPWAP protocol's 802.11 binding, and it
is also for MIB design. is also for MIB design.
4. Conventions 4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
5. Overview 5. Overview
The [I-D.ietf-capwap-base-mib] provides a way to configure and manage The [I-D.ietf-capwap-base-mib] provides a way to configure and manage
WTP and radio objects through SNMP. It's a basis for manage and WTP and radio objects through SNMP. It's a basis for manage and
control a IEEE 802.11 binding. control a IEEE 802.11 binding.
The CAPWAP Protocol's IEEE 802.11 binding MIB module (CAPWAP-DOT11- The CAPWAP Protocol's IEEE 802.11 binding MIB module (CAPWAP-DOT11-
MIB) provides a way to configure WLAN service, also could easily MIB) provides a way to configure WLAN service, and it also allows to
reuse current and future IEEE 802.11 MIB standards. easily reuse current and future MIBs defined in IEEE 802.11 standard
and its amendments.
It is designed to satisfy the following requirements and constraints: It is designed to satisfy the following requirements and constraints:
- The MIB module could easily reuse current and future IEEE 802.11 - The MIB module could easily reuse current and future MIBs defined
MIB standard in series defined by IEEE 802.11 WG, and not require to in IEEE 802.11 standard and its amendments, and not require to
redefine them. redefine them.
- From AC to centrally manage and configure WLAN service; - From AC to centrally manage and configure WLAN service;
- Operators could configure MAC type and tunnel mode for a specific - Operators could configure MAC type and tunnel mode for a specific
WLAN service by SNMP; WLAN service by SNMP;
- The MIB module supports virtual AP; - The MIB module supports virtual AP;
Before coming to details of CAPWAP-MIB-DOT11 module, it will Before coming to details of CAPWAP-DOT11-MIB module, it will
introduce how it is able to reuse IEEE MIB standard. As centralized introduce how it is able to reuse IEEE MIB standard. According to
Wireless architecture, the operator has to prepare configurations for [I-D.ietf-capwap-protocol-binding-ieee80211], each WLAN service is
each wireless at AC side before WTPs connect to AC. Under identified by WLAN Id. In the MIBs defined in IEEE 802.11 standard
centralized Wireless architectures, according to [I-D.ietf-capwap- and its amendments, the MIB tables such as
protocol-specification], each WLAN service is identified by WLAN Id.
According to IEEE 802.11 MIB standards, the MIB tables such as
Dot11AuthenticationAlgorithmsTable are able to support wireless Dot11AuthenticationAlgorithmsTable are able to support wireless
configuration (such as authentication algorithm), and these tables configuration (such as authentication algorithm), and these tables
use ifIndex as index. A Wireless service could be abstracted as an use ifIndex as index. To support 802.11 parameters for a specific
interface on the AC side, and which could be identified by ifIndex. WLAN service, and consider that the operator has to prepare
On the AC side, the MIB table CapwapDot11WirelessConfigTable will configurations for each WLAN service on the AC before WTPs connect to
indicate the mapping relation between a "WLAN Id" and ifIndex of a AC, a wireless service could be abstracted as a 'WLAN Service
"WLAN Service Interface". With ifIndex of a "WLAN Service Interface' on the AC, and which could be identified by ifIndex. On
Interface", system is able to reuse IEEE MIBs. the AC, the MIB table CapwapDot11WlanConfigTable will indicate the
mapping relation between a 'WLAN Id" and ifIndex of a 'WLAN Service
Interface'. With ifIndex of a 'WLAN Service Interface', system is
able to reuse the MIBs defined in IEEE 802.11 standard and its
amendments.
6. Structure of the MIB Module 6. Structure of the MIB Module
6.1. Textual Conventions 6.1. The capwapDot11Objects Subtree
The following textual conventions are defined:
CapwapDot11WLANId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for WLAN Id."
SYNTAX Unsigned32
6.2. The capwapDot11Objects Subtree
The subtree provides information for configuration parameters of WLAN The subtree provides information for configuration parameters of WLAN
service and binding WLAN service to a specific radio. service and binding WLAN service to a specific radio.
6.3. The capwapDot11Conformance Subtree 6.2. The capwapDot11Conformance Subtree
The subtree provides conformance information of MIB objects. The subtree provides conformance information of MIB objects.
6.4. Brief Description of MIB Objects 6.3. Brief Description of MIB Objects
The MIB objects were derived from the CAPWAP protocol 802.11 binding The MIB objects were derived from the CAPWAP protocol binding for
document [I-D.ietf-capwap-protocol-binding-ieee80211]. 802.11 document [I-D.ietf-capwap-protocol-binding-ieee80211].
1) capwapDot11WLANConfigTable 1) capwapDot11WlanConfigTable
The table is used for providing configuration such as MAC type and so The table is used for providing configuration such as MAC type and so
on for WLANs. For a specific WLAN service which is identified by on for WLANs. For a specific WLAN service which is identified by
capwapDot11WLANId, an interface of 'WLAN Service Interface' ifType capwapDot11WlanId, an interface of 'WLAN Service Interface' ifType
will be created. By the ifIndex of interface, it provides a way to will be created. By the ifIndex of interface, it provides a way to
reuse IEEE 802.11 MIB. For example, according to reuse the MIBs defined in IEEE 802.11 standard and its amendments.
[I-D.ietf-capwap-protocol-binding-ieee80211], there is a TLV of For example, according to
authentication Type for a WLAN. In IEEE 802.11 MIB, the MIB object [I-D.ietf-capwap-protocol-binding-ieee80211], Auth Type needs to be
configured for a WLAN. In IEEE 802.11 MIB, the MIB object
dot11AuthenticationAlgorithm in the dot11AuthenticationAlgorithm in the
dot11AuthenticationAlgorithmsTable is corresponding to Auth Type TLV. dot11AuthenticationAlgorithmsTable is corresponding to Auth Type.
Considering both capwapDot11WLANConfigTable and Considering both capwapDot11WlanConfigTable and
dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP- dot11AuthenticationAlgorithmsTable use ifIndex as index, CAPWAP-
DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm DOT11-MIB are able to easily reuse dot11AuthenticationAlgorithm
object in IEEE 802.11 MIB. It is same for other IEEE 802.11 MIBs' object in IEEE 802.11 MIB. It is same for other objects in the MIBs
reuse. defined in IEEE 802.11 standard and its amendments.
2) capwapDot11WLANBindTable 2) capwapDot11WlanBindTable
The table provides a way to bind WLAN service to a radio, then The table provides a way to bind WLAN service to a radio, then
support virtual AP. The binding operation will dynamically create supports virtual AP. The binding operation will dynamically create
"WLAN BSS Interface", and this logical interface is used for data 'WLAN BSS Interface', and this logical interface is used for data
forwarding function. forwarding function.
7. Relationship to Other MIB Modules 7. Relationship to Other MIB Modules
7.1. Relationship to the SNMPv2-MIB 7.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The CAPWAP-DOT11-MIB does entity and certain other system-wide data. The CAPWAP-DOT11-MIB does
not duplicate those objects. not duplicate those objects.
7.2. Relationship to the IF-MIB 7.2. Relationship to the IF-MIB
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing WLAN service that are extensions to the Interfaces Group for managing WLAN service that are
modeled as interfaces. modeled as interfaces.
For each WLAN, it will have a logical interface of 'WLAN Service For each WLAN, it will have a logical interface of 'WLAN Service
Interface' responding to it at AC side. The interface SHOULD be Interface' responding to it on the AC. The interface SHOULD be
modeled as an ifEntry and provide appropriate interface information. modeled as an ifEntry and provide appropriate interface information.
'WLAN Service Interface' provides a way to configure IEEE 802.11
parameters for a specific WLAN service, and reuse the MIBs defined in
IEEE 802.11 standard and its amendments.
To provide data forwarding service, system will dynamically create To provide data forwarding service, system will dynamically create
logical interface of 'WLAN BSS Interface'. The interface SHOULD be logical interface of 'WLAN BSS Interface'. The interface SHOULD be
modeled as an ifEntry and provide appropriate interface information. modeled as an ifEntry and provide appropriate interface information.
The interface enables the virtual AP function.
Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as Some specific interpretations of ifTable for CAPWAP-DOT11-MIB are as
follow. follow.
1) WLAN Service Interface 1) WLAN Service Interface
Object Use for the CAPWAP-DOT11-MIB Object Use for the CAPWAP-DOT11-MIB
ifIndex Each interface of 'WLAN Service Interface' type ifIndex Each interface of 'WLAN Service Interface' type
maybe be represented by an ifEntry. maybe be represented by an ifEntry.
ifDescr Description of the interface of 'WLAN Service ifDescr Description of the interface of 'WLAN Service
Interface' type. Interface' type.
ifType IANAifType of "WLAN Service Interface". ifType IANAifType of 'WLAN Service Interface'.
ifName Textual name (unique on this system) of the interface ifName Textual name (unique on this system) of the interface
or an octet string of zero length. or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager. specified by a network manager.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus This variable indicates the administrator's intent as ifAdminStatus This variable indicates the administrator's intent as
skipping to change at page 7, line 27 skipping to change at page 7, line 24
2) WLAN BSS Interface 2) WLAN BSS Interface
Object Use for the CAPWAP-DOT11-MIB Object Use for the CAPWAP-DOT11-MIB
ifIndex Each interface of 'WLAN BSS Interface' type maybe ifIndex Each interface of 'WLAN BSS Interface' type maybe
be represented by an ifEntry. be represented by an ifEntry.
ifDescr Description of the interface of 'WLAN BSS Interface' ifDescr Description of the interface of 'WLAN BSS Interface'
type. type.
ifType IANAifType of "WLAN BSS Interface". ifType IANAifType of 'WLAN BSS Interface'.
ifName Textual name (unique on this system) of the interface ifName Textual name (unique on this system) of the interface
or an octet string of zero length. or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager. specified by a network manager.
ifPhysAddress The physical address of interface. ifPhysAddress The physical address of interface, i.e. WTP assigned
One possible method is for the WTP to assign the BSSID.
address for 'WLAN BSS Interface' using the following
algorithm: base BSSID address + WLAN ID.
ifAdminStatus This variable indicates the administrator's intent as ifAdminStatus This variable indicates the administrator's intent as
to whether PHY should be enabled, disabled, or to whether PHY should be enabled, disabled, or
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. interface.
Also see [RFC2863]. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational status ifOperStatus This value reflects the actual or operational status
of interface. of interface.
Also see [RFC2863]. Also see [RFC2863].
skipping to change at page 8, line 4 skipping to change at page 7, line 47
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. interface.
Also see [RFC2863]. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational status ifOperStatus This value reflects the actual or operational status
of interface. of interface.
Also see [RFC2863]. Also see [RFC2863].
ifLastChange The value of sysUpTime at the time the interface ifLastChange The value of sysUpTime at the time the interface
entered its current operational state. entered its current operational state.
Also see [RFC2863]. Also see [RFC2863].
ifInOctets The number of octets received as 802.11 frames. ifInOctets The number of octets received as IEEE 802.11 frames.
ifOutOctets The number of octets transmitted as 802.11 ifOutOctets The number of octets transmitted as IEEE 802.11
frames. frames.
ifInErrors The number of 802.11 frames dropped due to ifInErrors The number of inbound IEEE 802.11 frames dropped due
uncorrectable errors. to uncorrectable errors.
ifInUnknownProtos ifInUnknownProtos
The number of received 802.11 frame discarded during The number of received IEEE 802.11 frame discarded
frame header validation, including frames with during frame header validation, including frames with
unrecognized label values. unrecognized label values.
ifOutErrors See [RFC2863]. ifOutErrors The number of outbound IEEE 802.11 frames dropped due
to uncorrectable errors.
7.3. Relationship to CAPWAP Base MIB 7.3. Relationship to CAPWAP-BASE-MIB
The CAPWAP Base MIB provides a way to manage and control WTP and The CAPWAP-BASE-MIB provides a way to manage and control WTP and
radio objects. Based on it, CAPWAP-DOT11-MIB provides more radio objects. Especially, CAPWAP-BASE-MIB has a mechanism of 'WTP
information from WLAN service perspective. Virtual Radio Interface' which enable system to reuse the MIBs
defined in IEEE 802.11 standard and its amendments. With it,
administrator could configure an IEEE 802.11 AP radio's parameter and
query radio's traffic statistics. Based on CAPWAP-BASE-MIB, CAPWAP-
DOT11-MIB provides more information from WLAN service perspective.
7.4. Relationship to IEEE 802.11 MIB 7.4. Relationship to the MIBs defined in IEEE 802.11 standard and its
amendments
Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface' Through ifIndex of 'WLAN Service Interface' and 'WLAN BSS Interface'
ifType, the MIB module is able to reuse MIB objects in the IEEE ifType, the MIB module is able to reuse MIB objects in the MIBs
802.11 MIB. defined in IEEE 802.11 standard and its amendments.
In the 802.11 binding document [I-D.ietf-capwap-protocol-binding-
ieee80211], it involves a part of MIB objects defined by IEEE 802.11
standard and its amendments. Although CAPWAP-DOT11-MIB uses the
802.11 binding document as a reference, it could reuse all the MIB
objects defined by IEEE 802.11 standard and its amendments , and not
limited by the scope of the 802.11 binding document.
7.5. MIB modules required for IMPORTS 7.5. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], The following MIB modules are required for IMPORTS: SNMPv2-SMI
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
CAPWAP-MIB [I-D.ietf-capwap-base-mib]. [RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib].
8. Example of CAPWAP-DOT11-MIB Usage 8. Example of CAPWAP-DOT11-MIB Usage
Combining the example in the [I-D.ietf-capwap-base-mib], In the CAPWAP-BASE-MIB, each PHY radio is identified by WTP Id and
here give a whole example for configuration and management of WTP, radio ID, and which has a corresponding 'WTP Virtual Radio Interface'
radio and WLAN object. on the AC. The IEEE 802.11 MIB associated with this interface
can be used to configure IEEE 802.11 wireless binding parameters for
radio such as RTS Threshold.
1) Identify each PHY radio by "WTP Virtual Radio Interface" In the CAPWAP 802.11 Binding MIB, each WLAN service is identified
by WLAN Id, and which has a corresponding 'WLAN Service Interface'
on the AC. The MIBs defined in IEEE 802.11 standard and its
amendments associated with this interface can be used to configure
WLAN parameters for a WLAN service, such as Authentication Algorithm.
The 'WLAN BSS Interface', created by binding 'WTP Virtual Radio
Interface' and 'WLAN Service Interface', is used for data forwarding.
Combining the example provided in the [I-D.ietf-capwap-base-mib],
the following is a whole example for configuration and management of
WTP, radio and WLAN service for IEEE 802.11 binding.
1) Identify each PHY radio by 'WTP Virtual Radio Interface'
According to [I-D.ietf-capwap-protocol-specification], each radio on According to [I-D.ietf-capwap-protocol-specification], each radio on
a WTP will be identified by a radio Id. Each WTP could be identified a WTP will be identified by a radio Id. Each WTP could be identified
by its serial number. by its serial number.
When configuration for a WTP is prepared before a WTP connects to AC, When configuration for a WTP is prepared before a WTP connects to AC,
the following information is available in the CapwapRadioBindTable. the following information is available in the
In CapwapRadioBindTable CapwapBaseRadioBindTable.
In CapwapBaseRadioBindTable
{ {
capwapWTPId = 12345678 capwapBaseWTPId = 12345678,
capwapRadioId = 1 capwapBaseRadioId = 1,
capwapWTPVirtualRadioifIndex = 10, capwapBaseWtpVirtualRadioifIndex = 10,
capwapWirelessBinding = dot11(2), capwapBaseWirelessBinding = dot11(2)
} }
Suppose WTP's serial number is 12345678, and first PHY radio's id Suppose WTP's serial number is 12345678, and first PHY radio's id
is 1. At AC side, the ifIndex of "WTP Virtual Radio Interface" is is 1. On the AC, the ifIndex of 'WTP Virtual Radio Interface' is
10 which represents the PHY radio 1. 10 which represents the PHY radio 1.
By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP By the mechanism of 'WTP Virtual Radio Interface', it seemed that WTP
PHY radios are located at AC side. PHY radios are located on the AC.
The interface of "WTP Virtual Radio Interface" is modeled by ifTable. The interface of 'WTP Virtual Radio Interface' is modeled by ifTable.
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = "WTP Virtual Radio Interface", ifDescr = 'WTP Virtual Radio Interface',
ifType = IANAifType of "WTP Virtual Radio ifType = IANAifType of 'WTP Virtual Radio
Interface", Interface',
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0, ifPhysAddress = 0.0.0.0.0.0,
ifAdminStatus = true, ifAdminStatus = true,
ifOperStatus = false, ifOperStatus = false,
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0, ifOutErrors = 0
} }
2) Configure IEEE 802.11 wireless binding parameters for "WTP Virtual 2) Configure IEEE 802.11 wireless binding parameters for 'WTP Virtual
Radio Interface" Radio Interface'
It will be done at the AC side through IEEE 802.11 MIB. It will be done on the AC through the MIBs defined in IEEE 802.11
For example, to configure parameter for "WTP Virtual Radio Interface" standard and its amendments.
For example, to configure parameter for 'WTP Virtual Radio Interface'
by IEEE 802.11 Dot11OperationTable. by IEEE 802.11 Dot11OperationTable.
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = 0.0.0.0.0.0,
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
skipping to change at page 10, line 6 skipping to change at page 10, line 31
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = 0.0.0.0.0.0,
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = "capwap", dot11ManufacturerID = 'capwap',
dot11ProductID = "capwap" dot11ProductID = 'capwap'
} }
In the example, it supposes ifIndex of a "WTP Virtual Radio
Interface" is 10. In the example, it supposes ifIndex of a 'WTP Virtual Radio
Interface' is 10.
3) Configure WLAN service 3) Configure WLAN service
WLAN service configuration will be done through CAPWAP-DOT11-MIB
and IEEE 802.11 MIB. WLAN service configuration will be done through CAPWAP-DOT11-MIB,
First step is to create a "WLAN Service Interface" through and the MIBs defined in IEEE 802.11 standard and its amendments.
CAPWAP-DOT11-MIB at AC side.
In CapwapDot11WLANConfigTable First step is to create a 'WLAN Service Interface' through
CAPWAP-DOT11-MIB on the AC.
In CapwapDot11WlanConfigTable
{ {
capwapDot11WLANId = 1, capwapDot11WlanId = 1,
capwapDot11WLANServiceIfIndex = 20, capwapDot11WlanServiceIfIndex = 20,
capwapWTPMACType = splitMAC(2), capwapDot11WlanMacType = splitMAC(2),
capwapWTPTunnelMode = dot3Tunnel, capwapDot11WlanTunnelMode = dot3Tunnel(2),
capwapDot11WLANConfigRowStatus = create capwapDot11WlanConfigRowStatus = create
} }
Here supposes to configure a WLAN service which is identified by Here supposes to configure a WLAN service which is identified by
capwapDot11WLANId 1. A "WLAN Service Interface" is created for it capwapDot11WlanId 1. A 'WLAN Service Interface' is created
and identified by ifIndex 20. for it and identified by ifIndex 20.
Corresponding to "WLAN Service Interface", it SHOULD be modeled as an Corresponding to 'WLAN Service Interface', it SHOULD be modeled as an
ifEntry at AC side and provide appropriate interface information. ifEntry on the AC and provide appropriate interface information.
In ifTable In ifTable
{ {
ifIndex = 20, ifIndex = 20,
ifDescr = "WLAN Service Interface", ifDescr = 'WLAN Service Interface',
ifType = IANAifType of "WLAN Service Interface", ifType = IANAifType of 'WLAN Service Interface',
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0, ifPhysAddress = 0.0.0.0.0.0,
ifAdminStatus = true, ifAdminStatus = true,
ifOperStatus = true, ifOperStatus = true,
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0 ifOutErrors = 0
} }
Second step is to configure WLAN parameters of "WLAN Service
Interface" through IEEE 802.11 MIB at AC side. Second step is to configure WLAN parameters of 'WLAN Service
Interface' through the MIBs defined in IEEE 802.11 standard and
its amendments on the AC.
In Dot11AuthenticationAlgorithmsTable In Dot11AuthenticationAlgorithmsTable
{ {
ifIndex = 20, ifIndex = 20,
dot11AuthenticationAlgorithmsIndex = 1, dot11AuthenticationAlgorithmsIndex = 1,
dot11AuthenticationAlgorithm = Shared Key, dot11AuthenticationAlgorithm = Shared Key,
dot11AuthenticationAlgorithmsEnable = true dot11AuthenticationAlgorithmsEnable = true
} }
Here ifIndex 20 is for interface of "WLAN Service Interface"
Here ifIndex 20 is for interface of 'WLAN Service Interface'
ifType. Suppose the index of authentication algorithm is 1. ifType. Suppose the index of authentication algorithm is 1.
4) Bind WLAN service to WTP radio 4) Bind WLAN service to WTP radio
At AC side, through CapwapDot11WLANBindTable, it configures which On the AC, through CapwapDot11WlanBindTable, it configures which
WLAN service (identified by capwapDot11WLANId) will be provided on WLAN service (identified by capwapDot11WlanId) will be provided
which radio (identified by ifIndex). Suppose capwapWTPMACType of WLAN on which radio (identified by ifIndex).
service is splitMAC(2), the interface of 'WLAN BSS Interface' Suppose capwapDot11WlanMacType of WLAN service is splitMAC(2),
will be created at AC side. the interface of 'WLAN BSS Interface' will be created on the AC.
The AC will use it for split data forwarding. Here supposes ifIndex The AC will use it for split data forwarding. Here supposes ifIndex
of interface in 'WLAN BSS Interface' ifType is 30. of interface in 'WLAN BSS Interface' ifType is 30.
In CapwapDot11WLANBindTable
In CapwapDot11WlanBindTable
{ {
ifIndex = 10, ifIndex = 10,
capwapDot11WLANId = 1, capwapDot11WlanId = 1,
capwapDot11WLANBSSIfIndex = 30, capwapDot11WlanBssIfIndex = 30,
capwapDot11WLANBSSRowStatus = create capwapDot11WlanBssRowStatus = create
} }
5) WTP reports its current configuration status 5) WTP reports its current configuration status
After join phase and before WTP get configuration from AC, it will After join phase and before WTP get configuration from AC, it will
report its current configuration status to AC through configuration report its current configuration status to AC through configuration
status message. The MIB data will be updated at AC side. status request message. The MIB data will be updated on the AC.
For example, for the 802.11 binding, WTP will update data in the As an example, for ifIndex 10 (which identifies an interface of 'WLAN
ifTable and IEEE 802.11 MIB so on according to message content. Virtual Radio Interface' ifType), its ifOperStatus in ifTable will
As a example for ifIndex 10 (which identify an interface of be updated with current radio operational status.
"WLAN Virtual Radio Interface" ifType), its ifOperStatus in ifTable
will be updated with current radio operational status in the message.
6) Query WTP and radio statistics data 6) Query WTP and radio statistics data
After WTPs come to run status, administrator could query WTP and After WTPs come to run status, administrator could query WTP and
radio statistics data through CAPWAP-MIB and CAPWAP-DOT11-MIB. radio statistics data through CAPWAP-BASE-MIB and CAPWAP-DOT11-MIB.
For example, through dot11CountersTable in the IEEE 802.11 MIB, For example, through dot11CountersTable in the IEEE 802.11 MIB,
administrator could query counter data for radio which is identified administrator could query counter data for radio which is identified
by ifIndex of a "WLAN Virtual Radio Interface". by ifIndex of a 'WLAN Virtual Radio Interface'.
7) Query other statistics data 7) Query other statistics data
For example, administrator could query the configuration of
WLAN service through Dot11AuthenticationAlgorithmsTable.
Query statistic data of 'WLAN BSS Interface' through ifTable; For example, administrator could query the configuration of
WLAN service through Dot11AuthenticationAlgorithmsTable and statistic
data of 'WLAN BSS Interface' through ifTable;
9. Definitions 9. Definitions
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
RowStatus, TEXTUAL-CONVENTION RowStatus, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB FROM IF-MIB
CapwapWTPMACType, CapwapWTPTunnelMode CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC
FROM CAPWAP-MIB; FROM CAPWAP-BASE-MIB;
capwapDot11MIB MODULE-IDENTITY capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "200806280000Z" -- June 28, 2008 LAST-UPDATED "200810110000Z" -- Oct 11th, 2008
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085) District,Beijing,China(100085)
Email: young@h3c.com Email: young@h3c.com
David T. Perkins David T. Perkins
228 Bayview Dr 228 Bayview Dr
San Carlos, CA 94070 San Carlos, CA 94070
skipping to change at page 13, line 4 skipping to change at page 13, line 38
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709 Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
Email: chelliot@cisco.com Email: chelliot@cisco.com
Puneet Agarwal
BroadCom, Inc. Yong Zhang
Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA USA
Email: pagarwal@broadcom.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2008 The Internet Society. This version of "Copyright (C) 2008 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the IEEE 802.11 bindings for the CAPWAP Protocol." the IEEE 802.11 bindings for the CAPWAP Protocol."
REVISION "200806280000Z" REVISION "200810110000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxx" "Initial version, published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual conventions -- Textual conventions
CapwapDot11WLANId ::= TEXTUAL-CONVENTION CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the TC for WLAN Id." "Represents an unique identifier of a WLAN."
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..16)
-- Top level components of this MIB -- Top level components of this MIB
-- Tables, Scalars -- Tables, Scalars
capwapDot11Objects OBJECT IDENTIFIER capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 } ::= { capwapDot11MIB 1 }
-- Conformance -- Conformance
capwapDot11Conformance OBJECT IDENTIFIER capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 } ::= { capwapDot11MIB 2 }
-- capwapDot11WlanConfigTable Table
capwapDot11WLANConfigTable OBJECT-TYPE capwapDot11WlanConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WLANConfigEntry SYNTAX SEQUENCE OF CapwapDot11WlanConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display and control the WLAN "A table of objects that display and control the WLAN
service." service.
Values of all read-create objects in this
table are persistent at restart/reboot."
::= { capwapDot11Objects 1 } ::= { capwapDot11Objects 1 }
capwapDot11WLANConfigEntry OBJECT-TYPE capwapDot11WlanConfigEntry OBJECT-TYPE
SYNTAX CapwapDot11WLANConfigEntry SYNTAX CapwapDot11WlanConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display and control the WLAN "A set of objects that display and control the WLAN
service." service."
INDEX { capwapDot11WLANId } INDEX { capwapDot11WlanId }
::= { capwapDot11WLANConfigTable 1 } ::= { capwapDot11WlanConfigTable 1 }
CapwapDot11WLANConfigEntry ::= CapwapDot11WlanConfigEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WLANId CapwapDot11WLANId, capwapDot11WlanId CapwapDot11WlanIdTC,
capwapDot11WLANServiceIfIndex InterfaceIndex, capwapDot11WlanServiceIfIndex InterfaceIndex,
capwapWTPMACType CapwapWTPMACType, capwapDot11WlanMacType CapwapBaseMacTypeTC,
capwapWTPTunnelMode CapwapWTPTunnelMode, capwapDot11WlanTunnelMode CapwapBaseTunnelModeTC,
capwapDot11WLANConfigRowStatus RowStatus capwapDot11WlanConfigRowStatus RowStatus
} }
capwapDot11WLANId OBJECT-TYPE capwapDot11WlanId OBJECT-TYPE
SYNTAX CapwapDot11WLANId SYNTAX CapwapDot11WlanIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WLAN id for a WLAN which has a "Represents the WLAN Id for a WLAN which has a
capwapDot11WLANServiceIfIndex interface corresponding to it." capwapDot11WlanServiceIfIndex interface corresponding to it."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx." RFC xxx."
::= { capwapDot11WLANConfigEntry 1 } ::= { capwapDot11WlanConfigEntry 1 }
capwapDot11WLANServiceIfIndex OBJECT-TYPE capwapDot11WlanServiceIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the ifIndex for an interface of 'WLAN Service "Represents the index value that uniquely identifies a
Interface' ifType. 'WLAN Service Interface'. The interface identified by a
particular value of this index is the same interface as
identified by the same value of ifIndex.
Before WTPs connect to AC and get configuration, administrator Before WTPs connect to AC and get configuration, administrator
will prepare configuration for them. For a specific WLAN will prepare configuration for them. For a specific WLAN
service, a logical interface of 'WLAN Service Interface' ifType service, a logical interface of 'WLAN Service Interface'
will be created, and administrator could configure WLAN ifType will be created, and administrator could configure WLAN
parameter through it. For example, according to IEEE 802.11 parameter through it. For example, according to IEEE 802.11
'6.1. IEEE 802.11 Add WLAN' in the '6.1. IEEE 802.11 Add WLAN' in the
[I-D.ietf-capwap-protocol-binding-ieee80211], administrator [I-D.ietf-capwap-protocol-binding-ieee80211], administrator
could configure specify Auth Type for a WLAN. The 'WLAN Service could configure Auth Type for a WLAN. The 'WLAN
Interface' provides a way to uniquely identify each WLAN by Service Interface' provides a way to uniquely identify each
logical at AC side. As most MIBs use ifIndex to identify an WLAN by logical on the AC. As most MIBs use ifIndex to
interface for configuration and statistic data, for example, identify an interface for configuration and statistic data,
dot11AuthenticationAlgorithmsTable in 802.11 MIB use ifIndex for example, dot11AuthenticationAlgorithmsTable in IEEE 802.11
as index, and dot11AuthenticationAlgorithm object is for MIB use ifIndex as index, and dot11AuthenticationAlgorithm
Auth Type mentioned in the CAPWAP '6.1. IEEE 802.11 Add WLAN', object is for Auth Type mentioned in the CAPWAP '6.1. IEEE
With the way of 'WLAN Service Interface', it will easily 802.11 Add WLAN', With the way of 'WLAN Service Interface',
reuse MIB table like dot11AuthenticationAlgorithmsTable, while it will easily reuse MIB table like
only care for other configurations like capwapWTPTunnelMode." dot11AuthenticationAlgorithmsTable, while only care for other
::= { capwapDot11WLANConfigEntry 2 } configurations like capwapDot11WlanTunnelMode."
::= { capwapDot11WlanConfigEntry 2 }
capwapWTPMACType OBJECT-TYPE capwapDot11WlanMacType OBJECT-TYPE
SYNTAX CapwapWTPMACType SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the WTP should run the WLAN in "Represents whether the WTP should support the WLAN in
Local or Split MAC modes." Local or Split MAC modes."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx." RFC xxx."
::= { capwapDot11WLANConfigEntry 3 } ::= { capwapDot11WlanConfigEntry 3 }
capwapWTPTunnelMode OBJECT-TYPE capwapDot11WlanTunnelMode OBJECT-TYPE
SYNTAX CapwapWTPTunnelMode SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the frame tunneling type to be used for 802.11 data "Represents the frame tunneling type to be used for 802.11 data
frames from all stations associated with the WLAN." frames from all stations associated with the WLAN.
Bits are exclusive with each other for a specific WLAN Id."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx." RFC xxx."
::= { capwapDot11WLANConfigEntry 4 } ::= { capwapDot11WlanConfigEntry 4 }
capwapDot11WLANConfigRowStatus OBJECT-TYPE capwapDot11WlanConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row in "This variable is used to create, modify, and/or delete a row in
this table." this table."
::= { capwapDot11WLANConfigEntry 5 } ::= { capwapDot11WlanConfigEntry 5 }
-- End of capwapDot11WlanConfigTable Table
-- capwapDot11WlanBindTable Table
capwapDot11WLANBindTable OBJECT-TYPE capwapDot11WlanBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WLANBindEntry SYNTAX SEQUENCE OF CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display the mapping relationship "A table of objects that display and control the mapping
between interface of 'WTP Virtual Radio Interface' and relationship between interface of 'WTP Virtual Radio Interface'
interface of 'WLAN BSS Interface'. interface and interface of 'WLAN BSS Interface'.
The PHY address for interface of 'WTP Virtual Radio The PHY address for interface of 'WTP Virtual Radio
Interface' ifType will be base BSSID address for PHY Interface' ifType will be base BSSID address for PHY
radio." radio."
REFERENCE REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11, "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx." RFC xxx."
::= { capwapDot11Objects 2 } ::= { capwapDot11Objects 2 }
capwapDot11WLANBindEntry OBJECT-TYPE capwapDot11WlanBindEntry OBJECT-TYPE
SYNTAX CapwapDot11WLANBindEntry SYNTAX CapwapDot11WlanBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the mapping relationship "A set of objects that display the mapping relationship
between interface of 'WTP Virtual Radio Interface' and between interface of 'WTP Virtual Radio Interface' and
interface of 'WLAN BSS Interface'." interface of 'WLAN BSS Interface'."
INDEX { ifIndex, capwapDot11WLANId } INDEX { ifIndex, capwapDot11WlanId }
::= { capwapDot11WLANBindTable 1 } ::= { capwapDot11WlanBindTable 1 }
CapwapDot11WLANBindEntry ::= CapwapDot11WlanBindEntry ::=
SEQUENCE { SEQUENCE {
capwapDot11WLANBSSIfIndex InterfaceIndex, capwapDot11WlanBssIfIndex InterfaceIndex,
capwapDot11WLANBSSRowStatus RowStatus capwapDot11WlanBssRowStatus RowStatus
} }
capwapDot11WLANBSSIfIndex OBJECT-TYPE capwapDot11WlanBssIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a ifIndex for an interface of "Represents the index value that uniquely identifies a
'WLAN BSS Interface' ifType. Each capwapDot11WLANBSSIfIndex will 'WLAN BSS Interface'. The interface identified by a
corresponding to a WLAN service on the PHY radio which is particular value of this index is the same interface as
identified by ifIndex. identified by the same value of ifIndex.
When CapwapWTPMACType is localMAC(1), the interface of Each capwapDot11WlanBssIfIndex will corresponding to a
'WLAN BSS Interface' will be created at AP side. WLAN service on the PHY radio which is identified by ifIndex.
The AP will use interface for local data forwarding. The PHY address for capwapDot11WlanBssIfIndex is BSSID.
When CapwapWTPMACType is splitMAC(2), the interface of
'WLAN BSS Interface' will be created at AC side.
The AC will use it for split data forwarding.
The PHY address for capwapDot11WLANBSSIfIndex is BSSID.
While manufacturers are free to assign BSSIDs using any While manufacturers are free to assign BSSIDs using any
arbitrary mechanism, it is advised that where possible the arbitrary mechanism, it is advised that where possible the
BSSIDs are assigned as a contiguous block. BSSIDs are assigned as a contiguous block.
When assigned as a block, implementations can still assign When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following is for the WTP to assign the address using the following
algorithm: base BSSID address + WLAN ID." algorithm: base BSSID address + WLAN ID."
REFERENCE REFERENCE
"Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11, "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx." RFC xxx."
::= { capwapDot11WLANBindEntry 1 } ::= { capwapDot11WlanBindEntry 1 }
capwapDot11WLANBSSRowStatus OBJECT-TYPE capwapDot11WlanBssRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row in "This variable is used to create, modify, and/or delete a row
this table." in this table."
::= { capwapDot11WLANBindEntry 2 } ::= { capwapDot11WlanBindEntry 2 }
-- Module compliance -- Module compliance
capwapDot11Groups OBJECT IDENTIFIER capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 } ::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 } ::= { capwapDot11Conformance 2 }
capwapDot11Compliance MODULE-COMPLIANCE capwapDot11Compliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
CAPWAP Dot11 MIB." CAPWAP-DOT11-MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { capwapDot11WLANConfigGroup, MANDATORY-GROUPS { capwapDot11WlanConfigGroup,
capwapDot11WLANBindGroup } capwapDot11WlanBindGroup }
::= { capwapDot11Compliances 1 } ::= { capwapDot11Compliances 1 }
capwapDot11WLANConfigGroup OBJECT-GROUP capwapDot11WlanConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WLANId, capwapDot11WlanServiceIfIndex,
capwapDot11WLANServiceIfIndex, capwapDot11WlanMacType,
capwapWTPMACType, capwapDot11WlanTunnelMode,
capwapWTPTunnelMode, capwapDot11WlanConfigRowStatus
capwapDot11WLANConfigRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "The collection of objects which are used to configure
property of WLAN." property of WLAN."
::= { capwapDot11Groups 1 } ::= { capwapDot11Groups 1 }
capwapDot11WLANBindGroup OBJECT-GROUP capwapDot11WlanBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDot11WLANBSSIfIndex, capwapDot11WlanBssIfIndex,
capwapDot11WLANBSSRowStatus capwapDot11WlanBssRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "The collection of objects which are used to configure
WLAN BSS." WLAN BSS."
::= { capwapDot11Groups 2 } ::= { capwapDot11Groups 2 }
END END
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. The followings are the tables and objects and
sensitivity/vulnerability: their sensitivity/vulnerability:
o - Unauthorized changes to the capwapDot11WLANConfigTable and o - Unauthorized changes to the capwapDot11WlanConfigTable and
capwapDot11WLANBindTable may disrupt allocation of resources in capwapDot11WlanBindTable may disrupt allocation of resources in
the network, also change the behavior of WLAN system such as MAC the network, also change the behavior of WLAN system such as MAC
type. type.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
skipping to change at page 20, line 46 skipping to change at page 21, line 36
December 2002. December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D.,
Elliott, C., and P. Elliott, C., and P.
Agarwal, "CAPWAP Agarwal, "CAPWAP
Protocol Base MIB", dra Protocol Base MIB", dra
ft-ietf-capwap-base- ft-ietf-capwap-base-
mib-00 (work in mib-00 (work in
progress), May 2008. progress), May 2008.
[I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP [I-D.ietf-capwap-protocol-specification] Montemurro, M.,
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol Protocol
Specification", draft- Specification", draft-
ietf-capwap-protocol- ietf-capwap-protocol-
specification-10 (work specification-13 (work
in progress), in progress),
March 2008. September 2008.
[I-D.ietf-capwap-protocol-binding-ieee80211] Calhoun, P., "CAPWAP [I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M.,
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol Binding for Protocol Binding for
IEEE 802.11", draft- IEEE 802.11", draft-
ietf-capwap-protocol- ietf-capwap-protocol-
binding-ieee80211-06 binding-ieee80211-10
(work in progress), (work in progress),
February 2008. September 2008.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., [RFC3410] Case, J., Mundy, R.,
Partain, D., and B. Partain, D., and B.
Stewart, "Introduction Stewart, "Introduction
and Applicability and Applicability
Statements for Statements for
Internet-Standard Internet-Standard
Management Framework", Management Framework",
skipping to change at page 22, line 4 skipping to change at page 22, line 39
EMail: young@h3c.com EMail: young@h3c.com
David Perkins (editor) David Perkins (editor)
SNMPinfo SNMPinfo
288 Quailbrook Ct San Carlos, 288 Quailbrook Ct San Carlos,
CA 94070 CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com EMail: dperkins@snmpinfo.com
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park
27709 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
EMail: chelliot@cisco.com EMail: chelliot@cisco.com
Yong Zhang (editor)
Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA
Puneet Agarwal (editor) EMail: yzhang@fortinet.com
Broadcom, Inc.
EMail: pagarwal@broadcom.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 133 change blocks. 
274 lines changed or deleted 326 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/