idnits 2.17.1 draft-ietf-capwap-base-mib-06.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 (August 13, 2009) is 5370 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) == Outdated reference: A later version (-06) exists of draft-ietf-capwap-802dot11-mib-04 Summary: 2 errors (**), 0 flaws (~~), 3 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: February 14, 2010 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 August 13, 2009 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-06 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 February 14, 2010. 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 . . . . . . . . . . . . . . . . . 8 71 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 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 . . . . . . 72 88 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 72 89 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 72 90 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 72 91 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 92 15.1. Normative References . . . . . . . . . . . . . . . . . . . 72 93 15.2. Informative References . . . . . . . . . . . . . . . . . . 73 94 Appendix A. Appendix A. Changes between -06 and -05 . . . . . . . 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 the management requirements for the centralized WLAN 238 architecture. 240 5.4. Design Idea 242 The basic design idea of the CAPWAP-BASE-MIB module is: 244 - The SNMP agent MUST be run on the AC devices and is not REQUIRED on 245 the WTP devices. It follows the same model as the CAPWAP protocol: 246 Centralized Control; 248 - It is designed to accommodate the specific needs of each wireless 249 technology in a standard way. It is independent of any wireless 250 technologies; 252 - The ifIndex [RFC2863] is used as a common handler for corresponding 253 interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific 254 wireless technologies; 256 - The operator could manage and control the centralized WLAN 257 architectures using multiple MIB modules defined by multiple SDOs, 258 while keeping them loosely coupled. 260 5.5. Mechanism of Reusing Wireless Binding MIB Modules 262 For any wireless technology, the configuration and management of 263 radios are very important. As usual, wireless binding MIB modules 264 support radio management on their own. For example, the MIB tables 265 such as the Dot11OperationTable [IEEE.802-11.2007] are able to 266 support WTP radio configuration. These tables use the ifIndex as the 267 index, and work well under autonomous WLAN architecture. 269 To reuse such wireless binding MIB modules is very important to 270 centralized WLAN architectures. According to [RFC5415], a specific 271 PHY radio could be identified by the combination of the identifiers 272 of the WTP and radio (WTP ID + radio ID), so the key point is to make 273 use of the ifIndex idea and find a way to maintain the mappings 274 between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism, 275 an ifIndex can identify an interface in an abstract way, and it does 276 NOT care for the interface's PHY location (either on the WTP or AC). 277 The AC can have WTP Virtual Radio Interfaces to logically represent 278 PHY radios on the WTP. It looks like that PHY radios are located on 279 the AC, and PHY location of the WTP (radio) is hidden to the 280 operator. The operator can operate radios through MIB tables with 281 the ifIndex of a WTP Virtual Radio Interface. As a type of abstract 282 interface, the WTP Virtual Radio Interface could be used by any 283 wireless technology such as IEEE 802.11 and 802.16. The 284 capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used 285 to store the mappings between the 'WTP ID+ Radio ID' and the ifIndex. 287 5.6. CAPWAP Protocol Wireless Binding MIB Module 289 According to the CAPWAP Protocol specification [RFC5415], when 290 defining a binding for wireless technologies, the authors MUST 291 include any necessary definitions for technology-specific messages 292 and all technology-specific message elements for those messages. A 293 CAPWAP binding protocol is required for a specific wireless binding 294 technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding. 296 Sometimes, not all the technology-specific message elements in a 297 CAPWAP binding protocol have MIB objects defined by other SDOs. For 298 example, the protocol of [RFC5416] defines WLAN conception. The WLAN 299 refers to a logical component instantiated on a WTP device. A single 300 physical WTP MAY operate a number of WLANs. Also, Local or Split MAC 301 modes could be specified for a WLAN. The MAC mode for a WLAN is not 302 in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in 303 addition to the existing wireless binding MIB modules defined by 304 other SDOs, a CAPWAP protocol wireless binding MIB module is required 305 to be defined for a wireless binding, e.g, the CAPWAP Protocol 306 Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. 308 5.7. WTP Profile 310 In a centralized WLAN architecture, a WTP profile is used to make 311 configurations such as static IP address for a WTP before and after 312 it connects to the AC. It MUST contain the Base MAC address 313 [RFC5415] of the WTP because the CAPWAP message received from the WTP 314 contains the Base MAC address and the AC uses this Base MAC address 315 to find the corresponding WTP profile. 317 The section 4.6.40 [RFC5415] does not clarify that the WTP's Base MAC 318 address MUST be included in the WTP Board Data message element. This 319 is a known errata item and assumed to be fixed in future by the 320 editors of the RFC5415. 322 Another important function of WTP profile is to trigger the creation 323 of WTP Virtual Radio Interfaces on the AC. To implement this 324 function, a WTP profile MUST include the WTP's model number 325 [RFC5415], which reflects the number of PHY radios on the WTP. In 326 this way, the creation of a WTP profile triggers the AC to 327 automatically create the same number of WTP Virtual Radio Interfaces 328 corresponding to the WTP's PHY radios without manual intervention. 329 With the ifIndexes of WTP Virtual Radio Interfaces, the operator 330 could configure and manage the WTP's PHY radios through the wireless 331 binding MIB modules. 333 6. Structure of the MIB Module 335 The MIB objects are derived from the CAPWAP protocol document 336 [RFC5415]. 338 1) capwapBaseAcNameListTable 340 The AC name list table is used to configure the AC name list. 342 2) capwapBaseMacAclTable 344 The ACL table is used to configure stations' Access Control 345 List(ACL). 347 3) capwapBaseWtpProfileTable 349 The WTP profile table is used to configure WTP profiles for WTPs to 350 be managed before they connect to the AC. An operator could change a 351 WTP's current configuration by changing the values of parameters in 352 the corresponding WTP profile, then the WTP could get the new 353 configuration through the CAPWAP control channel. 355 4) capwapBaseWtpStateTable 357 The WTPs status table is used to indicate each WTP's CAPWAP FSM 358 state, and helps operator to query WTPs' current configuration. 360 5) capwapBaseWtpTable 362 The WTPs table is used display properties of WTPs in running state. 364 6) capwapBaseWirelessBindingTable 366 The wireless binding table is used to display the mappings between 367 WTP Virtual Radio Interfaces and PHY radios, and the wireless binding 368 type for each PHY radio. 370 7) capwapBaseStationTable 372 The station table is used for providing stations' basic property 373 information. 375 8) capwapBaseWtpEventsStatsTable 377 The WTP events statistic table is used for collecting WTP reboot 378 count, link failure count, hardware failure count and so on. 380 9) capwapBaseRadioEventsStatsTable 381 The radio events statistic table is used for collecting radio reset 382 count, channel change count, hardware failure count and so on. 384 7. Relationship to Other MIB Modules 386 7.1. Relationship to SNMPv2-MIB Module 388 The CAPWAP-BASE-MIB module does not duplicate the objects of the 389 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being 390 mandatory for all systems, and the objects apply to the entity as a 391 whole. The 'system' group provides identification of the management 392 entity and certain other system-wide data. 394 7.2. Relationship to IF-MIB Module 396 The Interfaces Group [RFC2863] defines generic managed objects for 397 managing interfaces. This memo contains the media-specific 398 extensions to the Interfaces Group for managing WTP PHY radios that 399 are modeled as interfaces. 401 The IF-MIB module is required to be supported on the AC. Each PHY 402 radio on the WTP corresponds to a WTP Virtual Radio Interface on the 403 AC. The WTP Virtual Radio Interface provides a way to configure the 404 radio's parameters and query radio's traffic statistics, and reuse 405 wireless binding modules defined by other SDOs. The interface MUST 406 be modeled as an ifEntry, and ifEntry objects such as ifIndex, 407 ifDescr, ifName, ifAlias are to be used as per [RFC2863]. 409 Also, as an ifIndex [RFC2863] is used as a common handler for a 410 corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless 411 technologies MIB modules, the AC MUST have a mechanism that preserves 412 the values of the ifIndexes in the ifTable at AC reboot. 414 7.3. Relationship to ENTITY-MIB Module 416 The ENTITY-MIB module [RFC4133] meets the need for a standardized way 417 of representing a single agent, which supports multiple instances of 418 one MIB. It could express a certain relationship between multiple 419 entities, and provide entity properties for each entity. 421 In a centralized WLAN architecture, the SNMP agent runs on the AC, 422 and is not required on the WTP. With the ENTITY-MIB module on the 423 AC, it could keep entity information such as firmware revision and 424 software revision of the AC and WTPs. From the ENTITY-MIB module's 425 perspective, the overall physical entity (AC) is a 'compound' of 426 multiple physical entities (that is, the WTPs connected to AC), and 427 all entities are each identified by a Physical index. The 428 capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the 429 capwapBaseWtpPhyIndex object to store the mappings of WTP object 430 between CAPWAP-BASE-MIB and ENTITY-MIB modules. 432 By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules, 433 operators could query the status and properties of the AC and WTPs. 434 For example, they could get a WTP's current status through the 435 CAPWAP-BASE-MIB module, and a WTP's software revision information 436 through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not 437 duplicate those objects defined in the ENTITY-MIB module. 439 7.4. Relationship to Wireless Binding MIB Modules 441 The wireless binding MIB module of a wireless technology (such as 442 [IEEE.802-11.2007]) is required to be supported on the AC. The 443 CAPWAP-BASE-MIB module is able to support any wireless binding. 444 Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a 445 consistent and abstract way of reusing MIB objects in the wireless 446 binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate 447 those objects defined in the wireless binding MIB modules. 449 7.5. MIB Modules Required for IMPORTS 451 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 452 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP- 453 FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB 454 [RFC4133]. 456 8. Example of CAPWAP-BASE-MIB Module Usage 458 Here takes IEEE 802.11 binding as an example to show how the MIB 459 modules operate. 461 1) Create a WTP profile 463 Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create 464 the WTP profile as follows: 466 In CapwapBaseWtpProfileTable 467 { 468 capwapBaseWtpProfileId = 1, 469 capwapBaseWtpProfileName = 'WTP Profile 123456', 470 capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', 471 capwapBaseWtpProfileWtpModelNumber = 'WTP123', 472 capwapBaseWtpProfileWtpName = 'WTP 123456', 473 capwapBaseWtpProfileWtpLocation = 'office', 474 capwapBaseWtpProfileWtpStaticIpEnable = true(1), 475 capwapBaseWtpProfileWtpStaticIpType = ipv4(1), 476 capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', 477 capwapBaseWtpProfileWtpNetmask = '255.255.255.0', 478 capwapBaseWtpProfileWtpGateway = '192.168.0.1', 479 capwapBaseWtpProfileWtpFallbackEnable = true(1), 480 capwapBaseWtpProfileWtpEchoInterval = 30, 481 capwapBaseWtpProfileWtpIdleTimeout = 300, 482 capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, 483 capwapBaseWtpProfileWtpReportInterval = 120, 484 capwapBaseWtpProfileWtpSilentInterval = 30, 485 capwapBaseWtpProfileWtpStatisticsTimer = 120, 486 capwapBaseWtpProfileWtpWaitDTLSTimer = 60, 487 capwapBaseWtpProfileWtpEcnSupport = limited(0) 488 } 490 Suppose the WTP with model number 'WTP123' has one PHY radio and this 491 PHY radio is identified by ID 1. The creation of this WTP profile 492 triggers the AC to automatically create a WTP Virtual Radio Interface 493 and add a new row object to the CapwapBaseWirelessBindingTable 494 without manual intervention. Suppose the ifIndex of the WTP Virtual 495 Radio Interface is 10. The following information is stored in the 496 CapwapBaseWirelessBindingTable. 498 In CapwapBaseWirelessBindingTable 499 { 500 capwapBaseWtpProfileId = 1, 501 capwapBaseWirelessBindingRadioId = 1, 502 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 503 capwapBaseWirelessBindingType = dot11(2) 504 } 506 The WTP Virtual Radio Interfaces on the AC correspond to the PHY 507 radios on the WTP. The WTP Virtual Radio Interface is modeled by 508 ifTable [RFC2863]. 510 In ifTable 511 { 512 ifIndex = 10, 513 ifDescr = 'WTP Virtual Radio Interface', 514 ifType = xxx, 515 RFC Editor - please replace xxx with the value 516 allocated by IANA for IANAifType of WTP Virtual Radio Interface 517 ifMtu = 0, 518 ifSpeed = 0, 519 ifPhysAddress = '00:00:00:00:00:00', 520 ifAdminStatus = true(1), 521 ifOperStatus = false(0), 522 ifLastChange = 0, 523 ifInOctets = 0, 524 ifInUcastPkts = 0, 525 ifInDiscards = 0, 526 ifInErrors = 0, 527 ifInUnknownProtos = 0, 528 ifOutOctets = 0, 529 ifOutUcastPkts = 0, 530 ifOutDiscards = 0, 531 ifOutErrors = 0 532 } 534 2) Query the ifIndexes of WTP Virtual Radio Interfaces 536 Before configuring PHY radios, the operator needs to get the 537 ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY 538 radios. 540 As CapwapBaseWirelessBindingTable already stores the mappings between 541 PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio 542 Interfaces, the operator can get the ifIndex information by querying 543 this table. Such a query operation SHOULD run from radio ID 1 to 544 radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex 545 value (0) is returned. 547 This example uses capwapBaseWtpProfileId = 1 and 548 capwapBaseWirelessBindingRadioId = 1 as inputs to query the 549 CapwapBaseWirelessBindingTable, and gets 550 capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses 551 capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, 552 and gets a invalid ifIndex value (0), so the the query operation 553 ends. This method gets not only the ifIndexes of WTP Virtual Radio 554 Interfaces, but also the numbers of PHY radios. Besides checking 555 whether the ifIndex value is valid, the operator SHOULD check whether 556 the capwapBaseWirelessBindingType is the desired binding type. 558 3) Configure specific wireless binding parameters for a WTP Virtual 559 Radio Interface 561 This configuration is made on the AC through a specific wireless 562 binding MIB module such as the IEEE 802.11 MIB module. 564 The following shows an example of configuring parameters for a WTP 565 Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 566 Dot11OperationTable [IEEE.802-11.2007]. 568 In Dot11OperationTable 569 { 570 ifIndex = 10, 571 dot11MACAddress = '00:00:00:00:00:00', 572 dot11RTSThreshold = 2347, 573 dot11ShortRetryLimit = 7, 574 dot11LongRetryLimit = 4, 575 dot11FragmentationThreshold = 256, 576 dot11MaxTransmitMSDULifetime = 512, 577 dot11MaxReceiveLifetime = 512, 578 dot11ManufacturerID = 'capwap', 579 dot11ProductID = 'capwap' 580 dot11CAPLimit = 2, 581 dot11HCCWmin = 0, 582 dot11HCCWmax = 0, 583 dot11HCCAIFSN = 1, 584 dot11ADDBAResponseTimeout = 1, 585 dot11ADDTSResponseTimeout = 1, 586 dot11ChannelUtilizationBeaconInterval = 50, 587 dot11ScheduleTimeout = 10, 588 dot11DLSResponseTimeout = 10, 589 dot11QAPMissingAckRetryLimit = 1, 590 dot11EDCAAveragingPeriod = 5 591 } 593 4) Current configuration status report from the WTP to the AC 595 According to [RFC5415], before a WTP that has joined the AC gets 596 configuration from the AC, it needs to report its current 597 configuration status by sending a configuration status request 598 message to the AC, which use the message to update MIB objects on the 599 AC. For example, for IEEE 802.11 binding, the AC updates data in the 600 ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the 601 message. For ifIndex 10, its ifOperStatus in ifTable is updated 602 according to the current radio operational status in the CAPWAP 603 message. 605 5) Query WTP and radio statistics data 606 After WTPs start to run, the operator could query WTP and radio 607 statistics data through CAPWAP-BASE-MIB and specific binding MIB 608 module on the AC. For example, through dot11CountersTable in the 609 IEEE 802.11 MIB module, the operator could query the counter data of 610 a radio using the ifIndex of the corresponding WTP Virtual Radio 611 Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB 612 module, the operator could query the properties of running WTPs. 614 6) MIB operations through a CAPWAP protocol wireless binding MIB 615 module 617 For example, for CAPWAP IEEE 802.11 binding protocol [RFC5416], Some 618 MIB operations such as MAC mode configuration for a WLAN depend on 619 the CAPWAP Protocol Binding MIB for IEEE 802.11 620 [I-D.ietf-capwap-802dot11-mib]. For more information, refer to 621 [I-D.ietf-capwap-802dot11-mib]. 623 7) Query other properties of a WTP 625 The Operator could query MIB objects in the ENTITY-MIB [RFC4133] 626 module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable 627 of CAPWAP-BASE-MIB module. The properties of a WTP such as software 628 version, hardware version are available in the ENTITY-MIB module. 630 9. CAPWAP Message Element Extension 632 This section describes the CAPWAP control message extension for 633 CAPWAP protocol to support CAPWAP-BASE-MIB module. 635 To enable CAPWAP protocol timers and variables [RFC5415] manageable 636 through CAPWAP protocol, the following capwap message element 637 extensions are defined using Vendor Specific Payload message element 638 in this section. These message elements are used by WTP to report 639 extra configuration information to the AC. 641 CAPWAP Message Element Vendor Identifier Element ID 643 CAPWAP Protocol Timers Id assigned by IANA 1 644 CAPWAP Protocol Variables Id assigned by IANA 2 646 9.1. CAPWAP Protocol Timers 648 0 1 2 3 649 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 650 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 651 | Vendor Identifier | 652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 653 | Element ID | DataChannelKeepAlive | 654 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 655 | DataChannelDeadInterval | DiscoveryInterval | 656 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 | DTLSSessionDelete | EchoInterval | 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 659 | IdleTimeout | 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 | ImageDataStartTimer | MaxDiscoveryInterval | 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | ReportInterval | RetransmitInterval | 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 665 | SilentInterval | StatisticsTimer | 666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 667 | WaitDTLS | 668 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 669 Type: 37 for Vendor Specific Payload 671 Length: 34 673 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 674 Network Management Private Enterprise Codes". 676 Element ID: The Element ID field is set to 1 for CAPWAP Protocol 677 Timers. 679 DataChannelKeepAlive: A 16-bit value representing the time, 680 in seconds, that is used by the WTP to determine the next 681 must transmit the Data Channel Keep Alive. (see section 4.7.2 of 682 [RFC5415]). 684 DataChannelDeadInterval: A 16-bit value representing the minimum 685 time, in seconds, a WTP MUST wait without having received a Data 686 Channel Alive packets MAY be considered dead. The value of this 687 timer MUST be no less than 2*DataChannelKeepAlive seconds and 688 no greater that 240 seconds (see section 4.7.3 of [RFC5415]). 690 DiscoveryInterval: A 16-bit value representing the minimum time, in 691 seconds, that a WTP MUST wait after receiving a Discovery Response 692 message, before initiating a DTLS handshake (see section 4.7.5 of 693 [RFC5415]). 695 DTLSSessionDelete: A 16-bit value representing the minimum time, in 696 seconds, a WTP MUST wait for DTLS session deletion (see section 697 4.7.6 of [RFC5415]). 699 EchoInterval: A 16-bit value representing the minimum time, in 700 seconds, between sending Echo Request messages to the AC with 701 which the WTP has joined (see section 4.7.7 of [RFC5415]). 703 IdleTimeout: A 32-bit value representing the idle timeout value that 704 the WTP SHOULD enforce for its active station. The default Idle 705 Timeout is 300 seconds (see section 4.7.8 of [RFC5415]). 707 ImageDataStartTimer: A 16-bit value representing the number of 708 seconds the WTP will wait for its peer to transmit the Image 709 Data Request (see section 4.7.9 of [RFC5415]). 711 MaxDiscoveryInterval: A 16-bit value representing the maximum time 712 allowed between sending Discovery Request messages, in seconds. 713 This value MUST be no less than 2 seconds and no greater than 180 714 seconds (see section 4.7.10 of [RFC5415]). 716 ReportInterval: A 16-bit value representing the time, in seconds, 717 that is used by the WTP to determine the interval the WTP uses 718 between sending the Decryption Error message elements to inform 719 the AC of decryption errors (see section 4.7.11 of [RFC5415]). 721 RetransmitInterval: A 16-bit value representing the minimum time, 722 in seconds, in which a non-acknowledged CAPWAP packet will be 723 retransmitted (see section 4.7.12 of [RFC5415]). 725 SilentInterval: The minimum time, in seconds, a WTP MUST wait before 726 it MAY again send Discovery Request messages or attempt to 727 establish DTLS session (see section 4.7.13 of [RFC5415]). 729 StatisticsTimer: A 16-bit value representing the time, in seconds, 730 that is used by the WTP to determine the interval the WTP uses 731 between the WTP Events Requests it transmits to the AC to 732 communicate its statistics (see section 4.7.14 of [RFC5415]). 734 WaitDTLS: A 16-bit value representing the maximum time, in seconds, 735 a WTP MUST wait without having received a DTLS Handshake message 736 from an AC. This timer MUST be greater than 30 seconds (see 737 section 4.7.15 of [RFC5415]). 739 9.2. CAPWAP Protocol Variables 741 0 1 2 3 742 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 743 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 744 | Vendor Identifier | 745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 746 | Element ID | MaxDiscoveries | 747 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 748 | MaxFailedDTLSSessionRetry | MaxRetransmit | 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 751 Type: 37 for Vendor Specific Payload 753 Length: 12 755 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 756 Network Management Private Enterprise Codes". 758 Element ID: The Element ID field is set to 2 for CAPWAP Protocol 759 Variables. 761 MaxDiscoveries: A 16-bit value representing the maximum number of 762 Discovery Request messages that will be sent after a WTP boots 763 (see section 4.8.5 of [RFC5415]). 765 MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum 766 number of failed DTLS session establishment attempts before the 767 CAPWAP device enters a silent period (see section 4.8.6 of 768 [RFC5415]). 770 MaxRetransmit: A 16-bit value representing the maximum number of 771 retransmissions for a given CAPWAP packet before the link layer 772 considers the peer dead (see section 4.8.7 of [RFC5415]). 774 9.3. CAPWAP Messages for CAPWAP Control Message Extension 776 For CAPWAP Control Message Extension, the following CAPWAP messages 777 will be used. 779 9.3.1. Configuration Status Response Message 781 The following message elements MAY be included in the CAPWAP 782 Configuration Status Response Message. 784 - CAPWAP Protocol Timers, see Section Section 9.1 786 - CAPWAP Protocol Variables, see Section Section 9.2 788 9.3.2. Configuration Update Response Message 790 The following message elements MAY be included in the CAPWAP 791 Configuration Update Response Message. 793 - CAPWAP Protocol Timers, see Section Section 9.1 795 - CAPWAP Protocol Variables, see Section Section 9.2 797 10. Definitions 799 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 801 IMPORTS 803 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 804 DateAndTime, RowStatus 805 FROM SNMPv2-TC 806 InterfaceIndex 807 FROM IF-MIB 808 PhysicalIndex 809 FROM ENTITY-MIB 810 SnmpAdminString 811 FROM SNMP-FRAMEWORK-MIB 812 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 813 FROM SNMPv2-CONF 814 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 815 Integer32, Unsigned32, Counter32 816 FROM SNMPv2-SMI 817 InetAddressType, InetAddress 818 FROM INET-ADDRESS-MIB; 820 capwapBaseMIB MODULE-IDENTITY 821 LAST-UPDATED "200908130000Z" -- August 13th, 2009 822 ORGANIZATION "IETF Control And Provisioning of Wireless Access 823 Points (CAPWAP) Working Group 824 http://www.ietf.org/html.charters/capwap-charter.html" 825 CONTACT-INFO 826 "General Discussion: capwap@frascone.com 827 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 829 Yang Shi (editor) 830 Hangzhou H3C Tech. Co., Ltd. 831 Beijing R&D Center of H3C, Digital Technology Plaza, 832 NO.9 Shangdi 9th Street,Haidian District, 833 Beijing 834 China(100085) 835 Phone: +86 010 82775276 836 EMail: young@h3c.com 838 David T. Perkins 839 228 Bayview Dr 840 San Carlos, CA 94070 841 USA 842 Phone: +1 408 394-8702 843 Email: dperkins@snmpinfo.com 845 Chris Elliott 846 Cisco Systems, Inc. 847 7025 Kit Creek Rd., P.O. Box 14987 848 Research Triangle Park 27709 849 USA 850 Phone: +1 919-392-2146 851 Email: chelliot@cisco.com 853 Yong Zhang 854 Fortinet, Inc. 855 1090 Kifer Road 856 Sunnyvale, CA 94086 857 USA 858 Email: yzhang@fortinet.com" 860 DESCRIPTION 861 "Copyright (C) 2009 The Internet Society. This version of 862 the MIB module is part of RFC xxx; see the RFC itself 863 for full legal notices. 865 This MIB module contains managed object definitions for 866 the CAPWAP Protocol." 867 REVISION "200908130000Z" 868 DESCRIPTION 869 "Initial version published as RFC xxx" 870 ::= { mib-2 xxx } 872 -- Textual Conventions 874 CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION 875 DISPLAY-HINT "d" 876 STATUS current 877 DESCRIPTION 878 "Represents the unique identifier of a WTP profile." 879 SYNTAX Unsigned32 (0..4096) 881 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 882 DISPLAY-HINT "1x:" 883 STATUS current 884 DESCRIPTION 885 "Represents the unique identifier of a WTP instance. 886 As usual, the Base MAC address of WTP is used." 887 SYNTAX OCTET STRING (SIZE (6)) 889 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 890 DISPLAY-HINT "1x:" 891 STATUS current 892 DESCRIPTION 893 "Represents the unique identifier of a station instance. 894 As usual, the MAC address of station is used." 895 SYNTAX OCTET STRING (SIZE (6)) 897 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 898 DISPLAY-HINT "d" 899 STATUS current 900 DESCRIPTION 901 "Represents the unique identifier of a radio on a WTP." 902 SYNTAX Unsigned32 (1..31) 904 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 905 STATUS current 906 DESCRIPTION 907 "Represents the tunneling modes of operation that are 908 supported by a WTP. 909 The WTP MAY support more than one option, represented by 910 the bit field below: 911 localBridging(0) - Local bridging mode 912 dot3Tunnel(1) - 802.3 frame tunnel mode 913 nativeTunnel(2) - Native frame tunnel mode" 914 REFERENCE 915 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 916 SYNTAX BITS { 917 localBridging(0), 918 dot3Tunnel(1), 919 nativeTunnel(2) 920 } 922 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 923 STATUS current 924 DESCRIPTION 925 "Represents the MAC mode of operation supported by a WTP. 926 The following enumerated values are supported: 927 localMAC(0) - Local-MAC mode 928 splitMAC(1) - Split-MAC mode 929 both(2) - Both Local-MAC and Split-MAC" 930 REFERENCE 931 "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." 933 SYNTAX INTEGER { 934 localMAC(0), 935 splitMAC(1), 936 both(2) 937 } 939 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 940 STATUS current 941 DESCRIPTION 942 "Represents the channel type for CAPWAP protocol. 943 The following enumerated values are supported: 944 data(1) - Data channel 945 control(2) - Control channel" 946 SYNTAX INTEGER { 947 data(1), 948 control(2) 949 } 951 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 952 STATUS current 953 DESCRIPTION 954 "Represents the authentication credential type for a WTP. 955 The following enumerated values are supported: 956 other(1) - Other method, for example, vendor specific 957 clear(2) - Clear text and no authentication 958 x509(3) - X.509 certificate authentication 959 psk(4) - Pre-Shared secret authentication 960 As mandatory requirement, CAPWAP control channel 961 authentication SHOULD use DTLS, and either by certificate or 962 PSK. For data channel, DTLS is optional." 963 SYNTAX INTEGER { 964 other(1), 965 clear(2), 966 x509(3), 967 psk(4) 968 } 970 -- Top level components of this MIB module 972 -- Notifications 973 capwapBaseNotifications OBJECT IDENTIFIER 974 ::= { capwapBaseMIB 0 } 975 -- Tables, Scalars 976 capwapBaseObjects OBJECT IDENTIFIER 977 ::= { capwapBaseMIB 1 } 978 -- Conformance 979 capwapBaseConformance OBJECT IDENTIFIER 980 ::= { capwapBaseMIB 2 } 982 -- AC Objects Group 984 capwapBaseAc OBJECT IDENTIFIER 985 ::= { capwapBaseObjects 1 } 987 capwapBaseWtpSessions OBJECT-TYPE 988 SYNTAX Unsigned32 (0..65535) 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "Represents the total number of WTPs which are connecting to 993 the AC." 994 REFERENCE 995 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 996 ::= { capwapBaseAc 1 } 998 capwapBaseWtpSessionsLimit OBJECT-TYPE 999 SYNTAX Unsigned32 (0..65535) 1000 MAX-ACCESS read-write 1001 STATUS current 1002 DESCRIPTION 1003 "Represents the maximum number of WTP sessions configured on 1004 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 2 } 1010 capwapBaseStationSessions OBJECT-TYPE 1011 SYNTAX Unsigned32 (0..65535) 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "Represents the total number of stations which are accessing 1016 the wireless service provided by the AC." 1017 REFERENCE 1018 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1019 ::= { capwapBaseAc 3 } 1021 capwapBaseStationSessionsLimit OBJECT-TYPE 1022 SYNTAX Unsigned32 (0..65535) 1023 MAX-ACCESS read-write 1024 STATUS current 1025 DESCRIPTION 1026 "Represents the maximum number of station sessions configured 1027 on the AC. 1028 The value of the object is persistent at restart/reboot." 1029 REFERENCE 1030 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1031 ::= { capwapBaseAc 4 } 1033 capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE 1034 SYNTAX BITS { 1035 other(0), 1036 clear(1), 1037 dtls(2) 1038 } 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The AC communicates its policy on the use of DTLS for 1043 CAPWAP data channel. 1044 The AC MAY support more than one option, represented by the bit 1045 field below: 1046 other(0) - Other method, for example, vendor specific 1047 clear(1) - Clear text 1048 dtls(2) - DTLS" 1049 REFERENCE 1050 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1051 ::= { capwapBaseAc 5 } 1053 capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE 1054 SYNTAX INTEGER { 1055 other(0), 1056 clear(1), 1057 dtls(2) 1058 } 1059 MAX-ACCESS read-write 1060 STATUS current 1061 DESCRIPTION 1062 "Represents the security policy configured on the AC for 1063 CAPWAP data channel. 1064 The value of the object is persistent at restart/reboot. 1065 The following enumerated values are supported: 1066 other(0) - Other method, for example, vendor specific 1067 clear(1) - Clear text 1068 dtls(2) - DTLS" 1069 REFERENCE 1070 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1071 ::= { capwapBaseAc 6 } 1073 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 1074 SYNTAX BITS { 1075 x509(0), 1076 psk(1) 1077 } 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "Represents the authentication credential type supported by the 1083 AC for CAPWAP control channel. 1084 The AC MAY support more than one option, represented by the bit 1085 field below: 1086 x509(0) - X.509 certificate based 1087 psk(1) - Pre-Shared secret" 1088 REFERENCE 1089 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1090 ::= { capwapBaseAc 7 } 1092 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 1093 SYNTAX INTEGER { 1094 x509(1), 1095 psk(2) 1096 } 1097 MAX-ACCESS read-write 1098 STATUS current 1099 DESCRIPTION 1100 "Represents the authentication credential type configured on 1101 the AC for CAPWAP control channel. 1102 The value of the object is persistent at restart/reboot. 1103 The following enumerated values are supported: 1104 x509(1) - X.509 certificate based 1105 psk(2) - Pre-Shared secret" 1106 REFERENCE 1107 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1108 ::= { capwapBaseAc 8 } 1110 -- capwapBaseAcNameListTable table 1112 capwapBaseAcNameListTable OBJECT-TYPE 1113 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "A table of objects that configure the AC name list. 1118 Values of all read-create objects in this table are 1119 persistent at restart/reboot." 1120 REFERENCE 1121 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1122 ::= { capwapBaseAc 9 } 1124 capwapBaseAcNameListEntry OBJECT-TYPE 1125 SYNTAX CapwapBaseAcNameListEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "A set of objects that configure the AC name list." 1130 INDEX { capwapBaseAcNameListId } 1131 ::= { capwapBaseAcNameListTable 1 } 1133 CapwapBaseAcNameListEntry ::= SEQUENCE { 1134 capwapBaseAcNameListId Unsigned32, 1135 capwapBaseAcNameListName OCTET STRING, 1136 capwapBaseAcNameListPriority Unsigned32, 1137 capwapBaseAcNameListRowStatus RowStatus 1138 } 1140 capwapBaseAcNameListId OBJECT-TYPE 1141 SYNTAX Unsigned32 (1..255) 1142 MAX-ACCESS not-accessible 1143 STATUS current 1144 DESCRIPTION 1145 "Represents the unique identifier of a AC Name list." 1146 ::= { capwapBaseAcNameListEntry 1 } 1148 capwapBaseAcNameListName OBJECT-TYPE 1149 SYNTAX OCTET STRING(SIZE(512)) 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "Represents the name of an AC, and it is expected to be 1154 an UTF-8 encoded string." 1155 REFERENCE 1156 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1157 ::= { capwapBaseAcNameListEntry 2 } 1159 capwapBaseAcNameListPriority OBJECT-TYPE 1160 SYNTAX Unsigned32 (1..255) 1161 MAX-ACCESS read-create 1162 STATUS current 1163 DESCRIPTION 1164 "Represents the priority order of the preferred AC. 1165 For instance, the value of one (1) is used to set the primary 1166 AC, the value of two (2) is used to set the secondary AC, etc." 1167 REFERENCE 1168 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1169 ::= { capwapBaseAcNameListEntry 3 } 1171 capwapBaseAcNameListRowStatus OBJECT-TYPE 1172 SYNTAX RowStatus 1173 MAX-ACCESS read-create 1174 STATUS current 1175 DESCRIPTION 1176 "This variable is used to create, modify, and/or delete a row 1177 in this table." 1178 ::= { capwapBaseAcNameListEntry 4 } 1180 -- End of capwapBaseAcNameListTable table 1182 -- capwapBaseMacAclTable table 1184 capwapBaseMacAclTable OBJECT-TYPE 1185 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "A table of objects that configure station Access Control 1190 Lists (ACL). 1191 The WTP will not provide service to the MAC addresses 1192 configured in this table. 1193 Values of all read-create objects in this table are persistent 1194 at AC restart/reboot." 1195 REFERENCE 1196 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1197 ::= { capwapBaseAc 10 } 1199 capwapBaseMacAclEntry OBJECT-TYPE 1200 SYNTAX CapwapBaseMacAclEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "A set of objects that configure station Access Control 1205 List (ACL)." 1206 INDEX { capwapBaseMacAclId } 1207 ::= { capwapBaseMacAclTable 1 } 1209 CapwapBaseMacAclEntry ::= SEQUENCE { 1210 capwapBaseMacAclId Unsigned32, 1211 capwapBaseMacAclStationId CapwapBaseStationIdTC, 1212 capwapBaseMacAclRowStatus RowStatus 1213 } 1215 capwapBaseMacAclId OBJECT-TYPE 1216 SYNTAX Unsigned32 (1..255) 1217 MAX-ACCESS not-accessible 1218 STATUS current 1219 DESCRIPTION 1220 "Represents the unique identifier of an ACL." 1221 ::= { capwapBaseMacAclEntry 1 } 1223 capwapBaseMacAclStationId OBJECT-TYPE 1224 SYNTAX CapwapBaseStationIdTC 1225 MAX-ACCESS read-create 1226 STATUS current 1227 DESCRIPTION 1228 "Represents the MAC address of a station to which WTPs will 1229 no longer provides service." 1230 REFERENCE 1231 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1232 ::= { capwapBaseMacAclEntry 2 } 1234 capwapBaseMacAclRowStatus OBJECT-TYPE 1235 SYNTAX RowStatus 1236 MAX-ACCESS read-create 1237 STATUS current 1238 DESCRIPTION 1239 "This variable is used to create, modify, and/or delete a row 1240 in this table." 1241 ::= { capwapBaseMacAclEntry 3 } 1243 -- End of capwapBaseMacAclTable table 1245 -- End of AC Objects Group 1247 -- WTP Objects Group 1249 capwapBaseWtps OBJECT IDENTIFIER 1250 ::= { capwapBaseObjects 2 } 1252 -- capwapBaseWtpProfileTable Table 1254 capwapBaseWtpProfileTable OBJECT-TYPE 1255 SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry 1256 MAX-ACCESS not-accessible 1257 STATUS current 1258 DESCRIPTION 1259 "A table of objects that configure WTP profiles for WTPs to 1260 be managed before they connect to the AC. 1261 An operator could change a WTP's configuration by changing 1262 the values of parameters in the corresponding WTP profile, 1263 then the WTP could get the new configuration through the 1264 CAPWAP control channel. 1265 Values of all read-create objects in this table are 1266 persistent at restart/reboot." 1267 ::= { capwapBaseWtps 1 } 1269 capwapBaseWtpProfileEntry OBJECT-TYPE 1270 SYNTAX CapwapBaseWtpProfileEntry 1271 MAX-ACCESS not-accessible 1272 STATUS current 1273 DESCRIPTION 1274 "A set of objects that configure and display a WTP profile." 1275 INDEX { capwapBaseWtpProfileId } 1276 ::= { capwapBaseWtpProfileTable 1 } 1278 CapwapBaseWtpProfileEntry ::= SEQUENCE { 1279 capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, 1280 capwapBaseWtpProfileName SnmpAdminString, 1281 capwapBaseWtpProfileWtpMacAddr CapwapBaseWtpIdTC, 1282 capwapBaseWtpProfileWtpModelNumber SnmpAdminString, 1283 capwapBaseWtpProfileWtpName OCTET STRING, 1284 capwapBaseWtpProfileWtpLocation OCTET STRING, 1285 capwapBaseWtpProfileWtpStaticIpEnable TruthValue, 1286 capwapBaseWtpProfileWtpStaticIpType InetAddressType, 1287 capwapBaseWtpProfileWtpStaticIp InetAddress, 1288 capwapBaseWtpProfileWtpNetmask InetAddress, 1289 capwapBaseWtpProfileWtpGateway InetAddress, 1290 capwapBaseWtpProfileWtpFallbackEnable INTEGER, 1291 capwapBaseWtpProfileWtpEchoInterval Unsigned32, 1292 capwapBaseWtpProfileWtpIdleTimeout Unsigned32, 1293 capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32, 1294 capwapBaseWtpProfileWtpReportInterval Unsigned32, 1295 capwapBaseWtpProfileWtpSilentInterval Unsigned32, 1296 capwapBaseWtpProfileWtpStatisticsTimer Unsigned32, 1297 capwapBaseWtpProfileWtpWaitDTLSTimer Unsigned32, 1298 capwapBaseWtpProfileWtpEcnSupport INTEGER, 1299 capwapBaseWtpProfileRowStatus RowStatus 1300 } 1302 capwapBaseWtpProfileId OBJECT-TYPE 1303 SYNTAX CapwapBaseWtpProfileIdTC 1304 MAX-ACCESS not-accessible 1305 STATUS current 1306 DESCRIPTION 1307 "Represents the unique identifier of a WTP profile." 1308 ::= { capwapBaseWtpProfileEntry 1 } 1310 capwapBaseWtpProfileName OBJECT-TYPE 1311 SYNTAX SnmpAdminString 1312 MAX-ACCESS read-create 1313 STATUS current 1314 DESCRIPTION 1315 "Represents the name of a WTP profile." 1316 ::= { capwapBaseWtpProfileEntry 2 } 1318 capwapBaseWtpProfileWtpMacAddr OBJECT-TYPE 1319 SYNTAX CapwapBaseWtpIdTC 1320 MAX-ACCESS read-create 1321 STATUS current 1322 DESCRIPTION 1323 "Represents the Base MAC address of a WTP. 1324 A WTP profile MUST contain the Base MAC address of the WTP 1325 because the CAPWAP message received from the WTP contains 1326 its Base MAC address and the AC uses the Base MAC address to 1327 find the corresponding WTP profile. 1328 The section 4.6.40 [RFC5415] does not clarify that the WTP's 1329 Base MAC address MUST be included in the WTP Board Data 1330 message element. This is a known errata item and assumed to be 1331 fixed in future by the editors of the RFC5415." 1332 REFERENCE 1333 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1334 ::= { capwapBaseWtpProfileEntry 3 } 1336 capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE 1337 SYNTAX SnmpAdminString 1338 MAX-ACCESS read-create 1339 STATUS current 1340 DESCRIPTION 1341 "Represents the model number of a WTP. 1342 A WTP profile MUST include the WTP's model number, which 1343 reflects the number of PHY radios on the WTP. 1344 In this way, the creation of a WTP profile triggers the AC 1345 to automatically create the same number of WTP Virtual Radio 1346 Interfaces corresponding to the WTP's PHY radios without 1347 manual intervention. With the ifIndexes of WTP Virtual 1348 Radio Interfaces, the operator could configure and manage 1349 the WTP's PHY radios through the wireless binding MIB 1350 modules." 1351 REFERENCE 1352 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1353 ::= { capwapBaseWtpProfileEntry 4 } 1355 capwapBaseWtpProfileWtpName OBJECT-TYPE 1356 SYNTAX OCTET STRING(SIZE(512)) 1357 MAX-ACCESS read-create 1358 STATUS current 1359 DESCRIPTION 1360 "Represents the name of the WTP." 1361 REFERENCE 1362 "Section 4.6.45. of CAPWAP Protocol Specification, RFC 5415." 1363 ::= { capwapBaseWtpProfileEntry 5 } 1365 capwapBaseWtpProfileWtpLocation OBJECT-TYPE 1366 SYNTAX OCTET STRING(SIZE(1024)) 1367 MAX-ACCESS read-create 1368 STATUS current 1369 DESCRIPTION 1370 "Represents the location of the WTP." 1371 REFERENCE 1372 "Section 4.6.30. of CAPWAP Protocol Specification, RFC 5415." 1373 ::= { capwapBaseWtpProfileEntry 6 } 1375 capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE 1376 SYNTAX TruthValue 1377 MAX-ACCESS read-create 1378 STATUS current 1379 DESCRIPTION 1380 "Represents whether the WTP SHOULD use a static IP address 1381 or not. A value of false disables the static IP address, 1382 while a value of true enables it." 1383 REFERENCE 1384 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1385 ::= { capwapBaseWtpProfileEntry 7 } 1387 capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE 1388 SYNTAX InetAddressType 1389 MAX-ACCESS read-create 1390 STATUS current 1391 DESCRIPTION 1392 "Represents the static IP address type used by the WTP, IPv4 1393 or IPv6." 1394 ::= { capwapBaseWtpProfileEntry 8 } 1396 capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE 1397 SYNTAX InetAddress 1398 MAX-ACCESS read-create 1399 STATUS current 1400 DESCRIPTION 1401 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1402 it represents the static IP address to be assigned to the WTP." 1403 REFERENCE 1404 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1405 ::= { capwapBaseWtpProfileEntry 9 } 1407 capwapBaseWtpProfileWtpNetmask OBJECT-TYPE 1408 SYNTAX InetAddress 1409 MAX-ACCESS read-create 1410 STATUS current 1411 DESCRIPTION 1412 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1413 it represents the netmask to be assigned to the WTP." 1415 REFERENCE 1416 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1417 ::= { capwapBaseWtpProfileEntry 10 } 1419 capwapBaseWtpProfileWtpGateway OBJECT-TYPE 1420 SYNTAX InetAddress 1421 MAX-ACCESS read-create 1422 STATUS current 1423 DESCRIPTION 1424 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1425 it represents the gateway to be assigned to the WTP." 1426 REFERENCE 1427 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1428 ::= { capwapBaseWtpProfileEntry 11 } 1430 capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE 1431 SYNTAX INTEGER { 1432 enabled(1), 1433 disabled(2) 1434 } 1435 MAX-ACCESS read-create 1436 STATUS current 1437 DESCRIPTION 1438 "Represents whether to enable or disable automatic CAPWAP 1439 fallback in the event that a WTP detects its preferred AC, 1440 and is not currently connected to it. 1441 The following enumerated values are supported: 1442 enabled(1) - The fallback mode is enabled 1443 disabled(2) - The fallback mode is disabled" 1444 REFERENCE 1445 "Section 4.6.42. of CAPWAP Protocol Specification, RFC 5415." 1446 DEFVAL { enabled } 1447 ::= { capwapBaseWtpProfileEntry 12 } 1449 capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE 1450 SYNTAX Unsigned32 1451 UNITS "second" 1452 MAX-ACCESS read-create 1453 STATUS current 1454 DESCRIPTION 1455 "Represents the minimum time, in seconds, between sending Echo 1456 Request messages to the AC that the WTP has joined." 1457 REFERENCE 1458 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 1459 DEFVAL { 30 } 1460 ::= { capwapBaseWtpProfileEntry 13 } 1462 capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE 1463 SYNTAX Unsigned32 1464 UNITS "second" 1465 MAX-ACCESS read-create 1466 STATUS current 1467 DESCRIPTION 1468 "Represents the idle timeout value that the WTP SHOULD enforce 1469 for its active stations." 1470 REFERENCE 1471 "Section 4.7.8. of CAPWAP Protocol Specification, RFC 5415." 1472 DEFVAL { 300 } 1473 ::= { capwapBaseWtpProfileEntry 14 } 1475 capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE 1476 SYNTAX Unsigned32 (2..180) 1477 UNITS "second" 1478 MAX-ACCESS read-create 1479 STATUS current 1480 DESCRIPTION 1481 "Represents the maximum time allowed between sending Discovery 1482 Request messages, in seconds." 1483 REFERENCE 1484 "Section 4.7.10. of CAPWAP Protocol Specification, RFC 5415." 1485 DEFVAL { 20 } 1486 ::= { capwapBaseWtpProfileEntry 15 } 1488 capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE 1489 SYNTAX Unsigned32 1490 UNITS "second" 1491 MAX-ACCESS read-create 1492 STATUS current 1493 DESCRIPTION 1494 "Represents the interval for WTP to send Decryption Error 1495 report." 1496 REFERENCE 1497 "Section 4.7.11. of CAPWAP Protocol Specification, RFC 5415." 1498 DEFVAL { 120 } 1499 ::= { capwapBaseWtpProfileEntry 16 } 1501 capwapBaseWtpProfileWtpSilentInterval OBJECT-TYPE 1502 SYNTAX Unsigned32 1503 UNITS "second" 1504 MAX-ACCESS read-create 1505 STATUS current 1506 DESCRIPTION 1507 "Represents the minimum time, in seconds, a WTP MUST wait 1508 before it MAY again send Discovery Request messages or 1509 attempt to a establish DTLS session." 1510 REFERENCE 1511 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 1512 DEFVAL { 30 } 1513 ::= { capwapBaseWtpProfileEntry 17 } 1515 capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE 1516 SYNTAX Unsigned32 1517 UNITS "second" 1518 MAX-ACCESS read-create 1519 STATUS current 1520 DESCRIPTION 1521 "Represents the interval the WTP uses between the WTP Events 1522 Requests it transmits to the AC to communicate its statistics, 1523 in seconds." 1524 REFERENCE 1525 "Section 4.7.14. of CAPWAP Protocol Specification, RFC 5415." 1526 DEFVAL { 120 } 1527 ::= { capwapBaseWtpProfileEntry 18 } 1529 capwapBaseWtpProfileWtpWaitDTLSTimer OBJECT-TYPE 1530 SYNTAX Unsigned32 (30..4294967295) 1531 UNITS "second" 1532 MAX-ACCESS read-create 1533 STATUS current 1534 DESCRIPTION 1535 "Represents the maximum time, in seconds, an AC MUST wait 1536 without having received a DTLS Handshake message from an AC. 1537 This timer MUST be greater than 30 seconds." 1538 REFERENCE 1539 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 1540 DEFVAL { 60 } 1541 ::= { capwapBaseWtpProfileEntry 19 } 1543 capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE 1544 SYNTAX INTEGER { 1545 limited(0), 1546 fullAndLimited(1) 1547 } 1548 MAX-ACCESS read-create 1549 STATUS current 1550 DESCRIPTION 1551 "Represents the support for the Explicit Congestion Notification 1552 (ECN) bits, as defined in [RFC3168]. 1553 The following enumerated values are supported: 1554 limited(0) - Limited ECN support 1555 fullAndLimited(1) - Full and limited ECN support" 1556 REFERENCE 1557 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 1558 ::= { capwapBaseWtpProfileEntry 20 } 1560 capwapBaseWtpProfileRowStatus OBJECT-TYPE 1561 SYNTAX RowStatus 1562 MAX-ACCESS read-create 1563 STATUS current 1564 DESCRIPTION 1565 "This variable is used to create, modify, and/or delete a row 1566 in this table. 1567 Deleting a WTP profile in use will disconnect the WTP to 1568 the AC. So the network management system SHOULD 1569 ask the operator to confirm such an operation. 1570 When a WTP profile entry is removed from the table, 1571 the corresponding WTP Virtual Radio Interfaces are also 1572 removed from the CapwapBaseWirelessBindingTable and 1573 ifTable [RFC2863]. 1574 Also, the related object instances SHOULD be removed from 1575 the wireless binding MIB modules such as IEEE 802.11 1576 MIB module [IEEE.802-11.2007]." 1577 ::= { capwapBaseWtpProfileEntry 21 } 1579 -- End of capwapBaseWtpProfileTable table 1581 -- capwapBaseWtpStateTable table 1583 capwapBaseWtpStateTable OBJECT-TYPE 1584 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 1585 MAX-ACCESS not-accessible 1586 STATUS current 1587 DESCRIPTION 1588 "A table of objects that indicate each WTP's CAPWAP FSM 1589 state, and helps the operator to query the WTPs' current 1590 configuration." 1591 ::= { capwapBaseWtps 2 } 1593 capwapBaseWtpStateEntry OBJECT-TYPE 1594 SYNTAX CapwapBaseWtpStateEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "A set of objects that display the WTP's CAPWAP FSM state. 1599 Also, the operator could query the current configuration 1600 of a WTP by using the identifier of the corresponding 1601 WTP profile." 1602 INDEX { capwapBaseWtpStateWtpId } 1603 ::= { capwapBaseWtpStateTable 1 } 1605 CapwapBaseWtpStateEntry ::= SEQUENCE { 1606 capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, 1607 capwapBaseWtpStateWtpIpAddressType InetAddressType, 1608 capwapBaseWtpStateWtpIpAddress InetAddress, 1609 capwapBaseWtpStateWtpBaseMacAddress PhysAddress, 1610 capwapBaseWtpState INTEGER, 1611 capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC 1612 } 1614 capwapBaseWtpStateWtpId OBJECT-TYPE 1615 SYNTAX CapwapBaseWtpIdTC 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "Represents the unique identifier of a WTP." 1620 ::= { capwapBaseWtpStateEntry 1 } 1622 capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE 1623 SYNTAX InetAddressType 1624 MAX-ACCESS read-only 1625 STATUS current 1626 DESCRIPTION 1627 "Represents the IP address type of a WTP." 1628 ::= { capwapBaseWtpStateEntry 2 } 1630 capwapBaseWtpStateWtpIpAddress OBJECT-TYPE 1631 SYNTAX InetAddress 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "Represents the IP address of a WTP." 1636 ::= { capwapBaseWtpStateEntry 3 } 1638 capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE 1639 SYNTAX PhysAddress 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "Represents the WTP's Base MAC Address, which MAY be 1644 assigned to the primary Ethernet interface." 1645 REFERENCE 1646 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1647 ::= { capwapBaseWtpStateEntry 4 } 1649 capwapBaseWtpState OBJECT-TYPE 1650 SYNTAX INTEGER { 1651 dtls(1), 1652 join(2), 1653 image(3), 1654 configure(4), 1655 dataCheck(5), 1656 run(6), 1657 reset(7), 1658 dtlsTeardown(8), 1659 unknown(9) 1660 } 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "Represents the various possible CAPWAP FSM states of WTP 1665 The following enumerated values are supported: 1666 dtls(1) - DTLS negotiation states, which include 1667 DTLS setup, authorize, DTLS connect 1668 join(2) - The WTP is joining with the AC 1669 image(3) - The WTP is downloading software 1670 configure(4) - The WTP is getting configuration from 1671 the AC 1672 dataCheck(5) - The AC is waiting for the Data Channel Keep 1673 Alive Packet 1674 run(6) - The WTP enters the running state 1675 reset(7) - The AC transmits a reset request message 1676 to the WTP 1677 dtlsTeardown(8) - DTLS session is tear down 1678 unknown(9) - Operator already prepared configuration 1679 for the WTP, while the WTP has not contact 1680 with the AC till now" 1681 REFERENCE 1682 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 1683 ::= { capwapBaseWtpStateEntry 5 } 1685 capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE 1686 SYNTAX CapwapBaseWtpProfileIdTC 1687 MAX-ACCESS read-only 1688 STATUS current 1689 DESCRIPTION 1690 "Represents the current identifier of a WTP profile. 1691 The operator could query a WTP's current configuration 1692 with the identifier of a WTP profile." 1693 ::= { capwapBaseWtpStateEntry 6 } 1695 -- End of capwapBaseWtpStateTable Table 1697 -- capwapBaseWtpTable Table 1699 capwapBaseWtpTable OBJECT-TYPE 1700 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1701 MAX-ACCESS not-accessible 1702 STATUS current 1703 DESCRIPTION 1704 "A table of objects that display properties of the WTPs 1705 in running state." 1706 ::= { capwapBaseWtps 3 } 1708 capwapBaseWtpEntry OBJECT-TYPE 1709 SYNTAX CapwapBaseWtpEntry 1710 MAX-ACCESS not-accessible 1711 STATUS current 1712 DESCRIPTION 1713 "A set of objects that display properties of the WTPs 1714 in running state." 1715 INDEX { capwapBaseWtpCurrId } 1716 ::= { capwapBaseWtpTable 1 } 1718 CapwapBaseWtpEntry ::= SEQUENCE { 1719 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1720 capwapBaseWtpPhyIndex PhysicalIndex, 1721 capwapBaseWtpBaseMacAddress PhysAddress, 1722 capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, 1723 capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, 1724 capwapBaseWtpDiscoveryType INTEGER, 1725 capwapBaseWtpRadiosInUseNum Unsigned32, 1726 capwapBaseWtpRadioNumLimit Unsigned32, 1727 capwapBaseWtpRetransmitCount Counter32, 1728 capwapBaseWtpMaxDiscoveries Unsigned32, 1729 capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, 1730 capwapBaseWtpMaxRetransmit Unsigned32, 1731 capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, 1732 capwapBaseWtpDataChannelDeadInterval Unsigned32, 1733 capwapBaseWtpDiscoveryInterval Unsigned32, 1734 capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, 1735 capwapBaseWtpImageDataStartTimer Unsigned32, 1736 capwapBaseWtpRetransmitInterval Unsigned32 1737 } 1739 capwapBaseWtpCurrId OBJECT-TYPE 1740 SYNTAX CapwapBaseWtpIdTC 1741 MAX-ACCESS not-accessible 1742 STATUS current 1743 DESCRIPTION 1744 "Represents the unique identifier of a WTP in running state." 1745 ::= { capwapBaseWtpEntry 1 } 1747 capwapBaseWtpPhyIndex OBJECT-TYPE 1748 SYNTAX PhysicalIndex 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "Represents the unique physical index of a physical entity 1753 in the ENTITY-MIB module [RFC4133]. 1754 The information such as software version of a specific WTP 1755 could be accessed through the index." 1756 ::= { capwapBaseWtpEntry 2 } 1758 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1759 SYNTAX PhysAddress 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "Represents the WTP's Base MAC Address, which MAY be assigned 1764 to the primary Ethernet interface." 1765 REFERENCE 1766 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1767 ::= { capwapBaseWtpEntry 3 } 1769 capwapBaseWtpTunnelModeOptions OBJECT-TYPE 1770 SYNTAX CapwapBaseTunnelModeTC 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "Represents the tunneling modes of operation supported by 1775 the WTP." 1776 REFERENCE 1777 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 1778 ::= { capwapBaseWtpEntry 4 } 1780 capwapBaseWtpMacTypeOptions OBJECT-TYPE 1781 SYNTAX CapwapBaseMacTypeTC 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "Represents the MAC mode of operation supported by the WTP." 1786 REFERENCE 1787 "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." 1788 ::= { capwapBaseWtpEntry 5 } 1790 capwapBaseWtpDiscoveryType OBJECT-TYPE 1791 SYNTAX INTEGER { 1792 unknown(0), 1793 staticConfig(1), 1794 dhcp(2), 1795 dns(3), 1796 acRef(4) 1797 } 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "Represents how the WTP discovers the AC. 1803 The following enumerated values are supported: 1804 unknown(0) - Unknown 1805 staticConfig(1) - Static configuration 1806 dhcp(2) - DHCP 1807 dns(3) - DNS 1808 acRef(4) - AC referral" 1809 REFERENCE 1810 "Section 4.6.21. of CAPWAP Protocol Specification, RFC 5415." 1811 ::= { capwapBaseWtpEntry 6 } 1813 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1814 SYNTAX Unsigned32 (0..255) 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "Represents the number of radios in use on the WTP." 1819 REFERENCE 1820 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1821 ::= { capwapBaseWtpEntry 7 } 1823 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1824 SYNTAX Unsigned32 (0..255) 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "Represents the maximum radio number supported by the WTP." 1829 REFERENCE 1830 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1831 ::= { capwapBaseWtpEntry 8 } 1833 capwapBaseWtpRetransmitCount OBJECT-TYPE 1834 SYNTAX Counter32 1835 UNITS "retransmissions" 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "Represents the number of retransmissions for a given 1840 CAPWAP packet." 1841 REFERENCE 1842 "Section 4.8.8. of CAPWAP Protocol Specification, RFC 5415." 1843 ::= { capwapBaseWtpEntry 9 } 1845 capwapBaseWtpMaxDiscoveries OBJECT-TYPE 1846 SYNTAX Unsigned32 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "Represents the maximum number of Discovery Request messages 1851 that will be sent after a WTP boots." 1852 REFERENCE 1853 "Section 4.8.5. of CAPWAP Protocol Specification, RFC 5415." 1854 DEFVAL { 10 } 1855 ::= { capwapBaseWtpEntry 10 } 1857 capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE 1858 SYNTAX Unsigned32 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "Represents the maximum number of failed DTLS session 1863 establishment attempts before the CAPWAP device enters a 1864 silent period." 1865 REFERENCE 1866 "Section 4.8.6. of CAPWAP Protocol Specification, RFC 5415." 1867 DEFVAL { 3 } 1868 ::= { capwapBaseWtpEntry 11 } 1870 capwapBaseWtpMaxRetransmit OBJECT-TYPE 1871 SYNTAX Unsigned32 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "Represents the maximum number of retransmission for a given 1876 CAPWAP packet before the link layer considers the peer dead." 1877 REFERENCE 1878 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 1879 DEFVAL { 5 } 1880 ::= { capwapBaseWtpEntry 12 } 1882 capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE 1883 SYNTAX Unsigned32 1884 UNITS "second" 1885 MAX-ACCESS read-only 1886 STATUS current 1887 DESCRIPTION 1888 "Represents the next opportunity, in seconds, the WTP must 1889 transmit the Data Channel Keep Alive message." 1890 REFERENCE 1891 "Section 4.7.2. of CAPWAP Protocol Specification, RFC 5415." 1892 DEFVAL { 30 } 1893 ::= { capwapBaseWtpEntry 13 } 1895 capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE 1896 SYNTAX Unsigned32 (0..240) 1897 UNITS "second" 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "Represents the minimum time, in seconds, a WTP MUST wait 1902 without having received a Data Channel Keep Alive packet 1903 before the destination for the Data Channel Keep Alive 1904 packets MAY be considered dead." 1905 REFERENCE 1906 "Section 4.7.3. of CAPWAP Protocol Specification, RFC 5415." 1907 DEFVAL { 60 } 1908 ::= { capwapBaseWtpEntry 14 } 1910 capwapBaseWtpDiscoveryInterval OBJECT-TYPE 1911 SYNTAX Unsigned32 1912 UNITS "second" 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "Represents the minimum time, in seconds, that a WTP MUST 1917 wait after receiving a Discovery Response message, before 1918 initiating a DTLS handshake." 1919 REFERENCE 1920 "Section 4.7.5. of CAPWAP Protocol Specification, RFC 5415." 1921 DEFVAL { 5 } 1922 ::= { capwapBaseWtpEntry 15 } 1924 capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE 1925 SYNTAX Unsigned32 1926 UNITS "second" 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "Represents the minimum time, in seconds, a WTP MUST wait 1931 for DTLS session deletion." 1932 REFERENCE 1933 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 1934 DEFVAL { 5 } 1935 ::= { capwapBaseWtpEntry 16 } 1937 capwapBaseWtpImageDataStartTimer OBJECT-TYPE 1938 SYNTAX Unsigned32 1939 UNITS "second" 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "Represents the number of seconds the WTP will wait for its 1944 peer to transmit the Image Data Request." 1945 REFERENCE 1946 "Section 4.7.9. of CAPWAP Protocol Specification, RFC 5415." 1947 DEFVAL { 30 } 1948 ::= { capwapBaseWtpEntry 17 } 1950 capwapBaseWtpRetransmitInterval OBJECT-TYPE 1951 SYNTAX Unsigned32 1952 UNITS "second" 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "Represents the minimum time, in seconds, in which a 1957 non-acknowledged CAPWAP packet will be retransmitted." 1958 REFERENCE 1959 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 1960 DEFVAL { 3 } 1961 ::= { capwapBaseWtpEntry 18 } 1963 -- End of capwapBaseWtpTable table 1965 -- capwapBaseWirelessBindingTable Table 1967 capwapBaseWirelessBindingTable OBJECT-TYPE 1968 SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry 1969 MAX-ACCESS not-accessible 1970 STATUS current 1971 DESCRIPTION 1972 "A table of objects that display the mappings between 1973 WTP Virtual Radio Interfaces and PHY radios, and the 1974 wireless binding type for each PHY radio. 1975 Values of all objects in this table are persistent at 1976 restart/reboot." 1977 ::= { capwapBaseWtps 4 } 1979 capwapBaseWirelessBindingEntry OBJECT-TYPE 1980 SYNTAX CapwapBaseWirelessBindingEntry 1981 MAX-ACCESS not-accessible 1982 STATUS current 1983 DESCRIPTION 1984 "A set of objects that display the mapping between 1985 a specific WTP Virtual Radio Interface and a PHY 1986 radio, and the wireless binding type for the PHY radio." 1987 INDEX { 1988 capwapBaseWtpProfileId, 1989 capwapBaseWirelessBindingRadioId 1991 } 1992 ::= { capwapBaseWirelessBindingTable 1 } 1994 CapwapBaseWirelessBindingEntry ::= SEQUENCE { 1995 capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, 1996 capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, 1997 capwapBaseWirelessBindingType INTEGER 1998 } 2000 capwapBaseWirelessBindingRadioId OBJECT-TYPE 2001 SYNTAX CapwapBaseRadioIdTC 2002 MAX-ACCESS not-accessible 2003 STATUS current 2004 DESCRIPTION 2005 "Represents the identifier of a PHY radio on a WTP, which 2006 is required to be unique on a WTP. 2007 For example, WTP A and WTP B use a same value of 2008 capwapBaseWirelessBindingRadioId for their first radio." 2009 REFERENCE 2010 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2011 ::= { capwapBaseWirelessBindingEntry 1 } 2013 capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE 2014 SYNTAX InterfaceIndex 2015 MAX-ACCESS read-only 2016 STATUS current 2017 DESCRIPTION 2018 "Represents the index value that uniquely identifies a 2019 WLAN Virtual Radio Interface. The interface identified by 2020 a particular value of this index is the same interface as 2021 identified by the same value of the ifIndex. 2022 Before WTPs contact the AC to get configuration, 2023 the operator configures WTP profiles for them. 2024 The creation of a WTP profile triggers system to automatically 2025 create a specific number of WTP Virtual Radio Interfaces and 2026 add a new row object in the capwapBaseWirelessBindingTable 2027 without manual intervention. 2028 As most MIB modules use the ifIndex to identify an interface 2029 for configuration and statistic data, for example, IEEE 802.11 2030 MIB module [IEEE.802-11.2007] 2031 It will be easy to reuse other wireless binding MIB modules 2032 through the WTP Virtual Radio Interface in the Centralized 2033 WLAN Architecture." 2034 ::= { capwapBaseWirelessBindingEntry 2 } 2036 capwapBaseWirelessBindingType OBJECT-TYPE 2037 SYNTAX INTEGER { 2038 dot11(1), 2039 epc(3) 2040 } 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "Represents the wireless binding type for the radio. 2045 The following enumerated values are supported: 2046 dot11(1) - IEEE 802.11 2047 epc(3) - EPCGlobal" 2048 REFERENCE 2049 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2050 ::= { capwapBaseWirelessBindingEntry 3 } 2052 -- End of capwapBaseWirelessBindingTable Table 2054 -- capwapBaseStationTable Table 2056 capwapBaseStationTable OBJECT-TYPE 2057 SYNTAX SEQUENCE OF CapwapBaseStationEntry 2058 MAX-ACCESS not-accessible 2059 STATUS current 2060 DESCRIPTION 2061 "A table of objects that display stations which are accessing 2062 the wireless service provided by the AC." 2063 REFERENCE 2064 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2065 ::= { capwapBaseWtps 5 } 2067 capwapBaseStationEntry OBJECT-TYPE 2068 SYNTAX CapwapBaseStationEntry 2069 MAX-ACCESS not-accessible 2070 STATUS current 2071 DESCRIPTION 2072 "A set of objects that display a station which is 2073 associated with the specific radio on the WTP." 2074 INDEX { 2075 capwapBaseWtpCurrId, 2076 capwapBaseWirelessBindingRadioId, 2077 capwapBaseStationId 2078 } 2079 ::= { capwapBaseStationTable 1 } 2081 CapwapBaseStationEntry ::= SEQUENCE { 2082 capwapBaseStationId CapwapBaseStationIdTC, 2083 capwapBaseStationAddedTime DateAndTime, 2084 capwapBaseStationVlanName SnmpAdminString 2085 } 2087 capwapBaseStationId OBJECT-TYPE 2088 SYNTAX CapwapBaseStationIdTC 2089 MAX-ACCESS not-accessible 2090 STATUS current 2091 DESCRIPTION 2092 "Represents the unique identifier of the station." 2093 REFERENCE 2094 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2095 ::= { capwapBaseStationEntry 1 } 2097 capwapBaseStationAddedTime OBJECT-TYPE 2098 SYNTAX DateAndTime 2099 MAX-ACCESS read-only 2100 STATUS current 2101 DESCRIPTION 2102 "Represents the time when the station is added." 2103 REFERENCE 2104 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2105 ::= { capwapBaseStationEntry 2 } 2107 capwapBaseStationVlanName OBJECT-TYPE 2108 SYNTAX SnmpAdminString (SIZE (0..32)) 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "Represents VLAN name to which the station is associated." 2113 REFERENCE 2114 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2115 ::= { capwapBaseStationEntry 3 } 2117 -- End of capwapBaseStationTable Table 2119 -- capwapBaseWtpEventsStatsTable 2121 capwapBaseWtpEventsStatsTable OBJECT-TYPE 2122 SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry 2123 MAX-ACCESS not-accessible 2124 STATUS current 2125 DESCRIPTION 2126 "A table of objects that display the WTPs' events statistics." 2127 REFERENCE 2128 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2129 ::= { capwapBaseWtps 6 } 2131 capwapBaseWtpEventsStatsEntry OBJECT-TYPE 2132 SYNTAX CapwapBaseWtpEventsStatsEntry 2133 MAX-ACCESS not-accessible 2134 STATUS current 2135 DESCRIPTION 2136 "A set of objects that display the events statistic data 2137 of a WTP." 2138 REFERENCE 2139 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2140 INDEX { capwapBaseWtpCurrId } 2141 ::= { capwapBaseWtpEventsStatsTable 1 } 2143 CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { 2144 capwapBaseWtpEventsStatsRebootCount Counter32, 2145 capwapBaseWtpEventsStatsInitCount Counter32, 2146 capwapBaseWtpEventsStatsLinkFailureCount Counter32, 2147 capwapBaseWtpEventsStatsSwFailureCount Counter32, 2148 capwapBaseWtpEventsStatsHwFailureCount Counter32, 2149 capwapBaseWtpEventsStatsOtherFailureCount Counter32, 2150 capwapBaseWtpEventsStatsUnknownFailureCount Counter32, 2151 capwapBaseWtpEventsStatsLastFailureType INTEGER 2152 } 2154 capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE 2155 SYNTAX Counter32 2156 MAX-ACCESS read-only 2157 STATUS current 2158 DESCRIPTION 2159 "Represents the number of reboots that have occurred due to a 2160 WTP crash. A value of 65535 implies that this information is 2161 not available on the WTP." 2162 REFERENCE 2163 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2164 ::= { capwapBaseWtpEventsStatsEntry 1 } 2166 capwapBaseWtpEventsStatsInitCount OBJECT-TYPE 2167 SYNTAX Counter32 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "Represents the number of reboots that have occurred at the 2172 request of a CAPWAP protocol message, such as a change in 2173 configuration that requires a reboot or an explicit CAPWAP 2174 protocol reset request. A value of 65535 implies that this 2175 information is not available on the WTP." 2176 REFERENCE 2177 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2178 ::= { capwapBaseWtpEventsStatsEntry 2 } 2180 capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE 2181 SYNTAX Counter32 2182 MAX-ACCESS read-only 2183 STATUS current 2184 DESCRIPTION 2185 "Represents the number of times that a CAPWAP protocol 2186 connection with an AC has failed due to link failures." 2187 REFERENCE 2188 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2189 ::= { capwapBaseWtpEventsStatsEntry 3 } 2191 capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE 2192 SYNTAX Counter32 2193 MAX-ACCESS read-only 2194 STATUS current 2195 DESCRIPTION 2196 "Represents the number of times that a CAPWAP protocol 2197 connection with an AC has failed due to software related 2198 reasons." 2199 REFERENCE 2200 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2201 ::= { capwapBaseWtpEventsStatsEntry 4 } 2203 capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE 2204 SYNTAX Counter32 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "Represents the number of times that a CAPWAP protocol 2209 connection with an AC has failed due to hardware related 2210 reasons." 2211 REFERENCE 2212 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2213 ::= { capwapBaseWtpEventsStatsEntry 5 } 2215 capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE 2216 SYNTAX Counter32 2217 MAX-ACCESS read-only 2218 STATUS current 2219 DESCRIPTION 2220 "Represents the number of times that a CAPWAP protocol 2221 connection with an AC has failed due to known reasons, other 2222 than the AC initiated, link, software or hardware failures." 2223 REFERENCE 2224 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2225 ::= { capwapBaseWtpEventsStatsEntry 6 } 2227 capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE 2228 SYNTAX Counter32 2229 MAX-ACCESS read-only 2230 STATUS current 2231 DESCRIPTION 2232 "Represents the number of times that a CAPWAP protocol 2233 connection with an AC has failed for unknown reasons." 2234 REFERENCE 2235 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2236 ::= { capwapBaseWtpEventsStatsEntry 7 } 2238 capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE 2239 SYNTAX INTEGER { 2240 notSupport(0), 2241 acInit(1), 2242 linkFailure(2), 2243 swFailure(3), 2244 hwFailure(4), 2245 otherFailure(5), 2246 unknown(255) 2247 } 2248 MAX-ACCESS read-only 2249 STATUS current 2250 DESCRIPTION 2251 "Represents the failure type of the most recent WTP failure. 2252 The following enumerated values are supported: 2253 notSupport(0) - Not supported 2254 acInit(1) - The AC initiated 2255 linkFailure(2) - Link failure 2256 swFailure(3) - Software failure 2257 hwFailure(4) - Hardware failure 2258 otherFailure(5) - Other failure 2259 unknown(255) - Unknown (e.g., WTP doesn't keep track 2260 of info)" 2261 REFERENCE 2262 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2263 ::= { capwapBaseWtpEventsStatsEntry 8 } 2265 -- End of capwapBaseWtpEventsStatsTable table 2267 -- capwapBaseRadioEventsStatsTable table 2269 capwapBaseRadioEventsStatsTable OBJECT-TYPE 2270 SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry 2271 MAX-ACCESS not-accessible 2272 STATUS current 2273 DESCRIPTION 2274 "A table of objects that display statistics on radios behavior, 2275 and reasons why the WTP radio has been reset." 2276 REFERENCE 2277 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2278 ::= { capwapBaseWtps 7 } 2280 capwapBaseRadioEventsStatsEntry OBJECT-TYPE 2281 SYNTAX CapwapBaseRadioEventsStatsEntry 2282 MAX-ACCESS not-accessible 2283 STATUS current 2284 DESCRIPTION 2285 "A set of objects that display the statistic data of 2286 events happened on a specific radio of a WTP." 2287 INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId } 2288 ::= { capwapBaseRadioEventsStatsTable 1 } 2290 CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { 2291 capwapBaseRadioEventsStatsResetCount Counter32, 2292 capwapBaseRadioEventsStatsSwFailCount Counter32, 2293 capwapBaseRadioEventsStatsHwFailCount Counter32, 2294 capwapBaseRadioEventsStatsOtherFailCount Counter32, 2295 capwapBaseRadioEventsStatsUnknownFailCount Counter32, 2296 capwapBaseRadioEventsStatsConfigUpdateCount Counter32, 2297 capwapBaseRadioEventsStatsChannelChangeCount Counter32, 2298 capwapBaseRadioEventsStatsBandChangeCount Counter32, 2299 capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, 2300 capwapBaseRadioEventsStatsDecryptErrorCount Counter32, 2301 capwapBaseRadioEventsStatsLastFailType INTEGER 2302 } 2304 capwapBaseRadioEventsStatsResetCount OBJECT-TYPE 2305 SYNTAX Counter32 2306 MAX-ACCESS read-only 2307 STATUS current 2308 DESCRIPTION 2309 "Represents the number of times that that the radio has been 2310 reset." 2311 REFERENCE 2312 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2313 ::= { capwapBaseRadioEventsStatsEntry 1 } 2315 capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE 2316 SYNTAX Counter32 2317 MAX-ACCESS read-only 2318 STATUS current 2319 DESCRIPTION 2320 "Represents the number of times that the radio has failed due 2321 to software related reasons." 2322 REFERENCE 2323 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2324 ::= { capwapBaseRadioEventsStatsEntry 2 } 2326 capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE 2327 SYNTAX Counter32 2328 MAX-ACCESS read-only 2329 STATUS current 2330 DESCRIPTION 2331 "Represents the number of times that the radio has failed due 2332 to hardware related reasons." 2333 REFERENCE 2334 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2335 ::= { capwapBaseRadioEventsStatsEntry 3 } 2337 capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE 2338 SYNTAX Counter32 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "Represents the number of times that the radio has failed due to 2343 known reasons, other than software or hardware failure." 2344 REFERENCE 2345 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2346 ::= { capwapBaseRadioEventsStatsEntry 4 } 2348 capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE 2349 SYNTAX Counter32 2350 MAX-ACCESS read-only 2351 STATUS current 2352 DESCRIPTION 2353 "Represents the number of times that the radio has failed for 2354 unknown reasons." 2355 REFERENCE 2356 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2357 ::= { capwapBaseRadioEventsStatsEntry 5 } 2359 capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE 2360 SYNTAX Counter32 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 "Represents the number of times that the radio configuration has 2365 been updated." 2366 REFERENCE 2367 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2368 ::= { capwapBaseRadioEventsStatsEntry 6 } 2370 capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE 2371 SYNTAX Counter32 2372 MAX-ACCESS read-only 2373 STATUS current 2374 DESCRIPTION 2375 "Represents the number of times that the radio channel has 2376 been changed." 2377 REFERENCE 2378 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2379 ::= { capwapBaseRadioEventsStatsEntry 7 } 2381 capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE 2382 SYNTAX Counter32 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 "Represents the number of times that the radio has changed 2387 frequency bands." 2388 REFERENCE 2389 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2390 ::= { capwapBaseRadioEventsStatsEntry 8 } 2392 capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE 2393 SYNTAX Integer32 2394 UNITS "dBm" 2395 MAX-ACCESS read-only 2396 STATUS current 2397 DESCRIPTION 2398 "Represents the noise floor of the radio receiver in units of 2399 dBm." 2400 REFERENCE 2401 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2402 ::= { capwapBaseRadioEventsStatsEntry 9 } 2404 capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE 2405 SYNTAX Counter32 2406 MAX-ACCESS read-only 2407 STATUS current 2408 DESCRIPTION 2409 "Represents the number of decryption errors that have occurred 2410 on the WTP. Note that this field is only valid in cases where 2411 the WTP provides encryption/decryption services." 2412 REFERENCE 2413 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2414 ::= { capwapBaseRadioEventsStatsEntry 10 } 2416 capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE 2417 SYNTAX INTEGER { 2418 notSupport(0), 2419 swFailure(1), 2420 hwFailure(2), 2421 otherFailure(3), 2422 unknown(255) 2423 } 2424 MAX-ACCESS read-only 2425 STATUS current 2426 DESCRIPTION 2427 "Represents the failure type of the most recent radio failure. 2428 The following enumerated values are supported: 2429 notSupport(0) - Not supported 2430 swFailure(1) - Software failure 2431 hwFailure(2) - Hardware failure 2432 otherFailure(3) - Other failure 2433 unknown(255) - Unknown" 2434 REFERENCE 2435 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2436 ::= { capwapBaseRadioEventsStatsEntry 11 } 2438 -- End of capwapBaseRadioEventsStatsTable table 2440 -- End of WTP Objects Group 2442 -- CAPWAP Base Parameters Group 2444 capwapBaseParameters OBJECT IDENTIFIER 2445 ::= { capwapBaseObjects 3 } 2447 capwapBaseAcMaxRetransmit OBJECT-TYPE 2448 SYNTAX Unsigned32 2449 MAX-ACCESS read-write 2450 STATUS current 2451 DESCRIPTION 2452 "Represents the maximum number of retransmissions for a given 2453 CAPWAP packet before the link layer considers the peer dead. 2454 The value of the object is persistent at restart/reboot." 2455 REFERENCE 2456 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 2457 DEFVAL { 5 } 2458 ::= { capwapBaseParameters 1 } 2460 capwapBaseAcChangeStatePendingTimer OBJECT-TYPE 2461 SYNTAX Unsigned32 2462 UNITS "second" 2463 MAX-ACCESS read-write 2464 STATUS current 2465 DESCRIPTION 2466 "Represents the maximum time, in seconds, the AC will wait 2467 for the Change State Event Request from the WTP after having 2468 transmitted a successful Configuration Status Response 2469 message. 2470 The value of the object is persistent at restart/reboot." 2471 REFERENCE 2472 "Section 4.7.1. of CAPWAP Protocol Specification, RFC 5415." 2473 DEFVAL { 25 } 2474 ::= { capwapBaseParameters 2 } 2476 capwapBaseAcDataCheckTimer OBJECT-TYPE 2477 SYNTAX Unsigned32 2478 UNITS "second" 2479 MAX-ACCESS read-write 2480 STATUS current 2481 DESCRIPTION 2482 "Represents The number of seconds the AC will wait for 2483 the Data Channel Keep Alive, which is required by the 2484 CAPWAP state machine's Data Check state. 2485 The AC resets the state machine if this timer expires 2486 prior to transitioning to the next state. 2487 The value of the object is persistent at restart/reboot." 2488 REFERENCE 2489 "Section 4.7.4. of CAPWAP Protocol Specification, RFC 5415." 2490 DEFVAL { 30 } 2491 ::= { capwapBaseParameters 3 } 2493 capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE 2494 SYNTAX Unsigned32 2495 UNITS "second" 2496 MAX-ACCESS read-write 2497 STATUS current 2498 DESCRIPTION 2499 "Represents the minimum time, in seconds, the AC MUST wait 2500 for DTLS session deletion. 2501 The value of the object is persistent at restart/reboot." 2502 REFERENCE 2503 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 2504 DEFVAL { 5 } 2505 ::= { capwapBaseParameters 4 } 2507 capwapBaseAcEchoInterval OBJECT-TYPE 2508 SYNTAX Unsigned32 2509 UNITS "second" 2510 MAX-ACCESS read-write 2511 STATUS current 2512 DESCRIPTION 2513 "Represents the minimum time, in seconds, between sending Echo 2514 Request messages to the AC with which the WTP has joined. 2515 The value of the object is persistent at restart/reboot." 2516 REFERENCE 2517 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 2518 DEFVAL { 30 } 2519 ::= { capwapBaseParameters 5 } 2521 capwapBaseAcRetransmitInterval OBJECT-TYPE 2522 SYNTAX Unsigned32 2523 UNITS "second" 2524 MAX-ACCESS read-write 2525 STATUS current 2526 DESCRIPTION 2527 "Represents the minimum time, in seconds, in which a 2528 non-acknowledged CAPWAP packet will be retransmitted. 2529 The value of the object is persistent at restart/reboot." 2530 REFERENCE 2531 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 2532 DEFVAL { 3 } 2533 ::= { capwapBaseParameters 6 } 2535 capwapBaseAcSilentInterval OBJECT-TYPE 2536 SYNTAX Unsigned32 2537 UNITS "second" 2538 MAX-ACCESS read-write 2539 STATUS current 2540 DESCRIPTION 2541 "Represents the minimum time, in seconds, during which the AC 2542 SHOULD ignore all CAPWAP and DTLS packets received from the 2543 WTP that is in the Sulking state. 2544 The value of the object is persistent at restart/reboot." 2545 REFERENCE 2546 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 2547 DEFVAL { 30 } 2548 ::= { capwapBaseParameters 7 } 2550 capwapBaseAcWaitDTLSTimer OBJECT-TYPE 2551 SYNTAX Unsigned32 (30..4294967295) 2552 UNITS "second" 2553 MAX-ACCESS read-write 2554 STATUS current 2555 DESCRIPTION 2556 "Represents the maximum time, in seconds, the AC MUST wait 2557 without having received a DTLS Handshake message from an AC. 2558 This timer MUST be greater than 30 seconds. 2559 The value of the object is persistent at restart/reboot." 2560 REFERENCE 2561 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 2562 DEFVAL { 60 } 2563 ::= { capwapBaseParameters 8 } 2565 capwapBaseAcWaitJoinTimer OBJECT-TYPE 2566 SYNTAX Unsigned32 (20..4294967295) 2567 UNITS "second" 2568 MAX-ACCESS read-write 2569 STATUS current 2570 DESCRIPTION 2571 "Represents the maximum time, in seconds, the AC will wait 2572 after the DTLS session has been established until it receives 2573 the Join Request from the WTP. This timer MUST be greater 2574 than 20 seconds. 2575 The value of the object is persistent at restart/reboot." 2576 REFERENCE 2577 "Section 4.7.16. of CAPWAP Protocol Specification, RFC 5415." 2578 DEFVAL { 60 } 2579 ::= { capwapBaseParameters 9 } 2581 capwapBaseAcEcnSupport OBJECT-TYPE 2582 SYNTAX INTEGER { 2583 limited(0), 2584 fullAndLimited(1) 2585 } 2586 MAX-ACCESS read-write 2587 STATUS current 2588 DESCRIPTION 2589 "Represents the support for the Explicit Congestion Notification 2590 (ECN) bits, as defined in [RFC3168]. 2591 The value of the object is persistent at restart/reboot. 2592 The following enumerated values are supported: 2593 limited(0) - Limited ECN support 2594 fullAndLimited(1) - Full and limited ECN support" 2595 REFERENCE 2596 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 2597 ::= { capwapBaseParameters 10 } 2599 -- End of CAPWAP Base Parameters Group 2601 -- CAPWAP Statistics Group 2603 capwapBaseStats OBJECT IDENTIFIER 2604 ::= { capwapBaseObjects 4 } 2606 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 2607 SYNTAX Counter32 2608 MAX-ACCESS read-only 2609 STATUS current 2610 DESCRIPTION 2611 "Represents the number of failed DTLS session establishment 2612 attempts due to authentication failures." 2613 REFERENCE 2614 "Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415." 2615 ::= { capwapBaseStats 1 } 2617 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 2618 SYNTAX Counter32 2619 MAX-ACCESS read-only 2620 STATUS current 2621 DESCRIPTION 2622 "Represents the number of failed DTLS session 2623 establishment attempts." 2624 REFERENCE 2625 "Section 4.8.4. of CAPWAP Protocol Specification, RFC 5415." 2626 ::= { capwapBaseStats 2 } 2628 -- Notifications 2630 capwapBaseChannelUp NOTIFICATION-TYPE 2631 OBJECTS { 2632 capwapBaseNtfWtpId, 2633 capwapBaseNtfChannelType, 2634 capwapBaseNtfAuthenMethod 2635 } 2636 STATUS current 2637 DESCRIPTION 2638 "This notification is sent by the AC when a CAPWAP channel 2639 established. 2640 The notification is separated for data or control channel." 2641 ::= { capwapBaseNotifications 1 } 2643 capwapBaseChannelDown NOTIFICATION-TYPE 2644 OBJECTS { 2645 capwapBaseNtfWtpId, 2646 capwapBaseNtfChannelType, 2647 capwapBaseNtfChannelDownReason 2648 } 2649 STATUS current 2650 DESCRIPTION 2651 "This notification is sent by the AC when CAPWAP channel 2652 becomes down. 2653 The notification is separated for data or control channel." 2654 ::= { capwapBaseNotifications 2 } 2656 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 2657 OBJECTS { 2658 capwapBaseNtfWtpId, 2659 capwapBaseNtfRadioId, 2660 capwapBaseNtfStationIdList 2661 } 2662 STATUS current 2663 DESCRIPTION 2664 "This notification is generated when a WTP that has occurred 2665 decryption error since the last report." 2666 REFERENCE 2667 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2668 ::= { capwapBaseNotifications 3 } 2670 capwapBaseJoinFailure NOTIFICATION-TYPE 2671 OBJECTS { 2672 capwapBaseNtfWtpId, 2673 capwapBaseNtfJoinFailureReason 2674 } 2675 STATUS current 2676 DESCRIPTION 2677 "This notification is generated when a WTP fails to join." 2678 REFERENCE 2679 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2680 ::= { capwapBaseNotifications 4 } 2682 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 2683 OBJECTS { 2684 capwapBaseNtfWtpId, 2685 capwapBaseNtfImageFailureReason 2686 } 2687 STATUS current 2688 DESCRIPTION 2689 "This notification is generated when a WTP fails to update 2690 the firmware image." 2691 REFERENCE 2692 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2693 ::= { capwapBaseNotifications 5 } 2695 capwapBaseConfigMsgError NOTIFICATION-TYPE 2696 OBJECTS { 2697 capwapBaseNtfWtpId, 2698 capwapBaseNtfConfigMsgErrorType, 2699 capwapBaseNtfMsgErrorElements 2700 } 2701 STATUS current 2702 DESCRIPTION 2703 "This notification is generated when a WTP receives message 2704 elements in the configuration management messages which it 2705 is unable to apply locally." 2706 REFERENCE 2707 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2709 ::= { capwapBaseNotifications 6 } 2711 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2712 OBJECTS { 2713 capwapBaseNtfWtpId, 2714 capwapBaseNtfRadioId, 2715 capwapBaseNtfRadioOperStatusFlag, 2716 capwapBaseNtfRadioStatusCause 2717 } 2718 STATUS current 2719 DESCRIPTION 2720 "The notification is generated when a radio's operational state 2721 is changed." 2722 REFERENCE 2723 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2724 ::= { capwapBaseNotifications 7 } 2726 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2727 OBJECTS { 2728 capwapBaseNtfWtpId, 2729 capwapBaseNtfChannelType, 2730 capwapBaseNtfAuthenMethod, 2731 capwapBaseNtfAuthenFailureReason 2732 } 2733 STATUS current 2734 DESCRIPTION 2735 "The notification notifies an authentication failure event, 2736 and provides the reason for it." 2737 ::= { capwapBaseNotifications 8 } 2739 -- Objects used only in notifications 2741 -- for notifications 2742 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2743 ::= { capwapBaseObjects 5 } 2745 capwapBaseNtfWtpId OBJECT-TYPE 2746 SYNTAX CapwapBaseWtpIdTC 2747 MAX-ACCESS accessible-for-notify 2748 STATUS current 2749 DESCRIPTION 2750 "Represents the unique identifier of a WTP." 2751 ::= { capwapBaseNotifyVarObjects 1 } 2753 capwapBaseNtfRadioId OBJECT-TYPE 2754 SYNTAX CapwapBaseRadioIdTC 2755 MAX-ACCESS accessible-for-notify 2756 STATUS current 2757 DESCRIPTION 2758 "Represents the identifier of a PHY radio on a WTP, which is 2759 only required to be unique on a WTP. 2760 For example, WTP A and WTP B can use the same value of 2761 capwapBaseNtfRadioId for their first radio." 2762 REFERENCE 2763 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2764 ::= { capwapBaseNotifyVarObjects 2 } 2766 capwapBaseNtfChannelType OBJECT-TYPE 2767 SYNTAX CapwapBaseChannelTypeTC 2768 MAX-ACCESS accessible-for-notify 2769 STATUS current 2770 DESCRIPTION 2771 "Represents the channel type for CAPWAP protocol." 2772 ::= { capwapBaseNotifyVarObjects 3 } 2774 capwapBaseNtfAuthenMethod OBJECT-TYPE 2775 SYNTAX CapwapBaseAuthenMethodTC 2776 MAX-ACCESS accessible-for-notify 2777 STATUS current 2778 DESCRIPTION 2779 "Represents authentication method for CAPWAP Channel." 2780 ::= { capwapBaseNotifyVarObjects 4 } 2782 capwapBaseNtfChannelDownReason OBJECT-TYPE 2783 SYNTAX INTEGER { 2784 timeout(1), 2785 rekeyfailure(2), 2786 acRebootWtp(3), 2787 dtlsError(4), 2788 maxRetransmit(5) 2789 } 2790 MAX-ACCESS accessible-for-notify 2791 STATUS current 2792 DESCRIPTION 2793 "Represents the reason for Channel down. 2794 The following enumerated values are supported: 2795 timeout(1) - The keep alive is timeout 2796 rekeyfailure(2) - Rekey process is failed, channel will be 2797 broken 2798 acRebootWtp(3) - The AC reboot WTP 2799 dtlsError(4) - DTLS notifications: DTLSAborted, 2800 DTLSReassemblyFailure, DTLSPeerDisconnect, 2801 or frequent DTLSDecapFailure 2802 maxRetransmit(5) - The underlying reliable transport's 2803 RetransmitCount counter has reached the 2804 MaxRetransmit variable" 2805 ::= { capwapBaseNotifyVarObjects 5 } 2807 capwapBaseNtfStationIdList OBJECT-TYPE 2808 SYNTAX OCTET STRING 2809 MAX-ACCESS accessible-for-notify 2810 STATUS current 2811 DESCRIPTION 2812 "Represents a list of station identifiers separated by 2813 semicolons." 2814 REFERENCE 2815 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2816 ::= { capwapBaseNotifyVarObjects 6 } 2818 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2819 SYNTAX INTEGER { 2820 keyMismatch(1), 2821 invalidCert(2), 2822 reassemblyFailure(3), 2823 decapFailure(4), 2824 encapFailure(5), 2825 timeout(6), 2826 unknown(8) 2827 } 2828 MAX-ACCESS accessible-for-notify 2829 STATUS current 2830 DESCRIPTION 2831 "Represents reason for WTP authorization failure. 2832 The following enumerated values are supported: 2833 keyMismatch(1) - WTP's and AC's key are not matched 2834 invalidCert(2) - Certification is not valid 2835 reassemblyFailure(3) - Fragment reassembly failure 2836 decapFailure(4) - Decapsulation error 2837 encapFailure(5) - Encapsulation error 2838 timeout(6) - WaitDTLS timer timeout 2839 unknown(8) - Unknown reason" 2840 REFERENCE 2841 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 2842 ::= { capwapBaseNotifyVarObjects 7 } 2844 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2845 SYNTAX INTEGER { 2846 operable(0), 2847 inoperable(1) 2848 } 2849 MAX-ACCESS accessible-for-notify 2850 STATUS current 2851 DESCRIPTION 2852 "Represents the operation status of a radio. 2853 The following enumerated values are supported: 2854 operable(0) - The radio is operable 2855 inoperable(1) - The radio is inoperable, and the 2856 capwapBaseNtfRadioStatusCause object 2857 gives the reason in details" 2858 REFERENCE 2859 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2860 ::= { capwapBaseNotifyVarObjects 8 } 2862 capwapBaseNtfRadioStatusCause OBJECT-TYPE 2863 SYNTAX INTEGER { 2864 normal(0), 2865 hwError(1), 2866 swError(2), 2867 adminSet(3) 2868 } 2869 MAX-ACCESS accessible-for-notify 2870 STATUS current 2871 DESCRIPTION 2872 "Represents the reason why radio is out of service. 2873 The following enumerated values are supported: 2874 normal(0) - Normal status 2875 hwError(1) - Radio failure 2876 swError(2) - Software failure 2877 adminSet(3) - Administratively set" 2878 REFERENCE 2879 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2880 ::= { capwapBaseNotifyVarObjects 9 } 2882 capwapBaseNtfJoinFailureReason OBJECT-TYPE 2883 SYNTAX INTEGER { 2884 unspecified(1), 2885 resDepletion(2), 2886 unknownSource(3), 2887 incorrectData(4), 2888 sessionIdInUse(5), 2889 notSupportHw(6), 2890 notSupportBinding(7) 2891 } 2892 MAX-ACCESS accessible-for-notify 2893 STATUS current 2894 DESCRIPTION 2895 "Represents the reason of join failure. 2896 The following enumerated values are supported: 2897 unspecified(1) - Unspecified failure reason 2898 resDepletion(2) - Resource depletion 2899 unknownSource(3) - Unknown source 2900 incorrectData(4) - Incorrect data 2901 sessionIdInUse(5) - Session ID already in use 2902 notSupportHw(6) - WTP hardware not supported 2903 notSupportBinding(7) - Binding not supported" 2904 REFERENCE 2905 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2906 ::= { capwapBaseNotifyVarObjects 10 } 2908 capwapBaseNtfImageFailureReason OBJECT-TYPE 2909 SYNTAX INTEGER { 2910 invalidChecksum(1), 2911 invalidLength(2), 2912 other(3), 2913 inStorage(4) 2914 } 2915 MAX-ACCESS accessible-for-notify 2916 STATUS current 2917 DESCRIPTION 2918 "Represents the reason of image failure. 2919 The following enumerated values are supported: 2920 invalidChecksum(1) - Invalid checksum 2921 invalidLength(2) - Invalid data length 2922 other(3) - Other error 2923 inStorage(4) - Image already present" 2924 REFERENCE 2925 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2926 ::= { capwapBaseNotifyVarObjects 11 } 2928 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 2929 SYNTAX INTEGER { 2930 unknownElement(1), 2931 unsupportedElement(2), 2932 unknownValue(3), 2933 unsupportedValue(4) 2934 } 2935 MAX-ACCESS accessible-for-notify 2936 STATUS current 2937 DESCRIPTION 2938 "Represents the type of configuration message error. 2939 The following enumerated values are supported: 2940 unknownElement(1) - Unknown message element 2941 unsupportedElement(2) - Unsupported message element 2942 unknownValue(3) - Unknown message element value 2943 unsupportedValue(4) - Unsupported message element value" 2944 REFERENCE 2945 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 2946 ::= { capwapBaseNotifyVarObjects 12 } 2948 capwapBaseNtfMsgErrorElements OBJECT-TYPE 2949 SYNTAX SnmpAdminString 2950 MAX-ACCESS accessible-for-notify 2951 STATUS current 2952 DESCRIPTION 2953 "Represents the message elements sent by the AC in the 2954 Configuration Status Response message that caused the error." 2955 REFERENCE 2956 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 2957 ::= { capwapBaseNotifyVarObjects 13 } 2959 -- Module compliance 2961 capwapBaseCompliances OBJECT IDENTIFIER 2962 ::= { capwapBaseConformance 1 } 2964 capwapBaseGroups OBJECT IDENTIFIER 2965 ::= { capwapBaseConformance 2 } 2967 capwapBaseCompliance MODULE-COMPLIANCE 2968 STATUS current 2969 DESCRIPTION 2970 "Describes the requirements for conformance to the 2971 CAPWAP-BASE-MIB module." 2973 MODULE -- this module 2974 MANDATORY-GROUPS { 2975 capwapBaseAcNodeGroup, 2976 capwapBaseWtpProfileGroup, 2977 capwapBaseWtpStateGroup, 2978 capwapBaseWtpGroup, 2979 capwapBaseRadioGroup, 2980 capwapBaseStationGroup 2981 } 2983 GROUP capwapBaseAcNodeGroup2 2984 DESCRIPTION 2985 "The capwapBaseAcNodeGroup2 group is optional." 2987 GROUP capwapBaseAcNameListGroup 2988 DESCRIPTION 2989 "The capwapBaseAcNameListGroup group is optional." 2991 GROUP capwapBaseMacAclsGroup 2992 DESCRIPTION 2993 "The capwapBaseMacAclsGroup group is optional." 2995 GROUP capwapBaseWtpProfileGroup2 2996 DESCRIPTION 2997 "The capwapBaseWtpProfileGroup2 group is optional." 2999 GROUP capwapBaseWtpGroup2 3000 DESCRIPTION 3001 "The capwapBaseWtpGroup2 group is optional." 3003 GROUP capwapBaseWtpEventsStatsGroup 3004 DESCRIPTION 3005 "The capwapBaseWtpEventsStatsGroup group is optional." 3007 GROUP capwapBaseRadioEventsStatsGroup 3008 DESCRIPTION 3009 "The capwapBaseRadioEventsStatsGroup group is optional." 3011 GROUP capwapBaseParametersGroup 3012 DESCRIPTION 3013 "The capwapBaseParametersGroup group is optional." 3015 GROUP capwapBaseStatsGroup 3016 DESCRIPTION 3017 "The capwapBaseStatsGroup group is optional." 3019 GROUP capwapBaseNotificationsGroup 3020 DESCRIPTION 3021 "The capwapBaseNotificationsGroup group is optional." 3023 GROUP capwapBaseNotifyVarsGroup 3024 DESCRIPTION 3025 "The capwapBaseNotifyVarsGroup group is optional. 3026 If capwapBaseNotificationsGroup is supported, 3027 this group must be implemented." 3028 ::= { capwapBaseCompliances 1 } 3030 capwapBaseAcNodeGroup OBJECT-GROUP 3031 OBJECTS { 3032 capwapBaseWtpSessions, 3033 capwapBaseWtpSessionsLimit, 3034 capwapBaseStationSessions, 3035 capwapBaseStationSessionsLimit 3036 } 3037 STATUS current 3038 DESCRIPTION 3039 "A collection of objects which are used to represent 3040 the basic properties for the AC from the CAPWAP 3041 protocol perspective." 3042 ::= { capwapBaseGroups 1 } 3044 capwapBaseAcNodeGroup2 OBJECT-GROUP 3045 OBJECTS { 3046 capwapBaseDataChannelDTLSPolicyOptions, 3047 capwapBaseDataChannelDTLSPolicyConfig, 3048 capwapBaseControlChannelAuthenOptions, 3049 capwapBaseControlChannelAuthenConfig 3050 } 3051 STATUS current 3052 DESCRIPTION 3053 "A collection of objects which are used to represent 3054 the other properties such as security for the AC from 3055 the CAPWAP protocol perspective." 3056 ::= { capwapBaseGroups 2 } 3058 capwapBaseAcNameListGroup OBJECT-GROUP 3059 OBJECTS { 3060 capwapBaseAcNameListName, 3061 capwapBaseAcNameListPriority, 3062 capwapBaseAcNameListRowStatus 3063 } 3064 STATUS current 3065 DESCRIPTION 3066 "A collection of objects which are used to configure 3067 the AC name list." 3068 ::= { capwapBaseGroups 3 } 3070 capwapBaseMacAclsGroup OBJECT-GROUP 3071 OBJECTS { 3072 capwapBaseMacAclStationId, 3073 capwapBaseMacAclRowStatus 3074 } 3075 STATUS current 3076 DESCRIPTION 3077 "A collection of objects which are used to configure 3078 the stations ACL." 3079 ::= { capwapBaseGroups 4 } 3081 capwapBaseWtpProfileGroup OBJECT-GROUP 3082 OBJECTS { 3083 capwapBaseWtpProfileName, 3084 capwapBaseWtpProfileWtpMacAddr, 3085 capwapBaseWtpProfileWtpModelNumber, 3086 capwapBaseWtpProfileWtpName, 3087 capwapBaseWtpProfileWtpLocation, 3088 capwapBaseWtpProfileRowStatus 3089 } 3090 STATUS current 3091 DESCRIPTION 3092 "A collection of objects which are used to configure 3093 the WTP profile." 3094 ::= { capwapBaseGroups 5 } 3096 capwapBaseWtpProfileGroup2 OBJECT-GROUP 3097 OBJECTS { 3098 capwapBaseWtpProfileWtpStaticIpEnable, 3099 capwapBaseWtpProfileWtpStaticIpType, 3100 capwapBaseWtpProfileWtpStaticIp, 3101 capwapBaseWtpProfileWtpNetmask, 3102 capwapBaseWtpProfileWtpGateway, 3103 capwapBaseWtpProfileWtpFallbackEnable, 3104 capwapBaseWtpProfileWtpEchoInterval, 3105 capwapBaseWtpProfileWtpIdleTimeout, 3106 capwapBaseWtpProfileWtpMaxDiscoveryInterval, 3107 capwapBaseWtpProfileWtpReportInterval, 3108 capwapBaseWtpProfileWtpSilentInterval, 3109 capwapBaseWtpProfileWtpStatisticsTimer, 3110 capwapBaseWtpProfileWtpWaitDTLSTimer, 3111 capwapBaseWtpProfileWtpEcnSupport 3112 } 3113 STATUS current 3114 DESCRIPTION 3115 "A collection of optional objects which are used to 3116 configure the WTP profile." 3117 ::= { capwapBaseGroups 6 } 3119 capwapBaseWtpStateGroup OBJECT-GROUP 3120 OBJECTS { 3121 capwapBaseWtpStateWtpIpAddressType, 3122 capwapBaseWtpStateWtpIpAddress, 3123 capwapBaseWtpStateWtpBaseMacAddress, 3124 capwapBaseWtpState, 3125 capwapBaseWtpStateWtpCurrWtpProfileId 3126 } 3127 STATUS current 3128 DESCRIPTION 3129 "A collection of objects which are used to represent 3130 the WTP's state information." 3131 ::= { capwapBaseGroups 7 } 3133 capwapBaseWtpGroup OBJECT-GROUP 3134 OBJECTS { 3135 capwapBaseWtpBaseMacAddress, 3136 capwapBaseWtpTunnelModeOptions, 3137 capwapBaseWtpMacTypeOptions, 3138 capwapBaseWtpDiscoveryType, 3139 capwapBaseWtpRadiosInUseNum, 3140 capwapBaseWtpRadioNumLimit 3141 } 3142 STATUS current 3143 DESCRIPTION 3144 "A collection of objects which are used to represent 3145 the properties information for the WTPs in running state." 3146 ::= { capwapBaseGroups 8 } 3148 capwapBaseWtpGroup2 OBJECT-GROUP 3149 OBJECTS { 3150 capwapBaseWtpPhyIndex, 3151 capwapBaseWtpRetransmitCount, 3152 capwapBaseWtpMaxDiscoveries, 3153 capwapBaseWtpMaxFailedDTLSSessionRetry, 3154 capwapBaseWtpMaxRetransmit, 3155 capwapBaseWtpDataChannelKeepAliveTimer, 3156 capwapBaseWtpDataChannelDeadInterval, 3157 capwapBaseWtpDiscoveryInterval, 3158 capwapBaseWtpDTLSSessionDeleteTimer, 3159 capwapBaseWtpImageDataStartTimer, 3160 capwapBaseWtpRetransmitInterval 3161 } 3162 STATUS current 3163 DESCRIPTION 3164 "A collection of optional objects which are used to represent 3165 the properties information for the WTPs in running state." 3166 ::= { capwapBaseGroups 9 } 3168 capwapBaseRadioGroup OBJECT-GROUP 3169 OBJECTS { 3170 capwapBaseWirelessBindingVirtualRadioIfIndex, 3171 capwapBaseWirelessBindingType 3172 } 3173 STATUS current 3174 DESCRIPTION 3175 "A collection of objects which are used to represent 3176 the wireless binding type, the mappings between the 3177 ifIndexes of WLAN Virtual Radio Interfaces and PHY radios." 3178 ::= { capwapBaseGroups 10 } 3180 capwapBaseStationGroup OBJECT-GROUP 3181 OBJECTS { 3182 capwapBaseStationAddedTime, 3183 capwapBaseStationVlanName 3184 } 3185 STATUS current 3186 DESCRIPTION 3187 "A collection of objects which are used to represent 3188 the stations' basic properties." 3189 ::= { capwapBaseGroups 11 } 3191 capwapBaseWtpEventsStatsGroup OBJECT-GROUP 3192 OBJECTS { 3193 capwapBaseWtpEventsStatsRebootCount, 3194 capwapBaseWtpEventsStatsInitCount, 3195 capwapBaseWtpEventsStatsLinkFailureCount, 3196 capwapBaseWtpEventsStatsSwFailureCount, 3197 capwapBaseWtpEventsStatsHwFailureCount, 3198 capwapBaseWtpEventsStatsOtherFailureCount, 3199 capwapBaseWtpEventsStatsUnknownFailureCount, 3200 capwapBaseWtpEventsStatsLastFailureType 3201 } 3202 STATUS current 3203 DESCRIPTION 3204 "A collection of objects which are used for collecting 3205 WTP reboot count, link failure count, hardware failure 3206 count and so on." 3207 ::= { capwapBaseGroups 12 } 3209 capwapBaseRadioEventsStatsGroup OBJECT-GROUP 3210 OBJECTS { 3211 capwapBaseRadioEventsStatsResetCount, 3212 capwapBaseRadioEventsStatsSwFailCount, 3213 capwapBaseRadioEventsStatsHwFailCount, 3214 capwapBaseRadioEventsStatsOtherFailCount, 3215 capwapBaseRadioEventsStatsUnknownFailCount, 3216 capwapBaseRadioEventsStatsConfigUpdateCount, 3217 capwapBaseRadioEventsStatsChannelChangeCount, 3218 capwapBaseRadioEventsStatsBandChangeCount, 3219 capwapBaseRadioEventsStatsCurrentNoiseFloor, 3220 capwapBaseRadioEventsStatsDecryptErrorCount, 3221 capwapBaseRadioEventsStatsLastFailType 3222 } 3223 STATUS current 3224 DESCRIPTION 3225 "A collection of objects which are used for collecting 3226 radio reset count, channel change count, hardware failure 3227 count and so on" 3228 ::= { capwapBaseGroups 13 } 3230 capwapBaseParametersGroup OBJECT-GROUP 3231 OBJECTS { 3232 capwapBaseAcMaxRetransmit, 3233 capwapBaseAcChangeStatePendingTimer, 3234 capwapBaseAcDataCheckTimer, 3235 capwapBaseAcDTLSSessionDeleteTimer, 3236 capwapBaseAcEchoInterval, 3237 capwapBaseAcRetransmitInterval, 3238 capwapBaseAcSilentInterval, 3239 capwapBaseAcWaitDTLSTimer, 3240 capwapBaseAcWaitJoinTimer, 3241 capwapBaseAcEcnSupport 3242 } 3243 STATUS current 3244 DESCRIPTION 3245 "Objects used for the CAPWAP protocol's parameters." 3246 ::= { capwapBaseGroups 14 } 3248 capwapBaseStatsGroup OBJECT-GROUP 3249 OBJECTS { 3250 capwapBaseFailedDTLSAuthFailCount, 3251 capwapBaseFailedDTLSSessionCount 3252 } 3253 STATUS current 3254 DESCRIPTION 3255 "Objects used for collecting the CAPWAP protocol's statistic." 3256 ::= { capwapBaseGroups 15 } 3258 capwapBaseNotificationsGroup NOTIFICATION-GROUP 3259 NOTIFICATIONS { 3260 capwapBaseChannelUp, 3261 capwapBaseChannelDown, 3262 capwapBaseDecryptErrorReport, 3263 capwapBaseJoinFailure, 3264 capwapBaseImageUpgradeFailure, 3265 capwapBaseConfigMsgError, 3266 capwapBaseRadioOperableStatus, 3267 capwapBaseAuthenticationFailure 3268 } 3269 STATUS current 3270 DESCRIPTION 3271 "A collection of notifications in this MIB module." 3272 ::= { capwapBaseGroups 16 } 3274 capwapBaseNotifyVarsGroup OBJECT-GROUP 3275 OBJECTS { 3276 capwapBaseNtfWtpId, 3277 capwapBaseNtfRadioId, 3278 capwapBaseNtfChannelType, 3279 capwapBaseNtfAuthenMethod, 3280 capwapBaseNtfChannelDownReason, 3281 capwapBaseNtfStationIdList, 3282 capwapBaseNtfAuthenFailureReason, 3283 capwapBaseNtfRadioOperStatusFlag, 3284 capwapBaseNtfRadioStatusCause, 3285 capwapBaseNtfJoinFailureReason, 3286 capwapBaseNtfImageFailureReason, 3287 capwapBaseNtfConfigMsgErrorType, 3288 capwapBaseNtfMsgErrorElements 3289 } 3290 STATUS current 3291 DESCRIPTION 3292 "Objects used for notifications." 3293 ::= { capwapBaseGroups 17 } 3295 END 3297 11. Security Considerations 3299 There are a number of management objects defined in this MIB module 3300 with a MAX-ACCESS clause of read-write and/or read-create. Such 3301 objects MAY be considered sensitive or vulnerable in some network 3302 environments. The support for SET operations in a non-secure 3303 environment without proper protection can have a negative effect on 3304 network operations. The followings are the tables and objects and 3305 their sensitivity/vulnerability: 3307 - Unauthorized changes to the capwapBaseWtProfileTable, and writable 3308 objects under capwapBaseAcs group MAY disrupt allocation of resources 3309 in the network. For example, a WTP's static IP address could be 3310 changed by set capwapBaseWtpProfileWtpStaticIp object. 3312 - Unauthorized changes to writable objects under the capwapBaseAc 3313 group, it MAY disrupt allocation of resources in the network. For 3314 example, a invalid value for capwapBaseWtpSessionsLimit object will 3315 increase the AC's traffic burden. Also, some objects such as 3316 capwapBaseDataChannelDTLSPolicyConfig MAY cause network unsafe. 3318 - Unauthorized changes to the capwapBaseMacAclTable, it MAY cause 3319 legal stations unable to access the network any more while illegal 3320 stations have chance to access the network. 3322 - Unauthorized changes to writable objects under the 3323 capwapBaseParameters group, it MAY influence CAPWAP protocol 3324 behaviour and status. For example, an invalid value set for the 3325 capwapBaseAcDataCheckTimer MAY influence the CAPWAP state machine. 3327 Some of the readable objects in this MIB module (i.e., objects with a 3328 MAX-ACCESS other than not-accessible) MAY be considered sensitive or 3329 vulnerable in some network environments. It is thus important to 3330 control even GET and/or NOTIFY access to these objects and possibly 3331 to even encrypt the values of these objects when sending them over 3332 the network via SNMP. The followings are the tables and objects and 3333 their sensitivity/vulnerability: 3335 - The capwapBaseDataChannelDTLSPolicyOptions and 3336 capwapBaseControlChannelAuthenOptions under the capwapBaseAc group 3337 exposes the current security option for CAPWAP data and control 3338 channels. 3340 - The capwapBaseWtpTable exposes a WTP's important information like 3341 tunnel mode, MAC type and so on. 3343 - The capwapBaseWtpEventsStatsTable exposes a WTP's failure 3344 information. 3346 - The capwapBaseRadioEventsStatsTable exposes a radio's failure 3347 information. 3349 SNMP versions prior to SNMPv3 did not include adequate security. 3350 Even if the network itself is secure (for example by using IPSec), 3351 even then, there is no control as to who on the secure network is 3352 allowed to access and GET/SET (read/change/create/delete) the objects 3353 in this MIB module. 3355 It is RECOMMENDED that implementers consider the security features as 3356 provided by the SNMPv3 framework (see [RFC3410], section 8), 3357 including full support for the SNMPv3 cryptographic mechanisms (for 3358 authentication and privacy). 3360 Further, the deployment of SNMP versions prior to SNMPv3 is NOT 3361 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3362 enable cryptographic security. It is then a customer/operator 3363 responsibility to ensure that the SNMP entity giving access to an 3364 instance of this MIB module is properly configured to give access to 3365 the objects only to those principals (users) that have legitimate 3366 rights to indeed GET or SET (change/create/delete) them. 3368 12. IANA Considerations 3369 12.1. IANA Considerations for CAPWAP-BASE-MIB Module 3371 The MIB module in this document uses the following IANA-assigned 3372 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3374 Descriptor OBJECT IDENTIFIER value 3375 ---------- ----------------------- 3377 capwapBaseMIB { mib-2 XXX } 3379 12.2. IANA Considerations for ifType 3381 Require IANA to assign a ifType for the WTP Virtual Radio Interface. 3383 13. Contributors 3385 This MIB module is based on contributions from Long Gao. 3387 14. Acknowledgements 3389 The authors wish to thank David Harrington, Abhijit Choudhury, Fei 3390 Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin 3391 Zhao, Haitao Zhang, Xiansen Cai. 3393 15. References 3395 15.1. Normative References 3397 [RFC2119] Bradner, S., "Key words for use in 3398 RFCs to Indicate Requirement Levels", 3399 BCP 14, RFC 2119, March 1997. 3401 [RFC2578] McCloghrie, K., Ed., Perkins, D., 3402 Ed., and J. Schoenwaelder, Ed., 3403 "Structure of Management Information 3404 Version 2 (SMIv2)", STD 58, RFC 2578, 3405 April 1999. 3407 [RFC2579] McCloghrie, K., Ed., Perkins, D., 3408 Ed., and J. Schoenwaelder, Ed., 3409 "Textual Conventions for SMIv2", 3410 STD 58, RFC 2579, April 1999. 3412 [RFC2580] McCloghrie, K., Perkins, D., and J. 3413 Schoenwaelder, "Conformance 3414 Statements for SMIv2", STD 58, 3415 RFC 2580, April 1999. 3417 [RFC2863] McCloghrie, K. and F. Kastenholz, 3418 "The Interfaces Group MIB", RFC 2863, 3419 June 2000. 3421 [RFC3411] Harrington, D., Presuhn, R., and B. 3422 Wijnen, "An Architecture for 3423 Describing Simple Network Management 3424 Protocol (SNMP) Management 3425 Frameworks", STD 62, RFC 3411, 3426 December 2002. 3428 [RFC3418] Presuhn, R., "Management Information 3429 Base (MIB) for the Simple Network 3430 Management Protocol (SNMP)", STD 62, 3431 RFC 3418, December 2002. 3433 [RFC4001] Daniele, M., Haberman, B., Routhier, 3434 S., and J. Schoenwaelder, "Textual 3435 Conventions for Internet Network 3436 Addresses", RFC 4001, February 2005. 3438 [RFC4133] Bierman, A. and K. McCloghrie, 3439 "Entity MIB (Version 3)", RFC 4133, 3440 August 2005. 3442 [RFC5415] Calhoun, P., Montemurro, M., and D. 3443 Stanley, "Control And Provisioning of 3444 Wireless Access Points (CAPWAP) 3445 Protocol Specification", RFC 5415, 3446 March 2009. 3448 15.2. Informative References 3450 [IEEE.802-11.2007] "Information technology - 3451 Telecommunications and information 3452 exchange between systems - Local and 3453 metropolitan area networks - Specific 3454 requirements - Part 11: Wireless LAN 3455 Medium Access Control (MAC) and 3456 Physical Layer (PHY) specifications", 3457 IEEE Standard 802.11, 2007, . 3461 [RFC3168] Ramakrishnan, K., Floyd, S., and D. 3462 Black, "The Addition of Explicit 3463 Congestion Notification (ECN) to IP", 3464 RFC 3168, September 2001. 3466 [RFC3410] Case, J., Mundy, R., Partain, D., and 3467 B. Stewart, "Introduction and 3468 Applicability Statements for 3469 Internet-Standard Management 3470 Framework", RFC 3410, December 2002. 3472 [RFC4118] Yang, L., Zerfos, P., and E. Sadot, 3473 "Architecture Taxonomy for Control 3474 and Provisioning of Wireless Access 3475 Points (CAPWAP)", RFC 4118, 3476 June 2005. 3478 [RFC4347] Rescorla, E. and N. Modadugu, 3479 "Datagram Transport Layer Security", 3480 RFC 4347, April 2006. 3482 [RFC5416] Calhoun, P., Montemurro, M., and D. 3483 Stanley, "Control and Provisioning of 3484 Wireless Access Points (CAPWAP) 3485 Protocol Binding for IEEE 802.11", 3486 RFC 5416, March 2009. 3488 [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., 3489 and Y. Zhang, "CAPWAP Protocol 3490 Binding MIB for IEEE 802.11", 3491 draft-ietf-capwap-802dot11-mib-04 3492 (work in progress), May 2009. 3494 Appendix A. Appendix A. Changes between -06 and -05 3496 All the issues are tracked by 3497 http://www.capwap.org/cgi-bin/roundup.cgi/MIB/ 3499 1)Issue 70: For Base MIB, some bugs detected post-WGLC but pre-IESG 3501 capwapBaseWtpProfileWTPSerialId should be 3502 capwapBaseWtpProfileWtpSerialId (second WTP should be Wtp). 3503 capwapBaseWtpProfileWTPModelNumber should be 3504 capwapBaseWtpProfileWtpModelNumber (second WTP should be Wtp). 3506 In the section 5.4, it should say "The SNMP agent MUST be run on the 3507 AC devices" instead of CAPWAP-BASE-MIB. 3509 The editor's address is updated. 3511 2)Issue 72: The WTP id issue in the Base MIB 3513 Updated the section 5.7. WTP Profile and the description of 3514 capwapBaseWtpProfileWtpMacAddr. It clarify that "The section 4.6.40 3515 [RFC5415] does not clarify that the WTP's Base MAC address MUST be 3516 included in the WTP Board Data message element. This is a known 3517 errata item and assumed to be fixed in future by the editors of the 3518 RFC5415." 3520 Also, updated the ID of WTP with Base MAC address instead of the 3521 serial number. 3523 3)Issue 73: For the example section in the Base and Dot11 MIB, the 3524 Dot11OperationTable is incorrect 3526 In the draft version 05, the Dot11OperationTable follows the IEEE 3527 802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft 3528 version 06 is updated according to IEEE 802.11-2007. 3530 Authors' Addresses 3532 Yang Shi (editor) 3533 Hangzhou H3C Tech. Co., Ltd. 3534 Beijing R&D Center of H3C, Digital Technology Plaza, 3535 NO.9 Shangdi 9th Street,Haidian District, 3536 Beijing 3537 China(100085) 3539 Phone: +86 010 82775276 3540 EMail: young@h3c.com 3542 David Perkins (editor) 3543 SNMPinfo 3544 288 Quailbrook Ct San Carlos, 3545 CA 94070 3546 USA 3548 Phone: +1 408 394-8702 3549 EMail: dperkins@snmpinfo.com 3551 Chris Elliott (editor) 3552 Cisco Systems, Inc. 3553 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 3554 27709 3555 USA 3557 Phone: +1 919-392-2146 3558 EMail: chelliot@cisco.com 3559 Yong Zhang (editor) 3560 Fortinet, Inc. 3561 1090 Kifer Road 3562 Sunnyvale, CA 94086 3563 USA 3565 EMail: yzhang@fortinet.com