draft-ietf-capwap-base-mib-00.txt   draft-ietf-capwap-base-mib-01.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: November 22, 2008 SNMPinfo Expires: April 14, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
P. Puneet, Ed. Y. Zhang, Ed.
Broadcom, Inc. Fortinet, Inc.
May 21, 2008 October 11, 2008
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-00 draft-ietf-capwap-base-mib-01
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 22, 2008. This Internet-Draft will expire on April 14, 2009.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol. of Wireless Access Points (CAPWAP) Protocol.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5
6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 6.1. The capwapBaseObjects Subtree . . . . . . . . . . . . . . 6
6.2. The capwapObjects Subtree . . . . . . . . . . . . . . . . 7 6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6
6.3. The capwapConformance Subtree . . . . . . . . . . . . . . 7 6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6
6.4. The capwapNotifications Subtree . . . . . . . . . . . . . 7 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6
6.5. Brief Description of MIB Objects . . . . . . . . . . . . . 7 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8
7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 10 7.4. Relationship to MIB standards of other SDOs . . . . . . . 9
7.4. Relationship to MIB standards of other SDOs . . . . . . . 10 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9
8. Example of CAPWAP-MIB Usage . . . . . . . . . . . . . . . . . 10 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. Security Considerations . . . . . . . . . . . . . . . . . . . 49
10. Security Considerations . . . . . . . . . . . . . . . . . . . 48 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 11.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 50
11.1. IANA Considerations for CAPWAP-MIB . . . . . . . . . . . . 49 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 50
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 49 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 49 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 14.1. Normative References . . . . . . . . . . . . . . . . . . . 50
14.1. Normative References . . . . . . . . . . . . . . . . . . . 49
14.2. Informative References . . . . . . . . . . . . . . . . . . 51 14.2. Informative References . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
Current work is under way in the IETF to specify the CAPWAP Protocol The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines
[I-D.ietf-capwap-protocol-specification], which enables an Access a standard, interoperable protocol, which enables an Access
Controller (AC) to manage a collection of Wireless Termination Points Controller (AC) to manage a collection of Wireless Termination
(WTPs) Points(WTPs)
This document defines a MIB module that can be used to manage CAPWAP This document defines a MIB module that can be used to manage CAPWAP
implementations. This MIB module covers both configuration and WTP implementations. This MIB module covers both configuration and WTP
status-monitoring aspects of CAPWAP, and provides a way to reuse status-monitoring aspects of CAPWAP, and provides a way to reuse
current MIB standards and future extensions for any wireless binding current MIB standards and future extensions for any wireless binding
technology. technology.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
skipping to change at page 3, line 41 skipping to change at page 3, line 41
[RFC2580]. [RFC2580].
3. Terminology 3. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the
CAPWAP Protocol specification [I-D.ietf-capwap-protocol- CAPWAP Protocol specification [I-D.ietf-capwap-protocol-
specification]. WTPs are viewed as remote RF interfaces controlled specification]. WTPs are viewed as remote RF interfaces controlled
by the AC via CAPWAP protocol. The CAPWAP protocol supports two by the AC via CAPWAP protocol. The CAPWAP protocol supports two
modes of operation: Split and Local MAC. In Split MAC mode all L2 modes of operation: Split and Local MAC. In Split MAC mode all L2
wireless data and management frames are encapsulated via the CAPWAP wireless data and management frames are encapsulated via the CAPWAP
protocol and exchanged between the AC and the WTP. The Local MAC protocol and exchanged between the AC and the WTPs. The Local MAC
mode of operation allows for the data frames to be either locally mode of operation allows for the data frames to be either locally
bridged, or tunneled as 802.3 frames. From AC, operator could bridged, or tunneled as 802.3 frames. From AC, operator could
centrally control WTPs configuration and monitor their status. centrally control WTPs configuration and monitor their status.
CAPWAP use DTLS protocol to implement control channel security. CAPWAP use DTLS protocol to implement control channel security.
4. Conventions 4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
5. Overview 5. Overview
The CAPWAP Protocol MIB module (CAPWAP-MIB) have the following design The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) have the following
objectives: design objectives:
- To work well under centralized architectures, and provide a way to - To implement an architecture that uses SNMP for the management and
centrally manage and control wireless network by SNMP control of wireless networks, answering the operators requirements
for centralized management, whatever the deployment or configuration
of the network devices (centralized, distributed, or some mix)
- To be consistent with CAPWAP protocol - To be consistent with CAPWAP protocol
- To reuse current MIB standards and future extensions for a wireless - To reuse current MIB standards and future extensions for a wireless
binding technology binding technology
- To enable interoperability between vendors - To enable interoperability between vendors
- To meet operator requirements for centralized architectures - To meet operator requirements for centralized architectures
The basic idea of CAPWAP-MIB is: The basic idea of CAPWAP-BASE-MIB is:
- The SNMP agent run on the AC side, and it MAY not be required on - The CAPWAP-BASE-MIB MUST be run on the AC devices and is NOT
the WTP side. It follows same idea as CAPWAP protocol: Centralized REQUIRED on the WTP devices. It follows same idea as CAPWAP
Control protocol: Centralized Control
- As a generic mechanism, it is independent of any wireless binding - As a generic mechanism, it is independent of any wireless binding
technologies and defined by a independent MIB file technologies and defined by an independent MIB file
- To be independent of any wireless binding technologies and have - To be independent of any wireless binding technologies and have
ability to reuse MIB standards of other SDOs, is the main challenge ability to reuse MIB standards of other SDOs, is the main challenge
for design of the MIB for design of the MIB
- The ifIndex [RFC2863] will play a role in bridging between MIB - ifIndex [RFC2863] will be used as common handler for corresponding
standards defined by different SDOs interfaces in the CAPWAP-BASE-MIB and specific wireless technologies
MIB modules
- The operator could manage and control the centralized wireless - The operator could manage and control the centralized wireless
architectures using multiple MIB standards defined by multiple SDOs, architectures using multiple MIB standards defined by multiple SDOs,
while keeping them loosely coupled while keeping them loosely coupled
It is designed to satisfy the following requirements and constraints: It is designed to satisfy the following requirements and constraints:
- From AC to centrally manage and monitor WTPs - From AC to centrally manage and monitor WTPs
- The MIB module supports CAPWAP protocol parameters queries - The MIB module supports CAPWAP protocol parameters queries
skipping to change at page 4, line 49 skipping to change at page 5, line 4
architectures using multiple MIB standards defined by multiple SDOs, architectures using multiple MIB standards defined by multiple SDOs,
while keeping them loosely coupled while keeping them loosely coupled
It is designed to satisfy the following requirements and constraints: It is designed to satisfy the following requirements and constraints:
- From AC to centrally manage and monitor WTPs - From AC to centrally manage and monitor WTPs
- The MIB module supports CAPWAP protocol parameters queries - The MIB module supports CAPWAP protocol parameters queries
- The MIB module supports showing WTPs current state - The MIB module supports showing WTPs current state
- The MIB module provides the information of AC, WTPs, radio and - The MIB module provides the information of AC, WTPs, radio and
station objects' basic property and their relationship station objects' basic property and their relationship
- The MIB module supports indicating the "WTP Virtual Radio
Interface" and PHY radio's mapping relationship - The MIB module supports indicating the 'WTP Virtual Radio
Interface' and PHY radio's mapping relationship
- The counters are provided for WTP, radio's reboot event, hardware - The counters are provided for WTP, radio's reboot event, hardware
event failure and so on event failure and so on
- The MIB module provides the various notification like channel up, - The MIB module provides the various notification like channel up,
join failure and so on join failure and so on
Before coming to details of CAPWAP-MIB module, it will introduce how Before coming to details of CAPWAP-BASE-MIB module, it will introduce
CAPWAP-MIB is able to be independent of any wireless binding how CAPWAP-BASE-MIB is able to be independent of any wireless binding
technologies and reuse MIB standards of other SDOs. As centralized technologies and reuse MIB standards of other SDOs. As centralized
Wireless architecture, the operator has to prepare configuration at Wireless architecture, the operator has to prepare configuration on
AC side before WTPs connects to AC. For any wireless binding the AC before WTPs connects to AC. For any wireless binding
technology, the configuration and management of radio is very technology, the configuration and management of radio is very
important. Under centralized Wireless architecture, according to important. Under centralized Wireless architecture, according to
[I-D.ietf-capwap-protocol-specification], a specific PHY radio could [I-D.ietf-capwap-protocol-specification], a specific PHY radio could
be identified by identifier of a WTP and radio (WTP id + radio id). be identified by identifier of a WTP and radio (WTP id + radio id).
As usual, the standard of a binding technology provides MIB standard As usual, the standard of a binding technology provides MIB standard
for radio management on its own. For example, according to IEEE for radio management on its own. For example, according to IEEE
802.11 WG MIB standards, the MIB tables such as Dot11OperationTable 802.11 WG MIB standards, the MIB tables such as Dot11OperationTable
are able to support WTP radio configuration. These tables use are able to support WTP radio configuration. These tables use
ifIndex as the index, and work well under standalone Wireless ifIndex as the index, and work well under standalone Wireless
architecture. architecture.
To reuse MIB objects (defined by SDOs such as IEEE) for radio is very To reuse MIB objects (defined by SDOs such as IEEE) for radio is very
import, and the key point is to reuse the idea of ifIndex. So it is important, and the key point is to reuse the idea of ifIndex. So it
required a way to maintain the mapping relationship between "WTP id + is required a way to maintain the mapping relationship between 'WTP
radio id" and "ifIndex". As a generic mechanism, ifIndex can id + radio id' and 'ifIndex'. As a generic mechanism, ifIndex can
identify an interface in abstract way, and it does NOT care for an identify an interface in abstract way, and it does NOT care for an
interface's PHY location (either on WTP or AC). AC can have interface's PHY location (either on the WTP or AC). AC can have
interfaces of "WTP Virtual Radio Interface" ifType, it will logically interfaces of 'WTP Virtual Radio Interface' ifType, which will
represents PHY radios on the WTPs side. It looks like that PHY logically represent PHY radios on the WTP. It looks like that PHY
radios are located on the AC side, and PHY location of WTP (radio) is radios are located on the AC, and PHY location of WTP (radio) is
hidden to the operator. Operator can operate radios by MIB tables hidden to the operator. Operator can operate radios by MIB tables
(such as IEEE 802.11 WG's) with ifIndex of "WTP Virtual Radio (such as IEEE 802.11 WG's) with ifIndex of 'WTP Virtual Radio
Interface". As an Abstract interface, "WTP Virtual Radio Interface" Interface'. As an Abstract interface, 'WTP Virtual Radio Interface'
could be used by any wireless binding technology such as IEEE 802.11 could be used by any wireless binding technology such as IEEE 802.11
and 802.16. The table of capwapRadioBindTable will indicate the and 802.16. The table of capwapRadioBindTable will indicate the
mapping relationship between "WTP id + Radio id" and IfIndex. mapping relationship between 'WTP id + Radio id' and IfIndex.
6. Structure of the MIB Module 6. Structure of the MIB Module
6.1. Textual Conventions 6.1. The capwapBaseObjects Subtree
The following textual conventions are defined:
CapwapWTPId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a unique identifier of a WTP instance.
As usual, a serial number of WTP will be used."
SYNTAX OCTET STRING(SIZE(128))
CapwapStationId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a unique identifier of a station instance.
As usual, the MAC address of station will be used."
SYNTAX OCTET STRING (SIZE (6))
CapwapRadioId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a unique identifier of a radio on a WTP."
SYNTAX Unsigned32 (1..4294967295)
CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the tunneling mode for station data that are
supported by the WTP.
The possible value could be:
localBridging(1) - Local Bridging Mode,
dot3Tunnel(2) - 802.3 Frame Tunnel Mode,
nativeTunnel(3) - Native Frame Tunnel Mode."
REFERENCE
"Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX INTEGER { localBridging(1), dot3Tunnel(2),
nativeTunnel(3) }
CapwapWTPMACType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the MAC mode of operation supported by the WTP.
The possible value could be:
localMAC(1) - Local-MAC Mode,
splitMAC(2) - Split-MAC Mode."
REFERENCE
"Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX INTEGER { localMAC(1), splitMAC(2) }
CapwapChannelType::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the channel type for CAPWAP protocol.
The following values are supported:
data(1) - data Channel
control(2) - control Channel."
SYNTAX INTEGER { data(1), control(2) }
CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the authentication credential type
for WTP.
The following values are supported:
clear(1) - clear text and no authentication,
x509(2) - X.509 Certificate Based,
psk(3) - Pre-Shared Secret,
other(8) - Other method, for example, vendor specific.
As mandatory requirement, CAPWAP control channel
authentication should use DTLS, and either by certificate or
PSK. For data channel, DTLS is optional."
SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) }
6.2. The capwapObjects Subtree
The subtree provides information for statistic data and configuration The subtree provides information for statistic data and configuration
parameters of WTP and radio. parameters of WTP and radio.
6.3. The capwapConformance Subtree 6.2. The capwapBaseConformance Subtree
The subtree provides conformance information of MIB objects. The subtree provides conformance information of MIB objects.
6.4. The capwapNotifications Subtree 6.3. The capwapBaseNotifications Subtree
The subtree describe the notifications defined in the MIB module, and The subtree describes the notifications defined in the MIB module,
their purpose. and their purpose.
6.5. Brief Description of MIB Objects 6.4. Brief Description of MIB Objects
The MIB objects were derived from the CAPWAP protocol document The MIB objects were derived from the CAPWAP protocol document
[I-D.ietf- capwap-protocol-specification]. [I-D.ietf- capwap-protocol-specification].
1) capwapWTPStateTable 1) capwapBaseWtpStateTable
The WTPs status table is used to indicate each WTP's CAPWAP FSM The WTPs status table is used to indicate each WTP's CAPWAP FSM
state. state.
2) capwapWTPTable 2) capwapBaseWtpTable
The WTPs table is used for providing property and configuration The WTPs table is used for providing property and configuration
information in details for WTPs in running state. information in details for WTPs in running state.
3) capwapRadioBindTable 3) capwapBaseRadioBindTable
The radio bind table is used to indicate the mapping relationship The radio bind table is used to indicate the mapping relationship
between logical interface of "WTP Virtual Radio Interface" ifType and between logical interface of 'WTP Virtual Radio Interface' ifType and
PHY radio. PHY radio.
4) capwapStationTable 4) capwapBaseStationTable
The station table is used for providing stations' basic property The station table is used for providing stations' basic property
information. information.
5) capwapWTPRebootStatsTable 5) capwapBaseWtpRebootStatsTable
The WTP reboot statistic table is used for collecting WTP reboot The WTP reboot statistic table is used for collecting WTP reboot
count, link failure count, hardware failure count and so on. count, link failure count, hardware failure count and so on.
6) capwapRadioStatsTable 6) capwapBaseRadioStatsTable
The WTP radio statistic table is used for collecting radio reset The WTP radio statistic table is used for collecting radio reset
count, channel change count, hardware failure count and so on. count, channel change count, hardware failure count and so on.
7. Relationship to Other MIB Modules 7. Relationship to Other MIB Modules
7.1. Relationship to the SNMPv2-MIB 7.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The CAPWAP-MIB does not entity and certain other system-wide data. The CAPWAP-BASE-MIB does
duplicate those objects. not duplicate those objects.
7.2. Relationship to the IF-MIB 7.2. Relationship to the IF-MIB
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing WTP radio object that extensions to the Interfaces Group for managing WTP radio object that
are modeled as interfaces. are modeled as interfaces.
IF-MIB is required to support on the AC side. For each PHY radio at IF-MIB is required to support on the AC. For each PHY radio on the
WTP side, it will have a logical interface of 'WTP Virtual Radio WTP, it will have a logical interface of 'WTP Virtual Radio
Interface' ifType at AC side. The ifIndex of interface will Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides
represent PHY radio by logical. The interface SHOULD be modeled as a way to configure radio's parameters and query radio's traffic
an ifEntry and provide appropriate interface information. statistics, and reuse the MIBs defined by a specific wireless binding
technology. The interface SHOULD be modeled as an ifEntry and
provide appropriate interface information.
Some specific interpretations of ifTable for CAPWAP-MIB are as Some specific interpretations of ifTable for CAPWAP-BASE-MIB are as
follow. follow.
Object Use for the CAPWAP MIB. Object Use for the CAPWAP-BASE-MIB.
ifIndex Each interface of 'WTP Virtual Radio Interface' type ifIndex Each interface of 'WTP Virtual Radio Interface'
maybe be represented by an ifEntry. ifType maybe be represented by an ifEntry.
ifDescr Description of the interface of 'WTP Virtual Radio ifDescr Description of the interface of 'WTP Virtual Radio
Interface' ifType. Interface' ifType.
ifType IANAifType of 'WTP Virtual Radio Interface'. ifType IANAifType of 'WTP Virtual Radio Interface'.
ifName Textual name (unique on this system) of the interface ifName Textual name (unique on this system) of the interface
or an octet string of zero length. or an octet string of zero length.
ifAlias The nonvolatile 'alias' name for the interface, as ifAlias The nonvolatile 'alias' name for the interface, as
specified by a network manager. specified by a network manager.
ifPhysAddress The physical address of the interface; i.e., ifPhysAddress The physical address of the interface, such as the
BSSID of a 802.11 radio. BSSID of a 802.11 radio.
ifAdminStatus This variable indicates the operator's intent as ifAdminStatus This variable indicates the operator's intent as
to whether PHY should be enabled, disabled, or to whether PHY should be enabled, disabled, or
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. interface.
Also see [RFC2863]. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational status ifOperStatus This value reflects the actual or operational status
of radio. of radio.
Also see [RFC2863]. Also see [RFC2863].
ifLastChange The value of sysUpTime at the time the interface ifLastChange The value of sysUpTime at the time the interface
entered its current operational state. entered its current operational state.
Also see [RFC2863]. Also see [RFC2863].
ifInOctets The number of received octets over the interface; ifInOctets The number of received octets over the interface;
i.e., the number of octets received as 802.11 frames. such as the number of octets received as 802.11
frames.
ifOutOctets The number of transmitted octets over the interface; ifOutOctets The number of transmitted octets over the interface;
i.e., the number of octets transmitted as 802.11 such as the number of octets transmitted as 802.11
frames. frames.
ifInErrors The number of frames dropped due to ifInErrors The number of inbound frames dropped due to
uncorrectable errors. uncorrectable errors.
ifInUnknownProtos ifInUnknownProtos
The number of received frame discarded during The number of received frame discarded during
frame header validation, including frames with frame header validation, including frames with
unrecognized label values. unrecognized label values.
ifOutErrors See [RFC2863]. ifOutErrors The number of outbound frames dropped due to
uncorrectable errors.
7.3. Relationship to the ENTITY-MIB 7.3. Relationship to the ENTITY-MIB
The ENTITY-MIB [RFC4133] meets need for a standardized way of The ENTITY-MIB [RFC4133] meets need for a standardized way of
representing a single agent, which supports multiple instances of one representing a single agent, which supports multiple instances of one
MIB. It could express a certain relationship between multiple MIB. It could express a certain relationship between multiple
entities, and provide entity properties for each entity. entities, and provide entity properties for each entity.
Under the wireless centralized architectures, the SNMP agent will run Under the wireless centralized architectures, the SNMP agent will run
on the AC side, and not required on the WTP side. By the ENTITY-MIB on the AC, and not required on the WTP. By the ENTITY-MIB on the AC,
on the AC side, it could keep entity information of AC and WTPs. it could keep entity information such as firmware revision and
From the ENTITY-MIB perspective, the overall physical entity (AC) is software revision of AC and WTPs. From the ENTITY-MIB perspective,
a "compound" of multiple physical entities (WTPs which connects to the overall physical entity (AC) is a 'compound' of multiple physical
AC), all entities are identified by Physical index. In the entities (WTPs which connects to AC), all entities are identified by
capwapWTPTable of CAPWAP-MIB, it uses capwapWTPPHYIndex object to Physical index. In the capwapBaseWtpTable of CAPWAP-BASE-MIB, it
keep the mapping relationship of WTP object between CAPWAP-MIB and uses capwapBaseWtpPhyIndex object to keep the mapping relationship of
WTP object between CAPWAP-BASE-MIB and ENTITY-MIB.
By combining the MIBs, operators could query AC and WTP's status and
properties. For example, they could get WTP's current status through
CAPWAP-BASE-MIB, and WTP's software revision information through
ENTITY-MIB. ENTITY-MIB.
7.4. Relationship to MIB standards of other SDOs 7.4. Relationship to MIB standards of other SDOs
The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is
required to support on the AC side. The CAPWAP-MIB module is able to required to support on the AC. The CAPWAP-BASE-MIB module is able to
support any wireless binding technology. Through ifIndex of 'WTP support any wireless binding technology. Through ifIndex of 'WTP
Virtual Radio Interface' ifType, it provides consistent and abstract Virtual Radio Interface' ifType, it provides consistent and abstract
way of reusing MIB objects of a wireless binding technology. way of reusing MIB objects of a wireless binding technology.
7.5. MIB modules required for IMPORTS 7.5. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET-
ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133].
8. Example of CAPWAP-MIB Usage 8. Example of CAPWAP-BASE-MIB Usage
With the idea of "WTP Virtual Radio Interface" in the mind, the With the idea of 'WTP Virtual Radio Interface' in the mind, the
usage of MIB will be easily understood. Here takes IEEE 802.11 usage of MIB will be easily understood. Here takes IEEE 802.11
binding technology as an example. binding technology as an example.
1) Identify each PHY radio by "WTP Virtual Radio Interface" 1) Identify each PHY radio by 'WTP Virtual Radio Interface'
According to [I-D.ietf-capwap-protocol-specification], each radio on According to [I-D.ietf-capwap-protocol-specification], each radio on
a WTP will be identified by a radio Id. Each WTP could be identified a WTP will be identified by a radio Id. Each WTP could be identified
by its serial number. by its serial number.
When configuration for a WTP is prepared before a WTP connects to AC, When configuration for a WTP is prepared before a WTP connects to AC,
the following information is available in the CapwapRadioBindTable. the following information is available in the
In CapwapRadioBindTable CapwapBaseRadioBindTable.
In CapwapBaseRadioBindTable
{ {
capwapWTPId = 12345678 capwapBaseWtpId = 12345678,
capwapRadioId = 1 capwapBaseRadioId = 1,
capwapWTPVirtualRadioifIndex = 10, capwapBaseWtpVirtualRadioifIndex = 10,
capwapWirelessBinding = dot11(2), capwapBaseRadioWirelessBinding = dot11(2)
} }
Suppse WTP's serial number is 12345678, and first radio id is 1.
At AC side, the ifIndex of interface in "WTP Virtual Radio Interface" Suppose WTP's serial number is 12345678, and first radio id is 1.
On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface'
ifType is 10 which represents the PHY radio 1. ifType is 10 which represents the PHY radio 1.
By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP
PHY radios are located at AC side. By the mechanism of 'WTP Virtual Radio Interface', it seems WTP
The interface of "WTP Virtual Radio Interface" ifType is modeled by PHY radios are located on the AC. The interface of 'WTP Virtual
ifTable. Radio Interface' ifType is modeled by ifTable.
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = "WTP Virtual Radio Interface", ifDescr = 'WTP Virtual Radio Interface',
ifType = IANAifType of "WTP Virtual ifType = IANAifType of 'WTP Virtual
Radio Interface", Radio Interface',
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = 0.0.0.0.0.0, ifPhysAddress = 0.0.0.0.0.0,
ifAdminStatus = true, ifAdminStatus = true,
ifOperStatus = false, ifOperStatus = false,
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
ifOutDiscards = 0, ifOutDiscards = 0,
ifOutErrors = 0, ifOutErrors = 0
} }
2) Configure specific wireless binding parameters for "WTP Virtual 2) Configure specific wireless binding parameters for 'WTP Virtual
Radio Interface" Radio Interface'
It will be done at the AC side through specific wireless binding MIB It will be done on the AC through specific wireless binding MIB
such as IEEE 802.11 MIB. such as IEEE 802.11 MIB.
For example, to configure parameter for "WTP Virtual Radio Interface" For example, to configure parameter for 'WTP Virtual Radio Interface'
by 802.11 Dot11OperationTable. by 802.11 Dot11OperationTable.
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = 0.0.0.0.0.0,
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
skipping to change at page 12, line 4 skipping to change at page 10, line 49
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = 0.0.0.0.0.0, dot11MACAddress = 0.0.0.0.0.0,
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = "capwap", dot11ManufacturerID = 'capwap',
dot11ProductID = "capwap" dot11ProductID = 'capwap'
} }
In the example, it suppose ifIndex of an interface in In the example, it suppose ifIndex of an interface in
"WTP Virtual Radio Interface" ifType is 10. 'WTP Virtual Radio Interface' ifType is 10.
3) Other configurations for a specific wireless binding 3) Other configurations for a specific wireless binding
For example, WLAN service configuration will be done through CAPWAP For example, WLAN service configuration will be done through CAPWAP
binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB
draft, it will give more explain. draft, it will give more explain.
4) WTP reports its current configuration status 4) WTP reports its current configuration status
After join phase and before WTP get configuration from AC, it will After join phase and before WTP get configuration from AC, it will
report its current configuration status to AC through configuration report its current configuration status to AC through configuration
status message. The data of MIB objects will be updated at AC side. status request message. The data of MIB objects will be updated on
For example, for 802.11 binding, WTP will update data in the the AC. For example, for 802.11 binding, WTP will update data in the
ifTable and IEEE 802.11 MIB so on according to message content. ifTable and IEEE 802.11 MIB so on according to message content.
As an example for ifIndex 10, its ifOperStatus in ifTable will be As an example for ifIndex 10, its ifOperStatus in ifTable will be
updated according to current radio operational status in the updated according to current radio operational status in the
CAPWAP message. CAPWAP message.
5) Query WTP and radio statistics data 5) Query WTP and radio statistics data
After WTPs come to run status, operator could query WTP and After WTPs come to run status, operator could query WTP and
radio statistics data through CAPWAP-MIB and specific binding MIB. radio statistics data through CAPWAP-BASE-MIB and specific binding
For example, through dot11CountersTable in the IEEE 802.11 MIB, MIB. For example, through dot11CountersTable in the IEEE 802.11 MIB,
operator could query counter data for radio which is identified operator could query counter data for radio which is identified
by ifIndex of a virtual radio interface. With capwapACState table by ifIndex of a virtual radio interface. With capwapBaseAcState table
in the MIB, operator could query configuration and properties of in the MIB, operator could query configuration and properties of
WTPs which are in run status. WTPs which are in run status.
6) Query other statistics data of a specific wireless binding 6) Query other statistics data of a specific wireless binding
For example, operator could query the statistics data of For example, operator could query the statistics data of
WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. WLAN service through 802.11 binding MIB and IEEE 802.11 MIB.
In the CAPWAP 802.11 binding MIB draft, it will give more explain. In the CAPWAP 802.11 binding MIB draft, it will give more explain.
7) Query other properties of WTP 7) Query other properties of WTP
Operator could query MIB objects in the ENTITY-MIB by Operator could query MIB objects in the ENTITY-MIB by
capwapWTPPHYIndex in the capwapWTPTable of CAPWAP-MIB. capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB.
The properties of WTP such as software version, hardware version The properties of WTP such as software version, hardware version
and so on are available in the ENTITY-MIB. and so on are available in the ENTITY-MIB.
9. Definitions 9. Definitions
CAPWAP-MIB DEFINITIONS ::= BEGIN CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
PhysAddress, TEXTUAL-CONVENTION, TruthValue, PhysAddress, TEXTUAL-CONVENTION, TruthValue,
DateAndTime DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndex InterfaceIndex
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
skipping to change at page 13, line 21 skipping to change at page 12, line 18
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
FROM SNMPv2-SMI FROM SNMPv2-SMI
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
capwapMIB MODULE-IDENTITY capwapBaseMIB MODULE-IDENTITY
LAST-UPDATED "200805210000Z" -- May 21th, 2008 LAST-UPDATED "200810110000Z" -- Oct 11th, 2008
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085) District,Beijing,China(100085)
skipping to change at page 13, line 48 skipping to change at page 12, line 45
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.comP Email: chelliot@cisco.com
Puneet Agarwal
BroadCom, Inc.
Yong Zhang
Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA USA
Email: pagarwal@broadcom.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2008 The Internet Society. This version of "Copyright (C) 2008 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the CAPWAP Protocol." the CAPWAP Protocol."
REVISION "200805210000Z" REVISION "200810110000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapWTPId ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "128a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique identifier of a WTP instance. "Represents an unique identifier of a WTP instance.
As usual, a serial number of WTP will be used." As usual, a serial number of WTP will be used."
SYNTAX OCTET STRING(SIZE(128)) SYNTAX OCTET STRING(SIZE(128))
CapwapStationId ::= TEXTUAL-CONVENTION CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique identifier of a station instance. "Represents an unique identifier of a station instance.
As usual, the MAC address of station will be used." As usual, the MAC address of station will be used."
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
CapwapRadioId ::= TEXTUAL-CONVENTION CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique identifier of a radio on a WTP." "Represents an unique identifier of a radio on a WTP."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..31)
CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the tunneling mode for station data that are "Represents the tunneling modes of operation that are
supported by the WTP. supported by the WTP.
The possible value could be: The WTP MAY support more than one option, represented by
the bit field below.
unused(0) - This bit is unused
localBridging(1) - Local Bridging Mode, localBridging(1) - Local Bridging Mode,
dot3Tunnel(2) - 802.3 Frame Tunnel Mode, dot3Tunnel(2) - 802.3 Frame Tunnel Mode,
nativeTunnel(3) - Native Frame Tunnel Mode." nativeTunnel(3) - Native Frame Tunnel Mode."
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX INTEGER { localBridging(1), dot3Tunnel(2), SYNTAX BITS { unused(0),
localBridging(1),
dot3Tunnel(2),
nativeTunnel(3) } nativeTunnel(3) }
CapwapWTPMACType ::= TEXTUAL-CONVENTION CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the MAC mode of operation supported by the WTP. "Represents the MAC mode of operation supported by the WTP.
The possible value could be: The following enumerated values are supported:
localMAC(1) - Local-MAC Mode, localMAC(0) - Local-MAC Mode,
splitMAC(2) - Split-MAC Mode." splitMAC(1) - Split-MAC Mode,
both(2) - Both Local-MAC and Split-MAC."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx."
SYNTAX INTEGER { localMAC(1), splitMAC(2) } SYNTAX INTEGER { localMAC(0), splitMAC(1), both(2) }
CapwapChannelType::= TEXTUAL-CONVENTION CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the channel type for CAPWAP protocol. "Represents the channel type for CAPWAP protocol.
The following values are supported: The following enumerated values are supported:
data(1) - data Channel data(1) - data Channel
control(2) - control Channel." control(2) - control Channel."
SYNTAX INTEGER { data(1), control(2) } SYNTAX INTEGER { data(1), control(2) }
CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type "Represents the authentication credential type
for WTP. for WTP.
The following values are supported: The following enumerated values are supported:
clear(1) - cleartext and no authentication, other(1) - Other method, for example, vendor specific.
x509(2) - X.509 Certificate Based, clear(2) - Clear text and no authentication,
psk(3) - Pre-Shared Secret, x509(3) - X.509 Certificate authentication,
other(8) - Other method, for example, vendor specific. psk(4) - Pre-Shared Secret authentication,
As mandatory requirement, CAPWAP control channel As mandatory requirement, CAPWAP control channel
authentication should use DTLS, and either by certificate or authentication should use DTLS, and either by certificate or
PSK. For data channel, DTLS is optional." PSK. For data channel, DTLS is optional."
SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) } SYNTAX INTEGER { other(1), clear(2), x509(3), psk(4) }
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications -- Notifications
capwapNotifications OBJECT IDENTIFIER
::= { capwapMIB 0 } capwapBaseNotifications OBJECT IDENTIFIER
::= { capwapBaseMIB 0 }
-- Tables, Scalars -- Tables, Scalars
capwapObjects OBJECT IDENTIFIER capwapBaseObjects OBJECT IDENTIFIER
::= { capwapMIB 1 } ::= { capwapBaseMIB 1 }
-- Conformance -- Conformance
capwapConformance OBJECT IDENTIFIER capwapBaseConformance OBJECT IDENTIFIER
::= { capwapMIB 2 } ::= { capwapBaseMIB 2 }
-- AC Objects Group -- AC Objects Group
capwapAC OBJECT IDENTIFIER capwapBaseAc OBJECT IDENTIFIER
::= { capwapObjects 1 } ::= { capwapBaseObjects 1 }
capwapWTPSessions OBJECT-TYPE capwapBaseWtpSessions OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of WTPs which are connecting to "Represents the total number of WTPs which are connecting to
AC." AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 1 } ::= { capwapBaseAc 1 }
capwapWTPSessionsLimit OBJECT-TYPE capwapBaseWtpSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of WTP sessions supported by "Represents the maximum number of WTP sessions supported by
the AC." the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 2 } ::= { capwapBaseAc 2 }
capwapStationSessions OBJECT-TYPE capwapBaseStationSessions OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of stations which are accessing "Represents the total number of stations which are accessing
the wireless service." the wireless service provided by the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 3 } ::= { capwapBaseAc 3 }
capwapStationSessionsLimit OBJECT-TYPE capwapBaseStationSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of station sessions supported by "Represents the maximum number of station sessions supported by
the AC." the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 4 } ::= { capwapBaseAc 4 }
capwapDataChannelSecOptions OBJECT-TYPE capwapBaseDataChannelSecOptions OBJECT-TYPE
SYNTAX Integer32 SYNTAX BITS { other(0), clear(1), dtls(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the security policy supported for CAPWAP data "Represents the security policy supported for CAPWAP data
channel. 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.
clear(1) - Clear Text, clear(1) - Clear Text,
dtls(2) - DTLS, dtls(2) - DTLS."
vendor(3) - vendor specific."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 5 } ::= { capwapBaseAc 5 }
capwapWTPAuthenOptions OBJECT-TYPE capwapBaseWtpAuthenOptions OBJECT-TYPE
SYNTAX Integer32 SYNTAX BITS { unused(0), x509(1), psk(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the authentication credential type supported by the "Represents the authentication credential type supported by the
AC for control channel. AC for control channel.
The AC MAY support more than one option, represented by the bit The AC MAY support more than one option, represented by the bit
field below. field below.
unused(0) - This bit is unused
x509(1) - X.509 Certificate Based x509(1) - X.509 Certificate Based
psk(2) - Pre-Shared Secret." psk(2) - Pre-Shared Secret."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 6 } ::= { capwapBaseAc 6 }
capwapWTPFallbackEnable OBJECT-TYPE capwapBaseWtpFallbackEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents enable or disable automatic CAPWAP fallback in the "Represents whether to enable or disable automatic CAPWAP
event that a WTP detects its preferred AC, and is not currently fallback in the event that a WTP detects its preferred AC, and
connected to it." is not currently connected to it."
REFERENCE REFERENCE
"Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 7 } ::= { capwapBaseAc 7 }
capwapWTPACNameList OBJECT-TYPE -- capwapBaseAcNameListTable table
SYNTAX OCTET STRING(SIZE(256))
MAX-ACCESS read-write capwapBaseAcNameListTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name list of ACs and use semicolon to separate "A table of objects that display AC name list."
AC name. The AC name could be configured with the order of ::= { capwapBaseAc 8 }
Primary AC, secondary AC and so on. WTP will try to connect to
AC name in the list one by one till it connected to one AC." capwapBaseAcNameListEntry OBJECT-TYPE
SYNTAX CapwapBaseAcNameListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display AC name list."
INDEX { capwapBaseAcNameListId }
::= { capwapBaseAcNameListTable 1 }
CapwapBaseAcNameListEntry ::= SEQUENCE {
capwapBaseAcNameListId Unsigned32,
capwapBaseAcNameListName OCTET STRING,
capwapBaseAcNameListPriority Unsigned32 }
capwapBaseAcNameListId OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents a unique id for a AC Name list."
::= { capwapBaseAcNameListEntry 1 }
capwapBaseAcNameListName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(512))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the name of an AC."
REFERENCE REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapAC 8 } ::= { capwapBaseAcNameListEntry 2 }
capwapBaseAcNameListPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the priority order of the preferred AC.
For instance, the value of one (1) is used to set the primary
AC, the value of two (2) is used to set the secondary, etc."
REFERENCE
"Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAcNameListEntry 3 }
-- End of AC Objects Group -- End of AC Objects Group
-- WTP Objects Group -- WTP Objects Group
capwapWTPs OBJECT IDENTIFIER capwapBaseWtps OBJECT IDENTIFIER
::= { capwapObjects 2 } ::= { capwapBaseObjects 2 }
-- capwapBaseWtpStateTable table
capwapWTPStateTable OBJECT-TYPE capwapBaseWtpStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapWTPStateEntry SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display WTPs in different "A table of objects that display WTP CAPWAP FSM state."
CAPWAP FSM state." ::= { capwapBaseWtps 1 }
::= { capwapWTPs 1 }
capwapWTPStateEntry OBJECT-TYPE capwapBaseWtpStateEntry OBJECT-TYPE
SYNTAX CapwapWTPStateEntry SYNTAX CapwapBaseWtpStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display WTPs in different "A set of objects that display WTP CAPWAP FSM state."
CAPWAP FSM state." INDEX { capwapBaseWtpId }
INDEX { capwapWTPId } ::= { capwapBaseWtpStateTable 1 }
::= { capwapWTPStateTable 1 }
CapwapWTPStateEntry ::= SEQUENCE { CapwapBaseWtpStateEntry ::= SEQUENCE {
capwapWTPId CapwapWTPId, capwapBaseWtpId CapwapBaseWtpIdTC,
capwapWTPIPAddressType InetAddressType, capwapBaseWtpIpAddressType InetAddressType,
capwapWTPIPAddress InetAddress, capwapBaseWtpIpAddress InetAddress,
capwapWTPPHYAddress PhysAddress, capwapBaseWtpPhyAddress PhysAddress,
capwapWTPState INTEGER } capwapBaseWtpState INTEGER }
capwapWTPId OBJECT-TYPE capwapBaseWtpId OBJECT-TYPE
SYNTAX CapwapWTPId SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS accessible-for-notify MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP." "Represents the unique identifier of a WTP."
::= { capwapWTPStateEntry 1 } ::= { capwapBaseWtpStateEntry 1 }
capwapWTPIPAddressType OBJECT-TYPE capwapBaseWtpIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the type of IP address of WTP." "Represents the type of IP address of a WTP."
::= { capwapWTPStateEntry 2 } ::= { capwapBaseWtpStateEntry 2 }
capwapWTPIPAddress OBJECT-TYPE capwapBaseWtpIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the IP address(IPv4 or IPv6) of a WTP." "Represents the IP address of a WTP."
::= { capwapWTPStateEntry 3 } ::= { capwapBaseWtpStateEntry 3 }
capwapWTPPHYAddress OBJECT-TYPE capwapBaseWtpPhyAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the PHY address of a WTP." "Represents the PHY address of a WTP."
::= { capwapWTPStateEntry 4 } ::= { capwapBaseWtpStateEntry 4 }
capwapWTPState OBJECT-TYPE capwapBaseWtpState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dtls(1), join(2), image(3), configure(4), dtls(1), join(2), image(3), configure(4),
run(5), clear(6), unknown(7) dataCheck(5), run(6), clear(7), unknown(8)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the various possible CAPWAP FSM states of WTP "Represents the various possible CAPWAP FSM states of WTP
The following values are supported: The following enumerated values are supported:
dtls(1) - DTLS negotiation process dtls(1) - DTLS negotiation states, which include
DTLS Setup, Authorize, DTLS Connect.
join(2) - WTP is joining with AC, join(2) - WTP is joining with AC,
image(3) - WTP is downloading software, image(3) - WTP is downloading software,
configure(4) - WTP is getting configuration from AC, configure(4) - WTP is getting configuration from AC,
run(5) - WTP comes to run state, dataCheck(5) - AC is waiting for the Data Channel Keep
clear(6) - WTP recoveries default configuration. Alive Packet.
run(6) - WTP comes to run state,
unknown(7) - Operator already prepare configuration clear(7) - WTP recoveries default configuration.
unknown(8) - Operator already prepare configuration
for WTP, while WTP has not contact with AC for WTP, while WTP has not contact with AC
till now." till now."
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPStateEntry 5 } ::= { capwapBaseWtpStateEntry 5 }
-- End of capwapBaseWtpStateTable Table
-- capwapBaseWtpTable Table
capwapWTPTable OBJECT-TYPE capwapBaseWtpTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapWTPEntry SYNTAX SEQUENCE OF CapwapBaseWtpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display and control WTPs in "A table of objects that display and control WTPs in
running state. Values of all read-write objects in this running state. Values of all read-write objects in this
table are persistent at restart/reboot." table are persistent at restart/reboot."
::= { capwapWTPs 2 } ::= { capwapBaseWtps 2 }
capwapWTPEntry OBJECT-TYPE capwapBaseWtpEntry OBJECT-TYPE
SYNTAX CapwapWTPEntry SYNTAX CapwapBaseWtpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display and control a WTP in "A set of objects that display and control a WTP in
running state." running state."
INDEX { capwapWTPCurrId } INDEX { capwapBaseWtpCurrId }
::= { capwapWTPTable 1 } ::= { capwapBaseWtpTable 1 }
CapwapWTPEntry ::= SEQUENCE { CapwapBaseWtpEntry ::= SEQUENCE {
capwapWTPCurrId CapwapWTPId, capwapBaseWtpCurrId CapwapBaseWtpIdTC,
capwapWTPPHYIndex PhysicalIndex, capwapBaseWtpPhyIndex PhysicalIndex,
capwapWTPName SnmpAdminString, capwapBaseWtpName SnmpAdminString,
capwapWTPLocation SnmpAdminString, capwapBaseWtpLocation SnmpAdminString,
capwapWTPBaseMACAddress PhysAddress, capwapBaseWtpBaseMacAddress PhysAddress,
capwapWTPTunnelModeOptions CapwapWTPTunnelMode, capwapBaseTunnelModeOptions CapwapBaseTunnelModeTC,
capwapWTPMACTypeOptions CapwapWTPMACType, capwapBaseMacTypeOptions CapwapBaseMacTypeTC,
capwapWTPDiscoveryType INTEGER, capwapBaseWtpDiscoveryType INTEGER,
capwapWTPRadiosInUseNum Unsigned32, capwapBaseWtpRadiosInUseNum Unsigned32,
capwapWTPRadioNumLimit Unsigned32, capwapBaseWtpRadioNumLimit Unsigned32,
capwapWTPStaticIPEnable TruthValue, capwapBaseWtpStaticIpEnable TruthValue,
capwapWTPStaticIPType InetAddressType, capwapBaseWtpStaticIpType InetAddressType,
capwapWTPStaticIP InetAddress, capwapBaseWtpStaticIp InetAddress,
capwapWTPNetmask InetAddress, capwapBaseWtpNetmask InetAddress,
capwapWTPGateway InetAddress } capwapBaseWtpGateway InetAddress,
capwapBaseWtpRetransmitCount Unsigned32 }
capwapWTPCurrId OBJECT-TYPE capwapBaseWtpCurrId OBJECT-TYPE
SYNTAX CapwapWTPId SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP Which is "Represents the unique identifier of a WTP Which is
in running state." in running state."
::= { capwapWTPEntry 1 } ::= { capwapBaseWtpEntry 1 }
capwapWTPPHYIndex OBJECT-TYPE capwapBaseWtpPhyIndex OBJECT-TYPE
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique physical index of a physical entity "Represents the unique physical index of a physical entity
in the ENTITY-MIB. The information such as software version in the ENTITY-MIB. The information such as software version
of specific WTP could be accessed through the index." of specific WTP could be accessed through the index."
::= { capwapWTPEntry 2 } ::= { capwapBaseWtpEntry 2 }
capwapWTPName OBJECT-TYPE capwapBaseWtpName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name of a WTP." "Represents the name of a WTP."
REFERENCE REFERENCE
"Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 3 } ::= { capwapBaseWtpEntry 3 }
capwapWTPLocation OBJECT-TYPE capwapBaseWtpLocation OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the location of a WTP." "Represents the location of a WTP."
REFERENCE REFERENCE
"Section 4.6.31. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.29. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 4 } ::= { capwapBaseWtpEntry 4 }
capwapWTPBaseMACAddress OBJECT-TYPE capwapBaseWtpBaseMacAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the WTP's Base MAC Address, which MAY be assigned "Represents the WTP's Base MAC Address, which MAY be assigned
to the primary Ethernet interface." to the primary Ethernet interface."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 5 } ::= { capwapBaseWtpEntry 5 }
capwapWTPTunnelModeOptions OBJECT-TYPE capwapBaseTunnelModeOptions OBJECT-TYPE
SYNTAX CapwapWTPTunnelMode SYNTAX CapwapBaseTunnelModeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the tunneling modes for station data that are "Represents the tunneling modes of operation supported by
supported by the WTP. the WTP.
The WTP MAY support more than one option, represented by the The WTP MAY support more than one option, represented by the
bit field below. bit field below.
localBridging(1) - Local Bridging Mode, localBridging(1) - Local Bridging Mode,
dot3Tunnel(2) - 802.3 Frame Tunnel Mode, dot3Tunnel(2) - 802.3 Frame Tunnel Mode,
nativeTunnel(3) - Native Frame Tunnel Mode." nativeTunnel(3) - Native Frame Tunnel Mode."
REFERENCE REFERENCE
"Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 6 } ::= { capwapBaseWtpEntry 6 }
capwapWTPMACTypeOptions OBJECT-TYPE capwapBaseMacTypeOptions OBJECT-TYPE
SYNTAX CapwapWTPMACType SYNTAX CapwapBaseMacTypeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the MAC mode of operation supported by the WTP. "Represents the MAC mode of operation supported by the WTP.
The WTP MAY support more than one option, represented by the The following enumerated values are supported:
bit field below. localMAC(0) - Local-MAC Mode,
localMAC(1) - Local-MAC Mode, splitMAC(1) - Split-MAC Mode,
splitMAC(2) - Split-MAC Mode." both(2) - Both Local-MAC Mode and Split-MAC Mode."
REFERENCE REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 7 } ::= { capwapBaseWtpEntry 7 }
capwapWTPDiscoveryType OBJECT-TYPE capwapBaseWtpDiscoveryType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), staticConfig(2), dhcp(3), dns(4), acRef(5) unknown(0), staticConfig(1), dhcp(2), dns(3), acRef(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents how WTP discovered the AC. "Represents how WTP discovers the AC.
The following values are supported: The following enumerated values are supported:
unknown(1) - the method is unknown, unknown(0) - Unknown,
staticConfig(2) - static IP configuration, staticConfig(1) - Static Configuration,
dhcp(3) - DHCP, dhcp(2) - DHCP,
dns(4) - DNS, dns(3) - DNS,
acRef(5) - AC Referral." acRef(4) - AC Referral."
REFERENCE REFERENCE
"Section 4.6.23. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 8 } ::= { capwapBaseWtpEntry 8 }
capwapWTPRadiosInUseNum OBJECT-TYPE capwapBaseWtpRadiosInUseNum OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of radios which are in use." "Represents the number of radios in use in the WTP."
REFERENCE REFERENCE
"Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 9 } ::= { capwapBaseWtpEntry 9 }
capwapWTPRadioNumLimit OBJECT-TYPE capwapBaseWtpRadioNumLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum radio number could be supported "Represents the maximum radio number supported by the WTP."
by WTP."
REFERENCE REFERENCE
"Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 10 } ::= { capwapBaseWtpEntry 10 }
capwapWTPStaticIPEnable OBJECT-TYPE capwapBaseWtpStaticIpEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether the WTP should use a static IP address "Represents whether the WTP should use a static IP address
or not. A value of false disables the static IP address, or not. A value of false disables the static IP address,
while a value of true enables it." while a value of true enables it."
REFERENCE REFERENCE
"Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 11 } ::= { capwapBaseWtpEntry 11 }
capwapWTPStaticIPType OBJECT-TYPE capwapBaseWtpStaticIpType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents whether WTP uses IPV4 or IPV6 static IP address." "Represents whether WTP uses IPV4 or IPV6 static IP address."
::= { capwapWTPEntry 12 } ::= { capwapBaseWtpEntry 12 }
capwapWTPStaticIP OBJECT-TYPE capwapBaseWtpStaticIp OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapWTPStaticIPEnable is true, it represents the static "When capwapBaseWtpStaticIpEnable is true, it represents the
IP address to assign to the WTP." static IP address to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 13 } ::= { capwapBaseWtpEntry 13 }
capwapWTPNetmask OBJECT-TYPE capwapBaseWtpNetmask OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapWTPStaticIPEnable is true, it represents the netmask "When capwapBaseWtpStaticIpEnable is true, it represents the
to assign to the WTP." netmask to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 14 } ::= { capwapBaseWtpEntry 14 }
capwapWTPGateway OBJECT-TYPE capwapBaseWtpGateway OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When capwapWTPStaticIPEnable is true, it represents the gateway "When capwapBaseWtpStaticIpEnable is true, it represents the
to assign to the WTP." gateway to assign to the WTP."
REFERENCE REFERENCE
"Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPEntry 15 } ::= { capwapBaseWtpEntry 15 }
capwapBaseWtpRetransmitCount OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of retransmissions for a given
CAPWAP packet."
REFERENCE
"Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 16 }
-- End of capwapBaseWtpTable table
capwapRadioBindTable OBJECT-TYPE -- capwapBaseRadioBindTable Table
SYNTAX SEQUENCE OF CapwapRadioBindEntry
capwapBaseRadioBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display the mapping relationship "A table of objects that display the mapping relationship
between specific interface of 'WTP Virtual Radio Interface' between specific interface of 'WTP Virtual Radio Interface'
ifType and PHY radio. The mapping relationship in this table ifType and PHY radio. The mapping relationship in this table
is persistent at restart/reboot." is persistent at restart/reboot."
::= { capwapWTPs 3 } ::= { capwapBaseWtps 3 }
capwapRadioBindEntry OBJECT-TYPE capwapBaseRadioBindEntry OBJECT-TYPE
SYNTAX CapwapRadioBindEntry SYNTAX CapwapBaseRadioBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the mapping relationship "A set of objects that display the mapping relationship
between 'WTP Virtual Radio' and PHY radio." between 'WTP Virtual Radio' and PHY radio."
INDEX { capwapWTPId, capwapRadioId } INDEX { capwapBaseWtpId, capwapBaseRadioId }
::= { capwapRadioBindTable 1 } ::= { capwapBaseRadioBindTable 1 }
CapwapRadioBindEntry ::= SEQUENCE { CapwapBaseRadioBindEntry ::= SEQUENCE {
capwapRadioId CapwapRadioId, capwapBaseRadioId CapwapBaseRadioIdTC,
capwapWTPVirtualRadioIfIndex InterfaceIndex, capwapBaseVirtualRadioIfIndex InterfaceIndex,
capwapWirelessBinding INTEGER capwapBaseRadioWirelessBinding INTEGER
} }
capwapRadioId OBJECT-TYPE capwapBaseRadioId OBJECT-TYPE
SYNTAX CapwapRadioId SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS accessible-for-notify MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, and only "Represents the identifier of a PHY radio on a WTP, and only
requires unique on a WTP. requires unique on a WTP.
For example, WTP A and WTP B will use same value of For example, WTP A and WTP B will use same value of
capwapRadioId for their first radio." capwapBaseRadioId for their first radio."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioBindEntry 1 } ::= { capwapBaseRadioBindEntry 1 }
capwapWTPVirtualRadioIfIndex OBJECT-TYPE capwapBaseVirtualRadioIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the ifIndex for an interface of 'WTP Virtual Radio "Represents the index value that uniquely identifies a
Interface' ifType. 'WLAN Virtual Radio Interface'. The interface identified by a
particular value of this index is the same interface as
identified by the same value of ifIndex.
Before WTPs connect to AC and get configuration, operator Before WTPs connect to AC and get configuration, operator
will prepare configuration for them. At AC side, there are will prepare configuration for them. On the AC, there are
interface of 'WTP Virtual Radio Interface' type which represent interfaces of 'WTP Virtual Radio Interface' ifType which
PHY radio interface at WTP side. represent PHY radio interfaces on the WTP.
As most MIBs use ifIndex to identify an interface for As most MIBs use ifIndex to identify an interface for
configuration and statistic data, for example, IEEE 802.11 MIB. configuration and statistic data, for example, IEEE 802.11 MIB.
It will be very easy to reuse other MIBs such as IEEE 802.11 It will be very easy to reuse other MIBs such as IEEE 802.11
MIB by 'WTP Virtual Radio Interface'. MIB by 'WTP Virtual Radio Interface'."
Require IANA to assign an ifType for 'WTP Virtual Radio ::= { capwapBaseRadioBindEntry 2 }
Interface'."
::= { capwapRadioBindEntry 2 }
capwapWirelessBinding OBJECT-TYPE capwapBaseRadioWirelessBinding OBJECT-TYPE
SYNTAX INTEGER { none(1), dot11(2), dot16(3), epc(4) } SYNTAX INTEGER { reserved0(0), dot11(1), reserved2(2), epc(3) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the wireless binding type for radio. "Represents the wireless binding type for radio.
The following values are supported: The following enumerated values are supported:
none(1) - No any wireless binding defined. reserved0(0) - Reserved,
dot11(2) - IEEE 802.11. dot11(1) - IEEE 802.11,
dot16(3) - IEEE 802.16. reserved2(2) - Reserved,
epc(4) - EPCGlobal." epc(3) - EPCGlobal."
REFERENCE REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioBindEntry 3 } ::= { capwapBaseRadioBindEntry 3 }
-- End of capwapBaseRadioBindTable Table
-- capwapBaseStationTable Table
capwapStationTable OBJECT-TYPE capwapBaseStationTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapStationEntry SYNTAX SEQUENCE OF CapwapBaseStationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display stations which are "A table of objects that display stations which are accessing
associated with the specific radio on the WTP." the wireless service provided by the AC."
::= { capwapWTPs 4 } ::= { capwapBaseWtps 4 }
capwapStationEntry OBJECT-TYPE capwapBaseStationEntry OBJECT-TYPE
SYNTAX CapwapStationEntry 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 { capwapWTPCurrId, capwapRadioId, capwapStationId } INDEX { capwapBaseWtpCurrId,
::= { capwapStationTable 1 } capwapBaseRadioId,
capwapBaseStationId }
::= { capwapBaseStationTable 1 }
CapwapStationEntry ::= SEQUENCE { CapwapBaseStationEntry ::= SEQUENCE {
capwapStationId CapwapStationId, capwapBaseStationId CapwapBaseStationIdTC,
capwapStationAddedTime DateAndTime, capwapBaseStationAddedTime DateAndTime,
capwapStationVlanName OCTET STRING capwapBaseStationVlanName SnmpAdminString
} }
capwapStationId OBJECT-TYPE capwapBaseStationId OBJECT-TYPE
SYNTAX CapwapStationId SYNTAX CapwapBaseStationIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of the station." "Represents the unique identifier of the station."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStationEntry 1 } ::= { capwapBaseStationEntry 1 }
capwapStationAddedTime OBJECT-TYPE capwapBaseStationAddedTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the time when the station is added." "Represents the time when the station is added."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStationEntry 2 } ::= { capwapBaseStationEntry 2 }
capwapStationVlanName OBJECT-TYPE capwapBaseStationVlanName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(32)) SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents VLAN name to which the station is associated." "Represents VLAN name to which the station is associated."
REFERENCE REFERENCE
"Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStationEntry 3 } ::= { capwapBaseStationEntry 3 }
-- End of capwapBaseStationTable Table
-- capwapBaseWtpRebootStatTable
capwapWTPRebootStatsTable OBJECT-TYPE capwapBaseWtpRebootStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapWTPRebootStatsEntry SYNTAX SEQUENCE OF CapwapBaseWtpRebootStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display WTPs' reboot statistic "A table of objects that display WTPs' reboot statistics."
data."
REFERENCE REFERENCE
"Section 4.6.50. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapWTPs 5 } ::= { capwapBaseWtps 5 }
capwapWTPRebootStatsEntry OBJECT-TYPE capwapBaseWtpRebootStatsEntry OBJECT-TYPE
SYNTAX CapwapWTPRebootStatsEntry SYNTAX CapwapBaseWtpRebootStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display the reboot statistic data "A set of objects that display the reboot statistic data
of a WTP." of a WTP."
INDEX { capwapWTPCurrId } REFERENCE
::= { capwapWTPRebootStatsTable 1 } "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
INDEX { capwapBaseWtpCurrId }
::= { capwapBaseWtpRebootStatsTable 1 }
CapwapWTPRebootStatsEntry ::= SEQUENCE { CapwapBaseWtpRebootStatsEntry ::= SEQUENCE {
capwapWTPRebootCount Counter32, capwapBaseWtpRebootCount Counter32,
capwapWTPInitCount Counter32, capwapBaseWtpInitCount Counter32,
capwapWTPLinkFailureCount Counter32, capwapBaseWtpLinkFailureCount Counter32,
capwapWTPSwFailureCount Counter32, capwapBaseWtpSwFailureCount Counter32,
capwapWTPHwFailureCount Counter32, capwapBaseWtpHwFailureCount Counter32,
capwapWTPOtherFailureCount Counter32, capwapBaseWtpOtherFailureCount Counter32,
capwapWTPUnknownFailureCount Counter32, capwapBaseWtpUnknownFailureCount Counter32,
capwapWTPLastFailureType INTEGER capwapBaseWtpLastFailureType INTEGER
} }
capwapWTPRebootCount OBJECT-TYPE capwapBaseWtpRebootCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of reboots that have occurred due to a "Represents the number of reboots that have occurred due to a
WTP crash. A value of 65535 implies that this information is WTP crash. A value of 65535 implies that this information is
not available on the WTP." not available on the WTP."
::= { capwapWTPRebootStatsEntry 1 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 1 }
capwapWTPInitCount OBJECT-TYPE capwapBaseWtpInitCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of reboots that have occurred at the "Represents the number of reboots that have occurred at the
request of a CAPWAP protocol message, such as a change in request of a CAPWAP protocol message, such as a change in
configuration that required a reboot or an explicit CAPWAP configuration that required a reboot or an explicit CAPWAP
protocol reset request. A value of 65535 implies that this protocol reset request. A value of 65535 implies that this
information is not available on the WTP." information is not available on the WTP."
::= { capwapWTPRebootStatsEntry 2 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 2 }
capwapWTPLinkFailureCount OBJECT-TYPE capwapBaseWtpLinkFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to link failure." connection with an AC has failed due to link failure."
::= { capwapWTPRebootStatsEntry 3 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 3 }
capwapWTPSwFailureCount OBJECT-TYPE capwapBaseWtpSwFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to software related connection with an AC has failed due to software related
reasons." reasons."
::= { capwapWTPRebootStatsEntry 4 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 4 }
capwapWTPHwFailureCount OBJECT-TYPE capwapBaseWtpHwFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to hardware related connection with an AC has failed due to hardware related
reasons." reasons."
::= { capwapWTPRebootStatsEntry 5 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 5 }
capwapWTPOtherFailureCount OBJECT-TYPE capwapBaseWtpOtherFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed due to known reasons, other connection with an AC has failed due to known reasons, other
than AC initiated, link, software or hardware failure." than AC initiated, link, software or hardware failure."
::= { capwapWTPRebootStatsEntry 6 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 6 }
capwapWTPUnknownFailureCount OBJECT-TYPE capwapBaseWtpUnknownFailureCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of times that a CAPWAP protocol "Represents the number of times that a CAPWAP protocol
connection with an AC has failed for unknown reasons." connection with an AC has failed for unknown reasons."
::= { capwapWTPRebootStatsEntry 7 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 7 }
capwapWTPLastFailureType OBJECT-TYPE capwapBaseWtpLastFailureType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER { notSupport(0),
notSupport(1), acInit(2), linkFailure(3), acInit(1),
swFailure(4), hwFailure(5),other(6), unknown(255) linkFailure(2),
swFailure(3),
hwFailure(4),
otherFailure(5),
unknown(255)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The failure type of the most recent WTP failure. "Represents the failure type of the most recent WTP failure.
The following values are supported: The following enumerated values are supported:
notSupport(1) - Not Supported, notSupport(0) - Not Supported,
acInit(2) - AC Initiated, acInit(1) - AC Initiated,
linkFailure(3) - Link Failure, linkFailure(2) - Link Failure,
swFailure(4) - Software Failure, swFailure(3) - Software Failure,
hwFailure(5) - Hardware Failure, hwFailure(4) - Hardware Failure,
otherFailure(6) - 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)."
::= { capwapWTPRebootStatsEntry 8 } REFERENCE
"Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpRebootStatsEntry 8 }
-- End of capwapBaseWtpRebootStatsTable table
-- capwapBaseRadioStatsTable table
capwapRadioStatsTable OBJECT-TYPE capwapBaseRadioStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapRadioStatsEntry SYNTAX SEQUENCE OF CapwapBaseRadioStatsEntry
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 of radios have been reset." and reasons why the WTP radio has been reset."
::= { capwapWTPs 6 } REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtps 6 }
capwapRadioStatsEntry OBJECT-TYPE capwapBaseRadioStatsEntry OBJECT-TYPE
SYNTAX CapwapRadioStatsEntry SYNTAX CapwapBaseRadioStatsEntry
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 { capwapWTPCurrId, capwapRadioId } INDEX { capwapBaseWtpCurrId, capwapBaseRadioId }
::= { capwapRadioStatsTable 1 } ::= { capwapBaseRadioStatsTable 1 }
CapwapRadioStatsEntry ::= SEQUENCE { CapwapBaseRadioStatsEntry ::= SEQUENCE {
capwapRadioResetCount Counter32, capwapBaseRadioResetCount Counter32,
capwapRadioSwFailCount Counter32, capwapBaseRadioSwFailCount Counter32,
capwapRadioHwFailCount Counter32, capwapBaseRadioHwFailCount Counter32,
capwapRadioOtherFailCount Counter32, capwapBaseRadioOtherFailCount Counter32,
capwapRadioUnknownFailCount Counter32, capwapBaseRadioUnknownFailCount Counter32,
capwapRadioConfigUpdateCount Counter32, capwapBaseRadioConfigUpdateCount Counter32,
capwapRadioChannelChangeCount Counter32, capwapBaseRadioChannelChangeCount Counter32,
capwapRadioBandChangeCount Counter32, capwapBaseRadioBandChangeCount Counter32,
capwapRadioCurrentNoiseFloor Integer32, capwapBaseRadioCurrentNoiseFloor Integer32,
capwapRadioDecryptErrorCount Counter32, capwapBaseRadioDecryptErrorCount Counter32,
capwapRadioTxQueueLevel Integer32, capwapBaseRadioLastFailType INTEGER
capwapRadioRFLinkFramesCount Counter32,
capwapRadioLastFailType INTEGER
} }
capwapRadioResetCount OBJECT-TYPE capwapBaseRadioResetCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 1 } ::= { capwapBaseRadioStatsEntry 1 }
capwapRadioSwFailCount OBJECT-TYPE capwapBaseRadioSwFailCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 2 } ::= { capwapBaseRadioStatsEntry 2 }
capwapRadioHwFailCount OBJECT-TYPE capwapBaseRadioHwFailCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 3 } ::= { capwapBaseRadioStatsEntry 3 }
capwapRadioOtherFailCount OBJECT-TYPE capwapBaseRadioOtherFailCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 4 } ::= { capwapBaseRadioStatsEntry 4 }
capwapRadioUnknownFailCount OBJECT-TYPE capwapBaseRadioUnknownFailCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 5 } ::= { capwapBaseRadioStatsEntry 5 }
capwapRadioConfigUpdateCount OBJECT-TYPE capwapBaseRadioConfigUpdateCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 6 } ::= { capwapBaseRadioStatsEntry 6 }
capwapRadioChannelChangeCount OBJECT-TYPE capwapBaseRadioChannelChangeCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 7 } ::= { capwapBaseRadioStatsEntry 7 }
capwapRadioBandChangeCount OBJECT-TYPE capwapBaseRadioBandChangeCount 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 8 } ::= { capwapBaseRadioStatsEntry 8 }
capwapRadioCurrentNoiseFloor OBJECT-TYPE capwapBaseRadioCurrentNoiseFloor 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.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 9 } ::= { capwapBaseRadioStatsEntry 9 }
capwapRadioDecryptErrorCount OBJECT-TYPE capwapBaseRadioDecryptErrorCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of decryption errors that occurred on the "Represents the number of decryption errors that occurred on the
WTP. Note that this field is only valid in cases where the WTP WTP. Note that this field is only valid in cases where the WTP
provides encryption/decryption services." provides encryption/decryption services."
REFERENCE REFERENCE
"Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 10 } ::= { capwapBaseRadioStatsEntry 10 }
capwapRadioTxQueueLevel OBJECT-TYPE
SYNTAX Integer32 (0..100)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the percentage of Wireless Transmit queue
utilization,calculated as the sum of utilized transmit queue
lengths divided by the sum of maximum transmit queue lengths,
multiplied by 100."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 11 }
capwapRadioRFLinkFramesCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of frames transmitted or received per
second by the WTP over the radio interface."
REFERENCE
"Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapRadioStatsEntry 12 }
capwapRadioLastFailType OBJECT-TYPE capwapBaseRadioLastFailType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupport(1), notSupport(0),
swFailure(2), swFailure(1),
hwFailure(3), hwFailure(2),
otherFailure(4), 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 values are supported: notSupport(0) - Not Supported,
notSupport(1) - Not Supported, swFailure(1) - Software Failure,
swFailure(2) - Software Failure, hwFailure(2) - Hardware Failure,
hwFailure(3) - Hardware Failure, otherFailure(3) - Other Failure,
otherFailure(4) - Other Failure,
unknown(255) - Unknown." unknown(255) - Unknown."
::= { capwapRadioStatsEntry 13 } REFERENCE
"Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseRadioStatsEntry 11 }
-- End of capwapBaseRadioStatsTable table
-- CAPWAP Base Parameters Group
capwapVariables OBJECT IDENTIFIER capwapBaseParameters OBJECT IDENTIFIER
::= { capwapObjects 3 } ::= { capwapBaseObjects 3 }
capwapDataChannelDeadInterval OBJECT-TYPE capwapBaseDataChannelDeadInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait "Represents the minimum time, in seconds, a WTP MUST wait
without having received a Data Channel Keep Alive packet without having received a Data Channel Keep Alive packet
before the destination for the Data Channel Keep Alive before the destination for the Data Channel Keep Alive
packets may be considered dead." packets may be considered dead."
REFERENCE REFERENCE
"Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 1 } ::= { capwapBaseParameters 1 }
capwapDataCheckTimer OBJECT-TYPE capwapBaseDataCheckTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents The number of seconds the AC will wait for "Represents The number of seconds the AC will wait for
the Data Channel Keep Alive, which is required by the the Data Channel Keep Alive, which is required by the
CAPWAP state machine's Data Check state. CAPWAP state machine's Data Check state.
The AC resets the state machine if this timer expires The AC resets the state machine if this timer expires
prior to transitioning to the next state." prior to transitioning to the next state."
REFERENCE REFERENCE
"Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 2 } ::= { capwapBaseParameters 2 }
capwapMaxDiscoveryInterval OBJECT-TYPE capwapBaseMaxRetransmit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time allowed between sending "Represent the maximum number of retransmission for a given
Discovery Request messages, in seconds. CAPWAP packet before the link layer considers the peer dead."
This value MUST be no less than 2 seconds and no greater
than 180 seconds."
REFERENCE REFERENCE
"Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 3 } ::= { capwapBaseParameters 3 }
capwapMaxDiscoveries OBJECT-TYPE capwapBaseRetransmitInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "second"
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of Discovery Request messages "Represents the minimum time, in seconds, in which a
that will be sent after a WTP boots." non-acknowledged CAPWAP packet will be retransmitted."
REFERENCE REFERENCE
"Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 4 } ::= { capwapBaseParameters 4 }
capwapMaxRetransmit OBJECT-TYPE capwapBaseReportInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "second"
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represent the maximum number of retransmission for a given "Represents the interval for WTP to send Decryption Error
CAPWAP packet before the link layer considers the peer dead." report."
REFERENCE REFERENCE
"Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 5 } ::= { capwapBaseParameters 5 }
capwapRetransmitInterval OBJECT-TYPE capwapBaseEchoInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, in which a "Represents the minimum time, in seconds, between sending Echo
non-acknowledged CAPWAP packet will be retransmitted." Request messages to the AC with which the WTP has joined."
REFERENCE REFERENCE
"Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 6 } ::= { capwapBaseParameters 6 }
capwapReportInterval OBJECT-TYPE capwapBaseIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the interval for WTP send report." "Represents the idle timeout value that the WTP SHOULD enforce
for its active stations."
REFERENCE REFERENCE
"Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapVariables 7 } ::= { capwapBaseParameters 7 }
-- End of CAPWAP Base Parameters Group
-- CAPWAP Statistics Group -- CAPWAP Statistics Group
capwapStats OBJECT IDENTIFIER capwapBaseStats OBJECT IDENTIFIER
::= { capwapObjects 4 } ::= { capwapBaseObjects 4 }
capwapWTPRetransmitCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of retransmissions for a given
CAPWAP packet."
REFERENCE
"Section 4.8.9. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStats 1 }
capwapFailedDTLSAuthFailCount OBJECT-TYPE capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of failed DTLS session "Represents the number of failed DTLS session
establishment attempts due to authentication failures." establishment attempts due to authentication failures."
REFERENCE REFERENCE
"Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStats 2 } ::= { capwapBaseStats 1 }
capwapFailedDTLSSessionCount OBJECT-TYPE capwapBaseFailedDTLSSessionCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of failed DTLS session "Represents the number of failed DTLS session
establishment attempts." establishment attempts."
REFERENCE REFERENCE
"Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapStats 3 } ::= { capwapBaseStats 2 }
-- Notifications -- Notifications
capwapChannelUp NOTIFICATION-TYPE capwapBaseChannelUp NOTIFICATION-TYPE
OBJECTS { capwapWTPId, OBJECTS { capwapBaseNtfWtpId,
capwapChannelType, capwapBaseNtfChannelType,
capwapWTPAuthenMethod } capwapBaseNtfAuthenMethod }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by AC when a CAPWAP channel "This notification is sent by AC when a CAPWAP channel
established. The notification is separated for data or control established. The notification is separated for data or control
channel." channel."
::= { capwapNotifications 1 } ::= { capwapBaseNotifications 1 }
capwapChannelDown NOTIFICATION-TYPE capwapBaseChannelDown NOTIFICATION-TYPE
OBJECTS { capwapWTPId, capwapChannelDownReason } OBJECTS { capwapBaseNtfWtpId,
capwapBaseNtfChannelType,
capwapBaseNtfChannelDownReason }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by AC when CAPWAP channel becomes "This notification is sent by AC when CAPWAP channel becomes
down." down. The notification is separated for data or control
::= { capwapNotifications 2 } channel."
::= { capwapBaseNotifications 2 }
capwapDecryptErrorReport NOTIFICATION-TYPE capwapBaseDecryptErrorReport NOTIFICATION-TYPE
OBJECTS { capwapWTPId, OBJECTS { capwapBaseNtfWtpId,
capwapRadioId, capwapBaseNtfRadioId,
capwapIdEntryNum, capwapBaseNtfStationIdList }
capwapStationIdList }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP that has occurred "This notification is generated when a WTP that has occurred
decryption error since the last report." decryption error since the last report."
REFERENCE REFERENCE
"Section 4.6.18. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifications 3 } ::= { capwapBaseNotifications 3 }
capwapJoinFailure NOTIFICATION-TYPE capwapBaseJoinFailure NOTIFICATION-TYPE
OBJECTS { capwapWTPId, capwapJoinFailureReason } OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfJoinFailureReason }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP fails to join." "This notification is generated when a WTP fails to join."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifications 4 } ::= { capwapBaseNotifications 4 }
capwapImageUpgradeFailure NOTIFICATION-TYPE capwapBaseImageUpgradeFailure NOTIFICATION-TYPE
OBJECTS { capwapWTPId, capwapImageFailureReason } OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfImageFailureReason }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP fails to update "This notification is generated when a WTP fails to update
software image." firmware image."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifications 5 } ::= { capwapBaseNotifications 5 }
capwapConfigMsgError NOTIFICATION-TYPE capwapBaseConfigMsgError NOTIFICATION-TYPE
OBJECTS { capwapWTPId, capwapConfigMsgErrorType, OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfConfigMsgErrorType,
capwapMsgErrorElements } capwapBaseNtfMsgErrorElements }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a WTP received message "This notification is generated when a WTP received message
elements in the Configuration Status Response which it was elements in the configuration management messages which it was
unable to apply locally." unable to apply locally."
REFERENCE REFERENCE
"Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifications 6 } ::= { capwapBaseNotifications 6 }
capwapRadioOperableStatus NOTIFICATION-TYPE capwapBaseRadioOperableStatus NOTIFICATION-TYPE
OBJECTS { capwapWTPId, OBJECTS { capwapBaseNtfWtpId,
capwapRadioId, capwapBaseNtfRadioId,
capwapRadioOperStatusFlag, capwapBaseNtfRadioOperStatusFlag,
capwapRadioFailureReason } capwapBaseNtfRadioStatusCause }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification will notify which radio become inoperable "The notification is generated when a radio's operational state
or operable." is changed."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifications 7 } ::= { capwapBaseNotifications 7 }
capwapWTPAuthenticationFailure NOTIFICATION-TYPE capwapBaseAuthenticationFailure NOTIFICATION-TYPE
OBJECTS { capwapWTPId, OBJECTS { capwapBaseNtfWtpId,
capwapChannelType, capwapBaseNtfChannelType,
capwapWTPAuthenMethod, capwapBaseNtfAuthenMethod,
capwapWTPAuthenFailureReason } capwapBaseNtfAuthenFailureReason }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notification will notify the authentication failure event, "The notification will notify the authentication failure event,
and provides the reason for it." and provides the reason for it."
::= { capwapNotifications 8 } ::= { capwapBaseNotifications 8 }
-- Objects used only in notifications -- Objects used only in notifications
-- for notifications -- for notifications
capwapNotifyVarObjects OBJECT IDENTIFIER capwapBaseNotifyVarObjects OBJECT IDENTIFIER
::= { capwapObjects 5 } ::= { capwapBaseObjects 5 }
capwapChannelType OBJECT-TYPE capwapBaseNtfWtpId OBJECT-TYPE
SYNTAX CapwapChannelType SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the unique identifier of a WTP."
::= { capwapBaseNotifyVarObjects 1 }
capwapBaseNtfRadioId OBJECT-TYPE
SYNTAX CapwapBaseRadioIdTC
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the identifier of a PHY radio on a WTP, and only
requires unique on a WTP.
For example, WTP A and WTP B will use same value of
capwapBaseNtfRadioId for their first radio."
REFERENCE
"Section 4.3. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseNotifyVarObjects 2 }
capwapBaseNtfChannelType OBJECT-TYPE
SYNTAX CapwapBaseChannelTypeTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the channel type for CAPWAP protocol." "Represents the channel type for CAPWAP protocol."
::= { capwapNotifyVarObjects 1 } ::= { capwapBaseNotifyVarObjects 3 }
capwapWTPAuthenMethod OBJECT-TYPE capwapBaseNtfAuthenMethod OBJECT-TYPE
SYNTAX CapwapWTPAuthenMethod SYNTAX CapwapBaseAuthenMethodTC
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents authentication method for Channel." "Represents authentication method for Channel."
::= { capwapNotifyVarObjects 2 } ::= { capwapBaseNotifyVarObjects 4 }
capwapChannelDownReason OBJECT-TYPE capwapBaseNtfChannelDownReason OBJECT-TYPE
SYNTAX INTEGER { timeout(1), rekeyfailure(2), apReboot(3) } SYNTAX INTEGER { timeout(1),
rekeyfailure(2),
acRebootWtp(3),
dtlsError(4),
maxRetransmit(5) }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the reason for Channel down. "Represents the reason for Channel down.
The following values are supported: The following enumerated values are supported:
timeout(1) - The keep alive is timeout, timeout(1) - The keep alive is timeout,
rekeyfailure(2) - Rekey process is failed, channel will be rekeyfailure(2) - Rekey process is failed, channel will be
broken. broken.
apReboot(3) - AC reboot WTP." acRebootWtp(3) - AC reboot WTP.
::= { capwapNotifyVarObjects 3 } dtlsError(4) - DTLS notifications: DTLSAborted,
DTLSReassemblyFailure, DTLSPeerDisconnect,
capwapIdEntryNum OBJECT-TYPE or frequent DTLSDecapFailure.
SYNTAX Unsigned32 maxRetransmit(5) - The underlying reliable transport's
MAX-ACCESS accessible-for-notify RetransmitCount counter has reached the
STATUS current MaxRetransmit variable"
DESCRIPTION ::= { capwapBaseNotifyVarObjects 5 }
"Represents the entry number of station id in the
capwapStationIdList."
REFERENCE
"Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 4 }
capwapStationIdList OBJECT-TYPE capwapBaseNtfStationIdList OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the list of station id." "Represents the list of station id which use semicolons to
separate each station id."
REFERENCE REFERENCE
"Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 5 } ::= { capwapBaseNotifyVarObjects 6 }
capwapWTPAuthenFailureReason OBJECT-TYPE capwapBaseNtfAuthenFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
keyMismatch(1), invalidCA(2), micError(3), keyMismatch(1), invalidCA(2), micError(3),
timeout(4), unknown(8) timeout(4), unknown(8)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents reason for WTP authorization failure. "Represents reason for WTP authorization failure.
The following values are supported: The following enumerated values are supported:
keyMismatch(1) - WTP's and AC's key is not matched, keyMismatch(1) - WTP's and AC's key is not matched,
invalidCA(2) - ca is not valid, invalidCA(2) - ca is not valid,
micError(3) - detect MIC error, micError(3) - detect MIC error,
timeout(4) - WaitDTLS Timer is timeout, timeout(4) - WaitDTLS Timer is timeout,
unknown(8) - Unknown reason." unknown(8) - Unknown reason."
REFERENCE REFERENCE
"Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 6 } ::= { capwapBaseNotifyVarObjects 7 }
capwapRadioOperStatusFlag OBJECT-TYPE capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE
SYNTAX INTEGER { operable(1), inoperable(2) } SYNTAX INTEGER { reserved(0), operable(1), inoperable(2) }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the operation status of a radio. "Represents the operation status of a radio.
The following values are supported: The following enumerated values are supported:
reserved(0) - Reserved
operable(1) - To indicate radio is operable, operable(1) - To indicate radio is operable,
inoperable(2) - To indicate radio is inoperable, and inoperable(2) - To indicate radio is inoperable, and
capwapRadioFailureReason object will capwapBaseNtfRadioStatusCause object will
give reason in details" give reason in details."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 7 } ::= { capwapBaseNotifyVarObjects 8 }
capwapRadioFailureReason OBJECT-TYPE capwapBaseNtfRadioStatusCause OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
hwError(1), swError(2), adminSet(3), unknown(8) normal(0), hwError(1), swError(2), adminSet(3)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents errors caused by configuration operation. "Represents the reason the radio is out of service.
The following values are supported The following enumerated values are supported:
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."
unknown(8) - Unknown reason."
REFERENCE REFERENCE
"Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 8 } ::= { capwapBaseNotifyVarObjects 9 }
capwapJoinFailureReason OBJECT-TYPE capwapBaseNtfJoinFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unspecified(1), resDepletion(2), unknownSource(3), unspecified(1), resDepletion(2), unknownSource(3),
incorrectData(4), sessionInUse(5), notSupportHw(6), incorrectData(4), sessionIdInUse(5), notSupportHw(6),
notSupportBinding(7) notSupportBinding(7)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The following join failure types are supported: "Represents the reason of join failure.
The following enumerated values are supported:
unspecified(1) - unspecified failure reason, unspecified(1) - unspecified failure reason,
resDepletion(2) - Resource Depletion, resDepletion(2) - Resource Depletion,
unknownSource(3) - Unknown Source, unknownSource(3) - Unknown Source,
incorrectData(4) - Incorrect Data, incorrectData(4) - Incorrect Data,
sessionInUse(5) - Session ID already in use, sessionIdInUse(5) - Session ID already in use,
notSupportHw(6) - WTP Hardware not supported, notSupportHw(6) - WTP Hardware not supported,
notSupportBinding(7) - Binding Not Supported." notSupportBinding(7) - Binding Not Supported."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 9 } ::= { capwapBaseNotifyVarObjects 10 }
capwapImageFailureReason OBJECT-TYPE capwapBaseNtfImageFailureReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
invalidChecksum(1), invalidChecksum(1),
invalidLength(2), invalidLength(2),
other(3), other(3),
inUse(4) inStorage(4)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The following software upgrade failure types are supported: "Represents the reason of image failure.
The following enumerated values are supported:
invalidChecksum(1) - Invalid Checksum, invalidChecksum(1) - Invalid Checksum,
invalidLength(2) - Invalid Data Length, invalidLength(2) - Invalid Data Length,
other(3) - Other Error, other(3) - Other Error,
inUse(4) - Image Already Present." inStorage(4) - Image Already Present."
REFERENCE REFERENCE
"Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 10 } ::= { capwapBaseNotifyVarObjects 11 }
capwapConfigMsgErrorType OBJECT-TYPE capwapBaseNtfConfigMsgErrorType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknownElement(1), unsupportedElement(2), unknownElement(1), unsupportedElement(2),
unknownValue(3), unsupportedValue(4) unknownValue(3), unsupportedValue(4)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The following software upgrade failure types are supported: "Represents the type of configuration message error.
The following enumerated values are supported:
unknownElement(1) - Unknown Message Element, unknownElement(1) - Unknown Message Element,
unsupportedElement(2) - Unsupported Message Element, unsupportedElement(2) - Unsupported Message Element,
unknownValue(3) - Unknown Message Element Value, unknownValue(3) - Unknown Message Element Value,
unsupportedValue(4) - Unsupported Message Element Value." unsupportedValue(4) - Unsupported Message Element Value."
REFERENCE REFERENCE
"Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 11 } ::= { capwapBaseNotifyVarObjects 12 }
capwapMsgErrorElements 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 element sent by the AC in the "Represents the message elements sent by the AC in the
Configuration Status Response message that caused the error." Configuration Status Response message that caused the error."
REFERENCE REFERENCE
"Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapNotifyVarObjects 12 } ::= { capwapBaseNotifyVarObjects 13 }
-- Module compliance -- Module compliance
capwapCompliances OBJECT IDENTIFIER capwapBaseCompliances OBJECT IDENTIFIER
::= { capwapConformance 1 } ::= { capwapBaseConformance 1 }
capwapGroups OBJECT IDENTIFIER capwapBaseGroups OBJECT IDENTIFIER
::= { capwapConformance 2 } ::= { capwapBaseConformance 2 }
capwapCompliance MODULE-COMPLIANCE capwapBaseCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
CAPWAP Base MIB." CAPWAP-BASE-MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { capwapACNodeGroup, MANDATORY-GROUPS { capwapBaseAcNodeGroup,
capwapWTPStateGroup, capwapBaseWtpStateGroup,
capwapWTPsGroup, capwapBaseWtpsGroup,
capwapRadiosGroup capwapBaseRadiosGroup,
capwapBaseStationsGroup
} }
GROUP capwapACNodeGroup2 GROUP capwapBaseAcNodeGroup2
DESCRIPTION DESCRIPTION
"The capwapACNodeGroup2 group is optional." "The capwapBaseAcNodeGroup2 group is optional."
GROUP capwapWTPsGroup2 GROUP capwapBaseAcNameListGroup
DESCRIPTION DESCRIPTION
"The capwapWTPsGroup2 group is optional." "The capwapBaseAcNameListGroup group is optional."
GROUP capwapWTPRebootStatsGroup GROUP capwapBaseWtpsGroup2
DESCRIPTION DESCRIPTION
"The capwapWTPRebootStatsGroup group is optional." "The capwapBaseWtpsGroup2 group is optional."
GROUP capwapRadioStatsGroup GROUP capwapBaseWtpRebootStatsGroup
DESCRIPTION DESCRIPTION
"The capwapRadioStatsGroup group is optional." "The capwapBaseWtpRebootStatsGroup group is optional."
GROUP capwapVariablesGroup GROUP capwapBaseRadioStatsGroup
DESCRIPTION DESCRIPTION
"The capwapVariablesGroup group is optional." "The capwapBaseRadioStatsGroup group is optional."
GROUP capwapStatsGroup GROUP capwapBaseParametersGroup
DESCRIPTION DESCRIPTION
"The capwapStatsGroup group is optional." "The capwapBaseParametersGroup group is optional."
GROUP capwapNofificationGroup GROUP capwapBaseStatsGroup
DESCRIPTION DESCRIPTION
"The group capwapNofificationGroup is optional." "The capwapBaseStatsGroup group is optional."
GROUP capwapNotifyVarGroup GROUP capwapBaseNotificationGroup
DESCRIPTION DESCRIPTION
"The capwapNotifyVarGroup group is optional. "The group capwapBaseNotificationGroup is optional."
If capwapNofificationGroup is supported,
GROUP capwapBaseNotifyVarGroup
DESCRIPTION
"The capwapBaseNotifyVarGroup group is optional.
If capwapBaseNotificationGroup is supported,
this group must be implemented." this group must be implemented."
OBJECT capwapWirelessBinding OBJECT capwapBaseRadioWirelessBinding
SYNTAX INTEGER { none(1) } SYNTAX INTEGER { reserved0(0), reserved2(2) }
DESCRIPTION DESCRIPTION
"A value other than none(1) need not be supported if there is "A value other than reserved0(0), reserved2(2) need not be
no wireless binding defined for technologies used." supported if there is no wireless binding defined for
::= { capwapCompliances 1 } technologies used."
::= { capwapBaseCompliances 1 }
capwapACNodeGroup OBJECT-GROUP capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPSessions, capwapBaseWtpSessions,
capwapWTPSessionsLimit, capwapBaseWtpSessionsLimit,
capwapStationSessions, capwapBaseStationSessions,
capwapStationSessionsLimit capwapBaseStationSessionsLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
basic properties for AC from CAPWAP protocol perspective." basic properties for AC from CAPWAP protocol perspective."
::= { capwapGroups 1 } ::= { capwapBaseGroups 1 }
capwapACNodeGroup2 OBJECT-GROUP capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDataChannelSecOptions, capwapBaseDataChannelSecOptions,
capwapWTPAuthenOptions, capwapBaseWtpAuthenOptions,
capwapWTPFallbackEnable, capwapBaseWtpFallbackEnable
capwapWTPACNameList
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
other properties such as security for AC from other properties such as security for AC from
CAPWAP protocol perspective." CAPWAP protocol perspective."
::= { capwapGroups 2 } ::= { capwapBaseGroups 2 }
capwapWTPStateGroup OBJECT-GROUP capwapBaseAcNameListGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPId, capwapBaseAcNameListName,
capwapWTPIPAddressType, capwapBaseAcNameListPriority
capwapWTPIPAddress, }
capwapWTPPHYAddress, STATUS current
capwapWTPState DESCRIPTION
"The collection of objects which are used to represent
AC name list."
::= { capwapBaseGroups 3 }
capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS {
capwapBaseWtpIpAddressType,
capwapBaseWtpIpAddress,
capwapBaseWtpPhyAddress,
capwapBaseWtpState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
WTP state information." WTP state information."
::= { capwapGroups 3 } ::= { capwapBaseGroups 4 }
capwapWTPsGroup OBJECT-GROUP capwapBaseWtpsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPName, capwapBaseWtpName,
capwapWTPLocation, capwapBaseWtpLocation,
capwapWTPBaseMACAddress, capwapBaseWtpBaseMacAddress,
capwapWTPTunnelModeOptions, capwapBaseTunnelModeOptions,
capwapWTPMACTypeOptions, capwapBaseMacTypeOptions,
capwapWTPRadiosInUseNum, capwapBaseWtpRadiosInUseNum,
capwapWTPRadioNumLimit capwapBaseWtpRadioNumLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
configuration and properties information for WTP configuration and properties information for WTP
in running state." in running state."
::= { capwapGroups 4 } ::= { capwapBaseGroups 5 }
capwapWTPsGroup2 OBJECT-GROUP capwapBaseWtpsGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPPHYIndex, capwapBaseWtpPhyIndex,
capwapWTPDiscoveryType, capwapBaseWtpDiscoveryType,
capwapWTPStaticIPEnable, capwapBaseWtpStaticIpEnable,
capwapWTPStaticIPType, capwapBaseWtpStaticIpType,
capwapWTPStaticIP, capwapBaseWtpStaticIp,
capwapWTPNetmask, capwapBaseWtpNetmask,
capwapWTPGateway capwapBaseWtpGateway
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
configuration and properties information for WTP configuration and properties information for WTP
in running state." in running state."
::= { capwapGroups 5 } ::= { capwapBaseGroups 6 }
capwapRadiosGroup OBJECT-GROUP capwapBaseRadiosGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapRadioId, capwapBaseVirtualRadioIfIndex,
capwapWTPVirtualRadioIfIndex, capwapBaseRadioWirelessBinding
capwapWirelessBinding
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
wireless binding type, the mapping relationship between wireless binding type, the mapping relationship between
'WLAN Virtual Radio Interface' and PHY radio." 'WLAN Virtual Radio Interface' and PHY radio."
::= { capwapGroups 6 } ::= { capwapBaseGroups 7 }
capwapStationsGroup OBJECT-GROUP capwapBaseStationsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapStationAddedTime, capwapBaseStationAddedTime,
capwapStationVlanName capwapBaseStationVlanName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
stations' basic property." stations' basic property."
::= { capwapGroups 7 } ::= { capwapBaseGroups 8 }
capwapWTPRebootStatsGroup OBJECT-GROUP capwapBaseWtpRebootStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPRebootCount, capwapBaseWtpRebootCount,
capwapWTPInitCount, capwapBaseWtpInitCount,
capwapWTPLinkFailureCount, capwapBaseWtpLinkFailureCount,
capwapWTPSwFailureCount, capwapBaseWtpSwFailureCount,
capwapWTPHwFailureCount, capwapBaseWtpHwFailureCount,
capwapWTPOtherFailureCount, capwapBaseWtpOtherFailureCount,
capwapWTPUnknownFailureCount, capwapBaseWtpUnknownFailureCount,
capwapWTPLastFailureType capwapBaseWtpLastFailureType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "The collection of objects which are used for collecting
WTP reboot count, link failure count, hardware failure WTP reboot count, link failure count, hardware failure
count and so on." count and so on."
::= { capwapGroups 8 } ::= { capwapBaseGroups 9 }
capwapRadioStatsGroup OBJECT-GROUP capwapBaseRadioStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapRadioResetCount, capwapBaseRadioResetCount,
capwapRadioSwFailCount, capwapBaseRadioSwFailCount,
capwapRadioHwFailCount, capwapBaseRadioHwFailCount,
capwapRadioOtherFailCount, capwapBaseRadioOtherFailCount,
capwapRadioUnknownFailCount, capwapBaseRadioUnknownFailCount,
capwapRadioConfigUpdateCount, capwapBaseRadioConfigUpdateCount,
capwapRadioChannelChangeCount, capwapBaseRadioChannelChangeCount,
capwapRadioBandChangeCount, capwapBaseRadioBandChangeCount,
capwapRadioCurrentNoiseFloor, capwapBaseRadioCurrentNoiseFloor,
capwapRadioDecryptErrorCount, capwapBaseRadioDecryptErrorCount,
capwapRadioTxQueueLevel, capwapBaseRadioLastFailType
capwapRadioRFLinkFramesCount,
capwapRadioLastFailType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "The collection of objects which are used for collecting
radio reset count, channel change count, hardware failure radio reset count, channel change count, hardware failure
count and so on" count and so on"
::= { capwapGroups 9 } ::= { capwapBaseGroups 10 }
capwapVariablesGroup OBJECT-GROUP capwapBaseParametersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapDataChannelDeadInterval, capwapBaseDataChannelDeadInterval,
capwapDataCheckTimer, capwapBaseDataCheckTimer,
capwapMaxDiscoveryInterval, capwapBaseRetransmitInterval,
capwapMaxDiscoveries, capwapBaseMaxRetransmit,
capwapRetransmitInterval, capwapBaseEchoInterval,
capwapMaxRetransmit, capwapBaseIdleTimeout,
capwapReportInterval capwapBaseReportInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for CAPWAP protocol."
::= { capwapGroups 10 } ::= { capwapBaseGroups 11 }
capwapStatsGroup OBJECT-GROUP capwapBaseStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPRetransmitCount, capwapBaseWtpRetransmitCount,
capwapFailedDTLSAuthFailCount, capwapBaseFailedDTLSAuthFailCount,
capwapFailedDTLSSessionCount capwapBaseFailedDTLSSessionCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for CAPWAP protocol."
::= { capwapGroups 11 } ::= { capwapBaseGroups 12 }
capwapNofificationGroup NOTIFICATION-GROUP capwapBaseNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
capwapChannelUp, capwapBaseChannelUp,
capwapChannelDown, capwapBaseChannelDown,
capwapDecryptErrorReport, capwapBaseDecryptErrorReport,
capwapJoinFailure, capwapBaseJoinFailure,
capwapImageUpgradeFailure, capwapBaseImageUpgradeFailure,
capwapConfigMsgError, capwapBaseConfigMsgError,
capwapRadioOperableStatus, capwapBaseRadioOperableStatus,
capwapWTPAuthenticationFailure capwapBaseAuthenticationFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of notifications in this MIB." "Collection of notifications in this MIB."
::= { capwapGroups 12 } ::= { capwapBaseGroups 13 }
capwapNotifyVarGroup OBJECT-GROUP capwapBaseNotifyVarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapWTPId, capwapBaseNtfWtpId,
capwapRadioId, capwapBaseNtfRadioId,
capwapChannelType, capwapBaseNtfChannelType,
capwapWTPAuthenMethod, capwapBaseNtfAuthenMethod,
capwapChannelDownReason, capwapBaseNtfChannelDownReason,
capwapIdEntryNum, capwapBaseNtfStationIdList,
capwapStationIdList, capwapBaseNtfAuthenFailureReason,
capwapWTPAuthenFailureReason, capwapBaseNtfRadioOperStatusFlag,
capwapRadioOperStatusFlag, capwapBaseNtfRadioStatusCause,
capwapRadioFailureReason, capwapBaseNtfJoinFailureReason,
capwapJoinFailureReason, capwapBaseNtfImageFailureReason,
capwapImageFailureReason, capwapBaseNtfConfigMsgErrorType,
capwapConfigMsgErrorType, capwapBaseNtfMsgErrorElements
capwapMsgErrorElements
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for notification." "Objects used for notification."
::= { capwapGroups 13 } ::= { capwapBaseGroups 14 }
END END
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. The followings are the tables and objects and
sensitivity/vulnerability: their sensitivity/vulnerability:
o - Unauthorized changes to the capwapWTPTable, writable objects o - Unauthorized changes to the capwapBaseWtpTable, writable objects
under capwapACs group may disrupt allocation of resources in the under capwapBaseAcs group may disrupt allocation of resources in
network. the network.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. The followings are the tables and objects and
sensitivity/vulnerability: their sensitivity/vulnerability:
o - The capwapWTPTable exposes WTP's important information like IP o - The capwapBaseWtpTable exposes WTP's important information like
address, MAC type and so on; IP address, MAC type and so on;
o - The capwapWTPRebootStatTable exposes WTP's failure information; o - The capwapBaseWtpRebootStatTable exposes WTP's failure
information;
o - The capwapRadioStatsTable exposes radio's failure information; o - The capwapBaseRadioStatsTable exposes radio's failure
information;
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
skipping to change at page 49, line 12 skipping to change at page 50, line 8
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 11. IANA Considerations
11.1. IANA Considerations for CAPWAP-MIB 11.1. IANA Considerations for CAPWAP-BASE-MIB
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
capwapMIB { mib-2 XXX } capwapBaseMIB { mib-2 XXX }
11.2. IANA Considerations for ifType 11.2. IANA Considerations for ifType
Require IANA to assign a ifType for 'WTP Virtual Radio Interface' Require IANA to assign a ifType for 'WTP Virtual Radio Interface'
type. type.
12. Contributors 12. Contributors
This MIB is based on contributions from Long Gao. This MIB is based on contributions from Long Gao.
skipping to change at page 50, line 43 skipping to change at page 51, line 40
Schoenwaelder, "Textual Schoenwaelder, "Textual
Conventions for Internet Conventions for Internet
Network Addresses", Network Addresses",
RFC 4001, February 2005. RFC 4001, February 2005.
[RFC4133] Bierman, A. and K. [RFC4133] Bierman, A. and K.
McCloghrie, "Entity MIB McCloghrie, "Entity MIB
(Version 3)", RFC 4133, (Version 3)", RFC 4133,
August 2005. August 2005.
[I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP [I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley,
D., and P. Calhoun, "CAPWAP
Protocol Specification", dr Protocol Specification", dr
aft-ietf-capwap-protocol- aft-ietf-capwap-protocol-
specification-10 (work in specification-13 (work in
progress), March 2008. progress), September 2008.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., [RFC3410] Case, J., Mundy, R.,
Partain, D., and B. Partain, D., and B.
Stewart, "Introduction and Stewart, "Introduction and
Applicability Statements Applicability Statements
for Internet-Standard for Internet-Standard
Management Framework", Management Framework",
RFC 3410, December 2002. RFC 3410, December 2002.
skipping to change at page 51, line 44 skipping to change at page 52, line 37
Chris Elliott (editor) Chris Elliott (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park
27709 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
EMail: chelliot@cisco.com EMail: chelliot@cisco.com
Puneet Agarwal (editor) Yong Zhang (editor)
Broadcom, Inc. Fortinet, Inc.
1090 Kifer Road
Sunnyvale, CA 94086
USA
EMail: pagarwal@broadcom.com EMail: yzhang@fortinet.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 432 change blocks. 
931 lines changed or deleted 986 lines changed or added

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