idnits 2.17.1 draft-ietf-capwap-base-mib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (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 (January 2, 2010) is 5225 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Obsolete informational reference (is this intentional?): RFC 4347 (Obsoleted by RFC 6347) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Y. Shi, Ed. 3 Internet-Draft Hangzhou H3C Tech. Co., Ltd. 4 Intended status: Informational D. Perkins, Ed. 5 Expires: July 6, 2010 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 January 2, 2010 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-07 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) 18 for use with network management protocols. In particular, it 19 describes the managed objects for modeling the Control And 20 Provisioning of Wireless Access Points (CAPWAP) Protocol. 22 Status of This Memo 24 This Internet-Draft is submitted to IETF in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 This Internet-Draft will expire on July 6, 2010. 45 Copyright Notice 47 Copyright (c) 2010 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. The Internet-Standard Management Framework . . . . . . . . . . 3 64 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4 68 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 69 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 70 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 71 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 72 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 73 5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7 74 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 8 75 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 76 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9 77 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9 78 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 79 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10 80 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 81 8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10 82 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14 83 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14 84 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17 85 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17 86 9.3.1. Configuration Status Response Message . . . . . . . . 17 87 9.3.2. Configuration Update Response Message . . . . . . . . 18 88 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 89 11. Security Considerations . . . . . . . . . . . . . . . . . . . 76 90 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77 91 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 77 92 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 77 93 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 77 94 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 77 95 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 78 96 15.1. Normative References . . . . . . . . . . . . . . . . . . . 78 97 15.2. Informative References . . . . . . . . . . . . . . . . . . 79 98 Appendix A. Appendix A. Changes between -07 and -06 . . . . . . . 80 100 1. Introduction 102 The CAPWAP Protocol [RFC5415] defines a standard, interoperable 103 protocol, which enables an Access Controller (AC) to manage a 104 collection of Wireless Termination Points(WTPs). 106 This document defines a MIB module that can be used to manage the 107 CAPWAP implementations. This MIB module covers both configuration 108 and WTP status-monitoring aspects of CAPWAP, and provides a way to 109 reuse MIB modules for any wireless technology. 111 2. The Internet-Standard Management Framework 113 For a detailed overview of the documents that describe the current 114 Internet-Standard Management Framework, please refer to section 7 of 115 RFC 3410 [RFC3410]. 117 Managed objects are accessed via a virtual information store, termed 118 the Management Information Base or MIB. MIB objects are generally 119 accessed through the Simple Network Management Protocol (SNMP). 120 Objects in the MIB are defined using the mechanisms defined in the 121 Structure of Management Information (SMI). This memo specifies a MIB 122 module that is compliant to the SMIv2, which is described in STD 58, 123 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 124 [RFC2580]. 126 3. Terminology 128 This document uses terminology from the CAPWAP Protocol specification 129 [RFC5415] and the Architecture Taxonomy for CAPWAP [RFC4118]. 131 Access Controller (AC): The network entity that provides WTP access 132 to the network infrastructure in the data plane, control plane, 133 management plane, or a combination therein. 135 Wireless Termination Point (WTP): The physical or network entity that 136 contains an RF antenna and wireless physical layer (PHY) to transmit 137 and receive station traffic for wireless access networks. 139 Control And Provisioning of Wireless Access Points (CAPWAP): It is a 140 generic protocol defining AC and WTP control and data plane 141 communication via a CAPWAP protocol transport mechanism. CAPWAP 142 control messages, and optionally CAPWAP data messages, are secured 143 using Datagram Transport Layer Security (DTLS) [RFC4347]. 145 CAPWAP Control Channel: A bi-directional flow defined by the AC IP 146 Address, WTP IP Address, AC control port, WTP control port and the 147 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control 148 packets are sent and received. 150 CAPWAP Data Channel: A bi-directional flow defined by the AC IP 151 Address, WTP IP Address, AC data port, WTP data port, and the 152 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data 153 packets are sent and received. 155 Station (STA): A device that contains an interface to a wireless 156 medium (WM). 158 Split and Local MAC: The CAPWAP protocol supports two modes of 159 operation: Split and Local MAC. In Split MAC mode all L2 wireless 160 data and management frames are encapsulated via the CAPWAP protocol 161 and exchanged between the AC and the WTPs. The Local MAC mode allows 162 the data frames to be either locally bridged, or tunneled as 802.3 163 frames. 165 Wireless Binding: The CAPWAP protocol is independent of a specific 166 WTP radio technology, as well its associated wireless link layer 167 protocol. Elements of the CAPWAP protocol are designed to 168 accommodate the specific needs of each wireless technology in a 169 standard way. Implementation of the CAPWAP protocol for a particular 170 wireless technology MUST define a binding protocol for it, e.g., the 171 binding for IEEE 802.11, provided in [RFC5416]. 173 Autonomous Wireless Local Area Network (WLAN) Architecture: It is the 174 traditional autonomous WLAN architecture, in which each WTP is a 175 single physical device that implements all the wireless services. 177 Centralized WLAN Architecture: It is an emerging hierarchical 178 architecture utilizing one or more centralized controllers for 179 managing a large number of WTP devices. It can be said that the full 180 wireless functions are implemented across multiple physical network 181 devices, namely, the WTPs and ACs. 183 4. Conventions 185 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 186 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 187 document are to be interpreted as described in RFC 2119 [RFC2119]. 189 5. Overview 191 5.1. Requirements and Constraints 193 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to: 195 - Support centralized management and monitoring of WTPs from the AC 196 in combination with the CAPWAP protocol; 198 - Allow operators to make configurations for WTPs before and after 199 they connect to the AC; 201 - Support querying of CAPWAP protocol parameters; 203 - Support displaying of WTPs' current state and configuration; 205 - Provide basic property information about the AC, WTP, radio and 206 station and their relationships; 208 - Provide counters for events on WTPs and radios such as reboot and 209 hardware failure; 211 - Provide various notifications such as channel up and join failure. 213 5.2. Wireless Binding MIB Modules 215 Other Standards Developing Organizations (SDOs), such as IEEE, have 216 already defined MIB modules for a specific wireless technology, e.g., 217 IEEE 802.11 MIB module [IEEE.802-11.2007]. Such MIB modules are 218 called wireless binding MIB modules. 220 5.3. Design Objectives 222 This document introduces a mechanism to avoid redefining MIB objects 223 in the existing MIB modules for a specific wireless technology, in 224 other words, a mechanism to reuse wireless binding MIB modules 225 defined by other SDOs. 227 In summary, the CAPWAP-BASE-MIB module has the following design 228 objectives: 230 - To implement an architecture that uses SNMP for the management and 231 control of wireless networks, and answering the operator's 232 requirements for centralized management, whatever the wireless 233 devices are configured and deployed (centralized, autonomous, or some 234 mix); 236 - To be consistent with the CAPWAP protocol; 238 - To be independent of any wireless technologies and be able to reuse 239 wireless binding MIB modules defined by other SDOs; 241 - To enable interoperability between vendors; 243 - To meet the management requirements for the centralized WLAN 244 architecture. 246 5.4. Design Idea 248 The basic design idea of the CAPWAP-BASE-MIB module is: 250 - The SNMP agent MUST be run on the AC devices and is not REQUIRED on 251 the WTP devices. It follows the same model as the CAPWAP protocol: 252 Centralized Control; 254 - It is designed to accommodate the specific needs of each wireless 255 technology in a standard way. It is independent of any wireless 256 technologies; 258 - The ifIndex [RFC2863] is used as a common index for corresponding 259 interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific 260 wireless technologies; 262 - The operator could manage and control the centralized WLAN 263 architectures using multiple MIB modules defined by multiple SDOs, 264 while keeping them loosely coupled. 266 5.5. Mechanism of Reusing Wireless Binding MIB Modules 268 For any wireless technology, the configuration and management of 269 radios are very important. As usual, wireless binding MIB modules 270 support radio management on their own. For example, the MIB tables 271 such as the Dot11OperationTable [IEEE.802-11.2007] are able to 272 support WTP radio configuration. These tables use the ifIndex as the 273 index, and work well under autonomous WLAN architecture. 275 To reuse such wireless binding MIB modules is very important to 276 centralized WLAN architectures. According to [RFC5415], a specific 277 PHY radio could be identified by the combination of the identifiers 278 of the WTP and radio (WTP ID + radio ID), so the key point is to make 279 use of the ifIndex idea and find a way to maintain the mappings 280 between 'WTP ID + radio ID' and the ifIndex. As a generic mechanism, 281 an ifIndex can identify an interface in an abstract way, and it does 282 NOT care for the interface's PHY location (either on the WTP or AC). 283 The AC can have WTP Virtual Radio Interfaces to logically represent 284 PHY radios on the WTP. It looks like that PHY radios are located on 285 the AC, and PHY location of the WTP (radio) is hidden to the 286 operator. The operator can operate radios through MIB tables with 287 the ifIndex of a WTP Virtual Radio Interface. As a type of abstract 288 interface, the WTP Virtual Radio Interface could be used by any 289 wireless technology such as IEEE 802.11 and 802.16. The 290 capwapBaseWirelessBindingTable in the CAPWAP-BASE-MIB module is used 291 to store the mappings between the 'WTP ID+ Radio ID' and the ifIndex. 293 5.6. CAPWAP Protocol Wireless Binding MIB Module 295 According to the CAPWAP Protocol specification [RFC5415], when 296 defining a binding for wireless technologies, the authors MUST 297 include any necessary definitions for technology-specific messages 298 and all technology-specific message elements for those messages. A 299 CAPWAP binding protocol is required for a specific wireless binding 300 technology, e.g., the protocol of [RFC5416] for IEEE 802.11 binding. 302 Sometimes, not all the technology-specific message elements in a 303 CAPWAP binding protocol have MIB objects defined by other SDOs. For 304 example, the protocol of [RFC5416] defines WLAN management. The WLAN 305 refers to a logical component instantiated on a WTP device. A single 306 physical WTP MAY operate a number of WLANs. Also, Local or Split MAC 307 modes could be specified for a WLAN. The MAC mode for a WLAN is not 308 in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in 309 addition to the existing wireless binding MIB modules defined by 310 other SDOs, a CAPWAP protocol wireless binding MIB module is required 311 to be defined for a wireless binding, e.g, the CAPWAP Protocol 312 Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. 314 5.7. WTP Profile 316 In a centralized WLAN architecture, a WTP profile is used to make 317 configurations such as static IP address for a WTP before and after 318 it connects to the AC. It MUST contain the Base MAC address 319 [RFC5415] of the WTP because the CAPWAP message received from the WTP 320 contains the Base MAC address and the AC uses this Base MAC address 321 to find the corresponding WTP profile. 323 In the section 4.6.40 [RFC5415], it omits indicating that the WTP's 324 Base MAC address MUST be included in the WTP Board Data message 325 element. It is a known errata item and assumed to be fixed in future 326 by the editors of the RFC5415. 328 Another important function of WTP profile is to trigger the creation 329 of WTP Virtual Radio Interfaces on the AC. To implement this 330 function, a WTP profile MUST include the WTP's model number 331 [RFC5415], which reflects the number of PHY radios on the WTP. In 332 this way, the creation of a WTP profile triggers the AC to 333 automatically create the same number of WTP Virtual Radio Interfaces 334 corresponding to the WTP's PHY radios without manual intervention. 335 With the ifIndexes of WTP Virtual Radio Interfaces, the operator 336 could configure and manage the WTP's PHY radios through the wireless 337 binding MIB modules. 339 6. Structure of the MIB Module 341 The MIB objects are derived from the CAPWAP protocol document 342 [RFC5415]. 344 1) capwapBaseAcNameListTable 346 The AC name list table is used to configure the AC name list. 348 2) capwapBaseMacAclTable 350 The ACL table is used to configure stations' Access Control 351 List(ACL). 353 3) capwapBaseWtpProfileTable 355 The WTP profile table is used to configure WTP profiles for WTPs to 356 be managed before they connect to the AC. An operator could change a 357 WTP's current configuration by changing the values of parameters in 358 the corresponding WTP profile, then the WTP could get the new 359 configuration through the CAPWAP control channel. 361 4) capwapBaseWtpStateTable 363 The WTPs status table is used to indicate each WTP's CAPWAP FSM 364 state, and helps operator to query WTPs' current configuration. 366 5) capwapBaseWtpTable 368 The WTPs table is used display properties of WTPs in running state. 370 6) capwapBaseWirelessBindingTable 372 The wireless binding table is used to display the mappings between 373 WTP Virtual Radio Interfaces and PHY radios, and the wireless binding 374 type for each PHY radio. 376 7) capwapBaseStationTable 378 The station table is used for providing stations' basic property 379 information. 381 8) capwapBaseWtpEventsStatsTable 383 The WTP events statistic table is used for collecting WTP reboot 384 count, link failure count, hardware failure count and so on. 386 9) capwapBaseRadioEventsStatsTable 387 The radio events statistic table is used for collecting radio reset 388 count, channel change count, hardware failure count and so on. 390 7. Relationship to Other MIB Modules 392 7.1. Relationship to SNMPv2-MIB Module 394 The CAPWAP-BASE-MIB module does not duplicate the objects of the 395 'system' group in the SNMPv2-MIB [RFC3418] that is defined as being 396 mandatory for all systems, and the objects apply to the entity as a 397 whole. The 'system' group provides identification of the management 398 entity and certain other system-wide data. 400 7.2. Relationship to IF-MIB Module 402 The Interfaces Group [RFC2863] defines generic managed objects for 403 managing interfaces. This memo contains the media-specific 404 extensions to the Interfaces Group for managing WTP PHY radios that 405 are modeled as interfaces. 407 The IF-MIB module is required to be supported on the AC. Each PHY 408 radio on the WTP corresponds to a WTP Virtual Radio Interface on the 409 AC. The WTP Virtual Radio Interface provides a way to configure the 410 radio's parameters and query radio's traffic statistics, and reuse 411 wireless binding modules defined by other SDOs. The interface MUST 412 be modeled as an ifEntry, and ifEntry objects such as ifIndex, 413 ifDescr, ifName, ifAlias are to be used as per [RFC2863]. 415 Also, as an ifIndex [RFC2863] is used as a common index for a 416 corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless 417 technologies MIB modules, the AC MUST have a mechanism that preserves 418 the values of the ifIndexes in the ifTable at AC reboot. 420 7.3. Relationship to ENTITY-MIB Module 422 The ENTITY-MIB module [RFC4133] meets the need for a standardized way 423 of representing a single agent, which supports multiple instances of 424 one MIB. It could express a certain relationship between multiple 425 entities, and provide entity properties for each entity. 427 In a centralized WLAN architecture, the SNMP agent runs on the AC, 428 and is not required on the WTP. With the ENTITY-MIB module on the 429 AC, it could keep entity information such as firmware revision and 430 software revision of the AC and WTPs. From the ENTITY-MIB module's 431 perspective, the overall physical entity (AC) is a 'compound' of 432 multiple physical entities (that is, the WTPs connected to AC), and 433 all entities are each identified by a Physical index. The 434 capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the 435 capwapBaseWtpPhyIndex object to store the mappings of WTP object 436 between CAPWAP-BASE-MIB and ENTITY-MIB modules. 438 By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules, 439 operators could query the status and properties of the AC and WTPs. 440 For example, they could get a WTP's current status through the 441 CAPWAP-BASE-MIB module, and a WTP's software revision information 442 through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not 443 duplicate those objects defined in the ENTITY-MIB module. 445 7.4. Relationship to Wireless Binding MIB Modules 447 The wireless binding MIB module of a wireless technology (such as 448 [IEEE.802-11.2007]) is required to be supported on the AC. The 449 CAPWAP-BASE-MIB module is able to support any wireless binding. 450 Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a 451 consistent and abstract way of reusing MIB objects in the wireless 452 binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate 453 those objects defined in the wireless binding MIB modules. 455 7.5. MIB Modules Required for IMPORTS 457 The following MIB module IMPORTS objects from SYSAPPL-MIB [RFC2287], 458 SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF- 459 MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB 460 [RFC4001] and ENTITY-MIB [RFC4133]. 462 8. Example of CAPWAP-BASE-MIB Module Usage 464 Here takes IEEE 802.11 binding as an example to show how the MIB 465 modules operate. 467 1) Create a WTP profile 469 Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create 470 the WTP profile as follows: 472 In CapwapBaseWtpProfileTable 473 { 474 capwapBaseWtpProfileId = 1, 475 capwapBaseWtpProfileName = 'WTP Profile 123456', 476 capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00', 477 capwapBaseWtpProfileWtpModelNumber = 'WTP123', 478 capwapBaseWtpProfileWtpName = 'WTP 123456', 479 capwapBaseWtpProfileWtpLocation = 'office', 480 capwapBaseWtpProfileWtpStaticIpEnable = true(1), 481 capwapBaseWtpProfileWtpStaticIpType = ipv4(1), 482 capwapBaseWtpProfileWtpStaticIp = '192.0.2.10', 483 capwapBaseWtpProfileWtpNetmask = '255.255.255.0', 484 capwapBaseWtpProfileWtpGateway = '192.0.2.1', 485 capwapBaseWtpProfileWtpFallbackEnable = true(1), 486 capwapBaseWtpProfileWtpEchoInterval = 30, 487 capwapBaseWtpProfileWtpIdleTimeout = 300, 488 capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, 489 capwapBaseWtpProfileWtpReportInterval = 120, 490 capwapBaseWtpProfileWtpSilentInterval = 30, 491 capwapBaseWtpProfileWtpStatisticsTimer = 120, 492 capwapBaseWtpProfileWtpWaitDTLSTimer = 60, 493 capwapBaseWtpProfileWtpEcnSupport = limited(0) 494 } 496 Suppose the WTP with model number 'WTP123' has one PHY radio and this 497 PHY radio is identified by ID 1. The creation of this WTP profile 498 triggers the AC to automatically create a WTP Virtual Radio Interface 499 and add a new row object to the CapwapBaseWirelessBindingTable 500 without manual intervention. Suppose the ifIndex of the WTP Virtual 501 Radio Interface is 10. The following information is stored in the 502 CapwapBaseWirelessBindingTable. 504 In CapwapBaseWirelessBindingTable 505 { 506 capwapBaseWtpProfileId = 1, 507 capwapBaseWirelessBindingRadioId = 1, 508 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 509 capwapBaseWirelessBindingType = dot11(2) 510 } 512 The WTP Virtual Radio Interfaces on the AC correspond to the PHY 513 radios on the WTP. The WTP Virtual Radio Interface is modeled by 514 ifTable [RFC2863]. 516 In ifTable 517 { 518 ifIndex = 10, 519 ifDescr = 'WTP Virtual Radio Interface', 520 ifType = xxx, 521 RFC Editor - please replace xxx with the value 522 allocated by IANA for IANAifType of WTP Virtual Radio Interface 523 ifMtu = 0, 524 ifSpeed = 0, 525 ifPhysAddress = '00:00:00:00:00:00', 526 ifAdminStatus = true(1), 527 ifOperStatus = false(0), 528 ifLastChange = 0, 529 ifInOctets = 0, 530 ifInUcastPkts = 0, 531 ifInDiscards = 0, 532 ifInErrors = 0, 533 ifInUnknownProtos = 0, 534 ifOutOctets = 0, 535 ifOutUcastPkts = 0, 536 ifOutDiscards = 0, 537 ifOutErrors = 0 538 } 540 2) Query the ifIndexes of WTP Virtual Radio Interfaces 542 Before configuring PHY radios, the operator needs to get the 543 ifIndexes of WTP Virtual Radio Interfaces corresponding to the PHY 544 radios. 546 As CapwapBaseWirelessBindingTable already stores the mappings between 547 PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio 548 Interfaces, the operator can get the ifIndex information by querying 549 this table. Such a query operation SHOULD run from radio ID 1 to 550 radio ID 31 according to [RFC5415]), and stop when a invalid ifIndex 551 value (0) is returned. 553 This example uses capwapBaseWtpProfileId = 1 and 554 capwapBaseWirelessBindingRadioId = 1 as inputs to query the 555 CapwapBaseWirelessBindingTable, and gets 556 capwapBaseWirelessBindingVirtualRadioIfIndex = 10. Then it uses 557 capwapBaseWtpProfileId = 1 and capwapBaseWirelessBindingRadioId = 2, 558 and gets a invalid ifIndex value (0), so the the query operation 559 ends. This method gets not only the ifIndexes of WTP Virtual Radio 560 Interfaces, but also the numbers of PHY radios. Besides checking 561 whether the ifIndex value is valid, the operator SHOULD check whether 562 the capwapBaseWirelessBindingType is the desired binding type. 564 3) Configure specific wireless binding parameters for a WTP Virtual 565 Radio Interface 567 This configuration is made on the AC through a specific wireless 568 binding MIB module such as the IEEE 802.11 MIB module. 570 The following shows an example of configuring parameters for a WTP 571 Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 572 Dot11OperationTable [IEEE.802-11.2007]. 574 In Dot11OperationTable 575 { 576 ifIndex = 10, 577 dot11MACAddress = '00:00:00:00:00:00', 578 dot11RTSThreshold = 2347, 579 dot11ShortRetryLimit = 7, 580 dot11LongRetryLimit = 4, 581 dot11FragmentationThreshold = 256, 582 dot11MaxTransmitMSDULifetime = 512, 583 dot11MaxReceiveLifetime = 512, 584 dot11ManufacturerID = 'capwap', 585 dot11ProductID = 'capwap' 586 } 588 4) Current configuration status report from the WTP to the AC 590 According to [RFC5415], before a WTP that has joined the AC gets 591 configuration from the AC, it needs to report its current 592 configuration status by sending a configuration status request 593 message to the AC, which use the message to update MIB objects on the 594 AC. For example, for IEEE 802.11 binding, the AC updates data in the 595 ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the 596 message. For ifIndex 10, its ifOperStatus in ifTable is updated 597 according to the current radio operational status in the CAPWAP 598 message. 600 5) Query WTP and radio statistics data 602 After WTPs start to run, the operator could query WTP and radio 603 statistics data through CAPWAP-BASE-MIB and specific binding MIB 604 module on the AC. For example, through dot11CountersTable in the 605 IEEE 802.11 MIB module, the operator could query the counter data of 606 a radio using the ifIndex of the corresponding WTP Virtual Radio 607 Interface. With the capwapBaseWtpTable table in the CAPWAP-BASE-MIB 608 module, the operator could query the properties of running WTPs. 610 6) MIB operations through a CAPWAP protocol wireless binding MIB 611 module 612 For example, for CAPWAP IEEE 802.11 binding protocol [RFC5416], Some 613 MIB operations such as MAC mode configuration for a WLAN depend on 614 the CAPWAP Protocol Binding MIB for IEEE 802.11 615 [I-D.ietf-capwap-802dot11-mib]. For more information, refer to 616 [I-D.ietf-capwap-802dot11-mib]. 618 7) Query other properties of a WTP 620 The Operator could query MIB objects in the ENTITY-MIB [RFC4133] 621 module by using the capwapBaseWtpPhyIndex in the capwapBaseWtpTable 622 of CAPWAP-BASE-MIB module. The properties of a WTP such as software 623 version, hardware version are available in the ENTITY-MIB module. 625 9. CAPWAP Message Element Extension 627 This section describes the CAPWAP control message extension for 628 CAPWAP protocol to support CAPWAP-BASE-MIB module. 630 To enable CAPWAP protocol timers and variables [RFC5415] manageable 631 through CAPWAP protocol, the following capwap message element 632 extensions are defined using Vendor Specific Payload message element 633 in this section. These message elements are used by WTP to report 634 extra configuration information to the AC. 636 CAPWAP Message Element Vendor Identifier Element ID 638 CAPWAP Protocol Timers Id assigned by IANA 1 639 CAPWAP Protocol Variables Id assigned by IANA 2 641 9.1. CAPWAP Protocol Timers 643 0 1 2 3 644 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 645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 | Vendor Identifier | 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 648 | Element ID | DataChannelKeepAlive | 649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 650 | DataChannelDeadInterval | DiscoveryInterval | 651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 652 | DTLSSessionDelete | EchoInterval | 653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 654 | IdleTimeout | 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 656 | ImageDataStartTimer | MaxDiscoveryInterval | 657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 658 | ReportInterval | RetransmitInterval | 659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 660 | SilentInterval | StatisticsTimer | 661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 662 | WaitDTLS | 663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 664 Type: 37 for Vendor Specific Payload 666 Length: 34 668 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 669 Network Management Private Enterprise Codes". 671 Element ID: The Element ID field is set to 1 for CAPWAP Protocol 672 Timers. 674 DataChannelKeepAlive: A 16-bit value representing the time, 675 in seconds, that is used by the WTP to determine the next 676 must transmit the Data Channel Keep Alive. (see section 4.7.2 of 677 [RFC5415]). 679 DataChannelDeadInterval: A 16-bit value representing the minimum 680 time, in seconds, a WTP MUST wait without having received a Data 681 Channel Alive packets MAY be considered dead. The value of this 682 timer MUST be no less than 2*DataChannelKeepAlive seconds and 683 no greater that 240 seconds (see section 4.7.3 of [RFC5415]). 685 DiscoveryInterval: A 16-bit value representing the minimum time, in 686 seconds, that a WTP MUST wait after receiving a Discovery Response 687 message, before initiating a DTLS handshake (see section 4.7.5 of 688 [RFC5415]). 690 DTLSSessionDelete: A 16-bit value representing the minimum time, in 691 seconds, a WTP MUST wait for DTLS session deletion (see section 692 4.7.6 of [RFC5415]). 694 EchoInterval: A 16-bit value representing the minimum time, in 695 seconds, between sending Echo Request messages to the AC with 696 which the WTP has joined (see section 4.7.7 of [RFC5415]). 698 IdleTimeout: A 32-bit value representing the idle timeout value that 699 the WTP SHOULD enforce for its active station. The default Idle 700 Timeout is 300 seconds (see section 4.7.8 of [RFC5415]). 702 ImageDataStartTimer: A 16-bit value representing the number of 703 seconds the WTP will wait for its peer to transmit the Image 704 Data Request (see section 4.7.9 of [RFC5415]). 706 MaxDiscoveryInterval: A 16-bit value representing the maximum time 707 allowed between sending Discovery Request messages, in seconds. 709 This value MUST be no less than 2 seconds and no greater than 180 710 seconds (see section 4.7.10 of [RFC5415]). 712 ReportInterval: A 16-bit value representing the time, in seconds, 713 that is used by the WTP to determine the interval the WTP uses 714 between sending the Decryption Error message elements to inform 715 the AC of decryption errors (see section 4.7.11 of [RFC5415]). 717 RetransmitInterval: A 16-bit value representing the minimum time, 718 in seconds, in which a non-acknowledged CAPWAP packet will be 719 retransmitted (see section 4.7.12 of [RFC5415]). 721 SilentInterval: The minimum time, in seconds, a WTP MUST wait before 722 it MAY again send Discovery Request messages or attempt to 723 establish DTLS session (see section 4.7.13 of [RFC5415]). 725 StatisticsTimer: A 16-bit value representing the time, in seconds, 726 that is used by the WTP to determine the interval the WTP uses 727 between the WTP Events Requests it transmits to the AC to 728 communicate its statistics (see section 4.7.14 of [RFC5415]). 730 WaitDTLS: A 16-bit value representing the maximum time, in seconds, 731 a WTP MUST wait without having received a DTLS Handshake message 732 from an AC. This timer MUST be greater than 30 seconds (see 733 section 4.7.15 of [RFC5415]). 735 9.2. CAPWAP Protocol Variables 737 0 1 2 3 738 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 739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 740 | Vendor Identifier | 741 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 742 | Element ID | MaxDiscoveries | 743 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 744 | MaxFailedDTLSSessionRetry | MaxRetransmit | 745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 Type: 37 for Vendor Specific Payload 749 Length: 12 751 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 752 Network Management Private Enterprise Codes". 754 Element ID: The Element ID field is set to 2 for CAPWAP Protocol 755 Variables. 757 MaxDiscoveries: A 16-bit value representing the maximum number of 758 Discovery Request messages that will be sent after a WTP boots 759 (see section 4.8.5 of [RFC5415]). 761 MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum 762 number of failed DTLS session establishment attempts before the 763 CAPWAP device enters a silent period (see section 4.8.6 of 764 [RFC5415]). 766 MaxRetransmit: A 16-bit value representing the maximum number of 767 retransmissions for a given CAPWAP packet before the link layer 768 considers the peer dead (see section 4.8.7 of [RFC5415]). 770 9.3. CAPWAP Messages for CAPWAP Control Message Extension 772 For CAPWAP Control Message Extension, the following CAPWAP messages 773 will be used. 775 9.3.1. Configuration Status Response Message 777 The following message elements MAY be included in the CAPWAP 778 Configuration Status Response Message. 780 - CAPWAP Protocol Timers, see Section Section 9.1 782 - CAPWAP Protocol Variables, see Section Section 9.2 784 9.3.2. Configuration Update Response Message 786 The following message elements MAY be included in the CAPWAP 787 Configuration Update Response Message. 789 - CAPWAP Protocol Timers, see Section Section 9.1 791 - CAPWAP Protocol Variables, see Section Section 9.2 793 10. Definitions 795 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 797 IMPORTS 799 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 800 DateAndTime, RowStatus 801 FROM SNMPv2-TC 802 LongUtf8String 803 FROM SYSAPPL-MIB 804 InterfaceIndex, ifGeneralInformationGroup 805 FROM IF-MIB 806 PhysicalIndex 807 FROM ENTITY-MIB 808 SnmpAdminString 809 FROM SNMP-FRAMEWORK-MIB 810 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 811 FROM SNMPv2-CONF 812 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 813 Integer32, Unsigned32, Counter32, Gauge32, TimeTicks 814 FROM SNMPv2-SMI 815 InetAddressType, InetAddress 816 FROM INET-ADDRESS-MIB; 818 capwapBaseMIB MODULE-IDENTITY 819 LAST-UPDATED "201001020000Z" -- Jan 2th, 2010 820 ORGANIZATION "IETF Control And Provisioning of Wireless Access 821 Points (CAPWAP) Working Group 822 http://www.ietf.org/html.charters/capwap-charter.html" 823 CONTACT-INFO 824 "General Discussion: capwap@frascone.com 825 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 827 Yang Shi (editor) 828 Hangzhou H3C Tech. Co., Ltd. 829 Beijing R&D Center of H3C, Digital Technology Plaza, 830 NO.9 Shangdi 9th Street,Haidian District, 831 Beijing 832 China(100085) 833 Phone: +86 010 82775276 834 EMail: young@h3c.com 836 David T. Perkins 837 228 Bayview Dr 838 San Carlos, CA 94070 839 USA 840 Phone: +1 408 394-8702 841 Email: dperkins@snmpinfo.com 843 Chris Elliott 844 Cisco Systems, Inc. 845 7025 Kit Creek Rd., P.O. Box 14987 846 Research Triangle Park 27709 847 USA 848 Phone: +1 919-392-2146 849 Email: chelliot@gmail.com 851 Yong Zhang 852 Fortinet, Inc. 853 1090 Kifer Road 854 Sunnyvale, CA 94086 855 USA 856 Email: yzhang@fortinet.com" 858 DESCRIPTION 859 "Copyright (C) 2010 The Internet Society. This version of 860 the MIB module is part of RFC xxx; see the RFC itself 861 for full legal notices. 863 This MIB module contains managed object definitions for 864 the CAPWAP Protocol." 865 REVISION "201001020000Z" 866 DESCRIPTION 867 "Initial version published as RFC xxx" 868 ::= { mib-2 xxx } 870 -- Textual Conventions 872 CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION 873 DISPLAY-HINT "d" 874 STATUS current 875 DESCRIPTION 876 "Represents the unique identifier of a WTP profile." 877 SYNTAX Unsigned32 (0..4096) 879 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 880 DISPLAY-HINT "1x:" 881 STATUS current 882 DESCRIPTION 883 "Represents the unique identifier of a WTP instance. 884 As usual, the Base MAC address of WTP is used." 885 SYNTAX OCTET STRING (SIZE(6|8)) 887 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 888 DISPLAY-HINT "1x:" 889 STATUS current 890 DESCRIPTION 891 "Represents the unique identifier of a station instance. 892 As usual, the MAC address of station is used." 893 SYNTAX OCTET STRING (SIZE(6|8)) 895 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 896 DISPLAY-HINT "d" 897 STATUS current 898 DESCRIPTION 899 "Represents the unique identifier of a radio on a WTP." 900 SYNTAX Unsigned32 (1..31) 902 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 903 STATUS current 904 DESCRIPTION 905 "Represents the tunneling modes of operation that are 906 supported by a WTP. 907 The WTP MAY support more than one option, represented by 908 the bit field below: 909 localBridging(0) - Local bridging mode 910 dot3Tunnel(1) - 802.3 frame tunnel mode 911 nativeTunnel(2) - Native frame tunnel mode" 912 REFERENCE 913 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 914 SYNTAX BITS { 915 localBridging(0), 916 dot3Tunnel(1), 917 nativeTunnel(2) 918 } 920 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 921 STATUS current 922 DESCRIPTION 923 "Represents the MAC mode of operation supported by a WTP. 924 The following enumerated values are supported: 925 localMAC(0) - Local-MAC mode 926 splitMAC(1) - Split-MAC mode 927 both(2) - Both Local-MAC and Split-MAC 928 Note that the CAPWAP field [RFC5415] modelled by this 929 object takes zero as starting value, this MIB object 930 follows this rule." 931 REFERENCE 932 "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 } 976 -- Tables, Scalars 977 capwapBaseObjects OBJECT IDENTIFIER 978 ::= { capwapBaseMIB 1 } 979 -- Conformance 980 capwapBaseConformance OBJECT IDENTIFIER 981 ::= { capwapBaseMIB 2 } 983 -- AC Objects Group 985 capwapBaseAc OBJECT IDENTIFIER 986 ::= { capwapBaseObjects 1 } 988 capwapBaseWtpSessions OBJECT-TYPE 989 SYNTAX Gauge32 (0..65535) 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Represents the total number of WTPs which are connecting to 994 the AC." 995 REFERENCE 996 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 997 ::= { capwapBaseAc 1 } 999 capwapBaseWtpSessionsLimit OBJECT-TYPE 1000 SYNTAX Unsigned32 (0..65535) 1001 MAX-ACCESS read-write 1002 STATUS current 1003 DESCRIPTION 1004 "Represents the maximum number of WTP sessions configured on 1005 the AC. 1006 The value of the object is persistent at restart/reboot." 1007 REFERENCE 1008 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1009 ::= { capwapBaseAc 2 } 1011 capwapBaseStationSessions OBJECT-TYPE 1012 SYNTAX Gauge32 (0..65535) 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Represents the total number of stations which are accessing 1017 the wireless service provided by the AC." 1018 REFERENCE 1019 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1020 ::= { capwapBaseAc 3 } 1022 capwapBaseStationSessionsLimit OBJECT-TYPE 1023 SYNTAX Unsigned32 (0..65535) 1024 MAX-ACCESS read-write 1025 STATUS current 1026 DESCRIPTION 1027 "Represents the maximum number of station sessions configured 1028 on the AC. 1029 The value of the object is persistent at restart/reboot." 1030 REFERENCE 1031 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1032 ::= { capwapBaseAc 4 } 1034 capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE 1035 SYNTAX BITS { 1036 other(0), 1037 clear(1), 1038 dtls(2) 1039 } 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The AC communicates its policy on the use of DTLS for 1044 CAPWAP data channel. 1045 The AC MAY support more than one option, represented by the bit 1046 field below: 1047 other(0) - Other method, for example, vendor specific 1048 clear(1) - Clear text 1049 dtls(2) - DTLS" 1050 REFERENCE 1051 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1052 ::= { capwapBaseAc 5 } 1054 capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE 1055 SYNTAX INTEGER { 1056 other(0), 1057 clear(1), 1058 dtls(2) 1059 } 1060 MAX-ACCESS read-write 1061 STATUS current 1062 DESCRIPTION 1063 "Represents the security policy configured on the AC for 1064 CAPWAP data channel. 1065 The value of the object is persistent at restart/reboot. 1066 The following enumerated values are supported: 1067 other(0) - Other method, for example, vendor specific 1068 clear(1) - Clear text 1069 dtls(2) - DTLS 1070 Note that the CAPWAP field [RFC5415] modelled by this 1071 object takes zero as starting value, this MIB object 1072 follows this rule." 1073 REFERENCE 1074 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1075 ::= { capwapBaseAc 6 } 1077 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 1078 SYNTAX BITS { 1079 x509(0), 1080 psk(1) 1081 } 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "Represents the authentication credential type supported by the 1086 AC for CAPWAP control channel. 1087 The AC MAY support more than one option, represented by the bit 1088 field below: 1089 x509(0) - X.509 certificate based 1090 psk(1) - Pre-Shared secret" 1091 REFERENCE 1092 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1093 ::= { capwapBaseAc 7 } 1095 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 1096 SYNTAX INTEGER { 1097 x509(1), 1098 psk(2) 1099 } 1100 MAX-ACCESS read-write 1101 STATUS current 1102 DESCRIPTION 1103 "Represents the authentication credential type configured on 1104 the AC for CAPWAP control channel. 1105 The value of the object is persistent at restart/reboot. 1106 The following enumerated values are supported: 1107 x509(1) - X.509 certificate based 1108 psk(2) - Pre-Shared secret" 1109 REFERENCE 1110 "Section 4.6.1. of CAPWAP Protocol Specification, RFC 5415." 1111 ::= { capwapBaseAc 8 } 1113 -- capwapBaseAcNameListTable table 1115 capwapBaseAcNameListTable OBJECT-TYPE 1116 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "A table of objects that configure the AC name list. 1121 Values of all read-create objects in this table are 1122 persistent at restart/reboot." 1123 REFERENCE 1124 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1125 ::= { capwapBaseAc 9 } 1127 capwapBaseAcNameListEntry OBJECT-TYPE 1128 SYNTAX CapwapBaseAcNameListEntry 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "A set of objects that configure the AC name list." 1133 INDEX { capwapBaseAcNameListId } 1134 ::= { capwapBaseAcNameListTable 1 } 1136 CapwapBaseAcNameListEntry ::= SEQUENCE { 1137 capwapBaseAcNameListId Unsigned32, 1138 capwapBaseAcNameListName LongUtf8String, 1139 capwapBaseAcNameListPriority Unsigned32, 1140 capwapBaseAcNameListRowStatus RowStatus 1141 } 1143 capwapBaseAcNameListId OBJECT-TYPE 1144 SYNTAX Unsigned32 (1..255) 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "Represents the unique identifier of a AC Name list." 1149 ::= { capwapBaseAcNameListEntry 1 } 1151 capwapBaseAcNameListName OBJECT-TYPE 1152 SYNTAX LongUtf8String (SIZE(1..512)) 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "Represents the name of an AC, and it is expected to be 1157 an UTF-8 encoded string." 1158 REFERENCE 1159 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1160 ::= { capwapBaseAcNameListEntry 2 } 1162 capwapBaseAcNameListPriority OBJECT-TYPE 1163 SYNTAX Unsigned32 (1..255) 1164 MAX-ACCESS read-create 1165 STATUS current 1166 DESCRIPTION 1167 "Represents the priority order of the preferred AC. 1168 For instance, the value of one (1) is used to set the primary 1169 AC, the value of two (2) is used to set the secondary AC, etc." 1170 REFERENCE 1171 "Section 4.6.5. of CAPWAP Protocol Specification, RFC 5415." 1172 ::= { capwapBaseAcNameListEntry 3 } 1174 capwapBaseAcNameListRowStatus OBJECT-TYPE 1175 SYNTAX RowStatus 1176 MAX-ACCESS read-create 1177 STATUS current 1178 DESCRIPTION 1179 "This object is used to create, modify, and/or delete a row 1180 in this table. 1181 The value of capwapBaseAcNameListName and 1182 capwapBaseAcNameListPriority can be changed when this 1183 object is in state ''active'' or in ''notInService''. 1184 The capwapBaseAcNameListRowStatus may be changed to ''active'' 1185 if all the managed objects in the conceptual row with 1186 MAX-ACCESS read-create have been assigned valid values." 1187 ::= { capwapBaseAcNameListEntry 4 } 1189 -- End of capwapBaseAcNameListTable table 1191 -- capwapBaseMacAclTable table 1193 capwapBaseMacAclTable OBJECT-TYPE 1194 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 1195 MAX-ACCESS not-accessible 1196 STATUS current 1197 DESCRIPTION 1198 "A table of objects that configure station Access Control 1199 Lists (ACL). 1200 The WTP will not provide service to the MAC addresses 1201 configured in this table. 1202 Values of all read-create objects in this table are persistent 1203 at AC restart/reboot." 1204 REFERENCE 1205 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1206 ::= { capwapBaseAc 10 } 1208 capwapBaseMacAclEntry OBJECT-TYPE 1209 SYNTAX CapwapBaseMacAclEntry 1210 MAX-ACCESS not-accessible 1211 STATUS current 1212 DESCRIPTION 1213 "A set of objects that configure station Access Control 1214 List (ACL)." 1215 INDEX { capwapBaseMacAclId } 1216 ::= { capwapBaseMacAclTable 1 } 1218 CapwapBaseMacAclEntry ::= SEQUENCE { 1219 capwapBaseMacAclId Unsigned32, 1220 capwapBaseMacAclStationId CapwapBaseStationIdTC, 1221 capwapBaseMacAclRowStatus RowStatus 1222 } 1224 capwapBaseMacAclId OBJECT-TYPE 1225 SYNTAX Unsigned32 (1..255) 1226 MAX-ACCESS not-accessible 1227 STATUS current 1228 DESCRIPTION 1229 "Represents the unique identifier of an ACL." 1230 ::= { capwapBaseMacAclEntry 1 } 1232 capwapBaseMacAclStationId OBJECT-TYPE 1233 SYNTAX CapwapBaseStationIdTC 1234 MAX-ACCESS read-create 1235 STATUS current 1236 DESCRIPTION 1237 "Represents the MAC address of a station to which WTPs will 1238 no longer provides service." 1239 REFERENCE 1240 "Section 4.6.7. of CAPWAP Protocol Specification, RFC 5415." 1241 ::= { capwapBaseMacAclEntry 2 } 1243 capwapBaseMacAclRowStatus OBJECT-TYPE 1244 SYNTAX RowStatus 1245 MAX-ACCESS read-create 1246 STATUS current 1247 DESCRIPTION 1248 "This object is used to create, modify, and/or delete a row 1249 in this table. 1250 The value of capwapBaseMacAclStationId can be changed when 1251 this object is in state ''active'' or in ''notInService''. 1252 The capwapBaseMacAclRowStatus may be changed to ''active'' 1253 if all the managed objects in the conceptual row with 1254 MAX-ACCESS read-create have been assigned valid values." 1255 ::= { capwapBaseMacAclEntry 3 } 1257 -- End of capwapBaseMacAclTable table 1259 -- End of AC Objects Group 1260 -- WTP Objects Group 1262 capwapBaseWtps OBJECT IDENTIFIER 1263 ::= { capwapBaseObjects 2 } 1265 -- capwapBaseWtpProfileTable Table 1267 capwapBaseWtpProfileTable OBJECT-TYPE 1268 SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "A table of objects that configure WTP profiles for WTPs to 1273 be managed before they connect to the AC. 1274 An operator could change a WTP's configuration by changing 1275 the values of parameters in the corresponding WTP profile, 1276 then the WTP could get the new configuration through the 1277 CAPWAP control channel. 1278 Values of all read-create objects in this table are 1279 persistent at restart/reboot." 1280 ::= { capwapBaseWtps 1 } 1282 capwapBaseWtpProfileEntry OBJECT-TYPE 1283 SYNTAX CapwapBaseWtpProfileEntry 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "A set of objects that configure and display a WTP profile." 1288 INDEX { capwapBaseWtpProfileId } 1289 ::= { capwapBaseWtpProfileTable 1 } 1291 CapwapBaseWtpProfileEntry ::= SEQUENCE { 1292 capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, 1293 capwapBaseWtpProfileName SnmpAdminString, 1294 capwapBaseWtpProfileWtpMacAddr CapwapBaseWtpIdTC, 1295 capwapBaseWtpProfileWtpModelNumber SnmpAdminString, 1296 capwapBaseWtpProfileWtpName LongUtf8String, 1297 capwapBaseWtpProfileWtpLocation LongUtf8String, 1298 capwapBaseWtpProfileWtpStaticIpEnable TruthValue, 1299 capwapBaseWtpProfileWtpStaticIpType InetAddressType, 1300 capwapBaseWtpProfileWtpStaticIp InetAddress, 1301 capwapBaseWtpProfileWtpNetmask InetAddress, 1302 capwapBaseWtpProfileWtpGateway InetAddress, 1303 capwapBaseWtpProfileWtpFallbackEnable INTEGER, 1304 capwapBaseWtpProfileWtpEchoInterval Unsigned32, 1305 capwapBaseWtpProfileWtpIdleTimeout Unsigned32, 1306 capwapBaseWtpProfileWtpMaxDiscoveryInterval Unsigned32, 1307 capwapBaseWtpProfileWtpReportInterval Unsigned32, 1308 capwapBaseWtpProfileWtpSilentInterval Unsigned32, 1309 capwapBaseWtpProfileWtpStatisticsTimer Unsigned32, 1310 capwapBaseWtpProfileWtpWaitDTLSTimer Unsigned32, 1311 capwapBaseWtpProfileWtpEcnSupport INTEGER, 1312 capwapBaseWtpProfileRowStatus RowStatus 1313 } 1315 capwapBaseWtpProfileId OBJECT-TYPE 1316 SYNTAX CapwapBaseWtpProfileIdTC 1317 MAX-ACCESS not-accessible 1318 STATUS current 1319 DESCRIPTION 1320 "Represents the unique identifier of a WTP profile." 1321 ::= { capwapBaseWtpProfileEntry 1 } 1323 capwapBaseWtpProfileName OBJECT-TYPE 1324 SYNTAX SnmpAdminString 1325 MAX-ACCESS read-create 1326 STATUS current 1327 DESCRIPTION 1328 "Represents the name of a WTP profile." 1329 ::= { capwapBaseWtpProfileEntry 2 } 1331 capwapBaseWtpProfileWtpMacAddr OBJECT-TYPE 1332 SYNTAX CapwapBaseWtpIdTC 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "Represents the Base MAC address of a WTP. 1337 A WTP profile MUST contain the Base MAC address of the WTP 1338 because the CAPWAP message received from the WTP contains 1339 its Base MAC address and the AC uses the Base MAC address to 1340 find the corresponding WTP profile. 1341 In the section 4.6.40 [RFC5415], it omits be included in the 1342 WTP Board Data message element. It is a known errata item and 1343 assumed to be fixed in future by the editors of the RFC5415." 1344 REFERENCE 1345 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1346 ::= { capwapBaseWtpProfileEntry 3 } 1348 capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE 1349 SYNTAX SnmpAdminString 1350 MAX-ACCESS read-create 1351 STATUS current 1352 DESCRIPTION 1353 "Represents the model number of a WTP. 1354 A WTP profile MUST include the WTP's model number, which 1355 reflects the number of Physical Layer (PHY) radios on the WTP. 1357 In this way, the creation of a WTP profile triggers the AC 1358 to automatically create the same number of WTP Virtual Radio 1359 Interfaces corresponding to the WTP's PHY radios without 1360 manual intervention. With the ifIndexes of WTP Virtual 1361 Radio Interfaces, the operator could configure and manage 1362 the WTP's PHY radios through the wireless binding MIB 1363 modules." 1364 REFERENCE 1365 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1366 ::= { capwapBaseWtpProfileEntry 4 } 1368 capwapBaseWtpProfileWtpName OBJECT-TYPE 1369 SYNTAX LongUtf8String (SIZE(1..512)) 1370 MAX-ACCESS read-create 1371 STATUS current 1372 DESCRIPTION 1373 "Represents the name of the WTP." 1374 REFERENCE 1375 "Section 4.6.45. of CAPWAP Protocol Specification, RFC 5415." 1376 ::= { capwapBaseWtpProfileEntry 5 } 1378 capwapBaseWtpProfileWtpLocation OBJECT-TYPE 1379 SYNTAX LongUtf8String (SIZE(1..1024)) 1380 MAX-ACCESS read-create 1381 STATUS current 1382 DESCRIPTION 1383 "Represents the location of the WTP." 1384 REFERENCE 1385 "Section 4.6.30. of CAPWAP Protocol Specification, RFC 5415." 1386 ::= { capwapBaseWtpProfileEntry 6 } 1388 capwapBaseWtpProfileWtpStaticIpEnable OBJECT-TYPE 1389 SYNTAX TruthValue 1390 MAX-ACCESS read-create 1391 STATUS current 1392 DESCRIPTION 1393 "Represents whether the WTP SHOULD use a static IP address 1394 or not. A value of false disables the static IP address, 1395 while a value of true enables it." 1396 REFERENCE 1397 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1398 ::= { capwapBaseWtpProfileEntry 7 } 1400 capwapBaseWtpProfileWtpStaticIpType OBJECT-TYPE 1401 SYNTAX InetAddressType {ipv4(1), ipv4z(3)} 1402 MAX-ACCESS read-create 1403 STATUS current 1404 DESCRIPTION 1405 "Represents the static IP address type used by the WTP. 1406 Only ipv4(1) and ipv4z(3) are supported by the object. 1407 Although the CAPWAP protocol (RFC5415) supports both IPv4 1408 and IPv6, note that the CAPWAP field modelled by this 1409 object does not support IPv6, so the object does not 1410 support ipv6(2) and ipv6z(4)." 1411 REFERENCE 1412 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1413 ::= { capwapBaseWtpProfileEntry 8 } 1415 capwapBaseWtpProfileWtpStaticIp OBJECT-TYPE 1416 SYNTAX InetAddress (SIZE(4|8)) 1417 MAX-ACCESS read-create 1418 STATUS current 1419 DESCRIPTION 1420 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1421 it represents the static IP address to be assigned to the WTP. 1422 The format of this IP address is determined by the 1423 corresponding instance of object 1424 capwapBaseWtpProfileWtpStaticIpType." 1425 REFERENCE 1426 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1427 ::= { capwapBaseWtpProfileEntry 9 } 1429 capwapBaseWtpProfileWtpNetmask OBJECT-TYPE 1430 SYNTAX InetAddress (SIZE(4|8)) 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1435 it represents the netmask to be assigned to the WTP. 1436 The format of this netmask is determined by the 1437 corresponding instance of object 1438 capwapBaseWtpProfileWtpStaticIpType." 1439 REFERENCE 1440 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1441 ::= { capwapBaseWtpProfileEntry 10 } 1443 capwapBaseWtpProfileWtpGateway OBJECT-TYPE 1444 SYNTAX InetAddress (SIZE(4|8)) 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "When capwapBaseWtpProfileWtpStaticIpEnable is true, 1449 it represents the gateway to be assigned to the WTP. 1450 The format of this IP address is determined by the 1451 corresponding instance of object 1452 capwapBaseWtpProfileWtpStaticIpType." 1454 REFERENCE 1455 "Section 4.6.48. of CAPWAP Protocol Specification, RFC 5415." 1456 ::= { capwapBaseWtpProfileEntry 11 } 1458 capwapBaseWtpProfileWtpFallbackEnable OBJECT-TYPE 1459 SYNTAX INTEGER { 1460 enabled(1), 1461 disabled(2) 1462 } 1463 MAX-ACCESS read-create 1464 STATUS current 1465 DESCRIPTION 1466 "Represents whether to enable or disable automatic CAPWAP 1467 fallback in the event that a WTP detects its preferred AC, 1468 and is not currently connected to it. 1469 The following enumerated values are supported: 1470 enabled(1) - The fallback mode is enabled 1471 disabled(2) - The fallback mode is disabled" 1472 REFERENCE 1473 "Section 4.6.42. of CAPWAP Protocol Specification, RFC 5415." 1474 DEFVAL { enabled } 1475 ::= { capwapBaseWtpProfileEntry 12 } 1477 capwapBaseWtpProfileWtpEchoInterval OBJECT-TYPE 1478 SYNTAX Unsigned32 1479 UNITS "second" 1480 MAX-ACCESS read-create 1481 STATUS current 1482 DESCRIPTION 1483 "Represents the minimum time, in seconds, between sending Echo 1484 Request messages to the AC that the WTP has joined." 1485 REFERENCE 1486 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 1487 DEFVAL { 30 } 1488 ::= { capwapBaseWtpProfileEntry 13 } 1490 capwapBaseWtpProfileWtpIdleTimeout OBJECT-TYPE 1491 SYNTAX Unsigned32 1492 UNITS "second" 1493 MAX-ACCESS read-create 1494 STATUS current 1495 DESCRIPTION 1496 "Represents the idle timeout value that the WTP SHOULD enforce 1497 for its active stations." 1498 REFERENCE 1499 "Section 4.7.8. of CAPWAP Protocol Specification, RFC 5415." 1500 DEFVAL { 300 } 1501 ::= { capwapBaseWtpProfileEntry 14 } 1503 capwapBaseWtpProfileWtpMaxDiscoveryInterval OBJECT-TYPE 1504 SYNTAX Unsigned32 (2..180) 1505 UNITS "second" 1506 MAX-ACCESS read-create 1507 STATUS current 1508 DESCRIPTION 1509 "Represents the maximum time allowed between sending Discovery 1510 Request messages, in seconds." 1511 REFERENCE 1512 "Section 4.7.10. of CAPWAP Protocol Specification, RFC 5415." 1513 DEFVAL { 20 } 1514 ::= { capwapBaseWtpProfileEntry 15 } 1516 capwapBaseWtpProfileWtpReportInterval OBJECT-TYPE 1517 SYNTAX Unsigned32 1518 UNITS "second" 1519 MAX-ACCESS read-create 1520 STATUS current 1521 DESCRIPTION 1522 "Represents the interval for WTP to send Decryption Error 1523 report." 1524 REFERENCE 1525 "Section 4.7.11. of CAPWAP Protocol Specification, RFC 5415." 1526 DEFVAL { 120 } 1527 ::= { capwapBaseWtpProfileEntry 16 } 1529 capwapBaseWtpProfileWtpSilentInterval OBJECT-TYPE 1530 SYNTAX Unsigned32 1531 UNITS "second" 1532 MAX-ACCESS read-create 1533 STATUS current 1534 DESCRIPTION 1535 "Represents the minimum time, in seconds, a WTP MUST wait 1536 before it MAY again send Discovery Request messages or 1537 attempt to a establish DTLS session." 1538 REFERENCE 1539 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 1540 DEFVAL { 30 } 1541 ::= { capwapBaseWtpProfileEntry 17 } 1543 capwapBaseWtpProfileWtpStatisticsTimer OBJECT-TYPE 1544 SYNTAX Unsigned32 1545 UNITS "second" 1546 MAX-ACCESS read-create 1547 STATUS current 1548 DESCRIPTION 1549 "Represents the interval the WTP uses between the WTP Events 1550 Requests it transmits to the AC to communicate its statistics, 1551 in seconds." 1552 REFERENCE 1553 "Section 4.7.14. of CAPWAP Protocol Specification, RFC 5415." 1554 DEFVAL { 120 } 1555 ::= { capwapBaseWtpProfileEntry 18 } 1557 capwapBaseWtpProfileWtpWaitDTLSTimer OBJECT-TYPE 1558 SYNTAX Unsigned32 (30..4294967295) 1559 UNITS "second" 1560 MAX-ACCESS read-create 1561 STATUS current 1562 DESCRIPTION 1563 "Represents the maximum time, in seconds, an AC MUST wait 1564 without having received a DTLS Handshake message from an AC. 1565 This timer MUST be greater than 30 seconds." 1566 REFERENCE 1567 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 1568 DEFVAL { 60 } 1569 ::= { capwapBaseWtpProfileEntry 19 } 1571 capwapBaseWtpProfileWtpEcnSupport OBJECT-TYPE 1572 SYNTAX INTEGER { 1573 limited(0), 1574 fullAndLimited(1) 1575 } 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 "Represents the support for the Explicit Congestion Notification 1580 (ECN) bits, as defined in [RFC3168]. 1581 The following enumerated values are supported: 1582 limited(0) - Limited ECN support 1583 fullAndLimited(1) - Full and limited ECN support 1584 Note that the CAPWAP field [RFC5415] modelled by this 1585 object takes zero as starting value, this MIB object follows 1586 this rule." 1587 REFERENCE 1588 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 1589 ::= { capwapBaseWtpProfileEntry 20 } 1591 capwapBaseWtpProfileRowStatus OBJECT-TYPE 1592 SYNTAX RowStatus 1593 MAX-ACCESS read-create 1594 STATUS current 1595 DESCRIPTION 1596 "This object is used to create, modify, and/or delete a row 1597 in this table. 1598 The value of capwapBaseWtpProfileName, 1599 capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation 1600 can be changed when this object is in state ''active'' or in 1601 ''notInService''. 1602 The other objects in a row can be modified only when the value 1603 of this object in the corresponding conceptual row is not 1604 ''active''. Thus to modify one or more of the objects in 1605 this conceptual row, 1606 a. change the row status to ''notInService'' 1607 b. change the values of the row 1608 c. change the row status to ''active'' 1609 The capwapBaseWtpProfileRowStatus may be changed to ''active'' 1610 if the managed objects capwapBaseWtpProfileName, 1611 capwapBaseWtpProfileWtpMacAddr, 1612 capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpName 1613 and capwapBaseWtpProfileWtpLocation in the conceptual row 1614 have been assigned valid values. 1616 Deleting a WTP profile in use will disconnect the WTP to 1617 the AC. So the network management system SHOULD 1618 ask the operator to confirm such an operation. 1619 When a WTP profile entry is removed from the table, 1620 the corresponding WTP Virtual Radio Interfaces are also 1621 removed from the CapwapBaseWirelessBindingTable and 1622 ifTable [RFC2863]. 1623 Also, the related object instances SHOULD be removed from 1624 the wireless binding MIB modules such as IEEE 802.11 1625 MIB module [IEEE.802-11.2007]." 1626 ::= { capwapBaseWtpProfileEntry 21 } 1628 -- End of capwapBaseWtpProfileTable table 1630 -- capwapBaseWtpStateTable table 1632 capwapBaseWtpStateTable OBJECT-TYPE 1633 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 1634 MAX-ACCESS not-accessible 1635 STATUS current 1636 DESCRIPTION 1637 "A table of objects that indicate each WTP's CAPWAP FSM 1638 state, and helps the operator to query the WTPs' current 1639 configuration." 1640 ::= { capwapBaseWtps 2 } 1642 capwapBaseWtpStateEntry OBJECT-TYPE 1643 SYNTAX CapwapBaseWtpStateEntry 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "A set of objects that display the WTP's CAPWAP FSM state. 1648 Also, the operator could query the current configuration 1649 of a WTP by using the identifier of the corresponding 1650 WTP profile." 1651 INDEX { capwapBaseWtpStateWtpId } 1652 ::= { capwapBaseWtpStateTable 1 } 1654 CapwapBaseWtpStateEntry ::= SEQUENCE { 1655 capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, 1656 capwapBaseWtpStateWtpIpAddressType InetAddressType, 1657 capwapBaseWtpStateWtpIpAddress InetAddress, 1658 capwapBaseWtpStateWtpBaseMacAddress PhysAddress, 1659 capwapBaseWtpState INTEGER, 1660 capwapBaseWtpStateWtpUpTime TimeTicks, 1661 capwapBaseWtpStateWtpCurrWtpProfileId CapwapBaseWtpProfileIdTC 1662 } 1664 capwapBaseWtpStateWtpId OBJECT-TYPE 1665 SYNTAX CapwapBaseWtpIdTC 1666 MAX-ACCESS not-accessible 1667 STATUS current 1668 DESCRIPTION 1669 "Represents the unique identifier of a WTP." 1670 ::= { capwapBaseWtpStateEntry 1 } 1672 capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE 1673 SYNTAX InetAddressType 1674 MAX-ACCESS read-only 1675 STATUS current 1676 DESCRIPTION 1677 "Represents the IP address type of a WTP. 1678 Only ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) and dns(16) 1679 are supported by the object." 1680 ::= { capwapBaseWtpStateEntry 2 } 1682 capwapBaseWtpStateWtpIpAddress OBJECT-TYPE 1683 SYNTAX InetAddress 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "Represents the IP address of a WTP. 1688 The format of this IP address is determined by 1689 the corresponding instance of object 1690 capwapBaseWtpStateWtpIpAddressType." 1691 ::= { capwapBaseWtpStateEntry 3 } 1693 capwapBaseWtpStateWtpBaseMacAddress OBJECT-TYPE 1694 SYNTAX PhysAddress (SIZE(6|8)) 1695 MAX-ACCESS read-only 1696 STATUS current 1697 DESCRIPTION 1698 "Represents the WTP's Base MAC Address, which MAY be 1699 assigned to the primary Ethernet interface. 1700 The instance of the object corresponds to the Base MAC Address 1701 sub-element in the CAPWAP protocol [RFC5415]." 1702 REFERENCE 1703 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1704 ::= { capwapBaseWtpStateEntry 4 } 1706 capwapBaseWtpState OBJECT-TYPE 1707 SYNTAX INTEGER { 1708 dtls(1), 1709 join(2), 1710 image(3), 1711 configure(4), 1712 dataCheck(5), 1713 run(6), 1714 reset(7), 1715 dtlsTeardown(8), 1716 unknown(9) 1717 } 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "Represents the various possible CAPWAP FSM states of WTP 1722 The following enumerated values are supported: 1723 dtls(1) - DTLS negotiation states, which include 1724 DTLS setup, authorize, DTLS connect 1725 join(2) - The WTP is joining with the AC 1726 image(3) - The WTP is downloading software 1727 configure(4) - The WTP is getting configuration from 1728 the AC 1729 dataCheck(5) - The AC is waiting for the Data Channel Keep 1730 Alive Packet 1731 run(6) - The WTP enters the running state 1732 reset(7) - The AC transmits a reset request message 1733 to the WTP 1734 dtlsTeardown(8) - DTLS session is tear down 1735 unknown(9) - Operator already prepared configuration 1736 for the WTP, while the WTP has not contact 1737 with the AC till now" 1738 REFERENCE 1739 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 1740 ::= { capwapBaseWtpStateEntry 5 } 1742 capwapBaseWtpStateWtpUpTime OBJECT-TYPE 1743 SYNTAX TimeTicks 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "Represents the time (in hundredths of a second) since the 1748 WTP has been in the running state (corresponding to the 1749 value run(6) of capwapBaseWtpState)." 1750 ::= { capwapBaseWtpStateEntry 6 } 1752 capwapBaseWtpStateWtpCurrWtpProfileId OBJECT-TYPE 1753 SYNTAX CapwapBaseWtpProfileIdTC 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "Represents the current identifier of a WTP profile. 1758 The operator could query a WTP's current configuration 1759 with the identifier of a WTP profile." 1760 ::= { capwapBaseWtpStateEntry 7 } 1762 -- End of capwapBaseWtpStateTable Table 1764 -- capwapBaseWtpTable Table 1766 capwapBaseWtpTable OBJECT-TYPE 1767 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "A table of objects that display properties of the WTPs 1772 in running state." 1773 ::= { capwapBaseWtps 3 } 1775 capwapBaseWtpEntry OBJECT-TYPE 1776 SYNTAX CapwapBaseWtpEntry 1777 MAX-ACCESS not-accessible 1778 STATUS current 1779 DESCRIPTION 1780 "A set of objects that display properties of the WTPs 1781 in running state." 1782 INDEX { capwapBaseWtpCurrId } 1783 ::= { capwapBaseWtpTable 1 } 1785 CapwapBaseWtpEntry ::= SEQUENCE { 1786 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1787 capwapBaseWtpPhyIndex PhysicalIndex, 1788 capwapBaseWtpBaseMacAddress PhysAddress, 1789 capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, 1790 capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, 1791 capwapBaseWtpDiscoveryType INTEGER, 1792 capwapBaseWtpRadiosInUseNum Gauge32, 1793 capwapBaseWtpRadioNumLimit Unsigned32, 1794 capwapBaseWtpRetransmitCount Counter32, 1795 capwapBaseWtpMaxDiscoveries Unsigned32, 1796 capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, 1797 capwapBaseWtpMaxRetransmit Unsigned32, 1798 capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, 1799 capwapBaseWtpDataChannelDeadInterval Unsigned32, 1800 capwapBaseWtpDiscoveryInterval Unsigned32, 1801 capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, 1802 capwapBaseWtpImageDataStartTimer Unsigned32, 1803 capwapBaseWtpRetransmitInterval Unsigned32 1804 } 1806 capwapBaseWtpCurrId OBJECT-TYPE 1807 SYNTAX CapwapBaseWtpIdTC 1808 MAX-ACCESS not-accessible 1809 STATUS current 1810 DESCRIPTION 1811 "Represents the unique identifier of a WTP in running state." 1812 ::= { capwapBaseWtpEntry 1 } 1814 capwapBaseWtpPhyIndex OBJECT-TYPE 1815 SYNTAX PhysicalIndex 1816 MAX-ACCESS read-only 1817 STATUS current 1818 DESCRIPTION 1819 "Represents the unique physical index of a physical entity 1820 in the ENTITY-MIB module [RFC4133]. 1821 The information such as software version of a specific WTP 1822 could be accessed through the index." 1823 ::= { capwapBaseWtpEntry 2 } 1825 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1826 SYNTAX PhysAddress (SIZE(6|8)) 1827 MAX-ACCESS read-only 1828 STATUS current 1829 DESCRIPTION 1830 "Represents the WTP's Base MAC Address, which MAY be assigned 1831 to the primary Ethernet interface. 1832 The instance of the object corresponds to the Base MAC Address 1833 sub-element in the CAPWAP protocol [RFC5415]." 1834 REFERENCE 1835 "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." 1836 ::= { capwapBaseWtpEntry 3 } 1838 capwapBaseWtpTunnelModeOptions OBJECT-TYPE 1839 SYNTAX CapwapBaseTunnelModeTC 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "Represents the tunneling modes of operation supported by 1844 the WTP." 1845 REFERENCE 1846 "Section 4.6.43. of CAPWAP Protocol Specification, RFC 5415." 1847 ::= { capwapBaseWtpEntry 4 } 1849 capwapBaseWtpMacTypeOptions OBJECT-TYPE 1850 SYNTAX CapwapBaseMacTypeTC 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "Represents the MAC mode of operation supported by the WTP." 1855 REFERENCE 1856 "Section 4.6.44. of CAPWAP Protocol Specification, RFC 5415." 1857 ::= { capwapBaseWtpEntry 5 } 1859 capwapBaseWtpDiscoveryType OBJECT-TYPE 1860 SYNTAX INTEGER { 1861 unknown(0), 1862 staticConfig(1), 1863 dhcp(2), 1864 dns(3), 1865 acRef(4) 1866 } 1867 MAX-ACCESS read-only 1868 STATUS current 1869 DESCRIPTION 1870 "Represents how the WTP discovers the AC. 1871 The following enumerated values are supported: 1872 unknown(0) - Unknown 1873 staticConfig(1) - Static configuration 1874 dhcp(2) - DHCP 1875 dns(3) - DNS 1876 acRef(4) - AC referral 1877 Note that the CAPWAP field [RFC5415] modelled by this 1878 object takes zero as starting value, this MIB object 1879 follows this rule." 1880 REFERENCE 1881 "Section 4.6.21. of CAPWAP Protocol Specification, RFC 5415." 1882 ::= { capwapBaseWtpEntry 6 } 1884 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1885 SYNTAX Gauge32 (0..255) 1886 MAX-ACCESS read-only 1887 STATUS current 1888 DESCRIPTION 1889 "Represents the number of radios in use on the WTP." 1890 REFERENCE 1891 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1892 ::= { capwapBaseWtpEntry 7 } 1894 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1895 SYNTAX Unsigned32 (0..255) 1896 MAX-ACCESS read-only 1897 STATUS current 1898 DESCRIPTION 1899 "Represents the maximum radio number supported by the WTP." 1900 REFERENCE 1901 "Section 4.6.41. of CAPWAP Protocol Specification, RFC 5415." 1902 ::= { capwapBaseWtpEntry 8 } 1904 capwapBaseWtpRetransmitCount OBJECT-TYPE 1905 SYNTAX Counter32 1906 UNITS "retransmissions" 1907 MAX-ACCESS read-only 1908 STATUS current 1909 DESCRIPTION 1910 "Represents the number of retransmissions for a given 1911 CAPWAP packet." 1912 REFERENCE 1913 "Section 4.8.8. of CAPWAP Protocol Specification, RFC 5415." 1914 ::= { capwapBaseWtpEntry 9 } 1916 capwapBaseWtpMaxDiscoveries OBJECT-TYPE 1917 SYNTAX Unsigned32 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "Represents the maximum number of Discovery Request messages 1922 that will be sent after a WTP boots." 1923 REFERENCE 1924 "Section 4.8.5. of CAPWAP Protocol Specification, RFC 5415." 1925 DEFVAL { 10 } 1926 ::= { capwapBaseWtpEntry 10 } 1928 capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE 1929 SYNTAX Unsigned32 1930 MAX-ACCESS read-only 1931 STATUS current 1932 DESCRIPTION 1933 "Represents the maximum number of failed DTLS session 1934 establishment attempts before the CAPWAP device enters a 1935 silent period." 1936 REFERENCE 1937 "Section 4.8.6. of CAPWAP Protocol Specification, RFC 5415." 1938 DEFVAL { 3 } 1939 ::= { capwapBaseWtpEntry 11 } 1941 capwapBaseWtpMaxRetransmit OBJECT-TYPE 1942 SYNTAX Unsigned32 1943 MAX-ACCESS read-only 1944 STATUS current 1945 DESCRIPTION 1946 "Represents the maximum number of retransmission for a given 1947 CAPWAP packet before the link layer considers the peer dead." 1948 REFERENCE 1949 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 1950 DEFVAL { 5 } 1951 ::= { capwapBaseWtpEntry 12 } 1953 capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE 1954 SYNTAX Unsigned32 1955 UNITS "second" 1956 MAX-ACCESS read-only 1957 STATUS current 1958 DESCRIPTION 1959 "Represents the next opportunity, in seconds, the WTP must 1960 transmit the Data Channel Keep Alive message." 1961 REFERENCE 1962 "Section 4.7.2. of CAPWAP Protocol Specification, RFC 5415." 1963 DEFVAL { 30 } 1964 ::= { capwapBaseWtpEntry 13 } 1966 capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE 1967 SYNTAX Unsigned32 (0..240) 1968 UNITS "second" 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "Represents the minimum time, in seconds, a WTP MUST wait 1973 without having received a Data Channel Keep Alive packet 1974 before the destination for the Data Channel Keep Alive 1975 packets MAY be considered dead." 1976 REFERENCE 1977 "Section 4.7.3. of CAPWAP Protocol Specification, RFC 5415." 1978 DEFVAL { 60 } 1979 ::= { capwapBaseWtpEntry 14 } 1981 capwapBaseWtpDiscoveryInterval OBJECT-TYPE 1982 SYNTAX Unsigned32 1983 UNITS "second" 1984 MAX-ACCESS read-only 1985 STATUS current 1986 DESCRIPTION 1987 "Represents the minimum time, in seconds, that a WTP MUST 1988 wait after receiving a Discovery Response message, before 1989 initiating a DTLS handshake." 1990 REFERENCE 1991 "Section 4.7.5. of CAPWAP Protocol Specification, RFC 5415." 1992 DEFVAL { 5 } 1993 ::= { capwapBaseWtpEntry 15 } 1995 capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE 1996 SYNTAX Unsigned32 1997 UNITS "second" 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "Represents the minimum time, in seconds, a WTP MUST wait 2002 for DTLS session deletion." 2003 REFERENCE 2004 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 2005 DEFVAL { 5 } 2006 ::= { capwapBaseWtpEntry 16 } 2008 capwapBaseWtpImageDataStartTimer OBJECT-TYPE 2009 SYNTAX Unsigned32 2010 UNITS "second" 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "Represents the number of seconds the WTP will wait for its 2015 peer to transmit the Image Data Request." 2016 REFERENCE 2017 "Section 4.7.9. of CAPWAP Protocol Specification, RFC 5415." 2018 DEFVAL { 30 } 2019 ::= { capwapBaseWtpEntry 17 } 2021 capwapBaseWtpRetransmitInterval OBJECT-TYPE 2022 SYNTAX Unsigned32 2023 UNITS "second" 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "Represents the minimum time, in seconds, in which a 2028 non-acknowledged CAPWAP packet will be retransmitted." 2029 REFERENCE 2030 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 2031 DEFVAL { 3 } 2032 ::= { capwapBaseWtpEntry 18 } 2034 -- End of capwapBaseWtpTable table 2036 -- capwapBaseWirelessBindingTable Table 2038 capwapBaseWirelessBindingTable OBJECT-TYPE 2039 SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry 2040 MAX-ACCESS not-accessible 2041 STATUS current 2042 DESCRIPTION 2043 "A table of objects that display the mappings between 2044 WTP Virtual Radio Interfaces and PHY radios, and the 2045 wireless binding type for each PHY radio. 2046 As CapwapBaseWirelessBindingTable stores the mappings between 2047 PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio 2048 Interfaces, the operator can get the ifIndex information by 2049 querying this table. Such a query operation SHOULD run from 2050 radio ID 1 to radio ID 31 according to [RFC5415], 2051 and stop when a invalid ifIndex value (0) is returned. 2052 Values of all objects in this table are persistent at 2053 restart/reboot." 2054 ::= { capwapBaseWtps 4 } 2056 capwapBaseWirelessBindingEntry OBJECT-TYPE 2057 SYNTAX CapwapBaseWirelessBindingEntry 2058 MAX-ACCESS not-accessible 2059 STATUS current 2060 DESCRIPTION 2061 "A set of objects that display the mapping between 2062 a specific WTP Virtual Radio Interface and a PHY 2063 radio, and the wireless binding type for the PHY radio." 2064 INDEX { 2065 capwapBaseWtpProfileId, 2066 capwapBaseWirelessBindingRadioId 2067 } 2068 ::= { capwapBaseWirelessBindingTable 1 } 2070 CapwapBaseWirelessBindingEntry ::= SEQUENCE { 2071 capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, 2072 capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, 2073 capwapBaseWirelessBindingType INTEGER 2074 } 2076 capwapBaseWirelessBindingRadioId OBJECT-TYPE 2077 SYNTAX CapwapBaseRadioIdTC 2078 MAX-ACCESS not-accessible 2079 STATUS current 2080 DESCRIPTION 2081 "Represents the identifier of a PHY radio on a WTP, which 2082 is required to be unique on a WTP. 2083 For example, WTP A and WTP B use a same value of 2084 capwapBaseWirelessBindingRadioId for their first radio." 2085 REFERENCE 2086 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2087 ::= { capwapBaseWirelessBindingEntry 1 } 2089 capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE 2090 SYNTAX InterfaceIndex 2091 MAX-ACCESS read-only 2092 STATUS current 2093 DESCRIPTION 2094 "Represents the index value that uniquely identifies a 2095 WLAN Virtual Radio Interface. The interface identified by 2096 a particular value of this index is the same interface as 2097 identified by the same value of the ifIndex. 2098 Before WTPs contact the AC to get configuration, 2099 the operator configures WTP profiles for them. 2100 The creation of a WTP profile triggers system to automatically 2101 create a specific number of WTP Virtual Radio Interfaces and 2102 add a new row object in the capwapBaseWirelessBindingTable 2103 without manual intervention. 2104 As most MIB modules use the ifIndex to identify an interface 2105 for configuration and statistic data, for example, IEEE 802.11 2106 MIB module [IEEE.802-11.2007] 2107 It will be easy to reuse other wireless binding MIB modules 2108 through the WTP Virtual Radio Interface in the Centralized 2109 WLAN Architecture." 2110 ::= { capwapBaseWirelessBindingEntry 2 } 2112 capwapBaseWirelessBindingType OBJECT-TYPE 2113 SYNTAX INTEGER { 2114 dot11(1), 2115 epc(3) 2116 } 2117 MAX-ACCESS read-only 2118 STATUS current 2119 DESCRIPTION 2120 "Represents the wireless binding type for the radio. 2121 The following enumerated values are supported: 2122 dot11(1) - IEEE 802.11 2123 epc(3) - EPCGlobal" 2124 REFERENCE 2125 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2126 ::= { capwapBaseWirelessBindingEntry 3 } 2128 -- End of capwapBaseWirelessBindingTable Table 2130 -- capwapBaseStationTable Table 2132 capwapBaseStationTable OBJECT-TYPE 2133 SYNTAX SEQUENCE OF CapwapBaseStationEntry 2134 MAX-ACCESS not-accessible 2135 STATUS current 2136 DESCRIPTION 2137 "A table of objects that display stations which are accessing 2138 the wireless service provided by the AC." 2139 REFERENCE 2140 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2141 ::= { capwapBaseWtps 5 } 2143 capwapBaseStationEntry OBJECT-TYPE 2144 SYNTAX CapwapBaseStationEntry 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "A set of objects that display a station which is 2149 associated with the specific radio on the WTP. 2150 Note that in some cases such as roaming that a station may 2151 simultaneously associate with two WTPs for some (short) time. 2152 The MIB implementation MUST ensure there is only one valid 2153 and meaningful entry for a specific station." 2154 INDEX { capwapBaseStationId } 2155 ::= { capwapBaseStationTable 1 } 2157 CapwapBaseStationEntry ::= SEQUENCE { 2158 capwapBaseStationId CapwapBaseStationIdTC, 2159 capwapBaseStationWtpId CapwapBaseWtpIdTC, 2160 capwapBaseStationWtpRadioId CapwapBaseRadioIdTC, 2161 capwapBaseStationAddedTime DateAndTime, 2162 capwapBaseStationVlanName SnmpAdminString 2163 } 2165 capwapBaseStationId OBJECT-TYPE 2166 SYNTAX CapwapBaseStationIdTC 2167 MAX-ACCESS not-accessible 2168 STATUS current 2169 DESCRIPTION 2170 "Represents the unique identifier of the station." 2171 REFERENCE 2172 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2173 ::= { capwapBaseStationEntry 1 } 2175 capwapBaseStationWtpId OBJECT-TYPE 2176 SYNTAX CapwapBaseWtpIdTC 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "Represents the unique identifier of a WTP in running state." 2181 ::= { capwapBaseStationEntry 2 } 2183 capwapBaseStationWtpRadioId OBJECT-TYPE 2184 SYNTAX CapwapBaseRadioIdTC 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "Represents the identifier of a PHY radio on a WTP, which 2189 is required to be unique on a WTP. 2190 For example, WTP A and WTP B use a same value of 2191 capwapBaseStationWtpRadioId for their first radio." 2192 REFERENCE 2193 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2194 ::= { capwapBaseStationEntry 3 } 2196 capwapBaseStationAddedTime OBJECT-TYPE 2197 SYNTAX DateAndTime 2198 MAX-ACCESS read-only 2199 STATUS current 2200 DESCRIPTION 2201 "Represents the time when the station is added." 2202 REFERENCE 2203 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2204 ::= { capwapBaseStationEntry 4 } 2206 capwapBaseStationVlanName OBJECT-TYPE 2207 SYNTAX SnmpAdminString (SIZE(0..32)) 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "Represents VLAN name to which the station is associated." 2212 REFERENCE 2213 "Section 4.6.8. of CAPWAP Protocol Specification, RFC 5415." 2214 ::= { capwapBaseStationEntry 5 } 2216 -- End of capwapBaseStationTable Table 2218 -- capwapBaseWtpEventsStatsTable 2219 capwapBaseWtpEventsStatsTable OBJECT-TYPE 2220 SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry 2221 MAX-ACCESS not-accessible 2222 STATUS current 2223 DESCRIPTION 2224 "A table of objects that display the WTPs' events statistics." 2225 REFERENCE 2226 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2227 ::= { capwapBaseWtps 6 } 2229 capwapBaseWtpEventsStatsEntry OBJECT-TYPE 2230 SYNTAX CapwapBaseWtpEventsStatsEntry 2231 MAX-ACCESS not-accessible 2232 STATUS current 2233 DESCRIPTION 2234 "A set of objects that display the events statistic data 2235 of a WTP." 2236 REFERENCE 2237 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2238 INDEX { capwapBaseWtpCurrId } 2239 ::= { capwapBaseWtpEventsStatsTable 1 } 2241 CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { 2242 capwapBaseWtpEventsStatsRebootCount Counter32, 2243 capwapBaseWtpEventsStatsInitCount Counter32, 2244 capwapBaseWtpEventsStatsLinkFailureCount Counter32, 2245 capwapBaseWtpEventsStatsSwFailureCount Counter32, 2246 capwapBaseWtpEventsStatsHwFailureCount Counter32, 2247 capwapBaseWtpEventsStatsOtherFailureCount Counter32, 2248 capwapBaseWtpEventsStatsUnknownFailureCount Counter32, 2249 capwapBaseWtpEventsStatsLastFailureType INTEGER 2250 } 2252 capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE 2253 SYNTAX Counter32 2254 MAX-ACCESS read-only 2255 STATUS current 2256 DESCRIPTION 2257 "Represents the number of reboots that have occurred due to a 2258 WTP crash. 2259 Note that the CAPWAP field [RFC5415] modelled by this counter 2260 takes the value 65535 to indicate that the information is not 2261 available on the WTP. This MIB object does not follow this 2262 behaviour which would not be standard in SMIv2. If the WTP 2263 does not have the information, the agent will not instantiate 2264 the object." 2265 REFERENCE 2266 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2268 ::= { capwapBaseWtpEventsStatsEntry 1 } 2270 capwapBaseWtpEventsStatsInitCount OBJECT-TYPE 2271 SYNTAX Counter32 2272 MAX-ACCESS read-only 2273 STATUS current 2274 DESCRIPTION 2275 "Represents the number of reboots that have occurred at the 2276 request of a CAPWAP protocol message, such as a change in 2277 configuration that requires a reboot or an explicit CAPWAP 2278 protocol reset request. 2279 Note that the CAPWAP field [RFC5415] modelled by this counter 2280 takes the value 65535 to indicate that the information is not 2281 available on the WTP. This MIB object does not follow this 2282 behaviour which would not be standard in SMIv2. If the WTP 2283 does not have the information, the agent will not instantiate 2284 the object." 2285 REFERENCE 2286 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2287 ::= { capwapBaseWtpEventsStatsEntry 2 } 2289 capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE 2290 SYNTAX Counter32 2291 MAX-ACCESS read-only 2292 STATUS current 2293 DESCRIPTION 2294 "Represents the number of times that a CAPWAP protocol 2295 connection with an AC has failed due to link failures." 2296 REFERENCE 2297 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2298 ::= { capwapBaseWtpEventsStatsEntry 3 } 2300 capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE 2301 SYNTAX Counter32 2302 MAX-ACCESS read-only 2303 STATUS current 2304 DESCRIPTION 2305 "Represents the number of times that a CAPWAP protocol 2306 connection with an AC has failed due to software related 2307 reasons." 2308 REFERENCE 2309 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2310 ::= { capwapBaseWtpEventsStatsEntry 4 } 2312 capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE 2313 SYNTAX Counter32 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "Represents the number of times that a CAPWAP protocol 2318 connection with an AC has failed due to hardware related 2319 reasons." 2320 REFERENCE 2321 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2322 ::= { capwapBaseWtpEventsStatsEntry 5 } 2324 capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE 2325 SYNTAX Counter32 2326 MAX-ACCESS read-only 2327 STATUS current 2328 DESCRIPTION 2329 "Represents the number of times that a CAPWAP protocol 2330 connection with an AC has failed due to known reasons, other 2331 than the AC initiated, link, software or hardware failures." 2332 REFERENCE 2333 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2334 ::= { capwapBaseWtpEventsStatsEntry 6 } 2336 capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE 2337 SYNTAX Counter32 2338 MAX-ACCESS read-only 2339 STATUS current 2340 DESCRIPTION 2341 "Represents the number of times that a CAPWAP protocol 2342 connection with an AC has failed for unknown reasons." 2343 REFERENCE 2344 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2345 ::= { capwapBaseWtpEventsStatsEntry 7 } 2347 capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE 2348 SYNTAX INTEGER { 2349 notSupport(0), 2350 acInit(1), 2351 linkFailure(2), 2352 swFailure(3), 2353 hwFailure(4), 2354 otherFailure(5), 2355 unknown(255) 2356 } 2357 MAX-ACCESS read-only 2358 STATUS current 2359 DESCRIPTION 2360 "Represents the failure type of the most recent WTP failure. 2361 The following enumerated values are supported: 2362 notSupport(0) - Not supported 2363 acInit(1) - The AC initiated 2364 linkFailure(2) - Link failure 2365 swFailure(3) - Software failure 2366 hwFailure(4) - Hardware failure 2367 otherFailure(5) - Other failure 2368 unknown(255) - Unknown (e.g., WTP doesn't keep track 2369 of info) 2370 Note that the CAPWAP field [RFC5415] modelled by this 2371 object takes zero as starting value, this MIB object 2372 follows this rule." 2373 REFERENCE 2374 "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415." 2375 ::= { capwapBaseWtpEventsStatsEntry 8 } 2377 -- End of capwapBaseWtpEventsStatsTable table 2379 -- capwapBaseRadioEventsStatsTable table 2381 capwapBaseRadioEventsStatsTable OBJECT-TYPE 2382 SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry 2383 MAX-ACCESS not-accessible 2384 STATUS current 2385 DESCRIPTION 2386 "A table of objects that display statistics on radios behavior, 2387 and reasons why the WTP radio has been reset. 2388 To get all radios' event statistic on a specific WTP 2389 (identified by the capwapBaseWtpCurrId), it needs a query 2390 operation SHOULD run from radio ID 1 to radio ID 31 till there 2391 is no data returned. The radio ID here corresponds to the 2392 object capwapBaseRadioEventsWtpRadioId. If the previous MIB 2393 operations such as query on the CapwapBaseWirelessBindingTable 2394 know the exact value of each radio ID, the query operation on 2395 the capwapBaseRadioEventsStatsTable could use that value 2396 of Radio IDs." 2397 REFERENCE 2398 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2399 ::= { capwapBaseWtps 7 } 2401 capwapBaseRadioEventsStatsEntry OBJECT-TYPE 2402 SYNTAX CapwapBaseRadioEventsStatsEntry 2403 MAX-ACCESS not-accessible 2404 STATUS current 2405 DESCRIPTION 2406 "A set of objects that display the statistic data of 2407 events happened on a specific radio of a WTP." 2408 INDEX { capwapBaseWtpCurrId, capwapBaseRadioEventsWtpRadioId } 2409 ::= { capwapBaseRadioEventsStatsTable 1 } 2411 CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { 2412 capwapBaseRadioEventsWtpRadioId CapwapBaseRadioIdTC, 2413 capwapBaseRadioEventsStatsResetCount Counter32, 2414 capwapBaseRadioEventsStatsSwFailCount Counter32, 2415 capwapBaseRadioEventsStatsHwFailCount Counter32, 2416 capwapBaseRadioEventsStatsOtherFailCount Counter32, 2417 capwapBaseRadioEventsStatsUnknownFailCount Counter32, 2418 capwapBaseRadioEventsStatsConfigUpdateCount Counter32, 2419 capwapBaseRadioEventsStatsChannelChangeCount Counter32, 2420 capwapBaseRadioEventsStatsBandChangeCount Counter32, 2421 capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, 2422 capwapBaseRadioEventsStatsDecryptErrorCount Counter32, 2423 capwapBaseRadioEventsStatsLastFailType INTEGER 2424 } 2426 capwapBaseRadioEventsWtpRadioId OBJECT-TYPE 2427 SYNTAX CapwapBaseRadioIdTC 2428 MAX-ACCESS not-accessible 2429 STATUS current 2430 DESCRIPTION 2431 "Represents the identifier of a PHY radio on a WTP, which 2432 is required to be unique on a WTP. 2433 For example, WTP A and WTP B use a same value of 2434 capwapBaseRadioEventsWtpRadioId for their first radio." 2435 REFERENCE 2436 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2437 ::= { capwapBaseRadioEventsStatsEntry 1 } 2439 capwapBaseRadioEventsStatsResetCount OBJECT-TYPE 2440 SYNTAX Counter32 2441 MAX-ACCESS read-only 2442 STATUS current 2443 DESCRIPTION 2444 "Represents the number of times that that the radio has been 2445 reset." 2446 REFERENCE 2447 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2448 ::= { capwapBaseRadioEventsStatsEntry 2 } 2450 capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE 2451 SYNTAX Counter32 2452 MAX-ACCESS read-only 2453 STATUS current 2454 DESCRIPTION 2455 "Represents the number of times that the radio has failed due 2456 to software related reasons." 2457 REFERENCE 2458 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2460 ::= { capwapBaseRadioEventsStatsEntry 3 } 2462 capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE 2463 SYNTAX Counter32 2464 MAX-ACCESS read-only 2465 STATUS current 2466 DESCRIPTION 2467 "Represents the number of times that the radio has failed due 2468 to hardware related reasons." 2469 REFERENCE 2470 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2471 ::= { capwapBaseRadioEventsStatsEntry 4 } 2473 capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE 2474 SYNTAX Counter32 2475 MAX-ACCESS read-only 2476 STATUS current 2477 DESCRIPTION 2478 "Represents the number of times that the radio has failed due to 2479 known reasons, other than software or hardware failure." 2480 REFERENCE 2481 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2482 ::= { capwapBaseRadioEventsStatsEntry 5 } 2484 capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE 2485 SYNTAX Counter32 2486 MAX-ACCESS read-only 2487 STATUS current 2488 DESCRIPTION 2489 "Represents the number of times that the radio has failed for 2490 unknown reasons." 2491 REFERENCE 2492 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2493 ::= { capwapBaseRadioEventsStatsEntry 6 } 2495 capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE 2496 SYNTAX Counter32 2497 MAX-ACCESS read-only 2498 STATUS current 2499 DESCRIPTION 2500 "Represents the number of times that the radio configuration has 2501 been updated." 2502 REFERENCE 2503 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2504 ::= { capwapBaseRadioEventsStatsEntry 7 } 2506 capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE 2507 SYNTAX Counter32 2508 MAX-ACCESS read-only 2509 STATUS current 2510 DESCRIPTION 2511 "Represents the number of times that the radio channel has 2512 been changed." 2513 REFERENCE 2514 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2515 ::= { capwapBaseRadioEventsStatsEntry 8 } 2517 capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE 2518 SYNTAX Counter32 2519 MAX-ACCESS read-only 2520 STATUS current 2521 DESCRIPTION 2522 "Represents the number of times that the radio has changed 2523 frequency bands." 2524 REFERENCE 2525 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2526 ::= { capwapBaseRadioEventsStatsEntry 9 } 2528 capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE 2529 SYNTAX Integer32 2530 UNITS "dBm" 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "Represents the noise floor of the radio receiver in units of 2535 dBm." 2536 REFERENCE 2537 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2538 ::= { capwapBaseRadioEventsStatsEntry 10 } 2540 capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE 2541 SYNTAX Counter32 2542 MAX-ACCESS read-only 2543 STATUS current 2544 DESCRIPTION 2545 "Represents the number of decryption errors that have occurred 2546 on the WTP. Note that this field is only valid in cases where 2547 the WTP provides encryption/decryption services." 2548 REFERENCE 2549 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2550 ::= { capwapBaseRadioEventsStatsEntry 11 } 2552 capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE 2553 SYNTAX INTEGER { 2554 notSupport(0), 2555 swFailure(1), 2556 hwFailure(2), 2557 otherFailure(3), 2558 unknown(255) 2559 } 2560 MAX-ACCESS read-only 2561 STATUS current 2562 DESCRIPTION 2563 "Represents the failure type of the most recent radio failure. 2564 The following enumerated values are supported: 2565 notSupport(0) - Not supported 2566 swFailure(1) - Software failure 2567 hwFailure(2) - Hardware failure 2568 otherFailure(3) - Other failure 2569 unknown(255) - Unknown 2570 Note that the CAPWAP field [RFC5415] modelled by this 2571 object takes zero as starting value, this MIB object follows 2572 this rule." 2573 REFERENCE 2574 "Section 4.6.46. of CAPWAP Protocol Specification, RFC 5415." 2575 ::= { capwapBaseRadioEventsStatsEntry 12 } 2577 -- End of capwapBaseRadioEventsStatsTable table 2579 -- End of WTP Objects Group 2581 -- CAPWAP Base Parameters Group 2583 capwapBaseParameters OBJECT IDENTIFIER 2584 ::= { capwapBaseObjects 3 } 2586 capwapBaseAcMaxRetransmit OBJECT-TYPE 2587 SYNTAX Unsigned32 2588 MAX-ACCESS read-write 2589 STATUS current 2590 DESCRIPTION 2591 "Represents the maximum number of retransmissions for a given 2592 CAPWAP packet before the link layer considers the peer dead. 2593 The value of the object is persistent at restart/reboot." 2594 REFERENCE 2595 "Section 4.8.7. of CAPWAP Protocol Specification, RFC 5415." 2596 DEFVAL { 5 } 2597 ::= { capwapBaseParameters 1 } 2599 capwapBaseAcChangeStatePendingTimer OBJECT-TYPE 2600 SYNTAX Unsigned32 2601 UNITS "second" 2602 MAX-ACCESS read-write 2603 STATUS current 2604 DESCRIPTION 2605 "Represents the maximum time, in seconds, the AC will wait 2606 for the Change State Event Request from the WTP after having 2607 transmitted a successful Configuration Status Response 2608 message. 2609 The value of the object is persistent at restart/reboot." 2610 REFERENCE 2611 "Section 4.7.1. of CAPWAP Protocol Specification, RFC 5415." 2612 DEFVAL { 25 } 2613 ::= { capwapBaseParameters 2 } 2615 capwapBaseAcDataCheckTimer OBJECT-TYPE 2616 SYNTAX Unsigned32 2617 UNITS "second" 2618 MAX-ACCESS read-write 2619 STATUS current 2620 DESCRIPTION 2621 "Represents The number of seconds the AC will wait for 2622 the Data Channel Keep Alive, which is required by the 2623 CAPWAP state machine's Data Check state. 2624 The AC resets the state machine if this timer expires 2625 prior to transitioning to the next state. 2626 The value of the object is persistent at restart/reboot." 2627 REFERENCE 2628 "Section 4.7.4. of CAPWAP Protocol Specification, RFC 5415." 2629 DEFVAL { 30 } 2630 ::= { capwapBaseParameters 3 } 2632 capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE 2633 SYNTAX Unsigned32 2634 UNITS "second" 2635 MAX-ACCESS read-write 2636 STATUS current 2637 DESCRIPTION 2638 "Represents the minimum time, in seconds, the AC MUST wait 2639 for DTLS session deletion. 2640 The value of the object is persistent at restart/reboot." 2641 REFERENCE 2642 "Section 4.7.6. of CAPWAP Protocol Specification, RFC 5415." 2643 DEFVAL { 5 } 2644 ::= { capwapBaseParameters 4 } 2646 capwapBaseAcEchoInterval OBJECT-TYPE 2647 SYNTAX Unsigned32 2648 UNITS "second" 2649 MAX-ACCESS read-write 2650 STATUS current 2651 DESCRIPTION 2652 "Represents the minimum time, in seconds, between sending Echo 2653 Request messages to the AC with which the WTP has joined. 2654 The value of the object is persistent at restart/reboot." 2655 REFERENCE 2656 "Section 4.7.7. of CAPWAP Protocol Specification, RFC 5415." 2657 DEFVAL { 30 } 2658 ::= { capwapBaseParameters 5 } 2660 capwapBaseAcRetransmitInterval OBJECT-TYPE 2661 SYNTAX Unsigned32 2662 UNITS "second" 2663 MAX-ACCESS read-write 2664 STATUS current 2665 DESCRIPTION 2666 "Represents the minimum time, in seconds, in which a 2667 non-acknowledged CAPWAP packet will be retransmitted. 2668 The value of the object is persistent at restart/reboot." 2669 REFERENCE 2670 "Section 4.7.12. of CAPWAP Protocol Specification, RFC 5415." 2671 DEFVAL { 3 } 2672 ::= { capwapBaseParameters 6 } 2674 capwapBaseAcSilentInterval OBJECT-TYPE 2675 SYNTAX Unsigned32 2676 UNITS "second" 2677 MAX-ACCESS read-write 2678 STATUS current 2679 DESCRIPTION 2680 "Represents the minimum time, in seconds, during which the AC 2681 SHOULD ignore all CAPWAP and DTLS packets received from the 2682 WTP that is in the Sulking state. 2683 The value of the object is persistent at restart/reboot." 2684 REFERENCE 2685 "Section 4.7.13. of CAPWAP Protocol Specification, RFC 5415." 2686 DEFVAL { 30 } 2687 ::= { capwapBaseParameters 7 } 2689 capwapBaseAcWaitDTLSTimer OBJECT-TYPE 2690 SYNTAX Unsigned32 (30..4294967295) 2691 UNITS "second" 2692 MAX-ACCESS read-write 2693 STATUS current 2694 DESCRIPTION 2695 "Represents the maximum time, in seconds, the AC MUST wait 2696 without having received a DTLS Handshake message from an AC. 2697 This timer MUST be greater than 30 seconds. 2698 The value of the object is persistent at restart/reboot." 2700 REFERENCE 2701 "Section 4.7.15. of CAPWAP Protocol Specification, RFC 5415." 2702 DEFVAL { 60 } 2703 ::= { capwapBaseParameters 8 } 2705 capwapBaseAcWaitJoinTimer OBJECT-TYPE 2706 SYNTAX Unsigned32 (20..4294967295) 2707 UNITS "second" 2708 MAX-ACCESS read-write 2709 STATUS current 2710 DESCRIPTION 2711 "Represents the maximum time, in seconds, the AC will wait 2712 after the DTLS session has been established until it receives 2713 the Join Request from the WTP. This timer MUST be greater 2714 than 20 seconds. 2715 The value of the object is persistent at restart/reboot." 2716 REFERENCE 2717 "Section 4.7.16. of CAPWAP Protocol Specification, RFC 5415." 2718 DEFVAL { 60 } 2719 ::= { capwapBaseParameters 9 } 2721 capwapBaseAcEcnSupport OBJECT-TYPE 2722 SYNTAX INTEGER { 2723 limited(0), 2724 fullAndLimited(1) 2725 } 2726 MAX-ACCESS read-write 2727 STATUS current 2728 DESCRIPTION 2729 "Represents the support for the Explicit Congestion Notification 2730 (ECN) bits, as defined in [RFC3168]. 2731 The value of the object is persistent at restart/reboot. 2732 The following enumerated values are supported: 2733 limited(0) - Limited ECN support 2734 fullAndLimited(1) - Full and limited ECN support 2735 Note that the CAPWAP field [RFC5415] modelled by this 2736 object takes zero as starting value, this MIB object follows 2737 this rule." 2738 REFERENCE 2739 "Section 4.6.25. of CAPWAP Protocol Specification, RFC 5415." 2740 ::= { capwapBaseParameters 10 } 2742 -- End of CAPWAP Base Parameters Group 2744 -- CAPWAP Statistics Group 2746 capwapBaseStats OBJECT IDENTIFIER 2747 ::= { capwapBaseObjects 4 } 2749 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 2750 SYNTAX Counter32 2751 MAX-ACCESS read-only 2752 STATUS current 2753 DESCRIPTION 2754 "Represents the number of failed DTLS session establishment 2755 attempts due to authentication failures." 2756 REFERENCE 2757 "Section 4.8.3. of CAPWAP Protocol Specification, RFC 5415." 2758 ::= { capwapBaseStats 1 } 2760 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 2761 SYNTAX Counter32 2762 MAX-ACCESS read-only 2763 STATUS current 2764 DESCRIPTION 2765 "Represents the number of failed DTLS session 2766 establishment attempts." 2767 REFERENCE 2768 "Section 4.8.4. of CAPWAP Protocol Specification, RFC 5415." 2769 ::= { capwapBaseStats 2 } 2771 -- Notifications 2773 capwapBaseChannelUp NOTIFICATION-TYPE 2774 OBJECTS { 2775 capwapBaseNtfWtpId, 2776 capwapBaseNtfChannelType, 2777 capwapBaseNtfAuthenMethod 2778 } 2779 STATUS current 2780 DESCRIPTION 2781 "This notification is sent by the AC when a CAPWAP channel 2782 established. 2783 The notification is separated for data or control channel." 2784 ::= { capwapBaseNotifications 1 } 2786 capwapBaseChannelDown NOTIFICATION-TYPE 2787 OBJECTS { 2788 capwapBaseNtfWtpId, 2789 capwapBaseNtfChannelType, 2790 capwapBaseNtfChannelDownReason 2791 } 2792 STATUS current 2793 DESCRIPTION 2794 "This notification is sent by the AC when CAPWAP channel 2795 becomes down. 2796 The notification is separated for data or control channel." 2797 ::= { capwapBaseNotifications 2 } 2799 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 2800 OBJECTS { 2801 capwapBaseNtfWtpId, 2802 capwapBaseNtfRadioId, 2803 capwapBaseNtfStationIdList 2804 } 2805 STATUS current 2806 DESCRIPTION 2807 "This notification is generated when a WTP that has occurred 2808 decryption error since the last report." 2809 REFERENCE 2810 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2811 ::= { capwapBaseNotifications 3 } 2813 capwapBaseJoinFailure NOTIFICATION-TYPE 2814 OBJECTS { 2815 capwapBaseNtfWtpId, 2816 capwapBaseNtfJoinFailureReason 2817 } 2818 STATUS current 2819 DESCRIPTION 2820 "This notification is generated when a WTP fails to join." 2821 REFERENCE 2822 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2823 ::= { capwapBaseNotifications 4 } 2825 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 2826 OBJECTS { 2827 capwapBaseNtfWtpId, 2828 capwapBaseNtfImageFailureReason 2829 } 2830 STATUS current 2831 DESCRIPTION 2832 "This notification is generated when a WTP fails to update 2833 the firmware image." 2834 REFERENCE 2835 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2836 ::= { capwapBaseNotifications 5 } 2838 capwapBaseConfigMsgError NOTIFICATION-TYPE 2839 OBJECTS { 2840 capwapBaseNtfWtpId, 2841 capwapBaseNtfConfigMsgErrorType, 2842 capwapBaseNtfMsgErrorElements 2844 } 2845 STATUS current 2846 DESCRIPTION 2847 "This notification is generated when a WTP receives message 2848 elements in the configuration management messages which it 2849 is unable to apply locally." 2850 REFERENCE 2851 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 2852 ::= { capwapBaseNotifications 6 } 2854 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2855 OBJECTS { 2856 capwapBaseNtfWtpId, 2857 capwapBaseNtfRadioId, 2858 capwapBaseNtfRadioOperStatusFlag, 2859 capwapBaseNtfRadioStatusCause 2860 } 2861 STATUS current 2862 DESCRIPTION 2863 "The notification is generated when a radio's operational state 2864 is changed." 2865 REFERENCE 2866 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 2867 ::= { capwapBaseNotifications 7 } 2869 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2870 OBJECTS { 2871 capwapBaseNtfWtpId, 2872 capwapBaseNtfChannelType, 2873 capwapBaseNtfAuthenMethod, 2874 capwapBaseNtfAuthenFailureReason 2875 } 2876 STATUS current 2877 DESCRIPTION 2878 "The notification notifies an authentication failure event, 2879 and provides the reason for it." 2880 ::= { capwapBaseNotifications 8 } 2882 -- Objects used only in notifications 2884 -- Notification Objects 2885 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2886 ::= { capwapBaseObjects 5 } 2888 capwapBaseNtfWtpId OBJECT-TYPE 2889 SYNTAX CapwapBaseWtpIdTC 2890 MAX-ACCESS accessible-for-notify 2891 STATUS current 2892 DESCRIPTION 2893 "Represents the unique identifier of a WTP." 2894 ::= { capwapBaseNotifyVarObjects 1 } 2896 capwapBaseNtfRadioId OBJECT-TYPE 2897 SYNTAX CapwapBaseRadioIdTC 2898 MAX-ACCESS accessible-for-notify 2899 STATUS current 2900 DESCRIPTION 2901 "Represents the identifier of a PHY radio on a WTP, which is 2902 only required to be unique on a WTP. 2903 For example, WTP A and WTP B can use the same value of 2904 capwapBaseNtfRadioId for their first radio." 2905 REFERENCE 2906 "Section 4.3. of CAPWAP Protocol Specification, RFC 5415." 2907 ::= { capwapBaseNotifyVarObjects 2 } 2909 capwapBaseNtfChannelType OBJECT-TYPE 2910 SYNTAX CapwapBaseChannelTypeTC 2911 MAX-ACCESS accessible-for-notify 2912 STATUS current 2913 DESCRIPTION 2914 "Represents the channel type for CAPWAP protocol." 2915 ::= { capwapBaseNotifyVarObjects 3 } 2917 capwapBaseNtfAuthenMethod OBJECT-TYPE 2918 SYNTAX CapwapBaseAuthenMethodTC 2919 MAX-ACCESS accessible-for-notify 2920 STATUS current 2921 DESCRIPTION 2922 "Represents authentication method for CAPWAP Channel." 2923 ::= { capwapBaseNotifyVarObjects 4 } 2925 capwapBaseNtfChannelDownReason OBJECT-TYPE 2926 SYNTAX INTEGER { 2927 timeout(1), 2928 rekeyfailure(2), 2929 acRebootWtp(3), 2930 dtlsError(4), 2931 maxRetransmit(5) 2932 } 2933 MAX-ACCESS accessible-for-notify 2934 STATUS current 2935 DESCRIPTION 2936 "Represents the reason for Channel down. 2937 The following enumerated values are supported: 2938 timeout(1) - The keep alive is timeout 2939 rekeyfailure(2) - Rekey process is failed, channel will be 2940 broken 2941 acRebootWtp(3) - The AC reboot WTP 2942 dtlsError(4) - DTLS notifications: DTLSAborted, 2943 DTLSReassemblyFailure, DTLSPeerDisconnect, 2944 or frequent DTLSDecapFailure 2945 maxRetransmit(5) - The underlying reliable transport's 2946 RetransmitCount counter has reached the 2947 MaxRetransmit variable" 2948 ::= { capwapBaseNotifyVarObjects 5 } 2950 capwapBaseNtfStationIdList OBJECT-TYPE 2951 SYNTAX LongUtf8String (SIZE (6..1024)) 2952 MAX-ACCESS accessible-for-notify 2953 STATUS current 2954 DESCRIPTION 2955 "Represents a list of station identifiers separated by 2956 semicolons." 2957 REFERENCE 2958 "Section 4.6.17. of CAPWAP Protocol Specification, RFC 5415." 2959 ::= { capwapBaseNotifyVarObjects 6 } 2961 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2962 SYNTAX INTEGER { 2963 keyMismatch(1), 2964 invalidCert(2), 2965 reassemblyFailure(3), 2966 decapFailure(4), 2967 encapFailure(5), 2968 timeout(6), 2969 unknown(8) 2970 } 2971 MAX-ACCESS accessible-for-notify 2972 STATUS current 2973 DESCRIPTION 2974 "Represents reason for WTP authorization failure. 2975 The following enumerated values are supported: 2976 keyMismatch(1) - WTP's and AC's key are not matched 2977 invalidCert(2) - Certification is not valid 2978 reassemblyFailure(3) - Fragment reassembly failure 2979 decapFailure(4) - Decapsulation error 2980 encapFailure(5) - Encapsulation error 2981 timeout(6) - WaitDTLS timer timeout 2982 unknown(8) - Unknown reason" 2983 REFERENCE 2984 "Section 2.3.1. of CAPWAP Protocol Specification, RFC 5415." 2985 ::= { capwapBaseNotifyVarObjects 7 } 2987 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2988 SYNTAX INTEGER { 2989 operable(0), 2990 inoperable(1) 2991 } 2992 MAX-ACCESS accessible-for-notify 2993 STATUS current 2994 DESCRIPTION 2995 "Represents the operation status of a radio. 2996 The following enumerated values are supported: 2997 operable(0) - The radio is operable 2998 inoperable(1) - The radio is inoperable, and the 2999 capwapBaseNtfRadioStatusCause object 3000 gives the reason in details 3001 Note that the CAPWAP field [RFC5415] modelled by this 3002 object takes zero as starting value, this MIB object 3003 follows this rule." 3004 REFERENCE 3005 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 3006 ::= { capwapBaseNotifyVarObjects 8 } 3008 capwapBaseNtfRadioStatusCause OBJECT-TYPE 3009 SYNTAX INTEGER { 3010 normal(0), 3011 hwError(1), 3012 swError(2), 3013 adminSet(3) 3014 } 3015 MAX-ACCESS accessible-for-notify 3016 STATUS current 3017 DESCRIPTION 3018 "Represents the reason why radio is out of service. 3019 The following enumerated values are supported: 3020 normal(0) - Normal status 3021 hwError(1) - Radio failure 3022 swError(2) - Software failure 3023 adminSet(3) - Administratively set 3024 Note that the CAPWAP field [RFC5415] modelled by this 3025 object takes zero as starting value, this MIB object 3026 follows this rule." 3027 REFERENCE 3028 "Section 4.6.34. of CAPWAP Protocol Specification, RFC 5415." 3029 ::= { capwapBaseNotifyVarObjects 9 } 3031 capwapBaseNtfJoinFailureReason OBJECT-TYPE 3032 SYNTAX INTEGER { 3033 unspecified(1), 3034 resDepletion(2), 3035 unknownSource(3), 3036 incorrectData(4), 3037 sessionIdInUse(5), 3038 notSupportHw(6), 3039 notSupportBinding(7) 3040 } 3041 MAX-ACCESS accessible-for-notify 3042 STATUS current 3043 DESCRIPTION 3044 "Represents the reason of join failure. 3045 The following enumerated values are supported: 3046 unspecified(1) - Unspecified failure reason 3047 resDepletion(2) - Resource depletion 3048 unknownSource(3) - Unknown source 3049 incorrectData(4) - Incorrect data 3050 sessionIdInUse(5) - Session ID already in use 3051 notSupportHw(6) - WTP hardware not supported 3052 notSupportBinding(7) - Binding not supported" 3053 REFERENCE 3054 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 3055 ::= { capwapBaseNotifyVarObjects 10 } 3057 capwapBaseNtfImageFailureReason OBJECT-TYPE 3058 SYNTAX INTEGER { 3059 invalidChecksum(1), 3060 invalidLength(2), 3061 other(3), 3062 inStorage(4) 3063 } 3064 MAX-ACCESS accessible-for-notify 3065 STATUS current 3066 DESCRIPTION 3067 "Represents the reason of image failure. 3068 The following enumerated values are supported: 3069 invalidChecksum(1) - Invalid checksum 3070 invalidLength(2) - Invalid data length 3071 other(3) - Other error 3072 inStorage(4) - Image already present" 3073 REFERENCE 3074 "Section 4.6.35. of CAPWAP Protocol Specification, RFC 5415." 3075 ::= { capwapBaseNotifyVarObjects 11 } 3077 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 3078 SYNTAX INTEGER { 3079 unknownElement(1), 3080 unsupportedElement(2), 3081 unknownValue(3), 3082 unsupportedValue(4) 3084 } 3085 MAX-ACCESS accessible-for-notify 3086 STATUS current 3087 DESCRIPTION 3088 "Represents the type of configuration message error. 3089 The following enumerated values are supported: 3090 unknownElement(1) - Unknown message element 3091 unsupportedElement(2) - Unsupported message element 3092 unknownValue(3) - Unknown message element value 3093 unsupportedValue(4) - Unsupported message element value" 3094 REFERENCE 3095 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 3096 ::= { capwapBaseNotifyVarObjects 12 } 3098 capwapBaseNtfMsgErrorElements OBJECT-TYPE 3099 SYNTAX SnmpAdminString 3100 MAX-ACCESS accessible-for-notify 3101 STATUS current 3102 DESCRIPTION 3103 "Represents the message elements sent by the AC in the 3104 Configuration Status Response message that caused the error." 3105 REFERENCE 3106 "Section 4.6.36. of CAPWAP Protocol Specification, RFC 5415." 3107 ::= { capwapBaseNotifyVarObjects 13 } 3109 -- Notification Control 3110 capwapBaseNotifyControlObjects OBJECT IDENTIFIER 3111 ::= { capwapBaseObjects 6 } 3113 capwapBaseChannelUpDownNotifyEnable OBJECT-TYPE 3114 SYNTAX TruthValue 3115 MAX-ACCESS read-write 3116 STATUS current 3117 DESCRIPTION 3118 "Represents whether the Channel Up/Channel Down notification 3119 should be generated. 3120 A value of true(1) means that the notification is enabled 3121 A value of false(2) means that the notification is disabled" 3122 DEFVAL { false } 3123 ::= { capwapBaseNotifyControlObjects 1 } 3125 capwapBaseDecryptErrorNotifyEnable OBJECT-TYPE 3126 SYNTAX TruthValue 3127 MAX-ACCESS read-write 3128 STATUS current 3129 DESCRIPTION 3130 "Represents whether the decryption error notification should 3131 be generated. 3133 A value of true(1) means that the notification is enabled 3134 A value of false(2) means that the notification is disabled" 3135 DEFVAL { true } 3136 ::= { capwapBaseNotifyControlObjects 2 } 3138 capwapBaseJoinFailureNotifyEnable OBJECT-TYPE 3139 SYNTAX TruthValue 3140 MAX-ACCESS read-write 3141 STATUS current 3142 DESCRIPTION 3143 "Represents whether the notification of WTP join failure should 3144 be generated. 3145 A value of true(1) means that the notification is enabled 3146 A value of false(2) means that the notification is disabled" 3147 DEFVAL { true } 3148 ::= { capwapBaseNotifyControlObjects 3 } 3150 capwapBaseImageUpgradeFailureNotifyEnable OBJECT-TYPE 3151 SYNTAX TruthValue 3152 MAX-ACCESS read-write 3153 STATUS current 3154 DESCRIPTION 3155 "Represents whether the notification of WTP image upgrade 3156 failure should be generated. 3157 A value of true(1) means that the notification is enabled 3158 A value of false(2) means that the notification is disabled" 3159 DEFVAL { true } 3160 ::= { capwapBaseNotifyControlObjects 4 } 3162 capwapBaseConfigMsgErrorNotifyEnable OBJECT-TYPE 3163 SYNTAX TruthValue 3164 MAX-ACCESS read-write 3165 STATUS current 3166 DESCRIPTION 3167 "Represents whether the notification of configuration message 3168 error should be generated. 3169 A value of true(1) means that the notification is enabled 3170 A value of false(2) means that the notification is disabled" 3171 DEFVAL { false } 3172 ::= { capwapBaseNotifyControlObjects 5 } 3174 capwapBaseRadioOperableStatusNotifyEnable OBJECT-TYPE 3175 SYNTAX TruthValue 3176 MAX-ACCESS read-write 3177 STATUS current 3178 DESCRIPTION 3179 "Represents whether the notification of a radio's operational 3180 state change should be generated. 3182 A value of true(1) means that the notification is enabled 3183 A value of false(2) means that the notification is disabled" 3184 DEFVAL { false } 3185 ::= { capwapBaseNotifyControlObjects 6 } 3187 capwapBaseAuthenticationFailureNotifyEnable OBJECT-TYPE 3188 SYNTAX TruthValue 3189 MAX-ACCESS read-write 3190 STATUS current 3191 DESCRIPTION 3192 "Represents whether the notification of authentication failure 3193 should be generated. 3194 A value of true(1) means that the notification is enabled 3195 A value of false(2) means that the notification is disabled" 3196 DEFVAL { true } 3197 ::= { capwapBaseNotifyControlObjects 7 } 3199 -- Module compliance 3201 capwapBaseCompliances OBJECT IDENTIFIER 3202 ::= { capwapBaseConformance 1 } 3204 capwapBaseGroups OBJECT IDENTIFIER 3205 ::= { capwapBaseConformance 2 } 3207 capwapBaseCompliance MODULE-COMPLIANCE 3208 STATUS current 3209 DESCRIPTION 3210 "Describes the requirements for conformance to the 3211 CAPWAP-BASE-MIB module." 3213 MODULE IF-MIB -- The interfaces MIB, RFC2863 3214 MANDATORY-GROUPS { 3215 ifGeneralInformationGroup 3216 } 3218 MODULE -- this module 3219 MANDATORY-GROUPS { 3220 capwapBaseAcNodeGroup, 3221 capwapBaseWtpProfileGroup, 3222 capwapBaseWtpStateGroup, 3223 capwapBaseWtpGroup, 3224 capwapBaseRadioGroup, 3225 capwapBaseStationGroup 3226 } 3228 GROUP capwapBaseAcNodeGroup2 3229 DESCRIPTION 3230 "The capwapBaseAcNodeGroup2 group is optional." 3232 GROUP capwapBaseAcNameListGroup 3233 DESCRIPTION 3234 "The capwapBaseAcNameListGroup group is optional." 3236 GROUP capwapBaseMacAclsGroup 3237 DESCRIPTION 3238 "The capwapBaseMacAclsGroup group is optional." 3240 GROUP capwapBaseWtpProfileGroup2 3241 DESCRIPTION 3242 "The capwapBaseWtpProfileGroup2 group is optional." 3244 GROUP capwapBaseWtpGroup2 3245 DESCRIPTION 3246 "The capwapBaseWtpGroup2 group is optional." 3248 GROUP capwapBaseWtpEventsStatsGroup 3249 DESCRIPTION 3250 "The capwapBaseWtpEventsStatsGroup group is optional." 3252 GROUP capwapBaseRadioEventsStatsGroup 3253 DESCRIPTION 3254 "The capwapBaseRadioEventsStatsGroup group is optional." 3256 GROUP capwapBaseParametersGroup 3257 DESCRIPTION 3258 "The capwapBaseParametersGroup group is optional." 3260 GROUP capwapBaseStatsGroup 3261 DESCRIPTION 3262 "The capwapBaseStatsGroup group is optional." 3264 GROUP capwapBaseNotificationsGroup 3265 DESCRIPTION 3266 "The capwapBaseNotificationsGroup group is optional." 3268 GROUP capwapBaseNotifyVarsGroup 3269 DESCRIPTION 3270 "The capwapBaseNotifyVarsGroup group is optional. 3271 If capwapBaseNotificationsGroup is supported, 3272 this group must be implemented." 3274 GROUP capwapBaseNotifyControlGroup 3275 DESCRIPTION 3276 "The capwapBaseNotifyControlGroup group is optional. 3277 If capwapBaseNotificationsGroup is supported, 3278 this group must be implemented." 3279 ::= { capwapBaseCompliances 1 } 3281 capwapBaseAcNodeGroup OBJECT-GROUP 3282 OBJECTS { 3283 capwapBaseWtpSessions, 3284 capwapBaseWtpSessionsLimit, 3285 capwapBaseStationSessions, 3286 capwapBaseStationSessionsLimit 3287 } 3288 STATUS current 3289 DESCRIPTION 3290 "A collection of objects which are used to represent 3291 the basic properties for the AC from the CAPWAP 3292 protocol perspective." 3293 ::= { capwapBaseGroups 1 } 3295 capwapBaseAcNodeGroup2 OBJECT-GROUP 3296 OBJECTS { 3297 capwapBaseDataChannelDTLSPolicyOptions, 3298 capwapBaseDataChannelDTLSPolicyConfig, 3299 capwapBaseControlChannelAuthenOptions, 3300 capwapBaseControlChannelAuthenConfig 3301 } 3302 STATUS current 3303 DESCRIPTION 3304 "A collection of objects which are used to represent 3305 the other properties such as security for the AC from 3306 the CAPWAP protocol perspective." 3307 ::= { capwapBaseGroups 2 } 3309 capwapBaseAcNameListGroup OBJECT-GROUP 3310 OBJECTS { 3311 capwapBaseAcNameListName, 3312 capwapBaseAcNameListPriority, 3313 capwapBaseAcNameListRowStatus 3314 } 3315 STATUS current 3316 DESCRIPTION 3317 "A collection of objects which are used to configure 3318 the AC name list." 3319 ::= { capwapBaseGroups 3 } 3321 capwapBaseMacAclsGroup OBJECT-GROUP 3322 OBJECTS { 3323 capwapBaseMacAclStationId, 3324 capwapBaseMacAclRowStatus 3325 } 3326 STATUS current 3327 DESCRIPTION 3328 "A collection of objects which are used to configure 3329 the stations ACL." 3330 ::= { capwapBaseGroups 4 } 3332 capwapBaseWtpProfileGroup OBJECT-GROUP 3333 OBJECTS { 3334 capwapBaseWtpProfileName, 3335 capwapBaseWtpProfileWtpMacAddr, 3336 capwapBaseWtpProfileWtpModelNumber, 3337 capwapBaseWtpProfileWtpName, 3338 capwapBaseWtpProfileWtpLocation, 3339 capwapBaseWtpProfileRowStatus 3340 } 3341 STATUS current 3342 DESCRIPTION 3343 "A collection of objects which are used to configure 3344 the WTP profile." 3345 ::= { capwapBaseGroups 5 } 3347 capwapBaseWtpProfileGroup2 OBJECT-GROUP 3348 OBJECTS { 3349 capwapBaseWtpProfileWtpStaticIpEnable, 3350 capwapBaseWtpProfileWtpStaticIpType, 3351 capwapBaseWtpProfileWtpStaticIp, 3352 capwapBaseWtpProfileWtpNetmask, 3353 capwapBaseWtpProfileWtpGateway, 3354 capwapBaseWtpProfileWtpFallbackEnable, 3355 capwapBaseWtpProfileWtpEchoInterval, 3356 capwapBaseWtpProfileWtpIdleTimeout, 3357 capwapBaseWtpProfileWtpMaxDiscoveryInterval, 3358 capwapBaseWtpProfileWtpReportInterval, 3359 capwapBaseWtpProfileWtpSilentInterval, 3360 capwapBaseWtpProfileWtpStatisticsTimer, 3361 capwapBaseWtpProfileWtpWaitDTLSTimer, 3362 capwapBaseWtpProfileWtpEcnSupport 3363 } 3364 STATUS current 3365 DESCRIPTION 3366 "A collection of optional objects which are used to 3367 configure the WTP profile." 3368 ::= { capwapBaseGroups 6 } 3370 capwapBaseWtpStateGroup OBJECT-GROUP 3371 OBJECTS { 3372 capwapBaseWtpStateWtpIpAddressType, 3373 capwapBaseWtpStateWtpIpAddress, 3374 capwapBaseWtpStateWtpBaseMacAddress, 3375 capwapBaseWtpState, 3376 capwapBaseWtpStateWtpUpTime, 3377 capwapBaseWtpStateWtpCurrWtpProfileId 3378 } 3379 STATUS current 3380 DESCRIPTION 3381 "A collection of objects which are used to represent 3382 the WTP's state information." 3383 ::= { capwapBaseGroups 7 } 3385 capwapBaseWtpGroup OBJECT-GROUP 3386 OBJECTS { 3387 capwapBaseWtpBaseMacAddress, 3388 capwapBaseWtpTunnelModeOptions, 3389 capwapBaseWtpMacTypeOptions, 3390 capwapBaseWtpDiscoveryType, 3391 capwapBaseWtpRadiosInUseNum, 3392 capwapBaseWtpRadioNumLimit 3393 } 3394 STATUS current 3395 DESCRIPTION 3396 "A collection of objects which are used to represent 3397 the properties information for the WTPs in running state." 3398 ::= { capwapBaseGroups 8 } 3400 capwapBaseWtpGroup2 OBJECT-GROUP 3401 OBJECTS { 3402 capwapBaseWtpPhyIndex, 3403 capwapBaseWtpRetransmitCount, 3404 capwapBaseWtpMaxDiscoveries, 3405 capwapBaseWtpMaxFailedDTLSSessionRetry, 3406 capwapBaseWtpMaxRetransmit, 3407 capwapBaseWtpDataChannelKeepAliveTimer, 3408 capwapBaseWtpDataChannelDeadInterval, 3409 capwapBaseWtpDiscoveryInterval, 3410 capwapBaseWtpDTLSSessionDeleteTimer, 3411 capwapBaseWtpImageDataStartTimer, 3412 capwapBaseWtpRetransmitInterval 3413 } 3414 STATUS current 3415 DESCRIPTION 3416 "A collection of optional objects which are used to represent 3417 the properties information for the WTPs in running state." 3418 ::= { capwapBaseGroups 9 } 3420 capwapBaseRadioGroup OBJECT-GROUP 3421 OBJECTS { 3422 capwapBaseWirelessBindingVirtualRadioIfIndex, 3423 capwapBaseWirelessBindingType 3424 } 3425 STATUS current 3426 DESCRIPTION 3427 "A collection of objects which are used to represent 3428 the wireless binding type, the mappings between the 3429 ifIndexes of WLAN Virtual Radio Interfaces and PHY radios." 3430 ::= { capwapBaseGroups 10 } 3432 capwapBaseStationGroup OBJECT-GROUP 3433 OBJECTS { 3434 capwapBaseStationWtpId, 3435 capwapBaseStationWtpRadioId, 3436 capwapBaseStationAddedTime, 3437 capwapBaseStationVlanName 3438 } 3439 STATUS current 3440 DESCRIPTION 3441 "A collection of objects which are used to represent 3442 the stations' basic properties." 3443 ::= { capwapBaseGroups 11 } 3445 capwapBaseWtpEventsStatsGroup OBJECT-GROUP 3446 OBJECTS { 3447 capwapBaseWtpEventsStatsRebootCount, 3448 capwapBaseWtpEventsStatsInitCount, 3449 capwapBaseWtpEventsStatsLinkFailureCount, 3450 capwapBaseWtpEventsStatsSwFailureCount, 3451 capwapBaseWtpEventsStatsHwFailureCount, 3452 capwapBaseWtpEventsStatsOtherFailureCount, 3453 capwapBaseWtpEventsStatsUnknownFailureCount, 3454 capwapBaseWtpEventsStatsLastFailureType 3455 } 3456 STATUS current 3457 DESCRIPTION 3458 "A collection of objects which are used for collecting 3459 WTP reboot count, link failure count, hardware failure 3460 count and so on." 3461 ::= { capwapBaseGroups 12 } 3463 capwapBaseRadioEventsStatsGroup OBJECT-GROUP 3464 OBJECTS { 3465 capwapBaseRadioEventsStatsResetCount, 3466 capwapBaseRadioEventsStatsSwFailCount, 3467 capwapBaseRadioEventsStatsHwFailCount, 3468 capwapBaseRadioEventsStatsOtherFailCount, 3469 capwapBaseRadioEventsStatsUnknownFailCount, 3470 capwapBaseRadioEventsStatsConfigUpdateCount, 3471 capwapBaseRadioEventsStatsChannelChangeCount, 3472 capwapBaseRadioEventsStatsBandChangeCount, 3473 capwapBaseRadioEventsStatsCurrentNoiseFloor, 3474 capwapBaseRadioEventsStatsDecryptErrorCount, 3475 capwapBaseRadioEventsStatsLastFailType 3476 } 3477 STATUS current 3478 DESCRIPTION 3479 "A collection of objects which are used for collecting 3480 radio reset count, channel change count, hardware failure 3481 count and so on" 3482 ::= { capwapBaseGroups 13 } 3484 capwapBaseParametersGroup OBJECT-GROUP 3485 OBJECTS { 3486 capwapBaseAcMaxRetransmit, 3487 capwapBaseAcChangeStatePendingTimer, 3488 capwapBaseAcDataCheckTimer, 3489 capwapBaseAcDTLSSessionDeleteTimer, 3490 capwapBaseAcEchoInterval, 3491 capwapBaseAcRetransmitInterval, 3492 capwapBaseAcSilentInterval, 3493 capwapBaseAcWaitDTLSTimer, 3494 capwapBaseAcWaitJoinTimer, 3495 capwapBaseAcEcnSupport 3496 } 3497 STATUS current 3498 DESCRIPTION 3499 "Objects used for the CAPWAP protocol's parameters." 3500 ::= { capwapBaseGroups 14 } 3502 capwapBaseStatsGroup OBJECT-GROUP 3503 OBJECTS { 3504 capwapBaseFailedDTLSAuthFailCount, 3505 capwapBaseFailedDTLSSessionCount 3506 } 3507 STATUS current 3508 DESCRIPTION 3509 "Objects used for collecting the CAPWAP protocol's statistic." 3510 ::= { capwapBaseGroups 15 } 3512 capwapBaseNotificationsGroup NOTIFICATION-GROUP 3513 NOTIFICATIONS { 3514 capwapBaseChannelUp, 3515 capwapBaseChannelDown, 3516 capwapBaseDecryptErrorReport, 3517 capwapBaseJoinFailure, 3518 capwapBaseImageUpgradeFailure, 3519 capwapBaseConfigMsgError, 3520 capwapBaseRadioOperableStatus, 3521 capwapBaseAuthenticationFailure 3522 } 3523 STATUS current 3524 DESCRIPTION 3525 "A collection of notifications in this MIB module." 3526 ::= { capwapBaseGroups 16 } 3528 capwapBaseNotifyVarsGroup OBJECT-GROUP 3529 OBJECTS { 3530 capwapBaseNtfWtpId, 3531 capwapBaseNtfRadioId, 3532 capwapBaseNtfChannelType, 3533 capwapBaseNtfAuthenMethod, 3534 capwapBaseNtfChannelDownReason, 3535 capwapBaseNtfStationIdList, 3536 capwapBaseNtfAuthenFailureReason, 3537 capwapBaseNtfRadioOperStatusFlag, 3538 capwapBaseNtfRadioStatusCause, 3539 capwapBaseNtfJoinFailureReason, 3540 capwapBaseNtfImageFailureReason, 3541 capwapBaseNtfConfigMsgErrorType, 3542 capwapBaseNtfMsgErrorElements 3543 } 3544 STATUS current 3545 DESCRIPTION 3546 "Objects used for notifications." 3547 ::= { capwapBaseGroups 17 } 3549 capwapBaseNotifyControlGroup OBJECT-GROUP 3550 OBJECTS { 3551 capwapBaseChannelUpDownNotifyEnable, 3552 capwapBaseDecryptErrorNotifyEnable, 3553 capwapBaseJoinFailureNotifyEnable, 3554 capwapBaseImageUpgradeFailureNotifyEnable, 3555 capwapBaseConfigMsgErrorNotifyEnable, 3556 capwapBaseRadioOperableStatusNotifyEnable, 3557 capwapBaseAuthenticationFailureNotifyEnable 3558 } 3559 STATUS current 3560 DESCRIPTION 3561 "Objects used to enable or disable notifications." 3562 ::= { capwapBaseGroups 18 } 3564 END 3565 11. Security Considerations 3567 There are a number of management objects defined in this MIB module 3568 with a MAX-ACCESS clause of read-write and/or read-create. Such 3569 objects MAY be considered sensitive or vulnerable in some network 3570 environments. The support for SET operations in a non-secure 3571 environment without proper protection can have a negative effect on 3572 network operations. The followings are the tables and objects and 3573 their sensitivity/vulnerability: 3575 - Unauthorized changes to the capwapBaseWtProfileTable, and writable 3576 objects under capwapBaseAcs group MAY disrupt allocation of resources 3577 in the network. For example, a WTP's static IP address could be 3578 changed by set capwapBaseWtpProfileWtpStaticIp object. 3580 - Unauthorized changes to writable objects under the capwapBaseAc 3581 group, it MAY disrupt allocation of resources in the network. For 3582 example, a invalid value for capwapBaseWtpSessionsLimit object will 3583 increase the AC's traffic burden. Also, some objects such as 3584 capwapBaseDataChannelDTLSPolicyConfig MAY cause network unsafe. 3586 - Unauthorized changes to the capwapBaseMacAclTable, it MAY cause 3587 legal stations unable to access the network any more while illegal 3588 stations have chance to access the network. 3590 - Unauthorized changes to writable objects under the 3591 capwapBaseParameters group, it MAY influence CAPWAP protocol 3592 behaviour and status. For example, an invalid value set for the 3593 capwapBaseAcDataCheckTimer MAY influence the CAPWAP state machine. 3595 Some of the readable objects in this MIB module (i.e., objects with a 3596 MAX-ACCESS other than not-accessible) MAY be considered sensitive or 3597 vulnerable in some network environments. It is thus important to 3598 control even GET and/or NOTIFY access to these objects and possibly 3599 to even encrypt the values of these objects when sending them over 3600 the network via SNMP. The followings are the tables and objects and 3601 their sensitivity/vulnerability: 3603 - The capwapBaseDataChannelDTLSPolicyOptions and 3604 capwapBaseControlChannelAuthenOptions under the capwapBaseAc group 3605 exposes the current security option for CAPWAP data and control 3606 channels. 3608 - The capwapBaseWtpTable exposes a WTP's important information like 3609 tunnel mode, MAC type and so on. 3611 - The capwapBaseWtpEventsStatsTable exposes a WTP's failure 3612 information. 3614 - The capwapBaseRadioEventsStatsTable exposes a radio's failure 3615 information. 3617 SNMP versions prior to SNMPv3 did not include adequate security. 3618 Even if the network itself is secure (for example by using IPSec), 3619 even then, there is no control as to who on the secure network is 3620 allowed to access and GET/SET (read/change/create/delete) the objects 3621 in this MIB module. 3623 It is RECOMMENDED that implementers consider the security features as 3624 provided by the SNMPv3 framework (see [RFC3410], section 8), 3625 including full support for the SNMPv3 cryptographic mechanisms (for 3626 authentication and privacy). 3628 Further, the deployment of SNMP versions prior to SNMPv3 is NOT 3629 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3630 enable cryptographic security. It is then a customer/operator 3631 responsibility to ensure that the SNMP entity giving access to an 3632 instance of this MIB module is properly configured to give access to 3633 the objects only to those principals (users) that have legitimate 3634 rights to indeed GET or SET (change/create/delete) them. 3636 12. IANA Considerations 3638 12.1. IANA Considerations for CAPWAP-BASE-MIB Module 3640 The MIB module in this document uses the following IANA-assigned 3641 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3643 Descriptor OBJECT IDENTIFIER value 3644 ---------- ----------------------- 3646 capwapBaseMIB { mib-2 XXX } 3648 12.2. IANA Considerations for ifType 3650 Require IANA to assign a ifType for the WTP Virtual Radio Interface. 3652 13. Contributors 3654 This MIB module is based on contributions from Long Gao. 3656 14. Acknowledgements 3658 Thanks to David Harrington, Dan Romascanu, Abhijit Choudhury, Bert 3659 Wijnen and David L. Black for helpful comments on this document and 3660 guiding some technique solution. 3662 The authors also thank their friends and coworkers Fei Fang, Xuebin 3663 Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Hao Wang, Yujin Zhao, 3664 Haitao Zhang, Xiansen Cai and Xiaolan Wan. 3666 15. References 3668 15.1. Normative References 3670 [RFC2119] Bradner, S., "Key words for use in 3671 RFCs to Indicate Requirement Levels", 3672 BCP 14, RFC 2119, March 1997. 3674 [RFC2287] Krupczak, C. and J. Saperia, 3675 "Definitions of System-Level Managed 3676 Objects for Applications", RFC 2287, 3677 February 1998. 3679 [RFC2578] McCloghrie, K., Ed., Perkins, D., 3680 Ed., and J. Schoenwaelder, Ed., 3681 "Structure of Management Information 3682 Version 2 (SMIv2)", STD 58, RFC 2578, 3683 April 1999. 3685 [RFC2579] McCloghrie, K., Ed., Perkins, D., 3686 Ed., and J. Schoenwaelder, Ed., 3687 "Textual Conventions for SMIv2", 3688 STD 58, RFC 2579, April 1999. 3690 [RFC2580] McCloghrie, K., Perkins, D., and J. 3691 Schoenwaelder, "Conformance 3692 Statements for SMIv2", STD 58, 3693 RFC 2580, April 1999. 3695 [RFC2863] McCloghrie, K. and F. Kastenholz, 3696 "The Interfaces Group MIB", RFC 2863, 3697 June 2000. 3699 [RFC3411] Harrington, D., Presuhn, R., and B. 3700 Wijnen, "An Architecture for 3701 Describing Simple Network Management 3702 Protocol (SNMP) Management 3703 Frameworks", STD 62, RFC 3411, 3704 December 2002. 3706 [RFC3418] Presuhn, R., "Management Information 3707 Base (MIB) for the Simple Network 3708 Management Protocol (SNMP)", STD 62, 3709 RFC 3418, December 2002. 3711 [RFC4001] Daniele, M., Haberman, B., Routhier, 3712 S., and J. Schoenwaelder, "Textual 3713 Conventions for Internet Network 3714 Addresses", RFC 4001, February 2005. 3716 [RFC4133] Bierman, A. and K. McCloghrie, 3717 "Entity MIB (Version 3)", RFC 4133, 3718 August 2005. 3720 [RFC5415] Calhoun, P., Montemurro, M., and D. 3721 Stanley, "Control And Provisioning of 3722 Wireless Access Points (CAPWAP) 3723 Protocol Specification", RFC 5415, 3724 March 2009. 3726 15.2. Informative References 3728 [IEEE.802-11.2007] "Information technology - 3729 Telecommunications and information 3730 exchange between systems - Local and 3731 metropolitan area networks - Specific 3732 requirements - Part 11: Wireless LAN 3733 Medium Access Control (MAC) and 3734 Physical Layer (PHY) specifications", 3735 IEEE Standard 802.11, 2007, . 3739 [RFC3168] Ramakrishnan, K., Floyd, S., and D. 3740 Black, "The Addition of Explicit 3741 Congestion Notification (ECN) to IP", 3742 RFC 3168, September 2001. 3744 [RFC3410] Case, J., Mundy, R., Partain, D., and 3745 B. Stewart, "Introduction and 3746 Applicability Statements for 3747 Internet-Standard Management 3748 Framework", RFC 3410, December 2002. 3750 [RFC4118] Yang, L., Zerfos, P., and E. Sadot, 3751 "Architecture Taxonomy for Control 3752 and Provisioning of Wireless Access 3753 Points (CAPWAP)", RFC 4118, 3754 June 2005. 3756 [RFC4347] Rescorla, E. and N. Modadugu, 3757 "Datagram Transport Layer Security", 3758 RFC 4347, April 2006. 3760 [RFC5416] Calhoun, P., Montemurro, M., and D. 3761 Stanley, "Control and Provisioning of 3762 Wireless Access Points (CAPWAP) 3763 Protocol Binding for IEEE 802.11", 3764 RFC 5416, March 2009. 3766 [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., 3767 and Y. Zhang, "CAPWAP Protocol 3768 Binding MIB for IEEE 802.11", 3769 draft-ietf-capwap-802dot11-mib-06 3770 (work in progress), Jan 2010. 3772 RFC Editor - please remove the appendix before publication of the RFC 3774 Appendix A. Appendix A. Changes between -07 and -06 3776 1) Close IESG review issues raised by Bert Wijnen 3778 -------------------------------------------------------------- 3780 Added some notification control objects such as 3781 capwapBaseChannelUpDownNotifyEnable; Update the description to 3782 explain the objects of RowStatus type; give the note in the object 3783 description to explain why the object such as 3784 capwapBaseWtpProfileWtpEcnSupport starting value is zero; Added the 3785 MODULE IF-MIB. 3787 2) Close Gen-ART review issues raised by David L. Black 3789 -------------------------------------------------------------- 3791 Close some editorial problems such as using "index" instead of 3792 "handler"; Changed some text to make it clear. 3794 Authors' Addresses 3796 Yang Shi (editor) 3797 Hangzhou H3C Tech. Co., Ltd. 3798 Beijing R&D Center of H3C, Digital Technology Plaza, 3799 NO.9 Shangdi 9th Street,Haidian District, 3800 Beijing 3801 China(100085) 3803 Phone: +86 010 82775276 3804 EMail: young@h3c.com 3805 David Perkins (editor) 3806 SNMPinfo 3807 288 Quailbrook Ct San Carlos, 3808 CA 94070 3809 USA 3811 Phone: +1 408 394-8702 3812 EMail: dperkins@snmpinfo.com 3814 Chris Elliott (editor) 3815 Cisco Systems, Inc. 3816 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 3817 27709 3818 USA 3820 Phone: +1 919-392-2146 3821 EMail: chelliot@gmail.com 3823 Yong Zhang (editor) 3824 Fortinet, Inc. 3825 1090 Kifer Road 3826 Sunnyvale, CA 94086 3827 USA 3829 EMail: yzhang@fortinet.com