draft-ietf-capwap-base-mib-04.txt   draft-ietf-capwap-base-mib-05.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft Hangzhou H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: September 1, 2009 SNMPinfo Expires: November 30, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
February 28, 2009 May 29, 2009
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-04 draft-ietf-capwap-base-mib-05
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 September 1, 2009. This Internet-Draft will expire on November 30, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. 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 the managed objects for modeling the Control And
of Wireless Access Points (CAPWAP) Protocol. Provisioning 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4
5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5
5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5
5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6
5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6
5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7
5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 8 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 8 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9
7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9
7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 9 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10 8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10
9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14
9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 13 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14
9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 16 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17
9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 16 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17
9.3.1. Configuration Status Response Message . . . . . . . . 16 9.3.1. Configuration Status Response Message . . . . . . . . 17
9.3.2. Configuration Update Response Message . . . . . . . . 17 9.3.2. Configuration Update Response Message . . . . . . . . 18
10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 65 11. Security Considerations . . . . . . . . . . . . . . . . . . . 70
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71
12.1. IANA Considerations for CAPWAP-BASE-MIB module . . . . . . 67 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 71
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 67 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 71
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 67 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 71
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
15.1. Normative References . . . . . . . . . . . . . . . . . . . 67 15.1. Normative References . . . . . . . . . . . . . . . . . . . 72
15.2. Informative References . . . . . . . . . . . . . . . . . . 69 15.2. Informative References . . . . . . . . . . . . . . . . . . 73
Appendix A. Appendix A. Changes between -04 and -03 . . . . . . . 71 Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 74
1. Introduction 1. Introduction
The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP Protocol [RFC5415] defines a standard, interoperable
a standard, interoperable protocol, which enables an Access protocol, which enables an Access Controller (AC) to manage a
Controller (AC) to manage a collection of Wireless Termination 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 the
implementations. This MIB module covers both configuration and WTP CAPWAP implementations. This MIB module covers both configuration
status-monitoring aspects of CAPWAP, and provides a way to reuse MIB and WTP status-monitoring aspects of CAPWAP, and provides a way to
modules for any wireless technology. reuse MIB modules for any wireless 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 CAPWAP Protocol specification This document uses terminology from the CAPWAP Protocol specification
[I-D.ietf-capwap-protocol-specification] and the Architecture [RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118].
Taxonomy for CAPWAP [RFC4118].
Access Controller (AC): The network entity that provides WTP access Access Controller (AC): The network entity that provides WTP access
to the network infrastructure in the data plane, control plane, to the network infrastructure in the data plane, control plane,
management plane, or a combination therein. management plane, or a combination therein.
Wireless Termination Point (WTP): The physical or network entity that Wireless Termination Point (WTP): The physical or network entity that
contains an RF antenna and wireless PHY to transmit and receive contains an RF antenna and wireless PHY to transmit and receive
station traffic for wireless access networks. station traffic for wireless access networks.
Control And Provisioning of Wireless Access Points (CAPWAP): It is a Control And Provisioning of Wireless Access Points (CAPWAP): It is a
skipping to change at page 4, line 19 skipping to change at page 4, line 17
Address, WTP IP Address, AC data port, WTP data port, and the Address, WTP IP Address, AC data port, WTP data port, and the
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data
packets are sent and received. packets are sent and received.
Station (STA): A device that contains an interface to a wireless Station (STA): A device that contains an interface to a wireless
medium (WM). medium (WM).
Split and Local MAC: The CAPWAP protocol supports two modes of Split and Local MAC: The CAPWAP protocol supports two modes of
operation: Split and Local MAC. In Split MAC mode all L2 wireless operation: Split and Local MAC. In Split MAC mode all L2 wireless
data and management frames are encapsulated via the CAPWAP protocol data and management frames are encapsulated via the CAPWAP protocol
and exchanged between the AC and the WTPs. The Local MAC mode of and exchanged between the AC and the WTPs. The Local MAC mode allows
operation allows for the data frames to be either locally bridged, or the data frames to be either locally bridged, or tunneled as 802.3
tunneled as 802.3 frames. frames.
Wireless Binding: The CAPWAP protocol is independent of a specific Wireless Binding: The CAPWAP protocol is independent of a specific
WTP radio technology, as well its associated wireless link layer WTP radio technology, as well its associated wireless link layer
protocol. Elements of the CAPWAP protocol are designed to protocol. Elements of the CAPWAP protocol are designed to
accommodate the specific needs of each wireless technology in a accommodate the specific needs of each wireless technology in a
standard way. Implementation of the CAPWAP protocol for a particular standard way. Implementation of the CAPWAP protocol for a particular
wireless technology MUST defining a binding protocol for it, e.g., wireless technology MUST define a binding protocol for it, e.g., the
the binding for IEEE 802.11, provided in binding for IEEE 802.11, provided in [RFC5416].
[I-D.ietf-capwap-protocol-binding-ieee80211].
Autonomous WLAN Architecture: It is the traditional autonomous WLAN Autonomous WLAN Architecture: It is the traditional autonomous WLAN
architecture, in which each WTP is a single physical device that architecture, in which each WTP is a single physical device that
implements all the wireless services. implements all the wireless services.
Centralized WLAN Architecture: It is an emerging hierarchical Centralized WLAN Architecture: It is an emerging hierarchical
architecture utilizing one or more centralized controllers for architecture utilizing one or more centralized controllers for
managing a large number of WTP devices. It can be said that the full managing a large number of WTP devices. It can be said that the full
wireless functions are implemented across multiple physical network wireless functions are implemented across multiple physical network
devices, namely, the WTPs and ACs. devices, namely, the WTPs and ACs.
skipping to change at page 5, line 7 skipping to change at page 4, line 49
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
5.1. Requirements and Constraints 5.1. Requirements and Constraints
The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to:
satisfy the following requirements and constraints:
- From AC to centrally manage and monitor WTPs;
- Supports CAPWAP protocol parameters queries; - Support centralized management and monitoring of WTPs from the AC;
- Allow operators to make configurations for WTPs before and after
they connect to the AC;
- Supports showing WTPs current state; - Support querying of CAPWAP protocol parameters;
- Provides the information of AC, WTP, radio and station objects' - Support displaying of WTPs' current state and configuration;
basic property and their relationship;
- Supports indicating the 'WTP Virtual Radio Interface' and PHY - Provide basic property information about the AC, WTP, radio and
radio's mapping relationship; station and their relationships;
- Provides counters for WTP, radio's reboot event, hardware event - Provide counters for events on WTPs and radios such as reboot and
failure and so on; hardware failure;
- Provides the various notifications like channel up, join failure - Provide various notifications such as channel up and join failure.
and so on.
5.2. Wireless Binding MIB Modules 5.2. Wireless Binding MIB Modules
Other Standards Developing Organizations (SDOs), such as IEEE, have Other Standards Developing Organizations (SDOs), such as IEEE, have
already defined MIB modules for a specific wireless technology, e.g., already defined MIB modules for a specific wireless technology, e.g.,
the MIB module in IEEE 802.11 standard [IEEE.802-11.2007]. Such MIB IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are
modules are called as wireless binding MIB module. called wireless binding MIB modules.
5.3. Design Objectives 5.3. Design Objectives
This document brings forward a mechanism to avoid redefining MIB This document introduces a mechanism to avoid redefining MIB objects
objects in the existing MIB modules for a specific wireless in the existing MIB modules for a specific wireless technology, in
technology, in another words, a mechanism to reuse wireless binding other words, a mechanism to reuse wireless binding MIB modules
MIB modules defined by other SDOs. defined by other SDOs.
In summary, the CAPWAP-BASE-MIB module have the following design In summary, the CAPWAP-BASE-MIB module has the following design
objectives: objectives:
- To implement an architecture that uses SNMP for the management and - To implement an architecture that uses SNMP for the management and
control of wireless networks, answering the operators requirements control of wireless networks, and answering the operator's
for centralized management, whatever the deployment or configuration requirements for centralized management, whatever the wireless
of the network devices (centralized, distributed, or some mix); devices are configured and deployed (centralized, autonomous, or some
mix);
- To be consistent with CAPWAP protocol; - To be consistent with the CAPWAP protocol;
- To be independent of any wireless technologies and have ability to - To be independent of any wireless technologies and be able to reuse
reuse wireless binding MIB modules defined by other SDOs; wireless binding MIB modules defined by other SDOs;
- To enable interoperability between vendors; - To enable interoperability between vendors;
- To meet operator requirements for centralized wireless - To meet requirements for the centralized WLAN architecture.
architectures.
5.4. Design Idea 5.4. Design Idea
The basic design idea of CAPWAP-BASE-MIB module is: The basic design idea of the CAPWAP-BASE-MIB module is:
- The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT - 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 REQUIRED on the WTP devices. It follows the same model as the CAPWAP
protocol: Centralized Control; protocol: Centralized Control;
- It is designed to accommodate the specific needs of each wireless - It is designed to accommodate the specific needs of each wireless
technology in a standard way. It is independent of any wireless technology in a standard way. It is independent of any wireless
technologies; technologies;
- ifIndex [RFC2863] will be used as common handler for corresponding - The ifIndex [RFC2863] is used as a common handler for corresponding
interfaces in the CAPWAP-BASE-MIB and specific wireless technologies interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific
MIB modules; wireless technologies;
- The operator could manage and control the centralized wireless - The operator could manage and control the centralized WLAN
architectures using multiple MIB modules defined by multiple SDOs, architectures using multiple MIB modules defined by multiple SDOs,
while keeping them loosely coupled. while keeping them loosely coupled.
5.5. Mechanism of Reusing Wireless Binding MIB Modules 5.5. Mechanism of Reusing Wireless Binding MIB Modules
Before coming to details of CAPWAP-BASE-MIB module, it will introduce For any wireless technology, the configuration and management of
how CAPWAP-BASE-MIB module is able to be independent of any wireless radios are very important. As usual, wireless binding MIB modules
technologies and reuse wireless binding MIB modules defined by other support radio management on their own. For example, the MIB tables
SDOs. As centralized Wireless architecture, the operator has to such as the Dot11OperationTable [IEEE.802-11.2007] are able to
prepare configuration on the AC before WTPs connects to AC. For any support WTP radio configuration. These tables use the ifIndex as the
wireless technology, the configuration and management of radio is index, and work well under autonomous WLAN architecture.
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.
To reuse such wireless binding MIB modules is very important, and the To reuse such wireless binding MIB modules is very important to
key point is to reuse the idea of ifIndex. So it is required a way centralized WLAN architectures. According to [RFC5415], a specific
to maintain the mapping relationship between 'WTP id + radio id' and PHY radio could be identified by the combination of the identifiers
'ifIndex'. As a generic mechanism, ifIndex can identify an interface of the WTP and radio (WTP ID + radio ID), so the key point is to make
in abstract way, and it does NOT care for an interface's PHY location use of the ifIndex idea and find a way to maintain the mappings
(either on the WTP or AC). AC can have interfaces of 'WTP Virtual between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism,
Radio Interface' ifType, which will logically represent PHY radios on an ifIndex can identify an interface in an abstract way, and it does
the WTP. It looks like that PHY radios are located on the AC, and NOT care for the interface's PHY location (either on the WTP or AC).
PHY location of WTP (radio) is hidden to the operator. Operator can The AC can have WTP Virtual Radio Interfaces to logically represent
operate radios by MIB tables with ifIndex of 'WTP Virtual Radio PHY radios on the WTP. It looks like that PHY radios are located on
Interface'. As an abstract interface, 'WTP Virtual Radio Interface' the AC, and PHY location of the WTP (radio) is hidden to the
could be used by any wireless technology such as IEEE 802.11 and operator. The operator can operate radios through MIB tables with
802.16. The table of capwapBaseWirelessBindingTable in the CAPWAP- the ifIndex of a WTP Virtual Radio Interface. As a type of abstract
BASE-MIB module is used to indicate the such mapping relationship interface, the WTP Virtual Radio Interface could be used by any
between 'WTP id + Radio id' and IfIndex. wireless technology such as IEEE 802.11 and 802.16. The
capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used
to store the mappings between the 'WTP ID+ Radio ID' and the ifIndex.
5.6. CAPWAP Protocol Wireless Binding MIB Module 5.6. CAPWAP Protocol Wireless Binding MIB Module
According to the CAPWAP Protocol specification According to the CAPWAP Protocol specification [RFC5415], when
[I-D.ietf-capwap-protocol-specification], when defining a binding for defining a binding for wireless technologies, the authors MUST
wireless technologies, the authors MUST include any necessary include any necessary definitions for technology-specific messages
definitions for technology-specific messages and all technology- and all technology-specific message elements for those messages. A
specific message elements for those messages. A CAPWAP binding CAPWAP binding protocol is required for a specific wireless binding
protocol is required for a specific wireless binding technology, technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding.
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 Sometimes, not all the technology-specific message elements in a
CAPWAP binding protocol have MIB objects defined by other SDOs. For CAPWAP binding protocol have MIB objects defined by other SDOs. For
example, the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] example, the protocol of [RFC5416] defines WLAN conception. The WLAN
defines WLAN conception. The WLAN refers to a logical component refers to a logical component instantiated on a WTP device. A single
instantiated on a WTP device. A single physical WTP may operate a physical WTP MAY operate a number of WLANs. Also, Local or Split MAC
number of WLANs. Also, Local or Split MAC modes could be specified modes could be specified for a WLAN. The MAC mode for a WLAN is not
for a WLAN. The MAC mode for a WLAN is not in the scope of IEEE in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in
802.11 [IEEE.802-11.2007]. In such cases, in addition to the addition to the existing wireless binding MIB modules defined by
existing wireless binding MIB modules defined by other SDOs, a CAPWAP other SDOs, a CAPWAP protocol wireless binding MIB module is required
protocol wireless binding MIB module is required to be defined for a to be defined for a wireless binding, e.g, the CAPWAP Protocol
wireless binding, e.g, the CAPWAP Protocol Binding MIB for IEEE Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib].
802.11 [I-D.ietf-capwap-802dot11-mib].
5.7. WTP Profile
In a centralized WLAN architecture, a WTP profile is used to make
configurations such as static IP address for a WTP before and after
it connects to the AC. It MUST contain the serial number [RFC5415]
of the WTP because the CAPWAP message received from the WTP contains
its serial number and the AC uses this serial number to find the
corresponding WTP profile.
Another important function of WTP profile is to trigger the creation
of WTP Virtual Radio Interfaces on the AC. To implement this
function, a WTP profile MUST include the WTP's model number
[RFC5415], which reflects the number of PHY radios on the WTP. In
this way, the creation of a WTP profile triggers the AC to
automatically create the same number of WTP Virtual Radio Interfaces
corresponding to the WTP's PHY radios without manual intervention.
With the ifIndexes of WTP Virtual Radio Interfaces, the operator
could configure and manage the WTP's PHY radios through the wireless
binding MIB modules.
6. Structure of the MIB Module 6. Structure of the MIB Module
The MIB objects were derived from the CAPWAP protocol document The MIB objects are derived from the CAPWAP protocol document
[I-D.ietf-capwap-protocol-specification]. [RFC5415].
1) capwapBaseAcNameListTable 1) capwapBaseAcNameListTable
The AC name list table is used to configure the AC name list.
The AC name list table is used to configure AC name list.
2) capwapBaseMacAclTable 2) capwapBaseMacAclTable
The ACL table is used to configure stations' Access Control The ACL table is used to configure stations' Access Control
List(ACL). List(ACL).
3) capwapBaseWtpStateTable 3) capwapBaseWtpProfileTable
The WTP profile table is used to configure WTP profiles for WTPs to
be managed before they connect to the AC. An operator could change a
WTP's current configuration by changing the values of parameters in
the corresponding WTP profile.
4) 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, and helps operator to query WTPs' current configuration.
4) capwapBaseWtpTable 5) capwapBaseWtpTable
The WTPs table is used for providing property and configuration The WTPs table is used display properties of WTPs in running state.
information in details for WTPs in running state.
5) capwapBaseWirelessBindingTable 6) capwapBaseWirelessBindingTable
The wireless binding table is used to indicate the mapping The wireless binding table is used to display the mappings between
relationship between logical interface of 'WTP Virtual Radio WTP Virtual Radio Interfaces and PHY radios, and the wireless binding
Interface' ifType and PHY radio. type for each PHY radio.
6) capwapBaseStationTable 7) capwapBaseStationTable
The station table is used for providing stations' basic property The station table is used for providing stations' basic property
information. information.
7) capwapBaseWtpEventsStatsTable 8) capwapBaseWtpEventsStatsTable
The WTP events 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) capwapBaseRadioEventsStatsTable 9) capwapBaseRadioEventsStatsTable
The radio events 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 SNMPv2-MIB Module 7.1. Relationship to SNMPv2-MIB Module
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The CAPWAP-BASE-MIB module does not duplicate the objects of the
'system' group in the SNMPv2-MIB [RFC3418] that is defined as being
mandatory for all systems, and the objects apply to the entity as a 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 entity and certain other system-wide data.
module does not duplicate those objects.
7.2. Relationship to IF-MIB Module 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 PHY radios that
are modeled as interfaces. are modeled as interfaces.
IF-MIB module is required to support on the AC. For each PHY radio The IF-MIB module is required to be supported on the AC. Each PHY
on the WTP, it will have a logical interface of 'WTP Virtual Radio radio on the WTP corresponds to a WTP Virtual Radio Interface on the
Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides AC. The WTP Virtual Radio Interface provides a way to configure the
a way to configure radio's parameters and query radio's traffic radio's parameters and query radio's traffic statistics, and reuse
statistics, and reuse wireless binding modules defined by other SDOs. wireless binding modules defined by other SDOs. The interface MUST
The interface MUST be modeled as an ifEntry and provide appropriate be modeled as an ifEntry, and ifEntry objects such as ifIndex,
interface information. ifDescr, ifName, ifAlias are to be used as per [RFC2863].
Also, as ifIndex [RFC2863] will be used as common handler for Also, as an ifIndex [RFC2863] is used as a common handler for a
corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless
technologies MIB modules, the system (AC) MUST have a mechanism that technologies MIB modules, the AC MUST have a mechanism that preserves
preserves the values of ifIndex in the ifTable at AC reboot. the values of the ifIndexes in the ifTable at AC reboot.
7.3. Relationship to ENTITY-MIB Module 7.3. Relationship to ENTITY-MIB Module
The ENTITY-MIB module [RFC4133] meets need for a standardized way of The ENTITY-MIB module [RFC4133] meets the need for a standardized way
representing a single agent, which supports multiple instances of one of representing a single agent, which supports multiple instances of
MIB. It could express a certain relationship between multiple one 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 In a centralized WLAN architecture, the SNMP agent runs on the AC,
on the AC, and not required on the WTP. By the ENTITY-MIB module on and is not required on the WTP. With the ENTITY-MIB module on the
the AC, it could keep entity information such as firmware revision AC, it could keep entity information such as firmware revision and
and software revision of AC and WTPs. From the ENTITY-MIB module software revision of the AC and WTPs. From the ENTITY-MIB module's
perspective, the overall physical entity (AC) is a 'compound' of perspective, the overall physical entity (AC) is a 'compound' of
multiple physical entities (WTPs which connects to AC), all entities multiple physical entities (that is, the WTPs connected to AC), and
are identified by Physical index. In the capwapBaseWtpTable of all entities are each identified by a Physical index. The
CAPWAP-BASE-MIB module, it uses capwapBaseWtpPhyIndex object to keep capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the
the mapping relationship of WTP object between CAPWAP-BASE-MIB and capwapBaseWtpPhyIndex object to store the mappings of WTP object
ENTITY-MIB module. between CAPWAP-BASE-MIB and ENTITY-MIB modules.
By combining the MIB modules, operators could query AC and WTP's By combining the MIB modules, operators could query the status and
status and properties. For example, they could get WTP's current properties of the AC and WTPs. For example, they could get a WTP's
status through CAPWAP-BASE-MIB module, and WTP's software revision current status through the CAPWAP-BASE-MIB module, and a WTP's
information through ENTITY-MIB module. The CAPWAP-BASE-MIB module software revision information through the ENTITY-MIB module. The
does not duplicate those objects defined in the ENTITY-MIB module. CAPWAP-BASE-MIB module does not duplicate those objects defined in
the ENTITY-MIB module.
7.4. Relationship to Wireless Binding MIB Modules 7.4. Relationship to Wireless Binding MIB Modules
The wireless binding MIB module of a wireless technology (such as The wireless binding MIB module of a wireless technology (such as
[IEEE.802-11.2007]) is required to support on the AC. The CAPWAP- [IEEE.802-11.2007]) is required to be supported on the AC. The
BASE-MIB module is able to support any wireless binding. Through CAPWAP-BASE-MIB module is able to support any wireless binding.
ifIndex of 'WTP Virtual Radio Interface' ifType, it provides Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a
consistent and abstract way of reusing MIB objects in the wireless consistent and abstract way of reusing MIB objects in the wireless
binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate
those objects defined in the wireless binding MIB modules. 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], SNMP- SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP-
FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB
[RFC4133]. [RFC4133].
8. Example of CAPWAP-BASE-MIB Module Usage 8. Example of CAPWAP-BASE-MIB Module Usage
With the idea of 'WTP Virtual Radio Interface' in the mind, the usage Here takes IEEE 802.11 binding as an example to show how the MIB
of the MIB modules will be easily understood. Here takes IEEE 802.11 modules operate.
binding as an example.
1) Identify the PHY radio by 'WTP Virtual Radio Interface' 1) Create a WTP profile
According to [I-D.ietf-capwap-protocol-specification], each radio on Suppose the WTP's serial identifier is '12345678'. Create the WTP
a WTP will be identified by a radio Id. Each WTP could be identified profile as follows:
by its serial number.
Suppose a WTP's serial number is '12345678', and first radio id is 1. In CapwapBaseWtpProfileTable
On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' {
ifType is 10 which represents the PHY radio 1. The following capwapBaseWtpProfileId = 1,
information is obtained in the CapwapBaseWirelessBindingTable. capwapBaseWtpProfileName = 'WTP Profile 12345678',
capwapBaseWtpProfileWTPSerialId = '12345678',
capwapBaseWtpProfileWTPModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 12345678',
capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIp = '192.168.0.100',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
capwapBaseWtpProfileWtpReportInterval = 120,
capwapBaseWtpProfileWtpSilentInterval = 30,
capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpWaitDTLSTimer = 60,
capwapBaseWtpProfileWtpEcnSupport = limited(0)
}
Suppose the WTP with model number 'WTP123' has one PHY radio and this
PHY radio is identified by ID 1. The creation of this WTP profile
triggers the AC to automatically create a WTP Virtual Radio Interface
and add a new row object to the CapwapBaseWirelessBindingTable
without manual intervention. Suppose the ifIndex of the WTP Virtual
Radio Interface is 10. The following information is stored in the
CapwapBaseWirelessBindingTable.
In CapwapBaseWirelessBindingTable In CapwapBaseWirelessBindingTable
{ {
capwapBaseWtpStateWtpId = '12345678', capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1, capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10, capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2) capwapBaseWirelessBindingType = dot11(2)
} }
By the mechanism of 'WTP Virtual Radio Interface', it seems WTP PHY The WTP Virtual Radio Interfaces on the AC correspond to the PHY
radios are located on the AC. The interface of 'WTP Virtual Radio radios on the WTP. The WTP Virtual Radio Interface is modeled by
Interface' ifType is modeled by ifTable [RFC2863]. ifTable [RFC2863].
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface', ifDescr = 'WTP Virtual Radio Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WTP Virtual Radio Interface' allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '000000', ifPhysAddress = '000000',
ifAdminStatus = true, ifAdminStatus = true(1),
ifOperStatus = false, ifOperStatus = false(0),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0 ifOutErrors = 0
} }
2) Configure specific wireless binding parameters for 'WTP Virtual 2) Query the ifIndexes of WTP Virtual Radio Interfaces
Radio Interface'
It will be done on the AC through specific wireless binding MIB Before configuring PHY radios, the operator needs to get the
module such as IEEE 802.11 MIB module. ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY
radios.
For example, to configure parameter for 'WTP Virtual Radio Interface' As CapwapBaseWirelessBindingTable already stores the mappings between
by IEEE 802.11 Dot11OperationTable [IEEE.802-11.2007]. PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio
Interfaces, the operator can get the ifIndex information by querying
this table. Such a query operation SHOULD run from radio ID 1 to
radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex
value (0) is returned.
This example uses capwapBaseWtpProfileId = 1 and
capwapBaseWirelessBindingRadioId = 1 as inputs to query the
CapwapBaseWirelessBindingTable, and gets
capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses
capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2,
and gets a invalid ifIndex value (0), so the the query operation
ends. This method gets not only the ifIndexes of WTP Virtual Radio
Interfaces, but also the numbers of PHY radios. Besides checking
whether the ifIndex value is valid, the operator SHOULD check whether
the capwapBaseWirelessBindingType is the desired binding type.
3) Configure specific wireless binding parameters for a WTP Virtual
Radio Interface
This configuration is made on the AC through a specific wireless
binding MIB module such as the IEEE 802.11 MIB module.
The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the IEEE 802.11
Dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = '000000', 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 'WTP Virtual 4) Current configuration status report from the WTP to the AC
Radio Interface' ifType is 10.
3) WTP reports its current configuration status
According to [I-D.ietf-capwap-protocol-specification], after join According to [RFC5415], before a WTP that has joined the AC gets
phase and before WTP get configuration from AC, it will report its configuration from the AC, it needs to report its current
current configuration status to AC through configuration status configuration status by sending a configuration status request
request message. The data of MIB objects will be updated on the AC. message to the AC, which use the message to update MIB objects on the
For example, for IEEE 802.11 binding, WTP will update data in the AC. For example, for IEEE 802.11 binding, the AC updates data in the
ifTable and IEEE 802.11 MIB module so on according to message ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the
content. As an example for ifIndex 10, its ifOperStatus in ifTable message. For ifIndex 10, its ifOperStatus in ifTable is updated
will be updated according to current radio operational status in the according to the current radio operational status in the CAPWAP
CAPWAP message. message.
4) Query WTP and radio statistics data 5) Query WTP and radio statistics data
After WTPs come to run status, operator could query WTP and radio After WTPs start to run, the operator could query WTP and radio
statistics data through CAPWAP-BASE-MIB and specific binding MIB statistics data through CAPWAP-BASE-MIB and specific binding MIB
module. For example, through dot11CountersTable in the IEEE 802.11 module on the AC. For example, through dot11CountersTable in the
MIB module, operator could query counter data for radio which is IEEE 802.11 MIB module, the operator could query the counter data of
identified by ifIndex of a virtual radio interface. With a radio using the ifIndex of the corresponding WTP Virtual Radio
capwapBaseWtpTable table in the CAPWAP-BASE-MIB module, operator Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB
could query configuration and properties of WTPs which are in run module, the operator could query the properties of running WTPs.
status.
5) MIB operations through a CAPWAP protocol wireless binding MIB 6) MIB operations through a CAPWAP protocol wireless binding MIB
module module
For example, for CAPWAP IEEE 802.11 binding protocol [RFC5416], Some
MIB operations such as MAC mode configuration for a WLAN depend on
the CAPWAP Protocol Binding MIB for IEEE 802.11
[I-D.ietf-capwap-802dot11-mib]. For more information, refer to
[I-D.ietf-capwap-802dot11-mib].
For example, for CAPWAP IEEE 802.11 binding protocol 7) Query other properties of a WTP
[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 The Operator could query MIB objects in the ENTITY-MIB [RFC4133]
capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable
module. The properties of WTP such as software version, hardware of CAPWAP-BASE-MIB module. The properties of a WTP such as software
version and so on are available in the ENTITY-MIB module. version, hardware version 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 module. CAPWAP protocol to support CAPWAP-BASE-MIB module.
To enable CAPWAP protocol timers and variables To enable CAPWAP protocol timers and variables [RFC5415] manageable
[I-D.ietf-capwap-protocol-specification] manageable through CAPWAP through CAPWAP protocol, the following capwap message element
protocol, the following capwap message element extensions are defined extensions are defined using Vendor Specific Payload message element
using Vendor Specific Payload message element in this section. These in this section. These message elements are used by WTP to report
message elements are used by WTP to report extra configuration extra configuration information to the 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 13, line 50 skipping to change at page 15, line 21
Vendor Identifier: A 32-bit value containing the IANA assigned "SMI Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes". 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 Keep Alive. (see section 4.7.2 of must transmit the Data Channel Keep Alive. (see section 4.7.2 of
[I-D.ietf-capwap-protocol-specification]). [RFC5415]).
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 section 4.7.3 of [I-D.ietf- no greater that 240 seconds (see section 4.7.3 of [RFC5415]).
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 section 4.7.5 of message, before initiating a DTLS handshake (see section 4.7.5 of
[I-D.ietf-capwap-protocol-specification]). [RFC5415]).
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 section seconds, a WTP MUST wait for DTLS session deletion (see section
4.7.6 of [I-D.ietf-capwap-protocol-specification]). 4.7.6 of [RFC5415]).
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 section 4.7.7 of [I-D.ietf-capwap- which the WTP has joined (see section 4.7.7 of [RFC5415]).
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 section 4.7.8 of [I-D.ietf-capwap- Timeout is 300 seconds (see section 4.7.8 of [RFC5415]).
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 section 4.7.9 of [I-D.ietf-capwap-protocol- Data Request (see section 4.7.9 of [RFC5415]).
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 section 4.7.10 of [I-D.ietf-capwap-protocol- seconds (see section 4.7.10 of [RFC5415]).
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 section 4.7.11 of [I-D.ietf- the AC of decryption errors (see section 4.7.11 of [RFC5415]).
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 section 4.7.12 of [I-D.ietf-capwap-protocol- retransmitted (see section 4.7.12 of [RFC5415]).
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 section 4.7.13 of [I-D.ietf-capwap- establish DTLS session (see section 4.7.13 of [RFC5415]).
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 section 4.7.14 of [I-D.ietf- communicate its statistics (see section 4.7.14 of [RFC5415]).
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
section 4.7.15 of [I-D.ietf-capwap-protocol- section 4.7.15 of [RFC5415]).
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 29 skipping to change at page 17, line 29
Length: 12 Length: 12
Vendor Identifier: A 32-bit value containing the IANA assigned "SMI Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes". 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 section 4.8.5 of [-D.ietf-capwap-protocol-specification]). (see section 4.8.5 of [RFC5415]).
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 section 4.8.6 of CAPWAP device enters a silent period (see section 4.8.6 of
[I-D.ietf-capwap-protocol-specification]). [RFC5415]).
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 section 4.8.7 of [I-D.ietf-capwap- considers the peer dead (see section 4.8.7 of [RFC5415]).
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 17, line 39 skipping to change at page 18, line 38
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 "200902280000Z" -- Feb 28th, 2009 LAST-UPDATED "200905290000Z" -- May 29th, 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 18, line 33 skipping to change at page 19, line 31
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2009 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 "200902280000Z" REVISION "200905290000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP profile."
SYNTAX Unsigned32 (0..4096)
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "32a" DISPLAY-HINT "32a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a WTP instance. "Represents the unique identifier of a WTP instance.
As usual, a serial number of WTP will be used." As usual, a serial number of WTP is used."
SYNTAX OCTET STRING (SIZE (0..32)) 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 the unique identifier of a station instance.
As usual, the MAC address of station will be used." As usual, the MAC address of the station is used."
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents an unique identifier of a radio on a WTP." "Represents the 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 a 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:
localBridging(0) - Local Bridging Mode localBridging(0) - Local bridging mode
dot3Tunnel(1) - 802.3 Frame Tunnel Mode dot3Tunnel(1) - 802.3 frame tunnel mode
nativeTunnel(2) - Native Frame Tunnel Mode" nativeTunnel(2) - Native frame tunnel mode"
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415."
SYNTAX BITS { SYNTAX BITS {
localBridging(0), localBridging(0),
dot3Tunnel(1), dot3Tunnel(1),
nativeTunnel(2) nativeTunnel(2)
} }
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 a 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.44. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415."
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 a 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 -- Top level components of this MIB module
skipping to change at page 21, line 9 skipping to change at page 22, line 11
capwapBaseAc OBJECT IDENTIFIER capwapBaseAc OBJECT IDENTIFIER
::= { capwapBaseObjects 1 } ::= { capwapBaseObjects 1 }
capwapBaseWtpSessions OBJECT-TYPE capwapBaseWtpSessions OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of WTPs which are connecting to "Represents the total number of WTPs which are connecting to
AC." the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 1 } ::= { capwapBaseAc 1 }
capwapBaseWtpSessionsLimit OBJECT-TYPE capwapBaseWtpSessionsLimit 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 WTP sessions configured for "Represents the maximum number of WTP sessions configured on
the AC." 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 5415."
::= { capwapBaseAc 2 } ::= { capwapBaseAc 2 }
capwapBaseStationSessions OBJECT-TYPE capwapBaseStationSessions OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of stations which are accessing "Represents the total number of stations which are accessing
the wireless service provided by the AC." the wireless service provided by the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415."
::= { 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
on the AC. on the AC.
The value of the object is persistent at restart/reboot." 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 5415."
::= { capwapBaseAc 4 } ::= { capwapBaseAc 4 }
capwapBaseDataChannelDTLSPolicyOptions 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
"The AC communicates its policy on the use of DTLS for "The AC communicates its policy on the use of DTLS for
the CAPWAP data channel. 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 5415."
::= { capwapBaseAc 5 } ::= { capwapBaseAc 5 }
capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE
SYNTAX INTEGER { 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 on the AC for "Represents the security policy configured on the AC for
CAPWAP data channel. CAPWAP data channel.
The value of the object is persistent at restart/reboot.
The following enumerated values are supported: The following enumerated values are supported:
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 5415."
::= { capwapBaseAc 6 } ::= { capwapBaseAc 6 }
capwapBaseControlChannelAuthenOptions OBJECT-TYPE capwapBaseControlChannelAuthenOptions OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
x509(0), x509(0),
psk(1) psk(1)
} }
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 CAPWAP 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 x509(0) - X.509 certificate based
psk(1) - Pre-Shared Secret" psk(1) - Pre-Shared secret"
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 7 } ::= { capwapBaseAc 7 }
capwapBaseControlChannelAuthenConfig OBJECT-TYPE capwapBaseControlChannelAuthenConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
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 on
the AC for control channel. the AC for CAPWAP control channel.
The value of the object is persistent at restart/reboot.
The following enumerated values are supported: The following enumerated values are supported:
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 5415."
::= { 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 configure the AC name list.
Values of all read-create objects in this table are
persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 the AC name list."
Values of all read-create objects in this table are persistent
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
} }
capwapBaseAcNameListId OBJECT-TYPE capwapBaseAcNameListId OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique id for a AC Name list." "Represents the unique identifier of 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, and it is expected to be "Represents the name of an AC, and it is expected to be
an UTF-8 encoded string." 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 5415."
::= { 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.
For instance, the value of one (1) is used to set the primary For instance, the value of one (1) is used to set the primary
AC, the value of two (2) is used to set the secondary, etc." AC, the value of two (2) is used to set the secondary AC, etc."
REFERENCE REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAcNameListEntry 3 } ::= { capwapBaseAcNameListEntry 3 }
capwapBaseAcNameListRowStatus OBJECT-TYPE capwapBaseAcNameListRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table." in this table."
::= { capwapBaseAcNameListEntry 4 } ::= { capwapBaseAcNameListEntry 4 }
skipping to change at page 25, line 11 skipping to change at page 26, line 13
-- End of capwapBaseAcNameListTable table -- End of capwapBaseAcNameListTable table
-- capwapBaseMacAclTable table -- capwapBaseMacAclTable table
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). Lists (ACL).
WTP will not provide service to the MAC addresses configured The WTP will not provide service to the MAC addresses
in this table." configured in this table.
Values of all read-create objects in this table are persistent
at AC restart/reboot."
REFERENCE REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 table are persisten
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
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique id for a ACL." "Represents the unique identifier of an ACL."
::= { capwapBaseMacAclEntry 1 } ::= { capwapBaseMacAclEntry 1 }
capwapBaseMacAclStationId OBJECT-TYPE capwapBaseMacAclStationId OBJECT-TYPE
SYNTAX CapwapBaseStationIdTC SYNTAX CapwapBaseStationIdTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a station's MAC address which WTPs will no longer "Represents the MAC address of a station to which WTPs will
provides service to it." no longer provides service."
REFERENCE REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseMacAclEntry 2 } ::= { capwapBaseMacAclEntry 2 }
capwapBaseMacAclRowStatus OBJECT-TYPE capwapBaseMacAclRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table." in this table."
::= { capwapBaseMacAclEntry 3 } ::= { capwapBaseMacAclEntry 3 }
-- End of capwapBaseMacAclTable table -- End of capwapBaseMacAclTable table
-- End of AC Objects Group -- End of AC Objects Group
-- WTP Objects Group -- WTP Objects Group
capwapBaseWtps OBJECT IDENTIFIER capwapBaseWtps OBJECT IDENTIFIER
::= { capwapBaseObjects 2 } ::= { capwapBaseObjects 2 }
-- capwapBaseWtpProfileTable Table
capwapBaseWtpProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that configure WTP profiles for WTPs to
be managed before they connect to the AC.
An operator could change a WTP's configuration by changing
the values of parameters in the corresponding WTP profile.
Values of all read-create objects in this table are
persistent at restart/reboot."
::= { capwapBaseWtps 1 }
capwapBaseWtpProfileEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that configure and display a WTP profile."
INDEX { capwapBaseWtpProfileId }
::= { capwapBaseWtpProfileTable 1 }
CapwapBaseWtpProfileEntry ::= SEQUENCE {
capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC,
capwapBaseWtpProfileName SnmpAdminString,
capwapBaseWtpProfileWTPSerialId CapwapBaseWtpIdTC,
capwapBaseWtpProfileWTPModelNumber SnmpAdminString,
capwapBaseWtpProfileWtpName OCTET STRING,
capwapBaseWtpProfileWtpLocation OCTET STRING,
capwapBaseWtpProfileWtpStaticIpEnable TruthValue,
capwapBaseWtpProfileWtpStaticIpType InetAddressType,
capwapBaseWtpProfileWtpStaticIp InetAddress,
capwapBaseWtpProfileWtpNetmask InetAddress,
capwapBaseWtpProfileWtpGateway InetAddress,
capwapBaseWtpProfileWtpFallbackEnable INTEGER,
capwapBaseWtpProfileWtpEchoInterval Unsigned32,
capwapBaseWtpProfileWtpIdleTimeout Unsigned32,
capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32,
capwapBaseWtpProfileWtpReportInterval Unsigned32,
capwapBaseWtpProfileWtpSilentInterval Unsigned32,
capwapBaseWtpProfileWtpStatisticsTimer Unsigned32,
capwapBaseWtpProfileWtpWaitDTLSTimer Unsigned32,
capwapBaseWtpProfileWtpEcnSupport INTEGER,
capwapBaseWtpProfileRowStatus RowStatus
}
capwapBaseWtpProfileId OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP profile."
::= { capwapBaseWtpProfileEntry 1 }
capwapBaseWtpProfileName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the name of a WTP profile."
::= { capwapBaseWtpProfileEntry 2 }
capwapBaseWtpProfileWTPSerialId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the serial identifier of a WTP.
A WTP profile MUST contain the serial number of the WTP
because the CAPWAP message received from the WTP contains
its serial number and the AC uses the serial number to
find the corresponding WTP profile."
REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 3 }
capwapBaseWtpProfileWTPModelNumber OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the model number of a WTP.
A WTP profile MUST include the WTP's model number, which
reflects the number of PHY radios on the WTP.
In this way, the creation of a WTP profile triggers the AC
to automatically create the same number of WTP Virtual Radio
Interfaces corresponding to the WTP's PHY radios without
manual intervention. With the ifIndexes of WTP Virtual
Radio Interfaces, the operator could configure and manage
the WTP's PHY radios through the wireless binding MIB
modules."
REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 4 }
capwapBaseWtpProfileWtpName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(512))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the name of the WTP."
REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 5 }
capwapBaseWtpProfileWtpLocation OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(1024))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the location of the WTP."
REFERENCE
"Section 4.6.30. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 6 }
capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether the WTP SHOULD use a static IP address
or not. A value of false disables the static IP address,
while a value of true enables it."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 7 }
capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the static IP address type used by the WTP, IPv4
or IPv6."
::= { capwapBaseWtpProfileEntry 8 }
capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the static IP address to be assigned to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 9 }
capwapBaseWtpProfileWtpNetmask OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the netmask to be assigned to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 10 }
capwapBaseWtpProfileWtpGateway OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the gateway to be assigned to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 11 }
capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents whether to enable or disable automatic CAPWAP
fallback in the event that a WTP detects its preferred AC,
and is not currently connected to it.
The following enumerated values are supported:
enabled(1) - The fallback mode is enabled
disabled(2) - The fallback mode is disabled"
REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { enabled }
::= { capwapBaseWtpProfileEntry 12 }
capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo
Request messages to the AC that the WTP has joined."
REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseWtpProfileEntry 13 }
capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the idle timeout value that the WTP SHOULD enforce
for its active stations."
REFERENCE
"Section 4.7.8. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 300 }
::= { capwapBaseWtpProfileEntry 14 }
capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32 (2..180)
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the maximum time allowed between sending Discovery
Request messages, in seconds."
REFERENCE
"Section 4.7.10. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 20 }
::= { capwapBaseWtpProfileEntry 15 }
capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the interval for WTP to send Decryption Error
report."
REFERENCE
"Section 4.7.11. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 16 }
capwapBaseWtpProfileWtpSilentInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait
before it MAY again send Discovery Request messages or
attempt to a establish DTLS session."
REFERENCE
"Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 }
::= { capwapBaseWtpProfileEntry 17 }
capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the interval the WTP uses between the WTP Events
Requests it transmits to the AC to communicate its statistics,
in seconds."
REFERENCE
"Section 4.7.14. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 18 }
capwapBaseWtpProfileWtpWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 (30..4294967295)
UNITS "second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds."
REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 60 }
::= { capwapBaseWtpProfileEntry 19 }
capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE
SYNTAX INTEGER {
limited(0),
fullAndLimited(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the support for the Explicit Congestion Notification
(ECN) bits, as defined in [RFC3168].
The following enumerated values are supported:
limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support"
REFERENCE
"Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 20 }
capwapBaseWtpProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row
in this table.
Deleting a WTP profile in use will disconnect the WTP to
the AC. So the network management system SHOULD
ask the operator to confirm such an operation.
When a WTP profile entry is removed from the table,
the corresponding WTP Virtual Radio Interfaces are also
removed from the CapwapBaseWirelessBindingTable and
ifTable [RFC2863].
Also, the related object instances SHOULD be removed from
the wireless binding MIB modules such as IEEE 802.11
MIB module [IEEE.802-11.2007]."
::= { capwapBaseWtpProfileEntry 21 }
-- End of capwapBaseWtpProfileTable table
-- capwapBaseWtpStateTable table -- capwapBaseWtpStateTable table
capwapBaseWtpStateTable OBJECT-TYPE capwapBaseWtpStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display WTP CAPWAP FSM state." "A table of objects that indicate each WTP's CAPWAP FSM
::= { capwapBaseWtps 1 } state, and helps the operator to query the WTPs' current
configuration."
::= { capwapBaseWtps 2 }
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 the WTP's CAPWAP FSM state.
Also, the operator could query the current configuration
of a WTP by using the identifier of the corresponding
WTP profile."
INDEX { capwapBaseWtpStateWtpId } INDEX { capwapBaseWtpStateWtpId }
::= { capwapBaseWtpStateTable 1 } ::= { capwapBaseWtpStateTable 1 }
CapwapBaseWtpStateEntry ::= SEQUENCE { CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpStateWtpIpAddressType InetAddressType, capwapBaseWtpStateWtpIpAddressType InetAddressType,
capwapBaseWtpStateWtpIpAddress InetAddress, capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpStateWtpPhyAddress PhysAddress, capwapBaseWtpStateWtpBaseMacAddress PhysAddress,
capwapBaseWtpState INTEGER capwapBaseWtpState INTEGER,
capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC
} }
capwapBaseWtpStateWtpId 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 }
capwapBaseWtpStateWtpIpAddressType 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 IP address type of a WTP."
::= { capwapBaseWtpStateEntry 2 } ::= { capwapBaseWtpStateEntry 2 }
capwapBaseWtpStateWtpIpAddress 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 }
capwapBaseWtpStateWtpPhyAddress OBJECT-TYPE capwapBaseWtpStateWtpBaseMacAddress 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 WTP's Base MAC Address, which MAY be
assigned to the primary Ethernet interface."
REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 4 } ::= { capwapBaseWtpStateEntry 4 }
capwapBaseWtpState OBJECT-TYPE capwapBaseWtpState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dtls(1), dtls(1),
join(2), join(2),
image(3), image(3),
configure(4), configure(4),
dataCheck(5), dataCheck(5),
run(6), run(6),
clear(7), reset(7),
unknown(8) dtlsTeardown(8),
unknown(9)
} }
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) - The WTP is joining with the AC
image(3) - WTP is downloading software image(3) - The WTP is downloading software
configure(4) - WTP is getting configuration from AC configure(4) - The WTP is getting configuration from
dataCheck(5) - AC is waiting for the Data Channel Keep the AC
dataCheck(5) - The AC is waiting for the Data Channel Keep
Alive Packet Alive Packet
run(6) - WTP comes to run state run(6) - The WTP enters the running state
clear(7) - WTP recoveries default configuration reset(7) - The AC transmits a reset request message
unknown(8) - Operator already prepare configuration to the WTP
for WTP, while WTP has not contact with AC dtlsTeardown(8) - DTLS session is tear down
till now" unknown(9) - Operator already prepared configuration
for the WTP, while the WTP has not contact
with the AC till now"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 5 } ::= { capwapBaseWtpStateEntry 5 }
capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the current identifier of a WTP profile.
The operator could query a WTP's current configuration
with the identifier of a WTP profile."
::= { capwapBaseWtpStateEntry 6 }
-- 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
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display and control WTPs in "A table of objects that display properties of the WTPs
running state. Values of all read-write objects in this in running state."
table are persistent at restart/reboot." ::= { capwapBaseWtps 3 }
::= { capwapBaseWtps 2 }
capwapBaseWtpEntry OBJECT-TYPE capwapBaseWtpEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpEntry SYNTAX CapwapBaseWtpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display and control a WTP in "A set of objects that display properties of the WTPs
running state." in running state."
INDEX { capwapBaseWtpCurrId } INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpTable 1 } ::= { capwapBaseWtpTable 1 }
CapwapBaseWtpEntry ::= SEQUENCE { CapwapBaseWtpEntry ::= SEQUENCE {
capwapBaseWtpCurrId CapwapBaseWtpIdTC, capwapBaseWtpCurrId CapwapBaseWtpIdTC,
capwapBaseWtpPhyIndex PhysicalIndex, capwapBaseWtpPhyIndex PhysicalIndex,
capwapBaseWtpName OCTET STRING,
capwapBaseWtpLocation OCTET STRING,
capwapBaseWtpBaseMacAddress PhysAddress, capwapBaseWtpBaseMacAddress PhysAddress,
capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC,
capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC,
capwapBaseWtpDiscoveryType INTEGER, capwapBaseWtpDiscoveryType INTEGER,
capwapBaseWtpRadiosInUseNum Unsigned32, capwapBaseWtpRadiosInUseNum Unsigned32,
capwapBaseWtpRadioNumLimit Unsigned32, capwapBaseWtpRadioNumLimit Unsigned32,
capwapBaseWtpStaticIpEnable TruthValue,
capwapBaseWtpStaticIpType InetAddressType,
capwapBaseWtpStaticIp InetAddress,
capwapBaseWtpNetmask InetAddress,
capwapBaseWtpGateway InetAddress,
capwapBaseWtpFallbackEnable INTEGER,
capwapBaseWtpRetransmitCount Counter32, capwapBaseWtpRetransmitCount Counter32,
capwapBaseWtpMaxDiscoveries Unsigned32, capwapBaseWtpMaxDiscoveries Unsigned32,
capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32,
capwapBaseWtpMaxRetransmit Unsigned32, capwapBaseWtpMaxRetransmit Unsigned32,
capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, capwapBaseWtpDataChannelKeepAliveTimer Unsigned32,
capwapBaseWtpDataChannelDeadInterval Unsigned32, capwapBaseWtpDataChannelDeadInterval Unsigned32,
capwapBaseWtpDiscoveryInterval Unsigned32, capwapBaseWtpDiscoveryInterval Unsigned32,
capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, capwapBaseWtpDTLSSessionDeleteTimer Unsigned32,
capwapBaseWtpEchoInterval Unsigned32,
capwapBaseWtpIdleTimeout Unsigned32,
capwapBaseWtpImageDataStartTimer Unsigned32, capwapBaseWtpImageDataStartTimer Unsigned32,
capwapBaseWtpMaxDiscoveryInterval Unsigned32, capwapBaseWtpRetransmitInterval Unsigned32
capwapBaseWtpReportInterval Unsigned32,
capwapBaseWtpRetransmitInterval Unsigned32,
capwapBaseWtpSilentInterval Unsigned32,
capwapBaseWtpStatisticsTimer 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 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 module. The information such as software in the ENTITY-MIB module [RFC4133].
version of specific WTP could be accessed through the index." The information such as software version of a specific WTP
could be accessed through the index."
::= { capwapBaseWtpEntry 2 } ::= { capwapBaseWtpEntry 2 }
capwapBaseWtpName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(512))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the name of a WTP."
REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 3 }
capwapBaseWtpLocation OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(1024))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the location of a WTP."
REFERENCE
"Section 4.6.30. of CAPWAP Protocol Specification, RFC xxx."
::= { 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.40. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 5 } ::= { capwapBaseWtpEntry 3 }
capwapBaseWtpTunnelModeOptions 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."
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 6 } ::= { capwapBaseWtpEntry 4 }
capwapBaseWtpMacTypeOptions 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."
REFERENCE REFERENCE
"Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 7 } ::= { capwapBaseWtpEntry 5 }
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 the 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 5415."
::= { capwapBaseWtpEntry 8 } ::= { capwapBaseWtpEntry 6 }
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 on the WTP." "Represents the number of radios in use on the WTP."
REFERENCE REFERENCE
"Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 9 } ::= { capwapBaseWtpEntry 7 }
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.41. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 10 } ::= { capwapBaseWtpEntry 8 }
capwapBaseWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the WTP should use a static IP address
or not. A value of false disables the static IP address,
while a value of true enables it."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 11 }
capwapBaseWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether WTP uses IPv4 or IPv6 static IP address."
::= { capwapBaseWtpEntry 12 }
capwapBaseWtpStaticIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the
static IP address to assign to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 13 }
capwapBaseWtpNetmask OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the
netmask to assign to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 14 }
capwapBaseWtpGateway OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When capwapBaseWtpStaticIpEnable is true, it represents the
gateway to assign to the WTP."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 15 }
capwapBaseWtpFallbackEnable OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether to enable or disable automatic CAPWAP
fallback in the event that a WTP detects its preferred AC, and
is not currently connected to it.
The following enumerated values are supported:
enabled(1) - The fallback mode is enabled
disabled(2) - The fallback mode is disabled"
REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { enabled }
::= { capwapBaseWtpEntry 16 }
capwapBaseWtpRetransmitCount OBJECT-TYPE capwapBaseWtpRetransmitCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "retransmissions"
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 5415."
::= { capwapBaseWtpEntry 17 } ::= { capwapBaseWtpEntry 9 }
capwapBaseWtpMaxDiscoveries OBJECT-TYPE capwapBaseWtpMaxDiscoveries 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 Discovery Request messages "Represents the maximum number of Discovery Request messages
that will be sent after a WTP boots." that will be sent after a WTP boots."
REFERENCE REFERENCE
"Section 4.8.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.5. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 10 } DEFVAL { 10 }
::= { capwapBaseWtpEntry 18 } ::= { capwapBaseWtpEntry 10 }
capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE capwapBaseWtpMaxFailedDTLSSessionRetry 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 failed DTLS session "Represents 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 5415."
DEFVAL { 3 } DEFVAL { 3 }
::= { capwapBaseWtpEntry 19 } ::= { capwapBaseWtpEntry 11 }
capwapBaseWtpMaxRetransmit 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 "Represents 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 5415."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseWtpEntry 20 } ::= { capwapBaseWtpEntry 12 }
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 next opportunity, in seconds, the WTP must "Represents the next opportunity, in seconds, the WTP must
transmit the Data Channel Keep Alive message." transmit the Data Channel Keep Alive message."
REFERENCE REFERENCE
"Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.2. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseWtpEntry 21 } ::= { capwapBaseWtpEntry 13 }
capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..240) 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 5415."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseWtpEntry 22 } ::= { capwapBaseWtpEntry 14 }
capwapBaseWtpDiscoveryInterval OBJECT-TYPE capwapBaseWtpDiscoveryInterval 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 minimum time, in seconds, that a WTP MUST "Represents the minimum time, in seconds, that a WTP MUST
wait after receiving a Discovery Response message, before wait after receiving a Discovery Response message, before
initiating a DTLS handshake." initiating a DTLS handshake."
REFERENCE REFERENCE
"Section 4.7.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.5. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseWtpEntry 23 } ::= { capwapBaseWtpEntry 15 }
capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE capwapBaseWtpDTLSSessionDeleteTimer 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 minimum time, in seconds, a WTP MUST wait "Represents the minimum time, in seconds, a WTP MUST wait
for DTLS session deletion." for DTLS session deletion."
REFERENCE REFERENCE
"Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 5 } DEFVAL { 5 }
::= { capwapBaseWtpEntry 24 } ::= { capwapBaseWtpEntry 16 }
capwapBaseWtpEchoInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo
Request messages to the AC with which the WTP has joined."
REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 25 }
capwapBaseWtpIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the idle timeout value that the WTP SHOULD enforce
for its active stations."
REFERENCE
"Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 300 }
::= { capwapBaseWtpEntry 26 }
capwapBaseWtpImageDataStartTimer OBJECT-TYPE capwapBaseWtpImageDataStartTimer 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 number of seconds the WTP will wait for its peer "Represents the number of seconds the WTP will wait for its
to transmit the Image Data Request." peer 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 5415."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseWtpEntry 27 } ::= { capwapBaseWtpEntry 17 }
capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32 (2..180)
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time allowed between sending Discovery
Request messages, in seconds. This value MUST be no less than
2 seconds and no greater than 180 seconds."
REFERENCE
"Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 20 }
::= { capwapBaseWtpEntry 28 }
capwapBaseWtpReportInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the interval for WTP to send Decryption Error
report."
REFERENCE
"Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 120 }
::= { capwapBaseWtpEntry 29 }
capwapBaseWtpRetransmitInterval OBJECT-TYPE capwapBaseWtpRetransmitInterval 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 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."
REFERENCE REFERENCE
"Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 3 } DEFVAL { 3 }
::= { capwapBaseWtpEntry 30 } ::= { capwapBaseWtpEntry 18 }
capwapBaseWtpSilentInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait
before it MAY again send Discovery Request messages or attempt
to a establish DTLS session."
REFERENCE
"Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 31 }
capwapBaseWtpStatisticsTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the interval the WTP uses between the WTP Events
Requests it transmits to the AC to communicate its statistics,
in seconds."
REFERENCE
"Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 120 }
::= { capwapBaseWtpEntry 32 }
capwapBaseWtpWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 (30..4294967295)
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds."
REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 }
::= { 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 -- capwapBaseWirelessBindingTable Table
capwapBaseWirelessBindingTable OBJECT-TYPE capwapBaseWirelessBindingTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry 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 mappings between
between specific interface of 'WTP Virtual Radio Interface' WTP Virtual Radio Interfaces and PHY radios, and the
ifType and PHY radio, and wireless binding type for wireless binding type for each PHY radio.
a specific radio. The mapping relationship in this table Values of all objects in this table are persistent at
is persistent at restart/reboot." restart/reboot."
::= { capwapBaseWtps 3 } ::= { capwapBaseWtps 4 }
capwapBaseWirelessBindingEntry OBJECT-TYPE capwapBaseWirelessBindingEntry OBJECT-TYPE
SYNTAX CapwapBaseWirelessBindingEntry 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 between
between 'WTP Virtual Radio Interface' and PHY radio, and a specific WTP Virtual Radio Interface and a PHY
wireless binding type for a specific radio." radio, and the wireless binding type for the PHY radio."
INDEX { INDEX {
capwapBaseWtpStateWtpId, capwapBaseWtpProfileId,
capwapBaseWirelessBindingRadioId capwapBaseWirelessBindingRadioId
} }
::= { capwapBaseWirelessBindingTable 1 } ::= { capwapBaseWirelessBindingTable 1 }
CapwapBaseWirelessBindingEntry ::= SEQUENCE { CapwapBaseWirelessBindingEntry ::= SEQUENCE {
capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC,
capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex,
capwapBaseWirelessBindingType INTEGER capwapBaseWirelessBindingType INTEGER
} }
capwapBaseWirelessBindingRadioId 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, which
requires unique on a WTP. is required to be unique on a WTP.
For example, WTP A and WTP B will use same value of For example, WTP A and WTP B use a same value of
capwapBaseWirelessBindingRadioId 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 5415."
::= { capwapBaseWirelessBindingEntry 1 } ::= { capwapBaseWirelessBindingEntry 1 }
capwapBaseWirelessBindingVirtualRadioIfIndex 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 WLAN Virtual Radio Interface. The interface identified by
a 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 the ifIndex.
Before WTPs connect to AC and get configuration, operator Before WTPs contact the AC to get configuration,
will prepare configuration for them. On the AC, there are the operator configures WTP profiles for them.
interfaces of 'WTP Virtual Radio Interface' ifType which The creation of a WTP profile triggers system to automatically
represent PHY radio interfaces on the WTP. create a specific number of WTP Virtual Radio Interfaces and
As most MIB modules use ifIndex to identify an interface for add a new row object in the capwapBaseWirelessBindingTable
configuration and statistic data, for example, IEEE 802.11 MIB without manual intervention.
module. It will be very easy to reuse other wireless binding As most MIB modules use the ifIndex to identify an interface
MIB modules through 'WTP Virtual Radio Interface'." for configuration and statistic data, for example, IEEE 802.11
MIB module [IEEE.802-11.2007]
It will be easy to reuse other wireless binding MIB modules
through the WTP Virtual Radio Interface in the Centralized
WLAN Architecture."
::= { capwapBaseWirelessBindingEntry 2 } ::= { capwapBaseWirelessBindingEntry 2 }
capwapBaseWirelessBindingType OBJECT-TYPE capwapBaseWirelessBindingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dot11(1), dot11(1),
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 the radio.
The following enumerated values are supported: The following enumerated values are supported:
dot11(1) - IEEE 802.11 dot11(1) - IEEE 802.11
epc(3) - EPCGlobal" epc(3) - EPCGlobal"
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWirelessBindingEntry 3 } ::= { capwapBaseWirelessBindingEntry 3 }
-- End of capwapBaseWirelessBindingTable Table -- 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 REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 4 } ::= { capwapBaseWtps 5 }
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,
skipping to change at page 41, line 8 skipping to change at page 44, line 47
capwapBaseStationVlanName SnmpAdminString capwapBaseStationVlanName SnmpAdminString
} }
capwapBaseStationId OBJECT-TYPE capwapBaseStationId OBJECT-TYPE
SYNTAX CapwapBaseStationIdTC SYNTAX CapwapBaseStationIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of the station." "Represents the unique identifier of the station."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 1 } ::= { capwapBaseStationEntry 1 }
capwapBaseStationAddedTime OBJECT-TYPE capwapBaseStationAddedTime OBJECT-TYPE
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 5415."
::= { capwapBaseStationEntry 2 } ::= { capwapBaseStationEntry 2 }
capwapBaseStationVlanName OBJECT-TYPE capwapBaseStationVlanName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) 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 5415."
::= { capwapBaseStationEntry 3 } ::= { capwapBaseStationEntry 3 }
-- End of capwapBaseStationTable Table -- End of capwapBaseStationTable Table
-- capwapBaseWtpEventsStatsTable -- capwapBaseWtpEventsStatsTable
capwapBaseWtpEventsStatsTable OBJECT-TYPE capwapBaseWtpEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry 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' events statistics." "A table of objects that display the WTPs' events statistics."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 5 } ::= { capwapBaseWtps 6 }
capwapBaseWtpEventsStatsEntry OBJECT-TYPE capwapBaseWtpEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpEventsStatsEntry SYNTAX CapwapBaseWtpEventsStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the events statistic data "A set of objects that display the events statistic data
of a WTP." of a WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
INDEX { capwapBaseWtpCurrId } INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpEventsStatsTable 1 } ::= { capwapBaseWtpEventsStatsTable 1 }
CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { CapwapBaseWtpEventsStatsEntry ::= SEQUENCE {
capwapBaseWtpEventsStatsRebootCount Counter32, capwapBaseWtpEventsStatsRebootCount Counter32,
capwapBaseWtpEventsStatsInitCount Counter32, capwapBaseWtpEventsStatsInitCount Counter32,
capwapBaseWtpEventsStatsLinkFailureCount Counter32, capwapBaseWtpEventsStatsLinkFailureCount Counter32,
capwapBaseWtpEventsStatsSwFailureCount Counter32, capwapBaseWtpEventsStatsSwFailureCount Counter32,
capwapBaseWtpEventsStatsHwFailureCount Counter32, capwapBaseWtpEventsStatsHwFailureCount Counter32,
capwapBaseWtpEventsStatsOtherFailureCount Counter32, capwapBaseWtpEventsStatsOtherFailureCount Counter32,
skipping to change at page 42, line 30 skipping to change at page 46, line 21
capwapBaseWtpEventsStatsRebootCount 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 1 } ::= { capwapBaseWtpEventsStatsEntry 1 }
capwapBaseWtpEventsStatsInitCount 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 requires 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 2 } ::= { capwapBaseWtpEventsStatsEntry 2 }
capwapBaseWtpEventsStatsLinkFailureCount 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 failures."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 3 } ::= { capwapBaseWtpEventsStatsEntry 3 }
capwapBaseWtpEventsStatsSwFailureCount 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 4 } ::= { capwapBaseWtpEventsStatsEntry 4 }
capwapBaseWtpEventsStatsHwFailureCount 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 5 } ::= { capwapBaseWtpEventsStatsEntry 5 }
capwapBaseWtpEventsStatsOtherFailureCount 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 the AC initiated, link, software or hardware failures."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 6 } ::= { capwapBaseWtpEventsStatsEntry 6 }
capwapBaseWtpEventsStatsUnknownFailureCount 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 7 } ::= { capwapBaseWtpEventsStatsEntry 7 }
capwapBaseWtpEventsStatsLastFailureType 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) - The 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.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 8 } ::= { capwapBaseWtpEventsStatsEntry 8 }
-- End of capwapBaseWtpEventsStatsTable table -- End of capwapBaseWtpEventsStatsTable table
-- capwapBaseRadioEventsStatsTable table -- capwapBaseRadioEventsStatsTable table
capwapBaseRadioEventsStatsTable OBJECT-TYPE capwapBaseRadioEventsStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 6 } ::= { capwapBaseWtps 7 }
capwapBaseRadioEventsStatsEntry OBJECT-TYPE capwapBaseRadioEventsStatsEntry OBJECT-TYPE
SYNTAX CapwapBaseRadioEventsStatsEntry 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, capwapBaseWirelessBindingRadioId } INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId }
::= { capwapBaseRadioEventsStatsTable 1 } ::= { capwapBaseRadioEventsStatsTable 1 }
skipping to change at page 45, line 37 skipping to change at page 49, line 27
} }
capwapBaseRadioEventsStatsResetCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 1 } ::= { capwapBaseRadioEventsStatsEntry 1 }
capwapBaseRadioEventsStatsSwFailCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 2 } ::= { capwapBaseRadioEventsStatsEntry 2 }
capwapBaseRadioEventsStatsHwFailCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 3 } ::= { capwapBaseRadioEventsStatsEntry 3 }
capwapBaseRadioEventsStatsOtherFailCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 4 } ::= { capwapBaseRadioEventsStatsEntry 4 }
capwapBaseRadioEventsStatsUnknownFailCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 5 } ::= { capwapBaseRadioEventsStatsEntry 5 }
capwapBaseRadioEventsStatsConfigUpdateCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 6 } ::= { capwapBaseRadioEventsStatsEntry 6 }
capwapBaseRadioEventsStatsChannelChangeCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 7 } ::= { capwapBaseRadioEventsStatsEntry 7 }
capwapBaseRadioEventsStatsBandChangeCount 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 8 } ::= { capwapBaseRadioEventsStatsEntry 8 }
capwapBaseRadioEventsStatsCurrentNoiseFloor 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 9 } ::= { capwapBaseRadioEventsStatsEntry 9 }
capwapBaseRadioEventsStatsDecryptErrorCount 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 have occurred
WTP. Note that this field is only valid in cases where the WTP on the WTP. Note that this field is only valid in cases where
provides encryption/decryption services." the WTP provides encryption/decryption services."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 10 } ::= { capwapBaseRadioEventsStatsEntry 10 }
capwapBaseRadioEventsStatsLastFailType 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.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 11 } ::= { capwapBaseRadioEventsStatsEntry 11 }
-- End of capwapBaseRadioEventsStatsTable table -- 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 }
capwapBaseAcMaxRetransmit OBJECT-TYPE capwapBaseAcMaxRetransmit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 48, line 31 skipping to change at page 52, line 22
-- CAPWAP Base Parameters Group -- CAPWAP Base Parameters Group
capwapBaseParameters OBJECT IDENTIFIER capwapBaseParameters OBJECT IDENTIFIER
::= { capwapBaseObjects 3 } ::= { capwapBaseObjects 3 }
capwapBaseAcMaxRetransmit 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 "Represents the maximum number of retransmissions 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." 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 5415."
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." 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 5415."
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." 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 5415."
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, the AC MUST wait
for DTLS session deletion. for DTLS session deletion.
The value of the object is persistent at restart/reboot." 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 5415."
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." 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 5415."
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
skipping to change at page 50, line 13 skipping to change at page 54, line 4
::= { 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." 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 5415."
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." 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 5415."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseParameters 7 } ::= { capwapBaseParameters 7 }
capwapBaseAcWaitDTLSTimer OBJECT-TYPE capwapBaseAcWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 (30..4294967295) 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, the 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." 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 5415."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseParameters 8 } ::= { capwapBaseParameters 8 }
capwapBaseAcWaitJoinTimer OBJECT-TYPE capwapBaseAcWaitJoinTimer OBJECT-TYPE
SYNTAX Unsigned32 (20..4294967295) 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, the AC will wait
the DTLS session has been established until it receives the after the DTLS session has been established until it receives
Join Request from the WTP. This timer MUST be greater than 20 the Join Request from the WTP. This timer MUST be greater
seconds. than 20 seconds.
The value of the object is persistent at restart/reboot." 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 5415."
DEFVAL { 60 } DEFVAL { 60 }
::= { capwapBaseParameters 9 } ::= { capwapBaseParameters 9 }
capwapBaseAcEcnSupport OBJECT-TYPE capwapBaseAcEcnSupport OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
limited(0), limited(0),
fullAndLimited(1) fullAndLimited(1)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the support for the Explicit Congestion Notification "Represents the support for the Explicit Congestion Notification
(ECN) bits, as defined in [RFC3168]. (ECN) bits, as defined in [RFC3168].
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot.
The following enumerated values are supported:
limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support"
REFERENCE REFERENCE
"Section 4.7.25. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseParameters 10 } ::= { 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of failed DTLS session "Represents the number of failed DTLS session establishment
establishment attempts due to authentication failures." attempts due to authentication failures."
REFERENCE REFERENCE
"Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStats 1 } ::= { capwapBaseStats 1 }
capwapBaseFailedDTLSSessionCount OBJECT-TYPE capwapBaseFailedDTLSSessionCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of failed DTLS session "Represents the number of failed DTLS session
establishment attempts." establishment attempts."
REFERENCE REFERENCE
"Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.4. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStats 2 } ::= { capwapBaseStats 2 }
-- Notifications -- Notifications
capwapBaseChannelUp NOTIFICATION-TYPE capwapBaseChannelUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod capwapBaseNtfAuthenMethod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by AC when a CAPWAP channel "This notification is sent by the AC when a CAPWAP channel
established. The notification is separated for data or control established.
channel." The notification is separated for data or control channel."
::= { capwapBaseNotifications 1 } ::= { capwapBaseNotifications 1 }
capwapBaseChannelDown NOTIFICATION-TYPE capwapBaseChannelDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfChannelDownReason capwapBaseNtfChannelDownReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by AC when CAPWAP channel becomes "This notification is sent by the AC when CAPWAP channel
down. The notification is separated for data or control becomes down.
channel." The notification is separated for data or control channel."
::= { capwapBaseNotifications 2 } ::= { capwapBaseNotifications 2 }
capwapBaseDecryptErrorReport NOTIFICATION-TYPE capwapBaseDecryptErrorReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfRadioId, capwapBaseNtfRadioId,
capwapBaseNtfStationIdList capwapBaseNtfStationIdList
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP that has occurred "This notification is generated when a WTP that has occurred
decryption error since the last report." decryption error since the last report."
REFERENCE REFERENCE
"Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 3 } ::= { capwapBaseNotifications 3 }
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.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
::= { 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." the firmware image."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 receives message
elements in the configuration management messages which it was elements in the configuration management messages which it
unable to apply locally." is unable to apply locally."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
::= { 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.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 7 } ::= { capwapBaseNotifications 7 }
capwapBaseAuthenticationFailure NOTIFICATION-TYPE capwapBaseAuthenticationFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod, capwapBaseNtfAuthenMethod,
capwapBaseNtfAuthenFailureReason capwapBaseNtfAuthenFailureReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification will notify the authentication failure event, "The notification notifies an authentication failure event,
and provides the reason for it." and provides the reason for it."
::= { capwapBaseNotifications 8 } ::= { capwapBaseNotifications 8 }
-- Objects used only in notifications -- Objects used only in notifications
-- for notifications -- for notifications
capwapBaseNotifyVarObjects OBJECT IDENTIFIER capwapBaseNotifyVarObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 5 } ::= { capwapBaseObjects 5 }
capwapBaseNtfWtpId OBJECT-TYPE capwapBaseNtfWtpId OBJECT-TYPE
skipping to change at page 54, line 46 skipping to change at page 58, line 41
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP." "Represents the unique identifier of a WTP."
::= { capwapBaseNotifyVarObjects 1 } ::= { capwapBaseNotifyVarObjects 1 }
capwapBaseNtfRadioId OBJECT-TYPE capwapBaseNtfRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
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, which is
requires unique on a WTP. only required to be unique on a WTP.
For example, WTP A and WTP B will use same value of For example, WTP A and WTP B can use the same value of
capwapBaseNtfRadioId for their first radio." capwapBaseNtfRadioId for their first radio."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 2 } ::= { capwapBaseNotifyVarObjects 2 }
capwapBaseNtfChannelType OBJECT-TYPE capwapBaseNtfChannelType OBJECT-TYPE
SYNTAX CapwapBaseChannelTypeTC SYNTAX CapwapBaseChannelTypeTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the channel type for CAPWAP protocol." "Represents the channel type for CAPWAP protocol."
::= { capwapBaseNotifyVarObjects 3 } ::= { capwapBaseNotifyVarObjects 3 }
capwapBaseNtfAuthenMethod OBJECT-TYPE capwapBaseNtfAuthenMethod OBJECT-TYPE
SYNTAX CapwapBaseAuthenMethodTC SYNTAX CapwapBaseAuthenMethodTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents authentication method for Channel." "Represents authentication method for CAPWAP Channel."
::= { capwapBaseNotifyVarObjects 4 } ::= { capwapBaseNotifyVarObjects 4 }
capwapBaseNtfChannelDownReason OBJECT-TYPE capwapBaseNtfChannelDownReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
timeout(1), timeout(1),
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) - The 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
"Represents the list of station id which use semicolons to "Represents a list of station identifiers separated by
separate each station id." semicolons."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 6 } ::= { capwapBaseNotifyVarObjects 6 }
capwapBaseNtfAuthenFailureReason OBJECT-TYPE capwapBaseNtfAuthenFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
keyMismatch(1), keyMismatch(1),
invalidCA(2), invalidCert(2),
micError(3), reassemblyFailure(3),
timeout(4), decapFailure(4),
encapFailure(5),
timeout(6),
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 are not matched
invalidCA(2) - ca is not valid invalidCert(2) - Certification is not valid
micError(3) - detect MIC error reassemblyFailure(3) - Fragment reassembly failure
timeout(4) - WaitDTLS Timer is timeout decapFailure(4) - Decapsulation error
encapFailure(5) - Encapsulation error
timeout(6) - WaitDTLS timer 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 5415."
::= { capwapBaseNotifyVarObjects 7 } ::= { capwapBaseNotifyVarObjects 7 }
capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
operable(0), operable(0),
inoperable(1) inoperable(1)
} }
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:
operable(0) - To indicate radio is operable operable(0) - The radio is operable
inoperable(1) - To indicate radio is inoperable, and inoperable(1) - The radio is inoperable, and the
capwapBaseNtfRadioStatusCause object will capwapBaseNtfRadioStatusCause object
give reason in details" gives the reason in details"
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 why 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.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415."
::= { 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.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
::= { 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.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415."
::= { 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
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.36. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415."
::= { 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.36. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 module." CAPWAP-BASE-MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
capwapBaseAcNodeGroup, capwapBaseAcNodeGroup,
capwapBaseWtpProfileGroup,
capwapBaseWtpStateGroup, capwapBaseWtpStateGroup,
capwapBaseWtpsGroup, capwapBaseWtpGroup,
capwapBaseRadiosGroup, capwapBaseRadioGroup,
capwapBaseStationsGroup capwapBaseStationGroup
} }
GROUP capwapBaseAcNodeGroup2 GROUP capwapBaseAcNodeGroup2
DESCRIPTION DESCRIPTION
"The capwapBaseAcNodeGroup2 group is optional." "The capwapBaseAcNodeGroup2 group is optional."
GROUP capwapBaseAcNameListGroup GROUP capwapBaseAcNameListGroup
DESCRIPTION DESCRIPTION
"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 capwapBaseWtpProfileGroup2
DESCRIPTION DESCRIPTION
"The capwapBaseWtpsGroup2 group is optional." "The capwapBaseWtpProfileGroup2 group is optional."
GROUP capwapBaseWtpGroup2
DESCRIPTION
"The capwapBaseWtpGroup2 group is optional."
GROUP capwapBaseWtpEventsStatsGroup GROUP capwapBaseWtpEventsStatsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseWtpEventsStatsGroup group is optional." "The capwapBaseWtpEventsStatsGroup group is optional."
GROUP capwapBaseRadioEventsStatsGroup GROUP capwapBaseRadioEventsStatsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseRadioEventsStatsGroup 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 capwapBaseNotificationsGroup
DESCRIPTION DESCRIPTION
"The group capwapBaseNotificationGroup is optional." "The capwapBaseNotificationsGroup group is optional."
GROUP capwapBaseNotifyVarGroup GROUP capwapBaseNotifyVarsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseNotifyVarGroup group is optional. "The capwapBaseNotifyVarsGroup group is optional.
If capwapBaseNotificationGroup is supported, If capwapBaseNotificationsGroup is supported,
this group must be implemented." this group must be implemented."
::= { 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 "A collection of objects which are used to represent
basic properties for AC from CAPWAP protocol perspective." the basic properties for the AC from the CAPWAP
protocol perspective."
::= { capwapBaseGroups 1 } ::= { capwapBaseGroups 1 }
capwapBaseAcNodeGroup2 OBJECT-GROUP capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseDataChannelDTLSPolicyOptions, capwapBaseDataChannelDTLSPolicyOptions,
capwapBaseDataChannelDTLSPolicyConfig, capwapBaseDataChannelDTLSPolicyConfig,
capwapBaseControlChannelAuthenOptions, capwapBaseControlChannelAuthenOptions,
capwapBaseControlChannelAuthenConfig capwapBaseControlChannelAuthenConfig
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of objects which are used to represent
other properties such as security for AC from the other properties such as security for the AC from
CAPWAP protocol perspective." the CAPWAP protocol perspective."
::= { capwapBaseGroups 2 } ::= { capwapBaseGroups 2 }
capwapBaseAcNameListGroup OBJECT-GROUP capwapBaseAcNameListGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseAcNameListName, capwapBaseAcNameListName,
capwapBaseAcNameListPriority, capwapBaseAcNameListPriority,
capwapBaseAcNameListRowStatus capwapBaseAcNameListRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "A collection of objects which are used to configure
AC name list." the AC name list."
::= { capwapBaseGroups 3 } ::= { capwapBaseGroups 3 }
capwapBaseMacAclsGroup OBJECT-GROUP capwapBaseMacAclsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseMacAclStationId, capwapBaseMacAclStationId,
capwapBaseMacAclRowStatus capwapBaseMacAclRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "A collection of objects which are used to configure
stations ACL." the stations ACL."
::= { capwapBaseGroups 4 } ::= { capwapBaseGroups 4 }
capwapBaseWtpProfileGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpProfileName,
capwapBaseWtpProfileWTPSerialId,
capwapBaseWtpProfileWTPModelNumber,
capwapBaseWtpProfileWtpName,
capwapBaseWtpProfileWtpLocation,
capwapBaseWtpProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects which are used to configure
the WTP profile."
::= { capwapBaseGroups 5 }
capwapBaseWtpProfileGroup2 OBJECT-GROUP
OBJECTS {
capwapBaseWtpProfileWtpStaticIpEnable,
capwapBaseWtpProfileWtpStaticIpType,
capwapBaseWtpProfileWtpStaticIp,
capwapBaseWtpProfileWtpNetmask,
capwapBaseWtpProfileWtpGateway,
capwapBaseWtpProfileWtpFallbackEnable,
capwapBaseWtpProfileWtpEchoInterval,
capwapBaseWtpProfileWtpIdleTimeout,
capwapBaseWtpProfileWtpMaxDiscoveryInterval,
capwapBaseWtpProfileWtpReportInterval,
capwapBaseWtpProfileWtpSilentInterval,
capwapBaseWtpProfileWtpStatisticsTimer,
capwapBaseWtpProfileWtpWaitDTLSTimer,
capwapBaseWtpProfileWtpEcnSupport
}
STATUS current
DESCRIPTION
"A collection of optional objects which are used to
configure the WTP profile."
::= { capwapBaseGroups 6 }
capwapBaseWtpStateGroup OBJECT-GROUP capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpStateWtpIpAddressType, capwapBaseWtpStateWtpIpAddressType,
capwapBaseWtpStateWtpIpAddress, capwapBaseWtpStateWtpIpAddress,
capwapBaseWtpStateWtpPhyAddress, capwapBaseWtpStateWtpBaseMacAddress,
capwapBaseWtpState capwapBaseWtpState,
capwapBaseWtpStateWtpCurrWtpProfileId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of objects which are used to represent
WTP state information." the WTP's state information."
::= { capwapBaseGroups 5 } ::= { capwapBaseGroups 7 }
capwapBaseWtpsGroup OBJECT-GROUP capwapBaseWtpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpName,
capwapBaseWtpLocation,
capwapBaseWtpBaseMacAddress, capwapBaseWtpBaseMacAddress,
capwapBaseWtpTunnelModeOptions, capwapBaseWtpTunnelModeOptions,
capwapBaseWtpMacTypeOptions, capwapBaseWtpMacTypeOptions,
capwapBaseWtpDiscoveryType,
capwapBaseWtpRadiosInUseNum, capwapBaseWtpRadiosInUseNum,
capwapBaseWtpRadioNumLimit, capwapBaseWtpRadioNumLimit
capwapBaseWtpEcnSupport
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of objects which are used to represent
configuration and properties information for WTP the properties information for the WTPs in running state."
in running state." ::= { capwapBaseGroups 8 }
::= { capwapBaseGroups 6 }
capwapBaseWtpsGroup2 OBJECT-GROUP capwapBaseWtpGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpPhyIndex, capwapBaseWtpPhyIndex,
capwapBaseWtpDiscoveryType,
capwapBaseWtpStaticIpEnable,
capwapBaseWtpStaticIpType,
capwapBaseWtpStaticIp,
capwapBaseWtpNetmask,
capwapBaseWtpGateway,
capwapBaseWtpFallbackEnable,
capwapBaseWtpRetransmitCount, capwapBaseWtpRetransmitCount,
capwapBaseWtpMaxDiscoveries, capwapBaseWtpMaxDiscoveries,
capwapBaseWtpMaxFailedDTLSSessionRetry, capwapBaseWtpMaxFailedDTLSSessionRetry,
capwapBaseWtpMaxRetransmit, capwapBaseWtpMaxRetransmit,
capwapBaseWtpDataChannelKeepAliveTimer, capwapBaseWtpDataChannelKeepAliveTimer,
capwapBaseWtpDataChannelDeadInterval, capwapBaseWtpDataChannelDeadInterval,
capwapBaseWtpDiscoveryInterval, capwapBaseWtpDiscoveryInterval,
capwapBaseWtpDTLSSessionDeleteTimer, capwapBaseWtpDTLSSessionDeleteTimer,
capwapBaseWtpEchoInterval,
capwapBaseWtpIdleTimeout,
capwapBaseWtpImageDataStartTimer, capwapBaseWtpImageDataStartTimer,
capwapBaseWtpMaxDiscoveryInterval, capwapBaseWtpRetransmitInterval
capwapBaseWtpReportInterval,
capwapBaseWtpRetransmitInterval,
capwapBaseWtpSilentInterval,
capwapBaseWtpStatisticsTimer,
capwapBaseWtpWaitDTLSTimer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of optional objects which are used to represent
configuration and properties information for WTP the properties information for the WTPs in running state."
in running state." ::= { capwapBaseGroups 9 }
::= { capwapBaseGroups 7 }
capwapBaseRadiosGroup OBJECT-GROUP capwapBaseRadioGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWirelessBindingVirtualRadioIfIndex, capwapBaseWirelessBindingVirtualRadioIfIndex,
capwapBaseWirelessBindingType capwapBaseWirelessBindingType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of objects which are used to represent
wireless binding type, the mapping relationship between the wireless binding type, the mappings between the
'WLAN Virtual Radio Interface' and PHY radio." ifIndexes of WLAN Virtual Radio Interfaces and PHY radios."
::= { capwapBaseGroups 8 } ::= { capwapBaseGroups 10 }
capwapBaseStationsGroup OBJECT-GROUP capwapBaseStationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseStationAddedTime, capwapBaseStationAddedTime,
capwapBaseStationVlanName capwapBaseStationVlanName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "A collection of objects which are used to represent
stations' basic property." the stations' basic properties."
::= { capwapBaseGroups 9 } ::= { capwapBaseGroups 11 }
capwapBaseWtpEventsStatsGroup OBJECT-GROUP capwapBaseWtpEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpEventsStatsRebootCount, capwapBaseWtpEventsStatsRebootCount,
capwapBaseWtpEventsStatsInitCount, capwapBaseWtpEventsStatsInitCount,
capwapBaseWtpEventsStatsLinkFailureCount, capwapBaseWtpEventsStatsLinkFailureCount,
capwapBaseWtpEventsStatsSwFailureCount, capwapBaseWtpEventsStatsSwFailureCount,
capwapBaseWtpEventsStatsHwFailureCount, capwapBaseWtpEventsStatsHwFailureCount,
capwapBaseWtpEventsStatsOtherFailureCount, capwapBaseWtpEventsStatsOtherFailureCount,
capwapBaseWtpEventsStatsUnknownFailureCount, capwapBaseWtpEventsStatsUnknownFailureCount,
capwapBaseWtpEventsStatsLastFailureType capwapBaseWtpEventsStatsLastFailureType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "A 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 12 }
capwapBaseRadioEventsStatsGroup OBJECT-GROUP capwapBaseRadioEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseRadioEventsStatsResetCount, capwapBaseRadioEventsStatsResetCount,
capwapBaseRadioEventsStatsSwFailCount, capwapBaseRadioEventsStatsSwFailCount,
capwapBaseRadioEventsStatsHwFailCount, capwapBaseRadioEventsStatsHwFailCount,
capwapBaseRadioEventsStatsOtherFailCount, capwapBaseRadioEventsStatsOtherFailCount,
capwapBaseRadioEventsStatsUnknownFailCount, capwapBaseRadioEventsStatsUnknownFailCount,
capwapBaseRadioEventsStatsConfigUpdateCount, capwapBaseRadioEventsStatsConfigUpdateCount,
capwapBaseRadioEventsStatsChannelChangeCount, capwapBaseRadioEventsStatsChannelChangeCount,
capwapBaseRadioEventsStatsBandChangeCount, capwapBaseRadioEventsStatsBandChangeCount,
capwapBaseRadioEventsStatsCurrentNoiseFloor, capwapBaseRadioEventsStatsCurrentNoiseFloor,
capwapBaseRadioEventsStatsDecryptErrorCount, capwapBaseRadioEventsStatsDecryptErrorCount,
capwapBaseRadioEventsStatsLastFailType capwapBaseRadioEventsStatsLastFailType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "A 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 13 }
capwapBaseParametersGroup OBJECT-GROUP capwapBaseParametersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseAcMaxRetransmit, capwapBaseAcMaxRetransmit,
capwapBaseAcChangeStatePendingTimer, capwapBaseAcChangeStatePendingTimer,
capwapBaseAcDataCheckTimer, capwapBaseAcDataCheckTimer,
capwapBaseAcDTLSSessionDeleteTimer, capwapBaseAcDTLSSessionDeleteTimer,
capwapBaseAcEchoInterval, capwapBaseAcEchoInterval,
capwapBaseAcRetransmitInterval, capwapBaseAcRetransmitInterval,
capwapBaseAcSilentInterval, capwapBaseAcSilentInterval,
capwapBaseAcWaitDTLSTimer, capwapBaseAcWaitDTLSTimer,
capwapBaseAcWaitJoinTimer, capwapBaseAcWaitJoinTimer,
capwapBaseAcEcnSupport capwapBaseAcEcnSupport
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for the CAPWAP protocol's parameters."
::= { capwapBaseGroups 12 } ::= { capwapBaseGroups 14 }
capwapBaseStatsGroup OBJECT-GROUP capwapBaseStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseFailedDTLSAuthFailCount, capwapBaseFailedDTLSAuthFailCount,
capwapBaseFailedDTLSSessionCount capwapBaseFailedDTLSSessionCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for collecting the CAPWAP protocol's statistic."
::= { capwapBaseGroups 13 } ::= { capwapBaseGroups 15 }
capwapBaseNotificationGroup NOTIFICATION-GROUP capwapBaseNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
capwapBaseChannelUp, capwapBaseChannelUp,
capwapBaseChannelDown, capwapBaseChannelDown,
capwapBaseDecryptErrorReport, capwapBaseDecryptErrorReport,
capwapBaseJoinFailure, capwapBaseJoinFailure,
capwapBaseImageUpgradeFailure, capwapBaseImageUpgradeFailure,
capwapBaseConfigMsgError, capwapBaseConfigMsgError,
capwapBaseRadioOperableStatus, capwapBaseRadioOperableStatus,
capwapBaseAuthenticationFailure capwapBaseAuthenticationFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Collection of notifications in this MIB module." "A collection of notifications in this MIB module."
::= { capwapBaseGroups 14 } ::= { capwapBaseGroups 16 }
capwapBaseNotifyVarGroup OBJECT-GROUP capwapBaseNotifyVarsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfRadioId, capwapBaseNtfRadioId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod, capwapBaseNtfAuthenMethod,
capwapBaseNtfChannelDownReason, capwapBaseNtfChannelDownReason,
capwapBaseNtfStationIdList, capwapBaseNtfStationIdList,
capwapBaseNtfAuthenFailureReason, capwapBaseNtfAuthenFailureReason,
capwapBaseNtfRadioOperStatusFlag, capwapBaseNtfRadioOperStatusFlag,
capwapBaseNtfRadioStatusCause, capwapBaseNtfRadioStatusCause,
capwapBaseNtfJoinFailureReason, capwapBaseNtfJoinFailureReason,
capwapBaseNtfImageFailureReason, capwapBaseNtfImageFailureReason,
capwapBaseNtfConfigMsgErrorType, capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements capwapBaseNtfMsgErrorElements
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for notification." "Objects used for notifications."
::= { capwapBaseGroups 15 } ::= { capwapBaseGroups 17 }
END END
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects MAY be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. 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 capwapBaseWtProfileTable, and writable
under capwapBaseAcs group may disrupt allocation of resources in the objects under capwapBaseAcs group MAY disrupt allocation of resources
network. For example, a WTP's static IP address could be changed by in the network. For example, a WTP's static IP address could be
set capwapBaseWtpStaticIp object. changed by set capwapBaseWtpProfileWtpStaticIp 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 the AC's traffic burden. Also, some objects such as
capwapBaseDataChannelDTLSPolicyConfig 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 unable to access the network any more while illegal
stations have chance to access network. stations have chance to access the 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, an invalid value set for the
capwapBaseAcDataCheckTimer may influence CAPWAP state machine. capwapBaseAcDataCheckTimer MAY influence the 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 capwapBaseDataChannelDTLSPolicyOptions 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. channels.
- The capwapBaseWtpTable exposes WTP's important information like IP - The capwapBaseWtpTable exposes a WTP's important information like
address, MAC type and so on. tunnel mode, MAC type and so on.
- The capwapBaseWtpEventsStatsTable exposes WTP's failure - The capwapBaseWtpEventsStatsTable exposes a WTP's failure
information. information.
- The capwapBaseRadioEventsStatsTable exposes radio's failure - The capwapBaseRadioEventsStatsTable exposes a radio's failure
information. 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
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, the 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 module 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 the WTP Virtual Radio Interface.
type.
13. Contributors 13. Contributors
This MIB module 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, Fei Fang, Yu Liu, Sachin The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao
Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhang.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words [RFC2119] Bradner, S., "Key words for use in
for use in RFCs to RFCs to Indicate Requirement Levels",
Indicate Requirement BCP 14, RFC 2119, March 1997.
Levels", BCP 14,
RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D.,
Perkins, D., Ed., and Ed., and J. Schoenwaelder, Ed.,
J. Schoenwaelder, Ed., "Structure of Management Information
"Structure of Version 2 (SMIv2)", STD 58, RFC 2578,
Management Information
Version 2 (SMIv2)",
STD 58, RFC 2578,
April 1999. April 1999.
[RFC2579] McCloghrie, K., Ed., [RFC2579] McCloghrie, K., Ed., Perkins, D.,
Perkins, D., Ed., and Ed., and J. Schoenwaelder, Ed.,
J. Schoenwaelder, Ed., "Textual Conventions for SMIv2",
"Textual Conventions STD 58, RFC 2579, April 1999.
for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2580] McCloghrie, K., [RFC2580] McCloghrie, K., Perkins, D., and J.
Perkins, D., and J. Schoenwaelder, "Conformance
Schoenwaelder, Statements for SMIv2", STD 58,
"Conformance Statements
for SMIv2", STD 58,
RFC 2580, April 1999. RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. [RFC2863] McCloghrie, K. and F. Kastenholz,
Kastenholz, "The "The Interfaces Group MIB", RFC 2863,
Interfaces Group MIB", June 2000.
RFC 2863, June 2000.
[RFC3411] Harrington, D., [RFC3411] Harrington, D., Presuhn, R., and B.
Presuhn, R., and B. Wijnen, "An Architecture for
Wijnen, "An Describing Simple Network Management
Architecture for Protocol (SNMP) Management
Describing Simple Frameworks", STD 62, RFC 3411,
Network Management
Protocol (SNMP)
Management Frameworks",
STD 62, RFC 3411,
December 2002. December 2002.
[RFC3418] Presuhn, R., [RFC3418] Presuhn, R., "Management Information
"Management Information Base (MIB) for the Simple Network
Base (MIB) for the Management Protocol (SNMP)", STD 62,
Simple Network RFC 3418, December 2002.
Management Protocol
(SNMP)", STD 62,
RFC 3418,
December 2002.
[RFC4001] Daniele, M., Haberman, [RFC4001] Daniele, M., Haberman, B., Routhier,
B., Routhier, S., and S., and J. Schoenwaelder, "Textual
J. Schoenwaelder, Conventions for Internet Network
"Textual Conventions Addresses", RFC 4001, February 2005.
for Internet Network
Addresses", RFC 4001,
February 2005.
[RFC4133] Bierman, A. and K. [RFC4133] Bierman, A. and K. McCloghrie,
McCloghrie, "Entity MIB "Entity MIB (Version 3)", RFC 4133,
(Version 3)", RFC 4133,
August 2005. August 2005.
[I-D.ietf-capwap-protocol-specification] Montemurro, M., [RFC5415] Calhoun, P., Montemurro, M., and D.
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol
Specification", draft-
ietf-capwap-protocol-
specification-15 (work
in progress),
November 2008.
15.2. Informative References
[RFC3410] Case, J., Mundy, R.,
Partain, D., and B.
Stewart, "Introduction
and Applicability
Statements for
Internet-Standard
Management Framework",
RFC 3410,
December 2002.
[RFC4118] Yang, L., Zerfos, P.,
and E. Sadot,
"Architecture Taxonomy
for Control and
Provisioning of
Wireless Access Points
(CAPWAP)", RFC 4118,
June 2005.
[RFC4347] Rescorla, E. and N.
Modadugu, "Datagram
Transport Layer
Security", RFC 4347,
April 2006.
[IEEE.802-11.2007] "Information technology
- Telecommunications
and information
exchange between
systems - Local and
metropolitan area
networks - Specific
requirements - Part 11:
Wireless LAN Medium
Access Control (MAC)
and Physical Layer
(PHY) specifications",
IEEE Standard 802.11,
2007, <http://
standards.ieee.org/
getieee802/download/
802.11-2007.pdf>.
[I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M.,
Stanley, D., and P.
Calhoun, "CAPWAP
Protocol Binding for
IEEE 802.11", draft-
ietf-capwap-protocol-
binding-ieee80211-12
(work in progress),
November 2008.
[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 Stanley, "Control And Provisioning of
in the DESCRIPTION clause thatcapwapBaseAcnameListName is expected to Wireless Access Points (CAPWAP)
be a UTF-8 encoded string Protocol Specification", RFC 5415,
March 2009.
----------------------------------------------------------------- 15.2. Informative References
Yes, it is added
T17 - Object names in capwapBaseWtpStateTable do not respect the [IEEE.802-11.2007] "Information technology -
naming conditions relative to capwapBaseWtpStateEntry Telecommunications and information
exchange between systems - Local and
metropolitan area networks - Specific
requirements - Part 11: Wireless LAN
Medium Access Control (MAC) and
Physical Layer (PHY) specifications",
IEEE Standard 802.11, 2007, <http://
standards.ieee.org/getieee802/
download/802.11-2007.pdf>.
--------------------------------------------------------------- [RFC3168] Ramakrishnan, K., Floyd, S., and D.
Black, "The Addition of Explicit
Congestion Notification (ECN) to IP",
RFC 3168, September 2001.
Add one more WtpState in the object name. For example, [RFC3410] Case, J., Mundy, R., Partain, D., and
capwapBaseWtpId is to changed into capwapBaseWtpStateWtpId, other B. Stewart, "Introduction and
objects are similiar. Applicability Statements for
Internet-Standard Management
Framework", RFC 3410, December 2002.
all objects with new name: [RFC4118] Yang, L., Zerfos, P., and E. Sadot,
"Architecture Taxonomy for Control
and Provisioning of Wireless Access
Points (CAPWAP)", RFC 4118,
June 2005.
CapwapBaseWtpStateEntry ::= SEQUENCE { [RFC4347] Rescorla, E. and N. Modadugu,
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, "Datagram Transport Layer Security",
capwapBaseWtpStateWtpIpAddressType InetAddressType, RFC 4347, April 2006.
capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpStateWtpPhyAddress PhysAddress,
capwapBaseWtpState INTEGER
}
T18 - same for capwapBaseWtpStateTable [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP)
Protocol Binding for IEEE 802.11",
RFC 5416, March 2009.
----------------------------------------------------------------- [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C.,
and Y. Zhang, "CAPWAP Protocol
Binding MIB for IEEE 802.11",
(work in progress), October 2008.
Same as above Appendix A. Appendix A. Changes between -05 and -04
T19 - capwapBaseWtpName is of SYNTAX AsnmpAdminString which is 1) To close the issue 68 "Suggest Let Base MIB to Support a WTP
limited to SIZE 255, while the WTP name can be up to 512 characters Profile"
-------------------------------------------------------------- --------------------------------------------------------------
change with OCTET STRING(SIZE(512)) Add a new section 5.7. WTP Profile, update the section 8, add a new
table of capwapBaseWtpProfileTable and update the related MIB
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. 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 Hangzhou 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
EMail: young@h3c.com EMail: young@h3c.com
David Perkins (editor) David Perkins (editor)
SNMPinfo SNMPinfo
288 Quailbrook Ct San Carlos, 288 Quailbrook Ct San Carlos,
 End of changes. 375 change blocks. 
1514 lines changed or deleted 1183 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/