idnits 2.17.1 draft-ietf-capwap-base-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 29, 2009) is 5444 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Obsolete informational reference (is this intentional?): RFC 4347 (Obsoleted by RFC 6347) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Y. Shi, Ed. 3 Internet-Draft Hangzhou H3C Tech. Co., Ltd 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: November 30, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 May 29, 2009 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-05 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on November 30, 2009. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents in effect on the date of 45 publication of this document (http://trustee.ietf.org/license-info). 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. 49 Abstract 51 This memo defines a portion of the Management Information Base (MIB) 52 for use with network management protocols. In particular, it 53 describes the managed objects for modeling the Control And 54 Provisioning of Wireless Access Points (CAPWAP) Protocol. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4 64 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 65 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 66 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 67 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 68 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 69 5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7 70 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7 71 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 72 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9 73 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9 74 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 75 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10 76 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 77 8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10 78 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14 79 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14 80 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17 81 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17 82 9.3.1. Configuration Status Response Message . . . . . . . . 17 83 9.3.2. Configuration Update Response Message . . . . . . . . 18 84 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 85 11. Security Considerations . . . . . . . . . . . . . . . . . . . 70 86 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71 87 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 71 88 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 71 89 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 71 90 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71 91 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 92 15.1. Normative References . . . . . . . . . . . . . . . . . . . 72 93 15.2. Informative References . . . . . . . . . . . . . . . . . . 73 94 Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 74 96 1. Introduction 98 The CAPWAP Protocol [RFC5415] defines a standard, interoperable 99 protocol, which enables an Access Controller (AC) to manage a 100 collection of Wireless Termination Points(WTPs). 102 This document defines a MIB module that can be used to manage the 103 CAPWAP implementations. This MIB module covers both configuration 104 and WTP status-monitoring aspects of CAPWAP, and provides a way to 105 reuse MIB modules for any wireless technology. 107 2. The Internet-Standard Management Framework 109 For a detailed overview of the documents that describe the current 110 Internet-Standard Management Framework, please refer to section 7 of 111 RFC 3410 [RFC3410]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. MIB objects are generally 115 accessed through the Simple Network Management Protocol (SNMP). 116 Objects in the MIB are defined using the mechanisms defined in the 117 Structure of Management Information (SMI). This memo specifies a MIB 118 module that is compliant to the SMIv2, which is described in STD 58, 119 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 120 [RFC2580]. 122 3. Terminology 124 This document uses terminology from the CAPWAP Protocol specification 125 [RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118]. 127 Access Controller (AC): The network entity that provides WTP access 128 to the network infrastructure in the data plane, control plane, 129 management plane, or a combination therein. 131 Wireless Termination Point (WTP): The physical or network entity that 132 contains an RF antenna and wireless PHY to transmit and receive 133 station traffic for wireless access networks. 135 Control And Provisioning of Wireless Access Points (CAPWAP): It is a 136 generic protocol defining AC and WTP control and data plane 137 communication via a CAPWAP protocol transport mechanism. CAPWAP 138 control messages, and optionally CAPWAP data messages, are secured 139 using Datagram Transport Layer Security (DTLS) [RFC4347]. 141 CAPWAP Control Channel: A bi-directional flow defined by the AC IP 142 Address, WTP IP Address, AC control port, WTP control port and the 143 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control 144 packets are sent and received. 146 CAPWAP Data Channel: A bi-directional flow defined by the AC IP 147 Address, WTP IP Address, AC data port, WTP data port, and the 148 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data 149 packets are sent and received. 151 Station (STA): A device that contains an interface to a wireless 152 medium (WM). 154 Split and Local MAC: The CAPWAP protocol supports two modes of 155 operation: Split and Local MAC. In Split MAC mode all L2 wireless 156 data and management frames are encapsulated via the CAPWAP protocol 157 and exchanged between the AC and the WTPs. The Local MAC mode allows 158 the data frames to be either locally bridged, or tunneled as 802.3 159 frames. 161 Wireless Binding: The CAPWAP protocol is independent of a specific 162 WTP radio technology, as well its associated wireless link layer 163 protocol. Elements of the CAPWAP protocol are designed to 164 accommodate the specific needs of each wireless technology in a 165 standard way. Implementation of the CAPWAP protocol for a particular 166 wireless technology MUST define a binding protocol for it, e.g., the 167 binding for IEEE 802.11, provided in [RFC5416]. 169 Autonomous WLAN Architecture: It is the traditional autonomous WLAN 170 architecture, in which each WTP is a single physical device that 171 implements all the wireless services. 173 Centralized WLAN Architecture: It is an emerging hierarchical 174 architecture utilizing one or more centralized controllers for 175 managing a large number of WTP devices. It can be said that the full 176 wireless functions are implemented across multiple physical network 177 devices, namely, the WTPs and ACs. 179 4. Conventions 181 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 182 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 183 document are to be interpreted as described in RFC 2119 [RFC2119]. 185 5. Overview 187 5.1. Requirements and Constraints 189 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to: 191 - Support centralized management and monitoring of WTPs from the AC; 192 - Allow operators to make configurations for WTPs before and after 193 they connect to the AC; 195 - Support querying of CAPWAP protocol parameters; 197 - Support displaying of WTPs' current state and configuration; 199 - Provide basic property information about the AC, WTP, radio and 200 station and their relationships; 202 - Provide counters for events on WTPs and radios such as reboot and 203 hardware failure; 205 - Provide various notifications such as channel up and join failure. 207 5.2. Wireless Binding MIB Modules 209 Other Standards Developing Organizations (SDOs), such as IEEE, have 210 already defined MIB modules for a specific wireless technology, e.g., 211 IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are 212 called wireless binding MIB modules. 214 5.3. Design Objectives 216 This document introduces a mechanism to avoid redefining MIB objects 217 in the existing MIB modules for a specific wireless technology, in 218 other words, a mechanism to reuse wireless binding MIB modules 219 defined by other SDOs. 221 In summary, the CAPWAP-BASE-MIB module has the following design 222 objectives: 224 - To implement an architecture that uses SNMP for the management and 225 control of wireless networks, and answering the operator's 226 requirements for centralized management, whatever the wireless 227 devices are configured and deployed (centralized, autonomous, or some 228 mix); 230 - To be consistent with the CAPWAP protocol; 232 - To be independent of any wireless technologies and be able to reuse 233 wireless binding MIB modules defined by other SDOs; 235 - To enable interoperability between vendors; 237 - To meet requirements for the centralized WLAN architecture. 239 5.4. Design Idea 241 The basic design idea of the CAPWAP-BASE-MIB module is: 243 - The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT 244 REQUIRED on the WTP devices. It follows the same model as the CAPWAP 245 protocol: Centralized Control; 247 - It is designed to accommodate the specific needs of each wireless 248 technology in a standard way. It is independent of any wireless 249 technologies; 251 - The ifIndex [RFC2863] is used as a common handler for corresponding 252 interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific 253 wireless technologies; 255 - The operator could manage and control the centralized WLAN 256 architectures using multiple MIB modules defined by multiple SDOs, 257 while keeping them loosely coupled. 259 5.5. Mechanism of Reusing Wireless Binding MIB Modules 261 For any wireless technology, the configuration and management of 262 radios are very important. As usual, wireless binding MIB modules 263 support radio management on their own. For example, the MIB tables 264 such as the Dot11OperationTable [IEEE.802-11.2007] are able to 265 support WTP radio configuration. These tables use the ifIndex as the 266 index, and work well under autonomous WLAN architecture. 268 To reuse such wireless binding MIB modules is very important to 269 centralized WLAN architectures. According to [RFC5415], a specific 270 PHY radio could be identified by the combination of the identifiers 271 of the WTP and radio (WTP ID + radio ID), so the key point is to make 272 use of the ifIndex idea and find a way to maintain the mappings 273 between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism, 274 an ifIndex can identify an interface in an abstract way, and it does 275 NOT care for the interface's PHY location (either on the WTP or AC). 276 The AC can have WTP Virtual Radio Interfaces to logically represent 277 PHY radios on the WTP. It looks like that PHY radios are located on 278 the AC, and PHY location of the WTP (radio) is hidden to the 279 operator. The operator can operate radios through MIB tables with 280 the ifIndex of a WTP Virtual Radio Interface. As a type of abstract 281 interface, the WTP Virtual Radio Interface could be used by any 282 wireless technology such as IEEE 802.11 and 802.16. The 283 capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used 284 to store the mappings between the 'WTP ID+ Radio ID' and the ifIndex. 286 5.6. CAPWAP Protocol Wireless Binding MIB Module 288 According to the CAPWAP Protocol specification [RFC5415], when 289 defining a binding for wireless technologies, the authors MUST 290 include any necessary definitions for technology-specific messages 291 and all technology-specific message elements for those messages. A 292 CAPWAP binding protocol is required for a specific wireless binding 293 technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding. 295 Sometimes, not all the technology-specific message elements in a 296 CAPWAP binding protocol have MIB objects defined by other SDOs. For 297 example, the protocol of [RFC5416] defines WLAN conception. The WLAN 298 refers to a logical component instantiated on a WTP device. A single 299 physical WTP MAY operate a number of WLANs. Also, Local or Split MAC 300 modes could be specified for a WLAN. The MAC mode for a WLAN is not 301 in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in 302 addition to the existing wireless binding MIB modules defined by 303 other SDOs, a CAPWAP protocol wireless binding MIB module is required 304 to be defined for a wireless binding, e.g, the CAPWAP Protocol 305 Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. 307 5.7. WTP Profile 309 In a centralized WLAN architecture, a WTP profile is used to make 310 configurations such as static IP address for a WTP before and after 311 it connects to the AC. It MUST contain the serial number [RFC5415] 312 of the WTP because the CAPWAP message received from the WTP contains 313 its serial number and the AC uses this serial number to find the 314 corresponding WTP profile. 316 Another important function of WTP profile is to trigger the creation 317 of WTP Virtual Radio Interfaces on the AC. To implement this 318 function, a WTP profile MUST include the WTP's model number 319 [RFC5415], which reflects the number of PHY radios on the WTP. In 320 this way, the creation of a WTP profile triggers the AC to 321 automatically create the same number of WTP Virtual Radio Interfaces 322 corresponding to the WTP's PHY radios without manual intervention. 323 With the ifIndexes of WTP Virtual Radio Interfaces, the operator 324 could configure and manage the WTP's PHY radios through the wireless 325 binding MIB modules. 327 6. Structure of the MIB Module 329 The MIB objects are derived from the CAPWAP protocol document 330 [RFC5415]. 332 1) capwapBaseAcNameListTable 333 The AC name list table is used to configure the AC name list. 335 2) capwapBaseMacAclTable 337 The ACL table is used to configure stations' Access Control 338 List(ACL). 340 3) capwapBaseWtpProfileTable 342 The WTP profile table is used to configure WTP profiles for WTPs to 343 be managed before they connect to the AC. An operator could change a 344 WTP's current configuration by changing the values of parameters in 345 the corresponding WTP profile. 347 4) capwapBaseWtpStateTable 349 The WTPs status table is used to indicate each WTP's CAPWAP FSM 350 state, and helps operator to query WTPs' current configuration. 352 5) capwapBaseWtpTable 354 The WTPs table is used display properties of WTPs in running state. 356 6) capwapBaseWirelessBindingTable 358 The wireless binding table is used to display the mappings between 359 WTP Virtual Radio Interfaces and PHY radios, and the wireless binding 360 type for each PHY radio. 362 7) capwapBaseStationTable 364 The station table is used for providing stations' basic property 365 information. 367 8) capwapBaseWtpEventsStatsTable 369 The WTP events statistic table is used for collecting WTP reboot 370 count, link failure count, hardware failure count and so on. 372 9) capwapBaseRadioEventsStatsTable 374 The radio events statistic table is used for collecting radio reset 375 count, channel change count, hardware failure count and so on. 377 7. Relationship to Other MIB Modules 378 7.1. Relationship to SNMPv2-MIB Module 380 The CAPWAP-BASE-MIB module does not duplicate the objects of the 381 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being 382 mandatory for all systems, and the objects apply to the entity as a 383 whole. The 'system' group provides identification of the management 384 entity and certain other system-wide data. 386 7.2. Relationship to IF-MIB Module 388 The Interfaces Group [RFC2863] defines generic managed objects for 389 managing interfaces. This memo contains the media-specific 390 extensions to the Interfaces Group for managing WTP PHY radios that 391 are modeled as interfaces. 393 The IF-MIB module is required to be supported on the AC. Each PHY 394 radio on the WTP corresponds to a WTP Virtual Radio Interface on the 395 AC. The WTP Virtual Radio Interface provides a way to configure the 396 radio's parameters and query radio's traffic statistics, and reuse 397 wireless binding modules defined by other SDOs. The interface MUST 398 be modeled as an ifEntry, and ifEntry objects such as ifIndex, 399 ifDescr, ifName, ifAlias are to be used as per [RFC2863]. 401 Also, as an ifIndex [RFC2863] is used as a common handler for a 402 corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless 403 technologies MIB modules, the AC MUST have a mechanism that preserves 404 the values of the ifIndexes in the ifTable at AC reboot. 406 7.3. Relationship to ENTITY-MIB Module 408 The ENTITY-MIB module [RFC4133] meets the need for a standardized way 409 of representing a single agent, which supports multiple instances of 410 one MIB. It could express a certain relationship between multiple 411 entities, and provide entity properties for each entity. 413 In a centralized WLAN architecture, the SNMP agent runs on the AC, 414 and is not required on the WTP. With the ENTITY-MIB module on the 415 AC, it could keep entity information such as firmware revision and 416 software revision of the AC and WTPs. From the ENTITY-MIB module's 417 perspective, the overall physical entity (AC) is a 'compound' of 418 multiple physical entities (that is, the WTPs connected to AC), and 419 all entities are each identified by a Physical index. The 420 capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the 421 capwapBaseWtpPhyIndex object to store the mappings of WTP object 422 between CAPWAP-BASE-MIB and ENTITY-MIB modules. 424 By combining the MIB modules, operators could query the status and 425 properties of the AC and WTPs. For example, they could get a WTP's 426 current status through the CAPWAP-BASE-MIB module, and a WTP's 427 software revision information through the ENTITY-MIB module. The 428 CAPWAP-BASE-MIB module does not duplicate those objects defined in 429 the ENTITY-MIB module. 431 7.4. Relationship to Wireless Binding MIB Modules 433 The wireless binding MIB module of a wireless technology (such as 434 [IEEE.802-11.2007]) is required to be supported on the AC. The 435 CAPWAP-BASE-MIB module is able to support any wireless binding. 436 Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a 437 consistent and abstract way of reusing MIB objects in the wireless 438 binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate 439 those objects defined in the wireless binding MIB modules. 441 7.5. MIB Modules Required for IMPORTS 443 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 444 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP- 445 FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB 446 [RFC4133]. 448 8. Example of CAPWAP-BASE-MIB Module Usage 450 Here takes IEEE 802.11 binding as an example to show how the MIB 451 modules operate. 453 1) Create a WTP profile 455 Suppose the WTP's serial identifier is '12345678'. Create the WTP 456 profile as follows: 458 In CapwapBaseWtpProfileTable 459 { 460 capwapBaseWtpProfileId = 1, 461 capwapBaseWtpProfileName = 'WTP Profile 12345678', 462 capwapBaseWtpProfileWTPSerialId = '12345678', 463 capwapBaseWtpProfileWTPModelNumber = 'WTP123', 464 capwapBaseWtpProfileWtpName = 'WTP 12345678', 465 capwapBaseWtpProfileWtpLocation = 'office', 466 capwapBaseWtpProfileWtpStaticIpEnable = true(1), 467 capwapBaseWtpProfileWtpStaticIpType = ipv4(1), 468 capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', 469 capwapBaseWtpProfileWtpNetmask = '255.255.255.0', 470 capwapBaseWtpProfileWtpGateway = '192.168.0.1', 471 capwapBaseWtpProfileWtpFallbackEnable = true(1), 472 capwapBaseWtpProfileWtpEchoInterval = 30, 473 capwapBaseWtpProfileWtpIdleTimeout = 300, 474 capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, 475 capwapBaseWtpProfileWtpReportInterval = 120, 476 capwapBaseWtpProfileWtpSilentInterval = 30, 477 capwapBaseWtpProfileWtpStatisticsTimer = 120, 478 capwapBaseWtpProfileWtpWaitDTLSTimer = 60, 479 capwapBaseWtpProfileWtpEcnSupport = limited(0) 480 } 482 Suppose the WTP with model number 'WTP123' has one PHY radio and this 483 PHY radio is identified by ID 1. The creation of this WTP profile 484 triggers the AC to automatically create a WTP Virtual Radio Interface 485 and add a new row object to the CapwapBaseWirelessBindingTable 486 without manual intervention. Suppose the ifIndex of the WTP Virtual 487 Radio Interface is 10. The following information is stored in the 488 CapwapBaseWirelessBindingTable. 490 In CapwapBaseWirelessBindingTable 491 { 492 capwapBaseWtpProfileId = 1, 493 capwapBaseWirelessBindingRadioId = 1, 494 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 495 capwapBaseWirelessBindingType = dot11(2) 496 } 498 The WTP Virtual Radio Interfaces on the AC correspond to the PHY 499 radios on the WTP. The WTP Virtual Radio Interface is modeled by 500 ifTable [RFC2863]. 502 In ifTable 503 { 504 ifIndex = 10, 505 ifDescr = 'WTP Virtual Radio Interface', 506 ifType = xxx, 507 RFC Editor - please replace xxx with the value 508 allocated by IANA for IANAifType of WTP Virtual Radio Interface 509 ifMtu = 0, 510 ifSpeed = 0, 511 ifPhysAddress = '000000', 512 ifAdminStatus = true(1), 513 ifOperStatus = false(0), 514 ifLastChange = 0, 515 ifInOctets = 0, 516 ifInUcastPkts = 0, 517 ifInDiscards = 0, 518 ifInErrors = 0, 519 ifInUnknownProtos = 0, 520 ifOutOctets = 0, 521 ifOutUcastPkts = 0, 522 ifOutDiscards = 0, 523 ifOutErrors = 0 524 } 526 2) Query the ifIndexes of WTP Virtual Radio Interfaces 528 Before configuring PHY radios, the operator needs to get the 529 ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY 530 radios. 532 As CapwapBaseWirelessBindingTable already stores the mappings between 533 PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio 534 Interfaces, the operator can get the ifIndex information by querying 535 this table. Such a query operation SHOULD run from radio ID 1 to 536 radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex 537 value (0) is returned. 539 This example uses capwapBaseWtpProfileId = 1 and 540 capwapBaseWirelessBindingRadioId = 1 as inputs to query the 541 CapwapBaseWirelessBindingTable, and gets 542 capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses 543 capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, 544 and gets a invalid ifIndex value (0), so the the query operation 545 ends. This method gets not only the ifIndexes of WTP Virtual Radio 546 Interfaces, but also the numbers of PHY radios. Besides checking 547 whether the ifIndex value is valid, the operator SHOULD check whether 548 the capwapBaseWirelessBindingType is the desired binding type. 550 3) Configure specific wireless binding parameters for a WTP Virtual 551 Radio Interface 553 This configuration is made on the AC through a specific wireless 554 binding MIB module such as the IEEE 802.11 MIB module. 556 The following shows an example of configuring parameters for a WTP 557 Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 558 Dot11OperationTable [IEEE.802-11.2007]. 560 In Dot11OperationTable 561 { 562 ifIndex = 10, 563 dot11MACAddress = '000000', 564 dot11RTSThreshold = 2347, 565 dot11ShortRetryLimit = 7, 566 dot11LongRetryLimit = 4, 567 dot11FragmentationThreshold = 256, 568 dot11MaxTransmitMSDULifetime = 512, 569 dot11MaxReceiveLifetime = 512, 570 dot11ManufacturerID = 'capwap', 571 dot11ProductID = 'capwap' 572 } 574 4) Current configuration status report from the WTP to the AC 576 According to [RFC5415], before a WTP that has joined the AC gets 577 configuration from the AC, it needs to report its current 578 configuration status by sending a configuration status request 579 message to the AC, which use the message to update MIB objects on the 580 AC. For example, for IEEE 802.11 binding, the AC updates data in the 581 ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the 582 message. For ifIndex 10, its ifOperStatus in ifTable is updated 583 according to the current radio operational status in the CAPWAP 584 message. 586 5) Query WTP and radio statistics data 588 After WTPs start to run, the operator could query WTP and radio 589 statistics data through CAPWAP-BASE-MIB and specific binding MIB 590 module on the AC. For example, through dot11CountersTable in the 591 IEEE 802.11 MIB module, the operator could query the counter data of 592 a radio using the ifIndex of the corresponding WTP Virtual Radio 593 Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB 594 module, the operator could query the properties of running WTPs. 596 6) MIB operations through a CAPWAP protocol wireless binding MIB 597 module 598 For example, for CAPWAP IEEE 802.11 binding protocol [RFC5416], Some 599 MIB operations such as MAC mode configuration for a WLAN depend on 600 the CAPWAP Protocol Binding MIB for IEEE 802.11 601 [I-D.ietf-capwap-802dot11-mib]. For more information, refer to 602 [I-D.ietf-capwap-802dot11-mib]. 604 7) Query other properties of a WTP 606 The Operator could query MIB objects in the ENTITY-MIB [RFC4133] 607 module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable 608 of CAPWAP-BASE-MIB module. The properties of a WTP such as software 609 version, hardware version are available in the ENTITY-MIB module. 611 9. CAPWAP Message Element Extension 613 This section describes the CAPWAP control message extension for 614 CAPWAP protocol to support CAPWAP-BASE-MIB module. 616 To enable CAPWAP protocol timers and variables [RFC5415] manageable 617 through CAPWAP protocol, the following capwap message element 618 extensions are defined using Vendor Specific Payload message element 619 in this section. These message elements are used by WTP to report 620 extra configuration information to the AC. 622 CAPWAP Message Element Vendor Identifier Element ID 624 CAPWAP Protocol Timers Id assigned by IANA 1 625 CAPWAP Protocol Variables Id assigned by IANA 2 627 9.1. CAPWAP Protocol Timers 629 0 1 2 3 630 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 632 | Vendor Identifier | 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 | Element ID | DataChannelKeepAlive | 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 | DataChannelDeadInterval | DiscoveryInterval | 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 638 | DTLSSessionDelete | EchoInterval | 639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 640 | IdleTimeout | 641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 642 | ImageDataStartTimer | MaxDiscoveryInterval | 643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 644 | ReportInterval | RetransmitInterval | 645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 | SilentInterval | StatisticsTimer | 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 648 | WaitDTLS | 649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 650 Type: 37 for Vendor Specific Payload 652 Length: 34 654 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 655 Network Management Private Enterprise Codes". 657 Element ID: The Element ID field is set to 1 for CAPWAP Protocol 658 Timers. 660 DataChannelKeepAlive: A 16-bit value representing the time, 661 in seconds, that is used by the WTP to determine the next 662 must transmit the Data Channel Keep Alive. (see section 4.7.2 of 663 [RFC5415]). 665 DataChannelDeadInterval: A 16-bit value representing the minimum 666 time, in seconds, a WTP MUST wait without having received a Data 667 Channel Alive packets MAY be considered dead. The value of this 668 timer MUST be no less than 2*DataChannelKeepAlive seconds and 669 no greater that 240 seconds (see section 4.7.3 of [RFC5415]). 671 DiscoveryInterval: A 16-bit value representing the minimum time, in 672 seconds, that a WTP MUST wait after receiving a Discovery Response 673 message, before initiating a DTLS handshake (see section 4.7.5 of 674 [RFC5415]). 676 DTLSSessionDelete: A 16-bit value representing the minimum time, in 677 seconds, a WTP MUST wait for DTLS session deletion (see section 678 4.7.6 of [RFC5415]). 680 EchoInterval: A 16-bit value representing the minimum time, in 681 seconds, between sending Echo Request messages to the AC with 682 which the WTP has joined (see section 4.7.7 of [RFC5415]). 684 IdleTimeout: A 32-bit value representing the idle timeout value that 685 the WTP SHOULD enforce for its active station. The default Idle 686 Timeout is 300 seconds (see section 4.7.8 of [RFC5415]). 688 ImageDataStartTimer: A 16-bit value representing the number of 689 seconds the WTP will wait for its peer to transmit the Image 690 Data Request (see section 4.7.9 of [RFC5415]). 692 MaxDiscoveryInterval: A 16-bit value representing the maximum time 693 allowed between sending Discovery Request messages, in seconds. 695 This value MUST be no less than 2 seconds and no greater than 180 696 seconds (see section 4.7.10 of [RFC5415]). 698 ReportInterval: A 16-bit value representing the time, in seconds, 699 that is used by the WTP to determine the interval the WTP uses 700 between sending the Decryption Error message elements to inform 701 the AC of decryption errors (see section 4.7.11 of [RFC5415]). 703 RetransmitInterval: A 16-bit value representing the minimum time, 704 in seconds, in which a non-acknowledged CAPWAP packet will be 705 retransmitted (see section 4.7.12 of [RFC5415]). 707 SilentInterval: The minimum time, in seconds, a WTP MUST wait before 708 it MAY again send Discovery Request messages or attempt to 709 establish DTLS session (see section 4.7.13 of [RFC5415]). 711 StatisticsTimer: A 16-bit value representing the time, in seconds, 712 that is used by the WTP to determine the interval the WTP uses 713 between the WTP Events Requests it transmits to the AC to 714 communicate its statistics (see section 4.7.14 of [RFC5415]). 716 WaitDTLS: A 16-bit value representing the maximum time, in seconds, 717 a WTP MUST wait without having received a DTLS Handshake message 718 from an AC. This timer MUST be greater than 30 seconds (see 719 section 4.7.15 of [RFC5415]). 721 9.2. CAPWAP Protocol Variables 723 0 1 2 3 724 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 726 | Vendor Identifier | 727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 | Element ID | MaxDiscoveries | 729 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 730 | MaxFailedDTLSSessionRetry | MaxRetransmit | 731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 733 Type: 37 for Vendor Specific Payload 735 Length: 12 737 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 738 Network Management Private Enterprise Codes". 740 Element ID: The Element ID field is set to 2 for CAPWAP Protocol 741 Variables. 743 MaxDiscoveries: A 16-bit value representing the maximum number of 744 Discovery Request messages that will be sent after a WTP boots 745 (see section 4.8.5 of [RFC5415]). 747 MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum 748 number of failed DTLS session establishment attempts before the 749 CAPWAP device enters a silent period (see section 4.8.6 of 750 [RFC5415]). 752 MaxRetransmit: A 16-bit value representing the maximum number of 753 retransmissions for a given CAPWAP packet before the link layer 754 considers the peer dead (see section 4.8.7 of [RFC5415]). 756 9.3. CAPWAP Messages for CAPWAP Control Message Extension 758 For CAPWAP Control Message Extension, the following CAPWAP messages 759 will be used. 761 9.3.1. Configuration Status Response Message 763 The following message elements MAY be included in the CAPWAP 764 Configuration Status Response Message. 766 - CAPWAP Protocol Timers, see Section Section 9.1 768 - CAPWAP Protocol Variables, see Section Section 9.2 770 9.3.2. Configuration Update Response Message 772 The following message elements MAY be included in the CAPWAP 773 Configuration Update Response Message. 775 - CAPWAP Protocol Timers, see Section Section 9.1 777 - CAPWAP Protocol Variables, see Section Section 9.2 779 10. Definitions 781 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 783 IMPORTS 785 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 786 DateAndTime, RowStatus 787 FROM SNMPv2-TC 788 InterfaceIndex 789 FROM IF-MIB 790 PhysicalIndex 791 FROM ENTITY-MIB 792 SnmpAdminString 793 FROM SNMP-FRAMEWORK-MIB 794 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 795 FROM SNMPv2-CONF 796 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 797 Integer32, Unsigned32, Counter32 798 FROM SNMPv2-SMI 799 InetAddressType, InetAddress 800 FROM INET-ADDRESS-MIB; 802 capwapBaseMIB MODULE-IDENTITY 803 LAST-UPDATED "200905290000Z" -- May 29th, 2009 804 ORGANIZATION "IETF Control And Provisioning of Wireless Access 805 Points (CAPWAP) Working Group 806 http://www.ietf.org/html.charters/capwap-charter.html" 807 CONTACT-INFO 808 "General Discussion: capwap@frascone.com 809 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 811 Yang Shi 812 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 813 District,Beijing,China(100085) 814 Email: young@h3c.com 816 David T. Perkins 817 228 Bayview Dr 818 San Carlos, CA 94070 819 USA 820 Phone: +1 408 394-8702 821 Email: dperkins@snmpinfo.com 823 Chris Elliott 824 Cisco Systems, Inc. 825 7025 Kit Creek Rd., P.O. Box 14987 826 Research Triangle Park 27709 827 USA 828 Phone: +1 919-392-2146 829 Email: chelliot@cisco.com 831 Yong Zhang 832 Fortinet, Inc. 833 1090 Kifer Road 834 Sunnyvale, CA 94086 835 USA 836 Email: yzhang@fortinet.com" 838 DESCRIPTION 839 "Copyright (C) 2009 The Internet Society. This version of 840 the MIB module is part of RFC xxx; see the RFC itself 841 for full legal notices. 843 This MIB module contains managed object definitions for 844 the CAPWAP Protocol." 845 REVISION "200905290000Z" 846 DESCRIPTION 847 "Initial version published as RFC xxx" 848 ::= { mib-2 xxx } 850 -- Textual Conventions 852 CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION 853 DISPLAY-HINT "d" 854 STATUS current 855 DESCRIPTION 856 "Represents the unique identifier of a WTP profile." 857 SYNTAX Unsigned32 (0..4096) 859 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 860 DISPLAY-HINT "32a" 861 STATUS current 862 DESCRIPTION 863 "Represents the unique identifier of a WTP instance. 864 As usual, a serial number of WTP is used." 865 SYNTAX OCTET STRING (SIZE (0..32)) 867 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 868 DISPLAY-HINT "1x:" 869 STATUS current 870 DESCRIPTION 871 "Represents the unique identifier of a station instance. 872 As usual, the MAC address of the station is used." 873 SYNTAX OCTET STRING (SIZE (6)) 875 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 876 DISPLAY-HINT "d" 877 STATUS current 878 DESCRIPTION 879 "Represents the unique identifier of a radio on a WTP." 880 SYNTAX Unsigned32 (1..31) 882 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 883 STATUS current 884 DESCRIPTION 885 "Represents the tunneling modes of operation that are 886 supported by a WTP. 887 The WTP MAY support more than one option, represented by 888 the bit field below: 889 localBridging(0) - Local bridging mode 890 dot3Tunnel(1) - 802.3 frame tunnel mode 891 nativeTunnel(2) - Native frame tunnel mode" 892 REFERENCE 893 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 894 SYNTAX BITS { 895 localBridging(0), 896 dot3Tunnel(1), 897 nativeTunnel(2) 898 } 900 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 901 STATUS current 902 DESCRIPTION 903 "Represents the MAC mode of operation supported by a WTP. 904 The following enumerated values are supported: 905 localMAC(0) - Local-MAC mode 906 splitMAC(1) - Split-MAC mode 907 both(2) - Both Local-MAC and Split-MAC" 908 REFERENCE 909 "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." 910 SYNTAX INTEGER { 911 localMAC(0), 912 splitMAC(1), 913 both(2) 914 } 916 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 917 STATUS current 918 DESCRIPTION 919 "Represents the channel type for CAPWAP protocol. 920 The following enumerated values are supported: 921 data(1) - Data channel 922 control(2) - Control channel" 923 SYNTAX INTEGER { 924 data(1), 925 control(2) 926 } 928 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 929 STATUS current 930 DESCRIPTION 931 "Represents the authentication credential type for a WTP. 932 The following enumerated values are supported: 933 other(1) - Other method, for example, vendor specific 934 clear(2) - Clear text and no authentication 935 x509(3) - X.509 certificate authentication 936 psk(4) - Pre-Shared secret authentication 937 As mandatory requirement, CAPWAP control channel 938 authentication SHOULD use DTLS, and either by certificate or 939 PSK. For data channel, DTLS is optional." 940 SYNTAX INTEGER { 941 other(1), 942 clear(2), 943 x509(3), 944 psk(4) 945 } 947 -- Top level components of this MIB module 949 -- Notifications 950 capwapBaseNotifications OBJECT IDENTIFIER 951 ::= { capwapBaseMIB 0 } 952 -- Tables, Scalars 953 capwapBaseObjects OBJECT IDENTIFIER 954 ::= { capwapBaseMIB 1 } 955 -- Conformance 956 capwapBaseConformance OBJECT IDENTIFIER 957 ::= { capwapBaseMIB 2 } 959 -- AC Objects Group 961 capwapBaseAc OBJECT IDENTIFIER 962 ::= { capwapBaseObjects 1 } 964 capwapBaseWtpSessions OBJECT-TYPE 965 SYNTAX Unsigned32 (0..65535) 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "Represents the total number of WTPs which are connecting to 970 the AC." 971 REFERENCE 972 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 973 ::= { capwapBaseAc 1 } 975 capwapBaseWtpSessionsLimit OBJECT-TYPE 976 SYNTAX Unsigned32 (0..65535) 977 MAX-ACCESS read-write 978 STATUS current 979 DESCRIPTION 980 "Represents the maximum number of WTP sessions configured on 981 the AC. 982 The value of the object is persistent at restart/reboot." 983 REFERENCE 984 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 985 ::= { capwapBaseAc 2 } 987 capwapBaseStationSessions OBJECT-TYPE 988 SYNTAX Unsigned32 (0..65535) 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "Represents the total number of stations which are accessing 993 the wireless service provided by the AC." 994 REFERENCE 995 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 996 ::= { capwapBaseAc 3 } 998 capwapBaseStationSessionsLimit OBJECT-TYPE 999 SYNTAX Unsigned32 (0..65535) 1000 MAX-ACCESS read-write 1001 STATUS current 1002 DESCRIPTION 1003 "Represents the maximum number of station sessions configured 1004 on the AC. 1005 The value of the object is persistent at restart/reboot." 1006 REFERENCE 1007 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1008 ::= { capwapBaseAc 4 } 1010 capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE 1011 SYNTAX BITS { 1012 other(0), 1013 clear(1), 1014 dtls(2) 1015 } 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "The AC communicates its policy on the use of DTLS for 1020 CAPWAP data channel. 1021 The AC MAY support more than one option, represented by the bit 1022 field below: 1023 other(0) - Other method, for example, vendor specific 1024 clear(1) - Clear text 1025 dtls(2) - DTLS" 1026 REFERENCE 1027 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1028 ::= { capwapBaseAc 5 } 1030 capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE 1031 SYNTAX INTEGER { 1032 other(0), 1033 clear(1), 1034 dtls(2) 1035 } 1036 MAX-ACCESS read-write 1037 STATUS current 1038 DESCRIPTION 1039 "Represents the security policy configured on the AC for 1040 CAPWAP data channel. 1041 The value of the object is persistent at restart/reboot. 1042 The following enumerated values are supported: 1043 other(0) - Other method, for example, vendor specific 1044 clear(1) - Clear text 1045 dtls(2) - DTLS" 1046 REFERENCE 1047 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1048 ::= { capwapBaseAc 6 } 1050 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 1051 SYNTAX BITS { 1052 x509(0), 1053 psk(1) 1054 } 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "Represents the authentication credential type supported by the 1059 AC for CAPWAP control channel. 1061 The AC MAY support more than one option, represented by the bit 1062 field below: 1063 x509(0) - X.509 certificate based 1064 psk(1) - Pre-Shared secret" 1065 REFERENCE 1066 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1067 ::= { capwapBaseAc 7 } 1069 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 1070 SYNTAX INTEGER { 1071 x509(1), 1072 psk(2) 1073 } 1074 MAX-ACCESS read-write 1075 STATUS current 1076 DESCRIPTION 1077 "Represents the authentication credential type configured on 1078 the AC for CAPWAP control channel. 1079 The value of the object is persistent at restart/reboot. 1080 The following enumerated values are supported: 1081 x509(1) - X.509 certificate based 1082 psk(2) - Pre-Shared secret" 1083 REFERENCE 1084 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1085 ::= { capwapBaseAc 8 } 1087 -- capwapBaseAcNameListTable table 1089 capwapBaseAcNameListTable OBJECT-TYPE 1090 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "A table of objects that configure the AC name list. 1095 Values of all read-create objects in this table are 1096 persistent at restart/reboot." 1097 REFERENCE 1098 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1099 ::= { capwapBaseAc 9 } 1101 capwapBaseAcNameListEntry OBJECT-TYPE 1102 SYNTAX CapwapBaseAcNameListEntry 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "A set of objects that configure the AC name list." 1107 INDEX { capwapBaseAcNameListId } 1108 ::= { capwapBaseAcNameListTable 1 } 1110 CapwapBaseAcNameListEntry ::= SEQUENCE { 1111 capwapBaseAcNameListId Unsigned32, 1112 capwapBaseAcNameListName OCTET STRING, 1113 capwapBaseAcNameListPriority Unsigned32, 1114 capwapBaseAcNameListRowStatus RowStatus 1115 } 1117 capwapBaseAcNameListId OBJECT-TYPE 1118 SYNTAX Unsigned32 (1..255) 1119 MAX-ACCESS not-accessible 1120 STATUS current 1121 DESCRIPTION 1122 "Represents the unique identifier of a AC Name list." 1123 ::= { capwapBaseAcNameListEntry 1 } 1125 capwapBaseAcNameListName OBJECT-TYPE 1126 SYNTAX OCTET STRING(SIZE(512)) 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION 1130 "Represents the name of an AC, and it is expected to be 1131 an UTF-8 encoded string." 1132 REFERENCE 1133 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1134 ::= { capwapBaseAcNameListEntry 2 } 1136 capwapBaseAcNameListPriority OBJECT-TYPE 1137 SYNTAX Unsigned32 (1..255) 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "Represents the priority order of the preferred AC. 1142 For instance, the value of one (1) is used to set the primary 1143 AC, the value of two (2) is used to set the secondary AC, etc." 1144 REFERENCE 1145 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1146 ::= { capwapBaseAcNameListEntry 3 } 1148 capwapBaseAcNameListRowStatus OBJECT-TYPE 1149 SYNTAX RowStatus 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "This variable is used to create, modify, and/or delete a row 1154 in this table." 1155 ::= { capwapBaseAcNameListEntry 4 } 1157 -- End of capwapBaseAcNameListTable table 1158 -- capwapBaseMacAclTable table 1160 capwapBaseMacAclTable OBJECT-TYPE 1161 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 1162 MAX-ACCESS not-accessible 1163 STATUS current 1164 DESCRIPTION 1165 "A table of objects that configure station Access Control 1166 Lists (ACL). 1167 The WTP will not provide service to the MAC addresses 1168 configured in this table. 1169 Values of all read-create objects in this table are persistent 1170 at AC restart/reboot." 1171 REFERENCE 1172 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1173 ::= { capwapBaseAc 10 } 1175 capwapBaseMacAclEntry OBJECT-TYPE 1176 SYNTAX CapwapBaseMacAclEntry 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "A set of objects that configure station Access Control 1181 List (ACL)." 1182 INDEX { capwapBaseMacAclId } 1183 ::= { capwapBaseMacAclTable 1 } 1185 CapwapBaseMacAclEntry ::= SEQUENCE { 1186 capwapBaseMacAclId Unsigned32, 1187 capwapBaseMacAclStationId CapwapBaseStationIdTC, 1188 capwapBaseMacAclRowStatus RowStatus 1189 } 1191 capwapBaseMacAclId OBJECT-TYPE 1192 SYNTAX Unsigned32 (1..255) 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "Represents the unique identifier of an ACL." 1197 ::= { capwapBaseMacAclEntry 1 } 1199 capwapBaseMacAclStationId OBJECT-TYPE 1200 SYNTAX CapwapBaseStationIdTC 1201 MAX-ACCESS read-create 1202 STATUS current 1203 DESCRIPTION 1204 "Represents the MAC address of a station to which WTPs will 1205 no longer provides service." 1207 REFERENCE 1208 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1209 ::= { capwapBaseMacAclEntry 2 } 1211 capwapBaseMacAclRowStatus OBJECT-TYPE 1212 SYNTAX RowStatus 1213 MAX-ACCESS read-create 1214 STATUS current 1215 DESCRIPTION 1216 "This variable is used to create, modify, and/or delete a row 1217 in this table." 1218 ::= { capwapBaseMacAclEntry 3 } 1220 -- End of capwapBaseMacAclTable table 1222 -- End of AC Objects Group 1224 -- WTP Objects Group 1226 capwapBaseWtps OBJECT IDENTIFIER 1227 ::= { capwapBaseObjects 2 } 1229 -- capwapBaseWtpProfileTable Table 1231 capwapBaseWtpProfileTable OBJECT-TYPE 1232 SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "A table of objects that configure WTP profiles for WTPs to 1237 be managed before they connect to the AC. 1238 An operator could change a WTP's configuration by changing 1239 the values of parameters in the corresponding WTP profile. 1240 Values of all read-create objects in this table are 1241 persistent at restart/reboot." 1242 ::= { capwapBaseWtps 1 } 1244 capwapBaseWtpProfileEntry OBJECT-TYPE 1245 SYNTAX CapwapBaseWtpProfileEntry 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "A set of objects that configure and display a WTP profile." 1250 INDEX { capwapBaseWtpProfileId } 1251 ::= { capwapBaseWtpProfileTable 1 } 1253 CapwapBaseWtpProfileEntry ::= SEQUENCE { 1254 capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, 1255 capwapBaseWtpProfileName SnmpAdminString, 1256 capwapBaseWtpProfileWTPSerialId CapwapBaseWtpIdTC, 1257 capwapBaseWtpProfileWTPModelNumber SnmpAdminString, 1258 capwapBaseWtpProfileWtpName OCTET STRING, 1259 capwapBaseWtpProfileWtpLocation OCTET STRING, 1260 capwapBaseWtpProfileWtpStaticIpEnable TruthValue, 1261 capwapBaseWtpProfileWtpStaticIpType InetAddressType, 1262 capwapBaseWtpProfileWtpStaticIp InetAddress, 1263 capwapBaseWtpProfileWtpNetmask InetAddress, 1264 capwapBaseWtpProfileWtpGateway InetAddress, 1265 capwapBaseWtpProfileWtpFallbackEnable INTEGER, 1266 capwapBaseWtpProfileWtpEchoInterval Unsigned32, 1267 capwapBaseWtpProfileWtpIdleTimeout Unsigned32, 1268 capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32, 1269 capwapBaseWtpProfileWtpReportInterval Unsigned32, 1270 capwapBaseWtpProfileWtpSilentInterval Unsigned32, 1271 capwapBaseWtpProfileWtpStatisticsTimer Unsigned32, 1272 capwapBaseWtpProfileWtpWaitDTLSTimer Unsigned32, 1273 capwapBaseWtpProfileWtpEcnSupport INTEGER, 1274 capwapBaseWtpProfileRowStatus RowStatus 1275 } 1277 capwapBaseWtpProfileId OBJECT-TYPE 1278 SYNTAX CapwapBaseWtpProfileIdTC 1279 MAX-ACCESS not-accessible 1280 STATUS current 1281 DESCRIPTION 1282 "Represents the unique identifier of a WTP profile." 1283 ::= { capwapBaseWtpProfileEntry 1 } 1285 capwapBaseWtpProfileName OBJECT-TYPE 1286 SYNTAX SnmpAdminString 1287 MAX-ACCESS read-create 1288 STATUS current 1289 DESCRIPTION 1290 "Represents the name of a WTP profile." 1291 ::= { capwapBaseWtpProfileEntry 2 } 1293 capwapBaseWtpProfileWTPSerialId OBJECT-TYPE 1294 SYNTAX CapwapBaseWtpIdTC 1295 MAX-ACCESS read-create 1296 STATUS current 1297 DESCRIPTION 1298 "Represents the serial identifier of a WTP. 1299 A WTP profile MUST contain the serial number of the WTP 1300 because the CAPWAP message received from the WTP contains 1301 its serial number and the AC uses the serial number to 1302 find the corresponding WTP profile." 1303 REFERENCE 1304 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1305 ::= { capwapBaseWtpProfileEntry 3 } 1307 capwapBaseWtpProfileWTPModelNumber OBJECT-TYPE 1308 SYNTAX SnmpAdminString 1309 MAX-ACCESS read-create 1310 STATUS current 1311 DESCRIPTION 1312 "Represents the model number of a WTP. 1313 A WTP profile MUST include the WTP's model number, which 1314 reflects the number of PHY radios on the WTP. 1315 In this way, the creation of a WTP profile triggers the AC 1316 to automatically create the same number of WTP Virtual Radio 1317 Interfaces corresponding to the WTP's PHY radios without 1318 manual intervention. With the ifIndexes of WTP Virtual 1319 Radio Interfaces, the operator could configure and manage 1320 the WTP's PHY radios through the wireless binding MIB 1321 modules." 1322 REFERENCE 1323 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1324 ::= { capwapBaseWtpProfileEntry 4 } 1326 capwapBaseWtpProfileWtpName OBJECT-TYPE 1327 SYNTAX OCTET STRING(SIZE(512)) 1328 MAX-ACCESS read-create 1329 STATUS current 1330 DESCRIPTION 1331 "Represents the name of the WTP." 1332 REFERENCE 1333 "Section 4.6.45. of CAPWAP Protocol Specification, RFC 5415." 1334 ::= { capwapBaseWtpProfileEntry 5 } 1336 capwapBaseWtpProfileWtpLocation OBJECT-TYPE 1337 SYNTAX OCTET STRING(SIZE(1024)) 1338 MAX-ACCESS read-create 1339 STATUS current 1340 DESCRIPTION 1341 "Represents the location of the WTP." 1342 REFERENCE 1343 "Section 4.6.30. of CAPWAP Protocol Specification, RFC 5415." 1344 ::= { capwapBaseWtpProfileEntry 6 } 1346 capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE 1347 SYNTAX TruthValue 1348 MAX-ACCESS read-create 1349 STATUS current 1350 DESCRIPTION 1351 "Represents whether the WTP SHOULD use a static IP address 1352 or not. A value of false disables the static IP address, 1353 while a value of true enables it." 1354 REFERENCE 1355 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1356 ::= { capwapBaseWtpProfileEntry 7 } 1358 capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE 1359 SYNTAX InetAddressType 1360 MAX-ACCESS read-create 1361 STATUS current 1362 DESCRIPTION 1363 "Represents the static IP address type used by the WTP, IPv4 1364 or IPv6." 1365 ::= { capwapBaseWtpProfileEntry 8 } 1367 capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE 1368 SYNTAX InetAddress 1369 MAX-ACCESS read-create 1370 STATUS current 1371 DESCRIPTION 1372 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1373 it represents the static IP address to be assigned to the WTP." 1374 REFERENCE 1375 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1376 ::= { capwapBaseWtpProfileEntry 9 } 1378 capwapBaseWtpProfileWtpNetmask OBJECT-TYPE 1379 SYNTAX InetAddress 1380 MAX-ACCESS read-create 1381 STATUS current 1382 DESCRIPTION 1383 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1384 it represents the netmask to be assigned to the WTP." 1385 REFERENCE 1386 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1387 ::= { capwapBaseWtpProfileEntry 10 } 1389 capwapBaseWtpProfileWtpGateway OBJECT-TYPE 1390 SYNTAX InetAddress 1391 MAX-ACCESS read-create 1392 STATUS current 1393 DESCRIPTION 1394 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1395 it represents the gateway to be assigned to the WTP." 1396 REFERENCE 1397 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1399 ::= { capwapBaseWtpProfileEntry 11 } 1401 capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE 1402 SYNTAX INTEGER { 1403 enabled(1), 1404 disabled(2) 1405 } 1406 MAX-ACCESS read-create 1407 STATUS current 1408 DESCRIPTION 1409 "Represents whether to enable or disable automatic CAPWAP 1410 fallback in the event that a WTP detects its preferred AC, 1411 and is not currently connected to it. 1412 The following enumerated values are supported: 1413 enabled(1) - The fallback mode is enabled 1414 disabled(2) - The fallback mode is disabled" 1415 REFERENCE 1416 "Section 4.6.42. of CAPWAP Protocol Specification, RFC 5415." 1417 DEFVAL { enabled } 1418 ::= { capwapBaseWtpProfileEntry 12 } 1420 capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE 1421 SYNTAX Unsigned32 1422 UNITS "second" 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "Represents the minimum time, in seconds, between sending Echo 1427 Request messages to the AC that the WTP has joined." 1428 REFERENCE 1429 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 1430 DEFVAL { 30 } 1431 ::= { capwapBaseWtpProfileEntry 13 } 1433 capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE 1434 SYNTAX Unsigned32 1435 UNITS "second" 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "Represents the idle timeout value that the WTP SHOULD enforce 1440 for its active stations." 1441 REFERENCE 1442 "Section 4.7.8. of CAPWAP Protocol Specification, RFC 5415." 1443 DEFVAL { 300 } 1444 ::= { capwapBaseWtpProfileEntry 14 } 1446 capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE 1447 SYNTAX Unsigned32 (2..180) 1448 UNITS "second" 1449 MAX-ACCESS read-create 1450 STATUS current 1451 DESCRIPTION 1452 "Represents the maximum time allowed between sending Discovery 1453 Request messages, in seconds." 1454 REFERENCE 1455 "Section 4.7.10. of CAPWAP Protocol Specification, RFC 5415." 1456 DEFVAL { 20 } 1457 ::= { capwapBaseWtpProfileEntry 15 } 1459 capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE 1460 SYNTAX Unsigned32 1461 UNITS "second" 1462 MAX-ACCESS read-create 1463 STATUS current 1464 DESCRIPTION 1465 "Represents the interval for WTP to send Decryption Error 1466 report." 1467 REFERENCE 1468 "Section 4.7.11. of CAPWAP Protocol Specification, RFC 5415." 1469 DEFVAL { 120 } 1470 ::= { capwapBaseWtpProfileEntry 16 } 1472 capwapBaseWtpProfileWtpSilentInterval OBJECT-TYPE 1473 SYNTAX Unsigned32 1474 UNITS "second" 1475 MAX-ACCESS read-create 1476 STATUS current 1477 DESCRIPTION 1478 "Represents the minimum time, in seconds, a WTP MUST wait 1479 before it MAY again send Discovery Request messages or 1480 attempt to a establish DTLS session." 1481 REFERENCE 1482 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 1483 DEFVAL { 30 } 1484 ::= { capwapBaseWtpProfileEntry 17 } 1486 capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE 1487 SYNTAX Unsigned32 1488 UNITS "second" 1489 MAX-ACCESS read-create 1490 STATUS current 1491 DESCRIPTION 1492 "Represents the interval the WTP uses between the WTP Events 1493 Requests it transmits to the AC to communicate its statistics, 1494 in seconds." 1496 REFERENCE 1497 "Section 4.7.14. of CAPWAP Protocol Specification, RFC 5415." 1498 DEFVAL { 120 } 1499 ::= { capwapBaseWtpProfileEntry 18 } 1501 capwapBaseWtpProfileWtpWaitDTLSTimer OBJECT-TYPE 1502 SYNTAX Unsigned32 (30..4294967295) 1503 UNITS "second" 1504 MAX-ACCESS read-create 1505 STATUS current 1506 DESCRIPTION 1507 "Represents the maximum time, in seconds, an AC MUST wait 1508 without having received a DTLS Handshake message from an AC. 1509 This timer MUST be greater than 30 seconds." 1510 REFERENCE 1511 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 1512 DEFVAL { 60 } 1513 ::= { capwapBaseWtpProfileEntry 19 } 1515 capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE 1516 SYNTAX INTEGER { 1517 limited(0), 1518 fullAndLimited(1) 1519 } 1520 MAX-ACCESS read-create 1521 STATUS current 1522 DESCRIPTION 1523 "Represents the support for the Explicit Congestion Notification 1524 (ECN) bits, as defined in [RFC3168]. 1525 The following enumerated values are supported: 1526 limited(0) - Limited ECN support 1527 fullAndLimited(1) - Full and limited ECN support" 1528 REFERENCE 1529 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 1530 ::= { capwapBaseWtpProfileEntry 20 } 1532 capwapBaseWtpProfileRowStatus OBJECT-TYPE 1533 SYNTAX RowStatus 1534 MAX-ACCESS read-create 1535 STATUS current 1536 DESCRIPTION 1537 "This variable is used to create, modify, and/or delete a row 1538 in this table. 1539 Deleting a WTP profile in use will disconnect the WTP to 1540 the AC. So the network management system SHOULD 1541 ask the operator to confirm such an operation. 1542 When a WTP profile entry is removed from the table, 1543 the corresponding WTP Virtual Radio Interfaces are also 1544 removed from the CapwapBaseWirelessBindingTable and 1545 ifTable [RFC2863]. 1546 Also, the related object instances SHOULD be removed from 1547 the wireless binding MIB modules such as IEEE 802.11 1548 MIB module [IEEE.802-11.2007]." 1549 ::= { capwapBaseWtpProfileEntry 21 } 1551 -- End of capwapBaseWtpProfileTable table 1553 -- capwapBaseWtpStateTable table 1555 capwapBaseWtpStateTable OBJECT-TYPE 1556 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 1557 MAX-ACCESS not-accessible 1558 STATUS current 1559 DESCRIPTION 1560 "A table of objects that indicate each WTP's CAPWAP FSM 1561 state, and helps the operator to query the WTPs' current 1562 configuration." 1563 ::= { capwapBaseWtps 2 } 1565 capwapBaseWtpStateEntry OBJECT-TYPE 1566 SYNTAX CapwapBaseWtpStateEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "A set of objects that display the WTP's CAPWAP FSM state. 1571 Also, the operator could query the current configuration 1572 of a WTP by using the identifier of the corresponding 1573 WTP profile." 1574 INDEX { capwapBaseWtpStateWtpId } 1575 ::= { capwapBaseWtpStateTable 1 } 1577 CapwapBaseWtpStateEntry ::= SEQUENCE { 1578 capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, 1579 capwapBaseWtpStateWtpIpAddressType InetAddressType, 1580 capwapBaseWtpStateWtpIpAddress InetAddress, 1581 capwapBaseWtpStateWtpBaseMacAddress PhysAddress, 1582 capwapBaseWtpState INTEGER, 1583 capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC 1584 } 1586 capwapBaseWtpStateWtpId OBJECT-TYPE 1587 SYNTAX CapwapBaseWtpIdTC 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "Represents the unique identifier of a WTP." 1592 ::= { capwapBaseWtpStateEntry 1 } 1594 capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE 1595 SYNTAX InetAddressType 1596 MAX-ACCESS read-only 1597 STATUS current 1598 DESCRIPTION 1599 "Represents the IP address type of a WTP." 1600 ::= { capwapBaseWtpStateEntry 2 } 1602 capwapBaseWtpStateWtpIpAddress OBJECT-TYPE 1603 SYNTAX InetAddress 1604 MAX-ACCESS read-only 1605 STATUS current 1606 DESCRIPTION 1607 "Represents the IP address of a WTP." 1608 ::= { capwapBaseWtpStateEntry 3 } 1610 capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE 1611 SYNTAX PhysAddress 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Represents the WTP's Base MAC Address, which MAY be 1616 assigned to the primary Ethernet interface." 1617 REFERENCE 1618 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1619 ::= { capwapBaseWtpStateEntry 4 } 1621 capwapBaseWtpState OBJECT-TYPE 1622 SYNTAX INTEGER { 1623 dtls(1), 1624 join(2), 1625 image(3), 1626 configure(4), 1627 dataCheck(5), 1628 run(6), 1629 reset(7), 1630 dtlsTeardown(8), 1631 unknown(9) 1632 } 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Represents the various possible CAPWAP FSM states of WTP 1637 The following enumerated values are supported: 1638 dtls(1) - DTLS negotiation states, which include 1639 DTLS setup, authorize, DTLS connect 1640 join(2) - The WTP is joining with the AC 1641 image(3) - The WTP is downloading software 1642 configure(4) - The WTP is getting configuration from 1643 the AC 1644 dataCheck(5) - The AC is waiting for the Data Channel Keep 1645 Alive Packet 1646 run(6) - The WTP enters the running state 1647 reset(7) - The AC transmits a reset request message 1648 to the WTP 1649 dtlsTeardown(8) - DTLS session is tear down 1650 unknown(9) - Operator already prepared configuration 1651 for the WTP, while the WTP has not contact 1652 with the AC till now" 1653 REFERENCE 1654 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 1655 ::= { capwapBaseWtpStateEntry 5 } 1657 capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE 1658 SYNTAX CapwapBaseWtpProfileIdTC 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 "Represents the current identifier of a WTP profile. 1663 The operator could query a WTP's current configuration 1664 with the identifier of a WTP profile." 1665 ::= { capwapBaseWtpStateEntry 6 } 1667 -- End of capwapBaseWtpStateTable Table 1669 -- capwapBaseWtpTable Table 1671 capwapBaseWtpTable OBJECT-TYPE 1672 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1673 MAX-ACCESS not-accessible 1674 STATUS current 1675 DESCRIPTION 1676 "A table of objects that display properties of the WTPs 1677 in running state." 1678 ::= { capwapBaseWtps 3 } 1680 capwapBaseWtpEntry OBJECT-TYPE 1681 SYNTAX CapwapBaseWtpEntry 1682 MAX-ACCESS not-accessible 1683 STATUS current 1684 DESCRIPTION 1685 "A set of objects that display properties of the WTPs 1686 in running state." 1687 INDEX { capwapBaseWtpCurrId } 1688 ::= { capwapBaseWtpTable 1 } 1690 CapwapBaseWtpEntry ::= SEQUENCE { 1691 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1692 capwapBaseWtpPhyIndex PhysicalIndex, 1693 capwapBaseWtpBaseMacAddress PhysAddress, 1694 capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, 1695 capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, 1696 capwapBaseWtpDiscoveryType INTEGER, 1697 capwapBaseWtpRadiosInUseNum Unsigned32, 1698 capwapBaseWtpRadioNumLimit Unsigned32, 1699 capwapBaseWtpRetransmitCount Counter32, 1700 capwapBaseWtpMaxDiscoveries Unsigned32, 1701 capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, 1702 capwapBaseWtpMaxRetransmit Unsigned32, 1703 capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, 1704 capwapBaseWtpDataChannelDeadInterval Unsigned32, 1705 capwapBaseWtpDiscoveryInterval Unsigned32, 1706 capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, 1707 capwapBaseWtpImageDataStartTimer Unsigned32, 1708 capwapBaseWtpRetransmitInterval Unsigned32 1709 } 1711 capwapBaseWtpCurrId OBJECT-TYPE 1712 SYNTAX CapwapBaseWtpIdTC 1713 MAX-ACCESS not-accessible 1714 STATUS current 1715 DESCRIPTION 1716 "Represents the unique identifier of a WTP in running state." 1717 ::= { capwapBaseWtpEntry 1 } 1719 capwapBaseWtpPhyIndex OBJECT-TYPE 1720 SYNTAX PhysicalIndex 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "Represents the unique physical index of a physical entity 1725 in the ENTITY-MIB module [RFC4133]. 1726 The information such as software version of a specific WTP 1727 could be accessed through the index." 1728 ::= { capwapBaseWtpEntry 2 } 1730 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1731 SYNTAX PhysAddress 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Represents the WTP's Base MAC Address, which MAY be assigned 1736 to the primary Ethernet interface." 1737 REFERENCE 1738 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1739 ::= { capwapBaseWtpEntry 3 } 1741 capwapBaseWtpTunnelModeOptions OBJECT-TYPE 1742 SYNTAX CapwapBaseTunnelModeTC 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "Represents the tunneling modes of operation supported by 1747 the WTP." 1748 REFERENCE 1749 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 1750 ::= { capwapBaseWtpEntry 4 } 1752 capwapBaseWtpMacTypeOptions OBJECT-TYPE 1753 SYNTAX CapwapBaseMacTypeTC 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "Represents the MAC mode of operation supported by the WTP." 1758 REFERENCE 1759 "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." 1760 ::= { capwapBaseWtpEntry 5 } 1762 capwapBaseWtpDiscoveryType OBJECT-TYPE 1763 SYNTAX INTEGER { 1764 unknown(0), 1765 staticConfig(1), 1766 dhcp(2), 1767 dns(3), 1768 acRef(4) 1769 } 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "Represents how the WTP discovers the AC. 1774 The following enumerated values are supported: 1775 unknown(0) - Unknown 1776 staticConfig(1) - Static configuration 1777 dhcp(2) - DHCP 1778 dns(3) - DNS 1779 acRef(4) - AC referral" 1780 REFERENCE 1781 "Section 4.6.21. of CAPWAP Protocol Specification, RFC 5415." 1783 ::= { capwapBaseWtpEntry 6 } 1785 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1786 SYNTAX Unsigned32 (0..255) 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "Represents the number of radios in use on the WTP." 1791 REFERENCE 1792 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1793 ::= { capwapBaseWtpEntry 7 } 1795 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1796 SYNTAX Unsigned32 (0..255) 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "Represents the maximum radio number supported by the WTP." 1801 REFERENCE 1802 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1803 ::= { capwapBaseWtpEntry 8 } 1805 capwapBaseWtpRetransmitCount OBJECT-TYPE 1806 SYNTAX Counter32 1807 UNITS "retransmissions" 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "Represents the number of retransmissions for a given 1812 CAPWAP packet." 1813 REFERENCE 1814 "Section 4.8.8. of CAPWAP Protocol Specification, RFC 5415." 1815 ::= { capwapBaseWtpEntry 9 } 1817 capwapBaseWtpMaxDiscoveries OBJECT-TYPE 1818 SYNTAX Unsigned32 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "Represents the maximum number of Discovery Request messages 1823 that will be sent after a WTP boots." 1824 REFERENCE 1825 "Section 4.8.5. of CAPWAP Protocol Specification, RFC 5415." 1826 DEFVAL { 10 } 1827 ::= { capwapBaseWtpEntry 10 } 1829 capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE 1830 SYNTAX Unsigned32 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "Represents the maximum number of failed DTLS session 1835 establishment attempts before the CAPWAP device enters a 1836 silent period." 1837 REFERENCE 1838 "Section 4.8.6. of CAPWAP Protocol Specification, RFC 5415." 1839 DEFVAL { 3 } 1840 ::= { capwapBaseWtpEntry 11 } 1842 capwapBaseWtpMaxRetransmit OBJECT-TYPE 1843 SYNTAX Unsigned32 1844 MAX-ACCESS read-only 1845 STATUS current 1846 DESCRIPTION 1847 "Represents the maximum number of retransmission for a given 1848 CAPWAP packet before the link layer considers the peer dead." 1849 REFERENCE 1850 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 1851 DEFVAL { 5 } 1852 ::= { capwapBaseWtpEntry 12 } 1854 capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE 1855 SYNTAX Unsigned32 1856 UNITS "second" 1857 MAX-ACCESS read-only 1858 STATUS current 1859 DESCRIPTION 1860 "Represents the next opportunity, in seconds, the WTP must 1861 transmit the Data Channel Keep Alive message." 1862 REFERENCE 1863 "Section 4.7.2. of CAPWAP Protocol Specification, RFC 5415." 1864 DEFVAL { 30 } 1865 ::= { capwapBaseWtpEntry 13 } 1867 capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE 1868 SYNTAX Unsigned32 (0..240) 1869 UNITS "second" 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "Represents the minimum time, in seconds, a WTP MUST wait 1874 without having received a Data Channel Keep Alive packet 1875 before the destination for the Data Channel Keep Alive 1876 packets MAY be considered dead." 1877 REFERENCE 1878 "Section 4.7.3. of CAPWAP Protocol Specification, RFC 5415." 1880 DEFVAL { 60 } 1881 ::= { capwapBaseWtpEntry 14 } 1883 capwapBaseWtpDiscoveryInterval OBJECT-TYPE 1884 SYNTAX Unsigned32 1885 UNITS "second" 1886 MAX-ACCESS read-only 1887 STATUS current 1888 DESCRIPTION 1889 "Represents the minimum time, in seconds, that a WTP MUST 1890 wait after receiving a Discovery Response message, before 1891 initiating a DTLS handshake." 1892 REFERENCE 1893 "Section 4.7.5. of CAPWAP Protocol Specification, RFC 5415." 1894 DEFVAL { 5 } 1895 ::= { capwapBaseWtpEntry 15 } 1897 capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE 1898 SYNTAX Unsigned32 1899 UNITS "second" 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "Represents the minimum time, in seconds, a WTP MUST wait 1904 for DTLS session deletion." 1905 REFERENCE 1906 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 1907 DEFVAL { 5 } 1908 ::= { capwapBaseWtpEntry 16 } 1910 capwapBaseWtpImageDataStartTimer OBJECT-TYPE 1911 SYNTAX Unsigned32 1912 UNITS "second" 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "Represents the number of seconds the WTP will wait for its 1917 peer to transmit the Image Data Request." 1918 REFERENCE 1919 "Section 4.7.9. of CAPWAP Protocol Specification, RFC 5415." 1920 DEFVAL { 30 } 1921 ::= { capwapBaseWtpEntry 17 } 1923 capwapBaseWtpRetransmitInterval OBJECT-TYPE 1924 SYNTAX Unsigned32 1925 UNITS "second" 1926 MAX-ACCESS read-only 1927 STATUS current 1928 DESCRIPTION 1929 "Represents the minimum time, in seconds, in which a 1930 non-acknowledged CAPWAP packet will be retransmitted." 1931 REFERENCE 1932 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 1933 DEFVAL { 3 } 1934 ::= { capwapBaseWtpEntry 18 } 1936 -- End of capwapBaseWtpTable table 1938 -- capwapBaseWirelessBindingTable Table 1940 capwapBaseWirelessBindingTable OBJECT-TYPE 1941 SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry 1942 MAX-ACCESS not-accessible 1943 STATUS current 1944 DESCRIPTION 1945 "A table of objects that display the mappings between 1946 WTP Virtual Radio Interfaces and PHY radios, and the 1947 wireless binding type for each PHY radio. 1948 Values of all objects in this table are persistent at 1949 restart/reboot." 1950 ::= { capwapBaseWtps 4 } 1952 capwapBaseWirelessBindingEntry OBJECT-TYPE 1953 SYNTAX CapwapBaseWirelessBindingEntry 1954 MAX-ACCESS not-accessible 1955 STATUS current 1956 DESCRIPTION 1957 "A set of objects that display the mapping between 1958 a specific WTP Virtual Radio Interface and a PHY 1959 radio, and the wireless binding type for the PHY radio." 1960 INDEX { 1961 capwapBaseWtpProfileId, 1962 capwapBaseWirelessBindingRadioId 1963 } 1964 ::= { capwapBaseWirelessBindingTable 1 } 1966 CapwapBaseWirelessBindingEntry ::= SEQUENCE { 1967 capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, 1968 capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, 1969 capwapBaseWirelessBindingType INTEGER 1970 } 1972 capwapBaseWirelessBindingRadioId OBJECT-TYPE 1973 SYNTAX CapwapBaseRadioIdTC 1974 MAX-ACCESS not-accessible 1975 STATUS current 1976 DESCRIPTION 1977 "Represents the identifier of a PHY radio on a WTP, which 1978 is required to be unique on a WTP. 1979 For example, WTP A and WTP B use a same value of 1980 capwapBaseWirelessBindingRadioId for their first radio." 1981 REFERENCE 1982 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 1983 ::= { capwapBaseWirelessBindingEntry 1 } 1985 capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE 1986 SYNTAX InterfaceIndex 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "Represents the index value that uniquely identifies a 1991 WLAN Virtual Radio Interface. The interface identified by 1992 a particular value of this index is the same interface as 1993 identified by the same value of the ifIndex. 1994 Before WTPs contact the AC to get configuration, 1995 the operator configures WTP profiles for them. 1996 The creation of a WTP profile triggers system to automatically 1997 create a specific number of WTP Virtual Radio Interfaces and 1998 add a new row object in the capwapBaseWirelessBindingTable 1999 without manual intervention. 2000 As most MIB modules use the ifIndex to identify an interface 2001 for configuration and statistic data, for example, IEEE 802.11 2002 MIB module [IEEE.802-11.2007] 2003 It will be easy to reuse other wireless binding MIB modules 2004 through the WTP Virtual Radio Interface in the Centralized 2005 WLAN Architecture." 2006 ::= { capwapBaseWirelessBindingEntry 2 } 2008 capwapBaseWirelessBindingType OBJECT-TYPE 2009 SYNTAX INTEGER { 2010 dot11(1), 2011 epc(3) 2012 } 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "Represents the wireless binding type for the radio. 2017 The following enumerated values are supported: 2018 dot11(1) - IEEE 802.11 2019 epc(3) - EPCGlobal" 2020 REFERENCE 2021 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2022 ::= { capwapBaseWirelessBindingEntry 3 } 2024 -- End of capwapBaseWirelessBindingTable Table 2026 -- capwapBaseStationTable Table 2028 capwapBaseStationTable OBJECT-TYPE 2029 SYNTAX SEQUENCE OF CapwapBaseStationEntry 2030 MAX-ACCESS not-accessible 2031 STATUS current 2032 DESCRIPTION 2033 "A table of objects that display stations which are accessing 2034 the wireless service provided by the AC." 2035 REFERENCE 2036 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2037 ::= { capwapBaseWtps 5 } 2039 capwapBaseStationEntry OBJECT-TYPE 2040 SYNTAX CapwapBaseStationEntry 2041 MAX-ACCESS not-accessible 2042 STATUS current 2043 DESCRIPTION 2044 "A set of objects that display a station which is 2045 associated with the specific radio on the WTP." 2046 INDEX { 2047 capwapBaseWtpCurrId, 2048 capwapBaseWirelessBindingRadioId, 2049 capwapBaseStationId 2050 } 2051 ::= { capwapBaseStationTable 1 } 2053 CapwapBaseStationEntry ::= SEQUENCE { 2054 capwapBaseStationId CapwapBaseStationIdTC, 2055 capwapBaseStationAddedTime DateAndTime, 2056 capwapBaseStationVlanName SnmpAdminString 2057 } 2059 capwapBaseStationId OBJECT-TYPE 2060 SYNTAX CapwapBaseStationIdTC 2061 MAX-ACCESS not-accessible 2062 STATUS current 2063 DESCRIPTION 2064 "Represents the unique identifier of the station." 2065 REFERENCE 2066 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2067 ::= { capwapBaseStationEntry 1 } 2069 capwapBaseStationAddedTime OBJECT-TYPE 2070 SYNTAX DateAndTime 2071 MAX-ACCESS read-only 2072 STATUS current 2073 DESCRIPTION 2074 "Represents the time when the station is added." 2075 REFERENCE 2076 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2077 ::= { capwapBaseStationEntry 2 } 2079 capwapBaseStationVlanName OBJECT-TYPE 2080 SYNTAX SnmpAdminString (SIZE (0..32)) 2081 MAX-ACCESS read-only 2082 STATUS current 2083 DESCRIPTION 2084 "Represents VLAN name to which the station is associated." 2085 REFERENCE 2086 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2087 ::= { capwapBaseStationEntry 3 } 2089 -- End of capwapBaseStationTable Table 2091 -- capwapBaseWtpEventsStatsTable 2093 capwapBaseWtpEventsStatsTable OBJECT-TYPE 2094 SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry 2095 MAX-ACCESS not-accessible 2096 STATUS current 2097 DESCRIPTION 2098 "A table of objects that display the WTPs' events statistics." 2099 REFERENCE 2100 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2101 ::= { capwapBaseWtps 6 } 2103 capwapBaseWtpEventsStatsEntry OBJECT-TYPE 2104 SYNTAX CapwapBaseWtpEventsStatsEntry 2105 MAX-ACCESS not-accessible 2106 STATUS current 2107 DESCRIPTION 2108 "A set of objects that display the events statistic data 2109 of a WTP." 2110 REFERENCE 2111 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2112 INDEX { capwapBaseWtpCurrId } 2113 ::= { capwapBaseWtpEventsStatsTable 1 } 2115 CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { 2116 capwapBaseWtpEventsStatsRebootCount Counter32, 2117 capwapBaseWtpEventsStatsInitCount Counter32, 2118 capwapBaseWtpEventsStatsLinkFailureCount Counter32, 2119 capwapBaseWtpEventsStatsSwFailureCount Counter32, 2120 capwapBaseWtpEventsStatsHwFailureCount Counter32, 2121 capwapBaseWtpEventsStatsOtherFailureCount Counter32, 2122 capwapBaseWtpEventsStatsUnknownFailureCount Counter32, 2123 capwapBaseWtpEventsStatsLastFailureType INTEGER 2124 } 2126 capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE 2127 SYNTAX Counter32 2128 MAX-ACCESS read-only 2129 STATUS current 2130 DESCRIPTION 2131 "Represents the number of reboots that have occurred due to a 2132 WTP crash. A value of 65535 implies that this information is 2133 not available on the WTP." 2134 REFERENCE 2135 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2136 ::= { capwapBaseWtpEventsStatsEntry 1 } 2138 capwapBaseWtpEventsStatsInitCount OBJECT-TYPE 2139 SYNTAX Counter32 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "Represents the number of reboots that have occurred at the 2144 request of a CAPWAP protocol message, such as a change in 2145 configuration that requires a reboot or an explicit CAPWAP 2146 protocol reset request. A value of 65535 implies that this 2147 information is not available on the WTP." 2148 REFERENCE 2149 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2150 ::= { capwapBaseWtpEventsStatsEntry 2 } 2152 capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE 2153 SYNTAX Counter32 2154 MAX-ACCESS read-only 2155 STATUS current 2156 DESCRIPTION 2157 "Represents the number of times that a CAPWAP protocol 2158 connection with an AC has failed due to link failures." 2159 REFERENCE 2160 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2161 ::= { capwapBaseWtpEventsStatsEntry 3 } 2163 capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE 2164 SYNTAX Counter32 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "Represents the number of times that a CAPWAP protocol 2169 connection with an AC has failed due to software related 2170 reasons." 2171 REFERENCE 2172 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2173 ::= { capwapBaseWtpEventsStatsEntry 4 } 2175 capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE 2176 SYNTAX Counter32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "Represents the number of times that a CAPWAP protocol 2181 connection with an AC has failed due to hardware related 2182 reasons." 2183 REFERENCE 2184 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2185 ::= { capwapBaseWtpEventsStatsEntry 5 } 2187 capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE 2188 SYNTAX Counter32 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "Represents the number of times that a CAPWAP protocol 2193 connection with an AC has failed due to known reasons, other 2194 than the AC initiated, link, software or hardware failures." 2195 REFERENCE 2196 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2197 ::= { capwapBaseWtpEventsStatsEntry 6 } 2199 capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE 2200 SYNTAX Counter32 2201 MAX-ACCESS read-only 2202 STATUS current 2203 DESCRIPTION 2204 "Represents the number of times that a CAPWAP protocol 2205 connection with an AC has failed for unknown reasons." 2206 REFERENCE 2207 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2208 ::= { capwapBaseWtpEventsStatsEntry 7 } 2210 capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE 2211 SYNTAX INTEGER { 2212 notSupport(0), 2213 acInit(1), 2214 linkFailure(2), 2215 swFailure(3), 2216 hwFailure(4), 2217 otherFailure(5), 2218 unknown(255) 2219 } 2220 MAX-ACCESS read-only 2221 STATUS current 2222 DESCRIPTION 2223 "Represents the failure type of the most recent WTP failure. 2224 The following enumerated values are supported: 2225 notSupport(0) - Not supported 2226 acInit(1) - The AC initiated 2227 linkFailure(2) - Link failure 2228 swFailure(3) - Software failure 2229 hwFailure(4) - Hardware failure 2230 otherFailure(5) - Other failure 2231 unknown(255) - Unknown (e.g., WTP doesn't keep track 2232 of info)" 2233 REFERENCE 2234 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2235 ::= { capwapBaseWtpEventsStatsEntry 8 } 2237 -- End of capwapBaseWtpEventsStatsTable table 2239 -- capwapBaseRadioEventsStatsTable table 2241 capwapBaseRadioEventsStatsTable OBJECT-TYPE 2242 SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry 2243 MAX-ACCESS not-accessible 2244 STATUS current 2245 DESCRIPTION 2246 "A table of objects that display statistics on radios behavior, 2247 and reasons why the WTP radio has been reset." 2248 REFERENCE 2249 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2250 ::= { capwapBaseWtps 7 } 2252 capwapBaseRadioEventsStatsEntry OBJECT-TYPE 2253 SYNTAX CapwapBaseRadioEventsStatsEntry 2254 MAX-ACCESS not-accessible 2255 STATUS current 2256 DESCRIPTION 2257 "A set of objects that display the statistic data of 2258 events happened on a specific radio of a WTP." 2259 INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId } 2260 ::= { capwapBaseRadioEventsStatsTable 1 } 2262 CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { 2263 capwapBaseRadioEventsStatsResetCount Counter32, 2264 capwapBaseRadioEventsStatsSwFailCount Counter32, 2265 capwapBaseRadioEventsStatsHwFailCount Counter32, 2266 capwapBaseRadioEventsStatsOtherFailCount Counter32, 2267 capwapBaseRadioEventsStatsUnknownFailCount Counter32, 2268 capwapBaseRadioEventsStatsConfigUpdateCount Counter32, 2269 capwapBaseRadioEventsStatsChannelChangeCount Counter32, 2270 capwapBaseRadioEventsStatsBandChangeCount Counter32, 2271 capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, 2272 capwapBaseRadioEventsStatsDecryptErrorCount Counter32, 2273 capwapBaseRadioEventsStatsLastFailType INTEGER 2274 } 2276 capwapBaseRadioEventsStatsResetCount OBJECT-TYPE 2277 SYNTAX Counter32 2278 MAX-ACCESS read-only 2279 STATUS current 2280 DESCRIPTION 2281 "Represents the number of times that that the radio has been 2282 reset." 2283 REFERENCE 2284 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2285 ::= { capwapBaseRadioEventsStatsEntry 1 } 2287 capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE 2288 SYNTAX Counter32 2289 MAX-ACCESS read-only 2290 STATUS current 2291 DESCRIPTION 2292 "Represents the number of times that the radio has failed due 2293 to software related reasons." 2294 REFERENCE 2295 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2296 ::= { capwapBaseRadioEventsStatsEntry 2 } 2298 capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE 2299 SYNTAX Counter32 2300 MAX-ACCESS read-only 2301 STATUS current 2302 DESCRIPTION 2303 "Represents the number of times that the radio has failed due 2304 to hardware related reasons." 2305 REFERENCE 2306 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2307 ::= { capwapBaseRadioEventsStatsEntry 3 } 2309 capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE 2310 SYNTAX Counter32 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "Represents the number of times that the radio has failed due to 2315 known reasons, other than software or hardware failure." 2316 REFERENCE 2317 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2318 ::= { capwapBaseRadioEventsStatsEntry 4 } 2320 capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE 2321 SYNTAX Counter32 2322 MAX-ACCESS read-only 2323 STATUS current 2324 DESCRIPTION 2325 "Represents the number of times that the radio has failed for 2326 unknown reasons." 2327 REFERENCE 2328 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2329 ::= { capwapBaseRadioEventsStatsEntry 5 } 2331 capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE 2332 SYNTAX Counter32 2333 MAX-ACCESS read-only 2334 STATUS current 2335 DESCRIPTION 2336 "Represents the number of times that the radio configuration has 2337 been updated." 2338 REFERENCE 2339 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2340 ::= { capwapBaseRadioEventsStatsEntry 6 } 2342 capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE 2343 SYNTAX Counter32 2344 MAX-ACCESS read-only 2345 STATUS current 2346 DESCRIPTION 2347 "Represents the number of times that the radio channel has 2348 been changed." 2349 REFERENCE 2350 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2351 ::= { capwapBaseRadioEventsStatsEntry 7 } 2353 capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE 2354 SYNTAX Counter32 2355 MAX-ACCESS read-only 2356 STATUS current 2357 DESCRIPTION 2358 "Represents the number of times that the radio has changed 2359 frequency bands." 2360 REFERENCE 2361 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2362 ::= { capwapBaseRadioEventsStatsEntry 8 } 2364 capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE 2365 SYNTAX Integer32 2366 UNITS "dBm" 2367 MAX-ACCESS read-only 2368 STATUS current 2369 DESCRIPTION 2370 "Represents the noise floor of the radio receiver in units of 2371 dBm." 2372 REFERENCE 2373 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2374 ::= { capwapBaseRadioEventsStatsEntry 9 } 2376 capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE 2377 SYNTAX Counter32 2378 MAX-ACCESS read-only 2379 STATUS current 2380 DESCRIPTION 2381 "Represents the number of decryption errors that have occurred 2382 on the WTP. Note that this field is only valid in cases where 2383 the WTP provides encryption/decryption services." 2384 REFERENCE 2385 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2386 ::= { capwapBaseRadioEventsStatsEntry 10 } 2388 capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE 2389 SYNTAX INTEGER { 2390 notSupport(0), 2391 swFailure(1), 2392 hwFailure(2), 2393 otherFailure(3), 2394 unknown(255) 2395 } 2396 MAX-ACCESS read-only 2397 STATUS current 2398 DESCRIPTION 2399 "Represents the failure type of the most recent radio failure. 2400 The following enumerated values are supported: 2401 notSupport(0) - Not supported 2402 swFailure(1) - Software failure 2403 hwFailure(2) - Hardware failure 2404 otherFailure(3) - Other failure 2405 unknown(255) - Unknown" 2407 REFERENCE 2408 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2409 ::= { capwapBaseRadioEventsStatsEntry 11 } 2411 -- End of capwapBaseRadioEventsStatsTable table 2413 -- End of WTP Objects Group 2415 -- CAPWAP Base Parameters Group 2417 capwapBaseParameters OBJECT IDENTIFIER 2418 ::= { capwapBaseObjects 3 } 2420 capwapBaseAcMaxRetransmit OBJECT-TYPE 2421 SYNTAX Unsigned32 2422 MAX-ACCESS read-write 2423 STATUS current 2424 DESCRIPTION 2425 "Represents the maximum number of retransmissions for a given 2426 CAPWAP packet before the link layer considers the peer dead. 2427 The value of the object is persistent at restart/reboot." 2428 REFERENCE 2429 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 2430 DEFVAL { 5 } 2431 ::= { capwapBaseParameters 1 } 2433 capwapBaseAcChangeStatePendingTimer OBJECT-TYPE 2434 SYNTAX Unsigned32 2435 UNITS "second" 2436 MAX-ACCESS read-write 2437 STATUS current 2438 DESCRIPTION 2439 "Represents the maximum time, in seconds, the AC will wait 2440 for the Change State Event Request from the WTP after having 2441 transmitted a successful Configuration Status Response 2442 message. 2443 The value of the object is persistent at restart/reboot." 2444 REFERENCE 2445 "Section 4.7.1. of CAPWAP Protocol Specification, RFC 5415." 2446 DEFVAL { 25 } 2447 ::= { capwapBaseParameters 2 } 2449 capwapBaseAcDataCheckTimer OBJECT-TYPE 2450 SYNTAX Unsigned32 2451 UNITS "second" 2452 MAX-ACCESS read-write 2453 STATUS current 2454 DESCRIPTION 2455 "Represents The number of seconds the AC will wait for 2456 the Data Channel Keep Alive, which is required by the 2457 CAPWAP state machine's Data Check state. 2458 The AC resets the state machine if this timer expires 2459 prior to transitioning to the next state. 2460 The value of the object is persistent at restart/reboot." 2461 REFERENCE 2462 "Section 4.7.4. of CAPWAP Protocol Specification, RFC 5415." 2463 DEFVAL { 30 } 2464 ::= { capwapBaseParameters 3 } 2466 capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE 2467 SYNTAX Unsigned32 2468 UNITS "second" 2469 MAX-ACCESS read-write 2470 STATUS current 2471 DESCRIPTION 2472 "Represents the minimum time, in seconds, the AC MUST wait 2473 for DTLS session deletion. 2474 The value of the object is persistent at restart/reboot." 2475 REFERENCE 2476 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 2477 DEFVAL { 5 } 2478 ::= { capwapBaseParameters 4 } 2480 capwapBaseAcEchoInterval OBJECT-TYPE 2481 SYNTAX Unsigned32 2482 UNITS "second" 2483 MAX-ACCESS read-write 2484 STATUS current 2485 DESCRIPTION 2486 "Represents the minimum time, in seconds, between sending Echo 2487 Request messages to the AC with which the WTP has joined. 2488 The value of the object is persistent at restart/reboot." 2489 REFERENCE 2490 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 2491 DEFVAL { 30 } 2492 ::= { capwapBaseParameters 5 } 2494 capwapBaseAcRetransmitInterval OBJECT-TYPE 2495 SYNTAX Unsigned32 2496 UNITS "second" 2497 MAX-ACCESS read-write 2498 STATUS current 2499 DESCRIPTION 2500 "Represents the minimum time, in seconds, in which a 2501 non-acknowledged CAPWAP packet will be retransmitted. 2503 The value of the object is persistent at restart/reboot." 2504 REFERENCE 2505 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 2506 DEFVAL { 3 } 2507 ::= { capwapBaseParameters 6 } 2509 capwapBaseAcSilentInterval OBJECT-TYPE 2510 SYNTAX Unsigned32 2511 UNITS "second" 2512 MAX-ACCESS read-write 2513 STATUS current 2514 DESCRIPTION 2515 "Represents the minimum time, in seconds, during which the AC 2516 SHOULD ignore all CAPWAP and DTLS packets received from the 2517 WTP that is in the Sulking state. 2518 The value of the object is persistent at restart/reboot." 2519 REFERENCE 2520 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 2521 DEFVAL { 30 } 2522 ::= { capwapBaseParameters 7 } 2524 capwapBaseAcWaitDTLSTimer OBJECT-TYPE 2525 SYNTAX Unsigned32 (30..4294967295) 2526 UNITS "second" 2527 MAX-ACCESS read-write 2528 STATUS current 2529 DESCRIPTION 2530 "Represents the maximum time, in seconds, the AC MUST wait 2531 without having received a DTLS Handshake message from an AC. 2532 This timer MUST be greater than 30 seconds. 2533 The value of the object is persistent at restart/reboot." 2534 REFERENCE 2535 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 2536 DEFVAL { 60 } 2537 ::= { capwapBaseParameters 8 } 2539 capwapBaseAcWaitJoinTimer OBJECT-TYPE 2540 SYNTAX Unsigned32 (20..4294967295) 2541 UNITS "second" 2542 MAX-ACCESS read-write 2543 STATUS current 2544 DESCRIPTION 2545 "Represents the maximum time, in seconds, the AC will wait 2546 after the DTLS session has been established until it receives 2547 the Join Request from the WTP. This timer MUST be greater 2548 than 20 seconds. 2549 The value of the object is persistent at restart/reboot." 2550 REFERENCE 2551 "Section 4.7.16. of CAPWAP Protocol Specification, RFC 5415." 2552 DEFVAL { 60 } 2553 ::= { capwapBaseParameters 9 } 2555 capwapBaseAcEcnSupport OBJECT-TYPE 2556 SYNTAX INTEGER { 2557 limited(0), 2558 fullAndLimited(1) 2559 } 2560 MAX-ACCESS read-write 2561 STATUS current 2562 DESCRIPTION 2563 "Represents the support for the Explicit Congestion Notification 2564 (ECN) bits, as defined in [RFC3168]. 2565 The value of the object is persistent at restart/reboot. 2566 The following enumerated values are supported: 2567 limited(0) - Limited ECN support 2568 fullAndLimited(1) - Full and limited ECN support" 2569 REFERENCE 2570 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 2571 ::= { capwapBaseParameters 10 } 2573 -- End of CAPWAP Base Parameters Group 2575 -- CAPWAP Statistics Group 2577 capwapBaseStats OBJECT IDENTIFIER 2578 ::= { capwapBaseObjects 4 } 2580 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 2581 SYNTAX Counter32 2582 MAX-ACCESS read-only 2583 STATUS current 2584 DESCRIPTION 2585 "Represents the number of failed DTLS session establishment 2586 attempts due to authentication failures." 2587 REFERENCE 2588 "Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415." 2589 ::= { capwapBaseStats 1 } 2591 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 2592 SYNTAX Counter32 2593 MAX-ACCESS read-only 2594 STATUS current 2595 DESCRIPTION 2596 "Represents the number of failed DTLS session 2597 establishment attempts." 2599 REFERENCE 2600 "Section 4.8.4. of CAPWAP Protocol Specification, RFC 5415." 2601 ::= { capwapBaseStats 2 } 2603 -- Notifications 2605 capwapBaseChannelUp NOTIFICATION-TYPE 2606 OBJECTS { 2607 capwapBaseNtfWtpId, 2608 capwapBaseNtfChannelType, 2609 capwapBaseNtfAuthenMethod 2610 } 2611 STATUS current 2612 DESCRIPTION 2613 "This notification is sent by the AC when a CAPWAP channel 2614 established. 2615 The notification is separated for data or control channel." 2616 ::= { capwapBaseNotifications 1 } 2618 capwapBaseChannelDown NOTIFICATION-TYPE 2619 OBJECTS { 2620 capwapBaseNtfWtpId, 2621 capwapBaseNtfChannelType, 2622 capwapBaseNtfChannelDownReason 2623 } 2624 STATUS current 2625 DESCRIPTION 2626 "This notification is sent by the AC when CAPWAP channel 2627 becomes down. 2628 The notification is separated for data or control channel." 2629 ::= { capwapBaseNotifications 2 } 2631 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 2632 OBJECTS { 2633 capwapBaseNtfWtpId, 2634 capwapBaseNtfRadioId, 2635 capwapBaseNtfStationIdList 2636 } 2637 STATUS current 2638 DESCRIPTION 2639 "This notification is generated when a WTP that has occurred 2640 decryption error since the last report." 2641 REFERENCE 2642 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2643 ::= { capwapBaseNotifications 3 } 2645 capwapBaseJoinFailure NOTIFICATION-TYPE 2646 OBJECTS { 2647 capwapBaseNtfWtpId, 2648 capwapBaseNtfJoinFailureReason 2649 } 2650 STATUS current 2651 DESCRIPTION 2652 "This notification is generated when a WTP fails to join." 2653 REFERENCE 2654 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2655 ::= { capwapBaseNotifications 4 } 2657 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 2658 OBJECTS { 2659 capwapBaseNtfWtpId, 2660 capwapBaseNtfImageFailureReason 2661 } 2662 STATUS current 2663 DESCRIPTION 2664 "This notification is generated when a WTP fails to update 2665 the firmware image." 2666 REFERENCE 2667 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2668 ::= { capwapBaseNotifications 5 } 2670 capwapBaseConfigMsgError NOTIFICATION-TYPE 2671 OBJECTS { 2672 capwapBaseNtfWtpId, 2673 capwapBaseNtfConfigMsgErrorType, 2674 capwapBaseNtfMsgErrorElements 2675 } 2676 STATUS current 2677 DESCRIPTION 2678 "This notification is generated when a WTP receives message 2679 elements in the configuration management messages which it 2680 is unable to apply locally." 2681 REFERENCE 2682 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2683 ::= { capwapBaseNotifications 6 } 2685 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2686 OBJECTS { 2687 capwapBaseNtfWtpId, 2688 capwapBaseNtfRadioId, 2689 capwapBaseNtfRadioOperStatusFlag, 2690 capwapBaseNtfRadioStatusCause 2691 } 2692 STATUS current 2693 DESCRIPTION 2694 "The notification is generated when a radio's operational state 2695 is changed." 2696 REFERENCE 2697 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2698 ::= { capwapBaseNotifications 7 } 2700 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2701 OBJECTS { 2702 capwapBaseNtfWtpId, 2703 capwapBaseNtfChannelType, 2704 capwapBaseNtfAuthenMethod, 2705 capwapBaseNtfAuthenFailureReason 2706 } 2707 STATUS current 2708 DESCRIPTION 2709 "The notification notifies an authentication failure event, 2710 and provides the reason for it." 2711 ::= { capwapBaseNotifications 8 } 2713 -- Objects used only in notifications 2715 -- for notifications 2716 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2717 ::= { capwapBaseObjects 5 } 2719 capwapBaseNtfWtpId OBJECT-TYPE 2720 SYNTAX CapwapBaseWtpIdTC 2721 MAX-ACCESS accessible-for-notify 2722 STATUS current 2723 DESCRIPTION 2724 "Represents the unique identifier of a WTP." 2725 ::= { capwapBaseNotifyVarObjects 1 } 2727 capwapBaseNtfRadioId OBJECT-TYPE 2728 SYNTAX CapwapBaseRadioIdTC 2729 MAX-ACCESS accessible-for-notify 2730 STATUS current 2731 DESCRIPTION 2732 "Represents the identifier of a PHY radio on a WTP, which is 2733 only required to be unique on a WTP. 2734 For example, WTP A and WTP B can use the same value of 2735 capwapBaseNtfRadioId for their first radio." 2736 REFERENCE 2737 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2738 ::= { capwapBaseNotifyVarObjects 2 } 2740 capwapBaseNtfChannelType OBJECT-TYPE 2741 SYNTAX CapwapBaseChannelTypeTC 2742 MAX-ACCESS accessible-for-notify 2743 STATUS current 2744 DESCRIPTION 2745 "Represents the channel type for CAPWAP protocol." 2746 ::= { capwapBaseNotifyVarObjects 3 } 2748 capwapBaseNtfAuthenMethod OBJECT-TYPE 2749 SYNTAX CapwapBaseAuthenMethodTC 2750 MAX-ACCESS accessible-for-notify 2751 STATUS current 2752 DESCRIPTION 2753 "Represents authentication method for CAPWAP Channel." 2754 ::= { capwapBaseNotifyVarObjects 4 } 2756 capwapBaseNtfChannelDownReason OBJECT-TYPE 2757 SYNTAX INTEGER { 2758 timeout(1), 2759 rekeyfailure(2), 2760 acRebootWtp(3), 2761 dtlsError(4), 2762 maxRetransmit(5) 2763 } 2764 MAX-ACCESS accessible-for-notify 2765 STATUS current 2766 DESCRIPTION 2767 "Represents the reason for Channel down. 2768 The following enumerated values are supported: 2769 timeout(1) - The keep alive is timeout 2770 rekeyfailure(2) - Rekey process is failed, channel will be 2771 broken 2772 acRebootWtp(3) - The AC reboot WTP 2773 dtlsError(4) - DTLS notifications: DTLSAborted, 2774 DTLSReassemblyFailure, DTLSPeerDisconnect, 2775 or frequent DTLSDecapFailure 2776 maxRetransmit(5) - The underlying reliable transport's 2777 RetransmitCount counter has reached the 2778 MaxRetransmit variable" 2779 ::= { capwapBaseNotifyVarObjects 5 } 2781 capwapBaseNtfStationIdList OBJECT-TYPE 2782 SYNTAX OCTET STRING 2783 MAX-ACCESS accessible-for-notify 2784 STATUS current 2785 DESCRIPTION 2786 "Represents a list of station identifiers separated by 2787 semicolons." 2788 REFERENCE 2789 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2791 ::= { capwapBaseNotifyVarObjects 6 } 2793 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2794 SYNTAX INTEGER { 2795 keyMismatch(1), 2796 invalidCert(2), 2797 reassemblyFailure(3), 2798 decapFailure(4), 2799 encapFailure(5), 2800 timeout(6), 2801 unknown(8) 2802 } 2803 MAX-ACCESS accessible-for-notify 2804 STATUS current 2805 DESCRIPTION 2806 "Represents reason for WTP authorization failure. 2807 The following enumerated values are supported: 2808 keyMismatch(1) - WTP's and AC's key are not matched 2809 invalidCert(2) - Certification is not valid 2810 reassemblyFailure(3) - Fragment reassembly failure 2811 decapFailure(4) - Decapsulation error 2812 encapFailure(5) - Encapsulation error 2813 timeout(6) - WaitDTLS timer timeout 2814 unknown(8) - Unknown reason" 2815 REFERENCE 2816 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 2817 ::= { capwapBaseNotifyVarObjects 7 } 2819 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2820 SYNTAX INTEGER { 2821 operable(0), 2822 inoperable(1) 2823 } 2824 MAX-ACCESS accessible-for-notify 2825 STATUS current 2826 DESCRIPTION 2827 "Represents the operation status of a radio. 2828 The following enumerated values are supported: 2829 operable(0) - The radio is operable 2830 inoperable(1) - The radio is inoperable, and the 2831 capwapBaseNtfRadioStatusCause object 2832 gives the reason in details" 2833 REFERENCE 2834 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2835 ::= { capwapBaseNotifyVarObjects 8 } 2837 capwapBaseNtfRadioStatusCause OBJECT-TYPE 2838 SYNTAX INTEGER { 2839 normal(0), 2840 hwError(1), 2841 swError(2), 2842 adminSet(3) 2843 } 2844 MAX-ACCESS accessible-for-notify 2845 STATUS current 2846 DESCRIPTION 2847 "Represents the reason why radio is out of service. 2848 The following enumerated values are supported: 2849 normal(0) - Normal status 2850 hwError(1) - Radio failure 2851 swError(2) - Software failure 2852 adminSet(3) - Administratively set" 2853 REFERENCE 2854 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2855 ::= { capwapBaseNotifyVarObjects 9 } 2857 capwapBaseNtfJoinFailureReason OBJECT-TYPE 2858 SYNTAX INTEGER { 2859 unspecified(1), 2860 resDepletion(2), 2861 unknownSource(3), 2862 incorrectData(4), 2863 sessionIdInUse(5), 2864 notSupportHw(6), 2865 notSupportBinding(7) 2866 } 2867 MAX-ACCESS accessible-for-notify 2868 STATUS current 2869 DESCRIPTION 2870 "Represents the reason of join failure. 2871 The following enumerated values are supported: 2872 unspecified(1) - Unspecified failure reason 2873 resDepletion(2) - Resource depletion 2874 unknownSource(3) - Unknown source 2875 incorrectData(4) - Incorrect data 2876 sessionIdInUse(5) - Session ID already in use 2877 notSupportHw(6) - WTP hardware not supported 2878 notSupportBinding(7) - Binding not supported" 2879 REFERENCE 2880 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2881 ::= { capwapBaseNotifyVarObjects 10 } 2883 capwapBaseNtfImageFailureReason OBJECT-TYPE 2884 SYNTAX INTEGER { 2885 invalidChecksum(1), 2886 invalidLength(2), 2887 other(3), 2888 inStorage(4) 2889 } 2890 MAX-ACCESS accessible-for-notify 2891 STATUS current 2892 DESCRIPTION 2893 "Represents the reason of image failure. 2894 The following enumerated values are supported: 2895 invalidChecksum(1) - Invalid checksum 2896 invalidLength(2) - Invalid data length 2897 other(3) - Other error 2898 inStorage(4) - Image already present" 2899 REFERENCE 2900 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2901 ::= { capwapBaseNotifyVarObjects 11 } 2903 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 2904 SYNTAX INTEGER { 2905 unknownElement(1), 2906 unsupportedElement(2), 2907 unknownValue(3), 2908 unsupportedValue(4) 2909 } 2910 MAX-ACCESS accessible-for-notify 2911 STATUS current 2912 DESCRIPTION 2913 "Represents the type of configuration message error. 2914 The following enumerated values are supported: 2915 unknownElement(1) - Unknown message element 2916 unsupportedElement(2) - Unsupported message element 2917 unknownValue(3) - Unknown message element value 2918 unsupportedValue(4) - Unsupported message element value" 2919 REFERENCE 2920 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 2921 ::= { capwapBaseNotifyVarObjects 12 } 2923 capwapBaseNtfMsgErrorElements OBJECT-TYPE 2924 SYNTAX SnmpAdminString 2925 MAX-ACCESS accessible-for-notify 2926 STATUS current 2927 DESCRIPTION 2928 "Represents the message elements sent by the AC in the 2929 Configuration Status Response message that caused the error." 2930 REFERENCE 2931 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 2932 ::= { capwapBaseNotifyVarObjects 13 } 2934 -- Module compliance 2935 capwapBaseCompliances OBJECT IDENTIFIER 2936 ::= { capwapBaseConformance 1 } 2938 capwapBaseGroups OBJECT IDENTIFIER 2939 ::= { capwapBaseConformance 2 } 2941 capwapBaseCompliance MODULE-COMPLIANCE 2942 STATUS current 2943 DESCRIPTION 2944 "Describes the requirements for conformance to the 2945 CAPWAP-BASE-MIB module." 2947 MODULE -- this module 2948 MANDATORY-GROUPS { 2949 capwapBaseAcNodeGroup, 2950 capwapBaseWtpProfileGroup, 2951 capwapBaseWtpStateGroup, 2952 capwapBaseWtpGroup, 2953 capwapBaseRadioGroup, 2954 capwapBaseStationGroup 2955 } 2957 GROUP capwapBaseAcNodeGroup2 2958 DESCRIPTION 2959 "The capwapBaseAcNodeGroup2 group is optional." 2961 GROUP capwapBaseAcNameListGroup 2962 DESCRIPTION 2963 "The capwapBaseAcNameListGroup group is optional." 2965 GROUP capwapBaseMacAclsGroup 2966 DESCRIPTION 2967 "The capwapBaseMacAclsGroup group is optional." 2969 GROUP capwapBaseWtpProfileGroup2 2970 DESCRIPTION 2971 "The capwapBaseWtpProfileGroup2 group is optional." 2973 GROUP capwapBaseWtpGroup2 2974 DESCRIPTION 2975 "The capwapBaseWtpGroup2 group is optional." 2977 GROUP capwapBaseWtpEventsStatsGroup 2978 DESCRIPTION 2979 "The capwapBaseWtpEventsStatsGroup group is optional." 2981 GROUP capwapBaseRadioEventsStatsGroup 2982 DESCRIPTION 2983 "The capwapBaseRadioEventsStatsGroup group is optional." 2985 GROUP capwapBaseParametersGroup 2986 DESCRIPTION 2987 "The capwapBaseParametersGroup group is optional." 2989 GROUP capwapBaseStatsGroup 2990 DESCRIPTION 2991 "The capwapBaseStatsGroup group is optional." 2993 GROUP capwapBaseNotificationsGroup 2994 DESCRIPTION 2995 "The capwapBaseNotificationsGroup group is optional." 2997 GROUP capwapBaseNotifyVarsGroup 2998 DESCRIPTION 2999 "The capwapBaseNotifyVarsGroup group is optional. 3000 If capwapBaseNotificationsGroup is supported, 3001 this group must be implemented." 3002 ::= { capwapBaseCompliances 1 } 3004 capwapBaseAcNodeGroup OBJECT-GROUP 3005 OBJECTS { 3006 capwapBaseWtpSessions, 3007 capwapBaseWtpSessionsLimit, 3008 capwapBaseStationSessions, 3009 capwapBaseStationSessionsLimit 3010 } 3011 STATUS current 3012 DESCRIPTION 3013 "A collection of objects which are used to represent 3014 the basic properties for the AC from the CAPWAP 3015 protocol perspective." 3016 ::= { capwapBaseGroups 1 } 3018 capwapBaseAcNodeGroup2 OBJECT-GROUP 3019 OBJECTS { 3020 capwapBaseDataChannelDTLSPolicyOptions, 3021 capwapBaseDataChannelDTLSPolicyConfig, 3022 capwapBaseControlChannelAuthenOptions, 3023 capwapBaseControlChannelAuthenConfig 3024 } 3025 STATUS current 3026 DESCRIPTION 3027 "A collection of objects which are used to represent 3028 the other properties such as security for the AC from 3029 the CAPWAP protocol perspective." 3030 ::= { capwapBaseGroups 2 } 3032 capwapBaseAcNameListGroup OBJECT-GROUP 3033 OBJECTS { 3034 capwapBaseAcNameListName, 3035 capwapBaseAcNameListPriority, 3036 capwapBaseAcNameListRowStatus 3037 } 3038 STATUS current 3039 DESCRIPTION 3040 "A collection of objects which are used to configure 3041 the AC name list." 3042 ::= { capwapBaseGroups 3 } 3044 capwapBaseMacAclsGroup OBJECT-GROUP 3045 OBJECTS { 3046 capwapBaseMacAclStationId, 3047 capwapBaseMacAclRowStatus 3048 } 3049 STATUS current 3050 DESCRIPTION 3051 "A collection of objects which are used to configure 3052 the stations ACL." 3053 ::= { capwapBaseGroups 4 } 3055 capwapBaseWtpProfileGroup OBJECT-GROUP 3056 OBJECTS { 3057 capwapBaseWtpProfileName, 3058 capwapBaseWtpProfileWTPSerialId, 3059 capwapBaseWtpProfileWTPModelNumber, 3060 capwapBaseWtpProfileWtpName, 3061 capwapBaseWtpProfileWtpLocation, 3062 capwapBaseWtpProfileRowStatus 3063 } 3064 STATUS current 3065 DESCRIPTION 3066 "A collection of objects which are used to configure 3067 the WTP profile." 3068 ::= { capwapBaseGroups 5 } 3070 capwapBaseWtpProfileGroup2 OBJECT-GROUP 3071 OBJECTS { 3072 capwapBaseWtpProfileWtpStaticIpEnable, 3073 capwapBaseWtpProfileWtpStaticIpType, 3074 capwapBaseWtpProfileWtpStaticIp, 3075 capwapBaseWtpProfileWtpNetmask, 3076 capwapBaseWtpProfileWtpGateway, 3077 capwapBaseWtpProfileWtpFallbackEnable, 3078 capwapBaseWtpProfileWtpEchoInterval, 3079 capwapBaseWtpProfileWtpIdleTimeout, 3080 capwapBaseWtpProfileWtpMaxDiscoveryInterval, 3081 capwapBaseWtpProfileWtpReportInterval, 3082 capwapBaseWtpProfileWtpSilentInterval, 3083 capwapBaseWtpProfileWtpStatisticsTimer, 3084 capwapBaseWtpProfileWtpWaitDTLSTimer, 3085 capwapBaseWtpProfileWtpEcnSupport 3086 } 3087 STATUS current 3088 DESCRIPTION 3089 "A collection of optional objects which are used to 3090 configure the WTP profile." 3091 ::= { capwapBaseGroups 6 } 3093 capwapBaseWtpStateGroup OBJECT-GROUP 3094 OBJECTS { 3095 capwapBaseWtpStateWtpIpAddressType, 3096 capwapBaseWtpStateWtpIpAddress, 3097 capwapBaseWtpStateWtpBaseMacAddress, 3098 capwapBaseWtpState, 3099 capwapBaseWtpStateWtpCurrWtpProfileId 3100 } 3101 STATUS current 3102 DESCRIPTION 3103 "A collection of objects which are used to represent 3104 the WTP's state information." 3105 ::= { capwapBaseGroups 7 } 3107 capwapBaseWtpGroup OBJECT-GROUP 3108 OBJECTS { 3109 capwapBaseWtpBaseMacAddress, 3110 capwapBaseWtpTunnelModeOptions, 3111 capwapBaseWtpMacTypeOptions, 3112 capwapBaseWtpDiscoveryType, 3113 capwapBaseWtpRadiosInUseNum, 3114 capwapBaseWtpRadioNumLimit 3115 } 3116 STATUS current 3117 DESCRIPTION 3118 "A collection of objects which are used to represent 3119 the properties information for the WTPs in running state." 3120 ::= { capwapBaseGroups 8 } 3122 capwapBaseWtpGroup2 OBJECT-GROUP 3123 OBJECTS { 3124 capwapBaseWtpPhyIndex, 3125 capwapBaseWtpRetransmitCount, 3126 capwapBaseWtpMaxDiscoveries, 3127 capwapBaseWtpMaxFailedDTLSSessionRetry, 3128 capwapBaseWtpMaxRetransmit, 3129 capwapBaseWtpDataChannelKeepAliveTimer, 3130 capwapBaseWtpDataChannelDeadInterval, 3131 capwapBaseWtpDiscoveryInterval, 3132 capwapBaseWtpDTLSSessionDeleteTimer, 3133 capwapBaseWtpImageDataStartTimer, 3134 capwapBaseWtpRetransmitInterval 3135 } 3136 STATUS current 3137 DESCRIPTION 3138 "A collection of optional objects which are used to represent 3139 the properties information for the WTPs in running state." 3140 ::= { capwapBaseGroups 9 } 3142 capwapBaseRadioGroup OBJECT-GROUP 3143 OBJECTS { 3144 capwapBaseWirelessBindingVirtualRadioIfIndex, 3145 capwapBaseWirelessBindingType 3146 } 3147 STATUS current 3148 DESCRIPTION 3149 "A collection of objects which are used to represent 3150 the wireless binding type, the mappings between the 3151 ifIndexes of WLAN Virtual Radio Interfaces and PHY radios." 3152 ::= { capwapBaseGroups 10 } 3154 capwapBaseStationGroup OBJECT-GROUP 3155 OBJECTS { 3156 capwapBaseStationAddedTime, 3157 capwapBaseStationVlanName 3158 } 3159 STATUS current 3160 DESCRIPTION 3161 "A collection of objects which are used to represent 3162 the stations' basic properties." 3163 ::= { capwapBaseGroups 11 } 3165 capwapBaseWtpEventsStatsGroup OBJECT-GROUP 3166 OBJECTS { 3167 capwapBaseWtpEventsStatsRebootCount, 3168 capwapBaseWtpEventsStatsInitCount, 3169 capwapBaseWtpEventsStatsLinkFailureCount, 3170 capwapBaseWtpEventsStatsSwFailureCount, 3171 capwapBaseWtpEventsStatsHwFailureCount, 3172 capwapBaseWtpEventsStatsOtherFailureCount, 3173 capwapBaseWtpEventsStatsUnknownFailureCount, 3174 capwapBaseWtpEventsStatsLastFailureType 3175 } 3176 STATUS current 3177 DESCRIPTION 3178 "A collection of objects which are used for collecting 3179 WTP reboot count, link failure count, hardware failure 3180 count and so on." 3181 ::= { capwapBaseGroups 12 } 3183 capwapBaseRadioEventsStatsGroup OBJECT-GROUP 3184 OBJECTS { 3185 capwapBaseRadioEventsStatsResetCount, 3186 capwapBaseRadioEventsStatsSwFailCount, 3187 capwapBaseRadioEventsStatsHwFailCount, 3188 capwapBaseRadioEventsStatsOtherFailCount, 3189 capwapBaseRadioEventsStatsUnknownFailCount, 3190 capwapBaseRadioEventsStatsConfigUpdateCount, 3191 capwapBaseRadioEventsStatsChannelChangeCount, 3192 capwapBaseRadioEventsStatsBandChangeCount, 3193 capwapBaseRadioEventsStatsCurrentNoiseFloor, 3194 capwapBaseRadioEventsStatsDecryptErrorCount, 3195 capwapBaseRadioEventsStatsLastFailType 3196 } 3197 STATUS current 3198 DESCRIPTION 3199 "A collection of objects which are used for collecting 3200 radio reset count, channel change count, hardware failure 3201 count and so on" 3202 ::= { capwapBaseGroups 13 } 3204 capwapBaseParametersGroup OBJECT-GROUP 3205 OBJECTS { 3206 capwapBaseAcMaxRetransmit, 3207 capwapBaseAcChangeStatePendingTimer, 3208 capwapBaseAcDataCheckTimer, 3209 capwapBaseAcDTLSSessionDeleteTimer, 3210 capwapBaseAcEchoInterval, 3211 capwapBaseAcRetransmitInterval, 3212 capwapBaseAcSilentInterval, 3213 capwapBaseAcWaitDTLSTimer, 3214 capwapBaseAcWaitJoinTimer, 3215 capwapBaseAcEcnSupport 3216 } 3217 STATUS current 3218 DESCRIPTION 3219 "Objects used for the CAPWAP protocol's parameters." 3220 ::= { capwapBaseGroups 14 } 3222 capwapBaseStatsGroup OBJECT-GROUP 3223 OBJECTS { 3224 capwapBaseFailedDTLSAuthFailCount, 3225 capwapBaseFailedDTLSSessionCount 3226 } 3227 STATUS current 3228 DESCRIPTION 3229 "Objects used for collecting the CAPWAP protocol's statistic." 3230 ::= { capwapBaseGroups 15 } 3232 capwapBaseNotificationsGroup NOTIFICATION-GROUP 3233 NOTIFICATIONS { 3234 capwapBaseChannelUp, 3235 capwapBaseChannelDown, 3236 capwapBaseDecryptErrorReport, 3237 capwapBaseJoinFailure, 3238 capwapBaseImageUpgradeFailure, 3239 capwapBaseConfigMsgError, 3240 capwapBaseRadioOperableStatus, 3241 capwapBaseAuthenticationFailure 3242 } 3243 STATUS current 3244 DESCRIPTION 3245 "A collection of notifications in this MIB module." 3246 ::= { capwapBaseGroups 16 } 3248 capwapBaseNotifyVarsGroup OBJECT-GROUP 3249 OBJECTS { 3250 capwapBaseNtfWtpId, 3251 capwapBaseNtfRadioId, 3252 capwapBaseNtfChannelType, 3253 capwapBaseNtfAuthenMethod, 3254 capwapBaseNtfChannelDownReason, 3255 capwapBaseNtfStationIdList, 3256 capwapBaseNtfAuthenFailureReason, 3257 capwapBaseNtfRadioOperStatusFlag, 3258 capwapBaseNtfRadioStatusCause, 3259 capwapBaseNtfJoinFailureReason, 3260 capwapBaseNtfImageFailureReason, 3261 capwapBaseNtfConfigMsgErrorType, 3262 capwapBaseNtfMsgErrorElements 3263 } 3264 STATUS current 3265 DESCRIPTION 3266 "Objects used for notifications." 3267 ::= { capwapBaseGroups 17 } 3269 END 3270 11. Security Considerations 3272 There are a number of management objects defined in this MIB module 3273 with a MAX-ACCESS clause of read-write and/or read-create. Such 3274 objects MAY be considered sensitive or vulnerable in some network 3275 environments. The support for SET operations in a non-secure 3276 environment without proper protection can have a negative effect on 3277 network operations. The followings are the tables and objects and 3278 their sensitivity/vulnerability: 3280 - Unauthorized changes to the capwapBaseWtProfileTable, and writable 3281 objects under capwapBaseAcs group MAY disrupt allocation of resources 3282 in the network. For example, a WTP's static IP address could be 3283 changed by set capwapBaseWtpProfileWtpStaticIp object. 3285 - Unauthorized changes to writable objects under the capwapBaseAc 3286 group, it MAY disrupt allocation of resources in the network. For 3287 example, a invalid value for capwapBaseWtpSessionsLimit object will 3288 increase the AC's traffic burden. Also, some objects such as 3289 capwapBaseDataChannelDTLSPolicyConfig MAY cause network unsafe. 3291 - Unauthorized changes to the capwapBaseMacAclTable, it MAY cause 3292 legal stations unable to access the network any more while illegal 3293 stations have chance to access the network. 3295 - Unauthorized changes to writable objects under the 3296 capwapBaseParameters group, it MAY influence CAPWAP protocol 3297 behaviour and status. For example, an invalid value set for the 3298 capwapBaseAcDataCheckTimer MAY influence the CAPWAP state machine. 3300 Some of the readable objects in this MIB module (i.e., objects with a 3301 MAX-ACCESS other than not-accessible) MAY be considered sensitive or 3302 vulnerable in some network environments. It is thus important to 3303 control even GET and/or NOTIFY access to these objects and possibly 3304 to even encrypt the values of these objects when sending them over 3305 the network via SNMP. The followings are the tables and objects and 3306 their sensitivity/vulnerability: 3308 - The capwapBaseDataChannelDTLSPolicyOptions and 3309 capwapBaseControlChannelAuthenOptions under the capwapBaseAc group 3310 exposes the current security option for CAPWAP data and control 3311 channels. 3313 - The capwapBaseWtpTable exposes a WTP's important information like 3314 tunnel mode, MAC type and so on. 3316 - The capwapBaseWtpEventsStatsTable exposes a WTP's failure 3317 information. 3319 - The capwapBaseRadioEventsStatsTable exposes a radio's failure 3320 information. 3322 SNMP versions prior to SNMPv3 did not include adequate security. 3323 Even if the network itself is secure (for example by using IPSec), 3324 even then, there is no control as to who on the secure network is 3325 allowed to access and GET/SET (read/change/create/delete) the objects 3326 in this MIB module. 3328 It is RECOMMENDED that implementers consider the security features as 3329 provided by the SNMPv3 framework (see [RFC3410], section 8), 3330 including full support for the SNMPv3 cryptographic mechanisms (for 3331 authentication and privacy). 3333 Further, the deployment of SNMP versions prior to SNMPv3 is NOT 3334 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3335 enable cryptographic security. It is then a customer/operator 3336 responsibility to ensure that the SNMP entity giving access to an 3337 instance of this MIB module is properly configured to give access to 3338 the objects only to those principals (users) that have legitimate 3339 rights to indeed GET or SET (change/create/delete) them. 3341 12. IANA Considerations 3343 12.1. IANA Considerations for CAPWAP-BASE-MIB Module 3345 The MIB module in this document uses the following IANA-assigned 3346 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3348 Descriptor OBJECT IDENTIFIER value 3349 ---------- ----------------------- 3351 capwapBaseMIB { mib-2 XXX } 3353 12.2. IANA Considerations for ifType 3355 Require IANA to assign a ifType for the WTP Virtual Radio Interface. 3357 13. Contributors 3359 This MIB module is based on contributions from Long Gao. 3361 14. Acknowledgements 3363 The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao 3364 Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 3366 15. References 3367 15.1. Normative References 3369 [RFC2119] Bradner, S., "Key words for use in 3370 RFCs to Indicate Requirement Levels", 3371 BCP 14, RFC 2119, March 1997. 3373 [RFC2578] McCloghrie, K., Ed., Perkins, D., 3374 Ed., and J. Schoenwaelder, Ed., 3375 "Structure of Management Information 3376 Version 2 (SMIv2)", STD 58, RFC 2578, 3377 April 1999. 3379 [RFC2579] McCloghrie, K., Ed., Perkins, D., 3380 Ed., and J. Schoenwaelder, Ed., 3381 "Textual Conventions for SMIv2", 3382 STD 58, RFC 2579, April 1999. 3384 [RFC2580] McCloghrie, K., Perkins, D., and J. 3385 Schoenwaelder, "Conformance 3386 Statements for SMIv2", STD 58, 3387 RFC 2580, April 1999. 3389 [RFC2863] McCloghrie, K. and F. Kastenholz, 3390 "The Interfaces Group MIB", RFC 2863, 3391 June 2000. 3393 [RFC3411] Harrington, D., Presuhn, R., and B. 3394 Wijnen, "An Architecture for 3395 Describing Simple Network Management 3396 Protocol (SNMP) Management 3397 Frameworks", STD 62, RFC 3411, 3398 December 2002. 3400 [RFC3418] Presuhn, R., "Management Information 3401 Base (MIB) for the Simple Network 3402 Management Protocol (SNMP)", STD 62, 3403 RFC 3418, December 2002. 3405 [RFC4001] Daniele, M., Haberman, B., Routhier, 3406 S., and J. Schoenwaelder, "Textual 3407 Conventions for Internet Network 3408 Addresses", RFC 4001, February 2005. 3410 [RFC4133] Bierman, A. and K. McCloghrie, 3411 "Entity MIB (Version 3)", RFC 4133, 3412 August 2005. 3414 [RFC5415] Calhoun, P., Montemurro, M., and D. 3416 Stanley, "Control And Provisioning of 3417 Wireless Access Points (CAPWAP) 3418 Protocol Specification", RFC 5415, 3419 March 2009. 3421 15.2. Informative References 3423 [IEEE.802-11.2007] "Information technology - 3424 Telecommunications and information 3425 exchange between systems - Local and 3426 metropolitan area networks - Specific 3427 requirements - Part 11: Wireless LAN 3428 Medium Access Control (MAC) and 3429 Physical Layer (PHY) specifications", 3430 IEEE Standard 802.11, 2007, . 3434 [RFC3168] Ramakrishnan, K., Floyd, S., and D. 3435 Black, "The Addition of Explicit 3436 Congestion Notification (ECN) to IP", 3437 RFC 3168, September 2001. 3439 [RFC3410] Case, J., Mundy, R., Partain, D., and 3440 B. Stewart, "Introduction and 3441 Applicability Statements for 3442 Internet-Standard Management 3443 Framework", RFC 3410, December 2002. 3445 [RFC4118] Yang, L., Zerfos, P., and E. Sadot, 3446 "Architecture Taxonomy for Control 3447 and Provisioning of Wireless Access 3448 Points (CAPWAP)", RFC 4118, 3449 June 2005. 3451 [RFC4347] Rescorla, E. and N. Modadugu, 3452 "Datagram Transport Layer Security", 3453 RFC 4347, April 2006. 3455 [RFC5416] Calhoun, P., Montemurro, M., and D. 3456 Stanley, "Control and Provisioning of 3457 Wireless Access Points (CAPWAP) 3458 Protocol Binding for IEEE 802.11", 3459 RFC 5416, March 2009. 3461 [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., 3462 and Y. Zhang, "CAPWAP Protocol 3463 Binding MIB for IEEE 802.11", 3464 (work in progress), October 2008. 3466 Appendix A. Appendix A. Changes between -05 and -04 3468 1) To close the issue 68 "Suggest Let Base MIB to Support a WTP 3469 Profile" 3471 -------------------------------------------------------------- 3473 Add a new section 5.7. WTP Profile, update the section 8, add a new 3474 table of capwapBaseWtpProfileTable and update the related MIB 3475 objects. 3477 Authors' Addresses 3479 Yang Shi (editor) 3480 Hangzhou H3C Tech. Co., Ltd 3481 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 3482 Beijing 3483 China(100085) 3485 Phone: +86 010 82775276 3486 EMail: young@h3c.com 3488 David Perkins (editor) 3489 SNMPinfo 3490 288 Quailbrook Ct San Carlos, 3491 CA 94070 3492 USA 3494 Phone: +1 408 394-8702 3495 EMail: dperkins@snmpinfo.com 3497 Chris Elliott (editor) 3498 Cisco Systems, Inc. 3499 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 3500 27709 3501 USA 3503 Phone: +1 919-392-2146 3504 EMail: chelliot@cisco.com 3505 Yong Zhang (editor) 3506 Fortinet, Inc. 3507 1090 Kifer Road 3508 Sunnyvale, CA 94086 3509 USA 3511 EMail: yzhang@fortinet.com