draft-ietf-capwap-base-mib-09.txt   rfc5833.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force (IETF) Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd. Request for Comments: 5833 Hangzhou H3C Tech. Co., Ltd.
Intended status: Informational D. Perkins, Ed. Category: Informational D. Perkins, Ed.
Expires: August 14, 2010 SNMPinfo ISSN: 2070-1721 C. Elliott, Ed.
C. Elliott, Ed.
Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
February 10, 2010 May 2010
CAPWAP Protocol Base MIB Control and Provisioning of Wireless Access Points (CAPWAP) Protocol
draft-ietf-capwap-base-mib-09 Base MIB
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 the managed objects for modeling the Control And describes the managed objects for modeling the Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB
module is presented as a basis for future work on a SNMP management module is presented as a basis for future work on the SNMP management
of the CAPWAP protocol. of the CAPWAP protocol.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on August 14, 2010. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5833.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 2, line 15 skipping to change at page 2, line 18
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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5
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 5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 8 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 8
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9
7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 10
7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10 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. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 68 10. Security Considerations . . . . . . . . . . . . . . . . . . . 69
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70
11.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 70 11.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 70
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 70 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 70
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 70 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 70
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 71
14.1. Normative References . . . . . . . . . . . . . . . . . . . 70 14.1. Normative References . . . . . . . . . . . . . . . . . . . 71
14.2. Informative References . . . . . . . . . . . . . . . . . . 71 14.2. Informative References . . . . . . . . . . . . . . . . . . 72
Appendix A. Appendix A. Changes between -09 and -08 . . . . . . . 72
1. Introduction 1. Introduction
The CAPWAP Protocol [RFC5415] defines a standard, interoperable The CAPWAP Protocol [RFC5415] defines a standard, interoperable
protocol, which enables an Access Controller (AC) to manage a protocol, which enables an Access Controller (AC) to manage a
collection of Wireless Termination Points(WTPs). collection of Wireless Termination Points (WTPs).
This document defines a MIB module that can be used to manage the This document defines a MIB module that can be used to manage the
CAPWAP implementations. This MIB module covers both configuration CAPWAP implementations. This MIB module covers both configuration
and WTP status-monitoring aspects of CAPWAP, and provides a way to and WTP status-monitoring aspects of CAPWAP, and provides a way to
reuse MIB modules for any wireless technology. It presented as a reuse MIB modules for any wireless technology. It presented as a
basis for future work on a SNMP management of the CAPWAP protocol. basis for future work on a SNMP management of the CAPWAP protocol.
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
[RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118]. [RFC5415] and the Architecture 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 physical layer (PHY) to transmit contains an radio frequency (RF) antenna and wireless physical layer
and receive station traffic for wireless access networks. (PHY) to transmit and receive 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
generic protocol defining AC and WTP control and data plane generic protocol defining AC and WTP control and data plane
communication via a CAPWAP protocol transport mechanism. CAPWAP communication via a CAPWAP protocol transport mechanism. CAPWAP
control messages, and optionally CAPWAP data messages, are secured control messages, and optionally CAPWAP data messages, are secured
using Datagram Transport Layer Security (DTLS) [RFC4347]. using Datagram Transport Layer Security (DTLS) [RFC4347].
CAPWAP Control Channel: A bi-directional flow defined by the AC IP CAPWAP Control Channel: A bi-directional flow defined by the AC IP
Address, WTP IP Address, AC control port, WTP control port and the Address, WTP IP Address, AC control port, WTP control port, and the
transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control
packets are sent and received. packets are sent and received.
CAPWAP Data Channel: A bi-directional flow defined by the AC IP CAPWAP Data Channel: A bi-directional flow defined by the AC IP
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 (medium access control). In Split MAC
data and management frames are encapsulated via the CAPWAP protocol mode, all Layer 2 wireless data and management frames are
and exchanged between the AC and the WTPs. The Local MAC mode allows encapsulated via the CAPWAP protocol and exchanged between the AC and
the data frames to be either locally bridged, or tunneled as 802.3 the WTPs. The Local MAC mode allows the data frames to be either
frames. locally bridged or tunneled as 802.3 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 define a binding protocol for it, e.g., the wireless technology MUST define a binding protocol for it, e.g., the
binding for IEEE 802.11, provided in [RFC5416]. binding for IEEE 802.11, provided in [RFC5416].
Autonomous Wireless Local Area Network (WLAN) Architecture: It is the Autonomous Wireless Local Area Network (WLAN) Architecture: It is the
traditional autonomous WLAN architecture, in which each WTP is a traditional autonomous WLAN architecture, in which each WTP is a
single physical device that implements all the wireless services. single physical device that implements all the wireless services.
skipping to change at page 5, line 5 skipping to change at page 5, line 11
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:
- Support centralized management and monitoring of WTPs from the AC - Support centralized management and monitoring of WTPs from the AC
in combination with the CAPWAP protocol; in combination with the CAPWAP protocol;
- Allow operators to make configurations for WTPs before and after - Allow operators to make configurations for WTPs before and after
they connect to the AC; they connect to the AC;
- Support querying of CAPWAP protocol parameters; - Support querying of CAPWAP protocol parameters;
- Support displaying of WTPs' current state and configuration; - Support displaying of WTPs' current states and configurations;
- Provide basic property information about the AC, WTP, radio and - Provide basic property information about the AC, WTPs, radios, and
station and their relationships; stations, and their relationships;
- Provide counters for events on WTPs and radios such as reboot and - Provide counters for events on WTPs and radios such as reboot and
hardware failure; hardware failure;
- Provide various notifications such as channel up and join failure. - Provide various notifications such as channel up and join failure.
5.2. Wireless Binding MIB Modules 5.2. Wireless Binding MIB Modules
Other Standards Developing Organizations (SDOs), such as IEEE, have Other Standards Development 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.,
IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are
called wireless binding MIB modules. called wireless binding MIB modules.
5.3. Design Objectives 5.3. Design Objectives
This document introduces a mechanism to avoid redefining MIB objects This document introduces a mechanism to avoid redefining MIB objects
in the existing MIB modules for a specific wireless technology, in in the existing MIB modules for a specific wireless technology, in
other words, a mechanism to reuse wireless binding MIB modules other words, a mechanism to reuse wireless binding MIB modules
defined by other SDOs. defined by other SDOs.
In summary, the CAPWAP-BASE-MIB module has 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, and answering the operator's control of wireless networks, and answering the operator's
requirements for centralized management, whatever the wireless requirements for centralized management, whatever the wireless
devices are configured and deployed (centralized, autonomous, or some devices are configured and deployed (centralized, autonomous, or
mix); some mix);
- To be consistent with the CAPWAP protocol; - To be consistent with the CAPWAP protocol;
- To be independent of any wireless technologies and be able to
reuse wireless binding MIB modules defined by other SDOs;
- To be independent of any wireless technologies and be able to reuse - To enable interoperability between vendors;
wireless binding MIB modules defined by other SDOs;
- To enable interoperability between vendors; - To meet the management requirements for the centralized WLAN
- To meet the management requirements for the centralized WLAN architecture.
architecture.
5.4. Design Idea 5.4. Design Idea
The basic design idea of the CAPWAP-BASE-MIB module is: The basic design idea of the CAPWAP-BASE-MIB module is:
- The SNMP agent MUST be run on the AC devices and is not REQUIRED on - The SNMP agent MUST be run on the AC devices and is not REQUIRED
the WTP devices. It follows the same model as the CAPWAP protocol: on the WTP devices. It follows the same model as the CAPWAP
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.
- The ifIndex [RFC2863] is used as a common index for corresponding - The ifIndex [RFC2863] is used as a common index for corresponding
interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific
wireless technologies; wireless technologies.
- The operator could manage and control the centralized WLAN - 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
For any wireless technology, the configuration and management of For any wireless technology, the configuration and management of
radios are very important. As usual, wireless binding MIB modules radios are very important. As usual, wireless binding MIB modules
support radio management on their own. For example, the MIB tables support radio management on their own. For example, the MIB tables
such as the Dot11OperationTable [IEEE.802-11.2007] are able to such as the dot11OperationTable [IEEE.802-11.2007] are able to
support WTP radio configuration. These tables use the ifIndex as the support WTP radio configuration. These tables use the ifIndex as the
index, and work well under autonomous WLAN architecture. index, and work well under autonomous WLAN architecture.
To reuse such wireless binding MIB modules is very important to To reuse such wireless binding MIB modules is very important to
centralized WLAN architectures. According to [RFC5415], a specific centralized WLAN architectures. According to [RFC5415], a specific
PHY radio could be identified by the combination of the identifiers PHY radio could be identified by the combination of the identifiers
of the WTP and radio (WTP ID + radio ID), so the key point is to make of the WTP and radio (WTP ID + Radio ID), so the key point is to make
use of the ifIndex idea and find a way to maintain the mappings use of the ifIndex idea and find a way to maintain the mappings
between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism, between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism,
an ifIndex can identify an interface in an abstract way, and it does an ifIndex can identify an interface in an abstract way, and it does
NOT care for the interface's PHY location (either on the WTP or AC). NOT care for the interface's PHY location (either on the WTP or AC).
The AC can have WTP Virtual Radio Interfaces to logically represent The AC can have WTP Virtual Radio Interfaces to logically represent
PHY radios on the WTP. It looks like that PHY radios are located on PHY radios on the WTP. From the operator's perspective, it appears
the AC, and PHY location of the WTP (radio) is hidden to the that PHY radios are located on the AC, and the PHY location of the
operator. The operator can operate radios through MIB tables with WTP (radio) is hidden. The operator can operate radios through MIB
the ifIndex of a WTP Virtual Radio Interface. As a type of abstract tables with the ifIndex of a WTP Virtual Radio Interface. As a type
interface, the WTP Virtual Radio Interface could be used by any of abstract interface, the WTP Virtual Radio Interface could be used
wireless technology such as IEEE 802.11 and 802.16. The by any wireless technology such as IEEE 802.11 and 802.16. The
capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used
to store the mappings between the 'WTP ID+ Radio ID' and the ifIndex. 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 [RFC5415], when According to the CAPWAP Protocol specification [RFC5415], when
defining a binding for wireless technologies, the authors MUST defining a binding for wireless technologies, the authors MUST
include any necessary definitions for technology-specific messages include any necessary definitions for technology-specific messages
and all technology-specific message elements for those messages. A and all technology-specific message elements for those messages. A
CAPWAP binding protocol is required for a specific wireless binding CAPWAP binding protocol is required for a specific wireless binding
technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding. technology, e.g., the protocol of [RFC5416] 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 [RFC5416] defines WLAN management. The WLAN example, the protocol of [RFC5416] defines WLAN management. The WLAN
refers to a logical component instantiated on a WTP device. A single refers to a logical component instantiated on a WTP device. A single
physical WTP MAY operate a number of WLANs. Also, Local or Split MAC physical WTP MAY operate a number of WLANs. Also, Local or Split MAC
modes could be specified for a WLAN. The MAC mode for a WLAN is not modes could be specified for a WLAN. The MAC mode for a WLAN is not
in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in
addition to the existing wireless binding MIB modules defined by addition to the existing wireless binding MIB modules defined by
other SDOs, a CAPWAP protocol wireless binding MIB module is required other SDOs, a CAPWAP protocol wireless binding MIB module is required
to be defined for a wireless binding, e.g, the CAPWAP Protocol to be defined for a wireless binding, e.g, the CAPWAP Protocol
Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. Binding MIB for IEEE 802.11 [RFC5834].
5.7. WTP Profile 5.7. WTP Profile
In a centralized WLAN architecture, a WTP profile is used to make In a centralized WLAN architecture, a WTP profile is used to make
configurations such as static IP address for a WTP before and after configurations such as a static IP address for a WTP before and after
it connects to the AC. It MUST contain the Base MAC address it connects to the AC. It MUST contain the Base MAC address
[RFC5415] of the WTP because the CAPWAP message received from the WTP [RFC5415] of the WTP because the CAPWAP message received from the WTP
contains the Base MAC address and the AC uses this Base MAC address contains the Base MAC address and the AC uses this Base MAC address
to find the corresponding WTP profile. to find the corresponding WTP profile.
In the section 4.6.40 [RFC5415], it omits indicating that the WTP's Section 4.6.40 of [RFC5415] omits indicating that the WTP's Base MAC
Base MAC address MUST be included in the WTP Board Data message address MUST be included in the WTP Board Data message element. This
element. It is a known errata item and assumed to be fixed in future is a known errata item [Err1832] and should be fixed in any future
by the editors of the RFC5415. revision of RFC 5415.
Another important function of WTP profile is to trigger the creation Another important function of WTP profile is to trigger the creation
of WTP Virtual Radio Interfaces on the AC. To implement this of WTP Virtual Radio Interfaces on the AC. To implement this
function, a WTP profile MUST include the WTP's model number function, a WTP profile MUST include the WTP's model number
[RFC5415], which reflects the number of PHY radios on the WTP. In [RFC5415], which reflects the number of PHY radios on the WTP. In
this way, the creation of a WTP profile triggers the AC to this way, the creation of a WTP profile triggers the AC to
automatically create the same number of WTP Virtual Radio Interfaces automatically create the same number of WTP Virtual Radio Interfaces
corresponding to the WTP's PHY radios without manual intervention. corresponding to the WTP's PHY radios without manual intervention.
With the ifIndexes of WTP Virtual Radio Interfaces, the operator With the ifIndexes of WTP Virtual Radio Interfaces, the operator
could configure and manage the WTP's PHY radios through the wireless could configure and manage the WTP's PHY radios through the wireless
binding MIB modules. binding MIB modules.
6. Structure of the MIB Module 6. Structure of the MIB Module
The MIB objects are derived from the CAPWAP protocol document The MIB objects are derived from the CAPWAP protocol document
[RFC5415]. [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 the 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 Lists
List(ACL). (ACLs).
3) capwapBaseWtpProfileTable 3) capwapBaseWtpProfileTable
The WTP profile table is used to configure WTP profiles for WTPs to The WTP profile table is used to configure WTP profiles for WTPs
be managed before they connect to the AC. An operator could change a to be managed before they connect to the AC. An operator could
WTP's current configuration by changing the values of parameters in change a WTP's current configuration by changing the values of
the corresponding WTP profile, then the WTP could get the new parameters in the corresponding WTP profile, then the WTP could
configuration through the CAPWAP control channel. get the new configuration through the CAPWAP control channel.
4) capwapBaseWtpStateTable 4) capwapBaseWtpStateTable
The WTPs status table is used to indicate the AC's CAPWAP FSM state The state table of WTPs is used to indicate the AC's CAPWAP FSM
for each WTP, and helps operator to query WTPs' current state for each WTP, and helps the operator to query a WTP's
configuration. current configuration.
5) capwapBaseWtpTable 5) capwapBaseWtpTable
The WTPs table is used display properties of WTPs in running state. The WTP table is used to display properties of the WTPs in running
state.
6) capwapBaseWirelessBindingTable 6) capwapBaseWirelessBindingTable
The wireless binding table is used to display the mappings between The wireless binding table is used to display the mappings between
WTP Virtual Radio Interfaces and PHY radios, and the wireless binding WTP Virtual Radio Interfaces and PHY radios, and the wireless
type for each PHY radio. binding type for each PHY radio.
7) 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.
8) 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.
9) capwapBaseRadioEventsStatsTable 9) capwapBaseRadioEventsStatsTable
The radio events statistic table is used for collecting radio reset The radio events statistic table is used for collecting radio
count, channel change count, hardware failure count and so on. reset 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 CAPWAP-BASE-MIB module does not duplicate the objects of the The CAPWAP-BASE-MIB module does not duplicate the objects of the
'system' group in the SNMPv2-MIB [RFC3418] that is defined as being '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. entity and certain other system-wide data.
skipping to change at page 9, line 33 skipping to change at page 9, line 44
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing WTP PHY radios that extensions to the Interfaces Group for managing WTP PHY radios that
are modeled as interfaces. are modeled as interfaces.
The IF-MIB module is required to be supported on the AC. Each PHY The IF-MIB module is required to be supported on the AC. Each PHY
radio on the WTP corresponds to a WTP Virtual Radio Interface on the radio on the WTP corresponds to a WTP Virtual Radio Interface on the
AC. The WTP Virtual Radio Interface provides a way to configure the AC. The WTP Virtual Radio Interface provides a way to configure the
radio's parameters and query radio's traffic statistics, and reuse radio's parameters and query radio's traffic statistics, and reuse
wireless binding modules defined by other SDOs. The interface MUST wireless binding modules defined by other SDOs. The interface MUST
be modeled as an ifEntry, and ifEntry objects such as ifIndex, be modeled as an ifEntry, and ifEntry objects such as ifIndex,
ifDescr, ifName, ifAlias are to be used as per [RFC2863]. ifDescr, ifName, and ifAlias are to be used as per [RFC2863].
Also, as an ifIndex [RFC2863] is used as a common index for a Also, as an ifIndex [RFC2863] is used as a common index for
corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless
technologies MIB modules, the AC MUST have a mechanism that preserves technologies MIB modules, the AC MUST have a mechanism that preserves
the values of the ifIndexes 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 the need for a standardized way The ENTITY-MIB module [RFC4133] meets the need for a standardized way
of representing a single agent, which supports multiple instances of of representing a single agent that supports multiple instances of
one 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.
In a centralized WLAN architecture, the SNMP agent runs on the AC, In a centralized WLAN architecture, the SNMP agent runs on the AC and
and is not required on the WTP. With the ENTITY-MIB module on the is not required on the WTP. With the ENTITY-MIB module on the AC, it
AC, it could keep entity information such as firmware revision and could keep entity information such as firmware revision and software
software revision of the AC and WTPs. From the ENTITY-MIB module's 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 (that is, the WTPs connected to AC), and multiple physical entities (that is, the WTPs connected to AC), and
all entities are each identified by a Physical index. The all entities are each identified by a physical index. The
capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the
capwapBaseWtpPhyIndex object to store the mappings of WTP object capwapBaseWtpPhyIndex object to store the mappings of WTP object
between CAPWAP-BASE-MIB and ENTITY-MIB modules. between CAPWAP-BASE-MIB and ENTITY-MIB modules.
By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules, By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules,
operators could query the status and properties of the AC and WTPs. operators could query the status and properties of the AC and WTPs.
For example, they could get a WTP's current status through the For example, they could get a WTP's current status through the
CAPWAP-BASE-MIB module, and a WTP's software revision information CAPWAP-BASE-MIB module, and a WTP's software revision information
through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not
duplicate those objects defined in the ENTITY-MIB module. duplicate those objects defined in the ENTITY-MIB module.
skipping to change at page 10, line 29 skipping to change at page 10, line 43
[IEEE.802-11.2007]) is required to be supported on the AC. The [IEEE.802-11.2007]) is required to be supported on the AC. The
CAPWAP-BASE-MIB module is able to support any wireless binding. CAPWAP-BASE-MIB module is able to support any wireless binding.
Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a 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 SYSAPPL-MIB [RFC2287], The following MIB module IMPORTS objects from SYSAPPL-MIB [RFC2287],
SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF- SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580],
MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB IF-MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB
[RFC4001] and ENTITY-MIB [RFC4133]. [RFC4001], and ENTITY-MIB [RFC4133].
8. Example of CAPWAP-BASE-MIB Module Usage 8. Example of CAPWAP-BASE-MIB Module Usage
Here takes IEEE 802.11 binding as an example to show how the MIB Below, the IEEE 802.11 binding is used as an example of how the MIB
modules operate. modules operate.
1) Create a WTP profile 1) Create a WTP profile.
Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create
the WTP profile as follows: the WTP profile as follows:
In CapwapBaseWtpProfileTable In capwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 123456', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWtpMacAddress = '00:01:01:01:01:00', capwapBaseWtpProfileWtpMacAddress = '00:01:01:01:01:00',
capwapBaseWtpProfileWtpModelNumber = 'WTP123', capwapBaseWtpProfileWtpModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 123456', capwapBaseWtpProfileWtpName = 'WTP 123456',
capwapBaseWtpProfileWtpLocation = 'office', capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1), capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1), capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIpAddress = '192.0.2.10', capwapBaseWtpProfileWtpStaticIpAddress = '192.0.2.10',
skipping to change at page 11, line 27 skipping to change at page 11, line 30
capwapBaseWtpProfileWtpGateway = '192.0.2.1', capwapBaseWtpProfileWtpGateway = '192.0.2.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1), capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30, capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300, capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
capwapBaseWtpProfileWtpReportInterval = 120, capwapBaseWtpProfileWtpReportInterval = 120,
capwapBaseWtpProfileWtpStatisticsTimer = 120, capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpEcnSupport = limited(0) capwapBaseWtpProfileWtpEcnSupport = limited(0)
} }
Suppose the WTP with model number 'WTP123' has one PHY radio and this Suppose the WTP with model number 'WTP123' has one PHY radio,
PHY radio is identified by ID 1. The creation of this WTP profile which is identified by ID 1. The creation of this WTP profile
triggers the AC to automatically create a WTP Virtual Radio Interface triggers the AC to automatically create a WTP Virtual Radio
and add a new row object to the CapwapBaseWirelessBindingTable Interface and add a new row object to the
without manual intervention. Suppose the ifIndex of the WTP Virtual capwapBaseWirelessBindingTable without manual intervention.
Radio Interface is 10. The following information is stored in the Suppose the ifIndex of the WTP Virtual Radio Interface is 10. The
CapwapBaseWirelessBindingTable. following information is stored in the
capwapBaseWirelessBindingTable.
In CapwapBaseWirelessBindingTable In capwapBaseWirelessBindingTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWirelessBindingRadioId = 1, capwapBaseWirelessBindingRadioId = 1,
capwapBaseWirelessBindingVirtualRadioIfIndex = 10, capwapBaseWirelessBindingVirtualRadioIfIndex = 10,
capwapBaseWirelessBindingType = dot11(2) capwapBaseWirelessBindingType = dot11(2)
} }
The WTP Virtual Radio Interfaces on the AC correspond to the PHY The WTP Virtual Radio Interfaces on the AC correspond to the PHY
radios on the WTP. The WTP Virtual Radio Interface is modeled by radios on the WTP. The WTP Virtual Radio Interface 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 = 254,
RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '00:00:00:00:00:00', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = false(0), 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) Query the ifIndexes of WTP Virtual Radio Interfaces 2) Query the ifIndexes of WTP Virtual Radio Interfaces.
Before configuring PHY radios, the operator needs to get the Before configuring PHY radios, the operator needs to get the
ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY
radios. radios.
As CapwapBaseWirelessBindingTable already stores the mappings between As capwapBaseWirelessBindingTable already stores the mappings
PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual
Interfaces, the operator can get the ifIndex information by querying Radio Interfaces, the operator can get the ifIndex information by
this table. Such a query operation SHOULD run from radio ID 1 to querying this table. Such a query operation SHOULD run from radio
radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex ID 1 to radio ID 31 according to [RFC5415]), and stop when an
value (0) is returned. invalid ifIndex value (0) is returned.
This example uses capwapBaseWtpProfileId = 1 and This example uses capwapBaseWtpProfileId = 1 and
capwapBaseWirelessBindingRadioId = 1 as inputs to query the capwapBaseWirelessBindingRadioId = 1 as inputs to query the
CapwapBaseWirelessBindingTable, and gets capwapBaseWirelessBindingTable, and gets
capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses
capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId =
and gets a invalid ifIndex value (0), so the the query operation 2, and gets an invalid ifIndex value (0), so the query operation
ends. This method gets not only the ifIndexes of WTP Virtual Radio ends. This method gets not only the ifIndexes of WTP Virtual
Interfaces, but also the numbers of PHY radios. Besides checking Radio Interfaces, but also the numbers of PHY radios. Besides
whether the ifIndex value is valid, the operator SHOULD check whether checking whether the ifIndex value is valid, the operator SHOULD
the capwapBaseWirelessBindingType is the desired binding type. check whether the capwapBaseWirelessBindingType is the desired
binding type.
3) Configure specific wireless binding parameters for a WTP Virtual 3) Configure specific wireless binding parameters for a WTP Virtual
Radio Interface Radio Interface.
This configuration is made on the AC through a specific wireless This configuration is made on the AC through a specific wireless
binding MIB module such as the IEEE 802.11 MIB module. binding MIB module such as the IEEE 802.11 MIB module.
The following shows an example of configuring parameters for a WTP The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 Virtual Radio Interface with ifIndex 10 through the IEEE 802.11
Dot11OperationTable [IEEE.802-11.2007]. dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = '00:00:00:00:00:00', dot11MACAddress = '00:00:00:00:00:00',
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',
dot11CAPLimit = 2,
dot11HCCWmin = 0,
dot11HCCWmax = 0,
dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1,
dot11EDCAAveragingPeriod = 5
} }
4) Current configuration status report from the WTP to the AC 4) Get the current configuration status report from the WTP to the
AC.
According to [RFC5415], before a WTP that has joined the AC gets According to [RFC5415], before a WTP that has joined the AC gets
configuration from the AC, it needs to report its current configuration from the AC, it needs to report its current
configuration status by sending a configuration status request configuration status by sending a configuration status request
message to the AC, which use the message to update MIB objects on the message to the AC, which uses the message to update MIB objects on
AC. For example, for IEEE 802.11 binding, the AC updates data in the the AC. For example, for IEEE 802.11 binding, the AC updates data
ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the in the ifTable [RFC2863] and IEEE 802.11 MIB module, and so on,
message. For ifIndex 10, its ifOperStatus in ifTable is updated according to the message. For ifIndex 10, its ifOperStatus in
according to the current radio operational status in the CAPWAP ifTable is updated according to the current radio operational
message. status in the CAPWAP message.
5) Query WTP and radio statistics data 5) Query WTP and radio statistical data.
After WTPs start to run, the 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 statistical data through CAPWAP-BASE-MIB and the specific binding
module on the AC. For example, through dot11CountersTable in the MIB module on the AC. For example, through dot11CountersTable in
IEEE 802.11 MIB module, the operator could query the counter data of the IEEE 802.11 MIB module, the operator could query the counter
a radio using the ifIndex of the corresponding WTP Virtual Radio data of a radio using the ifIndex of the corresponding WTP Virtual
Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB Radio Interface. With the capwapBaseWtpTable table in the CAPWAP-
module, the operator could query the properties of running WTPs. BASE-MIB module, the operator could query the properties of
running WTPs.
6) MIB operations through a CAPWAP protocol wireless binding MIB 6) Run 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].
7) Query other properties of a WTP For example, for the CAPWAP IEEE 802.11 binding protocol
[RFC5416], some MIB operations such as MAC mode configuration for
a WLAN depend on the CAPWAP Protocol Binding MIB for IEEE 802.11
[RFC5834]. For more information, refer to [RFC5834].
The Operator could query MIB objects in the ENTITY-MIB [RFC4133] 7) Query other properties of a WTP.
module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable
of CAPWAP-BASE-MIB module. The properties of a WTP such as software The Operator could query MIB objects in the ENTITY-MIB [RFC4133]
version, hardware version are available in the ENTITY-MIB module. module by using the capwapBaseWtpPhyIndex in the
capwapBaseWtpTable of CAPWAP-BASE-MIB module. The properties of a
WTP such as software version, hardware version are available in
the ENTITY-MIB module.
9. Definitions 9. Definitions
CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
PhysAddress, TEXTUAL-CONVENTION, TruthValue, PhysAddress, TEXTUAL-CONVENTION, TruthValue,
DateAndTime, RowStatus DateAndTime, RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
skipping to change at page 14, line 43 skipping to change at page 15, line 9
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, Gauge32, TimeTicks Integer32, Unsigned32, Counter32, Gauge32, TimeTicks
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 "201002100000Z" -- Feb 10th, 2010 LAST-UPDATED "201004300000Z" -- 30 April 2010
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 (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza
NO.9 Shangdi 9th Street,Haidian District, NO. 9 Shangdi 9th Street, Haidian District
Beijing Beijing 100085
China(100085) China
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com Email: rishyang@gmail.com
David T. Perkins David T. Perkins (editor)
228 Bayview Dr 228 Bayview Dr.
San Carlos, CA 94070 San Carlos, CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@dsperkins.com
Chris Elliott Chris Elliott (editor)
Cisco Systems, Inc. 1516 Kent St.
7025 Kit Creek Rd., P.O. Box 14987 Durham, NC 27707
Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-308-1216
Email: chelliot@gmail.com Email: chelliot@pobox.com
Yong Zhang Yong Zhang (editor)
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2010 The Internet Society. This version of "Copyright (c) 2010 IETF Trust and the persons identified as
the MIB module is part of RFC xxx; see the RFC itself authors of the code. All rights reserved.
for full legal notices.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 5833;
see the RFC itself 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 "201002100000Z" REVISION "201004300000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC 5833"
::= { mib-2 xxx } ::= { mib-2 196 }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP profile." "Represents the unique identifier of a WTP profile."
SYNTAX Unsigned32 (0..4096) SYNTAX Unsigned32 (0..4096)
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP instance. "Represents the unique identifier of a WTP instance.
As usual, the Base MAC address of WTP is used." As usual, the Base MAC address of the WTP is used."
SYNTAX OCTET STRING (SIZE(6|8)) SYNTAX OCTET STRING (SIZE(6|8))
CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a station instance. "Represents the unique identifier of a station instance.
As usual, the MAC address of station is used." As usual, the MAC address of the station is used."
SYNTAX OCTET STRING (SIZE(6|8)) SYNTAX OCTET STRING (SIZE(6|8))
CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the 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 a 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 5415." "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 a 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
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object object takes zero as starting value; this MIB object
follows this rule." follows that rule."
REFERENCE REFERENCE
"Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." "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.
skipping to change at page 17, line 41 skipping to change at page 18, line 14
CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type for a WTP. "Represents the authentication credential type for a 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 a mandatory requirement, CAPWAP control channel
authentication SHOULD use DTLS, and either by certificate or authentication SHOULD use DTLS, either by certificate or
PSK. For data channel, DTLS is optional." PSK. For data channel authentication, DTLS is optional."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
clear(2), clear(2),
x509(3), x509(3),
psk(4) psk(4)
} }
-- Top-level components of this MIB module
-- Notifications -- Notifications
capwapBaseNotifications OBJECT IDENTIFIER capwapBaseNotifications OBJECT IDENTIFIER
::= { capwapBaseMIB 0 } ::= { capwapBaseMIB 0 }
-- Tables, Scalars -- Tables, Scalars
capwapBaseObjects OBJECT IDENTIFIER capwapBaseObjects OBJECT IDENTIFIER
::= { capwapBaseMIB 1 } ::= { capwapBaseMIB 1 }
-- Conformance -- Conformance
capwapBaseConformance OBJECT IDENTIFIER capwapBaseConformance OBJECT IDENTIFIER
::= { capwapBaseMIB 2 } ::= { capwapBaseMIB 2 }
-- AC Objects Group -- AC Objects Group
capwapBaseAc OBJECT IDENTIFIER capwapBaseAc OBJECT IDENTIFIER
::= { capwapBaseObjects 1 } ::= { capwapBaseObjects 1 }
capwapBaseWtpSessions OBJECT-TYPE capwapBaseWtpSessions OBJECT-TYPE
SYNTAX Gauge32 (0..65535) SYNTAX Gauge32 (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 that are connecting to
the AC." the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." "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 on "Represents the maximum number of WTP sessions configured on
the AC. 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 5415." "Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 2 } ::= { capwapBaseAc 2 }
capwapBaseStationSessions OBJECT-TYPE capwapBaseStationSessions OBJECT-TYPE
SYNTAX Gauge32 (0..65535) SYNTAX Gauge32 (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 that 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 5415." "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 5415." "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
CAPWAP data channel. the CAPWAP data channel.
The AC MAY support more than one option, represented by the bit The AC MAY support more than one option, represented by the bit
field below: field below:
other(0) - Other method, for example, vendor specific other(0) - Other method, for example, vendor specific
clear(1) - Clear text clear(1) - Clear text
dtls(2) - DTLS" dtls(2) - DTLS"
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 5 } ::= { capwapBaseAc 5 }
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
skipping to change at page 20, line 4 skipping to change at page 20, line 26
} }
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 CAPWAP 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 5415." "Section 4.6.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 6 } ::= { capwapBaseAc 6 }
-- 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 configure the AC name list. "A table of objects that configure the AC name list.
Values of all read-create objects in this table are Values of all read-create objects in this table are
persistent at restart/reboot." persistent at restart/reboot."
REFERENCE REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." "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 the AC name list." "A set of objects that configures the AC name list."
INDEX { capwapBaseAcNameListId } INDEX { capwapBaseAcNameListId }
::= { capwapBaseAcNameListTable 1 } ::= { capwapBaseAcNameListTable 1 }
CapwapBaseAcNameListEntry ::= SEQUENCE { CapwapBaseAcNameListEntry ::= SEQUENCE {
capwapBaseAcNameListId Unsigned32, capwapBaseAcNameListId Unsigned32,
capwapBaseAcNameListName LongUtf8String, capwapBaseAcNameListName LongUtf8String,
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 the unique identifier of a AC Name list." "Represents the unique identifier of an AC Name list."
::= { capwapBaseAcNameListEntry 1 } ::= { capwapBaseAcNameListEntry 1 }
capwapBaseAcNameListName OBJECT-TYPE capwapBaseAcNameListName OBJECT-TYPE
SYNTAX LongUtf8String (SIZE(1..512)) SYNTAX LongUtf8String (SIZE(1..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 5415." "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 AC, 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 5415." "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 object is used to create, modify, and/or delete a row "This object is used to create, modify, and/or delete a row
in this table. in this table.
The value of capwapBaseAcNameListName and The value of capwapBaseAcNameListName and
capwapBaseAcNameListPriority can be changed when this capwapBaseAcNameListPriority can be changed when this
object is in state ''active'' or in ''notInService''. object is in state 'active' or in 'notInService'.
The capwapBaseAcNameListRowStatus may be changed to ''active''
The capwapBaseAcNameListRowStatus may be changed to 'active'
if all the managed objects in the conceptual row with if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values." MAX-ACCESS read-create have been assigned valid values."
::= { capwapBaseAcNameListEntry 4 } ::= { capwapBaseAcNameListEntry 4 }
-- 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
Lists (ACL). Lists (ACLs).
The WTP will not provide service to the MAC addresses The WTP will not provide service to the MAC addresses
configured in this table. configured in this table.
Values of all read-create objects in this table are persistent Values of all read-create objects in this table are persistent
at AC restart/reboot." at AC restart/reboot."
REFERENCE REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." "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 configures station Access Control
List (ACL)." Lists (ACLs)."
INDEX { capwapBaseMacAclId } INDEX { capwapBaseMacAclId }
::= { capwapBaseMacAclTable 1 } ::= { capwapBaseMacAclTable 1 }
CapwapBaseMacAclEntry ::= SEQUENCE { CapwapBaseMacAclEntry ::= SEQUENCE {
capwapBaseMacAclId Unsigned32, capwapBaseMacAclId Unsigned32,
capwapBaseMacAclStationId CapwapBaseStationIdTC, capwapBaseMacAclStationId CapwapBaseStationIdTC,
capwapBaseMacAclRowStatus RowStatus capwapBaseMacAclRowStatus RowStatus
} }
capwapBaseMacAclId OBJECT-TYPE capwapBaseMacAclId OBJECT-TYPE
skipping to change at page 22, line 41 skipping to change at page 23, line 13
::= { 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 the MAC address of a station to which WTPs will "Represents the MAC address of a station to which WTPs will
no longer provides service." no longer provides service."
REFERENCE REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." "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 object is used to create, modify, and/or delete a row "This object is used to create, modify, and/or delete a row
in this table. in this table.
The value of capwapBaseMacAclStationId can be changed when The value of capwapBaseMacAclStationId can be changed when
this object is in state ''active'' or in ''notInService''. this object is in state 'active' or in 'notInService'.
The capwapBaseMacAclRowStatus may be changed to 'active'
The capwapBaseMacAclRowStatus may be changed to ''active''
if all the managed objects in the conceptual row with if all the managed objects in the conceptual row with
MAX-ACCESS read-create have been assigned valid values." MAX-ACCESS read-create have been assigned valid values."
::= { 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
skipping to change at page 23, line 32 skipping to change at page 24, line 4
SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that configure WTP profiles for WTPs to "A table of objects that configure WTP profiles for WTPs to
be managed before they connect to the AC. be managed before they connect to the AC.
An operator could change a WTP's configuration by changing An operator could change a WTP's configuration by changing
the values of parameters in the corresponding WTP profile, the values of parameters in the corresponding WTP profile,
then the WTP could get the new configuration through the then the WTP could get the new configuration through the
CAPWAP control channel. CAPWAP control channel.
Values of all read-create objects in this table are Values of all read-create objects in this table are
persistent at restart/reboot." persistent at restart/reboot."
::= { capwapBaseWtps 1 } ::= { capwapBaseWtps 1 }
capwapBaseWtpProfileEntry OBJECT-TYPE capwapBaseWtpProfileEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileEntry SYNTAX CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that configure and display a WTP profile." "A set of objects that configures and displays a WTP profile."
INDEX { capwapBaseWtpProfileId } INDEX { capwapBaseWtpProfileId }
::= { capwapBaseWtpProfileTable 1 } ::= { capwapBaseWtpProfileTable 1 }
CapwapBaseWtpProfileEntry ::= SEQUENCE { CapwapBaseWtpProfileEntry ::= SEQUENCE {
capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC,
capwapBaseWtpProfileName SnmpAdminString, capwapBaseWtpProfileName SnmpAdminString,
capwapBaseWtpProfileWtpMacAddress CapwapBaseWtpIdTC, capwapBaseWtpProfileWtpMacAddress CapwapBaseWtpIdTC,
capwapBaseWtpProfileWtpModelNumber SnmpAdminString, capwapBaseWtpProfileWtpModelNumber SnmpAdminString,
capwapBaseWtpProfileWtpName LongUtf8String, capwapBaseWtpProfileWtpName LongUtf8String,
capwapBaseWtpProfileWtpLocation LongUtf8String, capwapBaseWtpProfileWtpLocation LongUtf8String,
skipping to change at page 24, line 45 skipping to change at page 25, line 17
capwapBaseWtpProfileWtpMacAddress OBJECT-TYPE capwapBaseWtpProfileWtpMacAddress OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the Base MAC address of a WTP. "Represents the Base MAC address of a WTP.
A WTP profile MUST contain the Base MAC address of the WTP A WTP profile MUST contain the Base MAC address of the WTP
because the CAPWAP message received from the WTP contains because the CAPWAP message received from the WTP contains
its Base MAC address and the AC uses the Base MAC address to its Base MAC address and the AC uses the Base MAC address to
find the corresponding WTP profile. find the corresponding WTP profile.
In the section 4.6.40 [RFC5415], it omits be included in the Section 4.6.40 of [RFC5415] omits indicating that the WTP's
WTP Board Data message element. It is a known errata item and Base MAC address must be included in the WTP Board Data
assumed to be fixed in future by the editors of the RFC5415." message element. This is a known errata item and should be
fixed in any future revision of the RFC 5415."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 3 } ::= { capwapBaseWtpProfileEntry 3 }
capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the model number of a WTP. "Represents the model number of a WTP.
A WTP profile MUST include the WTP's model number, which A WTP profile MUST include the WTP's model number, which
reflects the number of Physical Layer (PHY) radios on the WTP. reflects the number of Physical Layer (PHY) radios on the WTP.
In this way, the creation of a WTP profile triggers the AC In this way, the creation of a WTP profile triggers the AC
to automatically create the same number of WTP Virtual Radio to automatically create the same number of WTP Virtual Radio
Interfaces corresponding to the WTP's PHY radios without Interfaces corresponding to the WTP's PHY radios without
manual intervention. With the ifIndexes of WTP Virtual manual intervention. With the ifIndexes of WTP Virtual
Radio Interfaces, the operator could configure and manage Radio Interfaces, the operator could configure and manage
the WTP's PHY radios through the wireless binding MIB the WTP's PHY radios through the wireless binding MIB
modules." modules."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 4 } ::= { capwapBaseWtpProfileEntry 4 }
capwapBaseWtpProfileWtpName OBJECT-TYPE capwapBaseWtpProfileWtpName OBJECT-TYPE
SYNTAX LongUtf8String (SIZE(1..512)) SYNTAX LongUtf8String (SIZE(1..512))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name of the WTP." "Represents the name of the WTP."
REFERENCE REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.45 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 5 } ::= { capwapBaseWtpProfileEntry 5 }
capwapBaseWtpProfileWtpLocation OBJECT-TYPE capwapBaseWtpProfileWtpLocation OBJECT-TYPE
SYNTAX LongUtf8String (SIZE(1..1024)) SYNTAX LongUtf8String (SIZE(1..1024))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the location of the WTP." "Represents the location of the WTP."
REFERENCE REFERENCE
"Section 4.6.30. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.30 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 6 } ::= { capwapBaseWtpProfileEntry 6 }
capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the WTP SHOULD use a static IP address "Represents whether the WTP SHOULD use a static IP address
or not. A value of false disables the static IP address, or not. A value of false disables the static IP address,
while a value of true enables it." while a value of true enables it."
REFERENCE REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 7 } ::= { capwapBaseWtpProfileEntry 7 }
capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType {ipv4(1)} SYNTAX InetAddressType {ipv4(1)}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the static IP address type used by the WTP. "Represents the static IP address type used by the WTP.
Only ipv4(1) is supported by the object. Only ipv4(1) is supported by the object.
Although the CAPWAP protocol [RFC5415] supports both IPv4 Although the CAPWAP protocol [RFC5415] supports both IPv4
and IPv6, note that the CAPWAP field modelled by this and IPv6, note that the CAPWAP field modeled by this
object does not support IPv6, so the object does not object does not support IPv6, so the object does not
support ipv6(2)." support ipv6(2)."
REFERENCE REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 8 } ::= { capwapBaseWtpProfileEntry 8 }
capwapBaseWtpProfileWtpStaticIpAddress OBJECT-TYPE capwapBaseWtpProfileWtpStaticIpAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true, "When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the static IP address to be assigned to the WTP. it represents the static IP address to be assigned to the WTP.
The format of this IP address is determined by the The format of this IP address is determined by the
corresponding instance of object corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType." capwapBaseWtpProfileWtpStaticIpType."
REFERENCE REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 9 } ::= { capwapBaseWtpProfileEntry 9 }
capwapBaseWtpProfileWtpNetmask OBJECT-TYPE capwapBaseWtpProfileWtpNetmask OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true, "When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the netmask to be assigned to the WTP. it represents the netmask to be assigned to the WTP.
The format of this netmask is determined by the The format of this netmask is determined by the
corresponding instance of object corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType." capwapBaseWtpProfileWtpStaticIpType."
REFERENCE REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 10 } ::= { capwapBaseWtpProfileEntry 10 }
capwapBaseWtpProfileWtpGateway OBJECT-TYPE capwapBaseWtpProfileWtpGateway OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX InetAddress (SIZE(4))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapBaseWtpProfileWtpStaticIpEnable is true, "When capwapBaseWtpProfileWtpStaticIpEnable is true,
it represents the gateway to be assigned to the WTP. it represents the gateway to be assigned to the WTP.
The format of this IP address is determined by the The format of this IP address is determined by the
corresponding instance of object corresponding instance of object
capwapBaseWtpProfileWtpStaticIpType." capwapBaseWtpProfileWtpStaticIpType."
REFERENCE REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.48 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 11 } ::= { capwapBaseWtpProfileEntry 11 }
capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether to enable or disable automatic CAPWAP "Represents whether to enable or disable automatic CAPWAP
fallback in the event that a WTP detects its preferred AC, fallback in the event that a WTP detects its preferred AC
and is not currently connected to it. and is not currently connected to it.
The following enumerated values are supported: The following enumerated values are supported:
enabled(1) - The fallback mode is enabled enabled(1) - The fallback mode is enabled
disabled(2) - The fallback mode is disabled" disabled(2) - The fallback mode is disabled"
REFERENCE REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.42 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { enabled } DEFVAL { enabled }
::= { capwapBaseWtpProfileEntry 12 } ::= { capwapBaseWtpProfileEntry 12 }
capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-create MAX-ACCESS read-create
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 that the WTP has joined." Request messages to the AC that the WTP has joined."
REFERENCE REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." "Section 4.7.7 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 30 } DEFVAL { 30 }
::= { capwapBaseWtpProfileEntry 13 } ::= { capwapBaseWtpProfileEntry 13 }
capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the idle timeout value that the WTP SHOULD enforce "Represents the idle timeout value that the WTP SHOULD enforce
for its active stations." for its active stations."
REFERENCE REFERENCE
"Section 4.7.8. of CAPWAP Protocol Specification, RFC 5415." "Section 4.7.8 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 300 } DEFVAL { 300 }
::= { capwapBaseWtpProfileEntry 14 } ::= { capwapBaseWtpProfileEntry 14 }
capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32 (2..180) SYNTAX Unsigned32 (2..180)
UNITS "second" UNITS "second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time allowed between sending Discovery "Represents the maximum time allowed between sending Discovery
Request messages, in seconds." Request messages, in seconds."
REFERENCE REFERENCE
"Section 4.7.10. of CAPWAP Protocol Specification, RFC 5415." "Section 4.7.10 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 20 } DEFVAL { 20 }
::= { capwapBaseWtpProfileEntry 15 } ::= { capwapBaseWtpProfileEntry 15 }
capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the interval for WTP to send Decryption Error "Represents the interval for WTP to send the Decryption Error
report." report."
REFERENCE REFERENCE
"Section 4.7.11. of CAPWAP Protocol Specification, RFC 5415." "Section 4.7.11 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 } DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 16 } ::= { capwapBaseWtpProfileEntry 16 }
capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the interval the WTP uses between the WTP Events "Represents the interval the WTP uses between the WTP Event
Requests it transmits to the AC to communicate its statistics, Requests it transmits to the AC to communicate its statistics,
in seconds." in seconds."
REFERENCE REFERENCE
"Section 4.7.14. of CAPWAP Protocol Specification, RFC 5415." "Section 4.7.14 of CAPWAP Protocol Specification, RFC 5415."
DEFVAL { 120 } DEFVAL { 120 }
::= { capwapBaseWtpProfileEntry 17 } ::= { capwapBaseWtpProfileEntry 17 }
capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
limited(0), limited(0),
fullAndLimited(1) fullAndLimited(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
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 following enumerated values are supported: The following enumerated values are supported:
limited(0) - Limited ECN support limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support fullAndLimited(1) - Full and limited ECN support
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object follows object takes zero as starting value; this MIB object follows
this rule." that rule."
REFERENCE REFERENCE
"Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.25 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 18 } ::= { capwapBaseWtpProfileEntry 18 }
capwapBaseWtpProfileRowStatus OBJECT-TYPE capwapBaseWtpProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create, modify, and/or delete a row "This object is used to create, modify, and/or delete a row
in this table. in this table.
The value of capwapBaseWtpProfileName, The value of capwapBaseWtpProfileName,
capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation
can be changed when this object is in state ''active'' or in can be changed when this object is in state 'active' or in
''notInService''. 'notInService'.
The other objects in a row can be modified only when the value The other objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in 'active'. Thus, to modify one or more of the objects in
this conceptual row, this conceptual row:
a. change the row status to ''notInService'' a. change the row status to 'notInService'
b. change the values of the row b. change the values of the row
c. change the row status to ''active'' c. change the row status to 'active'
The capwapBaseWtpProfileRowStatus may be changed to ''active'' The capwapBaseWtpProfileRowStatus may be changed to 'active'
if the managed objects capwapBaseWtpProfileName, if the managed objects capwapBaseWtpProfileName,
capwapBaseWtpProfileWtpMacAddress, capwapBaseWtpProfileWtpMacAddress,
capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpName capwapBaseWtpProfileWtpModelNumber,
and capwapBaseWtpProfileWtpLocation in the conceptual row capwapBaseWtpProfileWtpName, and
capwapBaseWtpProfileWtpLocation in the conceptual row
have been assigned valid values. have been assigned valid values.
Deleting a WTP profile in use will disconnect the WTP to Deleting a WTP profile in use will disconnect the WTP from
the AC. So the network management system SHOULD the AC. So the network management system SHOULD
ask the operator to confirm such an operation. ask the operator to confirm such an operation.
When a WTP profile entry is removed from the table, When a WTP profile entry is removed from the table,
the corresponding WTP Virtual Radio Interfaces are also the corresponding WTP Virtual Radio Interfaces are also
removed from the CapwapBaseWirelessBindingTable and removed from the capwapBaseWirelessBindingTable and
ifTable [RFC2863]. ifTable [RFC2863].
Also, the related object instances SHOULD be removed from Also, the related object instances SHOULD be removed from
the wireless binding MIB modules such as IEEE 802.11 the wireless binding MIB modules such as the IEEE 802.11
MIB module [IEEE.802-11.2007]." MIB module [IEEE.802-11.2007]."
::= { capwapBaseWtpProfileEntry 19 } ::= { capwapBaseWtpProfileEntry 19 }
-- End of capwapBaseWtpProfileTable table -- 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 indicate the AC's CAPWAP FSM state "A table of objects that indicate the AC's CAPWAP FSM state
for each WTP, and helps the operator to query the WTPs' for each WTP, and helps the operator to query a WTP's
current configuration." current configuration."
::= { capwapBaseWtps 2 } ::= { 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 the AC's CAPWAP FSM state "A set of objects that displays the AC's CAPWAP FSM state
for each WTP. for each WTP.
Also, the operator could query the current configuration Also, the operator could query the current configuration
of a WTP by using the identifier of the corresponding of a WTP by using the identifier of the corresponding
WTP profile." WTP profile."
INDEX { capwapBaseWtpStateWtpId } INDEX { capwapBaseWtpStateWtpId }
::= { capwapBaseWtpStateTable 1 } ::= { capwapBaseWtpStateTable 1 }
CapwapBaseWtpStateEntry ::= SEQUENCE { CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpStateWtpIpAddressType InetAddressType, capwapBaseWtpStateWtpIpAddressType InetAddressType,
skipping to change at page 31, line 27 skipping to change at page 31, line 50
DESCRIPTION DESCRIPTION
"Represents the IP address type of a WTP. "Represents the IP address type of a WTP.
Only ipv4(1) and ipv6(2) are supported by the object." Only ipv4(1) and ipv6(2) are supported by the object."
::= { 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 which corresponds to "Represents the IP address of a WTP that corresponds to
IP address in the IP packet header. the IP address in the IP packet header.
The format of this IP address is determined by The format of this IP address is determined by
the corresponding instance of object the corresponding instance of object
capwapBaseWtpStateWtpIpAddressType." capwapBaseWtpStateWtpIpAddressType."
REFERENCE REFERENCE
"Section 4. of CAPWAP Protocol Specification, RFC 5415." "Section 4 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 3 } ::= { capwapBaseWtpStateEntry 3 }
capwapBaseWtpStateWtpLocalIpAddressType OBJECT-TYPE capwapBaseWtpStateWtpLocalIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the local IP address type of a WTP. "Represents the local IP address type of a WTP.
Only ipv4(1) and ipv6(2) are supported by the object." Only ipv4(1) and ipv6(2) are supported by the object."
::= { capwapBaseWtpStateEntry 4 } ::= { capwapBaseWtpStateEntry 4 }
capwapBaseWtpStateWtpLocalIpAddress OBJECT-TYPE capwapBaseWtpStateWtpLocalIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the local IP address of a WTP and which models "Represents the local IP address of a WTP and models the
the CAPWAP field [RFC5415] CAPWAP Local IPv4 Address CAPWAP Local IPv4 Address or CAPWAP Local IPv6 Address fields
or CAPWAP Local IPv6 Address. [RFC5415].
If a Network Address Translation (NAT) device is present If a Network Address Translation (NAT) device is present
between WTP and AC, the value of between WTP and AC, the value of
capwapBaseWtpStateWtpLocalIpAddress will be different to the capwapBaseWtpStateWtpLocalIpAddress will be different from the
vale of capwapBaseWtpStateWtpIpAddress. value of capwapBaseWtpStateWtpIpAddress.
The format of this IP address is determined by The format of this IP address is determined by
the corresponding instance of object the corresponding instance of object
capwapBaseWtpStateWtpLocalIpAddressType." capwapBaseWtpStateWtpLocalIpAddressType."
REFERENCE REFERENCE
"Section 4.6.11 and 4.6.12. of CAPWAP Protocol Specification, "Sections 4.6.11 and 4.6.12 of CAPWAP Protocol Specification,
RFC 5415." RFC 5415."
::= { capwapBaseWtpStateEntry 5 } ::= { capwapBaseWtpStateEntry 5 }
capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6|8)) SYNTAX PhysAddress (SIZE(6|8))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WTP's Base MAC Address, which MAY be "Represents the WTP's Base MAC Address, which MAY be
assigned to the primary Ethernet interface. assigned to the primary Ethernet interface.
The instance of the object corresponds to the Base MAC Address The instance of the object corresponds to the Base MAC Address
sub-element in the CAPWAP protocol [RFC5415]." sub-element in the CAPWAP protocol [RFC5415]."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 6 } ::= { capwapBaseWtpStateEntry 6 }
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),
reset(7), reset(7),
dtlsTeardown(8), dtlsTeardown(8),
unknown(9) unknown(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the various possible the AC's CAPWAP FSM state "Represents the various possibilities of the AC's CAPWAP FSM
for each WTP. state for each 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) - The WTP is joining with the AC join(2) - The WTP is joining with the AC
image(3) - The WTP is downloading software image(3) - The WTP is downloading software
configure(4) - The WTP is getting configuration from configure(4) - The WTP is getting configuration from
the AC the AC
dataCheck(5) - The AC is waiting for the Data Channel Keep dataCheck(5) - The AC is waiting for the Data Channel Keep
Alive Packet Alive Packet
run(6) - The WTP enters the running state run(6) - The WTP enters the running state
reset(7) - The AC transmits a reset request message reset(7) - The AC transmits a reset request message
to the WTP to the WTP
dtlsTeardown(8) - DTLS session is tear down dtlsTeardown(8) - DTLS session is torn down
unknown(9) - Operator already prepared configuration unknown(9) - Operator already prepared configuration
for the WTP, while the WTP has not contact for the WTP, while the WTP has not
with the AC till now" contacted the AC until now"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." "Section 2.3.1 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 7 } ::= { capwapBaseWtpStateEntry 7 }
capwapBaseWtpStateWtpUpTime OBJECT-TYPE capwapBaseWtpStateWtpUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the time (in hundredths of a second) since the "Represents the time (in hundredths of a second) since the
WTP has been in the running state (corresponding to the WTP has been in the running state (corresponding to the
value run(6) of capwapBaseWtpState)." value run(6) of capwapBaseWtpState)."
skipping to change at page 34, line 10 skipping to change at page 34, line 31
DESCRIPTION DESCRIPTION
"A table of objects that display properties of the WTPs "A table of objects that display properties of the WTPs
in running state." in running state."
::= { capwapBaseWtps 3 } ::= { capwapBaseWtps 3 }
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 properties of the WTPs "A set of objects that displays properties of the WTPs
in 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,
capwapBaseWtpBaseMacAddress PhysAddress, capwapBaseWtpBaseMacAddress PhysAddress,
capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC,
capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC,
skipping to change at page 34, line 42 skipping to change at page 35, line 16
"Represents the unique identifier of a WTP in running state." "Represents the unique identifier of a WTP 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 [RFC4133]. in the ENTITY-MIB module [RFC4133].
The information such as software version of a specific WTP Information about a specific WTP such as its software version
could be accessed through the index." could be accessed through this index."
::= { capwapBaseWtpEntry 2 } ::= { capwapBaseWtpEntry 2 }
capwapBaseWtpBaseMacAddress OBJECT-TYPE capwapBaseWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6|8)) SYNTAX PhysAddress (SIZE(6|8))
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.
The instance of the object corresponds to the Base MAC Address The instance of the object corresponds to the Base MAC Address
sub-element in the CAPWAP protocol [RFC5415]." sub-element in the CAPWAP protocol [RFC5415]."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.40 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 3 } ::= { 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 5415." "Section 4.6.43 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 4 } ::= { 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 5415." "Section 4.6.44 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 5 } ::= { 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 the 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
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object object takes zero as starting value; this MIB object
follows this rule." follows that rule."
REFERENCE REFERENCE
"Section 4.6.21. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.21 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 6 } ::= { capwapBaseWtpEntry 6 }
capwapBaseWtpRadiosInUseNum OBJECT-TYPE capwapBaseWtpRadiosInUseNum OBJECT-TYPE
SYNTAX Gauge32 (0..255) SYNTAX Gauge32 (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 5415." "Section 4.6.41 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 7 } ::= { 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 5415." "Section 4.6.41 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 8 } ::= { capwapBaseWtpEntry 8 }
capwapBaseWtpRetransmitCount OBJECT-TYPE capwapBaseWtpRetransmitCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "retransmissions" 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 5415." "Section 4.8.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEntry 9 } ::= { capwapBaseWtpEntry 9 }
-- 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 mappings between "A table of objects that display the mappings between
WTP Virtual Radio Interfaces and PHY radios, and the WTP Virtual Radio Interfaces and PHY radios, and the
wireless binding type for each PHY radio. wireless binding type for each PHY radio.
As CapwapBaseWirelessBindingTable stores the mappings between As capwapBaseWirelessBindingTable stores the mappings between
PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio
Interfaces, the operator can get the ifIndex information by Interfaces, the operator can get the ifIndex information by
querying this table. Such a query operation SHOULD run from querying this table. Such a query operation SHOULD run from
radio ID 1 to radio ID 31 according to [RFC5415], radio ID 1 to radio ID 31 according to [RFC5415],
and stop when a invalid ifIndex value (0) is returned. and stop when an invalid ifIndex value (0) is returned.
Values of all objects in this table are persistent at Values of all objects in this table are persistent at
restart/reboot." restart/reboot."
::= { capwapBaseWtps 4 } ::= { 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 between "A set of objects that displays the mapping between
a specific WTP Virtual Radio Interface and a PHY a specific WTP Virtual Radio Interface and a PHY
radio, and the wireless binding type for the PHY radio." radio, and the wireless binding type for the PHY radio."
INDEX { INDEX {
capwapBaseWtpProfileId, capwapBaseWtpProfileId,
capwapBaseWirelessBindingRadioId capwapBaseWirelessBindingRadioId
} }
::= { capwapBaseWirelessBindingTable 1 } ::= { capwapBaseWirelessBindingTable 1 }
CapwapBaseWirelessBindingEntry ::= SEQUENCE { CapwapBaseWirelessBindingEntry ::= SEQUENCE {
capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC,
skipping to change at page 37, line 45 skipping to change at page 38, line 21
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, which "Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP. is required to be unique on a WTP.
For example, WTP A and WTP B use a 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 5415." "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 the ifIndex. identified by the same value of the ifIndex.
Before WTPs contact the AC to get configuration, Before WTPs contact the AC to get configuration,
the operator configures WTP profiles for them. the operator configures WTP profiles for them.
The creation of a WTP profile triggers system to automatically The creation of a WTP profile triggers the system to
create a specific number of WTP Virtual Radio Interfaces and automatically create a specific number of WTP Virtual Radio
add a new row object in the capwapBaseWirelessBindingTable Interfaces and add a new row object in the
without manual intervention. capwapBaseWirelessBindingTable without manual intervention.
As most MIB modules use the ifIndex to identify an interface As most MIB modules use the ifIndex to identify an interface
for configuration and statistic data, for example, IEEE 802.11 for configuration and statistical data (for example, the IEEE
MIB module [IEEE.802-11.2007] 802.11 MIB module [IEEE.802-11.2007]), it will be easy to
It will be easy to reuse other wireless binding MIB modules reuse other wireless binding MIB modules through the WTP
through the WTP Virtual Radio Interface in the Centralized Virtual Radio Interface in the Centralized WLAN
WLAN Architecture." 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 the 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 5415." "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 that 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 5415." "Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 5 } ::= { 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 displays a station that is
associated with the specific radio on the WTP. associated with the specific radio on the WTP.
Note that in some cases such as roaming that a station may Note that in some cases such as roaming that a station may
simultaneously associate with two WTPs for some (short) time. simultaneously associate with two WTPs for some (short) time.
The MIB implementation MUST ensure there is only one valid The MIB implementation MUST ensure there is only one valid
and meaningful entry for a specific station." and meaningful entry for a specific station."
INDEX { capwapBaseStationId } INDEX { capwapBaseStationId }
::= { capwapBaseStationTable 1 } ::= { capwapBaseStationTable 1 }
CapwapBaseStationEntry ::= SEQUENCE { CapwapBaseStationEntry ::= SEQUENCE {
capwapBaseStationId CapwapBaseStationIdTC, capwapBaseStationId CapwapBaseStationIdTC,
skipping to change at page 39, line 36 skipping to change at page 40, line 12
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 5415." "Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 1 } ::= { capwapBaseStationEntry 1 }
capwapBaseStationWtpId OBJECT-TYPE capwapBaseStationWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP in running state." "Represents the unique identifier of a WTP in running state."
::= { capwapBaseStationEntry 2 } ::= { capwapBaseStationEntry 2 }
capwapBaseStationWtpRadioId OBJECT-TYPE capwapBaseStationWtpRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which "Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP. is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of For example, WTP A and WTP B use a same value of
capwapBaseStationWtpRadioId for their first radio." capwapBaseStationWtpRadioId for their first radio."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC 5415." "Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 3 } ::= { capwapBaseStationEntry 3 }
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 5415." "Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 4 } ::= { capwapBaseStationEntry 4 }
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 5415." "Section 4.6.8 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseStationEntry 5 } ::= { capwapBaseStationEntry 5 }
-- 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 the WTPs' events statistics." "A table of objects that display the WTPs' events statistics."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 6 } ::= { 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 displays the events statistics
of a WTP." of a WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 41, line 29 skipping to change at page 42, line 4
capwapBaseWtpEventsStatsLastFailureType INTEGER capwapBaseWtpEventsStatsLastFailureType INTEGER
} }
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. WTP crash.
Note that the CAPWAP field [RFC5415] modelled by this counter
Note that the CAPWAP field [RFC5415] modeled by this counter
takes the value 65535 to indicate that the information is not takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this available on the WTP. This MIB object does not follow this
behaviour which would not be standard in SMIv2. If the WTP behavior, which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate does not have the information, the agent will not instantiate
the object." the object."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 requires a reboot or an explicit CAPWAP configuration that requires a reboot or an explicit CAPWAP
protocol reset request. protocol reset request.
Note that the CAPWAP field [RFC5415] modelled by this counter Note that the CAPWAP field [RFC5415] modeled by this counter
takes the value 65535 to indicate that the information is not takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this available on the WTP. This MIB object does not follow this
behaviour which would not be standard in SMIv2. If the WTP behavior, which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate does not have the information, the agent will not instantiate
the object." the object."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 failures." connection with an AC has failed due to link failures."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 5415." "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 5415." "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 the AC initiated, link, software or hardware failures." than the AC-initiated, link, software or hardware failures."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 5415." "Section 4.6.47 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpEventsStatsEntry 7 } ::= { capwapBaseWtpEventsStatsEntry 7 }
capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unsupported(0), unsupported(0),
acInit(1), acInit(1),
linkFailure(2), linkFailure(2),
swFailure(3), swFailure(3),
hwFailure(4), hwFailure(4),
otherFailure(5), otherFailure(5),
skipping to change at page 43, line 43 skipping to change at page 44, line 19
"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:
unsupported(0) - Not supported unsupported(0) - Not supported
acInit(1) - The 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)
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object object takes zero as starting value; this MIB object
follows this rule." follows that rule."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." "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 the radios'
and reasons why the WTP radio has been reset. behaviors and reasons why the WTP radio has been reset.
To get all radios' event statistic on a specific WTP To get the events statistics of all radios on a specific WTP
(identified by the capwapBaseWtpCurrId), it needs a query (identified by the capwapBaseWtpCurrId), a query
operation SHOULD run from radio ID 1 to radio ID 31 till there operation SHOULD run from radio ID 1 to radio ID 31 until there
is no data returned. The radio ID here corresponds to the is no data returned. The radio ID here corresponds to the
object capwapBaseRadioEventsWtpRadioId. If the previous MIB object capwapBaseRadioEventsWtpRadioId. If the previous MIB
operations such as query on the CapwapBaseWirelessBindingTable operations such as query on the capwapBaseWirelessBindingTable
know the exact value of each radio ID, the query operation on know the exact value of each radio ID, the query operation on
the capwapBaseRadioEventsStatsTable could use that value the capwapBaseRadioEventsStatsTable could use that value
of Radio IDs." of Radio IDs."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtps 7 } ::= { 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 displays the statistical data of
events happened on a specific radio of a WTP." events that happened on a specific radio of a WTP."
INDEX { capwapBaseWtpCurrId, capwapBaseRadioEventsWtpRadioId } INDEX { capwapBaseWtpCurrId, capwapBaseRadioEventsWtpRadioId }
::= { capwapBaseRadioEventsStatsTable 1 } ::= { capwapBaseRadioEventsStatsTable 1 }
CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
capwapBaseRadioEventsWtpRadioId CapwapBaseRadioIdTC, capwapBaseRadioEventsWtpRadioId CapwapBaseRadioIdTC,
capwapBaseRadioEventsStatsResetCount Counter32, capwapBaseRadioEventsStatsResetCount Counter32,
capwapBaseRadioEventsStatsSwFailureCount Counter32, capwapBaseRadioEventsStatsSwFailureCount Counter32,
capwapBaseRadioEventsStatsHwFailureCount Counter32, capwapBaseRadioEventsStatsHwFailureCount Counter32,
capwapBaseRadioEventsStatsOtherFailureCount Counter32, capwapBaseRadioEventsStatsOtherFailureCount Counter32,
capwapBaseRadioEventsStatsUnknownFailureCount Counter32, capwapBaseRadioEventsStatsUnknownFailureCount Counter32,
skipping to change at page 45, line 10 skipping to change at page 45, line 34
capwapBaseRadioEventsStatsLastFailureType INTEGER capwapBaseRadioEventsStatsLastFailureType INTEGER
} }
capwapBaseRadioEventsWtpRadioId OBJECT-TYPE capwapBaseRadioEventsWtpRadioId 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, which "Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP. is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of For example, WTP A and WTP B use the same value of
capwapBaseRadioEventsWtpRadioId for their first radio." capwapBaseRadioEventsWtpRadioId for their first radio."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC 5415." "Section 4.3 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 1 } ::= { capwapBaseRadioEventsStatsEntry 1 }
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 the radio has been
reset." reset."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 2 } ::= { capwapBaseRadioEventsStatsEntry 2 }
capwapBaseRadioEventsStatsSwFailureCount OBJECT-TYPE capwapBaseRadioEventsStatsSwFailureCount 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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 3 } ::= { capwapBaseRadioEventsStatsEntry 3 }
capwapBaseRadioEventsStatsHwFailureCount OBJECT-TYPE capwapBaseRadioEventsStatsHwFailureCount 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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 4 } ::= { capwapBaseRadioEventsStatsEntry 4 }
capwapBaseRadioEventsStatsOtherFailureCount OBJECT-TYPE capwapBaseRadioEventsStatsOtherFailureCount 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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 5 } ::= { capwapBaseRadioEventsStatsEntry 5 }
capwapBaseRadioEventsStatsUnknownFailureCount OBJECT-TYPE capwapBaseRadioEventsStatsUnknownFailureCount 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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 6 } ::= { capwapBaseRadioEventsStatsEntry 6 }
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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 7 } ::= { capwapBaseRadioEventsStatsEntry 7 }
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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 8 } ::= { capwapBaseRadioEventsStatsEntry 8 }
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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 9 } ::= { capwapBaseRadioEventsStatsEntry 9 }
capwapBaseRadioEventsStatsCurrNoiseFloor OBJECT-TYPE capwapBaseRadioEventsStatsCurrNoiseFloor 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 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 10 } ::= { capwapBaseRadioEventsStatsEntry 10 }
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 have occurred "Represents the number of decryption errors that have occurred
on the WTP. Note that this field is only valid in cases where on the WTP. Note that this field is only valid in cases where
the WTP provides encryption/decryption services." the WTP provides encryption/decryption services."
skipping to change at page 47, line 29 skipping to change at page 48, line 4
::= { capwapBaseRadioEventsStatsEntry 10 } ::= { capwapBaseRadioEventsStatsEntry 10 }
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 have occurred "Represents the number of decryption errors that have occurred
on the WTP. Note that this field is only valid in cases where on the WTP. Note that this field is only valid in cases where
the WTP provides encryption/decryption services." the WTP provides encryption/decryption services."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 11 } ::= { capwapBaseRadioEventsStatsEntry 11 }
capwapBaseRadioEventsStatsLastFailureType OBJECT-TYPE capwapBaseRadioEventsStatsLastFailureType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unsupported(0), unsupported(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:
unsupported(0) - Not supported unsupported(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
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object follows object takes zero as starting value; this MIB object follows
this rule." that rule."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 12 } ::= { capwapBaseRadioEventsStatsEntry 12 }
-- 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of retransmissions 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 5415." "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 5415." "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 5415." "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, the 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 5415." "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 5415." "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
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 5415." "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 5415." "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, the 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 5415." "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, the AC will wait "Represents the maximum time, in seconds, the AC will wait
after the DTLS session has been established until it receives after the DTLS session has been established until it receives
the Join Request from the WTP. This timer MUST be greater the Join Request from the WTP. This timer MUST be greater
than 20 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 5415." "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: The following enumerated values are supported:
limited(0) - Limited ECN support limited(0) - Limited ECN support
fullAndLimited(1) - Full and limited ECN support fullAndLimited(1) - Full and limited ECN support
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object follows object takes zero as starting value; this MIB object follows
this rule." that rule."
REFERENCE REFERENCE
"Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." "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 }
capwapBaseFailedDTLSAuthFailureCount OBJECT-TYPE capwapBaseFailedDTLSAuthFailureCount 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 establishment "Represents the number of failed DTLS session establishment
attempts due to authentication failures." attempts due to authentication failures."
REFERENCE REFERENCE
"Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415." "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 5415." "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 the AC when a CAPWAP channel "This notification is sent by the AC when a CAPWAP channel
established. is established.
The notification is separated for data or control 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 the AC when CAPWAP channel "This notification is sent by the AC when a CAPWAP channel
becomes down. is down.
The notification is separated for data or control 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 has had a
decryption error since the last report." decryption error since the last report."
REFERENCE REFERENCE
"Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." "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 5415." "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
the firmware image." the firmware image."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." "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 receives message "This notification is generated when a WTP receives message
elements in the configuration management messages which it elements in the configuration management messages that it
is unable to apply locally." is unable to apply locally."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." "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." has changed."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.34 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifications 7 } ::= { capwapBaseNotifications 7 }
capwapBaseAuthenFailure NOTIFICATION-TYPE capwapBaseAuthenFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
capwapBaseNtfWtpId, capwapBaseNtfWtpId,
capwapBaseNtfChannelType, capwapBaseNtfChannelType,
capwapBaseNtfAuthenMethod, capwapBaseNtfAuthenMethod,
capwapBaseNtfAuthenFailureReason capwapBaseNtfAuthenFailureReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification notifies an authentication failure event, "This is notification of 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
-- Notification Objects -- Notification Objects
capwapBaseNotifyVarObjects OBJECT IDENTIFIER capwapBaseNotifyVarObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 5 } ::= { capwapBaseObjects 5 }
capwapBaseNtfWtpId OBJECT-TYPE capwapBaseNtfWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP." "Represents the unique identifier of a WTP."
skipping to change at page 54, line 51 skipping to change at page 55, line 26
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, which is "Represents the identifier of a PHY radio on a WTP, which is
only required to be unique on a WTP. only required to be unique on a WTP.
For example, WTP A and WTP B can use the 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 5415." "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 the 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 CAPWAP Channel." "Represents the authentication method for the 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 the channel is down.
The following enumerated values are supported: The following enumerated values are supported:
timeout(1) - The keep alive is timeout timeout(1) - The keepalive timed out
rekeyFailure(2) - Rekey process is failed, channel will be rekeyFailure(2) - Rekey process failed; channel will be
broken broken
acRebootWtp(3) - The AC reboot WTP acRebootWtp(3) - The AC rebooted the 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 LongUtf8String (SIZE (6..1024)) SYNTAX LongUtf8String (SIZE (6..1024))
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a list of station MAC addresses separated by "Represents a list of station MAC addresses separated by
semicolons." semicolons."
REFERENCE REFERENCE
"Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." "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),
invalidCert(2), invalidCert(2),
reassemblyFailure(3), reassemblyFailure(3),
decapFailure(4), decapFailure(4),
encapFailure(5), encapFailure(5),
timeout(6), 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 the 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 are not matched keyMismatch(1) - WTP's and AC's keys did not match
invalidCert(2) - Certification is not valid invalidCert(2) - Certification is not valid
reassemblyFailure(3) - Fragment reassembly failure reassemblyFailure(3) - Fragment reassembly failure
decapFailure(4) - Decapsulation error decapFailure(4) - Decapsulation error
encapFailure(5) - Encapsulation error encapFailure(5) - Encapsulation error
timeout(6) - WaitDTLS timer timeout timeout(6) - WaitDTLS timer timeout
unknown(8) - Unknown reason" unknown(8) - Unknown reason"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." "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) - The radio is operable operable(0) - The radio is operable
inoperable(1) - The radio is inoperable, and the inoperable(1) - The radio is inoperable, and the
capwapBaseNtfRadioStatusCause object capwapBaseNtfRadioStatusCause object
gives the reason in details gives the reason in detail
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object object takes zero as starting value; this MIB object
follows this rule." follows that rule."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." "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 why radio is out of service. "Represents the reason why the radio is out of service.
The following enumerated values are supported: The following enumerated values are supported:
normal(0) - Normal status normal(0) - Normal status
hwError(1) - Radio failure hwError(1) - Radio failure
swError(2) - Software failure swError(2) - Software failure
adminSet(3) - Administratively set adminSet(3) - Administratively set
Note that the CAPWAP field [RFC5415] modelled by this Note that the CAPWAP field [RFC5415] modeled by this
object takes zero as starting value, this MIB object object takes zero as starting value; this MIB object
follows this rule." follows that rule."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." "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),
unsupportedHw(6), unsupportedHw(6),
unsupportedBinding(7) unsupportedBinding(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
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
unsupportedHw(6) - WTP hardware not supported unsupportedHw(6) - WTP hardware not supported
unsupportedBinding(7) - Binding not supported" unsupportedBinding(7) - Binding not supported"
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." "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 5415." "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 5415." "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 5415." "Section 4.6.36 of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseNotifyVarObjects 13 } ::= { capwapBaseNotifyVarObjects 13 }
-- Notification Control -- Notification Control
capwapBaseNotifyControlObjects OBJECT IDENTIFIER capwapBaseNotifyControlObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 6 } ::= { capwapBaseObjects 6 }
capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the Channel Up/Channel Down notification "Represents whether the Channel Up / Channel Down notification
should be generated. should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 1 } ::= { capwapBaseNotifyControlObjects 1 }
capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the decryption error notification should "Represents whether the decryption error notification should
be generated. be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 2 } ::= { capwapBaseNotifyControlObjects 2 }
capwapBaseJoinFailureNotifyEnable OBJECT-TYPE capwapBaseJoinFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of WTP join failure should "Represents whether the notification of a WTP join failure
be generated. should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 3 } ::= { capwapBaseNotifyControlObjects 3 }
capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of WTP image upgrade "Represents whether the notification of a WTP image upgrade
failure should be generated. failure should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 4 } ::= { capwapBaseNotifyControlObjects 4 }
capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of configuration message "Represents whether the notification of configuration message
error should be generated. error should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 5 } ::= { capwapBaseNotifyControlObjects 5 }
capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of a radio's operational "Represents whether the notification of a radio's operational
state change should be generated. state change should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { false } DEFVAL { false }
::= { capwapBaseNotifyControlObjects 6 } ::= { capwapBaseNotifyControlObjects 6 }
capwapBaseAuthenFailureNotifyEnable OBJECT-TYPE capwapBaseAuthenFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the notification of authentication failure "Represents whether the notification of authentication failure
should be generated. should be generated.
A value of true(1) means that the notification is enabled A value of true(1) means that the notification is enabled.
A value of false(2) means that the notification is disabled A value of false(2) means that the notification is disabled.
The value of the object is persistent at restart/reboot." The value of the object is persistent at restart/reboot."
DEFVAL { true } DEFVAL { true }
::= { capwapBaseNotifyControlObjects 7 } ::= { capwapBaseNotifyControlObjects 7 }
-- 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 IF-MIB -- The interfaces MIB, RFC2863 MODULE IF-MIB -- The Interfaces MIB, RFC 2863
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifGeneralInformationGroup ifGeneralInformationGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
capwapBaseAcNodeGroup, capwapBaseAcNodeGroup,
capwapBaseWtpProfileGroup, capwapBaseWtpProfileGroup,
capwapBaseWtpStateGroup, capwapBaseWtpStateGroup,
capwapBaseWtpGroup, capwapBaseWtpGroup,
capwapBaseRadioGroup, capwapBaseRadioGroup,
capwapBaseStationGroup capwapBaseStationGroup
} }
skipping to change at page 63, line 6 skipping to change at page 63, line 28
capwapBaseAcNodeGroup OBJECT-GROUP capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpSessions, capwapBaseWtpSessions,
capwapBaseWtpSessionsLimit, capwapBaseWtpSessionsLimit,
capwapBaseStationSessions, capwapBaseStationSessions,
capwapBaseStationSessionsLimit capwapBaseStationSessionsLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the basic properties for the AC from the CAPWAP the basic properties of the AC from the CAPWAP
protocol perspective." protocol perspective."
::= { capwapBaseGroups 1 } ::= { capwapBaseGroups 1 }
capwapBaseAcNodeGroup2 OBJECT-GROUP capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseDataChannelDTLSPolicyOptions, capwapBaseDataChannelDTLSPolicyOptions,
capwapBaseControlChannelAuthenOptions capwapBaseControlChannelAuthenOptions
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the other properties such as security for the AC from the other properties (such as security) of the AC from
the 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
"A collection of objects which are used to configure "A collection of objects that is used to configure
the 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
"A collection of objects which are used to configure "A collection of objects that is used to configure
the stations ACL." the stations ACL."
::= { capwapBaseGroups 4 } ::= { capwapBaseGroups 4 }
capwapBaseWtpProfileGroup OBJECT-GROUP capwapBaseWtpProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpProfileName, capwapBaseWtpProfileName,
capwapBaseWtpProfileWtpMacAddress, capwapBaseWtpProfileWtpMacAddress,
capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpModelNumber,
capwapBaseWtpProfileWtpName, capwapBaseWtpProfileWtpName,
capwapBaseWtpProfileWtpLocation, capwapBaseWtpProfileWtpLocation,
capwapBaseWtpProfileRowStatus capwapBaseWtpProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to configure "A collection of objects that is used to configure
the WTP profile." the WTP profile."
::= { capwapBaseGroups 5 } ::= { capwapBaseGroups 5 }
capwapBaseWtpProfileGroup2 OBJECT-GROUP capwapBaseWtpProfileGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpProfileWtpStaticIpEnable, capwapBaseWtpProfileWtpStaticIpEnable,
capwapBaseWtpProfileWtpStaticIpType, capwapBaseWtpProfileWtpStaticIpType,
capwapBaseWtpProfileWtpStaticIpAddress, capwapBaseWtpProfileWtpStaticIpAddress,
capwapBaseWtpProfileWtpNetmask, capwapBaseWtpProfileWtpNetmask,
capwapBaseWtpProfileWtpGateway, capwapBaseWtpProfileWtpGateway,
capwapBaseWtpProfileWtpFallbackEnable, capwapBaseWtpProfileWtpFallbackEnable,
capwapBaseWtpProfileWtpEchoInterval, capwapBaseWtpProfileWtpEchoInterval,
capwapBaseWtpProfileWtpIdleTimeout, capwapBaseWtpProfileWtpIdleTimeout,
capwapBaseWtpProfileWtpMaxDiscoveryInterval, capwapBaseWtpProfileWtpMaxDiscoveryInterval,
capwapBaseWtpProfileWtpReportInterval, capwapBaseWtpProfileWtpReportInterval,
capwapBaseWtpProfileWtpStatisticsTimer, capwapBaseWtpProfileWtpStatisticsTimer,
capwapBaseWtpProfileWtpEcnSupport capwapBaseWtpProfileWtpEcnSupport
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects which are used to "A collection of optional objects that is used to
configure the WTP profile." configure the WTP profile."
::= { capwapBaseGroups 6 } ::= { capwapBaseGroups 6 }
capwapBaseWtpStateGroup OBJECT-GROUP capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpStateWtpIpAddressType, capwapBaseWtpStateWtpIpAddressType,
capwapBaseWtpStateWtpIpAddress, capwapBaseWtpStateWtpIpAddress,
capwapBaseWtpStateWtpLocalIpAddressType, capwapBaseWtpStateWtpLocalIpAddressType,
capwapBaseWtpStateWtpLocalIpAddress, capwapBaseWtpStateWtpLocalIpAddress,
capwapBaseWtpStateWtpBaseMacAddress, capwapBaseWtpStateWtpBaseMacAddress,
capwapBaseWtpState, capwapBaseWtpState,
capwapBaseWtpStateWtpUpTime, capwapBaseWtpStateWtpUpTime,
capwapBaseWtpStateWtpCurrWtpProfileId capwapBaseWtpStateWtpCurrWtpProfileId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the WTP's state information." the WTP's state information."
::= { capwapBaseGroups 7 } ::= { capwapBaseGroups 7 }
capwapBaseWtpGroup OBJECT-GROUP capwapBaseWtpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpBaseMacAddress, capwapBaseWtpBaseMacAddress,
capwapBaseWtpTunnelModeOptions, capwapBaseWtpTunnelModeOptions,
capwapBaseWtpMacTypeOptions, capwapBaseWtpMacTypeOptions,
capwapBaseWtpDiscoveryType, capwapBaseWtpDiscoveryType,
capwapBaseWtpRadiosInUseNum, capwapBaseWtpRadiosInUseNum,
capwapBaseWtpRadioNumLimit capwapBaseWtpRadioNumLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the properties information for the WTPs in running state." the properties information for the WTPs in running state."
::= { capwapBaseGroups 8 } ::= { capwapBaseGroups 8 }
capwapBaseWtpGroup2 OBJECT-GROUP capwapBaseWtpGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpPhyIndex, capwapBaseWtpPhyIndex,
capwapBaseWtpRetransmitCount capwapBaseWtpRetransmitCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects which are used to represent "A collection of optional objects that is used to represent
the properties information for the WTPs in running state." the properties of the WTPs in running state."
::= { capwapBaseGroups 9 } ::= { capwapBaseGroups 9 }
capwapBaseRadioGroup OBJECT-GROUP capwapBaseRadioGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWirelessBindingVirtualRadioIfIndex, capwapBaseWirelessBindingVirtualRadioIfIndex,
capwapBaseWirelessBindingType capwapBaseWirelessBindingType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the wireless binding type, the mappings between the the wireless binding type and the mappings between the
ifIndexes of WLAN Virtual Radio Interfaces and PHY radios." ifIndexes of WLAN Virtual Radio Interfaces and PHY radios."
::= { capwapBaseGroups 10 } ::= { capwapBaseGroups 10 }
capwapBaseStationGroup OBJECT-GROUP capwapBaseStationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseStationWtpId, capwapBaseStationWtpId,
capwapBaseStationWtpRadioId, capwapBaseStationWtpRadioId,
capwapBaseStationAddedTime, capwapBaseStationAddedTime,
capwapBaseStationVlanName capwapBaseStationVlanName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects that is used to represent
the stations' basic properties." the stations' basic properties."
::= { capwapBaseGroups 11 } ::= { capwapBaseGroups 11 }
capwapBaseWtpEventsStatsGroup OBJECT-GROUP capwapBaseWtpEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpEventsStatsRebootCount, capwapBaseWtpEventsStatsRebootCount,
capwapBaseWtpEventsStatsInitCount, capwapBaseWtpEventsStatsInitCount,
capwapBaseWtpEventsStatsLinkFailureCount, capwapBaseWtpEventsStatsLinkFailureCount,
capwapBaseWtpEventsStatsSwFailureCount, capwapBaseWtpEventsStatsSwFailureCount,
capwapBaseWtpEventsStatsHwFailureCount, capwapBaseWtpEventsStatsHwFailureCount,
capwapBaseWtpEventsStatsOtherFailureCount, capwapBaseWtpEventsStatsOtherFailureCount,
skipping to change at page 66, line 20 skipping to change at page 66, line 41
capwapBaseWtpEventsStatsInitCount, capwapBaseWtpEventsStatsInitCount,
capwapBaseWtpEventsStatsLinkFailureCount, capwapBaseWtpEventsStatsLinkFailureCount,
capwapBaseWtpEventsStatsSwFailureCount, capwapBaseWtpEventsStatsSwFailureCount,
capwapBaseWtpEventsStatsHwFailureCount, capwapBaseWtpEventsStatsHwFailureCount,
capwapBaseWtpEventsStatsOtherFailureCount, capwapBaseWtpEventsStatsOtherFailureCount,
capwapBaseWtpEventsStatsUnknownFailureCount, capwapBaseWtpEventsStatsUnknownFailureCount,
capwapBaseWtpEventsStatsLastFailureType capwapBaseWtpEventsStatsLastFailureType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used for collecting "A collection of objects that is 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 12 } ::= { capwapBaseGroups 12 }
capwapBaseRadioEventsStatsGroup OBJECT-GROUP capwapBaseRadioEventsStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseRadioEventsStatsResetCount, capwapBaseRadioEventsStatsResetCount,
capwapBaseRadioEventsStatsSwFailureCount, capwapBaseRadioEventsStatsSwFailureCount,
capwapBaseRadioEventsStatsHwFailureCount, capwapBaseRadioEventsStatsHwFailureCount,
capwapBaseRadioEventsStatsOtherFailureCount, capwapBaseRadioEventsStatsOtherFailureCount,
capwapBaseRadioEventsStatsUnknownFailureCount, capwapBaseRadioEventsStatsUnknownFailureCount,
capwapBaseRadioEventsStatsConfigUpdateCount, capwapBaseRadioEventsStatsConfigUpdateCount,
capwapBaseRadioEventsStatsChannelChangeCount, capwapBaseRadioEventsStatsChannelChangeCount,
capwapBaseRadioEventsStatsBandChangeCount, capwapBaseRadioEventsStatsBandChangeCount,
capwapBaseRadioEventsStatsCurrNoiseFloor, capwapBaseRadioEventsStatsCurrNoiseFloor,
capwapBaseRadioEventsStatsDecryptErrorCount, capwapBaseRadioEventsStatsDecryptErrorCount,
capwapBaseRadioEventsStatsLastFailureType capwapBaseRadioEventsStatsLastFailureType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used for collecting "A collection of objects that is 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 13 } ::= { capwapBaseGroups 13 }
capwapBaseParametersGroup OBJECT-GROUP capwapBaseParametersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseAcMaxRetransmit, capwapBaseAcMaxRetransmit,
capwapBaseAcChangeStatePendingTimer, capwapBaseAcChangeStatePendingTimer,
capwapBaseAcDataCheckTimer, capwapBaseAcDataCheckTimer,
capwapBaseAcDTLSSessionDeleteTimer, capwapBaseAcDTLSSessionDeleteTimer,
capwapBaseAcEchoInterval, capwapBaseAcEchoInterval,
capwapBaseAcRetransmitInterval, capwapBaseAcRetransmitInterval,
skipping to change at page 67, line 22 skipping to change at page 67, line 44
"Objects used for the CAPWAP protocol's parameters." "Objects used for the CAPWAP protocol's parameters."
::= { capwapBaseGroups 14 } ::= { capwapBaseGroups 14 }
capwapBaseStatsGroup OBJECT-GROUP capwapBaseStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseFailedDTLSAuthFailureCount, capwapBaseFailedDTLSAuthFailureCount,
capwapBaseFailedDTLSSessionCount capwapBaseFailedDTLSSessionCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for collecting the CAPWAP protocol's statistic." "Objects used for collecting the CAPWAP protocol's statistics."
::= { capwapBaseGroups 15 } ::= { capwapBaseGroups 15 }
capwapBaseNotificationsGroup NOTIFICATION-GROUP capwapBaseNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
capwapBaseChannelUp, capwapBaseChannelUp,
capwapBaseChannelDown, capwapBaseChannelDown,
capwapBaseDecryptErrorReport, capwapBaseDecryptErrorReport,
capwapBaseJoinFailure, capwapBaseJoinFailure,
capwapBaseImageUpgradeFailure, capwapBaseImageUpgradeFailure,
capwapBaseConfigMsgError, capwapBaseConfigMsgError,
skipping to change at page 68, line 41 skipping to change at page 69, line 14
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects MAY be considered sensitive or vulnerable in some network objects MAY be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. 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 capwapBaseWtProfileTable, and writable - Unauthorized changes to the capwapBaseWtProfileTable and writable
objects under capwapBaseAcs group MAY disrupt allocation of resources objects under capwapBaseAcs group MAY disrupt allocation of
in the network. For example, a WTP's static IP address could be resources in the network. For example, a WTP's static IP address
changed by set capwapBaseWtpProfileWtpStaticIpAddress object. could be changed by setting the
capwapBaseWtpProfileWtpStaticIpAddress 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 MAY disrupt allocation of resources in the network. For
example, a invalid value for capwapBaseWtpSessionsLimit object will example, an invalid value for the capwapBaseWtpSessionsLimit
increase the AC's traffic burden. object will increase the AC's traffic burden.
- Unauthorized changes to the capwapBaseMacAclTable, it MAY cause - Unauthorized changes to the capwapBaseMacAclTable MAY prevent
legal stations unable to access the network any more while illegal legal stations from being able to access the network, while
stations have chance to access the network. illegal stations are able to access it.
- Unauthorized changes to writable objects under the - Unauthorized changes to writable objects under the
capwapBaseParameters group, it MAY influence CAPWAP protocol capwapBaseParameters group MAY influence CAPWAP protocol behavior
behaviour and status. For example, an invalid value set for the and status. For example, an invalid value set for the
capwapBaseAcDataCheckTimer MAY influence the 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 expose the current security option for CAPWAP data and control
channels. channels.
- The capwapBaseWtpTable exposes a WTP's important information like - The capwapBaseWtpTable exposes a WTP's important information like
tunnel mode, MAC type and so on. tunnel mode, MAC type, and so on.
- The capwapBaseWtpEventsStatsTable exposes a WTP's failure - The capwapBaseWtpEventsStatsTable exposes a WTP's failure
information. information.
- The capwapBaseRadioEventsStatsTable exposes a 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, the 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.
11. IANA Considerations 11. IANA Considerations
11.1. IANA Considerations for CAPWAP-BASE-MIB Module 11.1. IANA Considerations for CAPWAP-BASE-MIB Module
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
The MIB module in this document uses the following IANA-assigned Descriptor OBJECT IDENTIFIER value
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: ---------- -----------------------
capwapBaseMIB { mib-2 196 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapBaseMIB { mib-2 XXX }
11.2. IANA Considerations for ifType 11.2. IANA Considerations for ifType
Require IANA to assign a ifType for the WTP Virtual Radio Interface. IANA has assigned the following ifType:
Decimal Name Description
------- ------------ -------------------------------
254 capwapWtpVirtualRadio WTP Virtual Radio Interface
12. Contributors 12. Contributors
This MIB module is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
13. Acknowledgements 13. Acknowledgements
Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, Bert Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, Bert
Wijnen and David L. Black for helpful comments on this document and Wijnen, and David L. Black for helpful comments on this document and
guiding some technique solution. guiding some technical solutions.
The authors also thank their friends and coworkers Fei Fang, Xuebin The authors also thank the following friends and coworkers: Fei Fang,
Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Hao Wang, Yujin Zhao, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Hao Wang, Yujin
Haitao Zhang, Xiansen Cai and Xiaolan Wan. Zhao, Haitao Zhang, Xiansen Cai, and Xiaolan Wan.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in RFCs to
RFCs to Indicate Requirement Levels", Indicate Requirement Levels", BCP 14, RFC 2119,
BCP 14, RFC 2119, March 1997. March 1997.
[RFC2287] Krupczak, C. and J. Saperia, [RFC2287] Krupczak, C. and J. Saperia, "Definitions of
"Definitions of System-Level Managed System-Level Managed Objects for Applications",
Objects for Applications", RFC 2287, RFC 2287, February 1998.
February 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Ed., and J. Schoenwaelder, Ed., Schoenwaelder, Ed., "Structure of Management
"Structure of Management Information Information Version 2 (SMIv2)", STD 58, RFC 2578,
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Ed., and J. Schoenwaelder, Ed., Schoenwaelder, Ed., "Textual Conventions for
"Textual Conventions for SMIv2", SMIv2", STD 58, RFC 2579, April 1999.
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Schoenwaelder, "Conformance Statements for
Statements for SMIv2", STD 58, SMIv2", STD 58, RFC 2580, April 1999.
RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
"The Interfaces Group MIB", RFC 2863, Group MIB", RFC 2863, June 2000.
June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Wijnen, "An Architecture for Architecture for Describing Simple Network
Describing Simple Network Management Management Protocol (SNMP) Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3418] Presuhn, R., "Management Information [RFC3418] Presuhn, R., "Management Information Base (MIB)
Base (MIB) for the Simple Network for the Simple Network Management Protocol
Management Protocol (SNMP)", STD 62, (SNMP)", STD 62, RFC 3418, December 2002.
RFC 3418, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
S., and J. Schoenwaelder, "Textual Schoenwaelder, "Textual Conventions for Internet
Conventions for Internet Network Network Addresses", RFC 4001, February 2005.
Addresses", RFC 4001, February 2005.
[RFC4133] Bierman, A. and K. McCloghrie, [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB
"Entity MIB (Version 3)", RFC 4133, (Version 3)", RFC 4133, August 2005.
August 2005.
[RFC5415] Calhoun, P., Montemurro, M., and D. [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley,
Stanley, "Control And Provisioning of "Control And Provisioning of Wireless Access
Wireless Access Points (CAPWAP) Points (CAPWAP) Protocol Specification",
Protocol Specification", RFC 5415, RFC 5415, March 2009.
March 2009.
14.2. Informative References 14.2. Informative References
[IEEE.802-11.2007] "Information technology - [Err1832] RFC Errata, "Errata ID 1832", for RFC 5415,
Telecommunications and information <http://www.rfc-editor.org>.
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.
[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, [IEEE.802-11.2007] "Information technology - Telecommunications and
"Architecture Taxonomy for Control information exchange between systems - Local and
and Provisioning of Wireless Access metropolitan area networks - Specific
Points (CAPWAP)", RFC 4118, requirements - Part 11: Wireless LAN Medium
June 2005. Access Control (MAC) and Physical Layer (PHY)
specifications", IEEE Standard 802.11, 2007, <htt
p://standards.ieee.org/getieee802/download/
802.11-2007.pdf>.
[RFC4347] Rescorla, E. and N. Modadugu, [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The
"Datagram Transport Layer Security", Addition of Explicit Congestion Notification
RFC 4347, April 2006. (ECN) to IP", RFC 3168, September 2001.
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Stanley, "Control and Provisioning of "Introduction and Applicability Statements for
Wireless Access Points (CAPWAP) Internet-Standard Management Framework",
Protocol Binding for IEEE 802.11", RFC 3410, December 2002.
RFC 5416, March 2009.
[I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., [RFC4118] Yang, L., Zerfos, P., and E. Sadot, "Architecture
and Y. Zhang, "CAPWAP Protocol Taxonomy for Control and Provisioning of Wireless
Binding MIB for IEEE 802.11", Access Points (CAPWAP)", RFC 4118, June 2005.
draft-ietf-capwap-802dot11-mib-06
(work in progress), January 2010.
RFC Editor - please remove the appendix before publication of the RFC [RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport
Layer Security", RFC 4347, April 2006.
Appendix A. Appendix A. Changes between -09 and -08 [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.
1) Closed the issues raised during the IESG review. [RFC5834] Shi, Y., Ed., Perkins, D., Ed., Elliott, C., Ed.,
and Y. Zhang, Ed., "Control and Provisioning of
Wireless Access Points (CAPWAP) Protocol Binding
MIB for IEEE 802.11", RFC 5834, May 2010.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd. Hangzhou H3C Tech. Co., Ltd.
Beijing R&D Center of H3C, Digital Technology Plaza, Beijing R&D Center of H3C, Digital Technology Plaza
NO.9 Shangdi 9th Street,Haidian District, NO. 9 Shangdi 9th Street, Haidian District
Beijing Beijing 100085
China(100085) China
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com EMail: rishyang@gmail.com
David Perkins (editor) David T. Perkins (editor)
SNMPinfo 228 Bayview Dr.
288 Quailbrook Ct San Carlos, San Carlos, CA 94070
CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com EMail: dperkins@dsperkins.com
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. 1516 Kent St.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park Durham, NC 27707
27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-308-1216
EMail: chelliot@gmail.com EMail: chelliot@pobox.com
Yong Zhang (editor) Yong Zhang (editor)
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
EMail: yzhang@fortinet.com EMail: yzhang@fortinet.com
 End of changes. 358 change blocks. 
675 lines changed or deleted 674 lines changed or added

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