draft-ietf-capwap-base-mib-03.txt   draft-ietf-capwap-base-mib-04.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: May 5, 2009 SNMPinfo Expires: September 1, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
November 1, 2008 February 28, 2009
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-03 draft-ietf-capwap-base-mib-04
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 May 5, 2009. This Internet-Draft will expire on September 1, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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. of Wireless Access Points (CAPWAP) Protocol.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5
6.1. The capwapBaseObjects Subtree . . . . . . . . . . . . . . 6 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5
6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5
6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6
6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 8
7.4. Relationship to MIB standards of other SDOs . . . . . . . 9 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 8
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9
8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 9
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10
9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12
9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 12 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 13
9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 15 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 16
9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 15 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 16
9.3.1. Configuration Status Response Message . . . . . . . . 15 9.3.1. Configuration Status Response Message . . . . . . . . 16
9.3.2. Configuration Update Response Message . . . . . . . . 16 9.3.2. Configuration Update Response Message . . . . . . . . 17
10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 17
11. Security Considerations . . . . . . . . . . . . . . . . . . . 64 11. Security Considerations . . . . . . . . . . . . . . . . . . . 65
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67
12.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 65 12.1. IANA Considerations for CAPWAP-BASE-MIB module . . . . . . 67
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 65 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 67
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 65 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 67
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67
15.1. Normative References . . . . . . . . . . . . . . . . . . . 66 15.1. Normative References . . . . . . . . . . . . . . . . . . . 67
15.2. Informative References . . . . . . . . . . . . . . . . . . 67 15.2. Informative References . . . . . . . . . . . . . . . . . . 69
Appendix A. Appendix A. Changes from -02 . . . . . . . . . . . . 67 Appendix A. Appendix A. Changes between -04 and -03 . . . . . . . 71
1. Introduction 1. Introduction
The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines
a standard, interoperable protocol, which enables an Access a standard, interoperable protocol, which enables an Access
Controller (AC) to manage a collection of Wireless Termination Controller (AC) to manage a collection of Wireless Termination
Points(WTPs) Points(WTPs).
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. This MIB module covers both configuration and WTP implementations. This MIB module covers both configuration and WTP
status-monitoring aspects of CAPWAP, and provides a way to reuse status-monitoring aspects of CAPWAP, and provides a way to reuse MIB
current MIB standards and future extensions for any wireless binding modules for any wireless technology.
technology.
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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Terminology 3. Terminology
This document uses terminology from the document describing the This document uses terminology from the CAPWAP Protocol specification
CAPWAP Protocol specification [I-D.ietf-capwap-protocol- [I-D.ietf-capwap-protocol-specification] and the Architecture
specification]. WTPs are viewed as remote RF interfaces controlled Taxonomy for CAPWAP [RFC4118].
by the AC via CAPWAP protocol. The CAPWAP protocol supports two
modes of operation: Split and Local MAC. In Split MAC mode all L2 Access Controller (AC): The network entity that provides WTP access
wireless data and management frames are encapsulated via the CAPWAP to the network infrastructure in the data plane, control plane,
protocol and exchanged between the AC and the WTPs. The Local MAC management plane, or a combination therein.
mode of operation allows for the data frames to be either locally
bridged, or tunneled as 802.3 frames. From AC, operator could Wireless Termination Point (WTP): The physical or network entity that
centrally control WTPs configuration and monitor their status. contains an RF antenna and wireless PHY to transmit and receive
CAPWAP use DTLS protocol to implement control channel security. station traffic for wireless access networks.
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 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 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.
Station (STA): A device that contains an interface to a wireless
medium (WM).
Split and Local MAC: The CAPWAP protocol supports two modes of
operation: Split and Local MAC. In Split MAC mode all L2 wireless
data and management frames are encapsulated via the CAPWAP protocol
and exchanged between the AC and the WTPs. The Local MAC mode of
operation allows for the data frames to be either locally bridged, or
tunneled as 802.3 frames.
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 defining a binding protocol for it, e.g.,
the binding for IEEE 802.11, provided in
[I-D.ietf-capwap-protocol-binding-ieee80211].
Autonomous WLAN Architecture: It is the traditional autonomous WLAN
architecture, in which each WTP is a single physical device that
implements all the wireless services.
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.
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 CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) have the following 5.1. Requirements and Constraints
design objectives:
- To implement an architecture that uses SNMP for the management and The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to
control of wireless networks, answering the operators requirements satisfy the following requirements and constraints:
for centralized management, whatever the deployment or configuration
of the network devices (centralized, distributed, or some mix)
- To be consistent with CAPWAP protocol - From AC to centrally manage and monitor WTPs;
- To reuse current MIB standards and future extensions for a wireless - Supports CAPWAP protocol parameters queries;
binding technology
- To enable interoperability between vendors - Supports showing WTPs current state;
- To meet operator requirements for centralized architectures - Provides the information of AC, WTP, radio and station objects'
basic property and their relationship;
The basic idea of CAPWAP-BASE-MIB is: - Supports indicating the 'WTP Virtual Radio Interface' and PHY
radio's mapping relationship;
- The CAPWAP-BASE-MIB MUST be run on the AC devices and is NOT - Provides counters for WTP, radio's reboot event, hardware event
REQUIRED on the WTP devices. It follows same idea as CAPWAP failure and so on;
protocol: Centralized Control
- As a generic mechanism, it is independent of any wireless binding - Provides the various notifications like channel up, join failure
technologies and defined by an independent MIB file and so on.
- To be independent of any wireless binding technologies and have 5.2. Wireless Binding MIB Modules
ability to reuse MIB standards of other SDOs, is the main challenge
for design of the MIB
- ifIndex [RFC2863] will be used as common handler for corresponding Other Standards Developing Organizations (SDOs), such as IEEE, have
interfaces in the CAPWAP-BASE-MIB and specific wireless technologies already defined MIB modules for a specific wireless technology, e.g.,
MIB modules the MIB module in IEEE 802.11 standard [IEEE.802-11.2007]. Such MIB
modules are called as wireless binding MIB module.
- The operator could manage and control the centralized wireless 5.3. Design Objectives
architectures using multiple MIB standards defined by multiple SDOs,
while keeping them loosely coupled
It is designed to satisfy the following requirements and constraints: This document brings forward a mechanism to avoid redefining MIB
objects in the existing MIB modules for a specific wireless
technology, in another words, a mechanism to reuse wireless binding
MIB modules defined by other SDOs.
- From AC to centrally manage and monitor WTPs In summary, the CAPWAP-BASE-MIB module have the following design
objectives:
- The MIB module supports CAPWAP protocol parameters queries - To implement an architecture that uses SNMP for the management and
control of wireless networks, answering the operators requirements
for centralized management, whatever the deployment or configuration
of the network devices (centralized, distributed, or some mix);
- The MIB module supports showing WTPs current state - To be consistent with CAPWAP protocol;
- The MIB module provides the information of AC, WTPs, radio and
station objects' basic property and their relationship
- The MIB module supports indicating the 'WTP Virtual Radio - To be independent of any wireless technologies and have ability to
Interface' and PHY radio's mapping relationship reuse wireless binding MIB modules defined by other SDOs;
- The counters are provided for WTP, radio's reboot event, hardware - To enable interoperability between vendors;
event failure and so on
- The MIB module provides the various notification like channel up, - To meet operator requirements for centralized wireless
join failure and so on architectures.
Before coming to details of CAPWAP-BASE-MIB module, it will introduce 5.4. Design Idea
how CAPWAP-BASE-MIB is able to be independent of any wireless binding
technologies and reuse MIB standards of other SDOs. As centralized
Wireless architecture, the operator has to prepare configuration on
the AC before WTPs connects to AC. For any wireless binding
technology, the configuration and management of radio is very
important. Under centralized Wireless architecture, according to
[I-D.ietf-capwap-protocol-specification], a specific PHY radio could
be identified by identifier of a WTP and radio (WTP id + radio id).
As usual, the standard of a binding technology provides MIB standard
for radio management on its own. For example, according to IEEE
802.11 WG MIB standards, the MIB tables such as Dot11OperationTable
are able to support WTP radio configuration. These tables use
ifIndex as the index, and work well under standalone Wireless
architecture.
To reuse MIB objects (defined by SDOs such as IEEE) for radio is very The basic design idea of CAPWAP-BASE-MIB module is:
important, and the key point is to reuse the idea of ifIndex. So it
is required a way to maintain the mapping relationship between 'WTP
id + radio id' and 'ifIndex'. As a generic mechanism, ifIndex can
identify an interface in abstract way, and it does NOT care for an
interface's PHY location (either on the WTP or AC). AC can have
interfaces of 'WTP Virtual Radio Interface' ifType, which will
logically represent PHY radios on the WTP. It looks like that PHY
radios are located on the AC, and PHY location of WTP (radio) is
hidden to the operator. Operator can operate radios by MIB tables
(such as IEEE 802.11 WG's) with ifIndex of 'WTP Virtual Radio
Interface'. As an Abstract interface, 'WTP Virtual Radio Interface'
could be used by any wireless binding technology such as IEEE 802.11
and 802.16. The table of capwapRadioBindTable will indicate the
mapping relationship between 'WTP id + Radio id' and IfIndex.
6. Structure of the MIB Module - The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT
REQUIRED on the WTP devices. It follows same idea as CAPWAP
protocol: Centralized Control;
6.1. The capwapBaseObjects Subtree - It is designed to accommodate the specific needs of each wireless
technology in a standard way. It is independent of any wireless
technologies;
The subtree provides information for statistic data and configuration - ifIndex [RFC2863] will be used as common handler for corresponding
parameters of WTP and radio. interfaces in the CAPWAP-BASE-MIB and specific wireless technologies
MIB modules;
6.2. The capwapBaseConformance Subtree - The operator could manage and control the centralized wireless
architectures using multiple MIB modules defined by multiple SDOs,
while keeping them loosely coupled.
The subtree provides conformance information of MIB objects. 5.5. Mechanism of Reusing Wireless Binding MIB Modules
6.3. The capwapBaseNotifications Subtree Before coming to details of CAPWAP-BASE-MIB module, it will introduce
how CAPWAP-BASE-MIB module is able to be independent of any wireless
technologies and reuse wireless binding MIB modules defined by other
SDOs. As centralized Wireless architecture, the operator has to
prepare configuration on the AC before WTPs connects to AC. For any
wireless technology, the configuration and management of radio is
very important. Under centralized WLAN architecture, according to
[I-D.ietf-capwap-protocol-specification], a specific PHY radio could
be identified by identifier of a WTP and radio (WTP id + radio id).
As usual, wireless binding MIB modules support radio management on
its own. For example, the MIB tables such as Dot11OperationTable
[IEEE.802-11.2007] are able to support WTP radio configuration.
These tables use ifIndex as the index, and work well under autonomous
WLAN architecture.
The subtree describes the notifications defined in the MIB module, To reuse such wireless binding MIB modules is very important, and the
and their purpose. key point is to reuse the idea of ifIndex. So it is required a way
to maintain the mapping relationship between 'WTP id + radio id' and
'ifIndex'. As a generic mechanism, ifIndex can identify an interface
in abstract way, and it does NOT care for an interface's PHY location
(either on the WTP or AC). AC can have interfaces of 'WTP Virtual
Radio Interface' ifType, which will logically represent PHY radios on
the WTP. It looks like that PHY radios are located on the AC, and
PHY location of WTP (radio) is hidden to the operator. Operator can
operate radios by MIB tables with ifIndex of 'WTP Virtual Radio
Interface'. As an abstract interface, 'WTP Virtual Radio Interface'
could be used by any wireless technology such as IEEE 802.11 and
802.16. The table of capwapBaseWirelessBindingTable in the CAPWAP-
BASE-MIB module is used to indicate the such mapping relationship
between 'WTP id + Radio id' and IfIndex.
6.4. Brief Description of MIB Objects 5.6. CAPWAP Protocol Wireless Binding MIB Module
According to the CAPWAP Protocol specification
[I-D.ietf-capwap-protocol-specification], 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 [I-D.ietf-capwap-protocol-binding-ieee80211]
for IEEE 802.11 binding.
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 [I-D.ietf-capwap-protocol-binding-ieee80211]
defines WLAN conception. 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 [I-D.ietf-capwap-802dot11-mib].
6. Structure of the MIB Module
The MIB objects were derived from the CAPWAP protocol document The MIB objects were derived from the CAPWAP protocol document
[I-D.ietf- capwap-protocol-specification]. [I-D.ietf- capwap-protocol-specification].
1) capwapBaseAcNameListTable 1) capwapBaseAcNameListTable
The AC name list table is used to configure AC name list. The AC name list table is used to configure AC name list.
2) capwapBaseMacAclTable 2) capwapBaseMacAclTable
skipping to change at page 6, line 43 skipping to change at page 8, line 16
3) capwapBaseWtpStateTable 3) capwapBaseWtpStateTable
The WTPs status table is used to indicate each WTP's CAPWAP FSM The WTPs status table is used to indicate each WTP's CAPWAP FSM
state. state.
4) capwapBaseWtpTable 4) capwapBaseWtpTable
The WTPs table is used for providing property and configuration The WTPs table is used for providing property and configuration
information in details for WTPs in running state. information in details for WTPs in running state.
5) capwapBaseRadioBindTable 5) capwapBaseWirelessBindingTable
The radio bind table is used to indicate the mapping relationship The wireless binding table is used to indicate the mapping
between logical interface of 'WTP Virtual Radio Interface' ifType and relationship between logical interface of 'WTP Virtual Radio
PHY radio. Interface' ifType and PHY radio.
6) capwapBaseStationTable 6) capwapBaseStationTable
The station table is used for providing stations' basic property The station table is used for providing stations' basic property
information. information.
7) capwapBaseWtpRebootStatsTable 7) capwapBaseWtpEventsStatsTable
The WTP reboot statistic table is used for collecting WTP reboot The WTP events statistic table is used for collecting WTP reboot
count, link failure count, hardware failure count and so on. count, link failure count, hardware failure count and so on.
8) capwapBaseRadioStatsTable 8) capwapBaseRadioEventsStatsTable
The WTP radio statistic table is used for collecting radio reset The radio events statistic table is used for collecting radio reset
count, channel change count, hardware failure count and so on. count, channel change count, hardware failure count and so on.
7. Relationship to Other MIB Modules 7. Relationship to Other MIB Modules
7.1. Relationship to the SNMPv2-MIB 7.1. Relationship to SNMPv2-MIB Module
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-BASE-MIB does entity and certain other system-wide data. The CAPWAP-BASE-MIB
not duplicate those objects. module does not duplicate those objects.
7.2. Relationship to the IF-MIB 7.2. Relationship to IF-MIB Module
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 WTP radio object that extensions to the Interfaces Group for managing WTP radio object that
are modeled as interfaces. are modeled as interfaces.
IF-MIB is required to support on the AC. For each PHY radio on the IF-MIB module is required to support on the AC. For each PHY radio
WTP, it will have a logical interface of 'WTP Virtual Radio on the WTP, it will have a logical interface of 'WTP Virtual Radio
Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides
a way to configure radio's parameters and query radio's traffic a way to configure radio's parameters and query radio's traffic
statistics, and reuse the MIBs defined by a specific wireless binding statistics, and reuse wireless binding modules defined by other SDOs.
technology. The interface SHOULD be modeled as an ifEntry and The interface MUST be modeled as an ifEntry and provide appropriate
provide appropriate interface information. interface information.
Some specific interpretations of ifTable for CAPWAP-BASE-MIB are as
follow.
Object Use for the CAPWAP-BASE-MIB.
ifIndex Each interface of 'WTP Virtual Radio Interface'
ifType maybe be represented by an ifEntry.
ifDescr Description of the interface of 'WTP Virtual Radio
Interface' ifType.
ifType IANAifType of 'WTP Virtual Radio Interface'.
ifName Textual name (unique on this system) of the interface
or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager.
ifPhysAddress The physical address of the interface, such as the
BSSID of a 802.11 radio.
ifAdminStatus This variable indicates the operator's intent as
to whether PHY should be enabled, disabled, or
running in some diagnostic testing mode on this
interface.
Also see [RFC2863].
ifOperStatus This value reflects the actual or operational status
of radio.
Also see [RFC2863].
ifLastChange The value of sysUpTime at the time the interface
entered its current operational state.
Also see [RFC2863].
ifInOctets The number of received octets over the interface;
such as the number of octets received as 802.11
frames.
ifOutOctets The number of transmitted octets over the interface;
such as the number of octets transmitted as 802.11
frames.
ifInErrors The number of inbound frames dropped due to
uncorrectable errors.
ifInUnknownProtos
The number of received frame discarded during
frame header validation, including frames with
unrecognized label values.
ifOutErrors The number of outbound frames dropped due to Also, as ifIndex [RFC2863] will be used as common handler for
uncorrectable errors. corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless
technologies MIB modules, the system (AC) MUST have a mechanism that
preserves the values of ifIndex in the ifTable at AC reboot.
7.3. Relationship to the ENTITY-MIB 7.3. Relationship to ENTITY-MIB Module
The ENTITY-MIB [RFC4133] meets need for a standardized way of The ENTITY-MIB module [RFC4133] meets need for a standardized way of
representing a single agent, which supports multiple instances of one representing a single agent, which supports multiple instances of one
MIB. It could express a certain relationship between multiple MIB. It could express a certain relationship between multiple
entities, and provide entity properties for each entity. entities, and provide entity properties for each entity.
Under the wireless centralized architectures, the SNMP agent will run Under the wireless centralized architectures, the SNMP agent will run
on the AC, and not required on the WTP. By the ENTITY-MIB on the AC, on the AC, and not required on the WTP. By the ENTITY-MIB module on
it could keep entity information such as firmware revision and the AC, it could keep entity information such as firmware revision
software revision of AC and WTPs. From the ENTITY-MIB perspective, and software revision of AC and WTPs. From the ENTITY-MIB module
the overall physical entity (AC) is a 'compound' of multiple physical perspective, the overall physical entity (AC) is a 'compound' of
entities (WTPs which connects to AC), all entities are identified by multiple physical entities (WTPs which connects to AC), all entities
Physical index. In the capwapBaseWtpTable of CAPWAP-BASE-MIB, it are identified by Physical index. In the capwapBaseWtpTable of
uses capwapBaseWtpPhyIndex object to keep the mapping relationship of CAPWAP-BASE-MIB module, it uses capwapBaseWtpPhyIndex object to keep
WTP object between CAPWAP-BASE-MIB and ENTITY-MIB. the mapping relationship of WTP object between CAPWAP-BASE-MIB and
ENTITY-MIB module.
By combining the MIBs, operators could query AC and WTP's status and By combining the MIB modules, operators could query AC and WTP's
properties. For example, they could get WTP's current status through status and properties. For example, they could get WTP's current
CAPWAP-BASE-MIB, and WTP's software revision information through status through CAPWAP-BASE-MIB module, and WTP's software revision
ENTITY-MIB. information through ENTITY-MIB module. The CAPWAP-BASE-MIB module
does not duplicate those objects defined in the ENTITY-MIB module.
7.4. Relationship to MIB standards of other SDOs 7.4. Relationship to Wireless Binding MIB Modules
The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is The wireless binding MIB module of a wireless technology (such as
required to support on the AC. The CAPWAP-BASE-MIB module is able to [IEEE.802-11.2007]) is required to support on the AC. The CAPWAP-
support any wireless binding technology. Through ifIndex of 'WTP BASE-MIB module is able to support any wireless binding. Through
Virtual Radio Interface' ifType, it provides consistent and abstract ifIndex of 'WTP Virtual Radio Interface' ifType, it provides
way of reusing MIB objects of a wireless binding technology. 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.
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 module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP-
ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB
[RFC4133].
8. Example of CAPWAP-BASE-MIB Usage 8. Example of CAPWAP-BASE-MIB Module Usage
With the idea of 'WTP Virtual Radio Interface' in the mind, the With the idea of 'WTP Virtual Radio Interface' in the mind, the usage
usage of MIB will be easily understood. Here takes IEEE 802.11 of the MIB modules will be easily understood. Here takes IEEE 802.11
binding technology as an example. binding as an example.
1) Identify each PHY radio by 'WTP Virtual Radio Interface' 1) Identify the 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, Suppose a WTP's serial number is '12345678', and first radio id is 1.
the following information is available in the On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface'
CapwapBaseRadioBindTable. ifType is 10 which represents the PHY radio 1. The following
information is obtained in the CapwapBaseWirelessBindingTable.
In CapwapBaseRadioBindTable In CapwapBaseWirelessBindingTable
{ {
capwapBaseWtpId = 12345678, capwapBaseWtpStateWtpId = '12345678',
capwapBaseRadioId = 1, capwapBaseWirelessBindingRadioId = 1,
capwapBaseWtpVirtualRadioifIndex = 10, capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseRadioWirelessBinding = dot11(2) capwapBaseWirelessBindingType = dot11(2)
} }
Suppose WTP's serial number is 12345678, and first radio id is 1. By the mechanism of 'WTP Virtual Radio Interface', it seems WTP PHY
On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' radios are located on the AC. The interface of 'WTP Virtual Radio
ifType is 10 which represents the PHY radio 1. Interface' ifType is modeled by ifTable [RFC2863].
By the mechanism of 'WTP Virtual Radio Interface', it seems WTP
PHY radios are located on the AC. The interface of 'WTP Virtual
Radio Interface' ifType 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 ifType = xxx,
Radio Interface', RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WTP Virtual Radio Interface'
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0, ifPhysAddress = '000000',
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,
skipping to change at page 10, line 42 skipping to change at page 11, line 31
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 specific wireless binding parameters for 'WTP Virtual 2) Configure specific wireless binding parameters for 'WTP Virtual
Radio Interface' Radio Interface'
It will be done on the AC through specific wireless binding MIB It will be done on the AC through specific wireless binding MIB
such as IEEE 802.11 MIB. module such as IEEE 802.11 MIB module.
For example, to configure parameter for 'WTP Virtual Radio Interface' For example, to configure parameter for 'WTP Virtual Radio Interface'
by 802.11 Dot11OperationTable. by IEEE 802.11 Dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = '000000',
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 suppose ifIndex of an interface in In the example, it suppose ifIndex of an interface in 'WTP Virtual
'WTP Virtual Radio Interface' ifType is 10. Radio Interface' ifType is 10.
3) Other configurations for a specific wireless binding 3) WTP reports its current configuration status
For example, WLAN service configuration will be done through CAPWAP
binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB
draft, it will give more explain.
4) WTP reports its current configuration status According to [I-D.ietf-capwap-protocol-specification], after join
After join phase and before WTP get configuration from AC, it will phase and before WTP get configuration from AC, it will report its
report its current configuration status to AC through configuration current configuration status to AC through configuration status
status request message. The data of MIB objects will be updated on request message. The data of MIB objects will be updated on the AC.
the AC. For example, for 802.11 binding, WTP will update data in the For example, for IEEE 802.11 binding, WTP will update data in the
ifTable and IEEE 802.11 MIB so on according to message content. ifTable and IEEE 802.11 MIB module so on according to message
As an example for ifIndex 10, its ifOperStatus in ifTable will be content. As an example for ifIndex 10, its ifOperStatus in ifTable
updated according to current radio operational status in the will be updated according to current radio operational status in the
CAPWAP message. CAPWAP message.
5) Query WTP and radio statistics data 4) Query WTP and radio statistics data
After WTPs come to run status, operator could query WTP and
radio statistics data through CAPWAP-BASE-MIB and specific binding
MIB. For example, through dot11CountersTable in the IEEE 802.11 MIB,
operator could query counter data for radio which is identified
by ifIndex of a virtual radio interface. With capwapBaseAcState table
in the MIB, operator could query configuration and properties of
WTPs which are in run status.
6) Query other statistics data of a specific wireless binding After WTPs come to run status, operator could query WTP and radio
For example, operator could query the statistics data of statistics data through CAPWAP-BASE-MIB and specific binding MIB
WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. module. For example, through dot11CountersTable in the IEEE 802.11
In the CAPWAP 802.11 binding MIB draft, it will give more explain. MIB module, operator could query counter data for radio which is
identified by ifIndex of a virtual radio interface. With
capwapBaseWtpTable table in the CAPWAP-BASE-MIB module, operator
could query configuration and properties of WTPs which are in run
status.
7) Query other properties of WTP 5) MIB operations through a CAPWAP protocol wireless binding MIB
Operator could query MIB objects in the ENTITY-MIB by module
capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB.
The properties of WTP such as software version, hardware version For example, for CAPWAP IEEE 802.11 binding protocol
and so on are available in the ENTITY-MIB. [I-D.ietf-capwap-protocol-binding-ieee80211], Some MIB operations
such as MAC mode configuration for a WLAN depend on the CAPWAP
Protocol Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib].
In the [I-D.ietf-capwap-802dot11-mib], it will give more explain.
6) Query other properties of WTP
Operator could query MIB objects in the ENTITY-MIB module by
capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB
module. The properties of WTP such as software version, hardware
version and so on are available in the ENTITY-MIB module.
9. CAPWAP Message Element Extension 9. CAPWAP Message Element Extension
This section describes the CAPWAP control message extension for This section describes the CAPWAP control message extension for
CAPWAP protocol to support CAPWAP-BASE-MIB. CAPWAP protocol to support CAPWAP-BASE-MIB module.
To enable CAPWAP protocol timers and variables[I-D.ietf-capwap- To enable CAPWAP protocol timers and variables
protocol-specification] manageable through CAPWAP protocol, the [I-D.ietf-capwap-protocol-specification] manageable through CAPWAP
following capwap message element extensions are defined using Vendor protocol, the following capwap message element extensions are defined
Specific Payload message element in this section. These message using Vendor Specific Payload message element in this section. These
elements are used by WTP to report extra configuration information to message elements are used by WTP to report extra configuration
AC. information to AC.
CAPWAP Message Element Vendor Identifier Element ID CAPWAP Message Element Vendor Identifier Element ID
CAPWAP Protocol Timers Id assigned by IANA 1 CAPWAP Protocol Timers Id assigned by IANA 1
CAPWAP Protocol Variables Id assigned by IANA 2 CAPWAP Protocol Variables Id assigned by IANA 2
9.1. CAPWAP Protocol Timers 9.1. CAPWAP Protocol Timers
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 12, line 49 skipping to change at page 13, line 41
| ReportInterval | RetransmitInterval | | ReportInterval | RetransmitInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SilentInterval | StatisticsTimer | | SilentInterval | StatisticsTimer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WaitDTLS | | WaitDTLS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Type: 37 for Vendor Specific Payload Type: 37 for Vendor Specific Payload
Length: 34 Length: 34
Vendor Identifier: The Vendor Identifier field is assigned by IANA. Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes".
Element ID: The Element ID field is set to 1 for CAPWAP Protocol Element ID: The Element ID field is set to 1 for CAPWAP Protocol
Timers. Timers.
DataChannelKeepAlive: A 16-bit value representing the time, DataChannelKeepAlive: A 16-bit value representing the time,
in seconds, that is used by the WTP to determine the next in seconds, that is used by the WTP to determine the next
must transmit the Data Channel KeepAlive. (see [I-D.ietf-capwap- must transmit the Data Channel Keep Alive. (see section 4.7.2 of
protocol-specification]). [I-D.ietf-capwap-protocol-specification]).
DataChannelDeadInterval: A 16-bit value representing the minimum DataChannelDeadInterval: A 16-bit value representing the minimum
time, in seconds, a WTP MUST wait without having received a Data time, in seconds, a WTP MUST wait without having received a Data
Channel Alive packets may be considered dead. The value of this Channel Alive packets may be considered dead. The value of this
timer MUST be no less than 2*DataChannelKeepAlive seconds and timer MUST be no less than 2*DataChannelKeepAlive seconds and
no greater that 240 seconds (see [I-D.ietf-capwap-protocol- no greater that 240 seconds (see section 4.7.3 of [I-D.ietf-
specification]). capwap-protocol-specification]).
DiscoveryInterval: A 16-bit value representing the minimum time, in DiscoveryInterval: A 16-bit value representing the minimum time, in
seconds, that a WTP MUST wait after receiving a Discovery Response seconds, that a WTP MUST wait after receiving a Discovery Response
message, before initiating a DTLS handshake (see [I-D.ietf-capwap- message, before initiating a DTLS handshake (see section 4.7.5 of
protocol-specification]). [I-D.ietf-capwap-protocol-specification]).
DTLSSessionDelete: A 16-bit value representing the minimum time, in DTLSSessionDelete: A 16-bit value representing the minimum time, in
seconds, a WTP MUST wait for DTLS session deletion (see [I-D.ietf- seconds, a WTP MUST wait for DTLS session deletion (see section
capwap-protocol-specification]). 4.7.6 of [I-D.ietf-capwap-protocol-specification]).
EchoInterval: A 16-bit value representing the minimum time, in EchoInterval: A 16-bit value representing the minimum time, in
seconds, between sending Echo Request messages to the AC with seconds, between sending Echo Request messages to the AC with
which the WTP has joined (see [I-D.ietf-capwap-protocol- which the WTP has joined (see section 4.7.7 of [I-D.ietf-capwap-
specification]). protocol-specification]).
IdleTimeout: A 32-bit value representing the idle timeout value that IdleTimeout: A 32-bit value representing the idle timeout value that
the WTP SHOULD enforce for its active station. The default Idle the WTP SHOULD enforce for its active station. The default Idle
Timeout is 300 seconds (see [I-D.ietf-capwap-protocol- Timeout is 300 seconds (see section 4.7.8 of [I-D.ietf-capwap-
specification]). protocol-specification]).
ImageDataStartTimer: A 16-bit value representing the number of ImageDataStartTimer: A 16-bit value representing the number of
seconds the WTP will wait for its peer to transmit the Image seconds the WTP will wait for its peer to transmit the Image
Data Request (see [I-D.ietf-capwap-protocol-specification]). Data Request (see section 4.7.9 of [I-D.ietf-capwap-protocol-
specification]).
MaxDiscoveryInterval: A 16-bit value representing the maximum time MaxDiscoveryInterval: A 16-bit value representing the maximum time
allowed between sending Discovery Request messages, in seconds. allowed between sending Discovery Request messages, in seconds.
This value MUST be no less than 2 seconds and no greater than 180 This value MUST be no less than 2 seconds and no greater than 180
seconds (see [I-D.ietf-capwap-protocol-specification]). seconds (see section 4.7.10 of [I-D.ietf-capwap-protocol-
specification]).
ReportInterval: A 16-bit value representing the time, in seconds, ReportInterval: A 16-bit value representing the time, in seconds,
that is used by the WTP to determine the interval the WTP uses that is used by the WTP to determine the interval the WTP uses
between sending the Decryption Error message elements to inform between sending the Decryption Error message elements to inform
the AC of decryption errors (see [I-D.ietf-capwap-protocol- the AC of decryption errors (see section 4.7.11 of [I-D.ietf-
specification]). capwap-protocol-specification]).
RetransmitInterval: A 16-bit value representing the minimum time, RetransmitInterval: A 16-bit value representing the minimum time,
in seconds, in which a non-acknowledged CAPWAP packet will be in seconds, in which a non-acknowledged CAPWAP packet will be
retransmitted (see [I-D.ietf-capwap-protocol-specification]). retransmitted (see section 4.7.12 of [I-D.ietf-capwap-protocol-
specification]).
SilentInterval: The minimum time, in seconds, a WTP MUST wait before SilentInterval: The minimum time, in seconds, a WTP MUST wait before
it MAY again send Discovery Request messages or attempt to it MAY again send Discovery Request messages or attempt to
establish DTLS session (see [I-D.ietf-capwap-protocol- establish DTLS session (see section 4.7.13 of [I-D.ietf-capwap-
specification]). protocol-specification]).
StatisticsTimer: A 16-bit value representing the time, in seconds, StatisticsTimer: A 16-bit value representing the time, in seconds,
that is used by the WTP to determine the interval the WTP uses that is used by the WTP to determine the interval the WTP uses
between the WTP Events Requests it transmits to the AC to between the WTP Events Requests it transmits to the AC to
communicate its statistics (see [I-D.ietf-capwap-protocol- communicate its statistics (see section 4.7.14 of [I-D.ietf-
specification]). capwap-protocol-specification]).
WaitDTLS: A 16-bit value representing the maximum time, in seconds, WaitDTLS: A 16-bit value representing the maximum time, in seconds,
a WTP MUST wait without having received a DTLS Handshake message a WTP MUST wait without having received a DTLS Handshake message
from an AC. This timer MUST be greater than 30 seconds (see from an AC. This timer MUST be greater than 30 seconds (see
[I-D.ietf-capwap-protocol-specification]). section 4.7.15 of [I-D.ietf-capwap-protocol-
specification]).
9.2. CAPWAP Protocol Variables 9.2. CAPWAP Protocol Variables
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier | | Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element ID | MaxDiscoveries | | Element ID | MaxDiscoveries |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MaxFailedDTLSSessionRetry | MaxRetransmit | | MaxFailedDTLSSessionRetry | MaxRetransmit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 37 for Vendor Specific Payload Type: 37 for Vendor Specific Payload
Length: 12 Length: 12
Vendor Identifier: The Vendor Identifier field is assigned by IANA. Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes".
Element ID: The Element ID field is set to 2 for CAPWAP Protocol Element ID: The Element ID field is set to 2 for CAPWAP Protocol
Variables. Variables.
MaxDiscoveries: A 16-bit value representing the maximum number of MaxDiscoveries: A 16-bit value representing the maximum number of
Discovery Request messages that will be sent after a WTP boots Discovery Request messages that will be sent after a WTP boots
(see [I-D.ietf-capwap-protocol-specification]). (see section 4.8.5 of [-D.ietf-capwap-protocol-specification]).
MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum
number of failed DTLS session establishment attempts before the number of failed DTLS session establishment attempts before the
CAPWAP device enters a silent period (see [I-D.ietf-capwap- CAPWAP device enters a silent period (see section 4.8.6 of
protocol-specification]). [I-D.ietf-capwap-protocol-specification]).
MaxRetransmit: A 16-bit value representing the maximum number of MaxRetransmit: A 16-bit value representing the maximum number of
retransmissions for a given CAPWAP packet before the link layer retransmissions for a given CAPWAP packet before the link layer
considers the peer dead (see [I-D.ietf-capwap-protocol- considers the peer dead (see section 4.8.7 of [I-D.ietf-capwap-
specification]). protocol-specification]).
9.3. CAPWAP Messages for CAPWAP Control Message Extension 9.3. CAPWAP Messages for CAPWAP Control Message Extension
For CAPWAP Control Message Extension, the following CAPWAP messages For CAPWAP Control Message Extension, the following CAPWAP messages
will be used. will be used.
9.3.1. Configuration Status Response Message 9.3.1. Configuration Status Response Message
The following message elements MAY be included in the CAPWAP The following message elements MAY be included in the CAPWAP
Configuration Status Response Message. Configuration Status Response Message.
skipping to change at page 16, line 38 skipping to change at page 17, line 39
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2,
Integer32, Unsigned32, Counter32 Integer32, Unsigned32, Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
capwapBaseMIB MODULE-IDENTITY capwapBaseMIB MODULE-IDENTITY
LAST-UPDATED "200811010000Z" -- Nov 01th, 2008 LAST-UPDATED "200902280000Z" -- Feb 28th, 2009
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)
skipping to change at page 17, line 25 skipping to change at page 18, line 27
Email: chelliot@cisco.com Email: chelliot@cisco.com
Yong Zhang Yong Zhang
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2008 The Internet Society. This version of "Copyright (C) 2009 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 CAPWAP Protocol." the CAPWAP Protocol."
REVISION "200811010000Z" REVISION "200902280000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "128a" DISPLAY-HINT "32a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a WTP instance. "Represents an unique identifier of a WTP instance.
As usual, a serial number of WTP will be used." As usual, a serial number of WTP will be used."
SYNTAX OCTET STRING(SIZE(128)) SYNTAX OCTET STRING (SIZE (0..32))
CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a station instance. "Represents an unique identifier of a station instance.
As usual, the MAC address of station will be used." As usual, the MAC address of station will be used."
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
skipping to change at page 18, line 19 skipping to change at page 19, line 21
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a radio on a WTP." "Represents an unique identifier of a radio on a WTP."
SYNTAX Unsigned32 (1..31) SYNTAX Unsigned32 (1..31)
CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the tunneling modes of operation that are "Represents the tunneling modes of operation that are
supported by the WTP. supported by the WTP.
The WTP MAY support more than one option, represented by The WTP MAY support more than one option, represented by
the bit field below. the bit field below:
unused(0) - This bit is unused localBridging(0) - Local Bridging Mode
localBridging(1) - Local Bridging Mode, dot3Tunnel(1) - 802.3 Frame Tunnel Mode
dot3Tunnel(2) - 802.3 Frame Tunnel Mode, nativeTunnel(2) - Native Frame Tunnel Mode"
nativeTunnel(3) - Native Frame Tunnel Mode."
REFERENCE REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX BITS { SYNTAX BITS {
unused(0), localBridging(0),
localBridging(1), dot3Tunnel(1),
dot3Tunnel(2), nativeTunnel(2)
nativeTunnel(3)
} }
CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the MAC mode of operation supported by the WTP. "Represents the MAC mode of operation supported by the WTP.
The following enumerated values are supported: The following enumerated values are supported:
localMAC(0) - Local-MAC Mode, localMAC(0) - Local-MAC Mode
splitMAC(1) - Split-MAC Mode, splitMAC(1) - Split-MAC Mode
both(2) - Both Local-MAC and Split-MAC." both(2) - Both Local-MAC and Split-MAC"
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX INTEGER { SYNTAX INTEGER {
localMAC(0), localMAC(0),
splitMAC(1), splitMAC(1),
both(2) both(2)
} }
CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the channel type for CAPWAP protocol. "Represents the channel type for CAPWAP protocol.
The following enumerated values are supported: The following enumerated values are supported:
data(1) - data Channel data(1) - data Channel
control(2) - control Channel." control(2) - control Channel"
SYNTAX INTEGER { SYNTAX INTEGER {
data(1), data(1),
control(2) control(2)
} }
CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type "Represents the authentication credential type
for WTP. for WTP.
The following enumerated values are supported: The following enumerated values are supported:
other(1) - Other method, for example, vendor specific. other(1) - Other method, for example, vendor specific
clear(2) - Clear text and no authentication, clear(2) - Clear text and no authentication
x509(3) - X.509 Certificate authentication, x509(3) - X.509 Certificate authentication
psk(4) - Pre-Shared Secret authentication, psk(4) - Pre-Shared Secret authentication
As mandatory requirement, CAPWAP control channel As mandatory requirement, CAPWAP control channel
authentication should use DTLS, and either by certificate or authentication should use DTLS, and either by certificate or
PSK. For data channel, DTLS is optional." PSK. For data channel, DTLS is optional."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
clear(2), clear(2),
x509(3), x509(3),
psk(4) psk(4)
} }
-- Top level components of this MIB module
-- Notifications -- Notifications
capwapBaseNotifications OBJECT IDENTIFIER capwapBaseNotifications OBJECT IDENTIFIER
::= { capwapBaseMIB 0 } ::= { capwapBaseMIB 0 }
-- Tables, Scalars -- Tables, Scalars
capwapBaseObjects OBJECT IDENTIFIER capwapBaseObjects OBJECT IDENTIFIER
::= { capwapBaseMIB 1 } ::= { capwapBaseMIB 1 }
-- Conformance -- Conformance
capwapBaseConformance OBJECT IDENTIFIER capwapBaseConformance OBJECT IDENTIFIER
::= { capwapBaseMIB 2 } ::= { capwapBaseMIB 2 }
skipping to change at page 20, line 42 skipping to change at page 21, line 42
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 3 } ::= { capwapBaseAc 3 }
capwapBaseStationSessionsLimit OBJECT-TYPE capwapBaseStationSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of station sessions configured "Represents the maximum number of station sessions configured
for the AC." on the AC.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 4 } ::= { capwapBaseAc 4 }
capwapBaseDataChannelSecOptions OBJECT-TYPE capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
other(0), other(0),
clear(1), clear(1),
dtls(2) dtls(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the security policy supported for CAPWAP data "The AC communicates its policy on the use of DTLS for
channel. the CAPWAP data channel.
The AC MAY support more than one option, represented by the bit The AC MAY support more than one option, represented by the bit
field below. field below:
other(0) - Other method, for example, vendor specific. other(0) - Other method, for example, vendor specific
clear(1) - Clear Text, clear(1) - Clear Text
dtls(2) - DTLS." dtls(2) - DTLS"
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 5 } ::= { capwapBaseAc 5 }
capwapBaseDataChannelSecConfig OBJECT-TYPE capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE
SYNTAX BITS { SYNTAX INTEGER {
other(0), other(0),
clear(1), clear(1),
dtls(2) dtls(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the security policy configured for the AC for "Represents the security policy configured on the AC for
CAPWAP data channel. CAPWAP data channel.
The configuration is represented by one of the bit The following enumerated values are supported:
fields below. other(0) - Other method, for example, vendor specific
other(0) - Other method, for example, vendor specific. clear(1) - Clear Text
clear(1) - Clear Text, dtls(2) - DTLS"
dtls(2) - DTLS."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 6 } ::= { capwapBaseAc 6 }
capwapBaseControlChannelAuthenOptions OBJECT-TYPE capwapBaseControlChannelAuthenOptions OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unused(0), x509(0),
x509(1), psk(1)
psk(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type supported by the "Represents the authentication credential type supported by the
AC for control channel. AC for control channel.
The AC MAY support more than one option, represented by the bit The AC MAY support more than one option, represented by the bit
field below. field below:
x509(0) - X.509 Certificate Based
unused(0) - This bit is unused psk(1) - Pre-Shared Secret"
x509(1) - X.509 Certificate Based
psk(2) - Pre-Shared Secret."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 7 } ::= { capwapBaseAc 7 }
capwapBaseControlChannelAuthenConfig OBJECT-TYPE capwapBaseControlChannelAuthenConfig OBJECT-TYPE
SYNTAX BITS { SYNTAX INTEGER {
unused(0),
x509(1), x509(1),
psk(2) psk(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type configured for "Represents the authentication credential type configured for
the AC for control channel. the AC for control channel.
The configuration is represented by one of the bit The following enumerated values are supported:
fields below.
unused(0) - This bit is unused
x509(1) - X.509 Certificate Based x509(1) - X.509 Certificate Based
psk(2) - Pre-Shared Secret." psk(2) - Pre-Shared Secret"
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 8 } ::= { capwapBaseAc 8 }
-- capwapBaseAcNameListTable table -- capwapBaseAcNameListTable table
capwapBaseAcNameListTable OBJECT-TYPE capwapBaseAcNameListTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display AC name list." "A table of objects that display AC name list."
REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 9 } ::= { capwapBaseAc 9 }
capwapBaseAcNameListEntry OBJECT-TYPE capwapBaseAcNameListEntry OBJECT-TYPE
SYNTAX CapwapBaseAcNameListEntry SYNTAX CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that configure AC name list. "A set of objects that configure AC name list.
Values of all read-create objects in this Values of all read-create objects in this table are persistent
table are persistent at restart/reboot." at restart/reboot."
INDEX { capwapBaseAcNameListId } INDEX { capwapBaseAcNameListId }
::= { capwapBaseAcNameListTable 1 } ::= { capwapBaseAcNameListTable 1 }
CapwapBaseAcNameListEntry ::= SEQUENCE { CapwapBaseAcNameListEntry ::= SEQUENCE {
capwapBaseAcNameListId Unsigned32, capwapBaseAcNameListId Unsigned32,
capwapBaseAcNameListName OCTET STRING, capwapBaseAcNameListName OCTET STRING,
capwapBaseAcNameListPriority Unsigned32, capwapBaseAcNameListPriority Unsigned32,
capwapBaseAcNameListRowStatus RowStatus capwapBaseAcNameListRowStatus RowStatus
} }
skipping to change at page 23, line 25 skipping to change at page 24, line 21
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique id for a AC Name list." "Represents a unique id for a AC Name list."
::= { capwapBaseAcNameListEntry 1 } ::= { capwapBaseAcNameListEntry 1 }
capwapBaseAcNameListName OBJECT-TYPE capwapBaseAcNameListName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(512)) SYNTAX OCTET STRING(SIZE(512))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name of an AC." "Represents the name of an AC, and it is expected to be
an UTF-8 encoded string."
REFERENCE REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAcNameListEntry 2 } ::= { capwapBaseAcNameListEntry 2 }
capwapBaseAcNameListPriority OBJECT-TYPE capwapBaseAcNameListPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the priority order of the preferred AC. "Represents the priority order of the preferred AC.
skipping to change at page 24, line 16 skipping to change at page 25, line 14
capwapBaseMacAclTable OBJECT-TYPE capwapBaseMacAclTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseMacAclEntry SYNTAX SEQUENCE OF CapwapBaseMacAclEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that configure station Access Control "A table of objects that configure station Access Control
List (ACL). List (ACL).
WTP will not provide service to the MAC addresses configured WTP will not provide service to the MAC addresses configured
in this table." in this table."
REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 10 } ::= { capwapBaseAc 10 }
capwapBaseMacAclEntry OBJECT-TYPE capwapBaseMacAclEntry OBJECT-TYPE
SYNTAX CapwapBaseMacAclEntry SYNTAX CapwapBaseMacAclEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that configure station Access Control "A set of objects that configure station Access Control
List (ACL). List (ACL).
Values of all read-create objects in this Values of all read-create objects in this table are persisten
table are persistent at AC restart/reboot." at AC restart/reboot."
INDEX { capwapBaseMacAclId } INDEX { capwapBaseMacAclId }
::= { capwapBaseMacAclTable 1 } ::= { capwapBaseMacAclTable 1 }
CapwapBaseMacAclEntry ::= SEQUENCE { CapwapBaseMacAclEntry ::= SEQUENCE {
capwapBaseMacAclId Unsigned32, capwapBaseMacAclId Unsigned32,
capwapBaseMacAclStationId CapwapBaseStationIdTC, capwapBaseMacAclStationId CapwapBaseStationIdTC,
capwapBaseMacAclRowStatus RowStatus capwapBaseMacAclRowStatus RowStatus
} }
capwapBaseMacAclId OBJECT-TYPE capwapBaseMacAclId OBJECT-TYPE
skipping to change at page 25, line 40 skipping to change at page 26, line 40
DESCRIPTION DESCRIPTION
"A table of objects that display WTP CAPWAP FSM state." "A table of objects that display WTP CAPWAP FSM state."
::= { capwapBaseWtps 1 } ::= { capwapBaseWtps 1 }
capwapBaseWtpStateEntry OBJECT-TYPE capwapBaseWtpStateEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpStateEntry SYNTAX CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display WTP CAPWAP FSM state." "A set of objects that display WTP CAPWAP FSM state."
INDEX { capwapBaseWtpId } INDEX { capwapBaseWtpStateWtpId }
::= { capwapBaseWtpStateTable 1 } ::= { capwapBaseWtpStateTable 1 }
CapwapBaseWtpStateEntry ::= SEQUENCE { CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpId CapwapBaseWtpIdTC, capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpIpAddressType InetAddressType, capwapBaseWtpStateWtpIpAddressType InetAddressType,
capwapBaseWtpIpAddress InetAddress, capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpPhyAddress PhysAddress, capwapBaseWtpStateWtpPhyAddress PhysAddress,
capwapBaseWtpState INTEGER capwapBaseWtpState INTEGER
} }
capwapBaseWtpId OBJECT-TYPE capwapBaseWtpStateWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP." "Represents the unique identifier of a WTP."
::= { capwapBaseWtpStateEntry 1 } ::= { capwapBaseWtpStateEntry 1 }
capwapBaseWtpIpAddressType OBJECT-TYPE capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the type of IP address of a WTP." "Represents the type of IP address of a WTP."
::= { capwapBaseWtpStateEntry 2 } ::= { capwapBaseWtpStateEntry 2 }
capwapBaseWtpIpAddress OBJECT-TYPE capwapBaseWtpStateWtpIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the IP address of a WTP." "Represents the IP address of a WTP."
::= { capwapBaseWtpStateEntry 3 } ::= { capwapBaseWtpStateEntry 3 }
capwapBaseWtpPhyAddress OBJECT-TYPE capwapBaseWtpStateWtpPhyAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the PHY address of a WTP." "Represents the PHY address of a WTP."
::= { capwapBaseWtpStateEntry 4 } ::= { capwapBaseWtpStateEntry 4 }
capwapBaseWtpState OBJECT-TYPE capwapBaseWtpState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dtls(1), dtls(1),
skipping to change at page 27, line 6 skipping to change at page 28, line 6
clear(7), clear(7),
unknown(8) unknown(8)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the various possible CAPWAP FSM states of WTP "Represents the various possible CAPWAP FSM states of WTP
The following enumerated values are supported: The following enumerated values are supported:
dtls(1) - DTLS negotiation states, which include dtls(1) - DTLS negotiation states, which include
DTLS Setup, Authorize, DTLS Connect. DTLS Setup, Authorize, DTLS Connect
join(2) - WTP is joining with AC, join(2) - WTP is joining with AC
image(3) - WTP is downloading software, image(3) - WTP is downloading software
configure(4) - WTP is getting configuration from AC, configure(4) - WTP is getting configuration from AC
dataCheck(5) - AC is waiting for the Data Channel Keep dataCheck(5) - AC is waiting for the Data Channel Keep
Alive Packet. Alive Packet
run(6) - WTP comes to run state, run(6) - WTP comes to run state
clear(7) - WTP recoveries default configuration. clear(7) - WTP recoveries default configuration
unknown(8) - Operator already prepare configuration unknown(8) - Operator already prepare configuration
for WTP, while WTP has not contact with AC for WTP, while WTP has not contact with AC
till now." till now"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpStateEntry 5 } ::= { capwapBaseWtpStateEntry 5 }
-- End of capwapBaseWtpStateTable Table -- End of capwapBaseWtpStateTable Table
-- capwapBaseWtpTable Table -- capwapBaseWtpTable Table
capwapBaseWtpTable OBJECT-TYPE capwapBaseWtpTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpEntry SYNTAX SEQUENCE OF CapwapBaseWtpEntry
skipping to change at page 27, line 48 skipping to change at page 28, line 48
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display and control a WTP in "A set of objects that display and control a WTP in
running state." running state."
INDEX { capwapBaseWtpCurrId } INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpTable 1 } ::= { capwapBaseWtpTable 1 }
CapwapBaseWtpEntry ::= SEQUENCE { CapwapBaseWtpEntry ::= SEQUENCE {
capwapBaseWtpCurrId CapwapBaseWtpIdTC, capwapBaseWtpCurrId CapwapBaseWtpIdTC,
capwapBaseWtpPhyIndex PhysicalIndex, capwapBaseWtpPhyIndex PhysicalIndex,
capwapBaseWtpName SnmpAdminString, capwapBaseWtpName OCTET STRING,
capwapBaseWtpLocation SnmpAdminString, capwapBaseWtpLocation OCTET STRING,
capwapBaseWtpBaseMacAddress PhysAddress, capwapBaseWtpBaseMacAddress PhysAddress,
capwapBaseTunnelModeOptions CapwapBaseTunnelModeTC, capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC,
capwapBaseMacTypeOptions CapwapBaseMacTypeTC, capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC,
capwapBaseWtpDiscoveryType INTEGER, capwapBaseWtpDiscoveryType INTEGER,
capwapBaseWtpRadiosInUseNum Unsigned32, capwapBaseWtpRadiosInUseNum Unsigned32,
capwapBaseWtpRadioNumLimit Unsigned32, capwapBaseWtpRadioNumLimit Unsigned32,
capwapBaseWtpStaticIpEnable TruthValue, capwapBaseWtpStaticIpEnable TruthValue,
capwapBaseWtpStaticIpType InetAddressType, capwapBaseWtpStaticIpType InetAddressType,
capwapBaseWtpStaticIp InetAddress, capwapBaseWtpStaticIp InetAddress,
capwapBaseWtpNetmask InetAddress, capwapBaseWtpNetmask InetAddress,
capwapBaseWtpGateway InetAddress, capwapBaseWtpGateway InetAddress,
capwapBaseWtpFallbackEnable INTEGER, capwapBaseWtpFallbackEnable INTEGER,
capwapBaseWtpRetransmitCount Unsigned32, capwapBaseWtpRetransmitCount Counter32,
capwapBaseWtpMaxDiscoveries Unsigned32, capwapBaseWtpMaxDiscoveries Unsigned32,
capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32,
capwapBaseWtpMaxRetransmitCnt Unsigned32, capwapBaseWtpMaxRetransmit Unsigned32,
capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, capwapBaseWtpDataChannelKeepAliveTimer Unsigned32,
capwapBaseWtpDataChannelDeadInterval Unsigned32, capwapBaseWtpDataChannelDeadInterval Unsigned32,
capwapBaseWtpDiscoveryInterval Unsigned32, capwapBaseWtpDiscoveryInterval Unsigned32,
capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, capwapBaseWtpDTLSSessionDeleteTimer Unsigned32,
capwapBaseWtpEchoInterval Unsigned32, capwapBaseWtpEchoInterval Unsigned32,
capwapBaseWtpIdleTimeout Unsigned32, capwapBaseWtpIdleTimeout Unsigned32,
capwapBaseWtpImageDataStartTimer Unsigned32, capwapBaseWtpImageDataStartTimer Unsigned32,
capwapBaseWtpMaxDiscoveryInterval Unsigned32, capwapBaseWtpMaxDiscoveryInterval Unsigned32,
capwapBaseWtpReportInterval Unsigned32, capwapBaseWtpReportInterval Unsigned32,
capwapBaseWtpRetransmitInterval Unsigned32, capwapBaseWtpRetransmitInterval Unsigned32,
capwapBaseWtpSilentInterval Unsigned32, capwapBaseWtpSilentInterval Unsigned32,
capwapBaseWtpStatisticsTimer Unsigned32, capwapBaseWtpStatisticsTimer Unsigned32,
capwapBaseWtpWaitDTLSTimer Unsigned32 capwapBaseWtpWaitDTLSTimer Unsigned32,
capwapBaseWtpEcnSupport INTEGER
} }
capwapBaseWtpCurrId OBJECT-TYPE capwapBaseWtpCurrId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP Which is "Represents the unique identifier of a WTP which is
in running state." in running state."
::= { capwapBaseWtpEntry 1 } ::= { capwapBaseWtpEntry 1 }
capwapBaseWtpPhyIndex OBJECT-TYPE capwapBaseWtpPhyIndex OBJECT-TYPE
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique physical index of a physical entity "Represents the unique physical index of a physical entity
in the ENTITY-MIB. The information such as software version in the ENTITY-MIB module. The information such as software
of specific WTP could be accessed through the index." version of specific WTP could be accessed through the index."
::= { capwapBaseWtpEntry 2 } ::= { capwapBaseWtpEntry 2 }
capwapBaseWtpName OBJECT-TYPE capwapBaseWtpName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX OCTET STRING(SIZE(512))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name of a WTP." "Represents the name of a WTP."
REFERENCE REFERENCE
"Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 3 } ::= { capwapBaseWtpEntry 3 }
capwapBaseWtpLocation OBJECT-TYPE capwapBaseWtpLocation OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX OCTET STRING(SIZE(1024))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the location of a WTP." "Represents the location of a WTP."
REFERENCE REFERENCE
"Section 4.6.29. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.30. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 4 } ::= { capwapBaseWtpEntry 4 }
capwapBaseWtpBaseMacAddress OBJECT-TYPE capwapBaseWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WTP's Base MAC Address, which MAY be assigned "Represents the WTP's Base MAC Address, which MAY be assigned
to the primary Ethernet interface." to the primary Ethernet interface."
REFERENCE REFERENCE
"Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 5 } ::= { capwapBaseWtpEntry 5 }
capwapBaseTunnelModeOptions OBJECT-TYPE capwapBaseWtpTunnelModeOptions OBJECT-TYPE
SYNTAX CapwapBaseTunnelModeTC SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the tunneling modes of operation supported by "Represents the tunneling modes of operation supported by
the WTP. the WTP."
The WTP MAY support more than one option, represented by the
bit field below.
localBridging(1) - Local Bridging Mode,
dot3Tunnel(2) - 802.3 Frame Tunnel Mode,
nativeTunnel(3) - Native Frame Tunnel Mode."
REFERENCE REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 6 } ::= { capwapBaseWtpEntry 6 }
capwapBaseMacTypeOptions OBJECT-TYPE capwapBaseWtpMacTypeOptions OBJECT-TYPE
SYNTAX CapwapBaseMacTypeTC SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the MAC mode of operation supported by the WTP. "Represents the MAC mode of operation supported by the WTP."
The following enumerated values are supported:
localMAC(0) - Local-MAC Mode,
splitMAC(1) - Split-MAC Mode,
both(2) - Both Local-MAC Mode and Split-MAC Mode."
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 7 } ::= { capwapBaseWtpEntry 7 }
capwapBaseWtpDiscoveryType OBJECT-TYPE capwapBaseWtpDiscoveryType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
staticConfig(1), staticConfig(1),
dhcp(2), dhcp(2),
dns(3), dns(3),
acRef(4) acRef(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents how WTP discovers the AC. "Represents how WTP discovers the AC.
The following enumerated values are supported: The following enumerated values are supported:
unknown(0) - Unknown, unknown(0) - Unknown
staticConfig(1) - Static Configuration, staticConfig(1) - Static Configuration
dhcp(2) - DHCP, dhcp(2) - DHCP
dns(3) - DNS, dns(3) - DNS
acRef(4) - AC Referral." acRef(4) - AC Referral"
REFERENCE REFERENCE
"Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 8 } ::= { capwapBaseWtpEntry 8 }
capwapBaseWtpRadiosInUseNum OBJECT-TYPE capwapBaseWtpRadiosInUseNum OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of radios in use in the WTP." "Represents the number of radios in use on the WTP."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 9 } ::= { capwapBaseWtpEntry 9 }
capwapBaseWtpRadioNumLimit OBJECT-TYPE capwapBaseWtpRadioNumLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum radio number supported by the WTP." "Represents the maximum radio number supported by the WTP."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 10 } ::= { capwapBaseWtpEntry 10 }
capwapBaseWtpStaticIpEnable OBJECT-TYPE capwapBaseWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the WTP should use a static IP address "Represents whether the WTP should use a static IP address
or not. A value of false disables the static IP address, or not. A value of false disables the static IP address,
while a value of true enables it." while a value of true enables it."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 11 } ::= { capwapBaseWtpEntry 11 }
capwapBaseWtpStaticIpType OBJECT-TYPE capwapBaseWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether WTP uses IPV4 or IPV6 static IP address." "Represents whether WTP uses IPv4 or IPv6 static IP address."
::= { capwapBaseWtpEntry 12 } ::= { capwapBaseWtpEntry 12 }
capwapBaseWtpStaticIp OBJECT-TYPE capwapBaseWtpStaticIp OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the "When capwapBaseWtpStaticIpEnable is true, it represents the
static IP address to assign to the WTP." static IP address to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 13 } ::= { capwapBaseWtpEntry 13 }
capwapBaseWtpNetmask OBJECT-TYPE capwapBaseWtpNetmask OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the "When capwapBaseWtpStaticIpEnable is true, it represents the
netmask to assign to the WTP." netmask to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 14 } ::= { capwapBaseWtpEntry 14 }
capwapBaseWtpGateway OBJECT-TYPE capwapBaseWtpGateway OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the "When capwapBaseWtpStaticIpEnable is true, it represents the
gateway to assign to the WTP." gateway to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 15 } ::= { capwapBaseWtpEntry 15 }
capwapBaseWtpFallbackEnable OBJECT-TYPE capwapBaseWtpFallbackEnable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
reserved(0),
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether to enable or disable automatic CAPWAP "Represents whether to enable or disable automatic CAPWAP
fallback in the event that a WTP detects its preferred AC, and fallback in the event that a WTP detects its preferred AC, and
is not currently connected to it. is not currently connected to it.
The following enumerated values are supported: The following enumerated values are supported:
reserved(0) - The value is reserved, enabled(1) - The fallback mode is enabled
enabled(1) - The fallback mode is enabled, disabled(2) - The fallback mode is disabled"
disabled(2) - The fallback mode is disabled."
REFERENCE REFERENCE
"Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { enabled }
::= { capwapBaseWtpEntry 16 } ::= { capwapBaseWtpEntry 16 }
capwapBaseWtpRetransmitCount OBJECT-TYPE capwapBaseWtpRetransmitCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of retransmissions for a given "Represents the number of retransmissions for a given
CAPWAP packet." CAPWAP packet."
REFERENCE REFERENCE
"Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 17 } ::= { capwapBaseWtpEntry 17 }
capwapBaseWtpMaxDiscoveries OBJECT-TYPE capwapBaseWtpMaxDiscoveries OBJECT-TYPE
skipping to change at page 33, line 23 skipping to change at page 34, line 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represent the maximum number of failed DTLS session "Represent the maximum number of failed DTLS session
establishment attempts before the CAPWAP device enters a establishment attempts before the CAPWAP device enters a
silent period." silent period."
REFERENCE REFERENCE
"Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 3 } DEFVAL { 3 }
::= { capwapBaseWtpEntry 19 } ::= { capwapBaseWtpEntry 19 }
capwapBaseWtpMaxRetransmitCnt OBJECT-TYPE capwapBaseWtpMaxRetransmit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represent the maximum number of retransmission for a given "Represent the maximum number of retransmission for a given
CAPWAP packet before the link layer considers the peer dead." CAPWAP packet before the link layer considers the peer dead."
REFERENCE REFERENCE
"Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseWtpEntry 20 } ::= { capwapBaseWtpEntry 20 }
capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the the next opportunity, in seconds, the WTP must "Represents the next opportunity, in seconds, the WTP must
transmit the Data Channel KeepAlive message." transmit the Data Channel KeepAlive message."
REFERENCE REFERENCE
"Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseWtpEntry 21 } ::= { capwapBaseWtpEntry 21 }
capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..240)
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait "Represents the minimum time, in seconds, a WTP MUST wait
without having received a Data Channel Keep Alive packet without having received a Data Channel Keep Alive packet
before the destination for the Data Channel Keep Alive before the destination for the Data Channel Keep Alive
packets may be considered dead." packets may be considered dead."
REFERENCE REFERENCE
"Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx."
skipping to change at page 35, line 34 skipping to change at page 36, line 25
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of seconds the WTP will wait for its peer "Represents the number of seconds the WTP will wait for its peer
to transmit the Image Data Request." to transmit the Image Data Request."
REFERENCE REFERENCE
"Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseWtpEntry 27 } ::= { capwapBaseWtpEntry 27 }
capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (2..180)
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time allowed between sending Discovery "Represents the maximum time allowed between sending Discovery
Request messages, in seconds. This value MUST be no less than Request messages, in seconds. This value MUST be no less than
2 seconds and no greater than 180 seconds." 2 seconds and no greater than 180 seconds."
REFERENCE REFERENCE
"Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 20 } DEFVAL { 20 }
skipping to change at page 37, line 6 skipping to change at page 37, line 45
DESCRIPTION DESCRIPTION
"Represents the interval the WTP uses between the WTP Events "Represents the interval the WTP uses between the WTP Events
Requests it transmits to the AC to communicate its statistics, Requests it transmits to the AC to communicate its statistics,
in seconds." in seconds."
REFERENCE REFERENCE
"Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 120 } DEFVAL { 120 }
::= { capwapBaseWtpEntry 32 } ::= { capwapBaseWtpEntry 32 }
capwapBaseWtpWaitDTLSTimer OBJECT-TYPE capwapBaseWtpWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (30..4294967295)
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait "Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC. without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds." This timer MUST be greater than 30 seconds."
REFERENCE REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseWtpEntry 33 } ::= { capwapBaseWtpEntry 33 }
capwapBaseWtpEcnSupport 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]."
REFERENCE
"Section 4.7.25. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 34 }
-- End of capwapBaseWtpTable table -- End of capwapBaseWtpTable table
-- capwapBaseWirelessBindingTable Table
capwapBaseRadioBindTable OBJECT-TYPE capwapBaseWirelessBindingTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry
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 the mapping relationship
between specific interface of 'WTP Virtual Radio Interface' between specific interface of 'WTP Virtual Radio Interface'
ifType and PHY radio. The mapping relationship in this table ifType and PHY radio, and wireless binding type for
a specific radio. The mapping relationship in this table
is persistent at restart/reboot." is persistent at restart/reboot."
::= { capwapBaseWtps 3 } ::= { capwapBaseWtps 3 }
capwapBaseRadioBindEntry OBJECT-TYPE capwapBaseWirelessBindingEntry OBJECT-TYPE
SYNTAX CapwapBaseRadioBindEntry SYNTAX CapwapBaseWirelessBindingEntry
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 'WTP Virtual Radio' and PHY radio." between 'WTP Virtual Radio Interface' and PHY radio, and
wireless binding type for a specific radio."
INDEX { INDEX {
capwapBaseWtpId, capwapBaseWtpStateWtpId,
capwapBaseRadioId capwapBaseWirelessBindingRadioId
} }
::= { capwapBaseRadioBindTable 1 } ::= { capwapBaseWirelessBindingTable 1 }
CapwapBaseRadioBindEntry ::= SEQUENCE { CapwapBaseWirelessBindingEntry ::= SEQUENCE {
capwapBaseRadioId CapwapBaseRadioIdTC, capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC,
capwapBaseVirtualRadioIfIndex InterfaceIndex, capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex,
capwapBaseRadioWirelessBinding INTEGER capwapBaseWirelessBindingType INTEGER
} }
capwapBaseRadioId OBJECT-TYPE capwapBaseWirelessBindingRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, and only "Represents the identifier of a PHY radio on a WTP, and only
requires unique on a WTP. requires unique on a WTP.
For example, WTP A and WTP B will use same value of For example, WTP A and WTP B will use same value of
capwapBaseRadioId for their first radio." capwapBaseWirelessBindingRadioId for their first radio."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioBindEntry 1 } ::= { capwapBaseWirelessBindingEntry 1 }
capwapBaseVirtualRadioIfIndex OBJECT-TYPE capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the index value that uniquely identifies a "Represents the index value that uniquely identifies a
'WLAN Virtual Radio Interface'. The interface identified by a 'WLAN Virtual Radio Interface'. The interface identified by
particular value of this index is the same interface as a particular value of this index is the same interface as
identified by the same value of ifIndex. identified by the same value of ifIndex.
Before WTPs connect to AC and get configuration, operator Before WTPs connect to AC and get configuration, operator
will prepare configuration for them. On the AC, there are will prepare configuration for them. On the AC, there are
interfaces of 'WTP Virtual Radio Interface' ifType which interfaces of 'WTP Virtual Radio Interface' ifType which
represent PHY radio interfaces on the WTP. represent PHY radio interfaces on the WTP.
As most MIBs use ifIndex to identify an interface for As most MIB modules use ifIndex to identify an interface for
configuration and statistic data, for example, IEEE 802.11 MIB. configuration and statistic data, for example, IEEE 802.11 MIB
It will be very easy to reuse other MIBs such as IEEE 802.11 module. It will be very easy to reuse other wireless binding
MIB by 'WTP Virtual Radio Interface'." MIB modules through 'WTP Virtual Radio Interface'."
::= { capwapBaseRadioBindEntry 2 } ::= { capwapBaseWirelessBindingEntry 2 }
capwapBaseRadioWirelessBinding OBJECT-TYPE capwapBaseWirelessBindingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
reserved0(0),
dot11(1), dot11(1),
reserved2(2),
epc(3) epc(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the wireless binding type for radio. "Represents the wireless binding type for radio.
The following enumerated values are supported: The following enumerated values are supported:
reserved0(0) - Reserved, dot11(1) - IEEE 802.11
dot11(1) - IEEE 802.11, epc(3) - EPCGlobal"
reserved2(2) - Reserved,
epc(3) - EPCGlobal."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioBindEntry 3 } ::= { capwapBaseWirelessBindingEntry 3 }
-- End of capwapBaseWirelessBindingTable Table
-- capwapBaseStationTable Table -- capwapBaseStationTable Table
capwapBaseStationTable OBJECT-TYPE capwapBaseStationTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseStationEntry SYNTAX SEQUENCE OF CapwapBaseStationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display stations which are accessing "A table of objects that display stations which are accessing
the wireless service provided by the AC." the wireless service provided by the AC."
REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtps 4 } ::= { capwapBaseWtps 4 }
capwapBaseStationEntry OBJECT-TYPE capwapBaseStationEntry OBJECT-TYPE
SYNTAX CapwapBaseStationEntry SYNTAX CapwapBaseStationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display a station which is "A set of objects that display a station which is
associated with the specific radio on the WTP." associated with the specific radio on the WTP."
INDEX { INDEX {
capwapBaseWtpCurrId, capwapBaseWtpCurrId,
capwapBaseRadioId, capwapBaseWirelessBindingRadioId,
capwapBaseStationId capwapBaseStationId
} }
::= { capwapBaseStationTable 1 } ::= { capwapBaseStationTable 1 }
CapwapBaseStationEntry ::= SEQUENCE { CapwapBaseStationEntry ::= SEQUENCE {
capwapBaseStationId CapwapBaseStationIdTC, capwapBaseStationId CapwapBaseStationIdTC,
capwapBaseStationAddedTime DateAndTime, capwapBaseStationAddedTime DateAndTime,
capwapBaseStationVlanName SnmpAdminString capwapBaseStationVlanName SnmpAdminString
} }
skipping to change at page 40, line 16 skipping to change at page 41, line 22
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the time when the station is added." "Represents the time when the station is added."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseStationEntry 2 } ::= { capwapBaseStationEntry 2 }
capwapBaseStationVlanName OBJECT-TYPE capwapBaseStationVlanName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents VLAN name to which the station is associated." "Represents VLAN name to which the station is associated."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseStationEntry 3 } ::= { capwapBaseStationEntry 3 }
-- End of capwapBaseStationTable Table -- End of capwapBaseStationTable Table
-- capwapBaseWtpEventsStatsTable
capwapBaseWtpRebootStatsTable OBJECT-TYPE capwapBaseWtpEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpRebootStatsEntry SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display WTPs' reboot statistics." "A table of objects that display WTPs' events statistics."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtps 5 } ::= { capwapBaseWtps 5 }
capwapBaseWtpRebootStatsEntry OBJECT-TYPE capwapBaseWtpEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpRebootStatsEntry SYNTAX CapwapBaseWtpEventsStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the reboot statistic data "A set of objects that display the events statistic data
of a WTP." of a WTP."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
INDEX { capwapBaseWtpCurrId } INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpRebootStatsTable 1 } ::= { capwapBaseWtpEventsStatsTable 1 }
CapwapBaseWtpRebootStatsEntry ::= SEQUENCE { CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
capwapBaseWtpRebootCount Counter32, capwapBaseWtpEventsStatsRebootCount Counter32,
capwapBaseWtpInitCount Counter32, capwapBaseWtpEventsStatsInitCount Counter32,
capwapBaseWtpLinkFailureCount Counter32, capwapBaseWtpEventsStatsLinkFailureCount Counter32,
capwapBaseWtpSwFailureCount Counter32, capwapBaseWtpEventsStatsSwFailureCount Counter32,
capwapBaseWtpHwFailureCount Counter32, capwapBaseWtpEventsStatsHwFailureCount Counter32,
capwapBaseWtpOtherFailureCount Counter32, capwapBaseWtpEventsStatsOtherFailureCount Counter32,
capwapBaseWtpUnknownFailureCount Counter32, capwapBaseWtpEventsStatsUnknownFailureCount Counter32,
capwapBaseWtpLastFailureType INTEGER capwapBaseWtpEventsStatsLastFailureType INTEGER
} }
capwapBaseWtpRebootCount OBJECT-TYPE capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of reboots that have occurred due to a "Represents the number of reboots that have occurred due to a
WTP crash. A value of 65535 implies that this information is WTP crash. A value of 65535 implies that this information is
not available on the WTP." not available on the WTP."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 1 } ::= { capwapBaseWtpEventsStatsEntry 1 }
capwapBaseWtpInitCount OBJECT-TYPE capwapBaseWtpEventsStatsInitCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of reboots that have occurred at the "Represents the number of reboots that have occurred at the
request of a CAPWAP protocol message, such as a change in request of a CAPWAP protocol message, such as a change in
configuration that required a reboot or an explicit CAPWAP configuration that required a reboot or an explicit CAPWAP
protocol reset request. A value of 65535 implies that this protocol reset request. A value of 65535 implies that this
information is not available on the WTP." information is not available on the WTP."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 2 } ::= { capwapBaseWtpEventsStatsEntry 2 }
capwapBaseWtpLinkFailureCount OBJECT-TYPE capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to link failure." connection with an AC has failed due to link failure."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 3 } ::= { capwapBaseWtpEventsStatsEntry 3 }
capwapBaseWtpSwFailureCount OBJECT-TYPE capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to software related connection with an AC has failed due to software related
reasons." reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 4 } ::= { capwapBaseWtpEventsStatsEntry 4 }
capwapBaseWtpHwFailureCount OBJECT-TYPE capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to hardware related connection with an AC has failed due to hardware related
reasons." reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 5 } ::= { capwapBaseWtpEventsStatsEntry 5 }
capwapBaseWtpOtherFailureCount OBJECT-TYPE capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to known reasons, other connection with an AC has failed due to known reasons, other
than AC initiated, link, software or hardware failure." than AC initiated, link, software or hardware failure."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 6 } ::= { capwapBaseWtpEventsStatsEntry 6 }
capwapBaseWtpUnknownFailureCount OBJECT-TYPE capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed for unknown reasons." connection with an AC has failed for unknown reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 7 } ::= { capwapBaseWtpEventsStatsEntry 7 }
capwapBaseWtpLastFailureType OBJECT-TYPE capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupport(0), notSupport(0),
acInit(1), acInit(1),
linkFailure(2), linkFailure(2),
swFailure(3), swFailure(3),
hwFailure(4), hwFailure(4),
otherFailure(5), otherFailure(5),
unknown(255) unknown(255)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the failure type of the most recent WTP failure. "Represents the failure type of the most recent WTP failure.
The following enumerated values are supported: The following enumerated values are supported:
notSupport(0) - Not Supported, notSupport(0) - Not Supported
acInit(1) - AC Initiated, acInit(1) - AC Initiated
linkFailure(2) - Link Failure, linkFailure(2) - Link Failure
swFailure(3) - Software Failure, swFailure(3) - Software Failure
hwFailure(4) - Hardware Failure, hwFailure(4) - Hardware Failure
otherFailure(5) - Other Failure, otherFailure(5) - Other Failure
unknown(255) - Unknown (e.g., WTP doesn't keep track unknown(255) - Unknown (e.g., WTP doesn't keep track
of info)." of info)"
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 8 } ::= { capwapBaseWtpEventsStatsEntry 8 }
-- End of capwapBaseWtpEventsStatsTable table
-- capwapBaseRadioEventsStatsTable table
capwapBaseRadioStatsTable OBJECT-TYPE capwapBaseRadioEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioStatsEntry SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display statistics on radios behavior, "A table of objects that display statistics on radios behavior,
and reasons why the WTP radio has been reset." and reasons why the WTP radio has been reset."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtps 6 } ::= { capwapBaseWtps 6 }
capwapBaseRadioStatsEntry OBJECT-TYPE capwapBaseRadioEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseRadioStatsEntry SYNTAX CapwapBaseRadioEventsStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the statistic data of "A set of objects that display the statistic data of
events happened on a specific radio of a WTP." events happened on a specific radio of a WTP."
INDEX { capwapBaseWtpCurrId, capwapBaseRadioId } INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId }
::= { capwapBaseRadioStatsTable 1 } ::= { capwapBaseRadioEventsStatsTable 1 }
CapwapBaseRadioStatsEntry ::= SEQUENCE { CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
capwapBaseRadioResetCount Counter32, capwapBaseRadioEventsStatsResetCount Counter32,
capwapBaseRadioSwFailCount Counter32, capwapBaseRadioEventsStatsSwFailCount Counter32,
capwapBaseRadioHwFailCount Counter32, capwapBaseRadioEventsStatsHwFailCount Counter32,
capwapBaseRadioOtherFailCount Counter32, capwapBaseRadioEventsStatsOtherFailCount Counter32,
capwapBaseRadioUnknownFailCount Counter32, capwapBaseRadioEventsStatsUnknownFailCount Counter32,
capwapBaseRadioConfigUpdateCount Counter32, capwapBaseRadioEventsStatsConfigUpdateCount Counter32,
capwapBaseRadioChannelChangeCount Counter32, capwapBaseRadioEventsStatsChannelChangeCount Counter32,
capwapBaseRadioBandChangeCount Counter32, capwapBaseRadioEventsStatsBandChangeCount Counter32,
capwapBaseRadioCurrentNoiseFloor Integer32, capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32,
capwapBaseRadioDecryptErrorCount Counter32, capwapBaseRadioEventsStatsDecryptErrorCount Counter32,
capwapBaseRadioLastFailType INTEGER capwapBaseRadioEventsStatsLastFailType INTEGER
} }
capwapBaseRadioResetCount OBJECT-TYPE capwapBaseRadioEventsStatsResetCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that that the radio has been "Represents the number of times that that the radio has been
reset." reset."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 1 } ::= { capwapBaseRadioEventsStatsEntry 1 }
capwapBaseRadioSwFailCount OBJECT-TYPE capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due "Represents the number of times that the radio has failed due
to software related reasons." to software related reasons."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 2 } ::= { capwapBaseRadioEventsStatsEntry 2 }
capwapBaseRadioHwFailCount OBJECT-TYPE capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due "Represents the number of times that the radio has failed due
to hardware related reasons." to hardware related reasons."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 3 } ::= { capwapBaseRadioEventsStatsEntry 3 }
capwapBaseRadioOtherFailCount OBJECT-TYPE capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due to "Represents the number of times that the radio has failed due to
known reasons, other than software or hardware failure." known reasons, other than software or hardware failure."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 4 } ::= { capwapBaseRadioEventsStatsEntry 4 }
capwapBaseRadioUnknownFailCount OBJECT-TYPE capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed for "Represents the number of times that the radio has failed for
unknown reasons." unknown reasons."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 5 } ::= { capwapBaseRadioEventsStatsEntry 5 }
capwapBaseRadioConfigUpdateCount OBJECT-TYPE capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio configuration has "Represents the number of times that the radio configuration has
been updated." been updated."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 6 } ::= { capwapBaseRadioEventsStatsEntry 6 }
capwapBaseRadioChannelChangeCount OBJECT-TYPE capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio channel has "Represents the number of times that the radio channel has
been changed." been changed."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 7 } ::= { capwapBaseRadioEventsStatsEntry 7 }
capwapBaseRadioBandChangeCount OBJECT-TYPE capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has changed "Represents the number of times that the radio has changed
frequency bands." frequency bands."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 8 } ::= { capwapBaseRadioEventsStatsEntry 8 }
capwapBaseRadioCurrentNoiseFloor OBJECT-TYPE capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "dBm" UNITS "dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the noise floor of the radio receiver in units of "Represents the noise floor of the radio receiver in units of
dBm." dBm."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 9 } ::= { capwapBaseRadioEventsStatsEntry 9 }
capwapBaseRadioDecryptErrorCount OBJECT-TYPE capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of decryption errors that occurred on the "Represents the number of decryption errors that occurred on the
WTP. Note that this field is only valid in cases where the WTP WTP. Note that this field is only valid in cases where the WTP
provides encryption/decryption services." provides encryption/decryption services."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 10 } ::= { capwapBaseRadioEventsStatsEntry 10 }
capwapBaseRadioLastFailType OBJECT-TYPE capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupport(0), notSupport(0),
swFailure(1), swFailure(1),
hwFailure(2), hwFailure(2),
otherFailure(3), otherFailure(3),
unknown(255) unknown(255)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the failure type of the most recent radio failure. "Represents the failure type of the most recent radio failure.
The following enumerated values are supported: The following enumerated values are supported:
notSupport(0) - Not Supported, notSupport(0) - Not Supported
swFailure(1) - Software Failure, swFailure(1) - Software Failure
hwFailure(2) - Hardware Failure, hwFailure(2) - Hardware Failure
otherFailure(3) - Other Failure, otherFailure(3) - Other Failure
unknown(255) - Unknown." unknown(255) - Unknown"
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 11 } ::= { capwapBaseRadioEventsStatsEntry 11 }
-- End of capwapBaseRadioEventsStatsTable table
-- End of WTP Objects Group -- End of WTP Objects Group
-- CAPWAP Base Parameters Group -- CAPWAP Base Parameters Group
capwapBaseParameters OBJECT IDENTIFIER capwapBaseParameters OBJECT IDENTIFIER
::= { capwapBaseObjects 3 } ::= { capwapBaseObjects 3 }
capwapBaseAcMaxRetransmitCnt OBJECT-TYPE capwapBaseAcMaxRetransmit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represent the maximum number of retransmission for a given "Represent the maximum number of retransmission for a given
CAPWAP packet before the link layer considers the peer dead." CAPWAP packet before the link layer considers the peer dead.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseParameters 1 } ::= { capwapBaseParameters 1 }
capwapBaseAcChangeStatePendingTimer OBJECT-TYPE capwapBaseAcChangeStatePendingTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, the AC will wait "Represents the maximum time, in seconds, the AC will wait
for the Change State Event Request from the WTP after having for the Change State Event Request from the WTP after having
transmitted a successful Configuration Status Response transmitted a successful Configuration Status Response
message." message.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 25 } DEFVAL { 25 }
::= { capwapBaseParameters 2 } ::= { capwapBaseParameters 2 }
capwapBaseAcDataCheckTimer OBJECT-TYPE capwapBaseAcDataCheckTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents The number of seconds the AC will wait for "Represents The number of seconds the AC will wait for
the Data Channel Keep Alive, which is required by the the Data Channel Keep Alive, which is required by the
CAPWAP state machine's Data Check state. CAPWAP state machine's Data Check state.
The AC resets the state machine if this timer expires The AC resets the state machine if this timer expires
prior to transitioning to the next state." prior to transitioning to the next state.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseParameters 3 } ::= { capwapBaseParameters 3 }
capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, an AC MUST wait "Represents the minimum time, in seconds, an AC MUST wait
for DTLS session deletion." for DTLS session deletion.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseParameters 4 } ::= { capwapBaseParameters 4 }
capwapBaseAcEchoInterval OBJECT-TYPE capwapBaseAcEchoInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo "Represents the minimum time, in seconds, between sending Echo
Request messages to the AC with which the WTP has joined." Request messages to the AC with which the WTP has joined.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseParameters 5 } ::= { capwapBaseParameters 5 }
capwapBaseAcRetransmitInterval OBJECT-TYPE capwapBaseAcRetransmitInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, in which a "Represents the minimum time, in seconds, in which a
non-acknowledged CAPWAP packet will be retransmitted." non-acknowledged CAPWAP packet will be retransmitted.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 3 } DEFVAL { 3 }
::= { capwapBaseParameters 6 } ::= { capwapBaseParameters 6 }
capwapBaseAcSilentInterval OBJECT-TYPE capwapBaseAcSilentInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, during which the AC "Represents the minimum time, in seconds, during which the AC
SHOULD ignore all CAPWAP and DTLS packets received from the SHOULD ignore all CAPWAP and DTLS packets received from the
WTP that is in the Sulking state." WTP that is in the Sulking state.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseParameters 7 } ::= { capwapBaseParameters 7 }
capwapBaseAcWaitDTLSTimer OBJECT-TYPE capwapBaseAcWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (30..4294967295)
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait "Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC. without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds." This timer MUST be greater than 30 seconds.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseParameters 8 } ::= { capwapBaseParameters 8 }
capwapBaseAcWaitJoinTimer OBJECT-TYPE capwapBaseAcWaitJoinTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (20..4294967295)
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, an AC will wait after "Represents the maximum time, in seconds, an AC will wait after
the DTLS session has been established until it receives the the DTLS session has been established until it receives the
Join Request from the WTP. This timer MUST be greater than 20 Join Request from the WTP. This timer MUST be greater than 20
seconds." seconds.
The value of the object is persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseParameters 9 } ::= { 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."
REFERENCE
"Section 4.7.25. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseParameters 10 }
-- End of CAPWAP Base Parameters Group -- End of CAPWAP Base Parameters Group
-- CAPWAP Statistics Group -- CAPWAP Statistics Group
capwapBaseStats OBJECT IDENTIFIER capwapBaseStats OBJECT IDENTIFIER
::= { capwapBaseObjects 4 } ::= { capwapBaseObjects 4 }
capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 51, line 34 skipping to change at page 53, line 16
capwapBaseJoinFailure NOTIFICATION-TYPE capwapBaseJoinFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfJoinFailureReason capwapBaseNtfJoinFailureReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP fails to join." "This notification is generated when a WTP fails to join."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifications 4 } ::= { capwapBaseNotifications 4 }
capwapBaseImageUpgradeFailure NOTIFICATION-TYPE capwapBaseImageUpgradeFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfImageFailureReason capwapBaseNtfImageFailureReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP fails to update "This notification is generated when a WTP fails to update
firmware image." firmware image."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifications 5 } ::= { capwapBaseNotifications 5 }
capwapBaseConfigMsgError NOTIFICATION-TYPE capwapBaseConfigMsgError NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfConfigMsgErrorType, capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements capwapBaseNtfMsgErrorElements
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP received message "This notification is generated when a WTP received message
elements in the configuration management messages which it was elements in the configuration management messages which it was
unable to apply locally." unable to apply locally."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifications 6 } ::= { capwapBaseNotifications 6 }
capwapBaseRadioOperableStatus NOTIFICATION-TYPE capwapBaseRadioOperableStatus NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfRadioId, capwapBaseNtfRadioId,
capwapBaseNtfRadioOperStatusFlag, capwapBaseNtfRadioOperStatusFlag,
capwapBaseNtfRadioStatusCause capwapBaseNtfRadioStatusCause
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification is generated when a radio's operational state "The notification is generated when a radio's operational state
is changed." is changed."
REFERENCE REFERENCE
"Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifications 7 } ::= { capwapBaseNotifications 7 }
capwapBaseAuthenticationFailure NOTIFICATION-TYPE capwapBaseAuthenticationFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod, capwapBaseNtfAuthenMethod,
capwapBaseNtfAuthenFailureReason capwapBaseNtfAuthenFailureReason
} }
STATUS current STATUS current
skipping to change at page 54, line 6 skipping to change at page 55, line 36
rekeyfailure(2), rekeyfailure(2),
acRebootWtp(3), acRebootWtp(3),
dtlsError(4), dtlsError(4),
maxRetransmit(5) maxRetransmit(5)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the reason for Channel down. "Represents the reason for Channel down.
The following enumerated values are supported: The following enumerated values are supported:
timeout(1) - The keep alive is timeout, timeout(1) - The keep alive is timeout
rekeyfailure(2) - Rekey process is failed, channel will be rekeyfailure(2) - Rekey process is failed, channel will be
broken. broken
acRebootWtp(3) - AC reboot WTP. acRebootWtp(3) - AC reboot WTP
dtlsError(4) - DTLS notifications: DTLSAborted, dtlsError(4) - DTLS notifications: DTLSAborted,
DTLSReassemblyFailure, DTLSPeerDisconnect, DTLSReassemblyFailure, DTLSPeerDisconnect,
or frequent DTLSDecapFailure. or frequent DTLSDecapFailure
maxRetransmit(5) - The underlying reliable transport's maxRetransmit(5) - The underlying reliable transport's
RetransmitCount counter has reached the RetransmitCount counter has reached the
MaxRetransmit variable" MaxRetransmit variable"
::= { capwapBaseNotifyVarObjects 5 } ::= { capwapBaseNotifyVarObjects 5 }
capwapBaseNtfStationIdList OBJECT-TYPE capwapBaseNtfStationIdList OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 54, line 42 skipping to change at page 56, line 24
invalidCA(2), invalidCA(2),
micError(3), micError(3),
timeout(4), timeout(4),
unknown(8) unknown(8)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents reason for WTP authorization failure. "Represents reason for WTP authorization failure.
The following enumerated values are supported: The following enumerated values are supported:
keyMismatch(1) - WTP's and AC's key is not matched, keyMismatch(1) - WTP's and AC's key is not matched
invalidCA(2) - ca is not valid, invalidCA(2) - ca is not valid
micError(3) - detect MIC error, micError(3) - detect MIC error
timeout(4) - WaitDTLS Timer is timeout, timeout(4) - WaitDTLS Timer is timeout
unknown(8) - Unknown reason." unknown(8) - Unknown reason"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 7 } ::= { capwapBaseNotifyVarObjects 7 }
capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
reserved(0), operable(0),
operable(1), inoperable(1)
inoperable(2)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the operation status of a radio. "Represents the operation status of a radio.
The following enumerated values are supported: The following enumerated values are supported:
reserved(0) - Reserved operable(0) - To indicate radio is operable
operable(1) - To indicate radio is operable, inoperable(1) - To indicate radio is inoperable, and
inoperable(2) - To indicate radio is inoperable, and
capwapBaseNtfRadioStatusCause object will capwapBaseNtfRadioStatusCause object will
give reason in details." give reason in details"
REFERENCE REFERENCE
"Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 8 } ::= { capwapBaseNotifyVarObjects 8 }
capwapBaseNtfRadioStatusCause OBJECT-TYPE capwapBaseNtfRadioStatusCause OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(0), normal(0),
hwError(1), hwError(1),
swError(2), swError(2),
adminSet(3) adminSet(3)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the reason the radio is out of service. "Represents the reason the radio is out of service.
The following enumerated values are supported: The following enumerated values are supported:
normal(0) - Normal Status, normal(0) - Normal Status
hwError(1) - Radio Failure, hwError(1) - Radio Failure
swError(2) - Software Failure, swError(2) - Software Failure
adminSet(3) - Administratively Set." adminSet(3) - Administratively Set"
REFERENCE REFERENCE
"Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 9 } ::= { capwapBaseNotifyVarObjects 9 }
capwapBaseNtfJoinFailureReason OBJECT-TYPE capwapBaseNtfJoinFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unspecified(1), unspecified(1),
resDepletion(2), resDepletion(2),
unknownSource(3), unknownSource(3),
incorrectData(4), incorrectData(4),
sessionIdInUse(5), sessionIdInUse(5),
notSupportHw(6), notSupportHw(6),
notSupportBinding(7) notSupportBinding(7)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the reason of join failure. "Represents the reason of join failure.
The following enumerated values are supported: The following enumerated values are supported:
unspecified(1) - unspecified failure reason, unspecified(1) - unspecified failure reason
resDepletion(2) - Resource Depletion, resDepletion(2) - Resource Depletion
unknownSource(3) - Unknown Source, unknownSource(3) - Unknown Source
incorrectData(4) - Incorrect Data, incorrectData(4) - Incorrect Data
sessionIdInUse(5) - Session ID already in use, sessionIdInUse(5) - Session ID already in use
notSupportHw(6) - WTP Hardware not supported, notSupportHw(6) - WTP Hardware not supported
notSupportBinding(7) - Binding Not Supported." notSupportBinding(7) - Binding Not Supported"
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 10 } ::= { capwapBaseNotifyVarObjects 10 }
capwapBaseNtfImageFailureReason OBJECT-TYPE capwapBaseNtfImageFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
invalidChecksum(1), invalidChecksum(1),
invalidLength(2), invalidLength(2),
other(3), other(3),
inStorage(4) inStorage(4)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the reason of image failure. "Represents the reason of image failure.
The following enumerated values are supported: The following enumerated values are supported:
invalidChecksum(1) - Invalid Checksum, invalidChecksum(1) - Invalid Checksum
invalidLength(2) - Invalid Data Length, invalidLength(2) - Invalid Data Length
other(3) - Other Error, other(3) - Other Error
inStorage(4) - Image Already Present." inStorage(4) - Image Already Present"
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 11 } ::= { capwapBaseNotifyVarObjects 11 }
capwapBaseNtfConfigMsgErrorType OBJECT-TYPE capwapBaseNtfConfigMsgErrorType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknownElement(1), unknownElement(1),
unsupportedElement(2), unsupportedElement(2),
unknownValue(3), unknownValue(3),
unsupportedValue(4) unsupportedValue(4)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
skipping to change at page 57, line 4 skipping to change at page 58, line 32
SYNTAX INTEGER { SYNTAX INTEGER {
unknownElement(1), unknownElement(1),
unsupportedElement(2), unsupportedElement(2),
unknownValue(3), unknownValue(3),
unsupportedValue(4) unsupportedValue(4)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the type of configuration message error. "Represents the type of configuration message error.
The following enumerated values are supported: The following enumerated values are supported:
unknownElement(1) - Unknown Message Element, unknownElement(1) - Unknown Message Element
unsupportedElement(2) - Unsupported Message Element, unsupportedElement(2) - Unsupported Message Element
unknownValue(3) - Unknown Message Element Value, unknownValue(3) - Unknown Message Element Value
unsupportedValue(4) - Unsupported Message Element Value." unsupportedValue(4) - Unsupported Message Element Value"
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 12 } ::= { capwapBaseNotifyVarObjects 12 }
capwapBaseNtfMsgErrorElements OBJECT-TYPE capwapBaseNtfMsgErrorElements OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the message elements sent by the AC in the "Represents the message elements sent by the AC in the
Configuration Status Response message that caused the error." Configuration Status Response message that caused the error."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 13 } ::= { capwapBaseNotifyVarObjects 13 }
-- Module compliance -- Module compliance
capwapBaseCompliances OBJECT IDENTIFIER capwapBaseCompliances OBJECT IDENTIFIER
::= { capwapBaseConformance 1 } ::= { capwapBaseConformance 1 }
capwapBaseGroups OBJECT IDENTIFIER capwapBaseGroups OBJECT IDENTIFIER
::= { capwapBaseConformance 2 } ::= { capwapBaseConformance 2 }
capwapBaseCompliance MODULE-COMPLIANCE capwapBaseCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
CAPWAP-BASE-MIB." CAPWAP-BASE-MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
capwapBaseAcNodeGroup, capwapBaseAcNodeGroup,
capwapBaseWtpStateGroup, capwapBaseWtpStateGroup,
capwapBaseWtpsGroup, capwapBaseWtpsGroup,
capwapBaseRadiosGroup, capwapBaseRadiosGroup,
capwapBaseStationsGroup capwapBaseStationsGroup
} }
skipping to change at page 58, line 15 skipping to change at page 59, line 44
"The capwapBaseAcNameListGroup group is optional." "The capwapBaseAcNameListGroup group is optional."
GROUP capwapBaseMacAclsGroup GROUP capwapBaseMacAclsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseMacAclsGroup group is optional." "The capwapBaseMacAclsGroup group is optional."
GROUP capwapBaseWtpsGroup2 GROUP capwapBaseWtpsGroup2
DESCRIPTION DESCRIPTION
"The capwapBaseWtpsGroup2 group is optional." "The capwapBaseWtpsGroup2 group is optional."
GROUP capwapBaseWtpRebootStatsGroup GROUP capwapBaseWtpEventsStatsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseWtpRebootStatsGroup group is optional." "The capwapBaseWtpEventsStatsGroup group is optional."
GROUP capwapBaseRadioStatsGroup GROUP capwapBaseRadioEventsStatsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseRadioStatsGroup group is optional." "The capwapBaseRadioEventsStatsGroup group is optional."
GROUP capwapBaseParametersGroup GROUP capwapBaseParametersGroup
DESCRIPTION DESCRIPTION
"The capwapBaseParametersGroup group is optional." "The capwapBaseParametersGroup group is optional."
GROUP capwapBaseStatsGroup GROUP capwapBaseStatsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseStatsGroup group is optional." "The capwapBaseStatsGroup group is optional."
GROUP capwapBaseNotificationGroup GROUP capwapBaseNotificationGroup
DESCRIPTION DESCRIPTION
"The group capwapBaseNotificationGroup is optional." "The group capwapBaseNotificationGroup is optional."
GROUP capwapBaseNotifyVarGroup GROUP capwapBaseNotifyVarGroup
DESCRIPTION DESCRIPTION
"The capwapBaseNotifyVarGroup group is optional. "The capwapBaseNotifyVarGroup group is optional.
If capwapBaseNotificationGroup is supported, If capwapBaseNotificationGroup is supported,
this group must be implemented." this group must be implemented."
OBJECT capwapBaseRadioWirelessBinding
SYNTAX INTEGER { reserved0(0), reserved2(2) }
DESCRIPTION
"A value other than reserved0(0), reserved2(2) need not be
supported if there is no wireless binding defined for
technologies used."
::= { capwapBaseCompliances 1 } ::= { capwapBaseCompliances 1 }
capwapBaseAcNodeGroup OBJECT-GROUP capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpSessions, capwapBaseWtpSessions,
capwapBaseWtpSessionsLimit, capwapBaseWtpSessionsLimit,
capwapBaseStationSessions, capwapBaseStationSessions,
capwapBaseStationSessionsLimit capwapBaseStationSessionsLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
basic properties for AC from CAPWAP protocol perspective." basic properties for AC from CAPWAP protocol perspective."
::= { capwapBaseGroups 1 } ::= { capwapBaseGroups 1 }
capwapBaseAcNodeGroup2 OBJECT-GROUP capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseDataChannelSecOptions, capwapBaseDataChannelDTLSPolicyOptions,
capwapBaseDataChannelSecConfig, capwapBaseDataChannelDTLSPolicyConfig,
capwapBaseControlChannelAuthenOptions, capwapBaseControlChannelAuthenOptions,
capwapBaseControlChannelAuthenConfig capwapBaseControlChannelAuthenConfig
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
other properties such as security for AC from other properties such as security for AC from
CAPWAP protocol perspective." CAPWAP protocol perspective."
::= { capwapBaseGroups 2 } ::= { capwapBaseGroups 2 }
skipping to change at page 60, line 5 skipping to change at page 61, line 26
capwapBaseMacAclRowStatus capwapBaseMacAclRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "The collection of objects which are used to configure
stations ACL." stations ACL."
::= { capwapBaseGroups 4 } ::= { capwapBaseGroups 4 }
capwapBaseWtpStateGroup OBJECT-GROUP capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpIpAddressType, capwapBaseWtpStateWtpIpAddressType,
capwapBaseWtpIpAddress, capwapBaseWtpStateWtpIpAddress,
capwapBaseWtpPhyAddress, capwapBaseWtpStateWtpPhyAddress,
capwapBaseWtpState capwapBaseWtpState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
WTP state information." WTP state information."
::= { capwapBaseGroups 5 } ::= { capwapBaseGroups 5 }
capwapBaseWtpsGroup OBJECT-GROUP capwapBaseWtpsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpName, capwapBaseWtpName,
capwapBaseWtpLocation, capwapBaseWtpLocation,
capwapBaseWtpBaseMacAddress, capwapBaseWtpBaseMacAddress,
capwapBaseTunnelModeOptions, capwapBaseWtpTunnelModeOptions,
capwapBaseMacTypeOptions, capwapBaseWtpMacTypeOptions,
capwapBaseWtpRadiosInUseNum, capwapBaseWtpRadiosInUseNum,
capwapBaseWtpRadioNumLimit capwapBaseWtpRadioNumLimit,
capwapBaseWtpEcnSupport
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
configuration and properties information for WTP configuration and properties information for WTP
in running state." in running state."
::= { capwapBaseGroups 6 } ::= { capwapBaseGroups 6 }
capwapBaseWtpsGroup2 OBJECT-GROUP capwapBaseWtpsGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 60, line 46 skipping to change at page 62, line 20
capwapBaseWtpDiscoveryType, capwapBaseWtpDiscoveryType,
capwapBaseWtpStaticIpEnable, capwapBaseWtpStaticIpEnable,
capwapBaseWtpStaticIpType, capwapBaseWtpStaticIpType,
capwapBaseWtpStaticIp, capwapBaseWtpStaticIp,
capwapBaseWtpNetmask, capwapBaseWtpNetmask,
capwapBaseWtpGateway, capwapBaseWtpGateway,
capwapBaseWtpFallbackEnable, capwapBaseWtpFallbackEnable,
capwapBaseWtpRetransmitCount, capwapBaseWtpRetransmitCount,
capwapBaseWtpMaxDiscoveries, capwapBaseWtpMaxDiscoveries,
capwapBaseWtpMaxFailedDTLSSessionRetry, capwapBaseWtpMaxFailedDTLSSessionRetry,
capwapBaseWtpMaxRetransmitCnt, capwapBaseWtpMaxRetransmit,
capwapBaseWtpDataChannelKeepAliveTimer, capwapBaseWtpDataChannelKeepAliveTimer,
capwapBaseWtpDataChannelDeadInterval, capwapBaseWtpDataChannelDeadInterval,
capwapBaseWtpDiscoveryInterval, capwapBaseWtpDiscoveryInterval,
capwapBaseWtpDTLSSessionDeleteTimer, capwapBaseWtpDTLSSessionDeleteTimer,
capwapBaseWtpEchoInterval, capwapBaseWtpEchoInterval,
capwapBaseWtpIdleTimeout, capwapBaseWtpIdleTimeout,
capwapBaseWtpImageDataStartTimer, capwapBaseWtpImageDataStartTimer,
capwapBaseWtpMaxDiscoveryInterval, capwapBaseWtpMaxDiscoveryInterval,
capwapBaseWtpReportInterval, capwapBaseWtpReportInterval,
capwapBaseWtpRetransmitInterval, capwapBaseWtpRetransmitInterval,
skipping to change at page 61, line 22 skipping to change at page 62, line 44
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
configuration and properties information for WTP configuration and properties information for WTP
in running state." in running state."
::= { capwapBaseGroups 7 } ::= { capwapBaseGroups 7 }
capwapBaseRadiosGroup OBJECT-GROUP capwapBaseRadiosGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseVirtualRadioIfIndex, capwapBaseWirelessBindingVirtualRadioIfIndex,
capwapBaseRadioWirelessBinding capwapBaseWirelessBindingType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
wireless binding type, the mapping relationship between wireless binding type, the mapping relationship between
'WLAN Virtual Radio Interface' and PHY radio." 'WLAN Virtual Radio Interface' and PHY radio."
::= { capwapBaseGroups 8 } ::= { capwapBaseGroups 8 }
capwapBaseStationsGroup OBJECT-GROUP capwapBaseStationsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseStationAddedTime, capwapBaseStationAddedTime,
capwapBaseStationVlanName capwapBaseStationVlanName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
stations' basic property." stations' basic property."
::= { capwapBaseGroups 9 } ::= { capwapBaseGroups 9 }
capwapBaseWtpRebootStatsGroup OBJECT-GROUP capwapBaseWtpEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpRebootCount, capwapBaseWtpEventsStatsRebootCount,
capwapBaseWtpInitCount, capwapBaseWtpEventsStatsInitCount,
capwapBaseWtpLinkFailureCount, capwapBaseWtpEventsStatsLinkFailureCount,
capwapBaseWtpSwFailureCount, capwapBaseWtpEventsStatsSwFailureCount,
capwapBaseWtpHwFailureCount, capwapBaseWtpEventsStatsHwFailureCount,
capwapBaseWtpOtherFailureCount, capwapBaseWtpEventsStatsOtherFailureCount,
capwapBaseWtpUnknownFailureCount, capwapBaseWtpEventsStatsUnknownFailureCount,
capwapBaseWtpLastFailureType capwapBaseWtpEventsStatsLastFailureType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "The collection of objects which are used for collecting
WTP reboot count, link failure count, hardware failure WTP reboot count, link failure count, hardware failure
count and so on." count and so on."
::= { capwapBaseGroups 10 } ::= { capwapBaseGroups 10 }
capwapBaseRadioStatsGroup OBJECT-GROUP capwapBaseRadioEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseRadioResetCount, capwapBaseRadioEventsStatsResetCount,
capwapBaseRadioSwFailCount, capwapBaseRadioEventsStatsSwFailCount,
capwapBaseRadioHwFailCount, capwapBaseRadioEventsStatsHwFailCount,
capwapBaseRadioOtherFailCount, capwapBaseRadioEventsStatsOtherFailCount,
capwapBaseRadioUnknownFailCount, capwapBaseRadioEventsStatsUnknownFailCount,
capwapBaseRadioConfigUpdateCount, capwapBaseRadioEventsStatsConfigUpdateCount,
capwapBaseRadioChannelChangeCount, capwapBaseRadioEventsStatsChannelChangeCount,
capwapBaseRadioBandChangeCount, capwapBaseRadioEventsStatsBandChangeCount,
capwapBaseRadioCurrentNoiseFloor, capwapBaseRadioEventsStatsCurrentNoiseFloor,
capwapBaseRadioDecryptErrorCount, capwapBaseRadioEventsStatsDecryptErrorCount,
capwapBaseRadioLastFailType capwapBaseRadioEventsStatsLastFailType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "The collection of objects which are used for collecting
radio reset count, channel change count, hardware failure radio reset count, channel change count, hardware failure
count and so on" count and so on"
::= { capwapBaseGroups 11 } ::= { capwapBaseGroups 11 }
capwapBaseParametersGroup OBJECT-GROUP capwapBaseParametersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseAcMaxRetransmitCnt, capwapBaseAcMaxRetransmit,
capwapBaseAcChangeStatePendingTimer, capwapBaseAcChangeStatePendingTimer,
capwapBaseAcDataCheckTimer, capwapBaseAcDataCheckTimer,
capwapBaseAcDTLSSessionDeleteTimer, capwapBaseAcDTLSSessionDeleteTimer,
capwapBaseAcEchoInterval, capwapBaseAcEchoInterval,
capwapBaseAcRetransmitInterval, capwapBaseAcRetransmitInterval,
capwapBaseAcSilentInterval, capwapBaseAcSilentInterval,
capwapBaseAcWaitDTLSTimer, capwapBaseAcWaitDTLSTimer,
capwapBaseAcWaitJoinTimer capwapBaseAcWaitJoinTimer,
capwapBaseAcEcnSupport
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for CAPWAP protocol."
::= { capwapBaseGroups 12 } ::= { capwapBaseGroups 12 }
capwapBaseStatsGroup OBJECT-GROUP capwapBaseStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseFailedDTLSAuthFailCount, capwapBaseFailedDTLSAuthFailCount,
capwapBaseFailedDTLSSessionCount capwapBaseFailedDTLSSessionCount
skipping to change at page 63, line 26 skipping to change at page 64, line 49
capwapBaseChannelDown, capwapBaseChannelDown,
capwapBaseDecryptErrorReport, capwapBaseDecryptErrorReport,
capwapBaseJoinFailure, capwapBaseJoinFailure,
capwapBaseImageUpgradeFailure, capwapBaseImageUpgradeFailure,
capwapBaseConfigMsgError, capwapBaseConfigMsgError,
capwapBaseRadioOperableStatus, capwapBaseRadioOperableStatus,
capwapBaseAuthenticationFailure capwapBaseAuthenticationFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of notifications in this MIB." "The Collection of notifications in this MIB module."
::= { capwapBaseGroups 14 } ::= { capwapBaseGroups 14 }
capwapBaseNotifyVarGroup OBJECT-GROUP capwapBaseNotifyVarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfRadioId, capwapBaseNtfRadioId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod, capwapBaseNtfAuthenMethod,
capwapBaseNtfChannelDownReason, capwapBaseNtfChannelDownReason,
capwapBaseNtfStationIdList, capwapBaseNtfStationIdList,
skipping to change at page 64, line 17 skipping to change at page 65, line 40
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. The followings are the tables and objects and network operations. The followings are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
- Unauthorized changes to the capwapBaseWtpTable, writable objects - Unauthorized changes to the capwapBaseWtpTable, writable objects
under capwapBaseAcs group may disrupt allocation of resources in the under capwapBaseAcs group may disrupt allocation of resources in the
network. For example, a WTP's static Ip address could be changed by network. For example, a WTP's static IP address could be changed by
set capwapBaseWtpStaticIp object. set capwapBaseWtpStaticIp object.
- Unauthorized changes to writable objects under the capwapBaseAc - Unauthorized changes to writable objects under the capwapBaseAc
group, it may disrupt allocation of resources in the network. For group, it may disrupt allocation of resources in the network. For
example, a invalid value for capwapBaseWtpSessionsLimit object will example, a invalid value for capwapBaseWtpSessionsLimit object will
increase AC's traffic burden. Also, some objects such as increase AC's traffic burden. Also, some objects such as
capwapBaseDataChannelSecConfig may cause network unsafe. capwapBaseDataChannelDTLSPolicyConfig may cause network unsafe.
- Unauthorized changes to the capwapBaseMacAclTable, it may cause - Unauthorized changes to the capwapBaseMacAclTable, it may cause
legal stations could not access network any more while illegal legal stations could not access network any more while illegal
stations have chance to access network. stations have chance to access network.
- Unauthorized changes to writable objects under the - Unauthorized changes to writable objects under the
capwapBaseParameters group, it may influence CAPWAP protocol capwapBaseParameters group, it may influence CAPWAP protocol
behaviour and status. For example, the invalid value for behaviour and status. For example, the invalid value for
capwapBaseAcDataCheckTimer may influence CAPWAP state machine. capwapBaseAcDataCheckTimer may influence CAPWAP state machine.
Some of the readable objects in this MIB module (i.e., objects with a 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 MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. The followings are the tables and objects and the network via SNMP. The followings are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
- The capwapBaseDataChannelSecOptions and - The capwapBaseDataChannelDTLSPolicyOptions and
capwapBaseControlChannelAuthenOptions under the capwapBaseAc group capwapBaseControlChannelAuthenOptions under the capwapBaseAc group
exposes the current security option for CAPWAP data and control exposes the current security option for CAPWAP data and control
channel. channel.
- The capwapBaseWtpTable exposes WTP's important information like IP - The capwapBaseWtpTable exposes WTP's important information like IP
address, MAC type and so on. address, MAC type and so on.
- The capwapBaseWtpRebootStatTable exposes WTP's failure information. - The capwapBaseWtpEventsStatsTable exposes WTP's failure
information.
- The capwapBaseRadioStatsTable exposes radio's failure information. - The capwapBaseRadioEventsStatsTable exposes radio's failure
information.
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
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
skipping to change at page 65, line 28 skipping to change at page 67, line 7
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
12. IANA Considerations 12. IANA Considerations
12.1. IANA Considerations for CAPWAP-BASE-MIB 12.1. IANA Considerations for CAPWAP-BASE-MIB module
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
capwapBaseMIB { mib-2 XXX } capwapBaseMIB { mib-2 XXX }
12.2. IANA Considerations for ifType 12.2. IANA Considerations for ifType
Require IANA to assign a ifType for 'WTP Virtual Radio Interface' Require IANA to assign a ifType for 'WTP Virtual Radio Interface'
type. type.
13. Contributors 13. Contributors
This MIB is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
14. Acknowledgements 14. Acknowledgements
The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin The authors wish to thank David Harrington, Fei Fang, Yu Liu, Sachin
Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. Dutta, Ju Wang, Yujin Zhao, Haitao Zhang.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for [RFC2119] Bradner, S., "Key words
use in RFCs to Indicate for use in RFCs to
Requirement Levels", Indicate Requirement
BCP 14, RFC 2119, Levels", BCP 14,
March 1997. RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., [RFC2578] McCloghrie, K., Ed.,
Perkins, D., Ed., and J. Perkins, D., Ed., and
Schoenwaelder, Ed., J. Schoenwaelder, Ed.,
"Structure of Management "Structure of
Information Version 2 Management Information
(SMIv2)", STD 58, RFC 2578, Version 2 (SMIv2)",
STD 58, RFC 2578,
April 1999. April 1999.
[RFC2579] McCloghrie, K., Ed., [RFC2579] McCloghrie, K., Ed.,
Perkins, D., Ed., and J. Perkins, D., Ed., and
Schoenwaelder, Ed., J. Schoenwaelder, Ed.,
"Textual Conventions for "Textual Conventions
SMIv2", STD 58, RFC 2579, for SMIv2", STD 58,
April 1999. RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, [RFC2580] McCloghrie, K.,
D., and J. Schoenwaelder, Perkins, D., and J.
"Conformance Statements for Schoenwaelder,
SMIv2", STD 58, RFC 2580, "Conformance Statements
April 1999. for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. [RFC2863] McCloghrie, K. and F.
Kastenholz, "The Interfaces Kastenholz, "The
Group MIB", RFC 2863, Interfaces Group MIB",
June 2000. RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management [RFC3411] Harrington, D.,
Information Base (MIB) for Presuhn, R., and B.
the Simple Network Wijnen, "An
Architecture for
Describing Simple
Network Management
Protocol (SNMP)
Management Frameworks",
STD 62, RFC 3411,
December 2002.
[RFC3418] Presuhn, R.,
"Management Information
Base (MIB) for the
Simple Network
Management Protocol Management Protocol
(SNMP)", STD 62, RFC 3418, (SNMP)", STD 62,
RFC 3418,
December 2002. December 2002.
[RFC4001] Daniele, M., Haberman, B., [RFC4001] Daniele, M., Haberman,
Routhier, S., and J. B., Routhier, S., and
Schoenwaelder, "Textual J. Schoenwaelder,
Conventions for Internet "Textual Conventions
Network Addresses", for Internet Network
RFC 4001, February 2005. Addresses", RFC 4001,
February 2005.
[RFC4133] Bierman, A. and K. [RFC4133] Bierman, A. and K.
McCloghrie, "Entity MIB McCloghrie, "Entity MIB
(Version 3)", RFC 4133, (Version 3)", RFC 4133,
August 2005. August 2005.
[I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley, [I-D.ietf-capwap-protocol-specification] Montemurro, M.,
D., and P. Calhoun, "CAPWAP Stanley, D., and P.
Protocol Specification", dr Calhoun, "CAPWAP
aft-ietf-capwap-protocol- Protocol
specification-14 (work in Specification", draft-
progress), October 2008. ietf-capwap-protocol-
specification-15 (work
in progress),
November 2008.
15.2. Informative References 15.2. Informative References
[RFC3410] Case, J., Mundy, R., [RFC3410] Case, J., Mundy, R.,
Partain, D., and B. Partain, D., and B.
Stewart, "Introduction and Stewart, "Introduction
Applicability Statements and Applicability
for Internet-Standard Statements for
Internet-Standard
Management Framework", Management Framework",
RFC 3410, December 2002. RFC 3410,
December 2002.
Appendix A. Appendix A. Changes from -02 [RFC4118] Yang, L., Zerfos, P.,
and E. Sadot,
"Architecture Taxonomy
for Control and
Provisioning of
Wireless Access Points
(CAPWAP)", RFC 4118,
June 2005.
1) Section 9 is added to describe CAPWAP Message Element Extension [RFC4347] Rescorla, E. and N.
Modadugu, "Datagram
Transport Layer
Security", RFC 4347,
April 2006.
2) In the Section 10, the MIB objects (such as [IEEE.802-11.2007] "Information technology
capwapBaseWtpSilentInterval) are added into capwapBaseWtpTable and - Telecommunications
capwapBaseParameters to manage CAPWAP protocol timers and variables. and information
Rename object capwapBaseMaxStationSessionsConfig as exchange between
capwapBaseStationSessionsLimit and capwapBaseMaxWtpSessionsConfig as systems - Local and
capwapBaseWtpSessionsLimit. metropolitan area
networks - Specific
requirements - Part 11:
Wireless LAN Medium
Access Control (MAC)
and Physical Layer
(PHY) specifications",
IEEE Standard 802.11,
2007, <http://
standards.ieee.org/
getieee802/download/
802.11-2007.pdf>.
3) Section 11 is updated for capwapBaseParameters group, capwapBaseAc [I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M.,
group and capwapBaseMacAclTable to describe the security Stanley, D., and P.
considerations for them. Calhoun, "CAPWAP
Protocol Binding for
IEEE 802.11", draft-
ietf-capwap-protocol-
binding-ieee80211-12
(work in progress),
November 2008.
4) Appendix is added to log the changes happened between versions. [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D.,
Elliott, C., and Y.
Zhang, "CAPWAP Protocol
Binding MIB for IEEE
802.11", draft-ietf-
capwap-802dot11-mib-02
(work in progress),
October 2008.
Appendix A. Appendix A. Changes between -04 and -03
T1. Running smilint results in the following errors:
mibs/CAPWAP-BASE-MIB:480: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseWtpStateEntry' can exceed OID size limit by 6
subidentifier(s)
mibs/CAPWAP-BASE-MIB:582: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseWtpEntry' can exceed OID size limit by 6
subidentifier(s)
mibs/CAPWAP-BASE-MIB:1090: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseRadioBindEntry' can exceed OID size limit by 7
subidentifier(s)
mibs/CAPWAP-BASE-MIB:1181: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseStationEntry' can exceed OID size limit by 13
subidentifier(s)
mibs/CAPWAP-BASE-MIB:1249: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseWtpRebootStatsEntry' can exceed OID size limit by 6
subidentifier(s)
mibs/CAPWAP-BASE-MIB:1408: [5] {index-exceeds-too-large} warning: index
of row `capwapBaseRadioStatsEntry' can exceed OID size limit by 7
subidentifier(s)
The reason is that these tables are indexed with objects of SYNTAX of
CapwapBaseWtpIdTC which has a maximal size of 128, equal to the maximal
size allowed for the whole OID. Reducing the maximal size of the TC to
anything less or equal than 115 solves the problem.
--------------------------------------------------------------
Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define
CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32))
IF we use SnmpAdminString (SIZE (0..32)), libsmi would generate
error: textual convention `CapwapBaseWtpIdTC' can not be derived from
the textual convention `SnmpAdminString'
T2. Section 5 - ' To reuse current MIB standards and future
extensions for a wireless binding technology' - it is not clear what
'future extensions' may be and I would not commit to using them in
advance, so I would suggest to drop this
-------------------------------------------------------------
Change it into " To be independent of any wireless technologies and
have ability to reuse wireless binding MIB modules defined by other
SDOs;"
T3 What are the 'MIB standards of other SDOs' that need to be reused?
Please refer to them specifically at least by providing one example -
for instance where does Dot11OperationTable come from?
--------------------------------------------------------------
It is changed into:
The text give a definition of " 5.2. Wireless Binding MIB Modules"
For Dot11OperationTable, the chang is:
For example, the MIB tables such as Dot11OperationTable [IEEE.802-
11.2007] are able to support WTP radio configuration.
T4. In order for ifIndex to be used as a common handler for the
CAPWAP MIB and for the interface specific MIB modules like a dot11
MIB from IEEE one needs to ensure that the same numbering scheme and
mapping is used by all MIB modules, and that it behaves identically
for events like interface card swapping, reset or power loss. I do
not see how this can happen, I am not sure that this is possible at
all, and in any case there is no text in the CAPWAP MIB that explains
this mechanism.
--------------------------------------------------------------
in the Capwap Digest, Vol 39, Issue 4, we gave the text to explain a
mechanism that preserves the values of ifIndex, Request mailing list
to confirm it.
In the section of "Relationship to the IF-MIB", add text "Also, as
ifIndex[RFC2863] will be used as common handler for corresponding
interfaces in the CAPWAP-BASE-MIB and specific wireless technologies
MIB modules, the system (AC) MUST have a mechanisms that preserves
the values of ifIndex in the ifTable at AC reboot."
T5. Section 7.2 - 'The interface SHOULD be modeled as an ifEntry' -
Is a SHOULD enough or rather a MUST is required here taking into
account the requirements in Section 5.
-----------------------------------------------------------------
It is changed into:MUST be
T6. The documents that define the MIB modules required for IMPORTs
must be listed in the Normative References section.
-----------------------------------------------------------------
add reference to RFC3411 in the section of "MIB modules required for
IMPORTS", add "SNMP-FRAMEWORK-MIB [RFC3411],"
T7. In the example in Section 8 capwapBaseWtpId equals the
representation of the OCTET STRING '12345678' and not the number
12345678
----------------------------------------------------------------
Yes, it is change into '12345678'
T8. In the example in Section 8 ifPhysicalAddress should have six
zeros.
-----------------------------------------------------------------
Yes, it is change into '000000'
T9. What is the Vendor Identifier mentioned in Section 9 as being
assigned by IANA? Is this something specific for this MIB document -
in this case it needs to be mentioned in the IANA considerations
section?
-----------------------------------------------------------------
The description of Vendor Identifie is changed into: Vendor
Identifier: A 32-bit value containing the IANA assigned "SMI Network
Management Private Enterprise Codes"
T10. Why does one need a special TC for CapwapBaseWtpIdTC? If this
is typically a serial number, then SnmpAdminString SIZE (1..128)
should do.
-----------------------------------------------------------------
Station, radio, WTP are main objects to management by MIB drafts.
They would appear in the serval table and notification. Suggest to
have a TC for them.
T11. In any case why is the SIZE in this TC fixed at 128?
-----------------------------------------------------------------
Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define
CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32))
T12. A number of read-write objects do not have the persistency
behavior defined in case of agent reboot -
capwapBaseStationSessionsLimit, capwapBaseDataChannelSecConfig,
capwapBaseControlChannelAuthenConfig
-----------------------------------------------------------------
Add the "The value of the object is persistent at restart/reboot." in
the description of
capwapBaseAcMaxRetransmit,capwapBaseAcChangeStatePendingTimer, capwap
BaseAcDataCheckTimer,capwapBaseAcDTLSSessionDeleteTimer,capwapBaseAcE
choInterval, capwapBaseAcWaitJoinTimer,
capwapBaseAcWaitDTLSTimer,capwapBaseAcSilentInterval,
capwapBaseAcRetransmitInterval
T13 - Is more than one security policy possible to be configured on a
given AC? If not, then why is capwapBaseDataChannelSecConfig a BIT?
-----------------------------------------------------------------
Yes, the data type of capwapBaseDataChannelSecConfig should be
INTEGER
T14 - the name of capwapBaseDataChannelSecOptions should better be
something that includes DTLSPolicy to make clear to what fields in
the AC Descriptor it corresponds. The DESCRIPTION should also be
consistent with the text in the protocol document
-----------------------------------------------------------------
To make it consistent with protocol, change
capwapBaseDataChannelSecOptions with
capwapBaseDataChannelDTLSPolicyOptions. Change
capwapBaseDataChannelSecConfig with
capwapBaseDataChannelDTLSPolicyConfig Also, the DESCRIPTION should
also be consistent with the text in the protocol document
T15 - is more than one credential type possible to be configured on a
given AC? If not then why is capwapBaseControlChannelAuthenConfig a
BIT?
-----------------------------------------------------------------
Yes, the data type of capwapBaseControlChannelSecConfig should be
INTEGER
T16 - it would be good for management applications writers to mention
in the DESCRIPTION clause thatcapwapBaseAcnameListName is expected to
be a UTF-8 encoded string
-----------------------------------------------------------------
Yes, it is added
T17 - Object names in capwapBaseWtpStateTable do not respect the
naming conditions relative to capwapBaseWtpStateEntry
---------------------------------------------------------------
Add one more WtpState in the object name. For example,
capwapBaseWtpId is to changed into capwapBaseWtpStateWtpId, other
objects are similiar.
all objects with new name:
CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpStateWtpIpAddressType InetAddressType,
capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpStateWtpPhyAddress PhysAddress,
capwapBaseWtpState INTEGER
}
T18 - same for capwapBaseWtpStateTable
-----------------------------------------------------------------
Same as above
T19 - capwapBaseWtpName is of SYNTAX AsnmpAdminString which is
limited to SIZE 255, while the WTP name can be up to 512 characters
--------------------------------------------------------------
change with OCTET STRING(SIZE(512))
T20 - same about capwapbaseWtpLocation which can be up to 1024
characters in length
-----------------------------------------------------------------
change with OCTET STRING(SIZE(1024))
T21 - Section 4.8 defines default value for a number of variables.
However, these are not reflected in the MIB - for example why is
there not a DEFAULT clause that will set capwapBaseWtpFallbackEnable
to enabled(1) as per 4.8.9? Or capwapBaseWtpMaxDiscoveries which has
a default of 10 defined in 4.8.5
-------------------------------------------------------------------
Added DEFVAL { enabled } for capwapBaseWtpFallbackEnable.
capwapBaseWtpMaxDiscoveries already has DEFVAL { 10 }.
T22 - why does the MIB support reserved(0) for
capwapBaseWtpFallbackEnable. Does setting to reserved(0) by the
management application have any significance?
-----------------------------------------------------------------
The reserved(0) is removed for capwapBaseWtpFallbackEnable
T23 - According to 4.8.8 capwapBaseWtpRetransmitCount is a monotonous
increasing counter. The appropriate SYNTAX for such an object is
Counter32 and not Unsigned32
-----------------------------------------------------------------
Yes, capwapBaseWtpRetransmitCount should use Counter32
T24 - it would be useful to define UNITS clauses for objects like
capwapBaseWtpRetransmitCount
-----------------------------------------------------------------
It seemed capwapBaseWtpRetransmitCount does not require a UNIT.
T25 - define a range (2..180) for capwapBaseWtpMaxDiscoveryInterval
----------------------------------------------------------------
add value scope of (0..24) to capwapBaseWtpDataChannelDeadInterval
add value scope of (2..180) to capwapBaseWtpMaxDiscoveryInterval
add value scope of (30..4294967295) to capwapBaseWtpWaitDTLSTimer
add value scope of (30..4294967295) to capwapBaseAcWaitDTLSTimer
add value scope of (20..4294967295) to capwapBaseAcWaitJoinTimer
T27 - Object names in capwapBaseRadioBindTable do not respect the
naming conditions relative to capwapBaseRadioBindEntry
--------------------------------------------------------------------
Change all objects (entry, table)'s prefix from capwapBaseRadioBind
to capwapBaseWirelessBinding.
change CapwapBaseRadioBindTable to CapwapBaseWirelessBindingTable
The Objects with new name:
CapwapBaseWirelessBindingEntry ::= SEQUENCE {
capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC,
capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex,
capwapBaseWirelessBindingType INTEGER
}
T28 - What do the values reserved(0) and reserved(2) in
capwapBaseRadioWirelessBinding mean? Are they ever returned by an
agent?
-----------------------------------------------------------------
removed the reserved(0) and reserved(2) from the object definition.
T29 - in other IETF documents (like RFC 4363) VLAN names are defined
as SnmpAdminString (SIZE (0..32)). I suggest the same for
capwapBaseStationVlanName. I am aware that section 4.6.8 allows for
names up to 512, but I do not find this justified. In any case, if
the full size defined in 4.6.8 is to be accommodated, then
SnmpAdminString would not be sufficient as its size is limited to
256.
-----------------------------------------------------------------
capwapBaseStationVlanName use SnmpAdminString (SIZE (0..32))
T30 - Object names in capwapBaseWtpRebootStatsTable do not respect
the naming conditions relative to capwapBaseWtpRebootStatsEntry
------------------------------------------------------------------
Change table name from capwapBaseWtpRebootStatTable to
capwapBaseWtpEventsStatsTable.
The objects also do similar changes, for example, change
capwapBaseWtpRebootCount to capwapBaseWtpEventsStatsRebootCount
The objects with new name:
CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
capwapBaseWtpEventsStatsRebootCount Counter32,
capwapBaseWtpEventsStatsInitCount Counter32,
capwapBaseWtpEventsStatsLinkFailureCount Counter32,
capwapBaseWtpEventsStatsSwFailureCount Counter32,
capwapBaseWtpEventsStatsHwFailureCount Counter32,
capwapBaseWtpEventsStatsOtherFailureCount Counter32,
capwapBaseWtpEventsStatsUnknownFailureCount Counter32,
capwapBaseWtpEventsStatsLastFailureType INTEGER
}
T31 - Object names in capwapBaseWtpRadioStatsTable do not respect the
naming conditions relative to capwapBaseWtpRadioStatsEntry
----------------------------------------------------------------
Change table name from capwapBaseWtpRadioStatsTable to
capwapBaseRadioEventsStatsTable. The objects also do similar
changes, for example, change capwapBaseRadioSwFailCount to
capwapBaseRadioEventsStatsSwFailCount.
The objects with new name:
CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
capwapBaseRadioEventsStatsResetCount Counter32,
capwapBaseRadioEventsStatsSwFailCount Counter32,
capwapBaseRadioEventsStatsHwFailCount Counter32,
capwapBaseRadioEventsStatsOtherFailCount Counter32,
capwapBaseRadioEventsStatsUnknownFailCount Counter32,
capwapBaseRadioEventsStatsConfigUpdateCount Counter32,
capwapBaseRadioEventsStatsChannelChangeCount Counter32,
capwapBaseRadioEventsStatsBandChangeCount Counter32,
capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32,
capwapBaseRadioEventsStatsDecryptErrorCount Counter32,
capwapBaseRadioEventsStatsLastFailType INTEGER
}
E1. Even if this document uses terminology borrowed from other
CAPWAP documents, acronyms like WTP, AC, etc. should be expanded at
the first occurrence.
-----------------------------------------------------------------
The Terminology section is updated with more Terminology such as
Autonomous WLAN Architecture, Centralized WLAN Architecture, Wireless
Binding,Split and Local MAC and so on.
E2. It would be good for the document to be grammar and spelling
checked by a native English speaker.
E3. No need for sections 6.1, 6.2, 6.3 - these are standard in any
MIB module and their content is well known
-----------------------------------------------------------------
Ok, there are removed
E4. In Section 7.2 there is no need to mention information that is
not specific to the CAPWAP MIB
--------------------------------------------------------------------
Removed the "Some specific interpretations of ifTable for CAPWAP-
BASE-MIB are as follow." and the interpretations followed it.
E5. In the example in Section 8 ifType should be equal with the
value assigned by IANA for the ifType - you may mark it xxx and enter
an editor note saying 'RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WTP Virtual Radio Interface')
-----------------------------------------------------------------
It is done according to the comment
E6. Please indicate specifically for each field for the protocols
timers message the exact reference in than CAPWAP protocol document.
-----------------------------------------------------------------
The section was updated according to protocol
E7. The numbering of referred paragraphs in the REFERENCE clauses
are not synchronized with the latest version of the CAPWAP protocol
document as per http://www.rfc-editor.org/rfc/rfc3411.txt
-------------------------------------------------------------------
The REFERENCE clauses for the following TCs or objects are changed
with new id:
CapwapBaseTunnelModeTC
Section 4.6.42 to Section 4.6.43
CapwapBaseMacTypeTC
Section 4.6.43 to Section 4.6.44
capwapBaseWtpName
Section 4.6.44 to Section 4.6.45
capwapBaseWtpLocation
Section 4.6.29 to Section 4.6.30
capwapBaseWtpBaseMacAddress
Section 4.6.39 to Section 4.6.40
capwapBaseTunnelModeOptions
Section 4.6.42 to Section 4.6.43
capwapBaseMacTypeOptions
Section 4.6.43 to Section 4.6.44
capwapBaseWtpRadiosInUseNum and capwapBaseWtpRadioNumLimit
Section 4.6.40 to Section 4.6.41
capwapBaseWtpStaticIpEnable, capwapBaseWtpStaticIp,
capwapBaseWtpNetmask,capwapBaseWtpGateway
Section 4.6.47 to Section 4.6.48
capwapBaseWtpFallbackEnable
Section 4.6.41 to Section 4.6.42
all the objects in the capwapBaseWtpRebootStatsTable
Section 4.6.46 to Section 4.6.47
all the objects in the capwapBaseRadioStatsTable
Section 4.6.45 to Section 4.6.46
capwapBaseJoinFailure,capwapBaseImageUpgradeFailure,
capwapBaseConfigMsgError
Section 4.6.34 to Section 4.6.35
capwapBaseRadioOperableStatus,capwapBaseNtfRadioOperStatusFlag,
capwapBaseNtfRadioStatusCause
Section 4.6.33 to Section 4.6.34
capwapBaseNtfJoinFailureReason,capwapBaseNtfImageFailureReason
Section 4.6.34 to Section 4.6.35
capwapBaseNtfConfigMsgErrorType,capwapBaseNtfMsgErrorElements
Section 4.6.35 to Section 4.6.36
E8. No need to repeat the text in the DESCRIPTION clause if a TC is
used (e.g. capwapBaseTunnelModeOption, capwapBaseMacTypeOptions)
----------------------------------------------------------------
Change the description of them, and only talk about the function of
objects.
E9 - capwapBaseWtpMaxRetransmitCnt is not a counter so the suffix Cnt
should be dropped from the name.
-------------------------------------------------------------------
Change capwapBaseWtpMaxRetransmitCnt into capwapBaseWtpMaxRetransmit
E10 - capwapBaseAcMaxRetransmitCnt is not a counter so the suffix Cnt
should be dropped from the name.
-------------------------------------------------------------------
Change capwapBaseAcMaxRetransmitCnt into capwapBaseAcMaxRetransmit
Other changes made by authors:
1) To keep Terminology consistent
change "MIBs" with "MIB modules", change "MIB standards" with "MIB
modules".
2) Replace "As a generic mechanism, it is independent of any wireless
technologies and defined by an independent MIB file" with
"It is designed to accommodate the specific needs of each wireless
technology in a standard way. It is independent of any wireless
technologies;"
3) add reference to [IEEE.802-11.2007],[I-D.ietf-capwap-protocol-binding
-ieee80211] and [I-D.ietf-capwap-802dot11-mib]
4) Respect the naming conditions to capwapBaseWtpTable,
change capwapBaseMacTypeOptions to capwapBaseWtpMacTypeOptions
change capwapBaseTunnelModeOptions to capwapBaseWtpTunnelModeOptions
5) Change IPV6 to IPv6, IPV4 to IPv4
6) remove redundant "the" in the R"Represents the the next"
7) reorganized the section of overview, and divided it into the
following sub sections:
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
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
Especially, add the Terminology of "CAPWAP Protocol Wireless Binding
MIB Module" and "Wireless Binding MIB Module".
8) Remove unused(0) from CapwapBaseTunnelModeTC,
capwapBaseControlChannelAuthenOptions
and capwapBaseControlChannelAuthenConfig
9) Update some words in the section of" Example of CAPWAP-BASE-MIB
Module Usage"
10) Added capwapBaseAcEcnSupport, capwapBaseWtpEcnSupport
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
H3C Tech. Co., Ltd H3C Tech. Co., Ltd
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District,
Beijing Beijing
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
skipping to change at page 69, line 4 skipping to change at line 3839
Phone: +1 919-392-2146 Phone: +1 919-392-2146
EMail: chelliot@cisco.com EMail: chelliot@cisco.com
Yong Zhang (editor) Yong Zhang (editor)
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
EMail: yzhang@fortinet.com EMail: yzhang@fortinet.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 336 change blocks. 
755 lines changed or deleted 1406 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/