draft-ietf-capwap-base-mib-06.txt   draft-ietf-capwap-base-mib-07.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd. Internet-Draft Hangzhou H3C Tech. Co., Ltd.
Intended status: Standards Track D. Perkins, Ed. Intended status: Informational D. Perkins, Ed.
Expires: February 14, 2010 SNMPinfo Expires: July 6, 2010 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
August 13, 2009 January 2, 2010
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-06 draft-ietf-capwap-base-mib-07
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it
describes the managed objects for modeling the Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 44
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 14, 2010. This Internet-Draft will expire on July 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This memo defines a portion of the Management Information Base (MIB) described in the BSD License.
for use with network management protocols. In particular, it
describes the managed objects for modeling the Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4
5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5
skipping to change at page 2, line 41 skipping to change at page 3, line 34
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. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14
9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14
9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17
9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17
9.3.1. Configuration Status Response Message . . . . . . . . 17 9.3.1. Configuration Status Response Message . . . . . . . . 17
9.3.2. Configuration Update Response Message . . . . . . . . 18 9.3.2. Configuration Update Response Message . . . . . . . . 18
10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 70 11. Security Considerations . . . . . . . . . . . . . . . . . . . 76
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77
12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 72 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 77
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 72 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 77
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 72 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 77
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 72 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 77
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 78
15.1. Normative References . . . . . . . . . . . . . . . . . . . 72 15.1. Normative References . . . . . . . . . . . . . . . . . . . 78
15.2. Informative References . . . . . . . . . . . . . . . . . . 73 15.2. Informative References . . . . . . . . . . . . . . . . . . 79
Appendix A. Appendix A. Changes between -06 and -05 . . . . . . . 74 Appendix A. Appendix A. Changes between -07 and -06 . . . . . . . 80
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
skipping to change at page 3, line 41 skipping to change at page 4, line 41
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 PHY to transmit and receive contains an RF antenna and wireless physical layer (PHY) to transmit
station traffic for wireless access networks. 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
skipping to change at page 4, line 29 skipping to change at page 5, line 29
frames. frames.
Wireless Binding: The CAPWAP protocol is independent of a specific Wireless Binding: The CAPWAP protocol is independent of a specific
WTP radio technology, as well its associated wireless link layer WTP radio technology, as well its associated wireless link layer
protocol. Elements of the CAPWAP protocol are designed to protocol. Elements of the CAPWAP protocol are designed to
accommodate the specific needs of each wireless technology in a accommodate the specific needs of each wireless technology in a
standard way. Implementation of the CAPWAP protocol for a particular standard way. Implementation of the CAPWAP protocol for a particular
wireless technology MUST 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 WLAN Architecture: It is the traditional autonomous WLAN Autonomous Wireless Local Area Network (WLAN) Architecture: It is the
architecture, in which each WTP is a single physical device that traditional autonomous WLAN architecture, in which each WTP is a
implements all the wireless services. single physical device that implements all the wireless services.
Centralized WLAN Architecture: It is an emerging hierarchical Centralized WLAN Architecture: It is an emerging hierarchical
architecture utilizing one or more centralized controllers for architecture utilizing one or more centralized controllers for
managing a large number of WTP devices. It can be said that the full managing a large number of WTP devices. It can be said that the full
wireless functions are implemented across multiple physical network wireless functions are implemented across multiple physical network
devices, namely, the WTPs and ACs. devices, namely, the WTPs and ACs.
4. Conventions 4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
5. Overview 5. Overview
5.1. Requirements and Constraints 5.1. Requirements and Constraints
The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to: The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to:
- 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;
- 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 state and configuration;
- Provide basic property information about the AC, WTP, radio and - Provide basic property information about the AC, WTP, radio and
station and their relationships; station and their relationships;
skipping to change at page 6, line 17 skipping to change at page 7, line 18
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 on
the WTP devices. It follows the same model as the CAPWAP protocol: the WTP devices. It follows the same model as the CAPWAP protocol:
Centralized Control; 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 handler 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
skipping to change at page 7, line 16 skipping to change at page 8, line 16
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 conception. 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 [I-D.ietf-capwap-802dot11-mib].
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 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.
The section 4.6.40 [RFC5415] does not clarify that the WTP's Base MAC In the section 4.6.40 [RFC5415], it omits indicating that the WTP's
address MUST be included in the WTP Board Data message element. This Base MAC address MUST be included in the WTP Board Data message
is a known errata item and assumed to be fixed in future by the element. It is a known errata item and assumed to be fixed in future
editors of the RFC5415. by the editors of the RFC5415.
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
skipping to change at page 9, line 32 skipping to change at page 10, line 32
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, ifAlias are to be used as per [RFC2863].
Also, as an ifIndex [RFC2863] is used as a common handler for a Also, as an ifIndex [RFC2863] is used as a common index for a
corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless
technologies MIB modules, the 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, which 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.
skipping to change at page 10, line 26 skipping to change at page 11, line 26
The wireless binding MIB module of a wireless technology (such as The wireless binding MIB module of a wireless technology (such as
[IEEE.802-11.2007]) is required to 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 SNMPv2-SMI [RFC2578], The following MIB module IMPORTS objects from SYSAPPL-MIB [RFC2287],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP- SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-
FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-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 Here takes IEEE 802.11 binding as an example to show 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:
skipping to change at page 11, line 15 skipping to change at page 12, line 15
In CapwapBaseWtpProfileTable In CapwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 123456', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', capwapBaseWtpProfileWtpMacAddr = '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),
capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', capwapBaseWtpProfileWtpStaticIp = '192.0.2.10',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.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,
capwapBaseWtpProfileWtpSilentInterval = 30, capwapBaseWtpProfileWtpSilentInterval = 30,
capwapBaseWtpProfileWtpStatisticsTimer = 120, capwapBaseWtpProfileWtpStatisticsTimer = 120,
capwapBaseWtpProfileWtpWaitDTLSTimer = 60, capwapBaseWtpProfileWtpWaitDTLSTimer = 60,
capwapBaseWtpProfileWtpEcnSupport = limited(0) capwapBaseWtpProfileWtpEcnSupport = limited(0)
} }
skipping to change at page 13, line 17 skipping to change at page 14, line 17
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) 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 use the message to update MIB objects on the
AC. For example, for IEEE 802.11 binding, the AC updates data in the AC. For example, for IEEE 802.11 binding, the AC updates data in the
ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the
skipping to change at page 18, line 23 skipping to change at page 19, line 23
10. Definitions 10. 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
InterfaceIndex LongUtf8String
FROM SYSAPPL-MIB
InterfaceIndex, ifGeneralInformationGroup
FROM IF-MIB FROM IF-MIB
PhysicalIndex PhysicalIndex
FROM ENTITY-MIB FROM ENTITY-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2,
Integer32, Unsigned32, Counter32 Integer32, Unsigned32, Counter32, 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 "200908130000Z" -- August 13th, 2009 LAST-UPDATED "201001020000Z" -- Jan 2th, 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,
skipping to change at page 19, line 19 skipping to change at page 20, line 22
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709 Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
Email: chelliot@cisco.com Email: chelliot@gmail.com
Yong Zhang Yong Zhang
Fortinet, Inc. Fortinet, Inc.
1090 Kifer Road 1090 Kifer Road
Sunnyvale, CA 94086 Sunnyvale, CA 94086
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2009 The Internet Society. This version of "Copyright (C) 2010 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the CAPWAP Protocol." the CAPWAP Protocol."
REVISION "200908130000Z" REVISION "201001020000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION 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 WTP is used."
SYNTAX OCTET STRING (SIZE (6)) 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 station is used."
SYNTAX OCTET STRING (SIZE (6)) 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
skipping to change at page 20, line 49 skipping to change at page 22, line 4
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
object takes zero as starting value, this MIB object
follows this 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 22, line 11 skipping to change at page 23, line 18
-- 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 Unsigned32 (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 which 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
skipping to change at page 22, line 34 skipping to change at page 23, line 41
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 Unsigned32 (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 which are accessing
the wireless service provided by the AC." the wireless service provided by the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 3 } ::= { capwapBaseAc 3 }
capwapBaseStationSessionsLimit OBJECT-TYPE capwapBaseStationSessionsLimit OBJECT-TYPE
skipping to change at page 23, line 24 skipping to change at page 24, line 32
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. 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 }
capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
clear(1), clear(1),
dtls(2) dtls(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the security policy configured on the AC for "Represents the security policy configured on the AC for
CAPWAP data channel. CAPWAP data channel.
The value of the object is persistent at restart/reboot. The value of the object is persistent at restart/reboot.
The following enumerated values are supported: The following enumerated values are supported:
other(0) - Other method, for example, vendor specific other(0) - Other method, for example, vendor specific
clear(1) - Clear text clear(1) - Clear text
dtls(2) - DTLS" dtls(2) - DTLS
Note that the CAPWAP field [RFC5415] modelled by this
object takes zero as starting value, this MIB object
follows this rule."
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 }
capwapBaseControlChannelAuthenOptions OBJECT-TYPE capwapBaseControlChannelAuthenOptions OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
x509(0), x509(0),
psk(1) psk(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type supported by the "Represents the authentication credential type supported by the
AC for 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
skipping to change at page 24, line 15 skipping to change at page 25, line 25
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 7 } ::= { capwapBaseAc 7 }
capwapBaseControlChannelAuthenConfig OBJECT-TYPE capwapBaseControlChannelAuthenConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
x509(1), x509(1),
psk(2) psk(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type configured on "Represents the authentication credential type configured on
the AC for CAPWAP control channel. the AC for CAPWAP control channel.
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:
x509(1) - X.509 certificate based x509(1) - X.509 certificate based
psk(2) - Pre-Shared secret" psk(2) - Pre-Shared secret"
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseAc 8 } ::= { capwapBaseAc 8 }
-- capwapBaseAcNameListTable table -- capwapBaseAcNameListTable table
capwapBaseAcNameListTable OBJECT-TYPE capwapBaseAcNameListTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that configure the AC name list. "A table of objects that configure the AC name list.
skipping to change at page 25, line 12 skipping to change at page 26, line 23
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 configure the AC name list."
INDEX { capwapBaseAcNameListId } INDEX { capwapBaseAcNameListId }
::= { capwapBaseAcNameListTable 1 } ::= { capwapBaseAcNameListTable 1 }
CapwapBaseAcNameListEntry ::= SEQUENCE { CapwapBaseAcNameListEntry ::= SEQUENCE {
capwapBaseAcNameListId Unsigned32, capwapBaseAcNameListId Unsigned32,
capwapBaseAcNameListName OCTET STRING, 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 a AC Name list."
::= { capwapBaseAcNameListEntry 1 } ::= { capwapBaseAcNameListEntry 1 }
capwapBaseAcNameListName OBJECT-TYPE capwapBaseAcNameListName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(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
skipping to change at page 26, line 5 skipping to change at page 27, line 16
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 variable 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
capwapBaseAcNameListPriority can be changed when this
object is in state ''active'' or in ''notInService''.
The capwapBaseAcNameListRowStatus may be changed to ''active''
if all the managed objects in the conceptual row with
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
skipping to change at page 27, line 21 skipping to change at page 28, line 38
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 variable 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
this object is in state ''active'' or in ''notInService''.
The capwapBaseMacAclRowStatus may be changed to ''active''
if all the managed objects in the conceptual row with
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
capwapBaseWtps OBJECT IDENTIFIER capwapBaseWtps OBJECT IDENTIFIER
::= { capwapBaseObjects 2 } ::= { capwapBaseObjects 2 }
-- capwapBaseWtpProfileTable Table -- capwapBaseWtpProfileTable Table
capwapBaseWtpProfileTable OBJECT-TYPE capwapBaseWtpProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 28, line 17 skipping to change at page 29, line 40
DESCRIPTION DESCRIPTION
"A set of objects that configure and display a WTP profile." "A set of objects that configure and display a WTP profile."
INDEX { capwapBaseWtpProfileId } INDEX { capwapBaseWtpProfileId }
::= { capwapBaseWtpProfileTable 1 } ::= { capwapBaseWtpProfileTable 1 }
CapwapBaseWtpProfileEntry ::= SEQUENCE { CapwapBaseWtpProfileEntry ::= SEQUENCE {
capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC,
capwapBaseWtpProfileName SnmpAdminString, capwapBaseWtpProfileName SnmpAdminString,
capwapBaseWtpProfileWtpMacAddr CapwapBaseWtpIdTC, capwapBaseWtpProfileWtpMacAddr CapwapBaseWtpIdTC,
capwapBaseWtpProfileWtpModelNumber SnmpAdminString, capwapBaseWtpProfileWtpModelNumber SnmpAdminString,
capwapBaseWtpProfileWtpName OCTET STRING, capwapBaseWtpProfileWtpName LongUtf8String,
capwapBaseWtpProfileWtpLocation OCTET STRING, capwapBaseWtpProfileWtpLocation LongUtf8String,
capwapBaseWtpProfileWtpStaticIpEnable TruthValue, capwapBaseWtpProfileWtpStaticIpEnable TruthValue,
capwapBaseWtpProfileWtpStaticIpType InetAddressType, capwapBaseWtpProfileWtpStaticIpType InetAddressType,
capwapBaseWtpProfileWtpStaticIp InetAddress, capwapBaseWtpProfileWtpStaticIp InetAddress,
capwapBaseWtpProfileWtpNetmask InetAddress, capwapBaseWtpProfileWtpNetmask InetAddress,
capwapBaseWtpProfileWtpGateway InetAddress, capwapBaseWtpProfileWtpGateway InetAddress,
capwapBaseWtpProfileWtpFallbackEnable INTEGER, capwapBaseWtpProfileWtpFallbackEnable INTEGER,
capwapBaseWtpProfileWtpEchoInterval Unsigned32, capwapBaseWtpProfileWtpEchoInterval Unsigned32,
capwapBaseWtpProfileWtpIdleTimeout Unsigned32, capwapBaseWtpProfileWtpIdleTimeout Unsigned32,
capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32, capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32,
capwapBaseWtpProfileWtpReportInterval Unsigned32, capwapBaseWtpProfileWtpReportInterval Unsigned32,
skipping to change at page 29, line 15 skipping to change at page 30, line 37
capwapBaseWtpProfileWtpMacAddr OBJECT-TYPE capwapBaseWtpProfileWtpMacAddr 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.
The section 4.6.40 [RFC5415] does not clarify that the WTP's In the section 4.6.40 [RFC5415], it omits be included in the
Base MAC address MUST be included in the WTP Board Data WTP Board Data message element. It is a known errata item and
message element. This is a known errata item and assumed to be assumed to be fixed in future by the editors of the RFC5415."
fixed in future by the editors of the RFC5415."
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 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 OCTET STRING(SIZE(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 OCTET STRING(SIZE(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
skipping to change at page 30, line 26 skipping to change at page 31, line 49
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 SYNTAX InetAddressType {ipv4(1), ipv4z(3)}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the static IP address type used by the WTP, IPv4 "Represents the static IP address type used by the WTP.
or IPv6." Only ipv4(1) and ipv4z(3) are supported by the object.
Although the CAPWAP protocol (RFC5415) supports both IPv4
and IPv6, note that the CAPWAP field modelled by this
object does not support IPv6, so the object does not
support ipv6(2) and ipv6z(4)."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 8 } ::= { capwapBaseWtpProfileEntry 8 }
capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress (SIZE(4|8))
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
corresponding instance of object
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 SYNTAX InetAddress (SIZE(4|8))
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
corresponding instance of object
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 SYNTAX InetAddress (SIZE(4|8))
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
corresponding instance of object
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
skipping to change at page 33, line 48 skipping to change at page 35, line 36
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
object takes zero as starting value, this MIB object follows
this rule."
REFERENCE REFERENCE
"Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 20 } ::= { capwapBaseWtpProfileEntry 20 }
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 variable 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,
capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation
can be changed when this object is in state ''active'' or in
''notInService''.
The other objects in a row can be modified only when the value
of this object in the corresponding conceptual row is not
''active''. Thus to modify one or more of the objects in
this conceptual row,
a. change the row status to ''notInService''
b. change the values of the row
c. change the row status to ''active''
The capwapBaseWtpProfileRowStatus may be changed to ''active''
if the managed objects capwapBaseWtpProfileName,
capwapBaseWtpProfileWtpMacAddr,
capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpName
and capwapBaseWtpProfileWtpLocation in the conceptual row
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 to
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 IEEE 802.11
MIB module [IEEE.802-11.2007]." MIB module [IEEE.802-11.2007]."
skipping to change at page 35, line 8 skipping to change at page 37, line 18
WTP profile." WTP profile."
INDEX { capwapBaseWtpStateWtpId } INDEX { capwapBaseWtpStateWtpId }
::= { capwapBaseWtpStateTable 1 } ::= { capwapBaseWtpStateTable 1 }
CapwapBaseWtpStateEntry ::= SEQUENCE { CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, capwapBaseWtpStateWtpId CapwapBaseWtpIdTC,
capwapBaseWtpStateWtpIpAddressType InetAddressType, capwapBaseWtpStateWtpIpAddressType InetAddressType,
capwapBaseWtpStateWtpIpAddress InetAddress, capwapBaseWtpStateWtpIpAddress InetAddress,
capwapBaseWtpStateWtpBaseMacAddress PhysAddress, capwapBaseWtpStateWtpBaseMacAddress PhysAddress,
capwapBaseWtpState INTEGER, capwapBaseWtpState INTEGER,
capwapBaseWtpStateWtpUpTime TimeTicks,
capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC
} }
capwapBaseWtpStateWtpId OBJECT-TYPE capwapBaseWtpStateWtpId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP." "Represents the unique identifier of a WTP."
::= { capwapBaseWtpStateEntry 1 } ::= { capwapBaseWtpStateEntry 1 }
capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the IP address type of a WTP." "Represents the IP address type of a WTP.
Only ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) and dns(16)
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." "Represents the IP address of a WTP.
The format of this IP address is determined by
the corresponding instance of object
capwapBaseWtpStateWtpIpAddressType."
::= { capwapBaseWtpStateEntry 3 } ::= { capwapBaseWtpStateEntry 3 }
capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress 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
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 4 } ::= { capwapBaseWtpStateEntry 4 }
capwapBaseWtpState OBJECT-TYPE capwapBaseWtpState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dtls(1), dtls(1),
join(2), join(2),
image(3), image(3),
configure(4), configure(4),
skipping to change at page 36, line 34 skipping to change at page 39, line 5
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 tear 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 contact
with the AC till now" with the AC till now"
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpStateEntry 5 } ::= { capwapBaseWtpStateEntry 5 }
capwapBaseWtpStateWtpUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the time (in hundredths of a second) since the
WTP has been in the running state (corresponding to the
value run(6) of capwapBaseWtpState)."
::= { capwapBaseWtpStateEntry 6 }
capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileIdTC SYNTAX CapwapBaseWtpProfileIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the current identifier of a WTP profile. "Represents the current identifier of a WTP profile.
The operator could query a WTP's current configuration The operator could query a WTP's current configuration
with the identifier of a WTP profile." with the identifier of a WTP profile."
::= { capwapBaseWtpStateEntry 6 } ::= { capwapBaseWtpStateEntry 7 }
-- End of capwapBaseWtpStateTable Table -- End of capwapBaseWtpStateTable Table
-- capwapBaseWtpTable Table -- capwapBaseWtpTable Table
capwapBaseWtpTable OBJECT-TYPE capwapBaseWtpTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpEntry SYNTAX SEQUENCE OF CapwapBaseWtpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 37, line 27 skipping to change at page 40, line 7
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,
capwapBaseWtpDiscoveryType INTEGER, capwapBaseWtpDiscoveryType INTEGER,
capwapBaseWtpRadiosInUseNum Unsigned32, capwapBaseWtpRadiosInUseNum Gauge32,
capwapBaseWtpRadioNumLimit Unsigned32, capwapBaseWtpRadioNumLimit Unsigned32,
capwapBaseWtpRetransmitCount Counter32, capwapBaseWtpRetransmitCount Counter32,
capwapBaseWtpMaxDiscoveries Unsigned32, capwapBaseWtpMaxDiscoveries Unsigned32,
capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32,
capwapBaseWtpMaxRetransmit Unsigned32, capwapBaseWtpMaxRetransmit Unsigned32,
capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, capwapBaseWtpDataChannelKeepAliveTimer Unsigned32,
capwapBaseWtpDataChannelDeadInterval Unsigned32, capwapBaseWtpDataChannelDeadInterval Unsigned32,
capwapBaseWtpDiscoveryInterval Unsigned32, capwapBaseWtpDiscoveryInterval Unsigned32,
capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, capwapBaseWtpDTLSSessionDeleteTimer Unsigned32,
capwapBaseWtpImageDataStartTimer Unsigned32, capwapBaseWtpImageDataStartTimer Unsigned32,
skipping to change at page 38, line 13 skipping to change at page 40, line 41
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 The information such as software version of a specific WTP
could be accessed through the index." could be accessed through the index."
::= { capwapBaseWtpEntry 2 } ::= { capwapBaseWtpEntry 2 }
capwapBaseWtpBaseMacAddress OBJECT-TYPE capwapBaseWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress 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
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
skipping to change at page 39, line 4 skipping to change at page 41, line 34
::= { 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
object takes zero as starting value, this MIB object
follows this 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 Unsigned32 (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)
skipping to change at page 42, line 36 skipping to change at page 45, line 20
-- 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
PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio
Interfaces, the operator can get the ifIndex information by
querying this table. Such a query operation SHOULD run from
radio ID 1 to radio ID 31 according to [RFC5415],
and stop when a invalid ifIndex value (0) is returned.
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 display the mapping between
skipping to change at page 44, line 38 skipping to change at page 47, line 28
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 display a station which is
associated with the specific radio on the WTP." associated with the specific radio on the WTP.
INDEX { Note that in some cases such as roaming that a station may
capwapBaseWtpCurrId, simultaneously associate with two WTPs for some (short) time.
capwapBaseWirelessBindingRadioId, The MIB implementation MUST ensure there is only one valid
capwapBaseStationId and meaningful entry for a specific station."
} INDEX { capwapBaseStationId }
::= { capwapBaseStationTable 1 } ::= { capwapBaseStationTable 1 }
CapwapBaseStationEntry ::= SEQUENCE { CapwapBaseStationEntry ::= SEQUENCE {
capwapBaseStationId CapwapBaseStationIdTC, capwapBaseStationId CapwapBaseStationIdTC,
capwapBaseStationAddedTime DateAndTime, capwapBaseStationWtpId CapwapBaseWtpIdTC,
capwapBaseStationVlanName SnmpAdminString capwapBaseStationWtpRadioId CapwapBaseRadioIdTC,
capwapBaseStationAddedTime DateAndTime,
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
SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP in running state."
::= { capwapBaseStationEntry 2 }
capwapBaseStationWtpRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of
capwapBaseStationWtpRadioId for their first radio."
REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 2 } ::= { 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 3 } ::= { 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 }
skipping to change at page 46, line 30 skipping to change at page 49, line 43
capwapBaseWtpEventsStatsUnknownFailureCount Counter32, capwapBaseWtpEventsStatsUnknownFailureCount Counter32,
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. A value of 65535 implies that this information is WTP crash.
not available on the WTP." Note that the CAPWAP field [RFC5415] modelled by this counter
takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this
behaviour which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate
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
skipping to change at page 46, line 44 skipping to change at page 50, line 15
::= { 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. A value of 65535 implies that this protocol reset request.
information is not available on the WTP." Note that the CAPWAP field [RFC5415] modelled by this counter
takes the value 65535 to indicate that the information is not
available on the WTP. This MIB object does not follow this
behaviour which would not be standard in SMIv2. If the WTP
does not have the information, the agent will not instantiate
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
skipping to change at page 48, line 34 skipping to change at page 52, line 9
DESCRIPTION DESCRIPTION
"Represents the failure type of the most recent WTP failure. "Represents the failure type of the most recent WTP failure.
The following enumerated values are supported: The following enumerated values are supported:
notSupport(0) - Not supported notSupport(0) - Not supported
acInit(1) - 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
object takes zero as starting value, this MIB object
follows this 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 radios behavior,
and reasons why the WTP radio has been reset." and reasons why the WTP radio has been reset.
To get all radios' event statistic on a specific WTP
(identified by the capwapBaseWtpCurrId), it needs a query
operation SHOULD run from radio ID 1 to radio ID 31 till there
is no data returned. The radio ID here corresponds to the
object capwapBaseRadioEventsWtpRadioId. If the previous MIB
operations such as query on the CapwapBaseWirelessBindingTable
know the exact value of each radio ID, the query operation on
the capwapBaseRadioEventsStatsTable could use that value
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 display the statistic data of
events happened on a specific radio of a WTP." events happened on a specific radio of a WTP."
INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId } INDEX { capwapBaseWtpCurrId, capwapBaseRadioEventsWtpRadioId }
::= { capwapBaseRadioEventsStatsTable 1 } ::= { capwapBaseRadioEventsStatsTable 1 }
CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { CapwapBaseRadioEventsStatsEntry ::= SEQUENCE {
capwapBaseRadioEventsWtpRadioId CapwapBaseRadioIdTC,
capwapBaseRadioEventsStatsResetCount Counter32, capwapBaseRadioEventsStatsResetCount Counter32,
capwapBaseRadioEventsStatsSwFailCount Counter32, capwapBaseRadioEventsStatsSwFailCount Counter32,
capwapBaseRadioEventsStatsHwFailCount Counter32, capwapBaseRadioEventsStatsHwFailCount Counter32,
capwapBaseRadioEventsStatsOtherFailCount Counter32, capwapBaseRadioEventsStatsOtherFailCount Counter32,
capwapBaseRadioEventsStatsUnknownFailCount Counter32, capwapBaseRadioEventsStatsUnknownFailCount Counter32,
capwapBaseRadioEventsStatsConfigUpdateCount Counter32, capwapBaseRadioEventsStatsConfigUpdateCount Counter32,
capwapBaseRadioEventsStatsChannelChangeCount Counter32, capwapBaseRadioEventsStatsChannelChangeCount Counter32,
capwapBaseRadioEventsStatsBandChangeCount Counter32, capwapBaseRadioEventsStatsBandChangeCount Counter32,
capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32,
capwapBaseRadioEventsStatsDecryptErrorCount Counter32, capwapBaseRadioEventsStatsDecryptErrorCount Counter32,
capwapBaseRadioEventsStatsLastFailType INTEGER capwapBaseRadioEventsStatsLastFailType INTEGER
} }
capwapBaseRadioEventsWtpRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, which
is required to be unique on a WTP.
For example, WTP A and WTP B use a same value of
capwapBaseRadioEventsWtpRadioId for their first radio."
REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC 5415."
::= { 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 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 1 } ::= { capwapBaseRadioEventsStatsEntry 2 }
capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due "Represents the number of times that the radio has failed due
to software related reasons." to software related reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 2 }
::= { capwapBaseRadioEventsStatsEntry 3 }
capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due "Represents the number of times that the radio has failed due
to hardware related reasons." to hardware related reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 3 } ::= { capwapBaseRadioEventsStatsEntry 4 }
capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed due to "Represents the number of times that the radio has failed due to
known reasons, other than software or hardware failure." known reasons, other than software or hardware failure."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 4 } ::= { capwapBaseRadioEventsStatsEntry 5 }
capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that the radio has failed for "Represents the number of times that the radio has failed for
unknown reasons." unknown reasons."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 5 } ::= { 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 6 } ::= { 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 7 } ::= { 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 8 } ::= { capwapBaseRadioEventsStatsEntry 9 }
capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "dBm" UNITS "dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the noise floor of the radio receiver in units of "Represents the noise floor of the radio receiver in units of
dBm." dBm."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseRadioEventsStatsEntry 9 } ::= { 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 10 } ::= { capwapBaseRadioEventsStatsEntry 11 }
capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupport(0), notSupport(0),
swFailure(1), swFailure(1),
hwFailure(2), hwFailure(2),
otherFailure(3), otherFailure(3),
unknown(255) unknown(255)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the failure type of the most recent radio failure. "Represents the failure type of the most recent radio failure.
The following enumerated values are supported: The following enumerated values are supported:
notSupport(0) - Not supported notSupport(0) - Not supported
swFailure(1) - Software failure swFailure(1) - Software failure
hwFailure(2) - Hardware failure hwFailure(2) - Hardware failure
otherFailure(3) - Other failure otherFailure(3) - Other failure
unknown(255) - Unknown" unknown(255) - Unknown
Note that the CAPWAP field [RFC5415] modelled by this
object takes zero as starting value, this MIB object follows
this rule."
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 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 }
skipping to change at page 55, line 34 skipping to change at page 59, line 39
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
object takes zero as starting value, this MIB object follows
this 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 }
skipping to change at page 58, line 37 skipping to change at page 62, line 45
capwapBaseNtfAuthenFailureReason capwapBaseNtfAuthenFailureReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification notifies an authentication failure event, "The notification notifies an authentication failure event,
and provides the reason for it." and provides the reason for it."
::= { capwapBaseNotifications 8 } ::= { capwapBaseNotifications 8 }
-- Objects used only in notifications -- Objects used only in notifications
-- 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."
::= { capwapBaseNotifyVarObjects 1 } ::= { capwapBaseNotifyVarObjects 1 }
skipping to change at page 60, line 8 skipping to change at page 64, line 16
acRebootWtp(3) - The AC reboot WTP acRebootWtp(3) - The AC reboot WTP
dtlsError(4) - DTLS notifications: DTLSAborted, dtlsError(4) - DTLS notifications: DTLSAborted,
DTLSReassemblyFailure, DTLSPeerDisconnect, DTLSReassemblyFailure, DTLSPeerDisconnect,
or frequent DTLSDecapFailure or frequent DTLSDecapFailure
maxRetransmit(5) - The underlying reliable transport's maxRetransmit(5) - The underlying reliable transport's
RetransmitCount counter has reached the RetransmitCount counter has reached the
MaxRetransmit variable" MaxRetransmit variable"
::= { capwapBaseNotifyVarObjects 5 } ::= { capwapBaseNotifyVarObjects 5 }
capwapBaseNtfStationIdList OBJECT-TYPE capwapBaseNtfStationIdList OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX 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 identifiers separated by "Represents a list of station identifiers 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
skipping to change at page 61, line 9 skipping to change at page 65, line 18
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 details
Note that the CAPWAP field [RFC5415] modelled by this
object takes zero as starting value, this MIB object
follows this 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 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
object takes zero as starting value, this MIB object
follows this 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),
skipping to change at page 62, line 50 skipping to change at page 67, line 17
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
capwapBaseNotifyControlObjects OBJECT IDENTIFIER
::= { capwapBaseObjects 6 }
capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the Channel Up/Channel Down notification
should be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 1 }
capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the decryption error notification should
be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 2 }
capwapBaseJoinFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of WTP join failure should
be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 3 }
capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of WTP image upgrade
failure should be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { true }
::= { capwapBaseNotifyControlObjects 4 }
capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of configuration message
error should be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 5 }
capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of a radio's operational
state change should be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { false }
::= { capwapBaseNotifyControlObjects 6 }
capwapBaseAuthenticationFailureNotifyEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents whether the notification of authentication failure
should be generated.
A value of true(1) means that the notification is enabled
A value of false(2) means that the notification is disabled"
DEFVAL { true }
::= { 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 -- this module MODULE IF-MIB -- The interfaces MIB, RFC2863
MANDATORY-GROUPS {
ifGeneralInformationGroup
}
MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
capwapBaseAcNodeGroup, capwapBaseAcNodeGroup,
capwapBaseWtpProfileGroup, capwapBaseWtpProfileGroup,
capwapBaseWtpStateGroup, capwapBaseWtpStateGroup,
capwapBaseWtpGroup, capwapBaseWtpGroup,
capwapBaseRadioGroup, capwapBaseRadioGroup,
capwapBaseStationGroup capwapBaseStationGroup
} }
GROUP capwapBaseAcNodeGroup2 GROUP capwapBaseAcNodeGroup2
skipping to change at page 64, line 36 skipping to change at page 70, line 47
GROUP capwapBaseNotificationsGroup GROUP capwapBaseNotificationsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseNotificationsGroup group is optional." "The capwapBaseNotificationsGroup group is optional."
GROUP capwapBaseNotifyVarsGroup GROUP capwapBaseNotifyVarsGroup
DESCRIPTION DESCRIPTION
"The capwapBaseNotifyVarsGroup group is optional. "The capwapBaseNotifyVarsGroup group is optional.
If capwapBaseNotificationsGroup is supported, If capwapBaseNotificationsGroup is supported,
this group must be implemented." this group must be implemented."
GROUP capwapBaseNotifyControlGroup
DESCRIPTION
"The capwapBaseNotifyControlGroup group is optional.
If capwapBaseNotificationsGroup is supported,
this group must be implemented."
::= { capwapBaseCompliances 1 } ::= { capwapBaseCompliances 1 }
capwapBaseAcNodeGroup OBJECT-GROUP capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpSessions, capwapBaseWtpSessions,
capwapBaseWtpSessionsLimit, capwapBaseWtpSessionsLimit,
capwapBaseStationSessions, capwapBaseStationSessions,
capwapBaseStationSessionsLimit capwapBaseStationSessionsLimit
} }
STATUS current STATUS current
skipping to change at page 66, line 37 skipping to change at page 73, line 6
"A collection of optional objects which are used to "A collection of optional objects which are 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,
capwapBaseWtpStateWtpBaseMacAddress, capwapBaseWtpStateWtpBaseMacAddress,
capwapBaseWtpState, capwapBaseWtpState,
capwapBaseWtpStateWtpUpTime,
capwapBaseWtpStateWtpCurrWtpProfileId capwapBaseWtpStateWtpCurrWtpProfileId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects which are 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 {
skipping to change at page 67, line 46 skipping to change at page 74, line 16
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects which are used to represent
the wireless binding type, the mappings between the the wireless binding type, 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,
capwapBaseStationWtpRadioId,
capwapBaseStationAddedTime, capwapBaseStationAddedTime,
capwapBaseStationVlanName capwapBaseStationVlanName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to represent "A collection of objects which are used to represent
the stations' basic properties." the stations' basic properties."
::= { capwapBaseGroups 11 } ::= { capwapBaseGroups 11 }
capwapBaseWtpEventsStatsGroup OBJECT-GROUP capwapBaseWtpEventsStatsGroup OBJECT-GROUP
skipping to change at page 70, line 15 skipping to change at page 76, line 35
capwapBaseNtfJoinFailureReason, capwapBaseNtfJoinFailureReason,
capwapBaseNtfImageFailureReason, capwapBaseNtfImageFailureReason,
capwapBaseNtfConfigMsgErrorType, capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements capwapBaseNtfMsgErrorElements
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for notifications." "Objects used for notifications."
::= { capwapBaseGroups 17 } ::= { capwapBaseGroups 17 }
END capwapBaseNotifyControlGroup OBJECT-GROUP
OBJECTS {
capwapBaseChannelUpDownNotifyEnable,
capwapBaseDecryptErrorNotifyEnable,
capwapBaseJoinFailureNotifyEnable,
capwapBaseImageUpgradeFailureNotifyEnable,
capwapBaseConfigMsgErrorNotifyEnable,
capwapBaseRadioOperableStatusNotifyEnable,
capwapBaseAuthenticationFailureNotifyEnable
}
STATUS current
DESCRIPTION
"Objects used to enable or disable notifications."
::= { capwapBaseGroups 18 }
END
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects MAY be considered sensitive or vulnerable in some network objects MAY be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. The followings are the tables and objects and network operations. The followings are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
skipping to change at page 72, line 24 skipping to change at page 78, line 49
12.2. IANA Considerations for ifType 12.2. IANA Considerations for ifType
Require IANA to assign a ifType for the WTP Virtual Radio Interface. Require IANA to assign a ifType for the WTP Virtual Radio Interface.
13. Contributors 13. Contributors
This MIB module is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
14. Acknowledgements 14. Acknowledgements
The authors wish to thank David Harrington, Abhijit Choudhury, Fei Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, Bert
Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Wijnen and David L. Black for helpful comments on this document and
Zhao, Haitao Zhang, Xiansen Cai. guiding some technique solution.
The authors also thank their friends and coworkers Fei Fang, Xuebin
Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Hao Wang, Yujin Zhao,
Haitao Zhang, Xiansen Cai and Xiaolan Wan.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in
RFCs to Indicate Requirement Levels", RFCs to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997. BCP 14, RFC 2119, March 1997.
[RFC2287] Krupczak, C. and J. Saperia,
"Definitions of System-Level Managed
Objects for Applications", RFC 2287,
February 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., [RFC2578] McCloghrie, K., Ed., Perkins, D.,
Ed., and J. Schoenwaelder, Ed., Ed., and J. Schoenwaelder, Ed.,
"Structure of Management Information "Structure of Management 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. Schoenwaelder, Ed., Ed., and J. Schoenwaelder, Ed.,
"Textual Conventions for SMIv2", "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
skipping to change at page 74, line 30 skipping to change at page 81, line 14
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP) Wireless Access Points (CAPWAP)
Protocol Binding for IEEE 802.11", Protocol Binding for IEEE 802.11",
RFC 5416, March 2009. RFC 5416, March 2009.
[I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C.,
and Y. Zhang, "CAPWAP Protocol and Y. Zhang, "CAPWAP Protocol
Binding MIB for IEEE 802.11", Binding MIB for IEEE 802.11",
draft-ietf-capwap-802dot11-mib-04 draft-ietf-capwap-802dot11-mib-06
(work in progress), May 2009. (work in progress), Jan 2010.
Appendix A. Appendix A. Changes between -06 and -05
All the issues are tracked by
http://www.capwap.org/cgi-bin/roundup.cgi/MIB/
1)Issue 70: For Base MIB, some bugs detected post-WGLC but pre-IESG
capwapBaseWtpProfileWTPSerialId should be RFC Editor - please remove the appendix before publication of the RFC
capwapBaseWtpProfileWtpSerialId (second WTP should be Wtp).
capwapBaseWtpProfileWTPModelNumber should be
capwapBaseWtpProfileWtpModelNumber (second WTP should be Wtp).
In the section 5.4, it should say "The SNMP agent MUST be run on the Appendix A. Appendix A. Changes between -07 and -06
AC devices" instead of CAPWAP-BASE-MIB.
The editor's address is updated. 1) Close IESG review issues raised by Bert Wijnen
2)Issue 72: The WTP id issue in the Base MIB --------------------------------------------------------------
Updated the section 5.7. WTP Profile and the description of Added some notification control objects such as
capwapBaseWtpProfileWtpMacAddr. It clarify that "The section 4.6.40 capwapBaseChannelUpDownNotifyEnable; Update the description to
[RFC5415] does not clarify that the WTP's Base MAC address MUST be explain the objects of RowStatus type; give the note in the object
included in the WTP Board Data message element. This is a known description to explain why the object such as
errata item and assumed to be fixed in future by the editors of the capwapBaseWtpProfileWtpEcnSupport starting value is zero; Added the
RFC5415." MODULE IF-MIB.
Also, updated the ID of WTP with Base MAC address instead of the 2) Close Gen-ART review issues raised by David L. Black
serial number.
3)Issue 73: For the example section in the Base and Dot11 MIB, the --------------------------------------------------------------
Dot11OperationTable is incorrect
In the draft version 05, the Dot11OperationTable follows the IEEE Close some editorial problems such as using "index" instead of
802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft "handler"; Changed some text to make it clear.
version 06 is updated according to IEEE 802.11-2007.
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
China(100085) China(100085)
skipping to change at page 75, line 48 skipping to change at page 82, line 20
Phone: +1 408 394-8702 Phone: +1 408 394-8702
EMail: dperkins@snmpinfo.com EMail: dperkins@snmpinfo.com
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park
27709 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
EMail: chelliot@cisco.com EMail: chelliot@gmail.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. 123 change blocks. 
198 lines changed or deleted 460 lines changed or added

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